It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
cdljl2005 said:
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
Click to expand...
Click to collapse
Matr1x is undervolted. Run the kernel that comes with CyberGR or AOKPCB instead of flashing it.
It's fine that your friend Nexus S runs it, but you're not like your friend, are you? Well your Nexus S isn't like your friend Nexus S either.
cdljl2005 said:
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
Click to expand...
Click to collapse
Same thing happens to me, had to gave up Matr1x kernel because of that, despite i enjoyed it so much.
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
mathkid95 said:
Yeah that's not a kernel issue. Sorry to ruin your day
If you want, though, try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I had voltages raised +30 across the board. It wasn't a issue with booting or nothing like that, just out of the blue all apps would crash for no reason. Rebooting wouldn't fix it, fix permissions wouldn't fix it, only way to fix it was to reflash and kernel. And it only happened with your kernel in 5 or 6 builds of AOKP, any other kernel would not give that issue, but i enjoyed Matr1x the most.
I will try v21 and if the issue happens again i'll try to capture a logcat and forward it to you.
No I understand you're not bashing my work... forgive my rudeness
Yes, try to flash v21.0 and then if that doesn't work I will look into it
Sent from my Nexus S using XDA
polobunny said:
Matr1x is undervolted. Run the kernel that comes with CyberGR or AOKPCB instead of flashing it.
It's fine that your friend Nexus S runs it, but you're not like your friend, are you? Well your Nexus S isn't like your friend Nexus S either.
Click to expand...
Click to collapse
Thanks for replying. I raised voltage long ago, the problem happens... and now I left the voltage alone as its default, the problem still happens...
as for anything different using the kernel is that I'm using BLX, setting charging limit to 80%. dunno if that would lead to the problem.
DeuXGod said:
I had voltages raised +30 across the board. It wasn't a issue with booting or nothing like that, just out of the blue all apps would crash for no reason. Rebooting wouldn't fix it, fix permissions wouldn't fix it, only way to fix it was to reflash and kernel. And it only happened with your kernel in 5 or 6 builds of AOKP, any other kernel would not give that issue, but i enjoyed Matr1x the most.
I will try v21 and if the issue happens again i'll try to capture a logcat and forward it to you.
Click to expand...
Click to collapse
Yeah my problems are exactly the same! Moreover, I noticed that the crashing processes are more or less system, or requesting root, typically android.process.acore (that's Contacts I suppose?), Google maps, and third party apps like System Tuner, Rom Manager, etc.
As for whether it is a problem with the kernel, I'm not quite sure - I had changed ROM and kernel at the same time before undergoing the problem. And it's really strange of the stability in the first few days - if it is a undervolt problem, it should be happening from the beginning, shouldn't it? Or the problem may not be caused DIRECTLY by undervolt.
but I don't reflash to solve it... nandroid backup and restore will do.
and thanks for your reply DeuXGod! I thought it was only me who get this problem.
mathkid95 said:
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Will definitely try 21.0! Raising voltage doesn't seem to help, as one month ago I was using the kernel with raised voltage... the problem happened all the same.
If there's anything different in using the phone to my fellas using theirs, it's that I use BLX limiting charging up to 80%... don't know if it can cause the problem.
Anyway, I'll flash 21.0 first; if it doesn't help, I personally think one restore in each 3~5 days is also acceptable. Thanks mathkid! I'll be on matr1x.
p.s. more details about the problem are in the reply above... just FYI, hope it can help.
cdljl2005 said:
Thanks for replying. I raised voltage long ago, the problem happens... and now I left the voltage alone as its default, the problem still happens...
as for anything different using the kernel is that I'm using BLX, setting charging limit to 80%. dunno if that would lead to the problem.
Yeah my problems are exactly the same! Moreover, I noticed that the crashing processes are more or less system, or requesting root, typically android.process.acore (that's Contacts I suppose?), Google maps, and third party apps like System Tuner, Rom Manager, etc.
As for whether it is a problem with the kernel, I'm not quite sure - I had changed ROM and kernel at the same time before undergoing the problem. And it's really strange of the stability in the first few days - if it is a undervolt problem, it should be happening from the beginning, shouldn't it? Or the problem may not be caused DIRECTLY by undervolt.
but I don't reflash to solve it... nandroid backup and restore will do.
and thanks for your reply DeuXGod! I thought it was only me who get this problem.
Will definitely try 21.0! Raising voltage doesn't seem to help, as one month ago I was using the kernel with raised voltage... the problem happened all the same.
If there's anything different in using the phone to my fellas using theirs, it's that I use BLX limiting charging up to 80%... don't know if it can cause the problem.
Anyway, I'll flash 21.0 first; if it doesn't help, I personally think one restore in each 3~5 days is also acceptable. Thanks mathkid! I'll be on matr1x.
p.s. more details about the problem are in the reply above... just FYI, hope it can help.
Click to expand...
Click to collapse
Return to STOCK voltages. Stock volts aren't just 25mV across the board. This will likely sort out your issue. Have a search in the NS forums, i don't have a handy list on me.
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Harbb said:
Return to STOCK voltages. Stock volts aren't just 25mV across the board. This will likely sort out your issue. Have a search in the NS forums, i don't have a handy list on me.
Click to expand...
Click to collapse
I've experienced the problem under both stock & +2mV voltage ;P
I have no developing experience though, I don't quite believe it's caused by uv.
thanks for suggestion and your search anyway, you guys are really kind!
polobunny said:
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Click to expand...
Click to collapse
thanks! As I've already flashed Matr1x V21.0 before reading your post, I'm gonna give the new version a try - let's see how it will do!
In the next few days I should be flashing AOKPCB R2.1, if issue continues I would definitely do what you have posted.
Thanks again!
polobunny said:
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Click to expand...
Click to collapse
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
edit: thanks to polobunny for correcting me
Harbb said:
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 900mV
200MHz 950mV
400MHz 1000mV
800MHz 1050mV
1000MHz 1100mV
Click to expand...
Click to collapse
You are right, but those aren't the stock INT voltages.
However, those are:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
Cheers!
Ah, stupid mistake there. Thanks polo, clearly my mind was elsewhere.
mathkid95 said:
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Matter continues in V21.0 pal...
Harbb said:
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
edit: thanks to polobunny for correcting me
Click to expand...
Click to collapse
polobunny said:
You are right, but those aren't the stock INT voltages.
However, those are:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
Cheers!
Click to expand...
Click to collapse
Ah I just found that I forgot to say thanks to you guys...
Sorry for my absent of mind! And a lot of thanks!
mathkid95 said:
No I understand you're not bashing my work... forgive my rudeness
Yes, try to flash v21.0 and then if that doesn't work I will look into it
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
flashed V22 & raised voltage, still no use.
pm'ed you more details yesterday or earlier.
please tell me if logcat is needed.
cheers!
It Could Be Just A Hardware Issue ,I Had The Same Thing Happen With My Epic
MichaelCampos said:
It Could Be Just A Hardware Issue ,I Had The Same Thing Happen With My Epic
Click to expand...
Click to collapse
well this happens only when I'm on Matr1x kernel.... a great work it is though...
Same thing happens to me with Matr1x kernels, regardless of the rom (CM9 Kang, AOKP, or Kangyultra).
Everything returns to normal if I reflash just the kernel. Seems like a directory or file gets corrupted after a period of time.
Sent from my Nexus S 4G using Tapatalk 2
Related
I have been looking for a couple of days, and I can't seem to find my answer anywhere. Sorry if this question has already been asked. Does the Tiamat Kernel come overclock already, or do you need to use an app like SetCPU?
SetCPU is needed
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
anovinger said:
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
Click to expand...
Click to collapse
If you do not run an overclock program, the stock max is still on the CPU.
Sent from my Xoom
Do you know what the set Max is on the tiamat kernel?
anovinger said:
Do you know what the set Max is on the tiamat kernel?
Click to expand...
Click to collapse
1ghz
Sent from my Xoom
bwcorvus said:
1ghz
Sent from my Xoom
Click to expand...
Click to collapse
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Bandit504 said:
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Click to expand...
Click to collapse
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
bwcorvus said:
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
Click to expand...
Click to collapse
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Bandit504 said:
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Click to expand...
Click to collapse
Yea setcpu is not 100% yet. Does your widget show both cpus? What we were testing was the second CPU. After you xoom goes to sleep, the second CPU is never set again by setcpu (known bug). So lets say you are running 1.0/1.5. After you xoom goes to sleep you will wake up with cpu 0 at a max of 1.5, but cpu 1 will have a max of 1.0. The info i gave earlier was said wrong. I was actually looking at the wrong line, so you may in fact be correct on the 1.5ghz random jump . Gonna stop talking now, as we are hyjacking someone else's thread .
In theory, you should not need overclocking software, as the max is set at 1ghz on both cpus. But as said above by Bandit504, this may NOT be the case .
Thanks bwcorvus and Bandit504 . So I guess to call it is safe, it would be good idea to use SetCPU, or Droid Overclock and have the maximum set to 1 ghz, to keep the proc from hitting the 1.5 ghz speed. I just hate to ruin the hardware with the overclock, and have to drop another $600 for another xoom.
hello, I just wanted to make this thread for everyone to share their lowest AND stable voltage values for each frequency. Here goes mine:
(anything above 1000mhz was not tested)
1000mhz <-- 950mV
800mhz <-- 825mV
500mhz <-- 550mV
300mhz <-- 500mV
The following was done with eb1.0.4 + trinity kernel.
please share yours.
Copied from the kernel thread...
Bionix 2 at 1.2Ghz using deadline scheduler.
I attached my PMCpu settings in case anyone needs a reference.
Stressed tested for 15 mins stable.
Quadrant at 3337, Linpack around 45.
Click to expand...
Click to collapse
I started by doing -50 on all from 1200 oc...ill test for a whole day and drop it down -25 tomorrow and test for a whole day. And please post scheduler also.
So far @-50 on deadline scheduler all is working well, no freezes.
G2X
And how is battery life for everyone?
I can't belive how efin good mine has been, bt on, wifi on for 2 hrs, on xda forums every 30 minutes unplugged at 4:30a at 1:00p still had 55% left, whereas stock kernel would be at 15-10%...
G2X
GideonX said:
Copied from the kernel thread...
Click to expand...
Click to collapse
Using your settings running very smoothh!
Sent from my LG-P999 using XDA Premium App
fcisco13 said:
I started by doing -50 on all from 1200 oc...ill test for a whole day and drop it down -25 tomorrow and test for a whole day. And please post scheduler also.
So far @-50 on deadline scheduler all is working well, no freezes.
G2X
Click to expand...
Click to collapse
I have no idea what schedulers are
Also, a question to everyone, what are some of your unstable symptoms from UV? Since I've never had any rebooting issues with my g2x, I am not sure if some of the symptoms I was experiencing is from UV'ing or from the kernel. If you gone under the UV limit, does your phone just freeze or would it autoreboot?
c19932 said:
I have no idea what schedulers are
Also, a question to everyone, what are some of your unstable symptoms from UV? Since I've never had any rebooting issues with my g2x, I am not sure if some of the symptoms I was experiencing is from UV'ing or from the kernel. If you gone under the UV limit, does your phone just freeze or would it autoreboot?
Click to expand...
Click to collapse
UV will more than likely freeze or you will reboot... UV typically just makes everything really unstable, you might get stuck in a bootloop and have to reflash
JHaste said:
UV will more than likely freeze or you will reboot... UV typically just makes everything really unstable, you might get stuck in a bootloop and have to reflash
Click to expand...
Click to collapse
oh and a precaution to those using eb1.0.4 + trinity kernel. I set my max voltage for 1000mhz (my max. frequency as well) too low, and the phone autoreboot on startup twice and then did a factory reset itself This happened twice so be aware
GideonX said:
Copied from the kernel thread...
Click to expand...
Click to collapse
I'm running this settings and so far really good.
Thanks man!
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App
fcisco13 said:
I can't belive how efin good mine has been, bt on, wifi on for 2 hrs, on xda forums every 30 minutes unplugged at 4:30a at 1:00p still had 55% left, whereas stock kernel would be at 15-10%...
G2X
Click to expand...
Click to collapse
What ROM and Kernel are you using? Also, which EB can be used with the Trinity kernel? GB or FroYo?
Anyone find that their battery has actually gone down while UV'ing? I'm finding after a full charge, the first 30% has been quicker by almost an hour. Not a really scientific method of testing, but I do just about the same thing every morning (email, txt, etc.) left over from the night before. That first 30% has a lot of screen off time, which will lower the speed to 300Mhz using PMCpu.
I'm going to up the voltage to at least 700 for 300Mhz and see how that fairs.
hah2110 said:
What ROM and Kernel are you using? Also, which EB can be used with the Trinity kernel? GB or FroYo?
Click to expand...
Click to collapse
--EB 1.0.4 FROYO (gutted removed live wallpapers, wifi calling, tmo stuff)
--Trinity 15 EB1.04 FROYO
[email protected] pimp my cpu (free on xda)
--Went down -50volts on all speeds
Battery is unbelievable..
G2X
I just restored my EB 1.02. I'm going to flash trinity kernel and report back after one day of use.
Sent from my LG-P999 using XDA App
I've heard several people had lockups and phone factory reset when uv too low, i think going more than -50 is really risking it...
G2X
fcisco13 said:
--EB 1.0.4 FROYO (gutted removed live wallpapers, wifi calling, tmo stuff)
--Trinity 15 EB1.04 FROYO
[email protected] pimp my cpu (free on xda)
--Went down -50volts on all speeds
Battery is unbelievable..
G2X
Click to expand...
Click to collapse
Can Trinity be used with EB Gingerbread?
hah2110 said:
Can Trinity be used with EB Gingerbread?
Click to expand...
Click to collapse
There are specific kernel for gb, look for one that is for EB1.04GB
G2X
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
EDIT:
So I was asked what kernel I'm using... I will post my ROM + KErnel! and just to let you know, my G2x has never had any problems so that may be way my G2x can get -200 on 500 and 400
And I am using faux's CM7 Kernel Version 0.2.4
Full name:
"2.6.32.41-CM7-Faux123-v0.2.4
Mod version
CyanogenMod-EagleBlood_v1.2
Im new to setcpu, good thread for me to learn a bit more from other users...
Sent from my LG-P999 using XDA App
Yes I'm trying to decide on SetCPU or PimpMyCPU so any info is appreciated
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
What kernal are you using?
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
How are you not getting reboot problems with 400 at -200mv? I'm using faux's froyo kernel and when I undervolt at -100mv i get rebooting problems
I replied to your comment in my main post, since other people may be interested in that and that will cause them not to scan the pages.
Bump :\ I would like input
so how is your battery life?
Bad. Something about those settings messed it up. I much prefer just using the custom rom default kernel its much better on the battery
Sent from my LG-P999 using XDA Premium App
My chip could only use faux's OC 1.2ghz, using the kernel OC 1.5 would cause my phone to boot loop. I could go stable @ faux OC 1.2 with minimum UV, getting qudrant score of atleast 3000 - 3500. Another kernel that i tried is MOrfic's, I can go stable up to 1.4 Ghz/minimum UV- quadrant of atleast 4000-4300. I believe i have what they say as the "weak chip" though running OC @ 1.4 ghz doesn't make it look weak. Thanks to the great DevS!
So,
We've all got our Xooms, what are you experiences with each kernel, which one do you find the best? (and with what governors?)
Secondly, What are your UV values? Whats the best you've got when trying to undervolt?
Ive just got my Xoom (32gb, wifi, uk) and im just on the brink of experimenting with the undervolting, i searched but couldn't find a relevent topic.
So please, do post values, kernels and your experiences
ah okay, I thought this would be quite an important issue,
I've managed to get the xoom to handle 1.6 undervolting each state by 100mv
I am however having trouble getting both cores to stabilse at 1.6. Using os monitor I can see that only one core sticks, the other goes down to 300 mhz,.
tremblingwater said:
So,
We've all got our Xooms, what are you experiences with each kernel, which one do you find the best? (and with what governors?)
Secondly, What are your UV values? Whats the best you've got when trying to undervolt?
Ive just got my Xoom (32gb, wifi, uk) and im just on the brink of experimenting with the undervolting, i searched but couldn't find a relevent topic.
So please, do post values, kernels and your experiences
Click to expand...
Click to collapse
I haven't fooled around with over/undervolting, but I like the oc gpu version of the Tachi kernel.
Zero problems and very smooth. I am very stable at 1504MGh
okantomi said:
I haven't fooled around with over/undervolting, but I like the oc gpu version of the Tachi kernel.
Zero problems and very smooth. I am very stable at 1504MGh
Click to expand...
Click to collapse
what you using for OC?
Setcpu or pimp my cpu or anything else.
Which governor you use?
I had lots of rebooting with setcpu especially after applying voltages.
rohit3192 said:
what you using for OC?
Setcpu or pimp my cpu or anything else.
Which governor you use?
I had lots of rebooting with setcpu especially after applying voltages.
Click to expand...
Click to collapse
I use CPU Master for oc and setting profiles. I do have the oc set on boot, because 1504 is my sweetspot and is stable.
Just installed Moray+tachi
Mobo player freezed few times,rest ok.
Edit: Trying "No frills" discarded Set Cpu for now.
rohit3192 said:
Just installed Moray+tachi
Mobo player freezed few times,rest ok.
Edit: Trying "No frills" discarded Set Cpu for now.
Click to expand...
Click to collapse
No Frills is good, but I don't know if you can set profiles, which are good to save battery, control overheating, etc...
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...