Related
Can you please get Froyo to the Galaxy S owners!?!
http://www.engadget.com/2010/08/11/motorola-droid-android-2-2-froyo-ota-updates-are-go/
I'd be willing to hold off on 2.2 if they would fix the gps, the app lag, and the craptastic battery life.
I'm willing to bet that at&t are the ones holding this up, adding their "software."
Sent from my SAMSUNG-SGH-I897 using XDA App
behrouz said:
I'm willing to bet that at&t are the ones holding this up, adding their "software."
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Have to agree, AT&T probably needs to add it's crapware before releasing this.
Sent from my SAMSUNG-SGH-I897 using XDA App
Didn't they already announce that it wouldn't be available till September for the international GalaxayS?
Are you kidding me?
Captivate has been out 3 weeks... and you think it should have Froyo already?
I can wait. Let Samsung get it right first.
Froyo will be out in sept for I9000. We then have to wait for At&t to update and release it. If a froyo kernel is leaked for the captivate we can use the I9000 froyo rom.
joeybear23 said:
Are you kidding me?
Captivate has been out 3 weeks... and you think it should have Froyo already?
I can wait. Let Samsung get it right first.
Click to expand...
Click to collapse
That is what I was thinking. A lot of people think it takes a couple of minutes to crank out the new update to froyo for the Galaxy S phones. It takes time and a lot of coding and debugging to ensure maximum compatibility and stability with the new Froyo update. I prefer to wait and make sure the kinks get worked out.
At least we know they are working on updating to froyo since we have seen various I9000 froyo leaks, so now the best thing to do is wait and make due with what we have.
I have to agree with the concesus here, this phone is already blazing fast and its going to take time to port froyo to operator specific phones. Motorola just needs to deal with verizon whereas Samsung is dealing with 8 carriers ALL with different hardware... Not something that is easy.
Best thing you can do turn off live wallpaper and install LauncherPro and call it a day. Increase battery life and speed... Done and Done!
slider2828 said:
Motorola just needs to deal with verizon whereas Samsung is dealing with 8 carriers ALL with different hardware... Not something that is easy.
Click to expand...
Click to collapse
Make that 110 carriers. However, the core functionality of all these phones are almost the same. I'd say (just a guesstimate) around 95% of the hardware are similar. The software side maybe more different as pre-loaded software have to be considered.
OMG, Why don't we just go find the old threads for the blackjack and blackjack II WiMo upgrades. Do a little find and replace, paste the results here and stop wasting our time having this conversation again.
It will be realeased when it is released. Samsung is notorious for slow updates so we have to deal with it. After all we are all here on XDA which means almost every last one of use will flash a Froyo ROM long before the official update is released.
I was at the mall yesterday went to ATTto ask if they new when update is coming out. He said GPS will be end of Aug and Froyo is coming Mid-Sept.
ViniD said:
I was at the mall yesterday went to ATTto ask if they new when update is coming out. He said GPS will be end of Aug and Froyo is coming Mid-Sept.
Click to expand...
Click to collapse
And if you call ATT I bet they will give you some type of date. I will then gaurantee you that date will come and go with no update. This is par for the course when waiting for samsung OS updates on the ATT network. I think it was the blackjack I was waiting on. There were several dates, all confirmed by an ATT Rep. It took well over 6 months from the first date before we saw the update. So don't hold your breath.
Just got off the phone with samsung. Tech support said gps fix for sure by end of sept. And froyo as soon as a few days to no more than few months. Also the update will come straight from them no att involved. Sept. 21
Fro-noes!!
Froyo update. As soon as a few days to no later then a few months. Thats like me saying, Yeah........Ill get back to you Mr. President. Within a few days, but no later then 4 years when your run is over with. Garenteed!
Every time someone calls Samsung or walks into an AT&T store and asks about fixes and updates, we get a slightly different answer. A dozen calls will yield a dozen different answers. The reality is that none of the people you can get to through the normal channels will know diddly squat about the actual release schedules. If we're lucky, the better than average rep/support tech will hear something about it a few days before it happens at best.
To get the real schedule, we need inside information. We need a Deep Throat! Someone on the test team at AT&T and someone on the dev/QA team at Samsung.
ianwood said:
To get the real schedule, we need inside information. We need a Deep Throat! Someone on the test team at AT&T and someone on the dev/QA team at Samsung.
Click to expand...
Click to collapse
What if the dev/QA team at Samsung/ATT doesn't even have a schedule yet? This may sounds crazy but it is possible.
Remember that Galaxy S UK announced their Froyo update schedule 3 months ago. US division, on the other hand, still hasn't announced anything. Is it reasonable to assume the wait for Froyo update will be at least another 3 months?
ayoung614 said:
Just got off the phone with samsung. Tech support said gps fix for sure by end of sept. And froyo as soon as a few days to no more than few months. Also the update will come straight from them no att involved. Sept. 21
Click to expand...
Click to collapse
I have been checking the Samsung site nearly daily for a week or so because their tech support also told me it would be available on their support site. However the last few days my bookmarked page is 404 and drilling down through the web site comes up dry also on downloadable Captivates stuff.
mwxiao said:
What if the dev/QA team at Samsung/ATT doesn't even have a schedule yet? This may sounds crazy but it is possible.
Remember that Galaxy S UK announced their Froyo update schedule 3 months ago. US division, on the other hand, still hasn't announced anything. Is it reasonable to assume the wait for Froyo update will be at least another 3 months?
Click to expand...
Click to collapse
In all likelihood, it is part of their deal with AT&T to supply certain updates within certain time frames -- standard practice. It will also need to be factored into Sammy's development schedule as it sounds like their devs are going to be quite busy with different Galaxy S updates. There's probably only a couple dozen people who actually know first-hand what those dates are.
Few months...sounds like next year to me. Hopefully not, I really want Froyo on it.
whats the huge advantage of having 2.2? really whats so big about it
How many times are we going to have this same thread with the same responses and questions???
Ill believe a GPS fix when we have it, not a second before
Sent from my SAMSUNG-SGH-I897 using XDA App
AsSiMiLaTeD_77 said:
How many times are we going to have this same thread with the same responses and questions???
Ill believe a GPS fix when we have it, not a second before
Click to expand...
Click to collapse
OMG I'm currently downloading something from the update menu in the phone.
Update: OMG It just finished the download and is 50% through the update.
Update: OMG it went to 100% and said "update is failed." Is this because I'm rooted?
Update: Unrooted to try again and it don't let me re-update. The "check once/24hrs" deal is bull**** yO` Screw you ATT
I'm not sure about the rest of you Captivate owners, but mine has been undergoing a serious update for the past 2 hours. The first update I noticed was to Kies Mini from v10082.8.1 to v1.0.0.110104.1. I couldn't upgrade using Kies mini. Instead, Kies mini simply updated itself.
After seeing this, I performed a Phone update from my Captivate itself and it's still going at it.
Let us know if it is froyo
Sent from my SAMSUNG-SGH-I897 using XDA App
not to burst your bubble, but it probably isn't, for like the millionth time if official Froyo is released you will hear about it, stop being so optimistic whenever a kies update comes out. Trust me when this thing hits it'll hit hard, you won't not know lol
Sent from my bullet proof phone
phoney_stuff said:
I'm not sure about the rest of you Captivate owners, but mine has been undergoing a serious update for the past 2 hours. The first update I noticed was to Kies Mini from v10082.8.1 to v1.0.0.110104.1. I couldn't upgrade using Kies mini. Instead, Kies mini simply updated itself.
After seeing this, I performed a Phone update from my Captivate itself and it's still going at it.
Click to expand...
Click to collapse
My Kies mini updated sometime last week to:
SAMSUNG Kies mini Application v1.0.0.10104_1
It might be in preparation for the froyo update but not here yet.
Nope!
Just attempted OTA and no new firmware and then did Kies mini and latest is jh7 sorry.
phoney_stuff said:
I'm not sure about the rest of you Captivate owners, but mine has been undergoing a serious update for the past 2 hours. The first update I noticed was to Kies Mini from v10082.8.1 to v1.0.0.110104.1. I couldn't upgrade using Kies mini. Instead, Kies mini simply updated itself.
After seeing this, I performed a Phone update from my Captivate itself and it's still going at it.
Click to expand...
Click to collapse
Many posts about Kies Mini update last week.
When Froyo does drop you'll see all kinds of articles on the regular internet sites.
Added: I'm still betting on St. Patrick's Day!
those #'s refer to KIES software versions.
It is simply and update for your Kies desktop software......nothing to do with firmware for your smartphone.
I'm still going for Christmas - although they had said by end of November... so we still have what? 2 more days at this point
avgjoegeek said:
I'm still going for Christmas - although they had said by end of November... so we still have what? 2 more days at this point
Click to expand...
Click to collapse
Actually - the date for US has always been "by the end of the year" as reported by SamsungUSA twitter and facebook. It was the international Galaxy S (i9000) that was end of November. Many sites interpreted that to mean us to as our phones are also "Galaxy S".
My bad... false alarm. Nothing to see here. Move along.
I'm still puzzled why both Kies mini and my phone took ages to do whatever it did. Whateva! I want some Froyo!
Well all signs point to very soon. Samsung said we would get it by the end of the year, which means in less than a month. There was also a tip a couple weeks ago that Captivates running Froyo out of the box would go on sale on the first Sunday in December and the OTA would begin rolling out possibly the Monday after (12/6).
Can we all agree to post news about a Froyo update AFTER you actually get the OS on your phone?
It seems like every other day someone posts news that they have been notified/downloading an update.
skinien said:
Can we all agree to post news about a Froyo update AFTER you actually get the OS on your phone?
It seems like every other day someone posts news that they have been notified/downloading an update.
Click to expand...
Click to collapse
THIS is the best advice anybody has given on the oft repeated subject - +2 for this person...
Speaking of the new version of Kies... Since mine upgraded, it won't let me check for updates while in debug mode. When I take it out of debug mode, my PC doesn't see my phone... Any ideas?
You're chasing after a Unicorn people.
MikeyMike01 said:
You're chasing after a Unicorn people.
Click to expand...
Click to collapse
Not to mention stock froyo would be a Unicorn with half a horn
gk527 said:
Speaking of the new version of Kies... Since mine upgraded, it won't let me check for updates while in debug mode. When I take it out of debug mode, my PC doesn't see my phone... Any ideas?
Click to expand...
Click to collapse
What os are you running? If it Win 7 x64, this is what I run, then you could try a fresh install of Kies. Scrub the system of all things Samsung (apps, drivers, etc..) and then do a fresh install of Kies. Let it install the drivers. Once complete reconnect phone and let Windows reinstall drivers for device. Then see if you can get the computer to see the phone.
If that doesn't work, there was a post about a patched .dll that worked for some. Search for "Kies doesn't recognize my phone".
cappysw10 said:
What os are you running? If it Win 7 x64, this is what I run, then you could try a fresh install of Kies. Scrub the system of all things Samsung (apps, drivers, etc..) and then do a fresh install of Kies. Let it install the drivers. Once complete reconnect phone and let Windows reinstall drivers for device. Then see if you can get the computer to see the phone.
If that doesn't work, there was a post about a patched .dll that worked for some. Search for "Kies doesn't recognize my phone".
Click to expand...
Click to collapse
I am running Windows 7 Ultimate x64. Thanks for the information. I'll give it a try.
alphadog00 said:
Actually - the date for US has always been "by the end of the year" as reported by SamsungUSA twitter and facebook. It was the international Galaxy S (i9000) that was end of November. Many sites interpreted that to mean us to as our phones are also "Galaxy S".
Click to expand...
Click to collapse
Maybe their "by the end of the year" is lunar calendar year... which will put the release at 2/2/2011.
I sent them an email a couple of days ago explaining crap thats going on with the phone and how Froyo 2.2 would from what i understand fix most of the problems etc etc. I just wanted to try again to find out about a date. Well i got an email back from tec. upport saying they are glad to announce that the 2.2 update IS available and to call their 800 number for help if i had problems installing. but clicking on the link just brings me to the old FAQ page that they took down. Come on Samsung get a freaking clue. I don't understand why they would send this out and not be true?????
(so maybe things will be rolling out today then because after rereading email i noticed their central time which is 3 hours behind me. So right now my time there still closed) Fingers crossed
Ok so just got of the phone with Samsung. Acording to them and the information they have in their office Froyo 2.2 IS OUT but because theres a problem with the site we don't can't download it yet lol Samsung needs to really get an Fing clue.
I'm pretty sure you need to install that with Kies Mini if it is, indeed, available.
JRd1st said:
I'm pretty sure you need to install that with Kies Mini if it is, indeed, available.
Click to expand...
Click to collapse
Nothing showing up on Kies Mini eather. So again am hoping that things will start rolling out as soon as they open at 9 central time.
I saw another post at AT&T official forum about multiple Samsung reps claim the 2.2 for Froyo is avialable and directed to the same link. Looks like Samsung already trained or released information about Captivate 2.2 release internally, a bit prematurally. So, it seems our UCKB1 ROM will be the official ROM after all. It is just waiting for AT&T to give the final nod.
<--- not holding his breath... Plus, the more I think about it, at this point... What's the point? I mean, 2.2 is rapidly aging and I'm not aware of any newly released devices coming out with 2.1 anymore - They've all got 2.2, which means that 2.3 is the next step.... and with the excellent development we already have, running stable 2.2 is already a reality! I want the update just so the companies are held to their promises, but as for an official 2.2; I'm not going back to ATT bloatware and half ass GPS.
Tried OTA update and it just hung......
I tired to go into media hub yesterday just to see if i missed it being fixed and it hung on checking for update. Checked phone for OTA and it also hung on checking for update. funny thing is about 4 days ago everything was working just fine. Im about to get on the phone with ATT and ***** about the email and when samsung opens and nothing happenes today will be on the phone *****ing about sending false emails to people.
So basically Samsung has just changed the lies from "It will be out soon" to "It's out now but you can't have it"! Way to go Samsung!
UCKB1 has a working media hub. If I were you I'd just install that. It'll probably end up being the official build anyhow.
Bunch of crap Samsung is. wow.....
Just got done talking to live support. what a joke. i have a dam email saying it's out. if you call and talk to someone they say all the info they have says it's out but live says its not and gives you the say crap as before about no info right now. Someone over there needs to get their head out of their ass and get a CLUE.
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