yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] 30secs:
I'm sorry if this has been brought up... but my battery life seems to be pretty short.. and not only that.. but the battery dies even when it's USB-connected!!

Is this a known issue? that's pretty bad if even pluggin it to the computer or car won't save your phone from a slow and gruesome death!
[Fascinate Android Development] norm883:
Vinnie981 need more information. If you flashed I believe something went wrong and you need to start from scratch with ODIN. Post more specifics.

Norm883
[Fascinate Android Development] Neuman.Tim:
I got the kernel panic on a reboot after going to com rom from this. Battery pull fixed it but still..I was like wtf

SCH-I500 - EC09/ComRom 2.1/Crysis Revolution/Launcher Pro Plus
[Fascinate Android Development] kuronosan:
Had an SD crash, but SD was fine after a reboot. It only happened when I was trying to use something related to photo/video.

It's pretty sad that CM7, coded by jt, has more stability with video/netflix/gps than an official test ROM by Samsung.

Has anyone tried making a backup of the APN settings, flashing CM7, and seeing if restoring them fixes MMS like it does with other phones?
[Fascinate Android Development] sfobrien:
Got the same thing when I tested flashing ComRom over EC09. Odin EB01 and then build back up to ComRom and you will be fine.
[Fascinate Android Development] not balanced:
I have been running Nameless V4.0 since Monday morning without any issues.

These are the steps I went thru:

- Came from UKB2.0, Comavolt kernel, and High Voltage theme.

- Wiped data, cache, dalvik, voltage settings, and battery stats.

- Odin'ed the GB leak.

- Used Gingerbreak to root phone.

- Wiped data, cache, dalvik, voltage settings, and battery stats.

- Odin'ed times infinity's CWM3 Voodoo Blue recovery.

- Used times infinity's CWM3 Voodoo Blue recovery to flash navenedrob-nemesis2all-OTBv2-CWM3-recovery.

- Flashed Nameless V4.0

- Flashed SB stock Battery mod.

- Odin'ed EC09 Radio/Modem

- Restored Apps/Data using Titamium Backup Pro.

My thoughts so far:

- Seems much snappier than Froyo.

- No choppiness or lag.

- Has been very stable. Only Urbanspoon, Yelp, and Poynt caused FC's.

- GPS locks in 5-10 seconds.

- Have yet to see 3G drop signal. ( No 1X notifications. )

- SD Card works and has not been affected in any way.

- USB debugging works.

- Battery life has been amazing.
[Fascinate Android Development] fortesquieu:
Did you wipe? I would like to keep EC09 radio if possible when going back to comm rom.
[Fascinate Android Development] zakth:
For the person with bad battery life, I also had that problem at first. The solution for me was to drain the battery really low then wipe battery status in recovery and fully charge it over night. Now I get a full day.
[Fascinate Android Development] Kaessa:
FWIW.. my SD card is completely fried. Windows won't even recognize it. I'm having trouble even getting my phone flashed back to something resembling working order. I've Odin'd back to stock, it acts like it takes, then when it does the update it goes into a bootloop.

I would definitely avoid flashing this to your phone.
[Fascinate Android Development] blandj:
Argh. I was doing so well running this rom. I did have issues with Go Weather producing FC's (quickly uninstalled it afterwards ... no logcat, oops :o) and the Contacts app scrolling poorly and splitting contacts all over the place, but other than that, it ran very smoothly, and battery life was insane; 40 hours with an hour and a half of display time on the very first cycle, when on froyo with all the uv my phone can handle, it lasts about 48 just sitting there.

But then I got a USB device malfunction :( I'm not taking any more chances, back to froyo it is.

That Odin wipes and replaces radio, but there is a standalone Odin for the EC09 radio. I'm still using that radio.
[Fascinate Android Development] dc iz 2 legit:
sorry for the noob question but was is the atlas v.2.2pit file in the op what does it do?

and does anybody know if the stock leak cause sd problems and if not does anybody have the link to the gingerbreak to root it
[Fascinate Android Development] rand4ll:
It repartitions the file system on phone
[Fascinate Android Development] dc iz 2 legit:
so i should do this if coming from cm7 sorry again im doing this for my gf phone im not used to working on samsung with odin and not being able to use one cwr i own a thunderbolt so you could imagine how easy it is to install roms/kernals/radios
[Fascinate Android Development] zakth:
Seeing that some people are having their SD Cards fry perhaps it would be a good ideal if they tell the developer what ROM they started with, what steps the took to flash this ROM (in detail) and also what programs they installed/used prior to the card failing. It may be something specific that's causing this. Could this have anything to do with apps being stored on SD Card? Dunno, but thus far I have not had any problems. I started with the latest official froyo release from VZW (not even rooted), and followed the directions step by step. I have no tried to install any apps on the SD Card nor have I used anything like Titanium Backup.
[Fascinate Android Development] Phasze:
Recently flashed this rom and am loving it but I have a quick question. I did a backup of my comm rom before and when I went to restore it tells me I have a bad md5 sum. It's not super important, just wanted an app or two that I forgot to backup. Any way to back this one up, restore old and then restore this one?
[Fascinate Android Development] garywojdan81:
Just wondering, if you're having sd card problems, did you use or had you used the ext4 formatting facility prior to flashing this? Can this be finding something incompatible,(between the rom & the file structure or the recovery & the rom/file structure) trying to fix it, and borking the file system in the process? Were you all coming from voodoo or did you reconvert to rfs prior to flashing this?
[Fascinate Android Development] Headcase8911:
Dude, Tim, this gb leak has not been kind to you. I flashed the 4.1 rom and went back to com rom. No sd issues other than my pc prompting me to scan it, it said it was clear but I've never seen that before. Then I had a permanent message on my phone saying my internal memory was full. Re-format, com rom 1.3 to 2.0 and no more issues. Hope all this gets worked out because the gb rom is fast, just needs some tlc.
[Fascinate Android Development] bgoodwin:
As I have had no SD card issues,I flashed back to ComRom to be safe. Looking forward to getting on a bug-free GB rom, this one was fast, smooth, and the battery life was better than anything else I have ran.
[Fascinate Android Development] ChrisDDD:
I've found CWM backups have trouble with the md5 sums after switching to another version of the recovery, which is probably the issue here since Navenedrob provided a specific recovery to use when flashing his rom. You can rebuild your md5's by using a terminal emulator, navigating into your specific backup folder and typing this command:

md5sum *img > nandroid.md5

One word of caution is that if your backup file(s) became corrupt somehow, and that's why the backup is failing the md5 check, this would basically verify the corrupt files as good. But if you've had no SD card issues like some have, you're probably fine and this should get the backups working again.
[Fascinate Android Development] norm883:
Nameless 4.0

Not sure what is going on with others using this but as for GB this is the best my phone has ever run. I have V 4.0 overlayed on the Leaked version. Only problem I had was, I had no Email but with the Emial apk from V4.1 it runs perfect. The SD card is an issue in that it is hard to connect because the USB debugging has this built it auto off. Then you need to keep re-checking.

The reason I have keep 4.0 is because Netflix works with this. Does not with leaked or 4.1. I would like the original Desk Cradle but have no idea on how to install or find a CWM install. The built in one is kinda blaahh. Many of the apps that you use the most can be loaded in the V 4.0 unzipped and rezipped. I have successfully used ROM Manager, Root Explorer, Titanium Backup, Quick Boot, Netflix, Pandora, E-mail, Kindle,and Ginger Break all in the custom rezip of 4.0 with no adverse affects.This a a great build. I would like the Reboot, Recovery, Off Main button function of 4.1 however but Quick Boot gives me that option.

Recovery from ROM Manager puts me in CWM Recovery orange. Then I need to boot to Red from advanced to load from the SD all zips. All video and camera functions appear perfect. Hope this will help others etc. For a new build it is awful quiet in here except for the SD issues. And I have not seen this, except for acting different from prior builds and (other phones - Omnia and Omnia 2) comming from windows mobile which was a major pain!

Please give me more play things.

TY

Norm883
[Fascinate Android Development] Phasze:
Thank you for the quick reply, do you mean to have it *.img instead of *img? I've tried this and it doesn't appear to be working. Still getting the md5 mismatch on both *.img and *img using that command from inside the clockworkmod/backup/<my old com rom froyo> folder.
[Fascinate Android Development] Kaessa:
I hadn't used the ext4 formatting, and I wasn't on voodoo at the time. I was coming from Evil Fascination 3.6.

Currently running CM7 on my OG Droid. *sigh*
[Fascinate Android Development] Phasze:
Appears to have been an issue with me having a space in the name, now when I try and restore it says "Error while flashing boot image!" I fear this means it actually is corrupt, can anyone confirm that or should I just flash over my old CWM and attempt to restore with that?
[Fascinate Android Development] DownRiver_Droid:
I had no problems with SD card until I did a data/factory reset and in the process I lost about half the folders on my card. I was planning on doing a restore from a prior backup, but all I lost all of them. Restoring SD card on laptop and doing an odin back to CR 2.0.
[Fascinate Android Development] Neuman.Tim:
I agree man I loved the rom but it hated me lol

SCH-I500 - EC09/ComRom 2.1/Crysis Revolution/Launcher Pro Plus
[Fascinate Android Development] Phasze:
Well I can't believe this worked, but I went into CWM and just restored my data from my back in the advanced settings and then used titanium backup when it started up(which took a while). After that I restored this ROM and restored my apps :)
[Fascinate Android Development] 92GreenGT:
Running this on my phone as well as my wifes phone, it is amazing. It's so good I don't even want to mess with it, haha. Unreal battery life to say the least, we usually got 10-12 hours of our "normal" use and our battery was dead, I unplugged my phone at 7am this morning and it's on 78% now.

I love it!!!
[Fascinate Android Development] shorttripp86:
So i've been running this for the last 2 days now, and have had very few problems. Aside from a few FC's due to a glitchy contacts list (FC's when joining a contact with a Facebook friend now and then) and a stock music player that can't repeat songs or create playlists - this ROM is pretty solid.

Also: I initially had FC's when I attempted to use the TSM boot options, but after flashing the EC09 TSM boot options zip in the theme & apps forum, I haven't had one.
[Fascinate Android Development] 30secs:
I've figured it out... the phone never charged my 3rd party batteries!! I hope this gets fixed soon...
[Fascinate Android Development] norm883:
Are others having trouble with Micro SD?

Found this on a site for another phone but is the move from Froyo to GB an issue for the SD card? They clearly say when to remove and when to reinsert.

This is the un-official release of Android Gingerbread 2.3.3 for the

Galaxy S Epic 4G ONLY!!!

This version of the ROM is pre-rooted (you have read/write rights to system files)

First

CHARGE YOUR BATTERY.

Best if at full charge. But at least 65-80%

Step 1:

*Install Drivers (mine are 64bit) seek 32bit if applicable

Step 2:

*Place phone in USB Debugging mode (settings/applications/devolopement)

Step 3:

*Run One-click Root on current phone software.

*Connect your phone to USB double-click "run.bat"

*Your phone will restart.

Step 4:

*If step 3 was successful.

*Power down your phone completely

*Press and hold

VOLUME DOWN + CAMERA (press and hold these first) + Power

If successful you will now be in ClockworkMod Recovery Mode

Step 5:

Volume Up/Down: to scroll up or down....

Camera To Select Highlighted

Power to go back

*Select "backup and restore"

*Select "backup"

This will make a complete backup of all system files, apps, application data/settings as well...This may take a while...

*Reboot system now

Step 6:

*Power off your phone,

*Un-Plug Phone from computer

*Pull out battery

*Remove and don't lose microSD MemoryCard.

*Replace Battery and Cover (Skipping placing the battery cover on could result in battery falling out while updating...BAD VERY BAD)

Step 7:

*With your phone powered off Hold down the "1"

key on your keyboard and then hold Power.

*Your phone should enter "Download Mode"

If in Download Mode connect your phone to your computer with a

*quality usb cord (by Quality i mean if you have a cord that will randomly cut out while charging dont use it.)

*Open Odin3 1.81

*Un-check "F. Reset Time"

*Click "PDA" select "Rooted-CWM-Busybox-EF02.tar"

IF all is right ODIN will show a device connected by indicating COM 4 or 1 or...The number doesn't matter. In Yellow

*It is at this point I give both sides of the USB cord a light wiggle to double check that bumping it wont cause loss of connection.

*Good Connection? Great! Press Start.

Allow a few minutes your phone will automatically restart when update is complete.

All go well?

Let's Hope

Step 8:

*Re-insert micro-sd

* Power off

*Boot into Clockworkmod Recovery (Volume Down + Camera+ Power)

*select "backup and restore"

*select "Advance Restore"

*select your backup (If this is your first time there should only be one)

*select "restore data" this may take some time

* Reboot system now

You should now be updated to EF02 Beta version of Android 2.3.3 with your apps and settings restored right down to Facebook logins and Brightness Settings.

Norm883
[Fascinate Android Development] Kaessa:
navenedrob, you might want to mention in the original post that it's not just erasing SD cards, it's killing them and eating them for lunch. Mine is unrecoverable, I'm going to have to get a new one. This isn't something that backing up your SD card will get you out of.
[Fascinate Android Development] billakid:
idk if this is a rom prob or gb issue but my haptic feedback is spazzing out.. like it random brings up the menu and it keeps pulsating randomly
[Fascinate Android Development] sfobrien:
This is a strange problem. In all my computer support and build days I don't recall an OS ever destroying an external drive or storage of any kind.
[Fascinate Android Development] kuronosan:
Well, thank God I was able to format and back up my SDCard. Glad I made a backup, too. I'm switching back to CM7 now that the sensor/call issue is fixed. I'd rather live without MMS than have my SD corrupted or formatted for random reasons. It also wouldn't work with any of the apps that CM7 worked with.

It's still strange to me that an almost beta version of an OS coded by jt is more functional and less damaging to the phone than something coded by Samsung.

It was worth a shot. I'll give it a go again if it ever gets more stable, though I imagine CM7 will be ready long before it ever happens.
[Fascinate Android Development] InfiniteRefrain:
Running since release; no sd card issues and finally going to put it on the charger: 44hrs and battery still at 10% :-D
[Fascinate Android Development] sanewicked:
Whenever Windows 7 x64 attempts to communicate with my SD card (which got wiped by EC09), it will say that the SD card is in an unsupported file system and refuses to mount either in Windows or CWM. Does that mean it is destroyed completely or could possibly formatting through other means restore it? Does anyone have any success or feedback relating to that so that I don't have to go buy a new card?

I apologize in advance if this question has already been answered.
[Fascinate Android Development] InfiniteRefrain:
Some have been able to reformat, but a limited amount of people; most had to purchase new cards. Depends on which forum site you are currently looking at. If it's unreadable, I'd take the chance, unless there are things you cannot lose. Even 16gb cards are fairly cheap across the web store.

EDIT: One question: are you trying to look at it while it is in the Fascinate, or directly plugged into your computer?
[Fascinate Android Development] Domush:
Well, I hit my first NL 4.1 bug. It seems to occasionally max out CPU for "Linux base" task. Obviously you can't just kill it, as it is the Os itself. It seems to slow the phone to a crawl for about 30-60 seconds. I was last playing Star Trader (or some such) when it happened. It might be the game, as it's only happened a few times, and I've played it a few times so far.
[Fascinate Android Development] pkopalek:
Other than normal Internet browser downloads (I just use dolphin instead)

Youtube failing

All internet videos failing (including my beloved mobile pr0n)

Open Signal Maps force closing

And a random shutdown, then reboot into what the bottom left corner of the screen called "Safe Mode"

a reboot after that revealed all my widgets to have 'Problem Loading', but no other damage.

This is definitely based on the LEAK.

A few versions higher and I'm sure this thing will be tightened up.

Very smooth, and my daily driver. Reliable other than the now-predictable force closes.

Love this ROM.
[Fascinate Android Development] Kaessa:
I agree. I've never had this problem either. I've been doing computer support for over 15 years now, and I've never had software kill a drive. I don't know what it did. Overwrote something it wasn't supposed to overwrite or something, but my computer doesn't even see it as a valid drive anymore.
[Fascinate Android Development] jpaulwaite:
just a thought: I'm from the mesmerize forums, but this is my hazard at a guess: It looks like the build is treating the internal sd card as a normal usb composite device, thus using usb data buffers when data r/w occurs. Those buffers are most likely larger than normal sdcards are meant to handle. Large volume data transactions, like watching movies, may damage you card. Just a guess though, from what I'm seeing in the ui. In the task manager the typical sd app tab says usb device, as well as moving an app to sd, says move to usb device.
[Fascinate Android Development] kuronosan:
I believe he is right. I too noticed that the system seems to believe that the sdcard is a USB composite device. If that is true, then an overflow of data could be damaging the card due to heat. I don't know.

All I know is that I was able to format the card, and I reinstalled CM7 without looking back.
[Fascinate Android Development] vash8806:
Havent had much trouble with this build, running for a week or so... Only problems:

Youtube videos broken in player, so using defualt browser as desktop. Great work around.

Had the drive mount problem at first, but after enabling usb debugging, it went away.

Force close on video playback when using camcorder app.

But you can live with these ...
[Fascinate Android Development] kuronosan:
I said that a week ago, until my SD card crapped out. At this point you're much better living without MMS and going for CM7 until this build stabilizes.
[Fascinate Android Development] Dj-Dubster_TN:
Could this bug also destroy my sdcard and make it unreadable? Cause something went gnarly and now my sdcard won't read in a computer or phone and it just keeps asking me to format it
[Fascinate Android Development] Gurm:
Yeah, that's pretty much what it does. I'm working on resurrecting my card now, but it's looking pretty grim.
[Fascinate Android Development] Highriser:
Happened before

Something like this happened to me on a previous phone I had. So, this time I formatted it and just odined back to ED01 added the files back from a backup on my computer, and restored my backup from ED04. Then everything was fine... I don't really know why everyone else is having problems. Maybe I just got lucky.
[Fascinate Android Development] chrisp304:
My guess is its corrupting the MBR, which of course would have to be repaired before you can reformat.
[Fascinate Android Development] Gurm:
No, it's not that. It's doing something low-level to the SD card, which breaks it at a fundamental level. Nothing I've done has fixed it so far (20 years in PC IT, I know all the tricks) including MBR repair, switching it to GPT and back, and using the SD Consortium low-level formatter. Cameras can't format it, either.

It's borked.
[Fascinate Android Development] fortesquieu:
I don't know how many of you actually play "words with friends", but on this ROM, that game is laggy.
[Fascinate Android Development] AnalyzeFaith:
Same issue, can anyone confirm?
[Fascinate Android Development] sfobrien:
Have you tried to go from GB to Froyo without using Odin? I tried once to test and I got same thing. If so, Odin EB01 and build back up to what version you want.
[Fascinate Android Development] AnalyzeFaith:
Done it, didnt work... What causes this?
[Fascinate Android Development] fortesquieu:
I flashed Comm Rom 2.1 from this, I get this error too. Do I have to Odin all the way back to EB01??
[Fascinate Android Development] Gurm:
I would odin back to eb01 and use the PIT files, as well...
[Fascinate Android Development] :
Sorry if this has been covered. Can we use the EC01 radio with Gingerbread Roms? Or do we need to Odin something new?
[Fascinate Android Development] nitsuj17:
ec09 radio is the wtg on ec09
[Fascinate Android Development] :
Ok. Thanks. I'll Odin it up once EC09 is more tried and tested. Are Ext4 voodoo Gingerbread kernels suppose to be faster than froyo ones, or is the Gingerbread OS just suppose to run faster/smoother than froyo?
[Fascinate Android Development] fortesquieu:
Gingerbread is suppose to be much faster than Froyo, if I recalled correctly, at least 5 times more.
[Fascinate Android Development] Falcyn:
The big performance increase (2-5x) was from 2.1 to 2.2, not 2.2 to 2.3. There is certainly still a speed difference between 2.2 and 2.3, but it's subtle in comparison and is more of an improvement in UI responsiveness than in pure speed.

The big changes between 2.2 and 2.3 are the UI, the keyboard, power management improvements, communication upgrades (NFC, VoIP), and some substantial behind-the-scenes improvements related to games.

I can tell you that, in my experience, RFS NAMELESS v4.1, even though it's Gingerbread, is very noticeably slower and less responsive than Voodoo'd EF 3.6.0 or UKB 2.1. Obviously, there are quite a few reasons for that, though, not just RFS.
[Fascinate Android Development] :
Better battery is a plus, amongst other things. Thanks for the response guys.

Sent from my fascinate
[Fascinate Android Development] deafptl4ever:
Hi

I noticed on Twitter that there was a patch released for a Gingerbread rom on Mezermise phone (spelled wrong) and it said it was to fix a SD card error problem they were having. I was wondering if they are related to this problem too as the phones are similar in some ways. :confused:
[Fascinate Android Development] fortesquieu:
So any more people with the fried SD cards?
[Fascinate Android Development] Bardasian:
I just flashed it following the instructions to the letter. Running good, slightly laggy compared to Froyo ROMs but overall good feel. No SD problems yet.

Thanks and keep up the good work!
[Fascinate Android Development] jami2976:
maybe

maybe you need to reflash a froyo kernel :confused:
[Fascinate Android Development] fortesquieu:
Yea it's been on froyo kernel when i flashed back to comm rom 2.1. I odined everything back, it's alright now.
[Fascinate Android Development] Bardasian:
Whats everyone doing to get the best life/performance from this? I've seen around 10 hours of battery with mild lag with the Nameless Kernel installed.