[ROM][UNOFFICIAL][6.0.1][02/28] OmniROM - Xperia Z1 Original Android Development

[ROM][UNOFFICIAL][6.0.1][02/28] OmniROM - Xperia Z1 Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
DOWNLOADS
ROM - 02/27/2015
Recovery
OLD (5.1.1)
ROM - 11/18/2015
TWRP (for Updated TA)
boot.img with TWRP
BUGS
Buggy camera
Test and report back
SOURCE CODE
Kernel
Device Tree
Rhine Board Tree
CREDIT
erikcas - Developing and building this ROM
jerpelea
OmniROM Dev team
FXP Dev team
etc
XDA:DevDB Information
OmniROM, ROM for the Sony Xperia Z1
Contributors
zhuoyang, erikcas
Source Code: https://github.com/erikcas?tab=repositories
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2015-11-20
Last Updated 2016-02-28

Reserved

beware, the camera is an (partly) opensource development preview solution.
That is the "bad" news.
The good news is that we never had an opensource solution before this. Except a hacky closed source solution.
It can only get better from here

erikcas said:
beware, the camera is an (partly) opensource development preview solution.
That is the "bad" news.
The good news is that we never had an opensource solution before this. Except a hacky closed source solution.
It can only get better from here
Click to expand...
Click to collapse
Guys. Your TWRP won't have brightness control, which results in overheating. You need to change max brightness from 4095 to 255 in rhine omniboardconfig. This was merged by Slimroms in August...

optimumpro said:
Guys. Your TWRP won't have brightness control, which results in overheating. You need to change max brightness from 4095 to 255 in rhine omniboardconfig. This was merged by Slimroms in August...
Click to expand...
Click to collapse
Thanx for reporting. I have no ability to test on honami, I will make this device specific instead of platform specific.
edit: see here and here
Thanx again

erikcas said:
Thanx for reporting. I have no ability to test on honami, I will make this device specific instead of platform specific.
Click to expand...
Click to collapse
The brightness value is the same for all rhine devices...
By the way: Does Omnirom have Layers?

optimumpro said:
The brightness value is the same for all rhine devices...
By the way: Does Omnirom have Layers?
Click to expand...
Click to collapse
tested 255 earlier on amami a while ago as I read about this issue before. And that was no good. I couldn't see anything on my screen in daylight. Besides from that, I have no heating issues in twrp. I.e. I leave twrp asap always, as I hate to carry around a device in recovery mode all day. It drops too many functionalities for my phone I use it for, like mobile networking.
So, as I am in twrp for not more then 5 minutes I think it is impossible for it to overheat. And I think the auto dimming of the screen after a minute of inactivity also prevents overheating
can you be specific about layers, it can mean multiple things. And I remember you asking this somewhere else before
edit ph***, the brightness remark made me review my notes I have to retest that on amami, it maybe a case of a screwup with yukon M2 here. Anyway, good to bring this to attention

erikcas said:
tested 255 earlier on amami a while ago as I read about this issue before. And that was no good. I couldn't see anything on my screen in daylight. Besides from that, I have no heating issues in twrp. I.e. I leave twrp asap always, as I hate to carry around a device in recovery mode all day. It drops too many functionalities for my phone I use it for, like mobile networking.
So, as I am in twrp for not more then 5 minutes I think it is impossible for it to overheat. And I think the auto dimming of the screen after a minute of inactivity also prevents overheating
can you be specific about layers, it can mean multiple things. And I remember you asking this somewhere else before
Click to expand...
Click to collapse
Layers as a theme engine. If I asked before, I would know the answer.

Could you build a clean aosp as well please?
Sent from my Xperia Z1 using XDA Forums

optimumpro said:
Layers as a theme engine. If I asked before, I would know the answer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/omni/development/planning-theme-t3096423
tadeas482 said:
Could you build a clean aosp as well please?
yes, will be done this weekend
Sent from my Xperia Z1 using XDA Forums
Click to expand...
Click to collapse

Just flashed and started Manual camera compatibility test app from playstore,and it showed that our device now supports all manual settings,even raw support.

Had it flashed, it felt awesomely smooth, fast s hell, booted in a few seconds... Camera was a said in op.. I just lost root and recovery so had to reflash kernel with recovery... Otherwise hell of a job with the ROM... thank you

what are the features included in this ROM?

caki25 said:
Had it flashed, it felt awesomely smooth, fast s hell, booted in a few seconds... Camera was a said in op.. I just lost root and recovery so had to reflash kernel with recovery... Otherwise hell of a job with the ROM... thank you
Click to expand...
Click to collapse
I'm hot booting recovery at the moment. What kernel did you use . I don't want a 3.4 kernel again .
Rashr. Is pushing recovery to fota partition but ROM/kernel does not seem able to use it .

Another 3.10 kernel that doesn't seem to work with my device. I must mention that I have an aftermarket display. It would be great if the ROM had a recovery, so that I could post the last kmesg. @erikcas

LSD DREAMER said:
I'm hot booting recovery at the moment. What kernel did you use . I don't want a 3.4 kernel again .
Rashr. Is pushing recovery to fota partition but ROM/kernel does not seem able to use it .
Click to expand...
Click to collapse
I changed the kernel to get restore a backup... But I will definitely try again later. Agreed with the recovery, I tried optimumpro's fota recovery, but was not able to boot into it.

drakonizer said:
Another 3.10 kernel that doesn't seem to work with my device. I must mention that I have an aftermarket display. It would be great if the ROM had a recovery, so that I could post the last kmesg. @erikcas
Click to expand...
Click to collapse
Can you upload a dmesg from stock?
As early as possible from boot.
If you have an aftermarket display that works on stock, the display has to be defined in the stock kernel to. I need to see how it is inited on stock rom. If it is I will find it and make it work (oops.. no guaranty offcourse, but will do my outmost)
edit: recovery will be up in 20 minutes in this post
edit 2: download honami TWRP here (should be working, but not able to test...)
Verstuurd vanaf mijn E6653 met Tapatalk

LSD DREAMER said:
I'm hot booting recovery at the moment. What kernel did you use . I don't want a 3.4 kernel again .
Rashr. Is pushing recovery to fota partition but ROM/kernel does not seem able to use it .
Click to expand...
Click to collapse
the kernel has not compiled the recovery "incompiled". I use updated TA partition for opendevices which allows a permanent recovery to be flashed to a "real" recovery partition, which you can enter (after updating TA and flash recovery) by powerup device by <voldown> + <power> keys at the same time when device is turned off.

wow really good rom. Just a few things:
- green videos were even on 5.1? I thought that it was caused by 6.0. Never mind, can you use new adreno binaries in next build (maybe there are some for 5.1, but it's worth try https://github.com/alviteri/vendor-sony-blobs/commit/11f24412c2e3b4b5531f2fa061fc2a0576933d2a )? Now I'm trying to push them to my phone and I'll see if it fix that
- some graphics glitches were present after first boot but they're gone, so I don't mind it
- camera is "somehow" working, but as OP mentions it isn't usable and it making weird sound on camera init (I should better not use the camera, I don't want to break it )
- superb freq scaling - my phone heats I think even less then on tweaked stock
edit: Also I used nut's ramdisk recovery and it's working link: http://nut.xperia-files.com/?ql=89140980648c1ad31bad3aa52f38245a2ef3c5a7
edit2: okay, do not flash this, in recovery there is no screen, it just vibrates and I can't restart my phone even with red button. (I have to wait till it die )
OK, @erikcas thank you

erikcas said:
Can you upload a dmesg from stock?
As early as possible from boot.
If you have an aftermarket display that works on stock, the display has to be defined in the stock kernel to. I need to see how it is inited on stock rom. If it is I will find it and make it work (oops.. no guaranty offcourse, but will do my outmost)
edit: recovery will be up in 20 minutes in this post
edit 2: download honami TWRP here (should be working, but not able to test...)
Verstuurd vanaf mijn E6653 met Tapatalk
Click to expand...
Click to collapse
THANK YOU!
I will post the dmesg as soon as possible.
As for the recovery, will it work in this ROM if I flash it to FOTA partition? I have a C6902 so there is no way I can get the updated bootloader for using an actual recovery partition
EDIT: dmesg attached. The adb shell command resulted in 0kb logs so I had to use Syslog, so that might have resulted in a few seconds of delay in capturing the log. Hope it helps!

Related

[RECOVERY]TWRP BETA 1

