{
"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:
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"
}
Team OctOs presents Oct-L.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Frequently Asked Questions
Q: Is this Android 5 (Lollipop)?
A: Yes, this is Android 5.1.1
Q: What code is Oct-L based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code.
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-L.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favourite Android 5 based GApps package
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
The Oct-L ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
* OctOS ROM Downloads
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-L available on our GitHub repositories.
Unless otherwise specified, all Oct-L builds use the device's stock CyanogenMod 12.1 kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://review.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Follow Us at the various websites below!
XDA:DevDB Information
OctOS, ROM for the OEM Cross Device Development
Contributors
ujwal.p
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2015-08-12
Created 2015-08-12
Last Updated 2015-09-17
Reserved
More Screenshots in the dedicated Screenshots TAB
Labeled as Stable. Is that so? Anyways, thanks for the Rom.
@ujwal bro please make a build for sprout 8 too please.... _/\_
Shuvo_bd said:
Labeled as Stable. Is that so? Anyways, thanks for the Rom.
Click to expand...
Click to collapse
Yes u heard it right, its stable build
Sent from my Mi-498 using Tapatalk
abinsur279 said:
@ujwal bro please make a build for sprout 8 too please.... _/\_
Click to expand...
Click to collapse
Will take time as, most of the sprout8 builds are not popular and this rom takes 2 hr to build and on top of that im a student.
Sent from my Mi-498 using Tapatalk
ujwal.p said:
Will take time as, most of the sprout8 builds are not popular and this rom takes 2 hr to build and on top of that im a student.
Sent from my Mi-498 using Tapatalk
Click to expand...
Click to collapse
Ok bro, i appreaciate your work, but when you have time please make a build for it too [req]:good:
abinsur279 said:
Ok bro, i appreaciate your work, but when you have time please make a build for it too [req]:good:
Click to expand...
Click to collapse
Yeah, I will
Sent from my Mi-498 using Tapatalk
Bro Currently I am using your awesome Rom . Really its stable .
Big thanks for your hard work
Choritrowhin said:
Bro Currently I am using your awesome Rom . Really its stable .
Big thanks for your hard work
Click to expand...
Click to collapse
There is a "thanks" button for appreciating my work :3
Sent from my A0001 using Tapatalk
Thread updated with new build, very fluid and steady
Hit here:-
https://www.androidfilehost.com/?fid=24052804347810298
DATA/3G SIM Switching
hello>>>>
i appreciate your hard work. the rom is too smooth.
still smoth with 5 modules in xposed.
it would be very good anjd great if you fixed the Data/3g sim switching bugs
Nice Work.... Lovely And Smooth ROM
I appeciate your hard works.
I found your rom is very smooth even if i have 9 xposed modules running.
I m currently using your latest build.
i love the way that you keep all customization in Tentacles. its easy to navigate.
it would be better if you added some other features like Gesture Lock Screen, App Side Bar, System Animations with duration, Data Traffic Monitors, screenshots delay etc.
moreover, your ROM is the best ROM i have ever used.
meprakash_pyc said:
hello>>>>
i appreciate your hard work. the rom is too smooth.
still smoth with 5 modules in xposed.
it would be very good anjd great if you fixed the Data/3g sim switching bugs
Click to expand...
Click to collapse
Sim switching is an issue which cm has for our device, and the latest cm changes has made it difficult to patch the files, but anyway, il try my level best
Sent from my A0001 using Tapatalk
meprakash_pyc said:
I appeciate your hard works.
I found your rom is very smooth even if i have 9 xposed modules running.
I m currently using your latest build.
i love the way that you keep all customization in Tentacles. its easy to navigate.
it would be better if you added some other features like Gesture Lock Screen, App Side Bar, System Animations with duration, Data Traffic Monitors, screenshots delay etc.
moreover, your ROM is the best ROM i have ever used.
Click to expand...
Click to collapse
My pleasure
For feature requests, head on to their g+ community and request there, the team would be obliged to work on it
Sent from my A0001 using Tapatalk
It is bit offtopic I appreciate your passion. How do you post one build after another of different ROMs.My data pack gets emptied on downloading ROMs only.
rohitsonone said:
It is bit offtopic I appreciate your passion. How do you post one build after another of different ROMs.My data pack gets emptied on downloading ROMs only.
Click to expand...
Click to collapse
Unlimited internet (BSNL) :3
Sent from my A0001 using Tapatalk
New build is up, links updated in OP.
Else hit here,
https://www.androidfilehost.com/?fid=24052804347817516
Xposed and Lucky patcher
ujwal.p said:
New build is up, links updated in OP.
Else hit here,
https://www.androidfilehost.com/?fid=24052804347817516
Click to expand...
Click to collapse
i flashed xposed framework and installed 8 modules. all are working properly. the use of xuimod makes the rom a little bit slow and laggy. but when i apply custom patch from lucky patcher (e.g. Greenify), the result comes like this "patch already done or pattern error and failed". and after closing this when i open an app it automatically closes without any popup message. and i have to reboot my device. what's the problem?????
meprakash_pyc said:
i flashed xposed framework and installed 8 modules. all are working properly. the use of xuimod makes the rom a little bit slow and laggy. but when i apply custom patch from lucky patcher (e.g. Greenify), the result comes like this "patch already done or pattern error and failed". and after closing this when i open an app it automatically closes without any popup message. and i have to reboot my device. what's the problem?????
Click to expand...
Click to collapse
Get me a log.
{
"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"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-M.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
Weekly builds can be found here, https://www.teamoctos.com/weekly-builds/
We have Gapps here.
Aroma (659.6 mb)
http://opengapps.org/?download=true&arch=arm64&api=6.0&variant=aroma
Full (484 mb)
http://opengapps.org/?download=true&arch=arm64&api=6.0&variant=full
Mini (239 mb)
http://opengapps.org/?download=true&arch=arm64&api=6.0&variant=mini
Micro (136.2 mb)
http://opengapps.org/?download=true&arch=arm64&api=6.0&variant=micro
Nano (100.3 mb)
http://opengapps.org/?download=true&arch=arm64&api=6.0&variant=nano
Pico (58.1 mb)
http://opengapps.org/?download=true&arch=arm64&api=6.0&variant=pico
These are fully working 6.0 MM gapps built and maintained by OpenGApps. All credit goes to Opengapps, please show them some support!
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!
You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie
TBO thread http://forum.xda-developers.com/showthread.php?p=41545802
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes, this is Android 6.0.x
Q: What code is Oct-M based on?
A: Starting with Oct-M, we've rebased OctOs on the CyanogenMod 13 code.
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
Q: Why isn't there XYZ feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But XYZ and all the others have...
A: ROM developers build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file, MD5 file & Open gapps (arm64) linked above
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock CyanogenMod 13 kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
Above is our hidden menu. It can be accessed 3 different ways: "Tentacles" in app drawer, quick settings tile, or by pressing settings/about phone/OctOS build date.
MORE PICS OF OUR FEATURES: https://copy.com/9V9skpmRVsRaa6mx
Click to expand...
Click to collapse
XDA:DevDB Information
Oct-M, ROM for the T-Mobile LG G4
Contributors
canodroid15, cjkacz, joryb, bthorne79, hedwig34
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Version Information
Status: Testing
Beta Release Date: 2016-02-20
Created 2016-02-21
Last Updated 2016-08-26
Runs so smooth. Thanks for da great work guys. ????
canodroid15 said:
Team OctOs presents Oct-M.
Click to expand...
Click to collapse
like i mention before in other thread CM base related rom, is the Cam in this Rom as good as LG Stock Cam app?
DrakenFX said:
like i mention before in other thread CM base related rom, is the Cam in this Rom as good as LG Stock Cam app?
Click to expand...
Click to collapse
An impossibility.
Wow bro I have to take my hat to you just for the fact that this is one of the best OP first post for any ROM. Very detailed, explained and well put instructions. As for the ROM I will try it thanks for the share
Sent from my LG-H811 using Tapatalk
Excited about this. Missed OctOS since I gave up the galaxy note 2.
Thanks for checking us out! Feel free to drop by our gplus community and say hi!
https://plus.google.com/communities/102188586220747781076
Sent from my Nexus 6 using XDA Free mobile app
TecknoFreak said:
Wow bro I have to take my hat to you just for the fact that this is one of the best OP first post for any ROM. Very detailed, explained and well put instructions. As for the ROM I will try it thanks for the share
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thanks, we as a team take a very professional approach. ?
Been running this for a week now. Stable build! No issues to report.
Doze works great. 6 hrs off charger, still read 100%level.
Thanks to the maintainer.
Super stable build! Battery life amazing on just standard kernel. Any customs you would recommend to enhance this mod and make it even better!?
Sent from my LG-H811 using Tapatalk
Do you need to already be on MM to flash this? I am on rooted stock 5.1 10n. Thanks.
patcal said:
Do you need to already be on MM to flash this? I am on rooted stock 5.1 10n. Thanks.
Click to expand...
Click to collapse
Yes
sabrdawg said:
Yes
Click to expand...
Click to collapse
Thanks.
I remember OctOS back when I was using the s3! Ran great no problems then, looking forward to trying this out when I have the time to clean install a new rom! Appreciate the build im sure it will be stable and quick~
I think I did something wrong. Downloaded the 2/27 weekly build, dirty flashed on existing system, which was a clean install of 2/20.
Got missing Google services errors. Flashed nano gapps again, and everything crashed.
Wiped, installed 2/27 clean, all good.
Was this caused by the partition size change I saw in the changelog?
cjkacz said:
Thanks for checking us out! Feel free to drop by our gplus community and say hi!
https://plus.google.com/communities/102188586220747781076
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Wow, I Got to tell you. Two days ago I was looking around in some draws with old phones, just a bunch of tombstones and came across my old Samsung galaxy S3 which I semi-bricked . So what the Hell Right. why not have some fun and found Team-OctOs For SGH-T999. And wOw Marshmallow on Galaxy S3 !! So fast and clean. My wife took it back after she saw and said why did you do this Before? haha
So All I have to say if it was to good on that Samsung galaxy S3 , Then I Have to flash this ROM on my LGG4 H811 right now.
Thanks Team OctOS :good:
Qverse said:
Wow, I Got to tell you. Two days ago I was looking around in some draws with old phones, just a bunch of tombstones and came across my old Samsung galaxy S3 which I semi-bricked . So what the Hell Right. why not have some fun and found Team-OctOs For SGH-T999. And wOw Marshmallow on Galaxy S3 !! So fast and clean. My wife took it back after she saw and said why did you do this Before? haha
So All I have to say if it was to good on that Samsung galaxy S3 , Then I Have to flash this ROM on my LGG4 H811 right now.
Thanks Team OctOS :good:
Click to expand...
Click to collapse
Yep I was using Oct back when I had my s3 and it really brought new life back into the device after carrier support was dropped. Love how light and functional the rom is while still having great features.
@tiskewlio, @Qverse, Glad to see you guys here! Hope you'll enjoy Oct-M on this device as much as you guys did back then on the S3 ? I'm actually still using my S3's d2att & d2vzw. Both are running in beast mode on Oct-M ? Welcome back to OctOs fellas!
Most stable AOSP rom I've tested so far and the battery life OMG, it's amazing. The thing that I miss the most is the double tap anywhere at the lockscreen to sleep.
pedrito0906 said:
Most stable AOSP rom I've tested so far and the battery life OMG, it's amazing. The thing that I miss the most is the double tap anywhere at the lockscreen to sleep.
Click to expand...
Click to collapse
After testing this rom for a bit it's not bad, pretty quick and fast but my battery hasn't been that great. It's been two days now the battery should have settled but I'm getting less than 3hr SOT while I usually get 4. The lack of DT2S is slightly annoying after getting used to the stock rom but it's also not present in the CM builds i've tried but got the feature back through gravity box. Hope that helps!
---------- Post added at 09:01 PM ---------- Previous post was at 08:53 PM ----------
canodroid15 said:
@tiskewlio, @Qverse, Glad to see you guys here! Hope you'll enjoy Oct-M on this device as much as you guys did back then on the S3 I'm actually still using my S3's d2att & d2vzw. Both are running in beast mode on Oct-M Welcome back to OctOs fellas!
Click to expand...
Click to collapse
It's great to be back! Might stay with this rom for a few weeks or till I get bored. Nothing against it just like to flash different roms to test and support the devs by providing feedback and whatnot. This one is really snappy, missing a few features and customizations but it's probably for the sake of stability and lightweightness so it's fine. Hopefully the battery settles down because i'm getting an hour or more less than I usually get.
CarbonROM is an aftermarket firmware based on the CyanogenMod and Android Open Source Project.
{
"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"
}
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 at, build, and use our code on CarbonTEAM GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
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! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Sources:
My own device source based off of kyasu's
Kyasu's device source
Note that both sources have the base for the roomservice.xml, so just copy paste from mine and you should be good to go
Downloads:
ROM
Gapps
SuperSU
Big thanks to @kyasu for providing device sources, I did modify them somewhat to make them compatible with building carbonrom. Huge thanks to LineageOS for providing some of the necessary files needed to compile!
Seems to run great! Feedback is appreciated.
What works:
- Wifi
- Bluetooth
- NFC
- Airplane Mode
- USB Tethering
- Sound
- Camera
- Video recording
- Microphone
- Root
- SMS & Call (and data I assume)
- MTP
- Idk you tell me
What doesn't work:
- Reboot recovery option from reboot menu
- Idk you tell me
XDA:DevDB Information
CarbonROM 5.1, ROM for the Samsung Galaxy S4
Contributors
ramiabouzahra, kyasu
Source Code: http://github.com/CarbonROM/android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest bootloader
Version Information
Status: Testing
Created 2017-06-15
Last Updated 2017-06-21
Changelog
-20170622 build: Fixed simcard issue. Camera app is back. Synced with the latest sources.
-20170620 build: Fixed sound issue. Synced with the latest sources.
- 20170615 build: Initial release! Sound is being actively worked on to be fixed in next release.
Older versions:
20170615 build: http://www.mediafire.com/file/2ksmg....1-MOO-UNOFFICIAL-ks01ltexx-20170614-2231.zip
20170620 build: http://www.mediafire.com/file/gbn78....1-MOO-UNOFFICIAL-ks01ltexx-20170620-2236.zip
Thank you! I will test later today. I tried dirty flashing on kyasu's lineageos 14.1, because I am lazy. Did not work (surprising right?).
PixelChris95 said:
Thank you! I will test later today. I tried dirty flashing on kyasu's lineageos 14.1, because I am lazy. Did not work (surprising right?).
Click to expand...
Click to collapse
Haha, you get a medal for trying though
I tested the rom for a little bit. No obvious major bugs, but since it is based on lineageos I assume it got the known lineageos bugs (which are not many though). Compared to lineageos this rom has of course more customization options (substratum and lots of settings) and a better browser (AdBlock :good: ). One little bug I found: Rebooting to recovery from power menu does not work.
Finally got the time to flash it, sound doesn't work as expected (I had some issues with that during compiling), I'll try a full recompile today and see if it fixes anything
RAZERZDAHACKER said:
Finally got the time to flash it, sound doesn't work as expected (I had some issues with that during compiling), I'll try a full recompile today and see if it fixes anything
Click to expand...
Click to collapse
Seems like I should have tried to play a song before writing "there are no major bugs"
PixelChris95 said:
Seems like I should have tried to play a song before writing "there are no major bugs"
Click to expand...
Click to collapse
Yup, and now I am back at fixing compiler errors haha, we'll see how this build goes (I really need to document how I fix these errors for future reference)
PixelChris95 said:
I tested the rom for a little bit. No obvious major bugs, but since it is based on lineageos I assume it got the known lineageos bugs (which are not many though). Compared to lineageos this rom has of course more customization options (substratum and lots of settings) and a better browser (AdBlock :good: ). One little bug I found: Rebooting to recovery from power menu does not work.
Click to expand...
Click to collapse
Oh yes that one, I had to take a little shortcut to get the ROM compiled. I'll see what I can do
Update: Spoke to the CarbonROM devs, they said there was a new commit that should fix this issue. I'll have a compiled rom tomorrow and I'll test if sound works
Update:
http://www.mediafire.com/file/gbn78....1-MOO-UNOFFICIAL-ks01ltexx-20170620-2236.zip
- Fixed sound issue
- Synced with the latest
Do a backup before flashing, since this is still "beta".
Full wipe before flashing.
Root and Gapps in the OP.
Happy flashin
Can someone confirm that simcard is working in the latest update?
RAZERZDAHACKER said:
Can someone confirm that simcard is working in the latest update?
Click to expand...
Click to collapse
Simcard is not working for me. Furthermore the camera app disappeared for some strange reason.
PixelChris95 said:
Simcard is not working for me. Furthermore the camera app disappeared for some strange reason.
Click to expand...
Click to collapse
Gosh dang it hahaha, fixed one thing messed up another. I think I know what happened and I'm compiling a new one right now for testing
Update:
- Camera app fixed p)
- Sim card is now detected, hurray!
I don't have the fastest uploading speed (I'm on vacation in Lebanon, speed is around 300kb/s) and I want to go through the ROM for a couple moar bugs and roaches (ie, I haven't tested the reboot to recovery etc) but once all that's complete, it should be good to go for a daily driver (I don't know if you should trust me, I used a beta version as a daily once haha).
That's the update so far
Update:
See last post for changes
Link: In OP and here
No updates?
Thanks
Envoyé en utilisant Tapatalk
jeepcook said:
No updates?
Thanks
Envoyé en utilisant Tapatalk
Click to expand...
Click to collapse
I was thinking of updating again, but I haven't gotten any response from my last build so I assume everything is working :/ Plus, I'm in Lebanon where the internet is kB/s but I was planning on updating the source the 1rst of august. Do you have any bug reports you want to send?
ramiabouzahra said:
I was thinking of updating again, but I haven't gotten any response from my last build so I assume everything is working :/ Plus, I'm in Lebanon where the internet is kB/s but I was planning on updating the source the 1rst of august. Do you have any bug reports you want to send?
Click to expand...
Click to collapse
No bugs, but just to have the last commits ...
Have a good trip in Lebanon!!
{
"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"
}
Who's back? We're back.
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... and at CarbonROM Gerrit.
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! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
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) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Downloads:
Get CarbonROM
GitHub
Gerrit
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 Sony Xperia XZ
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Nightly
Created 2017-06-20
Last Updated 2018-03-17
Downloadlink doesnt work yet, also cant download from website, verry eager to try this ?? thanks for supporting our phone
Sent from my F8331 using XDA-Developers Legacy app
Wow great thanks
Thanks mate for ur work, will need ur help to compile working lineage kernel contact via pm or @ this discord https://discord.gg/RYejXrw
Will try the rom soon
Ps: new kernel source https://github.com/sonyxperiadev/kernel/tree/aosp/LA.UM.5.7.r1
（ROM Test feedback）
I just installed it Support XZ dual, very good work
1-Install next lock screen to find, the unresponsive after unlocking
2-The fingerprint recognition delay is serious
F8332 support? :crying:
mon73 said:
F8332 support? :crying:
Click to expand...
Click to collapse
yes ，Good job
fastbooking said:
Thanks mate for ur work, will need ur help to compile working lineage kernel contact via pm or @ this discord https://discord.gg/RYejXrw
Will try the rom soon
Ps: new kernel source https://github.com/sonyxperiadev/kernel/tree/aosp/LA.UM.5.7.r1
Click to expand...
Click to collapse
UM5.7 is the 4.4 Kernel. That is WIP and has no device binaries yet.
yang137197 said:
（ROM Test feedback）
I just installed it Support XZ dual, very good work
1-Install next lock screen to find, the unresponsive after unlocking
2-The fingerprint recognition delay is serious
Click to expand...
Click to collapse
Try restarting. I had this issue like once in 20 reboots. After a restart the phone is pretty damn smooth. Using it over my Pixel since some days.
Myself5 said:
UM5.7 is the 4.4 Kernel. That is WIP and has no device binaries yet.
Try restarting. I had this issue like once in 20 reboots. After a restart the phone is pretty damn smooth. Using it over my Pixel since some days.
Click to expand...
Click to collapse
The restart has improved, but there will still be delays
Myself5 said:
UM5.7 is the 4.4 Kernel. That is WIP and has no device binaries yet.
Try restarting. I had this issue like once in 20 reboots. After a restart the phone is pretty damn smooth. Using it over my Pixel since some days.
Click to expand...
Click to collapse
your rom was only 400 mb? is it true?
Using this now instead of omnirom.
Seems better. Less issues, just gonna monitor battery usage over next day of 2 as that's been a huge issue for my XZ so far.
Hopefully this will progress nicely, if so I will donate towards the project, as never use carbon rom before but I like what I see so far.
After install, phone reboot and ask password. I did not set password before.
Omnirom fingerprint sensor work strange, without need to press power button, only touch sensor. How it behaves on a CarbonROM?
lordgamma said:
After install, phone reboot and ask password. I did not set password before.
Click to expand...
Click to collapse
Thats the encryption password equal to the lockscreen password of the ROM you were running before.
If you came from stock it might be necessary that you format /data (wipes internal storage too, backup the stuff using TWRP before).
To do the formatting, go to wipe, select /data, choose filesystem, set to FAT, format. Reboot recovery, format data again, this time select ext4. That assures that the storage is getting completely formatted, not just wiped.
It should really only be needed for the Stock -> AOSP transition.
uglavnom_bezopasni said:
Omnirom fingerprint sensor work strange, without need to press power button, only touch sensor. How it behaves on a CarbonROM?
Click to expand...
Click to collapse
Equal. There is a way to disable that, but so far users always liked that across the Sony devices I supported.
Myself5 said:
Equal. There is a way to disable that, but so far users always liked that across the Sony devices I supported.
Click to expand...
Click to collapse
Me too
Omnirom kernel look like "default", did you do some modifications, modules, kcal... Desperate need a good kenel for AOSP.
I'll try CarbonROM as soon as possible.
uglavnom_bezopasni said:
Me too
Omnirom kernel look like "default", did you do some modifications, modules, kcal... Desperate need a good kenel for AOSP.
I'll try CarbonROM as soon as possible.
Click to expand...
Click to collapse
Havnt messed wirh the Kernel yet, other than preparing some slight adjustments for white balance on my personal build. The kernel shipped in the builds is straight from the source linked though.
Is echoing during voice calls ( callers always mention they can hear their own voice ) & garbled / heavily distorted in-car bluetooth phone calls a known issue, or is it something you'd want a logcat for?
Music over in-car bluetooth is fine.
Hi guys, why no camera2api support here?
Myself5 said:
UM5.7 is the 4.4 Kernel. That is WIP and has no device binaries yet.
Try restarting. I had this issue like once in 20 reboots. After a restart the phone is pretty damn smooth. Using it over my Pixel since some days.
Click to expand...
Click to collapse
Waiting for update optimization
Hi i like how the fingerprint work only touching the sensor but sometime it don't work need to fix
the camera is not working
but over all i love this rom
thank you
{
"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