Database Develop

[Q] Liberty and Safestrap

Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!

uconnjack said:
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
Click to expand...
Click to collapse
The thread at RootzWiki in the dev section for Droid3 is very helpful.
Some of the things to double check:
- Make sure you're swapping to "safe mode" before flashing the .zip
- Wipe data/cache

It works fine with safestrap
Sent from my DROID3 using xda premium

I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk

uconnjack said:
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Check the MD5, mine kept doing that until I downloaded over 3g. Downloading over 3g finally gave me an MD5 match
Sent from my DROID3 using xda premium

I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.

Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
It has a different way of reporting battery usage, it doesn't affect it though (based on 5.6.890) I've had my phone on for 9 hours now, medium usage, and I'm at 86%.

Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.

Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!

uconnjack said:
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
Click to expand...
Click to collapse
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
eww245 said:
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Click to expand...
Click to collapse
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.

Androidsims said:
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Click to expand...
Click to collapse
Using ring lockscreen, haven't tried any of the themes though. I'm suprised it did work actually.

I'm running it with safe strap right now not the best battery life but it'll do til hash gets ics running (which I know he will cm7 is my favorite but need tethering and camera)
Sent from my DROID3 using Tapatalk

My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App

kAmaOn said:
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
SBF back to stock 5.6.890, reroot, reinstall safestrap, re-do EVERYTHING pretty much. Thats my solution to everything.

[Q] ANOTHER Boot Loop Problem

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

[Q] Need HELP PLEASE (TouchPad Cyanogen 9 Alpha 0.6)...

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

[NIGHTLY] UNOFFICIAL CM9/ICS For Droid 4 For MotoICS Leak

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!

[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