Related
Hello all,
I've recently purchased a Galaxy Tab 8.9 and of course after a day or two with a stock ROM, I was looking to install a custom ROM to get a better overall experience.
Unfortunately, with every custom ROM I've tried, I get this weird display artifact (see video below). It starts when the bootloader switched over to the boot animation. The artifact will continue after the OS is loaded up and on the lock-screen. If the display is turned off manually or due to time-out and then turned back on, everything is fine. It's doesn't seem to affect functionality at all, it's just really annoying.
It's happened with CM9, Galaxian Soup AOSP, Galaxian Soup AOKP, Overcome 8.9, and AOKP b29-31. When I restore my nandroid backup, it works fine, so I don't think it's a hardware issue, but it's really annoying.
Broken up URL is below (still a newb), please let me know if anyone else has this issue and/or knows what may cause it or fix it.
http: //youtu.be /Xt2OPfy4TOU
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to General
Nobody has seen anything similar?
That unfortunately is a hardware issue. You need to replace the unit :-(
Thanks for the reply, but wouldn't a hardware issue be present with the stock OS as well?
It really depends on what registry is being touched by the custom rom. It looks like the vertical synchronisation of the screen is being screwed up somehow. If this effect is seen only in your device it must mean that something is fishy with a hardware part of the screen controller and the sync if being affected by a value written in some other part of the control registries. I have no idea how I could express this clearer.
That's awkward to be honest. I haven't seen anything like it in my 7310, be it with Stock, or any other custom ROMs I've tried (from the old AOSP Galaxian Soup alphas to the current beta and the old versions of Overcome too). Do you completely wipe your device before flashing any custom ROM?
I did completely wipe data/cache/dalvik before every ROM install.
Unfortunately, I don't know how I'd return it, since the error is only apparent when a custom ROM is installed.
jhhoffma said:
Hello all,
I've recently purchased a Galaxy Tab 8.9 and of course after a day or two with a stock ROM, I was looking to install a custom ROM to get a better overall experience.
Unfortunately, with every custom ROM I've tried, I get this weird display artifact (see video below). It starts when the bootloader switched over to the boot animation. The artifact will continue after the OS is loaded up and on the lock-screen. If the display is turned off manually or due to time-out and then turned back on, everything is fine. It's doesn't seem to affect functionality at all, it's just really annoying.
It's happened with CM9, Galaxian Soup AOSP, Galaxian Soup AOKP, Overcome 8.9, and AOKP b29-31. When I restore my nandroid backup, it works fine, so I don't think it's a hardware issue, but it's really annoying.
Broken up URL is below (still a newb), please let me know if anyone else has this issue and/or knows what may cause it or fix it.
http: //youtu.be /Xt2OPfy4TOU
Click to expand...
Click to collapse
i got the same issue, how did you resolve it?
thanks
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
Hey there,
First of all, a big thanks to pawitp and the other developers for the great ROMs,
my cell (SGS i9000, currently running pawitps nightly 10.1-20130423)
has never been faster, better or more beautiful.
Unfortunately, there is a little drawback:
I have missed several calls, since the phone won't make a sound while being called.
This is the case in over 90% of calls. With SMS notifications, this percentage rises to 100%.
The messenger notifications seem to work almost in every case.
Thanks to the site search, I'm aware of the issues with USB-connections, setting the ringtone
to "unknown", as I have experienced also.
I "fixed" the problem manually by choosing the ringtone (and notification sound) again,
sadly without any observable change for the better.
So, I upgraded the firmware, re-flashed it several times (by Odin and CWM), did wipe (dalvik) cache and tried a different file format for the ringtones. A friend of mine is running the exact same system, but has not experienced the mentioned issue apart from one week or so; and after installation of the newest nightly, his troubles were gone.
As I really like this ROM, I would favor not to switch my beloved firmware.
So, any of you guys has any suggestions how to get rid of that annoying problem?
As already mentioned, I love my SGS with CM, but a cellphone which doesn't ring seems a bit castrated to me^^
Of course I'm more than willing to give more information if needed.
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
ok guys, after almost a year of testing different custom ROMs (CM 11,10.1,10.2) I am thinking about going back to stock JB because of the bugs (GPS, dark camera, low incall volume, force close, compass and magnet sensor bugs, random reboots, youtube pixelation, twitch stream not working, 720p video lag, alarm not ringing very few times, fast battery drains). So If i go back to stock 4.1.2 JB then i will have to face lag and not bugs. One big reason that i want to go back to stock 4.1.2 JB is that in CM 11 custom rom team canjica which i am currently using, i found that there is a network bug and network seems to go away and i am unable to call anyone while the other phone is working fine with the same sim card at same location, and bringing the network back after restarting the phone is such a hassle. Is there any way to make stock JB ROM as fast and lag free as CM 11 ? I am willing to root and do anything to the phone (debloating and kernels). Any suggestions ??
heartbrake said:
ok guys, after almost a year of testing different custom ROMs (CM 11,10.1,10.2) I am thinking about going back to stock JB because of the bugs (GPS, dark camera, low incall volume, force close, compass and magnet sensor bugs, random reboots, youtube pixelation, twitch stream not working, 720p video lag, alarm not ringing very few times, fast battery drains). So If i go back to stock 4.1.2 JB then i will have to face lag and not bugs. One big reason that i want to go back to stock 4.1.2 JB is that in CM 11 custom rom team canjica which i am currently using, i found that there is a network bug and network seems to go away and i am unable to call anyone while the other phone is working fine with the same sim card at same location, and bringing the network back after restarting the phone is such a hassle. Is there any way to make stock JB ROM as fast and lag free as CM 11 ? I am willing to root and do anything to the phone (debloating and kernels). Any suggestions ??
Click to expand...
Click to collapse
Use the amulet in a thread here (the last version). Do not forget to give feedback to the users janice here too. Let others can know it too. I hope it can help.