[Q] Do we get Android L preview updates? - Nexus 5 Q&A, Help & Troubleshooting

Hey guys,
It's already a long time since the release of Android L preview and I was wondering if we were ever going to get an update to it. Can't believe this version is going to last until the public release.

Doubtfully, as it's just a preview of what's to come. The update will be the official release, followed by normal updates via OTA's.
Who knows, I guess Google could update the preview, but I seriously doubt it... Besides they never did a preview like this before. Usually we just wait until the new OS comes out. Believe it lol.

RoyJ said:
Doubtfully, as it's just a preview of what's to come. The update will be the official release, followed by normal updates via OTA's.
Who knows, I guess Google could update the preview, but I seriously doubt it...
Click to expand...
Click to collapse
Hmm, let's hope for it. There are some annoying bugs in Android L, but the advantages of Android L over 4.4.4 overrule the bugs, so I'm not downgrading, though.

Just curious, what advantages? I tried it, but ended up back on KK. I never run a stock nexus device, so I probably won't even run L at all until ROM devs get their hands on it after official release.

RoyJ said:
Just curious, what advantages? I tried it, but ended up back on KK. I never run a stock nexus device, so I probably won't even run L at all until ROM devs get their hands on it after official release.
Click to expand...
Click to collapse
Mainly the ones Google is bragging about; I really notice energy is maintained more efficiently, battery lasts longer than stock. Probably compared to a rooted device, it doesn't. The notifications and notification center toggle are great(!); love I don't need a separate ugly app for that. The new design is somehow fun; I'm a designer. Although it's better than KK, I'm not that fond of it, compared to some custom designs or even iOS, which both I like more. And the do-not-disturb functionality sometimes come in handy.
Just the way to handle it, it's got better.

Some google developer said that there wont be any updates to android L preview. And if you ask me, its not needed. This is only for devs to test and update their apps to android L guidelines so when google releases L officialy, more apps will take advantage of new design and animations.
Sent from Pure Nexus 5

There is already a sticky thread devoted to Android L discussion: Android "L" Developer Preview Help, Troubleshooting, Q&A, please continue there are don't open threads related to Android L discussion :good:

Related

[Q] android 5.0 lollipop on RAZR devices??

Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
We're not going to get official support for 5.0 if that's what you mean. As for custom ROMs, I'm sure it will happen eventually.
Once Android 5.0 L is officially released, we intend to bring this latest upgrade to many of our other Motorola devices, as well. This includes Moto X (1st and 2nd Gen), Moto G (1st and 2nd Gen), Moto G with 4G LTE, Moto E, Droid Ultra, Droid Maxx and Droid Mini. We're still working out the details on timing and the upgrade depends on our partners' support so stay tuned to our software upgrades page for the latest and greatest.
Click to expand...
Click to collapse
http://www.motorola-blog.blogspot.hu/2014/10/nexus-6-from-google-and-motorola-more.html
...and it begins...Took less than a day for someone to ask. It's not even released yet. Coming to the Razrs? Not a snowball's chance in hell. Unofficial, maybe? These things are at EOL and they received a barely functioning official KK update.
Sent from my HTC6525LVW using Tapatalk
Moto kind of hinted at the possibility of having other devices on Lollipop, but I'm not holding my breath this time.
derpyherp said:
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
Click to expand...
Click to collapse
We're not even going to get KK 4.4.4 officially. The only way we have that is via custom ROMs like CM11.
Those of us in the soak test were told that this latest OTA (.15 release) was the FINAL release for this phone. No more updates. That came straight from a Motorola person in the private soak test forums.
So, don't hold your breath for an "official" Lollipop release. As others have stated, you might see it via Cyanogen or some other custom ROMs, but that will only be for those who have unlocked bootloaders. Those who have already upgraded to the latest OTA without unlocking are screwed forever.
Besides, CM11 for this phone has just recently become completely stable. L isn't even out yet.
here's is how its going to go down.
L comes out nov 3.
cyanoagen inc /PA will merge the code to their repos; take about a month before the first nightly comes out. cm11 is EOL as they move to Lollipop.
gummy slim and others will take the cm base and fork to get their ROMs running too.
then dhacker epinter etc. our great maintainers will port to our devices; first nightly will be for the very brave.
about 2-3 months of bug fixes until it becomes usable.
give or take by feb we have a daily driver of android L
question is with the f* ups of jjbl and kkbl which kernel will be supported to L, i'm sure cm will use a custom kernel just like it did with cm11 before the moto kk ota.
paranoid android to make l for msm8960 unified
just saw a reply from cj360 he will be working on l for msm8960 devices jbbl and kkbl. he said dont hold your breath ait will take a while
Gr8 stuff so far!
I'm enjoying my recently renewed phone anyways!
Btw, this L inspired Nova Pro customizable theme rocks and ART runtime is superb!
Sent from my Razr HD, Unlocked KKBL, latest CyanogenMod CM11 KK 4.4.4 ROM, ART runtime.
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
the build
cartpig said:
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
Click to expand...
Click to collapse
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
derpyherp said:
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
Click to expand...
Click to collapse
No, it has issues. Blue-tooth is wonky and Netflix and Google Play Movies won't work (you can't watch anything).
DHacker told me via Twitter that it's due to the DRM libraries. He hasn't figured out the right combination yet to get it working,
But, other than that, it works well.
11/16 has the battery percentage in the notification icon.
11/17 apparently has radio issues. Some people have reported that it works for 5 minutes and then the radio dies. A reboot fixes it for about 5 minutes, and then it dies again. Might want to stay away. I'm going to test it, and if I see the same issues, I'll go back to 11/16.
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Not_A_Dev said:
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Click to expand...
Click to collapse
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Click to expand...
Click to collapse
Thanks. Just posted my impressions of running the 11/16 build on that thread.
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad? Xposed doesn't work on it, and if you're running a custom ROM you're already more than likely modified beyond anything that "Android L" is going to give you...
Other than "material design" and "ART" (along with being near impossible to root without an unlocked bootloader) I haven't even read up on what is so special about L that everyone is creaming their pants over it. Please someone enlighten me to the goodness of L other than "it's Google's lastest software".
EDIT: An acceptable answer would be to get off of the botched up KK Moto gave us... twice... Thus why I am sporting DU now - never going back.
LifeAsADroid said:
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad?
Click to expand...
Click to collapse
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Not_A_Dev said:
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Click to expand...
Click to collapse
Lol I will totally agree with you on the battery life thing! I thought my phone was on its way out with how fast the stock KK versions were draining my battery. Constantly had to keep the phone on a charger when I was in one place. I will say that the battery life on DU was one of the things that really caught my attention from the start. Phone makes it through the day, can make it through the night if I forget to charge it overnight, and no more does the phone heat up to 125-140F. Highest I've seen, even with charging, screen on, streaming movies or TV over LTE, has been 98F. Night and day compared to the stock KK ROMs Moto vomited at us. I'd be surprised if other custom KK ROMs for our phones didn't have much improved battery life over that failed attempt at a PR stunt giving us stock KK.
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
+1 for dirty unicorn dev
Not_A_Dev said:
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
Click to expand...
Click to collapse

