Related
Wondering if someone can help, on my Xperia s when I am in my home screen or any other app and I press and hold the camera button it will launch the camera app.
But on my girlfriends Xperia s this doesn't work. (launching camera in lock screen still works)
Does anyone know where the settings for this is?
Thanks
electric0ant said:
Wondering if someone can help, on my Xperia s when I am in my home screen or any other app and I press and hold the camera button it will launch the camera app.
But on my girlfriends Xperia s this doesn't work. (launching camera in lock screen still works)
Does anyone know where the settings for this is?
Thanks
Click to expand...
Click to collapse
Try launching the camera app, then click on Settings -> Quick launch
Rashkae said:
Try launching the camera app, then click on Settings -> Quick launch
Click to expand...
Click to collapse
Tried that, but that seems to be the settings for launching from the lock screen.
Maybe due her launcher? It isn't a different configuration on the launcher?
Sent from Xperia X10 Mini Pro using ICS by paul-xxx
Felimenta97 said:
Maybe due her launcher? It isn't a different configuration on the launcher?
Sent from Xperia X10 Mini Pro using ICS by paul-xxx
Click to expand...
Click to collapse
I am using Launcher pro with no specific customization but it works on home screen.
electric0ant said:
Wondering if someone can help, on my Xperia s when I am in my home screen or any other app and I press and hold the camera button it will launch the camera app.
But on my girlfriends Xperia s this doesn't work. (launching camera in lock screen still works)
Does anyone know where the settings for this is?
Thanks
Click to expand...
Click to collapse
I may not know the answer, but it's worth trying to re-flash the unit without wiping your user data.
The same thing for me! Quick shot works good.... but many times when i press the camera button with unlocked phone or in menu....the apllication doesn't start.....i must re-press 3/4 times.
herasymcuk said:
The same thing for me! Quick shot works good.... but many times when i press the camera button with unlocked phone or in menu....the apllication doesn't start.....i must re-press 3/4 times.
Click to expand...
Click to collapse
This seems to be the issue I am having, pressing a few times eventually loads the camera. Have tried reflashing, and makes no difference.
One thing I have found was that in the service menu and software info it says no file found for memory card. And touch firmware version as 6, while my working Xperia s says 7
On my Xperia S i have file for memory card (in the service menu) and touch firmware version 7 also.... but the problem with camera app happens very often!
herasymcuk said:
On my Xperia S i have file for memory card (in the service menu) and touch firmware version 7 also.... but the problem with camera app happens very often!
Click to expand...
Click to collapse
This looks like a software issue as the camera button works perfectly fine and quick launch for the camera works everytime when in the lock screen.
I have reflashed with different versions of firmware so I guess the memory card and the touch firmware versions are physically different hardware I suppose.
But this is just really bugging me at the moment!
Do you guys hold the button for like one second? Cause the camera starts only when i'm holding it a little.
Just touching the button has no effect in locked mode or on home screen for me.
1. How do I turn off floating touch completely? It makes gaming impossible, and has no real benefits other than previewing xvideos.com clips. I of course tried disabling glove mode, no success. I tried installing an app that was supposed to turn it off, it even requested root, but did nothing after reboot.
2. How do I disable the the illumination bar and the backlight of the capacitive buttons permanently? The led illuminates one side more than the other and it doesn't look good. A couple of apps allowed me to do this, but then they just stopped running in the background and the lights were back. I need a permanent solution here.
3. I love the option that I can limit my background processes, but I always end up with my xperia home closed, and the whole home screen gets reloaded. Can I add it as a specific exception? So a max of 4 processes, but never close xperia home.
4. The screen is flickering when I set the backlight to the lowest setting. I have my auto brightness off. What could be the problem?
5. After the ICS update, the notification bar has two battery indicators, one is a percentage, the other one is an icon. How do I get rid of one without installing a loader?
+1. How can I make my Sola more responsive? I froze bloatware, I restart the phone pretty much every day, but it seems to lag and freeze all the time.
Thanks!
Use a custom rom like CM and most of your problems will be solved!!!
But its meant for unlocked Bootloaders only ..
Sent from my Xperia Sola using xda premium
Yes, you need to flash CM as it doesn't have floating touch, and users say it's the fastest.
But I can tell you about flickering, it's normal no problem with that.
As to battery percentage, you must flash a modded notifications bar, you can find many in Apps section.
As to reloaded home, make sure u have latest .54 firmware, try using task killer, or simply another home launcher, and set background processes to 3 max.
Sent from my MT27i using xda app-developers app
** This module is no longer needed for Android 5.0 or higher **
This Xposed module restore LED functionality of Xperia devices when Stamina mode is enabled. Normally, when enabled, Stamina mode either disable the device LED or force it to show only white color.
Requirements
1. Your phone must be rooted
2. Xposed framework must be installed first http://forum.xda-developers.com/showthread.php?t=1574401
3. Xposed library 2.2 is required
Instructions
Install the module
Run Xposed Installer and enable the module Xperia Stamina LED
Reboot the phone
Source code
You can find source code for this module from GitHub here.
Download
Xposed Module Repository | Play Store
Well how about that, I finally got my Stamina working and I notice this white-only LED and went on adventure on how to fix this and here you were. Thanks man, gonna try right away and report back.
I don't really know what the purpose of this module is.
The LED remains active in Stamina mode since I believe the 4.2. update for the Xperia Z in mid 2013 or even earlier in one of the newer 4.1. official firmwares...
The same goes for the Z1 and Z1 compact so there is really no need for it.
People don't even need root as it is active with stock Sony firmware.
drsoran2 said:
I don't really know what the purpose of this module is.
The LED remains active in Stamina mode since I believe the 4.2. update for the Xperia Z in mid 2013 or even earlier in one of the newer 4.1. official firmwares...
The same goes for the Z1 and Z1 compact so there is really no need for it.
People don't even need root as it is active with stock Sony firmware.
Click to expand...
Click to collapse
Umm... I had some trouble with Stamina so I used the SuperStamina.apk from Existenz' rom v5. Then it worked but LED with white when stamina was active... and that is based on 10.4.B.0.569 which is afaik 4.3... So, I dont know.. I thought it was supposed to be fixed as well, but apparently not? This module helped...
Still, stamina is some wonky ****, it's like its random whether or not it works.
drsoran2 said:
I don't really know what the purpose of this module is.
The LED remains active in Stamina mode since I believe the 4.2. update for the Xperia Z in mid 2013 or even earlier in one of the newer 4.1. official firmwares...
The same goes for the Z1 and Z1 compact so there is really no need for it.
People don't even need root as it is active with stock Sony firmware.
Click to expand...
Click to collapse
Then you're very fortunate that the LED continue to work properly when stamina mode is enabled. For many other Xperia devices (I'm using ZR and many other 2012 models), Sony decided to disable LED or make it to display white color only when stamina mode is enabled. Previously people had to mod the SuperStamina.apk to restore LED, now I hope they find it easier with this Xposed module.
itandy said:
Then you're very fortunate that the LED continue to work properly when stamina mode is enabled. For many other Xperia devices (I'm using ZR and many other 2012 models), Sony decided to disable LED or make it to display white color only when stamina mode is enabled. Previously people had to mod the SuperStamina.apk to restore LED, now I hope they find it easier with this Xposed module.
Click to expand...
Click to collapse
I bet the fortunate ones simply just have a malfunctioning stamina I mean ive been rolling with stamins "enabled" for quite a while now with fine notification LEDs but I found out it wasnt working at all lol
Working like a charm in my xsp
Great work
Works great on Z1 Compact with firmware 14.3.A.0.757 (Android 4.4.2).
The LED was the only reason I disabled the Stamina mode. Thank you very much! :good:
Kocayine said:
I bet the fortunate ones simply just have a malfunctioning stamina I mean ive been rolling with stamins "enabled" for quite a while now with fine notification LEDs but I found out it wasnt working at all lol
Click to expand...
Click to collapse
May I ask how you figured out stamina mode was not working (properly or at all)? Reading all this, I began to wonder as my LED notification seems to work while stamina mode is switched on (now, I don't know if it is really working or just pretending to do so).
Wurstwarenfachverkäuferin said:
May I ask how you figured out stamina mode was not working (properly or at all)? Reading all this, I began to wonder as my LED notification seems to work while stamina mode is switched on (now, I don't know if it is really working or just pretending to do so).
Click to expand...
Click to collapse
What device are you using?
itandy said:
What device are you using?
Click to expand...
Click to collapse
Sorry, I forgot to mention - it's a z1 compact with stock 4.3 rom (rooted, though).
Wurstwarenfachverkäuferin said:
May I ask how you figured out stamina mode was not working (properly or at all)? Reading all this, I began to wonder as my LED notification seems to work while stamina mode is switched on (now, I don't know if it is really working or just pretending to do so).
Click to expand...
Click to collapse
I just used instant messaging apps to test. Make sure they're not on the exception list. Turn phone screen off without being in the charger. Then make someone write you. If stamina works the message will only get delivered once screen is turned on.
Wurstwarenfachverkäuferin said:
Sorry, I forgot to mention - it's a z1 compact with stock 4.3 rom (rooted, though).
Click to expand...
Click to collapse
I use a similar method as Kocayine to verify if stamina mode is working or not. The only thing different is I use Whatsapp instead of SMS because Whatsapp allows you to define the LED color while SMS always use white LED for me.
Anyway, you can post your Xposed log here for me to check.
Kocayine said:
I bet the fortunate ones simply just have a malfunctioning stamina I mean ive been rolling with stamins "enabled" for quite a while now with fine notification LEDs but I found out it wasnt working at all lol
Click to expand...
Click to collapse
Kocayine said:
I just used instant messaging apps to test. Make sure they're not on the exception list. Turn phone screen off without being in the charger. Then make someone write you. If stamina works the message will only get delivered once screen is turned on.
Click to expand...
Click to collapse
itandy said:
I use a similar method as Kocayine to verify if stamina mode is working or not. The only thing different is I use Whatsapp instead of SMS because Whatsapp allows you to define the LED color while SMS always use white LED for me.
Anyway, you can post your Xposed log here for me to check.
Click to expand...
Click to collapse
I may have misunderstood Kocayine's post about malfunctioning stamina mode as I thought it didn't relate to the Xposed framework or the specific module discussed here but describe a general issue with some xperia devices. The Xposed framework isn't installed on my phone yet.
However, with stamina mode (supposedly) turned on and screen off, the SMS app will indicate an incoming message with a purple/blueish LED notification. Turning on the screen, I will immediately see the message in the minimised notification area. Now, depending on the way I access the SMS app, the message will appear instantly or with some delay. If I - somehow - get to the conversations overview screen, the new message (or more exactly a preview of it) is shown immediately; if the respective conversation already has been on the screen (or I move there through the app switching thingy), the new message may take half a second to appear. It is very similar with Skype except that, in Skype, LED notifications sometimes do appear when the screen is off and sometimes not.
Wurstwarenfachverkäuferin said:
I may have misunderstood Kocayine's post about malfunctioning stamina mode as I thought it didn't relate to the Xposed framework or the specific module discussed here but describe a general issue with some xperia devices. The Xposed framework isn't installed on my phone yet.
However, with stamina mode (supposedly) turned on and screen off, the SMS app will indicate an incoming message with a purple/blueish LED notification. Turning on the screen, I will immediately see the message in the minimised notification area. Now, depending on the way I access the SMS app, the message will appear instantly or with some delay. If I - somehow - get to the conversations overview screen, the new message (or more exactly a preview of it) is shown immediately; if the respective conversation already has been on the screen (or I move there through the app switching thingy), the new message may take half a second to appear. It is very similar with Skype except that, in Skype, LED notifications sometimes do appear when the screen is off and sometimes not.
Click to expand...
Click to collapse
It doesn't relate to xposed framework. It's a general thing afaik. Btw, don't use SMS, stamina always allows SMS and calls. Instant messaging isn't SMS but something like WhatsApp, FB messenger or indeed Skype. The notification should be delayed until screen is on. Including vibration, vibrating and sound.
In Skype, with the screen off, it goes like that:
Skype running in the background
An incoming message will trigger a sound and a purple notification. When turning the screen on, the notification changes from purple to deep blue and seems to stay that way until I open Skype.
Skype running in the foreground
An incoming message is not indicated in any way. After turning on the screen, the rest is the same as above ...
Now, Skype, being all buggy (on Android even more than on Win) may not be the best test here, I guess.
Thank you! It works perfect and it solves one of my biggest annoyances of my XZ!
Any idea how this affects battery?
antonio1475 said:
Thank you! It works perfect and it solves one of my biggest annoyances of my XZ!
Any idea how this affects battery?
Click to expand...
Click to collapse
As far as I can see there's no noticeable impact on battery.
Not working on stock 4.4.2 :-/
Wysłane z mojego C6603 przy użyciu Tapatalka
Lukiqq said:
Not working on stock 4.4.2 :-/
Wysłane z mojego C6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
That's weird. It works perfectly here (Xperia Z, "stock" 4.4.2 by Rajeev).
I have a question for people who are using lollipop right now. I saw that there is a ultra stamina mod in that version for z ultra. It is a nice addition but it's kind of useless as well as low power saving mode present in kitkat. I wonder if Sony have added a cpu option In low power saving mode, which is there on Z3 for example? That would make this mode actually useful.
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.