yashsingh1/xdaforums huggingface dataset:
[Xperia Z2 Q&A, Help & Troubleshooting] TheFerhatKing:
Hey,

i don't know how this problem comes, but my problem is that my sd card don't mount when I boot into the system (lolipop), I have to put the card out and then again in, thats the way how its working again. But I don't want to do this every boot :(View attachment 3254262
[Xperia Z2 Q&A, Help & Troubleshooting] TheFerhatKing:
Fixed it with installing nuts recovery thanks to nut! Thread can be closed now
[Moto G Q&A, Help & Troubleshooting] 3dd1:
I've got a XT1039, still to get lollipop, seeing how badly it has effected my wife's XT1032, despite clearing the cache in recovery, and seeing that the Google Play Edition of the XT1032 already has 5.1 released, I am hoping that the XT1039 will jump straight to 5.1, what do you think the chances are?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
hLe 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...

#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 [MENTION=4193353]Emmanuel U[/MENTION] (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:

OpenGapps Mini

OpenGapps Micro

OpenGapps Nano

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-28
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Other Info...

Anyone looking to develop KitKat ROM's for the Doubleshot? This Local Manifest will give you a good start: :D

If looking to compile updated CarbonROM 4.4.4 for this device, you can start your build environment with:

mkdir carbon
cd carbon
repo init -u https://github.com/carbon-mt4gs/android.git -b kk && repo sync -f

Then continue all the build steps as normal. :cowboy:
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
What looks to be the first problem I encountered...camera:

/proc/kmsg

logcat

Essentially (via logcat):

D/[UCAM]CameraHolder( 9650): Open camera 0
E/CameraService( 170): CameraService::connect X (pid 9650) rejected (invalid cameraId 0).
W/CameraBase( 9650): An error occurred while connecting to camera: 0
E/[UCAM]CameraHolder( 9650): Fail to connect Camera
E/[UCAM]CameraHolder( 9650): java.lang.RuntimeException: Fail to connect to camera service

...and kmsg:

<4>[ 2831.616455] ------------[ cut here ]------------
<4>[ 2831.616546] WARNING: at /home/joel/carbon/kernel/htc/doubleshot/fs/sysfs/dir.c:455 0xc02879d8()
<4>[ 2831.616668] sysfs: cannot create duplicate filename '/devices/virtual/kgsl/kgsl/proc/9650'
<4>[ 2831.616821] Modules linked in:
<4>[ 2831.616943] Function entered at [<c010cc1c>] from [<c01940e0>]
<4>[ 2831.617034] Function entered at [<c01940e0>] from [<c0194218>]
<4>[ 2831.617156] Function entered at [<c0194218>] from [<c02879d8>]
<4>[ 2831.617218] Function entered at [<c02879d8>] from [<c0287ba0>]
<4>[ 2831.617370] Function entered at [<c0287ba0>] from [<c03c49c4>]
<4>[ 2831.617431] Function entered at [<c03c49c4>] from [<c03c51c0>]
<4>[ 2831.617553] Function entered at [<c03c51c0>] from [<c045c5f8>]
<4>[ 2831.617675] Function entered at [<c045c5f8>] from [<c0457cf4>]
<4>[ 2831.617767] Function entered at [<c0457cf4>] from [<c022c3c4>]
<4>[ 2831.617767] Function entered at [<c022c3c4>] from [<c02252d4>]
<4>[ 2831.617767] Function entered at [<c02252d4>] from [<c02265e0>]
<4>[ 2831.617767] Function entered at [<c02265e0>] from [<c0236c6c>]
<4>[ 2831.617767] Function entered at [<c0236c6c>] from [<c0238630>]
<4>[ 2831.617767] Function entered at [<c0238630>] from [<c0238d28>]
<4>[ 2831.617797] Function entered at [<c0238d28>] from [<c02266e4>]
<4>[ 2831.617797] Function entered at [<c02266e4>] from [<c0106c40>]
<4>[ 2831.617797] ---[ end trace debad88b1f20abd4 ]---
<3>[ 2831.617797] kobject_add_internal failed for 9650 with -EEXIST, don't try to register things with the same name in the same directory.

Well well well, I guess we cannot be perfect, and my work is far from done. Drat. :p

Guess I may have to commit this? EDIT: I did, and it made no difference.

Just for fun, I also have a logcat from bootup time. Namely of interest:

E/HAL ( 170): load: module=/system/lib/hw/camera.vendor.msm8660.so
E/HAL ( 170): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters15setPostviewSizeEii" referenced by "camera.vendor.msm8660.so"...
E/CameraWrapper( 170): failed to open vendor camera module
[T-Mobile myTouch 4G Slide] tbalden:
you might need some legacy build parameters for htc camera callbackd, and maybe some patch in the camera header hw part so that the proprietary camera module could fit with the os. I think Emmanuel's repos will contain what you may need.
[T-Mobile myTouch 4G Slide] Emmanuel U:
Lemme compile my own build later today and back to you, I think my github is missing something I have locally
[T-Mobile myTouch 4G Slide] Emmanuel U:
So I just reproduced the error build on my side, I'll be playing around with it later today when I have time.

Edit: so fixed the error with the focus modes, so the camera functions. But now the camcorder isnt working properly. It records but something fails when it stops recording and it doesn't save the video. I'll keep you posted.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
That was quick! Must be only recompiling the Camera2 apk (never figured out how to do that - although never really looked - except maybe drag the project into Eclipse).

So what is the focus mode fix? I can compile with that and see if my camcorder crashes as well.
[T-Mobile myTouch 4G Slide] Emmanuel U:
You should always steer away from hacking ROMs to fix an error, as the issue is usually on your side. https://github.com/KitKatDS/android...mmit/6ec8fea20ce4ef854f634b4ad0389986b9e4eb2e
[T-Mobile myTouch 4G Slide] Dukenukemx:
A new rom for my old MyTouch 4G slide?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
That's right. :cowboy:

I wanted to see what compiling from source is like, and since my daily driver (Fx3Q) has a few bits needed before development can be fruitful (need device tree), I figured I would build for the Doubleshot.

As Emman has pointed out, there are so many competing priorities with the newer ROM's thanks to newer devices that older devices can barely keep up and maintain their mark in the existing code.

I don't have the skill set to change that problem, but I will go along and debug away.

This ROM doesn't make any promises, it's just a change in perspective (presenting CarbonROM instead of having CM as the only KitKat ROM). And if I get bored enough in a months time (assuming the major bugs are squashed - I sure hope so), I just might try out another perspective.
[T-Mobile myTouch 4G Slide] Emmanuel U:
So this is my current logcat.

I'm concerned about this line

E/OMXCodec( 170): [OMX.google.h264.encoder] ERROR(0x80001001, 0)
E/MPEG4Writer( 170): The number of recorded samples is 0

That hex error code points to OMX_ErrorUndefined. I'm thinking I'm overlooking something because the road can't end here haha. I call it quits for tonight because I got a paper due in a few hours, but I'll hop back on it soon.

Edit: btw this is where the camcorder records but when trying to end the recording, it fails and it's like you never recorded a video. I have some local changes, but no point in uploading them yet because they haven't shown any signs of being beneficial. However, my change from before should fix your native_set_parms error. Later, I'm gonna remove a decent amount of unneeded lines from the camerawrapper.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
I see this is now your new enemy. How are those wrinkles coming? :p

Possibly related (further up):

E/SoftAVCEncoder( 170): Failed to initialize the encoder: -8
E/AudioHardwareMSM8660( 170): cur_rx for pcm playback = 2

So from my view, the crash has to do with checking the video content, but finding a null file.

Makes sense, in my earlier post about finding no camcorder app that actually worked, well, I did find one that didn't crash at the outset (or ever), but it didn't record anything.

Too bad any search for "E/SoftAVCEncoder Failed to initialize the encoder: -8" comes up with four results, all unrelated to our situation.
[T-Mobile myTouch 4G Slide] Dukenukemx:
I'll certainly keep an eye out for this rom. I'd like to bring back the MyTouch4G Slide with a working fast rom.
[T-Mobile myTouch 4G Slide] Emmanuel U:
Well those errors seem to be inherent from the OMX error, earlier in the logs.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
From my question in Stackoverflow:

Looks like we cannot just comment out/remove that line, more like remove the offending focus mode (or modes if we find more) from it.
[T-Mobile myTouch 4G Slide] Emmanuel U:
Yea we can, the problem isn't with the wrapper. That line was never supposed to be there anyway because we don't need to override the detected focus values. It's something in the framework....or else my KitKatDS wouldn't work either. I'm still on a busy streak but I'll dive into it soon I promise lol.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Update 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. :D
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
November 14th build...

...is on AndroidFileHost at the moment, will add to DevDB later today.

In short, this fixes the SF2.0 problems. Will be updating the OP shortly.

Enjoy! :cowboy:
[T-Mobile myTouch 4G Slide] Dukenukemx:
This rom is still being worked on? Does it fully work? Can I finally go back to a QWERTY phone?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
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. ;)
[T-Mobile myTouch 4G Slide] SKAm69:
Can the in-call volume be adjusted while using headphones? A typical mt4gs bug since CM9.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
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...

joel@oven:~/carbon$ make carbon -j5
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.4
CARBON_VERSION="CARBON-KK-UNOFFICIAL"-20151212-2303
TARGET_PRODUCT=carbon_doubleshot
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=scorpion
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-4-amd64-x86_64-with-debian-8.0
HOST_BUILD_TYPE=release
BUILD_ID=KTU84Q
OUT_DIR=/home/joel/carbon/out
============================================
Checking build tools versions...
/home/joel/carbon/out/target/product/doubleshot/obj/APPS/SignatureTest_intermediates
find: `src': No such file or directory
build/core/dynamic_binary.mk:44: *** hardware/qcom/audio-caf/legacy/alsa_sound: LOCAL_MODULE not defined before call to local-intermediates-dir. Stop.
joel@oven:~/carbon$
[T-Mobile myTouch 4G Slide] SKAm69:
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.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
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:

# 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 := caf

Ours:

# 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 := true

While 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.
[T-Mobile myTouch 4G Slide] SKAm69:
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?

And Sensation also has CM12 and CM13 :p
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
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

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.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Sometimes I wonder why I even bother... :p

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.
[T-Mobile myTouch 4G Slide] Posarius:
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!
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
Same issues as OP, update was just the January security patches.

Hope this helps.

Sent from my ASUS_Z00AD
[T-Mobile myTouch 4G Slide] HepCatChris:
Wow that's cool you are making something for this phone. Keyboard phone love!
[T-Mobile myTouch 4G Slide] escort5speed:
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!
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
I never had this problem. Sounds like the wrong gapps for starters...

Can you explain the process taken to flash?
[T-Mobile myTouch 4G Slide] shdmitch:
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.
[T-Mobile myTouch 4G Slide] bullracing:
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....
[T-Mobile myTouch 4G Slide] bullracing:
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?
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
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. :cowboy:
[T-Mobile myTouch 4G Slide] bullracing:
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 ----------

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.
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
AFH Mirror in the downloads section, first post in thread. :cowboy:
[T-Mobile myTouch 4G Slide] bullracing:
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:
[T-Mobile myTouch 4G Slide] OfficerJimLahey:
It 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.
[Verizon Samsung Galaxy S6] sincerity:
Coming from turbo and none of my play store apps downloaded...is this normal?
[Verizon Samsung Galaxy S6] fletch33:
honestly its probably a good thing. i have found my devices to work much better when i chose to fresh install everything versus restoring from backup from Google. with root products like Titanium i would restore but not with Play.

if you really want it you could try a factory reset then restore.