The two glitches I am noticing is there is still no functional camcorder, and the stock launcher has difficulties with the OK Google decorations.
Other than that, (if that's not a deal breaker) then it's quite the solid ROM. Worth trying out.
[ROM][EOL][CARBON][KK 4.4.4] CarbonROM (MT4GS)
- Thread starter OfficerJimLahey
- Start date
-
- Tags
- carbon rom development htc kitkat
- Status
The two glitches I am noticing is there is still no functional camcorder, and the stock launcher has difficulties with the OK Google decorations.
Other than that, (if that's not a deal breaker) then it's quite the solid ROM. Worth trying out.
The two glitches I am noticing is there is still no functional camcorder, and the stock launcher has difficulties with the OK Google decorations.
Other than that, (if that's not a deal breaker) then it's quite the solid ROM. Worth trying out.
Can the in-call volume be adjusted while using headphones? A typical mt4gs bug since CM9.
Would probably be one of those gems buried in the device tree somewhere. I'm not sure where to look nor if it would interact with something else.
I realize it's a common complaint over the years, which leads me to be believe that (a) nothing can be done about it or (b) it's just been overlooked since CM9 due to the complexity of what is all there (and the priority of the time was to make sure the tree was still build-able due to newer CM code).
I am a bit overwhelmed by what all gets defined there, and I don't know where to start.
Did the problem morph over the years? At one point I remember it always full blast...
EDIT: I did find we are not the only one. The T-Mo S3 uses the msm8960 chipset, so I am looking at commits around that time. Had to dive into CM-11.0 branch since 10.2 petered off around that time, yet I still don't see anything relevant.
Unless "BOARD_USES_ALSA_AUDIO := true" has some significance for us.
UPDATE:
Probably not. If it does, it requires more work than setting one flag...
Last edited:
As I remember, the msm8960 is built with Krait cores and is a part of Snapdragon S4 Plus family, while Doubleshot uses msm8260 with Scorpion cores. But T-Mobile S2 has same msm8260 chipset as Doubleshot has.
You are right, they (T-Mo S2 and MT4GS) share the same chipset, which is actually msm8660.
I will take a look at their issues and device tree at some point, to see if I can find any clues.
UPDATE:
From What I see, the T-Mo S2 does not have the issue. There is also nothing glaring from the Common Board Configs.
Theirs:
Code:
# Audio
BOARD_HAVE_SAMSUNG_AUDIO := true
BOARD_USES_LEGACY_ALSA_AUDIO := true
BOARD_QCOM_TUNNEL_LPA_ENABLED := true
BOARD_QCOM_VOIP_ENABLED := true
TARGET_QCOM_AUDIO_VARIANT := cafOurs:
Code:
# Audio
COMMON_GLOBAL_CFLAGS += -DHTC_ACOUSTIC_AUDIO -DLEGACY_QCOM_VOICE
TARGET_QCOM_AUDIO_VARIANT := caf
BOARD_QCOM_TUNNEL_LPA_ENABLED := false
BOARD_USES_LEGACY_ALSA_AUDIO := true
BOARD_QCOM_VOIP_ENABLED := trueWhile googling flags, I think I may have found the problem:
http://xdaforums.com/showpost.php?p=36768155&postcount=747
http://xdaforums.com/showpost.php?p=36854107&postcount=753
http://xdaforums.com/showpost.php?p=36856840&postcount=754
Does not seem the solution has been found.
Last edited:
Isn't msm8660 a CDMA-only chipset? That's not really important but I know that the only difference between msm8260 and msm8660 is the cellular radio support (GSM and CMDA). And Doubleshot happens to be a GSM device, thus it should be using msm8260.
I've seen that the newer Sensation (XE) ROMs (at least CM11 based ones) have up to 630 Mbs of RAM available while we only have 520 Mbs available. And the hardware is identical: 768 RAM, msm8x60. How is this possible?
I've seen that the newer Sensation (XE) ROMs (at least CM11 based ones) have up to 630 Mbs of RAM available while we only have 520 Mbs available. And the hardware is identical: 768 RAM, msm8x60. How is this possible?
Apparently they can do both.
http://system-on-a-chip.specout.com/l/284/Qualcomm-Snapdragon-S3-MSM8660
http://system-on-a-chip.specout.com/l/290/Qualcomm-Snapdragon-S3-MSM8260
I've seen that the newer Sensation (XE) ROMs (at least CM11 based ones) have up to 630 Mbs of RAM available while we only have 520 Mbs available. And the hardware is identical: 768 RAM, msm8x60. How is this possible?
Emman took some out for the kernel. His plans was to return some later on, I may have to see what he did originally and make some tests. :fingers-crossed:
Also, methinks our kernel has to be revamped (get above 3.0) in order for CM12+. I'm not up for that. Besides, I don't know what kind of dirty tricks the Sensation dev's did for CM12/13, but they have less storage space than us, and we are already fighting at the limit without ART. They must have took a page from the HTC Dream book and repartitioned the internal block and offloaded most of the storage to the SD card.
If so, we would have to do a bit of that ourselves, and that is quite dangerous. Anyway, as long as CM keeps maintaining monthly security level updates for CM11 (probably likely until this time next year), I will keep applying them to the Carbon build.
Sometimes I wonder why I even bother...
I found the commit that limited our usable memory to 518MB. I reverted it in a sense, that is, allocated 2/3 of what was taken it back into user-accessible, and built from there. That gives us a new total of...wait for it...524MB! :silly:
So if I reverted completely (probably a bad idea as the extra kernel allocation means something on the kernel end), we would have ended up with a whopping 527MB of usable RAM.
So there is something else going on, that was tweaked long ago. At any rate, I put that build up on AndroidFileHost, if you want to grab it.
Attachments
Hey, I notice an update to this ROM was uploaded on 01/08...were you able to fix any of the issues mentioned in the first post? I might have to go back to this phone for a bit as my current one is acting all wonky and am trying to decide on a ROM to use.
Thanks!
Thanks!
Same issues as OP, update was just the January security patches.
Hope this helps.
Sent from my ASUS_Z00AD
Last edited:
warning! This rom may cause your buttons to stop functioning permanetly
I installed this ROM in two different phones. I wiped the phones 5 times first. On the second boot I started getting Google play services has stopped error and youtube and Google play has stopped. Then all buttons seased to function . ALL HARDWARE BUTTONS! EVEN AFTER FLASHING PG59 THE BUTTONS STILL DO NOT WORK. I KNOW MY BUTTONS ARE FINE BECAUSE THEY ALL WORK IN HBOOT!
I installed this ROM in two different phones. I wiped the phones 5 times first. On the second boot I started getting Google play services has stopped error and youtube and Google play has stopped. Then all buttons seased to function . ALL HARDWARE BUTTONS! EVEN AFTER FLASHING PG59 THE BUTTONS STILL DO NOT WORK. I KNOW MY BUTTONS ARE FINE BECAUSE THEY ALL WORK IN HBOOT!
I never had this problem. Sounds like the wrong gapps for starters...
Can you explain the process taken to flash?
Last edited:
Just wanted to let you know that someone else appreciates your (and all the other contributors) support for this legacy phone (noticed in your filehost you have been continuing to upload your build w/the latest security patches). I have been out of the custom ROM/cooking biz since WINCE (the original windows mobile) but finally gave up on MS and in process of getting back into Android I wanted to get back into flashing and without experimenting on my newly purchased LG G4. I dug out my old DS and in the matter of one long day I had unlocked, S-Off, rooted, and flashed this ROM (and a few others before it). Definitely due more to the overall excellent community for their toolsets and documentation than my skill. Thought it would be a one-off experiment but so impressed with the life breathed back into this phone I am actually planning to use it for awhile while tackling my G4.
I got the same problem with CM9, I installed android 4.0.1, working perfectly by a few hours, but then , the (menu, back, home and geniuos) buttons stop working, all the oders work fine, with a reboot its fine to get them back to work, but then a few hours happends the same, I'm going to try Carbon ROM and see if it fix this....
I'm trying to install this ROM
CARBON-KK-UNOFFICIAL-20151213-2320-doubleshot.zip
MD5: 023864307a38b61d154e5679b229809b
but in TWRP I got a message of error, and the install aborts. Someone have face this issue?
CARBON-KK-UNOFFICIAL-20151213-2320-doubleshot.zip
MD5: 023864307a38b61d154e5679b229809b
but in TWRP I got a message of error, and the install aborts. Someone have face this issue?
Hi,
Which TWRP are you using? I recommend TWRP 2.6.x.x at this point. If using that already, what is the error?
Also, the December 2015 build is quite old now. Check the first post for the updated ones, hosted by AFH.
Good point... I'm using TWRP v2.2.2.1 looks like its kinda old xD. Okay let me try it with v2.6... Thanks
---------- Post added at 06:36 PM ---------- Previous post was at 05:56 PM ----------
---------- Post added at 06:36 PM ---------- Previous post was at 05:56 PM ----------
Thanks Jim Lahey, you're right with TWRP v2.6xx its possible to install your ROM. Were is the last update that you mention?, I find as the "most recent" the one I mentioned.Hi,
Which TWRP are you using? I recommend TWRP 2.6.x.x at this point. If using that already, what is the error?
Also, the December 2015 build is quite old now. Check the first post for the updated ones, hosted by AFH.
Last edited:
AFH Mirror in the downloads section, first post in thread.
Okay, I'm glad for your attention, I will try the new one. the older one seems very smooth. Love my old DoubleShoot :fingers-crossed: is nice to see him with Andorid OS 4.4.4
if I find any bug I'll give you feedback.
:highfive:
Last edited:
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
8hLe Storm ROM 4.4.4
Looks like I graduated from ArchiKitchen, now compiling from source and I may be on to something here. But first...
Code:#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and * YOU acknowledge you are doing so at your own risk. */
Now that that's out of the way, hLe Storm (pronounced "hailstorm") 4.4.4 is a build of CarbonROM, using the kernel from @Emmanuel U (among advice), and device identity and other projects from Team KitKatDS. As CarbonROM is EOL (end-of-life) as of April 5th (or earlier), some commits have been taken/"cherry picked" from CyanogenMod 11 source.
SCREENSHOTS:
WHAT WORKS:
- Powers on
- Phone calls
- SMS and (after using the busybox trick) MMS
- Mobile Data (HSPA detected with my carrier)
- Wifi
- Google Play
- GPS, based on GPS Status & Toolbox
- Camera via UCam app, also now stock and Google Camera
- Torch
- Needs further testing
WHAT DOES NOT WORK:
- Camcorder in stock app records nothing
- Probably the same for any replacement Camcorder app (encountered this problem earlier this month)
- No detail in the Google Search bar with the default launcher (search and voice search still work, just need to tap blindly)
- You tell me...
TODO:
- Continue to extensively test current functionality.
- Suggestions?
DOWNLOAD:
- AndroidFileHost Mirror
- CARBON-KK-UNOFFICIAL-20151213-2320-doubleshot.zip (MD5: 023864307a38b61d154e5679b229809b)
GAPPS:
INSTRUCTIONS:
- Download ROM above, and your favourite GApps package
- Save/push files to your External SD card (preferably in the root folder where you can find it later)
- Reboot into recovery ("adb reboot recovery")
- Nandroid/Back up device (optional)
- Wipe cache and data/factory reset
- Install ROM and GApps
- Wipe Dalvik cache
- Reboot
- Enjoy!
CREDITS:
- Emmanuel U for the Ion Kernel and other repo fun
- Team KitKatDS for the Device Tree and Vendor Info plus other goodies
- TeamSXL
- TeamHydra
- SilverL
- TBalden
- thewisenerd
- streambinder
- galaxyfreak
- CyanogenMod
- CarbonDev
Did I miss anything? I appreciate the feedback, and any thanks as well!
XDA:DevDB Information
[ROM][EOL][CARBON][KK 4.4.4] CarbonROM (MT4GS), ROM for the T-Mobile myTouch 4G Slide
Contributors
joel.maxuel
Source Code: https://github.com/carbon-mt4gs
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: No Longer Updated
Beta Release Date: 2015-12-13
Created 2015-05-27
Last Updated 2016-08-284Update later today...
As many may know, Kitkat is end-of-life, or near EOL, depending on the ROM you use. For CarbonROM, it have been EOL for several months now (when the commits stopped occurring), but for CyanogenMod, they are still maintaining critical patches all the way down to CM10.1 (which will probably cease soon).
Because of Stagefright issues, I wanted to re-do CM10.1 at the very least. But I was plagued with build errors. I got a build, but the robbing and stealing I did in the build phase made sure it didn't boot. So it seems CM10.1 is un-buildable at this point.
I then turned to CarbonROM. Because Carbon is close to that of CM in the code, I was able to cherry-pick any new android_frameworks_av commits (where the stagefright problem(s) are found), and get a successful build.
I am pleased to say, unlike out-of-the-box (EOL) CarbonROM 4.4.4, this build is not vulnerable - at least until the next round comes out...D'Oh!
I will be uploading the build tonight.Uploaded - see 1st post.2
Have merged KitKatDS/android_frameworks_av with CarbonDev/android_frameworks_av into my github, hopefully that will work. I figured out the missing parameter, and see in CameraParameters.cpp that it's just a dummy function. But it turns out I needed more than just the function and the call to it. Luckily I could do an automatic merge (because I am not up for the manual way - yet).
Going to be a few more hours compiling before I can figure out if that worked (my poor dual-core PC is working hard).
Eventually I want to get the CarbonDev commits into android_frameworks_native, but that will be a manual process (3 files to edit by hand) when I looked at the compare.
EDIT: Finished earlier than I thought. And a healthy camera init:
Torch now works as well, but when I open the stock Camera app (which is now there), I get "Unfortunately, Camera has stopped." Strangely, works fine in UCam. IP Webcam works as well, but I tried a few camcorder apps out there and neither worked.
CLEANUP of old thoughts:
So the latest change involving turning down face detection didn't work. Still getting the same error. A user on StackOverflow pointed out that what I was featuring from the logcat was secondary to the actual problem. That this is a more complete picture:
Code:E/QualcommCameraHardwareZSL( 170): Invalid focus mode value: continuous-picture E/QualcommCameraHardwareZSL( 170): virtual android::status_t android::QualcommCameraHardware::setParameters(const android::CameraParameters&): 6487, rc = -22 ... E/AndroidRuntime( 2700): FATAL EXCEPTION: Camera Handler Thread E/AndroidRuntime( 2700): Process: com.android.camera2, PID: 2700 E/AndroidRuntime( 2700): java.lang.RuntimeException: setParameters failed E/AndroidRuntime( 2700): at android.hardware.Camera.native_setParameters(Native Method) E/AndroidRuntime( 2700): at android.hardware.Camera.setParameters(Camera.java:1696) E/AndroidRuntime( 2700): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298) E/AndroidRuntime( 2700): at android.os.Handler.dispatchMessage(Handler.java:102) E/AndroidRuntime( 2700): at android.os.Looper.loop(Looper.java:136) E/AndroidRuntime( 2700): at android.os.HandlerThread.run(HandlerThread.java:61)
So it was a parameters problem after all! I looked up continuous-picture in (my copy and KitKatDS's) frameworks_av and it is listed, and not hidden behind any #ifdef's. So it should pick up. I just don't know how to tackle this one at this point (if I ever had a clue).
Any further suggestions @Emmanuel U, @thewisenerd, @streambinder, @galaxyfreak, @tbalden? Thanks for all the help so far.1It really seems like CM's support for KitKat is wrapping up.
July's security patches are a month behind now. I will keep watch, but with Nougat on the way, support for KitKat is going to be very few and far between (much like CM 10.1's treatment this time last year - only being revived to deal with Stagefright issues) and I don't imagine my updates will last beyond this year.
It's been a good run, I will do what I can (if those changes get merged I will include them in a new build), but there is no point to continue building something when the build environment itself has not changed.
EDIT: A day later, I got my wish. July and August security patches are merged now and new builds (one for inclusion of each month) done.
FINAL EDIT: According to this commit, it's all over. CM11 is (really) no longer supported, and weekly builds have stopped. I found out through their IRC. Since there will be no Android Security Bulletins brought in (which have become increasingly difficult), this is where this project ends as well.
Downloads will remain on AFH, and my GitHub will stay where it is, but I may clean up some of the older downloads in the coming months (only showcase the ones for this year).
I have thoroughly enjoyed having this as my first build device.
All that is left now is to close the thread. Take care.
