Related
so I flashed the Nexus Rom as well as the newly updated 3.8 version with the battery % feature flashed on my phone. The entire procedure was done as instructed (restore/clear 3+ times on everything as instructed) and I waited well over 10 minutes upon a reboot. So all is set and almost everything is working flawlessly.
There are few issues, however, which I'm curious to know if I'm the only one experiencing this:
1. Battery Drain: Fully Charged at 100%, unplugged the cable at 6AM this morning. The phone has been on its battery power for roughly 7.5 hours now handling a total of 5 minutes of calls, roughly 30 text messages, 5 minutes of non-wifi internet usage, email is being pushed, and flashed 3.8. My display is set slightly below the mid section and I have zero widgets on my main screen except for the search bar. A total of 6 icons on my menu and that's it (only 1 page). My battery is at 40% right now. It's only been a day since I've had this flash and I just flashed on the 3.8 just few minutes ago.
2. From the Status Bar pull down menu, Shutdown and Reboot, Recovery option would hang and freeze the phone until I pull out the battery. I can only enter the Recovery mode manually by holding both +/- volume, power on, and releasing both once the 'samsung' logo appears.
3. Mobile HotSpot freezes for good 1-2 minutes. I cannot use my phone as a Hotspot at the moment.
I absolutely love the Nexus Rom from the looks, performance, looks to looks, but few of the glitches I've mentioned are quite irritating. If I'm the only person experiencing this, I'd want to continue on the search to remedy this issue. Please share some experience, ideas, or resolution if you have any!
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
icenight89 said:
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
Click to expand...
Click to collapse
Thanks for the input. I wish the battery life was better. I'll let it sink in for a few days to see if it'll improve. If not, I'll just have to keep searching for a rom with a better battery life. I've tried Beastmod, Juggnaut and many others which have yet to last for over 12 hours.
I read that the hotspot issue was fixed and with the 3.8 update, I presumed it to be completely polished. The shutdown bug, I can live with - hoping there's an upcoming fix in the works.
This ROM is the sickest looking ROM I've tried so far. I wouldn't call it the smoothest due to it's intermittent force closures and freezes, but when things improve down the road, I think this one will stay on my phone for awhile!
I've been using this rom for about a week and the battery has been working great, better than any stock rom I've had. I'll unplug it in the morning around 745 and it'll last until I go to bed around 11.
Sent from my SAMSUNG-SGH-T989 using xda premium
You should try Mr X' s tweaked Telus stock ROM. This ROM has the best battery life among T989 ROMs period. It is Canadian but works great on T-mobile network. It also does not have much bloatwares as T mobiles stock one. Just Make sure you have wifi sharing, wifi sharing manager and social hub frozen through titanium backup.
As for wireless hotspot, the stock one from Telus works well.
I get about 16 hours use. It may vary for you but battery lasts longest with this ROM.
Sent from my SGH-T989D using XDA
I am seeing battery life, signal, speed, camera and wifi calling issues everywhere!
Is this in the official update from TMO as well as the ROM's that are popping up in the Dev section also? Did Samsung/TMO release a flakey ICS?
I am kind of worried and staying on GB at the moment...
I have noticed a definite decrease in battery life as well as
When listening to stock music player, if you get a text the sound goes to full volume which is quite annoying.
Randomly freezes for 5-10 seconds at a time.
Seems a bit laggy transitioning from program to program.
had to uninstall gosms, private box stopped working and for some reason would no longer vibrate on silent.
I suppose there will probably be an update at some point to fix some of these issues. not too worried, phone still kicks ass
I just recieved my S II today, and promply updated it to ICS. Everything is smooth, and I'll comment on battery life tonight.
Quadrant:
3776
It was really bad for me after about 2 hours after updating Tuesday when it released. That was the stock/unrooted GB update to the last update prior, then updated to ICS on Tuesday.
Since then I completely wiped everything, even used tdj's superwipe, reflashed stock and after that the only update kies had for me was the actual ICS bits.
Since flashing that last night it's settled down much better than Tuesday night. Battery seems to have stabilized and I'm pretty much running *everything*.
What will seriously shut down the battery drain is enabling the System Powersaving or whatever under the powersaving menu in settings.
It really makes the phone chop but if you're out and about or somehow away from a charge whatever it does really does save battery lol. It warns you the phone will mostly suck if you enable it but kinda interesting.
With the wallpaper changes, removal of some of the classic AOSP animation stuff etc. - I can only think T-Mobile is really paranoid of having people complaining about choppy phones so are in an under-the-table kind of way turning stuff off for you.
I'd rather decide that myself but that's why I'm here at XDA
i think the update have quite a few problem
sometime it freeze on text message,also don't show keyboard or laggy
Exactly! How can they release this with these critical issues?! Don't they have a QA team?
Now that ics has been out for a while, is it a good idea to have this on?
It does make the phone faster and only affects two of my apps but i still dont know how does it affect battery or RAM(i read somewhere it affects ram)
Do you guys use it?
Sent from my Galaxy Nexus
It's useful for scrolling in 2d apps. Although on xda makes the pictures not come up. I only use every once in a while.
Sent From My Sprint Galaxy Nexus
I've chosen to not use it. It was useful in the early days when not a lot of apps worked well on ICS, but nowadays it breaks more than it fixes in my experiences.
I don't use it. I find it makes many apps laggy. Though it does boost a quadrant score.
In theory, it would be better to the let the GPU render stuff as it takes the strain off the CPU. Too bad it breaks many apps, though.
nope dont use it. does more problems than good
I use it, never encountered any of this, EXCEPT for a GUI glitch in Power amp. Besides that, every works perfectly.
On side note, back when the Samsung Vibrant first got ICS (somewhere around December), I found that many apps just crashed when using it, such as trying to pick out a wallpaper in GO SMS. Nowadays, nothing besides that Power amp glitch I've noticed. And battery life is somewhat better too.
Sent from my Galaxy Nexus using Tapatalk 2
The United Airlines app used to have problems when this was on -- would show up as an incredibly tiny rectangle on the screen, as if scaling was totally thrown off. I was flying a lot then, so I unchecked the option. The United app has been updated a few times in the past few months, and I tried checking force GPU, and the latest version of the United app works again... I've got 104 apps installed, and the only other one I've seen that complains is Flipboard -- got a message once, yesterday, that it's not designed to work with forced GPU and that I should turn it off. I ignored the message, though, and Flipboard seems fine -- as does everything else I'm using.
I'll leave it turned on until / unless I run into incompatibilities with apps that I find important...
In the interest of making things easy for those who are holding off on the KitKat OTA, I thought it might be a good idea to consolidate all of our experiences into one thread. This is intended to cover mainly the changes specific to this OTA over Razr M-flavored Jellybean.
I'll start with my experience/thoughts and edit in additional findings. (Note: I'm bootloader locked, and now unrooted.)
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
My opinion, overall:
It's a nice upgrade, but all of little problems I've encountered (bugs, Verizon blockades, the works) make this feel like a bit of a letdown after the 6-month wait. In the end, after just three days, I find myself wishing I could take the phone back to Jellybean.
Here's hoping for either some exploitable holes or maintenance updates.
My opinion
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
Worth noting that I am using an unlocked bootloader, with CWM and SuperSU (only really did this to remove VZW bloat and install Xposed)
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to show more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
ATTACK said:
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to so more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
Click to expand...
Click to collapse
Gonna be doing some more testing in that regard. Even my M7 with its garbage radios gets LTE just about everywhere in the Metro Detroit area.
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
I have had the KitKat OTA now for 2 days and haven't found anything major wrong. The changes to the keyboard bugged me but I use swiftkey so that was moot. I also have an issue I haven't seen listed yet. The new sound for screen taps....it seems to give that "popping" feedback (that ive seen listed as an issue on driver start-up) ALL the time. I maybe get 1 clear sound out of every 5-6 screen taps. That is the only real "problem" I can find as of this point though. Does anyone have any insight on that?
Also activated Dev Mode and changed to ART runtime. Might be placebo but app response seems to be noticeably better! Not groundbreaking by any means but better than 4.1.2 for sure. Overall I am happy with the upgrade. Rather, will be happy once a root exploit comes up (I miss my debloating! On that note though, disabling apps never seemed to work right with 4.1.2....after hitting disable the app would show back up in active processes after a short time. Now I've gone 24 hours and 3 phone reboots and that damn NFL app is STILL disabled and NOT running as a background process. Might just have been an issue with my phone in particular before, but its fixed now!)
I am generally happy.
It fixed all the issues I had with Dhackers KitKat.
and feels about the same once you have rid of all the Bloat.
I like and I am happy that we still surprisingly got the update unlike the Galaxy S3
Happy =)
Just wanted to comment on the heat issue mentioned above:
I have only had KitKat for 2 days but I have definitely noticed a difference in heat after extended use compared to JB. One of the things I really liked about my Razr M was lack of heat so hopefully this is a fluke and I wont notice it too much in the future.
---
With that said, no big issues.
I don't like the keyboard -seems smaller, or something, The heptic feedback seems to be different too (for the worse IMO).
The lockscreen number pad seems smaller - definitely liked the number pad from JB.
I had to change the messaging app (hated the all white/lack of contrast). Using "8sms" if anyone is curious.
I also changed launchers to use the google-now launcher so the "okay google" thing would work on the homescreen and also get the transparency notification bar. But, in doing that I did lose the circle widgets which I liked. Can't win for losing sometimes...
---
On a positive note, Chrome/google searches seem to be much faster. The UI seems about the same (no complaints with JB).
If battery life can increase then I'll be satisfied with update (so far, no difference).
My experience has been very positive. My phone was bootloader locked and not rooted before (and, of course, after) the OTA. I cleared the cache partition from the recovery menu post-install but have not done a FDR. General impressions:
-- UI is overall much snappier/quicker. Extremely noticeable.
-- Love the new quick settings panel that you can get to after pulling down the notifications shade.
-- KK's changes to how the SDcard works have not been a big deal at all for me. The native "Files" app seems to have complete read/write access, as does ES File Explorer.
-- Like the new clock feature to automatically add a "home" display when traveling outside a pre-defined timezone.
-- Hate the new way you set the alarm on the clock. (Really, whoever came up with that input method should be transferred to a department where s/he can never affect design decisions again.)
-- I miss the audio silencer/mute on the lockscreen.
-- Battery life has been interesting. When I first installed the update (morning of 05/15), battery life was definitely worse, probably by about 50%. It has gradually been getting better, however, and now is probably only about 20%-25% worse than JB. Why it would change I have no idea, but it definitely is (I've been keeping notes, and am sure it is actually happening). I have noticed, using the Battery History details screen, that there are a LOT less wakelocks in KK than JB. In JB, I used to see tons of "Awake" indicators on that screen that did not pair with "Screen On" indicators. In KK, there are very few incidences of "Awake" that are not paired with "Screen On." Someone smarter than me will have to explain how that translates into worse battery life.
-- It may be my imagination, but it seems like the battery charges faster w/ KK. If it's not my imagination, I wonder if that means that the apparent decrease in battery life is really an issue of improper calibration/accuracy.
I have not experienced some of the things others have reported:
-- No random reboots.
-- No changes to WiFi or 4G signals. I don't use Bluetooth so can't comment on that.
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
4039995825
GPlX said:
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
Click to expand...
Click to collapse
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Nidstang said:
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
Click to expand...
Click to collapse
Attempted a FDR on my phone, unfortunately it did not work for me. I will attempt to clear the cache partition to see if that may help the issue if
possible. So far i can only get the boot menu for a couple seconds and im lucky to get a selection in time.
EDIT: I cleared the cache partition, no effect. (NOTE: it seems to get into the recovery menu after selecting it at boot menu, you have to hold power & vol UP for a couple seconds)
crazy4android said:
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Click to expand...
Click to collapse
That is an excellent point. I'll shut off the optimization and will edit my results in after tinkering with it for a while.
EDIT2: Without doing speedtests etc. It is very noticable that the wifi has improved. Youtube & other apps load as fast as they did on 4.1.2
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
kashif87 said:
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
maybe you can uninstall updates to the cam in apps
bwer1233 said:
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
Click to expand...
Click to collapse
Lockscreen widgets were introduced in Android 4.2.2.
Just want to let people know that the Google Now Launcher is working great on 4.4.2 including the "ok Google" functionality.
You can't download it from the play store. I just grabbed the apk from this thread.
http://www.xda-developers.com/andro...-and-gpe-devices-apk-mirrored-for-all-others/
Sent from my XT907 using Tapatalk
rooted + cwm
can't use "memory" feature under settings, while calculating settings app would crash
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
tieuvienson2005 said:
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
Click to expand...
Click to collapse
There are many "phone info" apps in the Market. Or create the short cut with Activity Launcher.
Also the Cam sucks on my Wife's m so get the Lenovo from my Moto x signature link.
Been running stock Android ever since I got my Pixel XL and have been happily running the phone since it came up with each Android update and security patch. Never an issue.
Since a couple of weeks ago when I got the OTA update for Pie, ever since I have noticed the phone to just be laggy. Switching apps and launching stuff, things just take longer to happen. Sometimes they take seconds sometimes less. Games that would play fine now seem to have low frame rates.
My partner who has the Pixel (not XL) is in the same boat as me but having a worse time with the whole phone becoming unresponsive and locking up all the time.
Now the only reports I've seen regarding Android Pie is fast charging issues but neither of us are suffering those issue. All our PD USB-c chargers continue to fast charge fine. I have also seen some high profile Pixel 2 XL users have lag issues but no lag issues with Pixel XL.
Anyone else having lag issues, low framerates and system lockups with Android Pie on the original Pixel phones?
We have yet to factory flash but want to hold out before having to set everything up again.
A theory I have to why my phone is laggy is that I think the system is throttling back my CPU due to battery health. I know Google put some new smarter battery management in this version of Android but I think it is working too hard to a point where the phone is getting very irritating to use.
Thoughts?
No lags on Android 9 here but also flashed clean with factory image.
My Pixel XL is also bit laggy on android 9.
Clearly visible with this live wallpaper which was running super smoothly in 8.1 android, now it freezes for a fraction of a second when unlocking the phone and live wallpaper kicks in.
General app start seems to have slowed down a bit for me too.
Maybe all this crap began with Adaptive battery thingie?
same problem here a lot of lag and freez in my og pixel xl when using ordinary apps like IG, gallery, clock and even xda apps but strangely it run smoothly when playing heavy game like asphalt or PUBG
---------- Post added at 04:30 PM ---------- Previous post was at 03:31 PM ----------
wingman021280 said:
My Pixel XL is also bit laggy on android 9.
Clearly visible with this live wallpaper which was running super smoothly in 8.1 android, now it freezes for a fraction of a second when unlocking the phone and live wallpaper kicks in.
General app start seems to have slowed down a bit for me too.
Maybe all this crap began with Adaptive battery thingie?
Click to expand...
Click to collapse
I've turn off adaptive battery on my pixel xl but the problem still persists
Phone runs smooth on 9.0 for me. Clean flashed factory image. Maybe you guys too need a clean flash? I do understand that formatting should not be required for a phone to run smoothly after each update but looks like that is the solution for now.
I would agree that Android 9 is not as smooth as 8.1. When I first updated, it ran really bad - I eventually did a factory reset, and while it's not as smooth or fluid as 8.1, there's far less freezes or frame drops.
Went back to 8.1. Pie runs like garbage. It was taking 4-5 seconds to open my texting app. Everything back to normal on Oreo.
Pie was lagging my v1 Pixel XL. Seriously bad and huge battery drain. Did a factory reset and that resolved all my issues. Except for the PITA having to log back into every app and resurrect Google Authenticator for 2FA (make sure to right down all the auth sites and have backup codes ready). But as the other poster mentioned a clean install seems to be the only way to get Pie to work. Just bite the bullet and factory reset Pie.
Same-laggy original pixel XL and fast draining battery+ brightness issue
I'll try to factory reset like everyone is suggesting but wanted to go on record about this since expect more from a Google flagship that's only 2 years old. In addition to what everyone else has said, I've experienced problem with brightness of screen. Before pie update I could really cranking up brightness. Obviously battery would take a hit but sometimes needed that extra brightness. Anyone else experience this?
Relamine said:
I'll try to factory reset like everyone is suggesting but wanted to go on record about this since expect more from a Google flagship that's only 2 years old. In addition to what everyone else has said, I've experienced problem with brightness of screen. Before pie update I could really cranking up brightness. Obviously battery would take a hit but sometimes needed that extra brightness. Anyone else experience this?
Click to expand...
Click to collapse
Do you have adaptive brightness enabled? It is enabled by default and adjusts the brightness based on machine learning algorithms
My pixel xl was lagging too. I noticed my Zooper widgets were not loading. I went into the Zooper widgets app and was prompted with a message about it not being tested on 9 yet. After I acknowledged the message, runs without any lag. Widgets loaded on home screen too. Maybe you have a hanging app in the background.
tiny4579 said:
Do you have adaptive brightness enabled? It is enabled by default and adjusts the brightness based on machine learning algorithms
Click to expand...
Click to collapse
I've had adaptive brightness off so that can't be it. But thanks
how do i disable the pie update notification on my android 8.1 pixel XL?
Can't. Not without root.
My camera was seriously lagging. Sometimes 6-7 seconds to open and then 3-4 seconds to take a pic. Someone mentioned adaptive battery and it occured to me that maybe Accubattery was somehow causing problems with the adaptive battery settings in Pie. I uninstalled Accubattery and now my phone is back to normal. No shutter lag at all, camera opens in a fraction of a second.
Bought it a few days ago with Oreo, updated to Pie, and got one bug fix update after - no lag or something, runs super smooth.
There's really no reason to use things like that anymore, especially with newer versions of Android. It used to be necessary back in the day, hell Greenify was like mandatory lol. But really if you're going to use anything , you'd want a program to turn off GPS while screen is off, stuff like that , but it doesn't honestly make a dramatic difference with the optimization in Pie. I get roughly 4 hours screen on time and about 20% battery life left at the end of a cycle. That's 20% drain per hour and I never turn ANYTHING off. GPS always on, most of my day not on wifi, Facebook, Twitter , I just kill it.
To enjoy pie, its best to format data and flash factory images
I've been rebooting my phone at least once a day because the lag is so bad. It's becoming very frustrating.
murso74 said:
I've been rebooting my phone at least once a day because the lag is so bad. It's becoming very frustrating.
Click to expand...
Click to collapse
Did you OTA update or start fresh flashing an image with fastboot?