[Analysis] EC09 SD Card Survey Preliminary Analysis - Fascinate General

So far (as of 11AM, 7/7/11), there have been 29 unique users who have voted in this survey. While the SD card bug has not been isolated as of yet, my preliminary analysis did turn up some significant trends. The 2nd post will analyze what those whose cards are still working had in common, and the 3rd post will analyze trends among those whose cards have experienced failure.

What Those Whose Cards are Still Working Had in Common
There have been four users (as of 11AM, 7/7/11) who posted that their cards were still working when they voted in the poll, who also posted more details about their experience flashing EC09. Unfortunately, the things they all had in common were also shared with some who have lost their SD cards. Nevertheless, following their steps **may** give you a greater chance of preserving your card. First I will list what all four had in common. Next I will list what three out of four had in common.
1. They all...
...previously ran UKB (Community Rom) 2.x
...used the stock EC09 kernel that came with the original leak
...had a working stock video player (Obviously, you can't control this but if your video player is working that's at least a good sign
...had more than 4GB available on their cards
2. Three out of four...
...flashed the stock EC09 leak (no custom ROM)
...wiped data, cache and Dalvik in CWM in addition to Odin (which also wipes all three)
...restored their apps with Titanium Backup rather than reinstalling them manually through the Market
As stated before, THERE IS NO GUARANTEE THAT FOLLOWING THESE STEPS WILL PREVENT YOUR CARD FROM BEING DISABLED. For the time being, there is no confirmed fix for this very serious issue. Even though every developer reminds you that you flash their ROMs at your own risk, flashing EC09 in any form is especially risky and far more dangerous. As more results come in, more trends may come up that at least help narrow down the causes of this issue.

Trends Among Those Whose SD Cards Were Disabled by EC09
There are some notable trends among those who have had their cards disabled by EC09. In this post, I will note the things that resulted in SD card failure for everyone who did or experienced them, and I will note other notable trends. It must be pointed out that this is a PRELIMINARY analysis of a NON-SCIENTIFIC poll, so these results should be taken as guidelines, not facts or rules etched in stone.
1. Things that users did that always led to SD card failure as of 7/7/11 (please also notice the disclaimers):
...All came from NON-UKB (Community ROM) 2.x builds (even some who WERE on UKB 2.x lost their cards)
...All were either on Nameless 4.0 or TechnoROM (but some of those who used stock EC09 and Nameless 4.1 also lost their cards)
...All used the recommended CWM recoveries posted on the Nameless ROM and TechnoROM threads (by the OP). Again, many who did not use these CWM recoveries also lost their cards.
...All flashed the Nameless custom kernel (many of those who used stock EC09 kernels also lost their cards)
...All had non-working stock video players (obviously, you can't control whether your video player works after flashing EC09, and many who had working video players also lost their cards - nevertheless, if your video player is not working, I strongly recommend getting off EC09 immediately - and I hope you already backed up your SD card's contents)
...All had less than 4GB available on their SD cards before flashing EC09 (most of those who had more than 4GB also lost their cards, but having less than 4GB has so far yielded a 100% rate of failure)
2. Other trends:
...9 users lost their cards right away or within a day (I CAN'T EMPHASIZE THIS ENOUGH - BACK UP YOUR CARD BEFORE TAKING THE PLUNGE!)
...12 users lost their cards within a few days (even if you didn't lose your card right away, you're definitely not in the clear)
...4 users lost their cards after a week or more of running EC09 (even after a week, there are no guarantees that you're safe)
...11 users lost their cards while their phones were running, and 11 users lost their cards while booting up (the conclusion is obvious, isn't it?)
Unfortunately, nothing conclusive has been found as to the cause of the SD card failures, but there are some things noted above that I strongly recommend avoiding, as they have yielded 100% failure rates so far. Actually, I strongly recommend against flashing EC09 at all, unless you have some spare SD cards and back your data up religiously (oh no! I said the "R" word!). Every developer I've talked to has said the bug has not been found and appears to be quite random. Please take this into consideration when you decide whether to flash anything EC09.

Given the number of voters and items and the fact that these things were also shared by people who did lose their sdcards, it seems likely that what your seeing is random noise rather than a causal connection.

drnihili said:
Given the number of voters and items and the fact that these things were also shared by people who did lose their sdcards, it seems likely that what your seeing is random noise rather than a causal connection.
Click to expand...
Click to collapse
Unfortunately, that is also the conclusion I came to

So of 29 reporting users, only 4 did not lose their cards. Even taking into account reporting bias (people without problems tend not to report that) that suggests a very high failure rate. Given that, the problem is likely something that is common in the system itself rather than in how users implement the system. For example, it may have something to do with the way that the leak examines, and perhaps tries to repair, media on the sdcard. (I know nothing about how the internals work, this is just an example idea.)
I commend you for taking the time to go through all this, but I agree, there's nothing terribly instructive in the results. Alas, research doesn't always yield the results we hope for. (As a suggestion, you may want to reword the items in point 1 of your third post. "All came from non-UKB" sounds like everyone who had a failed card came from non-UKB. I'd say something like "All who came from non-UKB".)

Good info. I wish there was some sort of smoking gun. Lots of desirable things are built into EC09.
That being said, I'm still waiting for mine to fail. Ran the first week with the stock 16GB card and no issues, went back to CM7 then back to EC09 with a spare 4GB card. Still no issues.
One thing you may want to add to the poll, is ask who had "auto rotate" disabled and if they did, was the SD card failure still there. That's a known issue with the package since it causes a HUGE cpu draw. Could be related, or may not be. Who knows.

sarkozy said:
Good info. I wish there was some sort of smoking gun. Lots of desirable things are built into EC09.
That being said, I'm still waiting for mine to fail. Ran the first week with the stock 16GB card and no issues, went back to CM7 then back to EC09 with a spare 4GB card. Still no issues.
One thing you may want to add to the poll, is ask who had "auto rotate" disabled and if they did, was the SD card failure still there. That's a known issue with the package since it causes a HUGE cpu draw. Could be related, or may not be. Who knows.
Click to expand...
Click to collapse
Good question! I may add that to this thread later (can't add to the original survey thread though)

sarkozy said:
Good info. I wish there was some sort of smoking gun. Lots of desirable things are built into EC09.
That being said, I'm still waiting for mine to fail. Ran the first week with the stock 16GB card and no issues, went back to CM7 then back to EC09 with a spare 4GB card. Still no issues.
One thing you may want to add to the poll, is ask who had "auto rotate" disabled and if they did, was the SD card failure still there. That's a known issue with the package since it causes a HUGE cpu draw. Could be related, or may not be. Who knows.
Click to expand...
Click to collapse
There is no guarantee that your card will fail. However, it appears that this situation is worse than I first thought. Assuming at least hundred people flashed, and at least 25+ had failed cards... it isn't looking good. Thank you skynet for your poll, but I really think that it will go nowhere. It most likely has little to do with the procedure one follows (like if they ran UKB). Probably the only thing that would matter is if they flashed the ODIN leak and then a custom, just a custom, or just the ODIN leak. It is probably just an issue within the system that may or may not be able to be fixed without source code.
Back when I updated the TechnoROM OP to warn about the extent of the SD Card bug, I pretty much stopped development. There is no reason to flash this leak (EC09) with the amount and severity of bugs. Not only does the SD Card have issues, but the auto-rotate causes excessive cpu usage. Other issues include wake lock permission issues (which may or may not be fixable without source).
More importantly, logcats and any debugging reports could be of help, so don't be afraid to post.

Yeah, looks like you're right, jptech. Nothing conclusive has resulted from the poll, and as you said it likely has nothing to do with user procedures. Just thought I'd try... Do you think there may be any correlation between the autorotate issue and the fried sd cards? Like, maybe, autorotate maxes the CPU which then causes the phone to spazz out and bork the sd card? Just grasping at straws...

skynet11 said:
Yeah, looks like you're right, jptech. Nothing conclusive has resulted from the poll, and as you said it likely has nothing to do with user procedures. Just thought I'd try... Do you think there may be any correlation between the autorotate issue and the fried sd cards? Like, maybe, autorotate maxes the CPU which then causes the phone to spazz out and bork the sd card? Just grasping at straws...
Click to expand...
Click to collapse
Does autorotate engage during boot? The proximal trigger seems to engage at a lot of different times. I'd start by looking at what happens during boot as that's likely to have the least amount of variation. However, the variability in the onset strongly suggests that there is also some interaction effect or random element to account for also.
Do we know that the SD failures are of the same type? Are they all fried in the same way or to the same degree?

The hard part with this survey ( and by no means is this your fault) is that you will inherently get more responses from those who had failed SD cards than those who are running just fine. Failure likes to promote itself while success does not. Again, not bashing you....just point out the obvious which I am sure you already know.
I do commend you for even attempting this and the results are interesting. Not really a clearly defined answer yet. Hopefully more will vote.

I may be 100% wrong in this assumption, but what if this is why Verizon has been quiet about our gb update? Maybe they saw the bug and are trying to fix it?
Sent from my SCH-I500 using XDA App

DirgeExtinction said:
I may be 100% wrong in this assumption, but what if this is why Verizon has been quiet about our gb update? Maybe they saw the bug and are trying to fix it?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Makes sense - remember how buggy DL30 and EB01 were? Of course, neither one had a bug anywhere near as serious as this one.
Another Fascinating post by my XDA app...

Didn't get in on the vote but I will add my expierence with EC09 in hopes it can help. I ran it for couple weeks and had no SD failure, I went back to ComRom because couldn't play videos and the gallery didn't work properly. Here was my upgrade and downgrade procedure.
1.Odined EC09 full stock leak while running ComRom 2.1
2.Odined CWM 3-30 fix all, installed Superuser ran couple days there.
3.Tried nameless for a couple days, didn't care for it (sorry nameless but good job)
4.Odined back to stock EC09 and rooted again same procedure as above.
5.Finally Odined back to EB01 then built back to current setup with ComRom
Hope this can help in some way.

Related

POLL: International I9000 Internal 16GB SD issues

Please vote ONLY if you have the international version of the I9000 16GB. No 8GB please!
Since us Canadians are experiencing massive issues with our I9000M dying, we would like to know if the international brethren have the same problem.
Poll is going to be simple
Please state how long you've own the phone, and how long have you been using your current configuration
I voted by accident, -1 vote to dead sd without lagfix 2.1. Sry about that.
Not a bad idea, but I haven't seen a single report on these forums about a dead internal SD card on an international Galaxy S I9000.... I'm pretty sure it's a Canadian I9000M issue only...
Edit: I guess I was wrong. Maybe this is a good idea after all!
Sorry for hijacking
Is it possible to replace internal sd on these phones?
Sent from my GT-I9000 using XDA App
sonci said:
Sorry for hijacking
Is it possible to replace internal sd on these phones?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yes, but you will need to replace the entire motherboard, so not really
stickied
I've been wanting to see this for a long while as I've come across several people in the forum with this problem on the I9000 version, not I9000M
also I know of Retail Stores having problems with 16GB I9000 version, and keeping them on stock due the constant return/exchange, according to the sales guys all 16GB versions seems to have the internal SD problem.
the 8GB I9000 version in the other hand seems to be less affected, return rate due internal SD issues are rare.
thedauntlessone said:
Please vote ONLY if you have the international version of the I9000 16GB. No 8GB please!
Since us Canadians are experiencing massive issues with our I9000M dying, we would like to know if the international brethren have the same problem.
Poll is going to be simple
Please state how long you've own the phone, and how long have you been using your current configuration
Click to expand...
Click to collapse
thedauntlessone said:
Please vote ONLY if you have the international version of the I9000 16GB. No 8GB please!
Since us Canadians are experiencing massive issues with our I9000M dying, we would like to know if the international brethren have the same problem.
Poll is going to be simple
Please state how long you've own the phone, and how long have you been using your current configuration
I voted by accident, -1 vote to dead sd without lagfix 2.1. Sry about that.
Click to expand...
Click to collapse
i9000M dying due to using the lagfixes ? or just a manufacturing problem?
i voted working sd with lagfix 2.1 , my i9000 was bought as soon as it was available in the UAE even before Etisalat got to it. It was running the JHJP4 FW
and ever since have been rooted/lagfixed with OCLF/Voodoo tried OC1.2 and back to voodoo+oclf, going strong no problems what so ever YET
about FW only upgraded from JHJP4 to JPJG8 and the last config was removing the 1.2oc kernal + voodoo and reverted back to voodoo V4 + Oclf as its working flawlessly with no black screen problems(unresponsive) since 2 weeks now.
battery was always a problem but i guess i got used to having my phone on the charger whenever i can and even if its in the 80-90% area
The I9000M 16GB are just dying from corrupted MoviNand from an unknown cause. It's pretty much concluded Lagfix is not killing the phone, just accelerating the defective phones to die faster (within days). I"m just following a similar poll structure from the I9000M poll thread.
GT-I9000
owned for almost 4 months
Used lagfix(es) for about 3 months (ext2 loops (+/-2months) and ext4 reformats (+/-1month) on internal SD)
No Issues Here...
No issues so far
I've using the international version with 16 GB internal SD for about two months. Initially with the stock ROM (Eclair JF1, I think) and Voodoo lag-fix and now with Froyo JPM without any lag-fix.
No problems so far (keeping fingers crossed though).
I own SGS GT-I9000 for a month, Android 2.1 Eclair, the internal SD card (16GB) works with and without lag fix.
Internal SD working with lagfix (OCLF till date, trying voodoo from today) - Eclair 2.1 (stock ROM) on SGS I9000 16GB. And what exactly do you guys mean by "dead" ? Does it work after a reformat or does it become completely unusable ? Also, would that be covered by the warranty ?
Prasad007 said:
Internal SD working with lagfix (OCLF till date, trying voodoo from today) - Eclair 2.1 (stock ROM) on SGS I9000 16GB. And what exactly do you guys mean by "dead" ? Does it work after a reformat or does it become completely unusable ? Also, would that be covered by the warranty ?
Click to expand...
Click to collapse
Don't bother with Voodoo. I probably have exactly the same hardware as you and the new JPM is working very well for me even without a lag-fix. I suggest you upgrade to that (via the registry hack) or just wait for a few days for the official India release.
I did have Voodoo lag-fix on my stock Eclair earlier, but frankly I didn't notice any difference. But then I wasn't having lag problems as such and just installed it out of curiosity
BTW, the warranty should cover a dead SD card. I bought mine in Croma, Mumbai and they said everything (including non-functional buttons etc) is covered, except damage caused directly caused by the user (broken screen etc). Not that i'd take their word for it. Also, not sure if rooting etc voids the warranty (anyways, I didn't buy the extended one they were plugging).
Got the i9000 16G for about a month now, memory seems to be fine till now.
Using the OCLF on JPM.
I also would like to know what is meant by "dead" internal SD.
I have voted for "2.2 working with lagfix", however guess will have to remove lagfix, fill the system and cache (2GB) partition completely (somehow) and the rest (13.xGB) as well completely.
We could load the internal SD as mass storage and run chkdsk (in Windows) to scan for bad clusters. If we do find some, guess there is some issue with the internal SD and we should go for a warranty claim.
been using my phone for 3 months now with and w/o lagfix and my internalSD works fine.
4 months ECLAIR without lagfix and never modified anything.. my internal SD is still fine!
thedauntlessone said:
The I9000M 16GB are just dying from corrupted MoviNand from an unknown cause. It's pretty much concluded Lagfix is not killing the phone, just accelerating the defective phones to die faster (within days). I'm just following a similar poll structure from the I9000M poll thread.
Click to expand...
Click to collapse
I have explained on the first page already.
There are plenty of information in the other thread about the i9000m. This is for the international version. As to whether you should install lag fix depends if you want to take the chance to see if your phone has a defective sd card. Lag fix doesn't kill your phone, it only will accelerate the inevitable.
Sent from my GT-I9000M using XDA App
No issues with my sd....its been 5 months now.

GPS Flawless/I am requesting XDA Community and Developers to please read!!

I just recently received a new Captivate today through the ATT insurance program that came preloaded with the JH7 Eclair build. The first feature that I was anxious about testing was the GPS since myself and others on this forum seemed to experience difficulty applying the OTA update from ATT. I drove an estimated 20 miles in the city and 15 miles on highway and noticed that I no longer experienced lag when making turns, or when I came to a complete stop and the navigation icon never jumped to adjacent streets or went over a 10m accuracy. I also was able to get a lock in 3-5 seconds while going 70MPH during my highway drive. When I returned home I rooted my phone and made a Nandroid backup and proceeded to flash cognition 2.4.1. Once I did this I decided to test the GPS again with a custom ROM installed and noticed that the GPS issues that I had previously experienced with my old phone were present once again. So after I tested the GPS on Cognition, I decided to restore to my original firmware and the GPS accuracy was restored to the favorable results as previously mentioned. What I am asking the community as well as the devlopers at XDA is if I provide you with my Nandroid backup files, would this be helpful in solving the GPS issues once and for all? I am just uncertain if maybe newer phones that came preloaded with JH7 may have different GPS settings than the OTA updates.
If the developers would like my Nandroid backup please just ask and I will upload.
UPDATE*
Here is the image file of the stock JH7 that has given me VERY accurate GPS results from the previous stated post. This is from a Nandroid backup and I do not know how you would go about installing this but I'm sure someone from here does and will test it. This has not been tested yet, but I respectfully challenge the developers and community to try this out to see if it is an improvement. This is an Eclair JH7 rom. Thank you for your time.
http://www.filefront.com/17508797/system.img/
http://www.sendspace.com/file/ryxaw1
UPDATE 2**
I went on about a 30 minute trip and here are my results
http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=114887993519189258855.000494f37559dc102964c&t=h&z=12
** Please note you will need to zoom in to notice all of the turns that I made. I also made a U-turn and traveled on some of the same roads in opposite directions. Everything is just as accurate as the day before.
UPDATE 3***
I would like to extend my thanks to mattbeau for trying this out and posting his results. The results furthermore prove my hypothesis and are consistent with my results. I requested mattbeau to post detailed instructions on how to flash it so others can try. Please I encourage others to give this a try the more tests we gather the easier it will be for the Developers to find what makes this different.
mattbeau My Tracks: http://maps.google.com/maps/ms?msa=0&msid=208605913791985313826.000494f74ae16f5e33c81
UPDATE 4****
Very special thank to mattbeau for posting instructions on how to get this to work. Still need a few more people to test this but so far this is the most accurate the GPS has ever been on the Captivate here it is:
download the following: http://www.multiupload.com/CB5PFRTRYF
extract with winrar or what ever you want
so this is what is working for me.
ensure the clockwork update.zip is insalled on the root of your internal SD card
create a folder /sdcard/clockworkmod/backup/jh7gps/
copy system.img and nandroid.md5 to the above folder
Oneclick back to JF6
enable debugging under settings
using adb
adb restart recovery
select reinstall packages
(it will install teh clockwork recovery)
again select reinstall packages
select advanced restore
select jh7gps
select restore system
select yes
your phone will reboot with the new system.img installed
baseband is still jf6
If I could as that everyone that tries this please post their results. The more consistent this is the more things we can rule out.
UPDATE 5*****
I apologize that the megauploads links it temporarily unavailable. We are currently working on getting this back up as soon as possible. Also will be posting my My Tracks for day 3 shortly as well. I encourage anyone else to post their results as well.
Here is mattbeau's link that was originally on megauploads. Since some of you were having problems I moved it to here:
http://www.multiupload.com/CB5PFRTRYF
Let me know how this works out. I thank all of you for your assistance.
UPDATE 6******
Here is the My Tracks for the third day of testing. GPS accuracy does not appear to be deteriorating and have consistent results from previous tracks. This is looking more and more promising by the day. Comments are welcome!
http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=114887993519189258855.00049509766fdff4bcb11&ll=34.720186,-77.346539&spn=0.005176,0.013078&t=h&z=17
Thank you mattbeau for your thorough comparison to other JH7 ROMs. Please keep us all posted on your findings.
Some people think that 2.4 caused GPS issues that were worse than stock. I'm not necessarily saying where I stand on the issue - but your decreased performance may just help prove that 2.4 is bad at GPS.
I feel skeptical that Samsung would have a different OTA JH7 and in store JH7 and what I said above sounds like a better idea. Hmm maybe I should go to an earlier version.... helpful either way!
Sent from my SAMSUNG-SGH-I897 using XDA App
I am definitely not certain as well, but the GPS performance that I am experiencing with this new phone is up to par with my Garmin. More notably, I have had my old captivate since early August and have tried out all official updates on it including JH7 that don't even compare to the perfect performance this one has. I am just trying to see if I could give my Nandroid backup to someone that knows more than I do and possibly solve this issue for custom rom development etc...
Wait a few days, if you still have awesome GPS then there might be something to it. I highly doubt it though.
Swyping...please read slowly!
im not sure about this although there quite possibly could be a combination of hardware and software. my wifes phone works perfectly with gps and we got ours at the same time but my gps has been horrible since day one but we use hers and no lag, jumping off the roads or anything
Here is one result for today will post at least one everyday for consistency.
http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=114887993519189258855.000494e61790fb41e435e&ll=34.65951,-77.343278&spn=0.018956,0.023432&t=h&z=15
ive had 4 captivates so far. me and my wifes original 2 and 2 replacements. all 4 have been the same where sometimes there dead on accurate, and they might be like this for a week. then one day they might take 10 min. to get a lock where the day before it would lock instantly. overall id say the gps on all the phones ive had werent horrible, but could be better. im to the point now that i think its just a hardware issue, and no matter what settings we put in or what we change, the gps just isnt going to be perfect.
danquirk2000 said:
I am definitely not certain as well, but the GPS performance that I am experiencing with this new phone is up to par with my Garmin. More notably, I have had my old captivate since early August and have tried out all official updates on it including JH7 that don't even compare to the perfect performance this one has. I am just trying to see if I could give my Nandroid backup to someone that knows more than I do and possibly solve this issue for custom rom development etc...
Click to expand...
Click to collapse
I had that kind of perfect GPS with my captivate once and lost it.... once you have it never let go hahaha
Sent from my SAMSUNG-SGH-I897 using XDA App
I will continue to track all my trips for the next couple weeks and post my results. I also have made a nandroid backup of the stock JH7 firmware that came with my phone that I will post shortly.
danquirk2000 said:
I will continue to track all my trips for the next couple weeks and post my results. I also have made a nandroid backup of the stock JH7 firmware that came with my phone that I will post shortly.
Click to expand...
Click to collapse
I would love to have a copy I just want a working phone
OP, so many of us are so over this GPS issue with these otherwise very nice performing phones. It's just a damn shame that Samsung let this line go to market with this type of problem. That being said, I, for one, appreciate those that continue to try to find a way to resolve this issue. I am one of those that read CLShortfuse's complete write-up on this matter and form that I feel pretty certain it is NOT a hardware issue; the same chip is used in other devices without issue. I think that the issue is with Samsung's coding and, perhaps, the placement of the chip in the phone.
I see a lot of notes about quick locks, slow locks, etc....the real issue is tracking, not locking. I have found that even my Garmin can take over a minute to lock, depending on where I am in the city (elevation, hills, etc.) and also is sometimes affected by weather. I've waited over 5 minutes for my Garmin to lock (only a few times) but when it does it stays locked and my tracking is very good. However, even my Garmin will loose me for a few seconds, especially when taking a ramp that it didn't expect me to (not the route it planned for me). Unfortunately, neither of my 2 Captivates worked this way. It's perplexing and frustrating. I can tell you that the fastest locks I ever got were immediately following the OTA update (I got mine through Kies Mini). Unfortunately, I flashed another ROM before I tested the tracking.
I hope some devs out there will take your offer seriously and take apart your backup, if possible.
I am going to upload the file once I have a friend with a captivate try it out first.
I agree with boomerod - remember the biggest problem for us is the losing a lock part mid-trip
Sent from my SAMSUNG-SGH-I897 using XDA App
I would think the first step would be to have someone with gps issues flash your nandroid. If that makes their gps perfect as you report, then it may be worth investigating further... just my .02
Sent from my GT-I9000 using XDA App
danquirk2000 said:
Here is one result for today will post at least one everyday for consistency.
http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=114887993519189258855.000494e61790fb41e435e&ll=34.65951,-77.343278&spn=0.018956,0.023432&t=h&z=15
Click to expand...
Click to collapse
are you kidding me??? zoom in on that track map, and you will see it takes you off the road all over the place. Accuracy is still horrible. I have never ever seen a phone go off track like that so dont tell us to "live with it". It may look good zoomed out but try actually looking closely at that and tell us it is perfect
Well buddy17, if you do look closely at that map you will notice that it is off less than 5 meters for the short period of time that it was off. Most GPS software maps auto lock onto streets when they are that close but when using My Tracks it does not. I am almost certain it is impossible to have GPS that is spot on all the time and this could also be due to the inaccuracy of Google My Tracks. If you would post your results I am sure you would see a significant difference in tracking.
Also the GPS performance on this firmware seems to not have the "turn lag" or movement while being stopped issues that I have previously experienced as well as what others have reported. I am almost done uploading and all I am respectfully requesting from the community is to try it out and see what happens please. I would like to thank the community for their time and effort to make our captivate have the best experience possible.
Another useless thread of gps nonsense...lol. I cant believe I even looked. Shame on me
Sent from my Ilikeboobs897
bulletproof1013 said:
Another useless thread of gps nonsense...lol. I cant believe I even looked. Shame on me
Sent from my Ilikeboobs897
Click to expand...
Click to collapse
I think more or less the shame is on you for posting.
On a side note:
OP I just got a new one today too from the warranty dept. The GPS While driving is nothing but flawless. Thank you for reporting this to us, and I am a 2nd to agree how amazing the mid drive is. Showed me on the road i was on the entire time. And didn't loose a lock.
UPDATE**
Here is the image file of the stock JH7 that has given me VERY accurate GPS results from the previous stated post. This is from a Nandroid backup and I do not know how you would go about installing this but I'm sure someone from here does and will test it. This has not been tested yet, but I respectfully challenge the developers and community to try this out to see if it is an improvement. This is an Eclair JH7 rom. Thank you for your time.
Update links are on first post
I agree with the others, this thread is a waste of time. Your software image is no different then the other 500,000 JH7 phones leaving the factory or that had the update. If Samsung made a fix, we would see a different version number.
They don't just replace files and leave the version numbers the same - that would be a support nightmare.
If someone was interested, they would just compare your files to another set and look for differences; BUT, because everyone else knows that files don't get changed without creating a new build, they are not going to spend time on your challenge.

[Q] Damage By Flashing?

Hello, I'm new to the whole Android thing, but I managed to recently root my Shift, and I can attest to the addictive properties of trying out ROMS/Kernels and all that good stuff. But I was worried about the idea of all this flashing I'm doing, as in the month or so I've been rooted I've flashed about four ROMS, messed up a few times, done a good 5 or 6 Nandroid restores/backups. I was just curios to know if this is excessive, or if this could damage my phone in any way. Thanks for any help guys!
P.S., I apologize if this is either in the wrong thread, or has already been answered >_< I'm still a young'un
As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.
I recall this discussion back when I had a TouchPro2, I don't know if it applies to the Shift as well but I assume it does. From my understanding it was determined by people far more informed than me that flashing would eventually wear out the NAND memory...but it would take more flashes than even the most fiendish flashaholic could complete in the phones lifetime to do. This is what I know from discussions of a past phone, I'm not claiming anything about the lifetime of the phone and take no responsibility if you flash 5000 ROMS tonight and your NAND burns out. lol
I think the only way you can actually brick your phone from flashing is if you flash a bad ratio from like a gsm carrier to a cdma phone. Might be wrong. Cause even if you flash a bad rom as long as you have a working recovery you can always just reflash a new rom or ruu
I think his underlying question may have to do with the fact that every NAND flash memory module has a limited number of writes in its lifetime before it can't write another bit and tell whether or not the module is in the 0 or 1 state.
This is also why data2ext/apps2ext etc anything that constantly writes information to your SD card will also degrade the lifetime of the SD card.
Basically yes, in principle the number of times you write new data to the phone's built-in memory, you shave off another write from its life. But I don't think this is significant at all. Just as a reference, I'm sure there are people with the original G1 who have flashed a countless number of times over several years and still have it working.
^^This.
If it gives you peace of mind, think about how many times a ROM chef's phone gets flashed in its lifetime and usually if the phone dies it's on account of flashing something experimental that bricks the phone (wrong radio, etc.) I've never heard of someones NAND actually burning out. I flashed my TouchPro and TouchPro2 quite literally hundreds of times if that makes you feel better.
kbrn said:
As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.
Click to expand...
Click to collapse
THIS. Main danger.
^ Shift Faced
jesusice said:
THIS. Main danger.
^ Shift Faced
Click to expand...
Click to collapse
Agreed!
Sent from my PG06100 using XDA Premium App
Thanks for all the answers, you guys are great I really appreciate your help. You're replies have put my mind at ease seeing as my level of flashing honestly doesn't seem that excessive compared to that of a developer's.
Sent from my PG06100 using XDA App
On my HeroC I changed roms two to three times a week. When CM6 came out, it was everyday (with full wipe) thanks to the nightlies. Then aosp started releasing his stuff in IRC yada yada.
My heroc made it well over a year of that torture. My wife did as well, barely.

EU bug

I keep on hearing this EU bug here and there .....I have some questions regarding this .....
1,why does this happen?
2,will it affect only vibrant running ics or even jellybean?
3.how can I bring back my vibrant to normal? (don't post me regarding those guide I need breif steps).........thanks for helping
Answers (sort of):
akarshfrevr said:
1,why does this happen?
Click to expand...
Click to collapse
1. No one knows why it happens yet. Seems the earliest case had been around February for the Vibrant (before it got a real name like EUbug. Happened to Jasonhunterx)
akarshfrevr said:
2,will it affect only vibrant running ics or even jellybean?
Click to expand...
Click to collapse
2. There has been a crap-ton (this isn't metric or imperial but is a valid form of volume in my realm) amount of speculation, attempts, theories, support, more speculation all in the [Guide] Encryption Unsuccessful - Reset Android thread in the Captivate side of things. Me, Yosup, Mr_Psycho, DerT, Silvercrown, Swehes,...have all contributed to it over time but no one can get to the *root* of the problem. Even Adam Outler and Cyanogen themselves don't know why. There is also a Reference thread going too and is located here ---> [REF][ICS] Encryption Unsuccessful Reference
Here is a recent post I had over there with a brief synopsis of devices effected and ROMs/Kernel.
Bottom line, is there is no solution yet, although some users have reported getting their /data back but have no idea why or how. Further bottom line would be, if you don't want to get hit or roll the dice with the EU bug, STAY ON FROYO OR GB builds. **Sorry for the Bold CAPs but that is an important part that many should read. So far I haven't heard anyone on JB get hit with it, but that doesn't mean it isn't out there. Was Months before ICS users realized what was happening and then it was too late.
akarshfrevr said:
how can I bring back my vibrant to normal?
Click to expand...
Click to collapse
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
agreed @ WOOD im yet to upgrade /update or renew my contract with Tmobile i dont know what i want to do anymore ever since the Vibrant it was like now all i think of is ..is there DEVing going on with this and that phone lol i wanted the Blaze 4g because the dual core SNAP Dragon s3 but i saw little to no dev on there still trooping out the Vibrant hardcore lol with great deal of DEV's was so sad to c FISH leave my heart SANK lol
Woodrube said:
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse
Since it happened to me also (read my testimony here), I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! Pull the battery out and boot to recovery through button combo and restore a nandroid. If you are a flasher and not a noob, always keep a working nandroid backup (it saved me). I'm not sure if I could flash anything else, perhaps it's the same flashing process somehow getting corrupted?
ioancr said:
... I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! ...
Click to expand...
Click to collapse
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.
yosup said:
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.
Click to expand...
Click to collapse
Wow, I didn't know that, it seems really worse than I thought of. Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore?
Then I was yes very lucky, sorry for you guys and hope someday someone will save your phones too...
ioancr said:
... Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore? ...
Click to expand...
Click to collapse
Yes, I could get to recovery, but I couldn't mount the internal sd anymore (and haven't been able to yet to date). So, I couldn't restore a nandroid backup or flash any of the roms I had downloaded on the int sd.
The vold.fstab emmc swap method at least let's me use the phone normally (albeit without the int sd), but I'm keeping my fingers crossed Woodrube & The Gang figure out how to restore access to the int sd ... some day.
I got scared by this bug i left ics itself and now I'm running helly bean ...........I don't have an ext memory card and should I get one? you know just in case if something goes wrong I can use the roms from ext memory card or nandroid backup and come back to normal ...........
This bug appears to be similar to the emmc bug on the note. Essentially, the eprom (programmable chip) on the motherboard of your phone.... for some reason it writes additional bits of code (like 2 bits or 8 bits) on the chip which then basically changes how the cpu sees the index... which then Bricks the phones.
Like Woodrube said...... The Vibe is 3 years old and it Totally Amazes me how great this phone really is.......... it is one of the few that could get ICS or JB ....... think about it this thing was released with Eclair (2.1)...... and still running like that lil bunny......
Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Woodrube said:
Answers (sort of):
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse
oka1 said:
... Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Click to expand...
Click to collapse
:thumbup::thumbup: Congrats, Woodman!! :thumbup::thumbup:
Very worthy bump-in-pay-grade for one of the all-time "counselors" that roam these halls. Great to see that good guys do win.
Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
How to reproduce:
- After bootup perform sudden power removal
- boot-up interup and reboot.
Click to expand...
Click to collapse
Yup, with encryption support in ICS, Android has become a lot more
picky about having all the filesystems initialized with valid data,
and mistakenly assumes that anything that's not zero or valid is
encrypted, refusing to go any further.
In Gingerbread and before, anything that wasn't valid was expected to
be invalid, and Android would just re-initialize it, regardless of
whether it was zero or not.
Click to expand...
Click to collapse
theexel said:
Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
Click to expand...
Click to collapse
Interesting stuff. I wonder what would cause part of the file system to become invalid though, seemingly during normal usage.
Not trying to thread jack but I read this quote on team-passion by the dev:
The encryption bug is due to a partition going bad. If it happens to the internal SD then you're done. It's not an ICS bug. It happens on all ROMs and all phones. ICS makes an effort at fixing it. Previous versions don't, or don't make themselves apparent. Bricks have been happening for ever. The Vibrant is 2 years old. Hardware fails. Just like in your PC. This kind of error come up on stock OTA updates, on other devices, as well. Not for SD, as far as I could find. But OTA updates of ICS are for new devices. If there are any corruptions the phone gets returned
Click to expand...
Click to collapse
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
till date it has only occurred on ics roms ......jb roms not even a single case reported .....I'm hoping it won't come to jb .....I got scared by this bug and I moved from ics to jb .......2.2 and 2.3 are safe to escape from this bug
crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)
Woodrube said:
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)
Click to expand...
Click to collapse
ok so I'm running chimera v1.1 if I want to flash froyo again can I just flash a froyo rom from ics and be ok? or do I have to odin back to stock and go from there?
Gingerbread/Ice Cream Sandwich/Jellybean to Froyo with just a ROM flash = Brick waiting to happen.
ODIN back to stock, bud.
You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.
Woodrube said:
You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.
Click to expand...
Click to collapse
Thanks guys I'm going to miss ICS but it's just not worth keeping. I would love to flash to JB but GPS and 911 issues are scaring me away.

Question:N7 I/O problem to N4??

While reading some article for android i saw an article for n7...that having problem with I/O do we have the same problem anyone notice this?
Code:
This little thread aims at getting some information about an issue I thought for months I am alone with.
Since I got my One X, stock or running custom stuff, my phone always gets sluggish far far beyond the point of being useable if I fill my /data partition with too much data (~1GB free triggers it usually), or move large files around in it (dd'ing some zeros onto it triggers it too).
No kind of rebooting, cache wiping, or anything else will fix it permanently. The lags will be back after a very short while once you experienced them.
Vodafone told me to RMA the phone (it was only software branded), but If you know me, then you know that I am lazy in these kinds of things and since I thought I was the only one and a wipe of /data fixed it every time for a short period, I didn't do it.
Yeah I know. Lazy b*tch.
[DEVS & EXP-USERS ONLY] HTC One X - High I/O wait. Same issue as the N7. (confirmed)
pikachukaki said:
While reading some article for android i saw an article for n7...that having problem with I/O do we have the same problem anyone notice this?
Code:
This little thread aims at getting some information about an issue I thought for months I am alone with.
Since I got my One X, stock or running custom stuff, my phone always gets sluggish far far beyond the point of being useable if I fill my /data partition with too much data (~1GB free triggers it usually), or move large files around in it (dd'ing some zeros onto it triggers it too).
No kind of rebooting, cache wiping, or anything else will fix it permanently. The lags will be back after a very short while once you experienced them.
Vodafone told me to RMA the phone (it was only software branded), but If you know me, then you know that I am lazy in these kinds of things and since I thought I was the only one and a wipe of /data fixed it every time for a short period, I didn't do it.
Yeah I know. Lazy b*tch.
[DEVS & EXP-USERS ONLY] HTC One X - High I/O wait. Same issue as the N7. (confirmed)
Click to expand...
Click to collapse
No, because the Nexus 4 is using better hardware than the Nexus 7.
Sent from my Nexus 4 using Tapatalk 2
pikachukaki said:
While reading some article for android i saw an article for n7...that having problem with I/O do we have the same problem anyone notice this?
Code:
This little thread aims at getting some information about an issue I thought for months I am alone with.
Since I got my One X, stock or running custom stuff, my phone always gets sluggish far far beyond the point of being useable if I fill my /data partition with too much data (~1GB free triggers it usually), or move large files around in it (dd'ing some zeros onto it triggers it too).
No kind of rebooting, cache wiping, or anything else will fix it permanently. The lags will be back after a very short while once you experienced them.
Vodafone told me to RMA the phone (it was only software branded), but If you know me, then you know that I am lazy in these kinds of things and since I thought I was the only one and a wipe of /data fixed it every time for a short period, I didn't do it.
Yeah I know. Lazy b*tch.
[DEVS & EXP-USERS ONLY] HTC One X - High I/O wait. Same issue as the N7. (confirmed)
Click to expand...
Click to collapse
No. Nexus 7 uses a cheap storage controller that starts behaving in weird ways when free space goes below 3gb.
Nexus 4 does not have such issues.
Sent from my Nexus 4
Thanks for the info...i never experianced any problems but i found it and just ask!!

Categories

Resources