I lost track of which versions of CM have which issues.
My phone has finally started exhibiting the flicker issue. I'd like to revert back to whichever CM it was prior to this becoming a problem, but I can't recall which it was. Were those the MDM builds?
Or do I have to avoid CM altogether if I want to avoid the flicker? I hope not, as it would kill me to have to go back to Viper after all this time on JB!
You should try techyon. It is a cm based build. I have had no issues on his rom.
Sent from my Fireball on TACHYON using XDA Premium 4 mobile app
any cm build with the 3.14 kernel will have a high % of the flickering screen. this hasnt been fixed yet. FYI
Right - my question is when was the kernel integrated? What versions are prior to that which I could try?
chupajr said:
Right - my question is when was the kernel integrated? What versions are prior to that which I could try?
Click to expand...
Click to collapse
you want to use mdm's 5 build.
(I cant post a link, but go to the CM thread, and go to "unofficial builds")
chupajr said:
Right - my question is when was the kernel integrated? What versions are prior to that which I could try?
Click to expand...
Click to collapse
that i dont know for sure. i know the 10.2 all have the 3.14 so you will need to look at 10.1
i do believe @PrimePalaver is correct, the mdm05 was one of the last builds with the 3.08 kernel
http://goo.im/devs/mdmower/fireball/cyanogenmod/mdm-releases
Related
Hi,
I am using CM 9 (14th April nightly build). I flashed Siyah's kernel 3.1rc4. Everything seems to work fine with it. But then I flashed the Speedmod kernel (K3-9).
Now when my phone boots, I don't see any boot animation and as soon as the lockscreen appears I get lots of "has stopped working popups" for various services (phone, acore etc etc) and the phone is basically un-usable.
I tried flashing CM 9 again, so that I get Codeworx's kernel. I flashed Speedmod over it but still the same problem
Anyone here facing/faced a similar issue ?
Thanks!
why are you migrating yourself from no problems to problems,
forget the Kernel which is giving treble thats it...or you really want to know the reason ask in the speedmode kernel thread....
amodj said:
Hi,
I am using CM 9 (14th April nightly build). I flashed Siyah's kernel 3.1rc4. Everything seems to work fine with it. But then I flashed the Speedmod kernel (K3-9).
Now when my phone boots, I don't see any boot animation and as soon as the lockscreen appears I get lots of "has stopped working popups" for various services (phone, acore etc etc) and the phone is basically un-usable.
I tried flashing CM 9 again, so that I get Codeworx's kernel. I flashed Speedmod over it but still the same problem
Anyone here facing/faced a similar issue ?
Thanks!
Click to expand...
Click to collapse
Yep, problems faced too.speedmod kernel just doesnt work for me,even when i was on gb
Sent from my GT-I9100 using XDA
engloa said:
Yep, problems faced too.speedmod kernel just doesnt work for me,even when i was on gb
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Oh that is sad ! Speedmod was the best kernel that I had on GB. That is why I wanted to try out the ICS version.
zaheedahmed said:
why are you migrating yourself from no problems to problems,
Click to expand...
Click to collapse
Because I haven't found a sweet spot yet. That is why I am experimenting with different kernels.
zaheedahmed said:
forget the Kernel which is giving treble thats it...or you really want to know the reason ask in the speedmode kernel thread....
Click to expand...
Click to collapse
Will post in the speedmod thread. Just wanted to know if this was a generic problem with all kernels or just speedmod specific.
It says very clearly in the Speedmod thread that it works only on Samsung based firmwares. CM9, AOKP, etc... are not Samsung based firmwares, so not too surprisingly it doesn't work.
thracemerin said:
It says very clearly in the Speedmod thread that it works only on Samsung based firmwares. CM9, AOKP, etc... are not Samsung based firmwares, so not too surprisingly it doesn't work.
Click to expand...
Click to collapse
Whoops ! missed that ! Thanks a lot
i have just updated to the lastest cm10.1 nightly update today and when i re-flash siyah 1.8.6 all sorts of problems breaks loose.
the cyanogen bootup logo was extremely slow and when the phone eventually booted up it was unusably lagging.
i has to restore from a backup and when i tried to reinstall siyah again, the same thing happens. I think i am correct to assume that it is the kernel that is causing the problems.
i am now using the stock cm kernal but i am missing the fact i can overclock my beast
anyone else having this issue and will it be fixed on further cm updates or will it be a siyah updating issue??
Thanks
kennyc1980 said:
i have just updated to the lastest cm10.1 nightly update today and when i re-flash siyah 1.8.6 all sorts of problems breaks loose.
the cyanogen bootup logo was extremely slow and when the phone eventually booted up it was unusably lagging.
i has to restore from a backup and when i tried to reinstall siyah again, the same thing happens. I think i am correct to assume that it is the kernel that is causing the problems.
i am now using the stock cm kernal but i am missing the fact i can overclock my beast
anyone else having this issue and will it be fixed on further cm updates or will it be a siyah updating issue??
Thanks
Click to expand...
Click to collapse
20130113*
kennyc1980 said:
20130113*
Click to expand...
Click to collapse
Have you installed 1st or 2nd rom ?
Have you tried the new update ? (Siyah 1.8.7)
Problem verifyed with: Yank.555 1.4, Siyah 1.8.6
Do not install these kernels with the latest CM10.1 nightly (13. jan) - use stock or Siyah 1.8.7 instead
This is quite strange because I use the Rom ReVolt 3.3.3 available here.
It uses Android 4.2.1 and I have Siyah Kernel 1.8.6.
So there might be a sort of compatibility ...
I have upgraded to the 1.8.7 and its fixed the problem ;]
Sent from my GT-I9300 using xda app-developers app
So with the 1.8.7 you can use the kernel on cm 10.1 ?
Sent from my GT-I9300 using Tapatalk 2
ruskat said:
So with the 1.8.7 you can use the kernel on cm 10.1 ?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Yes only as primair rom
daveve said:
Yes only as primair rom
Click to expand...
Click to collapse
But Gokhanmoral's website says "cm10.1 is now supported in dual-boot configurations" with the latest 1.8.7 build.
I am new to the rooting / rom / kernel game and done some research. I am just wanting to double check to make sure this is the correct one for me.
This is the rom I am wanting to use: [ROM][4.2.1][19/01]Slim Bean - I9100 [RC1]
My phone is rooted and I have done my rom backup and titanium backup of "All user apps + system data".
I just want to make sure this is the correct rom for my phone so I don't brick the damn thing lol.
My Model is:GT-I9100Android Version:4.0.3Baseband Version:I9100XXLPSKernel Version:[email protected] #3
yes, that rom will work.
be advised since they are starting with a new base, you may find it full of bugs and FC.
Cosmic Blue said:
yes, that rom will work.
be advised since they are starting with a new base, you may find it full of bugs and FC.
Click to expand...
Click to collapse
Would you suggest maybe going down a couple versions then?
ecordell said:
Would you suggest maybe going down a couple versions then?
Click to expand...
Click to collapse
Why not try CM9 (ICS) or CM10 (JB 4.1.2) or CM10.1 (JB 4.2.1). CM10 looks like stock Android but has some good tweaks. Alternatively if you would prefer as close as stock as possible try the rom you mentioned but get previous base version until they release final of JB base.
When you restore from Titanium its not "recommended" to restore the data as well if you have changed android versions. (although i generally ignore that advice)
the cm10 nightly from 22nd installed on my new s2 a breeze, i just installed a non stock kernel first.
I went ahead and installed their 3.1 version and had all kinds of bugs, so I went ahead and flashed the 4.2.1 version. Everything works great except my damn clock keeps restarting. I get a message "Clock has stopped" and then it resets to a random time. Then I reboot and it grabs my time from my provider again....
Anyone have any idea?
TheATHEiST said:
Why not try CM9 (ICS) or CM10 (JB 4.1.2) or CM10.1 (JB 4.2.1).
Click to expand...
Click to collapse
Do you know why stable releases disappeared from get.cm/?device=i9100 and why the last stable is 9.1 in get.cm/?device=galaxys2 ? (sorry I cannot post links)
ecordell said:
I went ahead and installed their 3.1 version and had all kinds of bugs, so I went ahead and flashed the 4.2.1 version. Everything works great except my damn clock keeps restarting. I get a message "Clock has stopped" and then it resets to a random time. Then I reboot and it grabs my time from my provider again....
Anyone have any idea?
Click to expand...
Click to collapse
Did you look for people with the same problem(s) as you in the rom-thread? If not, you can better ask there in the specific thread.
vipervault said:
Do you know why stable releases disappeared from get.cm/?device=i9100 and why the last stable is 9.1 in get.cm/?device=galaxys2 ? (sorry I cannot post links)
Click to expand...
Click to collapse
Because CM9.1 was their most recent stable version. CM10 was never really finished and the development went on to CM10.1, which is still 'under construction'
Sent from the Matrix
Tried searching first but couldn't really find anything
I know there aren't any kernels available for the 4.4 kitkat roms but I was curious if any of the 4.3 kernels would functions. Ideally I just want to be able to do some overclocking.
keithwired said:
Tried searching first but couldn't really find anything
I know there aren't any kernels available for the 4.4 kitkat roms but I was curious if any of the 4.3 kernels would functions. Ideally I just want to be able to do some overclocking.
Click to expand...
Click to collapse
I am using Palmer's kernel. It works well for me going on 3 days with omni. But don't complain if it breaks something as its not a supported kernel.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
I am using Palmer's kernel. It works well for me going on 3 days with omni. But don't complain if it breaks something as its not a supported kernel.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
4.90 for CM10.2?
4.90 for CM 10.2 broke wifi and possibly some other stuff on CM 11.0 unofficial. Had to nandroid back, perhaps palmers kernel only works on AOSP based roms for 4.4
Yes, WiFi will be broken on any newer builds. In 10.2 it assumes a kernel module and now it assumes that the WiFi driver is built into the kernel.
In addition to WiFi issues, I would expect some oddities in the display. These may get worse on the next round of builds.
For the time being, you'll need to be patient. Any time I spent on a custom kernel would mean less working on getting our device supported properly for CM 11.
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
My CM version
klin1344 said:
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
cm-11-20140407-NIGHTLY-jewel.zip
rohanpatelt7 said:
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Click to expand...
Click to collapse
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Reply
numel007 said:
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
rohanpatelt7 said:
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
Click to expand...
Click to collapse
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Thanks
numel007 said:
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
rohanpatelt7 said:
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
Click to expand...
Click to collapse
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Reply
GoblinZ said:
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Click to expand...
Click to collapse
Thanks! I am going to flash this after my root tonight but just a question, are you going to be following the updates with the nighties? CM's updater won't work will it with your build of it? Thanks!