Related
What is the best way to block OTA updates without flashing a new rom? I am rooted, and have removed some bloat as well a changed the mms.apk, as well as the lock screen. I have also fixed permissions through rom manager. I can use adb etc... Best suggestion?
If you installed CWM recovery you won't receive any updates.
ikon8 said:
If you installed CWM recovery you won't receive any updates.
Click to expand...
Click to collapse
false, you have to change some stuff in the build.prop
magneticzero said:
false, you have to change some stuff in the build.prop
Click to expand...
Click to collapse
You'll still receive update notifications but they won't install. But you're correct that you'll still receive notifications about an available update until you change the fingerprint in build.prop
Is there any particular format to change the fingerprint? Or do I simply change it from what it states to something different? And I assume we are talking about the line ro.build.fingerprint= verizon...etc.
When an update is available you can change the fingerprint to match the update's fingerprint so that it stops notifying you of the update. And yea, it's the ro.build.fingerprint= line.
Or ask someone with the .9 rom or something to upload their build.prop and steal that and hope you dont get an update nag message
Thank you!
I can't seem to find which program to freeze in Titanium Backup. Any ideas out there?
Have any 10e root users accepted the update? Do you lose root even with Voodoo Keeper?
Thanks!
You can try freezing 'lgfotapermission' app using Titanium Back up. It's just my guess. No guarantees. YMMV.
csrow said:
You can try freezing 'lgfotapermission' app using Titanium Back up. It's just my guess. No guarantees. YMMV.
Click to expand...
Click to collapse
Thanks for the reply. I think i'll wait for now and see if anyone else chimes in.
yettie10ff said:
Thanks for the reply. I think i'll wait for now and see if anyone else chimes in.
Click to expand...
Click to collapse
Mine is frozen and no updates yet. Just make up your mind before the phone gets updated automatically.
csrow said:
Mine is frozen and no updates yet. Just make up your mind before the phone gets updated automatically.
Click to expand...
Click to collapse
Ok - thanks. Can you always unfreeze applications without any harm? Not to nag, but curious how you decided on that file? Google search on that name, turns up nothing.
csrow said:
You can try freezing 'lgfotapermission' app using Titanium Back up. It's just my guess. No guarantees. YMMV.
Click to expand...
Click to collapse
Actually looking thru the backup/restore column in titanium backup I don't see that app anywhere. Only LG prefixed app's I see are as follows:
LG Keyboard...
LG MLT 2.3.8
LGinstallservice 1.3.11 (Perhaps this could be it??)
LGSetupWizard 4.3.013
LGSystemServer 1.0
yettie10ff said:
Actually looking thru the backup/restore column in titanium backup I don't see that app anywhere. Only LG prefixed app's I see are as follows:
LG Keyboard...
LG MLT 2.3.8
LGinstallservice 1.3.11 (Perhaps this could be it??)
LGSetupWizard 4.3.013
LGSystemServer 1.0
Click to expand...
Click to collapse
I don't have my phone with me but look for something like
com.LG.lgfotapermission.apk
fota = firmware over the air
csrow said:
I don't have my phone with me but look for something like
com.LG.lgfotapermission.apk
fota = firmware over the air
Click to expand...
Click to collapse
Thanks - I found it, and froze it, however I'm still getting the notification. Even after reset. Odd.
I believe the update check code is embedded into the settings apk. It will need to be re-compiled to prevent this.
If we knew what URL the device is getting its updates from we can block it with a hosts entry.
I found some info here on disabling the update notification for anyone who is still interested.
http://forum.xda-developers.com/showthread.php?t=2006946
It looks like you need to freeze these two apps in Titanium Backup:
com.lge.lgfota.permission
com.lge.omadmclient
V10C P765 Rooted
I simply unchecked following option and I think it stops future OTA Notification.
Settings >>> About Phone >>> Software Update >>> Check Automatically (Uncheck this)
May be I am wrong, may be you pals are talking something else..
kevev said:
I found some info here on disabling the update notification for anyone who is still interested.
http://forum.xda-developers.com/showthread.php?t=2006946
It looks like you need to freeze these two apps in Titanium Backup:
com.lge.lgfota.permission
com.lge.omadmclient
Click to expand...
Click to collapse
Doesn't seem to work as update notification is still popping up on my P769.
This is how I stoped my phone from updateing and nagging. ( Must be rooted )
1. Download and install ( system tuner apk from playstore )
2. Launch system tuner and choose ( system with the red icon )
3. Choose (Google services framework ) and hit (details)
4. Scroll down to services and uncheck ( update.systemUpdateService
Thats all.
Hit thanks if it helped.
Sent from my LG-P769 using xda premium
This one works for me on P769
Originally Posted by kamikazekyle (http://forum.xda-developers.com/showthread.php?p=37687393#post37687393)
While I can't vouch for anything else besides the P675 10e Tmobile version, the following method will stop the update prompts. It *should* work on all ICS and JB devices, including Nexus.
0. Root, if you haven't already.
1. Download AutoRun Manager
2. In ARM, choose "Advanced"
3. Touch the wrench icon, and check
- Show System Entries
- Enable System Application Disable
4. Back on the application list, tap the refresh (circle arrow) icon if you don't see system apps. They should have a red background.
5. Find the app Google System Framework (aka: GSF) and tap it.
6. Uncheck the "com.google.<something>.gsf.update.SystemUpdate" receivers. I can't read my own handwriting at the moment, but they both end in SystemUpdate.
Am I the only one who definitely DONOT hit thanks when I see this line "Hit thanks if it helped"?
Thread cleaned. I don't see the reason of this whole argue you had. If someone wants to post hit thanks, let it be. It's definitely not worthy to be discussed. Now you should both excuse each other for jumping the guns for nothing.
I really hope you will.
eagleeyetom said:
Thread cleaned. I don't see the reason of this whole argue you had. If someone wants to post hit thanks, let it be. It's definitely not worthy to be discussed. Now you should both excuse each other for jumping the guns for nothing.
I really hope you will.
Click to expand...
Click to collapse
+2. One from samomamo and one from me. Now lets all be on topic.
Sent from my LG-P765 using xda app-developers app
cmahendra said:
V10C P765 Rooted
I simply unchecked following option and I think it stops future OTA Notification.
Settings >>> About Phone >>> Software Update >>> Check Automatically (Uncheck this)
May be I am wrong, may be you pals are talking something else..
Click to expand...
Click to collapse
Can't find anywhere to do that on my phone. Of course I have a different phone, P769, think that is why?
---------- Post added at 02:47 PM ---------- Previous post was at 02:25 PM ----------
Vo_Dich said:
Doesn't seem to work as update notification is still popping up on my P769.
Click to expand...
Click to collapse
Ditto. Not working for me either.
samomamo said:
This is how I stoped my phone from updateing and nagging. ( Must be rooted )
1. Download and install ( system tuner apk from playstore )
2. Launch system tuner and choose ( system with the red icon )
3. Choose (Google services framework ) and hit (details)
4. Scroll down to services and uncheck ( update.systemUpdateService
Click to expand...
Click to collapse
This caused a permanent wakelock on SystemUpdateService on my LG Optimus P769, so my phone never went to sleep mode. I even rebooted several times, and checked over several days. As soon as I re-enabled update.systemUpdateService, the phone was able to sleep again. It did seem to prevent the OTA popup from re-appearing, but at a cost of battery life.
kevev said:
I found some info here on disabling the update notification for anyone who is still interested.
http://forum.xda-developers.com/showthread.php?t=2006946
It looks like you need to freeze these two apps in Titanium Backup:
com.lge.lgfota.permission
com.lge.omadmclient
Click to expand...
Click to collapse
Well I used Titanium backup to freeze com.lge.lgfota.permission and I used root explorer to change the lgfota.apk in \system\app folder to lgfota.bak and reboot.
No longer a needed tread and has been locked.
This thread is for discussing early development for the Omate TrueSmart. The current and most pressing is if Omate does not receive Google's OK for Gapps and play store. How to get this installed on a device using something your grandmother could figure out. Lets assume that Omate will commit installing CWM on all devices. So the set up would then be
Unrooted
CWM recovery
What's needed know- Can your script a device to reboot into CWM and flash a file then reboot normally without root?
How it implement- Have an app dl a "fixme.zip" and run the flash script with minimal interaction from the user.
(I know this is a mess but it's 5am and I have slept yet)
Recovery first
First question to answer:
TWRP or CWM as custom recovery?
We want Omate to ship the device unrooted, but with a custom recovery. The recovery can then be used to easily do the following tasks:
Install official updates from Omate (OTA)
Install unofficial updates from the community
Root the device
Install Google apps (in case there is no official support when the devices are shipping)
The recovery should allow instaling updates AUTOMATICALLY, that means SCRIPTED.
TWRP support OpenRecoveryScripting. Does CWM support scripting?
How much work is it to compile TWRP and CWM? Anybody experience with that?
---------- Post added at 02:23 PM ---------- Previous post was at 02:14 PM ----------
Here's a link about OpenRecoveryScripting:
http://www.teamw.in/OpenRecoveryScript
---------- Post added at 02:30 PM ---------- Previous post was at 02:23 PM ----------
Just one more idea:
What about a pre-installed app for installing "official" and "unofficial" apps?
The app could, e.g. look at a list of servers and retrieve potential updates. Similar to the updater of CM.
In the settings, we could specify what servers to use, so the watch as shipped would only look on Omate server. But you could tick an option like "Community updates" and the app would also check goo.im (or similar). That way, we could provide an "unofficial" update to install Google Apps.
If the user decides to install the update, the update should work completely automatically, if possible. So, just one click, then download, reboot to recovery, install and reboot again.
Anybody experience with the CM updater? Source code is open source, I guess?
Seeing that cwm is already built going with twrp should be a last resort. We would most likely need access to Omate's files to compile twpr and have anything we could even submit to them for testing.
From this link http://www.teamw.in/OpenRecoveryScript I got the impression that CWM also supports at least a subpart of OpenRecoveryScripting.
Did anyone see this? http://www.xda-developers.com/android/effortlessly-download-gapps-packages-with-easygapps/ ??
Can it be given to Omate to INCLUDE in the standard pre-installed apps?
WIll it work?
chrisvor said:
Did anyone see this? http://www.xda-developers.com/android/effortlessly-download-gapps-packages-with-easygapps/ ??
Can it be given to Omate to INCLUDE in the standard pre-installed apps?
WIll it work?
Click to expand...
Click to collapse
Very nice one. But Omate probably cannot include that into the pre-installed apps.
But the Updater app we are talking about could work very, very similar. Maybe we can get the dev involved in this project?
Lokifish Marz said:
We would most likely need access to Omate's files to compile twpr and have anything we could even submit to them for testing.
Click to expand...
Click to collapse
The porting "kit" would most probably come from mediaTek and be covered by an NDA. That is assuming Omate did the port themselves and didn't just receive the whole kernel ported and compiled from MediaTek. In both cases, given that MediaTek doesn't publish much info on their site its most probably covered by a NDA.
Neuer_User said:
Very nice one. But Omate probably cannot include that into the pre-installed apps.
But the Updater app we are talking about could work very, very similar. Maybe we can get the dev involved in this project?
Click to expand...
Click to collapse
I'm going to look into itanyways. Think, dl this apk, put on device and open it up in the file browser. This would trigger package manager and install it. Simply mention it and giving a link to the thread / apk would go a long ways. Hopefully root is not needed or regular folks will be boned.
Omate still needs to remove the play store included statement until they get an official answer from google or it will continue to cause problems.
iraqigeek said:
The porting "kit" would most probably come from mediaTek and be covered by an NDA. That is assuming Omate did the port themselves and didn't just receive the whole kernel ported and compiled from MediaTek. In both cases, given that MediaTek doesn't publish much info on their site its most probably covered by a NDA.
Click to expand...
Click to collapse
"
Solution. Pick some firmware devs and make them "subcontractors". I'm already under an NDA with Omate as it stands. It would just need to be amended.
Lokifish Marz said:
Solution. Pick some firmware devs and make them "subcontractors". I'm already under an NDA with Omate as it stands. It would just need to be amended.
Click to expand...
Click to collapse
If the work was commissioned by Omate. If not, wouldn't that also count as a breach of NDA?
My understanding is that the dev edition already comes with CWM, I recall reading a comment by Omate that they were already using it internally. If so, its simply a matter of extending CWM installation to all production units instead of dev only.
Updater code
Here is the code of the old CM updater app:
http://code.google.com/p/cyanogen-updater/
Lots of code, but maybe, if the original dev would be interested in the Omate, too, he might go and adapt his code?
iraqigeek said:
If the work was commissioned by Omate. If not, wouldn't that also count as a breach of NDA?
My understanding is that the dev edition already comes with CWM, I recall reading a comment by Omate that they were already using it internally. If so, its simply a matter of extending CWM installation to all production units instead of dev only.
Click to expand...
Click to collapse
There's a couple different ways it can be approached. I don't know what Omate's agreement is with MediaTek or Umeox regarding the firmware.
Even if CWM came preinstalled on all versions, flashing a gapps.zip is still not noob friendly. That's what I want to resolve. Something as simple as "visit this page and install this app" at the least and a preinstalled "one click" solution at best.
The other side of getting hands on the firmware ahead of time. Think of all those edits and tweaks being factory vs having to flash a custom rom. Oppo does this and has gained a a ton of attention as a result.
Even if CWM came preinstalled on all versions, flashing a gapps.zip is still not noob friendly. That's what I want to resolve. Something as simple as "visit this page and install this app" at the least and a preinstalled "one click" solution at best.
Click to expand...
Click to collapse
That's why I thought about the CM updater app.
The point is: In order to get CWM to do a scripted install the scripts need to be saved to /cache/recovery/openrecoveryscript
I'm pretty sure you can do that only with root rights. So, it would be best, if the updater would be bundled with the firmware. If you need to side-load the app, you would need to assign root rights etc. Not that easy for the average user.
A pre-bundeled Updater app could be the easiest way. Omate claims to have OTA updates. So the mechanism is already there. We only need to have a UI for the user to choose to install an "unofficial" Gapps update from a community server (goo.im) instead of only the official updates from Omate.
We really need an Omate guy here you understands this and the way they currently plan OTA updates!!
Neuer_User said:
That's why I thought about the CM updater app.
The point is: In order to get CWM to do a scripted install the scripts need to be saved to /cache/recovery/openrecoveryscript
I'm pretty sure you can do that only with root rights. So, it would be best, if the updater would be bundled with the firmware. If you need to side-load the app, you would need to assign root rights etc. Not that easy for the average user.
A pre-bundeled Updater app could be the easiest way. Omate claims to have OTA updates. So the mechanism is already there. We only need to have a UI for the user to choose to install an "unofficial" Gapps update from a community server (goo.im) instead of only the official updates from Omate.
We really need an Omate guy here you understands this and the way they currently plan OTA updates!!
Click to expand...
Click to collapse
Unless something has dramatically changed in the past week or so, you do not need root to side load most apps. I side load diagnostics apps all the time on tons of phones. If the gapps installer that was linked a couple of posts back does not need root to run then the "visit this page and install this app" is resolved.
Lokifish Marz said:
Unless something has dramatically changed in the past week or so, you do not need root to side load most apps. I side load diagnostics apps all the time on tons of phones. If the gapps installer that was linked a couple of posts back does not need root to run then the "visit this page and install this app" is resolved.
Click to expand...
Click to collapse
You misunderstood me.
Sure, you don't need root to side-load apps.
But I believe you need root to script CWM. The script must be put into /cache/recovery/openrecoveryscript and that is, I think, only accessible as root.
If you want to install Gapps, then this needs to fgo through CWM. If it goes through CWM, you don't want the user to manually go though CWM, but to do the installation automatically. And therefore you need a script telling CWM what to do ("install /sdcard/updates/Gapps.zip", "reboot"). And to save this script you need root. Also, to automatically reboot into recovery, you would need to have root.
So the app downloading the update would need to have root. And that is best, if it is already pre-installed.
I'm goign to try some thing and get back to you. It may take me a little bit as I don't have a singled unrooted device in my house.
Well, anyway. I want a definite commitment from omate to support any development we do. Otherwise, I won't invest time into this.
Let's hope some omate firmware guy will join this discussion here soon.
Neuer_User said:
Well, anyway. I want a definite commitment from omate to support any development we do. Otherwise, I won't invest time into this.
Let's hope some omate firmware guy will join this discussion here soon.
Click to expand...
Click to collapse
At least publicly, they're pretending that business is as usual and nothing happened. Instead of posting an update explaining what is what, they posted about the Clockface contest.
Speaking of Clockfaces, shouldn't those too be something devs can make through their SDK? Seems those too will be restricted to a few predefined ones :\
iraqigeek said:
At least publicly, they're pretending that business is as usual and nothing happened. Instead of posting an update explaining what is what, they posted about the Clockface contest.
Speaking of Clockfaces, shouldn't those too be something devs can make through their SDK? Seems those too will be restricted to a few predefined ones :\
Click to expand...
Click to collapse
Their failure to edit the kickstart page is a really bad idea. I will not go into details on this.
They should but we don't even know what the app is even capable of at this point. I posted my concept InfoCenter Clock just in case the clockface app has those functions. If it doesn't, it won't stay on my Omate for long.
Lokifish Marz said:
Their failure to edit the kickstart page is a really bad idea. I will not go into details on this.
Click to expand...
Click to collapse
That's what is also worrying me. The Kickstarter FAQ doesn't say anything about removing promised features, let alone doing so a few days before the campaign ends. I'm worried Omate will try to resolve this with Google until the last moment, then abruptly change the project to remove the play feature and jeopardize the whole campaign.
Ok. here's where I'm at with this. There was a workaround app "Google Installer" but it no longer works. What it did was install Play Store and services as regular apps from a remote server. I found an updated replacement that is in Chinese ONLY but it requires root and it's permissions are suspect. Also, forget any scripting while booted normally without root. It's a no go.
I need to take a break from this as I've been digging through poorly translated Chinese and Russian forums and the regular sources for hours trying to see if I missed something. My head and eyes are killing me.
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Alternatively, you can simply freeze the System Updates process via Titanium Backup, as discussed in the Bloatware thread.
What OTA ?
Cruiserdude said:
What OTA ?
Click to expand...
Click to collapse
I think they are just being proactive... in case one comes this year.
Cruiserdude said:
What OTA ?
Click to expand...
Click to collapse
My thoughts exactly. Disable updates for what? Verizon has their heads up their asses in that regard.
Wildcat2083 said:
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Click to expand...
Click to collapse
Thanks for the information. Verizon began pushing an OTA to my LG G3 today. It was very annoying, thanks again!
Thank you, but it seems I'm too late.
Now, event though I've unchecked it, I keep getting a menu to do an update. I keep pressing back to get out of the update now or schedule an update later, but I can't seem to get it to go away, Gonna try the titanium update freeze of the updater.
Disabling the System Updates apk also works.
Sent from my VS985 4G
Thanks for sharing!
Tillmorn said:
Alternatively, you can simply freeze the System Updates process via Titanium Backup, as discussed in the Bloatware thread.
Click to expand...
Click to collapse
Alternatively you can do what OP said since its easier and requires no third party apps or root. But hey, cool story bro.
Thank you. This method works. I tried the other two and they didn't work. The "hidden menu" version came up with a different menu than in the description and TiBU didn't stop the notifications (for me). First I tried moving the update files to a new directory I created, but the update message had already been triggered.
If you pull down the notifications and long-press on the OTA, you can disable the app and remove the icon from the screen.
Wildcat2083 said:
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Click to expand...
Click to collapse
Wildcat2083 said:
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Click to expand...
Click to collapse
At first I thought this worked, but it ended up not working. As you can see in the image below, I have the ota-dm unchecked, which worked for a while, but today the system update dialog/notification came back.
killswitch23456 said:
At first I thought this worked, but it ended up not working. As you can see in the image below, I have the ota-dm unchecked, which worked for a while, but today the system update dialog/notification came back.
Click to expand...
Click to collapse
Getting this too
Same here
Use Rom toolbox pro to freeze the 2 ota apps, titanium is junk.
Afterwards, delete any files in root/cache/fota.
Sent from my VS985 4G
Or use free app called Uninstall Expert and freeze it that way too
Sent from my Verizon LG G3 using Tapatalk
NetworkingPro said:
Alternatively you can do what OP said since its easier and requires no third party apps or root. But hey, cool story bro.
Click to expand...
Click to collapse
If you've already got root...which most people who are trying to stop OTAs have because they're wanting to keep root...why would you not simply freeze the process while you're going about the task of freezing all the bloat from Verizon? To me, that's easier as it allows a single action to restore everything back to stock settings (plus root and Bump) instead of having to use multiple methods to get back to such a state. But to each their own. I understand that some people like having their mobile OS weighed down from carrier installed garbage. Regardless, what kind of person knocks someone else for daring to add to the discussion with another method that, for many (especially those eventually wanting to flash ROMS), streamlines everything?
What are the exact names of the OTA apks? I looked in system/app and system/priv-apps.. Nothing really reads as system Ota or Ota something. Maybe I missed it. I would like to rename them manually.
Edit: is it LGFOTA.apk and its odex file?
Edit: ok thats not it update popped up after reboot. I now think its LGDMSClient.apk
jfriend33 said:
Or use free app called Uninstall Expert and freeze it that way too
Sent from my Verizon LG G3 using Tapatalk
Click to expand...
Click to collapse
This worked for me! Thank you very much!
MunkinDrunky said:
What are the exact names of the OTA apks? I looked in system/app and system/priv-apps.. Nothing really reads as system Ota or Ota something. Maybe I missed it. I would like to rename them manually.
Edit: is it LGFOTA.apk and its odex file?
Edit: ok thats not it update popped up after reboot. I now think its LGDMSClient.apk
Click to expand...
Click to collapse
It's a blue icon called 'system updates' in your application manager in your settings.
Hello All,
I want to add my OTA server URL into AOSP for my released device and I know I can use some applications to do it but I want to modify the default URL of Google's AOSP. I had been grabed OTA URL of Nexus 5 (android.clients.google.com....) as well as got some logs (from adb logcat) then I used grep command with some keywords as "android.clients.google.com/", "SystemUpdateService", "DownloadAttemp",... to find where the URL in. But I found nothing.
Anyone can tell me where I can change default OTA server URL.
Thanks,
Can anyone help me?
You most probably receive push notifications, so the URL is not available. I know though that the app you have to freeze if you want to disable OTAsin rooted devices is "Software update MUC", so you may start searching for that app in the sources.
A side note: although it would be way better to use the official OTA application rather than using 3rd party software as ROMs use to, there must be a reason. I once thought about modding that app, but never had the time nor the real intereset in doing so, as I'm out of custom ROMs development ATM.
I don't know if recent custom recoveries are able to detect the official OTA signals to automatically flash the update, nor if, for instance, the log is encrypted or not.
elegos said:
You most probably receive push notifications, so the URL is not available. I know though that the app you have to freeze if you want to disable OTAsin rooted devices is "Software update MUC", so you may start searching for that app in the sources.
A side note: although it would be way better to use the official OTA application rather than using 3rd party software as ROMs use to, there must be a reason. I once thought about modding that app, but never had the time nor the real intereset in doing so, as I'm out of custom ROMs development ATM.
I don't know if recent custom recoveries are able to detect the official OTA signals to automatically flash the update, nor if, for instance, the log is encrypted or not.
Click to expand...
Click to collapse
Thank you so much,