WARNING! This ROM is for the SPH-L520 variant only!
Code:
/*
* 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.
*
*/
Code:
[ROM]
[What works]
Boot Animation
Wifi/Teather
Bluetooth
Basic Sound
Adb/Usb/Charging
Camera
Notification LEDs
FM Radio
Calls
[Doesn't work right]
NFC
LTE/SMS/MMS/
GPS
IR Remote
[Untested]
Everything Else
[Bugs]
Camera crashes on startup if switched to external storage - to fix crash, go to settings -> apps -> all -> camera -> clear data
Code:
[Recovery]
[What works]
Nandroid backup
Nandroid Restore
Install Rom
Factory Restore
[Untested]
Everything else
[Bugs]
None Known
This is based off of arco's work at:
https://github.com/CyanogenMod/android_device_samsung_serranoltexx/tree/stable/cm-11.0
and all the rest of upstream.
Here's my github for gpl compliance/etc.
https://github.com/s0be/android_device_samsung_serranoltespr
Installation
Here's a simple list of what you need.
serranoltespr-cwm-6051.img
cm-12.1-20150815-UNOFFICIAL-serranoltespr.zip
CM12.1 Google Apps (Optional?)
THIS ROM ONLY WORKS WITH THIS RECOVERY. Do not use recoveries for other devices with the sprint s4 mini
Make sure to take a nandroid then wipe /data before installing this rom.
I'm too lazy to write proper install instructions, if someone would like to, I'll happily add them to this post.
I'm too lazy to update anything after this point. It's all old.
XDA:DevDB Information
CM11.0 for Sprint Galaxy S4 Mini, a ROM for the Samsung Galaxy S 4 Mini
Contributors
s0be
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-03-04
Last Updated 2014-03-26
3/10
- First release.
- Waiting on goo.im account
3/11
- Resync'd with upstream
- no local changes
3/17
- Still using the 3/11 upstream
- Switched to init.carrier.sh from stock
- Switched to ril files from stock
- Lots of other changes to make the previous 2 things work.
- Now feature complete, stable, daily driver, etc.
3/23
- Resync'd with upstream
- First build based off of grand unified serrano vendor tree
- Based on arco68's device tree.
Welcome s0be! Been a while since I've seen you around, so it's great to see you here! Let me know if you need anything.
arco68 said:
Welcome s0be! Been a while since I've seen you around, so it's great to see you here! Let me know if you need anything.
Click to expand...
Click to collapse
Will do. Just flashed my recovery. If you check my github you'll see a .patch file for the cm msm8930 kernel tree. I suspect my change in the gpio's was, in fact, exactly as wrong as I suspected. When I booted the recovery, the phone vibrated continuously. I did a nandroid backup and that seemed to work, backing up to sdcard1. Going to alter my change to the gpio defines for the cypress touch panel so that it always uses 24 for sda and 25 for scl.
I was actually amazed at exactly how LITTLE invasion I had to do into areas outside devices/samsung/serranoltespr to get it to compile. The kernel was the only place any non trivial changes were required (aside from extract-files.sh, but that's so device/rom specific that it's not a surprise at all).
Woohoo, working recovery!
s0be said:
Woohoo, working recovery!
Click to expand...
Click to collapse
Getting closer. I've built a recovery that has working usb. Now I'm trying to get a kernel that both boots CM11, and has working USB.
I've added serranoltespr to the build barriers. Without it the HAL for camera, gps and a few other things won't build.
Which reminds me, I need to add it to vendor barrier as well.
arco68 said:
I've added serranoltespr to the build barriers. Without it the HAL for camera, gps and a few other things won't build.
Which reminds me, I need to add it to vendor barrier as well.
Click to expand...
Click to collapse
Cool, thanks. Once I get a msm8930-common kernel working with USB, I'll sync up. Are you a kernel-msm8930-common maintainer? Should kernel patches go through github fork/pull requests or ??
Yeah, I'm the only maintainer. Patches usually goes through gerrit: http://review.cyanogenmod.org/#/q/status:open,n,z
I have elevated permissions on that repo, so I sometimes bypasses gerrit and pushes patches directly to github. Especially when there's a bulk of patches that needs to be merged.
I have an 'only mostly broken' build done, is anyone actually waiting for this, or should I get it feature complete first. Currently missing:
3g/Cell calls.
Basically, LTE works, or you can force 1x, and calls work, no 3g at this time. Everything else seems to work.
arco68 said:
Yeah, I'm the only maintainer. Patches usually goes through gerrit: http://review.cyanogenmod.org/#/q/status:open,n,z
I have elevated permissions on that repo, so I sometimes bypasses gerrit and pushes patches directly to github. Especially when there's a bulk of patches that needs to be merged.
Click to expand...
Click to collapse
only 1 patch so far is even remotely intrusive, and it's just updating the serial_msm_hs driver (which is disabled for the other 8930 boards). Now that I have USB charging working, I'm going to verify I need that change and likely drop it if not. I'm fine with the slow gerrit review.
I noticed that the US variants might need their own base defconfig, so you're using msm8930_serrano_usa_defconfig, right? If so, make sure CONFIG_USB_ANDROID_SAMSUNG_MTP is not enabled. That should probably give you working USB.
Try with this base config. I've adjusted the US variant one to match CM's defconfig.
I'll try to adjust BoardConfig in serrano-common so it selects the base deconfig based on variant.
arco68 said:
I noticed that the US variants might need their own base defconfig, so you're using msm8930_serrano_usa_defconfig, right? If so, make sure CONFIG_USB_ANDROID_SAMSUNG_MTP is not enabled. That should probably give you working USB.
Click to expand...
Click to collapse
arco68 said:
Try with this base config. I've adjusted the US variant one to match CM's defconfig.
I'll try to adjust BoardConfig in serrano-common so it selects the base deconfig based on variant.
Click to expand...
Click to collapse
Oh, I just based it off of msm8930_serrano_spr_defconfig (which inherits cyanogenmod-serrano) then enabled the stuff to get USB going. The actual specific issue looks to have been needing:
CONFIG_MFD_MAX77693 along with the correct battery/charger/etc.
Here's my current 'working' spr_defconfig
Code:
# This needs cleaned up, I suspect a lot of this is unnecessary.
CONFIG_MACH_SERRANO_SPR=y
CONFIG_2MIC_QUP_I2C=y
CONFIG_2MIC_ES305=y
CONFIG_2MIC_QUP_I2C_GSBI11=y
CONFIG_AUTHENTEC_VPNCLIENT_INTERCEPTOR=m
CONFIG_KEYBOARD_CYPRESS_TOUCH=y
CONFIG_POWER_SUPPLY=y
CONFIG_CHARGER_MAX77XXX=y
CONFIG_CHARGER_MAX77803=y
CONFIG_MFD_PM8921_CORE=y
CONFIG_MFD_PM8821_CORE=y
CONFIG_MFD_PM8038_CORE=y
CONFIG_MFD_PM8XXX_SPK=y
CONFIG_MFD_PM8XXX_BATT_ALARM=y
CONFIG_MFD_MAX77693=y
CONFIG_PM8921_BMS=n
CONFIG_PM8921_CHARGER=y
CONFIG_PM8921_SEC_CHARGER=n
CONFIG_MFD_PM8921_CORE=y
CONFIG_FUELGAUGE_MAX17048=y
CONFIG_BATTERY_SAMSUNG=y
CONFIG_SEC_DEBUG=y
CONFIG_SEC_DEBUG_SCHED_LOG=y
CONFIG_SEC_DEBUG_SUBSYS=y
CONFIG_USB_SWITCH_TSU6721=n
CONFIG_SERIAL_MSM_HS=y
CONFIG_USB_CI13XXX_MSM_HSIC=y
The only broken bits right now are 3g/lte phonecall sms/mms handovers and notification LEDS.
There's one base config for all variants, and one that's specific for each variant. For the EU variants, the base config is msm8930_serrano_defconfig. This is for stock ROM, so for CM I've adapted it and enabled custom bits in a new defconfig called cyanogen_serrano_defconfig.
The US variants seems to be using msm8930_serrano_usa_defconfig as their base config, and most of the things you added to the spr_defconfig should be enabled there already.
Add the defconfig I attached earlier to your kernel tree, and modify BoardConfigCommon.mk in serrano-common with
TARGET_KERNEL_CONFIG := cyanogen_serrano_usa_defconfig
The msm8930_serrano_spr_defconfig can be left as original without your changes. Only change there should be removing CONFIG_AUTHENTEC_VPNCLIENT_INTERCEPTOR, as afaik it's not used in CM.
Are you sure you have a notification light? None of the other variants have one.
arco68 said:
There's one base config for all variants, and one that's specific for each variant. For the EU variants, the base config is msm8930_serrano_defconfig. This is for stock ROM, so for CM I've adapted it and enabled custom bits in a new defconfig called cyanogen_serrano_defconfig.
The US variants seems to be using msm8930_serrano_usa_defconfig as their base config, and most of the things you added to the spr_defconfig should be enabled there already.
Add the defconfig I attached earlier to your kernel tree, and modify BoardConfigCommon.mk in serrano-common with
TARGET_KERNEL_CONFIG := cyanogen_serrano_usa_defconfig
The msm8930_serrano_spr_defconfig can be left as original without your changes. Only change there should be removing CONFIG_AUTHENTEC_VPNCLIENT_INTERCEPTOR, as afaik it's not used in CM.
Are you sure you have a notification light? None of the other variants have one.
Click to expand...
Click to collapse
Yep, notification light works fine in stock. at least tri-color (r/g/b). Will switch to the .config you sent. When I tried with the original usa_defconfig, the phone wouldn't boot.
Wow! Lucky you!
I'm pretty confident that's it's the same LED as in the regular S4 and the Mega, so you should be able to use this liblights: https://github.com/arco/android_device_samsung_melius-common/tree/cm-11.0/liblights
Also, you need to make the following changes to enable it: https://github.com/arco/android_dev...mmit/d002c6ee304e7caae71829b33135e26b5ea4e5f8
I'll need to figure out how to add this so it doesn't conflict with the variants that doesn't support it. Likely we need to move some stuff into device repos.
Btw, is this a GSM or a CDMA phone? If it's CDMA that may explain the network issues you have.
Ah right. It's a CDMA device. Yeah that will require some device changes. I'll look into it.
Just downloaded the kernel sauce for SPH-L520. Seems like it's using msm8930_serrano_defconfig as base config, and not the usa one. I'll need to compare what's different from the 9195 kernel, and also probably merge some code changes.
Related
As usual, pointing to the post concerning this ROM from its main team HERE
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-We've fixed PIE! It no longer decides to be invisible from time to time.
-We fixed the battery charge light! None of us use it but apparently you guys are just nuts for it!
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-3.4 kernel on D2xxx devices. It's finally stable enough where we're comfortable with this - remember to only flash other 3.4 kernels or it will not boot as there are rom-level dependencies.
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
Carbon change log HERE
6.02.13 -
Initial release "nightly" build
Fixed Camera
Fixed GPS
6.09.13 -
Synced to Chad0989's trees
Synced sources
Uses chad's -chad branch not fb branch kernel, crpalmer's kernel may work with this build.
6.11.13 -
HALO implemented
6.30.13
Code:
Synced back up with chad's trees
Synced with Carbon source
-Removed for space, post is to long
7.15.13
Code:
Device tree:
Updated with *SOME* of chad/flyhalf/crpalmer's recent work:
https://github.com/CM10DNA/android_device_htc_dlx/commit/b18cbc01baf535de447b44675727ca91b7548bea - cleanup more inline with cm *note* not all changes were done, it was causing issues with Carbon.
https://github.com/CM10DNA/android_device_htc_dlx/commit/9a01d0428755502b17cd2d5854fd293da9b6f143 - updates from m7
Kernel:
To many to list one by one, however visit here https://github.com/CM10DNA/android_kernel_htc_dlx/commits/cm-10.1-chad
And look back to june 30th which was my last pull.
Change log removed for space reasons (post is to long now)
8.06.13:
Tried out the BT fixes from Chad's CM10.2 stuff, so it may or may not work.
Current sources, should be the same as the 8.1.13 final stable releases for Nexus devices.
Change Log 8.06.13
The post is to big for XDA posts now, so instead I'll include a link to the changelog itself!
From here on ONLY use 4.3 gapps, I don't want to see any reports of broken cameras, keyboards or locking up if you are on anything besides a 4.3 gapps!
8.09.13
Fully updated to 4.3 Jellybean source
Fully updated to chad and crew's latest work on kernel/vendor/device
Use only the included kernel for now, crpalmer's 3.1.2 kernel is not fully compatible and will cause display and camera glitching.
Use only gapps for 4.3
A complete revamp of Carbon, they're starting over from the ground up so you may notice a lot of features missing, such as halo, expect these to return soon. What you can also expect is a smooth fast ROM with a solid foundation to build upon!
8.12.13
Updated source
BlueTooth now turns on (how well it works I can't test)
Single build, for now GSM is at least somewhat working on the CDMA build, so for now, pending further investigation, only a single "unified" version is available.
8.19.13
Updated souce
Updated with Chad and company's latest awesomeness
Features are beginning to trickle back in, Halo is back, etc.
Compatible with crpalmer's latest kernel (and .torrented's should also work)
Change Log 8.19.13
8.26.13
Updated Carbon source (ribbons?)
Updated with chad and groups work:
Device:
- Use correct mic for Google Search and other voice apps (bottom, not the top)
- Change back to HTCQualcommRil (from HTCCDMAQualcommRil) * CDMA build only
- Custom recovery graphics
- Sim hotswap will no longer prompt for reboot
- Everything from the 17th to today
https://github.com/CM10DNA/android_d...ommits/cm-10.2
Kernel:
- Hardware VSync support
- Missing clocks added
- ROW Scheduler added
- Everything done for the 14th to today, I'm not typing that all out
https://github.com/CM10DNA/android_k...ommits/cm-10.2
ROM:
- Carbon Fibers updated with a new swype style
- Ribbons returns from AOKP
- See change log on the site as usual
8.29.13
- Updated source
- Removed default showing of the overflow menu button, most hardware key map this and prefer to save the screen space.
- GSM Only: Changed default to WCDMA preferred from GSM/LTE: Should help with initial issues with calling/sms/mms maybe not working on some networks.
- Device, Kernel, Vendor trees otherwise untouched from last build.
- Listview Animations and Interpolator (Carbon Fibers > Interface)
9.13.13
- Updated source
- Built against the M7 kernel
- Includes everything done up to a couple of hours ago.
- NOT Global, CDMA and GSM versions will be needed still.
- CM's enhanced NFC added, I can't test it so any reports would be appreciated.
- MUST CLEAN FLASH THIS NO MATTER WHAT
- Compatible with crpalmer's 4.x.x kernels as far as I know.
9.13.13- B2
Removed qcom keystore to prevent hot reboot on display off.
9.13.13- CDMA B3
Correct issue causing bootlooping on the CDMA build, GSM didn't have it.
9.15.13
Updated source build:
Halo updates from PA
Add color support to text only battery
Fix network speed statusbar indicator traffic color on reboot
Fix reboot menu not being themed
Minor changes
9.16.13
Updated Carbon source:
Small stuff
Corrected QCOM keystore issue (thanks crpalmer)
9.23.13- Part Deux
Update 9.23.13
Updated Carbon source
All updates for the device/kernel sources.
Things that were messed with include the GPS HAL, some display stuff, camera stuff, and more. If you're interested in the details...
Device:
dlx: Import GPS HAL from jf
dlx: HTC camera expects insecure MM heap
dlx: enable option to set button brightness
Kernel:
Large amount, so I'll post the commits from last update, not each one. Not all concern the dna directly. Quite a few concerning bcmdhd, kgsl, msm_fb and other goodies
FROM HERE
TO HERE
Apparently the blank display was due to changes Carbon made to msm8960-common that I hadn't thought to look in on, and it changes quite a few things concerning the display. For now I have reverted to the CM common tree to correct the display issue.
12.5.13:
Initial bringup to KitKat 4.4
UNTESTED, CDMA Version only for now.
New folder for the 4.4 ROM here http://pio-masaki.com/DroidDNA/Carbon-KK
Please use an updated 4.4 GApps package!
Please CLEAN FLASH this only!
Please flash this with the latest 4.4 compatible recovery!
12.10.13:
CDMA only
Updated source and trees
I still can't test so those who had pervious issues (data, MMS) please give this a try and report when you have time.
1.22.14:
CDMA only, may be Global.
Updated build, untested as I lack the device now, please report any issues!
1.29.14:
Updated sources
Camera should work now
Please see if the Settings>Carbon Fibers> Interface FC still occurs.
As usual use the 4.4 GApps that has worked for you so far.
Not on pio-masaki.com yet, you can nab it now here http://d-h.st/Zsj
2.2.14:
Updated sources.
Camera and Interface FCs were corrected last build, should also be alright here.
4.4 GApps that you usually use.
Available on pio-masaki.com
2.5.14:
Updated sources.
Check that the carrier, date/day/whatever is proper and that the data connection icons are correct (IE no more roaming in 3G etc)
For those with speed issues, a report on that would be appreciated.
4.4 GApps that you used last time.
Available on pio-masaki.com
2.9.14:
Updated sources
Built because I was already on my 8th build of the day, why not?
4.4 GApps that you used last time.
Available on pio-masaki.com
2.20.14:
Updated sources
Built because my wife hates me and the couch sucks
4.4 GApps as usual
Available on pio-masaki.com
3.8.14:
Updated sources
Built because why not, its been awhile.
4.4 GApps as usual
Available on pio-masaki.com
4.7.14:
Updated sources
Built because its been a damn month, that's why!
4.4 GApps as usual
Available on pio-masaki.com
6.23.14:
4.4.4
Updated sources
JustArchi optimizations implemented
FULL 100% -03 built ROM, not just portions
Linaro 4.8 toolchain
Built as user instead of userdebug, odexes the ROM and disables some of the background logging
Updated Adreno candies
Peek
Available on pio-masaki.com in the usual place, however look in the SS folder as this is no longer just Carbon.
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
If you are not S-OFF you will need to extract the boot.img and flash it separately, either flashGUI or fastboot, your choice, needs done.
S-OFF:
Download the ROM for your needs, CDMA or GSM.
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup phone as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your phone in settings.
CDMA version: for use with Verizon, NOT for any other network.
GSM version: for use with GSM carriers, NOT for Verizon.
Global verison: for use with BOTH Verizon and GSM, no different build required
FAQS
If you didn't read the bugs list in the first post, go back up and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, that's basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. For now you can use the existing CM tree and build it that way. Any further help can be asked as needed.
Q. Can I use -insert kernel name here-?
A. No. Well ok you can, but please don't report any issues while running anything besides what came with the ROM.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyourass.zip"
Q. Can we do random bantering and good natured fun poking in your thread?
A. Sure, feel free to go OT on occasion, I'm all for having FUN on xda, even if some are not. I would like users to feel completely comfortable in my thread with no worries of me coming down on any thing not ROM or development related, I don't run a strict thread as many know by now. What I don't want is flame wars, though. Please keep a limiter on what is good natured fun as we all know things can get out of hand quickly. If someone is taking offense to something going on and its made known, please end it there with no hard feelings.
Bugs:
None specific to Carbon
Downloads:
Please visit pio-masaki.com for all my ROM builds
Kernel source used:
https://github.com/CyanogenMod/android_kernel_htc_m7
Whoop!!!! I heard rumors! I'm about to no sleep and flash this tonight...thanks so much for your hard work!
I downloaded this from your server and running it now. Seems very smooth and I like the breathing effect of notifications. You need to rest!
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Didn't notice the placeholder post? I was still making the posts lol
And yes, generally it will have whatever issues CM currently has.
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Goto www.pio-masaki.com and download from there
@pio,
Really nice work man.
Using it for the last 2 days and I can say that its the smoothest ROM out there. Paired with crpalmers kernel its SWEEEEEEEEEEET.
Tapatalked from TF300T with AOKP goodness
Pio is a ROM building machine! He probably dreams about code and bug fixes...lol
Websites going down at 3am CST for update and backup...only be down about 20 mins
Updates and backup done. Websites up.
Sent from my Nexus 7 using Tapatalk 2
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Epic 4g said:
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Click to expand...
Click to collapse
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
uppon2 said:
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
Click to expand...
Click to collapse
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Epic 4g said:
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Click to expand...
Click to collapse
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
diesburg said:
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
OK I will rename it "something.zip" as you said with out the quotations marks & flash. Thank you for the heads up. You are the man! :good:
Awesome going to flash this now! Does this include the halo framework or is that not released yet?
My head is spinning! Which way to I turn? Thanks pio!!
Sent from my HTC6435LVW using Tapatalk 2
I added the index.php issue to the FAQs last night.
Personally I use crpalmers kernel with this ROM, its great, by all means use it.
Personally I use carbon because I don't use PA features. Second is ReVolt, then PAC, though since the recent apps fix in PAC its a little harder to say lol
No halo in this, its in the works, though. The carbon team has released a special halo version for some devices a couple weeks ago, so it may happen once halo matures a little more.
Tapatalked from my HTC DNA - Carbon
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
coachcrey said:
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
Click to expand...
Click to collapse
It was fixed, also if you flash crpalmers kernel wifi will work as well.
Budwise said:
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
Click to expand...
Click to collapse
Its in /data/media, this is discussed numerous times in various threads so I won't get into much detail, but copy from /data/media to /0 and it'll work fine in 4.2 ROMs. To go back to a sense ROM move back from /0 to /data/media. After you can delete /0 but don't they to delete /data/media, just what may be in it as that's your internal SD card.
Tapatalked from my HTC DNA - Carbon
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.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Official CyanogenMod Wiki:https://wiki.cyanogenmod.org/w/Cherry_Info
Important information:
This thread is for official CyanogenMod 12.1 builds for Huawei Honor 4/4X (Qualcomm version). The following will not be supported here:
Custom kernels
Mods
Xposed
We 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
Baseband requirement:
Your must install a compatible baseband before CyanogenMod can be installed, or you won't be able to disconnect a call.
Just flash via recovery, you only need to perform the action once
Che1_L04
Che1_CL10
Che1_CL20
C8817D
G620S_UL00
G620S_L01
Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_cherry
Bug report: https://jira.cyanogenmod.org
Features:
Kernel based on official kernel source for Honor 4C(MSM8939), ported to MSM8916, update necessary drivers to QCOM lolipop baseline, and update from v3.10.28 to v3.10.49.
Many vendor blobs kang from rendang
Init scripts from Qualcomm's latest baseline: LA.BR.1.2.4-02710-8x16.0
Use open sourced charger
Set minium screen backlight to 5
Fix CPU Hotplug
Enhance Wifi signal strength (credits: @surdu_petru)
Fix multi-color battery & notifiction LED
Fix FLAC playback for some third-party players
Enable MTP by default
Add call recording
Add support for F2FS
Add PCC calibration interface
Add vibrator intensity control
Add double-tap-to-wake
Add glove mode
Add HW-based crypto support
Update CPU gorvenor driver from Qualcomm
Update thermal driver from Qualcomm
Update kernel scheduler and related syscalls (sched) from Qualcomm
Update memory manager from Qualcomm
Update lowmemorykiller from Qualcomm
Update bluetooth blobs from rendang
Enable KSM
Merge a bunch of kernel updates from Qualcomm baseline (see kernel commit for details)
Set SELinux to enforcing mode
If your device have an official lolipop port, please install that before install this CM port.
Supported devices:
C8817D
C8817E
G621-TL00
G620S-UL00
G620S-L01
Che1-CL20
Che1-CL10
Che1-L04
Installation:
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery, e.g., my TWRP with F2FS support: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-7-0-touch-recovery-t3199386
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Optional: Install the Google Apps addon package. OpenGAPPS recommended
Reboot
Download:
http://get.cm/?device=cherry
Credits:
Code Aurora Forum
CyanogenMod Team
surdu_petru
EloYGomeZ
ivan19871002
syhost
zhaochengw
mandfx
cofface
XDA:DevDB Information
CyanogenMod, ROM for all devices (see above for details)
Contributors
dianlujitao, surdu_petru
Source Code: https://github.com/cyanogenmod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: No Longer Updated
Created 2015-09-17
Last Updated 2016-02-14
Reserved
@Madhunath Already get solution for your device, read the thread and you'll find it
Thank You it's Really work full (Call hanging up issue Fixed) for Our Device Che1-L04.. :good:
dianlujitao said:
@Madhunath Already get solution for your device, read the thread and you'll find it
Click to expand...
Click to collapse
where is the solition dear?
Bug which i found
In MX Player if we Play any Videos then it's play good without any issue But if we Changed HW from SW then that Videos get reflecting like a light.. Hope it'll fixed in next build..
Request for a features !!!!
I Request you to can you please add Screenshot tile on Quick Setting Panel.. As we need to Press every time Volume Up + Volume Down Key for taking Screenshots.
Alternatively we can enable Screenshot Option from Settings> Buttons> Power menu.. But for this also need to Press Power Key. I want it on Quick Setting Panel.
Hope u'll add this features soon. Or if it can be enable by editing build prop then also let me know. How can i get this Screenshot Option in Quick Panel Setting as you mention that this Official CM12.1 doesn't Support any tweak or Xposed.
Thank You :good:
When we need to flash the baseband recovery , after wiping the data or before wiping data
Sent from my Che1-L04 using XDA Free mobile app
Raju Mondal said:
Thank You it's Really work full (Call hanging up issue Fixed) for Our Device Che1-L04.. :good:
Click to expand...
Click to collapse
How to fix call hanging issue?
Bharadwaz said:
When we need to flash the baseband recovery , after wiping the data or before wiping data
Sent from my Che1-L04 using XDA Free mobile app
Click to expand...
Click to collapse
Directly flash it.
wiping or not doesn't matter
Madhunath said:
How to fix call hanging issue?
Click to expand...
Click to collapse
Read the thread, baseband requirement part
Now G620S-L01 users can enjoy the nightly builds.
Follow the instruction, flash a suitable baseband, you won't get the dialer issue
I dont know why some issues are not mention in official CM bug report:
1. Audio totaly destroyed/not usable if ringtone volume is higher (AudioFX does nothing to speaker, not tested with headsets);
2. Compass not working - HERE IS how One Plus developer called Sultanxda, resolve the issue few weeks ago.. May be would help for our device too;
3. When forward youtube videos there is another issue - video stopped and needs to be reload;
Seems like everything else work as is...
PS: Does the modem needs to be one time installed to receive OTA updates, or every time when G620S-L01 receive update, the modem needs to be flashed again?
bmasgone said:
I dont know why some issues are not mention in official CM bug report:
1. Audio totaly destroyed/not usable if ringtone volume is higher (AudioFX does nothing to speaker, not tested with headsets);
2. Compass not working - HERE IS how One Plus developer called Sultanxda, resolve the issue few weeks ago.. May be would help for our device too;
3. When forward youtube videos there is another issue - video stopped and needs to be reload;
Seems like everything else work as is...
PS: Does the modem needs to be one time installed to receive OTA updates, or every time when G620S-L01 receive update, the modem needs to be flashed again?
Click to expand...
Click to collapse
The modem require only one installation, should be enough ( this will solve issue regarding Dialer, from some devices ) !
CM OTA flash only /system , /boot ( /recovery if you want ) partitions - so, modem partition will not be modified when you install a new update .
I just made a backup from my stock modem partition, just in case cannot receive officially Huawei OTA update .
Best regards !
bmasgone said:
I dont know why some issues are not mention in official CM bug report:
1. Audio totaly destroyed/not usable if ringtone volume is higher (AudioFX does nothing to speaker, not tested with headsets);
2. Compass not working - HERE IS how One Plus developer called Sultanxda, resolve the issue few weeks ago.. May be would help for our device too;
3. When forward youtube videos there is another issue - video stopped and needs to be reload;
Seems like everything else work as is...
PS: Does the modem needs to be one time installed to receive OTA updates, or every time when G620S-L01 receive update, the modem needs to be flashed again?
Click to expand...
Click to collapse
1: Will be fixed in the next cm nightly
2. can be fixed as long as huawei release lolipop kernel source
3. I've no idea
only need to flash baseband once
dianlujitao said:
2. can be fixed as long as huawei release lolipop kernel source
3. I've no idea
Click to expand...
Click to collapse
2. Very bad news. As my previous expirience with Huawei, should be miracle if officlialy update their phone even once.. what about sources..
3. @surdu_petru says in his thread, that already have solution and know how to fix the issue .. I hope you could include his fix to your release..
surdu_petru said:
I just made a backup from my stock modem partition, just in case cannot receive officially Huawei OTA update .
Click to expand...
Click to collapse
Would you share this with us, because I already flashed to test the Nightly with G7 modem..
bmasgone said:
2. Very bad news. As my previous expirience with Huawei, should be miracle if officlialy update their phone even once.. what about sources..
3. @surdu_petru says in his thread, that already have solution and know how to fix the issue .. I hope you could include his fix to your release..
Would you share this with us, because I already flashed to test the Nightly with G7 modem..
Click to expand...
Click to collapse
2. Already have official lolipop beta for honor 4x, when they release it, kernel source comes
3. I don't know about it
dianlujitao said:
3. I don't know about it
Click to expand...
Click to collapse
surdu_petru said:
About YouTube, I know how to fix this issue ... maybe I'll fix in the next update .
Click to expand...
Click to collapse
I hope there is a time to fix it before next release .. Higher Volume Ringtone + Youtbe fix .. and will remain just Compass when as you said Huawei release official sources .. :good:
bmasgone said:
I hope there is a time to fix it before next release .. Higher Volume Ringtone + Youtbe fix .. and will remain just Compass when as you said Huawei release official sources .. :good:
Click to expand...
Click to collapse
I decreased speaker volume to avoid boom, and increased voice call volume
Thank u so much for the Official CM, got a working and almost stable rom after a long wait, some issues found are
1.poor recieving of wifi signal, need to be closer to router to get proper signal
2.loudspeaker volume is very less usually when activate loudspeaker during a call and while playing recorded voice, whatsapp voices etc but playing music and videos are fine
3.Mobile data is not very stable, some time its not connecting even if its on
4.Camera clarity is low compared to stock camera, yellow colour appears all over the image while click using flash
One question> when new update comes in about phone> cyanogen update it download all 255mb file, is it possible to get only update file as ota?
Sent from my Che1-L04 using XDA Free mobile app
I DO NOT OWN THE ROM.
The developer of this rom is kumajaya on MIUI forum and thanks to him for his work.
MISSION:
Embarrass Xiaomi because refuse to release Redmi 2 kernel source
BUG:
Before you install this ROM, check your device magnetic sensor. Currently YAS537 not supported!
Still under development, built from sources, no hidden sources, not a binary dirty hack ROM
The following will not be supported in this thread:
- Custom Kernels
- Mods, including CPU management mod or any strawberry mod
- Modified system files
- Xposed
If you reuse even a part of my work here, a proper credit is a must, keep it open source also a must
Download:
Cyanogen and TWRP recovery: https://goo.gl/cDJQXI
CyanogenMod 12.1 ROM: https://goo.gl/zhGZjQ and https://goo.gl/5sqZGp
For better Google experience, install TK GApps Nano: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Don't create any mirror without a permission!
Cyanogen recovery above just like a standard AOSP recovery without a lot of features compared to TWRP, but you can temporary boot it using "fastboot boot cyanogen-recovery-wt88047.img" command to check if CyanogenMod 12.1 ROM possibly working on your device variant.
Don't even try this ROM on Redmi 2A variant!
Sources:
CyanogenMod source tree: [url]https://github.com/CyanogenMod[/URL]
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech
Changelog:
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047/commits/cm-12.1
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916/commits/cm-12.1-amss-1.0.2-wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech/commits/cm-12.1
Credits:
Google, AOSP, Cyanogen, CyanogenMod community, Qualcomm's CodeAurora @balika011, @zwliew, @Flour_Mo
Introducing me: XDA Recognized Developer, CyanogenMod contributor
My wife, she always believed I could restore back her device in minutes
Some tools: Kate (text editor), Kompare (diff viewer and generator), qgit (git GUI)
Smarfren Indonesia for Andromax Q source code
Micromax India for Yuphoria and Yureka source code
Current status:
Boot to Android, this is my first ROM that really boot on the first try
Touchscreen works, all hardware button mapped correctly
No screen flicker, fluid graphics
Voice call and SMS works, data over WiFi and GSM works (radio config in build.prop fix previous GSM issue)
Vibration and screen rotation works
All sensors seem works including GPS and compass but light sensor still need a fine tuning
Both camera working, the author found a super clean solution
No boot animation (fixed, kernel issue) Disable splash screen break Android boot animation but if I enable it, Cyanogen recovery covered by Tux the penguin logo in the center. The workaround solution, move Tux to the top right of the screen
No sound (fixed, kernel and user space issue) This also fix slow boot because of logcat flooding. BUG: Speaker output ignore headset jack insertion, sound out from both speaker and headset
Bluetooth file transfer fail (~42MB zip, failed at 17%) WiFi file transfer way faster
FM radio works
WiFi hotspot works
YouTube and local video 720p works
LED driver working great, multi color and blink
Remember, no contribution from Xiaomi yet. That's the reason why I try to avoid "Xiaomi" string in my source as possible but Wingtech.
I use CyanogenMod resources as much as possible, including common MSM8916 device tree and kernel. Maintain device source tree and leave common part to CyanogenMod community. I'll strictly follow CyanogenMod coding style and source structure. This is about source code quality.
AGAIN, I DO NOT OWN THE ROM.
Will try it soon. And I hope Xiaomi will release the kernel like Redmi 1s.
kumajaya and zwliew are the most stable CM12.1 roms for our phone. I hope they reach 100% full working version in near future.
Thank you both!
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
How about some screenshots?
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
crzlloid said:
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
Click to expand...
Click to collapse
There is a link in my post about the changelog and the YAS537 is still not yet supported.
zwliew said:
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Sorry, but I have already talk to kumajaya about it. Then he ask me to help him on requesting an official sub-forum for our device. Anyways, if anyone here oppose me about posting this thread, then maybe I should delete this.
wow, using this in 2020, 5 years later.
Hi All,
I've been working on a CAF version for osprey. This is started from kernel and device tree made by Alberto97 and Squid2, so thanks a lot to them for the bringup.
This version is very early and should only be flashed by people who know what they are doing. Flash this at your own risk.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
For now only a few things are working:
Working
Bluetooth
SMS/RIL
Sound
Camera
Not work
Binaries
Here
Sources
https://github.com/boulzordev/local_manifests/tree/caf-6.0
XDA:DevDB Information
CAF-6.0 [Surnia], ROM for the Moto E 2015
Contributors
scritch007, squid2, Alberto97
Source Code: git://codeaurora.org/platform/manifest.git
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP
Based On: CAF
Version Information
Status: Testing
Created 2015-11-16
Last Updated 2016-01-04
Changelog
surnia-caf-87.zip
Updated to latest version of CM13 device specific + CM13 kernel)
Updated to LA.BR.1.2.7-00910-8x09.0.xml (February security patch)
Fixed the ringtone setting issue
Using frameworks_av from CM13 from now on.
surnia-caf-86.zip
Only tested on my Osprey and Lux, so still in testing folder
Fix setting ringtone
Fix invalid number error when the call is ended by the other end
Sepolicy from cm imported (getting ready for Sepolicy being enabled)
surnia-caf-85.zip
Settings for light management ( When opening settings values reset to default)
Dual sims outgoing should be fine now
Updated frameworks_av with CM commits
Now building osprey/lux/surnia at the same time, this is why the version is 85
Backup script when flashing in recovery. This works with open gapps. This means gapps are copied and restored when flashing
surnia-caf-0.10.zip
Dual sim outgoing calls/sms fixed (tested on Lux). Thanks to @Men_in_black007 for pointing out the missing commit
Fixed exfat external storage
MM bootanimation added. thanks to This thread
surnia-caf-0.9.zip
Updated to 6.0.1
Now using commonized msm8916 like cm13 will do
Using libshim from cm for the missing symbols
There is a bug the initial bootanimation doesn't seem to load. But it loads once rom is started and optimising applications.
surnia-caf-0.7.zip
Didn't have time to test it
The google webview
"Maybe the reboot option"
The time.sleep for the camera3 application that was posted somewhere in here
Let's hope exfat sdcard working too
surnia-caf-0.6.zip
Dual sim support (Reported OK)
Fix an issue with wifi bootloop after installing gapps (Can't really tell the trigger, but it's fixed )
surnia-caf-0.5.zip
Sdcard is now mounted and can be mounted in mtp. Still some issues about the state in the getprop and so on, but data are accessible
Fixed the OEM unlocked button issue.
surnia-caf-0.4.zip
Video Recorded can be viewed
Change Language doesn't crash anymore when accessing to phone config (if I missed some languages please tell me I'll fix them too)
surnia-caf-0.3.zip
Initial version
ohhh I'm glad to be working on 6.0 for our Surnia. Keep up the good work, thank you.:victory:
nice job?thanks
Wow thanks bro!
good work
Any specific recommended gapps? I get force closes and play service errors from open gapps.
This ROM will support Dual Sim Surnia versions like unified cm12.1?
starkly_raving said:
Any specific recommended gapps? I get force closes and play service errors from open gapps.
Click to expand...
Click to collapse
The ROM has to have a patch to support gapps now. It says so on their website when you click 6.0.
cmason37 said:
The ROM has to have a patch to support gapps now. It says so on their website when you click 6.0.
Click to expand...
Click to collapse
@scritch007 we need this commit for gapps to work on CAF/AOSP...its already upstream in CM13...
https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a
I tested on a XT1527, and it works incredibly good only there's two issues:
1)When switching from wifi to Mobile Network (i think after a data connection, i don't know exactly) the phone freezes up, and after it shutdown to bootlogo. (i will try to provide you a logcat)
2)The mobile network doesn't work, i think so, the google search didn't response
Anyways, it's an incredible work, and keep it going! Thanks for porting Android 6.0 to our device
Wow, just tested, & everything pretty much works. The only bugs are gapps, SD Card, & the occasional random reboot. Everything else, including 4G, worked. I tested all the apps, & sideloaded chrome to test browsing/video. Once we get the gapps & SD Card fixed, it's pretty much daily driver material. Thanks, @scritch007!
starkly_raving said:
@scritch007 we need this commit for gapps to work on CAF/AOSP...its already upstream in CM13...
https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a
Click to expand...
Click to collapse
This is already there https://github.com/boulzordev/android_frameworks_base/commits/caf-6.0
But thanks for looking into it .
@all look at the Moto G 2015 thread, some of the errors/solutions are already posted there.
RIL seems to be broken in my X1521...sim card isn't getting detected
Just tried this on my XT1521... no RIL because this is dual SIM, and no microSD, but nonetheless, great work! The ROM was extremely fluid in the few moments I used it, and fixing those issues, I would have no issues in using it as a daily driver.
scritch007 said:
This is already there https://github.com/boulzordev/android_frameworks_base/commits/caf-6.0
But thanks for looking into it .
@all look at the Moto G 2015 thread, some of the errors/solutions are already posted there.
Click to expand...
Click to collapse
It seems that the issue is actually WebView. When opengapps installs, it installs Google Webview, and since this ROM is still configured to use AOSP WebView, it doesn't work. @scritch007 you actually need this commit.
surnia-caf-0.4.zip
Video Recorded can be viewed
Change Language doesn't crash anymore when accessing to phone config (if I missed some languages please tell me I'll fix them too)
@NSDCars5 thanks updated the change log. It was taken from osprey, which didn't get previous version
@scritch007
Video recording worked fine in the last build too, I just couldn't see the recorded video in Marshmallow (in Lollipop I could see what I'd recorded in Marshmallow). So does this mean we can see recorded video in the ROM itself?
Question
scritch007 said:
surnia-caf-0.4.zip
Video Recording
Change Language doesn't crash anymore when accessing to phone config (if I missed some languages please tell me I'll fix them too)
Click to expand...
Click to collapse
When you say SD doesn't work, you mean it doesn't recognize it at all? Or is it only a minor issue? Just wondering.
Sorry for the question but on XT1524 works this?
I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.