download
https://dl.google.com/dl/android/aosp/razorg-ktu84p-factory-f21762aa.tgz
Anyone know how to run this using Multirom? It needs to be in a zip format...
Bout damn time. Wonder if we'll have to wait 4 more months after L comes out next month? What's the damn point of having a nexus if its not up to date? Stupid. Im done with nexus. Selling this POS and getting something better. At least I'll like my versions behind tablet experience instead of hating everything about this stupid thing that's still behind in updates. Thanks for the heads up tho. At least for now I can say its up to date when I sell it.
Watch each file's last modified time from windows explorer.. It is not like the theories circulating that said google is still testing it or had to do w/ verizon blablabla.. It is just google delay it w/o any reason!
Sent from my Nexus 5 using Tapatalk
pre4speed said:
Bout damn time. Wonder if we'll have to wait 4 more months after L comes out next month? What's the damn point of having a nexus if its not up to date? Stupid. Im done with nexus. Selling this POS and getting something better. At least I'll like my versions behind tablet experience instead of hating everything about this stupid thing that's still behind in updates. Thanks for the heads up tho. At least for now I can say its up to date when I sell it.
Click to expand...
Click to collapse
What?!
Android L is not released yet. Our Nexus devices won't start getting L until it is officially released later this month at the Google Conference.
Google is doing things differently this round where they are announcing the newest build and releasing the beta roms ahead of time so manufactures and developers can get devices and apps out as soon as an official build drops.
The Nexus is up-to-date running the latest official 4.4.4 rom.
Once Android L is released, it will be 4.5 or 5.0 (we'll see).
The reason why the LTE versions take longer is because the LTE spec is not open source like the GSM spec is. Therefore it takes longer to push updates out for the LTE units. This will always be the case no matter the device.
player911 said:
What?!
Android L is not released yet. Our Nexus devices won't start getting L until it is officially released later this month at the Google Conference.
Google is doing things differently this round where they are announcing the newest build and releasing the beta roms ahead of time so manufactures and developers can get devices and apps out as soon as an official build drops.
The Nexus is up-to-date running the latest official 4.4.4 rom.
Once Android L is released, it will be 4.5 or 5.0 (we'll see).
The reason why the LTE versions take longer is because the LTE spec is not open source like the GSM spec is. Therefore it takes longer to push updates out for the LTE units. This will always be the case no matter the device.
Click to expand...
Click to collapse
LTE is not the reason for the delay, Verizon is the reason! If LTE was the reason the N5 would be in the same boat. As much as people want to deny it Verizon screws everything up.
Agree and Congrats !
Rhadamanthis said:
download
https://dl.google.com/dl/android/aosp/razorg-ktu84p-factory-f21762aa.tgz
Click to expand...
Click to collapse
Yes, was Pleasantly surprised
Upgraded immediately
After using it for good 6-7 months decided to root the monster.
1. Took backup of all my Stock apps [ adb backup -all -obb -apk -nosystem -f all.obb.nosystem ] ( pics and songs taken saperately)
2. adb reboot-bootloader
< fastboot oem unlock > ( deletes user-data, but we have backup )
3. adb reboot recovery-clockwork-touch-6.0.4.3-flo.img ( Didnt flash cwm just booted into it )
<Inside CWM>
4. adb sideload super_su_root_update.zip
<Clean Cache>
<Reboot>
5. Install net.segv11.bootunlocker.apk
6. Relock bootloader
7. adb restore all.obb.nosystem { Now All my apps ( even wallpaper ) are back}
And we are into Kitkat Stock Rom with Root.. Greenify, Freedom, Xpose framework, Lucky Patcher, Adblock, Wifi adb , systemApp uninstaller ,Busybox , SetCPU , Rom Toolkit, SoundBoost Patch, Nandroid Manager Patch Here I COME...
Just a serious question. What has Verizon to do with the updates? I have a contract free device, and shouldn't have to wait for months for updates. As someone else said already, LTE shouldn't be the deciding factor since the N5 got the update way before us.
Can someone make this to a flashable ZIP? Please devs.
ShannonAUT said:
Just a serious question. What has Verizon to do with the updates? I have a contract free device, and shouldn't have to wait for months for updates. As someone else said already, LTE shouldn't be the deciding factor since the N5 got the update way before us.
Click to expand...
Click to collapse
I thinks the reason google made the LTE version is mainly specific for Verizon network only..
That's my opinion...
I don't think so. When the N7 LTE first came out Verizon wouldn't let you get a SIM to get on their network even if you had a contract. They argued that it wasn't an approved device despite the fact that if you had an active Verizon SIM from another device you could get service just fine.
Well, I just got the OTA update today. East coast USA. Yeah!
Finally. Long delay in the release of 4.4.4 on Nexus 7/2013 for whatever reasons. My guess is Google forgot about it.
No doubt the L release will be something good, and maybe seeing some new Nexus devices. Hopeful.
I have in The netherlands Vodafone. There was a radio bug in The 4.4.3 update is this solved in the 4.4.4.??? I stil dont make 4g contact tot Vodafone....
Related
I'm still thinking about getting this phone and wondering how fast Motorola will be with their updates. Being that they are owned by Google, it's kind of baffling to me that it ships with 4.2 instead of 4.3 right about of the box.
And with 4.4 on the horizon, I'm not expecting it to be updated like a Nexus device but hoping they won't drag ass and take forever and a day. This would be my first Motorola device and I've heard about them being terrible with updates in the past but that was before Google bought them out.
Unless someone here can tell the future....
Sent from my XT1058 using Tapatalk 4
Someone with an inside source said that their timetable for releases is 2 months after a new version is released.
Part of the requirements for the purchase of Moto was that they couldn't receive any special treatment when it came to code release from Google. Which means that they don't get the source code for new versions before any other vendor unless they have been chosen to build a nexus device. I that case they can only work on it in connection with the Google Android team.
The two month timetable isn't assume h that has been officially confirmed, so it may not be completely accurate.
Sent from my XT1058 using Tapatalk 2
I've read a few articles which mentioned that although Motorola is now owned by Google, they are in fact keeping a "firewall" between the two companies. This could explain why the Moto X was released with 4.2 instead of 4.3.
Also, based on what I've seen in recent trends, carriers will be releasing Android OS updates over the air as opposed the Motorola (at least here in the States). Some approach OS updates better than others. Verizon is known to take their time releasing updates to phones because of the extensive testing they do with an upcoming update for a particular device. Take for instance the Droid DNA, a device released close to the end of last year which is only now getting the update to 4.2 from 4.1. I sincerely hope the Moto X does not see such neglect when it comes to future updates but I also wouldn't be surprised.
Over the years I have learned one thing. If it's not a nexus, expect the absolute worst case scenario for ROM updates.
with the ability to flash roms coming soon this may not matter
Sent from my XT1058 using XDA Premium 4 mobile app
scorpion667 said:
Over the years I have learned one thing. If it's not a nexus, expect the absolute worst case scenario for ROM updates.
Click to expand...
Click to collapse
I'd like to believe that Moto offers better support than Samsung and HTC. The 4.3 update is still in the works but hard to put an eta on it as they probably still need time to make sure the moto apps and hardware is optimized to work properly. Other than improved performance and stability, I'm not missing anything by using 4.2.2 for now.
One good thing this phone has going for it is it's pretty much stock Android. No Touchwiz, Sense or any other overlay like Motoblur. This means it should be easier and faster to update since they just have to get the few things working on the next version. I wouldn't be surprised if Motorola skipped 4.3 and went straight to 4.4 since it's close to being released.
housry23 said:
One good thing this phone has going for it is it's pretty much stock Android. No Touchwiz, Sense or any other overlay like Motoblur. This means it should be easier and faster to update since they just have to get the few things working on the next version. I wouldn't be surprised if Motorola skipped 4.3 and went straight to 4.4 since it's close to being released.
Click to expand...
Click to collapse
The problem isn't necessarily the skins though; it's the US carriers.
NoNameAtAll said:
The problem isn't necessarily the skins though; it's the US carriers.
Click to expand...
Click to collapse
This. If it's going to take moto two months, expect longer because it will need to be blessed by the carriers before OTA updates are pushed out.
I wonder where the T Mobile X fits in then... Will it be updated straight from Moto? If not that might be a big problem because T Mobile obviously doesn't even support the phone.
NoNameAtAll said:
The problem isn't necessarily the skins though; it's the US carriers.
Click to expand...
Click to collapse
You're right. I actually had a big long post about how once Motorola gets the code, implements their features, at&t still has to test it and approve. Hopefully, since it's basically stock android, it won't take as long because the skinning process doesn't have to happen.
Sent from my XT1058 using Tapatalk 4
Motorola has a very mixed record so far with their updates. The OG Droid was actually quite good at getting updates in a timely manner and only trailed the Nexus by a few weeks. After Motorola switched to Blur though for all their devices they lagged behind by a few months and even though with Jelly Bean they removed most of the Blur apps in favor of stock, that was still nearly what 9 months after 4.1's source was released before the Razr, Bionic, Droid 4 all got it. In fact for a while there they were one of the slowest at releasing their updates.
Now the Moto X is a new beast though and different from what Motorola has done now so it's hard to say. All the previous devices were part of the "old motorola" and the X is the first device of the "new motorola". The X is almost pure stock so there is very little tweaking that will need to be done. They just need to add in support for their Camera App, Active Display and Touchless Controls, do any kernel updates/bug fixes and then test/resolve any new bugs that popped up in 4.3. Motorola has said that an update is in the works and will come out soon with many improvements for the Moto X. Is this 4.3 or just a newer 4.2.2 build? We don't know.
I'd like to imagine that we will see 4.3 released sometime between now and early October on all carriers considering Samsung announced they will begin to roll out 4.3 to the SGS4, SGS3 and Note2. If Motorola is the first to release a stable, solid build of 4.3 for their new X8 devices and continues to keep up with their updates in a quick and timely manner, it would do a lot to rebuild their name. Right now we just have to wait and see if Motorola is serious about getting better about releasing timely updates or not.
clankfu said:
I'm still thinking about getting this phone and wondering how fast Motorola will be with their updates. Being that they are owned by Google, it's kind of baffling to me that it ships with 4.2 instead of 4.3 right about of the box.
And with 4.4 on the horizon, I'm not expecting it to be updated like a Nexus device but hoping they won't drag ass and take forever and a day. This would be my first Motorola device and I've heard about them being terrible with updates in the past but that was before Google bought them out.
Click to expand...
Click to collapse
I'm in contact with Punit Soni (Moto X product Manager). He's very active on Google+ and he addressed the update and OTA of 4.3 questions. He said when they officially released the device to distributors, 4.3 just got announced. So it was either delay the Moto X and piss off many pre-ordering customers, or continue with the primary plan and push through with 4.2.2.
He said the update is "Coming soon" as they always say, and he promises many fixes like Camera improvements, Picasa or Google Photos sync for Gallery, and OS 4.3 very soon.
"When will then be now? Soon!"
EDIT: wrong thread.
linuxgator said:
Part of the requirements for the purchase of Moto was that they couldn't receive any special treatment when it came to code release from Google. Which means that they don't get the source code for new versions before any other vendor unless they have been chosen to build a nexus device. I that case they can only work on it in connection with the Google Android team.
Click to expand...
Click to collapse
Each OEM gets the source at the same time. Makes no difference. The only reason it takes so long is a mixture between putting loads of framework in. And wanting to get new hardware out.
Moto, working with next to stock android, will be much much faster. No they dont get special treatment per se. But time will be light speed compared to HTC and Samsung
Sent from my XT1058 using XDA Premium 4 mobile app
GR36 said:
But time should be light speed compared to HTC and Samsung
Click to expand...
Click to collapse
FIFY
If it goes the way the Tmobile nexus 4 goes than it will be updated right away. My son has the nexus4 bought directly from Tmobile store & it receives updates along with those bought directly from Google. I know its still a nexus and the moto x isn't but from what I understand the Tmobile version of the x doesn't have any carrier installed stuff on it, so hopefully it will be treated as a device like the Google editions.
Sent from my GT-I9505G using xda app-developers app
Having just installed omnirom with it having the ota updates, once android L is officially released, will all nightlies adapt to it on current installs? Or will that be a whole new install? Just curious. Thanks
Without the code handy, it'll be hard to say for sure. I'd hazard a guess and say new Android base, new nightly branch. But that's just a guess.
I agree with you. Because it's a new code, I also think that you'll need the whole new installation after all..
Sent from my Xperia S using XDA Free mobile app
There's a good chance from a developer standpoint it'll require major rework/rebasing.
From a user standpoint, it SHOULD be feasible to do a straight upgrade without wiping. (Although in the case of features that aren't re-implemented yet when L nightlies start, they'll reset to their defaults when they make it back in.) You will NOT be able to downgrade without wiping or restoring a backup though.
As a historical reference - many of my devices that were running 4.3 Omni were upgraded straight to 4.4, even though we started from scratch with 4.4
Well it's close to nexus6 release... Any news if omnirom will adapt to Lollipop or require a new rom?
ryancell said:
Having just installed omnirom with it having the ota updates, once android L is officially released, will all nightlies adapt to it on current installs? Or will that be a whole new install? Just curious. Thanks
Click to expand...
Click to collapse
If you mean "will moving to L require a wipe?" - Only if we screw something up. Android is designed to allow for seamless upgrades from one version to another, in fact, in the commercial world, requiring a wipe to upgrade will render you ineligible for GMS (gapps) licensing I'm fairly certain.
As to "all nightlies" - probably quite a few devices are going to get dropped with L. Almost surely the Exynos 4210 family, good chance quite a few of the Exynos 4412 family (I'd prefer to make it ALL of them tbh, and get that hell platform out of our codebase...), and probably a few other devices.
Other than Exynos4, we won't know until L gets released.
I'm on the sprint galaxy nexus which just recently got support for omnirom. Hopefully it will get L.. It will save me buying the nexus 6 as I will be happy to upgrade and keep my device. Great job/rom.
Entropy512 said:
...quite a few of the Exynos 4412 family...
Click to expand...
Click to collapse
My heart...
Entropy512 said:
a few of the Exynos 4412 family (I'd prefer to make it ALL of them tbh, and get that hell platform out of our codebase...).
Click to expand...
Click to collapse
oh man, I really do hope you guys manage to get L on my Note 2. There's quite a few of us out there, and it would be oh so nice not having to upgrade our hardware.
And are Omni people already working with Android 5.0 or they need to wait for official release?
j2002 said:
And are Omni people already working with Android 5.0 or they need to wait for official release?
Click to expand...
Click to collapse
Wait for the code drop to happen. Should not take long.
Sent from my Nexus 5 using XDA Free mobile app
shri_chanakya said:
Wait for the code drop to happen. Should not take long.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unless Google drops source earlier than normal (read: typically not until a few days after the first OTAs go out to Nexus devices), I wouldn't expect work to even start until November. (Since it sounds like the earliest OTAs and devices shipping are going to be November 3, which means that's the earliest possible date to even think about doing work unless Google drops source earlier than they ever have in the history of Android.)
So according to this the Verizon Nexus 6 will come with 5.1 Lollipop. Does this mean that Motorola will rollout Lollipop to the DT around this time? And will it be 5.1 Lollipop?
Verizon's Nexus 6 could arrive very soon http://www.engadget.com/2015/02/27/verizon-nexus-6/ via Engadget Android
Update: Its been confirmed that the Nexus 6 will drop on Verizon tomorrow and with 5.1 Lollipop. No word on a locked down BL though.
Google's Nexus 6 will finally reach Verizon on March 12th http://www.engadget.com/2015/03/11/google-nexus-6-for-verizon/ via Engadget Android
While the Nexus 6 has been confirmed to have 5.1, no word has been given about the DT being upgraded to 5.1 or any other version of Lollipop as of yet.
So according to what?
Sorry forgot to attach the link - OP updated
I'm hoping we are updated by then, but I seriously doubt that it will be 5.1, most likely 5.0.2 which has been cycling through the Moto line.
kingersj1 said:
I'm hoping we are updated by then, but I seriously doubt that it will be 5.1, most likely 5.0.2 which has been cycling through the Moto line.
Click to expand...
Click to collapse
5.1 is already out for limited devices. We may get 5.1 after all said and done
True, we most likely get 5.1, I just don't think this update. Most likely the next update, which should be faster once we are on lollipop.
GreaterLesser said:
So according to this the Verizon Nexus 6 will come with 5.1 Lollipop. Does this mean that Motorola will rollout Lollipop to the DT around this time? And will it be 5.1 Lollipop?
Verizon's Nexus 6 could arrive very soon http://www.engadget.com/2015/02/27/verizon-nexus-6/ via Engadget Android
Click to expand...
Click to collapse
Motorola wont roll out anything the update will come from Verizon not Motorola.
sinclac said:
Motorola wont roll out anything the update will come from Verizon not Motorola.
Click to expand...
Click to collapse
lol! Nope... Verizon just approves the Update.. Rest of the work is done by Motorola! IF you look at the Logcat you will see the link from where the Update is downloaded off n its the Motorola Servers...
Gundabolu SC said:
lol! Nope... Verizon just approves the Update.. Rest of the work is done by Motorola! IF you look at the Logcat you will see the link from where the Update is downloaded off n its the Motorola Servers...
Click to expand...
Click to collapse
Keep dreaming, that update will come from Verizon just like all updates before, Verizon gets the update bloats the hell out of it and then releases it.
sinclac said:
Keep dreaming, that update will come from Verizon just like all updates before, Verizon gets the update bloats the hell out of it and then releases it.
Click to expand...
Click to collapse
Nope... U think Verizon sits n adds bloat n release the software? Nope.... They give the apps that need to be added to Moto's software Developers... the Verizon framework is allover the System partition on the turbo, so its not just adding a bunch of apps its integrated deep... Then Motorola makes loads of builds with one build a day n test the siftware on prototype phones... Once they feel the software is stable enough then send it to Verizon for approval... If Verizon is not satisfied with the bloat, they reject it and Motos gotta start adding the bloat n test it out again...
Not holding my breath on any updates soon on the Turbo. This phone has been out for over half a year now with nothing in the works. For a near stock phone I'm not sure why it's taking a back seat to all of these other devices that are getting Lollipop. So much for my decision to go with a Motorola device because of a so-called quick update schedule.
m4rk0358 said:
Not holding my breath on any updates soon on the Turbo. This phone has been out for over half a year now with nothing in the works. For a near stock phone I'm not sure why it's taking a back seat to all of these other devices that are getting Lollipop. So much for my decision to go with a Motorola device because of a so-called quick update schedule.
Click to expand...
Click to collapse
Nothing in the works eh? So there have been NO updates then?
Oh and its been 4 months, but what's rounding it up by another two gonna hurt? It makes it more dramatic.
Everyone wants Lollipop, but doesn't care that it is less stable than Kitkat. Lollipop is just another ICS repeat. ICS didn't start becoming truly stable until 4.1, which Google for some reason deserved a name change. It took forever for devices to update to ICS, and by the time some did, Jellybean was out. Lollipop is a full point release, and major Android overhaul. This is not a 4.0 -> 4.1 -> 4.3 -> 4.4 transition. This is a 4.4 -> 5.0 transition and major parts of Adroid have been reworked. It isn't just a theme. It hasn't been a smooth launch. Verizon is strict with their testing, and we all know that. They are not going to let an OS less stable than its predecessor pass testing on one of their flagship devices. Despite what you want to believe, the Turbo is their specific flagship and they will want it to be the most stable.
Hey, I want Lollipop too. However, Im willing to take the instability with it. Verizon apparently is not after seeing how it fared on the X. The truth has always been out there, no matter how much people want to ignore it: If you want the ultimate network and stability, you got Verizon. If you want bleeding edge software on your devices, you go elsewhere.
So to be frank, anyone who bought the Turbo expecting blazing fast updates should blame their own misconceptions.
You can get excited about two minor updates with imperceptible bug fixes but I'm referring to OS updates.
m4rk0358 said:
You can get excited about two minor updates with imperceptible bug fixes but I'm referring to OS updates.
Click to expand...
Click to collapse
Then you shouldn't be on Verizon. Verizon has had a few quick updates over the years, but it doesn't erase all the slow ones.
This is nothing new.
It sucks, but sometimes the bitter truth is what people need. I only stick with Verizon because I am potentially on call 24/7 and my phone at work is tied into my cell phone. I need a reliable carrier and due to where I live, where I travel, and where I work, Verizon is the most reliable.
adrynalyne said:
Then you shouldn't be on Verizon. Verizon has had a few quick updates over the years, but it doesn't erase all the slow ones.
This is nothing new.
It sucks, but sometimes the bitter truth is what people need. I only stick with Verizon because I am potentially on call 24/7 and my phone at work is tied into my cell phone. I need a reliable carrier and due to where I live, where I travel, and where I work, Verizon is the most reliable.
Click to expand...
Click to collapse
By far most reliable for me. Maybe I'm misunderstanding the concept of XLTE or how it ties in with VoLTE but since the DT had it's second VoLTE update I haven't dropped one call and with XLTE I'm on LTE 97% even underground here in Chicago. And I make a lot of calls everyday. We all want updates as soon as possible but as long as what we have works then I can wait.
Gundabolu SC said:
Nope... U think Verizon sits n adds bloat n release the software? Nope.... They give the apps that need to be added to Moto's software Developers... the Verizon framework is allover the System partition on the turbo, so its not just adding a bunch of apps its integrated deep... Then Motorola makes loads of builds with one build a day n test the siftware on prototype phones... Once they feel the software is stable enough then send it to Verizon for approval... If Verizon is not satisfied with the bloat, they reject it and Motos gotta start adding the bloat n test it out again...
Click to expand...
Click to collapse
Gundabolu is correct all Verizon does is test and certify the update. Motorola is the one to actually push it
Jweimn said:
Gundabolu is correct all Verizon does is test and certify the update. Motorola is the one to actually push it
Click to expand...
Click to collapse
Does not change the fact that Verizon releases it, then it is pushed to us.
Chicken/Egg
sinclac said:
Does not change the fact that Verizon releases it, then it is pushed to us.
Click to expand...
Click to collapse
No not at all nor does it change the fact that Verizon is slow to approve updates. I still feel this time around though that moto is being fairly slow at getting this update out but who knows
Jweimn said:
No not at all nor does it change the fact that Verizon is slow to approve updates. I still feel this time around though that moto is being fairly slow at getting this update out but who knows
Click to expand...
Click to collapse
Agreed, Verizon always seems to be the last to update.
Hey all I have a purely stock unrooted nexus 6p that I am trying to figure out why I am getting the monthly update a week before the release of the next update ever time. I am thinking its ATT blocking the updates. Can you please post the carrier, date and time when you received the May update please?
VZW and mine showed update on the 13th. Was starting to wonder when I'd see it, but it finally hit.
Still waiting here on Sprint for the update. This is taking forever.
Sent from my Nexus 6P using XDA-Developers mobile app
I have Project Fi and get my updates rather late too. It's not just you.
If you really want the update, then by all means flash it manually as soon as it comes out.
I don't think that the carrier can actually block the update, unless you somehow bought the 6P carrier-branded, and through the carrier. That being said, I've been on Tmo, Fi, VZW, and Straight Talk, and I have never actually received a monthly security update as soon as they are released. Usually I had to wait a couple of days. I think those updates roll out randomly, so I'd say just keep waiting, or flash it yourself.
Nexus updates are known to be pushed out in stages.
If you are desperate just flash the images via fastboot or sideload the ota via adb.
Yes I know I can side load the update. That is not the point of this post. Its to get an idea of timing of when people are getting the updates and what carriers they are on.
Google releases there updates in a phased approach. They first release it to 1% all the way up to 100%. 100% should be getting the update within 2 - 3 weeks. The 2 -3 week period I have yet to see!
What I was trying to determine is if this is the carriers blocking the updates till a specific time or its google just not pushing updates to the phones like they say they are.
Note ATT is notorious for blocking updates. And yes they can block the update as long as your using there network to check.
If Google is releasing security updates on a monthly bases and you don't get it before the next update is released, whats the use in a monthly update???
brichardson1991 said:
Nexus updates are known to be pushed out in stages.
If you are desperate just flash the images via fastboot or sideload the ota via adb.
Click to expand...
Click to collapse
How do you side load. I just saw that google has released images to do that. I too have a 6p completely stock. I want to keep the bootloader locked. I have never had a nexus device before. So this is new to me I always used Samsung. The problem with Samsung is you have to mod the hell out of it. this phone just works like it is supposed to. but I do want to try to update manually. So I followed the instructions in the general section and I am installing the sdk as we speak. So what is the process for side loading and where do I get the update? My phone gets its updates really late in the month and I hate waiting. Also I booted this phone into recovery and tried to do a factory reset but it didn't do it and there were all these options I am not used to. How do I do a basic factory reset from recovery? I would like to know just in case. I am not wanting to go crazy with this phone but I do want to understand it so when I get the nexus 7 I can play with this one when I get spare time.
They had a bug to fix finally...
Lenovorola mentioned this last month. Is your source different from mine (Lenovorola Germany)?
Might be AP's post - http://www.androidpolice.com/2016/1...7-1-1-update-will-come-nexus-6-early-january/ - they sent in a query to Google, and Google's response indicated "early Jan"
Was there ever any doubt? The Nexus 6 will get every Nougat release (7.1.1, 7.1.2, etc.). It will not, however, receive Android O.
@Candy[MAN]: It will be at Google's discretion as to whether we get an official upgrade to Android 8.0 or not. But even if we don't, ROM developers will be building from source for years to come. One way or another, this device will have Android 8.0 on it.
Never underestimate power of Nexus devices.
too little, too late. personally the only reason i bought a Nexus was to have the latest android version ALWAYS. and google has disappointed.
though im glad for drivers being available to public so we can have an arsenal of stable and functional ROMs being developed by other devs.
currently running PureNexus 7.1.1 with the middle finger help up facing google.
woomera said:
too little, too late. personally the only reason i bought a Nexus was to have the latest android version ALWAYS. and google has disappointed.
though im glad for drivers being available to public so we can have an arsenal of stable and functional ROMs being developed by other devs.
currently running PureNexus 7.1.1 with the middle finger help up facing google.
Click to expand...
Click to collapse
You have the ability. The nexus line was never meant for the average person. If you cant build from source then a nexus is beyond you
Strephon Alkhalikoi said:
@Candy[MAN]: It will be at Google's discretion as to whether we get an official upgrade to Android 8.0 or not. But even if we don't, ROM developers will be building from source for years to come. One way or another, this device will have Android 8.0 on it.
Click to expand...
Click to collapse
Exactly!! :highfive:
January images posted for every device except Nexus 6.
zelendel said:
You have the ability. The nexus line was never meant for the average person. If you cant build from source then a nexus is beyond you
Click to expand...
Click to collapse
Tsk tsk. There's no room for accusations like that here. The reason I got a Nexus 6 was so that I'd have the latest stock OS without having to flash some buggy (yes, they are buggy and there are always room for screwups) ROM and worry about having an operable phone. Google has done a fine job of providing a stable experience on great hardware at low cost. This phone has been out for 2 years now. Why they can't get these Nougat updates out on time is beyond me. "Well it's the only 32-bit Nexus left" is not an excuse. Android has been built on 32-bit up until the past year or two, and 64-bit phones only became "good" in the past year. Whether the fault lies with Lenovo/Motorola or with Google, the fact is that we just don't have 7.1.x yet, and that's just an embarrassment on whoever's fault that is.
BlockOfDynamite said:
Tsk tsk. There's no room for accusations like that here. The reason I got a Nexus 6 was so that I'd have the latest stock OS without having to flash some buggy (yes, they are buggy and there are always room for screwups) ROM and worry about having an operable phone. Google has done a fine job of providing a stable experience on great hardware at low cost. This phone has been out for 2 years now. Why they can't get these Nougat updates out on time is beyond me. "Well it's the only 32-bit Nexus left" is not an excuse. Android has been built on 32-bit up until the past year or two, and 64-bit phones only became "good" in the past year. Whether the fault lies with Lenovo/Motorola or with Google, the fact is that we just don't have 7.1.x yet, and that's just an embarrassment on whoever's fault that is.
Click to expand...
Click to collapse
Well considering that what ever Google pushes can be made by syncing aosp, build it, flash it and gapps and you have the same thing Google pushed out.
The n6 is eol pretty much. So it is not a surprise that it is last.
Also yes 64 bit just started being the norm. Which means they have been working on it for all east 2 years. People seem to forget that when a device is released the oem already started work on the next device a few months prior. So in sense the brand new device you just got is already outdated as far as the maker is concerned.
Also considering that the stock update issued from Google has bricked many devices that did get it. Then by all means be in a rush.
I have been on a bugless 7.1.1 room now for weeks if not months.
zelendel said:
Well considering that what ever Google pushes can be made by syncing aosp, build it, flash it and gapps and you have the same thing Google pushed out.
(..)
I have been on a bugless 7.1.1 room now for weeks if not months.
Click to expand...
Click to collapse
Some weeks ago when i flashed PN 7.1.1, as an example, i was stuck outside of home in need of creating an hotspot and not being able to do it kicking out an error (lucky me carrying more than one phone at a time). I wouldn't call that bugless, also the battery life is worse and it tends to lag more with time.
Custom roms are nice as they are, without proper blobs there will always be "bugs", "drains", "hacks" to make it work. It's funny flashing different roms to pass time but in the end i always return to stock with a custom kernel because everything works as it should.
Google spits out bull**** every time an update is released, i would prefer them saying they would stop supporting the device than spiting out lies as they always do lately. Good guy croogle is no more.
lordneopt said:
Some weeks ago when i flashed PN 7.1.1, as an example, i was stuck outside of home in need of creating an hotspot and not being able to do it kicking out an error. I wouldn't call that bugless, also the battery life is worse and it tends to lag more with time.
Custom roms are nice as they are, without proper blobs there will always be "bugs", "drains", "hacks" to make it work. It's funny flashing different roms to pass time but in the end i always return to stock with a custom kernel because everything works as it should.
Click to expand...
Click to collapse
Can't say anything about pure nexus as I have never used it nor will I.
Of course there will always be hacks but let me let you in on something. Considering that the 7.1.1 update was made for devices with dual partitions, for them to get it to work on the older devices, n6, n6p and 5x there will be hacks to make it work directly from Google. Most likely what caused a bunch of bricks from Google ota. There was a commit just yesterday that was supposed to fix the issue a second time.
No OS is perfect. Not custom or official. They all have bugs.
zelendel said:
Well considering that what ever Google pushes can be made by syncing aosp, build it, flash it and gapps and you have the same thing Google pushed out.
The n6 is eol pretty much. So it is not a surprise that it is last.
Also yes 64 bit just started being the norm. Which means they have been working on it for all east 2 years. People seem to forget that when a device is released the oem already started work on the next device a few months prior. So in sense the brand new device you just got is already outdated as far as the maker is concerned.
Also considering that the stock update issued from Google has bricked many devices that did get it. Then by all means be in a rush.
I have been on a bugless 7.1.1 room now for weeks if not months.
Click to expand...
Click to collapse
But that's the thing, it's not technically 7.1.1 without the proper driver blobs from Lenovo/Motorola, and obviously we don't have those without the official 7.1.1 update. You may have the 7.1.1 OS, but until the official 7.1.1 is released for Nexus 6, the hardware won't be any more stable than the latest official nougat we have.
BlockOfDynamite said:
But that's the thing, it's not technically 7.1.1 without the proper driver blobs from Lenovo/Motorola, and obviously we don't have those without the official 7.1.1 update. You may have the 7.1.1 OS, but until the official 7.1.1 is released for Nexus 6, the hardware won't be any more stable than the latest official nougat we have.
Click to expand...
Click to collapse
Assuming that there are significant changes in the drivers and vendor blobs from 7.0 official. Didn't seem to be from 7.0 to 7.1.
Funny we saw this same kind of bullkaka (lies) that google would keep updating our Nexus too. And we got nougat, like 3 or 4 months after they promised it. I ran the beta for a long time. Now we thought it would be 7.1.1 like the other Nexus devices that came out after ours. And not even a January patch yet. It does not take a genius to figure out that they are trying to get us to upgrade the device. I refuse to give in. I will just keep the November build and use a custom kernel and doubt I am missing any swell things.
lordneopt said:
Google spits out bull**** every time an update is released, i would prefer them saying they would stop supporting the device than spiting out lies as they always do lately. Good guy croogle is no more.
Click to expand...
Click to collapse
I just vented in the 9 forum as well, but F google here too. They suckered me in with the nexus 5 about 4 years ago as bait, great inexpensive phone I enjoyed using. It also opened up my world to sites like XDA and customizing android. I was hooked right away. So I even upgraded to the 6 and 9 when they came out expecting the same kind of experience . But now looking back I have had lie to myself about just how good the experience has been.
The 5x and 6p gave me no reason to upgrade, I was excited for the pixel line but Google seems to be taking steps to lock it all down from now on.... sooo, I'm out !
Can you point me in the direction of the nearest apple store?
fazbender said:
Can you point me in the direction of the nearest apple store?
Click to expand...
Click to collapse
First left, second right and then its on the left side of the road.
hey guys, is it possibile that the akku and bootloop bugs from the n6p also can happen to n6??