Database Users

[ROM][6.0.1][UNOFFICIAL][WIP] Cyanogenmod 13.0 - SM-T700

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial CyanogenMod 13.0 builds for klimtwifi (SM-T700). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Installation
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Make sure you are on the latest bootloader (Download below)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Install the Google Apps addon package (Optional)
Reboot
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/d....tortel.syslog
Downloads
CyanogenMod:
2/08 Build
2/10 Build
4/4 Build
4/11 Build
5/14 Build
Google Apps:
http://opengapps.org/- thanks to the OpenGapps team!
Latest T700 bootloader (Thanks @Schischu)
Here
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Source:
Kernel: https://github.com/CM-Tab-S/android_kernel_samsung_klimtwifi
Device Tree: https://github.com/CM-Tab-S/android_device_samsung_klimtwifi
Credits:
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)

Bugs:
Camera
My Local manifest this will allow you to build any of the tab s variants
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CM-Tab-S/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallwifi" path="device/samsung/chagallwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagalllte" path="device/samsung/chagalllte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallltetmo" path="device/samsung/chagallltetmo" remote="github" />
<project name="CM-Tab-S/android_kernel_samsung_klimtwifi" path="kernel/samsung/klimtwifi" remote="github" revision="deathly_cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="CM-Tab-S/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="deadman96385/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0-common" />
<remove-project name="platform/prebuilts/qemu-kernel" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" clone-depth="1" remote="aosp" revision="refs/tags/android-6.0.1_r31" />
</manifest>

Reserved

Enable rotation on the homescreen:
Long press on the homescreen select the up arrow and select allow rotation

Sweet. Will try this evening.

When do you plan making a build for the T705 (klimtlte)? I already tried my luck with building. The kernel booted, but I didn't boot completely up. This is my new device tree which I unfortunately can not test, because I have to redownload the sources: https://github.com/haimann951/android_device_samsung_klimtlte

oh yeah!
i will give it a try!

Thanks for this man ! Will try to install and will report back in a few minutes @deadman96385

haimann95 said:
When do you plan making a build for the T705 (klimtlte)? I already tried my luck with building. The kernel booted, but I didn't boot completely up. This is my new device tree which I unfortunately can not test, because I have to redownload the sources: https://github.com/haimann951/android_device_samsung_klimtlte
Click to expand...
Click to collapse
Soon, i have a klimtlte being shipped to me now. Once it arrives i will release a build.

I installed the rom and i said "WOW!"
its not 100% smooth but it is very good for a first build.
one question: how can i change the background in lock screen?

Thanks dead man, been waiting on a cm13 for the tab s. Judging on your other work I bet this is great. Downloading as I write

Does heat issue in gaming and dast battery drain stil presist in cm13 because it was in cm12.1 and thats the only thjng that kept mi away from CM

rookie12 said:
Does heat issue in gaming and dast battery drain stil presist in cm13 because it was in cm12.1 and thats the only thjng that kept mi away from CM
Click to expand...
Click to collapse
Currently there is a wakelock issue but before i had that bug there was no heating or battery drain issues.

deadman96385 said:
Currently there is a wakelock issue but before i had that bug there was no heating or battery drain issues.
Click to expand...
Click to collapse
So 40•C is normal when playing games and battery drains from 100 t0 p in 1 or 2 hours?

rookie12 said:
So 40•C is normal when playing games and battery drains from 100 t0 p in 1 or 2 hours?
Click to expand...
Click to collapse
Chill man i mean't on cm-13.0 on builds that i did not release, so once this wakelock bug is fixed your heating and power problems will be solved.

Bootloop when installing Beta-SuperSU 2.50.
Installed CM13 and Gaps, booted to android. configured first time. Rebooted to recovery and installed SuperSU, bootlooping....
Update:
Solved by installing UPDATE-SuperSU-v2.65-20151226141550.zip

Venzent said:
Bootloop when installing Beta-SuperSU 2.50.
Installed CM13 and Gaps, booted to android. configured first time. Rebooted to recovery and installed SuperSU, bootlooping....
Update:
Solved by installing UPDATE-SuperSU-v2.65-20151226141550.zip
Click to expand...
Click to collapse
Why flash supersu when there is root built in?

deadman96385 said:
Why flash supersu when there is root built in?
Click to expand...
Click to collapse
Maybe my lack of knowledge, I'm not that deep into custom builds, but I thought SuperSU is always needed to provide root access when apps requesting it? (the always allow or ask again within 15 minutes question).

Venzent said:
Maybe my lack of knowledge, I'm not that deep into custom builds, but I thought SuperSU is always needed to provide root access when apps requesting it? (the always allow or ask again within 15 minutes question).
Click to expand...
Click to collapse
If you unlock developer settings by tapping the build number in about tablet and then go to developer settings find the Root access option and select Apps only and you will have the same option as supersu it will prompt you when somthing wants to have root with an option to always allow it.

deadman96385 said:
If you unlock developer settings by tapping the build number in about tablet and then go to developer settings find the Root access option and select Apps only and you will have the same option as supersu it will prompt you when somthing wants to have root with an option to always allow it.
Click to expand...
Click to collapse
Thanks, didn't know that.....
And thanks for the ROM also of course
---------- Post added at 08:31 PM ---------- Previous post was at 08:03 PM ----------
Ok,
(very) first findings.
ROM is fast, smooth, no problems so far, heating and/or battery drain must be waited for in the upcoming days (if exists).
2 issues, Facebook FC's, directly at startup, and when an app that uses FB starts, it gives the CF error as well (like Candy Crush).
KPN iTV online (local televison provider, streaming application), gives black screen in app instead of the stream itself.

[ROM][6.0.1][UNOFFICIAL][WIP] Cyanogenmod 13.0 - SM-T807T

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial CyanogenMod 13.0 builds for chagallltetmo (SM-T807T). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Installation
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install the T805 TWRP Recovery
Make sure you are on the latest bootloader (Lollipop 5.0.2)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Install the Google Apps addon package (Optional)
Reboot
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
Downloads
CyanogenMod:
4/28 Build
Google Apps:
http://opengapps.org/- thanks to the OpenGapps team!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Source:
Kernel: https://github.com/CM-Tab-S/android_kernel_samsung_klimtwifi
Device Tree: https://github.com/CM-Tab-S/android_device_samsung_chagallltetmo
Credits:
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
 @suhridkhan (for doing all of the on device testing for chagallltetmo)

Bugs:
DRM content in Google Play Movies does not play
Mic is quiet
Mobile Network is not fully working, your phone number, simcard, baseband are found but it can not connect to T-Mobile/AT&T yet
This build is very similar to T805 but i have set the default apn to T-Mobile LTE, to get the mobile network even partially working (Did not work at all on T805 builds) i have had to replace almost all of the ril proprietary blobs, i am also going to have to probably completely rewrite the ril interface we will have to see.
My Local manifest this will allow you to build any of the tab s variants
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CM-Tab-S/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallwifi" path="device/samsung/chagallwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagalllte" path="device/samsung/chagalllte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallltetmo" path="device/samsung/chagallltetmo" remote="github" />
<project name="CM-Tab-S/android_kernel_samsung_klimtwifi" path="kernel/samsung/klimtwifi" remote="github" revision="deathly_cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="CM-Tab-S/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="deadman96385/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0-common" />
<remove-project name="platform/prebuilts/qemu-kernel" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" clone-depth="1" remote="aosp" revision="refs/tags/android-6.0.1_r31" />
</manifest>

Mine just in case

Haha I had the download link for this yesterday

for those who are going to give it a shot, rom is fast and quite usable. But you need some precautions.
use Banks gapps package. opengapps giving problems.
you shall have to flash the rom and gapps at the same time. Do not boot into rom, if you are going to need gapps.
During the setup process keep the tablet in portrait mode. If you go landscape, the screen will freeze.

OMG Finally Marshmallow on the T807T!
I do need data to fully work before I flash this but i'd like to say thanks for getting this to our devices!

Wow! So happy right now!! Thank you for putting in the work for this. I was just about to downgrade to Lollipop but no more!
So I do have mobile data fully functioning, although I am using opengapps. I installed the rom as noted and when the play store wouldn't allow me to download content I went back into recoevery and wiped data and cache and reinstalled the same gapps and had success. So far the only problem I'm having is with bluetooth. It's only with the S Mouse. I have the keyboard fully functioning though. Im currently unable to attach my logcat file but will do so later. This is one line that sticks out "04-30 14:30:34.307 E/EventHub(3546): could not get driver version for /dev/input/mouse0, Not a typewriter". Will try and upload a complete log later.
Thanks again! I'll be happy to help out in the process.

metiCkOn3 said:
Wow! So happy right now!! Thank you for putting in the work for this. I was just about to downgrade to Lollipop but no more!
So I do have mobile data fully functioning, although I am using opengapps. I installed the rom as noted and when the play store wouldn't allow me to download content I went back into recoevery and wiped data and cache and reinstalled the same gapps and had success. So far the only problem I'm having is with bluetooth. It's only with the S Mouse. I have the keyboard fully functioning though. Im currently unable to attach my logcat file but will do so later. This is one line that sticks out "04-30 14:30:34.307 E/EventHub(3546): could not get driver version for /dev/input/mouse0, Not a typewriter". Will try and upload a complete log later.
Thanks again! I'll be happy to help out in the process.
Click to expand...
Click to collapse
what! you have mobile data? how?
I am not having any data here.

suhridkhan said:
what! you have mobile data? how?
I am not having any data here.
Click to expand...
Click to collapse
I switched to the ims apn, which then kicked back to the tmobile lte apn and data kicked on. I also disabled data roaming, maybe that played a part.

So I have an update. It looks like my apn was switching to a net 10 apn and giving me a connection under that apn, maybe I had data roaming on at that point in testing. To test this theory I have deleted all my apns but my tmobile us lte apn and I no longer get an LTE signal, mms does work however. I did edit the apn to match tmobile's recommeded settings for android tablets (magenta emploee here). Will keep testing.
UPDATE: Okay I got a connection and it stays for the most part. It disconnects if I put the tablet to sleep. A quick workaround is to disconnet and reconnect data. I will upload a screenshot of the settings I'm using.

metiCkOn3 said:
So I have an update. It looks like my apn was switching to a net 10 apn and giving me a connection under that apn, maybe I had data roaming on at that point in testing. To test this theory I have deleted all my apns but my tmobile us lte apn and I no longer get an LTE signal, mms does work however. I did edit the apn to match tmobile's recommeded settings for android tablets (magenta emploee here). Will keep testing.
UPDATE: Okay I got a connection and it stays for the most part. It disconnects if I put the tablet to sleep. A quick workaround is to disconnet and reconnect data. I will upload a screenshot of the settings I'm using.
Click to expand...
Click to collapse
Can you get a log of you having an active data, going to sleep and then waking back up? easiest way is to download syslog give it root and then do the proccess. Then upload the zip anywhere you like.
Edit: Also you would probably know does the T-Mobile variant have the ability to make calls on stock? I know T805 and T705 can but they are international devices.
Edit2: I also will see if i can enable a few more mouse drivers in the kernel, bluetooth is a constant issue currently across all the tab s variants

deadman96385 said:
Can you get a log of you having an active data, going to sleep and then waking back up? easiest way is to download syslog give it root and then do the proccess. Then upload the zip anywhere you like.
Edit: Also you would probably know does the T-Mobile variant have the ability to make calls on stock? I know T805 and T705 can but they are international devices.
Edit2: I also will see if i can enable a few more mouse drivers in the kernel, bluetooth is a constant issue currently across all the tab s variants
Click to expand...
Click to collapse
To answer your question about phone calls, I can't remember to be honest. It's been a year almost since we sold it and I only had stock for a day, but with all our tablets we disable the ability to call so I would imagine it DOES NOT have the ability to make calls. I can flash back to stock and check for you if you need.
Here's the log of the data disconnect and the bluetooth fail. I was wrong about the sleep disconnecting data, it was just a coincidence. Regardless, here is the log. Let me know if you need more testing.

Anyone know if this works with t807p (sprint LTE variant)??
Sent from my SM-T807P using XDA-Developers mobile app

Data Works Now
I changed mine to the same ims apn and data works with not issues now. I did a speed test I am getting about 19mbps at 2bars of lte. so not bad. So far so good.
metiCkOn3 said:
I switched to the ims apn, which then kicked back to the tmobile lte apn and data kicked on. I also disabled data roaming, maybe that played a part.
Click to expand...
Click to collapse

chargerfn909 said:
Anyone know if this works with t807p (sprint LTE variant)??
Sent from my SM-T807P using XDA-Developers mobile app
Click to expand...
Click to collapse
This will not work on the sm-t807p sadly that variant has a snapdragon soc.

wanpa78 said:
I changed mine to the same ims apn and data works with not issues now. I did a speed test I am getting about 19mbps at 2bars of lte. so not bad. So far so good.
Click to expand...
Click to collapse
Nice! Glad I could help a little. I used to port miui & cm to the droid & droid 2 but quit because I had too much learning to do and not enough time . Anyway, I'm really looking forward to future dev of this rom. I'm really hoping for full s-mouse support, although I'll take any mouse support.

Very pleased to see work progressing on this. We need to make this thread get more views!!
Great work and when I get a free day (if ever lol) I will load it up and see what I can help with.
Sent from my SM-N920T using XDA-Developers mobile app

deadman96385 said:
This will not work on the sm-t807p sadly that variant has a snapdragon soc.
Click to expand...
Click to collapse
Damn...That variant is like the curse of all tablets in terms of modding...lol. Thanks

chargerfn909 said:
Damn...That variant is like the curse of all tablets in terms of modding...lol. Thanks
Click to expand...
Click to collapse
Yeah they have it worse then the 807t. At least we can run some roms with the stock kernel.
Sent from my SM-N920T using XDA-Developers mobile app

NXLTrauma25 said:
Yeah they have it worse then the 807t. At least we can run some roms with the stock kernel.
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Sadly, I am "they" :*( lol

{need testers} DOT OS DUMPLING (ROM)

im just a normal guy with no code experience which read some errors in english lol and compiled dot os for dumpling.
im going to test it later tonight but thought to share it. I dont know if it boots thats why i need yous.
I used gzosp sources and vendor from here
https://github.com/LiquidRemix-Devices/proprietary_vendor_oneplus/tree/oc-mr2/dumpling
Oh btw flash kernel is built in. Thanks tk nathanchance because his kernel is my favourite
. (if it boots ill fix the thread with proper credits) (maybe ob5 firmware or ob6???)
You most likely need to be decypted.
Can you please share the firmware and if you were decrypted or not. ill be testing it later today too on my device.
here:
https://www.androidfilehost.com/?fid=890278863836283024

Gonna give it a try my friend... downloading now...
Edit: doesnt boot so far

alewis2k12 said:
Gonna give it a try my friend... downloading now...
Edit: doesnt boot so far
Click to expand...
Click to collapse
Yep doesn't boot. Noooo wanted it to work so badly. I'll try with linesge sources but I'm getting errors atm

heres my roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="nathanchance/op5" path="kernel/oneplus/msm8998" remote="github" revision="8.1.0-unified" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-15.1" />
<project name="GZOSP-Devices/device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" revision="8.1" />
<project name="GZOSP-Devices/device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" revision="8.1" />
<project name="AospExtended-Devices/android_device_oppo_common" path="device/oppo/common" remote="github" revision="7.x" />
<project clone-depth="1" groups="pdk" name="platform/prebuilts/clang/host/linux-x86" path="prebuilts/clang/host/linux-x86/clang7" revision="master" />
</manifest>
with some edits it compiles but doesnt boot.
any suggestions guys on how to fix it? or what to add for this? ive tried lineage sources but keep keeping live display issues, missing this that. idk what to do

Wish I knew how to help, but I can confirm that it didn't boot for me either. Decrypted after flashing it with a few different firmwares and the no verity zip.

Jamie_oppo said:
heres my roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="nathanchance/op5" path="kernel/oneplus/msm8998" remote="github" revision="8.1.0-unified" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-15.1" />
<project name="GZOSP-Devices/device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" revision="8.1" />
<project name="GZOSP-Devices/device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" revision="8.1" />
<project name="AospExtended-Devices/android_device_oppo_common" path="device/oppo/common" remote="github" revision="7.x" />
<project clone-depth="1" groups="pdk" name="platform/prebuilts/clang/host/linux-x86" path="prebuilts/clang/host/linux-x86/clang7" revision="master" />
</manifest>
with some edits it compiles but doesnt boot.
any suggestions guys on how to fix it? or what to add for this? ive tried lineage sources but keep keeping live display issues, missing this that. idk what to do
Click to expand...
Click to collapse
Are you sure that flash kernel will work on aosp base roms? If it works then there's something wrong with your building or else just try to include some other kernel which supports aosp base.

chinnu07 said:
Are you sure that flash kernel will work on aosp base roms? If it works then there's something wrong with your building or else just try to include some other kernel which supports aosp base.
Click to expand...
Click to collapse
well if its kernel problem. We should try. Flash the rom then flash a kernel on top. What kernel would u try. I dont think its that. Heaps of custom roms and even the cheeseburger build has the flash kernel. Thanks for replying

updater script would be my guess

benny3 said:
updater script would be my guess
Click to expand...
Click to collapse
What abt the updater script is what could be making it not boot.

guys new rom built form more lineage based source. if anyone wants to test. im hoping this will boot. i used liquid device treeanad aicp vendor. use ;atest firmware
https://www.androidfilehost.com/?fid=746163614322263400
ill test later too

Jamie_oppo said:
guys new rom built form more lineage based source. if anyone wants to test. im hoping this will boot. i used liquid device treeanad aicp vendor. use ;atest firmware
https://www.androidfilehost.com/?fid=746163614322263400
ill test later too
Click to expand...
Click to collapse
Can't get the dang thing to boot :crying:

chesstopher said:
Can't get the dang thing to boot :crying:
Click to expand...
Click to collapse
doesnt boot, stuck on op logo!

Ok ill try a clean build. That build was from before and i just changed the parts i need like device tree and msm common. And compiled. It started from 36k not the usually 100k. Ill make clean and do a clean build.
It takes 6 hrs to compile arhh
Because this local_manifest worked for the cheeseburger.
It should build to 100% without errors

Jamie_oppo said:
Ok ill try a clean build. That build was from before and i just changed the parts i need like device tree and msm common. And compiled. It started from 36k not the usually 100k. Ill make clean and do a clean build.
It takes 6 hrs to compile arhh
Because this local_manifest worked for the cheeseburger.
It should build to 100% without errors
Click to expand...
Click to collapse
Thanks man, I appreciate your efforts. dotOS seems really cool!

Just hope it doesnt error

new build. Fresh. make clean. with these source and a couple edits. only edits made were for slim in device oppo common. (shouldnt affect anything ) and the removing smart pixels from an overlay becuase that was giving errors.
this is my roomservice
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
<project name="LiquidRemix-Devices/android_device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" revision="oc-mr1" />
<project name="LiquidRemix-Devices/android_device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" revision="oc-mr1" />
<project name="LiquidRemix-Devices/android_device_oppo_common" path="device/oppo/common" remote="github" revision="oc-mr1" />
<project name="LiquidRemix-Devices/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="oc-mr1" />
<project name="nathanchance/op5" path="kernel/oneplus/msm8998" remote="github" revision="8.1.0-unified" />
<project clone-depth="1" groups="pdk" name="platform/prebuilts/clang/host/linux-x86" path="prebuilts/clang/host/linux-x86/clang7" revision="master" />
<project name="LineageOS/android_lineage-sdk" path="lineage-sdk" remote="github" revision="lineage-15.1" />
</manifest>
if this doesnt boot then idk what will. But it should. it did for the cheeseburger.
heres the link. make sure u have a full backup and test if its decrypted or encrypted. i have no time today. i have work and school. ill test in 24hrs if someone hasnt already.
i hope it gets to the boot animation this time lol.
https://www.androidfilehost.com/?fid=962339331458991494

Just tested it decryoted. Didnt boot. I give up lol

Jamie_oppo said:
Just tested it decryoted. Didnt boot. I give up lol
Click to expand...
Click to collapse
:crying::crying:

Jamie_oppo said:
Just tested it decryoted. Didnt boot. I give up lol
Click to expand...
Click to collapse
Hi. I was the one who built dotOS successfully for cheeseburger and it was smooth.
But as i was maintaining AospExtended ROM for cheeseburger, i didnt find it useful to continue dotOS builds.
Currently I'm Officially maintaining AEX for cheeseburger.
Coming to dotOS for dumpling,
1) does the build process gives you any error??
2)If yes what did you try to overcome it?
3) Does the flash kernel work well for dumpling too??
If you think everything is well with above questions, then get a log from adb while your phone fails to boot and attach it. I will look into it. Thanx..

drpradsms said:
Hi. I was the one who built dotOS successfully for cheeseburger and it was smooth.
But as i was maintaining AospExtended ROM for cheeseburger, i didnt find it useful to continue dotOS builds.
Currently I'm Officially maintaining AEX for cheeseburger.
Coming to dotOS for dumpling,
1) does the build process gives you any error??
2)If yes what did you try to overcome it?
3) Does the flash kernel work well for dumpling too??
If you think everything is well with above questions, then get a log from adb while your phone fails to boot and attach it. I will look into it. Thanx..
Click to expand...
Click to collapse
OK. Yes flash kernel does work well.
Next week or so. I'll start fresh with ur roomservice.
I'll get up to the errors and tell you what I did to overcome it.
From what I remember I had errors with device oppo common and for slim ( not being able to made or something)
Obviously had to edit liquid. Mk and inside common. Mk and liquid to dot. And change the boardconfig for flash kernel.
Also other other one I remember was in msm8998 common (overlay) Where smart pixels and always on display was creating errors. So I removed the troubled lines.
If it requires too much coding experience for me to do. Don't worry about it. Ive got no experience. I'm playing around with it and learning at school rn.
Thanks for your consideration

[discussion] i9060 roms

Hi , This was created so we can make ROMs for the extinct grand neo . Every ROM , even Oreo is there for plus model but nothing at all for this model, I request devs and can help in any way as I still have the phone
But I currently use xperia e3 with lineage OS 14.1 (7.1.2 Android)

Hello
RaghavTecki29 said:
Hi , This was created so we can make ROMs for the extinct grand neo . Every ROM , even Oreo is there for plus model but nothing at all for this model, I request devs and can help in any way as I still have the phone
But I currently use xperia e3 with lineage OS 14.1 (7.1.2 Android)
Click to expand...
Click to collapse
The device can be added to lineageos but I do not know.

I think someday i will learn how to compile rom, so i can compile LOS for this device, idk when, but maybe, could be great because i have 2 samsung galaxy grand.
But i think my computer need to be more powerful, so this can be impossible

I might try to get something working, but I don't promise anything
Wanted to do the same thing back in 2017 (see https://forum.xda-developers.com/showpost.php?p=73299951) but forgot about it. I'll pick up on the project and see how far can I take it.

knuxfanwin8 said:
I might try to get something working, but I don't promise anything
Wanted to do the same thing back in 2017 (see https://forum.xda-developers.com/showpost.php?p=73299951) but forgot about it. I'll pick up on the project and see how far can I take it.
Click to expand...
Click to collapse
I can test your rom if you compile one.

Thanks! I'll try to compile it today or tommorow.
---------- Post added at 08:39 AM ---------- Previous post was at 08:37 AM ----------
antoine62 said:
I can test your rom if you compile one.
Click to expand...
Click to collapse
Thanks! I'll try to compile it today or tommorow.

knuxfanwin8 said:
Thanks! I'll try to compile it today or tommorow.
---------- Post added at 08:39 AM ---------- Previous post was at 08:37 AM ----------
Thanks! I'll try to compile it today or tommorow.
Click to expand...
Click to collapse
I hope that you compile it today

Current project status: rebranded stuff to Lineage, and I'm getting "No matches for product: lineage_baffinlite" despite all files being in the right places.
Thaaaat's Android building for 'ya.

Some news?

antoine62 said:
Some news?
Click to expand...
Click to collapse
I guess?
Bad news is, I didn't go much further.
Good news is, I found out about postmarketOS. It requires a lot less work to get the base up and running, but it's possible that hardware support can be a problem.
Even better news: I might get a device for testing next week (and if not next week, then likely on Easter).
So, could anybody get CPU-Z and send me screenshots of all the tabs, just so that I can verify everything? (What I need the most is the screen resolution)
Once that will be done, I'll post a flashable ZIP (or a full heimdall compatible thing, we'll see).

knuxfanwin8 said:
I guess?
Bad news is, I didn't go much further.
Good news is, I found out about postmarketOS. It requires a lot less work to get the base up and running, but it's possible that hardware support can be a problem.
Even better news: I might get a device for testing next week (and if not next week, then likely on Easter).
So, could anybody get CPU-Z and send me screenshots of all the tabs, just so that I can verify everything? (What I need the most is the screen resolution)
Once that will be done, I'll post a flashable ZIP (or a full heimdall compatible thing, we'll see).
Click to expand...
Click to collapse
I dont have my samsung grand rn, srry

