Develop Bugs

03/04 [ROM] Unofficial CM13 Nightlies d2att Android 6.0.1 Marshmallow

Update: my s3 broke, so I won't be posting new builds anymore...
Matrixzone's releases are probably of higher quality than mine, but I try to update nightly. Here's his thread if you're interested
[url]http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854 [/url]
My builds for now are straight from CM source and have been unchanged because I haven't learned how to cherry pick yet. Honestly, it's a miracle that my builds are even working right now
Update: I'm compiling builds again!!! I'll try to do them nightly as always
Downloads:
If you're downloading on mobile, request the desktop version on mega.nz
That way, you don't need to download the megasync app
03/04 [url]https://mega.nz/#!YdNx2ZQQ!AnBDi09ldadvGIocvPPHVF2VgpO763xB8c_jZeiMdLw [/url]
03/03 [url]https://mega.nz/#!AJkQlLqL!lPkCRlUEaPB7YDuvpziMUHPKZpb4KUqWOLqaSRFj65I [/url]
**no 03/02 build**
03/01 [url]https://mega.nz/#!hAdT2KIT!sBR_xNymClhjBHHWFSwuBNlGXpHR_ZFYyMPnfcNfNh0[/url]
**no dowloads in between these dates**
01/16 [url]https://mega.nz/#!QcFzBQSQ!gxew9-wyBfulCVr5eejbMFU9Kk4zzpqsBydntCWHrqM [/url]
01/07 [url]https://mega.nz/#!lQVVjTyb!WEV98HcbfLGZ_wmS8LVJCuMpKRsiodXHkpOJyB0vMig [/url]
01/06 [url]https://mega.nz/#!5VchxYDT!hNDmqxP9-RauNPtW4MPufyz07JGkMx7wJQEg9oHFT88[/url]
01/05 [url]https://mega.nz/#!QdVRiK7T!0I-OoxA9r2q9EkDHJ43znAdjkvdPyZ6ge6Flp5mlsmk[/url]
01/04 https://mega.nz/#!kRdxGD4B!2-_kzo9mK3bJwzd-Om0P5h5LhTqV1IJ1IJU7xVnlg9o
01/03 [url]https://mega.nz/#!9dUiXL5J!z0DKXE1CvGvR5Fkwn7XTjECkW5-zCXGU-MZ9UzlDsFk[/url]
01/02 [url]https://mega.nz/#!IQkh2Zgb!NinrEa1o3dOAKpKZ3XNvNrcJpIEsDfS-y-HTghLOK8A[/url]
12/30 https://mega.nz/#!AU1iwTzA!k_3YZTaR...HJ43znAdjkvdPyZ6ge6Flp5mlsmkYWxsX_UMrAJ9bKtKs[/url]
12/29 https://mega.nz/#!9Q9AmY4J!mOWp4d8n7mjKCjKqzmBZWtnsRM7QwxhyaBaVF3qFXDY
12/28 [url]https://mega.nz/#!Ed8AxKhQ!xReR_gjgq5a8BQmAIn6WlJ7GSyioaGxTwnJOL-PiKu8 [/url]
Gapps (choose arm 6.0):
[url]http://opengapps.org/ [/url]
What's not working:
Network Issues fixed!!!
You tell me​
Special thanks to these people for helping me figure things out:
@jason2678 (for teaching me how to use themuppets)
XDA:DevDB Information
Unofficial cm13 by Arunscape, ROM for the AT&T Samsung Galaxy S III
Contributors
Arunscape
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2015-12-28
Last Updated 2016-01-02
XDA:DevDB Information
Unofficial cm13 by Arunscape, ROM for the AT&T Samsung Galaxy S III
Contributors
Arunscape
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Current Beta Version: 6.0.1
Beta Release Date: 2016-01-05
Created 2015-12-28
Last Updated 2016-03-03

reserved

I'll try to help you figure out the sim issue. I'll be in touch soon ? gotta get to bed, work comes early.

canodroid15 said:
I'll try to help you figure out the sim issue. I'll be in touch soon gotta get to bed, work comes early.
Click to expand...
Click to collapse
I got the network issue fixed by setting up themuppets with an edit to roomservice.xml (before, I just used the extract-files.sh and connected my phone lol)

I just got a build error:
make: *** [/home/arunscape/cm13/out/target/product/d2att/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1
make: Leaving directory '/home/arunscape/cm13'
#### make failed to build some targets (01:39:11 (hh:mm:ss)) ####
It looks like something's wrong with the recovery?
update: my source code got all messed up after a power loss while compiling the rom, so I just deleted the source and redownloaded the entire source again..

I am really excited to see another dev (even if you are a n00b) building cm13 for the s3. Thanks a bunch. I can't wait to try it ... Probably will flash tonight waiting for the ball to drop. Do you see flaky cellular data in your builds?
-J

Hey man, I've been super duper slammed with work but I just wanted to drop in & say kudos! Glad you got the builds rolling & the sim issue fixed. I'll be following your progress. Oh, and Happy new year! ?

Thanks for your support! Also I resolved the issue with the build errors that I was getting! Turns out that the entire source code gets messed up if you lose power in the middle of compiling a build...
I will post a build for January 2 soon! (though I haven't tested it yet.. I'll report back when I have flashed it.)

miatawnt2b said:
I am really excited to see another dev (even if you are a n00b) building cm13 for the s3. Thanks a bunch. I can't wait to try it ... Probably will flash tonight waiting for the ball to drop. Do you see flaky cellular data in your builds?
-J
Click to expand...
Click to collapse
I can't test data, because I don't have a data plan with my carrier, but SMS and calls work no problem :good:

already uploading 01/04 build as I type right now!

Sorry I haven't uploaded a new build yet. Exams are happening right now so my uploads will slow down a lot.

So for folks who are using this, how's it working? Anybody finding bugs/issues? Thinking about making the jump from CM12 but need something stable..

so It's been a while since my last upload but I got one coming!

privatedoodle said:
So for folks who are using this, how's it working? Anybody finding bugs/issues? Thinking about making the jump from CM12 but need something stable..
Click to expand...
Click to collapse
If you want something more reliable, try matrixzone's ROM but I haven't seen any differences between our builds. Also, it's been a long time since he has updated his ROM http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
I am currently running the builds that I am building on my daily driver and they seem to be working fine

I'm coming back to the S3 after a year with a OnePlus, so there's a good chance I've missed something important.
The CM12 nightlies work just fine, but I can't get either this version of CM13 or the matrixzone version to boot. I wipe everything, install ROM, OpenGapps, and SuperSU, wipe cache/dalvik, and reboot. It hangs on the boot screen for over an hour before I give up and shut it down.
Am I missing something? A new bootloader maybe?

privatedoodle said:
I'm coming back to the S3 after a year with a OnePlus, so there's a good chance I've missed something important.
The CM12 nightlies work just fine, but I can't get either this version of CM13 or the matrixzone version to boot. I wipe everything, install ROM, OpenGapps, and SuperSU, wipe cache/dalvik, and reboot. It hangs on the boot screen for over an hour before I give up and shut it down.
Am I missing something? A new bootloader maybe?
Click to expand...
Click to collapse
Nevermind, it seems SuperSU was the problem. Booting fine without SuperSU.

SuperSU version. 2.66 works fine for me, but not the google play store version. You can get it here http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Anyone using their S3 with Marshmallow as a DAP/Transport. Does the USB Audio work? I moved my LG Pad 7.0 to Marshmallow and the USB Audio doesn't work. So I am looking for another alternative. Any information would be great on the USB Audio status

baseband - IMEI - SN is missing with this rom...
SGH-I747M

Does the camera work with this build?

[ROM][6.0.1] LineageOS 13.0

LineageOS 13.0
Marshmallow - Android 6.0
​
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Additional Information:
maguro wiki page
toro wiki page
toroplus wiki page
Download:
The latest builds & changelogs are available at
https://download.lineageos.org/maguro
https://download.lineageos.org/toro
https://download.lineageos.org/toroplus
Extras:
su (arm)
su removal (arm)
Google Apps can be found at http://opengapps.org/?api=6.0&variant=pico - beware that only the pico version will fit, unless you change your partition sizes! Also, starting from M, it's recommended to install gapps before the initial boot so the permissions are properly set up.
Bugs:
- Sometimes, quiet speaker pop sounds can be heard at the beginning and/or end of some audio streams (ie. touch sounds - the workaround is to disable them). For some reason, this isn't affecting everyone.
- Report back anything else you find which isn't listed here
FAQ:
Does this ROM supports F2FS?
- Yes, on /data and /cache - although /cache F2FS support might get removed in the future, as it's worthless.
Does this ROM uses DDK 1.9?
- Yes, with all the camera issues (ie. pink lines, rare crashes) resolved.
Why does the initial boot take so long, and where are my live wallpapers?!
- To make room on the system partition for the (bigger) M gapps packages, I had to sacrifice dexpreopt and the live wallpapers. This can result in pretty long initial boots or upgrade boots, and dexpreopt might run during the first time setup wizard as well, slowing down the system for an additional couple minutes.
Will you release newer ZMoD builds or something?
- Yes, as soon as the memory optimizations are finalized and I find enough time...
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
LineageOS 13.0, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi, Everyone else who helped me: AOSP, Hashcode, ...
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2016-02-11
Last Updated 2018-12-30

Does it have more ram 802 like the kernel used in cyanogenmod 12.1 you posted? Thank you!!!

Awesome!
Enviado desde mi GT-I9300 mediante Tapatalk

Thank you!!

AOSP Keyboard keeps crashing.. Apart from that everything seems to be working. Will check for more bugs in the meantime

Extraordinary work!!
PD: Device doesn't receive Internet connection. My ISP is Oceans Network from Spain.

You are a king!
Running on it for 1 hour, and already impressed... WOW !!!

Works perfectly
Works great! No problems at all and have been running it for 3hrs. Have xposed also installed. Great work!
I will continue to use and report any bugs i encounter.

great...Testing this rom right now. I had to rewipe,since installing gapps after the rom boot cause google play service to crash. I really wish there will be an official cm13 for galaxy nexus.I have a nexus 5 but I like galaxy nexus design and amoled screen...
Edit: this ROM runs very well,maybe a little better than other ones based on marshmallow

How much free ram? Is it 802mbytes or 762?in cn 12.1 there was a kernel boot img by zuyan that gave 802 mbytes of ram

Good job @Ziyan
Please guys, can anyone link me that kernel? I can't find it

Need suggestion, rootexplorer shown no root on this rom, how do i.
I try to flash ROM with TWRP, then fix root permission. @Ziyan could you please create this ROM support CWM.

Having random reboots now, is this happening to anyone else?

Reboots? Not yet
Gesendet von meinem Galaxy Nexus mit Tapatalk

@Ziyan can i flash kernels for lollipop like the one you posted on cm 12.1 recently?

NightWolf1396 said:
Having random reboots now, is this happening to anyone else?
Click to expand...
Click to collapse
Logs?
nikodr said:
@Ziyan can i flash kernels for lollipop like the one you posted on cm 12.1 recently?
Click to expand...
Click to collapse
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time

Ziyan said:
Logs?
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Click to expand...
Click to collapse
Will get them as soon as I get home

Ziyan said:
Logs?
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Click to expand...
Click to collapse
I will try zImage in my AOSP rom thanks can i use it no ?
Also there is no git commit for this extra RAM netither in OMAP4-AOSP or Ziyann github

werty100 said:
I will try zImage in my AOSP rom thanks can i use it no ?
Also there is no git commit for this extra RAM netither in OMAP4-AOSP or Ziyann github
Click to expand...
Click to collapse
Using the zImage on any DDK 1.9 / Android 6.0.1 ROM should be fine.
There is no git commit because I didn't push it yet (the values aren't final), but to get the same kernel I uploaded:
Clone https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-13.0, and apply this, but with the following values:
CONFIG_ION_OMAP_TILER2D_SIZE=72
CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE=32
uji_sine said:
Need suggestion, rootexplorer shown no root on this rom, how do i.
I try to flash ROM with TWRP, then fix root permission. @Ziyan could you please create this ROM support CWM.
Click to expand...
Click to collapse
Enable root the same way you did it on CM12.1: enable developer settings, then you'll find the root option there. And just forget about CWM... don't use fix permissions and friends, as it might cause problems.

Ziyan said:
Using the zImage on any DDK 1.9 / Android 6.0.1 ROM should be fine.
There is no git commit because I didn't push it yet (the values aren't final), but to get the same kernel I uploaded:
Clone https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-13.0, and apply this, but with the following values:
CONFIG_ION_OMAP_TILER2D_SIZE=72
CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE=32
Click to expand...
Click to collapse
I try before with zImage but rom was no booting i will try alter with commits thanks and kernel source

[ROM][ALPHA][7.1.1][23/12/16][UNOFFICIAL]CyanogenMod 14.1

DISCLAIMER
Code:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.​
Steps to install:
(0. Install any 6.0 rom)
1. Factory reset
2. Make sure you format /system and /data to ext4 for the install
2. Install ROM zip, you will get a warning about partition size change of system if its the first time you flash, just flash it a second time to confirm the change, this will erase your data partition!
3. Please do NOT install Gapps (you can still do it, but at your risks)
4. Reboot
5. Wait for a long time
Known Bugs:
- First boot is slow
- RIL sudden crash (?)
- Webkit render issues with the latest cm14.1. It will be fixed in the next build.
- CM's FileManager is bugged
Features:
- Stock Cyanogenmod 14.0
- Dirty CoW patched kernel (anyone cares ?)
- kernel built with GCC 6.2.1 with -03
- F2fs support on /data but not on /system
- Bigmem enabled (no cma for now)
- sdcardfs support to come someday
- Zram enabled
Please note that this rom is not ready for daily usage yet, it's an alpha.​
Downloads:
Android 7.0:
http://www.mediafire.com/file/5d1fdr0f75rywml/cm-14.0-20161120-UNOFFICIAL-galaxysmtd.zip
Android 7.1.1:
http://www.mediafire.com/file/xfcjvn1y1vjwwpu/cm-14.1-20161223-UNOFFICIAL-galaxysmtd.zip
I will provide mirrors later if needed.
Please check the MD5 !
094fa2133073f22cea28e80d18a628e5
HUGE thanks to @xc-racer99 for his AMAZING work on his variant, without him, this woudn't have been possible at all.
XDA:DevDB Information
CyanogenMod 14.0, ROM for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99, sooti
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2016-10-28
Last Updated 2016-12-23

Reserved
Changelog:
23/12/2016
Android 7.1.1 r6
No more crashes due to the graphic driver
Working ril (except data on the first boot apparently ?)
Fixed internal storage issues
Updated kernel
Latest TWRP (without their new app, tell me if you want me to add it back)
20/11/2016
Latest CM 14.0
As people wanted, cmc is back
Tweaked art settings (lag should be gone)
Fixed video recording
Fixed MTP crash
Fixed adb authkey issue
Disabled SDcardFS
More stable RIL (but there are still issues with 3g)
28/10/2016
Initial release

Reserved
FAQ & tips :
Where is SuperSU ?
You don't need to flash SuperSU, just enable it under the Developer options.
How to change Bigmem modes ?
You can change it in advanced parameters>Bigmem
What are the best schedulers/governors/...
That's up to you, personaly, I like the combinaison of smartassV2 and bfq.
But ... how to change them ???
You can use Kernel Adiutor or any other app like that.
When will you release the next build ?
Don't ask for ETA ..... and wait.
Something isn't working, please fix it, please PLEASE
Logcat. No logcat == no fix.
If you don't know how to logcat properly, read this.
My phone is bootlooping ,what can I do ?
Pull battery and restart. Also don't forget to do a factory reset before flashing this rom.
Can you add X feature on your rom ?
No. I wont add additional features, this is stock cm. The only thing I might add is signature spoofing support.
Here are a few additional tips to get the most of this rom :
Format /data in f2fs in TWRP
OC your cpu if it can handle it
Use Bigmem
Don't install unnecessary apps
Remove apps from startup
(Wait for the next build)

Wow!!! It is impossibly! Big thanks!!!

+1
:good:

Link is up, make sure to check the md5sum and tell me if you experience issues.
Logcats appreciated !

Ok, just tested it. Was compared with AOSP 7 from x-racer99.
Seems CM14 more laggy in games. Not so smooth like an AOSP. But problem probably is not in the kernel. Cause i was also use x-racer99 kernel on your CM14 rom. Look at this videos with Mega Jump game:
https://youtu.be/ueyjuPu3BgA AOSP rom by x-racer99
https://youtu.be/FWbCNKZdAdE Cyanogenmod 14 rom with x-racer99 kernel.
Second video is not so smooth with a lot of jerks. May be problem in low memory killer settings, or GFX drivers, or V-Sync, or build.prop tweaks, i do not know.

Also i prefer CMC instead Voodoo Color. Because VoodooColor have two bugs since android 2.x.x. It is yellowish tint of all screen (CMC have more right white balance) and green bug on low backlight with high gamma settings, look at this video:
https://youtu.be/gkP7VgWbTlY

Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
About CMC, you can tweak voodoo by yourself, but yeah if many people want me to switch to CMC, I will do it.

Coldwindofnowhere said:
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
Click to expand...
Click to collapse
You can just download Subway Surfer from market or another place and try to make run this game more smoother. Some times Subway Surfer have bad responce on touch and can hung up after long play. Also can try this on Mega Jump or other dynamic game.
Thank you!

Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...

First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
P.S. Issue with MXplayer was resolved by itself after reboot phone.

M1n3cr4f7.G4m35.2015 said:
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
Click to expand...
Click to collapse
Um pull off the battery, start the phone again. Got this issue once but no idea why.
jupiter5700 said:
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
Click to expand...
Click to collapse
Bigmem patched, I haven't tested 720p videos tbh.

This rom can run on samsung wave?

thinhx2 said:
This rom can run on samsung wave?
Click to expand...
Click to collapse
I haven't tried but as it's really similar to the i9000, you should give it a try.

Coldwindofnowhere said:
I haven't tried but as it's really similar to the i9000, you should give it a try.
Click to expand...
Click to collapse
Screen is different. You think driver display of i9000 can work on wave?

thinhx2 said:
Screen is different. You think driver display of i9000 can work on wave?
Click to expand...
Click to collapse
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.

Coldwindofnowhere said:
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Click to expand...
Click to collapse
You can public your kernel for aosp 7 of ss s1?

thinhx2 said:
You can public your kernel for aosp 7 of ss s1?
Click to expand...
Click to collapse
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/commits/staging

No way man, nice work
Android 7 N for s1
Ejgjskfkcisvjj hahah

[ROM][Unofficial][8.1.0][deprecated] Lineage OS 15.1 for Xperia Z1 compact 29.12.18

This Thread is deprecated!
Please use https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-lineageos-15-1-xperia-z1-compact-t3884247/
We'll provide Lineage 15.1 builds there as well. They come in two different flavours:
pure LineageOS
Security hardened microG LineageOS
Functionality is completely the same as provived by the builds from this thread - they are build from the same sources. Only difference: The new builds are signed to guarantee a maximum of security.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by AdrianDC
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: didn't test
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok, but installing updates only works with adb sideload!
- SEPolicies : Enforcing
Download
https://androidfilehost.com/?w=files&flid=269301
latest version: https://www.androidfilehost.com/?fid=11410963190603873784
Click to expand...
Click to collapse
FAQ
What about device encryption?
Device encryption is working. You only have to keep in mind that you need a PC with adb to install systemupdates.
Flashing via recovery isn't working until now, because there isn't a recovery capable of decrypting Oreo /data partitions at the moment. But an easy "adb sideload" should do the job. Or installing from the external SD card.
Click to expand...
Click to collapse
What about reboot to recovery?
Reboot to recovery is only working with magisk installed. Investigating this...
Reboot to recovery is working as it should now (and of course also without magisk).
Click to expand...
Click to collapse
What about GPS?
GPS apps like GPS Status&Toolbox or SatStat don't get location fixes. Nevertheless navigating with Osmand or googleMaps should work. Positionfinding is also slow. Got better
Click to expand...
Click to collapse
I found a bug. What should I do?
We need your feedback for optimization. But your feedback is only useful in connection with logs --> see section Bugreports
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 15.1 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/AICP/kernel_sony_msm8974
Manifest: https://github.com/115ek/manifest
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 15.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/115ek/manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-09-10
Created 2018-09-10
Last Updated 2019-03-18

Changelog
13.12.2018
fixed wrong bluetooth MAC address (00:00:00:00:5a:ad on all devices), now displaying correct device specific one
12.12.2018
synced LineageOS sources (security patch level December 05, 2018)
11.11.2018
fix problem with Lineage SU addon by using 64-bit binder API (thanks @NyQuilXT)
synced LineageOS sources (security patch level November 05, 2018)
14.10.2018
fixed GPS 3D fix
08.10.2018
fixed MHL (thanks @koron393)
added callrecording
synced LineageOS sources (security patch level October 05, 2018)
23.09.2018
fixed reboot to recovery without magisk
minor improvements from AICP devices trees (thanks @SpiritCroc)
synced LineageOS sources
10.09.2018
initial release

Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
Encryption : Ok but needs recovery capable of Oreo decryption for installing updates (AFAIK such a recovery doesn't exist until now for our device...)
Click to expand...
Click to collapse
I'm actually having some trouble finding a up-to-date recovery.

Jeroen1000 said:
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
I'm actually having some trouble finding a up-to-date recovery.
Click to expand...
Click to collapse
You can use this https://androidfilehost.com/?fid=5862345805528046823 or that https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450.
For Lineage 15.x flashing you need TWRP>=3.2.x If the version is older you'll end up in a error 7.
Concerning decryption: Google introduced some new encryption stuff and so the decryption of /data from inside TWRP is broken. Some guys are working on it (@nailyk).
Encrypting the device should work fine, but I don't know what happens if you want to update the encrypted device. (I'm going to test that ).
Basically you need to store the update package outside of encrypted partitions... Maybe adb sideload works - but it's circumstantial.
Edit:
That's only interesting if you plan to encrypt your device. Otherways you can relax.
Edit2:
adb sideload should do the job. But you need a PC for updating. Installing an image directly via recovery isn't possible until now.

With sources for both kernel and system unlike the other port! Thanks, I'll definitely be using this!

Xperia J1 Compact
could this work on an Xperia J1 Compact?
it's basically the same phone with the same specs right?

The rom looks very stable and balance, but I've some problems with root procedure. I tried the lineage addon, the root seems active, but opening apps (es. Ad away) results unrooted, any ideas?
Update: Now Works. Flashed lastest Magisk

Amazing to see this old device on Oreo, just installed and it feels smooth and nice. Just a pity that I have broken the sim card connectors inside so I cant use it as a phone but I will fins use of it at home just for fun. Thank you for your work 115ek :good:

Great to see this rom realy! This rom have stock camera?

munjeni said:
Great to see this rom realy! This rom have stock camera?
Click to expand...
Click to collapse
What do you mean with stock camera?
There was a thing with kernel versions 3.4 and 3.10, wasn't it? We're using 3.4.
Concerning the camera: I'm not that expert, but it looks okay I would say.
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.

115ek said:
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
Click to expand...
Click to collapse
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery

raschad said:
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
Click to expand...
Click to collapse
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome

115ek said:
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
Click to expand...
Click to collapse
I meant does this rom have stock camera blobs? Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?

munjeni said:
Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
Click to expand...
Click to collapse
Good news: an easy import of your init_board_device.h did the trick. Maybe a timing problem?
Anyway: reboot to recovery is now working correctly, even without magisk
Is that okay for you: http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/73688 ?

I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...

munjeni said:
I meant does this rom have stock camera blobs?
Click to expand...
Click to collapse
We're using them https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/rhine-common/proprietary/vendor, so I guess yes.
You're more into topic, aren't you? How to distinguish between AOSP and stock blobs? There were some mysteries around DRM, camera quality and so on. I remember a separate thread you also participated in...
But I'm not really into this topic.

munjeni said:
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
Click to expand...
Click to collapse
No, it's actually in here: https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/include/init_sony/init_board_device.h
But It's different from yours. Yours performs another keycheck.

Seems rom have stock blobs. To distinguish between AOSP and stock blobs... depends on kernel you have using, aosp kernel can't be used with stock blobs since aosp camera kernel module is diferent, but I'm out of development for long, have no free time and to be honest I still didn't forgot treatment & injustice for my status on xda, that made me more inactive here. Recognised members have bad treatment here, seems senior members have much more priority than recognised members, and thats reason why everybody here need to care how many hours per day to waste here. I decided to stop wasting my time on xda since xda leaders do not respect anybody's hard work here. I recommend the same to everyone here.

I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem ?

ULT][MO said:
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem
Click to expand...
Click to collapse
What recovery are you using? I recommend this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
With mine from here https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450 it still won't work. Maybe a timing thing.
But it's okay if we have at least one working TWRP.
And oreo /data decryption is still an issue we have to address.

[ROM][4.4][UNOFFICIAL] LineageOS 16.0 with 4.4 kernel

LineageOS 16.0 for Xiaomi Mi 5 with 4.4 kernel
Remember this is a beta release, althought I've been using it for more than a week and it's working perfectly.
If you experience any bugs, panics or so, please report full logs to me (logcat and dmesg, you can look in /sys/fs/pstore)
Installation:
You can flash it on top of OFFICIAL 3.18 LOS also you can always go back within a dirty flash.
For safety reasons always perform a backup of your important data!
Features:
This is well-known LOS, none of the functionalities have been altered.
Build is running 4.4.189 kernel with many improvements over 3.18, it will keep this device alive for upcoming Android releases.
Kernel is suited with initial bug fixes, however, it's a stock kernel without any advanced tweaks. It's built with CLANG (!).
Working:
Probably everything!
Not working:
Kernel is permissive
Temporary MTP fix (I didn't have enough time to investigate it well):
Developer settings -> Default USB conf -> MTP -> connect cable -> profit
READ ONLY IF YOUR DEVICE IS ENCRYPTED:
There is an incompatibility between 3.18 and 4.4 kernels, you have to flash new TWRP with 4.4 kernel, otherwise your data partition will be DAMAGED!
Nevertheless there could be a need to full wipe your /data (magic Format Data button in TWRP) so perform a FULL BACKUP.
Download:
LineageOS zip
TWRP
Future development:
Device tree will be created from scratch over new Qualcomm tag to get rid of old junk. Full Treble compability will be provided.
More kernel bug fixes
Vendor update
FAQ:
Can I install XXX ? Does it support XXX ?
- It's still LOS, it supports everything what stock LOS does.
Can't you ship kernel package only?
- No, ROM has to be modified to meet 4.4 requriements. You can't flash 4.4 kernel on top of 3.18 ROM.
But why 4.4? Do I need it?
- More fixes, more performance, more support. If you want, search for kernel changelog.
EAS?
- Not now, there are more important things to work on.
If you want to buy me a coffee, please consider donating, I've put much effort to make it working.
DONATE
Join Mi5 group on Telegram
Huge thanks to Zuk kernel team for initial 4.4 support!
Credits:
@DD3Boh
@YaroST12
@kenny3fcb
@Luk1337 - fix for USB
@Jawor245 - random stuff
@RadixCube
XDA:DevDB Information
LineageOS 16.0 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre/msm-4.4
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-01
Last Updated 2019-09-01

Reserved

Reserved

In Antutu 7.2.3 tested fresh, stock LOS + nano gapps and fresh this rom + nano gapps on my 32Gb version. Biggest improvement for my device is memory +22% in Antutu points.
Stock: 144 086 overall
CPU: 50 420
GPU: 53 892
UX: 34 159
MEM: 5 615
4.4 LOS: 148 079 overall
CPU: 50 600
GPU: 54 615
UX: 35 657
MEM: 7 207

@xNombre great job!
I'll be testing your ROM in the future for sure. Looks very promising.
It would be great if you pulled the Floppy Kernel mods to tweak your 4.4 kernel
(Just my wish)
However, congratulations man.

I really appreciate your effort I would love to test your ROM But I only want to know 2 things before if someone can help.
1. Can I use it as daily driver?
2. Android Auto is working?
3. Will I need to do clean flash for future updates? Atleast for couple weeks.
Thanks

I'm using it for two weeks and no problems here.
If Android Auto is working on official LOS it will for for mine, too.
Nope, not for now.
#edit
Here is the new kernel you can flash on top of my LOS. (DON'T FLASH IT ON ANYTHING ELSE)
https://androidfilehost.com/?fid=1899786940962575411
Changelog:
add exFAT and NTFS
fix problems with wakelocks
use LZ4 for ZRAM
debloat a bit
skip sync for better battery

@xNombre What is the reason behind choosing 4.4 instead of a newer LTS version like 4.9 or 4.14? Or was the decision out of your hands?

Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.

xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Whoa, calm down, mate. I just wanted to know the rationale. Knowing that msm8996 supports 4.4 is good enough for me. :good:
Sorry to hear about the two damaged devices, though. That must have been extremely frustrating.

xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Lots of love for 4.4 kernel.

Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?

Thank you for your work. This is quite big actually.

Thx

Myxomatom said:
Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?
Click to expand...
Click to collapse
There it no correlation between kernel and RIL. No changes here. Maaybe sth nice will happen with new vendor blobs but you have to wait for it.

great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!

bido1 said:
great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!
Click to expand...
Click to collapse
yeah ... been using it for the last 3 days ... the battery performance is better than the official one without any tweak

can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?

netrixken said:
can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?
Click to expand...
Click to collapse
Are you using TWRP provided in first post?