Related
Anyone know the .apk name of the nexus lock screen in the system/app folder?
Jboxen said:
Anyone know the .apk name of the nexus lock screen in the system/app folder?
Click to expand...
Click to collapse
I dont believe there is a apk for it as if you remove htclockscreen.apk it gives you the n1 lockscreen.
droidkevlar said:
I dont believe there is a apk for it as if you remove htclockscreen.apk it gives you the n1 lockscreen.
Click to expand...
Click to collapse
Right. I did that in evil Eris 2.0 and it has a background picture rather than being transparent. I'm trying to locate the .png it is loading so I cam change it to a transparent one.
Jboxen said:
Right. I did that in evil Eris 2.0 and it has a background picture rather than being transparent. I'm trying to locate the .png it is loading so I cam change it to a transparent one.
Click to expand...
Click to collapse
no one has figured out how to make it transparent again, i read it was being looked into. i prefer the background as it doesnt conflict with my htc clock on the home screen.
droidkevlar said:
I dont believe there is a apk for it as if you remove htclockscreen.apk it gives you the n1 lockscreen.
Click to expand...
Click to collapse
so if i remove the htclockscreen.apk from my eris it will just use the n1 lockscreen?
Macros617 said:
so if i remove the htclockscreen.apk from my eris it will just use the n1 lockscreen?
Click to expand...
Click to collapse
Yes this is true
Jboxen said:
Yes this is true
Click to expand...
Click to collapse
this may be going a bit out of the way but how do i remove it?
Macros617 said:
this may be going a bit out of the way but how do i remove it?
Click to expand...
Click to collapse
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I choose to save it incase I want it for later)
reboot phone and you should see the changes.
(for EE2 users) Just so you know, as of right now, you can not change the image for the Nexus Lockscreen. (I have tried a few times and for whatever reason it will not accept the change, it sends my phone into a loop)
dianeofarcadia said:
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I choose to save it incase I want it for later)
reboot phone and you should see the changes.
(for EE2 users) Just so you know, as of right now, you can not change the image for the Nexus Lockscreen. (I have tried a few times and for whatever reason it will not accept the change, it sends my phone into a loop)
Click to expand...
Click to collapse
before i do this what's ee2 user? I have the eris on 2.1 leak 3
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I cho
Click to expand...
Click to collapse
before i do this what's ee2 user? I have the eris on 2.1 leak 3
Click to expand...
Click to collapse
EE2= evil eris 2, it's a rom for those that are rooted. If you are on the leak, no root, then you can't make this change.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Ah alright thanks though
-------------------------------------
Sent via the XDA Tapatalk App
Has anyone talked to konikub or spencer about it?
-------------------------------------
Sent via the XDA Tapatalk App
dianeofarcadia said:
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I choose to save it incase I want it for later)
reboot phone and you should see the changes.
)
Click to expand...
Click to collapse
So if HTClockscreen.apk was deleted... anyway to get it back?
i tried to delete it with root explorer but it is saying it is a read only and i cant delete it...
i tried to delete it with root explorer but it is saying it is a read only and i cant delete it...
Click to expand...
Click to collapse
Make sure you have read/write mode on. You can also remove using adb
Sent from my JACKEDZ v1.1 using Tapatalk
droidkevlar said:
Make sure you have read/write mode on. You can also remove using adb
Sent from my JACKEDZ v1.1 using Tapatalk
Click to expand...
Click to collapse
im not very familiar with android...just bought the phone and just got the root explorer so im not sure how to do the read/write mode on thing
jpen said:
im not very familiar with android...just bought the phone and just got the root explorer so im not sure how to do the read/write mode on thing
Click to expand...
Click to collapse
Using rootexporer, just open the folder you want to remove the apk, at the very top, you will see it says mounted as r/o and then a button that says mount R/W. Hit that button. Now you can remove/edit files in that dir.
Piece of advice. If you are truly interested in learning your phone, look into adb commands. There are a few programs listed on this forum that do it for you or you can learn the commands yourself and just enter them via cmd line.
This will only work if your phone is rooted correct? Won't work on nonrooted or leak v3?
nesgodawg said:
This will only work if your phone is rooted correct? Won't work on nonrooted or leak v3?
Click to expand...
Click to collapse
is he right? cuz im not rooted i just have the official 2.1 and yea im not seeing the mount R/W option..
Yeah, after doing some research it does turn out you have to be rooted. I'm trying to adb my phone now and keep getting blocked out.
You have to root first.
Today I found that my camera is not present in the programs. I did some power saving tweaks. I am not sure whether that has caused my camera to disappear or un installed or something unknown has caused it un installed.
How can I re install. Please help.
Thanks in advance.
mirchichamu said:
Today I found that my camera is not present in the programs. I did some power saving tweaks. I am not sure whether that has caused my camera to disappear or un installed or something unknown has caused it un installed.
How can I re install. Please help.
Thanks in advance.
Click to expand...
Click to collapse
The "Camera" exe file should be there in the Windows Folder. copy that, paste a shortcut in the start menu in the Windows folder itself. that should fix things. (if things havent gone too wrong).
karthiksk said:
The "Camera" exe file should be there in the Windows Folder. copy that, paste a shortcut in the start menu in the Windows folder itself. that should fix things. (if things havent gone too wrong).
Click to expand...
Click to collapse
Thanks karthiksk for reply.
I found two files. One HTC_camera and other Camera. Both I copied to start menu BUT still my camera not working. The icons are now present in programs menu but when I click on them nothing happens.
Further help will be appreciated.
mirchichamu said:
Thanks karthiksk for reply.
I found two files. One HTC_camera and other Camera. Both I copied to start menu BUT still my camera not working. The icons are now present in programs menu but when I click on them nothing happens.
Further help will be appreciated.
Click to expand...
Click to collapse
Here have this file downloaded on ur opal.
http://www.mediafire.com/?xfj3971uvy4pr8p
OR better reflash ur current ROM.
shreyas18 said:
Here have this file downloaded on ur opal.
http://www.mediafire.com/?xfj3971uvy4pr8p
OR better reflash ur current ROM.
Click to expand...
Click to collapse
Thanks shreyas18.
I installed the file but it didn't work.
Sorry.
mirchichamu said:
Thanks shreyas18.
I installed the file but it didn't work.
Click to expand...
Click to collapse
Try reflashing the rom...cant help much then.
I know this is gonna sound a little weird, but it happened to me, and this is how u can solve it, the problem its on the hardware of the phone not the software, so reflashing the rom wont do anything, since the problem is inside, firste turn off the phone, then remove the back lit, then lightly press with both of your finger the area surrounding the camera, (like trying to push on the opposite direction of the camera) then turn on your phone and go directly to the photo tab, on the touch flo, and that should do it
Lsagara said:
I know this is gonna sound a little weird, but it happened to me, and this is how u can solve it, the problem its on the hardware of the phone not the software, so reflashing the rom wont do anything, since the problem is inside, firste turn off the phone, then remove the back lit, then lightly press with both of your finger the area surrounding the camera, (like trying to push on the opposite direction of the camera) then turn on your phone and go directly to the photo tab, on the touch flo, and that should do it
Click to expand...
Click to collapse
no offence Lsagara, but i doubt its a hardware issue, even if it were a hardware issue there is no reason for the files to disappear
@mirchichamu:
1)What happens when you run the "Camera" file from the windows folder itself?
2)You could use M2DC to customize your softkey to access camera. What happens when you do that?
Same problem - File deleted
Hello,
The file you have provided above has been deleted from the Mediafire.
Were you able to locate any solution? Even I am facing the same problem.
karthiksk said:
no offence Lsagara, but i doubt its a hardware issue, even if it were a hardware issue there is no reason for the files to disappear
@mirchichamu:
1)What happens when you run the "Camera" file from the windows folder itself?
2)You could use M2DC to customize your softkey to access camera. What happens when you do that?
Click to expand...
Click to collapse
Alright guys,
Pretty much what I'm after is a launcher shortcut which locks our gear.. The reason for this when using custom launchers the home/power button by default does not lock the device anymore.
It seems that particular feature was hardcoded into the TW launcher.
There are various applications available on the playstore, although I haven't found any which work on the gear as they require additional settings to be enabled in a traditional settings dialog.. which obviously we dont have.
If anyone has any ideas please post ! Or even better if you know of a app in mind which works !
Click to expand...
Click to collapse
EDIT:
jrdejavux said:
can you guys please post instructions thank you!
Click to expand...
Click to collapse
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
fOmey said:
Alright guys,
Pretty much what I'm after is a launcher shortcut which locks our gear.. The reason for this when using custom launchers the home/power button by default does not lock the device anymore.
It seems that particular feature was hardcoded into the TW launcher.
There are various applications available on the playstore, although I haven't found any which work on the gear as they require additional settings to be enabled in a traditional settings dialog.. which obviously we dont have.
If anyone has any ideas please post ! Or even better if you know of a app in mind which works !
Click to expand...
Click to collapse
Screen off and Lock
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
put a shortcut to the app and it'll lock your device
i'm now looking for a way to capture the 'home button' to run this app
karoolus said:
Screen off and Lock
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
put a shortcut to the app and it'll lock your device
i'm now looking for a way to capture the 'home button' to run this app
Click to expand...
Click to collapse
I tried this particular application, although it FC's here..
fOmey said:
I tried this particular application, although it FC's here..
Click to expand...
Click to collapse
yeah, you have to enable the device administrator somehow.. on my phone, it works just fine, now to get it to the watch
karoolus said:
yeah, you have to enable the device administrator somehow.. on my phone, it works just fine, now to get it to the watch
Click to expand...
Click to collapse
Yes im aware of that, you obviously didn't read the OP very well.. Thanks anyway..
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Brendo said:
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Click to expand...
Click to collapse
Genius. Worked a charm.. I sussed the keylayouts out previously.. I was looking at Generic.kl..
Modified Key 172 to POWER and it works a charm.
fOmey said:
Genius. Worked a charm.. I sussed the keylayouts out previously.. I was looking at Generic.kl..
Modified Key 172 to POWER and it works a charm.
Click to expand...
Click to collapse
Brendo said:
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Click to expand...
Click to collapse
Awesome tag team. Works great with Nova!
How do you modify the key?
Sent from my SM-N900V using xda app-developers app
bosshogg38 said:
How do you modify the key?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Root file explorer.. Open the file as a text file.
can you guys please post instructions thank you!
jrdejavux said:
can you guys please post instructions thank you!
Click to expand...
Click to collapse
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
fOmey said:
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
Click to expand...
Click to collapse
Do you happen to have the stock file setup? I think I may have accidentally edited the wrong key, so now i have two lines with "Key 172 POWER".
MaTtKs said:
Do you happen to have the stock file setup? I think I may have accidentally edited the wrong key, so now i have two lines with "Key 172 POWER".
Click to expand...
Click to collapse
I do not, Although this is what it should look like:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
key 172 POWER WAKE
fOmey said:
I do not, Although this is what it should look like:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
key 172 POWER WAKE
Click to expand...
Click to collapse
Awesome. Thanks buddy.
MaTtKs said:
Awesome. Thanks buddy.
Click to expand...
Click to collapse
I can't get this to stick...I make the changes, and save, but when I go back in they are different again.
Using root explorer.
Sent from my SM-N900V using xda app-developers app
So I was trying to follow a tutorial for installing Japanese apps on a non-JP phone, but after I modified the values and rebooted the system, the phone started turning off after the boot screen. I still have access to recovery and download mode. Any idea of what could have gone wrong? Thank you in advance.
Since I can't post images or outside links, I'll paste the text up to what I did here:
1. Run RootExplorer and navigate to /system. Click the button to remount as r+w.
2. Long press on build.prop and select Copy. Paste it into the same folder or another folder to make a backup. You DO NOT want to lose this.
3. Long press on build.prop and select Edit in Text Editor.
4. Find and modify the following values (jacked from an NTT DoCoMo SHARP SH12C). Be aware they may not be grouped logically, so search the whole file if need bed. If a value doesn't exist, you will need to create it:
ro.build.id=S7140
ro.build.display.id=01.01.02
ro.build.version.incremental=01.01.01
ro.build.version.release=2.3.3
ro.product.model=SH-12C
ro.product.brand=DOCOMO
ro.product.name=SH12C
ro.product.device=SH12C
ro.product.board=SH12C
ro.product.manufacturer=SHARP
ro.product.locale.language=ja
ro.product.locale.region=JP
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
ro.build.product=SH12C
ro.build.description=SH12C-user 2.3.3 S7140 01.01.01 release-keys
ro.build.fingerprint=DOCOMO/SH12C/SH12C:2.3.3/S7140/01.01.01:user/release-keys
5. Close Root Explorer.
6. Open System->Applications->All and scroll down to Market. Click Force Close and Clear Cache.
7. Power off your phone. You absolutely must reboot your phone in order to populate the new values we just made in the RAM.
bunnyrice said:
So I was trying to follow a tutorial for installing Japanese apps on a non-JP phone, but after I modified the values and rebooted the system, the phone started turning off after the boot screen. I still have access to recovery and download mode. Any idea of what could have gone wrong? Thank you in advance.
Since I can't post images or outside links, I'll paste the text up to what I did here:
1. Run RootExplorer and navigate to /system. Click the button to remount as r+w.
2. Long press on build.prop and select Copy. Paste it into the same folder or another folder to make a backup. You DO NOT want to lose this.
3. Long press on build.prop and select Edit in Text Editor.
4. Find and modify the following values (jacked from an NTT DoCoMo SHARP SH12C). Be aware they may not be grouped logically, so search the whole file if need bed. If a value doesn't exist, you will need to create it:
ro.build.id=S7140
ro.build.display.id=01.01.02
ro.build.version.incremental=01.01.01
ro.build.version.release=2.3.3
ro.product.model=SH-12C
ro.product.brand=DOCOMO
ro.product.name=SH12C
ro.product.device=SH12C
ro.product.board=SH12C
ro.product.manufacturer=SHARP
ro.product.locale.language=ja
ro.product.locale.region=JP
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
ro.build.product=SH12C
ro.build.description=SH12C-user 2.3.3 S7140 01.01.01 release-keys
ro.build.fingerprint=DOCOMO/SH12C/SH12C:2.3.3/S7140/01.01.01:user/release-keys
5. Close Root Explorer.
6. Open System->Applications->All and scroll down to Market. Click Force Close and Clear Cache.
7. Power off your phone. You absolutely must reboot your phone in order to populate the new values we just made in the RAM.
Click to expand...
Click to collapse
You just added those lines or you replace its values on already existing?
shut_down said:
You just added those lines or you replace its values on already existing?
Click to expand...
Click to collapse
I replaced the ones that already existed and added the rest. I think the ones that had to be added were
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
bunnyrice said:
I replaced the ones that already existed and added the rest. I think the ones that had to be added were
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
Click to expand...
Click to collapse
We use ro.build.id, not ro.sh_build.id. Try to remove that sh_.
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.build.id=S7301
ro.build.version.incremental=01.01.02
shut_down said:
We use ro.build.id, not ro.sh_build.id. Try to remove that sh_.
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.build.id=S7301
ro.build.version.incremental=01.01.02
Click to expand...
Click to collapse
Thank you very much. Can I edit it through my computer, or will I have to do a reset?
bunnyrice said:
Thank you very much. Can I edit it through my computer, or will I have to do a reset?
Click to expand...
Click to collapse
You can edit, and put it back in system, where it was. But permissions must be 644, you will get a bootloop if it is not like that.
shut_down said:
You can edit, and put it back in system, where it was. But permissions must be 644, you will get a bootloop if it is not like that.
Click to expand...
Click to collapse
My computer's no longer recognizing the phone when I plug the USB in. I tried wiping the user data and cache, but that didn't work either... Is there any other way to edit it?
bunnyrice said:
My computer's no longer recognizing the phone when I plug the USB in. I tried wiping the user data and cache, but that didn't work either... Is there any other way to edit it?
Click to expand...
Click to collapse
Go to recovery, and use this:
http://forum.xda-developers.com/showthread.php?t=2105707
shut_down said:
Go to recovery, and use this:
http://forum.xda-developers.com/showthread.php?t=2105707
Click to expand...
Click to collapse
Thank you so, so much. I will now try modifying the values the way you've said.
bunnyrice said:
Thank you so, so much. I will now try modifying the values the way you've said.
Click to expand...
Click to collapse
You can change permissions in that app by selecting build.prop and hit Files>Change attributes. To 644.
shut_down said:
You can change permissions in that app by selecting build.prop and hit Files>Change attributes. To 644.
Click to expand...
Click to collapse
It worked! I really can't thank you enough, both for saving my phone from my inexperient hands and actually making it work. Thank you.
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
guyd said:
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
Click to expand...
Click to collapse
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Yoshi910 said:
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Click to expand...
Click to collapse
I can mod systemui.apk to remove them, if you want it.
mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
guaneet said:
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
Click to expand...
Click to collapse
haha, yea im not a fan of having a ton of threads all with mostly the same thing. ill see what i can do about the toggles, i can for sure get rid of the other stuff.
You can also simply install Lux and turn off its persistent notification
Could this be used to do other tweaks like remove icons/clock from the status bar?
mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
teiglin said:
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
Click to expand...
Click to collapse
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
mikeyinid said:
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
Click to expand...
Click to collapse
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Edit for basic instructions:
Use a root-enabled file manager or console to replace /system/priv-app/SystemUI/SystemUI.apk with the attached file, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz. Make sure the permissions of the new SystemUI.apk are rw-r--r-- (chmod 644 /system/priv-app/SystemUI/SystemUI.apk at the console). Reboot and enjoy.
Caveat: you may not be able to swipe away notifications from within the region previously taken up by the sfinder/qconnect bar.
Great! Can also be done via adb:
Code:
adb shell settings put system notification_panel_brightness_adjustment 0
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Thanks! Works great.
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
How would you get it to work, I tried to install it but it won't install.
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Worked fine, thanks !
EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
v2.2v said:
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
Click to expand...
Click to collapse
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
That worked flawlessly, thank you.
teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
perfect! thank you so much
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Painless001 said:
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Click to expand...
Click to collapse
BINGO. Yea i forgot to mention that in my response, as well. Always fix permissions