yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Android Development] UltimateByte:
Man, i took time for testing today, i just tried both of those ROMs today, with a clean install, and just a few moment between them => i can say with quite of certitude that it's about the same input lag for those 2 ROMs and that they've got the best input lag i've seen for now on SGN2, or at least, slightly better than MIUI.

Dunnow what is their tweak in Alliance ROM, and now i'll stick with Omega that is one of my favourite ROMs, but i can tell you that i've tried some other ROMs that said buffer/vsync/touchscreen or whatever tweak, and didn't see any major improvement.
[Galaxy Note II Android Development] matejdro:
Sorry people, but unless someone can put those roms under slow motion cam, I call all those rom differences placebo.
[Galaxy Note II Android Development] UltimateByte:
I still have a friend that can lend me a 120fps Gopro (wich is twice the screen refresh rate, so enough already), i'll make tests as soon as i can, let's say 2 weeks maximum (i hope less).

But for sure, we can't compare accurately without two different phones at the same time, because 150 or even 300ms are hard to quantify.
[Galaxy Note II Android Development] Gnarfsan:
Re: [Dev request] Fix touchscreen input lag

Call it placebo or whatever you want. I will call the problem Project Butter and enjoy my rom with reduced input lag.

---------- Post added at 10:02 PM ---------- Previous post was at 09:49 PM ----------

So you are basically saying that scrolling is 100% smooth in the stock ROM and that there is no difference there between ROMs? I would say that there is a world of difference and that it's very likely that there is a connection with input lag. Every other type of lag is still software related eventhough the CPUs and GPUs are much faster. Besides 200MHz on each CPU core and 300 MHz for the GPU is quite significant.
[Galaxy Note II Android Development] matejdro:
Scrolling smoothness has nothing to do with input lag.
[Galaxy Note II Android Development] Gnarfsan:
The point is that scrolling lag has not been improved either. I had smoother scrolling with GB and the right setup on my S2 than I did with my Note 2 right out of the box. You cannot compare old software on old hardware to new software on new hardware.

And besides how do you know? A wild guess?

It's right there in OP. Disabling scrolling cache reduces input lag. Smoothing algorithms might do it too.
[Galaxy Note II Android Development] matejdro:
Scrolling lag = when device cannot update interface fast enough and you get dropped frames (scrolling "skips"). It usually means that device's CPU (or GPU) is completely filled up and cannot process things fast enough. Unlike with input lag, device knows you want to scroll, but it can't do that fast enough.

Input lag = delay between doing anything with touch screen (touching, moving finger, lifting finger etc.) and software on device reacting to that. Device does not know you want do something until this delay has passed.

Scrolling lag might trigger input lag as CPU would be too occupied to process touch events, but I don't think that is really likely as touch events themselves need little processing. And if CPU would be so occupied that it could not process touch events, then your device would probably be frozen rather than laggy.

Scrolling lag is partially resolvable by scaling up hardware (device can process more data and thus update faster), but if app is badly written, it would lag regardless of CPU power. Input lag is not resolvable by scaling up hardware as even years old CPUs have way more than enough power to handle touch events instantly.

At leas that is how I think of those two terms. But you might have meant something else.
[Galaxy Note II Android Development] Gnarfsan:
Exactly. It is the time difference between when you move your finger and the screen is done rendering. A lot of code is executed during that time.

I think that a good part of it is related to smoothing algorithms and resource management in Android 4+. If you keep changing timespans in which a certain peace of grahics moves from one place to another in seperate thread, you will get smooth but slow scrooling because the panel will keep scrolling while the next target and time is calculated. It would have to be very poorly coded to actually get freezes even with performance issues.
[Galaxy Note II Android Development] razorblader:
There is a simple solution for less input lag and faster (and more accurate) touch tracking for the Note 2.

Download and install SGS Screen Booster from the Play store (it's free) and open the application.

I've attached a screenshot with the default settings and the optimized settings that work for me.

Select the 'Super Optimized' preset, it will set Sensitivity to 28 (default 40), I've lowered it (lower values = higher sensitivity) to 0 without problems. Don't forget to check the 'Start Service on boot' checkbox to make the settings stick.

To see the difference try the method suggested by the OP by selecting 'Show touches' under System Settings/Developer Options, you should see an improvement in the speed of the input tracking with the optimized settings meaning even fast movements on the screen will still result in faster and slightly more accurate tracking of the movement compared to default settings.

It's also quite evident in SNote, the input delay of the SPen is reduced resulting in more of a 'real world' experience when using the SPen for writing or sketching.

It's not perfect but it does improve the input lag from pretty bad to IMHO tolerable levels.

Would like to hear feedback if this works for others as well.

For reference, I'm on ARHD 14.
[Galaxy Note II Android Development] Chrissssssss:
I've noticed the difference between my old Desire and my wife's Xperia Ray which are both gingerbread. When pulling the notification bar down the

graphics are far less smooth but the input lag is a lot lot less so I wouldn't be surprised if that is at least some of the reason.

Would be interesting to compare my Desire running ICS or JB to see if it's different. Can I be bothered though? probably not.
[Galaxy Note II Android Development] Tzarski:
Re: [Dev request] Fix touchscreen input lag

What Motion Filter for???

When set it to 0 I feel like the screen's reactions faster?
[Galaxy Note II Android Development] UltimateByte:
Already tried, and tried again : No improvement at all.

3 options

1) There is no imrpovement, and you're running under placebo effect

2) I don't notice the small improvement but you do

3) You've got an amazing phone that has a fix for the SGS1 working on it, but you're the only one.
[Galaxy Note II Android Development] UltimateByte:
I made a video about input lag, with some testing, but at 30fps, already enough to see a few things.

"I made this for you" guys ! (Kool Aid, Julian Smith reference)

Will be available in a few minutes after this post

http://www.youtube.com/watch?v=_MyfkypkNWk&feature=youtu.be
[Galaxy Note II Android Development] matejdro:
No improvement here either. I'm not sure what that app does but its probably placebo.
[Galaxy Note II Android Development] Chrissssssss:
Nice video. Can you do the same using a mouse to see if this is the display of the touch input? Something tells me this is something that can't be fixed.
[Galaxy Note II Android Development] UltimateByte:
Thanks :) Sadly, I don't have microUSB adapter for a mouse :(
[Galaxy Note II Android Development] Chrissssssss:
Shame. I will have to try and remember to try out this on my parents' camera when I'm around there next which has a 240FPS mode.
[Galaxy Note II Android Development] :
samsung needs to learn from apple when it comes to touchscreen input the iphones looks instant but im not really sure

imagine someone makes this for phones http://www.youtube.com/watch?feature=player_embedded&v=vOvQCPLkPt4
[Galaxy Note II Android Development] UltimateByte:
Sure, try it ! I'll try to get the 120fps gopro, to test different kernels (i don't wanna wipe my ROM again now, need a stable and efficien phone, i've got less and less free time these days), that will be enough already, as the screen is 58fps, the 8ms error margin will be negligible.

This link is on the main topic :)

But yeah, apple's recent touchscreens are slightly more responsive (divide samsung's time by 2 or 3)...
[Galaxy Note II Android Development] :
my moms iphone 3gs has a lower latency than my note 2 thats really depressing how a phone made in 2009 has a better touchscreen than a phone made in late 2012:confused:
[Galaxy Note II Android Development] UltimateByte:
Yes...

But the iphone 3g (not 3gs), even if better than a SGS3 or Note 2, has a worse input lag than the SGS1 :)

Still this SGS1, release 5 **edit** almost 3 years ago, and still better than a Note 2...
[Galaxy Note II Android Development] amerkiller1995:
Re: [Dev request] Fix touchscreen input lag

SGS1 was released in March 2010, 5 years is a bit too much

Sent from my GT-I9000
[Galaxy Note II Android Development] UltimateByte:
Oh yeah you're right. I thought i had been having it for 3 years and a half and that it was released 1 year before, mad was i when i wrote that, maybe because of the 25 hours of work in two days, i'm not used to it ! :p
[Galaxy Note II Android Development] Mohammed779:
Re: [Dev request] Fix touchscreen input lag

the s pen the hoovering cursor thing also has delay.. just like the touchscreen.. wouldnt that also say that's its a hardware problem.. or that is just a completely different thing..

Sent from my GT-N7100
[Galaxy Note II Android Development] UltimateByte:
Or that it's the same input detection's problem...
[Galaxy Note II Android Development] 3Dpixel:
Re: [Dev request] Fix touchscreen input lag

Where the calculated is done

Cpu or Gpu

And which is faster

And which one used iphone

(The youtube doc. Its hardware problem)

Verstuurd van mijn GT-N7100
[Galaxy Note II Android Development] UltimateByte:
Not sure to understand everything, your english is weird...

Here is what i know for sure : the capacitive touchscreen must have a dedicated controller (or interface/signal converter), that is linked to the cpu.

There could be a driver or program tweak for it, or the controller could just suxx.

The GPU doesn't cause a hardware latency itself, neither the CPU does, because their frequencies are hundred (GPU), thousand (CPU) megahertz, but there can be some frames buffering that add software latency on the display, not the input.

So 2 kind of latency : input (touchscreen detection), and display (buffering and hardware input lag).

Maybe the iphone has a better controller/converter or a better driver, or both... But anyway, the iphone is very far from being input lag free, it's more than 50ms, maybe 100ms for the 4gs, need to recheck the iphone 5 to tell if it's really better or not. Need to have an iphone 5 and a 4gs together to tell.
[Galaxy Note II Android Development] matejdro:
S4 appears to suffer from similar problems

http://www.youtube.com/watch?v=gEfG2K1EYlY (Look at around 4:50).
[Galaxy Note II Android Development] UltimateByte:
As i told into this topic, i saw that since the S4 Launch's day. I hate you Samsung.
[Galaxy Note II Android Development] amerkiller1995:
Do LG or Sony phones have this problem or is it exclusive to Samsung?

Sent from my GT-I9000
[Galaxy Note II Android Development] UltimateByte:
Nexus 4 seems to be even worse. I've seen sony with this issue...

But i particularly hate Samsung because their phones are the most interesting to me, and because of everyone being in crush for the S4 that is a superbomb... But with this ridiculous latency.
[Galaxy Note II Android Development] UltimateByte:
OK guys, got some interesting stuff, but hope someone can decrypt.

Here is the inside of a SGS4 http://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947/2

Is the Atmel the touchscreen controller ?

Found the datasheet http://www.atmel.com/Images/doc2467.pdf

Does anyone can tell if this can add a significant hardware latency ? Cause i've seen loads of 60+ms delays into it.
[Galaxy Note II Android Development] xartic12:
Has anyone compared the latency from the spen versus your exterior shell of your phalnges ? The spen on mine provides far more responsiveness.
[Galaxy Note II Android Development] UltimateByte:
Actualy, maybe it depends on the ROM, but at a moment, i saw the same input lag. After trying again under the last Omega ROM, i can say the S-Pen control is far more responsive, i think that you can reach about the iphone 5 responsiveness with it.
[Galaxy Note II Android Development] xartic12:
I'm running AllianceRomv3 and the response feels instantaneous with the s pen. My question is if these touchscreens have a longer delay for it to reactive to the amount of touch sensitive areas (the actual multiple spots the screen can register) as opposed to the spen having a radio frequency transmitter to provide a quicker response. Not that it should be any slower but it has to be Android as opposed to the actual touchscreen quality. Maybe newer phones equipped with higher dpi have more spots that register dpi.
[Galaxy Note II Android Development] UltimateByte:
Please read this

http://appglimpse.com/blog/touchmarks-i-smart-phone-touch-screen-latencies/

PS : I can't edit the initial post anymore, is that because it's not been modified for a while ? Anobody knows ?
[Galaxy Note II Android Development] lolmensch:
it's really a pity that google or the hardware manufacturers don't really care about it. (whatever the exact problem is, either hardware or software) I am really missing the responsiveness of my galaxy s2 on my note2. so weird that things get noticeable worse with theoretical better hardware.
[Galaxy Note II Android Development] UltimateByte:
Miss my SGS1 for that too... Let's drink dozens of beers and cry together.
[Galaxy Note II Android Development] scott.deagan:
Awesome post (and video) by the OP. I'd up-vote this a million times if I could.
[Galaxy Note II Android Development] UltimateByte:
Thanks buddy, don't hesitate to spam Samsung about it on every webstide you can see them (twitter, youtube, etc.), or any shop with a samsung demonstration...
[Galaxy Note II Android Development] Zanr Zij:
1. Totally Android can not compare to iPhone, Windows Phone about this

2. Note 2 has digitizer so response time even bigger.

3. With Odexed you will feel a bit faster response

4. With latest leak 4.3, a bit better again :)
[Galaxy Note II Android Development] scott.deagan:
I spread the word wherever I can, including directly to contacts I have at Samsung. There are many hurdles: the lag deniers ("no lag here"), definitions and terms ("lag" vs. "jank"), platform/brand zealots ("go buy an iPhone") etc etc etc.

You've taken the war on lag to a whole new level though - thank you!!
[Galaxy Note II Android Development] UltimateByte:
1) That's not a matter of Android or IOS, it's hardware isn't it ? My SGS 1 was faster than Iphone 4, and i guess 4S, iven running ICS.

2) What do you mean, how could a tactile detection be possible without a digitizer ?

3) Really ? Why that ?

4) Same question, why ? What part of the software can improve input lag ? WHERE IS INPUT LAG ?! :p

Thanks for saying, i'm flattered being considered as seriously involved in defending responsiveness. Yeah, Input lag deniers are a lot. I'm sorry for them, and i know that their feeling will be slightly better on devices with less input lag, even if they don't admitt it. Here is another example of that denial, check Robin Labadie's comment and Zeerak Waseem's answer http://www.youtube.com/watch?v=h9Sw20pJOrk
[Galaxy Note II Android Development] Zanr Zij:
1. Same hardware or even stronger, Android always lagger than iOS

2. That's the difference between S3 and Note 2, S4 and Note 3.

3. Because the principle of Odexed and Deodexed Rom.

4. The most important is kernel. With 4.3, touch screen sensitive improved. Try test Lockscreen.
[Galaxy Note II Android Development] Armazia:
Have you actually checked IOS 7?
[Galaxy Note II Android Development] UltimateByte:
Actually i did but on an Iphone 4, so the inpug lag was quite high. Higher than in my memories. Any source confirming a higher input lag in IOS 7 ?
[Galaxy Note II Android Development] UltimateByte:
OK guyz, still no solution, but here is a huge news : The input lag is only a display lag, the touchscreen lag is slightly inferior to it.

Why ? Because if you activate the touch vibration (for the keyboard) and haptic feedback, you feel like the vibration is in sync with your touches (so less than 50ms for sure, maybe less than 20ms, i will be able to measure it with a microphone when i got some time); on the other hand, the display is still 90 to 130ms late... So 2 solutions : laggy video software, or laggy screen/digital analog conversion. Maybe something to do with Pentile ? As SGS 1 and 2 were not Pentile, and way way faster than SGS 2 and 3.
[Galaxy Note II Android Development] Kiwito22:
This post doesnt help to improve input lag on the note 2... i just wanted to say im much happier with the note 3

I just got a note 3 and im happy to report that compared to the note 2 it has much less input lag. Sitting both next to each other and moving the notifications slider up and down with one hand you can clearly see how the note 2 lags behind. Also i can see it in games and everything else.

Both phones running 4.3(4.3 samsung leak on note ii)
[Galaxy Note II Android Development] Zanr Zij:
Note 2 with MJ5 Rom improved smoothness, input lag compare to MI6 :). Plz try again with it :)
[Galaxy Note II Android Development] matejdro:
Personally, I think there is no ROM that improves input lag. Only placebo.
[Galaxy Note II Android Development] nurbsenvi:
There is no cure for Android input lag period.

There is no cure for Android input lag period.

It's due to how the OS is constructed

Unlike iOS Android has some sort of middleware for the sake of compatibility across the vast

amount of different hardware.

I tried everything on SGS2, Xperia Z tablet and HTC One.

Nothing works.

And I couldn't stand the lag so I moved back to iOS.
[Galaxy Note II Android Development] thephenom696:
vsync

Disabling Vsync, Combined with upping the max.events.per.sec build.Prop tweak had completely fixed the touch delay issues for me, in the past.

Upgrading a reference xperia Ray 2011 from 2.3 to a 4.0 update, introduced a noticeably delayed touchscreen responsiveness.

Disabling Vsync had a definite, 100% rate of reducing touchscreen delays, both on my old Htc evo running android 4.0 and my new old Nexus 7 2012 (4.2 - 4.4)

There is something about the Android VSync implementation, from 4.0+ They managed to "improve " the touchscreen responsiveness in 4.1..4.4+ by optimizing Vsync for less delay, and mainly noticed when you disable Vsync.

We should research a bit on that.
[Networking] Product F(RED):
For AT&T compatible SIM cards, Net10 (Tracfone) has this to say:

https://net10data.com/

They're capping AT&T SIM customers at 1.5GB period. In some places it looks like it's 1.5GB and throttling after, but in the link above they make it pretty clear that it's 1.5GB

PERIOD

.

Tracfone owns Net10, STRAIGHT TALK, Simple Mobile, and basically most popular prepaid carriers. And since they stopped selling AT&T SIMs on both ST and Net10, it looks like us Straight Talk AT&T SIM customers can expect this next...

I use a Galaxy S3 i9300. There are some areas of my neighborhood with 1900 MHz T-Mobile coverage, but overall, not much. I'm at college and work most of the time, so it wouldn't benefit me to switch over to a T-Mobile SIM. I'd be on EDGE all the time. So this definitely sucks.
[Networking] rjr162:
When did they quit selling AT&T compatible SIMs? Im asking because I just got a Net10 one 3 days ago for the wifes unlocked Note II and my friend just got 4 StraightTalk ones last night...

And their websites (both of them) still say 2GBand throttle...

---------- Post added at 01:49 PM ---------- Previous post was at 01:41 PM ----------

Just checked net10sm and it looks like they updated the data info there as well.. well that blows
[Networking] elbaroark:
It's Unfortunately true.

They are capping data to 1.5GB of data/month for Straight Talk and Net10. I have a Straight Talk phone and spoke with a Tech Support lady named Karen at the Corporate office two days ago and she is sending out a new Galaxy S2 for Net10 so that I can switch back and then she is also providing me with the AT&T Sim that comes with the phone as well as a TMO sim for free as well if I want to make a switch, since TMO is not throttling customers until they reach the 5GB limit they have, which is WAY better IMO.

I got throttled just two weeks into my service when I switched from Net10 to ST on the 2nd of March. I use My Data Manager on Google Play and I have never went above 200 MB within a couple of weeks and they throttled my Straight Talk service down to dial-up speeds. Ah nostalgia. I am thinking about switching to TMO, even though they only offer 2G service in my home area in my small town, which when I am at home, besides making phone calls, I use my home Wi-Fi and everywhere else I need to go here in Missouri, they have 3g/4g speeds. So I may be good to go.
[Networking] Dr. Hax:
I really hope you're talking about some other version of the S2 and not the S2 that ST/Net10 sells...

That thing is obscenely overpriced!
[Samsung Galaxy S (4G Model)] domdroid6:
Hi I have a samsung t959v and I flash Team Acid Cyanogenmod 7.2 but when I put my simcard and put my simcard password it never get unlocked. There is a solution for that?
[Samsung Galaxy S (4G Model)] chacua358:
you cant do that anymore unlocking a phone has became illegal

http://gizmodo.com/5978982/unlocking-your-phone-is-illegal-starting-tomorrow

but there was a petition hope we win :fingers-crossed:
[Samsung Galaxy S (4G Model)] FBis251:
He doesn't want to unlock the phone, he's got a lock code on his sim card. I believe that none of the MTD roms we have (cm7, ics, jb) had the ability to unlock your sim, so you should flash back to stock, remove the sim passcode and then flash the MTD rom again.
[Samsung Galaxy S (4G Model)] hechoen:
Read that article that you linked. It's only illegal if the phone was purchased on or after Jan. 26th. Even then if you unlock it do you really think your carrier will begin legal actions against you?

OP

Where did you get the lock code? Unlocking these phones generally requires you to be on a stock based ROM. I believe some have had success unlocking from other ROMs but I'd flash back to stock then enter the code then reflash CM7.
[Samsung Galaxy S (4G Model)] FBis251:
Laggy network... Made me double post...
[Samsung Galaxy S (4G Model)] chacua358:
ok thanks i ge tit now hechoen but yhea as you said i tried to unlock m phone but it never worked only worked for me on audiphile froyo rom it didint work for me on gb
[Samsung Galaxy S (4G Model)] domdroid6:
I can with Cyanogenmod 9 and others

I can unlock the sim card with ICS mtd roms but I prefere Cyanogenmod 7.2 because it is more stable. There is any bug fix?
[Samsung Galaxy S (4G Model)] Rebel_X:
Like they said above, Do a full Nandroid backup, flash to stock, unlock, flash to

CM7, then restore your nandroid backup.

Shouldn't take more than 30 minutes. I hope this will help :)
[Samsung Galaxy S (4G Model)] gizmoscoop:
I wonder who is going to enforce this law? It would be funny if a cop came to your house and arrested you for breaking this stupid law, on a phone that you bought and paid for in full.
[Xperia Z Q&A, Help & Troubleshooting] nintendolinky:
hey guys, whats the keyboard apk called.
[Xperia Z Q&A, Help & Troubleshooting] avetny:
I think Textinput-tng.apk
[MDA, XDA, 1010 General] Li:
Hi ,

I am using the XDA O2.

I found the 'Request SMS text message delivery notification'is very useful

when I send SMS to others. But I have to enable it everytime. How can I

always open this function ? maybe to modify the XDA O2 registry to get it?

Are here anybody with rich knowlege can raise a solution for me?

li.ding@storaenso.com

:cry:

Great Thx

Li
[MDA, XDA, 1010 General] Tim C:
you can put

*0#

as the first part of the subject. It's not permanent, but only takes a few seconds to type.

Regards

Tim