647 replies to this topic

[pier11]

Updated rom on the first post with:
- OpenGL lib as per dr.flo findings
- Now usb_pid_index=25 (Ideos style) is set in kernel, no matter what in shared memory. This should care of enabling adb.

[dr.flo]

pier11, on 07 February 2012 - 04:33 AM, said:

Updated rom on the first post with:
- OpenGL lib as per dr.flo findings
- Now usb_pid_index=25 (Ideos style) is set in kernel, no matter what in shared memory. This should care of enabling adb.

cool this does the trick for me! Many thanks for investigating this!

[pier11]

@dr.flo,

tried your Ascend rom again, and yes - keypad leds work. But lights.msm7k.so in both roms is exactly the same (by md5 comparison).
Can't think what else is needed to change to fix the leds on u8150 rom...


EDIT:
- flashed boot image from u8150 port, leds still working
- even flashed  lights.msm7k.so from u8150 to Ascend rom - still works.

Edited by pier11, 07 February 2012 - 12:47 PM.

[dr.flo]

pier11, on 07 February 2012 - 12:34 PM, said:

- flashed boot image from u8150 port, leds still working

should always work on non-compat-branch kernels? At least that's what I believe...

You know where to toggle compat of leds since you have done it... maybe you also know which function name / devices / whatever the kernel exposes to user space for controlling leds. Possibly some /dev/xxx ? Then why not grep everything inside system/lib to see which lib accesses that device?

[pier11]

copy-paste all libs from u8150 (except libdvm.so which prevented system to load). Still lights work...

EDIT:
completely replaced /system/lib directory from u8150 (but mentioned libdvm.so). Still lights work... So it's not an issue with libs.

(Power button stopped to work, but that's different issue)

Edited by pier11, 07 February 2012 - 01:56 PM.

[dr.flo]

pier11, on 07 February 2012 - 01:32 PM, said:

completely replaced /system/lib directory from u8150 (but mentioned libdvm.so). Still lights work... So it's not an issue with libs.

nice experiment... and same with system/bin?

Other thing:
we might want to make a list of all libs present in system/lib and what functions they are used for.
this is to help future RIL experiments.

I think of s.th. like
libdvm.so -> dalvik vm related
libloc_api.so -> location api (gps related)

... and so on.. also it would be helpful to mark which of these libs are built from source (in cm6) and which are closed source vendor specific files

Edited by dr.flo, 07 February 2012 - 02:45 PM.

[pier11]

dr.flo, on 07 February 2012 - 02:39 PM, said:

nice experiment... and same with system/bin?

not tested /bin,
only /lib

[dr.flo]

just noticed this in logcat (rom 03)

E/lights  ( 1265): write_int failed to open /sys/class/leds/red/brightness
E/Sensors ( 1265): Couldn't open /dev/light (No such file or directory)

might be related to light issue

[pier11]

don't know, may be relevant to our cm7 issues with video recordings:
http://modmymobile.c...tml#post4093827

Moto Motus/Backflip (MSM7200A) people were replacing  their libGLES_qcom.so in cm7 build so to overcome camera issues...

[pier11]

Wi-Fi address = Bluetooth MAC address + 1 (or -1 don't remember)
CM knows how to get the latter.

Looks like BT MAC is somewhere in NV ram according to the below. Now need to figure address somehow...

$ strings system/bin/hci_qcomm_init | grep -ri "BD.ADDR"
BD_addr
BD_addr_string
bt_hci_qcomm_init Failed to read BD Address from NV default to %02X:%02X:%02X:%02X:%02X:%02X
This version attempts NV read of BD_ADDR, refclock, clock-sharing via RPC.
nv_cmd_remote failed to get BD_ADDR from NV, code %d

EDIT:
Write a wrapper atop of libnv.so?..

EDIT2:
must be it:

-b  --board-address   NV447 or rand Bluetooth MAC address to use

Edited by pier11, 08 February 2012 - 08:15 PM.

[pier11]

I've found this device - Huawei UM840 - it's like Ascend (msm7225, 480*320), but with front camera, as my research's figuring. It should have Froyo rom issued just recently. So chances are it have froyo camera app supporting front camera. Worth to investigate.

link

It has front camera switch according to this:

Edited by pier11, 08 February 2012 - 11:10 PM.

[lloco73]

pier11, on 08 February 2012 - 10:47 PM, said:

I've found this device - Huawei UM840 - it's like Ascend (msm7225, 480*320), but with front camera, as I my research's figuring. It should have Froyo rom issued just recently. So chances are it have froyo camera app supporting front camera. Worth to investigate.

The Huawei UM840 (for Venezuela mobile operator Movilnet)  is the Huawei U8500.

[pier11]

lloco73, on 08 February 2012 - 11:10 PM, said:

The Huawei UM840 (for Venezuela mobile operator Movilnet)  is the Huawei U8500.

Close, but not exactly. U8500 does not have front camera, as I understand...

[dr.flo]

nice find.
I tried pushing Camera.apk + Camera.odex into CM6 - camera application does not show up.
I don't know - is it possible to mix odexed and deodexed system apps or do I have to deodex Camera.apk first?

Another way would be trying to boot that rom unmodified like with ascend and u8150 roms...

[pier11]

dr.flo, on 09 February 2012 - 10:25 AM, said:

Another way would be trying to boot that rom unmodified like with ascend and u8150 roms...

This is what I did.
Even though I'm having "froyo (frozen yogurt)" - frozen picture in camera with acidic yogurt colors, as before, I can see the front camera switch.

I didn't succeed to add Camera.app in original odexed form to u8150 rom. Deodexed version helped.

[twrock]

dr.flo, on 09 February 2012 - 10:25 AM, said:

nice find.
I tried pushing Camera.apk + Camera.odex into CM6 - camera application does not show up.
I don't know - is it possible to mix odexed and deodexed system apps or do I have to deodex Camera.apk first?

Another way would be trying to boot that rom unmodified like with ascend and u8150 roms...

I've never been able to work with odexed apk's in modified roms.

[pier11]

um840 for Pulse (Froyo 2.2.2)
- front camera switch
- can be usb-tethered
- only minimum necessary changes to rom
- deodexed
- our 2.6.32 kernel from normal branch.
- (no radio, no wifi yet - please help if you can)

Do Wipe Data/Factory Reset before installation.
u8220 users: Install after TRE or CHT8000 roms.

It is a GSM phone btw, contrary to Ascend.

Edited by pier11, 09 February 2012 - 02:38 PM.

[lloco73]

pier11, on 09 February 2012 - 01:47 PM, said:

- (no radio, no wifi yet - please help if you can)

it's due to, maybe, different baseband?

[pier11]

lloco73, on 09 February 2012 - 02:07 PM, said:

it's due to, maybe, different baseband?

definitely.
I know in that region our phone is named u8220-6 and if they flash traditional for Europe/Asia GSM roms, like TRE, it breaks the phone...

Edited by pier11, 09 February 2012 - 02:35 PM.

[lloco73]

allready googled but no info about retrieving baseband from phone. Does anyone know how?

For info forum with UM840 firmwares. There they have a cm7 rom and the secondary camera does not work either.

Edited by lloco73, 09 February 2012 - 02:36 PM.