yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 3 Questions & Answers] cletusarrarr:
This is a request if someone can make a minimalistic rom, preferably for the SNapdragon version (both would be even better)

This rom preberaly runs on a custom kernel tweaked to have less logging and a minimalistic approach.

It should have only the minimal software needed for the hardware to function, the rest could be an optional flash package where one could choose what they need, this will not only help run the phone cool and smooth but also improve the spectacular battery life.

this rom if built on the global beta could have root built in , since bootloader would be unlocked to flash this rom.

Thoughts anyone ?
[Xiaomi Redmi Note 3 Questions & Answers] LordJeremy:
Nice idea! I also have the feeling MIUI is too bloated and that too many unnecessary services are active. I hope someone would consider this idea and if someone misses any functions, they should be able to flash a zip file or select the functions via an AROMA installer when you first install the rom.
[Xiaomi Redmi Note 3 Questions & Answers] cletusarrarr:
so used to having this on ever other device ive owned , have half a mind of doing it myself, unable to unlock my bootloader yet even though ive got the sms , waiting to do it the right way to get root access.
[Xiaomi Redmi Note 3 Questions & Answers] LordJeremy:
Wish you luck, unlocking the bootloader officialy is indeed quite the hassle. Hope they fix the problems with mi flash unlock tool some day. I'll try to help you out when I can unlock the bootloader as well.
[Xiaomi Redmi Note 3 Questions & Answers] mr.loverlover:
I also would like to see some slim version, especially one that doesn't consume too much ram.

The lightest edition I've found until now are the xiaomi.eu roms (around 620MB zip).
[Xiaomi Redmi Note 3 Questions & Answers] cletusarrarr:
thanks for that , it seems the xiaomi.eu roms are based on the latest CHina beta with all the chinese stuff removed, waiting for my bootloader to be unlocked. this seems like the best bet to use on the phone.

http://xdaforums.com/redmi-note-3/how-to/xiaomi-eu-rom-discussion-thread-t3373714 head to this link for further details.
[Xiaomi Redmi Note 3 Questions & Answers] mr.loverlover:
Hmm, invalid link.

But anyway, I have a global stable based xiaomi.eu rom. And a theme app is a proof for that (no customize menu on global roms).
[Xiaomi Redmi Note 3 Questions & Answers] cletusarrarr:
click it , works for me, dont copy paste , what differences have u noticed on the eu roms ? some comparison of whats missing or so would be nice.

here is the direct link

http://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
[Xiaomi Redmi Note 3 Questions & Answers] mr.loverlover:
Here are the stable builds: https://www.androidfilehost.com/?w=files&flid=51314

I didn't notice too big difference. It's faster, leaves more free ram and has more international languages. Bloatware removed.
[Pixel C Android Development] followmsi:
Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !

Thanks for your understanding.

This thread will be used for the unified tegra-3.18 kernel only.

Twelve:

tegra-3.18_unified_dragon_kernel_12_v211213.zip

Eleven:

tegra-3.18_unified_dragon_kernel_11_v201218.zip

Ten:

tegra-3.18_unified_dragon_kernel_10_v201010.zip

Pie:

tegra-3.18_unified_dragon_kernel_p_v200310.zip

Oreo:

tegra-3.18_unified_dragon_kernel_o_v200310.zip

Changes/Features:

- Upstream to kernel version 3.18.140

- Various patches and security updates

- Added Wireguard support

- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)

- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)

- Added "fix cpu frequency limitation"

- etc.

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

The package contains an Image.fit kernel binary only - and no ramdisk part !

This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.

And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.

Sources:

https://github.com/followmsi/android_kernel_tegra

https://github.com/followmsi/lazyflasher/tree/followmsi-dragon

https://github.com/followmsi/AnyKernel2/tree/dragon

Download:

https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn

Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !

Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !

Enjoy :)
[Pixel C Android Development] dmitrygr:
flashed your system image

devices does not boot

flashed back to stock

boots

edit: further details

every boot just dumps me into recovery.
[Pixel C Android Development] followmsi:
Thanks for feedback .. no good news. :(

Sorry, I can not reproduce your problem.

Tested the system_vendor udapte.zip several times on my Pixel C.

No problem so far ...

You flashed the complete .zip via TWRP ?

What was your previous firmware level ?

Did you upgrade bootloader as well ?

What kernel do you have in use ?

EDIT:

Which Version of TWRP ?

Pls use xceed version for now.

The NYChitman1 version seems to have problems.

http://xdaforums.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183/page14
[Pixel C Android Development] NYCHitman1:
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.

Also, I find it interesting that you've created a development thread while you aren't actually developing anything.
[Pixel C Android Development] followmsi:
Thanks for the update.

Still like to test your version.

Ok, the version from here is recommended .. http://xdaforums.com/showpost.php?p=66557703&postcount=101

In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.

When do you re-release this version ?

You may open a new thread for your TWRP releases .. :)

Thanks a lot for all your work!
[Pixel C Android Development] followmsi:
New kernel released ... pls test :)

Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip

There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/

Cheers
[Pixel C Android Development] redukt:
Many thanks for your work :) The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
[Pixel C Android Development] followmsi:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.

https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F

Last changes .. 6 weeks ..

https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a

I am running the new kernel on latest M stock release .. MXC89F.

No problems so far .. really stable.

The kernel should run on all stock M releases for PixelC.

Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.

But the actual kernel should work as well ..it's a dragon kernel.

Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..

Give it a try .. it will not hurt. :)

Cheers
[Pixel C Android Development] nic.:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
[Pixel C Android Development] followmsi:
Sounds good .. have it running on Nexus 7 flo .. really like it. :)

MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.

But like SuperSU .. automatic chromeos image unpack and repack, if required at all.

It seems Tassadar is not around anymore .. not sure if he will come back.

Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..

Works fine :)

Are you able to port it to Pixel C ?

Thanks
[Pixel C Android Development] redukt:
Bootloop :)

Restored my Nandroid and device is up :)

DU is CM based and unfortunately incompatible :/
[Pixel C Android Development] nic.:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
[Pixel C Android Development] followmsi:
Thanks for the test .. :)

Restore DU boot.img and you are back to normal ..yep

I will unpack the DU boot.img and have short look .. just to check it. :)
[Pixel C Android Development] followmsi:
Sounds like a lot of work .. but if you have the right people involved ..

Maybe xceed or nychitman will know better how to "manage" the bootloader ..

As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****. :)

Right now I am happy to "manage" the layer above .. boot.img and recovery.img :)
[Pixel C Android Development] NYCHitman1:
What are you talking about? We're not CM based.

I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
[Pixel C Android Development] redukt:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
[Pixel C Android Development] followmsi:
You are right .. there also many fixed not relevant for dragon at all.

But it´s a fresh kernel .. upstream :)

I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.

[MENTION=1614476]redukt[/MENTION], please test this kernel again .. on DU :)

Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip

https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59

Thanks .. still bootloop ?
[Pixel C Android Development] followmsi:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip

https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59

Thanks !
[Pixel C Android Development] redukt:
!!! Device is booting!!! :)

Meh... forget to install SU lol.... Will have a look in kernel auditor :)

Many thanks :)

edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work! :)
[Pixel C Android Development] followmsi:
Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18

https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18

Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing. :)

As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.

We will see ...

Cheers
[Pixel C Android Development] NYCHitman1:
I've been one of the lucky ones with no issues ?
[Pixel C Android Development] followmsi:
Lucky you .. my one has Bluetooth issues only ;(
[Pixel C Android Development] Alxoom33:
Try your kernel. Just kidding. Unfortunately, it sounds that the Pixel C had some quality control problems. Can you exchange your's for a better working Pixel?
[Pixel C Android Development] followmsi:
Have seen some Bluetooth related stuff inside the kernel change logs - Google has made some changes to BT Driver, they made also some reverts of existing commits/changes .. etc.

Maybe there is a software based fix for this problem.

The issue is not killing me - WiFi problems would stress me much more.

At some point I may consider a replacement unit.

Maybe the next kernel will fix it :)
[Pixel C Android Development] Bless1:
Can you please let me know how you went about deleting non-English language keyboards? Sorry for off topic and noob question just trying to learn a little
[Pixel C Android Development] Alxoom33:
No problem. I used root explorer (you have to be rooted), went into System/apps enabled R/W and started deleting. There is also an app called Uninstall that you can use to debloat, or you can delete apps in TWRP. I just prefer using Root Explorer. Good luck!.

Just to add to my previous post, I was able to get Substratum to work and my pixel is now nicely themed. However, layers still doesn't work with the new Vendor partition.
[Pixel C Android Development] pjdick:
Could you explain how you were able to get Substratum to work? I am on Android N with this kernel (Chromium, not Stock or Tegra) and CAN get Layers to work (it just works), but NOT Substratum....
[Pixel C Android Development] Alxoom33:
I am using the new Tegea kernel. Neither Layers nor Substratum were working for me after I upgraded to 7.0 v. NRD90R where as Layers worked with N DP5. You are probably on DP5 so that s why Layers is working. I got Substratum to work in the app. You need to activate it. I just am not sure how, but it worked. Sorry, but I don't have any further explanation.
[Pixel C Android Development] rustak:
Weird issue -- when I downloaded Update.ZIP_PixelC_Ryu_NRD90R-system-vendor.zip via Chrome on my Pixel C, TWRP refused to flash it, saying that the zip file was corrupt. Other images worked fine, e.g. the TWRP update.

When downloaded on a laptop and pushed to the device, it flashed fine. The file sizes were identical, but the Chrome-downloaded one was definitely corrupt; pulling it to my laptop, unzip -v fails, and they're different files:

901c169ce46bf65c4a2fc1df69602e6f *good/Update.ZIP_PixelC_Ryu_NRD90R-system-vendor.zip

2f707ebb486c17e066864a9881f07b18 *bad/Update.ZIP_PixelC_Ryu_NRD90R-system-vendor.zip

Haven't tried downloading via Firefox on the device, will give that a try as well.
[Pixel C Android Development] pkelly517:
No need to bother trying. substratum will not work in its 'new and improved' mode in the stock ROM. The ROM does not include the needed OS commits.

substratum does work in legacy (Layers) mode, as a you've seen.
[Pixel C Android Development] followmsi:
Weird issue - indeed.

Did you download twice ? .. just to verify the Chrome issue.

Pls post your firefox results, if possible.

Cheers
[Pixel C Android Development] yolka:
is that usable for rooting my tab with NRD90R on it?

Thanks for you effort.

Is that zip usable for rooting my tab with NRD90R installed on it?

If yes, then I'd appreciate if you could point me to the detailed rooting guide, which would include the step of using your zip.

Just FYI, I have the bootloader unlocked already.

Regards,
[Pixel C Android Development] nigelhealy:
You just quoted the detailed guide!

You can either permanently install TWRP or just boot it as required. I'm assuming you want to go the TWRP install method.

Boot into bootloader. Plenty of ways to do this, this is an example way, go to system, about tablet, at the bottom is build number, press it many times til you are developer.Then system, developer, enable USB debugging. Then into your chosen computer which has ADB and FASTBOOT installed and type "adb devices", the tablet will ask for to grant access tick to approve. Then type "adb reboot bootloader". Or you can use key presses but you'll be wanting ADB and Fastboot for other reasons so this is a good debugging step.

fastboot flash recovery recovery.img (or whatever you called the TWRP image) then reboot into recovery (press power and volume down button til it comes into an options menu then select recovery).

Boot back into normal and then download and save the 3 zips: your kernel choice, the system+vendor, the supesu

boot back into recovery, then install the system+vendor zip, then install the kernel zip, then install supersu zip, then reboot system

The usual hardest part of all of this is getting a working ADB and Fastboot, device drivers etc. I run Ubuntu which does this easily but I do need to sudo fastboot as otherwise I dont get fastboot permissions.
[Pixel C Android Development] followmsi:
Thanks for the detailed guide .. On top some more information.

No need to install system-vendor.zip if you are on the same Android Version. (NRD90R)

If you have a boot.img with unmodified ramdisk, like stock boot.img, you just need to install SuperSu.zip only.

Pixel C is supported since version 2.72+.

When you have custom recovery installed you may have problems to install monthly OTA .. some guys are using flashfire or similar tools.

If you flash system-vendor.zip you bypass the OTA process and you can keep TWRP installed.

You can choose between stock or other kernels. (boot.img)

They just should match the Android Version and have unmodified stock ramdisk included - to let SuperSu do the work.

If SuperSu will detect already modified ramdisk the installer will complain - rooting should still work - but based on "old" ramdisk changes which can lead into other problems.

After each flash of a new boot.img you need to install SuperSu.zip afterwards - to "root" the unmodified ramdisk again.

As the rooting is "systemless" your System.img will not be modified.

All the supersu binaries are located on /data now.

Hope this helps ..
[Pixel C Android Development] yolka:
need some more details

Thanks for the guidance, but could you plz clarify it little more for me:

[*]fastboot flash recovery recovery.img (or whatever you called the TWRP image) then reboot into recovery (press power and volume down button til it comes into an options menu then select recovery).

Which one of the below TWRP images should I use?

TWRP_dragon_3.0.2-21 .img

TWRP_dragon_3.0.2-23.img

What these zip files are for?

Update.ZIP_TWRP_dragon_3.0.2-21.zip

Update.ZIP_TWRP_dragon_3.0.2-23.zip

[*]Boot back into normal and then download and save the 3 zips: your kernel choice, the system+vendor, the supesu

Which one of the below zip files should I use for kernel?

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NRD90R_v160906_followmsi.zip

Update.ZIP_PixelC_Ryu_NRD90R-kernel-dragon.zip

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD90R_v160907_followmsi.zip

What these img files are for?

kernel-chromeos-3.18_v160906_NRD90R_boot.img

kernel-tegra-3.18_v160907_NRD90R_boot.img
[Pixel C Android Development] followmsi:
Pls read the the first thread again.

All files are described.

In general .. .zip files should be installed via TWRP and .img files will be flashed (normally) via fastboot.

( Twrp could manage some kind of .img files too.)

If you go for Android 7, pls take twrp v23.

The kernel have different "flavours" .. but all are fitting your needs.

All have stock ramdisk included - for rooting.

Good luck !
[Pixel C Android Development] rustak:
I just redownloaded with Chrome, but on a different network and everything was fine. I have no idea what happened, unfortunately.

Either way -- I upgraded using your packages and to the tegra-3.18 kernel, and now I'm getting the spontaneous reboot a lot more frequently than before. I'll try the stock kernel and see if it makes a difference; I wish google was more forthcoming as to what the actual fix was (if any).
[Pixel C Android Development] yolka:
!!!Done!!!

Thanks a lot for your great work and cooperation!
[Pixel C Android Development] Termynat0r:
Which zips to I have to use flash to perfom an update without loosing root?

I'm running stock kernel and Pixel is beeing a pain with his update notification..
[Pixel C Android Development] followmsi:
http://xdaforums.com/showpost.php?p=68563190&postcount=167
[Pixel C Android Development] nigelhealy:
Yippee the last app which doesnt like N is updated so I can upgrade to N, I been sitting on M waiting. Of the 3 kernels, is there anyone who has tested all 3 and have an opinion?
[Pixel C Android Development] Alxoom33:
I'm using the latest [MENTION=5480152]followmsi[/MENTION] kernel, from Android 7.0 source. Working great. Xceed has not yet been updated, so I would wait on that one.
[Pixel C Android Development] DollarUsername:
Is there support for btrfs? I would like to use a compressed disk image for Linux Deploy but there doesn't appear to be btrfs support now.
[Pixel C Android Development] followmsi:
Both kernels are based on stock config - dragon_defconfig.

If it's not working now, it will not change by this kernel.

Maybe at some point I will make a "custom" kernel as well .. including stuff like btrfs, if possible.
[Pixel C Android Development] Alxoom33:
What if you collaborate with [MENTION=4684315]flar2[/MENTION] and port his EX 4.07 kernel to the dragon. He has no plans to make a Pixel C kernel so collaboration with him may be possible.

I use his kernel on my Nexus 6 running Android 7.0 DP5.
[Pixel C Android Development] followmsi:
Not sure if I will have the time AND the knowledge to "clone" the Elemental X kernel to Pixel C.

This is a lot of work!

It´s quite a different to make some kind of EX kernel or just enabling a few "missing" filesystems like btrfs :)
[Pixel C Android Development] followmsi:
Another month .. another release -> NRD91D

system-vendor:

Update.ZIP_PixelC_Ryu_NRD91D-system-vendor.zip

stock kernel:

Update.ZIP_PixelC_Ryu_NRD91D-kernel-dragon.zip

Seems to be the same bootloader as used for the final version .. bootloader-dragon-google_smaug.7900.27.0.img

Of course we have a "new" compiled 3.18 tegra kernel as well .. still no new sources from google :(

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD91D_v161004_followmsi.zip

kernel-tegra-3.18_v161004_NRD91D_boot.img

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_NRD91D-system-vendor.zip

4. Install Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD91D_v161004_followmsi.zip

5. Install SR1-SuperSU-v2.78-SR1-20160915123031.zip

6. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy the October release !
[Pixel C Android Development] m0ritz:
Can anyone describe to me what is happening in this thread? I do realize we are talking about kernels. And normally there is a post which explains the benefits of flashing those. But here I just don't know...

What is the benefit of flashing this kernel?

When you say here

https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/ for example that there are many changes... Will those changes come official to the Pixel C with updates?

Thank you for your help (I know the flashing part and how you do this stuff...)
[Pixel C Android Development] followmsi:
The stock kernel used to be quite old.

The purpose of this kernel is to use "latest" available google sources and stock ramdisk.

Pls have a look here ...

http://xdaforums.com/showpost.php?p=67464345&postcount=115

A good example of fresh sources - at this time.

Currently google is a little bit lazy in terms of Pixel C - it seems they are working on other Pixel´s right now :)

This is one part of the thread - the other part are the monthly Update.zip files.

Hope this helps to understand the purpose of this thread/kernel a little bit better ...

Cheers