• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Android 2.x on Galaxy

yes, the task was kinda stupidly named, since 3d has always "worked", just that without hw gfx acceleration it's been pretty useless
 
Yes I just read on Drakaz's forum that 3D is required for the camera, I've no idea why, but it is. So I guess this is one of the big blocks that was preventing the rest of GAOSP from being completed therefore hopefully we'll have a fully working 2.1 on our phones. So indeed this could be big news, great stuff.
this is why you should read, follow and understand the the project you are wanting to work before making a comment putting it down.
yes its laggey, its early stages yet and the whole os has not been optimised and tweeked. its early stages however this is a huge step toward getting stuff done.
the gallery works although is a big resource but were dealing with a handheld that has really bad memory specs so what do you want?
 
this is why you should read, follow and understand the the project you are wanting to work before making a comment putting it down.
yes its laggey, its early stages yet and the whole os has not been optimised and tweeked. its early stages however this is a huge step toward getting stuff done.
the gallery works although is a big resource but were dealing with a handheld that has really bad memory specs so what do you want?

:) Well in an ideal world that'd be the case, but I do not have the time or the knowledge to read and understand everything that is going on. I read more than most users but am way behind most of you guys. In the end I just want my phone to work somewhere near the capabilities I thought it was going to have when I bought the bloody thing!!!

So here's another uninformed and ignorant question. Is this stuff new with 2.1 (the 3D & hardware gfx) - ie. was it not in 1.5/1.6 or was it just something that was preventing them from moving forward in GAOSP? In other words will things be smoother and faster (in yet another ideal world when it's all optimised and tweaked) with 2.1 or will it be much the same speed as what we currently have (albeit with lots of lovely new features).

I just wish Samsung would eat humble pie and work with Drakaz to get 2.1/2.2 working officially on our phones.
 
it would be more like it is now but with the features and additions of 2.1
i dont think you can get much faster than galax0 1.6.3.3 as its built for overclock and the kernal is heavily tweeked
 
Just posted this on SamsungFirmwares site:

Re: For I7500 Android 2.x (Official or UnOfficial) ROM

by porga on Wed Jun 09, 2010 8:56 pm
This post is for Administrator of this site: Samsung admin.

You wrote on twitter that Samsung will not update i7500 because of insufficient hardware.

Since you have connections inside Samsung, please send them mail to explain this:

- This is official statement that T-mobile myTouch 3g will have FroYo 2.2 update
myTouch3G Users, Your Wish Is About To Come True | TmoNews - Unofficial T-Mobile Blog - News, Videos, Articles and more

- This is myTouch 3g hardware info where we can see that it is same machine as i7500, even worse
http://www.gsmarena.com/t_mobile_mytouch_3g-2848.phphttp://www.gsmarena.com/t_mobile_mytouch_3g-2848.php

Please, send them mail with this information I wrote here, we are all very curious what will they say about this
icon_razz.gif
 
if you can edit the post, you might wanna add that the galaxy is still being sold, so dropping support without a valid technical reason should be unacceptable
 
i wonder why this issue (us not getting any updates) is kept so quiet, this is a popular handset for chrissakes. i follow twenty-something various android news websites via google reader and browse through tens of news every day, there's been nothing (literally nothing) about galaxy for months. recently the whole behold 2 not getting an update was quite popular, but that's it. just the usual information about many other phones getting 2.1 or being promised 2.2 and zero updates for us, nothing new
 
omg people are you that naive? the true reason isn't the hardware, it's their lack of will to make the update, you've seen their response on the last pikacz's letter
even if the handset is capable of supporting either OS version, there are no plans to incorporate either version in the Galaxy
you think you're smarter than samsung and want to humiliate them, show them they're wrong or something? they don't give a shit about it. just accept the truth that the only chance to get anything usable on Galaxy is drakaz and he's the guy who needs to be supported. and there's high chance we're getting at last fully functional 2.1 gaosp in near future. and really, you think they're able to make better firmware than drakaz?
 
That is not the point sado01. The point is to show on as many places which people read that Samsung lies to its users and offer arguments for it. Now we have solid one. So people, spread the word about this. Help others not to make mistake with new Samsung phones.
 
That is not the point sado01. The point is to show on as many places which people read that Samsung lies to its users and offer arguments for it. Now we have solid one. So people, spread the word about this. Help others not to make mistake with new Samsung phones.

exactly, there's no point arguing. i'm never getting a samsung phone in the future, no matter how cool it is (galaxy s seems tempting, but i have to say no). the safest choice (regarding future updates) is to get a htc and that's that
 
but surely the point Sado1 and other are trying to make is that you are wasting your time. the people that cvare about what you have said and will be listening are the android samsung users that have already been burned and will not be reinvesting
if you think there will be some kind of revolution because of our efforts to shame samsung then you are mistaken.

if it helps you feel; better cos you feel youve voiced your annoyance then i cant take that away from you but weve been screaming for a year. its time to let go and take our device where we want it to go as clearly they wont help us
 
if you think there will be some kind of revolution because of our efforts to shame samsung then you are mistaken

i'd say it probably has had some effect
just look at any recent engadget (a hugely popular site) article about an upcoming samsung android device (mainly the galaxy s that is) - half the comments are about how samsung's customer support sucks and it's the only reason why someone wouldn't buy the device in question
 
i'd say it probably has had some effect
just look at any recent engadget (a hugely popular site) article about an upcoming samsung android device (mainly the galaxy s that is) - half the comments are about how samsung's customer support sucks and it's the only reason why someone wouldn't buy the device in question
its wont really dmage samsung that much.
alot of the people that buy their phones dont read places like endgadget, gizmodo, androidforums and just buy the hardware and deal with it.
the people that want more are the people that notice it and when we go a new generation of people will fill our shoes
 
Good to see and hopefully we'll get 2.1 soon. I do wonder if they should be working on 2.2 instead, but I assume Drakaz & team know best.
 
Good to see and hopefully we'll get 2.1 soon. I do wonder if they should be working on 2.2 instead, but I assume Drakaz & team know best.

look how fast google has moved from 2.0 to 2.2
if drakaz kept changing the project to keep up with google there will never be a completed project
 
Well Google updated fast because there was so much to do to catch up with the other OS's out there. They are now feature parity on the whole and as they've said themselves development has slowed down a lot now and they expect release cycles to be one or two releases a year. So it makes more sense to work with 2.2 as chances are the next iteration is 6 months or more away. Not that i'd be complaining to have a decent 2.1 on my phone, but 2.2 with it's memory and speed improvements would seem like a more sensible option for the Galaxy given it's limitations.
 
Well Google updated fast because there was so much to do to catch up with the other OS's out there. They are now feature parity on the whole and as they've said themselves development has slowed down a lot now and they expect release cycles to be one or two releases a year. So it makes more sense to work with 2.2 as chances are the next iteration is 6 months or more away. Not that i'd be complaining to have a decent 2.1 on my phone, but 2.2 with it's memory and speed improvements would seem like a more sensible option for the Galaxy given it's limitations.

I might be wrong, but I think it has something to do with the 1.6 sources we got, and 2.2 working on another kernel or something.
 
Well Google updated fast because there was so much to do to catch up with the other OS's out there. They are now feature parity on the whole and as they've said themselves development has slowed down a lot now and they expect release cycles to be one or two releases a year. So it makes more sense to work with 2.2 as chances are the next iteration is 6 months or more away. Not that i'd be complaining to have a decent 2.1 on my phone, but 2.2 with it's memory and speed improvements would seem like a more sensible option for the Galaxy given it's limitations.

we pretty much know that gingerbread is coming for xmas
the 6 month release cycle is what they've been doing and they've said they'll likely slow down after gb to a 12 month release cycle (if i remember right)
anyway, like DaSchmarotzer said, the point in working on
 
on twitter
drakaz
Kernel expert needed on GAOSP project to port 2.6.29 galaxy drivers to 2.6.33. Done 90% of the job yesterday, but still have some errors...

:o
 
on twitter
drakaz
Kernel expert needed on GAOSP project to port 2.6.29 galaxy drivers to 2.6.33. Done 90% of the job yesterday, but still have some errors...

:o

goes on to say this
I don't try to port froyo on Galaxy, it's not interessting without the sources. I'm just take a look to port 2.6.29 drivers to 2.6.33...

anyway, what's with .33, shouldn't that be .32 ?
 
Back
Top Bottom