Still on KitKat (stock rooted) - Benefits to flashing M preview?

Title is pretty much it. I'm still on stock rooted kit kat. I've avoided Lollipop just because at the time it was apparently buggy, and I haven't really paid much attention to roms/android development in a long while. I've been tempted to grab the preview 3 since it came out, but I'm just not sure!
What has improved since KK? Other than having the latest thing, what is good about M?
http://www.android.com/versions/lollipop-5-0/#features
http://www.trustedreviews.com/opinions/android-m-features
http://phandroid.com/2015/07/10/android-marshmallow-preview-2-hands-on-video/
http://www.androidauthority.com/android-m-8-features-google-needs-improve-636359/
+ Developer M preview threads on XDA
I guess you have your answers.

Old Android (4.2/4.4) unsafe?

Hi there,
I know Ive asked this question before, and got some good help, though the thread was a much too long read so here a shorter version hoping to get more responses
Is it safe to use an old Android version? And if it isnt, is it safer to install Gapps so I can get some Google updates (for instance Stagefright fix)?
This tut says to keep 4.2 on your device which makes me wonder what to do: http://forum.xda-developers.com/general/security/tuto-how-to-secure-phone-t2960077
FYI I have a HTC Desire Z (there are some 5.x alfas), Sony Xperia T (pain in the ### to update so prefer not to update to newer Android with the risk of not being able to use my phone for some days if it needs some fixing) and a Gigaset 4.2 tablet.
Thanks a lot.
ruben112 said:
Hi there,
I know Ive asked this question before, and got some good help, though the thread was a much too long read so here a shorter version hoping to get more responses
Is it safe to use an old Android version? And if it isnt, is it safer to install Gapps so I can get some Google updates (for instance Stagefright fix)?
This tut says to keep 4.2 on your device which makes me wonder what to do: http://forum.xda-developers.com/general/security/tuto-how-to-secure-phone-t2960077
FYI I have a HTC Desire Z (there are some 5.x alfas), Sony Xperia T (pain in the ### to update so prefer not to update to newer Android with the risk of not being able to use my phone for some days if it needs some fixing) and a Gigaset 4.2 tablet.
Thanks a lot.
Click to expand...
Click to collapse
Safe..
Safe as in as safe as it gets? Dont the Android updates do nothing at the security front?
I think that the object behind the linked post is not the same as what most people consider "secure". I only looked at it briefly but I think the guide you list is more for "how to make sure that the Big Brother cannot find you". The security that newer versions of Android fix are things like exploits that malware can use to steal your info.
If you're worried about the "malware" type of security, then AFAIK the latest version of Android for your device is the best choice. If you're trying to keep absolutely anyone from tracking you... I guess you can follow that guide... but that's really outside of my area of expertise.
in my view older versions of Android are not sure, because of uncorrected publicized flaws on older android vertions.
for the rest it's up to you.
KitKat was released about the same time as Windows XP end of support. Do you think it would be safe running XP right now? Many would not.
Firefox's ssl/tls is also FAR superior to stock/webview browsers, especially on KitKat and earlier.
Even in the new androids (5.0.0 and above) have vulnerabilities in proprietary libs.
All who know about the vulnerabilities, just silent.

Official Nougat 7.0 soak test starts in Brazil

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

Custom Oreo roms?

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.

Categories

Resources