How to get rid of the annoying "System Update"

How to get rid of the annoying "System Update" - HTC Desire 510

Hello!
I'm on a rooted Cricket Android 4.4.2 device.
ROM Version: 1.11.506.1
Software Number: 1.11.506.1
HTC Sense 6
Baseband: 1.101.1372.19
Can somebody please tell me how to get rid of the annoying software update that has been coming the last week?
Is there way to somehow either change my software number to trick the phone into thinking I'm updated or perhaps I should update? If so, how?
I appreciate the help.

Using a root file explorer and freezing the updater app manually would probably be the safest (personally I like Root Browser by JRummy hasn't been updated in awhile but if ain't broke it don't need to be, and it is a tool I know will always perform these critical tasks correctly)
By freezing the the system updater app in the following way, you will be able to easily reverse the process using the same process. While there are some mods that can hide the notification itself (eg.: Xposed FW), this method completely disables the update check process, thus freeing up system resources. Twofold if you look at it this way imo, rather than adding potentially harmful additional resources.
# Open your root fs explorer
# navigate to fs root:
/
# then to:
/system/priv-app
# locate the file:
Updater.apk
# append ".bak" to the file name. In other words rename it to:
Updater.apk.bak
# note: no need to mess with it's .odex file, it never hurt no one. Also depending on your fs explorer and personal settings, the app's icon thumbnail has likely changed to a blank white square/unkown/generic file icon and is totally normal.
# profit and celebrate the newly liberated space in your notifications and don't forget to miss that pesky "remind me later" pop up.
#should there be an update that your are feeling compelled to (try) and install simply remove ".bak" from the files name and proceed as usual. Note that the only thing you should be changing in all this is +/- ".bak" from the file name. Don't go trying to change this or other apps file name. It don't work like that. Speaking of other apps, I urge great caution against going ape$#¡+ and doing this carelessly, especially for apps anywhere under "/system".
# The Disable button on the App Info pages should be the primary resource for disabling apps for most users. Know what the app does and is used for on your system BEFORE making changes or worse yet, deleting it.
~/#: print <INSERT STANDARD DISCLAIMER, AKA CYA STATEMENT HERE>
Don't just say it, hit that thanks button if I helped you in any way!!!
Sent from my HTC Desire 510 using Tapatalk

wow thank you so much :laugh:

jackunoff said:
Using a root file explorer and freezing the updater app manually would probably be the safest (personally I like Root Browser by JRummy hasn't been updated in awhile but if ain't broke it don't need to be, and it is a tool I know will always perform these critical tasks correctly)
By freezing the the system updater app in the following way, you will be able to easily reverse the process using the same process. While there are some mods that can hide the notification itself (eg.: Xposed FW), this method completely disables the update check process, thus freeing up system resources. Twofold if you look at it this way imo, rather than adding potentially harmful additional resources.
# Open your root fs explorer
# navigate to fs root:
/
# then to:
/system/priv-app
# locate the file:
Updater.apk
# append ".bak" to the file name. In other words rename it to:
Updater.apk.bak
# note: no need to mess with it's .odex file, it never hurt no one. Also depending on your fs explorer and personal settings, the app's icon thumbnail has likely changed to a blank white square/unkown/generic file icon and is totally normal.
# profit and celebrate the newly liberated space in your notifications and don't forget to miss that pesky "remind me later" pop up.
#should there be an update that your are feeling compelled to (try) and install simply remove ".bak" from the files name and proceed as usual. Note that the only thing you should be changing in all this is +/- ".bak" from the file name. Don't go trying to change this or other apps file name. It don't work like that. Speaking of other apps, I urge great caution against going ape$#¡+ and doing this carelessly, especially for apps anywhere under "/system".
# The Disable button on the App Info pages should be the primary resource for disabling apps for most users. Know what the app does and is used for on your system BEFORE making changes or worse yet, deleting it.
~/#: print <INSERT STANDARD DISCLAIMER, AKA CYA STATEMENT HERE>
Don't just say it, hit that thanks button if I helped you in any way!!!
Sent from my HTC Desire 510 using Tapatalk
Click to expand...
Click to collapse
I'm gonna chime in here and I know you're trying to help but this really isn't helping because you didn't actually freeze the app like you said. All you did was change the apps name so now when the system actually calls upon that app it's simply going to error out and actually cause it to use more resources and not less as you said albeit it will not show up anymore but that's not the way to stop it! If I go into /system/priv-app and change Phonesky.apk to Phonesky.apk.bak the play store is going to break and then send me the error to my screen every second until I fix it and that uses more resources and the only reason you're not seeing the error on the screen for the Updater is because it's doing it behind the scene in a log. Now the real way to stop this app is to actually really freeze it or uninstall it so the system actually knows the app is no longer there and there are plenty of apps in the play store that can do that.
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
Khiddfrost said:
wow thank you so much :laugh:
Click to expand...
Click to collapse
You should read my post above.

Related

Root access with Astro?

Is there anyway to start Astro as root so you can use it to edit system directories?

I had wished for the same thing.. but i didnt tell nobody.. soo maybe this will be more effective. prevents having to type in the terminal all the time.. not that its bad.. ive learned so much allready since ive had this phone...

I totally agree! That would be perfect! Maybe there a way of editing the code or smth...

If you can't work *MORE EFFICIENTLY* directly from the terminal, then you definitely should NOT have root access via GUI.

lbcoder said:
If you can't work *MORE EFFICIENTLY* directly from the terminal, then you definitely should NOT have root access via GUI.
Click to expand...
Click to collapse
Pretty much this. It seems like most of the people having problems on this website just want root because it's "kewl" but really have no idea what it is or even have a clue on how Linux works.

I actually Emailed the Dev of Astro about this same question and here was his reply.
Here is the email copied and pasted from gmail.
My question
Are you able to make a version that requests root access to delete chmod rename move etc for the 100,000+ users from xda and other boards with root access?
His Reply
On Jan 21, 2009 10:57 AM, "Kevin Payne" <metago.inc[at]gmail> wrote:
This is a bit outside ASTRO's scope at the moment. Technically, ASTRO should work fine on files owned by root if it were run as a root process, but running applications as root is not advised in general. Someone really needs to create a sudo type command to let an individual application run as root.

lbcoder said:
If you can't work *MORE EFFICIENTLY* directly from the terminal, then you definitely should NOT have root access via GUI.
Click to expand...
Click to collapse
d00m said:
Pretty much this. It seems like most of the people having problems on this website just want root because it's "kewl" but really have no idea what it is or even have a clue on how Linux works.
Click to expand...
Click to collapse
Considering the fact that I'm a Systems Administrator as my profession and work with hundreds of Linux/Unix/Windows servers a day, the whole reason why I bought the G1 was for development and tinkering, the fact that my home PC is running Vista x64 (i haven't gotten around to creating a VM or messing with the drivers), and that I do wipes frequently to test different configurations, I'm pretty sure I'll be ok with root access. I'm just tired of manually doing something on that tiny keyboard that can easily be done with a nice pretty GUI. I stare at consoles all day and thousands of lines of black and white text, when I come home I don't exactly want to be anywhere near a terminal.
Also, why bother doing anything on a phone, other than using it as a phone (or for email, texting, etc.), if you don't do it because it's "kewl". I mess with my phone because it's cool to have a mini-*nix based computer with several fun radios on it. If I do something stupid like type "rm -Rf /*" after logging in as root (never going to happen) then that's my own fault.
I don't care if you're a Unix purist and you write up your office reports, spreadsheets, and diagrams in vi. Good for you, you're wasting time that can be better spent on other things because of your stubborn prejudice against GUI's. I asked a question, because I have a reason for that question. If you don't have any answers to that question, then please don't bother replying.
diabolical28 said:
I actually Emailed the Dev of Astro about this same question and here was his reply.
Here is the email copied and pasted from gmail.
My question
Are you able to make a version that requests root access to delete chmod rename move etc for the 100,000+ users from xda and other boards with root access?
His Reply
On Jan 21, 2009 10:57 AM, "Kevin Payne" <metago.inc[at]gmail> wrote:
This is a bit outside ASTRO's scope at the moment. Technically, ASTRO should work fine on files owned by root if it were run as a root process, but running applications as root is not advised in general. Someone really needs to create a sudo type command to let an individual application run as root.
Click to expand...
Click to collapse
I looked into the commands to launch an application from the CLI and found that Astro can be started using the following command:
am start -n com.metago.astro/.FileManagerActivity
However, this doesn't do us any good, since the dalvik VM will take that command and create a process as a sandbox user regardless of what user executes that command. There looks like there's a way to tell the VM to fork the process as a specific uid and gid, but that requires editing the AndroidManifest.xml.
I'm not too good with Java, and I don't know how strict Android's API is, so I don't know if running an apk application as root is even possible.
However, I do know that running commands from inside an application, like su, is possible.
~TM
"Wise men speak because they have something to say; Fools because they have to say something." ~Plato

Solved--Astro with root...(workaround)
kinda late, but in case anyone wants to know this is what I did.
This way technically doesnt allow astro to run with root, but its just as good.
I originally did this a few months back for my G1, and just mod it a little to work on my nexus
- created a script to mount system as rw
- created a script that gives r/w permission to all app directories (/data, /data/app, /data/app-private, /system, /system/app, /system/sd, ...) and all apps inside those directories
-then merged the 2 scripts and named it astro_root_perm
-installed GScript from the market
-created another script that
-first changes all permissions on apps back to what they started as(644, 640...)-then changes permissions of directories back to what they were-and finally remounts system back to ro, and named this script to astro_basic_perm
-used Gscript to create shortcuts of the 2 scripts to my home screen.
-then with bettercut, I changed the scripts' icons to the astro icon. I just colored the astro stock icons "A" green for one script and red for the other
So anytime I want to use astro as root, I just click the shortcut I made with gscript off my home screen, open astro,
Then when Im done with astro, I just run the other script
I know its not the same as running astro AS root, but it works for me.
Im not really a linux guy......I'd really appreciate if someone could help me with this next step
++++++++++++++++++++++++++++++++++++
Does anyone know what I need to include in a script to have it call/open a program automatic?
My ultimate goal is to create one script that will
Mount system rw
Change needed permissions to rw
Automatically open up Astro
Then change all permissions back when astro is terminated
Possibly create a keyboard shortcut for the G1
What do ya think?? is it possible??

Estrongs has limited root file browsing on some ROMs and SU File Manager or Root File Manager will let you browse as root for a small price.

+1 recommendation on Estrongs File Explorer's root option if you want it for free, includes Windows shares browsing over lan.
Otherwise try SUFBS, also has built-in terminal.
Sent from my HTC Hero using Tapatalk

louieG1 said:
My ultimate goal is to create one script that will
Mount system rw
Change needed permissions to rw
Automatically open up Astro
Then change all permissions back when astro is terminated
Possibly create a keyboard shortcut for the G1
What do ya think?? is it possible??
Click to expand...
Click to collapse
I'm not sure exactly how gscript handles things, but with a normal bash (shell) script, the lines are run sequentially. That is, the next line isn't run until the previous line is done. It would seem that you could put all that in one script, and the still-running script wouldn't change the permissions back until astro has ended. But then again, java adds complexity to it and I'm not sure if it works the same.

louieG1 said:
kinda late, but in case anyone wants to know this is what I did.
++++++++++++++++++++++++++++++++++++
Does anyone know what I need to include in a script to have it call/open a program automatic?
My ultimate goal is to create one script that will
Mount system rw
Change needed permissions to rw
Automatically open up Astro
Then change all permissions back when astro is terminated
Possibly create a keyboard shortcut for the G1
What do ya think?? is it possible??
Click to expand...
Click to collapse
Love this idea! Unfortunatly I'm no coder but would love to see something like this created.

I created a "GodMode" script that does exactly this, email me if you want it, I can edit it to work for the G1.

Totally forgot I started this thread, then happened to find it on Google when looking for the same thing, again.
Went back to Windows Mobile for a little bit, missed Android, and now have a Samsung Vibrant.
Still want a way to use ASTRO with root priviledges, especially since I don't have a tactile keyboard anymore.

phaelox said:
+1 recommendation on Estrongs File Explorer's root option if you want it for free, includes Windows shares browsing over lan.
Otherwise try SUFBS, also has built-in terminal.
Sent from my HTC Hero using Tapatalk
Click to expand...
Click to collapse
Thank you.
Estrongs File Explorer enabled me to flash Tamil font in my Rooted T-Mobile G2X mobile phone.

I know i am not answering the question directly. But, i use Linda Manager it gets the job done.
---------- Post added at 08:17 PM ---------- Previous post was at 08:14 PM ----------
raddy said:
Thank you.
Estrongs File Explorer enabled me to flash Tamil font in my Rooted T-Mobile G2X mobile phone.
Click to expand...
Click to collapse
Hi raddy,
I'm also from TN as well, i would love to get the Tamil fonts. Can you please guide me?
Not having tamil fonts on the browser is simply annoying

Hi
If your mobile is rooted, then follow this link.
http://forum.xda-developers.com/showthread.php?t=798380
Sent from my LG-P999 using XDA App

raddy said:
Hi
If your mobile is rooted, then follow this link.
http://forum.xda-developers.com/showthread.php?t=798380
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Cool, i got the tamil fonts on my G1, thanks for the help.

[Script] Safe bloat removal script (50+ apps) [UPDATED 9/1/2011]

There's been a lot of speculation on what can and can't be removed as well as how to remove them without causing force-closes, boot loops, and other headaches. So I wrote this script that will let you disable all of the bloat with none of the hassle.
After a few prompts to find out if there's anything you want to keep that can't be replaced in the market, it will do its magic -- renaming files to a .bak extension so they are no longer recognized by Android. This will cause some system services to fail and force-close loop until you reboot (and the script reboots for you). Also included is a script that will undo all of this.
If you select every option, including the default launcher and text messaging apps (which are confirmed safe to remove without losing SMS or MMS ability or push notifications), then here's the list of apps removed:
AdService.apk, android-syncservice-app.apk, ArcVideoEditorLite.apk, BackupAssistanceClient.apk, Blockbuster.apk, BlurHome2.apk, BlurSNMessagingEngine.apk, BlurTasks.apk, BlurUpdater_VZW.apk, BooksPhone.apk, CitrixReceiver.apk, CityID.apk, Conversations.apk, DLNA.apk, DlnaSystemService.apk, FriendFeed.apk, gotomeeting-stub-1.0.74.apk, GuidedTours.apk, HelpCenter.apk, IMPresence.apk, IndexingService.apk, Kindle.apk, MessagesWidget.apk, Messaging.apk, MOTOPRINT.apk, MSExchangeService.apk, MyVerizon.apk, NewBayVault_4.2.99.36.Market.apk, NFLMobile.apk, OnlineAlbum.apk, PhotoEditor.apk, PortalStandAlone.apk, Preloaded.apk, RichLocationVzW.apk, SkypeBourbon.apk, Slackerradio.apk, SocialMessaging.apk, SocialShare.apk, StatusWidget.apk, SuggestionsProvider.apk, SuggestionsRuleCheckerCore.apk, SuggestionsServiceScheduler.apk, Swype.apk, ToggleWidgets.apk, UniversalInbox.apk, Upgrader.apk, VCAST_TONES_4_5_7.apk, VCASTMusic.apk, VCASTVideo.apk, VSuiteApp.apk, vzw_vnav_DROID3_rel_PROD_signed.apk, VZWIM.apk, VZWInstaller.apk, WeatherWidget.apk, ZumoCast_1.0.17.apk
Make sure you run these scripts using Script Manager or a comparable app and be sure to enable it to run as root or it won't have permission to make changes to /system/app.
This is version 1 of the scripts -- if any of the apps removed wind up causing problems or more are found, I'll add it to the list. I've tested the scripts back and forth myself and have tested it as much as I can without finding any issues. Also, some apps are removed without asking, such as ZumoCast or VCAST or NFL Mobile. You can find these apps in the market, so there's no point keeping them locked down in system.
Enjoy! Comments are welcome.
UPDATE 9/1/2011: fixed a typo in one of the variables (thanks everyone who reported this), added more options to keep (Swype and Car Dock Voice Commands), split into two versions -- one for the stock 5.5.959 build and 5.6.890 update (late August OTA), added a warning about removing the home screen without a launcher and that it removes the Calendar widget.

Great, but maybe it would be nice to make a y/n option for each .apk where it asks you if you want to delete that apk

script
instructions for use?
thanks

DoubleYouPee said:
Great, but maybe it would be nice to make a y/n option for each .apk where it asks you if you want to delete that apk
Click to expand...
Click to collapse
You shouldn't delete them -- we don't have an SPF yet. Someone posted the complete /system/app contents and you could restore, technically, manually, but it's a bad idea. Renaming to a .bak is completely effective.
lodisax said:
instructions for use?
Click to expand...
Click to collapse
Read the post.
You'll want to use Script Manager -- unzip the two scripts to your SD card (internal or external), launch Script Manager (free version is fine), find the script and click it, then tick on 'root' and then run the script. Follow the prompts from there.

script
thanks for the answer

psouza4 said:
You shouldn't delete them -- we don't have an SPF yet. Someone posted the complete /system/app contents and you could restore, technically, manually, but it's a bad idea. Renaming to a .bak is completely effective.
Click to expand...
Click to collapse
Yeh sorry that's what I meant.. Option to y/n rename the apk.
I'd like to use the script once I get my droid 3 but would like to 'keep' some of the apks.

DoubleYouPee said:
Yeh sorry that's what I meant.. Option to y/n rename the apk.
I'd like to use the script once I get my droid 3 but would like to 'keep' some of the apks.
Click to expand...
Click to collapse
There's Y/N for anything you'd want to keep. About 6-7 questions in total. Anything that you can't find in the market that isn't definitely bloat has a prompt.

script
script manager that you use?
I use script manager and asked me if I want to remove each apk or not.
There is a script manager that does everything automatically?
thanks for the answer

lodisax said:
script manager that you use?
I use script manager and asked me if I want to remove each apk or not.
There is a script manager that does everything automatically?
thanks for the answer
Click to expand...
Click to collapse
Please read the thread thoroughly -- I'm going to ignore obvious questions like these.

psouza4 said:
There's Y/N for anything you'd want to keep. About 6-7 questions in total. Anything that you can't find in the market that isn't definitely bloat has a prompt.
Click to expand...
Click to collapse
So what if I wanna keep DLNA, photoeditor and socialmessaging?

DoubleYouPee said:
So what if I wanna keep DLNA, photoeditor and socialmessaging?
Click to expand...
Click to collapse
Then answer 'Y' to the prompts asking if you want to keep 'DLNA' or 'social messaging'. There are plenty of photo editors in the market, so there's no prompt on that (although if you were so inclined, you could just rename the .BAK's back to their original files). I feel you haven't actually looked at the script or read my post.

psouza4 said:
I've tested the scripts back and forth myself and have tested it as much as I can without finding any issues. Also, some apps are removed without asking, such as ZumoCast or VCAST or NFL Mobile.
Click to expand...
Click to collapse
I think the ultimate test is to do factory reset and see how device will go through initialization stage. It can be surprises which are not noticeable during normal use. Without this it is kind of premature to say what is safe to delete and what is not.

serg675 said:
I think the ultimate test is to do factory reset and see how device will go through initialization stage. It can be surprises which are not noticeable during normal use. Without this it is kind of premature to say what is safe to delete and what is not.
Click to expand...
Click to collapse
Ehh I agree with you to a point, because i made the very noobish mistake of uninstalling bloat that i knew would not effect daily use; however, I did a factory reset to test a theory for krazy and learned that something I uninstalled makes the setup process FC and wont let you get to the blur launcher, luckily other launchers work and I was able to batch install via adb.
Thing is though is if the phone reboots when this stuff is renamed then it will survive a factory reset, though it may do the same thing mine has done. If it does its no big deal to load up adb and rename the files back so that you can complete the setup.

You forgot the World Clock widget in your removal script; the only clock that thinks it needs a permanently-resident service, regardless of whether it's running or not.

Xenoproctologist said:
You forgot the World Clock widget in your removal script; the only clock that thinks it needs a permanently-resident service, regardless of whether it's running or not.
Click to expand...
Click to collapse
That messes with the dock though, so I don't consider it bloat.

I know its a lot to ask... but can someone either create a comprehensive list of what each one actually does... or point us in a direction to where there already is one?
Sent from my DROID3 using Tapatalk

Seirÿu said:
I know its a lot to ask... but can someone either create a comprehensive list of what each one actually does... or point us in a direction to where there already is one?
Click to expand...
Click to collapse
Open the script in a text editor and read my comments -- it gives each one a title.

@psouza4 - nice work, it's about time someone took a more organised approach to figuring out what apks are safe to remove.
I tried to get a similar effort going here :-
http://forum.xda-developers.com/showpost.php?p=17004394&postcount=11
but the way people behave on this forum, it's like trying to herd cats.

thingonaspring said:
@psouza4 - nice work, it's about time someone took a more organised approach to figuring out what apks are safe to remove.
I tried to get a similar effort going here :-
http://forum.xda-developers.com/showpost.php?p=17004394&postcount=11
but the way people behave on this forum, it's like trying to herd cats.
Click to expand...
Click to collapse
Thanks!
Couple of notes, too:
It was asked in IRC why I'm removing 'android-syncservice-app.apk'. This service is the extra backup stuff that Verizon added on (as evidenced inside the package in /assets/system.properties you'll find several references to verizon servers for sync, like sm_connection_url=http://syncba.myvzw.com/syncml). This service doesn't do anything beneficial for you unless you really have a hard-on for Verizon's sync stuff. I've had it disabled since we achieved root and it has no affect on account sync services (contacts, gmail, calendar, reader, etc.) nor SMS/MMS push notifications, etc.
Also, a fellow PM'd me saying he got errors that variable names were invalid -- turns out he had edited the script in Windows, saved it, and that broke the UNIX-style line endings. If you're going to modify the script, use Notepad++, UltraEdit, or something that will maintain the correct line endings. Or just use an editor on the phone, such as in Root Explorer.

Thanks a bunch man, works great. About to run a benchmark to see the results!

De-Bloat Script

I used psouza4's Bloatware Removal for Droid 3 script to remove the bloat from my Bionic: http://forum.xda-developers.com/showthread.php?t=1238472.
While it got most of it, it left behind a few apps due to name changes in apps between the 2 devices. After SSH-ing into my device I compared the names of the lingering apps with the ones in the script and made the proper changes.
I saw in his post that some people were looking for a more refined way of removing Motorola's widgets, so I added that to the bottow of the script for users to uncomment if they want to remove specific widgets instead of all or nothing.
Lastely, I tossed in a few other options that would have to be uncommented to run, such as removal of QuickOffice, File Browser, and Browser. The latter 2 will need replacements installed prior to removing them or problems will occur (or so I've read).
That being said, I will not post the script until I get the OK from psouza4 to repost his work with my changes. Also, if this has been done already (I couldn't find it...and yes, I looked) then please let me know and I won't bother. Stay tuned if you're interested in using it. Hopefully I can repost it for new Bionic owners like myself.

Diff Output
Attached is the diff output I ran against my edit and the original script. The first entry of each comparison is my edit to the original command in the script.

Scripts
Attached are the de-bloat and restore scripts based on psouza4's Droid 3 work.

n00b Question:
Does this just freeze all bloat or does it remove it completely?
Easy answer I'm sure... I just want to be sure I understand what this does.
-Thanks

Darca said:
n00b Question:
Does this just freeze all bloat or does it remove it completely?
Easy answer I'm sure... I just want to be sure I understand what this does.
-Thanks
Click to expand...
Click to collapse
it renames the files with a .bak extension so the OS can't see them, and therefore wont load them.
by not deleting them you can run the restore script to remove the. bak extension. i had to do this today to update my bionic (the update fails upon installation if it cant see the apps you renamed.
make sure to follow the instructions in psouzas post with regards to using a program such as script manager.

Thank you!

[Script] Removing stupid useless apps from stock

Hi,
When I got my Droid, I couldn't believe all the stuff that came preinstalled with the phone, so I started deleting everything that seemed unnecessary. Given the fact that I already reflashed the phone 20 times in the last week, I made a little script to help me out. I thought I would share it with you in case it comes handy to someone.
BIG NOTE 0: There's a system part that Motorola uses to get stuff from your phone. It's called Data Collector. Whenever any app crashes, it makes quite a big dump, with your network carrier, signal level, applications installed, applications running and a lot of stuff that isn't opt-in. In fact, one of the scripts (/system/bin/bugtogo.sh) can take screenshots of your phone. I don't like being spied, so I tried to remove it all. Cannot be certain though, but I would recommend you to remove, if you like your privacy, at least, the DataCollector apks, and to empty the bugtogo.sh script from /system/bin
BIG NOTE 1: I don't use this phone in the US, so I don't know if I'm breaking part of the CDMA support. It still shows up in every settings and I don't have any reason to think it won't work, but since I can't test it in anything except GSM/UMTS, I can't know it for sure.
BIG NOTE 2: The script will install Apollo (Music Player), Nova Launcher (homescreen replacement), and Cyanogenmod's Gallery app. If you don't want them and want to keep Blur and the default gallery (the script doesn't remove the music player just in case it's needed by some other app), then don't use this script, or modify it as you wish.
BIG NOTE 3: I am not responsible for anything if this causes a mess. Worst case scenario you'll need to flash back the system partition (fastboot flash system system.img), and then reroot your phone. You have been warned.
This is what it removes:
Code:
/system/app/DataCollection.apk
/system/app/DataCollection.odex
/system/app/DataCollectorProvider.apk
/system/app/DataCollectorProvider.odex
/system/app/DataCollectorService.apk
/system/app/DataCollectorService.odex
/system/app/blur-services.apk
/system/app/blur-services.odex
/system/app/blur_facebook.apk
/system/app/blur_facebook.odex
/system/app/blur_flickr.apk
/system/app/blur_flickr.odex
/system/app/blur_kaixin001.apk
/system/app/blur_kaixin001.odex
/system/app/blur_lastfm.apk
/system/app/blur_lastfm.odex
/system/app/blur_orkut.apk
/system/app/blur_orkut.odex
/system/app/blur_photobucket.apk
/system/app/blur_photobucket.odex
/system/app/blur_picasa.apk
/system/app/blur_picasa.odex
/system/app/blur_youtube.apk
/system/app/blur_youtube.odex
/system/app/vzw_vnav_DROID4.apk
/system/app/vzwapnpermission.apk
/system/app/MyVerizon.apk
/system/app/VerizonSSOEngine.apk
/system/app/MotoVzwAtCmdPlugin.apk
/system/app/MotoVzwAtCmdPlugin.odex
/system/app/VzwController.apk
/system/app/VzwController.odex
/system/app/VzwDeviceSetup.apk
/system/app/VzwDeviceSetup.odex
/system/app/VzwEntitlementService.apk
/system/app/VzwEntitlementService.odex
/system/app/VzwPhoneService.apk
/system/app/VzwPhoneService.odex
/system/app/VCast.apk
/system/app/VCastStub.apk
/system/app/VCastTones.apk
/system/app/VCASTVideo.apk
/system/app/VmmGallery.apk
/system/app/com.motorola.android.server.ims.apk
/system/app/com.motorola.android.server.ims.odex
/system/app/com.motorola.android.settings.aplogd.apk
/system/app/com.motorola.android.settings.aplogd.odex
/system/app/VmmBackupManager.apk
/system/app/VmmBackupManager.odex
/system/app/VmmGallery.odex
/system/app/SmartActionFW.apk
/system/app/SmartActionFW.odex
/system/app/SmartActions.apk
/system/app/SmartCarDock.apk
/system/app/SmartDock.apk
/system/app/ZumoService.odex
/system/app/ZumoService.apk
/system/app/WelcomeWebtop.odex
/system/app/WelcomeWebtop.apk
/system/app/WeatherWidget.apk
/system/app/VZWInstaller.apk
/system/app/Vvm.odex
/system/app/Vvm.apk
/system/app/VSuiteApp.apk
/system/app/VRDClient.apk
/system/app/VMMServiceInterface.odex
/system/app/VMMServiceInterface.apk
/system/app/VideoSurf.apk
/system/app/Videos.apk
/system/app/VideoCalling.apk
/system/app/Swype.apk
/system/app/SocialShare.odex
/system/app/SlingBox.apk
/system/app/SocialShare.apk
/system/app/SlackerRadio.apk
/system/app/RichLocationVzW.apk
/system/app/Protips.odex
/system/app/Protips.apk
/system/app/PlusOne.apk
/system/app/PhotoEditor.odex
/system/app/PhotoEditor.apk
/system/app/OnlineAlbum.odex
/system/app/OnlineAlbum.apk
/system/app/NflMobile.apk
/system/app/Netflix.apk
/system/app/MusicStore.apk
/system/app/MotorolaAccountSetup.apk
/system/app/MotorolaAccountSetup.odex
/system/app/MotoEmailConfig.apk
/system/app/MotoDockHelperService.odex
/system/app/MotoDockHelperService.apk
/system/app/MotoConnect.odex
/system/app/MotoConnect.apk
/system/app/MotoCastDashboard.odex
/system/app/MotoCastDashboard.apk
/system/app/motoactv.apk
/system/app/MotMusic.apk
/system/app/MotGallery.apk
/system/app/MCDownloadManager.odex
/system/app/MCDownloadManager.apk
/system/app/Kindle.apk
/system/app/JunosPulsePlaceholder.apk
/system/app/IlsVzW.apk
/system/app/HuxVmmSetting.odex
/system/app/HuxVmmSetting.apk
/system/app/HuxSnCClient.odex
/system/app/HuxSnCClient.apk
/system/app/GuidedTours.apk
/system/app/GuidedTours.odex
/system/app/HelpCenter.apk
/system/app/FileManager.apk
/system/app/FileManager.odex
/system/app/Facebook.apk
/system/app/DockService.odex
/system/app/DockService.apk
/system/app/DlnaSystemService.odex
/system/app/DlnaSystemService.apk
/system/app/DLNA.odex
/system/app/DLNA.apk
/system/app/DemoMode.odex
/system/app/DemoMode.apk
/system/app/ContactIce.odex
/system/app/ContactIce.apk
/system/app/Cmas.odex
/system/app/Cmas.apk
/system/app/BuaContactAdapter.odex
/system/app/BuaContactAdapter.apk
/system/app/BlurUpdater_VZW.odex
/system/app/BlurUpdater_VZW.apk
/system/app/BlurChooser.odex
/system/app/BlurChooser.apk
/system/app/BackupRestoreConfirmation.odex
/system/app/BackupRestoreConfirmation.apk
/system/app/BackupAssistanceClient.odex
/system/app/BackupAssistanceClient.apk
/system/app/ArcVideoEditorLite.apk
/system/app/android-syncservice-app.apk
/system/app/OutOfBox.odex
/system/app/OutOfBox.apk
/system/app/FriendFeed.apk
/system/app/FriendFeed.odex
/system/framework/com.motorola.MCDownloadLibrary.services_lib.jar
/system/framework/com.motorola.MCDownloadLibrary.services_lib.odex
/system/framework/com.motorola.motoconnect_lib.jar
/system/framework/com.motorola.motoconnect_lib.odex
/system/framework/com.motorola.vzw.vmm.helper.jar
/system/framework/com.motorola.vzw.vmm.helper.odex
/system/framework/com.motorola.vzw.vmm.util.jar
/system/framework/com.motorola.vzw.vmm.util.odex
/system/framework/com.scalado.android.photoeditor.jar
/system/framework/com.scalado.caps.jar
/system/framework/com.verizon.phone.jar
/system/framework/com.verizon.phone.odex
/system/framework/com.vzw.android.gex.jar
/system/framework/com.vzw.android.gex.odex
/system/framework/com.vzw.android.hux.jar
/system/framework/com.vzw.android.hux.odex
/system/framework/com.vzw.android.jar
/system/framework/com.vzw.android.odex
/system/framework/com.vzw.android.smart.jar
/system/framework/com.vzw.android.smart.odex
Instructions:
1. Root your phone if you haven't already
2. Install Busybox from Google Play if you haven't already
2. Uncompress the zip into your internal sdcard. You should get this:
Code:
/sdcard/removecrap/Apollo.apk
/sdcard/removecrap/Gallery2.apk
/sdcard/removecrap/com.teslacoilsw.launcher-1.apk
/sdcard/removecrap/remover.sh
3. Run from a terminal on the phone, or from adb (always as root)
sh /sdcard/removecrap/remover.sh
4. Wait until the phone reboots
5. 200 extra Mb of system and a lot more free ram for your apps. Oh, and Motorola won't get another bug report from you
EDIT: Ooops, Reupdated the zip file, it was deleting one extra file (motosignature inside the framework folder)
EDIT2: Didn't catch Carrier IQ's qer binary on /xbin. Unfortunately we can't touch those binaries since they're in the randisk, so I updated the script so it removes the logfile qe generates and replaces it with a folder so it can never write the scan results again (thank you bofh.bug for the links!)

That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk

highlandsun said:
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Probably OTAs will fail after running the script, but fixing it is as easy as reinstalling the system partition with fastboot and then applying the OTA
Sent from my DROID4 using xda app-developers app

This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.

arleslie said:
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
Click to expand...
Click to collapse
Were you able to fix the script so it works for CDMA users? Or, do you know what apps breaks it?

Very nice script, thanks. Easy way to run it by using Root Browser: open as script. But as for me QuickPick is better than ICS Galerry
Sent from my DROID4 using xda app-developers app

Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance

Tanzior said:
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Click to expand...
Click to collapse
I did again the script for the jelly bean update. This time it removes less crap, since it seems Motorola left a bit less than on previous versions. This will remove the annoying "Foreign card" warning when you boot the phone with some non-verizon sim, the acoustic warning when you turn up the volume, smart actions and so on.
IT WON'T REMOVE THE APPS. It will leave them here:
Apps: /system/app/oldapps
system binaries: /system/bin/oldbin
Framework: /system/framework/oldframework
If you encounter any problem, you can simply move back the files through adb and the phone will be like before applying the script.
NOTE: Only tested on GSM. Probably won't work on CMDA since it's missing most of the Verizon stuff. If you can identify which apps are needed for CDMA to wokr again tell me and I'll update the script accordingly.
I run the script from ADB and worked like a charm. Been using it for 24hours and no problems so far, but you never know, so use at your own risk
Code:
[email protected]:~/Documents# adb push removecrap2.sh /sdcard/removecrap2.sh
[email protected]:~/Documents# adb shell
[email protected]_maserati:/ $ su
[email protected]_maserati:/ # sh /sdcard/removecrap2.sh

It works great, thank you. Good work.
Sent from my DROID4 using xda app-developers app

Hi to all, i found two app : ModemPanicReporter.apk and ModemStatsService.apk. What they are doing ? Maybe it is necessary to remove they too ? Removing these applications will improve battery life.
Sent from my DROID4 using xda app-developers app

[MOD] [P6800] DXMD3 Stock Jelly Bean Phabletized! [HELP WANTED - SCRIPTING PROBLEMS]

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.

Database Develop

welcome