Overclocking quirks.....holding menu seems to work - Hero CDMA Q&A, Help & Troubleshooting

My hero is one of the OC sensitive ones. I was running Aloysius 2.1 with overclock widget running at 710 no problem. I then wanted to change it up so I went to RegawMOD's themed ROM (love it!). So then I decided to add the new OC widget (the one for Honeybun works on this ROM) and it boot looped 3 times. The 4th time out of frustration I just held the menu key down until after about 20 seconds I get the Regaw boot screen and she fires right up. My Benchmark PI scores confirm it is indeed running OC now (went from 14500ish to 9800). I turned it off and back on and repeated the above process again, booted right up. Why does holding menu make it boot? I have had that happen when I tried to run Darchdroid 2.7 ROM but it only did it once, from then on it wouldn't boot ever again

Related

[Q] Cannot receive incoming calls

Sprint HTC Hero
DarchDroid v2.8
Recovery: RA-Darchstar (v1.7... I think)
PRL: 60667
I bought this phone last week, rooted it, and attempted three or four different ROMs before settling on DarchDroid (which is awesome, by the way!). I was initially having issues with multiple FCs and it eventually became unusable until I read up that my device might not be able to handle the OC to 710mhz. I installed the OC widget and throttled it down and now it works like a champ and is still WAY faster than the stock 2.1 ROM. I am still having issues though, that hopefully, somebody can help me with or point me in the right direction. I've spent the last hour scouring almost all parts of the forum and can't find any answers to these issues. Forgive me if I looked them over...
1) All incoming calls go directly to VM. I can make calls and send / receive texts, but no incoming voice calls.
The next one is a two-parter...
2a) The phone will occasionally become so sluggish (borderline non-operational) that I need to reboot it. When I do, I clear the cache and it will reboot then function normally. Could this be a result of a widget that I have installed? (OC widget, battery monitor?)
2b) When I reboot the phone without booting into recovery (normal reboot) it goes into a continuous boot loop. When I try to restore my Nandroid, it still boot loops and I have to wipe and re-flash the ROM. Is this normal?
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
I had the same issue with the latest Fresh Rom so I ended up switching to Zen Hero and have never had a FC on an incoming call since. I tried all the fixes for Fresh and never had any luck. I would suggest trying another rom.
p.s. I was able to OC the rom also and it still works fine.
chromiumleaf said:
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
Click to expand...
Click to collapse
Thanks for the advice. I ended up biting the bullet and calling Sprint and it turns out all that was needed was a refresh on my account, the phone works like a champ now! I'm using the OC widget and throttled it down to 595mhz, and even OC'd that little bit, it still BLAZES when compared to the Pre that I came from. No hitches or waiting - when I open a program or app, IT ACTUALLY OPENS QUICKLY... an amazing concept!
One more question though: in case I need to reboot, is there a way to save all of my phone settings? I already moved all of my apps to the SD card so I don't have to download them again, but it would be really helpful if I could just load a save file that would re-set my settings to the way I had them before. Is there an app or setting in the ROM for that?
Make a nandroid backup through recovery. It saves every little detail of your phone and if you ever need to go back to that you can simply restore that backup. Titanium Backup is another popular tool but I've never used it myself so I don't know anything about it.

[Q] Random Reboots

I'm running the current Extremely Blue CM6 version of Froyo. It runs great most of the time but it will randomly reboot occasionally. It did it this morning on the way to work. The only thing it was doing at the time was streaming bluetooth music to the car system. I've had it reboot in the middle of the night where all it's doing is charging and just randomly when it's not doing anything. I don't recall it ever doing it when I was actually using it though.
I'm not running any memory killer apps or custom kernal. Just the stock CM6.
Anyone have any suggestions as to what this could be? Or maybe how I can find out why it rebooted to begin with?
Thanks
I'm running the Ext Blue Nov 21 and I've experienced that as well. I read that flashing the decadence 691 kernal may fix it. It's only happened to me once. I'm not too sure what causes it, but it may be the processor being oc'ed too much. I've found that running mine above 691 makes it more prone to these reboots.
gorbisloth said:
I'm running the current Extremely Blue CM6 version of Froyo. It runs great most of the time but it will randomly reboot occasionally. It did it this morning on the way to work. The only thing it was doing at the time was streaming bluetooth music to the car system. I've had it reboot in the middle of the night where all it's doing is charging and just randomly when it's not doing anything. I don't recall it ever doing it when I was actually using it though.
I'm not running any memory killer apps or custom kernal. Just the stock CM6.
Anyone have any suggestions as to what this could be? Or maybe how I can find out why it rebooted to begin with?
Thanks
Click to expand...
Click to collapse
lol mine sometimes reboots while booting up the phone so it gotta wait 2X longer to boot the phone but its not much of a pain to me
I've had 2-3 reboots. I have Auto Killer & ATK, but even with just Auto Killer or maybe without it, iHeartRadio eventually = random reboot.
Flash the #43 691 cfs kernel over on deca's kernel thread. That should take care of reboots. If you are running a 768 already, turn it down to 710.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
LiquidSense 2.1
I am also getting random reboots constantly, probably 5 or 6 a day I am running LiquidSense 2.1 which is based on the NFX Sprint 2.31.651.7 STOCK Odex with Zen's AnyKernel with no Perflock (Set to 691 by default) but it also did it when i had NFX-Sprint.STOCK.2.32.651.2.ODEX.A2SD loaded as well. I have tried a full wipe and reformat of my SD card, as well as upgraded the sd ext partition to ext3 but no luck still reboots, any ideas?
jfarlik said:
I am also getting random reboots constantly, probably 5 or 6 a day I am running LiquidSense 2.1 which is based on the NFX Sprint 2.31.651.7 STOCK Odex with Zen's AnyKernel with no Perflock (Set to 691 by default) but it also did it when i had NFX-Sprint.STOCK.2.32.651.2.ODEX.A2SD loaded as well. I have tried a full wipe and reformat of my SD card, as well as upgraded the sd ext partition to ext3 but no luck still reboots, any ideas?
Click to expand...
Click to collapse
from my experience, the random reboots are almost always related to having an
overclocked CPU. Some phones seem to run fine cranked all the way up to 768,
my phone randomly reboots on anything past 691. If I run one of Deca's 691
kernels, I almost never get an unexpected reboot. (I think I've experienced one
unexplained reboot in the past two months). You can use somethign like
CPUSpeed or the overclock widget to control your CPU's speed, and crank it
down some, to see if that helps, or just flash a kernel that's capped at around 691.
I'm currently running LiquidSense 2.2.1 (Based on NFX Sprint.STOCK.2.32.651.2.ODEX.A2SD),
with one of the kernel's from the NFX thread, (Post by FdxRider)
691.perf.unlock.new.2.31.651.7_signed.zip,
Dalvik moved to the /cache partition, /swap enabled and in use, and am getting
good performance, phone runs nice and stable. Your mileage may vary, but I have
had zero issues running this kernel, and have used this kernel with
the NFX stock, and the sprint stock (unmodified) 651.2 roms with the same
results..

[Q] Issues with Screen Spazzing?

Has anyone had any problems with the screen doing its own thing? My nook is rooted using autonooter (1.0.0 eclair) but lately it has been doing things without me touching the screen at all. For example, one time i was in the (Dolphin HD?) browser and I went to go type something and it kept pressing the "O" on the keyboard until I exited the browser. Also, I have prolauncher installed for the home screen and it also spazzed out by switching back and forth between showing the thumbnails of the homescreen and back to the single homescreen view.
(Mine started to do this on 900mhz "screamer" kernel and also on the new 1ghz kernel thats based on that other omap processor (cannot remember right now)
This doesn't seem to be only happening to me. My roommate just bought one too and he said he was reading a book on his and it scrolled through 20 pages on its own. His is also autonootered on 1.0.0. His nook is on stock kernel.
Stumbled upon this thread, recently:
http://bookclubs.barnesandnoble.com...ok-Color-Touchscreen-Freaking-Out/td-p/731993

[Q] Weird OC/UV Kernel Issue...

Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
HTCOmega said:
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
Click to expand...
Click to collapse
Kernel flashing doesn't always go smoothly. Repeated kernel flashing without complete system wipes in between can cause some things to start going horribly wrong.
Don't use SetCPU to set clockspeeds. Just stick with voltage control.
If you forgot to disable any lagfixes at any point along the way, that could explain alot of the problem.
Suckerpunch kernel is a great concept and is showing alot of promise, but I personally have had alot of stability issues while using it, including random freezes (YMMV, of couse).
Just my opinion, but I would just back up all your data, flash back to stock, master clear, wipe all your cache data, reflash your rom, pick a kernel and stick with it for a while. If you want pure stability and battery life, use the most recent version of either DG's Firebird kernel 2 or Hardcore's speedmod kernel. If you want stability and oc/uv enabled, stick with Glitterball's kernel. Those 3 have been the best for me personally (again, YMMV).

Blitzkrieg trouble

FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
At least you got it installed, I couldn't even get that!
Sent from my Gingervolt-ed VS910 4G using xda premium
Mark Once Again said:
FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
Click to expand...
Click to collapse
Was it still unstable if you turned it down to 1GHz instead of keeping it at 1.5GHz?
I never could get that far. As soon as the phone was almost up it would restart. I tried about 5 or six times. I am happy with the phone without Blitzkrieg. Just thought I would pass along the info.
Thanks to all!
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
vortmax said:
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
Click to expand...
Click to collapse
I wonder why of all things, that would make a difference. You must've figured that out by chance? Haha
Sent from my Supercharged, Blitzed LG Revolution using xda premium.
I tried plugged into the usb on my pc, plugged into the charger and not plugged in at all. Same result each time. No complaint, just thought it might help having the info out there.
Thanks again!
You might try first installing a CPU utility like setcpu, and setting it to do no more than 1ghz on boot, and then flash it
Sent from my VS910 4G
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
Turn up the min. That fixed it for me
brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
You can turn off the haptic feedback to minimize that vibration reboot but it won't solve the issue tho
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
For those who use blitzkrieg kernel I recommend using cpu tuner instead of setcpu
I've been testing both app extensively for the past 2 weeks and notice cpu tuner is much more stable than set cpu and both have the same features
I use the free set cpu verison that you can download on the xda site that's the same as the paid version you get on the market
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
keynith said:
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
Click to expand...
Click to collapse
keynith, try to set the min cpu speed to 768 in setcpu.
So far after changing the min cpu speed i haven't had any issues again.
Did that yesterday and no problems since seemed to work
Sent from my VS910 4G using XDA App
brad08stanggt said:
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
Click to expand...
Click to collapse
Best thing I can say to do is to Restore to default and install things one or two at a time. It's likely an App causing the issue. I have had that happen a few times on my Droid 2 Global. Every time I would run the Goggle Nav App, my phone would randomly reboot. Don't have it installed, would be perfectly fine, until I installed Pandora app. Some buggy apps can cause such issue, and also bad settings. So, I would suggest going the 'long way' and starting from scratch and installing only necessary apps one or two at a time. If things work good, move on to next apps. When things go bad, recall the apps you just installed where the problem occurred. Restore your phone, install only those apps and see if you have reboot issues. If so, you are closing in to finding the real problem. I doubt, even by the post you wrote, that it's the phone or hardware. You need a factory fresh restore, including wiping ALL data, including settings for your apps.
-Cybie
Well?
I don't know if you guys fixed your problems yet, but I kinda had some of the same issues and I do not use CPU Tuner or Set CPU! Also I know that when you install Blitz 1.3 It defaults to normal CPU speeds that are already in phone settings as checked by CPU Spy after flashing Blitz. I have been using Antutu CPU Master Pro to set speeds and profiles works great for the price I use it on my Viewsonic G-tablet as well! Anyway what my first issue is the screen locks I had them all the time and the only way I kept them from happening was to set my min at the 245.76 MHz and my all the time max at 1200MHz. I also set the screen off at 122.88MHz - 245.76MHz On demand scaling profile to keep it not wakening from sleep quick enough. Antutu has all kinds of settings in the Pro version and If you want a overclock I think its the best to use.
The only Issue I have not figured out is you guys get a 10 sec vibrate then a reboot I get a Vibrate forever until I reboot I got woke up this morning at 4:00 A.M. by my phone vibrating next to my bed only happens at night and only when I start receiving emails early in the morning. I tried several screen off settings and not having vibration on at all and still happens figure that one out and I will gladly try anything you come up with!!! The only time it doesn't do it is if it is plugged in and charging!
Softkey lights
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
EDIT: charging to 100% fixed this.
Thanks for the quick reply and all your other posts too mt, they are very informative.
anangelablaze said:
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
Click to expand...
Click to collapse
Charge it to 100% and it will stop

Categories

Resources