I'm running ICS in my GT7300. I have already silenced the booth animation sound by renaming the ong to bak. But how can I kill the samsung animation completely? I have used other rooted tools to replace or kill the animation, but failed. Advice please?
Problem partly solved
I can now kill the animation by digging in the following thread:
http://forum.xda-developers.com/showthread.php?t=1425942ut
But I still would appreciate if someone can tell me how to replace a new boothanimation.zip file.
Related
Can anyone post up the clock API that comes on fascinate...like the alarm app.
com.sec.android.app.clockpackage.ClockPackage would be the answer you're looking for. This is the stock clock app, and upon opening it defaults to the alarm page. Heh, you making your own clock too?
yessir, ty
App not installed messege!
Thanks a lot! I've been looking for this app for a while. I accidentaly deleted this app after I rooted my new phone for the first time in my life (big mistake). I was able to re-install other pre-installed apps that i deleted accidentaly. However, for some reason, I can NOT install the clock apk and the Info Alarm apk. Im getting a "Application not Installed" messege when i try to install them!!
I've search the web for 3 hours and I found nothing! what's wrong with my phone? some people said that I might have those apps already installed on the phone. But I looked for them, and they are not installed on the phone. Dont know what else to do.
I need some help!
Just grab it out of ROM manager. SonofSkywalker's
blackhole ROM has it as a standalone option that you can simply flash onto any deodexed rom. Also, learn to use google modifiers.
I am having the sound issue where sometimes I lose sound due to some unknown issue. In Linux I can usually restart the sound process by running
alsa-utils restart
A find on that does find an alsa folder as /system/usr/shared/alsa with shows the pcm file but whats the command in Android to try and restart it manually if there is no alsa-utils. I shouldn't have to reboot to get it restarted and it would be nice to create a shortcut to a script that would run when I lose sound.
I know some people have said it was a fault with some Nooks that needed returning, but I'm under the suspicion its something else causing it. Any suggestions?
Xerxes910 said:
I am having the sound issue where sometimes I lose sound due to some unknown issue. In Linux I can usually restart the sound process by running
alsa-utils restart
A find on that does find an alsa folder as /system/usr/shared/alsa with shows the pcm file but whats the command in Android to try and restart it manually if there is no alsa-utils. I shouldn't have to reboot to get it restarted and it would be nice to create a shortcut to a script that would run when I lose sound.
I know some people have said it was a fault with some Nooks that needed returning, but I'm under the suspicion its something else causing it. Any suggestions?
Click to expand...
Click to collapse
It has been reported that 1.1.0 fixes the No sound after sleep issue.
Is there an autonooter for 1.1.0? I didn't think there was? Any update now would mess up my rooting of it. I'm also having intermittent reboots. Anyone seen that?
Xerxes910 said:
Is there an autonooter for 1.1.0? I didn't think there was? Any update now would mess up my rooting of it. I'm also having intermittent reboots. Anyone seen that?
Click to expand...
Click to collapse
Are you on 1.01? If so, you might want to get ROM Manager from the market and install Clockwork recovery using Rom Manager. That way you have recovery if something goes south.
There is no current AutoNooter for 1.1. There are some ROM updates to rooted 1.1 but read the full thread so you know the problems if any before you try a 1.1 ROM.
If you don't want to update beyond 1.01 now use the SCRIPT solution to block the OTA altho reports say the OTA won't run on a rooted NC. Hope this helps.
So I took my Nook in to possible exchange it because some people said it was possibly a bad batch. I wiped it and went back to the stock image and when I took it in I was informed there were none ANYWHERE in the Phoenix valley. So something is definitely up. The person there said they are going to announce their own market! LAME! Give me a Froyo or Gingerbread update! Anyway the dude said I had to update to 1.1.0 to fix the problem and now I have to go down that rooting experience. <SIGH>
1.10 does indeed fix the audio problem.
However I have yet to find a rooted 1.10 image that has worked. Last time I tried (yesterday) gmail wouldn't work, market refused to download and my nook reported corruption and forced a erase & deregister / clear data upon itself...
Hey all,
Very, very new to the forums (and I'm putting this here as I can't seem to add to the Dev forum thread) but I just wanted to pop on and report a critical bug I found after installing Salty Bean 4.2.1 (02/01/13 build).
I installed an app called LBE Privacy Guard onto my sgh-i896, gave it SU permissions and immediately the phone died. As in power off. But not quite, I couldn't reboot -- I had to pull the battery in order for it to boot again. After that rebooting worked fine... until LBE auto-loaded after boot -- at which point the phone powered down again.
I booted into Recovery and used the file manager to delete the .apk and that fixed the problem.
Also, apparently flash doesn't work (though I see there may be a patch available so I'll try that out and report back).
Thanks everyone for these incredible forums and thanks to dave71670 for this fantastic ROM.
Cheers!
Brandon
BCLaraby said:
Hey all,
Very, very new to the forums (and I'm putting this here as I can't seem to add to the Dev forum thread) but I just wanted to pop on and report a critical bug I found after installing Salty Bean 4.2.1 (02/01/13 build).
I installed an app called LBE Privacy Guard onto my sgh-i896, gave it SU permissions and immediately the phone died. As in power off. But not quite, I couldn't reboot -- I had to pull the battery in order for it to boot again. After that rebooting worked fine... until LBE auto-loaded after boot -- at which point the phone powered down again.
I booted into Recovery and used the file manager to delete the .apk and that fixed the problem.
Also, apparently flash doesn't work (though I see there may be a patch available so I'll try that out and report back).
Thanks everyone for these incredible forums and thanks to dave71670 for this fantastic ROM.
Cheers!
Brandon
Click to expand...
Click to collapse
Based on what I just read about that app, it is the one causing the bootloop and has nothing to do with Salty Bean.
you might take a look in your etc/init.d folder for any scripts the app left behind. Init.d scripts can bork things up before your phone finishes booting.
Hi, i need some help...
i have samsung galaxy s III lte uk on 4.1.2 stock, rooted with busybox, supersu and clockworkmod recovery.
i am trying to stop the phone from waking up and beeping when it is fully charged.
i have spent hours searching and trying different solutions from various threads.
so far i have...
grabbed SystemUI.odex (and SystemUI.apk) + framework files decompiled it (.odex) and edited PowerUI.smali and PowerUI$1.smali
put the editied .odex back into SystemUI.apk, zipaligned, pushed to sdcard, dexopt-wrapper, copy file attributes and replace original SystemUI.odex (but not SystemUI.apk) with edited one, change permissions, sync, reboot
making the following changes from the following threads and used combinations...
http://forum.xda-developers.com/show....php?t=2125129
http://forum.xda-developers.com/show....php?t=2202334
while using the above info stops the battery full in the notification bar it doesn't always stop the beep and screen turning on when plugged into the mains.
I have also tried using xposed framework with tweakbox again that stops the notification bar icon but not the beep and screen on alert.
Any help would be much appreciated!
See your exact same post .
Decided to go with custom rom [XXBMG3-V18.5] Ripper Rom. Easy to install and customise, and removes battery notification.
Still would like to be able to modify the code myself though if anyone has any suggestions...
Fender9770 said:
Decided to go with custom rom [XXBMG3-V18.5] Ripper Rom. Easy to install and customise, and removes battery notification.
Still would like to be able to modify the code myself though if anyone has any suggestions...
Click to expand...
Click to collapse
See my guide here:
http://forum.xda-developers.com/showthread.php?p=46354325#post46354325
Thanks for the info will give that a try!
I implemented the tweaks in your guide. stops the battery notification thanks. is there a way to disable the screen from turning on and fully charged beep sound (without deleting the sound file)
Thanks
Update...
have tried every suggested method. still cannot stop the screen on wake when fully charged. was hoping that the ripper rom update would solve this but still has the same problem which is a shame because its a fantastic stock based rom. what does work is installing a non stock based rom have tried cyanfox which is so far so good!
I tried to install the CM10.1 MMS.apk like I usually do on all of the phones that I root since I prefer the stock android messaging look. I have done this on Samsung phones before with no problem whatsoever. The way I go about this is renaming the samsung mms apk (secmms or something) in system/app to have secmms.apk.bak, and then moving the cm10.1 mms.apk to system app, fixing the permissions and rebooting.
When I reboot my phone is where I get the problem. On boot I get a notification saying that an app has been closed due to unauthrized attempt to access system. I am assuming this is a knox security thing going on preventing the cm10 mms.apk from opening, even though it appears in my app drawer.
my questions are:
-what can I do to allow the cm10.1 mms.apk to run? Do I need to freeze knox? Are there negative effects of doing so?
-am I trying to install an incompatible apk since the note 3 runs 4.3?
-at the very least I'd like the stock messaging app back working again. However, the one hiccup here is that I deleted the odex file for the stock messaging app... I know I should have just renamed it, but I was confident in my method. If the answers to my first two bullet points are negative for getting the cm10.1 mms.apk to work, can someone post the stock samsung odex file so I can get stock messaging back up and running?
THANKS GUYS! I appreicate it.
EDIT: Went ahead and froze the knox software (as per the thread regarding the freezing of knox/tripping the counter thread) and the cm10.1 mms.apk works like a charm. However please comment if freezing this software is ill-advised. Thanks again.