Related
Hey guys I noticed earlier that my Netflix app was ALOT smoother than it used to be before the ICS update but several others disagreed with me so I was confused. Then I remembered that I enabled this setting in the developer options menu in the android settings, "Force GPU Rendering". Make sure you enable that, close Netflix and start it back up and it should be a million times smoother after you do that. Hope this helps.
Definitely shows great improvement
Learned from GNex with ICS, this option may also FC some apps.
Do not force GPU rendering.
Leave it to app developers to turn it on and make sure nothing goes wrong. Forcing GPU for all apps will make some apps force close and some apps simply slower. If you use a lot of apps there's a chance that while some apps will be faster, others will become slower and more choppy. Read Galaxy Nexus forum for a lot of information on this.
i tired it and it didn't seem to do any difference.
Force GPU Rendering in Transformer Prime
Beware of Force GPU Rendering - DO NOT Enable it
Although some apps appear to run smoother with this option enabled, there are apps that become laggy or even crash with this option. Sometimes the touch response can also degrade. You may also see broken lines and artifacts. The option has no effect on vast majority of games that use GPU anyway. Thus, its not really worth the trouble - it is meant for developers to test/verify their older apps.
Please leave it up to app developers to turn it on for their apps - otherwise you may experience a buggy Transformer Prime with random lockups and crashes
If you do decide to use it - Please make sure you do a COLD BOOT (shut it down, and then press volume down and power button together to boot up). You may also want to clear the cache data for certain apps. This will help some apps to work better with the GPU option - and avoid some undesirable force close.
Thanks but I will leave mine enabled. The smoothness outweighs the 1 or 2 apps that dislike it (I really can't find any)
Have had it enabled since the minute I got the OTA.
Strange behavior with Force Close
timgt said:
Thanks but I will leave mine enabled. The smoothness outweighs the 1 or 2 apps that dislike it (I really can't find any)
Have had it enabled since the minute I got the OTA.
Click to expand...
Click to collapse
thanks, I would be thankful if someone can experiment and share their findings regarding the following observation I had with my prime.
Please try Google Earth with and without Force GPU (dont forget to cold boot after changing the option) and see if you notice any subtle difference. Although at first it appears smoother with force GPU enabled, I sometimes find there are hidden lines displayed on edges of the globe. Also in a slower wifi connection, sometimes the touch response becomes less responsive, as the app waits to render/download the image data. It seems force gpu time to time affects the way the process priority is handled (touch response vs rendering of the globe). Clearing the force gpu restores the correct behaviour in slower connections.
May be this behavior is just random and isolated to my prime, but would be great if someone can try it and confirm.
It would be nice if there was a list of apps that become buggy with this option enabled in the Transformer Prime. There is a list for galaxy nexus that might be indicative of what might not work: http://forum.xda-developers.com/showthread.php?t=1372007
Also please note that for all apps that are released for Android 4.0 ICS will have GPU rendering turned ON by default with or without the "Force GPU rendering" option enabled. So, this option is for OLDER apps only, this option has no effect on newer apps and games.
As application developers start updating their older apps for ICS, they will turn it on for their apps to take advantage of GPU rendering. So, keeping your apps up-to-date from Android Market is the RECOMMENDED approach for getting the best reliability and performance.
chrome browser
a Mandroid said:
thanks, I would be thankful if someone can experiment and share their findings regarding the following observation I had with my prime.
Please try Google Earth with and without Force GPU (dont forget to cold boot after changing the option) and see if you notice any subtle difference. Although at first it appears smoother with force GPU enabled, I sometimes find there are hidden lines displayed on edges of the globe. Also in a slower wifi connection, sometimes the touch response becomes less responsive, as the app waits to render/download the image data. It seems force gpu time to time affects the way the process priority is handled (touch response vs rendering of the globe). Clearing the force gpu restores the correct behaviour in slower connections.
May be this behavior is just random and isolated to my prime, but would be great if someone can try it and confirm.
It would be nice if there was a list of apps that become buggy with this option enabled in the Transformer Prime. There is a list for galaxy nexus that might be indicative of what might not work: http://forum.xda-developers.com/showthread.php?t=1372007
Also please note that for all apps that are released for Android 4.0 ICS will have GPU rendering turned ON by default with or without the "Force GPU rendering" option enabled. So, this option is for OLDER apps only, this option has no effect on newer apps and games.
As application developers start updating their older apps for ICS, they will turn it on for their apps to take advantage of GPU rendering. So, keeping your apps up-to-date from Android Market is the RECOMMENDED approach for getting the best reliability and performance.
Click to expand...
Click to collapse
chrome beta was design for ics so it must be using gpu for default but when i tried open the chrome settings it looks laggy and when i tried using force gpu the setting looks smooth!
Tried this on my gtab 10.1 running cm9
Enabling it makes Flipboard a lot smoother.
"Beware of Force GPU Rendering - DO NOT Enable it* "Although some apps appear to run smoother with this option enabled, there are apps that become laggy or even crash with this option. Sometimes the touch response can also degrade. You may also see broken lines and artifacts"
One answer; It can not be more worse...
a Mandroid said:
Beware of Force GPU Rendering - DO NOT Enable it
Please leave it up to app developers to turn it on for their apps - otherwise you may experience a buggy Transformer Prime with random lockups and crashes
Click to expand...
Click to collapse
Developers have all the fun
With this option enabled, if you scroll a list the CPU will not get past 500 Mhz, without it the CPU will go 100% if you scroll fast (tested it on SGN). So it is providing some battery savings at least....
ON SGN with this option enabled Reduce Photo does not work (crop FC) and SNote /SMemo is much slower.
Good, but not always the best option
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU or better. Its best bet to have it switched off on quad-core CPU devices.
a Mandroid said:
Beware of Force GPU Rendering - DO NOT Enable it
Although some apps appear to run smoother with this option enabled, there are apps that become laggy or even crash with this option. Sometimes the touch response can also degrade. You may also see broken lines and artifacts. The option has no effect on vast majority of games that use GPU anyway. Thus, its not really worth the trouble - it is meant for developers to test/verify their older apps.
Please leave it up to app developers to turn it on for their apps - otherwise you may experience a buggy Transformer Prime with random lockups and crashes
If you do decide to use it - Please make sure you do a COLD BOOT (shut it down, and then press volume down and power button together to boot up). You may also want to clear the cache data for certain apps. This will help some apps to work better with the GPU option - and avoid some undesirable force close.
Click to expand...
Click to collapse
hi,i havent ever heared about such a booting metod guy! what the difference with normal boot from off state?
really will some apps(may be a game) toggle this option in background?how to get asured about that?
excuse bad Eng.
I've only noticed this since about a week.
Its most prominent when I'm in text based apps - Pulse/Verge/Kindle - with a lot of white background.
To describe it - its like a 3mm thick 'glitch', appears for hardly a few milliseconds - just enough to be noticeable.
Its always along the length of the device, and does not matter what orientation I'm holding it in.
I felt it happened more often with auto-brightness but that feeling may just be a dud.
The recurrence is quite random, but I can easily see it if I stare at the screen for even a minute.
Finally I've never noticed it in games or on home screens - not sure if thats just because I miss it in those or otherwise..
I noticed this yesterday for the first time when reading some text. It was very distracting, hoping it was a fluke deal.
Seconding this. I don't have auto-brightness, but I notice it. Definitely happens when reading text with a white background - so get it pretty often in RSS readers, rarely in gmail, and never in games / movies.
Thanks for the replies..
I also noticed this never happens in gmail or currents. Looks like Google-supplied apps run fine...
This leads me to believe that these other apps are doing something wrong, maybe overflowing buffers due to the massive resolution as someone else projected in another thread...
Have you guys played with either the "Disable HW Overlays" or "Force GPU rendering" settings to see if they impact this issue one way or another?
Ravynmagi said:
Have you guys played with either the "Disable HW Overlays" or "Force GPU rendering" settings to see if they impact this issue one way or another?
Click to expand...
Click to collapse
I second this idea.. please try and report the results.
Since my last soft-reboot, I've yet to see ant tearing. However I'll try those options if I see it happening again. Thanks for the suggestions. Maybe some of the others seeing this can try those tweaks?
Happens to me no matter what app I'm running and has been happening since I got my nexus. Even just happened in the app drawer. I will check the force gpu settings and get back to you.
Sent from my Nexus 10 using xda app-developers app
phoenix79 said:
Happens to me no matter what app I'm running and has been happening since I got my nexus. Even just happened in the app drawer. I will check the force gpu settings and get back to you.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Force GPU rendering changed nothing for me. Still got the screen tearing. I'm going to try the Disable HW overlays for a while now.
I have a couple of "issues" with the phone. Not sure if its software related or hardware related. Maybe you guys can check on yours too see if it happens. This is all on stock ATT rom
It seems the One has "dynamic contrast" enabled by default. When scrolling on webpages, for example, if I come to an area with a dark advertisement, the brightness adjusts very slightly most of the time. Thats all well and good but the annoying thing is that it does it in steps causing quick blinks of the backlight. Its most pronounced at medium brightness. The same "blinking" happen when autobrightness wants to set the brightness to a very low level . It does it in very discrete steps and it takes a long time for the brightness to settle to its minimum.
If i set my brightness to 50% (most prevalent when the slider is under the "t" in brightness) I get a VERY subtle, but constant pulsating of the backlight. Again, Its a very subtle but my eyes pick it up regardless and its distracting as hell. I wouldn't mind it if autobrightness didn't hit this brightness level, but it does sometimes indoors. The effect is best seen on a mixed white and color screen, like a homescreen with a white widget and most websites. If the brightness goes a bit above or below this level, the pulsing goes away . Anyone else seeing this? maybe it happens at a different brightnesses on different screens.
Thanks
I noticed this when watching a video today. Maybe it only happens if you have autobrightness on?
Sent from my HTC One
It happens with autobrightness off for me. I actually tested it a bit more. I happens on a variety of backlight settings depending on what's on the screen.
At approx. 33% brightness (im using an app called screen adjuster to set the system brightness to a specific value), the screen does heavy pulsating on an all white image. For example, if I go to "about:blank" in the web browser. I can be seen on a desktop screen with a white widget or the settings menu.
Same thing at 40. Worst is 33% though. I have a feeling its dynamic contrast going haywire at certain brightnesses. If you turn the screen off then on, it doesnt do it for a second or 2, but then it will start. I haven't been able to find a demo unit anywhere around me to test this out. So if someone can check this on their device, I would appreciate it. Please use Screen Adjuster to get a definitive reading on the brightness. (Use the slider in "system brightness" to set it to a specific brightbess) and go to "about:blank" in the default browser
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
shep98 said:
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
Click to expand...
Click to collapse
Thanks for the response. I ended up looking at 4 more devices at 2 different stores and they all had the flicker. The sales associates even saw it. I got tired of doing exchanges and I ended up reversing my upgrade. Im going to wait and see what happens with this issue. Hopefully it gets sorted out with a firmware update, because otherwise its an awesome phone. Its a shame that the $100 trade-in offer is going to end by then and I wont be getting a free medialink device, but atleast i'd be able to get it in black, which is what I originally wanted.
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Mr Sliff said:
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Click to expand...
Click to collapse
In addition to the phones I exchanged, every display model that I've come across has had it. I'm was a bit surprised at first that not many people have come across this. I'm starting to think that maybe the One has a PWM backlighting, which some folks are sensitive to and some don't even notice. I'm in the former category and I think you are too. It a shame really that this problem exist. Besides that, I couldn't find any other faults with the phone. It was perfect in every other aspect
I've run Into the same exact behavior using the HTC droid DNA with both sense 4+ and sense 5 ROMs. I smell tomfoolery afoot.
Screen Flicker
I'm glad I'm not the only one that has noticed this. It doesn't stay that way very long for me, but it is quite annoying. Seems to happen when there's a white or light-colored background the most. So I guess there's nothing specifically wrong with my phone and we'll either have to live with it or wait until someone figures out how to fix it?
I guess most people don't notice this.m it's extremely irrational going between this and my tablet and having the black.ighting flashing in my face when I scroll through webpages.
[Q] Flashing/blinky screen in black but only on "application level" of display
Hey folks,
So what I'm seeing is the application area/layer of the screen blacking-out in a blinky way, and this seems to happen when there's screen updates like from the application or when I'm scrolling with my finger. The weird thing is this only seems to affect the "application level" layer -- the Status bar and other things like CPU usage (and overlay apps like SwipePad) are unaffected and don't black-flash.
I'm running PAC-MAN ROM (Android 4.4.4) but have experienced this on other ROMS so I think this is either a Note i717 thing and/or something that I'm doing to create this issue. It actually happened with less intensity with other roms of previous Android versions. (probably back to 4.4.2)
What I done wrong? I'm getting a hurt real bad. (a Russell Peters reference, for those who haven't heard his older material)
mentalfloss said:
Hey folks,
So what I'm seeing is the application area/layer of the screen blacking-out in a blinky way, and this seems to happen when there's screen updates like from the application or when I'm scrolling with my finger. The weird thing is this only seems to affect the "application level" layer -- the Status bar and other things like CPU usage (and overlay apps like SwipePad) are unaffected and don't black-flash.
I'm running PAC-MAN ROM (Android 4.4.4) but have experienced this on other ROMS so I think this is either a Note i717 thing and/or something that I'm doing to create this issue. It actually happened with less intensity with other roms of previous Android versions. (probably back to 4.4.2)
What I done wrong? I'm getting a hurt real bad. (a Russell Peters reference, for those who haven't heard his older material)
Click to expand...
Click to collapse
If you would consider this a screen flicker, you may want to try disabling HW Overlay in the developer options.
Another option may be to read up on POLLUTIONS "Patch". There is a thread for it, but I cannot say as to what issues it will fix. Apparently it is a miracle cure in tye Beanstalk thread.
Thats why I say....read on it first.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
If you would consider this a screen flicker, you may want to try disabling HW Overlay in the developer options.
Another option may be to read up on POLLUTIONS "Patch". There is a thread for it, but I cannot say as to what issues it will fix. Apparently it is a miracle cure in tye Beanstalk thread.
Thats why I say....read on it first.
Click to expand...
Click to collapse
Yeah those are some good ideas, but here's some more info:
I don't have the HW Overlay option enabled.
The "flickering" is not the entire screen, and it's more like a "black flicker", and ONLY on the "application layer"
I found the patch you mentioned in this thread and I'll see if it addresses it when I get a chance to work on the device.
Oddly, I just booted the phone with OTG HDMI connected to a monitor and the flicker is gone! :/ Not really a solution but an interesting oddity.
Hey everyone,
This will be a Thread for collecting all the kinds of bugs and other issues you might have encountered.
I talked to the german FB group and talked about them sending them a collection of bugs etc from the community. They gave me an email address (from the communication team) where i can send it to once everything is done.
They will then proceed to send the information to the people developing for axon 7 (A2017G in this case). Of course it's not guaranteed that they will definitely fix all the issues. But it's worth a shot imo.
So at first it's important that bugs have the most importance in this thread since those have to be fixed in order to get an enjoyable oreo experience.
BUT you can also post any features you want to have back (examples are daydream, screen color calibration)
To get things finally started, here are the issues that i gathered so far from this thread:
-SD card mounting issues (SD card doesn't stay mounted after reboot)
-Increased battery drain (mixed opinion, some say it's worse, some say it's the same as nougat)
-Preinstalled apps which are uninstallable (like Accuweather, WPS Office) reinstall themselves after reboot
-Events set in Google calendar don't show a notification
-Bluetooth audio developer options (LDAC, 32bit, 96khz, etc) do not stick
-screencast not working on some miracast devices
-Panorama has lower vertical resolution (approximately 1900px while Nougat had 2800px)
-Charging sound file is missing (now it uses error sound file when connecting/disconnecting USB which sounds really annoying)
Missing Features that you wish to come back or added:
-Screen Color Calibration
-Daydream (which might come back since how they worded it to be temporarily disabled)
-Camera2 api not yet fully implemented
-Vulkan API (was present in Nougat, now removed in Oreo for unknown reason)
-Screen lock app (shortcut in quick settings to lock the device)
-Option to remove Carrier name in status bar
-Dark Mode option (preferably true black background for the while UI like quicksettings menu, settings menu etc for max SOT.)
-More sorting options for stock music player (by title number etc instead of by alphabetical order)
-ZTE Toolbox app
I'm sure there is more. But this is what i have found so far as of now. If there is any more issues you encountered, please post them so i can add them to the list.
Also if i missed any additional info for the issues above, please feel free to tell me.
- Dark mode option
- further dimming option (lowest brightness still too bright)
- screen off toggle/widget
1. Screen cast still won't work well, I never get it connected to miracast since nougat and they didnt fix it on oreo, all my other devices work so good with the same miracast.
2. Battery drain faster than nougat or I think this even worse than oreo beta build B01.
Feature:
- The alphabetical order on music folder for stock music is still annoying. No one hopes listening music from A to Z based on title.
One more:
I don't know if it's just me, but I have a bug where the download manager won't download anything for a long time despite having stable internet connection. This affects Play Store app downloads and downloads other than Chrome (since Chrome has its own download manager it seems). Basically, if I want to quickly download an app or update them, the initialisation starts but it keeps waiting for stuff to download. It won't abort with an error, it just sticks to the spinning circle. In the notification bar you won't see the download arrow animation, which should be there actually. But if I lay down my phone for a while and then pick it up, it may start downloading normally. It's very annoying, you can imagine m
ChiDi9901 said:
One more:
I don't know if it's just me, but I have a bug where the download manager won't download anything for a long time despite having stable internet connection. This affects Play Store app downloads and downloads other than Chrome (since Chrome has its own download manager it seems). Basically, if I want to quickly download an app or update them, the initialisation starts but it keeps waiting for stuff to download. It won't abort with an error, it just sticks to the spinning circle. In the notification bar you won't see the download arrow animation, which should be there actually. But if I lay down my phone for a while and then pick it up, it may start downloading normally. It's very annoying, you can imagine m
Click to expand...
Click to collapse
I know what you mean. But it's not a bug from oreo. I had this too on nougat. Sometimes it still happens. But not as often as it used to be. Dunno what fixes it sadly, but thats probably an issue of play services messing up something since the axon 7 isn't alone. Many other devices have this problem as well sometimes. It comes and goes randomly.
And as you said, chrome and other apps with their own download manager don't seem to have these issues. Again, it's probably play services doing something wrong. Not sure tho, just a guess as play services had many problems in their history
macmobile said:
- Dark mode option
- further dimming option (lowest brightness still too bright)
- screen off toggle/widget
Click to expand...
Click to collapse
What do you mean with dark mode? Like amoled substratum themes? Or like night light?
Poor wifi and 4g reception. This has been my main problem with this rom.
GodOfPsychos said:
What do you mean with dark mode? Like amoled substratum themes? Or like night light?
Click to expand...
Click to collapse
Quick settings, status bar and system settings are all unbearably white. Due to Google's safety measures you can't even use a third party filter anymore.
On Nougat you could change the quick settings to gray at least and use a third party filter for all the rest. On Oreo, no chance at all. What a bad user experience!
So why even bother with a system update, if it doesn't let you adjust the display brightness to your liking anymore?! And I haven't even mentioned the usefulness of an all white UI on an AMOLED screen (Battery!?).
Panorama has lower vertical resolution.
Nougat approx 2800px
Oreo approx 1900px
Signal issues
Hd calls work with incoming but call does not connect for outgoing
Band switching issue band keeps switching thats the main reason for battery drain on 4g
My network is Jio 4g in India
It works in band 3 5 and 40
3 and 5 bands work together but they wont work well with 40 that is they keep switching from one to other with internet connecting and disconnecting
So i switched off band 40 using network signal guru app with magisk root permissions and everything works fine except slow internet speed and persistent hd call issue
Can anyone make solution for band issue
If there is a possiblity to reduce the heat generated during simple tasks.
I had most of those issues: significantly worse battery life, camera freeze when using RAW capture, when I reseted the phone, everything is back to normal, maybe battery is like 5-10% worse than nougat but not sure. Can't say anything about the missing features. I want them too, but most of wanted a Stock + UI and now we complain ? vanilla Android lacks many features like it or not. Hope they release some future firmware update to fix any issues and update the security bulletin.
alexvv said:
I had most of those issues: significantly worse battery life, camera freeze when using RAW capture, when I reseted the phone, everything is back to normal, maybe battery is like 5-10% worse than nougat but not sure. Can't say anything about the missing features. I want them too, but most of wanted a Stock + UI and now we complain ? vanilla Android lacks many features like it or not. Hope they release some future firmware update to fix any issues and update the security bulletin.
Click to expand...
Click to collapse
You had most of these because i used the same thread your post was in as well about the freezing raw capture with stock cam.
But you are the first and only one who had this happen with the camera. So far nobody else reported having the same issue.
alexvv said:
I had most of those issues: significantly worse battery life, camera freeze when using RAW capture, when I reseted the phone, everything is back to normal, maybe battery is like 5-10% worse than nougat but not sure. Can't say anything about the missing features. I want them too, but most of wanted a Stock + UI and now we complain [emoji39] vanilla Android lacks many features like it or not. Hope they release some future firmware update to fix any issues and update the security bulletin.
Click to expand...
Click to collapse
I never ever wanted Stock Android. Stock is the least customizable iteration of Android. So who could want this kind of user experience? People who think Google knows what's best for you? Ridiculous!
Any one tried downgrading to Nougat?
Tried official update.zip. Downgrade FAILS!
This package is for "ailsa_ii" devices; this is a ""
(My device only received official updates, never a custom ROM or root)
Yerry said:
Any one tried downgrading to Nougat?
Tried official update.zip. Downgrade FAILS!
This package is for "ailsa_ii" devices; this is a ""
(My device only received official updates, never a custom ROM or root)
Click to expand...
Click to collapse
You can't downgrade with the official update.zip
Also this is the wrong thread to post this. This thread is for bugs found in oreo.
I appear to be having poor quality sound when playing audio though the main speakers. There's a hissing sound.
GodOfPsychos said:
You can't downgrade with the official update.zip
Also this is the wrong thread to post this. This thread is for bugs found in oreo.
Click to expand...
Click to collapse
I disagree on both of your statements. here is why:
1. It is possible to downgrade, but not with all official update.zip that exist (I succeeded in the meantime!)
2. It is a bug in the Oreo rom that the device type is not set, preventing majority of old update.zip to run since they check the device type
I am missing the stock Nougat 'lock screen' option in the Quick options menu. I am using an app to soft lock the screen at the moment which works but am not sure at all why they removed it in first place.
I am also missing the Messaging and Phone customization options available in Nougat, including the different message bubbles types and the background change settings. It is now simply white and blue and you couldn't change it.
I have had a hard time fixing the Notification problem Oreo brought to many apps, including system, resulting in oversleeping for alarm clock app not working at all. This may not be a particular problem of ZTE directly since apparently it is an Oreo issue but I still don't understand why so many notifications have been forced to the swipe-down menu without default option to disable them. Like "this and this process running in the background" and using default notification tone for every single thing happening to the phone. Adjusting settings in Android System notification modes solved some problems but delayed or not showed at all certain notifications like SMS messages or alarm clock not working - even though these were specifically made to pop and make sound.
Battery life for me varies. It may be up to 10-12 hours if I don't do almost anything and just keep it in stand-by to 3-4-5 hours if I use the screen, some browsing and listening to music. Screen-on-Time in general is up to 2-3 hours in best case scenario. Also sometimes for no apparent reason I see the battery percentage going down like every few seconds by 1 percent and with no use of anything special, just the screen. Overall I could rate it (a little) worse than Nougat considering that I've now gone through all Power settings and disabling anything I don't need per app.
I can only congratulate ZTE for making Dolby Atmos now working on both earphones and front speakers at all times, including with custom player equalizer running at the same time as Dolby Atmos. It never worked for me and was also accompanied with various bugs on all 6, 6.1, 7 and 7.1.
The "choose what your SD card should do" on every restart is pretty bad and I strongly prefer the Nougat behavior when it simply worked. Maybe adding a Setting - "do not ask again" or an option in the System Settings where you can change the status of the SD card on the go would work better than unmounting it every time. This causes many issues with file managers, players and different other apps with files located on the SD card. I hope they re-work it.
Finally, I noticed that Ultra Power Saver works in a much worse way than it did on Nougat. It kind of goes into another OS mode upon return from which it does not start apps that are set to auto-start upon reboot. The Nougat style of simply black-and-whit-ening the screen and turning off any data was so much better and didn't return the phone in a half-functioning state when connected to the charger. Also at 15% as I adjusted it, the middle power saving function (Power Saver or so) does not seem to be at least visibly working so the battery keeps draining as fast as if it was not on.
So, in short - dark(er) Quick Menu, getting back Nougat default app customization options, fixing the SD card message upon every reboot, not forcing TouchPal to be default keyboard or in use even if another keyboard is chosen, or disabling both, and possibly working on better battery life would be all amazing. I still think ZTE did a great job with 8.0 and am happy they finally released it to us.
The phone was frozen and restarted several times.
After that, fingerprint doesn't work and I had to reconfigure fingerprint record.