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

[Guest dinamo1975]

Hi, sorry for the confusion, I was convinced that that was the mistake.

This error appears (it is an error message from the application): http://i.imgur.com/79TdT86.png

And this is the logcat:

 

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

 

It could be an error with the sample rate?

 

In the device Y300 also the same error occurs: http://www.modaco.com/topic/368783-applications-stop-working-cyanogenmod-11-y300/

 

Edit: For what it's worth, I currently use the nightly Dec. 26, voip calls work well.

 

Thank you very much for reviewing the problem.

What "Dialer.apk" you use?

[Guest MetalDroid]

What "Dialer.apk" you use?

I use the dialer.apk which is included in the rom, but I think it has nothing to do with the failure of the line and viber calls (VoIP calls).

[Guest rhen]

For the people complain about the MMS sending/receiving with data disabled. Install today's nightly:

c273007 Mms: Add configuration for sending and receiving Mms with data disabled

Anyway there are a lots of changes in telephony related services in today's nightly.

[Guest 7arfoush]

Hey,

Is the problem in the camera app still exist in today's nightly?

And it would be great if the homescreen app icon is saved weither the apps are installed or not, everytime I restart the device I've to place the apps in the dock bar and the homescreen again (Only apps in the SD card)

And a transparent status bar in the lock screen also would be good, and without the ability of opening notifications as it bypasses the lock whatever it's.

[Guest pejicgoran]

Problem with attachmants in email.apk still exist.

@rhen:Try to send jpg from gmail to your email and save it on email.apk.Then try to find it in download folder.

[Guest rhen]

Hey,

Is the problem in the camera app still exist in today's nightly?

And it would be great if the homescreen app icon is saved weither the apps are installed or not, everytime I restart the device I've to place the apps in the dock bar and the homescreen again (Only apps in the SD card)

And a transparent status bar in the lock screen also would be good, and without the ability of opening notifications as it bypasses the lock whatever it's.

Camera is still working.

I don't know how the transparent status bar looks like on lock screen when turned on, but on home screen works. If it don't work in lock screen, I think it will be fixed later by cyanogenmod team.

The status bar behavior you described is normal. The status bar is accessible on lock screen except you use a pin/pattern etc lock.

 

Problem with attachmants in email.apk still exist.

@rhen:Try to send jpg from gmail to your email and save it on email.apk.Then try to find it in download folder.

Do you use the email app, or the gmail app?

I have never used the email app.

 

 

Ps.: Today's nightly has problem with data connection. Dazzozo made a change in the source today, so it can be fixed in tomorrow's build.

[Guest pejicgoran]

@rhen:I am using a email.apk on every rom and it is very importment to me and this is a bug becouse when you recive a jpg you can not find them later.

[Guest rhen]

@rhen:I am using a email.apk on every rom and it is very importment to me and this is a bug becouse when you recive a jpg you can not find them later.

Just tried out email app with my rarely used hotmail account and works fine. I can save images. The images placed in the download folder as in GMail. (/storage/sdcard0/Download/)

I think you do something wrong.

[Guest pejicgoran]

On gmail everything works fine.Attachmant saved in dowmload folder but when you us email.apk attachmant is gone.

[Guest rhen]

On gmail everything works fine.Attachmant saved in dowmload folder but when you us email.apk attachmant is gone.

I can't help you more. It works for me in gmail and email app too. 

[Guest qwertyu123]

Ps.: Today's nightly has problem with data connection. Dazzozo made a change in the source today, so it can be fixed in tomorrow's build.

 

I have problems with data connection as well since last big telephony update, sometimes I don't know the reason it doesn't get activated.

I see the change that dazz made is for u8833, this does also apply to g300?

Anyone else with problems? Any change with today's build?

[Guest rhen]

I have problems with data connection as well since last big telephony update, sometimes I don't know the reason it doesn't get activated.

I see the change that dazz made is for u8833, this does also apply to g300?

Anyone else with problems? Any change with today's build?

Today's build still broken.

We need this change, but still haven't merged: http://review.cyanogenmod.org/#/c/60641/

I'll post it here if it gets into the ROM.

[Guest hunter`]

so, what's the last working nightly? 03/03 ?

[Guest rhen]

so, what's the last working nightly? 03/03 ?

Yes.

[Guest 7arfoush]

Today's nightly is notably much faster than the previous ones, I guess I'll keep it till I find a problem.

The camera app gives me "Unfortunately, Camera has stopped" everytime I try to open it, the problem is therr since I updated to 2-26 nightly I guess.

[Guest rhen]

Today's nightly is notably much faster than the previous ones, I guess I'll keep it till I find a problem.

The camera app gives me "Unfortunately, Camera has stopped" everytime I try to open it, the problem is therr since I updated to 2-26 nightly I guess.

Don't you experience data connection problems?

 

Camera app work fine. If you install an older build that worked for you again, it work? (maybe the problem is with your camera)

Do a nandroid backup and install a version that has worked for you before to check if the problem is with the ROM.

[Guest 7arfoush]

Wi-Fi works without problems, and I can't tell if there's a problem with carrier's data connection since it sucks in Egypt no matter what.

And I have to do that 'sign in as ___' step in the browser everytime I open it.

And Multitasking is great now, I don't know what happened but I can open 4 apps including the browser without having tabs reloading everytime I select them.

[Guest rhen]

Wi-Fi works without problems, and I can't tell if there's a problem with carrier's data connection since it sucks in Egypt no matter what.

And I have to do that 'sign in as ___' step in the browser everytime I open it.

And Multitasking is great now, I don't know what happened but I can open 4 apps including the browser without having tabs reloading everytime I select them.

WiFi is fine, the problem is with mobile data.

 

I don't know what version you used before, the multitasking improvement may the result of the enabled zram. (but this is enabled since 20140205)

 

Edit:

The fix for data connection problem has been merged.

It should be in the tomorrow's build.

 

Possible fix for VOIP calls has been merged too.

Edited March 5, 2014 by rhen

[Guest rhen]

doublepost.

Edited March 5, 2014 by rhen

[Guest MetalDroid]

I'm looking forward to updating this night. :D

[Guest razor74]

Compressing ram it means much CPU usage. And this is the big problem of this device. It has a single core. For me , with zram activated , the phone becomes slighty slower...

[Guest rhen]

Compressing ram it means much CPU usage. And this is the big problem of this device. It has a single core. For me , with zram activated , the phone becomes slighty slower...

Now you can't change it.

It is turned on by default and no option to change this.

If you haven't notice the change a month ago, the impact of the zram has no noticeable drawback.

[Guest cjcandrei]

The kernel should be compiled with linaro tools if it does not already. For ics if I installed a kernel compiled with linaro, the whole system was much smoother ... Also oc would help a lot with the zram enabled by default ...

Thanks.

[Guest fiona_stargatefan]

Hi,

I've been having problems with the phone not recognising the storage since I installed 11.0. I'm going to do a clean install and I've gone right back to the start and re-installed the Huwaei g300 drivers etc. When I try to root the 'phone, even though I've rooted it previously it doesn't seem to work. I get a message- error: device offline

It then retries and I get error: device offline again. It then says install complete & phone will reboot (but it doesn't).

 

Given it's already rooted (and I've unlocked the bootloader) does this matter?

Fiona

PS I'm using Windows 8

[Guest goodfella123]

Aplogies if i'm hijacking and posting in the wrong place.

Is it possible to flash this kitkat rom straight from slimbean 4.2.2 v8?

My CWM is 4.0.1.5 and i have baseband 2030, do i need to flash CWM 6.0.4.5 before the kitkat rom?