yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Themes and Apps] eurosport360:
Hey guys,

A very, very cool boot animation:

http://www.youtube.com/watch?v=EF_vfEs6Jok&feature=related

If someone could port this boot animation to the Atrix, or at least lead me to a download that would work on an Atrix/how to install (either through CWM as a zip or place in root using root explorer), that would be wonderful :):):):).

Or, if someone could make or lead me to a boot animation that has bios-like text scrolling up and down with something going on (like in that video), it would be much appreciated.

Thank you so much!!!!!!!
[Atrix 4G Themes and Apps] shady_lanem:
Here's the bootanimation. Install with cwm :)

http://www.mediafire.com/?uqlfoibwl7msvvh
[Samsung Infuse 4G] Entropy512:
OK, as most of you are well aware, I've been doing a lot of poking at our battery charger/power management chipset. (The MAX8998 basically does everything in the case of our device...) This was in response to frequent complaints about slow battery charging and batteries dropping when running Navigation at full brightness on a car dock.

What I've been able to figure out so far:

1) Our stock charge current limit is 600 mA, same as the Captivate and I'm fairly certain the i9000

2) Our battery is slightly larger (1750 mAh) than the Captivate's (1500 mAh).

3) At least on our devices, CPU/screen/etc. usage count against the charge current limit. So the amount going into the battery is 600 mA MINUS whatever the phone is using to operate. This becomes a negative amount with navigation at full brightness.

Lots of Captivate users indicate that their batteries charged MUCH faster than the Infuse.

1) and 2) alone would only cause a small difference between our device and the Captivate - our device has the same charge current limit and the battery is only slightly larger.

3) can make a huge difference, especially if the Captivate doesn't count usage against the charge current limit at all. So the question is, which of the following is the behavior of the Captivate?

a) CPU/screen/etc usage don't count against charge current at all

b) They count against charge current, but the slower CPU and smaller screen mean there's less current counting against us.

So, I'm asking for help from Captivate/i9000 users to run some tests for me. What I need you to have:

1) A Captivate or i9000

2) A kernel that supports the CurrentWidget app from the market. It needs to report 0 mA when off of a charger, and a positive number when on the charger. If it reports "no data", you need a different kernel. I know that for a while MikeyMike01 was running an MIUI/CyanogenMod kernel that was missing the required support. If you get "no data", point me to some other kernels that have source posted on github (please, no kernels with only tarball sources) you can try and I'll look to see if CurrentWidget is supported in them.

Once you've got the above, plug the phone into a charger when the phone is reasonably discharged (below 70-80%, and more specifically make sure battery voltage doesn't rise above 4.05-4.10 volts when you check charge current.) Report the current in mA indicated by CurrentWidget here and I'll provide more instructions based on those results. Please report whether you had the phone connected via a wall charger or via USB - it DOES make a difference.
[Samsung Infuse 4G] welchertc:
I came from a captivate, my dad is using it now, when I get home I can check it out..gimme an hour or so

I don't know if his rom supports current widget though. I think the last one I installed for him was mosaic v. If it is supported it shouldn't be a problem at all.
[Samsung Infuse 4G] welchertc:
Bummer, the rom he is on doesn't support it. I don't really want to change stuff up for him, so somebody else will have to chime in. Sorry. I know that there are plenty if people on here though that have switched from a captivate, so somebody should be able to help you out. Either that or go make a thread in the captivate forum to have somebody help you out there; they're pretty friendly over there so that shouldn't be an issue. I know that different chargers make a difference, so maybe tell them to make sure and use the oem samsung wall charger.

On a side note, I'm running infused 2.0.4 and current widget is saying I'm charging at 1115-1117 mA with the oem samsung wall charger. Hmmm. I am at like 6% battery though, don't know if that means anything.
[Samsung Infuse 4G] TheChefSLC:
I have my captivate standing by at home. I will be there in around 2 hrs and can install any rom you like on it. Im currently stock KF1
[Samsung Infuse 4G] 00mred00:
just waiting on my battery to die
[Samsung Infuse 4G] Entropy512:
This is why I wanted information from a partially discharged battery - During the constant-current phase (from very low up to around 90% or so), our phones and the Captivate are limited to 600 mA. However all of the ADCs have a scaling factor that is different from phone to phone. Ours is 1.83 times reality, Epic 4G is apparently something like reality divided by 2.2.

So I need to find out what the Cappy is.

I'll poke around to see what's available. I'm not super-familiar with what ROMs are available - but with a link to kernel source I can determine if a kernel is likely to support CurrentWidget. Of course it's ideal if a few people have phones that support it already.

Doesn't need to be dead, just needs to be low enough to get a good scale factor for CW (see above). Once we've figured out the right correction factor the region I'm looking in is the constant-voltage phase near the end of charging (starts around 90%ish). This is where voltage is held constant at nearly 4.2 volts and the current starts dropping.

In our phones, if you turn the screen on for a bit or run StabilityTest for a few minutes, the charge current goes up significantly (since CPU/screen usage count against charge current limit). So the CurrentWidget graph if you're logging with CW looks "spiky". Ideally it should look smooth - so I'm wondering if the Captivate is smooth, or just "spiking less" due to smaller screen/slower CPU.
[Samsung Infuse 4G] 00mred00:
Using infused 2.04 and bedwa's gb kernel.

1102-1115 ma

It started at 3.66 volts and went to 3.96 volts
[Samsung Infuse 4G] Entropy512:
I've got a fair amount of data on the Infuse itself - I'm looking for Captivate (and maybe i9000) data for comparison.

Those are about what I'd expect for an Infuse. If you set CurrentWidget to divide by 1.83 you should see it report 600 mA until voltage hits around 4.18 volts. Voltage will initially rise rapidly right after you connect the charger, then rise more slowly up to 4.18 or so. At 4.18, current will start dropping. On the Infuse it drops but with "spikes".

I'm curious if the Captivate also has "spikes" in this phase or not.
[Samsung Infuse 4G] b-eock:
I didnt know that 1.6 Ghz is slower than the infuse? Maybe i pushed mine a little more but my phones faster :p

Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
[Samsung Infuse 4G] Entropy512:
Stock is 1...

However if it charges when cranked to full speed with the screen on, that would be interesting. I would LOVE for some CurrentWidget tests if CW is working for you.
[Samsung Infuse 4G] b-eock:
I does, but only for a bit, then it wont charge for a bit...

Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
[Samsung Infuse 4G] 00mred00:
Driving....car charger....nav and pandora running

871 ma 3.728 vlts

Sorry...see now you are looking for captivate info
[Samsung Infuse 4G] Entropy512:
That's interesting...

Does CurrentWidget work for you?

"Plain KF1" - does that include stock kernel?

Forgive me - I'm only mildly familiar with the Captivate, just that there are LOTS of reports from others it charges significantly faster than the Infuse, so I'm trying to figure out why.
[Samsung Infuse 4G] b-eock:
Yahh stock kernel, for now. Was on MIUI a few days ago at 1.6 GHz stable(im a speed and flashing junkie) and i havent tried the widget

Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
[Samsung Infuse 4G] Entropy512:
Heh. Your car charger is either being detected as USB or it's browning out (not enough current capacity). Probably USB - 871 mA becomes 475 when you divide it by the 1.83 scale factor, and that's EXACTLY what the current limit when on a USB charger is. In CurrentWidget settings, it's "Operation on Value", "Operation Type" is Divide, and "Operation Value" is 1.83 for the Infuse.

The correct settings for the Captivate are unknown. That's what the initial test (reported current on AC when reasonably discharged) is for.
[Samsung Infuse 4G] 00mred00:
Makes sense....my car charger is usb>into a usb car adaptor

Made the changes to /1.83
[Samsung Infuse 4G] araemo:
That saddens me. I was thinking about adding a USB port to my dash area to allow me to more easily keep my infuse plugged in with the car dock(the cigarette adapter blocks one of only two cupholders). If I can't use USB to charge enough, I'm screwed. ;P
[Samsung Infuse 4G] Entropy512:
There's a bit of confusion here. There is a REAL USB port, there are dumb chargers that are detected as USB ports, and there are dumb chargers that are properly detected as dumb chargers. Physically, they all look exactly the same. Electrically they are different.

Real USB port - An actual USB host

Dumb charger accidentally detected as USB - who knows. The resistors that iDevices use to indicate "dumb charger" are nonstandard and frequently cause this. iPad/iPhone/iPod chargers are detected as normal USB ports by the Infuse.

