yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] Arju:
Android O is only in Dev preview stage. The code is bound to change and the full code is not there for us to compile. So if anyone actually are going to try then they are going to build a messy hacked build and have to start all over again when next preview comes. Best is to wait until Android O launched at fall when the final code gets pushed to aosp and that's the right time for developers to work on Android O for our Shamus. In short, now is not the right time.
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
No one is sure. It very well maybe the last AOSP we see. It will still be worked on i am sure but I doubt we will see anything past it for the shamu. This is why many devs have moved to other devices like the 6p or the 3t.
[Nexus 6 Q&A, Help & Troubleshooting] gothy.gothy:
No, not about the time I asked, but the possibility to have Android O, doesn't matter when.

I asked what will be after 7.1.1.

---------- Post added at 11:21 PM ---------- Previous post was at 11:19 PM ----------

Well, it is a pity, because it's a very good device!
[Nexus 6 Q&A, Help & Troubleshooting] Arju:
[MENTION=5266159]gothy.gothy[/MENTION] We will probably see Android O through the unofficial route and I'm sure the Nexus 6 will live to see another year, but further than that it's hard to predict. Zelendel is right that it will only get harder and harder by time and when apps only starts supporting 64bit and looses support for 32bit then we're out of the game. We might get a sloppy hack of a build but loose app support in future major updates after Android O. So the best would be to move to a device that runs 64bit.
[Nexus 6 Q&A, Help & Troubleshooting] npjohnson:
No developers are "working" on 7.1.2 (except maybe a few brave kernel developers), because the source isn't pushed to AOSP until the final release.

I don't mean to start a flame war, but this just isn't right. There has been no effort to "remove" 32-bit support. In fact, the Nexus Player is still a 32-bit device (albeit x86) which is supported by O, it may be 64-bit hardware, but due to proprietary firmware, they decided to have the 2nd-stage bootloader, and kernel/user-space boot in 32-bit mode. It has the O preview out now. Plus the 32-bit toolchains still get active support, and even 64-bit devices (i.e. angler/marlin) run some amount of arm(32) code in the form of their proprietary firmware/libraries, so we'll always need the ability to run 32-bit code on Android, and therefore, not stripping 32-bit compatibility from Android.

Also, there haven't been any specific moves by Google in terms of AOSP source away from 32-bit support.

I'd bet just about any amount of money the Nexus 6 will see O once source drops.

Why would O be the last AOSP we see? Android is mostly licensed under GPLv3, so they have to release source (that compiles) for the large majority of android. If you're refereeing to the fushcia OS they are creating, according to git logs, it is to be used on intergrated system's, as the kernel they wrote is very minimal.
[Nexus 6 Q&A, Help & Troubleshooting] rester555:
My apologies gentlemen, I thought that AOSP was pushed on each developer preview. I didn't realize that it doesn't hit the AOSP Branch until the final build.
[Nexus 6 Q&A, Help & Troubleshooting] rignfool:
Hence why you look silly putting up this thread...
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
This is where you are mistaken. Android isn't under the GPL. Only the kernel is. Android is under the apache license. Google doesn't have to push any code for Android at all. They could completely stop. Or keep doing what they started with the 6p and that is make the system files like system ui closed sourced.

You really have not been paying attention much. Just look at the last issues the nexus had with the updates. Not to mention not getting all of the stuff in the update that the 62 bit devices got.
[Nexus 6 Q&A, Help & Troubleshooting] npjohnson:
Apologies for the typo there. GPLv3 (which requires source release) ==> Apache (which does not). As you noted though, kernel sources are GPLv3.

I really have been paying attention though. I too wondered why the Nexus 6 didn't get Nougat as quickly, and why the 6P's 7.1.2 updates were delayed. If you do some static disassembly/analysis on the Nexus 6's proprietary blobs (in specific, take a look at the prebuilt qcom binaries, like qmuxd and mm-qcamera and the date they were signed), you can deduce that the reason we saw a delayed 7.1.1 (and 7.0 for that matter) on the Nexus 6 was because QCOM either had issues with the specific hardware peripherals related, or just wasn't keen on working on them. An issue that isn't strictly related to 32-bit support, because we saw the same exact issue with Angler on the initial 7.1.2 Beta release (some blobs which are pre-signed being dated barely before the build date). Plus the Nexus 6 itself was never intended to be a Nexus phone. In an interview with one of the Engineer's who worked on the Nexus 6, they stated that there initially was another manufacturer who backed out last minute, forcing them to use the Moto X Pro shell that shipped in China (the hardware is identical + an IR sensor for Moto Display), so Google hasn't ever been to keen on the Nexus 6.

And, what are you referring to that 64-bit devices got that the Nexus 6 didn't? Other than some of the gestures, I don't see it. The 6, 6P, and 5x all got Assistant (well, everyone did), with 7.1.1, they all got gesture support (the 6 is missing one, I think double-tap to wake? And that's because it never worked reliably on the 6's display panel without significant battery repercussions). None of the Nexus series devices got Pixel Launcher (officially at least), but they're all capable of side-loading it (i.e. no 64-bit only libraries), and none of the Nexus series got the Pixel style navigation bar, but I suppose those two could be written off as 'Pixel Exclusives', and are 32-bit agnostic anyway.

One more shining example of 32-bit getting updates just fine is the Android One program, which contains a boatload of currently supported devices (many of which are expected to get O), many of which are not only 32-bit, but MediaTek powered (unrelated, but still interesting).
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
If you look close at the one program, it was an epic fail. They seldom see an update. MTK bweing the main reason they dont get updates. Just ask anyone where andoid one is even sold. Many never even saw a single update.

If you look at the official software that was pushed (not what was pushed to AOSP as they are different) to the pixel you will notice things like the system ui being different as google now closed alot of that off.

Delayed/. You mean delayed, pushed, pulled and then reuploaded. Even with things still broken on the n6. I mean even the latest update for it disabled saftynet checks for the nexus 6 as a workaround for the changes in the code that didnt convert properly from 64bit to 32bit.

You have to understand that google doesnt care about anything older. All they are worring about is the pixel line now.
[Nexus 6 Q&A, Help & Troubleshooting] rester555:
I don't think I look silly at all. Based on the conversation on the thread. I think it was a good discussion.
[Nexus 6 Q&A, Help & Troubleshooting] :
It's still possible for Nexus 6 to see Android 8.0 but it's now more of a chicken and egg issues. As for Android 7.1.2, I am sure it's still officially a hybrid build as well. All we can do is wait and see what's in Android 8.0 Oreo source code this early winter.

As for Nexus player, I doubt they locked Long Mode out of firmware, it's impossible because the kernel can call the stack register required for a jump from Protected Mode (32-bit) into Long Mode (64-bit) directly, no matter what (yes, even in MS-DOS). It's up to Google to decide if Nexus Player stay in 32-bit mode - I bet Android 8.0 will allow it to enter Long Mode this time, with the Long Mode option enabled in Linux kernel - only CPU-Z app will tell you whether it's running in 64-bit mode.
[Nexus 6 Q&A, Help & Troubleshooting] :
we believe in great developers like in lineageOS they are still supporting nexus 4 and nexus 5 without any problems with regularly updates , but if android o is 64 bit that will be the pain
[Nexus 6 Q&A, Help & Troubleshooting] npjohnson:
Well, I wish this was right, but the 2-nd Stage Bootloader (a LittleKernel derivative) runs in strictly 32-bit mode, and we are unable to load any 64-bit kernel's, plus, several device firmwares for the Nexus Player (as provided by Intel) are strictly 32-bit, and don't work in 64-bit contexts.

Several of the One program's phones like, seed, seed2, general mobile 4g, have all not only been hosted on Google's factory image page, and some even got updates much faster than the Nexus 6 did (comical, and ridiculous I agree, but 32-bit non-the-less).

And, with the Pixel's I would agree that Google close sources several app (SystemUI, Frameworks-res, etc.) but it is worth questioning a few things:

1) If they'd given the Nexus's those apps, don't you suppose there'd be some backlash from owners who bought the phone because of its open source nature? The Pixel's made no promise of that.

2) Are the small features they contain even worth it? A blue color scheme (when the old teal is arguably more visually appealing), circular icons (which many hate), and a Night Light Overlay (this is useful, but requires a new hardwarecomposer setup that the 6P just doesn't have, and all the 3rd party/flashable solutions fall back to using a GL shader and the device's battery/performance takes a noticeable compared to the Pixels implementation).

And, as for the SafetyNet check disabling, though Android Police said that, there is literally no proof. The check tokens are still sent, and verified server side, and if you're rooted, the device still fails the authentication. AP threw out some unsubstantiated information. No deivce side-change was needed on the Nexus 6, so they re-uploaded the same factory image, and made a server side change. And nowhere was anything said about it being 64 ==> 32-bit code incompatibility. Do you have any source on that?
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
People these days aways looking for proof when info like this can't be shared openly nor can sources. You would be amazed at things talked about in development chats that don't make it to the users.

Just sit back and watch. I like most other developers have already decided to leave the N6 and get newer devices. When asked about it they already said they will not be converting any 64bit code at all. So anything that is coded for 64 bit devices then the N6 will never see it.
[Nexus 6 Q&A, Help & Troubleshooting] :
At least I have two agendas on hand; 1. I am already planning on buying the next Nexus (Pixel 2) or similar phone with Qualcomm Snapdragon 835 SOC whose bootloader remain user-unlockable and usable on Verizon network (I absolutely hate Verizon's locked bootloader policy). 2. There's other options, like Ubuntu Touch.
[Nexus 6 Q&A, Help & Troubleshooting] H4X0R46:
I sure hope to see Android O on our Shamu! Fingers crossed we'll start to slowly see ROMs after official release and AOSP! Hope it's possible!

---------- Post added at 08:32 PM ---------- Previous post was at 07:58 PM ----------

There's no such thing as a dumb question, how else does one learn? :angel:
[Nexus 6 Q&A, Help & Troubleshooting] AndroidDeveloperLB:
I think there is hope seeing Android O on Nexus 6.

I can see it on this video by Google:

https://youtu.be/63pKwVE4Uog?t=209

Anyway, I created a new post about it here:

https://code.google.com/p/android/issues/detail?id=291102

Please star it if you also wish Nexus 6 to have official update of Android O.
[Nexus 6 Q&A, Help & Troubleshooting] Lawstorant:
Two main things Nexus 6 didn't receive with nougat:

1. File based encryption

2. Vulkan (despite Qualcomm's claim that adreno 420 will get it)
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
A waste of time, and one that I fully expect Google to eliminate by summarily closing your issue.

The reason we are not getting Android 7.1.2 is not because we can't run it - we can - but because Lenovorola wouldn't provide Google with the updated bits necessary to properly support it. Lenovorola I believe is the entire reason it took so blasted long for Android 7.0 to even hit the Nexus 6. Couple that with the fact our device is 2-1/2 years old at the time I write this and it's easy to see why the Nexus 6 won't get an update. And, that doesn't even take the processor into account.

I would be extremely surprised if Google reverses course and offers us Android O. Especially as they want to push the Pixel devices.
[Nexus 6 Q&A, Help & Troubleshooting] adm1jtg:
They wont reverse anything.... they wont even give us 712 as lets face it they still havent been able to get us a properly running 711 and even that may never happen.
[Nexus 6 Q&A, Help & Troubleshooting] 5.1:
Their policy is clear... 2 years software updates and 3 years security updates​. After that, they no more owe you anything. Not that I like it, that's how it is.

Of course 7.1.1 will never be as stable as it should. They are already focusing​ on their next devices. Let's not talk about Lenovo/Motorola...

I just want to see how things go. I was already enjoying the N6 when i first got it, but thanks god we have so much talented developers who made the N6 what it is. A wonderful device. Hopefully the game is not over..! :good:

Cheers...
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
I'd like to see Android O. If I don't get Android O, then I still have Android 7.1.1 working flawlessly on my device. As long as the apps I have still function, I'll be good until it's time for me to upgrade, which probably will not be for another year or so. After all, this isn't the first time I've used a device whose updates stalled due to a technical issue.
[Nexus 6 Q&A, Help & Troubleshooting] adm1jtg:
My first android was a samsung vibrant it went EOL from samsung in under 6 months
[Nexus 6 Q&A, Help & Troubleshooting] AndroidDeveloperLB:
Could be. Still I want to think positively.

I did the same thing about Nexus 5, and it got tons of stars (here), so Google wrote they will think about it. Sadly, in the end they decided not to support it anymore, yet left the thread in "assigned" state to this day.
[Nexus 6 Q&A, Help & Troubleshooting] Ind33d:
Nexus 5 official support only until 6.0.1

So nothing shock if nexus 6 official support only until 7.1.1

The truth is phone manufacturer including Google want us to upgrade to new phone every year or at least every two years when you renew your contract.

They will find a way to make sure you upgrade over the old phone. We are living in the capitalist world anyway.

Even many dev are slowly moving and not supporting old device anymore.

Nobody expect it will become like this when Apple start using 64bit SoC back then...but other manufacturer slowly follow the trend because they will make money from it.

They don't care if you still love your old phone and want software update to it because they already get your hard working money when you buy your old phone . They are busy thinking how new phone will capture the market.
[Nexus 6 Q&A, Help & Troubleshooting] foxxx5oh:
This video shows a Nexus 5 running the O developer preview...so it seems quite possible that the 6 will be able to get it too.

https://www.youtube.com/watch?v=bdB_CL-daxA
[Nexus 6 Q&A, Help & Troubleshooting] 5.1:
Hello,

What video... :eek:

Cheers...
[Nexus 6 Q&A, Help & Troubleshooting] foxxx5oh:
lol my bad...thought I hit paste

https://www.youtube.com/watch?v=bdB_CL-daxA
[Nexus 6 Q&A, Help & Troubleshooting] 5.1:
Hey,

Lol, not sure why he says he has a Nexus 5, but the displayed device is clearly a Nexus 6P... :)

Google for Nexus 5 pictures and compare both devices...

Cheers...
[Nexus 6 Q&A, Help & Troubleshooting] foxxx5oh:
Looking at my 6p, I don't see any similarities...but it does show Nexus imprint...so I may have jumped the gun a bit as it seems more likely to be a 5x and not a 5 -_-
[Nexus 6 Q&A, Help & Troubleshooting] 5.1:
Hello,

It's a 5X indeed... :good:

Cheers...
[Nexus 6 Q&A, Help & Troubleshooting] byt3b0mb:
that is a nexus 5x which has a preview build straight from google. 5x is 64 bit if i am not mistaken.

https://developer.android.com/preview/download.html
[Redmi Note Q&A, Help & Troubleshooting] Prajwal CJ:
After flashing a developer ROM my phones sensors are not working completely.!!! Not even the screen rotates I don't know what's the issue with. I flashed developer after my device was bricked and after unbricking I got this issue.

Plz help me.
[LG Optimus L90] claymes:
Sorry for what may be a stupid question, but what custom ROM would you recommend? I am currently running stock ROM (5.0.2) and it is driving me mad, as it is very slow (on Kitkat it was a lot better).

Btw, on antutu it has something like 16700+ score, is it okay?

The custom rom priorities:

1) fast and stable

