[ROM] [7.1.x] [OMS] [EAS] ibrokemyLINEAGE [LOS] [20170807]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
no legal responsibility taken for anything.
use at own risk.
install with full knowledge that this //could// make your phone 100% unusable and out of warrantee.
INTRODUCTION
This is a personal LineageOS build, based upon 14.1. I pull in changes as I see them, and sometimes this breaks things. I will upload builds as I build them, as long as they pass brief personal testing (eg they boot)
Posting this as a seperate thread mainly because it may take a different direction to others, and is not meant to just be a LOS nightly, I will be pulling changes at my discretion, this ROM is being built by me, for me, and I just happen to be sharing it.
Feel free to contribute, recommendations and (new) bug reports are always very welcome.
Click to expand...
Click to collapse
SPECIAL FEATURES
At the moment this may seem a little bland, but the point is not to become a new big rom, but simply to be a LineageOS based rom with the latest little addons, which at the moment include:
@tabp0le Kernel built with rom (Source)
FULL Energy Aware Scheduler support
FULL ROOTLESS Substratum theme engine support with ThemeInterfacer and OMS7
Substratum app pre-included with app store updates
SU_ENABLED by default (builtin root manager from CyanogenMod)
FULLY compatible with both firmwares (MM and N)
Supports F2FS
SELinux ENFORCING
ForceEncrypt DISABLED
Click to expand...
Click to collapse
INSTRUCTIONS
Download the rom, check the hash and flash it and ARM64 7.1 GAPPS (Dynamic/Beansgapps recommended) through TWRP.
For updates, dirty flash of ROM only should do, if you have played around with system apps then perhaps clean the dalvik and cache, just to be safe.
Click to expand...
Click to collapse
BUGS
None known
Click to expand...
Click to collapse
DOWNLOADS
LATEST:
20170807
older versions:
20170502
20173003
20170903
20170131
20170131
20161218
20161215
20161215
Click to expand...
Click to collapse
CHANGELOG
Code:
Rebuild on latest sources
Update OMS
Update themeinterfacer
Fixed sdcard issues
Fixed USB OTG issues
Older changelogs:
Code:
Remove snap camera
Add google camera
UBERTC
Snapdragon LLVM
Update OMS commits
Add substratum as system app
Substratum verification
Rebase of sources upon tabp0le's eas
Fix SD issues
Add back software nav bar
EAS config changes
Improved hardware blobs
Updated power config
Updated hardware overlays
LOS upstream changes
Kernel upstream changes
WLAN wakelocks toggleable
Improved battery usage
Removed some redundant dev settings
Update some drivers/configs for camera and display
Adds Qualcomm Snap Camera
Add OMS7 rootless commits
Fix inclusion of Substratum app (604)
Replace masquerade with ThemeInterfacer (v50)
Compiled with UberTC and Snapdragon LLVM
Tabp0le kernel 1.03
Updated vendor files
Pre odex enabled (faster first boot)
GPS config updated
fix fingerprint sensor
update from upstream
include bluetooth aptx support
new vendor blobs
Rebrand to ibrokemyLINEAGE
Switch from Elite Kernel to Tabp0le Kernel
Better OMS7 integration
FINGERPRINT SENSOR works on both firmwares without need for patches
Substratum app now updates correctly from store
EAS support enabled by default, Kernel and Ramdisk support out of box.
Rebase on CAF sources
Latest patches/fixes
GPS fixes
WiFi stability improvements
WITH_SU set to true
Forceencrypt disabled again
Rebase on LineageOS 14.1
Update kernel
Refactor OMS changes
General cleanups
Latest source from upstream.
OMS7/Masquerade, the backend for the new SUBSTRATUM theme engine. Simply download the substratum app from the play store to use it!
FINALLY a working subwoofer (bottom speaker)
innumerable misc patches
other misc perf changes
Revert breaking audio commits. - https://github.com/ibrokemypie/android_device_htc_pme/commit/928c5e1674571fac980d2e730983c4c59c55f412
Build with Elite Kernel, thanks @buckmarble! - https://github.com/ibrokemypie/android_device_htc_pme/commit/6df6a1b650336bd9f97bed756dc397f1a2862d50
Click to expand...
Click to collapse
Thanks To/Credits
Code:
rc420head, Mahdi786, crpalmer, leedroid, buckmarble and tabp0le
XDA:DevDB Information
ibrokemyLINEAGE 14.1.x, ROM for the HTC 10
Contributors
ibrokemypie, rc420head, Mahdi786, crpalmer, leedroid, buckmarble, tabp0le
Source Code: https://github.com/ibrokemypie/android_device_htc_pme/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2016-12-15
Last Updated 2017-03-29
XDA:DevDB Information
ibrokemyLINEAGE 14.1.x, ROM for the HTC 10
Contributors
ibrokemypie, rc420head, Mahdi786, crpalmer, leedroid, buckmarble, tabp0le
Source Code: https://github.com/ibrokemypie/android_device_htc_pme/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Beta Version: ibrokemypie
Created 2016-12-15
Last Updated 2017-08-10
Reserved
I shall give this a try. Thanks @ibrokemypie!
Yup me too, I will also try it. I tested the RR Android N this morning with ZERO issues coming from BadBoys (Sprint HTC 10). I remained on the MM kernel so even TWRP worked with no issues. VERY excited and glad to see N is coming to the HTC 10!
Thanks for contributing! I wish I had the knowledge to contribute .
Moderator Warning,
Thread cleaned. Flaming users is not acceptable on XDA. If you have an issue with a post, report it and move on.
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
GROOVYJOSHCLARK said:
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
Click to expand...
Click to collapse
What about the speaker problem?
GROOVYJOSHCLARK said:
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
Click to expand...
Click to collapse
Did you flash the N firmware?
mcwups1 said:
Did you flash the N firmware?
Click to expand...
Click to collapse
Nope, stayed with MM, and I had speaker, no issues with sound, maybe I am lucky, IDK but TWRP worked, and everything I need from my daily driver except GPS.
Hello, the codename "pme" which version of HTC 10 corresponds?
All these.. perfume_uhl, perfume_whl and perfume_ul?! Thanks!
pickandrew said:
Hello, the codename "pme" which version of HTC 10 corresponds?
All these.. perfume_uhl, perfume_whl and perfume_ul?! Thanks!
Click to expand...
Click to collapse
those are the country codes are they not? pme is perfume in general
Stephen said:
Moderator Warning,
Thread cleaned. Flaming users is not acceptable on XDA. If you have an issue with a post, report it and move on.
Click to expand...
Click to collapse
Edit: only quoted you because the post I was replying to got erased.
Thanks for following rules. Sorry if I'm breaking them.
BUT
As far as I'm concerned flaming should be done if source is not public on github and someone hacked your private github account. But sharing is caring
And It benefits us all.
I didn't Flame when I asked in a thread if anybody was working on cm-14.1 and when I started work on it I didn't even write what the commit was that I added but somehow cm-14.1 still came and all the work I done was used. IT REALLY WASNT USED. as there is plenty of github sources to give ideas and plenty of code changes. We as developers need more developers as the code game is big. If someone is contributing to a worthy cause let them. Do any of you developers out there like having sleepless nights trying to figure out code? I don't think so. And me I don't know **** but I can figure it out hahahaha.
This post is just a general post so report me but let people learn dammit. And a guide doesn't teach you how to fix building errors so guides don't help. Going through code of familiar devices does.
twinnfamous said:
Edit: only quoted you because the post I was replying to got erased.
Thanks for following rules. Sorry if I'm breaking them.
BUT
As far as I'm concerned flaming should be done if source is not public on github and someone hacked your private github account. But sharing is caring
And It benefits us all.
I didn't Flame when I asked in a thread if anybody was working on cm-14.1 and when I started work on it I didn't even write what the commit was that I added but somehow cm-14.1 still came and all the work I done was used. IT REALLY WASNT USED. as there is plenty of github sources to give ideas and plenty of code changes. We as developers need more developers as the code game is big. If someone is contributing to a worthy cause let them. Do any of you developers out there like having sleepless nights trying to figure out code? I don't think so. And me I don't know **** but I can figure it out hahahaha.
This post is just a general post so report me but let people learn dammit. And a guide doesn't teach you how to fix building errors so guides don't help. Going through code of familiar devices does.
Click to expand...
Click to collapse
Hey, I didnt see your post from before, this whole thing, I really didn't mean to offend or steal, I just wanted to make the progress accessible to people who dont have the time or resources to build the code themselves, even if it is mostly just following a guide. Beside from that, the point of open source is for people to take something and make it do what they want, without restrictions, and to be able to give and take if they can. I am not simply taking the work of others and packaging it as my own, I am trying to make contributions, even if I am not a super great programmer like @crpalmer, who is putting together the pieces to make this work for us all. I am not taking the work of others and claiming ti was mine. That was not my intention at all and I am sorry it may have seemed as such.
GROOVYJOSHCLARK said:
Nope, stayed with MM, and I had speaker, no issues with sound, maybe I am lucky, IDK but TWRP worked, and everything I need from my daily driver except GPS.
Click to expand...
Click to collapse
Hey, about to start properly looking into GPS as I was able to repro the problem, however GPS satellites are being detected, and certain bits are working, so I feel fixing it should be within my capabilities, however for the moment I am working on including theming through Substratum, with full implementation with the inclusion of Masquerade backend (OMS) which should be build ready in a little while.
Hey @ibrokemypie,
Out of curiosity, are you duel booting Linux, using a VM Linux environment or just generally using Linux as your OS and building Cyanogenmod from there? Also how much space have you got allocated for building Cyanogenmod. I'm trying to figure out if I have the capability to do it on my MacBook Pro if I clear out some space.
Sent from my HTC 10 using XDA Labs
ibrokemypie said:
Hey, about to start properly looking into GPS as I was able to repro the problem, however GPS satellites are being detected, and certain bits are working, so I feel fixing it should be within my capabilities, however for the moment I am working on including theming through Substratum, with full implementation with the inclusion of Masquerade backend (OMS) which should be build ready in a little while.
Click to expand...
Click to collapse
That's awesome, I really appreciate it! This is the only thing keeping me from fully committing to this as my daily runner. I use GPS pretty much every day so I need it. I've always ran with AOSP on all of my androids and this is usually an issue across the board in the initial releases so I get it and appreciate your hard work!
sent from my HTC 10
rav101 said:
Hey @ibrokemypie,
Out of curiosity, are you duel booting Linux, using a VM Linux environment or just generally using Linux as your OS and building Cyanogenmod from there? Also how much space have you got allocated for building Cyanogenmod. I'm trying to figure out if I have the capability to do it on my MacBook Pro if I clear out some space.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Well, initially I tried just building on my macbook, but ran out of space verrrry quickly. Do not recommend even trying unless you have a MINIMUM of 150gb that you can dedicate it, wasted a whole two days with this.
Tried building on a ****ty laptop too, but discovered that you really can't build at all unless you also have at the very least 8gb of ram, so ended up taking the drive out of that and sticking it in my gaming rig with 16gb ram.
Building on an arch linux install, mostly just via ssh with a tmux session to reduce overhead.
GROOVYJOSHCLARK said:
That's awesome, I really appreciate it! This is the only thing keeping me from fully committing to this as my daily runner. I use GPS pretty much every day so I need it. I've always ran with AOSP on all of my androids and this is usually an issue across the board in the initial releases so I get it and appreciate your hard work!
sent from my HTC 10
Click to expand...
Click to collapse
hey, just as a test, could you try setting your location to device only, open up google maps and tap the little icon to go to your location? I think it will ask you to allow it access to enable wifi/cell location, so deny that and tap it again, and you should see your location as a grey dot. If this works, can you then tap it once more, and take your device somewhere? There is a chance gps is wokring after all, just not reporting itself as suck to anything...
ibrokemypie said:
Well, initially I tried just building on my macbook, but ran out of space verrrry quickly. Do not recommend even trying unless you have a MINIMUM of 150gb that you can dedicate it, wasted a whole two days with this.
Tried building on a ****ty laptop too, but discovered that you really can't build at all unless you also have at the very least 8gb of ram, so ended up taking the drive out of that and sticking it in my gaming rig with 16gb ram.
Building on an arch linux install, mostly just via ssh with a tmux session to reduce overhead.
Click to expand...
Click to collapse
Yeah I think it's gonna be a no go for me then as my MacBook Pro only has 256gb in total and im currently using 60gb for Windows 10.
If I were to get a build PC together, what components are most required for building Android? After having at least 8gb of ram, is it all processor or a mix of processor and gpu?
Trying to think if I can make an Intel NUC type PC with the built in graphics card or if I need to be getting discrete graphics card as well.
Sent from my HTC 10 using XDA Labs
Related
I BUILD ABANDON A TWRP!
THIS PROJECT IS ABANDONED (2015-12-06)
Blastagator's 2.8.7.3 release fixes the problem that started my quest: the sepolicy squashing that damaged the gapps permissions on CM-12 OS updates. Given that I had many more issues that came from my choice of CM-12.1 as a base (instead of whatever TWRP wanted) and that I lacked the time, inclination or expertise to pursue the issues, I have chosen to abandon this project. If it worked for you and you didn't need the extra features that were buggy, then by all means enjoy. However this project is no longer supported.
What is it?
It's TWRP! It's for a number of the G2's! Which ones? The ones supported by whatever the current CyanogenMod is. GSM: D800/1/2/3, CDMA: LS980, VS980. This is because, despite the TWRP documentation, I use CyanogenMod as a base, and if CyanogenMod doesn't currently support the given model, then I won't be supporting it with my TWRP. This TWRP is built with hints from (and thanks for) @blastagator's TWRP.
README.FIRST / DISCLAIMER
THERE BE DRAGONS HERE!!! USE THIS AT YOUR OWN RISK!!!
This is your one AND ONLY warning. I am not responsible for whatever happens to your phone. This software has the feature set to let you backup all of your partitions, but it also has the power TO BOTCH each and every partition on your device. This includes your EFS and other sensitive things. It is entirely possible that you may end up bricking your device. I really hope that doesn't happen, but I am also not responsible if it does. Please, behave responsibly and know that if you've taken the time to get this installed, well... your warranty is void.
Features
Flashes Gapps properly so that it doesn't crash on reboot
Thermal Support
Material Theme
{
"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"
}
Known Issues / Red Flags
I've only really tested on the D800 because that's what I have access to. However I've reports that it works fine on the other variants.
Reports that it doesn't work with blastagator's hybrid LP bootstack. (User says reboots into bootloader)
F2FS Support currently a bit borked. (User's say formatting doesn't work and causes ROM to bootloop, or is very slow and doesn't work.)
Users using AROMA will have issues installing things. Something about the installation process causes the recovery to reboot.
Cherry Picks / Links
Device Repo: https://github.com/dr4stic/twrp_device_lge_g2-common
CyanogenMod / 89474: Make recovery permissive (manually applied) - (20151003 - current)
TWRP / 12728: [WIP] gui: stock theme rework - (20151015 - current)
CyanogenMod / 110402: f2fs: Import latest F2FS + AIO Optimization - (upcoming)
TWRP / 14355: Fix broken fsflags support (upcoming)
TWRP / 14462: Support resuming block based OTAs (upcoming)
Releases / Changelog:
2.8.7.0 - 20151015
Added directives to tell twrp where our media REALLY is (blastagator suggested bad things happen if I don't)
Cherry picked a more material like theme because Rashed97 whined about ugliness
D800: twrp-2.8.7.0-20151015-d800.zip - 11.6 MB (MD5 Sum: 7e46ea96fed69a5cde9da73e26d6742e)
D801: twrp-2.8.7.0-20151015-d801.zip - 11.4 MB (MD5 Sum: 7a71cda865b0f32c1403938eb76eeb5e)
D802: twrp-2.8.7.0-20151015-d802.zip - 11.4 MB (MD5 Sum: 52143681915a53b910040fb6501dd324)
D803: twrp-2.8.7.0-20151015-d803.zip - 11.4 MB (MD5 Sum: e8ee2f05ca06be1924a45e49da29e439)
LS980: twrp-2.8.7.0-20151015-ls980.zip - 11.4 MB (MD5 Sum: f76642bd7f5bb2b0eb8bb2a20e4adfed)
VS980: twrp-2.8.7.0-20151015-vs980.zip - 11.4 MB (MD5 Sum: bdfdb1e2132ab08a8f7e42c06e3699a4)
2.8.7.0 - 20151003
Initial release
Download 2.8.7.0 - 20151003: D800 | D801 | D802 | D803 | LS980 | VS980
Thanks To:
The TWRP Development Team
@blastagator
@Rashed97
dr4stic said:
Hello folks,
I BUILD A TWRP!
Click to expand...
Click to collapse
When I see how many projects are done for the G2, I really think I should give a try... Anyway, !gg mate, I'll try this recovery .
What did you change? Or did you just build my repos and post a new thread?
blastagator said:
What did you change? Or did you just build my repos and post a new thread?
Click to expand...
Click to collapse
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
The build started as the end of my trying to figure out what the problem was with CM and Gapps that required it to be re-flashed each time a rom update was flashed. I experimented with running commands by hand, dissecting upgrade scripts, found that contexts were either not being set or being lost, etc... etc... And at some point the only answer I could come up with was that it was the recovery. I tried the CM recovery, which is worse than the black death, and it worked fine. Since your TWRP is the latest, I didn't understand why it wasn't keeping contexts. At that point I decided to build my own TWRP, so I started from the only official docs I could find. That's what my base started as.... the cm-10.1 repos they have on their github for g2.
After realizing that simply wasn't going to work, I started re-working and basing off of CM. I didn't necessarily want to look at your work because in my mind yours was done right and based on latest CM. I eventually looked at it for some hints (hence my attribution). It wasn't until I realized your device repos looked odd to me that I realized what happened. Your device repos were based from back when the G2 stuff was barely starting out on CM-12.1... it was still very 12.0 (which, in itself was a ball of vomit for the g2). It lacked the selinux stuff (which is why it was losing contexts) and you also used an alternate kernel (unsurprisingly, cuz the CM stuff was still in a state of vomit). There are no judgements. At the time you built the recovery, it's what was available and working. I don't think the G2 got selinux turned up until some time in very early August.
So, I decided to fork copies of the latest CM device repos which all work now, base everything off the current CM kernel (I figured this was safest for compatibility). I actually looked through the TWRP sources to hunt for actual BoardCommonConfig.mk settings (the docs seemed VERY lacking) and an understanding of how they all interacted. I looked at your repo for hints, but I didn't just copy it. As a result I use more current settings (a few of yours are actually deprecated). I'm assuming because of the age of your repo that your builds were lokified and you bumped them after the fact. Mine have all the changes that came with 12.1 including a lack of loki and being bumped as part of the build process. The rc files are all stock CM. Many things simply don't exist from your version because the recovery environment seems REALLY restricted once it's built. The few things that I did borrow, I moved into more appropriate locations and file names to be more respectful of the build process.
So, to answer your question: it started as a rather long and annoying bug hunt, then turned into a long but fruitful learning experience, and once I had a version that worked, I posted it for the few folks on the CM forum for whom this is a real pain in the ass.
It certainly wasn't a quick process and a grab for glory.... hell, once I realized that the CM build process needed to build a full ROM to get all the appropriate files into the recovery image, each one of those device builds took over an hour to build.
I started a new thread because I wanted to have a specific place where I could respond to issues if they arose, or at least tell people that I didn't care about their piddly little problems. I wanted a little more control over the support process, to be able to modify the OP with pertinent issues and links as they came up. It's something I wish had happened with CM-12.1 "official" threads.
There are things that I'm not sure of, and I try to indicate as much in the OP. The thread regulars indicated the history of needing thermal support, but I'm not sure if I got it right. Neither your recovery nor mine actually got the thermal libraries or binary included in the file system, however the process seems to be running. Nor are the configuration files included on the file system. f2fs support seems to simply be an additional package, and since the official G2 repos theoretically have f2fs support, I added that and moved along. The tools seem to be included on the file system.
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.
@dr4stic
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
Lawlrus said:
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
Click to expand...
Click to collapse
@Lawlrus, thank you for the explanation! After I investigated I assumed that's what was going on, but I didn't want to assume and then tell people something I wasn't sure about. I noticed that mine gets a slight toastier than blastagator's, but not a significant difference. I attributed it more to kernel tuning with the finalized CM kernel than anything else.
dr4stic said:
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.
Click to expand...
Click to collapse
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
My builds are built with the Omni 4.4 Source, and these changes:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-11.0/blastagator_g2-common.xml
The device trees are actually based on cm-11, not 12.
As for SELinux, issues probably stem from this: https://github.com/blastagator/aicp...mmit/85953d0cf8dd3d33406ad8a745ced99e5039f766. When I committed it I thought it set SELinux to permissive. However, it actually completely disables SELinux, so the kernel won't automatically preserve contexts, etc. This seems like the most likely culprit for your issue. I will run a test build and revert that commit, if you'd like it to test.
As to cm-12, in general: I'm certainly interested in moving up, I just never really had a reason to spend any time on it.
blastagator said:
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
Click to expand...
Click to collapse
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
dr4stic said:
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight
Click to expand...
Click to collapse
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
sandys1 said:
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
Click to expand...
Click to collapse
Thanks for your suggestion. I'm already talking to blastagator. The problem is that his current build isn't actually based on CM-12, we are working from different sources.
jacoghi said:
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
Click to expand...
Click to collapse
I have a few d800's, it's the device I use. Which bootloader are you on? JB? KK? LP?
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
jacoghi said:
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
Click to expand...
Click to collapse
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.
dr4stic said:
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.
Click to expand...
Click to collapse
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
jacoghi said:
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
Click to expand...
Click to collapse
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
dr4stic said:
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
Click to expand...
Click to collapse
I'm using cloudy 3.3 right now with xceeds kernel. After I got the fastboot mode, I could boot my system normally, if that helps. Rebooted again, got fastboot once more. Then booted system up again and installed autorec, which corrected the problem.
Well, messed around with this for a bit, decided to format /data to f2fs.
Dont do that. Not on this recovery. Formatting to f2fs takes forever (probably hangs entirely as i waited at least 10 minutes before rebooting)
Then noticed my /data wouldnt mount on reboot, causing my rom to bootloop and, even worse, the recovery to bootloop.
Due to a (probably unrelated) bug the lg flash tool didnt work either, so had to open up the device to boot in qhsusb mode and manually format /data to ext4.
This is the closest I've been to a complete brick on this phone since I got it.
Please update the OP to warn people about f2fs.
Nice work on the kernel update, but I personally am going to avoid this recovery until the above issue is solved
My problem is that it would not reboot nor power off while in this recovery. But it works by pressing power button.
It is ok now by removing the theme file ui.zip.
Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* 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. :P
* blah blah blah you get the point.
*/
This is a simple unofficial CyanogenMod 13 build with a few small tweaks and my custom kernel.
Builds are made with that day's nightly source code, with my roomservice. I try to keep my repos up to date.
How to install this:
Download this build (and MD5, if you want to verify integrity)
Download Gapps (Optional, I use OpenGAPPS Nano)
Download SuperSU (Optional, I use SuperSU Beta 2.74)
Reboot into Recovery
Wipe /cache, /data, and /system (Should only be needed on initial flash, upgrading should be seamless)
Flash ROM Zip
Flash Gapps Zip (Optional)
Flash SuperSU Zip (Optional)
Reboot & Enjoy!
How to build this (if you don't trust my builds, or want to DIY):
Sync CM13
Add my local manifest: https://github.com/javelinanddart/roomservice/blob/cm-13.0/roomservice.xml
Sync
Go to kernel/samsung/ (you may have to mkdir samsung folder, if it doesn't exist)
Clone my kernel manually into a folder called jf
git clone https://github.com/javelinanddart/android_kernel_samsung_jf -b cm-13.0 jf
Build
Make sure you manually git pull the kernel when you run a new build.
Bug Reporting:
Please read http://forum.xda-developers.com/showthread.php?t=1520508 & http://forum.xda-developers.com/wiki/Reporting_A_Problem_-_Android
before reporting any bugs. It is incredibly frustrating and useless to receive bug reports like "bt broke plz fix thx in advance....." without any other information. I would more than like to help fix your bug for you, but I cannot help without proper information.
Credits (off the top of my head):
CyanogenMod Team
@arter97
@show-p1984
and many more I can't think of off the top of my head....
Source Code:
Kernel: https://github.com/javelinanddart/android_kernel_samsung_jf
Local Manifest: https://github.com/javelinanddart/roomservice/blob/cm-13.0/roomservice.xml (for the rest of my repos)
OP Post List:
#1: Introduction
#2: Changelog
#3: Feature List
#4: Downloads
#5: Feature Explanations
#6: Known Bugs
#7: Reserved for future use
XDA:DevDB Information
Unofficial CyanogenMod 13 with Cake Kernel, ROM for the T-Mobile Samsung Galaxy S 4
Contributors
javelinanddart, CyanogenMod Team
Source Code: https://github.com/javelinanddart/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: NK2
Based On: CyanogenMod
Version Information
Status: Stable
Created 2016-06-02
Last Updated 2016-06-02
Changelog:
Aug 1, 2016
Sync with CM
Initial Rerelease
Cleaned Everything Up
Enable LiveDisplay by Default
June 7, 2016
Sync with CM
Fix 1080p Video Playback
Potentially fixed micro lag while scrolling
June 1, 2016
Initial Release
ROM Feature List:
Built with -O3 Optimization (GCC & Clang)
Built with UBERTC GCC 5.3 Toolchain
Built with Java 8
Some apk Optimizations (from @arter97)
Kernel Feature List:
Built with -O3 Optimization
Built with UBERTC GCC 5.3 Toolchain
Fsync Toggle
MSM_MPDEC
Bricked Thermal
CPU Toggle
IO Scheduler Optimizations
/dev/frandom Support
Gentle Fair Sleepers & Arch Power Toggle
MMC CRC Toggle
Dynamic Readahead
Lowered Swappiness
Aggressive Multi Core Power Saving
Simple GPU Governor
CPU Voltage Control
GPU Voltage Control
Fast Charge
Badass Governor
FIOPS I/O Scheduler
Sound Control
Backlight Dimmer
Disabled Input Boost
Added patch to fix Entropy Depletion
Potential Benefits of These Features:
Better Battery Life
Downloads:
NOTE: You will need to turn off ad block in order to download these builds. The wonderful Codefire team has provided me with access to this build server for free (thanks specifically to @thecubed) and in order to try to make it break even, they rely on ad revenue. @thecubed takes a loss on this server every month, so please help this guy to keep providing this wonderful service to developers for free. Thanks for understanding!
MIRRORS ARE NOT ALLOWED!!! (Mods: Please help me enforce this)
BUILDS PULLED
KNOWN BUGS:
Upstream CM Bugs
Micro Lag when Scrolling (Possibly)
You tell me....
Reserved 6
Reserved 7
javelinanddart said:
KNOWN BUGS:
Upstream CM Bugs
Micro Lag when Scrolling (Working on it)
You tell me....
Click to expand...
Click to collapse
Do you mind my asking if you are using this rom now or are you just working on it?
I would like to update to a 6.0 rom but don't really want to give up much functionality. I am using 5.1.1 and I do like it but would like the security updates of the newer rom while I decide which new device if any to purchase. Thanks
darazor said:
Do you mind my asking if you are using this rom now or are you just working on it?
I would like to update to a 6.0 rom but don't really want to give up much functionality. I am using 5.1.1 and I do like it but would like the security updates of the newer rom while I decide which new device if any to purchase. Thanks
Click to expand...
Click to collapse
I am both using it and working on it. As far as I know, all device features are fully functional (camera, GPS, IR, etc). Nothing I've tried has been broken, except the occasional google play services crash, which is Google's fault. As far as ROM features go, I haven't done much of a comparison with any LP ROMs.
To clarify, what I meant by working on it, I meant I was trying to fix that bug.
javelinanddart said:
I am both using it and working on it. As far as I know, all device features are fully functional (camera, GPS, IR, etc). Nothing I've tried has been broken, except the occasional google play services crash, which is Google's fault. As far as ROM features go, I haven't done much of a comparison with any LP ROMs.
To clarify, what I meant by working on it, I meant I was trying to fix that bug.
Click to expand...
Click to collapse
Thanks for the quick response. I am still on the MDL boot loader with OK3 base band is that a deal breaker?
Also is this compatible with xposed. I've read that they don't work well together. At this stage I could live without it but just for clarification and planning purposes. I like to have a path in my mind as I update.
darazor said:
Thanks for the quick response. I am still on the MDL boot loader with OK3 base band is that a deal breaker?
Also is this compatible with xposed. I've read that they don't work well together. At this stage I could live without it but just for clarification and planning purposes. I like to have a path in my mind as I update.
Click to expand...
Click to collapse
I've no idea with either, unfortunately. I've only ever had this phone with NK2 baseband, and I've never used Xposed, I've never had a use for it. Sorry.
javelinanddart said:
I've no idea with either, unfortunately. I've only ever had this phone with NK2 baseband, and I've never used Xposed, I've never had a use for it. Sorry.
Click to expand...
Click to collapse
I've spent the last several hours installing etc. This rom is GREAT! While I will have to test more, at this stage everything I've installed works perfectly and the bootloader/baseband doesn't seem to be an issue. Even AdAway has been perfect so far. I will expore the Xposed option later but if it isn't viable I can live very well with the current setup. I will report more unless someone else covers the topic. If anyone is hesitant to try this rom, don't be. Out of the box it is much more than I could have hoped for.
Disable adblock ?
Nope
Grudger said:
Disable adblock ?
Nope
Click to expand...
Click to collapse
1. Just to download the ROM
2. If you're not willing to help support the people who do this FOR FREE by turning off adblock for a few minutes, or even just on the download site, then realize that it's people like you who are going to cause free services to go extinct.
javelinanddart said:
1. Just to download the ROM
2. If you're not willing to help support the people who do this FOR FREE by turning off adblock for a few minutes, or even just on the download site, then realize that it's people like you who are going to cause free services to go extinct.
Click to expand...
Click to collapse
I just prefer donations and the thanks button
As soon as I try out the ROM though.
Grudger said:
I just prefer donations and the thanks button
As soon as I try out the ROM though.
Click to expand...
Click to collapse
I don't really care about donations, but the ad supported download page helps the owner of the build server I use, he gives it to me for free. I could not provide these builds if he wasn't so gracious as to let me use his build server for free. He consistently pulls losses from it, which makes it difficult to justify after a while. If you want to donate to someone (you'll still need to turn off adblocker on the download page, because he can't disable ads just for you unfortunetely), donate to @thecubed, it's his server.
javelinanddart said:
I don't really care about donations, but the ad supported download page helps the owner of the build server I use, he gives it to me for free. I could not provide these builds if he wasn't so gracious as to let me use his build server for free. He consistently pulls losses from it, which makes it difficult to justify after a while. If you want to donate to someone (you'll still need to turn off adblocker on the download page, because he can't disable ads just for you unfortunetely), donate to @thecubed, it's his server.
Click to expand...
Click to collapse
As I said before like this rom very much. Only issue so far is the standard CM bluetooth problem "Unfortuneatly bluetooth share has stopped". Are or have you been able to connect with BT?
darazor said:
As I said before like this rom very much. Only issue so far is the standard CM bluetooth problem "Unfortuneatly bluetooth share has stopped". Are or have you been able to connect with BT?
Click to expand...
Click to collapse
I unfortunately have not tested BT, and I don't really have any devices to test, except maybe connecting to my other phones. I will be out all of today, however I noticed a very annoying video playback bug that I will try to fix today.
New build is UP!
Changelog:
-Synced with CM
-Fix 1080p Video Playback
-Possibly fixed scrolling lag
Many thanks for your work on this ROM for our phones! :good::good:
Fingers xx'd that someday soon BT problems will be past us.
{
"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?
{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! These builds are experimental and can contain Bugs (as listed above). Make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Special thanks to @derf elot and @modpunk for most of the work on the yoshino platform.
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia XZ Premium
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2019-08-24
Last Updated 2019-08-28
Downloading,I will feedback
Sorry for my bad english
But I found some problems:
1. NFC is not working, I cant open NFC
2.Fingerprint sensor is insensitive,
when I try to create my fingerprint,the system says "It has stains on sensor." but I have cleaned already
Sorry it seems that is my problem , please ignore it.
3.Style Cover Stand SCSG10 is working inappropriate (same problem on early oreo builds)
when i covered up, xzp couldn't sleep
4.Mobile data cant work
others seems work perfectly
My firmware is 47.2.A.10.107
---
Edit:
I changed firmware to 47.1.A.16.20, NFC can work now
SCSG10 still works inappropriately, and Mobile data doesn't work. (only calls / sms)
But now the system says "your vendor doesn't match to your system".
1,NFC is dead
2,G8142 card 2 can't be recognized
3,Network not available
（basic on .107）
other things working Great！！！
how about make Camera Switch available？
I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Edit: found the cause for the mobile data, must've removed that by accident during a cleanup. A working build will be released later today
EDIT2: Build is running right now and will appear on the download page once done.
Can anyone confirm camera2api and gcam hdr+ support?
Thanks for fixing Mobile data and now it works.
NFC is also working, but need reboot after gapps setup wizard or first boot, I dont know if this is a problem.
(Just clean flash 47.2.A.10.107, I dont know why i cant open nfc in my first try. I clean flashed before...)
Incrovantilist said:
Can anyone confirm camera2api and gcam hdr+ support?
Click to expand...
Click to collapse
No, this rom blobs are based stock, so no level3 support.
Just flashed the rom and its smooth and awesome. So far everything working except dt2w.
For some reason with Magisk 19.3, ctsProfile is returning false. It didnt fail in any of the other SODPs or the latest stock rom. Anyone facing same issue?
Myself5 said:
I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
Click to expand...
Click to collapse
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Myself5 said:
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Click to expand...
Click to collapse
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.
LSS4181 said:
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Click to expand...
Click to collapse
Given it works on both my phones that were on .107 before and that the blobs are from .107, this could be the cause. If you flash the latest stock ROM make sure to fully boot into it at least once because the stock ROM sometimes also upgrades the NFC Firmware on the chip itself.
P.S. The kernel is the same as cryptomilks.
LSS4181 said:
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.
Click to expand...
Click to collapse
Oh cmon man you literally quoted a message of me saying that I don't have the Dual SIM variant nor any testers for it (yet). I have quite a few ideas on how I could fix it, but without any testers I'm just not gonna touch it at all.
I have G8142 and I can say, "Yes, SD card still works on G8142."
But I dont have 2nd sim card so i cant test if dualsim works
.107 clean installation, there were also problems with NFC, after rebooting it was fixed.
The Smart Cover function does not work, the screen continues to light after closing the cover, or the action of the magnetic cover (by the Hall sensor), I do not know how it should, but it does not work ..
So far stable enough to be daily driver except issues with magisk. Magisk keeps getting uninstalled on its own and have to be reinstalled in twrp every now and then. And after it gets installed, the rom stutters and doesn't open any apps or the settings and have to be restarted a few times for it to go back to normal.
Also a feature to modify charging led settings would be awesome. (I tried to find and modify it in root but couldn't find the charging led settings in /sys/class/leds)
Camera is frickin awesome. It's sooo much better than stock even without lvl3 camera2api. For anyone trying to find a decent camera app, try using opencamera with camera2api enabled in settings. Except for hdr(doesn't work, will force close), it's able to take really good images. If only somehow able to shoot 960fps slomo .
Magisk 19.3 - there were no problems with self-removal, there is a delay when starting up applications with a white screen after a reboot, it holds the battery well 2% per night.
I spent some time working with @haiha2001 on the XZ1 Dual today. Along the road we came across a few things but it's not working yet. HOWEVER, the XZ1 seems to have a different/more advanced issue than the XZ Premium. Whereas the XZ Premium has SIM1 working, the XZ1 doesn't have any SIM working at all.
That brings me to the following:
There was a fairly obvious flaw (thank Sony for that for not having unity of system property locations across Single/Dual SIM) which could explain why only one SIM is working on the XZ Premium. I've fixed it in the linked boot.img. If someone with two SIM Cards and the Dual SIM variant could try and let me know how it's doing on maple_dsds I'd be very happy.
https://dl.myself5.de/maple/.fwafwafwafo/boot.img
flash it via fastboot with
Code:
fastboot flash boot boot.img
on top of the latest weekly.
Just flashed your boot.IMG
I'll put in the wife's sim and see
Myself5 said:
I spent some time working with @haiha2001 on the XZ1 Dual today.
Click to expand...
Click to collapse
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
Because I see the XZ1 seems to be less supported by programmers for this device while the XZ Premium has quite a lot, while I know that the XZ Premium is not too different from the off-screen XZ1, so I'm willing to support the programmers to check the rom or mod version for XZ1, if they have an idea I will help my best ?
Sent from my Sony G8342 using XDA Labs
beammer335d said:
Just flashed your boot.IMG
I'll put in the wife's sim and see
Click to expand...
Click to collapse
Did she voluntarily gave it to you yet or do we need to send armed troops to make her ? First screenshot looks promising already.
also, in case you're rooted, please get me the output of the following:
Code:
adb shell
then enter
Code:
su
(Accept Magisk request on the phone)
and then run
Code:
cat /cache/modem/modem_switcher_status
cat /cache/modem/modem_switcher_report
And send me the output.
Alternatively you can run it via terminal emulator starting at the "su" part.
Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
+1
Who are we?YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Downloads
Downloads
cheeseburger (OP5) : https://drive.google.com/file/d/11S4K-_SGOJLyHFd9hX_P_Uj_2Ai4wzQL/view?usp=sharing | https://yaap.angerycat.tk/YAAP-11-Alpha-yaap_cheeseburger-20201025.zip
dumpling (OP5t) : https://drive.google.com/file/d/1B4JIzRcl3iLmq7imzYvhrNQ3ESjfRe8U/view?usp=sharing| https://yaap.angerycat.tk/YAAP-11-Alpha-yaap_dumpling-20201025.zip
Flashing ProcedureInstall TWRP (Latest codeworkx is recommended)
Coming from a different rom / OS you'll need to clean flash:
1. Wipe data (Factory reset)
(1.1.) If coming from stock OS you may need to format internal storage
2. Flash rom
(2.1.) Flash mods (magisk, no veirty if on ext4 decrypted.)
3. Rejoice
For dirty flash just skip step 1, 1.1
and possibly 2.1 if your mods support addon.d (ex: Magisk)
It does not matter when you flash the firmware zip, and you only need to flash it once per firmware version
XDA:DevDB Information
Yet another AOSP project, ROM for the OnePlus 5
Contributors
poad42
Source Code: https://github.com/yaap
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS stable 10.0
Based On: AOSP
Version Information
Status: Alpha
Created 2020-09-15
Last Updated 2020-09-15
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Alert slider, Panel modes, HBM stuff
Permissive kernel
SafetyNet
Broken:
Encryption
Note: The ROM includes gapps with some pixel additions .
Feel like buying me some coffee for my efforts?
Donation link: https://paypal.me/generichandle
Join our chat : https://t.me/yaapop5 or https://t.me/yaapcommon
Screenshots
Congrats and Thanks for the Wonderful Support. Downloading the same...
woah! thank you so much for you work. I'm excited!
Great job Devs thank you
awesome, this is not a alpha, this is a beta :good: (my first post)
>barebones AOSP
>includes Gapps
Ok
d1n0x said:
>barebones AOSP
>includes Gapps
Ok
Click to expand...
Click to collapse
Barebones AOSP in regards to the UI because the dev's previous NitrogenOS had a bunch of customisations. I don't think that's very hard to understand. The objective is to be as barebones as possible, Gapps have nothing to do with being barebones or not.
Hello! Thank you in advance for doing this great project. It is possible to make a ROM Similar to Oxygen OS 11? I really liked this new Oxygen aesthetic. Thank you again for doing this for us.
Spider-Vice said:
Barebones AOSP in regards to the UI because the dev's previous NitrogenOS had a bunch of customisations. I don't think that's very hard to understand. The objective is to be as barebones as possible, Gapps have nothing to do with being barebones or not.
Click to expand...
Click to collapse
Yes it does. It isn't as barebones as possible in its current state because GApps is unnecessary for Android to run. It also increases the file size of the rom. False advertisation.
Besides, I've never, ever seen an initial AOSP rom for a new Android version that includes GApps on XDA. Heck, I've never seen a "barebones" AOSP rom that includes GApps. I think that's quite telling.
poad42 said:
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Broken:
Alert slider, Panel modes, HBM stuff (all need source side changes)
Permissive kernel
SafetyNet
Note: The ROM includes gapps with some pixel additions .
Click to expand...
Click to collapse
So what can be done for broken (how can we do side changes .. Permissive kernel any link for that
Tq exited for ur reply
SirSoviet said:
Yes it does. It isn't as barebones as possible in its current state because GApps is unnecessary for Android to run. It also increases the file size of the rom. False advertisation.
Besides, I've never, ever seen an initial AOSP rom for a new Android version that includes GApps on XDA. Heck, I've never seen a "barebones" AOSP rom that includes GApps. I think that's quite telling.
Click to expand...
Click to collapse
Well, actually a lot of 'AOSP' roms are just 'LineageOS based but with the AOSP interface'. Even in this case some repos are based on the LineageOS repos:
https://github.com/yaap/device_oneplus_cheeseburger/commit/62baf1aa2596ecc100b36890f2245ba832ff3cfc
robertogl said:
Well, actually a lot of 'AOSP' roms are just 'LineageOS based but with the AOSP interface'. Even in this case some repos are based on the LineageOS repos:
https://github.com/yaap/device_oneplus_cheeseburger/commit/62baf1aa2596ecc100b36890f2245ba832ff3cfc
Click to expand...
Click to collapse
The device tree was created by los yes, but has been extensively reworked both in Q and R, the cheeseburger tree is just a bunch of makefiles. The common tree is the one that has most of the stuff. So its not los based with an aosp interface or anything like that lol. Its just its own thing.
Thank you for freely sharing your great work. It is much appreciated! :highfive:
poad42 said:
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Broken:
Alert slider, Panel modes, HBM stuff (all need source side changes)
Permissive kernel
SafetyNet
Note: The ROM includes gapps with some pixel additions .
Click to expand...
Click to collapse
It's purely already amazing bro, thx
Will redo a donation soon, keep my NOS Nand Backup for trying this A11
poad42 said:
The device tree was created by los yes, but has been extensively reworked both in Q and R, the cheeseburger tree is just a bunch of makefiles. The common tree is the one that has most of the stuff. So its not los based with an aosp interface or anything like that lol. Its just its own thing.
Click to expand...
Click to collapse
1st thing first: Congrats for working so frequently to bring up Android 11 for oneplus 5 & 5t. Brother I've suggestion not to react for users who don't understand the efforts of dev's hard work, I know how much time it takes and from where that time we manage? We cut down that time from our family, our rest and by changing our sleeping pattern. It's not our business, We're doing this just for hobby not for money. But instead of appreciation getting questions. I haven't seen if anyone has asked politely that " Sir please correct barebones word because you've included GApps". Brother again I'll say don't answer to users who always seeking your writing mistakes but not measuring your efforts and hard work.
[Thread Cleaned]
As outlined in our Forum Rules:
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
Click to expand...
Click to collapse
Please respect the wishes and decisions of the developer. You may provide constructive criticism but spewing disbelief for a feature or module that is or isn't present does not comply with the above rule.
Keep in mind there are plenty of alternatives to choose from and realize how lucky you are with a device that gets so much development love.
If you are wondering why your post was removed or edited, please feel free to drop me a PM.
Have a great day and keep it safe!
Thanks for your work mate! Great to have R for OP5. I planned to change my phone, but if I can have R as daily driver, I may wait a bit more
Do you plan to stay "barbone" or will you gradually port nitrogen's features to R?