Jump to content

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


Guest Dazzozo

Recommended Posts

Hl all

When im in a call and when i want to use speaker, the volume e very low.

Is there a way to fix this?

Cheers...

Nomax

Turn it up? Or have you already tried that ;) :lol:

Link to comment
Share on other sites

Hi all. I'm new to these stuff. So I don't know (almost  :D ) anything. Does this rom get updates regulary? And I heard that there's a problem with wifi hotspot and autofocus. Is it true? Thanks. (Sorry for bad English)

 

Edit: If it gets updates, how can I install them without losing data?

Edited by pasham
Link to comment
Share on other sites

Does this rom get updates regulary? And I heard that there's a problem with wifi hotspot and autofocus. Is it true? 

 

Well the name of the thread is...

 

[KK] [4.4.2] CyanogenMod 11.0 [ROM] [NIGHTLY BUILDS AVAILABLE]

 

Search the thread for details of current issues and workarounds where applicable.

Edited by dalyer
Link to comment
Share on other sites

Guest trumpet-t1

Today when I was listening music on Apollo and playlist finished (no loop) I clicked next song and player suspend then phone was not responding. I had to pull out battery to restart phone.
 
If someone have problems with dashclock widget gmail extension try this

Link to comment
Share on other sites

Guest MetalDroid

I suspect that the VoIP fails because some XML files in the folder Permissions missing. (Missing 4 files). In other phones using CM11 it might solve. Tomorrow I try to see if we are lucky.
 
Edit: didn't work. :(
 
Edit2:
Here is the logcat (at failure):
 
 

02-21 03:22:14.119 I/Test (1332): msgId: 24


02-21 03:22:14.469 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:15.069 I/Choreographer(1332): Skipped 34 frames! The application may be doing too much work on its main thread.
02-21 03:22:15.179 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:15.269 I/ActivityManager(1332): Timeline: Activity_idle id: android.os.BinderProxy@41946b28 time:1486726
02-21 03:22:15.609 I/ActivityManager(578): Timeline: Activity_windows_visible id: ActivityRecord{41f451c0 u0 com.gau.go.launcherex/com.jiubang.ggheart.apps.desks.diy.GoLauncher t1} time:1487062
02-21 03:22:15.889 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:16.539 W/Test (1332): onInterceptTouch mIsDragging: false
02-21 03:22:16.609 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:16.719 I/ActivityManager(1332): Timeline: Activity_launch_request id:jp.naver.line.android time:1488176
02-21 03:22:16.879 I/Test (1332): onPause
02-21 03:22:16.879 I/Test (1332): msgId: 41
02-21 03:22:16.889 I/Test (1332): onPause: com.jiubang.shell.common.component.ShellContentView{41c0d920 V.E..... ........ 0,0-480,800 #0}
02-21 03:22:17.319 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:17.579 I/ActivityManager(3464): Timeline: Activity_idle id: android.os.BinderProxy@4214ffe0 time:1489032
02-21 03:22:17.669 I/ActivityManager(578): Timeline: Activity_windows_visible id: ActivityRecord{422a12c0 u0 jp.naver.line.android/.activity.main.MainActivity t15} time:1489125
02-21 03:22:17.739 I/ggheart (1332): onStop
02-21 03:22:17.739 I/Test (1332): onStop
02-21 03:22:17.739 I/Test (1332): msgId: 25
02-21 03:22:18.029 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:18.749 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:19.459 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:20.169 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=2, nb=0
02-21 03:22:20.229 I/ActivityManager(3464): Timeline: Activity_launch_request id:jp.naver.line.android time:1491689
02-21 03:22:20.859 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=1, nb=1
02-21 03:22:21.309 I/ActivityManager(3464): Timeline: Activity_idle id: android.os.BinderProxy@423689a8 time:1492764
02-21 03:22:21.319 I/ActivityManager(578): Displayed jp.naver.line.android/jp.naver.voip.android.activity.VoipActivity: +852ms (total +31s208ms)
02-21 03:22:21.319 I/ActivityManager(578): Timeline: Activity_windows_visible id: ActivityRecord{4213e068 u0 jp.naver.line.android/jp.naver.voip.android.activity.VoipActivity t37} time:1492775
02-21 03:22:21.529 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:21.599 I/MediaFocusControl(578): AudioFocus requestAudioFocus() from android.media.AudioManager@423b4b38kr.naver.amp.android.internal.AmpSoundManager$AmpMusicControllerWithAudioFocus8@4238a520
02-21 03:22:22.249 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:22.379 I/Choreographer(3464): Skipped 30 frames! The application may be doing too much work on its main thread.
02-21 03:22:22.959 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:23.669 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:24.269 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.269 W/AudioHardwareMSM76XXA(136): rpc_snd_set_device(0, 0, 1)
02-21 03:22:24.279 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.319 I/AudioHardwareMSM76XXA(136): do input routing device 400000
02-21 03:22:24.319 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.319 W/AudioHardwareMSM76XXA(136): rpc_snd_set_device(0, 0, 1)
02-21 03:22:24.319 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: format
02-21 03:22:24.319 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: bufferSize
02-21 03:22:24.319 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: format
02-21 03:22:24.319 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: sampleRate
02-21 03:22:24.329 I/AudioHardwareMSM76XXA(136): do input routing device 400000
02-21 03:22:24.329 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.329 W/AudioHardwareMSM76XXA(136): rpc_snd_set_device(0, 0, 1)
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: bufferSize
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: format
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: sampleRate
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: bufferSize
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): AudioStreamOutDirect: sampleRate
02-21 03:22:24.329 E/AudioFlinger(136): no playback thread found for output handle 27
02-21 03:22:24.329 E/AudioTrack(3464): AudioFlinger could not create track, status: -22
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): Not closing MVS driver
02-21 03:22:24.329 E/AudioHardwareMSM76XXA(136): Not closing MVS driver
02-21 03:22:24.329 W/AudioSystem(136): ioConfigChanged() closing unknown output! 27
02-21 03:22:24.329 W/AudioSystem(578): ioConfigChanged() closing unknown output! 27
02-21 03:22:24.329 W/AudioSystem(895): ioConfigChanged() closing unknown output! 27
02-21 03:22:24.339 W/AudioSystem(3464): ioConfigChanged() closing unknown output! 27
02-21 03:22:24.339 W/AudioSystem(1452): ioConfigChanged() closing unknown output! 27
02-21 03:22:24.339 E/AudioTrack-JNI(3464): Error initializing AudioTrack
02-21 03:22:24.339 E/android.media.AudioTrack(3464): Error code -20 when initializing AudioTrack.
02-21 03:22:24.339 I/AudioHardwareMSM76XXA(136): do input routing device 400000
02-21 03:22:24.339 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.429 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:24.429 W/System.err(3464): java.lang.IllegalStateException: play() called on uninitialized AudioTrack.
02-21 03:22:24.439 W/System.err(3464): at android.media.AudioTrack.play(AudioTrack.java:999)
02-21 03:22:24.439 W/System.err(3464): at dalvik.system.NativeStart.run(Native Method)
02-21 03:22:24.509 I/AudioHardwareMSM76XXA(136): do input routing device 400000
02-21 03:22:24.509 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.509 W/AudioHardwareMSM76XXA(136): rpc_snd_set_device(0, 0, 1)
02-21 03:22:24.529 I/AudioHardwareMSM76XXA(136): do input routing device 400000
02-21 03:22:24.529 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:24.529 W/AudioHardwareMSM76XXA(136): rpc_snd_set_device(0, 0, 1)
02-21 03:22:25.149 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:25.859 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:26.039 I/AudioHardwareMSM76XXA(136): Routing audio to Handset
02-21 03:22:26.039 W/AudioHardwareMSM76XXA(136): rpc_snd_set_device(0, 1, 1)
02-21 03:22:26.069 I/MediaFocusControl(578): AudioFocus abandonAudioFocus() from android.media.AudioManager@423b4b38kr.naver.amp.android.internal.AmpSoundManager$AmpMusicControllerWithAudioFocus8@4238a520
02-21 03:22:26.649 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:27.359 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:28.069 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:28.789 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:29.499 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:29.889 I/ActivityManager(3464): Timeline: Activity_idle id: android.os.BinderProxy@4214ffe0 time:1501348
02-21 03:22:30.209 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:30.619 I/ActivityManager(578): Timeline: Activity_windows_visible id: ActivityRecord{422a12c0 u0 jp.naver.line.android/.activity.main.MainActivity t15} time:1502078
02-21 03:22:30.929 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1
02-21 03:22:31.639 E/Sensors (578): sensors_poll_context_t::pollEvents, line 202: receive event #### i=3, nb=1

 

Perdón por mi inglés.

Edited by MetalDroid
Link to comment
Share on other sites

Guest razor74

I think there are much important problems to resolve than adding overclocking. Very slow loading widgets(almost two minutes)  for HD widgets or other widgets after boot, almost unusable gps ( with any app) in some cases because of slow gps refresh. I encounter  gps refresh of 5-10 secconds sometimes. Loosing audio settings (tone settings) from time to time (need audio player restart or phone restart), etc.

Link to comment
Share on other sites

I think there are much important problems to resolve than adding overclocking. Very slow loading widgets(almost two minutes)  for HD widgets or other widgets after boot, almost unusable gps ( with any app) in some cases because of slow gps refresh. I encounter  gps refresh of 5-10 secconds sometimes. Loosing audio settings (tone settings) from time to time (need audio player restart or phone restart), etc.

 

Did you post a logcat to help the developer investigate such issues?

Link to comment
Share on other sites

Guest cjcandrei

Bit rude demanding stuff from a voluntary developer... :mellow:

Bit rude demanding stuff from a voluntary developer... :mellow:

Never meant to be rude, just I know he is strugling to make oc work on both y300 and g300, y300 being the problem... probably it's much easier on g300. Sorry if this seamed rude...
Link to comment
Share on other sites

Guest bidzapfc

@rhen

 

When you have time, it would be nice to activate /cust partition and to transfer not updateable apk from /system there as it has 76 mb of space.

 

Instructions are here
http://4pda.ru/forum/index.php?showtopic=358122&st=4800#entry22089120

 

I would do it but I'm messing around with repack of b952, and you are pretty active with cm11

Link to comment
Share on other sites

Guest fiona_stargatefan

I've been using 11.0 since early January and installing the latest nightly every week or so. However, I've still got a number of Apps that don't work 'cause the external storage doesn't seem to be recognised - camera doesn't work, Amazon appstore can't download anything, CM updater doesn't work 'cause it can't download etc. etc.

 

I've searched the forum but no-one else seems to have this problem - any suggestions?

 

I used the "offical" bootloader unlock process and I've wiped the caches on multiple occasions.

 

Fiona.

 

Link to comment
Share on other sites

Guest razor74

Yes. It seems that storage locations  are inversed. SD card(external) is internal storage and internal storage it is seen as external storage SD card. But CM updater works if you helped a bit. If you manually move downloaded nightly to internal storage in the same cm updater folder, will work.

But the same problem is  at CM 10.2 too.

Link to comment
Share on other sites

Guest TamerlanW

On versions of CM 11 from February 22 and 23 does not work when switching ART - goes into a cyclic reboot .... Who uses ART - probably better not to. :excl:

 

P.S. Sorry my bad english...

Link to comment
Share on other sites

Guest fiona_stargatefan

Yes. It seems that storage locations  are inversed. SD card(external) is internal storage and internal storage it is seen as external storage SD card. But CM updater works if you helped a bit. If you manually move downloaded nightly to internal storage in the same cm updater folder, will work.

But the same problem is  at CM 10.2 too.

Mmm, my problem is perhaps different. The internal storage isn't visible (via file manager or when I connect the phone to the computer). CM updater won't even download - presumably 'cause the 'phone thinks there isn't any external storage. Any suggestions welcome.

Fiona

PS I've tried making external storage as primary, that doesn't help at all

Link to comment
Share on other sites

Guest bigas80
I have a few problems: 
1. when call me there is a delay in turning the screen, this also when I turn on the screen 
2. if the phone is fully discharged, the reboot I lose the audio settings of notifications and the background image 
3. Notification lights are wrong, imposed green and white displays
Link to comment
Share on other sites

Guest Tommy.35

If I download to the device in Google Play Music some songs, and hit play, phone freeze, maybe u cant chech this out? :)

Its freeze too if i play any music from Google Play Unlimited :(

Edited by Tommy.35
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.