Team,
I've upgraded my S2 to I9100XXLPQ (installing Apex launcher additionally for the personal reasons ;-)). Generally the phone works just great, no big problems found.
Except the one really annoying - the scroll performance. It is smooth, but it reacts somehow weird. Can you feel it too?
For me weird means (tested on Contact List):
- it's not consistent - doing the same moves on the screen gives different scrolling of contacts, sometimes just by few names, sometimes by the half of list
- it reacts with a small delay, can be observed if you tap&hold the screen and then slide your finger
- if I slide my finger I feel like sliding the paper on a table (sometimes I'm able to slide it, sometimes not).
It may sounds funny what I'm writing here, but I'd like to ask you, what's your experience and if the scrolling somehow customizable (i.e. it can improve with another update).
Thanks!
Maciej
Its a known issue. Try lp7 which is having similar scrolling like gb
Sent from my GT-I9100 using XDA
This is very old news. Check the lpq thread and you will see many people have reported it. There is even a thread in general about how to improve it.
Supposedly lp7 is better.
Sent from my GT-I9100T
like people above me said: known issue. just flashanother stock ics! like DXLP7
Related
I have noticed that the flick sensitivity is very bad on the Galaxy Tab 10.1. In order to scroll anywhere, I need to do long, sweeping swipes across the screen. A small flick should scroll quite a bit but only scrolls about half an inch.
I have installed ToucScreenTune and used it to Tweak sensitivity as well as adding the build.prop edit, windowsmgr.max_events_per_sec=300. But flick scrolling still just does not work.
Is there any solution to this?
Bump
Anyone got any idea?
ICS 1 solution ....... maybe
decoyjoe said:
I have noticed that the flick sensitivity is very bad on the Galaxy Tab 10.1. In order to scroll anywhere, I need to do long, sweeping swipes across the screen. A small flick should scroll quite a bit but only scrolls about half an inch.
I have installed ToucScreenTune and used it to Tweak sensitivity as well as adding the build.prop edit, windowsmgr.max_events_per_sec=300. But flick scrolling still just does not work.
Is there any solution to this?
Click to expand...
Click to collapse
you can try the ICS roms which are available since they mostly do not have lag issues like honeycomb .......
I use Task 14 and don't have lag issues or flicking issues being too little for me. Actually the opposite happens to annoy me more depending on where I am when I flick. Some things seem to scroll forever, or way too far and fast. Some are just fine. Makes me think it's more of issue with things other than what ROM your using. Sadly, I don't have an answer, just a comparison.
Sent from my GT-P7510 using XDA Premium HD app
Has anyone noticed a change in how the touchscreen behaves after installing ICS?
It seems to me that it is biased a little more towards interpreting a touch as swipe or scroll rather than select. For example clicking links in a webpage or tapping icons on the homescreen seem to require a much more deliberate effort to select/open. It's not awful, but I would like to be able to bias it back a little more to selecting rather than swiping.
Is there a setting for this anywhere or an app available that allows adjustment?
I would to know too.. I hate this..
But it's not just from latest ICS 4.0.3 International, the Beta version also suffer same thing.
Is HC not like this? (I upgraded to 4.0.3 Beta as soon as after bought Mediapad )
Yes, I noticed it also. When you turn on Settings - Developer options - Pointer location, it clearly shows how your clicks/dots becomes swipes/lines.
yes, you're right.. it sometime (most time ) cause texting experience not so fluid (letter not appear as it's detected as swipe not click).
got the same thing.. i've changed the launcher, so with the Apex launcher it's not that bad in the homescreens.. when i enabled the option to show "pointer location" i can see the "tap" as a line, or a "swipe" line :\
tried the same on my Galaxy S, and all the "taps" are only a small point.. it's much better than on the MediaPad.. i hope it's just a software issue and it can be solved..
maybe, we could try something like "screen booster" or "touchscreen booster" from the Market (Play)
Erratic screen while charging
The other thing I've noticed after ICS international is that the touchscreen is now erratic while charging and in a case. I believe this is a common problem with capacitive touchscreens, but hadn't noticed it until after flashing ICS. It is not an issue if I remove the pad from the case and hold it in my hand.
Anyone else seen this?
This sensitive touchscreen isn't Angry Birds friendly. Constantly shakes a little bit.
soooo.....is there any solutions?
noaustin said:
soooo.....is there any solutions?
Click to expand...
Click to collapse
Not unless huaweis coders tweak it or releases the source code.
question and observationsstion part:
1. Has anyone noticed a white washed effect one their prime every so often? I am having this issue where reading something in black/white, the letters seems to be washed out and the white over powers the black text line definition so it becomes a white blurish effect.
1a. I have also noticed my led display has this "oil spill" under the glass somewhere in the upper middle area. A little minor grab of the prime on certain corners moves and reshapes this "oil spill". Does this have anything to do with #1?
Observation:
Not a super tech junkie but is there some sort of a memory leak in the ROM? I have noticed the reboot happens when the Asus task manager craps out and when ics+ browser is handling some open tabs with at least one tab with a video playing. I may be completely off here but that's just my observation. It seems the prime slows to a crawl with a few apps open and it speeds up when i close them but then it reboots when I reopen the same apps (mostly ics+ and maybe maps and translator and opera). I am going to stop using ics+ and use opera and see if it does this. I am also using dolphin so I'll be switching around however I am wonder if anyone has found a rhythm or rhyme to the rebooting issues.
Thanks!
Well the reboot thing isn't new,but you know there is a limit of available memory so if you're like me, opening closing apps like crazy and complaining about when one of them eventually crash you're just rising the pole. I use system panel to track how the device is doing and if in need of something to do to it.
I've had the wash out effect happen when you hold it on certain angles. I posted a thread about it not too long ago because I noticed my TF101 didnt do this. So I had asked some people who had them both to compare. The last post in the thread the poster noticed it as well.
http://forum.xda-developers.com/showthread.php?t=1669860
Got the OTA update to L on my 6833. Yes, it has made the already smooth animation slightly smoother but otherwise what is there? The power widgets are gone, I had to install third party Power Toggles app. The new notification swipe down is annoying, having to swipe up when waking device is annoying. The status bar colors are inconsistent. The menus look childish looking.
Without being dramatic, did Sony take all this time to make sure it ran without crashing? Because I notice very few changes (not even improvements, just any changes) on the UI. I must be missing something.
more than that:
can only set one volume at a time.
either portrait or auto, you can't force landscape like in KK.
animations are fluid, but the functionality isn't. My opinion is, if the device has extra power that it can use to make things animate, slide and fade all over the place, better to put that extra power into making the device perform faster. Anyone here who prefers prettier animations instead of faster functionality?
low resolution screenshots in the recents screen. wat. Seriously... wat? Also, the way they've made it it is faster to just go to the apps screen and open whatever app i want, instead of waiting for the recents screen to load and then scroll awkwardly through the programs... Also, you can only see three recent apps. On a device with 6" of screen. three. think about it.
Also... what is the point of having screenshots, anyway? icons are faster, easier to distinguish, take fewer resources and smaller area on screen.
I agree fully on the recent apps screenshots. The blurry images are embarrassing and don't at all go with the clean/sharp theme of everything else. I don't understand why they've made it low res, can't be for performance given no restraint or need anywhere else. Bizarre!
There is over-prettying. For example, the stupid screen swipe up to unlock (after hitting the power button already), the sparkles are just so unnecessary, it is one of the few places the phone actually seems to struggle pulling off the effect.
At the moment my biggest problem is with Yahoo Mail. The account does not seem to auto-sync despite all the settings being correct and even when I force the sync manually the notifications don't show. I've uninstalled and reinstalled, most likely Yahoo to blame, their webmail is always breaking but never ever had a single issue before with KK. This is problematic because it is effectively no longer push email, I have to manually check 50 times a day.
My biggest annoyance is the inability to reclaim the Google search bar area in the Home Screen. I don't want that search button, why can't I use that space, and why a stupid dot to represent the pages of the Homescreen when I only have 1.
Is there actually anything different/new on the backend? My issues aren't severe enough to go back to KK (yet) but seeing what I see, I would have no problem whatsoever buying an Xperia Sony will not upgrade beyond KK.
jess91 said:
Got the OTA update to L on my 6833. Yes, it has made the already smooth animation slightly smoother but otherwise what is there? The power widgets are gone, I had to install third party Power Toggles app. The new notification swipe down is annoying, having to swipe up when waking device is annoying. The status bar colors are inconsistent. The menus look childish looking.
Without being dramatic, did Sony take all this time to make sure it ran without crashing? Because I notice very few changes (not even improvements, just any changes) on the UI. I must be missing something.
Click to expand...
Click to collapse
I agree with you about small changes. I even face some strange problems in my WiFi. the mac address haven't change, but I can't connect to my work WiFi protected network. Sometimes it connects in limited status. One of my friends which updated his Ultra has this problem too.I could connect it to my laptop adhoc wifi netwrok, but for one time. it even can't connect to that network anymore. I rolled back to my stock 14.4.A.0.133 backup. and a'm waiting to fixes from sony.
Agree with you guys. And that stock greenish blueish greyish statusbar color pisses me off! Anybody knows how to change that color?
Quite pathetic attempt by a mod to bury this thread by moving it to this section. If negative feedback on L bothers you so much, delete the thread and censor it outright. Sad day for xda.
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.