Related
Hi I had just flashed the new CM7 RC2 and I flashed the snap dragon kernel and now the 4g is stuck on turning on. I was wondering if CM7 RC2's original kernel is the reason why it works.
If so is there a way to get the original kernel or do I have to reflash everything? Please let me know thanks!
Just reflash the rc2. The kernal in there is why 4g works. Or u can use the savagenzen kernal and just flash that on top of rc2
yeah im using the Savage Zen 0.1.2 can its working great for me....battery life is also amazing with this kernel....give it a go....u can always go back
I only see rc1 and nightly 14 where is rc2???
I can not find where to get rc2. It is not on my ROM Manager
RC2: http://download.cyanogenmod.com/get/update-cm-7.0.0-RC2-Supersonic-signed.zip
GApps 20110307 (Flash immediately after RC2): http://goo-inside.me/gapps/latest/7/universal/
drmacinyasha said:
RC2
Click to expand...
Click to collapse
What's the difference between this and RC1? besides wimax I mean. And is it pretty stable right now? Cause RC1 works like a dream for me.
bluestatus said:
What's the difference between this and RC1? besides wimax I mean. And is it pretty stable right now? Cause RC1 works like a dream for me.
Click to expand...
Click to collapse
Alot has changed. Maybe you should take the time and read up on it.
Sent from my PC36100 using XDA App
All that matters to me is speed, stability and battery life.
I have been running Darkys 9.2 for a long time now, but the battery life is getting to be very poor, so looking to try out something new.
Appart from the battery life if has been rock solid to date.
Any advice is welcome
Sent from my GT-I9000 using XDA App
"All that matters to me is speed, stability and battery life."
...bit like saying "all that matters is health, wealth and happiness"
There are plenty out there and only one way to find out, happy flashing
Sent from my GT-I9000 using XDA App
In my opinion, there isn't a perfect rom in this world which matches your description. However, if I were to choose one, I would choose Cyanogenmod 7. It is currently on Nightly, but it is stable enough for daily usage. Battery life is not that good, but its speed complements it, combined with loads of customisations available.
I hope that helps, mate
Sent from my GT-I9000 using XDA App
djglenn1337 said:
All that matters to me is speed, stability and battery life.
Click to expand...
Click to collapse
So why not flash stock odexed JVQ without any modifactions?
Try s.u.f.a.ce rom .Its a base rom with addons I installed the base and manually extracted and installed what I wanted from the addons. Almost a build your own without being a developer. Fastest rom ive tried with best battery because its light
Sent from my GT-I9000 using XDA App
kb909 said:
Try s.u.f.a.ce rom .Its a base rom with addons I installed the base and manually extracted and installed what I wanted from the addons. Almost a build your own without being a developer. Fastest rom ive tried with best battery because its light
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This ^
Ive tried a bunch, I only flashed this ROM cuz Sam ported a theme I liked ended up liking the ROM since its a barebones ROM
Other then that ROM Id go with just a stock JVQ, Ive always fallen back to the stock ROMs after not liking something about the customs I installed
Thanks guys will give s.u.r.f.a.c.e a shot!
Just out of interest, does it have a lagfix like Darkys rom?
Cyanogen's battery issues are keeping me away from it for now.
I have it on my wife's wildfire and its a completely new animal since I flashed it.
djglenn1337 said:
Thanks guys will give s.u.r.f.a.c.e a shot!
Just out of interest, does it have a lagfix like Darkys rom?
Cyanogen's battery issues are keeping me away from it for now.
I have it on my wife's wildfire and its a completely new animal since I flashed it.
Click to expand...
Click to collapse
Yes it does
F1 Galaxy S2 V6
no battery drain and smooth with galaxianEE2.4 kernel
GingerReal 7.1.4 , Semaphore 1.3.3. kernel, works briliant-e.
Search: Android Development topic
Stock is the best...
In the past weeks i tested several roms and kernels.
Roms: GingerReal 7.1.4, Surface 2.1, Juwe 5.2, CM7, Darky 10.2
Kernel: Speedmod, Galaxian, Semaphore
For me the best pair is Darkys Rom with the semaphore kernel on EXT4.
I never had such a smooth, speedy and long battery usage on any rom/kernel.
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
it was the same for me. nscollab was unusable since it was always freezing in two minutes after boot. changing the kernel did not help. so I decided to change the rom to Nexus MV 10.05. it works very stable (not a single reboot or freeze) and faster than nscollab.
mikkkg said:
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
Click to expand...
Click to collapse
Well, I found that custom kernels can work with stock ROM's. I'm using stock Google 2.3.6 on my 9023 + pete's kernel with Voodoo sound and BLN. Stable as ****, practically no issues, I'm happy with my NS as never before just because of the lack of constant flashing the **** around to "optimize". It just works flawlessly.
Here's the link to the kernel : http://www.peteralfonso.com/2011/08/download-nexus-s-263514-kernel.html
Had the no wake issue with cm7 216 and nscol 1.4.5. On nscol 1.4.6 and no problems yet. If it happens again it would seem to be a cm7 issue. While annoying devs are constantly hunting down and correcting problems, just the way it is and doesn't bother me.
Sent from my Nexus S using xda premium
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
The hole point for me is not using any other kernel but the stock one.. compile yourself a nexus s kernel (google it for how to) and be happy without any reboot, crash..
baterry? normally 1.5 days @ 1.0ghz..
You could do that as well
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
.45 with stock voltages caused the "pin asking" issue even with stock voltages(even with 5.5 cfs - maybe a cyanogen problem?), so that's why i am stuck at .42 with 5.5 cfs and did not even try .46.
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
If you see, in the thread of nscollab, there are also problems with the phone dying etc, even with the new stable cyanogenmod + matr1x kernel.
I only do tests in my mobile during the weekend, because i use it all week for my job. So stuck with matr1x 5.5 until i see a really stable matr1x kernel coming after 8.
madd0g said:
Here's the link to the kernel :
Click to expand...
Click to collapse
Thank you very much for posting this link. I did not know that kernel. I just found some time to flash nscollab .50 with this kernel and i only changed interactive governor with ondemand to be even closer to stock kernel.
I hope that it is as stable as it is for you.
After some hours with this new kernel, i am not sure about stability(although it seems stable) but nexus is running smoothier than ever.
I've used ondemand from the beginning I started using this kernel, then I tried interactive (default) just to try it out. Not really a difference, same stability/speed and I could get rid of NoFrillsCPU app setting the default governor at startup. So to wrap up, kernel runs beautiful from the start, no extra fiddling necessary.
I do not believe the issues described in the OP are kernel related. They persist in all custom kernels. I think it is from Dalvik VM crash but I have no proof.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Id say if you want stability, stay on stock, extra features like BLN and Voodoo sound are added via kernel anyway.
Sent from my Nexus S using Tapatalk
mikkkg said:
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Click to expand...
Click to collapse
Kalimocho found a kernel error and a missing vendor file in the CM kernel. It will be fixed in the next nightly. The hope is that this was the cause of the freezes/reboots/bootloops/dimscreen bootloops that people were seeing.
mikkkg said:
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
Click to expand...
Click to collapse
I use this, if it helps you.
Thread here.
mikkkg said:
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
Click to expand...
Click to collapse
lol i keep looking but i dont find anything
ahhhh
Just wondering what ROM people say is the most stable and dependable. I've heard 201 is the best out right now. Opinions?
Sent via Tapatalk on my *voided* Evo running CM 7.1.0
At the moment I'd say the most problem free is MiRaGe. None of the stables or nightlies have the latest SOD fix in plus other fixes for things like phone signal icon showing up.
MiRaGe has these fixes in plus some other optimizations.
bobtidey said:
At the moment I'd say the most problem free is MiRaGe. None of the stables or nightlies have the latest SOD fix in plus other fixes for things like phone signal icon showing up.
MiRaGe has these fixes in plus some other optimizations.
Click to expand...
Click to collapse
+1 for MiRaGe.
Merry Christmas
MiRaGe for me with the mods suggested. http://forum.xda-developers.com/showthread.php?t=1344873
+1 MiRaGe.
Since no more official CM nightlies are coming, I've also started using Mirage off SD boot. No problems so far.
mr72 said:
+1 MiRaGe.
Click to expand...
Click to collapse
I have done 2 Nooks with this and have found it pretty good except I can't seem to apply updates per the normal process. Haven't needed to yet (didn't use the updated theme because it wouldn't apply)
@bobstro CM tweeted awhile back (shortly after AOSP released ICS source 4.0.1) that stable CM 7.2 was in the works still. I believe they are finalizing stability issues while also working on the new CM9 simultaneously. It's just that most devs are playing with the new source right now, getting preliminary work done to set up CM9.
But as far as recommendations go, Mirage Kang is solid. Just be sure to rename phone.apk to phone.apk.bak for increased battery life.
I also recommend LauncherPro, however, with this ROM, I cannot get versions newer than 0.8.3 to install.
disynthetic said:
@bobstro CM tweeted awhile back (shortly after AOSP released ICS source 4.0.1) that stable CM 7.2 was in the works still.
Click to expand...
Click to collapse
I'll definitely check it out when it becomes available. n253 was giving me grief that Mirage seems to have cleared up in the meantime!
I believe they are finalizing stability issues while also working on the new CM9 simultaneously. It's just that most devs are playing with the new source right now, getting preliminary work done to set up CM9.
Click to expand...
Click to collapse
I'm definitely looking forward to checking out CM9 as well.
Hi. I'm running CM10.1 stable because I don't have much time to test the latest nightlies and need a stable phone. Everything works ok, but battery doesn't seem to last as much as it did when I had the stock ROM (Google's 4.3 ROM).
I wanted to try Franco Kernel to see if it helps with battery. Has anyone tried it with CM10.1 stable (Android 4.2.2)? It should work accoding to the Franco Kernel thread, but I wanted someone to confirm if it actually does, and maybe hear some opinions. Thanks!
lopardo said:
Hi. I'm running CM10.1 stable because I don't have much time to test the latest nightlies and need a stable phone. Everything works ok, but battery doesn't seem to last as much as it did when I had the stock ROM (Google's 4.3 ROM).
I wanted to try Franco Kernel to see if it helps with battery. Has anyone tried it with CM10.1 stable (Android 4.2.2)? It should work accoding to the Franco Kernel thread, but I wanted someone to confirm if it actually does, and maybe hear some opinions. Thanks!
Click to expand...
Click to collapse
Yep running 10.1.2 stable with the last 4.2.2 franco here
Sent from my Nexus 4 using Tapatalk 4
Warbuff said:
Yep running 10.1.2 stable with the last 4.2.2 franco here
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Ah, thanks. Do you think it helps with battery life? Also, I should flash these ones, right?
Yea in my situation it has helped with battery life. I average 11 to 13 hrs on battery. I'm running build 163. For some reason the link you placed I couldn't click so here's the milestones http://minooch.com/franciscofranco/Nexus4/4.2.2/milestones/
If you get the chance try to look for in the thread for build 165 as that was the last 4.2.2 release and more recent than the milestones
Sent from my Nexus 4 using Tapatalk 4
Warbuff said:
Yea in my situation it has helped with battery life. I average 11 to 13 hrs on battery. I'm running build 163. For some reason the link you placed I couldn't click so here's the milestones http://minooch.com/franciscofranco/Nexus4/4.2.2/milestones/
If you get the chance try to look for in the thread for build 165 as that was the last 4.2.2 release and more recent than the milestones
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thank you very much. Build 165 seems to be in http://minooch.com/franciscofranco/Nexus4/4.2.2/
I'm going to try that one. Thanks!
Using milestone 3 with cm 10.1.2 stable and definitely notice better battery life. I only flashed it last night but so far im at 15 hours on the battery with 3 hours of on screen time and its only at 50%.