MIUI.us DefX - 2012.11.11 - Aroma Installer, HBM Updates

[aaronc222]

I haven't actually updated the full Miui portion since December. I tried through the end of February / beginning of March, but all of them had CDMA so broken it wasn't worth releasing. Instead I've been adding things and trying to get things more stable. Currently I've been digging into the stock Blur code to see how Moto did things specific for our phone (like Deep Sleep) and porting them in. It's a ton of work in smali, but it's well worth it in the end.

If you want a way to quickly force yourself to learn smali, take something like CM7 that's open sourced, sync the repo and make sure you can compile it. Then find a class that is similar between the two (diff the smali from the compiled CM7 and Miui). Then try to convert the smali to Java and make the CM7 java class match. You'll have to compile it, then compare the smali again (and probably have to repeat until you get it just right). I've learned more in the last month porting the Deep Sleep code out to Java to help CM7 and eventually ICS than I have the entire time leading up to it.

If you haven't worked with smali before, let me know. I'll post links for the tools you'll need and some good links that help to understand what the smali commands are.

Thank you. I haven't used smali before so any links would be great if you want to pm me. The CM7.2 Inc 2 build is pretty stable so I'll definitely go off of that. I'm sure the crowd will appreciate it if I can get it together.

[wizard0f0s]

Thank you. I haven't used smali before so any links would be great if you want to pm me. The CM7.2 Inc 2 build is pretty stable so I'll definitely go off of that. I'm sure the crowd will appreciate it if I can get it together.

Sorry, I haven't forgotten about you, I just got slammed. I'm going to post the links here so anybody that wants them can find them.

For learning and working with smali:

http://http://developer.android.com/reference/dalvik/bytecode/Opcodes.html - This site is really good when you are reading the error messages from logcat. You'll see things like this error (below). Notice the line that includes "rejecting opcode 0x6e at 0x01a3". This site is where you look up the opcode (0x6e in this example) to see which smali command it's actually talking about. Just do a search on the page for 6e and you should be able to find it. The page actually lists it as 0x0000006e (invoke-virtual).

W/dalvikvm( 1885): VFY: register1 v0 type 2, wanted 6
W/dalvikvm( 1885): VFY:  rejecting call to Landroid/os/IPowerManager$Stub;.shutdown (ZZLjava/lang/String;)V
W/dalvikvm( 1885): VFY:  rejecting opcode 0x6e at 0x01a3
W/dalvikvm( 1885): VFY:  rejected Landroid/os/IPowerManager$Stub;.onTransact (ILandroid/os/Parcel;Landroid/os/Parcel;I)Z
W/dalvikvm( 1885): Verifier rejected class Landroid/os/IPowerManager$Stub;
W/Zygote  ( 1885): Class not found for preloading: android.os.IPowerManager$Stub

http://pallergabor.uw.hu/androidblog...k_opcodes.html - This is a great place to learn what the opcodes actually do and some information about syntax, etc. If you aren't a Computer Science person, this information can be a little hard to understand. Keep referencing it though as you will get a feel for what it means and it will help out tremendously at that point. You can search for either the opcode or the command (6e or invoke-virtual respectively, still using the example above). You will find the following information (although that site lays it out better than I can here).

6E
invoke-virtual { parameters }, methodtocall
Invokes a virtual method with parameters.
6E53 0600 0421 - invoke-virtual { v4, v0, v1, v2, v3}, Test2.method5:(IIII)V // method@0006
Invokes the 6th method in the method table with the following arguments: v4 is the "this" instance, v0, v1, v2, and v3 are the method parameters. The method has 5 arguments (4 MSB bits of the second byte)5.

The information in the last box is extremely important to understand (and what sets this site apart from the first). This information actually helps you read the smali and understand what it means.

Now for some tools so you can actually get to the smali.

JDK
The very first thing you need is the Java JDK. You can download it from oracle here - http://www.oracle.com/technetwork/ja...k-6u31-oth-JPR. Currently you have to stay with Java 6 as 7 is not supported yet. The JDK also includes the JRE, so you don't need to download and install it separately.

Android SDK
Next you need to get the Android SDK from here - http://developer.android.com/sdk/index.html. If you don't know it already, learn how to use ADB. ADB will be a life saver for you and makes things SO much easier. For example, if you are making some changes to framework.jar, you don't have to repackage the whole rom, zip it, move it to your phone, flash it, realize you broke something, make a code change and repeat the whole process. Just make your change to framework.jar and use "adb push framework.jar /system/framework/" to push the new file to the /system/framework/ folder. Depending on the change you make, you may need to reboot your phone. If it breaks something, just push the original framework.jar file back to it. You can also get into your phone via adb before it finishes booting. So if you get stuck in a boot loop, you can usually just adb in and fix it.

adb remount
adb push framework.jar /system/framework/
adb shell chmod 644 /system/framework/framework.jar

That would be what you would actually run to remount the /system/ partition as read-write instead of read-only, then push the new framework.jar file to /system/framework/, then set the rights on the file to 644 (rw-r--r--). You can also use "adb shell" by itself to get command line access to your phone (this is where knowing Linux REALLY comes in handy).


Smali & Baksmali
You'll need to download smali and baksmali from here - http://code.google.com/p/smali/. You will use these extensively to rip jar files down to smali and then reassemble them back to jar files.


APKTool
http://code.google.com/p/android-apktool/ - Apktool is a tool you will also use a great deal. You can use it to decompile both jar and apk files and recompile them. Be aware though, there are times that it does not keep everything that was in the original jar or apk file. Just watch for this and you will be ok.

Apktool will need you to import the framework-res.apk files before you run it. To do this, just run "apktool if framework-res.apk". If there are multiple *-res.apk files in /system/framework you will need to do this on each one. Once you've done that, the basic commands are "apktool d package.apk" to decompile it and "apk b folder" to build it. You can run "apktool d package.apk folder" to extract it to a specific folder and "apk b folder package.apk" to build the folder to a particular package.apk name. Here is an example for working on the Browser.apk file.

apktool d Browser.apk Browser

This extracted the Browser.apk to the Browser folder.

apktool b Browser Browser-new.apk

This compiled the Browser folder to a new apk called Browser-new.apk.

Notes
These are just some notes off the top of my head. They are a little random, but it is little things that may be helpful.

* If you don't use Linux now I highly recommend it. Ubuntu is pretty popular, but I prefer Fedora myself. Fedora does a full release upgrade 2 to 4 times a year. If you don't keep up, you end up losing updates to your software. That's probably the worst thing with Fedora. The best though is that it is easy to work with and learn. I would also recommend KDE instead of Gnome as your desktop. KDE is more familiar for anyone not already used to Linux (and I hate the Gnome 3 desktop anyway). If you go with Fedora, you'll want to get the RPMFusion repos setup from here - http://rpmfusion.org/. Fedora can not officially offer some packages (like NVidia drivers) so they are hosted on RPM Fusion instead. The repos are basically just sites that maintain a package list of what they have available. So if you run "yum search nvidia" you get a list of available packages that include "nvidia". I'm a hardcore command line guy for most things, but Fedora also has lots of Gui (graphical) tools for packages (yumex is my favorite gui package tool). Just do a google search for linux distros and you'll find a ton of options. Fedora specifically is here - http://fedoraproject.org/ Using linux will give you the ability to script a ton of your jobs (like running apktool against the entire /system/app directory instead of doing it manually).

* I highly recommend scripting your commands. For example, to baksmali framework.jar you would have to type "java -jar /home/jeg5592/bin/baksmali-1.3.2.jar framework.jar -o framework" (/home/jeg5592/bin/baksmali-1.3.2.jar is where my baksmali.jar file is located). I've scripted it into a script called bsmali.sh so all I type is "bsmali.sh framework.jar framework".

* Use something like CM7 as a reference as well to help understand the smali code. Pull down the repo for CM7 and get where you can compile it yourself (it does take a while to compile). You can compile it and compare the smali there to what you have in Miui. Most of the time it will be very similar or exactly the same (all based off of AOSP after all). When sections are the same, you can look back at the CM7 source code to have an easier time reading what the smali is actually doing.

* The fastest way to learn smali is by converting it back to Java. Pick a class (like PowerManager) and convert the Miui smali into Java in CM7. Follow the functions calls, etc to make sure all of it matches. Compile it and then compare the new CM7 smali to the original Miui smali. Where does it still differ? Change the Java code and try again. You will get a much better feel for it this way and will force yourself to learn it faster.

Ok, that's all I can think of at the moment. I'll post again if I think of anything else.

Edit - Forgot the link for apktool. Added it to the apktool section.

[wizard0f0s]

Ok, I ran out of available characters. Here's an addition to the Android SDK section


Another useful way to use adb is for logcat. If you run "adb logcat" you will get a running log of what is occurring on your phone. If you start it close to the time your phone booted, you will get the full log from boot time until you stop logcat from running. If you are running linux, open 2 terminal windows. In the first window type:

touch logcat.log
tail -f logcat.log

This creates a new file called logcat.log in the first command. The second command tells your system to show the last few lines of the log (which is blank) and to continue to show lines that get added.

Now in the second window, type the following:

adb logcat > logcat.log

You will now see lines flow past in the first window. Depending on how long the phone has been booted up, they will fly past and then slow down as you see the current events. If you would rather see what happened as the phone booted, simply press Ctrl-C in the first window to stop the tail. Now open the logcat.log file with your favorite text editor. For example, if you are running kde, you can type:

kwrite logcat.log &

This will open the logcat.log file in kwrite. The & symbol tells it to open kwrite as a separate thread, allowing you to continue using the terminal for other things.

[aaronc222]

*bows down before you*

This will help immensely. I do have a background in CS (mainly C# as of late), have used various forms of linux since it came out, and spend my days as a lvl 2 deskside support tech for a major firm. So 90%+ of it makes perfect sense and the rest seems sensible enough that I think trying it out will make me go 'oh, that's what he meant...'.

I'll have to give Fedora a go. I've been dual booting Win 7 (gotta get my Diablo 3 fix in) and Ubuntu and the new interface does bug the crap out of me enough that I'm mostly in Windows lately (of course the crack they call Diablo 3 might have something to do with that too ).

I'm sure once I get my dev environment set up I'll have some questions. The only one that's burning right now would be does it hurt to use bootmanager to have a 'stable' main and 'development' slots? I would think the only drawback would be speed but thought I'd ask before I get too far in.

[wizard0f0s]

*bows down before you*

This will help immensely. I do have a background in CS (mainly C# as of late), have used various forms of linux since it came out, and spend my days as a lvl 2 deskside support tech for a major firm. So 90%+ of it makes perfect sense and the rest seems sensible enough that I think trying it out will make me go 'oh, that's what he meant...'.

I'll have to give Fedora a go. I've been dual booting Win 7 (gotta get my Diablo 3 fix in) and Ubuntu and the new interface does bug the crap out of me enough that I'm mostly in Windows lately (of course the crack they call Diablo 3 might have something to do with that too ).

I'm sure once I get my dev environment set up I'll have some questions. The only one that's burning right now would be does it hurt to use bootmanager to have a 'stable' main and 'development' slots? I would think the only drawback would be speed but thought I'd ask before I get too far in.

No issues at all with boot manager. I went that route until I started working on bootmenu. That changes things prior to BootManager kicking in.

Sent from my DROIDX using Tapatalk 2

[onlyred]

It's possible that the stock cpu settings are to low.
Hold power button and hit reboot/bootmenu and open cpu settings and change yours to the following.

BOOSTEDassV2 gov
clk1 300
clk2 600
clk3 800
clk4 900
vsel1 18
vsel2 31
vsel3 41
vsel4 61
Scroll to the bottom and hit save
Then back out and go back into cpu settings and make sure your changes are there.
Back out and select reboot.
See if that is stable enough to keep yours from rebooting

teleported from MI Wizardry UI DXtreme

I was also having hiccup-y video problems, so I did this and now my battery life is.. horrid. I calibrated, like I always do, and it's toast. Can someone post the old settings so I can go back? Last night I went to bed with my batt at 46% and it was dead as a doornail when I woke up. I haven't made a single change to any apps, nor added any - the only thing that changed was those settings. I should just sbf and start clean but I have zero time for that right now, need my phone up and running for my job, which at the moment is 7 days a week..

[clothednblack]

I will look for the original settings, but those settings that you used are better battery settings, you have something else draining your phone, Google maps and Widgets are the worse.

teleported from MI Wizardry UI DXtreme

[jsauder2]

I've had times were my phone will get stuck on 1000 even if I didn't have that as a level. that will make it drain crazy fast. usually a reboot fixes that. it could be apps but that seems crazy that an app would suck 46% overnight. unless the GPS got stuck on our something like that.

Sent from my DROIDX using Tapatalk 2

[onlyred]

Thanks guys.. I don't know what happened with those settings, but I cheated and reinstalled 5/12 to reset them, my battery had drained 3x in one day - with the previous settings, it was doing much better. I use my phone heavily all day, so I expect fast drops, especially if I open facebook, but my phone really hated those settings. I'm gonna guess either I need to start fresh or I have an app running that's truly annoyed by those settings. I don't run the cleanest setup as far as widgets, but I have a car charger to make up for that lol

In case anyone else needs to reset their settings, the og settings were:
300
600
800
1000
24
35
45
55

[Kajun4288]

Hello Wizard & Clothednblack,

I was wondering if Wizard has done any work on Miui roms for the razr? My X is run 5.12 great, but I needed the dual core & upgraded. My sister now has my X, so the rom is still used & loved. So I was wondering if y'all working on a razr rom or worked with or knew anybody who did? If so please let me know because I would really like to have a Good working Miui to use again. Thank y'all!

[clothednblack]

I'm not sure if wizard has shared any of the tweaks or bootmenu with a dev that's working on the rzr, I will find out.

teleported from MI Wizardry UI DXtreme

[wizard0f0s]

Nope, but I'd be more than happy to. I'm not sure who is deving on it. If they're interested, just send them my way.

Sent from my DROIDX using Tapatalk 2

[slicnic911]

so, i just installed this rom coming from an ics one (too much doesn't work right).
I kept the default theme but installed the black android lockscreen and unchecked to change background. now, there is nothing on my lockcreen so i cannot even unlock it or do anything. if i call the phone i can still answer but once i hang up it goes back to nothing but my background. any way to resolve this with a format? i had just finished getting my apps installed and settings the way i like, too
thanks!

edit: problem resolved. gracias!

[clothednblack]

Glad you got it fixed, black android lockscreen does not get along with this Rom, just for future reference, you can hold the back key and volume down to unlock the lockscreen if you ever run into another theme that causes issues. I think it was those two keys lol, been a long time since that's happened.

teleported from MI Wizardry UI DXtreme
Edit: back + volume up

[XeroBass]

First time poster, long time viewer of the forums here.
Big thanks to Wiz for continuing the DX GB Miui goodness.

Glad you got it fixed, black android lockscreen does not get along with this Rom, just for future reference, you can hold the back key and volume down to unlock the lockscreen if you ever run into another theme that causes issues. I think it was those two keys lol, been a long time since that's happened.

teleported from MI Wizardry UI DXtreme

I had ran into a similar issue the other day after updating the android black theme (lock screen is a separate theme load.) I had remembered about the button unlock ability (menu + vol down ) and unfortunately it doesn't work in the current build... Instead the screen re-runs the on animation. I did end up finding another way to break through the lock screen, as I didn't want to format/reinstall.

[clothednblack]

First time poster, long time viewer of the forums here.
Big thanks to Wiz for continuing the DX GB Miui goodness.



I had ran into a similar issue the other day after updating the android black theme (lock screen is a separate theme load.) I had remembered about the button unlock ability (menu + vol down ) and unfortunately it doesn't work in the current build... Instead the screen re-runs the on animation. I did end up finding another way to break through the lock screen, as I didn't want to format/reinstall.

Back + volume up works

teleported from MI Wizardry UI DXtreme

[slicnic911]

Thanks for your responses. I honestly don't how I got it to finally get to the pattern screen but in the future I will use back and volume up.

Two questions concerning the rom:
Does anyone have camera focus problems? It will not focus at all. I have to put it in infinity or macro and the move the phone closer to or further away to "manual" focus.

Also, when I pull down the notification window the time and battery disappear. How can I make those stay put. Even better, how can I make it display the date in the status bar with the notification window open?

Thanks so much for your help! While I loved the looks and customizations of the ICS roms, they were no substitute for everything working like it mostly does on this rom.

[jsauder2]

Thanks for your responses. I honestly don't how I got it to finally get to the pattern screen but in the future I will use back and volume up.

Two questions concerning the rom:
Does anyone have camera focus problems? It will not focus at all. I have to put it in infinity or macro and the move the phone closer to or further away to "manual" focus.

Also, when I pull down the notification window the time and battery disappear. How can I make those stay put. Even better, how can I make it display the date in the status bar with the notification window open?

Thanks so much for your help! While I loved the looks and customizations of the ICS roms, they were no substitute for everything working like it mostly does on this rom.

I use pro-capture for my camera, so can't help you on that one...

For the date issue...go to MIUI Control Panel -> Statusbar options -> Date format options -> Notification bar date format. However you format it, is how it will show when you pull down the statusbar. All the different formatting options are listed below the input windows.

I'm not sure there is a way to keep the battery there, at least not that I know of.

Sent from my DROIDX using Tapatalk 2

[clothednblack]

Time will disappear when the bar is pulled down, just how it is, as for the battery, if you use the top bar option for your battery indicator, it will stay. There isn't a work around unless you use a third-party battery monitor app.

teleported from MI Wizardry UI DXtreme

[jsauder2]

Time will disappear when the bar is pulled down, just how it is, as for the battery, if you use the top bar option for your battery indicator, it will stay. There isn't a work around unless you use a third-party battery monitor app.

teleported from MI Wizardry UI DXtreme

it will disappear unless you set it up through MIUI Control Panel. you can format it any way you want for date/time options there.

Sent from my DROIDX using Tapatalk 2