Related
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Rutr said:
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Click to expand...
Click to collapse
Yup, I saw that, just wondering if we will get official anytime soon.
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
crpalmer said:
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
Click to expand...
Click to collapse
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
kortik9 said:
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
Click to expand...
Click to collapse
Not necessarily having visibility into any framework changes I've made is a pretty reasonable concern. There's only one change that I have already submitted for review so nothing too magical going on behind the scenes. Everything else is available in my public git repos for anyone to verify.
Most of the time official builds start out as unofficial builds. At least that's what I've noticed.
Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03
Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545
Future FAQ if necessary (let's hope not).
Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.
gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.
build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?
Flounder still isn't listed just lunch it anyway
Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse
belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.
gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.
So... CyanogenMod is dead. LineageOS is taking it's place. The ROM is basically CyanogenMod but with changes to the name.
This is completely 'stock' from their source code, so this will encrypt your tablet, and will be prerooted (under Developer options in Settings)
Changelog is available at LineageOS Gerrit
There are no apparent bugs, but any bug reports will be welcome.
Gapps are available at opengapps.org.
Installation
Flash the latest 7.1.1 vendor image in fastboot (fastboot flash vendor vendor.img)
Download latest release from here
Install it in TWRP recovery
Install the downloaded opengapps package
XDA:DevDB Information
Unofficial CyanogenMod/LineageOS 14.1 for Nexus 9, ROM for the Nexus 9
Contributors
hazzer
Source Code: https://github.com/LineageOS/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 7.1.1 (NMF26F) vendor, latest bootloader
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2016-12-04
Last Updated 2016-12-29
Not quite the first CM14.1 for the Nexus 9, but appreciated you taking the time and effort to compile it in any case.
lmulli said:
Not quite the first CM14.1 for the Nexus 9, but appreciated you taking the time and effort to compile it in any case.
Click to expand...
Click to collapse
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
Check hashbang's cm14.1 builds on Android file host.
Can you please post the 7.1.1 vendor image?
Sent from my Nexus 9 using Tapatalk
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
Just go on Androidfilehost and type in flounder
hazzer said:
I hunted for ages trying to find one that had periodical builds, and I couldn't find any here. Do you mind linking me to the thread?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=profile&uid=95897840722645866
Right hand side.
@hazzer Root is broken on latest 12/05 build. It disappeared from the developer settings. It was functioning in 12/04 build.
tibere86 said:
@hazzer Root is broken on latest 12/05 build. It disappeared from the developer settings. It was functioning in 12/04 build.
Click to expand...
Click to collapse
Hi,
Sorry there was no note attached to the build about this. I purposely removed this so that I could pass safety net by default on the ROM.
If you would like root instead of Android Pay, you can try either SuperSU or Magisk with phh's superuser. If you use Magisk hide, you should be able to get root while passing safety net.
Again, sorry about not noting this, I'll make sure I do later today.
Hi,
If you take a look at the download page, I've now added the reason root was and still will be removed. I've also posted a link to the vendor image and latest bootloader. I would recommend downloading the bootloader from Google themselves if possible. The newest source code for the Nexus 9 device tree has been merged into my GitHub however hasn't made it's way into the latest build (20161205). It will be in 06's build.
Sorry about the poor communication regarding root and the likes
hazzer said:
Hi,
If you take a look at the download page, I've now added the reason root was and still will be removed. I've also posted a link to the vendor image and latest bootloader. I would recommend downloading the bootloader from Google themselves if possible. The newest source code for the Nexus 9 device tree has been merged into my GitHub however hasn't made it's way into the latest build (20161205). It will be in 06's build.
Sorry about the poor communication regarding root and the likes
Click to expand...
Click to collapse
Thanks for the info. Just wanted to let you know :good:
Rom is working great!! But i have one problem: I don't have a mobile signal. It just says "no carrier" (in german "Kein Dienst") and i can't set up mobile settings. What to do?
McFlypants said:
Rom is working great!! But i have one problem: I don't have a mobile signal. It just says "no carrier" (in german "Kein Dienst") and i can't set up mobile settings. What to do?
Click to expand...
Click to collapse
That's probably because this is built for the non-LTE version of the Nexus 9. I'm gonna try and add flounder_lte to my build system tonight. I'll post a build sometime tonight or tomorrow if that's okay?
hazzer said:
That's probably because this is built for the non-LTE version of the Nexus 9. I'm gonna try and add flounder_lte to my build system tonight. I'll post a build sometime tonight or tomorrow if that's okay?
Click to expand...
Click to collapse
Yeah, great!! I'll flash it immediately when it's online. Going to try the stock rom now to prove that it's your rom and not the device. We'll stay in contact
McFlypants said:
Yeah, great!! I'll flash it immediately when it's online. Going to try the stock rom now to prove that it's your rom and not the device. We'll stay in contact
Click to expand...
Click to collapse
Hi,
I'm a little late actually successfully getting an LTE version built, as the device tree hasn't been updated for CM14.1 yet. I'll make sure to mention you here when I've got one ready. Sorry for taking so long
Harry
hazzer said:
Hi,
I'm a little late actually successfully getting an LTE version built, as the device tree hasn't been updated for CM14.1 yet. I'll make sure to mention you here when I've got one ready. Sorry for taking so long
Harry
Click to expand...
Click to collapse
No problem, i am aware that it's your freetime you are spending here.
Btw LTE works on CM13 and stock rom, so it's definately not the device. I'm looking forward for your build but i don't need LTE on my nexus 9 the next 4 days. So don't stress yourself :good:
McFlypants said:
No problem, i am aware that it's your freetime you are spending here.
Btw LTE works on CM13 and stock rom, so it's definately not the device. I'm looking forward for your build but i don't need LTE on my nexus 9 the next 4 days. So don't stress yourself :good:
Click to expand...
Click to collapse
I've actually managed to get one built, if you want to take a look. It's below the flounder section. I don't have an LTE Nexus 9 to test, so you'll to let me know how it goes
hazzer said:
I've actually managed to get one built, if you want to take a look. It's below the flounder section. I don't have an LTE Nexus 9 to test, so you'll to let me know how it goes
Click to expand...
Click to collapse
It's fine! Runs smooth like the non-LTE-version but LTE works! Nice
I tried your builds for 13th and 14th of December (WITH LTE) and they all don't get a LTE signal. Also no sim-toolkit installed and no APN-Settings.
I stay with your first LTE-Build, it's fine!
@hazzer: Thanks for your work on the Nexus 9. Any plans to support the official flounder builds?
I was wondering if anyone could send me the last LineageOS 14 build since there are still too many issues in LOS 15 for it to be usable on my daily driver.
Please bring back the LoS 14.1 development, the users are tired of waiting for stable LoS 15 version!
andrevallestero said:
I was wondering if anyone could send me the last LineageOS 14 build since there are still too many issues in LOS 15 for it to be usable on my daily driver.
Click to expand...
Click to collapse
In the los14 thread there is a download link
mezstah said:
In the los14 thread there is a download link
Click to expand...
Click to collapse
Yes, and that download link (in the LOS14 thread) takes you to the download page, which ONLY has LOS 15 downloads...
Search is great tool on XDA
https://forum.xda-developers.com/showpost.php?p=76482344&postcount=2731
predragiPredrag said:
https://forum.xda-developers.com/showpost.php?p=76482344&postcount=2731
Click to expand...
Click to collapse
That's exactly what I was looking for. Thanks!
This is not my build. Credit ny-hardcore for all the hard work on this. I'm just posting it.
Screen call is broken.
This is Lineage 18, Android 11 custom rom for the Pixel 4a Sunfish
If you do not want root, you can stop after step 6
1. Reboot to bootloader
2. fastboot flash --slot all boot recovery.img https://drive.google.com/file/d/1Hh7D_UbnnoTRr1XbC9i0-dvtFgbuFqrP/view?usp=sharing
3. Reboot to recovery
4. factory reset
5. adb sideload lineage-18.0-20201209-UNOFFICIAL-sunfish.zip
https://mega.nz/file/cUlVXApI#NbzUJ6UlyQvyPTitKnW7uJG_tHrsfYor9O0dH4yIiWc
6. Reboot to system
7. Install Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
8. Reboot to bootloader
9. fastboot flash boot magisk_patched.img https://drive.google.com/file/d/1cONN9Ev0jdAHaRSeOeYyeRTONJ-yO_8-/view?usp=sharing
10. Reboot to system
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
liamwhite said:
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
Click to expand...
Click to collapse
Based on the fact that this is NOT my work as stated above, I'm NOT at liberty to tell you. No offense. I would contact xda member edmontonchef and ask him. He's the one who sent it to me. I would like to think this wouldn't be a issue because if it was mine, I wouldn't care, but it's not.
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
I'm using it right now. Great Rom. Thank you!!! Hope you don't mind I shared it.
Does this support signature spoofing?
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
Would doubt it, if it's just vanilla LOS
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
Are Gapps included. Looking for a non gapps rom
EggZenBeanz said:
Are Gapps included. Looking for a non gapps rom
Click to expand...
Click to collapse
No gapps. Minimal Google play service function are included in build.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
No
TheSayaMan said:
No gapps. Minimal Google play service function are included in build.
Click to expand...
Click to collapse
Actually it contains gapps/Google play.
ny-hardcore said:
Actually it contains gapps/Google play.
Click to expand...
Click to collapse
I guess I assumed wrong. I thought he was referring to having to flash a seperate gapps zip.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
ny-hardcore said:
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
Click to expand...
Click to collapse
Oh yeah! Would love to see that. I'm ready to hop from my pixel 3xl once there's a non gapps ROM available
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
TheSayaMan said:
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
Click to expand...
Click to collapse
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
I haven't been able to check everything out. One thing I just noticed is that I am unable to pass safetynet with it but not a big deal for me.
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
TheSayaMan said:
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
Click to expand...
Click to collapse
december hasnt been merged in lineage sources
Is the boot.img a twrp recovery or? I am coming from stock, so would i need to touch twrp at all for this?