I've install cm9 on my touchpad and i understand that the camera is not working in cm9 so i always boot into webos if i need to make skype video calls. But recently i found that my camera is also not working in webos. All the camera apps fail to open. I am currently with webos 3.05 with dualboot cm9. Any idea about how to fix it? Thanks.
Sent from my HTC Vision using XDA
You might need to reinstall WebOS - sounds like something got touched that wasn't supposed to be.
Take a Nandroid backup, then follow the instructions in the thread in General on how to Factory Reset / Downgrade to 3.0.0, then upgrade from there to 3.0.5, and then reinstall Android, then restore your backup. Will take about 30 mins, and you should have everything working again.
You can check to see if you have loaded any other camera apps in webOS. I experienced this when I installed a preware camera app in 3.0.5. After working with tech support in a live chat, I removed the preware app and rebooted the touchpad. My camera works flawlessly now. You could also follow the above suggestion to make a nandroid backup in android then do a full erase in webOS. Reinstallation of the webOS software might be just the thing to get you back on track. Hope this helps.
-- Sent from my TouchPad using Communities
Thx a lot for replying. Will try your mothed n report here.
Sent from my HTC Vision using XDA
Related
Okay I am having some problems. I upgraded from the Cyanogen 7 Alpha 3.5 to the new Cyanogen 9 0.6 using the lilputing (spell?) instructions to the letter. Everything upgraded and installed just fine but when it booted up I got a picture asking for pin code/pass code with a numbered keypad.
I don't have a pass code or pin on my TouchPad. What am I supposed to enter here??? Please someone HELP ME so I can have my TouchPad back! Thanks and hope someone can help me SOON! I don't want to wipe the data as I don't want to loose all my apps and games I put on there when I had 7. Is there anything else I can do??? I am anxious to try Cyanogen 9 after hearing so many GOOD things about it! THANKS DEVELOPERS!
sorry but dont think its possible to go from cm7 to cm9 and keep your apps and data.
some wont work on ICS anyway.
Actually according to RootzWiki here: http://rootzwiki.com/topic/15509-releasealpha06-cyanogenmod-9-touchpad/ it states you can do it. My Mother was able to upgrade from 7 (Alpha 3.5) to 9 (Alpha 0.6) without any problems. I just can't figure why it would work on one TouchPad but not another.
There is. When i upgraded mine, i did not lose my apps and data. What i did is I ran the novacom acmeuninstaller2 script in dos prompt and made sure i have the zip file inside the cminstall folder in my tp.
colin_404 said:
sorry but dont think its possible to go from cm7 to cm9 and keep your apps and data.
some wont work on ICS anyway.
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App
alias4ever said:
Actually according to RootzWiki here: http://rootzwiki.com/topic/15509-releasealpha06-cyanogenmod-9-touchpad/ it states you can do it. My Mother was able to upgrade from 7 (Alpha 3.5) to 9 (Alpha 0.6) without any problems. I just can't figure why it would work on one TouchPad but not another.
Click to expand...
Click to collapse
It states you can try it and results may vary.
7 to 9
alias4ever said:
Okay I am having some problems. I upgraded from the Cyanogen 7 Alpha 3.5 to the new Cyanogen 9 0.6 using the lilputing (spell?) instructions to the letter. Everything upgraded and installed just fine but when it booted up I got a picture asking for pin code/pass code with a numbered keypad.
I don't have a pass code or pin on my TouchPad. What am I supposed to enter here??? Please someone HELP ME so I can have my TouchPad back! Thanks and hope someone can help me SOON! I don't want to wipe the data as I don't want to loose all my apps and games I put on there when I had 7. Is there anything else I can do??? I am anxious to try Cyanogen 9 after hearing so many GOOD things about it! THANKS DEVELOPERS!
Click to expand...
Click to collapse
I was able to jump from CM7 to CM9 via an upgrade. However, you might want to invest in Titanium Backup to be able to easily do a complete wipe and easy restore. It is a great product for "ROM jumpers"
I was also able to make the jump, but it made me reinstall almost all of my apps before they would work again anyway. Thankfully I was able to use Amazon for them, as the Market forgot what free apps I had...
I use Astro app backup for my touchpad. It doesn't back up data, but I like it that way, fresh install.
You could try reinstalling CM7, and see if it will boot, then back up your apps, wipe and install CM9. I use Titanium Backup on my phone, but on the TP it was spotty which ROMs would let it open. Because Astro doesn't need root it always works.
Sent from my Galaxy S II (i777)
Has anyone tried ROM Toolbox to see if it was any more compatible than Titanium Backup is. I would personally recommend a clean install to make sure no bugs are caused by leftover applications. To each his own though.
They say on rootzwiki that if you use the acmeinstaller2 you shouldn't have any problems upgrading
Sent from my MB860 using Tapatalk
Had the same Pincode issue, I used ACMEUninstall to remove all traces of prev installs/.
then just reinstalled, working
I have been running Android on the TouchPad since the cm7 days and have gone through plenty of ROMS. Unfortunately though, I tried to update TWRP to 2.3 and also change over to a new CM9 ROM. Now if I try to get into TWRP or Android I get a boot loop. I can still get into WebOS just fine though.
Is there a simple fix for this? In my reading/searching I've heard horror stories of just running WebOS Doctor. Can I just do an Acmeuninstall and do acmeinstall?
newbk said:
I have been running Android on the TouchPad since the cm7 days and have gone through plenty of ROMS. Unfortunately though, I tried to update TWRP to 2.3 and also change over to a new CM9 ROM. Now if I try to get into TWRP or Android I get a boot loop. I can still get into WebOS just fine though.
Is there a simple fix for this? In my reading/searching I've heard horror stories of just running WebOS Doctor. Can I just do an Acmeuninstall and do acmeinstall?
Click to expand...
Click to collapse
You'll have to do an ACMEUninstall, then reinstall. I did the same thing when the fault TWRP update came out. And thanks to wwjoshdew, I got it all fixed.
I guess that's okay if you have a recent nandroid backup. Which I didn't *sad face*
Anyways, that's all you need to do.
Sent from Mr Z's HP Touchpad
Thanks for the reply. Acmeuninstall it is.
*UPDATE* Alright, dang thing isn't being recognized in webOS recovery. I guess I am going to have to really start over again.
Sent from my One X using xda app-developers app
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
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.
A while back I installed cm9 on my Touchpad and it worked great. Decided to upgrade to cm10 and now gapps/youtube etc went working. What is the easiest way to start over. I don't mind going back to cm9. I'm not very experienced at these type of things. I just want the easiest way to get it working like it was. Thanks in advance for the help.
frza21 said:
A while back I installed cm9 on my Touchpad and it worked great. Decided to upgrade to cm10 and now gapps/youtube etc went working. What is the easiest way to start over. I don't mind going back to cm9. I'm not very experienced at these type of things. I just want the easiest way to get it working like it was. Thanks in advance for the help.
Click to expand...
Click to collapse
The easiest way to start over is to doctor the TouchPad to clear everything and then use the TouchPad toolkit installer I'm sure this would work for you
Sent from my TouchPad using XDA Premium HD app
The easiest and fastest way is to boot into recovery, either TWRP of CWM, and do a factory reset, then clear cache , then clear Dalvik cache. After that has been done, then all you need to do is flash CM 9 and the Gapps and then reboot. I have done this many times and it works fine. The only problem is that you close all of your apps and data. But as soon as you go to Google Play all of your apps will download automatically. IF you created a Nano backup....then just do the factory reset, clear caches then restore your backup. This was is WAY easier and you don't lose any or your apps.
Do not use webos Doctor without removing android first!!
You maybe have an incorrect version of gapps for your version of android, so maybe check this first. It is worth upgrading from cm9 -> cm10, definitely!
Cheers