Related
http://www.engadget.com/2010/12/31/android-still-has-horrible-text-messaging-bugs-thatll-get-you-f/
Is this really a widespread problem, or is it more Engadget anti-Android propaganda?
Not sure but I haven't experienced it in almost a year of using several android devices.
I use Handcent, so I have no idea what they're talking about.
Sent from my Nexus S using Tapatalk
Read the source links.
For the record, I love android. I hate all the anti-android crap going around. But I have experienced this before. One time upon booting up, my contacts were all mixed up with the wrong numbers. It was so weird. My friend became my dads name on there and another friend became my cousins whom I never texted. So when they texted me I saw the names and was like wtf? How do they know about (whatever we were chatting about earlier). Took another reboot and everything was fine. I also experienced the phone clicking on the wrong thread that I pressed, that definitely happens. I've learned to double check who Im texting.
Is this fixed by using a different SMS app then? Apparently it happens with e-mails, too, but only with the default e-mail app.
I have been using an HD2, that dual boots WM 6.5 and Android 2.2 Froyo, never had this problem.
My daughter uses a Behold 2 and sends and receives over 16000 text messages per month, and never a problem like this.
I think it's more hate against Android, since it is starting to get a strong hold of the smartphone market.
I'm also sure it's a lot of user error too.
Google just updated this to critical, so I'm guessing it'll be patched pretty soon.
It happens to me at least twice a week. I actually switched to handcent it was so bad. Thankfully I never had anything truly embarrassing go to the wrong person, but I have had some confusing moment...The worst was when I carried out a long conversations with the wrong person... The problem happens when you click on the new message item in the notification menu without actually opening it up through the messaging app. You see the correct reply thread, and it is only when you press send that you realize it sent to the wrong person. This is very real, but I used to think it was just my phone.
lmao. This is just amusing.
The ONLY time I ever got the bug was when I received a new message, I used the drop down menu bar to view the message, and this was on a beta froyo build. Any time I went through the regular messaging app, everything was fine. Last I read in a forum long ago burried, only time the bug happened was when you used the drop down...
I've used Android since the G1 was released and don't remember ever experiencing this issue. But if it is an issue, then it needs media attention to get Google to fix it as quick as possible. Although, the problem is getting the fix out, since you know, all these carriers and manufacturers take forever to get an OTA out.
Google said:
Hi all,
I want to let everyone know that we are actively investigating this issue, and we hope to have an update soon. Obviously, this is a very difficult to reproduce bug.
Rather than replying "me too", you can star this issue to follow it. Just saying "me too" just obscures the useful information in this bug, and makes it harder to fix. Of course, if you have useful information to add to the bug, such as a system dump or an insightful analysis of the code, feel free to update the bug with your observations.
Click to expand...
Click to collapse
So they are now investigating this. I'll be using Handcent on my DHD until they sort it.
tooter1 said:
I have been using an HD2, that dual boots WM 6.5 and Android 2.2 Froyo, never had this problem.
My daughter uses a Behold 2 and sends and receives over 16000 text messages per month, and never a problem like this.
I think it's more hate against Android, since it is starting to get a strong hold of the smartphone market.
I'm also sure it's a lot of user error too.
Click to expand...
Click to collapse
16,000? I'm sure most networks in the UK have a 3,000 FUP
Anyway, I haven't experienced this issue in the 18 months I've been using Android
LooieENG said:
16,000? I'm sure most networks in the UK have a 3,000 FUP
Anyway, I haven't experienced this issue in the 18 months I've been using Android
Click to expand...
Click to collapse
I can believe 16,000. My 17 year old sister has about 10,000 a month. Unlimited texting, ftw.
I've been using Android since the release of the HTC Dream in Canada and I've never ever ever ran into this problem, and most of the ROMs I've ran have been beta or experimental. I'm thinking they're blowing it out of proportion.
TheBiles said:
I can believe 16,000. My 17 year old sister has about 10,000 a month. Unlimited texting, ftw.
Click to expand...
Click to collapse
When we were on Verizon, one month it was up to 39,000. I was floored. That is when I was like thank goodness for.....Unlimited Texting FTW!
Still no problems like this.
I've never had this problem and Goggle has made a press release and said they are having a hard time replicating it. I think that there could be an error that happens once in a blue moon, but I think most of the time it's just user error.
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic! http://mobilehighway.blogspot.com/
TheBiles said:
I can believe 16,000. My 17 year old sister has about 10,000 a month. Unlimited texting, ftw.
Click to expand...
Click to collapse
Oh yeah, I believe it. I'm just curious as to how their fingers haven't worn to the bone yet?
Googles claiming they can't reproduce this internally and they've only upped it's status cause of bad publicity. That's what androidguys claim ...
Sent from my Nexus One using XDA App
Yeah sometimes when I get a message I click on the thing in the drop down menu and it takes me to another thread, but I'm pretty sure the point of clicking that button is just for it to get you to the messaging app. Also sometimes I go to the messaging app and click the top thread and it takes me to a different thread. So this bug is true at times.
We all know the thunderbolthas been plagued with problems since its launch. First the launch date was delayed. Now the GB update that has been delayed for months gets released and pulled immediately due to more bugs. I have read about people who complain so much that they are given free replacement phones of their choosing. I would like to do the same and try and get the new nexus phone. So I need your help with making a list of all the thunderbolt problems since launch so I can make a good argument for why I should get a new phone. Thanks guys!
Just to add my 2 cents
You have to remember that as with most forums, you usually only see the problems and not the ones with good units and that one or two people talking in a forum thread or maybe a handful of people posting multiple threads can make it seem alot worse then it really is. I have never had an issue with my bolt since getting it on launch. I was first on line at bestbuy and it has worked great since the moment I activated it.
Also the launch was not delayed. Neither HTC or Verizon gave a specific date on release. Everybody was basing the release off rumors and a mistaken bestbuy ad...
when you say 'new phone', are you trying to get Verizon to allow you to exchange your TB for something else?
if so, that's not that hard. you just need to call and complain a few times(bring up battery life & call quality - data speeds couldn't hurt to) and after a few calls & complaining about how you wish you never got this phone they should offer to exchange it for you so long as you got the phone somewhat recently.
if you bought the phone back at launch though then the most they would do(other then offer a warrenty exchange) is allow you to get a different phone at the upgrade price instead of full retail, then you'd still have your TB to sell on craigslist or something.
xTFGx said:
We all know the thunderbolthas been plagued with problems since its launch. First the launch date was delayed. Now the GB update that has been delayed for months gets released and pulled immediately due to more bugs. I have read about people who complain so much that they are given free replacement phones of their choosing. I would like to do the same and try and get the new nexus phone. So I need your help with making a list of all the thunderbolt problems since launch so I can make a good argument for why I should get a new phone. Thanks guys!
Click to expand...
Click to collapse
I can tell you right now, no amount of *****ing will get you the Galaxy Nexus.
And if you don't actually have any problems with your phone, and are just *****ing because you want something free, you should head to wall street, I hear a lot of that is going on there.
Good luck is all i can say. I went through 3 Droids and 4 droid 2s, and an iPhone (on their suggestion) and STILL had to pay full 2 year contract price for the T Bolt. VZW isn't like att you barely get anything for free EVER
ScoobarSTI said:
Good luck is all i can say. I went through 3 Droids and 4 droid 2s, and an iPhone (on their suggestion) and STILL had to pay full 2 year contract price for the T Bolt. VZW isn't like att you barely get anything for free EVER
Click to expand...
Click to collapse
AT&T has to give things out for free just to get people to stay on their inferior network. Verizon knows if you leave, you will more than likely come back at sometime after you get fed up with inferior service lol
xTFGx said:
So I need your help with making a list of all the thunderbolt problems since launch so I can make a good argument for why I should get a new phone. Thanks guys!
Click to expand...
Click to collapse
I think it would be pretty funny if you get no helpful list of "problems"
xTFGx said:
We all know the thunderbolthas been plagued with problems since its launch. First the launch date was delayed. Now the GB update that has been delayed for months gets released and pulled immediately due to more bugs. I have read about people who complain so much that they are given free replacement phones of their choosing. I would like to do the same and try and get the new nexus phone. So I need your help with making a list of all the thunderbolt problems since launch so I can make a good argument for why I should get a new phone. Thanks guys!
Click to expand...
Click to collapse
So lemme make sure I understand this. You want a list of other people's problems, so YOU can get a new phone for free?
"I deserve a new phone because forum members are having these problems which makes me unhappy with my thunderbolt"
Yep, sounds like a GREAT idea.
*Sent from my BAMF'ing Blissed-out 'bolt sportin' Taykiin mods*
The thunderbolt was the best choice at the time and I don't see any reason to change it now. Nothing newer is too much better. I think the bionic looks and feels cheaper and that's before you consider the locked bootloader... major con for me... the grass ain't always greener. Just sayin.
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
Charge would be nice, but if I want one bad enough ill buy one. Trying to get one for free is lame.
Sent from my ADR6400L using Tapatalk
xTFGx said:
We all know the thunderbolthas been plagued with problems since its launch. First the launch date was delayed. Now the GB update that has been delayed for months gets released and pulled immediately due to more bugs. I have read about people who complain so much that they are given free replacement phones of their choosing. I would like to do the same and try and get the new nexus phone. So I need your help with making a list of all the thunderbolt problems since launch so I can make a good argument for why I should get a new phone. Thanks guys!
Click to expand...
Click to collapse
You need to stop believing all the internet crap you read. I've had a couple of phones that were FAR, FAR worse than the Thunderbolt and I never got free upgrades to replace them. The people that say they did probably took an early upgrade on another line. I ended up going back to old phones with the POS devices. So yeah, if you think I calling them liars or misrepresenting the truth, that's EXACTLY what I'm doing. And I know for a fact none of them can prove it.
loonatik78 said:
You need to stop believing all the internet crap you read. I've had a couple of phones that were FAR, FAR worse than the Thunderbolt and I never got free upgrades to replace them. The people that say they did probably took an early upgrade on another line. I ended up going back to old phones with the POS devices. So yeah, if you think I calling them liars or misrepresenting the truth, that's EXACTLY what I'm doing. And I know for a fact none of them can prove it.
Click to expand...
Click to collapse
The ONLY reason why they gave me a bionic is they tried to charge me twice for not returning a defective device two separate times. Even then I had to fight them for it, first they offered to pay my data for a month. I guess their logic was "sorry we tried to steal $1200 from you, here's $30".
There was no early upgrade or anything, I told the guy to just cancel my contact. I had no intention of canceling, look what else is out there. If you really think you can get a free phone just because of the issues you've had with it good luck.
Sent from my DROID BIONIC using Tapatalk
JillyBohnson said:
The ONLY reason why they gave me a bionic is they tried to charge me twice for not returning a defective device two separate times. Even then I had to fight them for it, first they offered to pay my data for a month. I guess their logic was "sorry we tried to steal $1200 from you, here's $30".
There was no early upgrade or anything, I told the guy to just cancel my contact. I had no intention of canceling, look what else is out there. If you really think you can get a free phone just because of the issues you've had with it good luck.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
That's certainly above and beyond a few complaints about a device that works otherwise! Wow... That's pretty screwed up.
Problems with the Thunderbolt (STOCK)
Now granted i dont know if verizon has pushed any radio upgrades, i do that myself and the first radio upgrade i got fixed my issue.
1. GPS takes forever to lock. I walk in with a friend tried to get him a discount and showed him how MY thunderbolt wil lock in seconds where the thunderbolt, charge and nearly every other android phone they have took over 5 minutes to lcok (i never locked before we left).
2. Battery life on the stock is disgusting in comparison to clean ROMs. (my opinin you shouldnt have to root the phone to get all the specs to work correctly)
thats really all i can think of.
My main issue with this phone is battery life when on a sense based rom (any sense based rom sucks battery life a really fat guy with a milkshake), but I have an upgrade on my account and am definitely grabbing a nexus when it comes out
God.... Please don't help this guy! This is stupid!
loonatik78 said:
God.... Please don't help this guy! This is stupid!
Click to expand...
Click to collapse
^^this
*Sent from my BAMF'ing Blissed-out 'bolt sportin' Taykiin mods*
Lol its dumb but its life. I dont support it nor am i against it. I had HTC Touch Pro 2 i had for over 2 years. It was a fantastic phone for the era that the Iphone came out. Sure apps were very very few and far between but being able to get ROms that were similar to HTC's 2.1 or3.0 was awesome. The only problem i ever had with the phone was i was plagued with BSOD's constantly after unlocking. But as we all know its based on the phone you get, my brother and sister both had them and were unlocked overclocked and had 0 problems...again i know where the guys coming from we all play the system at one point or another to get what we want. He was just a little more blunt about it than most people would have been. Next time bro just be a little more incognito about the whole idea behind it. Its like Backtrack. Its a tool to "test your wireless security" and you know 80% of the people that use the tool are not testing their secruity with it.
It's threads like this that made me remember why I left in the first place. I had hoped things had changed... guess not...
loonatik78 said:
God.... Please don't help this guy! This is stupid!
Click to expand...
Click to collapse
This... 1000 times, this.
I have an HTC Shift that is now a replacement phone Sprint sent because the other Shift bricked on a OTA update. The phone itself looks brand new. (we have had it since Apriil) The problem with the phone is that it will never charge the battery. I actually have 3 spare batteries so in total 4 batteries are charged to 100% but as soon as I put them into the Shift device the battery status will range from 0% to 8% an occassionally will charge to 12% but no higher. If I take the battery out and put it into another HTC it will show 95% or better as charged - to be clear this is the same battery that just seconds before registered 12% or less.
I've tried everything. I've changed Roms (the good thing about this is that I can tell you the ins and outs on about 12 different Roms and kernels now) I've changed up kernels. I installed Bettery Battery, battery calibration tools, spare parts...booted it up empty, let it stay off and "charge" all night, on and charge all night, factory reset, everything but RUU because it just won't do it and HTC update, won't do that either because of the battery being below 30%.
OK, so you say - take it back to Sprint and get a new one - can't do that because I can't unroot it with the RUU as it still shows s-off -
I'm brain dead on this one.
I'm not a newbie at this. I've rooted several phones, HTC, LG, Palm Pre, even turned the Palm Pixie to a wifi goddess in it's day by switching out the radio(you know). I've jailbroke the Iphone and Ipad. Rooted my Thrive and turned a pandigital into a sweet little android.
I don't want to take the phone back like it is. I want to figure out what the heck is the issue. (i know...i know) When I plug the phone in the led comes on as though it is charging but it never charges...any ideas? you know it's probably something simple and I've just fried my brain at this point. Any ideas? Anybody??
Thanks in advance for any input, ideas or helpful tips!
Sondee
We be - Riding With The Nerd Herd
I'm no expert on this, but if i were you i'd just brick the thing and take it to sprint.
jesuscash said:
I'm no expert on this, but if i were you i'd just brick the thing and take it to sprint.
Click to expand...
Click to collapse
Excellent advice... FAIL... COME ON MAN...
Make sure you are wiping the system partition as well... Going from sense to aosp needs a thorough system (not data) wipe... To wipe system, it's located in mounts and storage in recovery if using cwm...
Sent from my EVO LTE
My girlfriend's phone has the EXACT SAME ISSUE. No idea how to fix, I figure there's a contact or sensor hw at fault. It's not ROM specific, flashing a new rom won't make a diff. As soon as the gf or I get a new phone, I'll mess with the device itself.
Best advice - return it!
jkrlvgn said:
My girlfriend's phone has the EXACT SAME ISSUE. No idea how to fix, I figure there's a contact or sensor hw at fault. It's not ROM specific, flashing a new rom won't make a diff. As soon as the gf or I get a new phone, I'll mess with the device itself.
Best advice - return it!
Click to expand...
Click to collapse
Can't return something rooted unless you want your account flagged lol
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Can't return something rooted unless you want your account flagged lol
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Been there.....not fun at first, but once CS knew I knew more than they did it was no longer an issue to have my account credited for the service I WASN'T getting. Most ever off was 165 from a 180 dollar bill
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Been there.....not fun at first, but once CS knew I knew more than they did it was no longer an issue to have my account credited for the service I WASN'T getting. Most ever off was 165 from a 180 dollar bill
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Well that's a lot of money. When i was buying the Evo LTE i didn't know i would have to give them my phone and so when she asked for it i was like ummm... I need to go home and do something real quick. She gave me a weird like and ask what i need to do and told her that i can't say. I think she knew i was rooted cause she told me i won't get in trouble but i just was like nope i don't want a flagged account so i'll be back in 30 minutes. She gave up at that point
YoungCorruptionV2.0 said:
Well that's a lot of money. When i was buying the Evo LTE i didn't know i would have to give them my phone and so when she asked for it i was like ummm... I need to go home and do something real quick. She gave me a weird like and ask what i need to do and told her that i can't say. I think she knew i was rooted cause she told me i won't get in trouble but i just was like nope i don't want a flagged account so i'll be back in 30 minutes. She gave up at that point
Click to expand...
Click to collapse
How I got stuck was I was having like extremely poor service and was waiting on a call back from them, and through reading what people said about them never calling I thought I was safe, about 30 minutes after I flashed cm7 a rep called and wanted me to go into epst and at that time I was so new to being a rooted user I had no idea it wasn't in aosp. So I tried the ## code and when she asked what happened I said nothing she said ok hang on while I flag your account. My first words to the rep was are you fu**ing kidden me! So I stabbed back by tethering to my ps3 while playing Modern Warfare lol
Sent from my myTouch_4G_Slide using Tapatalk 2
YoungCorruptionV2.0 said:
Can't return something rooted unless you want your account flagged lol
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
So...unroot before taking. As it says, there's an issue with reading the battery correctly. It's charging the battery, because when it goes into another phone, it shows the correct percentage.
It -has- to be a hardware issue. Unroot, RUU, whatever... there isn't an easy fix for this without messing with the hardware (which will likely result in ruining the device).
If the flex cables were shot, you'd all recommend the same thing. What's the difference with this?
There is a newer and easier way to unroot HERE
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
I bought this phone maybe two months or a month and a half ago. At the time, I had no idea that root was impossible. I also own a Play Store Galaxy Nexus, so after being so free to do what I wanted with it for so long, the One X was giving me anxiety fits (anxiety over a cell phone, yes I know).
I don't really need two phones, so I should sell one. Which one though? The HOX is a monster in every aspect, but I can't fiddle with it. The Nexus is so nice in that arena, but the camera is borderline putrid and the screen is sort of dark. Plus I have good eyesight, so the Pentile nature of the screen boasts its presence at every turn. It runs everything pretty well and gets updates very quickly. The development is second to none. But the HOX. That screen. That camera. It has LTE. That snapdragon. I'm going to have less "spending money" available to me soon, so I want the phone that's most futureproof. That's obviously the HOX. Software is important. So what do I do? Hold out for the next Nexus? Sell both and get a Galaxy S3? I really prefer the HOX over the S3, so I don't want to do that. If only I could root the damn thing and put CM10 on it like I have on my GNex. Damn damn damn. I guess I'll be patient and see if the heroes of legend at XDA can work their magic.
I sift through the forums reading about this and that. CM10 on the HOX has a bunch of wakelocks? Wifi problems? Man, is it worth it to wait or should I just sell this thing while the prices are good? AT&T is purposefully crippling my baby. The one phone I want and I'm at the mercy of damn AT&T. Why can't HTC have the sort of power necessary to stand up to carriers like that fruit company from California? If only.
And just two nights ago, BAM. I worked until 12:30AM and have to return to work the next day at ~4:30AM, not to mention wake up at 3:30 so I can shower and shave with time to pick up a coworker at her place. It's 1:30 and I really ought to get some sleep. But I'm not finished with this delicious beer yet. Guess I'll check XDA in the meantime. Oh god... "Exploit found" says the bounty thread. Welp, so much for going to sleep now. So after fighting with both my computer and my phone for a while, my bootloader is unlocked. I don't know how to root yet because this is my first HTC phone. But we're off to a good start. I get an hour and a half of sleep and come home from work, tired and miserable. Should I nap? Hell no, I need TWRP. To XDA! Hello, custom recovery. Now I need root. What's this? A flashable SuperSU .zip? Hmm... let's try it. Better install a root check app since I don't know how to tell if I have root otherwise. Success! Well damn it, now I'm ready to flash the CM10 zip from Goo manager. Oh, no I'm not. I have to flash the boot.img with fastboot first. I've never done this before (GS2 and Gnex were my previous phones) and I don't know what the hell S-On is, but whatever. Let's do it. Good Lord, it worked. I'm one step closer to the love child of the Gnex and HOX that I've been so long waiting to adopt. Now I can flash the CM10 zip? Alright, let's do it.
And here I am. This is what I've been waiting for. After switching my sim card between my HOX and GNex almost every other day, I can finally leave it in one phone for a while. The ROM I'm running is labeled "experimental," but it really seems to be anything but. Aside from some visual quirks and some in-call echo, I've had practically zero issues using this phone. The battery life is comparable to stock, and while it seems to be lacking some of the butter of the CM10 Gnex nightlies, it's just fine for me. Fast. Stable. Powerful.
So this is me gushing over the devs here at XDA. Thank you for all your hard work and dedication to righting what is repeatedly wronged by the juggernaut telecoms here in the US.
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
cool man , dont forget to try other roms! many of them are cm10 based, you should try paranoid android :good:
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
Lmao
Sent from my HTC One XL using xda app-developers app
What can I say. The OP is a showman haha.. awesome OP, glad to have you here in this awesome community
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
Lol that's just plain funny
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
still fraud. :'(
Sent from my One X using xda premium
To the OP, I felt the same type of excitement when I saw it. I appreciate the time and effort put into this exploit and anyone who may have helped. It's even more exciting that theres awesome people who freely release these to the public so that awesome ROMS can be put on. I was so ticked off with my locked bootloader I almost switched it out for a motorola atrix HD. The first time I took it back was legit though, it had the muffled voice syndrome, and the phone was only 6 days old, the corp store tried to give me a refurbished phone! ... I refused it and got a new one, and that one had battery issues, had to take it back a second time but finally got it straight right on the day of the root exploit. At the end of the week if I got any spare change I am definitely going to donate for the hard work it took and the time and patience.
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
LOL, good quote find.
On one hand yes, I can understand why a company may lock down a bootloader and I am sure many companies going forward may get the same dangerous idea. Maybe its true intentions is to protect people from bricking the phone or wasting their time with claims etc .. but on the other hand imagine if you bought a computer and Dell or HP comes in and says, well we locked down the firmware we dont want you putting any other OS in there but microsoft. Also, on top of that we dont want you using any other video cards besides an ATI card .. to prevent you from this we locked down the firmware. It's poisonous to creativity.
I believe in open source and feel saddened when we get locked bootloaders. I love the Android OS, I feel it should be completely open without any company interferences so that many great devs can continue to create and modify the existing OS/ROMs. Its a two sided coin.
I really am loving XDA, so much useful info, so many things to learn.
Lmao I nearly messed myself when I first saw that thread. That douche is never gonna live it down.
Sent from my HTC One XL using xda premium
Stories like that kind of worry me, I just got the phone and love playing with Nova Prime but have dug into rooting it yet until I read more about it.
Sent from my HTC One X using xda premium
Everyone is guilty of the childlike excitement you get when you successfully root a new phone and see that first Rom you want to try
:fingers-crossed: