Database Develop

[Q] CM9 Reboot Issue

I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...

I meant ACMEInstaller2 where I wrote Novacom2 ....

The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)

that may be the route I go. After about 15 reboots it is currently holding steady I have not made any interventions.
As a side issue, I get email notifications but the email app crashes upon opening. Gmail works fine though....

quarlow said:
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I did a fresh start as above and the CM9 from is running problem free and 10x better than before when I had done the acmeinstaller2 method. Thanks button hit.

gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
Try fixing permissions and wiping up cache from CWM, that fixes the reboots after power-on for me.
It used to do it if I left the screen to go off, but is fine now

I too am having reboot issues, but it only happens when I'm doing something. So far trying to open the Photoshop PS Touch app will cause a reboot, clicking settings in boat browser, etc. It's strange as hell.

I as well get the stock android mail client crashing when opened but its notifacations and gmail all work. I just installed maildroid and disabled stock email and seems to work OK

gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
I have the same issue, but normally when the screen is on, it always reboots when I try to connect to usb storage, I have a galaxy s2 running on stable(nightly had too many bugs). anyone has the same problem?

I usually get reboots when I let the screen turn off due to inactivity. I tried installing TWRP and doing a clean install from there but it rebooted at the setup screen for CM9. I've had reboot issues since I first installed CM9, but its improved a little bit. I did try uninstalling android completely then reinstalling, but still got reboots. Does anyone have any other suggestions?

I think the best thing to do is use ACMEUninstaller to complete remove Android from your TP, then reinstall from scratch. I had reboot issues after upgrading from CM7a2 until I did a complete wipe.

Tablet Constantly Reboots

So I've come here as a last ditch effort
I've been trying to load CM9 onto my tablet for several days now and am having absolutely no luck. There are always two things that happen with it either it constantly reboots on the loading screen right after the splash screen or if I somehow manage to get past the loading screen, which has happened maybe a half dozen times it reboots after I hit one or two buttons.
Now as far as I know I've tried every single way of flashing the roms.
I've used ACMEInstaller2
I've used ACMEUnInstaller, then ACMEInstaller2
I've used cwm and twrp to flash (I wipe data, cache and dalvik everytime)
I've flashed CM7 and then ACMEInstaller2 CM9 on top
I've flashed CM7 and cwm to flash to CM9
I've used the uImage cleaner in cwm then wiped data, cache, dalvik and reformatted data, cache, and system, reflashed and wiped cache/dalvik again and fixed permissions
I've tried multiple Roms including but not limited to Classicnerd, CM9 alpha 2, and CM9 nightly.
They all end up with the same issue
Note:I've also applied the various reboot fixes, and none of them seem to make a difference.
I can get CM7 to work on the tablet in the effect that it runs smoothly once it starts up but it does do the loading screen reboot quite often and the only way Ive found around that is to wipe the cache/dalvik every time I start up the tablet.
If anyone has any ideas of where I could go next with this it would be greatly appreciated, I'm pretty much at my wits end lol.
Edit: Oh I forgot to mention I've also WebOS doctored it.

What version of WEB OS doctor did you use? And have you tried formatting the SD card option in web os?

I used webos doctor 3.0.0
Also I was told not to format the sdcard, is it just the option in cwm or do i go about doing that another way.

In web os you have the option to format the memory card. But if you doctored with 3.0 you should be fine as it re partitions the device before formatting and flashing.

Hrm, well if I got the right WebOS doc any other ideas that might work?

Have you tried a full factory reset ? Using THIS THREAD, you can wipe everything back to complete nothingness, then try reinstalling. It could be something is wrong with your boot entries, partition table, or the like. I know you've tried to doctor it, but doing it this way ensures you start with a completely clean slate (to the point of deleting all of your partitions and starting fresh).
Back up anything you wanna keep, then try that - and re-download all of the necessary files again, just to be sure. It's what I would do.

Check that its charged.
My tp will reboot at the splash screen if charge is <70%. Only booting to webos whilst connected to charger, then leaving for a day will allow it to boot reliably to cm9.
Even on the latest nightly, I have big charging issues with cm9
Sent from my cm_tenderloin using xda premium

Well I did the factory reset as you suggested and then doctored it from 3.0.0 to 3.0.4 then tried CM9 again-No Change. So I decided to flash CM7, which seems to run fairly stable it I think I've only seem it reset once and as for the rebooting after the splash screen it still does that but if you let it restart a couple times it eventually goes through. I downloaded a CPU overclocker and set the min to 384 then reflashed CM9 through ACME. It seemed to work for awhile, about half an hour, watched an episode on netflix then when I tried to open another app BAM reboot and now its back to either loading screen reboots or about 5 seconds worth of CM9 then reboot. This has got to be the most frustrating piece of equipment I've ever worked with.

That's really odd... Especially since it worked for a bit and then not. Is it getting overly warm ? That might be a sign of an overheating problem. Or you could just have a bad device. They do exist. Does it do the reboots from within WebOS as well ? Or just when you're on Android ?

No its never rebooted in webos. And it doesnt feel like it was getting hot, when I was checking the CPU stuff it was running at around 27 degrees celcius I believe I'm not sure whether thats overly hot or not.
Update: I ran the tablet again and it seemed to work pretty stable for about 10 mins then random restart I had the cpu temp up on the main screen though and it read 22 Celsius before it rebooted.

Restart Problem
I have had touchpad for 8 months after which the screen did not respond to the touch. So I sent it for RMA and received another unit. I installed the aplha2 but it kept on restarting as soon as I boot into the Android. I tried different ROMS's as well but same problem.
I downgraded the webos with webos doctor 3.0.0 but the same. No matter how I use the touchpad in webos it does not reboot.
Any help will be much appreciated.
Thanx

kenbhaji said:
I have had touchpad for 8 months after which the screen did not respond to the touch. So I sent it for RMA and received another unit. I installed the aplha2 but it kept on restarting as soon as I boot into the Android. I tried different ROMS's as well but same problem.
I downgraded the webos with webos doctor 3.0.0 but the same. No matter how I use the touchpad in webos it does not reboot.
Any help will be much appreciated.
Thanx
Click to expand...
Click to collapse
WebOS doctor back up to 3.0.5
AcmeInstaller2 to install one of the latest nightlies (alpha 2 is quite outdated which a search would have revealed)
If you still have issues you may be one of the unlucky few whose Touchpad hardware just won't tolerate Android to which there is no fix
Sent from my cm_tenderloin using Tapatalk 2

Replacement?
Thanx for replying. Is there any way that I can get it replaced since it is under the warranty of course I wouldn't say that it reboots in Android but can I make some excuse to get a replacement which may turn out to be good device?

[Q] CM11 bug?

I had CM 10.2 installed on EMMC and I updated to verygreen's CM 11 from the development forum. I performed an update vice a clean install, but I did clean davlik, but other than that I didn't reset anything.
I activated developer options the normal way with no issues once in CM 11, but when I click on developer options in settings, the settings app crashes. I performed a factory reset, cleared all cache, and it worked fine. Then I did a full restore from backup and now when I try to access developer options it crashes again.
I have since updated to the nightlies a couple of times, but there's no change after each update.
Has anyone else had this issue? I searched and couldn't find anyone else that had this issue. Any ideas?

Do a fresh install, those are still nightlys and sometimes **** like this happens.
I had a time where Trebuchet crashed everytime I opened the drawer.

Jann F said:
Do a fresh install, those are still nightlys and sometimes **** like this happens.
I had a time where Trebuchet crashed everytime I opened the drawer.
Click to expand...
Click to collapse
Yea, that's what I ended up doing. Did a fresh install after wiping everything and now it works great.

[Q] ART on CM11 20140714-UNOFFICIAL

