yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] geokilla:
It's the infamous charge bug. Switch to the latest test version of Talon. It's supposed to eliminate the charge bug, along with many other features and fixes that make it better than Dark Core.
[Captivate Android Development] sl0v4k:
i know i may be asking for too much but if this fixes charge bug may i please receive the link please :D cause my phone charges just fine but sometimes the battery depletes within 8 hours and other times i get 2 days out of it. and i use it close to the same amount per day.
[Captivate Android Development] geokilla:
It's not that hard to find, regardless of whether you're using the XDA app or browsing on your browser at home. The thread literally gets bumped to the top every hour or two.
[Captivate Android Development] Kyuta Syuko:
I never see it leave the front page...
[Captivate Android Development] jewellsimon:
Thank you so much ( :

Sent from my Brain...
[Captivate Android Development] jewellsimon:
Omg you are the sweetest person I never met....

Thank you and get better soon...

Sent from my Brain...
[Captivate Android Development] kangi26:
Unfortunately, changing to Talon Kernel did not fix the charging issue. Loaded Talon's latest last night, woke to my phone at 40%, and not charging. I'm beginning to think there might be a issue with the physical connection
[Captivate Android Development] aalh:
the latest test release 0.4.4.20?
[Captivate Android Development] BWolf56:
Are you charging through pc usb port or with charger?

Also, highly doubt that Talon would fix the charging problem.. It came along with the GB port to our phone lol.

On a side note, those amazing colors in your sig makes me want to eat it... looks like candy!! lol
[Captivate Android Development] stevebic83:
I would have to agree with you... definitely sounds like a physical issue, I'd say 7 out of 10 times that's the reason. I have only experienced the charge issue a few times and it's so random, and I have so many different cables laying around from so many different phones that that is what I chalk it up to everytime. I just switch the cable and voila the issue is resolved. Could maybe even be the usb connection in the plug or pc if it gets hit or pulled a lot.
[Captivate Android Development] kangi26:
I generally charge with USB, but what I didn't know is the issue came with GB, thanks for the info on that. I won't be expecting a fix with a kernel change :)

On a side note, Num, num!
[Captivate Android Development] studacris:
Yeah I had that bug when I first hopped over to jvb from firefly, right when it was first ported, what I did to work around it was charge it full right before I went to bed then unplugged, the battery would only drain a little bit throughout the night and when I woke up I would plug it in and go shower make my coffee and let the dog out, when I came back it would be fully charged and ready to go.

I personally haven't had the bug since jvb...
[Captivate Android Development] gocats7:
Not sure if there is a relation but I only had the issue when I had wifi on at some point. After I started turning wifi off and rebooted before going on charge it went away. May have just been a fluke.
[Captivate Android Development] BWolf56:
I can't remember who it was but someone mentionned that he was only getting the charging bug with pc usb port. I guess try the wall charger?

Also saw somewhere that older charger didn't cause charging bug. Worthed a try if you have one laying around.
[Captivate Android Development] aalh:
I have also heard of pulling the battery for 10+min resetting what ever is off on the battery charging
[Captivate Android Development] jde984:
I finally figured out what was causing the charging bug! I only ever get it when people start discussing it on this thread (i unplugged to 75% a couple hours ago). Seriously... I don't get it a lot, but when I do it's the topic of the day on there.
[Captivate Android Development] stevebic83:
While I haven't figured out the problem with the charging bug... I finally had it happen to me today at work, was at F and dropped to 74% when unplugged, and this cable has NEVER given me issues.... I think maybe I have a step in the right direction due to some research... First off it appears that the issue resides in the bootloaders. After reading countless pages it looks like people on the I897 bootloaders DO NOT experience the problem, where those of us on the I9000's DO. So it must have something to do with the bootloaders.

Bootloaders are basically the devices instructions for booting up the OS and are particularly device specific due to the fact that it gets the hardware ready for the OS and every phone has different hardware. So while the I9000 hardware is very similar to the I897 hardware they are not the same, and I think this is where the issue arises...

There must be something not quite jiving in the hardware for the charging protocols/module... Is it possible to open the bootloader code to see what might be causing this, and if so, could we take the right code from the I897 bootloader and drop it into the I9000 boatloader?
[Captivate Android Development] stevebic83:
Still reading.... may also be a kernel issue, in which case it may be easier to resolve, while obviously the h/w and circuitry is there to facilitate the correct charging protocols, since it use to work, maybe the charging drivers in the kernel are wrong and slightly incompatible with our h/w... seems like we should be able to find the correct drivers and build it into the kernel... does anyone know what piece of hardware is responsible for charging and possibly the manufacturer? :confused:

Ok so here are some links to the I897 & I9000 charging ports:

I9000: http://www.globaldirectparts.com/Samsung-i9000-Charging-Port-p/smsng6087140.htm

I897: http://www.globaldirectparts.com/Samsung-SGH-i897-Charging-Port-p/smsng6086090.htm

just a starting point... still reading
[Captivate Android Development] stevebic83:
Ok it is the usb charging port switch and controller module/s that controls basically the on/off state of the charging port... does anyone know who makes the one in our cappy's? I would assume TI but maybe sumsung makes their own.
[Captivate Android Development] NunHugger:
I am just surprised to see that months after the bug was found, we are still talking about it :D
[Captivate Android Development] jde984:
Was it over when the Germans bombed Pearl Harbor?
[Captivate Android Development] stevebic83:
I never had the issue or maybe just didn't notice it till today, but now that I have my OCD won't let me let IT go! LOL! I've spent the last 3 hours researching it since, and I'm at work :eek:... currently I'm downloading the two bootloaders and will be running a camparison of the code between them. Hopefully it won't be to difficult to find, but if you or anyone else knows specifically where I should look it'll make my life a little easier, thanks for the great rom btw! :)
[Captivate Android Development] stevebic83:
BTW for anyone that hasn't read this... DO! Just found it and while it doesn't all pertain to us it has TON's of GREAT information and well formatted!

http://xdaforums.com/showthread.php?t=723596
[Captivate Android Development] stevebic83:
Alright hit a snag... can someone tell me how to open a .rfs and .lfs file to read or view?
[Captivate Android Development] sl0v4k:
just a little problem. sometimes when i put the phone in flight mode, it goes into flight mode but i cant get out of it. the "button" grays out and i cant click it. have to colpletely restart phone. its a nuisance lol.
[Captivate Android Development] rquiett:
Try adding the flight mode to your extended power menu and see if that works for you
[Captivate Android Development] sl0v4k:
already did that :D same problem :/ also if i could ask if google maps is safe to update yet or is the batt drain bug still present. aaaand lol when the phone starts up and i lock the screen when i go to use it again the lock screen is sometimes transparent. nothing bad just it flickers like crazy when i unlock it. lol sorry for all the questions but ive been away on business never had time to state these things :)
[Captivate Android Development] Kyuta Syuko:
Would just like to note that I'm on the I897 bootloaders and have has the charge bug a few times lately...
[Captivate Android Development] Madtowndave:
I have never seen much definitive in difference between i897 and i9000 GB bootloaders.

I've only intentionally flashed GB boot loaders once, so I remain on the i897...never tried i9000. Unless I see a real good reason for doing so, I'm not taking the risk of flashing boot loaders again.

TL:DR This boot loader side bar probably deserves it's own thread...but since it happens on most/all GB Cappy ROMs, this issue doesn't directly relate to MVI.
[Captivate Android Development] keller.jeff:
I only saw the charging bug once... I was on stock MV, flashed talon kernel, got the charge issue on first night. Flashed dc over it, still there, Re flashed MV and ita been gone ever since.

Has anyone with the bug constantly tried a fresh re flash?

Sent from my GT-I9000
[Captivate Android Development] robm1911:
I'll let you know tomorrow I just got back to MVI from 2.1
[Captivate Android Development] keller.jeff:
Fyi

Root explorer is 99c on Amazon app store. Down from 3.99!

http://www.amazon.com/gp/aw/d/B004SRWW0C/ref=redir_mdp_mobile/189-0165009-3599639?redirect=true&tag=gmgamzn-20

Sent from my GT-I9000
[Captivate Android Development] insane08:
flashing as im posting! comming from cm7 my battery was horrible...lets see how this runs ! :D

edit: Loving it so far...always been a fan of team phoenix work..it seems to be alittle laggy for me when i click the bottom buttons such as back..anybody know as to why ? i followed full instructions and everything went smoothly ...

time to go flash a themme !
[Captivate Android Development] blutruck:
Some have found that if you disable lagfix it will run smoother. Try it, maybe you will be one that it will work. Also some have flashed Darky 3.0 kernel.
[Captivate Android Development] gokartracer5:
I moved to the Darky 3.0 kernel a couple days ago and it seems pretty stable to me. I had the lagfix on while switching. Not getting the charging bug other folks are talking about. I did clear the caches after and re-calibrated the battery, so that may have helped.
[Captivate Android Development] Delicate Donut:
ok quick question here. I am currently on stock gingerbread via the instructions on the OP, however I cannot seem to get into recovery. I used the vol up plus power releasing the power when the screen turns on, and also using adb all to no avail. Any suggestions will be greatly appreciated the faster I flash this rom the better

edit: it appears the phone is now stuck at the boot screen :( I can still get into download mode though
[Captivate Android Development] jde984:
Did you flash Xcal's reorientated kernel?
[Captivate Android Development] Delicate Donut:
yes through odin
[Captivate Android Development] Delicate Donut:
So I got it to work and have mosaic installed. Works flawlessly I'm impressed! Smoother than the rom on my charge! One little thing though the ota app doesn't seem to want to install. It says to update and when I try to install it it says not installed. Any idea why? Sorry if these questions have been asked before but I've been away for to long as I now own a droid charge. Thanks
[Captivate Android Development] aalh:
use root explorer or similar to copy the apk to /system/app replacing the old one and reboot
[Captivate Android Development] Delicate Donut:
I feel like an idiot now as I didn't think of that! I was about to adb lmao
[Captivate Android Development] JoeDV:
Did it not download as a zip file? I don't remember which version was included with MVI but the later version have the download as a flashable zip. Just curious since there have been several posts about attempting to install it from the apk.
[Captivate Android Development] Delicate Donut:
Not the first update the second one was a flashable zip however. Were all the battery mods made using the uot kitchen?
[Captivate Android Development] stevebic83:
Can anyone else verify if they have the charge bug and are on the I897 bootloaders?

Also, can anyone verify if switching to a new kernel solved the bug for them? and which kernel.

The issue appears to be in one of these two places...

Not to hi-jack the thread, as I saw the post suggesting a new thread, but I take the comments of the folks here in a higher regard than in other threads, and since we have such an awesome rom with few issues, ergo posts, I hope the dev's don't mind... let me know if you do though and I'll gladly post a new thread. :D
[Captivate Android Development] stevebic83:
This is why we CAN use the I9000 bootloaders, because there isn't much difference between the two.
[Captivate Android Development] stevebic83:
Interesting... there may be some kinda of kernel 'dance' we can do, similar to the modem 'dance', that may fix the issue for us... I will try to reproduce this tonight when I get home.
[Captivate Android Development] TheSoaresan:
Hmm the last few talons fixed the charge bug (gives accurate battery reading)...
[Captivate Android Development] BWolf56:
Not so true.. Kangi tried it and it didn't fix his charging problem.

I think latest Talon only fixed part of the problem which doesn't work for everyone.
[Captivate Android Development] metlmangreg:
I am sure most people know this, but for those who don't, if after charging to full with the phone on, you turn it off and allow it to charge to 100% while off, it will show 100% when you restart your phone and drop normally, this has worked for me since 2.2.;)
[Captivate Android Development] BWolf56:
That's bump charging, you usually only do that after resetting battery stats as it's hard on your battery life.
[Captivate Android Development] metlmangreg:
yeah, thanks Wolf I don't do it regularly, maybe a week or two in between, and I have only had it drop drastically once, so not really any need.
[Captivate Android Development] kangi26:
That's true, I'm on Talon 4.4, AND I charged on wall outlet, not USB last night and just before I hit the hay, noticed I was at 74%. When I plugged in I was at 82%.

I unplugged, plugged back in and charging went fine.

I have not changed boot loaders

Sent from a autonomous device
[Captivate Android Development] Delicate Donut:
This rom rocks! wish we had this on the charge :(
[Captivate Android Development] stevebic83:
Well I got it fixed on my phone just did a battery calibration a few times and it fixed the issue haven't been able to reproduce the it since so I guess I'll just let it go at that :D
[Captivate Android Development] ChikiBujia:
Themes Updates

Hey guys!!!

Please check the themes thread for some updates :D
[Captivate Android Development] ChikiBujia:
Battery

Wow!!! There has been a lot of talk about the known battery bug!!!!!

Well, this has been happening since the first GB version, and the way I fix it is that, after I flash the ROM, I calibrate my battery (even if I flash at 100%). I let my phone charge all the way to 100% and then turn it off (yes, I have to bump charge it until it hits 100 and stay there). Plug it back in while it is off and leave it until it hits 100%. Reboot in recovery and delete the Batt stats (which are in the advance menu of the CWM recovery menu). Turn the phone on and leave it plugged in until it says it is full again.

After doing this, my phone always stays at 100 after unplugging it.

Also, you can delete Batt Stats using SGS tools too :D
[Captivate Android Development] cliftomr1082:
Filling better I see, welcome back. Or you may have never went anywhere!
[Captivate Android Development] cliftomr1082:
So Chiki, is In Call only good for Candy Theme.
[Captivate Android Development] ChikiBujia:
No, you can use it with any theme or with Stock MVI, but since it has the Candy Real colors, that is why it is geared towards that theme :)

I am feeling a lot better :D Thanks!!! :)

Sent From My Mosaic Powered-Up Cappy, Using My Paul Diddy Remix XDA App
[Captivate Android Development] WillyWonka23:
International swype keyboard?
[Captivate Android Development] stevebic83:
This is basically what I did, minus the bump charge, I charged to 100% unplug phone, reboot to recovery (CWM) wipe batt stats, reboot, plug phone back in during reboot, then repeat until it shows 100% on boot up. Seems to have fixed it for me.

As far as the research goes, I believe the issue is in the kernel, after thinking long and hard about the bootloaders, I decided the binary code between the two controllers was probably identical, at least at boot; bootloaders only really affect the phone during boot (duh!). The kernel is where the drivers are located and thus should be where the issue would arise. I'll keep looking in my spare time, but it is fixed for me for now.
[Captivate Android Development] 305Freak:
Just an FYI, as per my request, fecito (the darkcore kernel dev) is looking into adding the code necessary to the kernel which will allow it to route audio via the car dock. He's asked Xcal for the code required and it was promptly provided. Hopefully it all works out. Stay tuned.....
[Captivate Android Development] geokilla:
Can you link or provide an explanation to what car dock does? I tried searching on google before but not on XDA. didn't find anything on Google.

Sent from my Samsung i896
[Captivate Android Development] djbrian52:
OK devs...I'm in the wrong forum for this, but I do have a Cappy running this ROM and it's amazing. I also ran the Ninja on my Inspire b4 getting the Infuse. So for my question. Could a Cappy themed dialer work on the Infuse? You can pm me so as not to clutter up the thread. Thanks guys. I'm a Team Phoenix fan for life.

Sent from my gtg465x-ified Infuse!
[Captivate Android Development] 305Freak:
It's for those of us who bought the Samsung car dock that goes with the Captivate.
[Captivate Android Development] brandon_L:
I'm currently running Serendipity VII, so i have the gingerbread bootloaders. Which xcal kernal do I need before flashing Mosaic VI?
[Captivate Android Development] studacris:
You don't need an xcal kernel...if you're already on gingerbread just flash the rom in recovery.
[Captivate Android Development] brandon_L:
Thanks! :)
[Captivate Android Development] killinjoke:
So I flashed this rom and I haven't been able to get my external sd to work. Any suggestions?
[Captivate Android Development] Kyuta Syuko:
Sounds like a bad flash to me... Think someone else had the same issue and a reflash fixed it for them though I could be wrong...
[Captivate Android Development] killinjoke:
Thanks I will flash again when I get home. Makes sense too since I still had a bunch of old folders when I went back to stock and MC.
[Captivate Android Development] TheSoaresan:
Hey guys...I was wondering if a kind soul would be able to make bln on texts, missed calls, etc to work and/or light on touch. If not, could I get assisstance on how to do it myself? I know there was a zip that came out on MV for bln but it didn't work for me when I tried it out
[Captivate Android Development] jamezz23:
I'm kind of stuck right now. My phone was running super slow so I was going to do a reflash of the rom to hopefully get it back up to speed and I'm having a few issues. First is somehow I must have deleted the Mosiac VI rom so I cant reflash in recovery. and I'm also in bootloop for some odd reason now, after doing a factory reset and clearing both caches. I just neeed a refresher on how to flash the rom in download mode using odin. any help would be awesome!
[Captivate Android Development] ChikiBujia:
You could download MosaicVI in your computer, and then plug your phone and mount the sd card in recovery (there is an option for this), and just transfer Mosaic VI from your computer to your phone.

Unmount and flash :D
[Captivate Android Development] jamezz23:
Thank you for that tip :D

Works now
[Captivate Android Development] Seanbest:
*#*#4636#*#* is supposed to bring up usage statistics which is does, but it doesn't allow me to see anything about data usage. Everything I could find on this code was from mid 2010 so I'm guessing it was all on Froyo. Anything like this work and show data usage by app on gingerbread?
[Captivate Android Development] Mortem Tuam:
don't mean to hijack the thread Mosaic devs :cool:

just wanted to share my latest wall for your great ROM!

enjoy folks and you know where to find me....if you don't check my siggy ;)
[Captivate Android Development] robm1911:
Love it!!!!!

But shouldnt it be a unicorn
[Captivate Android Development] Mortem Tuam:
probably but I liked this horse. :)
[Captivate Android Development] fishfingers15:
I'm on 1.8.12 o MIUI Cyanogen mod.

I had Phoenix raising (Froyo) and I liked it very much, but when I tried to switch to Gingerbread, I had bricked my phone and got a replacement from AT and T :D

I read through the thread and I really like Mosaic VI. I'm reasonably pleased with MIUI and it's fast, but I'm unable to decide if I should take the plunge. Another thing, ODIN doesn't recognize my phone anymore (although if I turned on the USB Storage, I can see my internal SD card)

Can I root to Mosaic VI from MIUI without going to stock?

And, how is Mosaic VI generally? Should I switch or should I wait for next lease?
[Captivate Android Development] Kyuta Syuko:
Just photoshop a Unihorn on it
[Captivate Android Development] aalh:
nice work

+1 on the Unicorn

and there is a Theme thread for this

Mosaic Theme Thread
[Captivate Android Development] ChikiBujia:
Double check this, but I am fairly certain that Miui is a complete different system, and you definitely have to flash stock gingerbread and the gingerbread bootloaders via Odin before flashing any regular gingerbread ROM :(

Have you tried another port in your computer to mount your phone to Odin? or another cable? This has work for some people in the past.
[Captivate Android Development] fishfingers15:
Ah shucks. I have tried everything. Different cables, different connectors as well. Each time, when I turn USB storage on, I can see my internal SD Card too. However, ODIN doesn't recognize my phone and I get the 'Unknown Device connected' in the Device Manager.

Is there a way I can go back to a stock gingerbread ROM without having to use ODIN? I have clockwork mod recovery, I'm fairly certain that I can do a 3 button recovery and boot with a CWM, and choose a zip from my internal memory :(
[Captivate Android Development] ChikiBujia:
I am sorry but someone else is gonna have to jump in here :( I only know how to work with Odin :(

Since it is saying that your device is not recognized, I would suggest maybe trying to reinstall the samsung drivers in your computer, and see if that helps.

Also, I honestly have no knowledge on Miui ROMs at all, but maybe, if it is also based on the i9000 version of gingerbread, try installing the i9000 drivers instead of the i897, and see if the computer recognizes the phone that way.

I really hope this helps, or that someone more knowledgeable can come and help you :o
[Captivate Android Development] fishfingers15:
Thanks anyway, I'll try the drivers again and try a different machine as well. Will also keep a watch for any replies here.
[Captivate Android Development] willzane:
Are you putting your phone in download mode? Its been awhile but I think that's your problem.

Sent from my mpx 200
[Captivate Android Development] robm1911:
It also sounds like odin is not seeing your phone when its on. yes you need to be in DL mode on your phone to flash to stock. but also for odin to see your phone when its on be sure usb debuging is on. menu/settings/applications/development you can do a master reset in odin from there. (if you need to)