Related
I saw a review of the lovely Nokia N9, and I noticed that whenever it is put in sleep mode, it does not shut off the screen entirely - instead, it shows a clock that moves around the screen to prevent burn-in. I rather like this idea, and it apparently draws very little juice from the AMOLED screen (which is what my Captivate has).
I spent some time looking for an Android app that accomplishes something like this, but I didn't find anything like it. If there is such an app, could someone point me towards it? If not, is this even possible?
Alright, since this thread doesn't seem to be generating much interest, allow me to bump it with some ideas that might help spark your imagination.
- Replaces sleep mode completely, and might even replace lockscreens
- Displays notification alerts
- Can be toggled on/off by, say, holding down the volume rocker for a few seconds
- Uses the proximity sensor to disable itself when facing down or when placed in one's pocket
- Can be configured to only display under certain conditions (e.g. at night time when plugged in, so as to function as a bedside clock)
- Can cook bacon and eggs
Something like this probably doesn't exist, but would anyone else be interested in something like this if it doesn't use too much battery? If so, I might put up a bounty for whomever brings this to fruition. Would a developer be able to tell me if this is possible? I realize it would probably require root access, but that's fine with me.
Hello.
So I've been tampering with the android SDK and made an app for practice. However, while trying to stick to my basic level goals, it seemed like I was going against the grain of how stuff seemed to work. I'm gonna read up on theory now, but it'd be a real help if you could tell me if there were any glaring dumb/broken/bad things there.
Anyway, the general idea was to have a reverse-stopwatch that I could populate with types of laps with custom durations. So I'd have, for example, WALK 10sec, RUN 30sec JOG 15sec *10 times. I wanted the app to vibrate every time one of these laps ended (no matter what, even in screen lock) but I also wanted those laps and their duration-countdowns to be dynamically shown in a ListView inside the main Activity.
In order to do that, I populated an Object that extended Application with my dataset, plugged it into an Adapter to update the ListView with, then when I had a populated list, I'd invoke an IntentService which would make a deep copy of the data and do countdowns inside logic loops. That IntentService also periodically sent messages to a BroadcastReceiver, who would update durations and remove expired laps on the Original List (linked to the Adapter) and handle vibrations. The intentService could be aborted prematurely , I haven't been able to think of a way to pause it.
Well, it works if you don't ever let it re-orient screens and while phonecalls don't break it, some of the listview data appearance was corrupt after one (the timers were fine tho which is weird).
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Big Cam said:
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Click to expand...
Click to collapse
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
hutzdani said:
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
Click to expand...
Click to collapse
I already use this while my phone is on the desk. Way quicker to double tap screen and input key then grab phone and pick it up
hutzdani said:
Its also pretty useless for alot of scenarios with the finger print scanner - its fine when connected to a trusted BT device and then swipe to unlock or if you want to check the time with a double tap.
Its pointless otherwise, however a nice feature for the sake of a feature - the power button achieves the same thing or just finger print to unlock right out the pocket.
The only case I have found a use for the D2W is when in my car connected via BT streaming music and want to quick unlock in traffic to change a track without having to reach around my phone holder on the windscreen to unlock via the scanner.
I'd hazzard a guess its why google never enabled it out the box but left the function in.
Click to expand...
Click to collapse
I mean, come on man. the conceptual point of Android was the ability to have your choice of options than what a single company deems necessary. It becomes second nature once you have devices that have it like the m8 or Nexus 9. Also some cases or bumpers tend to mush the power button travel, making even that way more difficult.
Even that aside, sometimes you just want to check and manage notifications or whatever, fingerprint immediately unlocks the device.
Jbluna said:
I mean, come on man. the conceptual point of Android was the ability to have your choice of options than what a single company deems necessary. It becomes second nature once you have devices that have it like the m8 or Nexus 9. Also some cases or bumpers tend to mush the power button travel, making even that way more difficult.
Even that aside, sometimes you just want to check and manage notifications or whatever, fingerprint immediately unlocks the device.
Click to expand...
Click to collapse
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Do we need root for this to work?
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
I dont want to pick up my phone and movie it around to get to the fingerprint scanner. Even getting to the power button can cause me to focus to much attention. A double tap is quite easy todo to check what notifications you have.
You have never used double tap is my guess and I recommend it even if it seems kinda useless.
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
DT2W is an AWESOME feature - even if it was disabled by Google after careful thought. Yes, the fingerprint scanner is quick and very convenient. However, because it bypasses the lock screen it also bypasses lock screen notifications. Sometimes I just want to read a quick text/push notification without picking up my phone or locating the power button. A quick double tap on the screen is a lot better than picking up the phone, using my fingerprint to unlock, and then swiping down the notification shade to read my updates.
deeproot said:
I dont want to pick up my phone and movie it around to get to the fingerprint scanner. Even getting to the power button can cause me to focus to much attention. A double tap is quite easy todo to check what notifications you have.
You have never used double tap is my guess and I recommend it even if it seems kinda useless.
Click to expand...
Click to collapse
Used DT2W with N5 / 6 / 7 / G3 and G4 because it was useful as I never used pin entry or any other type of passworded lock, just swipe to unlock.
Now we have a finger print scanner the whole idea of D2TW is depricated alongside active display ( to a certain degree & AW )
D2TW works fine as a quick check for the time but coupled with finger prints its a dead end function beyond checking the time or expanding a notification, notifications are mostly acted on in day to day use.
Now go through the motions - You DT2W see a notification you want to attend to and your faced with one of two things 1. Finger print to get in or 2. Pin or pattern unlock.
In these two cases its slower than just doing FP or Unlock codes - Now factor in the accuracy of DT2W ( yes it can be adjusted ) but some cases it will just ignore it and require a more firm press on the screen.
Now we have two hurdles to factor in - now Imagen your at Google and your selling a device with a quick and efficient and secure way of getting into your device fast to compete with the growing trend of other OEMs.
Do you plump for a slow unaccurate system that does not even get you into the device and still requires PIN entry to do stuff or do you go the FP route.
looking at it this way makes it all very clear from Googles perspective as to why its not enabled by defult.
I like DT2W don't get me wrong but its just irrelevant for those who will use the FP in conjunction with the LED or active display or AW.
The fact that it only serves a good useful purpose when connected to a trusted device for quicker access, alone shows how its a Gimmick feature these days due to tech moving on.
Alot of people will still naturally use the power switch to check the screen for notifications as its been creature habit for many since androids inception, LG introduced it and it gained traction before the whole active display thing moto dropped on the scene.
Now with active display ( Frankly a stupid gimmick if you ask me - give me a blinky LED anyday ) and android wear ( if you can believe that is even worth the effort or cash trust me its not ! ) its even less relevant to DT2W to read the screen.
Point is its not there by defualt for a reason - a design reason - a technical reason - a marketing reason : yes android is open source and google knows nexus people like to tweek their devices so they will have left some gems for people to play with.
As a device they are selling DT2W is not a likely candidate to hit the specs sheet or the TV adverts or Ads is it now when its up against bigger better selling features : FP / Permium build quality / USB C / Slow mo video capture e.c.t
I like to look at things from both points of view but DT2W has little going for it these days with all the additional functionality
hutzdani said:
Used DT2W with N5 / 6 / 7 / G3 and G4 because it was useful as I never used pin entry or any other type of passworded lock, just swipe to unlock.
Now we have a finger print scanner the whole idea of D2TW is depricated alongside active display ( to a certain degree & AW )
D2TW works fine as a quick check for the time but coupled with finger prints its a dead end function beyond checking the time or expanding a notification, notifications are mostly acted on in day to day use.
Now go through the motions - You DT2W see a notification you want to attend to and your faced with one of two things 1. Finger print to get in or 2. Pin or pattern unlock.
In these two cases its slower than just doing FP or Unlock codes - Now factor in the accuracy of DT2W ( yes it can be adjusted ) but some cases it will just ignore it and require a more firm press on the screen.
Now we have two hurdles to factor in - now Imagen your at Google and your selling a device with a quick and efficient and secure way of getting into your device fast to compete with the growing trend of other OEMs.
Do you plump for a slow unaccurate system that does not even get you into the device and still requires PIN entry to do stuff or do you go the FP route.
looking at it this way makes it all very clear from Googles perspective as to why its not enabled by defult.
I like DT2W don't get me wrong but its just irrelevant for those who will use the FP in conjunction with the LED or active display or AW.
The fact that it only serves a good useful purpose when connected to a trusted device for quicker access, alone shows how its a Gimmick feature these days due to tech moving on.
Alot of people will still naturally use the power switch to check the screen for notifications as its been creature habit for many since androids inception, LG introduced it and it gained traction before the whole active display thing moto dropped on the scene.
Now with active display ( Frankly a stupid gimmick if you ask me - give me a blinky LED anyday ) and android wear ( if you can believe that is even worth the effort or cash trust me its not ! ) its even less relevant to DT2W to read the screen.
Point is its not there by defualt for a reason - a design reason - a technical reason - a marketing reason : yes android is open source and google knows nexus people like to tweek their devices so they will have left some gems for people to play with.
As a device they are selling DT2W is not a likely candidate to hit the specs sheet or the TV adverts or Ads is it now when its up against bigger better selling features : FP / Permium build quality / USB C / Slow mo video capture e.c.t
I like to look at things from both points of view but DT2W has little going for it these days with all the additional functionality
Click to expand...
Click to collapse
Agree to disagree. Double tapping for a quick check of the time or a notification is a handy feature. Not every notification requires you to act on it. A lot of times (Gmail Spam) I will DT2W and then swipe to dismiss the notification. That does not require using a pin and or fingerprint.
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
Your argument is pointless, just because google turned it off doesn't mean it doesn't serve a purpose. Example, google heavily pushed ambient display over LED notifications and we all know LED notifications work ten times better....
Yep, my phone sits most of the day next to me in a trusted space and it is mucho nice to be able to double tap in and check messsages, time, etc. without having to specifically hit the power button to light the phone up. Further I have owned a phone where the power button eventually died and DT2W removes the majority of cycles on the power button. It can be done when the phone is on either side. It can be done while the phone is in a dock and more without taking your eyes off the road if docked in the car. Just because someone in particular doesn't use it doesn't mean it isn't a useful feature.
I think the reason DT2W was disabled is because someone on the android team secretly is taking money on the sly from Apple in exchange for removing useful and nice features from android. Anyone who says anything else clearly needs more tequila in their life.
i couldn't get this to work. anyone else successful?
I'd like to have this enabled on mine when it gets here Monday. Why not? When it's on table I can just tap to check it. More is more
Sent from my XT1096 using Tapatalk
double tap to LOCK?
Is it possible to modify your code so double (or maybe triple?) trap would lock the device? Thanks!
Big Cam said:
This is not my code and I apologize if this doesn't belong here, I think it does.
Simply enter this into a terminal emulator, it does not survive a reboot, so I'm posting this in hopes ROM makers will add it in.
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
Source is here
Click to expand...
Click to collapse
.
There is no need for this anymore, by installing a custom Kernel you can get this highly needed feature.
im currently running ElementalX Kernel which enables DT2W.
http://elementalx.org/devices/nexus-6p/
Working like a champ. I hope Francisco Franko kernel gets realeased soon.
Yeah, this is redundant now.
Sent from my Nexus 6P using Tapatalk
Excellent, that's what I was hoping would happen!
hutzdani said:
Yeah I know, However its been disabled for a reason clearly after some thought.
its not like the nexus 5/6/7 or 9 who did not have Fingerprint scanners this is a case of features for the sake of features.
Yeah its cool the devs enabled this from digging through the code but really its depreciated by the finger print scanner in this case.
That's all i'm saying
Click to expand...
Click to collapse
It is made difficult by the finger print scanner being on the back of the device. If it was on the front the functionality would be unnecessary. I like the scanner on the back for in the hand use but it is a limiting factor during use on a table/flat surface.
byproxy said:
i couldn't get this to work. anyone else successful?
Click to expand...
Click to collapse
1) You must be rooted
2) type
Code:
SU
into terminal
3) type the code
Code:
echo 1 > /sys/devices/soc.0/f9924000.i2c/i2c-2/2-0070/input/input0/wake_gesture
The app is setedit and you'll need to hand over almost $3 Canadian if you want these tweaks. 1 of them will work for sure without needing to enforce but I think it's a sweet deal and 3 of these are working on Pie. 2 of them, or even 1 is worth the price.
You'll need to go into a shell and enter exactly:
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Copy and paste it. If you don't know how to do that just look up ADB, android developer options, and Samsung USB drivers.
First the freebie. Go into Secure Table and click +add new setting (your first entry may ask you to grant a permission. DO IT)! enter: clock_seconds value: 1 BOOM! Hope you like it because it'll NEVER go away! Just kidding. If you factory reset... or simply enter a value of 0 you'll be rid of the ticker.
Next up I think is a freebie, too. Still in Secure Table, scroll down to sysui_qs_tiles delete everything. NO DON'T! Carefully, without erasing the entire list, add in MobileData exactly like that. So actually it'll be a comma first. Have a look around for other tiles because 'ol Sammy likes to keep things real tight with the carriers. You can also remove some but I think it's best to not potentially freezing your phone up.
Now, pretty sure these ones will need the guardian to stick so if you can manage 3 bucks it'll be worth it, especially the last 2!
Change tile rows and columns.
Right above the tile edit in Secure Table is sysui_qqs_count I like a value of 7. Don't go too small or too high. Or do it and see what happens. Please don't. I can only vouch for 7 and 8. I have heard of 3 but never tried it. This changes the first row, first pull on notification menu.
Now to change the rows, the long pull I guess you can call it, qs_tile_row in Secure Table still. I do 4. I heard if you enter in 50 you get a widescreen TV. No idea. I only tried 4.
Screen Timeout not long enough?
While some of you may not need it, I need more than 10 minutes. Head to System Table and... not sure why, but I think this needs both screen_off_timeout_rollback AND screen_off_timeout to work. I set mine to 1800000 (yes 5 zeroes) to get 30 minutes. Do it on both. Double that, 3600000 will give you an hour. So if you want 13 minutes and 27 seconds, figure it out. I think entering a value of 1 will get you a free trip to the ODIN app. Don't know what that is? You'll find out pretty quick if you screw this one up. Of course you're gonna head to the menu and look to see a new entry of 18 minutes and 55 seconds. Not happening. What you will see is that no selection is made. DON'T TOUCH IT! Just leave it alone. It's working. This one works in Pie. Only one setting is needed. Can't remember but you'll find it.
These 2 are the bestest and they work in Pie.
Goodbye HIGH BRIGHTNESS and HEADPHONE VOLUME warning!
In Global System set audio_safe_volume_state to a value of 2. "But mine's already at 2." So then you've been warned. Now add it to the guardian.
In System Table, you'll want to alter a value of 1 in the shown_max_brightness_dialog "But I don't have that entry." So close the app, crank up the brightness and be told how evil it is. Wasn't that fun? Now fix up the entry. Add it to the guardian with the 1 value and if set to 0 don't forget to change to 1
*NOTE* most of these values take about 15-45 seconds to kick in after every reboot. So, before you reboot and say it doesn't work, well, you're kinda right. But you'll soon forget about it and one day be able to reboot without seeing if it works or not. Finally, one day, you'll go to turn up the brightness, or volume, and that warning will not appear. And THAT'S when the real joy is felt. As you're cranking up that slider, in all of .02876 seconds, you're going to think, "Stupid warning" "OMG I am not gonna get a warning" "Hey cool I didn't get the warning. Anyone see that?"
Bonus Feature! When bored I random;y change values of random entries. See how fast you can screw yours up! Don't play with anything unless it's your friend's phone. We're not friends.
I can't vouch this works on any other device except A8. It's a representation of what's on your phone. Adding a custom ROM will change the output and results. Use your noggin, yo
Finally, I turned off battery optimization for the app and feature pack, and turned off notifications. It works fine. No usage pops up because it's very small and no problems with enforcing the edits. No annoying notification required.
mindlery,
I'm doing an article about Drone flight and high NITS display devices. A tablet or phablet that can display the sun equivalent brightness is very expensive so most pilots use cell phones. Of these cell phones samsung and lg both have models that will BOOST brightness (manually at least on the lg G7) but it will only boost for up to 3 minutes. one might think its' a heat issue but the timer is probably a battery saver because when flying I keep resetting my boosted brightness on the Lg-G7 and the phone never gets warm.
So you appear t6o have knowledge on this and there may be an opportunity to help a bunch of pilots if a boost timeout can be changed (easily via app or some easy method) to fix the boosted time to about 30 minutes or make it a manual switch.
If you are at all interested, I'm going to do an article and video for other pilots on this if I can get a solution down.
Bill
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.