yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
No idea about the current status of mounting vold based usb storage .. which file-systems are allowed and which not.

Did you try to use "StickMount" ? .. the app should help here - needs root access.

Yes, ext4 is part of the kernel .. required for android partitions too.
[Pixel C Android Development] followmsi:
Strange indeed .. if you install the boot.img of your current ROM and reboot (may install magisk as well)

What happens ?

Any tools or software which is manipulating ramdisk or changing sys values like kernel values .. ?

Did you try factory reset as well ?

Hope you will sort it out !

Cheers
[Pixel C Android Development] chob0:
I formatted before installing 14.1. After installation I did a wipe of the data, system, and cache before installing the most recent vendor and it still has me stuck in the google logo on boot. The OS works fine however moment I install the vendor it sticks me in a bootloop. The vendor in the gdrive and none of the recent vendors work and it keeps me stuck in bootloop. Even after wiping the data, system, and cache again after installing the vendor I get stuck. The same thing happens after installing 15.1 and a vendor.img.
[Pixel C Android Development] followmsi:
How do you install the vendor.img ?

There are no known issues with vendor.img .. maybe a warning message after boot, if you use old vendor.img only.

Flash vendor.img inside TWRP and choose vendor partition as target !

I will upload a new ROM soon .. maybe the last unofficial lineage-15.1 version ever ;)
[Pixel C Android Development] followmsi:
This ROM is based on "official" lineage-15.1 sources .. as last test before going official !

lineage-15.1-20180327-UNOFFICIAL-dragon.zip

Changes:

- Official lineage-15.1 sources

- FORCE ENCRYPTION is activated in this ROM - pls install Magisk to prevent encryption !

- The "old big" NavBar icons overlay is not part of this ROM - not yet.

- Pls use March vendor.img !

Pls use official opengapps !

Enjoy :p
[Pixel C Android Development] chob0:
I've been flashing the vendor through TWRP. I'm currently on TWRP 3.2 in case the latest recovery is a problem.

I was able to get things working however. After flashing 14.1 and vendor it put me in a bootloop. So I restarted to twrp and flashed 15.1 over the existing 14.1 and it got me out of the bootloop. Strange but I'm now running 15.1. I did notice however that my system is still encrypted but at this point I'm just glad I was able to get out of bootloop. Loving the ROM.
[Pixel C Android Development] Warell:
I think I was celebrating too soon. My Pixel got stuck in 300Mhz once again :(

I took a screenshot, lots of frequencies are not even used. It is or em 204-306 or deep sleep.

And the 21 minutes of glorious 1122Mhz I posted about.

I can try the boot.img, don´t know what can help.

I´m not using any ramdisk or changing sys / kernel values as far as I´m know.

To clarify, so far, what I did, in detail, is:

1) Once the Pixel started to feel strange and stuck in 300mhz, I downloaded the last Oreo image from google (ryu-opm1.171019.022.a1-factory-e5c762a1) and installed using flash-all.bat.

2) Problem not solved, so I decided to install Lineage. Booted in recovery, installed twrp-3.2.1-0-dragon.

3) Rebooted in TWRP, wiped system, cache, dalvik, data, Installed lineage-15.1-20180309-UNOFFICIAL-dragon

4) Installed vendor_OPM1.171019.022.A1_Mar-2018 from TWRP in the vendor partition.

5) Installed open_gapps-arm64-8.1-micro-20180322 from opengapps.org

6) Installed SuperSU-v2.82-201705271822 (I never used Magisk, is it any better? I did not tried it because of people talking about bootloops using it. You said to use Magisk 15.3, and I found 2 (15.3.1530 and 15.3.1531), because of this I never tried and used Super SU instead.

7) Rebooted into system, same problem. Reported here, got your feedback, so I repeted steps starting at 3, this time I did a factory reset, not just wipes and after flash SuperSu I flashed tegra-3.18_kernel_dragon_v180308_unicorn-xceed-followmsi-o

8) This time the tablet went to 1122, and I reported back.

9) Used it for about half a hour, gone to sleep, got it today just to see it stuck at 306 again.

Sorry for keep asking for your help, but I really can´t understand what´s going on.

Do you think flashing boot.img can help? I saw you just published another update, I want to try it out, but you said to install Magisk. I need to replace SuperSU with Magisk?

Thanks in advance!
[Pixel C Android Development] followmsi:
The vendor.img for 14.1 is from August 2017 - last year .. for lineage 15.1 you should use the latest one .. March 2018.

Official lineage versions do have force encryption .. unofficial versions do not forceencrypt.

Glad you sorted it out and able to boot into system ..

Cheers
[Pixel C Android Development] tebra:
Hello Followmsi,

I'm on your last unofficial build unrooted.

Do I need to install Magisk to install official build?

Do I need to reflash opengapps to install official build?

Thanks

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] followmsi:
All the changes have been approved .. Pixel C is an official Lineage-15.1 device now ! :D

The first build will be made on Monday . :good:

If you move from unofficial to official (or vice versa) you should (normally) wipe data before.

The signature keys are different and you will get plenty of strange errors if you do not change the keys.

To change the keys without factory reset - pls check below:

https://wiki.lineageos.org/signing_builds.html

Test-keys to official or vice versa

If you are moving from a test-keys build (eg an “unsigned” unofficial build) to an official LineageOS build, you can push the script to your device and run it from Android:

adb root # This requires an userdebug/eng build and ADB root access to be enabled
adb shell stop
adb push ./lineage/scripts/key-migration/migration.sh /data/local/tmp/migration.sh
adb shell chmod +x /data/local/tmp/migration.sh
adb shell sh /data/local/tmp/migration.sh official
adb reboot recovery
# Now install the official LineageOS install zip

Or run it from recovery:

# Ensure both /data and /system are mounted, then continue
adb push ./lineage/scripts/key-migration/migration.sh /data/local/tmp/migration.sh
adb shell chmod +x /data/local/tmp/migration.sh
adb shell /data/local/tmp/migration.sh official

If you are migrating from an official build to your own “unsigned” builds, you can run the script in the same way, but instead using the argument “unofficial” instead of “official”

On the lineage wiki there is TWRP flashable zip to do the same stuff .. https://blunden.se/migration

Good luck !
[Pixel C Android Development] followmsi:
Just switch to magisk 15.3 (1531) .. yes - later version are bootlooping on dragon.

If you still use SuperSU then take last 2.85 version.

Maybe you try without any rooting tools .. for testing.

Anyway .. Installing Magisk/SuperSU should not be related to your problem.

If you wipe system and data before ROM installation there should not be any "strange" stuff left.

If you overwrite boot.img you delete potential ramdisk modifications.. etc.

On the last graph you have sent the are 1% (1020) and 3% (1122) - it's still going over 306 above.

But not much ...

If you change governor inside kernel auditor for testing ?

Sorry, right now I can't help you better .. need to get more infos.
[Pixel C Android Development] wizzardsk:
Is it true that the latest Magisk causes boot loop?

It is very strange, when i reboot to recovery, it wants some password for decryption. It was not necessary on los 14, now i run los 15, data was encrypted all the time.

It also seems that hw keyboard does not work.
[Pixel C Android Development] followmsi:
Magisk issues have been reported.. Still on 15.3.. and no problems.

Are you using latest twrp 3.2.1?

Did hw keyboard work fine on cm-14.1?

We did switch blobs for the last 15.1 version.. Did you test previous 15.1 Rom too?

Did you move from official to unofficial version.. Keys changed?
[Pixel C Android Development] wizzardsk:
Keyboard works, it was my fault, not correctly paired.

I have TWRP 3.2.1.0, since LOS 14.1.

I moved from official LOS 14.1 to the latest unofficial LOS 15.1, full wipe, data was not formatted.

I am not sure if I understand what they keys means.
[Pixel C Android Development] followmsi:
If you not have wiped you need to change keys ..

There are quite a lof of encryption issues.. For some devices only.

A lot of other people don't have encryption issues.

Full disk encryption works only - no File based encryption anyway.

You may format data and start from scratch.. Or remove encryption completely.
[Pixel C Android Development] wizzardsk:
Ok, I may format the data, but is there any way to remove the encryption without issues? When LOS 15.1 will be official, it will have force encrypt by default, wont it?
[Pixel C Android Development] followmsi:
Yes.. Which you remove with magisk/supersu or the twrp flashable zips to just remove force encryption, if you don't want root.
[Pixel C Android Development] wizzardsk:
Ok, I formatted the data, rebooted to recovery and it asks me for a password again. What did I do wrong?
[Pixel C Android Development] Warell:
I flashed the boot.img (fastboot flash boot boot.img, right?), rebooted and nothing changed.

If you see this new screenshot I took just before flashing the boot.img, you can see the system never went back to higher frequencies. It is stuck in 306 all the time :(

I will wait for the official rom to come out and wipe everything and start fresh again.

If you can think anything else I must be missing, or if I can provide you any other info you need, I will be really appreciated, because I really, really don´t know what is wrong with this.

Thanks again!

EDIT: I just flashed Magisk to test, and it definitely changed something.

Now, I only have the 204mhz. All the other frequencies are unavailable (second screenshot).

Knowing this, it help to solve the problem?
[Pixel C Android Development] blue_algae:
I just flashed it with unofficial 15.1, it still lags like stock ROM but not as bad. Could you try docs app on the left side and chrome on the right side and then try scrolling on docs for 2 pages. Mine usually shows lag when I do that. TIA!
[Pixel C Android Development] wizzardsk:
Do I have to flash something more? What is that keys file for?
[Pixel C Android Development] followmsi:
Strange indeed :confused:

If you just reboot . you always get the same "values" ?

Are they changing on each reboot .. any pattern here ?

If your remove magisk and reboot several times .. always the same values ?

Or do they change with same kernel on each boot ?

Switch back to unified kernel .. also same values after each reboot ?

Try to go back to stock ROM and use the flash-all script to update bootloader and all partitions and full format again.

Did you check "dmesg" kernel logs .. and normal android logcat too ?

Is the tablet getting hot ?

Maybe overheating issue ?

Mabye some hardware issue ? :(

Sorry .. No idea whats going wrong with your dragon device.

Good luck !
[Pixel C Android Development] followmsi:
Pls install this kernel .. and test again !

tegra-3.18_kernel_dragon_v180308_unicorn-xceed-followmsi-o.zip

https://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591

Does it improve ?
[Pixel C Android Development] followmsi:
The keys files are for moving between official and unofficial builds.

Here you get more information ..

https://wiki.lineageos.org/signing_builds.html
[Pixel C Android Development] blue_algae:
It improved a lot! It still lags but not as bad before. I also noticed that if I turn on 'Disable HW overlays' on Developer Options, the lag goes away so I'm sure hardware-wise, the tablet can handle split screen no problem. I don't think though that turning this setting on is advisable.

Anyway, do I just install the flashable zip you gave to switch to official so I don't have to wait for Monday? And will I still get official updates if I am on this kernel?
[Pixel C Android Development] followmsi:
You will need to download and install official release anyway .. the fist time manually.

Prepare data partition to move to official ..

Pls read here .. https://xdaforums.com/showpost.php?p=76042630&postcount=409

And you will need to install the unified kernel manually, via TWRP, after each ROM update you install.

The ROM update will overwrite complete boot.img.

Let's see on Monday ..
[Pixel C Android Development] blue_algae:
Just to humor myself I decided to install stock nougat and saw no issues with split screen. Then I flashed LOS 14.1, no problems too. So it looks like it is a problem with with Oreo since both stock Oreo and unofficial LOS has it. I don't I will get a fix given that only security patches will be released. Oh well. Thanks anyway! Appreciate the help still.
[Pixel C Android Development] Agent.Orange:
Just a dumb question: I have choosen SuperSU for rooting after installing lineage-15.1-20180309 build and no experience with Magisk and I am a little bit afraid because of the caused bootlops of the newest version.

What will happen, if I just install your newest build from yesterday via TWRP over the old one? It will encrypt my Pixel C, right? So I have to enter a pin code?. Will I be locked out of my device? My smartphone is encrypted as well, but I had to select a pin code before.

Thank you for your answer.
[Pixel C Android Development] followmsi:
You just install SuperSu again - after ROM installation .. removes forceencryption too.
[Pixel C Android Development] wizzardsk:
Ok, I have run that commands according to http://xdaforums.com/showpost.php?p=76042630&postcount=409 using keys-migration-to.zip.

After reboot to recovery, I am not still able to access data partition because it asks me for a password. I dont understand it at all..
[Pixel C Android Development] followmsi:
The keys-migration-to.zip are zipped scripts to change keys for moving unofficial/official .. old version anyway.

Pls use current version from here...

https://github.com/LineageOS/scripts/tree/master/key-migration

But .. this has nothing to do with data encryption ! ;)

To remove data encryption you need to "format" and not wipe data inside TWRP.

Before you boot into system you need to install tools to prevent force encryption .. like magisk/SuperSu .. etc.

Cheers
[Pixel C Android Development] Warell:
I got the tablet today, thinking about restart it and see, but as soon as I unlocked the screen it felt more responsive.

Used it for some time and it is going all the bay back to 1530 Mhz. (screenshot attached) Just out of nowhere. I don´t even restarted it, the beast looks to be doing what it wants.

Don´t know if it can be heat. It don´t feel warm at hands, and CPU is aroud 36C and Battery 31.5C. Are this values too high?

I don´t know how to see "dmesg" kernel logs or logcat. Can you point me how to do it? I can get all the logs you want.

But your last sentence put me to think.. "No idea whats going wrong with your dragon device".. in fact, once I unlocked the bootloader, it showed me it´s not a dragon, its a smaug. I did a little research and all I could find is that there is no difference in dragon, smaug and ryu, but, maybe, there is no little difference in frequencies and the kernel can be trying to put some wrong values and it does not accept or something like this?

Thanks again and sorry for all the questions. :o
[Pixel C Android Development] wizzardsk:
All I want to do is to install supersu to get root on los15.1. To do that, I need to see the data partition in twrp to flash it or to use sideload. I formatted the data before, but after initial setup it was encrypted again and i dont know the password. I dont care that it is encrypted, i just want to see it in twrp without password like before on los 14.1.
[Pixel C Android Development] followmsi:
1. Boot into twrp

2. Format data in TWRP

3. Reboot into TWRP again.

4. Now data is not encrypted, copy SuperSu and ROM, gapps via adb onto /data .. or use USB stick right ..etc.

5. Install ROM, gapps and SuperSu as last step

6. Reboot system ..

Done

Happy Eastern ! ;)
[Pixel C Android Development] followmsi:
All the same .. smaug, dragon and ryu .. just different names.

