Related
Whether it's a Gingerbread ROM, or just pre-rooted GB Motorola ROM, I am not stable. I get random freezes sometimes, but more often I just can't turn the screen on. It turns on, but is completely black (but you can tell it's on) and I have to do a battery pull. Liberty GB (all versions) do this as well. No GB ROM in existence is stable. I go back to .340 stock Froyo SBF or back to some other Froyo-based ROM, everything is fine. The problem never happens once.
HOW ARE YOU GUYS HAVING STABLE GINGERBREAD ON THE DX?
Ugh. Rant over. If it was a hardware problem, it'd happen at least occasionally on Froyo.
My next phone is so going to be an HTC or Samsung.
Absolutely no problems at all using Apex 2.0 RC2. Gingerbread AOSP.
No problems on prerooted GB. I was having that issue with rooted Froyo towards the end before I upgraded. It would mainly happen when I used Maps and as far as I could tell it was the GPS screwing up because when I turned off GPS my phone worked fine. I have yet to turn on GPS on GB, food for thought.
Sent from my DROIDX using XDA App
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
try cyanogen its pretty fukin awesome. only bugs so far are vieo camera and hdmi. other than that its fast n stable...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Cyph' said:
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
Click to expand...
Click to collapse
I don't think it's Win7 64bit causing the issue, I'm running it at home and work and I haven't had any issues connecting or disconnecting my phone. I would really recommend SBF'ing back to Froyo, clearing data and cache a few times, and starting with a fresh ROM. And if you have TB backing up any system data, don't restore that, just apps + data.
I love how people say they will switch to a different device manufacturer as if they expect that device to be 100% flawless.
I use prerooted GB .588 and I don't have any freezes and the random reboots stopped after I did a factory reset.
I,ve been running 596 deodexed since the first day it came out with no issues. Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Sent from my DROIDX using XDA Premium App
.596 rooted deodexed. Perfectly stable. Are you overclocked?
The only time mine froze was when I went from having it underclocked at 800 MHz to overclocking at 1.4 GHz. But I expected that to happen lol
Sent from my DROIDX using XDA App
Liberty is working great for me. I have had one freeze up since may.
Sent from my Xoom using XDA Premium App
My Verizon Droid X works great with GB. Even pushed it with Netflix and Hulu. I burn about 2200 min a month of cell time on avg. No issues.
I am running the latest DarkSlideX on my DX. It's flashed on top of TBH's 2-part 596. It's fast, stable, and has pretty good battery life, too. I had a reboot issue the first day with it, but a couple reboots and it hasn't hiccuped in over a week.
My DroidX Thrives on the DarkSlide!!
I have had about 1 of the problems you've discribed: The lockscreen blackout but that only happened once.
The problem is that you are probably deleting necessary files with Titanium backup. The crappy thing about GB is that half of the apps on the system that moto puts in there are interconnected with everything else so if you kill one app it'll make your phone die. I have never had the random freezing; but If I were you I'd delete WInzip if you have it on your phone. This is the main reason for a lot of my gingerbread issues. I now use ProPlayer: you can either get it free somewhere online, or off the market[place for like 3 bucks.
Everything is now working great.
Massgainer said:
Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Click to expand...
Click to collapse
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
BBJohnnyT said:
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
Click to expand...
Click to collapse
After SBF'ing, I've always had to (so far) wipe data and cache to stop it from bootlooping anyways, which is basically the same thing as doing a factory reset.
Roland Deschain said:
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
Click to expand...
Click to collapse
Nothing to add, just wanted to say "Hile, Gunslinger!" (just finished the audiobook version of DT 7).
Hey guys,
I installed 4.3 (stock) on my nexus and hoped that it would improve the performance but was not good at all. Then I tried paranoid Android and it still lags so bad. Do you experience the same?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nope
What do you mean about bad performance? Do you have any quantitative data or just a qualitative?
vndnguyen said:
Nope
What do you mean about bad performance? Do you have any quantitative data or just a qualitative?
Click to expand...
Click to collapse
I mean that it there are a lot of lags and sometimes the tablet doesn't respond at all...... I barely have installed any apps and I only have a few pictures on it
gsindl00 said:
I mean that it there are a lot of lags and sometimes the tablet doesn't respond at all...... I barely have installed any apps and I only have a few pictures on it
Click to expand...
Click to collapse
Then it won't be a hassle to factory reset it. I just did mine, and it's flying again, before it was laggy as hell.
Apps you remove leave stuff behind, eventually it gets cluttered, what can you do.
How many do you get in Quadrant benchmark?
Sent from my Nexus 7 using Tapatalk 4
gsindl00 said:
Hey guys,
I installed 4.3 (stock) on my nexus and hoped that it would improve the performance but was not good at all. Then I tried paranoid Android and it still lags so bad. Do you experience the same?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, gsindl00...
Jellybean 4.3 build JWR66Y (stock rooted) is running great on my Nexus 7... no lag at all.
A question... how much free space do you have left on the internal storage of your Nexus 7?
I ask because a recent experience of mine occurred that may have some bearing on your problem.
I have a 16 Gb WiFi only 'grouper' Nexus 7... but only 13.24 Gb is available to the the user.
Now, at frequent intervals I make Nandroid backups using TWRP. These backups take up significant space, routinely clocking in at around 2.5 Gb's. Due to their size, and for this reason, I only ever keep two backups on my Nexus 7 at any one time - an 'untouched, unmodified and unrooted' backup of factory stock, should I wish to quickly (for whatever reason) restore back to pure factory (without having to pull out my laptop and resort to fastboot)... this backup clocks in at around 600 Mb. This backup never gets deleted, and remains constantly on my Nexus 7.
The second Nandroid backup is a backup of my current setup, and frequently gets deleted and made anew, roughly once a month.
Several days ago, I created a new Nandroid, BUT FORGOT TO DELETE MY OLD ONE. As I have already mentioned, these backups are quite large, and with everything else on my Nexus 7 (pics, movie clips and music), this pushed my available user space down to 1.27 Gb.
This very low available user space had a significantly deleterious effect on the performance of my Nexus 7.
After booting the device, the white-on-black Google screen would appear (as normal), after which, the pulsing luminescent 'X' boot animation would then seemingly take forever to appear, and then hesitantly (as though the device was struggling to boot).
Anyway, it did boot and upon success, my widgets (I have several), would all have to reload again, which took a good half minute or so. Normally, they just appear on the Nova launcher desktop instantly. Several reboots later, and the lag and slow boot persisted, as well as the slow loading of widgets.
This peculiar behavior went on for several days... I couldn't understand it!
I was on the verge of restoring back to stock, when I remembered the undeleted Nandroid backup.
So, booting into TWRP, I deleted the old Nandroid backup, and for good measure, I wiped Cache and Dalvik cache.
Upon reboot, I discovered I had a more healthy 4.9Gb of user space available, and the lag was gone.
Anyway, my point is this (and it really has nothing to with Nandroids or TWRP)... make sure you have at least 4Gb of free space on your device. Delete stuff you don't need (or backup to your PC), and occasionally use a cache cleaner like Clean Master.
Also, if you have TWRP installed, clearing out Cache and Dalvik Cache sometimes helps.
----------------------------------
Since Jellybean 4.3, fstrim/discard has been fully implemented (it was always there in 4.2.2, but it wasn't enabled). Under 4.3, fstrim/discard now runs regularly, but only under certain conditions...
QUOTE- "The folks at AnandTech mention how TRIM will run when your tablet is idle with the screen off and sitting with a battery life of 70 percent or greater. The issue with the previous model Nexus 7 is that while TRIM support has been around since Android 4.2 — it wasn’t enabled. And regardless of how good a feature can be, if it is turned off then it will not do anything."
SOURCE -http://androidcommunity.com/nexus-7-2012-getting-performance-boost-with-android-4-3-update-20130729.
See also here for more technical and interesting info on 'fstrim'.
So, 'fstrim' is now part of Jellybean 4.3... and will run at regular intervals, providing the battery is above 70% and the Nexus 7 is 'sleeping'. But there's nothing to stop you from running 'fstrim' yourself with this app. Particularly after you've JUST deleted some really big files. You will need to be rooted of course.
Right... apologies for the length of this post... just wanted to reference my own experiences in the hope it might help.
Rgrds,
Ged.
Disable the bloatware Apps that you don't need/use like Google currents.
Throw on ASOP Browser. I believe that needs root to install, but IMHO that browser smokes Chrome.
IDK disabling bloat and using a better browser definitely changed my opinion about the N7 being slow.
Also Google around, there's different tips and tweaks to make your N7 perform better, but with those 2 tips above I saw immediate results for the better...
Sent from my GT-I9100 using xda premium
ccrows said:
Disable the bloatware Apps that you don't need/use like Google currents.
Throw on ASOP Browser. I believe that needs root to install, but IMHO that browser smokes Chrome.
IDK disabling bloat and using a better browser definitely changed my opinion about the N7 being slow.
Also Google around, there's different tips and tweaks to make your N7 perform better, but with those 2 tips above I saw immediate results for the better...
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
...throw on ASOP Browser. I believe that needs root to install...
Not anymore.... check out this thread...
AOSP browser without root.
Although on a Nexus 4 forum, I can (as can others) report it works great on the Nexus 7 as well. Only downside is, I've never been able to get Adobe Flash Player to work with it.
Rgrds,
Ged.
performance issues
Im a noob, but a CM 10.2 nightly with the latest Franco kernel, then flash the jubei test script gave me a significant boost in performance. Made the thing useable again in my book.
Try setting governor in kernel to performance. Makes a huge difference for me. I don't use my tablet enough in a day to kill it. Gets over 4 hours screen on time.
Sent from my Nexus 7 using Tapatalk 2
TLDR:
Refurbished Nexus 7(Grouper) is unnaturally sluggish no matter what I do, hope to find a solution that will speed it up just enough for reading and light internet usage.
-Overclocking helps just slightly.
-Would installing original(4.1 or 4.2) ROM make it work better or worse?
-Any ideas for a test that could find out what the problem is?(my guess is either RAM or maybe the CPU/GPU)
Full story:
I had screen discoloration on my Nexus 7 a loooong time ago, so I had it replaced by google under warranty. As soon as I got it I installed some custom ROM on it(because that's how I roll), which had sluggish performance. I figured it was due to an unstable ROM and was too lazy to do anything about it(because, that's also how I roll) for a couple of months. Since then I have tried various ROMs and they all have the same sluggishness.
I recently installed 5.0, which has such a terrible response time that it made it unusable. I was wondering if you guys can think of a way to find out the problem, or a method to speed the device up just enough to make it usable for light internet browsing and ebooks.
Mine was slow too. They did have problems with emmc. You could try running a fstrim manually and see if that helps..if not? Go back to 4.4.4, install a custom kernel like Metallice and slightly OC and make sure to run ART. Also root and greenify help a tonnnnn there as well. Good luck.
Sent from my Nexus 5 on Lollipop 5.0
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Alex338 said:
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Click to expand...
Click to collapse
That's so odd for someone on the bleeding edge to have issues. Give it time
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
dontbeweakvato said:
That's so odd for someone on the bleeding edge to have issues. Give it time
Click to expand...
Click to collapse
I'm impatient. They've had a whole day to work out the bugs
Pain-N-Panic said:
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Click to expand...
Click to collapse
Yeah Feb factory image was basically perfect for me. I don't use Bluetooth much so didn't have any of those issues. I had no issues flashing, but like I said I'm stock with no root, so no twrp to worry about. And yes we buy these phones to experiment!
Update: Had the phone completely freeze on me. First it lagged like crazy and wouldn't respond to touch, then screen went blank. Had to hold down power until finally it shut off. Seems to be fine after a reboot. I definitely never had anything like that happen since I got the phone. Hopefully it was some random one off bug!
quantumqweef said:
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
Yep I'm aware of all that. Like I said, not really a complaint, more of an observation.
After upgrading everything was nice and smooth for the first couple days but now I've hit some hard performance and lag issues especially keyboard lag. I experienced these on the developer previews on every preview so I always downgraded but this is kinda ridiculous to experience this on the official release of Nougat. Anyone else having these problems? Any fix? Clearing cache is not a workable fix, it only helps for a small amount of time say 20mins and then it's right back yo lag central. Hugely frustrating as this is my only device.
Worse than MM? I'm honestly disappointed with the performance of the device. Recommended it to my girlfriend when she had to upgrade from her iPhone, and performance is atrocious on MM. It seemed like a memory leak, because rebooting would help for a day or so, then the stuttery laggy mess comes back. It's performace pales next to my Oneplus One . I hoped the Nougat update would help fix those issues?
Ive never had any lag issues on MM or Nougat
Didn't have lag issues on MM(I'd say performance went doing after the 6.0.1 release especially in the battery dept tho.) but Nougat has been atrocious. I don't understand how mkbhd was saying he had no problems with developer preview or 7.0 because its apparent after a day of use. I've rebooted my phone like 5 times so far tonight clearing my cache each time and sure enough an hour or more later it's right back to lag town. I will say it's gotten better since dev preview 5 but it's still too bad for daily driver. Who the actual **** is working on the Android team at Google? This has been reported and known since preview 1 and yet it seems to never be addressed
Lately Google's quality of work seems to be: ¯\_(?)_/¯
Yeah, I'm seeing bad intermittent lag and stutter on 7. I also saw it on 6. 0.1 though. It may just be a hardware issue with the rubbish 810?
Sent from my Nexus 6P using Tapatalk
7.1??
shanxybeast said:
7.1??
Click to expand...
Click to collapse
He didn't say seven dot one (7.1), he said seven period space (capital) eye (7. I).
So here's something interesting, after I uninstalled screenwise panel I haven't been experiencing the keyboard and performance lag
No lag here on stock unrooted nougat. Has to be a third party app. Battery life has been a unicorn on nougat I must say. When the phone dirty flashed nougat over marshmallow i had terrible battery life. Lost 25% precent in just two hours! Factory reset cleared that up so o thought. This morning after leaving the house and the charger, phone felt slightly warm on hostler. Checked it and sure enough, down to 80% in 2 hours. Rebooted and problem was gone. I hope i don't have to reboot every day to get good battery life. I believe this is not the same update Google will push to non beta members. Hopefully the "release" version will have these things sorted out.
Sent from my Nexus 6P using XDA-Developers mobile app
The 7.0 pushed to the beta users is the same release version, there aren't two different Roms. Also while uninstalling screenwise panel seems to have cleared up the majority of the lag, there is still Ram Memory problems and slight stuttering
Factory data reset after EVERY MAJOR ANDROID UPDATE. If you haven't, you need to do that. After an update a lot of the time the temp and backup files aren't erased after the update and they can lead to performance issues. Especially on a new device you should not see any lag on the 6P on MM or Nougat.
In fact, I have seen my 6P even smoother and snappier on N over MM.
I never experienced any kind off issues on MM was very happy with the performance. Now that I have taking the Full OTA update to 7 I can tell a big difference in battery life and it's amazing. 7 has been running very smooth and buttery for me. But I've noticed that a lot of people that moved to 7 never factory reset their phone BC of losing data n such and most of them seem to be having a bad experience.
Soon as 7 booted after the update I then went in to stock recovery and factory reset the phone then went through the set up installed all my apps then flashed TWRP 3.0.2.1 then made a backup of r he stock ROM. Then flashed superuserUpdate 2.76 booted the phone and restored all app data via Titanium backup ran for a few days to make sure no issues was going to pop up then made another backup.
Currently I'm 7 all stock with stock kernel and root. The only mod I flashed was the soft key swap.
And during the wipe n stock recovery I wiped the internal storage also..
But hope you get it figured out man BC it's really worth the move..
Sent from my Nexus 6P using Tapatalk
Eric214 said:
Factory data reset after EVERY MAJOR ANDROID UPDATE. If you haven't, you need to do that. After an update a lot of the time the temp and backup files aren't erased after the update and they can lead to performance issues. Especially on a new device you should not see any lag on the 6P on MM or Nougat.
In fact, I have seen my 6P even smoother and snappier on N over MM.
Click to expand...
Click to collapse
why not just download a free app like cc cleaner that can get rid of files like those?
My 6P started acting weird the last 4 days. Apps will freeze then the pop up says app not responding close it or wait. Also the screen will not turn on when I hit the power button or use the fingerprint reader. I have to hit it many times before it comes on. I have booted into safe mode and still have the problem. I was running Preview 5 so my phone updated to 7.0 stable the day it was released. Everything was running smooth until Saturday night. Now it is about useless. Im hoping someone has a recommendation other than factory reset but I'm afraid that is going to be my only hope. Just don't want to waste another day setting this thing back up.