Hi guys,
On my old OnePlus X and OnePlus 6T thanks to Oxygen OS I could set actions depending on the presses on the navigation bar (for example: long press the home button to lock the screen) in the settings but I can't seem to find this option on the settings app of my OnePlus Nord 2.
Is it hidden somewhere?
If it's not possible anymore out of the box, are there any apps, adb commands or accessibility hacks to lock the screen when I long press the home button?
I really miss this feature, I was able to lock the screen without touching the power button from anywhere (while being in an app, while texting, etc.).
Thanks!
Do you mean this?
Badtz-Maru said:
Do you mean this?
Click to expand...
Click to collapse
No that's not it.
There was a setting on previous OnePlus phones that simply locked the screen (as pressing the power button would do) by long pressing the home button (the round one in the middle).
I can't seem to find this setting on my Nord 2 even though it is present on my OnePlus X, 6T and even on my friends 8T...
The Oxygen OS version running on the Nord 2 is completely different from all the other OnePlus phones, which sucks...
This is probably why:
https://www.slashgear.com/oneplus-nord-2-oxygenos-is-built-on-top-of-oppo-coloros-25683993/
I use on Nord 2 , Double Tap to Sleep and Double Tap to Wake . DTS from Microsoft Launcher and DTW from own system . Both are working flawless .
muppetz said:
I use on Nord 2 , Double Tap to Sleep and Double Tap to Wake . DTS from Microsoft Launcher and DTW from own system . Both are working flawless .
Click to expand...
Click to collapse
Yes I also do that but this isn't exactly what I want since you have to return to the homescreen and only then you can double tap to lock. I want to be able to lock my device while in an app and without touching the power button.
No those actions are sadly missing , the OS in the Nord2 is missing a lot of OxygenOS previous features because it's now merged with ColorOS and they decided to not include a lot of usefull features from both OS and that's very stupid IMO .
Pouic said:
No those actions are sadly missing , the OS in the Nord2 is missing a lot of OxygenOS previous features because it's now merged with ColorOS and they decided to not include a lot of usefull features from both OS and that's very stupid IMO .
Click to expand...
Click to collapse
Yeah that's what I figured, that sucks
Just returned the phone because of that (and other reasons too for example slight black crush on low brightness and very bad battery drain especially on standby/when I sleep)...
I have a Nord CE and even though it lags sometimes in the UI it's overall way nicer (screen and battery life are fantastic). I just miss the alert slider on the CE and the vibration motor sucks but it's not a big deal to me.
I think the black crush in low brightness is a common issue with a lot of OLED panels , my previous oled phones had exactly the same behaviour .
As for the standby drain it must be an app you have, during the night I get 0.5~0.7% per hour on my nord 2 , and I easily get 2 days with a single charge and moderate usage.
But the fake OxygenOS with so many useful features missing is clearly very annoying for me, if the Android 12 update don't bring anything new I think i'll switch for a Pixel 6
Pouic said:
I think the black crush in low brightness is a common issue with a lot of OLED panels , my previous oled phones had exactly the same behaviour .
As for the standby drain it must be an app you have, during the night I get 0.5~0.7% per hour on my nord 2 , and I easily get 2 days with a single charge and moderate usage.
But the fake OxygenOS with so many useful features missing is clearly very annoying for me, if the Android 12 update don't bring anything new I think i'll switch for a Pixel 6
Click to expand...
Click to collapse
Yeah the battery life would probably have settled after 2-3 more days of use but the fake feeling OS really put me off.
The black crush issue is indeed plaguing OLED displays it seems, I tried the 7T, 8, 8T and Nord 2 in the span of a year and sent every single one back after a few days because of it and stayed with my 6T which had a perfect screen.
I recently bought the Nord CE to give it at try and the screen is also perfect, so now that I've finally won the OLED lottery I'm keeping it despite it lagging sometimes compared to my 6T.
I feel like the black crush issues are worse on high refresh screens: the 8T screen (120Hz) had the worst black crush and all of the 90Hz had it too but less pronounced (except for my Nord CE). I rarely see black crush on older 60Hz devices (My 6T, my girlfriends Oppo Reno 2, older Samsung phones, etc.).
I miss this feature too. Could you please share it with me if you find a solution?
platway said:
I miss this feature too. Could you please share it with me if you find a solution?
Click to expand...
Click to collapse
Depending on which Android version you are: when rooted (Magisk) activate LSPosed and then GravityBox (R). This has all the options you need! DO. NOT. PUT. YOUR. CLOCK. IN. THE. MIDDLE!!! This will bootloop your device! All other GravityBox features seem to work.
On A12 there is no official GravityBox but in LSPosed you'll find an unoffical version for Android S. Not a lot works but buttoncontrol does!
exis_tenz said:
Depending on which Android version you are: when rooted (Magisk) activate LSPosed and then GravityBox (R). This has all the options you need! DO. NOT. PUT. YOUR. CLOCK. IN. THE. MIDDLE!!! This will bootloop your device! All other GravityBox features seem to work.
On A12 there is no official GravityBox but in LSPosed you'll find an unoffical version for Android S. Not a lot works but buttoncontrol does!
Click to expand...
Click to collapse
So I have to root my phone first.
In case you want to use GravityBox: yes.
exis_tenz said:
Depending on which Android version you are: when rooted (Magisk) activate LSPosed and then GravityBox (R). This has all the options you need! DO. NOT. PUT. YOUR. CLOCK. IN. THE. MIDDLE!!! This will bootloop your device! All other GravityBox features seem to work.
On A12 there is no official GravityBox but in LSPosed you'll find an unoffical version for Android S. Not a lot works but buttoncontrol does!
Click to expand...
Click to collapse
Any solution you know for A13? I have a OP9P with A11 but decided to update OS and I miss this feature a lot, both long pressing home button to open notification bar and double press home button to lock screen. Don‘t know why they took out these features, they were really useful. (Im rooted but I didnt found GB for A13 or any other magisk module solution yet)
Unfortunately this was all I have. My OP9 is running A12 with /e/OS
Does anybody know whether LineageOS 20 has this long press mapping feature? I'm getting really annoyed with this and the fingerprint brightness bug in OOS12 on my OP7T. About ready to jump ship.
xdapepe said:
Hi guys,
On my old OnePlus X and OnePlus 6T thanks to Oxygen OS I could set actions depending on the presses on the navigation bar (for example: long press the home button to lock the screen) in the settings but I can't seem to find this option on the settings app of my OnePlus Nord 2.
Is it hidden somewhere?
If it's not possible anymore out of the box, are there any apps, adb commands or accessibility hacks to lock the screen when I long press the home button?
I really miss this feature, I was able to lock the screen without touching the power button from anywhere (while being in an app, while texting, etc.).
Thanks!
Click to expand...
Click to collapse
Related
Hi Everyone,
Why Huawei didn't activate this function to their high end phone. THIS IS VERY USEFUL.
Anyone, manage to activate this on their rooted mate 10 pro?
Think you posted in the wrong section, only way is to install nova launcher as it works with this
ant78 said:
Think you posted in the wrong section, only way is to install nova launcher as it works with this
Click to expand...
Click to collapse
No, nova launcher has no double tap to wake. It has only double tap to sleep. I think you are wrong. If there is, pls guide me and appreciate it much.
hi man with the system update. 10 pro will support this function
i believe and u?
i am chinese i will Positive feedback on this problem to huawei
because of the emui8.0 Just released i also found some problen like wifi connect、Photo Red，Electrical abnormality .
得之坦然 said:
hi man with the system update. 10 pro will support this function
i believe and u?
i am chinese i will Positive feedback on this problem to huawei
because of the emui8.0 Just released i also found some problen like wifi connect、Photo Red，Electrical abnormality .
Click to expand...
Click to collapse
Thanks for the positive reply. Huawei is to slow in improving their software update
得之坦然 said:
hi man with the system update. 10 pro will support this function
i believe and u?
i am chinese i will Positive feedback on this problem to huawei
because of the emui8.0 Just released i also found some problen like wifi connect、Photo Red，Electrical abnormality .
Click to expand...
Click to collapse
Which system update are you talking about?
ant78 said:
Which system update are you talking about?
Click to expand...
Click to collapse
Some weeks ago someone hinted at some code in the firmware which was supposed to handle double tap to wake. But there's no confirmation anywhere that Huawei will ever enable or further develop that code, just assumptions.
in Mate 8 forum there is a thread about enabling double tap to wake through some modifications on build prop.
That requires Root but I have no idea if that procedure could be implemented on mate 10
https://forum.xda-developers.com/mate-8/general/enable-double-tap-to-wake-t3312676
pasil.pt said:
in Mate 8 forum there is a thread about enabling double tap to wake through some modifications on build prop.
That requires Root but I have no idea if that procedure could be implemented on mate 10
https://forum.xda-developers.com/mate-8/general/enable-double-tap-to-wake-t3312676
Click to expand...
Click to collapse
Hi, have tried it week ago but no luck.
eabrillos said:
Hi, have tried it week ago but no luck.
Click to expand...
Click to collapse
It's probably because of the screen technoligy that's being used.
I thought I'd miss the double tap to wake after coming from a oneplus one but the fingerprint sensor on this phone is so good I haven't looked back, one press and it's unlocked
mad.jack10 said:
I thought I'd miss the double tap to wake after coming from a oneplus one but the fingerprint sensor on this phone is so good I haven't looked back, one press and it's unlocked
Click to expand...
Click to collapse
Yes it really good but it is at the back of the phone.
mad.jack10 said:
I thought I'd miss the double tap to wake after coming from a oneplus one but the fingerprint sensor on this phone is so good I haven't looked back, one press and it's unlocked
Click to expand...
Click to collapse
Me too
Yes, the sensor is good, but kind of difficult to access while phone is mounted in a car - double tap to wake would be nice then, I miss it from my OnePlus X.
hello to all.... is possible that even in march update official, for huawei mate pro, is not present double tap to wake? other alternatives drain many battery... i hope a solution in last 4 monthes in this post
my solution
Hello,
As a former LG G2 user I've quickly begun to miss the double tap to wake/sleep | knockon/off function with my Huawei Mate 10 Pro. So after lots of investigations and app trials here's my solution which seems to perform pretty well in my opinion.
After trying many apps I've encountered the so called 'Always on AMOLED | Edge lighting'.
Here's my setup on the mate 10 pro (emui 8.0.0, android 8.0.0, build 8.0.0.157 C432) first:
1) Disable smart cover
2) Disable pick to wake
3) Disable pulse light (it won't work and we'll use app's notification handling which is great in my opinion)
4) Disable always on display information
5) After installing the app (VERY IMPORTANT!):
- Go to ignore battery optimisation in android's settings and add this app to the Allowed list
- Go to battery / launch - then Manage manually the amoled app:
* set to on - auto launch
* set to on - secondary launch
* set to on - run in background
To quickly find the upper settings use the search bar in the settings menu.
Then in the app (v. 2.1.7 tested):
1) I've made a fully black background instead of a clock - upto your flavor
2) Enable the POCKET MODE! This actually saves battery a lot since if proximity sensor is covered the screen is completely shut down. When you sleep/want to save battery place the phone with face down - sounds as no problem to me..
3) Brightness is set to 10 or so - again upto you, the less the better for the battery
For double tap to lock I use a widget placed all over the screens where there are no icons - sounds annoying but once settled it works flawlessly. Here's the widget I use - DTS widget Skynet Software.
To be honest I've found it from this forum.
Share your experience as I might have missed something.
P.S Somehow the power button won't lock the screen now but I don't use it at all anyway, so no problem to me..
P.S.2 I would have bought another LG phone if only they have kept the IR Blaster but that's another story..
mad.jack10 said:
I thought I'd miss the double tap to wake after coming from a oneplus one but the fingerprint sensor on this phone is so good I haven't looked back, one press and it's unlocked
Click to expand...
Click to collapse
Same, I only like double-tap to wake on my phones without fingerprint sensors. On my mate 10 and Xiaomis, whether front or back, I am prone to using the fingerprint sensors, and they bypass the lock screen too.
Of course, it's a nice feature to have that doesn't drain battery, all my phones, except Huawei, have dt2w.
The recent FunTouch OS 12 has a lot of features missing. It feels like IQOO has rolled up the updates in a hurry.
1. No Android 12 Clock widget.
2. No Quick Panel tiles like Android 12.
3. Dark mode not getting applied on App Drawer.
4. Etc etc
Bloody hell, when will we get Origin OS for Indian market.
This device has so much potential if they just unlock the bootloader for installating custom roms
Disabled animations in Developer menu doesn't get applied either
Also, home screen is not coming from many widgets like the one we get by swipimg right from left edge
This seems like an Alpha version without much testing and stitching with animations quite annoying like dark mode not applying to app drawer
This is almost the the first few versions when we bought the device during launch. Only after one June or July upgrade things became like a release version. Established that IQOO OS team for IQOO 7 releases updates without proper testing and going through beta testing as such issues were never encountered in IQOO 3 with IQOO OS which people for some reason criticize
Witnessing huge flashes of brightness fluctuations at night even when automatic brightness is turned off.
Still can't find a way to switch off Accessibility button
Prankey said:
Witnessing huge flashes of brightness fluctuations at night even when automatic brightness is turned off.
Still can't find a way to switch off Accessibility button
Click to expand...
Click to collapse
Same here. Gets blindingly bright in the middle of the night. My phone also keeps crashing atleast 3 times a day. Waiting for a fix update.
abnormalindian said:
Same here. Gets blindingly bright in the middle of the night. My phone also keeps crashing atleast 3 times a day. Waiting for a fix update.
Click to expand...
Click to collapse
Yup, same here as well. Plus sometimes when I enable battery saver the brightness also increases even if auto brightness is turned off and manual bright is set to lowest possible value.
I still have similar issues on my Vivo X80 Pro and many familiar features like the new Control Center are still missing! What shoud that? OriginOS would be so much better, why do you have to develop such a bad operating system internationally. I don't get it and I'm actually very, very excited about the X80 Pro but the software totally ruins the experience!
Does anyone know of a way to make the 3-button navigation bar taller/bigger on Android 12? I have magisk and lsposed, but none of the older solutions work (eg GravityBox). I also haven't been able to find any xposed modules that work. I tried gesture navigation but I prefer the 3 buttons. I also increased the touchscreen sensitivity.
I just upgraded to Pixel 6 from Pixel 4XL but I'm noticing that the navigation bar buttons don't always respond as it did on the Pixel 4XL. I'm frequently having to press the nav bar buttons again bc they're not registering my touch. I'm thinking that it's because the height of the nav bar is short, but I've also never had an issue on the 4XL. It might be due to the my screen protector, but I don't have any issues on the other areas of the touchscreen and my 4XL also had a screen protector without issue. Thx!
i would kill for a mod that kept the navigation bar always visible, personally i think google was STUPID to push the no physical buttons for android design plan.
neo_lithic3K said:
Does anyone know of a way to make the 3-button navigation bar taller/bigger on Android 12? I have magisk and lsposed, but none of the older solutions work (eg GravityBox). I also haven't been able to find any xposed modules that work. I tried gesture navigation but I prefer the 3 buttons. I also increased the touchscreen sensitivity.
I just upgraded to Pixel 6 from Pixel 4XL but I'm noticing that the navigation bar buttons don't always respond as it did on the Pixel 4XL. I'm frequently having to press the nav bar buttons again bc they're not registering my touch. I'm thinking that it's because the height of the nav bar is short, but I've also never had an issue on the 4XL. It might be due to the my screen protector, but I don't have any issues on the other areas of the touchscreen and my 4XL also had a screen protector without issue. Thx!
Click to expand...
Click to collapse
Did you find anything in the themes and mods section that could help you?
Google Pixel 6
The Google Pixel 6 is a 6.4" phone with a 1080x2400 resolution display. The Google Tensor chipset is paired with 8GB of RAM and 128/256GB of storage. The main camera is 50+12MP and the selfie camera is 8MP. The battery has a 4614mAh capacity.
forum.xda-developers.com
vandyman said:
Did you find anything in the themes and mods section that could help you?
Google Pixel 6
The Google Pixel 6 is a 6.4" phone with a 1080x2400 resolution display. The Google Tensor chipset is paired with 8GB of RAM and 128/256GB of storage. The main camera is 50+12MP and the selfie camera is 8MP. The battery has a 4614mAh capacity.
forum.xda-developers.com
Click to expand...
Click to collapse
no unfortunately.
I'm actually thinking of returning my Pixel 6. It's not performing as well as I expected and not any faster than my Pixel 4XL.
neo_lithic3K said:
no unfortunately.
I'm actually thinking of returning my Pixel 6. It's not performing as well as I expected and not any faster than my Pixel 4XL.
Click to expand...
Click to collapse
check out a benckmark to see if its really not faster. sad thing is oyu get more ram, more speed int he cpu , but google loads it down with 400MB of google play services and other frills that make it run like an old woman from a mugger... far to hard for no benefit.
nutzfreelance said:
check out a benckmark to see if its really not faster. sad thing is oyu get more ram, more speed int he cpu , but google loads it down with 400MB of google play services and other frills that make it run like an old woman from a mugger... far to hard for no benefit.
Click to expand...
Click to collapse
I did check the benchmarks and it did show the 6 being faster/better than the 4xl, but I didn't notice any difference in most cases. (Though, I did notice my swiftbackup being much faster on the 6 when I was backing up all my user apps.)
Right, I was thinking the 16GB ram and better cpu would translate into very noticeable performance.
Main reason that I upgraded was because my pixel 4 xl has been draining battery fast lately, so I thought it was time to upgrade... But noticed the same issue on my pixel 6. Couple that with the other pixel 6 issues and I'm wondering whether it's really worth it to keep the 6.
nutzfreelance said:
i would kill for a mod that kept the navigation bar always visible, personally i think google was STUPID to push the no physical buttons for android design plan.
Click to expand...
Click to collapse
Not sure if I'm understanding you correctly. There is a way to switch to the 3-button navigation bar in android settings. That's what I'm using now.
neo_lithic3K said:
Not sure if I'm understanding you correctly. There is a way to switch to the 3-button navigation bar in android settings. That's what I'm using now.
Click to expand...
Click to collapse
i know but it constantly disappears in most of my apps and its a pain to bring back
nutzfreelance said:
i know but it constantly disappears in most of my apps and its a pain to bring back
Click to expand...
Click to collapse
oh that's very odd. I've never had that issue before in any phone, any android version, or any rom (custom or stock). The only time it disappears is when it's intended -- if I'm playing a full screen game, watching a full screen video, etc.
In case anyone's interested, I was able to sort-of resolve this issue by switching to the 2-button navigation (via magisk, since 2-button is not an option in settings). I don't seem to have the nav bar issue anymore.
I do believe it's your screen protector causing your main issue. I've noticed they can be temperamental near the edges of the screen. On my LG V40 thin Q, I used the left-hand version of the keyboard, because, the right side letters & numbers were so hard to register a tap. In your case, it's likely at the bottom. Personally, I'm not using a screen protector on my pixel 6, since I own it outright, instead of payments on the LG. But, you do need to be more on target tapping the nav buttons.
neo_lithic3K said:
Does anyone know of a way to make the 3-button navigation bar taller/bigger on Android 12? I have magisk and lsposed, but none of the older solutions work (eg GravityBox). I also haven't been able to find any xposed modules that work. I tried gesture navigation but I prefer the 3 buttons. I also increased the touchscreen sensitivity.
I just upgraded to Pixel 6 from Pixel 4XL but I'm noticing that the navigation bar buttons don't always respond as it did on the Pixel 4XL. I'm frequently having to press the nav bar buttons again bc they're not registering my touch. I'm thinking that it's because the height of the nav bar is short, but I've also never had an issue on the 4XL. It might be due to the my screen protector, but I don't have any issues on the other areas of the touchscreen and my 4XL also had a screen protector without issue. Thx!
Click to expand...
Click to collapse
I know it is late but I understand what you mean .
It is not the navigation bar that looks small . When you enable Task Bar it will make Navigation Bar smaller to the side . So to disable it go to.
Settings > Display > taskbar. Uptick it.
Now you have the normal long navigation bar
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.
So here's a ROM that i would recommend even tho it's in beta Corvus OS it's android 12 and everything works even the Camera but sadly not the greatness of Sony's Camera app...i personally haven't tried it with the Custom Kernel Kirisakura just yet but i will and report back on here if they place nice together...Magisk also works great with this ROM you just have to be careful what you flash...
Hopefully our device will be fully supported soon.
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Ainz_Ooal_Gown said:
Yeah this is the only ROM that i found that legit decided to be custom and not just copy/pasta of Pixel Experience without the GCAM and a different name.....for what I use my phone for it's 100% functional...but it's far from being perfect for everyone rn...
Click to expand...
Click to collapse
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
UsernameNotRecognized said:
Yeah, this is why I've been very hesitant to install to install GSI ROMs, all the issues I've mentioned are because the X1 III is not the same as most other devices.
Wake to tap? Device specific thing.
Native res issues? X1III specific.
No built in battery health? Not device specific, devs pls
Camera issues? Device specific.
I think I'll drop the higher res as that will remove the most jarring of issues. The camera is whatever as it will not improve by switching to PE and double tap to wake is meh. Annoying at worst.
Click to expand...
Click to collapse
True that...but hey it's there Incase people get bored lol
UsernameNotRecognized said:
Just putting down some thoughts here.
Double tap to wake is borked, the setting already hints that it is unlikely to work and I can confirm this.
Forcing native res works rather poorly. On reboot I need to reset the dpi to make the GUI play nice, but some things remain iffy. Such as:
Gesture navigation still thinks preview windows should be the lower res, not native (looks poor, see attached images)
Some random visual glitches that cause a silent crash + restore, it's not critical but you can see it happening
No built-in battery health (as in limiting it), have to use something external (AccA)
Camera quality is way worse compared to stock. I don't mind as much as I don't care a lot, but quality regression is very significant (if I have to quantify it, I would accept 20-30%, but this feels more like 60%)
The GCAM's I've found that don't immediately crash (not many) all have serious bugs
No camera app found that plays nice with front camera, hope you weren't planning on taking pictures with the front camera
Edit: For 6 you can actually use the native app. Performance is super bad though.
To not sound too much like a downer I'll also put in some "niceties" compared to stock.
Holding volume button to seek is now native
OTA work again
Good visual eyecandy for charging, locking and more
No bloatware galore
Much much finer control over lots of little things, especially status bar is very nice
Other things:
The default launcher is a bit lacking, so I installed Nova 7, but this still has some shenanigans with force reloading and short unresponsiveness with gesture navigation. Very annoying, but I'm quite sure this is not the fault of the ROM. Just hoped this was improved (suggestions welcome)
If someone found a good GCAM please share, the ones I've found are either broken or seriously lacking.
It seems that sometimes the phone does not respond to my finger until I press the button. This could be intentional to prevent accidental unlocks / phone being locked for X seconds because lots of "bad" fingerprints detected.
Click to expand...
Click to collapse
Alright some more shenanigans and needing to do a clean install further I do know some more things now.
1. is still broken, I'll try flashing a different kernel perhaps.
2. It's actually not so bad. It will remember and auto apply on reboot after a couple seconds. Gesture and notification bar may be slightly borked, but that's fixed fast by reloading system UI and switching between gesture and button navigation. The thing about recents has been resolved by switching to a different launcher with it's own quickswitch (lawnchair).
3. Acca works fine.
4/5/6 Nothing.
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
UsernameNotRecognized said:
Another update.
2 is fine. Just don't use the built in launcher while forcing 4k. Just use lawnchair or something (+ quickswitch).
On another note, automatic brightness does NOT appear to work. This is quite the massive issue. I'm honestly a bit baffled how I haven't noticed until today.
AOD is also quite broken, while the phone is on the wireless charging and being ratiod to 90% it will continously blink. That's super annoying as I normally use AOD to check if I got a message, if it blinks it takes my attention, effectively defeating the entire purpose of AOD. *Groan*
These issues are really starting to stack up by now, I'm seriously considering reverting to stock. I'm really worried something else won't be working once I need it in the future.
Click to expand...
Click to collapse
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
thatguy222 said:
No autobrighness may be caused by not having an overlay. I've also been annoyed by that on Pixel Experience. Can you create a fresh overlay for this phone and do a pull request with phhuson's repo? (I assume that's what must done)
Click to expand...
Click to collapse
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
UsernameNotRecognized said:
Well, sort of.
[Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"
Kirisakura-Kernel for the Sony Xperia 1 III Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Sony Xperia 1 III aka Sagami. Sagami is the internal codename for this years development platform of Sony Mark III devices. Please...
forum.xda-developers.com
Issue is that the "official" info provided by Sony seems to explicitly disable double tap to wake.
This makes absolutely no sense as double tap to wake works fine in the vanilla ROM.
Maybe someone can confirm this? It's been some time.
Click to expand...
Click to collapse
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
kevinmcmurtrie said:
It's available in stock but it has never worked correctly. The proximity sensor doesn't disable it! There's a "Prevent accidental operations with screen off" setting as the world's dumbest work-around. That puts a keyboard and alert on the screen while you're walking. It stops emergency butt-dialing but the battery still runs down.
Click to expand...
Click to collapse
A what now? I do recall the proximity sensor not working really well with dt2w but at least it worked and I didn't notice some significant battery drain.
I did see some things about dt2w being disabled because the touch interface is powered when the screen is powered and this can't be decoupled. I'm not sure if this applies to this phone though.
Regardless, it shouldn't really matter as the X1 III is an OLED screen anyways. So as long as it's full black it should be fine(?)
I'm not asking for the perfect solution and if battery drain slightly increases that's a worthwhile investment to me. At least provide the option. Don't decide what I want because it has potential side-effects (just warn or something lol).
Actually I'm going out on a limb and stating that dt2w should be enabled by default if the device's screen is an OLED screen. Overlay and device specific things be damned.