No Wake On Charge keeps screen off when usb/charger cable is plugged in or unplugged. This module works fully only on Samsung Galaxy S5 as it uses non standard (AOSP) way of waking up the display.
I tried to use various other Xposed modules but none removed the plug in wake.
It works like this:
Screen wake on plug in - changes android.os.PowerManager#newWakeLock(ACQUIRE_CAUSES_WAKEUP | SCREEN_BRIGHT_WAKE_LOCK, "charger plug") to PARTIAL_WAKE_LOCK only (based on fix by @tdunham http://forum.xda-developers.com/showthread.php?t=2799050). Again, this is S5 only fix.
Screen wake on unplug - sets config_unplugTurnsOnScreen to false (this is well known and used solution)
Beep on plug in - disables com.android.systemui.power.PowerUI#playSound(1)
There are few more hooks in versions 0.2 and higher (supports wireless charging as well).
This (old) module is designed for Samsung Galaxy S5 running stock Android 4.4.2. If you need compatibility with newer version of Android, use this module: http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109 which works with Android 5.0 (and newer once released).
Great job! Finally my T-Mobile note 3 running X-note doesn't wake up when I plug the charger. Only module that works on touchwiz and I've tried them all.
moneytoo said:
No Wake On Charge keeps screen off when usb/charger cable is plugged in or unplugged. This module works fully only on Samsung Galaxy S5 as it uses non standard (AOSP) way of waking up the display.
I tried to use various other Xposed modules but none removed the plug in wake.
It works like this:
Screen wake on plug in - changes android.os.PowerManager#newWakeLock(ACQUIRE_CAUSES_WAKEUP | SCREEN_BRIGHT_WAKE_LOCK, "charger plug") to PARTIAL_WAKE_LOCK only (based on fix by @tdunham http://forum.xda-developers.com/showthread.php?t=2799050). Again, this is S5 only fix.
Screen wake on unplug - sets config_unplugTurnsOnScreen to false (this is well known and used solution)
Beep on plug in - disables com.android.systemui.power.PowerUI#playSound(1)
No Wake On Charge is also available from Xposed Module Repository.
Click to expand...
Click to collapse
Does it actually work? I just installed and still wakes up. I use wireless charging though not USB one.
@moneytoo: Many many thanks! I want report that it works very well with my S4active - google-edition (no touchwitz). Was not possible with any other module before
@moneytoo I can confirm that this mod also works on the T-Mobile variant of the LG G3
Thanks!!
artisticcheese said:
Does it actually work? I just installed and still wakes up. I use wireless charging though not USB one.
Click to expand...
Click to collapse
It's working with my Verizon Developer Edition S5 with wireless charging.
Works great on Sprint GS4 (SPH-L720T). Thanks! :good:
isnt this already a feature built in to android or gravity box ? Im not sure if it is or not..
VZW Note3
werks. Thank you kind sir.
SystemErrorOne said:
isnt this already a feature built in to android or gravity box ? Im not sure if it is or not..
Click to expand...
Click to collapse
Yeah, such option is in Cyanogenmod and most probably other ROMs as well. GravityBox and other modules also offer this but nothing was working fully with TouchWiz.
I'll test on my xperia :good:
Thought I would give it a shot ? on TW custom stock Super S4 rom on galaxy S4 SPH-L720, didn't work. Don't have GravityBox.
@moneytoo:
For my device it seems to be enough to set the unplugTurnsOnScreen. The handleLoadPackage part even throws a cant find class exception. Can you please provide an option to set boolean only?
Works great on my T-Mo S4 running Insane Kit Kat
Sent from my Insane S4.
I didn't expect this to work on the HTC One (M8), as it seems to be a Samsung tweak. However I found a non-Xposed app SnooZy Charger that does the job fairly well. So, if the plugin doesn't work for you, this is a viable alternative.
How do I know that the module is working?
Sent from my C5303 using XDA Free mobile app
defim said:
@moneytoo:
For my device it seems to be enough to set the unplugTurnsOnScreen. The handleLoadPackage part even throws a cant find class exception. Can you please provide an option to set boolean only?
Click to expand...
Click to collapse
There are already multiple modules dealing with this config option alone (at least GravityBox, Wanam Xposed, ScreenTweaks, Xposed Additions, Wireless Charging Xposed...) so I don't think it's worth providing anything more. This module is intended solely for S5 (maybe for few more TouchWiz devices).
Thx, GravityBox has no such option (i thought first, i translated not correctly), Xposed Additions & Wanam Xposed a lot to much options, Wireless Charging does not work (im charging with usb), ScreenTweaks is for Sony Xperia
So it would be nice if you could do it, but i'm also able to do it my self if it's okay for you
defim said:
Thx, GravityBox has no such option (i thought first, i translated not correctly), Xposed Additions & Wanam Xposed a lot to much options, Wireless Charging does not work (im charging with usb), ScreenTweaks is for Sony Xperia
So it would be nice if you could do it, but i'm also able to do it my self if it's okay for you
Click to expand...
Click to collapse
I'm not into adding any additional functionality as it works perfectly as I need and once you start adding options to disable plug/unplug wakes only, you will also enable/disable sounds. Then someone will want to change the sounds. Then someone will want to blink LED instead... Feel free to do anything you want to.
Doesn't disable beep on plugin on T-Mobile G3
Related
Introduction:
Sequence unlock is an Xposed module which allows you to unlock your phone with a sequence of volume keys (Example: U U D ).
With this module you can unlock your phone in a simple and nifty way and avoid using the default android lockscreen altogether.
You will need to set up a sequence of your choice in the module settings. The default sequence is: U U U
Features include:
Unlock device even when the screen is off.
Disable default wake buttons (Power button, home button etc.)
Bypass the android screenlock
Compatibilty:
This app is compatible with 4.1+ AOSPish devices only (excluding lollipop).
Tested devices:
Sony Xperia 4.2
Samsung Galaxy S3 4.4 (CM11)
BUGS:
Sequence Unlock is currently not compatible with the Physical button music control module.
Download:
Note: I had to change the package name to differentiate the module from it's PRO version. Sorry for the inconvenience.
http://repo.xposed.info/module/com.mb14.sequenceunlock.lite
PRO version:
You can buy the PRO version available on Google Playstore to support development (Being a college kid, I don't earn much).
It comes with extra features like:
Set sequence timeout interval
Vibrate on failed unlock attempt
Changelog
Code:
Changelog:
1.6
Fixed deep sleep bug
1.5
Added support for OPO CM11S.
Fixed magnetic lid wake bug.
Miscellaneous bug fixes
1.4
Fixed the lock screen bypass bug
1.3
Initial release
WOW! nice one! But do I need to wake up the screen in order to unlock or i just press sequence of the volume button?
a4apple said:
WOW! nice one! But do I need to wake up the screen in order to unlock or i just press sequence of the volume button?
Click to expand...
Click to collapse
You don't need to wake up the device to unlock. You can enter the sequence even when the screen is off
You will be my saviour!!!
my so called college sometime checks whether the device is in switch off mode or not...
this module will help me to set a pattern to wake !!!!
YAY!!! Hell Yeah
What happens when you're playing a song? Can you still unlock?
Sent from my SM-G900F using XDA Premium 4 mobile app
aHecticLife said:
What happens when you're playing a song? Can you still unlock?
Sent from my SM-G900F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can unlock the phone even if music is playing in the background. But the keys pressed will affect the volume of your music app.
So it isn't compatible with Lollipop yet? Is it?
Ciao600 said:
So it isn't compatible with Lollipop yet? Is it?
Click to expand...
Click to collapse
It won't work on lollipop as of now but I'll release an update as soon as possible.
not working on Xperia Z stock 4.4.4
Bn 292. Only turns screen on, no unlock. Also not compatible with "physical button music control" module (sequence module only works with that module disabled)
mb-14 said:
You can unlock the phone even if music is playing in the background. But the keys pressed will affect the volume of your music app.
Click to expand...
Click to collapse
Sebi673 said:
Bn 292. Only turns screen on, no unlock. Also not compatible with "physical button music control" module (sequence module only works with that module disabled)
Click to expand...
Click to collapse
Almost every phone has the physical button music control, poweramp integrated that aww man.
Did you try it? He's talking about the xposed module "physical button music control". So chances are it works with music players that use these controls.
Sent from my Boeffla powered Slim GT-I9300
Sebi673 said:
Bn 292. Only turns screen on, no unlock. Also not compatible with "physical button music control" module (sequence module only works with that module disabled)
Click to expand...
Click to collapse
I've fixed the lockscreen unlocking bug in version 1.4. As for the incompatibility with the Physical button music control module, I'll try fixing the bug and release an update as soon as possible.
Working like a charm with MT6572 phone :good:. Every function is working great (including unlock from deep sleep)! This is some cheap non-branded china phone with Android 4.2 just for you to know.
Edit: It is also working with Galaxy Gio (s5660) on CM11 (Android 4.4.4). (Including unlock from deep sleep).
mb-14 said:
I've fixed the lockscreen unlocking bug in version 1.4. As for the incompatibility with the Physical button music control module, I'll try fixing the bug and release an update as soon as possible.
Click to expand...
Click to collapse
Awesome I'll test it and report any found bugs. Physical button music ctrl Module doesnt have mapping over single volume button click, yet it somehow breaks functionality as it follows - when phone is in dock - volume buttons act as Wake trigger (only when docked - native behaviour) but with that module nothing happens on vol but. press. And while Phys. but. M Ctrl was activated, Sequence Unlock wasn't functional. If you need any logs or feedback let me know.
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
aHecticLife said:
Almost every phone has the physical button music control, poweramp integrated that aww man.
Click to expand...
Click to collapse
I was talking about the module named "physical button music control". Still i'm gonna wait for the update. Really interested in the sequence unlock
mb-14 said:
It won't work on lollipop as of now but I'll release an update as soon as possible.
Click to expand...
Click to collapse
thanks man am waiting u :good:
Update on 1.4.
With bypass option, module now unlocks the screen - Xperia Z stock rom A 4.4.4 bn 292 Odexed.
Yet it only unlocks if the screen is ON - courtesy of PBMC module. I also tried playing with the settings and mappings of PBMC but no success. The issue lies in the Capture Mode - If Screen off + Lockscreen selected, - then Sequence module will not work at all. If Screen Off only, then Sequence U. will work with screen ON + lockscreen. So issue is in PBMC and its button capture mode (even if no custom option is set for volume up/down click)
would be great if you will add features such as, long press for flashlight or camera, sequence for open specific apps...
other than that, great module, keep it coming..
working great on note 2..rom dn4 :good::good:
edit : its only working right after i lock the phone...not working after phone deep sleep..
I like the idea. Will be waiting for Lollipop support.
This is my first ever Xposed module which consists of several CM options / settings that are otherwise missing, but I find useful. This module has been tested on my personal device (Google Nexus 5) running the latest CM nightlies (hammerheadcaf - 4/3/2015).
The options within the module include:
Enable call recorder - Allows option in overflow menu to turn on call recording for the current call
Hide volume boost - Hides/displays the volume boost button
Automatic proximity speaker - Turns on speakerphone automatically when in a call and proximity sensor detects you have taken phone away from your ear
Proximity speaker delay - Sets a delay (ms) before turning on/off automatic speakerphone
Only while in call - Only turns on spearkerphone after recipient has answered the call
Hide superuser icon - Hides/displays the # superuser session active icon in the statusbar
Debug logging - Turns on basic Xposed module logging for this module
Changelog:
4/2/2015 - Initial release
4/3/2015 - Updated CM call recording code to force resource loading and set audio source
4/7/2015 - Redid CM call recording to force it on if enabled, small UI config tweaks and logging
Installation:
Download / Install attached APK
Enable module in Xposed Installer
Turn on settings you want
Reboot
Do I have to have CM for this to work? Or can anyone use it?
terrorist96 said:
Do I have to have CM for this to work? Or can anyone use it?
Click to expand...
Click to collapse
maybe its only for cm
works in lollipop??
Hi
Looks like does not work on CM12.
Call recording isn't showing up here, with the Xposed Module "EnableCMCallRecording" it works fine however. CM12 20150402 nightly.
terrorist96 said:
Do I have to have CM for this to work? Or can anyone use it?
Click to expand...
Click to collapse
No sorry unfortunately it only works for CM12 based ROMS.
jayaraj.chinna said:
works in lollipop??
Click to expand...
Click to collapse
Yes, I have geared the API version of the module so that it will only run with minimum Android API version 21 (Android 5.0)
Publiuss said:
Hi
Looks like does not work on CM12.
Click to expand...
Click to collapse
You have turned on/off the settings you want, and nothing happens? What particular function does not seem to work?
XlAfbk said:
Call recording isn't showing up here, with the Xposed Module "EnableCMCallRecording" it works fine however. CM12 20150402 nightly.
Click to expand...
Click to collapse
My approach to to enable call recording simply was to attach to the recording service "isEnabled" method and override the return to be always true, if enabled in the settings. I will push an update to attempt to override the resource loading on the boolean flag, which is based on country / region values. But it seems like overkill to me. I will also explicitly attach the current voice call as the audio source. Please let me know if this works.
Nice, can do you add „Navbar height“ Settings?
art.montesinos said:
You have turned on/off the settings you want, and nothing happens? What particular function does not seem to work?
Click to expand...
Click to collapse
Well i set call recording, no button appears, I tried speakerphone when phone is far from the ear, it does not activates...
When I was on a CM11 nether "cm call recording" module worked (button appeared but no working registration).
I own a Sgs2 plus and resurrection remix 5.0.2 ROM.
Can you add advanced reboot menu? By the way nice module there!
FantasticalX said:
Can you add advanced reboot menu? By the way nice module there!
Click to expand...
Click to collapse
CM already has an advanced reboot feature. You do not need Xposed for that.
Publiuss said:
Well i set call recording, no button appears, I tried speakerphone when phone is far from the ear, it does not activates...
When I was on a CM11 nether "cm call recording" module worked (button appeared but no working registration).
I own a Sgs2 plus and resurrection remix 5.0.2 ROM.
Click to expand...
Click to collapse
As for the call recording the UI is different in CM12 vs CM11. When enabled in CM12 you have to click the overflow menu (3 dots ...) And you should see a menu item to record the current call.
For the speakerphone issue I am at a bit of a loss. Could you try to get me a logcat of what if any errors are occurring? Is resurrection remix CM12 based?
RevUnix said:
Nice, can do you add „Navbar height“ Settings?
Click to expand...
Click to collapse
I can try this week to add some new features. Modifying the navbar might require hooking into resource methods which gets a bit tricky. I am just learning this as I go. But I will definitely give it a shot. It would be nice if CM12 did have more Navbar options.
Is there any way to enable call recording without using Xposed?
which xposed framework are you using guys? the one I have is not working properly, I have many faulty modules which are supposed to work on lollipop.
dafank said:
which xposed framework are you using guys? the one I have is not working properly, I have many faulty modules which are supposed to work on lollipop.
Click to expand...
Click to collapse
I am using Xposed framework alpha2, version 3.0 for lollipop.
harpin14789 said:
I am using Xposed framework alpha2, version 3.0 for lollipop.
Click to expand...
Click to collapse
I guess you mean this one http://forum.xda-developers.com/showthread.php?t=3034811 which is the one I'm using
have you tried cputemp or cpufreq in status bar modules?
Features
Tune the vibration strength of you phone.
Global vibration: it will affect all vibration.
Special vibration: some system vibration such as virtual key vibration.
Compatibility
Android 4.1+
I test it on my Xperia Z3 Compact using Android 5.1.1 .
Credits
@rovo89 Xposed Framework
@C3C076 SeekBarPreference
Download
See attachment or Xposed store
For those guys whose phone unable to use the module, Send me your xposed log can help me solve the problem better.
(It seems as module isn't activated) or something of that nature. 4.4.4
ztc1997 said:
Features
Tune the vibration strength of you phone.
Global vibration: it will affect all vibration.
Special vibration: some system vibration such as virtual key vibration.
Compatibility
Android 4.1+
I test it on my Xperia Z3 Compact using Android 5.1.1 .
Credits
@rovo89 Xposed Framework
@C3C076 SeekBarPreference
Download
See attachment or Xposed store
Click to expand...
Click to collapse
I searched app like this.
Virtual key vibration works only "on and off".
With 10% vibration is off, and above 10 is on, but with constant strength.
Is it possible to change vibration strange to notification, phone calls, alarm separately? For example low vibration for virtual key, and strong for phone calls.
It will be nice to change level of vibrations for SwiftKey keyboard
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
Maybe you need changes related do vibration in kernel since not everything can be done using Xposed.
ggogolewski said:
I searched app like this.
Virtual key vibration works only "on and off".
With 10% vibration is off, and above 10 is on, but with constant strength.
Is it possible to change vibration strange to notification, phone calls, alarm separately? For example low vibration for virtual key, and strong for phone calls.
It will be nice to change level of vibrations for SwiftKey keyboard
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
Click to expand...
Click to collapse
This module is actually changed the vibration time.In general, vibration time is very short, so the change of time, intensity of feeling is changed the strength.
increase to 300 and add a vibration multipler delay
Hey, so far I am liking the app.
Could you please add a vibration multiplier/delay to your app?
Thanks work great on note 3 n900 cm12.1
Would anyone know if this can be used to achieve the same "feel" as the HTC One M8 on the M9?
On my moto x running stock 5.1, it says that the module isn't set up right, but I have checked it off and rebooted a bunch. This has never happened to me before. Anybody else?
BrownDog99 said:
On my moto x running stock 5.1, it says that the module isn't set up right, but I have checked it off and rebooted a bunch. This has never happened to me before. Anybody else?
Click to expand...
Click to collapse
Check if you installed xposed framework properly and activated this module.
I can not set up a long tap. All I tried.
Global and virtual, interconnected?
Sony ZR 5.0.2
Check if you installed xposed framework properly and activated this module.
I rebooted a few times, nada, not working/
it's this module, all other modules I never had a problem with/
galaxy s3, 4.1.2
The global setting works and everything seems to work except the keyboard intensity. It doesnt change anything on my LG G3 D852. Stock lollipop. If you can get it to increase the keyboard vibration intensity, I dont mind sending you a paypal donation. Its one thing I really hate about the G3; the weak keyboard presses/vibration.
squall458 said:
The global setting works and everything seems to work except the keyboard intensity. It doesnt change anything on my LG G3 D852. Stock lollipop. If you can get it to increase the keyboard vibration intensity, I dont mind sending you a paypal donation. Its one thing I really hate about the G3; the weak keyboard presses/vibration.
Click to expand...
Click to collapse
This module change special vibration via hooking PhoneWindowManager, if your keyboard itself access vibrator instead of using system api, the module will be invalid.
I have many other modules set up and have used xposed since release. I double checked still doesn't work
starcallr said:
Check if you installed xposed framework properly and activated this module.
I rebooted a few times, nada, not working/
it's this module, all other modules I never had a problem with/
galaxy s3, 4.1.2
Click to expand...
Click to collapse
same issue here. reinstalled the framework even and no difference. i would like it to turn off vibrations from persistent apps!
ztc1997 said:
This module change special vibration via hooking PhoneWindowManager, if your keyboard itself access vibrator instead of using system api, the module will be invalid.
Click to expand...
Click to collapse
Im using the LG keyboard. Im not sure if its using vibrator or system api. Thanks though!
I've installed on my z3 (not compact) on 5.1.1 and it seems to change the vibration length but not the intensity. Am I doing something wrong?
Sent from my Xperia Z3
devinalonzo said:
(It seems as module isn't activated) or something of that nature. 4.4.4
Click to expand...
Click to collapse
Have you already run the app?
It doesn't for me too... I can see the same pop up...
with 4.4.4.(CM11)...
Same thing. Says it's not activated. All other xposed modules working. Stock android 4.4.4. Sony xperia z3 compact.
QuickBoot AntiTheft
QuickBoot is a Cyanogen OS feature forOnePlue One but also can work with other devices with Cynogen Roms
The Feature is redusing the boot-up time by altering the shutdown and putting the device in a SleepMode, it also boot up back when its time to Alarm Clock.
Quickboot disables wifi, cellular and killing all the apps beside the clock app for the alarm clock then shuts down the screen.
My Oneplus One device stolen and I counld not find it because some thief shut it down
The idea for the AntiTheft or Lost is to keep the 3G/4G & GPS working with Android Device manager or anti theft apps when in SleepMode.
AntiTheft will help when the thief is shutting down the device but its going to sleep mode and give more time to locate the device by the local authorities
I Decompiled the Quickboot App and made & added the changes in the java code but I can't Recompile it back
if Developers can help it will be awesome
I decompiled the universal apk that can work with other devices with cm12.0/1 thanks to arter97
http://forum.xda-developers.com/android/software/universal-quickboot-cyanogenmod-12-0-12-t3082041
I upload here changed zip
Great concept! Incredibly useful once fully functional!
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Tnx ?
Definitely going to use it once fully functional.
Keep the good work bro.
But did you fix that bug, when you reboot or shutdown the device with Quickboot activated , the icon of Quickboot keep showing when switching between app's?
Both my OP1 and OP2 turned themselves on around the time the alarms were set to go off without me installing this. Is this something that is built into exodus and/or cm12.1 nightlies and enabled by default? Or is this an android thing?
xxBrun0xx said:
Both my OP1 and OP2 turned themselves on around the time the alarms were set to go off without me installing this. Is this something that is built into exodus and/or cm12.1 nightlies and enabled by default? Or is this an android thing?
Click to expand...
Click to collapse
A feature of the stock QuickBoot. Did you not read OP? It's said in the second line.
skymera said:
A feature of the stock QuickBoot. Did you not read OP? It's said in the second line.
Click to expand...
Click to collapse
Is this a different quick boot than the one you can enable/disable in developer settings? I had quick boot disabled in dev settings on both devices, yet they both still turned on when the alarm was supposed to go off, but because the devices were booting, alarm never went off. Both devices did completely power on, radios and all. This does not sound like what the OP described as "quickboot". I figured this might be helpful to the op.
Work AOSP?
Is this dead or still running somewhere somehow?
AlFu30b said:
Is this dead or still running somewhere somehow?
Click to expand...
Click to collapse
Would be good to know
This should be implemented.
Want to know the progress
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.