{
"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"
}
What is OmniROM?
OmniROM Gerrit Review
OmniROM JIRA Bug Tracker
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
ROM DOWNLOAD:
GAPPS: Use whatever you would like [/SIZE]
INSTRUCTIONS:
Best off to be on an Android 8.0 rom, whether another rom or stock
Do a full wipe in TWRP
Install Rom
Flash newest TWRP again (failure to do so will result in losing TWRP)
Reboot recovery
Flash GAPPS
For now you don't need to install the vendor.img as its built into the rom, this will change though
build in vendor.img is found here https://github.com/Hardslog/proprietary_vendor_google_devices
Omni only supports TWRP recovery, use any alternate recovery at your own risk.
PLEASE SUBMIT BUG REPORTS AND FEATURE REQUESTS TO JIRA
Sources:
Device: http://github.com/Hardslog/android_device_gogle_marlin
Kernel: http://github.com/Hardslog/android_kernel_google_marlin
XDA:DevDB Information
Omnirom for Google Pixel Sailfish, ROM for the Google Pixel
Contributors
hardslog
Source Code: http://github.com/omnirom
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Current Beta Version: 11-20-2017
Beta Release Date: 2017-11-20
Created 2017-11-30
Last Updated 2017-11-29
Btw I don't root or install custom kernels so I have no idea if they work or not. My gut feeling is no but have no time to test these things.
First..!!
Any features list?
installing now!
edit: succesfully installed and is working well.
good to see the development is still going on!
shagbag913 said:
installing now!
edit: succesfully installed and is working well.
Click to expand...
Click to collapse
Are you rooted? If so, Magisk or SuperSU?
Just curious because I tried with Magisk 14.5 and couldnt get past the Google boot screen and it was looping
uodii said:
Are you rooted? If so, Magisk or SuperSU?
Just curious because I tried with Magisk 14.5 and couldnt get past the Google boot screen and it was looping
Click to expand...
Click to collapse
I'm not rooted right now. I might try later though
Nice to see someone making an 8.0 rom available...
btw, AFAICT - you seem to be missing the Nov Updates for your kernel.
You also might consider adding LTS. just a thought.
nine7nine said:
Nice to see someone making an 8.0 rom available...
btw, AFAICT - you seem to be missing the Nov Updates for your kernel.
You also might consider adding LTS. just a thought.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
another 8.0 Rom available here on xda. works very fine
nine7nine said:
Nice to see someone making an 8.0 rom available...
btw, AFAICT - you seem to be missing the Nov Updates for your kernel.
You also might consider adding LTS. just a thought.
Click to expand...
Click to collapse
Feel free to add a pull request for November Kernel changes. Not so much my focus right now but will get to it.
Also what is LTS?
hardslog said:
Feel free to add a pull request for November Kernel changes. Not so much my focus right now but will get to it.
Also what is LTS?
Click to expand...
Click to collapse
No man, Im just pointing it out ~ I develop my own kernel for Marlin, so unlikely that I'm not going to be cloning yours to do that bit of work for you, I have enough on my plate -> It's your responsibility as someone who is providing a Rom and kernel to other users....
You should make staying up-to-date with Security patches / kernel patches every month a priority. there are bug fixes and security fixes for things like CVEs ~ not keeping up-to-date can put users at risk....
LTS = Long Term Stable Release - upstream linux updates to your kernel. this also serves the same purpose, as above (google has been slack on this, but that's changing). Some info on how to set yourself up for LTS; https://forum.xda-developers.com/an...rence-how-to-upstream-android-kernel-t3626913
Also, another important note / advice on providing ROMs to people. Please make sure that you are properly signing your builds (signature signing). ref: https://source.android.com/devices/tech/ota/sign_builds .... I'm not sure how OmniRom does things; if they have their own keys that you can use, but if you are using testkeys from the SDK - that's a bad idea. ~ as your system/platform apps would be signed with publicly known/available keys. That breaks an important layer of Android's security model.
nine7nine said:
No man, Im just pointing it out ~ I develop my own kernel for Marlin, so unlikely that I'm not going to be cloning yours to do that bit of work for you, I have enough on my plate -> It's your responsibility as someone who is providing a Rom and kernel to other users....
You should make staying up-to-date with Security patches / kernel patches every month a priority. there are bug fixes and security fixes for things like CVEs ~ not keeping up-to-date can put users at risk....
LTS = Long Term Stable Release - upstream linux updates to your kernel. this also serves the same purpose, as above (google has been slack on this, but that's changing). Some info on how to set yourself up for LTS; https://forum.xda-developers.com/an...rence-how-to-upstream-android-kernel-t3626913
Also, another important note / advice on providing ROMs to people. Please make sure that you are properly signing your builds (signature signing). ref: https://source.android.com/devices/tech/ota/sign_builds .... I'm not sure how OmniRom does things; if they have their own keys that you can use, but if you are using testkeys from the SDK - that's a bad idea. ~ as your system/platform apps would be signed with publicly known/available keys. That breaks an important layer of Android's security model.
Click to expand...
Click to collapse
Long Term Support
Nick80835 said:
Long Term Support
Click to expand...
Click to collapse
thanks Nick - small detail - not enough coffee. lol
I figured you were referring to long term support but never heard that terms of android kernels before.
Anyway the homebuilds are likely signed using test keys. When omni has the Jenkins server up and running it has its own keys.
Also I'd like to respectfully disagree with your statement on making sure I keep up to date and that's it's all things I MUST do.
Firstly this is a beta. When we get the weeklies rolling I'll keep on top of CVEs etc.
Secondly if people don't like the security of this ROM I don't really care. I'm not forcing anyone to flash it. This is an open source project for anyone to contribute. It is not my job to be trying to make sure I develop things and merge patches the minute they become available. In fact none of this is my job.
I'll merge security patches when I have time. And if someone wants to add PRs to get them in quicker they are welcome to do so. But if someone has the means to help out but only wants to criticize then please take discussions elsewhere. Not saying this to anyone in particular, but as a generality, as nine you are making valid statemtents.
hardslog said:
I figured you were referring to long term support but never heard that terms of android kernels before.
Click to expand...
Click to collapse
All android kernels are (supposed to be) based on LTS. Vendors just don't end up patching them fast, if at all. not a good thing.
hardslog said:
Also I'd like to respectfully disagree with your statement on making sure I keep up to date and that's it's all things I MUST do.
Firstly this is a beta. When we get the weeklies rolling I'll keep on top of CVEs etc.
Secondly if people don't like the security of this ROM I don't really care. I'm not forcing anyone to flash it. This is an open source project for anyone to contribute. It is not my job to be trying to make sure I develop things and merge patches the minute they become available. In fact none of this is my job.
I'll merge security patches when I have time. And if someone wants to add PRs to get them in quicker they are welcome to do so. But if someone has the means to help out but only wants to criticize then please take discussions elsewhere.
Click to expand...
Click to collapse
#1 - I wasn't criticizing, in fact; I said it was great to see some Oreo rom development Happening... What I did was; pointed out that your kernel isn't up to date (by a month, not a minute) * That's not a criticism, it's just a fact.... && I made some suggestions on how to rectify that and provided you with some additional potentially useful information on LTS ~ thinking it may be helpful to you...
I also mentioned the signature signing because in the past I've seen ROMs on XDA haven't been signed properly - because the people who built them skipped that important step or didn't know any better. (not implying you, but; you would know 100% -> one requires generating your own private keys, one doesn't).
#2 - I never said you "MUST" do anything. Please go back and re-read what I actually wrote... I suggested that you probably *should* merge the monthly patches from Google and suggested possibly making use of LTS, As something that *should* be a priority (not *must* be). Monthly patches and LTS exist for a reason.... But yes; At the end of the day, your right ~ It's entirely your choice..... It's also one of the reasons, why I tend to avoid flashing custom roms -> you have zero idea whether the people cooking them up have actually done things properly (again, not talking about you, just a general statement).
#3 - I gave you a valid reason why I wouldn't be doing a pull request; I'm working on my own kernel, I'm busy && It's not my responsibility. What IS my responsibility to make sure that any kernel that I release IS patched and up-to-date. *It doesn't matter that it's not my job; I'm putting it out there for other people to use on their device; which typically contain loads of personal info, mobile banking, accounts, contacts, etc... So even with a disclaimer added; I still put in the extra effort. Because it's important.
Regardless, the whole thing of getting up-to-date and even merging LTS (if you chose to do so) takes maybe 10min. ~ not exactly something that you need me or anyone else to do for you or a pull request for. ~ It would take me longer to fork/grab your sources, pull in all of the commits and do a pull request... See why I'm not doing it now? Anyway, good luck with your ROM.
nine7nine said:
All android kernels are (supposed to be) based on LTS. Vendors just don't end up patching them fast, if at all. not a good thing.
Regardless, the whole thing of getting up-to-date and even merging LTS (if you chose to do so) takes maybe 10min. ~ not exactly something that you need me or anyone else to do for you or a pull request for. ~ It would take me longer to fork/grab your sources, pull in all of the commits and do a pull request... See why I'm not doing it now? Anyway, good luck with your ROM.
Click to expand...
Click to collapse
You aren't telling me anything that I don't already know but thanks for the input anyway as it is good topic for discussion.
You'd think that with this being a google device on AOSP that developing for it would be easy, which certainly isn't the case. There was a lot of bull%##! going on with this device which has caused people to have difficulty getting anything going for it.
Just for info though when the weeklies come out for Omni they are very quick to patch security flaws. The next question though is to see if we can get opendelta working on this device with its weirdo A/B partition scheme
hardslog said:
You'd think that with this being a google device on AOSP that developing for it would be easy, which certainly isn't the case. There was a lot of bull%##! going on with this device which has caused people to have difficulty getting anything going for it.
Just for info though when the weeklies come out for Omni they are very quick to patch security flaws. The next question though is to see if we can get opendelta working on this device with its weirdo A/B partition scheme
Click to expand...
Click to collapse
one would hope that it would be easy to develop for due to aosp support, but yeah. the concensus seems to be that is not the case...mol.... however, if u look at Copperheados; that's one main developer; he's had their OS working nicely and that's also with a locked bootloader and system updates coming from their servers, etc...
It's a given that strncat (cos Dev) is a smart dude.... but yeah; it demonstrates that it's very doable... if one core Dev can pull it off, a community of devs on xyz ROM should be able to, as well....
BTW, I'm curious, is odexing working on your ROM?
@hardslog
Another question; Do you build the Bash interpreter into your rom?
I tried this rom with Magisk and custom kernel ( separately and together ) and I got bootloop. It's a shame cuz I really like this rom added features. I'm back on stock 8.0.0 now
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"
}
Code:
#include
/*
* Your warranty is now void.
* and I didn't give you any warranty to begin with
*
* I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, 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, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
*/
crDroid G+ community
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today.
Based on Lineage with extra goodies
Installation files & steps
Downloads :
NB: MUST USE OLD BOOTLOADER AND MODEM!! see LineageOS 15.1 thread
ROM: crDroidAndroid-8.1-20180917-ks01ltexx-v4.6.1-DiamondJohnDroid.zip MD5: ba48e90509017db02d767511af7fabac
Previous build: (will disappear as I am low on space!), and I know no known reason to use the older builds.
Rom :
The following two need the Newer I9506XXUDRB1 Modem and matching bootloader => I9506XXUDRB1_I9506XXUDRA1_bootmodem.tar
crDroidAndroid-8.1-20180911-ks01ltexx-v4.6-DiamondJohnDroid.zip MD5: daa44cc297fe7a2acfeb133c5c82e27a
crDroidAndroid-8.1-20180826-ks01ltexx-v4.6-DiamondJohnDroid.zip MD5: 6da18f10f38fbd0a54efd2a40a4d9f33
The following need the old J2 Modem and matching bootloader
crDroidAndroid-8.1-20180723-ks01ltexx-v4.5-DiamondJohnDroid.zip MD5: fc8b3a842e930202380aea13842b8c9f
crDroidAndroid-8.1-20180708-ks01ltexx-v4.4-DiamondJohnDroid.zip MD5: 831ccc71211bb444dfc04105f7449ef2
crDroidAndroid-8.1-20180515-ks01ltexx-v4.2.zip MD5: c2f4de35c418d074c82e7467740c5205
deleted crDroidAndroid-8.1-20180430-ks01ltexx-v4.2-DiamondJohnDroid.zip MD5: f5231e52e269c8cfce73c56de2a12ab2
TWRP: twrp-3.2.3-0-ks01lte.img
GApps : Opengapps 8.1
INSTALLATION INSTRUCTIONS
If you don't know how, then this isnt for you. But ensure you have a NANDROID as its not for daily use or replacement of your current ROM!
See the LineageOS 15.1 thread for hints: https://forum.xda-developers.com/ga...-lineageos-15-1-unofficial-galaxy-s4-t3747831
If you get a SystemUI has stopped during the first boot, click on wait not close/stop.
SuperUser is included in the ROM, but is switched OFF by default.
DEVICE: Samsung S4 - GT-i9506 - ks01ltexx
Recommended Bootloader / Modem: I9506XXSDPL2_I9506XXUDOJ2_bootmodem
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: crDroid
SELinux: ENFORCING
Sources:
https://github.com/crdroidandroid
https://github.com/kyasu/android_kernel_samsung_msm8974
https://github.com/kyasu/android_device_samsung_ks01ltexx
https://github.com/kyasu/android_device_samsung_msm8974-common
https://github.com/LineageOS/android_device_samsung_msm8974-common
https://github.com/kyasu/android_vendor_samsung_ks01ltexx
WITHOUT THE DEVICE TREE BUILT BY @kyasu THIS ROM WOULD NOT BE POSSIBLE
see: https://forum.xda-developers.com/ga...-lineageos-15-1-unofficial-galaxy-s4-t3747831 and show some well deserved thanks!
NB: THIS BUILD SHOULD BE CONSIDERED:==>
* I WILL NOT BE DEBUGGING THIS ROM, HOWEVER, PLEASE FEEL FREE TO POST ISSUES FOR THE BENEFIT OF OTHERS
* A ONE OFF BUILD, I WILL NOT BE DOING REGULAR UPDATES
* NOT BE CONSIDERED A DAILY CANDIDATE
* JUST A PREVIEW OF WHAT THE CURRENT STATE OF SOURCE CODE IS AT
Did I mention this would not be possible without the work by @kyasu, the crDroid & LineageOS teams.
Will try it rom, tks u for support
Thanks for posting, I personally still use version 14.1 of crdroid.
But what is the purpose if you're not gonna debug and maintain this rom?
I'm sure something will pop up...
Sent from my GT-I9506 using Tapatalk
DonAndress said:
Thanks for posting, I personally still use version 14.1 of crdroid.
But what is the purpose if you're not gonna debug and maintain this rom?
Click to expand...
Click to collapse
DiamondJohn said:
* JUST A PREVIEW OF WHAT THE CURRENT STATE OF SOURCE CODE IS AT
Click to expand...
Click to collapse
I personally am currently using my own build of Nougat ResurrectionRemix, which I have also shared here at XDA. I personally wanted to check if I could build a non LineageOS Oreo ROM using @kyasu LOS device tree's. ie Hopefully, in the future, when all the source code code is more stable, I will be able to build another ROM for my personal use (which I would also share).
aaand ... https://en.wikiquote.org/wiki/George_Mallory)
DonAndress said:
I'm sure something will pop up...
Click to expand...
Click to collapse
ALL the oreo code is still VERY early days, I dont think there are even too many official devices with releases yet ie not even Alpha's. You don't need to look too far before something "pops up"
DonAndress said:
if you're not gonna debug and maintain this rom?
Click to expand...
Click to collapse
Thats one of the brilliant things of open source code. There are a team of people working on LineageOS (the basis for crDroid and ResurrectionRemix), as well as people working on crDroid and RR, as well as the work being done by @kyasu specifically for our device. Any work they do, would flow through to anyone building the ROM from source. ie "I" do not specifically need to do the debugging, hopefully. And that makes me think of another reason, maybe this build will inspire someone else to give it a go.
DiamondJohn said:
I personally am currently using my own build of Nougat ResurrectionRemix, which I have also shared here at XDA.
Click to expand...
Click to collapse
I have to check your build then. I'm aiming for most debloated rom.
maybe this build will inspire someone else to give it a go.
Click to expand...
Click to collapse
You know I would but unfortunately I'm completely noob in this area. I don't even know where to start
Sent from my GT-I9506 using Tapatalk
DonAndress said:
I have to check your build then. I'm aiming for most debloated rom.
Click to expand...
Click to collapse
Do you consider lineageos bloated?
Big thanks @DiamondJohn for providing us with some options besides LOS! By the way, was the "ks01ltexxd" in the title intended?
PixelChris95 said:
Do you consider lineageos bloated?
Click to expand...
Click to collapse
Each Dev has a right to include all the crap he wants. I'm not saying that DiamondJohn does but still, some roms are faster and more battery efficient then other.
Sent from my GT-I9506 using Tapatalk
DonAndress said:
Each Dev has a right to include all the crap he wants. I'm not saying that DiamondJohn does but still, some roms are faster and more battery efficient then other.
Click to expand...
Click to collapse
Yes that's true, but since almost every custom rom is based on LOS I wouldn't expect a huge difference. Also in my experience the apps installed by the user or Google services eat up the battery, not so much the rom (of course the system consumes battery, but most of the time it's something else, if one has unusual high battery drain). I think if you really want to save energy you probably need to throttle the CPU. And Oreo isn't too great at saving battery at the moment (I am only talking about the builds available for our device of course). I hope this will get better in the future. I am using Oreo nevertheless because it's rock stabil and I like the features.
Interesting, what features are they?
Sent from my GT-I9506 using Tapatalk
DonAndress said:
Interesting, what features are they?
Click to expand...
Click to collapse
Picture in picture mode, autofill framework and the design are the new features I benefit the most from. Might be different for others of course.
PixelChris95 said:
Do you consider lineageos bloated?
Click to expand...
Click to collapse
I'd like to hear the answer to this question.
I dont think you should be looking at ROMs like ResurrectionRemix or crDroid if you wish to be running "light", and I would also go for PICO GApps (which is what I run).
PixelChris95 said:
By the way, was the "ks01ltexxd" in the title intended?
Click to expand...
Click to collapse
nope, thanks, and corrected
DonAndress said:
Each Dev has a right to include all the crap he wants. I'm not saying that DiamondJohn does but still, some roms are faster and more battery efficient then other.
Click to expand...
Click to collapse
As this was a build straight from the source (I only changed one line to make it permissive), its the decision of the devs at the crDroid Team, not me.
By the way, whenever I have looked at the changes made in crDroid, the non-device specific code changes has always been by a single dev. I am sure its a group that decides on bigger things, like what to include, just interesting that shared (between devices) code almost seems to be maintained by a single guy.
PixelChris95 said:
Yes that's true, but since almost every custom rom is based on LOS I wouldn't expect a huge difference. Also in my experience the apps installed by the user or Google services eat up the battery, not so much the rom (of course the system consumes battery, but most of the time it's something else, if one has unusual high battery drain). I think if you really want to save energy you probably need to throttle the CPU. And Oreo isn't too great at saving battery at the moment...
Click to expand...
Click to collapse
I am running Nougat ResurrectionRemix, and to limit my battery drain, I have Greenify running VERY aggressively. I also have the CPU at standard max, but a conservative governor; Tripndroid, which doesn't seem to lag for my usage, but likes the lower frequencies.
PixelChris95 said:
I am using Oreo nevertheless because it's rock stabil and I like the features.
Click to expand...
Click to collapse
I am guessing you are running LOS. The latest build appears to have caused some "noise", which worries me as this build is based on similar code. GPS also appears to be a common issue. I tried GPS on this build and it didnt connect to any satellites (I was inside, and it was heavily overcast that day) but when I restored my daily and it didnt lock a location either (but at least connected to a few satellites). I'd be interested to know by anyone who tries this ROM if the GPS works? That's a deal breaker for me personally. The "efs" partition talk also really concerns me.
New build!
There is anew build up (see OP). This build was basically a test to see what would happen (ie would it even boot) if the SELinux was ENFORCING
Make sure you flash GApps along with the ROM before the first boot. I accidentally booted without GApps and then flashing it after caused issues.
I also tried Magisk 16.0 for root, and that appeared to work. Instead of the LineageOS add-an
I also tried flashing Viper, and that worked as soon as I switched over to permissive. I also took a log to see what permissions/SELinux statements would enable it to run enforcing.
I did appear to have issues the second time I flashed it with ADB over WiFi (it didnt pop up the request/confirmation).
I am also hoping that the GPS will be fixed soon in the LOS 15.1 builds which will hopefully flow through to crDroid:fingers-crossed:
Remember, this is unofficially an an unofficial build:silly:
does not work NFC
DiamondJohn said:
I dont think you should be looking at ROMs like ResurrectionRemix or crDroid if you wish to be running "light"
Click to expand...
Click to collapse
You don't think crdroid is light?
I've been using it for a year now and I believe it's pretty light.
Sent from my GT-I9506 using Tapatalk
DonAndress said:
You don't think crdroid is light?
I've been using it for a year now and I believe it's pretty light.
Click to expand...
Click to collapse
Feature wise, it is NOT light; as it is very featured. Those features come from code.
To me, if you truly want light, you go with a "vanila" AOSP ROM. I am NOT talking about how they run, but their contents. On a different device (xt907) I built a number of Nougat ROMs, and AICP actually seemed noticeably "snappier" to me than crDroid or RR. A ROM not being light, does not mean it is slow.
Not that's its an accurate comparison of anything, but comparing the Oreo file sizes,
LOS 15.1 = 359MB
RR v6.0.0 = 329MB (I recently did a test build, and it booted and ran :victory
crDroid v4.0 = 385MB
also, the main build section has "steps" when compiling a ROM, below are the results from the last time I compiled each of these
LOS 15.1 = 75755
RR v6.0.0 = 76872
crDroid v4.0 = 77145
On a side note, I have another device (Nexus 5, the xt907 has died) and that has an RR Oreo ROM at around 359MB and an AOSP ROM (v8.0) at 297MB.
By the way, RR is my ROM of choice, as (I think) this device is much more than capable of handling just about any ROM we can thrown at it, at least thus far for me.:good:
onenett said:
does not work NFC
Click to expand...
Click to collapse
Do you know if it works on the Oreo LineageOS builds?
out of interest
There has been over 100 downloads of the ROM. Is anyone actually using it as a daily? or simply as a preview? noting that was the actual purpose; ie a preview not a daily.
BEST ANDROID OREO ROM FOR - S4 I9506 ks01ltexx
DiamondJohn said:
There has been over 100 downloads of the ROM. Is anyone actually using it as a daily? or simply as a preview? noting that was the actual purpose; ie a preview not a daily.
Click to expand...
Click to collapse
Hi DiamonJohn,
I'm giving a daily test although this is not the case, but I'm even amazed by the result even with this state of the ROM.
In terms of apps, everything works, at least the ones I use daily basis that are; Facebook, Messenger, Inbox "2 email accounts", Outlook "1 email account", Google Keep, DropBox, Skype, Twitter, Youtube, etc..., bluetooth works and I'm going to test the GPS tomorrow when I go running
What I mean is that even though not being for daily use (for now) this ROM is not too far from that in my point of view, of course you still need a lot of work ahead and the battery does not last long but what does it matter at this stage since the RR roms happens the same :laugh:
With spirit and with head this rom can get very good at level ★ ★ ★ crDroid ★ ★ ★ Official[7.1.2][ks01lte][V3.5][09 JUN] and by the way, it's the rom I use every day and it's great.
I was going to forget to mention, Magisk Manager, Xposed and Greenify they are installed and working properly.
For now is everything and I hope this rom go forwar, I am very interested because my GALAXY S4 LTE still has much to give :good:
And I say even that this ROM in the point that is, deserves the title that I gave :angel:
pedra3000 said:
... and I'm going to test the GPS tomorrow when I go running ...
Click to expand...
Click to collapse
I would not expect the GPS to be working. It was built without a change from LOS that would fix it. But I tried including the code, which didn't appear to work for me, and only after realised that I had a hardware issue (my antenna wasn't connecting well physically on the device fixed now) I am now waiting (patiently) for @kyasu to update his actual device tree with the changes.
I have also built an Oreo ResurrectionRemix. I am hoping someone will test applying a substratum theme against one of these Oreo ROMs (although I haven't made public the RR one) I have built. That (and the GPS) are probably my roadblocks right now foir me to upgrade and thereby be more frequent with new builds; ie I dont know if Substratum works or not. I have tested Viper (another one of my personal deal-breaks, and that works)
GPS Works well
Surprise LOL, GPS works well with me!
I use Endomondo - Running & Walking and GPS and continued to work well, without having the 4G connected!
I installed the GPS TESTE to see how many satellites it picks up and the accuracy and it seemed to me everything normal (view image link)
https://www.dropbox.com/s/kycoe6blbovs78g/Screenshot_GPS_Test_20180327-082957.png?dl=0
About the Resurrection Remix I tested (Nougat) are good, but the battery is the weak point, because until now they all drain very quickly, which can not be for me to be daily use. As I mentioned, the crdroid ★ ★ ★ ★ Official [7.1.2] [ks01lte] [V3.5] [09 JUN] the battery is very good and for now is my choice for daily use.
I want to update to the OREO and so far and I have always liked crDroid for better results this your unofficial ROM is very very good :good:
Of course I'm here to test your Oreo RR
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
USB OTG
Rotation
Key backlights
Video/Audio playback on mxplayer/vlc for now
What's NOT working :
Everything Else
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Build : https://drive.google.com/open?id=1kHXl7YKIt8qq6Mk3R8FojVz5LZYlokDO
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
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 /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Donations :
You don't have to but if you want so...
[email protected]
Contributors
Ather
Source Code:
android_vendor_samsung_gts28wifi
android_vendor_samsung_gts2-common
android_device_samsung_gts28wifi
android_device_samsung_gts2-common
android_kernel_samsung_exynos5433
local_manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2018-04-05
Last Updated 2018-04-05
Congratulations
congratulations
So MTP works as long as usb debugging is disabled, also source resync'd for April 5th patches, will update link in OP later
What is the benefit of this new lineage over PoseidonROM 1.1?
Can you please share your source repos so that others may build? https://github.com/LineageOS is not specific to gts28wifi.
raysucks said:
What is the benefit of this new lineage over PoseidonROM 1.1?
Click to expand...
Click to collapse
This is pure Android from Google as opposed to Samsung's modifications, this is the latest android version (8.1.x) where as Samsung stopped at 7.0 for our t710 model, this has the latest security patch as of yesterday April 5th,whilst our TouchWiz rom has from January
Sure this Rom will have bugs but hopefully we'll fix them
ripee said:
Can you please share your source repos so that others may build? https://github.com/LineageOS is not specific to gts28wifi.
Click to expand...
Click to collapse
I'll do that later when they're all synced up, have to add few fixes
Ather said:
This is pure Android from Google as opposed to Samsung's modifications, this is the latest android version (8.1.x) where as Samsung stopped at 7.0 for our t710 model, this has the latest security patch as of yesterday April 5th,whilst our TouchWiz rom has from January
Sure this Rom will have bugs but hopefully we'll fix them
Click to expand...
Click to collapse
Thanks for the explanation. Does this new lineage support the finger print scanner? Your PoseidonROM from what I've read is the only ROM that supports it, it's a must have for me.
Thx again for your hard work.
raysucks said:
Thanks for the explanation. Does this new lineage support the finger print scanner? Your PoseidonROM from what I've read is the only ROM that supports it, it's a must have for me.
Thx again for your hard work.
Click to expand...
Click to collapse
Sadly no fingerprint yet, you're welcome to continue using PoseidonROM until the bugs are fixed in this
Will do. Off topic, super weird anomaly with my Chase bank application. As a security feature, devices have to be registered. This requires an access code be sent to your email address, this confirms your identity. Once confirmed, you're set. Recently, the Chase application continues to interpret that my device is not registered. Is the device ID a moving target with PoseidonROM 1.1? Never had this occur with 1.0. Thx
Thank you very much for being with us.
complete sources are added to OP
Ather said:
complete sources are added to OP
Click to expand...
Click to collapse
What the difference between your code and mine, which you successfully forked some days ago?
I hope you don't mind if I report to you.
I forked your repos if you decide to delete them.
Anyway, tell us, please, your wonderful oreo development story here in public. What Were you doing during 2 weeks of hard work?
I can prove each string of code there. Where was the problem, how I fixed it etc.. But I never have any thoughts to upload almost useless rom to public, but I had this opportunity since february...
Wanted to be famous? You are famous now as kanger and thief.
ps: i'm very loyal when someone uses my code even without any credits. And I even ignored your uploaded rom until you reuploaded sources yesterday night without any mentions at least... So, you are the thief now and you have to live with it. Good luck.
bonuzzz said:
I forked your repos if you decide to delete them.
Anyway, tell us, please, your wonderful oreo development story here in public. What Were you doing during 2 weeks of hard work?
I can prove each string of code there. Where was the problem, how I fixed it etc.. But I never have any thoughts to upload almost useless rom to public, but I had this opportunity since february...
Wanted to be famous? You are famous now as kanger and thief.
ps: i'm very loyal when someone uses my code even without any credits. And I even ignored your uploaded rom until you reuploaded sources yesterday night without any mentions at least... So, you are the thief now and you have to live with it. Good luck.
Click to expand...
Click to collapse
Hello, I helped him to bring oreo to this tab, this is a work in progress, who told it was not useless to flash it and ready for daily use ?
You are right, he used your sources, might you would like to be added on credit right. A quick pm would have been better.. I do not know you that much, might you started to do lineage 15.1 too, in this case you can create a git project and work together, I would be glad to see this project growing up ! I think working together is the best way to learn from each others !
Ps: useless to call him a thief, this is just a mistake .. useless to create a new drama about this story, hope to see you working together
McFy said:
Hello, I helped him to bring oreo to this tab, this is a work in progress, who told it was not useless to flash it and ready for daily use ?
Are you jealous ?
You are right, we used your sources, might you would like to be added on credit right. But why doesn't send a quick pm instead of writing a post that will be deleted by xda mods or hated by people having interest in news rom for this tab, I do not know you that much, might you started to do linege 15.1 too, in this case you can create a git project and work together, I would be glad to see this project growing up !
Rethink life
Click to expand...
Click to collapse
He was writing me also when he tried to compile...
Do you think the rom without wifi is very useful for users? I dont think so..
Answer me one question: what the difference between my code and his code?
I said I ignored this situation until he reuploaded my sources without leaving any history and mention. But he had my forked sources on his git until yesterday.. I dont know why he decided to assign all work to himself. And I really wonder why the xda stuff, retired in particular allows himself to just steal other work.
I dont need any credits of something, but I spent my time to bring up oreo here and it is very unrespectful to just kang all work, publish with other credits and wrote he spent 2 weeks for that..
Just curious, why you answer to me instead of him?
bonuzzz said:
He was writing me also when he tried to compile...
Do you think the rom without wifi is very useful for users? I dont think so..
Answer me one question: what the difference between my code and his code?
I said I ignored this situation until he reuploaded my sources without leaving any history and mention. But he had my forked sources on his git until yesterday.. I dont know why he decided to assign all work to himself. And I really wonder why the xda stuff, retired in particular allows himself to just steal other work.
I dont need any credits of something, but I spent my time to bring up oreo here and it is very unrespectful to just kang all work, publish with other credits and wrote he spent 2 weeks for that..
Just curious, why you answer to me instead of him?
Click to expand...
Click to collapse
I don't think so too,
He did some edit's to boot,
I think this is a mistake,
This doesn't mean anything here
As I said work together, just let him add you to credit and push the commit history, I am pretty sure it's a mistake
For your 2 last question: He wanted to taste oreo on his tab so he tried to build, I told him some edit's to do on nougat tree to build then boot as your sources wasn't fully fixed about this, he shared it for free here to let people know he work on, I just want you know real reason of what you call a kang, I think it's a simple mistake whith a simple solution that you have to found together, might xda is not place for this and it doesn't have to create a drama.
First of all, i'm no thief or a kanger, the only thing i used from you was your kernel modified for oreo , the rest of the sources were initiated by raymanfx BUT they wouldnt compile, and anan is witness to that because i sent him the files to test aswell, the kernel by lineageOS had sepolicy errors which i tried very hard to fix but they woudnt boot with it, FYI before you initiated Oreo commits to your kernel, i already had added my fixes to it, like the missin zimage type, min/max errors, you can ask matt about that, then when i finally got to bootloop it was ueventd error which remi told me about, after that i was missing manifest which by help of matt i generated for gts2 by looking at his. the sources that were upped had problems which i fixed so i pushed them with them included minus the orignal author thats my bad i agree, but please dont call me a kanger atleast i deserve that much respect. this is not a competition to become famous, you withheld souces and the rom from others before aswell and when i always asked you for help you simply gave meaningless answers, rayman never replied, the lineage irc channel is full of dickheads so i did all of it on my own with help from Matt and remy.
i'll add your forked kernel in OP, and also releasing the bare minimum version was because so others could help me fix it not for becoming famous, i've been on xda since windows mobile days and have made my share of custom roms,apps so i dont need to be famous
Ather said:
the lineage irc channel is full of dickheads
Click to expand...
Click to collapse
I laughed so hard when I read this part! :laugh:
{
"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.
Requirements:
You should start off with the latest OxygenOS on both slots and then proceed to flash Carbon.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
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 OnePlus 6
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-03-02
Last Updated 2019-08-28
Yess! Finally you are here! Tnx a lot buddy!
Sweet! Thanks man, going to flash it now!
Nice to see you here ...
This is the one I've been waiting for ???
Flashed and ROM is superfast and fluid.
Feb security patch if need to know
Man, the last time I ran Carbon was in the LG G3 days, and it rocked back then.
Installed and setup without a hitch. The ROM is super snappy. It's impressively fluid and responsive. Too early to tell much else. I'm going to take this for a spin in the coming days. Great job, brother!
As noted, it is an early release. Please be patient and give it time to mature. While not bare bones, it is lacking some popular features. Inb4 the can I has storm.
Edit: The ROM is performing great. No crazy idle drain and deep sleeps as it should. The stock kernel is very efficient.
Wow.. Its soo Aww to see this rom for op6..
Can't believe how good this rom is on an initial release. This is why carbon is top notch?
cmart4 said:
Can't believe how good this rom is on an initial release. This is why carbon is top notch
Click to expand...
Click to collapse
Thanks for your feedback. I don't mean to start a war but what's your background on this device? Like did you try a lot of other custom ROMs and you can tell this one is faster?
Tomatot- said:
Thanks for your feedback. I don't mean to start a war but what's your background on this device? Like did you try a lot of other custom ROMs and you can tell this one is faster?
Click to expand...
Click to collapse
Had the device since launch, been rooted forever and have tried almost all roms on xda, stock and aosp. All roms are good for what they are, but some miss features while others have a plethora of features. I've used Carbon on many previous devices and always found myself going back to Carbon. Yes, I'm a flashaholic of many years, but to me, Carbon has always been a gold-standard thru all my flashing of various devices... I stray, but always come back
This is my opinion only of course, but past experiences with Carbon have been nothing but buttery goodness. This initial release is an excellent beginning of what I hope will be a long line of releases for this device. Some of my fave roms on here are Omni, AOSIP, Tresk, and Syberia. One of the reasons I bough the Oneplus 6 was the ability to flash roms and the excellent community of sites like XDA. Love this site
cmart4 said:
Had the device since launch, been rooted forever and have tried almost all roms on xda, stock and aosp. All roms are good for what they are, but some miss features while others have a plethora of features. I've used Carbon on many previous devices and always found myself going back to Carbon. Yes, I'm a flashaholic of many years, but to me, Carbon has always been a gold-standard thru all my flashing of various devices... I stray, but always come back
This is my opinion only of course, but past experiences with Carbon have been nothing but buttery goodness. This initial release is an excellent beginning of what I hope will be a long line of releases for this device. Some of my fave roms on here are Omni, AOSIP, Tresk, and Syberia. One of the reasons I bough the Oneplus 6 was the ability to flash roms and the excellent community of sites like XDA. Love this site
Click to expand...
Click to collapse
Thanks for your detailed feedback! I might give it a try in a few builds once it gets more mature.
If you feel like it and have time for it, could you fill this sheet to give users an idea about features available? Thanks.
https://docs.google.com/spreadsheet...jKcs4x_N8x7FEYqWwq-j5vZ8Kw/edit#gid=724111415
Great rom.Its smooth and stable.please add the navigation gestures and on the go mode if possible.
New build
Just finished uploading a new build.
Small Changelog:
March ASB
As always let us know if you encounter any bugs. We're currently all rounding up on some remaining bugs/quirks and hope to present you an official build soon
I guess @Myself5 forgot to post it here
In case someone isn't in telegram:
https://twitter.com/carbonrom/status/1107471097560264704
This is a good sign. This is a popular ROM but the thread is completely dead. This usually means nobody is having any problems worth noting.
I'll have to give this a shot
gorilla p said:
This is a good sign. This is a popular ROM but the thread is completely dead. This usually means nobody is having any problems worth noting.
I'll have to give this a shot
Click to expand...
Click to collapse
When you try it, please give us some feedback, I'm really interested in this rom. Thanks.
Hey guys,
nice to See carbon here, i used it some years ago on my S4,S3,S2 (and maybe Note 2 LTE,but im not sure )
i was on 9.0.4 and installed it some minutes ago. After first Boot there was a message i should update my Vendor or something like that.
I dont know if its important i got my OP6 4 days ago and i didnt mod my last phone so much (Huawei Mate 10 Pro btw) so i dont have big knowledge at the moment, sorry
Everything else works for now (at least what i have Seen/tried ) and it runs very smooth!
Here is what ive done,maybe i made a mistake here,it was the first Rom i flashed in this phone:
- of course a Backup (Titanium Backup and Nandroid)
- wipe Dalvik,System and Data
- flashed Rom and twrp
- reboot
- flash pico gapps and Magisk
i Miss the gestures so i think i will go back to stock for a while (until i found something similar, i know there are some apps but i didnt try Them now)
Edit: had to decrypt my device to be able to boot stock afterwards, simply did a factoy reset and restored my Data partition.
Gesendet von meinem ONEPLUS A6003 mit Tapatalk
Official builds are here
The time has finally come, we're going official.
After Server issues, and several rebases due to Google's Upstream doing the same, we're finally satisfied with the ROM to make it officially available to the public.
The new CarbonROM revision 7.0 is codenamed Opal, and is currently based on android-9.0.0_r35 (thats the April security bulletin).
The OP has been updated to include the official download.
PLEASE NOTE: You WILL need to perform a clean install. The official builds are signed with custom keys for your security and are therefore not compatible with the unofficial builds that were signed with the default Google keys.
We feel like this might be one of our best releases yet, with new features like Aggressive Battery, a newly designed performance vendor and many more coming. Let us know what you think.
Also, this is the first time ever we will keep on maintaining the older branch. That means you will still get monthly security updates of Noct on the devices that do not support Pie yet.
A new blog is due to get up soon, an in depth release post will follow there.
For now, Happy flashing and we hope you'll enjoy the ROM as much as we did creating it
Best news this week so far...?
subodhdhull said:
Great rom.Its smooth and stable.please add the navigation gestures and on the go mode if possible.
Click to expand...
Click to collapse
Can someone please confirm that navigation Gestures are included in the latest update? Thanks
LineageOS 16.0 Unofficial for Samsung Galaxy A3 (2015)
Supported variants:
SM-A300FU
DISCLAIMER
Code:
#include
/*
* Your warranty is now void.
* The ROM is under developement and have some bugs.
* 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. By flashing this ROM, you accept this disclaimer.
*/
LineageOS 16.0-20191129
Kernel 3.10.108
CAF LA.BR.1.2.9.1_rb1.5
Magisk compatible
MicroG ready
NFC disabled
Keymaster disabled
Thx to @vl_w
This TWRP recovery uses Lineage partition layout that differs from other recoveries.
Do not mix up efs/modem/apnhlos... backups with other releases.
All ROMs/Recoveries are compiled with latest LOS16 sources/toolchain.
BUGS:
No Sound (WIP - needs proper ASOC driver)
Probably the same as 15.1
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 16 for Galaxy A3 (2015)
Uploading my files elsewhere is not appreciated, if you need to upload my files, just use the links provided here. Thanks.
ROM 16.0 -> DOWNLOAD
TWRP 3.3.1 -> DOWNLOAD
Credits:
@vl_w
Sources:
https://github.com/Galaxy-MSM8916
Version Information:
ROM Status: Beta
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Any Bootloader and Modem.
Based On: LineageOS 16.0
Created: 2019-11-29
Last Updated: 2019-11-29
Hi !
Works well for now :good:
Thanks to @DualJoe
@DualJoe
The rom works well but there is no sound.
What setting can I activate to fix this?
Thanks
carlos974 said:
@DualJoe
The rom works well but there is no sound.
What setting can I activate to fix this?
Thanks
Click to expand...
Click to collapse
Sound only works with headphones, yet.
carlos974 said:
Hi !
Works well for now :good:
Thanks to @DualJoe
Click to expand...
Click to collapse
Hi @carlos974! How did you manage it? On my A300FU there is still no Sound without headphones. Thumbnails is the same as yours.
Sorry, that was a temporal error! This request ist irrelevant!
The function of the speaker icon on the phone is meant to be to let other people participate in the conversation or to work while speaking (for example ). But if i tap on it, i cannot here anything anymore. The sound is not redirected to the speaker. Consequently I can only hear the conversation partner, if do not tap and keep the phone on my ear.
The driver for the speaker/amplifier is missing so it's not working at all atm. I will fix it asap.
But good to know that the phone function is otherwise working properly. Thanks for reporting.
OEM unlock required?
Hello! I'm just about to flash my Dad's A3FU with Lineageos 16 (which I use on my own phone), but something is unclear to me: there is no OEM unlock option in the dev menu. Does it means that I should not worry about it and I can simply flash anything I want (with heimdall, manually compiled because Debian's precompiled version seems to have a bug that prevents it from connecting to the phone)?
Thanks a lot!
Mathias
PS: by the way, any news on the sound routing issue for the speaker phone?
My A3FU hasn't got a OEM-unlock option, too (maybe it is like this in general). Never mind, just confirm "USB-Debugging". That's enough! (At least it was with me like that).
Make sure you've downloaded the OS from the link above!
I had no OEM unlock option either and just flashed LOS without problems. That's the only thing i can tell about this.
Regarding the sound problem: The Samsung sound driver implementation is horribly outdated and doesn't work properly anymore (just affects the external speaker on the backside). The userspace part is closed source and there seems to be some kind of race condition or timing problem. What people have done on other devices with same hardware is they patched the 'mute' function (or something similar) in the closed source HAL blobs so the speaker is always on. That leads to several side effects like the speaker is always-on as well when calling and similar. It's a dirty hack and unfortunately the only thing we have currently. I do not really like that. Instead i'm going to overhaul the kernel driver. I have the new codec driver running already. The next part is to glue it all together and bring it to userspace.
bavay said:
Hello! I'm just about to flash my Dad's A3FU with Lineageos 16 (which I use on my own phone), but something is unclear to me: there is no OEM unlock option in the dev menu. Does it means that I should not worry about it and I can simply flash anything I want (with heimdall, manually compiled because Debian's precompiled version seems to have a bug that prevents it from connecting to the phone)?
Thanks a lot!
Mathias
PS: by the way, any news on the sound routing issue for the speaker phone?
Click to expand...
Click to collapse
A3FU doesn't have locked bootloader at all.. so no OEM unlock option needed :laugh:
DualJoe said:
I had no OEM unlock option either and just flashed LOS without problems. That's the only thing i can tell about this.
Click to expand...
Click to collapse
Jesus, even OP doesn't know that... wasted..
Good luck :laugh:
P.S.: but it will trigger knox count (aka warranty from 2015 ) - useless these days
Great!
So, for me too the rom works great so far. But I have one more question: I've seen that SE-Linux is not enabled. Is it because this is a development rom and you need more permissions debug information, is it because of some other issues or is it related to a LineageOs misconfiguration (such as this issue)? Or in short, can I just revert the kernel boot parameter to get it to "enforced" and it would work?
Thanks a lot,
Mathias
You cannot enforce SELinux because your kernel is build with permissive policy.
bavay said:
So, for me too the rom works great so far. But I have one more question: I've seen that SE-Linux is not enabled. Is it because this is a development rom and you need more permissions debug information, is it because of some other issues or is it related to a LineageOs misconfiguration (such as this issue)? Or in short, can I just revert the kernel boot parameter to get it to "enforced" and it would work?
Thanks a lot,
Mathias
Click to expand...
Click to collapse
$ sudo setenforce 1
Hi!
Thank you for the ROM! am just flashing so i cannot refer to it.
May I ask when can we expect sound support and whether we get nfc?
Thanks again
It's not working. Needs help.
Hi. I've used TWRP 3.X and LineageOS 16.X before in my SGA300FULTE before. But other roms or recoveries didn't work. Only 2 TWRP 3.X and the LineageOS 16.X by @vl_w strangely seemed to work so I used them as daily driver. But these 2 became old and I needed new latest updated Roms and Recoveries. So I searched for new ones but found none. I'm glad when I found your this post a few days ago. Your TWRP 3.3.X is working somehow but the LineageOS 16.X isn't working. When I flash it from the Recovery and I reboot my device [ To remind you I always do full clean flash with wipe dalvik, cache, data, system and sometimes even internal storage ] it flashes and reboots and shows the Samsung stock Boot Logo/Splash Screen and the LineageOS also boots till the LineageOS boot animation. And it bootloops [ Either it keeps booting and showing boot animation forever or the screen gets dimmed with the boot animation completely freezed with the boot animation stopped ].
I was waiting for this latest TWRP 3.X and LineageOS 16.X. But It's very bad and sad thing that they're not working in my device . :crying: I thought I'd use them like before as daily driver. But I'm disappointed now because of this. I wish it'd work. And I wish this device SGA300FULTE had more developers working with more things and also make it Project Treble supported. I'm also trying to experiment with this to make it Project Treble supported. I'm eagerly waiting for your reply. I hope you can assist me with this. Thanks.
Alex Mahdi Ghost Infinity said:
Hi. I've used TWRP 3.X and LineageOS 16.X before in my SGA300FULTE before. But other roms or recoveries didn't work. Only 2 TWRP 3.X and the LineageOS 16.X by @vl_w strangely seemed to work so I used them as daily driver. But these 2 became old and I needed new latest updated Roms and Recoveries. So I searched for new ones but found none. I'm glad when I found your this post a few days ago. Your TWRP 3.3.X is working somehow but the LineageOS 16.X isn't working. When I flash it from the Recovery and I reboot my device [ To remind you I always do full clean flash with wipe dalvik, cache, data, system and sometimes even internal storage ] it flashes and reboots and shows the Samsung stock Boot Logo/Splash Screen and the LineageOS also boots till the LineageOS boot animation. And it bootloops [ Either it keeps booting and showing boot animation forever or the screen gets dimmed with the boot animation completely freezed with the boot animation stopped ].
I was waiting for this latest TWRP 3.X and LineageOS 16.X. But It's very bad and sad thing that they're not working in my device . :crying: I thought I'd use them like before as daily driver. But I'm disappointed now because of this. I wish it'd work. And I wish this device SGA300FULTE had more developers working with more things and also make it Project Treble supported. I'm also trying to experiment with this to make it Project Treble supported. I'm eagerly waiting for your reply. I hope you can assist me with this. Thanks.
Click to expand...
Click to collapse
Alright, let's go in parts:
1) It is very likely that this build is as old as those published by @vl_w, it would not be much of being surprised the problems that this ROM brings.
2) No one, not even the one who published this ROM, has done any further research on GitHub (where development is done for the MSM8916) on what happened to development for Android 9.
3) There are already Pie builds made for some phones like Grand Prime (as expected [additional note] the weak or no development for fortuna3g or serranove) with changelogs in late 2018 or mid 2019, I don't remember exactly, Still, it was not wrong to consult at least here with some of the developers for such phones on topics related to driver compatibility mainly, as long as libraries and other components are tested in order to see if work something or not.
4) At least with a33g it is impossible to have a generic image because there is no way to create a partition from which it is required to make it work. An average developer for this model simply won't want to work on it since, equally whether or not there's a chance to have a dedicated partition, Creating such a ROM is said to be very difficult.
5) It is highly unlikely that we will have a sufficiently new Android Pie ROM available, much less for the A300FU (which in theory among all models is the one that receives the most support), the most probable but not totally certain reason (due to some mistake) is that the published changes on LineageOS are not available on the final ROM, i.e The battery icon setting.
6) There is no one capable or willing to try again the construction of a ROM (for each version of the A3, of course) with the latest updates from each repository for, In addition to discarding the theory of the old versions, to advance a little more in the mediocre development that there is, even being reporting every moment to GitHub.
7) It is believed (as I did) that a much easier way is to port a ROM ... with Brotli it is an impossible mission, with that I summarize everything.
@DualJoe
Can we expect an update that fixes sound issue? It's basically the only thing that makes this ROM unusable, it would be great if you could manage to get around it.
At the moment there's nothing i can do. There are too many open questions regarding the manual kernel driver implementation and the alternative method (how ppl did it in the past) with proprietary blobs and newer CAF drivers is unreliable on LOS16. It works properly on one boot and on the next it's gone.
DualJoe said:
At the moment there's nothing i can do. There are too many open questions regarding the manual kernel driver implementation and the alternative method (how ppl did it in the past) with proprietary blobs and newer CAF drivers is unreliable on LOS16. It works properly on one boot and on the next it's gone.
Click to expand...
Click to collapse
Hi,
Thank you for the information !
Maybe try to build android 10
Have a nice day
{
"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...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
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! As always, 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 addressed it already. Especially if you're even close to new at this.
2) 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.
3) 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.
Install Instructions:
You should start off with the latest OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery using
Code:
fastboot boot kebab-YYYYMMDD-HHMM-recovery.img
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-kebab-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
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!
Ive so been waiting for this for so long... Big big fan.
The only thing that could be better than Carbon coming to OnePlus 8T would be if Resurrection Remix came..
God.. old school rom names.. <3
hope you can lease two roms.one is no gapps,the other has the gapps!
niceee running awesome
Hi,
Flash with Fastboot ROMinstaller, reboot recovery install mind the gapps, reboot recovery install Magisk 23.
Reboot, all is running fine !
testflight app said:
hope you can lease two roms.one is no gapps,the other has the gapps!
Click to expand...
Click to collapse
The install instructions include a step on how to install GApps (MindTheGapps recommended). There is no reason for us to release seperate builds for that, especially as the builtin updater as well as CarbonRecovery keep the GApps installed during updates.
Myself5 said:
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...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
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! As always, 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 addressed it already. Especially if you're even close to new at this.
2) 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.
3) 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.
Install Instructions:
You should start off with the latest OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery using
Code:
fastboot boot kebab-YYYYMMDD-HHMM-recovery.img
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-kebab-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
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!
Click to expand...
Click to collapse
FINALLY!!!!!! I have been waiting for this rom to come on the 8T!!!! THANK YOU SOOOOOO MUCH DEVS ;-)
i ve error while installing this rom on pc after enter adb sideload CARBON-CR-9.0-R-WEEKLY-kebab-YYYYMMDD-HHMM.zip say : adb: failed to read command: no error, and on phone failed to read 16777216 bytes data at offset .... (with several long number )
angus6969 said:
i ve error while installing this rom on pc after enter adb sideload CARBON-CR-9.0-R-WEEKLY-kebab-YYYYMMDD-HHMM.zip say : adb: failed to read command: no error, and on phone failed to read 16777216 bytes data at offset .... (with several long number )
Click to expand...
Click to collapse
Check Drivers and see if ADB is updated, also make sure the file you downloaded isn't corrupted.
already checked and re-downloaded the ROM ..flash from twrp is ok.. only by adb error..is it possible that one of the 2 slots is corrupt?
angus6969 said:
already checked and re-downloaded the ROM ..flash from twrp is ok.. only by adb error..is it possible that one of the 2 slots is corrupt?
Click to expand...
Click to collapse
Mine installed perfectly when using the rom installer method after extracting the images with the payload dumper. Try that method via fastboot. Also use the Basic NikGapps. That wont give errors while syncing your google accounts (if you desire to use gapps).
Myself5 said:
The install instructions include a step on how to install GApps (MindTheGapps recommended). There is no reason for us to release seperate builds for that, especially as the builtin updater as well as CarbonRecovery keep the GApps installed during updates.
Click to expand...
Click to collapse
thanks
Hello
First of all, praise for the successful Rom
I still have one question, will you implement AOD?
Zweeni1 said:
Hello
First of all, praise for the successful Rom
I still have one question, will you implement AOD?
Click to expand...
Click to collapse
AOD in AOSP os Ambient Display which is working great in CarbonROM.
EmperorEye1993 said:
AOD in AOSP os Ambient Display which is working great in CarbonROM.
Click to expand...
Click to collapse
oops I completely overlooked it.
I'm using this rom lately, it's running great !! Thank you !!
I got Carbon on my Mi Pad 4 Plus, which would be a bummer without the great work of custom ROM devs like the Carbon crew.
Now I thought about giving my 8T Carbon too. Got some questions before doing so.
What camera is included in Carbon for the 8T? The original OnePlus camera?
Does Carbon on 8T have the dialer/SMS/contacts system apps like on the Mi Pad 4 - I mean the system apps from AOSP (?) or is it the bloated Google apps from Google Play?
Did anybody flash Carbon on 8T and is using another custom Kernel, if yes - which and how's it?
I guess flashing flame Gapps on this would be OK?
t-ryder said:
I got Carbon on my Mi Pad 4 Plus, which would be a bummer without the great work of custom ROM devs like the Carbon crew.
Now I thought about giving my 8T Carbon too. Got some questions before doing so.
What camera is included in Carbon for the 8T? The original OnePlus camera?
Does Carbon on 8T have the dialer/SMS/contacts system apps like on the Mi Pad 4 - I mean the system apps from AOSP (?) or is it the bloated Google apps from Google Play?
Did anybody flash Carbon on 8T and is using another custom Kernel, if yes - which and how's it?
I guess flashing flame Gapps on this would be OK?
Click to expand...
Click to collapse
Camera: "Snap", the Opensource camera app from CAF (as known from Lineage or OmniROM)
Yes. All official builds only contain the opensource AOSP apps.
Can't answer that
Yes. See the install instructions on how to do that.
Myself5 said:
Camera: "Snap", the Opensource camera app from CAF (as known from Lineage or OmniROM)
Yes. All official builds only contain the opensource AOSP apps.
Can't answer that
Yes. See the install instructions on how to do that.
Click to expand...
Click to collapse
Thank you for the reply, Sir.
I guess then it's good to have gCam and Google photos to have a decent camera. Or is "snap" any good?
Already getting annoyed with Oxegen OS with issues that seem to follow me from my 6T
How's the bluetooth on 8T AOSP?
Also since this is Android 11 does it have that power menu with all the smart home junk I have grown attached to?