Maybe it's still a hardware issue .. don't know.

If it continues this way you may replace the device completely.

Sorry .. can't help you better.
[Pixel C Android Development] wizzardsk:
Happy easter:) so i have to reinstall rom even though it is woking fine?

Ok, i installed the supersu after data format and twrp restart and root works. I had to install supersu also from playstore because there was no app installed. Just have problem with freeze/unfreeze of apps in link2sd.
[Pixel C Android Development] MrPhilo:
I am on AOSP, can I dirty flash? I heard that Lineage is based of AOS 8.1, so should be that much of a problem right?
[Pixel C Android Development] JLowe:
tested it again also with Sticknount with the LOS 14.1 from 2/18 and an ext4 sdcard isn't recognized.

On a Mi5 device with LOS 15.1 with same setup it works out of the box. So I conclude there's no ext4 support in the kernel or something is broken.

Maybe someone can test if the ext4 support in 15.1 is really working.
[Pixel C Android Development] followmsi:
This is device related .. mass-storage support was never activated for Pixel C.

Not even sure if the mass-storage support will be enough to make it running.

I made a quick Nougat test kernel and did enable mass-storage support .. the init.rc needs to be changed as well.

tegra-3.18_kernel_dragon_v180331_Nougat.zip

You may enter the code below as root in terminal app .. and test again .

mkdir /config/usb_gadget/g1/functions/mass_storage.0

For lineage-15.1 .. I will check usb mounting with ext4 and other file systems in the next time ..
[Pixel C Android Development] followmsi:
Just have a try .. wipe system and reinstall gapps too.

You still need to change the keys .. for going official !
[Pixel C Android Development] followmsi:
Pixel C moved from LineageOS 14.1 to LineageOS 15.1 !

The first official Oreo build ..

lineage-15.1-20180402-nightly-dragon-signed.zip

If you move between unofficial and official builds .. pls have a look here:

https://xdaforums.com/showpost.php?p=76042630&postcount=409

https://wiki.lineageos.org/signing_builds.html

Enjoy :p
[Pixel C Android Development] xda_jm:
Nice. Was about to ask :)

Any problems to expect when going from alst official 14.x release to 15.1 ?

Also - do you have instructions (detailed) on upgrading the device (like as usual Vendor Image to take, which google apps to use, what to take into account to prevent issues)

So far, I have downloaded the last dragon-archive from the 28.03.2018, The Vendor image from March 2018.

