responsive dialer - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

does anyone know of a responsive dialer? I am looking for an original looking(bigger buttons would be nice) dialer that doesnt have a delay between pressing and recognition/drawing/tone. The lag time on all the dialers i have used seems excessive. I wonder why, as response to screen presses are quite snappy otherwise.

sorry I am no help here..............I would like to see a dialer that is more responsive too. I imagine it has something to do with how fast the processor can process the little app's requests...........not too fast it appears.

i dont know about wm6, but i'm using wm5 and turning off smartdialing helps A LOT, well not much help if you do use smartdialing...

mthomas said:
does anyone know of a responsive dialer? I am looking for an original looking(bigger buttons would be nice) dialer that doesnt have a delay between pressing and recognition/drawing/tone. The lag time on all the dialers i have used seems excessive. I wonder why, as response to screen presses are quite snappy otherwise.
Click to expand...
Click to collapse
I gained some speed by deactivating the sound of the keys when you press them

I did global search on the forum and found this one, so I'll just add comment on this one rather than creating a new thread
pfmboidi said:
I gained some speed by deactivating the sound of the keys when you press them
Click to expand...
Click to collapse
i only got a tiny bit improvement, my cheap nokia 3210 that came with T-mobile pre-paid card was MUCH MUCH MORE responsive!!!
I'm totally frustrated, it took up to 3 seconds to dial 1 number, consider the following:
- in order to improve the performance I need to turn the key sound off, so I have to keep looking at my screen
- pressing a button can fail altogether or can work with delay
- if i don't see the number you pressed immediately on the screen I have 2 options:
-- press again, but this can work OR create DOUBLE PRESSES
-- wait and see if it's just a delay, sometimes i wait only to see that I NEED TO PRESS AGAIN
this is OK when i don't badly need the phone "feature" and all the other bells and whistles distract me from thinking I'm supposed to have a dependable phone in this stupid device.
let me know if there's any smarter way around this and how do you guys deal with this? is iphone much more responsive when it comes to phone?

I think the real problem is that MS really doesn't care. If iphone (my wife has one) could do decent secure exchange I would dump this turkey of a phone and go that route. It is excellent as aphone except for the lack of voice commander and most of the pda functions are great as well. I n fact ifyou eliminate the ability to add a bunch of beta aps that are trying to imitate the user interface of a competing product, and screw up you r phone after a couple of days, what is the advantage of a wm platform?

Related

Interactive Touch (Like the Voyager)

I did a search on PPCGeeks, XDA, and Google, and couldn't find any app to make the touch screen on the Titan interactive - similar to the way the Voyager touch screen works (quick vibrate when the screen is touched).
Is there any app like this? If not, can someone make one?
Thanks!
You would think HTC being one (if not THEE one) #1 Smartphone manufacture that would have SOMETHING similiar to the iphone or Voyager. The HTC Cube to me is very "amatuer" looking compared to the iphone and Voyager UI. Even microsoft couldn't make anything similiar...hopefully WM7 will blow us away.
I agree that the Cube looks pretty basic (that's why I won't put it on my phone, but I do have the TouchFLO).
But what I'm looking for is for the phone to do a very quick vibrate whenever the screen is touched.
That technology is called Haptics and it is much more than just the phone vibrating. Haptics allows you to physically feel a vibration exactly on the spot of the screen you are touching. Your phone has to have Haptics vibration built into it to use it and there isn't a single HTC phone out there using the said technology.
http://www.immersion.com/corporate/press_room/what_is_haptics.php
worth a shot
vaxick said:
That technology is called Haptics and it is much more than just the phone vibrating. Haptics allows you to physically feel a vibration exactly on the spot of the screen you are touching. Your phone has to have Haptics vibration built into it to use it and there isn't a single HTC phone out there using the said technology.
http://www.immersion.com/corporate/press_room/what_is_haptics.php
Click to expand...
Click to collapse
Indeed.
That said, I'm still interested in any app that does simply what whiteblazer01 asked for. I'm always looking over my fingers when I'm trying to dial a phone number. I'd be willing to give a simple touch-response app a shot.
Anyone?
ryanshepherd said:
Indeed.
That said, I'm still interested in any app that does simply what whiteblazer01 asked for. I'm always looking over my fingers when I'm trying to dial a phone number. I'd be willing to give a simple touch-response app a shot.
Anyone?
Click to expand...
Click to collapse
I have been looking into this also. Especialy when i use the media player or just the main screen shortcuts.
In the mean time I was able to find a CAB somewhere in this forum that enables vibration feedback when you dial a number. It replaces the tone with vibration. I hope you guys like it. (Sorry I dont have support for it because I am not the original creator of this CAB)
Make sure that once you install the CAB that you soft reset after.
Hope you like it.
That's exactly what it is - Haptics. Thanks for the link. The program [email protected]$ put a link to (thanks!) works on the keypad, but it really doesn't feel like the Haptics system. O well, its still cool though.
I found a link to another thread on this forum for the same thing. http://forum.xda-developers.com/showthread.php?p=1685449
whiteblazer01 said:
That's exactly what it is - Haptics. Thanks for the link. The program [email protected]$ put a link to (thanks!) works on the keypad, but it really doesn't feel like the Haptics system. O well, its still cool though.
I found a link to another thread on this forum for the same thing. http://forum.xda-developers.com/showthread.php?p=1685449
Click to expand...
Click to collapse
I was thinkin about how we can make the phone vibrate when we tap the screen in any application instead of only the dial pad.
I came up with a theory that might give us some type of haptics feed back. It might not be exactly like haptics but it could make the phone vibrate.
There is a feature in our phone that can enable the phone to play a sound when we tap the screen for any reason. I was thinking why not replace the sound with just vibration like the CAB that changes the sound to vibration on the dialer?
Im not experienced at programming, but I am willing to take a shot into making this possible. Maybe some one can get a hold of a good programmer or some one good at registry tweaks to make this possible.
Just an idea
steps said:
You would think HTC being one (if not THEE one) #1 Smartphone manufacture that would have SOMETHING similiar to the iphone or Voyager. The HTC Cube to me is very "amatuer" looking compared to the iphone and Voyager UI. Even microsoft couldn't make anything similiar...hopefully WM7 will blow us away.
Click to expand...
Click to collapse
Voyager is hella gay
[email protected]$ said:
I have been looking into this also. Especialy when i use the media player or just the main screen shortcuts.
In the mean time I was able to find a CAB somewhere in this forum that enables vibration feedback when you dial a number. It replaces the tone with vibration. I hope you guys like it. (Sorry I dont have support for it because I am not the original creator of this CAB)
Make sure that once you install the CAB that you soft reset after.
Hope you like it.
Click to expand...
Click to collapse
Great Idea [email protected]$, deffinately move forward with it, Ive been using the phonepadvibrate (essentially the same as what you posted) for well over 2 months now and love it. If you could do the same with the normal touch screen it would be amazing.
Yes its not full haptics, but in my opinion it really doesnt need to be. some sort of physical feedback (ie a slight vibration) would be great when working with the touch screen.
[email protected]$ said:
I was thinkin about how we can make the phone vibrate when we tap the screen in any application instead of only the dial pad.
I came up with a theory that might give us some type of haptics feed back. It might not be exactly like haptics but it could make the phone vibrate.
There is a feature in our phone that can enable the phone to play a sound when we tap the screen for any reason. I was thinking why not replace the sound with just vibration like the CAB that changes the sound to vibration on the dialer?
Im not experienced at programming, but I am willing to take a shot into making this possible. Maybe some one can get a hold of a good programmer or some one good at registry tweaks to make this possible.
Just an idea
Click to expand...
Click to collapse
Carlos, I definitely agree, I would love to have that whenever the screen vibrated. Although, I don't know who would be willing to do that. I remember when I had the Apache (XV6700), I thought it would be cool if someone could make the LED lights on top into indicator lights for the shift and caps keys - which never happened (I don't know how, otherwise I would do it myself).
In fact, I wonder if someone can make a cab to have the shift and caps buttons make the indicator lights turn on whenever the buttons are pushed, not just when shift lock or caps lock are enabled.
Paul
whiteblazer01 said:
Carlos, I definitely agree, I would love to have that whenever the screen vibrated. Although, I don't know who would be willing to do that. I remember when I had the Apache (XV6700), I thought it would be cool if someone could make the LED lights on top into indicator lights for the shift and caps keys - which never happened (I don't know how, otherwise I would do it myself).
In fact, I wonder if someone can make a cab to have the shift and caps buttons make the indicator lights turn on whenever the buttons are pushed, not just when shift lock or caps lock are enabled.
Paul
Click to expand...
Click to collapse
It is very possible. I found other sources and they have some sort of program / prototype that can make this happen but it doesnt work on every tap of the screen.
What I want to do is make mine work on every tap of the screen but have the ability to turn it off and on to save power. Like turning the notification for the sound to play when you tap the screen on and off.
So far I have planned some steps to do it through the registry but since I am not an expert at programming like others are here it might take a while.
But any help is very welcome to complete this project and make it available for all.
As to changing the LED's on your phone. I think no2chem and some other guys found a way to customize your LED settings, but I'm not sure if it will be custom enough to indicate caps or shift. Maybe in the near future.
whiteblazer01 said:
I did a search on PPCGeeks, XDA, and Google, and couldn't find any app to make the touch screen on the Titan interactive - similar to the way the Voyager touch screen works (quick vibrate when the screen is touched).
Is there any app like this? If not, can someone make one?
Thanks!
Click to expand...
Click to collapse
this is a oem out there i havent seen Cab for it
Dc_striker said:
this is a oem out there i havent seen Cab for it
Click to expand...
Click to collapse
I am sure you probably have. I have the copy of the program that enables this feature. I believe it is extracted from a phone that has haptic feed back. But it is an executable.
This program is faulty. It doesn't respond on every tap and has performance issues. Other then that there hasn't been another one developed.
I'm trying to find a way to fix the issues of of the one that I found. Maybe by creating a new way to enable haptic feed back like I posted on previews posts, but it might take time to develop because I'm still learning how to mess with WM Reg. and programming.
[email protected]$ said:
I am sure you probably have. I have the copy of the program that enables this feature. I believe it is extracted from a phone that has haptic feed back. But it is an executable.
This program is faulty. It doesn't respond on every tap and has performance issues. Other then that there hasn't been another one developed.
I'm trying to find a way to fix the issues of of the one that I found. Maybe by creating a new way to enable haptic feed back like I posted on previews posts, but it might take time to develop because I'm still learning how to mess with WM Reg. and programming.
Click to expand...
Click to collapse
i still havent tried the program out yet i really dont see the use for it
Let me know what you find out Carlos. I would agree with you that it may be better to have the phone vibrate maybe when any button is pushed instead of anytime the screen is tapped (or maybe have the option to choose?), and also have the option to turn it off. Lol, maybe we can call it "Taptics" instead of Haptics.
As for the LED's, I'll check with some of the other guys about what they can do. I do a lot of modding myself with other electronics (cars, motorcycles, game consoles, etc...), but I don't really get into programming all that much (although the logic makes sense to me).
-Paul
Okay, so I noticed the phone does vibrate, however, when using the keypad while in a call, it makes a different tone, and does not vibrate.
Also, is there any update on ways to make all buttons vibrate (and configurable) when pressed? And of course, an option to turn the feature off?
whiteblazer01 said:
Okay, so I noticed the phone does vibrate, however, when using the keypad while in a call, it makes a different tone, and does not vibrate.
Also, is there any update on ways to make all buttons vibrate (and configurable) when pressed? And of course, an option to turn the feature off?
Click to expand...
Click to collapse
I am not sure for all buttons but there is a CAB to make the phone vibrate when you press the screen. I tried it out and it works, but it's faulty and kills performance.
I'm still working on this project. I haven't had much time to work with it, but if any break through happens then I will post it up.

