Related
Hi all,
I recently upgraded to 4.2q on my Nexus 7, and I experienced a lot of lag on it. I was browsing the Internet, and I found this on the internet which has worked well for me, and now I have no lag. I don't know if this has already been posted here.
This is what I found on the internet:
"If you’re one of the poor users experiencing major lag on your Nexus 7 after the Android 4.2 update, here’s what you can do to remedy the situation:
Open your app drawer
Open Google Currents
Click the three dots in the top right corner of the app
Tap “Settings”
Uncheck “Enable Background Sync”
Reboot your Nexus 7
That’s it. You shouldn’t experience anymore lag and you probably won’t even need to reboot. For me the difference was night and day. I went an extra step and disabled the app completely just in case. If you want to disable Google Currents for good measure, you can do so by going into your main Settings menu, clicking Apps, swiping to the All category, clicking Google Currents, and then clicking Disable. (If you do this you won’t be able to use Google Currents anymore, but at least your Nexus 7 will be back to normal."
Hope this helps.
Cheers
Corey
Sent from my Nexus 7 using Tapatalk 2
This fixed the lag issues instantly. Thanks so much!
Sent from my Nexus 7 using xda app-developers app
WOW
really? google currents is what is lagging everyone on 4.2?
thats weird , totally weird to be that reason and....totally weird easy solution, think your gonna get many thanks for this well done for the find!
still on 4.1 here cos heard of laggy issues , when i do update ill remember this though :highfive::good:
ps. might be good to let the guys in "androidforums" know too:good:
Could be why I have never seen the lag. I always have Currents sync unchecked in my Google account since I don't use it.
If this really works, it is the most representative of the issue I have with Android. How is a normal user going to monitor all apps and deduce what app or setting is causing the issue. So... does this really work or is it just imagination?
read that this morning on Drippler ... Can't believe thats the fix! haha Thats awesome
I read this on Drippler too, disabled currents background sync, and have noticed the significant improvement. Im surprised there arnt task managers to identify such a promlem. I thought these rooters and flashers could run terminal commands. No one ran ps?
Sent from my Nexus 7 using XDA Premium HD app
thx it works
This doesn't cure lag across the board, I suspect my continuing lag issues are due to having added a user.
Added account for my GF so she could see how nice jelly bean is and that iOS doesn't rule the world, and the more she's used it more laggy my use of n7 has become.
Ok I can fix by deleting it but its quite a serious issue so hope Google fix quick.
Sent from my Nexu
bkmaracas said:
This doesn't cure lag across the board, I suspect my continuing lag issues are due to having added a user.
Added account for my GF so she could see how nice jelly bean is and that iOS doesn't rule the world, and the more she's used it more laggy my use of n7 has become.
Ok I can fix by deleting it but its quite a serious issue so hope Google fix quick.
Sent from my Nexu
Click to expand...
Click to collapse
Wow, you were so lagged that you couldn't even get the "s" in 'Nexus' to register in time for your post.
phonic said:
Wow, you were so lagged that you couldn't even get the "s" in 'Nexus' to register in time for your post.
Click to expand...
Click to collapse
Hmm just a user booboo that
Sent from my Nexus 7
Question would this still work if you left it on but only sync when charging? Or does it have to be disabled completely ?
sent from my Nexus 7 while my SGS3 rests!
~~ATTENTION~~
This guide was PLAGIARIZED directly from TalkAndroid.com. You can find the ORIGINAL story here.
http://www.talkandroid.com/141899-does-your-nexus-7-lag-after-the-4-2-update-theres-a-fix-for-that/
This post should be reported and removed.Thanks.
~~ATTENTION~~
Shrew said:
~~ATTENTION~~
This guide was PLAGIARIZED directly from TalkAndroid.com. You can find the ORIGINAL story here.
http://www.talkandroid.com/141899-does-your-nexus-7-lag-after-the-4-2-update-theres-a-fix-for-that/
This post should be reported and removed.Thanks.
~~ATTENTION~~
Click to expand...
Click to collapse
How was it plagerized the OP said he found it on the internet just didn't say where. He didn't claim he came up with it himself which would be plagiarized material at that point
sent from my Nexus 7 while my SGS3 rests!
I had already frozen the damn thing and many other Google apps as they ate at my plan.
I can't stand asps that just do whatever they want whenever they want.
Sent from my Nexus 7 using xda app-developers app
AndreaCristiano said:
How was it plagerized the OP said he found it on the internet just didn't say where. He didn't claim he came up with it himself which would be plagiarized material at that point
sent from my Nexus 7 while my SGS3 rests!
Click to expand...
Click to collapse
It's plagiarized because it directly quotes a large portion of the article without citing the source.
---------- Post added at 03:32 AM ---------- Previous post was at 03:29 AM ----------
AndreaCristiano said:
How was it plagerized the OP said he found it on the internet just didn't say where. He didn't claim he came up with it himself which would be plagiarized material at that point
sent from my Nexus 7 while my SGS3 rests!
Click to expand...
Click to collapse
It's plagiarized because it directly quotes a large portion of the article without citing the source.
Edit: nice signature, by the way!
bkmaracas said:
This doesn't cure lag across the board, I suspect my continuing lag issues are due to having added a user.
Added account for my GF so she could see how nice jelly bean is and that iOS doesn't rule the world, and the more she's used it more laggy my use of n7 has become.
Ok I can fix by deleting it but its quite a serious issue so hope Google fix quick.
Sent from my Nexu
Click to expand...
Click to collapse
If you are rooted try temporarily unrooting. Root kills multiuser for me.
How to cure lag and a bevy of other stupid problems that shouldn't have made it past a 5 year old let alone `professional' paid developers.
Step 1: Don't install 4.2
Step 2: ????
Step 3: Profit
styckx said:
How to cure lag and a bevy of other stupid problems that shouldn't have made it past a 5 year old let alone `professional' paid developers.
Step 1: Don't install 4.2
Step 2: ????
Step 3: Profit
Click to expand...
Click to collapse
Grats! Least useful post I have seen on this forum.
I actually get no lag at all on my nexus 7.
Used "forever gone (SD card cleaner)" from the market after updating.
Currents sync was already disabled prior to my update. It was an issue since 4.1 that's noting new and just part of the reason for the lag.
Forever Gone fixed my lag and I'm happy.
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39892
it's pretty sad that there's only 45 votes on this issue. Here's a hint: bugs won't get fixed if people don't speak up about them. And don't think your voice exactly resonates here on XDA.
Just star it, and leave a comment. Doesn't have to be anything long winded either.
Sent from my Nexus 10 using xda premium
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Troute said:
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Click to expand...
Click to collapse
While agree it's not the end of the world, it's a complaint I see often here in kernel and ROM threads. While a lot of it is due to wonky behavior due to OC (either CPU or GPU), it's really just exacerbating an issue that is already present.
Besides, UI bugs are some of the most prevalent and immediately noticeable to more "common" end users. While functionally it's not debilitating, it's an aesthetic scar that doesn't need to be there.
Sent from my Nexus 10 using xda premium
Hmmm.. So I assume it doesn't matter that I need exactly 15 seconds everytime I get a notification to pull down the status bar, caused by flipbacks. Okay I'm like 1000% sure Google noticed it anyway, cause its on most devices, also 100% stock ones (like me) so...
Sent from my Galaxy Nexus using xda premium
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
jbdan said:
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it would bounce back after a reboot one time, I wouldn't care, but its always there, it doesn't matter what I do, it bounces every time... So its a bit annoying.. This is the only thing which sometimes makes me want to throw the 7 at a wall...
Sent from my Galaxy Nexus using xda premium
Thanks OP, have added my star.
I had not noticed this problem but I was intrigued.
I could not duplicate the problem, but I am using Apex launcher, not the stock launcher. Does the problem occur in all launchers? Also I am not using the stock ROM.
I wonder if this problem happens with only some units, or perhaps it relates to those user's expectations. Maybe they expect their device to react more quickly than it is able to.
Far be it for me to be dismissive of people's satisfaction with their devices, but that bug-report thread has a lot of problems. It contains over-reaching claims and supposed knowledge of the problem's causes and solutions.
Again, I don't write off these people's unhappiness but I personally would not star that issue.
i too have this problem when on stock rom..now on PA beta 9 with m-kernel, the problem still exist...and it's very annoying...i even thought there was a problem with my touch screen panel and sent it to asus for repair but when i got it back, the same problem still remains..
Not starring because it does not bother me.
Life has too many other issues to worry about having to occasionally re-swipe.
Now pop-up ads in the Yahoo app could get me started...
squshy 7 said:
Come on guys, with all the members here and all the people who like to complain, it's pretty sad that there's only 45 votes on this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
I noticed this issue minutes after pulling this thing out of the box, this might not bother you people who casually use their tablets, but top those of us who have been using android since the G1 notice this. It bothers me so much that I am considering taking this junk back and using the money to get a real tablet from Samsung.
This issue is so annoying to me, I not only notice it on the stock launcher, but also Nova and Apex. Now, the launcher I can deal with, but where I becomes a deal breaker for me is the browser, whether it's chrome or the stock browser in CM10. Trying to scroll around the OS that requires some flicking reminds me of trying to flick scroll on a resistive touch screen, I think that best describes the issue.
I just wanna know if it's fixable through a software update or a hardware problem, cause if it's the latter, this thing is going back, and that's too bad because it was a Santa gift, so I'll have some explaining to do.......
compact_bijou said:
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
Click to expand...
Click to collapse
As I stated (not in precise terms sorry) in the OP, it would be a mistake to think that xda threads are the first place companies like Google and Asus check to see what issues people are having. They have issue and bug trackers for a reason. The universe does not revolve around our little community.
Also, this issue pertains to the general consensus that touch screen issues (like bounce back) have become exacerbated on 4.2 and above. Not anything regarding physical QC issues (though, to be fair, may very well be the root cause, but that is an entirely different issue; the fact of the matter remains that anecdotally it appears the touchscreen responded better on 4.1.2)
And besides, I'm just looking out for the well being of this device's future. Reporting bugs on bug trackers is important to these developers.
Sent from my Nexus 10 using xda premium
to be honest, this annoys me a lot.
starred and commented.
This really annoys me as well. I voted and commented. Hopefully they can get this fixed soon. Otherwise I might switch to CM10.
Sent from my Nexus 7 using xda app-developers app
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
leonclement said:
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
Click to expand...
Click to collapse
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
farmerbb said:
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
Click to expand...
Click to collapse
Yea the notification bar is better on 4.2.2, but the launcher still does it, nova prime does it too, and even when on dolphin or boat browser sometimes when you flick it will scroll nicely & sometimes a flick wont move the page much at all, weird and annoying, would be a much better experience if it was fixed!
This is a huge issue for me. Is there a way to increase or decrease sensitivity? Maybe that would help.
Sent from my Nexus 7 using xda app-developers app
Interesting, I thought I was the only one who had noticed this. Don't know why I haven't seen this thread earlier.
For me I solved this by using apex launcher, somehow you never get those annoying jumpbacks. I tried nova launcher as well but it worked as bad as the original launcher. Going to star tomorrow.
Sent from my GT-I9300
Settings, Apps, All, Google Service Framework.
Force Stop, Clear Data.
Then check for update in About Phone.
Then repeat these steps, and the update shows up on the second check. Repeated this on 3 phones to get 4.4.2 where 4.4.1 hadn't even popped up previously.
---
Note, this procedure is to be followed at your own risk. I have completed this successfully on 3 x Nexus 5 from v4.4, however I can not test all scenarios or be responsible for any subsequent issues, whether related to this method or not. If you cant accept this, then wait for the OTA.
FunkyMagic-UK said:
Settings, Apps, All, Google Service Framework.
Force Stop, Clear Data.
Then check for update in About Phone.
Then repeat these steps, and the update shows up on the second check. Repeated this on 3 phones to get 4.4.2 where 4.4.1 hadn't even popped up previously.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
FunkyMagic-UK said:
Settings, Apps, All, Google Service Framework.
Force Stop, Clear Data.
Then check for update in About Phone.
Then repeat these steps, and the update shows up on the second check. Repeated this on 3 phones to get 4.4.2 where 4.4.1 hadn't even popped up previously.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
No. We already had a long thread about this. Please have a mod close this.
And not to sound rude - but if you're uncomfortable with sideload, you probably shouldn't have a Nexus.
I don't believe the Dan M statement is wholly accurate, given I've thoroughly checked the issues he says might arise.
I suspect it's more a case of him protecting Googles roll out schedule planning with a plausible explanation.
Not sure why someone not comfortable with sideloads shouldn't have a Nexus... it's just a regular consumer phone like any other.
Sent from my Nexus 5 using xda app-developers app
FunkyMagic-UK said:
I don't believe the Dan M statement is wholly accurate, given I've thoroughly checked the issues he says might arise.
I suspect it's more a case of him protecting Googles roll out schedule planning with a plausible explanation.
Not sure why someone not comfortable with sideloads shouldn't have a Nexus... it's just a regular consumer phone like any other.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
1. If someone who writes the code for Google tells you not to do something and gives you a list of reasons, I would suggest listening. As pointed out in the thread it can cause problems and it isn't always something you notice.
2. Because there is no danger in sideloading. It will either work or refuse to flash.
3. It's a Nexus. It's meant for that kind of thing. It's EXTREMELY easy.
4. If they aren't comfortable with sideloading, they probably wouldn't know whether or not their device had an issue after the update. They could miss out on certain features, apps not functioning properly, etc. You are essentially telling someone computer illiterate that they should do something that could potentially mess something up on their device instead of doing something that is fool-proof. That's irresponsible. Not to mention - they wouldn't even know how to fix it if it did damage anything
FunkyMagic-UK said:
I don't believe the Dan M statement is wholly accurate, given I've thoroughly checked the issues he says might arise.
I suspect it's more a case of him protecting Googles roll out schedule planning with a plausible explanation.
Not sure why someone not comfortable with sideloads shouldn't have a Nexus... it's just a regular consumer phone like any other.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
What do you mean you've thoroughly checked? You've isolated and tested the behavior of every single app that uses GCM after a framework data clear?
I mean, you are essentially accusing an Android engineer of taking to reddit to lie.. but why? Considering they have provided an officially supported method of sideloading OTA updates the idea they are "protecting roll out schedule planning" is total nonsense.
There are only 2 possible scenarios here
1) Dan Morrill is being 100% truthful
2) Instead of simply disabling the "Clear Data" button in Framework which would be dead simple, Google has chosen to send engineers to social media to spread lies and misinformation
I upgraded from 4.4 to 4.4.2 with 0 problems , if Google says don't sideload what u gonna do no side load?
Sent from my Nexus 5 using XDA Premium 4 mobile app
seriously sideload is about the easiest way to do it other than being able to download it direct to the phone and parse the sdcard like the way phones used to work... i know windows machines and that whole "driver" thing you guys need to deal with can get annoying but it's really not difficult. if you are afriad of command prompts then wait the 2 weeks or so that it takes to get it rolled out.
People spend a good amount of time on making instructional threads, gathering information all in one place, doing everything in their power to make it easy for even a complete beginner to do stuff with their phones, and we still have people wanting them to do it the harder way.
And then they defend their thinking with some ridicilous conspiracy theory that completely contradicts the very nature of how Google DEMONSTRATES that they are 100% behind people sideloading (ie: taking the all of 30 seconds it takes to do) an upate onto their phone) by implying that they have a vested interest in slowing down the number of activations?
Seriously now.
You people crack me up. Before this person from google said do not do this we ALL did it multiple time on multiple devices at least I did. No core meltdowns... yet.
remember these are the same people who thought the Nexus 5 camera was good to go as is...
crachel said:
What do you mean you've thoroughly checked? You've isolated and tested the behavior of every single app that uses GCM after a framework data clear?
I mean, you are essentially accusing an Android engineer of taking to reddit to lie.. but why? Considering they have provided an officially supported method of sideloading OTA updates the idea they are "protecting roll out schedule planning" is total nonsense.
There are only 2 possible scenarios here
1) Dan Morrill is being 100% truthful
2) Instead of simply disabling the "Clear Data" button in Framework which would be dead simple, Google has chosen to send engineers to social media to spread lies and misinformation
Click to expand...
Click to collapse
It's not worth your time trying to explain this. There are those who will always believe they are right. They will continue to ignore knowledge provided by those who are experts on the matter and believe they are right.
The most common excuse I read is "I've been doing it for so long without any issues". The technical explanation clearly states that the issues that happen are more often than not invisible to the user. Then they'll take to XDA to create a bunch of threads about "OMGZZZZ MY PHONE IS BROKEZORZ, GOOGLE IS TURNING INTO APPLE...RABBLE RABBLE RABBLE" and not even think that the issues might be related to breaking GCM in an app or similar.
Who cares if it can be bad. It can often be easier than sideloading, especially if you don't have a computer near by. I did it while waiting for my plane the other day and it was nice to have the camera improvements before I got to my destination. Just plan to do a factory reset after you get the update if it bothers you.
Not to mention, I am fairly sure whenever you install Google Apps after installing a dirty flashing an updated ROM it does the same thing as clearing data on the framework. I have certain apps I always have to reinstall or they stop getting push updates after doing that.
Tony_YYZ said:
It's not worth your time trying to explain this. There are those who will always believe they are right. They will continue to ignore knowledge provided by those who are experts on the matter and believe they are right.
The most common excuse I read is "I've been doing it for so long without any issues". The technical explanation clearly states that the issues that happen are more often than not invisible to the user. Then they'll take to XDA to create a bunch of threads about "OMGZZZZ MY PHONE IS BROKEZORZ, GOOGLE IS TURNING INTO APPLE...RABBLE RABBLE RABBLE" and not even think that the issues might be related to breaking GCM in an app or similar.
Click to expand...
Click to collapse
I don't want to progress yet another thread about this within two days, but I completely agree with your last point. I bet half of the people that do this will post on here in about a week saying their apps aren't syncing/working and "nexus 5 sucks" etc etc. I've already responded to someone who was asking about his gmail not syncing properly on 4.4.2. I asked him if he cleared the framework to get the update. Would be a great example if that's why he's having the problem.
Grims said:
Not to mention, I am fairly sure whenever you install Google Apps after installing a dirty flashing an updated ROM it does the same thing as clearing data on the framework. I have certain apps I always have to reinstall or they stop getting push updates after doing that.
Click to expand...
Click to collapse
That's not the point. He's not telling people who are familiar with these phones to do it. He's telling people who have no idea what the hell they are doing to do it.
PsychDrummer said:
I don't want to progress yet another thread about this within two days, but I completely agree with your last point. I bet half of the people that do this will post on here in about a week saying their apps aren't syncing/working and "nexus 5 sucks" etc etc. I've already responded to someone who was asking about his gmail not syncing properly on 4.4.2. I asked him if he cleared the framework to get the update. Would be a great example if that's why he's having the problem.
Click to expand...
Click to collapse
Alright, the real question here is after someone has cleared the framework, is there a way to recover or go back without restoring a backup or reflashing an OTA from scratch? Or does it just take time for Google to catch up? And DO they eventually catch up to the device? Or is it inevitably doomed once you clear. We can argue about why or why not, but lets figure out how.
Love how people jump on this guy or the one from yesterday who posted it. Been doing this on my past 4 devices. If something clears, wouldn't it be like hard resetting your device. All the information will get populated back. I also believe the engineer said there is a possibility something can go wrong. There is always the possibility something can go wrong with anything!
You can screw up your phone just taking an OOTO. People just need to let it go. We also do not know what his true intentions were for saying that.
If you do not want to clear data, then don't but don't tell others not to do it unless anyone here has experienced a problem first hand in doing so.
[email protected] said:
Love how people jump on this guy or the one from yesterday who posted it. Been doing this on my past 4 devices. If something clears, wouldn't it be like hard resetting your device. All the information will get populated back. I also believe the engineer said there is a possibility something can go wrong. There is always the possibility something can go wrong with anything!
Click to expand...
Click to collapse
It is not a question of 'if'. If you clear the services framework, Gmail notifications are 100% guaranteed to stop working for a time (could be 10 minutes, could be several days). Thankfully, Gmail is one of the few apps that will eventually realize the GCM id has changed and is able to deal with it. That is not the case for other apps.
The problem is people here don't see their phone or apps crashing and think everything is fine. But a week later they realize stuff isn't syncing or notifications aren't coming in and they blame it on the software update.
Again?? REALLY!! Google say no, like it or not they are the experts...
Sent from my Nexus 5 using XDA Premium 4 mobile app
HOXnoo8 said:
Alright, the real question here is after someone has cleared the framework, is there a way to recover or go back without restoring a backup or reflashing an OTA from scratch? Or does it just take time for Google to catch up? And DO they eventually catch up to the device? Or is it inevitably doomed once you clear. We can argue about why or why not, but lets figure out how.
Click to expand...
Click to collapse
His true intentions were to stop people from potentially messing up their phones and then ignorantly going online or on an apps review page and spouting off about how broken the app or phone is. To think differently makes no sense.
Sent from my Nexus 5 using xda app-developers app
I am stuck in boot loop with this method
Sent from **Nexus 5 signal sucks**
I've seen posts of several loving 4.4 and others going back to 4.2. Is it worth it? Battery life? Are there known bugs and issues?
Imo, its still very much subjective. As much as I've frequented here throughout the years,I would probably still be considered a noob. With that being said, here are my thoughts
Initially I was regretting the update. My battery life being terrible was my biggest gripe. I decided to root it only three days of having the stock 4.4 rom. Once I did that, my battery life levels returned to 4.2 levels. I'm getting about 15 hours off a single charge which is huge for me. Not sure if rooting actually made the difference but that's the only thing I changed after I initially made the switch.
Plus I love the new camera app which isn't offered for 4.2. I just wish Google incorporated a long press to kill apps feature. Seems like the only way you can get that is through a custom rom
Also, my screen rotation seems to be broken. It works on certain apps and not on others. It will work if I click on a video within flipboard, but not in my picture gallery. I can deal with it for a while but not too much longer
Reel E. Weird said:
Imo, its still very much subjective. As much as I've frequented here throughout the years,I would probably still be considered a noob. With that being said, here are my thoughts
Initially I was regretting the update. My battery life being terrible was my biggest gripe. I decided to root it only three days of having the stock 4.4 rom. Once I did that, my battery life levels returned to 4.2 levels. I'm getting about 15 hours off a single charge which is huge for me. Not sure if rooting actually made the difference but that's the only thing I changed after I initially made the switch.
Plus I love the new camera app which isn't offered for 4.2. I just wish Google incorporated a long press to kill apps feature. Seems like the only way you can get that is through a custom rom
Also, my screen rotation seems to be broken. It works on certain apps and not on others. It will work if I click on a video within flipboard, but not in my picture gallery. I can deal with it for a while but not too much longer
Click to expand...
Click to collapse
You may want to look into xposed framework and either wanam or gravitybox. It will give you your long press back to kill along with a while host of other features. I could never live on a stock ROM without one of those.
Sent from my SAMSUNG-SGH-I537 using XDA Premium HD app
Duckman5 said:
You may want to look into xposed framework and either wanam or gravitybox. It will give you your long press back to kill along with a while host of other features. I could never live on a stock ROM without one of those.
Sent from my SAMSUNG-SGH-I537 using XDA Premium HD app
Click to expand...
Click to collapse
Dude, you are a life saver! I was able to put it on my phone with absolutely no problems. Long press to kill is back!
You wouldn't by chance happen to know how to fix the screen rotation problem would you?
Reel E. Weird said:
Dude, you are a life saver! I was able to put it on my phone with absolutely no problems. Long press to kill is back!
You wouldn't by chance happen to know how to fix the screen rotation problem would you?
Click to expand...
Click to collapse
Honestly, no. That's really weird that it's hit or miss like that. There's a reason they pulled that update, though. I'm wondering if there's not different hardware revisions or something and 4.4.2 just works better with some than others. Only suggestion I could make is make a nandroid, do a factory reset, and see if that fixes it. If not, just restore your backup.
Did you make any other modifications or delete any system apps after rooting?
Sent from my SAMSUNG-SGH-I537 using XDA Premium HD app
Duckman5 said:
Honestly, no. That's really weird that it's hit or miss like that. There's a reason they pulled that update, though. I'm wondering if there's not different hardware revisions or something and 4.4.2 just works better with some than others. Only suggestion I could make is make a nandroid, do a factory reset, and see if that fixes it. If not, just restore your backup.
Did you make any other modifications or delete any system apps after rooting?
Sent from my SAMSUNG-SGH-I537 using XDA Premium HD app
Click to expand...
Click to collapse
I actually saw something that suggested it was related to the removal of the Samsung hub app. I could probably do a reflash but I'm Judy now getting all my settings finalized. Idk man
Reel E. Weird said:
I actually saw something that suggested it was related to the removal of the Samsung hub app. I could probably do a reflash but I'm Judy now getting all my settings finalized. Idk man
Click to expand...
Click to collapse
No idea how or why that might make a difference, but I made a backup of mine with Titanium Backup and I've attached an archive with the files in it. You can use that to reinstall it. I just froze all the stupid system apps on my phone. I figured it was safer that way. Anyway, let me know if that works. Hope it does.
hy
can anyone upload the camera app+need apps for camera from 4.4.2 ?
Duckman5 said:
No idea how or why that might make a difference, but I made a backup of mine with Titanium Backup and I've attached an archive with the files in it. You can use that to reinstall it. I just froze all the stupid system apps on my phone. I figured it was safer that way. Anyway, let me know if that works. Hope it does.
Click to expand...
Click to collapse
Damn, thanks dude
My only "issue" is that I was trying to free up some internal memory. Freezing apps doesnt get rid of them right? It just suspends them from showing up in your app tray correct?
---------- Post added at 07:50 AM ---------- Previous post was at 07:50 AM ----------
d31v1d said:
can anyone upload the camera app+need apps for camera from 4.4.2 ?
Click to expand...
Click to collapse
Why not just d/l the new google camera app from the play store? Its better (at least it is to me) than the stock camera.
Reel E. Weird said:
Damn, thanks dude
My only "issue" is that I was trying to free up some internal memory. Freezing apps doesnt get rid of them right? It just suspends them from showing up in your app tray correct?
---------- Post added at 07:50 AM ---------- Previous post was at 07:50 AM ----------
Why not just d/l the new google camera app from the play store? Its better (at least it is to me) than the stock camera.
Click to expand...
Click to collapse
System apps live on a different partition from your regular apps and so do their .dex files (for odexed roms, which stock usually is). So no, unless you need to push some apps (supersu? ) to the /system/ partition, there is no need to free up space. Just uninstall updates and freeze.
Sent from my SAMSUNG-SGH-I537 using XDA Premium HD app
Android 5.0 update causes problems http://www.bbc.co.uk/news/technology-30116319
Other than a few connection issues, I haven't noticed these issues.
Lollipop is getting some pretty bad press but overall, I think it was a great update. What do you guys think? 5.1 on the horizon?
5.0.1 will definately be on the horizon, four patches per release seems to be the norm.
Android Orca said:
Android 5.0 update causes problems http://www.bbc.co.uk/news/technology-30116319
Other than a few connection issues, I haven't noticed these issues.
Lollipop is getting some pretty bad press but overall, I think it was a great update. What do you guys think? 5.1 on the horizon?
Click to expand...
Click to collapse
If you read carefully the problems lies with the nexus 7 2012 due to the crappy nand Asus included and tegra 3.
Only issue affecting hammerhead is the lag after opening many apps. Looks like memory management is a bit borked
Has anyone cleared recents and reopened them? That's the only issue I've found
topgeardave said:
If you read carefully the problems lies with the nexus 7 2012 due to the crappy nand Asus included and tegra 3.
Only issue affecting hammerhead is the lag after opening many apps. Looks like memory management is a bit borked
Click to expand...
Click to collapse
+1
On KitKat I could opened up to 9 apps without reload the app page again.
Lollipop only up to 3-5 apps.
This is backwards. [emoji17]
So there was no WiFi issue then for nexus5
a g bell said:
So there was no WiFi issue then for nexus5
Click to expand...
Click to collapse
I think there was, and I do keep having connection issues so I'm not sure it's completely resolved. The actual WiFi issue was related to battery drainage and not connection drops. Still, you do get a sense it was rushed for the headlines/flagship launch, but it's backfiring in the press now unfortunately.
We got the memory leaks. That's the only one I am experiencing. 800MB system usages after about a day or 2. Not sure what app is triggering it.
I'm not having any issues. Wifi is fine. I took mine back to stock, took the OTA, & re-rooted. Battery is as good as KK, maybe better, but too early to tell really
I've done fresh image install. Maybe that reduces problems instead of OTA updates?
So far I'm not having any issues those are reported.
Sent from my Nexus 5 using XDA Free mobile app
a g bell said:
So there was no WiFi issue then for nexus5
Click to expand...
Click to collapse
It seems to me like there are both WiFi and Cell issues with every android update/release and the Nexus 5. Probably mostly related to different batches of hardware and user configurations however.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
sharpehenry said:
I've done fresh image install. Maybe that reduces problems instead of OTA updates?
So far I'm not having any issues those are reported.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I suspect that the case myself. It's much like doing a clean Windows install on a computer vs upgrades.
Fresh install here. Absolutely zero wifi, battery, or any other issues. Runs buttery smooth. Only thing I've noticed is more stable bluetooth connectivity. Bluetooth was sometimes flaky for me on KK.
crucialcolin said:
It seems to me like there are both WiFi and Cell issues with every android update/release and the Nexus 5. Probably mostly related to different batches of hardware and user configurations however.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
I suspect that the case myself. It's much like doing a clean Windows install on a computer vs upgrades.
Click to expand...
Click to collapse
R1R N1GHTMARE said:
Fresh install here. Absolutely zero wifi, battery, or any other issues. Runs buttery smooth. Only thing I've noticed is more stable bluetooth connectivity. Bluetooth was sometimes flaky for me on KK.
Click to expand...
Click to collapse
Yeah me too. In fact one thing I was truly worried about was battery life after seeing all the negative reports on here. I actually think that has improved as well. Even with known killer apps such as FB & Runkeeper.
DigitalUnderground said:
Has anyone cleared recents and reopened them? That's the only issue I've found
Click to expand...
Click to collapse
Yep I have had that issue reproduced too if you are talking about a mysterious process showing in recent apps. I saw on a article people reporting the package installer showing in recent apps. Although for me it shows the Android System process in recent apps. So it is an issue others are experiencing. Not a major issue, but a very weird and annoying one. You can see an article about it, and a video of it being reproduced right here.
AndroidPurity said:
Yep I have had that issue reproduced too if you are talking about a mysterious process showing in recent apps. I saw on a article people reporting the package installer showing in recent apps. Although for me it shows the Android System process in recent apps. So it is an issue others are experiencing. Not a major issue, but a very weird and annoying one. You can see an article about it, and a video of it being reproduced right here.
Click to expand...
Click to collapse
I hadn't noticed, but the package installer showed up in my recent apps earlier too. Strange.
The BBC Technology News looks to have it in for "Android" or a love of "free lunches". They have also reported on 21 Nov 'Sophisticated' Android malware hits phones - "Hundreds of thousands of Android phones have been infected with malware that uses handsets to send spam and buy event tickets in bulk." Reading the article you get plugs for 2 security firms and references back to 2012. The trojan "Notcompatible" has a great history on this site - I can find 1 thread with one post! http://forum.xda-developers.com/showthread.php?t=1633957.
I'm not having any issues. Wifi is fine. I took mine back to stock, took
the OTA, & re-rooted. Battery is as good as KK, maybe better, but too
early to tell really
no issues except no led notification after missed call. Did a fresh install using factory images
I've got memory leak issue since the second preview. After more than 20 hours use, so many apps can not run in background. Can't believe that Google didn't fix this serious issue on final release.
DigitalUnderground said:
Has anyone cleared recents and reopened them? That's the only issue I've found
Click to expand...
Click to collapse
I've also had a couple apps magically reappear after clearing everything in recents. LightFlow Lite also doesn't work well for notifications, but that's probably the apps fault. No, Lolly isn't perfect, but all new OS's go through growing pains.