Database Info

[Q] Tiamat Kernel Question

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.

[Q] [Discussion] Kernels/UV Values

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...

[Q] Setcpu crashing at 1.9Ghz?

I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.

pranker98 said:
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
Click to expand...
Click to collapse
Sounds like you weren't aware that 1.7GHz and higher aren't considered stable freqs, 1.9GHz has a high Voltage which may cause the kernel to panic and issue a reboot. Just stick with a lower freq around the 1.2 stock speed.

pranker98 said:
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
Click to expand...
Click to collapse
Any CPU aren't the same. It seem that your CPU can't handle that much clock speed. Speed on 1.9 and 1.782 Ghz are quite the same. (Quadrant might shows couple hundreds higher but not effect any everyday uses.)

Ace42 said:
Sounds like you weren't aware that 1.7GHz and higher aren't considered stable freqs, 1.9GHz has a high Voltage which may cause the kernel to panic and issue a reboot. Just stick with a lower freq around the 1.2 stock speed.
Click to expand...
Click to collapse
Thanks for the heads up. Where'd you hear that? i dont remember reading about it. Is there a way to make 1.9ghz work?

What benefits will 1.9GHz provide other than wearing down your battery faster?

pranker98 said:
Thanks for the heads up. Where'd you hear that? i dont remember reading about it. Is there a way to make 1.9ghz work?
Click to expand...
Click to collapse
Just looking at that voltage table and my experiences with that freq from past phones tells me so . Jumping from the low level to such a high one should cause a freeze on any device.
@LooieEng 1.9GHz may help this phone run future Android revisions smoothly, and perhaps Win8 will function on the phone too.

Issues with AT&T RUU_Evita_UL_Cingular_US-1.82.502

Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.

gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2

gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Wowsers! That's good to know. I haven't updated yet as I'm on Rogers, but I'll keep that in mind when a Rogers version comes around.
As for the WiFi issue, I've had it the whole time. I went 9 days before rooting, and it's been maybe 15 days since I rooted. It existed pre- and post-root for me.

mobilehavoc said:
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Mine seems to be running at 1.5ghz fine. I'm on the new version. I smell FUD.
Sent from my HTC One X using Tapatalk 2

same as above, no issues here.

Also have the update no issues
Sent from my HTC One X using Tapatalk 2

I went from the full detox to 1.82 and after start up i ran both quadrant and antutu benchmarks. I noticed that quadrant score was only 4k when it used to be 4.5k. antutu was also lower and thats when I noticed the clock speed being listed at 1243 mhz (something around there). I downloaded the antutu cpu master free and it allowed me to move the slider back up to 1512 mhz.
Only sharing what I expierenced, now i'm trying to go back to 1.73 and having trouble...seems like it doesn't want me to move back down.

gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.

cloudraker said:
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.
Click to expand...
Click to collapse
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?

gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Im guessing that like the only other HTC phone ive owned, downgrading wont happen without s-off. So the only thing i can suggest is to instead try going back to 1.82 and get the phone functional so at least its not a brick and if its still showing an incorrect clock speed maybe you can get an exchange.

gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Yea you can't go back down.Have to wait for the official ota and see if its any different.

My phone runs much smoother with the new update...almost like a different phone. I could care less what the benchmarks say...I'm a real world guy.
Sent from my HTC One X using Tapatalk 2

I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.

1.73 here...
5,013 -- Quadrant Standard
So perhaps something is just wrong with you're phone. Also, I thought you couldn't modify your clock speed without unlocked bootloader + root/s-off or whatever. I know the basics, Just not the full technical explanation of it all. Sounds to me like you have a problem though from the beginning to have <5K of a quadrant score.
Just removed everything I dont need. De-oxed and removed bloatware + added a couple games. Cleared "multi-tasker" and used task manager [not the stock] widget to free up memory... Which made it go to 4,760. So doing all this stuff to "help" somewhat backfired. Im wondering if its the task manager widget/app always running :b Idk. Point is, I think its your phone. Even if i'm not at 1.8~.

gtung99 said:
I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.
Click to expand...
Click to collapse
good to know. and FYI, though it's not my forte, i was reading either the "Update 1.82" thread or the thread with the title named the same as the 1.82 patch (can't recall which one) and I remember someone mentioning that to roll back to 1.72 after upgrading, you need to edit a certain .apk file, which, if done improperly, will totally brick the device. glad you were able to get 1.82 to run properly. I've decided to wait for the full OTA from ATT since my wi-fi issues are generally minimal.

Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.

ThisWasATriumph said:
Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.
Click to expand...
Click to collapse
The IO score is lower now. Can't wait until Franco or someone else releases some kernels that will really make this phone rock. I had a galaxy nexus before with the stock rom but running Franco latest kernel that boosted the Quadrant score from 2200 to 3600. Mostly it was due to enhancements that dramaticlly increased memory and IO performance.

I installed the leaked update and my wifi still doesn't work right. It is extremely slow and crashes my entire network and brings it to its knees. Wifi will not work on a single device when my one x is connected to my wifi network. Ideas? Has anyone else experience this?

I hadn't thought of this being the cause but I have noticed that my wifi at home, specially when watching netflix is way slow. I always have my wifi on my HOX turned on when at home. I'm on 1.82 and running Clean ROM 2.3. Are you saying that this could be causing my slowness on all my devices that are also hooked into my wifi at home?

[Q] Processes Crash Like Doom...

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