• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] [ROM] Warp OEM 2.70

I applaud your dedication to the details, it will be nice to have a rom that gives the look and feel of the high end phones. On behalf of all of us, I thank you for your efforts and cant wait to take this baby for a ride! ;)

Well dude we all here appreciate all your hard work and time you spend on it...... Kudos dude......:thumbup::rock:
Thanks, guys! That's what keeps development rollin'!

Speaking of which, I encountered a slight issue which caused my latest build to bootloop. Oops.

Back to the drawing board... :hmmmm2:
 
Well, it took a complete rebuild - from scratch, no less! - but I finally got the bootloop fixed. I have a couple other tweaks, then I'll pretty much be down to just the mods which require recompiling APKs, which may take some time. Soon I'll post a partial changelog of features that have been implemented thus far.

Goodnight, all!
 
Well, it took a complete rebuild - from scratch, no less! - but I finally got the bootloop fixed. I have a couple other tweaks, then I'll pretty much be down to just the mods which require recompiling APKs, which may take some time. Soon I'll post a partial changelog of features that have been implemented thus far.

Goodnight, all!

Any update? I am liking what I am seeing.
 
Any update? I am liking what I am seeing.

Updates were slow for several days there since I got backed up at work and took last weekend off from dev work (cabin in the middle of nowhere for the win! :D) But I've been back at it since I got home from work last night (minus a nap, of course lol) but I still can't figure out this stupid framework issue. I've tried everything I know! It's just not working :banghead:
 
OK. Didn't mean to come across sounding pushy. Just checking on ya. Sorry can't help with the framework issues.
 
OK. Didn't mean to come across sounding pushy. Just checking on ya. Sorry can't help with the framework issues.

It wasn't taken that way at all :) It's just that this is getting really frustrating. I can decompile / recompile regular APKs, just not framework-res.

I think it's time to make an official separate help thread on this!
 
It wasn't taken that way at all :) It's just that this is getting really frustrating. I can decompile / recompile regular APKs, just not framework-res.

I think it's time to make an official separate help thread on this!

Hit some of the other Dev's up with a PM;)
 
Hit some of the other Dev's up with a PM;)

I've tried several! They've come up with several good answers, but alas none have gotten me anywhere so far :(

Not meaning that as a hit to the other devs, though! It's just that something just doesn't click when I try it, and seemingly no matter how I try it.
 
I've tried several! They've come up with several good answers, but alas none have gotten me anywhere so far :(

Not meaning that as a hit to the other devs, though! It's just that something just doesn't click when I try it, and seemingly no matter how I try it.

Just some of the reasons I myself dont do dev, work.!!;):p:D:rolleyes:
 
Just some of the reasons I myself dont do dev, work.!!;):p:D:rolleyes:

Ugh, I hear you, Bit!

But this weekend wasn't a total loss! I transferred nearly my entire development tool suite over to Virtuous Ten Studio, and actually managed to get an APK or two recompiled. My main thing with this version is optimization, optimization, optimization; and, to that end, I implemented a number of default settings mods. The out-of-the-box Warp OEM now has WiFi disabled, automatic screen brightness enabled and non-market sources enabled.

As I promised everyone earlier in the thread, here's a list of the new features which have been completed or started thus far:

-------------

integrated complete B10G firmware update (including patched amss, dbl and osbl, minus bloat and spyware)

modified hosts file to integrate ad-blocking

modified init.arthur.rc in ramdisk for flashlight fix

modified system_conf.xml to enable the battery-saving "automatic brightness" setting by default

modified default_names.xml to remove extra Boost contacts

Modified SettingsProvider.apk:
-enabled installation of non-market apps by default
-WiFi is now off by default

modified mms.apk: (in progress - needs tested)
-changed text highlight color to blue
-changed link color to red
-changed text size to 14 point
-changed “attached” to “attachment” in attachment actions menu
-increased message-per-thread limit from 5000 to 8192
-changed supported image size from 640x480 to 2560x1920 (near QSXGA-level HD support)
-increased max MMS attachment size to 2MB
-made SMS automatically convert to MMS if greater than 160 chars to stop SMS split-up
-allowed requesting message read receipts

themed Status Bar (SystemUI.apk):
-added custom signal meter icon set
-added custom service indicator icon set
-modified wi-fi icons when data not syncing
-modified vibrate mode icon
-added custom battery icon set with state of charge numbering
-added custom battery charging icon set
-modified battery charging idle and low icons
-modified TTY icon font to Nasalization
-modified other miscellaneous icons
-added gradient in status bar header with "Warp OEM" text
-modified status bar pulldown handle
-modified charging image
-changed notification colors
-removed carrier name

themed framework-res.apk:
-added custom default wallpaper
-replaced text selection handles with ICS versions
-replaced “missing app” icon with ICS version
-modified jog tab bars to blue
-modified loading spinners to blue
-modified sync icons to blue
-modified ECB mode icon font to Nasalization
-modified dialog alert icon
-modified dialog info icon
-modified voicemail icon
-modified download icon
-modified USB file transfer image


