[ROM][10]LineageOS Z4Tablet[SGP712/771] - Xperia Z4 Tablet Android Development

There is Android Q ROM for Xperia Tablet Z4.
This is a quite stable rom, but there are:
- a broken camera (there is a small chance that someday it'll be fixed);
- when the tablet is off, during charging, the diode will always light red;
- FM radio;
- Hardware encryption (external SD Card as internal storage)
- LiveDisplay;
Many games like clash of clans crash after some time of using;
It works quite laggy.
How to install:
1) use TWRP 3.1.1 or 3.4.0 (this is better). If you using 3.1.1 one, remove the first two lines from updater-script (\ META-INF \ com \ google \ android);
Code:
assert(getprop("ro.product.device") == "SGP771" || getprop("ro.build.product") == "SGP771" ||
getprop("ro.product.device") == "karin" || getprop("ro.build.product") == "karin" || abort("E3004: This package is for device: SGP771,karin; this device is " + getprop("ro.product.device") + "."););
Note, I often upload ROM with having two lines removed.
2) wipe system, data, cashe, dalvik;
3) Flash the firmware, gapps, magisk and that’s it.
Change log:
20200620 - livedisplay now fully works.
20200730 - fixing memory leaks in the kernel.
20200812 - fixing led and light sensor.
20201023 - camera fix.
Last builds (mirror) are here.
Sabar_op link
Kernel sources.
We must be infinite grateful to sabar_op for his hard work in development of this rom and Bernie and Tarkzim who help to update kernel for kitakami devices. :good:.
Battery consumption significantly reduced! For further reduction, please follow these instructions https://forum.xda-developers.com/showpost.php?p=83211949&postcount=197 .

First of all: Thank you for keeping our device with up to date rom. Very much appreciated. I am still on LOS 7.1. and would like to move on to a more recent rom with current security patches.
The first two lines in updater-script of lineage-17.1-20200620-UNOFFICIAL-karin/ read
Code:
ui_print("Target: Sony/karin/karin:10/QQ3A.200605.001/eng.sabar.20200621.001556:userdebug/test-keys");
package_extract_dir("install", "/tmp/install");
and not what is written in the post. What is the problem? I want to use TWRP 3.1.1. for flashing. Am I missing something?

Hybel1507 said:
First of all: Thank you for keeping our device with up to date rom. Very much appreciated. I am still on LOS 7.1. and would like to move on to a more recent rom with current security patches.
The first two lines in updater-script of lineage-17.1-20200620-UNOFFICIAL-karin/ read
Code:
ui_print("Target: Sony/karin/karin:10/QQ3A.200605.001/eng.sabar.20200621.001556:userdebug/test-keys");
package_extract_dir("install", "/tmp/install");
and not what is written in the post. What is the problem? I want to use TWRP 3.1.1. for flashing. Am I missing something?
Click to expand...
Click to collapse
Before the uploading roms, I ckeck it on my own to see whether it works and as far as remember I've done this step.
All you need to do is to wipe necessary and flash the rom with twrp 3.1.1. If you will have zero byte internal storage, you have to format it by twrp.

May I ask where the source code for this build is located at ? (both kernel and rom)

kevinhecox99 said:
May I ask where the source code for this build is located at ? (both kernel and rom)
Click to expand...
Click to collapse
It's not still published.
Last ROMs work better.

alex009988 said:
It's not still published.
Last ROMs work better.
Click to expand...
Click to collapse
Which version works best (which date)?
Also why not put the files on androidfilehost, this site looks unusual and with no source code available people should be careful what they are installing.

belrik said:
Which version works best (which date)?
Also why not put the files on androidfilehost, this site looks unusual and with no source code available people should be careful what they are installing.
Click to expand...
Click to collapse
The sources of common tree and kernel are in https://github.com/Sony-MSM8994-Dev
I am just doing a bit modification to match our device, while the device tree can be found in my github.

Hi all, what about the camera with this ROM?

belrik said:
Which version works best (which date)?
Also why not put the files on androidfilehost, this site looks unusual and with no source code available people should be careful what they are installing.
Click to expand...
Click to collapse
The last ones are most stable from 30072020. The 12082020 with fixing led and light sensor.
I use my own cloud storage as this would be saved for many years and it's fast enough to download.

1GTRBG said:
Hi all, what about the camera with this ROM?
Click to expand...
Click to collapse
No hope for z4 tab camera as long as these guys find the solution for z5 https://forum.xda-developers.com/z5-compact/development/rom-lineageos-17-1-z5c-suzuran-t4052973

Thanks for the rom.
Is the latest build (12082020) compatible with SGP712 (karin_windy), or I should use 30072020-karin_windy for my SGP712?

joyirwin said:
Thanks for the rom.
Is the latest build (12082020) compatible with SGP712 (karin_windy), or I should use 30072020-karin_windy for my SGP712?
Click to expand...
Click to collapse
You must use the second one 30072020.

How are The battery performance compaired to stock?

torben5247 said:
How are The battery performance compaired to stock?
Click to expand...
Click to collapse
I have not used stock for years. But i can say performance is quite well and it's better then for los 15. Dont afraid just try it.

@alex009988
I installed 120820 on My lte tablet.
This version is Working very well!
Thanks to the hardworking devs??

Can someone post a specific way to install this ROM? I would like to try it as 7.x is killing my battery and I do not use the camera anyway.
Thank You

Metoposcopy said:
Can someone post a specific way to install this ROM? I would like to try it as 7.x is killing my battery and I do not use the camera anyway.
Thank You
Click to expand...
Click to collapse
Install twrp 3.4.0, wipe system data cashe dalvik, install ROM magisk and gapps.

alex009988 said:
Install twrp 3.4.0, wipe system data cashe dalvik, install ROM magisk and gapps.
Click to expand...
Click to collapse
twrp site doesnt list any versions for Z4 tablet. Are there any links or threads taht can provide a compiled / genuine twrp link. Appreciate it.
i tried from some threads version 3 of TWRP and it didnt work on my 771

rb69 said:
twrp site doesnt list any versions for Z4 tablet. Are there any links or threads taht can provide a compiled / genuine twrp link. Appreciate it.
i tried from some threads version 3 of TWRP and it didnt work on my 771
Click to expand...
Click to collapse
Download 3.4.0 from first page of this thread.

alex009988 said:
Download 3.4.0 from first page of this thread.
Click to expand...
Click to collapse
I tried using 3.4.0 for karin_windy but the recovery wouldn't boot. Reverted back to 3.3.1 and used it to flash.

Related

[ROM][6.0.1][SM-T325] Unofficial CyanogenMod 13 for the Tab Pro 8.4 LTE

