yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] alex is alex:
Hi, have you found a solution for this? I'm experiencing the same issue, but I have unfortunately not found a solution.

I have S$0.85 in my Google Play balance. The message says that I cannot change my country unless I have less than S$10.00 left. I'm trying to change from Singapore to Philippines, but everytime I try, the same message keeps appearing.
[General Questions and Answers] eddy2060:
Google wallet adress changing problems

When ever you purchase anything via google your purchase is on pending till next 48 hours. So in that period you can't change your adress, many people will try to help and say that your balance should be 0 but thats false, your balance should be less than $10 and you can change your adress 48 hours after your last purchase.
[HTC Rezound] trud9340:
Previously, I was on TRON 1.2 and had no issues with ADB and/or USB tethering.

Since updating to TRON 2.0, I have not been able to tether my usb connection via adb (ive tried clockworkmodtether, pdanet, klink).

USB debugging is enabled. I tried disabling, rebooting, and enabling again, but I have had no success.

When I run "adb devices", it tells me my device is offline.

BTW, I am on windows 7 64 bit.

Thanks!
[HTC Rezound] El Schisne:
To use adb in 4.2.2, you need the most recent version of Android platform-tools from the SDK. Open the SDK Downloader like you did when initially installing adb and update the platform-tools package. (Make sure you kill any instances of the current adb process/daemon running on your computer.) It should be able to connect after that, although you'll be asked to authenticate it on your phone the first time you try.
[HTC Rezound] trud9340:
Thank you, I updated my sdk and its working like a charm!
[Galaxy Note II Android Development] UltimateByte:
Reserved space
[Galaxy Note II Android Development] nabilsweet007:
Useess
[Galaxy Note II Android Development] UtkarshGupta:
Re: [Dev request] Fix touchscreen input lag

Yeah posting other's work under your name and not giving them proper credits is useful.

Sent from my GT-N7100
[Galaxy Note II Android Development] UltimateByte:
TROLL SPOTTED

And giving a stupid personal judgement without any explaination is very usefull ?

I don't see the point : How could any improvement be useless ? Especially if some of us find this issue very unpleasant, and if it's directly about what you feel (consciously or not) when you're using your smartphone...

The fact is as you can't even write correctly, i guess you can't even use your fingers and eyes properly to enjoy a latency free device.
[Galaxy Note II Android Development] bushako:
I do notice this input lag more often on a stock based roms then aosp/cm10.1. Ive tried the "show touches" options on both the roms and noticed that the input lag on the aosp rom is significantly less than that present on the stock. As for, whether this is a feature or intended to improve visual quality, i dont know but i do hope its not. This is an issue that does bother me alot and the only reason why i keep going back to custom stock roms is due to the poor batterylife present on the cm10.1 roms, other than that i was quite happy with aosp/cm10.1.

Hopefully, more people will get aware of this issue, enough for Sammy/XDA Developers to try and tackle it. Good Thread:good:
[Galaxy Note II Android Development] mariosraptor:
Re: [Dev request] Fix touchscreen input lag

I like your investigation but I think it is hardware issue. As MS engineer says "in the next decade".
[Galaxy Note II Android Development] UltimateByte:
Thanks, nice to show how this is bothering you too :highfive:

And yes, even if we don't find a solution, at least poeple will be more aware of this global issue and the lack of efforts from Samsung about it. I'm sad to say that, but Apple is the only one that seems to take care of that, with a really lower input lag. I tried one more iphone 5 this morning, it must be around 50ms input lag, still not perfect, but much better already.

Thank you too.

As the SGS2 and even the SGS1 has lower input lag, this just makes no sense, it's supposed to get down and it's getting up ? :confused:

There is almost always a hardware part and a software part in input lag. I know the touchscreen implies at least 80ms, but in those, how much are software due to buffers, or error corrections, or whatever it is ? I hope we can at least get rid of a big part of the software one, and i hope it's the biggest one... :angel: If the hardware is 80% of it, then i'll just wait for any other nice android phone without this bad spec, and change the Note 2, but at least, poeple will know about it, and stop thinking that this latency is a smoothing and is normal... This is latency, and it really sucks !

Smoothing would be a bad thing with touchscreens anyway (and i think it's a bad thing on any input device as well) as you should feel what you're doing, not something different, or your senses are just going mad, and it's the same for a delay. But yeah, just in case if anyone has a doubt : this is not a gentle smoothing, this is just a nasty input lag.

Edited the main topic with a comparison to music production's world.
[Galaxy Note II Android Development] mariosraptor:
Re: [Dev request] Fix touchscreen input lag

http://www.overclock.net/t/1351079/guru3d-galaxy-s-iv-confirms-exynos-5-octa-cpu/140

http://gamesfromwithin.com/lag-the-bane-of-touch-screens

Found this seems good.

This is only one page.

But as I said hardwre issue more than software. Yes optimizing software to 110% seems reasonable but because not to many seems bothered by this, then no jardware manufacturer will try to make hardware to have lower input latency.

If we press them and this becomes a common issue among android (and other touch devices users) then some light might show up at the end of the tunnel.

Anyway, good luck and I hope that some more knowledgeable then me responses.

Cheers
[Galaxy Note II Android Development] Kiwito22:
Yes, we do understand that all touchscreens have huge input lag... the thing is, the note ii's input lag is way higher than older gen devices.

For example Subway surfers is way more responsive on my Optimus 3D than on the Note II. If you have an older phone to compare, you can easylly see the difference. I dont care much about input lag, smoothing or whatever in UI, browsers and stuff like that. but in games, its very noticible and very annoying. It almost makes me want to throw my phone against a wall.

I prefer tearing, thats why i have vsync off and minimal frame prerendering.... on my PC almost all the time.
[Galaxy Note II Android Development] UltimateByte:
Looks nice, thanks, i'll read it entierely when i got more time, for now i really need to sleep and have a big day waiting for me tomorrow.

From what i've already read, i just can say that my hope is a tweak in the touchscreen driver... There must have a way to override stupid values.

OMG, i thought it was a quote from me, i've written the exact same idea somewhere on the web ! Totally agree, about everything.
[Galaxy Note II Android Development] vRbas_r:
Good Thread:good:

I like your investigation and i dont think the hardware is the issue here at all look at the older sgs2 and iphone both of them have lower input lag
[Galaxy Note II Android Development] doclucas:
Great thread!!

This is the thing I hate the most about my Android phones (I had all the flagships - GS1, GS2, GN1, GS3 and now GN2).

My iPhone 4s and iPad 3 have significantly lower input lag (and much better/smoother scrolling, but that's another issue), but they also do have completely different hardware than the Galaxy line.

The thing is, that on CM Roms I also get lower input lags, so this must be fixable or at least significantly improved via software...
[Galaxy Note II Android Development] xartic12:
Re: [Dev request] Fix touchscreen input lag

Since these Gnote II uses a Wacom touchscreen, could there be a possibility that the screen is trying to detect the spen momentarily?
[Galaxy Note II Android Development] matejdro:
AFAIK Wacom is completely off if you have pen power save enabled and pen is stored inside Note2.
[Galaxy Note II Android Development] oop1:
A goooooood notice .....
[Galaxy Note II Android Development] D3_:
Re: [Dev request] Fix touchscreen input lag

But the way the s-pen is detected for touches etc is completely different to the way you touching the screen with your finger is. That's why air view works, and you can hold your s-pen above the screen, use something to push the nib in, and the phone will register q touch without even touching the screen, so I highly doubt that's the cause of any input lag.
[Galaxy Note II Android Development] lolmensch:
Did anybody try and compare whether there is any difference regarding the input lag on the touch screen with your finger and the wacom digitizer with the stylus?

The only solution I could think of is reverse engineering of the touchscreen driver and that is such an ungrateful huge work for such a small interested userbase that I'd say it is not going to happen. Unless there is a developer with immense skill and way too much(!) time around :D
[Galaxy Note II Android Development] UltimateByte:
I've just watched the S4 presentation > in the intro video > Exact same input lag. Then i wateched "hands on SGS4" videos > same input lag.

What a waste, I hate them.

=> I read it, it's interesting but gaming lag of a console isn't the same.

Anyway, that's not normal that input lag increased... Maybe touchscreens got more expensive, but physical digital controllers got cheaper.
[Galaxy Note II Android Development] sandulea:
I think software is where the problem lies. I tried an iphone 4 or 4s, couldn't tell which, and it was way more responsive, and the technology is the same as in Android phones. It can't be that big a hardware issue because it would be too easy to solve, just replacing a component, and in a race to sell millions of phones surely Apple couldn't be the only company that afforts an extra dollar or so per unit to purchase a more expensive, but better component. Plus we've all seen articles and teardowns showing that Apple uses plenty of regular components that are found in other phones as well, so there's definitely no magic there. Also, the trackpads in laptops seem to be based on capacitive technology as well, yet the input lag is a lot smaller than it is on the Note 2.

My guess is that there is noise filtering, to eliminate false touches, as well as smoothing and approximation, and the programmers are also generous with the input lag to ensure a smooth approximation. The smoothing, more specifically, is what must be the most lag-inducing feature. It's most obvious when we draw something quickly on the Note 2 with a finger (and even with the pen): small detail gets lost, but all the curves are smooth, and that's because the sampling rate for the finger position is low, and it interpolates points between the sampled positions to ensure a smooth animation. Since it can't approximate all the points between two sampled positions until you actually reach the second position, and it must also run the animation through all these approximated points at the same speed that you moved your finger, that means that a list doesn't start scrolling until the screen has captured at least 2 samples of finger movement, so the animation will always be at least 1 sample behind your finger's actual movement. How many samples is unknown, but the sampling rate can be found out, and together with an accurate measurement of the lag it would be possible to find out how many touch samples it needs before it starts actually performing an animation.

So the obvious solution would be to increase the touch sampling rate, so that animations start faster, and tone down the smoothing because it would be less useful and to compensate for the computing power used by the increased sampling rate (it's not enough to prevent the power usage from rising, that's my guess, and maybe that's why iphones don't last as much as droids with comparable specs in the battery department).

For what it's worth, I'm an amateur sound engineer, bass player with an ear and a passion for drums, so I really know how you feel about input lag OP!
[Galaxy Note II Android Development] UltimateByte:
Yay, another musicman ! Cheers ;)

Here is what i can say for sure : I activated "show touches" in developper option, and 99% of the time, the actual detected position is in sync with the object => Means that devs know how to minimize latency.

I believe the touchscreen has a good refresh rate, as if you make a fast and complex movement, it will get it and reproduce it perfectly. Somebody said 240hz, I can believe that.

The problem could be in the android touchscreen's management (but in this case i'd be worried that no dev already made some tweaks), or : into the driver of the controller : Something that would add delay to remove noise and false touches as you said.

No componoent, even a bad 50Khz controller could add 80ms of input lag, so i do believe that the issue is caused by touchscreen's management.

Now is there a way to get those drivers ? Is there anybody to try some reverse engineering ? I don't know, I hope so.

Next week, i'll try to get a GoPro that films at 120fps, and measure the exact delay between moving a finger and the actual action on the screen by measuring frames separating those two actions.

I expect about 15-20 frames over a pure Samsung ROM, maybe a bit less on Revolution HD or AOSP ROMs.
[Galaxy Note II Android Development] dirn1111:
You might just be wrong. After countless flashing, i have found that certain rom builds have massive lags with it and some of them include recent builds as well. On my current rom i barely notice the latency you are talking about. And lag. For android will never be so optimized because it is not running on native.. so we can say it is essentially the software problem which can only be dealt with hardware improvement.

I am no expert so this is just my opinion and observation
[Galaxy Note II Android Development] UltimateByte:
The lags, choppy ROMs have nothing in common with what we're talking about, you understood that right ?

Which ROM ? "barely notice" is subjective... I guess Revolution HD has better input lag than stock, but it's still really too much.

That makes no sense to me : If it's a sofware issue, how a hardware improvement could change anything ?
[Galaxy Note II Android Development] matejdro:
I think he is saying software will never be optimized and hardware needs to be beefed up to speed up software.

However, I don't think power of hardware has anything to do with it. Galaxy S has much smaller input lag than Note 2 (or maybe it just looks that due to smaller screen?) and this device is from 2010, powered by 1Ghz single core CPU - significantly less powerful than Note 2.

It may be touch screen hardware or software.

Also another way to test input lag is on the jelly bean easter egg - it feels like those beans on leash instead on the finger.
[Galaxy Note II Android Development] UltimateByte:
Yes, i guess you're right about him, and i totally agree with you.

I've been wondering the same thing about the screen size and feeling of input lag : for sure, the bigger the screen is,the bigger your moves are, and the most it will be annoying. But if you objectively look for the delay between your move and the actual start of the move on the screen (not the distance) you will easilly see that the Note 2 takes longer than the SGS1 released 4 years ago...

So yeah, the causes could be : touchscreen's driver, touchscreen's physical controller, touchscreen itself. I'm pretty sure that no digital hardware (except maybe an analog part of it, like capacitors on the touchscreen's detection) can take 80ms to work, so i guess it's just horrible timings set by the driver/firmware of the controller.
[Galaxy Note II Android Development] Kiwito22:
It does take longer. Just play a game on the NOTE II and the same game on another device. You will notice the difference instantly
[Galaxy Note II Android Development] UltimateByte:
Not any device... Many recent devices have the same problem of too high input lag... But it's for sure one of the worst with the S3 and S4.
[Galaxy Note II Android Development] modstar:
Its not the new android? 4.0 and upwards? i remember i had a desire hd and i was running cm 7.2 (Android 2.3) and then i tried the other roms with higher android version and there it came the input lag..
[Galaxy Note II Android Development] dannejanne:
Pretty sure it's in the software. I noticed "input lag" on stock rom with my Note 2. But MIUI that I run now is more responsive. For example the clock app in MIUI, the alarm screen in particular responds instantly to my touch. I mean instantly. While other parts of the clock app ain't as responsive.
[Galaxy Note II Android Development] matejdro:
On HD2, Jelly bean is much more laggy than GB or ICS. But on Galaxy S everything is fine.
[Galaxy Note II Android Development] kuma0007:
Someone said it..

Thanks for putting it up. I love my Note 2 but ya it is noticeable. Was recently laughing at a friends iphone 5 which felt like a toy but man! the responsiveness. Touch really comes naturally on it. I actually compared the notification drop down on both and note felt a little hesitant. Hope someone finds a cure. I can confirm even stock CM ROM doesn't improve it by that much. test subway surfer game or temple run.
[Galaxy Note II Android Development] :
this has always bothered me since my first android phone i hope we can get a fix :good:
[Galaxy Note II Android Development] UltimateByte:
I compared again the SGS2 and the Note 2... Both running 4.1. (omega ROM for the SGS2 and Revolutin HD12 for the Note 2)

=> I'll make a video with a 120fps gopro as soon as i can get it from a friend, the difference in gmaps is just obvious, even scrolling apps, or top bar... The SGS2 is slightly more responsive...

So it's not a mater of OS. Also, i've already compared 3 times a SGS1 running CM10.1 with the Note 2 (@stock, @HD12, @Omega) => the SGS1 was slightly better as well.
[Galaxy Note II Android Development] UltimateByte:
http://www.youtube.com/watch?v=LY7s2zxZ23E

We can see the same huge input lag here than on any other ROM while scrolling. But what do you mean with this clock being awesomely more responsive than the rest ? It would have a magic feature that removes input lag... ? I doubt it.
[Galaxy Note II Android Development] Gnarfsan:
I agree. I am currently on MIUI 4 and it seems to track my finger much quicker than anything else that I have tried. There is still lag though.
[Galaxy Note II Android Development] UltimateByte:
I've read that several times, do you have a link of this ROM ? I've been looking for that a little bit but didn't find the good one.

A video, even a 30fps video of the ROM to see its input lag, would be very appreciated :)
[Galaxy Note II Android Development] Gnarfsan:
Re: [Dev request] Fix touchscreen input lag

Sure, here it is ;)

http://xdaforums.com/showthread.php?t=2192641
[Galaxy Note II Android Development] UltimateByte:
Nice man, i'll try that when i'm done with my work, i hope in a few days, or at the beginning of the next week.
[Galaxy Note II Android Development] Gnarfsan:
I hope you get the same experience ;)

Unfortunately the Note II is my video camera, so I can't film it :-\

Oh, and I should mention that I use the latest Perseus kernel.
[Galaxy Note II Android Development] cd993:
Hi, regarding battery life would you say MIUI is on par with sammy based roms?

Thanks
[Galaxy Note II Android Development] UltimateByte:
Too bad you don't have another camera !

Maybe i could try the Perseus Kernel alone first, but i don't know if it would work with PAC Rom. If anyone knows, it would be very appreciated... ^^

Otherwise, i'll just try the MUI without and with this kernel :)
[Galaxy Note II Android Development] Gnarfsan:
Re: [Dev request] Fix touchscreen input lag

I get much better battery life with other Samsung roms, but it still easily gets me through the day. So to me it's no big deal. Other users report ok battery life so you might have a different experience.
[Galaxy Note II Android Development] Gnarfsan:
It might do the trick. If not, try overclocking and forcing GPU rendering. I have a feeling that this is related to rendering.
[Galaxy Note II Android Development] UltimateByte:
Well, after a boring headphone bug using PAC ROM, i just tried MIUI...

With or without Perseus kernel, no difference, still a huge input lag, maybe a little bit less than without it => but i would even say that it's worse than PAC ROM, even with Perserus Kernel... So i tried GPU rendering... Maybe a very very little improvement (too small to tell if it's a placebo effect or not) but still bad anyway. But CPU overclocking is pointless for an input lag issues (almost when it already never reaches 100%).

So sad.
[Galaxy Note II Android Development] matejdro:
It is NOT CPU or GPU or anything having to do with raw power. Older devices with much slower (non-overclocked and CPU rendered) hardware had better input lag than N2.
[Galaxy Note II Android Development] pimjai:
Re: [Dev request] Fix touchscreen input lag

This is true, my mother uses my old galaxy S with CM10.1 and the input lag is clearly lower than on my note 2. I have to add that my note 2 has gotten better with Perseus kernel and android revolution HD, but still not as good as the galaxy S.
[Galaxy Note II Android Development] Gnarfsan:
Re: [Dev request] Fix touchscreen input lag

Well I get a lot less input lag now, so it must be a software issue. So overclocking will likely reduce input lag.
[Galaxy Note II Android Development] UltimateByte:
So we're 2 here, to confirm that the SGS1 has a slightly better input lag than the Note 2...

See this :

As the CPU clock is already about 1.000.000.000x superior to the touchscreen's refresh, how do you want overclocking to improve input lag ? It could be possible if the CPU was used at 25% (one core) just by touching the screen, but as far as i know, it's not the case.
[Galaxy Note II Android Development] matejdro:
Sorry, but I must call placebo on that. My guess is that input lag originates from either touchscreen hardware, low level drivers or android design which can't be really fixed by overclocking. And if someone would fix it, he would not silently slip it into the ROM, he would advertise it probably.
[Galaxy Note II Android Development] pimjai:
Re: [Dev request] Fix touchscreen input lag

I agree with this, it is probably an issue that is very hard to fix, and I don't think overclocking helps, at least I don't notice any difference.

However, I do think there are at least some things ROM and kernel makers can do. not that I know a lot about it, but it would declare the difference between for example omega and android revolution HD. When I switched to ARHD, it was definitely better.

Also when you scroll to the bottom of the http://xdaforums.com/showpost.php?p=37631642&postcount=4changelog from alliance ROM it says this: "Build prop tweaks for touch and smoothness"

I wonder what it is they did, but I don't have time to flash ROMs now.
[Galaxy Note II Android Development] UltimateByte:
Well, I just tried 3 kernels on the Omega V15 ROM

Stock MB6 (default)

N.E.A.K Note 2

Perseus alpha 34.2

The only thing i'm sure about is that Perseus doesn't provide a better input lag at all, i'd even say it's a bit worse (at least 1 or 2 more frames).

To be sure of myself i would need to try two phones at the same time with two different kernels, but for sure, Perseus isn't any better.

So NEAK and Stock are the bests in terms of responsiveness (about the same).

Not to mention that i've tried Perseus for 20 mins, and didn't like the "right after boot choppiness" and the overall smoothness that seemed bad to me, maybe it has nice functionnalities, but it's not a example in terms of responsiveness.