Android 2.2 Development

[Guest screwface]

Screw the camera. When are you going to be putting out beta roms with the new kernel ?

[Guest totiadrenalin]

Ah. Blame Cyanogenmod.. that's where I stole it from :lol:

I'll make the changes to the apns file. Thank you.

I'm using the original APN configuration file from 2.1 UK rom.

Both of this files doesn't contain the Macedonian internet and mms apn configurations.

Edited September 14, 2010 by totiadrenalin

[Guest Holograph]

Screw the camera. When are you going to be putting out beta roms with the new kernel ?

You can't call it a beta, when it's still Alpha :lol:

[Guest totiadrenalin]

I'm using the original APN configuration file from 2.1 UK rom.

Both of this files doesn't contain the Macedonian internet and mms apn configurations.

If all apn's were in 2.1 than the should be in this file two.

[Guest totiadrenalin]

I'm using the original APN configuration file from 2.1 UK rom.

Both of this files doesn't contain the Macedonian T-Mobile internet and mms apn configurations.

If all apn's were in 2.1 than they should be in this file two.

apns_conf.xml

Edited September 14, 2010 by totiadrenalin

[Guest gusthy]

Tom G, Fibblescan:

I don't want to urge the thing, only I am asking: on other Froyos there is a tethering option in the Settings->Wireless & networks menu.

Where did this gone in our Froyos? Is it artifically disabled?

[Guest zuccster]

The only difference in the O2 entries is carrier="o2 Hidden MMS" mcc="234" mnc="30". Is that the one you need?

I've update the apns-conf.xml on git. The next build should include it.

The original file (Cyanogenmod) contains these lines for O2 UK:

<apn carrier="O2 UK" apn="mobile.o2.co.uk" user="vertigo" pass="password" mcc="234" mnc="10"/>

<apn carrier="O2 UK Prepay MMS" apn="payandgo.o2.co.uk" user="Vertigo" pass="password" mmsc="http://mmsc.mms.o2.co.uk" mmsproxy="193.113.200.195" port="8080" mcc="234" mnc="10"/>

<apn carrier="O2 UK Postpay MMS" apn="wap.o2.co.uk" user="O2wap" pass="password" mmsc="http://mmsc.mms.o2.co.uk" mmsproxy="193.113.200.195" port="8080" mcc="234" mnc="10"/>

As I understand it, the user [vV]ertigo is valid only for iPhone accounts, and results in a 403 from the O2 MMSC if on a non iPhone contract. The second file contains the following:

<apn carrier="o2 UK Internet" apn="mobile.o2.co.uk" user="o2web" password="password" mcc="234" mnc="10" type="default"/>

<apn carrier="o2 UK MMS" mcc="234" mnc="10" apn="wap.o2.co.uk" proxy="193.113.200.195" port="8080" user="o2wap" password="password" mmsc="http://mmsc.mms.o2.co.uk:8002" mmsproxy="193.113.200.195" mmsport="8080"/>

<apn carrier="o2 Hidden MMS" mcc="234" mnc="30" apn="wap.o2.co.uk" proxy="193.113.200.195" port="8080" user="o2wap" password="password" mmsc="http://mmsc.mms.o2.co.uk:8002" mmsproxy="193.113.200.195" mmsport="8080"/>

Which functions correctly, See here

Edited September 14, 2010 by zuccster

[Guest totiadrenalin]

The original file (Cyanogenmod) contains these lines for O2 UK:

<apn carrier="O2 UK" apn="mobile.o2.co.uk" user="vertigo" pass="password" mcc="234" mnc="10"/>

<apn carrier="O2 UK Prepay MMS" apn="payandgo.o2.co.uk" user="Vertigo" pass="password" mmsc="http://mmsc.mms.o2.co.uk" mmsproxy="193.113.200.195" port="8080" mcc="234" mnc="10"/>

<apn carrier="O2 UK Postpay MMS" apn="wap.o2.co.uk" user="O2wap" pass="password" mmsc="http://mmsc.mms.o2.co.uk" mmsproxy="193.113.200.195" port="8080" mcc="234" mnc="10"/>

As I understand it, the user [vV]ertigo is valid only for iPhone accounts, and results in a 403 from the O2 MMSC if on a non iPhone contract. The second file contains the following:

<apn carrier="o2 UK Internet" apn="mobile.o2.co.uk" user="o2web" password="password" mcc="234" mnc="10" type="default"/>

<apn carrier="o2 UK MMS" mcc="234" mnc="10" apn="wap.o2.co.uk" proxy="193.113.200.195" port="8080" user="o2wap" password="password" mmsc="http://mmsc.mms.o2.co.uk:8002" mmsproxy="193.113.200.195" mmsport="8080"/>

<apn carrier="o2 Hidden MMS" mcc="234" mnc="30" apn="wap.o2.co.uk" proxy="193.113.200.195" port="8080" user="o2wap" password="password" mmsc="http://mmsc.mms.o2.co.uk:8002" mmsproxy="193.113.200.195" mmsport="8080"/>

Which functions correctly, See here

Ok then!

But you still don't have the T-mobile MK internet apn and MMS configurations.

So I did modifications of the APN"S and MMS configurations from the file you just upload, and Tom G could include this file in the githup.

[Guest totiadrenalin]

Ok then!

But you still don't have the T-mobile MK internet apn and MMS configurations.

So I did modifications of the APN"S and MMS configurations from the file you just upload, and Tom G could include this file in the githup.

WTF?

How can I always forgot to click upload?!

EDIT:

But first check it, and confirm if anything's Ok with it?

apns_conf.xml

Edited September 15, 2010 by totiadrenalin

[Guest Simon O]

Tom G, Fibblescan:

I don't want to urge the thing, only I am asking: on other Froyos there is a tethering option in the Settings->Wireless & networks menu.

Where did this gone in our Froyos? Is it artifically disabled?

It's part of kernel .32 which other Froyo roms are using, or higher.

[Guest gusthy]

It's part of kernel .32 which other Froyo roms are using, or higher.

Thx.

[Guest AdamBaker]

Camera Status:

For those who don't read github, the situation with the camera is that there is a device specific user space shared library libcamera.so for which we don't have source code. Some of the functions that this library calls have been moved to a different library in 2.2 so attempting to link the 2.2 framework to the old library fails. It looks as though to solve this it will be necessary to pull the elf file to bits, extend the string table and the dynamic section to include references to the extra library we now need to link to then put the bits back together updating all the size info in the header in the process. If anyone knows of any tools that could do this rather than me having to write a program to do it that might speed things up. I'm aware of elfsh but I've never used it and it has restricted capabilities dealing with ARM object files so my current thought is that it isn't wirth investing the time to see if it can do it.

The alternatives are

1) rewrite libcamera.so - now we have kernel source we know bothy sides of what it interfaces with but there appears to be a lot of code in there taking advantage of bits of hardware we don't have much / any docs for so I wouldn't hold out much hope on that front.

2) Fix the problems with the codeaurora camera interface implementation. As Tom hasn't managed to find all the bits of code needed to make this even compile it could be a long job.

[Guest Simon O]

May be a silly question but are there any devices with a similar or identical camera to ours? Darchstar made some camera libs for the Hero which might give us an idea?

[Guest Simon O]

With the Camera some Cyanogenmod roms use the 2.1 camera modules as they don't have any source to build the camera. They add a line to BoardConfig.mk called BOARD_USES_ECLAIR_LIBCAMERA and a prelink map is added to the build.

http://github.com/CyanogenMod/android_devi.../BoardConfig.mk

I guess this is what AdamBaker meant. Now question is how do we generate the prelink map?

[Guest gwenhwyfaer]

Does the post below help at all?

http://android.modaco.com/index.php?s=&amp...t&p=1296292

ed. Yes, thank you phpBB, dumping me at the top of the thread when I explicitly requested a single post's URL was sooo helpful. ...Post no.14 on that page is the one to which I was referring. Grrr.

Edited September 15, 2010 by gwenhwyfaer

[Guest al_3sjad]

Dear, the Arabic language can be supported in this version. However, I used your version 1.5 and the language was good in that version, but in this version not, Can you help me or I should stay in 1.5 :lol:

[Guest Simon O]

Froyo doesn't have fully working Arabic support, or support for any right to left languages. It is a known problem.

[Guest al_3sjad]

Froyo doesn't have fully working Arabic support, or support for any right to left languages. It is a known problem.

Thanks, for Quick Replay, anyway, I will continue testing this version for some days.

[Guest whackster]

One thing I noticed, the phone won't connect to a wifi network automatically, and the settings are there. It just disconnects, have to manually connect to it. Still haven't gotten the 3G apns in so I don't know how it will behave then...

[Guest totiadrenalin]

One thing I noticed, the phone won't connect to a wifi network automatically, and the settings are there. It just disconnects, have to manually connect to it. Still haven't gotten the 3G apns in so I don't know how it will behave then...

WTF?

How can I always forgot to click upload?!

EDIT:

But first check it, and confirm if anything's Ok with it?

apns_conf.xml - Right click and save link as.

Edited September 15, 2010 by totiadrenalin

[Guest Simon O]

One thing I noticed, the phone won't connect to a wifi network automatically, and the settings are there. It just disconnects, have to manually connect to it. Still haven't gotten the 3G apns in so I don't know how it will behave then...

I think thats to do with the build.prop command "wifi.supplicant_scan_interval"

[Guest totiadrenalin]

I think thats to do with the build.prop command "wifi.supplicant_scan_interval"

I don't have any problem with auto connection.

By the way.

It's confirmed that test-keys build of the froyo is the only reason for the market issue.

After editing the build.prop, and do a wipe of the data.

I get my market app working just perfectly.

[Guest totiadrenalin]

I think thats to do with the build.prop command "wifi.supplicant_scan_interval"

And Flibble or Tom.

Will you guys do me a big favour?

I need you to build new boot.img of froyo, but to put this drivers in /drivers/input/touchscreen/

And send the boot.img to my private email: [email protected]

Flibble. You know what I'm trying to do man?!

I'll be very grateful to you guys, if you do me that favour.

EDIT:

Now I realize that I have some problem with my IMAP server.

I can not receive attachments

So use this email:

[email protected]

Once again I'll be very grateful to you guys, if you do me that favour.

Thanks anyway.

Best regards

TOTI

MT_Synaptics_driver.zip

Edited September 15, 2010 by totiadrenalin

[Guest AntonioPT]

And Flibble or Tom.

Will you guys do me a big favour?

I need you to build new boot.img of froyo, but to put this drivers in /drivers/input/touchscreen/

And send the boot.img to my private email: [email protected]

Flibble. You know what I'm trying to do man?!

I'll be very grateful to you guys, if you do me that favour.

EDIT:

Now I realize that I have some problem with my IMAP server.

I can not receive attachments

So use this email:

[email protected]

Once again I'll be very grateful to you guys, if you do me that favour.

Thanks anyway.

Best regards

TOTI

Is this the synaptics touchscreen driver with multi/dualtouch enabled?

[Guest DanWilson]

And Flibble or Tom.

Will you guys do me a big favour?

I need you to build new boot.img of froyo, but to put this drivers in /drivers/input/touchscreen/

And send the boot.img to my private email: [email protected]

Flibble. You know what I'm trying to do man?!

I'll be very grateful to you guys, if you do me that favour.

EDIT:

Now I realize that I have some problem with my IMAP server.

I can not receive attachments

So use this email:

[email protected]

Once again I'll be very grateful to you guys, if you do me that favour.

Thanks anyway.

Best regards

TOTI

Just try to take all the multi-touch...

I think, however, Bobo said at one point that the touch controller thing might need to be re-flashed, meaning we get no multi-touch unless we open the Pulse up.