Hi, I've got this terrible problem that I've never been able to resolve on my phone.
From what I remember, the bug has always been there, and I'm now using the cyanogenmod, but the problem is still there.
The screen doesn't turn black, the file stops near the end (if it's a really short file, like 2 seconds, it'll look like it won't play it at all)
If it's a file of 30 seconds, the file will play with 0 problems until it reaches something like 75% of the progess bar, then It'll bug itself, making me hear crappy audio or nothing.
Could you guys please help me? I REALLY don't know what to do, I've searched a lot on Google but I haven't found anything!
Related
Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.
Pics
SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)
Hello!
I hope this forum isn't 100% dead...
I had to take my Kaiser out of my closet because my HD2's screen broke and I can't afford a replacement. I flashed Android to it and I was surprised, how fast does it work on so weak hardware. But my problem is that I installed few apps (Next browser, Heroes 2 port - nevermind it works unplayable, exDialer, ES file explorer, updated all apps already present in ROM...), and I'm using PowerAmp to listen for music. But it simply doesn't work properly. When I turn the screen off, after a few seconds, playback stops. Did anyone suffer the same issue as me? I'm using Scoot's CyanogenMod 6 rom.
Also, I have another problem. Every time I turn on the scree, it goes white for a moment, then it shows some garbage and in the end, it shows everything properly. But it takes a while until it finishes. Maybe there's a cure for it, too?
I've notice that sometimes my photos/vídeos disappear from my cellphone.
At first I noticed with media received from whatssapp and I thout it was an app issue and don't give to much attention to it.
Now I realized that recent media disappear, and then paying more attention I notice that they disappear just after my cellphone suddenly shutdown when running low battery.
Today I had a sad story, I was recording a trial, after that while using Waze my phone just shutdown without showing the logo information "shutting down". When I charged my phone and tryed to send the videos to people in the trial they do not appear. Searching for them I discovered the files still there, but the size now is 0 kB (and I watched some of them before the sudden shutdown)
So the question is, does anyone is facing the same issue? Is there a known solution? And the most important to me, does anyone know how to recover the videos?
Since Android does not appear anymore as a common removable card I can not use anymore tools like "miniTool Power Data Recovery".
Can anyone help me?
Thanks
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
Try a factory reset. Ive had it fix many a strange bug before.
Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
I've had the same problem, running N developer preview 1 listening with wired headphones. I've learned that I just kind of have to wait for it to pass, try force stopping play music, or restart the phone.
Are you streaming your music, or is it downloaded onto your device? I manually copy music onto my phone from my computer, and this is when I've got the issue, as I stream with Spotify fairly often and never have the problem. I've always thought it was just some bug reading all of these crazy 3rd party audio files in the storage.
Hasn't been much of a problem for me... Just jumped at the opportunity to share when I saw this thread. If it bothers you that much, try a full wipe of internal storage and reinstall everything. Cheers! Hope I helped.
It's not saved as one of the ringtone or notification sounds on my phone.
It does not do any type of notification I have already tried notification sniffers and it does not do any type of notification at all.
I kill all apps, turn of the screen, nothing can stop it from playing the entire toon for about 45 seconds.
I have posted on several boards but cant figure it out.
I've attached the audio that I recorded of it playing.
They did tell me to run a bug report directly after it happened which I did. They told me to upload it to battery historian: https://bathist.ef.lc/
But I can't figure out what to do once I upload it or how to parse the information.
audio sound:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
Does the sound play at any specific time or is it at least once a day or something?
Usual practice is to see what your most recent apps were, as one of them may be causing this. You might even check for latest updated apps, because it could be something added by a new feature/update.
If that's not finding an issue, you might boot into safe mode and seeing if the noise stops happening - this would indicate that an app is causing it. Alternatively, maybe uninstalling all other apps is a good place to start. If it goes away, then add apps back (maybe a few at a time, to make it easier) and monitor for when it comes back.
I'm not familiar with that Battery Historian app, but it seems interesting. If you can identify when the sound happened, it should line up with the "audio" events shown in the graph. I assume there's some way to zoom in on that graph, so maybe you can see what happened during that time, and help narrow down a possible app that could be causing this.
thanks so much for your reply.
The sound happens so infrequently, the last time it happened was 2 weeks ago. Sometimes it might happen 3 or 4 times in 1 day. And the phone use and app use are static and have not changed. Same phone use every single day. It's impossible to figure out it seems.
It's so frustrating.
I ran the bug report directly after the sound played so the end of the historian file is when it happened and looking at the "audio" I do see something there that played for 59s which is about right for how long the audio is.
But I can't figure out any info about the audio besides what is on the tooltip.
Maybe someone knows more about this battery historian.
Bug report for who? If you're just throwing out a but report to an app or even the OS, chances are that it will be ignored as irrelevant, unless you can convince the place you're reporting it that this is something they are causing... I'm guessing that report is not going to do what you think it is.
I don't see how battery historian is going to help, so maybe you need to pursue the thread which recommended it. I did a quick search and I don't see how that app will help identify the problem.
One other idea I saw was that maybe a browser tab is generating the noise. Websites can sometimes provide notifications and such, if you allow them to. I never do, but I can imagine that as a source of noise.
In the end, this is likely an app that you have. You just have to remove as many as you can, and see if it goes away. If it doesn't then you can look deeper at your remaining apps. If it does, then the job is easier and you just need to add them back in (if you still want them) until it comes back. Since it's so infrequent, it's going to be difficult to have happen... but I doubt it's an OS-level problem otherwise others would have the same issue.
thanks for your response and I have been trying to do that but it has not worked so far and that is why I am posting here.
Something on my phone is firing this sound and if you are telling me there is no way for me to figure it out from some type of log, then I have to tell you that you are wrong.
Everything that is done on Android there is a record of I just need to figure out how to read this record.
Not everything is always logged with any OS or app. There are settings to set log-levels higher or lower. Most apps set only "warning" or "error" level logs, generally speaking. There are often ways to increase this, but it's not there by default for sure... I wouldn't expect a sound activity to be logged by default as it's not an error.
But, if you know better than me, then I'm sorry I can't be more helpful. I will stay out of it going forward. I would love to hear how you find it, because it's great information for anyone on XDA (and I would certainly like to know as well).