2) support of the Cost save mode (or contact so sim bind) - Every contact is added along with assigned SIM when adding in phone book.

3) no problems with BT

3) no problems with GPS

4) good battery life

I did not follow the scene, so I feel a bit lost. So what ROM (based on the priorities above) would you recommend?

1) Cyanogen Mod

2) LineageOS

3) Resurrection Remix

4) Android Ice Cold

5) ... something else

Thank you very much!
[LG Optimus L90] Bayernholic:
For me, CyanogenMod 13 works the best. It is the fastest and the most stable ROM and many Roms are based off of it. I have tried other Roms multiple times but Cyanogen Mod is the one I keep coming back to. :good:
[LG Optimus L90] The_Voice:
Hello,

I have an LG 90 D405n and I want to put a custom ROM on it but I can't get the phone in recovery mode.

I tried everything but the only thing he does is rebooting (until I release the power + Volume down Button).

What can I do?

Second question is: I want the most stable and fast ROM. Which one should I install and where can I find the needed files ?

regards,

Yves
[Galaxy S6 General] couitchy:
Hi everyone,

I am running stock G920FXXU4DPIL (6.0.1) and I want to go back to stock G920FXXU3COI9 (5.1.1).

When I try to flash G920FXXU3COI9 with Odin, it fails at sboot.bin with error "sw rev check fail device 4 binary 3", which is quite normal because Samsung prevents flashing older bootloader over newer bootloader.

So I extracted the content of the stock firmware, removed sboot.bin, cm.bin, modem.bin and repacked a new .tar using android unified toolkit.

Then I flashed the resulting file with Odin.

Flashing worked but now I am stuck at Samsung logo. I cannot enter recovery either.

Only way to soft unbrick the phone is flash stock G920FXXU4DPIL again.

Why ??
[Galaxy S6 General] qasim799:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
[Galaxy S6 General] couitchy:
So do you know where I can find SM-G920F engineering bootloader?

I have searched hundreds of pages and it's nowhere to be found :'(

Thanks!
[Galaxy S6 General] ilDuceo:
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
[Galaxy S6 General] couitchy:
OK i managed to find a combination firmware:

COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02

However there is a pit file inside. Does this mean I have to repartition the device?

Seems tricky since I want to be able to flash a stock firmware afterwards.

Can I extract and flash only sboot.bin from combination firmware?

From my understanding, once I have the engineering bootloader, it will let me flash an older one...
[Galaxy S6 General] qasim799:
there is no problem with it. You can go back to any MM or N firmware.

---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------

Maybe I"m fed up from N grace ux as before N was released i was using note 7 grace ux port. Lollipop is so responsive if you used it then you can feel that is pretty obvious.
[Galaxy S6 General] couitchy:
It worked!

I flashed COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658 768_QB10183466_REV02 to get the engineering bootloader rev4.

Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME but it failed at sboot.bin device 4 binary 3 which prooves that even engineering bootloader prevents downgrade.

Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME without sboot.bin, cm.bin and modem.bin => it worked (not stuck at Samsung logo anymore).

My fingerprint scanner is not working but baseband is here (IMEI ok).

So I have kind of a "hybrid Lollipop" G920FXXU3COI9_G920FXXU4BPF1 but that's ok for what I wanted to do :)

EDIT: CF-Auto-Root-zeroflte-zerofltexx-smg920f doesn't seem to work when using engineering bootloader => I guess I'll have to find a new way to root the phone :-S
[Galaxy S6 General] tazaga:
so any good way to do it ? because nougat is bad
[Galaxy S6 General] couitchy:
Finally I got it rooted using TWRP and flashing SuperSU :)

So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):

(my guess is it will also work with Nougat)

1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free

2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)

3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin

4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files

5. Flash combination firmware with Odin

6. Let it boot once and then go back to Odin

7. Flash repacked stock firmware with Odin

Additional steps to get root:

8. Download SuperSU (flashable zip)

9. Download TWRP

10. Flash TWRP with Odin

11. Enter recovery (TWRP) and flash SuperSU

Voilà !
[Galaxy S6 General] halloo7:
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
[Galaxy S6 General] halloo7:
Okay I downgraded my S6 edge sucessfully to 5.1.1!

I missed that old UI soo mucchh thanks for your guidance
[Galaxy S6 General] couitchy:
Actually there is a reason Samsung doesn't want you to downgrade bootloader: I noticed that every bootloader update usually comes with modem/baseband update, which implies some modifications in the /efs partition as well. An older bootloader would then be unable to read new /efs partition, resulting in a null IMEI. That is why the correct way to downgrade is to flash the old system files but keeping current modem/baseband.

The real stupid thing here is that the stock MM bootloader prevents stock LP image to boot. Fortunately the engineering bootloader can bypass this :)
[Galaxy S6 General] couitchy:
Cool ! :o

:good:
[Galaxy S6 General] halloo7:
Sometimes I get a Kernel Problem. The phone crashes randomly after the downgrade. How to fix this?
[Galaxy S6 General] qasim799:
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
[Galaxy S6 General] couitchy:
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying: