Database Develop

Camera is not working with webos

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

ClassicNerd to CM9 Question

Hey all,
So awhile back, I flashed ClassicNerd, which was fantastic, but I wanted to switch back to CM9 last night. I went into CWM and wiped everything and flashed CM9, but when I booted up my Touchpad, it seems like ClassicNerd remained there. It's a bit hard to explain, so I've attached a pic of the issue I'm having. How exactly do I get rid of ClassicNerd? Do I just leave it there? Thanks for your help guys!

sportsinger75 said:
Hey all,
So awhile back, I flashed ClassicNerd, which was fantastic, but I wanted to switch back to CM9 last night. I went into CWM and wiped everything and flashed CM9, but when I booted up my Touchpad, it seems like ClassicNerd remained there. It's a bit hard to explain, so I've attached a pic of the issue I'm having. How exactly do I get rid of ClassicNerd? Do I just leave it there? Thanks for your help guys!
Click to expand...
Click to collapse
download root exblorer or es file manager go boot folder and delete the classicnerd ulmage

Here you go. Full instructions in the OPs post.
http://forum.xda-developers.com/showthread.php?t=1705627
Sent from my cm_tenderloin using xda app-developers app

Thanks guys, I appreciate it

Just download tga.uImage cleaner from the Classicnerd website and flash in CWM before flashing a new rom and it will completely clean moboot and return it to default settings
Sent from my CyanogenMod9 TouchPad using TapaTalk 2

Safestrap 3.05 help please.

I uninstalled the old version of safestrap, then installed the new version. I can do everything just fine (install, wipe, etc) but when I try to boot from the ROM slots, the phone just sits at a black screen.. I tried flashing Eclipse 3.0 and nothing happens.. help???
Sent from my DROID3 using xda app-developers app

Well eclipse 3.0 hasn't worked for me. The latest cm10,aokp,and aosp boot for me as well as mavrom 4.5 and axiomcs 1.0. Have u tried any other roms aside from eclipse?
Sent from my XT862 using xda app-developers app

Don't think eclipse works with new Safestrap. I have tested CM10, AOKP, AOSP, and Steel Droid. Those 4 all are "working".
Steel Droid is the most stable one i have tried so far, CM10, AOKP and AOSP all lag for me.

Hey guys,
New to Droid 3/ Milestone 3 World here.
I just bought one, actually with the 5.2.390.XT860.Brasil.en.BR version.
I'm not exacly new to flashing roms, and recoveries, but in this case I'm a little confused. Is it possible to use SafeStrap on this one? Or better go for an older version of it?
Thanks in advance.

@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!

bArAbAts said:
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
Click to expand...
Click to collapse
I was thinking about trying... Maybe during the weekend..
Thanks for the advice, man!

I took my phone back to stock (from an oldish CM9 that had been working reasonably well for me for some time) so I could install SS3. Made the mistake of letting the phone OTA update itself and then had to find a new root hack before I could get SS3 installed.
Unfortunately the OTA update has messed with the radio, as reinstalling the CM9 I've used for months gets a system where the phone app just crashes.
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.

Well,
I installed the 3.0.5 version. Works like a charm! The easiest to use recovery that I ever use.
But the question is: Is it safe to downgrade it?
Sorry about the dumb question.

SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.

matthewgeier said:
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Click to expand...
Click to collapse
Is the issue you're having that when you're speaking to people on the phone you can't hear anything and they can't hear you? Cause on CM9 there should be no issues with using it as a phone as long as you don't enable bluetooth ever or use buttons on a headset connected to your phone. I haven't tried CM10 yet so I wouldn't know too much about that. Just for some extra info to save your time do not flash Liberty or Eclipse, they don't seem to work. The newest Maverick works fine.

matthewgeier said:
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
Click to expand...
Click to collapse
I was going to try from the stock.
I am much more familiar with clockworkmod.
Anyway, thank you for the advice
Sent from my XT860 using xda app-developers app

[Q] Do I have an un-android-able Touchpad?

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

[Q] Android side of my Touchpad won"t boot.

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.