When I search Google for this problem, very little comes up, although I found one other person (at least) who seems to have the same problem as me and has filed this issue on the Android bugtracker:
http://code.google.com/p/android/issues/detail?id=20650
When I'm driving and running Google Navigate, the backlight turns off after a while and I can barely see the screen. Surely this is a bug, and not by design? When you're navigating you want to see the display clearly. It's such an obvious flaw that I can only assume that most people aren't experiencing it. So I thought I'd ask here; is anyone else getting this problem and/or does anyone know whether it can be fixed without Google updating Navigate? If you're having this problem, please vote for the issue on the code.google.com link above, and maybe Google will fix it.
Just to add, this 'feature' is also being described in various places as 'screen dimming'.
Related
Does anyone know where the issue is with these two items in the code is? I have worked as a web developer many years and would like to take a look if anyone has some immediate direction. (never worked on android roms yet) Or has anyone made any advances on these issues already?
Thanks
Hi, Wizards:
I have a Galaxy Tab GT-P1000 running Overcome 3.3.1. On occasion, when all else seems quiet, the device will suddenly decide to play the /system/media/audio/notifications/12_Tweeters.ogg sound file (sounds something like a bird chirp), and I would like to find the application that causes this sound file to be played. I ran the Log Collector app (v1.1.0) and poured through its output, and that is how I determined which file is being played,
In the latest instance, the log shows:
09-06 08:40:24.230 I/MediaPlayer( 306): The actual path is:/system/media/audio/notifications/12_Tweeters.ogg.
Before that, I can see references to (306) like "KeyguardViewMediator" in the same second. In fact, there are hundreds of references to 306 within parentheses in the log, mostly involving Sensors and PowerManagerService BatteryService. But I don't see a way to trace back to the originator. (Frankly, I also don't have any indication that the '306' is important.)
How would I go about finding the reason that MediaPlayer was kicked off in the first place? (My goal is to find the application that suddenly decides to play this sound file, and to understand why it does so. After all, I'm being notified of something, right? Wouldn't it be swell to understand the reason for the notification, instead of just "Hey!" ?)
I've searched for general information on how to figure out what the Log is trying to tell me, but to no avail for something like this. Is there enough information in the typical Log Collector output to determine this information? If so, where can I read up on how to trace this? If not, then what might I do to trap/identify this?
I appreciate any pointers you may have on this.
delovelady said:
Hi, Wizards:
I have a Galaxy Tab GT-P1000 running Overcome 3.3.1. On occasion, when all else seems quiet, the device will suddenly decide to play the /system/media/audio/notifications/12_Tweeters.ogg sound file (sounds something like a bird chirp), and I would like to find the application that causes this sound file to be played. I ran the Log Collector app (v1.1.0) and poured through its output, and that is how I determined which file is being played,
In the latest instance, the log shows:
09-06 08:40:24.230 I/MediaPlayer( 306): The actual path is:/system/media/audio/notifications/12_Tweeters.ogg.
Before that, I can see references to (306) like "KeyguardViewMediator" in the same second. In fact, there are hundreds of references to 306 within parentheses in the log, mostly involving Sensors and PowerManagerService BatteryService. But I don't see a way to trace back to the originator. (Frankly, I also don't have any indication that the '306' is important.)
How would I go about finding the reason that MediaPlayer was kicked off in the first place? (My goal is to find the application that suddenly decides to play this sound file, and to understand why it does so. After all, I'm being notified of something, right? Wouldn't it be swell to understand the reason for the notification, instead of just "Hey!" ?)
I've searched for general information on how to figure out what the Log is trying to tell me, but to no avail for something like this. Is there enough information in the typical Log Collector output to determine this information? If so, where can I read up on how to trace this? If not, then what might I do to trap/identify this?
I appreciate any pointers you may have on this.
Click to expand...
Click to collapse
Log Collector should give you enough information to solve the problem. I suppose one simple and quick solution you could try is go into /system/media/audio/notifications/12_Tweeters.ogg and just delete the file. If you delete the file, then when it wants to play that sound it won't be able to because it doesn't exist, and then it shouldn't bother you anymore.
shimp208 said:
Log Collector should give you enough information to solve the problem.
Click to expand...
Click to collapse
That's encouraging. Sorry I wasn't clear. Where might I find out how to read the log in such a way?
shimp208 said:
I suppose one simple and quick solution you could try is go into /system/media/audio/notifications/12_Tweeters.ogg and just delete the file. If you delete the file, then when it wants to play that sound it won't be able to because it doesn't exist, and then it shouldn't bother you anymore.
Click to expand...
Click to collapse
Hmmm... to me, that sounds like "If the fire alarm bothers you, just remove the battery." I do appreciate your reply, but that doesn't that sound to me like a good idea since I don't know the cause... I do welcome advice regarding figuring out that cause.
I had a problem with audios starting to play randomly. Googling led to many possible causes.
The only one I remember is the fix that worked for me - simply installing and running once a program available free from the market called DisableAutoPlay.
It disables the feature where plugging headphones in causes auto-playing. Mind you I wasn't doing anything with headphones when my music started randomly, but apparently there can be some intermittent hardware malfunction that makes the phone think you are plugging headphones in (perhaps limited to Samsung phones like mine IIRC... I have an Infuse).
electricpete1 said:
I had a problem with audios starting to play randomly. Googling led to many possible causes.
The only one I remember is the fix that worked for me - simply installing and running once a program available free from the market called DisableAutoPlay.
It disables the feature where plugging headphones in causes auto-playing. Mind you I wasn't doing anything with headphones when my music started randomly, but apparently there can be some intermittent hardware malfunction that makes the phone think you are plugging headphones in (perhaps limited to Samsung phones like mine IIRC... I have an Infuse).
Click to expand...
Click to collapse
Thanks. I will keep that in mind if the time comes that I need to take such action.
I'm sorry I'm apparently expressing my intent so poorly. My goal, to be clear, is to find out WHY the alarm is sounding, not to prevent it. (I reserve the right to want to prevent it in the future, but right now the point remains.)
I will try to track down the author(s) of Log Collector and see where that leads me. If I find out anything useful, I will post back here.
delovelady said:
Thanks. I will keep that in mind if the time comes that I need to take such action.
I'm sorry I'm apparently expressing my intent so poorly. My goal, to be clear, is to find out WHY the alarm is sounding, not to prevent it. (I reserve the right to want to prevent it in the future, but right now the point remains.)
I will try to track down the author(s) of Log Collector and see where that leads me. If I find out anything useful, I will post back here.
Click to expand...
Click to collapse
Id also look into using logcat to try and solve your problem take a look at this guide to reading and writing logcat files.
Reading and Writing Logs in Android
I've been searching the web for a couple of days, without finding any real solution to the problem. From September 2011, Google Maps decided to lump together its volume control with media apps, that used to be separated. I found a huge thread on googleproducts forums, titled "Why is the Google Navigator Volume No Longer Separate - But Now Linked with Media Volume?" where I see that things have never changed, nor Google acknowledged this being a problem.
Now, at the beginning I was confident that a simple solution existed for a rooted phone (Note 3 9005 for me) but, alas, I can't seem to find anything. Am I missing something?
Thank you.
PS
Not able to link the discussion mentioned above, too few messages for me, still.
I suppose there could be two ways to handle this. One would be to have a "per app" volume setting, through some clever Xposed module. The other a "simpler" (don't have a clue) hack on Google Maps itself. I just find strange that there's so little "literature" around, regarding this, as it's a really annoying problem, once it manifests itself in the car.
gorman42 said:
I suppose there could be two ways to handle this. One would be to have a "per app" volume setting, through some clever Xposed module. The other a "simpler" (don't have a clue) hack on Google Maps itself. I just find strange that there's so little "literature" around, regarding this, as it's a really annoying problem, once it manifests itself in the car.
Click to expand...
Click to collapse
Bump.
Bump
Bump...
Bump
Bump. Is this the wrong section, maybe?
apologies for cluttering the place up previously.
To the question:
I bought a used TF201 and it's at 4.4.4 CROMB1 is 11.0-20140930. Kernel is 3.1.10
Best way I can describe the issue is that the screen is flaky. That is, when I attempt, for example, to move an icon from one spot to another it 'dances'. It's difficult to control the position of the icon. Rebooting resolves for a few minutes.
The issue manifests itself in 'settings' also when I scroll up and down on the left side to select something.
Anyone seen this or heard of it? No joy in my search for info on here.
Many thanks up front folks,
Jim
don't you love it
when a newbie fixes his own problem?
A wipe solved it.
There is a long-term bug in the basic Android system that affects the keyboard when autocorrect is used, and I hope someone here can offer some insight and help because it's been driving me nuts for years, over many phones and many versions of Android. Now it's just started happening on my new Sony Xperia X3.
At first, all is well. But then, after a certain amount of typing, you start to experience the Autocorrect Backspace Bug. Symptoms:
If you use autocomplete by selecting one of the suggested words and then press Backspace, no longer is the entire word deleted. Instead, entire words or parts or words are inserted until whatever you were trying to type is complete garbled.
If you press Space before Backspace, the autocompleted word will be repeated in its entirety followed by a space, and then you can delete both words letter by letter without new words or letters being inserted.
If you long-press the text to bring up the CopyAll-Cut-Paste menu and select CopyAll, only the word you were pressing on is selected, rather than all the text.
Clearing the Android cache for all apps and data doesn't help, nor does deleting all the learned autocorrect data. Turning off Autocorrect completely isn't a great solution for me because that also turns off Swype, which I like to use.
I have had this problem with my last 3 Android phones, so it has existed since at least Android Gingerbread. Google searches of this problem have turned up complaints about this bug since Gingerbread, but NOT ONE SOLUTION.
The people who frequent this forum are the smartest anywhere about things Android. Any thoughts????
anyone else experienced this?
Has anyone else here even experienced this bug?
God, yes! This is such a PITA, especially when typing om forums or fb-comment sections..! Please tell me you solved it?!
I recorded the bug to show it better - why is no-one else complaining about this, googling gets me no answers. FYI it happens to all keyboards I've tried, incl Google and Xperia.
Android backspace/autocorrect bug: https://youtu.be/0-x_Q8eWxSE
Solution to backspace bug
Good video!
I solved the problem by switching to a keyboard that has its own autocorrect. Not all do. Many use the built-in autocorrect. I'm using SwiftKey now. It had its own autocorrect.