[REF] Solving touchscreen sensitivity issue - Galaxy S II Original Android Development

As some of you have noticed SGS2 touchscreen have quite an annoying issue - it starts to register movement only when you have moved finger on screen quite a bit. Probably this video will explain it better: Youtube video. (original thread)
I have analyzed kernel sources and found ways to fix this issue, so the touchscreen will behave normally like on SGS1.
1) use attached app. Obviously you will need root for this. Just drag slider to 0, press "Apply" and press "Enable serv.". That will make service to autostart when you reboot, and apply settings after every screen lock/unlock cycle. Please note - some people reported that movement becomes a bit jerky immediately after applying setting, so just lock/unlock your phone. At least for me everything is smooth then. Also you can play with advanced settings if you feel adventurous
BTW you can test settings in this app too - large black area is a multi-touch tester as well
2) any custom kernel maker - just modify file /arch/arm/mach-s5pv310/mach-c1.c
you need to change this config structure (and of course mention me and this thread in your kernel description ) :
Code:
static u8 t9_config[] = {TOUCH_MULTITOUCHSCREEN_T9,
131, 0, 0, 19, 11, 0, 32, MXT224_THRESHOLD, 2, 1,
0,
15, /* MOVHYSTI */
1, 11, MXT224_MAX_MT_FINGERS, 5, 40, 10, 31, 3,
223, 1, 0, 0, 0, 0, 143, 55, 143, 90, 18};
change
Code:
15, /* MOVHYSTI */
to
Code:
0, /* MOVHYSTI */
AND guys if you find it useful, don't be leechers, buy me a beer, I spend a lot of time figuring all of this out
link to buy a beer

Good job, mate, good job. Thank you.

You sir! are a hero! This is so much better when playing games!

On the SGS1 I remembered there was some service menu code to change the touch screen sensitivity and some kernel changes as well that didnt rely on running an app, would that be possible on the SGS2 in the future as well ?

GREAT job!! really well done, works without any hiccups
PS - if it annoys anyone that the su app allows this app permission after every screen on, just switch off notifications in the su app!

So the 2nd option is the better option because you don't have to constantly have a service running setting this every unlock which would use battery and maybe other things?

Whats all these advanced options? You able to explain what they do?
Or is there any interesting ones worth mentioning ?
What does MOVHYSTI stand for
Ooo and another thing is there a way to edit a kernel thats all ready been compiled to have this change? Like hex edit or something

thanks for this great app
at first when i had similar problem i though it was just me
but it turned out to be a problem for all
so thanks for fixing it

Thanks for this m8 , really works!
Lite 1.5/Tegrak's kernel/1500Mhz

This seems to have broken certain things. Put ur phone down and with 4fingers make a square. Some touch points disappear now (like on the s1)

bcam117 said:
This seems to have broken certain things. Put ur phone down and with 4fingers make a square. Some touch points disappear now (like on the s1)
Click to expand...
Click to collapse
this occurs even without applying this fix. not really a problem though as it dowsnt happen if held in the hand

Thanks for the tips, I have not trouble with 4 fingers in square.
I have made a translation for french here with your thanks link.

The square thing happened even in my hand after applying settings PLUS the sensitivity seems to really decrease. To test this I basically just use my nail or part of my nail on my finger. And yes I locked/unlocked. I will experiment more. And I am not trying to be an a** to the dev just stating my experience so far.

Also, putting it on 0 can make the phone register tiny swipes as clicks. (which you actually meant to be swipes)
Nonetheless, I rike it!

Ok I rebooted my phone and locked/unlocked it and this time everything seems to be fine
I might have been locking/unlocking it too quickly or something before.
Anyways awesome work.

does it work with all roms like CM7 and MIUI?
Greetz and nice work

redbull320 said:
does it work with all roms like CM7 and MIUI?
Greetz and nice work
Click to expand...
Click to collapse
Yes...................

Huh whaa?? Just got back from work so im tired but do u mean u have to apply this after every screen lock/unlock cycle?? :-/
Sent from my GT-I9100 using XDA Premium App

It's working great
Hope everybody will change this in their roms by default.

Working great. But the notification after every unlock is kinda annoying. I know I can turn that off globally, but this leaves me with an insecure feeling.
Sent from my GT-I9100 using XDA Premium App

Related

[Q] Motion Sensor working in reverse?

Hi,
Whenever I try a game that uses the S2's motion sensor like Glyder or Nova 2, left and right seem to be switched. Maybe its me, but it just feels wrong when you lift the left side of your phone and your view or character goes left as well.
Does anyone know if this is configurable, because it doesn't seem to be an option within the games.
Thank you for any feedback.
Regards,
Karel
Calibrate your sensors (Settings > Display Horzontal/Gyro Calibration) and also check in-game settings?
karel3s said:
Hi,
Whenever I try a game that uses the S2's motion sensor like Glyder or Nova 2, left and right seem to be switched. Maybe its me, but it just feels wrong when you lift the left side of your phone and your view or character goes left as well.
Does anyone know if this is configurable, because it doesn't seem to be an option within the games.
Thank you for any feedback.
Regards,
Karel
Click to expand...
Click to collapse
Get glyder from the market instead of Samsung Apps. The one from Samsung doesn't work properly.
Glyder also does this on my phone. Tried calibrating, assumed it's a game glitch.
Hi,
Thank you all for the tips.
I've actually tried horizontal calibration, but nothing changes.
I'll try downloading the Glyder app from the market instead and see if that makes a difference.
For Nova you can actually set the gyro settings to 270 degrees instead of 90, but then up and down handles a bit awkward.
I'm guessing there is no solution for this yet so I'll wait for someone to release an app for this someday.
Just one of the disadvantages of a brand new phone model
Wow! I thought that was how Glyder was supposed to be ... I actually got pretty good at the controls
Update
Just a quick update to say the market Glyder app is working fine.

[Q] Serious multitouch issue - most obvious in games

Bear with me here, this issue is kind of hard to describe. When I am playing a game that requires touch inputs from both hands, I often get bugs. It's most obvious in games that have controller-style overlays. As is normal, I am using my left thumb to tell a character to move right or left, and then I press the button on the right to jump. However, when I release my jump, I stop running. The screen no longer recognizes that my left thumb has been pressed down the whole time and should still be moving in the direction I am pressing. This happens in Bean's Quest, Chono'n'Cash, Delver, Gunman Clive, and any other game of this nature I have tried on my device.
I played some of these games just fine on my old Evo. Is anyone experiencing this issue? I experienced it on stock as well as several custom roms I have tried.
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
gutrrob said:
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
Click to expand...
Click to collapse
Doesn't seem to have fixed my issue, I am still having problems with some two finger games. I will be using two fingers just fine, when I remove one finger from the display the first finger is no longer recognized even though it is still touching. I have to remove the first finger and press it again every time.
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
ryanalan82 said:
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
Click to expand...
Click to collapse
Appears that widgetlocker is the culprit! Is this issue documented or known, exactly? What causes it? Thanks so much for the help. I will surely miss widgetlocker.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I encountered this recently
It seemed to get "stuck" after using multi touch gestures in-game. Tapping the game with two fingers often "unstuck" it, but overall it was extremely frustrating.
This was on an APK not designed for the phone, though
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Racer Of All said:
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Click to expand...
Click to collapse
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
ryanalan82 said:
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
Click to expand...
Click to collapse
Did you try my edit 2? The Retain System keyguard? I can assure you that I have Widgetlocker installed and I have the 10 inputs (that video was recorded with widgetlocker running).
[SOLVED!] - HTC Evo 4G LTE touch screen trouble - WidgetLocker is the problem
Retaining system keyguard in WidgetLocker worked for me! Thank you for this Racer for All. (Actually I found your YouTube video, and a link to this thread)
I was wondering why all the games I played all of a sudden stopped functioning properly (in terms of touch controls... Example: MineCraft PE, moving forward and trying to look left or right - suddenly character would stop moving.)
Sorry to dig up an old thread, but I want people to know if they have WidgetLocker (and don't want to uninstall it) just go to Settings - Advanced - Retain system keyguard - zmag

[Q] Is the Z2 just REALLY slow to respond?

I've had my Z2 for a day, and before I bought it I read a review that measured phone reaction time between when the screen was clicked and when the phone started to react and it was DOG SLOW. Now I'm definitely experiencing the same. I mean there is noticeable lag when clicking something (like the Home button for example) and when the phone actually starts to take action. Is this normal? Is this just due to Sony's Android Customization?
Really?!! My experience is exactly opposite. I think the phone's touchscreen is too sensitive.
So I usually type wrong... ( Maybe it's my personal problem)
carbonmeteor said:
Really?!! My experience is exactly opposite. I think the phone's touchscreen is too sensitive.
So I usually type wrong... ( Maybe it's my personal problem)
Click to expand...
Click to collapse
Yeah the problem isn't sensitivity, it's responsiveness. The screen sensitivity is fine, it's just that the time it take between when I click the Home button and the point at which the Z2 actually STARTS to close my current app and bring me to the home screen seems WAY too long to me. Not sure if the review I read and my experience is normal or is the reviewer and I both have phones with issues.
I see... I misunderstood your words~~
Did u upgrade the firmware ? OR the problem had existed from the beginning?
Coz it's seldom that a new phone has such...lag
My phone did update when I started it for the first time, but I don't know how it was before the update since it was brand new.
SwarlosEstavez said:
My phone did update when I started it for the first time, but I don't know how it was before the update since it was brand new.
Click to expand...
Click to collapse
For myself, I usually do a factory reset after a OS version update~ otherwise waiting for the next update released by official .
I always do a factory reset on system updates. Prevents a lot of weird things...
Sent from my SGP312 using XDA Premium 4 mobile app
SwarlosEstavez said:
Yeah the problem isn't sensitivity, it's responsiveness. The screen sensitivity is fine, it's just that the time it take between when I click the Home button and the point at which the Z2 actually STARTS to close my current app and bring me to the home screen seems WAY too long to me. Not sure if the review I read and my experience is normal or is the reviewer and I both have phones with issues.
Click to expand...
Click to collapse
Maybe its the default animation of the default launcher. Personally I don't seem to have this problem, when I press the home button it goes straight to the homescreen, there is no delay but I don't use the default launcher.
Go into developer options and turn animations off, maybe this might help you
Settings>About phone>Build number, keep clicking it until you unlock developer mode
SwarlosEstavez said:
I've had my Z2 for a day, and before I bought it I read a review that measured phone reaction time between when the screen was clicked and when the phone started to react and it was DOG SLOW. Now I'm definitely experiencing the same. I mean there is noticeable lag when clicking something (like the Home button for example) and when the phone actually starts to take action. Is this normal? Is this just due to Sony's Android Customization?
Click to expand...
Click to collapse
Nope. My Z2 responds very quickly. It may be a problem with your device.
Same goes, although i curently have a very defective unit, everything is very rapid
I agree with @nreuge this could be a fault with your device
Sent from my D6503 using XDA Premium 4 mobile app
My z2 sometimes lags too, not much, but I can feel it,
How about a backup and a hard reset then? It helps to that most at-times.
Definitely more sluggish than the HTC One M8 and iPhone 5s. It isn't as bad as the Galaxy S5 though.
Sent from my iPhone using Tapatalk
Its far from sluggish, and the speed at which home button reacts to your press isnt really a deciding factor in phones performance..
Thanks for the responses everyone. I did a factory reset and it did help a bit. I guess the phone just isn't as fast and responsive as others on the market. It's a far cry from the Nexus 5 and the HTC M8, but I'm sure that over time I'll either get used to it or flash a custom rom on it.
The Z2 isnt as slugish as people have mentioned
I can play almost all games around -40-60fps
If you cant acheieve this and have no lag at all lag through home or navigating apps, your unit is probably defective
Sent from my D6503 using XDA Premium 4 mobile app
feis said:
Its far from sluggish, and the speed at which home button reacts to your press isnt really a deciding factor in phones performance..
Click to expand...
Click to collapse
You're right it's not, but a Snapdragon 801 shouldn't hesitate to go to the home screen when you press home.
Envious_Data said:
The Z2 isnt as slugish as people have mentioned
I can play almost all games around -40-60fps
If you cant acheieve this and have lag through home or navigating apps, your unit is defective
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This has nothing to do with gaming performance. I can play all games without any stutter, but as soon as the home button is hit or the recent apps button is hit, it will hesitate before opening or going to the homescreen. It's not "defective", something is just making the phone sluggish.
OP, I removed the small apps launcher from the recent apps panel and it seems to be a bit faster, though still not instant.
Ya, it is not about playing games, it is these little things, like home key, camera app, setting manual, recent app key.....
the z2 is a bit slow and lags compares to other flagships. It is not too bad, but the lags are there. It doesn't happen all the time.
If you are coming from dual core phones you will not notice it, however if you are coming from M8 or S5, you will notice it.
Hopefully the next update will fix this.
No phone is perfect, overall I am very happy with the z2, except the audio......:crying: I will get used to it.
If you need to speed up the phones response try altering the 'Drawing modes' for Window animation, transition animation and animator duration scales.
To do this you first need to activate Developer mode.
Go to Settings/About phone and at the very bottom of the list tap on Build number eight times.
This will bring up a small warning informing you Developer mode is now active.
Next, go back to Settings and you will notice in between Printing and About phone you now have 'Developer options' available.
Tap on Developer options and scroll down to the 'Drawing' section.
Where it says:-
Window animation scale
Transition animation scale
Animator duration scale
Change these three settings from 1x to .5x
You should now notice your phone is much snappier and responsive.
Beards said:
If you need to speed up the phones response try altering the 'Drawing modes' for Window animation, transition animation and animator duration scales.
To do this you first need to activate Developer mode.
Go to Settings/About phone and at the very bottom of the list tap on Build number eight times.
This will bring up a small warning informing you Developer mode is now active.
Next, go back to Settings and you will notice in between Printing and About phone you now have 'Developer options' available.
Tap on Developer options and scroll down to the 'Drawing' section.
Where it says:-
Window animation scale
Transition animation scale
Animator duration scale
Change these three settings from 1x to .5x
You should now notice your phone is much snappier and responsive.
Click to expand...
Click to collapse
That does make a difference, thanks!

[HOW TO] Increase touch sensitivity and Double-Tap-To-Wake Functionality(Force Touch)

First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Awesome, T2W works better now.... Thanks
P. S. Adding your thread to my all in one place guides.
xgerryx said:
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Click to expand...
Click to collapse
With the shortcut master i had several loading problems, i used QuickshortcutMaker and this is more easy, Thanks !
xgerryx said:
First of all, thanks to @xtermmin for pointing me in the right direction for this.
Steps to increase touch sensitivity and get DTTW functioning better:
Download Shortcut Master Lite
Hit the ellipsis at the top right and click App Explorer (Yes to the error)
Tap anywhere to get the loading circle to go away and find something called Force Touch
In the Force Touch menu, select ZteLCDPressureSettings and hit Launch
Here you will find some options.
Tap Pressure Sensitivity and move the red dot slider all the way to the left where the green "Light" is.
Back out of the menu and you are done.
There are some other things under features that may be of interest as well to some people.
Additionally, there are a couple other items in the Force Touch menu that could play a role in ROMs down the line. The "Press Image" option has a toggle within that item but it does not stick upon backing out and reentering the menu.
If you find anything else of interest, please let everyone know so we can make this the best phone we've ever owned.
Thanks!
Click to expand...
Click to collapse
This definitely helped! Kinda odd that there is a slight delay from when you double tap and when it actually wakes. I remember the LG G2 responding more quickly with this feature. Also miss the double tap to lock screen too that almost no other phone had (though with nova launcher and an app, you can do this). Regardless, I'm glad the functionality is there.
What's interesting about this little hack is that it clearly is using the force touch settings that will be found in the 6GB RAM model that has a force touch display. Funny how it remains in the ROM anyway, just tucked away since this model doesn't use force touch.
Can I remove the vibration when I use the double tap to wake?
This has made 0 difference for me. I've got a 64gb US variant. I've also noticed double tap to wake stops working when the phone is in Doze. Anyone else have this issue?
Same same with doze, but when my phone isn't deeply asleep this tip indeed increased touch sensitivity.
Sent from my ZTE A2017U
DrakenFX said:
Awesome, T2W works better now.... Thanks
P. S. Adding your thread to my all in one place guides.
Click to expand...
Click to collapse
Did you know this app is also present on the a2017u usa version?
But it is not doing anything...
manu7irl said:
Did you know this app is also present on the a2017u usa version?
But it is not doing anything...
Click to expand...
Click to collapse
I'm using the a2017u LoL always has been.
tolymatev said:
Can I remove the vibration when I use the double tap to wake?
Click to expand...
Click to collapse
Is there a setting to disable the vibration with double tap to wake?
I've tried the mod but don't see any differences for better response for the double tap to wake.
Sent from my iPad Air 2
I don't have anything like force touch in quick shortmaster app or shortcut master lite. I'm on european B03 update... Can anyone confirm this?
kodrnusa said:
I don't have anything like force touch in quick shortmaster app or shortcut master lite. I'm on european B03 update... Can anyone confirm this?
Click to expand...
Click to collapse
It's actually there as been always and with B02 software version.
Do hard reset if not see it
Something get wrong with upgrade in your case.
pklee said:
Is there a setting to disable the vibration with double tap to wake?
Click to expand...
Click to collapse
Don't have vibration with double tap.
How did you get it
paatha13 said:
Don't have vibration with double tap.
How did you get it
Click to expand...
Click to collapse
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
rczrider said:
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
Click to expand...
Click to collapse
Totally agree with this. It's still very inconsistent, but mine does work if I slam it twice as well as tap it lightly twice. It doesnt always work and it's still delayed. This was sort of a bandaid for a bigger problem though. I hope CM, and ....probably nothing else? at this point...can address it further.
rczrider said:
It's there by default on the US model, at least.
While this definitely improves DT2W functionality, it's still temperamental. I find that now it responds best to very light touches, but harder taps are ignored. If I tweak it to be less sensitive, it does exactly that: it requires a harder touch at all times. Why can't it just respond to a range of touches? My G3 worked just fine in this regard.
Click to expand...
Click to collapse
At EU version I don't see any option for vibration so far.
But totally agree I would like to be more response to a range of touch.
I remember when had LG flex 2 was better implementation than ZTE.
Hope future update improve that.
Sent from my iPad Air 2
paatha13 said:
At EU version I don't see any option for vibration so far.
But totally agree I would like to be more response to a range of touch.
I remember when had LG flex 2 was better implementation than ZTE.
Hope future update improve that.
Click to expand...
Click to collapse
Quite honestly, the Axon 7's story is perpetually: "[insert company here] did a better job of implementing [insert feature here]". There is very little (if anything) that the Axon 7 does better than the big manufacturers, IMO. It does a passable (sometimes even decent) job of most things, though - and at an appreciable discount - which is why I still have mine. It's a budget flagship. It's high-trim Toyota versus a Lexus. Add to that the potential for improvements via software (which is the source of many of my complaints, really), and I think it's a solid buy with quirks I'm willing to live with for a little while as ZTE steps up and makes improvements.
Yep exactly from hardware point is very very capable device but from software although it's pretty good level but there's still staff for many improvements.
Axon 7 is my first Chinese smartphone from Chinese company until now and I'm quite pleased with the all package offering having it 5-6 days,but I would like to see from ZTE much more effort and listening the user base and bring as much improvement and tweaks to the software.
Sent from my iPad Air 2
paatha13 said:
It's actually there as been always and with B02 software version.
Do hard reset if not see it
Something get wrong with upgrade in your case.
I already did factory reset. And then again . No such setting in quickshortmaker. I can post pics.. Weird...
Edit..
Did change language to English and found it ?
Click to expand...
Click to collapse
I notice no difference in the week that I used this tweak. So I just put this settings back. Yup, still no difference to me.
Sent from my ZTE A2017U using Tapatalk

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