Database Users

[Q] SETCPU

Hey, quick question: I am on mytouch 4g cm7 ROM
What is a safe max to set the overclocking at? Obviously I don't want to burn the chip, but I want to make it as fast as possible. I have LauncherPro, currently my max is at 1.4, but sometimes it lags when I gesture to expand home screens.
I have 7 Home screens, all of them have 1 or more widget..
Thanks

1.5 is a good speed but you really wanna avoid charging when its set that high. so when charging set it to 1.2. Also what Kernel are you using? Defaults on Faux123 ASOP kernel should do well. I'n still on T-Mo stock and i run defaults with Faux123 Sense Kernel and i have no lag at all so CM7 whit its optimized code and no bloat it should run like a dream with one of his kernels, no OC Needed
Edit: corrected Link
http://forum.xda-developers.com/showthread.php?t=957267

Will the Kernel you linked to work with CM7 rc3? It only mentions CM6
Nm, Cm7 is the gingerbread...see it..got it, thanks!

I kept mine at 1.2ghz. Never gave me a problem.
sent from the rooty tooty fresh and fruity cm7 nighly powered G2

So I flashed 2.3.0 , then like the thread says, before rebooting, I flashed 2.4.3 stock version.
However, I am getting a wi-fi error. I saw some posts on it, and they said to "fix permissions". So I did that, yet still seeing a wi-fi error.
So for now, I restored my backup, but I would really like to have this kernel, do you know what I am doing wrong or what I can do to fix it?
Thanks

My mistake i linked the wrong Kernel here you go.
http://forum.xda-developers.com/showthread.php?t=957267

Yeah, I did use that link, however as described above, the wifi is giving me an error..any idea of a fix or what I am doing wrong?

I was getting the same issues. Then I reflashed the rom, rebooted before turning wifi on and had no problems. Also have had no problems set at 1.75 max and .75 min on minmax. Have been using that setting since faux started making his kernels (cm7 amd froyo based) and have never froze once. Quadrant scores for the new evil dhd ext 4 rom at 2900.
Sent from my HTC Glacier using XDA App

Low voltage kernels

Just rooted. Im new to the droid world, so im curious, can i get a low voltage kernel? A friend has Savage Zen and brags about battery life, but would it be compatible with my default-rooted rom? Also can i backup the kernel? Thanks.
Btw i tried googling but every time i got a good lead the links were dead
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock, came preinstalled) hardware v.4 bought new in July.

If you are referring to a rooted, stock HTC Sense ROM, no, do not use SavagedZen. It is only for AOSP ROMs.
AOSP - Android Open Source Project (vanilla, like on the Nexus)
Sense - HTC's UI
You cannot use a Sense kernel on an AOSP ROM, or an AOSP kernel on a Sense ROM.
(All Gingerbread)
AOSP Kernels:
Tiamat
SavagedZen
Cyanogenmod (kernel)
Godmode
PoonKang
I know that Tiamat and SavagedZen have HAVS and can be undervolted using Vipermod. Cyanogenmod, Godmode and Poonkang may come undervolted, but they do not have HAVS so you cannot adjust it.
Sense Kernels:
Freedom by Lithid
Golden Monkey by Netarchy
ChopSuey by barnacles10
Stock HTC
None of these kernels have HAVS (Freedom used to, but it was causing issues so he took it out). Golden Monkey, ChopSuey, and Freedom can come undervolted by certain degrees, it depends on which version of the kernel you download.
I can't think of any way to back up a kernel except for nandroiding system, but I am probably wrong. Just go into recovery, wipe cache and dalvik and flash a new kernel if you have any issues.
There is a good study guide in I think Q&A stickied, telling all that you need to know about kernels. I advise you to read it. Link: http://forum.xda-developers.com/showthread.php?t=894880

tropicalbrit said:
I can't think of any way to back up a kernel except for nandroiding system, but I am probably wrong. Just go into recovery, wipe cache and dalvik and flash a new kernel if you have any issues.
Click to expand...
Click to collapse
You can usually recover a bad kernel by flashing to back to the stock kernel and wiping cache and dalvik. Its usually worked for me, but depends on how much the custom kernel changed things.
To OP, go check out Kernel Manager in the market. It takes a good amount of the guesswork out of kernel flashing.

