Related
So, my LG G3 updated yesterday from kitkat (12b) to Lollipop 5.0 (23c).
I have to say, I am on the fence about it being an upgrade. Here is my thoughts: 2 major annoyances and 1 feature I love.
First, "Quite mode" is GONE! It has been replaced with a less functional, yet more confusing and complicated feature called "Interruptions". LG's Quite mode worked perfectly and did everything I wanted it to and was super easy to setup. Google's Interruptions thing is just plain horrible. First, I discovered that I can't set certain contacts to be allowed to ring though, only options are to allow "Priority only" which the Contacts options only gives u "Anyone" (everyone), "Favorites" (those who u add to your favorite list) or " Contacts Only" (all contacts). So, I had to use my "Favorites" list as my "allow" list. Ok...fine. BUT then, I discovered last night, that Interruptions does NOT silence system sounds like charging sounds or the LED notification light. I set my phone on the charger when I went to bed, and it made its chime and the LED stayed on. I was woken up a few hours later when the phone chimed again for Charge Complete and the LED was bright green. LG's Quite mode allowed these features to be silenced. I also dislike how the volume bar pop-up now has tabs added to it to adjust enable/adjust Interruptions...clutter and can easily be accidentally pressed. (SoundHud app helps with this) I have read that this Interruptions is a Lollipop thing(baked into the OS) and is meant to replace any custom manufacture add-on Quite Mode or Blocking Mode(Samsung). I found many folks complaining about this in other forums. I was able to address this annoyance by finding a 3rd party app (Do Not Disturb by Cabooze Software) but I am greatly annoyed that I have to now use a separate app to do something that one once a built in feature of my device.
Second, I am not a fan of how notifications work now. That is that the notification bar and lock screen notifications are one in the same. You can't have one with out the other. I want my weather app to have its notification in the drop down bar, and keep its little temperature figure notification in the upper left of my notification bar.... NOT the entire notification cluttering up my lock screen. I set the option to not show notifications on the lock screen, and it removes the notification bar notifications for that app too...wtf? I can set something about Private or sensitive notifications are hidden, but that only changes the notification to say its private and to unlock to view...doesn't actually hide anything. The new way of dismissing notifications is nice, but if I recall, I could swipe away certain notifications like call or txt on the lock screen before (LG thing maybe). I suppose I can adapt to and get used to the new way notifications works....but does the clock have to be so tiny even when only one notification is up? Seriously, the text is too small.
They still haven't "fixed" the LG keyboard so that u can adjust height of the keyboard when the phone is rotated to landscape mode....still only adjustable when in portrait mode.
On the good side....I LOVE the "Smart Unlock" feature. Only thing I recall having this kinda feature is if you had a Android Wear device. I love how u can have a Bluetooth (or NFC) device paired and it will set the lock screen to swipe....and not have to use knock or password code. I have this set for when my headset is paired and also my Pebble Steel watch. Very convenient feature to have. (I don't get NFC option though....what?! Do I need to get an NC chip implanted in the palm of my hand, so that when I hold the phone, I can use this feature to bypass the lock code...LOL!)
As far as other things go...the phone does feel more responsive. The new animations are quite welcome. I can't really say anything about battery life at this point. I got excellent battery life on KitKat.
I have read some discouraging things about the Lollipop update for the G3. Many forums filled with complaints about it...not just for VZW. A few of my co-workers who have a G3(various carriers) each one of them has issues and/or complaints about the update and discouraged me from updating. I also was quite confused as I was seeing VZW G3's for sale online starting over a month or so ago(swappa, ebay etc) that already came with Lollipop 5.0 and they claimed it was the official release. I was indeed suspicious of these phones that they were installed with a leaked OTA, but 23b as far as many insisted was the official OTA, but I(and several others I know in various states) never got 23b. I went from 12b to 23c. I checked the OTA option on the phone and the Update software on my computer frequently enough, never gave me any other update. Maybe VZW waited to push out the OTA in my area(Twin Cities, MN)...and thus we got the latest version.
Anyway, I guess its a love/hate relationship with my phone at the moment. :silly:
There are a few ways to get a more traditional "quiet" mode back...
http://forum.xda-developers.com/xposed/modules/xposed-true-silent-mode-lollipop-t3042924
and a few others out there, but I haven't upgraded yet.
As for the NFC deal...
https://www.indiegogo.com/projects/the-xnt-implantable-nfc-chip
They do exist...
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
Here's the other one I tried to remember.
https://play.google.com/store/apps/details?id=com.greatbytes.soundhud
Free 2 week trial I think. hasn't been updated since it came out though.
RED ZMAN said:
There are a few ways to get a more traditional "quiet" mode back...
http://forum.xda-developers.com/xposed/modules/xposed-true-silent-mode-lollipop-t3042924
.
Click to expand...
Click to collapse
Doesn't exposed require root?
Yes. SoundHud doesn't though.
I'm pretty sure there are others too, but these are the 2 I knew of for sure.
RED ZMAN said:
Yes. SoundHud doesn't though.
I'm pretty sure there are others too, but these are the 2 I knew of for sure.
Click to expand...
Click to collapse
Phone not rooted. Not sure if it can be. I know that 12b was not rootable. I have no intentions of rooting requadless.
Either way, Do Not Disturb app works fine.
Did you check out SoundHud? That does NOT require root.
Do Not Disturb
I used to use its predecessor 'Noyze' before the developer gave up on it, loved the themes and options.
I'll check out Do Not Disturb when I upgrade.
RED ZMAN said:
Did you check out SoundHud? That does NOT require root.
Do Not Disturb
I used to use its predecessor 'Noyze' before the developer gave up on it, loved the themes and options.
I'll check out Do Not Disturb when I upgrade.
Click to expand...
Click to collapse
Excellent! Just installed it. SoundHud is perfect to address the annoying larger volume sliders default to Lollipop. (its not a Quite Mode or D.N.D. app) Thanks for the recommendation.
Still, yet another 3rd party app I have to install and having running to "fix" things that Google changed....hope it doesn't affect battery life at all.
Both apps arn't free though....hate that.
That's what I use all of my Google Opinion Rewards money on, apps I don't want to buy.
LOL
BTW, I haven't played with it on Lollipop yet but the description on SoundHud says...
Description
SoundHUD is a highly customizable volume panel replacement that doesn't require root access. And maybe best of all: It comes with a true silent mode for Lollipop users!
What's in the box:
• Multiple styles - choose between an expandable volume panel, a statusbar volume panel, or just a thin line that stays out of your way
• Lollipop silent mode - tired of the lack of a true silent mode for Lollipop? Yeah, so are we!
• Long press actions - launch any app simply by long-pressing one of the volume buttons
• No root required - leave the drill at home: no root, no Xposed - keep that sweet, sweet warranty!
• Volume stream lock - got a media tablet? Turn on volume stream lock to always adjust the music volume instead of having to deal with a useless ringer volume
• ...and much more!
Like Lollipop's design and simplicity? It sure is swell, but it seems the stock volume panel didn't get the memo - if you've tried getting Lollipop to shush while still getting woken up in the morning, I'm pretty sure you were on the verge of feeding your phone to Rusty (pro-tip: plastic doesn't make a very good dog treat!). Enter SoundHUD, which comes with a true silent mode for Lollipop, an expandable volume panel with separate, draggable volume sliders for every volume stream (ringer, music, notifications, alarms, in-call volume), and much more!
Silent mode HOW-TO
1. Go to System settings -> Sound & notification -> Interruptions
2. Turn OFF all priority interruption switches
3. Get up, do a little dance, and enjoy the silence! No more calls, notifications, reminders - just alarms!
Click to expand...
Click to collapse
Let us know how it works out.
RED ZMAN said:
That's what I use all of my Google Opinion Rewards money on, apps I don't want to buy.
LOL
BTW, I haven't played with it on Lollipop yet but the description on SoundHud says...
Let us know how it works out.
Click to expand...
Click to collapse
Works fine for me. But I did not got to settings and adjust Interruptions settings as they said to. That would interfere with the Do Not Disturb app I have....I do want some things to be let through.
Honestly, I don't care nor have ever used a pure Silent mode during the day.
Only time I want everything (except alarms and certain contacts- mainly my work contacts) "Silent" is at night set to a schedule(10p - 9a).
Downgrade? I feel the exact opposite. I think it's a huge upgrade and I love the way LP runs. Both stock/AOSP based roms are awesome. I hope you get the issues worked out so you can enjoy it.
12b is rootable, so is 23x (a,b,c). Can be done in situ, no need to downgrade, root, and then upgrade.
speedingcheetah said:
Phone not rooted. Not sure if it can be. I know that 12b was not rootable. I have no intentions of rooting requadless.
Either way, Do Not Disturb app works fine.
Click to expand...
Click to collapse
Sent from my VS985 4G using XDA Free mobile app
Welcome to Lollipop, Google is your friend.
Oh and by the way, alarm clock won't sound if you set to "No Interruptions" even if you set it as a priority notification.
DigitalMD said:
Welcome to Lollipop, Google is your friend.
Oh and by the way, alarm clock won't sound if you set to "No Interruptions" even if you set it as a priority notification.
Click to expand...
Click to collapse
When I was using Interruptions, the alarm did sound fine. First thing I tested.
theistus said:
12b is rootable, so is 23x (a,b,c). Can be done in situ, no need to downgrade, root, and then upgrade.
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
I was told (and read) multiple times, even by a dev that 12b is not rootable..directly. HAd to downgrade or something.
speedingcheetah said:
I was told (and read) multiple times, even by a dev that 12b is not rootable..directly. HAd to downgrade or something.
Click to expand...
Click to collapse
A new root method was discovered a week or two ago that works with pretty much every current LG device regardless of firmware version or carrier. It's not Stumproot, that was patched after 10 b, yes.
This new root method seems to involve zeroing out the laf partition, causing the boot process to fall through to fastboot, or something like that. I did not understand It, no, but theroadwarrior here and others seemed to. Works on the G2 also, if I can get hers away from My Lady Susan !
Sent from my VS985 4G using Tapatalk
I don't care for 5.0 as much either. I'm heading back to my 10B backup where everything works. Also, I missed Xposed in just a few days. When Xposed can run on Stock 5.0 I'll give it another go.
vudugan said:
I don't care for 5.0 as much either. I'm heading back to my 10B backup where everything works. Also, I missed Xposed in just a few days. When Xposed can run on Stock 5.0 I'll give it another go.
Click to expand...
Click to collapse
5.X really has been one of the worst android releases. Google tries to keep shining that turd
Sent from my Nexus 7 2013
Bluetooth issues
Another thing to report. My co-worker reported issues with his car stereo and the G3 after he updated to 5.0. U pair the phone to the stereo and it will play music or sound from any app fine for about 2 min, then it goes all frizzy. Only way to restore proper sound is to toggle bluetooth on and off and re-connect. Tried with a few different apps. I paired my phone (we have the same phone and OS version) and I can confirm the same issue. My phone was rest recently before the 5.0 update. He also reports that he tried a few other phones(not sure models or OS version) but the worked fine with his car.
Weird, thinking it must be something with his car stereo, as both of us have paired our phones to several other Bluetooth sound devices and have had no issues.
Underwhelmed in general
Just like with Apple products, the more hoopla about a release, the less I should expect. Android 5.0 on the G3 is no exception:
Despite the changes in "Notifications", there doesn't appear to be a way (as with v4.4.2) to just have Notification icons appear on the lock screen, without any content.
Despite the change, the recent apps list is a mess, with multiple pages per app for some apps.
What was wrong with the "home" icon??? It looked like a home. Do a lot of people live in a hole rather than conventional house? If they do, how do they have enough money to buy a phone? I have no objection to the new icons per se; it just seems like so much of the rest of the commercial software world, making changes for changes sake. Or perhaps Google assigns meaningless GUI changes to test new software developers ...
Then, for the crowning achievement, lets take more screen space with the new "floating buttons", which block content, and for which there is ample space for the button in the top bar of the app.
I had hoped for LG to fix the sharing of the "recent apps" button (primary function) with the (app-specific) "settings" function, but no; let's keep that UI not only different from most other Android devices, but even different from the LG G Pad 8.3. The latter has the "recent apps" functionality as a secondary function of the "home" button, a much more consistent idea.
Finally, does anyone at LG or Verizon, beta test the GUI? It is my imagination, or in the "Sound & notification" section of "Settings", there is a line titled "Interruptions". Under that, mine always says, "Have no interruptions from notifications" as the current setting, despite the fact that is NOT the current setting.
At least they fixed the QSlide version of the text message app: you can now get to the contacts list from within it. I don't think you could do that before.
Ah well, that's progress, I suppose.
Just my opinion....I like the new lollipop. I've not had any issues as of yet. VZW LG G3... OTA'd to 23C.... Manually flashed 12C aboot and 23C bump'd kernel...then flashified TWRP. No reboots...great battery. Now the thing I most dislike is that there's no silent mode.. I really miss that. Seems the interruptions thing is just more complicated. Other than that...I'm happy.
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.
There is a new update.
【Release Note】
Updated Android security patch
Improved touch stability of glove mode
Improved camera quality
Improved camera stability
Fixed video unclear issue when turning on hypersteady.
Fixed BoardMic test fail issue
Yeah just got this update as well.
I've tested a bit the camera aspect. It seems now we have a wide angle at 0.5x minimum instead of 0.6x.
I do not remember whether we had 0.5x or not before this update. To my eyes the 0.5x is there only because the distorsion correction is disabled at this zoom level.
I did not observe any noticeable improvement yet.
deadlynounou said:
I've tested a bit the camera aspect. It seems now we have a wide angle at 0.5x minimum instead of 0.6x.
I do not remember whether we had 0.5x or not before this update. To my eyes the 0.5x is there only because the distorsion correction is disabled at this zoom level.
I did not observe any noticeable improvement yet.
Click to expand...
Click to collapse
It was 0.5x before too
I believe the Ai scene in camera settings is new in this update
Seosam said:
I believe the Ai scene in camera settings is new in this update
Click to expand...
Click to collapse
It's not new
Anyone else noticed pocket mode is too sensitive since the update? When I move my finger to touch stuff near the top of the screen, the display turns off. Very annoying!
crumble6 said:
Anyone else noticed pocket mode is too sensitive since the update? When I move my finger to touch stuff near the top of the screen, the display turns off. Very annoying!
Click to expand...
Click to collapse
It shouldn't do anything if the screen is already on
Tagion said:
It shouldn't do anything if the screen is already on
Click to expand...
Click to collapse
Sorry I should have stated that it only happens in a dimly lit room. If the room is well-lit, it doesn't happen. Pocket mode activates whether the screen is on or off, but it must be dark and something activate the proximity sensor.
Previously I didn't have an issue but now if I am using the device on an evening where we have set our room lights very low, or for example sat in bed with just a small lamp on. Since the update this is dark enough to trigger it.
EDIT: I flashed the update again and the problem seems to have gone away
The update disappears on the Asus Homepage
https://www.gsmarena.com/asus_issue...n_urgent_hotfix_for_the_camera-news-45882.php
There's a new update 29.13.7.44, changelog:
Hotfix for camera license expiration at the end of October 2020
Please ensure upgrade to this version for proper camera functionality
Click to expand...
Click to collapse
I can't find it on Asus' site and I can't do an OTA because I had my bootloader unlocked. Now even if I RELOCKED it, still can't do OTA updates. Thanks ASUS! So stupid.
jericho246 said:
https://www.gsmarena.com/asus_issue...n_urgent_hotfix_for_the_camera-news-45882.php
There's a new update 29.13.7.44, changelog:
I can't find it on Asus' site and I can't do an OTA because I had my bootloader unlocked. Now even if I RELOCKED it, still can't do OTA updates. Thanks ASUS! So stupid.
Click to expand...
Click to collapse
It's always 1-2 days later on the website available.
Link for new firmware WW
Update 29.13.7.44
You must be on official boot.img before update
Should I just wait for this to appear on OTA? Or is there an update.zip method via sd card method? I'm pure stock btw.
Should I just wait for this to appear on OTA? Or is there an update.zip method via sd card method? I'm pure stock btw.
CVonV said:
Should I just wait for this to appear on OTA? Or is there an update.zip method via sd card method? I'm pure stock btw.
Click to expand...
Click to collapse
I have just updated OTA. The update possibility appeared today.
Ahh yep it's appeared now for me over OTA.
Here are the details
WW_user_29.13.7.44_20201015
1. Optimized the logic of camera flipping obstacle detection
2. Optimized the dynamic camera photo effect
3. Improved the occassional shaking issue in Camera 60FPS video mode
4. Updated IT Windtre APN
5. Enabled VoWiFi on CSL (HK)
267.48 MB
Click to expand...
Click to collapse
I had to come from 29.12.18.16 as the one in OP didn't appear for me.
Is there any way to lock the camera app rotation in Android 6.0.1 without root?
Im using a couple of our old Galaxy Note 4 as video recorders for tutorials. I have them set up on booms. I have the phones rotation locked, but the camera orientation will still change. When Im needing straight down shots, the camera greatly favors portrait. Im constantly having to adjust the rig and slowing lock the rig into place. But after hitting stop, 9 times out of 10, it snaps back to portrait. Ive tried various lock rotation apps, but nothing works. Ive also looked at alternative Camera apps, but nothing works there either.
Here's the. . . .well. . . . you'll probably think this is obnoxious, but i MUST (subjectively speaking) have the phones as minimalist as possible. Obviously I can't activate the phones, and i do not want to sign into any google account. So, conventional means of updating are out. I came across something where if I could get to Android 10, I could go into development options and disable sensors. But still stuck on Android 6.0.1 and developer mode doesn't have that option. Updates keep showing up as being available, but despite going through about 7 updates, Android remains at 6.0.1.
Can anyone help me?
I bought my Xperia 1 IV last week and almost considered returning it at first, because it was overheating a lot the first day. I have sort of a traumatic experience with overheating phones as I had the Z5 which was simply a bad phone with the Snapdragon 810 and insufficient cooling. After some research I read the same thing about the Xperia 1 III, with people saying that the "AI needs to learn" and it will "go away after 2 days". It still gets warm, but I did notice I was overly conscious of it, and since I had my XZ3 around with my SIM inside, I could do some comparisons. The XZ3 has a much smaller hotspot, so when it gets warm, it's only above the camera area on the back, and you don't really feel it holding in your hand. When the 1IV gets warm, the heat is spread along the top half of the back and into the sides so you're much more aware of when it gets warm. So I decided to just keep it, root it and start using it as my daily phone.
The rooting experience was problem free, just like with my XZ3. Grab the unlock code from Sony, use XperiFirm to extract boot.sin, use unSIN to convert to boot.img, do the same with vbmeta.sin, install Magisk, use it to patch boot.img, use fastboot to oem unlock and flash the patched boot.img and unpatched vbmeta.img. Done! I looked at installing a custom recovery, but TWRP doesn't support Android 12 yet, so I'll just have to be careful and not get myself into situations where I need recovery to bail me out of bootloops for now.
What works:
Magisk 25.1
Zygisk
LSPosed 1.8.3
Universal SafetyNet Fix 2.2.1
fbind v2021.12.7
MagiskHide Props Config 6.1.2 (used to hide navbar and enable bluetooth in-band ringing)
G-VisualMod 4.1 (although I removed it again because it didn't do what I wanted)
Modded GCam 8.1.101 A9 GV2a ENG (for Night Sight as the Sony camera app has no equivalent - only issue is clipped highlights turn yellow)
Fluid Navigation Gestures (navbar hide doesn't work but see above for workaround)
YouTube Vanced non-root mode (make sure to set microG to restricted battery mode)
XPrivacyLua 1.31
What doesn't work:
Immersive mode and any apps/mods that claim to enable it
AOSP Mods (crashes SystemUI constantly and most of the mods don't work)
GravityBox (S) (crashes GPS apps like google maps / waze)
MinMinGuard 2.1.1 (shows 0 ads blocked)
YouTube Vanced root mode (YouTube app is too new, can't downgrade)
Another issue I encountered is that Google Maps on my XZ3 has driving mode available, but since this is Android 12, there is a new revamped version of driving mode that is region locked to US/CA/UK/AU. You will get "Driving mode is not yet available in your region" in unsupported regions. The workaround is to sign out from Google Maps, add the Driving Mode shortcut to your home screen, and then sign in again. The shortcut will work even when signed back in.
I really resent not being able to hide the (rather big) status bar and all the OLED burn in consequences of having the status bar visible at all times. The pixel shifting of the status bar icons is also fairly extreme and it really looks ugly when the icons are crooked compared to the rest of the UI. I always had immersive mode enabled on my XZ3 and after 3.5 years of daily use I have zero burn in. If anyone has ideas or suggestions to get immersive mode re-enabled on Android 12, I'd love to hear them.
UPDATE: I managed to hide the status bar with Xposed Edge Pro! I've set up a trigger to hide the status bar when the Xperia Home launcher loses focus and to unhide it when the launcher gains focus. This way, the home screen shows the clock, battery and notifications, but during app use there is no burn in from the status bar. It's basically how I had it set up on my XZ3, although I used Immersive Manager which unfortunately no longer works on Android 11 and higher. The only downside to using Xposed Edge is that you can briefly see the home screen reflowing when the status bar appears. Curiously, you can't see the other apps reflow when the status bar disappears again, even with doubled animation speed.
The phone buzzer is also really strong, to the point where if you have it on a hard surface like a table, it makes a lot of noise vibrating. I tried Vibration Tuner but it hasn't been updated in so long that it doesn't work. Are there any modern alternatives? The haptic feedback is too strong for my liking as well.
So what is it you used to sort the heating problems being rooted exactly? Was thinking of doing the same thing myself. Thanks for posting this btw!
JP10101 said:
So what is it you used to sort the heating problems being rooted exactly?
Click to expand...
Click to collapse
Just wait for the "AI" scheduler/governor to learn to throttle the device. It takes a few days but the heat is acceptable afterwards. It will never be as cool as a phone without heat issues (like the XZ3 or 1 II) but it doesn't impair daily app usage and the only overheating incident I've encountered the last few days was sitting outside in 30 degree heat leaving the phone in the direct sun, and I was impressed how quickly it recovered from that.
For me personally, the awesome camera and 120hz display ultimately won out over returning the phone. In an ideal world, Sony would have used the Snapdragon 8+ gen 1 which doesn't have thermal issues, and you could hope for a mid-generation refresh of the 1 IV with the 8+, but that probably won't happen. Like the reviews say, the phone does get warm and it throttles to keep the heat manageable, but once Adaptive Battery has had a few days to learn your usage pattern, it's probably not going to be so bad as to cause problems.
When you rooted, did it stop you from using the camera software that came with the phone by any chance?
No, the camera works 100% the same as before.
mufunyo said:
No, the camera works 100% the same as before.
Click to expand...
Click to collapse
That is great to know, thank you!
Is Viper4Android working? I think I installed AML, JamesDSP, and V4A to get it working on the 1 III.
mufunyo said:
Grab the unlock code from Sony
Click to expand...
Click to collapse
How'd you get the unlock code from Sony?
I went to their developer portal (https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/) but the Device dropdown to get the unlock code doesn't have the Xperia 1 IV in the list?
hahimot483 said:
Is Viper4Android working? I think I installed AML, JamesDSP, and V4A to get it working on the 1 III.
Click to expand...
Click to collapse
I'm sorry, but I'm not interested in Viper4Android myself and its installation looks a bit too involved to try out simply to be able to say if it works or not. I also don't have a custom recovery yet so I'm a bit wary about boot loops still.
aussiebum said:
I went to their developer portal (https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/) but the Device dropdown to get the unlock code doesn't have the Xperia 1 IV in the list?
Click to expand...
Click to collapse
Just select the Xperia 1 III from the list. The code will still work.
Thank you for letting us know!
I was wondering if you are going to try underclock the device to see how it reacts with the thermals?
hary232 said:
I was wondering if you are going to try underclock the device to see how it reacts with the thermals?
Click to expand...
Click to collapse
If and when there's enough developer interest in this device to develop a custom kernel or magisk overlay to tweak the thermals, I might try that. For now I'm satisfied with thermals and battery life, it's not nearly as bad as it was with the Z5 back then. I run battery care at 80% max charge most days and reach about 40-20% charge at bedtime, and on days where I'm out of the house for a long time I disable battery care for a full 100% charge to extend battery life for heavy usage which works well. I'm mostly just happy to have a camera that's a joy to use again after using the XZ3 which was extremely mediocre to the point where taking photos was just not enjoyable.
hary232 said:
Thank you for letting us know!
I was wondering if you are going to try underclock the device to see how it reacts with the thermals?
Click to expand...
Click to collapse
Even with the stock kernel, once rooted, you can easily use Franco Kernel Manager to disable some cores which will immensely improve any heating issues you might have.
I want to flash HongKong firmware but my phone is now using China firmware which version is higher than HongKong one, once I flash it my phone goes black. So I wonder if I unlock bootloader, can I flash lower firmware?
You should be able to downgrade to any official firmware with FlashTool without unlocking your bootloader. If your phone goes black it's more likely you're flashing incorrect firmware. You realise there are two distinct hardware variants of the 1 IV, maybe you picked the wrong one? There's the XQ-CT54 and the XQ-CT72. Mine is the XQ-CT54.
mufunyo said:
You should be able to downgrade to any official firmware with FlashTool without unlocking your bootloader. If your phone goes black it's more likely you're flashing incorrect firmware. You realise there are two distinct hardware variants of the 1 IV, maybe you picked the wrong one? There's the XQ-CT54 and the XQ-CT72. Mine is the XQ-CT54.
Click to expand...
Click to collapse
It can't downgrade once you upgrate to any newer version... My phone goes black either unlocked and locked BL. I can only recover it using Xperia Companion
mufunyo said:
Just select the Xperia 1 III from the list. The code will still work.
Click to expand...
Click to collapse
Thanks, I got the code generated, but now I'm stuck with getting the Fastboot Drivers installed.
The Sony "OEM Drivers" ADB drivers work fine when the phone's powered on, but when I switch over to Fastboot mode (vol up, plug in usb, blue led comes on), it's not recognised.
Sony's "fastboot driver" inf from 2014 does recognise the device, but I can't use that ancient inf with the latest Google USB drivers (Windows refuses to install the drivers due to hash not matching).
Would you be able to point or supply the fastboot driver you used to connect up your Xperia 1 IV?
EDIT: rebooting to fastboot via ADB brings up the "android fastbootd", but this doesn't seem like the actual Sony fastboot environment, so still can't oem unlock :/
Nevermind, finally figured it out. Followed the section about force-installing the Google Android Bootloader driver as per https://www.xda-developers.com/download-android-usb-drivers/ and that worked.
As this is the *only* current gen SD 8 phone with both a 3.5mm jack *and* an SD card slot, it may end up being my next upgrade. As my third hard requirement is at least the possibility of rooting it(I always do this before a phone can become my daily driver), this does a lot to seal the deal, so to speak, and is extremely helpful besides.
With my current phone(a Motorola g100) experiencing digitizer errors, even still under warranty, I may just upgrade and sell it after the warranty repair.
mufunyo said:
MinMinGuard 2.1.1
Click to expand...
Click to collapse
How did you get MinMinGuard to work? It seems to do nothing on my Xperia 1 IV. Are you using the auto mode?
Bad experience with Z5? I have had my Z5 and Z5 Compact for 7 years now. Works flawlessly, never overheated. Maybe you have a faulty model?
mazany said:
How did you get MinMinGuard to work? It seems to do nothing on my Xperia 1 IV. Are you using the auto mode?
Click to expand...
Click to collapse
It's interesting, when I look in the MinMinGuard interface it doesn't seem to be working (it's showing it blocked 0 ads), but I don't get any ads in apps so I just assumed it was working anyway. I have to admit I'm also using AdAway which blocks ads using the hosts file (of course making sure to install Magisk Systemless hosts first), which could be making MinMinGuard redundant.