Develop Bugs

ROM UPDATED May 19, 2015 [ROM] LP 5.1 Resurection-Remix Hardened Unofficial

Rom updated on May 19. This is LP 5.1 release 2. Latest Google/CM/Resurrection sources + all hardened features. Plus cleaned IP addresses (got rid of Google, Level 3 communication, AT&T, Orange, Department of Defense and other shady ips). Also enabled is Volte (enhanced LTE), which is Voice over LTE. This depends on the service provided by your carrier. In the States, for example, T-Mobile provides such services, which include high definition voice. Usually, you need special update done by the manufacturer in conjunction with your carrier. This rom does not need that. Your Z1 is already provisioned for Volte. You will see in Mobile Settings another entry: Enhanced 4g LTE Mode. ALso, in test menu/phone (*#*#4636#*#*), you will see a Volte Provisioned Flag. So, as soon as your carrier starts Volte, you are all set.
Sources are the same...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12531
_____________________________________________________________________________________
Rom updated to latest sources on May 4. In addition to regular hardened features, more than 40 instances of Google IP, Level 3 Communication and Department of Defense IPs removed from sources both for IPV4 and IPV6. The same is replaced with Opendns IP. Keep in mind that those ips go not only in configuration files, but libs also and the latter cannot be decompiled and fixed...
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12289
______________________________________________________________________________________
Rom Updated to LP 5.1.1. All hardened/security features implemented. Kernel used from Slimroms 5.1.
TWRP 2.8.6 is integrated in kernel.
Obviously, this is an alpha version...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12110
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Rom updated to 5.1: all hardened features enabled.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=11901
___________________________________________________________________________________________________
March 31: kernel updated to include screen color calibration:
See Download link: http://forum.xda-developers.com/showpost.php?p=59801528&postcount=94
_________________________________________________________________________________________________
March 27: New build is up, latest CM and Resurect changes; kernel includes voltage table, syncookie and TWRP.
Download Link: http://d-h.st/lw2s
Mirror Link: http://forum.xda-developers.com/devdb/project/dl/?id=11744
_________________________________________________________________________________
March 15: New build is up including latest sources, TWRP integrated in kernel, led lights fixed
DOWNLOAD LINK: http://d-h.st/UO7W
_______________________________________________________________________________________________
Marchh 7: Rom Updated to the latest version + plus all security enhancements. Sources for security changes are the same as posted
See Download section for update
Here is Resurection Remixed Lollipop hardened and secure. Built from sources on February 24.
Changes:
First of all, as many know, encryption on lollipop slows down the device to almost unusable. I was able to resolve that. The culprit was Qualcom crypto module and drivers that collide with graphics. In this rom, when you encrypt your device, there is no noticeable slow down at all. Your master encryption key is no longer stored in crypto module (which rumor has it is backdoored anyway), but rather hashed and salted on the drive itself.
1. Modified kernel to disable creepy SElinux and enable Tomoyo security. Now you can safely use Xposed framework and some modules such as Xprivacy, Appsettings and ShowDialpad, as well as many others
2. Modified kernel to disable qualcom module and drivers
3. Disabled creepy qualcom random number generation and enabled all other methods
4. Enabled 256 bit AES drive encryption as opposed to Google's default 128 bit
5. Enabled all ciphers and hashes available in kernel and disabled by default (thanks Sony and Google)
6. Latest CM changes
7. Omniswitch (to be flashed separately after flashing the rom)
Maybe more
INSTALL:
1. Be on Kitkat, rooted with CWM or TWRP
2. Enter Recovery, wipe System, Data, Cache
3. Flash the rom
4. Flash Omniswitch
5. Reboot and enjoy
If you want to encrypt your device, you need to do 2 additional steps before or after encryption. Go to Developer Options and enable "Force GPU rendering" and "Disable HW overlays. Yes, you have to enable (not disable) "Disable HW overlays" option. The latter won't stick after reboot. So, manually transfer the attached init.d script to /system/etc/init.d and set permissions to at least 744. This way the option will be set at boot and you won't have any noticeable slowdown. In fact, I don't see any difference in speed between encrypted and non encrypted device.
CREDIT: Resurection-Remix Team, Cyanogenmod, AOSP and Omniroms
WARNING:
I am not responsible if your device explodes and kills everyone around. You are doing it on your own. Russians, who are definitely coming, won't help you either :laugh:
Download links
Rom: http://d-h.st/l1rB For Update see Download Section
Omniswitch: http://d-h.st/AbGH
Init.d script (in case you want to encrypt your data): http://d-h.st/QIiE
Sources: https://github.com/ResurrectionRemix
https://github.com/HonamiZ1/android_system_vold
https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Resurection-Remixed Lollipop 5.1.1 Hardened, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Cyanogenmod
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-05-19

screenshots
Screenshots added

Kernel updated with CPU voltage table
Kernel updated to allow under/over volting. See attachment.
Instructions:
1. Unzip the file
2. Flash in fastboot: fastboot flash boot boot.img and fastboot reboot
Enjoy

Thanks for this ROM, are there any known bugs?

wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
All CM bugs as of February 24. You can go on their site and see the list of changes...

optimumpro said:
All CM bugs as of February 24. You can go on their site and see the list of changes...
Click to expand...
Click to collapse
So just need to look at http://forum.xda-developers.com/xperia-z1/general/rom-official-cyanogenmod-12-nightlies-t3007118 is that right?
Sorry I have to confirm, there are multiple threads (Official/Development) for CM12.
This ROM will maintain root and recovery, right?
I'll flash and let you know if I find any other issues.

Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.

Kyrius said:
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Click to expand...
Click to collapse
I use Textsecure as sms replacement. Microphone works great...

Very buggy
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE

darkdevu said:
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
Click to expand...
Click to collapse
1. Learn the rule about not posting bug reports without logcat
2. Camera works fine: verified
3. Always wipe System/Data/Cache before flashing
4. Are you sure you have Xperia Z1?
Cheers

his profile says Z3. lol

Any further reports on this ROM? Interesting to know how it performs and about stability

Deleted

wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
Rom Updated to the latest version. See Download section in the OP.

and where is the link to the update?

shikimafia said:
and where is the link to the update?
Click to expand...
Click to collapse
It is in Download section:
http://forum.xda-developers.com/devdb/project/?id=8412#downloads

Screenshots added in post #2. Note that only this rom and SlimLP work with the latest Xpivacy module. Tried on Crdroid and others and there is bootloop as soon as you enable Xprivacy.

Has no one tried this rom as not reports or posts
tried flashing update from scratch and get play services fc on every gapps i used............i am guessing i may have to flash initial release and dirty flash this over it? excuse me if i may have got it wrong

shingers5 said:
Has no one tried this rom as not reports or posts
Click to expand...
Click to collapse
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...

optimumpro said:
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
Click to expand...
Click to collapse
I'm having issues flashing the new version as getting play services errors.... Was gonna try dirty flash over previous versions

[Kernel][7.1.1] SunKernel Pedigree Z5 for LineageOS [sumire]

A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30

Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse

Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)

Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I

Thanks, I hope you don't forget dsds variant.

It is a pleasure to have SunKernel in LineageOS.

Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.

Flashing lineage and kernel, looking forward to try it
Thanks for upload

s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload

Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.

Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update

zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.

stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)

In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install

zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.

actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?

@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.

L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks

zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse

L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse

[KERNEL]Mate 10 Pro Stock "setenforce" kernel (Wireguard) (Upstreamed)

Note: I have only tested this on Mate 10 Pro, so I don't know if it works on Mate 10. Title will stay until tested
Kernel downloads: https://github.com/Ante0/BKL_OREO_EMUI8/tree/master/releases
Source used: https://github.com/Ante0/BKL_OREO_EMUI8
Currently upstreamed to: 4.4.130
4.4.60 and above contains Blu_Active governor
Windows: https://mega.nz/#!NTgEFKiZ!4nB6QuznpI-Q4R8mtJENZ34KV4YNr6aUIlMTyTYOQcQ
Download Kernel_Pack_tool_windows.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_windows folder, open a command prompt in the extracted folder and run "pack_kernel.bat 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
Linux: https://mega.nz/#!Ne5mXATT!FXjWsnY61VewihTWagrJ09G6jv15_y4BlS_R0HDQ5UM
Download Kernel_Pack_tool_linux.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_linux folder, open a terminal in the extracted folder and run "./pack_kernel.sh 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
If you get permission errors you may have to chmod +x pack_kernel.sh and mkbootimg
UPDATE: I have changed sources to use Honor View 10 instead as camera works here (and everything else) and I'm also upstreaming it. Currently at 4.4.52: https://github.com/Ante0/BKL_OREO_EMUI8.0
Downloads will come soon. I will make a new script to change patch level instead of changing each image (from 2017-12 to 2018-09) as it takes time and space on my mega.
This does not set selinux to permissive all the time, you have to use 'setenforce 0' to enable permissive, this is to only enable it when you need it.
All this does is let us use 'setenforce' again, since Huawei decided to disable it in Oreo.
Could be useful for V4A and other sound mods, since they usually require permissive. Or anything else that could need permissive.
V4A still doesnt work with permissive, something else needs fixing
Note: This is for Security Patch level 2018-01. If yours is 2017-12 or 2018-02 you will bootloop.
This is because --os_patch_level must match ro.build.version.security_patch in /vendor/build.prop
If so you need to repack kernel and change --os_patch_level to match your version.
I will keep my github updated with security patches from Google, but if Huawei changes something in their own source it won't be in this kernel.
Mate 10/Mate 10 Pro downloads: https://mega.nz/#F!FbBBCaIS!YYH94l12su3HcsbwIqDygg
(Check Settings -> About - "Android security patch:" to get the correct patch level.
If it says 1 January 2018, download and flash 201801 kernel. 1 February 2018: 201802 and so on.)
Flash using: Fastboot flash kernel kernel.img
Mate 10 Kernel source: https://github.com/Ante0/ALP_OREO_EMUI8
Mate 10 Pro Kernel source: https://github.com/Ante0/BLA_OREO_EMUI8.0
Update 10/2: Added Wireguard support, for those who like to use VPNs.
Added some simple build scripts
Please note that portrait mode in camera has been broken with custom kernel since BLA-L29C432B137

Not working on BLA-L09, error mode boot image load failed.

Will try on ALP and report later
Edit: Failed flash due partition lenght get error

smariob said:
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
Click to expand...
Click to collapse
Bordo_Bereli51 said:
Not working on BLA-L09, error mode boot image load failed.
Click to expand...
Click to collapse
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.

ante0 said:
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
Click to expand...
Click to collapse
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?

@ante0
Thank you for the new kernel!!!
Keep up the good work dev :good::good::good:

smariob said:
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
Click to expand...
Click to collapse
No. Kernel is separate. Magisk goes in ramdisk.
Before oreo ramdisk and kernel was merged in the boot partition, but now they're split into ramdisk and kernel partitions.
So you only need to flash kernel to kernel.

Congrats for the first Mate 10 kernel, mate![emoji482]

noob question here: setenforce 0 is written in terminal or adb? how to?

Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.

Bordo_Bereli51 said:
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Click to expand...
Click to collapse
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Saadkhalid786 said:
noob question here: setenforce 0 is written in terminal or adb? how to?
Click to expand...
Click to collapse
terminal.
Or use the Magisk Module as Bordo_Bereli51 suggested.
Though if you don't have any app or something that needs permissive it's no use in running it at all times.

ante0 said:
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Click to expand...
Click to collapse
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?

@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Bordo_Bereli51 said:
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
Click to expand...
Click to collapse
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.

Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
I am already doing that but wanted to know if he had stock but I am almost finished getting stock kernel

Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
According to Kconfig, it's not used. So there must be a vibrator elsewhere.

ante0 said:
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
Click to expand...
Click to collapse
Yes, looks like that driver is disabled, but i still didn't found another vibrator/motor.

lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.

Bordo_Bereli51 said:
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Click to expand...
Click to collapse
It's set to always permissive.
Edit: And for me it bootloops for some reason.

ante0 said:
It's set to always permissive.
Click to expand...
Click to collapse
Which is why I want it in order to get V4A working
I am on kangvip rom.

Bordo_Bereli51 said:
Which is why I want it in order to get V4A working
Click to expand...
Click to collapse
I've tried with permissive, doesn't work with the Magisk Modules...
You might have luck with installing to /system and /vendor manually.
Kangvip might be why the kernel is not working for you, they usually incorporate their own hacks.

[ROM] [10.0] [STABLE] [walleye] Dirty Unicorns 14.6 [UNOFFICIAL]

ROM VERSION: 14.6
Device: Google Pixel 2
Build Type: UNOFFICIAL
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH :
Download the latest build (Pixel Gapps included)
Reboot to recovery
Wipe System, Data, Dalvik
Flash the latest build
Reboot
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
Latest build
Kernel Source:: https://github.com/gibranmather/android_kernel_google_wahoo
Device Tree:: https://github.com/gibranmather/abc_device_google_walleye
XDA:DevDB Information
Dirty Unicorns , ROM for the Google Pixel 2
Contributors
gibranm
Source Code: https://github.com/gibranmather/android_kernel_google_wahoo
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: May Firmware
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.4
Stable Release Date: 2020-06-08
Created 2020-05-29
Last Updated 2020-06-08

Stock kernel provides a balanced experience in terms of battery and smoothness.
For users who want a lightweight efficient kernel with great battery gains, I would strongly recommend Sultans kernel.
For user who want a bit more customisations from their kernel, I would suggest Flar2's elemental x.

Reserved
This rom provides a lossless pixel experience with extra features and customisations.
All pixel features working: Active Edge, Now Playing, Google Assistant
All sensors are working
Safetynet passes by default
Widevine L1 DRM present for hd video
Kernel is unicornblood for taimen with commits to enable touch on walleye.
TWRP will not be able to decrypt if you have a pin. So only disable pin when you need to use twrp

Thank you for keeping walleye alive!! So far everything is working good.

Pretty stable ROM!! Thanks a lot!

14.4 update is compiling right now. Will release soon

14.4 Out
14.4 Changelog:
June ASB merged
Kernel upstreamed with asb merged
Redesigned front end of tweaks app

gibranm said:
14.4 Changelog:
June ASB merged
Kernel upstreamed with asb merged
Redesigned front end of tweaks app
Click to expand...
Click to collapse
@gibranm THREAD CLOSED! Placeholder are not accepted.
Please advise the moderators' team (best via the report function) to re-open the thread when ready to provide a download link.

New Build 11/08/20
Dirty Unicorns have returned to XDA, hence the thread reopening. Here is du 14.6 for walleye.
Changelog:
- Merged in August's security update
- Add option to hide clock on home screen
- Add in the Caviar Dreams font
- Added various AOSP fixes to improve the overall experience
- Device specific fixes where applicable
- Imported French translations
Latest build

gibranm said:
Dirty Unicorns have returned to XDA, hence the thread reopening. Here is du 14.6 for walleye.
Changelog:
- Merged in August's security update
- Add option to hide clock on home screen
- Add in the Caviar Dreams font
- Added various AOSP fixes to improve the overall experience
- Device specific fixes where applicable
- Imported French translations
Latest build
Click to expand...
Click to collapse
CLEAN FLASH :
Download the latest build (Pixel Gapps included)
Reboot to recovery
Wipe System, Data, Dalvik
Flash the latest build
Reboot
Sorry for the maybe dumb question. Do i have to flash it to both slots A and B? Not mentioned above. Is there a how to?
It's my first Pixel 2 after many years of Nexus Phones. THX
PS: I'm @ abc Rom (Bill Blandford) atm

MontiBurn said:
CLEAN FLASH :
Download the latest build (Pixel Gapps included)
Reboot to recovery
Wipe System, Data, Dalvik
Flash the latest build
Reboot
Sorry for the maybe dumb question. Do i have to flash it to both slots A and B? Not mentioned above. Is there a how to?
It's my first Pixel 2 after many years of Nexus Phones. THX
PS: I'm @ abc Rom (Bill Blandford) atm
Click to expand...
Click to collapse
No need. If you have twrp, reboot to recovery and follow instructions. Don't forget to flash twrp zip after ROM zip

gibranm said:
No need. If you have twrp, reboot to recovery and follow instructions. Don't forget to flash twrp zip after ROM zip
Click to expand...
Click to collapse
Thanks! Stock Rom needed before or just over my current Rom?

No. As long as you are on June firmware and have twrp. Follow the instructions and flash twrp zip

gibranm said:
No. As long as you are on June firmware and have twrp. Follow the instructions and flash twrp zip
Click to expand...
Click to collapse
Hey there, is the June firmware required or will July/August work as well?

Shamestick said:
Hey there, is the June firmware required or will July/August work as well?
Click to expand...
Click to collapse
June or newer will be fjne

gibranm said:
June or newer will be fjne
Click to expand...
Click to collapse
Awesome I appreciate your quick reply, my friend. I also hopped over to the official Taimen thread and your comment was confirmed.
Have had my Pixel 2 for over 2.5 years now and never flashed a custom rom (previous flashaholic on all previous devices ) but I think I may just take this for a spin over the weekend and see how it goes. Always loved DU.

Does anyone use / willing to try installing LMT pie?
This is the first time I've had any problems, but it's granted all the accesses it needs and comes out but the commands won't work. Curious if others have the same.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:46 AM ---------- Previous post was at 08:42 AM ----------
The build is running great otherwise!
Sent from my [device_name] using XDA-Developers Legacy app

Can't use screen mirror or screen cast to Roku tv seems like a kernel crash but can't catch a log as I have another issue I can't tell if ROM related or hardware related so till then screen cast is only issue I have

Tried to download Latest Build. Have to Login with G-Account and send the request. Getting immediately
Delivery Status Notification (Failure)
, can't be send how do i get this rom? @du Homepage only Pixel2 XL is available. Will there be updates?

Development [KERNEL]Despair Kernel

Mission:
The purpose of this project is to increase efficiency of the Pixel 6 series devices by merging functional patches with minimal bloat.
If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Installation:
To install kernel on a rooted device with EXKM/FKM
- Download ZIP and flash using the manual flasher in the app
To manually flash kernel updates
-Download ZIP for kernel and the current boot.img
-Use the below commands to flash from bootloader/fastboot
-fastboot reboot fastboot
-fastboot flash vendor_dlkm vendor_dlkm.img
-fastboot reboot bootloader
-fastboot flash dtbo dtbo.img
-fastboot flash boot boot.img
-fastboot flash vendor_boot vendor_boot.img
Links:
Telegram:
Despair
You can view and join @despairchat right away.
t.me
Downloads:
raviole - Google Drive
drive.google.com
Source:
https://github.com/DespairFactor/raviole
Credits:
Google

I will update OP when I am back at a PC on the weekend

Kir is working on pixel 6, is this also working on pixel 6?

ne0ns4l4m4nder said:
Kir is working on pixel 6, is this also working on pixel 6?
Click to expand...
Click to collapse
Should be

yeah know i have to go back to p6pro

freddienuxx said:
yeah no i have to go back to p6pro
Click to expand...
Click to collapse
What do you mean?
Also, I have updated the top post with a telegram link for chat

Flashed this last night because DespairFactor's work is awesome and I had some suspicion about the stock kernel. Stock kernel loss the previous night was 1.4%/hr and last night's result with Despair was 0.8%/hr. Doing a screen on test comparison through my workday today so I'll have more to share later but this paired with EXKM is excellent so far!

do you need to flash anything else apart from the kernel img?

Nekromantik said:
do you need to flash anything else apart from the kernel img?
Click to expand...
Click to collapse
For now it is just the boot.img

Also, don't make the mistake I did and forget to root the image via the app first. Flashing the boot by itself will unroot you so just use magisk to root the image before flashing. If you're already rooted this can be flashed via EXKM without issue.

Damn, it's been a while. I think I flashed Despair's ROM on the Nexus 5..?
Anyways, running rooted (Magisk 23013) Despair kernel now atop the 036 update.
Smooth and hopefully less power hungry.

Build V1.01 is out now and source has been pushed

Just pushed build V1.02 this morning with some changes from Google's Android 13 branch

working great so far

Testing this kernel as well (rooted) ... will post findings ...

1.03 and 1.04 are released, source on github

There's a lot of activity in the telegram channel for those interested including tips for Wakelock blocking and other tips for battery life improvement. Feel free to join in and report your results using the kernel!
We find that we can only do Wakelock blocking on Franco Kernel Manager. EXKM doesn't work for Wakelock blocking so just wanted to mention that as well even though it is included in the kernel.

AlkaliV2 said:
There's a lot of activity in the telegram channel for those interested including tips for Wakelock blocking and other tips for battery life improvement. Feel free to join in and report your results using the kernel!
We find that we can only do Wakelock blocking on Franco Kernel Manager. EXKM doesn't work for Wakelock blocking so just wanted to mention that as well even though it is included in the kernel.
Click to expand...
Click to collapse
The latest version of EXKM has the updated paths for wakelock blocking

flar2 said:
The latest version of EXKM has the updated paths for wakelock blocking
Click to expand...
Click to collapse
Tested it already, working great. Thank you for updating it

Note that 037 OTA just dropped. Don't know if there's kernel changes.
BTW, can Despair be flashed over the Verizon versions of the OTAs..?