Not very sure about the authenticity of the pic provided in this link, maybe someone could dig deep down and flush out the real news (maybe based on the kernel or baseband version) but here is the link:
MOTO G4+ SPOTTED RUNNING 8.0
It seems fake to me. Also, there is no mentioned source of that screenshot. Also, Moto probably wouldn't have released the February security patch if all the work is focused on Oreo, which shows the January patch in that screenshot.
A L S O, the screenshot doesn't include the build number. That would have helped to confirm that the screenshot is 100% fake. And I would consider it kinda stupid from Moto to release 8.0.0 when 8.1.0 has already been out for months.
corlatemanuel said:
It seems fake to me. Also, there is no mentioned source of that screenshot. Also, Moto probably wouldn't have released the February security patch if all the work is focused on Oreo, which shows the January patch in that screenshot.
A L S O, the screenshot doesn't include the build number. That would have helped to confirm that the screenshot is 100% fake. And I would consider it kinda stupid from Moto to release 8.0.0 when 8.1.0 has already been out for months.
Click to expand...
Click to collapse
That I agree with, that's why my post didn't say it's real, it happened before with the g5 Oreo, someone faked it using x4 Oreo's build number
In addition to the other comments made about this:
1)Zooming into the picture, seems the 'Moto G4 Plus' text is slightly darker than the other descriptors and the font for the baseband (beginning with MSM8952) appears to be a different font to the other descriptors.
For example, look at the capital C in the baseband (CUST) and the C in the kernel timestamp (CST) and they seem to be 2 different styles. Contrast that with an Oreo soak test screenshot from the Moto Z Play: https://forum.xda-developers.com/showpost.php?p=75395738&postcount=15 The capital Cs are more consistent in their styles.
Additionally, look at the M in 'Modelo' and the M in 'Moto G4 Plus' and the 'MSM8952'. The M in 'Modelo' has its 'tails' pointing straight down, whereas the M in 'Moto G4 Plus' is angled. Contrast that again with the Moto Z Play screenshots where the M is pointing straight down in the About Phone photos.
2)As mentioned above, seems odd they would have the Jan 2018 patch, and the Jan 2018 baseband, when the February 2018 patch has come out. Jan 2018 baseband ends in 62.01R, with the Feb 2018 baseband ending in 62.02R. In theory, this could be an early build of the Oreo beta, but Motorola in the past has appeared to focus development on soak tests and included the latest patches with them, rather than splitting development (I think with the G4 Play, Motorola continued to release security patches as they had major issues with the soak test).
3)The kernel version and build timestamps match that from the Moto Z Play Oreo soak test build. https://forum.xda-developers.com/showpost.php?p=75395738&postcount=15 As others have noted in this thread https://forum.xda-developers.com/moto-g4-plus/help/android-oreo-t3763868 our device is likely to be running kernel version 3.10 (now on extended support), which makes a kernel change to 3.18 unlikely. Especially as Google only mandated newer kernels for devices released with Oreo/built in 2017 - devices updated to Oreo, if I recall, could maintain their original kernels.
Yeah, at first glance may be convincing but now seems just to bring false hope and/or is clickbait for tech sites. Regardless, I await evidence or signs of a soak test for our devices.
EDIT: that's at least 2 articles from Techdroider I've seen where they've not verified their sources...
EDIT 2: I see that this has gotten some traction on the Techdroider website, and yes, my post has a lot of focus on the screenshot. However, that's the only screenshot of an 'Oreo build' for G4 Plus devices I've seen, and without word of a soak test, so the timing of this seems a little suspect. Couple that with previous fakes mentioned on the Moto G subreddit and thus it warranted closer inspection, if only to stop giving false hopes to users and try to keep the record straight. Else, users will keep asking on this forum and the other G5/G5S forums when Oreo is arriving. The simple answer is we don't know (yet).
As for those that are commenting about the kernel version requiring to be 3.18 or higher, Google's documentation says that if your device is being upgraded, you can stay on the base kernel if you so wish:
Kernel version
Kernel version requirements:
All SoCs productized in 2017 must launch with kernel 4.4 or newer.
All other SoCs launching new Android devices running Android 8.0 must use kernel 3.18 or newer.
Regardless of launch date, all SoCs with device launches on Android 8.0 remain subject to kernel changes required to enable Treble.
Older Android devices released prior to Android 8.0 but that will be upgraded to Android 8.0 can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
Reference: https://source.android.com/devices/architecture/kernel/modular-kernels
LOL, you're just thinking too much. When you try to prove something "Fake" and you observe each and every detail of a Screenshot.
This was also Fake right? http://bit.ly/2FWnp2z
The thing is the screenshot is too good to be true, that's the only reason you cannot accept it. Also what makes you think G4 Plus is going to stay with base version? They can update it to 3.18 if the want.
Your logic in faking a Screenshot is not sound.
Moderator edit: Please avoid quoting the entire PREVIOUS post, and your choice of words for another member has been amended.
harsinghal said:
LOL, you're just thinking too much. When you try to prove something "Fake" and you observe each and every detail of a Screenshot.
This was also Fake right? http://bit.ly/2FWnp2z
The thing is the screenshot is too good to be true, that's the only reason you cannot accept it. Also what makes you think G4 Plus is going to stay with base version? They can update it to 3.18 if the want.
Your logic in faking a Screenshot is not sound.
Click to expand...
Click to collapse
Did you get the Oreo update then? Otherwise his analysis is dope. Echo is one of the masters when it comes to fixing. Hus saying this means it's the truth.
Ayan Uchiha Choudhury said:
Did you get the Oreo update then? Otherwise his analysis is dope. Echo is one of the masters when it comes to fixing. Hus saying this means it's the truth.
Click to expand...
Click to collapse
Saying something fake on the basis of color and font of words and letters makes you think his analysis is dope. Well, great then
He might be great in fixing and development, but i think his points are no facts but too much thinking to prove the ss fake.
harsinghal said:
Saying something fake on the basis of color and font of words and letters makes you think his analysis is dope. Well, great then
He might be great in fixing and development, but i think his points are no facts but too much thinking to prove the ss fake.
Click to expand...
Click to collapse
I get the impression you see the screenshot as real, so I'd like to ask you for your view on why you see this as genuine, or at least not faked. I would be interested in evidence too, e.g. do you have the build on your device? Or at least what you see as 'stupid in faking a screenshot'?
As for the screenshot you linked, that Chinese Moto Z Play screenshot looks genuine to me.
Here I have done a closer look at the screenshot and a comparison between that screenshot and a screenshot from my build of Lineage 15.1 and found two more details:
1. If you pay close attention/have a well trained eye, you will notice that the spacing is wrong for the Baseband Version when compared to the other elements (Android version, Kernel version etc.). When compared, the spacing between the "Baseband version" and the actual baseband version looks rather like the one on my LOS 15.1 build than the one on the stock Moto ROM, with the two being closer together on LOS 15.1. Though you need to look really close to notice it.
2. When you look at it, there is a part of the baseband version that only the stock ROM (7.0) and the bootloader show. On that screenshot, that detail is next to the baseband version rather than underneath the part that would be found on custom ROMs. Look at the dotted lines.
I also think this is fake cuz of the simplest reason that a company would be actually cheating to the customers who bought the g5 family if we had a soak test before them since we are an older model. Even if the company had a soak test ready they would hold till ALL the g5 phones had a soak test out and then would release for g4 plus. I doubt Lenovo would want an uproar from the community.
harsinghal said:
LOL, you're just thinking too much. When you try to prove something "Fake" and you observe each and every detail of a Screenshot.
This was also Fake right? http://bit.ly/2FWnp2z
The thing is the screenshot is too good to be true, that's the only reason you cannot accept it. Also what makes you think G4 Plus is going to stay with base version? They can update it to 3.18 if the want.
Your logic in faking a Screenshot is pure stupid.
Click to expand...
Click to collapse
Have you ever seen a company which updated their kernel, except Google? No.
Motorola didn't even upstream the kernel. It's still .84 while there's .108
He proved that this screenshot is fake in a detailed way and you just disrespected him.
That screenshot is fake, believe or not.
LineageOS 15.1
corlatemanuel said:
Here I have done a closer look at the screenshot and a comparison between that screenshot and a screenshot from my build of Lineage 15.1 and found two more details:
1. If you pay close attention/have a well trained eye, you will notice that the spacing is wrong for the Baseband Version when compared to the other elements (Android version, Kernel version etc.). When compared, the spacing between the "Baseband version" and the actual baseband version looks rather like the one on my LOS 15.1 build than the one on the stock Moto ROM, with the two being closer together on LOS 15.1. Though you need to look really close to notice it.
2. When you look at it, there is a part of the baseband version that only the stock ROM (7.0) and the bootloader show. On that screenshot, that detail is next to the baseband version rather than underneath the part that would be found on custom ROMs. Look at the dotted lines.
Click to expand...
Click to collapse
Hi, I saw in your post that you have a catch of LineageOS 15.1 with a latest version of March.
Can you tell me or pass the link where you downloaded it?
Thank you very much
al3al3al3jandr0 said:
Hi, I saw in your post that you have a catch of LineageOS 15.1 with a latest version of March.
Can you tell me or pass the link where you downloaded it?
Thank you very much
Click to expand...
Click to collapse
About Lineage OS. Yes, it's a build of mine, I didn't make a thread about it because I'm an absolute noob when it comes to ROM building and this is my first ever ROM built. I can upload it somewhere, if you want me to.
corlatemanuel said:
About Lineage OS. Yes, it's a build of mine, I didn't make a thread about it because I'm an absolute noob when it comes to ROM building and this is my first ever ROM built. I can upload it somewhere, if you want me to.
Click to expand...
Click to collapse
Of course it would be fine, congratulations for doing it.
What bugs do you have?
corlatemanuel said:
About Lineage OS. Yes, it's a build of mine, I didn't make a thread about it because I'm an absolute noob when it comes to ROM building and this is my first ever ROM built. I can upload it somewhere, if you want me to.
Click to expand...
Click to collapse
Post edited - XDA is for public sharing, not code via PM...
LenAsh said:
Post edited - XDA is for public sharing, not code via PM...
Click to expand...
Click to collapse
It has been shared meanwhile:
https://forum.xda-developers.com/moto-g4-plus/development/lineageos-15-1-nightlies-thanks-to-nikit-t3765065
(actually, that's a different one )
jer194 said:
It has been shared meanwhile:
https://forum.xda-developers.com/mo...ageos-15-1-nightlies-thanks-to-nikit-t3765065
(actually, that's a different one )
Click to expand...
Click to collapse
Actually, It's pretty much the same thing, only that mine has very minor changes. Maybe I'll make a thread of my own if I manage to sort everything out for my builds. I didn't make a thread yet as I didn't feel like it was ready for use yet
I just a saw youtube video,in that video he told that moto is testing oreo on the g4 plus
jaxx08 said:
I just a saw youtube video,in that video he told that moto is testing oreo on the g4 plus
Click to expand...
Click to collapse
i know seen that too. sad it is. probably his own ignorance to deceitful nature
here's latest news
https://www.xda-developers.com/motorola-testers-moto-g4-plus-android-oreo/
Related
Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Source: http://www.androidpit.com.br/teste-nougat-moto-x-force-e-style-comecarao-em-breve
Update 1: Motorola send out soak test invitations to US users
Update 2: Android Headlines reports Moto X Style Is Receiving Android 7.0 Nougat In India
Update 3: Moto X Style and X Pure Nougat update spotted on GFXBench (Yes, again. The last time it was spotted on 7.1 was in last week of December.)
Update 4: A user on reddit who is located near Chicago states he received the Nougat update.
Soak test is going on in India also.
This is a good news !!!!!!
soak test is only available for limited users and if anyone who will break their rules will be out of the soak test permanently so don't expect that someone might just end up sharing the files !! all we need to do is just wait for that moment when it gets as stable as a daily driver and we all are good to go
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2
Why not get it now?
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.
I got bored waiting for official nougat and went to AICP 7.1
It's pretty good, can't see myself going back to stock tbh
Put me down for Dirty Unicorns. Last things for me were camera functioning well (which it seems to be if using OpenCamera) and torch working well (which it seems to be improved).
Sagar_1401 said:
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2
Click to expand...
Click to collapse
no chance for that
iks8 said:
no chance for that
Click to expand...
Click to collapse
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS
josdehaes said:
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS
Click to expand...
Click to collapse
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd
iks8 said:
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd
Click to expand...
Click to collapse
I'm with you here. I have no desire leave the stock ROM for any reason other than updates. It's been bug-free and smooth sailing for me with Motorola's software ever since 2015, no doubt because they stick to AOSP.
The only way I'd be interested in a custom ROM is if the developers were on a very long release cycle where they spent months ironing out every tiny bug before tinkering with new things, similar to how OEMs approach stock ROMs. That seems rare these days, though I don't follow things too closely anymore. "Man this ROM is amazing... except, oh yeah, Bluetooth breaks and requires a reboot... oh, and calls drop a lot... and, uh, call volume randomly goes to max/silent for no reason... oh yeah, and MMS just doesn't show up sometimes, and the camera crashes every 3rd open requiring another reboot" seems to be the way of the world, and I don't have patience for it. Putting up with random bugs can be worth it if it frees you from TouchWiz or Sense or LG UI, but when the stock ROM is already AOSP and fast/fluid, I don't see the point.
http://www.androidauthority.com/moto-x-style-pure-edition-nougat-758023/
I have to agree that stock rooted ROMs are my way of going now. Of course that also means I won't buy from makes like Samsung who overburden their ROMs with too much frill. Besides, with manufactures like one plus, the is really no reason to revert.
good news
ptn107 said:
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.
Click to expand...
Click to collapse
I'm on RW too. Are you using a certain version that's working good? I just don't wanna messed up my service, but would love to try 7.1.1.
Sent from my SM-P600 using XDA-Developers Legacy app
Official Android 7.0 Nougat out for Moto X Style (Pure) in India and Brazil
AsquareX said:
Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse
About time. I see that the Android O developer preview is out and we don't even have 7.0 yet. Grrr!
strafer69 said:
About time.
Click to expand...
Click to collapse
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto
iks8 said:
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto
Click to expand...
Click to collapse
Not Moto's fault. Blame it all on Lenovo, as the Moto's work force is pretty much non-existent.
Rmsalt said:
AsquareX said:
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse
Honestly, a while... It usually goes Brazil, India, Europe, then US and UK (sometimes US/UK flip-flop). To be honest, Lenovo doesn't see the US as a major market, these phones are not carrier subsidized so their market penetration is minimal at best. US is always the last to get Moto (Lenovo) updates in the last 12-18 months. Not likely to see that change anytime soon. Each region will have it's own beta if history repeats, we are at minimum 2-3 months out in the US.
Click to expand...
Click to collapse
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
revdirty said:
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
Click to expand...
Click to collapse
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Just from my point of view, finding the various aspects for my themes was a pain in the butt from N to O. Somethings that were once png are now vector images and that is just from a themers aspect,,,rom building is a whole other thing. I am sure there will be some soon.
I was thinking the exact same thing as OP. I hope this isn't the case for the Pixel 2 XL. My Nexus 6 is running a custom Oreo ROM and it's great so far. It's like a ghost town.
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Oreo appears buggy...
I will wait for Pure Nexus Oreo
udahy.manna said:
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Click to expand...
Click to collapse
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
cntryby429 said:
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Click to expand...
Click to collapse
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Why is custom ROM development on Pixel is very low?
hp13 said:
Why is custom ROM development on Pixel is very low?
Click to expand...
Click to collapse
Because it's an expensive device and it has this new crappy A/B partitions system
lorax70 said:
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
Click to expand...
Click to collapse
The new official flashable TWRP is out and compatible with pixel Oreo.
yeah, I would give "O" a little time. It appears that some are starting to have a few issues with phones being bricked. It's possible that one of the 3 is not related, but certainly my advice would be to wait folks. This could be related directly to branded phones, but not exactly sure and would only be speculation at this point. It's possible the DEV's are waiting on a few areas...
https://forum.xda-developers.com/pixel/help/pixel-bricked-overnight-t3681377
https://forum.xda-developers.com/pixel/help/google-pixel-bricked-oreo-twice-ideas-t3671302
dantexaiver said:
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Click to expand...
Click to collapse
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Golf c said:
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Click to expand...
Click to collapse
Flash back to a nougat custom rom. Problem solved.
mitchdickson said:
Flash back to a nougat custom rom. Problem solved.
Click to expand...
Click to collapse
Haha, not quite.
Recently got a pixel after years of sony phones and am awaiting some Oreo custom roms. It's great I'm getting the latest OS updates straight away but the downside I guess is the newness means custom roms take longer. Now there's a working TWRP I'm hopeful we'll start to see custom Oreo roms appearing.
zelendel said:
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
Click to expand...
Click to collapse
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
nine7nine said:
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
Click to expand...
Click to collapse
It is the standard for Google device. Notice how only Google devices use it?
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
A/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
zelendel said:
It is the standard for Google device. Notice how only Google devices use it?
Click to expand...
Click to collapse
Motorola has been testing it, including a device that utilizes it now. Same goes with Xaoimi... Furthermore, a/b partition is a part of AOSP... Oreo devices going forward will be making use of Project Treble and I suspect in the next year, you are going to see more vendors adopting the new partition scheme.
On top of that, all new mediatek and Qualcomm SOCs will support A/b partition schemes.
https://www.xda-developers.com/xiaomi-mi-a1-android-ab-partition/
https://www.xda-developers.com/moto-z2-force-ab-seamless-updates/
https://review.lineageos.org/#/c/156378/
https://source.android.com/devices/tech/ota/ab_updates
zelendel said:
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
Click to expand...
Click to collapse
Um, no. it's perfectly reasonable for an end use running a custom ROM to want/expect OTA upgrades that uses seamless updating, where supported.... I've been involved in ROM development, in the past. thanks.... for someone developing a ROM; ya, you will be flashing your custom builds, but for an end user not building from AOSP, lineageOS repositories; OTA is far bore reasonable...
zelendel said:
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
Click to expand...
Click to collapse
lol. that comment makes zero sense, given the context... It's always been the case (for stock vs. custom roms) that you will be getting updates from one or the other, not both...
zelendel said:
IA/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
Click to expand...
Click to collapse
We will see, but given that Qualcomm and mediatek will be supporting it going forward and the revelations and direction of Project treble && VTS; I suspect that a/b partitions will become the norm...
the only question is what will Samsung do for future devices, since they unlike most vendors produce their own SOCs/Exynos boards.... I guess we will see when the next galaxy line is released.
I know about the Google site to download factory imsges but I'm wondering if anyone on here ever posted a list of each release in order? Including which carriers each build was for. Thanks!
aholeinthewor1d said:
I know about the Google site to download factory imsges but I'm wondering if anyone on here ever posted a list of each release in order? Including which carriers each build was for. Thanks!
Click to expand...
Click to collapse
erm, Google does that already....
each release has a versioning, date, carrier and hashes to go with them....
there are maybe a handful of releases that don't have a carrier directly listed... So I don't understand why anyone would compile a list....? what purpose would it serve?
ref: https://developers.google.com/android/images
nine7nine said:
erm, Google does that already....
each release has a versioning, date, carrier and hashes to go with them....
there are maybe a handful of releases that don't have a carrier directly listed... So I don't understand why anyone would compile a list....? what purpose would it serve?
ref: https://developers.google.com/android/images
Click to expand...
Click to collapse
Yea i guess I was more worried about the different builds for carries. Sometimes it would be the same and other times there would be different ones for some carries and stuff like that. Thought I saw a post like that somewhere
aholeinthewor1d said:
Yea i guess I was more worried about the different builds for carries. Sometimes it would be the same and other times there would be different ones for some carries and stuff like that. Thought I saw a post like that somewhere
Click to expand...
Click to collapse
I think I know what ur talking about; earlier on with 7.x.x releases there was a few unclear builds, then later the switched how a couple of carriers were grouped... but at the end of the day; old releases don't matter and current ones do... people shouldn't be running older images...
the current ones are labelled clearly and all one has to do is download the correct image for their carrier...
that's my 2 cents ?
nine7nine said:
I think I know what ur talking about; earlier on with 7.x.x releases there was a few unclear builds, then later the switched how a couple of carriers were grouped... but at the end of the day; old releases don't matter and current ones do... people shouldn't be running older images...
the current ones are labelled clearly and all one has to do is download the correct image for their carrier...
that's my 2 cents ?
Click to expand...
Click to collapse
I'm going to be going back to an old version for a little. Not sure which one yet. I wanna test some things with my battery that's all. Plus I need to get off the beta anyways
aholeinthewor1d said:
I'm going to be going back to an old version for a little. Not sure which one yet. I wanna test some things with my battery that's all. Plus I need to get off the beta anyways
Click to expand...
Click to collapse
I see. just keep in mind, older build will contain well-known security issues, exploits and bugs...
out of curiousity; are u having battery issues or something?
ya, I tried the beta / dp2 - went back to the 8.0 Nov build... plus, I couldn't run my kernel on the Dev previews, well not without effort.
I think LineageOS official is near.... I've found interesting information about polaris
https://review.lineageos.org/#/q/topic:polaris-bringup+(status:open+OR+status:merged)
can't wait
Still early stages, not even buildable yet
Going to bring an old thread back to life. Especially with Lineage 16.0 on its way out, do we have anyone attempting to build for this phone?
I'm not sure I've ever owned a phone with this little developer support.
15.1 device tree wont be finished , we have jumped straight to 16.0.
YazumiWuHung said:
15.1 device tree wont be finished , we have jumped straight to 16.0.
Click to expand...
Click to collapse
Oh! Thanks, didn't realize we had dev's looking into it. Thanks for your work.
gogogo....would not have thought that the difference to "mi mix 2" is so big
tom65824 said:
gogogo....would not have thought that the difference to "mi mix 2" is so big
Click to expand...
Click to collapse
Official support for Lineage hasn't been updated since July. I wouldn't hold your breath.
Yeah last update was August on 16.0
https://review.lineageos.org/#/q/project:LineageOS/android_device_xiaomi_polaris
andyphone said:
Yeah last update was August on 16.0
https://review.lineageos.org/#/q/project:LineageOS/android_device_xiaomi_polaris
Click to expand...
Click to collapse
As far as I can tell the 2 polaris repos were deleted off of their GitHub today
aeppacher said:
As far as I can tell the 2 polaris repos were deleted off of their GitHub today
Click to expand...
Click to collapse
This one still exists....
https://github.com/LineageOS/android_device_xiaomi_polaris
and here ?
https://www.getdroidtips.com/lineage-os-15-1-xiaomi-mi-mix-2s/
official?
tom65824 said:
and here ?
https://www.getdroidtips.com/lineage-os-15-1-xiaomi-mi-mix-2s/
official?
Click to expand...
Click to collapse
No, its not official. Its a treble system image. You can probably download a more updated version at the Treble-enabled device development forum.
This thread seems to be a collection of random guesses. Is there any actual source of information on the status of an official build for the Mix 2s? Surely if someone were working on it, they would post something somewhere... Not trying at all to be demanding or complain, but I would like to know if there is a reasonable chance of a release at some point.
I have until Oct. 15 to return this device. It's an outstanding phone with a PoS operating system. Without going into a big rant about miui 10, I don't want to own a phone where text messages are unreliable using anything but xiaomi's crappy (and likely invasive) messaging app.
Xar99 said:
This thread seems to be a collection of random guesses. Is there any actual source of information on the status of an official build for the Mix 2s? Surely if someone were working on it, they would post something somewhere... Not trying at all to be demanding or complain, but I would like to know if there is a reasonable chance of a release at some point.
I have until Oct. 15 to return this device. It's an outstanding phone with a PoS operating system. Without going into a big rant about miui 10, I don't want to own a phone where text messages are unreliable using anything but xiaomi's crappy (and likely invasive) messaging app.
Click to expand...
Click to collapse
I broke my cardinal rule with this handset: never buy hardware based upon the promise of future software updates because they may not ever happen.
I think if it was being worked on we would have heard by now. Devs just seem disinterested in the device.
andyphone said:
This one still exists....
Click to expand...
Click to collapse
The one andyphone linked above has quite a few commits since Oct. 1 (today, even). Good sign?
Los 16.0 should come eventually. Seems like a very capable developer is working on our device right now!
There may not be any official announcement yet, but you can easily see that work to bring up LineageOS for the Mix 2S is still underway here: https://github.com/LineageOS/android_device_xiaomi_polaris.
The last commit to this Mix 2S-specific repository was a day ago.
Starting off at version 9, the official P3 Rom thread now lists version 12...
I was under the impression that such devices usually received a max of 3 Android releases. So for P3, that would be 9, 10 and 11
I had also read elsewhere that version 11 will be the final release that Google will issue for the P3
12.0.0 (SP1A.210812.015, Oct 2021)FlashLinkc5f3469cfd9ac914377eac1d05eb60bde3b88d109c9e618eecf82a938bad562512.0.0 (SP1A.210812.016.A1, Oct 2021, Verizon)FlashLink514272b9973ab900dd92ab7652291498e868d9778be77979291e9ed60c287838
Now I see this
I am not interested in the Verizon release. But there is still SP1A.210812.015 which seems to be unbranded one
Is there any reason behind Google's intention to further support the P3 into yet another Android release?
jstoner said:
Starting off at version 9, the official P3 Rom thread now lists version 12...
I was under the impression that such devices usually received a max of 3 Android releases. So for P3, that would be 9, 10 and 11
I had also read elsewhere that version 11 will be the final release that Google will issue for the P3
12.0.0 (SP1A.210812.015, Oct 2021)FlashLinkc5f3469cfd9ac914377eac1d05eb60bde3b88d109c9e618eecf82a938bad562512.0.0 (SP1A.210812.016.A1, Oct 2021, Verizon)FlashLink514272b9973ab900dd92ab7652291498e868d9778be77979291e9ed60c287838
Now I see this
I am not interested in the Verizon release. But there is still SP1A.210812.015 which seems to be unbranded one
Is there any reason behind Google's intention to further support the P3 into yet another Android release?
Click to expand...
Click to collapse
It's more of a time thing. Google typically supports devices for 3 years from their release date. The Pixel 3 was released in October 2018, so its last update is Oct 2021.
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
But, the Pixel 3 / 3XL have been sunsetted as of that 3 year mark, so they will no longer receive any updates.
The 3a/3aXL will be supported to May of this year; the 4/4XL will be supported to October; and so on.
My Pixel 5 will no longer be supported beyond October 2023.
V0latyle said:
It's more of a time thing. Google typically supports devices for 3 years from their release date. The Pixel 3 was released in October 2018, so its last update is Oct 2021.
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
But, the Pixel 3 / 3XL have been sunsetted as of that 3 year mark, so they will no longer receive any updates.
The 3a/3aXL will be supported to May of this year; the 4/4XL will be supported to October; and so on.
My Pixel 5 will no longer be supported beyond October 2023.
Click to expand...
Click to collapse
So those two builds of Android 12 I mentioned above (SP1A.210812.015 and SP1A.210812.016.A1) are in fact the first and last ones for P3..?
Ackward approach to have this version 12 and leave it premature. I m sure there will be some sort of issues with it
jstoner said:
So those two builds of Android 12 I mentioned above (SP1A.210812.015 and SP1A.210812.016.A1) are in fact the first and last ones for P3..?
Ackward approach to have this version 12 and leave it premature. I m sure there will be some sort of issues with it
Click to expand...
Click to collapse
Yes, the initial release of Android 12 on the Pixel 3 /3XL is also the last update the device will ever receive. That being said, the initial 12 release is quite stable, the only bugs I found were nothing that impaired usability.
I suspect the reason why the P3 / XL got Android 12 for its final release is because of the GSI architecture on Pixel devices. Google doesn't develop multiple ROMs for multiple devices - the only thing really different are the bootloaders, baseband, drivers, and maybe kernel. Android 12 on the Pixel 6 looks and performs exactly like Android 12 on the Pixel 3. So, all Pixels get updated at the same time; the fact that the initial release of Android 12 was the final update on the P3 is more of a coincidence, really.
V0latyle said:
Yes, the initial release of Android 12 on the Pixel 3 /3XL is also the last update the device will ever receive. That being said, the initial 12 release is quite stable, the only bugs I found were nothing that impaired usability.
I suspect the reason why the P3 / XL got Android 12 for its final release is because of the GSI architecture on Pixel devices. Google doesn't develop multiple ROMs for multiple devices - the only thing really different are the bootloaders, baseband, drivers, and maybe kernel. Android 12 on the Pixel 6 looks and performs exactly like Android 12 on the Pixel 3. So, all Pixels get updated at the same time; the fact that the initial release of Android 12 was the final update on the P3 is more of a coincidence, really.
Click to expand...
Click to collapse
Excellent, thank you for the input
Way I see it, from security perspective, there isn't much of a benefit moving from latest v11 to v12 final (if its not to receive any further updates)
Perhaps someone may be tempted for a specific new feature on v12 (?), but so I far, I don't see a need for it
jstoner said:
Excellent, thank you for the input
Way I see it, from security perspective, there isn't much of a benefit moving from latest v11 to v12 final (if its not to receive any further updates)
Perhaps someone may be tempted for a specific new feature on v12 (?), but so I far, I don't see a need for it
Click to expand...
Click to collapse
To each their own. I disagree on the security perspective; Android 12 introduced a lot of privacy and security features that are a major improvement over Android 11. Even if there are no further updates, that alone would be of some benefit.
Of course, for those still using the P3, there may soon come a time when custom ROMs are safer as they often incorporate the latest kernel fixes and security updates from AOSP.
V0latyle said:
To each their own. I disagree on the security perspective; Android 12 introduced a lot of privacy and security features that are a major improvement over Android 11. Even if there are no further updates, that alone would be of some benefit.
Of course, for those still using the P3, there may soon come a time when custom ROMs are safer as they often incorporate the latest kernel fixes and security updates from AOSP.
Click to expand...
Click to collapse
Hello there new to the forum, pretty much a newb when it comes to tech talk, really..
But I am a Google Pixel 3 user, just found the news that it will no longer be supported. Asked some friends and they mentioned custom ROMs as a way around this... My old school nature finds all of this ridiculous, but it is what it is, I guess xD
In response to this, my question is when would a user like me consider switching to a custom ROM? "there may soon come a time..." ... what time might that be? When I start to see functions failing? When Android 12 updates globally but not for me?
Additionally, what would be the best resource to finding which custom ROM would fit my needs best?
Currently, my phone works great still. Hopefully I can exist for quite a while and not even think about it... but it works so good that I'd hate to go and buy a Pixel 6 when its security issues that render my device obsolete. If it means a custom ROM before $600, I'll probably take the shot.
Thanks!
neat_moss said:
Hello there new to the forum, pretty much a newb when it comes to tech talk, really..
But I am a Google Pixel 3 user, just found the news that it will no longer be supported. Asked some friends and they mentioned custom ROMs as a way around this... My old school nature finds all of this ridiculous, but it is what it is, I guess xD
In response to this, my question is when would a user like me consider switching to a custom ROM? "there may soon come a time..." ... what time might that be? When I start to see functions failing? When Android 12 updates globally but not for me?
Additionally, what would be the best resource to finding which custom ROM would fit my needs best?
Currently, my phone works great still. Hopefully I can exist for quite a while and not even think about it... but it works so good that I'd hate to go and buy a Pixel 6 when its security issues that render my device obsolete. If it means a custom ROM before $600, I'll probably take the shot.
Thanks!
Click to expand...
Click to collapse
When to switch depends entirely on your attitude towards monthly security updates. That would also effect what ROM you consider. Personally I switched about 4 months ago. I chose LineageOS because it reliably receives monthly security updates.
Do you have an unlockable bootloader? If not, all your questions are moot, because you must be able to unlock the bootloader to install a custom ROM.
dcarvil said:
When to switch depends entirely on your attitude towards monthly security updates. That would also effect what ROM you consider. Personally I switched about 4 months ago. I chose LineageOS because it reliably receives monthly security updates.
Do you have an unlockable bootloader? If not, all your questions are moot, because you must be able to unlock the bootloader to install a custom ROM.
Click to expand...
Click to collapse
LineageOS was the one recommended to me as well, sounds like a good bet.
"unlockable bootloader" is totally Greek to me though xD. Really have no idea what that means lmao. How might I find out if I have an unlockable bootloader? And if I do... how does one... unlock it? xD
And thanks for the insight!
neat_moss said:
LineageOS was the one recommended to me as well, sounds like a good bet.
"unlockable bootloader" is totally Greek to me though xD. Really have no idea what that means lmao. How might I find out if I have an unlockable bootloader? And if I do... how does one... unlock it? xD
And thanks for the insight!
Click to expand...
Click to collapse
See the "Unlocking the Bootloader" section in this thread. https://forum.xda-developers.com/t/guide-how-to-root-pixel-3-android-12.4366041/#post-86294311
Also, the LineageOS installation instructions have an "Unlocking the bootloader" section. https://wiki.lineageos.org/devices/blueline/install
If you have a Verizon or AT&T variant, you cannot unlock the bootloader.
dcarvil said:
See the "Unlocking the Bootloader" section in this thread. https://forum.xda-developers.com/t/guide-how-to-root-pixel-3-android-12.4366041/#post-86294311
Also, the LineageOS installation instructions have an "Unlocking the bootloader" section. https://wiki.lineageos.org/devices/blueline/install
If you have a Verizon or AT&T variant, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Very cool, thanks! A lot of this documentation makes sense.
Verizon or AT&T variant though... you mean the phone itself? In my case, i bought the phone directly from google and just put an AT&T SIM card into it... is that the same thing?
Thanks!
neat_moss said:
Very cool, thanks! A lot of this documentation makes sense.
Verizon or AT&T variant though... you mean the phone itself? In my case, i bought the phone directly from google and just put an AT&T SIM card into it... is that the same thing?
Thanks!
Click to expand...
Click to collapse
The AT&T variant would be a phone purchased from AT&T. If you purchased it from Google, you probably have the unlockable version. If you can enable the OEM Unlocking toggle, you can unlock the bootloader. Unlocking will wipe your phone, though, so be sure to backup everything you need.
dcarvil said:
The AT&T variant would be a phone purchased from AT&T. If you purchased it from Google, you probably have the unlockable version. If you can enable the OEM Unlocking toggle, you can unlock the bootloader. Unlocking will wipe your phone, though, so be sure to backup everything you need.
Click to expand...
Click to collapse
Thank you much! I'll likely be trying this soon enough
V0latyle said:
Additionally, Google avoids the fragmentation we see among other manufacturers - they use that month's AOSP for the core of the update. It so happens that October 2021 was the official release of Android 12.
Click to expand...
Click to collapse
It seems that more v12 releases are coming out. So the initial assumption that the P3 will receive updated v12 builds up till OCT21, doesn't seem to be the case anymore
(although I am not complaining!)
In addition to the OCT21 rels:
SP1A.210812.015
SP1A.210812.016.A1
I can now see JAN22 / FEB22 rels:
SP1A.210812.016.A2
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
After reading some positive feedback on v12, I think I will be updating to that latest version
But I want an 'unbranded' ROM. So it would make sense to go for "SP1A.210812.016.C1", right?
I really hope that if this is one of the last v12 releases for P3, it is at least as stable as my latest v11 build. It would be nice to have those extra privacy features, but stability on that phone is no1 prio...
jstoner said:
It seems that more v12 releases are coming out. So the initial assumption that the P3 will receive updated v12 builds up till OCT21, doesn't seem to be the case anymore
(although I am not complaining!)
Click to expand...
Click to collapse
As I stated previously, Google only committed to 3 years of software updates on most of the Pixel line. The October '21 update was the end of the update agreement for the 3 / 3XL. Interesting that there are January and February releases too.
The 3a and 3aXL will be sunsetted in May of this year.
My Pixel 5 will receive its last update on Oct '23, and my wife's 5a will be supported up to Aug '24.
Software updates on Pixel devices
That being said, Pixel devices use AOSP, so it wouldn't be hard for someone to build updated firmware for the Pixels using the latest AOSP release. Google even makes the driver binaries available. The only caveat to this is that TWRP often doesn't keep up with the newer devices, so the update would have to be in the same format as either an OTA file, or factory image.
V0latyle said:
The October '21 update was the end of the update agreement for the 3 / 3XL. Interesting that there are January and February releases too.
Click to expand...
Click to collapse
Then maybe there was something important on the OCT21 release that needed to be fixed? No idea. I wonder if that FEB22 release is going to be the final one (in which case I d rather wait a bit longer)
Just curious about those:
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
Aren't all those releases supposed to be 'brand-less' (i.e. not associated with any provider)? So what's with that Telstra/Optus/Vodafone AU sidenote on that release?
Am I right in thinking that at the moment, "SP1A.210812.016.C1" is the one to go for? I m only interested in having a retail ROM - just as if I bought the device directly from Google..
jstoner said:
Then maybe there was something important on the OCT21 release that needed to be fixed? No idea. I wonder if that FEB22 release is going to be the final one (in which case I d rather wait a bit longer)
Click to expand...
Click to collapse
Even if there were bugs in the October release, I'm surprised they bothered with January and February too. October '21 is the last one they committed to, any more will be out of the ordinary for them.
jstoner said:
Just curious about those:
SP1A.210812.016.B1 (Telstra, Optus, Vodafone AU)
SP1A.210812.016.C1
Aren't all those releases supposed to be 'brand-less' (i.e. not associated with any provider)? So what's with that Telstra/Optus/Vodafone AU sidenote on that release?
Click to expand...
Click to collapse
Baseband fixes, most likely. Bootloader, kernel and system are the same; usually the only difference is the baseband.
jstoner said:
Am I right in thinking that at the moment, "SP1A.210812.016.C1" is the one to go for? I m only interested in having a retail ROM - just as if I bought the device directly from Google..
Click to expand...
Click to collapse
Probably.
V0latyle said:
Even if there were bugs in the October release, I'm surprised they bothered with January and February too. October '21 is the last one they committed to, any more will be out of the ordinary for them.
Baseband fixes, most likely. Bootloader, kernel and system are the same; usually the only difference is the baseband.
Probably.
Click to expand...
Click to collapse
Sorry to bother again - but do you by any chance know where I can find Rel notes for those releases
I would like to see what the changes are e.g. from SP1A.210812.016.A2 to SP1A.210812.016.C1
Are those not supposed to be releases to public? (only for Devs?)
jstoner said:
Sorry to bother again - but do you by any chance know where I can find Rel notes for those releases
I would like to see what the changes are e.g. from SP1A.210812.016.A2 to SP1A.210812.016.C1
Click to expand...
Click to collapse
Pixel Update Bulletins | Android Open Source Project
source.android.com
These are general topics across the board and not device specific so I have no idea what is different in the P3 updates. This article provides more information, looks like it's mainly a security update and bug fixes.
jstoner said:
Are those not supposed to be releases to public? (only for Devs?)
Click to expand...
Click to collapse
No, they're intentional, the February update apparently includes fixes that were supposed to be rolled out in your last "official" update in November '21
V0latyle said:
Pixel Update Bulletins | Android Open Source Project
source.android.com
No, they're intentional, the February update apparently includes fixes that were supposed to be rolled out in your last "official" update in November '21
Click to expand...
Click to collapse
According to that source, that FEB22 update, is almost certainly the last for P3 + P3 XL
And as it turns out, my initial assumption about a major bug fix was actually true - it was the 911 calling issue (which due to life critical scenarios) was handled with priority
So it would seem that SP1A.210812.016.C1 is the one to go for P3. No need to wait further, as there won't be any more rels. From what I also read on Reddit, v12, despite only being introduced for P3, is decent enough. No major bugs so far. So I guess it is stable
For this device that I need it for, stabi is more important than security. Don't know if that changes anything or whether I should not move to v12..