I know it is experimental, but I'm running CM11 20140714-UNOFFICIAL and posts in the developers forum says that ART works well on it, so I thought I'd give it a try. I went to settings, developer options, select runtime and chose ART. The phone rebooted, did a phone is upgrading / reoptimizing 122 apps and when it finished, I got that:
"unfortunately com.android.phone has crashed"
When I checked "ok" the same message pops. Repeat. I rebooted and phone and it did re-optimization on 22 appls. But still the loop of crashes, maybe 80% are the com.android.phone, but I also get com.android.gapps and com.android.acore and other apps (youtube, etc). I tried booting into recovery mode and wiping the cache davlik cache and cache, but same problem. I was able to switch back to davlik (when you press ok after a crash, 20% of the time you get a half-second window to do something and I was eventually able to get to settings, etc). That caused the phone to crash on startup, but wiping the cache cleared that. So now I'm back where I started.
But it seems like other people having gotten ART working on the 20140714 CM11 build. Did I do something wrong when switching to ART? Anything else to try?
Thanks,
Ben

exhibit679 said:
I know it is experimental, but I'm running CM11 20140714-UNOFFICIAL and posts in the developers forum says that ART works well on it, so I thought I'd give it a try. I went to settings, developer options, select runtime and chose ART. The phone rebooted, did a phone is upgrading / reoptimizing 122 apps and when it finished, I got that:
"unfortunately com.android.phone has crashed"
When I checked "ok" the same message pops. Repeat. I rebooted and phone and it did re-optimization on 22 appls. But still the loop of crashes, maybe 80% are the com.android.phone, but I also get com.android.gapps and com.android.acore and other apps (youtube, etc). I tried booting into recovery mode and wiping the cache davlik cache and cache, but same problem. I was able to switch back to davlik (when you press ok after a crash, 20% of the time you get a half-second window to do something and I was eventually able to get to settings, etc). That caused the phone to crash on startup, but wiping the cache cleared that. So now I'm back where I started.
But it seems like other people having gotten ART working on the 20140714 CM11 build. Did I do something wrong when switching to ART? Anything else to try?
Thanks,
Ben
Click to expand...
Click to collapse
depends on which gapps you use. Banks mini so far works the best for art aside 1 issue. you have to use different camera app or at least i have to. experiment your self and see which gapps works best for you other then cm gapps as it fails with art.

TripFX said:
depends on which gapps you use. Banks mini so far works the best for art aside 1 issue. you have to use different camera app or at least i have to. experiment your self and see which gapps works best for you other then cm gapps as it fails with art.
Click to expand...
Click to collapse
Can I dirty flash different gapps over my working install, or I do I need to do a full wipe to remove my current (non-ART compatible) gapps first?
Thanks,

exhibit679 said:
Can I dirty flash different gapps over my working install, or I do I need to do a full wipe to remove my current (non-ART compatible) gapps first?
Thanks,
Click to expand...
Click to collapse
you can try dirty if you want but personally I would do a full wipe.

Google Play after Pie

Hi everyone,
I hope someone can help me. One week ago I upgraded to Pie on my Galaxy Note9 (Verizon). Ever since, I've been having a problem updating apps in Google Play. Most of apps get stuck on Download Pending. A few go through just fine, but most don't. When I turn off my NordVPN, every update goes through without a problem. I never had this problem on Oreo, and I don't want to have to turn off VPN every time I update.
Has anyone else encountered this problem? Any suggestions or solutions?
Thank you.

Try clearing cache and data on the google play app or maybe loadvpn has a glitch with android pie and u could report it. Also try wiping cache on phone by going into stock recovery.

timex300 said:
Try clearing cache and data on the google play app or maybe loadvpn has a glitch with android pie and u could report it. Also try wiping cache on phone by going into stock recovery.
Click to expand...
Click to collapse
Hi. This seems to have worked. Thank you very much.
First I cleared cache in Settings > Device Care > Storage, and Memory
Then I went to Settings > Apps and cleared out cache in Google Play
I don't know about clearing cache in stock recovery, is that a better way of doing it?
Thanks again

Well if wiping data and cache helped no need to wipe cache on stock recovery. What wipe cache does is help phone perform better sometimes. But it doesnt delete anything. U could do it. All u gotta do is power off phone then hold volume up and bixby button and press power button also and it should take u to stock recovery then use volumes(up or down) to highlight wipe cache then highlight yes and wipe it them reboot and it should perform better.