My HDX is near to useless with quite a big part of the touchscreen not beeing recognized (see picture).
This was drawn "upside down" (power button on top) --> The unrecognized part is on the side without camera.
Seems to be a hardware fault, as it percistently existed troughout my entire updates I made coming from 3.2.1 over 3.2.5 over 4.5.2 and even on CM11 in safestrap v4.
I got it from Amazon Germany.
Should I email them and if they aggree to help me flash this: http://forum.xda-developers.com/kin.../hdx-stock-images-pre-rooted-updates-t2911954 ?
UPDATE: When you think it can't get worse...
I just found out that it is probably not a hardware fault, but rather something with the software. On CM11 I now got like 3 minutes of full touchscreen before it started to randomly freeze again and blocked the same part of the touchscreen as before. As there is nobody else having this problem I have a feeling that it's pretty bad and I can't solve it on my own.
zoyoo said:
My HDX is near to useless with quite a big part of the touchscreen not beeing recognized (see picture).
This was drawn "upside down" (power button on top) --> The unrecognized part is on the side without camera.
Seems to be a hardware fault, as it percistently existed troughout my entire updates I made coming from 3.2.1 over 3.2.5 over 4.5.2 and even on CM11 in safestrap v4.
I got it from Amazon Germany.
Should I email them and if they aggree to help me flash this: http://forum.xda-developers.com/kin.../hdx-stock-images-pre-rooted-updates-t2911954 ?
UPDATE: When you think it can't get worse...
I just found out that it is probably not a hardware fault, but rather something with the software. On CM11 I now got like 3 minutes of full touchscreen before it started to randomly freeze again and blocked the same part of the touchscreen as before. As there is nobody else having this problem I have a feeling that it's pretty bad and I can't solve it on my own.
Click to expand...
Click to collapse
This is almost certainly a hardware problem. Temperature may play a role explaining the short period of full functionality. Amazon will not help you flash an image from XDA or any other 3rd party. Seek an exchange if still in warranty.
Regarding warranty I am pretty unlucky. It's three month over the one year period. I will stick to CM11 as it is less likely to freeze and runs smoother over all. I cant figure out though how to set the CPU gouverneur to performance. It just changes back instanly after I clicked on it.
zoyoo said:
Regarding warranty I am pretty unlucky. It's three month over the one year period. I will stick to CM11 as it is less likely to freeze and runs smoother over all. I cant figure out though how to set the CPU gouverneur to performance. It just changes back instanly after I clicked on it.
Click to expand...
Click to collapse
- Try Kernel Adiutor: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
- If it immediately flips back governor is not supported by rom/kernel
I found ROM Toolbox to be working fine. Seems to be pretty much the same as Kernel Adiutor.
To the touchscreen problem I would now say that it is hard to tell if it is a hard- or software issue. It does not respond correctly in situations you would expect the device getting warm (e.g. watching a movie), but on the other side locking and unlocking the screen often solves the freezes (not the broken touchscreen part though).
Hi. Can you tell me what's the situation with your device right now?
I am still using the stock rom (4.5.5.1) with an unmodified bootloader on the Thor and experiencing the same issues. It does not seem to be a real HW issue as it happens intermittently and I was not able to link it to overheating, CPU overuse, etc. Moreover, there are cases when only parts of the display are not taking taps, and these are not wired regions. E.g. the back button is not working, while the home reacts, regardless of the orientation. Then after some rotation events or standby-awake cycles it gets back to normal for a while.
One of my ideas was to go for CG or the Nexus rom, but your case shows that it can still happen there.
I'd expect now something on the software side, though, at really lower levels. (Kernel / driver hiccups, irq handling issues, etc.) Do you have any idea how to track down what could go wrong?
Related
Hello,
I have an issue with the transformer prime and the tablet has been replaced and the issue occurs also on the new tablet which caused me to dig a bit deeper.
The symptoms:
When I press one location a different location is pressed (all application).
When holding my finger in a single location the screen scrolls like crazy (all applications)
Sometimes presses are not registered.
(rare) I am sometime able to do a zoom in / out with a single finger.
This issue occurs to me after using the tablet for a while (usually CPU & GPU intensive applications accelerate this) and the tablet is placed horizontally and connected to the charger.
The Asus support was not able to solve the problem (3 RMAs + 1 replacement), so digging into the driver code for the digitizer I found that it is sensitive to noise (EMI) caused by the charging circuit and has even a special mode to handle this, however I suspect the the EMI is more than the noise reduction function can handle which causes the issue.
My question to you, is how would one go about to debug the issue (the driver loads a binary blob firmware to the digitizer when the system boots which I am not able to decompile / have the source code).
p.s. the device is currently on its 4th RMA visit per Asus support instructions.
Try using a different charger. Are you using an aftermarket charger ?
ccrazythunder said:
Try using a different charger. Are you using an aftermarket charger ?
Click to expand...
Click to collapse
It happens with the original charger with 1 tablet that has been repaired several times and a brand new replacement tablet.
I think this is a hardware issue in the series although Asus refuses to acknowledge it (same as was in the beginning with the GPS issues), there is even an hint in the digitizer driver code that they are aware of the issue and have even added a mode in order to try and mitigate it (noise reduction mode is activated when the charger is connected, probably due to the added EMI caused by the charging circuit).
I ended up returning it for a full refund which they only agreed after lawsuit papers have been prepared for knowingly selling a defective product and not complying with the warranty (since I got the refund the lawsuit did not proceed).
If you know how to modify drivers, can you invert the x-axis for the touchscreen and compile it up? ;D
Nightpath said:
If you know how to modify drivers, can you invert the x-axis for the touchscreen and compile it up? ;D
Click to expand...
Click to collapse
While that might be fun, and quite annoying (doing it to your own tablet), rooting my device and uploading a custom rom would mean loosing the warranty, however at the price cost of the tablet I would have expected to receive a device without serious defects.
I agree.
I have my tablet rooted, etc. I'd be willing to test it, if you were up to it. It'd just reverse the stock x-axis...if that worked all sorts of people would test it.
Irulu AL101: No Sound, Dicky Auto-Rotate
Greetings.
I had reached a point of near Android-Nirvana with my non-phone 10” off brand (but still pretty nifty) tablet: all of its/my issues had been resolved or accommodated and “we” were actually approaching something akin to productivity. Then, of course, things went bad. Perhaps you can help?
The tablet in question:
Model Number: IRULU AL101
(Currently selling for ~$120 with combo USB keyboard/case & shipping included on ebay, though I bought mine months ago)
Android Version: 4.0.4
Baseband Version: 1.5rc4
Kernel Version: 3.0.8+, Nov 5, 2012
Build Number: crane_al101-eng4.0.4 IMM76D, 20121113 test-keys
The problems:
Auto-Rotate acting oddly.
No sound.
Note: I normally use the tablet in a noisy industrial environment while wearing ear plugs, so I can’t be sure if the sound stopped working the same time the auto-rotate stopped working properly. Earlier this April, I went on a trip and used my tablet as an Internet clock radio, so I KNOW the sound and I THINK the auto-rotate were both working properly then.
The no sound problem is, of course, self explanatory. The auto-rotate problem requires some explanation.
a. When I switch auto-rotate on, auto-rotate switches on. Excellent.
b. When I rotate the tablet, the screen rotates properly. Excellent.
c. If I suspend the tablet (short press on the power switch), the tablet suspend. Excellent.
d. If I turn the tablet back on, the tablet turns on. I am greeted with the tablet locked screen, which rotates properly. Excellent.
e. If I unlock the device, the screen instantly rotates back to the normal landscape position, and the screen will not rotate again. Not excellent.
f. If I inspect the settings, I discover that auto-rotate has become unchecked.
I have done everything a clueless newbie with a computer running a slipshod OS supported by crappie/nonexistent documentation might (e.g., reboot; remove apps; “factory reset”, etc.), but, other than wasting my time and engendering in myself a deep longing for ZDS DOS & CP/M-86, I have accomplished nothing.
Other than taking myself and my tablet to one of Google’s campi and immolating us both in protest, can anyone suggest anything?
Thanks in advance.
MD
Did you ever solve this problem with this tablet? Mine just started doing it. The only other thing I noticed is that the sound will start up if the screen is off, but only once it starts a new music track. Also video playback problems at the same time. I just wondered if you were able to.solve your issue without a factory reset or with a reset. Thankyou for your time.
Dear Bert,
I’m sorry (for both of us), but I never did solve the problem. I went as far as trying to reinitialize the tablet, but the feature that back’s up and restores the firmware (or whatever it’s called) doesn’t work on any Irulu tablet I’ve ever tried (which is two or three).
I eventually just bought another one (and a few spares). I certainly can’t prove anything, but I think installing an app might have corrupted it. I have treated my new tablet like a Windoze computer — i.e., I’ve tried to avoid installing software that can be done without — and thus far all is okay with the replacement unit.
If you have any success, do report back when you have a chance.
Good luck!
MD
Well I have the firmware tools from the board manufacturer, I had recovered this unit from being bricked before. Anyway I loaded a full fresh firmware flash for it formatting the system partition as well. The problem still persists. At the moment my current working theory is power issues internally. For some reason when the screen turns off the sound will return. So I in hooked the backlight and got some static over the speakers. Its almost as if the power is being drained from the sound processor and the tilt sensor causing them to stop functioning. It could also be an issue similar to the trod on xboxes, solder joints under CPU coming undone because of heat. No heatsink or heat spreader on these units. If I can't figure anything else out I may try reflowing the solder. The person this tablet came from lost all paperwork that came with it otherwise I would return it.
If you want recovery mode instructions, firmware and firmware tools let me know. Most of the info I found to help me get that unit back online before was in Chinese. Also Hecate what you do install app wise. These tablets are "rooted" with full system access. Easy to mess up the basic software. These tools should work with all of the irulu tablets. Worst case I do have access to the firmware archive and can get the firmware you might need.
Sorry for rambling here, I have ADHD can you tell.
Sent from my TC970 using Tapatalk 2
Dear Bert,
Thanks for the feedback.
At the time this problem appeared, I made some fairly extensive efforts to restore the tablet, which included obtaining the Chinese utility which is supposed to reformat the tablets internal memory and reinstall the operating system. I confess that I can’t recall all the details of what I did, except that my efforts resulted in a broad and impressive variety of failures.
I think I might still have the software/etc. lying about, so I don’t need to avail myself of your very generous offer. Thanks anyway!
Fortunately, other than this issue, I’ve had no trouble with the tablets (the original or its replacement) whatsoever.
Cordially,
MD
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Do you remember when were the times when the screen was unresponsive?
I've read somewhere that sometimes when the screen is woken up and is under some pressure this will happen, and the only way is to do what you did. It's not uncommon in touchscreen phones though, so I wouldn't worry about it.
The verge app was broken until the most recent app update. Also, the s5 seems to refuse allowing Dashlane's accessibility service from working properly. So no more auto filling passwords for me. Ugh. I hoped rooting might help but it didn't. Now I really can't wait for custom ROMs to start appearing. Samsung, you make great hardware (like amoled displays) but your software sucks. Even the software on my Samsung TV is stupid.
Yes on two out of three!
finotti said:
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Click to expand...
Click to collapse
The unresponsive screen is more than a little issue, it is being reported all over the web, and get's more severe over time. I'm thinking that it is a bad proximity sensor defect, either firmware, hardware or software. Some people are reporting along with myself that sometimes for no apparent reason, the screen will not turn on even though the phone is completely operational! This has happened to me four times now and I am stock with very few apps on my phone, five total games and Pandora. I do use a substitute launcher that I've used for years but I don't believe that would be the issue since others report the same issue with stock launcher.
The pop or skipping you speak of in sound happens to many of us who stream music in our automobiles. It even happens on the note3. The fix is simple for that one though! Turn the screen on. I was told that with many of the streaming software music programs that the phones CPU goes to sleep and does not offer enough processing power to the music program. I stream all day via bluetooth to my Auto's sound system and it will usually start to skip, click or whatever after the phone has been untouched for about twenty minutes. The second I turn the screen on the problem alleviates itself. You can find even more information by googling that one, in fact both of those! The heat one I have not had, both with stock battery and zero lemon high capacity battery. The phone very rarely get's warm. However, when I was using wireless charging it would get warm even after charging was complete but I believe that is a normal event with QI type tech.
It seems touchscreen dont like me this is the 3 or 4th phone ive ever owned with this flaw. Does anyone else have there phone touch itself, pressing on the screen in random places, etc
droidkeyboardfan12 said:
It seems touchscreen dont like me this is the 3 or 4th phone ive ever owned with this flaw. Does anyone else have there phone touch itself, pressing on the screen in random places, etc
Click to expand...
Click to collapse
Ghost touches are caused by either a hardware fault, an incorrectly configured custom kernel, or a bad charger/bad current to your charger.
This means that either:
A: you have incredibly bad luck with hardware (not likely)
B: you've used custom kernels on all of your phones all of which bear the same defect (less likely)
C: you're using the same cheap charger with each phone (God I hope not)
D: your house/powerstrip has bad wiring (most likely)
EDIT:
E: you may have an abnormally strong magnetic field. This happens to some people for no obvious reason, and there's nothing you can really do about it (less likely than anything else I mentioned).
Well i havent been flashing any custom kernels for this phone. I did however finally flash cm11 snapshots and it seems to have gotten better. In fact this phone has so many kernels im not sure where to find them all or what all of them do. I stopped buying motorola phones cause they all screwed up. Im honestly more convinced i probably have too much magnetic field in me lol
droidkeyboardfan12 said:
Well i havent been flashing any custom kernels for this phone. I did however finally flash cm11 snapshots and it seems to have gotten better. In fact this phone has so many kernels im not sure where to find them all or what all of them do. I stopped buying motorola phones cause they all screwed up. Im honestly more convinced i probably have too much magnetic field in me lol
Click to expand...
Click to collapse
It's most likely the wiring in your house, especially if you live kind of out in the country. Next to that, I'd guess your powerstrip.
but it does it when not connected to power
having the same issue myself, it got worse after I flashed a different radio, ever since it has gone nuts. one day the touchscreen stopped working for good, I had to let the cellphone rest for a few days and then it started working again. Not sure what it is, this cellphone has given me so many headaches, I feel like smashing it into a wall.
After I press the power button to turn off the screen and leave it like that for a certain period of time (sometimes several hours, sometimes an hour), the screen won't turn back on and I'm forced to hold the power button to restart the device.
It started doing this half a year ago, I first thought that it was somehow caused by my ROM (Archidroid 3.1.4), but I flashed LineageOS 14.1 last night and the problem still persists.
It seems to happen most often while it's charging, and after rebooting it, the battery is never at 100% percent (despite being plugged in the entire time before the reboot), it usually sits at around 92% or lower than that.
On Archidroid, the battery menu showed that during the period of... it being frozen I guess, only WiFi is on, stuff like cellular data is labeled as not active and the phone never wakes up either. On LineageOS, the battery graph just shows the device during that time period as if it was turned off.
If there's any LED that's been flashing before the device "freezes", it sometimes stops flashing or is permanently on until I reboot the device. For whatever reason, enabling touch to wake and setting it to be permanently active makes the device function for longer before having to be rebooted. Also, at times, the phone works for a day or two perfectly before freezing again. Also, the phone is usually hot when I grab it and try to turn on the screen and see that I can't.
I'm starting to believe that it's a hardware failure, maybe something related to the screen?
The problem is custom roms/kernels in general. Even the stock roms suffer to some extent but not as bad and you can wake the phone up by covering the proximity sensor.
Beamed in by telepathy.
shivadow said:
The problem is custom roms/kernels in general. Even the stock roms suffer to some extent but not as bad and you can wake the phone up by covering the proximity sensor.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hmm, how exactly does the ROM/Kernel cause this issue? I'm curious.
Also, where exactly is the proximity sensor and how do I cover it up? By hand or something?
Thanks.
I'd love to be able to tell you exactly why but I honestly don't know. All I know is I had the exact same issues with custom roms and kernels on my s3 but now it's stock rooted and only has that issue in phone calls.
The proximity sensor is 1 of the 2 dots between the earpiece and the front facing camera lens. Just cover them up for a few seconds with a fat finger or thumb and when you let go the screen "should" jump back into life. If it doesn't then you have to reboot the device.
I think you were halfway there with "hardware bug" but I think it's a "software interfacing with the hardware bug", not necessarily a hardware bug on its own.
Beamed in by telepathy.
shivadow said:
I'd love to be able to tell you exactly why but I honestly don't know. All I know is I had the exact same issues with custom roms and kernels on my s3 but now it's stock rooted and only has that issue in phone calls.
The proximity sensor is 1 of the 2 dots between the earpiece and the front facing camera lens. Just cover them up for a few seconds with a fat finger or thumb and when you let go the screen "should" jump back into life. If it doesn't then you have to reboot the device.
I think you were halfway there with "hardware bug" but I think it's a "software interfacing with the hardware bug", not necessarily a hardware bug on its own.
Beamed in by telepathy.
Click to expand...
Click to collapse
The problem started happening a few months after I flashed Archidroid, so I'm guessing something in the meantime managed to mess it up.
I tried covering the proximity sensor with my thumb, but it didn't work. It didn't even work while the phone was working normally. :/
Is the problem maybe caused by Kernel settings?
Have you changed the cpu clockspeeds?. The minimum the cpu can scale down to is 200mhz. If you haven't changed the cpu clockspeeds then the problem is the same one that I encountered that did my head in for months trying to find a fix, to no avail, so much that it put me off custom roms and kernels completely for any device.
The only "fix" is to use a stock rom/firmware and stop at rooting it, that's all. If you change to another custom rom or kernel all you'll do "is plaster over the cracks".
So your choice is put up with it or go back to stock.
Beamed in by telepathy.
shivadow said:
Have you changed the cpu clockspeeds?. The minimum the cpu can scale down to is 200mhz. If you haven't changed the cpu clockspeeds then the problem is the same one that I encountered that did my head in for months trying to find a fix, to no avail, so much that it put me off custom roms and kernels completely for any device.
The only "fix" is to use a stock rom/firmware and stop at rooting it, that's all. If you change to another custom rom or kernel all you'll do "is plaster over the cracks".
So your choice is put up with it or go back to stock.
Beamed in by telepathy.
Click to expand...
Click to collapse
I've messed with clockspeeds only AFTER I started experiencing the issue, I even tried setting the minimum clockspeed to 1000 MHz to make sure the Kernel doesn't somehow "sleep" because of the low CPU frequency, but it didn't help.
But if that's the case, then I guess I'll just put up with it. I'm way too used to Android 5.1.1 and 7.1 by now to make the change back to Android 4.3. Shame that nothing can be done to fix this though.
Thanks for your help, appreciate it.
No problem, it is definitely the issue I experienced with my s3 that I couldn't solve for months on end. It's not worth chasing shadows.
Underclocking will make the problem worse but eventually you'll get to a point where every single time the phone turns the screen off it'll immediately crash and you'll find it unresponsive, needing a reboot.
I remember conferring with a dev of a certain kernel to attempt to resolve the issue but even the dev was perplexed by it. That's why I say it's a halfy half hardware/software issue.
It's a shame though, the s3 is a good phone even by today's standards but due to the lack of ram it struggles with newer versions of Android. Anything past 4.3 has issues, probably because they're not stock.
Beamed in by telepathy.
shivadow said:
No problem, it is definitely the issue I experienced with my s3 that I couldn't solve for months on end. It's not worth chasing shadows.
Underclocking will make the problem worse but eventually you'll get to a point where every single time the phone turns the screen off it'll immediately crash and you'll find it unresponsive, needing a reboot.
I remember conferring with a dev of a certain kernel to attempt to resolve the issue but even the dev was perplexed by it. That's why I say it's a halfy half hardware/software issue.
It's a shame though, the s3 is a good phone even by today's standards but due to the lack of ram it struggles with newer versions of Android. Anything past 4.3 has issues, probably because they're not stock.
Beamed in by telepathy.
Click to expand...
Click to collapse
I personally never had many problems with 5.1.1 or 7.1.2 ROM's, the 7.1.2 ROM I flashed a few days ago actually made my phone faster.
Unfortunately, as of last night, my phone is officially dead. Left it to charge and when I came back, the screen had millions and millions of colors scattered on it, as if someone smashed it with a hammer. Rebooted, screen turned into this white and grey zig-zag pattern and the only way to shut it down is to remove the battery. Can't boot it into recovery or download mode and my computer does not recognize the phone when I plug it in using USB.
My S3 has served me well for the last 5 years, but I think it's time for me to put it to rest and look for a new phone. Again, thanks for your help, at least now I know that the issue I had was unfixable and now it doesn't even matter anymore
The device is now dead but it is not related. That is now hardware failure of the gpu.
If you're looking for an easily moddable device you should stick with Samsung but get an international variant of whatever model if available. If you want a nice phone that is cheap nowadays go for an htc m9. If you want an outright monster of a device take a look at the new htc's. Sense launcher is just awesome once you get used to it as it makes the phone too easy to navigate.
Beamed in by telepathy.