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
Related
So we all know that for some reason the youtube app doesnt open after a login, we also know that a simple delete of the youtube.xml in shared preferences lets us once again use youtube...(/data/data/com.google.android.youtube/shared_prefs)
I had a been working on a little script to delete that file every time I closed youtube but realized this would get repetitive. I am wondering is this a B&N problem with the way permissions work and where information is stored...similiar to the inability to run shortcuts. Even if you go in and delete from the .xml file your username information or even delete everything in the file but dont delete the physical file, after trying to open youtube it will once again reset. I have been frustrated by this numerous times...where is that data being stored? Does anyone know...
I can't help other than bumping this, but being able to favorite videos is a big part of my youtube experience and I also find this annoying.
On an unrelated note side loading honeycomb youtube apk is wonderful.
Here is where I fail. I have managed to delve further into the youtube.xml file and figure out what exactly is seeming to cause the problem with permission, but I cannot repackage the apk after editing...because I cant sign it. Any thoughts on a solution to this...also it is possible to extract edit then repackage an apk on the nook itself?
Check out this tool. It handles re-signing the APKs.
http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1
I actually came across that tool about 20 minutes before you replied, as an update. I now have youtube where it will allow me to sign in (I do a full quit using task killer) and then restart it with no problems. The problem occurs when I shut down my nook and bring it back...on some shutdowns it just makes me sign in again, others it does the normal process where it does not open up. I dont understand where this thing is storing my permissions or login data, I have erased and looked at most every bit of code that could have anything to do with data storage...maybe it calls some process built in to the nook that I'm missing.
Oh wow...finally got this running on the stook root. I'm having a few friends test it out to make sure I'm not breaking permissions for other things...I'll send out the apk or explain the steps momentarily.
Awesome! Can't wait to try it out. Is this for Froyo or for Nook rooted?
Just for rooted 1.1 though I see no reason it wouldnt work on rooted 1.01 or 1.00...though I'm running into problems. It seems that I wont be able to release an update to the apk but instead will need to include instructions on how to update your own apk which will automatically make it less doable.
I originally posted this in the E4GT forum, but didn't get any takers. As this is something that is extremely perplexing to me, I decided to take the impatient route and post this here as well.
Searching failed pretty badly, both here and a general Google search.
However, I am perfectly willing to admit the possibility that I wasn't searching for the correct terms.
I can pretty consistently flash new boot animations with CWM. The context of the zip was pretty easy to get a handle on. That being said, I've run into a problem with certain specific sounds being used as the boot sound.
I've renamed them with the appropriate PowerOn.wav name, but some work and some do not.
The ones that don't work show an odd behavior. The boot animation plays fine, the sound that I've selected plays normally, but then the looping part of the boot animation just loops indefinitely.
The phone itself has actually finished booting, since I can unlock it, and can navigate blindly, hearing the appropriate noises. I can power it off by guessing where the buttons are onscreen, but I can't see anything aside from the boot animation.
Changing the power on sound file fixes the problem, but doesn't give me the sound I would like to have for my boot.
The length of the file doesn't seem to matter, some shorter ones work, some longer ones work.
I'm wondering if possibly the encoding of the files may matter, but I can't seem to figure out a difference between what works and what doesn't...
I can post some examples if anyone would deem it helpful.
Thoughts?
Hey. Just got into the world of smartphones with a Galaxy S2 (GT-I9100P), running Samsung's stock ICS (XXLPH). After a fairly smooth rooting of the phone, I did something stupid - I tried to use CWM to install this mod - an NFC enabler. Stupid, because the mod wasn't designed for ICS.
I was fortunate enough to have the enabler 'only' freeze the phone every 5 seconds instead of bricking it. Then I went in through the adb shell and deleted the appropriate apk.
My question is - is the apk the whole of the app? It looks like it, certainly - the phone works like before, no problem. I'm just worried about leaving 'garbage' around it.
I don't expect everyone here to be an expert on this particular mod - but in general, if I am manually uninstalling an app, do I need to worry about anything besides the apk?
If so, where else should I look (again, generally, where do apps tend to change or dump things)? I'd ask the developer, but it seems rude to privately message him, and I can't exactly post in the relevant thread.
No you should be ok. Nothing more needs to be done. Some apps also install data on the sd card which show up in 'My files'. It doesn't affect the phone in any way but if you find anything just delete it. I have mine sort by date so changes show at the top of the list.
Sent from my GT-I9100T
No expert by any means but im really having a hard time wrapping my head around this one. My phone (Blu Life One x2) is rooted (as you can see in the video), i can make changes to it as rooting an android would allude to, but whenever i make a change to system based file, folder permission anything at the root the phone just hard stops and i have to do a hard reboot. I'd love to know whats going on here.
Im trying to follow a tutorial to make my phone ring louder in the video. I get to the media xml, try to change a permission and poof! It also happens if i just open the file and try to edit it. Once i save it, phone does the same thing. No changes committed. Video is a onedrive video. If it gets wonky i'll upload to youtube.
h ttps://1drv.ms/v/s!AlQ2y7AA9o6DjJYlZnmjDFT_zMerJA
anyone have any ideas?
Hey folks,
OK, I'm just a little bit out of my depth here, so here it goes!
This probably sounds dodgy, but it is what it is: my daughter's phone (rooted HTC Desire 816) appears to have been "hacked" by someone at her school - whether its a prank gone wrong or she's a victim of bullying, we don't know and now we're dealing with the fallout.
By hacked what I mean is that the person or persons have somehow managed to find out my daughter's PIN and have then used it to gain access to her phone. Once in, they have turned off the custom lock screen installed (Hi Locker) and turned on the default lock screen and set a PIN which we don't know. Obviously, we're trying to get back into it without wiping it and don't know how to except for trying all 10,000 combinations!
So yeah, does anyone know how I might be able to go about getting back into the phone quicker than trying all 10,000 combos of PINs!?
Like I said, it is a rooted device; I was the one who initially set the phone up for my daughter. So its running TWRP and through TWRP I've been able to do an 'ADB Pull' request and dump the contents of external_sd and sdcard to my laptop so that at least that much data is preserved. I've also backed up the mmssms.db so that hopefully I can restore these databases if needs be. My daughter would like to not have to wipe the phone as she can't remember what other data (if any) might be lost if we do and I said I would try all other avenues before it gets to that.
Anyhow, I thought I would reach out to the community to find out if there is some way that I might be able to disable the lock screen or at least initiate some sort of backup process from the lock screen that would enable us to reset the lock screen. If not: such is life. But, if there is something that could be done, well, that would just be absolutely fantastic.
Thanks in advance folks for your responses and time.
Kind regard,
Dodgy Bob.
Hi folks,
After a bunch of further digging through random blogs and YouTube videos and whatever else, I happened across this site which pointed out a couple of different tricks that hadn't popped up on other sites I had come across. These were:
Safe Mode Option; and
adb shell rm /data/system/gesture.key
Safe Mode Option didn't work for me, because it wasn't the 3rd party lock screen app that was the issue.
However, the gesture.key option did work for me, albeit with a couple of tweaks! Gesture.key wasn't present because the phone is running a newer version of Android, v6.0 (I had forgotten this!), so I had 2 gatekeeper files and 3 db files -and- rather than deleting them, I added .orig to the file names. Once I had done this, I rebooted back into System from Recovery and ta-da, I was back into the phone!
Big thanks to @Helloworld294 for this post here which I found after searching more due to reading this page.
It's all worked out in the end.
Kind regards,
Dodgy Bob