Now with working radio, thanks to kyasu. You should thank him, not me.
I am not responisble if you brick you device, if you lose all of your data or if you mess up in any other way.
Please also note that this ROM may contain bugs that I do not know about. If you find a bug, please let me know.
This ROM is made for the Samsung Galaxy Tab Pro 8.4 4G, and will not work on any other device.
This is CyanogenMod 13, based on Android 6.0 Marshmallow. This rom uses crpalmers device trees and kernel and would not have been possible without his work.
Bugs:
Auto-rotate is kind of buggy
Proximity sensor not working
Probably more.
Installation:
Do a NANDROID backup and back up all of your important files.
Wipe System, Cache and Dalvik Cache
Flash the ROM
Flash Gapps (optional)
Wipe Cache and Dalvik
Boot
Download:
http://forum.xda-developers.com/showpost.php?p=65197348&postcount=17
Device Trees:
mondrianlte: https://github.com/dens0n/android_device_samsung_mondrianlte/tree/cm-13.0
tabpro-common: https://github.com/dens0n/android_device_samsung_tabpro-common/tree/cm-13.0
Kernel:
https://github.com/cyanogenmod/android_kernel_samsung_mondrianwifi/tree/cm-13.0
Also please note that I am not an experienced developer. I am just a guy who wanted Marshmallow on the tablet, and happened to have the required skills to build a ROM. I will try to fix the SIM card, but I don't think I can do it.
If you find a bug please tell me about it. I will probably not be able to fix it, but I will let everyone else know about it.
Also, please don't ask for features. I have no idea how to implement new features.
Well to be fair Mr. Palmer had mentioned to me on the T320 thread that the Radios were broken on CM13. As I understand it I think he owns the T525 (10.1 LTE), and such work that has been done trickeled down from that.
Sadly I don't seem to have the mad chops to even get as far as that, though lord I'm trying. But, from the looks of things it seems like that bit of Code will need to be rewritten again.
Does SD card works as Internal Storage in this ROM? I'm currently using CM13 SM-T320 on my SM-T325 as I don't need LTE and radio. On crpalmer's latest nightly build 20/01/2016 for SM-T320 it works.
zdenko1 said:
Does SD card works as Internal Storage in this ROM? I'm currently using CM13 SM-T320 on my SM-T325 as I don't need LTE and radio. On crpalmer's latest nightly build 20/01/2016 for SM-T320 it works.
Click to expand...
Click to collapse
Yeah, it looks like it works.
Also, can you install SM-T320 ROMs on SM-T325? I had no idea that was possible.
DensonX said:
Yeah, it looks like it works.
Also, can you install SM-T320 ROMs on SM-T325? I had no idea that was possible.
Click to expand...
Click to collapse
Yep, they are basically same device except the SM-T325 has additional radio, 4G and earpiece. When you download ROM for SM-T320 (it might not work for all ROMs) just open zip file in winrar, navigate to /META-INF/com/google/android/ and open file updater-script with your preferred text editor. Right on the first line you command starting like this "assert (getprop("ro.product.device") == "mondrianwifi" || getprop("ro.build.product") == "mondrianwifi" || ..." (this is checking the name of device so you don't flash bad files on your device and potentially brick it)
Here you want to add your device so you can flash it - add this "getprop("ro.product.device") == "mondrianlte" || getprop("ro.build.product") == "mondrianlte". Don't forget to correctly add "||" and keep correct spaces between commands. Close text editor, resave the zip file and you can flash it on your device.
zdenko1 said:
Yep, they are basically same device except the SM-T325 has additional radio, 4G and earpiece. When you download ROM for SM-T320 (it might not work for all ROMs) just open zip file in winrar, navigate to /META-INF/com/google/android/ and open file updater-script with your preferred text editor. Right on the first line you command starting like this "assert (getprop("ro.product.device") == "mondrianwifi" || getprop("ro.build.product") == "mondrianwifi" || ..." (this is checking the name of device so you don't flash bad files on your device and potentially brick it)
Here you want to add your device so you can flash it - add this "getprop("ro.product.device") == "mondrianlte" || getprop("ro.build.product") == "mondrianlte". Don't forget to correctly add "||" and keep correct spaces between commands. Close text editor, resave the zip file and you can flash it on your device.
Click to expand...
Click to collapse
Well, damn. I wish I had known that before.
Yeah I personally can't see much use in that. Had I actually wanted the T320 (Wi-Fi ONLY) Model I could have saved me a lot of Coins on the T325 (LTE). That I'm very pro Phablet. This will never be an acceptable answer for me. But for the moment I can be happy on Lollipop (i.e. CM 12.1).
Praying hard that this ROM will be stable in future releases! Can't wait to flash it on my Tab Pro 8.0 SM-T325!
justmoto92 said:
Praying hard that this ROM will be stable in future releases! Can't wait to flash it on my Tab Pro 8.0 SM-T325!
Click to expand...
Click to collapse
Stability isn't the issue here. I think we can say with some confidence that this ROM isn't any less stable then CM 12.1. The problem hits the fan (in as far as that), when you actually want to use your T325 as a T325. (e.g. as a phone!). Apparently the Radio Stack from CM 12.1 is now broken under CM 13.0. As such what we have to accept is that there really is next to zero support for either the T325 (8.4), or the T525 (10.1) both LTE PROs.
Really we owe Mr. Palmer a huge debt in just giving us CM 12.1. But until someone, anyone can do a rewrite on the Radio Stack there won't be a CM 13 for us. And, as I pointed out outside of Mr. Palmer we don't have as many Devs as the T320 (Wi-Fi) has
justmoto92 said:
Praying hard that this ROM will be stable in future releases! Can't wait to flash it on my Tab Pro 8.0 SM-T325!
Click to expand...
Click to collapse
I wouldn't get my hopes up. SIM support probably won't be fixed for a while, if at all. Also there won't be nightlies or anything, and I will likely prioritize some other ROM in the future, probably MinimalOS, as I don't really like Cyanogenmod.
New Update
New update is here. Still no SIM-support, but you can now access Mobile network settings, which hopefully is a step in the right direction (but don't get your hopes up). You can now also access Security settings, which caused the settings app to crash in the previous one.
Download: https://drive.google.com/open?id=0Bxf2YUR9_3hDREExdzljcUxZV1k
Just outta interest would it be possible to compare a working Marshmallow Qualcomm Stack to the one on the Tab PRO? If, not outright stealing it for the Tab PRO? Or is it really not just as simple as that?
Ichijoe said:
Just outta interest would it be possible to compare a working Marshmallow Qualcomm Stack to the one on the Tab PRO? If, not outright stealing it for the Tab PRO? Or is it really not just as simple as that?
Click to expand...
Click to collapse
I'm not actually good at ROM... stuff, so I am pretty much as clueless as everyone else, but I did use some code from the Tab S in the latest update, so I am going to keep trying that and see if it leads to anything good.
I know it's probably already been done/thought of @crpalmer but is there that much of a difference between the T325 and the Galaxy Tab S version (the T705) that, sections of CM13 could not be used with our T325?
RavenY2K3 said:
I know it's probably already been done/thought of @crpalmer but is there that much of a difference between the T325 and the Galaxy Tab S version (the T705) that, sections of CM13 could not be used with our T325?
Click to expand...
Click to collapse
I guess until someone tries well never know. Sadly it seems that this was - is a Device that has completely fallen though all the cracks. That most of the Devs here seem to be more focused on the cheaper T320 should be a very sad clue as to the future of both the T325 & T525.
I'm not even sure if its even possible to even rewrite these Drivers, as I understand it the Radio Stack(s), are pretty much the holly of Hollies in proprietary closed source regarding corporate secrets, and the need to prevent such exposure to the GSM code to such exploits to get free LTE or calls.
cm-13.0-20160207-UNOFFICIAL-mondrianlte.zip
Here is my port. Radio (call and mobile data) is working.
Download: cm-13.0-20160207-UNOFFICIAL-mondrianlte.zip
https://www.androidfilehost.com/?fid=24407100847292993
Sources:
https://github.com/kyasu/android_device_samsung_mondrianlte
https://github.com/kyasu/android_vendor_samsung_mondrianlte
Is really working the data ? If radio works you are a good developer. Thanks
Enviado desde mi SM-N920C mediante Tapatalk
kyasu said:
Here is my port. Radio (call and mobile data) is working.
Download: cm-13.0-20160207-UNOFFICIAL-mondrianlte.zip
https://www.androidfilehost.com/?fid=24407100847292993
Sources:
https://github.com/kyasu/android_device_samsung_mondrianlte
https://github.com/kyasu/android_vendor_samsung_mondrianlte
Click to expand...
Click to collapse
Wow! Awesome job, man. It works perfectly!
This rom is bug free. This is a great news. Tnks kyasu you are the man.
Enviado desde mi SM-N920C mediante Tapatalk

[ROM][7.0.0_r1] Decrypted+Debloated AOSP Nougat Build

Hey XDA!
This is just a quick build of AOSP Nougat that I though I should upload and share. It's just pure AOSP with a modified fstab and a bunch of the useless apps removed. While it does boot, the main problem is that there aren't any gapps available, so there is little functionality.
Instructions:
1. Flash vendor.img
2. Flash ROM zip
3. Boot up
Downloads:
Unofficial vendor.img: http://oceighty.co/ Created and uploaded by @xanaxdroid
ROM zip: https://basketbuild.com/ Build and uploaded by me.
DISCLAIMERS:
I'm not responsible for any mishaps you have.
This is simply a courtesy upload, do not expect updates.
The vendor.img was pulled from the OTA and is not an official factory image.
is it rooted?
The latest TWRP version functions with Android N, it now correctly decrypts the phone (yes, I'm aware this ROM is pre-decrypted). You can flash SuperSU through that and then download most of the needed GApps from APKMirror, I know Android N preview GApps were uploaded there.
confused... so I could just flashed this like a regular rom? would my internal disk erase? is this rooted?
you guys need to read the OP and stop asking senseless questions
"It's just pure AOSP with a modified fstab and a bunch of the useless apps removed"
Lol, this is why I wish rooting wasn't just a click away. I miss the old days where you actually had to know what you were doing to root the damn thing like actually being familiar with adb I doubt half the people that root haven't used shell period. Point being that the people that did it knew the ins and outs of what they were doing and there wasnt all this clutter. people used to actually do the time to research and educate themselves on what was going on now it's all entitlement give me give me i don't understand oh blah blah won't work fix it for me anyway this isn't helpful or constructive please delete goodnight
Sent from my Nexus 6P using Tapatalk
Interesting ROM. :good:
Opengapps.org should have 7.0 gapps very shortly. The August 24th build for arm has 7.0, but 8/24 hasn't built for arm64 yet.
Sent from my Nexus 6P using XDA-Developers mobile app
First to market ROM nice!
hibby50 said:
Opengapps.org should have 7.0 gapps very shortly. The August 24th build for arm has 7.0, but 8/24 hasn't built for arm64 yet.
Click to expand...
Click to collapse
ARM64 builds for 7.0 are now available for flashing.
Why do people prefer decrypted roms, what is the advantage?
rest0ck said:
Why do people prefer decrypted roms, what is the advantage?
Click to expand...
Click to collapse
One reason should be faster "iops" I presume.
Skickat från min Nexus 6P via Tapatalk
That was fast, OP your pic looks alot like this dude.
Hm okay I see, thanks.
Can I encrypt it again if I want to?
Also I thought the Source of Android N is not released yet (delevopers.google.com) so where is this source from exactly?
.. Okay I just looked it up. So is there a difference between this one and the official OTA update? I really want to flash another ROM because my Dirty Unicorn is just a mess at the moment.
Iceburn1 said:
That was fast, OP your pic looks alot like this dude.
Click to expand...
Click to collapse
Oh wow! I've never seen that guy around the forums, but you're right!
rest0ck said:
Why do people prefer decrypted roms, what is the advantage?
Click to expand...
Click to collapse
Faster boot, slightly faster I/O (although there isn't too much of a difference).
Thank you for the answer.
Can someone confirm that flashing the lastest SuperSU beta works? http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So basically flashing this ROM + Vendor + ARM64 GApps + SuperSU = Android N, decrypted, rooted, with gapps?
How'd you even build this? I synced r1 and tried a build last night and it wouldn't build (for the 6p). The website doesn't show 6p as included in r1 yet
rest0ck said:
Thank you for the answer.
Can someone confirm that flashing the lastest SuperSU beta works? http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So basically flashing this ROM + Vendor + ARM64 GApps + SuperSU = Android N, decrypted, rooted, with gapps?
Click to expand...
Click to collapse
The latest Beta SU works with 7 NRD90M
rest0ck said:
Thank you for the answer.
Can someone confirm that flashing the lastest SuperSU beta works? http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So basically flashing this ROM + Vendor + ARM64 GApps + SuperSU = Android N, decrypted, rooted, with gapps?
Click to expand...
Click to collapse
Not really, no. The ROM isn't technically decrypted at all. It just doesn't force encryption. So if you were encrypted prior to flashing you would still be encrypted. The only way to decrypt is to format userdata. The advantage of a ROM not forcing encryption (or being incorrectly labelled as decrypted in this case) is that if you were previously decrypted the kernel won't encrypt your storage on the first boot.

[2017-10-23][7.1.2] LineageOS 14.1

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!

[ROM][9.0][STABLE][Z3] LineageOS 16.0 for Sony Xperia Z3

[CENTRE]LineageOS 16.0 for Sony Xperia Z3[/CENTRE]
LineageOS
MrTapok(4PDA) said:
[CENTRE]LineageOS 16.0 for Sony Xperia Z3[/CENTRE]
LineageOS
Click to expand...
Click to collapse
Where is the rom? I don't find it on the Lineage OS Download site.
dhacke said:
Where is the rom? I don't find it on the Lineage OS Download site.
Click to expand...
Click to collapse
In 4Pda - https://4pda.ru/pages/go/?u=https:/..._3R2kJYJEKD7C5cz14y7xPaD_6pG5xCe1c&e=85694788
The ROM is stable for now, but LED does not work
Edit: The latest update is
https://4pda.ru/pages/go/?u=https:/...wP5wW3d0p-KKCJB8Bnc7ZD9PxOYS_heLV8&e=85750587
1. Video record not work
2. AudioFX not work
3. Hotspot not work
4. Developer option crash
Worst thread ever created. Ever.
Tux111 said:
Worst thread ever created. Ever.
Click to expand...
Click to collapse
Original thread on 4pda...
@ronidianpatisa @MrTapok(4PDA) maybe linking it? writing some infos about? neither 3 years old kid could create such a bad/disinformative post.
---------- Post added at 11:03 AM ---------- Previous post was at 11:02 AM ----------
[/COLOR @ronidianpatisa @MrTapok(4PDA) maybe linking it? writing some infos about? neither 3 years old kid could create such a bad/disinformative post.
Good evening.
First of all sorry to misuse this thread but it seems pretty dead anyway and the topic is good.
My name is arian and I am working on LineageOS 16 for the Z3 Compact. I'm trying to get it official soon, therefore we would like to also ship Z3, since I don't have this device I haven't shared builds yet and the possible device maintainer is busy right now I would love to get a quick test already.
Would anyone be able to do me a favour and test the LineageOS 16 build + the twrp from here: https://sourceforge.net/projects/ephedraceae/files/z3/ ?
I can't guarantee _anything_ about the stability of this build and the actual possibility of official builds. That would just be my personal target.
After all the build should work pretty good (as my z3c builds - https://forum.xda-developers.com/z3-compact/orig-development/9-lineageos-16-0-z3c-t3886777 ).
Encryption and Decryption should work as long as the data is formatted with my twrp build.
Device Specific sources can be found here: https://github.com/z3c-pie/
Happy flashing
NeoArian said:
Good evening.
First of all sorry to misuse this thread but it seems pretty dead anyway and the topic is good.
My name is arian and I am working on LineageOS 16 for the Z3 Compact. I'm trying to get it official soon, therefore we would like to also ship Z3, since I don't have this device I haven't shared builds yet and the possible device maintainer is busy right now I would love to get a quick test already.
Would anyone be able to do me a favour and test the LineageOS 16 build + the twrp from here: https://sourceforge.net/projects/ephedraceae/files/z3/ ?
I can't guarantee _anything_ about the stability of this build and the actual possibility of official builds. That would just be my personal target.
After all the build should work pretty good (as my z3c builds - https://forum.xda-developers.com/z3-compact/orig-development/9-lineageos-16-0-z3c-t3886777 ).
Encryption and Decryption should work as long as the data is formatted with my twrp build.
Device Specific sources can be found here: https://github.com/z3c-pie/
Happy flashing
Click to expand...
Click to collapse
Word is very well, thank you for the work that you have done for our device
Good Job
NeoArian said:
Good evening.
First of all sorry to misuse this thread but it seems pretty dead anyway and the topic is good.
My name is arian and I am working on LineageOS 16 for the Z3 Compact. I'm trying to get it official soon, therefore we would like to also ship Z3, since I don't have this device I haven't shared builds yet and the possible device maintainer is busy right now I would love to get a quick test already.
Would anyone be able to do me a favour and test the LineageOS 16 build + the twrp from here: https://sourceforge.net/projects/ephedraceae/files/z3/ ?
I can't guarantee _anything_ about the stability of this build and the actual possibility of official builds. That would just be my personal target.
After all the build should work pretty good (as my z3c builds - https://forum.xda-developers.com/z3-compact/orig-development/9-lineageos-16-0-z3c-t3886777 ).
Encryption and Decryption should work as long as the data is formatted with my twrp build.
Device Specific sources can be found here: https://github.com/z3c-pie/
Happy flashing
Click to expand...
Click to collapse
Your work is going well on my Z3 D6603 device, and everything works, but the display size is too small, so I have to adjust it via the display settings
I hope you can continue to develop it for Z3 devices
I thank you very much and immediately create a new thread on XDA for this project
NeoArian said:
Good evening.
First of all sorry to misuse this thread but it seems pretty dead anyway and the topic is good.
My name is arian and I am working on LineageOS 16 for the Z3 Compact. I'm trying to get it official soon, therefore we would like to also ship Z3, since I don't have this device I haven't shared builds yet and the possible device maintainer is busy right now I would love to get a quick test already.
Would anyone be able to do me a favour and test the LineageOS 16 build + the twrp from here: https://sourceforge.net/projects/ephedraceae/files/z3/ ?
I can't guarantee _anything_ about the stability of this build and the actual possibility of official builds. That would just be my personal target.
After all the build should work pretty good (as my z3c builds - https://forum.xda-developers.com/z3-compact/orig-development/9-lineageos-16-0-z3c-t3886777 ).
Encryption and Decryption should work as long as the data is formatted with my twrp build.
Device Specific sources can be found here: https://github.com/z3c-pie/
Happy flashing
Click to expand...
Click to collapse
@NeoArian
That are great news. Many thanks for your effort. I hope your builds will be better maintained than the other Pie roms for our z3 because aside from Carbon the majority of pie roms in last months are uploaded here and than abanded.
I will install your rom and twrp today evening and report when i find any issues. Thx again for your work.
@NeoArian
Well I installed your uploaded twrp, made a wipe (system + data + Caches) to uninstall the previous rom and then install your lineage build.
At least by me the encryption doesn't work (as in the latest CR 7.0 builds).
It shows for a moment the Android men when i start the encryption process in the settings, then the screen is black and I'm back at the lineage mainscreen.
Result: No encryption.
Or did i something wrong in my procedure?
Very stable for me on D6603
dhacke said:
@NeoArian
Well I installed your uploaded twrp, made a wipe (system + data + Caches) to uninstall the previous rom and then install your lineage build.
At least by me the encryption doesn't work (as in the latest CR 7.0 builds).
It shows for a moment the Android men when i start the encryption process in the settings, then the screen is black and I'm back at the lineage mainscreen.
Result: No encryption.
Or did i something wrong in my procedure?
Click to expand...
Click to collapse
You definitely have to format the data partition within my twrp, not just wipe it for working encryption.
Im wipe all partition with twrp @NeoArian and flash Lineageos 16 + Gapps
NeoArian said:
You definitely have to format the data partition within my twrp, not just wipe it for working encryption.
Click to expand...
Click to collapse
Yes! That was the trick. Big thanks @NeoArian.
Now the encryption works.
Mayby the wipe was my think issue at the carbon builds, too. So when i test it on Carbon would that be the correct procedure?
1. Format the data in your twrp
2. Wipe system and Caches
3. Install Carbon and boot it
4. Go in your twrp and make again a data formatting
5. Boot Carbon and start the encryption process.
dhacke said:
Yes! That was the trick. Big thanks @NeoArian.
Now the encryption works.
Mayby the wipe was my think issue at the carbon builds, too. So when i test it on Carbon would that be the correct procedure?
1. Format the data in your twrp
2. Wipe system and Caches
3. Install Carbon and boot it
4. Go in your twrp and make again a data formatting
5. Boot Carbon and start the encryption process.
Click to expand...
Click to collapse
That's too complicated, just install my twrp format data, wipe the other partitions then reboot twrp and flash the ROM.
NeoArian said:
That's too complicated, just install my twrp format data, wipe the other partitions then reboot twrp and flash the ROM.
Click to expand...
Click to collapse
Thx the steps worked. Now i am happy?
@NeoArian
The volume call was too strong, although it's in the smallest volume...
How to flash this recovery? Now I have version 3.2.3-0

[ROM][LineageOS][Android 11.0.0_r46]TugaPower™ 2.0

Build 02/06/2023 #OPO
Telegram Group: https://t.me/TugaPowerOPO
#TugaPower R 11.0.0_r46 1.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Please be sure you are using one TWRP that can handle firmware flash
Advise to use latest official TWRP
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is pico package since nano its now too big to install ( ARM):
OTA built in on rom for updates easly
Three fingers screenshot ( enable in settings over gestures options )
Support out of the box to microG GmsCore ( https://forum.xda-developers.com/t/...oftware-clone-of-google-play-services.3217616 )
No more need to make microG system app
PoGO: Gonna catch then all ( Always report using real GPS in case of mock location been used )
Nethunter/Kali supported
What does not works:
Let me know to add to second post
Download: https://cld.pt/dl/download/16e0f9e9-8f40-4f8d-8142-46bf5088f201/TugaPowerR2_OP1.zip
MD5: f064915c3dbb1fc4cc3d1fae0b62a623
Please dont mirror for now the roms zips, thanks
Sources :
Rom:- https://github.com/LineageOS
Device:- https://github.com/LineageOS/android_device_oneplus_bacon
Kernel:- https://github.com/LineageOS/android_kernel_oppo_msm8974
Place HOLDER for bugs !
Down link not working.
Gold Ribbed said:
Down link not working.
Click to expand...
Click to collapse
Fixed, bad copy paste, thanks for reporting that !
I have one question, does this rom supports DRM content and apps based on it?
Thanks for this Rod. Working good for me.
Not too much different from normal LoS but appreciated, thanks for keeping the OPO alive. Checked it out and everything is working smoothly, no major bugs, crashes or anything so far.
oneplusausage said:
Not too much different from normal LoS but appreciated, thanks for keeping the OPO alive. Checked it out and everything is working smoothly, no major bugs, crashes or anything so far.
Click to expand...
Click to collapse
Thats normal, the base it self its Los, the diference its on having 3 finger screenshot, microg nogapps support, nethunter support and mock locations apps the system report real GPS instead of mock app ( Pokemon will not ban for using mock location app ), support for face unlock its WIP ( no eta )
Hi, I've read somewhere that for new roms (Starting from Android 10) need to resize system partition. I've currently run 7.1.2 Rom, do I need to do the resize for this ROM? Thanks!
saphta said:
Hi, I've read somewhere that for new roms (Starting from Android 10) need to resize system partition. I've currently run 7.1.2 Rom, do I need to do the resize for this ROM? Thanks!
Click to expand...
Click to collapse
If the rom fail to flash its because you need to make that, but on OPO if you did not messed with the partitons before you will be probably just fine flashing and no need to resize. The issue is not really rom problem, the problem its when flashing gapps that will ask for more space, but that is most for bigger gapps packaging, it you use the nano or base package you will have no issues flashing. Sorry for late answer mate !
Hi Daniel, thanks for your reply! Will probably use a pico gapps package. Anyone used MindTheGapps?
saphta said:
Hi Daniel, thanks for your reply! Will probably use a pico gapps package. Anyone used MindTheGapps?
Click to expand...
Click to collapse
One or another should be fine, if use open gapps pick the small package and then install the rest trough Play Store !
Will do! thank you very much!
I'm not able to flash opengapps pico : error 70
I tried to resize system partition but not being able...
@danieldmm can you help me?
@danieldmm
I can confirm what amadeumagalhaes wrote above. Gapps pico won't install.
I've installed Magisk, got root and I tried deleting some system files to make more space but all apps I've used gave me the same message: uninstall failed. I used SD Maid, System app remover, My Android Tools.
Any ideas?
P.S.1 Instead of opengapps pico, I've flashed mindthegapps. No issues flashing it even if it's larger than opengapps pico. The issue with deleting system files remains unchanged.
Hi all,
Found one bug, after installing Signal. On video calls, my video is overexposed. Anyone else has this problem?
saphta said:
Hi all,
Found one bug, after installing Signal. On video calls, my video is overexposed. Anyone else has this problem?
Click to expand...
Click to collapse
A bunch of us had this same problem with @Tomoms ROM. He managed to fix this in recent releases.
I have no issues on whatsapp. On Tomoms ROM thread it says to restart the app until the overexposure is gone.
Well, its being a while guys, updated OP with 2.0 build done today.
TugaPower R 2.0 2023/06/02
https://cld.pt/dl/download/16e0f9e9-8f40-4f8d-8142-46bf5088f201/TugaPowerR2_OP1.zip
MD5: f064915c3dbb1fc4cc3d1fae0b62a623
If you have still 1.0 you cannot use OTA since the system its down, to use OTA you need to update the Updater you have on 1.0, will drop on bottom a update apk of Updater if you are on 1.0 and prefer to use OTA, just install as regular app updating the system one. And then use the built OTA to update from 1.0 to 2.0, you can also check the change log after updating the updater, its too big to post here, it have all the changes commited to lineageos since my last build. Enjoy guys, long live to OPO

Categories

Resources