yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] geokilla:
Ya I tried pulling it from Serendipity before when I was on FireFly, but it was still showing the received time instead of the sent time. Dunno if I pulled the wrong SMS.apk or something...
[Captivate Android Development] nzahorchak:
What would cause images in MMS not to show on the device? They're showing up fine in my backup in Gmail. Any ideas?
[Captivate Android Development] Wdustin1:
Did u make a backup if your efs folder by chance? If you did copy that folder over your current efs and reboot and see if that fixes it

Sent from my captivate BLAZING on firefly 3.0
[Captivate Android Development] deathgod1989:
iam just wondering can i flash a different modem on this rom and kernel that came with firefly 3.0, iam sorry iam a bit new to android.
[Captivate Android Development] studacris:
Yes. make sure its an I9000 modem.
[Captivate Android Development] ap1618:
Will the Spectrum 3.2 Theme work on FireFly 3.0?

thanks
[Captivate Android Development] studacris:
Link?

Help me help you.
[Captivate Android Development] ap1618:
http://xdaforums.com/showthread.php?t=932418

Link to download 3.2 is at the end of the post.

also his website: http://racerboy3801themesxda.weebly.com/spectrum1.html
[Captivate Android Development] studacris:
That's a gingerbread theme.

Will not work.
[Captivate Android Development] ap1618:
No, he added that later. that's spectrum 1.0. Im referring to 3.2 which was older version for Froyo ROMs.

if I remember right it said it supports JPY/JS5/6/8 etc.

what is firefly based on? JS8?
[Captivate Android Development] studacris:
Oh, sorry I don't see where it says its for froyo, I believe you I just don't see it, and I assumed 3.2 was a later version if 1.0 but I guess 1.0 is just the gb port of 3.2.

I say try it, first go into the framework folder and delete any .jars you se there should only be a framework-res.apk and a twframework-res.apk. Also if it had themed settings you may lose some options, such as the clock toggle, go into /system/app and delete the settings.apk if you want to prevent that possibility. Then flash.

have another theme on your sdcard in case it doesn't work. The worst that can happen is a bootloop no permanent damage, if that happens button combo into recovery and flash the other theme.
[Captivate Android Development] Schmarvin:
Awaiting the next update for firefly. Been what, two weeks now? :/
[Captivate Android Development] BWolf56:
It has been a little bit but X is working really hard on Mosaic. He will put some time in FF when he has some :) Don't worry too much, He won't let his little baby rom go ;)
[Captivate Android Development] ryanshapiro44:
phones getting a little laggy. idk y but popups are slow and the gallery takes forever to load up, along with other little things. anything i can do to fix this? thanks in advance.
[Captivate Android Development] BWolf56:
Go in recovery and clear your cache/dalvik. You probably have too much junk packed up.

There's also a app called sd maid that can do some good if that's not enough.
[Captivate Android Development] deathgod1989:
thanks., iam getting poor signal on the modem that came with the firefly 3.0 so ill the other ones thanks :)
[Captivate Android Development] PhrProfess:
Hello everyone,

I'm using the latest build of Firefly, and I've got to say: this ROM is smoooooooth! I appreciate the transitions, and the very sharp UI. It's a great base to build upon!

I'm currently scheming and theming my phone up, and I've gotten to the unlock screens. I've had some fun replacing the OGGs in system/media/audio/ui with droplet noises for keypresses, and some awesome electric-gun sounds for lock/unlock (see attached)—but I've run into a problem that I can't seem to resolve.

I notice that there are five different unlock screens available: "Android unlock", "Rotary unlock", "Orb unlock", "Glass unlock", and "Epic unlock". My favourite of these are the first two: "Android" and "Rotary". I've seen success in modifying both of their lock sounds—but apparently, neither makes use of an unlock sound and therefore I cannot seem change it. Does anyone know if there is a way to...?

Search is proving difficult: "Android unlock sound" is too ambigious.

Thanks,

PhreshP
[Captivate Android Development] fade2black:
I am having the same issue. Phone gets slower and slower and slower. Reboot, no change. rebooted into recovery, cleared delvik/cache and that helped for about a day or two then phone slowed down again. I'm backing everything up now and reflashing FF.
[Captivate Android Development] PhrProfess:
Do you have a lot of photos on your SD (placed there by you, or by apps)? I noticed that when I attempted to copy a lot of high-resolution photos to my internal SD, and tried to view them in Gallery, my phone lagged something awful. I'd thought that this'd be only temporary, or just while Gallery was trying to thumb them all, but this wasn't the case. I ended up having to delete all of the photos, and the thumbs that appeared in /DCIM in order to rectify. I even went so far as to disable Gallery (that darn POS appli'). Following that, my phone immediately improved.

Watch for icon-packs, and skin-packs for widgets and such that contain tons of little images. This phone really doesn't like images for some reason, and tries to pick all of them up and to thumb them. This proves very problematic when one tries to copy over a couple of thousand icons at a time, or load a skin-pack for a clock widget....

I've yet to find a snappy gallery app, or a decent picture-frame/slideshow widget, and this really bugs me. I've experienced no such problems with images on old Apple products, and believe you me: that's not fun to admit.

Anyway F2B, that might be it.
[Captivate Android Development] d3v14n7:
You can fix the problem with theme/skin packs and icons and such if you create a ".nomedia" (without quotes) file within it's directory, that way the images won't show up in the gallery and won't be thumbed. You can use the same file in other directories where you don't want audio, music, videos and images to show up in the gallery or players.
[Captivate Android Development] PhrProfess:
Thanks! I do appreciate the suggestion. Unfortunately, to "hide" files from applications does in some cases defeat the purpose of loading them on the card in the first place. For example, if I were to "hide" all of my icon files with a .nomedia file, then I would not be able to access them with an application like BetterCut. Thus, they would serve no purpose :/

One might experience similar problems when attempting to hide skin-pack files.

Edit: I've since trashed BetterCut as a shortcut creating appli' (it wasn't working with FireFly anyway), and started using FolderOrganizer. When making shortcuts and folders with FO, one can make use of an application called AndExplore to select icons. This appli' will see through a .nomedia file.
[Captivate Android Development] Phoenix-Lead:
Recognized developers unite!!
[Captivate Android Development] Reynaldinho111:
I heard about that man. Congrats. Cant believe the BS xda gave you about that. Of all the devs in these forums very few deserve it as much.

Sent from my beloved Cappy!!

Rom: Phoenix Mosaic III

Kernel: eXistZ TalonDev 0.1.7

Modem: Trying JVK
[Captivate Android Development] BWolf56:
Grats man, about time ;)
[Captivate Android Development] Phoenix-Lead:
You're telling me! It was bc of the crap I said to Mikey way back when I was caught having a bad day. I just had to let them know it is in the past and take into account everything I have done around that one incident. They were more than willing to reverse it. I love how much faster the XDA pages load when there are no adds!
[Captivate Android Development] BWolf56:
haha - Just say he had it coming ;)

Kidding :p

How about you throw that no adds thing towards here :rolleyes:
[Captivate Android Development] TRusselo:
firefox use the add-on " ad-block "

IE use the privacy filter list " easy list "

no more ads!!
[Captivate Android Development] BWolf56:
I don't use firefox :p

And you're still alive :eek: Haven't seen you around in quite a while!!
[Captivate Android Development] tbong777:
Congrats..And I just happend to load up Firefly today....

Tried all the GB ROMs... Not ready for me as a daily driver..Had Obsession whack out and flashed Continiuum over it to get a working phone, then flashed Cog4.4.9 to get a bootloop....(but CW2.5 in the process) and then found your little gem on my EX SD Card and figured what the hell.....I never tried that one.

Very nice ROM.... Seems every bit as fast and smooth as the GB ROMs I tried. I think we are splitting hairs here between a well baked Froyo and buggy 2.3.3 source.

So why 2.2 and not 2.2.1?
[Captivate Android Development] bryman27:
Firefly is based on the Rogers official froyo which is 2.2, changing bases was discussed at one point, but it didn't happen.
[Captivate Android Development] deathgod1989:
so can i use the modems in this post?

http://xdaforums.com/showthread.php?t=876391

which one do i use the froyo one right? thanks! and how do i know whther my phone have a i9000 based kernel?
[Captivate Android Development] studacris:
Yes the froyo one.

You are on firefly, that has an I9000 kernel ... so unless you changed kernels go with an I9000 modem.
[Captivate Android Development] amace04:
Ok, Obvious noob question here, please forgive ;)

First ROM flash on an i896 Cappy. Was recommended from a Canadian board by others on Rogers Network, says it runs smooth as butter. Anyway,

I've flashed to stock, I've rooted. I've copied clockwork and the ROM to the SD card (yes, internal, not external)

On re-install packages, I get:

Install default apk-files, please wait

Install default apk-files, finished

-- Install from sdcard...

Finding update package...

Opening update package...

Verifying update package...

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted.

Any suggestions? Gotta be something pretty basic I'm missing here.
[Captivate Android Development] bryman27:
Are you sure you flashed to stock right? You should be on Eclair/Android 2.1. It sounds like you are on Froyo/Android 2.2, it's easiest to flash ROMs from 2.1. Here's what I use to flash to stock: http://xdaforums.com/showthread.php?t=731989
[Captivate Android Development] amace04:
I'm on Stock Rogers 2.2

I'll try 2.1
[Captivate Android Development] amace04:
Does it matter if I'm AT&T 2.1 vs. Rogers 2.1?
[Captivate Android Development] studacris:
Nope, you will soon be overwriting it anyway
[Captivate Android Development] bryman27:
Oh, I didn't notice you were Canadian. Rogers would be better, that way you don't get an AT&T splash screen on boot. Here's the stock Rogers thread: http://xdaforums.com/showthread.php?t=979133, be sure to read everything in the OP.
[Captivate Android Development] studacris:
Meh... A splash screen is replaceable http://xdaforums.com/showthread.php?t=944353

Make sure you scroll down to trusselo's post with the links ;)
[Captivate Android Development] amace04:
Well, too late now, Already got AT&T version going. Waiting on first boot now.
[Captivate Android Development] amace04:
Master clear started.. here's to something NOT a brick. I'll let you knwo how all goes.
[Captivate Android Development] amace04:
Got into CW, currently flashing the ROM, how long does it take normally?

Been at "Finding update package..." for about 6 mins now.
[Captivate Android Development] bryman27:
Try redownloading the rom

I'm going to sleep now, hopefully studacris will help you with any more problems of yours this evening.

Sent from my GT-I9000
[Captivate Android Development] amace04:
At what point should I assume it has hung?

Can I turn off at this point? All it says is it is finding update package, but has made no indication that any writing has happened yet.
[Captivate Android Development] amace04:
Is it safe to battery pull or turn off?

I'm assuming that process of finding update package should only take a few seconds right?
[Captivate Android Development] bryman27:
Correct, it should be safe to battery pull.

Sent from my GT-I9000
[Captivate Android Development] studacris:
Redownload pull the battery and try again.

there is nothing in the rom that could do any permanent damage...you could drop the battery mid progress worst case is a clay, odin again and start over. But you haven't done enough to even need to do that.
[Captivate Android Development] amace04:
Cool. Re-downloading now. Internet chose this point to slow right down, so will be a few mins, but thanks for the help thus far.
[Captivate Android Development] studacris:
Lol that's my "job"
[Captivate Android Development] amace04:
Ok, formatting now, fingers crossed.
[Captivate Android Development] ryanshapiro44:
im getting allot of delay and freezings going through screens and opening the app drawer. anything i can do?
[Captivate Android Development] markdexter:
I know that when I first rooted my Rogers cappy, I had to change the recovery image because it wouldn't recognise there update.zip file, something to do with the signature, I had to use Root explorer changeg the recovery in system/ bin, delete the original and replace it with new, not sure if that affects you, also, this ROM is a great choice if its your first time flashing a custom ROM, and buy the way you have one if the best helping you, studacris! got me out of a jam!

typed with big fat fingers
[Captivate Android Development] amace04:
Well, all seems to be good. ROM looks slick, didn't even need to put in APN setting or anything, figured it out on its own.. Good Captivate... *can be seen scratching phone under battery door*

Thanks for the help all.
[Captivate Android Development] amace04:
Only one issue I noticed, now, rather than going to bed for work in the morning, I'm gonna be up for a while tinkering around... Damn you new things!!

Although serious question, is there a way to get haptic feedback on the home/back/file/search buttons, or is that not available in this rom?
[Captivate Android Development] savvacon:
Second time around flashing the firefly Rom after playing around with some of the gb Roms and i have noticed one issue. My wifi stops working after about 10 minutes any thoughts on how to fix?
[Captivate Android Development] goodolsen:
Go to Settings\Sounds and check Haptic Feedback. You can also try changing the intensity setting.
[Captivate Android Development] FredOak3:
Did you go back to stock first (I'm assuming) and do the 3 clears before flashing (both Caches and a master).

I did the same as you tried GB's and then came back to FF and haven't noticed that issue.
[Captivate Android Development] amace04:
Thanks anyway, but I found it. just curious why it was off by default, but fortunately it was just a setting.
[Captivate Android Development] amace04:
Noticed by noon, after being unplugged since 8 the batter was down to 61%, that is unacceptable.

I'm currently charging it up and gonna try resetting the battery stats in CWM, hopefully something is just screwy there. If not, gonna have no choice but to find another ROM. This one looks pretty sharp though.
[Captivate Android Development] FlKTION:
I accidentally deleted my contacts.apk if someone could upload the apk that would be awesome as I don't have pc access atm

Thanks!
[Captivate Android Development] BWolf56:
If you have root explorer and the rom on your sd, you can simply pull it out from there.
[Captivate Android Development] eureb:
So, I have FF 3.0 and love it.

I looked at Mosaic, and while it looks cool, the steps for getting to a GB ROM seem awfully long. What're the advantages of going to GB from FF, besides the obvious "Hey look, I have GB!" and Netflix? is it a much faster OS?

I'm debating if I want to wait the month or 2 (well, it's hoping only going to take that long... haha) for GB to hit the states, or if I should take the jump now...
[Captivate Android Development] Barbarian:
Make the jump. All it takes is following simple instructions.
[Captivate Android Development] Emperor Jon:
I just flashed CM7 to my captivate..

A couple things I miss about Firefly were the keyboards.. The swype keyboard, and the mtm blackout keyboard.

I haven't been able to find the mtm blackout keyboard that i can actually flash to my phone..

I was wondering if anyone knew if there is any way I can port the keyboards from Firefly to the new rom. And if not, where I can find similar keyboards.

Any help would be greatly appreciated. :)
[Captivate Android Development] anishz:
Hail Emperor!!:D:p

You can try this link here

There are lots of color options and install instructions, hope this helps.

(I know its on vibrant forum but works on captivate as well, tested by me and i am using the mtm gb blue one)
[Captivate Android Development] Emperor Jon:
Yeah, I tried that, but when I try to install zip from SD using CWM it just says installation aborted.. I've checked system/app and there's nothing keyboard related in there :/

So I haven't had any luck getting it on. I was trying the MTM green, but I'll try flashing one of the others and see if it works..

Any thoughts on the swype used on Firefly? That one looked pretty neat, and worked really well.
[Captivate Android Development] anishz:
you can extract the swype.apk file from firefly rom in System/app and place it in your current rom's system/app
[Captivate Android Development] Emperor Jon:
No dice.. Does it have any relevance that Firefly is 2.2 and CM7 is 2.3.4?
[Captivate Android Development] zelendel:
It could. Alot of things that would normally work on Samsung based roms will not work on CM based roms. Your best bet is to ask in the CM7 thread as it may need to have a different version of Swype. As for the theme, You might have to edit the files yourself to get it to work.
[Captivate Android Development] themisfit:
holy jesus.

honestly, after coming from a evo, then to the captivate, and now having an inspire, i am holding off on using the insipire until a great rom like this one comes out. I would donate to hell and back to see this exact rom ported to an inspire
[Captivate Android Development] amace04:
I have noticed since installing my GPS accuracy has been no better than awful. At best it will be about 10 meters from my current location, sometimes as far as 100m. and it's not saying I'm within a 10m radius, it thinks it's being accurate. Trying the JM9 fix now, hopefully that fixes things.
[Captivate Android Development] BWolf56:
Try adam's gps fix. Was working like a charm for alot of us :)
[Captivate Android Development] capocaccia:
I thought this rom was the **** as well until I realized if your battery dies, you cant reboot without it going into a boot loop. Its happened to me about 5 times. I got fed up with it and went back to stock. So its a great rom, as long as you can make sure your battery never dies.
[Captivate Android Development] BWolf56:
Umm I always let my battery die and that never happened to me..

You might've had a bad flash or needed to clear you cache/dalvik. Also resetting your battery stats is always a good thing to do.

The rom has nothing to do with it :)
[Captivate Android Development] matase:
After trying most of the froyo roms, I can say this one gets the best battery life. I've been only using this rom for about a day but so far I haven't had any problems with it.

Can I use those other themes that are provided on the first page of this thread if I am using a touchwizGTG launcher?
[Captivate Android Development] markdexter:
I agree completely, this rom is one of the best, was on serendipity 7, having a couple of issues, came back to this, its just great
[Captivate Android Development] NightTickler:
Hi Everyone,

I am on FireFly 2.3 and I wish to upgrade to 3.0 but I have one question. I am also using SuckerPunch Voodoo #11 kernel and was wondering do I need to worry about this if I plan to use the FF app to incrementally upgrade? Do I need to re-flash another kernel before I attempt this?

Thanks in advance.
[Captivate Android Development] BWolf56:
The only thing you have to do is disable ext4 before flashing. Also you should probably flash full FF3.0 instead of just the update package.
[Captivate Android Development] Jwebbfuze:
Flashing Modems

I've been on FireFly for few weeks now. Love the Rom btw, runs smooth, good battery, and looks pretty. But I have had awful service in my area (Arizona on AT&T)

I wanted to try flashing a new modem from here

http://xdaforums.com/showthread.php?t=876391

But I've never toyed with modems so not sure where to start.

From what I read through this thread is to try, try, and try some more til you find one thats right but I'd love to hear anyone else's opinions on specific ones.

Also, if I read things right the Modem stock in this ROM is "I9000UGJK4 (Froyo)" from the list? Just in case I decide to cut my losses and switch back. :rolleyes:

Thanks for the help in advance.
[Captivate Android Development] BWolf56:
Sorry to say that we really can't say "Hey use this one" cause they act completly different on every phone and in every area. JK4 is a great base and works but as you noticed, not as great for everyone.

Your best bet is to try the most popular one and read on that thread to find something like "Hey I'm in Arizona and this X modem works perfect".
[Captivate Android Development] fuloplori:
+1 Couldn't have said it better, one thing to add is that u shoud stay away from kb1 in case u don't plan to flash a kb1 kernel so basicly try everything thats I9000.

Edit: I've tried that kb1 with the stock kernel combo long time ago and the result was impressive,most bars ever,'till I tried to get a lock on my gps thats when I ended up in endless restarts.Rookie mistake,lesson learned.
[Captivate Android Development] Jwebbfuze:
Thanks for the input! I went ahead and downloaded all the ones labeled I9000 and started flashing one by one, doing a couple of speed tests with the Speedtest.net app. before flashing the next one. My personal best results came from the I9000UGJK3. Since I know a lot more goes in to a modem then Up/Down speeds I'm going to start here for a few days and see how everything goes and try one of my other top speeds if I'm still not happy.

Is there any apps or ways to test the modems that would give me consistent results on the other variables?

Thanks again!
[Captivate Android Development] BWolf56:
Not that I know of. The only thing you can do is test call, text and check your reception with each. Also, some modem can take a bit to settle down (or even a couple reboot). Like I said, they all act differently on every phone so all you can do is test (like you seem have started already!).
[Captivate Android Development] NightTickler:
Oh okay. I am confused then as on the first post it says:

Quick Info:

If you flash the ROM, and it is taking really long to boot, don't worry, this is normal. It will only happen on the first boot. Subsequent boots will be lightning fast.

Only use the update package if you are on FireFly 2.9. If you are on an older version, please use the update package in incremental order from the FF app
​

So should I follow this advice or yours? I guess on the safe side I should just go back to stock and flash FF 3.0.

Thanks for your response.
[Captivate Android Development] BWolf56:
I'd suggest to flash full 2.8 and update 2.9 + update to 3.0

Might not be "needed" but that's what I did a couple months back and worked like a charm. Maybe going full 2.9 and updating to 3.0 will do it as well. Either, I'm sure it will work fine :)
[Captivate Android Development] studacris:
Damn. That seems like hella overkill.

Easier way would be to disable lagfix, flash 3.0 full, then flash suckerpunch voodoo (assuming you still want to use that)

easiest way would be to take the zImage from the updates folder of the kernel zip, throwing it in to the updates folder of FF full 3.0 fish that once. Done.

If you don't want to use suckerpunch anymore just flash the full 3.0.

No need to over complicate.
[Captivate Android Development] NightTickler:
Interesting so I can just go from FF 2.3 to 3.0? There is no harm in not flashing incrementally, even if you are on FF already? Wonder why the front page says to flash incrementally if you're not on 2.9.