Database Users

Anyone Notice these 2 Issues? - Sound + Market

It seems the system volume, which I always set to mute keeps going up by it self. I am not sure as to what is causing this.
Also, I don't know why they programmed it that way, or if it is a bug but in the market, if I rotate my screen, the list seems to go back to the top automatically. I would find my self way down in the list only to have to go back down again. I know I can turn off rotation but I like mine on. Good thing 2.2 has the option in the taskbar.

Hmm, either this is a very rare incident for a lot of you or maybe just maybe you guys are too zoned in on Froyo But yes, this problem irks me quite a bit.

My market has the same issue when switching between landscape and portrait. Never noticed it until now. I usually don't switch between views, so not much of an issue for me.

the market has always done that... always.. ever since day one... i hated it even back in 1.0

Touchscreen issue may have found temp fix.

Sorry if this should be posted here but Ive been switching around with all the builds and I have found that with all the builds if I disable auto rotation in system setting I do not get the touchscreen issues ever and Ive been running them for like 3 plus days with heavy texting. However, when I turn it on I get occasional freezing. Just putting this out there so others can try it and see if it works for them too.

Interesting, I've seen other people reporting similar things, going to try it! Thanks!

What is the fix?
Sent from my HTC Desire using XDA App
Edit: didn't read post fully..

Post findings please

sorry i have the auto rotation off since i hate home screen flipping around but i always had the screen freeze problem...

evolutionqy7 said:
sorry i have the auto rotation off since i hate home screen flipping around but i always had the screen freeze problem...
Click to expand...
Click to collapse
Maybe its a rom and build combo plus the auto rotate that makes it work similar to the robot voice

Wow, this one actually worked for me! My screen had stopped registering fast swipes, but I checked this off and now it is! It's even working when I put auto-rotate back on. (It'll probably crap out again, but we'll see).
EDIT: I just noticed that this is the HD2 board :O I have a Sensation. It still worked though. Thanks!

[Q] Phone goes to sleep, doesn't wake up 50% of the time.

