Loss of touch interface on bootUp

[Guest shawnboy5]

Hey guys,

I have recently installed the Jellyfish RLS9 on my newly bought OSF, it looks great so far but I have a few queries about loss of touch interface. I have wiped all data and used clockworks to install the zip file provided in this post.

Upon completion of installation, I rebooted the device and prompted the green android screen start up.

None of my touch interface works when the screen prompts "Touch the green man to start".

So I removed the battery and replace it in again, The touch interface works this time and I can continue on setup my phone.

However, after completing setting up my phone, I tried to reboot my phone again, but this time the touch interface just does not work at all, no matter how many times I remove the battery or rebooting.

Has anyone came across the same problem?

Your input will be very much appreciated.

Thanks!

[Guest Mushroom_Lord]

Hey guys,

I have recently installed the Jellyfish RLS9 on my newly bought OSF, it looks great so far but I have a few queries about loss of touch interface. I have wiped all data and used clockworks to install the zip file provided in this post.

Upon completion of installation, I rebooted the device and prompted the green android screen start up.

None of my touch interface works when the screen prompts "Touch the green man to start".

So I removed the battery and replace it in again, The touch interface works this time and I can continue on setup my phone.

However, after completing setting up my phone, I tried to reboot my phone again, but this time the touch interface just does not work at all, no matter how many times I remove the battery or rebooting.

Has anyone came across the same problem?

Your input will be very much appreciated.

Thanks!

Hmm...have a look on the JJ thread, see if anyone has found this before. A quick forum search might provide a patch/fix.

Japanese Jellyfish is no longer under development, and despite once "leading" the ROMS for the blade, it is becoming obsolete.

I recommended MCR for a stable, smooth, basic, polished, day to day ROM

FLB is a faster, smoother, day to day, and stable ROM

I would not start installing Cyanogen yet. It has many issues that are still to be fixed (eg, screen black after calls, [can not be woken either]), the ADW launcher is slow (and quite frankly ugly). there are workarounds available.

For the install with less hassle, basic ROM, go for MCR

for a SLIGHTLY longer install (two zips not one) with the same basic day to day, polished ROM as MCR, but notably faster, go for MCR.

If you are willing to risk it get cyanogen, for 2.3 which may have faster gaming, and scores higher in tests, but, for average use is much slower.

I started out with MCR, headed to JJ cause of its reputation, headed back to MCR for a faster, more polished ROM, and then turned to FLB which does everything that MCR does, but with added speed.

I tried cm7. but it annoyed me so much, I reverted back to FLB (ah how I love it)

[Guest Ralph Martin]

If you search the forum you will see that faulty touchscreens have happened to quite a few people - irrespective of the ROM used. It seems to be some sort of manufacturing (or design?) problem. Mine works on and off...

[Guest shawnboy5]

Great, I will give MCR and FLB a try tonight.

I hope I am not the special case where screen fails. =.=

First android experience.

Thanks for the input guys.

Hmm...have a look on the JJ thread, see if anyone has found this before. A quick forum search might provide a patch/fix.

Japanese Jellyfish is no longer under development, and despite once "leading" the ROMS for the blade, it is becoming obsolete.

I recommended MCR for a stable, smooth, basic, polished, day to day ROM

FLB is a faster, smoother, day to day, and stable ROM

I would not start installing Cyanogen yet. It has many issues that are still to be fixed (eg, screen black after calls, [can not be woken either]), the ADW launcher is slow (and quite frankly ugly). there are workarounds available.

For the install with less hassle, basic ROM, go for MCR

for a SLIGHTLY longer install (two zips not one) with the same basic day to day, polished ROM as MCR, but notably faster, go for MCR.

If you are willing to risk it get cyanogen, for 2.3 which may have faster gaming, and scores higher in tests, but, for average use is much slower.

I started out with MCR, headed to JJ cause of its reputation, headed back to MCR for a faster, more polished ROM, and then turned to FLB which does everything that MCR does, but with added speed.

I tried cm7. but it annoyed me so much, I reverted back to FLB (ah how I love it)

[Guest wbaw]

You're not a special case, it's a fairly common fault, but you do have a broken phone. You should take it back to the shop that you bought it from & get a replacement.

[Guest yoghurt]

You're not a special case, it's a fairly common fault, but you do have a broken phone. You should take it back to the shop that you bought it from & get a replacement.

Hi

I have experienced exactly the same problem with several of the popular custom ROMS ie touch screen does not respond and have to remove the battery.

Do you suggest I also return it? I ask as I put the stock ROM back on and turned it on and its now fine! (booted first time on 3 consecutive goes)

Cheers

Yoghurt

[Guest wbaw]

Hi

I have experienced exactly the same problem with several of the popular custom ROMS ie touch screen does not respond and have to remove the battery.

Do you suggest I also return it? I ask as I put the stock ROM back on and turned it on and its now fine! (booted first time on 3 consecutive goes)

Cheers

Yoghurt

