yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
"I "might be a victim of software counterfeiting

LineaGenuine (both 15.1 and 14.1)

Our new tool allows you to feel more comfortable knowing whether you’re running a certified build. In case the device is caught running an uncertified OS, this tool will warn the user and some measures will be taken in order to guarantee you the device’s resources aren’t being misused.

If you want to disable the persistent notification, run this command from a root shell (such as adb root / recovery or terminal app)*setprop persist.lineage.nofool true*and reboot the device

You may have heard of the*recent changes*Google has done in order to block some OEMs to sell uncertified devices with GApps: we will discuss about the impacts this has on custom ROMs such as LineageOS in a dedicated post soon.

If you have already signed in your Google account, you don’t have to worry, don’t panic and don’t rush to register your device since it would change nothing for you.

https://lineageos.org/Changelog-17/

Perhaps we can add flash light tile .. will check.

EDIT .. which flashlight on pixel c ?
[Pixel C Android Development] tebra:
Thanks for your reply but did you know why the official build is detected as uncertified?
[Pixel C Android Development] xda_jm:
I actually used BeansGapps-Mini-7.1.x-20170610.zip (not opengaps). Will it make a difference? Or should I go over to openGapps?

Trying to find the right version as I write this :)

UPDATE: I actually went ahead and followed your instructions.

Took backup of data, formatted system, installed ROM - and TWRP UI was stuck. No more response.

adb worke though. So rebooted into recovery with "adb reboot rebcovery" and I was back in business...

Installed Vendor image, the open-gapps-mini - then Wiped cache/Dalvik and rebooted.

I usually skip rooting the device, as I don't always need it (rarely actually), hence leaving it as is.

The rebooted .... (with prayers ;) ) ...

Got a warning for the wrong Vendor Image version. Actually, on your download there is also the April version which is not working here. The March relesae is required.

After that, TWRP now is encrypted. So much I noticed. And I can't decrypt it.

Copied the March Vendor image to /tmp and flashed it.

So far - so good. Old apps are there.

---------- Post added at 11:40 AM ---------- Previous post was at 10:42 AM ----------

OK - here is what I noticed:

1. The UI is way smoother :)

2. All my apps etc. and desktop arrangement has been removed (Back to standard empty desktop)

3. The sdcard is now encrypted. Can't decrypt it. I have read that there is a script here in this thread to take care of this (I'll be looking for it, but if someone has the link, thx for pointing it out).

4. I get message of Counterfeiting blabla.

5. At first start, I also got a message telling me that because I'm not a regular user, they'll mine bitcoins on my device. Hopefully this is only an April joke. Nothing point to it actually ;)

A part from that, it all seems to run fine. will fine-tune all I had in there again ;) Will let you know if I notice anything else.

[MENTION=5480152]followmsi[/MENTION] Thx again! :)

BTW - where did you guys get your magisk 15.3 from?

There are so many links out there, and by default I trust no one I don't know ... :} So very difficult for me.
[Pixel C Android Development] frauhottelmann:
It's an April fools joke ?
[Pixel C Android Development] dafresh:
Any plan when we have big buttons back in official rom or is it save to use the modified apk on official lineage?
[Pixel C Android Development] tebra:
[MENTION=5480152]followmsi[/MENTION]

I'm now on last official build with encrypted data partition.

Rebooting in TWRP 3.2.1 ask me a password to decrypt data partition but failed with my 4 digit pin code.

Any help?

Thanks
[Pixel C Android Development] wizzardsk:
I was having the same prob with unofficial 15.1. Now i have unencrypted, but i think it will be the same after next update.
[Pixel C Android Development] xda_jm:
Actually - I think that if you encrypt and provide the password, you can use the provided password to decrypt it. This happens when you actively encrypt the device yourself.

This is how it works on my phone with Lineage OS 14.1 at this time.
[Pixel C Android Development] wizzardsk:
I never encrypted the device myself, it was always encrypted automatically without my intention. I never had any pin or anything else set.
[Pixel C Android Development] frauhottelmann:
Just go to the security settings and change your pin to something else. Agree to use it for start up as well. It should then be the pin that you can use within TWRP.
[Pixel C Android Development] tebra:
It works, thank you

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] wizzardsk:
I wonder why 14.1 did not have this problem and 15.1 has it, it means los 14.1 worked with encryption in twrp without asking for password.
[Pixel C Android Development] followmsi:
Are you using last year Nougat gapps ?

Why not .. if it's working fine for you.

Pls download magisk from here ..

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Pixel C Android Development] followmsi:
Like mentioned above .. should be possible to include into official too.

Maybe already next week Monday...
[Pixel C Android Development] followmsi:
Encryption was always an issue.. all discussed in the TWRP thread a few times.

Until last month the encryption still did work fine. .. this month also google stock ROM user seems to have issues.

The Pixel C TWRP grabs all the relevant Code from system partition .. fresh on each boot.

This way it catches most of the google changes .. and they do change security stuff all the time.

Again ..

File based encryption (fbe) does not work !

Standard full disk encryption (fde) works normally.

Most of the historic (fde) problems we're solved by the user.

The "default_password" for "automatic" encrypted devices is hardcoded in TWRP.

Should not have changed .. other users did use workarounds like mentioned by frauhottelmann above .. etc.

The official TWRP is based on lineage cm-14.1 .. should not be a problem, and was never a problem.

I did made a few test versions based on Oreo code .. still some BusyBox issues at this point.

But no rush here .. the underlying OS is not really relevant for TWRP.

If there are general problems since Google April updates .. the TWRP team will fix them soon, and we get new official TWRP version automatically.
[Pixel C Android Development] xda_jm:
heh. Thx for the update.

Thing is - at this time an update/upgrade to your next release will probably not work as twrp can't put the files on a temporary location for the upgrade to happen.

The other thing is, as this is the system only, it is not a problem to actually boot into twrp, on the password prompt for encryption hit cancel, from a computer copy over all required system files using adp, format the system partition and install the ROM magisk/SuperSU and the google-apps. The data-partition remains unharmed and should work as always :) Even worked for me from 14.1 -> 15.1 :D

Until they fix the encryption stuff :) I can wait ;)

PS: I noticed one thing on my Pixel C. When playing War Robots, sometimes the screenplay replays the same 1sec for 10 to 15 secs.

I don't know if it the game or the underlying drivers for the GPU or android 8.1.
[Pixel C Android Development] followmsi:
Have a try with the unified kernel .. there is a fix for gamer included.

Cheers
[Pixel C Android Development] redukt:
Made my day :laugh::laugh::laugh:
[Pixel C Android Development] followmsi:
For the "big" NavBar icons fans .. like me too. :)

https://github.com/LineageOS/androi...mmit/87e6f41ba7688b37773183aba534fe63fb2472b0

I hope there will be no discussions.

Included in the next build on Monday .. and you will need April vendor.img too.

Cheers
[Pixel C Android Development] ToldYouSo:
Magisk beta 16.3 confirmed working on latest official build.

Thanks for all the work you guys. I think the effort you have put into this for LOS - Pixel C support is more than Google ever invested in this tablet.
[Pixel C Android Development] xda_jm:
I will do that. Thx for the hint.

FYI - when setting a new PIN and telling Yes to allow bootup with the PIN only, reset the PWD also for TWRP.

Now the PIN decrypts the partitions in TWRP. Nice to know :)
[Pixel C Android Development] xda_jm:
Thx. Just tried. It indeed works better. it happens from time to time only, and not too long now :) Not completely fixed though.

Thx for the hint :)
[Pixel C Android Development] DJAverage:
This is a general problem with the Pixel C and Oreo.

There is an open issue at issuetracker dot google dot com. Search for "OpenGL suttering bug in Android 8.1"

Please go and star it and submit a bug report so that they'll (hopefully) fix it! Especially now that we're not getting Android P
[Pixel C Android Development] Rox598:
This persistent notification from April fools Day is really annoying, is there no way to remove it?
[Pixel C Android Development] followmsi:
If you want to disable the persistent notification, run this command from a root shell (such as adb root / recovery or terminal app) setprop persist.lineage.nofool true and reboot the device
[Pixel C Android Development] ToldYouSo:
I sometimes wake up my tablet from a screen off state and find my touch screen is unresponsive... I have to use the power button to turn off- and on again (not reboot, just screen off and on) and the touchinput works again.... Is this the same issue as the OpenGL stutter? I did not read anything about an unresponsive touch screen... Although the screen off and on-trick is the same fix I used for those horrible graphic stutters when still on the factory image....

Maybe it could be caused by magnets in my case?

---------- Post added at 15:54 ---------- Previous post was at 15:39 ----------

https://issuetracker.google.com/issues/71678283

or

https://issuetracker.google.com/issues/71522801 ?
[Pixel C Android Development] Rox598:
This has got to be the worst april fools they've done tbh
[Pixel C Android Development] ToldYouSo:
To elaborate... The only thing that works is pulling down the top menu with brightness settings etc. And then i can press something within that menu, but not outside of it. All other touch inputs are not working... really weird... def. not magnets in my case causing it... maybe related to the quick pulldown setting? Or a lockscreen issue?

---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------

Yes weird sense of humor indeed :P
[Pixel C Android Development] bigtreiber:
Lockscreen orientation

Hi there,

I've just installed LOS 15.1 on my Pixel C and what confuses me is, that the lockscreen orientation is always in landscape mode. After unlocking, screen rotation just works fine. But I didn't find any way to rotate the lockscreen.

Any suggestions?

bigtreiber
[Pixel C Android Development] followmsi:
Search settings for rotation settings .. click rotate lock screen.

Works fine for me ..

Cheers
[Pixel C Android Development] bigtreiber:
That solved it, thx
[Pixel C Android Development] bigtreiber:
WeatherProvider not working

Next question :) I've installed OpenWeatherMapWeatherProvider.apk from the Lineagos Extras section. But when trying to enable weather provider in clock it says: No weather provider installed.

Is there anything I have to enable?

cheers,

bigtreiber
[Pixel C Android Development] wizzardsk:
Seems that last update requires vendor update and play store does not load.
[Pixel C Android Development] xda_jm:
You can find that on followmsi's google drive.

First page of thread, last Entry under Downloads.

DOWNLOADS:

https://drive.google.com/drive/folde...TZmNWJoaU1iazg

---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------

Just a question to the others using Lineage 15.1.

In the last 24 hours my Pixel C rebooted twice (randomly).

Only happens when closed and doing nothing (IMHO, I make sure there are no apps running in background. Maybe I should make sure something runs in background).

I do know that this is an issue with this tablet since Android 6 (the very beginnings).

I had this happening from time to time with lineage 14.1, but never that often (once every 4 or 5 days).

Anyone else noticed this?
[Pixel C Android Development] ToldYouSo:
The Play store loads fine here

---------- Post added at 09:50 ---------- Previous post was at 09:47 ----------

Not noticed any reboots yet...

I do have another very annoying 'issue'. I can't for the life of me create app folders in the (Pixel) launcher. Dont know what i am doing wrong
[Pixel C Android Development] xda_jm:
Ah yes. It's a getting used to process.

I had that too. In fact, it is a very time sensitive thing, and you don't have to get the dragging app on top of the other app you want to create a folder with.

Get in from the side and as soon as a circle forms under the drop, drop the dragging app. It works, but kind of tricky :)
[Pixel C Android Development] ToldYouSo:
My gawd... My motor skills seem too retarded to be able to do this... I drop as soon as a circle forms but it refuses to make a folder. How quick a drop are we talking about? I've always had trouble creating folders but never as bad as this....
[Pixel C Android Development] xda_jm:
*lol* I have kids, and we are all games in the family. So - adapt or die ;)

It is tricky. Once you made it, you'll manage.

I think it is due to the UI being way smoother on LOS 15.1 that it became that difficult. I think it really is a matter of 50milli seconds you can drop it.

I take me roughly 10tryes to get on drop. Once a group is formed, it is easier to drop into that group BTW.
[Pixel C Android Development] ToldYouSo:
I know but even 1 folder seems impossible. I even slowed the animations x10 in the developer options. Which seemed like the best idea I had all week. But still.... No folder.... Thanks anyway for your input.
[Pixel C Android Development] followmsi:
No unexpected reboots since a very long time .. which Kernel are you using ?
[Pixel C Android Development] tebra:
I'm on last official build -> no reboot at all

[MENTION=5480152]followmsi[/MENTION]

Any news about "flash light" quick setting ?
[Pixel C Android Development] followmsi:
As edited above .. which flash light to enable for Pixel C ?

No reboot ?

Since last week there were no device changes except for fingerprint and the big navbsr icons.
[Pixel C Android Development] followmsi:
https://lineageos.org/An-April-Apology/
[Pixel C Android Development] tebra:
Sorry my fault, was sur that we have a light near the back camera on puxel c :(

About "no reboot" just said that my pixel c is stable
[Pixel C Android Development] bigtreiber:
Anybody got working weather providers with clock widget?
[Pixel C Android Development] ToldYouSo:
I think I found the setting that causes this issue. Having selected a pattern as lock screen. Under "screen lock settings" I have to turn "Directly show pattern view" off, otherwise I get the quoted issue.

Also after maybe 100 tries in creating folders, deleting the PIxel launcher apps (icons too) data, cache, also dalvik cache. I'm starting to think a bug is preventing me from creating folders in my Pixel launcher.... No idea where to start searching to fix the issue... Any tips are welcome!

I do see the shadow appear to indicate I want to create a folder. But when releasing the app it always just moves the icons instead of creating a folder.

---------- Post added at 08:21 ---------- Previous post was at 08:16 ----------

A very well put apology... Some jokes are just not funny and very misplaced.
[Pixel C Android Development] xda_jm:
The one provided with the last Update 15.1 April 9 2018. Didn't install your other kernel on that one (Was installed with the first 15.1 image :) )
[Pixel C Android Development] followmsi:
On both Kernels are no unexpected reboots .. last unexpected reboots were last year .. when we was playing with low memory killer.

There must be different reason in your case.
[Pixel C Android Development] xda_jm:
Well - is there something I can do, like activating Logging so I see what was the last thing that happened before the reboot?

Doing that on some linux systems in similar situations.

Do you by chance know how to activate it? The developer options give me too many options :}
[Pixel C Android Development] bigtreiber:
Sorry to bother again, but weather provides work on LOS14.1, not on 15.1?

Suggestions?
[Pixel C Android Development] xda_jm:
The only weather provider that works on my phone, Lineage OS 14.1 though, is the yahoo-weather. All the others fail.

On my Tablet/Pixel C with LOS 15.1 - none works.

---------- Post added at 03:31 PM ---------- Previous post was at 03:28 PM ----------

I actually removed some unneeded apps that were very intrusive (and locked down/no access to things and not allowed to run in background). So far no reboots.

So I guess there are some apps that don't behave well and make the system crash. All I can say so far. I have no proof though, as not reproducible. It seems stable now though.
[Pixel C Android Development] followmsi:
I use pixel launcher and get temperature next to the clock.

Did not change any settings ..

The weather provider from lineage seems to have problems on 15.1.

Found this one ..

https://www.reddit.com/r/LineageOS/comments/83yr54/lineageos_151_no_weather_provider/

Sorry .. No more infos here.

Will ask razorloves for more details next time ..

Cheers
[Pixel C Android Development] bigtreiber:
thx for the information, but Yahoo doesn't work either. It says: "no weather data provider installed"
[Pixel C Android Development] followmsi:
Did you test the one from the link as well ?
[Pixel C Android Development] bigtreiber:
Sorry, followed the link to late ;) Wunderground seems to work ...
[Pixel C Android Development] kurze12:
Nightly from 16.04. Bootloop...
[Pixel C Android Development] followmsi:
The ROM only .. or after Magisk installation ?

Tested 16.3 without problems.

If you install previous version it works again ?

Same install process ?
[Pixel C Android Development] kurze12:
supersu ..., even without supersu I have the bootloop. Version before goes again, my Nexus 5x also has problems, because magisk is no longer running.
[Pixel C Android Development] followmsi:
Hmmm .. not sure what happened here.

No device and kernel changes for dragon at all.

I hope it will be sorted out till next week release ..
[Pixel C Android Development] wizzardsk:
After the latest update it is starting very long...
[Pixel C Android Development] kurze12:
After 45 minutes I stopped.
[Pixel C Android Development] frauhottelmann:
Yes, same here. I flashed back to the previous one. Only gapps and su add-on...
[Pixel C Android Development] wizzardsk:
Me too. I was also trying to revert to stock image, but I needed newer fastboot and it did not work :)
[Pixel C Android Development] JLowe:
https://xdaforums.com/showthread.php?t=3545275
[Pixel C Android Development] bra1niac:
after full zip OTA I'm stuck on the boot animation. magisk 16.3. I restored the TWRP backup that was made immediately prior to the upgrade so I'm back on the previous nightly and working fine.
[Pixel C Android Development] followmsi:
Did it finally boot into system ?

Are you still on this build now ?

Can you pls create logs ... Logcat of the slow boot process.

Thanks
[Pixel C Android Development] followmsi:
In this case it's no Magisk/SuperSU issue.

You did use the new lineage 15.1 su add-on ?

https://mirrorbits.lineageos.org/su/addonsu-15.1-arm64-signed.zip

Some logs would be helpful .. logcat of the slow boot process.
[Pixel C Android Development] wizzardsk:
Nope, reverted to prev version.
[Pixel C Android Development] Lostprophet85:
Can't get Lineage 15.1 to work, please advise

Hi guys,

I have always loved CM and Lineage and have never had serious trouble (one or two bootloops in the last six years or so, but fortunately nothing I couldn't handle). I am trying to get my beloved Pixel C up to Lineage 15.1, but this time the upgrade is a desaster.

First I relied on the "How to upgrade from an official Lineage 14.1"-guide on the official website, but that was rather generic. So I just wiped the system partition, installed Lineage 15.1, OpenGapps and the root stuff from Lineage and wiped cache/Dalvik. I never got past the Google logo.

Second, I started googling and found this thread. I learned about flashing a vendor image and I followed this guide to the T:

The good news is, I get past the Google logo now. The bad news: the Lineage boot animation runs endlessly. I can access the device from TWRP (3.2.1.0) via adb and I can easily go back to Lineage 14.1. I have lost all my data in the process of trying to get it to work (stupid full disk encryption). So I don't have much to lose anymore (apart from bricking my tablet of course), I just want to get 15.1 + OpenGapps + root running on my device. Oh and I would like to disable the full disk encryption if it isn't too much of a hassle with regards to later OTA updates.

Can anyone tell me what to else to try?
[Pixel C Android Development] frauhottelmann:
Could be related to the unofficial su-addon that I had installed. I'll try without
[Pixel C Android Development] followmsi:
If you used latest official version you may have the same problem described above ..

Pls use the version form last week.

On first page you will find download link for unofficial April version too ..
[Pixel C Android Development] Lostprophet85:
Damn that was fast, thank you very much for your response. The first time I used an older version, but for my second attempt (the one including the vendor image), I indeed used the latest one. I'll give the older version a try and report back.
[Pixel C Android Development] followmsi:
Thanks .. as there were no device and kernel changes for last 10 days the release from this week "should" work the same way like the one from last week.

We need to find the root cause .. logs are welcome !

Will make a new build in the next time to test myself (unofficial - no difference except for the signing part of the ROM)
[Pixel C Android Development] frauhottelmann:
So, it's not related to the su-addon. It tries to boot, but never asks for the decryption password...

I had a encryption problem before, where I had set a 4*4 pattern. But I couldn't choose the 4*4 when it booted. Worked fine in TWRP.

---------- Post added at 09:24 PM ---------- Previous post was at 09:20 PM ----------

How would I get the logs at boot time?
[Pixel C Android Development] Lostprophet85:
It works! Something is definitely wrong with the current official nightly (20180416). I used the 20180409 one and it works beautifully. Thank you so much followmsi :)

On a side note: The whole vendor image thing kind of indicates that 15.1 will be the last Lineage version the Pixel C will get - as 8.1 is the last version it will get from Google. Is this assumption correct or is there still hope for a life after 15.1?
[Pixel C Android Development] followmsi:
You are encrypted .. make it even more complicated. ;)

If you see the lineage bootanimation have a try with ADB connection and logcat.

Anyway .. will check myself .. in the next time.

Hopefully more devices are affected and we find the root cause more quickly ...

Cheers
[Pixel C Android Development] followmsi:
Glad you enjoy the previous build.

Yep .. something seems to be wrong with current build.

15.1 is live since a few weeks and you are asking for P ? ;)

No idea right now .. depends on various points.

You are a bit too early.

But Yes - once Google made the last stock Oreo ROM for Pixel C you will not need to change vendor.img anymore.

Like Nougat ROMs are using the last Nougat vendor.img from last year.

Cheers