yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] k0nane:
Thanks for getting some data! It's high time someone did so.

A kmsg would be incredibly helpful to go along with this. For future reference, you may wish to paste to pastebin.com for readability and to save space.
[Samsung Epic 4G Touch] DarkPhoenix:
OK I will do that. How do I go about getting a kmsg?
[Samsung Epic 4G Touch] frifox:
cat /proc/kmsg?
[Samsung Epic 4G Touch] jirafabo:
Would it help to add some others? I'll need direction as I've never done a logcat but I'm willing to learn and share...
[Samsung Epic 4G Touch] k0nane:
This, on a rooted phone.

Hook up to your PC in debugging mode, have adb at the ready, and do:

adb shell cat /proc/kmsg > out.txt

...right after an LOS incident. Then pastebin the context of the .txt.
[Samsung Epic 4G Touch] dtm_stretch:
Here is a kmsg after a LOS incident

http://pastebin.com/4HQTMH2C
[Samsung Epic 4G Touch] jirafabo:
Tried it without a LOS incident, just to practice... The out.txt gets output to the same folder as ADB correct?

Found it and it just said this..

"cat: can't open '/proc/kmsg': Permission denied"

logcat printed out fine.....
[Samsung Epic 4G Touch] dtm_stretch:
Make sure you give super user rights. after adb shell type su and then acknowledge on your phone.
[Samsung Epic 4G Touch] jirafabo:
thanks good sir. yeah i tried that too, but i didn't acknowledge on phone, i already have so wasn't asked too. trying again, here's my results, tried two different commands....

\

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bo>cd..

C:\Users>cd..

C:\>cd androidsdk/tools

C:\AndroidSDK\tools>adb shell

$ su

su

# adb shell cat /proc/kmsg > out.txt

adb shell cat /proc/kmsg > out.txt

adb: not found

# cat /proc/kmsg > kmsg2.txt

cat /proc/kmsg > kmsg2.txt

cannot create kmsg2.txt: read-only file system

#
[Samsung Epic 4G Touch] dtm_stretch:
after you have granted su just type

cat /proc/kmsg then just right click>select all>paste in paste bin

for some reason creating the .txt is causing the error
[Samsung Epic 4G Touch] jirafabo:
That worked. Weird that it won't write the file now, as it did for logcat and it actually did earlier but with an error written in the txt file. Oh well, this way worked.

I'll share my kmsg in the morning when I wake up with my LOS.
[Samsung Epic 4G Touch] dtm_stretch:
Bump just in case no one reads the first page. This is after an LOS.
[Samsung Epic 4G Touch] frifox:
or better yet, bugreport -d > /sdcard/bugreport.txt and pastebin that file.

i set my tasker to detect LOS and dump a log/bugreport to sdcard as soon as the sh1t happens. see this thread for more info:

http://xdaforums.com/showthread.php?t=1286773
[Samsung Epic 4G Touch] eagercrow:
Great minds think alike!

Here is my post in that other thread:
[Samsung Epic 4G Touch] DarkPhoenix:
That's not a bad idea. I tried running bugreport -d > /sdcard/bugreport.txt but when I open it the text inside says that the file is to large.

Also added a few more logs to the 2nd and 3rd posts.
[Samsung Epic 4G Touch] eagercrow:
I get the same error, you have to open it with something other than the text editor or transfer it to your computer.
[Samsung Epic 4G Touch] DarkPhoenix:
OK thanks.
[Samsung Epic 4G Touch] jirafabo:
Here's my kmsg from tonight. Had the LOS bug but this time it was WITHOUT or before the icon showed up. Turns out my phone was LOS for over 3 hours, without LOS icon. This happens quite often too. I just wonder if it's before the icon is activated, bc it still shows some bars.

http://pastebin.com/ArVRNf1j < ---- not complete, will post another soon.

it looks like my cmd window is cutting off after the logcat or kmsg gets too big. i had to edit my "buffer size" so it looks like that kmsg was shorter than it should be. i did manage to send a complete logcat to my sd card from the phone, so I'll post that for now...

and... Logcat too big for pastebin. I'll clear and try again tomorrow.
[Samsung Epic 4G Touch] DarkPhoenix:
I have noticed that mine is doing the same thing. I will post your logs to the top of the thread once you get the complete log posted. Thanks
[Samsung Epic 4G Touch] Pheno.menon:
I keep reading "lolcat" every time I glance at the thread title. Internet, you have spoiled me..
[Samsung Epic 4G Touch] k0nane:
jirafabo, thanks for the kmsg - it's that, over logcat, that really needs to be complete. You can upload the text files to Dropbox or Mediafire and link them here. The more info the better - once we have a complete log, the true experts can have a look. I may alert mkasick to this.
[Samsung Epic 4G Touch] DarkPhoenix:
I just had something weird happen. I was playing with LCD Resolution and applied a new resolution setting, LCD Resolution asked to restart the phone to apply the new settings and asked for root privileges. I allowed root privileges and it restarted the phone. I noticed that this wasn't a full reset but a reset kind of like restarting your xserver in linux. When the phone restarted I noticed that I had a LOS occurrence. I kept playing with LCD Resolution and applied the resolution settings 2 more times which of course restarted the phone 2 more times. After the last restart I noticed that the LOS was gone and my signal was restored.

Edit: I have added 3 more logs, 2 in the 2nd post and 1 log in in the 3rd post. I really hope someone can use all of these.
[Samsung Epic 4G Touch] DarkPhoenix:
OK quick update, after making the post regarding the LCD Resolution LOS my 3g went off and my signal dropped to zero. I still had the signal strength indicator but no signal. I did not get the circle with the line but I had no connection. I actually missed a call from my wife because of it. I restarted and am back to normal.
[Samsung Epic 4G Touch] jirafabo:
Someone mind explaining what a kmsg is? It seems like it just keeps going forever when I run it. I'm assuming it's just a readout of current information and it keeps updating as long as you leave it open? Also when I look through it, it looks like same information over and over.
[Samsung Epic 4G Touch] jirafabo:
Here's my most current one. Not sure why mine are so freaking long....

http://pastebin.com/Xr4dF8nx
[Samsung Epic 4G Touch] DarkPhoenix:
Thank you, I've added it to the 3rd post. I don't know much about kmsg but I believe it is a kernel message that contains information relating to anything thing the kernel does.
[Samsung Epic 4G Touch] dtm_stretch:
Do we need more kmsgs and logcats or has someone looked at these and got the info they need?
[Samsung Epic 4G Touch] frifox:
not just kmsg & alogcat but rather a full bugreport dump. already posted it in LOS Alarm without realizing that there is a thread for such.

ps: looking at the bugreport, note line 16,161:

this is where sh1t hits the fan... definitely not healthy :D
[Samsung Epic 4G Touch] DarkPhoenix:
Thanks for the report. This is the first bug report I've had uploaded. It's been moved to the 4th post.
[Samsung Epic 4G Touch] DarkPhoenix:
I will keep posting them as long as they are posted. I think the more we have the better.
[Samsung Epic 4G Touch] frifox:
got another bugreport... this time it happened when phone was supposedly asleep. after a quick look at the radio dump, i see this pattern.

just before LOS (or during) i see repeating message like 1000000 times

then, i notice first signs of failures

and finally, after more of that GPS loops, OEM_HOOK_RAW fails, and what seems like CDMA requests we get

at which is where, i'm assuming, the phone gave up and turned my radios off, which is confirmed by the kernel dump:

GPS at fault? horrible timing? bwuah, i'm getting sick of this LOS :eek:

ps: bugreport attached, as usual.
[Samsung Epic 4G Touch] squshy 7:
Lol mkasick to the rescue ;) he would definitely be the one to contact about this
[Samsung Epic 4G Touch] mkasick:
Can folks post the output of:

adb shell 'cat /proc/interrupts' > interrupts.txt

and specify which kernel you're running? Doesn't matter if you presently suffering LOS or not.

I also shouldn't need more than one for each kernel.
[Samsung Epic 4G Touch] dtm_stretch:
I am running Chris' stock plus.

cat /proc/interrupts: not found

*Edit* Disregard, issue with ADB pushing outputs with .txt. I am on LoStkernal and someone else posted those outputs.
[Samsung Epic 4G Touch] frifox:
interrupts dump for this kernel:

https://github.com/chris41g/LoStKernel

