DXMD3 Stock Jelly Bean Phabletized!
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Screenshots:
They're big. There are many, Unhide to see.
Mostly just showing off the Samsung apps. From my experience, most apps are a lot easier to handle on a bigger dpi. Again, if on some apps you don't like the change...go with Xposed framework.
Undoubtedly you'll notice how the fonts in the Settings app seem smaller than the rest of the rom and the alarm clock app seems bigger. You're right. They are. That's Xposed + App settings hard at work. I want the alarm clock buttons big when I'm smacking the **** out of my tab in the morning (300dpi) and don't need the big fonts when I'm fiddling with the settings (160dpi).
By the way, don't mind the "25% brightness" (I had it at -28% on some other screenshot). That's just Lux. It helps keep the display at a comfortable level in the dark. A screen filter basically. I also found this and this very helpful on a big screen and fiddly-sometimes-hard-to-press-when-your-hands-are-messy-when-cooking-and-just-need-to-look-at-the-recipe-one-more-time buttons (the other two persistent notifications).
Coming soon: Flashable zip. I'll get around to it, I promise. Having trouble scripting the thing. Take a look at the help wanted section if you think you can help. Thanks.
It is wonderful seeing someone try to create something for our Tablets...
I wish I could help in your efforts but instead I can only thank and applause you...
Good luck...
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
zip
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
edan1979 said:
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Click to expand...
Click to collapse
Doesn't e-robot have some issues? I got the distinct feeling it wasn't quite so stock. I might be wrong though.
EDIT: Now I remember! I couldn't get over the flickering wifi icon in the status bar. Annoyed the **** out of me. Trivial, I know. I could live with something not working quite right if it wasn't visible most of the time.
{Diemex} said:
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Click to expand...
Click to collapse
Good tip. Thanks!
vivalamoza said:
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
I'll take some and post asap.
konsolen said:
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
Click to expand...
Click to collapse
Can this create a single zip for multiple apps or is it one app = one zip?
It creates one ZIP file. So exactly what you looking for.
Just a quick update:
I'm working on a cwm flashable zip that would back up the original apk and odex files and copy the new ones in place. Plus, I've been toying around with other versions of system apps.
I will be posting everything in the next few days - after I test it out.
Cheers
paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) Restart
13) If you have any issues with any of the apps, first try clearing their caches and data.
Click to expand...
Click to collapse
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
obeguin said:
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
Click to expand...
Click to collapse
Never heard of LCDDensity before, but I'll add it to the instructions.
You're correct, the phablet ui starts at 180 (176 I believe), but the navigation bar keys are off center when lcd density is not set to 213.
Sort of defeats the purpose of phablet ui for me. Personally, I changed to a smaller dpi (for a smaller status bar - 195) and removed the navigation bar with the qemu.hw.mainkeys switch. I mainly navigate thru gestures (using GMD Gesture Control) anyway.
Again, you're correct. But when starting out on a freshly flashed rom, some might happen to skip the part where they connect to the wifi or connect their google account. Besides, I've seen Play being hesitant to install and update on it's own - sometimes it requires you to launch it before you get update notifications and automated app downloads which requires a launcher. I want the instructions to be as foolproof as possible. That's why I'll be making a separate flashable zip with a custom home and keyboard, just in case.
On that topic, do you know anything about scripting? I'm having trouble with the update script. Check out the first post.
You can try this note 8 samsung keyboard, it work on both tablet and phablet ui.
http://forum.xda-developers.com/showthread.php?t=2228836
Sent from my GT-P6800 using XDA Premium 4 mobile app
paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Click to expand...
Click to collapse
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
vivalamoza said:
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
Click to expand...
Click to collapse
My suggestions:
You sure you're rooted?
You might have free space issues. Try disabling and uninstalling the apps from titanium backup and then pasting the apps in place. Samsung roms are pretty huge and fill the available space almost to the limit.
Pasting sometimes didn't work for me when the apps were running. Try closing them from a task manager. I always did the modding after a fresh boot on a fresh rom.
I hope this is helpful.
Related
Just wondering if there is a mechanism for running a custom post install script after flashing a rom, specifically CM.
There are things that I always do after I flash a rom and it would be nice to be able to do these as a part of the flashing process, so I don't forget. For example, symlinking /system/etc/hosts to /data/data/hosts. I also would like to remove the videos app as it serves no purpose since the 3D gallery displays my videos in it.
It would be awesome if I could have a script on the SD card that would just get executed right before reboot after the rom was flashed.
A bit less elegant than what you're suggesting, but I just made an update.zip to do that symlinking. Have to apply it with ROM Manager after flashing (so an extra reboot when flashing a new rom), but it beats booting into recovery and doing it by adb.
Link if anyone is interested: http://oysteivi.tihlde.org/adfree-symlink.zip
With this flashed, the "adfree android" app seems to work nicely when I tick "symlink from /data/data/hosts".
Didn't feel a need to remove the videos app, but it should be easy to add it in there. Just add something like this to the update-script in the zip:
delete SYSTEM:app/Videos.apk
(untested, and you'll have to replace "Videos" with the actual apk name. I'm too lazy to check what it is )
This is pretty much what I was looking for, thanks a lot!
Hi there,
Thanks a lot, due to this zipfile I finally got adfree working appropriately.
zorro
I have a Captivate I just upgraded to, from a BlackBerry. [FINALLY]
After reading around for a week or two on XDA it's about time I ask the questions I've been searching so long for.
It's a couple questions, but I have no idea:
I'm running the latest Cognition rom. Though it's nice and all, can I have my old boot animation back? How?
Ever since I started researching Android and their themes, I've fallen in love with chancellorr's minimalist themes, notably this one from his deviantART account: http://chancellorr.deviantart.com/gallery/26259232#/d33q9jd. I've been trying to get his setup ever since I started. Help please?
How do I use MetaMorph? I'm not sure if it's the main theming app for Android, but it's nothing like Winterboard on the iPhone, I have no idea what I'm doing! Help with that too, please?
What's the nicest and most customizable launcher for Android?
Anything else I might need to know to help further customize my Captivate? What I should be worried about, and how I can prevent issues loading themes and the like.
Thanks for helping me out, loving this Captivate so far
bugmenever said:
I'm running the latest Cognition rom. Though it's nice and all, can I have my old boot animation back? How?
Ever since I started researching Android and their themes, I've fallen in love with chancellorr's minimalist themes, notably this one from his deviantART account: http://chancellorr.deviantart.com/gallery/26259232#/d33q9jd. I've been trying to get his setup ever since I started. Help please?
How do I use MetaMorph? I'm not sure if it's the main theming app for Android, but it's nothing like Winterboard on the iPhone, I have no idea what I'm doing! Help with that too, please?
What's the nicest and most customizable launcher for Android?
Anything else I might need to know to help further customize my Captivate? What I should be worried about, and how I can prevent issues loading themes and the like.
Click to expand...
Click to collapse
1. Yes; the boot animation resides in /system/media/bootanimation.zip. To replace it, put the new bootanimation.zip on your SD card and move it over with root explorer. Should you not have root explorer, run the commands below via AndroidSDK/tools (put the bootanimation.zip in the /tools folder too)...
Code:
adb push bootanimation.zip /sdcard/
adb shell
su [i](should change from a $ to a #, dont forget to accept superuser on the phone too)[/i]
cp /sdcard/bootanimation.zip /system/media/
exit
exit
adb reboot
2. As this seems to be designed for a different device, it would require decompiling the frameworks and such and porting them over to captivate-esque code; that would work with the captivates framework.
3. This thread should teach you how to MetaMorph.
4. It's a matter of opinion. The two big ones are Launcher Pro and ADW.Launcher, both come with their own advantages and disadvantages. Want a transparent app drawer background? ADW. Want to hide apps in the app drawer? LauncherPro. Best way to find which one you like is to try them yourself, but as for customizable, i would say Launcher Pro as you don't have to jump through hoops to change the dock background.
5. Don't try to flash a theme that was designed for a different phone. When you theme a ROM, you theme the framework, which is tightly bound to the rest of the software. Changing the Captivates framework to the Evo framework for example would cause problems, as the Evo frameworks calls for different values in different places. The code isn't necessarily different, but the layout and string values will be different too.
All in all, this phone is pretty unbrickable. Get used to making backups and flashing back from a bad flash, and before you apply a theme, make sure you back up whatever files this theme calls for you to replace! Most of the time, even with a theme that doesn't work(assuming it's for the captivate), you'll still retain basic functions. Backup is key!
Enjoy the new toy!
geokhentix said:
1. Yes; the boot animation resides in /system/media/bootanimation.zip. To replace it, put the new bootanimation.zip on your SD card and move it over with root explorer. Should you not have root explorer, run the commands below via AndroidSDK/tools (put the bootanimation.zip in the /tools folder too)...
Code:
adb push bootanimation.zip /sdcard/
adb shell
su [i](should change from a $ to a #, dont forget to accept superuser on the phone too)[/i]
cp /sdcard/bootanimation.zip /system/media/
exit
exit
adb reboot
2. As this seems to be designed for a different device, it would require decompiling the frameworks and such and porting them over to captivate-esque code; that would work with the captivates framework.
3. This thread should teach you how to MetaMorph.
4. It's a matter of opinion. The two big ones are Launcher Pro and ADW.Launcher, both come with their own advantages and disadvantages. Want a transparent app drawer background? ADW. Want to hide apps in the app drawer? LauncherPro. Best way to find which one you like is to try them yourself, but as for customizable, i would say Launcher Pro as you don't have to jump through hoops to change the dock background.
5. Don't try to flash a theme that was designed for a different phone. When you theme a ROM, you theme the framework, which is tightly bound to the rest of the software. Changing the Captivates framework to the Evo framework for example would cause problems, as the Evo frameworks calls for different values in different places. The code isn't necessarily different, but the layout and string values will be different too.
All in all, this phone is pretty unbrickable. Get used to making backups and flashing back from a bad flash, and before you apply a theme, make sure you back up whatever files this theme calls for you to replace! Most of the time, even with a theme that doesn't work(assuming it's for the captivate), you'll still retain basic functions. Backup is key!
Enjoy the new toy!
Click to expand...
Click to collapse
Thanks so much for answering :]
2. Where can I find Captivate frameworks? I always see different amazing looking themes, but no frameworks specifically for Captivate.
4. Learned that the hard way. Scared myself two days after getting it by trying to flash a theme for the G1 and had to wait half an hour to flash back to stock ROM, so I've started to backup more now.
bugmenever said:
Thanks so much for answering :]
2. Where can I find Captivate frameworks? I always see different amazing looking themes, but no frameworks specifically for Captivate.
4. Learned that the hard way. Scared myself two days after getting it by trying to flash a theme for the G1 and had to wait half an hour to flash back to stock ROM, so I've started to backup more now.
Click to expand...
Click to collapse
You can find them on this board. A theme almost always changes the framework, which can point to a couple files. These aren't all of the files in theming, but generally, these 2 are almost always changed.
/system/framework/framework-res.apk
/system/framework/twframework-res.apk
Themes usually come as a .zip file, which is intended for you to flash with CWM(ClockworkMod Recovery). Cognition comes with ROM Manager I believe, if it doesn't, DL it off the market. Open it, click Flash ClockworkMod, select Captivate, then you can reboot into recovery and flash themed updates.
Put the themed .zip on your SD card
1. Open ROM Manager, and Flash it, selecting Captivate.
2. Select Reboot into Recovery. (On the first attempt, you might have to click "Reinstall Packages" when it boots into recovery, to get you into CWM for the first time.)
3. Once inside CWM, Install ROM from SD Card > Choose ROM from SD card > theme.zip
It's pretty hard to brick this phone, so don't be afraid to experiment a bit. Generally, most captivate themes are available here in teh Apps & Themes board, but make sure you read the thread to see if there's any information about it being compatible with your current ROM or not.
That's awesome!
Is there anything I would really need to get started up with this phone? I used to have an iPhone and I'm used to their framework, so... :]
Hoping to become a master at this.
I would say ROM Manager, Root Explorer, Titanium Backup, and NinjaMorph are all musts. I would say update to one of the newer roms too; like Perception. The newer kernels are much faster. If you're into customizations, it's worth modifying the rom before you install it (please note however, to always keep a stock unmodified copy of the rom you're modifying, incase it doesn't work).
It's pretty easy. Open the Rom's .zip(like perception, etc etc) in 7z or WinRAR
Apps go in /system/app if you want them to be system-installed (can't remove them, samsung/atnt bloatware is installed in the /system/app for example..well was)
OR the /data/app , which is pre-installed but on a user level, uninstallable like any app downloaded from the market.
Anything theme related goes in /system/framework
Kernels/Modems/etc go in the /updates folder
drag, drop, replace. No need to uncompress and recompress. Whatever you download, assuming it's not an odin flashable, will generally be in the same file system as the rom you're modifying, so it's easy to swap them out. This way themes install with the rom, please note however that if you do install a theme in such a way, features like the all-boot menu (Reboot/recovery/download on power menu), or any extra animations or unlock screens may not work; unless the theme you're building in has them too!
Woops. Accidently double posted.
requires Root (Superuser/Busybox), and a kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/).
The script also has a partner called V6 supercharger they go pretty well together heres a link to the V6 supercharger by zeppelinrox
this script is so easy to use but users might have problems using it so here is a easy install for you all to use i have converted it to run on non samsung phones by renaming the file and removing processes connected to the stock samsung apps
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Now for the really easy part
Using Root Explorer navigate to ect/init.d and select mount RW now scroll down to the "97loopy_smoothness_tweak" file and open it in the text editor within root explorer and you will see the 3 main sections to the script they are called
At the start of the script you will see this
Code:
USER_LAUNCHER=""
you need to add the launcher you currently use so that it gets locked in
Resident system apps
Other system apps
Other apps
in the 3 sections you will see lines one code that look the same which are
Code:
if [ $PROCESS_1 -eq "0" ]; then PNAME="com.android.phone"; NICELEVEL=-20; if [ `pidof $PNAME` ]; then renice $NICELEVEL `pidof $PNAME`; PROCESS_1=1; P_CHECK=`expr $P_CHECK + 1`; fi; fi;
All you do to add a app you want to keep in memory for as long as possible is to edit the script and change these values for e.g the stock dialer to go contacts
Code:
PNAME="com.android.phone";
to
Code:
PNAME="com.japps.contactpro";
that will keep Go Contacts EX locked in the background so everytime you wish to use the GC EX dialer you wont have to wait for it redrawing before using it.
To find the process names goto the data/data folder and all the folders you see in there are the process names used by the apps e.g. the com.android.vending folder is the process name for the vending.apk aka market app.
Just to let users no this script will not auto start the apps on reboot and once you first select the app you have added to the script after reboot you will have to wait for the app to redraw the app again into the memory slot once it has done that the app will remain in a cache type(hidden) form until you run the app again then it will return to ram in the foreground.
lpy of XDA said:
What this script hopes to achieve:
- Entering your PIN with minimal/no delay/lag
- Minimising delay with lock screen pattern/unlock (not the time it takes to wakeup, but the touchscreen response lag)
- Having smoother notifications on the status bar, and smoother pulldown menu response
- Minimising Launcher lag while Media Scanner is running (can scroll through screens without heavy pauses)
- Minimising lag when scrolling through the market while icons are still loading
- Installing/Uninstalling apps while continuing other tasks
- Minimising/eliminating intermittent lag spikes in gaming
- No delay in being able to answer phone calls
... you get the idea
Click to expand...
Click to collapse
Thanks goes to the creator lpy @XDA
tweak source:
http://forum.xda-developers.com/showthread.php?t=1137554
Download:
http://www.mediafire.com/?g4fte3m87t3ukui
Install via CWM as update.zip ???
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
nutterbg said:
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
Click to expand...
Click to collapse
yes i have tested it and it works i will be uploading a modded one for the update.zip but if you install it just rename it to 97smoothnees, it asks for the launcher you currently are using e.g. adw launcher but if you have any worries wait until tomorrow for the tut
I think this is helping with battery management because my battery seems to be going down slower
Sent from my GT540 using XDA Premium App
Let's hope I'm wrong. Looking forward to that tutorial.
Downloaded it, and flash'd it in cwm on my girlfriends gt540. In her opinion, it makes a noticeable difference.
Sent from my Nexus S using XDA Premium App
Oki, so I install this script and I must say that it's working. ;-)
Tut added hopefully you can all understand it
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
pRo_lama said:
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
Click to expand...
Click to collapse
let me have a quick check to see whats going on
eoghan2t7 said:
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Click to expand...
Click to collapse
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
pRo_lama said:
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
Click to expand...
Click to collapse
i just tried the update.zip again there and it installed fine for me what clockwork version are you using?
but you can extract the zip file and manually add the file to the init.d folder and give it these perrmissions
xxx
xxx
xxx
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
pRo_lama said:
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
Click to expand...
Click to collapse
try adding it manually to see what happens.
So I must manualy add the file into system and then continue with tutorial ???
yes you coy the script to the ect/init.d folder then continue with the tut
ok, i'm going to try it ;-)
Can't download please mirror on another hoster.
Sent from my GT540 using XDA Premium App
Should this method not eat battery rather than conserving it? As apps run in background correct me if m wrong....
Sent from my GT540 using XDA App
So the Nexus 7 does not have a primary camera, so a ton of apps in the market that use a camera show up as Not Compatible. You can sideload them and they may or may not work. However, there's a fix.
I'm on rooted stock, but if your custom ROM is also having this issue in the market you can tell your ROM Chef what file to add.
Caveat: This IS working for me as of right now, but it did not immediately, so there might be some delay or something else needed to do to make it work immediately. I'll update this post based on feedback if it's working immediately for folks or there's some other way to speed things up.
Caveat: Just because you can install an app won't make it work. If an app crashes, you've been warned. All apps might not work, but at least some apps that can use camera and don't need the camera function can be installed (Grocery King works fine, barcode scanning crashes), some will work fine (Camera Zoom FX).
And just to be clear, you are modifying /system. If you do this wrong, you could cause yourself problems. You have been warned.
Pre-reqs
Rooted
Root file explorer app to copy a file into /system (I use Ghost Commander, use your favorite app)
--OR THE FOLLOWING--
ADB working
Busybox (does not need to be installed, but needs to be available for cp, or you can use cat if you know how to do that method instead)
Busybox might be needed to remount /system as read-write, or you can use some other method to do this
Pick the method you want to use, adb, or a file explorer that can mount /system and write files there. Pick one method or the other, I've hidden the content on both by default so fewer people think you need to do everything..
android.hardware.camera.autofocus.xml is a file inside of the zip attached to this post, all references to copying that file imply you open the zip file and extract or copy it directly over. NOT the zip file itself. And no, this is not "cwm flashable". If this is working for folks and someone wants to make a CWM Flashable ZIP file to use, I'll be happy to add it to the post and update instructions.
Instructions for using your favorite root explorer kind of app
Download the file attached to this post to your device
Launch your favorite root explorer type app and remount /system as read/write
Copy android.hardware.camera.autofocus.xml to /system/etc/permissions/
Remount /system as read-only
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Instructions for using ADB/Manually copying it
Download the file attached to this post
Connect to your device over adb (I use wifi adb personally)
Do the following commands to launch adb and inside of adb respectively
adb push android.hardware.camera.autofocus.xml /sdcard
adb shell
su
mount -o rw,remount /system
cp android.hardware.camera.autofocus.xml /system/etc/permissions/
mount -o ro,remount /system
Click to expand...
Click to collapse
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Thanks to bonks in #nexus7 for confirming for me that he cannot access a few Camera apps and validating some permissions files for me to verify my changes had worked on my end.
Works for 4.3 as well, but the same caveat... It took three days to show apps as compatible, so not sure what needs to "clear" for the permissions to be updated, but give it a few days and it'll be fine.
Reserving for any followup info, particularly around if the market permission doesn't clear "immediately".
A partial list of apps that work/don't work, but all will install now and previously would not. If anyone tries another app or has more input I'll update this post.
I've also started a list of apps I know of that have altered their permissions in the market so that they should show up natively on the N7 without the fix.
Work Perfectly (maybe mirrored)
Paper Camera - Mirrored
Google Translate - Mirrored, maybe upside down.. Wonky, but does work.
Work With Caveats
Grocery King - Barcode scanning crashes, otherwise completely usable
Don't Work at All
Google Goggles - Blank image, although you can load images you took with other cameras
Retro Camera - Can't find camera
Fixed market permissions
Camera FX Zoom - Use landscape, or things are mirrored and flippped
This worked great for me...thanks a bunch!
Sent from my Nexus 7 using xda premium
Ima give this a go when I get home, thanks
Nexus 7 camera permissions
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David
DavidTheBourne said:
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David
Click to expand...
Click to collapse
http://stackoverflow.com/questions/...ort-for-android-application-manifest-assembly
Just wanted to bump this thread and let everyone know this still works for 4.3. However, I'm not sure what one would need to do to make it work faster.
I installed the XML file on my N7 about three days ago, cleared Market data, rebooted etc, specific apps still showed as not compatible.
Finally today I look, and compatible! Perhaps it's on Google's side, it only updates every so often.. I dunno.
Anyway, so it works, but it might take a few days for it to propagate
** Designed for stock Moto 98.72.22 and 98.72.22-based ROMs **
** FOR OTHER ROMS and updated stock, see post #7 **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default = same end result as SQL hack.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
0. Backup just in case!!
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!
tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.
Ismokel said:
tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.
Click to expand...
Click to collapse
JB 246 98.72.22? I'm assuming you used a root explorer due to the FC. I recommend using Safestrap's built-in file manager (see the updated instructions).
I could also make a flashable ZIP to mitigate user-error if there is demand for it.
The last issues you mentioned are unrelated to this. The modified APK is exactly the same as the original, except for a single byte (1 -> 0) and deodexed. Oh, and a "false" to "true" in the manifest so we could manually clear data, but that didn't work out. You can decompile and compare yourself
Same issue here as Ismokel. It might be a signing issue, as I saw the same thing occur when I tried doing the mod myself and was experimenting with the different options for signing. It worked for me when I left the existing signature.
I would post my modded version, but I need to make one with only that mod first, as mine has mods to change other defaults as well.
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
You mentioned that yours worked for you without wiping data. Did you change default_entitlement_check in the xml resources or did you change something else? I was only interested in this mod to change the default and not the existing setting, but I'm still somewhat curious.
progrockguy said:
** Designed for stock Moto 246 (JB 4.1.2) and 246-stock-based ROMs **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!
Click to expand...
Click to collapse
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.
ShadyDreamer said:
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
Click to expand...
Click to collapse
Whoops!! 98.72.22 is the base I used. If you took OTA updates, that could explain the boot loops. See below on how to DIY
dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
Brolzy said:
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.
Click to expand...
Click to collapse
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
My safestrap instructions will work on your newly modified APK. (If you're going to try replacing via root file explorers, I suggest an overwriting Paste. That way you'll keep permissions in case android crashes and hot reboots. Do not delete, *then* paste. It'll likely crash before you can set the permissions.)
Good luck!
progrockguy said:
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
Click to expand...
Click to collapse
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
If you are using adb from a computer connected by USB to copy and install the apk, after using su you can use the stop command to close all apps, then you can safely move, rename, replace, or delete system apps without it crashing and rebooting. Just make sure you have it in the proper state before you reboot. If a prompt to allow su from adb comes up on the phone, be sure to allow it with no time limit in case you need to use su again before you use adb reboot to restart the phone.
ShadyDreamer said:
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
Click to expand...
Click to collapse
Curious, where did you get your APK from? Because stock is odexed.
My file also had a manifest edit (which didn't work out), but I doubt that's the issue since it works on two of my Bionics.
When I quoted the part I was replying to, I included your "All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM." line in the quote for a reason. I did that part.