Related
After I updated my G1 to the newest Radio. Radio: 2.22.19.26I
My G1's voice quality has improved. But it would random reboot or not responed after an incoming calling (Ringing) or after the call (when I press the Back KEY).
IF it doesn't reponse, it could be powered on as well. I have to take off the battery and put on the battery again to power the phone.
Drea110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
ROM 1.5
baseband 62.50S.20.17H_2.22.19.26I
Kernel 2.6.27-00392-g8312baf
Internal version kila-user 1.5 CRB21 147201 ota-rel-keys,release-keys
I have bought a new battery, but it doesn't help.
Before I updated the Radio, Only voice quality problem. Do I have to update the SPL or ROM ?
Any suggestion? Thanks very much!
I have been having the same issues with mine and no matter what ROM I try I keep having the same issues with random resets.. sometimes on incoming calls etc.. I was starting the think that perhaps it is my phone.
You have a crap SPL installed. Search the DEV forum for the hugely long SPL thread and find yourself the 0.95.3000 SPL -- that is the good one that you want -- includes unlimited fastboot.
The radio image itself isn't known for causing that kind of weirdness unless there is something in the system image that doesn't like it, I suggest upgrading to Android 1.6.
myfriendsh said:
After I updated my G1 to the newest Radio. Radio: 2.22.19.26I
My G1's voice quality has improved. But it would random reboot or not responed after an incoming calling (Ringing) or after the call (when I press the Back KEY).
IF it doesn't reponse, it could be powered on as well. I have to take off the battery and put on the battery again to power the phone.
Drea110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
ROM 1.5
baseband 62.50S.20.17H_2.22.19.26I
Kernel 2.6.27-00392-g8312baf
Internal version kila-user 1.5 CRB21 147201 ota-rel-keys,release-keys
I have bought a new battery, but it doesn't help.
Before I updated the Radio, Only voice quality problem. Do I have to update the SPL or ROM ?
Any suggestion? Thanks very much!
Click to expand...
Click to collapse
Thanks very much lbcoder !
I would try to upgrade my SPL and ROM.
Is this one for my G1?
hxxp://android-roms.googlecode.com/files/EngBootloader_v2_NoSigCheck.zip (SPL)
and Another ROM based on Official Donut 1.6
SPL flash first ? then ROM?
Thanks again for your help!
Best regards!
David
Yes, I believe that that is the correct SPL, however, I am not familiar with that source.
I would suggest getting it from HERE: http://forum.xda-developers.com/showthread.php?t=455860 -- I know for fact that it is good from this link.
Note: the so-called "hardspl" doesn't actually offer any benefits. Unlocked fastboot is a free for all. You can literally write anything you like in the world with the proper engineering spl, so it really doesn't make sense to use a HACKED UP SPL.
Thanks lbcoder.
After upgrade to the 0.95.3000 SPL and 1.6ROM
The G1 still would reboot randomly.
Strange! Any suggestion? Before the upgrade of radio, it won't reboot or FReeze.
No idea for me now.
Anyway, thanks very much!
myfriendsh said:
Thanks lbcoder.
After upgrade to the 0.95.3000 SPL and 1.6ROM
The G1 still would reboot randomly.
Strange! Any suggestion? Before the upgrade of radio, it won't reboot or FReeze.
No idea for me now.
Anyway, thanks very much!
Click to expand...
Click to collapse
What 1.6 ROM are you using?
Since we're trying to deal with stability issues at this moment, try installing the official ADP1 system image from http://developer.htc.com/adp.html
And don't forget to perform a user-data wipe.
See if it'll work stable as a fully-stock ADP1. If it does, then start playing with modified firmwares and see where it gets you.
If it doesn't work stable with all official ADP1 software on it, then I would guess that there is some kind of hardware fault.
There is a newer radio out now..
http://forum.xda-developers.com/showthread.php?t=640535
Might be worth a try if all else fails.
goldenarmZ said:
There is a newer radio out now..
http://forum.xda-developers.com/showthread.php?t=640535
Might be worth a try if all else fails.
Click to expand...
Click to collapse
Not related.
Risky.
2.22.19.26 radio is known to be stable. I suggest sticking with that rather than trying out random things from questionable sources.
goldenarmZ said:
There is a newer radio out now..
http://forum.xda-developers.com/showthread.php?t=640535
Might be worth a try if all else fails.
Click to expand...
Click to collapse
been confirmed to work over and over.... also works for me. a lot of people say they also get faster gps lock and better reception... dunno about that for me. it's definitely stable, though.
I had to send out my g1 to HTC, back in july for the same issue. If i pressed down the lower portion of the phone, it would reboot. Like a short/mobo issue. They replaced the board. You may have a hardware fault.
r3s-rt said:
been confirmed to work over and over.... also works for me. a lot of people say they also get faster gps lock and better reception... dunno about that for me. it's definitely stable, though.
Click to expand...
Click to collapse
Go back to 3rd grade.
You do NOT introduce unknown variables into an equation until AFTER you have isolated the problem. If you do, and the problem persists, you will NEVER know the source of the problem.
bigo1087 said:
I had to send out my g1 to HTC, back in july for the same issue. If i pressed down the lower portion of the phone, it would reboot. Like a short/mobo issue. They replaced the board. You may have a hardware fault.
Click to expand...
Click to collapse
Way to read between the lines, Poindexter.
Where do you think I've been leading him?
If he follows exactly what I have suggested and there are STILL problems, then it MUST be hardware defect.
lbcoder said:
Go back to 3rd grade.
You do NOT introduce unknown variables into an equation until AFTER you have isolated the problem. If you do, and the problem persists, you will NEVER know the source of the problem.
Click to expand...
Click to collapse
Actually, since the variable that triggered the problem in the first place was a change of radio, It seems perfectly logical to try another version.
I do agree though, chances of a radio rom alone causing this kind of instability seem remote. I'd look elswhere first.
goldenarmZ said:
Actually, since the variable that triggered the problem in the first place was a change of radio, It seems perfectly logical to try another version.
I do agree though, chances of a radio rom alone causing this kind of instability seem remote. I'd look elswhere first.
Click to expand...
Click to collapse
It is actually a well known side effect of mismatched radio/system combinations.... which is why it is NOT a good idea to try yet another radio, but instead to try a KNOWN VALID combination with KNOWN GOOD radio and KNOWN GOOD system.
That "new" radio that people seem to be jumping into... where did it come from? Some guy named "phreke"? What is in it? You REALLY trust that source? It could be ANYTHING -- it COULD just be hacked to change the version number. There is no telling what it is!!!
Until it comes from a KNOWN SAVE SOURCE (i.e. developer.htc.com/adp.html), I would STRONGLY recommend keeping clear of it!
lbcoder said:
Go back to 3rd grade.
You do NOT introduce unknown variables into an equation until AFTER you have isolated the problem. If you do, and the problem persists, you will NEVER know the source of the problem.
Click to expand...
Click to collapse
Here's what you said in a nice little metaphor (if it was grammatically correct):
You're cars engine blows up. You put a new steering column in your car. Since you changed the steering column, you will never know why your car broke down.
Um... wa? I seriously rofled when I read that. Thanks, bro.
Now, blah blah blah, he said it was the newest radio that caused the problem: so try the newest newest one and see if it works. If that doesn't make sense to you, then damn. There are some good psychiatrists these days. They can probably help you with such abnormal thinking.
Oh: I'm in college. Calculus for that matter.
Reason I state this - this isn't an equation. The correct definition for equation is a mathematical problem. Not a general problem. Argue back "yes it is," then please grab a dictionary. Or use google. Or wikipedia. Or just get brain. <3
Ahhh a pissing match! What fun! LOL.
Probably a good idea for you to evaluate your opponent before just assuming that you can piss further, otherwise you will tend to make a fool out of yourself. Which you have.
You: College student.
You have NOT graduated... otherwise you wouldn't call yourself a student any more. That leaves on the table the possibility that you will FLUNK OUT.
Similarly with your "calculus" course. The fact that you are in the course does NOT imply that you know calculus since you could still FAIL.
On top of that, calculus has no relevance to this discussion at all! Are we trying to come to the integral of .... radio? LOL. How about the partial derivative of engine with respect to steering column?
I would suggest that you enroll yourself in some LOGIC courses -- that seems to be the area where you are suffering. Might help you to learn the meaning of "correlation".
Reason I state this - this isn't an equation. The correct definition for equation is a mathematical problem. Not a general problem. Argue back "yes it is," then please grab a dictionary. Or use google. Or wikipedia. Or just get brain. <3
Click to expand...
Click to collapse
Yes and no.
The nice thing about a "general" problem is that it can be expressed mathematically -- otherwise what is the point of math? In fact, this problem is very simple, we can express it numerically in base-2 (binary) and just use straight BOOLEAN LOGIC to solve it.
Here's our boolean definitions: Works = 1 "true". Doesn't work = 0 "false".
Here's our equation expressed logically:
radio AND spl AND system_image AND hardware = false.
radio = works/true,
spl = works/true,
true AND X = X, applied twice, (this is called the "property of boundedness")
system_image AND hardware = false
TWO VARIABLES -- "system_image", and "hardware".
Either could be bad.
BOTH could be bad.
How do you tell?
(you don't want to add in another variable here, do you?)
By substituting one for a known good.
So we introduce the STOCK ADP1 system image.
system_image AND hardware = ?
You will note the "?" introduced since we no longer know the answer.
system_image = works/true
property of boundedness one more time...
hardware = ? --> if it works with known good system image, radio image, and SPL, then the previous system image was defective, otherwise the hardware is defective.
Note: if we find that the hardware STILL doesn't work, this does NOT prove that the previously tried system image is good, since FALSE AND FALSE = FALSE, and TRUE AND FALSE = FALSE.
Proven logically.
Mathematically.
Using equations.
Imagine that!
And to put the pissing match to rest... I have two university degrees in computer engineering, one of which is a graduate degree. I have taken all of the advanced calculus courses offered, as well as all of the logic courses.
Congratulations kid, you lost the pissing match.
I hope you can learn something from this.
lbcoder said:
Ahhh a pissing match! What fun! LOL.
Probably a good idea for you to evaluate your opponent before just assuming that you can piss further, otherwise you will tend to make a fool out of yourself. Which you have.
You: College student.
You have NOT graduated... otherwise you wouldn't call yourself a student any more. That leaves on the table the possibility that you will FLUNK OUT.
Similarly with your "calculus" course. The fact that you are in the course does NOT imply that you know calculus since you could still FAIL.
On top of that, calculus has no relevance to this discussion at all! Are we trying to come to the integral of .... radio? LOL. How about the partial derivative of engine with respect to steering column?
I would suggest that you enroll yourself in some LOGIC courses -- that seems to be the area where you are suffering. Might help you to learn the meaning of "correlation".
Yes and no.
The nice thing about a "general" problem is that it can be expressed mathematically -- otherwise what is the point of math? In fact, this problem is very simple, we can express it numerically in base-2 (binary) and just use straight BOOLEAN LOGIC to solve it.
Here's our boolean definitions: Works = 1 "true". Doesn't work = 0 "false".
Here's our equation expressed logically:
radio AND spl AND system_image AND hardware = false.
radio = works/true,
spl = works/true,
true AND X = X, applied twice, (this is called the "property of boundedness")
system_image AND hardware = false
TWO VARIABLES -- "system_image", and "hardware".
Either could be bad.
BOTH could be bad.
How do you tell?
(you don't want to add in another variable here, do you?)
By substituting one for a known good.
So we introduce the STOCK ADP1 system image.
system_image AND hardware = ?
You will note the "?" introduced since we no longer know the answer.
system_image = works/true
property of boundedness one more time...
hardware = ? --> if it works with known good system image, radio image, and SPL, then the previous system image was defective, otherwise the hardware is defective.
Note: if we find that the hardware STILL doesn't work, this does NOT prove that the previously tried system image is good, since FALSE AND FALSE = FALSE, and TRUE AND FALSE = FALSE.
Proven logically.
Mathematically.
Using equations.
Imagine that!
And to put the pissing match to rest... I have two university degrees in computer engineering, one of which is a graduate degree. I have taken all of the advanced calculus courses offered, as well as all of the logic courses.
Congratulations kid, you lost the pissing match.
I hope you can learn something from this.
Click to expand...
Click to collapse
Lol.
Quick, I have to run. Wanted to get my laugh in from you.
1. Still not mathematical.
2. It doesn't just have to be the system image, spl, or hardware. Could be an application doing it. Could be a lot of things.
3. Your University Degree doesn't really mean anything.
4. Starting college fresh out of high school with already 2 years under my belt, suggests I probably won't fail. School is too damn easy. I've never once had to study for any test I've ever came across. That's how damn easy school really is.
5. You didn't prove anything except that if one doesn't work it could affect the other one. Who the HELL ever said it couldn't? I just suggested trying a new radio if he thought the radio was the problem. If it still causes random reboots, the it wasn't. Next step is disable applications. This is more likely the cause rather than a hardware failure or a "bad" SPL.
6. Chill out, bro. Take 4 blue footballs and report to me in the morning. 8)
7. I SAID IF THE ENGINE BLOWS UP. I promise you, if your engine blows up putting another steering column won't help you at all. I PROMISE you that. Don't believe me, please feel free to toss a match in your oil, replace your steering column (if you can find it), and start your car. It won't work.
8. You said go back to third grade. I just knew you were going to attack with something like "blah, blah, it is mathematical (because it's really not) what are you in 5th grade math." You're quite predictable, and fun.
Lbcoder, while I do agree with your logic of isolating variables to figure out what is causing the phone issues, your attitude towards others opinions/thoughts could use some improvement. How about you guys put an end to this "pissing match" and help the OP figure out his phone issues.
OP, I would suggest following lb's suggestions of using what has been proven to work together first. If your issues are still there, signs lead to a possible haredware issue. If your problem is gone, start replacing SINGLE components first in hopes to replicate your issues. If single components don't cause the issue, then its quite possibility a combination.
Lbcoder, I'm not against you in anyway, I just think your attitude towards others could be better, IMO.
I've already provided you with all you need in order to understand.
If you insist on STILL failing to understand (I assume to be some moronic childish ego thing...), then that is YOUR LOSS.
I could go through and refute your statements with proof, but that would not be worth the effort, you clearly lack the necessary understanding of logic and mathematics in order for this to work for you.
I suggest you stick to your drama courses. There is some chance that you will pass that.
r3s-rt said:
Lol.
Quick, I have to run. Wanted to get my laugh in from you.
1. Still not mathematical.
2. It doesn't just have to be the system image, spl, or hardware. Could be an application doing it. Could be a lot of things.
3. Your University Degree doesn't really mean anything.
4. Starting college fresh out of high school with already 2 years under my belt, suggests I probably won't fail. School is too damn easy. I've never once had to study for any test I've ever came across. That's how damn easy school really is.
5. You didn't prove anything except that if one doesn't work it could affect the other one. Who the HELL ever said it couldn't? I just suggested trying a new radio if he thought the radio was the problem. If it still causes random reboots, the it wasn't. Next step is disable applications. This is more likely the cause rather than a hardware failure or a "bad" SPL.
6. Chill out, bro. Take 4 blue footballs and report to me in the morning. 8)
7. I SAID IF THE ENGINE BLOWS UP. I promise you, if your engine blows up putting another steering column won't help you at all. I PROMISE you that. Don't believe me, please feel free to toss a match in your oil, replace your steering column (if you can find it), and start your car. It won't work.
8. You said go back to third grade. I just knew you were going to attack with something like "blah, blah, it is mathematical (because it's really not) what are you in 5th grade math." You're quite predictable, and fun.
Click to expand...
Click to collapse
Warning : This survey is only for i9000M (Aka Bell Samsung Vibrant)
Hey,
So i know theres already another thread. Problem is, only those who have got corrupted internal sd's ever visit that thread, and hence we end up with a lot of "non working" data.
I want both sides of the story. What causes it to screw up and what causes it not to.
Ive created a form at Link
The data from the form is at Link
These questions are a lot more focussed than the ones in the original thread.
Current Maintainers in charge of modifying data upon a user-request / Keeping data clean:
wang1chung
daneshm90
Suggestions are welcome to improve the questionnaire.
Hopefully this will help us find out what is causing these corruptions.
bump... keep this on the first page so that we get more and more data entries...
Interesting poll. Hope we get a bigger data set.
Sent from my GT-I9000M using XDA App
aphoebic said:
Interesting poll. Hope we get a bigger data set.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Yea we've gotten a lot of entries so far.
So far seems as though anything through odin eventually screws up these phones :S
Replied (oops, set name as groan instead of Groaner. Owner can correct this if you want.)
Nice to see.
it seems it's all over the board and does not matter if you had made changes or not. rooted, lagfix, Rom...makes no diff. i didnt change anythign and got the problem.
At one point there were no SGS's to be found. this dry period of about 2 weeks before a new shipment came in. Could they have corrected some hardware issues for this 2nd batch (i think it was in September)?
I'd like to know how many phones after the dry period are experiencing this issue.
groaner said:
Replied (oops, set name as groan instead of Groaner. Owner can correct this if you want.)
Nice to see.
it seems it's all over the board and does not matter if you had made changes or not. rooted, lagfix, Rom...makes no diff. i didnt change anythign and got the problem.
At one point there were no SGS's to be found. this dry period of about 2 weeks before a new shipment came in. Could they have corrected some hardware issues for this 2nd batch (i think it was in September)?
I'd like to know how many phones after the dry period are experiencing this issue.
Click to expand...
Click to collapse
Im starting to consider whether those who say they didn't do nething and it still bricked have "used phones" where the previous user mightve flashed stuff.
Yea ill change ur name on it.
I added my info..and bumping the thread at the same time.
I forgot to put in other that i removed OCLF after a couple weeks due to all the problems I saw ppl were having. You can update my info if you'd like
by the looks of things, im REALLY glad ive never used odin
evil-doer said:
by the looks of things, im REALLY glad ive never used odin
Click to expand...
Click to collapse
I know eh. By the looks of it, odin screws up our phones, aside from a few odd cases where even stock phones got corrupted :S
But yea im on my 3rd sgs and im just using stock + voodoo. Gonna wait it out for froyo.
My first entry, row 52, was an error.
I repartitioned with odin last month while returning to stock JH2 from the aborted Scandanavian Froyo. No problems yet with an August 21st battery manufacturing date.
Good idea !
I've been lucky with my phone. I flashed twice with ODIN using the JH2 rom. Once with re partition and it's been ok.
From the looks of things there is no real rule as to if you flash then your phone will screw up... But seems like the chances of getting a brick increasing with flashing. If thats the case, then whats the point of having this phone... it sucks all the fun out of android (to me atleast...)
Whats the warranty on these things ?
1 yr no ???
Here are the 2 combos im interested in :
1. Has anyone bricked their i9000m using only heimdall ?
2. Has anyone bricked their i9000m w/o using odin but flashing roms/stuff through recovery (for eg Doc's rom)
from my understanding, heimdall doesn't repartition, so it would be equivalent to using odin without repartition.
i'm going to have to agree though, when i get my phone back, no more odin flashing. only clockwork. clearly, there's a pattern there.
AvatarReborn said:
Whats the warranty on these things ?
1 yr no ???
Click to expand...
Click to collapse
Yea there is 1 year warranty...
Hi everyone...I just wanted to suggest that the form should also include a manufacture date field (the battery or the phone's doesn't really matter) because if it is a faulty batch of memory (internal sd), then maybe we can pinpoint the timeframe in which that faulty batch was present. btw: my battery says 28 august.
EDIT: on #43 on the results says that the battery is manufactured in sept but the phones bought in aug... a new battery?
B-1P said:
Hi everyone...I just wanted to suggest that the form should also include a manufacture date field (the battery or the phone's doesn't really matter) because if it is a faulty batch of memory (internal sd), then maybe we can pinpoint the timeframe in which that faulty batch was present. btw: my battery says 28 august.
Click to expand...
Click to collapse
I did consider adding that before. Thing is how do you find this info ?
Are you going by manufacturer date on battery ?
Cuz in a lot of cases if sent for repair the battery is not replaced.
Also the battery manufacture date has no relation with the phone's manufacture date.
submitted.
Okay, so i called a sprint store today and talked to a rep named Ozzie. I told him, "My samsung epic's physical keyboard skips keys when I type on it every once in a while." His response was, "oh well the froyo they released has a great deal of bugs involved such as the camera and sd card." I asked him if the keyboard skipping keys was a common problem with the update and he told me, "yes that is very common." He told me to wait for the "new" update that is supposed to be coming out within the next week (yeah, right). I didn't realize eb13 caused this issue...
UPDATE: Talked to a sprint rep through chat and this is what he said,
17:41:52 : Tim: Initial Question/Comment: I received the eb13 froyo update for my Samsung Epic and now my physical keyboard skips keys every once in a while. I press on the key and it still skips. I was told by a sprint rep that it was a known bug with eb13 and it should be fixed with another update coming soon.
17:41:57 : You are number (2) in queue.
17:42:02 : Please wait and the next available account specialist will be with you shortly.
17:42:07 : You are next in queue...
17:42:12 : Jonas S has joined this session!
17:42:12 : Connected with Jonas S. Your Reference Number for this chat session is 2290211.
17:42:12 : Thank you for contacting Sprint. My name is Jonas S.
17:42:20 : Tim : Hi
17:42:39 : Jonas S: Hi.
17:45:19 : Jonas S: I understand your concern that you are not able to use froyo update with you EPIC, I apologize to inform you that this is a know issue and most of our customers have this issue with epic but you don't worry our technicians are working over this and soon this will be fixed
17:45:51 : Tim : Really? And what if this issue is not fixed?
17:47:24 : Jonas S: Actually due to some issues froyo has been removed from our server and we are diligently working on this, I will provide you a link where you can view this once it is available
17:48:27 : Tim : Okay. So what if the release they come up with next doesn't fix the issue? Will I be able to get a new phone that doesn't have this problem? (Since it is a known issue that sprint caused)
17:50:09 : Jonas S: I certainly understand your point but the new update will fix the issue you will not need to change the phone. I understand how it feels to pay for something that does not work up to your expectations. I re apologize for that
17:50:36 : Tim : Okay. So the update will fix the issue?
17:52:34 : Jonas S: Yes, be assured this will fix the issue, most of our customers using epic are facing this issue so we have been working over this and soon we will come up with new update
17:54:01 : Tim : Okay thanks for your help
17:54:14 : Tim : one more thing
17:54:18 : Tim : any eta on the update?
17:54:24 : Jonas S: You're welcome and thank you for you understanding in this regard.
17:54:24 : Jonas S: Sure
17:56:24 : Jonas S: Please let me know your second concern
17:56:40 : Tim : what do you mean?
17:57:19 : Jonas S: Oh, got it, you meant is there any expected time when this will be available, right?
17:57:24 : Tim : yes.
17:58:49 : Jonas S: I don't want to provide you incorrect or false information, as of now we do not have any expected date, you can view the link below and once it is available it will be updated there
17:59:23 : Tim : Alright thanks
17:59:29 : Jonas S: http://shop.sprint.com/en/software_downloads/pda_smartphone/index.shtml
17:59:59 : Jonas S: You're welcome
18:00:09 : Jonas S: Is there anything else I can help you with?
18:00:28 : Tim : Nope thats all. Thanks Jonas
18:01:03 : Tim : wait
18:01:14 : Jonas S: Sure
18:01:19 : Tim : Is there a reason the epic isn't on that link?
18:02:29 : Jonas S: Yes, once the updated version of friyo is available, this phone will be there
18:02:40 : Tim : Alright, thanks again. Bye
18:03:19 : Jonas S: You're welcome, thank you for your time with us and have a great weekend
18:04:23 : Jonas S: It’s been my pleasure to serve you. Please don't hesitate to chat again at sprint.com.
Keys skipping was on di18 also, just very very very less common. The nearly one skipped key a sentence crap started on dk28, eb13 is improved to about one skipped key every 2-3 sentences.
Sent from my SPH-D700 using Tapatalk
I agre that this issue is worse on DK28 and EB13 than on DI18..... (I'm on EB13 right now, and made several 'mistakes' just typing this!) kind of unaceptable for such an expensive phone.... but oh well. I hope the next update fixes it, but I'm not holding my breath after all that has happened recently.
Turning swype off seemed to fix my missing key issue. YMMV
Turning off Swype helped my issue but did not fix it completely and I still fail the "qaol" test.
I skip letters almost every other word. It's next to impossible to use the physical keyboard on EB13. Double letters (like tt in letters) will always skip the second one.
I returned my phone once for skipping, and the second one was just as bad or worse than the first one. DK28 was worse than DI18, and EB13 makes using the physical keyboard pointless.
So frustrating. I otherwise love the phone!
Also, turning of Swype doesn't help at all. Even removing the apk doesn't help. Using touchpal prediction for the hardware keyboard fixed the problem in a way, but it's annoying it a whole new way.
How to fix? Remove swype?
Sent from my SPH-D700 using XDA App
There is no solution currently. Bummer.
churro7 said:
How to fix? Remove swype?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
since the problem seems to vary by OS, it should be software-related.... that's the good news, I suppose. I wish I knew what was involved in fixing it, and hopefully the next update will fix it.... but I'm not counting on it. but yeah, DI18 seems the best for typing.
I didn't have this problem *at all* on DI18. It started for me on DK28. Definitely software-related.
I do believe it is some service or app interfering with the keyboard. I do have days when I have no skipping at all, even now. But I don't know what I do to enable that. I am one of those people that randomly force closes various things when my phone gets frustratingly slow, so I think there's something that I occasionally shut off that does it, but it probably automatically comes back.
Some people have hypothesized that it's related to the long key press opening a selection of extended characters. It seems plausible, but I haven't the faintest idea how to remove that feature. I've never used it, and doubt I ever will.
I think this is related more to the size of the fingers and the speed of the brain more than a problem with the hardware or software.
Top Nurse said:
I think this is related more to the size of the fingers and the speed of the brain more than a problem with the hardware or software.
Click to expand...
Click to collapse
Go away troll.
Sent from my SPH-D700 using XDA App
Sesquipedalian said:
Some people have hypothesized that it's related to the long key press opening a selection of extended characters. It seems plausible, but I haven't the faintest idea how to remove that feature. I've never used it, and doubt I ever will.
Click to expand...
Click to collapse
That was me, I wish some devs could look into it.
Sent from my SPH-D700 using Tapatalk
Top Nurse said:
I think this is related more to the size of the fingers and the speed of the brain more than a problem with the hardware or software.
Click to expand...
Click to collapse
1/10
Try harder
styckx said:
1/10
Try harder
Click to expand...
Click to collapse
I happen to have big fingers. It is also a known fact that the brain runs faster than the fingers. So skipped keys (or added ones) are a known problem since the days of the first typewriters. Unless you guys can somehow separate the keyboard from the phone so as to perform some scientific testing, I will go with my previous statement.
Top Nurse said:
I happen to have big fingers. It is also a known fact that the brain runs faster than the fingers. So skipped keys (or added ones) are a known problem since the days of the first typewriters. Unless you guys can somehow separate the keyboard from the phone so as to perform some scientific testing, I will go with my previous statement.
Click to expand...
Click to collapse
The arrogance.......
Sent from my SPH-D700 using XDA App
Kinda related. Do you guys have the problem when you slide out the keyboard to do a quick "just type" search that it ALWAYS fails to register the first key press? When my phone is sleeping and I kick open the keyboard to search in google it never fails that first letter is always gone.
Sent from my SPH-D700 using XDA App
qbking77 said:
The arrogance.......
Click to expand...
Click to collapse
That was exactly what I said after reading the first post. Who would believe anyone at Sprint about anything like this?
Sent from Bonsai 6.0.3
cheapfx said:
Kinda related. Do you guys have the problem when you slide out the keyboard to do a quick "just type" search that it ALWAYS fails to register the first key press? When my phone is sleeping and I kick open the keyboard to search in google it never fails that first letter is always gone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yes LWAYS (just switched to ladscape) lol, sometimes it puts in a letter of it choice without even touching the keyboard.
I've been trying really hard to like this phone. The number 1 reason I'm now using my old Eris until my wife's upgrade date comes in 7 weeks is because the sd card won't mount through usb in Mac OS. Stupid friggin' Samsung! Not to mention the whole Froyo issue. To add salt to all your wounds, I'm running Gingerbread on my Eris. Yeah, my 2 year old Eris is running an OS that should have been on the Continuum months ago. Anyhow, good luck to you all!
Check imnuts's post in the dev section.. Might help change your mind.
Sent from my SCH-I400 using XDA App
I checked all that. I also tried to flash the PBJ kernel, but no luck. After the flash, I had garbled video and needed to odin back. I'm happy with GB running on my Eris for now, and in 7 weeks I will be getting the DI2 when my wife's upgrade date rolls around.
you realize the garbled video thing is only an aesthetic change, right?
The PBJ kernel does that to the video its a known side effect. The post I was referring to is the Froyo Rom and kernel for the Continuum. Give that a try.
http://forum.xda-developers.com/showthread.php?t=1197415
Hahahah you can't own a continuum and not be excited about froyo...
Sent from my SCH-I400 using XDA Premium App
^
lol, so true
jaizero said:
The PBJ kernel does that to the video its a known side effect. The post I was referring to is the Froyo Rom and kernel for the Continuum. Give that a try.
http://forum.xda-developers.com/showthread.php?t=1197415
Click to expand...
Click to collapse
Wow, I completely missed that thread! I'll give it a shot. I tried to return my phone to Verizon today after having it only 10 days. They wanted to screw me out of $35 for a restock fee. I told them where they could put their retocking fee, as that's completely unreasonable considering that I'd have to buy a whole new computer if I wanted to be able to mount the sd card. I'm not switching to Windows! Anyhow, I'm going to sell it on eBay if this new ROM doesn't fix the sd issue for Mac users. Thanks for linking the thread!
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.