{
"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"
}
Introduction
I've moved from my OPO to the Z1 and was simply disturbed with the lack of development this device receives, including how Cyanogen Inc & CM treats it like the ugly duckling in the family.
This might not have been received as such by the public, but should you ever give the CM code (device tree, kernel, etc) a look you will know what I mean.
And even if you don't, you will "feel" it while using their software too (half working or missing features, bugs in the kernel, etc).
To right this wrong I've set myself a simple goal, produce a proper CM13 device tree, Marshmallow proprietary repository and finally, clean up the device tree mess that Cyanogen Inc & CM produced for the Z1.
I also throw in a kernel fix or two every once in a while.
As a side-product of this, you guys will (obviously) reap the benefits of this endeavour of mine, namely a properly working CM13 build for the Z1 as well as several other (maybe even more functional) ROMs that will have the opportunity to base their work on mine.
Working Stuff
Dual-SIM
Phone Calls
Phone Call Recording (2-way and unlocked)
Text Messaging
Mobile Data
Sensors
WLAN
EAP-SIM
Bluetooth
Camera (please use Micro OpenGapps, other Gapps sometimes break the camera)
4K Video Recording
1080p Front-Facing-Camera Recording
60FPS Slow-Motion Recording (720p & 1080p only)
GPS
USB / USB-OTG
Doze mode
Double-Tap to Wake
Fingerprint Reader
Capacitive Home Button (Keycodes: 249 = Right Slide, 254 = Left Slide, 158 = Tap, mapped in fpc1020tp.kl)
Tethering
Fixed Headphone Button Voltage Tables (this fixes headphone buttons, like that of the Xiaomi Pistons)
Most (if not all) OS-related stuff
Credits
Steve Kondik (cyanogen) for the bacon device tree & proprietaries (I've used some of these as bring-up reference)
Team CyanogenMod for... well, CyanogenMod
TheCrazyLex for general bring-up advice
JoaoPaulo for his CAF 1.1.3 / Chroma 6.0 kernel and TWRP port
Myself (Coldbird) for the actual bring-up and general bugfixing
Donations
Should you wish to support this (or other projects of mine), please consider donating a few bucks to me via PayPal.
Alternatively, if you like the general idea of bringing proper Android support to badly supported devices (mostly China-Phones), please consider becoming a patron to my "Bring CyanogenMod to China-Phones" movement over at Patreon by pledging a few dollars every month to move me closer to the goal of doing this for a living instead of only squeezing in a few hours every week next to my regular work.
Every support, no matter how tiny, is appreciated.
Donators
Here's a list of all the kind people that have donated to this project in one way or another.
I thank these people for the trust and support they have shown to this project and honor them by listing each and every one of them here.
Dominik Hopf 20€
Jan Hildebrandt 10€
Henk-Jan Zilverberg 10€
Andrew Carmicheal 10£
N J Grayson 10€
MKKLR21 10€
Paolo Hamam 10€
Andreas Körner 10€
Joern Feldhausen 10€
Sergio Avram 10€
Mauro Longano 10€
Jonathan 10€
Javi 10€
tndb 10$
Max Plotnikov 10$
Max 10$
EggZenBeanz 5£
Kai Hellmeier 5€
Moritz Fey 5€
David Mesegar 5€
Sergei Razladin 5€
Manuel Vögel 5€
Wido van der Gaag 5€
fr4nkr0c 5€
Анатолий Чистяков 5$
Kamil Respondek 2€
Downloads
Pre-Requisites
JoaoPaulo's TWRP Recovery (required for flashing)
Marshmallow Firmware, Sensors & Bootloader (required to fix sensor and boot issues with some devices)
Builds
CyanogenMod 13 Builds
Changelogs
Local Manifest (for developers)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="MrColdbird/proprietary_vendor_zuk" path="vendor/zuk" remote="github" revision="cm-13.0" />
<project name="MrColdbird/android_device_zuk_ham" path="device/zuk/ham" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
<project name="ChromaKernel/cKernel" path="kernel/cyanogen/msm8974" remote="github" revision="cm-13.0" />
</manifest>
XDA:DevDB Information
[ROM][6.0.1] Unofficial CyanogenMod 13.0 Nightlies (4K, USB-OTG, OTA, etc), ROM for the Lenovo Zuk Z1
Contributors
MrColdbird, JoaoPaulo
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-12-24
Last Updated 2016-03-02
Wow! Nice work mate
Where to download?
hfutxqd said:
Where to download?
Click to expand...
Click to collapse
Are you read the op?
"Downloads aren't up yet due to the rather low quality of the build (at the moment)."
Why make you Thread whene you dont have a working build? Please read the xda rules and delete this thread for now.
Gesendet von meinem Z1 mit Tapatalk
hfutxqd said:
Where to download?
Click to expand...
Click to collapse
I will post a link once I deem the release stable enough for public testing (after WiFi and RIL is working).
I will work more on it tomorrow and, for those that feel adventurous, I will also post the local manifest required to build it.
MrColdbird said:
Introduction
I've moved from my OPO to the Z1 and was simply disturbed with the lack of development this device receives, including how Cyanogen Inc & CM treats it like the ugly duckling in the family.
This might not have been received as such by the public, but should you ever give the CM code (device tree, kernel, etc) a look you will know what I mean.
To right this wrong I've set myself a simple goal, produce a proper CM13 device tree, Marshmallow proprietary repository and finally, clean up the device tree mess that Cyanogen Inc & CM produced for the Z1.
As a side-product of this, you guys will (obviously) reap the benefits of this endeavour of mine, namely a working CM13 build for the Z1.
Downloads aren't up yet due to the rather low quality of the build (at the moment), however, once I've fixed both WLAN & RIL, I will provide unofficial nightlies via my own little building bot so that you guys won't be missing out on any CM13 updates from now on.
Screenshots
Broken Stuff (at the moment)
RIL / Data
GPS
Most likely a lot more...
Changelog
25.12.2015
Added prebuilt kernel + modules
Fixed WLAN
Donations
Should you wish to donate / buy me a beer / raise my working morale, feel free to send a few bucks via PayPal to [email protected].
Who knows, maybe my next grocery shopping trip can be paid by donation money? That would be marvelous.
XDA:DevDB Information
UNOFFICIAL CM13, ROM for the Lenovo Zuk Z1
Contributors
MrColdbird
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Created 2015-12-24
Last Updated 2015-12-24
Click to expand...
Click to collapse
First of all thank you very much for endorsing this great project. I also wonder why such a good device with CM out of the box hasn't received better support from the community, at the end of the day OnePlus was nobody when the One was released and despite it was very hard to get it, it did see a good support from the beginning.
Second and foremost, as you probably have the skills, why don't you start porting AICP, Carbon, BlissPop or your favourite ROM to the Z1?
Thank you again!!
Because I think a working CM13 tree will benefit people more than yet another 5.1 ROM.
MrColdbird said:
Because I think a working CM13 tree will benefit people more than yet another 5.1 ROM.
Click to expand...
Click to collapse
I understand what you mean but official CM13 support will come, while ROMs are not available yet despite official 12.1 is out...
I think most ROM devs only develop official ROMs if they get the device, at least, carbon ROM when asked for support for my old mi2.
Others offer support but without owning the device, so you can't expect best support.
The thing is lots of devices who are not supported by CM have got 6.0 before supported devices and that make me feel like second division costumer.
Enviado desde mi Z1 mediante Tapatalk
Fixed SIM-Card detection a minute ago, along with phone calls (those two kinda go hand-in-hand).
Next up on the todo list: Mobile Data.
Wish me luck. All changes to the device tree for self-builders can be found on my github "MrColdbird".
Hello, is thé CAMERA2 API implémentée un CM13 ?
frk22 said:
Hello, is thé CAMERA2 API implémentée un CM13 ?
Click to expand...
Click to collapse
The HAL is there for sure but I got no idea whether all the functions work yet.
In general I'm more concerned about getting mobile data working right now.
Great start
Could you push the source code to Github.com?
hfutxqd said:
Could you push the source code to Github.com?
Click to expand...
Click to collapse
It is on github.
Amazing. Thank u very much for this amazing project. Finally we got someone working in cm13! I hope Cyanogenmod and CyanogenOS start working soon...
Enviado desde mi Z1 mediante Tapatalk
PD. If u need any betatesters just ask for it, we will be happy ti help u.
It's good to see some developer has interested to do some marshmallow ROM with ZUK Z1. Thank you very much @MrColdbird really appreciate your hard work.
MrColdbird said:
Introduction
I've moved from my OPO to the Z1 and was simply disturbed with the lack of development this device receives, including how Cyanogen Inc & CM treats it like the ugly duckling in the family.
This might not have been received as such by the public, but should you ever give the CM code (device tree, kernel, etc) a look you will know what I mean.
To right this wrong I've set myself a simple goal, produce a proper CM13 device tree, Marshmallow proprietary repository and finally, clean up the device tree mess that Cyanogen Inc & CM produced for the Z1.
As a side-product of this, you guys will (obviously) reap the benefits of this endeavour of mine, namely a working CM13 build for the Z1.
Screenshots
Broken Stuff (at the moment)
Mobile Data
GPS
Most likely a lot more...
Changelog
26.12.2015
Fixed SIM Card Detection
Fixed Phone Calls
25.12.2015
Added prebuilt kernel + modules
Fixed WLAN
Fixed RIL
Donations
Should you wish to donate / buy me a beer / raise my working morale, feel free to send a few bucks via PayPal to [email protected].
Who knows, maybe my next grocery shopping trip can be paid by donation money? That would be marvelous
Thanks MrColdbird
Click to expand...
Click to collapse
Thank you for your effort!
Related
[ROM] [UNOFFICIAL][LP 5.1.1] CarbonROM (Z00A) - Updated August 9, 2016
{
"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"
}
Another build, compiled from source. But before I get too far...
Code:
#include
/*
* 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
* YOU acknowledge you are doing so at your own risk.
*/
Now that that's out of the way, this is a build of CarbonROM, using the device tree, kernel and advice from @jrior001 and @crpalmer. The current build is based off the latest CyanogenMod commits (and upstream AOSP) available at the time..
NOTICE:
Final build coming.
As work with Nougat begins, I will need to switch over to the MM bootloader. I won't be going back (downgrading) to check builds. For OctOS, as that is MM anyway, I can begin special builds (reliant on the MM bootloader) once I become established. For Carbon LP, it means the end of the road.
The September Android Security Bulletin should filter down to LP in about a week. Once that is done, I will crank out the final build, test, and post. Device-identity-wise, the only difference between the upcoming build and the one previous is the fix to the "off-path TCP" exploit. The ASB will have other fixes, but to the ROM instead (which is why I prefer to wait for the ASB).
Thank you for all the support. Cheers.
SCREENSHOTS:
One tab over
WHAT WORKS:
Powers on
Phone calls and texts
Mobile data (later builds)
Torch
Charges
MTP
Play Store
WHAT DOES NOT WORK:
GPS works, but does not seem to lock on out-of-the-box. Download your country's gps.conf and replace.
Doubtful NFC will work, as it does not look like that functionality is built into CarbonROM (missing nfc_enhanced.mk).
A random reboot was detected, at which point mobile data was lost. Toggle airplane mode to restore data.
As this ROM shares the same device tree as CM, this will share the same flaws. Otherwise, please tell me.
DOWNLOAD:
Mirror (AndroidFileHost)
GAPPS:
OpenGApps -or-
[AOSP] [X86] [Gapps] [5.1.X] [Zenfone Gapps]
INSTRUCTIONS:
Download ROM above, and a GApps package
Save/push files to your (External) SD card (preferably in the root folder where you can find it later)
Reboot into recovery ("adb reboot recovery")
Nandroid/Back up device (optional, but highly recommended)
Wipe cache and data/factory reset (unless updating from previous CarbonROM version)
Install ROM and GApps
Wipe Dalvik cache
Reboot
Enjoy!
CREDITS:
jrior001
crpalmer
deadman96385
CyanogenMod
CarbonDev (incl. Christian Oder)
Niropa
rirozizo
NSLUG
Did I miss anything? I appreciate the feedback, and any thanks as well!
XDA:DevDB Information
[ROM] [UNOFFICIAL][LP 5.1.1] CarbonROM (Z00A), ROM for the Asus ZenFone 2
Contributors
joel.maxuel
Source Code: https://github.com/carbon-z00a
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-08-07
Last Updated 2016-09-10
Other Info...
For those following along....
Project GitHub: https://github.com/carbon-z00a (complete fork of CarbonROM LP with ZF2 device projects)
LOCAL MANIFEST:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cr-z00a"
fetch="https://github.com/carbon-z00a"
revision="lp5.1.1" />
<remote name="cm-z00a"
fetch="https://github.com/carbon-z00a"
revision="cm-12.1" />
<remote name="muppet"
fetch="https://github.com/TheMuppets"
revision="cm-12.1" />
<remote name="cyanogenmod"
fetch="https://github.com/CyanogenMod"
revision="cm-12.1" />
<!-- CM-ZENFONE2 DEVICE PROJECTS -->
<project name="android_device_asus_Z00A" path="device/asus/Z00A" remote="cr-z00a" />
<project name="android_device_asus_mofd-common" path="device/asus/mofd-common" remote="cm-z00a" />
<project name="android_kernel_asus_moorefield" path="kernel/asus/moorefield" remote="cm-z00a" />
<project name="proprietary_vendor_asus" path="vendor/asus" remote="muppet" />
</manifest>
CHERRY PICK(S):
Code:
None.
Make a new folder for and then initialize the build tree:
Code:
mkdir carbon
cd carbon
repo init -u https://github.com/carbon-z00a/android.git -b lp5.1.1
Copy your Z00A local manifest to ".repo/local_manifests/" (you may need to create the local manifests folder first), and then sync everything:
Code:
cp ../Z00A.xml .repo/local_manifests/
repo sync -f
Complete all the normal steps at this point.
CHANGE LOG:
Besides the project git hub...
CyanogenMod upstream
ZF2-Related Commits
Quick-Charging UI
AOSP upstream
Holy cow, I'm tempted to test this but I will wait for official release '-'
Yay...... Even more ROMS
SenpaiCham said:
Holy cow, I'm tempted to test this but I will wait for official release '-'
Click to expand...
Click to collapse
Official release may be a problem, as you would never get one of those from me - I am not affiliated with CarbonROM, I just like building their stuff.
For it to be official, one of their team members will have to own the device and take in the build themselves - in other words - do a lot more than my kanging (all the "work" for this project is in my second post and the commits in my github - all work I borrowed from somewhere else) - which is why I give credit where it's due.
Awesome work buddy
CM Theme Engine included ?
AL_IRAQI said:
Awesome work buddy
CM Theme Engine included ?
Click to expand...
Click to collapse
I think so - I remember seeing a Themes icon in the app drawer...
And thanks!
Sent from my ASUS_Z00AD
fast charge no work...use back 2.1v charge ok no problem,sorry for my bad English
I ran carbon for almost the entire time I had a Note 2. Fantastic Rom! Thanks for all the work in bringing it to the ZF2
pandan80 said:
fast charge no work...use back 2.1v charge ok no problem,sorry for my bad English
Click to expand...
Click to collapse
Unfortunately I don't have a fast charger to check (as I have the 2GB model), but can you try fast charging when powered off?
I think that was the recent progress with this ROMs older brother (CyanogenMod).
Sent from my ASUS_Z00AD
joel.maxuel said:
Unfortunately I don't have a fast charger to check (as I have the 2GB model), but can you try fast charging when powered off?
I think that was the recent progress with this ROMs older brother (CyanogenMod).
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Fast charging worked for me. I regular charged it and using the round battery indicator the phone charged like 3 % in 5 mins. The battery indicator read the %.
I used the fast charger and when plugged in the battery % changed to "?" while charging. After about 10 minutes I unplugged the charger and it had increased like 20%.
I like the ROM so far but I can't get data working. Sms and calls work but no data. Tried reentering the APN but no luck. Reflashing didn't fix it either. Any ideas?
rivethead23 said:
I like the ROM so far but I can't get data working. Sms and calls work but no data. Tried reentering the APN but no luck. Reflashing didn't fix it either. Any ideas?
Click to expand...
Click to collapse
I will play with it tomorrow to see if I have the same problem, and see what I can dig up. Good task for a rainy Sunday.
EDIT:
Looked at it tonight
Interestingly enough, it picks up all the APN's automatically. Stock never did that. But no mobile data. Could be that I used the CAF version of the hardware_ril project (only because the standard version stalled the device on boot). Most likely, it has t do with Carbon working on their rebase - I built before hearing that they finished that (I have problems accessing their website so I thought maybe they bypassed their G+ page to place it on the news section of their site).
As a result of the current situation, I am unable to try a newer build right now.
Sent from my ASUS_Z00AD
Appreciate the work I hope you can get this ROM working Carbon was fantastic in the past.
Added to index, thanks for your work!
Sorry if this is a stupid question. But for us noobs, can you explain how this is different than the nightly rom?
oijjio said:
Sorry if this is a stupid question. But for us noobs, can you explain how this is different than the nightly rom?
Click to expand...
Click to collapse
Historically (at least with KitKat), CarbonROM was more feature-rich than CyanogenMod (at least, I found).
These days, it's had to say. CarbonROM bases itself off of CM and SlimROMs (and probably others) and the feature set is probably similar. I haven't tried CM 12.1 yet, so I cannot do a real comparison. But since Carbon is still getting their feet on the ground for this version, my bet is things are very similar (the options are just found in different locations).
Sorry, I cannot be more specific. These are features I enabled that seem pretty standard, the two that I think stand out are "App Circle Bar" and "AppBar" (those are two ways of accessing apps without going to home screen or app drawer - just pull from the left or right).
I featured the former in attached.
August 9th Build ...
... but still no mobile data
I did get something different when I cleaned flashed though - see attachment. I didn't get this before, and made me hopeful. Too bad it didn't make any difference in the end.
This version seemed to be stubborn at first. Can dirty flash (as far as I can tell - I did and no problems), but if you clean flash, you will have to power cycle (as in, don't soft reboot) after the first full boot to get service back.
Also, I took a logcat (of enabling data services), I could not find any "E/"'s relating to SIM or anything related to mobile data. So that was a dead end.
CHANGE LOG:
Upstream pull request into local project (android_bootable_recovery)
Some commits to the device tree and vendor info that may have been included in previous build
Unknown upstream changes
rivethead23 said:
Appreciate the work I hope you can get this ROM working Carbon was fantastic in the past.
Click to expand...
Click to collapse
I thought of something, and it was a dead end for me, but can you try downgrading your connection (I forget what the option is called, but it is on the parent page to the APN's), from LTE to 3G? Then reboot (power cycle, do not soft reboot) and see if you got connection.
I am unable to do this as my carrier does 4G only (LTE and fake-4G).
It's a long shot, and it means a slower connection if it does work, but if it does work, it may be a half-decent kludge for now...
That was one of the things I tried to get it to work. I did the following things (might help you eliminate some stuff):
Chose 3G/2G as my connection.
Removed and reinserted the SIM card with phone on (I got message like the one you got but it didn't work)
Removed and Manually put in APN information. (I am on T-Mobile in the USA BTW)
Turned off Phone removed SIM. Booted Phone with no SIM. Inserted SIM.
Copied the APN file (at /etc) from SlimROM (which data works on) and after flashing used TWRP's file manager to put it in the same location before the first boot of a clean Carbon.
To answer another person Carbon ROM has more options than CM, Slim, or PA for the Zenphone 2. Also on my previous phone (Note 2) CarbonRom was rock solid stable fast and good on battery life.
I think I know what the problem is.
android_hardware_ril has two branches: 12.1 and 12.1-caf. I originally pulled the project into my github, patched 12.1 branch, and added the project into my local manifests with the upstream removal included.
That build died at the splashscreen. So then I patched the 12.1-caf branch and changed the local manifest to use that branch instead. It booted, but you know what happened then.
I looked at the master manifest, and it calls on both at the same time, renaming the latter to hardware/ril-caf. Worse, my local manifest, because it removes the upstream ril project, really that should be plural because it attacked both, and I only put one back.
So, local manifest has been altered, synced, and building. Next morning I should have some indication on how it went. Maybe this time tomorrow I will have build three for the week - with working mobile data - uploaded!
Sent from my MeMO Pad 8"
UPDATE:
Guess what I found 3:00 in the morning...see attached clip.
Updated ROM is uploading right now.
CHANGE LOG:
Alteration to local manifest in include both hardware_ril projects
Some commits to android_device_asus_mofd-common and android_hardware_intel_img_hwcomposer (Aug 9th and 10th)
Usual upstream changes
{
"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.
{
"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-N.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Feature List
Substratum rootless theme engine support (must install Substratum from play store)
Tentacles settings!
Pixel Launcher Included
OmniSwitch
Power menu options
Screenshot
Screen record
DPI settings
Status bar time and date options
Status bar network traffic indicator
Status bar notification settings
Quick tile settings
Volume button playback control
Volume button wake
DUI (fling, pulse, smartbar)
Screen record
And much more!!!!
Click to expand...
Click to collapse
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.2
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
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 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-N.
Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)
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 favorite Open Gapps package http://opengapps.org
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 ---
The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
Flash ROM, GApps and any additional .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
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-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
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
Donate to OctOS Development (PayPal)
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
AOSP
Open Gapps
LineageOS
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Team-OctOS!
XDA:DevDB Information
OCT-N, ROM for the Samsung Galaxy S4 Mini
Contributors
jason972000, jason972000, manfromgta
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Created 2017-03-05
Last Updated 2017-04-23
Testers needed
We would like to get each S4 Mini up again for OCT-N.
Thanks to those who already tested, we now have weeklies starting the week of 3/10/17.
Downloads for all four supported variants are at: https://www.teamoctos.com/oct-n-weekly-lineageos-base/
For those using the US Cellular variant, here is an updated TWRP Recovery.
twrp serranolteusc --> https://www.androidfilehost.com/?fid=817550096634751007
** This is also officially supported on twrp.me but only for the serranolteusc. I am currently testing their 3.1.0-0.
All other variants of TWRP can be found on Ne0Zone's thread.
twrp other variants --> https://forum.xda-developers.com/showthread.php?t=2678420
If you post on this thread, please mention which variant/device you have.
Thanks
We need some permission to download the file serranosdd
rookie12 said:
We need some permission to download the file serranosdd
Click to expand...
Click to collapse
They should work now, I had to change them from "restricted" to "public" folders.
Great to see OctOS back up, the unified thread is a good idea, 99% of the issues are common
Flashed will test this whole week thanks for your work serranosdd
Thank you @jason972000
I've flashed OCT-N-M0-7.1.1-20170304-serranoltexx.zip with open_gapps-arm-7.1-nano-20170305.zip and so far no problems at all(a few hours). It seems like a really mature rom, plenty of customizations and no reboots/fc's. I'm impressed.
For anyone wanting a stable nougat rom with pixel launcher, I would recommend it. I'll test it for a few more days for battery life and other things.
I have flashed rom serranodsdd Around 6 hours Ago and its look very mature and stable.
jason972000 said:
We would like to get each S4 Mini up again for OCT-N.
So far, the US Cellular variant has been posted on main website for OCT-N Lineage for the past few weekly builds.
But if you want to see the other variants to start showing up on weekly builds, I need testers to confirm some initial builds are looking good.
Here are links for testers to get the rom from AFH:
rom serrano3gxx --> https://www.androidfilehost.com/?fid=745425885120712660
md5 --> https://www.androidfilehost.com/?fid=529152257862707835
rom serranoltexx --> https://www.androidfilehost.com/?fid=457095661767141983
md5 --> https://www.androidfilehost.com/?fid=817550096634750899
rom serranodsdd --> https://www.androidfilehost.com/?fid=529152257862707912
md5 --> https://www.androidfilehost.com/?fid=529152257862707911
For those using the US Cellular variant, here is an updated TWRP Recovery.
twrp serranolteusc --> https://www.androidfilehost.com/?fid=817550096634751007
All other variants of TWRP can be found on Ne0Zone's thread.
twrp other variants --> https://forum.xda-developers.com/showthread.php?t=2678420
Once I get feedback for each of the GSM variants we can decide if it is time to get them added to the weekly builds.
If post on this thread, please mention which variant/device you have.
Thanks
Click to expand...
Click to collapse
I try 20170304-serrano3gxx zip with opengapps 20170205 and everything ok, no fc, reboots, etc, everything works well (ril, camera, speaker, etc), but the rom does not have a browser, have two file explorer, and does not like pixel launcher, but for me the rom is already stable :good::good:
I return to aokp
Thank you Jason. Great work and great ROM.
Will download and test serranoltexx in a few hours
awesome rom bro
its good that we octos back with nougat.
will test and give you a nice feedback
thanks again
Awesome !!! :victory:
Thx Team OctOS!! :good:
I love this ROM!!
Yeah!!!!
During these 3 days I have been my daily driver and the rom is stable enough ..... Very nice in my opinion. All the features have worked without any problem for me. Thank you for your good work.
One week of testing done.
ROM very stable great ROM for a daily driver like everyone said. I put this ROM after AOKP
This baby is ready to go official
Thank you for your work
I agree with the last two users. Very stable and feature-full. I've used it for almost a week and no issues at all. :good:
noppy22 said:
I agree with the last two users. Very stable and feature-full. I've used it for almost a week and no issues at all. :good:
Click to expand...
Click to collapse
I'm very curious to try this rom. How about battery consumption? [emoji4]
Inviato dal mio GT-I9195 utilizzando Tapatalk
s.goten said:
I'm very curious to try this rom. How about battery consumption? [emoji4]
Inviato dal mio GT-I9195 utilizzando Tapatalk
Click to expand...
Click to collapse
At least as good as AOKP and AICP(7.1.1). IMO nougat is better on battery than android 5 or 6
I noticed on the Oct OS site that we have gone official. Although not on the download list yet.......
Thanks again @jason972000
noppy22 said:
At least as good as AOKP and AICP(7.1.1). IMO nougat is better on battery than android 5 or 6
I noticed on the Oct OS site that we have gone official. Although not on the download list yet.......
Thanks again @jason972000
Click to expand...
Click to collapse
Weeklies are building now and they will include all four serrano devices. Thanks for testing everyone.
I'm running the USC version on an SCH-i435L, and although I had to change my build prop to make it default to Verizon, which is what I use, it works perfectly. (Also no radio built in) I'm not sure what the codename for this particular one is, however, if it's one of the listed ones, I'd be happy to verify it works for you. If it's not one of the listed ones, I can again confirm the USC version works.
One bug I have noticed is that although it was supposedly fixed for the regular S4, the back lights for the back and menu buttons still don't seem to work (at least for me) on the S4 Mini.
Two things I'd love to see added to the kernel, which have been done before for older builds of Android on S4 Mini's, would be fast charge (as seen here) and OTG support. (As seen here)
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"
}
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: