Database Users

Samsung Nexus S 4G updated to support Google Wallet

Samsung Nexus S 4G updated to support Google Wallet
This has been posted on Engadget
"It looks like the rumors are true, folks -- the long-awaited update that brings Google Wallet to the Samsung Nexus S 4G on Sprint is indeed here, just two days shy of missing the "summer" deadline completely. We're pretty scant on details at the moment, but the announcement has shown up on an official FAQ page on Samsung's site informing us that build GWK74 is available. If you're a proud owner of the now fully-functional device, you should receive a notification stating that an update is available to deliver the goods via an OTA refresh. We're not sure how long it will take for this to get pushed out to everyone, so a bit of patience may need to be exercised here as you wait. Let us know if you're one of the lucky recipients below."
Has anyone else seen or heard about this yet? Is this different from when this was posted on Sprints site? Will it actually be rolled out now?

Samsung
Sprint update page shows nothing.
No update on my 4G yet.

FOTA_CANCEL is the harshest of messages at times like these.

What's the possibility of pulling the app off of a Sprint Nexus S and having it work on a T-Mo Nexus S?

CaseyB said:
What's the possibility of pulling the app off of a Sprint Nexus S and having it work on a T-Mo Nexus S?
Click to expand...
Click to collapse
I'm sure someone will post the APK soon, but given that it requires NFC Secure Element support, it might have to wait for a similar OS update to enable it on the non-Sprint models. Time will tell.

devlogic said:
I'm sure someone will post the APK soon, but given that it requires NFC Secure Element support, it might have to wait for a similar OS update to enable it on the non-Sprint models. Time will tell.
Click to expand...
Click to collapse
The access to the SE has been in AOSP since 2.3.5. If you have a pure AOSP or other custom rom based off of AOSP you should have access to the SE. If you are running stock 2.3.4 you won't though.

Google tweet

And i'm assuming that if you're on a non-stock rom that you can't OTA right?

EddyBalls said:
And i'm assuming that if you're on a non-stock rom that you can't OTA right?
Click to expand...
Click to collapse
To install the OTA, youll probably need to have a completely stock /system and the stock recovery.

EddyBalls said:
And i'm assuming that if you're on a non-stock rom that you can't OTA right?
Click to expand...
Click to collapse
My Nexus is Rooted, but otherwise completely stock. Too bad it's on T-Mo!

i'm a Nexus S 4g user, and mine is rooted too, but i'm running a custom rom. figures though, i guess tailsthecar3 is right. I'll need to have a stock system. i WAS on a stock rooted rom, and it looks like i'll have to wait for a new rom release with the next build.
lol GO SPRINT! (not really)

i just flashed back to stock, got a 22MB update and it's rebooting and installing now. will edit post later once i get the chance to play with it

I tried updating my stock rooted to the grj22 or whatever...I didnt have the stock apps in /system cause i deleted them, like books, google earth, etc. I wanted to try to update even though I knew I needed the stock /system. I put the stock recovery on it but because the update couldnt find the original files, the update failed.
---------- Post added at 05:24 PM ---------- Previous post was at 05:23 PM ----------
thedudejdog said:
i just flashed back to stock, got a 22MB update and it's rebooting and installing now. will edit post later once i get the chance to play with it
Click to expand...
Click to collapse
Whats your location? Are you certain it was the GWK update? Thanks

thedudejdog said:
i just flashed back to stock, got a 22MB update and it's rebooting and installing now. will edit post later once i get the chance to play with it
Click to expand...
Click to collapse
yea i don't think it's the GWK74 release, i remember when i first got my phone 5 days ago, it gave me an update that was 22 mb.

tailsthecat3 said:
[/COLOR]
Whats your location? Are you certain it was the GWK update? Thanks
Click to expand...
Click to collapse
Kansas City, and no, it seems to be maybe the 2.3.5 update. i don't have a wallet app.
but i'll be waiting for a few days with the stock /system and /recovery just to see what happens. just tweeted sprint for an ETA. seems like they would push the update before they announce it?

Whoever gets it first, please post the full filename of the zip in /cache before you reboot to install it.

Maximilian Mary said:
Whoever gets it first, please post the full filename of the zip in /cache before you reboot to install it.
Click to expand...
Click to collapse
Sure thing. If I get it today...which I doubt I will.

Maximilian Mary said:
Whoever gets it first, please post the full filename of the zip in /cache before you reboot to install it.
Click to expand...
Click to collapse
For sure.
Sent from my Nexus S 4G using xda premium

Google wtf 2.3.7 us day one nexus s users still on 2.3.4 what's the deal? And before I get flamed I know its the wallet update etc etc etc. If I want it that bad it will b on cm7 etc.
There gotta b others out there feeling the same.
Sent from my Nexus S using XDA App

leerobson99 said:
Google wtf 2.3.7 us day one nexus s users still on 2.3.4 what's the deal? And before I get flamed I know its the wallet update etc etc etc. If I want it that bad it will b on cm7 etc.
There gotta b others out there feeling the same.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Haha, switch to sprint and deal with the signal and battery life problems. You gsm nexus s guys have it so good
Sent from my Nexus S 4G using xda premium

Lollipop source is out

Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk

brolic925t said:
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Source ?
Sent from my LG-D852 using XDA Free mobile app

shahkam said:
Source ?
Sent from my LG-D852 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/

I'm OK now, I'm happy to have waited this long for an AOSP ROM.
I can wait longer if it becomes a L ROM for our G3!!

Great news !

it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta

It is usually very hard to get new android versions ported to a device where there is no official rom of the same version for it - you basically are going in blind trying to get all the hardware to work.
If we are lucky we might see one or two builds before LG release theirs (which is now less than 2 months away!) but I would expect them to be buggy with some hardware not working - so far we don't even have a fully working Kitkat AOSP build for our device.

manups4e said:
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
Click to expand...
Click to collapse
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance

Deeemm79 said:
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Click to expand...
Click to collapse
if someone would like to help here is last_kmsg at the very end you'll find the kernel panic about modem

bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/

Oooh. I so happy. ????

jayzhoukj said:
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Click to expand...
Click to collapse
this is true although (and i may well be wrong) i would presume this would only apply if you take the update from OEM and not custom rom .... if we take a flashable custom rom i would assume that this lockdown is completely irrelevant and fairly risk free providing the devs can get all the hardware side of things up and running

ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom

jayzhoukj said:
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
that all depends what you want to be able to do on your device ..... without root you cannot use xposed (although until made to run on ART it wont work with lollipop onwards ) ... you need root to delete / modify any / all system apps and other tweaks under the hood ..... there are many things you could need root for

jayzhoukj said:
not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.

LeoRex said:
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
Click to expand...
Click to collapse
infact since 1 month i'm trying to port lollypop and i'm blocked by kernel panic at boot due to modem resetting

My concern is for our d850 development .... It will pick up im guessing
2SHAYNEZ

OEM Unlock feature in Lollipop dev options
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.

so excited in looking forward to your effort - friends....

hwong96 said:
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
Click to expand...
Click to collapse
OEM unlock meaning ?

No Android N preview roms for N5X?

I'm really surprised for this. On N5, we had m preview roms for every single preview release days after the release, which were just factory images turned into flashable roms, and they worked fine with multirom also.
For N5x, we don't have any of those apparently, and there doesn't seem also to be demand for it. We have unofficial multirom thanks to jolla and others, and yet there is no movement for more roms or profit for it.
This subforum is, for this being a Nexus, way more empty that for any other Nexus phone .

What? There are developer roms available here and you can opt-in to the beta here if you want to use OTA instead of flashing.

link6155 said:
What? There are developer roms available here and you can opt-in to the beta here if you want to use OTA instead of flashing.
Click to expand...
Click to collapse
I think he means a flashable zip for TWRP

