yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] smashpunks:
just adding to the love of the g2x... Where my trollls at lol
[T-Mobile LG G2x] cjmcmillion:
This phone is truely amazing... No if only tmobile would release the throttle on there so called unlimited data plans i would be even more happy
[T-Mobile LG G2x] Sarchie1982:
Couldn't be happier! Love this speed demon especially on eaglesblood 2.3.5. Vroooom!!
[HD2 Android NAND Development] arkatis:
Wow! Good stuff!
[HD2 Android NAND Development] patensas:
Wow nice find, perhaps you should talk to Tytung & Rafpigna about this as they are the most active kernel chefs @ HD2 :rolleyes:
[HD2 Android NAND Development] speedyracer5:
Thanks, I have now contacted them and am awaiting a reply :D
[HD2 Android NAND Development] tytung:
Kernel source code related to msm_i2c is done by the great dev Cotulla. (and maybe other devs)

I don't participate in his work.

And you're linking to a non-working kernel git in your first post.
[HD2 Android NAND Development] s_superman:
but tytung please try to look into this ?

because this issue is really annoying and I dont think cotulla would mind if you do some modifications to his great work ?
[HD2 Android NAND Development] white-energy:
Nice! now the only thing left to do is to fix it =))
[HD2 Android NAND Development] white-energy:
Farrrk now what....??

-Wrong thread... sorry.
[HD2 Android NAND Development] NoXXX:
Well, I'm waiting for screen delay issue to be fixed since I installed MAGLDR on my HD2. So it will be just great.

What if just remove this loop and sleeps and recompile kernel? Madness? THIS! IS! SPARTA! :)
[HD2 Android NAND Development] sagarjawaress:
Great found kid!! We have great hope on this!

Hope it gets fixed soon...
[HD2 Android NAND Development] beston94:
I didn't understand anything you just said but .... This is great! And your only 15? That's amazing.

Hope we can fix this problem.
[HD2 Android NAND Development] Spl4tt:
nice work. especially if you are 15.

i would be so happy without the wakeup lag.. >.<
[HD2 Android NAND Development] john_duff:
Hah ! That reminds me of an old trick to enable hackintoshes to use USB2...

The PC bios never gave back the bus ownership. So correctly programmed software could not use it.

The fix was to take bus ownership without asking "please".

Here it might be the same idea: just ignore (or need to call msm_i2c_recover_bus_busy earlier)

Once back home, if my kids give me spare time, I'll try to setup a compilation environment and give it a try.
[HD2 Android NAND Development] speedyracer5:
Good idea, im sure that calling it earler and avoiding the loop will reduce the delay, after that is done we need to find a 'clean' hack as calling msm_i2c_recover_bus_busy would probably still add a delay, albeit not as much as if we just left it :) Good luck in your testing...
[HD2 Android NAND Development] white-energy:
You guys speak like you've found the solution lol =D
[HD2 Android NAND Development] john_duff:
Well not tonight... bad news came, I have to fix the dishwasher first.

I'll keep you informed.
[HD2 Android NAND Development] beston94:
Hey can the dishwasher remove the screen delay? NO!

only joking ! :D Im just so excited for this !
[HD2 Android NAND Development] speedyracer5:
ahah finding a problem isnt that hard but finding the solution is harder:) we will probably need some help from experienced kernel coders to help fix it properly:(
[HD2 Android NAND Development] Mafioso:
Why are you using charansingh's HD2 Kernel GitHub to see the code? Just guessing, it may have .37 kernel code on which work is still going on as its still buggy...

Is there a similar error tytung or Rafpigna or ACA's kernel's git also?
[HD2 Android NAND Development] needabottle:
Well, I can't argue with that.... I can't understand it either .. :-)

Sounds like you did A tremendous piece of detective work. Nice one.
[HD2 Android NAND Development] speedyracer5:
Hi, cheers for the QR code, I am currently running Typhoon Cyanogenmod which has tytungs r10 kernel and it has the same errors, I will change all the code on the front page to tytungs code later :)
[HD2 Android NAND Development] nkos719:
damn i need the fix to take place soon!
[HD2 Android NAND Development] bell2010:
I hope somebody can fix this bug,make sense rom beautiful。
[HD2 Android NAND Development] nemuro:
Am I the only one who thinks this thread is funny? :)
[HD2 Android NAND Development] pReXx:
Nope. (:

Don't think it works..

Cotulla would noticed these errors i think..
[HD2 Android NAND Development] beston94:
Anyone can make mistakes..that's what makes us human right?

Sent from my HTC Desire HD premium xda application.
[HD2 Android NAND Development] semihbalcioglu:
Please fix this only annoying issue for my hd2. wake up lag really pisses me off... I don't know anything about kernel programming so sorry for this suggestion if its to stupid but can't we just change the while statement from this

" while (retries != 200) "

to

" while (retries != 1) "

this?
[HD2 Android NAND Development] john_duff:
In tytung yes it seems so.
[HD2 Android NAND Development] Spl4tt:
what if cotulla had a sharp display HD2, and didnt even notice the error, cause he dosent have it?^^

then it would definitely make sense that he didnt look into, meaning that this what OP found here could be true

COULD

so lets hope.
[HD2 Android NAND Development] white-energy:
Maybe =) but we still need a response from Cotulla -))))
[HD2 Android NAND Development] clyder:
I have a sharp display and I also have this error. Just saw it in dmesg.

But my wakeup lag is very short(less then one second usualy). In HyperDroid and UltimateDroid it was almost nonexistent. In MIUI is a bit more noticible.
[HD2 Android NAND Development] Cissmayazz:
I'm compiling as we speak. Not sure if doing it right though. Read some manuals and removed the check which makes our devices sleep.

If this works, i'll update this post
[HD2 Android NAND Development] invicible:
i using htc leo 512 with 3 sec wake up lag with any android nand/sd rom ..since from last two week my phone lcd screen light never light on again ..so i went to repair shop they told me need to change the lcd..(costly *.*)

after few days i take it back my phone from repair shop ..but i found that top of the screen with "t mobile" logo..i keep silent front of the shopkeeper and paid.... quickly back home and test android nand with my phone ..

3 sec lag have gone now !!! LOL

how u all check your screen is sharp or any brand?? may be i can check for you guys!!??
[HD2 Android NAND Development] clio94:
check also nand memory size.Maybe you have now t-mobile hd2 with 1gb rom.
[HD2 Android NAND Development] arkatis:
LOL! They changed your HTC HD2 LEO (512) with a Tmobile one (1024)! You are one lucky guy! :D
[HD2 Android NAND Development] invicible:
checked...in titanium backup details internal : 268 mb (31.5 mb free)

sd card: 7.29gb(593 mb free)

sd card (a2sd):520mb (166mb free)

i dont think i have 1 gb rom........
[HD2 Android NAND Development] arkatis:
Keep us posted dude! I am anxious!!!!!!!!
[HD2 Android NAND Development] invicible:
yeah !! thanks!!
[HD2 Android NAND Development] arkatis:
So they actually changed the Front case with the LCD display (1 set)

How much did you pay? Also check the Total in titanioum! If it's 900Mb and above then you have the Tmous version!
[HD2 Android NAND Development] beston94:
maybe they just put a sticker on top of his screen xD
[HD2 Android NAND Development] invicible:
malaysia here rm380

usd may be 126 usd..

but i know i can buy from spare part shop only 5x or 60 usd....

but i duno to change it ...
[HD2 Android NAND Development] invicible:
if really just put a sticker on top ..but why my 3sec lag have gone??

and my gf using hd2 too..so i can compare that...
[HD2 Android NAND Development] Cissmayazz:
I'm having a problem flashing the new zImage, anyone that can help?
[HD2 Android NAND Development] beston94:
you could be lying..We never know a video proof would be amazing :D
[HD2 Android NAND Development] M..N:
What's the problem?
[HD2 Android NAND Development] Cissmayazz:
Nvm, was able to create a new boot.img. Testing it atm. Not noticing much of a difference. But, hey, probably did it wrong anyway :s
[HD2 Android NAND Development] pReXx:
Surpise, surprise :P
[HD2 Android NAND Development] M..N:
What are logs saying any difference in code before?
[HD2 Android NAND Development] tytung:
dmesg | grep panel

You will see

panel type is 1 :board id is 4 : AUO

or

panel type is 10 :board id is ? : SHARP
[HD2 Android NAND Development] speedyracer5:
Im going to make some modification to the code and try and compile a new boot.img too, I will also report back :)

Edit: Going to partition and install ubuntu too, this may take longer than expected :P
[HD2 Android NAND Development] tytung:
I got some free time, so I looked into this issue.

@speedyracer5

Good try. But unfortunately, you don't hit the target.

Firstly, the time unit of usleep_range() is microsecond (0.000001s), not millisecond (0.001s), so your delay time calculation is totally wrong.

Secondly, while (retries != 200) loop in msm_i2c_poll_notbusy() is used by all Android kernels (CM and AOSP; AOSP even uses msleep(10) which means 0.01s), so this function doesn't have any problem.

Finally, thanks for your time trying to find a bug albeit it is unsuccessful.
[HD2 Android NAND Development] ORiZorrie:
Thanks tytung for investigating. Fair attempt though speedyracer5.

But is it really unknown what is causing this delay? I assume it's a driver problem (can't be HW issue since it's working for WiMo right?) ... so if it's in the driver... is there anything that could help us narrow down the problem?

(sorry if my questions are stupid)
[HD2 Android NAND Development] speedyracer5:
Thanks for your time in looking into the post and the problem, and for clarifying some of the issues :(

I have looked at all the logs and cannot see any other problems other than the 4 at the top of my first post, although my screen delay is <= 1 second, maybe someone with a longer screen delay could look at their logs?
[HD2 Android NAND Development] rizky_p:
Didnt know HD2 have a wakeup delay.
[HD2 Android NAND Development] speedyracer5:
It may not affect your device as much as it does others, this can be due to different hardware/software configurations:) Some people report they have delays as long as 2-3 seconds!
[HD2 Android NAND Development] pReXx:
I have a ~2s wakeup delay.

if you tell me where i can find the log file, i could upload it.

(EU, PAT's JW MIUI Sense like 1.8.5)
[HD2 Android NAND Development] arkatis:
I made a quick demo for you to see the different screens that HD2 has.

On the 1st screen, my screen has that diagonal line and i have 1 sec lag.

On the 2nd phone, that was my previous HD2 that i exchange for an HD7. Look at the screen... you will see the lines and dots in the middle. I had 2-3 sec lag with this screen.

And finally, the 3rd phone is a mates Tmobile phone which the screen is Clear. You can not see anything in the screen. Therefore no lag and this is not a kernel problem! It's Hardware problem!

And now, 1 question to HTC! Why would you create a phone with 3 different lcd screens????????:confused:

This is the Demo i made in a hurry!

Look at your HD2 screen and let us know what Type you have.
[HD2 Android NAND Development] nkos719:
i have the second one.i have a 2-3 secs delay.
[HD2 Android NAND Development] beston94:
ye mee too i have the second one :/

But what you are saying is if i change my screen to a tmobile screen then it will work without the delay?

The screen wouldnt fit though would it? its a european..
[HD2 Android NAND Development] Jolqq:
i have the second too and a 0-1 sec delay

where should i put this code?
[HD2 Android NAND Development] pReXx:
My friend has a T-Mobile HD2, too and i noticed yesterday, that there is no (0-0.5s) wakeuplag...

Damn it! :D

Ok,... need a hardwaredefect and hope that they replace my screen with one from tmobile :D:D
[HD2 Android NAND Development] NoXXX:
I checked my logcat and every time I turn screen on or off I have errors like:

E/lights ( 279): gpc: manual set BL value=4 (Mode = 1)
E/lights ( 279): gpc: value=5 (Mode = 1)
E/lights ( 279): gpc: value=6 (Mode = 1)
E/lights ( 279): gpc: value=7 (Mode = 1)
E/lights ( 279): gpc: value=8(Mode = 1)

Value increases from 0 to 70 when I turn screen on. Looks like something tries to turn backlight smoothly, but fails. Maybe we should look into that?

Sorry if this is not the problem.
[HD2 Android NAND Development] semihbalcioglu:
Maybe a part of it but i don't think it its ONLY an hardware issue.

My HD2 is the second one and now has a 0,8 sec lag. But in my previous android rom i was having 1,5 sec lag. And in winmo 6.5 i have no lag!

My brother also has the second HD2 with android rom and has NO LAG in any android rom and winmo 6.5.
[HD2 Android NAND Development] codiak:
I also have the second screen and I have just a small lag (under 1s). Its ok to me :)

With other ROMS I got longer lags so I dont think it only hardware related.
[HD2 Android NAND Development] speedyracer5:
could you possibly get a logcat for all the devices? Are they all running the same software?

Im sure there are different sections of code that the different displays run through in the kernel as you cant really control 3 different screens with the same piece of code?

Also if the startup lag is non existant on winmo 6.5 then it cannot be a hardware issue...
[HD2 Android NAND Development] Spl4tt:
i have teh second screen with <1sec delay. its not thaaaaat bad.. but when i look at my friends HD2 (wich he bought like 2 or 3 months after me) and how i see he has absolutely no lag.. envy >.>
[HD2 Android NAND Development] john_duff:
man you're too fast... I did not even have the time to setup the compiling environment...

the dishwasher is fixed though. and the kids are clean.
[HD2 Android NAND Development] speedyracer5:
Could you possibly get logs for the three phones when the screen is turned on?

If there is no lag in Windows Mobile this cannot be a hardware issue.

The issue would be different modules in the kernel for different screen types. You cannot control 3 different screens from one piece of code at kernel level?

So either the start up routines for the different screens are optimised differently, or some are producing errors, I am 99% sure this is a software issue....

I also have these lines in the logcat, anyone know what they mean?
[HD2 Android NAND Development] leeyunfook:
i would like to share my experience with my hd2 lcd screen. I bought my hd2 almost 2 years ago, considered early batch. I also experience screen on lag on my hd2 android. Few months back, my screen suddenly became unresponsive and sent for repair. They changed new lcd screen due to faulty and luckly still under 2 years warranty. Ever since, no more wake up lag anymore! Consider myself lucky.
[HD2 Android NAND Development] NoXXX:
I think it should be "fade in" and "fade out", which doesn't work for any reason. Because when I turn the screen off, I see these line in logcat and only after that the screen turns off. The same thing when I turn on the screen. These lines and only after that screen turns on.

P.S.: Because I use latest Typhoon ROM with tytung's kernel, maybe tytung knows what is these lines? :)
[HD2 Android NAND Development] ORiZorrie:
Indeed. If it would be a hardware issue the issue would be present in all ROM's. Since there is a difference between WiMo & Android that simply can't be the case right?

And there is even a huge difference between some Android ROM's. For example I had at least a 2 second lag when using an Imilka ROM in the past, now I only have 0.8s lag with Dorimanx & HyperDroid. Which is significantly better and actually workable. But I would LOVE a snappy phone =D
[HD2 Android NAND Development] arkatis:
I would like to have a snappy phone too but... This Thread is going No where! :o
[HD2 Android NAND Development] hitvan:
what screen delay are you guys talking about, i dont have any delay im on tyween's latest rom. and i have never had those delays.
[HD2 Android NAND Development] arkatis:
It's an Old pain story mate! :cool:
[HD2 Android NAND Development] jan-willem3:
It is just related to the lights libary you use. This one as you can see is developed by iamgpc. That is why it says :gpc.

As you can see it says manual set BL value xxx.

The reason why it tries to fade is because you are using Auto blacklight.
[HD2 Android NAND Development] pyrorob:
so, how's this to add to the confusion... checking my logs, i too have the error, but i have absolutely no screen lag.. i have a brand new hd2 sent to me by htc about 2 months ago.
[HD2 Android NAND Development] Rick_1995:
Just my tid bit in here,

I2C stands for Intercurcuit communication, From what i can see the logs, i interpret that when there is the "screen wake" interrupt, the kernel tries to reach the LCD but that bus is busy hence waits some time before trying again( The Lag ). Either we can try removing the check and flash the kernel, if it works then the code which decides if the bus is busy or not is faulty else we will have too look deeper in regarding which device is using that bus.

Again, i could be wrong, but that seems to be the most sensual answer to me.
[HD2 Android NAND Development] ghertgh:
Please tell me you didn't put the kids in the dishwasher :/
[HD2 Android NAND Development] invicible:
i see my phone is "sharp_panel".

but my's gf 1 is show "panel type 1 :board 260 :auo . ."

so means sharp din hav 3 sec lag???
[HD2 Android NAND Development] rizky_p:
I dont see any delay. If there is a delay it is really similar with my HTC Sensation.

FYI. If i see it correctly mine is No.3 (TMoUS)
[HD2 Android NAND Development] agormog:
Logcat turning the screen on with AUO panel & jw miui:

D/KeyguardViewMediator(20928): wakeWhenReadyLocked(5)
I/power (20928): *** set_screen_state 1
D/SurfaceFlinger(20928): Screen about to return, flinger = 0x13f558
E/lights (20928): gpc: manual set BL value=2 (Mode=1)
E/lights (20928): gpc: value=4 (Mode=1)
E/lights (20928): gpc: value=7 (Mode=1)
I/screenstate_scaling(25121): *** awake ***: switching CPU frequency governor to -> smartass
E/lights (20928): gpc: value=9 (Mode=1)
E/lights (20928): gpc: value=11 (Mode=1)
E/lights (20928): gpc: value=13 (Mode=1)
E/lights (20928): gpc: value=16 (Mode=1)
E/lights (20928): gpc: value=18 (Mode=1)
E/lights (20928): gpc: value=21 (Mode=1)
E/lights (20928): gpc: value=23 (Mode=1)
E/lights (20928): gpc: value=25 (Mode=1)
E/lights (20928): gpc: value=28 (Mode=1)
E/lights (20928): gpc: value=30 (Mode=1)
E/lights (20928): gpc: value=32 (Mode=1)
E/lights (20928): gpc: value=35 (Mode=1)
D/dalvikvm(21024): GC_CONCURRENT freed 447K, 41% free 4756K/7943K, external 0K/0K, paused 3ms+23ms
W/ResourceType(23915): No package identifier when getting value for resource number 0x00000000
D/dalvikvm(23915): GC_CONCURRENT freed 440K, 49% free 3187K/6215K, external 0K/0K, paused 3ms+9ms
D/dalvikvm(23987): GC_EXPLICIT freed 4K, 46% free 3648K/6727K, external 0K/0K, paused 44ms

Did not filter anything
[HD2 Android NAND Development] Rick_1995:
dmesg are required, not logcat.

adb shell dmesg > c:\dmesg.log
[HD2 Android NAND Development] NoXXX:
If I disable autobacklight the messages still exist
[HD2 Android NAND Development] agormog:
dmesg:

<6>[70128.862823] request_suspend_state: wakeup (3->0) at 70128338592467 (2011-08-14 19:19:26.084472654 UTC)
<6>[70128.863922] [R] late_resume start
<6>[70128.864044] lcdc_resume: resuming
<4>[70128.864105] auo_panel_init
<6>[70128.864318] msmfb: ready, waiting for full update
<6>[70128.880218] msmfb: full update starting
<6>[70128.898986] msmfb: full update completed
<6>[70128.899169] msmfb: turning on panel
<6>[70128.899261] lcdc_unblank: ()
<6>[70128.899322] auo_panel_unblank
<3>[70129.594421] msm_i2c msm_i2c.0: error, status 43c8 (5C)
<3>[70129.594573] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
<3>[70129.594696] msm_i2c msm_i2c.0: error, status 43c8 (34)
<3>[70129.594818] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
<6>[70129.595855] [R] late_resume end
<6>[70133.076660] request_suspend_state: sleep (0->3) at 70132552429161 (2011-08-14 19:19:30.298309347 UTC)
<6>[70133.076873] [R] early_suspend start
<6>[70133.094360] __spi_bma150_set_mode: BMA get into SLEEP mode!
<6>[70133.097839] lcdc_blank: ()
<4>[70133.097930] auo_panel_blank
<6>[70133.134796] msmfb: drawing while asleep
<6>[70133.247955] msmfb: drawing while asleep
<3>[70133.334472] lsensor: nothing to disable
<6>[70133.348083] lcdc_suspend: suspending
<6>[70133.348236] [R] early_suspend: sync
<6>[70133.734863] active wake lock kgsl
<6>[70133.734954] active wake lock vbus_present
<6>[70133.735015] wake lock SMD_DATA1, expired
<6>[70133.735076] wake lock SMD_DS, expired
<6>[70133.735168] [R] early_suspend end
[HD2 Android NAND Development] leaskovski:
How did you run the command? Im using a terminal emulator to run it and it gives me loads of stuff back but not what has been mentioned.

Cheers
[HD2 Android NAND Development] ph03n!x:
Hope all of you having screen delay in AUO panel are following this:

http://xdaforums.com/showthread.php?t=1222427
[HD2 Android NAND Development] HierOS:
hm... i'm have "panel type is 10 :board id is 4 : SHARP" on my tmous
[HD2 Android NAND Development] kundanjuit:
This thread should be closed now as this could be misleading as the fix is already out.
[HD2 Android NAND Development] Rick_1995:
I really hope you are out of your mind as of now.

The fix only takes care of switching the screen on, the msm i2c error is still evident. Yes, I'm using that fix on an AUO panel myself. That leads to inactive touchscreen for that initial few seconds.

Mislead of all the things ?
[HD2 Android NAND Development] jdivic:
I would like to explain that i2c errors shown here... they are result of touch screen wakeup procedure... in the wakeup process there is procedure that tries to identify type of touch screen (there are 3 known ts in HD2 kernel). Code is probing at three different addresses and when communication go to an error that means it is not that kind of ts, and tries with another... so... every time ts is started there will be two errors and one success (identifying correct type of ts). It is by design, and it is correct way to identify ts type. But that errors don't take much time and are not responsible for ts lag when device is powered on (it is easy to check that claim, just get kernel that produce timestamped dmesg log and observe timestamps around the errors).

We tried to reduce ts lag at wakeup but with no success... as of my knowledge I seriously doubt that is possible... someone wrote that lag was present in wm6.5... I must say that I don't remember, but it would be wonderful if someone has wm6.5 and check.

One more thing... while trying to reduce ts lag, we logged start and end time of ts initialization procedure... and there was a 300 milisec sleep at the end of the procedure... so we removed it just to find out what will happen... and guess what... everything was just the same... in log, init procedure finished 300 milisec sooner than before (as expected), just around the time when panel initialization was over, but the lag was still there and it appeared just the same as before...

I don't want to discourage anyone to try to fix this... but... I'm sceptic...
[HD2 Android NAND Development] jan-willem3:
But should the screen type not be identified on startup instead of every wakeup?
[HD2 Android NAND Development] kundanjuit:
"inactive touchscreen for that initial few seconds" I hope you are out of your mind now. I don't see any ts freeze when the screen wakes up. At least not for "few seconds" and didn't find anyone complaining bout so either.

Secondly the issue reported by this thread is already proved to be incorrect. So if you get some better solution to this can always start a new thread. At least ppl looking for a fix might not end up searching in this thread.
[HD2 Android NAND Development] TonyCubed:
Would it be possible that a fix could be made for the 3 separate screens and we just flash the correct kernel to the right TS?