Database Develop

Enabling sideloading on Captivate with mac

Hi guys, I know some of you are just going to tell me to do a search on this, but I've already tried. So, my problem is, I'm very new to android and am trying to learn all this stuff and quickly and possible but it still feel like a giant noob because even when I've followed directions on what to do in Terminal it never works and I need some help. I've already rooted it and have removed At&T's bloatware and am running 2.1. Does anyone have, or have a link to relatively n00b related instructions for how to do this on a Mac thru terminal or something? Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App

You can install a rom if you want, thats what I did.

Jsmallsawe said:
Hi guys, I know some of you are just going to tell me to do a search on this, but I've already tried. So, my problem is, I'm very new to android and am trying to learn all this stuff and quickly and possible but it still feel like a giant noob because even when I've followed directions on what to do in Terminal it never works and I need some help. I've already rooted it and have removed At&T's bloatware and am running 2.1. Does anyone have, or have a link to relatively n00b related instructions for how to do this on a Mac thru terminal or something? Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Here's a link to how I did it. (and there are probably other ways like just simply flashing custom ROM).
1) Root'ed using one of the update.zip methods floating around. I think I used this one.
2) Downloaded Root Explorer and SQLite Editor. Both of these are paid apps but look like they are worth owning. For instance, you can also use Root Explorer to rename and disable the AT&T bloatware, as an alternative to this method.
3) Using Root Explorer, mount the filesystem R/W and copy /dbdata/databases/com.android.providers.settings/settings.db to /sdcard/settings.db
4) Open /sdcard/settings.db in SQLite Editor
5) Open the 'secure' table
6) Long-hold on record 6, "install_non_market_apps" and select "Edit Record"
7) Change the value from 0 to 1 and save
8) Back in Root Explorer, copy /sdcard/settings.db back to /dbdata/databases/com.android.providers.settings/settings.db
9) I don't remember if I had to reboot or not, but you may as well.
Click to expand...
Click to collapse
Couple of notes, instead of downloading SQLite Editor, you can download an add-on for firefox called SQLite Manager. Load up your settings.db and select secure, then I believe the numbering is different from SQLite Editor. Just find "install_non_market_apps", edit the value from 0 to 1, then copy and paste the new settings.db to the original location. You might also want to re-name the original settings.db to something so that the phone doesn't recognize it but it's there. Also you need to reboot.

[Q] Better Keyboard

So I just installed better keyboard and I went to enable it and Im getting a message that says "This input method may be able to collect all the text you type, including personal data like passwords and credit card numbers. It comes from the application Better Keyboards. Use this input method?"
Should this be something I should be worried about?

No. That is the standard Android warning when installing any keyboard.

Anyone know if Swype is working on here yet?

Can't get alternate keyboard to enable
After I get an alternate keyboard installed, I can't get the checkbox to enable. I get the warning described above but then the keyboard doesn't enable and doesn't appear as a choice when you do the long press and select input method.

I have the same problem with an IME for pen reader. the main justifyer for me to purchase this tablet was to take notes at work but I can't get teh app to work... I am just waiting for 3.0 and hoping that it will evolve...

justauser said:
After I get an alternate keyboard installed, I can't get the checkbox to enable. I get the warning described above but then the keyboard doesn't enable and doesn't appear as a choice when you do the long press and select input method.
Click to expand...
Click to collapse
Check this out:
http://forum.xda-developers.com/showpost.php?p=10128678&postcount=35

justauser said:
After I get an alternate keyboard installed, I can't get the checkbox to enable. I get the warning described above but then the keyboard doesn't enable and doesn't appear as a choice when you do the long press and select input method.
Click to expand...
Click to collapse
I was able to get SlideIt to work by installing it and then copying the apk file from /data/app and pasting it in /system/app. Then make sure to Mount R/W in the system folder and change permissions of the copied apk so that User is read/write and Group, Others is read only. Mount R/O. Now reboot. It should work now.
I am using TnT 2.2. There shouldn't be any need to enable it in the settings either. It will act like a system keyboard and will always be enabled. All you have to do is change input method by long tapping on a text box and selecting the newly installed keyboard.
I have tried this with a couple of other keyboards and it didn't work. Swype just says that it won't work with the screen size of the device.
I read this in another thread somewhere here. I can't take credit for this. Hope this helps.

keyboards
I'm running the stock rom with the TNT enhancement pack. The strange thing is that I can't even find the downloaded apk file for the keyboard. When I go to the data folder in iFileManager, it is blank. What am I doing wrong?