I say go with chopsuey 9.1 ill say its really good left my phone off charger for 8 hours while i slept was at 41% before and when i woke up it was still at 41% i mean does it get anybetter than that

Thanks for the help. Really in depth and helpful advice . Using freedom aggressive kernel now. Still testing to see if it helped. Great forums.
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock, came preinstalled) hardware v.4 bought new in July.

nscollab/cyanogenmod - the need of a stable 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

[Q] Random Reboots!

Hey guys,
I have the Lightspeed 1.0.7 ROM w/ Thor's 3.9R3 kernel installed. I have my tab overclocked to 1.5 Ghz and I'm noticing random reboots the 3rd day which is weird because i never had reboots the first 2 days.
I noticed it after I open the system tuner app. does this have anything to do with the kernel? Or app?
Thanks

I have the same issue with system tuner on Thor's 14.1 using the 3.9R3 kernel. Also
using SetCPU to undervolt so I thought they may be conflicting or its just a glitch in the app. It usually crashes even if I don't change anythind just leave it on the CPU tweaks tab. I think I remember it happening on Taboonay 2.2 but I forget which kernel I was using at the time.

Neutrino Rom cannot wake up after a long period of idle

I am currently at Neutrino rom V2.5p2 GT
my phone have some problem that it cannot wake up after a long period of idle, such as EVERYDAY I wake up in the morning but I cannot wake my phone up. I have to pull my battery off and back in to reboot the device. This problem made me fail to receive morning calls for a whole week.
I am using Juicedefender, but not sure if it is the cause of problem.
Since this is the first custom rom I flash and I love Neutrino, but I think stability is a must to me. Are the V2.5p2 EE or V2.2 having a better stability? should I try them? or any patch can fix this problem?
Thank you so much!

same as u with 2.5p2 ee
wait for the next build

Sleep of death as its known, not always rom specific many of us experience it on different roms under different loads under different situations.
There's a few of us trying to track down the underlying problem, but at the moment we are all trying out different things which some work for people and not others
so agreed with the above just wait for the next build maybe that will work for you.

Harrison85 said:
Sleep of death as its known, not always rom specific many of us experience it on different roms under different loads under different situations.
There's a few of us trying to track down the underlying problem, but at the moment we are all trying out different things which some work for people and not others
so agreed with the above just wait for the next build maybe that will work for you.
Click to expand...
Click to collapse
Like i've said in the Neutrino thread - it's a CM7 bug that was present in the original weekly.
Flash the 023 kernel, wipe dalvik, reboot.
023 seems to have fixed the problem for me. Going through a second day without random reboots, sleep of death.
Link to the kernel can be found in the faux dev thread, but it's also in my sig.

I think my phone must be hate custom ROMs because it have SOD for Jokersax and Turl CM9 as well as Neutrino ROM. Did flash some faux kernel but solve nothing. Still running Jokersax CM9 although SOD simply because of ICS. My own opinion, don't try CM9 unless you are ready to stay with it until official release.
Sent from my MB860 using XDA

ko_wei13 said:
I think my phone must be hate custom ROMs because it have SOD for Jokersax and Turl CM9 as well as Neutrino ROM. Did flash some faux kernel but solve nothing. Still running Jokersax CM9 although SOD simply because of ICS. My own opinion, don't try CM9 unless you are ready to stay with it until official release.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
What's your WIFI sleep policy set to?
And just to be 100% sure - do you wipe properly during rom flashing?

xploited said:
What's your WIFI sleep policy set to?
And just to be 100% sure - do you wipe properly during rom flashing?
Click to expand...
Click to collapse
I didn't enable wifi. Just using data plan. The setting for 'Keep Wi-Fi on during sleep' is Always as default.
I'm using N_01.100.00R baseband, could it be the issue? Any baseband recommend to use in Asia?
I follow what Jokersax said, format /system, wipe user data, wipe cache and dalvik cache in CWM. I manage to flash every single ROM and boot normally. Weird.
Sent from my MB860 using XDA

