[Q] Gnex lag/wifi problem. - Samsung Galaxy Nexus

Hello.
Recently I've upgraded my Android version to 4.2.1 on my Gnex and since then I've experienced many problems regarding Wi-Fi and lag. The problem with the Wi-Fi is that looses connectivity when in standby even if the rooter has no problem. There are some times when I loose Wi-Fi connectivity even when I use my phone. On the other hand, it became laggy, taking forever to open an application.
My question is: what would you suggest me to make my phone better/faster? hard-factory-resetting my phone, or installing a new version of Android, with custom ROMs and other things?
I am new to this community and I don't really know how to reset my phone to the factory Android version.
Thank you.

From my understanding, there isn't a fix. I have a Gnexus on 4.2.2 and get the same issue a lot.
My belief is its a problem with jb itself

To fix the slowness, either update to 4.3 or install this app https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix and run it regularly.
If you read this article you'll understand the issue: http://www.androidcentral.com/nexus-devices-updated-android-43-will-now-have-trim

Thank's
rafa1696 said:
To fix the slowness, either update to 4.3 or install this app and run it regularly.
If you read this article you'll understand the issue:
Click to expand...
Click to collapse
Thank you very much for your advice.
Using efrant's excellent guide, I've managed to update my Android to 4.3 and rooted it.
Recently I've seen the Paranoid Android custom ROM, and I really liked it. What I wanted to ask you: is it good? I mean, when it comes to device's speed, extra options, etc.
I really wanted to install that ROM, but from what I've seen from their thread, in the matter of installation, it's kinda blurry.
Help?

Bump?
Bump?

Lestat2308 said:
Thank you very much for your advice.
Using efrant's excellent guide, I've managed to update my Android to 4.3 and rooted it.
Recently I've seen the Paranoid Android custom ROM, and I really liked it. What I wanted to ask you: is it good? I mean, when it comes to device's speed, extra options, etc.
I really wanted to install that ROM, but from what I've seen from their thread, in the matter of installation, it's kinda blurry.
Help?
Click to expand...
Click to collapse
Paranoid Android is still in its early 4.3 development stages so it will have bugs and hiccups. I flashed it and noticed it's not up to speed as stock 4.3 so I reverted. If you don't mind the bugs and hiccups, go for it.
As for flashing it:
-Be on the latest TWRP or CWM recovery
-Wipe everything (Factory reset, cache, dalvik)
-Install ROM and then install the PA GAPPS
-Reboot

TA
DroidOnRoids said:
Paranoid Android is still in its early 4.3 development stages so it will have bugs and hiccups. I flashed it and noticed it's not up to speed as stock 4.3 so I reverted. If you don't mind the bugs and hiccups, go for it.
As for flashing it:
-Be on the latest TWRP or CWM recovery
-Wipe everything (Factory reset, cache, dalvik)
-Install ROM and then install the PA GAPPS
-Reboot
Click to expand...
Click to collapse
Thank you very much for your advice. Well then, I guess I'll wait for PA to be "applied" for 4.3.

Try Fancy or Golden kernel.
Sent from my Galaxy Nexus using Tapatalk 4

Problem
Hi. I have a new "problem" with my Gnex.
From the past few days a notification came, which tells me to update to Android 4.3, even though I have installed it few weeks ago. It won't dissapear, no matter what I do.
Should I update to their "version", or should I ignore it?
LE: The battery started to drain reaaaaaaaaally fast.

Bump?
Bump?

It is fix for a security issue, and it stays on 4.3. You can just disable notifications for the app which checks for updates(I forgot the name of it).
Sent from my Galaxy Nexus using xda app-developers app

Related

[Q] Lockscreen slide + Pattern, etc. in JB

I switched over to jelly bean almost a soon as it became available without doing a wipe and noticed that the first time I started my phone, it presented me with the slide Lockscreen followed by my actual pattern Lockscreen, which I remember was an option on CM9. However, when I go to the security options in JB, I can't replicate that initial behavior (Slide -> pattern). Does anyone know if this is possible somehow in JB, out will I have to wait for ROMs to bring that feature?
Sent from my Galaxy Nexus using Tapatalk 2
LMAO.
That just means you didn't wipe your data...so your previous settings attempted to merge over.
This will cause MUCH more than the little bug that you noticed.
You're going to see FC's...reboots...etc.
Look into properly installing a rom.
Especially when moving from one version of android to another.
Post two in my guide has info on doing so.
Wow. Android 4.0.4 custom rom --> Android 4.1 different custom rom with no wiping whatsoever? You are very brave OP! I could never do that (or deal with the possible consequences that may occur).
Jubakuba said:
LMAO.
That just means you didn't wipe your data...so your previous settings attempted to merge over.
This will cause MUCH more than the little bug that you noticed.
You're going to see FC's...reboots...etc.
Look into properly installing a rom.
Especially when moving from one version of android to another.
Post two in my guide has info on doing so.
Click to expand...
Click to collapse
LMAO
only I wiped to stock 4.0.4 before moving to Jellybean. nice assumptions there. Go patronize someone else. I've had Jellybean since the day it became available, and I haven't had one problem, thank you very much.
So, can anyone with a legitimate answer chime in?
Features from custom ROMs do not transfer over. When the JB source is released, CM10 will probably have the feature, for now you will have to do with stock JB features.
InvalidUsername said:
LMAO
only I wiped to stock 4.0.4 before moving to Jellybean. nice assumptions there. Go patronize someone else. I've had Jellybean since the day it became available, and I haven't had one problem, thank you very much.
Click to expand...
Click to collapse
You didn't wipe completely or properly if you were prompted for your PIN on a "fresh" install of a ROM.
I'm not sure he really did anything wrong. I came from a stock ICS (4.0.4) ROM as well and went straight to JB (4.1.1) and experienced the same thing just a few minutes ago. I got super excited thinking that I had the slide > pattern back without having to use a custom ROM.
Device: GSM GNEX (from google play), flashed XXLF1 baseband and XXLF1 (JB, 4.1.1) RIL using GetRIL. Unlocked and Rooted per the instructions in this thread.
ICS ROM I was running downloaded from; https://developers.google.com/android/nexus/images#takju
JB ROM I am currently running from downloaded from; http://forum.xda-developers.com/showpost.php?p=20843237 (takju JRO03C from IMM76I)
Per the instructions from efrant's 1st post here, a wipe is not required if coming from a stock ROM. Which apparently is functioning fine for both the OP and myself. I suppose it's too soon to really say I won't have an issue since I performed the upgrade so recently, but based on efrant's post with instructions I don't foresee any issues.

Phone stuck on app optimization