Got the resolution from GSMarena
Anyways, I did I quick test build with weston, just to see if it works. I definitively will get LineageOS 16.1 working soon, and possibly run some TWRP builds if necesarry.
Here are the files:
https://androidfilehost.com/?w=files&flid=291150
The pmos-samsung-baffinlite.zip file is a flashable ZIP file - flash it through TWRP. The tar.md5 is just the boot.img. As this post is being written, I'm still uploading the samsung-baffinlite.img which I assume is the rootfs only. (EDIT: It's done)

knuxfanwin8 said:
Got the resolution from GSMarena
Anyways, I did I quick test build with weston, just to see if it works. I definitively will get LineageOS 16.1 working soon, and possibly run some TWRP builds if necesarry.
Here are the files:
https://androidfilehost.com/?w=files&flid=291150
The pmos-samsung-baffinlite.zip file is a flashable ZIP file - flash it through TWRP. The tar.md5 is just the boot.img. As this post is being written, I'm still uploading the samsung-baffinlite.img which I assume is the rootfs only. (EDIT: It's done)
Click to expand...
Click to collapse
wait
Thid is the rom?
For the grand i9060?

antoine62 said:
wait
Thid is the rom?
For the grand i9060?
Click to expand...
Click to collapse
Not really, it's postmarketOS, which is basically pure Linux for Android devices (and doesn't have fully developed mobile capabilities yet). As I said, I'll be trying to get lineage os 16 builds working next (for real this time).

Oh, ok but this is for the i9060?

knuxfanwin8 said:
Not really, it's postmarketOS, which is basically pure Linux for Android devices (and doesn't have fully developed mobile capabilities yet). As I said, I'll be trying to get lineage os 16 builds working next (for real this time).
Click to expand...
Click to collapse
Thank you for your time trying to compile a rom for this device. I hope you might get positive results. I tried compiling, porting a rom, also failed didn't know what I did wrong. Hopes are on you my friend
I'm here to test the rom for you.

BREAKING NEWS: I no longer get that "cannot find product spec" error! Expect LineageOS 16 builds from whatever sources I was able to find soon, possibly around next week.

This is awsome If this old phone get android pie (with basic thing working, like RIL and wifi)
---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------
Another thing: Where can i find how to compile a rom for a device that isn't officially suported?

Some more news: I've got my own Grand Neo for testing now!
The build's going well, at the moment I'm a bit stuck but will get everything sorted out eventually.
Device tree:
https://github.com/knuxdroid/android_device_samsung_baffinlite
antoine62 said:
Another thing: Where can i find how to compile a rom for a device that isn't officially suported?
Click to expand...
Click to collapse
You can follow the official build guide (this one). You'll have to add the device to the repo manifest:
- create ~/android/.repo/local_manifests/local_manifest.xml
- copy the following (replace information as needed):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="https://github.com/" />
<project path="device/DEVICE MANUFACTURER/DEVICE CODENAME" name="GITHUB USER/android_device_DEVICE MANUFACTURER_DEVICE CODENAME" remote="github" revision="master" />
<project path="kernel/DEVICE MANUFACTURER/DEVICE CODENAME" name="GITHUB USER/android_kernel_DEVICE MANUFACTURER_DEVICE CODENAME" remote="github" revision="master" />
<project path="kernel/DEVICE MANUFACTURER/DEVICE CODENAME" name="GITHUB USER/android_kernel_DEVICE MANUFACTURER_DEVICE CODENAME" remote="github" revision="master" />
<project path="hardware/DEVICE MANUFACTURER" name="LineageOS/android_hardware_DEVICE MANUFACTURER" remote="github" revision="master" />
</manifest>
You can find the repositories on github, replace the name="GITHUB USER/android_device_DEVICE MANUFACTURER_DEVICE CODENAME" with the link to the repository (without https://github.com/) and make the path match the name (for example android_device_samsung_baffinlite becomes path="device/samsung/baffinlite").
There are many better tutorials than this online in case you don't understand something (I'm pretty bad at explaining things )

Relatively recent?
Rip, my pc is very old xD
Like 6-7 years old
---------- Post added at 05:25 PM ---------- Previous post was at 05:18 PM ----------
Android 9 rom need twrp 3.2 i think?
If yes, then we need a new twrp version

Lineage 15.1 Build For Athene: Multiple Errors

Hello developers!
I am a newbie to XDA and also a newbie to ROM development, so if I am doing anything wrong, please do tell me. I own a Motorola Moto G4 Plus and I am very ready to invest as much time as needed in building and creating ROMs for this phone.
I am currently building LineageOS for this phone, and once that is done, I want to try my hand at porting Lineage 16 to this device. I had recently successfully built the cm-14.1 branch for this device (which seems to be the only official build for athene, see the LineageOS Wiki https:// wiki.lineageos.org/ devices/athene/ build#initialize-the-lineageos-source-repository). Now, I downloaded the code for LineageOS 15.1 onto my Linux computer (running Ubuntu 19.04) and have tried to build it.
Steps I took to build -
- Initialised repo with repo init.
- Synced the repository to my Linux computer with
Code:
repo sync -c --no-tags --no-clone-bundle -j24
- Created .repo/local_manifests/roomservice.xml for the device tree, kernel, etc. with the following content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_athene" path="device/motorola/athene" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_kernel_motorola_msm8952" path="kernel/motorola/msm8952" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
- Ran
Code:
repo sync -c -j24
- Then ran
Code:
export ROOMSERVICE_BRANCHES="lineage-15.0"
to specify a fallback branch
- Ran
Code:
source build/envsetup.sh
- Ran
Code:
breakfast athene
The command ran successfully, no errors until now.
- Then ran
Code:
brunch athene
This is where the problems started popping up. I got errors while building in the following places -
(Treat .(dot) as my source dir)
ERROR 1 - In out/soong/make-vars(don't remember correct file name) - Still get it after
Code:
make clobber[\CODE], I have to always comment line 692 which throws the my-check error to suppress it.
ERROR 2 - Couple of old CyanogenMod dependencies and packages which I managed to get past after messing about with the ./device/motorola/athene/BoardConfig.mk file.
ERROR 3 - Errored out because BOARD_KERNEL_IMAGE_NAME was not defined, finally found an old XDA thread for the 15.1 ROM that told me that I had to set that to zImage in device/motorola/athene/BoardConfig.mk
ERROR 4 - In file ./system/core/init/init.h - Could not find <android-base/chrono_utils.h>, Could not find <selinux/label.h> - Got rid of it by putting in relative file paths and also modifying the ./system/core/init/Android.mk's LOCAL_C_INCLUDES to have relative file paths.
ERROR 5 - In file system/core/adb/daemon/main.cpp, system/core/base/include/android-base/macros.h: Cannot identify arraysize(groups).
ERROR 6 - In file system/core/adb/daemon/main.cpp - Use of undeclared identifier 'AID_UHID'
I can try to fix these errors, but I feel that there must be some branch/fork of the LOS15.1 code that must have all these issues fixed. If anyone has any pointers regarding this or the errors, I would be very grateful.
Thanks in advance,
gamemaker1

I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.

Wheels564 said:
I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.
Click to expand...
Click to collapse
Ok, thanks! I just saw the link, it seems good. Will try it out today and let you know the result.

@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1

gamemaker1 said:
@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1
Click to expand...
Click to collapse
No problem at all. The only thing about LOS 15.1 is that Lineage will never make it official. They've dumped all the rest of the phone on 15.1 because of repo changes I believe. Check here: https://review.lineageos.org/269773
I'm sure they will continue to submit security patches just like 14.1. Looks like the only way to become official is to jump to 16.1. It looks like developers have had issues with athene on LOS 16.1. Glad you were able to build the rom and good luck with future projects.