hello
i'm using samsung galaxy i5510 , and my problem is i'm having a dim dark invisble screen on cwm recovery 5.0.2.6 and some 2.3.6 official roms , and in all modded roms 7 and 10 that i found here ,even with this problem i succeed installing some mod roms using cwm recovery that is barely visible but the same problem the rom installed is dark and invisible but installed ,
here a photo is what the screen looks like it's from another guy on youtube having same problem with i5510
i dont want to come back to 2.2 or 2.3.6 beacause i can do it but i want a solution to install modded roms and cwm recovery without the screen problem , thanks to developper for help
up any help ????
ryu11 said:
up any help ????
Click to expand...
Click to collapse
If you are referring to a problem like this video:
http://www.youtube.com/watch?v=Kwll8ZfgaD0
Then i had the same issue, the only fix is to either never let the screen turn off (which consumes the battery) or run one of the two roms that dont have that issue, those would be
- Stock Gingerbread 2.3.6 latest ones (TPH or PAN)
- Arkas 1.2.3. (based on Gingerbread)
Every other single rom i tried has the same issue (CM7-10,MiUi,...).
Best of luck
Muaadib said:
If you are referring to a problem like this video:
Then i had the same issue, the only fix is to either never let the screen turn off (which consumes the battery) or run one of the two roms that dont have that issue, those would be
- Stock Gingerbread 2.3.6 latest ones (TPH or PAN)
- Arkas 1.2.3. (based on Gingerbread)
Every other single rom i tried has the same issue (CM7-10,MiUi,...).
Best of luck
Click to expand...
Click to collapse
yes this the problem that i have ,the one on the video
i'm now on arkas 1.2.3 based on gingerbread but i want to install cm 7 or cm 10 .. , and i see that many other users of i5510 are on cm 10 without having the invisible display problem
So please can someone help us to define why cm 7 10 work without problems on some i5510 ans don't on other i5510 ,it will be great
up any solutions ????
Sorry to bring up such a silly issue.
But I never encountered any problem like this. So, pls help me out....
I have a WT19i device which being modded with various custom rom at various time.
for more than 1.5 years I didn't got into any kind of problem. and it all messed up.
Yesterday I was trying to install Super jelly bean 8.0 rom.
to do that,
1. I flashed nAa's kernel
2. Wiped whatever needed.
3. Installed rom's zip and gapps
4. Reboot my device.
Everything working well except i don't have any touch response....!
Then I re-flashed my stock 4.0.4 rom, and then everything working fine. (including touch)
Again I flashed cm10 kernel and then installed Cm10 rom
Same problem again, no touch response.....
I really want to install jelly bean rom to my device.
So, pls give me a solution.
Sry if this [Q] is bothering.
I posted this topics to few other places with no solution yet.
Right now, I am on with stock ics rom on my LWW
When I flashed any ics custom or stock rom my touch works fine.
But whenever i tried to flash any custom JB/KK rom to my device according to the procedure i end up with a touchscreen bricked device.
Hardware keys works fine. Everything works fine except touch screen.
I really need some help r8 now.
I tried...
1. cm10
2. cm11
3. Super jellybean 8
4. bean streak etc.
All ends up with a bricked touch screen.
then i flash back to stock and everything is r8.
(I should mention that, I changed my touch screen few weeks ago)
Now plz give me suggestion, what should I do?
I have installed 6 different ICS roms including the stock rom but my touch screen is not working on ICS roms. i have installed the roms according to instructions and all roms installed correctly but when my phone (st15i) restarts for the for the first time after installation than my touch doesn't work at all. i have tried fresh installing again and also tried changing different kernels but problem remained the same.
( Please note that touch screen is working perfectly on custom JB roms and also on stock GB rom )
please solve my problem. i will be very thankful to you
Aashirg said:
I have installed 6 different ICS roms including the stock rom but my touch screen is not working on ICS roms. i have installed the roms according to instructions and all roms installed correctly but when my phone (st15i) restarts for the for the first time after installation than my touch doesn't work at all. i have tried fresh installing again and also tried changing different kernels but problem remained the same.
( Please note that touch screen is working perfectly on custom JB roms and also on stock GB rom )
please solve my problem. i will be very thankful to you
Click to expand...
Click to collapse
remove battery and turn it on again when its not working OK and say result!
Hello friends.
I am new to this wonderful community and very happy to be a part of it.
I am facing a very strange problem. I am trying to update my WT9i Live with walkman from Gingerbread to Ice cream sandwich. Problem is .. whenever I flash an ICS rom my touch doesn't work !! Everything else works fine (physical keys / network / audio). Then if I install GB rom again it works flawlessly.
I have unlocked bootloader.
I am using Flashtool to flash stock roms.
* WT19i_4.0.2.A.0.58_(1254-1868).ftf = works
* WT19i_4.0.2.A.0.62_(1254-1889).ftf = works
* WT19i_4.1.B.0.431_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_Generic.ftf = touch doesn't respond
* WT19i_4.1.B.0.587_CUSTOMIZED CE3 WORLD I 1254-1889.ftf = touch doesn't respond
I have no idea what could be the reason. Any GB roms works smoothly. Any ICS roms bricks the touch screen. I have tried custom kernel (mesa .. kappa) and many custom ICS rom .. same problem. But at any moment I flash GB rom .. everything works.
I did all the research I could (for last 4 days) and read many threads .. tried many things. Nothing helped.
Please help me! Please Please Please.
I have seen many threads with problem "touch does't work because of flashing wrong rom or kernel".
I don't think that's my case. Because whenever I flash a stock GB rom .. it works just fine. Problem happens with ICS roms .. custom or stock.
I am going to try some custom GB rom with custom kernel. I'll post if that works.
This thread is most likely my last hope of finding a solution .. please help!
Just out of curiosity downloaded the 587 ICS generic rom from flasstool website then flashes it .. same touch problem.
Now downloading latest Nightly CM10 coconut. I'll try it. CM 9.1 stable did not worked .. same touch problem.
Please Help ! I dont see a clue ! Why ICS roms would freeze my touch when everything else works? I am on the verge of throwing my phone out of window !!!
Latest CM10 Nightly build = same problem .. touch screen is not working.
Flashed Stock GB = everything is fine !
:crying::crying::crying::crying::crying:
Now I am downloading every regional roms of stock ICS .. its all I can think of.
I know its a very old phone and update / development for it completely stopped. Its forgotten. Still I love this little cute handset and I would love to get ICS on it (for app support .. many app do not work on GB .. like google chrome).
So please help !
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Pixelado said:
Hello there!
Quick question: has your LWW ever been repaired? Like, had it's touch digitizer replaced or manipulated in any way?
I know some replacement parts can conflict with non-stock (or "comes-out-of-the-box" to be precise) software. I bought a replacement display for my Mini Pro and it would just freeze on CM10.1 but worked (kinda) on stock ICS.
And yeah, it's and old phone, but a good one. Development for it and it's 2011 brothers has clearly slowed down but has absolutely not stopped
Click to expand...
Click to collapse
Hello. Thank you for replying. Its a second hand phone .. my brother purchased it from a friend then gave it to me. So it may have a replaced display or digitizer. I just checked with my brother and he said his friend never repaired the phone.
So GB and ICS use different digitizer drivers? Is it possible to use GB touch drivers with ICS?
No idea. Your problem is truly rare haha.
I'm out of ideas here, most of the time flashing a stock ftf does the trick, but not here.
if I were you, i'd sell that phone to someone who woulndn't care about software updates hehe.
Hello Friends.
I am posting this in case someone else face the same problem and find this thread. In my opinion ..this is a very rare and strange problem.
This problem should never happen with an original handset.
If your touch only works with Gingerbread stock roms and even after complete wipe other stock roms freeze your touch .. then you can be sure that your touch was replaced with a cheap one. Go to a servicing center and replace it with a good touch or sell the phone to someone else who doesn't care about updates.
I went to a servicing center today and replaced my touch. Now it works smoothly with stock ICS rom. I am sure it will work with CM too. It costed me around 25$.
1 tip to recognize low quality touch. Low quality touch will not have transparent bottom-left and bottom-right button. You wont be able to see the key lights through it. Good quality touch will have transparent button. Another warning .. after market touch is most probably not scratch resistant like the original touch .. so you may want to use a good screen protector (plastic film) on it.
This is not only for WT19i. Whenever you buy a secondhand set .. make sure its touch wasn't replaced and best to check if its upgraded and working properly.
Thanks to "Pixelado" for hinting me about the replaced touch issue. Then it made sense to me .. there was no other logical reason for the stock rom not working.
I am very happy with my upgraded ICS But kinda sad about the money loss ! Anyway loss is loss. This is a good handset and I hope it will serve me good. Now looking for a way to root it.
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Pixelado said:
i'm always more than glad to help
Now, on the rooting issue, I strongly recommend unlocking your bootloader and flashing a pre-rooted kernel. Why, you ask? Well, you'll find out eventually
Custom kernels often pack a bunch of optimizations and the ability to overclock. I strongly recommend Rage kernel for stock ICS. Once you flash it, i'll take care of rooting your phone on first boot. If you're not able to unlock your bootloader/don't feel comfortable flashing kernels, rooting by exploits is your only choice.
By the way, I strongly suggest giving LegacyXperia CM10.1 a try. Its awesome
Click to expand...
Click to collapse
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
I've never tried mesa, so no comment there. Quie frankly, rage 3.2 seemed to be all i ever needed when using a stock rom. I tried lupus, but stopped using it when they switched from CWM to TWRP.
Angelina7 said:
Thanks a lot Pixelado. I have unlocked bootloader and using mesa kernel 4.8. Would Rage 3.2 would be better than Mesa?
I'll try LegacyXperia CM10.1 .. appreciate the recommendation.
Click to expand...
Click to collapse
i have same problem too
can u solve this problem?