I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?
Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.
The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box
ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S
3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.
I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.
I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny
Related
EXCHANGE IT!
sorry! I'm just really excited, I wasn't getting any GPS signal so I took it back to the corporate store, saved a quick ti backup to my sd, swapped the phone and BAM! I now get perfect GPS locks within SECONDS of activating maps!
also! I had some weird Facebook errors, only few would sync, wouldn't sync all the time etc. etc. NO PROBLEMS ANYMORE all my contacts sync and match up perfectly.
seriously the phone is now like it should be.
I asked the corporate rep (same guy I've been going to for years) he told me that the first batch of captivates went out with corrupt firmwares, but they weren't bad enough that they would have noticed anything wrong (or they did and chose to ignore it...) anyways, round two of the phone is fixed up and great!
My firmware: 2.1-update1
my baseband: I897UCF6
my kernal 2.6.29
that is the LATEST firm/base/kernal and If you can't get your phone to OTA update to it, I HIGHLY suggest you make a Ti backup and exchange it, you'll be out a few hours of your life but the phone will WORK
I bought my Captivate on launch day, and I've been running the same firmware/baseband/kernel since day one. You were misinformed about an initial batch of bad firmware.
That is the same Firmware, Baseband, and Kernel everyone has...
You were misinformed.
Expect your GPS to work for a few days then crap out.
Same here. Got it on release day and have the same firmware. I have not noticed any issues yet.
jmreed97 said:
That is the same Firmware, Baseband, and Kernel everyone has...
You were misinformed.
Expect your GPS to work for a few days then crap out.
Click to expand...
Click to collapse
well my GPS didn't work out of the box but i just figured it was because I was in the mall. but as soon as I got the new one, it started right up.
facebook sync wouldn't sync properly either, and now it is syncing 100% fine
the phone would randomly shut down, it's been 4 days no shut downs
I dunno, I waited to post this to make sure it wasn't a fluke, maybe its just mine but it seems legit and my launch day device was definitely NOT 2.1-update1, I checked it right before I turned it in and it was just 2.1
yup, same here, got it on launch day, same info, but no dice on a consistent GPS lock.
you just got a bad phone dude. my friend got a launch day phone and his ate his external sd card, had a dead pixel, and would random shut off. just one of those thangs!
I got mine on launch day and have same firmware and everything. We didn't all happen to get a few bad phones. Samsung has manufactured phones that are bad from the beginning and they won't admit to it yet. This is worse then antennagate with apple.
Atleast then all you had to do was stick a piece of tape on the corner and voila! no problems. I wish fixing the issues with this phone were that easy. But we have the brightest minds at xda trying to fix our issues and they are still stumped by gps... nearly a month after release.
And even if xda minds can fix the issues... I find it extremely frightening that part time developers that do this for fun can fix issues faster then samsung can even admit to it(lag fix for example..) The more and more I think about this whole issue... the less I feel confident about Samsung as a mobile manufacturer.
V DidDy 210 said:
my baseband: I897UCF6
Click to expand...
Click to collapse
Are you sure it is I897UCF6, or is it I897UCJF6 ? Mine has a J.
Mine has JF6 also.
:facepalm:
everyones GPS works for the first day or two.
Can anyone confirm OP's post? It is possible that Samsung released a corrupted batch. At this point I almost want to unroot my Captivate and exchange it for a new one. I paid $500 for this and it's not working.
Speaking of which can someone PM an UNROOT tutorial for the Captivate. I'll be a guinea pig and go exchange my phone for a new one to see if this fixes any issues.
I returned my Phone yesterday and can confirm the GPS issue still exist on the replacement. Also, according to the sales rep this was from a newly shipped batch, so take it for what its worth.
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market and it can't even get a GPS lock in under 10 minutes.
IsaiahC said:
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market and it can't even get a GPS lock in under 10 minutes.
Click to expand...
Click to collapse
The Gps problem is a known problem for last few months, so i wouldnt be holding my breath for any fix to be coming out anytime soon. I am sure they will get around to it eventually if they do. Seems to me they are more concerned getting galaxy s phones out in multiple markets
IsaiahC said:
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market.....
Click to expand...
Click to collapse
According to who?
i have the same firmware as you bro, everything is the same with the same GPS issue as everyone else.
IsaiahC said:
Can anyone confirm OP's post? It is possible that Samsung released a corrupted batch. At this point I almost want to unroot my Captivate and exchange it for a new one. I paid $500 for this and it's not working.
Speaking of which can someone PM an UNROOT tutorial for the Captivate. I'll be a guinea pig and go exchange my phone for a new one to see if this fixes any issues.
Click to expand...
Click to collapse
So to follow up from yesterday, I installed a lag fix and messed my phone up pretty badly. I flashed back to stock rom and took it back to AT&T and exchanged it for a new one.
I HAVE ABSOLUTELY NO TROUBLE GETTING A LOCK IN UNDER 1-3 SECONDS EVERY TIME. Also, as a note, the SIM tray in the back of the phone is different than the one I had previously.
I'm not telling you to go exchange your phone but AT&T has an under 30 money back or exchange return policy. Just tell them you called Samsung or AT&T already and they told you to bring it in for a new one because it has trouble establishing a GPS lock.
Anyone try gps status app?
Run that first, get a lock then go to maps, should get a lock fast...
I Had my phone for 2+ weeks and gps works, not great but works (locks under 2 minutes if I can point to the sky, drop signal occasionally, pretty accurate).
Thought I'd share this with you guys. I recommend sending out a similar email so that they know that there are serious concerns about the phone. I did it online at the Contact Us page on the Samsung website.
Here's what I wrote:
Hello,
I recently purchased a Samsung Captivate. Overall, I am quite pleased with the device. However, there are a few things that irritate me about it that I was hoping you could comment on:
1.) There is a serious lag issue. Do a quick google search and you'll find that this is a universal problem with the phone.
2.) The GPS does not work. Also a universal issue.
3.) No 2.2 Froyo.
4.) No last.fm scrobbling support for the default music player (which I love by the way!)
5.) Drivers for Windows 7 x64 do not work well. After a lot of trial and error, I finally got it. Again, a universal issue.
A lot of people complain about the TouchWiz UI, but I personally enjoy it, as long as the lag issue is taken care of. Also I'm pleased with the phone call quality, and almost all other aspects of the phone.
I appreciate your time, and hope to hear from you soon.
Thank you,
[thecoolestcow]
Here is the response:
Dear [thecoolestcow],
Thank you for your inquiry.
Regarding the GPS on the phone, Samsung Mobile is aware that under certain conditions, the GPS on our U.S. Galaxy S devices may not be meeting performance expectations. We are diligently evaluating the situation and will provide an update as soon as possible.
We advise you to use assisted GPS powered by your service provider.
We still don't have any update regarding the release of the Android 2.2 for the Captivate and the drivers that will be compatible with Windows 7 64bit.
We will forward your report of this behavior along to the appropriate parties for additional review and consideration.
We are unable to speculate when/if this software revision might be available due to the fact that this might lead to inaccurate information and confusion.
Should this become available, it will be posted on our website in the Samsung Download Center.
Please feel free to check back with us periodically for updates.
Should you desire additional assistance resolving this, we invite you to call Samsung Customer Support by phone at our toll free number 1-888-987-4357 between the hours 7:00 a.m. to 9:00 p.m. Monday through Friday, and 9:00 a.m. to 6:00 p.m. Saturday, Central Standard Time.
Thank you for choosing Samsung.
Sincerely,
Technical Support
thecoolestcow said:
Thought I'd share this with you guys. I recommend sending out a similar email so that they know that there are serious concerns about the phone. I did it online at the Contact Us page on the Samsung website.
Here's what I wrote:
Hello,
I recently purchased a Samsung Captivate. Overall, I am quite pleased with the device. However, there are a few things that irritate me about it that I was hoping you could comment on:
1.) There is a serious lag issue. Do a quick google search and you'll find that this is a universal problem with the phone.
2.) The GPS does not work. Also a universal issue.
3.) No 2.2 Froyo.
4.) No last.fm scrobbling support for the default music player (which I love by the way!)
5.) Drivers for Windows 7 x64 do not work well. After a lot of trial and error, I finally got it. Again, a universal issue.
A lot of people complain about the TouchWiz UI, but I personally enjoy it, as long as the lag issue is taken care of. Also I'm pleased with the phone call quality, and almost all other aspects of the phone.
I appreciate your time, and hope to hear from you soon.
Thank you,
[thecoolestcow]
Here is the response:
Dear [thecoolestcow],
Thank you for your inquiry.
Regarding the GPS on the phone, Samsung Mobile is aware that under certain conditions, the GPS on our U.S. Galaxy S devices may not be meeting performance expectations. We are diligently evaluating the situation and will provide an update as soon as possible.
We advise you to use assisted GPS powered by your service provider.
We still don't have any update regarding the release of the Android 2.2 for the Captivate and the drivers that will be compatible with Windows 7 64bit.
We will forward your report of this behavior along to the appropriate parties for additional review and consideration.
We are unable to speculate when/if this software revision might be available due to the fact that this might lead to inaccurate information and confusion.
Should this become available, it will be posted on our website in the Samsung Download Center.
Please feel free to check back with us periodically for updates.
Should you desire additional assistance resolving this, we invite you to call Samsung Customer Support by phone at our toll free number 1-888-987-4357 between the hours 7:00 a.m. to 9:00 p.m. Monday through Friday, and 9:00 a.m. to 6:00 p.m. Saturday, Central Standard Time.
Thank you for choosing Samsung.
Sincerely,
Technical Support
Click to expand...
Click to collapse
man I just dont see this lag yall are talking about... Had the phone since day 1, no lag fix and its fast as my n1 on 2.2. about.. Wierd...
Also GPS does work, just not reliably all the time, some works fine, others not, others sometimes.. So saying it dont work is exadurating. I just dont want people that dont have one think that the GPS dont work. It does and I use it everyday without issue. No fixes or anything, mine and some others works...
2.2 froyo will be here soon. Hold your horses on and it will be here next month I will bet...
I didn't see the lag either for a while, but I see it in most of the Samsung native apps, like Messaging and the screen unlock.
GPS also used to work amazingly. It just stopped completely now for me.
It's good though that they acknowledged in the email that they were going to release a fix for it.
thecoolestcow said:
I didn't see the lag either for a while, but I see it in most of the Samsung native apps, like Messaging and the screen unlock.
GPS also used to work amazingly. It just stopped completely now for me.
It's good though that they acknowledged in the email that they were going to release a fix for it.
Click to expand...
Click to collapse
Yea, Well Im certain it will be fixed. The samsung epic 4g is rumored to have a working GPS (more testing needs done for me to believe it for sure) and if we have the same hardware gps wise as the Epic 4g we should definatly see a fix...
Nice, Engadget confirms.
engadget.com/2010/08/18/samsung-says-gps-is-tested-and-validated-on-epic-4g-our-testi/
There is most certainly lag. Like you guys, it wasn't a big deal until I saw the lag fix.
Long story short, I've been running the lag fix about a week, then borked my phone with another tweak and had to revert back to stock. HOLY COW was that thing slow... I never really knew any different until I had seen greener pastures
I will say I don't think the DEFAULT lag is worse than any other phone on the market. But it is capable of much, much faster.
Also you forgot to include the complaint that MMS doesn't work on EDGE, only 3G.
TexUs said:
There is most certainly lag. Like you guys, it wasn't a big deal until I saw the lag fix.
Long story short, I've been running the lag fix about a week, then borked my phone with another tweak and had to revert back to stock. HOLY COW was that thing slow... I never really knew any different until I had seen greener pastures
I will say I don't think the DEFAULT lag is worse than any other phone on the market. But it is capable of much, much faster.
Click to expand...
Click to collapse
Which lag fix did you use? I saw several. I haven't rooted my device yet because I'm a little girl. I'm trying to gather as much info as possible first.
thecoolestcow said:
Which lag fix did you use? I saw several. I haven't rooted my device yet because I'm a little girl. I'm trying to gather as much info as possible first.
Click to expand...
Click to collapse
Well I did all my tweaks manually the first time. However when I borked and started over I used this: http://forum.xda-developers.com/showthread.php?t=751934
That will do all necessary tweaks at once. Just download the update.zip file to the root of your INTERNAL card, reboot into recovery mode (ask if you don't know how... easiest way is to use ADB), and select "reinstall packages" and you're done.
Just check the post I linked to, but it'll remove all the ATT crapware, remove the loud startup sounds, install root, block ads, etc.
After it's ran you then can go into the app it adds and run the lag fix... After you run that script it needs a reboot... And then you've got a lag fixed phone that runs twice as fast. ROM Manager, for instance, takes like a whole freaking minute it seems to open un-lag-fixed. Lag-fixed it takes several seconds max.
TexUs said:
Well I did all my tweaks manually the first time. However when I borked and started over I used this: forum.xda-developers.com/showthread.php?t=751934
That will do all necessary tweaks at once. Just download the update.zip file to the root of your INTERNAL card, reboot into recovery mode (ask if you don't know how... easiest way is to use ADB), and select "reinstall packages" and you're done.
Just check the post I linked to, but it'll remove all the ATT crapware, remove the loud startup sounds, install root, block ads, etc.
After it's ran you then can go into the app it adds and run the lag fix.
Click to expand...
Click to collapse
Holy crap, how did I miss that one? Excellent, thank you. I will likely be doing that in the near future!
Sent from my SAMSUNG-SGH-I897 using XDA App
thecoolestcow said:
Holy crap, how did I miss that one? Excellent, thank you. I will likely be doing that in the near future!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
NP.
I'm happy with 2.1 right now... I mean the Captivate at 2.1 runs faster than anything else on the market, including the N1 2.2......
So I can live with 2.1 until Samsung releases 2.2
Once you see how much faster it is with the lag fix, you'll start to wonder how much faster 2.2 will be. The Captivate will be untouchable.
There is definitely significant lag on the stock firmware - most notably for me with the marketplace but s also for some other apps when they are loading data. I haven't applied any fixes yet as I'm waiting for a decent firmware update before I do too much with my phone.
JH2/3 are looking like good bets, but I would suspect that an official firmware is right around the corner given the few changes between JH2 and JH3.
Sent from my SAMSUNG-SGH-I897 using XDA App
Why wait? It takes 5 minutes to vastly improve the usability of your phone.
And worst comes to worst, you use the Odin3 one-click to restore it to stock. Seems pretty awesome. I'll probably be "super-rooting" tonight!
Also to note you should only be doing that super-rooting from stock to start with... It's the most reliable method anyway. You can try it from what you've got but- if there's issues you just need to do it from stock.
Hm. And there's no way to back up my apps/data right?
thecoolestcow said:
Hm. And there's no way to back up my apps/data right?
Click to expand...
Click to collapse
Yes, download ROM Manager but you need to be rooted first I think... So you can root your phone only (same process but it just does rooting: http://forum.xda-developers.com/showthread.php?t=725555), download/install ROM Manager (http://forum.xda-developers.com/showthread.php?t=734163). Then when you reboot into the ROM Manager recovery screen there's nandroid backup utility that'll back up everything.
If you like selective backups of stuff you can also use Titanium Backup (also requires root).
smashpunks said:
man I just dont see this lag yall are talking about... Had the phone since day 1, no lag fix and its fast as my n1 on 2.2. about.. Wierd...
Also GPS does work, just not reliably all the time, some works fine, others not, others sometimes.. So saying it dont work is exadurating. I just dont want people that dont have one think that the GPS dont work. It does and I use it everyday without issue. No fixes or anything, mine and some others works...
2.2 froyo will be here soon. Hold your horses on and it will be here next month I will bet...
Click to expand...
Click to collapse
GPS does NOT work. It barely functions, so it does not work. Anybody that says it does is just trying fool themselves into thinking they didnt make a mistake. GPS absolutely does not work. Its been documented by numerous sources and tens of thousands (or more) vibrant and captivate users here in the US. For Christ's sake, even Samsung has admitted that it doesnt work. They've used incorrect drivers from Broadcom, so it can't possibly work.
Samsung may release Froyo to the carriers toward the end of next month, but it'll be quite a while before AT&T releases it to us. They have to go through and add all their crapware and remove any functionality that's in the stock rom that they can charge money for (this really pisses me off I REALLY, want that wifi hotspot functionality!!!) and they have to cripple the kernel and radio so there'll be no HSUPA.
derek4484 said:
GPS does NOT work. It barely functions, so it does not work. Anybody that says it does is just trying fool themselves into thinking they didnt make a mistake. GPS absolutely does not work. Its been documented by numerous sources and tens of thousands (or more) vibrant and captivate users here in the US. For Christ's sake, even Samsung has admitted that it doesnt work. They've used incorrect drivers from Broadcom, so it can't possibly work.
Samsung may release Froyo to the carriers toward the end of next month, but it'll be quite a while before AT&T releases it to us. They have to go through and add all their crapware and remove any functionality that's in the stock rom that they can charge money for (this really pisses me off I REALLY, want that wifi hotspot functionality!!!) and they have to cripple the kernel and radio so there'll be no HSUPA.
Click to expand...
Click to collapse
We're about a month after release and have Vanilla Android 2.1 ROMs, so chill out. Have some patience, I'm sure we'll see them for 2.2 as well.
derek4484 said:
GPS does NOT work. It barely functions, so it does not work. Anybody that says it does is just trying fool themselves into thinking they didnt make a mistake. GPS absolutely does not work. Its been documented by numerous sources and tens of thousands (or more) vibrant and captivate users here in the US. For Christ's sake, even Samsung has admitted that it doesnt work. They've used incorrect drivers from Broadcom, so it can't possibly work.
Samsung may release Froyo to the carriers toward the end of next month, but it'll be quite a while before AT&T releases it to us. They have to go through and add all their crapware and remove any functionality that's in the stock rom that they can charge money for (this really pisses me off I REALLY, want that wifi hotspot functionality!!!) and they have to cripple the kernel and radio so there'll be no HSUPA.
Click to expand...
Click to collapse
Mine works and so do others in those thousands of people threads. If you would like I can copy n paste them for ya...
Its directed me to many places perfectly so it works, its just unreliable and not the best, hence needs to be optimized ...
now post a link where samsung admitted using incorrect drivers? I've never saw that...
http://www.engadget.com/2010/09/22/samsung-captivate-gets-gps-fix-other-galaxy-s-versions-wait-pat/
"An update to improve the Samsung Captivate's GPS performance is now available. Captivate customers will receive a notification on their device that an update is available and will simply need to download the file to update their phone. The updates will be pushed to customers' devices over the next few weeks.
The update for the Captivate will also improve additional device functions, such as media scanning time, add the full version of Quickoffice and address Microsoft Exchange 2003 policy support."
Fingers crossed, that this already hasn't been leaked, torn apart, and found useless...
Its probably the JH7 OTA that they started rolling out yesterday, not a new separate fix...has anyone that received the OTA updated noticed any difference on the GPS?
I saw a few ppl that got the update say the GPS is the same as before.
I wouldn't trust Engadget for anything GPS related. They botched Galaxy S reviews so many time on the GPS topic:
1. They said GPS works just fine when they review Captivate and Vibrant.
2. They said all you need to do to fix the GPS is just turn on the 'Use Wireless Networks' in Location and Security settings because Samsung told them so.
3. They said EPIC 4G has GPS all fixed out of box, again because Samsung told them so.
4. Now, again, they claim the latest JH7 update fixes GPS because, again, Samsung told them so. Never mind AT&T itself never mentioned any GPS fixes in its release notes.
Yea, I re-read the update discription that was posted on a couple of other android sites, and it sounds just like the JH7 ...
Damn
I am downloading and updating now.. will see.
Yes, they are wrong again. Well, I wouldn't put the blame on them 100%, since I believe that letter came from Samsung PR (who know nothing tbh).
andy2na said:
Yes, they are wrong again. Well, I wouldn't put the blame on them 100%, since I believe that letter came from Samsung PR (who know nothing tbh).
Click to expand...
Click to collapse
Yes, it is bad jounalism. What happens to 'trust but verify'?
Yea, I read the same quote on a couple of different sites outside of engadget...
ipxnsv said:
I am downloading and updating now.. will see.
Click to expand...
Click to collapse
I just downloaded and updated then said "Update is failed." Is this because I'm rooted?
Engadget does suck. All those aggregate tech sites suck at everything, but stealing good sites articles.
I am happy about quick office though. I really hope custom roms don't rip it out as bloat.
This site is claiming that the update DOES fix the gps, and has video:
http://www.careace.net/2010/09/21/s...te-being-rolled-out-this-week-starting-today/
I'm not rooted, am stock and update failed. Won't resume either, says no firmware to update if I try that.... so it may be something wrong with the update.....
compuguy1088 said:
This site is claiming that the update DOES fix the gps, and has video comparing before and after:
http://www.careace.net/2010/09/21/s...te-being-rolled-out-this-week-starting-today/
Click to expand...
Click to collapse
The site says they are doing more testing and update the results by 2PM. The video only shows a GPS location fix by standing still, not driving around. My JH7 can do that w/o problem either but when driving, it is all over the place.
What is the csc version after the update?
I have had jh7 for over a week, it is an improvement but not a fix
Sent from my SAMSUNG-SGH-I897 using XDA App
To be honest, my GPS was working when I first got it.
And yes, it is jh7. Which has bad ass GPS when I use it.
klloyd said:
I'm not rooted, am stock and update failed. Won't resume either, says no firmware to update if I try that.... so it may be something wrong with the update.....
Click to expand...
Click to collapse
I unrooted to give it another shot and just learned of the "check once/24hrs" deal. Bull****! Thanks ATT
I am downloading now. It is taking quite a while (out in the wilds of KS we only get EDGE speeds). Does anyone know if this will work if I am rooted? I didn't un-root, and the last time I did a backup was Saturday. I suppose I won't lose much if it craps out.
mine is stuck at "Communication in progress" it just loads....
If anybody has successfully done the OTA update, can they please post the stock JH&GPS settings from the LBSTEstMode menu?
Has anyone tried Keis?
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Yea I got a text running perception 5. Not sure its froyo or a really late text for jh7.
I've been getting them for the last few days, though I'm not willing to flash to find out lol....
I got it shortly after flashing to cognition 2.3b6 - checked for new OTA updates and didn't get anything.
Just tried and failed to connect to server.. though it's probaly nothing. Been a lot of posts about people getting texts to update (I haven't gotten one, I'm running stock JH7). I think it's just AT&T trying to get everyone to update to JH7.
From androidforums.com:
"This has been happening for a while now. People who are running anything other than Samsung/AT&T firmware have been getting these notices."
Stock
JimmehDean said:
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope. Stock.
1. AT&T doesn't know what firmware you are running. They are STILL sending out general update notifications to remind people to update to JH7.
2. There are two other threads in the forum, on the front page discussing the same topic...LOL. Come on guys.
For whatever it's worth, I spoke with three AT&T techs today, from common answerer, all to UPPER LEVEL WIRELESS TECH, and the answers I got from all three, screwed my thinking, which at times, AT&T does well. The OTA to side-load they been speaking of, IS NOT A SOFTWARE UPDATE, as I thought it had to be, but online instructions, on how to make am adjustment, Menu, then Settings, to stop BLOCKING the install of NON MARKET APPS, like from Amazon. I thought the OTA, was a software 'patch' that would fix the blocking of apps not from the Market, but they all told me, that the OTA, was really a set of steps, that showed you how to make the MANUAL ADJUSTMENTS, on my Captivate. Maybe I'm the only one feeling like an idiot over this, but that is how I was left feeling. They sent not one, but two different text mess., that for some reason, didn't do a thing, so the upper level tech, tried walking me through the adjustment, his own self, but he flat failed to tell me how. He finally suggested, that since it was Amazon's appstore app I was trying to install, and my Captivate still was BLOCKING the install, to ask AMAZON for help, in case THEY KNOW how to make the adjustments on the Captivate, or better, to ask SAMSUNG, since it's their phone. The guy was nice..., but why do I feel shafted for paying outrageous premiums for service from AT&T, but when I ask for help, I get shoved along to someone else, for them to help me?
Has anyone heard, that the OTA, is NOT SOFTWARE, but actually instructions, to make in your phones settings? If anyone could give a rational explanation of this to me, I'd appreciate it. My AT&T Samsung Captivate, is a great phone, to me, but AT&T, leaves a lot to be desired. Any suggestions?
Please don't hijack threads.
Anyways if it is instructions then they will need to push out an ota to even enable the option. They removed the option to prevent people from enabling it to begin with.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
AT&T updates
JimmehDean said:
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Last night my wife's phone completely hung. Had to use 3-button combo to get into recovery and reboot. After reboot, Device Management was running endlessly. Tried to kill it but it wouldn't stop. Tried to use TIBU to freeze it but TIBU wiuldn't open. Finally killed it by clearing Device Management data. Went into TIBU again and froze it. Unbelievable. Her phone is stock 2.2 but rooted. 2 hours later, I noticed on my phone that Device Management was running (notification bar). Went through the same sequence to kill it and freeze it. I will never defrost this!!
On my stock 2.2 not rooted cappy it was enabled just by turning the phone off and back on a couple of days ago.
Sent from my SAMSUNG-SGH-I897 using XDA App
ffman2152 said:
For whatever it's worth, I spoke with three AT&T techs today, from common answerer, all to UPPER LEVEL WIRELESS TECH, and the answers I got from all three, screwed my thinking, which at times, AT&T does well. The OTA to side-load they been speaking of, IS NOT A SOFTWARE UPDATE, as I thought it had to be, but online instructions, on how to make am adjustment, Menu, then Settings, to stop BLOCKING the install of NON MARKET APPS, like from Amazon. I thought the OTA, was a software 'patch' that would fix the blocking of apps not from the Market, but they all told me, that the OTA, was really a set of steps, that showed you how to make the MANUAL ADJUSTMENTS, on my Captivate. Maybe I'm the only one feeling like an idiot over this, but that is how I was left feeling. They sent not one, but two different text mess., that for some reason, didn't do a thing, so the upper level tech, tried walking me through the adjustment, his own self, but he flat failed to tell me how. He finally suggested, that since it was Amazon's appstore app I was trying to install, and my Captivate still was BLOCKING the install, to ask AMAZON for help, in case THEY KNOW how to make the adjustments on the Captivate, or better, to ask SAMSUNG, since it's their phone. The guy was nice..., but why do I feel shafted for paying outrageous premiums for service from AT&T, but when I ask for help, I get shoved along to someone else, for them to help me?
Has anyone heard, that the OTA, is NOT SOFTWARE, but actually instructions, to make in your phones settings? If anyone could give a rational explanation of this to me, I'd appreciate it. My AT&T Samsung Captivate, is a great phone, to me, but AT&T, leaves a lot to be desired. Any suggestions?
Click to expand...
Click to collapse
What is with all of the commas? Load a rom and don't worry about any ota from AT&T!
This is my Captivate. There are many like it but this one is mine
no problem here rogers Canada ftw side loading enabled from the beginning. and as for the messages if you want them to stop just block them. and chances are if your on this site you have sideloading anyways
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app
dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.
Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction