Pushing out a ROM update? - Nexus 6P Q&A, Help & Troubleshooting

Hey,
I'm working on a 6P Marshmallow ROM and wanted to know if there is a way you can push out a software update to every device running the ROM?
Example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm planning on pushing an update for Nougat to current Marshmallow devices, if possible. I'm new to Android development and was just curious.. would I need to have a dedicated server for this?

hjterry said:
Hey,
I'm working on a 6P Marshmallow ROM and wanted to know if there is a way you can push out a software update to every device running the ROM?
Example:
I'm planning on pushing an update for Nougat to current Marshmallow devices, if possible. I'm new to Android development and was just curious.. would I need to have a dedicated server for this?
Click to expand...
Click to collapse
I know some Developers use something like Pushbullet.
But a build-in notification and update function could be also possible if you implement it in your rom, but i never tried it so i cant say anything about it.
One way could be, watching the source code of other Roms which has implemented this feature, but then you must check if this is legal and the original developer is okay with that.

kaufikauf said:
I know some Developers use something like Pushbullet.
But a build-in notification and update function could be also possible if you implement it in your rom, but i never tried it so i cant say anything about it.
One way could be, watching the source code of other Roms which has implemented this feature, but then you must check if this is legal and the original developer is okay with that.
Click to expand...
Click to collapse
Pretty sure CM has that baked in

kaufikauf said:
I know some Developers use something like Pushbullet.
But a build-in notification and update function could be also possible if you implement it in your rom, but i never tried it so i cant say anything about it.
One way could be, watching the source code of other Roms which has implemented this feature, but then you must check if this is legal and the original developer is okay with that.
Click to expand...
Click to collapse
I actually found a tool called OTA Update Center, and it allows you to notify users of new ROM updates. It's pretty old, but should get the job done.

Related

Bugs in stock phone

I am assuming once you root the phone and push a custom ROM onto the phone, this will fix HTC's introduced bugs?
Bluetooth
SMS battery drain
Reverting apps versions
Stuff like this.
No, because the custom ROM is just the Sprint ROM with a few additions and modifications.
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Treefallingquietly said:
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Click to expand...
Click to collapse
HTC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although the bugs are not fixed, rooting allow one to use various workarounds that would not be possible without, and in fact for EACH of the issues you have listed:
Bluetooth: http://community.sprint.com/baw/thread/23854?tstart=0
While I cannot personally vouge for this, I have seen many posts on Sprint and here that detail the workaround described in the post as effective.
SMS Battery Drain: I think this may have actually been the first big bug discovered, and also fixed without root! Unfortunately, the default messaging app is defective, so in the meantime it is recommended to use either chompSMS or Handcent SMS from the Market until an update is released.
See this post: http://community.sprint.com/baw/thread/23043
Finally...
Reverting Apps: This is addressed on both forums, but a workaround only exists with root, and is similar in fashion to the bluetooth fix but for a different directory.
http://forum.xda-developers.com/showthread.php?t=582176
http://forum.xda-developers.com/showthread.php?t=581806
Hope this helps! I intend on posting a very detailed guide on every step of rooting, backing up, and working around most of the detailed problems in the very near future, stay tuned!
What I'd like is a kernel that will have this working as intended. But really, I am not afraid of the work arounds and the hands on work required, but if my wife had this phone with these problems, she would have chucked it out the window within days.
One more...
You left out the original bug (mentioned by briankwest, one of the first rooters), the TCP timestamp issue:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
This could also be added to the MoDaCo init.rc so it is set at each boot (otherwise it will revert back to "1").

[Q] Change device ID/Name for wifi?

Hi all, hoping you can help me out with this. It's not a critical issue, more a vanity/QOL thing.
I'd like to change the device name/ID that shows up when connecting my Nexus 7 to a wifi network. Currently it shows up as "android-<string of alphanumerics>" but I'd like to be able to give it a more descriptive name to help differentiate when setting up a wifi connection around multiple similar devices.
I've got my N7 rooted but not unlocked, and I'd prefer not to flash a custom ROM if possible. I'm no stranger to flashing ROMs, I'm just not interested in putting a huge amount of work or potentially causing myself problems for something that is so relatively minor.. I can live without a custom device name, but it would be nice to be able to set one up.
Thanks in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is that screenshot from the custom ROM you have listed in your sig?
I'm using a stock N7 with build JDQ39 and I don't seem to have many of those options listed in the Developer Options menu. Or is there something I need to do to enable those, similar to the method used to 'unhide' the Developer Options in the first place?
My apologies if this is basic information that I could have found elsewhere.
TechDragon said:
Is that screenshot from the custom ROM you have listed in your sig?
I'm using a stock N7 with build JDQ39 and I don't seem to have many of those options listed in the Developer Options menu. Or is there something I need to do to enable those, similar to the method used to 'unhide' the Developer Options in the first place?
My apologies if this is basic information that I could have found elsewhere.
Click to expand...
Click to collapse
Yes it is Slim Bean Build 7. That is just what I use as it is included in the ROM. You can set it manually or use an app such as these.
Wow.. I feel incredibly dumb right now. I'm so used to doing things the hard way I didn't even consider checking if there were apps in the store that might do what I wanted. Thanks for reminding me to look in the easy places first!
Cheers!