Dumb charger detected as a dumb charger - In the case of our Infuse, these have USB D+ and D- shorted together. You can either fix this with a solder blob in the charger, or a cable that shorts D+ and D- for you, like AT&T's dedicated "charge only" cable.

Still looking for someone with working CurrentWidget on a Captivate or i9000...
[Samsung Infuse 4G] araemo:
Why does this seem like a recipe for trouble to me? If a simple cable can cause the phone to attempt to draw over-spec, I'd imagine seeing lots of fried usb ports and simple usb chargers. (That said, we're only drawing 600mA normally? That's only 20% over spec, so they can probably handle it.)

Interesting stuff.. didn't know that the extra-power usb power ports had that simple a standard.. I had gotten the impression that there was real negotiation going on, to figure out what they're rated at. (Since they originally said up to 1A I think, but then decided they needed a way to let some devices safely draw more).

And, consider this a bump. ;P

I think a buddy of mine has a captivate, so I may be able to get you some info in a week or two if you haven't gotten it by then.
[Samsung Infuse 4G] clown_luv:
Entropy see if Andromeda 3.0 running Ursa minor kernel will do please I can test a cappy on that rom and kernel.
[Samsung Infuse 4G] Entropy512:
Does your current ROM and kernel not work?

Edit: Try your current ROM/kernel. If that doesn't work, try the above - There's a reasonable chance it'll work. If not, I think it will be easy to add CurrentWidget support - that kernel comes from AdamOutler's team so I can contact him about a rebuild and enabling CW support is a matter of a single #define.
[Samsung Infuse 4G] clown_luv:
Entropy its my employees phone and that's its current Tom and kernel ill try what do I do just leave the screen and run that widget???
[Samsung Infuse 4G] Entropy512:
Run the widget, look initially to see if it says "No Data" or not. If it reports 0 mA when unplugged, plug it into the charger and tell me what current it reports when it's below 80-85% battery. (More specifically, what current it reports when it's reporting battery voltage of 4.1 volts or less.)
[Samsung Infuse 4G] clown_luv:
Entropy it says no data
[Samsung Infuse 4G] Entropy512:
I'll try to talk to AdamOutler about getting a fixed up kernel to you. That ROM is from his team. Or maybe he can run the tests for me.
[Samsung Infuse 4G] TheNetwork:
855-860mA ............ Infusion kernel 2
[Samsung Infuse 4G] Entropy512:
That's USB charging on an Infuse.

I'm primarily looking for Captivate/i9000 data at this point.

I was out all night so I couldn't catch up with Adam. I'll prolly try PMing him tomorrow, this sort of thing is right up his alley.
[Samsung Infuse 4G] clown_luv:
Yeah i tried to update to cog 5.2 but I can't seem to mod the recovery for it so I can't install cwm
[Samsung Infuse 4G] mv1luv:
Wish i could find and external battery charger with an output higher than 350ma. I have a spare battery charger ordered off ebay.takes forever to charge. I have current widget also. No matter how strong the usb charger is max ma is around 600ma according to current widget with the operation set to divide at 1.83. i do have a captivate and an infuse let me see if i can borrow the cappy to test its.my wifes so i have a 50% shot.

Sent from my SAMSUNG-SGH-I997 using MeNtal TelePaThy
[Samsung Infuse 4G] Entropy512:
I've seen plenty of AC chargers rated 1A - pretty much any HTC charger. The Samsung one is rated 700 mA and that's enough for this test.

So you own a Captivate? Are you going to be collecting some data for me? Otherwise keep such discussion in General, Accessories, or Q&A please.
[Samsung Infuse 4G] xijar:
I don't have an infuse but I have a captivate. Widget seems to function properly so waiting for battery to discharge. Will report back with results.

Also you might want to try posting tthis in the captivate or i9000 forums. and maybe a list of supported rom/kernels for the widget in the op

Sent from my i897 running Apex9.1 with TalonDev kernel.
[Samsung Infuse 4G] Entropy512:
You just confirmed the first working kernel for me. Ursa Minor is missing the support needed, I was going to actually fix it and compile myself then send to Adam to test, but I REALLY prefer not to compile kernels and send them without testing.

You don't need the battery discharged too much - When down in the mid-low 80s you should be able to hit full current without hitting the voltage cap.

I'm considering going to the i9000/Captivate forums, but I feel weird asking in their development section for something that primarily benefits Infuse users - although I could help some kernel devs get CW support working I guess.

I mentioned this process earlier, but to repeat it for simplicity:

When the battery is in the mid-low 80s or lower, do the following:

1) Put the phone on an AC charger and wait for CW to update 2-3 times. Check to make sure voltage when on charger is below 4.15 volts, and that the reported current by CW is not fluctuating too much. Record the current as A

2) Put the phone on a PC's USB port and wait for CW to update 2-3 times. Record this current as B

3) Figure out what number you have to multiply or divide A and B by such that A is scaled to 600 mA and B is scaled to 475 mA. On the Infuse, A/B must be divided by 1.83 to get the true current.

4) Input this scale factor into CurrentWidget in the "Operation on Value" settings

5) Set CurrentWidget to update every 10 seconds and log to a file. Clear the log and then start charging the phone on AC. Leave the screen off but periodically turn it on and check it. What you should see is that when you hit the 90s in terms of battery percentage, the voltage holds steady at 4.18-4.2 volts and the current starts dropping.

The key I'm looking for here is: In this phase where current starts dropping, if you turn on the screen and do something with the phone briefly, does the current curve "spike" up or does it stay smooth?
[Samsung Infuse 4G] b-eock:
Hey were all nice over here :D just post in the Q&A part, not development, DEVs check there all the time! So you should get answers quickly!

Sent from my stock 2.3.4 AT&T Captivate!
[Samsung Infuse 4G] xijar:
Well im dumb. I saw voltages being read accurately and assumed it was all working. Wont pick up charge current though. Im gonna fflash all kinds of kernels/roms until I get this working lol.

Also you can send me untested kernels. Wont scare me too much got easy access to repair.

On another note, has anyone tried a stock rom? although it seems not many people are trying lol.

UPDATE: Stock JF6 Rooted. Working perfectly with widget. Currently charging with periodic use and logging currents. I'll post the log file once im done. Also im doing this test by USB and will do another by wall charger

Got called into work so my testing is a little wierd. Started on usb. Went to car charger then to usb then to car charger. Seems i got above 4.10V while charging below %70. Wierd. At any rate charging so far is untouched asleep or in heavy use(played dungeon defenders for about 20min on usb charger. )

I plan to do a more controlled test when i get home. Here is the logfile for my crazy on the move test:

http://db.tt/sxxQo7l

Sent from my i897 running Apex9.1 with TalonDev kernel.
[Networking] jjpp23:
Anyone get lucky or know someone who is beta testing Android network toolkit ? ? can't wait to play with that new toy ! ! :-)
[Networking] Zreo:
i'm waiting for the same..hehe..i missed DefCon this year and i think thats the only way you get the beta invite...
[Networking] chizzy58:
following this :)
[Networking] Jaredsburrows:
PLEASE

someone please post a link lol. i live too far away to attend defcon or most certainly would have.
[Networking] androidman1234:
Release date?

Does anyone know when is "ANTI" going to be released?:confused:
[Networking] termleech:
I actually hope they make it a hard install

That way only people who should have it installed will install it and we wont have a bunch of script kiddies running around. Too much of that already.

Tapped from my CherryPi Atrix
[Networking] strtkempo:
Keep this thread alive if anyone has the beta let us know copy extract and upload for us there are a lot of people on other forums within xda that want this app I can provide instructions on how to get it to us if someone has it!
[Networking] Milhouse82:
Seriously.... Still no released?
[Networking] sheep_duck:
its been like over a week since there have been any updates from the developers twitter :/
[Networking] chrisjz:
No kidding. What's taking them so long?
[Networking] chrisjz:
Pre-release sign-ups are open again! Hopefully someone here gets it.

http://zimperium.com/Android_Network_Toolkit.html
[Networking] MeWarning:
Here it is:

I think this should work
[Networking] basily:
Can anyone confirm if this is legit?
[Networking] dadyal:
Download it at

http://www.emoiz.com/download-android-network-toolkit-app-for-android
[Networking] dinips:
# Arrow # Android network toolkit #beta!

Will this support Android 2.1version handsets...?
[Nook Color General] sidenine:
Better than the Overstock deal. Buy.com has it for $169 ($179 - $10 instant savings) with free shipping, for a refurbished unit. Sold by Barnes and Noble, so 1 year warranty, new box, and 90 days of phone support. Grab it while it's still available!

http://www.buy.com/prod/nook-color-.../q/loc/111/listingid/140072914/221376447.html
[Nook Color General] gallymimus:
Wow great deal!

Thanks! I will get one!
[General Topics] jciota73:
I am pretty experienced with flashing roms. I am a fan of Gruesome Wolfs EVO 3d port and want to post on his thread...How? It says i cant
[General Topics] Kiboe:
need atleast 10 posts.
[General Topics] milad2002boy:
don't you think that it's not good rules? i think it raise up junk post in general discussion ...
[General Topics] dmeadows013:
It's to stop the new users from posting their questions in the development sections. 10 posts are very easy to get. Just help people in the Q&A section/Post cool things in General/Put themes in the themes section. Or, check out the off topic thread and chat about sports. Good luck and welcome to XDA.
[General Questions and Answers] Kiboe:
read somewhere, even stated in the motorola thread. so, carriers can't legally recognise older phone anymore, because of them not having the emergincy 911?

i mean it is a valid reason, was just wondering.
[Verizon Droid Charge] xdadevnube:
Not sure if this is ROM specific, so I am unsure whether to post in General or on the Gummycharged 1.91 thread...

I would like to get the old Market working on Gummycharged 1.91.

I was able to get the old Android Market 2.2.6 using Gummycharged 1.85. Market Updater even updated to version 3.0.xx, which I uninstalled, and was able to get Market 2.2.6 working even after I as auto-updated.

Now I'm on Gummycharged 1.91 and I cannot get 2.x.x working. I've tried 2.2.6, 2.3.2, and 2.3.6. They all install and work after clearing data and a restart, BUT they always FC when selecting an app in the Market.

Any suggestions?

*edited out my Market 3.0.xx bashing...*
[Verizon Droid Charge] rmanaka:
Have you tried Menu>Settings>Applications>Manage Applications, select ALL, scroll to Market and tap, choose "Clear data"? That's worked for some...

HTH
[Verizon Droid Charge] nitroglycerine33:
I bet you have an update installed. Check out data/app. If you go to your applications in settings you might see it there as well. Not sure if it will show up when the old version is installed.
[Verizon Droid Charge] xdadevnube:
Yes, I tried that multiple times. I had to do it on Gummy1.85 in order for the market to work at all. A restart was also required. Gummy1.85, as I recall, came with Market 2.2.6, so it is known to work with the older Markets. Unfortunately, Market 3.0.xx comes with Gummy 1.90 and 1.91.

I tried removing the com.android.vending.apk, as well as vending.apk (depending on Market version is installed) as well as clearing data. I also pulled the com.market.vending folder from /data/data as well. I also tried Titanium Backup recovery uninstall option, which would just hang on the "android with exclamation" icon during startup. Same issue, after clear data and restart market FC when selecting an app. I tried factory reset, clear cache, clear delvik cache, fix permissions to no avail. I reflashed Gummy 1.91, removed Android Market via Titanium Backup normal uninstall method, cleared data, cache, delvik, permissions, etc.

I am starting to think that this is a ROM-related issue.

I also tried various combinations of deleting android.com.vending.apk, vending.apk, uninstallting via Titanium backup, removing android.com.vending folder from /data/data with Root Explorer, restarting, clearing data, fix permisisons, clear delvik cache, reflashing ROM, and general cursing the new Market.

As for actually finding and comparing apps, I think I'll just use website (I really wish I could filter out the games from an app search, I get dozens of "space" games when I'm searching for astronomy apps, for example.)

I also uninstalled the updates via "manage applications" in settings. This worked on Gummy 1.85 which had the old market. Uninstalling the Market update only rolls back to 3.0.26 or whatever when on Gummy 1.85.

Thanks for the responses, though!
[T-Mobile myTouch 4G Slide] 936mane:
Is there a way to make the icons on the notification bar change to look like the icons on the stock android on the mytouch 4G without rooting it?
[T-Mobile myTouch 4G Slide] unclespoon:
No, since it requires writing new files to the system which can only be done with root