CPU0 CPU1
99: 0 0 GIC s3c-pl330.1
100: 2434 0 GIC s3c-pl330.2
106: 382961 0 GIC mct_tick0_irq
108: 0 0 GIC s3c2410-rtc alarm
109: 0 0 GIC s3c2410-rtc tick
112: 39 49636 GIC mct_tick1_irq
122: 165 0 GIC s3c2410-i2c.0
123: 216647 0 GIC s3c2410-i2c.1
124: 0 0 GIC s3c2410-i2c.2
125: 36184 0 GIC s3c2410-i2c.3
126: 18 0 GIC s3c2410-i2c.4
127: 160979 0 GIC s3c2410-i2c.5
128: 301342 0 GIC s3c2410-i2c.6
129: 34 0 GIC s3c2410-i2c.7
135: 1407 0 GIC s3c-udc
136: 1096 0 GIC DPRAM irq
139: 42870 0 GIC mmc1
140: 9551 0 GIC mmc2
141: 33307 0 GIC mmc0
142: 0 0 GIC s3c-csis0
144: 0 0 GIC s3c-csis1
148: 0 0 GIC s3c-fimc0
149: 0 0 GIC s3c-fimc1
150: 0 0 GIC s3c-fimc2
151: 0 0 GIC s3c-fimc3
152: 0 0 GIC s5p-jpeg
153: 6963 0 GIC s5p-fimg2d
155: 0 0 GIC s5p-mixer
156: 0 0 GIC s5p-hdmi
158: 0 0 GIC s3c-mfc
160: 0 0 GIC s5p-rp
169: 1995 0 GIC s3c64xx-adc
178: 0 0 GIC s5p-tvout-cec
182: 0 0 GIC mali_mmu_irq_handlers
183: 0 0 GIC mali_mmu_irq_handlers
184: 0 0 GIC mali_mmu_irq_handlers
185: 0 0 GIC mali_mmu_irq_handlers
186: 0 0 GIC mali_mmu_irq_handlers
187: 9119 0 GIC mali_core_irq_handlers
188: 8876 0 GIC mali_core_irq_handlers
189: 9054 0 GIC mali_core_irq_handlers
190: 9079 0 GIC mali_core_irq_handlers
191: 9249 0 GIC mali_core_irq_handlers
224: 0 0 COMBINER s5p-sysmmu
225: 0 0 COMBINER s5p-sysmmu
226: 0 0 COMBINER s5p-sysmmu
227: 0 0 COMBINER s5p-sysmmu
228: 0 0 COMBINER s5p-sysmmu
229: 0 0 COMBINER s5p-sysmmu
230: 0 0 COMBINER s5p-sysmmu
231: 0 0 COMBINER s5p-sysmmu
232: 0 0 COMBINER s5p-sysmmu
233: 0 0 COMBINER s5p-sysmmu
234: 0 0 COMBINER s5p-sysmmu
235: 0 0 COMBINER s5p-sysmmu
236: 0 0 COMBINER s5p-sysmmu
237: 0 0 COMBINER s5p-sysmmu
238: 0 0 COMBINER s5p-sysmmu
239: 0 0 COMBINER s5p-sysmmu
281: 6451 0 COMBINER s3cfb
325: 1873 0 s5pv310-eint k3g
326: 0 0 s5pv310-eint proximity_int
328: 4988 0 s5pv310-eint mxt224_ts
331: 687 0 s5pv310-eint max8997-irq
332: 13 0 s5pv310-eint QSC_INT irq
334: 10631 0 s5pv310-eint CP_DUMP_INT irq
338: 1 0 s5pv310-eint QSC_ACTIVE
340: 0 0 s5pv310-eint gpio_keys
341: 2 0 s5pv310-eint gpio_keys
342: 0 0 s5pv310-eint akm_int
343: 2 0 s5pv310-eint max17042 fuel alert
345: 5601 0 s5pv310-eint bcmsdh_sdmmc
346: 0 0 s5pv310-eint bt_host_wake_irq_handler
347: 8 0 s5pv310-eint gpio_keys
350: 0 0 s5pv310-eint sec_headset_detect
352: 1 0 s5pv310-eint AST_CD#
355: 1 0 s5pv310-eint hpd
356: 0 0 GPIO s3c-sdhci.2
383: 41623 0 GPIO AST_INT#
481: 210 0 GPIO mhl_int
496: 0 0 GPIO mhl_wake_up
537: 66 0 GPIO sec_touchkey
570: 1 0 max8997 chg-insert
571: 0 0 max8997 chg-remove
573: 0 0 max8997 chg-topoff
577: 240 0 max8997 rtc-alarm0
582: 0 0 max8997 muic-adc
584: 0 0 max8997 muic-adcerr
585: 1 0 max8997 muic-chgtype
589: 1 0 max8997 muic-vbvolt
IPI: 35782 61459
LOC: 0 0
Err: 0
[Samsung Epic 4G Touch] jirafabo:
Here's mine... http://pastebin.com/PFF9UWWi

Running ZedoMax v3.

Was not suffering LOS at the moment, but do run into one or two a day.
[Samsung Epic 4G Touch] musclehead84:
Mkasick is the man we need to figure this out. Thanks for helping.

Sent From My Evo Killer!!!
[Samsung Epic 4G Touch] mkasick:
Thanks for the interrupt lists. I'm still working on this, but I think I've already seen one odd thing. There's an external interrupt, EINT7, that appears to be frequently (spuriously?) bringing the phone out of suspend state. It corresponds to interrupt "87" in that list, which doesn't exist, hence isn't registered or used by anything. Nor can I find any refernce to it in the kernel source. So I think there might be a bug in the generation of the external interrupt wake up mask. But I need to look at this more, possibly tomorrow. I'm also not sure how related to LOS that is, but I'm just working through the bug reports at the moment.

Anyways, the earlier bugreport collected via tasker as soon as the radio cut out is really useful. If possible, I'd like to get another. But it would be even better to have one bug report as soon as the radio cuts out (as the existing one), then another bug report, say, five minutes later.

As for LOS, I think it might be related to when the phone suspends, which in some of these kmsg logs it appears to be doing rather frequently, at least once a minute. One thing worth trying, and anyone who is rooted (even running a stock kernel) can do. Before you hit LOS, open a root shell and run:

echo foo > /sys/power/wake_lock

which will keep the phone from suspending untli the next reboot, and hopefully prevent LOS if it is related to suspending. This may result in decreased battery life, which is why it would be nice to address the frequent suspending issue, but I guess that's better than having to reboot all the time.

If for some reason you want to disable that wake lock, in a root shell run:

echo foo > /sys/power/wake_unlock

or just reboot.

Hopefully that's a start. I'll look into this again tomorrow or Wednesday when I have more time.
[Samsung Epic 4G Touch] frifox:
Set my Tasker to dump bugreport at the time of service loss and 5mins after the initial dump. I'll refrain from wakelock until I hit another LOS.
[Samsung Epic 4G Touch] frifox:
haha, wasn't too long till I hit another LOS :D running same kernel as that interrupts dump just above.

here attached are the bugreports, one at the time of LOS and another 5 minutes later. It seemed to me the LOS happaned (or at least Tasker popped the notification) right when i turned my phone on after some time of screen-off time, during which for past 5 minutes gmail was trying to send an email. Email wasn't sent, so it could be that LOS actually happened before and Tasker and/or NoService icon appeared when i woke the phone up.

either way, the two bugreports are attached.

ps: 1st bugreport was right when LOS was detected, and 2nd bugreport is 5 minutes into the LOS. i rebooted the phone after 2nd bugreport was dumped, and as always got the service back.
[Samsung Epic 4G Touch] chris41g:
mkasick nice to see you over here

id like to talk to you on irc if you dont mind, and have you take a look at my kernel source which seems to have eliminated the LoS almost completely... and discuss what causes it and why... maybe we can nip this thing.. you are just the expert i needed to see...

if you dont mind, irc.freenode.net #lostkernel
[Samsung Epic 4G Touch] mkasick:
I took a glance at these, I'll have to go through them again more thoroughly later. But the dmesg log in the first report only contains two minutes worth of logs during which the phone attempts to suspend 40 times, each failing due to one of two different errors, one of which is the radio (actually dpram) failing to suspend, and the other the alarm device.

Unfortunately becuase the suspend errors comprise the entirety of the kmsg buffer I can't see where it begins in this case, although your previous bugreport may shed some light on that. From the radio log it looks though that "the problems" start sometime between 20:43:38 and 20:45:18, with the RIL not noticing until 20:46:23.

Probably what happens is that data connectivity is lost and that's reflected in any data-utilizing program not working. But the phone doesn't "realize" there's a radio event until a short time after, when it attempts to actually power down and reset the whole thing. Which, from what I can tell actually works, until the next suspend event when dpram blows up and the RIL gives up for good.

Would you mind grabbing another bugreport without LOS? Preferably after the phone has been booted for a while and you haven't otherwise used it in the past ten minutes or so.
[Samsung Epic 4G Touch] frifox:
non-LOS bugreport attached.

note that this one (including the ones i loaded above) is from my "daily" rom which is loaded with apps/widgets and some /system mods/tweaks (nothing too serious tho). i also got a "testing" rom which is cleaned stock rom + same kernel as above with no extra apps installed besides tasker and su. i can switch over to it and try to get a cleaner bugreport if you need, just lemme know.
[Samsung Epic 4G Touch] chris41g:
@mkasick

Removing the debugging from dpram, and fixing it to compile seemed to fix it... for the most part.. then make small patches to cpufreq...
[Samsung Epic 4G Touch] DarkPhoenix:
Hi everyone, sorry I've been busy working for the last few days and haven't had a chance to do much with this thread. I will get it cleaned up and get the logs moved to the first few pages. I'm glad this info is useful. Thanks everyone that is posting and trying to resolve the issue.
[Samsung Epic 4G Touch] mkasick:
Although the dmesg log covers 20 minutes, there's no suspend instances in it. Were you actively using the phone in the 20 minutes preceeding the bugreport?

If not, it might be that the extra widgets are resulting in more wake locks and so it's not going into suspend. Perhaps the testing ROM is worth a shot.

Also, you didn't apply the manual wake lock I suggested above right? I am curious if doing so reduces LoS events, but it shouldn't be applied when collecting a bugreport--I'm trying to get a glimpse of the phone's non-erroneous suspend behaivor.
[Samsung Epic 4G Touch] frifox:
phone wasn't used for at least 40 minutes but it could have been that leaving it attached to usb prevented the suspends... i'll take if off usb and post a proper bugreport in 1hr. after this, i'll switch to my stripped rom and see if i can get LoS tracked on that one as well.

no, haven't wakelocked it yet... i usually don't get LoS at my home but i do at my work, which is where i'm heading to in 40mins.
[Samsung Epic 4G Touch] frifox:
here's a dump with phone being off usb & no LOS
[Samsung Epic 4G Touch] DarkPhoenix:
All logs have been moved to the first 4 posts in the thread respectively. Thank you.:D
[Samsung Epic 4G Touch] frifox:
correct, most of bugreports i dumped were with my phone charging but not always... some (don't remember which now) were taken while i was driving and phone was not connected to anything.

^^ will do that right now.

this morning, my phone was on WiFi. when i left to work i flipped WiFi off and noticed that 3G didn't come back on. then, i flipped airplane mode on and off and right away i got the no-service logo, at which point tasker kicked in and dumped these bugreports. not 100% sure if this was the traditional LOS case but either way, here attached are the bugreports in case someone would like to check them.
[Samsung Epic 4G Touch] mkasick:
Great!

Yeah, it's already a goner by the time tasker kicks in. But thanks!
[Samsung Epic 4G Touch] slixzen:
Here are a couple more logs

Here are a couple more logs, this is a running logcat file while the "LoS" issues happen. Phone was not charging, sitting at my desk with the WiFi turned on. We have a Airave in our house, so it shouldn't even drop signal out, especially when I sit right next to it.

My phone is rooted, however, I am using the stock Sprint Kernel.

http://www.mediafire.com/?3os3s13gtzp8sd8

And here is a bugreport output as well:

http://www.mediafire.com/?3sznsfsdqmewe68

Sorry, couldn't upload or paste these on to pastebin so I resorted to mediafire.

They are direct .txt files.
[AT&T Samsung Galaxy S II SGH-I777] naturallyfrozen:
I'm getting my phone soon. I hope (I'm begging) I get to see a MIUI rom for this phone. Don't YOU like MIUI?
[AT&T Samsung Galaxy S II SGH-I777] poofyhairguy:
Don't worry, now that the iPhone announcement is such a letdown AT&T will sell millions of these phones. In a few months you will have more ROMs then you can handle.
[AT&T Samsung Galaxy S II SGH-I777] naturallyfrozen:
Yeah, that was pretty bad... Whatta letdown..
[AT&T Samsung Galaxy S II SGH-I777] rodger-sp:
yes I too want the MIUI ROM
[AT&T Samsung Galaxy S II SGH-I777] nraudigy2:
Vote MIUI for Galaxy S2 here. From the developers of MIUI.

http://www.facebook.com/questions/217517851641131/?qa_ref=ssp
[AT&T Samsung Galaxy S II SGH-I777] naturallyfrozen:
Awesome. Thanks!
[AT&T Samsung Galaxy S II SGH-I777] alton987:
I posted a work around around for now.

Basically flash international ROM then flash ATT kernel and modem. Everything works but wifi, Bluetooth and home button.
[T-Mobile myTouch 4G Slide] Blue6IX:
Anyone come across a place in the code where you can configure the brightness of the light behind the hardware keyboard and the hardware buttons on the face?

Here's the deal, the buttons on the front facing of the phone are just too damn bright, and now that I have one of those privacy-shield screen protectors on (love it, btw) the hardware buttons are way too bright, about 3 times the level of light that emanates from the screen.

I desperately need to figure out how to dim those front face buttons, because it's really screwing with my eyes while i'm trying to work with the device.

Everything I search for on XDA comes up with using the hardware buttons to set the brightness levels, but nothing about setting the brightness levels of the backlit buttons themselves.

While we're poking around on it I figured we should see about the brightness level of the hardware buttons on the keyboard, too. I think they're fine, but someone else might want to adjust it and it stands to reason to concentrate the info all in one spot.

Anyone come up with a clue while browsing through the device, or know how to do this? I don't want to lose all the illumination, just dim it a bit.

Thanks!
[T-Mobile myTouch 4G Slide] Blue6IX:
Clue 1:

In kernel source, /arch/arm/mach-msm/board-doubleshot.c

Around line 2300 some info defined.

More as it's found, going through all kernel source line by line takes a while.
[LG Optimus 3D] mrfantastic:
I have the Rogers version of the Optimus 3D(p925g) and I cant get flash videos to play all I get is sound and a green screen. I have tried uninstalling and reinstalling updating to flash 11.0. Flash ads work sadly, I was wondering if anyone else was having this issue?
[LG Optimus 3D] CallMeAria:
I think the problem lies in Flash 11 itself. You need to downgrade to Flash 10.3 and all should be well. Were having problems with flash 11 on the Thrill as well.
[Samsung Epic 4G Touch] chris41g:
Stock EG30Plus Kernel for Epic Touch 4g compiled from source, properly.

Proper initramfs

ClockworkMod 5 (Compiled by bubby323)

Various Virtual Machine, Kernel and Network Tweaks I've been using in my plus kernels for quite some time...

Bootanimation support, either bootanimation.zip or sanim.zip

init.d support

Does NOT install Root

Does NOT install Busybox

Odin the tar.md5 file

Immediately update profile

Made this one for cnz, calkulin, and crawrj

http://www.forums.acsyndicate.net/s...-Plus-Tweaks-(No-root-and-does-not-install-BB)

Source:

https://github.com/chris41g/EG30Plus

Thanks to qbking77 for the how to video:

http://www.youtube.com/watch?v=kExN-Y2pfxA

Thanks to:

bubby323

Drockstar

Johncorleone

pyrostic

rjmjr69

nubecoder

thefredelement

cnz

calkulin

crawrj
[Samsung Epic 4G Touch] slick4mitch:
Not sure why but the .tar file is followed by a .md5 extention, so I just removed it and it became a .tar, just for others to know, thanks ;)
[Samsung Epic 4G Touch] chris41g:
the md5 extension is so you know it hasnt been messed with, and so you know the download is not corrupt...

odin flashes md5s and checks the downloads...
[Samsung Epic 4G Touch] Beejis:
What would be the benefit of flashing this versus your other similar kernel? Sorry if this is a stupid question....
[Samsung Epic 4G Touch] crawrj:
Thank you so much. This is perfect. Do have a question. Does this have a new version of cwm or the same one from yesterday? I ask cause the back soft button wasn't working and the storage mounts were reversed. Just checking to see if that has been fixed.
[Samsung Epic 4G Touch] slick4mitch:
Ok, good to know, thanks for the reply and the lesson :)