Here are patch sets for speaker working on ze60xkl pie ROMs
<Link>
ZE600KL : http://www.mediafire.com/folder/5l0hwa9n7aice/ze600kl
ZE601KL : http://www.mediafire.com/folder/r8wbjbqjjh46j/ze601kl
<Notice>
These patch sets are only for ZE60xKL model on pie custom rom users.
DO NOT apply these for other models or Andoroid versions.
<Patch Files>
1) Kernel Packages (be careful for mistaking model).
- ze600kl-spk-pie-kernel-v1.zip (for ZE600KL(Z00L))
- ze601kl-spk-pie-kernel-v1.zip (for ZE601KL(Z00T))
2) ze60xkl-spk-pie-libs-v1-01.zip (for both ZE600KL and ZE601KL)
<Install Instructions>
1. Download 2 patches (#1 and #2) to any folder
2. Reboot recovery (TWRP)
3. Flash 2 files
4. Reboot system and you can fun sound from device
<Tested Roms>
- Lineage OS
- CrDroid
- AEX
<Features>
- Add speaker sound stream to your rom
- Stereo mic support
<Known Issue>
- Noisy sound with bluetooth and enabling reverb
<Source Code>
https://github.com/zekken1977?tab=repositories
<Change log>
[2019-05-05: v1.0]
- Add tfa9887 driver
[2019-05-26: v1.01]
- Rebased on firekernel r2.10
Finally thank you for helping to test my patch
@Rayonecma, @celtic1453, @fabricio6791 and @ndrancs
First Release On : 2019-05-05
Last Update On : 2019-05-26
Τhanks
Works ok for the ZE600KL
Sent from my MI PAD 4 using Tapatalk
test on ze601kl... working friend
And... For my ze601kl it's working too... ???
can i test the patch on other pie custom rom ?? RR, Cdroid...??
right now i have lineage pie
fabricio6791 said:
can i test the patch on other pie custom rom ?? RR, Cdroid...??
right now i have lineage pie
Click to expand...
Click to collapse
Please
I think this patch will be available for other pie roms unless modified audio HAL or enforced SElinux.
Ze60xkl sound patch
Thx a lot, i've made patch for oreo, but i didn't find any time to work on the pie version .
Great job !!!
You are awesome! Thank you for this work ^-^
zekken1977 said:
Please
I think this patch will be available for other pie roms unless modified audio HAL or enforced SElinux.
Click to expand...
Click to collapse
You are doing Gods work bro!
Hats off to you.
One question.
What about enforced SELinux? LOS will eventually get SELinux to enforcing. What after that? This won't work?
[email protected] said:
You are doing Gods work bro!
Hats off to you.
One question.
What about enforced SELinux? LOS will eventually get SELinux to enforcing. What after that? This won't work?
Click to expand...
Click to collapse
Enforcing SELinux is enabled in stock rom from Oreo (maybe... ) but most custom roms are disabled (permissive) like attached.
Exactly after enabled SELinux, this patch will not work because of enforcing SELinux.
If so, my ideas which we can choose are :
1. Add sepolicy file into patch to access driver
-> It seems to be good but we need to be aware differences of sepolicy between custom roms
2. Change patch design for hold all amp device (tfa9887) controls in userspace (this means kernel patch will be disappeared)
-> It also seems to be good but we need a new designed libs, and making completely independent module from SELinux is difficult, I think.
To be honest, I have no ieda for the best solution
zekken1977 said:
Enforcing SELinux is enabled in stock rom from Oreo (maybe... ) but most custom roms are disabled (permissive) like attached.
Exactly after enabled SELinux, this patch will not work because of enforcing SELinux.
If so, my ideas which we can choose are :
1. Add sepolicy file into patch to access driver
-> It seems to be good but we need to be aware differences of sepolicy between custom roms
2. Change patch design for hold all amp device (tfa9887) controls in userspace (this means kernel patch will be disappeared)
-> It also seems to be good but we need a new designed libs, and making completely independent module from SELinux is difficult, I think.
To be honest, I have no ieda for the best solution
Click to expand...
Click to collapse
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
[email protected] said:
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
Click to expand...
Click to collapse
And another idea is that custom rom maintainers implement tfa9887 driver and sepolicy.
The driver is disappeared without device tree because driver probing doesn't work, this means the driver will not affect to other models except ZE60xKL (strictly other models which are made dtb from not ZE60xKL's device tree).
Otherside we'll distribute patches including audio/amp HALs and audio routing cofigs.
I think this is the most reasonable idea like similar style until Oreo...
zekken1977 said:
And another idea is that custom rom maintainers implement tfa9887 driver and sepolicy.
The driver is disappeared without device tree because driver probing doesn't work, this means the driver will not affect to other models except ZE60xKL (strictly other models which are made dtb from not ZE60xKL's device tree).
Otherside we'll distribute patches including audio/amp HALs and audio routing cofigs.
I think this is the most reasonable idea like similar style until Oreo...
Click to expand...
Click to collapse
I guess, the Devs will implement this driver in to their ROM. But it is more prudent to have a Patch (Like we had upto Oreo). Reason being, there are tens of ROMS. Convincing each dev will be counter productive. The patch can be applied more efficiently.
We'll have to wait and see when the SEPolicy enforcement occurs.
About update patch
Hi patch users,
These patches are based on Firekernel r2.9, then already r2.10 is updated.
So if you'll need to update based on r2.10, pleaase let me know
Thanks
Workaround
[email protected] said:
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
Click to expand...
Click to collapse
Thé selinuxswitch from [email protected] will ne a working workaround to keep selinux disabled even on enforcing mode ROM...
---------- Post added at 05:44 AM ---------- Previous post was at 05:33 AM ----------
zekken1977 said:
Hi patch users,
These patches are based on Firekernel r2.9, then already r2.10 is updated.
So if you'll need to update based on r2.10, pleaase let me know
Thanks
Click to expand...
Click to collapse
Yes, i'm interrested in ...
Please zekken1977 , Can you made jour kernel patch code public ?
Thx a lot.
Superbezo said:
Thé selinuxswitch from [email protected] will ne a working workaround to keep selinux disabled even on enforcing mode ROM...
---------- Post added at 05:44 AM ---------- Previous post was at 05:33 AM ----------
Yes, i'm interrested in ...
Please zekken1977 , Can you made jour kernel patch code public ?
Thx a lot.
Click to expand...
Click to collapse
OK. I'll update but next version will be available on this weekend.
And about source code, please see the link in my 1st post
Thanks
Can you make sound patch for Zenfone Selfie Z00UD (Z00T)?
Because I will try this rom (https://forum.xda-developers.com/zenfone-2-laser/development/rom-prometheusoneui-z00t-t3929198) to my Zenfone Selfie Z00UD (Z00T), but the sound patch only for Zenfone 2 Laser ZE601KL (Z00T). Thanks in advance!
ManOfFeel said:
Zenfone Selfie did not have speaker issue lol
Click to expand...
Click to collapse
But, the prometheusoneui said that need to flash sound patch
fuady7 said:
But, the prometheusoneui said that need to flash sound patch
Click to expand...
Click to collapse
Hi, my patch made for drive spk amp device tfa9887 which mounts on only ZE600 or ZE601KL.
So I guess this patch isn't valuable for other zenfones.
I checked Z00UD schematic and I couldn't find tfa amp.
If you are facing sound issue, my patch can't improve your problem.
Hello, i'll glad to know if someone else encountered the same issue:
I have tested this patch with los ans crdroid with thé same results.
I flashed successfully the ROM & patch and all was working fine (sound ,data ans GSM connexion) for few hours. Then the phone freezes and after reboot,no GSM network détectéd at all... The only way to recover was to do a factory reset with twrp or revert back to oreo backup... Any idea?
Related
SM-N910F - Stock Kernel
Root Android 5.1.1
We have here 2 kernel variants
Original Samsung SE enforced kernel, repacked with a patched sepolicy through SuperSU 2.50
- Recommended kernel as it runs in enforced mode if you are concerned about security
- Recommended method by Chainfire
- Supports only SuperSU 2.50 app for root
- You must update to SuperSU 2.50 before flashing kernel or you end up in a bootloop
- TIMA SecurityLogAgent service still needs to be freezed
- Selinux runs in enforced mode
- Private mode can be used
Click to expand...
Click to collapse
Compiled from stock sources permissive kernel, with NTFS support
- huge drop in security, as it runs in permissive mode
- will allow you to run any superuser app
- supports ntfs mount (needs NTFS helper for the mount ntfs binary or get them from xda or from download link
- selinux is forced to permissive because of new Android 5.1.1 restrictions
- Private mode relies on Selinux and can no more be enabled
- TIMA SecurityLogAgent service needs to be freezed as new Android 5.1.1 detects changes in kernel/SE and warns you about them
Click to expand...
Click to collapse
Why a custom kernel or a modified boot image will probably be needed to root ?
answered by the master: http://www.androidauthority.com/chainfire-rooting-android-lollipop-541458/
New selinux restrictions make it quiet hard for the su daemon to load at boot without exploiting some kernel vulnerabilities that google will patch asap any way.
It seems also that even if we only revert the selinux permissive/enforced toggle, set state to permissive at boot and then enforce security once SU daemon is loaded, many issues could still rise because of the new SE policies. Chainfire says himself that trying to do so will in any case need to drop even more the security level.
Furthermore, enabling toggling of selinux state is now more complicated since 5.0: enabling CONFIG_SECURITY_SELINUX_DEVELOP in defconfig needs androidboot.selinux=permissive in board kernel cmdline. However, this won't be processed in user builds, but only in eng and userdebug builds. This means you cannot expect any such fixes to work on a stock ROM. We now must hardcode the kernel into always permissive mode
In permissive mode, it is impossible to use any KNOX protected features and system will triggers kernel modification alarms by security TIMA agent:
http://www.samsung.com/hk_en/support/skp/faq/1028007. That's why those services must be disabled.
Seems it is not Samsung to blame, but really Google.
Chainfire came with a new approach to avoid compiling the kernel and to be able to run in enforced mode: patching the sepolicy in ramdisk to allow root while still running a stock enforced kernel. This needs version 2.50+ of SuperSU, and won't support, currently, any other root application. This needs a complex procedure documented by Chainfire. It needs rooting the reference device under 4.4 - 5.0.1 enforced mode, patching the 5.1.1 sepolicy under that reference device and export the patched sepolicy to the 5.5.1 boot image of the device. The good part is that we only need to repack boot image with a changed sepolicy, without modifying anything else, mainly the kernel.
Credits
@Chenglu
@Chainfire
Emotroid-Team
XDA:DevDB Information
Android 5.1.1 Kernel, Stock, Root, Enforced and Permissive, Kernel for the Samsung Galaxy Note 4
Contributors
Phil3759
Kernel Special Features: stock, enables root for 5.1.1
Version Information
Status: Stable
Created 2015-09-23
Last Updated 2015-10-30
Download + source diff
- flash kernel in recovery (zip) or odin (tar)
- flash SuperSU v2.50+ for enforced kernel or any root app for permissive kernel
Link:
https://mega.nz/#F!RV8wGT6C!rsfnBrjuqukBNLgLxIgNIA
More original third party releases by @_alexndr (untested by me): https://www.androidfilehost.com/?w=files&flid=45166
FAQ and fixes
How to fix the security notice popup for the permissive recompiled kernels ?
Using Titanium backup, freeze this service: SecurityLogAgent
How to fix Screen Mirroring after root for permissive kernels ?
This is not related to the kernel, but affects some Samsung devices with root
For the fix, check here: http://forum.xda-developers.com/showpost.php?p=63004244&postcount=11
How to fix my wifi passwords not saved on reboot / wifi disconnect for permissive kernels ?
Add this line in /system/build.prop
Code:
ro.securestorage.support=false
What changes are done to the permissive kernel before compiling?
selinux permissive to enable root
NTFS stock Samsung implementation enabled in kernel (needs OTG helper probably)
History changes for permissive kernels
v1.0
N910P-VPU4COG5 kernel sources + N910F-XXU1COH4 ramdisk
v1.1
revert properties to defaults: if you have issues saving wifi passwords, add this line to /system/build.prop or revert to 1.0
v2.0
N910-F latest stock sources
back to ro.securestorage.support=false for wifi password issues in permissive mode
Click to expand...
Click to collapse
Sources:
post 2 with download link
Than you. Could you make a flashable zip with your kernel?
"Somos dueños de nuestro silencio y esclavos de nuestras palabras"
antz_77 said:
Than you. Could you make a flashable zip with your kernel?
"Somos dueños de nuestro silencio y esclavos de nuestras palabras"
Click to expand...
Click to collapse
added a zip file
Which App for Root can i use for example?
Just use SuperSU, after installing kernel with TWRP use the option to add root when exiting from recovery. You'll be fine
Verstuurd vanaf mijn SM-N910F met Tapatalk
patensas said:
Just use SuperSU, after installing kernel with TWRP use the option to add root when exiting from recovery. You'll be fine
Verstuurd vanaf mijn SM-N910F met Tapatalk
Click to expand...
Click to collapse
PhilZ Touch 6.59.0 works perfectly with 5.1.1 by the way, even time with Time Daemon load
Why a custom kernel will probably be needed to root ?
answered by the master: http://www.androidauthority.com/chainfire-rooting-android-lollipop-541458/
New selinux restrictions make it quiet hard for the su daemon to load at boot without exploiting some kernel vulnerabilities that google will patch asap any way.
It seems also that even if we only revert the selinux permissive/enforced toggle, set state to permissive at boot and then enforce security once SU daemon is loaded, many issues could still rise because of the new SE policies. Chainfire says himself that trying to do so will in any case need to drop even more the security level.
So, for now, and maybe also in near future, no other way to root will be possible except using a custom kernel in a selinux permissive state. Sure some vulnerabilities could be found and used, but will probably be patched by Google.
Seems it is not Samsung to blame, but really Google.
Hello
i have installed the kernel, the TWRP and Super su and i have now root on my note 4.
But i always have in my notification bar a notification that says "security notification non authorized action have been made" (i translate from french so it is maybe not exactly what it write on english phones)
What can i do to don't have that anymore ?
Thank you
parisien99 said:
Hello
i have installed the kernel, the TWRP and Super su and i have now root on my note 4.
But i always have in my notification bar a notification that says "security notification non authorized action have been made" (i translate from french so it is maybe not exactly what it write on english phones)
What can i do to don't have that anymore ?
Thank you
Click to expand...
Click to collapse
You can freeze security log agent with TB and you're fine.
@topic screen mirroring is not working here on note 4. Must be kernel related. Stock rooted Rom.
Gesendet von meinem SM-N910F mit Tapatalk
robotnikz said:
You can freeze security log agent with TB and you're fine.
@topic screen mirroring is not working here on note 4. Must be kernel related. Stock rooted Rom.
Gesendet von meinem SM-N910F mit Tapatalk
Click to expand...
Click to collapse
Not related to the custom kernel
http://forum.xda-developers.com/showpost.php?p=61396065&postcount=66
Or just do this:
In build.prop, add this line and reboot device
Code:
wlan.wfd.hdcp=disable
It works perfectly with my Samsung Smart TV
[N910F][Kernel][Stock][Root] Android Stock 5.1.1 Kernel for root
Hi !
Thank you @Phil.
Could you tell me if it's works on the last germany firmware COI3 for N910F please ?
Guillaume59610 said:
Hi !
Thank you
Could you tell me if it's works on the last germany firmware COI3 for N910F please ?
Click to expand...
Click to collapse
I didn't test, but normally, there are no significant changes between those micro letters. Probably just the branded stuff
Can you upload stock boot.img from COI3 ? I will look at it then
Thanks for your answer.
I 've uploaded stock boot.img from COI3. Here is the link :
https: //mega.nz/#!wAlFBTQK!G2Y09HP2mYmtgQMo2PWUGYGPBlJkgyrMDLZpCnjCnqk
Guillaume59610 said:
Thanks for your answer.
I 've uploaded stock boot.img from COI3. Here is the link :
https: //mega.nz/#!wAlFBTQK!G2Y09HP2mYmtgQMo2PWUGYGPBlJkgyrMDLZpCnjCnqk
Click to expand...
Click to collapse
ramdisk changes don't seem relevant
Until we have new kernel sources for N910F, there is no need to recompile
I am using it heavily since a few days without any issue or bug I could spot
Ok, thanks @Phil !
only for F
cant't work on 910C ?
crazydeepman said:
only for F
cant't work on 910C ?
Click to expand...
Click to collapse
No way. The 910C use exynos chip. You have to request on exynos subforum.
"If it compiles, it is good, if it boots up it is perfect"
Best kernel I have seen, until now! - Works without any problems also with German (DBT) ROM: N910FXXU1COI3, that also contains final fixes for StageFright and a better fingerprint support.
THX Phil!
P.S.: Every update is welcome...
Added some info in post 1 on what changed in Android 5.0 that probably will make it near impossible to root a stock ROM while having even the option to run in enforced mode when needed. Any other way that could be found in the future will mean using kernel vulnerabilities. This obviously will be fixed asap by google. At the end, it will be probably simpler and safer (stability wise) to choose between root and a selinux enforced device, not both
This also makes it impossible to use any KNOX protected features and triggers kernel modification alarms by security TIMA agent:
http://www.samsung.com/hk_en/support/skp/faq/1028007
That's why those services must be disabled
Furthermore, enabling toggling of selinux state is now more complicated since 5.0: enabling CONFIG_SECURITY_SELINUX_DEVELOP in defconfig needs androidboot.selinux=permissive in board kernel cmdline. However, this won't be processed in user builds, but only in eng and userdebug builds. This means you cannot expect any such fixes to work on a stock ROM. We now must hardcode the kernel into always permissive mode
Click to expand...
Click to collapse
PS: The anime character "Haruhi Suzumiya" is copyright of its owner
PS: arise fix
Open up a file manager and go to the root folder. You need to have SuperSU installed for this
You'll see a folder called su, go to /su/su.d
In this folder create a text file, label it as "permissive.sh" and put the following code in
Code:
supolicy --live "permissive *"
Then save the file and go to recovery and flash arise and Dolby Atmos addons again and then reboot
It should now work
Stop reading my bs! Here's the download link
https://srv1.botstack.host:8000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
Or
http://srv1.botstack.host:9000/oneplus/op2/custom-kernel-for-haruhios-v3.8-STABLE.zip
This is a project that started as a kernel for my ROM and that is what it's going to be
It can be flashed on other ROMs too and I will gladly provide support however I can't guarantee results
Do note that this is a "secure" kernel. It has many of the security patches merged from CAF and selinux enforcing is forced with no way to go to permissive
What about v4a?
Get SuperSU and input these lines in a terminal
Code:
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };
allow audioserver audioserver_tmpfs:file { read write execute };"
Wait for a few seconds, swipe away v4a from the recent apps list and launch it again. It should now work
Why isn't a thermal throttling tweak included inside this kernel?
Well in my usage the kernel is so fast that thermal throttling modifications are not needed. You can apply if you want
Currently known bugs?
Nothing
OMG you're copying boeffla!
Relax. I used boeffla's anykernel base as I was in a hurry and didn't have time to make my own zip. Also, boeffla's anykernel zip is one of the best around trust me
What are the features?
Too lazy to write, check back here in a few days but there are quite a lot of features you're gonna like
I'm a nerd, I support the GPL, I'm gonna take you down because you didn't release the source code and neither did you tell me whose toolchain you used!
Bro you need to take it easy
Toolchain: https://bitbucket.org/mdalexca/aarch64-linux-android-6.x
Kernel source: https://github.com/anupritaisno1/android_kernel_oneplus_msm8994_custom
I'll try it when there is ROM with new security patch. Looking forward to it!
NeoVsk said:
I'll try it when there is ROM with new security patch. Looking forward to it!
Click to expand...
Click to collapse
I don't care about other ROMs but I'm actively adding security patches into my kernel's source so relax
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
chxei said:
uuu, every time i see new thread, and especialy new kernel i'm goign crazy excited thanks and good luck!
btw, so this kernel is same that comes with halogenos?
Click to expand...
Click to collapse
Not at all
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
NeoVsk said:
Anyone else having slow charging speeds with this kernel? Usually I get around 1.9A, here I only get around 0.5A
Click to expand...
Click to collapse
Known issue
anupritaisno1 said:
Known issue
Click to expand...
Click to collapse
Could you include fast charge in following builds?
NeoVsk said:
Could you include fast charge in following builds?
Click to expand...
Click to collapse
That was my mistake. I forked fast charging from halogenos without realizing that it never worked
This is something I sadly can't fix. You'll have to wait for halogenos devs to update this
Fast charge coming in next build like....
Camera bug fixed!
I don't usually gamble but when I do I buy note7
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
xarisCY said:
May we have two versions? A reverted version for the camera and the current one...? Some ROMs are behind and are not working properly with the new commits about camera. Sorry if I am saying something wrong. I am a noob on these
Click to expand...
Click to collapse
If you start the camera, my kernel fails to turn it off so the camera will be unavailable for use after the first time you use it and you'll have to reboot
I'm working on fixing this bug. Why are you interested in this bug?
Sorry, my mistake. I though was something different.. Sorry
Where can i download naruhi ROM?
Kernel has been updated
All known bugs squashed!
Seems cool but an enforcing only kernel has its downside for me. I'm not sure if arise works with an enforcing kernel, would love to see a permissive version as well.
anupritaisno1 said:
Kernel has been updated
All known bugs squashed!
Click to expand...
Click to collapse
Great job! But I'm still getting only about 700mA when charging
Although the Kernel make the ROM very smooth but it's not battery friendly.
playkish said:
Although the Kernel make the ROM very smooth but it's not battery friendly.
Click to expand...
Click to collapse
On my phone I can't find a difference between my kernel and stock
Also this is a cm kernel. Expect some general battery drain
That being said, I've really worked hard on wakelocks and doze
Hi got your quote on bens kernel page @anupritaisno1, could you explain me more about this kernel. I guess it will break the focus of my camera due to some new commits, etc as bens kernel v5 had done the same to me. Also, as im using bens RR Rom, will this have any bugs or side affects with that rom (i had flashed boeffla kernel and had to face a lot of problems on his rom such as the xposed modules becoming inactive or not performing after some time, etc.) and last main thing, idle battery drain
This LineageOS 14.1 ROM is built from source for Blu R1 HD.
Some features of this LineageOS 14 rom are:
- Hardware rendered LiveDisplay (no UI lag in night mode)
- Android security patches up to October
- Security hardened kernel (including BlueBorne bluetooth patches)
- Kernel patched for Nougat (Nougat compatible SELinux)
- No Chinese spyware
Credits:
zhaofengli (major thanks for getting the rom booting + hotspot/GPS fix, among other things!)
vampirefo
danielhk (GPS fix)
DeckerSu(Initial device tree, MTK patches)
Sources:
Code:
[URL=https://github.com/blumonks/android_device_blu_p6601]Device Tree[/URL]
[URL=https://github.com/blumonks/android_kernel_mediatek_mt6735]Kernel Source[/URL]
[URL=https://github.com/blumonks/android_p6601]Build Manifest[/URL]
[URL=https://github.com/blumonks/twrp_device_blu_p6601]Recovery device tree[/URL]
Downloads:
LineageOS 14.X Downloads
TWRP Recovery
Click to expand...
Click to collapse
Installation Guide:
1) Flash TWRP recovery (See downloads)
Code:
fastboot flash twrp-3.1.1-0-p6601.img
This TWRP recovery has a different device name than previous versions of TWRP.
2) Boot into recovery (Hold vol up when booting and use vol keys to select recovery)
3) If coming from a non lineageOS rom, please format system, data, and cache in recovery before flashing this rom. Otherwise stale files from previous roms may cause bugs.
5) Flash lineage rom
6) Flash gapps (obtain here: http://opengapps.org/)
Current bugs:
Camera does not work. It is still under active research and development.
Bluetooth
Github Issue Tracker (Please do not open duplicate issues)
Please note that support will be limited.
UPDATED BUILD 24 AUG 2020.
If anyone is still using this device, here is an updated build with the August 2020 Android Security Bulletin & all merged LineageOS changes since October 2017. MAKE SURE YOU FLASH USING THE TWRP IN THE ORIGINAL POST! You can flash over any builds in this thread, the camera still doesn't work and I have no interest in fixing it.
https://www.mediafire.com/file/dbdmk...p6601.zip/file
https://gofile.io/d/vTddMJ
Vulnerability said:
Nice! Can't wait to test it! Any screenshots?
Click to expand...
Click to collapse
It's the same as any other lineage rom. Updated OP.
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Is enforcing SELinux supported? Or only permissive?
EDIT: Don't worry I saw the issue tracker post
I'm gonna try this rom
It's nice to see development alive!!!
Hope you could a finally fix the broken camera
Does anyone know anything about the KRACK vulnerability?
zombie_ryushu said:
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Click to expand...
Click to collapse
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
zombie_ryushu said:
Does anyone know anything about the KRACK vulnerability?
Click to expand...
Click to collapse
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Thanks for the updated version.
Urg, but I just finished downloading the original release
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Does this fix also apply to the LineageOS 13.x Rom? I need the Front facing camera working, and that works under Marshmellow and not Nougat.
Just wanted to thank you for your hard work and dedication on this ROM project and wish you good luck with the camera as well.
Not that I find the camera on the R1 HD all that useful as it takes pretty lame photos, but the lack of camera is basically the only thing keeping me from ditching Blu software altogether.
I really hope you manage to get a 100% operational LineageOS for the R1 HD.
Yesterday I called Amazon and complained about the software that collected our personal information and data and submitted it to Blu headquarters in China. They said that I could return the phone for a full refund so at this point I am seriously contemplating doing that. The only problem is that I don't have a backup phone.
The lack of resources from MTK based processors is such a deal breaker. I was not aware it would be so difficult to get development going for it when I bought my phone last year.
Now I'm contemplating getting an used phone with better development support after I return my R1 HD.
I really wanted to wait until OnePlus released their new device with a better display and hopefully a near bezel less display and at least IP67 water resistance. That's the reason why I didn't go for the OP5. The upside-down screen was also another one.
If you could get the camera working in LOS than I'd hold on to my R1 HD for a a while longer. But I'm not keeping my hopes up... Just being realistic. Haha!
Thanks again!
Thanks for your support!
As of now, I've been studying the leaked MTK camera sources for other devices and using IDA to see what extra symbols and logic the stock libcameraservice.so and libcamera_client.so has. It appears that replacing these two libs was the key to fixing camera in cm-13 ports.
Thank you!
Oh, I didn't know camera support was fixed for CM 13 on the R1 HD. Maybe I didn't see it here. But I'd much rather have a non Blu version of Android with all security patches even if it's just on marshmallow.
Three days ago I just realized that Blu had a frigging app collecting my personal data and sending it back to China.
It had sent over 5.9MB of data since July 21st. I think it's a lot of data for text only transmissions.
Anyhow, I've been seeing people using Footej on other ROMs in which they could not get the camera working with stock camera app. Is that what you mean by getting the camera to work?
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Dang! That's old! I guess devs should be more organized in doing a walk through with links to the files and recoveries needed to flash their awesome work.
Here's mine that I've just uploaded to zippy. I think it's the latest available and should be compatible with all ROMs.
Please report back with your findings and opinions on the ROM.
Please try to use both SIM cards to see if they work okay.
http://www8.zippyshare.com/d/p4HMiDRq/41954/R1_Port_3.1-TWRP.img
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Which version of the ROM is installed on it now? Modified or stock? Which recovery is on the phone? Stock or TWRP?
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
frosted.efizzle said:
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
Click to expand...
Click to collapse
Did you download and flash the image I've just shared above?
AndroidBR said:
Did you download and flash the image I've just shared above?
Click to expand...
Click to collapse
Same error
With they recovery You provided above
Thanks for your support!
Lineage OS 16 For Xperia X [Treble]Based on Sony Open DevicesI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
Opinional files:
Disable ForceEncrypt:Link
Required files:
[Tested]
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v6_loire.zip
[OEM-Files]
Download Link
How to flash
Read README.txt in zip file please.
Optional step If you want to use a GSI
Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Because of Anti-Rollback, If you want to Use GSI, You need to choose the same or newer one as the treble build date.
Update and known BUG:
V20190323:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll Script
Contributors
Sjll @infixremix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-03-31
Last Updated 2019-03-31
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
LOLisLIFE said:
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Click to expand...
Click to collapse
lookmanns14 said:
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
Click to expand...
Click to collapse
I will try to build a optimize kernel in free time.
Hi,
Can you please help me with the download from the GSI? Where can I get the right file from?
after install, bluetooth and settings tell me that it stops all the time and sim cant be detected. Also there is some encryption so i can't access data or system anymore with twrp... even magisk can't be installed. great...
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
iH8Ecchi said:
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
Click to expand...
Click to collapse
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Some random said:
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Click to expand...
Click to collapse
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
iH8Ecchi said:
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
Click to expand...
Click to collapse
Hmmmmm
Well like that it worked with all pie ROMs that I used
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Fardin Rehman said:
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Click to expand...
Click to collapse
Use Twrp-Q (Ask Simeone for Link)
Some random said:
Use Twrp-Q (Ask Simeone for Link)
Click to expand...
Click to collapse
Yeah I have TWRP-Q just need to flash recovery and then try again. Thank you very much for helping
Can anyone please tell me which Gcam can i use on this ROM?
New version of LOS 16 + Treble
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
iH8Ecchi said:
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
Click to expand...
Click to collapse
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Fardin Rehman said:
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Click to expand...
Click to collapse
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
iH8Ecchi said:
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
Click to expand...
Click to collapse
Yeah I am using the gcam port and I get pretty good pictures with it but not very good video quality so I guess I'm gonna give it a try to Chippa_a's Unofficial LOS16.
Xperia XZ1 G8341 Vanilla AOSP ROM
This is my first ROM and its fully Vanilla. I Just followed this Build guide without any modifications whatsoever.
The future goal is to build a stable Rom with mostly FOSS Software, stability and useful tools/settings.
Bugs/missing functions i discovered so far:
- Camera Not working always and -> Lens Distortion. Although RAW should be possible.
- Sony Bootlogo has some Artifacts
- No automatic APN setting
- No NFC 25.05 working
- No 90/120Hz mode (or does it?)
- No Display Colour Calibration
- Low Singlethread Geekbench Score (836) and (6060 Multicore) [Governors and schedulers not optimized]
Fingerprint Sensor is working and it takes some time to find Network (not sure if bug or normal).
I hope to find usable answers to those problems + ideas and hope, to receive enough feedback to improve as much as possible.
Just Flash all files (boot, recovery [or any working TWRP], system,vendor, userdata and the OEM Binaries [
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.img] and you should be good to go.
XZ1 Single Sim(25.05.19)
XZ1 Dual Sim
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.img
120Hz Mode
Obviously I am not responsible for bricked devices or anything that this could be related to.
XDA:DevDB Information
RumiRom, ROM for the Sony Xperia XZ1
Contributors
celeron1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: Stock AOSP Userdebug
Version Information
Status: Testing
Created 2019-05-25
Last Updated 2019-05-30
Don't use V8 binaries, V9 are out
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/
Worse perfomance is expected because of lack of qti perf framework
marios199546 said:
Don't use V8 binaries, V9 are out
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/
Worse perfomance is expected because of lack of qti perf framework
Click to expand...
Click to collapse
Neat!
Im gonna try these. Thanks a lot.
I would marry if you turn 60fps to 90-120-144 omg plz plz
ΒΕΓΑ said:
I would marry if you turn 60fps to 90-120-144 omg plz plz
Click to expand...
Click to collapse
There is little to nothing about this I could find for the xz1 except one oreo based rom. I have to compile the kernel for it and find out if 60+ hz is really working and how to succesfully implement a toggle option for it. Since im new at this it might take some time without help but its something I want to impliment.
The Xz1s Display obviously is really underperforming in non Sony roms without the "Bravia engine" (colour apperence) imo compared to other open roms. I tried the Bravia magisk module but could not see any difference (also did not checked what it should do at system level).
So if someone has more knowledge feel free to share
I compiled a Kernel from here and modified:
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-base-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar.dtsi
(changed 60hz to 90/120hz).
How can I check if the Panel really is working under those frequencies and if other steps are needed?
When compiling I got an Error with drivers/staging/wlan-qc/qcacld-3.0 -> so i removed them from drivers/staging/Kconfig (So apparently no Wifi).
These are the Kernels (boot):
90Hz
*Update 29.05. I Fixed Wifi for the 120Hz version. link in first post
Camera seems to work without problems (also Raw) so I guess there is something wrong with the precompiled Sony Kernel.
Also the Sony bootlogo is not present (no artifakts??)
And again. Flash at own risk.
What about the version for two SIM cards?
Model G8342.
Your rom works perfect on my phone, thanks dev.
Btw, doesn't it support Treble? I cannot boot any of the GSI roms on the forum...
Riskypedia said:
Your rom works perfect on my phone, thanks dev.
Btw, doesn't it support Treble? I cannot boot any of the GSI roms on the forum...
Click to expand...
Click to collapse
It should support Treble.
Maybe you also need to flash "Disable DM Verity" and "Magisk" after
Can be used on G8342 ? ?
Sent from my Sony Xperia XZ1 using XDA Labs
celeron1 said:
I compiled a Kernel from here and modified:
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-base-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar.dtsi
(changed 60hz to 90/120hz).
How can I check if the Panel really is working under those frequencies and if other steps are needed?
When compiling I got an Error with drivers/staging/wlan-qc/qcacld-3.0 -> so i removed them from drivers/staging/Kconfig (So apparently no Wifi).
These are the Kernels (boot):
90Hz
120Hz
Camera seems to work without problems (also Raw) so I guess there is something wrong with the precompiled Sony Kernel.
Also the Sony bootlogo is not present (no artifakts??)
And again. Flash at own risk.
Click to expand...
Click to collapse
Can i use this kernel with stock sony rom? (Existenz patched btw...)
ΒΕΓΑ said:
Can i use this kernel with stock sony rom? (Existenz patched btw...)
Click to expand...
Click to collapse
The Kernel is for AOSP (Linux kernel 4.9) so normally it shouldnt work with the Stock Firmware but i dont know if it works with the patched Existenz rom.
therma.cpp said:
What about the version for two SIM cards?
Model G8342.
Click to expand...
Click to collapse
Its for the single Sim.
Im not satisfied with the current State but I can build a dual sim version as well. (Building on hdd due to small SSD so it might take a while)
Screen is not responsive (SOV36). Any suggestions?
update: not the rom. tried to flash different rom and same result.
sinkoo1979 said:
Screen is not responsive (SOV36). Any suggestions?
update: not the rom. tried to flash different rom and same result.
Click to expand...
Click to collapse
Does it respond different while charging?
Is the screen properly clean?
Try flashing the last stock rom > same result?
If not try flashing any gsi > result?
Then full cfw flash + sw binary.
And do factory resets before flashing.
Hoping for the best. Not sure how and if the SOV36 model differs from the rest
celeron1 said:
Does it respond different while charging?
Is the screen properly clean?
Try flashing the last stock rom > same result?
If not try flashing any gsi > result?
Then full cfw flash + sw binary.
And do factory resets before flashing.
Hoping for the best. Not sure how and if the SOV36 model differs from the rest
Click to expand...
Click to collapse
no
yes
no
did not work
works with stock
sinkoo1979 said:
no
yes
no
did not work
works with stock
Click to expand...
Click to collapse
Dis you try one of these GSIs and did you flash the SW-Binaries after?
How "non responsive" is it? Laggy/Not at all/Ghost touches etc.?
Since this is off-Topic i will delete this message after you read it. You shuld open a new Thread where the Problem could be discussed.:good:
celeron1 said:
Dis you try one of these GSIs and did you flash the SW-Binaries after?
How "non responsive" is it? Laggy/Not at all/Ghost touches etc.?
Since this is off-Topic i will delete this message after you read it. You shuld open a new Thread where the Problem could be discussed.:good:
Click to expand...
Click to collapse
Nothing at all
sinkoo1979 said:
Nothing at all
Click to expand...
Click to collapse
Try flashing a oreo based stock rom.(or if you only tried oreo then pie), then flash gsi etc
ΒΕΓΑ said:
I would marry if you turn 60fps to 90-120-144 omg plz plz
Click to expand...
Click to collapse
don't you think it would be the least manner to put some pics of your ass when you come around with "marrying-for-asking"? XD :silly::silly: