3143 replies to this topic

[-=Extreme=-ShamaN]

96frozen, on 19 January 2013 - 08:37 PM, said:

definitely, CM10 has (almost) everything working and CM10.1 is just a baby, there aren't even any stable releases for any cellphone / device. Also, the audio routing issue and others might be CM10's problems. I don't know, but CM10 is currently the most stable for our trusted blades

Everything is working? Well, how about these:

-=Extreme=-ShamaN, on 15 January 2013 - 11:19 PM, said:

Is there any plans to:
1. fix wrong high temperature data, when is in sleep/standby/screen off mode.
2. add undervolting-overvolting kernel support to CM 10.
or
How can I fix/add this to work these all by myselfs (in detailed steps, if you can)?

and these:

WiiSky70, on 16 January 2013 - 09:38 PM, said:

Things that needs fix to 4.1 be a daily driver .
- Fix WiFi Tethering (Very Easy)
- Fix some media errors on 3rd Party apps
- Fix the headphones issue

Anything else?

Edited by -=Extreme=-ShamaN, 19 January 2013 - 09:40 PM.

[96frozen]

-=Extreme=-ShamaN, on 19 January 2013 - 09:40 PM, said:

Everything is working? Well, how about these(..)

Anything else?

I'd be saying you're being quite a bitch, seeing that you're active in 3 posts.

If KonstaT doesn't want to support CM10 anymore and is moving on to CM10.X

-=Extreme=-ShamaN, on 19 January 2013 - 09:40 PM, said:

1. fix wrong high temperature data, when is in sleep/standby/screen off mode.

wat?

-=Extreme=-ShamaN, on 19 January 2013 - 09:40 PM, said:

2. add undervolting-overvolting kernel support to CM 10.

why would you want undervolting (if it is even supported)? It'd make the blade even slower, which I think isn't what we're going for here.

-=Extreme=-ShamaN, on 19 January 2013 - 09:40 PM, said:

Things that needs fix to 4.1 be a daily driver .
- Fix WiFi Tethering (Very Easy)
- Fix some media errors on 3rd Party apps
- Fix the headphones issue

1st - Use CM10.x or PA by zeelog
2nd - Talk with Ganster or daemond, they've done great work here. But don't go and bitch with them how about X doesn't work and Y isn't working quite properly.
3rd - There was a temporary solution here posted by someone, your work is to find it.

Edited by 96frozen, 19 January 2013 - 10:09 PM.

[elrond_bs]

"Fix some media errors on 3rd Party apps" - you can't expect all apps to work on non supported Android version for this phone (and using hack to play H\W video).

I agree with 96frozen, most of those things are not important and are the result of other things working as hacks (it's inevitable). If they were easy to fix, without breaking something else, I'm sure they would have been fixed. You don't seem to realize that the Blade doesn't support even 4.0 at all, including as hardware (ARM6)! So it's a miracle that 4.x is so stable and everything is working so well (thanks to the long and hard work of the developers).

[daemond]

Can anyone please sum up what this "headphone issue" is all about?

[96frozen]

daemond, on 19 January 2013 - 11:11 PM, said:

Can anyone please sum up what this "headphone issue" is all about?

it's an audio routing problem / bug. When headphones are plugged in, the notification sounds (alarms, push notifications, etc...) go through the speaker, not through the earplugs / headphones.

[daemond]

Ah, interesting. I am currently looking at another audio routing issue... SIP calls don't work because the audio library wants to select a wired headset as input. Even if nothing is plugged in... it's probably related.

[HarryPirate]

daemond, on 19 January 2013 - 11:21 PM, said:

Ah, interesting. I am currently looking at another audio routing issue... SIP calls don't work because the audio library wants to select a wired headset as input. Even if nothing is plugged in... it's probably related.

I've noticed the same issue. Have you looked in CM9 code?

[jventura]

daemond, on 19 January 2013 - 06:07 PM, said:

I have another interesting fix for CM10 and CM10.1. Please read this.

Daemond, this works fine too in CM9.. Good patch!

[daemond]

The audio routing issue with notifications is easy to fix. It's actually a feature called "combo device", but for our usage I completely agree that it is not desirable. If you look at this, someone #define'd COMBO_DEVICE_SUPPORTED to 0, clearly with the intention of disabling it. Unfortunately, #ifdef does not work like that.

SIP is also easy to fix. It uses the VOICE_COMMUNICATION audio source which is mapped to a special meta device in libhardware_legacy (some kind of proprietary Qualcomm crap again... sigh). I added the device to the AudioPolicy configuration and now it's working fine.

Here's the commit for both of these fixes.

Edited by daemond, 20 January 2013 - 01:32 AM.

[96frozen]

daemond, on 20 January 2013 - 01:07 AM, said:

The audio routing issue with notifications is easy to fix. It's actually a feature called "combo device", but for our usage I completely agree that it is not desirable. If you look at this, someone #define'd COMBO_DEVICE_SUPPORTED to 0, clearly with the intention of disabling it. Unfortunately, #ifdef does not work like that.

SIP is also easy to fix. It uses the VOICE_COMMUNICATION audio source which is mapped to a special meta device in libhardware_legacy (some kind of proprietary Qualcomm crap again... sigh). I added the device to the AudioPolicy configuration and now it's working fine.

Here's the commit for both of these fixes.

what was the sip issue anyway? thanks for the quick fixes adding this to my compiled ROM

[daemond]

The issue with SIP was that audio did not work at all.

[nokiafan02]

96frozen, on 19 January 2013 - 10:03 PM, said:

I'd be saying you're being quite a bitch

[anantk]

daemond, on 20 January 2013 - 01:07 AM, said:

The audio routing issue with notifications is easy to fix. It's actually a feature called "combo device", but for our usage I completely agree that it is not desirable. If you look at this, someone #define'd COMBO_DEVICE_SUPPORTED to 0, clearly with the intention of disabling it. Unfortunately, #ifdef does not work like that.

SIP is also easy to fix. It uses the VOICE_COMMUNICATION audio source which is mapped to a special meta device in libhardware_legacy (some kind of proprietary Qualcomm crap again... sigh). I added the device to the AudioPolicy configuration and now it's working fine.

Here's the commit for both of these fixes.

Thanks Daemond.

Could you please take a look at unfinished work regarding FM radio functionality on CM9/CM10 from Konsta and Jventura at http://www.modaco.co...00#entry2077357 and see whether FM Radio App functionality can be added to our Blades on CM9/CM10/CM10.1 . FM Radio is now the only "Not Working" category for Blade on CM9/CM10/CM10.1.

[-=Extreme=-ShamaN]

Am I correct: KonstaT no longer will support the CM10?


After all, the M10 is close to the ideal solution for ZTE Blade. And then suddenly it stops support ...
Because I and probably many others Blade owners not able to backport fixes in the latest firmware itselfs, if anyone has the ability to integrate the above mentioned fixes in the final ROM?

[GizmoTheGreen]

any chance you could release a rom with the latest of your patches, Daemond?

[-=Extreme=-ShamaN]

96frozen, on 19 January 2013 - 10:03 PM, said:

I'd be saying you're being quite a bitch, seeing that you're active in 3 posts.

Such post can not paint you from a good side, maaaaan!

[zeekzar]

GizmoTheGreen, on 20 January 2013 - 10:53 AM, said:

any chance you could release a rom with the latest of your patches, Daemond?

I'm pretty sure that KonstaT will merge the patches in his rom.

And for those of you always whining that things don't work and that's easy to fix.... then fix them or go back to stock. I never thought I would have such a great OS when I bought my phone (latest rom was Froyo).

Edited by zeekzar, 20 January 2013 - 11:12 AM.

[96frozen]

-=Extreme=-ShamaN, on 20 January 2013 - 10:59 AM, said:

Such post can not paint you from a good side, maaaaan!

A superior being should give me superpowers to be patient with whiny people...

Let me give you an example: 1-2 months ago konstat said he'd stop developing for the blade because of ungrateful people, then, out of nowhere he released CM10.1 and everyone kept quiet about the whining because konstat in the first post of CM10.1 basicly says this: "I don't care if you're having problems with the rom". After a while people like you came to the forum (again) and started whining once more when the blade only has a kernel and hardware that isn't even supposed to work with 4.x.

Instead of whining, be thankful for having to rely on konstat for the most recent android on your cellphone, for all we know he could buy a new cellphone and stop development here.

Also, if you want everything working go back to gingerbread.

Edited by 96frozen, 20 January 2013 - 12:45 PM.

[daemond]

anantk, on 20 January 2013 - 05:42 AM, said:

Could you please take a look at unfinished work regarding FM radio functionality on CM9/CM10 from Konsta and Jventura at http://www.modaco.co...00#entry2077357 and see whether FM Radio App functionality can be added to our Blades on CM9/CM10/CM10.1 . FM Radio is now the only "Not Working" category for Blade on CM9/CM10/CM10.1.

To be honest, I don't see much of a point in this. The FM radio in the Blade is rubbish, at least in my experience. Reception is bad, but even if you manage to properly receive a station with very strong signal, audio quality is still bad and with a lot of static.

FM support requires a lot of changes all over the Android framework and in various hardware-specific libraries. Someone is trying to get all that FM support ported to CM10.x, if that is successful it should be doable quite easily to make FM work on the Blade. If not, I won't bother.

[jventura]

daemond, on 20 January 2013 - 12:11 PM, said:

To be honest, I don't see much of a point in this. The FM radio in the Blade is rubbish, at least in my experience. Reception is bad, but even if you manage to properly receive a station with very strong signal, audio quality is still bad and with a lot of static.

FM support requires a lot of changes all over the Android framework and in various hardware-specific libraries. Someone is trying to get all that FM support ported to CM10.x, if that is successful it should be doable quite easily to make FM work on the Blade. If not, I won't bother.

Daemond,

again, good catch with that Audio routing problem.. I will port it to my CM9 build, someone mentioned problems with apps like Viber, maybe this fixes it..

About the FM radio, you are right, there are lots of changes that must be done. I've successfully been able to use CM7 radio app (which won't compile in >= ICS) to connect to the FM hardware although I still can't hear any radio.. I've had to adjust patches from CodeAurora from JB to ICS, but they don't seem to work..
I will still try to port things from CM7 to CM9 to see if I can hear something, otherwise will see if the patches by Jerpelea in CM gerrit will make something work..

Keep up the good work!