Hi all,
I'm running OzDROID 2.0 for my rom, 2.10.50.26 for my radio, and Hyperdroid1.6 for Android. Also TMOUS. I just recently updated my rom from an energy build to this one (wanted a lighter, faster loading WinMo). I've been having a nasty problem with the screen not coming back on when it goes to sleep. The buttons light up when i press them, but the screen stays black. Just today alone, i've had to pull the battery FOUR times. Some days it's ok, some days it's a nightmare. I checked the hyperdroid post for a radio recomendation but couldn't see any. I've tried using SetCPU to adjust clock speeds using profiles for sleeping, etc in hopes that some obscure thing will work. no good. I mean, what if i see bigfoot and want to snap a pic but the screen doesn't turn on?
My only ideas left include:
-Formatting my 16gb SD card. (would like to avoid, but will do if people think it would help. I hate setting stuff back up)
-Getting Hyperdroid1.7. (Havent yet cause 1.6 w/ Cyanogen is pretty F'n awesome, and minus this problem, i LOVE it)
-Updating my radio. (Going to do this anyways as i randomly get the "robot voice" problem. I plan on upgrading to 2.12.50.02_2 unless anyone has better suggestions)
I just wanted to check here to see if anyone has one of those "Ohh, enable <enableable option>, dumbass!" fixes. I'm not that experienced with this phone stuff. If anyone could help I would greatly appreciate it.
Thanks!

Searching is your friend. App tray->Settings->Display->Auto-Rotate to OFF/Auto brightness to OFF. This has been covered bajillions of times, the HD2 builds of Android have problems with rotation and the light sensor causeing the kernel to wig out and BSOD.

Sorry for inconveniencing you. If you had any idea how much time i've spent on here trying to figure it out, you'd understand why I decided to just ask this myself. I've had this problem for a month and am finally just now posting. If I found that anywhere I would have gladly done it. The funny thing is - those two ARE disabled, and have been. I dont like auto-rotate and auto-adjust brightness has always been off.
I even took the time to read the "similar posts" that are recommended after typing in the subject.
Since those two are off and my problem persists, I suppose I should format my SD card and try other stuff. So while that problem may have been covered "a bajillion times" it appears your solution is not the miracle cure and is probably a good reason as to why it's been asked "a bajillion times."

Why is it then when I tell people to search, they instantly peg me as some jackass just trying to pawn them off. This issue, the "black screen of death" or, "my phone wont wake from sleep under android" HAS INDEED been covered many, many times. It's cause by either what I just told you, or the particular kernel that you are running is one that tends to get stuck in the sleep mode and won't let the screen come back on. Seriously 9 times out of 10 the problem is caused by auto rotate or auto brightness.

Ashasaur is right but also none of the android versions are very stable anyway and eventually you will face this problem on all of them some sooner than others but they will eventually crash in one way or another
Sent from my PC36100 using XDA App

ashasaur said:
Why is it then when I tell people to search, they instantly peg me as some jackass just trying to pawn them off. This issue, the "black screen of death" or, "my phone wont wake from sleep under android" HAS INDEED been covered many, many times. It's cause by either what I just told you, or the particular kernel that you are running is one that tends to get stuck in the sleep mode and won't let the screen come back on. Seriously 9 times out of 10 the problem is caused by auto rotate or auto brightness.
Click to expand...
Click to collapse
I don't doubt that, but when you reply to someone asking for help with a tone as if they are retarded, don't expect them to buy you flowers. Sorry this has been asked so many times but I feel i put good time into researching this problem and didn't see a problem asking a Question on a QUESTION and answer forum. Like i said, sorry i inconvenienced you and I do appreciate your response, however you did come across as a jackass. I understand you probably deal with a lot of crap as a forum mod, but I didn't post this intending to ruin your day. You can see my post count and gather from it that I don't spend days posting pointless questions. If I came across a solution that worked, this post wouldn't exist.

Try a different radio(2.11.50.20) seems to be doing good for me, also try copying your files to a better SD card. And there is a tab under Setting>Home>>Items that says Home Timeout: 4 Hrs... try unchecking that box. I am new to the HD2 also and trying to tweak it just right so it stops turning off in the middle of the night and making me late for work cause no alarm lol

Fix for Nexus 7 2013 (flo) Touchscreen Glitches

For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.

Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.

Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.

yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013

Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia

pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.

Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.

can anyone provide a flashable patch to try? Thanks

This problem is starting to annoy me really badly D:

I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.

This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5

Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133

Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.

H918 Compass Problems

I am relatively new to this device, coming from Samsung. So different hardware, newer Android. Trying to work through everything. The phone is rooted and I have been making some mods including Xposed.
My latest problem is that the compass seems to be stuck pointing North (at least on some apps). This affects GPS Status and HereWeGo, both of which I have used for years now without problems. Interestingly, this does not seem to affect GPS Test app which I have also used for years.
I have seen a few posting elsewhere mentioning this same problem. Those were for Verizon models, if I recall. But even those posting said it happened before rooting, etc.
Anyone have any suggestions? Thanks!

Try this?:
Another method I've used is to lay the phone on a flat surface face up and rotate it slowly 3-5 times clockwise and counterclockwise. Then do the same with it face down (on a cloth to avoid scratching).
I've only had to do this when I noticed my magnetic sensor picking up a false reading (I use a sensor reading to launch a Tasker profile when it reaches a certain level).
Good luck.

pistacios said:
Try this?:
Another method I've used is to lay the phone on a flat surface face up and rotate it slowly 3-5 times clockwise and counterclockwise. Then do the same with it face down (on a cloth to avoid scratching).
I've only had to do this when I noticed my magnetic sensor picking up a false reading (I use a sensor reading to launch a Tasker profile when it reaches a certain level).
Good luck.
Click to expand...
Click to collapse
Sorry, should have mentioned that I did all the calibration stuff. It is as if the nav apps do not see there is a compass available. On my old phone, for example, Here Navigation shows a compass icon. On the LG V20 it does not. Cheers

whitedavidp said:
Sorry, should have mentioned that I did all the calibration stuff. It is as if the nav apps do not see there is a compass available. On my old phone, for example, Here Navigation shows a compass icon. On the LG V20 it does not. Cheers
Click to expand...
Click to collapse
I know this sounds stupidly simple and you have prolly already done it but there seems to be a bug in my H918 where sometimes my phone doesn't detect certain sensors like proximity and accelerometer hence no compass and screen won't turn off during a call also can't use phone in landscape since it can't detect when phone is sideways but basically the only solution I've found is to just reboot phone and it solves it. It does it very rarely but figured I'd suggest it just in case.
Also can't remember if you said in OP but does this happen without Xposed? Xposed had quite a few bugs still and it's suggested to remove entirely when troubleshooting issues.

KUSOsan said:
I know this sounds stupidly simple and you have prolly already done it but there seems to be a bug in my H918 where sometimes my phone doesn't detect certain sensors like proximity and accelerometer hence no compass and screen won't turn off during a call also can't use phone in landscape since it can't detect when phone is sideways but basically the only solution I've found is to just reboot phone and it solves it. It does it very rarely but figured I'd suggest it just in case.
Also can't remember if you said in OP but does this happen without Xposed? Xposed had quite a few bugs still and it's suggested to remove entirely when troubleshooting issues.
Click to expand...
Click to collapse
Hi and thanks. I am not sure of other sensors but if true, that makes things even worse. I do notice, however, that after several reboots, the compass is back and working again. Obviously, rebooting is NOT a solution for most folks. I am in the process of removing xposed to see if that has any impact. Cheers!

whitedavidp said:
Hi and thanks. I am not sure of other sensors but if true, that makes things even worse. I do notice, however, that after several reboots, the compass is back and working again. Obviously, rebooting is NOT a solution for most folks. I am in the process of removing xposed to see if that has any impact. Cheers!
Click to expand...
Click to collapse
When it happens test to see if you can rotate your phone into landscape mode. Mine rarely happens for me and it only happens upon rebooting. It won't just happen while the phone is on