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
Related
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* 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.
*
*/
Instructions
1. Download the zip(s) - firmware and Google Apps additional package (optional)
2. Download and install a compatible recovery
3. Wipe data, system & cache partitions and flash firmware
4. Optional: install the Google Apps additional package
Known Issues:
- XBMC and some games touch input will fail. A work around would be to purchase a bluetooth keyboard, they are pretty cheap from ebay, or use your existing one to navigate inside XBMC until we solve the problem.
- audio routing does not work when making calls with viber, hangout or skype while connected to bluetooth headset.
- MHL output the colours wrong and audio does not route to tv.
- Google movies will crash if you want to download locally.
- Anything else? you tell me
02/12/2014 stable build
cm-11-20141202-UNOFFICIAL-klimtwifi.zip
- Hulu not working fixed
- google movies not downloading locally fixed
- charging while tablet is off fixed
cm-11-20141202-v2-klimtwifi.zip
fix graphic glitches
added kernel Performance, powersave and userspace governors
All current and previous builds, kernels and fixes can be found HERE
Latest build by senior user miscom:
12/12/2014
https://www.androidfilehost.com/?fid=95854736883843077
upstream cm source update
17/12/2014
https://www.androidfilehost.com/?fid=95857557620393377
upstream cm source update
27/12/2014
https://www.androidfilehost.com/?fid=95864024717070862
upstream cm source update
04/01/2015
cm-11-20150104-UNOFFICIAL-klimtwifi.zip
cm-11-20150104-UNOFFICIAL-klimtwifi.zip.md5sum
corrected true battery values for klimtwifi thanks to github user moneytoo who brought to my attention
update CM source
1/03/2015
cm-11-20150301-UNOFFICIAL-klimtwifi.zip
cm-11-20150301-UNOFFICIAL-klimtwifi.zip.md5sum
Fixed Kodi/xbmc touch issues, and with many games that had no touch register issues.
all credit for the touch issue patch goes to @Patrick Lower
20/05/2015
cm-11-20150520-UNOFFICIAL-klimtwifi.zip
cm-11-20150520-UNOFFICIAL-klimtwifi.zip.md5sum
Google Apps additional package:
http://wiki.cyanogenmod.org/w/Gapps
TWRP:
http://forum.xda-developers.com/gal...recovery-twrp-2-7-1-0-touch-recovery-t2817100
Sources Barracuda:
device tree
kernel for exynos 5420
vendor files
thanks to CyanogenMod team, Google and thanks to:
Nvertigo67 fixing many bugs, eousphoros for starting the intital port to klimtwifi, danny19901, fedecape, rukawa84, kafandi, miscom and anyone else I forgot for testing the rom , crpalmer for his hard work.
Special big thanks to Nvertigo67.
How to build your own
The Guide
1) please visit this thread and follow the instruction to prepare your build environment.
2) once you have CM11 sources downloaded and ready on your build server.
You will need to find your roomservice.xml android/.repo/local_manifests/roomservice.xml and add the following entries:
<project name="barracuda7/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" revision="master" />
<project name="barracuda7/android_kernel_samsung_chagallwifi" path="kernel/samsung/chagallwifi" remote="github" revision="cm-11.0" />
<project name="barracuda7/android_vendor_samsung_klimtwifi" path="vendor/samsung/klimtwifi" remote="github" revision="master" />
click save.
Note: if you fork the repos to your own github account, replace barracuda7 with your own github username.
3) from terminal type the following:
repo sync this should download the blobs, device tree and the kernel.
breakfast klimtwifi will add the rest of the repo's that are needed.
source build/envsetup.sh
brunch klimtwifi
if all above steps were done successfully depending on how fast is your build server you should end up with a zip in about an hour or more.
you can find the zip file here:
android/out/target/product/klimwifi
You are most welcome to post question on this thread regarding building the rom, please only PM me if it is not this rom related, in this way other users can benefit from
the information
Happy Building
reserved
one more
can you make one for t705?
rowihel2012 said:
can you make one for t705?
Click to expand...
Click to collapse
I already tried, not having the tablet makes it extremely hard, until a similar device gets Ported that I can base upon the answer to your question is sadly no.
Sent from my Nexus 5 using Tapatalk
Amazing really great and only 1 issue mic doesn't seem to be picking anything up at all
Barracuda77777 said:
I already tried, not having the tablet makes it extremely hard, until a similar device gets Ported that I can base upon the answer to your question is sadly no.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Have you tried contacting crpalmer??
He is maintaining CM 11 on the tab pro lte version and both devices uses the same qualcomm snapdragon 800.hopefully this can point you in the right direction to get lte working.
also,thanks for the cm lovin on the t705,samdung's lagwizz on this beast's hardware is a complete waste.
and i believe many t705 owners will be willing to trip knox jus to get cm on this baby.
frostmore said:
Have you tried contacting crpalmer??
He is maintaining CM 11 on the tab pro lte version and both devices uses the same qualcomm snapdragon 800.hopefully this can point you in the right direction to get lte working.
also,thanks for the cm lovin on the t705,samdung's lagwizz on this beast's hardware is a complete waste.
and i believe many t705 owners will be willing to trip knox jus to get cm on this baby.
Click to expand...
Click to collapse
My T705 exynos 5 octa not snapdragon
my t705 is exynos 5 octa
rowihel2012 said:
my t705 is exynos 5 octa
Click to expand...
Click to collapse
So snapdragon won't help us as of different radios etc...
danny19901 said:
So snapdragon won't help us as of different radios etc...
Click to expand...
Click to collapse
yea
rowihel2012 said:
yea
Click to expand...
Click to collapse
so back to square one
so the 9500 is the closest to the 705 -805 tablet, but that one is a 3g not LTE
i think if we did not got t705 i will replace it with nexus 9
lagwiz roms make this tab dead
i had the lg pro 2 it was externally fast no lag at all i love snapdragon
my bad abut the cpu,mine is also the exynos octa but the next closest is not the n9500 but the n9005 (Note 3 exynos).
http://www.gsmarena.com/samsung_galaxy_note_3-5665.php
so i guess that where we should look at instead.
i havent been following the note series phone forum after the knox crap samdung tired to ram down consumers throats.but i am sure there are cm roms floating ard.
will keep an eye out on recognised dev to see if anyone can help.
is there a way to look at the lte tw roms for 705 to see if we can get any answers?
For everyone who is gonna try this out I have done some more testing and found a few things that need fixing
In build that's been uploaded
Mono speaker/only 1 speaker works = fixed in next update as I have both working
MIC = not working but also fixed in next update
SD card = won't read or mount but does in recovery
Camera = wrong orientation and looks weird also camera apps I have tested struggle/crash when going to front facing camera
These are what I have found so far
danny19901 said:
For everyone who is gonna try this out I have done some more testing and found a few things that need fixing
In build that's been uploaded
Mono speaker/only 1 speaker works = fixed in next update as I have both working
MIC = not working but also fixed in next update
SD card = won't read or mount but does in recovery
Camera = wrong orientation and looks weird also camera apps I have tested struggle/crash when going to front facing camera
These are what I have found so far
Click to expand...
Click to collapse
Can confirm this.
On the software side:
- battery stats is finally working
- on a dirty flash the unlockers from various programs are corrupted
- trebuchet still crashes on boot
- people apps works
- synapse doesn't work anymore (UCI not supported)
Going to report back on the battery, previous version of cm11 (other thread) had serious battery drain problems
But definitely a step up, keep up the great work!!
thomas_pieps said:
Can confirm this.
On the software side:
- battery stats is finally working
- on a dirty flash the unlockers from various programs are corrupted
- trebuchet still crashes on boot
- people apps works
- synapse doesn't work anymore (UCI not supported)
Going to report back on the battery, previous version of cm11 (other thread) had serious battery drain problems
But definitely a step up, keep up the great work!!
Click to expand...
Click to collapse
Just finished building a new build:
External sd fixed
microphone fixed
mono speaker issue
just waiting for danny19901 to test it out and I will post the link, or if there is anyone willing to test pm me.
happy to see people working on the T700 again will be giving it a try soon. I'm also a bit tired of TouchWiz
OP updated with new build:
cm-11-20141116-UNOFFICIAL-klimtwifi.zip
fixed:
external sd
stereo sound
microphone
still to be fixed camera preview is a bit skewed .
A big thank you do danny19901 for doing the testing. :good:
Great, feedback on the battery is as followed:
50% battery drain on 2h 26min, problem still there. For the moment I use the skyhigh cm 1.4 kernel
Which kernel do you guys use? And is the battery any better?
Hi,
Since I don't have permissions to post under development forum, I have to post this here
This is my unofficial compilation of PAC-ROM Lollipop.
I did this because there is no lollipop pac for yuga.
Download:
New from 28.03.15:
http://d-h.st/z76p
New MD5:
b408191649b3d35e52589b2b76020256
Old one:
http://d-h.st/HMsN
Old MD5:
1d271e26fdf2225cc0ca95b4e6e1a889
Note for mods: Can you please move this thread to development section?
Here is my local_manifest:
Code:
<project name="Pinky-Inky-and-Clyde/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_yuga" path="device/sony/yuga" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_qcom-common" path="device/sony/qcom-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_fusion3-common" path="device/sony/fusion3-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_msm8960-common" path="device/sony/msm8960-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_kernel_sony_apq8064" path="kernel/sony/apq8064" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="cm-12.0"/>
Sorry for my English
No screenshots ? :v
It's just like any other PAC-Rom
So whats working and whats not?
I don't see any bugs or something strange here. I'm using this ROM as daily driver
Repository synced and new ROM compiled!
Updated ROM and MD5 added to OP!
dzialo88 said:
Repository synced and new ROM compiled!
Updated ROM and MD5 added to OP!
Click to expand...
Click to collapse
great work! So far so good! :fingers-crossed:
Good Rom.
Thanks man,gonna take this AS daily driver too
Thanks to @Schneiderle who said me that there is this awesome lookin Rom
Btw so "things" Mike USB otg (EG with controller) and (native) screen mirroring is working ? Thanks !
Will report!
@dzialo88
Can you please edit the Start Post, Pac-Rom has since pretended that I know what kernel sources have taken you.? Github link would be very nice
@Cr33D OrB
I don't use screen mirroring but I got cheap USB OTG cable and it's working pretty good :good:
@Schneiderle
Added local_manifest to OP. Can be? :highfive:
@dzialo88
OK,USB otg working
So u dont know if scm is workng?..
Hmm.no prob ;p
Then i will have a look at it and will See if it works or not!
Pls give me info about it's working or not :highfive:
Installed rom CLEAN flash and seems that there no root Privilegs although actived in devoptioms and supersu and superuser..
Whatsapp is FC too.
Solution?
EDIT : Isnt this Rom Pre-rooted ?
Cant gain root access .. @dzialo88
Go into developer settings. There is root option. By default is no root
root is enabled but it's not
Yeah,same there is no root
Btw USB otg using controller AND screen mirroring not Working..
Man,thats no beta
Any Update News ?
Schneiderle said:
Any Update News ?
Click to expand...
Click to collapse
Now I'm going to provide pacman5.1 but many features aren't merged yet so please be patient
I'm gonna recover my Kitkat backup.
The current build doesn't suit my expectations. It doesn't feel ripe at the current state.
I have a massiv battery drain and I don't know why. Compared to the KitKat image, my phone dies in just a quarter of the time. According to Wakelock Detector, my phone was 87% of the time awake because msm_hsic_host had a wakelock. I also flashed Super Su (due to a missing management delivered by the ROM?) that kept a screen wakelock (wtf? my screen was definitly off!).
Another bug: When installing a self signed certificate, a gesture is recognized as a valid lock, but the certificate fails to install with "certificate not installed". I had to set a PIN to install my certificate. Also I'm missing different pattern sizes for the lockscreen.
Also: My wifi and mobile are always marked with a exclamation mark so I can't see, if I'm using 2G or 3G (possibly because I have no Gapps installed). I'm also missing the quick settings tile for switching between 2G and 3G. There's just a toggle for 4G.
The battery bar isn't visible if it's configured top or bottom the navbar.
That's everything that I have on my mind. Maybe it could scale the UI (notifcation drawer) better like the Settings app does, if the dpi value is lower (see image). At a value of 240 dpi, I have to draw my gesture on a box of 5x5 cm. Also the SIM-PIN request is small. (see second image). I would be really nice, if something could happen to scale them up to use the available space.
Everything else I'm using seems to run stable and fine. So nice work.
I'm going to try an Android 5.1 build when available. So I hope the era of Xperia Z isn't over already and we get some more updates by enthusiastic devs.
/edit: I also missed the PacPerformance manager
- I don't like the nearly useless CM Recovery
- I killed my baseband while undoing my upgrade
I'm testing 5.1 now (It compiled with source from 5.0 ). That's true CM Recovery is useless You should flash this in FOTAKernel partition http://forum.xda-developers.com/xperia-z/orig-development/recovery-teamwin-recovery-project-t2982889 . I only compiled this ROM, I don't know how to remove bugs :v
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.
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
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.