[KK] [4.4.4] CyanogenMod 11.0 [ROM] [WEEKLY BUILDS ON FRIDAY]

[Guest Venael]

anyone experiencing gps issues like me? endomondo cant save any track despite it says "gps ok" what means that gps fix is locked. No idea what can be the reason, other programs can work fine.

[Guest MetalDroid]

Edited. My fault.

Edited April 8, 2014 by MetalDroid

[Guest norayrhajian]

I had this rom installed, then put another on, and now I can't seem to get this put back on.  It says it is installed but when I reboot the phone, it just sits and sits and sits on the Huawei logo and the little CyanogenMod logo doesn't come up.  I think I've waited 10 minutes.  Am I being too impatient?

 

I used the same cvm that I had originally used.  Any thoughts?

[Guest dalyer]

Did you do all wipes/formats in CWM/TWRP for a clean install?

[Guest guda]

hello , im a little confused about the signal lost solution. i read a lot of post , and i understand that the solution is official bootloader unlocker in the huawei page right?

i used the huaweig300.com steps to root, bootload unlock and clockwork mode, after that i installed the last version of clockwork of dazzozo and this KK rom...

and this is the part that i cant understand, i have to do what to official unlock?
install oficial rom ics, relock bootloader, official unlock, and after this i need to root again to install clockworkmod again? or only install it ? i really like this rom and the signal lost is killing me...

Please , help me...
cumps from portugal to the world

[Guest dalyer]

hello , im a little confused about the signal lost solution. i read a lot of post , and i understand that the solution is official bootloader unlocker in the huawei page right?

i used the huaweig300.com steps to root, bootload unlock and clockwork mode, after that i installed the last version of clockwork of dazzozo and this KK rom...

and this is the part that i cant understand, i have to do what to official unlock?

install oficial rom ics, relock bootloader, official unlock, and after this i need to root again to install clockworkmod again? or only install it ? i really like this rom and the signal lost is killing me...

Please , help me...

cumps from portugal to the world

 

Read the tutorial - it explains how to do an official bootloader unlock.

 

http://www.modaco.com/topic/362821-tutorial-how-to-officially-unlock-the-bootloader-with-definitions-relock-guide-included/page-1

 

If you have problems getting the unlock code from Huawei then this approach may work:

 

http://www.modaco.com/topic/362821-tutorial-how-to-officially-unlock-the-bootloader-with-definitions-relock-guide-included/page-17#entry2168479

 

But please read all of the tutorial thread first.

Edited April 9, 2014 by dalyer

[Guest guda]

Read the tutorial - it explains how to do an official bootloader unlock.

 

http://www.modaco.com/topic/362821-tutorial-how-to-officially-unlock-the-bootloader-with-definitions-relock-guide-included/page-1

 

If you have problems getting the unlock code from Huawei then this approach may work:

 

http://www.modaco.com/topic/362821-tutorial-how-to-officially-unlock-the-bootloader-with-definitions-relock-guide-included/page-17#entry2168479

 

But please read all of the tutorial thread first.

this is the post that i already read it... and its to much info there... i just want to understand if the steps that i wrote before are right... 

 

1- install oficial ics rom

2-relock bootloader

3-unlock bootloader oficial http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=pre

4-install clockwork mode 

5- install rom CM11

i realy want to unlock it official because i already unlock like i said before and the network is not ok... i already tried your method of dc.unlocker and didnt work here, thats why i used the huaweig300.com method... 

sorry about my english bro and thank you for the reply 

[Guest dalyer]

Installing official ICS (e.g. B952) also installs the original locked bootloader so step 2 in your list is redundant.

You probably also have to re-root before step 4?

DC Unlocker will not work unless you have stock ICS installed. And even then it may not work for some people.

[Guest bidzapfc]

dalyer, i admire you... you are a GOD with these things. they all come here, doing before reading/asking and then they expect someone to take out his magic wand and fix their problems. keep up man...

[Guest sueboy]

Edited. My fault.

 

I have same question or problem~~  I follow your setp, try to change setting. but can't ok. My hangouts can use. Skype can use. Only line can't use. same error code 104.

 

If I use cm10, very old version. Line is ok~ so I think problem in CM11. And you test 20131230 rom can use. Just Hope Someone Can Help Us.  I am programer but domain in Web, Erp....

not ROM.......  Thank you try many many time~~

Edited April 9, 2014 by sueboy

[Guest MetalDroid]

I have same question or problem~~  I follow your setp, try to change setting. but can't ok. My hangouts can use. Skype can use. Only line can't use. same error code 104.

 

If I use cm10, very old version. Line is ok~ so I think problem in CM11. And you test 20131230 rom can use. Just Hope Someone Can Help Us.  I am programer but domain in Web, Erp....

not ROM.......  Thank you try many many time~~

The problem is that our framework developer can not do the tests with LINE. He makes testing Viber (device users on him). I have asked users in a thread of Konstat that if they can prove LINE calls, but nobody seems to use it there.

In any case I'm sure that to them does not work either.

Finally, I contacted LINE developers to see if they can check the fault (Viber works and is the same).

Until then, we will continue with the nightly Dec. 27 (or the Mod 30 December).

Greetings.

[Guest pejicgoran]

What is LINE calls?

Edited April 9, 2014 by pejicgoran

[Guest Tentmaster]

What is LINE calls?

 

Google is your friend. :P

[Guest dalyer]

This I presume?

 

http://en.wikipedia.org/wiki/Line_(application)

[Guest sueboy]

The problem is that our framework developer can not do the tests with LINE. He makes testing Viber (device users on him). I have asked users in a thread of Konstat that if they can prove LINE calls, but nobody seems to use it there.

In any case I'm sure that to them does not work either.

Finally, I contacted LINE developers to see if they can check the fault (Viber works and is the same).

Until then, we will continue with the nightly Dec. 27 (or the Mod 30 December).

Greetings.

 

cm11 on January 2014, I install rom Dazzozo, Install finish. Can use Line voip and video call. but just maybe 1 day or 2 day. That time hangouts and skype is ok.

After 1 or 2 days Line can't work, have 104 error code. That time I no change any rom or setting. So I search internet, someone say because open art setting.

but I try install new rom, clean system  for test. Line still can't work. 

 

I confuse, I not do anythings. January and Feb I search internet, have many people get this problem. If use cm11 early, easy get this problem. So I think, maybe this bug for line.

wait wait wait 2 months. Line change many version for Line call out. this problem still have error code 104. so now I think or sure problem in cm11.

 

between this time, I try many cm11, even new linux kernel, but can't work. only old cm10 can work. but g510 only use cm11, that can get very good performance..(thank Dazzozo)

 

before less people use cm11. now more people use. so I search internet get more message about Line 104 in cm11. I check Line website, Q&A no this problem. but some Fourm have people get this problem and don't know how to fix.

 

Line in asia is more than 400 million people, My friends use Line very Public, hangouts very less. skype for $, very good quality voip and video call. So just keep hope.

 

Thank MetalDroid.

Edited April 10, 2014 by sueboy

[Guest okkbojan]

WiFi not working! I can't turn on WiFi ! Any solution?

[Guest pejicgoran]

Reboot.

Edited April 10, 2014 by pejicgoran

[Guest okkbojan]

Reboot.

Rebooted million times and still the same no WiFi!

[Guest MetalDroid]

Rebooted million times and still the same no WiFi!

Restart your router.

[Guest MetalDroid]

Hi, I just created a logcat of the LINE calls and Viber calls.

 

Here the result:

 

LINE (NOT working):

 

LINE

03:40:48.079 I/MediaFocusControl( 567): AudioFocus requestAudioFocus() from android.media.AudioManager@42a4fd48kr.naver.amp.android.internal.AmpSoundManager$AmpMusicControllerWithAudioFocus8@41f02568
04-11 03:40:51.069 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:51.069 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 03:40:51.079 I/AudioHardwareMSM76XXA( 136): Setting in-call volume to 3 (available range is 2 to 7)
04-11 03:40:51.119 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 03:40:51.119 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:51.119 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 03:40:51.129 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 03:40:51.129 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:51.129 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: format
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: sampleRate
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: format
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: format
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: bufferSize
04-11 03:40:51.139 I/AudioFlinger( 136): HAL output buffer size 160 frames, normal mix buffer size 160 frames
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: bufferSize
04-11 03:40:51.139 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: format
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: sampleRate
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: bufferSize
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: format
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: sampleRate
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: bufferSize
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: format
04-11 03:40:51.149 E/AudioHardwareMSM76XXA( 136): AudioStreamOutDirect: sampleRate
04-11 03:40:51.149 E/AudioFlinger( 136): createTrack_l() Bad parameter: sampleRate 16000 format 1, channelMask 0x00000001 for output 0x4003efd0 with format 1
04-11 03:40:51.149 E/AudioTrack( 3695): AudioFlinger could not create track, status: -22
04-11 03:40:51.159 I/AudioFlinger( 136): AudioFlinger's thread 0x41abb4a0 ready to run
04-11 03:40:51.159 E/AudioTrack-JNI( 3695): Error initializing AudioTrack
04-11 03:40:51.169 E/android.media.AudioTrack( 3695): Error code -20 when initializing AudioTrack.
04-11 03:40:51.169 E/AudioHardwareMSM76XXA( 136): Not closing MVS driver
04-11 03:40:51.179 E/AudioHardwareMSM76XXA( 136): Not closing MVS driver
04-11 03:40:51.179 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 03:40:51.179 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:51.369 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 03:40:51.369 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:51.369 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 03:40:51.389 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 03:40:51.389 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:51.389 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 03:40:53.189 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 03:40:53.189 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 03:40:53.219 I/MediaFocusControl( 567): AudioFocus abandonAudioFocus() from android.media.AudioManager@42a4fd48kr.naver.amp.android.internal.AmpSoundManager$AmpMusicControllerWithAudioFocus8@41f02568

 

Viber (WORKING):

 

VIBER

04-11 04:19:42.268 I/MediaFocusControl( 567): AudioFocus requestAudioFocus() from android.media.AudioManager@41b7a4a0com.viber.voip.sound.AudioFocusController$1@41b87488
04-11 04:19:42.368 I/AudioHardwareMSM76XXA( 136): Setting in-call volume to 0 (available range is 2 to 7)
04-11 04:19:42.478 I/AudioHardwareMSM76XXA( 136): Setting in-call volume to 3 (available range is 2 to 7)
04-11 04:19:42.488 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:42.488 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:19:52.348 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:19:52.348 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:52.348 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:19:52.358 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:19:52.358 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:52.358 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:19:52.368 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:19:52.368 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:52.368 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:19:52.418 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:52.418 W/AudioHardwareMSM76XXA( 136): VoipCall in MODE_IN_COMMUNICATION
04-11 04:19:52.418 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 04:19:52.448 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:19:52.448 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:52.448 W/AudioHardwareMSM76XXA( 136): VoipCall in MODE_IN_COMMUNICATION
04-11 04:19:52.448 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 0, 1)
04-11 04:19:52.458 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:19:52.458 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:19:52.598 W/AudioFlinger( 136): RecordThread: buffer overflow
04-11 04:19:52.598 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:20:01.978 W/AudioFlinger( 136): RecordThread: buffer overflow
04-11 04:20:09.408 W/AudioFlinger( 136): RecordThread: buffer overflow
04-11 04:20:10.328 I/MediaFocusControl( 567): AudioFocus abandonAudioFocus() from android.media.AudioManager@41b7a4a0com.viber.voip.sound.AudioFocusController$1@41b87488
04-11 04:20:10.338 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:20:10.368 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:20:10.368 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:20:10.378 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:20:10.418 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:20:10.418 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:20:10.418 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:20:10.438 I/AudioHardwareMSM76XXA( 136): do input routing device 400000
04-11 04:20:10.438 I/AudioHardwareMSM76XXA( 136): Routing audio to Handset
04-11 04:20:10.438 W/AudioHardwareMSM76XXA( 136): rpc_snd_set_device(0, 1, 1)
04-11 04:20:12.138 I/MediaFocusControl( 567): AudioFocus abandonAudioFocus() from android.media.AudioManager@41b7a4a0com.viber.voip.sound.AudioFocusController$1@41b87488

 

It is observed that Viber uses "rpc_snd_set_device (0, 1, 1)"

While LINE uses "rpc_snd_set_device (0, 0, 1)" (except at the end).

We may be able to fix it by editing "audio_policy.conf".

Any cook can help us?

 

On the other hand, we see the following error:

 

E/AudioFlinger( 136): createTrack_l() Bad parameter: sampleRate 16000 format 1, channelMask 0x00000001 for output 0x4003efd0 with format 1

 

Greetings.

[Guest okkbojan]

Restart your router.

I can not turn on wifi. The display shows that the wifi starts and never turns on. I do not see even one network!

[Guest eurogon]

dear Dazzozo please correct graphical artifacts in the browser as borders

 

displaying in another browser

 

also does your ROM is not working with voice search (voicesearch.apk) 

 

 

make corrections please  :)

 

[Guest norayrhajian]

Somewhere along the way of trying to get a decent working ROM, I installed one that basically disabled my 3G connection.  Now, when I put CyanogenMod back on (or any other) I get it installed but no 3G.

 

If someone has a suggestion on how I can get my 3G up again on my Y300-0150, I would be so grateful.

[Guest derfuhrer2007]

Is there any way of having the mass storage show only the SD card, as right now it is showing both and my TV can't read it because of that.

[Guest Meglestus]

Somewhere along the way of trying to get a decent working ROM, I installed one that basically disabled my 3G connection.  Now, when I put CyanogenMod back on (or any other) I get it installed but no 3G.

 

If someone has a suggestion on how I can get my 3G up again on my Y300-0150, I would be so grateful.

Do a wipe and then reinstall KK rom. (Not sure if it works though)