badandy2021
Newbie
seconded
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Overclocking Ally
- Thread starter Sk1llsNYYRC09
- Start date
-
- Tags
- lg ally
seconded
gregskeels
Member
I'm useing the helix launcher at 768 and no probs yet I hope.
klumpingkalooper
Newbie
My SetCPU complained every startup that it had problems detecting so I used the setcpu.txt with the speeds you posted earlier. I also uploaded it here. Is it bad if I use the txt instead of auto detect? It shouldn't change anything, right?
badandy2021
Newbie
i am unaware of set cpu doing this. what it does do is display the temperature in fahrenheit and celsius, your processor minimum and maximum. thats it...
The way I read flick's response, I interpreted that the function he says is provided by the widget is the same as what you stated. In other words, unless I misinterpreted what flick said, you WERE aware that setcpu did what he described, because you just described the same thing.
----
Anyway... running the Ally at 768 last night I played some Home Run Battle 3D for 2 hours (I was really pretty bored after 45 minutes, but I pressed on anyway... cause I'm a warrior!
) then I checked my temps. The battery said 92.1F. I was pretty darn happy with that considering I had been running a graphically intense 3D game for a couple of hours. I then decided to surf the web on the Ally. After 20 minutes of surfing I checked the battery temps again, and I found the battery was now at 104F. I was quite surprised that using the Dolphin Browser for 20 minutes seemed to beat up on the phone more than Home Run Battle did, but I decided to throttle the cpu back to 748 and resume testing today.
It is possible that something else was taxing the cpu/battery in the background (although, I'm pretty good about killing background processes frequently) during the heat up I experienced while surfing the internet, and it may not have been a direct 1 to 1 correlation of Dolphin surfing being more stringent than home run bashing... still I was SUPER SURPRISED to find that 20 minutes reading text on a web page caused my battery to heat up 12 more degrees over what it experienced from the game.
This is one that I want to watch, so in addition to continuing my testing at 748 today, and comparing temps vs various speeds -- I will also be testing the temps when the phone is doing various duties... 2d gaming, 3d gaming, web surfing, taking and viewing pictures and video, texting, and calling... and more ideas if you guys have them.
Jace417 (who shoplifted my normal handle of JaceMan here???) out! Gee whiz, I feel like I just gave a report to the boss.
badandy2021
Newbie
Are you using wifi? I've found out that if you use anything while wifi is on, it tends to heat the phone up. Makes sense, since that's just one more piece of active hardware.
flick159
Well-Known Member
Has anyone experienced any force close issues? I was using a 748/320 rom last night. Went to bed and woke up today to find constant force close issues and horrible laggy-ness. Can't tell if it's related to the overclock, or the higher minimum speed. Anyone else have this issue?
ok, well my phone wouldn't hold stable at 787 all day. It would eventually lock up after a couple hours of operation and it wouldn't kernel panic unless i was running several apps at once. It was just freezing up, black screen, then reboot. So I kicked it down a notch to 768 and I haven't been able to lock it up or get a kernel panic! I haven't exceeded 94f on the battery after constant checking while doing various things. It has been unseasonably cool in SLC though, so that may have helped.
Velocity V0.1.1
768mh/z
92.7F
Stress test for 425sec, no errors.
I can't run Quadrant. Gets stuck at 11/12.
Boot is much faster.
Noticeable difference when playing RoboDefender.
Keep up the good work!
I would be interested in donating to your projects and testing any betas you might have. Keep me informed.
768mh/z
92.7F
Stress test for 425sec, no errors.
I can't run Quadrant. Gets stuck at 11/12.
Boot is much faster.
Noticeable difference when playing RoboDefender.
Keep up the good work!
I would be interested in donating to your projects and testing any betas you might have. Keep me informed.
esmith4211
Newbie
same here, except for the slc part.
jamesnmandy
Android Enthusiast
mine runs better on the stock rom vs. Velocity as well......but for whatever reason i cannot get it to boot into recovery anymore so im unable to try this new overclocking feature
i rooted the phone, installed rom manager, installed ClockworkMod Recovery successfully, backed up my stock rom, then flashed Velocity, which went fine
played with it a few days, slow to boot, slow doing everything, not happy, so i used ClockworkMod Recovery to flash back stock rom from backup, which went fine
phone is now much much better, however, no matter what i do now it refuses to boot into recovery mode, manual, or by choosing this overclocking kernel to "update" (i renamed the getitnowmarketing_oc_beta#1 to update and moved it to the root of the sd card) and then telling it to reboot into recovery and install the update
one time i got a blue screen that said something about Fastboot and hung up....so i did a battery pull, rebooted fine, so i said ok......start over
uninstalled Rom Manager, re-ran Androot for good measure, rebooted in between, went back to market, re-installed Rom Manager, re-installed ClockworkMod Recovery, this time it actually rebooted into recovery mode once time to "backup current rom"
since then, it will not reboot into recovery mode for anything in order to flash this custom rom....whether i do it manually or as part of telling it to load this "update" directory.......all it does is reboot and show an exclamation mark triangle symbol with the android and then boots normally......and now i am getting random graphical glitches......
im stuck
jamesnmandy
Android Enthusiast
ok got mine to work, here's what i did
i performed the flash of ClockworkMod Recovery again from within Rom Manager. then chose the manual boot into recovery option, got the green recovery screen, chose "apply update.zip from sd card" (i think is what it said), next screen had a bunch of no no no no no and then a yes, apply update.zip, which is what i chose, there was a real fast few seconds where it said it wrote the files successfully, then it rebooted
then i went to the market and bought SetCPU for $2, rebooted.
used the setcpu.txt file from this thread and saved it to sd card root, because autodetect wasnt working right...kept saying maximum should be 19Mhz and minimum 245Mhz.....not sure whats up with that...but the setcpu.txt file in root of sd card fixed that (see klumpingkalooper's post on page 3 of this thread)
set to 729max and 245min, set to ondemand, checked set on boot, rebooted
for several reboots it would keep everything else i changed as i set it except for some reason the first several reboots it kept choosing the performance profile on its own...i just kept changing it to on demand and making sure it was set to 729/245 and checked set at boot and finally now it stays set that way every time.....finally
jamesnmandy
Android Enthusiast
went to add setCPU widget to the home screen, got kernel panic, rebooted, went to setCPU app, profile reverted back to performance.......wtf...
happened again
seems that any time i have a kernel panic it defaults to performance again and , but if i reboot manually it keeps the settings i set....
happened again
seems that any time i have a kernel panic it defaults to performance again and , but if i reboot manually it keeps the settings i set....
I reflashed Clockwork a few more times and did the reboot into recovery from ROM Manager and it seems to have worked. Sweetness.
I guess what they say about perseverance is true.
getitnowmarketing
Android Enthusiast
Couple things this zip is a kernel only not a rom. You have to reapply setcpu stuff after every reboot. There is nothing in this kernel to cause recovery issues and if you are having issues with clockwork why dont you just use mine after all.
Oh and worth noting on setcpu the user that had the 19mhz max on setcpu if that happens just move the sliders up to raise the max.
The stock rom has a file named install-recovery.sh that rewrites your stock recovery to it after a reboot. Thats probably why you lost your custom recovery. Instructions on disabling it in my recovery thread. Also, renaming the flashable oveeclocking beta to update.zip wasn't needed for acustom recovery. You had the stock recovery and you can only do OTA updates signed by LG with it.
Oh and worth noting on setcpu the user that had the 19mhz max on setcpu if that happens just move the sliders up to raise the max.
jamesnmandy said:
The stock rom has a file named install-recovery.sh that rewrites your stock recovery to it after a reboot. Thats probably why you lost your custom recovery. Instructions on disabling it in my recovery thread. Also, renaming the flashable oveeclocking beta to update.zip wasn't needed for acustom recovery. You had the stock recovery and you can only do OTA updates signed by LG with it.
jamesnmandy
Android Enthusiast
so after getting everything ironed out, phone running fine, set to on-demand and only 729Mhz max and 245Mhz min....sitting charging not using it it works fine for an hour
go to leave for the evening, make a phone call on it, screen turns off when raised to head while making call like normal, get done with call, bring down in front of me, go to hit END button on screen, no screen, hit buttons, nothing, slide open and shut, brings back screen, hit end, call ends, then phone goes into kernel panic reboot
so im like ok, my phone wont overclock, so i go to remove it...go into setCPU, max has set itself back to 600MHz max and performance profile, so i uninstall, as soon as i hit ok to uninstall it goes into reboot automatically again.....
so then as soon as it comes back i go into ClockworkMod Recovery to flash the backup i made right before doing this kernel update....
it takes me four tries before i finally got it, my phone was rebooting itself within 20 seconds of booting up, like pretty much as soon as the phone becomes responsive to screen touches, it is laggy and reboots....so i keep trying and i think on the 4th try i finally got into the Recovery and told it to reboot and load last backup
finally......
and now it is fine.....
this is waaaaayyyy....tooo early to be flashing to devices bro....this is early alpha shit man....
go to leave for the evening, make a phone call on it, screen turns off when raised to head while making call like normal, get done with call, bring down in front of me, go to hit END button on screen, no screen, hit buttons, nothing, slide open and shut, brings back screen, hit end, call ends, then phone goes into kernel panic reboot
so im like ok, my phone wont overclock, so i go to remove it...go into setCPU, max has set itself back to 600MHz max and performance profile, so i uninstall, as soon as i hit ok to uninstall it goes into reboot automatically again.....
so then as soon as it comes back i go into ClockworkMod Recovery to flash the backup i made right before doing this kernel update....
it takes me four tries before i finally got it, my phone was rebooting itself within 20 seconds of booting up, like pretty much as soon as the phone becomes responsive to screen touches, it is laggy and reboots....so i keep trying and i think on the 4th try i finally got into the Recovery and told it to reboot and load last backup
finally......
and now it is fine.....
this is waaaaayyyy....tooo early to be flashing to devices bro....this is early alpha shit man....
flick159
Well-Known Member
He did say this was for testing. Sounds to me like your device just can't handle that level of over clocking. Many users have reported good results here, I've got a stable 748/245 rom that's been running doing heavy usage for 3 days now without issues.
Have you tried lower clock speeds? Did you flash this as an update or build a rom using this kernel (method I used, using the android kitchen). Don't be so quick to anger, this is after the bleeding edge of this phones development, nothing is guaranteed.
getitnowmarketing
Android Enthusiast
Looks like his processor barely passed QA and is the first one reported that cant overclock.
jamesnmandy
Android Enthusiast
maybe thats why it rebooted a couple times playing Antigen just a few days after i got it....that was long before i was even thinking about flashing roms and overclocking....maybe i should file a warranty replacement claim with LG?