Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

CyanogenMod 11.0 for Photon Q

OP kabaldan

16th December 2014, 11:27 PM   |  #101  
kabaldan's Avatar
OP Recognized Developer
Flag Prague
Thanks Meter: 3,497
 
1,461 posts
Join Date:Joined: Dec 2009
Donate to Me
More
Quote:
Originally Posted by Fr4gg0r

My notification light always lights up in white, regardless of the color I set in the settings. -.-
Is that a known bug?

The Photon Q (and also other moto_msm8960 devices) RGB LEDs behave in a binary way - they can be only on or off.
You can't change their brightness and mix various amounts of different colours to get the full colour palette.
So you can have only 7 different colours of notification LED (2^3 = 8 which includes all three LEDs off - black).
ff0000 is the same as 010000 - red LED on.

You have to make sure that at least one of the RGB values is zero, otherwise it means all three (R & G & B) LEDs are on = white light.

Code:
ff0000 - red
00ff00 - green
0000ff - blue
ffff00 - yellow
ff00ff - magenta
00ffff - cyan
ffffff - white
The Following 2 Users Say Thank You to kabaldan For This Useful Post: [ View ]
17th December 2014, 08:35 PM   |  #102  
Member
Flag San Jose
Thanks Meter: 7
 
39 posts
Join Date:Joined: Jun 2014
More
I just upgraded to 16-December's nightly and sliding open the keyboard doesn't unlock the phone anymore. I looked thru settings incase there was something there but couldn't find anything. It used to unlock (although quite slow) on my previous version but I didn't take note of what that was, something from late october or early november I think.
18th December 2014, 10:29 PM   |  #103  
Fr4gg0r's Avatar
Recognized Developer
Flag Bremen
Thanks Meter: 682
 
686 posts
Join Date:Joined: Aug 2010
Donate to Me
They unmerged that patch, after people reported problems on nexus 5. I was too lazy to implement an option for that. -_-

By the way, does one of the photon q kernel devs know why it takes so long for the phone to wake up when opening the slider? If I listen for the SW_LID event with
Code:
getevent -lt /dev/input/event0
I can observe a significant delay until the screen is turned on. It appears to show a greater lag than compared to the power button. Is it not interrupt triggered?

Anyway, maybe I am gonna start to publish a custom CM build for our photon q, with such options (and other stuff ) enabled. The question is, is it worth doing this for 4.4 (with 5.0 around the corner)?
Anyone else in?
Last edited by Fr4gg0r; 18th December 2014 at 10:36 PM.
The Following 2 Users Say Thank You to Fr4gg0r For This Useful Post: [ View ]
21st December 2014, 05:10 PM   |  #104  
Junior Member
Thanks Meter: 0
 
18 posts
Join Date:Joined: Aug 2013
Question Is it a bug?
Whenever i tap on "Settings"->"Data usage" I get "Unfortunately, Settings has stopped" message and Settings closes. Apps from Market, like Data Monitor or My Data Manager works fine.

Motorola Photon Q, CyanogenMod 11-20141112-SNAPSHOT-M12-moto_msm8960_jbbl
logcat:
Code:
12-21 02:01:59.209 I/ActivityManager(849): START u0 {act=android.settings.SETTINGS flg=0x14000000 cmp=com.android.settings/.Settings} from pid 1114
12-21 02:01:59.239 V/PanelView(1114): animationTick called with dtms=0; nothing to do (h=888.0 v=-3000.0)
12-21 02:01:59.579 I/Timeline(7029): Timeline: Activity_idle id: android.os.BinderProxy@42060780 time:301114658
12-21 02:02:00.320 I/Timeline(849): Timeline: Activity_windows_visible id: ActivityRecord{420591d8 u0 com.android.settings/.Settings t325} time:301115392
12-21 02:02:00.370 I/Choreographer(1114): Skipped 41 frames!  The application may be doing too much work on its main thread.
12-21 02:02:01.111 I/Timeline(7029): Timeline: Activity_launch_request id:com.android.settings time:301116195
12-21 02:02:01.111 I/ActivityManager(849): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 7029
12-21 02:02:01.211 D/SubSettings(7029): Launching fragment com.android.settings.DataUsageSummary
12-21 02:02:03.854 E/JavaBinder(7029): !!! FAILED BINDER TRANSACTION !!!
12-21 02:02:03.854 D/AndroidRuntime(7029): Shutting down VM
12-21 02:02:03.854 W/dalvikvm(7029): threadid=1: thread exiting with uncaught exception (group=0x417dece0)
12-21 02:02:03.864 E/AndroidRuntime(7029): FATAL EXCEPTION: main
12-21 02:02:03.864 E/AndroidRuntime(7029): Process: com.android.settings, PID: 7029
12-21 02:02:03.864 E/AndroidRuntime(7029): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2212)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2271)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.ActivityThread.access$800(ActivityThread.java:144)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1205)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.os.Handler.dispatchMessage(Handler.java:102)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.os.Looper.loop(Looper.java:136)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.ActivityThread.main(ActivityThread.java:5146)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at java.lang.reflect.Method.invokeNative(Native Method)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at java.lang.reflect.Method.invoke(Method.java:515)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at dalvik.system.NativeStart.main(Native Method)
12-21 02:02:03.864 E/AndroidRuntime(7029): Caused by: java.lang.NullPointerException
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at com.android.settings.net.NetworkPolicyEditor.read(NetworkPolicyEditor.java:70)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at com.android.settings.DataUsageSummary.onCreate(DataUsageSummary.java:287)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.Fragment.performCreate(Fragment.java:1678)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.BackStackRecord.run(BackStackRecord.java:684)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1447)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.Activity.performStart(Activity.java:5240)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2178)
12-21 02:02:03.864 E/AndroidRuntime(7029): 	... 12 more
12-21 02:02:03.864 W/ActivityManager(849):   Force finishing activity com.android.settings/.SubSettings
12-21 02:02:03.864 W/ActivityManager(849):   Force finishing activity com.android.settings/.Settings
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes