Related
Has anyone pulled the phone apart and read the serial number off the chip. We are trying to compair it to the US phone. If you have the info thanks Ours is a Broadcomm BCM4751 (Captivate)
Can I ask how you know the Captivate has a BCM4751 chip? Did you disassemble and see it? It appears that the Galaxy S generic being sold everywhere else outside the US has the BCM2075 chip that integrates BT and FM radios; at least that's what's being reported by others here.
If it were true that the Captivate/Fascinate/Vibrant in the US are using the BCM4751 chip, then it would truly mean these phones have no FM capability at all and there is no prospect of rooting the phone to disable a software level crippling.
This pisses me off. I was willing to forgo the front facing camera of the US versions, but the fact that they (apparently) went so far as to have samsung supply a different GPS chip to eliminate the FM radio so you are FORCED to use some ****e, data intensive service like AT&T radio instead is just outrageous. With the GPS/compass/antenna problems seemingly going ignored by samsung, maybe I won't get this phone at all.
http://www.broadcom.com/products/GPS/GPS-Silicon-Solutions/BCM2075
bugmenever said:
Can I ask how you know the Captivate has a BCM4751 chip? Did you disassemble and see it? It appears that the Galaxy S generic being sold everywhere else outside the US has the BCM2075 chip that integrates BT and FM radios; at least that's what's being reported by others here.
If it were true that the Captivate/Fascinate/Vibrant in the US are using the BCM4751 chip, then it would truly mean these phones have no FM capability at all and there is no prospect of rooting the phone to disable a software level crippling.
This pisses me off. I was willing to forgo the front facing camera of the US versions, but the fact that they (apparently) went so far as to have samsung supply a different GPS chip to eliminate the FM radio so you are FORCED to use some ****e, data intensive service like AT&T radio instead is just outrageous. With the GPS/compass/antenna problems seemingly going ignored by samsung, maybe I won't get this phone at all.
http://www.broadcom.com/products/GPS/GPS-Silicon-Solutions/BCM2075
Click to expand...
Click to collapse
Well the Galaxy S might have the BCM20751 but untill someone tears down the phone and checks with their eyes. The US Captivate was torn down and it is a 4751. But the 4751 doesn't have BT on it. So it could be all the phones have a 4751 with a seprate BT and FM. The 4751 is supposed to be a better GPS unit then the BCM20751 though.
ah, I see it on the Captivate general forum now. The only teardown of the generic Galaxy S that I have seen anywhere is the original one done in Korea a month ago. The pictures from that disassembly are too low-res for me to make out chip IDs. I tried going through their video of the teardown frame by frame too, but again, I can't see the numbers clearly and I saw nothing that resembled a broadcom chip. The Captivate board layout is much different than the Galaxy S, I can't really even see where the broadcom chip should be on it either.....
You're gonna love this. On my Galaxy S, According to jupiter.xml:
<gll
LogPriMask="LOG_DEBUG"
LogFacMask="LOG_GLLAPI | LOG_NMEA"
FrqPlan="FRQ_PLAN_26MHZ_2PPM_26MHZ_300PPB"
RfType="GL_RF_4751_DANUBE"
BrcmRFwildBase="0x1E2D6409"
BrcmRFclkDiv="21"
BrcmRFclkRefHz="26000000"
pps-enable="false" pps-offset-ms="0" pps-width-ns="100"
/>
Click to expand...
Click to collapse
I changed the RfType to GL_RF_2075_BRCM and it just didn't work.
Well thats good. We've accomplished something. But Broadcomm says this is the best GPS they have ever made some hopfully samsung messed up the code and we get a super good GPS.
TBH - I think we may actually be waiting on the driver from Broadcom. Something about Broadcoms reputation as an open source provider is in question.
sjdean said:
TBH - I think we may actually be waiting on the driver from Broadcom. Something about Broadcoms reputation as an open source provider is in question.
Click to expand...
Click to collapse
Yeah it could deff. be broardcoms side. They better fix it.
Is the 4751 used in any other phones just want to see the performance of the gps on this chipset in other devices..
The mere fact that we have Broadcom chip for GPS and not some off brand that I've never heard before like InCrystal really, really points to a serious issue with the drivers/firmware for the GPS. The phone should be operating in MS-Based mode out of the box anyway and I don't know why it isn't. That's not the only problem it has but standalone mode is not what it should be operating in. Nearly all phones GPS' are truly the pits without network assistance.
Lots of phones use Broadcom for GPS, right off of the top of my head, the iPhone is one of them!
Well I really hope it can operate in stand alone mode reasonably well, it should be able to, I dont see why a phone couldn't. agps is mainly just for helping get locks faster at startup and possibly in areas where gps signals are weak but agps is not going to help you out of the city much etc etc.
However yeah I really hope it is a driver issue and if so broadcom and samsung need to get together or its going to drag both their names down.
Kilack said:
Well I really hope it can operate in stand alone mode reasonably well, it should be able to, I dont see why a phone couldn't. agps is mainly just for helping get locks faster at startup and possibly in areas where gps signals are weak but agps is not going to help you out of the city much etc etc.
However yeah I really hope it is a driver issue and if so broadcom and samsung need to get together or its going to drag both their names down.
Click to expand...
Click to collapse
Well like I said there appears to be some other issues besides the fact that they ship in standalone mode which is awful for any phone.. aGPS is the first choice for most phones (Galaxy S is an exception I suppose!) before falling back to standalone mode which does take 2-3 minutes for a fix. Standalone GPS will always take a few minutes to get a lock, a phone certainly isn't going to perform better than a Garmin and I have yet to see one of those in standalone mode lock faster than a phone with aGPS. aGPS is for an initial fix regardless of other circumstances and it's why phones get such snappy fixes.
Ok, but I posted elsewhere that there's a whole stack of a lot happening behind the scenes, which Im not even Samsung know what's going on.
First, even in Standalone mode, you see data being streamed in the initial few seconds, so there must be something in there.
But Ok, we have:
Operation Mode under LBSTestMode - MS Based, MS Assisted, Network Provider or standalone
GPS Plus - Uses the OneXtra servers
Skyhook - Another form of AGPS
SUPL Settings
And irrespective of what you set the SUPL settings to:
Jupiter.xml - Points to both www.spirent-lcs.com as an acSuplServer then points to bcmls2.glpals.com as the LbsServer.
Then under Location and Security, we have the ability to Use Wireless Networks (using WiFi and Cellular Networks). Even if this is switched off, the phone still wants to enable Wireless and see what's out there.
So that's what, 6, perhaps 7 or even 8 seemingly different settings, different methods, of A-GPS.
No wonder the phone is getting confused.
Cya
Simon
sjdean said:
Ok, but I posted elsewhere that there's a whole stack of a lot happening behind the scenes, which Im not even Samsung know what's going on.
First, even in Standalone mode, you see data being streamed in the initial few seconds, so there must be something in there.
But Ok, we have:
Operation Mode under LBSTestMode - MS Based, MS Assisted, Network Provider or standalone
GPS Plus - Uses the OneXtra servers
Skyhook - Another form of AGPS
SUPL Settings
And irrespective of what you set the SUPL settings to:
Jupiter.xml - Points to both www.spirent-lcs.com as an acSuplServer then points to bcmls2.glpals.com as the LbsServer.
Then under Location and Security, we have the ability to Use Wireless Networks (using WiFi and Cellular Networks). Even if this is switched off, the phone still wants to enable Wireless and see what's out there.
So that's what, 6, perhaps 7 or even 8 seemingly different settings, different methods, of A-GPS.
No wonder the phone is getting confused.
Cya
Simon
Click to expand...
Click to collapse
Interesting, so standalone isn't really standalone at all
I wonder if any of the problems are actually being caused by agps especially as a lot of the "fixes" by users were basically changes to the agps.
Curious....., if you google skyhook and you see how samsung and I think even apple used skyhook etc and all the big fanfare etc over it but it seems to be disabled in this phone.
and some of the fixes were to use the google location server right?
(weren't google roasted around the world for wardriving and recording wifi sites and also the data? hehe), now i know why they did it.. for location services I guess... a bit off topic but just now seeing why there were even interested in wifi sites etc.
So.. this broadcom chip... its supposed to be good? can we eliminate the hardware as being a bad gps chipset?
Other things to keep in mind when determining the chip are BT and wifi. The 2075, for example, provides bt 2.1, which rules out its presence on the SGS, unless samsung decided to install multiple bluetooth chips. So, the chip we are looking for provides either bt, version 3.0 and wifi N and GPS, or one or 2 of those 3, which makes the 4751 way more likely indeed. I also don't see a reason to change the internals of the phone.
Gps is a Qualcomm RTR6285 like desire, nexus, some blackberry.
careace.net/2010/06/09/disassembly-of-the-samsung-galaxy-s/
news.danawa.com/News_List_View.php?nModeC=4&nSeq=1742568
sesamee said:
Gps is a Qualcomm RTR6285 like desire, nexus, some blackberry.
careace.net/2010/06/09/disassembly-of-the-samsung-galaxy-s/
news.danawa.com/News_List_View.php?nModeC=4&nSeq=1742568
Click to expand...
Click to collapse
This:
news.danawa.com/News_List_View.php?nModeC=4&nSeq=1742568
must be the korean version (hardware is diferent)
for example :
http://www.careace.net/wp-content/uploads/2010/06/galaxy-s-disassembly-29.jpg
http://www.danawa.com/cms/popup_image.php?url=http://img.danawa.com/cms/img/2010/07/06/14.jpg
Audio codec is the same (wolfson)
Configuration files show tha GPS chip is bcm4751 in european galaxy s (not GPS BT FM BCM20751 or BCM2075) in captive there are photos also.
it REALLY seems like a driver issue. I can get a lock within seconds in MS based mode like all other Android phones with 6 meter accuracy tracking in my car but the performance diminishes after that and the phone requires a reboot for another fix -- IF GPS doesnt cause a lock up trying to get a lock.
Anyone else notice the same behavior in MS based mode?
Sent from my SGH-T959
as i have said in the gps issue thread my settings are as they were from the factory, and at least for now my gps works, in test mode it sees 9-11 satalites, and locks 5-7 of then in about 9 secs, it even suprised me today when i was stood on my staires surrounded by brick walls it managed to get a fix.
this was however not the case with the first one i had, no matter what i tried i could not get a reasonable fix, so it seems to me like some phones are better then others, even thought they are the same phones, this is why i suggested it could be a faulty batch but that is not the case, so i have no idea why this one works and the other never.
if you want the settings: gps is set to oo
application setting
session type: tracking
test mode: s/w test
opperation mode: standalone
start mode: hot start
gps plus: on
dynamic accuracy: on
accuracy: 50
skyhook: off
use pc tool: off
supl/cp setting
sever fqdn: custom
server: www.sprint-lcs.com
server port: 7275
supl secure socket: on
agps mode: supl
hope these can be of use for someone, please note im in the uk.
edit: just tested out my window and got 8 found / 8 locked satalites in 12 secs
Things are getting even more weird...
I was browsing around in the jupiter.xml file shipped in the JP2 firmware and found what I suspect must be a a typo:
arp-supl-reaiding-time-sec = "1200"
Shouldn't that be: arp-supl-reading-time-sec = "1200" ?
With all that mucking about with wads of configuration files and a bazillion places where (conflicting) settings can be made, this doesn't exactly make me feel better about the reliability of AGPS on this device.
edit: nah, probably not a typo (read as 're-aiding', duh) but an unfortunate name choice anyway. At least it appears consistent with what the app is expecting.
Since some think that the GPS hardware (that can't be fixed by software settings) in the Captivate is crap, do you think that Samsung should use hardware from a different GPS provider in their next version of the phone? Does Broadcom have any GPS hardware in other phones that work well? Other than buying a Garmin phone, are there any other phones out there that use "true" GPS, as in one that you would find in a "real" handheld GPS device? I see/hear a lot of people returning their phones strictly because of the GPS not working well.
I'm just wondering if there will ever be a GPS fix for my Captivate, if the hardware is at fault. If it is a poor GPS chip in the phone, there's not much we can do about it, unless the GPS manufacturer updates their driver and they produce some type of software fix.
I updated my Captivate with the OTA update that claims to "fix" GPS performance. It has improved from never getting a fix to providing one relatively quickly. However it loses the fix moving, it loses the fix for NO REASON when stationary (sitting on a surface with a clear view of the sky), goes nearly a minute without updating at times and isn't accurate. People that are using it and saying it works great have never used a real GPS before. The Captivate is useful for location based services at best and hopefully with more improvements navigation.
I compared it side by side with a 9 year old Garmin eTrex and the ancient eTrex blew the Samsung out of the water. Initial fix on the Samsung was faster (thanks to AGPS) but while the Garmin hovered between 6-8ft CEP and the Galaxy S was about 32ft CEP. This makes the Garmin about 30x more accurate in my book.
This was both outside and INSIDE in my home. To the naysayers that say GPS shouldn't be working indoors please take a walk. It depends on the construction of your home. The fact that a 9 year old GPS receiver that was never known for its sensitivity beats the pants off off the Galaxy S really speaks to how much of a terrible joke the phone's GPS is.
If I could I would return the phone. This OTA update was AT&T and Samsung's fix for the GPS and I believe they're going to say it's "done". Because they'll claim to have fixed it already I hold out no hope that this issue will be further addressed and am upset I have the phone. GPS is a basic feature for such a well-spec'ed phone - we shouldn't be thankful when features work - we should demand that they do.
I'd say probably that's all Samsung can do for its crapy implementation of BroadCOM 4751 chip. The GPS chip may be the latest and greatest (newer than the one used in iPhone4, BCM4750) but we are the beta testers for BroadCom/Samsung as the chip is very new (released in April 2010) and never field tested in any devices.
I have no doubt that we will see great GPS performance from this chip later on from other phones or GPS devices. Just not from any of the current Samsung Galaxy S phones. There is only so much they can do to compensate in software for the bad hardware implementation. Ultimately they have to change the board design and/or chip designs to address the real issue. I just can't see Samsung willing to recall millions of existing SGS phones back and replace the motherboard on each one of them.
The update was certainly discouraging. The phone really has no ability to track you correctly on GPS when moving and it loses its lock frequently. Wasn't there a leaked vibrant rom that fixes the tracking part of GPS? Having something like that come to the Captivate is really the only hope we have left at this point.
I'm not a GPS expert, but since basically every phone that comes out these days has a working GPS, I really can't understand how Samsung managed to screw this up. I'm sure that GPS is quite complicated, but aren't the methods and alrogithms for calculating position from the data pretty well established at this point? I don't know why its this difficult for them to get this right. They souldn't have to reinvent the wheel with this; just implement an existing algorith. I wish I knew what is so challenging for them, it seems way to easy for this much time to go by without addressing this properly.
This needs to go in Q&A or General.
TheSopranos16 said:
They souldn't have to reinvent the wheel with this; just implement an existing algorith.
Click to expand...
Click to collapse
It is not the algorithm, it is the chip. For what ever reason, Samsung decided to use the latest and greatest, but untested, GPS chip that was officially anounced only the spring of 2010. Basically, we are beta testers for BroadCom for its BCM4751 version 1.0 sillicon. Of course, adding a slighly bigger or better GPS atenna inside the phone probably will help too but Samsung has to cut corners somewhere (they always do)
I'm also disappointed with the GPS in this phone. I have a standalone Garmin that I bought this summer, but its nice to know that I can use the phone if I don't have my Garmin with me...but I can't rely on this thing.
I had the Nexus One before this and its GPS was great. I used it on a 300+ mile trip between St. Louis and Chicago and it never lost its fix.
I like the Captivate better for its screen, true multitouch and better graphics processor (although I don't really notice a difference there).
I like the Nexus One better for more ROMs (Cyanogen), stock Android, WORKING GPS, first for updates.
IF (and that's a big IF), they can get GPS to be reliable while driving, then I will prefer this phone.
It is very frustrating. I purchased 2 Captivates, one for my wife and one for myself. Both phones are factory still. The wifes gps works excellently, fix within 5 seconds (indoors too).....whereas my gps couldn't find me if I was the only crumb on the plate.
I returned the first phone. The second phone handed to me worked just as my wifes did. Excellent gps fixes. This phone unfortunately had the turn off problem. If the phone was in my pocket for any period off time it would turn off.
I returned this one for a third phone. The third phone stays on but still has the gps problem.
Is it the device, the hardware or the software, you be the judge!
Sent from my SAMSUNG-SGH-I897 using XDA App
drez22 said:
It is very frustrating. I purchased 2 Captivates, one for my wife and one for myself. Both phones are factory still. The wifes gps works excellently, fix within 5 seconds (indoors too).....whereas my gps couldn't find me if I was the only crumb on the plate.
I returned the first phone. The second phone handed to me worked just as my wifes did. Excellent gps fixes. This phone unfortunately had the turn off problem. If the phone was in my pocket for any period off time it would turn off.
I returned this one for a third phone. The third phone stays on but still has the gps problem.
Is it the device, the hardware or the software, you be the judge!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Its still hard to say. Signs are starting to point towards hardware, but it could also just be poor drivers, which will eventually get fixed hopefully.
I've said this in another post.. but these phones are being produced on an assembly line - errors get made - the phones are all using the same hardware.
this is my #5 captivate - the last 2 phones were battery issues, but att replaced the entire phone.. I tested gps before I left the store with the new phone -
everyone needs to understand that there will ALWAYS be problems - It's technology. If your GPS didn't work within the first 29 days, take it back!
There is a reason Samsung is creating a "fix" for the GPS - they aren't RECALLING the phone because of a hardware problem. I will eat my words if the phone gets recalled because of a bad "GPS chip." But for now, if you are within 30 days and you aren't happy, please go return it, test the new phone in the store before you leave!
There is still SOME home for this chipset. Nokia is developing a device with the same chipset. I made a thread in i9000 - Android Development forum with the linux driver source code written by Nokia. We'll have to see. If Nokia releases a device with this chip and the GPS works, we know it's Samsung's fault.
Has anyone ever tried to get a comment from Broadcom about the GPS issues? Since its their chip and there are over a million Galaxy S phones out there, I would think it would be appropriate for them to weigh in on this...
born_fisherman said:
I've said this in another post.. but these phones are being produced on an assembly line - errors get made - the phones are all using the same hardware.
this is my #5 captivate - the last 2 phones were battery issues, but att replaced the entire phone.. I tested gps before I left the store with the new phone -
everyone needs to understand that there will ALWAYS be problems - It's technology. If your GPS didn't work within the first 29 days, take it back!
There is a reason Samsung is creating a "fix" for the GPS - they aren't RECALLING the phone because of a hardware problem. I will eat my words if the phone gets recalled because of a bad "GPS chip." But for now, if you are within 30 days and you aren't happy, please go return it, test the new phone in the store before you leave!
Click to expand...
Click to collapse
You have to realize that the percentage of the bad SGS with GPS issues are too high to be caused by any reasonable manufacturaing defects.
You can't test GPS properly in a store without going through a driving test. Period. The problem with the GPS is not about whether or not you get a lock, it is whether or not the phone can keep an accurate lock on you while driving. Unfortunately, most ppl didn't realize this at all.
Samsung will not recall the phone even if it turns of the GPS chip or motherboard is the problem. It is not some kind of safety issue.
TheSopranos16 said:
Has anyone ever tried to get a comment from Broadcom about the GPS issues? Since its their chip and there are over a million Galaxy S phones out there, I would think it would be appropriate for them to weigh in on this...
Click to expand...
Click to collapse
Broadcom made some small fixes in the driver. That's why with JH7, you can see your phone can lock on to more than 8 satellites now. Old drivers will only allow max lock of 8 satellites and minimal SNR value of 20. New driver allow lock on to more than 8 satellites and minimal SNR value of 10 or so. But unfortunately, it didn't improve moving accuracy.
So when you go to the AT&T store take the phone outside and the phone you are going to walk away with doesn't see any satellites, you should just take it and run?
I'm saying this with experience. I've had 2 phones that didn't pickup any satellites even after waiting 5 minutes.
My current phone immediately saw satellites and got a lock within 45 seconds.
Regardless if you are moving or not, the phone should be able to see satellites - I understand the problem is when you are mobile and keeping the lock, this is not my argument.
my argument is that people are still complaining that they can't get a lock even after the OTA update - Test your phone before taking it home. That's all. Not a big deal if you ask me! If your new LCD TV with HD tuner isn't picking up HD channels, you would bring it back right??
My gps was pretty terrible until I flashed Cognition the first version. Now my gps works amazingly and never has the blue circle of ambiguity. Very happy with the gps performance now. So much that I haven't flashed the cognition that is updated with JH7. Worried it could brea kit haha. might as well try though.
Yeah, the new one (Cognition v2.1) with OTA JH7 in it is pretty bad based on my reading. JH7 is an old firmware. Original Cognition has some files from T-Mo Vibrant JI2 firmware which is newer than JH7.
Our only hope is that the final version of Froyo has some improvement baked into.
Hi I received the HTC Firmware update last week for my HD7 and ever since I've been having lots of issues with connecting to WiFi networks. The two networks I've been having major issues with are my work and home networks.
My first thoughts were that MAC Filtering was enabled hence why I couldn't connect but when I checked both networks don't have it enabled at present (I think I turned it off at home because of issues with my xbox).
However now I struggle to connect to my Work Wifi Network but can at least see it whereas my home network (which my laptop, netbook and xbox can connect to no problem) is not even listed on my HD7 anymore.
Has anyone seen anything similar? This is starting to really bother me now and I'm not seeing many people report it.
OS Version: 7.10.7720.68
Firmware Revision Number: 2250.21.51003.206
Hardware Revision Number: 0002
Radio Software Version: 5.71.09.02a_22.51.50.21U
Radio Hardware Version: A.102.0.D4
Bootloader Version: 5.10.2250.0(132274)
Chip SOC version: 2.2.5.0
Hi there,
I have exactly the same problem. Lost wifi connection after updating my HD7 with new HTC firmware. After few hours I have notice that my mobile can't connect because my router was set to broadcast on channel 13th. After switching router to different channel it connected. I did some test and can't connect to my router if it broadcast on 12th and 13th channel. Strange.
OS Version: 7.10.7720.68
Firmware Revision Number: 2250.21.51003.206
Hardware Revision Number: 0002
Radio Software Version: 5.71.09.02a_22.51.50.21U
Radio Hardware Version: A.102.0.D4
Bootloader Version: 5.10.2250.0(132274)
Chip SOC version: 2.2.5.0
Yep that's helped me narrow it down. I've been through all if the channels on my router and my HD7 just doesn't see networks on channel 12 or 13. Every other channel is absolutely fine.
Need to find the right place to report this to HTC now as it's reproducable.
Here is a post tweeted by XDA
http://www.xda-developers.com/windows_phone/have-you-recently-updated-your-htc-wp7-device-to-7740-if-so-check-this-out/
Hi tfn, this is a different issue and not linked the the MAC Address issue. Neither of us have MAC filtering enabled, this appears to be purely related to the channel on which the wifi is broadcasting.
Thanks for the link though
Another problem I have noticed after HTC firmware update is no jump list in app list!!! Did anybody reported that? I am in touch with HTC but they have rubbish customer services.
Here is the update from HTC they say that it should never have worked on channels 12 and 13 which I've countered. I've also experienced appalling wifi connectivity since the firmware update really considering rolling back.
Thanks for your reply. As mentioned, we recommend that your router is set between 1 - 12, I cannot speculate as to why that worked previously. If this response has resolved your query, and you have no further questions please close this ticket by following the link below. Upon closure of the ticket you will be invited to complete our Customer Satisfaction Survey which should take no more than 1 minute to complete.
2011/11/22 15:47:05
Andrew Westgarth
Reply
Hi, I have read your response and am a little intrigued as ever since I received my HD7 from my operator O2 in November 2010 my phone has had no problems whatsoever in connecting to my home wifi which has been broadcasting on channel 13 for years. So I'm a little confused as to whether the phone had an issue before this latest firmware update. Please could you clarify? Thanks Andrew
2011/11/22 14:58:30
Close Pending
Thanks for contacting HTC regarding your HD7 I understand you have noticed a matter regarding the channels numbers Wifi can connect to. HTC do appreciate your time writing in. This is not a 'bug' in the traditional sense, it is actually the design, our phone will operate on any channels between 0 - 12 (i.e. 1 to 11) This is just the way it is, sorry to say. It will just be a case of making sure the router is set similarly. I hope that this information meets with your requirements. Should you have any further questions please do not hesitate to contact us again. If this response has resolved your query, and you have no further questions please close this ticket by following the link below. Upon closure of the ticket you will be invited to complete our Customer Satisfaction Survey which should take no more than 1 minute to complete.
This is some lousy explanation by HTC. They said that they cannot speculate as to why that worked previously!
1. Because it used to work for god sake!
2. Because in UK we have WIFI broadcasting on 1-13th channels that's why.
I'm just still wondering why my app jump list disappeared after I did a hard reset as they told me to do. I'm not happy neither satisfy with HTC respond.
Hi guys, for some reason i can't connect to my work's hidden wifi after the update. It can see it once i've input the name and stuff, it just fails to connect.
There's not much i can do in terms of diagnosing as it's not administered by myself, but just thought i'd put my 2p in..
Hi there,
I've had the same issues - changing mac address, poor wifi performance, and not seeing channel 13.
I used Zune to roll back to the last firmware, 2250.21.40501.206 and the issues went. Oddly though, when I've updated back to the latest 2250.21.51003.206 firmware. The MAC addres continues to change. I've not played around long enough to comment on if the performance though. I've also noticed since returning to the latest firmware that I can see wireless-n but not connect to it. I'll do a bit more trial-and-error diagnosis on that one tonight and report back
HTC support has been less than useful, foolishly I didn't come here first and went to them. Anyway they advised a soft reset, no joy, then master reset, no joy and all settings etc lost. Said they can't advise how to roll back firmware (which sent me digging with google "aha - it can be done but needs some sort of hack").
the @winphonesupport twitter account have engaged with me and seem interested in the problem. HTC want me to return my phone to be inspected!
Right, came to do my scientific research of exactly what versions did what, and I've banjaxed myself.
Zune advised that another update was available, in spite of my updating since the roll back to 17 Nov and wouldn't let me roll back to what I had on the phone this morning. So... I'm now stuck with either the current wp7 release and current firmware or previous wp7 release and current firmware.
The current firmware has the mac problem, doesn't see ch13 and won't connect to my access point if it's set to wireless-n only, it can see it but everytime gives a connection unsuccessful message when I try to force it to connect. It won't play nice with the AP if it's set to g and n mixed mode... sometimes it'll work, mostly it'll fallback to cellular. If it's set to g only it's fine and dandy. It's wifi performance is poor compared to my nexus one on the basis of it sees far fewer networks at any given location in the house.. I know it's an imperfect measure, but so are signal strenght bars
The previous firmware deffo didn't muck about with the mac address, I'm 95% certain worked on ch13, and I don't know if it worked with wireless-n but it certainly played nicely with the AP set to mixed mode.
That is the replay I had from HTC:
"Hi, having had my technical mentor to look into the lack of the Application Jump List, we can confirm that we have been unable to find this feature on our updated devices. There is not settings for that either. Therefore, unfortunately, it's not possible to add the jump list feature in the device with the current software. What I can do is to raise an escalation requesting this feature back in a possible future update, however, I cannot give you any guarantees this will be added. Regarding the WiFi issue, I still haven't heard back from the relevant department. I hope that this information meets with your requirements, should you have any further questions please do not hesitate to contact us again. If this response has resolved your query, and you have no further questions please close this ticket by following the link below. Upon closure of the ticket you will be invited to complete our Customer Satisfaction Survey which should take no more than 1 minute to complete."
This is bunch of rubbish for me. Application jump list it is an integral feature of WP7.5 and I can't understand how would it disappear??? I'm going to escalate this problem with Microsoft.
Jumplist
I read somewhere that you must have a certain number of apps to activate the jump list feature. I think it was 22?
igor32uk said:
That is the replay I had from HTC:
"Hi, having had my technical mentor to look into the lack of the Application Jump List, we can confirm that we have been unable to find this feature on our updated devices. There is not settings for that either. Therefore, unfortunately, it's not possible to add the jump list feature in the device with the current software. What I can do is to raise an escalation requesting this feature back in a possible future update, however, I cannot give you any guarantees this will be added. Regarding the WiFi issue, I still haven't heard back from the relevant department. I hope that this information meets with your requirements, should you have any further questions please do not hesitate to contact us again. If this response has resolved your query, and you have no further questions please close this ticket by following the link below. Upon closure of the ticket you will be invited to complete our Customer Satisfaction Survey which should take no more than 1 minute to complete."
This is bunch of rubbish for me. Application jump list it is an integral feature of WP7.5 and I can't understand how would it disappear??? I'm going to escalate this problem with Microsoft.
Click to expand...
Click to collapse
Personal background: Associate degree in Laser Electro Optics. 12 years research and development semiconductor manufacturing, 15 years as an EMT, last 10 years as a 911 telecommunicator for Austin-Travis County Emergency Medical Services. 6 of those years as a Training Officer.
The reason for my (cough) resume is so everyone understands I have the technical background and experience to explain the differences between e911 and 911.
Public Safety Answering Point: the local organization tasked with answering emergency request phone calls and dispatching appropriate emergency resources. PSAP's are broken into two types, primary and secondary. The primary PSAP is typically the local police department for city's and the local sheriff's department for unincorporated areas. Some colleges have their own police department and may have their own PSAP. So realistically a person can connect to a different 911 call center depending upon their location within a small geographic area.
Large urban areas typically have secondary PSAP's. The secondary PSAP usually consists of public safety departments not related to law enforcement such as fire and/or emergency medical services (ambulance services) specially trained to send request specific resources dependent upon the emergency. In Austin and Travis County we run 120 thousand EMS 911 calls per year. The police department takes about 2000 911 calls per day.
911: a simple to remember phone number nation wide allowing everyone access to emergency services. No location information is transmitted or received. The PSAP is responsible for determining location by interrogation of the caller. This can a problem if the caller is altered or otherwise unable to give accurate information.
e911: Enhanced 911 was created to ensure location information was transmitted to the 911 call center regardless of the callers ability to give this information. The phone companies are responsible for ensuring this information is available and transmitted to the PSAP. Conventional e911 is effective for landline phones. Cell phones present a completely different problem.
Cell phones are required to meet two different location technology standards.
Phase 1 wireless data: as cell phone use skyrocketed in the nineties, legislation was passed requiring provider's to transmit location data based on the cell phone tower that the cell phone was connected to. While this is helpful, it is problematic due to the sheer size of the area that had to be searched if the caller was unable to give their location.
Phase 2 wireless data: legislation now requires GPS location data be provided by the cell phone company. This location information can be transmitted via the gps chip from the cell phone or via radio location triangulation using the cell towers in the immediate area of the caller.
So in a nut shell, my test of neobuddy's ICS indicated that 911 worked for a sim loaded phone. I did not test the phone with the sim pulled. I also did NOT verify that GPS data was being received by the PSAP.
If 911 works with your phone it should work in any area. I was connecting with two different PSAP's as I live right between two different area's and sometimes connect to one or the other.
Hope this clears some of the confusion. A good explanation is located at en.wikipedia.org/wiki/Enhanced_9-1-1.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Later tators
Sent from my Touchpad using xda premium
thanks a lot. i can confirm cm7.1 has 911 issue.
Sent from my SGH-T959 using XDA Premium App
Developers should also note that as technology continues to advance, video conferencing and text message 911 activation requirements will also be legislated in.
I firmly believe that Google should begin requiring manufacturers make their modem software and audio software open source. Manufacturers should also be required to provide detailed explanations of how the relevant library's interface with the operating system, modems and audio system when activating an emergency call. This is Androids achilles heel. All it will take is one national media event to slam the door on open source operating systems for cell phones. I love the freedom Android provides and the exceptional programing skilss of our developers.
Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Sent from a cell tower to the XDA server to you.
Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Click to expand...
Click to collapse
correct as none had the source code....but for 2.3 onwards rom.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Click to expand...
Click to collapse
made my day.....thanks a lot....will be keeping a close eye on this thread...
My understanding is the issue is only without a sim right?
The 911 issue is with SIM, i don't know about without and im not planning on finding out.
HaloMediaz said:
My understanding is the issue is only without a sim right?
Click to expand...
Click to collapse
It has to do with emergency mode (no dim) and when no compatible roaming network is around (no service) .
Sent from my HTC Sensation 4G
hmmm I havent called 911 in YEARS but it still feels nice to have the ability and this was a nice explantion thank you
MIUI 360 in Asheville NC works fine but not in other areas?
Hopefully they can test the cm9 test ports that are out now.
Sent from my SGH-T959 using xda premium
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Can we get independent confirmation of this? (not that I don't believe you)
Sent from my SGH-T959 using xda premium
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
You typed all that from your touch pad? props
Sent from my SGH-T959 using XDA App
Genesis3 said:
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
Click to expand...
Click to collapse
No, I get that. Just wanted to make sure he verified was all..
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Don't know who you are or where you came from but, you sir may have saved CM development for the vibrant community. Here's hoping and you're the man!!!
Sent from my SGH-T959
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
I just downloaded your kang and running great so far, Thanks for you work !!
Question, is this 911 fix kernel dependent ? ie will it break if I flash another cm7 kernel ?
Thanks again for your hard work !!!
will replacing the kernel break both 911 and gps fixes?
I didn't save anything.
Here's the bottom line, if you're interested in it.
In the original Vibrant device directory there was a set of sources for libaudio -- one of the shared libraries that Android depends on to talk to the audio hardware in the phone. There was no documentation as to where this source came from, but I know where it didn't come from -- it didn't come from a public Gingerbread source for the Vibrant, because there isn't one.
It turns out the library this source builds does not work correctly but exactly why I'm not certain of. One of the problems with debugging this is that I have to have someone else test for me, which means I can't do the sort of testing I like to when I'm tracing things like this (a highly-iterative process that requires that I actually be staring at the debugging screen while doing the deeds that cause the bad behavior) since I can't call 911 myself.. Had the provenance of this code been documented originally (or lack thereof) I would have investigated this possible connection, as I knew the problem lay in the audio connectivity due to myriad kernel and application traces a couple of months ago. I didn't chase that library down and attempt to graft in other related versions because I assumed that the CM people knew what they were doing building that library from source rather than using a cribbed copy from, for example, Froyo or a different gingerbread build off a similar device.
Picking up a different shared library does work. Exactly what the provenance of that library is (e.g. was it grabbed from a binary, was it built from DIFFERENT source, where did it come from?) is also unknown.
Now that I have a working shared library on this device and a non-working one I'm going to compare traces. Maybe I'll get lucky and find the changes necessary in the source that's in the build tree and be able to fix that, at which point I'll know what I've got rather than having a "magic" library from God-knows-where.
Now here's the part that annoys me -- I was all over some of the CM guys about audio problems with other Samsung devices and tried to get access to the "not yet finished" repos because I expected that if I could run down the same sort of problem with ordinary calls in one of the OTHER Samsungs it was rather more likely than not that the same fix would be pertinent in some way on the Vibrant -- simply because manufacturers tend to use the same chipsets and bits, along with APIs, between different devices (it makes it easier for their coders and maintainers to do their jobs.) In addition when I started working one this one of the other protagonists didn't give me jack and crap about the provenance of anything in the device tree and, again, there's no docs embedded in the tree either. You can find the flamewar and slander aimed at me here if you'd like. It turns out I was on the right path; the problem this library allegedly fixed was having to hit <MUTE> twice to turn off and on the audio path. Sound familiar? Well, the pointer to the file that I found and integrated was from a bug logged against the I-9000, a similar phone to the Vibrant, and that library version works. What's changed in it? There's no set of commits logged against the ZIP file provided in that patch; is it a binary lift from a different build (e.g. some factory build) or did someone fix the source?
Who the hell knows because again, it's not documented in the bugtracker. Until I know where it came from and, if there's source, I have access to it, I won't support it. I don't play the "hide the sausage" game when it comes to alleged community coding projects.
I ran into something similar with the Triumph in that there was a different set of parameters coming up from the hardware when a wired headset was plugged in. That was easy to run down because I could do it and see what was going on; it was a literal couple of line change in the code once I found it. There are a couple of places in the libaudio source that might be the cause of this now that I have a reason to look in there, but without being able to easily reproduce the condition that creates the failure (e.g. call 911) it's a guess.
The ICS builds out at present have a different copy of the same compiled library and it also works. I bet that one works too on CM7 as it's fairly close to the metal and thus the API's probably the same (or close) on the Android side but I haven't tried it yet. I've got little reason to since I now have a libaudio.so that's functional on CM7 in any event.
While I've been working on the 911 issue (for a couple months on and off) I also traced down some actual working (properly) GPS libraries that handle the AGPS assist data in the correct way, something that other sets of them do not, and added those too. I also made a few other changes. The battery life is reported to be rather impressive, and the near-instant GPS locks most-definitely are. I can't speak much to the battery life view of the world as of yet but I will be looking at that; that's an area I know quite a bit about (getting these devices to properly go into deep sleep as they should) and the source tree I'm working with does have kernel source.
Any sideloaded kernel that leaves libaudio.so alone (check the zip file to make sure that /system/lib/libaudio.so is NOT present) should be ok, but no promises. Before you go screwing with kernels make sure you want to --you might break GPS performance as a number of the kernels have various attempts to get the GPS to work right and load various libraries along with the kernel itself with varying degrees of success.
I'd be willing to maintain this port but there are two conditions -- first, I expect apologies from the CM people who attacked me, in public, and second, I expect a formal commitment that there will be no more hiding of information. "I don't know" is an acceptable answer provided you run down the person who does -- someone does know because someone DID either import or code the material in question; silence and lack of documenting where things came from and how they came to be is not acceptable. When things go into the codebase through review they damn well ought to be documented. I played "talking to the brick wall" with the Triumph and now the Vibrant and I won't do it if I'm taking on responsibility for maintaining something.
If CM wants me involved in this that's the deal. If not I'll consider setting up a parallel build and set of repos for the bits that have to be changed from the base CM7 Gingerbread branch as I did for the Triumph if there are people interested in it, but my time is not unlimited and in all honesty my taste for working with the CM people and the CM code in general has been seriously damaged, never mind that what I have here seems to work just fine. As such the benefits of continued efforts are likely to be relatively small. If I decide against a continuing effort I will take the build environment that produced that I have now and attempt to set up a manifest so it can be cloned by anyone else who cares to do so, which should take care of others being able to build and run the KANGs from source if they wish. The latter may take a while as I need to find a day when I'm not busy and can put that together (again, lack of documentation doesn't help) and then pull a clean test from a zero base and make sure it builds and runs.
The Vibrant is no longer my daily device but I do still own one, and given its relatively modest resale value I'll probably keep it as a spare device -- it's a very credible phone and with working GPS code it actually locks faster and better than my Hercules does. It's biggest shortcoming is that it's relatively RAM-starved compared to more-modern devices.
Fancy that.
samsung ativ s has a fmradio !!!
-when ik goto diag screen *#9999#
-then goto main menu : *#0
when i scroll arround i see this ( see picture)
and when i plugin a earphone i hear FM noise ....mmmm thats strange ?!?!
is it possible to use it ???
Me!
megasounds said:
samsung ativ s has a fmradio !!!
-when ik goto diag screen *#9999#
-then goto main menu : *#0
when i scroll arround i see this ( see picture)
and when i plugin a earphone i hear FM noise ....mmmm thats strange ?!?!
is it possible to use it ???
Me!
Click to expand...
Click to collapse
It should be possible with the GDR2 update. If you've already got it you should find FM radio in the music hub as long as the phone fully supports it
IzaacJ said:
It should be possible with the GDR2 update. If you've already got it you should find FM radio in the music hub as long as the phone fully supports it
Click to expand...
Click to collapse
i am allready on GDR2 ...but there is NOTHING under music+videos ;-(
...m
megasounds said:
i am allready on GDR2 ...but there is NOTHING under music+videos ;-(
...m
Click to expand...
Click to collapse
Hmm, that sounds weird. I've got radio in my music hub, and I'm also on GDR2, but on a Lumia 920. Could be that there are some incompatibility with the ATIV S. Tried a hard reset? I flashed my Lumia so I got a "free" hard reset
IzaacJ said:
Hmm, that sounds weird. I've got radio in my music hub, and I'm also on GDR2, but on a Lumia 920. Could be that there are some incompatibility with the ATIV S. Tried a hard reset? I flashed my Lumia so I got a "free" hard reset
Click to expand...
Click to collapse
FM Radio requires also a OEM update on top of GDR2 that adds the drivers. This was the Amber update on Nokia phones.
I've recieved ALSO OEM update post GDR2, titled as usual SAMSUNG Firmware update. And still no Data Sense, neither FM
Hmmm, that's weird. I imagine that another OEM update must be coming in order to enable FM Radio. Thanks for the diag screenshots though. Others were telling me that it was missing some board in order to have FM Radio functionality, but this pretty much proves that Samsung still hasn't included a package for it yet.
hardreset
Kopacha said:
I've recieved ALSO OEM update post GDR2, titled as usual SAMSUNG Firmware update. And still no Data Sense, neither FM
Click to expand...
Click to collapse
please do a HARD RESET and you will have data sense available
Kopacha said:
I've recieved ALSO OEM update post GDR2, titled as usual SAMSUNG Firmware update. And still no Data Sense, neither FM
Click to expand...
Click to collapse
What's your firmware version after the OEM update ?
dragonide said:
what's your firmware version after the oem update ?
Click to expand...
Click to collapse
Here it is
Before:
After:
@megasounds, i know mate, but i don't want to lose my games saves, and overall - don't want to reinstall everything exactly now, for basically seeing and using a feature, that SHOULD'VE BEEN available normally after the update, effin Samsung.
Update:
Oh , and btw - also when i enter Test mode (*#9999#)
and then dial through the soft touch keys there *#0
this is the message i get (after GDR2)
megasounds said:
samsung ativ s has a fmradio !!!
-when ik goto diag screen *#9999#
-then goto main menu : *#0
when i scroll arround i see this ( see picture)
and when i plugin a earphone i hear FM noise ....mmmm thats strange ?!?!
is it possible to use it ???
Me!
Click to expand...
Click to collapse
I also have GDR2, and i tried this also but there was no FM noise for me....
---------- Post added at 08:45 AM ---------- Previous post was at 08:28 AM ----------
Kopacha said:
Here it is
Before:
View attachment 2187670
After:
View attachment 2187673
@megasounds, i know mate, but i don't want to lose my games saves, and overall - don't want to reinstall everything exactly now, for basically seeing and using a feature, that SHOULD'VE BEEN available normally after the update, effin Samsung.
Update:
Oh , and btw - also when i enter Test mode (*#9999#)
and then dial through the soft touch keys there *#0
this is the message i get (after GDR2)
View attachment 2187685
Click to expand...
Click to collapse
To enter the menu under GDR2 you have to:
1.) Enter *#9999# in the Diagnosis app
2.) Tap two times on the "Back" Button on the Test Mode screen
3.) Enter *#0 Code
After that the main menu appears:
You will find the FM RADIO TEST when you navigate to:
[1] UMTS
[6] COMMON
[7] FACTORY TEST
Ikkari said:
I also have GDR2, and i tried this also but there was no FM noise for me....
---------- Post added at 08:45 AM ---------- Previous post was at 08:28 AM ----------
To enter the menu under GDR2 you have to:
1.) Enter *#9999# in the Diagnosis app
2.) Tap two times on the "Back" Button on the Test Mode screen
3.) Enter *#0 Code
After that the main menu appears:
You will find the FM RADIO TEST when you navigate to:
[1] UMTS
[6] COMMON
[7] FACTORY TEST
Click to expand...
Click to collapse
Same here. No noise.
"Hardware Tests" app keeps on saying FM Radio is not supported on my device when I try to run a FM Radio test.
I repeat myself : it seems AtivS doesn't not have FM Radio, for the same reason it has not Bluetooth 4.0 like the Lumias
It looks like AtivS Neo will have FM Radio, not that I care about it. AtivS is a great device and Data Sense >>>>> FM Radio for me.
I never used FM Radio on my (stolen :crying htc titan
dragonide said:
AtivS is a great device and Data Sense >>>>> FM Radio for me.
I never used FM Radio on my (stolen :crying htc titan
Click to expand...
Click to collapse
+1 here man.
BUT... why should we always be ****ed in some way by the Samsung's incompetence. My previous phone was Omnia 7, the one before that i8910 Omnia HD - the Symbian one. I also had a Bad (the first "Wave" device i think it was). My point being that the vicious circle of total software related incompetence and post-production software support weaknesses from Samsung. It's always this way with them - they create awesome hardware in terms of engineering (and even in that area they tend to overlook certain aspects - the "beneath the camera heating" of the Ativ, similar with the Omnia 7 before that, now the different BT Stack/FM chipset in our ATIVs). But the software part is where they got dunked. Even the Galaxy devices are filled mostly with a first party bloat and shovelware, with almost all of their "top" features are basically junk and gimmicks.
And that company is struggling for years to create and assemble a dedicated software followers and devs. Even their current line up of software for the ATIV in Samsung Zone is mediocre. Just see how many Photo related apps with a lots of overlapping features they have.
The Omnia HD device didn't had Java 2.0 mobile virutal machine out of the box. The
They had AllShare DLNA app for WP7 - but not for WP8? Reason - unknown. My reason - cuz they are aholes.
The others have an FM radio - they had it before - now - they don't! Reason - unknown. My reason - cuz they are aholes.
They tend to say they support WP, but can't cough up some money for some out-of-the box Navigation solution a-la Nokia style? Reason - Greedy, but don't want to spare a little chunk of those huge revenues the earn, to support a loyal customers like us.
They don't create or distribute (or they don't give em enough marketing impact to be recognized by the devs) in general. Instead of that focusing on all kinda of "dead-by-birth" projects like Bada, Tizen, and so on and so forth..
Kopacha said:
+1 here man.
BUT... why should we always be ****ed in some way by the Samsung's incompetence. My previous phone was Omnia 7, the one before that i8910 Omnia HD - the Symbian one. I also had a Bad (the first "Wave" device i think it was). My point being that the vicious circle of total software related incompetence and post-production software support weaknesses from Samsung. It's always this way with them - they create awesome hardware in terms of engineering (and even in that area they tend to overlook certain aspects - the "beneath the camera heating" of the Ativ, similar with the Omnia 7 before that, now the different BT Stack/FM chipset in our ATIVs). But the software part is where they got dunked. Even the Galaxy devices are filled mostly with a first party bloat and shovelware, with almost all of their "top" features are basically junk and gimmicks.
And that company is struggling for years to create and assemble a dedicated software followers and devs. Even their current line up of software for the ATIV in Samsung Zone is mediocre. Just see how many Photo related apps with a lots of overlapping features they have.
The Omnia HD device didn't had Java 2.0 mobile virutal machine out of the box. The
They had AllShare DLNA app for WP7 - but not for WP8? Reason - unknown. My reason - cuz they are aholes.
The others have an FM radio - they had it before - now - they don't! Reason - unknown. My reason - cuz they are aholes.
They tend to say they support WP, but can't cough up some money for some out-of-the box Navigation solution a-la Nokia style? Reason - Greedy, but don't want to spare a little chunk of those huge revenues the earn, to support a loyal customers like us.
They don't create or distribute (or they don't give em enough marketing impact to be recognized by the devs) in general. Instead of that focusing on all kinda of "dead-by-birth" projects like Bada, Tizen, and so on and so forth..
Click to expand...
Click to collapse
If you want support Nokia is the only company to go... Not Samsung, not HTC... I only bought the Ativ S because it's running WP8 and for 200€ it's steal! And at least with WP8 I have support from Microsoft to get the OS updates
Ikkari said:
If you want support Nokia is the only company to go... Not Samsung, not HTC... I only bought the Ativ S because it's running WP8 and for 200€ it's steal! And at least with WP8 I have support from Microsoft to get the OS updates
Click to expand...
Click to collapse
Same here
Here's the FM Radio test on my T899M. No error messages saying FM radio not supported.
I tried pressing a bunch of random buttons but I can't figure out how to work the test.
dragonide said:
I repeat myself : it seems AtivS doesn't not have FM Radio, for the same reason it has not Bluetooth 4.0 like the Lumias
Click to expand...
Click to collapse
Well, do you know what the SoC is? The MSM8960 SoC has built-in chip with BT4 and FM. No one can remove the chip for fun. Only software support is needed to get it working because hardware it self supports it already. So the very only thing here is Samsung's will and nothing more.
ShocWave said:
Here's the FM Radio test on my T899M. No error messages saying FM radio not supported.
I tried pressing a bunch of random buttons but I can't figure out how to work the test.
Click to expand...
Click to collapse
Like me. I have I8750.
ShocWave said:
Here's the FM Radio test on my T899M. No error messages saying FM radio not supported.
I tried pressing a bunch of random buttons but I can't figure out how to work the test.
Click to expand...
Click to collapse
Same for me, I8750, i don't hear any noise
eshield said:
Well, do you know what the SoC is? The MSM8960 SoC has built-in chip with BT4 and FM. No one can remove the chip for fun. Only software support is needed to get it working because hardware it self supports it already. So the very only thing here is Samsung's will and nothing more.
Click to expand...
Click to collapse
The Bluetooth hardware in the Lumia 820 and 920 is part of the SoC (system-on-a-chip) provided by Qualcomm. The specific version of the Snapdragon S4 used in the Lumia devices is the MSM8960 (dual core version), clocked at 1.5GHz. Specific Bluetooth support is provided by the WCN3660 "Combo Chip", which also provides WiFi and FM radio functionality, and is a piece of companion silicon to the main central processing unit. Both Bluetooth 3.1 and Bluetooth 4.0 are supported by the WCN3660.
Click to expand...
Click to collapse
There are two hardware things missing from the ATIV S from Galaxy S3 !
- WCN3660/80 chip not in the ATIV S hardware spec witch gives you Bluetooth 4.0/FM Radio.
- No hardware LED notification light.
Click to expand...
Click to collapse
pretty sure the lack of FM Radio is due to the absence of the WCN3660 chip (which the Lumia 920 has). Pretty sure that's tue reason why the ATIV S hasn't received Bluetooth 4.0 certification. Likely that the ATIV S will never see FM radio.
Click to expand...
Click to collapse
References :
http://allaboutwindowsphone.com/features/item/15752_Nokia_Lumia_920_and_820_certif.php
http://forums.wpcentral.com/samsung-ativ-s/236214-samsung-ative-s-gdr2-disappointed.html
http://www.wpcentral.com/unlocked-samsung-ativ-s-receiving-window-phone-8-gdr2-update
Sigh.
I do know what SoC is, but there are really many many many strange things in this crazy world.