Related
Hiho,
I've been working on getting the panel to unblank faster, not stall to unblank and to not show distortions on unblank (which also happens sometimes).
Please report your experience on blanking/unblanking the panel using the given packages. If you are unsure which one to use, use the dualdie one!
For dualdie (most common) devices: here
For monodie (rare) devices: here
Please report your device (topa100, topa210,...).
If some lone Rhodium user comes by, don't hesitate to test if this breaks the known behaviour on your devices. (From the code, pretty nothing should work for rhods. Please confirm nothing is broken.)
Update: The code has been committed to gitorious. Fetch newer builds from the autobuild service. Thanks to everyone who tested!
Hi,
Kernel is booting fine on my topa100. The lights on the buttons light up immeadtly. Screen doesn't wake always fast. I normally wake up with power and menu button for unlock. This goes realy fast.
Regards,
Bart
bheremans said:
Hi,
Kernel is booting fine on my topa100. The lights on the buttons light up immeadtly. Screen doesn't wake always fast. I normally wake up with power and menu button for unlock. This goes realy fast.
Regards,
Bart
Click to expand...
Click to collapse
But the time from pressing power until the LCD is unblanked is seriously faster now compared to regular kernels, no?
Sent from my MSM using XDA App
TOPA160
boots fine, see this is new 28 package,
freaking, apocalyptic, incredible fast screen.
would almost never think about that fast.
thank you very much. all i need now is a better battery or power management and HW3D working.
I've got a monodie device, the zimage & modules seem to work fine for me but I don't notice any speed difference on unblanking. So I guess if it works well for dualdie devices we know that it won't upset those of us with monodie devices.
shavenyaknz said:
I've got a monodie device, the zimage & modules seem to work fine for me but I don't notice any speed difference on unblanking. So I guess if it works well for dualdie devices we know that it won't upset those of us with monodie devices.
Click to expand...
Click to collapse
Haha, just fooled myself. At least the last package for monodie devices which was posted in the dedicated thread already contained the panel fixes, so you won't really notice a difference. Be told that it took approximately 2 to 3 seconds to unblank before So just go on using the kernel posted here until the monodie issue has been solved.
mweirauch said:
At least the last package for monodie devices which was posted in the dedicated thread already contained the panel fixes, so you won't really notice a difference.
Click to expand...
Click to collapse
Ah, tricky. Thanks for looking out for us monodie guys.
For me (my TOPA200) it's different. Most times it's really fast, sometimes the screen left black and I must press home button a second time.
No other (new) problems at this time.
Greetings and thanks for your great work
shavenyaknz said:
Ah, tricky. Thanks for looking out for us monodie guys.
Click to expand...
Click to collapse
I still "owe" you guys a proper fix. Cotulla - one of the HD2 kernel devs - might need this for the HD2, too. So I see a chance we can find a way of getting the required changes/extensions into HaRET.
cheesy33 said:
For me (my TOPA200) it's different. Most times it's really fast, sometimes the screen left black and I must press home button a second time.
No other (new) problems at this time.
Greetings and thanks for your great work
Click to expand...
Click to collapse
Yap, when device is in idle sleep mode, it shortly wakes (red LED) and sleeps (green LED) immedeately. Only pressing home button helps. But If I recall correctly, that also happened with the old panel setup/init code, it just took longer to fail waking up the lcd panel. I wouldn't clarify this as a regression as it also happened before, just "behaved" a tad bit different due to the long panel waking times. Another issue to be sorted out later ...
Topa 100
Wow, it is awesome.
I never feel the screen wake up that fast before. However, the screen left black and I need to press home button a second time.
You did a very good work and keep it up.
Tested on my Topa100.
"monodie" version cannot create data.img and crashed, "dualdie" booted and now wakeup works much faster.
Thanks!
TOPA100
Dualdie works perfect and gives a much faster feeling!
Thanks for this update!
This dualdie package works fine on my topa100 device.
The screen tuens on incredibly fast, just like(or even faster than) what the WinMo does!
If I "actively" turn on and switch off the LCD, the LCD would react very fast (i.e what I have mentioned above).
However, if the device is standby for about 10sec or longer, usually, the LCD would not turn on. In this situation, i need to press the power again and the LCD turns on immediately.
Also, i found that, in this kernel, pressing the power key would have a higher chances to turn on the LCD than pressing the "end call" key.
Thanks for these positive replies peeps!
I also can observe that it won't power on when in "pm idle sleep mode". When holding end-key for a little bit longer it awakes. Using the home button immediately gets it out of sleep correctly.
I am not quite sure this is a regression or not, but I am of the opinion that this also happened with the old (slow) panel init code, just wasn't as present that much.
Will take a look.
I tried your package on my pure(topa210) and it worked great! Before it took almost 5 secs to unblank, now only 1 or 2 secs!
Very good job, the dualdie version works prety well, wakes the display very fast, but if i continuously lock then wake up few times it will stuck on the blank screen for some secs, then after works again.
monodie or dualdie?
I've got a T5353 TOPA100 but how do I know if I've got a dualdie or monodie device?
Edit: Is this fix ever going to end up in the main build?
stijnr said:
I've got a T5353 TOPA100 but how do I know if I've got a dualdie or monodie device?
Edit: Is this fix ever going to end up in the main build?
Click to expand...
Click to collapse
First try to dualdie version, if that doesn't work out, you got one of the more rare monodie devices.
The panel fix is going to end up in the kernel when I find the time committing it gitirious.org had some problems at the start of the weekend...
Im rooted, and oc at 1100. Havent done anything different lately except added Softlocker. Its kind of unresponsive. I have to hold down longer sometimes, but not by much. (just enough to dive me nuts lol). Any ideas why?
Not that i have an answer but.. mine is the same way for the first several minutes(i don't know how many) after i re-boot. It only started happening after i OC'd to 1100. Usually it gets to being normal after a while. Yes it is annoying..
Do you have soft locker installed? After I deleted it and rebooted it seems fine. So far at least lol.
This is a know issue if you use one of the OC kernels. Just turn your screen off and wait a few seconds and then turn it back on. Your screen will be back to normal.
No, I've had that. It's slightly different. Softlocker removal worked for me.
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
Obviously I have an N7000 and I am noticing a peculiar problem for the past 2 days.
When I use the Power / Home button to wake the phone up, it takes close to 10 seconds to wake up.
When the phone is sleeping and I receive a call, it takes 10 seconds to wake up again.
When the phone is awake and someone calls, and I slide to Answer, the slider gets stuck and the phone is answered after 10 seconds.
I tried various ROMs, did a factory reset as well.
Interesting bit - All these problems vanish when am charging the phone. These problems occur only when am on battery. Could this be a battery issue ? Will replacing the battery help ?
Thanks,
Amit
So have you tried different kernels? Imho, I would flash a rom that is stable. I assume you are 4.0.4. After you fully wipe and install the rom of choice, check if you still have the lag. There are so many reasons that could cause it. Cable you're using, kernel, rom, etc. Do you use setcpu? You can actually set it to change when and how the cpu acts while screen off, on etc etc. In the past if I had a lag like that it was a problem with thte rom itself or an app that was causing the lag. If you need more help just PM me. Please post your results here so we can all follow the symptoms until we find a cure.
Thanks DBY,
I tried AbyssNoteKernel 4.2 and CF-Root. Both are showing the same issues. I am going to try another battery today. If the problem persists, I will let you know.
Thanks,
Amit
Which various ROMs ?
Please post the ROM name,version and the kernel which you are using.
Check your power save settings.
Disable all power saving and see if this resolves your problem.
Sent from my GT-N7000 using xda premium
Hi Guys,
After installing Nameless ROM nightly updates, I experience slow wake up screen problem.
Sometimes it takes good 3-4 seconds after pressing power button to wake the phone up and after it wakes up, suddenly goes to sleep mode. And if I now press power button, it wakes up in 1-2 seconds. Quicker than before, but still not the quickest.
Also, when phone rings most of the time it takes 5-6 seconds for screen to wake up and sometimes by the time you try answering/rejecting call, call has been missed.
I am currently on nameless-4.4.2-20140308-p880-NIGHTLY update.
Has anybody on LG Optimus 4X HD experienced this issue? Going through other forums, I also tried removing SD card and checking if this improves wake up time, but no joy.
Please shed some lights.
Thanks.
Same problems here. Never misses a call because of it though. I believe a way to decrease the time to wake up is to increase the CPU screen off values. This can be done by changing kernels and using trickster and all that, but I'd like to be able to do it from within the ROM. I asked the developer (@Evisceration) if he could add CPU screen off settings to the device control section. He said he liked the idea, so hopefully we'll see the function somewhere in the near future!
Sent from my Nexus 7 using Tapatalk
Nameless
Nameless has many bugs ... I was not happy with it ... I'm sorry for the developers work..
Flash iodak kernel to fix it
Sent from my Nexus 5 using Tapatalk
romulandu said:
Nameless has many bugs ... I was not happy with it ... I'm sorry for the developers work..
Click to expand...
Click to collapse
Hardly any bugs at all for me. If you encounter bugs on a ROM, it will be greatly appreciated if you report them to our devs so they can try to fix things!
This particular 'bug' (not really a bug though) is just due to a relatively low Max CPU Screen Off Freq and can be easily avoided by using another kernel or upping the freq if the current kernel supports it.