Related
Downloaded this today off the market and it is awesome. For those who dont stray from the Charge forum check it out.
Its great since we do not have MIUI running on the Charge.
Best of all it is free.
https://market.android.com/details?id=com.miui.home
Also Lockscreens can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=1288096
Put them on your SD Card in the folder MIUI\Themes
jselden said:
Downloaded this today off the market and it is awesome. For those who dont stray from the Charge forum check it out.
Its great since we do not have MIUI running on the Charge.
Best of all it is free.
https://market.android.com/details?id=com.miui.home
Also Lockscreens can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=1288096
Put them on your SD Card in the folder MIUI\Themes
Click to expand...
Click to collapse
Great suggestion! However, I keep getting Chinese as the default language in the themes. Did you have this problem? If so, how did you fix it? If not wth am I doing wrong?
jrocketdroid said:
Great suggestion! However, I keep getting Chinese as the default language in the themes. Did you have this problem? If so, how did you fix it? If not wth am I doing wrong?
Click to expand...
Click to collapse
You can do it, but it's kind of a bear to do... What you need to do is to copy the MTZ files from the MIUI folder of your SD card to your computer. Next, extract the MTZ's with 7Zip and scan all of the XML files for Chinese. Next, go to Google Translate and translate the text, then replace the Chinese with English. Once you've got all the Chinese translated, use 7Zip to repack everything as an MTZ again. DO NOT alter the naming of any of the files!!
Place the repacked MTZ files back into the MIUI folder of your phone's SD card, overwriting the existing files.
Boom. English.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Now the real question... can you get this to work with NoLED? If so, how?
---------- Post added at 07:15 PM ---------- Previous post was at 07:11 PM ----------
P.S. You can install a ton of themes that are English from this thread: http://forum.xda-developers.com/showthread.php?t=1134657
Wow. Thats a lot of work. I just used the ones from the lockscreen thread and just manually put in sd card folder. Some didnt work. Others worked perfectly.
This is an awesome, "must have" app. I have a small annoyance though and maybe you can help. Upon restart, the default lockscreen is the one used until I open milocker. Anyway around this?
I am using infinityROM 12/11 w/TSM
thanks for the info KarateExplosion6...well, might as well try it once and see what happens...
Hi!
I've downloaded a few themes from the link above and they don't seem to work for me... I've downloaded, extracted (if zipped) and moved the into the /MIUI/themes folder. Application shows them properly but, after aplying them, I just see my screen background instead of the lockscreen. What could I be doing wrong?
|EverybodyLies| said:
Hi!
I've downloaded a few themes from the link above and they don't seem to work for me... I've downloaded, extracted (if zipped) and moved the into the /MIUI/themes folder. Application shows them properly but, after aplying them, I just see my screen background instead of the lockscreen. What could I be doing wrong?
Click to expand...
Click to collapse
There were a handful that unfortunately didn't work for me but about 75% of them worked fine.
However I also just did the google translate to a few downloaded from the app and it was actually quite simple.
Just an fyi I think the screen size effects the lock screens you can use on your phone. I think that might be the problem.
|EverybodyLies| said:
Hi!
I've downloaded a few themes from the link above and they don't seem to work for me... I've downloaded, extracted (if zipped) and moved the into the /MIUI/themes folder. Application shows them properly but, after aplying them, I just see my screen background instead of the lockscreen. What could I be doing wrong?
Click to expand...
Click to collapse
I just had the same problem with my Droid 3 (thought it was just my phone/rom).
So did a bit of comparison between the themes from the Miui thread and the themes downloaded with MiLocker.
It seems that there is a folder in the Miui themes called 'lockscreen' which shouldn't be a folder...but instead should be a zip file without the zip extension for it to work with MiLocker.
So what I did was take the folder called 'advance' inside the 'lockscreen' folder and made it into a zip file (lockscreen.zip). Then I renamed it to remove the '.zip' extension. I deleted the 'lockscreen' folder from the .mtz file, dragged this file into the .mtz theme file and voila! The theme works!
Hopefully this will bring joy to some people.
fl4r3 said:
I just had the same problem with my Droid 3 (thought it was just my phone/rom).
So did a bit of comparison between the themes from the Miui thread and the themes downloaded with MiLocker.
It seems that there is a folder in the Miui themes called 'lockscreen' which shouldn't be a folder...but instead should be a zip file without the zip extension for it to work with MiLocker.
So what I did was take the folder called 'advance' inside the 'lockscreen' folder and made it into a zip file (lockscreen.zip). Then I renamed it to remove the '.zip' extension. I deleted the 'lockscreen' folder from the .mtz file, dragged this file into the .mtz theme file and voila! The theme works!
Hopefully this will bring joy to some people.
Click to expand...
Click to collapse
Nice job figuring this out.
fl4r3 said:
I just had the same problem with my Droid 3 (thought it was just my phone/rom).
So did a bit of comparison between the themes from the Miui thread and the themes downloaded with MiLocker.
It seems that there is a folder in the Miui themes called 'lockscreen' which shouldn't be a folder...but instead should be a zip file without the zip extension for it to work with MiLocker.
So what I did was take the folder called 'advance' inside the 'lockscreen' folder and made it into a zip file (lockscreen.zip). Then I renamed it to remove the '.zip' extension. I deleted the 'lockscreen' folder from the .mtz file, dragged this file into the .mtz theme file and voila! The theme works!
Hopefully this will bring joy to some people.
Click to expand...
Click to collapse
Thanks for posting this since I'm sure people where confused as to why some themes worked and some didn't. For people that want to know why this is done, here's why:
Afaik, there are two reasons that the lockscreen folder is left as a folder and not already zipped with the extension removed. First, and mainly why, it is because the actual MIUI theme engine (which MiLocker is based on but not the same) will actually do all the work for you and convert the lockscreen folder to the correct format. The MIUI lockscreen thread was meant for people using MIUI and don't take into consideration people that just use MiLocker. Second, by leaving lockscreen as a folder it makes things a bit easier and faster for people to do their own customizations to the theme/lockscreen by just having to unzip one file rather than two.
Man I miss MIUI, so easy to theme .
I do like MiLocker but man it's been frustrating for me on my UK T Mobile stock 2.3.3 SGS2.
At first I wanted 1) a decent looking theme 2) with a camera shortcut and 3) music widget/player thing.
You don't know how hard it is to find these! Well from the official in app availible themes anyways.
*Even then with the music player, it's weird, as to activate it you have to click on a certain part of the lock (varies for each one).
When I finally found several I discovered 2 major major flaws. Can you guys try this and not/say it's just me?!
Play some music then lock the screen and now try to raise the volume.
For me using the physical volume buttons,
1) the screen turns on.
2) it only changes the volume by one (higher or lower).
How annoying is that?! Is this a problem with my phone or settings?
---------- Post added at 04:39 AM ---------- Previous post was at 04:13 AM ----------
^Try tried some of the pretty themes from the other thread and oh man they are so nice but I still have the same problem!
So anyone got time to help me out here or confirm they get the same results as me?
Thanks if you can help!
fl4r3 said:
So what I did was take the folder called 'advance' inside the 'lockscreen' folder and made it into a zip file (lockscreen.zip). Then I renamed it to remove the '.zip' extension. I deleted the 'lockscreen' folder from the .mtz file, dragged this file into the .mtz theme file and voila! The theme works!
Click to expand...
Click to collapse
Trying to follow your guide but confused...
1. If you zip 'advance' surely it becomes 'advance.zip' and not 'lockscreen.zip'?
2. What did you rename it to and with what extension?
3. The theme I have is zipped - do I change this to .mtz and is this then where you deleted the 'lockscreen' folder from?
Update: this is the theme which has me stumped http://forum.xda-developers.com/attachment.php?attachmentid=642540&d=1309491017
I have extracted it but there's no .mtz in there...?
How's everybody's battery react to using this app? Does your phone enter sleep the same frequency as the stock lock screen?
I always feel like I am getting a little bit of an extra drain, but after doing comparisons I think it is just in my head....battery drain paranoia.
Sent from my SCH-I510 using XDA App
i'd hate to beat a dead horse and spam but can you guys look at my problem too?
regarding battery drain i don't notice that much of an issue. i think there may be some but not really something that should be major.
chasingstatus said:
I do like MiLocker but man it's been frustrating for me on my UK T Mobile stock 2.3.3 SGS2.
At first I wanted 1) a decent looking theme 2) with a camera shortcut and 3) music widget/player thing.
You don't know how hard it is to find these! Well from the official in app availible themes anyways.
*Even then with the music player, it's weird, as to activate it you have to click on a certain part of the lock (varies for each one).
When I finally found several I discovered 2 major major flaws. Can you guys try this and not/say it's just me?!
Play some music then lock the screen and now try to raise the volume.
For me using the physical volume buttons,
1) the screen turns on.
2) it only changes the volume by one (higher or lower).
How annoying is that?! Is this a problem with my phone or settings?
---------- Post added at 04:39 AM ---------- Previous post was at 04:13 AM ----------
^Try tried some of the pretty themes from the other thread and oh man they are so nice but I still have the same problem!
Click to expand...
Click to collapse
The one I am using does turn the screen on but I can move the volume up and down with ease (more than one notch) throw me a link to one of the thees you are using and I will throw it on my Charge to see whats up
^Hey cheers for the reply but no need now!
In 1.3 they've fixed and acknowledged it was a problem.
"What's in this version:
(Feb.10, 2012，Version 1.3)
Support Android 4.0.
Support pattern password unlocking(need to enable "lock home key" in setting).
Support media keys.
Support volume key adjusting while playing music.
Fix some one-key lock related bugs on certain device models."
The screen still turns on though but that's something I guess I can live with. Cheers!
dead after reboot
I shutdown my phone over night with MIUI Locker installed and working. Started my phone this morning... no lockscreen. Enabled/disabled Miui Locker and it worked. had to kill the app properly between enable/disable but it worked.
Fix to make it work after reboot? I'm on CM7.2
greetings fellow XDA members.
need some professional help regarding the tabs' systemui.
i personally hate the system bar at the bottom, it takes up space which isnt really needed.
most of us would definitely accidentally pressed the buttons there while playing some games.
so what i usually do is to hide the system bar via honeybar.
problem is, no back home nor menu buttons. so i used an overlay. worked pretty well and soon enough i graduated to using GMD gesture control[awesome app]
now i have no system bar + freestyle gesture controls tailored to my own style.
the new problem is that since hiding the system bar simply kills systemui, i am unable to receive any notifications except toasts from su etc and using notification apps just doesnt work seamlessly like the systemui.
is there anyway to hide/kill system bar without killing the notification?
or better, is it at all possible to have a regular non tab status bar [aka top statusbar + pulldown notification] for our tab?
i apologize for being long winded, just trying to be detailed.
any help is appreciated. googling it gave diff answers not relating to tabs so im at a lost.
Only workable way I found was to
decompile framework-res.apk, track down dimens.xml and edit "status_bar_height" and "navigation_bar_height" = 0, depending on what dpi you use, I use 213 and that shows a combined bottom bar.
Its important to mention that since the combinedbar thinks its still there a transparent area still occupy the space when ex. in any dialogs that uses dimming you´ll see a area without dim, so esthetically all 3 backgroundDimAmount´s should be also set to 0 in /values/styles.xml.
Still any apps you open, will open in fullscreen and occupy entire screen..
There is a challenge if you dissable GMD, making it very difficult to return or manouver, unless I find a way to add back or home to the powermenu in CM9, which I haven´t yet..
This stops polluting catlog with systemui crashes every darn minute, wich bordered me from the beginning..
If you have ideas I am all ears
cheers!
thanks for the reply.
im a newbie when it comes to edting xml files, heck im not even sure how to decomompile the framework-res.apk but i'll tinker around for a lil bit and see what comes out of edting the files.
if its similar to editing xml files from within an apk, then i guess im safe since ive tinkered with an xml file that granted apps permission to save data to ext sd. thats a start i guess.
youve basically given me something to work with.
will get back here if i have any further queries or run into any problems with your stated workaround.
Sent from my GT-P6800 using XDA Premium App
Zulhitler said:
thanks for the reply.
im a newbie when it comes to edting xml files, heck im not even sure how to decomompile the framework-res.apk but i'll tinker around for a lil bit and see what comes out of edting the files.
if its similar to editing xml files from within an apk, then i guess im safe since ive tinkered with an xml file that granted apps permission to save data to ext sd. thats a start i guess.
youve basically given me something to work with.
will get back here if i have any further queries or run into any problems with your stated workaround.
Sent from my GT-P6800 using XDA Premium App
Click to expand...
Click to collapse
ok, if you need any help just pm me..
systemui.apk
biopsin said:
ok, if you need any help just pm me..
Click to expand...
Click to collapse
Hi, I'm not a tech geek, but interested in tweaking my tab, but if you please share your updated framework-res.apk so i can just replace it with mine :fingers-crossed:
vijay.alapati said:
Hi, I'm not a tech geek, but interested in tweaking my tab, but if you please share your updated framework-res.apk so i can just replace it with mine :fingers-crossed:
Click to expand...
Click to collapse
My framework is way to heavy slimmed for your likings, but I could rather make a specific one for your current os.
PS. there is some preparations:
1. you will need to setup GMD and assign home,back,show notifications and so on..(activate GMD notification icon (optional))
2. just in case, make important shortcuts on home to apps drawer, open notification, so on if GMD stops working
3. make a restore CMW package of current framework-res and SystemUI, you might change your mind
I have not mentioned this, but sometimes GMD will be unresponsive when waking up the device (worst case 20-30sec), therefore it is wise to have some sort of backup shortcuts of some kind if you can´t wait for it to restart..
(future focus : adding home or back to the powermenu if GMD would be switched off.)
If you are rooted and running the lastest CM10 (from Aorth) or CM10.1 rom, you can use the expanded desktop option:
http://www.youtube.com/watch?v=m1u2c_s1QaI
Not sure about getting notifications, will have to try that out later...
Since you're using GMD gesture control, why not set it to disable the notification bar on some apps, but leave it open for others? You could, for example, run "fullscreen" in everything but your home screen if you wished, and just go there periodically for notifications. I also found that if you make a custom gesture to show notifications, it will both reactivate the notification bar and then pop the notifications out. You can use that gesture and then re-hide the bar manually.
If you are rooted and running the lastest CM10 (from Aorth) or CM10.1 rom, you can use the expanded desktop option:
http://www.youtube.com/watch?v=m1u2c_s1QaI
Not sure about getting notifications, will have to try that out later...
Click to expand...
Click to collapse
As you say, he dosen´t show if notifications work, I will asume this still kills systemui in the background...
Since you're using GMD gesture control, why not set it to disable the notification bar on some apps, but leave it open for others? You could, for example, run "fullscreen" in everything but your home screen if you wished, and just go there periodically for notifications. I also found that if you make a custom gesture to show notifications, it will both reactivate the notification bar and then pop the notifications out. You can use that gesture and then re-hide the bar manually.
Click to expand...
Click to collapse
I experienced instability, it also consumes more battery when systemui is killed like this, and my logs got polluted with crash reports more or less every minute, therefore I looked for a solution to preserve both..
Hi guys
Back with a all new thing.
Feeling torch is eating battery or is of no use to see in dark.
Flash is not good or flaah is too shiny.
Here is a quick and simple solution fr all.
Now you have to be pre rooted and nothing else.
Use es file manager and brouse to /sys/class/flaahlight and there is a folder inside open it and in the fopder are two file to bf mooded
Strobe brightnesa and torch brightness.
add them to your favourits using es file manager so that you dont have to go such long to mod them.
Now a thing of importance plz check the max limit of both strobe and torch in the filea strobe max brightneaa and torch max brightnass.
These files will be in the same folder.
Hope you are helped by this now.
Now for those rare cases which do not have a screen brightness control bar can also try the mod just insted of flashlight folder go to backlight folder and mod the brightness file and adf it to favourits of es.
Peace
Sent from my SM-G355H using XDA Free mobile app
Hi there, I've about had it with the stock camera app automatically boosting brightness when it's launched. It's a nice feature when you're outside, but if you're inside it's way too bright. It makes scenes look brighter than they really are, causing under-exposed photographs. And it's super distracting in a dark room. I've spent a few hours looking through the APK and can't find a setting that would be controlling this auto-brightness behavior. But I'm not an experienced Android dev.
Almost all other camera apps have a toggle for this, but not the S7's.
I also spent a couple weeks fooling with Tasker to disable auto-brightness when the app is launched, the re-enable when exiting. The problem is the display brightness level is not consistent when AB is toggled off and sometimes the screen is way too dark or way too bright. Example:
1. Inside, display at 20% brightness.2. Launch camera app, Tasker disables auto-brightness, display stays at 20%.3. Exit camera app, Taske enables auto-brightness, display still at 20%.4. Go outside, display increases to 75% brightness.[here's where it gets whacky]
5. Launch camera app, Tasker disables auto-brightness, display drops to 20%.It's like the OS remembers the last manual brightness setting for an app. If there were a way in Tasker to freeze the brightness level before display auto-brightness, that'd be ideal. But I can't figure that out.
So, I'm requesting help from a developer(s) to find a solution. Either a foolproof Tasker recipe, or a modification to the camera app itself. Solution found. Read thread.
If you want payment for your efforts (assuming you find a solution), I'm happy to do that! :good:
Optimistically bumping this thread. It sucks that Samsung's closed-off everything has chased away so many devs from this device.
Ignore
Look in this file.
Camera.smali - For auto brightness change - 0x78 (120) to 0x1.
120 is the lower limit where brightness override kicks in.
I found the actual pictures the S7 takes are bright anyway so if the viewfinder is dull the actual image is brighter anyway. So I've left mine.
Just disable auto brightness when dark viewfinder is needed. It works even on the lowest level when auto brightness is disabled.
zeroprobe said:
Look in this file.
Camera.smali - For auto brightness change - 0x78 (120) to 0x1.
120 is the lower limit where brightness override kicks in.
I found the actual pictures the S7 takes are bright anyway so if the viewfinder is dull the actual image is brighter anyway. So I've left mine.
Click to expand...
Click to collapse
AWESOME. Where/How can I find this file to edit? I couldn't find it packaged in the APK but maybe I missed it...
mrmattolsen said:
AWESOME. Where/How can I find this file to edit? I couldn't find it packaged in the APK but maybe I missed it...
Click to expand...
Click to collapse
Make sure you have decompiled the APK. Good tool is AndroidMultiTool.
Might need to also copy the latest apktool to AndroidMultiTools Program Files directory.
zeroprobe said:
Make sure you have decompiled the APK. Good tool is AndroidMultiTool.
Might need to also copy the latest apktool to AndroidMultiTools Program Files directory.
Click to expand...
Click to collapse
I've tried this, but decompiling the APK does not reveal any smali files. What am I doing wrong? I tried checking "Use Baksmali" but get this error:
The system cannot find the path specified.
Exception in thread "main" org.jf.dexlib2.DexFileFactory$DexFileNotFound: zip file SamsungCamera5.apk does not contain a classes.dex file
at org.jf.dexlib2.DexFileFactory.loadDexFile(DexFileFactory.java:94)
at org.jf.dexlib2.DexFileFactory.loadDexFile(DexFileFactory.java:78)
at org.jf.baksmali.main.main(main.java:292)
Click to expand...
Click to collapse
mrmattolsen said:
I've tried this, but decompiling the APK does not reveal any smali files. What am I doing wrong? I tried checking "Use Baksmali" but get this error:
Click to expand...
Click to collapse
Are you decompiling your own Camera? This is probably an odexed rom.
The Camera needs to be deodexed, alternatively you can use my modded camera.apk here which should decompile.
http://forum.xda-developers.com/galaxy-s7/themes/zero-camera-mod-v1-0-increased-bitrates-t3439176
zeroprobe said:
Are you decompiling your own Camera? This is probably an odexed rom.
The Camera needs to be deodexed, alternatively you can use my modded camera.apk here which should decompile.
http://forum.xda-developers.com/galaxy-s7/themes/zero-camera-mod-v1-0-increased-bitrates-t3439176
Click to expand...
Click to collapse
Thanks so much. I used that apk, decompiled, found the smali file and made the edit. I recompiled and planned to use it to install your bitrate mod. However, I cannot rename the SamsungCamera5.odex or its folder -- access denied. Am I stuck? I've replaced the apk with the modded one, but I can't rename the odex. Can't replace media_profiles.xml either -- access denied too.
mrmattolsen said:
Thanks so much. I used that apk, decompiled, found the smali file and made the edit. I recompiled and planned to use it to install your bitrate mod. However, I cannot rename the SamsungCamera5.odex or its folder -- access denied. Am I stuck? I've replaced the apk with the modded one, but I can't rename the odex.[/Q
Do you use ES file explorer, you need to enable root explorer then click root explorer and set /system to rw mount
Click to expand...
Click to collapse
zeroprobe said:
mrmattolsen said:
Thanks so much. I used that apk, decompiled, found the smali file and made the edit. I recompiled and planned to use it to install your bitrate mod. However, I cannot rename the SamsungCamera5.odex or its folder -- access denied. Am I stuck? I've replaced the apk with the modded one, but I can't rename the odex.[/Q
Do you use ES file explorer, you need to enable root explorer then click root explorer and set /system to rw mount
Click to expand...
Click to collapse
I was using Solid Explorer. Could access some files. For example, was able to replace the camera apk, but other was denied. Tried ES too and can't enable Root Explorer. I'm not rooted, so am I screwed?
-edit- I take that back. Can't replace the camera apk either. Bummer. I guess that's that.
Click to expand...
Click to collapse
mrmattolsen said:
zeroprobe said:
I was using Solid Explorer. Could access some files. For example, was able to replace the camera apk, but other was denied. Tried ES too and can't enable Root Explorer. I'm not rooted, so am I screwed?
Click to expand...
Click to collapse
Yes you need to be rooted to change camera. I doubt the camera.apk has been replaced as you are not rooted. The only other way is to flash through custom recovery example TWRP
Click to expand...
Click to collapse
zeroprobe said:
mrmattolsen said:
Yes you need to be rooted to change camera. I doubt the camera.apk has been replaced as you are not rooted. The only other way is to flash through custom recovery example TWRP
Click to expand...
Click to collapse
Dang it. My hopes and dreams crushed. Thanks for you help anyways.
I guess I need to revisit the Tasker recipe...
Click to expand...
Click to collapse
Alright @zeroprobe, I rooted and used your instructions to modify the app. Works like a charm! Brightness now stays the same as my screen brightness. And now indoor photos are a million times better. I appreciate your help very, very, much. Sending a little PayPal love your way. Thank you for help!
mrmattolsen said:
Alright @zeroprobe, I rooted and used your instructions to modify the app. Works like a charm! Brightness now stays the same as my screen brightness. And now indoor photos are a million times better. I appreciate your help very, very, much. Sending a little PayPal love your way. Thank you for help!
Click to expand...
Click to collapse
Thanks a lot, appreciated !
Hi there!
The brightness issue with the camera app annoys me as well but unfortunately I have no rooted phone.
But is it possible that someone (e.g. @mrmattolsen) can send me the modified camera apk I can install? (my camera app version is 5.0.88) Will it work that way? ... and of course I would also send some appreciation via PayPal for your effort
best regards, Tom
Hey I know that other people have asked this sort of question before, but I was wondering if anyone can help me with setting up the Pixel/Pixel XL navigation bar animation on a none Pixel device (in my case Nexus 5X).
The reason I have started this thread is because I'm very suspicious of people when ever I see someone post a system modification for a device without explaining what they did to get there so I research things online and make my own version of they're system mod. Another reason is that asking these questions allows people to help me with my struggles and it expands everyone's knowledge on system modifications allowing everyone to create their own system mods or this same mod for their own device on any version of android.
Anyway the current things that I have found out is that the Pixel's SystemUI has a few extra files in the drawable folder (SystemUI.apk\res\drawable) they are
ic_sysbar_opa_blue.xml
ic_sysbar_opa_green.xml
ic_sysbar_opa_red.xml
ic_sysbar_opa_yellow.xml
Click to expand...
Click to collapse
they contain a information similar to these
<?xml version="1.0" encoding="utf-8"?>
<shape android:shape="oval"
xmlns:android="http://schemas.android.com/apk/res/android">
<size android:height="@dimen/opa_dot_diam" android:width="@dimen/opa_dot_diam" />
<solid android:color="#fffbbc05" />
</shape>
What this means:
Version of XML
Start of draw circle shape string
Thing
The size of the circle
Colour of the circle
End of string
Click to expand...
Click to collapse
This tells android to draw the little dots that appear when you press the home button on the Pixel. I have inported these files into my sytemui and was now wondering how to create the dots and make them move. I believe that this can be activated by finding out which file causes the home button to make that little ripple effect when you tap it and comparing it to find out what's different. So my question is at the moment is:
What file controls current home button animations (the home button ripple effect) on the Nexus 5X?
Click to expand...
Click to collapse
If any of you want the uncompressed versions of the Pixel's SystemUI and current Nexus SystemUI that I'm using then feel free too download them. (I have removed any unnecessary guff).
Edit: I think I have found the file. It's located at:
SystemUI.apk\res\layout\home.xml
Edit: I have edited the home.xml and it seems that it just cuases my SystemUI to crash. I believe this is caused by something else in the apk.
My current guess is that there is another file in the Pixels SystemUI that reads the xml file ic_sysbar_opa_colour.xml or home.xml
If anyone knows of a way I can search for those values in a large amount of xml files quickly, then please tell me.
No, It is not that simple. lots of things needs to modify, not only the res, dex code needs to patch, the one that detect the assistant and trigger the animation.
The worse thing is, if you do anything wrong, you have to use the twrp to restore the phone...
Charles_l said:
No, It is not that simple. lots of things needs to modify, not only the res, dex code needs to patch, the one that detect the assistant and trigger the animation.
The worse thing is, if you do anything wrong, you have to use the twrp to restore the phone...
Click to expand...
Click to collapse
I've edited the navigation bar in the SystemUI before without any problems. I know what you mean by resetting the phone if I mess anything up because I messed up a few things while editing the framework.apk but I haven't run into any problems with the dex file before.
Jackio987 said:
I've edited the navigation bar in the SystemUI before without any problems. I know what you mean by resetting the phone if I mess anything up because I messed up a few things while editing the framework.apk but I haven't run into any problems with the dex file before.
Click to expand...
Click to collapse
The dev that figured out how to enable the animated nav bar for the Nexus 5 posted this I hope it helps
http://forum.xda-developers.com/goo...-fake-nexus-rom-nexus-5-t3466736/post69496350
kevtrysmoddin said:
The dev that figured out how to enable the animated nav bar for the Nexus 5 posted this I hope it helps
http://forum.xda-developers.com/goo...-fake-nexus-rom-nexus-5-t3466736/post69496350
Click to expand...
Click to collapse
I noticed that someone else has done it before, (it's on page 120) link:
http://forum.xda-developers.com/goo...t/rom-fake-nexus-rom-nexus-5-t3466736/page120
Click to expand...
Click to collapse
And that inspired me to ask how it was done. Another thing is that I have a nexus 5X and he has a nexus 5 which both have different processor types (arm and arm64). I also tried flashing his zip which as you would of guessed caused my phone to crash as soon as the phone had booted up requiring me to factory reset it. I might try flashing the zip onto a phone that has an arm processor (my moto g 2nd generation running cyanogenmod 14 beta) and figure out how to export it to my Nexus. Anyway I have asked qitt the guy that made the original nav bar animation for the nexus 5 work how he did it and he still hasn't responed.
Also taking a look at it, it seems that the Pixel's SystemUI and qitt's SystemUI are almost identical with only about a 200 byte difference.
Jackio987 said:
Hey I know that other people have asked this sort of question before, but I was wondering if anyone can help me with setting up the Pixel/Pixel XL navigation bar animation on a none Pixel device (in my case Nexus 5X).
The reason I have started this thread is because I'm very suspicious of people when ever I see someone post a system modification for a device without explaining what they did to get there so I research things online and make my own version of they're system mod. Another reason is that asking these questions allows people to help me with my struggles and it expands everyone's knowledge on system modification allowing everyone to create their own system mod or this same mod for their own device on any operating system.
Anyway the current things that I have found out is that the Pixel's SystemUI has a few extra files in the drawable folder (SystemUI.apk\res\drawable) they are
they contain a information similar to these
This tells android to draw the little dots that appear when you press the home button on the Pixel. I have inported these files into my sytemui and was now wondering how to create the dots and make them move. I believe that this can be activated by finding out which file causes the home button to make that little ripple effect when you tap it and comparing it to find out what's different. So my question is at the moment is:
If any of you want the uncompressed versions of the Pixel's SystemUI and current Nexus SystemUI that I'm using then feel free too download them. (I have removed any unnecessary guff).
Edit: I think I have found the file. It's located at:
SystemUI.apk\res\layout\home.xml
Edit: I have edited the home.xml and it seems that it just cuases my SystemUI to crash. I believe this is caused by something else in the apk.
My current guess is that there is another file in the Pixels SystemUI that reads the xml file ic_sysbar_opa_colour.xml or home.xml
If anyone knows of a way I can search for those values in a large amount of xml files quickly, then please tell me.
Click to expand...
Click to collapse
I'm working on same and I'm willing to help you .. it's quite a surprise why despite so many ppl being there, none have managed to figure this one out. I'm also moderately knowledgeable about the subject so I just might be Able to help you. Can you share the systemUI.apk file for pixel?
raghavsharmaxda said:
I'm working on same and I'm willing to help you .. it's quite a surprise why despite so many ppl being there, none have managed to figure this one out. I'm also moderately knowledgeable about the subject so I just might be Able to help you. Can you share the systemUI.apk file for pixel?
Click to expand...
Click to collapse
Here you go.
I got this by flashing the Pixel's system.img onto my Nexus 5X extracting the entire system partition then re flashing android 7.1.1 beta. I have also included the .obex files in the system_other.img that comes with the Pixel's factory image.
I'm just wondering if it's as simple as changing the name of the Pixel's SystemUI, the AndroidManifest.xml, the meta-inf, the .odex and anything else related to application identification to get it working. The reason I say this is because qitt claims to have done this and I've taken a look at what he has done and it seems that there is basically no different between the Pixel's SystemUI and his in terms of file and folder layout. One problem is that qitt's SystemUI is optimized for the Nexus 5 which has a arm based processor not a arm64 one like the nexus 5x meaning that we just can't install it.
Here is qitts post
http://forum.xda-developers.com/goo...t/rom-fake-nexus-rom-nexus-5-t3466736/page120
Just create a flashable zip of systemui with animated navbar ( from 26/10 ). Try it if you want. Worked for me on 1/11 Fake Nexus. All credits to author this ROM ganachoco.
Attached Files
File Type: zip Pixel_NavBar.zip - [Click for QR Code] (11.56 MB, 856 views)
Click to expand...
Click to collapse
Jackio987 said:
Here you go.
I got this by flashing the Pixel's system.img onto my Nexus 5X extracting the entire system partition then re flashing android 7.1.1 beta. I have also included the .obex files in the system_other.img that comes with the Pixel's factory image.
I'm just wondering if it's as simple as changing the name of the Pixel's SystemUI, the AndroidManifest.xml, the meta-inf, the .odex and anything else related to application identification to get it working. The reason I say this is because qitt claims to have done this and I've taken a look at what he has done and it seems that there is basically no different between the Pixel's SystemUI and his in terms of file and folder layout. One problem is that qitt's SystemUI is optimized for the Nexus 5 which has a arm based processor not a arm64 one like the nexus 5x meaning that we just can't install it.
Here is qitts post
http://forum.xda-developers.com/goo...t/rom-fake-nexus-rom-nexus-5-t3466736/page120
Click to expand...
Click to collapse
I'm wondering how to solve the signature problem after modifying the AndroidManifest.xml?
Charles_l said:
I'm wondering how to solve the signature problem after modifying the AndroidManifest.xml?
Click to expand...
Click to collapse
I really want to just flash the files and then start editing from there but since my 5X is my personal device and if there are any stuff ups with this installation it meas that I have to factory reset my device which isn't that great if I have to do it every time I flash the file. I also don't want to make a TWRP backup and just recover from that when I'm all finished be cause every time I have done that my data partition always stuffs up basically causing me to factory reset again.
Testing this could become a slow and repetitive process
Ok I have figured out how to keep my devices data intact so I can flash the systemUI.apk over and over again without having to factory reset my device, now it's time to get this thing working.
Jackio987 said:
Ok I have figured out how to keep my devices data intact so I can flash the systemUI.apk over and over again without having to factory reset my device, now it's time to get this thing working.
Click to expand...
Click to collapse
If you keep the apk signature, when you get systemui fc, you can always replace the original apk file with TWRP, reboot and everything back to normal.
Jackio987 said:
Ok I have figured out how to keep my devices data intact so I can flash the systemUI.apk over and over again without having to factory reset my device, now it's time to get this thing working.
Click to expand...
Click to collapse
I have succeeded in porting all res and smali things to 5X's systemUI which is related to Assistant.
Process by now, the sendOpaBroadcast refuse to work.
issue:
Code:
11-11 11:58:02.915 D/AssistManagerGoogle(3038): New assistant: null
Charles_l said:
I have succeeded in porting all res and smali things to 5X's systemUI which is related to Assistant.
Process by now, the sendOpaBroadcast refuse to work.
issue:
Code:
11-11 11:58:02.915 D/AssistManagerGoogle(3038): New assistant: null
Click to expand...
Click to collapse
Do you have the new google assistant enabled?
If not then you can change your build.prop to get it working
Code:
change
ro.product.model=Nexus 5X to ro.product.model=Pixel
and add
ro.opa.eligible_device=true
somewhere into the build.prop then flash it or push it back onto the device.
This might be useful since the little circles the home buttons draws are called
ic_sysbar_opa_colour.xml
Click to expand...
Click to collapse
and the build prop tells the device that you can use opa with this line
ro.opa.eligible_device=true
Click to expand...
Click to collapse
Charles_l said:
I have succeeded in porting all res and smali things to 5X's systemUI which is related to Assistant.
Process by now, the sendOpaBroadcast refuse to work.
issue:
Code:
11-11 11:58:02.915 D/AssistManagerGoogle(3038): New assistant: null
Click to expand...
Click to collapse
Also can you tell us how to got the System UI's nav bar working, if it does work after you have changed the build.prop
Jackio987 said:
Also can you tell us how to got the System UI's nav bar working, if it does work after you have changed the build.prop
Click to expand...
Click to collapse
What did you do with build.prop, if you add a line in it to enable some settings, the setting doesn't turn off when you delete the line, you have to set the value to 0 of what you have added.
Good news, now I got the home button animation, though the four dots didn't appera.
I might need the Pixel phone user setting, if I can't override the Opa_Enabled settings.
Charles_l said:
What did you do with build.prop, if you add a line in it to enable some settings, the setting doesn't turn off when you delete the line, you have to set the value to 0 of what you have added.
Good news, now I got the home button animation, though the four dots didn't appera.
I might need the Pixel phone user setting, if I can't override the Opa_Enabled settings.
Click to expand...
Click to collapse
Here goes the build.prop from the Pixel if it helps.
Jackio987 said:
Here goes the build.prop from the Pixel if it helps.
Click to expand...
Click to collapse
Thank you but no need, after analysising Google App, I found a way to get systemUI turn on the OPA animation switch. I will start a new thread for details.
Charles_l said:
Thank you but no need, after analysising Google App, I found a way to get systemUI turn on the OPA animation switch. I will start a new thread for details.
Click to expand...
Click to collapse
Can you please make a tutorial on this so we can port it to other devices like my moto g 2014 or a nexus 6P or future updates to the nexus 5X.
Charles_l said:
Thank you but no need, after analysising Google App, I found a way to get systemUI turn on the OPA animation switch. I will start a new thread for details.
Click to expand...
Click to collapse
I worked on this for week but no luck .. if you have figured out how and do know the exact reasons, let me know..thank you
PS- don't back and restore /data all the time. Simply replace the apk and grand permissions from aroma file manager which can manipulate data from recovery itself.