[Q] Better answer phone button. Or the iPhone complex.

Hy,
Previoulsly I was using a flased HTC Polaris. There was one great thing with this phone : buttons. Espacially incoming call answer button.
I love my X10, but I do have problem answering incoming phonecall. The slide button is very difficult to use with both hands, and impossible if you use your phone with one hand only (It could be a good thing for not answering while driving though).
I expected that flashing with a custom rom would solve this issue, as I was sure that everyone would agree with this point of view, but so far, I haven't tested a ROM that provide an incoming call button that isn't a slide button.
I believe that this slide thing (even for unlocking I don't like it) is some sort of iPhone like complex. Well to my point of view, an Android phone isn't an iPhone, and shouldn't try to look like an iPhone (espacially when it comes to details that are not so great about the iPhone)
Now to my question : is there a way to change the style of the answer button from this stupid and unpracticle slide button to a more simple touch button ?
There is a handfull of apps to do that... i listed some of them here, but i guess you can find even more of them:
https://market.android.com/details?id=com.lab1945.advphone&feature=search_result
https://market.android.com/details?id=org.nsd.easyanswer
https://market.android.com/details?id=tw.nicky.FullScreenCallerPro&feature=search_result
I guess some of them even allow you to use camera button to answer the phone.
The "iPhone Complex" is SO true...
Well said.
(I am using MIUI, but that's all about absorbing the good aspects of the iPhone and combining them with the Android power)
Lofwyr said:
There is a handfull of apps to do that...
I guess some of them even allow you to use camera button to answer the phone.
Click to expand...
Click to collapse
Great. Thanks a LOT.
I thought this kind of things would be changed only with a mod ROM.
Nope.. it's a case of "There's an app for that" !!!!!!

what dialer do you use?

I find the stock dialer on the Z2 super annoying. it's slow and laggy. If i tilt the phone just a little bit it decides to go into the super useful (NOT) landscape mode, often causing me to hit the wrong key. I'm sure there are other things pissing me off about this but can't think of any right now.
I'd like to learn if other people have the same annoyances and if you've done anything about it, i.e. replace the dialer with something else.
thanks
i oddly dont find my self across this problem
i use stock, CM11 and CM12
i usualy use stock which i dont have problems with
[w] said:
I find the stock dialer on the Z2 super annoying. it's slow and laggy. If i tilt the phone just a little bit it decides to go into the super useful (NOT) landscape mode, often causing me to hit the wrong key. I'm sure there are other things pissing me off about this but can't think of any right now.
I'd like to learn if other people have the same annoyances and if you've done anything about it, i.e. replace the dialer with something else.
thanks
Click to expand...
Click to collapse
One issue I have (not sure if its a Sony thing or Android) is when I move the phone away from my ear to use the dial pad and its so unresponsive, especially annoying when the call is one of those automated voice machine things and they tell you to press 2 or something, either the screen is slow turning back on the button takes forever to press
Ned_Flanders said:
One issue I have (not sure if its a Sony thing or Android) is when I move the phone away from my ear to use the dial pad and its so unresponsive, especially annoying when the call is one of those automated voice machine things and they tell you to press 2 or something, either the screen is slow turning back on the button takes forever to press
Click to expand...
Click to collapse
yes. i get this sometimes too.

Changing the Long Press Duration of Hardware Keys

Hi guys,
I just flashed android 10 on my oneplus 3 via Havoc v3.4.
I was wondering, whether somebody were able to help me with a kind of special problem.
So I'm using my home button to put the phone to sleep by long pressing it. This can be set in the phone settings. so far so good.
But now on android 10 the duration of said long press seems to be unnecessarily long, like over a second. Thats really annoying, when you just want to put your phone away and have to keep your finger on that capacity button for that extra amount of time.
So I was wondering, whether there might be a relatively simple way of tweaking the build.prop or something, to change the duration of said time_out ?
I already tried the hold/delay in the google settings, but that's just for touch inputs on the screen.
Also the forum search didn't pop up any usefull results.
Thanks so far!

General GSI for our phone Corvus OS

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.

Categories

Resources