yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Accessories] avetny:
......................
[Galaxy S III Accessories] be1ieve1111:
no way.
[Galaxy S III Accessories] 10076757:
those are a bag of ****. no point wasting your money. they get so hot like after 10mins. dont bother
[Galaxy S III Accessories] papi92:
Mine is running very well. No heat issues. Worth the $11 it cost me. I get about 10% more battery life than with stock. I looked under gold wrapping and it is ranked at 2850 mAh.
[Galaxy S III Accessories] SlimJ87D:
Bs.
[Galaxy S III Accessories] papi92:
Pics to come.
[Galaxy S III Accessories] bidboy:
Made in Japan & sold from China. :D
[Galaxy S III Accessories] kaoztheory:
Need a full review on the battery.. Got pics?

Thanks!
[Galaxy S III Accessories] exekewtable:
If you are shopping around for batteries, you may as well go the whole hog:

4300 mah with Extra battery cover is available on alibaba. I wonder if thats a ticking timebomb for exploding batteries or not....
[Galaxy S III Accessories] papi92:
Sorry no pics as SIII is my only phone. It fits in stock battery cover. Im getting 3:45 of display time on ATT LTE. The battery does get warm but not so much that it is dangerous. Charging takes longer than stock as expected. I would recommended this battery. I dont really know what else to say im not a pro in batteries really but on stock battery i got 3 hours of display time.
[Galaxy S III Accessories] Product F(RED):
Japanese battery...from China?
[Galaxy S III Accessories] papi92:
Lol i guess
[Galaxy S III Accessories] joshnichols189:
That's depressing. I got 6 hours and forty minutes yesterday.

There's no way to fit more mah into the same size battery for so cheap. If there was don't you think Samsung would have done that?
[Galaxy S III Accessories] Product F(RED):
Edit. Misunderstood.
[HTC One X] greyhulk:
Posting this in general, as I'm not asking a question. I'm stating my findings. Though, feel free to chime in with your experiences.

I'm quite frustrated with mail on my One X. It drives me so insane, I want to go back to my Gnex or iPhone because mail works flawlessly on those. I have read others claiming they don't have this issue, but that's bull. I have had the AT&T version and now the International version and this problem is very real.

I have two accounts set up as Exchange accounts: One is my work e-mail, the other is Gmail. I also have Gmail set up through the native app.

Mail will work fine for a while, then just stops coming in. Today, it was my work e-mail account. I went into Accounts and Sync and there was a "!" on Calendar. It seems like when it can't sync one component of the account, nothing else comes in. I could be wrong. Most certainly, mail stops coming into the Mail app from time-to-time. It's like it just goes to sleep.

It will then inexplicably start working for a while, then stop again. It drives me batty. The moral of the story is, I can't rely on my phone for e-mail at this point, which is kind of a fundamental function of a smartphone. It's even more frustrating when I see the mail come in on every other device and my One X just doesn't get it. If I open Mail, it comes in and sometimes it will work normally for a while after that, but then it stops again.

Really hoping HTC fixes this soon, because it's a serious issue. The only thing I haven't tried is using a 3rd party client, but I don't want to do that because then the mail conversations won't be threaded in my contact history. And honestly, I shouldn't have to.

Also, disclaimer, I am NOT set to Smart Sync on any of my accounts. They are all push.
[HTC One X] chrisnash:
I can confirm that I am having the same experience and its really pi##ing me off!

Occasionally I get a message stuck in the Outbox as well and then it just keeps on resending the mail. 27 times once!

It also really sucks the battery when it plays up like this.

Always seems to happen after low or no connectivity.
[HTC One X] ladyhaly:
It happens to me with WiFi here at home. It's not just Mail but also other apps that need to sync like Weather. It's not because of the apps but because even though it shows my WiFi is connected, it is actually disconnected.

I went to another house with WiFi the other day. Perhaps they have different settings... Either way it never happened there. NEVER. I received e-mails right away on my Mail Exchange... Right away. My Weather never missed the update schedule.

Btw, have you enabled the security thing with Mail For Exchange? Something to do with the server. I have only enabled it yesterday.
[HTC One X] williamyi:
Is it because of sync setting?

