Jump to content

Android 2.2 Development


Guest eckengucker1
 Share

Recommended Posts

Guest Sh4d0w940
i think, most of Huawei Android devices using the same 3.2mp camera, couldnt we just steel the libs?

I don't know, but maybe that new phone that comes with Froyo could be usefull to get some libs.

Sh4d0w940

Edited by Sh4d0w940
Link to comment
Share on other sites

Guest Letterbox115
That is exactly like with the Angry birds, why is this problem?

I don't know, maybe our Pulses have to small amount of ram? :lol:

Flibble said he got Angry Birds working though, I wonder how he did

Link to comment
Share on other sites

Guest whackster
I don't know, maybe our Pulses have to small amount of ram? :)

Flibble said he got Angry Birds working though, I wonder how he did

Just use a task killer to free as much memory as possible, it worked when I tried it on FLBMOD 1.5, there are some issues to install it on froyo, would be nice to see how it runs now, it should really fly :lol:

Link to comment
Share on other sites

I don't know, maybe our Pulses have to small amount of ram? :lol:

Flibble said he got Angry Birds working though, I wonder how he did

By launching the app. I did nothing else to make it work, it just works every single time I launch it.. and I have a lot of apps on my phone (running Froyo).

I don't use a task killer. Never saw the point in them as Android is very good at killing tasks itself.

Link to comment
Share on other sites

Guest Epic-Emodude
By launching the app. I did nothing else to make it work, it just works every single time I launch it.. and I have a lot of apps on my phone (running Froyo).

I don't use a task killer. Never saw the point in them as Android is very good at killing tasks itself.

Whenever I try to install it it fails. Any ideas why?

Link to comment
Share on other sites

By launching the app. I did nothing else to make it work, it just works every single time I launch it.. and I have a lot of apps on my phone (running Froyo).

I don't use a task killer. Never saw the point in them as Android is very good at killing tasks itself.

are you using flash 10 or flash lite? a2sd or extended partition on sd?

Link to comment
Share on other sites

Guest totiadrenalin
I get the same error last night trying to build the eclair boot from the pulse 2.1 source.

This drivers aren't patched by BB, but i pervorm the same patch he did over the 1.5 synaptics drivers.

I guess i did something wrong.

I'll recheck it again, after i get home from work.

Or maybe it'll be better to conract BB and let him take a look over it.

Thanks anyway man.

If i get 2.1 kernel compiled it'll be much easyer to build the froyo kernel.

Best regarts

Toti

I don't know what's the problem?

If i try to change one single line in the synaptics_rmi_tm1319.c drivers, I get the build failed.

And I have some other question.

Is there differences between froyo_pulse_51.zip by flibble and by Tom G?

Because when I fastboot the flibble's froyo I don't get any problems, But in the Tom's froyo get Rild and 3G issues.

The network is constantly reconnecting.

And I can't connect the 3G.

The apn's configuration isn't the reason for it.

If the both roms are the same then I must did some mess. :lol:

About the camera bug.

Flibble. Can you do adb pull /proc/config.gz of your Pulse mini.

And check what drivers it's using.

Compare it with the (Big brother) Pulse U8220 config and if they are the same than you could most likely use the same drivers, and I guess so, the same camera lib files for our Pulse Froyo.

Link to comment
Share on other sites

Whenever I try to install it it fails. Any ideas why?

Yes, it wants to install to the SD. Unmount the SD from the android settings app first, then install Angry Birds.

are you using flash 10 or flash lite? a2sd or extended partition on sd?

I don't use any flash on my phone. I use A2SD with 512mb ext2 partition on SD. Dalvik-cache on SD also.

Link to comment
Share on other sites

Yes, it wants to install to the SD. Unmount the SD from the android settings app first, then install Angry Birds.

I don't use any flash on my phone. I use A2SD with 512mb ext2 partition on SD. Dalvik-cache on SD also.

Please remind me, what are the advantages of dalvik cache on sd ? Is this recommended?