afarooki said:
I'm running the stock rom with the TNT enhancement pack. The strange thing is that I can't even find the downloaded apk file for the keyboard. When I go to the data folder in iFileManager, it is blank. What am I doing wrong?
Click to expand...
Click to collapse
From what I can tell, ES File Explorer can't see stuff in /data unless it is started AFTER the phone is rooted. Maybe the same goes for iFileManager.
So what I do is use z4root to get temporary root, kill ES File Explorer, then start ES File Explorer again. Then it can see /data.
Hope that this helps.
Jim

afarooki said:
I'm running the stock rom with the TNT enhancement pack. The strange thing is that I can't even find the downloaded apk file for the keyboard. When I go to the data folder in iFileManager, it is blank. What am I doing wrong?
Click to expand...
Click to collapse
I use Root Explorer and I have no problems seeing any files at all.

Block BN OTA Updates the EASY way!!!

First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.
Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.
Required Apps:
- Root Explorer (in market)
- SQLite Editor (in market)
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. Hope this helps!

RootNewbie said:
First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development...
Click to expand...
Click to collapse
Really? Or push a modified build.prop, done... *shrug*

Thats actually a good find because for a minute we were all sweating losing root over the 1.1.0 update.

khaytsus said:
Really? Or push a modified build.prop, done... *shrug*
Click to expand...
Click to collapse
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.

RootNewbie said:
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
Click to expand...
Click to collapse
Nobody I'm aware of, including my two NC's. Perhaps you're confusing updating the build.prop with renaming the otacerts file?
http://forum.xda-developers.com/showthread.php?t=930382

RootNewbie said:
First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.
Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.
Required Apps:
- Root Explorer (in market)
- SQLite Editor (in market)
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. Hope this helps!
Click to expand...
Click to collapse
Thanks for posting this. I'm sure it will help someone out. It would have been me a week or two ago. I was trying to figure out how to change this value to avoid the OTA and really didnt understand ADB, SDK, Sqlite or any of that then. when i first opened Root explorer i remember it asking me if i would like to purchase it and i declined, now if i only would have known how easy it could have been.

RootNewbie said:
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
Click to expand...
Click to collapse
I agree. Changing the setting in devicemanager.db is A LOT cleaner than the build.prop fix.

I just use a task killer and kill the B&N stuff... No updates here..

redking79 said:
I agree. Changing the setting in devicemanager.db is A LOT cleaner than the build.prop fix.
Click to expand...
Click to collapse
Considering this is how all Android OTAs are determined.... eh, whatever floats your boat

Slightly off-topic: I made this change (in devicemanager.db) to disable B&N updates. Whilst in the database, I noticed a table called Tasks that has 5 entries with types 100, 101, 102, 3, 2. The types 100 & 2 are tagged as enabled, the others are disabled. They have a date_next_run column. I imagine this is some kind of scheduling. I haven't worked out the date format. Does anyone know what these tasks will do - I would imagine one of them forces a B&N update?

RootNewbie said:
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Click to expand...
Click to collapse
Thank you for this- It's nice to find a nice, easy, self-contained way to ensure my NC will stay the way I have set it up 'til I decide otherwise.
One question though- to make it stick shouldn't there be one more step-
10. Reboot?

Block OTA updates
Xboxexpert has posted a bat file for download in a zip file Block updates.zip. Has anyone used this?
I need instructions regarding running the bat file.
Do I load the contents of the zip file on my SD card or do I open a command prompt box?
What do I do to run this bat file?
Thank you.

I can't get the "actions" window to pop up.

Wow this is an awesome find. Can anyone verify that this did indeed work for them? I have my rooted NC running 1.1 smoothly with all apps running perfectly. My final task is to stop OTA's from triggering. I don't feel confident doing this via ADB but using this method on the NC seems easy. Does this sound the same thing as the bat file does from the other thread? Thank you all for your amazing help!

Followed the process listed here... so far so good, no resets.

I have been through this 4 times so far and have been unable to get it to stick. I have backed up the rom after installing sqllite and root explorer, modded the registry, rebooted and still getting the damn OTA. Anyone else having this issue or has figured out if there is another entry that needs to be edited to defeat this?

Nm, I edited the url that the fota uses to check for updates so it is "dead"
backedup the rom again and have yet to see fota from BN. *fingers crossed as this is annoying*
****NM this didnt work either****

http://forum.xda-developers.com/showthread.php?t=930382

Thanks khaytsus! I do believe that has done the trick. I went ahead and edited the build.prop versus pushing it but we will see how it fairs now that i have hit wifi back on

Does this method still works to prevent 1.2 ota update? it surely looks the easiest method of all.
Yes or no?

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

How to get rid of the annoying "System Update"

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.