Android 2.x on Galaxy

[kam187]

We've tried to contact him many times. He never responds to anyone.

He could quite easily decide tommorow he can't be bothered again. So its not going to halt our effort.

 

[steev182]

And there we were hoping he could be Samsung's Cyanogen... I ended up drifting off to sleep watching the chatter on #i7500 and they seem to be putting in a load of effort for it too. Well done Kam187 and others! Watching the irc channel, I felt like the only real input I could give is Comic relief though, but I'll be more than happy to help with the testing effort and donate when I can.

 

[Xenon]

Does irc.freenode.net have a way to be used from the browser?
I really don't want to install mIRC again after all these years.

 

[Terry]

Yes... Freenode Java applet IRC portal

 

[informale]

Or you could use Opera browser (please, no browser wars here ), it has a very simple IRC client built-in.

 

[kam187]

You can click 'live chat' in the forum bar above.

Once you're in you can join the channel by typing

/j #i7500

 

[photon00]

Andronix, how are you finding your version of Eclair on the galaxy. What is the battery life like? Are you seeing any shutdowns? Is it much faster than cupcake? Having problems downloading any apps from the market? Questions, questions questions!

 

[Andronix]

Andronix, how are you finding your version of Eclair on the galaxy. What is the battery life like? Are you seeing any shutdowns? Is it much faster than cupcake? Having problems downloading any apps from the market? Questions, questions questions!

It's 2.0 AOSP. The battery life is similar to IK4, but the presentation on remaining battery is very different. Battery starts falling much faster, but the fall is linear, not like on 1.5 where you're long on 50+ and then suddenly you find your phone turned off.

The fastest you get is galaxo1.1 because framebuffer works, there are few tweaks in the kernel, all drivers working well. But the code of the browser is latest meaning some pages, google reader per example, are rendered accurately, while on 1.5 browser are not rendered well. Also, new Market app is nice... try it.

 

[Jazzerather]

Pretty much the only reason I want 2.0 is for multitouch support...

No no no and no! Multitouch is the last thing I would upgrade the phone for. MT option is mostly useless, it does a trick or two and that's it. I can't imagine how MT does improve functionality in general (because it doesn't) and I can imagine dosen things new Android 2.x can really improve. Anyhow it depends of Samsung (drivers & hardware - Galaxys HW limitations might be a problem I believe) and apps to support multitouch, not the Android 2.x to do it.

(Pozdrav svim HR Galaxyovcima)

 

[sado1]

Personally I'd even say I can't wait to have multitouch but that's not top priority for me. It's kinda useful sometimes - web browsing is much more comfortable with MT, at least for me. But there are some things like Bluetooth that I'd like to see more than MT and let's hope we can reach it.

 

[Xenon]

Don't forget that multitouch would probably help with the
keyboard responsiveness. I never thought of myself as a
particularly quick typist, but I often have difficulties with
the keypresses not registering because I (apparently) type too
fast.


(pozdrav i tebi)

 

[shalafi]

MT is pretty important for gaming - especially on devices without a physical keyboard - all controls have to be on the screen. imagine playing a game on your computer when you only can move the mouse OR click a button OR press a single key .. but none of these at once. sucks, eh?

 

[informale]

Correct me if I'm wrong, but multiple consecutive touches (no matter how fast) have nothing to do with multi-touch. Multi-touch is a method of interpreting two (or more?) simultaneous touches.

 

[Xenon]

If you type quickly then I guess they aren't really consecutive. You
press with one finger and then you press with another one in a different
place while your first finger is still being lifted from the screen. You
often have both fingers on the screen at the same time. Because
they didn't "land" at the same moment a multitouch keyboard easily
discerns the order of the presses and it works. Without multitouch,
you can't type another letter until you completely lifted your finger
from the first one. Try it on the Galaxy. Keep one letter pressed and
press another. It doesn't register.

 

[Rastaman-FB]

If you type quickly then I guess they aren't really consecutive. You
press with one finger and then you press with another one in a different
place while your first finger is still being lifted from the screen. You
often have both fingers on the screen at the same time. Because
they didn't "land" at the same moment a multitouch keyboard easily
discerns the order of the presses and it works. Without multitouch,
you can't type another letter until you completely lifted your finger
from the first one. Try it on the Galaxy. Keep one letter pressed and
press another. It doesn't register.

indeed this happens quite alot due to my lazy thumbs but im quick

 

[informale]

Of course it does not - Galaxy has no multi-touch.

But how do you suggest the phone should interpret touches, when you push two letters at once? Typing needs sequential touches. Or you'll end up with something like that:

Ytping eneds esquential otuches.

I personally type with one thumb in portrait mode using HTC full qwerty keyboard with auto-complete.

 

[Rastaman-FB]

Of course it does not - Galaxy has no multi-touch.

But how do you suggest the phone should interpret touches, when you push two letters at once? Typing needs sequential touches. Or you'll end up with something like that:

Ytping eneds esquential otuches.

I personally type with one thumb in portrait mode using HTC full qwerty keyboard with auto-complete.

i type in landscape mostly and devices like iphone write with a 1st to press recognition so it memorises order of key press
i know the galaxy can do it as if its lagging and you type really fast you can wait a second and watch the galaxy print the word you typed a seconds before.
if you had multitouch it would just remove deadspots and typos a bit

 

[informale]

It would need a keyboard programmed to recognize typos caused by simultaneous touches and touches made in wrong order.

 

[NoUse4aNick]

Mustymod 1.02a released!

 

[Hark]

I haven't seen this posted anywhere on the forums, but it says on the Samsung Twitter page that 2.0 is coming soon. Did everyone miss this? I mean why work on 2.0 if they are about to release it?

SamsungFirmware (SamsungFirmware) on Twitter

Last firmware for the samsung galaxy is online I7500XXIK5
11:26 AM Jan 4th from web

@jeebjp @DrHyperKALICH Samsung is busy with android 2.0 updates... First phone with 2.0 is for the Galaxy later Q1 for the Galaxy Lite.
11:08 AM Jan 4th from web in reply to jeebjp

Great news for the Samsung I7500.... Android 2.0 is almost finish.
10:11 AM Jan 4th from web


Jan 4th, was a good day.

 

[informale]

Lol, I've just read this too )

SamsungFirmware (SamsungFirmware) on Twitter is not an official Samsung source. I'ts a twitter account of www.Samsung-Firmware.tk, which is now down for some reason.
_

 

[Xenon]

Great news and thanks for the twitter link. Even if it is an unofficial twitter
they seem to know awfully lot about Samsung fimwares, which is a good thing

 

[Xenon]

Mustymod 1.02a released!

That's amazing. Lots of progress there.

 

[Andronix]

That's amazing. Lots of progress there.

While others are talking, he's doing an amazing job

Odin time

 

[Jazzerather]

It would need a keyboard programmed to recognize typos caused by simultaneous touches and touches made in wrong order.

Pay attention to the HW limitations of Galaxys screen. We are speaking software here, but I think I was reading an article or two about HW limitations (for Galaxy, not in general) and that's the main reason that some devices aren't capable of having MT. Their HW / screen, from the beginning, is not designed to work in that way, so no SW can help.