LG P940 Prada 3.0 Touch sensitivity problem after ICS update - Miscellaneous Android Development

I have an issue with LG Prada 3.0 P940 after update to ICS 4.0.4, touch sensitivity isn't OK, I really have to press screen hard to enter something or to click somewhere (with 2.3.7 everything was fine). Is there any way to solve this problem, because this way phone is unusable and it is not broken but I cant use it normally. Thanks for any kind of help, really appreciate it.

Does anyone have any suggestion, solution, anything. In this condition my phone is unusable.

Try and do a factory reset.
dfrimmel said:
Does anyone have any suggestion, solution, anything. In this condition my phone is unusable.
Click to expand...
Click to collapse
dfrimmel said:
I have an issue with LG Prada 3.0 P940 after update to ICS 4.0.4, touch sensitivity isn't OK, I really have to press screen hard to enter something or to click somewhere (with 2.3.7 everything was fine). Is there any way to solve this problem, because this way phone is unusable and it is not broken but I cant use it normally. Thanks for any kind of help, really appreciate it.
Click to expand...
Click to collapse

Tried that already but no luck,still the same thing.

Is your device rooted?
dfrimmel said:
Tried that already but no luck,still the same thing.
Click to expand...
Click to collapse

No it`s not rooted, stock 4.0.4 without root.

I have this device but rooted and i don´t have this issue, maybe you can reflash it and flash CWM then do a factory reset via CWM
dfrimmel said:
No it`s not rooted, stock 4.0.4 without root.
Click to expand...
Click to collapse

Related

[Q] Bluetooth not working!

I got my HTC Sensation, it was already upgraded to the official ICS, everything works except bluetooth. When I try to start bluetooth it just says "Turning bluetooth on" and stays like that for about 10 seconds and nothing happens. Is there any fix for this?
reboot the phone,I think this is a ICS glitch because it happens on every rom I have tried.
Macklessdaddy said:
reboot the phone,I think this is a ICS glitch because it happens on every rom I have tried.
Click to expand...
Click to collapse
I did as you said, but still nothing. i.imgur. com/8bBhf.png
Have you been flashing any radios?
Rumball said:
Have you been flashing any radios?
Click to expand...
Click to collapse
I have no idea, I just bought the phone and it had ICS in it... when I turn the phone on it says swisscom... The phone is not even rooted.
Swisscom?
KAwAtA said:
Swisscom?
Click to expand...
Click to collapse
shop.swisscom. ch/Onlineshop/Pages/ProductDetail/ProductDetail.aspx?cat=OS_Mobilkommunikation&subcat=OS_Mobiles_Internet&lang=EN&id=000000000010039811
D_avi_D said:
I have no idea, I just bought the phone and it had ICS in it... when I turn the phone on it says swisscom... The phone is not even rooted.
Click to expand...
Click to collapse
I would return it. Could be a hardware issue if the phone isn't rooted /running a custom ROM
Rumball said:
I would return it. Could be a hardware issue if the phone isn't rooted /running a custom ROM
Click to expand...
Click to collapse
Alright, thanks for the help!

[Q] Updated to Jelly Bean and got bugged

So, yesterday I decided to upgrade my Android version from ICS to JB. I forgot to do a factory reset first, and now I can barely use the tab. I'm guessing it's laggy and slow because it has only 200~mb of space only. Buuut, the huge problem is that I can't reboot. The button for the last comfirmation is dead. I click it, but nothing happens.
Anyone had a similar experience? The device is not rooted.
Hekikai said:
So, yesterday I decided to upgrade my Android version from ICS to JB. I forgot to do a factory reset first, and now I can barely use the tab. I'm guessing it's laggy and slow because it has only 200~mb of space only. Buuut, the huge problem is that I can't reboot. The button for the last comfirmation is dead. I click it, but nothing happens.
Anyone had a similar experience? The device is not rooted.
Click to expand...
Click to collapse
reflash correctly
qazmed said:
reflash correctly
Click to expand...
Click to collapse
What do you mean, exactly?
Hekikai said:
What do you mean, exactly?
Click to expand...
Click to collapse
download the rom on ur pc and flash it using odin
qazmed said:
download the rom on ur pc and flash it using odin
Click to expand...
Click to collapse
I second quazmed's info.. Something went wrong with the install.. I'm guessing you upgraded through Samsung kies? Or did you get a notification to upgrade? Either way its a messed up system and you should use Odin to reflash the firmware.
Tip. If you just hold the power button long enough, the device will reboot that's true on any Samsung device I believe..

Un-intentional brick??

:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
dpeti said:
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
Click to expand...
Click to collapse
No, sorry, you won't be able to use APX mode without have making the NvFlash backups beforehand.
is this possible? I'm now afraid to update to newer cm11 versions...
aplopeanu said:
is this possible? I'm now afraid to update to newer cm11 versions...
Click to expand...
Click to collapse
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
cmendonc2 said:
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
Click to expand...
Click to collapse
so basically ... don't update CM11 until this is fixed right?
aplopeanu said:
so basically ... don't update CM11 until this is fixed right?
Click to expand...
Click to collapse
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
cmendonc2 said:
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
Click to expand...
Click to collapse
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
aplopeanu said:
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
Click to expand...
Click to collapse
In theory, yes. But many people consider it easier to RMA it.
cmendonc2 said:
In theory, yes. But many people consider it easier to RMA it.
Click to expand...
Click to collapse
RMA?
aplopeanu said:
RMA?
Click to expand...
Click to collapse
Send it back to Asus and pay the repair costs.

[Q] Problem with touchscreen after unrooting

Hello guys,
So... I have samsung GT-S7710 (Galaxy Xcover2).
I had it rooted with prerooted odexed FW (from this post)
So this is the OK part :laugh: .... everything was working fine.
Then, to claim my waranty, i have unrooted it...so I've reseted the counter and flashed it with FW I've backed up from my phone before rooting.
So now for the wierd part...everything was ok, booted my phone, everything was working, then restarted it, and all of the sudden touchscreen stoped working
I've read about bricked touchscreens, but mine worked for some time..
So I was thinking now...should I try and flash official FW for my phone, rather than backed up one ?
Or is there any thing else to do ? Or even...did maybe touchscreen went to *khm* ?
Thank you guys for your time you spent reading & hopefully anwsering this
Flyzoor said:
Hello guys,
So... I have samsung GT-S7710 (Galaxy Xcover2).
I had it rooted with prerooted odexed FW (from this post)
So this is the OK part :laugh: .... everything was working fine.
Then, to claim my waranty, i have unrooted it...so I've reseted the counter and flashed it with FW I've backed up from my phone before rooting.
So now for the wierd part...everything was ok, booted my phone, everything was working, then restarted it, and all of the sudden touchscreen stoped working
I've read about bricked touchscreens, but mine worked for some time..
So I was thinking now...should I try and flash official FW for my phone, rather than backed up one ?
Or is there any thing else to do ? Or even...did maybe touchscreen went to *khm* ?
Thank you guys for your time you spent reading & hopefully anwsering this
Click to expand...
Click to collapse
i would say try to flash it again with OFFICIAL STOCK ROM and do let me know the results by QUOTING ME!!
pushkardua said:
i would say try to flash it again with OFFICIAL STOCK ROM and do let me know the results by QUOTING ME!!
Click to expand...
Click to collapse
Thanks for your reply, I've tried this right away.
I've tried with official version (from SamMobile)...I've choosen version for Slvoenia (my country) w/o any provider
But still no sucsess...
Odin sucsesfully flashes, phone boots, and touch doesnt work again (I'm stuck at that starting page...to chose language and so on..)
But like I've said everything else works ok, eg.: power btn, wolume up/down,... only touch doesnt work.
pushkardua said:
i would say try to flash it again with OFFICIAL STOCK ROM and do let me know the results by QUOTING ME!!
Click to expand...
Click to collapse
Sorry for the double post..
I've tried to flash ROM that I was using before (rooted one). And now touch even doesnt work in this one.
Is this maybe hardware problem ?
Flyzoor said:
Sorry for the double post..
I've tried to flash ROM that I was using before (rooted one). And now touch even doesnt work in this one.
Is this maybe hardware problem ?
Click to expand...
Click to collapse
i think you should flash stock rom and give it to samsung maybe.. if it's in warrentee they would get it replaced i guess
hope it helps you
pushkardua said:
i think you should flash stock rom and give it to samsung maybe.. if it's in warrentee they would get it replaced i guess
hope it helps you
Click to expand...
Click to collapse
I will do exactly this
One more thing... I've bought my phone in a electronic store (no carier involved). Should I flash it with FW for my country ? What if phone had any other FW on when it was new ?
EDIT:
Just realised....I've flashed rooted FW on my phone...which has increased the counter of custom flashes... To reset the counter I need root permisions...but how if I cant even unlock my phone.
I probably cant use [email protected], because I've hard reseted the phone, which means that Usb debug is disabled (correct me if I'm wrong), so thats of the list..
Do you guys know if any FW has enabled USB debug by default ? Or if there is any other option ?

How to update an outdated bootloader J710fn?

Hello,
I have two j7 2016 fn. One is mine one for repair. I recognized that there is a bootlogo difference. The onw which works has a thin powered by android line while the one with touch problems has a bold android. So I guess there I have an outdated bootloader on that phone. How can I update?
spirit_of_the_ocean said:
Hello,
I have two j7 2016 fn. One is mine one for repair. I recognized that there is a bootlogo difference. The onw which works has a thin powered by android line while the one with touch problems has a bold android. So I guess there I have an outdated bootloader on that phone. How can I update?
Click to expand...
Click to collapse
Use samsung smart switch
sandeepkumar0153 said:
Use samsung smart switch
Click to expand...
Click to collapse
Yes I already tried
But smartswitch said that the phone does not allow data transfer via usb.
I can't use touch. Every rom I flashed does not make the touchscreen work.
I saw on youtube that some said to get back to marshmallow. But I heard that could lead to loosing the imei.
What should I do?
spirit_of_the_ocean said:
Yes I already tried
But smartswitch said that the phone does not allow data transfer via usb.
I can't use touch. Every rom I flashed does not make the touchscreen work.
I saw on youtube that some said to get back to marshmallow. But I heard that could lead to loosing the imei.
What should I do?
Click to expand...
Click to collapse
Does the touch work in twrp ?? There is a twrp flashable stock rom in here, maybe it helps
sandeepkumar0153 said:
Does the touch work in twrp ?? There is a twrp flashable stock rom in here, maybe it helps
Click to expand...
Click to collapse
Thanks for your help. Since in download mode frp lock shows as on I did not tried to install twrp. I don't know what will happen because my friend gave it with a Factory reset to me.
spirit_of_the_ocean said:
Thanks for your help. Since in download mode frp lock shows as on I did not tried to install twrp. I don't know what will happen because my friend gave it with a Factory reset to me.
Click to expand...
Click to collapse
Out of ideas now, good luck and i hope you get it solved

Categories

Resources