This isn't what I would call a troublesome thing, but I found it odd. I'm trying to learn all I can about Android's inner workings, so perhaps someone around here could clue me in on this behavior.
I decided earlier to tweak my SystemUI.apk. I pulled it, tweaked it, pushed it back, and it started into an FC loop. In retaliation, I deleted it, rebooted, and restored the TB copy. I tried my tweak again, pushed it back, and noticed no reaction from Android whatsoever. I took a peek at my /system/app directory, and saw that my SystemUI.apk was now neighbored by a com.android.systemui.apk that TB dropped in there.
This is where it gets a bit odd. For yucks, I deleted both apks, cleaned the DC, booted recovery, and dropped in a brand new SystemUI.apk extracted from the ROM I'm currently using. After rebooting, I had no status bar, TB reported it as not installed, and logcat complained about it missing.
So, I deleted my SystemUI.apk, cleaned the DC - it found one file - rebooted, restored the TB backup, rebooted, and all was fine. I renamed com.android.systemui.apk to SystemUI.apk, cleaned the DC, rebooted, and still no problems. I deleted SystemUI.apk, pushed a fresh copy from the ROM again, and still no problems.
That brings me to my question. Could anybody provide insight as to why Android was ignoring SystemUI.apk after having removed com.android.systemui.apk and rebooting?
Related
I am trying to edit an .xml file in settings.apk, i can't remember the name as im away from my computer, but i tried decompiling manually and recompiling and i jsut get force closes when i copy back to system\app. I also tried apk manager and get the same force closes. I did sign them .apk and also include the twframework.apk as a dependency when compiling/decompiling. Any tips as why i could possibly be getting all force closes? I removed touchwiz from system/app could this effect it?
I don't have experience with your specific case, but when it comes to removing touchwiz from system/app I have noticed problems. For one, when I select Airplane mode, phone lags and I get a force close error. Another, I experience longer (not considerably longer, but still longer) boot times. Tried various things such as factory resets, flashing touchwiz-less systems, but still got these error.s Both issues remedied by putting touchwiz back in system/app.
So yea, not directly answering your specific case, just saying it's possible since removing touchwiz seems to cause problems for myself.
I was hoping someone here can give me a bit of advice.
A couple days ago I was able to successfully root my SF and change out the bottom right search key so it would default to Google from now on.
Feeling good from all that I thought I'd take on a little tougher challenge and do some more customizing, starting out small before I think about tackling the Voodoo stuff later on.
WELL... I tried to change the battery indicator to the circle indicator followed the directions here: UOT Kitchen. How-To
It asked me to back up my "framework-res.apk" because I would have to replace it with one the website generated for me.
Everything went fine until I stupidly tried to do a 1:1 exchange of the new "framework-res.apk" for the original one, by first renaming it to apk.old with the hopes to paste in the new one in its place. BUt as soon as I renamed it and moved it to a backup folder it froze before I could insert the new one.
I know now I should've run the new .apk instead of swapping, but am now stuck with a SF that turns on but that is stuck at the SAMSUNG logo.
I hear the startup sound play and the verizon logo music, but that's as far as it goes. I can still boot into recovery or download mode.
Now, It seems that "all I need to do" is find a way to get access to my internal SD card and rename the "original back to .apk and move it to its original spot in the framework folder.
Is there a way to do something like this? I'm hoping there's some easy way to do this, short of having to do something more radical.
Hopefully there's someone out there that might be able to offer some advice for my current situation.
THANKS!
UPDATE:
FIXED!
Here's what I did.
I tried all the fixes in this link
Odin Restore files to get you to stock - xda-developers
but i was still getting forced closes.
then I wiped the stock recovery cache from the recovery menu.
After that it was still giving me FCs but to a lesser degree and I was able to make it into the "Settings menu" and do a factory reset.
After factory Reset everything has been quite stable.
Im running BAMF 1.8 remix with ZHP Pilot's sense squared theme with a few minor mods i did and some uot kitchen stuff applied.. I went to the toolkit and zipaligned and when it was done i lost my market completely. The apk was no longer on my phone. I went in and pulled the apk from the theme but it wouldnt install when i tried. I restored a backup so it wasnt an issue i was just wondering why this happened.
If you modified it, you also have to resign the application (apk). Google for ways to do that or if you know what you are doing, jarsigner works inside the /bin folder for the java jdk.
blackbass595 said:
Im running BAMF 1.8 remix with ZHP Pilot's sense squared theme with a few minor mods i did and some uot kitchen stuff applied.. I went to the toolkit and zipaligned and when it was done i lost my market completely. The apk was no longer on my phone. I went in and pulled the apk from the theme but it wouldnt install when i tried. I restored a backup so it wasnt an issue i was just wondering why this happened.
Click to expand...
Click to collapse
After you zip-align your apps, you should immediately to go to Recovery and Fix Permissions from there. I first didn't know this and i had force close problems and some apps wouldn't work and some were gone. I reflashed ROM and later when I tried to zip-align again, i immediately went to the recovery and Fixed Permissions and rebooted, everything was working fine.
Using Rooted Samsung Proclaim:
(I have used both of the root kernels and the stock kernel)
I've read multitudes of online problems involving bootloops. I've even fixed one of my own a few months ago using adb. (In that case I renamed the framework-res.apk file because I was messing around with changing the emoticons, this turned out to be a terrible Idea, but easily fixed after about 12 hours of frantic trial and error.) I learned that ADB is quite awesome.
Anyway, I recently used System Tuner Pro to boil the stock Video Player after installing and uninstalling a few video players from the play store. I like to freeze most stock apps to see whether I really want to use them or not. I didn't pay attention to the toast which warned me that I might need to reboot for the change to take affect. So after I couldn't find the Video Player in my apps, I boiled it again. This time noticing the toast warning. So I rebooted. Now I'm stuck at the bootanimation loop.
I can still connect with adb from the bootloader and during the bootanimation loop. I have pulled most of the system files just to see if everything is still in there. I have also removed the VideoPlayer.apk file thinking the double boil had something to do with it. Still loops.
I've tried reinstalling the framework-res file that was still on my computer from the last time I had trouble. It installed just fine but still looping after reboot.
There must be some unresolved conflict during the bootanimation but I have no Idea which files to replace or reinstall. I have even wiped everything using the factory reset in the bootloader. I have attempted to wipe with adb but this always seems to give failures and permission troubles.
Any Ideas?
Well now I've really gone and messed things up. Pretty sure it's out of my realm of possibilities now.
After pushing my wife's (same phone) bin folder into mine i have lost all permissions due to system/bin/sh.
Now I can't do anything with adb except connect to the phone. So technically its all still there.
I just need to write over the bin with my original bin and then I might hopefully be back at the previous problem.
Also, it's looping at the Samsung logo now so I've definitely gone backwards.
This is what I get for messing with things that I don't fully understand.
The problem:
I rooted my Galaxy Ace and installed an app called Root Cleaner. Though it did a good job on cleaning up the internal memory, the app also had an option to uninstall system and non-system apps. It so happened that I accidentally tapped on Bluetooth Share and it got uninstalled without asking any confirmation. Now, whenever I try to send a file via Bluetooth, it simply gets queued and refuses to be sent.
//pics go here, unable to submit them due to 10 post limitation...
So I realized I messed up. I had to find a way to re-install Bluetooth Share.
What I tried to do:
I rooted my friend's Galaxy Ace (both of them are 2.3.6), compared the programs in /system/app and sure enough BluetoothPbap.apk was missing from my list. So I copied the .apk onto my sd card, then copied it to the /system/app directory. Total Commander asked me for rw permissions, I just pressed ok and the file got copied. I tried installing the .apk, but I simply got "Application not installed". I looked around for ways of re-installing system apps, but one page suggested simply leaving the .apk in the /app folder and re-staring the phone. After doing so Bluetooth Share was back on the system app list, yet it is still unable to send any files.
Sooo... Help? What I suspect right now is that the .apk file I got might be in some way incompatible with my device, though I got it from and Ace with the same version of Android, could this really be the case? Any advice is welcome.
Oh, and another interesting thing. After doing everything mentioned above, I tried deliberately uninstalling Bluetooth Share and reinstalling it. The BluetoothPbap.apk disappears from /system/app, but when I paste it in and try to install it, It asks if I want to replace the application. In other words, It's asking me if I want to replace something that isn't installed, so I have no idea how to explain this.