I have 2 work email account, one set as push and another set to auto sync every 4 hours, both works fine no matter i'm on 3G or wifi. Besides, my Gmail using the native gmail app also works fine. The moment i saw a notification on my desktop then immediately the phone will notify me.
[HTC One X] lostunsunghero:
This is a very real issue for me, i was just about to make a thread on it myself. I have 2 email accounts, a hotmail and a gmail, neither refuse to sync. I Cant see new or old messages, sent, deleted etc on either account. It did work at one point but then it stopped again for no apparent reason.

100% battery

doesnt work on network or wifi

everything else syncs fine, inc dropbox and weather.

using default mail client.

set to sync when i open app.
[HTC One X] ladyhaly:
Er... Is it because it is set to sync only when you open the app?
[HTC One X] j4n87:
There is definatly an issue on HTC's side.

My exchange mail isnt working well as well. Set it to push...the first few minutes/hours AFTER I turned off the screen pushing works more or less good.

Test mails arrives a few seconds/sometimes minutes after I sent them to my own mail account...but when the phone is idling for some more hours it wont sync the mails anymore...it starts syncing the mails again when I turn on the screen.

Really annoying imo. On gingerbread push mail was working fine..mails arrived seconds after you sent them to the maila ccount that syncs the mails on the device.

I think the issue is smartsync in the settings.apk.

It tries to handle the data connection of the device to give better battery life..but therefore breaks for example proper mail syncing.

On gingerbread you was able to deactivate that feature, it was called "constant mobile data" or similar..if you unckecked it, your mobile data went to sleep after a while when your turned off the screen....on ICS you cant control it yet...Hope htc will fix it for the next OTA.
[HTC One X] lostunsunghero:
Well if thats the issue then its poorly designed. I'm seriously considering exchanging for the S3.

Regardless of when it is set to sync, it should sync when i want it to. So if i have manual sync, then when i refresh it i should be able to see new email, correct?
[HTC One X] greyhulk:
Yeah, that's what it seemed like to me: That HTC was defaulting to smartsync, even when it was set to Push, because it'll start working fine for a while, then stop again. This is really my only issue with the phone currently and it's also one of the most critical. It needs to be addressed sooner, rather than later.
[HTC One X] f3nd3r:
This has been happening to me too. It is not new though. It happened on my HTC Sensation. E-mail would gets stuck in the outbox and tells me it has failed when in fact it is sending it over and over and people end up with multiple e-mails from me. It is extremely frustrating. I also get the exclamation mark when trying a manual sync. It ONLY happens over WiFi and it is not all the time. It happens on different WiFi connections, not just mine and it can sometimes be fine for days. The annoying thing is, I do not know I am unable to receive e-mail until I try sending one and it fails. As soon as it fails I know the problem is back and I have to switch WiFi off.

Glad I am not the only one with this issue. I may end up trying a third party mail app if it isn't fixed.
[HTC One X] GuestD0799:
Yes, this is very annoying.

Happened to me once too, and I had to remove my account and re-create it.

Fixed it - but that's just really a work around for a problem that shouldn't exist...
[HTC One X] f3nd3r:
This doesn't work for me. I wish it was that easy.
[Xperia Play General] eztrada:
Hello, I go to all developers of this forum to start a petition and ask Sony to provide us the latest version of the update for Xperia Play ICS created by them. I believe that among all users of XDA we can achieve a stable version and enjoy our Xperia Play ICS, and I imagine we all like to be updated daily. I hope I can help. I accept ideas, criteria, complaints, all Luck. I'm on the lookout.
[Xperia Play General] Jordanooo:
http://xdaforums.com/showthread.php?t=1673231
[Android Q&A, Help & Troubleshooting] beginner:
I would like to extend from 10 minutes, the standard maximum possibility on Ics for lock the screen. Do you know if it is possible?

I was supposing it was some parameter on the system.

Thanks.
[Android Q&A, Help & Troubleshooting] mannu_in:
Hi,

In order to increase the wakeup time, follow the following steps:

System->Display-> Sleep and from the menu select the time you want...

In my phone, I have 30 minutes as maximum time.

Hope this resolve your problem.
[Android Q&A, Help & Troubleshooting] burdman:
I use a widget called screen toggle timeout to set mine to never
[Android Q&A, Help & Troubleshooting] beginner:
Thanks for your responses but...

- If you increase the screen time, it will be ever displaying.

- My company forces me for strong password when screen is locked. The solution I need is something can increase the delay time between the screen is off and the screen is locked. I have tested many solutions in the market but it dont work: everytime you getup the device the password screen is the first action, later the application that apparently can extend the delay, I expect you understand my meaning.

I think the delay time of the lock screen after the screen is off (from seconds to 10 mins) is stored in some table in the system, and maybe is not complex to change...
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Edit:

Check to see if your Tab 7.7 contains the brick bug using Chainfire's new "Got Brickbug?" app. URL below.

http://db.tt/ee0RCtoK

Here's my results:

Edit:

CONFIRMED. TAB 7.7 CONTAINS SUPERBRICK BUG. READ BELOW.

Edit:

Yah. I flubbed a few things in my explanation. I'm not an expert. But I am thorough. And as I said in this post before editing, my Tab 7.7 has the same chip and firmware. I only listed the firmware version though, here's both now below. Please just take a look at it and tell me if I was right. (By the way, I'd really much prefer it if you told me I was wrong.)

Less summary. More facts.

GT-P6810 - MAG4FA

/sys/block/mmcblk0/device/cid

1501004d414734464119d71350251f49

GT-N7000 - VYL00M:

/sys/block/mmcblk0/device/cid

15010056594c30304d191e8647cbae3b
[Galaxy Tab 7.7 General] wintermute000:
Speaking generally (i.e. for all droids) under what circumstances is that command invoked, and does it need root permissions?

i.e. what normal app / or system function would call that command in normal operation?
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
No. It is not dependant on root privileges. The bug is triggered by large erase operations such as large file deletion, "wipe data/factory reset" in ClockworkMod or stock recovery, or a simple factory reset from within the OS via the "Settings" menu. However, if the current Honeycomb builds for the Tab 7.7 made use of MMC_CAP_ERASE, I suspect we would know about it already. I'm fairly confident that we don't have anything to worry about for the time being. However, once ICS is released, things may change drastically. I'm hoping this thread gives devs and users enough to prepare themselves for the possibility of MMC storage problems in the future. With any luck, we'll be able to avoid the problems that so many Note owners experienced.
[Galaxy Tab 7.7 General] Entropy512:
You summarized a lot of things incorrectly.

MMC_CAP_ERASE is not a command, it's a flag in the driver that allows ERASE commands to be sent to the MMC chip.

Gingerbread kernels DID have this flag enabled - but they didn't cause damage because Gingerbread recovery does not attempt to erase a partition when wiping it, it just does a format (without a low-level ERASE).

Honeycomb recoveries/kernels are unknown.

Also, the fwrev is not the only important item - the flash chip name (/sys/block/mmcblk0/device/name) is also important.

To be in danger, you need:

MAG4FA, VYL00M, or KYL00M fwrev 0x19 - M8G2FA fwrev 0x11 (some Kindle Fires - assuming that the fwrev field is even at offsets 19,20 in the cid for that chip) may also be affected (There may be other Samsung eMMC chips/fwrevs affected, but these are the confirmed ones.)

A kernel with MMC_CAP_ERASE enabled in drivers/mmc/host/mshci.c

A recovery that performs erase operations when formatting a partition

Edit: It was recently confirmed that in nearly all configurations, large file deletion is safe. It's only dangerous if one of the partitions in use is mounted with the "discard" option - which isn't the case for any device I've seen yet.
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Okay. Let's go ahead and address the reason why I PM'ed you and asked you to look at this in the first place. I AM NOT AN EXPERT. I was asking for your help. I simply noticed that everything that made my Note susceptible to bricking was also found in the Tab 7.7. Now, if I understand you correctly, my Tab 7.7 has all the bad juju and the wrong kind of wipe/format could really ruin my day. Am I missing something?
[Galaxy Tab 7.7 General] Entropy512:
No - you still haven't posted the name of the flash chip, just the cid - we need the name too.
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Yes I did post the name. It's in the first post edit.
[Galaxy Tab 7.7 General] Entropy512:
MAG4FA fwrev 0x19 is the same chip the E4GT uses - it's affected.

So it's really a question of whether Samsung disables MMC_CAP_ERASE in the kernels or not. I personally wouldn't touch your ICS releases until source code is reviewed or Samsung acknowledges the issue and states that they have fixed it in P68x0 releases
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Thank you. I appreciate you hopping on the Tab 7.7 forum and looking at this. Any mods out there feel like posting a sticky about this? Or, Entropy, would you like to throw together a warning post about this? As eager as I am to get off of Honeycomb, I would rather avoid the palpitations that accompanied my GT-N7000 upgrade.
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Bump. Added download link for Chainfire's new Brick Bug app. See first post.
[Galaxy Tab 7.7 General] wathefak:
I got the same output..

How can we fix this?
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
There's nothing we can do to fix it. Either Samsung needs to find a way to update the eMMC firmware, or remove MMC_CAP_ERASE from the kernel (as far as I know). Unfortunately though, Samsung has yet to even acknowledge the existence of the bug.
[Galaxy Tab 7.7 General] skeeterpro:
It's an understatement to say this is rather disquieting! If indeed as smarter people that I have said this "bug" exists on ALL 7.7's and Samsung has been less than forthcoming about it, would reaching out to the appropriate trades be a wise move? Perhaps they (with a "bigger and louder voice") motivate Samsung to effect a fix or at least plans to issue one?

I do so enjoy this tab and am concerned a "time bomb" lays in wait to bite me....
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Thursday, June 7, 2012

SkeeterPro & XDA Members:

Well, I understand your fear. I am an amateur when it comes to Android and mobile hardware. My forte has historically been networking. Just see Entropy's reply to my original post for an example of my ignorance. However, mobile or not, all computers contain the same basic components. Considering how integrated mobile devices are, this bug SHOULD scare the crap out of anyone with an affected device.

However, that being said, Tab 7.7 owners shouldn't have anything to worry about at present. It seems that Honeycomb on the Tab 7.7 is configured the same as Gingerbread on other affected devices. This means that while the bug is present, the OS will not trigger it. The problem with the other devices, like the International Note (Which I own), is that the new ICS updates for these devices were configured so that they COULD trigger the bug (Unlike Gingerbread). So until Samsung releases ICS for our beloved, unique, spectacular, awe-inspiring tablet, we should be in the clear. Of course, take all of this with a grain of salt; but if Honeycomb were capable of triggering the bug, I think we would have noticed by now.

Now, on another note, I think this thread should be stickied. Maybe it's just me, but I'd rather avoid the fiasco that the GT-N7000 endured. As an International Note owner, I would have much rather known about this bug BEFORE I updated to ICS. I was one of the first to update, so I didn't hear about the bug until the day after I updated. Lots of good people completely lost their devices to this bug! Now, if we're in any position to avoid this calamity, shouldn't we take advantage of it? Again, this is just my opinion. However, if you don't believe me about how awful this whole thing was/is, hop on over to the GT-N7000 forum and see for yourself. Samsung still hasn't issued a fix. It is a very terrible and very real problem. Hopefully, Samsung will forego enabling MMC_CAP_ERASE in our ICS build when it comes. But just in case it doesn't, I think we would all be better off if we understood what this bug is and what this bug isn't.

Anyway, I've rambled enough. If anyone with the power to do so would consider it, please sticky this. I would really appreciate it, and ALL of the Tab 7.7 owners would have the opportunity to benefit from it. Thank you.

Thank you,

Ed (Mister_Mxyzptlk)
[Galaxy Tab 7.7 General] Entropy512:
Well, I think stickying the thread would unnecessarily scare people. Remember, to be in danger requires ALL THREE of the conditions below - fail any of the conditions listed and you're safe.:

1) Defective flash chip

2) A kernel that allows ERASE commands to hit the chip

3) A recovery that attempts to do a low-level erase when wiping.

Currently, as far as I can tell:

1) All of your current stock kernels fail condition 3 for danger at a minimum

2) The CM9 release fails condition 2 for danger due to being based off of the I9100 Update4 source code.

In short - currently there is no known dangerous configuration for this device, despite the defective flash chip. When you receive ICS leaks that may change - but it is unknown.

Stickying this would create unnecessary panic - look at all of the I9100 users that got scared when Got Brickbug? made the portal, even though with one exception (a kernel which was quickly pulled), they have always been safe as all of their kernels/recoveries have always failed either condition 2 or 3 above or both.
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
Yeah. Maybe you're right. But I still think something should be done to caution users about updating to ICS when it comes out. Maybe an announcement instead of stickying this. As a Note owner, I'm already well aware of the danger, and I'm totally comfortable using my Tab 7.7 right now; and others should be too. However, there has to be a way to caution people without generating a panic. After all, nothing can compare to the panic that comes AFTER devices have started bricking. The N7000 forum still gets daily brick posts, and warnings have been posted all over the place. I would just like to see if we can make sure there isn't a single bricked Tab 7.7. That would be nice. Avoiding the problem would be a lot better than trying to clean it up. Would you feel like writing a casual, non-alarming word of caution on the matter?
[Galaxy Tab 7.7 General] aletheus:
Hey, so what do we do if we have this bug? Not upgrade to ics when/if its released?
[Galaxy Tab 7.7 General] Mister_Mxyzptlk:
I wouldn't upgrade until after the source is released to see if it's safe.
[Galaxy Tab 7.7 General] skeeterpro:
Good advice. While it's most often best to be forewarned....no reason to morph into "Chicken Little"! Let's leave that to the Tea Party. :)

But seriously, thanks Ed and Entropy, for the information. I shall await ICS until source is deemed appropriately safe.

(Mr. Mxyzptlk..."Ed" would be simpler to say backwards. lol)
[Galaxy Tab 7.7 General] kishd:
I agree forewarned is forearmed. I bought the 7.7 after bricking my note. Still waiting for it to be returned from Samsung who are charging an absolute fortune to repair what is essentially a manufacturing defect.
[Galaxy Tab 7.7 General] sg10:
I suppose no problem with my P6800 ?

:)
[Galaxy Tab 7.7 General] steveathome:
Tried the app and have the brick bug. I wonder if Samsung in testing of ICS on 7.7 they may have bricked a few Tabs! :D
[Galaxy Tab 7.7 General] LSD DREAMER:
If i update with the official Samsung ota update and i have the brick bug they should repair it under warranty . They can't make me pay for there mistakes
[Galaxy Tab 7.7 General] aletheus:
The problem with that is they say they can tell the device has been rooted even if the flash counter isn't triggered. I dunno, I'm just saying, a bunch of rooted devices and superbrickbug strickes them on through an ICS rollout, all of a sudden anybody who wants one just has to buy a new one.

I had to root my device to do what I wanted with it in the first place (screencast screen activity of drawings)... I'm cautious. I've heard now hong kong and autrailia rollouts are first?

The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
[Galaxy Tab 7.7 General] aletheus:
well, i may have bricked my tab.... i'm getting an emmc error when i try to apply an update from zip. but for some reason, cwm thinks the sd card is "internal".
[Galaxy Tab 7.7 General] FateZero:
CWM thinks my SD is internal as well,I think its just a glitch from CWM did you make a nandroid backup? When I get odd error or failed flash I just wipe and restore.
[Galaxy Tab 7.7 General] adinis78:
I got the same message, what should we do if we get the update? Should we install it? Please advise. Thanks.
[Galaxy Tab 7.7 General] aletheus:
i did wipe and factory restore from within cwm. i did a backup, then moved it to the "external" sd. now cwm thinks it's internal and when i go to the restore option, it's not available. now, i attempted to backup in its current state and it created a clockworkmod directory on the internal sd. but it FC's after i select the option. it gets far enough to make the directory then it flops. i tried flashing the OC kernel but i don't have the firmware its written for, so even though it worked, it didn't kick it out of soft brick. the problem now is that the usb cable won't be here till tomorrow. is 24 hours stuck on the gTab splash screen (won't proceed to boot animation and won't turn off) going to cause any noticeable burnout? i read online that the average lifetime of amoled and oled displays is measured by the time it takes for its luminosity to drop by %50)--around 50,000 hours. i calculated this is 58 months running 24/7, so surely 24 hours is negligible...)
[Galaxy Tab 7.7 General] himadri:
Got the bug in the system. Could someone with the required knowledge make a to do and not to do list when we recieve the long waited update ? Only thing i learnt from various threads that one must never do a factory wipe/reset if detected to have the malaise. And better to avoid cwm, deleting large files. We will appreciate a clear to do list very much. Thank you.