[ROM] KarbonKat v1.2-3 (5/1/15) [Carbon/CM11][4.4.4-r2]
This ROM was put together after the maintainers of CarbonDev moved on from this phone as it was no longer building successfully with the standard build process for CarbonROMs. The amazing work they'd done had made everyone want this ROM working on this phone as it was fast, stable and had the latest features from AOSP code. They did an amazing job so I used the base code, added the pure CyanogenMod device trees and started posting this ROM from then on. Unfortunately my build server was behind a firewall so it couldnt' be part of the Carbon build system hence why this ROM was born. So the kudos for this ROM has to go to the original developers at Carbon, CyanogenMod and of course AOKP plus a little snippet from PAC-Man to get the latest build stable and working!
The original ROM is on this thread: CarbonRom JB
It uses HBoot 2.18.0000, has SimplePIE, OmniSwitch, CarbonFibres, PowerSaver mode, Performance tweaks, built-in root, themer support, Daydream, Apollo music player and it's fast!
Without further ado here's the ROM plus source location, Gapps to use and firmware to use:
KarbonKat v1.1-5 10/09/2014
KarbonKat v1.1-6 19/09/2014
KarbonKat v1.1-7 22/09/2014
KarbonKat v1.1-8 29/09/2014
KarbonKat v1.1-9 08/10/2014
KarbonKat v1.1-11 22/10/2014
KarbonKat v1.1-12 28/10/2014
KarbonKat v1.2-0 02/12/2014
KarbonKat v1.2-2 18/12/2014
KarbonKat v1.2-3 5/1/2015 latest stable 4.4.4 version!
BaNKs Gapps for 4.4.3: Goo.im folder
PA Gapps for 4.4.2 to 4.4.4: Paranoid Android Gapps
TWRP Recovery download section now at 2.8.0.0
TWRP Recovery new encryption
TWRP Recovery old encryption
All files on Android File Host: KitKat and JB uploads
Full ChangeLogs can be worked out from these:
CyanogenMod Review for the CM device and kernel trees and CarbonDev's Review for the rest!
My own source is available via http://github.com/Aronar
Firmware in use on my phone: 5.14.61.2-3.17.61.1
XDA:DevDB Information
KarbonKat, ROM for the AT&T HTC One X
Contributors
Soenisti
Source Code: http://github.com/Aronar
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 2.7+, Firmware from 5.14.61.2-3.17.61.1
Based On: CarbonDev,AOSP,CyanogenMod
Version Information
Status: Nightly
Current Stable Version: 1.2-3
Stable Release Date: 2015-01-05
Created 2014-09-11
Last Updated 2015-01-05
Scozzar said:
Why the new thread?
Click to expand...
Click to collapse
This was when I created the DevB info page it created this thread automatically.
Excuse my ignorance, but what you mean with "Firmware"?
Mexickano said:
Excuse my ignorance, but what you mean with "Firmware"?
Click to expand...
Click to collapse
Firmware is the BIOS for the phone essentially.
I just thought I'd let you know latest version of the ROM has been running smooth for 2-3 days now. I only had one reboot and I forgot to catch the last_kmsg. But otherwise it's been great
Subjectively this is the fastest ROM I've ever run on this device, no reboots thus far. Only bug is bluetooth audio stuttering/speeding up or slowing down occasionally but that is a bug in all AOSP roms at this point. Thanks!
nicolahaye said:
I just thought I'd let you know latest version of the ROM has been running smooth for 2-3 days now. I only had one reboot and I forgot to catch the last_kmsg. But otherwise it's been great
Click to expand...
Click to collapse
I just have a reboot recently, how can I get the last_kmsg? maybe it can help to the dev.
Mexickano said:
I just have a reboot recently, how can I get the last_kmsg? maybe it can help to the dev.
Click to expand...
Click to collapse
Right after your phone rebooted you open an app called terminal emulator (that's the one I use) and type the following lines
su
cat /process/last_kmsg > /mnt/sdcard/last_kmsg
Then you're gonna have a file called last_kmsg on the sdcard
What Kernel do you recommend to use?
sometimes I can check my WiFi connections cuz never open the wifi options, I have to reboot my device to connect and see the options
Everything mess up since I installed that firmware, omg.
Mexickano said:
What Kernel do you recommend to use?
sometimes I can check my WiFi connections cuz never open the wifi options, I have to reboot my device to connect and see the options
Everything mess up since I installed that firmware, omg.
Click to expand...
Click to collapse
As a reference alternative you could always try the latest torched for 4.4 as that contains fixes for wifi problems as well in 4.4.4-r2.
Soenisti said:
As a reference alternative you could always try the latest torched for 4.4 as that contains fixes for wifi problems as well in 4.4.4-r2.
Click to expand...
Click to collapse
4.8 or 4.8 oc doesnt works for me, I lost the conection so fast.
Mexickano said:
4.8 or 4.8 oc doesnt works for me, I lost the conection so fast.
Click to expand...
Click to collapse
Did you clean flash ? cause I've been on stock kernel with this ROM for more than a week and it's been an example of stability :highfive:
Sent from my One XL
nicolahaye said:
Did you clean flash ? cause I've been on stock kernel with this ROM for more than a week and it's been an example of stability :highfive:
Sent from my One XL
Click to expand...
Click to collapse
Yes, I did, but I dont know what happened that wifi setting doesnt work, it works sometimes and later I have to reboot my device more than 3 times.
i always have to reenter the password for my wifi whenever my battery dies completely. not really a big issue to me but i haven't noticed that on any other roms before. incredibly stable otherwise.
Anyone have HDR working in Google Camera? Mine is missing the option, flashed PA Full Gapps.
sephiroth2k said:
Anyone have HDR working in Google Camera? Mine is missing the option, flashed PA Full Gapps.
Click to expand...
Click to collapse
Have you tried the stock versions of Gapps instead?
unblanking screen bug
can anyone shed some light on this wierd bug im having...
im coming from sense rom with latest firmware and recovery and every aosp rom im flashing (4.4.4)
has this wake screen bug.
once my screen turns off it wont turn on again.
i tried logging and came up with this line: Unblanking display: 0, after locking screen.
i searched google and found similar issues but no answers.
any ideas?
b_ophir said:
can anyone shed some light on this wierd bug im having...
im coming from sense rom with latest firmware and recovery and every aosp rom im flashing (4.4.4)
has this wake screen bug.
once my screen turns off it wont turn on again.
i tried logging and came up with this line: Unblanking display: 0, after locking screen.
i searched google and found similar issues but no answers.
any ideas?
Click to expand...
Click to collapse
Hi,
I think it's an ongoing bit that's being developed in the qcom code as there have been quite a few changes there recently. Have you tried resetting screen lock as a way to work around it? Is pocket mode enabled?
Soenisti said:
Hi,
I think it's an ongoing bit that's being developed in the qcom code as there have been quite a few changes there recently. Have you tried resetting screen lock as a way to work around it? Is pocket mode enabled?
Click to expand...
Click to collapse
i tried it all yes. disabled all features related to screen but didnt try pocket mode
Latest version posted! Seems nice and stable and works with Torched 5...
Related
WildKernel
for AT&T Samsung Galaxy S II
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
v013: AFH
TRU Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
[#WildKernel-Celox-CL]
[/HIDE]
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultanxda
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
My recommended Governor/Scheduler setups:
Battery w/ Good Performance at 96-1350mhz:
Intellidemand/SIO (personal choice)
Lazy/SIO
Badass/SIO
Ondemand/SIO
Wheatley/SIO
'lil more Performance at 96-1512mhz:
Smartass/SIO
Hyper/Deadline
Samsung/Deadlne
lulzactive/Deadline
Savagedzed/Deadline
Best Performance (worst battery): 384-???mhz
Gaming/Deadline
Performance/Deadline
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the AT&T Galaxy S II (skyrocket), Kernel for the AT&T Samsung Galaxy S II Skyrocket SGH-I727
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_samsung_msm8660/tree/android-msm-skyrocket-3.0
Kernel Special Features: Too many features to list, just install it.... now.
Version Information
Status: Stable
Current Stable Version: 013
Stable Release Date: 2015-01-29
Created 2014-10-15
Last Updated 2015-02-01
Tried to install but keep getting an md5 error and a message about getprop device not equaling.
Downloaded and tried twice...
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Installer zip fixed, please re download if you downloaded kernel before seeing this message....thanks!
The new installer worked, thanks. I'll play around with it and report back but I can already say that WiFi direct doesn't work (it's always the first thing I check b/c it's the only problem I have with any of the skyrockets current kernels)
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
tsew2674 said:
The new installer worked, thanks. I'll play around with it and report back but I can already say that WiFi direct doesn't work (it's always the first thing I check b/c it's the only problem I have with any of the skyrockets current kernels)
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure that problem is directly related to the kernel? It sounds more like a Rom issue....does it work on your rom's stock kernel?
Emmanuel U said:
Installer zip fixed, please re download if you downloaded kernel before seeing this message....thanks!
Click to expand...
Click to collapse
I guess the burning question for me if this includes all of Sultan's bluetooth fixes. His kernel for CM really is the gold standard for our device thus far.
I see you mentioned him in the OP so I am hopeful lol. I'd love to be able to flash this kernel with any rom knowing the usual plagues (such as the constant BT disconnect) are no longer an issue.
Thanks a lot for this! Nice to see the SR still getting some love
Emmanuel U said:
Are you sure that problem is directly related to the kernel? It sounds more like a Rom issue....does it work on your rom's stock kernel?
Click to expand...
Click to collapse
I'm pretty sure it's at the kernel level only because it works with @Sultanxda's kernel. His is the only 4.4.x kernel that WiFi direct has ever worked on for me on the skyrocket. It worked on the official CM10.2 ROMS/kernels but every since CM11 was introduced it's been broken. The ROM I'm using now could connect with WIFI direct when built with Sultan's kernel.
Even with Sultans kernel, Miracast (with uses WIFI direct) will connect but the graphics are all scrambled. I suspect that has to do with some of the memory enhancements he's made. If I knew how to build kernels I'd like to try using the official CM11 kernel source and only applying his WIFI direct commit to see what the results are, but unfortunately I don't know how to build them and can't seem to find the time to do the research to learn. Maybe one day.
I've had no issues otherwise and I've been using it for a few days now. Thanks
I tried flashing usin dirtya unicorns i can get oast boot logo ut restarts
raptorddd said:
I tried flashing usin dirtya unicorns i can get oast boot logo ut restarts
Click to expand...
Click to collapse
Once your screen goes black from the reboot, hold both the volume buttons until your device goes into recovery. Then either use ADB or your recovery's file manager to retrieve /proc/last_kmsg and it post it here. It always helps to present issues with a log ready, for future reference.
So... I got bored.
I installed the following ROM's and got bootloops for each (basically every 4.4.4 ROM I know of for Skyrocket):
AOKP - Dated 15-Sep-14
CM11 - Dated 19-Oct-14
PacRom - Dated 25-Aug-14
Mokee - Dated 12-Oct-14
Dirty Unicorns - Dated 2-Oct-14
SlimKat - Dated 14-Oct-14
CarbonRom - Dated 17-Oct-14
Beanstalk - Dated 9-Oct-14
CandyKat - Dated 18-Oct-14
Paranoid - Dated 9-Oct-14
I didn't test the following ROMs:
SultanXDA CM11 - Dated 19-Oct-14 Didn't test since I was told it would bootloop
MIUI V6 - Currently getting a bootloop so no reason to try it
Emmanuel U said:
Once your screen goes black from the reboot, hold both the volume buttons until your device goes into recovery. Then either use ADB or your recovery's file manager to retrieve /proc/last_kmsg and it post it here. It always helps to present issues with a log ready, for future reference.
Click to expand...
Click to collapse
Never done this before (well, I know how to get into recovery...lol). I'll post the file in a few minutes after reflashing one of the ones above. Can i empty this folder when I'm done? There's 200 or so subfolders in there.
ETA: Added attachment.
xonelith said:
So... I got bored.
I installed the following ROM's and got bootloops for each (basically every 4.4.4 ROM I know of for Skyrocket):
AOKP - Dated 15-Sep-14
CM11 - Dated 19-Oct-14
PacRom - Dated 25-Aug-14
Mokee - Dated 12-Oct-14
Dirty Unicorns - Dated 2-Oct-14
SlimKat - Dated 14-Oct-14
CarbonRom - Dated 17-Oct-14
Beanstalk - Dated 9-Oct-14
CandyKat - Dated 18-Oct-14
Paranoid - Dated 9-Oct-14
I didn't test the following ROMs:
SultanXDA CM11 - Dated 19-Oct-14 Didn't test since I was told it would bootloop
MIUI V6 - Currently getting a bootloop so no reason to try it
Never done this before (well, I know how to get into recovery...lol). I'll post the file in a few minutes after reflashing one of the ones above. Can i empty this folder when I'm done? There's 200 or so subfolders in there.
ETA: Added attachment.
Click to expand...
Click to collapse
Hmm interesting, since I dont have this device, I can't do this myself. But do u think u can you do the following?
1. Flash one of the Roms you listed that bootlooped above
2. Open my kernel installer and delete /system/bin/thermald
3. Push it to your device and install
4. Does it boot?
Emmanuel U said:
Hmm interesting, since I dont have this device, I can't do this myself. But do u think u can you do the following?
1. Flash one of the Roms you listed that bootlooped above
2. Open my kernel installer and delete /system/bin/thermald
3. Push it to your device and install
4. Does it boot?
Click to expand...
Click to collapse
Sadly, bootloops again (I installed the AOKP rom; clean, no GApps, let it boot once, boot to recovery and flash modified zip).
xonelith said:
Sadly, bootloops again (I installed the AOKP rom; clean, no GApps, let it boot once, boot to recovery and flash modified zip).
Click to expand...
Click to collapse
Too bad i hope emmanuel fix this.. Anything i can do ..
Reboots
I was playing around in Tame earlier and my phone rebooted a few times. I wasn't doing anything too crazy, turned off SweepToWake, changed the governor to Lazy and it froze and rebooted. The first time it happened I had changed the max frequency and a couple of other things, so I attributed the reboot to that, however when it booted back up I only changed the two items mentioned above and it rebooted again, this time it stayed off so I booted into recovery and got the kMsg, hopefully it helps. That's not the first time I've used Tame, I initially installed it, changed a few things and everything was fine, but my phone had been turned off since then so I was going back in to set it back the way I had it.
I'm currently using the liquidsmooth as my ROM, and this is really the first issue I've had with your kernel (other than WIFI direct, but that's pretty much all the kernels for this device). I think you've even improved my battery life, I don't do gaming or anything so I don't really ever notice any performance gains or that sort of thing, but I haven't noticed anything moving slower, which is good.
Update
Another minor update today, sorry about the initial discrepancies! Blame me, since I don't actually have this device. Well it should boot on all ROMs now, enjoy .... I guess.
Works great on PA! I'll mess with it for a bit and provide useful feedback.
Sent from my SGH-I727 using XDA Free mobile app
Flashed successfully on Carbon 10/17 nightly. Seems pretty snappy so far. Nice work! :thumbup:
Hi. Thanks for sharing this Kernel. I have a question...
Before, I was using Carbon with its stock kernel, Conservative governor and noop; there was no lag at all, but battery seems to last too little time in continous use and even when it was with screen off. Even before that, the CPU governor was set by default at Interactive, but the Skyrocket freezes in several times, sometimes after unplug it from charger or after unlocking it after a time (like 1 hour or something), sometimes the device hangs so long until I reboot it or it reboots itself. So, Interactive isn't the best choice for me.
The question is: What is the best choice for a governor if I want the longest battery life, but with any freezing any time?
Could you please help me?
franzpimp87 said:
Hi. Thanks for sharing this Kernel. I have a question...
Before, I was using Carbon with its stock kernel, Conservative governor and noop; there was no lag at all, but battery seems to last too little time in continous use and even when it was with screen off. Even before that, the CPU governor was set by default at Interactive, but the Skyrocket freezes in several times, sometimes after unplug it from charger or after unlocking it after a time (like 1 hour or something), sometimes the device hangs so long until I reboot it or it reboots itself. So, Interactive isn't the best choice for me.
The question is: What is the best choice for a governor if I want the longest battery life, but with any freezing any time?
Could you please help me?
Click to expand...
Click to collapse
See the OP for ny recommendations.
Emmanuel U said:
See the OP for ny recommendations.
Click to expand...
Click to collapse
Yes, I'm sorry, I forgot to say that actually I'm using Lazy governor at 96-1350 and sio as you recommended it, but I thought that maybe there's a no listed recommendation for maximun battery or something like that.
CyanogenMod 11 and 12 by ivanichFeatures:
3.4 kernel with latest patches
USB-OTG
Stable enough to be daily driver
Fully working camera
In kernel mp-decision
Bugs:
Major:
No one
Minor:
VoiP - BuiltIn VoIP client - no audio, also VoIP apps like Hangouts crashes when "Ok Google" enabled (CM-12)
All CyanogenMod upstream bugs
All thanks goes to ivanich, not me. I'm just started new thread.
Downloads:
CM11
CM12
GAPPSCM11 and CM12 final buildsSources:
ivanich's GitHub
Changelog:
Kernel Changelog
ROM Changelog
TWRP Recovery:
Download
XDA:DevDB Information
CyanogenMod11 and 12 by ivanich, ROM for the HTC Sensation
Contributors
Daniiiik49, ivanich
Source Code: https://github.com/ivanich?tab=repositories
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 1.27/1.29
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Stable Release Date: 2016-12-30
Created 2014-10-19
Last Updated 2016-12-03
CM12 BugsMajor:
Audio
Camera
Video recording
Mobile Data
GPS
Video playback
Minor:
Video recoding in 1080p is broken
All CM upstream bugs
All Android 5.0 bugs
First you should put link into @ivanich github for source
EXTRAS:
SD-EXT Boot MOD - by hinxnz
http://forum.xda-developers.com/showthread.php?t=3068867
Google apps:
ivanich said:
cm12.1 require 5.1 gapps, found this GAPPS thread and PA GAPPS
Click to expand...
Click to collapse
I've just try to install this rom but sensation xe give me error installatio aborted (status 0)
mdr04 said:
I've just try to install this rom but sensation xe give me error installatio aborted (status 0)
Click to expand...
Click to collapse
update your recovery version
SD card problems?
First of all thanx a lot to ivanich and all others involved in the efforts of bringing up-to-date software to our manufacturer-abandoned hardware. Big thumbs up! :good:
I came to this rom some weeks ago from Albinoman887's CM10.1 which worked out quite well for more than a year now. Due to the space-consuming updates of the gapps i ran out of memory and searched for a more recent rom. Using this for two weeks now leaves me quite happy except one thing.
I expierience constant and sudden unmounts of the SD-Card, quite like papete mentioned them in the old thread for this rom.
Is this there anthing i can do on my side, to overcome this behaviour configuration-wise?
Could it be that i need a special firmware for this rom to work properly?
Getting rid of this problem would definetly let me use my Sensation for at least an other ten months or so.
@Sajito , seems like I've found a workaround for LPA seek bug. Could you test it on your builds. Also If I remember correctly there was issue with lpa and bluetooth - can you check this too?
https://github.com/ivanich/android_...mmit/9093a8f1f4bef98fbf89b54bcdb1e735e0a821bc
On latest build and clean install, SystemUI force close when changing or adding quick tiles. CM upstream issue?
saldymhmd said:
On latest build and clean install, SystemUI force close when changing or adding quick tiles. CM upstream issue?
Click to expand...
Click to collapse
It's not very hard to find at gerrit, isn't it ? http://review.cyanogenmod.org/#/c/75384/
Uploaded new build with this commit included.
ivanich said:
@Sajito , seems like I've found a workaround for LPA seek bug. Could you test it on your builds. Also If I remember correctly there was issue with lpa and bluetooth - can you check this too?
https://github.com/ivanich/android_...mmit/9093a8f1f4bef98fbf89b54bcdb1e735e0a821bc
Click to expand...
Click to collapse
I will merge that commit and make a build with that and lpa enabled.
I'll report back tomorrow.
Just remembered that in the last builds carbonrom seems to have a bug with playing music via bluetooth in general. It connects, but music plays always from phone, if lpa is enable or disabled doesn't matter. Gonna test it anyway.
dirty flash
Hi, I've got two questions:
Can updates be flashed as dirty flash? I flashed the ROM's previus version three days ago with full wipe, it's ok to dirty flash the new one?
It's mandatory to flash gapps in a dirty flash?
Thanks.
kastlell said:
Hi, I've got two questions:
Can updates be flashed as dirty flash? I flashed the ROM's previus version three days ago with full wipe, it's ok to dirty flash the new one?
It's mandatory to flash gapps in a dirty flash?
Thanks.
Click to expand...
Click to collapse
You can dirty flash ROM updates always. If you experience problems, do a clean install.
Gapps usually don't need to be reflashed after an update.
This is for every rom the same.
@ivanich I've tried that commit on my own for normal playback and everything seems to be fine at least on paranoid android. Carbon seems to have issues with music at the moment.
Couldn't test bluetooth yet, someone else needs to test that.
I remeber that Skype audio was not working when phone display is off, so I guess this could be a good test to try LPA, can't test myself unfortunately atm
banesi said:
I remeber that Skype audio was not working when phone display is off, so I guess this could be a good test to try LPA, can't test myself unfortunately atm
Click to expand...
Click to collapse
LPA is not used with skype or similar apps.
http://forum.xda-developers.com/showpost.php?p=40281352&postcount=6
@ivanich I just tested your latest build and even with that one I'm not having any issues with seeking with lpa enabled.
After disabling touch sounds everything is perfectly fine.
But for some reason in my roms neither in carbonrom, nor in aospa audio over bluetooth is working. May I ask you for your local_manifest?
Sajito said:
@ivanich I just tested your latest build and even with that one I'm not having any issues with seeking with lpa enabled.
After disabling touch sounds everything is perfectly fine.
But for some reason in my roms neither in carbonrom, nor in aospa audio over bluetooth is working. May I ask you for your local_manifest?
Click to expand...
Click to collapse
http://pastebin.com/mXqKaG4i
ivanich said:
http://pastebin.com/mXqKaG4i
Click to expand...
Click to collapse
I don't get it. I use the same kernel and device trees, I didn't change anything to the audio or anything that could affect it and yet still audio over bluetooth is broken in my builds while it's working perfectly fine here...
Sajito said:
I don't get it. I use the same kernel and device trees, I didn't change anything to the audio or anything that could affect it and yet still audio over bluetooth is broken in my builds while it's working perfectly fine here...
Click to expand...
Click to collapse
So you built cm11 by yourself and got bt audio issues or it's broken only in carbon/aospa? Check repos in your build tree, maybe you changed something directly in code, in that case repo sync wont overwrite changes.
Seems I know why you are not experiencing issues with lpa seek. I've rebooted phone and start GooglePlay Music, seek issue almost not noticeable in this app, then I started Apollo and no seek issue again, but then I looked into logcat and realized that after I exited from GooglePlay Music it puts LPAPlayer into underrun state so lpa not worked after I've started Apollo.
EDIT: Returning to GooglePlay Music app shows in logcat that lpa is working again, probably there is something wrong with Apollo
slim
I am opening new thread for SlimKAT rom because @phoenixita not building ROM anymore and it is easier to have newer thread.
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the ROM.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
Kernel Source - The source of your device's kernel.
XDA:DevDB Information
[UNOFFICIAL] [4.4.4] [S4] SlimKAT, HBOOT 2.15, ROM for the HTC One S
Contributors
mikronac.ns, rc
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.15 HBOOT
Version Information
Status: Stable
Created 2014-10-25
Last Updated 2014-12-04
I like slimrom, I'm happy to see this post !
One simple thing... there's a way to reduce the resolution ?!
truevision said:
I like slimrom, I'm happy to see this post !
One simple thing... there's a way to reduce the resolution ?!
Click to expand...
Click to collapse
Install build.prop editor from Play and change LCD Density param to 240 or 256.
mikronac.ns said:
Install build.prop editor from Play and change LCD Density param to 240 or 256.
Click to expand...
Click to collapse
240 is default right? I always set mine to 200 or 190.
Looks a lot slicker in my honest opinion.
Verstuurd van mijn One S
mikronac.ns said:
Install build.prop editor from Play and change LCD Density param to 240 or 256.
Click to expand...
Click to collapse
I know this method, I think there was an option in the rom, because is very unusable with default dpi.
But, is not possible to set 240 to default ?
Sorry, do not want to sound cocky, I just think if you try this rom and it shows like this, maybe you leave it immediately, only to see this resolution.
PS for who want to keep Google out from our life: there is
Performance Control (System configuration) - https://f-droid.org/app/com.brewcrewfoo.performance
for manage build.prop and many other stuff. ?
I'm on this rom from few days... all right so far... no reboot, no strange behaviour, battery drain seems ok.
truevision said:
I'm on this rom from few days... all right so far... no reboot, no strange behaviour, battery drain seems ok.
Click to expand...
Click to collapse
Nothing is sexy like slim
Hboot 2.16
Will it be available for Hboot 2.16 ?
Zrel said:
Will it be available for Hboot 2.16 ?
Click to expand...
Click to collapse
heres one i made a week ago https://www.androidfilehost.com/?fid=95747613655049854
for use root access, is necessary to install an App (like Supersu), right?
truevision said:
for use root access, is necessary to install an App (like Supersu), right?
Click to expand...
Click to collapse
Check also in Dev Options if you have enabled root access to apps and ADB
@truevision @mmarkvoort Are you experiencing random reboots on ville with SlimKAT or any other rom which I am buildin'?
mikronac.ns said:
@truevision @mmarkvoort Are you experiencing random reboots on ville with SlimKAT or any other rom which I am buildin'?
Click to expand...
Click to collapse
Good morning!!
When i first started using LS i had no reboots. But after a few updates and restores they started happening once in a while.
I'm on AICP now. Had it running on stock kernel with no reboots for 3 days. Now installed IceCode and until now no problems. (1,5 days)
I'll keep you posted if anything happens.
Sent from Holland with my One S
mikronac.ns said:
@truevision @mmarkvoort Are you experiencing random reboots on ville with SlimKAT or any other rom which I am buildin'?
Click to expand...
Click to collapse
I'm using slimkat from about 10 days, no one reboots, no one strange behavior and great battery, so far seems a very rock rom ! thnx !
truevision said:
I'm using slimkat from about 10 days, no one reboots, no one strange behavior and great battery, so far seems a very rock rom ! thnx !
Click to expand...
Click to collapse
It make sense because SlimKAT is not using CyanogenMOD kernel. It is Slim's msm8960 kernel. I am buiding new version. I synced mms application with CM's one because I like send delay option, it's useful in some situations... I will test if it works and if so, I will upload it on AFH, if not... building it again This rom is really amazing and sexy like a slim
EDIT: building again...
have someone trouble with bluetooth ?
I try to use my bluetooth earphone but don't work.
I will test this ROM soon, I like slim very much.
Thanks to the OP !
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I wanted to use some extra features like fast charge, thus flashed bubba kernel, latest version that is for 4.4 based ROMs. I thought a kernel for AOSP based ROMs is the right choice. After reboot I cannot turn on WiFi.
Did I choose the wrong kernel?
LT
Sent from my One S using XDA Free mobile app
linuxteddy said:
Hi,
I wanted to use some extra features like fast charge, thus flashed bubba kernel, latest version that is for 4.4 based ROMs. I thought a kernel for AOSP based ROMs is the right choice. After reboot I cannot turn on WiFi.
Did I choose the wrong kernel?
LT
Sent from my One S using XDA Free mobile app
Click to expand...
Click to collapse
Bubba was not updated for a loong time by rmbq. He moved to another device. Therefore the last builds are not containing latest wifi related commits and are not compatible with any of the latest built ROMs. If you want to use Bubba, look into the IceCode kernel thread, somewhere on the last pages, AKToronto has compiled latest Bubba including wifi commits. It's called Bubba Zombie Edition. You can use that one, it works (this is what I use also). Or you can use latest IceCode from the same thread, but it does not have dt2w/s2w
Sent from nowhere over the air...
only to confirm a rock ROM... also with latest update seems always all right!
Great work mikronac... great work...
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
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.
/[B]Submitting bug reports on nightly builds is the leading cause of male impotence[/B].
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Root:
HERE - By @autoprime
Recovery:
TWRP HERE
Instructions:
First time flashing CyanogenMod 11 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Already on CM11, try a dirty flash.
Reboot into recovery
Make back up <optional>
Wipe cache, system, dalvik-cache
Install ROM, GApps and optional Superuser app
Reboot
Bug Reports: How to report a bug?
Check post #2 to see if it has been reported.
Search thread first or at least attempt to. Yes, we all know XDA can be difficult to search but try to search this thread only first.
If you have issues and have used TiBu or any other app restore program then perform a clean install without restoring apps to see if you can replicate before reporting.
List the following info: ROM build date, what you were doing and can you replicate it.
Get a logcat if possible.
Download: CM11 nightly builds
HERE
Google Apps: Optional add on package that allows Google Play services such as Google Play Store and other Google Apps outside of AOSP based ROMs.
Check THIS post
Changelog:
CyanogenMod Change Log HERE
G3 Specific Change Log HERE
AndroidUser00110001 Change Log HERE
invsisblek Change Log HERE
XDA:DevDB Information
Cyanogenmod 11, ROM for the AT&T LG G3, ROM for the AT&T LG G3
Contributors
timmytim, invisiblek, AndroidUser00110001
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Nightly
Stable Release Date: 2014-12-05
Created 2014-12-08
Last Updated 2014-12-09
Mine!
Nice
??
Official CM11 at last, this is great! I clean flashed and everything is very stable so far, especially for a nightly.
Sent from G3 running CM11
Congrats on being official!
Mind opening up the Q&A? There's no Q&A tab yet.
Thanks for all the hard work!
Maroon Mushroom said:
Mind opening up the Q&A? There's no Q&A tab yet.
Thanks for all the hard work!
Click to expand...
Click to collapse
The QA Bot hasn't created the thread yet. If it isn't created by tomorrow then I will make sure one gets opened. Thanks for letting me know
Moved to PM
Will give this a shot. Thanks m8.
Any known issues (camera/video, etc...)?
How is this running ? I'm on power user ROM cause its awesome with rin kernel. But I always have to have some Cm... Running good ?.. Yo Tim have you heard anything on ir blaster integration ? Its kind of a must have. Are you running this ? Hope all is well.!:thumbup:
2SHAYNEZ
shayneflashindaily said:
How is this running ? I'm on power user ROM cause its awesome with rin kernel. But I always have to have some Cm... Running good ?.. Yo Tim have you heard anything on ir blaster integration ? Its kind of a must have. Are you running this ? Hope all is well.!:thumbup:
2SHAYNEZ
Click to expand...
Click to collapse
Personally I'm now running my Candy5 ROM. I'm loving me some Lollipop!
shayneflashindaily said:
How is this running ? I'm on power user ROM cause its awesome with rin kernel. But I always have to have some Cm... Running good ?.. Yo Tim have you heard anything on ir blaster integration ? Its kind of a must have. Are you running this ? Hope all is well.!:thumbup:
2SHAYNEZ
Click to expand...
Click to collapse
Super smooth! No hangups yet!
@timmytim did they stop making nightly builds? Haven't seen one go live since Dec 6th.
objektive_1 said:
Super smooth! No hangups yet!
@timmytim did they stop making nightly builds? Haven't seen one go live since Dec 6th.
Click to expand...
Click to collapse
I dont think so. CM skips nightlies for some reason, not sure why. Hopefully we will see one tonight or tomorrow night at the latest.
timmytim said:
I dont think so. CM skips nightlies for some reason, not sure why. Hopefully we will see one tonight or tomorrow night at the latest.
Click to expand...
Click to collapse
This is stable enough for me to use as an everyday (12/6 nightly). Will OTA update list show when an official stable version releases? Will I be able to update CM versions OTA using the update feature in settings? Great work last CM i used was CM 7 for my HTC One X hahaha:good::good:
timmytim said:
I dont think so. CM skips nightlies for some reason, not sure why. Hopefully we will see one tonight or tomorrow night at the latest.
Click to expand...
Click to collapse
tonight it is... 20141209 is there :good:
Camera quality seems to be great on CM11. I tested this next to a stock Verizon G3 and the only difference I noticed between the 2 would be the color temperature. One macro image I took with both was noticeably better on the one with CM11.
so does the laser auto focus still seem to function correctly with this?
is there any real way to verify that it is working except supposed time to capture image by estimation
Best flashed rom yet... Tried Liquid Smooth and ran into a bunch of different issues and wanted something more stable. This runs fast and smooth, no issues as of yet. Wish the LG quick remote would one day work on this rom. Thanks for posting!
Bodymore420 said:
Best flashed rom yet... Tried Liquid Smooth and ran into a bunch of different issues and wanted something more stable. This runs fast and smooth, no issues as of yet. Wish the LG quick remote would one day work on this rom. Thanks for posting!
Click to expand...
Click to collapse
Try a universal remote and report back..... Or maybe making your own universal remote through qremote
2SHAYNEZ
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure