FORUMS

[APP][DEV] OTA Update Center. (Released version 2.0.5)

306 posts
Thanks Meter: 334
 
Post Reply Email Thread
Announcement from M3nti0n: Version 2.0 Released, also available on the market! It's stable, and working on almost all devices!
26th February 2015, 06:22 AM |#631  
corphish's Avatar
Recognized Developer / Inactive Recognized Contributor
Flag Durgapur
Thanks Meter: 2,451
 
Donate to Me
More
Quote:
Originally Posted by qmobilea2

Dropbox did not work now and users got 403 forbidden errors and google drive doesn't create the direct links for 25MB file so suggest me any fast and direct link capable file hosting website ? Thank you

You can share Dropbox files using hot link.
Select the file and click share.
A share link will be generated.
It will look like - www.dropbox.com/blabla..
Just replace www.dropbox.com by dl.dropboxusercontent.com
And put the final download link, i.e
dl.dropboxusercontent.com/blabla...
In otaupdatecenter site in ur rom page, and u r done.
It works fr me.
To verify, try opening your otaupdatecenter rom page in incognito mode and download.
If download succeeds, you are done.
The Following 2 Users Say Thank You to corphish For This Useful Post: [ View ]
26th February 2015, 06:45 AM |#632  
berryman13's Avatar
Senior Member
Flag San Francisco
Thanks Meter: 1,246
 
Donate to Me
More
Subscribed. I'm the official maintainer of PAC ROM 5.0 for the nvidia shield tablet. My Google drive folder is already showing signs of taking up too much space at this rate so something like this would be a lifesaver once it comes time to release publicly. I would if I could but it would get removed. PAC is a project much greater than myself and the real work is done by people who started well before me. So I can't decide when their project is finished with its alpha testing, even if it runs fine on my device... It'd be disrespectful because they ask all maintainers not to publicly test their current builds.

Anyways.... I freaking can't wait to use this app. Seriously. I even made a new folder for it in my subscriptions
1st March 2015, 03:59 PM |#633  
Senior Member
Flag karachi
Thanks Meter: 237
 
More
Quote:
Originally Posted by AvinabaDalal

You can share Dropbox files using hot link.
Select the file and click share.
A share link will be generated.
It will look like - www.dropbox.com/blabla..
Just replace www.dropbox.com by dl.dropboxusercontent.com
And put the final download link, i.e
dl.dropboxusercontent.com/blabla...
In otaupdatecenter site in ur rom page, and u r done.
It works fr me.
To verify, try opening your otaupdatecenter rom page in incognito mode and download.
If download succeeds, you are done.

Thank you so much mate but now another problem appears as i have provided the ota to users and in that ota i replaced the older version of ota updater app with the latest version and now after installing that ota, my rom's users getting the invalid rom id ( screenshot attached below)
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2015-02-27-23-57-07.png
Views:	524
Size:	132.9 KB
ID:	3196119   Click image for larger version

Name:	Screenshot_2015-02-27-23-56-54.png
Views:	506
Size:	170.2 KB
ID:	3196120   Click image for larger version

Name:	Screenshot_2015-02-27-23-56-59.png
Views:	506
Size:	121.9 KB
ID:	3196121  
7th March 2015, 10:10 AM |#634  
OP Inactive Recognized Developer
Flag Zoetermeer
Thanks Meter: 334
 
Donate to Me
More
Quote:
Originally Posted by qmobilea2

Thank you so much mate but now another problem appears as i have provided the ota to users and in that ota i replaced the older version of ota updater app with the latest version and now after installing that ota, my rom's users getting the invalid rom id ( screenshot attached below)

Quote:
Originally Posted by AvinabaDalal

First of all thanks for great work and service.
I now host files using hot link, suitable for pushing updates via ota.
But one doubt,
I made users available an update via ota, I got user counter 15, ok.
Then I updated my rom and wanted to push it via ota (for the same device).
So i tried to add a new file, but failed due to same device .
So i modified the existing one, and success. I tested and ota notifications are coming as it should.

My question here is, the 15 users who got update previously, will get new update. Considering all of them updates, will the user counter tick to 30 or will it stay 15?

It will stay 15

Quote:
Originally Posted by qmobilea2

Thank you so much mate but now another problem appears as i have provided the ota to users and in that ota i replaced the older version of ota updater app with the latest version and now after installing that ota, my rom's users getting the invalid rom id ( screenshot attached below)

You obviously updated the app itself, without adding the ROM.OTA.prop instead of the build.prop options.

The OTA.prop has the recovery and path values.
The ROM.OTA.prop has the ROM values.
The KERNEL.OTA.prop has all the kernel updates values.

In the old version you needed the values inside the build.prop

I hope this helps you to fix your current problem.


