Macehammer
New member
Yes. I am.
BringGo Master Thread
- Thread starter Eranthe
- Start date
Yes. I am.
bkmitchy600
New member
Cool. Thanks for the response, Macehammer.
I disagree. I don't think this is an "Android" issue, and I'm not going to get into a rant about Android versus iPhone. Both are good, and there are plenty of people that prefer one or the other.
I have about 50 apps downloaded to my Galaxy S3. Even when the phone is upgraded to a new version of Android, I've never gotten an 'incompatible' message. I don't know exactly how the Playstore determines compatibility, but it is likely a combination of acceptable Android versions and some minimum hardware requirements, rather than long lists for each app of specific handsets.
Consider the Verizon Galaxy S3. When I first checked the Playstore, it was available, meaning my device was compatible. 3 days later, my Android version was upgraded from 4.1.1 to 4.1.2, a minor version upgrade. After that, Bringgo was no longer compatible or available to be purchased through the Playstore. Same hardware, same screen size, same amount of memory.
None of my other apps stopped working because there was a minor version upgrade. My bet is that Bringgo set up specific version criteria for compatibility, including probably most Android versions from 2.3 through 4.1.1, but failed to edit that list to include 4.1.2 when it was rolled out.
By the way, these Android version upgrades aren't a surprise and don't happen overnight. I get a version upgrade to the OS about every three or four months, and their release is quite well publicized on sites like Androidcentral.com.
Engis, up until Bringgo, was purely an iPhone programmer, and only played in that sandbox with Apple 'rules', which are different than Android. If they want to play in the Android space, they just need to pay attention. I don 't think it'sthat complicated, and thousands of other developers do just fine keeping their Android apps compatible.
So I do think this is a Bringgo problem. Android is an afterthought to them, and they don't understand yet how to work in the Android space. They could easily 'release' compatibility for 4.1.2. If it crashes, then pull it back. It is a little different animal than 4.2.2, which is on the Nexus devices, which does have some major changes to the OS. But that's no different than the major version upgrades to iOs.
Very curious that Bringgo is totally silent on here. Nobody from that company is participating on here (and yes, they know about it, if not from me ---I've emailed them about it --- then they should know from Chevy.) This could be a great resource for them, but they're totally ignoring it.
I have about 50 apps downloaded to my Galaxy S3. Even when the phone is upgraded to a new version of Android, I've never gotten an 'incompatible' message. I don't know exactly how the Playstore determines compatibility, but it is likely a combination of acceptable Android versions and some minimum hardware requirements, rather than long lists for each app of specific handsets.
Consider the Verizon Galaxy S3. When I first checked the Playstore, it was available, meaning my device was compatible. 3 days later, my Android version was upgraded from 4.1.1 to 4.1.2, a minor version upgrade. After that, Bringgo was no longer compatible or available to be purchased through the Playstore. Same hardware, same screen size, same amount of memory.
None of my other apps stopped working because there was a minor version upgrade. My bet is that Bringgo set up specific version criteria for compatibility, including probably most Android versions from 2.3 through 4.1.1, but failed to edit that list to include 4.1.2 when it was rolled out.
By the way, these Android version upgrades aren't a surprise and don't happen overnight. I get a version upgrade to the OS about every three or four months, and their release is quite well publicized on sites like Androidcentral.com.
Engis, up until Bringgo, was purely an iPhone programmer, and only played in that sandbox with Apple 'rules', which are different than Android. If they want to play in the Android space, they just need to pay attention. I don 't think it'sthat complicated, and thousands of other developers do just fine keeping their Android apps compatible.
So I do think this is a Bringgo problem. Android is an afterthought to them, and they don't understand yet how to work in the Android space. They could easily 'release' compatibility for 4.1.2. If it crashes, then pull it back. It is a little different animal than 4.2.2, which is on the Nexus devices, which does have some major changes to the OS. But that's no different than the major version upgrades to iOs.
Very curious that Bringgo is totally silent on here. Nobody from that company is participating on here (and yes, they know about it, if not from me ---I've emailed them about it --- then they should know from Chevy.) This could be a great resource for them, but they're totally ignoring it.
Macehammer
New member
You are missing my point, I am not debating Android over iPhone... I too am uninterested in the difference.
Yes, Engis coded the app to only work on certain handsets. This is because the more handsets it allows to run the app, the harder it is for them to support and debug $$$ wise.
The problem supporting the device on android, as compared to iPhone is that their are really only 2-3 phones you are gonna load this on with iPhone. Those are the 4, 4s, and the 5.
The android space there are probably well over 150 android phones since the iPhone 4 was released, and they all have variable differences in their hardware, and Android OS version. That's a monumental amount of work with little-to-no payoff for most devices.
Heck, even big players like Netflix limit the amount of support they provide to certain android devices, and they have a much higher return-on-investment than Engis ever will....
Yes, Engis coded the app to only work on certain handsets. This is because the more handsets it allows to run the app, the harder it is for them to support and debug $$$ wise.
The problem supporting the device on android, as compared to iPhone is that their are really only 2-3 phones you are gonna load this on with iPhone. Those are the 4, 4s, and the 5.
The android space there are probably well over 150 android phones since the iPhone 4 was released, and they all have variable differences in their hardware, and Android OS version. That's a monumental amount of work with little-to-no payoff for most devices.
Heck, even big players like Netflix limit the amount of support they provide to certain android devices, and they have a much higher return-on-investment than Engis ever will....
laborsmith
New member
Macehammer, if I understood your posts, you are not running your Apple based BringGo out of the box. Which is fine and somewhat akin to those members who do not run their Sonics out of the box in that intake and exhaust systems, wheels, brakes and tires, even transmission mods are made and the results are positive. But where you may be comfortable with modding electronics other may not.
I have made a preliminary assessment (less than 54 hours in the game) that the Exhibit 4G was certified as BringGo friendly based on 4Gigs of internal memory but the version T-Mobile is shipping has but 2Gigs. The T-Mobile persons I have worked with assure me my handset has 4Gigs and I can't see but 2Gigs because I have downloaded too many apps!
If you go to the T-Mobile site and check the Exhibit 4G specs you will see internal memory is 4Gigs, which is close to the 3.5Gigs BringGo requires to download and install their program. But 2Gigs is less than either 4Gigs or 3.5Gigs unless I have forgotten basic math and so it is.
I am not bashing Apple or Android. I may be bashing T-Mobile or more likely Samsung but I do not know enough about this to say for sure. All I know is T-Mobile says their Exhibit 4G has four gigs of internal memory where in reality it has two gigs and BringGo requires 3.5 gigs of internal memory: so I am up the river with no paddle.
What is frustrating is I can not depend on the BringGo list of compatible handsets so I can not say that since this product will not work give me that product and I will pay the difference because that product also may not work.
Iphone is fine if your carrier uses it but as far as I know T-Mobile does not.
I do not know but I do suspect there is a difference in appearing to be one handset over another and having actual amounts of internal memory. How do you trick a two gig device into presenting as a four gig device when the extra gig or two are physically necessary?
Coherent and understandable suggestions are welcomed. And switching to a carrier who uses Iphone may, after all is said and done, be the answer.
Laborsmith
I have made a preliminary assessment (less than 54 hours in the game) that the Exhibit 4G was certified as BringGo friendly based on 4Gigs of internal memory but the version T-Mobile is shipping has but 2Gigs. The T-Mobile persons I have worked with assure me my handset has 4Gigs and I can't see but 2Gigs because I have downloaded too many apps!
If you go to the T-Mobile site and check the Exhibit 4G specs you will see internal memory is 4Gigs, which is close to the 3.5Gigs BringGo requires to download and install their program. But 2Gigs is less than either 4Gigs or 3.5Gigs unless I have forgotten basic math and so it is.
I am not bashing Apple or Android. I may be bashing T-Mobile or more likely Samsung but I do not know enough about this to say for sure. All I know is T-Mobile says their Exhibit 4G has four gigs of internal memory where in reality it has two gigs and BringGo requires 3.5 gigs of internal memory: so I am up the river with no paddle.
What is frustrating is I can not depend on the BringGo list of compatible handsets so I can not say that since this product will not work give me that product and I will pay the difference because that product also may not work.
Iphone is fine if your carrier uses it but as far as I know T-Mobile does not.
I do not know but I do suspect there is a difference in appearing to be one handset over another and having actual amounts of internal memory. How do you trick a two gig device into presenting as a four gig device when the extra gig or two are physically necessary?
Coherent and understandable suggestions are welcomed. And switching to a carrier who uses Iphone may, after all is said and done, be the answer.
Laborsmith
I'm an Android user, but regardless of Android or iPhone, if Chevrolet intends to put the MyLink Radio in more and future model cars, the company making BringGo had better pull their heads out and get Android fully supported. (soon) To not better support Android "before" this was released is a complete failure by Chevrolet and BringGo. Word will spread about this and whether it's difficult or not to support Android is going to be irrelevant to customers. And the silence from them is not a positive sign.
It's my hope that they recognize this and get significantly more support for Android. I would consider updating to a newer Android phone, but there are only certain models available, and of them, only a few are acceptable to me. But despite this, the BringGo folks wouldn't answer my questions on which Android phones are supported (and from which carrier), nor if they have any plans to support more. There's been precious few replies here with supported Android models, so at this point, BringGo is an epic failure for me, and I suspect many others.
It's my hope that they recognize this and get significantly more support for Android. I would consider updating to a newer Android phone, but there are only certain models available, and of them, only a few are acceptable to me. But despite this, the BringGo folks wouldn't answer my questions on which Android phones are supported (and from which carrier), nor if they have any plans to support more. There's been precious few replies here with supported Android models, so at this point, BringGo is an epic failure for me, and I suspect many others.
laborsmith
New member
Only Sonic and Spark MyLink versions use BringGo for nav, for the other models nav is a $795 option plus $3 a month for access to real time traffic updates.
But ^ is correct and Chevy should not forget nav problems using MyLink is what people will remember not a particular flavor of MyLink.
Laborsmith
But ^ is correct and Chevy should not forget nav problems using MyLink is what people will remember not a particular flavor of MyLink.
Laborsmith
When I bought my Sonic back in October, the upcoming release of Bringgo - promoted by the dealer - was one of the main reasons that tipped me to the Sonic over the Accent or the Fiesta. And Chevy's promos at the time (and still now) tout BOTH Android and iPhone compatibility. Nobody said "We're only really sure it will work on an iPhone. It may or may not work on Android." Given that I had a Galaxy S3, Samsung's flagship phone and, at the time, the best selling smartphone on the market, I think I made a safe assumption (although now erroneous in hindsight) that if any Android phone would be supported, it would be the S3.
So I got bring go update done today on my car, and they stuffed the whole thing up. Somehow deleted Pandora, and only gave me the Brazil, west Europe, and china versions of the bring go app. They acted as if they never heard of it before, which is weird because a previous reply here indicated they had already performed one. Sutliff Chevrolet in harrisburg. I have an appointment to drop my car off for the day tomorrow, and if they can't get it right then I'll be at a loss of what I should do. 2013 sonic with my link and 1.4 turbo automatic. It was weird though, because it still had my Bluetooth pair to my cellphone stored in the radio and from what I understood I would have to redo that, but whatever.
Btw, I had to show them the pi # from earlier in the thread (the one that ends with the a I showed them.) And then they said they could do it.
Btw, I had to show them the pi # from earlier in the thread (the one that ends with the a I showed them.) And then they said they could do it.
Last edited:
sonic24740
Zippy
that's weird they didn't do it right.
Well, reading the other thread about bringgo in here about it being released or whatever, apparently this has happened to someone else so they should be able to fix it. He said the flash "went wrong" in the other thread. Fingers crossed they fix it tomorrow. I already have the app running on my "non-supported" phone thanks to a device ID switcher in the android marketplace, works fine for an app that shouldn't be supported.
key1cc
New member
laborsmith
New member
While I was at the Chevrolet dealer, the service manager started talking about the inconsistency of this update rollout and he showed me the Bulletin: the pod cast training for the dealers is Thursday. What?! This has been out in updated form for over a week and the training for how to do it will be Thursday! No wonder we have trouble finding compatible phones, Chevy hasn't even gotten around to training it field staff about the program.
I will decide tomorrow whether to take a chance with the phone I have or go backwards to the previous version of what I have. Since I want the phone almost exclusively for BringGo I expect I will downgrade but not happy doing it.
Chevy, you have enough management people working in Korea, send them over to engis to push them to improve their rollout, too many of your targeted customers are being left out in the cold because they have phone sets that are too new for BringGo.
OnStar anyone?
Laborsmith
I will decide tomorrow whether to take a chance with the phone I have or go backwards to the previous version of what I have. Since I want the phone almost exclusively for BringGo I expect I will downgrade but not happy doing it.
Chevy, you have enough management people working in Korea, send them over to engis to push them to improve their rollout, too many of your targeted customers are being left out in the cold because they have phone sets that are too new for BringGo.
OnStar anyone?
Laborsmith
Last edited:
laborsmith
New member
I am sympathetic but I would go for the boss of Chevrolet who has the power to get something done.
Laborsmith
Laborsmith
I spoofed the device manufacturer info on my phone and was able to download and install all the maps I'll need for an upcoming trip...assuming it works out at the dealership tomorrow, I'll be giving this thing a thorough run for it's money in NYC in about 5 days....if it works, I'll give ya'll an update, but as of now, it seems to be working fine without being able to hook up to the car.
Isambard
New member
Nexus 4 on Android 4.2.2 is still unsupported, so for the meantime I am just running Google Maps Nav through Bluetooth for turn by turn. Once all this funny business with MyLink dies down and the dealerships are trained, then I'll do the upgrade. For now I'll just cross my fingers and hape that BringGo gets their act together Especially with the next major Android version (Key Lime Pie) supposedly coming in May.
Especially with the next major Android version (Key Lime Pie) supposedly coming in May.laborsmith
New member
Following is the BringGo response to my query about me waiting or going ahead and trading my current Samsung Exhibit for the older model it replaced.
Thank you for contacting BringGo Customer Support.
We will review the list of supported phones periodically to ensure that the app supports the widest range of phones possible. It is not possible to support certain phones due to limitations with the hardware itself or the interfaces used.
The list may change in the future as new devices have been tested and approved for compatibility. We do need to test each phone device for compatibility to ensure that the app works as intended.
The list of supported devices on the following link and shall be updated periodically:
The older version has a 3.5 inch screen, my current has a 3.7 inch screen, the old version is Gingerbread 2.3.3 and my current is 2.3.6 and the old version has half the memory of my current version, shooting a hole in my theory that internal memory resource was the problem.
I think I'll review Macehammer's spoofing suggestions.
Laborsmith
Thank you for contacting BringGo Customer Support.
We will review the list of supported phones periodically to ensure that the app supports the widest range of phones possible. It is not possible to support certain phones due to limitations with the hardware itself or the interfaces used.
The list may change in the future as new devices have been tested and approved for compatibility. We do need to test each phone device for compatibility to ensure that the app works as intended.
The list of supported devices on the following link and shall be updated periodically:
The older version has a 3.5 inch screen, my current has a 3.7 inch screen, the old version is Gingerbread 2.3.3 and my current is 2.3.6 and the old version has half the memory of my current version, shooting a hole in my theory that internal memory resource was the problem.
I think I'll review Macehammer's spoofing suggestions.
Laborsmith
I used an app called "Device Spoofer" It was $1.50 from the app store. I changed my device to several of the supported devices on the phone and it still wouldn't show up in the play store ON MY PHONE. So, I went to the play store website, where it was still listed as incompatible, but my device showed as one of the samsung models that are actually compatible. I bought the app and hit the install button. The little popup window comes up, I was able to select my phone! It downloaded to my phone, it's about 103mb download first from play store, then 600 just for the base maps, and a few 100 more for each state you want, or you can download the whole country for a few gigs. I chose to pick the 3 states I would actually be driving in in the next few weeks. Your Mileage May Vary, but that's what worked for me.