Asking, as I have some games and I don t want to loose my game-status/data (War Robots, it is a pain to level up ;))

Cheers - and Thx again for all your hard work on this ;)
[Pixel C Android Development] iestyn99:
Downloaded the official 15.1 from the LineageOS site and did a clean install. After the setup wizard it works fine (I think) but I keep getting a warning over a "Validation error" and that I "might be a victim of software counterfeiting". What?? Any more who encounter this?

Edit: According to Reddit this is a kind of april fools joke... funny?
[Pixel C Android Development] MrPhilo:
Thanks!

Does it use your kernel you provided before? Since it's official I can see it being stock lineage kernel etc
[Pixel C Android Development] followmsi:
Nothing special for Pixel C .. same like for every other device ..

1. Copy all required files into download folder or onto USB stick.

2. Boot into TWRP and verify you have latest 3.2.1 version.

3. Take backup of your /data partition !!!

4. Wipe system partition only !

5. Install new ROM and vendor.img afterwards

6. Install (open)gapps package - arm64 for 8.1 - same package size you used on cm-14.1

7. Install Magisk/SuperSU - recommended but optional

8. Clean cache/dalvik !

9. Reboot into system ..

And .. still running fine ? ;)
[Pixel C Android Development] followmsi:
It seems .. a fool's day joke.

Maybe also something like this ..

https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/

Or you just did not install the Oreo March vendor.img ...

All do have similar warnings ;)
[Pixel C Android Development] followmsi:
For all lineage and RR ROMs I use the "stock" lineage kernel .. which is done by me anyway ;)

Only the AOSP kernel is slightly different.

But you can install the "unified" kernel onto "official" lineage too ..

Hope this helps ..

Edit:

For explanation ..

Lineage and AOSP kernel are very close to Google stock sources, some little config and code changes.

The unified kernel is fully upstreamed and has more code inside.
[Pixel C Android Development] MrPhilo:
Thanks for the reply! Is there any difference between the kernels :)?
[Pixel C Android Development] followmsi:
I just did edit my post .. ;)

For explanation ..

Lineage and AOSP kernel are very close to Google stock sources, some little config and code changes.

The unified kernel is fully upstreamed and has more code inside.
[Pixel C Android Development] MrPhilo:
I came from AOSP Oreo and did the step above, I flashed the TWRP key signature first before flashing Lineage and all is good! Also flashed exceed kernel...

The ROM seems a lot smoother and there's more option to play with than the plain AOSP. Thanks a lot followmsi!

Only grips is that notification from Lineage, only way to remove it is to force stop the lineage setting. Anyway to get rid of it? I assume its an April fool thing :P
[Pixel C Android Development] Rox598:
just gonna flash lineage now since Google has stopped support

Just wanted to thank [MENTION=5480152]followmsi[/MENTION] for all he's done for the tablet, great work!

I see the official builds still have navigation bar issues (so small and dark mode you can't see them) is this due to be fixed in the next build?
[Pixel C Android Development] Mustkeg:
Official LineageOS 15.1 - awesome! :victory:

With Magisk 16, boot gets stuck at the Google logo.

With Magisk 15.3, LineageOS boots fine.
[Pixel C Android Development] followmsi:
Hopefully next build .. the navbar overlay will be merged in the next time.
[Pixel C Android Development] followmsi:
Yes .. known issue.

version 13.x were similar problem .. at some point it was working again.

Since 15.3 it seems to be broken again .. using 15.3 since a while did not test to update to latest 16.3.
[Pixel C Android Development] followmsi:
Like mentioned above .. not sure if it's a fools days joke.

Glad you enjoy the ROM ..

Cheers
[Pixel C Android Development] followmsi:
Did you test the Nougat kernel ?

Any changes ?
[Pixel C Android Development] wizzardsk:
Great that we have Lineage 15.1 official, thanks followmsi.

I just wonder if I have to reflash supersu after each update to prevent encryption or it will be preserved.
[Pixel C Android Development] tebra:
[MENTION=5480152]followmsi[/MENTION]

Thank you I'm now on last official build. I migrate from your unofficial without wipe data partition.

Everything works good.

I also get the notification "I "might be a victim of software counterfeiting".

Did you now why dragon don't have the "flash light" quick setting?

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] followmsi:
He .. you have to flash after each release.

Magisk has "survival" add-on script .. SuperSu does not.