xploited said:
Like i've said in the Neutrino thread - it's a CM7 bug that was present in the original weekly.
Flash the 023 kernel, wipe dalvik, reboot.
023 seems to have fixed the problem for me. Going through a second day without random reboots, sleep of death.
Link to the kernel can be found in the faux dev thread, but it's also in my sig.
Click to expand...
Click to collapse
I am going to flash the 023 for a try. I just flash it in cwm recovery and that will be ok?

OK I have just flashed the 023 kernal, let me test my device for a few days to see whether SOD still exist, thanks!

ko_wei13 said:
I didn't enable wifi. Just using data plan. The setting for 'Keep Wi-Fi on during sleep' is Always as default.
Click to expand...
Click to collapse
I am using the default ATT baseband N_01.77.30P.
But from my experience, the reboot / sleep of death issue is most definitely related to WiFi.
Try setting Wifi sleep to "off when the screen is off" and switching to 023 kernel.
Haven't had any issues with this set up in the last 2 days.

xploited said:
I am using the default ATT baseband N_01.77.30P.
But from my experience, the reboot / sleep of death issue is most definitely related to WiFi.
Try setting Wifi sleep to "off when the screen is off" and switching to 023 kernel.
Haven't had any issues with this set up in the last 2 days.
Click to expand...
Click to collapse
Read from other thread with the workaround solution by installing Load Monitor or Wake Lock to prevent phone to go into deep sleep and fail to wake up. Now my phone run at 216Mhz instead of deep sleep when screen off. So far no SOD experience yet. But don't know how my battery life ink this case. Will update again after more observation.
[edit] no luck for load monitor. Get a SOD after 2 hours. Trying wake lock now. So far 6 hours no SOD. Will keep update.
Sent from my MB860 using XDA
Jokersax CM9 v0.4.1

I flashed the 023 1.3GHz kernal and the SOD disappeared last night!
I think the 023 1.0GHz kernal also work
I will observe for a few more days and report it here

Neutrino V2.6 GT and GT+ comes with 023 Kernel. It might solve the SOD as well. Downloaded. Will try it now..
Sent from my MB860 using XDA

ko_wei13 said:
Neutrino V2.6 GT and GT+ comes with 023 Kernel. It might solve the SOD as well. Downloaded. Will try it now..
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I think the problem is solved with the 023 kernal! 2 days after flashing with no problem even set the wifi to be always on.
I think V2.6 EE version is worth trying since it include the CM7 kernal and claimed to have amazing battery efficient! But the V2.6 version introduced Launcherpro and many changes so I am not going to change it at this point, maybe a few days later.

Can I just flash the V2.6 stock CM7 kernal on my V2.5p2?
where can I find that CM7 kernal???

stainlesteel said:
Can I just flash the V2.6 stock CM7 kernal on my V2.5p2?
where can I find that CM7 kernal???
Click to expand...
Click to collapse
Why would you want the 2.6 kernel on 2.5p2?
For me 023 fixed the SOD issues.
Anyway, if you want to try the 2.6 kernel, download the rom, extract boot.img from the archive and flash it via fastboot, wipe dalvik, reboot.
If i were you, I would switch to 2.6 entirely. Haven't had any SODs in the past 24 hours since flashing.

stainlesteel said:
I think the problem is solved with the 023 kernal! 2 days after flashing with no problem even set the wifi to be always on.
I think V2.6 EE version is worth trying since it include the CM7 kernal and claimed to have amazing battery efficient! But the V2.6 version introduced Launcherpro and many changes so I am not going to change it at this point, maybe a few days later.
Click to expand...
Click to collapse
Flashed V2.6 GT and no SOD so far, but Play Store keep FC. Now revert back to CM9 Jokersax v0.4.1 with wake lock to keep my CPU on when screen off. No SOD for 2 days, but battery only can stay around 10hrs.
Sent from my MB860 using XDA

Oh I found the kernal swaping thread and the problem is solved!

I got is every once in a while with neutrino 2.2

My neutrino 2.6 have a priblem in search and home buttons.