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,
Related
Hi,
I am currently developing an app for a customer. It is only intended for his staff. The specification says, the app should be updated automatically. The devices may not be rooted and are running Froyo and Gingerbread.
Is it possible to update the app without the user being able to stop the update and giving a feedback to the user on how long the update is going to take and its progress?
How can I get access to the program files without having root permission?
Or, if I can not, how can I install an APK while the user cannot interact with the installation. And can the installation automatically start the program when done?
Always bearing in mind, that I can not root the phones.
Thank you very much,
Chris
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.
Is there currently a way to have both the Amazon App store and the Google Play store working together? On the newest update?
Does rooting have any adverse affects from Amazon? Like will anything stop working?
I plan on buying a used tablet, how can I check to make sure the tablet is deactivated so that I can use my own Amazon stuff on it and it doesn't get marked as stolen?
I may think of other questions I need help with in the meantime, but thanks for any help.
everwhere
Hobox10 said:
Is there currently a way to have both the Amazon App store and the Google Play store working together? On the newest update?
Does rooting have any adverse affects from Amazon? Like will anything stop working?
I plan on buying a used tablet, how can I check to make sure the tablet is deactivated so that I can use my own Amazon stuff on it and it doesn't get marked as stolen?
I may think of other questions I need help with in the meantime, but thanks for any help.
Click to expand...
Click to collapse
Check out the general section, you will find the anwser you seek. if you have any other questions there is also a search abilility..there are only about a half a dozen threads titled with the same or basically the same as yours...thanks for visiting and I hope you find all the information you need. Previous owner must unregister. the tablet from their account before u received it.and I would attempt to register it and setup your account before cash exchanges hands or contact amazon with id to verify that it has not been blackliisted already, it can either be unregistered by owner from tab then reset . Or done through ther online account..
A lot of the threads I have read seem to have people contradicting or trying to figure out what actually works or not, or is simply outdated.
Yeah, I'm with OP. I have a new Fire HDX and am trying to figure out the 'best' way to root it, and after reading through everything I'm more confused than before.
I haven't taken my Fire out of the box yet. There seems to be discussion that if I haven't downloaded an OTA yet, I can root in a way others can't because the new updates block it?
Is there a known "best" ROM someone can point us to?
Why do I keep seeing everyone say 'don't ever turn on wifi!'? I assume that is just to not get the OTA update at the beginning. But once rooted, obv we can use wifi right?
Is every root method dependant on creating a separate partition for the new ROM, and whenever we use the Kindle we have to choose to use the stock amazon rom or the new ROM we've flashed?
Thanks!
well
lordtigger said:
Yeah, I'm with OP. I have a new Fire HDX and am trying to figure out the 'best' way to root it, and after reading through everything I'm more confused than before.
I haven't taken my Fire out of the box yet. There seems to be discussion that if I haven't downloaded an OTA yet, I can root in a way others can't because the new updates block it?
Is there a known "best" ROM someone can point us to?
Why do I keep seeing everyone say 'don't ever turn on wifi!'? I assume that is just to not get the OTA update at the beginning. But once rooted, obv we can use wifi right?
Is every root method dependant on creating a separate partition for the new ROM, and whenever we use the Kindle we have to choose to use the stock amazon rom or the new ROM we've flashed?
Thanks!
Click to expand...
Click to collapse
Well "root"has nothing to do with seperate partitions n such. root is all permission control over system.
The only way to flash anything currently is being on older os rooting,then installing safestrap which will set up alternate system and data boot path allowing you to flash a ROM separately from your factory os ,as to not disturb it. Because currently we do not have stable working fastboot for this device. As for BEST rom. In any situation is totally in one own experience and opinions. Currently there isn't any selection if u look in development section the only two that function only work on old firmware ...you can roll back to that firmware ..but also bootloader is locked tight thus the need for a "safe" type of recovery as of moment only works on older firmware also. Just.within the last couple of days have reveiled a couple of rooting options for lastest firmware so ...this tab per Amazon gives no warning nor asks permission to upgrade of firmware which unrooted a ton of people last few months...soooo no root no development....now we have root again we will get going again..Have fun and most of all be PATIENT and do not ask for ETA remember all the developers here are doing that on there FreeTime and free of pay most the time. AS FAR as rooting and adding gapps to newest firmware I heard that it has been achieved with HDXPOSED found in development and permission module . Then sideload gapps... As far as adverse effects... Like I said you will have to be patient if you want somebody else to find out bugs for you.. still to new .....due to new root releases..like last three days.
I'm perfectly fine with the stock rom honestly, as long as I can get Google Play store working alongside the Amazon app store. Now, assuming I can root when I receive the tablet, I will install safestrap. Is there any bugs or anything with safestrap but just using the stock rom? I saw some people mention getting permission errors and such but I think that was just for custom roms in another slot. I only want safestrap to make a backup.
Basically, is there any actual danger to modifying the stock rom at all, even something simply like play store? Or should it all be done on a custom rom slot? I would assume having the backup would mean if something got messed up I can just restore it.
Secondly, there is a SEPARATE play store mod you can do where they don't both work together right? I believe I saw something about it where you just have to install a custom launcher, and with the custom launcher the google play apps work but under the amazon launcher, amazon stuff works? If that's correct, does that work without root? Because I can live with that temporarily until root is secured.
Thanks.
nope
Hobox10 said:
I'm perfectly fine with the stock rom honestly, as long as I can get Google Play store working alongside the Amazon app store. Now, assuming I can root when I receive the tablet, I will install safestrap. Is there any bugs or anything with safestrap but just using the stock rom? I saw some people mention getting permission errors and such but I think that was just for custom roms in another slot. I only want safestrap to make a backup.
Basically, is there any actual danger to modifying the stock rom at all, even something simply like play store? Or should it all be done on a custom rom slot? I would assume having the backup would mean if something got messed up I can just restore it.
Secondly, there is a SEPARATE play store mod you can do where they don't both work together right? I believe I saw something about it where you just have to install a custom launcher, and with the custom launcher the google play apps work but under the amazon launcher, amazon stuff works? If that's correct, does that work without root? Because I can live with that temporarily until root is secured.
Thanks.
Click to expand...
Click to collapse
As far as I know gapps aside from gmail will not work without root and HDXposed..(fixes permissions)and as far as doing any mods to stock slot it is not advised because of very difficult if even possible recovery due to no fastboot capabilities. Check for bugs for any mods in associated threads. As far as flashing anything ,again I am not sure safestrap is functioning on latest firmware .. And there hasn't been enough time for any development because of the recent rooting capabilities.
Alright, so it sounds like this is what I should do then:
Get tablet
Root it (If I can't, then I stop here)
Install safestrap
Backup
Install the backup on romslot 1??
Make the modifications I want to romslot 1
Is that right?
Also let's assume I can't root it, I can still sideload most apps I want like Gmail, Youtube, etc? (Those aren't on the amazon app store correct?)
yeap
Hobox10 said:
Alright, so it sounds like this is what I should do then:
Get tablet
Root it (If I can't, then I stop here)
Install safestrap
Backup
Install the backup on romslot 1??
Make the modifications I want to romslot 1
Is that right?
Also let's assume I can't root it, I can still sideload most apps I want like Gmail, Youtube, etc? (Those aren't on the amazon app store correct?)
Click to expand...
Click to collapse
Yeah I would say you just about got the idea .... If it is a brand-new unit you have a possibility that it will be on the old firmware still ... That is why they need to bypass activation skip set up . And check firmware before you hook it to any active Wi-Fi service .. And even if it does or is already updated there is now root available for the latest firmware ... It's just a question whether or not we can get anything else to work along with the latest firmware ... I would be advised if you attempt to run the OTA blocker which comes in the HDX utility you may have Wi-Fi glitches and reboots .... But like I said those bugs need to be checked for and follow through and repaired in their associated threads ... Not a new thread that only plugs up our forums but puts the helpful threads on the next page where cannot find them ... Remember there are multiple pages each forum section and some of the helpful threads have been buried on the next page due to people starting new threads with the same questions or problem... That have been resolved already... Remember reading is more informative than typing . And remember if anybody here is giving you their personal time to answer your questions and respond to your post it is courtesy here to hit the thanks button in the left lower corner of the post.End rant. thx
<~~~~~~~~~~ ; )
Why is not possible to update from previous versions is that?( ota)
And is there a way to be alerted(get notofation on the phone) to update existing modules instead of occasionally enter the Xposted?(Was the only way my understanding?)
adome5 said:
Why is not possible to update from previous versions is that?( ota)
And is there a way to be alerted(get notofation on the phone) to update existing modules instead of occasionally enter the Xposted?(Was the only way my understanding?)
Click to expand...
Click to collapse
Up.. Someone?
adome5 said:
Up.. Someone?
Click to expand...
Click to collapse
Because it's not coded yet. Xposed is an open source project, by the way. You want installer to be able to update over-the-air? You want periodic update check and notifications? Go on, code it and submit a pull request.
To be honest I do not know how to do it and I just noticed that and thought to offer it as a proposal for streamlining. Also for alerts and regarding the automatic update ...
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.