Since there are individual threads going on regarding diff. issues that some Sensations suffer from, i thought i would start this thread to have all these issues in one place. And more importantly, we can suggest some tests that could be performed right out of the box to figure out whether or not the device should be sent for replacement.
I'll keep the first post updated based on your recommendations in this thread.
-The first thing i can think of is the issue with the device being loose in its back cover, which is something that should be kept in mind and also can be easily tested
-Then comes the problem of "separate" layers under the screen which is accompanied by a sound resembling "a sticker being peeled of a surface".
Touchscreen not working properly.
Except you can't test for that when you first get it because it takes a few days to appear.
bcpk said:
Touchscreen not working properly.
Except you can't test for that when you first get it because it takes a few days to appear.
Click to expand...
Click to collapse
did u see that "grounding issue" video?
bcpk said:
Touchscreen not working properly.
Except you can't test for that when you first get it because it takes a few days to appear.
Click to expand...
Click to collapse
FWIW, I had that issue but once I installed ADW launcher it hasn't happened again...it's been two days now. It's probably just a coincidence, but never the less figured I'd pass it on.
Is the second issue on the OP is relevant to this video?
http://www.youtube.com/watch?v=O3sZYKz9duI
I couldn't see any thing wrong on that video though.
Figure_desire said:
Is the second issue on the OP is relevant to this video?
http://www.youtube.com/watch?v=O3sZYKz9duI
I couldn't see any thing wrong on that video though.
Click to expand...
Click to collapse
what is this one tryin to show?
alireza_simkesh said:
what is this one tryin to show?
Click to expand...
Click to collapse
Don't know. Don't have the phone yet. Just tought it was something relevant
Related
Hey,
I have had a vox for over half a year now and I was using the new OS from HTC.
Recently I had to reflash my phone because it was having a number of issues. The enter key on the front keypad would not work. It would handomly turn the bluetooth on. The screen would not be bright while I was using it (the standy dim lighting).
The enter key on the slide out keyboard does work.
After the reflash everything worked great. Now I have used the phone for a week and this starts happening again. Sometimes restarting will get rid of these problems, but it still seems to be there.
I tried to update to Dr. Gonzo's 6.1 ROM, but I was unable to flash that one, I got an error saying the ROM is corrupt.
Do you think this may be a hardware problem?
Please let me know what you think,
Thanks,
GRoder
which ROM are you currently using?
Did you USPL the device before flashing WM6.1 ROM?
that is a necessary step.
Let us know after you flash doc's ROM.
And another one who didn't even care to read the readme or some threats...
frauhottelmann said:
And another one who didn't even care to read the readme or some threats...
Click to expand...
Click to collapse
oh come on man... play nice. some just don't know that search is your friend. They'll learn though.
frauhottelmann said:
And another one who didn't even care to read the readme or some threats...
Click to expand...
Click to collapse
hey hey, I did read both of the supplied read me files, however I'm sure sure that the updates UPL/SPL updates worked correctly. There is one step that I am unsure about.
bellor said:
oh come on man... play nice. some just don't know that search is your friend. They'll learn though.
Click to expand...
Click to collapse
yea I always use the search function in forums, why ask what 10 others have asked before.
I'm just curious if anyone has experienced a similar problem with their phone. I'm hoping this is not a hardware issue...
Nope, this is something for which people are opening a new threat every day, so I hope you can understand that I am a bit grumpy sometimes!
@groder54
There is one step that I am unsure about.
Click to expand...
Click to collapse
what is it?
prajith said:
@groder54
what is it?
Click to expand...
Click to collapse
I will try it again tonight when I get home. I think it was the step where I had to run the *.bat file with all the promts...at the end the phone did not behave like it said in the read me so I think something may have gone wrong at that point.
The display stopped working 2-3 days ago. On booting i can see the google logo for 2-3 seconds before the screen goes dark. The phone works and i can hear dings of messages, but i cant access any of it. Once i kept shut it for a day i was able to see the screen for 10-15 seconds( i used this window to remove the screen lock so that i can use the usb transfer ). Now keeping the phone shut for long duration has no effect.
I can see the fastboot screen but not the recovery screen throught it.
I also bought a slimport so that i could see the screen on my pc. It works (not for the fastboot or recovery), however the touch doesn't work and the volume and power buttons response is too sluggish. I can connect the mouse but it is of no use as i can't see the screen on PC and use the mouse at the same time. I tried adb ( i have no experience of it ) but i cant touch the allow pernmissions key on the screen for the above reasons. Also what advantage would adb be in this case?.
Any advice ?
PS: i have cyanogenmod
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Sorry, i don't follow. U mean a ram replacement is needed ?
jd1639 said:
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nexmus said:
Sorry, i don't follow. U mean a ram replacement is needed ?
Click to expand...
Click to collapse
It was a typo.. He meant RMA
- Sent from an IceCold Hammerhead!
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
vin4yak said:
It was a typo.. He meant RMA
Click to expand...
Click to collapse
nexmus said:
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
Click to expand...
Click to collapse
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
How can i do it using fastboot ?
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
nexmus said:
How can i do it using fastboot ?
Click to expand...
Click to collapse
I do t understand the question. Is this question one you're asking having already read the fastboot return to stock guide?
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
vnvman said:
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
Click to expand...
Click to collapse
What does the month it was made have to do with anything?
rootSU said:
What does the month it was made have to do with anything?
Click to expand...
Click to collapse
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
vnvman said:
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
Click to expand...
Click to collapse
They're not really built in batches. Manufacturing was continuous. They just changed the serial number every time the month changes so I dont think this would actually mean anything
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
vnvman said:
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
Click to expand...
Click to collapse
Speaker holes is a bad example because even the latest built devices it was still a lottery whether you got bigger or smaller holes. That's down to what you mentioned earlier, QC
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
I was able to unroot and flash the stock image. The problem still exists though, so it has to be a hardware issue. Fortunately the phone is still in warranty.
Thanks for all the support.
Heya!
So i just got this Nvidia tablet with blisspop/lollipop or whatever it's called already installed.
Now i've been trying to read through some of the threads on this page but it honestly feels like im reading a different language.
I've noticed the Nvidia power options is gone from the tablet and since im lagging pretty bad often when playing games although not all the time, i'd like to fix this.
I thought the best option would be to increase my cpu usage, do you guys have any guides or tips for me on how i could do that?
Thanks in advance!
honestly, the kernel included in blisspop is plagued with odd behavior.. hangs, audio skips, and weird lag that comes and goes without reason...
some say it works fine for them, but myself and many others have had this issue... so, that is probably your problem.
DreadApex said:
honestly, the kernel included in blisspop is plagued with odd behavior.. hangs, audio skips, and weird lag that comes and goes without reason...
some say it works fine for them, but myself and many others have had this issue... so, that is probably your problem.
Click to expand...
Click to collapse
I understand, is there anything i can install which works better? or am i stuck with the current "kernel" as it's called?
Sorry, i'm not familiar with the contents of blisspop and such.
you can try the official firmware, but if you bought the tablet with blisspop installed on it already... it is probably killswitched... so you need to follow the instructions here or risk breaking your tablet for good.
DreadApex said:
you can try the official firmware, but if you bought the tablet with blisspop installed on it already... it is probably killswitched... so you need to follow the instructions here or risk breaking your tablet for good.
Click to expand...
Click to collapse
I'll check it out!
One last question; if i just use it regularly as i've been doing, will it actually just not work after some time?
Edit: i checked my serial number and it said "Next OTA: ST - yy (urgent)" so im guessing it's killswitched
Cladias said:
I'll check it out!
One last question; if i just use it regularly as i've been doing, will it actually just not work after some time?
Click to expand...
Click to collapse
I'm not sure what you mean... the battery will die if that's what you mean..lol
Cladias said:
Edit: i checked my serial number and it said "Next OTA: ST - yy (urgent)" so im guessing it's killswitched
Click to expand...
Click to collapse
yes, just be sure to remove the ota app as instructed in that post to ensure it won't get delivered.
DreadApex said:
I'm not sure what you mean... the battery will die if that's what you mean..lol
yes, just be sure to remove the ota app as instructed in that post to ensure it won't get delivered.
Click to expand...
Click to collapse
I assumed the Killswitch is something that deactivates my tablet if i dont do anything to fix it, hence why i asked if it wouldn't work after a while if i didn't do anything about it.
I'll try to follow what the thread says. Thanks for the replies!
the killswitch could kill your tablet the instant it connects to the internet.
make sure you remove it BEFORE you do and you won't have any issues from that point on with anything.
So I have this weird scrolling issue, like the one on this video:
Can someone please test if their phone does the same? I will replace the phone if this turns out to be a hardware fault. Thanks!
Hi,
I have the same issue on my OP9. But if I hadn't seen this video, I would never have known there was such a problem. Like in your video, problem exists only in stock launcher.
Dominius said:
Hi,
I have the same issue on my OP9. But if I hadn't seen this video, I would never have known there was such a problem. Like in your video, problem exists only in stock launcher.
Click to expand...
Click to collapse
Alright, thank you! Yes it is a minor issue, but still quite annoying (at least for me and my way of using the device). Hopefully they will fix as it soon, as it seems to be happening only on the base non-pro 9 model.
First thing i do is install NOVA launcher. So never noticed an issue.
nujackk said:
First thing i do is install NOVA launcher. So never noticed an issue.
Click to expand...
Click to collapse
This happenes throughout the device, regardless of the launcher used. Can you please try replicating the steps as shown in the video?
I did didn't notice any problem. But reading the previous post said only occurred in stock launcher which i uninstalled
I've lowered my animations to 0.25 with joneplus tool so that may make a difference as well
nujackk said:
I did didn't notice any problem. But reading the previous post said only occurred in stock launcher which i uninstalled
Click to expand...
Click to collapse
Okay, that's weird. Maybe I'm just too sensitive but scrolling feels off to me because of this.
Also, are you using the preinstalled screen protector?
Nope, didn't come with one. Got phone from t-mobile this time. Using one from Amazon forget which brand
nujackk said:
Nope, didn't come with one. Got phone from t-mobile this time. Using one from Amazon forget which brand
Click to expand...
Click to collapse
Thanks for all the info so far! Just one more thing, could you please test it again, but keep your finger still for at least a second before flicking.
I am really sorry to bother you with this, but I am going to replace the phone, if yours turns out to be ok. I'm just paranoid that you might have missed it because it's so subtle.
In Nova the app drawer is side to side, but no issue there and in trying up and down in couple apps no issue . Even tested keyboard and virtually instant response using exact same keys from video. P0qla no delay at all
nujackk said:
In Nova the app drawer is side to side, but no issue there and in trying up and down in couple apps no issue . Even tested keyboard and virtually instant response using exact same keys from video. P0qla no delay at all
Click to expand...
Click to collapse
Alright, something is wrong with mine then... Or maybe the T-mobile version of the phone doesn't have this bug, since it uses a slightly different software.
Yeah could be. Maybe t-mobile turned down the touch rejection.
Alright, so currently im dealing with some Multitouch issues on my Pixel 4a. The repair place i went to UBREAKIFIX said they'll have to do the whole repair they did preciously again and charge me (because of 2 small dents at the side of the screen). Would not recommend. I wanted to get a poll of everyone with this exact issue Here is some steps to test:
1. Enable Developer Options (Go into build number click however many times and get developers options
2. Go to Developer Options in System settings,
3. Scroll down to Input and enable "Show taps" and "Pointer Location.
4. Put two fingers down and see if multiple pointers are shown (If not, Multi-touch does not work)
Also some other Notes:
Downgrading to Android 10, Makes multitouch work for some reason :/
Also would like to know if you've gotten your phone repaired before.
Any help figuring this whole thing out is appreciated
Can I ask what was the repair they did the first time to fix your touch problem?
hammered58 said:
Can I ask what was the repair they did the first time to fix your touch problem?
Click to expand...
Click to collapse
The first time, it was just a broken screen, had to replace it
fbievan said:
The first time, it was just a broken screen, had to replace it
Click to expand...
Click to collapse
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
fbievan said:
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
Click to expand...
Click to collapse
That's sucks, hard to prove if there right or wrong without putting a known good screen on
hammered58 said:
That's sucks, hard to prove if there right or wrong without putting a known good screen on
Click to expand...
Click to collapse
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
fbievan said:
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
Click to expand...
Click to collapse
I honestly cant say if its the hardware or software, maybe it might be a combination of both? I'm not entirely sure, however downgrading to android 10 from googles flash tool does seem to have it work. I had what i would guess is a full screen replacement from UBREAKIFIX, due to shattering the entire screen. Honestly, spending 140 dollars just to see if it might work is not worth it to me, so I'm really not sure what to do.
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
hammered58 said:
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
Click to expand...
Click to collapse
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
fbievan said:
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
Click to expand...
Click to collapse
idk,, maybe the sensitivity is setup diff
hammered58 said:
idk,, maybe the sensitivity is setup diff
Click to expand...
Click to collapse
After looking for a while seems the entire drivers are different in the kernel. But that is my brief look at. If anyone who knows kernel drivers would like to take a look at it. Would be helpful
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
I'm on stock but rooted. I've been slack so still on October patch. Multi touch working fine. Never had a problem with it.
(Finally updated to December patch and it's still working.)
LionDGem said:
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
Click to expand...
Click to collapse
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
fbievan said:
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
Click to expand...
Click to collapse
Wonder how this actually fixes the issue. Sounds strange.
LionDGem said:
Wonder how this actually fixes the issue. Sounds strange.
Click to expand...
Click to collapse
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
fbievan said:
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
Click to expand...
Click to collapse
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
qqBenji said:
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
Click to expand...
Click to collapse
I have LineageOS 19.1 here. So android 12. i'll try that android 10 approach
I can confirm now that downgrading to Official Google Pixel 4a Stock Rom Android 10 fixed the issue. I try to go back to LOS 20 now and see what happens.
PS: Using internal updater to update to Android 13 broke it again. Taking the long route now.
PPS: That chromium based flash tool is really handy. Would be awesome to have something like that for LineageOS.
PPS: As soon as I install anything above Android 10, multitouch stops working. I'll sell this stupid thing as is (will let te buyer know of course). Its a shame.