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?
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?
Central project page
https://forum.xda-developers.com/xperia-xz2/development/rom-lineageos-17-1-t4044653
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
How is the fingerprint sensor responsiveness as compared to the stock android 10? This is the biggest grip coming from 9 to 10, it's almost useless if the screen is off.
SODP and STOCK using different drivers
Here the FP is fast.
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
Wait for the OEMv9c release
Don't use it with OEMv9b
Is my SODP based LineageOS Port still needed or are the users moved to PixelExperience or the stock based LineageOS which both are official and receive OTA updates?
If yes, I will EOL the SODP based LineageOS port and focus on other stuff.
I unlocked the bootloader few days ago, after 1 stock year, and I'm trying the official LineageOS (the other one thread).
MartinX3 said:
Is my SODP based LineageOS Port still needed or are the users moved to PixelExperience or the stock based LineageOS which both are official and receive OTA updates?
If yes, I will EOL the SODP based LineageOS port and focus on other stuff.
Click to expand...
Click to collapse
Hi Martin,
I'm testing stock based LineageOS since two days.
Unfortunately this rom works better for me; everything is working. (no matter if it's official or not)...
- the rom is fasterrrrrrrrrrr. It's just like you had a 3/4 year old phone and you by a flagship...
- Lte 2.25Mbps / 141Mbps.
- There was a lot of distortion in my speaker with Whatsapp calls. It was unusable.
- Notification led was most of time not blinking for new notification.
- Sometime my touch screen gets mad. When I tipped one time a letter it wrote me 2 or 3 time the same letter or the status bar was scrolling down...
- Waking up the phone with fingerprint was not possible.
I really appreciate all your efforts to be the first to port LineageOS for our XZ2C. Thank you very much, for your willingness to quickly answer our (sometime noob) questions.
This post must no sound like a good bye, if you EOL the SODP based LineageOS tell me witch is the next smartphone you'll buy so I'll be sure they will be a LineageOS ported
EDIT : where is the "PINT" Smilies ???!!!
Raphos said:
Hi Martin,
I'm testing stock based LineageOS since two days.
Unfortunately this rom works better for me; everything is working. (no matter if it's official or not)...
- the rom is fasterrrrrrrrrrr. It's just like you had a 3/4 year old phone and you by a flagship...
- Lte 2.25Mbps / 141Mbps.
- There was a lot of distortion in my speaker with Whatsapp calls. It was unusable.
- Notification led was most of time not blinking for new notification.
- Sometime my touch screen gets mad. When I tipped one time a letter it wrote me 2 or 3 time the same letter or the status bar was scrolling down...
- Waking up the phone with fingerprint was not possible.
I really appreciate all your efforts to be the first to port LineageOS for our XZ2C. Thank you very much, for your willingness to quickly answer our (sometime noob) questions.
This post must no sound like a good bye, if you EOL the SODP based LineageOS tell me witch is the next smartphone you'll buy so I'll be sure they will be a LineageOS ported
EDIT : where is the "PINT" Smilies ???!!!
Click to expand...
Click to collapse
Thank you very much for your friendly critics.
About the next phone, it depends when my XZ2 got damaged and if I am unable to repair it.
24.08.2020
Since we have now an official LineageOS based on stock, this ROM would be double work.
So I stop the LOS port.
(Sadly unless a dev owns a XZ2P or XZ3 these phones won't be supported in the official stock based LineageOS)
The only difference between the stock and SODP editions are:
SODP will get GCAM support later and has camera2API level 3.
stock will never support GCAM apps and has the limited stock camera2API level.
SODP uses a 4.14 kernel and probably get mainline support later.
stock uses the stock 4.9 kernel and will probably be there forever.
SODP targets to use as much open source as possible.
And LiveDisplay doesn't work in my SODP version.
PS: After the September exams in the new semester I look for a ROM replacement for the sake of diversity.
It's good to have a choice and with the available official supported SODP based Pixel Experiment, we have a ROM which sadly forces you to use the full GAPPS (Google Apps package).
Click to expand...
Click to collapse
24.08.2020
Since we have now an official LineageOS based on stock, this ROM would be double work.
So I stop the LOS port.
The only difference between the stock and SODP editions are:
SODP will get GCAM support later and has camera2API level 3.
stock will never support GCAM apps and has the limited stock camera2API level.
SODP uses a 4.14 kernel and probably get mainline support later.
stock uses the stock 4.9 kernel and will probably be there forever.
SODP targets to use as much open source as possible.
And LiveDisplay doesn't work in my SODP version.
PS: After the September exams in the new semester I look for a ROM replacement for the sake of diversity.
It's good to have a choice and with the available official supported SODP based Pixel Experiment, we have a ROM which sadly forces you to use the full GAPPS (Google Apps package).
Click to expand...
Click to collapse
Hi, i have flash the rom and everything works fine.
But even though I got root with magisk I can't uninstall system apps as the system folder doesn't have RW permissions.
I can't even install TWRP because at every boot it always enters the lineage recovery.
Can someone help me?
I'm sorry for my english
andreux481 said:
Hi, i have flash the rom and everything works fine.
But even though I got root with magisk I can't uninstall system apps as the system folder doesn't have RW permissions.
I can't even install TWRP because at every boot it always enters the lineage recovery.
Can someone help me?
I'm sorry for my english
Click to expand...
Click to collapse
Please remount the systempartiiton as RW in android.
Hi,
My device: Sony Xperia XZ2 Compact, version SO-05K, NTT DoCoMo, Android 10 > working well.
.
I tried to install LineageOS 17.1 on the Xperia XZ2c.
I followed the page https://wiki.lineageos.org/devices/xz2c/install
- Performed the basic requirements.
- The latest recovery file 'lineage-17.1-20210514-recovery-xz2c.img' has been installed.
Recovery installed in 'Active slot: a'.
- 'Factory reset', then 'Format data / factory reset' was done.
- Sideload package using: 'adb sideload copy-partitions-20210323_1922.zip'
Everything went well, but when installing the update 'lineage-17.1-20210514-nightly-xz2c-signed.zip' an error occurred and does not allow to proceed:
.
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
That said, I am not an expert.
Someone can help me?
Sorry for the bad English.
EDIT:
.....
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc(89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
.....
Someone can help me?
ProtonAOSP • Pixel 3a
Android 11 ROM
ProtonAOSP is a minimal custom Android 11 ROM focused on UI/UX and performance, with a touch of privacy.
Instead of customization it is focused on more smoother experience.
Installation
1. Unlock Bootloader
2. fastboot flash boot boot.img
3. Reboot to factory and factory reset
4. adb sideload rom.zip
5. RebootNote:- Rom already comes with gapps included so no need to flash them
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Download HereKnown issues
No eSIM support(I plan to add in next build)
Join the Telegram group for support
Kernel source code
ROM source code
This is just a side project, I may or may not maintain it in future.
A huge thanks to @kdrag0n for the amazing rom and the work done on this rom.
Reserved
I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.
96carboard said:
I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.
Click to expand...
Click to collapse
1. Soon I'll push source
2. I do have microg build for sargo as it is my main device, but not for bonito, so I did not post here on xda, if you want it join the support link group in the thread. Regarding google crap, for some users flashing gapps externally had less fluid experience so I did it.
I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?
96carboard said:
I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?
Click to expand...
Click to collapse
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.
FoxA said:
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.
Click to expand...
Click to collapse
Thank you very much. I'll give that a go
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
sorry, I don't have the device anymore.
The link download is not working, please update it
cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
Here's a current source.
I don't know if it's trusted, or who the maintainer of this unofficial build is though. Just found it via telegram.
ProtonAOSP - Browse /ProtonAOSP at SourceForge.net
sourceforge.net
Nice one. It's really handy to be able to revive old, unsupported devices like the Pixel 3a, which is a perfectly usable phone and can be picked up for next to nothing.
Some of us don't care about de-googling our phones and really just want to extend their lifespan with security updates, so having gapps baked in to ProtonOASP is really nice. Especially when we're just trying to help out our non-technical friends get a bit more life out of their old phones. A consistent, familiar user experience is all they really want.
I was wondering though: Does your build (or any build of ProtonOASP) come with verified-boot signatures so that the device's bootloader can be locked down after the ROM is installed, or is CalyxOS the only option for this?
Unfortunately, Calyx are very puritanical when it comes to de-googling, and microG is just a terrible substitute for interacting with Google services. I tried it on the Pixel 3a, and it doesn't even sync the contact list from your Google account. My non-technical friend was not impressed.
GrapheneOS still has builds up for 3a, however new builds were terminated as of February. While it doesn't ship with gCrap preinstalled, installation is trivial as they've built a compatibility layer to make it work correctly (and much MUCH more securely) as user-installed software, which you can install from the program "Apps".
LineageOS 20.0 is a free, community built, aftermarket firmware distribution of Android 13.0 (T), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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.
The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Known bugs:
Screen mirroring via slimport HDMI adapter doesn't work. (won’t fix)
PMF aka 802.11w doesn't supported. PMF SHOULD NOT be enforced in your wifi router! (can’t fix)
Encryption doesn’t work. FDE encryption was removed completely in Android 13! (can’t fix)
There may be a lot of other issues because these builds are experimental!
Downloads:
ROM: https://sourceforge.net/projects/hammerhead-lineageos/files/20.0/
GAPPS: https://bitgapps.github.io/latest.html
Credits:
Many thanks to the LineageOS and LineageOS-UL team and all the contributors out there in the community
Contributors:
z3DD3r
Source Code:
Device tree: https://github.com/z3DD3r/android_device_lge_hammerhead/tree/lineage-20.0
Kernel tree: https://github.com/z3DD3r/android_kernel_lge_hammerhead/tree/lineage-20.0
Vendor tree: https://github.com/z3DD3r/android_vendor_lge/tree/lineage-20.0
Android version: 13.0.0 (T)
Kernel version: Linux 3.4.113
SELinux: Enforcing
Status: Beta
Created 2022-11-24
Last Updated 2023-02-20
ROM Installation
To install rom you should increase the /system partition size
This can be done for example with TWRP HH.R
[RECOVERY][UNOFFICIAL] TWRP HH for Nexus 5 (hammerhead)
TWRP HH for Nexus 5 About: TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with...
forum.xda-developers.com
GAPPS Installation
LineageOS Team have recommendations about GAPPS
My recommendation is BiTGapps for Android 13.0.0 for arm devices.
Google apps should be installed via recovery immediately after installing LineageOS. If you reboot into LineageOS before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
ROM Build
To make your own build of LineageOS 20.0 please use my trees with manifests from LineageOS-UL github.
Currently HAL3 camera is broken in LineageOS-UL repos. You should use my forks of the android_frameworks_av and android_frameworks_base or use roomservice.xml attached to this post.
reserved
Comment with google nexus 5 lineage os 20 android 13..just camera and video suddenly stuck..but overall all perfect..smooth ui..this is the most fastest and smooth os i use on my nexus 5..tq so much for make my nexus 5 more powerfull
The only issue I have is that I cannot turn on Bluetooth. I wiped the phone and clean installed it with BiTGApps. Even in the setup wizard I got the Bluetooth keeps stopping message. Apart from this everything I tried seems to be working. I tried to wipe cache in TWRP, but that didn't fix it. Also wanted to clear cache in Apps but Clear storage and Clear cache is grayed out.
Edit: Here's a logcat. Is this some more SELinux policy issue? Because in the logcat I see this:
Code:
11-29 00:19:09.309 1586 1586 E SELinux : seapp_context_lookup: No match for app with uid 1002, seinfo default, name com.android.bluetooth
I'm just guessing blindly. That line caught my eye.
___________________________________________________
Edit 2: Did some more digging and found out this is because com.android.bluetooth is signed with a different certificate?
I found that for another device: https://github.com/phhusson/treble_experimentations/issues/58
Then I found this patch on LineageOS Gerrit: https://review.lineageos.org/c/LineageOS/android_packages_modules_Bluetooth/+/344542
That topic has two more patches: https://review.lineageos.org/q/topic:bluetooth-cert
Is this what we need? Does this build have these patches?
Thanks for developing latest roms for the Nexus 5! Really awesome of what people can do
@bluetooth-bug,
Yes these patches are included. It is very strange because we have tested bluetooth and it worked. Unfortunately i can't do anything with it without device
@bluetooth-bug and @z3DD3r same issue with bluetooh even i wiped the phone and clean installed it with BiTGApps.
Otherwise the rom is super smooth and usable.
Good work
@bluetooth-bug, @androcib,
Please try new build. Please test with clean flash and without gapps and magisk.
@z3DD3r I dirty flashed it from previous build and Bluetooth is working now. Something was definitely missing from the previous build and somehow com.android.bluetooth was still not signed with the proper certificate.
I knew something was wrong because I dirty flashed the previous build as well and Bluetooth was still borked. (lineage-20.0-20221124-UNOFFICIAL-hammerhead-experimental.zip)
Thank you for all the hard work! This ROM definitely has potential. I think I am going to keep it.
@z3DD3r thanks
bluetooh seems to be ok however camera does not work same for listening msique with app
androcib said:
@z3DD3r thanks
bluetooh seems to be ok however camera does not work same for listening msique with app
Click to expand...
Click to collapse
@bluetooth-bug,
Can you please also check this?
@z3DD3r @androcib
Of course I can check. And cannot confirm the issue, because camera works for me. And works as intended.
I opened the Camera app, took a picture, and I was able to view the picture as well. Next, I switched to video and recorded one. Then I was able to play it back.
@androcib keep in mind that if you play a video you shot for the first time then you will need to raise the volume. Every LineageOS is like that.
Sure the preview window is a bit tiny but that's just how the app is. So yeah. Push volume up and you will see that you will have sound if that's what you mean. This is not a bug.
z3DD3r said:
@bluetooth-bug,
Can you please also check this?
Click to expand...
Click to collapse
bluetooth work now , camera also and music too
a reinstallation, formatting and repair file system solves my camera and music issues
I was excited to see Android 13 for my Nexus 5, but is it really discontinued already...?
I'll be trying it anyway. The feedback above seems positive. Thanks for giving us more toys to play with.
This is really impressive and awesome that Android 13 works on the Nexus 5.
It would be great to have a stable-daily 13 android for our N5!
thanks @z3DD3r
https://sourceforge.net/projects/hammerhead-lineage/files/lineage-20.0/lineage-20.0-20221216-UNOFFICIAL-hammerhead.zip/download
Build with December security patch. Just in case someone needs it