Hey,

Has anyone experienced regular disconnects on older parrot bluetooth kit using CM9? (doesn't occur using Samsung ROM).

The problem occurs only when using CM9, along with these kits, If i switch to a Samsung ROM, all is fine, if I use a different bluetooth device, all is fine.

I'm happy to run / whatever is required to diagnose the problem, ADB and such is all set up on my laptop (I write apps), just don't know where to start debugging the OS itself though.

- Anthony

Originally Posted by trinode

Hey,

Has anyone experienced regular disconnects on older parrot bluetooth kit using CM9? (doesn't occur using Samsung ROM).

The problem occurs only when using CM9, along with these kits, If i switch to a Samsung ROM, all is fine, if I use a different bluetooth device, all is fine.

I'm happy to run / whatever is required to diagnose the problem, ADB and such is all set up on my laptop (I write apps), just don't know where to start debugging the OS itself though.

- Anthony

Shouldn't have posted it here, but now that you have, post the build id / date, status of the ROM (any mods / custom kernels etc.), and a logcat

I'll try to make a patch to be able to toggle the requirement of a more secure lockscreen when using the keystore or vpn.

The reason is that just installing cacert CA forces you to PIN or pattern lockscreen, which I don't like.

The setting would be in build.prop or local.prop.

What do you think about it? Does it have any chance of being merged?

Julian.

Originally Posted by julianjm

I'll try to make a patch to be able to toggle the requirement of a more secure lockscreen when using the keystore or vpn.

The reason is that just installing cacert CA forces you to PIN or pattern lockscreen, which I don't like.

The setting would be in build.prop or local.prop.

What do you think about it? Does it have any chance of being merged?

Julian.

sounds like a security break. -1

Originally Posted by codeworkx

sounds like a security break. -1

Well, if I have physical access to a device, it doesn't mind the lockscreen the user has. I could just flash a custom rom with no enforced security.

Also, if the user has root (which you can toggle from the ROM settings itself, isn't that a security issue?), there is nothing stopping him from taking full control of the device.

What I mean is... the device will work as usual unless you create a key in build.prop or local.prop. And not having this option don't increase security at all... it's just a little inconvenience for the potential cracker.

Julian.

Edit: Here it is, http://review.cyanogenmod.com/#/c/16584/

Can you please review this change:
http://review.cyanogenmod.com/#/c/14094/

I'm sure that Bulgarian CM9 users would be happy to have a spell checking dictionary for the Bulgarian keyboard.

need option to use 3G only mode!! music player crashes sometimes

Sent from my Galaxy S II via XDA app so sorry if i did any typographical or other mistakes!!

Originally Posted by rajaspidey

need option to use 3G only mode!! music player crashes sometimes

Sent from my Galaxy S II via XDA app so sorry if i did any typographical or other mistakes!!

Wrong thread, try here: http://forum.xda-developers.com/show....php?t=1419102

This thread is for dev issues, requests for features aren't being taken, bug reports aren't being taken, especially not in this thread.

Reboot if CRT-On while on Youtube app?

---

I've struggled a while to make CRT-On effect available on stock Samsung ROMs and now that it's working, we notice that if the screen is turned off while watching a youtube video, when switching back on the CRT-On effect will hang and make the phone reboot after a while.

I've seen previous references for the need to have sources or headers for the "hwcomposer.exynos4.so" library, among others, and since the stack trace for the error comes from there I'm wondering whether you are noticing the same issue.
Can anyone please let me know if you face(d) the same issue and if it eventually has been solved?

My stack trace shows:

05-30 14:04:00.210 1826 1826 I DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000084
05-30 14:04:00.210 1826 1826 I DEBUG : r0 00000048 r1 00000001 r2 00000001 r3 00000001
05-30 14:04:00.210 1826 1826 I DEBUG : r4 000426f0 r5 000426f0 r6 00000001 r7 fffffff8
05-30 14:04:00.210 1826 1826 I DEBUG : r8 000269b0 r9 00000003 10 00043c68 fp 00000004
05-30 14:04:00.210 1826 1826 I DEBUG : ip 400a40c4 sp 40efcb88 lr 00000000 pc 41184d94 cpsr 60000030
...
05-30 14:04:00.345 1826 1826 I DEBUG : #00 pc 00003d94 /system/lib/hw/hwcomposer.exynos4.so
05-30 14:04:00.345 1826 1826 I DEBUG : #01 pc 00019ad2 /system/lib/libsurfaceflinger.so (_ZNK7android10HWComposer6commitEv)
05-30 14:04:00.345 1826 1826 I DEBUG : #02 pc 00018e18 /system/lib/libsurfaceflinger.so (_ZNK7android15DisplayHardware4flipERKNS_6RegionE)
05-30 14:04:00.345 1826 1826 I DEBUG : #03 pc 000200ec /system/lib/libsurfaceflinger.so (_ZN7android14SurfaceFlinger33electronBeamOnAnimat ionImplLockedEv)

which corresponds to:
electronBeamOnAnimationImplLocked() -> hw.flip(screenBounds) -> HWComposer::commit() -> hwc_composer_device_t->set() -> BANG on the Samsung code



PS: sorry for double post, but I posted this initially in the user thread and it's probably more suited for development discussion.

Codeworkxx: Regarding wifi driver and lockscreen: http://forum.xda-developers.com/show...postcount=9753