...among others :)
 
You can has update!

The recompilation issue is solved!!! Because of that, half of the extended power menu mod is done - framework-res.apk is completed and working! YAY! Next up: android.policy.jar.

Wish me luck :D
 
This file is proving to be easier to work with, but I'm still having a slight issue. The power menu appears, along with icons and everything, but when you select something that was added, nothing happens in the case of the screenshot option, or you get a partial reboot for the other two.

Hmm...
 
It's 2AM... I'm tired... it's bedtime... I'm going to bed... no... WAIT! One more edit! ONE MORE BUILD! Just one. I promise. Please?

Aaaaannnnnnnnywayyyyyy... here's the summary of tonight's APK editing and pushing session, A.K.A. "dev work" lol



The WOEM settings menu just got another overhaul. This time, I'm redoing the layout and adding options, more custom icons and hopefully some other fun things :)

I probably won't finish this until tomorrow night, but fear not - screenshots are to come!
 
Merc, how about dropping the word "discontinued" form the title of this thread. Maybe say "working on rev 2" or something.

I get nervous when I see the discontinued word
 
Merc, how about dropping the word "discontinued" form the title of this thread. Maybe say "working on rev 2" or something.

I get nervous when I see the discontinued word

I agree, need a new thread title Merc.:p

*smacks head* I can't believe I forgot to do that! I was thinking about what to say and everything...

Oh well... fixed!


Trust me, after all this work I'm putting into it there's no way I'm discontinuing it now lol
 
Nooo, no risk of that! This dev is alive and well!

...well, except for being severely time-pressed and sleep deprived lol


But enough about that. IT'S UPDATE TIME!!

Behold: WarpOEM's new settings menu and all its bundled features :D

Features?! New features, you say?? Why, yes indeed! I took all the commonly used settings across all the essential apps (No-Frills, the launcher, and a couple others) and rolled them into one easy to access place. Now you can do everything from fine tune your launcher to overclock your CPU, all right from the settings menu.

But wait! There's more! lol

As complete as it may look, I plan on adding another few features to it in the end, so look for a couple surprises in the finished product :)

Hey, it's better than the menu looked stock lol
 

Attachments

  • 1.jpg
    1.jpg
    117.9 KB · Views: 135
  • 2.jpg
    2.jpg
    127.9 KB · Views: 142
  • 3.jpg
    3.jpg
    117.8 KB · Views: 120
  • 4.jpg
    4.jpg
    122.4 KB · Views: 114
Tonight's update: I think I finally solved the power menu issue. Well, solved may be a little hasty... we'll go with "pinpointed."

Apparently I misconstrued the information in this post way back when, and have been focusing on editing only two of the needed three files ever since. The power menu mod does in fact use all three files to work properly, as it even says later in that very post! Duh.

Hopefully now I can get some interesting things going on this part of WOEM 2!
 
UPDATE!!!
*sings* I've got an uuuuupdate, another uuuupdate... [/singing]

The power menu works! After this long of a fight, I feel the need to repeat myself:

THE *expletives deleted lol* POWER MENU WORKS!!
:dancing::party: :dancing:


There are probably some other devs out there who will facepalm after reading how elementary of a solution this was, but for me this was a big win. I've always felt completely out of my element when it comes to the internals of Android, but I'm starting to learn. And that gets me excited! So bear with me... lol

So my earlier conclusion was correct, framework.jar did need modified as well to complete the mod. After locating exactly what code would need imported, I did so and hit compile only to get an error message. The code compiled fine when my additions were commented out, but as soon as one of the two major chunks were reactivated, boom! Compile error. So I studied (or just stared dumbfoundedly at :p) the code. And studied. And read, and learned. Smali assembly turns out to not be that far removed from the good old computer-based assembly I'm used to. So applying the logic I did know to the things I didn't know, I came to the conclusion that somewhere in what I was adding lie something that was conflicting with the existing code; judging from previous experience, I figured it was a line label. A quick search proved this correct - sure enough, there was a duplicate ":cond_0" label in one of the methods in ShutdownThread. Apparently the new changes that ZTE made in the B10G update caused their compiler to add a line label that seemingly wasn't present in the previous firmware versions. I gave all three line labels in the code I was including their own unique names and compiling was suddenly successful :D After a quick ADB push, victory was mine!

So, the basics are in place. As per the tutorials I've been following (attacking?) I now have Reboot, Recovery and Bootloader added to the menu, and all function perfectly. As you've probably come to expect with me, however, I'm not done with it yet - I think I'll remove Bootloader since it's really not something used on a daily basis, and I still need to add the Screenshot option as well. But this is a start! And it sure is nice to see some results after staring at code I began totally unfamiliar with.

And also, once everything's all said and done, I intend to write up some step-by-step detailed tutorials on how I did this and the settings menu mods. That way other beginners won't have to slough through all the stupid little details as I'm finding myself doing.

Until next time... goodnight, everyone :)
 
  • Like
Reactions: Doc
Back
Top Bottom