Related
It keeps popping up every single GD SECOND! Everything I do it POPS UP and WONT Leave me ALONE! PLEASE HELLP! I bought Root Explorer but I cant find Car Home Anywhere! How DO I Purge my evo from this demonic evil!!!!!!!
crakerjaks said:
It keeps popping up every single GD SECOND! Everything I do it POPS UP and WONT Leave me ALONE! PLEASE HELLP! I bought Root Explorer but I cant find Car Home Anywhere! How DO I Purge my evo from this demonic evil!!!!!!!
Click to expand...
Click to collapse
Huh?
Sent from my PC36100 using XDA App
When it is open press menu and go to options and it will say something about automatic launch, un check that, then if you are rooted get titanium backup and uninstall it from there. Are you having problems with the speaker phone being on every time you make or receive a call? That's my problem and I can't figure out how to stop it.
Clay333 said:
When it is open press menu and go to options and it will say something about automatic launch, un check that, then if you are rooted get titanium backup and uninstall it from there. Are you having problems with the speaker phone being on every time you make or receive a call? That's my problem and I can't figure out how to stop it.
Click to expand...
Click to collapse
Yes it puts me on speaker all the time also, orientation cannot be disabled,screen lock cannot be disabled, volume stays at the same volume and cannot be adjusted. It is truly fubar'd!
crakerjaks said:
Yes it puts me on speaker all the time also, orientation cannot be disabled,screen lock cannot be disabled, volume stays at the same volume and cannot be adjusted. It is truly fubar'd!
Click to expand...
Click to collapse
Still have same issues stated above plus the car mode!
crakerjaks said:
Still have same issues stated above plus the car mode!
Click to expand...
Click to collapse
Me too!!!! Any help is greatly appreciated!!!!
Assuming you mean Car Panel.
Is it docked? If not, you should probably reflash your ROM and if you are restoring using Titanium Backup, don't restore Car Panel or the system data for it.
Car Panel
my evo cm7 wouldnt charge in my car even though the car panel app came up. i uninstalled it through Titanium Backup and now my phone charges!
My wives EVO is having the same issues. It started on FreshRom, so I switched to MikFroyo, and its doing the same thing. Would flashing a new radio have anything to do with it, because FreshRom was fine until a few days ago?
Sent from my HTC Hero CDMA using XDA App
My friend's phone just started doing this. His USB started bugging out at the same time so I'm thinking the two issues might be related.
i fixd the car home thing!
ok.. for those who are seeing car home annoyingly pop up.. here is my solution.
1. extract the zip file that u use to install the google apps on ur computer.
2. once extracted, delete the car home apk found under system>app> carhomegoogle.apk.
3. once deleted, go to the first sub folder in the extrated folder. ( the folder should have two folders in there called META-INF and system)
4. highlight those folders and create a .zip file.
5. rename it something simple ( gapps may work. since your are replacing the original gapps.zip folder)
6. mount on to the root of ur sd card.
this part might sound a bit extreme but this is the only way to make sure..
7. go to ur phone's recovery, and reinstall cm7 and the new google apps.
thats it.
the key here is to delete the car home app from the zip file. since anything inside cant be tampered with,u must extract it and modify it that way. then remake a new .zip file that does not contain car home.
enjoy.
i am now car home free.
for anyone still having this issue, which just started for me this morning, it seems to be a hardware issue not a Software issue. I could fiddle with my USB jack and it would stop for a few then start back up i am guessing mine is worn down and causing it to send a false call for a car dock.
Just look up "Dock no-op" on the market that fixed it for me.
Titanium back up works well too. It's also faster and easier in my opinion.
Sent from my PC36100 using XDA App
Not sure if anyone found a fix, but someone on the Google Code forum has found a solution. I am NOT taking credit for his fix, simply getting it out there as it is a huge issue.
1) Open up the .zip for your custom or stock Rom and look in the /system folder for a file called "build.prob". Copy this to your Desktop as you will be editing the file and then replacing the original on the Rom.
2) Open Notepad++ or any text editor of your choice and open the file. You are going to want to search for a line that says:
# try to disable proximity sensor in call by default
gsm.proximity.enable=false
Uncomment that line and make it equal to false.
3) Next, copy it back onto the /system directory of the Rom and then flash it. If it doesn't work for you, I am sorry. This is what worked for me so I just wanted to get another solution out there.
Again, I did not make this solution! I found it on Google Code forums.
Enjoy!
What problem does this fix ?
After making a phone call, there should be a process called Dialer. It gradually increases over time to 99% and kills the battery
Sent from my HTC Wildfire S A510e using XDA App
Small correction
Hey, small correction to your above post, hopefully this helps somebody out there
The file is actually build.prop
And the original commented line looks like the below WITH the hash in front
# try to disable proximity sensor in call by default
#gsm.proximity.enable=false
Instead of reflashing the ROM I booted the phone into recovery, then did
adb shell
adb mount /system
exited the adb shell, then
adb pull /system/build.prop c:\temp
edit c:\temp\build.prop, removed the comment hash
adb push c:\temp\build.prop /system/build.prop
rebooted, made a call, watching the battery usage, and dialer isn't at 98% after 30 minutes, in fact, it hasn't even shown its ugly face!
Awesome, thanks for that find!
Ah. Been reading posts all over and they all say to remove the hash tag. I'll give this a try later. You can for sure tell its not showing up after a reboot, power off, etc.? This really is an frustrating bug we have on our hands and I for one hate having a phone that lasts ~5 on a ful charge.
Sent from my HTC Wildfire S A510e using XDA App
Quick question. Dialer is already in my processes running. Will it still work or do I need to clear it first, cause I have no idea how to do that lol.
Sent from my HTC Wildfire S A510e using XDA App
Need your help. I'm trying to run these commands, but they aren't working for me. When I go to type adb shell mount /system, it keeps saying adb: not found. Any help with this? I used to be able to do this, but it's not letting me do it
Please clarify one thing for me...
I don't know for sure but this seems to disable the phone's proximity sensor during calls, so the screen will be always on while calls are being made (until the screen timeout activates).
Am I right? If so this fixes one bug and creates another problem.
I would be glad if someone that already tried this can confirm what I'm thinking.
Thanks a lot in advance.
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
But it seemed to work for me. I did it and rebooted my phone and the Dialer process was gone. I then made a test call and while the call was on, the Dialer process was not there. Then, I kept checking and it still did not appear. I also applied the best battey tip you'll ever need.
aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
aigaming, thanks a lot for confirming what I already suspected.
This is a "fix" that creates an even bigger problem.
Last week I had a phone call with an Engineer that lasted more than 80 minutes.
If the screen was on during this period then instead of the Dialer draining the battery I would have the LCD draining the battery.
I don't need the proximity sensor for auto-brightness for example (like to set it on my own) but it shouldn't be turned off because it's probably necessary for the camera application (for example).
This Dialer battery drain is just a cosmetic bug IMO.
If we want to know what really eats our batteries then we should use *#*#4636#*#*, usage statistics instead.
There is info in miliseconds of usage by each app.
And what about fix for S-ON phones?
shaarky said:
And what about fix for S-ON phones?
Click to expand...
Click to collapse
If you edit the file, replace it on the ROM and flash it, then this method works on s-on phones. Be warned that the screen will remain on during calls.
miguelca said:
I guess that's off-topic here. This thread is about another problem.
Click to expand...
Click to collapse
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
I also interested in fix for battery drain on s-on phones. Mine adb says permission denied.=(
shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
The method drzerog uses is for s-off phones. The method on the first post works with all, s-on included.
Sent from my HTC Wildfire S A510e using XDA App
shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
I updated my posts. Sorry for the mistakes but now info is correct. Please read again. Thanks.
Sent from my HTC Wildfire S A510e using XDA App
I can also confirm that, for me, during a call it does NOT leave the screen on. It turns it off on my device. Maybe it's different for each phone? But that can't be. Weird. Again, confirming it works on my device and my battery is now showing proper statistics, as well as Dialer process not appearing
Also wanted to make note that I have changed the topic title and noticed this thread is now in the rom/recovery/guides/kernal/root stickie!! VERY COOL!
Not work for my WS rom 2.3.5 stock/ S-OFF, the dialer process still keep 92%
I am having a problem installing the Amazon Appstore (and the foxfi installer too now that I think about it). I am able to download the APK and run it but once in the program the install button does nothing. I mean I click on it and there is no error message, no program crash, nothing. It's almost like the install button image isn't a button and I'm clicking on nothing. Clicking cancel or show all for the permissions works fine.
I have enabled install from unknown sources and even tried to disable it and try but nothing works. Has anyone encountered anything like this before? TIA for any help.
EDIT: BTW I'm on stock and not rooted.
SOLVED: Thanks to Zerkai it appears that Screen Filter and Screen Adjuster can prevent APKs from installing.
Try to install these apps with an APK Installer. Like the following.
https://play.google.com/store/apps/...SwyLDEsImNvbS5wb3RlbnRlLmFway5pbnN0YWxsZXIiXQ..
See if that changes anything.
X10D3 said:
install an APK installer app.
https://play.google.com/store/apps/...SwyLDEsImNvbS5wb3RlbnRlLmFway5pbnN0YWxsZXIiXQ..
See if that changes anything.
Click to expand...
Click to collapse
Just tried that and it is exhibiting the same issue. Called amazon and they hadn't heard of it and had no suggestions on how to fix it. They did mention security apps might be able to block installs and that led me to look at my apps. I did have Norton mobile security installed but stopping it and then even uninstalling it didn't get rid of the issue.
This is really starting to frustrate me.
May sound obvious, but have you tried restarting your phone?
If you were rooted I'd recommend clearing your dalvik and /cache.
One thing you may try is cleaning up your SD card.. Even try renaming the android folder on your sd card. It holds app data for diff apps. you system will recreate it. just delete the recreated on and change the name back after you've tested it.
The only other option (that comes to mind) is a factory reset. I would try the other stuff first. Something is corrupt somewhere.
By any chance are you using, Screen Filter?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
X10D3 said:
May sound obvious, but have you tried restarting your phone?
If you were rooted I'd recommend clearing your dalvik and /cache.
One thing you may try is cleaning up your SD card.. Even try renaming the android folder on your sd card. It holds app data for diff apps. you system will recreate it. just delete the recreated on and change the name back after you've tested it.
The only other option (that comes to mind) is a factory reset. I would try the other stuff first. Something is corrupt somewhere.
Click to expand...
Click to collapse
I did try rebooting. anything ever goes wrong with any electronic device of mine and it's the first thing I try.
zerkai said:
By any chance are you using, Screen Filter?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I am not, but I did have screen adjuster installed and figured whatever screen filter was doing might be done by screen adjuster. So I uninstalled and guess what it worked now. Thanks a lot Zerkai, you the man.
But wtf would screen filter do that could cause this?
Beats me. Lol. I was baffled when I figured out Screen Filter was the cause. But all is well as long as it's not active. Have a good day!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Old thread. Yes, I know. Came across this thread trying to fix the same issue. The app causing the issue for me was JuiceDefender. I think JD controlling the screen's brightness level was the issue. Anyway, I disabled JD and I was able to access the button.
SG3 SGH-T999 Stop Installing third party APK's SOLVED! is REAL
erikk said:
I am having a problem installing the Amazon Appstore (and the foxfi installer too now that I think about it). I am able to download the APK and run it but once in the program the install button does nothing. I mean I click on it and there is no error message, no program crash, nothing. It's almost like the install button image isn't a button and I'm clicking on nothing. Clicking cancel or show all for the permissions works fine.
I have enabled install from unknown sources and even tried to disable it and try but nothing works. Has anyone encountered anything like this before? TIA for any help.
EDIT: BTW I'm on stock and not rooted.
SOLVED: Thanks to Zerkai it appears that Screen Filter and Screen Adjuster can prevent APKs from installing.
Click to expand...
Click to collapse
BUMP THANKS SO MUCH! I posted videos of my problem on you tube and Facebook etc! this was it my Official solution you have helped relieved me from this terrible Situation! Hi5 forever dude!
Justin Cram
DyingJedi
Tapdeck
Sorry to bump, but we can add Tapdeck to the list of apps that cause this problem. It's a live wallpaper.
I posted this question in the correct thread for the ROM I'm using in my signature (also note I'm using the newest version of the KT747 kernel as well), but people are currently more interested in hearing themselves talk on that thread, calling people trolls when the "troll" is actually helping answer questions, and just waste space with non-development chit-chat.... So maybe asking it here will get an answer!
I'm getting a partial wakelock constantly from LPAPlayer, a low power audio player that supposedly gets installed or screwed up when you install AwesomeBeats, but I never had that installed and can't seem how to disable or fix the issue with LPAPlayer eating up the battery, making the CPU run at max while the screen is off....
Anyone got any ideas or suggestions? Thanks!
Bump... Same problem here with VZW s3 running stock rooted JB 4.1.1!
Sent from my SCH-I535 using xda app-developers app
Have you tried flashing clean from stock? And just to clarify, you have LPAplayer without installing the Beats audio equalizer?
Sent from my SGH-I747 using xda premium
crazililazn said:
Have you tried flashing clean from stock? And just to clarify, you have LPAplayer without installing the Beats audio equalizer?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
No I didn't come from stock but I did do a clean flash. And you are correct and having that wakelock without having installed beats
Sent from my SCH-I535 using xda app-developers app
travis.bridges10 said:
No I didn't come from stock but I did do a clean flash. And you are correct and having that wakelock without having installed beats
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe it was a bad flash? Have you tried reflashing since you noticed the wake lock?
Sent from my SGH-I747 using xda premium
crazililazn said:
Maybe it was a bad flash? Have you tried reflashing since you noticed the wake lock?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I've been on this since about 2 days after it came out never had a problem. The all of a sudden it started 2 days ago. I haven't installed anything new and haven't made any substantial changes. The only media players I use are play and Pandora.
Sent from my SCH-I535 using xda app-developers app
Just to add in to what Travis has been saying, and it all applies the same for me too, I just reflashed the device with the same ROM, but wiped everything first, including System.... Because these aren't official JB ROMs, I'm not spending too much time getting everything set up on the device right now, so when I wipe, I restore data from a previous backup, and while I'm sure that's not helping anything, there has to be a way to prevent LPAPlayer from using up so much battery!
KryptosXLayer2 said:
Just to add in to what Travis has been saying, and it all applies the same for me too, I just reflashed the device with the same ROM, but wiped everything first, including System.... Because these aren't official JB ROMs, I'm not spending too much time getting everything set up on the device right now, so when I wipe, I restore data from a previous backup, and while I'm sure that's not helping anything, there has to be a way to prevent LPAPlayer from using up so much battery!
Click to expand...
Click to collapse
Well one thing I know for sure is that we have the same exact nonofficial JB rom installed (lol) and that I do not have the LPAPlayer issue, nor could I find it installed. Travis says that he uses Google Play Music and Pandora, so maybe it has to do with one of the two. Try using Titanium and freezing these two apps and see if it fixes your battery drain.
I know it isn't Pandora, I don't use it or even have it installed on my phone.... I could see it having to do something with Google Music, I use that constantly while driving. Won't be in the car tomorrow so I'll freeze it tonight and see if anything gets better, one can only hope when no real solutions are being presented!
STILL having the issue, Pandora and GMusic are NOT the issue (as far as I can tell....)
Here's a guy having the same issues too, found that Awesome Beats was the recommendation, and never installed it either, still no resolution for him:
http://www.samsunggalaxys3forum.com...s3-help/7523-interesting-battery-problem.html
Looks like the only solution is to wipe and reinstall everything with TiBU, hoping that the issue isn't stuck in one of my user apps and just the data I'm restoring after every time I wipe....
EDIT - I MAY have found a solution! Those affected, please help me test this - those NOT affected, please check and see if your settings are different!
http://forum.xda-developers.com/showpost.php?p=25475691&postcount=4732
On there, it said to disable LPAPlayer, set lpa.decode=false in build.prop, under System, using Root Explorer, or similar. I like Root Explorer because when you select R/W at the top, press and hold on build.prop, select Open in Text Editor, you can hit the Menu button and Save and Exit while Root Explorer automatically saves the original as a backup, using .BAK. If you're unfamiliar with Root Explorer or need more instructions, let me know, I need others to test this OR see if your lpa.decode setting was already set to false! Mine WAS set to true before I edited it, rebooted, and now I'm testing to see if it works.... after 14 mins, I'm seeing a deep sleep of 5 mins so far, so it may have worked!!! There isn't any mention of any partial wakelocks from LPAPlayer right now either!
KryptosXLayer2 said:
STILL having the issue, Pandora and GMusic are NOT the issue (as far as I can tell....)
Here's a guy having the same issues too, found that Awesome Beats was the recommendation, and never installed it either, still no resolution for him:
http://www.samsunggalaxys3forum.com...s3-help/7523-interesting-battery-problem.html
Looks like the only solution is to wipe and reinstall everything with TiBU, hoping that the issue isn't stuck in one of my user apps and just the data I'm restoring after every time I wipe....
EDIT - I MAY have found a solution! Those affected, please help me test this - those NOT affected, please check and see if your settings are different!
http://forum.xda-developers.com/showpost.php?p=25475691&postcount=4732
On there, it said to disable LPAPlayer, set lpa.decode=false in build.prop, under System, using Root Explorer, or similar. I like Root Explorer because when you select R/W at the top, press and hold on build.prop, select Open in Text Editor, you can hit the Menu button and Save and Exit while Root Explorer automatically saves the original as a backup, using .BAK. If you're unfamiliar with Root Explorer or need more instructions, let me know, I need others to test this OR see if your lpa.decode setting was already set to false! Mine WAS set to true before I edited it, rebooted, and now I'm testing to see if it works.... after 14 mins, I'm seeing a deep sleep of 5 mins so far, so it may have worked!!! There isn't any mention of any partial wakelocks from LPAPlayer right now either!
Click to expand...
Click to collapse
Also started noticing this issue on my Sprint GS3, while playing Google Music, as that is the only music player I have, and have not installed any other apps, like Beats, or the like. Via Betterbatterystats I would see that anytime I'd play/use Google Music, LPAPlayer would keep the phone awake, even if I forced closed the Google Music app. Only way to stop it from keeping the phone awake was to reboot my phone, which was a pain since I use it to stream music all day. Anyone know what LPAPlayer is for, where it's located? I can't find much info on it. I'm going to try the above and edit the build.prop entry, as mine was set to true, and report what I get! Thanks!
r3ddawn said:
Also started noticing this issue on my Sprint GS3, while playing Google Music, as that is the only music player I have, and have not installed any other apps, like Beats, or the like. Via Betterbatterystats I would see that anytime I'd play/use Google Music, LPAPlayer would keep the phone awake, even if I forced closed the Google Music app. Only way to stop it from keeping the phone awake was to reboot my phone, which was a pain since I use it to stream music all day. Anyone know what LPAPlayer is for, where it's located? I can't find much info on it. I'm going to try the above and edit the build.prop entry, as mine was set to true, and report what I get! Thanks!
Click to expand...
Click to collapse
Yep, same issue I had too - someone must have edited the build.prop on us in a ROM or something to have that effect on different carrier's SGSIII's.... I've seen MUCH better battery life out of my phone since then, with the only wakelock coming in the form of Light Manager, but everyone who uses LightFlow / Light Manager for their LED notifications complain about poor battery life from wakelocks, so there's nothing I can do with that right now!
Glad I could help, definitely report back and let me know what you come up with when you change that setting and reboot!
KryptosXLayer2 said:
Yep, same issue I had too - someone must have edited the build.prop on us in a ROM or something to have that effect on different carrier's SGSIII's.... I've seen MUCH better battery life out of my phone since then, with the only wakelock coming in the form of Light Manager, but everyone who uses LightFlow / Light Manager for their LED notifications complain about poor battery life from wakelocks, so there's nothing I can do with that right now!
Glad I could help, definitely report back and let me know what you come up with when you change that setting and reboot!
Click to expand...
Click to collapse
Yup that was it, after the change and a reboot, I no longer have that issue. I am still searching to try to figure out why/what would have caused it, but the issue is fixed with the edit made, so I hope this helps others as well. Thanks again!
KryptosXLayer2 said:
Yep, same issue I had too - someone must have edited the build.prop on us in a ROM or something to have that effect on different carrier's SGSIII's.... I've seen MUCH better battery life out of my phone since then, with the only wakelock coming in the form of Light Manager, but everyone who uses LightFlow / Light Manager for their LED notifications complain about poor battery life from wakelocks, so there's nothing I can do with that right now!
Glad I could help, definitely report back and let me know what you come up with when you change that setting and reboot!
Click to expand...
Click to collapse
I was getting wakelock from LPAPlayer too (on sprint gsIII). Yesterday was the first day i noticed the poor battery like. About two days ago for the first time, i installed lightflow just to check it out. I immediately uninstalled it cause i don't really have a use for the app. I just now looked in betterbatterystats and found it was LPAPlayer. Do you think that app is causing the issue then?
r3ddawn said:
Yup that was it, after the change and a reboot, I no longer have that issue. I am still searching to try to figure out why/what would have caused it, but the issue is fixed with the edit made, so I hope this helps others as well. Thanks again!
Click to expand...
Click to collapse
Glad to hear it!
smac7 said:
I was getting wakelock from LPAPlayer too (on sprint gsIII). Yesterday was the first day i noticed the poor battery like. About two days ago for the first time, i installed lightflow just to check it out. I immediately uninstalled it cause i don't really have a use for the app. I just now looked in betterbatterystats and found it was LPAPlayer. Do you think that app is causing the issue then?
Click to expand...
Click to collapse
It's possible, but probably not likely.... I know I had Lightflow installed as well and uninstalled it to use Light Manager instead (Lightflow was causing a separate battery drain not associated with LPAPlayer, from what I understand), but I think that's just coincidence that we both had it installed at one point and it changed the settings to enable LPAPlayer....
I am/was having the same issue. I only saw LpaPlayer giving my phone a partial wake after using Google Play Music. I changed the build.prop as suggested and it looks like that fixed the problem. Thanks
sorry for bumping a month old thread but i've noticed this issue as well. Google music would also freeze up on me. Rather annoying. Let's see if editing build.prop fixes it
KryptosXLayer2 said:
STILL having the issue, Pandora ROM rooted GMusic are NOT the issue (as far as I can tell....)
Here's a guy having the same issues too, found that Awesome Beats was the recommendation, and never installed it either, still no resolution for him:
http://www.samsunggalaxys3forum.com...s3-help/7523-interesting-battery-problem.html
Looks like the only solution is to wipe and reinstall everything with TiBU, hoping that the issue isn't stuck in one of my user apps and just the data I'm restoring after every time I wipe....
EDIT - I MAY have found a solution! Those affected, please help me test this - those NOT affected, please check and see if your settings are different!
http://forum.xda-developers.com/showpost.php?p=25475691&postcount=4732
On there, it said to disable LPAPlayer, set lpa.decode=false in build.prop, under System, using Root Explorer, or similar. I like Root Explorer because when you select R/W at the top, press and hold on build.prop, select Open in Text Editor, you can hit the Menu button and Save and Exit while Root Explorer automatically saves the original as a backup, using .BAK. If you're unfamiliar with Root Explorer or need more instructions, let me know, I need others to test this OR see if your lpa.decode setting was already set to false! Mine WAS set to true before I edited it, rebooted, and now I'm testing to see if it works.... after 14 mins, I'm seeing a deep sleep of 5 mins so far, so it may have worked!!! There isn't any mention of any partial wakelocks from LPAPlayer right now either!
Click to expand...
Click to collapse
Just want to say THANK YOU for this post. AT&T GS3 here stock rom 4.1.2 and rooted. This fixed the lpaplayer wakelock for me. I used Root Browser to change the setting and then restarted. Noticeable improvement in battery life as a result.
Since I soft bricked and then restored my phone I have been having a couple issues. The first is that my service just drops for no reason, and I only get it back from restarting the device. The second is whenever I turn my phone on, it tells me that gapps has stopped working. Should I be concerned /is there fix?
Sent from my LG-LS980 using xda app-developers app
eddytheyeti2 said:
Since I soft bricked and then restored my phone I have been having a couple issues. The first is that my service just drops for no reason, and I only get it back from restarting the device. The second is whenever I turn my phone on, it tells me that gapps has stopped working. Should I be concerned /is there fix?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Flash the ZVC.tot, maybe something got corrupted. Did you edit the build.prop? The G2 build.prop is too big for some apps and when you edit they truncate it, giving the effects you have. I use RootExplorer and at least it gives me a warning that it will truncate the build.prop as its too big. If thats the case, next time use a build.prop editor or edit on desktop and replace original setting permissions back to rw-r-r.