yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] moonlight@china:
give some commit to fix data,you can push to team-hydra.Thanks to DU.

https://github.com/DirtyUnicorns-Ki...mmit/30f6e77bfe56f612c88a2f2b7dc017ebd9a5ea39

https://github.com/DirtyUnicorns-Ki...mmit/f445d0cf4a3dd3a3209e66c4b5c0faff26e1bb98

https://github.com/DirtyUnicorns-Ki...mmit/269e3234c60a44eddb789a7787aca756f7b1c498

https://github.com/DirtyUnicorns-Ki...mmit/873c815b75aded65f15ae57b6cfe8dee858e2008

https://github.com/DirtyUnicorns-Ki...mmit/2698f2d78d772743d5bad962eed9d0bf6a581ff1
[Samsung Epic 4G Touch] benutne:
OK, I've gone all the way back to the January 12th release and data works for me with that. I am on Ting, not Sprint so that might make a small difference. I tried every release after the 01-12-2014 release and not one had mobile data working.

Just FYI.
[Samsung Epic 4G Touch] HighxVoltage:
It's been a known issue that builds after Jan 12 don't have mobile data working. Regardless of what carrier said person is on (Sprint, Boost, Virgin, Ting, Freedompop, etc.)
[Samsung Epic 4G Touch] dastin1015:
That's cause that is a pre-qcril build. I'm not going to revert to that, but rather fix qcril
[Samsung Epic 4G Touch] benutne:
Well then. My fault for not reading that far. Thanks. It seems several builds of 4.4 don't support data on our devices then.

---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------

Sounds good to me. Will we need to do a clean install or can we just flash over, assuming I'm still on the Jan 12 build?
[Samsung Epic 4G Touch] dastin1015:
That's cause most ROM's since CM 10.1 were based off my work they continue to base off of me. So issues I have they usually have as well.

I always recommend clean installs, but dirty flashes are fine. If you run into issue then clean wipe.
[Samsung Epic 4G Touch] benutne:
I looked through the thread a bit in hopes of finding something that would fix this annoyingly low volume. The Xplosion mod came up a couple of times. I installed it fine but now, no matter what, the driver will not stay installed. The driver installation doesn't report any error but as soon as I open the program after a reboot, it asks to install the driver again. Should I go ask over in the mod thread or is this something specific to this ROM? I'm on the Jan 12 build BTW since I can't not have working data.
[Samsung Epic 4G Touch] south956:
....recently I was on this build and I had found the system file for volume modding, if anyone knows of it or anything...I would appreciate the help, you mod the values and the earphone and speaker volume drastically increase, be warned that too high values might hurt your ear and might pop your speaker, use with caution and if by some case I reflash ROM I'll look into it

For your own custom Sig : http://xdaforums.com/showthread.php?t=1922304
[Samsung Epic 4G Touch] Linux guy:
Hi does any body still have trouble with the "OK Google"? I dirty flash this from 4.3 and it's running perfect (minus battery and data). I wiped afterwards and the "OK Google" voice command stopped working. Downloading the English offline files fixed it. Hope it helps

sent from tumblr
[Samsung Epic 4G Touch] mholloway:
Has anyone checked out the apns-conf.xml file.its huge,really long the one one cm 4.3 is like 1/4 the size.is that the way its supposed to be?.CM4.4 apns-conf.xml size is 204.33k and CM4.3 apns-conf.xml size is 2.24k
[Samsung Epic 4G Touch] HighxVoltage:
Wipe first, then flash CM11.

dirty flashing from one version to another often cause problems.
[Samsung Epic 4G Touch] SuperGoober:
I don't know but the size now on my 4.4 is less than 5k and my kk works fine with it on CM11 and also slimkat , both for the gnex . its big because it prolly has info for every carrier whereas we just need the part that would pertain to sprint . The problem wasn't with size , it was something in it causing erroneous behavior from what i understand and wasn't letting data work . Not telephony or anything like that , just a messed up file .
[Samsung Epic 4G Touch] easyrider77:
Well if they got it working on the gnex variants, it's just a matter of time before this will to work....(I hope)

For now not much we can do about it, unless someone can generate a fix.

Good to see progress is being made, even if it's not this model, it jsut means it's one step closer to our fix.
[Samsung Epic 4G Touch] mholloway:
Iam running hood Pope with Google launcher,swipe over to Google now.go in settings,voice,and download English in offline voice ,after that my OK Google works.
[Samsung Epic 4G Touch] Linux guy:
Sweet

That's my good deed for this year.

BTW I restored a nand back up and flashed dirty again and everything's good. I know you shouldn't flash without wiping but I'm a rebel. (A lazy rebel)

Don't try it anyways :p

sent from tumblr
[Samsung Epic 4G Touch] easyrider77:
I believe I have found a fix for the Camcorder [Anything higher than 420p] issue. I have tested this a coupe times and it works every time, in both 720p and 1080p recording, No lockups or freezes.

Not sure if anyone is really interested in a fix or not for that, but if so let me know I will post what I did.
[Samsung Epic 4G Touch] FuMMoD:
Has anyone been able to use the emoji keyboard? I can see emoji but can't send any. I've actually pushed the files for the emoji keyboard from my nexus 5 and nothing. The keyboard crashes.
[Samsung Epic 4G Touch] CamCroz99:
lemme check. I have always had the problem on other ROMs where I could send but not receive. I could send emojis but but when they came back they were just spaces.
[Samsung Epic 4G Touch] FuMMoD:
I can't send though. My issue is that I'm able to receive them system wide but cannot get the keyboard to run.
[Samsung Epic 4G Touch] CamCroz99:
The Emoji keyboard is working fine on my device. I wish data was working.
[Samsung Epic 4G Touch] XxlemonxX:
I literally check this thread every hour. I can't wait till data works this rom is so smooth and the only KitKat rom. Can't wait keep up the work :)
[Samsung Epic 4G Touch] FuMMoD:
How exactly are you using it? Are you sending or just receiving? Receiving works perfect. The keyboard just doesn't load up. Did you flash the keyboard or what? Please share your steps. Thank you

Edit: Complete wipe and fresh install doesn't even include an emoji keyboard.
[Samsung Epic 4G Touch] CamCroz99:
I knew it shouldn't be this easy. I thought you meant this

---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------

Same here. It will be awesome! I need to make a bot that auto "f5"s. :laugh:
[Samsung Epic 4G Touch] FuMMoD:
Yes! That keyboard right there! Can you use it in anything that is not that modified SMS app? It only works in the messaing app and I want to be able to use it anywhere just like in the official kitkat roms. On my nexus 5 all i do is select the emoji keyboard and do my thing then enter and it goes back to swype.

By the way you can install "Auto Refresh Plus" on google chrome extensions to auto refresh at a specified interval if you want.
[Samsung Epic 4G Touch] CamCroz99:
Check this out: http://xdaforums.com/showthread.php?t=2506116 BTW thanks for the refresh thing lol. :laugh:
[Samsung Epic 4G Touch] FuMMoD:
That's the same keyboard i pushed from my nexus 5. =/ The only way to get the emojis to work is to have the emoji keyboard not the Google keyboard (Latinime).
[Samsung Epic 4G Touch] CamCroz99:
What do you mean?

You have to hold the enter button for a second or two and it will bring up the emoji menu.
[Samsung Epic 4G Touch] FuMMoD:
Wow, I feel like an idiot now lol. The easiest thing just flew right over my head. That works perfectly, thank you. In the nexus 5 all I have to do is select the emoji keyboard from imei options in the status bar and once I sent it switches back to swype so you can use emoji with any keyboard. I guess ill just switch between google and swype keyboard until I can figure out a way to port the emoji keyboard.
[Samsung Epic 4G Touch] benutne:
That would be really awesome. So far the speaker volume is my only complaint about the ROM. If I could fix that I'd be super happy with my phone again. The ROM is so fast and smooth I don't ever want to go back to a TW ROM.
[Samsung Epic 4G Touch] dastin1015:
Update released! See changelog for details! Enjoy!