Return it & get a replacement if it stops working while on the stock rom.

A few phones have a bad connection to the touch screen, so it might work intermittently & it might get worse. If gently squeezing the phone at the top, or removing the back cover (but not battery) brings the touch screen back to life temporarily, then it's a hardware problem & you need a replacement.

There are different touch screen problems in some of the different roms. If going back to the stock rom totally fixes it, then it's one of those problems, try a different rom.

[Guest yoghurt]

Will do-many thanks for your helpful advice

Return it & get a replacement if it stops working while on the stock rom.

A few phones have a bad connection to the touch screen, so it might work intermittently & it might get worse. If gently squeezing the phone at the top, or removing the back cover (but not battery) brings the touch screen back to life temporarily, then it's a hardware problem & you need a replacement.

There are different touch screen problems in some of the different roms. If going back to the stock rom totally fixes it, then it's one of those problems, try a different rom.

[Guest darren 1980]

Hey guys,

I have recently installed the Jellyfish RLS9 on my newly bought OSF, it looks great so far but I have a few queries about loss of touch interface. I have wiped all data and used clockworks to install the zip file provided in this post.

Upon completion of installation, I rebooted the device and prompted the green android screen start up.

None of my touch interface works when the screen prompts "Touch the green man to start".

So I removed the battery and replace it in again, The touch interface works this time and I can continue on setup my phone.

However, after completing setting up my phone, I tried to reboot my phone again, but this time the touch interface just does not work at all, no matter how many times I remove the battery or rebooting.

Has anyone came across the same problem?

Your input will be very much appreciated.

Thanks!

Hey there dude,

I had exactly the same thing with my new Orange San Francisco. Am curious to know if it was one of the Black models???

It's just that my girlfriend ordered two OSF's hers was the White one and I installed Seb404's R8 de orangeated Rom,

it runs flawless and does what it says on the tin (lol) ...yet when it came to my OSF the thing was a nightmare.

I spent the whole day trying nearly every rom from Seb404's r8 to latest, JJ Rls9, MCR.

Became an expert at using Clockwork and wore down my thumb from battery removal (lol)

Also the manual method of getting Clockwork on...the "Vol up & Power" combo didn't work on this new Black OSF.

I got the touchscreen working about 3 times out of many battery removal power downs.

Have since restored the stock orange rom and sent it back. They said the only replacement they

can offer at this time is a White model OSF (I kinda jumped at that lol)

Hope you manage to get sorted too, its definitely not related to the awesome roms these guys write. :(

[Guest as500]

Hey there dude,

I had exactly the same thing with my new Orange San Francisco. Am curious to know if it was one of the Black models???

It's just that my girlfriend ordered two OSF's hers was the White one and I installed Seb404's R8 de orangeated Rom,

it runs flawless and does what it says on the tin (lol) ...yet when it came to my OSF the thing was a nightmare.

I spent the whole day trying nearly every rom from Seb404's r8 to latest, JJ Rls9, MCR.

Became an expert at using Clockwork and wore down my thumb from battery removal (lol)

Also the manual method of getting Clockwork on...the "Vol up & Power" combo didn't work on this new Black OSF.

I got the touchscreen working about 3 times out of many battery removal power downs.

Have since restored the stock orange rom and sent it back. They said the only replacement they

can offer at this time is a White model OSF (I kinda jumped at that lol)

Hope you manage to get sorted too, its definitely not related to the awesome roms these guys write. :)

Same here, followed instructions on orangesanfrancisco.co.uk, unlocked first so I could use o2 sim, then clockwork etc and finally put JJ9 rom on. Immediately on bootup, had the 'touch screen to begin' logo, but touch screen unresponsive. Reflashed several times wipe cache etc, but still not working. I put back the (allegedly) stock Orange UK B10 rom and still had the same problem.

Removal of battery etc made no difference for me and as I was now on stock B10 rom, and clockwork had disappeared completely, with no method to get into the phone to reinstall, I sent it back for a replacement. Left out the SD card as I could not get the phone to mount the card on the computer so I would not have been able to delete the JJ9 rom on the root of the card :(

Mine was a black one, so maybe there is a subtle difference in touch screen on the black ones with B10 standard rom? Replacement is black too, so I have done nothing except unlock and use the non-Orange homescreen etc :(

Might update to a 2.3 rom later in the year once it's established what the issue is with these newer B10 rom handsets (assuming it's not just a bad batch with flakey touchscreens), but I'm not that keen at the moment....

Not a bad little phone actually, replacing my iPhone 3GS with this, the OSF is not quite as slick or responsive, but am liking some of more flexible options in Android compared to iOS. It's quite amazing value too.

[Guest chs01]

I've had similar problems with a new BLACK Orange San Francisco shipped with B10 ROM.

I've tried FLB r10b, JJ RLS9, MCR r12, de-crossed (cheque) r0.2 and the touchscreen never worked once.

On some of the ROMS I noticed that the two ".."s at the bottom left corner of the screen are highlighted, which makes me wonder whether the system thinks I'm touching there?

Restoring the original B10 ROM brings the touchscreen back to life without fail. I have tried several apps (MultiTouch Tester, Multitouch Vis Test, MultiTouch Visualizer 2) when running the original ROM and all show the touchscreen is working fine.

Maybe these new black OSFs have got a different touchscreen?

[Guest Cerberii]

Just adding another user with the same problems. New SF with B10 rom and touchscreen would not work after flashing latest JJ rom. I tried several other roms including the stock orange B10 rom and could not get the touchscreen to work with any of them. I sent it back and got a replacement but am reluctant to flash anything now in case there is a hardware compatibility problem with these latest phones.

I can't really provide any more information that has not been covered already other than the key test in clockwork would not show any activity for the touchscreen post flashing. I don't know if it was registering touches in the test before the first flash but the touchscreen was working fine with the phone in delivered state.

[Guest Cerberii]

Well today I bit the bullet and flashed the replacement with mcr r12 using clockwork 3.0.0.6 and all went well and then changed over to flb r10b with no problems. Everything is working fine.

So maybe it was just a bad handset after all and not an issue with the roms?

[Guest darren 1980]

Well today I bit the bullet and flashed the replacement with mcr r12 using clockwork 3.0.0.6 and all went well and then changed over to flb r10b with no problems. Everything is working fine.

So maybe it was just a bad handset after all and not an issue with the roms?

Good to hear your sorted :D

I got my replacement (White OSF running B08 rom) , Have since clockwork'd, Nandroid backup'd and de-orangeated it.

All went smooth, Just glad to be sorted at last too.

[Guest 2brains]

Just got a new San Fran today. All ok out the box. Loaded FLB-froyo and touch screen wouldnt work. Then tried modaco, still no touchscreen. Have now tried to put the stock rom back (via recovery and then TPT version) and touchscreen still doesnt work :-(

Loading the stock roms has also removed clockwork recovery. Stuck with a non working phone now !

[Guest ronc2000]

For those with touch screen problem after flashing to new rom, can you state the colour and IMEI number?

Just the first 4 numbers of the last 7 digits - i.e. I have one ending with 069xxxx (working!).

This might give a hint to what may or may not work with a new rom.

[Guest darren 1980]

For those with touch screen problem after flashing to new rom, can you state the colour and IMEI number?

Just the first 4 numbers of the last 7 digits - i.e. I have one ending with 069xxxx (working!).

This might give a hint to what may or may not work with a new rom.

fortunately I kept the details of my (non working) Black OSF with firmware B10, IMEI 0973xxx

Hope this information proves helpful, Having been in the same situation :D

[Guest Tadger]

My OSF that doesn't like custom ROMS's is also a black(grey) version, B10 Stock firmware and ,last bit of the IMEI: 098xxxx

[Guest chs01]

My non-working-after-custom-ROM Black/Grey OSF with original firmware B10 has IMEI 0999xxx

As well as the two '..'s in bottom left of homescreen appearing to be highlighted, the back button flashes red.

Edited March 16, 2011 by chs01

[Guest 2brains]

For those with touch screen problem after flashing to new rom, can you state the colour and IMEI number?

Just the first 4 numbers of the last 7 digits - i.e. I have one ending with 069xxxx (working!).

This might give a hint to what may or may not work with a new rom.

mine is grey/black

IMEI Digits : 0992xxx

[Guest abarthman]

Bought two OSFs within a few days of each other from the onestopphoneshop at the end of February.

Both dark grey with B10 roms.

IMEIs 0746XXX and 0776XXX

Installed JJ in both to begin with.

One works flawlessly and the other - 0776XXX - which was bought a few days later has the intermittent non-responsive touch-screen.

It usually stops responding after a battery recharge - from computer or mains - but it has also stopped responding at other times.

Taking the back off and disconnecting the battery seems to bring it back to life most of the time, but, on a couple of occasions it has needed a couple of battery removals to do so.

I installed the latest flb froyo at the weekend to see if that made a difference, but the issue remains.

It's not that big an issue, but, if it gets worse, I'll need to put the stock orange B10 rom back on and, if that doesn't cure it, get it replaced.

I am really hoping that this is just a software issue and one of the clever rom developers will suss it eventually.

Edited March 16, 2011 by abarthman

[Guest gamer9]

So basically this is only affecting the new grey/black handsets and not the white ones?

Thx

[Guest 2brains]

pretty much out of ideas at the moment, tried loading cyanogen, no change touchscreen still not working.

Has any one got a recovery backup of a stock B10 to hand? on the offchance its different to the TPT image I downloaded from here

[Guest rexlampard]

same here, my touch screen was not responding at all after trying few custom roms.

Returned it today and got a replacement...but not willing to try again...may wait for a week or so to see anyone can solve it..hopefully

[Guest ronc2000]

So any one with a grey IMEI number ending 077xxx or later working without issues?