yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Exhibit 4G] cars1189:
CM11 Update

Hey guys. I have a working build environment now and have uploaded a new build. And yes you read the changes right the built in CM torch app aka flashlight now works including the widget and more that it has!(so useful) (ty [MENTION=3044346]arco68[/MENTION])

Updated K^Kernel to come soon.

Also if you guys are ever wondering whats new in CM faily easy way is to look on http://www.cyanogenmod.org/blog.
[Samsung Galaxy Exhibit 4G] Nitro Lopez:
sweet!! my rom from jfbs is running pretty great right meow but I love flashing new roms so i'll give it a go!! thanks for the update!!
[Samsung Galaxy Exhibit 4G] jajb:
This is great news! Thank you for all your hard work [MENTION=1816400]cars1189[/MENTION] and [MENTION=3044346]arco68[/MENTION]! Very much appreciated!

About to flash...
[Samsung Galaxy Exhibit 4G] karaki93:
great work man thanks a lot and about this issue Lowest quality in camcorder, doesn't work. Therefore MMS Video Capture also.and also flash is not working with camcorder so i suggest you check on the Rem-ICS its a jellybean 4.1.2 rom where the cam is fully working. keep up the good work
[Samsung Galaxy Exhibit 4G] cars1189:
Yea that MMS video has been broken since kitkat. Its a new thing and earlyer version wont help any. If you know of a new KK rom though that is working now that i can work with. Its something changed in the new camera app. Its my next project. I have a thought in mind needs testing. The video flash never worked and im not sure ever will. Its never worked and also doesnt work on any of the other devices that are similar to ours.(as far as i know please correct me if im wrong again with evidance so i can work with it) If im not mistaken i think mms video works with third party apps maybe? and then you can just tell it to attach the video. Not 100% sure about that. Again though ...next project...if you cant do without it might wana move to a different rom for a bit till i can work it out but if it isnt to hard/my thought works it should be fixed soon(thats soon TM if your familiar with the blizzard joke :P ).
[Samsung Galaxy Exhibit 4G] det0xx:
i appreciate all the work you do for this rom/phone. hard or not its an effort you do and many others dont do but again thanks, like you said many things will be not fully functional but the basis will. thanks again from the community
[Samsung Galaxy Exhibit 4G] TripFX:
thanks [MENTION=1816400]cars1189[/MENTION] now just waiting for the oc kernels to set it all up on wifes phone.
[Samsung Galaxy Exhibit 4G] cars1189:
[MENTION=4825437]Christopher83[/MENTION]

It appears right now the other kernels are incompatible. I made builds tonight and there was a issue with some where the touch screen would turn on but not respond to touches. We'll have to wait for them to be updated.
[Samsung Galaxy Exhibit 4G] TripFX:
i might try pulling out jfbs kernel out of his latest madhi rom later today and see what breaks or ill just wait for a newer kernel base.
[Samsung Galaxy Exhibit 4G] cars1189:
CM11 MMS

Hey guys. I have made a small more of a workaround for MMS/Low quality. Basicly i made it so that the low quality is the same as QVGA resolution. So in the camera app it still says QCIF but in reality its QVGA. This at least for now gets MMS working i sent two test messages and both worked one 3 seconds long and one 10. Beyond that im not sure of any downsides. It maybe possible that it will be too big in file size for MMS with more mostion/longer times. So thats why it more of a workaround. Will work on more of a permanent solution in the future. Or maybe ill just keep it if theres no downside.

Flashable Zip

Edit: If im not mistaken the current file limit is set to 307kb in the mms app but we could probably increase that if needed. If a better solution doesn't come up. And therefore could keep the current workaround. Let me know your guys opinion and what not and well see what happens. To my knowledge other newer devices use a higher file size so im assuming it would work fine.

Edit2: In testing it looks like a video of 10 sec with lots of motion comes out to be ~447kb of course this can vary so might need to up the size. For the time being if using the work around id keep it to ~5 sec which is pretty lame but hey...im working on it lol. At least in one device i see they have it set to 1.2Mb so we could literally more than double it and should still send fine over the network. Which means we could keep the better quality and make videos ~15-20 sec long. Again might test that latter depending on what you guys think and how well the workaround works.
[Samsung Galaxy Exhibit 4G] jajb:
Thanks [MENTION=1816400]cars1189[/MENTION] for the workaround. 15 to 20 seconds would be best. Would definitely like to see if you could up the size for the MMS app to make this possible.
[Samsung Galaxy Exhibit 4G] cars1189:
If thats what everyone wants hit the thanks on [MENTION=5772029]SlurmsMcKenzie[/MENTION] 's or my post and if it gets a high amount of likes then ill do that.
[Samsung Galaxy Exhibit 4G] TripFX:
it fails as well using mahdi kernel too bad now i just wait patiently.
[Samsung Galaxy Exhibit 4G] cars1189:
Kernels

Hey guys i found the missing part. New Kernels are up. Note because of a update in the touchscreen driver the new kernels are not compatible with older roms. And older roms not compatible with new kernels....you get the idea.
[Samsung Galaxy Exhibit 4G] TripFX:
got it up and running on wifes phone with art enabled oc/uv few other personal tweaks and it's running solid torch and everything that she uses works great gj
[Samsung Galaxy Exhibit 4G] karaki93:
Here is two thing i noticed the dialer issue seem to be related to the kernel cz it didn't appear until i flashed the new kernel this morning and i was recording a video and i used the torch to open the flashlight and it worked
[Samsung Galaxy Exhibit 4G] TripFX:
wife hasn't got the dialer issue since builds ago. did you make sure you one zipped it and wiped davlik-cache per a full reboot? if not or you don't remember try it.
[Samsung Galaxy Exhibit 4G] jajb:
[MENTION=1816400]cars1189[/MENTION] after flashing your 08/28 build, everything's been running well except for one strange bug. I'm currently experiencing a blue flickering on my device screen. One way I've been able to consistently produce this bug is when I launch the Apollo app to play music. I would get a constant blue flicker every five to ten seconds. I also just experienced a blue flickering on my device's screen when I was trying to hang-up from a call earlier today. Anyone else experiencing this issue?

Reports from users over at the Galaxy W forum have mentioned the same bug as well:

http://xdaforums.com/showpost.php?p=55186097&postcount=1954 (reports of issue start here and continue)

http://xdaforums.com/showpost.php?p=55194399&postcount=1957 (possible fix? note: users are still reporting the problem even after potential fix)

P.S. arco68 seems to have a hard time re-producing the issue. I'll try to see if maybe I can catch it in a log.
[Samsung Galaxy Exhibit 4G] cars1189:
I think he eventually figured it out maybe. He reverted some stuff on github to try and resolve it. If it is the fix then ill do the same in the next build. And yes i noticed the reports of the issue before but i havent seen it myself. So im aware of the issue and when a solution is found ill make a new build sorry for any inconvenience this may have caused. (beta'ish rom is beta'ish :) ) If im not mistaken he at least at one point believed it to be a kernel issue. The problem in the kernel he suspected isnt in the K^Kernel i dont think so you may want to try that, The OC build is the most like stock it only has added goves and the ability to OC so there should be no risk if you are one to avoid things like OCing.(in my testing i didnt see the bug with that kernel)
[Samsung Galaxy Exhibit 4G] jajb:
Thank you for the information [MENTION=1816400]cars1189[/MENTION]. And no need to apologize, I'm just grateful to even have KitKat running on this ancient device.

I did want to mention that the blue flickering still occurred while using the K^Kernel. However, arco68 mentioned to set the minimum CPU frequency to 368 Mhz and sure enough that fixed the issue.

Thank you again for all your hard work!
[Samsung Galaxy Exhibit 4G] cars1189:
Update

New CM11 up, has a more complete workaround for the mms issue. Also fixes the bluescreen issue some have seen. At least from what arco has reported. He also does mention that it may happen sometimes but its alot more rare than before. As always you can expect updated kernels to be up soon.

Edit: Kernels up now.
[Samsung Galaxy Exhibit 4G] spiked_mistborn:
I'm having an issue with the exposure when recording video on the main camera. It looks fine during preview, but goes dark as soon as recording starts. Recording with the front camera does not have this problem. I tried Google camera in addition to the stock camera. I'm running the CM11 9-9-14 build with the k^kernel 3.4.102 uv vhm 9-9-14 build.

One other issue that I've noticed that might just be KitKat related, because my stock Moto E does this too, is that any apps installed to the sd card lose their icons on the launcher after rebooting.

Other than this, I can't believe how good this runs!

Is anybody else having these issues?
[Samsung Galaxy Exhibit 4G] TripFX:
not sure about cars version as my wife never used video recording.

[MENTION=1816400]cars1189[/MENTION] and [MENTION=4657373]jfbs[/MENTION] just wanted to say it was a nice run with these phones and was awesome to see what you guys have done for us. I was given 2 599's which me and my wife now use. so just wanted to say thanks and it's time for me to move on.
[Samsung Galaxy Exhibit 4G] cars1189:
I dont seem to be having any of these issues.

When you say you loose icons on the launcher do you mean the home screen or the app drawer? And what launcher do you use?
[Samsung Galaxy Exhibit 4G] spiked_mistborn:
The launcher is stock CM11 Trebuchet. The icons are disappearing from the home screen. If I make a folder on the homescreen and put all the games in there, any of them that are "on SD card" will be gone after a reboot. I think it's a timing issue, because if I open the app drawer right after rebooting it takes some time for apps on the sd card to show up. I think the launcher is doing a check to see if all of the home screen app links are valid as soon as it loads, and this happens before the apps on the SD card are enumerated which causes the launcher to think they're invalid.

I wouldn't worry about it too much though. It don't think it's a problem with your build because I see the same behavior on my Moto E with both the stock and Google Now launchers, and stock KitKat 4.4.3.

If nobody else is having the issue recording video maybe I'll try a full wipe to see if that helps. My daughter decided she likes recording video now, but it's so dark it's hard to make anything out.
[Samsung Galaxy Exhibit 4G] wrusry:
dialer issue fix

Quite some time ago, I reported an issue I was having with CM11 build and the dialer/keypad not activating the first time it was selected. Turns out it is an issue with Animation duration scale. I had lowered the values initially on all of these items in order to speed up the transitions. Changing this value fixed the issue for me. See: http://android.stackexchange.com/qu...kit-kat-does-not-like-to-bring-up-the-num-pad

FYI
[Samsung Galaxy Exhibit 4G] cars1189:
Well.... definaitly seems like its a rom code issue so cyanogenmod would have to fix it. However unless they dont know about it it looks like that post is over 1/2 year old so not sure its going to be fixed and if it does its probably last on their list.
[Samsung Galaxy Exhibit 4G] theking1st:
[MENTION=1816400]cars1189[/MENTION] just want to say THANK YOU! You don't realize how helpful you are. This phone is supposed to be dead at this moment. But thanks to you we are running on the latest version of Android which other more powerful Android phones don't. Meaning that we are getting some features and enhancements that they can't have unless upgraded! I mean just thank you for e what you are doing! It really means a lot!! THANK YOU!

CM11 on Samsung Galaxy Exhibit 4G: http://youtu.be/df4Fweo8DQI
[Samsung Galaxy Exhibit 4G] karaki93:
This is the strangest problem I encounter when the system memory have less than 100 mb free the speaker stop working and when I restart the phone it work for just 5 minutes and stop again
[Samsung Galaxy Exhibit 4G] kernelkode:
some questions

Thanks for the efforts here. Thought I'd test some before I bought a new phone and have been pretty impressed.

CM10.1 runs great. CM11 is a bit laggy for me. So far, SlimKat is currently my favorite as it seems to run excellent.

Something I noticed in the the JellyBean+ roms is that the screen rotation button widgets don't seem to toggle properly. In CM10.1, it appeared to have no effect in browsers, but some games it worked. In CM 11 and SlimKat, the widget doesn't seem to properly link to the settings state. Is this just me?

I previously used Go Launcher EX, and really liked the process widget that shows the running processes as icons and has a killall button. Are there any lightweight alternative that anyone can recommend?

Also, I liked being able to dial the tmobile codes that would show you your data usage and minutes. Does anyone know exactly what needs to be installed to use these? And do these slow the system down?

Thanks again for the taking the time to do these things. :good:
[Samsung Galaxy Exhibit 4G] jajb:
[MENTION=1816400]cars1189[/MENTION], thank you for the updated build! Very much appreciated! Will you also be providing updated kernels? I noticed both your 10-04 and your latest 10-18 build did not include any.
[Samsung Galaxy Exhibit 4G] cars1189:
Hey, the last released kernels should work with them..i was actually away the past weeks so i haven't had time to put some together, the rom is more automated. The next build ill make sometime soon and itll have updated kernels as usual.
[Samsung Galaxy Exhibit 4G] cars1189:
Hey guys... new rom and kernels up. New CMW too its not really needed but it builds with rom so i figured id thow it up in the cwm thread this time.

NOTE: If you are one of those people who dl things before i even post them here go re-download the kernel if you already did. There was a error in upload and i re-uploaded all the kernels. (All Kernels Zips are ok as of 10.31.2014 @ 10:10PM EST)
[Samsung Galaxy Exhibit 4G] joelrg:
Thank you!

Just a quick thanks to all the dev's that have done work on this phone. I've been reaping the rewards of your hard work since Jocala's work on CM7 and on. Just picked up a new S4, so I'm moving on from the old Exhibit.

Thanks:

Jocala

Cars

JFBS

TripFX

Camcory

Core2idiot

And any other dev's I've forgotten! Good luck guy's!

Joel
[Samsung Galaxy Exhibit 4G] spiked_mistborn:
Bluetooth audio

I had an issue trying to play music using both Apollo and ES File Explorer when connected to a Bluetooth speaker. It will quickly cycle through the playlist and nothing actually plays. I was not able to find a solution with the CM11 10-4-14 build, but after updating to CM11 10-31-14 + 3.4.104 k^kernel I was able to get BT audio working by disabling lpa audio. Just an FYI if anybody else has run into this issue.
[Samsung Galaxy Exhibit 4G] cars1189:
Yea lpa is a feature thats pretty hard to get working and even on stock roms doesnt always work 100% with all apps.

Side Note: I am going to continue providing cm11 builds for a while as cm is still making changes but with "L" cm12 being merged recently of course that will change at some point and so will me providing builds. And as for "L" for this device...its not looking good. For one the partition sizes are just too small i mean even with 4.4 and some gapps packages we run out of room. And with art being the only option(i think?) in 5.0(or w.e.) its not good. We are looking into using different partitions for different things but as this will break backwards compatibility, maybe with being at the very least hackish, most likely i probably wont release one if i do it will probably be uploaded but not shared so those that are adventurous can find it but thats all. Obviously its pretty early and not many "official" cm devices have it so this is a pretty long ways away. Just a heads up...(buy a new device!) lol you can get fairly new devices that have official cm support and will get "cm12" for fairly cheap now.(like 60$ maybe) I know i dont really have money to do so, so ill probably try to make a 5.0 build but this phone is just really getting old. People said this back with like 4.1 which i dont totally agree with but its definitely getting there now. That all being said as we get closer to cm11 not getting updates(still a ways away) i will probably do one last up date for cm10.2 since i havnt in a long time but nothing has really changed just to ensure its left in a good state like with cm10.1. Once cm12 is the devs main focus(really long time away) ill do the same and stop within ~ 1 months time). If i had to guess i would probably say by the end of this year or maybe early next year. This will start happening. (4-5 months maybe).

Sorry for the long post. :)
[Samsung Galaxy Exhibit 4G] spiked_mistborn:
Thanks for the update [MENTION=1816400]cars1189[/MENTION]! I've been thinking this phone needed to be re-partitioned for a while and figured it would never happen just for the reason you said -- it would break backwards compatibility and also need support from the rom. I could see where that would cause some problems if people don't pay attention and flash the wrong rom. I would be interested in giving this a try if you do decide to do this, so I'll keep an eye on the builds. My current phone is a Moto E which also has 4GB of flash, but the way it's partitioned it makes much better use of the available space.
[Samsung Galaxy Exhibit 4G] karaki93:
Ok man thanks for the hard work your making to keep the phone alive, I'm interested in getting the cm12 i've its already available to some devices and fully working i hope you can make one for this phone and for me re-partitioning should be done for kitkat before lollipop cz its already causing some problems but your the expert so its up to you
[Samsung Galaxy Exhibit 4G] cars1189:
So i have found a solution that should work to solve our storage issue. The only thing is it requires a modified kernel and recovery and the two cant be mixed. This potentially poses a problem with compatibility. How much of an issue im not sure. The issue is when you change what partitions are used for you end up with things like app data on the system partition and system on sd card or something. Now this isnt too bad as after we make the switch the recovery/kernel uses mount points for example "/system" instead of "/dev/block/mmcblk0p15" so anything it does wont matter. So once you are switched to the custom kernel and recovery and then wipe all the partitions your fine but its makeing the switch that im affraid of for others because if you mix them your gonna end up with wrong data on wrong partitions which can end in corrupt data or data loss.
[Samsung Galaxy Exhibit 4G] canodroid15:
[MENTION=1816400]cars1189[/MENTION] well it doesn't sound too bad a little confusing but I get it! If you need tester I'm down just let me know man! Thanks for all you do to keep the exhibit from fading away!
[Samsung Galaxy Exhibit 4G] cars1189:
The one thing im not sure about is how can i get a rom onto the sdcard without recovery. (For Testing Purposes) Because the SD need to be in ext4 but i seem to be having permissions issues going from pc to phone. And for some reson i cant extract the rom on the phone. If anyone has any ideas im open to sugestions.

Edit: I was able to extract the rom onto the SD with root via terminal bu then the phone couldnt read the files.

Edit2: Figured it out (see attached) (System 1.9 GB Big)(Stock is 512MB)

Now the only thing is, the kernel has its own idea of how the partitions look and so does the recovery and so does the updater-script in the rom.zip. So...we have options...

1. Custom kernel/recovery/rom.

2.Custom kernel/rom.

If we do all three doing things like wipe system in recovery will actually work and not just wipe the old system which is unused. If we dont do all three it makes switching easyer and since the sd card is used as /system doing a format on sd is the same as formating /system. Also i only figured it out using the external sd. Trying the internal seems really risky and since i dont have money for another phone im not able to test. (I just cant risk it)However it seems like a wast for those of you that might have 16 or 32gb external sd's or bigger?(lol) even the 2gb i have is overkill....so..yea idk..
[Samsung Galaxy Exhibit 4G] theking1st:
So you managed to replace sdcard0 (the internal memory) with sdcard1 (which is the MicroSD we insert ourselves in the phone) right? So if I happen to have a bigger capacity sdcard1 it will be cool for me. So if I'm logical, when we will flash the ROM it will actually be installed on sdcard1 so it will have to naturally remain in the phone's MicroSD slot. Am I right??[emoji52]

I also would like to know where did the initial 512MB internal memory went. [emoji3]
[Samsung Galaxy Exhibit 4G] aaopt:
That's easy. jfbs' ROM supports toggling it in storage settings. I suspect he is talking about something more fundamental, like moving /system and/or /data to larger partitions.
[Samsung Galaxy Exhibit 4G] canodroid15:
[MENTION=1816400]cars1189[/MENTION] I knew you'd figure this out AWESOME!!
[Samsung Galaxy Exhibit 4G] cars1189:
i moved "/system" from internal memory(not sdcard0) to "/sdcard1" aka the microsd in even more detail i specifically moved it to the first partition on the microsd. Now this means if i where to release a build like this you could partition your sd into whatever you want but the first one needs to be atleast 550+mb big(other wise theres no point itd be just as big as our current "/system") and it will always be used as "/system" now the only thing is is what happenes with usb mass stroage? It wouldnt really work but i supposed if you made a nother partition you could manually mount it or make a init script to mount it as something. However since everyones would be different i couldnt make use of it. And in my sample the original "/system" is just unused. It is so small i dont know what to do with it and at least for my testing it made a lame dual boot(all i had to do was switch kernels to change roms) but its not really a dual boot because it uses the same "/data" so has to be the same rom but a different build.
[Samsung Galaxy Exhibit 4G] aaopt:
I always try to keep the same /data when switching between ROMs. At most I wind up deleting one or two apps' data using "clear data" in settings when something crashes. But often it works fine. [Edit:] But I wouldn't dual boot that way. OTOH nothing stops you from building two different ROMS that use different /data partitions if you really want to dual-boot. [End edit.]

The p500 people have it worse. Their device has roughly 200MB for each of /system and /data. In this thread they have a solution to "everyone's would be different" which is, to declare in the install instructions a standard way to partition the SDcard for their ROM: first system, then /sdcard, then /data. They have a TWRP build that goes with their ROM that knows how to partition cards that way. I used it to partition some for a couple old phones, with 1GB for system, about 12 for /sdcard, and 3GB for /data. The sizes can be different as long as the order of the partition table entries is the same. As the ROM developer, you get to decide what the requirements are for your ROM.