Let me know if data works now.
[Samsung Epic 4G Touch] LOWCOUNTRYDAVE:
Just downloaded and flashed the latest release, and my data is working great! Any tweak packages known to work with this ROM? I just switched over from official mokee ROM. New to cyan. Lightning zap maybe?

Sent from my super futuristic, rooted and tooted, Samsung Galaxy S13,437 Epic 25G Touch
[Samsung Epic 4G Touch] HighxVoltage:
No lightning zap. It's only meant for 4.2.2

I've been reading comadose works.
[Samsung Epic 4G Touch] benutne:
Thanks. Downloading now. I'll let you know if data still works after on my device. I'm gonna dirty flash it first.
[Samsung Epic 4G Touch] Krowbarr:
I've been using Extreme kernel. It's here if you wanna give it a try

https://www.dropbox.com/s/60ttmfe13w80dij/Extreme_Kernel1.zip

☞"And on the eight day the Lord made a backup"☜
[Samsung Epic 4G Touch] benutne:
I had thought that kernel was all kinds of broken...did they fix stuff yet? Some people were having issues with bootloops and recovery not coming up.
[Samsung Epic 4G Touch] Krowbarr:
I hadn't heard about that. I've been using it for awhile with no reboots or SOD's. Using TWRP recovery with no issues.

☞Owner/Operator Samsung E4GT/Villuminati Rom 4.4.1 Kitkat

We were born in a time where if something was broken we would fix it and not just throw it away
[Samsung Epic 4G Touch] HighxVoltage:
The working kernel isn't posted on the Extreme Kernel post.
[Samsung Epic 4G Touch] benutne:
Oh, ok. So the link Krowbarr posted is the working link? I'd like to give it a shot.
[Samsung Epic 4G Touch] Sik-1:
Nope jus tried it and force closed android phone kept popping up still
[Samsung Epic 4G Touch] benutne:
Thanks for trying that out. Good to know to avoid it for a bit.
[Samsung Epic 4G Touch] biglama:
The bottom of page 21 in the mokee thread has a working link to the extreme kernel. I use it with all 4.4 Roms.
[Samsung Epic 4G Touch] benutne:
You rock man. Thanks.

---------- Post added at 11:23 AM ---------- Previous post was at 11:21 AM ----------

Just checking in with the update. Data does indeed appear to work (on Ting). Thanks for all your hard work dastin. My phone is actually nice to use again.
[Samsung Epic 4G Touch] El.Dante565:
So data is working now sweet!
[Samsung Epic 4G Touch] benutne:
Yup. Confirmed on mine and one others so far.
[Samsung Epic 4G Touch] dastin1015:
The problem was with the new qcril (CAF [Qualcomm] additions to the telephony stack). D710 was having issues getting data via RIL_REQUEST_DATA_REGISTRATION_STATE so used a legacy prop added for the shooter (Evo 3D, which I also support) that allows getting data via RIL_REQUEST_VOICE_REGISTRATION_STATE

Commit is here:

Telephony part:

https://github.com/Team-Hydra/andro...mmit/d71bd65c894b5467cda6b672549997a307b7d268

Device part:

https://github.com/Team-Hydra/andro...mmit/9dc85dd8bf0404f8e2b6ead7611c5e83671036d8

私の ネクサス7 から送信される。
[Samsung Epic 4G Touch] benutne:
Welp, the phone process FCs with the kernel you listed. Looks like it doesn't work with this ROM.
[Samsung Epic 4G Touch] usablefawn:
I was also running the extreme kernel, but on Mokee and it worked fine. Have yet to try it on this version.
[Samsung Epic 4G Touch] drk65:
Should I Upgrade.... Reason, Benefits, Process?

I"m still on the January 12th build with working data. My primary issues are...

- No Dock Audio Output

- MMS works only through 8SMS (External) App

- Audio Cuts Out At Low Volume Settings (Especially On Headphones)

Now that data is working (a must for me) on the newest build, can someone advise if any of the above-mentioned issues are resolved with this latest build. Additionally, does this latest build provide any additional features or functionality that was not included within the earlier (January 12th) build?

Finally, while I have flashed and rooted several times (from scratch), I've yet to do a version update/upgrade such as this. I'd appreciate knowing if I need to do a full wipe and start from scratch again, or can I flash the latest version (and new Micro GAPPS?), while maintaining my apps, settings, and data? Sorry if this seems to be a bit of a "noob" question, but I just want to be sure in understanding the best/proper way to proceed from here, as I've been quite pleased with the January 12th build and don't want to do something that will cause me to take a step backwards. Of course, I have a recent and confirmed CWM/Nandroid backup, so I'm covered there.

Thanks to the Dev for all his hard work and thanks to all the forum members for all the great info and knowledge you've shared.
[Samsung Epic 4G Touch] HighxVoltage:
Dock Audio not functional. Dastin has no accessories. (See 1st post)

Don't know about MMS, out of service.

Low volume cut off has been an issue since CM10 or 10.1 I believe.

Clean wipe is optional when updating to the same ROM but, often recommended to get best results.
[Samsung Epic 4G Touch] benutne:
The thing about the dock audio not working is an issue with all CM builds. Not sure if anyone is really interested in looking into that ATM. I asked a bit earlier about the audio issues and I hope someone can chime in and help with that because that is super annoying. Apparently, ALSO an issue that is CM wide on our devices.

I haven't tried MMS but I've never been able to get mine to work on any phone I have so I kinda don't even try any more. Sorry I can't help you there. I did a full wipe and reinstall after backing up apps I use most but you MIGHT be able to dirty flash. Give it a whirl. I was on the Jan 12 build and flashed this morning and I can confirm data does work for me.

---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

Beat me to it.
[Samsung Epic 4G Touch] drk65:
Thanks for the quick feedback and info. It appears that my primary issues/concern still exist... not deal breakers. So, at this point, I guess my remaining question is WHY do I want to upgrade to the current build from the January 12th build... What do I gain or improve over the build I'm currently running?
[Samsung Epic 4G Touch] benutne:
Bugs in CM11 that were fixed upstream. That's about it but you should really check the changelog in the first post. There are a few things that might be important to you.
[Samsung Epic 4G Touch] Krowbarr:
Just wanted to report data and mms working on boost mobile. No problems encountered with clean flash. I did lose my MEID though, it says "unknown."

☞Owner/Operator Samsung E4GT/Villuminati Rom 4.4.1 Kitkat

We were born in a time where if something was broken we would fix it and not just throw it away
[Samsung Epic 4G Touch] dastin1015:
The issue with the dock audio is the same as it's been. Open sourced audio drivers don't have the support for them and I don't have a dock to even test with if I attempt to fix it (which I probably don't have the coding/debugging skills).

Low audio was a really low priority issue to me since trying to fix major issues take priority (like data), and I do this in my free time which lately I don't have lately between work 5 days a week, school during the weekdays and homework. Roughly an hour or two I can dedicate to each of my devices (mainly shooter for video playback and camcorder which the new 90% ION is broken with). The low audio issue is either a few config files needing boosted numbers or the audio drivers in the kernel needing a boost. I'll look at it probably this Sunday since that's my free day if nothing big comes up.

私の ネクサス7 から送信される。
[Samsung Epic 4G Touch] Sik-1:
The last build that works with the extreme kernel is the march 3rd build, if anyone wants to kno
[Samsung Epic 4G Touch] benutne:
We're happy with whatever you can give us. I'm just glad someone cares enough to work on this old thing at all. Let us know if you need something to help debug (logcats, etc). I'm wondering if someone has a dock they'd donate to get it working.