How can I use this updater?
Code:
Download the latest APK from our GitHub page.
Pick a ROM/Kernel OTA ID that you will use on this site. This should be alpha-numeric (dashes and underscores allowed). This should be unique across our site (multiple files for separate devices can use the same OTA ID).
Add the following files to your ROM or Kernel:
/system/app/OTA-Updater.apk: OTA Updater APK you downloaded
/system/rom.ota.prop: ROM or Kernel version file
/system/ota.prop (optional): General properties file
/system/features/com.otaudater.feature.xml: OTA Updater feature file (get it here)
Package your ROM, generate an MD5 of the zip file, and upload it somewhere.
Add your ROM or Kernel on this site. You will need the OTA ID you picked, the device you packaged for, and the URL and MD5 of the zip file. When you have updates, simply update your ROM/Kernel here.
For further updates, just make sure you update the otatime and otaver properties in rom/kernel.ota.prop file
Optional settings for /system/ota.prop file:
{
    "noflash": "<< true or false - prevents app from rebooting into recovery for flashing (user must flash manually) >>",
    "rebootcmd": "<< reboot command if different than `reboot recovery` (can be a script included with ROM/Kernel) >>",
    "system_sdpath": "<< path to external storage in OS if it's non-standard >>",
    "recovery_sdpath": "<< path to external storage in recovery if it's non-standard >>"
}
Format for /system/rom.ota.prop file:
{
    "otaid": "<< ROM OTA ID >>",
    "otaver": "<< ROM Version >>",
    "otatime": "<< Date/time of ROM in yyyymmdd-hhmm format >>"
}
Format for /system/kernel.ota.prop file:
{
    "otaid": "<< Kernel OTA ID >>",
    "otaver": "<< Kernel Version >>",
    "otatime": "<< Date/time of Kernel in yyyymmdd-hhmm format >>",
    "fullver": "<< Output of `cat /proc/version` (*) >>"
}
* - this is necessary to detect if a ROM update overwrote your Kernel.
The Following User Says Thank You to M3nti0n For This Useful Post: [ View ] Gift M3nti0n Ad-Free
7th March 2015, 10:17 AM |#635  
corphish's Avatar
Recognized Developer / Inactive Recognized Contributor
Flag Durgapur
Thanks Meter: 2,451
 
Donate to Me
More
Quote:
Originally Posted by qmobilea2

Thank you so much mate but now another problem appears as i have provided the ota to users and in that ota i replaced the older version of ota updater app with the latest version and now after installing that ota, my rom's users getting the invalid rom id ( screenshot attached below)

Yeah, you need to push an xml permission file to system/etc.
Copy pasting didn't work for me, so what I did is downloaded the 2MB source from their git, and aquired the xml from it.
7th March 2015, 11:23 AM |#636  
Senior Member
Flag karachi
Thanks Meter: 237
 
More
Quote:
Originally Posted by AvinabaDalal

Yeah, you need to push an xml permission file to system/etc.
Copy pasting didn't work for me, so what I did is downloaded the 2MB source from their git, and aquired the xml from it.

But how bro ? they didn't getting the update which i issued last night just for checking

---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------

Quote:
Originally Posted by M3nti0n

It will stay 15



You obviously updated the app itself, without adding the ROM.OTA.prop instead of the build.prop options.

The OTA.prop has the recovery and path values.
The ROM.OTA.prop has the ROM values.
The KERNEL.OTA.prop has all the kernel updates values.

In the old version you needed the values inside the build.prop

I hope this helps you to fix your current problem.

Thankew very much for replying but mate my users are no more able to receive the update although in my roms section it is showing my rom and 70+ users but as i issued a update last night but still users haven't get the update notification. Hope you understand my condition
7th June 2015, 02:35 PM |#637  
UzUmAKI_NaRuTo1's Avatar
Senior Member
Flag Mumbai
Thanks Meter: 263
 
More
Quote:
Originally Posted by M3nti0n

OTA Update Center
Is an Over The Air update service, that is free of use.



OTA Update Center is an Over The Air update service, that is free of use. This project is especially for the rom devs around, to be able to implement an easy to use, and free OTA Update app. The project has one goal, to provide a way to provide OTA Updates as easy and noob friendly as possible.




I am trying to give a ota update for my ROM BUT, its not working

I have made sure it was a direct link still it says md5 error -invalid download !!


I get following results when i try these file hostings/clouds:-


XDA - given direct link from xda... it downloads whole update ..and immediately gives md5 error !


Gdrive - Gives md5 error without even downloading the file !!


Dropbox - it gives different error like this --> unable to get download status.




Someone please help , i need to get it working




EDIT :-

Now i tried hosting the file on webhost ftp....

this time to .. the whole zip gets downloaded but.. but as soon as it downloads
it throws md5 error - download is invalid
8th September 2015, 12:45 PM |#638  
Matx13's Avatar
Senior Member
Thanks Meter: 74
 
More
Hello,

Thank you for this application, it's been years since I use it for my roms customs, but on my new phone I have a problem...
With OTA Updater if I check Wipe Cache, the zip is not installed ! must uncheck "Wipe cache", how to solve this problem?

Thank you.

(Android 5.1 arm64; MT6752, recovery TWRP)
4th October 2015, 08:49 PM |#639  
Mentalmuso's Avatar
Recognized Developer
Flag Austin
Thanks Meter: 8,417
 
Donate to Me
More
Is anyone aware of anything i can do to stop the automatic reboot while in recovery just after the rom has flashed? My rom requires a second Aroma addon zip to be flashed straight after the base rom, having it reboot straight after the zip flash is causing problems.
The Following User Says Thank You to Mentalmuso For This Useful Post: [ View ]
14th March 2016, 05:46 PM |#640  
Duck1245's Avatar
Senior Member
Flag Colombia
Thanks Meter: 177
 
More
someone has a tutorial on how to configure OTA I am developing a rom?
20th March 2016, 06:12 AM |#641  
Member
Thanks Meter: 16
 
More
I'll make this short and sweet:

Will this work with Stock Touchwhiz 6.01

Or is it for custom Roms only
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes