Database Users

[Q] Replacing build.prop?

hi!
in order to test something, i need to replace the build.prop in root/system with a modified one. but trying to delete this file with astro manager displays an error message, and just copying the modified build.prop over the old one doesn't work too (nothing happens).
so my question is: how do you replace such a file?
thanks in advance for your help

are you serious!?!?!?
If the build.prop is located on the Android folder IT HAS TO BE A SYSTEM FILE !!!
if you mod the system files you could break android or the system just won't let you do it, you will need R and W privileges to do that.
edit the system files from your PC or just boot up in to windows mobile.
use some common scene next time.
hope it helps!
Sent from my HTC HD2 using XDA App

Do you use a cyanogen build?

yes and there is already a cyanogen rom posted with the proper build.prop fixed, so you won't have to edit anything, just search for it.
Sent from my HTC HD2 using XDA App

mmmh actually cyanogen made things easy to replace a system file, just copy your file into sdcard/android/root/system and reboot.

thanks for your help / posts. but unfortunately they're not helpful.
yes, i am serious! and yes, of course it's a system file. i know as well that modification might brick android.
there are reasons for modifying this file. some people seem to be able to, e.g. for chaning screen point density or modify the data passthrough.
so, please tell me, how can i edit/modify a system file from pc or windows mobile when its within the data.img-file?
thanks for any tips / hints on this.

use root explorer

Sichroteph said:
mmmh actually cyanogen made things easy to replace a system file, just copy your file into sdcard/android/root/system and reboot.
Click to expand...
Click to collapse
Thank you VERY much for your help - I finally got it to work by listening your instructions. It is simply different if you have HD2 and plus CM mod. That figures why it was going back all the time to 180 instead of changing it - because it runs from sd card and that's where it needs to be replaced as well ...

Droid Explorer

[Q] How to edit theme images and not have phone hang on boot?

I've figured out all apk files are really just zip files, but why am I not able to unzip the framework-res.apk file, edit the images within, then save it again without causing my phone to hang on boot?
Is there some step I am missing? I've tried rezipping with normal compression, store only, and only photoshopping and resaving a single image within the apk and still it fails.
How are images edited and updated? What am I missing?

I use apkmanager myself for most theming. You might look into it
Sent from my SCH-I500 using XDA App

An apk is a zip, but it's a *signed* zip
Sent from my SCH-I500 using XDA App

Here is the way I do it. I use 7zip to do this and I think it is the only program that can do it.
The way you can do it is to extract the drawable-hdpi folder within the framework-res.apk then do all your edits and save them with the exact same file names. Then you can go back into your framework-res.apk and drag and drop the drawable-hdpi folder back in and it will over write the original ones. Now just hit the Up (like to move up a directory) button until you see the message "framework-res.apk has been changed. Update it in the archive?" then click yes. Now you can put it on your phone without force closing. If you were just editing framework-res and it was not within another .zip file then you won't get that message and that is fine.

APK Manager.
You can use extract/zip (2/3) for image-only edits, but you need to decompile/compile (9/11) to mess with xml files.
Do *not* sign system apks (like framework-res.apk). Do sign other apks.
Btw, this is in the wrong forum.
(Next step: learn about the update.zip packaging script. Remember to name it something besides update.zip afterwards, because on the Fascinate we're installing everything through Clockwork, which should be the only file actually called update.zip.)

s44 said:
APK Manager.
You can use extract/zip (2/3) for image-only edits, but you need to decompile/compile (9/11) to mess with xml files.
Do *not* sign system apks (like framework-res.apk). Do sign other apks.
Click to expand...
Click to collapse
Oooh! I didn't know this app made xml's editable. That opens up a whole new set of theming fun. I can't wait to release my new theme. It should be well received (I hope)
Btw, this is in the wrong forum.
Click to expand...
Click to collapse
I considered putting this in Themes, but this was a theme development question, so here it ended up. If the Theme and Development forums ever hook up and have a few drinks, then spawn a sub-forum, Theme Development, I assure you it would have been a much easier decision to make

Thanks everyone for helping me out. My last time playing with a phone is an old WinMo 5 device. Anroid seems limiting in it's own ways (no dedicated theme files (can't update without losing the apk theme), but much better for customizing for a 'look' of the OS.

[MOD] Add top number row to Swype

Hello guys,
Since I use a Samsung device, I'm used to the extra number row on top of the keyboard so I modded Swype to have that extra row. However since Swype is to be purchased and not distributed, I'll only tell here how to do it for your legally purchased copy. And this is a bit complicated and for advanced users and you need to be rooted. You also need Root Explorer. Here we go:
1- First buy/download Swype from Google Play.
2- Go to /mnt/asec/com.nuance.swype.dtc-1 folder, copy pkg.apk to your sdcard, rename it to com.nuance.swype.dtc-1.apk.(keep a backup of this file at all times)
3- Go to /mnt/asec/com.nuance.swype.dtc-1/lib folder copy the files (libnmsp_speex.so and libswypecore.so) to your sdcard.
4- Using apktool (I used version 1.52) decompile com.nuance.swype.dtc-1.apk.,
5- Go to decompiled folder\res\xml folder. kbd file pertaining to your language is to be edited, I edit kbd_qwerty.xml for English using Notepad++.
6- Check the attached kbd_qwerty.xml in portrait folder and notice the extra row section I added to the top. You can in fact add secondary characters to numbers or customize the keyboard completely, rearrange letters, add symbols etc.
7- Once done, save the file and go to decompiled folder\res\xml-land folder and edit the landscape for the layout, kbd_qwerty.xml file, notice the attached file in landscape folder.
8- Once done, save the file and go to decompiled folder\res\values folder and edit the dimens.xml file. Here I raise the height of the keyboard and height of the key to 270dip and 54dip respectively, check the top rows of the attached dimens.xml. Also increase the keyboard height for landscape (if you want) by changing the dimens.xml under res\values-land folder.
9- Once done, recompile the folder with apktool, go to decompiled folder\dist folder and copy the apk here to a different folder and rename it to temp.apk.zip
10- Open temp.apk.zip with 7z/winrar and copy the resources.arsc and kbd_qwerty.xml files from res\xml and res\xml-land folders to your PC(obviously keep the 2 files in seperate folders not to overwrite)
11- Then, rename the original apk from step 2 to com.nuance.swype.dtc-1.apk.zip , open with winrar and first delete resources.arsc file, then drag the resources.arsc file from step 10 to the archive, it will be added. Staying in winrar, go to res\xml folder and replace the file with kbd_qwerty.xml from step 10 (the portrait version). Do the same with res\xml-land folder and the landcape file.
12- Once finished rename the file back to com.nuance.swype.dtc-1.apk, don't sign it, don't delete META-INF folder, leave it as it is.
13- Now, on your phone, uninstall Swype. Reinstall it from the apk file on Step 2. Go to /data/app-lib/com.nuance.swype.dtc-1 folder and move the 2 files (libnmsp_speex.so and libswypecore.so) to system/lib folder. You have to mount the System R/W from Root Explorer on this step. Fix the permissions so these 2 files have the same permissions with other files there. If you can't find these files just use the ones from Step 3.
14- Once done, copy com.nuance.swype.dtc-1.apk from Step 12 to /system/app and fix the permissions so that it has the same permissions as other files there.
15- Then delete the com.nuance.swype.dtc-1.apk from /data/app/ folder. Restart your phone.
This should be it if you followed it exactly, tracing and Dragon voice dictation also works. While you're doing all this work (takes 10 minutes by the way), you might also consider changing how Swype looks (theming) and changing many other things like swype thickness, colors etc. Please note that this is for advanced and rooted users and please don't ask me to give you the modded apk, you have to do it on your legally bought version. You might consider doing backups just in case anything goes wrong. Have fun.
And a quick tip: if you swype from swype icon to symbol key(123), arrow keyboard opens up.
You can also add arrow keys by copying arrow keys from kbd_edit.xml, check the 2nd screenshot.
Please hit the thanks button if you think this is useful.

Nice how to. But may u should tell that the latest Android versions store purchased apps in data/app-asec as asec version, this need special procedure to get a apk from the asec format.

Can you please update this tutorial to 4.3 ? I couldn't find the files in the mentioned paths. . I'm on stock rooted 4.3 on gt9500
Sent from my GT-I9500 using XDA Premium 4 mobile app

lesalloum said:
Can you please update this tutorial to 4.3 ? I couldn't find the files in the mentioned paths. . I'm on stock rooted 4.3 on gt9500
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It works same for me on 4.3 stock rooted i9500, maybe you could do a file search to find the necessary folder. Here is another screenshot with the updated Swype(1.6.2.22328), where I made number buttons smaller like original Samsung Keyboard and hide the suggestions bar to save space.

ozkaya said:
Hello guys...
9- Once done, recompile the folder with apktool, go to decompiled folder\dist folder and copy the apk here to a different folder and rename it to temp.apk.zip
....
Click to expand...
Click to collapse
using the current play store version (1.6.3.22544), i decompiled com.nuance.swype.dtc-1.apk (/mnt/asec/com.nuance.swype.dtc-1/pkg.apk) using APKTool 1.52. i made no changes and attempted to recompile without success.
the first error displayed by apktool is:
"C:\Users\Phil\apktool\com.nuance.swype.dtc-1\res\values\arrays.xml:545: error: Found tag dimen-array where item is expected"
i do use APKTool successfully to mod other apps so i am familiar with the process.
QUESTION: what frameworks file are you using when making your mods? are you using a TW ROM frameworks? that's the only other variable i can think of...
EDIT: well, i just tried using TW framework too without success

PhilDX said:
using the current play store version (1.6.3.22544), i decompiled com.nuance.swype.dtc-1.apk (/mnt/asec/com.nuance.swype.dtc-1/pkg.apk) using APKTool 1.52. i made no changes and attempted to recompile without success.
the first error displayed by apktool is:
"C:\Users\Phil\apktool\com.nuance.swype.dtc-1\res\values\arrays.xml:545: error: Found tag dimen-array where item is expected"
i do use APKTool successfully to mod other apps so i am familiar with the process.
QUESTION: what frameworks file are you using when making your mods? are you using a TW ROM frameworks? that's the only other variable i can think of...
EXIT: well, i just tried using TW framework too without success
Click to expand...
Click to collapse
Latest version of Swype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.

ozkaya said:
Latest version of Skype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
Click to expand...
Click to collapse
i'll give this a shot tomorrow, thanks a lot!

ozkaya said:
Latest version of Swype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
Click to expand...
Click to collapse
it works!!!
thanks man, appreciate the help and info!

I've been going nuts trying to edit swype for a week now and still can't seem to get it to work. All I want to do is change the suggested word color and maybe a few other minor color related things. I assumed just changing the color codes in /res/values/styles.xml that seemed to pertain to the holo theme would work but I can't ever get the app to install. Not even sure where to begin to ask for help on this one but if anyone has any advice I'd greatly appreciate it.

Ok I've tried this a hundred times following all the steps completely and it just wont work.
Once I go to install the final apk it always tries to install then sais App Not Installed.

TeknoGodz said:
Ok I've tried this a hundred times following all the steps completely and it just wont work.
Once I go to install the final apk it always tries to install then sais App Not Installed.
Click to expand...
Click to collapse
You don't install the final apk, in fact you can't since the certificate is no longer valid. You copy the final apk in place as in Step 14.

I would love this! I have used Swype for years but I would love a number row. To be honest I have no idea how to follow those instructions! I have a rooted phone - what can I do?

Am I right in concluding that you can't use TB to backup and restore the finished product and this will have to be done manually? I did this on my rooted Note 3 and I keep going back to my stock image because I don't want to have to keep doing the steps when I flash a new ROM or ROM update.
Would I maybe just have to do steps 12 onward every time?

