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.
Related
I bought a Galaxy S from Bell Canada in august. Made the update to JH2 trough kies. Had the GPS bug (locked fine, but was sometimes way off (1-3 streets off)).
I told Bell. They said they didn't know any GPS problem affecting their device.
I tried many differents things, but I still had the problem so I recorded tracks with both my Hero and my Galaxy S to prove that the Galaxy S has a bug.
I called Samsung. I told them that I had a bug with the GPS. They said that they were not aware of any GPS bug affecting the GT-i9000M (the canadian version).
I went to Bell and asked for a repair. Seems like I was the first in Canada to report the problem because they told me again that there was no report on such problem, so it must be a specific problem with my device. They give me a Samsung Omnia II for the time of the repair. Worst touch screen ever, almost useless compared to a Galaxy S.
My device came back "repaired" (what they did was a factory reset and allegedly a ROM update, but it was JH2 before and after the repair, so this is bull****). In short they did nothing but loose my time.
Of course, I still have the exact same bug, the repair guy probably didn't even test it.
I call Bell again. Shock! Horror! They admit that there is a problem with ALL Galaxy S. Finally! Not that I told them since August... And it's not only in Canada, according to the tech support agent, it affects devices from all around the world. And that I shouldn't worry because the update to 2.2 will be released everywhere in the world in November and will fix that. Great!
Oh wait. The update to 2.2 is already released in some parts of Europe. I am not even sure that it fixes the GPS. At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
+1
Two thumbs up for your effort. Hopefully canadian sgs froyo update comes on November like the rest of the world....
Sent from my GT-I9000M using XDA App
Great job on the audio recording too, nice move
Good job. Please keep us posted when froyo released.
Sent from my GT-I9000M Ver. UGJH2 using XDA App on Bell Mobility Network
sorry to say but some tech reps are more informed than others because they take time to do their own independant research. One tech i talked to barley knew a thing about the galaxy S, while another rep was fascinated by it and couldnt wait to get their own. Mine is in repair for faulty internal SD, lets hope froyo will fix the gps, as i didnt send it in for that issue.
Those who know something about the Galaxy S (and other smartphones) are the so-called "data" support.
1-877-328-2123 (choose language and then select the first option in the menu)
I agree data support are the only ones that know anything. I called customer service like 5 times before they gave me someone that knew anything, ala data support.
Sent from my GT-I9000M using XDA App
Well, I think that of course the response is "we haven't heard about any bugs". It's business -- they aren't allowed to admit to anything unless an order comes from the top to announce that a certain bug .. or a few bugs have been found. I haven't seen any admittals from Samsung that SGS is slow, laggy and the 2.2 update is crap. Or that there are any bugs at all. That would crash sales.
Same here
I got pretty much the same info. been through the same ordeal. I don't think I can last til the end of november for a maybe fix that might not fix anything or might get pushed back to january or even february or??? At least now with them endorsing the issue it should not be as hard to fight for an exchange, maybe get a Z.....
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
sbcmp3 said:
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
Click to expand...
Click to collapse
Well that's not the GPS bug I am talking about. My GPS locks just fine (as already said). The problem is that it is not always precise. But anyways xtra1.gpsonextra.net seems farther aways (mesured by ping times) than north-america.pool.ntp.org, so it should not fix anything.
And north-america.pool.ntp.org works just fine on my HTC Hero.
thurtig said:
Well, I think that of course the response is "we haven't heard about any bugs". It's business -- they aren't allowed to admit to anything unless an order comes from the top to announce that a certain bug .. or a few bugs have been found. I haven't seen any admittals from Samsung that SGS is slow, laggy and the 2.2 update is crap. Or that there are any bugs at all. That would crash sales.
Click to expand...
Click to collapse
Well the thing is, when you know that there is a bug and you hide it to increase your sales, you do not deserve any customers.
zorxd said:
At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
Click to expand...
Click to collapse
I am very curious as to what software you used to record that call?
You didn't use a Korean Galaxy S (SHW-M110S) by any chance, did you? Because its firmware has a native call recorder function that I would die to get my hands on, but unfortunately Samsung doesn't allow international Galaxy S users to flash to the Korean firmware Send me a PM if you know how to force flash it!
dillovic said:
I am very curious as to what software you used to record that call?
You didn't use a Korean Galaxy S (SHW-M110S) by any chance, did you? Because its firmware has a native call recorder function that I would die to get my hands on, but unfortunately Samsung doesn't allow international Galaxy S users to flash to the Korean firmware Send me a PM if you know how to force flash it!
Click to expand...
Click to collapse
I am a proud user of the Asterisk PBX, which I installed on my OpenWRT router . I used that to record, not my cell phone.
zorxd said:
Well the thing is, when you know that there is a bug and you hide it to increase your sales, you do not deserve any customers.
Click to expand...
Click to collapse
All companies do that. Focusing on all the bugs takes the attention from the good to the bad. Basic stuff. All the companies that made you any of the things you own operate on the same principle. This is business. This is life.
But this does not mean they are not working hard on fixing the issues -- believe me, they are. Our comments and complaints are very important in bringing these things out. Stuff that gets discussed here on XDA dev is _vital_.
sbcmp3 said:
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
Click to expand...
Click to collapse
Interesting- this is one fix I hadn't seen before. Where did you read about it?
zorxd said:
Oh wait. The update to 2.2 is already released in some parts of Europe. I am not even sure that it fixes the GPS. At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
Click to expand...
Click to collapse
thats rite live in the uk and upgraded ma android to 2.2 using kies reg mod and guess what it made the GPS worst. it wont go two streets without losing gps signal. theres no hope i heard it may even be a hardware fault.
Ok I havnt seen or heard anyone talk about this. But I've had this problem with my slide out keyboard since I got the phone. I don't know if I'm typing to fast for it or what. But ill type an entire text then read what I wrote and random letters will be missing from words. This never happend on my g1 I had before I got the epic. I actually catch it when it does it now and its really annoying. I traded the phone for a new one at sprint and it did the same thing even before I rooted and installed a rom on it. Anyone have same issue? I'm really reconsidering this purchase because of this.
Sent from my SPH-D700 using XDA App
Ya. This happens to alot of people due to Samsung not knowing how to code.
Sent from my SPH-D700 using XDA App
It appears that the input from the keyboard is faster than the phone can process. It's quite annoying.
Yep, I think it happens to almost everyone. Ever since I switched to the gingerbread keyboard it seems to happen less often, but I have no real evidence to back it up.
abrognlie said:
Yep, I think it happens to almost everyone. Ever since I switched to the gingerbread keyboard it seems to happen less often, but I have no real evidence to back it up.
Click to expand...
Click to collapse
the gingerbread keyboard is an onscreen keyboard. the op was talking about the slide out hard keyboard.
world of difference.
austin420 said:
the gingerbread keyboard is an onscreen keyboard. the op was talking about the slide out hard keyboard.
world of difference.
Click to expand...
Click to collapse
He isn't wrong technically..as remember, disabling Swype seems to alleviate the issue..so if he is not using Swype and using the Gingerbread keyboard instead..the physical kb would work better lol
Ok so ive seen this thread and another one regarding this issue.. Questions so the solution to miss keys on the hardware keyboard is disabling swype meaning using the standard android keyboard instead? OR deleting swype?
And im surprised there hasnt been a fix for it? but i think once we have official froyo source maybe it will be fixed?
Ok well I just disabled swype and will install gingerbread kb when I get home. Even the slightest bit of change would be better than what I'm dealing with now. Is a pretty good excuse to exchange my phone for a new one every week though haha. I'm surprised the guys at sprint had never heard of this happening. But they had also never seen adw launcher and the unlock screen I had either...
Sent from my SPH-D700 using XDA App
I disabled swype and just got the GB keyboard on my stock 2.1 rooted custom kernal rom and all i must say i really like this GB keyboard.
I will test the hardware kb today and see if it fixes some of the lag
This is also one reason I deleted Swype from my ROM,but I still get missed keys all the time on the hardware keyboard.
gTen said:
He isn't wrong technically..as remember, disabling Swype seems to alleviate the issue..so if he is not using Swype and using the Gingerbread keyboard instead..the physical kb would work better lol
Click to expand...
Click to collapse
Exactly. I should have been more specific and said that by disabling Swype it seemed to help. Several other places in the forum have mentioned that tip.
I definitely understand that the OP was talking about the physical keyboard - I've never had a problem with any on-screen keyboard missing keystrokes.
I never even use the on screen keyboard. I'm no good with it honestly. I had the g1 before this then an lg rumor before that; all of which had keyboards so its all I am used to. Maybe I should learn the onscreen one a little more but isn't the point of having a hardware one is to use it? But disabling swype seems to help slightly and after I post this imma look into installing the gingerbread one. Thanks for the advice though I really appreciate it. Also I am relieved to know I'm not the only one with the issue. I plan on keeping this phone for awhile so hopefully it gets completely resolved in the very near future.
Sent from my SPH-D700 using XDA App
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
They must also fix
1)Choppy browser with and without flash.....
2)Random freeze of the gingerbread launcher...
slateac said:
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
Click to expand...
Click to collapse
I think it was posted that the reboot fix was coming, but not the loss of data.
Maybe I am just a lucky one, but I have had Nexus S since release and have only had a "random reboot" once; and no data signal loss issue AFAIK like Engadget has described. I have owned three Nexus Ss.
There are other issues, though, making it clear 2.3 is not bug free.
fchipm said:
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Click to expand...
Click to collapse
and they didn't even give us XDA credits
Perhaps 2.4 is coming sooner than planned and the fixes will be implemented in that? Just a wild guess.
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
i'm hoping they fix the quirky back button as well. that thing is driving me crazy!
I recommended the nexus s to my girlfriend, but seeing all these issues are making me regret it :\ there are no fixes/workarounds?
Sent from my SPH-D700 using XDA App
aaaaaand... 10char
Update: Huzzah! Just got a note from Google saying: "All of the issues described in the post are resolved and will be fixed with an OTA that will go out soon." Feel free to start mashing that "system updates" menu item.
Click to expand...
Click to collapse
that was fast.
Weird. I haven't had a single one of the issues described in any form. However, the browser issues do make me angry.
Glad there is a hotfix on the way (for the issues mentioned, that is, not necessarily the browser issues)!
The only issue that regularly bothers me is the vanishing ringtone one. It's not exactly critical from a utilitarian standpoint, but I think it's stupid that I should have to root and move files around my phone in order to set a custom ringtone. Still, I'm far too happy with pretty much everything else to switch.
I think one major sticking point with the Nexus S is that we have a fairly lengthy list of at least semi-common issues, but in several cases it's not clear whether those are hardware- or software-related. This is troublesome because the latter may be reasonably expected to get fixed in OTAs, while the former will probably only ever be resolved through workarounds, if at all.
I would be very pleased if Google were more transparent about what it's working on, or at least aware of, even if they (understandably) don't want to commit to fix dates. As a user, just knowing the basic nature of these problems and that they are being acknowledged would go a long way towards improving customer satisfaction in my book.
SooSpecial said:
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i read that there will be an ota update, but (maybe its a noob question) if your rooted will you still receive the update, and if so will it unroot the phone??
Fix the GPS!!!!!
Fix the keyboard: http://www.youtube.com/watch?v=RUZdvr6Pdjk
Discussed more in depth at this thread: http://forum.xda-developers.com/showthread.php?t=932838&page=13
Thought i'd post these here. Others can post theres as well. If I get any answers I'll post those here also.
1. Are there plans to fix the gps issues on the epic? Or is it simply hardware related?
2. Why did samsung choose the rfs file system?
3. What is Samsung's corporate position on open-source software development?
Sent from my last samsung phone using tapatalk.
I have a question for you and other members. What exactly is the gps issue? Mine works perfectly on my epic on 2.1 and 2.2.1
Sent from my SPH-M900 using XDA App
rgregg504 said:
I have a question for you and other members. What exactly is the gps issue? Mine works perfectly on my epic on 2.1 and 2.2.1
Sent from my SPH-M900 using XDA App
Click to expand...
Click to collapse
Some people have gps issues such as accuracy i believe. some don't
Oh ok thanx just curious because me and my wife both have the epic and both are fine.
Sent from my SPH-M900 using XDA App
I have a problem where the gps doesn't lock at random. Usually a battery pull clears the problem. Accuracy is usually within 30 feet or so.
Rfs? It was the thing they had at the time. On new phones they are using ext4.
Supposedly 2.2.1 official on Monday will address GPS.... we will see... not sure the point of that Q&A at this time (the next few days) as we have yet to see what they listened to for the build they are dropping in a few days. I honestly think he wants our input on matters other than software/hardware complaints that are well known. I think that will be useful if everyone is contented with the 2.2.1 release, Its not a bad thing to have a suggestion box, IF the issues are addressed somewhat promptly...
I asked:
Does Samsung intend to address the hardware keyboard issue that causes the phone to miss keystrokes?
and
one other question that I completely forgot.
Edit: strike that, just remembered.
Is Samsung going to offer firmware updates for the Camera which is available in the settings menu of the leaked 2.2 rom??
rgregg504 said:
I have a question for you and other members. What exactly is the gps issue? Mine works perfectly on my epic on 2.1 and 2.2.1
Click to expand...
Click to collapse
Gps locks fine and quickly, but then loses lock after 5-15 minutes. You have to manually turn the gps on and off again to get it to re lock.
And I asked because it was supposed to be addressed in an update that came our months ago but still happens for a lot of us.
aleph23 said:
Gps locks fine and quickly, but then loses lock after 5-15 minutes. You have to manually turn the gps on and off again to get it to re lock.
And I asked because it was supposed to be addressed in an update that came our months ago but still happens for a lot of us.
Click to expand...
Click to collapse
Dont forget you cant lock GPS with wifi or 4g on.
Well there must be enough wrong with GPS for them to mention it as one of the main features of the udpate to happen monday... hopefully they will fix your issues, I have got my GPS to 2 meters on DK28, but actually have yet to leave it on for an extended period of time, dont really use Nav, I know my city from jobs... and dont really like leaving that on, Ive disabled it since they first came in phones... tinfoil hat and all...
HW Keyboard!!! If it does not improve, I will take it in for service. I got a replacement like Jan 3, for my OG that I had since launch week, and aside from the screen fail, my original never dropped keys... not that I can remember... it also seems to be getting worse, and since January I have not gotten that much faster at typing on it to make a difference that way... but I HOPE its software... else I may end up with another TEP claim.
muyoso said:
Dont forget you cant lock GPS with wifi or 4g on.
Click to expand...
Click to collapse
I lock with wifi on.
My question is what is samsung's plans for future os updates for the epic?
Sent from my SPH-D700 using XDA App
From the sound of it, Svetius at captivate says that xda will be filtering the questions before they go to Sammy.
Sent from my last samsung phone using tapatalk.
I can probably easily tell you how they will answer it or at least summarize it..
aleph23 said:
1. Are there plans to fix the gps issues on the epic? Or is it simply hardware related?
Click to expand...
Click to collapse
We are working hard to isolate and fix this issue..
2. Why did samsung choose the rfs file system?
Click to expand...
Click to collapse
We chose RFS for its reliability (they made RFS themselves they are not going to say any bad about it)
3. What is Samsung's corporate position on open-source software development?
Click to expand...
Click to collapse
Samsung is committed to open source
---
Those will be your answers..in a fancier manner..
As for GPS locking , I lock just fine..I noticed Google Maps gets stuck here and there but if I use any other software there is no issue...
aleph23 said:
I lock with wifi on.
Click to expand...
Click to collapse
Generally not for long. Leave WiFi on for 2 days, without ever shutting it off. Then try getting a lock. Promise you won't be able to.
I've never had problems locking on to GPS
The problem that I share with many others is that the GPS will randomly stop connecting with satellites after 10-20 minutes of use. Sometimes a lot sooner than that. It'll reconnect after about 2 minutes, but its really annoying when you're using google nav.
I've tried using GPS status and I can see that it has a great signal, but it won't connect to a couple of sats at random times. Very buggy.
AFTER the update, if it happens, those with GPS issues should get an ALL GPS thread like the 2.2 one... it seems like a real clusterfuk as it stands, and theres no clear proof that its software, or a crappy GPS radio, and thats the end of the story. After the update, which claims to address GPS, those with GPS issues need to compare notes, and figure out as best as possible what is hardware limitation, what is software, what is user error. As stated above, other software besides google maps should be tried as well, in case there is something weird happening with that... I dont use GPS much, so I wonder why this issue keeps popping up so much, and people dont collaborate enough on solving the issue. After that best GPS fix ever thread popped up, I Odin'ed to DI18, and did all the steps, even considered going to DG27 or whatever to be extra retentive, but once I got all the way up to my rooted, rom'd setup, got 2 meters, or maybe 1... thats all I bothered with. I understand those that use their epics as a tom-tom need much higher standards of connectivity.... hopefully you wont be disappointed.
I hope so too. I work at several different locations and user the phone as nav. Gps locks fine, just loses lock soon enough, often at critical times...
Sent from my last samsung phone using tapatalk.
got this from a "sprint rep" on their forums
TiNy-2nz -
I apologize for the frustrations associated with the current issues with the GB release... Please know that we are aware of many of the issues people are experiencing and are working with HTC to resolve them. Although I don't have a time frame now, they will be sending out a patch to resolve issues associated with your device.
SOOO take it for what its worth and maybe there is a hair of hope .....
TInY
hope this is true.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
I had a prompt to download an update today. I skipped cuz I'm still holding out for root on this update that I'm on. I'm not actually having issues other than I can't root...
sent from my 2.3.3 unrooted piece o ****....
I was also prompted for an update today, after just being prompted for the GB update the other day. I was hoping maybe they were being true to their word and unlocking the bootloader.
It was a rather lengthy update process with two reboots involved.
tiny2nz said:
got this from a "sprint rep" on their forums
TiNy-2nz -
I apologize for the frustrations associated with the current issues with the GB release... Please know that we are aware of many of the issues people are experiencing and are working with HTC to resolve them. Although I don't have a time frame now, they will be sending out a patch to resolve issues associated with your device.
SOOO take it for what its worth and maybe there is a hair of hope .....
TInY
Click to expand...
Click to collapse
Kiduno99 said:
hope this is true.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Not to sound like a douche, but I think it's pretty obvious that Sprint & HTC plan on releasing an update that would fix the problems presented with the GB update.
There was the 4.22 update,GB
Then the 4.24 update,GB fix,
Are you guys saying there is a 3rd update being pushed?
Sent from my PC36100 using XDA App
I'm wondering the same thing...I've already had two updates. I took both of them because I like my evolution stock, only reason I ever rooted my hero is because Sence made it sluggish.
Sent from my SPH-P100 using Tapatalk
at this point in time....i am not confident that we will have any sort of solution in the near future, we will simply have to deal with this horrible android version of gingershitbread, i never tought id hate the awsomeness that is an EVO , but currently...i kind of do, clearing user data, resetting,done it all, it still sucks arse and glitches half the dam time,its horrible, if id have known i would have stayed with stock 2.2 (not because of root but because it actually friggin functioned better)
I waited a couple weeks and did the rooted stock rom, 4.24
Have had no issues after a full week of use.
Sent from my PC36100 using XDA App
the more i think about it you think he said that just to shut me up and so the sprint forums dont get filled up with posts about it ??? I dunno; like the corp store told me; "as long as you can make and recieve calls there is nothing wrong with your handset"
IT suxx to be stock its like having a maseratti that only goes 55MPH