Is there a way to remove the "honking" sound of the low battery message? I dont mind getting the message, but the sound every minute drives me crazy. Most solutions offered are in the way of removing / renaming lowbattery.ogg in the system folder, but I've not rooted my device (yet)
Related
Just after I power on my phone it makes a loud, annoying noise like: "beep-beep beep-beep beep-beep beep-beep"
It started when I set a custom ringtone and notification sound.
The only cause I can think of is that maybe the phone is trying to play my custom sounds files before they have been scanned by the media scanner, which is resulting in a system notification sound being played instead.
Is that likely to be the case?
My custom sounds are stored in: /mnt/sdcard/media/audio/notifications and /mnt/sdcard/media/audio/ringtones
Thanks.
Delete or move your custom sounds to test your theory .
No mention of firmware .
jje
Sorry, I was sort of seeing if anyone had a similar problem first. Anyway:
Firmware: 2.2.1
Baseband: I9000XXJPY
Build: FROYO.XXJPY
(Not rooted)
I think I am meant to get Gingerbread any day now, and I plan to root after that - so maybe one of those will fix it.
I think I am meant to get Gingerbread any day now,
Dusty Springfield .
Wishing and a Hoping .
What I noticed on mine is this only happens when there is a voice mail left when phone was off. I get this annoying, almost non-stop beeping when the phone boots up, and about the only way to stop it is too check notifications asap. I have no tone that sounds like this beeping, and have no clue why it does this on boot. I thought it was stock ROM issues, but I have flashed auxora and trigger 3.2, and get the same annoying beeping. It is only when there is a voice mail in the notifications, when booting up phone.
Thanks jman!
I had the same problem, hours of searching 'android boot alarm' and endless variations on google found nothing on this. I googled 'android beeping at boot', found this thread and you were 100% correct. I cleared my voicemail and no more beeps! Seems like an odd bug, anyone know a way to prevent this from happening any further? I was minutes away from a hard reset before I found your advice. Thanks!
Same here on I9000B Froyo 2.2 JPA
I hate this beep. Its so loud.
Recently and suddenly, my media scanner seems to be very messed up. Whether triggered from a file manager, or simply booting, it never gets past 0% of the internal storage. After about 10 minutes, my user memory is completely full, and I start getting errors about the database being full, telling me to delete apps. I also can no longer receive any text messages when this happens due to the memory being full. If I go to the list of installed apps through the Settings menu and choose Media Storage, I see that it is using up almost 100MB of my ~130MB of user data. I can choose force close and then clear data, and the phone is back to normal (until the media scanner is triggered again).
I don't want to disable the media scanner, because I use stock apps that rely on it (such as Gallery). I've already scanned and checked my phone's memory for errors, as well as cleared cache/dalvik cache and factory reset. My ROM/kernel/etc. are in my signature.
I had a similar problem a little while ago and it turned out that a corupt video file that I had saved to my phone was causing the media scanner to be stuck at 0%.
Try removing any recent (or all) media files and see if that helps. Then all you have to do is figure out which one(s) was causing the problem.
Sent from my Cappy.
DaveyBB said:
I had a similar problem a little while ago and it turned out that a corupt video file that I had saved to my phone was causing the media scanner to be stuck at 0%.
Try removing any recent (or all) media files and see if that helps. Then all you have to do is figure out which one(s) was causing the problem.
Sent from my Cappy.
Click to expand...
Click to collapse
You were spot on. There were 4 video files on my phone's memory that seemed to be causing the issue. Interestingly enough, I couldn't find anything wrong with the videos--they were standard DIVX 5.1 vids and they play fine on both my computer and phone (although the file needs to be opened through a file manager or player that doesn't rely on the media scanner). None of my other videos trigger this issue, so I guess I'm stuck with re-encoding these 4 and taking a quality hit, even though I wanted to avoid that.
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!
I seem to have been bitten by whatever it is that's causing Note 8s to freeze. In my case, it seems to freeze when idle - case closed, always-on display showing a clock. Sometimes the digital clock - just stopped; the last time, the analog clock with the second hand ticking, but an otherwise unresponsive phone.
It seems like this is happening to other people, in a variety of other applications - and the only advice anybody is giving is to see what happens in safe mode, then uninstall applications one-by-one. All of which seems rather time-consuming, and counter-intuitive -- if a single App is freezing the system, that suggests on o/s or hardware issue -- the o/s should be isolating the rest of the system from app misbehavior.
Which leads me to wonder how one might track down what's actually going on. If this were one of our servers, I'd crank up logging and look at crash logs. But... those options don't seem to be available without rooting the phone. (Why does Google insist on making syslogs unreadable by normal users - that puts a big crimp in the ability to do any kind of real trouble diagnosis.)
Any suggestions on how to do crash analysis? Any tools that someone can recommend?
Any insight on the matter?
I have not had this problem, so I would not know how to tackle all down to pinpoint the exact culprit, but I would start by controling what apps I dont want to run in background, in maintenance>battery>always sleeping, I put all the apps I dont need to be in always running state, I would also try to unistall or freeze apps I installed just before the problem began, if you have bk disabler this is a rather easy process, as you can batch-disable/enable apps, in the end it is a trial-error exercise
You can use logcat extreme, Catlog or somthing similiar from playstore. But you need some knowless to see wat happend and root. Perhaps you can pull the log file without root to your computer with ADB.
Sounds like impending motherboard failure. My wife's S7 Edge started doing the same thing then one day it just wouldn't start up at all.
Common thing for Samsung phones unfortunately .... and if you're out of warranty they won't repair without a charge.
Ever since I have had this handset I am not notified when I get a call on WhatsApp.
On my old OnePlus, if someone rang it would wake up my screen and in full screen.
I have my phone on silent usually but still used to get the full alert in my old phone. On this phone, I have to unlock the phone and click in the top bar to see someone is calling me.
Ive fiddled with notifications and alerts but no joy.
Any ideas?
Application such as CCleaner can supress application notifications, if you have used it, try removing it from your Device. You can also try resetting notifications to default to fix this.