Hi guys, i swear i searched! for like days! i still haven't found out how to solve this issue. problem started when i tried hellybean a few weeks back, and then i heard someone on the thread said to try and use the latest beta uber kernel at the time, and i did. What end up happening was that my hardware keys are dead, the lights still works but very dim, i think this is because of the swipe to wake thing where it leaves your hardware keys on 24/7 as long as the phone is on, which is not that bad because i'm now used to using the nav bar. but the real problem is that now every time I install a rom that is not JB 4.1 (haven't tried 4.2 though) i.e. 4.3, 4.3.1, it gets stuck at the app optimization screen, it would go about half way through optimizing the apps, and then just reboots itself, and it'll do that over and over, like boot loop but it can actually go into the rom. So i think this is not as bad as a situation as soft bricking or hard brick, but i just really don't know what the heck is going on to even try and fix it. I've tried odin, thinking that there may be something wrong in the boot file, nada, factory reset, nada, the only thing that worked was installing the 4.1 roms, i think it is because the 4.1 roms don't require app optimization.
If anything maybe anyone out there can help me find a way to disable app optimization? maybe that'll let me get into the rom.
btw, i dont really mind using 4.1, but i really want to try the jedi rom, but having my hardware buttons dead and jedi rom being TW and it doesn't seem to have a nav bar make it impossible for me to use the rom, so i've only been able to use cyanogen 4.1, which are great but they are pretty outdated, so if there are anyway to fix that, lmk too.
Anyways, any help would be appreciated thanks a ton guys! sry for essay!
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
krazierokz said:
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
Click to expand...
Click to collapse
Lol actually the problem started when I was on 4.3, and then upgraded to 4.3.1 helly bean, in which i tried to use the beta uber kernel, that was when the problem started. So the only roms that allows me to get pass the optimization screen were the 4.1.2 roms, which were TW, pananroid, like i tried a bunch, like super old ones, they all worked, just that when i try to get any rom higher than 4.1.2, it keep going back to that. And yeah when i tried to upgrade from jedi to aosp, to tried using infamous cache and it didnt work :/ because i've heard that's what would fix it... and lastly, Im using twrp 6.1 i think, not the latest one.
Thanks alot for the reply!
PS. I see you running slimbean 4.2.2, how is it? any probs? maybe i can try a 4.2.2 if this doesn't work out, i havn't been able to get any 4.2.2 roms cause the links are all dead, so idk if i'll have problems with 4.2.2. if there's anyway you can link it for me that'll be great! thanks!
PSS: also i've tried odin, but idk if that actually wipes everything, i'm having a feeling that it might be a script problem or something because it goes into the rom once, but it just refused to work and after like 10 seconds it reboots.
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
krazierokz said:
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
Click to expand...
Click to collapse
Ey thanks for the reply, ok so first, I did not try to restore any apps or system apps, I even odin so everything were wiped cleaned. So really dont know whats going on. After I updated to a newer hellybean, not newest by now, and a beta uber kernel, this happens. I see two other people having the same problem too. Also I tried to use 4.2.2 roms, did not work
Anyways any insight would be apreciated!
Thanks!
One more thing, I tried twrp 2.6.1.0 to flash as reccomended by all devs and still no results. :/
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
krazierokz said:
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
Click to expand...
Click to collapse
oh well, thanks for the reply then, im trying 4.4, hopefully it'll help... somehow... lmao idk haha

Who's Still Running JB 4.3 On Their N7??

So I'm new to Android and the Nexus 7. I come from the world of iOS. After thinking and thinking then buying a ipad mR then having buyer's remorse because of the price I found the N7 2 at the beginning of the month and was pretty happy with it. The day I took it home it upgraded to 4.4 before I knew what happened. I quickly found a couple of my favorite apps didn't work with 4.4 (then later found that some privacy features I'm very use to in iOS where not accessible) I started reading and proceeded to learn how to unlock the bootloader and sideload stock 4.3 (I hope I used the term sideloading properly). I've been running that for a while and for the most part I love the tablet. I've seen some of those apps have now updated for 4.4 support and I'm considering sideloading 4.4 stock, (I know 4.4.2 is out there but until Google gets with it and gives users the type of privacy control iOS does I'm not willing to move past code that doesn't give me app ops in some form or fashion). For those still on 4.3 tell me why you're still on JB. I'm not looking to start a new flame thread but looking to get good insightful information to help me make my mind up. Thanks.
Sent from my Nexus 7 using Tapatalk 4
Android has several app ops launchers, like this one: https://play.google.com/store/apps/details?id=com.findsdk.apppermission
You can find them by searching "app ops" on the Play store.
4.4 was a pretty major upgrade, which is why some apps didn't work with it right away.
I don't think any of the app ops launchers work with 4.2.2 as Google has stripped that functionality out of 4.2.2 is what I've read. The question really is do I stay on 4.3 or upgrade to 4.4 now that a few of my legacy apps are supported now. If your answer is no, why. I'm looking for those that have decided to stay on 4.3 and why.
Sent from my Nexus 7 using Tapatalk 4
I'm still on 4.3 because I'm running on Paranoid Android; and their 4.4 ROM isn't out yet. You could tell me to use the unofficial 4.4 AOSPA , but I'd have to clean wipe everything, and I don't really want to.
So here I am, waiting desperately for the official Paranoid Android 4.0 build
This one just was updated to work with 4.4.2, it installs itself into system and works fine.
https://play.google.com/store/apps/details?id=com.findsdk.apppermission&hl=en
Requires root, of course.
I was thinking of going back to jb just for the flash videos i miss some of my fave porn site
LoVeRice said:
I was thinking of going back to jb just for the flash videos i miss some of my fave porn site
Click to expand...
Click to collapse
Dolphin+Jetpack+Modified Flash APK works fine.
Video to explain how: http://www.youtube.com/watch?v=luxqwoxYzxw (NOTE: Jetpack now installs alongside Dolphin automatically for KitKat devices automatically now)
The only reason I'm still running 4.3 is because there are a couple of features that I really like with aokp, so I'm just going hold on and a little longer for a 4.4.2 release from them...
Sent from my Nexus 7
im on omni 4.4.2, but am going back to stock jb because the battery life is better.
Still running 4.3 as not had update sent through to n7 2, device says its up to date and was last checked 19 Nov even though I press check for up dates. Am keenly reading up to see if its worth moving to 4.4 if it ever comes through.
Stuck
I'm still on 4.3 because I can't get off of it. I rooted several weeks ago without a problem, installed TWRP, and when the new updates started rolling out I unrooted. The update always looks like its going to work, all the way up to rebooting only to find that nothing has changed. Many update attempts later, and because I couldn't think of anything else to try, I have tried to restore to stock, factory reset, etc. and nothing changes. Still on 4.3 no matter what!
heliosue said:
I'm still on 4.3 because I can't get off of it. I rooted several weeks ago without a problem, installed TWRP, and when the new updates started rolling out I unrooted. The update always looks like its going to work, all the way up to rebooting only to find that nothing has changed. Many update attempts later, and because I couldn't think of anything else to try, I have tried to restore to stock, factory reset, etc. and nothing changes. Still on 4.3 no matter what!
Click to expand...
Click to collapse
Try using fastboot to unlock, then wipe the cache, system and userdata partitions. Then there's no reason the stock image's flash-all.bat shouldn't work.
Well update has come through and waiting my install, so the question is do I install it, is the recommendation to install it or not.
Finally
Pandae said:
Try using fastboot to unlock, then wipe the cache, system and userdata partitions. Then there's no reason the stock image's flash-all.bat shouldn't work.
Click to expand...
Click to collapse
Thanks for the advice. I tried lots of strategies, and ultimately, I'm not at all sure what I did, but somehow managed to get the Nexus 7 updated. I sure hope nobody wants me to explain how to do it. because I have no idea.
Thanks again.
As long as something worked, short of hitting it with a sledgehammer!
Pandae said:
As long as something worked, short of hitting it with a sledgehammer!
Click to expand...
Click to collapse
Same technique I had to use on the 3 Nexus 7 2013's I returned and that was just to touch an icon
Sent from my Nexus 7 using xda app-developers app

[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)

[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.
Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.
Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.
aaa
nothing
I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me
This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.
Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.
Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.
Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!
Q
Is the camera fixed yet?
Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.
I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.

[Q] Is there a stable version of Cyanogenmod for Xperia M?

Sorry if i make any errors or mistakes. I just spent the last 20 minutes on creating this thread and in the end, made me login again and guess what - everything i typed went away.
My phone is sony Xperia M C1904 single sim, running android 4.3 stock(latest).
This is the first time i am rooting.
I am doing it because
1) Low free space thanks to Sony's bloatware.
2) Expected them to atleast give Kitkat as they were supposed to.
3) Need app to sd
I need a stable version of cyanogenmod for my phone.
Does updating work like normal? Like, do i just use update center and download the new version updates(like perform all steps and install once, then use as usual), or do i have to flash again and again?
Is there any feature that i won't be able to use? It will only be better right?
Can the process be done on the phone itself via sd card after downloading everything necesary, or do i have to install/flash it while connected to pc?
Please explain in detail.
1. stable CM12 yet to be released, please go to cyanogenmod site and look for device Nicki
2. from my personal exp. updating work like normal update. you need to enable root and other feature from setting.
3. i am using link2sd and successfully managed to cap the space <800 MB. currently 1.2+GB is free on my XMS.
4. only thing i hate, after update you need to grant access to link2sd so that your app can comes back.
5. you can check change log in cm site for each nightly, i.e. 12-20150322 nightly has an issue on mobile network check/uncheck while using wifi.
6. you need to flash cm12 and gapps on each update.
debaxish said:
1. stable CM12 yet to be released, please go to cyanogenmod site and look for device Nicki
2. from my personal exp. updating work like normal update. you need to enable root and other feature from setting.
3. i am using link2sd and successfully managed to cap the space <800 MB. currently 1.2+GB is free on my XMS.
4. only thing i hate, after update you need to grant access to link2sd so that your app can comes back.
5. you can check change log in cm site for each nightly, i.e. 12-20150322 nightly has an issue on mobile network check/uncheck while using wifi.
6. you need to flash cm12 and gapps on each update.
Click to expand...
Click to collapse
How about stable CM11?
debaxish said:
1. stable CM12 yet to be released, please go to cyanogenmod site and look for device Nicki
2. from my personal exp. updating work like normal update. you need to enable root and other feature from setting.
3. i am using link2sd and successfully managed to cap the space <800 MB. currently 1.2+GB is free on my XMS.
4. only thing i hate, after update you need to grant access to link2sd so that your app can comes back.
5. you can check change log in cm site for each nightly, i.e. 12-20150322 nightly has an issue on mobile network check/uncheck while using wifi.
6. you need to flash cm12 and gapps on each update.
Click to expand...
Click to collapse
I can't get link2sd working on cm12, any advice? guide may be? What type of partition? I have FAT32.
Georgepaul said:
How about stable CM11?
Click to expand...
Click to collapse
CM11 seems to be quite stable.
Sometimes Google Play Services crash but it got better after I switched from dalvik cache to art. If you reboot your phone once or twice a week CM11 works great.
Battery life on the other side is really bad compared to stock 4.3 rom. (On Stock Rom I had to charge every 5 days, with CM11 every 2)
There are no updates for CM11 anymore, so no need for that.
If you want something that just works, go for CM11 and wait until CM12 gets a final realease. Otherwise you have to deal with bugs, even worse battery life and flash your stuff again after an update.
xa.fr said:
CM11 seems to be quite stable.
Sometimes Google Play Services crash but it got better after I switched from dalvik cache to art. If you reboot your phone once or twice a week CM11 works great.
Battery life on the other side is really bad compared to stock 4.3 rom. (On Stock Rom I had to charge every 5 days, with CM11 every 2)
There are no updates for CM11 anymore, so no need for that.
If you want something that just works, go for CM11 and wait until CM12 gets a final realease. Otherwise you have to deal with bugs, even worse battery life and flash your stuff again after an update.
Click to expand...
Click to collapse
to fix google play services just type in terminal:
Code:
su
pm disable com.google.android.gms/com.google.android.gms.droidguard.DroidGuardService
I don't see any battery life difference beetwen 4.3, 4.4.4 aosp, cm11 and cm12
btw it's preatty old thread
iks8 said:
Code:
su
pm disable com.google.android.gms/com.google.android.gms.droidguard.DroidGuardService
Click to expand...
Click to collapse
Thanks, but what exactly does this disable? No idea what DroidGuardService is and how it is needed....
Are you using your phone a lot of times during the day? If yes, there is not much difference for me either.
But often times during a busy week at work I barely use it and in this situations stock did last way longer than CM11.
xa.fr said:
Thanks, but what exactly does this disable? No idea what DroidGuardService is and how it is needed....
Are you using your phone a lot of times during the day? If yes, there is not much difference for me either.
But often times during a busy week at work I barely use it and in this situations stock did last way longer than CM11.
Click to expand...
Click to collapse
I don't know, it's Boonobo's guide but I think it's safe to discable since it's not working properly anyway. Yes, I use my phone a lot.
Okay, thanks. Do you have a link to your mentioned guide or something?
no, it's some old post and I don't know where it is, anyway I'm using this on my phone and I don't see any difference (except no fc ofc)
iks8 said:
no, it's some old post and I don't know where it is, anyway I'm using this on my phone and I don't see any difference (except no fc ofc)
Click to expand...
Click to collapse
So my experience so far. If you disable this, most apps can't get your location over Wifi anymore or if they do, it is not really exact.
Had some Llama rules with Wifi which are not working anymore and my weather app can't find my location when connected to Wifi.
Had to enable it again...
xa.fr said:
CM11 seems to be quite stable.
Sometimes Google Play Services crash but it got better after I switched from dalvik cache to art. If you reboot your phone once or twice a week CM11 works great.
Battery life on the other side is really bad compared to stock 4.3 rom. (On Stock Rom I had to charge every 5 days, with CM11 every 2)
There are no updates for CM11 anymore, so no need for that.
If you want something that just works, go for CM11 and wait until CM12 gets a final realease. Otherwise you have to deal with bugs, even worse battery life and flash your stuff again after an update.
Click to expand...
Click to collapse
about "red line"
for me just go to setting, apps, google play services, uninstall update. it's work fine for me

Categories

Resources