RusherDude said:
I'm really surprised for this. On N5, we had m preview roms for every single preview release days after the release, which were just factory images turned into flashable roms, and they worked fine with multirom also.
For N5x, we don't have any of those apparently, and there doesn't seem also to be demand for it. We have unofficial multirom thanks to jolla and others, and yet there is no movement for more roms or profit for it.
This subforum is, for this being a Nexus, way more empty that for any other Nexus phone .
Click to expand...
Click to collapse
Neither 5X or 6P has N Preview roms. Not sure why the change but it is what it is.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Dont relock your bootloader. Because 1. You cant flash the factory images with it locked and 2. If the OTA fails see reason 1.
You aren't going to be on N for that long. There are simply too many bugs right now. So, when you are annoyed you are going to have to wait a day for the MM OTA (if you sign up for OTAs) or you are going to flash the MM images which require an unlocked bootloader. If you sign up for the OTAs, request the MM OTA, wait for it to come, take it and then want to go back to a custom ROM or root or whatever, you are going to need an unlocked bootloader.
Unless you plan on being on the stock ROM (MM or N, unrooted) for the foreseeable future, you dont want to lock that bootloader.
Click to expand...
Click to collapse
Yes if is there a way that we can just flash N and then if we want to go back and restore our custom ROMs without needing to use a stock recovery that would be awesome!! That would make things so much easier. Lol Looking forward to seeing that hopefully soon.

I agree with the OP. There are so many awesome devs who shred stock OTAs and make slim, light ROMs which are flashable via custom recoveries. I wish they did the same for N Developer Preview too.

gururoop said:
I agree with the OP. There are so many awesome devs who shred stock OTAs and make slim, light ROMs which are flashable via custom recoveries. I wish they did the same for N Developer Preview too.
Click to expand...
Click to collapse
+1

gururoop said:
I agree with the OP. There are so many awesome devs who shred stock OTAs and make slim, light ROMs which are flashable via custom recoveries. I wish they did the same for N Developer Preview too.
Click to expand...
Click to collapse
That would be great. Wish I had the know how.

So I took the plunge and installed it. So far so good. Hopefully tomorrow or the next few days when they update the next release will even be greater.

Me too waiting for a striped down custom version of N ROM which can run side by side with M without the need of different vendor images.
Sent from my Nexus 5X using XDA-Developers mobile app

Bump.

http://forum.xda-developers.com/showthread.php?t=3398617

The future development of the S7 Edge?

