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

Root [ROM] DroidSmith_Force - Beta

oh god, connection optimizer? really? i hate that thing its always messing up the mobile data connection. to do the phone apk though it is a real pain, i know i have done it myself on the warp2, you cant rebuild it because of zte's shotty coding. the solution although not exactly elegant, is to figure out what is causing the errors, im gonna assume that its certain spanish strings, and the touchui xml file. delete the touchui file that gives you issues, copy any other file, then rename it to the actual name of the touch ui file, and delete the bad strings from the correct strings.xml

you will see a readout whenever you run a recompile, itll say W:whatever warning, those dont matter, its the E: things starting from the top you have to worry about, warnings will still let it build. identify the strings by line number, i think its :599 means its line 598 is the problem or something im not really sure anymore but youll figure it out, hell you can delete a whole section of them if you really want it wont matter kuz you wont be using that file

once you get it to rebuild the thing, open it up in an archive manager, its basically just a glorified zip file so it wont be a problem, the problem is its encoded so you cant edit it directly like that, youll want to take the files you modified from the apk you just built, and toss them and only them in the original apk you started with

i know its a horribly painful workaround but it does work and it seems to be the only option
 
software on your computer is irrelevant its a matter of horrible coding by zte, they always do that, use my method and it will work. i had the same issue and managed to get it removed from mine
 
You nailed it on the head sir. Ill run through it tonight following your instruction. There were alot of coding errors on the warp that had to be corrected, but it was nowhere near as bad as this.
 
oh one more thing, make sure if it says the error is in values-es you dont go looking in values and changing that strings.xml. i confused myself there a couple times. you should be good to go though, fake the incall_touch_ui.xml in layout, delete the strings the build tells you are bad, then rebuild and copy whatever you customized from one apk to the original like they were zip files. done deal
 
yea, they were bad at making gb roms, now they wanna try to hack together copies of ics and jb with the same horrible coding... that makes our job so much harder
 
If I remember correctly the issue I was having. On recomplie other than the es strings was that itemsnwefe declaired in public.XML and not defined in the strings. Is there an easy way to remove the entries in the public.xml without messing up all of the hex code? In my work with gingerbread apktool would always place a "dummy" in the place of items that had no definition. This is my first stab at ics, and as we stated earlier gb was no where near this goofed up
 
umm, im not really sure, i didnt think something being defined in public and not strings would really be an issue. what is the exact string of error messages after removing the bad strings?
 
k, kuz itll throw warnings yes but those wont stop the build, and every time it throws an error, every warning listed after that is labeled as an error instead of a warning. you should be able to get away with just removing the bad strings and faking the other stuff outside the values directory. everything inside values cant be faked though

just remember all you need to do is force it to build with your mods in, as long as the modded files are intact that is all that matters kuz ur just gonna be stuffing them into the original phone.apk after its all packed up
 
I wasn't asking to leave connections optimizer in, I was just wondering what it did and why you guys hate it. And what sdcardchameleon is.
 
connection un-optimizer automatically tries to connect you to open wifi networks, even when wifi isnt supposed to be on. isnt that a great feature? lets force enable wifi at all times, and on top of that momentarily interrupt your internet connection every time we see a new network... lol, their attempt to unload mobile traffic onto wifi basically, its horrible. and sdcardchameleon is some proprietary thing i dont remember what it does, i know the chameleon provider is to stop you from tethering without paying for tethering service and make sure you use sprint proxies though, it also has something to do with mms and if you remove it you will break the rom
 
I wasn't asking to leave connections optimizer in, I was just wondering what it did and why you guys hate it. And what sdcardchameleon is.


Not sure what sdcardchameleon is, but if you would like to help out you could delete it and let me know what if any adverse effects happen. If not I understand. Only input from you guys is driving development at this point. Once I buy the phone I will be able to accomplish more on my own.
 
software on your computer is irrelevant its a matter of horrible coding by zte, they always do that, use my method and it will work. i had the same issue and managed to get it removed from mine

That took care of it. One string deleted and it recompiled with only a few warnings. I can believe that I have never ran into an issue like that before. Thanks a million.
 
0.2.2 is up. Thanks goes out to Junkie2100 for help with the phone.apk, chevanlol360 for his work with faceunlock on the sequent, and to all of you for testing and providing input.

Connections optimizer has been removed from the settings menu. I've also made another attempt at getting faceunlock to work. I did some work to the updater script which should allow me to install apps to the data partition. This will be handy in the future for adding user requested apps.

Edit: found an error I had made in the updater script. I pulled the link, and 0.2.3 will be up soon. Sorry guys
 
I can wait to get my Force cause ima flash it walking out the store. Have poot ready with terminal emulator and rom on a sdcard :)
 
Back
Top Bottom