mr.BeBoT said:
Am I right in concluding that you can't use TB to backup and restore the finished product and this will have to be done manually? I did this on my rooted Note 3 and I keep going back to my stock image because I don't want to have to keep doing the steps when I flash a new ROM or ROM update.
Would I maybe just have to do steps 12 onward every time?
Click to expand...
Click to collapse
When you install a new ROM, you install original Swype from apk file then you move the lib files to /system/lib, copy the modded apk to /system/app and delete original apk from /data/app folder. So it is 4 steps once you have the modded apk ready, should take no more than 5 minutes.

thumm138 said:
I've been going nuts trying to edit swype for a week now and still can't seem to get it to work. All I want to do is change the suggested word color and maybe a few other minor color related things. I assumed just changing the color codes in /res/values/styles.xml that seemed to pertain to the holo theme would work but I can't ever get the app to install. Not even sure where to begin to ask for help on this one but if anyone has any advice I'd greatly appreciate it.
Click to expand...
Click to collapse
This is similar. Please go through the steps, you don't (can't) install the modded apk, you move it in place.

ozkaya said:
This is similar. Please go through the steps, you don't (can't) install the modded apk, you move it in place.
Click to expand...
Click to collapse
Yeah I realized that after I posted and still nothing. I'm no programmer but I've never NOT been able to change a few things and recompile. Not sure how just changing a few color codes is causing such a problem. Shame such a nice keyboard has such little customization and few themes. Don't get me wrong I like orange but it really doesn't mesh at all with the rest of the UI. Thanks for the reply though.

ozkaya said:
This is similar. Please go through the steps, you don't (can't) install the modded apk, you move it in place.
Click to expand...
Click to collapse
I did all that and it changed the height of the keyboard, but didn't add any additional number row.
kdb_qwerty or whatever it's called is the default that comes up when you install it, right? Becuase I tried again and specifically made sure to use this one and it just wont give me the extra row, just the height.

TeknoGodz said:
I did all that and it changed the height of the keyboard, but didn't add any additional number row.
kdb_qwerty or whatever it's called is the default that comes up when you install it, right? Becuase I tried again and specifically made sure to use this one and it just wont give me the extra row, just the height.
Click to expand...
Click to collapse
It depends on your system language. Try kbd_qwerty_panlatin.xml.

ozkaya said:
Latest version of Swype has incompatible tags with Apktool. What you do is go to all the lines that give error and change them to <string-array>. Then it compiles.
Click to expand...
Click to collapse
Thank you for this change, this is exactly what I was looking for to compile.
Once again my Swype is blue!!! :victory:

here's my creation, what do you guys think?
the theme is "Lucid" from the pay store: https://play.google.com/store/apps/...lucid&pcampaignid=APPU_8szYUoedK9PNsAThnoDQDQ

Boot animations

I am trying to change the boot animations with no luck thus far can anybody point me in the right direction, I am rooted and have Xposed framework , Wanam, and Rom toolkit all installed. Thanks in advance for the help

Skip Richmond said:
I am trying to change the boot animations with no luck thus far can anybody point me in the right direction, I am rooted and have Xposed framework , Wanam, and Rom toolkit all installed. Thanks in advance for the help
Click to expand...
Click to collapse
You need to use a Root Explorer type app. There are 2 files in system/media that need to be replaced with the 2 boot animation files you want to use. The 2 files are: bootsamsungloop.qmg and bootsamsung.qmg.

airmaxx23 said:
You need to use a Root Explorer type app. There are 2 files in system/media that need to be replaced with the 2 boot animation files you want to use. The 2 files are: bootsamsungloop.qmg and bootsamsung.qmg.
Click to expand...
Click to collapse
going to give it a try with a different file explorer tried it with ROM toolkit and didnt work and im new to rooting so it is definetly a user error just inexperenced

Still no luck
Skip Richmond said:
going to give it a try with a different file explorer tried it with ROM toolkit and didnt work and im new to rooting so it is definetly a user error just inexperenced
Click to expand...
Click to collapse
I still dont know what I am missing....

I assume you meant "ROM Toolbox" because I don't see "ROM Toolkit" in the market. ROM Toolbox has dozens of bootanimations to choose from. If you see one you like, you should be able to install it within ROM Toolbox. It has been a while since I used it to change bootanis, but I think it was a pretty simple and self-explanatory process. If you want to change bootanis manually, you have to go to
/system/media and swap these files:
bootsamsung.qmg
bootsamsungloop.qmg
bootsamsungmini.qmg
bootsamsungminiloop.qmg
And set permissions to rw-r--r--
Sent from my Rooted SM-N900V using Tapatalk

sublimaze said:
I assume you meant "ROM Toolbox" because I don't see "ROM Toolkit" in the market. ROM Toolbox has dozens of bootanimations to choose from. If you see one you like, you should be able to install it within ROM Toolbox. It has been a while since I used it to change bootanis, but I think it was a pretty simple and self-explanatory process. If you want to change bootanis manually, you have to go to
/system/media and swap these files:
bootsamsung.qmg
bootsamsungloop.qmg
bootsamsungmini.qmg
bootsamsungminiloop.qmg
And set permissions to rw-r--r--
Sent from my Rooted SM-N900V using Tapatalk
Click to expand...
Click to collapse
The boot animations in ROM Toolbox are in the bootanimation.zip format that need to go in either /system/media or /data/local folder. Unfortunately, with Samsung Touchwiz, the required format is the qmg format.
I'm not 100% sure how it is now, but it used to be that the kernel needed to support the bootanimation.zip format in order to be used (or a deeper system/framework support) Most AOSP based ROM/kernels have this support by default but TW doesn't allow this to work.
There's a thread in the theming section that has several of these files to use, but aren't of the greatest quality, IMO.

I used the international bootanimation files from this thread
[Stock] International Note 3 Bootanimation
Sent from my Rooted SM-N900V using Tapatalk

Building first ROM for G900V

Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake

jake5253 said:
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
Click to expand...
Click to collapse
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the response!
It seems perhaps I didn't quite make clear what I've done versus what I'm trying to accomplish.
Firstly, I wouldn't go so far as to say I'm "having so many issues". Everything in my ROM is in perfectly fine working order. I just have these few quirks that I would like to address both so I can learn, and to make this and future projects better.
While I appreciate the recommendation to use bean's base, I have taken a look at his and there seems to be nothing in his which copies data into /data/data/com.whatever.package (or at least there's nothing in his zip in the /data/data folder -- not sure if his ROM has the toggle activated?)
I have the Apps working correctly in my ROM -- they just go in /data/apps, /system/app or /system/priv-app, respectively.
What I need, is to get /data/data/com.whatever.package/ copied With Correct Permissions when the ROM is installed; I do not want a second zip to update things after install, especially for a toggle and a couple shortcuts, seems silly.
For instance, when you boot your phone up with the default [stock] samsung launcher, it has a list of default apps and widgets on the first screen you see such as phone, messages, a clock widget, etc, etc. Since I've replaced the stock launcher with Holo Launcher HD and some other default apps have also been replaced, there's very few shortcuts on the main launcher screen.
** Holo Launcher does have a list of default apps it adds to your main page, but many of those have been removed in my rom.
The solution I've come up with basically waits for the system to boot up to the point that Holo Launcher actually creates the default (mostly blank) /data/data/com.mobint.hololauncher.hd/databases/launcher.db and then my script uses sqlite3 to update the DBs with a list of different shortcuts -- ones to apps that actually exist.
The Hotspot Toggle is the same way as above.. Hotspot works fine in my rom if you go through settings!
I just cannot add the notification panel pull-down toggle to /data/data/com.android.providers.settings/database/settings.db until after the system boots up at least ONE time, and then update the DB to include WiFiHotspot in notification_panel_active_app_list and notification_panel_active_app_list_for_reset
As for the zipalign and deodexing, I will have to try those again now that I have a fairly stable rom.
****EDIT****
I think I figured it out. I can just use busybox to kill the systemui after I update the databases during the first boot. I also figured out how I can add the SetupWizard without it locking up on activation.
Thanks anyways, guys.
Look for my rom, coming soon!
=P

Please add support for more languages
I found a mod for Motorola latest 4.4 please port it
Sent from my SM-G900T using XDA Free mobile app