Jump to content


Photo

[DEV][ROM][8.1.] CyanogenMod 10 (Android 4.1.2)

* * * * * 69 votes

  • Please log in to reply
3134 replies to this topic

#3081
WiiSky70

WiiSky70

    Addict

  • Members
  • PipPipPipPipPip
  • 788 posts
  • Gender:Male
  • Location:Porto (Portugal)
  • Interests:Is not your business...
  • Devices:BQ Aquaris 5
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

  • 1
  • Current Device : BQ Aquaris 5 (JB 4.2) 
  • Optimus Monte Carlo (GB 2.3)  --- >>> SOLD ! 

 

 

 


#3082
snakewhisper

snakewhisper

    Newbie

  • Members
  • Pip
  • 16 posts
Hey, i found a little bug with this rom, i don't know if its a problem regarding cm10.1 all togheter or the port.
I usually only use 2G network to save battery, changing to 3G only when i need it. What happens is that even tough i have 2G selected in the new toggle buttons, when i restart the phone, it allways starts the phone using a 3G connection and show the toggle button as 2G. I need to change it to 3G (even tough it's already using it) and then to 2G.

* Edit
Sorry this was regarding CM10.1, wrong thread :D

Edited by snakewhisper, 17 January 2013 - 04:28 PM.

  • 0

#3083
ilopez85

ilopez85

    Regular

  • Members
  • PipPip
  • 108 posts
Can anyone compile new build with new WiFi theter patch (including WoW one) and working navbar size selection (don't work on 20130114)?

Thanks in advance.

  • 1

#3084
daemond

daemond

    Regular

  • Members
  • PipPip
  • 140 posts
  • Gender:Male
  • Location:Germany
I have another interesting fix for CM10 and CM10.1. Please read this.

  • 2

#3085
elrond_bs

elrond_bs

    Diehard

  • Members
  • PipPipPipPip
  • 395 posts
  • Gender:Male
  • Devices:ZTE Blade
Great work, daemond! :) Ganster tried to fix this, but was unsuccessful.

I hope KonstaT will make a new CM10 build with this fix and the Wifi tethering fix, because now he has very good reasons and CM10 is still more stable (less people have problems) than CM10.1.

  • 0

ZTE Blade with CyanogenMod 11 (Android 4.4.4 KitKat)


#3086
96frozen

96frozen

    Enthusiast

  • Members
  • PipPipPip
  • 159 posts

Great work, daemond! :) Ganster tried to fix this, but was unsuccessful.

I hope KonstaT will make a new CM10 build with this fix and the Wifi tethering fix, because now he has very good reasons and CM10 is still more stable (less people have problems) than CM10.1.


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 :P

  • 0
ROM: CM10 by KonstaT

CWM: GEN2 CWM 6.0.1.1 by Snap.IT

Thank all of the developers topics, rate them 5 stars, they are the people who are keeping your cellphone alive.

Thanks to KonstaT, Snap.IT, tilal6991, daemond, Ganster (this guy is specially awesome for fixing OMX on 4.x ROMS), burstlam and many others that I can't think of right now :D

#3087
-=Extreme=-ShamaN

-=Extreme=-ShamaN

    Newbie

  • Members
  • Pip
  • 8 posts
  • Devices:ZTE Blade

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 :P


Everything is working? Well, how about these:

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:

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.

  • 0

#3088
96frozen

96frozen

    Enthusiast

  • Members
  • PipPipPip
  • 159 posts

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

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


wat?

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.



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 :P
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.

  • 0
ROM: CM10 by KonstaT

CWM: GEN2 CWM 6.0.1.1 by Snap.IT

Thank all of the developers topics, rate them 5 stars, they are the people who are keeping your cellphone alive.

Thanks to KonstaT, Snap.IT, tilal6991, daemond, Ganster (this guy is specially awesome for fixing OMX on 4.x ROMS), burstlam and many others that I can't think of right now :D

#3089
elrond_bs

elrond_bs

    Diehard

  • Members
  • PipPipPipPip
  • 395 posts
  • Gender:Male
  • Devices:ZTE Blade
"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).

  • 0

ZTE Blade with CyanogenMod 11 (Android 4.4.4 KitKat)


#3090
daemond

daemond

    Regular

  • Members
  • PipPip
  • 140 posts
  • Gender:Male
  • Location:Germany
Can anyone please sum up what this "headphone issue" is all about?

  • 0

#3091
96frozen

96frozen

    Enthusiast

  • Members
  • PipPipPip
  • 159 posts

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.

  • 0
ROM: CM10 by KonstaT

CWM: GEN2 CWM 6.0.1.1 by Snap.IT

Thank all of the developers topics, rate them 5 stars, they are the people who are keeping your cellphone alive.

Thanks to KonstaT, Snap.IT, tilal6991, daemond, Ganster (this guy is specially awesome for fixing OMX on 4.x ROMS), burstlam and many others that I can't think of right now :D

#3092
daemond

daemond

    Regular

  • Members
  • PipPip
  • 140 posts
  • Gender:Male
  • Location:Germany
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.

  • 0

#3093
HarryPirate

HarryPirate

    Regular

  • Members
  • PipPip
  • 91 posts
  • Gender:Male
  • Devices:ZTE Libra (Sapo a5)

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?

  • 0
Device: ZTE Libra (Sapo a5)
ROM: The Most Recent CM
Recovery: ClockworkMod 5.0.2.0
External Storage: Transcend 8GB MicroSDHC (Class 4)
Current Launcher: Espier Launcher

#3094
jventura

jventura

    Diehard

  • Members
  • PipPipPipPip
  • 454 posts
  • Gender:Male
  • Location:Portugal
  • Devices:ZTE Blade

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


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

  • 0

#3095
daemond

daemond

    Regular

  • Members
  • PipPip
  • 140 posts
  • Gender:Male
  • Location:Germany
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.

  • 2

#3096
96frozen

96frozen

    Enthusiast

  • Members
  • PipPipPip
  • 159 posts

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 :P

  • 0
ROM: CM10 by KonstaT

CWM: GEN2 CWM 6.0.1.1 by Snap.IT

Thank all of the developers topics, rate them 5 stars, they are the people who are keeping your cellphone alive.

Thanks to KonstaT, Snap.IT, tilal6991, daemond, Ganster (this guy is specially awesome for fixing OMX on 4.x ROMS), burstlam and many others that I can't think of right now :D

#3097
daemond

daemond

    Regular

  • Members
  • PipPip
  • 140 posts
  • Gender:Male
  • Location:Germany
The issue with SIP was that audio did not work at all.

  • 0

#3098
nokiafan02

nokiafan02

    Newbie

  • Members
  • Pip
  • 40 posts

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



:D :D

  • 0

#3099
anantk

anantk

    Regular

  • Members
  • PipPip
  • 124 posts
  • Gender:Male
  • Location:India
  • Devices:Idea Blade

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.

  • 0

#3100
-=Extreme=-ShamaN

-=Extreme=-ShamaN

    Newbie

  • Members
  • Pip
  • 8 posts
  • Devices:ZTE Blade
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?

  • 0




2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users