Some radios of the atrix will have the " 1 bar signal " issue.
It is caused by a moto customize system setting flag "rat_signal_strength_raw".
If you use the radio version is not mapping with the system version, the flag won't correct. It will cause the radio signal is always 1 bar in 3G mode.
There is a workaround for this issue. We just ignore the flag.
I have made a fix in the SystemUI.apk. It will solve the one bar issue.
Now, with the workaround fix, you can use any version of the radios without one bar issue. Just try it now!
The attachment SystemUI.apk is based on 4.5.91.
DO NOT USE THIS in others base ROM.
How to use it?
I suggest you MUST backup your data and ROM first. Don't forget to delete the /system/app/SystemUI.odex and give permission rw-r--r to SystemUI.apk.
Using ROOT Explorer ( you can also use my free software "Super Manager" on the Market) or ADB to put the SystemUI.apk into /system/app and reboot your device.
Code:
adb shell rm /system/app/SystemUI.odex
adb push c:\SystemUI.apk /system/app
For the ROM cooker
If you are a ROM maker, you can use smali to decompile the SystemUI.apk
Find the file, com\android\systemui\statusbar\policy\StatusBarPolicy.smali
Search the keyword "rat_signal_strength_raw" and change the string into anything you like. For example :
Code:
Original: const-string v6, "rat_signal_strength_raw"
New: const-string v6, "rat_signal_strength_raw_gpc"
This removed the status bar completely from my phone. Running Alien 4.0, Faux 123, with GoLauncher.
carlharsch said:
This removed the status bar completely from my phone. Running Alien 4.0, Faux 123, with GoLauncher.
Click to expand...
Click to collapse
It means the APK is not match with your system.
The systemUI.apk is a system APK. If the signature is not correct, it will disappear
Maybe you can wait the ROM maker to import the fix.
Thanks for the reply. I'm restoring my backup now.
does not work on my atrix with 1.100.00r radio and stock 4.5.91
show 1 bar
carlharsch said:
This removed the status bar completely from my phone. Running Alien 4.0, Faux 123, with GoLauncher.
Click to expand...
Click to collapse
this is because you are not give permission rw-r--r for SystemUI.apk when move it
sergey1977 said:
does not work on my atrix with 1.100.00r radio and stock 4.5.91
show 1 bar
this is because you are not give permission rw-r--r for SystemUI.apk when move it
Click to expand...
Click to collapse
How i can give my phone or file the permission? I need a instruction for a beginner, sorry.
Domingo2010 said:
How i can give my phone or file the permission? I need a instruction for a beginner, sorry.
Click to expand...
Click to collapse
You can use root explorer.
Can confirm this works on UK T-mobile Atrix with Alien #4 and EternityProject kernel. Thanks =]
after deliting SystemUI.odex work correctly
Thanks
Works great, running Alien 4.0, Faux 123, international user (UK)
Thanks
worked on my 4.5.91 alien with kohlks kernel
had to backup first then reboot
status bar disappeared
then moved the new file and changed permissions and no more 1 bar
+1
thanks!
nameejokerx said:
You can use root explorer.
Click to expand...
Click to collapse
Ok thank you and how i can set these permissions?
Confirmed working on Alien 4, Att, on 1.97 baseband. Just make sure you set permissions correctly.
Is 1.97 the latest for att
It works for me on Alien4, Bell phone (on Rogers network at the moment), on 1.95 baseband. Somehow the permission of the file was set correctly after I reboot the phone, couldn't figure out why.
primeboss said:
Confirmed working on Alien 4, Att, on 1.97 baseband. Just make sure you set permissions correctly.
Is 1.97 the latest for att
Click to expand...
Click to collapse
AFAIK, 1.77.30 is the latest official att, 1.97 was the leaked beta radio. Someone please correct me if I'm wrong
You da man.... works great!
iamgpc said:
Some radios of the atrix will have the " 1 bar signal " issue.
It is caused by a moto customize system setting flag "rat_signal_strength_raw".
If you use the radio version is not mapping with the system version, the flag won't correct. It will cause the radio signal is always 1 bar in 3G mode.
There is a workaround for this issue. We just ignore the flag.
I have made a fix in the SystemUI.apk. It will solve the one bar issue.
Now, with the workaround fix, you can use any version of the radios without one bar issue. Just try it now!
The attachment SystemUI.apk is based on 4.5.91.
DO NOT USE THIS in others base ROM.
How to use it?
I suggest you MUST backup your data and ROM first. Don't forget to delete the /system/app/SystemUI.odex and give permission rw-r--r to SystemUI.apk.
Using ROOT Explorer ( you can also use my free software "Super Manager" on the Market) or ADB to put the SystemUI.apk into /system/app and reboot your device.
Code:
adb shell rm /system/app/SystemUI.odex
adb push c:\SystemUI.apk /system/app
For the ROM cooker
If you are a ROM maker, you can use smali to decompile the SystemUI.apk
Find the file, com\android\systemui\statusbar\policy\StatusBarPolicy.smali
Search the keyword "rat_signal_strength_raw" and change the string into anything you like. For example :
Code:
Original: const-string v6, "rat_signal_strength_raw"
New: const-string v6, "rat_signal_strength_raw_gpc"
Click to expand...
Click to collapse
awesome man,good job
For the lazy, after you push SystemUI.apk, type chmod 644 /system/app/SystemUI.apk to get the correct rw-r--r permissions, dunno why the OP left out the command for that. This works perfectly on mine running Aura and 1.97 baseband.
EDIT: It does break the removed carrier logo on Aura 1.1.2, so i gotta figure out how to remove that now! Ugh!
bimmerd00d said:
For the lazy, after you push SystemUI.apk, type chmod 644 /system/app/SystemUI.apk to get the correct rw-r--r permissions, dunno why the OP left out the command for that. This works perfectly on mine running Aura and 1.97 baseband.
EDIT: It does break the removed carrier logo on Aura 1.1.2, so i gotta figure out how to remove that now! Ugh!
Click to expand...
Click to collapse
If I do that, it just says SystemUI.apk is read only.
I just changed the permissions with root explorer.
Hi all,
Here is the patched SystemUI.apk for use only with this rom and users using the ALIEN THEME on the ALIEN ROM. This fixes the one bar bug as described in this thread.
ALIEN THEME ONLY.
http://www.multiupload.com/LK8R77AUDV
To install:
Code:
- Download SystemUI.apk from the link above.
- Mount your /system to r/w (I did this with RootExplorer)
- Use adb to backup your present SystemUI.apk .... for example (adb shell cp /system/app/SystemUI.apk SystemUI.apk.bak)
OR
Nandroid backup
- Copy the modified SystemUI.apk to /system/app/SystemUI.apk .... for example (adb push SystemUI.apk /system/app/SystemUI.apk)
- Set the correct permissions (644 / rw--r--r-) .... for example (adb shell chmod 644 /system/app/SystemUI.apk)
- Clear cache/dalvik in recovery and reboot =]
This worked on my phone with the ALIEN THEME. I am not saying it will work on yours. Give it a go and get back to me =]
Related
This version has no ATT, White notification text, fixed signal bars, and no FC's! Based on Adeo, so you keep the reboot functionality. This works for me on the new 1.5.2 SBF as well as Adeo. the "newbackup" framework apk is NOT deodexed, and from the new 1.5.2 SBF.
I still need to take new screenshots without the ATT and white notification text, but nothing else changed, so you should be able to use your imagination
New Black Browser (still unfortunately black text and a white text box until I can get apktool to actually build the browser apk).
For those who would like to know, I'm using Launcher Pro Plus, Light Grid LWP, and Beautiful Widgets with the small Super Clock and Simplicity theme with no background. Androdena weather icons.
If you want to revert, please follow the instructions with the framework-old and services-old files renamed to framework-res.apk and services.jar (remove .zip).
For the Black Browser, please just re-run with the backup browser apk.
To install the Browser, copy (cp) your current /system/app/Browser.apk to /mnt/sdcard, then adb push the downloaded apk to your phone in a directory of your choosing, and with root, run cp /path/to/Browser.apk /system/app/Browser.apk and reboot.
If you are deodexed, and you follow these instructions to a tee, there shouldn't be issues. No guarantees if not, though I'm running the new SBF non-deodexed, and no issues.
Here are modified instructions copypasta'd from Designgears (thanks man!):
First, Rename the downloaded services.zip to services.jar (due to xda's upload restriction on .jar files).
[/B]
run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your framework file:
mkdir /data/framework
Exit shell:
exit
Then from the directory of the downloaded files, run:
adb push framework-res.apk /data/framework
adb push services.jar /data/framework
Enter ADB Shell:
adb shell
Copy your new files to their proper location:
cp /data/framework/services.jar /system/framework
cp /data/framework/framework-res.apk /system/framework
Reboot:
reboot now
Phone will flash a red led. Just let the phone reboot (it will take up to a minute, so just be patient!).
IF YOU GET ANY READ ONLY ERRORS WHILE INSTALLING, MAKE SURE YOU'RE IN A ROOT SHELL (IF NOT, TYPE SU), THEN RUN THE FOLLOWING BEFORE TRYING THE FAILED STEP:
mount -o rw,remount /dev/block/mmcblk0p12 /system
nice
i want it
but dammmn its alot of work
I think fastboot might be unnecessary, however for some reason, I've had the best results using super one click every time.
Really, it takes 5-10 minutes, and some copy pasting...I've already done the hard stuff.
Im planning on releasing a shell script to be run in the folder with the files on the phone with terminal emulator, but want to polish the theme a bit more.
Sent from my MB860 using XDA App
thanks, i'll be bookmarking this page for updates.
synergye, you can remove AT&T from the status bar if you change framework-res.apk/res/layout/status_bar.xml, and carrier length and padding to zero on line 5.
Also, the phone will reboot itself with the reboot now command, it just takes a bit (45-60 seconds). Do that instead of pulling the battery.
Good luck on getting the white text and removing AT&T from the task bar.
Can't wait
shawnbuck said:
synergye, you can remove AT&T from the status bar if you change framework-res.apk/res/layout/status_bar.xml, and carrier length and padding to zero on line 5.
Also, the phone will reboot itself with the reboot now command, it just takes a bit (45-60 seconds). Do that instead of pulling the battery.
Click to expand...
Click to collapse
Thank You very much Shawn! I'm going to change the original post, and remove ATT ASAP.
synergye said:
Thank You very much Shawn! I'm going to change the original post, and remove ATT ASAP.
Click to expand...
Click to collapse
Glad to help
Also, this theme won't mix with Adeo because of the reboot option it uses.
shawnbuck said:
Glad to help
Also, this theme won't mix with Adeo because of the reboot option it uses.
Click to expand...
Click to collapse
I'm actually using Adeo with it right now and still have the reboot option. I would assume this is because I modified the framework-res apk from Adeo.
Thats great, going to install this right now.
Shawn, I've tried droiddraw, microsoft's xml editor, excel, eclipse, wordpad, and notepad won't actually open the status bar xml. What am I missing?
It's a proprietary compiled XML format. To unpack it, you need to use apktool.
http://code.google.com/p/android-apktool/
Use:
apktool d framework-res.apk framework-res
apktool b framework-res.apk framework-new.apk
IMPORTANT:
Make sure you have the META-INF files inside the new apk. The easiest way of doing this is repacking the apk as something new, pulling out the compiled XML files, then adding them into the original apk.
On a side note, its nice to see an honest representation of what data connection the phone is getting.
I have a question. The data/framework folder we create, is there any reason why we cannot do it from a folder on our sdcard like how we pushed the deodex file over from designgears? Is this just your preference to have it in data or is it 100% required? Just curious cuz after we do all this we will have an empty data/framework folder just sitting there.
There's no reason it can't be in an already existing folder, or just data.
@Sean, thanks for the help, didn't know I'd be using apktool for that.
Sent from my MB860 using XDA App
synergye said:
There's no reason it can't be in an already existing folder, or just data.
@Sean, thanks for the help, didn't know I'd be using apktool for that.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks. There is a minor typo in your instructions. You forgot a space between CP and / for the service.jar line. You will get a directory does not exist without that space
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp/data/framework/services.jar /system/framework
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp /data/framework/services.jar /system/framework
Some reason my signal icons are not showing up properly and stays on white even though i have full bars. also the signal part is still black
NguyenHuu said:
Thanks. There is a minor typo in your instructions. You forgot a space between CP and / for the service.jar line. You will get a directory does not exist without that space
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp/data/framework/services.jar /system/framework
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp /data/framework/services.jar /system/framework
Some reason my signal icons are not showing up properly and stays on white even though i have full bars. also the signal part is still black
Click to expand...
Click to collapse
Thank you for your correction.I believe this is because I replaced only one set of radio icons, so.if you're roaming, etc, they'll revert. Ill unify them later today. Also, the data portion stays white as if it's uploading and downloading until.it connects.
Sent from my MB860 using XDA App
Another note: after you push framework it will auto reboot, no need to enter in a command. So you push services.jar first, then push framework or else it will reboot before you can do it. Not sure if it will also auto reboot if you push services.jar, but it does with framework-res.apk.
I also noticed that graphics were replaced that were unrelated to the status bar such as graphics for various menu items and popups. It made them have white text on light grey background, which was hard to see. I went through the original framework and compared it with the gingerbread one and only moved over miles that were related to the status bar.
it looks better now, just missing the icons for the signal bars for normal state and also getting rid of the at&t text. Thanks for the mod!
@synergye
Would changing the images in the framework file work? Or would we need to take any special care? I mean, if we update the images only in the framework file and push that to our phone, would it work?
diablo009 said:
@synergye
Would changing the images in the framework file work? Or would we need to take any special care? I mean, if we update the images only in the framework file and push that to our phone, would it work?
Click to expand...
Click to collapse
yeah that's what i did too to replace the images that were misplaced. just change up the images in framework-res, then follow the directions in the OP to push it back in. i did it several times today.
you still gotta be wary of making your own though cuz some of the pngs are .9 extensions, those are tricky. but if you just copying and pasting images from other frameworks over, that should be fine.
NguyenHuu said:
yeah that's what i did too to replace the images that were misplaced. just change up the images in framework-res, then follow the directions in the OP to push it back in. i did it several times today.
you still gotta be wary of making your own though cuz some of the pngs are .9 extensions, those are tricky. but if you just copying and pasting images from other frameworks over, that should be fine.
Click to expand...
Click to collapse
I only want to change the status bar to something dark, and the battery icon to be one with numbers so I can take off the battery level app.
Discontinued. The latest versions of all previously supported ROMs have this functionality built in.
This gives you an over-scroll glow when you reach the end of a list.
I really hope you knew that before clicking on this thread.
Example if you don't know what I'm talking about
It's just a modified framework.jar with modified files allowing the over-scroll to work and the correct glow images assigned to it. Theming is very easy, just colorize the over-scroll glow pngs in framework-res.apk. The default is orange.
What I want to do with this thread is sort of have a place where you can find the over-scroll enabling mod for every popular ROM for our phones. If you think I should support a ROM that I currently don't, then please post in the forums because I read every post! Ask to put a ROM on the wishlist. Upload the ROM's framework-res.apk and framework.jar files and I'll work on it when I'm not busy with school.
Currently, the wish list is:
Stock KH7
[Update on 10/15/11] UnNamed v1.0.1 compatible files uploaded. Give them a try. Honorable mention to quarlow
Installation:
BACK UP YOUR OLD FRAMEWORK.JAR
Because I'll just laugh at you if you complain that your phone won't boot up.
>>>ADB:
Code:
Extract the CWM package to get the framework.jar
adb remount
adb shell
su
cd /system/framework/
cp framework.jar framework.jar.backup
exit
exit
adb push framework.jar /system/framework/
adb reboot
>>>ROOT EXPLORER:
Extract the CWM package to get the framework.jar
Okay, now you can theoretically do this, but why would you want to? You'll get lots of crashes and might mess something important up.
Go to: /system/framework/ and rename framework.jar to something else. Go back to where-ever you saved my modified framework.jar and copy it over to /system/framework/ and change the permissions of the new framework.jar to match the old one. I'm pretty sure it's rw-r--r--, but don't quote me on that. + Restart your phone.
Simba501 has a more indepth tutorial on how to install this mod through Root Explorer here
>>>RECOVERY (preferred):
Flash the one specific to the ROM you're running
Whatever method you choose, know that it will take a stupidly long time for your phone to boot-up. Don't worry though, it'll be worth the wait.
Yoderk created some cool themes for the over-scroll glow for Cognition Beta-4 which you can find HERE.
UnNamed 1.0.1 works with 1.0.2 and 1.0.3 as well.
Also, please remember to say THANKS if I helped you!
cwm please!!
<3
diabolicalangle said:
cwm please!!
<3
Click to expand...
Click to collapse
It's there if you REALLY need it. I haven't tested it and to be honest, it's been a very very long time since I made my last CWM compatible file. Maybe it works though, try it out. If not, then use one of the other methods.
Fine work sir! Works well on Cog Beta 4.
yoderk said:
Fine work sir! Works well on Cog Beta 4.
Click to expand...
Click to collapse
That's awesome! Someone test it on stock w/ root, because if it works there, I'll be amazed.
Confirming that the cwm flashable zip works on cog beta 3!
Working fine here. I'm technically on Beta 1, but I've manually added the components I wanted from each Beta update because there were things I didn't want.
I have a suggestion. I don't know why everyone repeats that method for using root explorer. That's a terrible way to do it. I always use root explorer to manually replace my files and have never experienced any issues. Here is the correct way to use root explorer for manually replacing modded files:
1. Navigate to the file that you plan to replace (in this case, system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. In this case, the permissions are RW-R-R, which in root explorer, means that the first two boxes on the first line are checked and only the first box on the next two lines are checked.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and that the permissions also match what it is replacing.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
Cwm file worked great on cog beta 4. Thnkz!!
Sent from my SAMSUNG-SGH-I777 Cognition
Simba501 said:
Working fine here. I'm technically on Beta 1, but I've manually added the components I wanted from each Beta update because there were things I didn't want.
I have a suggestion. I don't know why everyone repeats that method for using root explorer. That's a terrible way to do it. I always use root explorer to manually replace my files and have never experienced any issues. Here is the correct way to use root explorer for manually replacing modded files:
...
No force closes, no problems .
Click to expand...
Click to collapse
Thanks! I added your tutorial to the OP.
Well if your like me and hate orange! Then here are two framework-res.apk with a blue and green overscroll color. Just rename them to framework-res.apk and overwrite the original file in system/framework.
Do not forget to back up original file! I claim no responsibility to problems.
Very subtle but a very nice touch...kudos...came zip worked great!!!
Sent from my SAMSUNG-SGH-I777 using XDA App
stock with root, i've got nothing. tried root explorer method and cwm
Does this still have the problem of not changing the Contacts or other Samsung apps?
illathanyours said:
stock with root, i've got nothing. tried root explorer method and cwm
Click to expand...
Click to collapse
Alright this may be Cog4 only... if you want, upload your framework.jar and framework-res.apk and I'll mod it for you and let me know if that works.
MikeyMike01 said:
Does this still have the problem of not changing the Contacts or other Samsung apps?
Click to expand...
Click to collapse
Yes. Those need the tw-framework to be modified and I haven't taken a look at those yet since I'm trying out Perception for a couple of days and that already has it coded in? But it isn't a problem per-say, it's just how Samsung decided to code those specific apps and there isn't a way to implement them in 2.3.4 without breaking the slide left to call, slide right to message, feature. 2.3.5 Roms have that built in on Samsung apps.
Problem probably isn't the best word.
Thanks for answering though. I always wanted the overscroll but having mixed bothered me.
Sent from my SGH-i777
shishir95 said:
Alright this may be Cog4 only... if you want, upload your framework.jar and framework-res.apk and I'll mod it for you and let me know if that works.
Well it's not that pressing of an issue, but maybe I'll send it to you later but right now I'm Dealing with insane iPhone customers, makes me want to hang myself... If 2.3.5 is gonna be coming sometime soon I wouldn't care about the wait.
Anyone know about 2.3.5 ota eta?
Sent from illaphone.
Click to expand...
Click to collapse
illathanyours said:
shishir95 said:
Alright this may be Cog4 only... if you want, upload your framework.jar and framework-res.apk and I'll mod it for you and let me know if that works.
Well it's not that pressing of an issue, but maybe I'll send it to you later but right now I'm Dealing with insane iPhone customers, makes me want to hang myself... If 2.3.5 is gonna be coming sometime soon I wouldn't care about the wait.
Anyone know about 2.3.5 ota eta?
Sent from illaphone.
Click to expand...
Click to collapse
There's a leaked 2.3.5 ROM for the i777 but personally I'm using designgear's Perception which is a port of a i9100 ROM and it works perfectly. I'd recommend the latter since leaked ROMs tend to have problems.
Click to expand...
Click to collapse
could you modify the framework.jar for UnNamed v1.0.1 - First ever well documented and open source stock derived rom? It has the extended power menu and if I overwrite the framework.jar using this it will break that extended power menu. Much thanks for getting the overscroll glow!!
Skyler2Dope said:
could you modify the framework.jar for UnNamed v1.0.1 - First ever well documented and open source stock derived rom? It has the extended power menu and if I overwrite the framework.jar using this it will break that extended power menu. Much thanks for getting the overscroll glow!!
Click to expand...
Click to collapse
I'll give it a try if there's enough demand for it.
shishir95 said:
I'll give it a try if there's enough demand for it.
Click to expand...
Click to collapse
+1 here
I used root explorer to move some system apk & its corresponding odex file from /system/apk to sdcard. I rebooted and found that I have moved some essential app like the stock dialer (it wasn't possible to figure out from the apk name). So now the dialer was gone. I then moved them back from sdcard to /system/app using root explorer thinking that it would undo the mess.
However the apps didn't come back, for example the dialer. The phone still tells me that there is no dialer.
What do I need to do?
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Gregrin said:
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Click to expand...
Click to collapse
I didn't move anything from any other directory. I moved back each and every file to /system/app that I had moved from it earlier. Still no luck.
I didn't delete anything in this process. I don't see dialer in app drawer either.
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Markuzy said:
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes, umpteen number of times.
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
RavinduSha said:
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
Click to expand...
Click to collapse
Yes, you are so right.
The apk permissions have screwed up after all the moving. I issued ls -l command in adb shell and this is what I found out.
-rw-r--r-- 1 root root 3973 May 7 2012 HTMLViewer.apk
-rw-r--r-- 1 root root 8784 May 7 2012 HTMLViewer.odex
----rwxr-x 1 system sdcard_r 562553 Feb 9 04:31 LatinIME.apk
----rwxr-x 1 system sdcard_r 327896 Feb 9 04:31 LatinIME.odex
-rw-r--r-- 1 root root 14569 May 7 2012 LiveWallpapersPicker_gles20.apk
-rw-r--r-- 1 root root 21392 May 7 2012 LiveWallpapersPicker_gles20.odex
LatinIME.apk is the keyboard with screwed up permission.
Now how do I fix it? What command do I issue?
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
You can also change permissions in Root Explorer itself. Hold down on the files, choose permissions and tick the first column and the first box of the second one. Leave the rest blank and press ok. That's it. If it still doesn't show, reboot. Fixing permissions in recovery does exactly this, but for all files in /system/app, /data/app and /data/data. Every time you copy something to /system or /data, you have to set the right permissions. Either in a root explorer app, adb shell, terminal emulator or fixing permissions in recovery.
LatinIME is the stock Android keyboard btw.
Sent from my Desire HD using xda premium
calisro said:
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
Click to expand...
Click to collapse
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
sashank said:
LatinIME is the stock Android keyboard btw.
Click to expand...
Click to collapse
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
sashank said:
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can see two apks in my phone with dialer icon.
Phone.apk (& Phone.odex)
TelephonyProvider.apk (& TelephonyProvider.odex)
How do I get back the dialer? This is a dual sim phone and only the stock dialer gives the option to select sim before dialing. None of the market dialers provide this option.
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
RavinduSha said:
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
Click to expand...
Click to collapse
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
ontherocks62 said:
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
Click to expand...
Click to collapse
advanced section. look through. it should be self explanatory.
ontherocks62 said:
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Click to expand...
Click to collapse
the dialer is Phone.apk
calisro said:
advanced section. look through. it should be self explanatory.
Click to expand...
Click to collapse
Fixed permission. Still dialer doesn't appear. :crying:
ontherocks62 said:
Fixed permission. Still dialer doesn't appear. :crying:
Click to expand...
Click to collapse
reflash the rom. easy peasy. next time careful what you delete! sry guy.
if u have a backup just restore only system partition
RavinduSha said:
if u have a backup just restore only system partition
Click to expand...
Click to collapse
I have a backup. Unfotunately, I took a backup after messing up. So after re-flashing it with the backup, it boots in the messed up state.
I downloaded one gingerbread Phone.apk yesterday. I renamed the Phone.apk and Phone.odex in my phone to Phone.apk.bak & Phone.odex.bak. Then copied the downloaded Phone.apk to /system/app. Then fixed permissions via recovery and rebooted.
To my horror, not only did the dialer didn't appear, but also the phone wouldn't detect the sim cards. It would say no connection available...
So Phone.apk is affecting other stuff too. So I deleted the new Phone.apk and renamed the .bak to its original names, fixed permissions via recovery and rebooted. The phone still wouldn't detect the sim cards.
Then I went back to recovery, cleared Dalvik cache & user data, and performed clear data & factory reset. After reboot, the phone started detecting the sim cards again.
So this leads me to believe that something else other than permissions has a role to play.
PLEASE READ
This mod ONLY applies to UNLIMITED USERS who DO NOT have tethering on their plan
This mod DOES NOT apply to SHARE EVERYTHING plans
I took a peak over at this thread http://forum.xda-developers.com/verizon-lg-g3/help/g3-hotspot-hack-t2812305 and saw that there were issues with using the G2 apk. I decided to take a looksy at it and see if I can replicate the functionality of the G2 apk with out having to re-apply settings to turn on tethering.
I have always had issues using root explores and database explorers messing up permissions and causing boot loops so until I have a proper recovery I use the android terminal emulator. Many people here have had plenty of success using file explores so give it a shot if you like!
Skip down to the bottom for a video walkthrough created by { owenbeals aka DroidModderX}
First things first you will need root!
0.) Start a root shell
Code:
su
1.) mount the system partition for read and write access
Code:
mount -o remount,rw /system
2.) Rename stock files HotspotProvision.apk and HotspotProvision.odex to something memorable. I use .bak and .bakdex
Code:
cd /system/app
mv HotspotProvision.apk HotspotProvision.bak
mv HotspotProvision.odex HotspotProvision.bakdex
3.) Now copy over the new file, can be the root of the extSD card which is /storage/external_SD/HotspotProvisionVzG3.apk
Code:
cp /storage/external_SD/HotspotProvisionVzG3.apk .
4.) The last thing is to change permissions to 644 (RW- R-- R-- for you file browsy types )
Code:
chmod 644 HotspotProvisionVzG3Mod.apk
5.) Now reboot and enjoy your glitch free hotspot action!
You must reboot! Do not try to "install" it, it does not function like that.
N.B.
Some users have noted that their cpu governors change to Performance while the hotspot is on and change back to On Demand when off instead of normal Interactive. This is the stock behaviour of the kernel, and not a bug introduced by this mod.
Thanks to { owenbeals aka DroidModderX} for this handy video walkthrough.
Thanks { Robshr, JayGoat } for bringing this up
Also thanks to { nrage23 } for answering a ton of questions on here
CREDIT:
Guest who started previous thread
Anonymous original creator
WACOmalt for making the original G2 thread
what was glitchy about the first hotspot app? HotspotProvision_24A_mod.apk
rp201 said:
what was glitchy about the first hotspot app? HotspotProvision_24A_mod.apk
Click to expand...
Click to collapse
You have change something every time you use it.
The modded apk works perfectly. I used root explorer to do it though. I renamed the original files, copied your apk to system/app, renamed it to HotSpotProvision.apk, fixed the permissions and rebooted.
Sent from my VS985 4G using XDA Premium HD app
Pretty cool. I'll have to give this a try when I'm bored later on today at work. Could you explain what you actually did to the hotspot apk though?
One thing though - why not just append ".bak" to the end of the existing filename/extension? That way, you don't lose the original extension so you can't forget what it was. It works fine. That's what I always do. In other words, your files would end in ".apk.bak" and ".odex.bak". The system only sees the extension after the final period.
nrage23 said:
You have change something every time you use it.
The modded apk works perfectly. I used root explorer to do it though. I renamed the original files, copied your apk to system/app, renamed it to HotSpotProvision.apk, fixed the permissions and rebooted.
Sent from my VS985 4G using XDA Premium HD app
Click to expand...
Click to collapse
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
The downloaded apk he modded is named differently from the original one in the system/app folder. After I changed the names for the original files in system/app. I changed the name of the modded apk to match the original apk in system/app. I copied the renamed modded apk to system/app, set the permissions correctly, then rebooted. I went into Settings then More... under wireless networks,Mobile HotSpot and changed the SSID and password. I can turn it on via settings or the quick setting in the notification bar.
sstapley_56 said:
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
Click to expand...
Click to collapse
I'd guess for it to work from stock menus (i.e. without starting the apk directly from a file browser app or terminal emulator) you'd have to rename it the same as the stock apk so that the path is the same for the various apps that would call it.
nrage23 said:
The downloaded apk he modded is named differently from the original one in the system/app folder. After I changed the names for the original files in system/app. I changed the name of the modded apk to match the original apk in system/app. I copied the renamed modded apk to system/app, set the permissions correctly, then rebooted. I went into Settings then More... under wireless networks,Mobile HotSpot and changed the SSID and password. I can turn it on via settings or the quick setting in the notification bar.
Click to expand...
Click to collapse
So I have renamed it exactly as the original apk was and rebooted but still no go. On reboot I get a force close of VZWAWSService. I have some of the system bloat frozen, maybe this has something to do with it.
phobos512 said:
I'd guess for it to work from stock menus (i.e. without starting the apk directly from a file browser app or terminal emulator) you'd have to rename it the same as the stock apk so that the path is the same for the various apps that would call it.
Click to expand...
Click to collapse
---------- Post added at 09:36 AM ---------- Previous post was at 09:33 AM ----------
Sweet it's working now, I had the lgmobilehotspot GUI.apk frozen and that's what was causing the issue. Thanks for the apk and tutorial guys!
sstapley_56 said:
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
Click to expand...
Click to collapse
Did you reboot?
There should be no reason to rename the apk. When android installs applications it goes into the /data... Dir as the package name. All intents are handled via package names therefore the apk name is inconsequential.
To use you should be able to go settings > more and see all the tethering options.
To verify placement and permissions use
Code:
su
ll /system/app/Hotspot*
You should see your two backup files and the new HotspotProvisionVzG3Mod.all
Permissions should be rw-r--r--
Let me know if you still have issues.
I will post a DIY response so that people who want to learn about the modification can play along at home. Think of it as source code for this mod:good:
[email protected] said:
Did you reboot?
There should be no reason to rename the apk. When android installs applications it goes into the /data... Dir as the package name. All intents are handled via package names therefore the apk name is inconsequential.
To use you should be able to go settings > more and see all the tethering options.
To verify placement and permissions use
Code:
su
ll /system/app/Hotspot*
You should see your two backup files and the new HotspotProvisionVzG3Mod.all
Permissions should be rw-r--r--
Let me know if you still have issues.
I will post a DIY response so that people who want to learn about the modification can play along at home. Think of it as source code for this mod:good:
Click to expand...
Click to collapse
Thanks for the detailed response, I got it working now. I had previously frozen some of the bloat on the phone when I got it and one of the apps I froze was the lgemobilehotspotui.apk which is needed to work correctly. Thanks for all the help from the awesome devs here.
Nice work, thanks. I just installed it with Root Explorer, and it worked perfectly. Just have to do it to the wife's phone, now.
Well done. Working great!
Thanks! Works perfect. And now I can use the toggle on the drop down menu to activate the hotspot. Thanks so much.
Worked
Worked perfectly for me. Used ES file explorer to move the files around.
I have downloaded, changed permissions, changed the file names to .bak but when I try to install the nodded split says application not installed. I'm using root explorer. I did have the othe mod installed and deleted it first. Wondering if that is the problem
Edit...Stopped trying to install and just rebooted and it turns on just fine, and my laptop connects...the app shows it connected and listed as an approved device...yet I'm not able to actually get a a connection.
Sent from my VS985 4G using XDA Free mobile app
Thanks! Works like a champ.
works great!
I'm also getting the VZWARSService has stopped message, and when I go into settings and turn on the hotspot, nothing happens. If I go into mobile hotspot and turn it on from there, I get this message: Unfortunately, com.lge.mobilehotspot.ui has stopped. Followed the directions exactly, so I'm not sure what's going on.
Works perfectly. I used Root Explorer to rename and move everything. Thanks!
Worked like a charm the only thing is still changes the cpu governor to performance the g2 one did it to I don't know if someone is able to fix that
It's just when I turn on the hotspot afterwards I use android tuner and change it back to interactive
Does anyone else have this issue
I tried to modify SystemUI.apk on my rooted s3 neo... Unfortunately i came to uninstallation of SystemUI... now It's not installed. I have the modified SystemUI.apk file (I changed 3G and 4G icons), i tried to install it but 3 seconds later it says "Installation unsuccessfull" of course... i have lost my notification bar, i tried changing permissions to : rw - r - r and reinstalling it, no success plz help
FireGhost1337 said:
I tried to modify SystemUI.apk on my rooted s3 neo... Unfortunately i came to uninstallation of SystemUI... now It's not installed. I have the modified SystemUI.apk file (I changed 3G and 4G icons), i tried to install it but 3 seconds later it says "Installation unsuccessfull" of course... i have lost my notification bar, i tried changing permissions to : rw - r - r and reinstalling it, no success plz help
Click to expand...
Click to collapse
get root explorer and move the SystemUI to
system/app (JB roms)
system/priv-app(KK roms)
or wherever your current UI is.
Replace it and then change the permission to rw-r-r
BatDroid said:
get root explorer and move the SystemUI to
system/app (JB roms)
system/priv-app(KK roms)
or wherever your current UI is.
Replace it and then change the permission to rw-r-r
Click to expand...
Click to collapse
Thanks for the help but just this morning I fixed it by flashing the StockSystemUI.zip in my TWRP recovery