5.1.1 InSaNiTy Rom found out there

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just want to give this hint. i am not the dev, i've got nothing to do with this work. the whole honor belongs to cannondalev2000. just found it while searching for another rom for another device and like to share for those who can't get enough of flashing and testing roms, as i do .
the link(s):http://drdevs.com/devs/cannondalev2000/InSaNiTy/
- LMY48B 5.1.1r4
Rom seems to get updated from time to time
0616 build up
i flashed it and it boots. attacked kernel was flashed by myself.
Edit: used it since yesterday and no problems so far. Works good.
Final edit: now supported in dev section forum.xda-developers.com/moto-g/development/insanity-ethan-t3135382
cheers
Thanks for the information...
Any informations about this rom? Mayby site of this rom? G+? anything?
plantator said:
Any informations about this rom? Mayby site of this rom? G+? anything?
Click to expand...
Click to collapse
Tried to find something, but no luck. Strange. It's slim based Android 5.1.1r4, uses layers but not working quite right atm. The rom itself working flawlessly. There are just a few modification options like changing height of navbar. As mentioned in op I'm using it with latest attacked kernel. That's all I know atm.
This rom was compiled by cannondalev2000, a great dev. I used some of his KK roms. Actually his account has been disabled, I don't know why...
Dual SIm Works
$lim $hady said:
Dual SIm Works
Click to expand...
Click to collapse
Needs to be tested by somebody else as I have single sim
I am opening up thread in Dev section shortly
Well check out the dev section with full details
http://forum.xda-developers.com/moto-g/development/insanity-ethan-t3135382
thank you so much, I've searched for it so long
sfoot13 said:
This rom was compiled by cannondalev2000, a great dev. I used some of his KK roms. Actually his account has been disabled, I don't know why...
Click to expand...
Click to collapse
his name is ethan. Well due some unfortunate reason his account is disabled. he created this ROM on my request.... Enjoy the ROM
sachoosaini said:
his name is ethan. Well due some unfortunate reason his account is disabled. he created this ROM on my request.... Enjoy the ROM
Click to expand...
Click to collapse
Ethan Chen? The code reviewer from CM?
follow google plus profile
sfoot13 said:
Ethan Chen? The code reviewer from CM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/development/insanity-ethan-t3135382?styleid=21

Sony releases the binaries for Android M!

Holy smokes that was fast! Kudos Sony!
http://developer.sonymobile.com/201...-binaries-added-to-sonys-open-device-program/
Meaning the "preview" will soon perish nice
Btw, thats with 3.10 kernel?
Gonna do a build now, who's keen to flash? I doubt many things will work, mainly RIL (Phone/SMS) and Camera that I'm 99% sure wont..
Just got my phone back from Warranty so not going to unlock just yet in case it has it's own issues right away.
I think the AOSP builds have availabled for 3 months ago? Just have not been the latest binary.
Sent from my Xperia Z2 using Tapatalk
The older builds still used the old API level and didn't include all of the features from what I can see.
Build still running, could be a little while yet.
Edit: Failed - libperipheral_client.so: File format not recognized in the Sony vendor files - hmm.
XeKToReX said:
The older builds still used the old API level and didn't include all of the features from what I can see.
Build still running, could be a little while yet.
Edit: Failed - libperipheral_client.so: File format not recognized in the Sony vendor files - hmm.
Click to expand...
Click to collapse
I got the same error while building for Z1 compact. do you know how to fix it? or is this a problem with the sony binaries?
XeKToReX said:
Gonna do a build now, who's keen to flash? I doubt many things will work, mainly RIL (Phone/SMS) and Camera that I'm 99% sure wont..
Just got my phone back from Warranty so not going to unlock just yet in case it has it's own issues right away.
Click to expand...
Click to collapse
I can gladly help you by flashing it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
coolkil said:
I got the same error while building for Z1 compact. do you know how to fix it? or is this a problem with the sony binaries?
Click to expand...
Click to collapse
Based on the image above, looks like there is some corruption in the binaries, might message jerplea later on and see if there is a fix around.
XeKToReX said:
Based on the image above, looks like there is some corruption in the binaries, might message jerplea later on and see if there is a fix around.
Click to expand...
Click to collapse
No, and no recovery for lollipop as of yet.
i've flashed the Lolipop AOSP from FXP few days ago, had a recovery included.

/e/ project - Google free open source android available for OPO

https://gitlab.e.foundation/e/wiki/en/wikis/device/bacon/info
Looks interesting - meant to send absolutely no information to Google. Anyone tried it?
REALLY interesting. I'm going to try.
patp said:
https://gitlab.e.foundation/e/wiki/en/wikis/device/bacon/info
Looks interesting - meant to send absolutely no information to Google. Anyone tried it?
Click to expand...
Click to collapse
I was looking for this kind of ROM long time. Going to try now. :fingers-crossed:
forked from Nougat LineageOS but opensource except map application.
it's in beta stage.
So far so good...only complaint so far is the click/noise that the lens does when exiting the default camera app (open camera)...i will try it for a few days but will return to my normal rom as that "clicking noise" is really annoying (to me).
what mean/is /e/ project?!
Now the only thing OPO would need is completely FOSS rom. That would be really cool. No proprietary bits. Something like Replicant.
Is it nougat rom?
pankspoo said:
Is it nougat rom?
Click to expand...
Click to collapse
7.1.2
Can anyone provide me some screen shots and help me out about battery backup of this rom????
Read the FAQ page, it is written by Gael Duval. The name sounds familiar.. Yeah he is Mandrake Linux creator.. That brings back memories.
Is this better than the LineageOS microG ROM? I'm keen to try going Googlefree, we have no idea what Play Services and Google Framework are sending to the mothership.
can any one upload some screenshots of this?
agstn.tanmay said:
can any one upload some screenshots of this?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as I know for the optimized ROM, size in less than 400MB.
size of this rom is greater than 600MB ?!
Fatsodonkey said:
7.1.2
Click to expand...
Click to collapse
Does it update to oreo or pie ?
No update after Nougat
Bunty1924 said:
Does it update to oreo or pie ?
Click to expand...
Click to collapse
Nope, the last version available is Nougat

Categories

Resources