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

Android 2.x on Galaxy

Ok so we've had a talk with must on irc, and we're all working together. Just in time as we were drowning in source fixing the ril. I'll explain later the exact issue.

There never was any 'i refuse to work with u' etc, its the first time we've actually been able to talk to him.

So Lets drop all the arguments - i dont really care who's right :)

We're now waiting for his sources.. so lets give him the benefit of the doubt for now!
 
Upvote 0
So, in the above code excerpt, what happens if you put a printf()
below case INPUT_TYPE_DUAL?

Nothing gets printed. The only events happening are input_type_single and palm. There are two possibilities still to get it working:

1. Read from a different register and hope that will magically make multitouch working (chance of success: very low, but easy to do)
2. Update the touchscreen firmware. There is code to flash it and an actual firmware in the beholden 2 kernel. No source or anything - binary only. You could try an ARM disassembler, i read somewhere that there's an ARM cpu in some Melfas touchscreens. This is rather tricky, but i'm sure there are people around who can do it.

See Samsung Galaxy recognize more as one finger | receptorBlog for more details on the results.
 
Upvote 0
Ok so we've had a talk with must on irc, and we're all working together. Just in time as we were drowning in source fixing the ril. I'll explain later the exact issue.

There never was any 'i refuse to work with u' etc, its the first time we've actually been able to talk to him.

So Lets drop all the arguments - i dont really care who's right :)

We're now waiting for his sources.. so lets give him the benefit of the doubt for now!

We really can get "one ROM" from all Galaxy devz?:eek:
never happier than this.:D
 
Upvote 0
Finally I found it but I must apologize as the article was NOT about the Galaxy, but the G1 (and Android in general).

Anyhow it may help to see whats going on in the Galaxy also when trying to get MT to work.

http://tinyurl.com/y97blcf

BR

Yup. I know about this. G1 has a Synaptics touchscreen. As you can see in this article, it is already supported in the kernel. That guy just modified some libs in the application framework stack and write a proof-of-concept app that uses this modified lib. He didn't even as much as touched the kernel.

In contrast to G1, Galaxy's touchscreen doesn't have a MT support on a lowest level (kernel/firmware). If we manage to solve this, then rest of it is pretty much a walk in the park. ;)
 
Upvote 0
Nothing gets printed. The only events happening are input_type_single and palm. There are two possibilities still to get it working:

1. Read from a different register and hope that will magically make multitouch working (chance of success: very low, but easy to do)
2. Update the touchscreen firmware. There is code to flash it and an actual firmware in the beholden 2 kernel. No source or anything - binary only. You could try an ARM disassembler, i read somewhere that there's an ARM cpu in some Melfas touchscreens. This is rather tricky, but i'm sure there are people around who can do it.

See Samsung Galaxy recognize more as one finger | receptorBlog for more details on the results.

Pieter, do you know did Steffen tried to play around with this some more? I am willing to give it a shot. I don't have ARM assembly knowledge though, so I would try that guess-a-register :) approach.

I would have probably tried it already, but the thing is that I'm not sure how to make a boot image. I've read this:
HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki

From this, it's clear that boot image goes to /dev/mtd/mtd2 and that it contains the kernel. But what about ramdisk?

Or could I forget all this and just flash the newly compiled kernel zImage with fastboot?
 
Upvote 0
Pieter, do you know did Steffen tried to play around with this some more? I am willing to give it a shot. I don't have ARM assembly knowledge though, so I would try that guess-a-register :) approach.

He has instructions on his site for compiling a kernel. I don't know how he flashed it to his phone - i know nothing about android images, fastboot or recovery mode - so far i've limited my contributions to reading source code and suggesting things other people could do :). I'm sure there's documentation at google's android site about fastboot and recovery mode. The samsung supports the standard google tools directly.
 
Upvote 0
Pieter, do you know did Steffen tried to play around with this some more? I am willing to give it a shot. I don't have ARM assembly knowledge though, so I would try that guess-a-register :) approach.

I would have probably tried it already, but the thing is that I'm not sure how to make a boot image. I've read this:
HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki

From this, it's clear that boot image goes to /dev/mtd/mtd2 and that it contains the kernel. But what about ramdisk?

Or could I forget all this and just flash the newly compiled kernel zImage with fastboot?

I suggest you to contact Drakaz. He's the most knowladgable around regarding building and transfering kernel to galaxy.
 
Upvote 0
Believe me, I've searched, but Google documentation on this particular subject is next to nonexistent. Steffen did provide the image he tested MT with on his blog though, and it looks to me it's in fact just a compressed kernel image (it's the same size as the zImage I've just built, but I'll check it with a hex editor later just to be sure).

Thanks for your advice, Pieter. I hope we'll make this working somehow.
 
Upvote 0
I suggest you to contact Drakaz. He's the most knowladgable around regarding building and transfering kernel to galaxy.

I thought about that too, but I don't want to steal his time over this. However, I did learn a lot in past few days and I like to think I know how it all works in principle. I'm just reluctant to try it out on my device because I am not 100% sure and there are still some pieces of the puzzle missing. But I'll keep reading and learning, and when I get enough courage, I'll try it out. :)
 
Upvote 0
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)

I disagree. I find it quite annoying using the web browser without MT support. Also, various photo editors you can find on the market use it intuitively enough for fast manipulation with photos and wallpapers. However, I agree it's a matter of hardware support. It'll be a while until it's sorted out.

(Pozdravi i tebi. Cini mi se da nas ima nekoliko:)
 
Upvote 0
the people that monitor those forums are customer services i believe.
they get fed all sorts of nonsense although its likely to be the truth
they UK counterpart it far larger than o2IE and theyve still not heard anything solid from samsung about 2.0

i know that certain operators are looking at this mod closely though and it my be a trigger for samsung to pull their head out of their arses
 
Upvote 0
Read this on the O2 UK forums

This article is 'assuming' that the Galaxy will be getting 2.x, as Samsung has reported that the 'Spicia' (Galaxy Lite) will have 2.x (due for release in the UK in the spring).
This was confirmed by Samsung a few months back, and given as the reason why the Galaxy would NOT be getting the upgrade, as they would be concentrating their development efforts on their 'new' 2010 models.

Nothing has changed since then. The only good to be taken from this, is that the Spicia uses fairly similar hardware to the Galaxy, so it should make if fairly easy for the community to port 2.x to our devices, voiding all our warranties, and breaking our contract with O2 at the same time.

O2 Forum :: View topic - Samsung no longer supporting Android on Galaxy
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones