Hello All,
I'm not that new to the XDA scene as I've been rooting for a couple of years now (HTC Aria, HTC One XL), however I am completely stumped as to why my HP Touchpad keeps randomly rebooting while in android. Here's the TL;DR
1. Installed moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly using ACMEInstaller2.
2. Everything installed fine, except device randomly reboots within 5 min of starting up, sometimes immediately (before I can even unlock the display), sometimes even while loading the cyanogenmod splash screen.
3. I have read everything on the XDA's about this problem and scoured Google for hours to no avail. Tried clearing cache, Dalvik cache, then fix permissions. Still randomly reboots. Tried turning off beats audio in webOS. Still randomly reboots. Used ACMEUninstaller, erased webOS completely, re-rooted using ACMEInstaller3, moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly. Still Randomly Reboots.
I am at the end of my ropes here, about to give up and just accept that my device is not compatible with android, even though countless others are running android with little problem. I'm just not understanding what I am doing wrong, if anything. Any comments / advice would be very much appreciated.
Peace and Love
That's odd. Maybe try a different ROM?
bananagranola said:
That's odd. Maybe try a different ROM?
Click to expand...
Click to collapse
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
leetpcguy said:
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
Click to expand...
Click to collapse
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
bananagranola said:
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
Click to expand...
Click to collapse
Just tried that and it rebooted before I could even navigate to No-Frills CPU Control :/ I appreciate the input though.
It seems that once it boots, if i don't touch anything, it will not reboot while at the lock screen. I've had it charging for the past 4 hours or so while booted in CM9 and haven't ventured past the lock screen and it hasn't rebooted yet.
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
rrrrrrredbelly said:
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
Click to expand...
Click to collapse
I have tried both of those as well as setting both the min and max frequency to 1.2 GHz. It still reboots; seems to be independent of CPU clock speed.
I've also tried disabling all haptic feedback as well as turning the sound all the way down and turning off the keypress sounds. Still reboots.
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
slicetwo said:
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Click to expand...
Click to collapse
The only thing I did different than what you suggested here is let the ACMEInstaller3 install CM9 for me. I have not tried jscullins build of CWM though, I will give that a shot and also try installing the ROM manually after ACME has installed CWM.
jsgraphicart said:
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
Click to expand...
Click to collapse
I'm 99% sure I was using the right apps, and usually I can make it through the setup portion of the initial boot without a restart. Doesn't last too much longer than that though...
dmarchant said:
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
Click to expand...
Click to collapse
I've used ACMEInstaller3 the last two times I reverted everything to stock, erased and reset webOS, and started over. Still had the same problems as when I used ACMEInstaller2.
youre doing something wrong,, probly something simple..
have you looked @ youtube?
roland has some good vids.
so does reverendkjr
Related
Been A long time Lurker here at XDA, so much great info and support!!
Ok so here is my problem I have a 32GB touchpad. I have WebOS running, no problems at all. I have tried many many times installing CM7 and CM7 XRON-ified. Every version and i get into this boot loop....
I have done an ACME Uninstall....reinstalled webos with the Doctor.... fresh installs of everything... full formats of "SD Card"... I am at a loss
After i have done a fresh install i will reboot into CM and it will be working... then just reboot, and start the boot loop...ill stop it on the MBOOT menu and just let it sit then boot back into CM and it will load... then randomly just reboot and go back to the boot loop...
I am at a loss... could it be hardware related... WebOS runs find and diagnostics that i have run in webos come back clean... Any one have any thoughts?.....
If you need any other info please let me know...
Thanks
Cdrshm
Sounds to me like the caches need wiping and another fresh install. But I'm sure you've tried this so I am at a loss.
"A little nonsense, now and then, is relished by the wisest men."
strikerage said:
Sounds to me like the caches need wiping and another fresh install. But I'm sure you've tried this so I am at a loss.
"A little nonsense, now and then, is relished by the wisest men."
Click to expand...
Click to collapse
I have done it more then a dozen times.. hardware issue maybe?
Sent from my Galaxy Nexus using Tapatalk
Bump. Anyone have any thoughts?
Sent from my Galaxy Nexus using Tapatalk
according to the thread, it does that a few times (exact numbers havent been given) because of initial settings.
the 4 TPs ive done all had at least 2 or 3 random reboots that settled out and disappeared .
endlesszeal said:
according to the thread, it does that a few times (exact numbers havent been given) because of initial settings.
the 4 TPs ive done all had at least 2 or 3 random reboots that settled out and disappeared .
Click to expand...
Click to collapse
Yea, but this is actually a boot loop, not just a reboot....many times won't even boot back into cm...
Sent from my Galaxy Nexus using Tapatalk
FLASHING ROMS WILL VOID YOUR WARRANTY AND COULD POTENTIALLY DAMAGE YOUR PHONE -- WHILE I MAKE EVERY ATTEMPT NOT TO LET THIS HAPPEN, IT'S STILL A RISK THAT YOU'RE TAKING. IF SOMETHING BAD SHOULD HAPPEN TO YOUR PHONE, PLEASE DON'T BLAME ME -- HENCE THIS WARNING.
This isn't so much a ROM announcement as it is a direction to find the unofficial nightly builds of CM9 for the Droid 4 (based on Motorola ICS leaks)
Download Here from ROMbot
Download GApps Here (04/29 Goo-Inside GApps Link).
FLASH THE GAPPS.ZIP FILE AFTER YOU FLASH THE ICS.ZIP
WHAT do I need to run this ROM?
- Rooted
- Running a Motorola ICS leak (.206, .208, .211, etc)
- I recommend that you run Safestrap v2.00 to install this. Here's how to use Safestrap
And you can download Safestrap for the Droid 4 (v2.x for ICS-leak users) here:
Safestrap « Hash-of-Codes
WHAT can I expect to work right now?
- 4G and basic phone function
- All sensors
- Camera, Panorama and Face-unlock
- Video Recording
- HD YouTube
- Netflix
Current Known Issues?
- Data connection is a work in progress. It's MUCH better than it used to be in the old ICS builds, however there is always room for improvement. Due to the "global" data connection style of stock Motorola ICS, this problem will probably continue to be worked on. Feedback is always appreciated, but if you see it posted already then there's a good chance I know about specific issues.
- Currently, there is a bug in the rotation display of the phone. What I mean is, that when you take the phone and rotate it, the display will squeeze in on itself and then pop back out. This is a *known* issue and I'm working very hard to fix it.
- The CM9 built-in Wifi Tether won't work. You need to use the "Wifi Tether" app that's bundled into the ROM. Once you open it, hit [menu] and "Settings". Select "Change Device-Profile" to "Generic ICS".
- I'm sure there's more, I'll update this list here in a bit.
WHO works on this?
Myself and @DHacker29 work as a team to build AOSP-based ROMs (and device setups) for several Motorola phones. Typically, I do the coding work in C, C++ or Java while DHacker maintains the blobs, runs merges with CM/AOKP sources, and solves device issues which require less coding.
WHAT is a "nightly"?
It's an automated build ran from a script. It basically: deletes the current set of output files, sync's with github, and then attempts to do a brand new build. It can break at times, in which case we'll fix it (usually this happens when there are framework changes which didn't get merged).
WHY would I want this?
- Since we work on several devices, this is how we decided to start keeping builds up-to-date. Rather than spend several hours a week on builds and uploading. This happens automatically every night around 2am PST.
- It's up to you the community to identify good "stable" builds.
Feel free to follow me on Twitter as I do sometimes make announcements there before I do forum postings:
Hashcode (@Hashcode0f) on Twitter
We maintain all of our code at github:
https://github.com/o...ns/STS-Dev-Team
Screenshots:
[ COMING SOON ]
Reserved for future use
Looking great Hash! Thanks for your work.
my excitement is robust
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
jgardner said:
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
Click to expand...
Click to collapse
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I did the exact same thing (not wiping on a fresh safestrap). I believe that message about the sd-ext is normal when wiping dalvik.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I believe the reason behind that message is that the Dalvik cache is not stored on the sd-ext, but rather the sd, which is internal. Since theres technically 2 SD cards on our device, it looks for the dalvik on the first one. A dev would probably have better advice on it though,....I may be wrong.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
Safestrap checks for a dalvik cache under a theoretical /sd-ext partition on the external SD. It's almost never there tho. So you can safely ignore that message.
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
kwyrt said:
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I havent flashed this one just yet but i know on my droid 3 i let the battery charge all the way up and then wiped battery stats and all was fine after that.
Sent from my DROID4 using XDA
thanks hashcode! you're the man!
Appreciate the Rom.. Runs very nicely on Droid 4. Easy install.
I know HW video is being worked on. Will that fix or update allow Movie Studio to work?
Very interested and excited about Ice Cream Sandwich and future updates to this Rom
Installed and loving it so far.
The one thing I've noticed, the phone gets really hot, and the battery usage is pretty poor. I actually watched my battery percentage drop while doing my installs of all the apps that I had to download.
I lost about 3% during that process, even when plugged into the wall charger.
I'll keep an eye on it, as I'm close to a charger at all times, so bad battery life doesn't affect me too much.
Can't wait for BT to work, as that would be the last piece in a daily driver for me.
EDIT - just discovered I'm having issues with Chrome Beta. I've never used it before, but it won't load any websites. I'll DL Dolphin for the time being, but would love to try out Chrome. Just wondering if anyone else is running into this.
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
doubleokneegro said:
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
Click to expand...
Click to collapse
Ok found out it was my charger. For some reason it wasn't actually charging and was just causing heat. Plugged it into a different charger and all is well now.
still no love with Chrome though.
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
---------- Post added at 10:16 PM ---------- Previous post was at 10:07 PM ----------
gangrif said:
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
Click to expand...
Click to collapse
Nevermind, google has solved my despair.
http://www.technipages.com/how-to-reset-frozen-droid-4.html
Thanks.
Absolutely love this ROM!!!!! One request though, what do I need to install to get webtop working? Just got the lapdock 500 a couple hours ago and love this ROM to much to give it up
Sent from my DROID4 on ICS
Everything seems to be working perfectly for me, even the camera is working properly. I haven't tried bluetooth yet, but I'm not too worried about it, I barely use it. Wifi connects and works, no problem there. I noticed a slight lag after installing setCPU but now it seems fine. I'll check tomorrow to see how the battery life is but for now every things pretty smooth. Thanks!
I get this message with every ROM I tried with fresh install or "restored".
It happens almost everytime I install or uninstall some app or do something cpu intensive! Why? Does system have the highest priority when in use?
It happens in GB and ICS!
Let's not talk about how SLOW and unresponsive it gets after you install or remove something. I really don't get why. Never happened with another android device I have :S
More info, what Rom + Kernel and ramhack are you use...?
What app unistal, system app or user app...?
Because if u remove some system app get errors and freezing...
Fresh install is wipe data / factory reset before install a new rom...
It happened with every single rom/kernel I used. And also with a fresh install wiping before installing
Don't worry you're not alone.
System has stopped responding occurs frequently on my phone when installing uninstalling or updating apps.
I'm on Temasek cm7 120.
Sent from my Optimus 2X using Tapatalk 2
-sandro- said:
It happened with every single rom/kernel I used. And also with a fresh install wiping before installing
Click to expand...
Click to collapse
Strange, I use temasek CM 7 at long time ago + vadonka's kernel and don't have some issues like you... My phone is faster, responsive like a first day with + 100 app instaled... I don't have your problem... Try flash only rom without kernel and looks if is stable...
Mungulz said:
Don't worry you're not alone.
System has stopped responding occurs frequently on my phone when installing uninstalling or updating apps.
I'm on Temasek cm7 120.
Sent from my Optimus 2X using Tapatalk 2
Click to expand...
Click to collapse
I would like to know the reason! My inexpert guess: some process gets all the cpu with a high priority causing everything else to queue, basically the resources are not balanced
Is it know that tegra 2 might have bottleneck problems?
Hi, I'm having a problem with my Touchpad 32GB. I'm having problem with the CM9 2012/11/18 build. I've installed it, but after a few minutes of use, it resets on me. I've done it a few times, same problem. I've restore it back to webos 3.0 using this page http://forum.xda-developers.com/showthread.php?t=1426244 and I've tried installing it again, but I still get the same problem.
The files that I have in the cminstall folder when I started are:
moboot_0.3.5
update-cm-9-20121118-NIGHTLY-tenderloin
update-cwm_tenderloin-1012
And when I run the novacom command, I'm using the ACMEInstaller2.
Can someone help me with this problem? Also, on a side note, which version of Android would be most stable?
Thanks in advance for any help.
vdn20 said:
Hi, I'm having a problem with my Touchpad 32GB. I'm having problem with the CM9 2012/11/18 build. I've installed it, but after a few minutes of use, it resets on me. I've done it a few times, same problem. I've restore it back to webos 3.0 using this page http://forum.xda-developers.com/showthread.php?t=1426244 and I've tried installing it again, but I still get the same problem.
The files that I have in the cminstall folder when I started are:
moboot_0.3.5
update-cm-9-20121118-NIGHTLY-tenderloin
update-cwm_tenderloin-1012
And when I run the novacom command, I'm using the ACMEInstaller2.
Can someone help me with this problem? Also, on a side note, which version of Android would be most stable?
Thanks in advance for any help.
Click to expand...
Click to collapse
I use the 11/18 nightly and it works fine for me.
Take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=2002968
It could help with your rebooting problem. I've been lucky, never have had that problem.
Make sure if you doctor back to 3.0.0 to update to 3.0.5. You can do it OTA.
Good luck.
chicle_11 said:
I use the 11/18 nightly and it works fine for me.
Take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=2002968
It could help with your rebooting problem. I've been lucky, never have had that problem.
Make sure if you doctor back to 3.0.0 to update to 3.0.5. You can do it OTA.
Good luck.
Click to expand...
Click to collapse
Okay, I'll give that a shot. I'm curious, can you tell me which version of ACMEInstaller did you use? Thanks
Update:
Playing a sound didn't seem to work. There were some sounds played when I tap a button, but I also played a music button to be sure, but it still restarted on me after a few minutes.
Update 2:
I've restore my touchpad hopefully back to the way it was when I got it. Can someone give me some direction on what to use to install Android, hoping what I originally done caused some kind of problem.
I used acme installer 2.
I recommend using ACMEInstaller3. It will be necessary if you ever want to install Jelly Bean, so might as well do it now.
chicle_11 said:
I used acme installer 2.
Click to expand...
Click to collapse
bananagranola said:
I recommend using ACMEInstaller3. It will be necessary if you ever want to install Jelly Bean, so might as well do it now.
Click to expand...
Click to collapse
Tried using both during the install, but both gave the same problem. Any other ideas on what I can try?
vdn20 said:
Tried using both during the install, but both gave the same problem. Any other ideas on what I can try?
Click to expand...
Click to collapse
What are your min/max clock settings set to?
Sent from my ThunderBolt using xda premium
I'm wondering, does it freeze or get jittery before it shuts off, or does it just turn black and die
Sent from my SAMSUNG-SGH-T989 using xda premium
rrrrrrredbelly said:
What are your min/max clock settings set to?
Sent from my ThunderBolt using xda premium
Click to expand...
Click to collapse
I'm not sure what the min/max clock settings are set to. How can I check?
-SGA- said:
I'm wondering, does it freeze or get jittery before it shuts off, or does it just turn black and die
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
After a few minutes of use, it freezes for a moment, and then it resets.
vdn20 said:
I'm not sure what the min/max clock settings are set to. How can I check?
Click to expand...
Click to collapse
I dont remember where the setting is on CM roms, but if you go into settings, then they should have a cyanogenmod setting option, then performance I think. The min clock CPU speed is 192 I believe, I can't run anything below 384, and on some rom's I have to set the min at 432 or it will randomly reboot. Not saying this will solve your issue, I was just curious what your speeds were set to.
You can also use an app from the play store, such as kernel tuner or no frills cpu to set your speeds.
rrrrrrredbelly said:
I dont remember where the setting is on CM roms, but if you go into settings, then they should have a cyanogenmod setting option, then performance I think. The min clock CPU speed is 192 I believe, I can't run anything below 384, and on some rom's I have to set the min at 432 or it will randomly reboot. Not saying this will solve your issue, I was just curious what your speeds were set to.
You can also use an app from the play store, such as kernel tuner or no frills cpu to set your speeds.
Click to expand...
Click to collapse
Just reinstalled CM9 on it using ACMEInstaller3. The min/max is 384/1188 MHz. This time, it was a little different. A few minutes in, I tried to turn on the WiFi and the screen gone blue. I restarted it and and up the CPU speed. It restarted in a few minutes, last longer this time. I wiped the both cache and did a fix permission, saw it in another post, and it restarted within the first 2 minutes after it boots into CM9.
I've been running first CM9 then CM10 (jcsullins) for about 18 months with no problem. For some reason I can't fathom, the Android side stopped booting. I've tried wiping and reflashing through TWRP as well as restoring a nandroid backup (through TWRP) but no joy. I've also done a reinstall through ACMEInstaller as well as an ACMEUninstall followed by a fresh ACMEInstall. Nothing has worked so far.
A couple of nights ago i'd been using it but at bedtime I just shut it down. I didn'.t put it on the touchstone as it was already fully charged. In the morning it wouldn't boot until I pressed the on/off and home buttons together. I could and still can, boot into WebOS. I suspect there is some file or folder is corrupt but have no idea how to find and fix it. Any guidance will be greatly appreciated.
DaElderGeek said:
I've been running first CM9 then CM10 (jcsullins) for about 18 months with no problem. For some reason I can't fathom, the Android side stopped booting. I've tried wiping and reflashing through TWRP as well as restoring a nandroid backup (through TWRP) but no joy. I've also done a reinstall through ACMEInstaller as well as an ACMEUninstall followed by a fresh ACMEInstall. Nothing has worked so far.
A couple of nights ago i'd been using it but at bedtime I just shut it down. I didn'.t put it on the touchstone as it was already fully charged. In the morning it wouldn't boot until I pressed the on/off and home buttons together. I could and still can, boot into WebOS. I suspect there is some file or folder is corrupt but have no idea how to find and fix it. Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
Make sure you have a full charge, then try this guide: http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
Try using cwm instead of TWRP. Several (myself included) have had problems with it.
Also, when you reinstall android, use acmeinstaller3. It gives you more space for the Rom.
Good luck.
chicle_11 said:
Make sure you have a full charge, then try this guide: http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
Try using cwm instead of TWRP. Several (myself included) have had problems with it.
Also, when you reinstall android, use acmeinstaller3. It gives you more space for the Rom.
Good luck.
Click to expand...
Click to collapse
That for the suggestions. I'll try them and post back. BTW, all the install attempts were with ACMEInstaller3. I even tried to restore a previous TWRP backup. That didn't work either.
touchpad android running, cant reboot
ok here's a good one.
My wife's (yes, ugh, support duty here) HP touchpad (android 4.2.2)
Kernel 2.6.35 cyanogenmod dated aug--9-13
cyanogenmod v 10.1.20130808-EXPERIMENTAL -tenderloin-bluetooth_test
OK. here's the problem
according to status screen, this durn machine has been up for (and I bet this is part of the problem)
503 hours, 27 mins , and 55 seconds.
lets see 503/24= almost 21 days since last boot.
All is working fine in android (except like all machines, it is starting to get sluggish.
think this is a 16 gb system, not a 32 gb.
any ideas???
HELP..................
chicle_11 said:
Make sure you have a full charge, then try this guide: http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
Try using cwm instead of TWRP. Several (myself included) have had problems with it.
Also, when you reinstall android, use acmeinstaller3. It gives you more space for the Rom.
Good luck.
Click to expand...
Click to collapse
You might want to upgrade to acmeinstaller 4 or 5; 5 works great for me.
Sent from my Nexus 4 using xda app-developers app
markbnj said:
ok here's a good one.
My wife's (yes, ugh, support duty here) HP touchpad (android 4.2.2)
Kernel 2.6.35 cyanogenmod dated aug--9-13
cyanogenmod v 10.1.20130808-EXPERIMENTAL -tenderloin-bluetooth_test
OK. here's the problem
according to status screen, this durn machine has been up for (and I bet this is part of the problem)
503 hours, 27 mins , and 55 seconds.
lets see 503/24= almost 21 days since last boot.
All is working fine in android (except like all machines, it is starting to get sluggish.
think this is a 16 gb system, not a 32 gb.
any ideas???
HELP..................
Click to expand...
Click to collapse
If rebooting doesn't help then install and use the Clean Master app from the app store. It may help you clean up some memory.
If webos is slow then delete everything in LOST.DIR. This is the recycle bin.