Hi,
Would like to post all the firmwares/baseband version that are available for the Galaxy S and the problems people have with it
I bought mine from the UK one of the first batch 8gb model
its baseband version is I9000XXJF3
Having some problems with GPS , take quite awhile to lock into the sattelites about 3-5 mins from startup.
Lagging in GPS turn by turn...I am using co-pilot live.
Korean Galaxy S
M110S.DG07.1842.ST (2nd firmware update)
I have slight GPS problems, but not those that are reported by those on here and I think they use a worse GPS chip in Korea do to regulations regarding GPS tracking but I haven't seen any conclusive GPS information on my phone.
I have a slight issue with the FLAC support, either information missing from the tags (I need to actually re-upload the FLAC songs now that there is new firmware, haven't tested since original.)
I can't use Swipe (wah-wah), but it didn't come stock, so I think it's because I couldn't get a legit copy and the international version probably called on code out of the I9000 my phone doesn't have.
Besides that...great success...
Edit: I bought mine from SK first batch of 16GB, hardware differences that I know/suspect: DMB, Cell Radio & GPS chip
Indian Galaxy S
Stock F/W: i9000DDJF3
Updated to JG1...
GPS was fine... never used it much. But I would say a little on the slower side.
Playback was excellent.
-> Though support for subs would have been cool.
-> FLAC playback is amazing. Like the above user, my player too has issues with detecting tags and artist info.
Camera is good during daylight but sucks at night. No flash man!
TwLauncher is cool and all, but lags after quitting an app or a game. Takes time to settle down I guess.
All in all I am happy I updated to JG1 and rooted with MCR!
I started a thread before, but found out it could be a software problem as a lot of demo units' compasses don't work all the time.
S4 has this problem too.
I have the N900W8 device, if that makes a difference.
Fill the poll out above to answer ^, or just comment down below.
Same problem here
nicholaschum said:
I started a thread before, but found out it could be a software problem as a lot of demo units' compasses don't work all the time.
S4 has this problem too.
I have the N900W8 device, if that makes a difference.
Fill the poll out above to answer ^, or just comment down below.
Click to expand...
Click to collapse
Hi, nicholaschum.
I've the same problem. Mi phone is a N9005 (europe free note 3).
I agree that is a software problem, as if you calibrate the compass sensor (*#0*#) it runs without problem until I restart the phone.
I've also tested several demo units at a samsung store and all of them (galaxy s4, note 3, s4 mini) presented the same problem.
The technical service guy told me that they can change the motherboard of the phone, but I doubt that itgonna fix the problem.
There is a lot of threads, here on XDA, but also in other forums reportinf the same problem on several samsung devices...but unfortunately without solutions.
I'm very pessimistic about this problem, due to that we're more concerned about getting new versions of android instead of get this kind of issues fixed.
Sorry for my english!
Mine's accurate in Smart Tools. DBT N9005 4.4.2 NB7
The calibration does seem to get lost upon a reboot, but you do not have to go into the service menu to recalibrate it.
When you are in google maps, simply rotate your wrist (not your arm). Rotate your wrist around and around about 3-4 times (no need for anything more than this so only takes 5 seconds). And then I find everything works just fine.
You shouldn't have to do that after every reboot, but its not too bad if you realise you don't need to go into the service menu and the right movement to recalibrate it quickly.
Bought my note 3 in December and was generally very impressed, well, until I started to record video. One of the main reasons I bought the 3, was I was ahppy owner of the original note, and have always liked Samsung phones, and had read it was a great flagship phone.
I hve notice these horizontal bars that flicker across recordings, its very frustrating, as I use the camera and video a lot. Its more evident in video, but does sometime show up on stills.
https://www.dropbox.com/sh/6x53r9qq0uydvq4/iIInGxTgl1
I originally thought maybe a software update would fix it, but ive now gone from 4.3, to 4.4 and now 4.4.2.. and the problem still happens.
Not impressed! Samsung have asked me to send phone in to be fixed, but Ive asked them to review the vids and assure me it can be fixed, before I send the phone in!
Wifi is the main cause of this problem turning it off solves the problem, and turn off auto network switch aswell in advance wifi settings.
It a software problem as it doesn't do it with other camera apps only Samsung own.
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls.
A HTC spokesperson confirmed the problem to TechRadar, with a recent HTC Service Pack downloaded from the Google Play Store the presumed (but unconfirmed) culprit.
The firm says resolving the problem, which could also be affecting One M8 users, is its number one priority and has told customers to expect the roll out in the coming days.
The statement says: “We are aware that some HTC One M7 (and possibly some M8) users have recently been experiencing audio issues making network calls on their devices.
“WiFi calling does not seem to be impacted at this time. We're working around the clock with our technical teams and partners to resolve the issue as a number one priority.
“We will provide further updates as soon as we can. For anyone experiencing this issue with your HTC One (M7 or M8), you may want to try WiFi calling, and we ask that you please contact your local Customer Care: www.htc.com/support."
Speculation suggests the Service Pack may have caused the instability, but HTC isn’t offering up that information at this stage. As the original report points out, if you haven’t downloaded the update yet, it may be wise not to do so.
jkolner said:
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls..
Click to expand...
Click to collapse
This might explain the issues I have been experiencing since the 5.01 OTA. Call recording has failed with every SW I have tried. Sound quality during calls has crackling and is very poor.
This makes a lot of sense, in the last couple of days mine has had the same problem as was told by HTC that it was a hardware issue, but if this is the case may just hold back and wait for an update.
I've had mine recently producing no audio at either end when answering a call, a reboot seems to sort it out for a while. Hopefully this is all it is and they can sort it out fairly soon, I'm in the middle of buying my first home and trying to talk to lawyers and stuff gets a bit embarrassing when this happens.
Oh my a God.
Thought was mine only!
Sent from my HTC One using XDA Free mobile app
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Pavlova said:
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Click to expand...
Click to collapse
On M8 Original GPE, HTC service pack was installed with 5.01 OTA update. No choice on whether to install or not - it appeared on the list of updated apps.
Apart from sound issues (which I suspect come from HTC/Google disabling features at the Kernel level), I am now experiencing delayed touch response.
Yes, but as I remeber, it was updated also after initial startup. Last update of the Service Pack (on Sense) in Play Store was from 11th December. Anyway, on T-Mo firmware 3.29.118.9 call quality is much better. Also ringtones and notifications are more clear.
Just got a service pack update.
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Andrew149 said:
Just got a service pack update.
Click to expand...
Click to collapse
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
RedBlackPellet said:
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Click to expand...
Click to collapse
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Roadrunner100 said:
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Click to expand...
Click to collapse
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
RedBlackPellet said:
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
Click to expand...
Click to collapse
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Roadrunner100 said:
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Click to expand...
Click to collapse
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
RedBlackPellet said:
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
Click to expand...
Click to collapse
Like you I'm trying to find out what's going on. I can confirm issues with the proximity sensor. I have further issues like skype not gaining access to camera, voice call issues like loud speaker switching on by itself during a call.. etc. What's clear at the moment is that this GPE release is screwed up big time. Like you I've reset the device a few times, but noting changes. Same problems reappear.
I think that finding out more is difficult since there are no specific Forums or threads dedicated to non converted stock GPE's. So finding out more about issues specific to this version is very hard... I have two other colleagues with Original GPE's (mine is a very early device, their's purchased recently) that have the exact same issues, so I can only assume that this is not HW related, but due to Google disabling certain features and getting it badly wrong or HTC's service Pack at fault. In the office there are three other Sense M8's, which don't have any of these issues, but none of them are on Lollipop yet, so I cannot compare until they get HTC's update.
I have a OEM gpe m8, running mrjaydee82's lollipop gpe ROM. I've seen no weirdness besides memory leak.
So when I bought my Nexus 6P I knew I was going to get the latest updates as soon as Google released them. I also expected to find minor bugs because we are getting updates much faster as well.
What I was not expecting is to both, bugs that make for a nearly unusable device and minor annoying ones. For my device the bugs that hit me hard are;
Max Volume Bluetooth Speaker Bug - Most bluetooth speakers are stuck in max volume mode and can't be turned down. Distorts the audio and creates a situation were you could blow out the speaker. Not all speakers are effected.
No LTE On Boot - Annoying to have but "fixable" by putting the device in Airplane mode. Otherwise no Data or SMS until you do and hope your phone doesn't reboot in you pocket while waiting for an important message.
No Phone Calls - You can't make or receive calls. As a result you can't check VM either. No amount of Airplane mode or rebooting will fix it. Neither will the phone service menu.
My concern here is that Google hasn't patched these bugs yet, even after releasing another update to 6.0.1 M. For now I'm fine with downgrading to 6.0.0M but I'm missing out on updates.
To add to insult any ROM build with the 6.0.1 source is effected by these bugs, so I can't even use most ROMs unless I find an older version.
I guess my main question here is this:
Is this normal? Does Google usually go so long without patching the bugs?
Seems really silly to have a phone, but not be allowed to make or receive calls at all and not be able to send SMS or email unless you do a few tricks first. It's a phone. Don't they test these things?
Disclaimer: I already know not all 6P or Nexus devices are effected. That does add to my confusion as they all should be the same exact device.
EDIT: I also wanted to add that when I got the device I could do all these things however even downgrading will no longer allow phone calls. Something is retaining.
Well that's weird mate. I'm on 6.0.1 and have none of these problems.
I was experiencing awful battery life after the latest update but clearing the cache has made a huge difference
Have you tried reaching out to Google? It would be helpful if you could share how you upgraded to 6.0.1? As mentioned above did you clear cache? The more info you can provide; the faster someone can help you.
The Bluetooth volume issue is the only one I have and only on one of my speakers. The others with fine.
Huh, ya 6.0.1 here too and none of these issues are present.