Hello There!
I am here with a good news and a bad news!
The good news is that I have sucessfully compiled TWRP recovery for our beloved Xperia M!
The bad news is that It is unstable, and I am not able to make it stable. I need help from some developers in order to make it stable.
Please note that this kernel bringup is only for CM11 FXP310.So, dont try it on other ROMs, as your may get into a serious problem after that.
Please bear with me, as I am a noob and will need a lot of help in making this stable for use!
Sources :
The TWRP sources can be found here : https://github.com/omnirom/android_bootable_recovery
The device tree of rebelos(contains commits for TWRP bringup, thanks to him for letting me use the tree) : https://github.com/rebelos/android_device_sony_nicki
The Kernel sources used : https://github.com/freexperia/android_Kernel_sony_msm8x27
Working /Not working
Working :
Normal Touch
Navigation
And Basic operations
Not - Working
Some glitches (sometimes) [that is, the half screen problem]
Screenshots(again, thanks to Bonoboo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
New flashable zip(thanks to Bonoboo) : https://www.mediafire.com/?gg84xysk8w64fwc
OLD[not recommended for use] :
boot.img
recovery.img ( I am having problems installing this, via fastboot. Use boot.img)
Changelogs
16-03-2014
Initial Release
17-03-2014
fixed up the bugs in main ROM. i.e, the wifi and RIL bugs.
Credits :
PecanCM - For sources
FXP, for supporting this device officially
rebelos for allowing me to use his updated commits in device tree. His device tree can be found on his github.
Bonoboo for giving the idea of packing the ramdisk(the partition with recovery and the boot.img) and for packing it up for me!
A note : I need help from you all to achieve this task Please help me up.
XDA:DevDB Information
[RECOVERY] TWRP, a Tool/Utility for the Sony Xperia M
Contributors
PixCM
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2014-03-17
Created 2014-03-16
Last Updated 2014-03-18

lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues

rebelos said:
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
Click to expand...
Click to collapse
Thank You soo much Will compile and post in an hour or so! Got to do something else at the moment
Tried.. But they didnt help :/ Same bugs!

Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off

Best Recovery Shown up!
TWRP just the best recovery ever... my fav.
hope this can be fixed soon... thanks for the good job

Good work bro...
Sent from my C1905 using XDA Premium 4 mobile app

Thanks mate for TWRP recovery! Always used this on my GT-I9100
Wating for an update
Sent from my C1905 using Tapatalk

Bonoboo said:
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
About screenshots.
Please hide them under spoiler – thread very lagre with them now.
Here flashable ZIP with original FXP310 kernel and this recovery.
Click to expand...
Click to collapse
Thanks dude! I will give you another build, check if the mount is working in this one!
Check your PM.

SUM ONE SAY TWRPDDDDDD goddamn, i want try it, but after the bug like wifi-RIL etc fixed

PixCM said:
Thanks dude! I will give you another build, check if the mount is working in this one! .
Click to expand...
Click to collapse
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Richardsentosa said:
i want try it, but after the bug like wifi-RIL etc fixed
Click to expand...
Click to collapse
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).

Bonoboo said:
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Click to expand...
Click to collapse
but now i using HellKat .-.

Updated
Updated OP with new build.
Download : https://www.mediafire.com/?gg84xysk8w64fwc
Special thanks to @Bonoboo for this

@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.

Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.

PixCM said:
I will release it in both the forms.
Click to expand...
Click to collapse
Yes, this will be nice and more flexible: someone can manually add recovery in beloved kernel and CM11 users can directly flash it.
PixCM said:
And, will you become my tester?
Click to expand...
Click to collapse
Recovery – yes, but not ROM, sorry.

PixCM said:
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
Click to expand...
Click to collapse
OmniROM with TWRP recovery is brilliant mate! Hope you will release it
Sent from my C1905 using Tapatalk

a new build? i will try it (if i flashed the FXP CM11)

Richardsentosa said:
a new build?
Click to expand...
Click to collapse
Yep, CM11 FXP311 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.

Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
+1 lol... you just wrote what i want to...
now it's being clear...
coz i need to replace the whole cwm from every Roms i've downloaded... yeah... keep it rolling dude :good:

CM11 FXP312 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.

[ROM][4.4.4][UNOFFICIAL] CyanogenMod 11.0 [R30, 2015-11-14]

Bug reports:
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Known bugs:
Bluetooth doesn't properly work with some devices. If you're affected, flash THIS ZIP in recovery.
Frequently Asked Questions:
Q) Where are Developer options and Performance settings?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I set 3G only network mode?
A) Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) Why is cpu min freq raising to 1190MHz?
A) It's "touch boost", cpu min freq increases when you touch the screen to give a better response. When you don't touch the screen for a couple of seconds, cpu min freq goes back to 300MHz.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. Reboot.

KitKat bootloader/modem files
This zip contains the bootloader and modem files from latest stable international release (MIUI7 V7.0.5.0 KitKat). I made it so users don't have to download and install the official zip, which also includes the rom. It's a flashable zip, so just install it from recovery and reboot (no wipes required).
Firmware 7.0.5.0: https://www.androidfilehost.com/?fid=24052804347850305

THX to developers work.!
Deleted the nonsense.

pgreed said:
The developer of the CM 11 for Redmi 1s is Kra1o5. Because him is present on the forum you have no right to post in the orig-dev section. I will report that.
Click to expand...
Click to collapse
You should've asked first. There are two developers in armani-dev, you know that. Well, I'm the other one. Check this:
https://github.com/armani-dev/android_device_xiaomi_armani/wiki
http://forum.xda-developers.com/showpost.php?p=56107913&postcount=11

does this kernel source really work?? i mean cause no cm11 rom has dev's version of kernel ! instead they all have xiaomi's stock kernel??
https://github.com/armani-dev/android_kernel_xiaomi_armani.git

ateeq72 said:
does this kernel source really work?? i mean cause no cm11 rom has dev's version of kernel ! instead they all have xiaomi's stock kernel??
https://github.com/armani-dev/android_kernel_xiaomi_armani.git
Click to expand...
Click to collapse
We use that kernel source for the headers, they are needed at build time. But for now we have to use stock kernel (latest version available). Still waiting that Xiaomi releases the kernel source....
Edit: New build up, 20141018 (a.k.a. R7).

jsevi83 said:
We use that kernel source for the headers, they are needed at build time. But for now we have to use stock kernel (latest version available). Still waiting that Xiaomi releases the kernel source....
Edit: New build up, 20141018 (a.k.a. R7).
Click to expand...
Click to collapse
Thanks!! Awesome ! Downloading....... :highfive: :highfive:
Lol.. i compilied a kernel using these Sources! and was gonna flash it to my phone!!

@ jsevi83 a.k.a fefifofum. (orig-dev) thank you for attending here, thank you for bringing to our devices cm11. and don't forget to thank you also to @ Kra1o5 (orig-dev)
I like your work...
#Still waiting that Xiaomi releases the kernel source
sorry my bad english.

jsevi83 said:
You should've asked first. There are two developers in armani-dev, you know that. Well, I'm the other one. Check this:
https://github.com/armani-dev/android_device_xiaomi_armani/wiki
http://forum.xda-developers.com/showpost.php?p=56107913&postcount=11
Click to expand...
Click to collapse
My complete apologizes but I didn't found your name before listed on the CM. I did a regrettable thing. Sorry and best wishes.
Now that is 2 developers is a hope that one of you can be able to modify the kernel adding more governor, voltage selector, optimize the screen consumption .... and dreaming
Back to reality why you can't use the XOLO q1100 kernel to modify the redmi?

Hi, I want to ask, is it OTA (CM Updater) supported? Or everytime we'll have to download and flash the whole ROM? And if its not, why don't you @jsevi83 add this project to an automated build server like Jenkins, It'll help users to get latest builds easily and the devs to solve the bugs fast. And what's the Gerrit Instance link (If you have one)? And I wanna know about the bugs in the ROM, is everything is working? SIM2 RIL, Data everything? Android One Devices will soon taste Official CyanogenMod support as stated by the developer. Our hardware is a bit better than A1, can we too look forward to have a Official CM support? Please do reply.
ThankYou

Really great ROM, thanks mates

We really appreciate reports about if Miracast / Wifi Display works or not for you guys.
Greetings

Kra1o5 said:
We really appreciate reports about if Miracast / Wifi Display works or not for you guys.
Greetings
Click to expand...
Click to collapse
Kra1o5, i'll ask some users about logs of it, greetings

Thanks for the wonderful ROM.
Dear Developer,
Thanks for bringing such a wonderful ROM for our device. I have been using it for quite sometimes now. And I never looked back after installing CM11. Having said just wanted to inform few bugs which I have been facing.
Proximity: The After a long call, and when you want to hang up the phone, when you pull the phone from your ear, it doesn't not wake. You have press power button to switch on or wake up the screen. What I am saying is that long hours mean something like more that half and hour talk on the phone. It does wake up when the other person hang up his phone.
UI Crashed: This usually happens when you try to change the wallpaper. But I know for sure, it happens only when you try to change the default wallpaper to something of your own choice. You can change it but occasionally or randomly , the ui crashed report pop up will show up and it will go the imersive mode and will start the ui from the lockscreen. If i don't change the wallpaper then it's cool.
Thanks

Hello dev,
thanks for bringing awesome rom for this device.
i'd like to ask about this glitch, because this problem exist since R1 release.
which one carrier name for sim card 1 isn't displayed correctly.

Sometimes to wake up the phone, you have to press the button several times 3-5 times
Sent from my HM 1S using xda premium

In call touches are still present - screen react on swipe down and afterwards you can touch anything from notifications up to buttons in quick settings.
Issue is easy to reproduce - call number, which don't pick up (SIM2), put one finger on proximity and with other swipe down from upper corner. Tap on screen...
Till now, I found 2 workarounds:
1. Call (pick up call), press power button. (this is easy to forget)
2. Use app ProximityScreenOff. It works perfectly, but messes with proximity sensor and sometimes lock screen don't start after pressing power button.
HM1S CM11 R7
---------- Post added at 10:37 AM ---------- Previous post was at 10:27 AM ----------
Benyegh said:
Sometimes to wake up the phone, you have to press the button several times 3-5 times
Sent from my HM 1S using xda premium
Click to expand...
Click to collapse
It's known issue. Go to Settings - Display & lights - uncheck Prevent accidental wake-up.
After some time you can check it back and it will work as intended.
HM1S CM11 R7

tried screen mirroring with sony w700b ,both tv and phone detected each other,but in the end tv showed device connection failed while the phone showed connected :/( when i first tried the tv was stuck at showing connecting to device , while the phone showed connecting and then reset back to the original prompt ,this was the case when until i accidentally locked the screen while connecting and then it started showing the error mentioned above)
i couldnt test much, as i had to return the phone ,its my sisters, so had to reflash to stock, so no log cat :/

Benyegh said:
Sometimes to wake up the phone, you have to press the button several times 3-5 times
Sent from my HM 1S using xda premium
Click to expand...
Click to collapse
Uncheck "Prevent accidental wake-up" under Display & lights settings.

[ROM][UNOFFICIAL][6.0.1] crDroid [12/21]

OFFICIAL VERSION HERE : http://forum.xda-developers.com/xperia-z1/orig-development/rom-crdroid-android-t3280304
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
DOWNLOADS
12/25/2015
Not Working
Camera
Test and report back
SOURCE CODE
Kernel
Device Tree
Rhine Board Tree
crDroid
CREDIT
davidteri91
erikcas
jerpelea
crDroid Dev team
FXP Dev team
etc
XDA:DevDB Information
crDroid, ROM for the Sony Xperia Z1
Contributors
zhuoyang
Source Code: https://github.com/crdroidandroid
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2015-12-20
Last Updated 2015-12-29

Recovery
NOTE: For build after 12/25 only (build before 12/25 untested)
CyanogenMod Recovery - Download
How to flash (using fastboot):
Code:
fastboot flash recovery recovery.img
How to boot into recovery :
Press power button once (don't hold) when LED lights up on the Sony screen.

Should google gapps? Does have root? Internal and external memory work?
Sorry for bad Englisch!

I install rom from TWRP and phone not turn on... In .zip in build prop I read: ro.build.description=C6903-user 5.0.2 14.5.A.0.270 3750474323 release-keys
This is not Android 6.

opengapps doesn't work , used those instead
http://www.devfiles.co/download/m4Er5IlQ/gapps-600-base-20151016-1-signed.zip
had to set permission on my own , but playstore keeps on fc

aleksandar9999a said:
I install rom from TWRP and phone not turn on... In .zip in build prop I read: ro.build.description=C6903-user 5.0.2 14.5.A.0.270 3750474323 release-keys
This is not Android 6.
Click to expand...
Click to collapse
Here's a prove

solved said:
opengapps doesn't work , used those instead
http://www.devfiles.co/download/m4Er5IlQ/gapps-600-base-20151016-1-signed.zip
had to set permission on my own , but playstore keeps on fc
Click to expand...
Click to collapse
Hmm strange ... I do use opengapps myself , it works perfectly
Did you wipe everything (including /system) before you flash to this ROM ?

aleksandar9999a said:
Should google gapps? Does have root? Internal and external memory work?
Sorry for bad Englisch!
Click to expand...
Click to collapse
Yes , you should install gapps, Root can be enabled in development settings.
Both Internal and external storage works !

Okay, this ROM is really good. Just a few things and it will be perfect:
- no built-in recovery (I know I should use new bootloader but I don't know if there's any way how can I "downgrade" it back if I want to)
- Mi Pistons headphones are still buggy - you have to press all buttons to get it recognized
- in YouTube app when you use you phone in landscape and minimize some video (browsing other videos when the previous one is still playing) you see some graphical artefacts in right upper corner. Above multitasking button.
- and of course camera but that's known bug
edit : there are more glitches - see screenshot in attachments

I try again to install rom and it is work. I don't know why first time not work. I install from philz recovery. I have some questions. If you port camera from other rom, it will work? Before I was install cm12.1 and view that on first and second boot camera was work, but after this it isn't work. This is similar problem. The problem may be in framework.jar.

SuperLamic said:
Okay, this ROM is really good. Just a few things and it will be perfect:
- no built-in recovery (I know I should use new bootloader but I don't know if there's any way how can I "downgrade" it back if I want to)
- Mi Pistons headphones are still buggy - you have to press all buttons to get it recognized
- in YouTube app when you use you phone in landscape and minimize some video (browsing other videos when the previous one is still playing) you see some graphical artefacts in right upper corner. Above multitasking button.
- and of course camera but that's known bug
edit : there are more glitches - see screenshot in attachments
Click to expand...
Click to collapse
There's actually boot to recovery implementation in kernel but it seems to be not working. Will have to investigate that later on.
The graphical glitches seems to be cyanogenmod bug (crDroid is based on cm).

aleksandar9999a said:
I try again to install rom and it is work. I don't know why first time not work. I install from philz recovery. I have some questions. If you port camera from other rom, it will work? Before I was install cm12.1 and view that on first and second boot camera was work, but after this it isn't work. This is similar problem. The problem may be in framework.jar.
Click to expand...
Click to collapse
Unfortunately the problem is not that simple.
Camera just doesn't work yet in marshmallow.
We'll have to wait for Sony to release camera for marshmallow or someone else to get it working.

I try to merge memory, but it not work. It is possible that I'm wrong thing.

New build released.
https://www.androidfilehost.com/?fid=24338798368260209
In this build , proximity sensor is fixed.
Complete changelog available at Settings > About Phone > About crDroid > Changelog

Pls dear developer if possible can twrp be implemented in the kernel please??

gauravbhakuni90 said:
Pls dear developer if possible can twrp be implemented in the kernel please??
Click to expand...
Click to collapse
Unfortunately this would take some time. I just can't figure out yet what's wrong with the boot to recovery implementation.
For now , your best bet is updating TA with recovery mode and flash TWRP
or you can hotboot any kernel with recovery using "fastboot boot boot.img"

When phone is turn off and you plug charger, screen is light and then charger screen will restart and screen remaints lit. After 2 or 3 restarts the charger screen, phone will turn on and after this it will turn off (or not turn off someone) and situation will repeat.
Sorry for bad Englisch. I hope you understand me.

zhuoyang said:
Unfortunately this would take some time. I just can't figure out yet what's wrong with the boot to recovery implementation.
For now , your best bet is updating TA with recovery mode and flash TWRP
or you can hotboot any kernel with recovery using "fastboot boot boot.img"
Click to expand...
Click to collapse
Hi,
I tried to update my ta, but there are only generic softwares (I flashed .368) and no ta update - in emma. Do you know what am I doing wrong? because it's really wierd to boot another kernel everytime I want to go to recovery.

SuperLamic said:
Hi,
I tried to update my ta, but there are only generic softwares (I flashed .368) and no ta update - in emma. Do you know what am I doing wrong? because it's really wierd to boot another kernel everytime I want to go to recovery.
Click to expand...
Click to collapse
did you copy customization.ini to emma installation folder ?

zhuoyang said:
did you copy customization.ini to emma installation folder ?
Click to expand...
Click to collapse
yes, I wouldn't be able to run it if I didn't
edit: can I use the recovery you posted before like fota recovery? because fota recovery works, you only must have recovery built with 3.10 kernel otherwise you have no display.

[ROM][8.1.0][OFFICIAL] ⚛ CarbonROM (Noct) Weeklies | Sony Xperia Z1 ⚛

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Credits:
Huge thanks to everyone below, without whom this would have not been possible.
* rcstar6696 (and everyone else who helped with the shinano bring up - these guys are the best)
* SpiritCroc
* Myself5
* The entire CarbonROM team
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z1
Contributors
drakonizer
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP + CAF
Version Information
Status: Alpha
Created 2017-12-25
Last Updated 2018-05-22

CHANGELOGS:
All changes can be tracked here:
https://blog.carbonrom.org/changelog
You can find the changelog prior to official builds below.
Official Build:
* Fixed Video Recording
* Improved RIL for C6903 devices
14/04/2018:
* Fixed Camera
* Fixed RIL and mobile data (on C6902 at least)
* Enforcing SELinux + user build
* Fixed Bluetooth
23/01/2018:
* Fixed audio
* Fixed thermanager
24/12/2017:
Initial Release
BUGS:
* Connecting to data for C6902 devices is buggy (read FAQ).
* NFC may or may not be broken (I cannot test it as my device does not have the NFC plate).
FAQs (Please read before posting questions):
Q: Does the ROM support OMS and theming with Substratum?
A: Yes it does! Simply enable "Allow untrusted overlays" from Settings -> CarbonFibers -> Privacy and Security and follow the instructions that follow.
Q: Does the ROM work on C6902 as well?
A: Yes, but you will face a few issues while trying to connect to mobile data. Apparently the way to make it work is by going to *#*#4636#*#* -> Phone Info, change the network mode to WCDMA only, and turn on and turn off airplane mode.
Q: Is the ROM rooted by default?
A: No, please flash your favorite root solution after installing the ROM.
Q: Do I need to make a factory reset before installing this ROM?
A: If you're moving from cr-5.1 official builds to cr-6.1 builds, then a factory reset is recommended. Some have been able to dirty flash their way from cr-5.1 to cr-6.1, but before trying that, make sure you have a backup, in case you're caught in a bootloop. Clean install is ALWAYS recommended. If you face any issues after dirty flashing, clean flash first and see if it's persistent and only then report the bug.
Q: SafetyNet?
A: Sure, if you use Magisk and enable Magisk hide.

Reserved

Nice!
Merry Christmas :victory:

Thanks for sharing carbon rom oreo, I will download and let you know whether audio and nfc work
---------- Post added at 03:41 PM ---------- Previous post was at 03:23 PM ----------
Unable to flash on latest TWRP, any ideas how to fix?
Coming from CarbonROM nougat, i already done wipe /data /system /dalvik-cache /cache
https://drive.google.com/open?id=1fVGP6Be2u5j7T8lpPkeuF_mXmQXxIw6_

miXXed404 said:
Thanks for sharing carbon rom oreo, I will download and let you know whether audio and nfc work
---------- Post added at 03:41 PM ---------- Previous post was at 03:23 PM ----------
Unable to flash on latest TWRP, any ideas how to fix?
Coming from CarbonROM nougat, i already done wipe /data /system /dalvik-cache /cache
https://drive.google.com/open?id=1fVGP6Be2u5j7T8lpPkeuF_mXmQXxIw6_
Click to expand...
Click to collapse
Try to install advanced kernel img via fastboot. Then reboot. In the kernel is twrp 3.1 included. Then you're able to boot into that recovery. Wipe all and try again to flash

MIcHiJK said:
Try to install advanced kernel img via fastboot. Then reboot. In the kernel is twrp 3.1 included. Then you're able to boot into that recovery. Wipe all and try again to flash
Click to expand...
Click to collapse
same issue

miXXed404 said:
same issue
Click to expand...
Click to collapse
Okay strange. When nothing helps try to start from the bottom and go back to stock. I will also test this rom later to check, if it's working on my third party screen.

Reflashing stock, flashing twrp again doesn't help, still same issue, something is wrong with carbon rom oreo zip

@miXXed404 update your recovery in this version https://androidfilehost.com/?fid=745425885120742869
https://forum.xda-developers.com/showthread.php?t=2522762
in any case follow the XDA link to resolve the error!
Merry Christmas!

Hansars said:
@miXXed404 update your recovery in this version https://androidfilehost.com/?fid=745425885120742869
https://forum.xda-developers.com/showthread.php?t=2522762
in any case follow the XDA link to resolve the error!
Merry Christmas!
Click to expand...
Click to collapse
Flashing recovery that you provided does not help, still same issue persist, also there is no lines in updater-script thats checking for specific device

thankyou so much....

Nevermind,somehow i managed to flash it,first impressions.. working better than nougat, at first boot up it heated up a lot, i can't enable NFC in settings, so i can't even test it, battery is draining pretty quick, gapps is working, audio is not working , i'm gonna use it for few days, maybe i will find more bugs.. and please fix thermal in this rom, 81c cpu 44 battery and still all cores is enabled on max frequency 2150mhz

miXXed404 said:
Nevermind,somehow i managed to flash it,first impressions.. working better than nougat, at first boot up it heated up a lot, i can't enable NFC in settings, so i can't even test it, battery is draining pretty quick, gapps is working, audio is not working , i'm gonna use it for few days, maybe i will find more bugs.. and please fix thermal in this rom, 81c cpu 44 battery and still all cores is enabled on max frequency 2150mhz
Click to expand...
Click to collapse
I have no issues of battery draining on my end. Nor did I face heating issues. My phone went to deep sleep and drained less than 1% an hour. Maybe you should just let it settle down for a few days and see if it helps.
If not, maybe it's me not using a SIM card or gapps giving me a better experience.

drakonizer said:
I have no issues of battery draining on my end. Nor did I face heating issues. My phone went to deep sleep and drained less than 1% an hour. Maybe you should just let it settle down for a few days and see if it helps.
If not, maybe it's me not using a SIM card or gapps giving me a better experience.
Click to expand...
Click to collapse
Really? no heating issues? try use 100% of cpu and it should throttle down frequency when it heats up, but it doesn't doing that
i'm only connected to wi-fi and charging, brightness set to 0% no apps in background.... no problems with heating? look at this
https://drive.google.com/open?id=1PMnMLuNsunStZV_Wd-AKXj8uR3FrOGCV

ΤΗΑΝΚ YOU! Merry Christmas!

miXXed404 said:
Flashing recovery that you provided does not help, still same issue persist, also there is no lines in updater-script thats checking for specific device
Click to expand...
Click to collapse
good morning, I saw that you have solved, I still do not flash because of too many bugs and the bug that is present in addition to the other bugs! thanks to the developer for the work done! @drakonizer

o be an alpha, the rom is stable.
some things do not work:
- without audio in calls and player
- root can not be activated
- the phone gets very hot
- the wifi is disconnected every time
- the sim card sometimes detects it and other times it does not
- the gapp can not be installed gives error 20 the twpr
for now just notice those problems .... thanks

rayzo_1986 said:
o be an alpha, the rom is stable.
some things do not work:
- without audio in calls and player
- root can not be activated
- the phone gets very hot
- the wifi is disconnected every time
- the sim card sometimes detects it and other times it does not
- the gapp can not be installed gives error 20 the twpr
for now just notice those problems .... thanks
Click to expand...
Click to collapse
Gapps.. use this, it will work-- https://drive.google.com/drive/folders/16D1ev3XgcjoewlPuafvlheUaqFA15cly
Root.. flash magisk it worked for me
Wi-Fi also works for me
No sim card problems
i agree that phone gets very hot, this rom is not safe to use because of overheating

miXXed404 said:
Gapps.. use this, it will work-- https://drive.google.com/drive/folders/16D1ev3XgcjoewlPuafvlheUaqFA15cly
Root.. flash magisk it worked for me
Wi-Fi also works for me
No sim card problems
i agree that phone gets very hot, this rom is not safe to use because of overheating
Click to expand...
Click to collapse
thanks
gapps work
but I do not get root with magisk 15 and 14 gives me error 1 in twrp
a question the audio works for you?
temperature in 40 degrees and more

[ABANDONED][ROM][Pixel 2][UNOFFICIAL] LineageOS 15.1 / 16.0 [walleye]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing

Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.

Is link not posted yet?

I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!

JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?

JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...

Any chance for an MD5

jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f

TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.

Thanks very much for sharing this. I've got it installed and it's running fantastic.

Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!

razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.

Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?

Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support

@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.

redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo

I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?

Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.

banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview

Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list

Develop Bugs

welcome