225 replies to this topic

[dr.flo]

pier11, on 05 March 2012 - 05:36 AM, said:

that version have many other issues, like no sound is a major of them.

(I did not yet have a closer look at the device trees, so what I say may be obvious to you)
Doesn't the u8150 ics tree feature sources of a device specific libaudio (overriding common libaudio)? Since u8150 libaudio is somewhat compatible with our hardware, including their libaudio source in our device tree might help getting their audio?

In general I wonder, since u8150 device tree has already received a lot of ics specific fixes, would it be easier to take that tree as a base and make u8220 specific adjustments only where needed?

[pier11]

true that u8150 cm9 tree is way more compatible in the moment with our device than our own.

the only advantage I see with our build so far is that radio works. But even that are run a top of u8150 ramdisk (never tried us}

but u8150 tree is not ideal for us too. It is low resolution device and have received quite some patches in that area.

the point is that differences need to be studied.

Edited by pier11, 05 March 2012 - 12:23 PM.

[pier11]

got sound if replace /system/lib/hw/audio* from the first rom.

Changed some other things before as well, but don't think that influenced/influences working sound.

so yes, likely we need to use libaudio source from u8150

Hmm...
It's no different then us apart from:

-LOCAL_MODULE := audio_policy.u8220
+LOCAL_MODULE := audio_policy.u8150
 
-LOCAL_MODULE := audio.primary.u8220
+LOCAL_MODULE := audio.primary.u8150

but u8150 build has 3 times more /system/lib/hw/audio* libs,
strange...

EDIT:
our build completely misses (and no u8220 equivalents):
audio.a2dp.default.so
audio_policy.u8150.so
audio.primary.u8150.so

@dtox125?

Edited by pier11, 05 March 2012 - 02:18 PM.

[pier11]

hm...
figured that

audio_policy.u8150.so
audio.primary.u8150.so 

come from prebuild (!)
what put it there?.. What's the origin?...

Edited by pier11, 05 March 2012 - 03:48 PM.

[pier11]

interesting info on Wallpaper Scrolling and hardware acceleration ("Now it's really smooth, better than GB" <-- citation )
https://github.com/G...droid/issues/46

EDIT:
And this is from tilal's rom for zte blade:
"Full HW acceleration makes it faster than Gingerbread"

Curious, will we be able to achieve the same at some point in time with our adreno 130?..

Both of the above are msm7227 machines/Adreno 200 ... (we are msm7200a for those who don't know)

Edited by pier11, 05 March 2012 - 08:16 PM.

[didije]

Hi pier,

to be honest I don't understand half of the things you are writing on this forum I am not a programer, so I am unable to help you with this rom. I see you struggling 'alone' to make this very demanding mod and I just want to give you some moral support Good luck

Cheers

[cyb3rsp4rk]

I have one problem :s in my phone u8230(A1 TMN) the rom can't load... it keeps loading but nothing happens

[jonnybird]

I have a 8230 and it works fine afther 10 minutes +/-
Very nice work

[pier11]

while fighting with brightness in the new build figured that the following successfully control it:

echo 50 > /sys/class/leds/lcd-backlight/brightness

Max value is 255.

And the below lights up keypad:

echo 255 >  /sys/class/leds/button-backlight/brightness

0 value turns it back off.

Edited by pier11, 06 March 2012 - 01:06 AM.

[pier11]

bluetooth actually also works on our build. (I'm using ramdisk from my initial rom...)

sent test file from laptop...

Edited by pier11, 06 March 2012 - 03:58 AM.

[dr.flo]

hey pier,

sorry for not being more supportive on this, but I have decided that although it is interesting, it may not be worth the amount of time it takes. We can expect this port to reach some basic functionality, but at what price? It will never be perfect - even cm6 still has issues. I think we should not have a phone where there is "no sound during a call" and stuff like this. Not even sometimes... this will be endless work and probably no one - apart from a few posts in a thread - will be able to really thank you for the time you spend on this.

I just started working on this because by chance I ended up with this pulse phone. In the end, I just want a phone that works reliably and can run a few current apps. I don't like the idea of loosing sms if the phone is low on ram and stuff like this. Some hardware limitations just cannot be worked around in software...

I wish you good luck on this, but don't work too hard...

Edited by dr.flo, 06 March 2012 - 08:53 PM.

[pier11]

Fixed that ridiculous mouse pointer when operating jogball. Thanks to HeroC ICS active development.
Now jogball operates as before.

Was a matter of another .idc config

[twrock]

dr.flo, on 06 March 2012 - 08:53 PM, said:

sorry for not being more supportive on this, but I have decided that although it is interesting, it may not be worth the amount of time it takes. We can expect this port to reach some basic functionality, but at what price? It will never be perfect - even cm6 still has issues. I think we should not have a phone where there is "no sound during a call" and stuff like this. Not even sometimes... this will be endless work and probably no one - apart from a few posts in a thread - will be able to really thank you for the time you spend on this.

I just started working on this because by chance I ended up with this pulse phone. In the end, I just want a phone that works reliably and can run a few current apps. I don't like the idea of loosing sms if the phone is low on ram and stuff like this. Some hardware limitations just cannot be worked around in software...

Of course each one will choose how to use their time, but I really like your way of looking at this dr.flo.

I recall Tom G moving on to CM7 before CM6 was really a "solid" rom. I kept waiting on a CM6 "final" that never came. Quite a few bugs remained that have subsequently been patched/hacked/resolved. Now with your CM6 ports, we are very much closer to that rom I kept waiting for. But it has been a looooooong wait. CM7 is now starting to feel the same; it's close, but not complete. Will it get there, or will those of you who really know how to find and fix things move on before it is "completed"? Is the draw of the "next big challenge" too strong?

Maybe my sights are too low, but my dream is to have a really solid CM6 rom, free of  "show-stopper" bugs. If I had that, I can imagine myself happily using my phone for the remainder of 2012. (I expect to get a new phone in January 2013, after I complete a temporary relocation.) And if somehow CM7 can get there too, that would be great too.

Just my $0.02.

[gold-concert]

Personally, I think that it is necessary to try to port the new version of Android.
Then it will choose what is best to finish .For example, it makes no sense to improve the CM6, if the same amount of workmust be invested in improving the ICS. If this is really - why not? Moreover, our device is capable of running ICS.
I very much want to thank pier11, dr.flo and twrock (sorry if someone forgot) for the work you are doing.
I've several times wanted to replace the device, but success in the CM7 I stopped. And now and ICS.

[sasukekun67]

I think a good cm9 build will give our phone a last breath before we move on and hope you guys get it to work properly!
Thanks for working on this, your work is amazing

Cheers

[desalesouche]

+1    thank you all...

[pier11]

brightness start to work if replace all libs from u8150 build...

need to figure which one exactly is responsible and what we are missing in our build.
Without it display is at minimal brightness and can't be adjusted...

EDIT:
narrowed down to /system/libs/hw/*

if then delete lihgts.u8150.so - it breaks brightness control. So pretty much think this is the lib making difference.

And we are not building lights.u8xxx.so (we did in cm7 build) ...

@dtox125 ?

I see u8150 require it like that:

PRODUCT_PACKAGES += \
	lights.u8150 \
	gps.u8150

Also we likely need to add:

# Audio
PRODUCT_PACKAGES += \
	audio.a2dp.default

Edited by pier11, 07 March 2012 - 03:37 PM.

[dtox125]

pier11, on 07 March 2012 - 02:16 PM, said:

brightness start to work if replace all libs from u8150 build...

need to figure which one exactly is responsible and what we are missing in our build.
Without it display is at minimal brightness and can't be adjusted...

EDIT:
narrowed down to /system/libs/hw/*

if then delete lihgts.u8150.so - it breaks brightness control. So pretty much think this is the lib making difference.

And we are not building lights.u8xxx.so (we did in cm7 build) ...

@dtox125 ?

I see u8150 require it like that:

PRODUCT_PACKAGES += \
	lights.u8150 \
	gps.u8150

Also we likely need to add:

# Audio
PRODUCT_PACKAGES += \
	audio.a2dp.default

yes you should add that for audio as for the lights.u8220 and gps.u8220 did you tried to compile with dose lines.if i remember had some errors wnhen compiling.

Edited by dtox125, 07 March 2012 - 03:58 PM.

[pier11]

dtox125, on 07 March 2012 - 03:57 PM, said:

yes you should add that for audio as for the lights.u8220 and gps.u8220 did you tried to compile with dose lines.if i remember had some errors wnhen compiling.

compilation with lights.u8220 fails, complaining on unknown

LIGHT_ID_CAPS
LIGHT_ID_FUNC
LIGHT_ID_WIMAX

Those and related logic were added to out lib, compared to msm7k.

need to debug

static int open_lights(const struct hw_module_t* module, char const* name,
		struct hw_device_t** device)

to see what 'name' are coming into on keypad lighting event as well as on display backlight on/off (it's all in one lib).

Good chances if we make it right, keypad leds will work as well.

Edited by pier11, 07 March 2012 - 04:19 PM.

[pier11]

the following entry points are in lights.msm7k of our original Eclair rom:

/sys/class/leds/jogball-backlight/brightness
/sys/class/leds/red/brightness
/sys/class/leds/green/brightness
/sys/class/leds/blue/brightness
/sys/class/leds/amber/brightness
/sys/class/leds/red/device/grpfreq
/sys/class/leds/red/device/grppwm
/sys/class/leds/red/device/blink
/sys/class/leds/amber/blink
/sys/class/leds/keyboard-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
/sys/class/leds/button-backlight/brightness