Hello Everyone,
I wanted to ask if anyone knew what feature or function of Jellybean 4.1.2 made BatteryGuru for the LGOG AT&T E970 work properly. I have reflashed Houstonn's KitKat Rom on to my after doing a proper cleaning procedure. When I open the app it says that it's Wi-Fi Management Feature will be disabled by this device not supporting Android's Network Location Feature. What is this feature and how was it in Jellybean but not KitKat?
Thank you so much.
briguy15 said:
Hello Everyone,
I wanted to ask if anyone knew what feature or function of Jellybean 4.1.2 made BatteryGuru for the LGOG AT&T E970 work properly. I have reflashed Houstonn's KitKat Rom on to my after doing a proper cleaning procedure. When I open the app it says that it's Wi-Fi Management Feature will be disabled by this device not supporting Android's Network Location Feature. What is this feature and how was it in Jellybean but not KitKat?
Thank you so much.
Click to expand...
Click to collapse
There was a lot changed in KitKat. Some apps need to be updated to work with 4.4
By the way... Did that app ever even increase battery life for you? I've messed with many battery apps over the years, and that app ranks at the very bottom of my list.
Sent from my LG Optimus G using xda app-developers app
4.4 changed something related to who/what can access battery information, so No battery apps work so far., BetterBatteryStats being the only significant casualty.
briguy15 said:
Hello Everyone,
I wanted to ask if anyone knew what feature or function of Jellybean 4.1.2 made BatteryGuru for the LGOG AT&T E970 work properly. I have reflashed Houstonn's KitKat Rom on to my after doing a proper cleaning procedure. When I open the app it says that it's Wi-Fi Management Feature will be disabled by this device not supporting Android's Network Location Feature. What is this feature and how was it in Jellybean but not KitKat?
Thank you so much.
Click to expand...
Click to collapse
Have you made sure you are on the latest gapps? Batteryguru is still in learning mode atm so i can't tell, but it's not showing any errors. I'm on the 11/12 PA kitkat build from houstonn with the gapps from the same folder here(supports dalvik and ART): http://downloads.codefi.re/houstonn/kitkat/geeb/PA
MiZrY said:
There was a lot changed in KitKat. Some apps need to be updated to work with 4.4
By the way... Did that app ever even increase battery life for you? I've messed with many battery apps over the years, and that app ranks at the very bottom of my list.
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
It helps on houstonn's carbon 4.3 ROM. Nothing drastic.
Sent from my LG Optimus G using Tapatalk
Related
Hey guys,
I am soon going to enter the rooted world of android and flashing roms on my note. Is there still a reason to remove bloatware from the phone when running a custom rom? Will the bloatware apps still be running or will they merely just be taking up memory in the storage?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
fullyflaredfred said:
Hey guys,
I am soon going to enter the rooted world of android and flashing roms on my note. Is there still a reason to remove bloatware from the phone when running a custom rom? Will the bloatware apps still be running or will they merely just be taking up memory in the storage?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
The answer largely depends on which rom you choose..
Most custom roms are relatively bloat free, unless you are wanting to use a rooted stock variant build ...
And with regard to running bloat, the answer is yes ...
Apps like Google maps, navigation apps etc. Will often run in the background as available services, even when closed.
But you can use titanium backup and other similar apps, to "freeze " these applications....g
Edit : I always remove my bloat .....even from stock builds ....by freezing a suspected app for testing....
Then if all is well and stable ....I dump it ....g
Takes up space
possibly running in the background
things you may never use anyway
can add as you want after the custom rom
They fixed the battery drain issue with Google maps...don't worry about any Google services.
Sent from my Galaxy Nexus using Tapatalk 2
First, if task reads this, thanks for the great ROM. I would thank you in the dev thread, but I do not have enough posts yet to post there. Maybe by the end of this thread.....
I have been using handcent for texting because I have friends who constantly use group messaging from iPhones and the stock MMS app was a mess to use in that scenario.
I got frustrated with handcent (it is really slow to load, and overall not the same kind of smoothness I enjoy from the rest of the ROM). I looked at the stock MMS app yesterday and noticed that it has group threading!
There seem to be some UI issues though, and I am interested in trying to work on it.
So after all that, my question is where should I look for this particular MMS app? Are these changes part of AOSP, CM, or AOKP? Task's version in particular?
Thanks for your time everyone.
anaithnid said:
First, if task reads this, thanks for the great ROM. I would thank you in the dev thread, but I do not have enough posts yet to post there. Maybe by the end of this thread.....
I have been using handcent for texting because I have friends who constantly use group messaging from iPhones and the stock MMS app was a mess to use in that scenario.
I got frustrated with handcent (it is really slow to load, and overall not the same kind of smoothness I enjoy from the rest of the ROM). I looked at the stock MMS app yesterday and noticed that it has group threading!
There seem to be some UI issues though, and I am interested in trying to work on it.
So after all that, my question is where should I look for this particular MMS app? Are these changes part of AOSP, CM, or AOKP? Task's version in particular?
Thanks for your time everyone.
Click to expand...
Click to collapse
That's the 4.2 app you will have to wait
Sent from my GS4 running CM11 Kandy Kane
Meaning it is part of 4.2 Android AOSP? Or was this modified by AOKP or someone else?
So where can I go to find out more about how the path works from Google's code to where task releases his version for our device?
I think he's wanting tasks version of the mms? If I'm wrong correct me but couldn't he simply pull the mms.apk from his files on his phone and take a look at them to get the info he's looking for?
Sent from my SGH-I777 using xda premium
The 4.2 MMS apk gas group threading
Sent from my GS4 running CM11 Kandy Kane
122ninjas said:
The 4.2 MMS apk gas group threading
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
So I take this to mean that it is part of the os. Not something added in somewhere else along the chain that comes to our devices.
Sent from my SGH-I777 using Tapatalk 2
anaithnid said:
So I take this to mean that it is part of the os. Not something added in somewhere else along the chain that comes to our devices.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Weren't you referencing the stock messaging app that came with tasks Rom, that's the messaging app you're wanting to try to smooth out right?
Sent from my SGH-I777 using xda premium
Weren't you referencing the stock messaging app that came with tasks Rom, that's the messaging app you're wanting to try to smooth out right?
Click to expand...
Click to collapse
I was using handcent, but now I am using the stock app the comes with Task's AOKP rom
Maybe my question was not clear (sorry, I am not meaning to sound like a ****, but thats a hard sentence to type without jerk inflection)
The group mms threading option that now exsists in the AOKP rom from Task, who added it in?
Did the AOSP and Google people put that option in there? Meaning is this going to be part of the Google Stock version of android 4.2?
Did the AOKP team add it, meaning that we will continue to see that option in any AOKP roms?
Did Task add it, is he a wizard?
I partly want to know because I am interested in taking a look at the code to see if I can squash some bugs I have found. Thus, I would like to know where the original point of entry is for this change.
If I can get beyond this being a exercise for myself, I would like to know where I should contribute any changes I make.
Alternatively, if someone can suggest where I can find more info on how the chain is put together that gets the code from Google all the way through task to my phone, that would also be helpful.
Thanks for all the replies so far.
I have found most music apps stop responding after first song load on boot in JB based ROMs. Rockbox widget does not have this problem and is what I am using. It is in early development for Android and is not available in the play store yet.
For me the app freezes after clicking play. Then I close the app and remove from task manager then open the app and it works from then on
Sent from my SGH-I897 using xda app-developers app
developweb said:
I have found most music apps stop responding after first song load on boot in JB based ROMs. Rockbox widget does not have this problem and is what I am using. It is in early development for Android and is not available in the play store yet.
Click to expand...
Click to collapse
I'm confused, is this a question or an advertisement? If it's a question, there's a fix. If it's an advertisement, ugh.
Common problem for jellybean roms. To fix you need to edit your build prop. Change the lines "lpa.decode=true" and "lpa.use-stagefright=true". change them both so they are "lpa.decode=false" and "lpa.use-stagefright=false". Reboot. then problem should be fixed.
I would kindly accept direction to the fix. I have done searches and most results site bluetooth issues which I don't have. Not meant to be an advertisement as they are simply open source developers working on a project for porting to multiple platforms - namely mp3 players - as they have done for many years. I understand some young chaps may not have heard of these devices as they grew up with Androids.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
_INSPIREed said:
Common problem for jellybean roms. To fix you need to edit your build prop. Change the lines "lpa.decode=true" and "lpa.use-stagefright=true". change them both so they are "lpa.decode=false" and "lpa.use-stagefright=false". Reboot. then problem should be fixed.
Click to expand...
Click to collapse
Worked perfectly. Many thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
_INSPIREed said:
Common problem for jellybean roms. To fix you need to edit your build prop. Change the lines "lpa.decode=true" and "lpa.use-stagefright=true". change them both so they are "lpa.decode=false" and "lpa.use-stagefright=false". Reboot. then problem should be fixed.
Click to expand...
Click to collapse
whoa! works... why is that? What do these setting mean? And why is this not fixed in the nightlies already?
Thanks a bunch.
lowspeed said:
whoa! works... why is that? What do these setting mean? And why is this not fixed in the nightlies already?
Thanks a bunch.
Click to expand...
Click to collapse
Couldn't give you a technical reason why it works honestly. A buddy of mine explained it to me quite some time ago, but I do not remember what he said. I think it was something along the lines of making android code audio through software instead of hardware. And as to why it isn't implemented in ALL jellybean ROMS and nightlies, I have absolutely no idea. This fix may not be known to everyone, but its been available for a while & I would think most devs know about it by now and would implement it in their ROMS. I just make it a habit to do that first when I flash a jellybean ROM. :good:
So its not just me, my sd card, or my phone?? I'll try the fix out. A real pain this is when you flash roms daily and have to go through the initial freeze, close and reopen :/
Hi ! I would like to download my verizon mobile from the play store but i can't. Look at the screen shot.
Does someone know how to fix that?
Thanks!
That's because my Verizon mobile doesn't support cm
Sent from my VZW Galaxy S4 using Tapatalk 4
So is there a workaround for this?
Can no cm user have the my verizon mobile app?
LinkinParkmetre said:
So is there a workaround for this?
Can no cm user have the my verizon mobile app?
Click to expand...
Click to collapse
Try to find the following from a deodexed TW ROM:
VerizonSSO.apk
VZWAPNLib.apk
VZWAPNService.apk
Put those in /system, set permissions and try it out.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Which version of CM?
I'm running 10.1.3 and MV works fine. I was considering updating to 10.2 but I use MV to track data the three of us share.
BTW - 10.1.3 is the smoothest and glitch free version of Cyanogenmod I've ever run. Amazing piece of work.
Biggest gripe I've got is the damm google services app destroys my battery life. Can't seem to get it under control. Not CM's fault.
Used CM10.1 nightly 8/13, 10.1 RC1, and 10.2 9/5 nightly. Will all of them, I was able to install my stock verizon mobile.
Does anyone know of any ROMs or builds that qremote works while still running lollipop?
Sent from my LG-VS985 using XDA Free mobile app
TheNolandNailer said:
Does anyone know of any ROMs or builds that qremote works while still running lollipop?
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
It's possible it's not a ROM issue, but that they developer needs to update the app to work under Lollipop. I know it says on the store page that it works for 4.x or later, but usually, the devs will say in the description that ii has been updated to work under Lollipop.
Do you know for a fact that it runs under Lollipop on other devices? Just curious.
No I have never been able to run qremote on lollipop. Installs but won't run. But some one else said they Believe it worked on an earlier build of a ROM (I believe that's what he was saying.)
But yeah as far as lollipop goes it's a pretty complete build for me. I just wish I had that darn remote...
Sent from my LG-VS985 using XDA Free mobile app
TheNolandNailer said:
No I have never been able to run qremote on lollipop. Installs but won't run. But some one else said they Believe it worked on an earlier build of a ROM (I believe that's what he was saying.)
But yeah as far as lollipop goes it's a pretty complete build for me. I just wish I had that darn remote...
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Then it's an issue with the ART runtime. Under LP, ART is the default runtime, not Dalvik. The app obviously wasn't programmed to work under ART, so until the dev fixes it, it won't work under LP at all. No LP ROM has Dalvik enabled as the default. I don't even know if any of them allow switching over to Dalvik under LP. There might be some that allow it, and that might be the reason it worked for the individual you mentioned, but ART is considered the defacto standard for LP, and Dalvik is dead and buried.
You can go into the "developer options" in system settings to see if you can switch from ART to Dalvik and try that. If you don't see that option in the developer options settings, then you are stuck on ART.
What about the official lollipop released to g3s overseas, they have all the bells and whistles.