What is the difference?
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
THIS IS A UNOFFICIAL VERSION BECAUSE IT CAN'T BE BUILT AT OFFICIAL SERVER! I just want you know Mokee and other AOSP ROM can't be official unless alberto96's lineage os be official.
I won't have time to update it anymore,you can use my source to continue it.See you next summer,everyone.(if nobody want to continue it,I will update it mouthly.(Sometimes weekly)
About
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Credits:
Google, Qualcomm, Linux Kernel Organization, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser, lineageOS, TeamWin,
Smartisan Digital Co, Substratum Development Team, The Open GApps Team.
ContributorErag0n(Migrate source from Lineage OS and build a zip) @sunilpaulmathew(Thanks for his suggestions and reply, most importantly, his awesome Kernel source.) @Alberto96(all hard work)
Features
1.Fully OMS Supported
2.Xposed Framework Supported
3.Can make a dirty flash which Lineage OS can't.
4.Phone & Messaging:Quick contacts look up, speed dialing, caller location and other useful features
5.Colorful Themes:Unleash the creative side of you, customize how your phone looks; make it cool, make it colorful!
6.Smart Controls:Increase your productivity with Active Display, Lockscreen Notifications and other shortcuts
7.Power Saver:With our unique battery saving strategies, get the most out of your phone's battery
8.Latest source merge from google android source.
9.Minimal but not simplify.
10.Delta update:8~15Mb, more than 300mb download space saved.
11.OTA Update
12.Odexed
Supproted Devices
ja3gxx(GT-I9500),ja3gchnduos(GT-I9502),jaltelgt(SHV-E300L),jalteskt(SHV-E300S/K),ja3gduosctc(SCH-I959).
After Odexed,ROM may have a large size(600~700MB),but it can get a better improvement.
Enjoy it!
Change logs:
MK60.1-8.13
Alpha build,this build is a stable RELEASE version,what is RELEASE?Please see the first line of post.
MK71.2-7.23
First build,sync to latest Mokee Source.
MK71.2-7.24
Second build, sync to lastest Mokee Source, Delta update available, Automatical translation, charger:fix small capture font.
MK71.2-7.25
Sync to lastest Mokee Source, change pixel launcher to default launcher, new kernel merged, now you can use Kernel Adiutor to custom kernel governor.
MK71.2-7.25-17.06
Fixed all bug, include high sensitive screen, display mode, novbar.Alberto not fixed bug I unable to fix.
MK71.2-7.26
Sync to latest source.
MK71.2-7.27
Sync to lastest Mokee Source, Kernel updated to 3.4.113, thanks to sunil.
MK71.2-7.28
Sync to latest source, stability is improved.
MK71.2-7.28-19.31
Sync to latest source.
MK71.2-7.29~8.05
Sync to latest source,new LawnChair launcher is added.
MK71.2-8.12
Xposed app added,automatical translation.Update to android-7.1.2_r29-tag
MK71.2-8.13
Only update for ja3gchnduos,jaltelgt,jalteskt.
MK71.2-8.20
Update source,probably fixed jalteskt incoming problem.OTA update supported,Gapps added.
MK71.2-8.26
Device Source updated,PowerHAL added,odexded,improve boot speed,Blur effect added and etc.
MK71.2-8.30
Source Update,bug fix.
MK71.2-9.02
Hardware source update,in next build,Gapps will be removed.
MK71.2-9.09
Source Update and Gapps removed, device ja3gduosctc added.
MK71.2-9.15
Source Update.
MK71.2-9.23
Source Update,kernel change to origin.
Delta update and full download：
Everyone can use delta update now, even installed stock gapps.
Delta Update can save your download time but get full function which contains in full update.
Full update is made for who use Mokee just once or need system files repaired.
Delta(OTA) update will keep 1 generation system up to date, in order to save space.
Version MK 71.2-7.23~7.26
https://drive.google.com/folderview?id=0B5BV4JClBJELa19mNjU4b2ZubUk
You must choose a version which is correct for you.
Version MK 60.1-8.13&MK 71.2-7.27 and above.(You can find all ROM contains MK 60.1 in it)
https://www.androidfilehost.com/?w=files&flid=202052
Recommend Kernel: (Now is build-in in Mokee.)
SmartPack is a good kernel that can give you better battery drain and system fluency.Thanks to sunilpaulmathew for making a awesome kernel.
If you want to see more about kernel,here is the link:https://forum.xda-developers.com/ga...nel-smartpack-project-lineage-os-14-t3590858/
How to build:https://github.com/exynos5410/manifest There are some unique changes for mokee open source,if you want to build one,ask me for help without hesitation,I will try my best to help you.
Issues (copy from Alberto's post)
MK 71.2 issues:
Filesystem Socket Whitelist (https://goo.gl/1N6n7G) - The only issue that requires to be fixed in order to get official.
SELinux (Permissive)
BASED ON USERS FEEDBACK: Mobile Signal Reception isn't 100% stable.
Shared Storage (doesn't encrypt the storage)
ja3gxx: In-Call Echo Effect (random and rare)
ja3gxx: In-Call Volume can't be increased/decreased
ja3gxx: OK Google (Automatic Voice Recognition)
ja3gchnduos: Missing Dual SIM support.
jalteskt: Mobile Data and Incoming Calls don't work.
jalteskt: USSD Codes can't be sent.
jaltelgt: RIL crashes on boot, meaning that Calls/Data won't work.
MK 60.1 issues:
1.Audio HAL isn't working correctly, causing VOIP issues, HDMI audio instabilities and mixer paths conflicts
2.STK Toolkit isn't working yet, SMSs aren't properly sent (RIL issue)
3.SELinux policies are almost complete, with just some minor missing rules
4.Wireless Display (or Miracast if you like) stream is corrupted, buffer issues
5.Adoptable Storage isn't stable, crashes while encrypting the external storage (Kernel Panic). Read Here: http://goo.gl/0w6DPt
6.Device Encryption isn't stable for the same issue that affects Adoptable Storage
Problems report
You need report problems with your
ROM Version
Step to get bugs
If possible,with a logcat is better.
Source Code
https://github.com/Dracanrage
Sorry for my bad English
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.113
ROM Firmware Required: Lollipop Bootloader and Modem, TWRP 3.1.1 as Recovery
Based On: AOSP
Version Information
Status: UNOFFICIAL
Created 2017-07-23
Last Updated 2017-09-23
Screenshots
Is there any differences between Los and it?
Super Sha said:
Is there any differences between Los and it?
Click to expand...
Click to collapse
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Erag0n said:
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Click to expand...
Click to collapse
Nice work!I will try it soon. Will it be official?
Super Sha said:
Nice work!I will try it soon. Will it be official?
Click to expand...
Click to collapse
Sorry, it can't be.
As Alberto says, unless Samsung update the Kernel source to fix the Zygote problem, it can't be official.
i will try, thanks.
Is there any problem with mobile data and call echo?
tosunkaya said:
i will try, thanks.
Is there any problem with mobile data and call echo?
Click to expand...
Click to collapse
As Lineage OS, there should not have any problem with mobile data, but call echo will appear randomly (according to different hardware which Samsung use).
app to sd
how to move app to sd card ?
RahmahTunisa said:
how to move app to sd card ?
Click to expand...
Click to collapse
There is a error in make SD card as internal storage, so it can't move app to SD card in Nougat.
This error is mentioned in Alberto's post, I use his device, vendor, hardware source to make this ROM, so this ROM have the same problem.
What about battery draining?
It's like lineage ?
Mohamed rajab said:
What about battery draining?
It's like lineage ?
Click to expand...
Click to collapse
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Hey, guys.
Delta update is come back now, you will see it in today's update.
Edited
Delta update is available.
Camera2.zip for installed stock gapps guys.
About how to use, please read the main post.
Edited
This file is useless, you need get Camera2.app from 7.23 ROM zip.
Edited 7.25
Mokee updated the check script, it is no need to keep Camera2 installed.
Nice work
Thank you so much
Erag0n said:
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Click to expand...
Click to collapse
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
nebrassfarfoor said:
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
Click to expand...
Click to collapse
Yes, you can use aroma, but had better not install Google camera in order to use delta update.
It support remapping the hardware but not support long press custom.
About bugs, please read the main post
About battery drain, Mokee Open Source make some optimizations, and kernel is not been limited.
About using smartpack Kernel, you can use twrp to flash it, and I am working for merge smartpack kernel to Mokee.
About telegram group, I am so sorry that I can't make one because Chinese telephone number is limited in sent message to strangers.
Hey, guys.
I fixed my S4 today.
Now I can test a amazing Kernel.
Thanks to @sunilpaulmathew for his help and smartpack source.
Hi
Bug = not notification miscall and sms
deletanha said:
Hi
Bug = not notification miscall and sms
Click to expand...
Click to collapse
Oh, it was terrible.
Let me check.
Waiting for a minutes please.
Edited
In my S5 official Mokee, missing was common if I use Aegis.
Did you use it?
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"
}
Click here to get to the new post where we'll keep updating this rom
What it is
It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)
Disclaimer
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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
What gapps to flash?
Use f-droid
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!
NEW RELEASE
2017-06-13:
Xperia Z3
Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09
Xperia Z3 Dual
See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.
Temporal Z3 Dual rom (fixes SIM problems)
nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody
Click to expand...
Click to collapse
What's new:
Code:
- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness (again)
Release notes:
2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual
Older Releases
Based on Kernel 3.4
Some of these can be found here
Release History
Code:
2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17)
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU
2017-05-17:
- Tweaked general audio output processing
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates
2017-04-16
- Audio changes,
- NFC fixes,
- Brightness changes,
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more
2017-04-05:
- Enforcing selinux
2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now
2017-03-22:
- Full rework based on stock 3.4 kernel
Based on Kernel 3.10 by @nailyk
2017-01-23:
Download
md5: 04a3a614d820df78e7a70538df61203d
sha1: 10a3ea95d823a6b87b5f5a8f79896e3dabf7a8b5
Status
Workaround for in-call reboot
Include PR1130 PR1128
2017-01-15:
Download / 2
md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
Use of the reworked device trees
Include some experimental kernel pull requests
2017-01-01:
Download
md5: 6c5abcbeda01c75344cd4296bb2358d1
sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
Switch to LineageOS
Bluetooth deepsleep fixed
2016-12-02:
Download
md5: 496de65608fd4236f5d451a4179e1ce8
sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
Bluetooth improvements
P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.
Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.
XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3
Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-09
Created 2016-11-27
Last Updated 2017-07-01
Thank you!
Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5
All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.
TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me
FAQ
How to post
I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.
This is not against you but try to keep thread clean as a dev reference. Thanks in advance.
What is not working
BT headset calls --> pending. Detailed post.
OTG --> 2017-04-16
Wifi auto connect (boot/deepsleep),
HW Encryption, --> 2017-04-16
Vibrator level
4k (unfixable without Sony camera app)
120 fps (pending)
Some volume loudness problem --> not reported
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
Slow charging,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
NFC, --> topic
Wifi access point,
Adaptive brightness not good. --> Fixed by @xkeita
How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward
Some examples:
I cannot record videos with open camera.
Click to expand...
Click to collapse
Is useless on a dev thread and you probably won't get an answer.
Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Click to expand...
Click to collapse
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.
This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)
@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
steadfasterX said:
You talked about using IRC to get support. What is this and how can I use that?
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
Click to expand...
Click to collapse
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.
How to contribute
I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.
What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.
Thanks for posting this rom. Thank you for your awesome developing.
Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks
great work and z3 compact?
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
Click to expand...
Click to collapse
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?
Click to expand...
Click to collapse
Can you report me as I can answer please?
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
Click to expand...
Click to collapse
Well, thanks then.
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.
drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Click to expand...
Click to collapse
IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.
If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
Click to expand...
Click to collapse
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
Click to expand...
Click to collapse
Hey no problems, I'm actually battling just to get my latest CM build to install properly
mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly
Click to expand...
Click to collapse
Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.
2016-11-28 release
Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.
Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.
This rom is not intended to be used as a daily driver and is unstable!
cm14.1 wowww :good:
After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?
April 7. New release, Slim 0.18.
1. Accidental f/c of apps, such as browser, gallery and some others has been fixed. Nothing f/c anymore. The interface is fast and smooth. As a matter of fact, this is the fastest among the ones I have tried. Do and experiment. If you are on DU or Lineage, press virtual button for recents and then back to virtual button for home. Do it several times: in other roms, there is a delay. In this rom, the transition is instantaneous. The same is if you want to bring up phone dialer: no delay on this rom.
2. The rom has an interface for enabling/disabling sim cards
3. Recents: some people complained they didn't like Slim recents. If you want vanilla android recents, just disable Slim recents in settings
Plus other improvements...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=24111
__________________________________________________________________________________________________________
April 1: Rom updated. Phone calls and WIFI now work. Confirmed. This is Slim's release 0.17.
Latest sources plus
1. Zen Decision Hotplug
2. Intelithermal management
3. Magisk included and incorporated in settings
4. Substratum in settings - will show up, once installed
5. Vibration adjustment in kernel (you need KernelAdiutor for that)
6. Option to disable USB access (no access, no on lockscreen and yes to all
7. Option to disable/enable access to clipboard - off by default, so, if you want to copy/paste, enable it in Settings/Security
Remember, you need Afwall to have the internet
_______________________________________________________________________________________________________
Hello, Z2 plus users!
I am the creator of Jaguar rom for Sony Xperia Z1/Z1c/Z2/Z3/Z3c, which is quite popular. Recently, I have switched to Zuk Z2 and here is my first presentation for this device: Unofficial Slimrom with custom 3.18 kernel.
Everyone knows Slimroms, so I won't be describing much. It is based on AOSP and includes some special Slim features, which everyone knows.
Kernel is a Zuk 3.18 kernel with heavy modifications, including my own taken from Jaguar:
1. Implementation of some features from Grsecurity
2. Yama security enabled
3. Mixed hardware and software random number generation
4. Sleep issue has been completely resolved
Other features that are not in Slim
Magisk is included with open source Superuser, credit to topjohnwu and phhusson
Credit: Slimroms, Davidevinavil for initial device tree and vendor files
Instructions: Keep in mind that flashing this rom will take about 1.5 min longer, because it is zipped the Omni way, i.e., no dat files, but rather the full system structure..
1. Obviously, unlocked bootloader and TWRP installed
2. In TWRP wipe /system/data/cache/dalvik-art
3. Flash the rom and reboot
IMPORTANT: this rom has a script that runs on early boot that cuts the internet for both data and wifi to prevent leaking. To have the Internet you have 2 options:
1. Install Afwall, set it up, allow access to apps you want to connect (or all, if you don't care), enable Afwall and you'll have the internet;
2. If you don't care that all your apps will be connecting to the Internet all the time wasting battery and leaking data, use any root explorer, go to /system/etc and delete crashdod.sh file. Reboot.. Or you can do this before flashing: unzip the rom, delete the same file (crashdod.sh), rezip and flash...
Download Rom April 1 https://www.androidfilehost.com/?fid=817550096634758903
Issues: if you find any and want them to be addressed, submit a logcat. Without logcat I won't bother to fix...
Kernel Source: https://github.com/AOSP-Jaguar/android_kernel_zuk_z2_plus
XDA:DevDB Information
Slimrom Nougat 7.1.1 Unofficial, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/AOSP-Jaguar/android_kernel_zuk_z2_plus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader and TWRP Recovery
Based On: Slimrom
Version Information
Status: Beta
Current Beta Version: 0.17
Created 2017-03-21
Last Updated 2017-03-30
Pictures
Here are some screenshots...
Reserving
Reserving
thanx for the work, bro.
what camera you put in this rom?
I don't know nothing about Jaguar roms.
this device has an amazing hardware, I expect you bring to us a great software solution!
ROGGGER3G said:
thanx for the work, bro.
what camera you put in this rom?
I don't know nothing about Jaguar roms.
this device has an amazing hardware, I expect you bring to us a great software solution!
Click to expand...
Click to collapse
Check this thread for Jaguar: https://forum.xda-developers.com/xperia-z1/orig-development/rom-aosp-jaguar-lp-5-1-1-r13-official-t3188925
Camera: I haven't touched anything, so this is Slim's Camera2. And it works fine: video doesn't stop after 30 seconds unlike on other roms...
Wlan
Too bad . Wlan does not work in Germany
:crying:
auto99 said:
Too bad . Wlan does not work in Germany
:crying:
Click to expand...
Click to collapse
There is no reason wifi shouldn't work in Germany. Just let it scan, as it would take longer the first time...
auto99 said:
Too bad . Wlan does not work in Germany
:crying:
Click to expand...
Click to collapse
Actually, you were right. I forgot to mention (and I have already updated the OP), that the rom has a script running on early boot that cuts the internet to prevent data leaks. You have 2 options, depending on what you want, described in the OP...
Can you port stock ZUI camera and put in this rom?
I tried to but failed.
I guess its possible cuz naptha included it in his aosp 7 rom.
There are plenty roms but all with bad camera
Internet
Hello
Thank you very much. Works now best
cu auto99
VoLte is not working.
Torres.09 said:
Can you port stock ZUI camera and put in this rom?
I tried to but failed.
I guess its possible cuz naptha included it in his aosp 7 rom.
There are plenty roms but all with bad camera
Click to expand...
Click to collapse
The best camera for this and other roms is Open Camera. I had stock camera for about 2 days and I didn't notice any difference between stock and AOSP, especially now, when video recording no longer stops after 30 seconds...
miju12 said:
VoLte is not working.
Click to expand...
Click to collapse
Volte has stopped working with r26 and up. And generally, there are problems with March security patches, which broke a few things. But we'll resolve that...
optimumpro said:
Hello, Z2 plus users!
I am the creator of Jaguar rom for Sony Xperia Z1/Z1c/Z2/Z3/Z3c, which is quite popular. Recently, I have switched to Zuk Z2 and here is my first presentation for this device: Unofficial Slimrom with custom 3.18 kernel.
Everyone knows Slimroms, so I won't be describing much. It is based on AOSP and includes some special Slim features, which everyone knows.
Kernel is a Zuk 3.18 kernel with heavy modifications, including my own taken from Jaguar:
1. Implementation of some features from Grsecurity
2. Yama security enabled
3. Mixed hardware and software random number generation
4. Sleep issue has been completely resolved
Other features that are not in Slim
Magisk is included with open source Superuser, credit to topjohnwu and phhusson
Credit: Slimroms, Davidevinavil for initial device tree and vendor files
Instructions: Keep in mind that flashing this rom will take about 1.5 min longer, because it is zipped the Omni way, i.e., no dat files, but rather the full system structure..
1. Obviously, unlocked bootloader and TWRP installed
2. In TWRP wipe /system/data/cache/dalvik-art
3. Flash the rom and reboot
IMPORTANT: this rom has a script that runs on early boot that cuts the internet for both data and wifi to prevent leaking. To have the Internet you have 2 options:
1. Install Afwall, set it up, allow access to apps you want to connect (or all, if you don't care), enable Afwall and you'll have the internet;
2. If you don't care that all your apps will be connecting to the Internet all the time wasting battery and leaking data, use any root explorer, go to /system/etc and delete crashdod.sh file. Reboot.. Or you can do this before flashing: unzip the rom, delete the same file (crashdod.sh), rezip and flash...
Download Rom: https://www.androidfilehost.com/?fid=457095661767147159
Issues: if you find any and want them to be addressed, submit a logcat. Without logcat I won't bother to fix...
Kernel Source: https://github.com/AOSP-Jaguar/android_kernel_zuk_z2_plus
XDA:DevDB Information
Slimrom Nougat 7.1.1 Unofficial, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/AOSP-Jaguar/android_kernel_zuk_z2_plus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader and TWRP Recovery
Based On: Slimrom
Version Information
Status: Beta
Current Beta Version: 0.7
Created 2017-03-21
Last Updated 2017-03-21
Click to expand...
Click to collapse
The official builds are at the 0.16 beta... Why is this only at the 0.7? Btw you chose a nice rom. I hope that will become a stable rom.
DD3Boh said:
The official builds are at the 0.16 beta... Why is this only at the 0.7? Btw you chose a nice rom. I hope that will become a stable rom.
Click to expand...
Click to collapse
It is 0.16. I have changed the OP.
optimumpro said:
It is 0.16. I have changed the OP.
Click to expand...
Click to collapse
Ok, nice.
Great rom
I will keep an eye on that rom one of the best for our device.
I have only one issue, things slowdown when scrolling through Google+. The stock nougat rom has the same issue. Keep up the good work
Nice rom. Smooth and minimal. Haven't encountered any bug in my usecase. Will keep an eye on the development as slim has always been one of the favorite roms for me. Also, a different take on kernel and features is nice to see. Good job!
KKaushal said:
Nice rom. Smooth and minimal. Haven't encountered any bug in my usecase. Will keep an eye on the development as slim has always been one of the favorite roms for me. Also, a different take on kernel and features is nice to see. Good job!
Click to expand...
Click to collapse
Everything is smooth because hardware overlays are disabled by default in framework.
By the way, Jaguar N for Zuk Z2plus is almost done. In addition to other features, you will have alucard, darkness, and nightmare governors. You will also have Zen decision hotplug, as well as vibration sensitivity adjustment. Also, slim recents and memory ram bar; a switch to disable/enable clipboard access; hardened bionic with runtime permissions set to read only, so that third party apps can't manipulate android...
optimumpro said:
Everything is smooth because hardware overlays are disabled by default in framework.
By the way, Jaguar N for Zuk Z2plus is almost done. In addition to other features, you will have alucard, darkness, and nightmare governors. You will also have Zen decision hotplug, as well as vibration sensitivity adjustment. Also, slim recents and memory ram bar; a switch to disable/enable clipboard access; hardened bionic with runtime permissions set to read only, so that third party apps can't manipulate android...
Click to expand...
Click to collapse
Great rom keep up the good work. eagerly waiting for the new rom.
can u reproduce this one issue, things slowdown when scrolling through Google+?. The stock nougat rom has the same issue. Hope u can fix it
The Unlegacy Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for hammerhead include:
BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
Volume button wakeup (setprop persist.wm.volume_wake_screen 1)
Last upstream (kernel/msm) hammerhead kernel tag merged
Charging LED control (setprop persist.sys.led_on_charger 0)
Enhanced backlight map for lower min brightness
Night display blue light filter (GLES-based)
KCAL & PCC color temperature interfaces
Other security patches & minor bug fixes
F2FS support from K4.4 backports
SELinux in Enforcing mode
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post.
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
No known issues on Nougat builds
See post #3 for Oreo/Pie notes
If you notice anything, be sure to report it in this thread. Stability is our main concern. While it may takes some time, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
Also, we'll have a built-in OTA updater (just like stock) soon (it's a work in progress).
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see second post). The aim of this project is to create a fast and stable ROM, as close to AOSP as possible without diminishing usability. Occasionally, small non-AOSP features may be implemented, provided there is a clear need and they make sense on hammerhead.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Google Nexus 5
Contributors
amaces, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-04-18
Current Beta Version: 9.0.0
Beta Release Date: 2017-10-02
Created 2017-04-21
Last Updated 2018-10-30
GApps
If you want to install GApps, we recommend micro packages on N builds (e.g., Open GApps), and pico otherwise.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
Rooting
You can flash the latest SuperUser (phh's open source fork), Chainfire's SuperSU, or Magisk to get rooted.
Oreo/Pie Status & CAF Notes
Oreo 8.1 builds are almost bug-free at this point, but still tagged as experimental. While last issues are sorted out, I will trigger manual builds, also published at https://builds.unlegacy-android.org/aosp-8.1/hammerhead.
To my knowledge, these are the remaining issues:
Bluetooth HFP speaker (mono/SCO) output is garbled. This seems related to a more general issue with audio effect/ACDB blobs.
Once all visible issues are fixed, and stability is comparable to Nougat builds, I'll switch on official builds on our Jenkins server.
Pie 9.0 builds are also becoming fully usable. Current builds have the same one remaining HFP bug described above.
Beyond "official" experimental builds, I post personal builds (including CAF experiments) in the hammerhead folder here.
Regarding sources for the WIP CAF kernel-based builds, see https://github.com/airend/android_kernel_lge_hammerhead/commits/tmp/caf+113+common. Corresponding device tree is still in rough shape and not uploaded yet, but assuming everything goes well, it'll replace current device tree when it's ready.
I've used the 05/04 build for 2 days a few weeks ago and it was a great rom.
The only issue I came across back then was that it has the green flickering when recording videos.
It's nice that the project has a XDA thread now and I gonna test this rom asap.
Thanks for keeping our good old Nexus 5 up to date.
Nexive said:
The only issue I came across back then was that it has the green flickering when recording videos.
Click to expand...
Click to collapse
Should be fixed on current builds (both green bar, and Google Camera flickering).
have a volume wake option?
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
alessio89g said:
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
Click to expand...
Click to collapse
No, all UA ROMs have this issue fixed
Ziyan said:
No, all UA ROMs have this issue fixed
Click to expand...
Click to collapse
Great, I think I'll try this ROM tomorrow!
--- --- ---
EDIT:
Is there any kind of changelog?
--- --- ---
RE-EDIT:
Okay, I found this:
https://gerrit.unlegacy-android.org
Hi....
Any screen shot?
keretapanau said:
Any screen shot?
Click to expand...
Click to collapse
Umm… it's barebones AOSP?
Buttery smooth,everything seems to be working fine here..Awesome jobs dev..keep it up.Finally this is the rom i been waiting for.:good:
CreateYourDream said:
have a volume wake option?
Click to expand...
Click to collapse
It is not an AOSP feature. It is something custom roms introduced.
Android-Andi said:
It is not an AOSP feature. It is something custom roms introduced.
Click to expand...
Click to collapse
thanks for answer, but i have broken power button :crying:
Cant Install Gapps
I've flashed it for about half a day, and it's very promising, it seems a great ROM!
I've noticed only three defects:
- The blue light filter (Night mode) is missing;
- With stock kernel, SuperSU will be in system mode;
- The Clock app crashes if you try to add another Time zone in the main screen.
Everything else works fine.
CreateYourDream said:
thanks for answer, but i have broken power button :crying:
Click to expand...
Click to collapse
Did you try this
Check out "Custom Navigation Bar"
https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Thanks for the ROM guys!
When I flash Open Gapps this message appears:
"This Gapps pkg is for Android 7.1.x ONLY
Please download the correct version for you ROM: 5.1.1 (SDK 22)"
I've flashed build ua_hammerhead-7.1.2-20170423031839 before gapps
Is there any alternative app for kcal..?KCAL app seems to be force closing once installed.
substratum support please
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
What's working
Mostly everything
How to install
1. Wipe system, data and both cache partitions
2. Install ROM + GApps
3. Wipe again both cache partitions
4. Now you can boot to the system
Download
Unofficial LineageOS 14.1
opengapps
Sources
github.com/sgspluss
Credits and Thanks
@sgspluss @Nikit @golden-guy
Changelog
Code:
[B]lineage-14.1-20180805-UNOFFICIAL-athene.zip[/B]
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180721-UNOFFICIAL-athene.zip[/B]
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180715-UNOFFICIAL-athene.zip[/B]
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180626-UNOFFICIAL-athene.zip[/B]
Revert CPU overclock
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180620-UNOFFICIAL-athene.zip[/B]
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180612-UNOFFICIAL-athene.zip[/B]
Add again given 1,6GHz as max frequency for big cluster
Add some more memory leak fixes
Revert adreno idler
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180528-UNOFFICIAL-athene.zip[/B]
Add kernel based exfat support
Revert power saving lines they do nothing
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180523-UNOFFICIAL-athene.zip[/B]
Add some power saving lines into build.prop
Add enable LPM prediction
Revert vulkan because its not supported
Clean up system.prop a bit
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180520-UNOFFICIAL-athene.zip[/B]
Add rebased kernel 3.10.108
Revert CPU overclock
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180519-UNOFFICIAL-athene.zip[/B]
Add Kernel update from 3.10.107 to 3.10.108
Remove Updater because we are not offical
Revert GPU overclock
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180504-UNOFFICIAL-athene.zip[/B]
Add given 1,6GHz as max frequency for big cluster
Add GPU overclock to 600MHz
Some other frequency changes
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180501-UNOFFICIAL-athene.zip[/B]
Add few memory leak fixes
Sync with latest LineageOS sources
Sync with latest TeamButter sources
Some other device and kernel stuff
[B]lineage-14.1-20180425-UNOFFICIAL-athene.zip[/B]
Initial stable release
Troubleshooting
Playstore show not certified
Try to clean app data and cache first, if its not working for any reason read this
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Low RAM Configuration
Add the four lines into your build.prop with any rootexplorer you want, save it and restart your phone to activate them.
Code:
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
If you need more information read this
https://source.android.com/devices/tech/perf/low-ram#intro
Can you point what advantages this build has comparing to official 14.1 Los?
can you point out this app https://play.google.com/store/apps/details?id=com.bsb.hike why this app is not working with los14.1 i try this app but this app is stuck on almost ready screen please can you check this app in on your device thanks in advnce ?
Thanks @sgspluss. Does this room support microg?
Does moto camera works in this rom.?
niyas90 said:
Does moto camera works in this rom.?
Click to expand...
Click to collapse
Yes working
Iamanel said:
Can you point what advantages this build has comparing to official 14.1 Los?
Click to expand...
Click to collapse
It contains all good changes from my los15.1 rom, for example slightly OC CPU/GPU more memory leak fixes and so on.
My goal was performance and good battery life time and of course stable rom, as written in OP you can see it as fallback if you are unhappy with lineageos 15.1 at the moment.
halifage said:
Thanks @sgspluss. Does this room support microg?
Click to expand...
Click to collapse
Its not a part of this rom, but if you get an flashable zip with needed files to get it work, it should.
This time just kernel update...
Updated version from .107 to .108.
Should speed up overall performance and little memory leak patches.
Download could be found in OP under download - updated kernel.
Remember its an .img file so flash in TWRP as image, or if you are rooted flashify or else.
You've done a wonderful job. Finally I found a better ROM than InvictaOS.
So far so good, I just can point out this tiny bug:
*When we switch to see Recent Apps, both Lock and Close(X) button takes a decent time to load.
*After flashing boot.img, I've lost chop-chop.
Other than that, there are few things I miss from InvictaOS like Memory Available when switching to Recent Apps, Temperature on Lockscreen when charging and LED management. But as you can see, they are minor features.
Thanks again.
ebol94 said:
You've done a wonderful job. Finally I found a better ROM than InvictaOS.
So far so good, I just can point out this tiny bug:
*When we switch to see Recent Apps, both Lock and Close(X) button takes a decent time to load.
*After flashing boot.img, I've lost chop-chop.
Other than that, there are few things I miss from InvictaOS like Memory Available when switching to Recent Apps, Temperature on Lockscreen when charging and LED management. But as you can see, they are minor features.
Thanks again.
Click to expand...
Click to collapse
Will take a look about chopchop maybe i've forgott something.
Overall performance should be better in next update.
No features request i am did not add anything, this is lineage and not xyzrom.
Sent from my athene using XDA Labs
New update is out...
If you want to know whats new, read post #2 https://forum.xda-developers.com/showpost.php?p=76341261&postcount=2
So far so good. ChopChop is working again. I haven't notice any change in performance, but will update if anything happen.
Nice work!
I'm getting crashes in the official 14.1 LOS, do you happen to know if this issue is fixed for the XT1625 in your version?
ebol94 said:
So far so good. ChopChop is working again. I haven't notice any change in performance, but will update if anything happen.
Nice work!
Click to expand...
Click to collapse
Perfect... :good:
Slayer5934 said:
I'm getting crashes in the official 14.1 LOS, do you happen to know if this issue is fixed for the XT1625 in your version?
Click to expand...
Click to collapse
What crashes? So far all ok on official and mine for me.
Slayer5934 said:
I'm getting crashes in the official 14.1 LOS, do you happen to know if this issue is fixed for the XT1625 in your version?
Click to expand...
Click to collapse
Give it a try. Remember to wipe everything except external sd.
New update is out...
If you want to know whats new, read post #2 https://forum.xda-developers.com/showpost.php?p=76341261&postcount=2
I would like to really thank you dev, for the constant updates and fixes put into this. This phone was my luckiest purchase in life! Even if we don't get P for a number of reasons we are well passed end of life but developers like you keep athene alive! All I can use to express my thankfulness is words, so, here they are, for you and the other amazing developers in this forum. :victory:
Finally, LOS 14.1 Is better than stock. Smooth and the performance is so perfect. Everything is working without any problems. Thanks for all your effort, dev ?
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Gemini forever alive!
Download:
TWRP with 4.4 kernel
LineageOS 17.1
Installation:
If you are on stock TWRP you need to flash 4.4 to avoid any problems like /data corruption!
You need to perform a factory reset (format /data)!
Flash rom, gapps/microG and optionally magisk.
Known bugs:
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Join Mi5 group on Telegram
Please consider donating to my hard work
https://paypal.me/xNombre
XDA:DevDB Information
Enchanted LineageOS 17.1 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-01-06
Last Updated 2020-04-02
Reserved
Antutu Score
Reserved
¯\_(ツ)_/¯
Thanks for your hard work
hi
tanx 4 ur hard work
i want know about battery life plz..
install instruction?
and best frimware?
tanx
Can not change battery icon style it is stuck on Icon Portrait.
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
do we need jdc treble for this or what? since it "treble"
What about battery life?
can i flash other android 10 gsi based on this rom since it "treble"
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
nebik said:
Can not change battery icon style it is stuck on Icon Portrait.
Click to expand...
Click to collapse
It's LOS bug.
3V0LU710N said:
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
Click to expand...
Click to collapse
1. AFAIR not yet because it's not merged on LOS.
2. Probably no because there are too many custom changes made (dt & vendor) and I don't like listening to moaning that something is broken. I want to release more interesting ROMs some day (Syb... uhh ekh... eria).
shandianex1 said:
can i flash other android 10 gsi based on this rom since it "treble"
Click to expand...
Click to collapse
Hmmm, that's interesting question. I've only focused on making it fulfill all Android Q requirements concerning vendor separation (and such as APEX), not intended to make it GSI friendly. I guess there are still some incompabilities and you can't expect such and old device to be GSI friendly.
jackryder38 said:
What about battery life?
Click to expand...
Click to collapse
Test yourself, the biggest culprit about I can do nothing more is RIL. Maybe when Xiaomi releases Q for daisy, the blobs will make it better.
RmznDndr said:
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
Click to expand...
Click to collapse
The group is protected with antibot, I've checked your nickname and youre not banned for sure.
Enchanted LineageOS updated!
Changelog:
Merge latest kernel_common and CAF tag into kernel
Merge latest branch into qcacld driver
Use fq_codel queuing discipline, faster net
Update some blobs (those I have access to) from LA.UM.8.6.r1-02900-89xx.0
Remove unused move time data script
Add missing wifi mac generator
Fix USB tethering
Uprev Mapper to 2.1
Tweak Dalvik parameters accroding to new google configs
Go back to stock WiFi config and add some new Xiaomi edits - fixes connectivity problems
Rootdir updates
Minor cleanup
Fixup microG location
Massive overlay update from LA.UM.8.6.r1-02900-89xx.0
Selinux enforcing
Safetynet PASS!!!
Important LOS updates:
Fixed battery style
Updated to android 10.0 r23
Added survival script (magisk reflashes itself)
Repo sync all
Download via sf:
https://sourceforge.net/projects/xn...-17.1-20200119-UNOFFICIAL-gemini.zip/download
Please consider donating...
https://paypal.me/xNombre
xNombre said:
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Known bugs:
Speaker playing only left channel
5GHz hotspot
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Click to expand...
Click to collapse
Fixed?
PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
nebik said:
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
Click to expand...
Click to collapse
Use this Gcam
https://easyupload.io/5ms9tu
It's version 7.2 - optimized and working 100% on gemini
PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
xNombre said:
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
Click to expand...
Click to collapse
I have problem with permission name (icon != Permission name)