Link to comment
Share on other sites

Guest totiadrenalin
Please remind me, what are the advantages of dalvik cache on sd ? Is this recommended?

The advantages of using dalvik-cache on sd is that you will get more free memory.

But be aware of it.

To use it you will need at least class 4 SDCARD.

So if you have class 4 or class 6 SDCARD it's not bat the Idea putting the dalvik-cache on the ext partition.

there's even a way to symlink the data/data to the SADCARD.

But in that case you will definitely gonna need class 6 sdcard.

Link to comment
Share on other sites

Guest AdamBaker

I'm sorry to report the camera isn't working yet - I can at least boot a version of froyo that includes the real camera library but when I try to run the camera app the first time after a power on I get

E/QualcommCameraHardware( 1083): initDefaultParameters

E/QualcommCameraHardware( 1083): jpeg_encoder_setGPSInfo = 0x80102b5d.

D/CameraService( 1083): Client::Client X (pid 1535)

D/Camera ( 1535): app passed NULL surface

W/dalvikvm( 1535): threadid=12: thread exiting with uncaught exception (group=0x400207d8)

E/AndroidRuntime( 1535): FATAL EXCEPTION: Thread-13

E/AndroidRuntime( 1535): java.lang.NullPointerException

E/AndroidRuntime( 1535): at com.android.camera.Camera.updateCameraParametersPreference(Camera.java:1779)

E/AndroidRuntime( 1535): at com.android.camera.Camera.setCameraParameters(Camera.java:1911)

E/AndroidRuntime( 1535): at com.android.camera.Camera.startPreview(Camera.java:1665)

E/AndroidRuntime( 1535): at com.android.camera.Camera.access$5600(Camera.java:94)

E/AndroidRuntime( 1535): at com.android.camera.Camera$4.run(Camera.java:930)

E/AndroidRuntime( 1535): at java.lang.Thread.run(Thread.java:1096)

W/ActivityManager( 1141): Force finishing activity com.android.camera/.Camera

subsequent runs get all sorts of odd errors but I suspect that is because lots of framework stuff has been left in a bad state by the error above which is always first. I do wonder if the "app passed NULL surface" message refers to the window that the video preview is supposed to be rendered into and if that could be related to the video playback problems.

On a more positive note I have tracked down my problem accessing WiFi with froyo - The MAC address has changed and my router is configured to reject unknown MAC addresses. I need to go back and check what eclair was doing because the address I had set in the router is now the bluetooth MAC address and the WiFi address is still Huawei's not some fallback default value.

Link to comment
Share on other sites

Guest AdamBaker

I'm giving up looking at the camera for tonight now. I've attached my diffs to Tom's repo in case anyone else wants to see what I've been up to. I suspect the fact this has got us past the linking problems means it is at least a step in the right direction. There is still a minor build issue that copying libcamera.so to the target dir doesn't happen at the right time so I copy it in by hand when the build fails.

Also of possible interest (and a hint the problem may not be down to video rendering) is the following output from the CameraServiceTest program

D/CameraServiceTest( 1518): CameraServiceTest start

D/CameraServiceTest( 1518): void testConnect()

E/QualcommCameraHardware( 1083): initDefaultParameters

E/QualcommCameraHardware( 1083): jpeg_encoder_setGPSInfo = 0x80102b5d.

D/CameraService( 1083): Client::Client X (pid 1518)

I/DEBUG ( 1079): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 1079): Build fingerprint: 'generic/full_pulse/pulse/:2.2/FRF91/eng.aab.20100916.000110:eng/test-keys'

I/DEBUG ( 1079): pid: 1083, tid: 1140 >>> /system/bin/mediaserver <<<

I/DEBUG ( 1079): signal 11 (SIGSEGV), fault addr 00000008

I/DEBUG ( 1079): r0 00000000 r1 00000000 r2 afd418dc r3 00000001

I/DEBUG ( 1079): r4 0001647c r5 00000000 r6 40509dc0 r7 00000000

I/DEBUG ( 1079): r8 00100000 r9 a811b865 10 4040a000 fp 0000d848

I/DEBUG ( 1079): ip 00000003 sp 40509cd8 lr afd103f0 pc a811c2b2 cpsr 60000030

D/QCRIL_MSC ( 1080): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_ph_info()"];

I/DEBUG ( 1079): #00 pc 0001c2b2 /system/lib/libutils.so

I/DEBUG ( 1079): #01 pc 0001c2da /system/lib/libutils.so

I/DEBUG ( 1079): #02 pc 000083ca /system/lib/libcamera.so

I/DEBUG ( 1079): #03 pc 000097ec /system/lib/libcameraservice.so

I/DEBUG ( 1079): #04 pc 0002523c /system/lib/libui.so

I/DEBUG ( 1079): #05 pc 000132dc /system/lib/libbinder.so

I/DEBUG ( 1079): #06 pc 0001652c /system/lib/libbinder.so

I/DEBUG ( 1079): #07 pc 00016700 /system/lib/libbinder.so

I/DEBUG ( 1079): #08 pc 0001bf08 /system/lib/libbinder.so

I/DEBUG ( 1079): #09 pc 0001b474 /system/lib/libutils.so

I/DEBUG ( 1079): #10 pc 0001b8ca /system/lib/libutils.so

I/DEBUG ( 1079): #11 pc 0001103c /system/lib/libc.so

I/DEBUG ( 1079): #12 pc 00010b20 /system/lib/libc.so

I/DEBUG ( 1079):

I/DEBUG ( 1079): code around pc:

I/DEBUG ( 1079): a811c290 1859447b ff6ef7ff 46c0bd10 00008764

I/DEBUG ( 1079): a811c2a0 ffff70d1 1c0db570 42a81c04 f7ffd012

I/DEBUG ( 1079): a811c2b0 68abfcf3 d00b2b00 60a36869 1c086061

I/DEBUG ( 1079): a811c2c0 41991e4b 3810424a f7fc4010 e001fdc3

I/DEBUG ( 1079): a811c2d0 60a36063 bd701c20 f7ffb510 bd10ffe3

I/DEBUG ( 1079):

I/DEBUG ( 1079): code around lr:

I/DEBUG ( 1079): afd103d0 0a000014 e5964000 e5967000 e2144903

I/DEBUG ( 1079): afd103e0 1a000012 e5961000 e2015a02 ebfff99e

I/DEBUG ( 1079): afd103f0 e3853001 e1500003 0a000008 e3550000

I/DEBUG ( 1079): afd10400 13a01001 03a01081 e5865000 e1a00006

I/DEBUG ( 1079): afd10410 e3a02001 ebfff9b8 e1a00004 e8bd87f0

I/DEBUG ( 1079):

I/DEBUG ( 1079): stack:

I/DEBUG ( 1079): 40509c98 00000002

I/DEBUG ( 1079): 40509c9c afd41854 /system/lib/libc.so

I/DEBUG ( 1079): 40509ca0 00016ef8 [heap]

I/DEBUG ( 1079): 40509ca4 0001647c [heap]

I/DEBUG ( 1079): 40509ca8 00016e40 [heap]

I/DEBUG ( 1079): 40509cac 40509dc0

I/DEBUG ( 1079): 40509cb0 00000000

I/DEBUG ( 1079): 40509cb4 afd0cd81 /system/lib/libc.so

I/DEBUG ( 1079): 40509cb8 0001647c [heap]

I/DEBUG ( 1079): 40509cbc a8118e4f /system/lib/libutils.so

I/DEBUG ( 1079): 40509cc0 0001647c [heap]

I/DEBUG ( 1079): 40509cc4 a811bcc1 /system/lib/libutils.so

I/DEBUG ( 1079): 40509cc8 0001647c [heap]

I/DEBUG ( 1079): 40509ccc 00000000

I/DEBUG ( 1079): 40509cd0 df002777

I/DEBUG ( 1079): 40509cd4 e3a070ad

I/DEBUG ( 1079): #00 40509cd8 00016478 [heap]

I/DEBUG ( 1079): 40509cdc 00016408 [heap]

I/DEBUG ( 1079): 40509ce0 40509dc0

I/DEBUG ( 1079): 40509ce4 a811c2df /system/lib/libutils.so

I/DEBUG ( 1079): #01 40509ce8 00016478 [heap]

I/DEBUG ( 1079): 40509cec a96883cd /system/lib/libcamera.so

I/DEBUG ( 1079): debuggerd committing suicide to free the zombie!

I/DEBUG ( 1526): debuggerd: Sep 12 2010 22:41:13

I/BootReceiver( 1142): Copying /data/tombstones/tombstone_04 to DropBox (SYSTEM_TOMBSTONE)

address 83ca is in QualcommCameraHardware::setParameters but the call into libui looks like an invalid address

If anyone knows why I can't get verbose log messages to come out using "logcat Camera:V \*:S" that might be a help tracking stuff down.

froyo.diff.txt

Link to comment
Share on other sites

I'm giving up looking at the camera for tonight now. I've attached my diffs to Tom's repo in case anyone else wants to see what I've been up to. I suspect the fact this has got us past the linking problems means it is at least a step in the right direction. There is still a minor build issue that copying libcamera.so to the target dir doesn't happen at the right time so I copy it in by hand when the build fails.

Also of possible interest (and a hint the problem may not be down to video rendering) is the following output from the CameraServiceTest program

Good work so far. I have a feeling that even with a working libcamera it is going to fail because of the video/egl problem.

If this is based on the cyanogenmod camera solution have you also ported the USE_ECLAIR_MEMORYDEALER code. I downloaded the cyanogenmod code last night but haven't had time to really look at it yet.

I've been playing with tethering. I found the configuration for froyo tethering and as expected wifi doesn't work, but I can't get USB working either. I'm not sure why as the are no error messages.

Link to comment
Share on other sites

Guest AdamBaker
Good work so far. I have a feeling that even with a working libcamera it is going to fail because of the video/egl problem.

I fear you may be right there

If this is based on the cyanogenmod camera solution have you also ported the USE_ECLAIR_MEMORYDEALER code. I downloaded the cyanogenmod code last night but haven't had time to really look at it yet.

I've been playing with tethering. I found the configuration for froyo tethering and as expected wifi doesn't work, but I can't get USB working either. I'm not sure why as the are no error messages.

No, I hadn't spotted the memory dealer patch. I've glanced at it now (at http://github.com/CyanogenMod/android_fram...bcb79f3c9.patch ) and it's a rather bigger change but worth a try to see if it works.

Link to comment
Share on other sites

There's a problem with the wifi mac address. It's wrong and appears to be using a false MAC address. On my phone it's using 00:18:82:82:20:01

What MAC do you see on FLB-Mod 1.5 if with wireless turned off in Android you run

insmod /system/wifi/ar6000.ko

busybox ifconfig eth0

Make sure you do it without running wpa_supplicant.

I will test it when I get home.

Link to comment
Share on other sites

What MAC do you see on FLB-Mod 1.5 if with wireless turned off in Android you run

insmod /system/wifi/ar6000.ko
busybox ifconfig eth0[/code] Make sure you do it without running wpa_supplicant. I will test it when I get home.
[code]insmod /system/wifi/ar6000.ko
# busybox ifconfig eth0
busybox ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:18:82:82:20:01
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:528 (528.0 B) TX bytes:35 (35.0 B)

#

on FLB 1.4

Edited by flibblesan
Link to comment
Share on other sites

insmod /system/wifi/ar6000.ko

# busybox ifconfig eth0

busybox ifconfig eth0

eth0	  Link encap:Ethernet  HWaddr 00:18:82:82:20:01

		  BROADCAST MULTICAST  MTU:1500  Metric:1

		  RX packets:9 errors:0 dropped:0 overruns:0 frame:0

		  TX packets:3 errors:0 dropped:0 overruns:0 carrier:0

		  collisions:0 txqueuelen:1000

		  RX bytes:528 (528.0 B)  TX bytes:35 (35.0 B)


#

on FLB 1.4

I think it will be the modified wext driver used in the official releases that sets the correct MAC, but I have no idea where it would read the MAC from. wpa_supplicant is licensed under both GPL and BSD, so there will not be a requirement for Huawei to provide their modifications.

Link to comment
Share on other sites

In FLB 1.5 my WiFi MAC is one more than my BT one.

I just checked this and my bt mac in froyo is the mac under the battery -1, so if we can figure out how it set that one (which shouldn't be hard, we have all the source) then we should be able to set the wifi mac to that value +1.

Link to comment
Share on other sites

Now I'm just wondering about working on building kernel 2.6.32-9 for the Pulse. I've extracted the kernel config from the Huawei Ideos and to my untraining eye a lot of it is in common with the Pulse and Pulse Mini. I downloaded some 2.6.32-9 code for the HTC Hero as this is the closest device with a .32 kernel source I know of. Seeing as the Cyanogen guys have often ported newer kernels to run on devices stuck with 2.1 source, it can't be that difficult? Or can it?

Tom you mentioned you had a .32 kernel working with recovery? What source did you use to build it and what config file please?

Link to comment
Share on other sites

Guest LorianNod
I'm sorry to report the camera isn't working yet - I can at least boot a version of froyo that includes the real camera library but when I try to run the camera app the first time after a power on I get...

There seem to be plenty of other folk working on this same error, maybe someone already found a solutiion.

I haven't read it all yet, but maybe this thread wiill help

http://ip208-100-42-21.static.xda-develope...0600&page=1

Edited by LorianNod
Link to comment
Share on other sites

Now I'm just wondering about working on building kernel 2.6.32-9 for the Pulse. I've extracted the kernel config from the Huawei Ideos and to my untraining eye a lot of it is in common with the Pulse and Pulse Mini. I downloaded some 2.6.32-9 code for the HTC Hero as this is the closest device with a .32 kernel source I know of. Seeing as the Cyanogen guys have often ported newer kernels to run on devices stuck with 2.1 source, it can't be that difficult? Or can it?

Tom you mentioned you had a .32 kernel working with recovery? What source did you use to build it and what config file please?

Someone else got it working a few months back, but he never got anything working on the display. I was playing with that and have it working in recovery. It boots and displays the menu and you can run things via scripts, but its hard to work with since you need to change scripts and rebuild the boot image every time you want to change something. No input works and no usb.

I don't know where he got his code from, it was newer than the december update code which we were all working from at the time. There is a patch back around page 15.

Hopefully the converter I need to test the rs232 turned up today (next day delivery has been three days now and the place shipping it is only 5 minutes down the road), if that works it will hopefully make playing with kernels a bit easier.

Link to comment
Share on other sites

Guest android.test.uz
Now I'm just wondering about working on building kernel 2.6.32-9 for the Pulse. I've extracted the kernel config from the Huawei Ideos and to my untraining eye a lot of it is in common with the Pulse and Pulse Mini. I downloaded some 2.6.32-9 code for the HTC Hero as this is the closest device with a .32 kernel source I know of. Seeing as the Cyanogen guys have often ported newer kernels to run on devices stuck with 2.1 source, it can't be that difficult? Or can it?

Tom you mentioned you had a .32 kernel working with recovery? What source did you use to build it and what config file please?

What is ANDR on your IDEOS (2.1 by default or 2.2 upgraded) ?

I have used 2.1 and 2.2 on the IDEOS. 2.2 worked well, very stable.

Is something needs, I'll try to help you!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.