Related
http://forum.xda-developers.com/showthread.php?t=751518&page=10
Good news, hopefully its legit and its software.....
Here's a video of proof. http://www.youtube.com/watch?v=FJ65sS8nbRE&feature=youtube_gdata_player
Update on compass: jhego says it works, also says compass view works in google maps... he also used gps navigation for 15 mind straight without losing the route .... some good looking stuff...
Originally Posted by smashpunks Awesome. Thanks again. This will put my mind at ease and I can sleep well.
Originally Posted by smashpunks Awesome thanks for this update.. one last thing if ya could... check google maps street view in compass mode... no hurry just wondering.. may be a seperate fix but still interesting to know.. Thanks again for your testing...
Man, that's sick! I haven't used that mode before. I can tell you that it works__________________(2007-2008) CID/SIM Unlocked ATT Tilt(2008-2010) Unlocked Blackberry Bold 5.0.0.681(2010- Current) Rooted Samsung Captivate
UPDATE 2: some people are reporting no fix or worse... hmmmm.. what's going on. Half say its getting great locks and others not... maybe its a location thing?
Farkkkkk
If the GPS is fixed in this rom, can we have some crow for the people saying it's not fixable via firmware?
heygrl said:
If the GPS is fixed in this rom, can we have some crow for the people saying it's not fixable via firmware?
Click to expand...
Click to collapse
Agreed. People getting 8 satellites locked..... awesome
http://www.youtube.com/watch?v=FJ65sS8nbRE
6/6 INSTANTLY! 7/7 shortly after... yep, I'd say it's fixed
heygrl said:
http://www.youtube.com/watch?v=FJ65sS8nbRE
6/6 INSTANTLY! 7/7 shortly after... yep, I'd say it's fixed
Click to expand...
Click to collapse
Yes. This makes me very very happy.. now IMO its a perfect device... (hope not speaking to soon but I'd say its fixed also)...
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
but this isnt for the vibrant right? or can it be ported over since they are so close to each other?
Jon C said:
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
Click to expand...
Click to collapse
I'm having the dude test the compass... also even if this exact thing don't work on vibrant.. its proof that its software and fixable
.. that's all I really wanna know...
Update on compass soon....
It's the firmware for the Captivate, which flashes for different radios and so forth. It could be ported, but it would be a lot of unnecessary work.
To be honest, I find the idea of flashing different ROMs to be stressful. I stopped using my jailbroken iPhone because I grew tired of keeping up with flashing and jumping through hoops. I just want Samsung to fix the phone with an OTA, so I can go back to my normal life.
So, we have no word on a fix for the Vibrant. But one can assume that a fix on AT&T will find itself on the T-Mobile device.
Jon C said:
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
Click to expand...
Click to collapse
Your the dude wanting to bail on the vibrant right? Its cool I understand . Hopefully this changes your mind...
Jon C said:
Neat.
Has anyone been able to test out the compass? Whoever is making these videos, could someone ask them to demo Google Sky Map / Street View?
Click to expand...
Click to collapse
Jon C said:
It's the firmware for the Captivate, which flashes for different radios and so forth. It could be ported, but it would be a lot of unnecessary work.
To be honest, I find the idea of flashing different ROMs to be stressful. I stopped using my jailbroken iPhone because I grew tired of keeping up with flashing and jumping through hoops. I just want Samsung to fix the phone with an OTA, so I can go back to my normal life.
So, we have no word on a fix for the Vibrant. But one can assume that a fix on AT&T will find itself on the T-Mobile device.
Click to expand...
Click to collapse
The fix is leaked from samsung .. we will get one too. Point again is its fixable, we never knew this before till now.
Although its still not been said if its 100% working.. could be a start though
No, it's a great piece of encouragement. Still, unless something is said soon, I will probably return my phone until the official fix is out. I can always purchase it again at a later date. It's encouraging to see a leak from Samsung fix the problem, but I'm sure you can understand: $500+ is a lot to spend on a phone.
Keep delivering the good news. Hopefully the Compass has been fixed as well. I really love TouchWiz, and was dreading the possible jump to HTC Sense.
Jon C said:
No, it's a great piece of encouragement. Still, unless something is said soon, I will probably return my phone until the official fix is out. I can always purchase it again at a later date. It's encouraging to see a leak from Samsung fix the problem, but I'm sure you can understand: $500+ is a lot to spend on a phone.
Keep delivering the good news. Hopefully the Compass has been fixed as well. I really love TouchWiz, and was dreading the possible jump to HTC Sense.
Click to expand...
Click to collapse
I can understand your view.
For me it is also encouraging that samsung really is trying .
This is encouraging news. Hopefully it's true and I can quit obsessing with it
This gives me a damn hard-on.
My phone locked & rebooted* itself twice today, while trying to use GPS. And I was in Mountain View, even - buncha bull****.
-bZj
*when it does this routine, it resets the volume on the system (thus the startup sound) to maximu8m - makes me even angrier!
heygrl said:
If the GPS is fixed in this rom, can we have some crow for the people saying it's not fixable via firmware?
Click to expand...
Click to collapse
don't recall anyone saying it couldn't be fixed - can you point us at one?
the consensus opinion has been no one knew whether it was firmware or software
and btw, while this is good news, we're not totally certain this is a permanent "fix"
if it's still working in 2 or 3 weeks for the folks that installed it, then it might be considered a fix
larryccf said:
don't recall anyone saying it couldn't be fixed - can you point us at one?
the consensus opinion has been no one knew whether it was firmware or software
and btw, while this is good news, we're not totally certain this is a permanent "fix"
if it's still working in 2 or 3 weeks for the folks that installed it, then it might be considered a fix
Click to expand...
Click to collapse
Regardless its getting 8 satellite locks for a lot of people .. that's never happened before ... this is a leak so not even official. So official may even be better ....
I was very concerned about the compass as I wasn't convinced that could be fixed via firmware basd on what I saw in the GPS service screens (seemed laggy even straight from the device). Eugene373 posted a fix to GPS for rooted phones here ://to.ly/5TFy (add http to follow the link). I installed it and it fixed both GPS and compass for me personally. This for me was proof positive tha there will be an official Samsung fix released to solve this issue.
K
larryccf said:
don't recall anyone saying it couldn't be fixed - can you point us at one?
the consensus opinion has been no one knew whether it was firmware or software
and btw, while this is good news, we're not totally certain this is a permanent "fix"
if it's still working in 2 or 3 weeks for the folks that installed it, then it might be considered a fix
Click to expand...
Click to collapse
ignored
sfsdf
down8 said:
This gives me a damn hard-on.
My phone locked & rebooted* itself twice today, while trying to use GPS. And I was in Mountain View, even - buncha bull****.
-bZj
*when it does this routine, it resets the volume on the system (thus the startup sound) to maximu8m - makes me even angrier!
Click to expand...
Click to collapse
Mine has been doing it for a couple of weeks and I finally got fedup with this routine and called TMO and complained. I'm getting a replacement Vibrant in 3 days or so but I'm not holding my breath on it working any better really although I hope that it won't freeze and reboot at least. This official fix can't come fast enough because this GPS caused freezing and rebooting is really getting to me at this point.
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
Im so sick of DK28 and all of its issues. I just went back to DI18 Epic Experience. So much more smoother. No lag. No cant hear when calling glitch. No gallery problems. No force closes. No random reboots. NOTHING!! Just a nice smooth phone that I can use and that is reliable!!!!!! Im done with the whole leaked version thing. I wont flash my phone again until the official froyo comes out for the Epic. Good night DK28!!
I did. Well I was an idiot and bricked my phone and was lucky enough to get it replaced without the $100 deposit (thank you Dustin). I planned on rooting and flashing asap until I literally was about to connect the usb cable into my pc. For now I am staying stock. I may Z4 it to get rid of some stock apps but I am taking a break from the ROM/Modem flashing and theming stuff. My new Epic is running WAY better now then my old one was on DK28. I mainly wanted flash 10 but once I got it I never used it. I thought it would be great for watching HULU in between class or when I take the bus to work but my battery life was only 4hrs and I never could fix it no matter what recommendation I tried. Now my battery lasts all day again. We will see what I do in another week or 2 though lol.
youngpro83 said:
Im so sick of DK28 and all of its issues. I just went back to DI18 Epic Experience. So much more smoother. No lag. No cant hear when calling glitch. No gallery problems. No force closes. No random reboots. NOTHING!! Just a nice smooth phone that I can use and that is reliable!!!!!! Im done with the whole leaked version thing. I wont flash my phone again until the official froyo comes out for the Epic. Good night DK28!!
Click to expand...
Click to collapse
Did you try the "Truly Epic Rom" I was on the same boat as you, and was about to switch till I gave that ROM try....Its rocks!!! and its silky smooth!!
Erica8123 said:
I did. Well I was an idiot and bricked my phone and was lucky enough to get it replaced without the $100 deposit (thank you Dustin). I planned on rooting and flashing asap until I literally was about to connect the usb cable into my pc. For now I am staying stock. I may Z4 it to get rid of some stock apps but I am taking a break from the ROM/Modem flashing and theming stuff. My new Epic is running WAY better now then my old one was on DK28. I mainly wanted flash 10 but once I got it I never used it. I thought it would be great for watching HULU in between class or when I take the bus to work but my battery life was only 4hrs and I never could fix it no matter what recommendation I tried. Now my battery lasts all day again. We will see what I do in another week or 2 though lol.
Click to expand...
Click to collapse
Yeah I hear ya!! Hopefully they will come out with the official froyo so I can actually have a decent phone with froyo that actually works without all the head aches.
youngpro83 said:
Im so sick of DK28 and all of its issues. I just went back to DI18 Epic Experience. So much more smoother. No lag. No cant hear when calling glitch. No gallery problems. No force closes. No random reboots. NOTHING!! Just a nice smooth phone that I can use and that is reliable!!!!!! Im done with the whole leaked version thing. I wont flash my phone again until the official froyo comes out for the Epic. Good night DK28!!
Click to expand...
Click to collapse
From what I've experienced, there really aren't any issues with DK28 that aren't already in 18. Every Rom I've tried recently (Quantum, Bonsai, Midnight) has been silky smooth and I haven't gotten any FCs, calling glitches or anything you've experienced.
I just think its odd that people blame all their problems on the build. Its understandable if everyone is having the same issues as you, but when you're the odd one out, doesn't that mean you're the one thats the problem?
riceknight said:
From what I've experienced, there really aren't any issues with DK28 that aren't already in 18. Every Rom I've tried recently (Quantum, Bonsai, Midnight) has been silky smooth and I haven't gotten any FCs, calling glitches or anything you've experienced.
I just think its odd that people blame all their problems on the build. Its understandable if everyone is having the same issues as you, but when you're the odd one out, doesn't that mean you're the one thats the problem?
Click to expand...
Click to collapse
Well when Im looking through the threads and Im reading the titles that people post who are experiencing the same issues as I am and many others on this site, then I would assume its the build and not just one particular person. Not to mention its a leak.....Its not even an official release so for you to sit here and claim that it is more STABLE than the STOCK BUILD or anywhere close, you sound like a fan/groupie of DK28 rather than a person who is speaking from knowledge. There are more people on this thread than me who have been experiencing more than a few issues with the "leaked" froyo. When dialing out and sometimes the call not going through or you can talk but cant hear is a KNOWN ISSUE with the "BUILD" that even the devs are curious about. Never had an issue like that on the stock BUILD. Anyways like I said F DK28.
For me, Quantum 2.1 is more stable than the stock ever was. It's not fanboy speak, it's that we know what we're doing and it's pretty obvious that Froyo is much faster. Maybe Froyo doesn't work as well on older revisions of the Epic hardware, I know I got mine in December rather than when it was first released. But for me, it is much better than the crappy stock rom which is bloated with Sprint garbage.
Do we all care about if someone flashes back. It seems like posts like this keep clutterng up the forums. It makes it really difficult to search. Who cares u went back to stock. Mod please delete thread.
Sent from my viperROM rooted ext4 epic 4g
So what your telling me is that the pre-release version of a ROM is more buggy and less stable then a final product. Got ya.
MedicStuder said:
Do we all care about if someone flashes back. It seems like posts like this keep clutterng up the forums. It makes it really difficult to search. Who cares u went back to stock. Mod please delete thread.
Sent from my viperROM rooted ext4 epic 4g
Click to expand...
Click to collapse
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.
Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.
Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
snowmanwithahat said:
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.
Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.
Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
Click to expand...
Click to collapse
Exactly! I have been flashing my phone since I had my Touch Pro so I know all about leaks and the benefits they bring to a hardcore phone user like myself. I enjoyed DK28 for sometime now and it seems like the more people do to it the more some things stop working. I just got to the point where I was just tired of constantly updating the ROM with the newer version because the dev "FIXED" another DK28 issue. I appreciate all of their hard work. I even donated to a few of them because they made me love my Epic again with all these new EXT4 and no journaling mods. My phone has never been so fast and snappy......But at the end of the day when I need to use my phone I dont need it to do a random reboot or even worse miss a call because the other person cant hear me which is a very common problem some users are having. Although now that I am back on the DI18.......Its hard to find all those cool mods that I have been so used to. lol. Decisions decisions.
snowmanwithahat said:
Get off his case. He's sharing his experience on DK28 vs DI18 in case some DI18 users were still on the fence as to whether or not they want to jump to a buggy 2.2.1 build. There's a lot of hate going around these forums and it's the response like what you just gave thats give people a poor outlook of our community.
Personally I've experienced both sides of the argument. I went with DK28 first and killed my gps, flashed back to DI18 and went with ACS for 3 weeks. Got sick of 2.1 and really wanted some 2.2 features back so I went with midNIGHT and a 2.3 theme.
Thanks for your thoughts OP, I share the same concerns but found some of the buggy issues of DK28 to outweigh the bugs and lack of features of DI18. I actually think its funny though because a buggy DK28 makes me want a real stable froyo build even more than being on eclair made me want a 2.2 update lol
Click to expand...
Click to collapse
If he wanted to share his experience then he should have searched for one of the other threads that has already been started about this topic instead of starting yet another one.
Sent from my viperROM rooted ext4 epic 4g
youngpro83 said:
Well when Im looking through the threads and Im reading the titles that people post who are experiencing the same issues as I am and many others on this site, then I would assume its the build and not just one particular person. Not to mention its a leak.....Its not even an official release so for you to sit here and claim that it is more STABLE than the STOCK BUILD or anywhere close, you sound like a fan/groupie of DK28 rather than a person who is speaking from knowledge. There are more people on this thread than me who have been experiencing more than a few issues with the "leaked" froyo. When dialing out and sometimes the call not going through or you can talk but cant hear is a KNOWN ISSUE with the "BUILD" that even the devs are curious about. Never had an issue like that on the stock BUILD. Anyways like I said F DK28.
Click to expand...
Click to collapse
Way to get defensive without backing your claims. There are also much more than a few people who aren't experiencing the same problems you are. I've never even heard of the dial out bug nor experienced it in any flash. If you don't want to work to get a good beta experience, why are you even on XDA and flashing in the first place? I find that DK28 isn't perfect, but its still leaps and bounds better than stock.
You have problems? Try to get them fixed, reflash or ask some questions on the Q&A. Don't just blame it on the build. Basic rule of thumb? If majority don't have the same problem you're having, double check what you've done or reflash.
NYYFan325 said:
So what your telling me is that the pre-release version of a ROM is more buggy and less stable then a final product. Got ya.
Click to expand...
Click to collapse
These are Samsung builds so I don't thinks there's really a difference between a alpha/beta/RC and a final build!
juise said:
These are Samsung builds so I don't thinks there's really a difference between a alpha/beta/RC and a final build!
Click to expand...
Click to collapse
Riiiiiiiiiiiight
To use the OS "windows" as an analogy for you...
How do you think the bugs get found and fixed? When Vista (or any OS for this matter) was in Beta 1 / Beta 2 stage... guess what? It had MORE BUGS / glitches then the version that was released to the public. When it went to RC stage, it had less bugs then the beta. When it went to RTM (the version released to the public) it had less buts the beta and the rc.
Nothing will ever be 100% bug free, but to say you dont think there is a difference between alpha/beta/rc and final builds is very VERY naive of you.
P.S. if you were being sarcastic, my bad lol
Actually MS betas don't work that way, they release betas and continue to fix the bugs they are allowed to fix and run 100000 regression scripts and if any regressions are found they actually unfix the bug and attempt a different fix for it.
Eventually they end up releasing a few release candidates and end up picking the least buggy of these to promote to RTM.
I have a number of friends who work as SDE/Ts for MS, this is how it goes.
Also -- it's very possible that an updated code branch has more bug fixes than bugs introduced on smaller projects (like Android customizations) versus something huge like Windows.
riceknight said:
You have problems? Try to get them fixed, reflash or ask some questions on the Q&A. Don't just blame it on the build. Basic rule of thumb? If majority don't have the same problem you're having, double check what you've done or reflash.
Click to expand...
Click to collapse
Seriously? Don't you think if the build was so perfect, Sprint would have released it by now?
Fact: There are bugs in DK28. Congrats that you aren't experiencing them.
I personally experience the calling out bug, but not the GPS bug. My accelerometer was jacked up for a while when I moved to DK28 until I found a good workaround (and no, the simple "recalibrate in the terminal method" didn't work). HOWEVER, the benefits to me are greater than the disadvantages of having these bugs in DK28.
This is a forum - the OP was sharing his experience. What kind of forum would it be if no one was able to share there personal experiences with the phone we all have?
Cut the guy some slack.
abrognlie said:
Seriously? Don't you think if the build was so perfect, Sprint would have released it by now?
Fact: There are bugs in DK28. Congrats that you aren't experiencing them.
I personally experience the calling out bug, but not the GPS bug. My accelerometer was jacked up for a while when I moved to DK28 until I found a good workaround (and no, the simple "recalibrate in the terminal method" didn't work). HOWEVER, the benefits to me are greater than the disadvantages of having these bugs in DK28.
This is a forum - the OP was sharing his experience. What kind of forum would it be if no one was able to share there personal experiences with the phone we all have?
Cut the guy some slack.
Click to expand...
Click to collapse
So... you had a bug and you looked around and found a way to fix it. Congrats. Thats exactly what my advice was.
I've had FC problems on prior Rom flashes before. I reflashed and took my time to fix it. My phone runs smoothly now. I could just Odin DI18 and blame it all on DK28, but like most people, I took the time to get it right. If it were an OTA upgrade, you could blame it on the build, but its a Rom, so take the time to get it running and like you said yourself, there are plenty of people to help with good workarounds.
I don't understand all the pandering and hand holding thats encouraged in these forums. You encourage whining and then complain when there is so much of it. How about encouraging these same people to go out and improve their phones instead of coddling them?
+1 Theres so many resources and answers theres no reason to not have a sweet running,personalized non buggy phone on dk28
Hi everyone,
Some of you may already know me (the new guy to rooting ). For those who don't, I'm completely new to rooting and roms (just started a day ago).
I've tried two different roms so far other than stock (Urban and ERA, currently on ERA). and one of the biggest things to come to my eyes is the keyboard lag fix..
This fix is so significant it's crazy. I mean I used to hate the Epic keyboard because of this. I never knew that I could simply root and have a rom that would have fixed this issue until now.
I'm really curious why Samsung didn't bother to apply this fix? Did it sacrifice anything? Was it simply to make the keys more sensitive?
Just curious about everyone elses thoughts.
HanMan5000 said:
Hi everyone,
Some of you may already know me (the new guy to rooting ). For those who don't, I'm completely new to rooting and roms (just started a day ago).
I've tried two different roms so far other than stock (Urban and ERA, currently on ERA). and one of the biggest things to come to my eyes is the keyboard lag fix..
This fix is so significant it's crazy. I mean I used to hate the Epic keyboard because of this. I never knew that I could simply root and have a rom that would have fixed this issue until now.
I'm really curious why Samsung didn't bother to apply this fix? Did it sacrifice anything? Was it simply to make the keys more sensitive?
Just curious about everyone elses thoughts.
Click to expand...
Click to collapse
Honestly I think it was a matter of mkasick finding a better way to deal with key press events. He did some serious reasearch, and being a kernel dev I can see he really put some effort into it. I think mkasick just understood the hardware better than the guy who originally wrote the code
Sent from my SPH-D700 using XDA Premium App
thomasskull666 said:
Honestly I think it was a matter of mkasick finding a better way to deal with key press events. He did some serious reasearch, and being a kernel dev I can see he really put some effort into it. I think mkasick just understood the hardware better than the guy who originally wrote the code
Click to expand...
Click to collapse
I think you just hit the nail on the head! It's amazing what an enthusiast programmer can and will do that someone just earning a paycheck will overlook, intentional or not.
I agree with you there, but it makes you wonder exactly how the hell something so BAD and so CENTRAL to the device can make it out the damn door! Not only that, but it doesn't get fixed for multiple releases! *boggle*
I tell ya, I generally avoid rooting, just because that's my preference, but if the next update doesn't fix the skips, I'm gonna have to do it.
sleebus.jones said:
I agree with you there, but it makes you wonder exactly how the hell something so BAD and so CENTRAL to the device can make it out the damn door! Not only that, but it doesn't get fixed for multiple releases! *boggle*
I tell ya, I generally avoid rooting, just because that's my preference, but if the next update doesn't fix the skips, I'm gonna have to do it.
Click to expand...
Click to collapse
Yeah, I bought this phone and not the Evo one of the main reasons being the keyboard. I was more than dissapointed with the crappy keyboard problems. If I knew there's a fix if you root, I would have done this months ago lol.
Mkasiak, huge thanks.
Thanks the the Devs here, the current fixes added to the Gingerbread build really make the Epic shine.
It's fast, stable, has great battery life, a useful keyboard, and gtalk working.
It really makes me happy that I decided to choose this phone over the EVO back when both these phones were top of the line.
sleebus.jones said:
I agree with you there, but it makes you wonder exactly how the hell something so BAD and so CENTRAL to the device can make it out the damn door! Not only that, but it doesn't get fixed for multiple releases! *boggle*
I tell ya, I generally avoid rooting, just because that's my preference, but if the next update doesn't fix the skips, I'm gonna have to do it.
Click to expand...
Click to collapse
Awww, just go ahead and root and fix it! and while you are at it, fix your GPS too! I waited a long time to root while on Froyo, but I finally did, but went unrooted to get the OTA to GB (don't really know why) and couldn't stand being unrooted. I wanted control back that only root could give me. Even my wife asked me to root her phone to keep certain apps from killing her battery.
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.