Related
Has anyone been successfull? i have tried every OC kernel and as soon as i overclock it just reboots my phone to a freeze (only way out is to either pull the battery or adb reboot). That being said the UV kernel runs fine.
Not sure if it has to do with the I9020A series.
But overall, each NS phone can tolerate its own OC levels. Some phones can tolerate only up to 1.2 GHz, some may be able to achieve 1.4GHz (or beyond). And for some of the unfortunate, some aren't able to OC at all.
Thus this post. I hope my phone is'nt the issue. it would be nice to push a little bit more out of it if i needed it down the line.
I over clocked mine to 1.4 and it was fine, I leave it at 1.0 tho, this friggin thing is quick enough for now.
hmm how do you check your radio. I'm gonna try that as a last resort. And i can set mine as 1.4 but as soon as i run a resource heavy task (n64) my phone locks up and reboot freezes.
themapleboy said:
hmm how do you check your radio. I'm gonna try that as a last resort. And i can set mine as 1.4 but as soon as i run a resource heavy task (n64) my phone locks up and reboot freezes.
Click to expand...
Click to collapse
Not sure why a radio would affect your ability to OC but...
Menu -> Settings -> About Phone -> Baseband Version
the last 3 are what you want to look at "JK8/KB1/KB3"
List all the kernels you've tried. The best in my opinion is Netarchy's 1.3.0.3-CFS kernel using SetCPU
Try intervals of 1.2 GHz too. My phone can only go up to 1.2 GHz
Yeah actually i had tried all of the bfs kernels. I just succeeded in getting Netarchy's 1.3.0.3-CFS kernel. And i can run up to 1.4 . Maybe the brain fk scheduler does not play nice with 9020a's
themapleboy said:
Yeah actually i had tried all of the bfs kernels. I just succeeded in getting Netarchy's 1.3.0.3-CFS kernel. And i can run up to 1.4 . Maybe the brain fk scheduler does not play nice with 9020a's
Click to expand...
Click to collapse
awesome. I just prefer CFS because with BFS the boot animation doesn't show, and it bothers me.
zephiK said:
awesome. I just prefer CFS because with BFS the boot animation doesn't show, and it bothers me.
Click to expand...
Click to collapse
i flashed the BFS first, and lost my boot animation. Then i switched to the CFS, and the boot animation still didnt appear.
Any ideas as to how i can get it back?
Also, is there anyway to recover the stock kernel? I'd like to have it handy to be able to go back to it.
thnks
mixxy said:
i flashed the BFS first, and lost my boot animation. Then i switched to the CFS, and the boot animation still didnt appear.
Any ideas as to how i can get it back?
Also, is there anyway to recover the stock kernel? I'd like to have it handy to be able to go back to it.
thnks
Click to expand...
Click to collapse
Wipe dalvik and cache. Flash a rom that flashes stock. Like cm7 but netarchys is so much better than stock
You can also get ogdobbers which is stock + ext4 + voodoo.
Sent from my Nexus S using XDA Premium App
Hey everyone,
This is an off topic question but does anyone know what happened to the 1.6 OC support for Netarchy? I loved to see the absurdly high quadrant scores and instantaneous screen transitions.
Thanks,
Justin
JTECJ said:
Hey everyone,
This is an off topic question but does anyone know what happened to the 1.6 OC support for Netarchy? I loved to see the absurdly high quadrant scores and instantaneous screen transitions.
Thanks,
Justin
Click to expand...
Click to collapse
you're better off asking that in the netarchy kernel thread in dev forums.
netarchy could answer that... not a lot of phones can tolerate 1.6 GHz Oc
Thanks, yeah i felt a little bad posting the question here. Though ive been an avid user for a long time i have never posted so i didnt have sufficient rites to post in the decelopment section yet : (
Justin
Sent from my Nexus S using XDA Premium App
zephiK said:
Wipe dalvik and cache. Flash a rom that flashes stock. Like cm7 but netarchys is so much better than stock
You can also get ogdobbers which is stock + ext4 + voodoo.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
so cm7 flashes the stock kernel?
mixxy said:
so cm7 flashes the stock kernel?
Click to expand...
Click to collapse
yep! low on bugs and freezes but no voodoo or bln.. dammit
Setcpu FC's on me everytime i open it. Also at startup which option should i choose. There are a bunch of different phones (g2x not listed)
Not sure about the FC thing but you should choose the option that says something about Tegra 2.
G2X CM7
use recommended settings. and if your kernel doesnt oc you probably dont need to use setcpu.
No tegra 2. Theres [ARM] and [Custom frequencies] in running Faux's kernel
dligon said:
use recommended settings. and if your kernel doesnt oc you probably dont need to use setcpu.
Click to expand...
Click to collapse
You can still use it to setup profiles. I run a screen off profile to keep the processor speed down when the screen is off. Helps with battery life.
G2X CM7
When you FIRST run the app it asks you to select an option out of like 10 and they're all different proccesors. Which should i select. I selected custom and [ARM] and they both FC'd after i hit them
autodetect?
mmapcpro said:
autodetect?
Click to expand...
Click to collapse
There isnt an option for autodetect.
NEVERMIND! Thanks everyone i had an old version haha
Mister Hat said:
NEVERMIND! Thanks everyone i had an old version haha
Click to expand...
Click to collapse
Lol nice
G2X CM7
Wait but it wont let me overclock. Im on Faux's AOSP ROM with his kernel?
Mister Hat said:
Wait but it wont let me overclock. Im on Faux's AOSP ROM with his kernel?
Click to expand...
Click to collapse
Wow. I got a newer version but it wasn't the newest. Found the newest and selected auto detect. Thanks everyone for helping tho.
new with the nexus s (tmobile) so im being careful before flashing. im looking for a kernel that supports voodoo app controls so i can change the yellow stock tint screen. maybe get some overclocking in
Matrix works great for me
Netarchys universal all the way.
Sent from my Nexus S 4G
vabeachfc3s said:
new with the nexus s (tmobile) so im being careful before flashing. im looking for a kernel that supports voodoo app controls so i can change the yellow stock tint screen. maybe get some overclocking in
Click to expand...
Click to collapse
oh, and trinity does too. it supports voodoo and all the other nexus s goodies available. plus, its by far the fastest kernel(or most battery efficient, depending on which trinity kernel you chose).
simms22 said:
oh, and trinity does too. it supports voodoo and all the other nexus s goodies available. plus, its by far the fastest kernel(or most battery efficient, depending on which trinity kernel you chose).
Click to expand...
Click to collapse
hey buddy can u direct me to where u got your kernel? im on cm7.1.0 rc1 ns kang (2.3.5)
"Stable" Version: 1.3.7
2.3.4 based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.3.7-cfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
BFS BUILDS:
Netarchy Nexus - 1.3.7-bfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-bfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
whats the difference betweem CFS and BFS? is it ok to flash a 2.3.4 stable kernal on my rom thats 2.3.5?
please excuse the noobism. very familiar with the vibrant but picked up this nexus and learning right now.
vabeachfc3s said:
hey buddy can u direct me to where u got your kernel? im on cm7.1.0 rc1 ns kang (2.3.5)
"Stable" Version: 1.3.7
2.3.4 based roms (Nexus-S AND Sprint Nexus-S 4G Phones):
CFS BUILDS:
Netarchy Nexus - 1.3.7-cfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
BFS BUILDS:
Netarchy Nexus - 1.3.7-bfs-2.3.4 (For stock 2.3.4 roms)
Netarchy Nexus - 1.3.7-bfs-2.3.4-universal (Universal for non-stock 2.3.4 roms)
whats the difference betweem CFS and BFS? is it ok to flash a 2.3.4 stable kernal on my rom thats 2.3.5?
please excuse the noobism. very familiar with the vibrant but picked up this nexus and learning right now.
Click to expand...
Click to collapse
its ok to flash a 2.3.4 kernel onto 2.3.5, provided that your phone boots it. and if it doesnt, just flash another. heres where the trinity kernels are. they come in many flavors, from 1ghz and up. there is also a "teuv" kernel, trinity extra undervolted. its at 880mhz, and made for battery saving. dont let the 880mhz scare you, its faster than many 1.2ghz kernels and much more battery efficient http://forum.xda-developers.com/showpost.php?p=12931657&postcount=1
thanks for the help boss.
vabeachfc3s said:
thanks for the help boss.
Click to expand...
Click to collapse
anytime
So I read setcpu is not necessary with cm7 since it's already implemented with the rom. I'm just wondering why some people still use setcpu with it, are there any benefits?
I'm running latest version of cm7 with stock kernel.
*I'm also wondering what kernels you all use with cm7?
SetCPU has way more features than CM7's built-in CPU Governor.
With SetCPU, you're able to set custom CPU profiles to lower CPU Usage In-Call, when the screen is off, or when the battery hits a certain percentage... etc.
You're also able to control undervoltage in SetCPU (If you're using a custom kernel)
Thank you, so I can run them both simultaneously or is it possible to close the built in one?
kharnage said:
Thank you, so I can run them both simultaneously or is it possible to close the built in one?
Click to expand...
Click to collapse
I don't think it's possible to remove the CM7 Governor, but you can just use SetCPU with no problems at all.
Are you using CM7 as well? What kernel are you running it with?
kharnage said:
Thank you, so I can run them both simultaneously or is it possible to close the built in one?
Click to expand...
Click to collapse
Just disable the 'set on boot' setting in the CM7 settings and enable 'set on boot' in setCPU
kharnage said:
Are you using CM7 as well? What kernel are you running it with?
Click to expand...
Click to collapse
I realize you didn't ask me, but for reference, I'm running CM7 with faux's 0.4.2 kernel.
omarsalmin said:
Just disable the 'set on boot' setting in the CM7 settings and enable 'set on boot' in setCPU
I realize you didn't ask me, but for reference, I'm running CM7 with faux's 0.4.2 kernel.
Click to expand...
Click to collapse
Thank you, how's faux's kernel? is it faster than the stock and how's the battery life?
kharnage said:
Thank you, how's faux's kernel? is it faster than the stock and how's the battery life?
Click to expand...
Click to collapse
I'm running Nightly build 154 with Faux 0.4.2 with SV and DS battery driver...i get performance and great battery life. I use SETCpu and I've been OC'd @ 1.4 for about 3hrs now and my battery has only gone down 2% with mild texting and no overheating. My battery's temp has been constant at around 88-90 degrees.
If you're looking for the right Kernel...Faux's 0.4.2 with SV and DS battery driver is the way to go.
babymatteo said:
I'm running Nightly build 154 with Faux 0.4.2 with SV and DS battery driver...i get performance and great battery life. I use SETCpu and I've been OC'd @ 1.4 for about 3hrs now and my battery has only gone down 2% with mild texting and no overheating. My battery's temp has been constant at around 88-90 degrees.
If you're looking for the right Kernel...Faux's 0.4.2 with SV and DS battery driver is the way to go.
Click to expand...
Click to collapse
I wanted to use that but doesn't DS have the weird battery fluctuation? How is that? Is it manageable?
kharnage said:
I wanted to use that but doesn't DS have the weird battery fluctuation? How is that? Is it manageable?
Click to expand...
Click to collapse
It was weird at first...but i all i did was re-flash the kernel and fix permissions...and that solved the problem for me.
babymatteo said:
It was weird at first...but i all i did was re-flash the kernel and fix permissions...and that solved the problem for me.
Click to expand...
Click to collapse
What kind of permissions? So you don't have any weird battery readings at all anymore?
kharnage said:
What kind of permissions? So you don't have any weird battery readings at all anymore?
Click to expand...
Click to collapse
Fix permissions in CWM. Nothing weird...atleast nothing that i know of.
babymatteo said:
Fix permissions in CWM. Nothing weird...atleast nothing that i know of.
Click to expand...
Click to collapse
So technically all you did was reflash it? I just flashed the kernel and the battery is jumping from 41 to 44 to 47. Can you please tell me your exact steps :3
Wipe cache wipe dalvik flash kernel then go to advanced and fix permissions...enjoy
Sent from my LG-P999 using Tapatalk
Aw man I really wanted it to work but I tried your method and it just jump from 59 - 61
can someone post a link to the faux's OC kernel the CM one...the link in the original thread is dead...
Device: LG G2X
Rom: MIUI 1.11.11 (2.3.7)
Issue: Black Screen After Phone Call
Failed Fix Attempts: Turning Off Proximity Sensor, Reflashing Rom
Question: Does anyone know how to fix this issue? The only way to turn the phone back on after some calls is to pull the battery and turn the phone back on. It's starting to get a little frustrating. Any help is appreciated.
Azuske said:
Device: LG G2X
Rom: MIUI 1.11.11 (2.3.7)
Issue: Black Screen After Phone Call
Failed Fix Attempts: Turning Off Proximity Sensor, Reflashing Rom
Question: Does anyone know how to fix this issue? The only way to turn the phone back on after some calls is to pull the battery and turn the phone back on. It's starting to get a little frustrating. Any help is appreciated.
Click to expand...
Click to collapse
Its more a kernel issue than a rom issue.
If your using Trinity kernel than that would be I'm guessing the reason why. I always had the call SOD when using Trinity kernel new or old. Ive used different kernels to see if it would help and that fixes it for me. Currently am running eagle blood with faux's 4.3 kernel and that resolved my call SOD. I could be wrong in your case but for me it worked switching kernels.
Sent from my LG-P999 using XDA App
gman87 said:
Its more a kernel issue than a rom issue.
If your using Trinity kernel than that would be I'm guessing the reason why. I always had the call SOD when using Trinity kernel new or old. Ive used different kernels to see if it would help and that fixes it for me. Currently am running eagle blood with faux's 4.3 kernel and that resolved my call SOD. I could be wrong in your case but for me it worked switching kernels.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
That would explain it because I actually was using Trinity. Now I am using Dragon-G2X and its working perfect (so far). Thanks for your input.