Reputation
246
Top tag
Next privilege 250 Rep.
View close votes
Badges
2 4 10
Impact
~33k people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Apr
27
awarded  Nice Question
Apr
21
awarded  Famous Question
Jun
18
awarded  Famous Question
Jan
26
awarded  Yearling
May
16
awarded  Nice Question
Mar
22
awarded  Notable Question
Feb
10
awarded  Notable Question
Dec
27
awarded  Notable Question
Dec
21
awarded  Popular Question
Nov
24
awarded  Popular Question
Nov
1
awarded  Popular Question
Aug
18
awarded  Tumbleweed
Aug
10
awarded  Commentator
Aug
10
comment Why are there so many different Android kernels (technical answer please)
From what you are saying the drivers are not all compiled as modules but integrated into the Kernel itself, so even if CM gets a working kernel on a device it can not simply "move the XXX modules" to the new build and have it work because there may not be XXX moduels. The drivers must be hunted down, hacked (possibly), and recompile.
Aug
10
awarded  Scholar
Aug
10
awarded  Supporter
Aug
10
comment Why are there so many different Android kernels (technical answer please)
Upvotes all around!!! Thanks for the detailed answer.
Aug
10
accepted Why are there so many different Android kernels (technical answer please)
Aug
10
comment Why are there so many different Android kernels (technical answer please)
Yes but why the need to hack. If they work with the OEM kernel, why can't you just move the driver files and associated libraries to the Cyanogen mod installation since the kernel is basically the same.
Aug
10
comment Why are there so many different Android kernels (technical answer please)
What I mean is for example with CyanogenMod there are always complaints of my wifi, bluetooth, etc doesn't work. Why do these drivers have to be "ported" to CyanogenMod. Why can't they just take the stock drivers, copy them to the device, and run them with CyanogenMod