Let me start off by saying i appreciate all the developers who put in the hard work to make root and such possible. I could not imagine the frustration they go through.
So my question is about the future of this phones development, I feel like as of December 31 2016 that the chances of root are only for those with builds with/under pd8 (as far as I'm aware) (I am running PK1) everyone above pd8 build is SoL. So my question, is there any chance we will see full root for those of us on the newer builds? Also with the talks of the Nougat update around the corner will root be harder to achieve seeing as its new firmware and developers haven't had much time digging into it? My reason for wanting root is to have xposed running, viper4android and be able to debloat it. Forgive my ignorance but does it feel like the s7e development is stuck? I feel like maybe I would get a better experience if I traded in s7e for a device that has more stable development. I'm sorry if I offended anyone, if anything I just want to be informed.

isaac970 said:
Let me start off by saying i appreciate all the developers who put in the hard work to make root and such possible. I could not imagine the frustration they go through.
So my question is about the future of this phones development, I feel like as of December 31 2016 that the chances of root are only for those with builds with/under pd8 (as far as I'm aware) (I am running PK1) everyone above pd8 build is SoL. So my question, is there any chance we will see full root for those of us on the newer builds? Also with the talks of the Nougat update around the corner will root be harder to achieve seeing as its new firmware and developers haven't had much time digging into it? My reason for wanting root is to have xposed running, viper4android and be able to debloat it. Forgive my ignorance but does it feel like the s7e development is stuck? I feel like maybe I would get a better experience if I traded in s7e for a device that has more stable development. I'm sorry if I offended anyone, if anything I just want to be informed.
Click to expand...
Click to collapse
Nothing sure what kind of answer you're looking for that you wouldn't already know.
We only have root due to an engineering kernel.
Android 7 requires a different kernel. So we can't use it.
So unless we get a leaked engineering kernel for Android 7 then we will have to see if we can unlock the bootloader or discover some other kind of exploit. But I'm sure you already knew all of that.

The s7 is pretty much dead, are only hope is that a dev finds an exploit and capitalizes or an inside man leaks a file for Nougat.

AceDaMack said:
The s7 is pretty much dead, are only hope is that a dev finds an exploit and capitalizes or an inside man leaks a file for Nougat.
Click to expand...
Click to collapse
I just got CM14 (Nougat) on my Note 4, it made it into a whole new device way better than the laggy S7Edge. Here's hope that Nougat has some exploit and we can root it. CM14 is so smooth.

Root is supposed to work thru pk1 with eng kernel. When I update to official 7.x I am going to leave bootloader as is so I can still root.
I am not impressed that much with the new rom and hate the user interface, so I may go back to rooted 6.0 until if and when 7.x is rooted.
Sent from my SM-G935T using XDA-Developers mobile app

gaww said:
Root is supposed to work thru pk1 with eng kernel. When I update to official 7.x I am going to leave bootloader as is so I can still root.
I am not impressed that much with the new rom and hate the user interface, so I may go back to rooted 6.0 until if and when 7.x is rooted.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
you may not be able to bootup android 7 with a MM bootloader. I ran into this problem in the past with my older notes. I couldn't get MM to work on a LP bootloader. It would awesome if someone could pull out the Beta nougat BL so we could revert it ends up being a problem.

black96ss said:
you may not be able to bootup android 7 with a MM bootloader. I ran into this problem in the past with my older notes. I couldn't get MM to work on a LP bootloader. It would awesome if someone could pull out the Beta nougat BL so we could revert it ends up being a problem.
Click to expand...
Click to collapse
Before I went back to stock to get the beta on the second phase, I went to stock Verizon and flashed their beta.
I was able to revert to stock tmo pk1, so am hoping that will be possible with the official 7.0 also, as that bootloader in rootable.
Sent from my SM-G935T using XDA-Developers Legacy app

gaww said:
Before I went back to stock to get the beta on the second phase, I went to stock Verizon and flashed their beta.
I was able to revert to stock tmo pk1, so am hoping that will be possible with the official 7.0 also, as that bootloader in rootable.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
it was also BETA so they purposely could let you revert back if you didn't like the bugs ons BETA. that's why I said would be awesome if someone could pull the BETA boatloader so you have best of both worlds(pending on if they the official update wont boot up with a MM BL)

black96ss said:
it was also BETA so they purposely could let you revert back if you didn't like the bugs ons BETA. that's why I said would be awesome if someone could pull the BETA boatloader so you have best of both worlds(pending on if they the official update wont boot up with a MM BL)
Click to expand...
Click to collapse
If we can't revert back to a bootable mm and that us no sign of a rootable nouget, I may just kiss thus device good by and get a 935f.
Chen has multiboot working on it plus, he has a 7.0 Rom with Wi-Fi calling working. I may have to give up some tmo network features, but given that they have no plans to get the higher speed frequencies where I live, there is not much that I will be loosing out on.
Sent from my SM-G935T using XDA-Developers Legacy app

gaww said:
If we can't revert back to a bootable mm and that us no sign of a rootable nouget, I may just kiss thus device good by and get a 935f.
Chen has multiboot working on it plus, he has a 7.0 Rom with Wi-Fi calling working. I may have to give up some tmo network features, but given that they have no plans to get the higher speed frequencies where I live, there is not much that I will be loosing out on.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was thinking the same thing, what all features would you lose? obviously t mobile bloat and wifi calling. what LTE bands would we lose?

black96ss said:
I was thinking the same thing, what all features would you lose? obviously t mobile bloat and wifi calling. what LTE bands would we lose?
Click to expand...
Click to collapse
Would not loose WiFi calling - it is working in Chen's 935f ROM. I think we loose band 12 and possibly another, bit not sure.
The best way would be to ask him - but am going to search his threads before I ask.

Downgrade to Marshmallow to avoid bootloop?

My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel

No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!

Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app

rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..

rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk

Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.

Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?

I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app

CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.

I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.

jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!

Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.

Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app

Bad news, and there isnt official answer from Google

I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it

seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.

jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse

CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?