yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Moebius01:
Small flame war broke out. Should die just as quick one would hope. In the meantime, I'd definitely try a clean download and wipe everything out just to see if you get to a stable 3.0. If you do, you could always go back to a 2.8 nandroid and try to flash again. And if not, maybe try the stock kernel? From the reading I've done so far (still new to the android side of this game), they can be pretty temperamental. I played around with a couple one night just to see for myself, but couldn't discern too much difference to the naked eye, though I did see a lot of FCs on one that I chalked up to a bad flash.
[Samsung Epic 4G Touch] parmend:
Setcpu
[Samsung Epic 4G Touch] niv3d:
Everyone really having a lot of problems with 3.0?
[Samsung Epic 4G Touch] nibrwr:
Mine's running really well except for small MMS image size
[Samsung Epic 4G Touch] Spider_Pig27:
at everyone?? dude seriously?? what the hell is wrong with you?? if you read clearly i stated some help to those having issues and i also stated this to the people who kept saying this rom sucked and blah blah blah in other words to all the trolls,, i dont understand how you can get offended if i was not even offending everyone ion the thread just the freaking trolls... you need to start relaxing and reading more clearly before starting an argument that makes no sense

---------- Post added at 02:20 PM ---------- Previous post was at 02:11 PM ----------

Ignorant folk? HA! are you serious??.. tell me in what way have i offended you? unless your those type of users that runs into problems or issues while flashing a rom and right away state that the rom sucks and that the developer is doing bad work then i can not understand how it affects you... and for your information yes i had a error earlier and it was due to a mistake i made.. I DID NOT READ THE OP'S INSTRUCTIONS AND JUST FLASHED... so instead of flaming a thread i searched for where i went wrong... and for future reference i dont see anywhere in my statement were i insult anyone but the trolls and users who flame threads... if you read, well thats if you know how to read clearly, and go back a few pages youll see that there is ALOT of people bad mouthing the developer and rom... and just so you know i do run into problems but i dont go flaming a thread instead i ask for help or read the most recent posts to see if other users are experiencing the same issues and how they fix the problem.. so calm down before you wet your pants...
[Samsung Epic 4G Touch] tdunham:
So this happens even when you take a picture and send it to yourself?

Just for reference, I sent one out from the gallery and when it came back in I long pressed and selected properties or something like that on each pic and they were the exact same size.

I don't think I saw any other replies. Can someone else check out mms please and let him know too? Thanks.
[Samsung Epic 4G Touch] Custodian:
Sense a closing thread soon.
[Samsung Epic 4G Touch] nibrwr:
I've sent MMS to myself and my wife, says size is xxKB and file received is. I remember being on Calk's ROMs before and the compression was much more relaxed.

When I pushed the Blazer ROM MMS.apk, the file size was 8-10x larger. Can you upload your MMS.apk or PM me with it? I've redownloaded with same results.
[Samsung Epic 4G Touch] driftinganomaly:
All the pics that I have sent or received from Calk's rom have been between 50KB and 150KB. I am on 3.0 and my gf is on 2.9.2 so it doesn't seem to just be an issue with the custom kernel. I think I first noticed it back when running 2.8.1 but can't confirm it.
[Samsung Epic 4G Touch] tdunham:
No problem. It took me a while to figure out how to 'pull' the apk files. BTW, just sent a 520k pic to my wife on tmobile and had her send (to sprint) it back and it still came in as 520k filesize.

I'm attaching both mms.apk and mmsprovisioning.apk.

Let me know how it goes.

Edit: Umm, forgot to mention that I'm using Handcent. Let me try again with the default app.

Ok. Back to report that the default messaging app shrunk the crap out of my picture outgoing and incoming were both 89k! :cool:

Note: Attachment removed. No point in confusing anybody by leaving it here.
[Samsung Epic 4G Touch] s2kdriver:
Runaway Processes?

Please bare with me here as I feel compelled to offer a bit of history prior to my questions.

I have only had my E4GT for almost two months now and for the most part I'm enjoying it. But, things that I have noticed, other than the lousy GPS, is the poor battery life.

Please correct me if I'm wrong here, but I would expect close to, if not better battery life to my last phone (HTC Evo 4g). The battery is larger (1800 mAh vs 1500mAh) and from what I understand, the Super AMOLED display is more efficient. Granted, the E4GT has a dual core CPU and it clocks higher, but I believe it should be a wash with the other savings. My E4GT gets about 8-12 hours of normal use where my Evo got close to 24 hours normal use (>36hrs with lite use and without 4G of course).

So, my next step was to try a custom ROM. My E4GT shipped with EL29 and seeing all the issues with the ICS I decided to stay with EL29 based ROMS. And so far all of them I flashed seem to have the same related issue.

I'm constantly seeing "Security Storage" as the number 1 process. Examining this process I see that it is part of the Dalvik Virtual Machine. And more to the point, it is the Dalvik Garbage Collection (GC) routine that is driving the parent process to the top spot. This is also why the Android OS reports high battery usage.

Next, I tried to see what was causing this excessive GC and finally tracked it down to the Google "Calendar Storage 1.1" process. It seems to be constantly polling and each time it runs it causes the Dalvik JIT GC to run. The GC has to run or the calendar would become a huge memory leak (gotta love JIT).

To attempt to calm this down, I first froze it with TI Backup and saw a huge difference in the GC rate. It immediately dropped from the top process and mAh usage decreased which would in turn should prolong battery life. Of course there is the down side of not having any Calendar capability with the phone and this is, of course, unacceptable.

I then tried turning off all Google calendar syncs because I only use Exchange calendar. No effect seen and out of curiosity I tried to disabled Exchange as well and still no effect. Still polling like crazy.

Now with all that explained and very little information that I could find via searching, I have the following questions for all you wonderful E4GT experts:

1) Is everyone experiencing the same high "Security Storage" usage?

2) Did any of the previous gingerbread versions have the same issue?

3) If not, can we use a previous version of CalendarProvider.apk or has the framework changed to the point that we can't? (It may not be Framework dependent, I don't know)

4) Can we use a newer version from somewhere else?

I don't mind trying it as I think I have a better than average chance of not bricking.

I apologize for the long winded post, but maybe we can make some progress here.
[Samsung Epic 4G Touch] tdunham:
(Ok, definitely had to censor most of that quote ;) )

Where are you noting this usage, in betterbatterystats?
[Samsung Epic 4G Touch] s2kdriver:
I understand the censoring, LOL. I used a combination of tools; catlog, Usage Timelines, Battery Monitor, built in utilities and OS Monitor (a really good tool).

I also forgot to mention in my first post that I played with the VM Heap settings with Rom Toolbox (another great tool) by raising and lowering the settings. My thought process was to try and give the GC more space and see if it would not have to clean up as much.

I did see some difference, but it was short lived as soon as the heap free level reached some predefined point the GC kicked in. Then it was off to the races once again. Lowering the Heap size really had no ill effect, but I didn't take it down past 48mb.

---------- Post added at 08:29 PM ---------- Previous post was at 08:21 PM ----------

One more question, does anyone know where I can get the source code to CalendarProvider.apk? I would dearly love to debug it!
[Samsung Epic 4G Touch] tdunham:
Well it sounds like you've gone far beyond what the average user is willing or capable to try. Unless somebody jumps in with some experience with the troubleshooting methodology you're using, it's going to be pretty tough advising you because I don't know what some of those processes are.

Let me say (before someone else does) that I'm pretty much getting similar battery life as you with this ROM. And I don't really know how much more tweaking can be done that the developers haven't tried already. Some phones get better results than others with different combinations of tweaks.

You've spent so much time troubleshooting this one, why not just back it up and try a different ROM for a while. Many of them are based on this one and they're themed (I prefer the stock colors) but every single one of them will tell you that theirs is the best :).

There are some wild claims out there for battery life. I don't know if you'll ever get 24-36 hrs but ya never know.
[Samsung Epic 4G Touch] s2kdriver:
Thanks, I was really trying to get off easy by not "redesigning the wheel" If you know what I mean. I have already flashed 6 different ROMs in the past two weeks. I always give them a couple of days to settle in along the way.

Just about all the the EL29 based ROMs must be using the same Android Calendar. Probably, because the ROM developers also don't want the "redesign the wheel". I can't blame them. But, since I'm a Unix/Linux systems engineer by trade and fancy myself as an above average coder, I'm always trying to fix something.

Since Android isn't too far from the Linux structure and most of the mechanics are very similar, I figured I'd start to dabble with Android debugging. Dalvik VM is also not much different from Oracle JVM as the principles are basically the same. Wish me Luck and start placing your bets as to how long it takes me to brick it.:D
[Samsung Epic 4G Touch] driftinganomaly:
I think that this topic deserves it's own thread in general. You will get better visibility and accessibility to more knowledgeable people that way. I have wondered and seen other people post about how odd it is that android system uses so much more of the resources on this phone than others.

I hope that you have struck the core of the issue. Thank you and good luck!
[Samsung Epic 4G Touch] Custodian:
Added

pm.sleep_mode=1

dalvik.vm.verify-bytecode=false

dalvik.vm.dexopt-flags=v=n,o=v

To the build.prop. Now I feel the quality of this rom.
[Samsung Epic 4G Touch] Bazirker:
Does anyone know...

If I want to flash the bare ROM converter, can I do it immediately after a full wipe and flash of the full ROM (i.e. during the same recovery session), or do I have to wipe, flash ROM, boot, then reboot back in to recovery and flash the converter?

Thanks!
[Samsung Epic 4G Touch] Darkne0:
I did it right after I flashed the ROM, worked perfectly.
[Samsung Epic 4G Touch] Drybonz:
For some reason, on 3.0, my visual voicemail app does not work. Anyone else have experience with this, or a fix?

Thanks.
[Samsung Epic 4G Touch] simply dave:
Sorry, first time on SGS2 rooting. Coming from a rooted EVO.

Just wondering if this has clockwork mod recovery already built in or am I going to have to download that from somewhere else?

Thanks!
[Samsung Epic 4G Touch] krisI0N:
yes, and it screens of to, and when I screen on I have to home real quick before it screens out, then I have to screen on again and it'll be in home, then I can use. The browser.. gets tedious
[Samsung Epic 4G Touch] tdunham:
Check out this page. It was posted by Saxxman a long while back.

http://xdaforums.com/showthread.php?p=20331247&highlight=voicetogo+apk#post20331247
[Samsung Epic 4G Touch] jxb25:
Sorry for asking this question but after having to go back to a blackberry for a week what's the best kernel modem combo for battery and performance
[Samsung Epic 4G Touch] tdunham:
Yes it does. However, you have to be rooted with CWM installed first. The roms will flash its own kernel with CWM also.

But you have to root and install cwm just to start off first. I posted how to root and install cwm here on this page:

http://xdaforums.com/showthread.php?t=1332837&page=998

If you're starting out, I wouldn't recommend using any of the ICS roms. Stay exclusively with the Gingerbread EL29 based roms and do a LOT of research.

---------- Post added at 09:33 AM ---------- Previous post was at 09:28 AM ----------

Well maybe we have another developer to 'reinvent the wheel' for us. LOL

We expect to see a better and improved ROM in your near future. :D

---------- Post added at 09:44 AM ---------- Previous post was at 09:33 AM ----------

Tell us more please! What types of changes will these make?

Edit: Found this thread: http://xdaforums.com/showthread.php?t=1290324

It looks like the first 2 lines are new and the third is just a value change. Kinda curous why pm.sleep_mode isnt there to begin with though.
[Samsung Epic 4G Touch] nibrwr:
Just added this. Am I imagining it, or does this ROM feel quicker now?
[Samsung Epic 4G Touch] Custodian:
Sorry im always in a rush lol... maybe calk over looked sleep pm or just didnt add because of his modifications. As for the odex settings, not many devs dabble around to find new changes etc... doesnt hurt for us users to make it aware to them though.
[Samsung Epic 4G Touch] Custodian:
No doubt the rom is smokingly quicker snd smoother! You added those dalvik tweaks that gives you the performance of an odex rom while youre deodexed. I personally dont even odex roms anymore... :-)
[Samsung Epic 4G Touch] tdunham:
The dalvik flags value change, phone stuck at first Samsung screen. No UV, rogue 1.3.0 kernel.

I used an editor developed by Nathan and he has a thread here. I changed the existing values from m=y to the ones you posted. Any ideas?
[Samsung Epic 4G Touch] mrcrptguy:
Does anybody know how to use the stock android lockscreen with this Rom?
[Samsung Epic 4G Touch] rondietz1:
Battery stats

With all the talk about battery stats and battery life, anyone know of a thread that explains in detail what all the battery stats mean? I can look at the stats (what's the best place to look?) but I can only take an intelligent guess at what they are really telling me. What % should be used by Android System vs Android OS, what's reasonable for Cell standby and Phone idle, etc. Before someone states the obvious, I know that all this will greatly differ by user and phone setup, but what should I be looking for, what is a good cause and effect? If I knew what all these things mean and what phone services use what resource, I could maybe setup my phone a little more intelligently to maximize battery life without sacrificing too much performance.

Just an attempt at a little more knowledge to further the phones enjoyment.
[Samsung Epic 4G Touch] akarol:
After making the tweaks, I also couldn't get passed the Galaxy logo.
[Samsung Epic 4G Touch] tdunham:
Just so everyone knows, I only applied the one tweak for flags to make sure that was it.

Thanks Custodian for the build prop dump, I'll check it out a little better when I get back later.
[Samsung Epic 4G Touch] s2kdriver:
I haven't tried and verified the performance gains, but here is a short explanation of what is being modified.

This will cause the phone to sleep deeper by lowering power consumption. I have heard of people who overclock or undervolt can experience issues when waking the phone up.

These two settings turn off the Dalvik class pre-verifications.

The Dalvik Virtual Machine by default will attempt to pre-verify and optimize class loading of any newly started application. This causes the first start of the app to be slower, but increases the speed of any subsequent app restarts. The verification process also determines the application to be structurally sound.

Think of it as an insurance policy for "bad" apps.

Hope this helps.
[Samsung Epic 4G Touch] s2kdriver:
When Android displays battery usage it is in percentages since last reboot.

If you have a phone and it is very lightly used then the Android OS will be at the top since it is the only thing really running. "Android OS" battery usage is comprised of the bottom two layers of the OS, i.e. Dalvik VM w/associated libraries (the engine) and the Kernel (drivers and settings). Everything else (Applications and the Application Framework) should be itemized.

Now if you watch a movie or launch a game shortly after a reboot it should push your app or framework resource (display) to the top of the list.

The main thing to look out for is very abnormal usage patterns. For example, if you don't use it very much, but the phone usage or time without signal is very high then something is definitely wrong.
[Samsung Epic 4G Touch] tdunham:
S2k, our new little programming buddy. :D

Ok finally got to a pc. Someone please tell me that the build.prop can be edited from a pc... :confused:

Because, I'm gonna have fun with Custodians wildly modded Build.Prop file :).
[Samsung Epic 4G Touch] s2kdriver:
Thanks, that is a good idea. You are right because this really isn't a particular ROM issue. It is, in fact, a Gingerbread issue. I really respect the work and time that the developers put into these kind of endeavors. I have been a long time fan of Calkulin's especially. But even the developers have to start with what is available from the open source releases.

I'm just trying to get my sh*t together before I possibly jump off into any potential flame riots. I consider myself to be a noobie when it comes to the E4GT and that is why I watched and researched the posts for a month or so before posting. I'm still playing catchup to most of you. But, i do have the desire and willingness to assist where possible.
[Samsung Epic 4G Touch] tdunham:
We really appreciate any help that people can provide. With all due respect, Calk is spread pretty thin working with multiple developers and all the ICS issues as well. Since this is one of the most popular ROMs, we get wide a range of users here. I help where I can but I'm relatively new too so when something like the build.prop tweaks drops by it's really exciting to try something different.
[Samsung Epic 4G Touch] driftinganomaly:
I am still more of a newbie than yourself. I have read thousands of pages of forums and have only started to post. I am trying to post answers to simple problems to help take the load off of the other helpful people on the forums. I can follow directions and am constantly expanding my knowledgebase, but still have a long way to go.

With your background, you will be a real asset to the community as your time and interest allow. Good luck and look me up if you ever need a tester. I work full time and go to school at night, but I still squeeze a bit of time for android related research.
[Samsung Epic 4G Touch] daniel4653:
Hey do I just copy and paste this into the build prop?
[Samsung Epic 4G Touch] tdunham:
No way don't do it :).

The dalvik.vm.dexopt-flags=v=n,o=v is an existing line that needs to be edited.

I did a nandroid right before editing this line and sure enough the phone wouldn't boot so I've got to figure that out why. I was using a build.prop editor app specifically designed for this purpose too.

So the moral of the story is... backup first!
[Samsung Epic 4G Touch] s2kdriver:
I might just take you up on this. I just joined the Samsung Open Resource Center and am now downloading all three open releases for the E4GT. I might also note that there aren't many discussions on their forum about our phone. I think I'll change that.;)

Update: Sorry about the link, I have corrected it.
[Samsung Epic 4G Touch] tdunham:
You probably know better but make sure they're for the D710 not the D700.

There are several flavors floating around, good way to brick a phone inadvertently.
[Samsung Epic 4G Touch] Custodian:
My apologies.. thought I mentioned.. if the line exists already, simply remove it completely and add those to the bottom of the build.prop. also make sure that there's an empty space after the last line in the build.prop

Like.,:

David.Cow.Horse=1234

Space here
[Samsung Epic 4G Touch] s2kdriver:
Good point, but I already made sure of that. They are the three releases of the SPH-D710. Oh - and now I know why they are very few posts out there. I tried two different times to post something and both times the window shutdown with a invalid URL when I tried to submit it. :mad:
[Samsung Epic 4G Touch] akarol:
Aha! That was the culprit for freezing my phone in the Samsung logo. I had created an additional line for the flags command and it was causing problems. Since then, I just edited the previous on from m=y to v=n,o=v and it's all good to go now.

Thanks for the heads up!
[Samsung Epic 4G Touch] Toonlinkmaster25:
How can I get the 5x5 app drawer back

Sent from my Epic 4G Touch on Calc's GB ROM
[Samsung Epic 4G Touch] shinedown87:
If I get an error stating that the package file is invalid when installing an app (Instagram) is it a ROM issue?

I have tried rebooting and clearing cache and Dalvik but nothing seems to work.
[Samsung Epic 4G Touch] tdunham:
Sounds like a bad download. Was this a download from the Market?

---------- Post added at 11:15 AM ---------- Previous post was at 11:04 AM ----------

I think you mean the default touchwiz launcher (I use Go Launcher so don't recall). You can reinstall that from the Stock_EL29_TouchWiz_Launcher zip on the OP.
[Samsung Epic 4G Touch] ling4383:
thanks calk!

Just now downloading the latest...this rom was my very 1st flash and my "goto" rom when i wanna go "back to basics" (noticed he has an ics rom out but i havnt played with that one as much).i also saw the thread on how you arent "recognized as a developer" and read how many xda members disagree...i am one of those.huge fan of your work calk!just showin some appreciation:)
[Samsung Epic 4G Touch] tdunham:
I extracted the app for you. Here is the link you can download it and try to install it manually.

http://dl.dropbox.com/u/57223406/com.instagram.android.apk
[Samsung Epic 4G Touch] Toonlinkmaster25:
No in earlier builds Calk modified the app drawer to 5x5 instead of 4x4 but now it's 5x4

Sent from my Epic 4G Touch on Calc's GB ROM
[Samsung Epic 4G Touch] tdunham:
Ah ok. I guess the best thing to try it is to extract touchwiz from the version of this ROM that has it and replace the touchwiz you're using now with that one. Let us know if you need help with that.
[Samsung Epic 4G Touch] Maxx134:
Hi is there any setting for charging thru USB?

I dont know why I cannot get it to charge

as I am plugged in but see my battery level dropping...
[Samsung Epic 4G Touch] tdunham:
Does the notification LED turn red Maxx? Also is the USB port on a desktop or laptop?
[Samsung Epic 4G Touch] Maxx134:
Yes light on I think maybe because this desktop not hVe the samsung drivers?
[Samsung Epic 4G Touch] Toonlinkmaster25:
I'd like some help with that

Sent from my Epic 4G Touch on Calc's GB ROM
[Samsung Epic 4G Touch] Custodian:
Anyone have issues with the buildprop I posted?
[Samsung Epic 4G Touch] nibrwr:
Nope, no issues whatsoever. I copy/pasted it line for line, and rebooted
[Samsung Epic 4G Touch] shinedown87:
Thanks! I was able to install it without problems, however when I run the app it says my device isn't compatible because it doesn't meet the minimum camera requirements. Strange.
[Samsung Epic 4G Touch] tdunham:
I have a flashable zip I will post for you in a little while.
[Samsung Epic 4G Touch] tdunham:
Here is a flashable Touchwiz 5x5 launcher taken from Calk's 2.7 ROM.

Let me know if it works for you. Also, you may want to wipe caches before rebooting after flashing.
[Samsung Epic 4G Touch] shinedown87:
Also, maybe I could ask you another question...when I try to download large apps (like greater than 15 mb) I get an error saying there is insufficient space on the device.

Maybe I just need to delete some apps? I have tried moving lots of them to sdcard bit that hasn't seemed to help. When I check my storage amounts in the menu, it appears that I have plenty.
[Samsung Epic 4G Touch] Toonlinkmaster25:
Couldn't flash it it just aborted.

Sent from my Epic 4G Touch on Calc's GB ROM