{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
LineageOS is a free, community-built, aftermarket firmware distribution of Android 6, 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.
Code:
[B]BUGS:[/B]
-RIL [IMEI don't dissapear when you insert SIM CARD, but phone don't get SIGNAL]
[B]What is Working:[/B]
-Audio (v3)
-ADB
-Bluetooth (v3)
-Battery (v3)
-Brightness
-GPS (v3)
-Location (Turns ON)
-Radio FM (v4)
-Sensors (v3)
-Vibration
-WiFi (v2)
-EngineerMode [Add it (v5)]
-YGPS [Add it (v5)]
-Torch (v7)
-Camera (7)
-Video Recording (v8)
-NFC (v8)
-BootAnimation (v9)
-Storage Errors (v9)
-Update kernel to 43.0.A.7.106 (v9)
-OMX (v10)
ROM HAVE BEEN TEST IT ON G3311 VARIANT
V12 Changelog:
Import SonyDoze.
Import libinit,
Update assert.
Switch to libshims.
Make some progress with RIL.
Use all blobs from L1 43.0.A.7.106 not more blobs from other devices.
Set correct permission to /dev/ccci* and /data/nvram/md
Make partition_permission being executed
Import properties from /oem partition.
Set ro.build.imeisv as 15
Update spn-conf.xml
Remove some duplicated props
Build librilutils
Build Stk
Use device/sample/etc/apns-full-conf.xml
Define dual sim slot counts at overlay
Add frameworks/opt/telephony missing patch
Switch to my custom kernel aka AvengedKervel
Improve stability
Installation:
Boot this TWRP https://forum.xda-developers.com/xp...elease-twrp-sony-l1-g3311-single-sim-t3818260
Format Data
Wipe Cache, Dalvik Cache, System.
Flash ROM
Flash GAPPS (If you used, i recommend Pico GAPPS)
Flash Magisk (OPTIONAL)
Reboot to System, without installing TWRP APP
Download LINKS:
ROM v1
ROM v2
ROM v3
ROM v4
ROM v5
ROM v6
ROM v7
ROM v8
ROM v9
ROM v10
ROM v11
ROM v12
GAPPS
Magisk
Thanks to:
KJONES
BILUX
R0RT1Z2
PAUL (SODP)
Rote66
Myst33d
Maanush
Bigrammy
TEAM M.A.D
Sources:
Device Tree
Kernel Source
Vendor blobs
te mamaste
just made a profile to say that it's running just fine on my G3311 (of course, with all the aforementioned things missing)
RIL is still broken, I have a SIM card in
GPS doesn't seem to work
you said Xperia bootscreen but what mine booted to isn't what you said, not that I mind of course
Great work! Glad to see you got it booting! You are making great progress! Keep it up!
Makurawa said:
just made a profile to say that it's running just fine on my G3311 (of course, with all the aforementioned things missing)
RIL is still broken, I have a SIM card in
GPS doesn't seem to work
you said Xperia bootscreen but what mine booted to isn't what you said, not that I mind of course
Click to expand...
Click to collapse
Strange.
When i boot phone i have this BootAnimation.
AlaskaLinuxUser said:
Great work! Glad to see you got it booting! You are making great progress! Keep it up!
Click to expand...
Click to collapse
Thanks!
jmpf_bmx said:
Strange.
When i boot phone i have this BootAnimation.
Click to expand...
Click to collapse
doesn't particularly matter since it works just fine, just something I noticed
jmpf_bmx said:
Strange.
When i boot phone i have this BootAnimation.
Thanks!
Click to expand...
Click to collapse
Probably the bootanimation is being loaded from other partition that is not /system, i.e: /cust in your case
Great work tho, mtk ones are so difficult
Regards.
Rortiz2 said:
Probably the bootanimation is being loaded from other partition that is not /system, i.e: /cust in your case
Great work tho, mtk ones are so difficult
Regards.
Click to expand...
Click to collapse
Thanks.
jmpf_bmx said:
Strange.
When i boot phone i have this BootAnimation.
Thanks!
Click to expand...
Click to collapse
Some bootanimoation read from oem partition
AlaskaLinuxUser said:
Great work! Glad to see you got it booting! You are making great progress! Keep it up!
Click to expand...
Click to collapse
Hi,
I am unsure what Sony do with the RIL on their MediaTek device range or what piece of the puzzle everyone is missing
The Sony M5, XA, XA1 and this L1 (All MT67xx) all have 99% working custom ROM's eg Lineage but everyone has this same issue (broken ril)
Other MediaTek devices with the Same CPU's and Release versions do not seem to suffer this issue so I can only assume it's something that Sony has done so the usual blame MediaTek wont wash.
Are we missing some key commit or revert, something with the /ta or mobicore
I know these MTK devices are not official Sony open devices but it would nice if the boffins over at Sony would help out just a little either officially or unofficially
I got zero reply's to my question/post HERE about this exact same issue on the XA you will see there the XA got as far as the Ril looping over and over.
It's frustrating to get so close with out crossing the finishing line :crying:
I am still waiting to get to my Sony L1 back so I can try help out a little here but I have a feeling we will hit the same brick wall as we have done on the Sony XA https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212 :crying:
@andrw.gldmn did a awesome job on the XA :good:
Peace.
bigrammy said:
Hi,
I am unsure what Sony do with the RIL on their MediaTek device range or what piece of the puzzle everyone is missing
The Sony M5, XA, XA1 and this L1 (All MT67xx) all have 99% working custom ROM's eg Lineage but everyone has this same issue (broken ril)
Other MediaTek devices with the Same CPU's and Release versions do not seem to suffer this issue so I can only assume it's something that Sony has done so the usual blame MediaTek wont wash.
Are we missing some key commit or revert, something with the /ta or mobicore
I know these MTK devices are not official Sony open devices but it would nice if the boffins over at Sony would help out just a little either officially or unofficially
I got zero reply's to my question/post HERE about this exact same issue on the XA you will see there the XA got as far as the Ril looping over and over.
It's frustrating to get so close with out crossing the finishing line :crying:
I am still waiting to get to my Sony L1 back so I can try help out a little here but I have a feeling we will hit the same brick wall as we have done on the Sony XA https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212 :crying:
@andrw.gldmn did a awesome job on the XA :good:
Peace.
Click to expand...
Click to collapse
Hi,I don't know M5/XA Also Nougat too,And In ALPS-N,it have ril-proxy.I know most MTK device (Vendor in Nougat)have ril problem,and some device revert to mm vendor and some device replace them.I tried replace A7010a48 ril files,and Modify kernel ccci part from A7010a48,baseband can be recognized,but insert card will lose it.
Also,i think it about TA partition,but all TA service in Los14.1 cannot run normally,so i removed them.
And i know danielhk modify the ril sources from aosp and add ril-proxy in oreo.
rote66 said:
Hi,I don't know M5/XA Also Nougat too,And In ALPS-N,it have ril-proxy.I know most MTK device (Vendor in Nougat)have ril problem,and some device revert to mm vendor and some device replace them.I tried replace A7010a48 ril files,and Modify kernel ccci part from A7010a48,baseband can be recognized,but insert card will lose it.
Also,i think it about TA partition,but all TA service in Los14.1 cannot run normally,so i removed them.
And i know danielhk modify the ril sources from aosp and add ril-proxy in oreo.
Click to expand...
Click to collapse
Hi rote66,
@rrvuhpg built CM13 (MM) for the XA using the MM release firmware blobs and pretty much the same result none working RiL
I have noticed on Both my XA and XA1 on the stock ROM's that the Signal is almost the last thing to get started up
Example: Phone boots to home screen, WiFi is up and NFC but no SIM then at the very last moment the SIM gets detected and the signal bars appear.
I am not sure if it's the same thing on the stock L1 or not?
Ref rilproxy:
Using rilproxy on the XA gets the sim detected but it crashes repeatably I made a video of it here Crashing RiL using rilproxy
I will get my L1 back soon and will be able to compare things better.
bigrammy said:
Hi rote66,
@rrvuhpg built CM13 (MM) for the XA using the MM release firmware blobs and pretty much the same result none working RiL
I have noticed on Both my XA and XA1 on the stock ROM's that the Signal is almost the last thing to get started up
Example: Phone boots to home screen, WiFi is up and NFC but no SIM then at the very last moment the SIM gets detected and the signal bars appear.
I am not sure if it's the same thing on the stock L1 or not?
Ref rilproxy:
Using rilproxy on the XA gets the sim detected but it crashes repeatably I made a video of it here Crashing RiL using rilproxy
I will get my L1 back soon and will be able to compare things better.
Click to expand...
Click to collapse
Yes,ril Proxy is just one problem.I don't know sony modified what.Exactly as my says.I use Lenovo ril files and ccci part,Same as i use official ril files.Just recognize the baseband version and insert sim will lose it.And i found a strange thing.In radio log it return -1 from ttyC0 whether i use official or Lenovo ril files in Los14.1.But in official rom,it's normally.
rote66 said:
Yes,ril Proxy is just one problem.I don't know sony modified what.Exactly as my says.I use Lenovo ril files and ccci part,Same as i use official ril files.Just recognize the baseband version and insert sim will lose it.And i found a strange thing.In radio log it return -1 from ttyC0 whether i use official or Lenovo ril files in Los14.1.But in official rom,it's normally.
Click to expand...
Click to collapse
I have just received my L1 so I do some investigation when I have done a backup and pulled stock prop's etc, etc.
The -1 from ttyC0 seems to be familiar
I am sure I saw that response in the ril source code some place hopefully I can find it again and see what it means
I will reply more in a day or two. :highfive:
bigrammy said:
I have just received my L1 so I do some investigation when I have done a backup and pulled stock prop's etc, etc.
The -1 from ttyC0 seems to be familiar
I am sure I saw that response in the ril source code some place hopefully I can find it again and see what it means
I will reply more in a day or two. :highfive:
Click to expand...
Click to collapse
Fine. return -1 says it not normally.And in logcat i can't find another stranges,just some Fake error.
Info and Findings
Hi All dev's,
I THINK I may of just stumbled upon the RiL issues with our Sony (MediaTek) devices. :fingers-crossed:
All the Sony MTK devices share a common problem which is the RiL is broken on All these custom ROMS.
While the dev's have done a totally awesome job with these devices the working Ril has alluded everyone.
The one thing all our devices have in common is org.simalliance.openmobileapi and I think this maybe the key.
Having installed this L1 Lineage I was amazed to see pretty much the exact same issues as was on the XA Lineage Rom made by @andrw.gldmn
So I did some digging and came up with the below .pdf which explains what this means for our Sony mtk's with the org.simalliance.openmobileapi installed.
Section 6 In the PDF below explains what is needed for CM/Lineage so we can communicate with SIM via the api using the Stock Ril parts hopefully.
as a side note I noticed that in setting/Lockscreen &/or Security under "Credentcial storage" Storage Type Stock Rom = "Hardware Backed" but under Lineage it says "Software only"
OpenMobileSim.pdf HERE
Sadly Compiling is beyond my capabilities so Hopefully the OP could apply the patches.
As for this ROM I fixed the Multiple "corrupted storage" issue and fixed the boot logo which now boots from system without disabling the /oem partition.
bigrammy said:
Hi All dev's,
I THINK I may of just stumbled upon the RiL issues with our Sony (MediaTek) devices. :fingers-crossed:
All the Sony MTK devices share a common problem which is the RiL is broken on All these custom ROMS.
While the dev's have done a totally awesome job with these devices the working Ril has alluded everyone.
The one thing all our devices have in common is org.simalliance.openmobileapi and I think this maybe the key.
Having installed this L1 Lineage I was amazed to see pretty much the exact same issues as was on the XA Lineage Rom made by @andrw.gldmn
So I did some digging and came up with the below .pdf which explains what this means for our Sony mtk's with the org.simalliance.openmobileapi installed.
Section 6 In the PDF below explains what is needed for CM/Lineage so we can communicate with SIM via the api using the Stock Ril parts hopefully.
as a side note I noticed that in setting/Lockscreen &/or Security under "Credentcial storage" Storage Type Stock Rom = "Hardware Backed" but under Lineage it says "Software only"
OpenMobileSim.pdf HERE
Sadly Compiling is beyond my capabilities so Hopefully the OP could apply the patches.
As for this ROM I fixed the Multiple "corrupted storage" issue and fixed the boot logo which now boots from system without disabling the /oem partition.
Click to expand...
Click to collapse
Los14.1 's corrupted storage and bootanimation had fixed in my release two weeks ago ,and uploaded to PineDevelopment.So los14.1 just remain OMX and RIL.And if any sony devices have this api,why qcom sony device normally.Just curiously.
rote66 said:
Los14.1 's corrupted storage and bootanimation had fixed in my release two weeks ago ,and uploaded to PineDevelopment.So los14.1 just remain OMX and RIL.And if any sony devices have this api,why qcom sony device normally.Just curiously.
Click to expand...
Click to collapse
I did not see any other builds in the OP I used the v8 build date 2020/03/14 and this build had the above bugs
I see now you made commits to fix the bootanimation in the source. It maybe a good idea to add Releases page on the PineDevelopment git?
Just to be clear I am not very good with github and would hate to wreck anything on the PineDevelopment. :laugh:
The fixes I used consisted of replacing the bootanimation in /bin and replacing the bootanimation.zip in /system/media.
The corrupted storage issue was fixed by using the stock rom's vold as I did on the tuba (XA) some time back which had the exact same issue.
As for Open Sony qcom devices Sony release the blobs for these devices which i assume differ from the ones in the stock ROM's.
I could be totally wrong about org.simalliance.openmobileapi been the cause of the Ril issue but it does seem to be a bit of a coincidence.
I do not know which other MTK devices use org.simalliance.openmobileapi to try compare.
bigrammy said:
I did not see any other builds in the OP I used the v8 build date 2020/03/14 and this build had the above bugs
I see now you made commits to fix the bootanimation in the source. It maybe a good idea to add Releases page on the PineDevelopment git?
Just to be clear I am not very good with github and would hate to wreck anything on the PineDevelopment. :laugh:
The fixes I used consisted of replacing the bootanimation in /bin and replacing the bootanimation.zip in /system/media.
The corrupted storage issue was fixed by using the stock rom's vold as I did on the tuba (XA) some time back which had the exact same issue.
As for Open Sony qcom devices Sony release the blobs for these devices which i assume differ from the ones in the stock ROM's.
I could be totally wrong about org.simalliance.openmobileapi been the cause of the Ril issue but it does seem to be a bit of a coincidence.
I do not know which other MTK devices use org.simalliance.openmobileapi to try compare.
Click to expand...
Click to collapse
Release in my github's device,i didn't merge it to pinedevelopment beacuse both have some differents.
Maybe can try To merge the openapi To have a try
I will update the post tomorrow.
That i have a fix for OMX.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KITKAT), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Unofficial build of CyanogenMod 11 (Android 4.4.4) for the Sony Xperia M2 (eagle)
What's working:
Display
Audio playback
Audio recording
Video playback
Screenshot
External SDcard
Internal SDcard
WiFi
Bluetooth
Notification LED
MTP
USB Host / OTG
Torch
Brightness control
GPS
RIL
Not working:
Camera (http://pastebin.com/Te5CTy9a)
Sensors (light-sensor, accelerometer)
It's entirely possible that features not used by me are broken, but overall the device should be usable. You have been warned.
Download:
ALPHA 2 : https://www.mediafire.com/?wea2vj8265qx33s
ALPHA 1 : https://www.mediafire.com/?f5389z009525alx
GAPPS
Install instructions:
Boot into Recovery
Wipe data and cache
Flash the CM11 zip
Reboot
Reboot into Recovery
Install gapps
Reboot
Upgrading from earlier version of CyanogenMod 11:
Boot into Recovery
Flash CM11 zip
Reboot
Source:
https://github.com/M2Dev
https://github.com/CyanogenMod
Thanks to:
adfad666
XDA:DevDB Information
CyanogenMod 11 for Xperia M2, ROM for the Sony Xperia M2
Contributors
galaxyfreak
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-10-15
Last Updated 2014-10-17
Good work there I assumed this is for the single sim LTE model, but should this work for the single sim WCDMA ?
Sent from my D2305
@galaxyfreak
I have updated camera, gps and arch config. Probably we should add some more sony defs but please test how it is now. Logcat should look differently now or eventaually saying it's missing other parameters.
volunteering my assistance for this project, I can't install CM11 on my phone as it is my daily driver, but if you need someone to help read through logs etc, I would be happy to help
I would love to install CM11 to help developers solve some problems, but my model is D2306, I have root but no one made CWM for this model on KK. How can I proceed? D2306 is Single SIM, LTE, South America variant.
lozohcum said:
@galaxyfreak
I have updated camera, gps and arch config. Probably we should add some more sony defs but please test how it is now. Logcat should look differently now or eventaually saying it's missing other parameters.
Click to expand...
Click to collapse
did you test your updates? As I am building it now with some mods of my own.
Galaxyfreak / lozohcum added my to the M2Dev github (thanx ). If you guys like, I have setup M2Dev on my review site. I think it is better working for all of us to commit to there for commits that require testing. Only thing to do is to add my gerrit user to M2Dev so we can actually push to github from the review
Also, is the issue list in the OP complete? NFC? BT/Wifi tethering? To name some?
Looking forward to do some nice things here
initial code review
erikcas said:
did you test your updates? As I am building it now with some mods of my own.
Galaxyfreak / lozohcum added my to the M2Dev github (thanx ). If you guys like, I have setup M2Dev on my review site. I think it is better working for all of us to commit to there for commits that require testing. Only thing to do is to add my gerrit user to M2Dev so we can actually push to github from the review
Also, is the issue list in the OP complete? NFC? BT/Wifi tethering? To name some?
Looking forward to do some nice things here
Click to expand...
Click to collapse
As said, I have no another NFC device to test, also, I did not test tethering.
Added NFC to not working as you said it's not working last night.
Working on perfectly but please fix screen brightness settings thanks
ishakcez said:
Working on perfectly but please fix screen brightness settings fix thanks
Click to expand...
Click to collapse
Fixed just an hour ago. Will be featured in next build.
"Real-time" bug list: https://github.com/M2Dev/M2_logs/blob/master/README.md
Thanks a lot
Thank you bro, but i'll wait for Mobile Network and Camera, if you say me how i can do a total backup of my ROM i can test to say you if it work
(Sorry i'm french)
Tested it for 30 min now and it seem that themes are recognized very slowly, when I install one it takes 10-20 seconds to be availble to choose in theme chooser tested it with play store themes and themes i have to install via apk.
cant say anything about nfc because i dont have anything nfc related here.
everything you stated is working is working for me too so no problem there :fingers-crossed:
I have one question why is the android version 4.4.2, I also have the moto g and 4.4.4 seemed not to make any problems maby somethings can be fixed by upgrading the cm version.
keep up the good work looking forward to give my brother cm11 for his birthday :victory:
Very good !
I'll test it and i love !
When problems will be resolve i'll keep this ROM !
And i have a problem, my recovery don't work, why ?
Bryandu13 said:
I'll test it and i love !
When problems will be resolve i'll keep this ROM !
And i have a problem, my recovery don't work, why ?
Click to expand...
Click to collapse
The Kernel has to be replaced and I think that deletes the recovery, I reflashed it but you cant boot cyanogenmod after that
Sent from my D2303 using XDA Free mobile app
How can I have a custom recovery ?
How get CWM with cyanogenmod ? I need flash GAPPS !
Bryandu13 said:
How get CWM with cyanogenmod ? I need flash GAPPS !
Click to expand...
Click to collapse
You should have flashed that with cyanogenmod without reboot between
Sent from my D2303 using XDA Free mobile app
Thanks !
tomemon said:
You should have flashed that with cyanogenmod without reboot between
Sent from my D2303 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you bro, did you test it ?
Does CWM work after that ?
Bryandu13 said:
Thank you bro, did you test it ?
Does CWM work after that ?
Click to expand...
Click to collapse
I have tested it and it works but cwm doesnt
now some devtalk (I see a lot of Q&A talk in a dev section)
@galaxyfreak / @lozohcum see my reimplement of primadriver here
I have re-imported it from caf. Now working, and without unbalanced irq's.
For ril (or actually, the problem might reside in qmuxd I think), first step to be taken is replace all firmware blobs that are taken from T2 ultra by blobs pulled from M2. I have already done so here
Now the device is able to power up the modem.
Ril is not working yet. For now, I am using the prebuilt ril blobs. Will now recompile without them and test that, also to check the qmuxd theory I have.
erikcas said:
now some devtalk (I see a lot of Q&A talk in a dev section)
@galaxyfreak / @lozohcum see my reimplement of primadriver here
I have re-imported it from caf. Now working, and without unbalanced irq's.
For ril (or actually, the problem might reside in qmuxd I think), first step to be taken is replace all firmware blobs that are taken from T2 ultra by blobs pulled from M2. I have already done so here
Now the device is able to power up the modem.
Ril is not working yet. For now, I am using the prebuilt ril blobs. Will now recompile without them and test that, also to check the qmuxd theory I have.
Click to expand...
Click to collapse
Nice work! Replaced adfad666's WiFi commits with yours in M2Dev.
On firmware, yeah, I left T2U firmware because on stock firmwares are stored on /persist partition and so I was feeling lucky
AOSPA 6.0.1 for the Xperia Z3 Compact!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Instructions
If installing fresh and/or coming from another ROM (including previous PA versions)
Reboot into Recovery (Please use the latest TWRP) and MAKE A BACKUP!
Wipe System, Data, Cache, and Dalvik Cache
Flash Latest OFFICIAL STOCK ROM - This will ensure a clean system and all bootloader etc updated to latest.
Wipe System, Data, Cache, and Dalvik Cache
Flash the ROM
Flash GApps
Flash SuperSU (if you want to have root, that is)
Wipe Caches and Reboot
Profit!
Download Links
ROM: http://get.aospa.co/official/aries
AOSPA Links
Google+: https://plus.google.com/communities/112514149478109338346
Gerrit: http://gerrit.aospa.co/
GitHub: https://github.com/AOSPA
#StayParanoid
XDA:DevDB Information
Paranoid Android 6.0.x, ROM for the Sony Xperia Z3 Compact
Contributors
tomgus1, sonyxperiadev, PA Team
Source Code: https://github.com/AOSPA/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSPA
Version Information
Status: Stable
Created 2016-08-08
Last Updated 2016-08-11
Reserved
Except for the camera bugs, seems to be stable. I've read somewhere about Sony releasing new sources for camera. Are these new sources used in this ROM?
juliopw said:
Except for the camera bugs, seems to be stable. I've read somewhere about Sony releasing new sources for camera. Are these new sources used in this ROM?
Click to expand...
Click to collapse
You are correct in that Sony will be releasing new binaries for camera and this is indeed what we are using for PA on Sony. However this work will take time, but we will in the end have Nexus like support for Sony devices.
tomgus1 said:
You are correct in that Sony will be releasing new binaries for camera and this is indeed what we are using for PA on Sony. However this work will take time, but we will in the end have Nexus like support for Sony devices.
Click to expand...
Click to collapse
That's what we are waiting for, Nexus like support :highfive:
However due to that nasty reversed fish-eye people just gave up, since Sony didn't release proper binaries and blobs. Lets see if that gets fixed with those releases.
Yeah. Making the camera work properly seems to be the biggest difficulty in developing for the Z3C. I will test every build and give feedback. Thanks!
@tomgus1 thanks for the rom !!
@juliopw source about new camera blobs ? Thanks !
@snaky90 Can't remember where I saw it. Only found this old post. Sorry. I will look into it again.
I have a lot of problems with this rom! Sometimes I have lag and my phone has randoms reboots. The camera worked at the first time with a very bad quality. Now I can not acces to the camera because I got a error code.
Please fix this problems
@TomGus 1 hi I can't find your sources on the official PA repository. Are you using the sony open devices repos for device tree etc?
I have a lot of problems with this rom! Sometimes I have lag and my phone has randoms reboots. The camera worked at the first time with a very bad quality. Now I can not acces to the camera because I got a error code.
Please fix this problems
Click to expand...
Click to collapse
mcgi5sr2 said:
@TomGus 1 hi I can't find your sources on the official PA repository. Are you using the sony open devices repos for device tree etc?
Click to expand...
Click to collapse
Hi, for the reboots etc this is a kernel issue. Currently we are using the 1.2.2 branch from sonyxperiadev which has an issue with vidc/iommu. This is fixed in the 1.3.3 branch but currently Camera is not yet supported. Once support is added we will move over. I can confirm that it is fixed as I am currently running from that branch at the sacrifice of no camera.
For your current camera issue please try a reboot or going into recovery and wiping dalvik/cache and trying again. Had this happen once and a reboot fixed it.
We are using Sony Open Devices repositories for all Sony Devices as seen in our dependency files.
tomgus1 said:
Hi, for the reboots etc this is a kernel issue. Currently we are using the 1.2.2 branch from sonyxperiadev which has an issue with vidc/iommu. This is fixed in the 1.3.3 branch but currently Camera is not yet supported. Once support is added we will move over. I can confirm that it is fixed as I am currently running from that branch at the sacrifice of no camera.
For your current camera issue please try a reboot or going into recovery and wiping dalvik/cache and trying again. Had this happen once and a reboot fixed it.
We are using Sony Open Devices repositories for all Sony Devices as seen in our dependency files.
Click to expand...
Click to collapse
Thanks for the reply, that is an almighty dependency list
mcgi5sr2 said:
Thanks for the reply, that is an almighty dependency list
Click to expand...
Click to collapse
More than I'd like but Sony has some cross-overs with Nexus which causes incompatibility.
As reported on G+ here a short sum-up after a week of usage PA on z3c.
Installation broken
Installation expects the getprop("ro.product.device") to be "aries", but mine was z3c, therefore failing. Had to edit the META-INF/com/google/android/updater-script to get it working (exchange "aries" with "z3c").
Tim: Fixed for next release.
Voice Calling volume not changable (very loud)
https://plus.google.com/u/0/+GeorgGrabler/posts/FY9xZZuHMde
Tim: No fix yet.
Voice calling crashes most of the time (beeping or no sound at all), rebooting / locking up the phone (huge issue, makes the ROM unusable for me now)
https://plus.google.com/u/0/+GeorgGrabler/posts/GF2Eac9xtcn
Tim: Fixed next release.
NFC broken
https://plus.google.com/u/0/+GeorgGrabler/posts/iejmnYxSDkh
Tim: Can't reproduce.
=> Got a log of me because he can't reproduce it. Maybe that will help (does not happen if you have a USB attached).
Log at: http://pastebin.com/brZiHsky
Fast Charge not working
https://plus.google.com/+GeorgGrabler/posts/7kKjXJDKQB7
Tim: Will never work, not part of Sony AOSP.
=> Sad, but ok .
Camera issues
Well known, we'll have to see how the open drivers get along over time. They got better in the past, but still there are issues.
I sometimes even get "could not connect to camera" after making a picture.
Can't use the rom for production until the calling issue is solved.
tomgus1 said:
I have a lot of problems with this rom! Sometimes I have lag and my phone has randoms reboots. The camera worked at the first time with a very bad quality. Now I can not acces to the camera because I got a error code.
Please fix this problems
Hi, for the reboots etc this is a kernel issue. Currently we are using the 1.2.2 branch from sonyxperiadev which has an issue with vidc/iommu. This is fixed in the 1.3.3 branch but currently Camera is not yet supported. Once support is added we will move over. I can confirm that it is fixed as I am currently running from that branch at the sacrifice of no camera.
For your current camera issue please try a reboot or going into recovery and wiping dalvik/cache and trying again. Had this happen once and a reboot fixed it.
We are using Sony Open Devices repositories for all Sony Devices as seen in our dependency files.
Click to expand...
Click to collapse
bad news: My recovery was deleted by aospa
recovery isn't touched by aospa. You can't use the standard adb commands to get to recovery though, you have to use the "hardware method".
If your recovery is really gone, just re-flash it, that's not a big issue.
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Just wanted to add: AOSPA team and Tim - great work there. It looks like we could get a really usable rom some time soon (though, the volume highness will still be an annoyance if it can't be fixed ).
---------- Post added at 01:19 AM ---------- Previous post was at 12:42 AM ----------
Last but not least, thanks PA team for all the work and effort. I may not be able to use the ROM yet, even though, I'd love to. You have been and are doing great work, and I hope you'll manage to bring us a good AOSP(A) image some day (rather sooner than later if you ask me ).
Don't take my reports and disappointment as a grain of salt but constructive feedback.
STiAT said:
As reported on G+ here a short sum-up after a week of usage PA on z3c.
Voice Calling volume not changable (very loud)
https://plus.google.com/u/0/+GeorgGr...ts/FY9xZZuHMde
Tim: No fix yet.
Can't use the rom for production until the calling issue is solved.
Click to expand...
Click to collapse
@tomgus1 : Calling volume sound had already been a problem in CM12.1 sometime in 2015. Was solved then. Maybe you can find some useful infos over CM JIRA:
https://jira.cyanogenmod.org/browse/NIGHTLIES-930?jql=status = Closed AND text ~ "z3"
regards, phil
Boils down to this two commits.
https://github.com/CyanogenMod/andr...mmit/fe714b9501b58a63daef424d90cae62dc9743517
https://github.com/CyanogenMod/andr...mmit/899b01eea912bae4d31ae9d0181018de41990f61
the new version 6.0.3 is already working with the camera?
I found a little time on the site and the AOSP rom has a new version 6.0.3, someone already tested the camera is working?
http://get.aospa.co/official/aries
Camera is working, but still the same bad quality. We have to wait for the opensource drivers to get better. Sony is working on this, but it's still a long road ahead as it seems.
Lock-Ups have been fixed, the voice issue (speakers / loud uncontrollable voice level during calls) isn't (yet).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Moto Mods are not supported
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Video Playback
LED Notifications
NFC
Not Working/Bugs
-
Installation
Make sure you have a nougat bootloader and modem else TWRP denies the installation by throwing a message about the wrong bootloader. Further details and a guide to upgrade what you need without losing data here.
Requires Unlocked Bootloader & a custom recovery
Place ROM & Gapps in your virtual SD
Reboot in Bootloader Mode
Go to "Recovery" (Vol +/Vol -) and confirm (power)
Wipe Data/Factory Reset
Wipe Dalvik cache
Install the ROM zip
Install su for root (get it here, you have to enable it from developer settings) [optional]
DO NOT REBOOT
Install the Gapps zip
Reboot
Downloads
download.lineageos.org/addison
AndroidFileHost
Sources
Device Tree
Kernel
XDA:DevDB Information
LineageOS 14.1, ROM for the Moto Z Play
Contributors
Alberto97
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Created 2016-11-07
Last Updated 2017-10-08
Device Specific Changelog
02/04/2017
Switched back to Snap Camera
Now Moto Camera camcorder is fully working
Fixed call recording
25/03/2017
Switched back to QCamera2 HAL
3.18.48 kernel
Fixed some background, probably irrelevant, kernel crashes
16/03/2017
24 bit playback through headphones fixed
Switched to XML audio policy
Added back "comfort" (astronomy/night mode) color profile
09/03/2017
March Security patches
Reverted a patch that caused frequent high latency of wifi packets
25/02/2017
February Security patches
Enforcing SELinux
Switched to the fully working Snap Camera
Improved stability
Updated Adreno blobs
aptX support? (not tested)
18/02/2017
Camera is now working, more or less
SELinux is almost ready
Now using Nougat blobs (thanks a lot @felipevsw for his efforts)
18/01/2017
January security patches
QCOM Color Modes Support
Vulkan support
Fixed GLONASS (Satellites fixing time seems slower though)
Wlan drivers update
CyanogenMod Releases:
24/12/2016
Many CVE(s) have been fixed (kernel side)
Wlan drivers update (should improve the stability with Android 7.1.1 releases)
10/12/2016
Android 7.1.1 and December Security Patches
Switched back to 3.18.24 kernel
Blobs updated to the latest Marshmallow release (MPNS24.104-44-7)
03/12/2016
Fixed Fingerprint sensor
Kernel upgraded to v3.18.45 (just a test, I'll probably switch back to the previous one)
19/11/2016
Introduced the ability of using fingerprint sensor as Home Button (available under Settings -> Gestures)
LiveDisplay has been implemented (kernel side)
Added qcom IPA (Internet Protocol Accelerator)
All the kernel side Android security patches have been merged
Removed some camera hacks
Ramdisk cleanup
07/11/2016
Initial release
I think I love you. Thanks for the hard work.
For those are wondering, yes I've built the CM13 too but I have a weird and annoying bug there. For some reason Google's Location Provider causes random memory corruptions which lead to many random reboots when you're connected to a wifi network. Without a WiFi connection presence the device bootloops endlessly (we actually had a similar issue with moto msm8916 family but the problem was explicit there, here it's not). Nougat isn't affected by this bug, so that's why I'm directly publishing CM14.1 and skipping CM13
I think i love you too, very very thanks for the hard work :laugh:
Does this work for the dual sim model? ("retla release channel")?
Skipped right over 6.0 and 7.0 and right to 7.1, Heh. My moto x pure isnt even on 7.1 yet. Awesome work!
What about encryption, does CM 14.1 Will encrypt when I set up the fingerprint scanner? Because I don't want encryption in my phone, I want to get the most of the SD625. Thanks.
Uclydde said:
Does this work for the dual sim model? ("retla release channel")?
Click to expand...
Click to collapse
This is actually tested only on my dual sim device and it works fine
MuyKurioso said:
What about encryption, does CM 14.1 Will encrypt when I set up the fingerprint scanner? Because I don't want encryption in my phone, I want to get the most of the SD625. Thanks.
Click to expand...
Click to collapse
No, I've disabled forced encryption on cm but you have to erase userdata through fastboot to get rid of encryption. Wipe data from TWRP isn't enough.
Alberto97 said:
This is actually tested only on my dual sim device and it works fine
No, I've disabled forced encryption on cm but you have to erase userdata through fastboot to get rid of encryption. Wipe data from TWRP isn't enough.
Click to expand...
Click to collapse
Thanks for the reply. Do we need source code from Nougat to get camera working?
Thanks! I'll test it as soon as I get home.
MuyKurioso said:
Thanks for the reply. Do we need source code from Nougat to get camera working?
Click to expand...
Click to collapse
Camera stack is closed source on most of devices, motos included. On Nougat Google has done a lot of changes to the camera sources, so our prebuilt files find a new "unknown evnironment" while they expect the Marshmallow one.
There currently are some workarounds for this but nothing changes on this device; probably because of some changes made in our stack for the hasselblad camera module.
Do you think it will be possible to get moto mods working on custom roms? Is it something like the camera where we just need the blobs for 7.0 and integrate them into the kernel and all that or would it be a complicated mess to get them working at all?
Perhaps I'll be flashing this, how stable is it beside the camera and torch bugs? Are you using it as your daily driver?
Also, what gapps should I download? 64bit?
Hey bro, and Moto G 2015? ?
@Alberto97
MuyKurioso said:
Perhaps I'll be flashing this, how stable is it beside the camera and torch bugs? Are you using it as your daily driver?
Also, what gapps should I download? 64bit?
Click to expand...
Click to collapse
The Snapdragon 625 that's in our devices is 32-bit, so you wouldn't use the 64-bit GApps.
Uclydde said:
The Snapdragon 625 that's in our devices is 32-bit, so you wouldn't use the 64-bit GApps.
Click to expand...
Click to collapse
Im pretty sure our snapdragon 625 is not 32-bit, it is definitely built on aarch64. I think they just built the stock rom for armv7 or aarch32 which our processor is still compatible with. Probably because there isnt much of a reason to compile for aarch64. Taking a guess, I would think that this rom is 32-bit as well because the kernel source for our device would be based off of stock, I can easily be wrong about this though.
This is for Build Number MPN24.104-44 ? Indian Dual Sim.
Thank u so much man for working on this rom. Was regularly checking everyday for any Nougat rom and saw this. Very Happy. But I use my camera a lot so can't flash it right now. Hope the bugs get resolved pretty soon. Thanks for the rom again
mijing said:
This is for Build Number MPN24.104-44 ? Indian Dual Sim.
Click to expand...
Click to collapse
It doesn't matter.
---------- Post added at 01:39 AM ---------- Previous post was at 12:55 AM ----------
I tested it and everything works (except for the camera for reasons already stated). In order for me to get a similar experience to Moto Display I found this app and it works almost as good on CM.
https://play.google.com/store/apps/details?id=com.compass.ambiturner
The only bad thing is that you have to purchase Pro to get Wave to Wake, but it is worth it in my opinion.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device..
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github Repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
Downloads
ROM: https://www.androidfilehost.com/?w=files&flid=134255
Recovery: https://dl.twrp.me/z3c/
Gapps: http://opengapps.org
What works?
Wi-Fi
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Video (playback)
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
Systemsounds are too loud (the soundlevel of systemsounds couldn’t be influenced by any of the loudnesssliders) - device related
Music can't be adjusted by EQ - device related
Vibration intensity can't be adjusted - device related
Touch focus doesn't work properly (until we get new blobs) - device related
Focus via Sony’s hardware (Cam) - Button doesn’t work - device related
Video recording- device related
Show weather on the status bar doesn’t work - CM related
NFC - device related
Random reboots while charging - device related
No Swipe (keyboard) - CM related
On Lockscreen there is only the actual weather displayed without location name and without icons - CM related
FLAC files could not be played - CM related
Problems with Bluetooth - device related
Theme engine is missing - CM related
Installation Instructions
Make a backup!
Unlock bootloader
Install the latest TWRP Recovery
Download the ROM and GApps
Reboot to recovery
Wipe data/factory reset if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Flash the ROM and then GApps
Reboot your phone
Enjoy!
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again. (However, if you are experiencing strange issues, you may want to try a wipe.)
OTA Updates:
Recommended recovery: TWRP
Changelog
Code:
20161206:
- Initial release
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
CyanogenMod14.1, ROM for the Sony Xperia Z3 Compact
Contributors
doriandiaconu
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 1
Beta Release Date: 2016-12-27
Created 2016-12-08
Last Updated 2017-01-06
First!
Nice one @doriandiaconu Will get testing today!
In call volume is fixed and other user experiences echo
video recording isn't functional but preview works
Also i noticed in your aries tree that you still have egl.cfg which is deprecated now
Thanks!
It seems I misplaced the thread. I'll ask one of the admins to move it.
am i correct in assuming that you will get the fisheye effect on the camera with this?
downloading right now - will give it a try and report...
@doriandiaconu OK here is my first impression:
The ROM starts without probs - i even don't have to adjust the updater script :good:
Cam starts without forceclosing - but this could be not valid for the whole time - but for now it works - the foto i have taken has still little problems with autofocus - but for now not bad
* Equalizer for Music seems not to work - there is no difference in sound while applying different presets.
* Though weather for statusbar could be selected there is no weather to be seen - the same could be said for weather on the lockscreen simply not there - i installed Yahoo CM weather Provider - but the service couldn't even accept a given location ???
* System sounds could not be adjusted - they are very loud for now - but maybe there is a hidden feature to adjust...
* NFC could not be activated - the field is insensitiv
THX for this build
Update:
Weather seems to work now - maybe some time was needed for an update - on Lockscreen Weather could be seen, but Music on lockscreen has to be deactivated
veti said:
am i correct in assuming that you will get the fisheye effect on the camera with this?
Click to expand...
Click to collapse
You are absolutely right. That's something that won't be fixed that easily (if ever)
[emoji7] [emoji7] [emoji7]
Downloading now...
Hmmm, my new home...
mcgi5sr2 said:
First!
Nice one @doriandiaconu Will get testing today!
In call volume is fixed and other user experiences echo
video recording isn't functional but preview works
Also i noticed in your aries tree that you still have egl.cfg which is deprecated now
Click to expand...
Click to collapse
You lucky bastard!!
I wanted to be first [emoji23]
A.R.I.S.E Z3C DiSCONTiNUEdSLiMM EliteKernel Phh.superuser Magisk Substratum
mcgi5sr2 said:
Also i noticed in your aries tree that you still have egl.cfg which is deprecated now
Click to expand...
Click to collapse
My bad & thanks for the info.
Maybe it is now time for the common github creation to keep all of this clean. Will see if I can do this today.
Here is z3 not working list.
Bluetooth is fixed, then break again, etc... Other meaning: Under development
Another point are deep_sleep, we are working on it but will take time.
CC: @doriandiaconu
P.S. I came from z3 and don't own z3c so only can help on basics.
Thank you for the intervention @nailyk
Will edit OP when I get home and hopefully will fix some stuff in the next days.
EDIT: can someone make a list with what it's not working? It seems some of the things took some time to settle @Rhonin86 @mcgi5sr2
Never mind .....
i think tomorrow afternoon / evening i will find some time to proceed further tests and create a list - any wishes concerning the format of the list ?
Google Doc / Excel sheet / a simple post ...
Your wish is my demand
Cheers
Rhonin
doriandiaconu said:
You are absolutely right. That's something that won't be fixed that easily (if ever)
Click to expand...
Click to collapse
It's so bad that we will not get a proper working aosp or cm rom. I'm so pissed on sony about this, probably will not buy any sony device just because of this reason.
Delete
Truth is we could get a good working camera but this implies a lot of knowledge that i don't have and a lot of time.
Sony aren't at fault for this. Look at Samsung. Because of the Exynos CPU and the knox partition they don't even hope for a CM/AOSP project, either on the S7 or the S6.
@Rhonin86 I don't mind it either way
doriandiaconu said:
Truth is we could get a good working camera but this implies a lot of knowledge that i don't have and a lot of time.
Sony aren't at fault for this. Look at Samsung. Because of the Exynos CPU and the knox partition they don't even hope for a CM/AOSP project, either on the S7 or the S6.
@Rhonin86 I don't mind it either way
Click to expand...
Click to collapse
People know there will be no custom aosp/cm rom working on exynos chipset before buying samsung phones. I bought this phone with high expectations, but regretted.
Barua said:
People know there will be no custom aosp/cm rom working on exynos chipset before buying samsung phones. I bought this phone with high expectations, but regretted.
Click to expand...
Click to collapse
On a long term, there will be development for the shinano devices. Now it's just the beginning and we are few that are working. But there's still hope. CM12.1 was good, CM13 was hardly workable because of the 3.4 kernel. Devs didn't like that and left. Now they have switched to the 3.10 kernel again and CM14.1 is less buggy than CM13.
I think I managed to fix the NFC issue. Camera will get better once the new blobs will be released. Things will get OK. But only in due time and with a lot of work.
why is fish eye so present in this device? I got that in every rom (stock even when in 4k without steadyshot)... I came to this device from xperiaZ thinking camera will rock, and now I can't even use cm/aosp cause camera is so important to me
Edit: sorry for partially off-topic :3
I am getting error 7 when installing in recovery, please help
I also got error 7 flashing this in twrp 3+ but flashed this version last week successfully. Might have to change script can't remember if i had to or not. Good luck. I'm going to keep trying this. Cant post link new user but bing "sony aries cm14.1" choose androidbiits how to install nougat 7.1 on sony z3c. The link is good.
Take out underscores and link is to rom.
ps://androidfilehost. ______-com./?______fid=385035244224400853
For people with error 7 you can just remove the first line of the install script in the zip.
For comments on the camera, to be honest no one cares what you think here. If you want to vent go to the official sony forum, the people on XDA are working with what we have. This is a development thread for CM-14.1 if you don't have anything to add about the ROM ie logcats dmesg etc or bug reports then please don't post.
https://github.com/mcgi5sr2/device_sony_aries is the device tree i used for some early builds. It was forked from latest 7.1 branch of the sonyxperiadev repos.
hey, thanks for ur work. is great. i want to ask if is possible to apply any theme. theme engine is not yet implemented, so exist another alternative?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* BOOM goes the Dynamite
*/
Working
Same as PixelExperience
Broken
Same as PixelExperience
Difference between stock lineageos 17
Stripped ART debugging
Bionic improvements from AOSPA
Remove some debugging from framework_base
device tree changes
zram 1gb -> 512mb
lazytime support for EX4 (enabled by default)
custom dalvik props:
dalvik.vm.heapstartsize=8m -> 16m
dalvik.vm.heapminfree=512k -> 2m
lMemory Optimizations (am.reschedule_service & sys.fw.bservice_enable both enabled)
Simplified version of GlassCannon interactive profile
Tune sched parameters
Cpuset tweaks
kernel changes (pop kernel):
see second post
DOWNLOAD ROM
DOWNLOAD KERNEL
Installation:
Make full wipe (Format data and also normal wipe)
Flash rom
Flash GApps if needed
Flash Magisk if needed
Flash kernel
reboot
Telegram group
Credits:
All devs that did the ten bringup,
@theandroid02 for the device tree and vendor,
@mr.ace for his shadow kernel,
Many others
XDA:DevDB Information
UNOFFICIAL OPTIMIZED LineageOS 17.1, ROM for the LG Nexus 5X
Contributors
linckandrea
Source Code: https://github.com/linckandrea
ROM OS Version: 10.x Q
Version Information
Status: Beta
Created 2020-09-15
Last Updated 2020-09-15
Features
-based on the latest shadow kernel
-Cpu governors: electron,chill,relaxed,blu_active + all stocks
-Ioscheds: maple,bfq + all stocks
-dsync
-adreno idler (disabled by default)
-cpuboost optimization
-touchboost disabled (msm_performance module)
-wakelock blocker by boeffla
-wake gestures
-many other check source
NOTE: the kernel is compatible with oreo-pie-ten so it can be flashed in other roms
reserved 2
Hey,
thanks for your ROM and kernel! I am looking forward to test it.
You say everything works like PE ROM, great.
Has someone confirmed that VoLTE and more importantly to me is Google Camera with encryption enabled actually working?
[edit] Clarified that it is a question if someone has tested if Google Camera is working is encryption enabled.
That is great, thank you!
Just flashed the kernel on my Nexus ROM and seems very smooth, maybe I'll try also the ROM!
Just to know, does your kernel ha voltage control enabled, making undervolting possible?
I ask because the section and the values appears inside Ex Kernel Manager, but I can't edit them.
RelentlesS747 said:
Hey,
thanks for your ROM and kernel! I am looking forward to test it.
You say everything works like PE ROM, great.
Has someone confirmed that VoLTE and more importantly to me Google Camera with encryption enabled is actually working.
Click to expand...
Click to collapse
Unfortunately my provider doesn't support VoLTE so i can't test it however if it works on PE i don't see why it shouldn't work here
Punkiderma said:
That is great, thank you!
Just flashed the kernel on my Nexus ROM and seems very smooth, maybe I'll try also the ROM!
Just to know, does your kernel ha voltage control enabled, making undervolting possible?
I ask because the section and the values appears inside Ex Kernel Manager, but I can't edit them.
Click to expand...
Click to collapse
Undervolting/Overvolting is not possible since kernel sysf provide only the information about voltages
i tried manual undervolting on ether(nextbit robin msm8992) and it was very unstable so it should be the same with bullhead
Can you test if Google Camera is working with encyption enabled because svlogs LOS17.1 ROM does not work for me in that regard.
Nice ROM and nice kernel.
I installed this ROM on LineageOS 17.1 by equlog and it works very well. Thank for your great work
linckandrea said:
Undervolting/Overvolting is not possible since kernel sysf provide only the information about voltages
i tried manual undervolting on ether(nextbit robin msm8992) and it was very unstable so it should be the same with bullhead
Click to expand...
Click to collapse
Sphinx kernel had working voltage control but it was never updated to support android Q.
I used it for a long time under Oreo and after finding the right values the device remained very stable.
Can this be a useful source to get voltage control working also under android Q or there are other issue that makes this not possible? I'm not a dev so sorry if this is a silly question
EDIT: I noticed that live display stops working if i flash this kernel, and also if I flash shadow kernel, so maybe there's a bug in the base. I'm on nexus rom.
GPS Problems
linckandrea said:
Installation:
Make full wipe (Format data and also normal wipe)
Flash rom
Flash GApps if needed
Flash Magisk if needed
Flash kernel
reboot
Click to expand...
Click to collapse
Hello again
I moved from NexusROM to your ROM and kernel. Encryption and Google Camera is working fine and switching from mobile data to WiFi and back is also working good (I had problems with that in the past). Thank you very much!
GPS Problems:
However I cannot get GPS working. It just never picks up a signal to locate me. Attached you can find a looong logcat log file. I think it has some gnss, Loc_hal_worker, Gps, LocSvc_eng errors in it. I suggest you start taking a look from the end of the log file. I had to split the file into two because of a 512kB *.txt file size limit.
Punkiderma said:
Sphinx kernel had working voltage control but it was never updated to support android Q.
I used it for a long time under Oreo and after finding the right values the device remained very stable.
Can this be a useful source to get voltage control working also under android Q or there are other issue that makes this not possible? I'm not a dev so sorry if this is a silly question
EDIT: I noticed that live display stops working if i flash this kernel, and also if I flash shadow kernel, so maybe there's a bug in the base. I'm on nexus rom.
Click to expand...
Click to collapse
this kernel doesn't support lineage livedisplay, in futures release i will implement klapse...
RelentlesS747 said:
Hello again
I moved from NexusROM to your ROM and kernel. Encryption and Google Camera is working fine and switching from mobile data to WiFi and back is also working good (I had problems with that in the past). Thank you very much!
GPS Problems:
However I cannot get GPS working. It just never picks up a signal to locate me. Attached you can find a looong logcat log file. I think it has some gnss, Loc_hal_worker, Gps, LocSvc_eng errors in it. I suggest you start taking a look from the end of the log file. I had to split the file into two because of a 512kB *.txt file size limit.
Click to expand...
Click to collapse
i see, thank you for the logs.. using this should fix the issue
https://github.com/LiteApplication/hardware_qcom_gps
linckandrea said:
i see, thank you for the logs.. using this should fix the issue
https://github.com/LiteApplication/hardware_qcom_gps
Click to expand...
Click to collapse
cool
I also have lots of stability issues with Google Camera.
Crashes after two Pictures or so.
RelentlesS747 said:
cool
I also have lots of stability issues with Google Camera.
Crashes after two Pictures or so.
Click to expand...
Click to collapse
i have the same issues with the google play store version, on other phones
camera NX works without problems if is installed as system app
in fact the next build i will include it by default
linckandrea said:
i have the same issues with the google play store version, on other phones
camera NX works without problems if is installed as system app
in fact the next build i will include it by default
Click to expand...
Click to collapse
Nice, do you plan to maintain this for some time?
For Volte question: there was a specific patch on PE10 for that in the device tree. i.e.: https://github.com/PixelExperience-...ackages/apps/CarrierConfig/res/xml/vendor.xml
Have you merged that changes?
linckandrea said:
this kernel doesn't support lineage livedisplay, in futures release i will implement klapse...
i see, thank you for the logs.. using this should fix the issue
Click to expand...
Click to collapse
How do you install the GPS fix? Install zip from TWRP?
Nice one! Thanks for keeping this device alive!
@linckandrea
have you found some time and passion to tackle the GPS and / or Camera Problems?
no stress, i am just wondering
@linckandrea I wonder does this ROM include live caption since I am deaf and need those feature. let me know. thanks
Updated: Ignore my asking question, i got it working and thanks
New update
download links are updated in the first post
Rom changes
Some bionic improvements from AOSPA
Stripped out some debugs in framework_base
device tree changes
radio power saving
sensors: Don't wake on significant motion
kernel changes
see this github history
i can't test the gps since... well you know the lockdown
anyway i created a telegram group where i will release early my rom/kernel builds
linckandrea said:
New update
download links are updated in the first post
Rom changes
Some bionic improvements from AOSPA
Stripped out some debugs in framework_base
device tree changes
radio power saving
sensors: Don't wake on significant motion
kernel changes
see this github history
i can't test the gps since... well you know the lockdown
anyway i created a telegram group where i will release early my rom/kernel builds
Click to expand...
Click to collapse
I just mentiond you in the other thread. I will try your build and report back about the GPS.
I'm curious if my banking apps work with your updated rom, because they don't with @berom his build and also don't work with PixelExperience