Thanks again. You rock.
[Samsung Epic 4G Touch] dastin1015:
To be honest this is an easy device to maintain compared to the shooter. HTC dropped support in ICS so lots of kernel work has to be done just to keep it going for each new version. ION being almost absolutely requires nowadays (which my kernel has ION everything except for the camera, which will be stuck that way anyways). I just have to fix camcorder, video playback and get it's media hardware repo out of legacy (display is using CAF now).

This phone still needs work for the JB modem and open sourced RIL

私の ネクサス7 から送信される。
[Samsung Epic 4G Touch] Linux guy:
Well you've done and outstanding job at making this device relevant. You've saved a lot of people from having to upgrade phones. We are all extremely grateful.

sent from tumblr
[Samsung Epic 4G Touch] dastin1015:
Appreciate it :) Stuff like this makes me keep going. I'm not in it for the fame and money some developers sadly hound over. This is a community to share common interests, not a revenue source.

私の ネクサス7 から送信される。
[Samsung Epic 4G Touch] IamFlynn:
I second what linux guy said. I have an upgrade available but I won't be because my device works perfectly.

I'm sure i can vouch for everyone when I say this, thanks so much Dastin. Also don't feel obligated to fix things like low audio, take your time because all thats necessary is data to work. Thanks once again [MENTION=3257303]dastin1015[/MENTION]
[Samsung Epic 4G Touch] drk65:
Can you briefly define "Dirty Flash" for me... Flash latest CM11 build (only) over the existing build, without and Data/System Wipe? If so, must I also re-flash GAPPS, as well? --- If this does not work or causes problems, I assume I can simply restore the current CWR Nandroid I have.
[Samsung Epic 4G Touch] HighxVoltage:
Thanks to [MENTION=3257303]dastin1015[/MENTION] [MENTION=4878501]ktempleton[/MENTION] [MENTION=4467521]sniper[/MENTION] [MENTION=2633294]DHO[/MENTION] [MENTION=5184047]mtb3000gt[/MENTION] and others. If it wasn't for these guys I would have spent hundreds of dollars on a new phone just to get a new OS. I haven't bothered with a new phone as this phone has served me well over the past 2 years. Still snappy, and still getting unofficial OS updates not from Samsung. So again, thanks you guys. :)
[Samsung Epic 4G Touch] dastin1015:
Dirty flash constitutes a wipe of the cache and dalvik-cache. Then you flash the new update. GAPPS doesn't need to be reflashed since CM has a built in saver script for the system portion of GAPPS and the rest is on the data partition which hasn't been touched.

私のONEから送信される。
[Samsung Epic 4G Touch] jhonka232:
So between Jan 12th, when Data last worked, to this most recent build with working Data, what has changed telephony-wise?
[Samsung Epic 4G Touch] dastin1015:
Merging off all of CAF's (Qualcomm) changes for the telephony stack. Improved support for CDMA, dual-SIM, and DC-HSPAP devices among others.

私のONEから送信される。
[Samsung Epic 4G Touch] jhonka232:
Awesome! I just flashed it and data works well, MMS does not work, though, and I believe it has to do with DcTracker.java in the telephony framework This thread explains better what I'm trying to say... http://xdaforums.com/showthread.php?t=2663277
[Samsung Epic 4G Touch] dastin1015:
I already have that commit added unless I forgot to readd it with the qcril merge.

Edit: It's there: https://github.com/Team-Hydra/andro...mmit/d51884c40f7c82feb94ae38bf8f0601e0f993ee0

私のONEから送信される。
[Samsung Epic 4G Touch] jhonka232:
I think so, when I opened the APNs with the voice dialer the list was empty
[Samsung Epic 4G Touch] dastin1015:
You replied faster than I can edit lol

私のONEから送信される。
[Samsung Epic 4G Touch] jhonka232:
LOL sorry about that. I think you need the DCtracker.java commit as well, to pick up the APNs on first boot. It's at the bottom of the thread I linked.
[Samsung Epic 4G Touch] dastin1015:
Yup missing that last piece. I'm gonna revert the previous commit and squash it into one big commit to alleviate anybody else's issues when they choose to cherry-pick from my repo. One less command

私のONEから送信される。
[Samsung Epic 4G Touch] jhonka232:
Thanks Dastin, you da man
[Samsung Epic 4G Touch] drk65:
[QUOTE =dastin1015;51345000]Dirty flash constitutes a wipe of the cache and dalvik-cache. Then you flash the new update. GAPPS doesn't need to be reflashed since CM has a built in saver script for the system portion of GAPPS and the rest is on the data partition which hasn't been touched.

[/QUOTE]

Thanks for the clarification. I opted to go the Clean/Full Wipe Route... Did Nandroid > Full Wipe > Flashed FL24 Modem > Flashed Latest CM11 Build > Flashed GAPPS... Now for my question...

At this point, can I select "Advanced Restore" and "Restore Data" from the Nandroid Backup I just made (before doing the wipe/update)? Or, do I need to Reboot into the new/updated ROM and then Reboot to Recovery and THEN "Advanced Restore" > "Restore Data"?

Hopefully, someone will see this post and answer shortly, as I'm sitting here in Recovery, hoping for an answer so I can proceed properly. Thanks very much to all for the help!
[Samsung Epic 4G Touch] dastin1015:
Thanks for the clarification. I opted to go the Clean/Full Wipe Route... Did Nandroid > Full Wipe > Flashed FL24 Modem > Flashed Latest CM11 Build > Flashed GAPPS... Now for my question...

At this point, can I select "Advanced Restore" and "Restore Data" from the Nandroid Backup I just made (before doing the wipe/update)? Or, do I need to Reboot into the new/updated ROM and then Reboot to Recovery and THEN "Advanced Restore" > "Restore Data"?

Hopefully, someone will see this post and answer shortly, as I'm sitting here in Recovery, hoping for an answer so I can proceed properly. Thanks very much to all for the help![/QUOTE]

After the ROM has booted up. Personally I use Titanium Backup for restores of apps and data

私のONEから送信される。
[Samsung Epic 4G Touch] south956:
OK so I got the volume mod I was taking about

Using ES File explorer with root permissions and read/write checked in root explorer settings......

First go to /etc folder then go to bottom to a XML file named tinyalsa-audio.XML

Click file and use ES file editor

Go to line <ctrl name="Master Playback Volume" value="75" />

And change the 75 to 80, click back and make sure to save

Reboot and try the new max volume

For your own custom Sig : http://xdaforums.com/showthread.php?t=1922304
[Samsung Epic 4G Touch] dastin1015:
Added that for next release. I confirm it fixes the audio cutoff at second to last volume step.
[Samsung Epic 4G Touch] benutne:
Does this do anything to fix the low notification volume? I want to be able to crank that up. I can't hear the phone ring or hear texts come in when the phone is in my pocket. Or does it only fix the headphone cutoff?
[Samsung Epic 4G Touch] biglama:
Yes it fixes the external speaker. Distorts a touch. Might want to set it to 78 or 79 and test it.
[Samsung Epic 4G Touch] benutne:
Dude. You. Are. AWESOME. I can finally hear my notifications and ringer. Thank you so much. I did crank mine to 85 and yea, it distorts a little. I'm fine with that. No more missed alerts/calls!
[Samsung Epic 4G Touch] south956:
These lines are needed to make speaker and headphone volume go up, if you only want to higher one or the other.

For example if you only want boosted headphone volume then mod second line

Found in /etc/tinyalsa-audio.XML

</device>

<device type="speaker">

<path type="enable">

<ctrl name="Speaker Playback Volume" value="26" />

<ctrl name="Speaker Playback Switch" value="on" />

Change 26 to 30 for speaker volume only

</path>

</device>

<device type="wired-headphone">

<path type="enable">

<ctrl name="Headphone Playback Volume" value="15" />

<ctrl name="HP Gain Playback Volume" value="3" />

<ctrl name="Headphone Playback Switch" value="on" />

Change 15 to 20 and 3 to 5 for boosted headphone volume

For your own custom Sig : http://xdaforums.com/showthread.php?t=1922304