Several months ago my old trusted Galaxy Tab 10.1 Z(Google IO) developed a strange problem. I will not be able to tap on certain buttons or select list items (for example in Settings). Not all buttons/items but some. Since that tab was pretty much trashed by my 10 yo I did the factory reset/cache clean but the problem remained.
Finally I got to rooting the tab, cleaned dalvik and regular cache and installed CM 10.2.
But the problem remains so it is really low level, not the OS. Is it hardware problem or can I try something else as far as resetting or installing some packages here?
Work around for me is to change tablet orientation and going from landscape to portrait I get the button/item back.
I also noticed that while typing tapping on the key sometimes produces multiple strokes and sometimes two adjacent keys are tapped (very frustrating to enter any sort of password)
Is there a life left in the device or should I just toss it to the garbage can? Having my Nexus7 bricked recently does not help either so any suggestions will be greatly appreciated
Related
My SGS2 (original AT&T version) has started rebooting randomly once every 3 or so days. It doesn't appear to be triggered by any single thing or event. The last time it happened was when I was opening the Market. The device rebooted back to the Samsung Galaxy S II boot screen.
I've been pretty careful with the phone (only installed trustworthy looking apps, etc). The phone never rebooted in the first 30 days of ownership. Sometime after that it started rebooting with increasing frequency.
Has anyone else run into this problem?
I also had this issue. I returned my phone for another one. I havent had the issue on the new phone but I am crossing my fingers that it doesnt start doing it again on this new device.
Thanks for the input. I had an Atrix that also exhibited this problem after 3 weeks of use. Based on the similarities, I figured it must be something in common on both devices.
At first I tried removing the microSD card I had installed (same one I used in both devices). I still had reboot issues after removing the microSD so it probably wasn't the source of the problems.
I finally realized it was the Dolphin HD browser that was always 'involved' in the reboots. I noticed that I could sometimes trigger a reboot by exiting the browser. The device would stop responding and then reboot after a small timeout. Sometimes the reboots would happen after opening another app, but it was always preceded by exiting Dolphin HD.
I found a thread in the international SGS2 forums that talks about this issue: http://forum.xda-developers.com/showthread.php?t=1321612. It seems that it doesn't affect everyone, so it may be just be some combination of settings / installed apps that triggers the reboots.
For now I've uninstalled Dolphin HD and am using the stock browser. I'm going to use the stock browser for a while and see if removing Dolphin HD fixes the issues.
EDIT: To clarify, this only appears to happen if I 'Exit' the browser. Leaving it running in the background doesn't appear to cause reboot issues, which may be why I didn't run into this issue until now.
That looks really strange, dolphin never gave me any issues. However you can try using opera browser that is my main browser and supports all the features.
Soft reboot (back to bootanimation/homescreen) or hard reboot (back to Samsung screen)?
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Soft reboot (back to bootanimation/homescreen) or hard reboot (back to Samsung screen)?
Click to expand...
Click to collapse
It automatically reboots back to the Samsung Galaxy S II screen. It then proceeds to go through the AT&T boot animation and finally ends up at the home screen. I assume this would mean it's a hard reboot?
I haven't had any reboot issues since I uninstalled Dolphin HD. I'm not sure if it's truly caused by Dolphin so I'm going to try a few more days without Dolphin before reinstalling it.
As a side note, I noticed some other issues which may or may not be related. These occur even with Dolphin uninstalled.
- Menu button sometimes not responding on the homescreen unless I go to 'Applications' and go back to the homescreen. Once I enter / exit the Applications screen the homescreen menu button will work again. Issue seems to be related to enabling/disabling the GPS from the notification bar, but I haven't reliably reproduced the issue.
- GPS not locking for long periods of time, even though it shows 6+ satellites in view. Sometimes it will lock within 10 seconds. My guess is some sort of AGPS download problem (maybe related to how supl is set to use wap.cingular?). A quick search on Google reveals a number of people suffering the same issue on the AT&T SGS2. All posts also indicate that it worked fine for 5+ weeks before GPS issues started to show up.
I'm trying to hold off on resetting my device back to factory defaults. I want to track down the problem instead of just assuming it was some bug that won't happen again. Based on the international forum posts, the Dolphin HD issue will come back eventually even with a reset.
Thanks again for all the input and help!
Yup that's a hard reboot. An app shouldn't be able to cause a hard reboot like this, but it is not possible to debug. Stock kernels don't have ramconsole for crash debugging.
Anyone else have issues with their accelerometer being off. I was trying to play temple run and noticed I had to hold it at an angle for the player to stay in the middle of the screen. Then I loaded up bubble level and it shows it being 5 degrees off. I tried to calibrate it from the screen menu and a factory reset neither of which helped. Should I send to Samsung for repairs?
Hmm, no clue. Have you tried Googling "how to calibrate android accelerometer" or similar?
Sent using Tapatalk
Me too
Man, that's so weird. I had almost the same problem on the same day. Suddenly, my player's accelerometer freaked out. The x axis keeps showing -9 at horizontal position. I have tried calibrating it many times and also tried lots of wipes and even 2 flashes using odin and nothing seems to solve the problem.
My player was bought 2 months ago in Brazil and I have never let it fall or suffer any kind of physical shock. Now I don't know even how to send for repair cause I only have rooted roms to flash on it and support may discover custom roms through CWM recovery on boot.
I'm still pretty sure it's not hardware malfunction. Something has happened and I can't find out how to reset sensors the hard way.
Strange that happened to us on the same day (at least, with me was on 21st).
I'll keep searching for a solution. It's horrible to use the player with this issue. (Not to say, almost impossible.)
Best regards.
I have found this and it seems to work for many ppl. I'll try it later, when I get back home (I'm at work).
First, navigate to /data/system folder and then rename or delete ms3c_yamaha.cfg
Later (you need to have your phone rooted), try this at the terminal:
adb shell
su
/system/bin/sensorcalibutil_yamaha
then place your phone horizontally and still and press enter.
Finally, run the Horizontal Calibration from the Display settings and then reboot.
Really hope it helps and work.
I tried everything I could
So, I got back home and started trying many things I saw on the web.
I reflashed again, using odin, different roms (now I'm keeping Eryigit-GB-2.3.6 G70ZCKPA Galaxy Player 5.0 For USA and INT (Rls:3.5) with rotation off).
I also tried what I have posted before and it didn't work, actually I found 2 files similar to the ones posted before: One is caled sensorlib_yamaha_test.so and the other is sensorlibconfig.so (not pretty sure about the name of the second file).
What happened during my attempts was that: before, the X sensor had the problem (value -9 with the cellphone laid on a desk, at horizontal position) and now, surprisingly, the X sensor is OK and now the Y sensor has the failure.
Using the HORIZONTAL CALIBRATION in SAMSUNG 2.3.6 (or 2.3.5, whatever), the ball only stays in the middle of the screen if I keep my phone in vertical position - upside (cause of the Y axis). Even if I rotate the tab in every direction possible, the ball never goes UP, so it only keeps with negative values and never positive ones.
BUT If I shake the phone, not so hard and not so soft, I see the ball of the calibration software moving on all directions. But when I manage to do it softly (as we do with normal use), the ball never goes up.
I have downloaded many sensor programs to test the calibration and after trying about 20 programs, ONLY ONE have showed the exact values as if the accelerometer was normal, but the calibration of the program did not affect the accelerometer on the system and other programs.
So, this is it, of course I won´t give up and try as many things as I can. Here in Brazil we have a saying that is: I'm Brazilian and I never give up.
P.S. I hope someone reads this and give me ideas. hehe
Thanks in advance.
Have a nice day u all.
Great news - a solution
GREAT NEWS - I HAVE SOLVED IT
Ok, after lots of attempts here is what I did.
I have downloaded android Froyo firmware from a Korean website (its on a thread of android development from galaxy player). Then I flashed it with ODIN and when it turned on, at first it was discalibrated the same way (Y axis only showing from 0 to -9).
I turned the player OFF and then turned it ON holding vol + button to enter in stock recovery mode. In recovery mode I wiped cache and data. Then I tried to calibrate again, with my device upside down and then voila.
Of course it was sort of a luck, but I had to try everything my mind could guess.
After all, I think that maybe It wasn't necessary to flash other roms (but it would be impossible to solve it using ICS due to a lack of calibrator - without having to use terminal / for curious noobies like me).
Then, I always tried to calibrate my tab laying it in horizontal position and that is the why I never got any satisfactory results. When I tried the calibration with the tab in 'incorrect' positions, the problem was solved. I guess, the calibration program tried to compensate the wrong results cause of the vertical position and then it calibrated itself.
Hope this helps someone someday. (But I really hope you won't have this kind of problem. It's frustrating.
Any device you have, if you have accelerometer problems, you should try this idea: wipe data and cache, and the first calibration you do, do it with your device turned to the side that has the wrong value or to the oposite side. This worked for me.
Best Regards,
Very happy Zilian28.
go to settings>display>horizontal calibration lay it on a flat surface and calibrate it
Sent from my GT-I9000 using XDA
Hey guys
My Galaxy Tab 10.1 is giving me a hard time since a few weeks.
I run the CM 10.1 nightlies on the device and have the following issue:
The touchscreen does not react to my finger properly. Sometimes it works, but then doesn't react anymore. I then press the power button, to send it into sleep mode, then press it again to wake up. the device reacts then like 99% of the time to unlock it. but after that its just a pain in the a**. As far as I can remember, I did not change the ROM when this happened, but since then I tried dozens of different nightly versions, even ones that I know they worked before.
The strange thing is, that it seems to be dependent on the position sensor, because when the tablet is on a flat surface, and is not moved, it works the best. Not 100% but like 80% of the time. But when I hold it in an upright position, or just in my hands, not flat on a table or something, it reacts to like 5% of my tries...
I have been searching on xda and on google about that problem, the most matching one was a driver issue that occurs after like a minute or when a graphic intense app has loaded. They provided a kernel fix, which just made my tab boot into infinity and never reaches the lock screen. after factory reset it boots again, but the problem still exists.
hope somebody can help, because I love my Tab and I can just not accept the fact that it could be a HW issue, since it works 99% of the time on the logon screen, and due to the fact of the position sensor being involved...
thanks in advance! please make me happy again!
@shr00my
Let me ask you this..Does this problem occur in all apps or just you're browser...?
Also..when you flash a new rom..I assume you wipe data/cache/dalvik cache...but do you go in and format system( only system )...you might have something left over from a bad flash that is causing problems..
Hi Gil81
Thanks for your answer! Yes that happens everywhere, in the android menu, homescreen, inside games, video player etc...
Yes i always wipe the caches and data. But I also tried various combinations with different nightlies and wipe scenarios.
Could you tell me a good different rim that is on android 4.2 and not CM based so I could try to flash that and see what happens.
Sent from my GT-I9195 using Tapatalk 4
Looks like the problem is deeper than i thought...
I installed the latest cm10.2 build from the forum here, full wipe cache/dalvik/everything except SD mount, before and after installation.
when coming back to the recovery to install the gapps that I forgot to download, I realized, that i also had issues with the touchscreen in the recovery menu...
I also installed the Kernel (kernel_p4wifi-cm-10.2-20130903-0100-exp.zip) that was provided on the goo.im directory http://goo.im/devs/loosethisskin/p4wifi/cm-10.2
I also experienced some ghost touch issues with the "back" button... Not sure yet if it was because of a specific touching of the frame or an angle of the tabled when lying on my back, holding the tablet in face down. (since I experienced strange behaviour depending on the position sensor)
My brother inlaw won some cheap (he won it in a vending machine ) Android tablet (7") where you turn it on, you get a splash screen (Tablet PC, Keep Moving Forward) with some animation on that text, then the tablet reboots. Every now and then I have gotten to what seems to be the main screen (like maybe 2 or 3 times) but as soon as you touch the screen it reboots OR locks up
I know jack about Android but told him I would take a look. I assume a hardware problem or maybe something corrupt in the software. I have been able to boot into what I will call the root menu. I have tired clearing the user cache as well as a factory reset. No help.
I am thinking it is a hardware issue but it would seem worth reinstalling the software (4.4.4). I have not had much luck figuring out if I can do this (everything I seem to find is on updating the OS not reinstalling or flashing), where to get the files/rom or how to do this. Any direction would be appreciated
I honestly don't know where to post this so I'm going to post it under "General" in hopes that someone far smarter than me can help (!)!...
ScreenShot:
https://drive.google.com/open?id=0Bx8wdr_asZMFZXE1dGFWSnZ2NmM
I've had the following issue for the past 30 days (at first I thought it was some glitch that caused the UI to crash when phoning-home to Cyanogenmod for updates). It SEEMS to have happened right when I first started screwing around with TitaniumBU... that may be a total coincidence, also...
The phone works just fine but will suddenly start showing things in Landscape instead of Portrait (and vise-versa). After I reboot the phone boots to a black screen with just the status bar at the top (showing the time, wifi, etc...) with absolutely NOTHING ELSE except for what appears to be a "back" arrow at the bottom of the screen (that does nothing when pressed).
WTH?! Please. Because I've tried everything (to include wiping internal and ext-SD). :crying: I have, of course, searched other forums but "Android UI Crashing" returns a ton of unrelated results...
:cyclops:I'm still having this issue so I'm gonna bump this thread... Any help is much-appreciated!:cyclops:
I'd wipe the whole internal storage (including ROM) and reinstall the ROM.
Dude - WAY ahead of ya - already did. To the extent that I accidentally soft-bricked the stupid phone!
We all know, as engineers and troubleshooters, that the first step to solving a problem is duplicating it.... and I cannot seem to consistently duplicate the problem! And the crux of it is that this started at the end of December when I was bored around the holidays and playing with my phone (making several different changes).
Obviously I'm not restoring anything from a previous backup... I've even blown away my backed-up App settings in my google account... Formatted Internal and External... Installed latest OS and GApps...
Gun to my head; if I had to guess I'd say that it has something to do with the "System Profiles" feature... I started using it to disable my Lock Screen whenever it detected my home wifi, and to return to the System Default (with the Lock Screen enabled) whenever it no longer detected my home wifi... Because I swear that the crashed-phone looks the same as the screen where you enter your PIN with the addition of the status bar at the top...
The issue has to do with System Profiles to use wifi-detection for toggling the lock screen. Not sure what it is about this that causes the issue, but that was the cause.