Database Info

[Q] ClearDroid latest gingerbread serious issues.

The cleardroid is the best ROM i have ever seen on the XDA, but a few days ago when i flash my htc inspire 4g with Cleardroid gingerbread build, my messaging doesnt work. When I click on compose message, I got force close error on it. I have done some steps to resolve it but unable to resolve the issue.
1) First I have clear the data of messages from the settings.
2) I have run fix permissions from ROM manager.
and some other steps; but it didnt solve my problem.
Also wifi hotspot is not working.
Due to this i have downgraded the ROM to froyo again.
Please work on it, and resolve the issue, because i want to keep this rom on my phone.

faridtkp said:
The cleardroid is the best ROM i have ever seen on the XDA, but a few days ago when i flash my htc inspire 4g with Cleardroid gingerbread build, my messaging doesnt work. When I click on compose message, I got force close error on it. I have done some steps to resolve it but unable to resolve the issue.
1) First I have clear the data of messages from the settings.
2) I have run fix permissions from ROM manager.
and some other steps; but it didnt solve my problem.
Also wifi hotspot is not working.
Due to this i have downgraded the ROM to froyo again.
Please work on it, and resolve the issue, because i want to keep this rom on my phone.
Click to expand...
Click to collapse
Regarding the hotspot issue, that one is a real pain in the butt, and if you check the apps, there is a secondary tethering app included that is known to work for you.
The MMS issue is a strange one. Only about 1 in 100 users have any problem with it, and they are all different. Try this:
1. Make a backup through Rom Manager.
2. Do a full wipe, including dalvik wipe.
3. Re-download the ROM and reinstall.
4. Make sure you aren't running any apps that may conflict with Android, such as task managers or antivirus apps.
It may have been something to do with old app information being stored, or another app interfering with it. We will try to get you sorted out.

[Q] All Applications Force Closing on Reboot

I'm having this problem where sometimes after I reboot my G2x (running HellFire Phoenix V2.1 with the kernel already included) it would start back up with the "Touch Android to begin" screen as if I just did a fresh install and then nearly all my applications would start Force Closing on me.
I'm not sure what is causing this. My applications that we're previously installed all force close when I try to open it, and the Play Store is back to Market. My saved Google account is erased as well. Any ideas? It's beginning to get very annoying to have to wipe my phone and reinstall everything all over again.

hiefx said:
I'm having this problem where sometimes after I reboot my G2x (running HellFire Phoenix V2.1 with the kernel already included) it would start back up with the "Touch Android to begin" screen as if I just did a fresh install and then nearly all my applications would start Force Closing on me.
I'm not sure what is causing this. My applications that we're previously installed all force close when I try to open it, and the Play Store is back to Market. My saved Google account is erased as well. Any ideas? It's beginning to get very annoying to have to wipe my phone and reinstall everything all over again.
Click to expand...
Click to collapse
have you tried actually going in and wiping /data and /cache before re-flashing the rom to see if it helps? if not, try that.
if its only happening to you on that rom, try flashing another.
if none of this works for you, then use This tool.

Klathmon said:
have you tried actually going in and wiping /data and /cache before re-flashing the rom to see if it helps? if not, try that.
if its only happening to you on that rom, try flashing another.
if none of this works for you, then use This tool.
Click to expand...
Click to collapse
I always use the Nullifier application before installing the rom, yet I'm still having this weird problem. I'm going try that other wiping method and see how it goes. Thank you !

Downloads of gapps/ROM might be at fault also. If wiping doesn't solve it for you then you should re-download them.
Sent from my LG-P999 using xda premium

[Q] Constant Reboots with Synergy

This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.

jdubsss said:
This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.
Click to expand...
Click to collapse
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.

adoublearonn said:
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.
Click to expand...
Click to collapse
Thanks for the reply. I flashed leankernel tonight and so far so good... time will tell though.

[Q] Phone stays "Awake"

So I have had this problem two days in running -
Phone specs -
ROM: Viper XL 3.2.6
Kernel: Bulletproof
S-off
The problem - Each time I come out "Airplane Mode", the Phone stays "Awake" and this is a huge battery drain. When I checked the battery usage it is "Google Services". I have to restart the phone to resolve this issue. Is there a solution for this? I thought it is the kernel and went back to stock.
Am I doing something wrong?
Any help is appreciated.
Thanks

Did you just try to dirty flash the ROM again (wipe Dalvik and cache, but keep user data and reflash)? Its always worth a try when you encounter random bugs.
Was it a clean install originally (wiped Dalvik, cache and factory reset)?

Yes, it was a clean install of the ROM. for the Kernel i wiped the Cache and Dalvik cache. Now when I went back to stock kernel, i again wiped the caches alone and didn't do a factory reset.

Try to dirty re-flash the ROM. Can't hurt, especially if you still have the file, it will just take a few minutes to do.

Go into Apps and find Google Services Framework. Force stop and clear data, then reboot. This will temporarily break your Play Store account and other Google functions, but they will come back.

Thanks Redpoint and Elvis, I try these and see if it fixes the problem the next time i put it in "airplane" mode.

It's also important to note the Recovery you are using as, you may have done a clean install however 2.4 seems to have issues wiping, so this could be the root of your issue.

ah I see.. yes i do have TWRP 2.4. may that is it then. Thanks.

exad, i downgraded to TWRP 2.3.3 and went to airplane mode and back to normal. In fact i even flashed Bulletproof 1.1 kernel. The problem has gone away. Thanks!

If it's no trouble could you switch the [Q] to [RESOLVED]. This way people won't waste their time. Thanks!
-Sugardaddy Duncan

sriramll said:
exad, i downgraded to TWRP 2.3.3 and went to airplane mode and back to normal. In fact i even flashed Bulletproof 1.1 kernel. The problem has gone away. Thanks!
Click to expand...
Click to collapse
Any time! Glad it's working fine now!

[Resolved] Phone stays "Awake"
Arrow44 said:
If it's no trouble could you switch the [Q] to [RESOLVED]. This way people won't waste their time. Thanks!
-Sugardaddy Duncan
Click to expand...
Click to collapse
Sure.

Bringing this one up again.
Flashed Bulletproof 1.3 to my Viper XL 3.2.7. First time I took my phone off Airplane mode, it seemed to work fine. But the second time, Google Services "wakelocked" my phone.
I have TWRP 2.3.x. Right now, I went to Apps -> Google Services Framework and force stopped it and cleared the cache. I am not sure if it fixed the problem.
Any help is appreciated.

Use gsam or better battery stats to figure out what app it is.
Sent from my One X using xda app-developers app

sriramll said:
Bringing this one up again.
Flashed Bulletproof 1.3 to my Viper XL 3.2.7. First time I took my phone off Airplane mode, it seemed to work fine. But the second time, Google Services "wakelocked" my phone.
I have TWRP 2.3.x. Right now, I went to Apps -> Google Services Framework and force stopped it and cleared the cache. I am not sure if it fixed the problem.
Any help is appreciated.
Click to expand...
Click to collapse
I answered another person with a fix that worked for me on page 1419 of the venom thread in the dev section.

sriramll said:
Bringing this one up again.
Flashed Bulletproof 1.3 to my Viper XL 3.2.7. First time I took my phone off Airplane mode, it seemed to work fine. But the second time, Google Services "wakelocked" my phone.
I have TWRP 2.3.x. Right now, I went to Apps -> Google Services Framework and force stopped it and cleared the cache. I am not sure if it fixed the problem.
Any help is appreciated.
Click to expand...
Click to collapse
Go download greenify and "greenify" Maps, gmail and any other apps that may cause wake locks
-Sugardaddy Duncan

Thanks everyone for your suggestions. I will try those.
Stopping and clearing data on Google services did help with the wakelock but it broke google locations and such. but nevertheless it was a solution.

[Q] How often automatic crash reboot on Android? (Lollipop)

A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!

Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.

JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.

I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling

Two days, no reboots.

I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.

cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.

JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?

I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk

Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.

running cloudy 2.2 without any crashes. Thanks cloudyfa

illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck