I find them incredibly annoying.
Does anyone know if deleting the video files would cause an error or not? I've found the locations of the shutdown files:
/system/media/audio/ui/Shutdown_128.ogg
/system/media/video/shutdown
I'm hoping the phone would notice that the files aren't there anymore and move on, but I want to make sure my phone will still boot/shutdown if I remove them.
Thoughts?
No offense, but you should probably look and/or search before posting or else the message boards get a lot redundant posts like this one.
Here is what you're looking for: http://forum.xda-developers.com/showthread.php?t=732311
I attempted to change the boot sound. I got the animation working perfectly. But the sound is not working at all now. No sound, nothing.
The FinalThunder.mp3 has been renamed, and the original still works. But the new one doesn't. Anyone got any idea what might be wrong?
I've Checked:
Permissions
File Locations
If the file ACTUALLY has audio
it works in "android emulator"
bumping for great justice. This will not only help me, but hundreds of others who are having the same issues in the theming sections!
bumping again before sleep...come on, someone has to know this.
Does anyone else think that the Xperia Ray shutdown/poweroff sequence is a bit annoying? First, it's too long - who needs to confirm twice that they want to switch off their phone? Then it signs off by vibrating which I find really irritating - I'm a committed vibration hater!
Anyone else share this opinion and done anything to remedy the situation? If so, do let me know.
I'm sure the vibration thing's sorted out easily by removing an .apk file or something somewhere.. My Ray's rooted/locked bootloader/ ICS 4.0.4 btw.
go to general section, this is the development thread, don't open up a new thread just to ask this
This how shut down works on every single Android device I have and I really doubt it can be changed...
Sent from my MB860 using xda premium
Sure it can be changed, I got rid of that (bloody horrible) O2 closedown animation by deleting an .apk file or two from the internal memory. Removing the shutdown vibration should be just as easy.
It's hardcoded in the operating system (probably in services.jar), it's not an apk that you could just delete
Exactly. Any animation can be deleted as it is added by the carrier or manufacturer but the vibration is there in Vanilla Android.
The length will depend on the phone specs, the ROM and the number of process the phone has to shut down (which changes from user to user) so you'll never get anything faster unless Google makes some changes.
On my Atrix running CM7, it's taking 6 to 8 seconds to shut down and the vibration is kind of a an alert saying that it all went fine. Perfect if you shut it down and then put it in your pocket : you know it shut down without having to check it. It's a feature.
Its possible to shutdown with one touch in 1 sec but its like turning off ur PC by pulling out power cable... I would not recommend since OS is saving ur present Settings for Next boot...
If u want to try then check Quickboot app from Play store.. it does the same thing...
That's fine - thanks all for the replies!
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
Hey everyone, I’m posting this to both XDA and the CyanogenMod forums for simplicity’s sake
I recently inherited a Note 3 from my sister who just got the Note 5, so of course I promptly rooted it and flashed CM 12.1
However, I’ve had some problems that I can’t seem to find a fix for, and I’m hoping someone can point me in the right direction.
1) GPS
GPS cannot get a lock. Sometimes it will kinda work sporadically for a second or two, but it’s definitely not the fast, solid Lock that it’s supposed to be. Google Maps Navigation gets close, and I can see my route, but it doesn’t give me the solid Lock that it’s supposed to. I’ve downloaded GPS Status and re-downloaded AGPS data and done the available calibrations but that doesn’t really seem to do anything.
I found this thread regarding the GPS issue, but there seems to be a debate as to whether or not the fix suggested actually works. Haven’t tried it for myself yet but I plan to soon as I can get backups made:
http://forum.cyanogenmod.org/topic/105538-have-they-fixed-gps-on-note-3-hltespr-sprint-yet/
I also found this possible solution over in the Galaxy S4 forums, but I couldn’t figure out how to edit my gps.conf file. I tried with both Astro File Manager and Terminal Emulator but I couldn’t edit the file due to permissions I’m pretty sure. I have some basic Linux knowledge but I’m not sure what the problem is. The usual “just sudo it” method doesn’t seem to work:
http://forum.cyanogenmod.org/topic/108806-gps-not-fixing-with-latest-cm121/
2) Startup/Shutdown Sound
Apparently the Note 3 has a Startup and Shutdown sound. I’ve previously had an S3 and S4 and neither of them had it.
So now CyanogenMod plays my Default Notification Sounds whenever it starts up or shuts down. Which is fine, but there doesn’t seem to be a way to change the sound aside from changing my Default Notification Sound. I like to keep all my sounds different so I don’t like to have the same sound for two different functions. Does anyone know if there’s any possible way to change the Startup and Shutdown sounds?
Thanks in advance for any help!