Will Gingerbread bring centralized updates? - Android Software/Hacking General [Developers Only]

One of the biggest issues I see with Android today is that security bugs do not get patched until my manufacturer releases a new firmware, while very few enjoy OTA updates.
Will Gingerbread change that, so that all phones "with Google" will get patched more or less in realtime?

Probably not until all manufacturers decided to use just vanilla android, and I don't see that happening anytime soon. Htc, Moto, and Sammy, for whatever reason, insist on inflicting their custom skins on us, and updating those is what takes so long.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!

user7618 said:
Htc, Moto, and Sammy, for whatever reason, insist on inflicting their custom skins on us, and updating those is what takes so long.
Click to expand...
Click to collapse
I thought that's what Gingerbread would try to solve?
Therefore my question if bugs will be patched promptly by rolling out patches OTA.
It would even suffice to have a "android-patch-announce" mailing list I could subscribe to. I'd then download and update by myself.

As far as I'm informed Google only stated that the new Android UI will be so good that it's not necessary that phone manufacturers develop their own UI over it. I have nowhere seen in written that they are not allowed anymore to build them.
But I wonder why automatic updates are still not possible? I mean look at your notebook. You have Windows 7 on it and the manufacturers (Toshiba, Acer, etc.) add their own stuff on top i.e. like an enhanced Desktop and whatever, but the Windows update is of course still working.
Maybe the problem is that Android quickly grew the few years since it's existence in order to have a "fullly working system" like we have it now. Once the main structures of the platform are stable, maybe it's easier to adapt 3rd party software. But then, the switch from 2.1 to 2.2 is not very heavy, isn't it?
I hope as well there's a solution soon! It's very annoying! I have a HTC Wildfire with 1&1 brand (German phone network). First you have to wait until HTC provides the update to 2.2 but then you still can't use it because 1&1 have to update their software as well. Maybe just installing the HTC firmware but then you loose the warranty of your phone.... stupid **** really!

Related

Developers of ROMs

Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.
Agreed! (This text is just to pass 10 char limit)
Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.
but arnt all these builds just different attempts at getting a working 1.5 build?
Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.
well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!
Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.
momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?
Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave
I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.
Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.
As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.
momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave
I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.
Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.

Google Maps Navigation for CDMA Hero???

Has anybody gotten this to work on CDMA Hero's???
http://www.gadgetvenue.com/google-maps-navigation-works-usa-11233152/
1.6 only....we are on 1.5. Not going to happen.
As noted, requires 1.6+.
We will be getting 2.0 eventually, probably a few months from now. Keep your fingers crossed.
Why are we waiting?
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
5tr4t4 said:
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
Click to expand...
Click to collapse
I can't agree with you more. When I transfered to the android platform I was under the assumption that what u said supposed to happen was the case.
However I hear it's very difficult to build a 2.0 for hero.
You see the "drivers" that are in the hero right now will not work on 2.0. If you build the provided open source 2.0 rom, you will get an OS with no tie to the hardware. a map with gps a phone with no radio and a browser with no wifi. which will be useless to any one.
sm_x said:
You see the "drivers" that are in the hero right now will not work on 2.0. If you build the provided open source 2.0 rom, you will get an OS with no tie to the hardware. a map with gps a phone with no radio and a browser with no wifi. which will be useless to any one.
Click to expand...
Click to collapse
Uha, I know. The Linux guys warned us years ago about allowing proprietary drivers in Linux (see the old NVIDIA debate, for instance). So you have a kernel that can't talk to the hardware until manufacturer X says it can.
And so we wait for HTC or Qualcomm or whomever to release their drivers.
Sorry for the rant (and thanks for the solidarity, sm-x), this Google Nav thing just set me off. The hack-a-day progress on XDA is really wonderful but we should have real access to the code so we can make it better, not just reverse engineering...I can do that on my iPhone/iPod.
2.0 is out of the question without the binaries from HTC, but 1.6 should be doable with the 1.5 bits. It'd take someone with a lot of time and dedication, though.
kRutOn said:
2.0 is out of the question without the binaries from HTC, but 1.6 should be doable with the 1.5 bits. It'd take someone with a lot of time and dedication, though.
Click to expand...
Click to collapse
How about tricking the rom into showing itself as 1.6? Not sure what all that would entail tho
5tr4t4 said:
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
Click to expand...
Click to collapse
I also agree with this. I wrote up a little article about it:
http://www.thesearethedroids.com/2009/11/24/a-look-into-custom-ui/
well said gents

Google Goggles in Market?

I'm running Fresh 0.6 but Google Goggles is not showing up in it. Anyone else having problems with this?
If you haven't come across it yet, check it out. Very cool visual search app.
http://www.google.com/mobile/goggles/#landmark
It is very likely as with the new Maps, this is only compatible with 2.1 and will not show up in the market for phones with 1.5.
Sorry to break your heart. Google has taken it away from us.
Never Mind
Never mind...just read somewhere that its for 1.6 and up Looks very cool....
Hopefully 2.0/2.1 is just round the corner
Yup.. Here's hoping us Hero users will get an update sometime before next year :|
google goggles
yeah in the feed i read about it in said 1.6+ so cupcake is left out yet again...wow i cant wait for 2.1 to be stable.
Doh! The app seems very cool
Bummer
Yeah I tried to download it too when I saw it on Gizmodo. Seankk what do you mean you can't wait for 2.1 to be stable? Is there a way to get it loaded on our hero now? If so I'd like to play around with it.
Never mind I just read this thread.
http://forum.xda-developers.com/showthread.php?t=593015
Cannot wait for 2.1 on hero btw.
anyone know where i can get the apk, just to try?
This is bull**** ... an updated Maps and Goggles and Favorite Places all happen on the same day - yet we can't use any of them, because we're stuck on 1.5. What the ****!
And I know Eris will get 2.0 before Hero does, because Verizon is way more into Android than Sprint. UGH.
Damnit
Alright, this is getting ridiculous now. I bought a Google phone (it's emblazoned on the back for god's sake!) and can't use two of Google's flagship mobile apps, Navigation and now Goggles. Even when 2.0 arrives, there are sure to be more pointless delays like this in the future.
We have GOT to get off of the "waiting for carrier updates" ride as soon as is humanly possible. This is open source, right? Then why are we waiting and hacking? Let's demand the GPL code from HTC, fork it, get a vanilla 2.0/2.1 community build, and move on. The carriers and manufacturers are clearly not Linux people and should not be allowed to hold back development like this. On my Desktop Linux box I'm updating constantly. Every day there are newer, faster, better things. Waiting weeks for an optimization (or at least for the code to test it out) would seem absurd to any standard Linux user.
So far I've just been contributing ideas/suggestions (many thanks to the may excellent devs on this and other pages!!), but I'm going to set up a development environment here and see what I can do to get started....
Sorry for the rant (not my first on this board, I'm afraid) but my hopes for Android are being dashed day by day. "Open handset" my ass.
Amen, brother.
amen to that too.
5tr4t4 said:
Alright, this is getting ridiculous now. I bought a Google phone (it's emblazoned on the back for god's sake!) and can't use two of Google's flagship mobile apps, Navigation and now Goggles. Even when 2.0 arrives, there are sure to be more pointless delays like this in the future.
We have GOT to get off of the "waiting for carrier updates" ride as soon as is humanly possible. This is open source, right? Then why are we waiting and hacking? Let's demand the GPL code from HTC, fork it, get a vanilla 2.0/2.1 community build, and move on. The carriers and manufacturers are clearly not Linux people and should not be allowed to hold back development like this. On my Desktop Linux box I'm updating constantly. Every day there are newer, faster, better things. Waiting weeks for an optimization (or at least for the code to test it out) would seem absurd to any standard Linux user.
So far I've just been contributing ideas/suggestions (many thanks to the may excellent devs on this and other pages!!), but I'm going to set up a development environment here and see what I can do to get started....
Sorry for the rant (not my first on this board, I'm afraid) but my hopes for Android are being dashed day by day. "Open handset" my ass.
Click to expand...
Click to collapse
Start twitter bombing @sprint and @htc
Amen as well. What good is open source when you have to rely on proprietary code from the handset manufacturers? And time is clearly not of the essence for these guys. It's really disappointing that HTC's flagship phone is taking this long to update. It really feels like they don't give a ****.
Hey, I just found this article and thought I'd post it.
http://htcsource.com/index.php?option=com_content&task=view&id=791&Itemid=50
5tr4t4 said:
Alright, this is getting ridiculous now. I bought a Google phone (it's emblazoned on the back for god's sake!) and can't use two of Google's flagship mobile apps, Navigation and now Goggles. Even when 2.0 arrives, there are sure to be more pointless delays like this in the future.
We have GOT to get off of the "waiting for carrier updates" ride as soon as is humanly possible. This is open source, right? Then why are we waiting and hacking? Let's demand the GPL code from HTC, fork it, get a vanilla 2.0/2.1 community build, and move on. The carriers and manufacturers are clearly not Linux people and should not be allowed to hold back development like this. On my Desktop Linux box I'm updating constantly. Every day there are newer, faster, better things. Waiting weeks for an optimization (or at least for the code to test it out) would seem absurd to any standard Linux user.
So far I've just been contributing ideas/suggestions (many thanks to the may excellent devs on this and other pages!!), but I'm going to set up a development environment here and see what I can do to get started....
Sorry for the rant (not my first on this board, I'm afraid) but my hopes for Android are being dashed day by day. "Open handset" my ass.
Click to expand...
Click to collapse
Just an FYI many of the devs here are working on a version of the 2.1 Eclair or Flan update. They have gotten the system dump from a 2.1 GSM phone and are working on getting it ported to CDMA. So check that thread and try not to reinvent the wheel. Seems like the one thing they cannot get working is the Data. Text and Calls work, but useless without Data. From what i have gathered all that is very specific to sprint and is rolled into the kernel. Which we don't have yet, and without ground up building one we are kind of at a standstill.

This is ridiculous...

Anyone still on 2.1 is officially obsolete. Google has released a ton of new features for froyo and gingerbread users. Including google instant, new gmail app, and other things.
Which leaves 2.1 users with old software never to be upgraded again.
I still haven't flashed (due to warranty issues) but even if I did I would be upset because it still is based on buggy pre-release software.
Based on the epic 4g leak the froyo should be version 2.2.1 so new roms would be 2.2.1 instead of buggy 2.2
Why doesn't samsung care about their customers!
Yea, I share your sentiments. I tried most of the 2.2 leak ROMs, but most had troubles. The list of apps that don't work on 2.1 and below is growing. I wonder if Google Maps 5 will be the same way.
I really thinking about just buying an unlocked nexus s but then i realize its still samsung!!!
I returned a samsung tv i bought for my family for christmas because they suck so much ;D
The more I read about this (and the GPS malfunction), the more I think that when my Captivate arrives tomorrow I may just take it into an AT$T store and demand a refund and contract cancellation.
What we need is a Samsung Customer Service number we can start calling to voice our opinions. Any have a good Samsung number for this or a similar purpose?
Yes more than half of android devices are "obsolete"...
Return it? Because your too lazy to flash your phone with functional software instead of the junk Samsung and att gave us? I've been rocking the beta cm 6.1 for quite awhile and blows the doors off any 2.1 variant that was out there.....and as far as voiding your warranty its almost impossible to brick these phones so its completely easy to flash back to an out of the box state. So quit whining. This is what makes android so great. Take a phone with amazing hardware with crappy software and put amazing software on it
Sent from my SAMSUNG-GT-I9000 using XDA App
For one, I'm not lazy or whining. I shouldn't have to flash my phone to get basic functionality out of it. The GPS should work without my having to invest in searching through a myriad of unauthorized solutions and risk not only voiding my warranty, but bricking my phone. If I wanted to put this much effort into making a phone work I would have stuck with WinMo 6.5 and my Tilt 2, which I know inside and out already. I moved to Android hoping I'd no longer have to spend so much time dicking around with my phone just to get things to work. You know, the whole "Droid Does" marketing ploy? The main reason I agreed to buy this phone was because I read on several different sites where Samsung said they were definitely going to update it to Froyo. I understand that their timetable may be off, but they should at least keep their promise. Is that too much to ask or expect?
Samsung promised Froyo by the end of the year for the US Market. They still have a 20 days. Their stance has not changed, so I don't see what anyone has to complain about.
As for GPS mine works as good as the one on my Bravo - my Tracks, Turn by Turn are the same. If your GPS has problems, take it back. If you try multiple phones and still have a problem, then make them switch you to another phone.
everyone knows they won't make the end of december date
It's not that I don't want to try custom ROMs. However, all the custom ROMs are built on leaked (and often buggy) Froyo ROMs. The sooner AT&T releases an official release Froyo ROM, the sooner we can get a stable (or more stable) custom Froyo ROM....hopefully they release the source code too. There's code in the custom ROMs that comes from all sorts of other ROMs lol
Ditto^^^ Well, according to Mr. Smalls, we're just lazy, whiny jerks with no valid excuse for not wanting to use a custom ROM on our phones.
emuneee said:
It's not that I don't want to try custom ROMs. However, all the custom ROMs are built on leaked (and often buggy) Froyo ROMs. The sooner AT&T releases an official release Froyo ROM, the sooner we can get a stable (or more stable) custom Froyo ROM....hopefully they release the source code too. There's code in the custom ROMs that comes from all sorts of other ROMs lol
Click to expand...
Click to collapse
try axura.. VERY stable, fast, practical rom with good themes. its a work of art. been rocking it with very minimal issue (less issues compared to stock).
Miami_Son said:
For one, I'm not lazy or whining. I shouldn't have to flash my phone to get basic functionality out of it. The GPS should work without my having to invest in searching through a myriad of unauthorized solutions and risk not only voiding my warranty, but bricking my phone. If I wanted to put this much effort into making a phone work I would have stuck with WinMo 6.5 and my Tilt 2, which I know inside and out already. I moved to Android hoping I'd no longer have to spend so much time dicking around with my phone just to get things to work. You know, the whole "Droid Does" marketing ploy? The main reason I agreed to buy this phone was because I read on several different sites where Samsung said they were definitely going to update it to Froyo. I understand that their timetable may be off, but they should at least keep their promise. Is that too much to ask or expect?
Click to expand...
Click to collapse
Am I correct that you don't even have your device as you're typing that?! Try it first..a lot of the stuff you read isn't what you will experience. I.E.: my gps has worked a charm since I picked mine up in mid October..it's an excellent device. I've had a Samsung DLP for more than 2 years and it works flawlessly. People like to rant..find out for yourself for chrissake. It's nice to be happy with a cell device for the first time in awhile for me..only complaint is att dragging heels on 2.2. I'm too busy and old (55) to have the energy to do all that stuff that many do..but it's also nice to know that if I get tired of waiting and get a wild hair, I'll root and flash when I'm good and ready. Meantime I think the Captivate is a great companion
From what I've heard, I think that it might be the carriers that are delaying the update. Don't know if this is true or not but I kinda doubt this is Samsung's fault.
@fldude, Thanks for the encouragement. I used to love fiddling with my WinMo phones and I enjoyed modding my Tilt 2 to where it runs great and does (almost) all I ask of it. I'd still be using it if WinMo wasn't a dead platform and the thing wasn't so laggy. That saidI was hoping the switch to Android would mean I finallly would have a phone that I could tinker with if I wanted to, but didn't HAVE to, like WinMo. I guess reading through these forums exposes one mostly to the negative since most people only post when having problems. I brushed most of it aside, but the GPS issue really stood out because I use GPS-enabled apps a lot and it works so well on my Tilt 2. I can't wait for the Cap to get here tomorrow so I can start playing with it. Thanks to running XDAndroid on my Tilt 2 I already have some idea of what to expect and how to use it.
I will say this, reading about rooting and flashing of Android, kernel this and apk that is a lot more intimidating than working with WinMo. I never hesitated to edit my registry, but modding Android sounds pretty scary.
By the way, does fl mean you're a fellow H-D rider?
alphadog00 said:
Samsung promised Froyo by the end of the year for the US Market. They still have a 20 days. Their stance has not changed, so I don't see what anyone has to complain about.
As for GPS mine works as good as the one on my Bravo - my Tracks, Turn by Turn are the same. If your GPS has problems, take it back. If you try multiple phones and still have a problem, then make them switch you to another phone.
Click to expand...
Click to collapse
They were previously quoted saying by the end of November. There was that whole JH7 fiasco. And your argument doesn't change what he was saying. His whole point was that he shouldn't have to **** around to make it work. It just should.
david717;971 His whole point was that he shouldn't have to **** around to make it work. It just should.[/QUOTE said:
Ummm, I'm stock, never rooted, make phone calls, email, navigate with gps, surf the web, play games, usw.. How is this not a working phone? By my calculations this phone does "just work" and has since I pulled it out of its box in July.
I too am waiting for, now, v2.2.1...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Before I bought mine I knee of the GPS issues and swwvthat a fix was coming. It still is. Besides the GPS my phone just works. Texting browsing g music video all just worked email too. Running the froyo leak my phone now completely 100% percent works. I'm excited to see how much more stable the official release will be.
Sent from my SAMSUNG-SGH-I897 using XDA App
Also Frustrated
I have been following the forums regarding the so called Froyo release and I have to say that I am rather frustrated as well. I actually called AT&T last week to complain about the delay with Froyo with Gingerbread's release within a few weeks. Not to mention Honeycomb on the horizon.
In speaking with one of the techs he also shared his frustrations and was hoping that it would be released in early January. I told him that it was understood that it would be release at the end of the year and he confirmed that same understanding. However his sources revealed that it is now for early January. Let's hope this is true, but as you all know we have been given so many empty promises.
Furthermore,I read an article that Samsung is undecided whether to release Gingerbread for the Galaxy devices. For a product that has been so popular and successful, what are they thinking? Or maybe they are not!!
Either way my fingers and toes are crossed for Froyo for now...

Spam HTC's Facebook. Let them know we want ICS.

http://m.facebook.com/HTC
Facbook.com/HTC
Ok, since HTC won't answer our questions for an ICS Update. Why don't we just constantly ask them on Facebook? I feel that everybody on XDA want ICS. If we get an Offical ICS Kernel. We can have a massive jump on Deving. Proper soucre for 1080p video, fullying working AOSP roms. What else is there to do? Wait? If we stay quite, they'll think we sont care. We need to let them know we want ICS. So I ask of all the XDA Doubleshot users. Just constantly ask HTC for ICS on the Mytouch 4G Slide. Ask a lot, ask 10 times a day. Ask 1000 if you can. If 10 people post 5 times that's 50 post. 50 post HTC will see knowing we want, and need ICS.
I thank those who will do this. Let's help our devs out, and get those AOSP lovers a fully working Rom.
i agree with you altough i don't use facebook.
but anyway the point is that just staying quiet won't do any good to us, we have to make them know we actually want ICS because from the looks of it, they have no intention of updating our phone
I thought it was up to T-mo though not HTC. So would this really do anything?
ICS is T-Mobile's fault, not HTC's. HTC can only release an update if T-Mobile calls for it.
tl;dr: Spam T-Mobile for ICS
both t-mobile and htc are involved in the decision, but the work is done 100% by htc
anyway, i don't think we would get something out of t-mobile but maybe from htc yes.
i would point out that while it's a t-mobile branded phone it still has the HTC logo on the back and wasn't HTC one of the companies that adhered to the Google initiative to keep phones updated for atleast 18 months from release ?
those are the points to work on, hit HTC's pride and *maybe* we could get something back. T-mobile couldn't care less imo
i just asked t mobile on their Facebook page and they said this T-Mobile is committed to enhancing customers’ experience with our devices, including providing upgrades to the latest Android operating system -- Android 4.0 (Ice Cream Sandwich). We are actively working with our OEM partners to ensure that a number of eligible T-Mobile devices are upgraded to Android 4.0 in the coming months and will communicate updates as we have additional details to share. ^CL
wiswis said:
i just asked t mobile on their Facebook page and they said this T-Mobile is committed to enhancing customers’ experience with our devices, including providing upgrades to the latest Android operating system -- Android 4.0 (Ice Cream Sandwich). We are actively working with our OEM partners to ensure that a number of eligible T-Mobile devices are upgraded to Android 4.0 in the coming months and will communicate updates as we have additional details to share. ^CL
Click to expand...
Click to collapse
At least a 1Ghz Processor [X]
More than 512Mb Ram [X]
Atleast than 400Mb of System Mem. [X]
Some basic things needed for ICS. So we are in the ranks of an upgrade. If T-Mobile gives us a ICS update I'll never use another carrier for the rest of my life.
It's Always Sunny in XDA
AgentCherryColla said:
At least a 1Ghz Processor [X]
More than 512Mb Ram [X]
Atleast than 400Mb of System Mem. [X]
Some basic things needed for ICS. So we are in the ranks of an upgrade. If T-Mobile gives us a ICS update I'll never use another carrier for the rest of my life.
It's Always Sunny in XDA
Click to expand...
Click to collapse
don't get too excited. that's just some standard PR response. We should keep going until we get some official and specific information about our phone
Everybody do what I did and ask them to leak us out a ROM.
Posted from Spaceball One
Good news? The newest update coming on March 19th (Tomorrow) is a major fix. Making the stock very usable. The same update is coming to the Mytouch 4G, being th last it will get. T-Mobile is still going to update our phone. Since this new update is going to fix all bugs. That only means a OS update can come. So those on stock roms have a nice update coming.
Also we have hope now. Mabey we'll get a leak??
It's Always Sunny in XDA
marc12868 said:
I thought it was up to T-mo though not HTC. So would this really do anything?
Click to expand...
Click to collapse
It is handled by T-Mobile. HTC might already be developing an ICS ROM for our phone, but their lips are sealed until they get word from T-Mobile that they are allowed to release it or even announce it. Even then, such an announcement would be done by T-Mobile anyways.
Braccoz said:
both t-mobile and htc are involved in the decision, but the work is done 100% by htc
anyway, i don't think we would get something out of t-mobile but maybe from htc yes.
i would point out that while it's a t-mobile branded phone it still has the HTC logo on the back and wasn't HTC one of the companies that adhered to the Google initiative to keep phones updated for atleast 18 months from release ?
those are the points to work on, hit HTC's pride and *maybe* we could get something back. T-mobile couldn't care less imo
Click to expand...
Click to collapse
And same thing with the myTouch 4G. They got updates slower than a pig through molasses. They're still getting one last update after being released for 16 months. It took them forever to get Gingerbread, but they still got it eventually. No need to be so negative. The MT4GS hasn't even been out for a year.
AgentCherryColla said:
Good news? The newest update coming on March 19th (Tomorrow) is a major fix. Making the stock very usable. The same update is coming to the Mytouch 4G, being th last it will get. T-Mobile is still going to update our phone. Since this new update is going to fix all bugs. That only means a OS update can come. So those on stock roms have a nice update coming.
Also we have hope now. Mabey we'll get a leak??
It's Always Sunny in XDA
Click to expand...
Click to collapse
We'll probably get an ICS ROM, but don't expect it any time soon.
http://www.tmonews.com/2012/03/main...for-t-mobile-mytouch-4g-and-mytouch-4g-slide/
If you look at the update it is the paused mr that messed up the HTC unlocker. But it will fix somethings.
Sent from my HTC HD2 with Sense 3.5 using XDA Premium App
AgentCherryColla said:
At least a 1Ghz Processor [X]
More than 512Mb Ram [X]
Atleast than 400Mb of System Mem. [X]
Some basic things needed for ICS. So we are in the ranks of an upgrade. If T-Mobile gives us a ICS update I'll never use another carrier for the rest of my life.
It's Always Sunny in XDA
Click to expand...
Click to collapse
Honestly, that's almost every device since ye olde Nexus One. That doesn't mean a thing. HTC and T-Mobile damn well know our phone can handle anything they throw at it.
Posted on HTC's wall. Although I think emailing HTC and T-Mobile directly will be much more effective. Facebook posts are good for publicity, but no one at either company is actively reading them.
---------- Post added at 05:19 PM ---------- Previous post was at 05:10 PM ----------
WOW, ok maybe I was wrong about them replying. Commented back on my wall post about 10 mins later
Hey, XXXX. We're still working on our portfolio to see which devices are suitable for the upgrade. We will have more information in the coming weeks. You can check out our latest note on ICS here: http://bit.ly/yTJiXX.
i will do this since im in love with ics!!!!!!
That's probably helpful, it is true that everything is assumed to be fine unless people say otherwise, I wouldn't prioritize a project I didn't think anyone cared about (from a business standpoint)
I don't have a facebook, and don't intend on getting one, but I know some people who do and can probably talk them into posting an occasional message about it.
Just try to be polite and inquisitive, don't use profanity, and use real words and not internet shorthand ( lol...omg...and other childish crap like that).
You are interacting with a business and in a business sense, the customer-manufacturer relationship is a business one, you're not talking to your friends on your couch.
If you are gonna do it, might as well try to be as successful as possible and being rude, crude and posting hateful or illegible messages will have a negative impact on your campaign. Not saying you are, but just putting it out there for the people who will read through this and act on the thread.
----
AgentCherryColla said:
... If T-Mobile gives us a ICS update I'll never use another carrier for the rest of my life...
Click to expand...
Click to collapse
After all the recent back and forth between T-Mobile customer 'service' and myself I am so thoroughly disgusted with T-Mo from a customer standpoint that i'm more then casually running the numbers on the best way to sever our relationship.
I've worked a call center before, i'm always polite and patient over the phone, and AgentCherryColla I see myself in that quoted line - don't ask for much and set a low-bar for the 'i'm a loyal customer' mark... so that as long as they don't rock the boat it's smooth sailing. But...
...given that I still have at least one MORE customer service call ahead of me to continue working out my issues with them and what the last few have been like ... I really hope it doesn't come down to T-Mobile deciding to do something for their customers. In my experience that goes completely against their company philosophy... this is at least what they've taught me from direct interaction.
I think as soon as I can orchestrate it i'll be on simple mobile or someone like that instead (as opposed to 'in addition to').
I've got more faith in tbalden primarily right now, but also anyone else from the open source community that puts time into bringing us ICS from source. What we really need is ICS kernel source from HTC so getting through to HTC is an important step, they can encourage T-Mobile to give the nod a lot more then we can.
Hate to be the squeaky wheel just to get some grease, but HTC customer service is the complete polar opposite of T-Mobile. HTC has done everything possible, above and beyond, every time i've had to interact with them. Stellar company and I highly recommend them to everyone I meet...and i'm done paying them so they already got THEIR money, yet still do their best to treat me well and help me out. I wish more companies were like that, they're getting harder and harder to find.
Definitely not trying to be negative, and all we need is HTC ICS kernel source for the doubleshot, Google ICS source gets us the rest - but we'll never see any ICS kernel source from HTC without an ICS ROM so it looks like we need to buy the whole pie just to get the slice we want.
Good job with the letter campaign, if everyone keeps it clean and professional I think it'll help!

Categories

Resources