Battery drain!!! - Galaxy Note 3 Q&A, Help & Troubleshooting

Battery drain!!! - Galaxy Note 3 Q&A, Help & Troubleshooting

Here's my BBS log
I want to know what's draining my battery could anyone help me?
===================
General Information
===================
BetterBatteryStats version: 2.0.0.0
Creation Date: 2015-04-17 21:02:49
Statistic Type: Unplugged to Current
Since 11 h 32 m 22 s
VERSION.RELEASE: 5.0
BRAND: samsung
DEVICE: hlte
MANUFACTURER: samsung
MODEL: SM-N9005
OS.VERSION: 3.4.0-3643614
BOOTLOADER: N9005XXUGBNL8
HARDWARE: qcom
FINGERPRINT: samsung/hltexx/hlte:5.0/LRX21V/N9005XXUGBOB6:user/release-keys
ID: LRX21V
TAGS: release-keys
USER: dpi
PRODUCT: hltexx
RADIO: N9005XXUGBOA1
Rooted: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -20%(76% to 56%) [1.7%/h]
Voltage lost [mV]: (3985-3833) [13.2%/h]
===========
Other Usage
===========
Deep Sleep (): 9 h 49 m 27 s 85.1%
Awake (): 1 h 42 m 55 s 14.9%
Screen On (): 27 m 5 s 3.9%
Phone On (): 6 m 29 s 0.9%
No Data Connection (): 10 h 16 m 38 s 89.1%
No or Unknown Signal (): 10 h 16 m 38 s 89.1%
Moderate Signal (): 41 m 25 s 6.0%
Screen dark (): 9 m 9 s 1.3%
Screen dimmed (): 16 m 13 s 2.3%
Screen medium (): 12 s 0.0%
Screen light (): 2 s 0.0%
Screen bright (): 1 m 27 s 0.2%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
android.media.MediaPlayer (com.sec.android.app.music.Music): 12 m 38 s Count:4 1.8%
AudioOffloadThread (1013): 12 m 38 s Count:8 1.8%
[email protected]/B4Tb64lLpLSCksk5w/QSxQTciH9sVsR (com.tencent.mm.WeChat): 3 m 54 s Count:74 0.6%
ConnectivityService (Android System): 3 m 12 s Count:15 0.5%
ProximitySensorManager (Phone): 2 m 46 s Count:12 0.4%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 1 m 50 s Count:47 0.3%
*alarm* (Android System): 52 s Count:336 0.1%
AudioMix (1013): 48 s Count:58 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 25 s Count:40 0.1%
StartingAlertService (com.android.mms.Messages): 20 s Count:327 0.0%
TimedEventQueue (1013): 19 s Count:4 0.0%
GCM_CONN_ALARM (Google Play services): 18 s Count:69 0.0%
RILJ0 (Phone): 12 s Count:1269 0.0%
MusicSyncService (com.sec.android.app.music.Music): 11 s Count:6 0.0%
FbClientConnManager (com.facebook.katana.Facebook): 10 s Count:10 0.0%
*alarm* (com.tencent.mm.WeChat): 8 s Count:197 0.0%
com.samsung.musicplus.service.MultiPlayer (com.sec.android.app.music.Music): 8 s Count:11 0.0%
GsmConnection (Phone): 6 s Count:1328 0.0%
AudioOffload (1013): 4 s Count:453 0.0%
show keyguard (com.android.systemui.System UI): 4 s Count:20 0.0%
AudioMix (com.android.systemui.System UI): 4 s Count:40 0.0%
GsmInboundSmsHandler (Phone): 3 s Count:2 0.0%
*alarm* (Google Play services): 2 s Count:303 0.0%
Event Log Service (Google Play services): 2 s Count:93 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar Storage): 2 s Count:40 0.0%
*alarm* (com.sec.spp.push.Samsung Push Service): 1 s Count:64 0.0%
*alarm* (com.a0soft.gphone.aDataOnOff.2 Battery): 1 s Count:19 0.0%
ActivityManager-Sleep (Android System): 1 s Count:419 0.0%
handleAudioEvent (Android System): 1 s Count:19 0.0%
HyberSvc (com.oasisfeng.greenify.Greenify): 1 s Count:14 0.0%
wake:com.google.android.gms/.config.ConfigFetchService (Google Play services): 1 s Count:19 0.0%
handleMediaEvent (Android System): 1 s Count:58 0.0%
*alarm* (com.viber.voip.Viber): 1 s Count:35 0.0%
*alarm* (com.android.providers.calendar.Calendar Storage): 1 s Count:77 0.0%
GCM_CONN (Google Play services): 1 s Count:166 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!(uses API)
================
PowerManagerService.WakeLocks (*api*): 30 m Cntc/wc/ec)2940/0/0 4.3%
PowerManagerService.Display (*api*): 25 m 18 s Cntc/wc/ec)88/0/0 3.7%
bam_dmux_wakelock (*api*): 20 m 33 s Cntc/wc/ec)538/0/0 3.0%
ssp_sensorhub_wake_lock (*api*): 15 m 36 s Cntc/wc/ec)294/0/0 2.3%
radio-interface (*api*): 14 m 1 s Cntc/wc/ec)713/0/0 2.0%
event0-994 (*api*): 4 m 48 s Cntc/wc/ec)1229/0/0 0.7%
event1-994 (*api*): 4 m 47 s Cntc/wc/ec)1233/0/0 0.7%
event15-994 (*api*): 4 m 23 s Cntc/wc/ec)1350/0/0 0.6%
smdcntl0 (*api*): 2 m 54 s Cntc/wc/ec)4463/0/0 0.4%
ssp_wake_lock (*api*): 2 m 40 s Cntc/wc/ec)253/0/0 0.4%
DS (*api*): 2 m 10 s Cntc/wc/ec)43/0/0 0.3%
resume_wakelock (*api*): 1 m 56 s Cntc/wc/ec)1228/0/0 0.3%
alarm_rtc (*api*): 1 m 39 s Cntc/wc/ec)285/0/0 0.2%
alarm (*api*): 1 m 37 s Cntc/wc/ec)796/0/0 0.2%
PowerManagerService.Broadcasts (*api*): 1 m 10 s Cntc/wc/ec)81/0/0 0.2%
sec-battery-monitor (*api*): 37 s Cntc/wc/ec)1371/0/0 0.1%
sec_jack_det (*api*): 29 s Cntc/wc/ec)5/0/0 0.1%
sec-battery-vbus (*api*): 9 s Cntc/wc/ec)0/0/0 0.0%
ipc00000004_rmt_storage (*api*): 9 s Cntc/wc/ec)49/0/0 0.0%
ApmAudio (*api*): 8 s Cntc/wc/ec)296/0/0 0.0%
vib_present (*api*): 7 s Cntc/wc/ec)15/0/0 0.0%
KeyEvents (*api*): 7 s Cntc/wc/ec)19312/0/0 0.0%
qmuxd_port_wl_0 (*api*): 4 s Cntc/wc/ec)6128/0/0 0.0%
LightsService (*api*): 3 s Cntc/wc/ec)8/0/0 0.0%
event5-994 (*api*): 3 s Cntc/wc/ec)80/0/0 0.0%
rmt_storage_-1229455232 (*api*): 2 s Cntc/wc/ec)25/0/0 0.0%
event4-994 (*api*): 2 s Cntc/wc/ec)16167/0/0 0.0%
rmt_storage_-1229454592 (*api*): 2 s Cntc/wc/ec)24/0/0 0.0%
muic wake lock (*api*): 1 s Cntc/wc/ec)0/0/0 0.0%
SensorService (*api*): Cntc/wc/ec)71/0/0 0.0%
charger-chgin (*api*): Cntc/wc/ec)0/0/0 0.0%
smsm_snapshot (*api*): Cntc/wc/ec)828/0/0 0.0%
SMDTTY_READ_IN_SUSPEND (*api*): Cntc/wc/ec)5/0/0 0.0%
ApmOutput (*api*): Cntc/wc/ec)178/0/0 0.0%
qpnp-iadc-ead33600 (*api*): Cntc/wc/ec)16/0/0 0.0%
ipc00000021_Loc_hal_worker (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc0000001d_Loc_hal_worker (*api*): Cntc/wc/ec)49/0/0 0.0%
power-supply (*api*): Cntc/wc/ec)114/0/0 0.0%
gpio_input (*api*): Cntc/wc/ec)2/0/0 0.0%
event2-994 (*api*): Cntc/wc/ec)154/0/0 0.0%
ipc0000000e_time_daemon (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc0000000b_time_daemon (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc00000002_rfs_access (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc00000005_rmt_storage (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc00000011_thermal-engine (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc00000012_thermal-engine (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc_rtr_smd_ipcrtr (*api*): Cntc/wc/ec)188/0/0 0.0%
ipc00000016_thermal-engine (*api*): Cntc/wc/ec)49/0/0 0.0%
ipc0000000d_time_daemon (*api*): Cntc/wc/ec)77/0/0 0.0%
ipc00000003_kworker/2:1 (*api*): Cntc/wc/ec)191/0/0 0.0%
ipc_rtr_q6_ipcrtr (*api*): Cntc/wc/ec)215/0/0 0.0%
ipc00000018_thermal-engine (*api*): Cntc/wc/ec)49/0/0 0.0%
SMD_TTY_DS_RA (*api*): Cntc/wc/ec)44/0/0 0.0%
event17-994 (*api*): Cntc/wc/ec)1/0/0 0.0%
======================================================
Processes (requires root / system app on Android 4.4+)
======================================================
system (Android System): Uid: 1000 Sys: 9 m 35 s Us: 4 m 41 s Starts: 0
com.android.phone (Phone): Uid: 1001 Sys: 2 m 26 s Us: 1 m 15 s Starts: 0
com.facebook.katana (com.facebook.katana.Facebook): Uid: 10262 Sys: 45 s Us: 2 m 25 s Starts: 4
surfaceflinger (Android System): Uid: 1000 Sys: 1 m 21 s Us: 49 s Starts: 0
com.android.systemui (com.android.systemui.System UI): Uid: 10067 Sys: 45 s Us: 1 m 3 s Starts: 0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10271 Sys: 41 s Us: 36 s Starts: 1
*wakelock* (com.tencent.mm.WeChat): Uid: 10208 Sys: 34 s Us: 17 s Starts: 0
*wakelock* (1013): Uid: 1013 Sys: 27 s Us: 21 s Starts: 0
mpdecision (0): Uid: 0 Sys: 45 s Us: 2 s Starts: 0
servicemanager (Android System): Uid: 1000 Sys: 33 s Us: 14 s Starts: 0
com.android.chrome:sandboxed_process0 (com.android.chrome.Chrome): Uid: 10272 Sys: 6 s Us: 36 s Starts: 2
com.whatsapp (com.whatsapp.WhatsApp): Uid: 10207 Sys: 16 s Us: 19 s Starts: 1
com.android.chrome:sandboxed_process2 (com.android.chrome.Chrome): Uid: 10272 Sys: 5 s Us: 29 s Starts: 2
com.android.chrome (com.android.chrome.Chrome): Uid: 10272 Sys: 13 s Us: 18 s Starts: 3
com.tencent.mmush (com.tencent.mm.WeChat): Uid: 10208 Sys: 18 s Us: 10 s Starts: 0
*wakelock* (Phone): Uid: 1001 Sys: 17 s Us: 11 s Starts: 0
com.android.mms (com.android.mms.Messages): Uid: 10056 Sys: 15 s Us: 12 s Starts: 2
mediaserver (1013): Uid: 1013 Sys: 17 s Us: 10 s Starts: 0
com.android.contacts (Android Core Apps): Uid: 10026 Sys: 10 s Us: 15 s Starts: 2
kswapd0 (0): Uid: 0 Sys: 25 s Us: Starts: 0
*wakelock* (com.sec.android.app.music.Music): Uid: 10049 Sys: 14 s Us: 10 s Starts: 0
cfinteractive (0): Uid: 0 Sys: 20 s Us: 4 s Starts: 0
kworker/u:0H (0): Uid: 0 Sys: 23 s Us: Starts: 0
com.sec.android.app.launcher (TouchWiz Home): Uid: 10014 Sys: 11 s Us: 11 s Starts: 0
com.android.incallui (Phone): Uid: 1001 Sys: 9 s Us: 12 s Starts: 0
com.tencent.mm (com.tencent.mm.WeChat): Uid: 10208 Sys: 10 s Us: 10 s Starts: 1
*wakelock* (com.sec.android.app.clockpackage.Clock): Uid: 10099 Sys: 12 s Us: 6 s Starts: 0
mmcqd/1 (0): Uid: 0 Sys: 18 s Us: Starts: 0
com.google.android.gms (Google Play services): Uid: 10019 Sys: 12 s Us: 5 s Starts: 0
ksoftirqd/0 (0): Uid: 0 Sys: 17 s Us: Starts: 0
kworker/u:8 (0): Uid: 0 Sys: 15 s Us: Starts: 0
mdss_fb0 (0): Uid: 0 Sys: 15 s Us: Starts: 0
com.google.process.gapps (Google Play services): Uid: 10019 Sys: 10 s Us: 5 s Starts: 0
kworker/u:7 (0): Uid: 0 Sys: 15 s Us: Starts: 0
*wakelock* (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10271 Sys: 8 s Us: 6 s Starts: 0
com.touchtype.swiftkey (com.touchtype.swiftkey.SwiftKey Keyboard): Uid: 10216 Sys: 6 s Us: 8 s Starts: 0
kworker/u:6 (0): Uid: 0 Sys: 14 s Us: Starts: 0
kworker/u:4 (0): Uid: 0 Sys: 14 s Us: Starts: 0
rild (0): Uid: 0 Sys: 10 s Us: 4 s Starts: 0
com.android.chromerivileged_process0 (com.android.chrome.Chrome): Uid: 10272 Sys: 6 s Us: 7 s Starts: 2
com.sec.android.widgetapp.ap.hero.accuweather (com.sec.android.widgetapp.ap.hero.accuweather.Weather): Uid: 10081 Sys: 4 s Us: 9 s Starts: 0
kworker/u:1 (0): Uid: 0 Sys: 13 s Us: Starts: 0
kworker/u:9 (0): Uid: 0 Sys: 13 s Us: Starts: 0
kworker/0:1H (0): Uid: 0 Sys: 13 s Us: Starts: 0
kworker/u:3 (0): Uid: 0 Sys: 13 s Us: Starts: 0
kworker/u:5 (0): Uid: 0 Sys: 12 s Us: Starts: 0
com.a0soft.gphone.aDataOnOff (com.a0soft.gphone.aDataOnOff.2 Battery): Uid: 10275 Sys: 10 s Us: 2 s Starts: 1
kworker/u:2 (0): Uid: 0 Sys: 12 s Us: Starts: 0
kworker/u:11 (0): Uid: 0 Sys: 12 s Us: Starts: 0
irq/626-synapti (0): Uid: 0 Sys: 11 s Us: Starts: 0
com.google.process.location (Google Play services): Uid: 10019 Sys: 8 s Us: 3 s Starts: 0
com.google.android.googlequicksearchbox:search (com.google.android.googlequicksearchbox.Google App): Uid: 10070 Sys: 6 s Us: 5 s Starts: 2
com.viber.voip (com.viber.voip.Viber): Uid: 10209 Sys: 9 s Us: 2 s Starts: 0
android.process.media (Media): Uid: 10053 Sys: 6 s Us: 5 s Starts: 0
android.process.acore (Android Core Apps): Uid: 10026 Sys: 6 s Us: 4 s Starts: 0
lmkd (0): Uid: 0 Sys: 9 s Us: Starts: 0
kworker/u:10 (0): Uid: 0 Sys: 10 s Us: Starts: 0
com.sec.spp.push (com.sec.spp.push.Samsung Push Service): Uid: 10045 Sys: 5 s Us: 4 s Starts: 0
com.estoty.game2048 (com.estoty.game2048.2048 Puzzle): Uid: 10264 Sys: 1 s Us: 8 s Starts: 1
kworker/0:1 (0): Uid: 0 Sys: 9 s Us: Starts: 0
daemonsu:10271 (0): Uid: 0 Sys: 8 s Us: Starts: 0
com.oasisfeng.greenify:service (com.oasisfeng.greenify.Greenify): Uid: 10245 Sys: 5 s Us: 3 s Starts: 0
spi11 (0): Uid: 0 Sys: 8 s Us: Starts: 0
com.instagram.android (com.instagram.android.Instagram): Uid: 10252 Sys: 1 s Us: 6 s Starts: 1
su (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10271 Sys: 7 s Us: Starts: 0
com.sec.android.daemonapp (com.sec.android.daemonapp.Unified Daemon): Uid: 10190 Sys: 4 s Us: 3 s Starts: 0
zygote (0): Uid: 0 Sys: 7 s Us: Starts: 0
kthreadd (0): Uid: 0 Sys: 7 s Us: Starts: 0
com.android.vending (com.android.vending.Google Play Store): Uid: 10035 Sys: 5 s Us: 2 s Starts: 1
*wakelock* (com.sec.spp.push.Samsung Push Service): Uid: 10045 Sys: 5 s Us: Starts: 0
*wakelock* (com.android.systemui.System UI): Uid: 10067 Sys

Related

[TOOL] Nbench for Android

Hi!
Just released Nbench 1.1. Android NBench is a native port of BYTE's BYTEmark CPU benchmark.
The benchmark was designed to expose the capabilities of a system's CPU, FPU, memory and C compiler performance. Supports Arm v5, Arm v7, x86 and Mips32 CPUs. Only a SINGLE core is benchmarked.
What's interesting about nbench is that the results can be published and seen on http://www.tux.org/~mayer/ and lets you compare your Android phone with desktop computers or high-end servers (Nbench even worked on i386 processors!).
It's also interesting to test for ndk performance regressions, for example, I found gcc 4.6.0 was much slower than gcc 4.4.3 with -O2 optimisation.
The latest version was compiled with ndk 8e, gcc 4.6.0 and -O3 optimisation.
It's open source, the code can be browsed here: http://sourceforge.net/p/drolez/nbench/ci/master/tree/
You can also download it on the market: https://play.google.com/store/apps/details?id=com.drolez.nbench
[QRCODE]market://details?id=com.drolez.nbench[/QRCODE]
Enjoy!

Below the results for my Wiko Cink Peax.
BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)
TEST : Iterations/sec. : Old Index : New Index
: : Pentium 90* : AMD K6/233*
--------------------:------------------:-------------:------------
NUMERIC SORT : 559.82 : 14.36 : 4.72
STRING SORT : 32.621 : 14.58 : 2.26
BITFIELD : 1.802e+08 : 30.91 : 6.46
FP EMULATION : 67.74 : 32.50 : 7.50
FOURIER : 7886.2 : 8.97 : 5.04
ASSIGNMENT : 7.3016 : 27.78 : 7.21
IDEA : 1549.9 : 23.70 : 7.04
HUFFMAN : 849.9 : 23.57 : 7.53
NEURAL NET : 8.7529 : 14.06 : 5.91
LU DECOMPOSITION : 322.29 : 16.70 : 12.06
==========================ORIGINAL BYTEMARK RESULTS==========================
INTEGER INDEX : 22.861
FLOATING-POINT INDEX: 12.817
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==============================LINUX DATA BELOW===============================
CPU : Dual ARMv7 Processor rev 0 (v7l) 1001MHz
L2 Cache : 0
OS : Linux version 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Fri Jan 11 14:47:11 CST 2013
C compiler : gcc 4.6.0 (-march=armv7-a)
libc : Android Bionic libc
MEMORY INDEX : 4.717
INTEGER INDEX : 6.579
FLOATING-POINT INDEX: 7.109
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
* Trademarks are property of their respective holder.

More nbench results here: http://forum.xda-developers.com/showthread.php?t=1270596

Using nbench v1.1 -
Nexus 7:
BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)
TEST : Iterations/sec. : Old Index : New Index
: : Pentium 90* : AMD K6/233*
--------------------:------------------:-------------:------------
NUMERIC SORT : 649.43 : 16.65 : 5.47
STRING SORT : 30.14 : 13.47 : 2.08
BITFIELD : 2.1665e+08 : 37.16 : 7.76
FP EMULATION : 80.456 : 38.61 : 8.91
FOURIER : 9063.5 : 10.31 : 5.79
ASSIGNMENT : 8.4955 : 32.33 : 8.38
IDEA : 1859.4 : 28.44 : 8.44
HUFFMAN : 1012.7 : 28.08 : 8.97
NEURAL NET : 10.479 : 16.83 : 7.08
LU DECOMPOSITION : 344.88 : 17.87 : 12.90
==========================ORIGINAL BYTEMARK RESULTS==========================
INTEGER INDEX : 26.126
FLOATING-POINT INDEX: 14.581
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==============================LINUX DATA BELOW===============================
CPU : 4 CPU ARMv7 Processor rev 9 (v7l) 1300MHz
L2 Cache : 0
OS : Linux version 3.1.10-g009b6d1 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Sep 26 12:53:01 PDT 2012
C compiler : gcc 4.6.0 (-march=armv7-a)
libc : Android Bionic libc
MEMORY INDEX : 5.138
INTEGER INDEX : 7.794
FLOATING-POINT INDEX: 8.087
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
* Trademarks are property of their respective holder.
Sent from my Nexus 7 using Tapatalk 4 Beta

Hi!
Here are the numbers for my RK3188 quad-core Android HDMI key (a CX 919 on geekbuying). Not bad at all!
Cheers,
Ludo
==========================ORIGINAL BYTEMARK RESULTS==========================
INTEGER INDEX****** : 33.551
FLOATING-POINT INDEX: 19.353
Baseline (MSDOS*)** : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==============================LINUX DATA BELOW===============================
CPU**************** : 4 CPU ARMv7 Processor rev 0 (v7l) 1608MHz
L2 Cache*********** : 0
OS***************** : Linux version 3.0.36+ ([email protected]) (gcc version 4.8.2 20130624 (prerelease) (Linaro GCC 4.8-2013.07-1) ) #438 SMP PREEMPT Wed Sep 4 12:08:53 BST 2013
C compiler********* : gcc 4.6.0 (-march=armv7-a)
MEMORY INDEX******* : 6.239
INTEGER INDEX****** : 10.439
FLOATING-POINT INDEX: 10.734
Baseline (LINUX)*** : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38

RCA 7 Voyager RCT6773W22, quad core:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Samsung Galaxy S4 using Tapatalk

It seems that nbench does not work under lollipop... Can somebody give me more details?

Hi!
I finally took the time to make the benchmark work for lollipop users.
Can someone test the latest Google play nbench release?
TIA.

..where is NORMAL link to the apk. no google store user here.
Is it too hard for posting ATTACHEMENT xda link?
The latest version was compiled with ndk 8e, gcc 4.6.0 and -o3 optimisation.
Click to expand...
Click to collapse
I wonder, how compiler used may have difference on..test..hmmmm. I mean - someone has kernel/rom made with -o3, others have -o2, then how -o3 for bench can have impact on -o2 based roms/kernels..hhheh...confusing, isn't it?
Benchmarking matter is difficult, i suppose....

xo.en said:
I wonder, how compiler used may have difference on..test..hmmmm. I mean - someone has kernel/rom made with -03, others have -02, then how -03 for bench can have impact on -2 based roms/kernels..hhheh...
Click to expand...
Click to collapse
That's because nbench is a native benchmark: it's compiled with a C compiler and it's not a java program.
Moreover Rom optimisation has no influence on nbench because it's a CPU benchmark.

ldrolez said:
That's because nbench is a native benchmark: it's compiled with a C compiler and it's not a java program.
Moreover Rom optimisation has no influence on nbench because it's a CPU benchmark.
Click to expand...
Click to collapse
..allright, so give me..a link..

Any plans to port the nbench app to Windows Phone?

Or iOS?
Sent from my SM-G930T using Tapatalk

Hi !
I'll try to update nbench since it does not seem to work on 8.x devices. :/
LD

Bricked my lg d802 i think please help

i think ive bricked it!
i cant boot at all
LG G2D802
was running CM11 snapshot, i flashed a kernal and when twrp said....reboot nothing
no LEDS on, the screen seems to have some light but nothing, ive tried booting to recovery via power button and volume but it wont
wen i plug it in windows shows multiple external drives that need formatting!?
please help!

please can someone help!?

Valiceemo said:
i think ive bricked it!
i cant boot at all
LG G2D802
was running CM11 snapshot, i flashed a kernal and when twrp said....reboot nothing
no LEDS on, the screen seems to have some light but nothing, ive tried booting to recovery via power button and volume but it wont
wen i plug it in windows shows multiple external drives that need formatting!?
please help!
Click to expand...
Click to collapse
Got it, don't worry bro.
http://forum.xda-developers.com/showthread.php?t=2582142
Just follow this instruction. Had the same problem, solved it just fine.

Schindler069 said:
Got it, don't worry bro.
http://forum.xda-developers.com/showthread.php?t=2582142
Just follow this instruction. Had the same problem, solved it just fine.
Click to expand...
Click to collapse
ive seen this but im very unfamiliar with ubuntu...i dint even know how to install it on my laptop so it will run along side Windows 8?
Did you have exactly the same as me?
Cannot boot to anything at all?
Cant boot to recovery
Cant boot to fastboot
Cant boot to download
And the screen dimly lit but nothing happening?

Valiceemo said:
ive seen this but im very unfamiliar with ubuntu...i dint even know how to install it on my laptop so it will run along side Windows 8?
Did you have exactly the same as me?
Cannot boot to anything at all?
Cant boot to recovery
Cant boot to fastboot
Cant boot to download
And the screen dimly lit but nothing happening?
Click to expand...
Click to collapse
http://www.ubuntu.com/download/desktop/try-ubuntu-before-you-install
Ubuntu is very easy similiar to windows

[QRCODE][/QRCODE]
Valiceemo said:
ive seen this but im very unfamiliar with ubuntu...i dint even know how to install it on my laptop so it will run along side Windows 8?
Did you have exactly the same as me?
Cannot boot to anything at all?
Cant boot to recovery
Cant boot to fastboot
Cant boot to download
And the screen dimly lit but nothing happening?
Click to expand...
Click to collapse
So u get nothing when holding volume down and connecting USB cable with device turned off?
I'm not used to win 8, only used it briefly at work but maybe u can "boot" ubuntu with a USB stick?
I used lg PC suite to restore failed update (attempts to flash 4.4)
Worth a try at least.

Valiceemo said:
ive seen this but im very unfamiliar with ubuntu...i dint even know how to install it on my laptop so it will run along side Windows 8?
Did you have exactly the same as me?
Cannot boot to anything at all?
Cant boot to recovery
Cant boot to fastboot
Cant boot to download
And the screen dimly lit but nothing happening?
Click to expand...
Click to collapse
Yup, i had exactly your problem. This is the way to fix it, i got it in xda irc.
And yes, just set up ubuntu with a virtual machine and it will run like any programm. and make sure to disable auto mount usb in ubuntu for it to work, otherwise it will just open the partitions as it does on windows.

Schindler069 said:
Yup, i had exactly your problem. This is the way to fix it, i got it in xda irc.
And yes, just set up ubuntu with a virtual machine and it will run like any programm. and make sure to disable auto mount usb in ubuntu for it to work, otherwise it will just open the partitions as it does on windows.
Click to expand...
Click to collapse
Thanks @Schindler069
Ill try this when i get home, fingers crossed!:fingers-crossed:
What do you mean you got it in xda IRC?
(sorry for noob questions!)

Valiceemo said:
Thanks @Schindler069
Ill try this when i get home, fingers crossed!:fingers-crossed:
What do you mean you got it in xda IRC?
(sorry for noob questions!)
Click to expand...
Click to collapse
your welcome
xda has their own irc channel, it's a chat platform besides the usual forum.

ok, new development.
Thought id plug my G2 into worek laptop before heading home.,
as ususal a load of drives appear in windows explorer, as in the screen shot
When i look into that drive E: tghere is one folder, image.
Inside this folder are the following:
Directory of E:\image
07/07/11 14:07 <DIR> .
07/07/11 14:07 <DIR> ..
20/01/14 22:28 12,321,200 modem.b17
20/01/14 22:28 80 tqs.b03
20/01/14 22:28 35,556 tqs.b02
20/01/14 22:28 6,568 tqs.b01
20/01/14 22:28 180 tqs.b00
20/01/14 22:28 334,928 adsp.b10
20/01/14 22:28 180 playread.b00
20/01/14 22:28 776 adsp.b06
20/01/14 22:28 120,364 playread.b02
20/01/14 22:28 2,055,480 adsp.b04
20/01/14 22:28 799,548 adsp.b05
20/01/14 22:28 1 adsp.b02
20/01/14 22:28 5,043,888 adsp.b03
20/01/14 22:28 500 adsp.b00
20/01/14 22:28 608 playread.b03
20/01/14 22:28 107,712 dxhdcp2.b02
20/01/14 22:28 308 dxhdcp2.b03
20/01/14 22:28 180 dxhdcp2.b00
20/01/14 22:28 6,568 dxhdcp2.b01
20/01/14 22:28 6,748 playread.mdt
20/01/14 22:28 120 adsp.b08
20/01/14 22:28 276 adsp.b09
20/01/14 22:28 6,568 playread.b01
20/01/14 22:28 657,312 modem.b18
20/01/14 22:28 73,728 modem.b19
20/01/14 22:28 23,156 isdbtmm.b02
20/01/14 22:28 92,760 modem.b14
20/01/14 22:28 1,213,768 modem.b15
20/01/14 22:28 1,056,468 modem.b16
20/01/14 22:28 12 wcnss.b08
20/01/14 22:28 7,384 adsp.b12
20/01/14 22:28 54,528 modem.b11
20/01/14 22:28 105,176 modem.b13
20/01/14 22:28 7,068 wcnss.mdt
20/01/14 22:28 7,388 adsp.mdt
20/01/14 22:28 6,568 cmnlib.b01
20/01/14 22:28 180 cmnlib.b00
20/01/14 22:28 72 cmnlib.b03
20/01/14 22:28 94,568 cmnlib.b02
20/01/14 22:28 6,568 widevine.b01
20/01/14 22:28 180 widevine.b00
20/01/14 22:28 6,748 cmnlib.mdt
20/01/14 22:28 125,556 widevine.b02
20/01/14 22:28 6,748 mlserver.mdt
20/01/14 22:28 180 mlserver.b00
20/01/14 22:28 6,568 mlserver.b01
20/01/14 22:28 26,524 mlserver.b02
20/01/14 22:28 592 mlserver.b03
20/01/14 22:28 2,558,544 wcnss.b07
20/01/14 22:28 28,976 wcnss.b06
20/01/14 22:28 39,936 wcnss.b04
20/01/14 22:28 126,976 mc_v2.b02
20/01/14 22:28 12 mc_v2.b03
20/01/14 22:28 6,728 wcnss.b01
20/01/14 22:28 340 wcnss.b00
20/01/14 22:28 8,284 modem.mdt
20/01/14 22:28 104 isdbtmm.b03
20/01/14 22:28 180 mc_v2.b00
20/01/14 22:28 6,568 isdbtmm.b01
20/01/14 22:28 180 isdbtmm.b00
20/01/14 22:28 6,748 tqs.mdt
20/01/14 22:28 168 mc_v2.b01
20/01/14 22:28 7,620,520 modem.b21
20/01/14 22:28 5,376 modem.b20
20/01/14 22:28 3,909,264 modem.b22
20/01/14 22:28 179,504 modem.b25
20/01/14 22:28 6,748 dxhdcp2.mdt
20/01/14 22:28 10,084 wcnss.b02
20/01/14 22:28 179,165 modem.b08
20/01/14 22:28 81,920 modem.b05
20/01/14 22:28 7,432,976 modem.b04
20/01/14 22:28 6,374,376 modem.b03
20/01/14 22:28 90,868 modem.b02
20/01/14 22:28 7,336 modem.b01
20/01/14 22:28 948 modem.b00
20/01/14 22:28 6,748 widevine.mdt
20/01/14 22:28 6,888 adsp.b01
20/01/14 22:28 720 widevine.b03
20/01/14 22:28 348 mc_v2.mdt
20/01/14 22:28 6,748 isdbtmm.mdt
20/01/14 22:28 88,372 adsp.b11
20/01/14 22:28 201,792 modem.b26
20/01/14 22:28 84 mba.mdt
20/01/14 22:28 236,400 mba.b00
84 File(s) 53,659,066 bytes
2 Dir(s) 12,451,840 bytes free
Does this help with diagnosing?

Can you get into download mode if so you can use lg flash tool so what you need to do if download a copy of the right kdz for your phone and use that program to flash it to your phone on download mode it worked for me when this happen hope it works for you and you can do this on windows too

Valiceemo said:
ok, new development.
Thought id plug my G2 into worek laptop before heading home.,
as ususal a load of drives appear in windows explorer, as in the screen shot
When i look into that drive E: tghere is one folder, image.
Inside this folder are the following:
Directory of E:\image
07/07/11 14:07 <DIR> .
07/07/11 14:07 <DIR> ..
20/01/14 22:28 12,321,200 modem.b17
20/01/14 22:28 80 tqs.b03
20/01/14 22:28 35,556 tqs.b02
20/01/14 22:28 6,568 tqs.b01
20/01/14 22:28 180 tqs.b00
20/01/14 22:28 334,928 adsp.b10
20/01/14 22:28 180 playread.b00
20/01/14 22:28 776 adsp.b06
20/01/14 22:28 120,364 playread.b02
20/01/14 22:28 2,055,480 adsp.b04
20/01/14 22:28 799,548 adsp.b05
20/01/14 22:28 1 adsp.b02
20/01/14 22:28 5,043,888 adsp.b03
20/01/14 22:28 500 adsp.b00
20/01/14 22:28 608 playread.b03
20/01/14 22:28 107,712 dxhdcp2.b02
20/01/14 22:28 308 dxhdcp2.b03
20/01/14 22:28 180 dxhdcp2.b00
20/01/14 22:28 6,568 dxhdcp2.b01
20/01/14 22:28 6,748 playread.mdt
20/01/14 22:28 120 adsp.b08
20/01/14 22:28 276 adsp.b09
20/01/14 22:28 6,568 playread.b01
20/01/14 22:28 657,312 modem.b18
20/01/14 22:28 73,728 modem.b19
20/01/14 22:28 23,156 isdbtmm.b02
20/01/14 22:28 92,760 modem.b14
20/01/14 22:28 1,213,768 modem.b15
20/01/14 22:28 1,056,468 modem.b16
20/01/14 22:28 12 wcnss.b08
20/01/14 22:28 7,384 adsp.b12
20/01/14 22:28 54,528 modem.b11
20/01/14 22:28 105,176 modem.b13
20/01/14 22:28 7,068 wcnss.mdt
20/01/14 22:28 7,388 adsp.mdt
20/01/14 22:28 6,568 cmnlib.b01
20/01/14 22:28 180 cmnlib.b00
20/01/14 22:28 72 cmnlib.b03
20/01/14 22:28 94,568 cmnlib.b02
20/01/14 22:28 6,568 widevine.b01
20/01/14 22:28 180 widevine.b00
20/01/14 22:28 6,748 cmnlib.mdt
20/01/14 22:28 125,556 widevine.b02
20/01/14 22:28 6,748 mlserver.mdt
20/01/14 22:28 180 mlserver.b00
20/01/14 22:28 6,568 mlserver.b01
20/01/14 22:28 26,524 mlserver.b02
20/01/14 22:28 592 mlserver.b03
20/01/14 22:28 2,558,544 wcnss.b07
20/01/14 22:28 28,976 wcnss.b06
20/01/14 22:28 39,936 wcnss.b04
20/01/14 22:28 126,976 mc_v2.b02
20/01/14 22:28 12 mc_v2.b03
20/01/14 22:28 6,728 wcnss.b01
20/01/14 22:28 340 wcnss.b00
20/01/14 22:28 8,284 modem.mdt
20/01/14 22:28 104 isdbtmm.b03
20/01/14 22:28 180 mc_v2.b00
20/01/14 22:28 6,568 isdbtmm.b01
20/01/14 22:28 180 isdbtmm.b00
20/01/14 22:28 6,748 tqs.mdt
20/01/14 22:28 168 mc_v2.b01
20/01/14 22:28 7,620,520 modem.b21
20/01/14 22:28 5,376 modem.b20
20/01/14 22:28 3,909,264 modem.b22
20/01/14 22:28 179,504 modem.b25
20/01/14 22:28 6,748 dxhdcp2.mdt
20/01/14 22:28 10,084 wcnss.b02
20/01/14 22:28 179,165 modem.b08
20/01/14 22:28 81,920 modem.b05
20/01/14 22:28 7,432,976 modem.b04
20/01/14 22:28 6,374,376 modem.b03
20/01/14 22:28 90,868 modem.b02
20/01/14 22:28 7,336 modem.b01
20/01/14 22:28 948 modem.b00
20/01/14 22:28 6,748 widevine.mdt
20/01/14 22:28 6,888 adsp.b01
20/01/14 22:28 720 widevine.b03
20/01/14 22:28 348 mc_v2.mdt
20/01/14 22:28 6,748 isdbtmm.mdt
20/01/14 22:28 88,372 adsp.b11
20/01/14 22:28 201,792 modem.b26
20/01/14 22:28 84 mba.mdt
20/01/14 22:28 236,400 mba.b00
84 File(s) 53,659,066 bytes
2 Dir(s) 12,451,840 bytes free
Does this help with diagnosing?
Click to expand...
Click to collapse
No, just follow the instructions
But DO NOT partition any of those, otherwise you risk an unrepairable brick!

Reecegibbs said:
Can you get into download mode if so you can use lg flash tool so what you need to do if download a copy of the right kdz for your phone and use that program to flash it to your phone on download mode it worked for me when this happen hope it works for you and you can do this on windows too
Click to expand...
Click to collapse
No i cant get into download mode at all, i can get nothing!
just a dim lit screen
Schindler069 said:
No, just follow the instructions
But DO NOT partition any of those, otherwise you risk an unrepairable brick!
Click to expand...
Click to collapse
I followed the guide, using ubuntu in Virtual Box and im stuck at the first step!!
i type ls /dev/sd*
and it returns only
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
Any ideas?
Ive selected my LG from the USB devices in Virtual Box??!
:crying:

Valiceemo said:
I followed the guide, using ubuntu in Virtual Box and im stuck at the first step!!
i type ls /dev/sd*
and it returns only
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
Any ideas?
Ive selected my LG from the USB devices in Virtual Box??!
:crying:
Click to expand...
Click to collapse
Does Ubuntu also open the different partitions like windows?
Have you unplugged all other usb devices?
Otherwise he says
Partager.info said:
Now just boot into ubuntu and plug your LG G2 to the computer.
Put the downloaded files in the desktop or wherever you want. You just need to know the path to your files.
unplug any other usb device except your mouse, keyboard and lg g2.
Open terminal in ubuntu then type:
Code:
ls /dev/sd*
It should return something like this:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
Click to expand...
Click to collapse
In this case your device is detected under sdb. you may have it under sdc. just look for the biggest number, in this case /dev/sdb36 so it is sdb.
Click to expand...
Click to collapse
So then your biggest number would be 5. I cant remember, what my number was.

Im gonna work it out today i will try and put my over lg g2 in your state and fix it and i will upload all the steps needed but if you have good luck with any over solutions let me know

Reecegibbs said:
Im gonna work it out today i will try and put my over lg g2 in your state and fix it and i will upload all the steps needed but if you have good luck with any over solutions let me know
Click to expand...
Click to collapse
that would be awsome if you could do that!
Thanks very much, please keep the thread updated, as i see there are a few people who have the same problem

Schindler069 said:
Does Ubuntu also open the different partitions like windows?
Have you unplugged all other usb devices?
So then your biggest number would be 5. I cant remember, what my number was.
Click to expand...
Click to collapse
yeah, all other devices unplugged, it doesnt look like ubuntu opens the various partitions no, im going to try again tonight and see what i get. i was soooo tired last night!
Hopefully the guy above can help aswell

how can I get into download mode the buttons aren't working
Sent from my MB855 using xda app-developers app

Ok sorry for the late reply but i just came home from.college can you try and get into recovery mode press vol down and power until lg logo sows release and press and hold both buttons again can you tell me what is shown if it does show anything at all i am starting work on your problem.now this would help me understand more of the state of your phone thanks
---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------
Also btw there was a guide mensioned in this thread i have seen it before and i have had problems when using a virtual machien infack i clean install ubuntu on a old laptop and had sucsess with it dont know why but if you have an old pc laptop hanging around clean instal ubuntu on it that fix guide may now work that way if you dont have anything lying around dont wroory im onto a work around for you

Reecegibbs said:
Ok sorry for the late reply but i just came home from.college can you try and get into recovery mode press vol down and power until lg logo sows release and press and hold both buttons again can you tell me what is shown if it does show anything at all i am starting work on your problem.now this would help me understand more of the state of your phone thanks
---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------
Also btw there was a guide mensioned in this thread i have seen it before and i have had problems when using a virtual machien infack i clean install ubuntu on a old laptop and had sucsess with it dont know why but if you have an old pc laptop hanging around clean instal ubuntu on it that fix guide may now work that way if you dont have anything lying around dont wroory im onto a work around for you
Click to expand...
Click to collapse
thanks for trying to help
i cant get into recovery at all
its just a dimly lit screen.

{SOLVED} Note-4 DevEd LP Screen brightness bug

Update: We now have a patched Kernel! The brightness bug is cured
Thanks to all those that helped! Go to this thread and flash the kernel
We should be able to find a work around for the Developer Edition Screen locked to max after LP update. Lets share information, and logs so we can patch the bug. Lets gitRdone
I have some logs.
Recovery Log shows locations of brightness settings:
Code:
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_HAS_DOWNLOAD_MODE := true
I:TW_BRIGHTNESS_PATH := /sys/devices/fd900000.qcom,mdss_mdp/qcom,mdss_fb_primary.163/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/devices/fd900000.qcom,mdss_mdp/qcom,mdss_fb_primary.163/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Some monitor logs while turning brightness up, down, and auto on/off
Code:
04-11 22:05:56.465: D/DisplayPowerController(1184): getFinalBrightness : Summary is 78 -> 78
04-11 22:05:56.465: D/DisplayPowerController(1184): animation target = 78, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:56.465: D/lights(1184): lcd : 10 +
04-11 22:05:56.465: D/lights(1184): lcd : 10 -
04-11 22:05:56.485: D/lights(1184): lcd : 44 +
04-11 22:05:56.485: D/lights(1184): lcd : 44 -
04-11 22:05:56.505: D/DisplayPowerController(1184): getFinalBrightness : Summary is 78 -> 78
04-11 22:05:56.505: D/lights(1184): lcd : 78 +
04-11 22:05:56.505: D/DisplayPowerController(1184): animation target = 78, rate=500 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:56.505: D/lights(1184): lcd : 78 -
04-11 22:05:56.505: D/DisplayPowerController(1184): getFinalBrightness : Summary is 78 -> 78
04-11 22:05:56.505: D/DisplayPowerController(1184): animation target = 78, rate=500 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:56.635: E/Sensors(1184): RED : 270, GREEN : 203, BLUE : 193, CLEAR : 581,Lux = 90.000000, CCT = 3691.000000, RawLux = 90.000000
04-11 22:05:56.815: E/Sensors(1184): RED : 270, GREEN : 203, BLUE : 196, CLEAR : 584,Lux = 89.000000, CCT = 3729.000000, RawLux = 89.000000
04-11 22:05:56.885: D/InputReader(1184): Input event: value=1
04-11 22:05:56.885: D/InputReader(1184): Input event: value=1
04-11 22:05:56.885: I/InputReader(1184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, s=0.726 ] when=10679301538000
04-11 22:05:56.885: I/InputDispatcher(1184): Delivering touch to (1376): action: 0x0, toolType: 1
04-11 22:05:56.885: D/PowerManagerService(1184): [input device light] setInputDeviceLightOn is called : 1
04-11 22:05:56.885: D/ViewRootImpl(1376): ViewPostImeInputStage ACTION_DOWN
04-11 22:05:56.885: D/PowerManagerService(1184): [input device light] handleInputDeviceLightOn
04-11 22:05:56.895: D/PanelView(1376): mDispatchInitX=250.0, mDispatchInitY=610.0
04-11 22:05:56.895: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:56.895: D/PanelView(1376): !handled - true
04-11 22:05:56.895: D/PanelView(1376): findNotificationView(mDispatchInitX, mDispatchInitY) == null - true
04-11 22:05:56.895: D/PanelView(1376): shouldPanelIntercept(mDispatchInitX, mDispatchInitY) - true
04-11 22:05:56.895: D/PanelView(1376): UnlockMethodCache.getInstance(mContext).isMethodInsecure() - true
04-11 22:05:56.895: D/PanelView(1376): !mQsTracking - true
04-11 22:05:56.895: D/PanelView(1376): !getClearAllview(mDispatchInitX, mDispatchInitY) - true
04-11 22:05:56.905: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:56.905: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:56.925: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:56.925: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:56.945: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:56.945: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:56.955: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:56.955: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:56.965: D/SettingsProvider(1184): name = screen_brightness_mode
04-11 22:05:56.965: D/SettingsProvider(1184): edmUri: content://com.sec.knox.provider/RestrictionPolicy3
04-11 22:05:56.965: D/SettingsProvider(1184): projectionArgs: isSettingsChangesAllowed
04-11 22:05:56.965: D/SettingsProvider(1184): selectionArgs: false
04-11 22:05:56.965: D/SettingsProvider(1184): selectionArgs: 10064
04-11 22:05:56.965: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:56.965: D/SettingsProvider(1184): ret = -1
04-11 22:05:56.965: W/BackupManagerService(1184): dataChanged but no participant pkg='com.android.providers.settings' uid=10064
04-11 22:05:56.975: D/PowerManagerService(1184): [api] SettingsObserver: onChange: content://settings/system/screen_brightness_mode
04-11 22:05:56.975: D/PowerManagerService(1184): [PSM] lowPowerModeEnabled: false mLowPowerModeSetting: false, autoLowPowerModeConfigured: false mAutoLowPowerModeConfigured: false, lowBatteryTriggerLevel: 0 mLowBatteryTriggerLevel: 0
04-11 22:05:56.975: D/PowerManagerService(1184): [api] updateSettingsLocked : mDreamsEnabledSetting: false mDreamsActivateOnSleepSetting: false mDreamsActivateOnDockSetting: true mScreenOffTimeoutSetting: 300000 mStayOnWhilePluggedInSetting: 0 mScreenBrightnessSetting: 2 mScreenAutoBrightnessAdjustmentSetting: 0.0 mScreenBrightnessModeSetting: 0 mSmartStayEnabledSetting: false mTouchKeyOffTimeoutSetting: 1500 mKeyboardOffTimeoutSetting: 2000 mPowerSaveModeSettingBroadcasted false mLimitedPerformanceBroadcasted true useSystemPowerSaveMode false mTouchKeyForceDisableOverrideFromSystemPowerSaveMode: false mATTautoPowerSavingModeSetting: false mATTautoPowerSavingModeSuspend: false mEmergencyMode false
04-11 22:05:56.975: D/AutomaticBrightnessController(1184): [DAB] setLightSensorEnabled : Send Update unregisterListener mLightSensor
04-11 22:05:56.975: I/AutomaticBrightnessController(1184): [DAB] fileWriteInt : /sys/class/tcon/tcon/auto_br value : 0
04-11 22:05:56.975: I/AutomaticBrightnessController(1184): [DAB] fileWriteInt : /sys/class/backlight/panel/auto_brightness value : 0
04-11 22:05:56.975: I/AutomaticBrightnessController(1184): [DAB] fileWriteInt : /sys/class/mdnie/mdnie/auto_brightness value : 0
04-11 22:05:56.975: D/AutomaticBrightnessController(1184): [DAB] no lux value from sensor manager
04-11 22:05:56.975: D/AutomaticBrightnessController(1184): [DAB] setLightSensorEnabled : unregisterListener mLightSensor
04-11 22:05:56.975: I/Sensors(1184): Light old sensor_state 513, new sensor_state : 1 en : 0
04-11 22:05:56.975: D/DisplayPowerController(1184): getFinalBrightness : Summary is 2 -> 2
04-11 22:05:56.975: D/DisplayPowerController(1184): animation target = 2, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:56.975: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:56.975: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 2 (uid: 10064 pid: 1376)
04-11 22:05:56.975: D/AnimatedBrightnessIconView(1376): setValue : 0
04-11 22:05:56.975: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:56.975: D/AnimatedBrightnessIconView(1376): setValue : 0
04-11 22:05:56.975: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:56.985: D/SensorManager(1184): unregisterListener ::
04-11 22:05:56.985: D/SettingsProvider(1184): name = screen_brightness_mode
04-11 22:05:56.985: D/SettingsProvider(1184): edmUri: content://com.sec.knox.provider/RestrictionPolicy3
04-11 22:05:56.985: D/SettingsProvider(1184): projectionArgs: isSettingsChangesAllowed
04-11 22:05:56.985: D/SettingsProvider(1184): selectionArgs: false
04-11 22:05:56.985: D/SettingsProvider(1184): selectionArgs: 10064
04-11 22:05:56.985: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:56.985: D/SettingsProvider(1184): ret = -1
04-11 22:05:56.985: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 11 (uid: 10064 pid: 1376)
04-11 22:05:56.985: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 11
04-11 22:05:56.985: D/DisplayPowerController(1184): getFinalBrightness : Summary is 11 -> 11
04-11 22:05:56.985: D/AnimatedBrightnessIconView(1376): setValue : 9
04-11 22:05:56.985: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:56.985: D/AnimatedBrightnessIconView(1376): setValue : 9
04-11 22:05:56.985: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:56.985: D/AnimatedBrightnessIconView(1376): setValue : 9
04-11 22:05:56.985: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:56.985: D/DisplayPowerController(1184): animation target = 11, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:56.985: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:56.985: D/SensorManager(1184): unregisterListener ::
04-11 22:05:56.995: D/lights(1184): lcd : 46 +
04-11 22:05:56.995: D/lights(1184): lcd : 46 -
04-11 22:05:57.005: D/lights(1184): lcd : 13 +
04-11 22:05:57.005: D/lights(1184): lcd : 13 -
04-11 22:05:57.015: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.025: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.025: D/SettingsProvider(1184): name = screen_brightness_mode
04-11 22:05:57.025: D/SettingsProvider(1184): edmUri: content://com.sec.knox.provider/RestrictionPolicy3
04-11 22:05:57.025: D/SettingsProvider(1184): projectionArgs: isSettingsChangesAllowed
04-11 22:05:57.025: D/SettingsProvider(1184): selectionArgs: false
04-11 22:05:57.025: D/SettingsProvider(1184): selectionArgs: 10064
04-11 22:05:57.025: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.025: D/SettingsProvider(1184): ret = -1
04-11 22:05:57.025: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 42 (uid: 10064 pid: 1376)
04-11 22:05:57.025: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 42
04-11 22:05:57.025: D/DisplayPowerController(1184): getFinalBrightness : Summary is 42 -> 42
04-11 22:05:57.025: D/DisplayPowerController(1184): animation target = 42, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.025: D/lights(1184): lcd : 11 +
04-11 22:05:57.025: D/lights(1184): lcd : 11 -
04-11 22:05:57.025: D/DisplayPowerController(1184): getFinalBrightness : Summary is 42 -> 42
04-11 22:05:57.025: D/DisplayPowerController(1184): animation target = 42, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.025: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:57.035: D/AnimatedBrightnessIconView(1376): setValue : 40
04-11 22:05:57.035: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.035: D/AnimatedBrightnessIconView(1376): setValue : 40
04-11 22:05:57.035: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.035: D/AnimatedBrightnessIconView(1376): setValue : 40
04-11 22:05:57.035: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.035: D/StatusBar.BrightnessController(1376): updateMode : true
04-11 22:05:57.035: D/StatusBar.BrightnessController(1376): updateSlider : 0
04-11 22:05:57.045: D/lights(1184): lcd : 40 +
04-11 22:05:57.045: D/lights(1184): lcd : 40 -
04-11 22:05:57.045: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.045: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.045: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 67 (uid: 10064 pid: 1376)
04-11 22:05:57.045: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 67
04-11 22:05:57.045: D/DisplayPowerController(1184): getFinalBrightness : Summary is 67 -> 67
04-11 22:05:57.045: D/DisplayPowerController(1184): animation target = 67, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.045: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:57.045: D/AnimatedBrightnessIconView(1376): setValue : 65
04-11 22:05:57.045: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.045: D/AnimatedBrightnessIconView(1376): setValue : 65
04-11 22:05:57.045: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.055: D/AnimatedBrightnessIconView(1376): setValue : 65
04-11 22:05:57.055: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.055: D/DisplayPowerController(1184): getFinalBrightness : Summary is 67 -> 67
04-11 22:05:57.055: D/lights(1184): lcd : 67 +
04-11 22:05:57.065: D/DisplayPowerController(1184): animation target = 67, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.065: D/lights(1184): lcd : 67 -
04-11 22:05:57.065: D/DisplayPowerController(1184): getFinalBrightness : Summary is 67 -> 67
04-11 22:05:57.065: D/DisplayPowerController(1184): animation target = 67, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.065: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.065: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.065: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 81 (uid: 10064 pid: 1376)
04-11 22:05:57.065: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 81
04-11 22:05:57.065: D/DisplayPowerController(1184): getFinalBrightness : Summary is 81 -> 81
04-11 22:05:57.065: D/DisplayPowerController(1184): animation target = 81, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.075: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:57.085: D/lights(1184): lcd : 79 +
04-11 22:05:57.085: D/lights(1184): lcd : 79 -
04-11 22:05:57.085: D/AnimatedBrightnessIconView(1376): setValue : 79
04-11 22:05:57.085: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.085: D/AnimatedBrightnessIconView(1376): setValue : 79
04-11 22:05:57.085: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.085: D/AnimatedBrightnessIconView(1376): setValue : 79
04-11 22:05:57.085: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.095: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.095: D/DisplayPowerController(1184): getFinalBrightness : Summary is 81 -> 81
04-11 22:05:57.095: D/lights(1184): lcd : 81 +
04-11 22:05:57.095: D/DisplayPowerController(1184): animation target = 81, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.095: D/lights(1184): lcd : 81 -
04-11 22:05:57.095: D/DisplayPowerController(1184): getFinalBrightness : Summary is 81 -> 81
04-11 22:05:57.095: D/DisplayPowerController(1184): animation target = 81, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.095: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.095: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 96 (uid: 10064 pid: 1376)
04-11 22:05:57.095: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 96
04-11 22:05:57.095: D/DisplayPowerController(1184): getFinalBrightness : Summary is 96 -> 96
04-11 22:05:57.095: D/DisplayPowerController(1184): animation target = 96, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.095: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:57.095: D/AnimatedBrightnessIconView(1376): setValue : 94
04-11 22:05:57.095: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.095: D/AnimatedBrightnessIconView(1376): setValue : 94
04-11 22:05:57.095: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.095: D/AnimatedBrightnessIconView(1376): setValue : 94
04-11 22:05:57.095: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.105: D/DisplayPowerController(1184): getFinalBrightness : Summary is 96 -> 96
04-11 22:05:57.115: D/lights(1184): lcd : 96 +
04-11 22:05:57.115: D/lights(1184): lcd : 96 -
04-11 22:05:57.115: D/DisplayPowerController(1184): animation target = 96, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.115: D/DisplayPowerController(1184): getFinalBrightness : Summary is 96 -> 96
04-11 22:05:57.115: D/DisplayPowerController(1184): animation target = 96, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.115: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.115: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.115: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 130 (uid: 10064 pid: 1376)
04-11 22:05:57.115: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 130
04-11 22:05:57.115: D/DisplayPowerController(1184): getFinalBrightness : Summary is 130 -> 130
04-11 22:05:57.115: D/DisplayPowerController(1184): animation target = 130, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.115: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:57.115: D/AnimatedBrightnessIconView(1376): setValue : 128
04-11 22:05:57.115: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.115: D/AnimatedBrightnessIconView(1376): setValue : 128
04-11 22:05:57.115: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.115: D/AnimatedBrightnessIconView(1376): setValue : 128
04-11 22:05:57.115: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.125: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.135: D/lights(1184): lcd : 117 +
04-11 22:05:57.135: D/lights(1184): lcd : 117 -
04-11 22:05:57.135: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.135: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 149 (uid: 10064 pid: 1376)
04-11 22:05:57.135: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 149
04-11 22:05:57.135: D/DisplayPowerController(1184): getFinalBrightness : Summary is 149 -> 149
04-11 22:05:57.135: D/DisplayPowerController(1184): animation target = 149, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.135: D/AnimatedBrightnessIconView(1376): setValue : 147
04-11 22:05:57.135: D/PowerManagerService(1184): [s] DisplayPowerCallbacks : onStateChanged()
04-11 22:05:57.135: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.135: D/AnimatedBrightnessIconView(1376): setValue : 147
04-11 22:05:57.135: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.135: D/AnimatedBrightnessIconView(1376): setValue : 147
04-11 22:05:57.135: D/AnimatedBrightnessIconView(1376): setIcon
04-11 22:05:57.145: D/lights(1184): lcd : 149 +
04-11 22:05:57.145: D/DisplayPowerController(1184): getFinalBrightness : Summary is 149 -> 149
04-11 22:05:57.145: D/DisplayPowerController(1184): animation target = 149, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.145: D/lights(1184): lcd : 149 -
04-11 22:05:57.145: D/DisplayPowerController(1184): getFinalBrightness : Summary is 149 -> 149
04-11 22:05:57.145: D/KeyguardEffectViewController(1376): isRichLockWallpaper() = false
04-11 22:05:57.145: D/DisplayPowerController(1184): animation target = 149, rate=2000 (PSM:false, AB limit:(-1 ~ -1) MB Limit:(-1 ~ -1) MAdj:(0, (0, 255)))
04-11 22:05:57.145: D/SecContentProvider(1184): uri = 17 selection = isSettingsChangesAllowed
04-11 22:05:57.145: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverride: brightness: 169 (uid: 10064 pid: 1376)
04-11 22:05:57.145: D/PowerManagerService(1184): [api] setTemporaryScreenBrightnessSettingOverrideInternal: brightness: 169
04-11 22:05:57.145: D/DisplayPowerController(1184): getFinalBrightness : Summary is 169 -> 169

Some Screen shots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910V using Tapatalk

I'm not sure that this is helpful but i dont think it hurts... when using the gear vr on my dev lollipop note 4, instead of the brightness cranked all the way up, it seems to set itself to a low dark brightness (still unchangeable via the interface). something about it is able to lower the brightness when its plugged in. again not sure if thats useful information..
maybe it uses a screen filter like lux does ( i turned off lux before trying this to make sure it wasn't affecting it)

What is LP Screen brightness bug?
I don't have the DE phone but I'd like to know.

nabbed said:
What is LP Screen brightness bug?
I don't have the DE phone but I'd like to know.
Click to expand...
Click to collapse
It is a bug that affects Developer Note-4's that are on the latest LP.
It causes the screen to remain on full brightness. So far a good fix is an app called Lux Light. It works so well, I bought the pro version. https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite

Other fix for same problem
I am not a developer, but I read a lot on XDA. On one of the other ROM posts, I saw this:
chenxiaolong said:
Hey @AxAtAx:
Just found out how to fix the brightness issue! The Kit Kat bootloader on the Note 4 does not report the display panel's name, which the Lollipop kernel expects. CM already worked around this by hardcoding a valid value into the source code (https://github.com/CyanogenMod/andr...mmit/7fd52ab04c816cd03f65f8a991cf03054f18d731). I've applied this patch to ktoonsez's sources (at commit a2efde66e8903cd00eb70255b20802482f37552e), and as expected, the brightness changes work now
The following boot.img file should fix the brightness issue. I recompiled the kernel and swapped out the kernel from your boot image.
Enjoy!
Download: https://noobdev.io/visionx/boot.img
EDIT: Fantastic ROM by the way! It works much better than I originally anticipated.
Click to expand...
Click to collapse
Might the CM12 fix work on a dev ed now that the source code is available for the Verizon version?

ebrinkis said:
I am not a developer, but I read a lot on XDA. On one of the other ROM posts, I saw this:
Might the CM12 fix work on a dev ed now that the source code is available for the Verizon version?
Click to expand...
Click to collapse
I just flashed the above kernel and it dose fix the brightness issue. Now we need to have someone add this to our kernel. It's working but it isn't for the Note 4 and I get a S-Health crash on start up. This is great news the patch fixes the brightnes.:good:

Misterxtc said:
I just flashed the above kernel and it dose fix the brightness issue. Now we need to have someone add this to our kernel. It's working but it isn't for the Note 4 and I get a S-Health crash on start up. This is great news the patch fixes the brightnes.:good:
Click to expand...
Click to collapse
Confirmed working on my Verizon DevEd also.
Note 4 DE Sent

Misterxtc said:
I just flashed the above kernel and it dose fix the brightness issue. Now we need to have someone add this to our kernel. It's working but it isn't for the Note 4 and I get a S-Health crash on start up. This is great news the patch fixes the brightnes.:good:
Click to expand...
Click to collapse
After S-Health crash on startup does S-Health eventually work correctly? Or is it completely borked?

Misterxtc said:
I just flashed the above kernel and it dose fix the brightness issue. Now we need to have someone add this to our kernel. It's working but it isn't for the Note 4 and I get a S-Health crash on start up. This is great news the patch fixes the brightnes.:good:
Click to expand...
Click to collapse
Today's Kernel release by AEL for TMO:
(13 April 2015) N4 AEL Kernel v11B [Multivariant Lollipop Ed.]
Supposedly brightness bug fixed. I use the AEL TMO Kernel for Definitive KK ROM, maybe this will work as well?
I am just too chicken to try it myself because I know enough to get into trouble, but not enough to get out of trouble.

I was digging through this last night and I suspected this was the cause and was going to hard-code a device definition but saw this instead. I will flash AEL now to test.

ebrinkis said:
I am not a developer, but I read a lot on XDA. On one of the other ROM posts, I saw this:
Might the CM12 fix work on a dev ed now that the source code is available for the Verizon version?
Click to expand...
Click to collapse
Misterxtc said:
I just flashed the above kernel and it dose fix the brightness issue. Now we need to have someone add this to our kernel. It's working but it isn't for the Note 4 and I get a S-Health crash on start up. This is great news the patch fixes the brightnes.:good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks for this! It does help. I'm building a patched N910VVRU1BOAF kernel from source & will need testers soon, since I've not received my own device yet (will be delivered by Friday).

wy1d said:
I was digging through this last night and I suspected this was the cause and was going to hard-code a device definition but saw this instead. I will flash AEL now to test.
Click to expand...
Click to collapse
AEL Kernel works great. Brightness and screen modes now adjust properly. Clear data on the S-Health App to get it working with FC.

wy1d said:
AEL Kernel works great. Brightness and screen modes now adjust properly. Clear data on the S-Health App to get it working with FC.
Click to expand...
Click to collapse
It's working good here too. Viper4Android now works, as for shealth I just deleted it because I never use it.

so now we are just waiting on xposed

Mibuix0r said:
so now we are just waiting on xposed [emoji14]
Click to expand...
Click to collapse
Or SOMETHING to get rid of all these icons in my bar - Bluetooth, NFC, battery, clock AM/PM...

hsbadr said:
Thanks for this! It does help. I'm building a patched N910VVRU1BOAF kernel from source & will need testers soon, since I've not received my own device yet (will be delivered by Friday).
Click to expand...
Click to collapse
I'll gladly test pm when ready.
Also confirming AEL Kernel is working in the interim and clearing data on s-health works. Restored data, now good to go. Can't wait for xposed for samsung devices.

Misterxtc said:
It's working good here too. Viper4Android now works, as for shealth I just deleted it because I never use it.
Click to expand...
Click to collapse
dukins said:
I'll gladly test pm when ready.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'm almost done with the kernel building... will pack boot.img & send it your way
It includes the following changes:
Build from Samusng N910VVRU1BOAF source code
Patched to fix Screen Brightness Issue
Insecure debuggable kernel & Permissive SELinux
I'll add init.d support, BusyBox, rsync, SQLite3, .. etc.
I've also compared AEL kernel/ramdisk with ours & found that it at least doesn't include "Verizon Device Stats Partition" & "Sec EFS". I don't know if this affects anything though

hsbadr said:
I'm almost done with the kernel building... will pack boot.img & send it your way
It includes the following changes:
Build from Samusng N910VVRU1BOAF source code
Patched to fix Screen Brightness Issue
Insecure debuggable kernel & Permissive SELinux
I'll add init.d support, BusyBox, rsync, SQLite3, .. etc.
I've also compared AEL kernel/ramdisk with ours & found that it at least doesn't include "Verizon Device Stats Partition" & "Sec EFS". I don't know if this affects anything though
Click to expand...
Click to collapse
Sounds good, standing by.

I'd be happy to test also. Getting a couple of FC and one reboot in my pocket with AEL. It does have the fading LED which is neat.

upgrade of firmware for Mstar Cedric3 full AOSP 4.1 Jelly bean to 4.4 Kitkat

Hi Developers and friends ,
I bought a car android DVD from a distributor in Egypt I have no experience in android devices and found out later on it runs android 4.1.1 with an old user interface I would like to upgrade it to Kitkat 4.4.4 and install a new interface but have no idea how to the distributor says it is not up gradable so I decided to consult you guys to tell me what to do and is it possible to upgrade the device I managed to get the specs which is very similar to this device
General Specifications
Manufacturer MStar Semiconductor, Inc.
Model Full AOSP on MStar Cedric3
Android version 4.1.1; V1.0.1.0; SDK16
CPU 2 cores; ARMv7 Processor rev 0 (v7l) cedric
Display 1024 x 600; DPI: 160; Evaluated Size: 7.4"
Touch screen Multitouch 5 points
GPU Mali-400 MP; ARM; OpenGL ES-CM 1.1; OpenGL ES 2.0
RAM 1024 MB (1014 MB available)
Flash 16 GB Build-in (14.676 GB actual); 8 GB (7.455 GB actual)
Communications
Phone None
WiFi ntfs_3g
USB Host Yes
Bluetooth no
GPS No
Advanced Features
Front camera Photo: 2.1 MP; Max: 1920x1080; Video: 2.1 MP; Max: 1920x1080; Focus: auto; Flash modes: auto
Back camera Photo: 0.9 MP; Max size: 1280x720; Video: 0.9 MP; Max: 1280x720; Focus: auto; Flash modes: auto
Vibrator No
Supported languages 47; Afrikaans; Amharic; Arabic; Belarusian; Bulgarian; Catalan; Czech; Danish; German; Greek; English; Spanish; Estonian; Persian; Finnish; Filipino; French; Hebrew; Hindi; Croatian; Hungarian; Indonesian; Italian; Japanese; Korean; Lithuanian; Latvian; Malay; Norwegian; Dutch; Polish; Pashto; Portuguese; Romansh; Romanian; Russian; Slovak; Slovenian; Serbian; Swedish; Swahili; Thai; Turkish; Ukrainian; Vietnamese; Chinese; Zulu
Battery Technology: null; Voltage: 0
Owner's comment: Breton Car AVN
KERNEL: Linux version 3.4.5 ([email protected]) (gcc version 4.7.3 20130328 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC 2013.04) ) #609 SMP Wed Apr 23 14:08:14 CST 2014
CODENAME: REL
Mainboard: unknown
BRAND: Mstar
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: mstarcedric3
DISPLAY: full_mstarcedric3-userdebug 4.1.1 JRO03C V1.0.1.0 test-keys
FINGERPRINT: Mstar/full_mstarcedric3/mstarcedric3:4.1.1/JRO03C/V1.0.1.0:userdebug/test-keys
HARDWARE: cedric
ID: JRO03C
TAGS: test-keys
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1790.77
processor : 1
BogoMIPS : 1784.21
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0
Hardware : cedric
Revision : 0000
Serial : 0000000000000000
GL_EXT_debug_marker
GL_OES_texture_npot
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_depth24
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth_texture
GL_OES_packed_depth_stencil
GL_EXT_texture_format_BGRA8888
GL_EXT_blend_minmax
GL_OES_EGL_image_external
GL_OES_EGL_sync
GL_OES_rgb8_rgba8
GL_EXT_multisampled_render_to_texture
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_ARM_mali_program_binary
GL_EXT_shader_texture_lod
GL_EXT_robustness
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03C
ro.build.display.id=full_mstarcedric3-userdebug 4.1.1 JRO03C V1.0.1.0 test-keys
ro.build.version.incremental=V1.0.1.0
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=2014年 02月 09日 星期日 11:25:17 CST
ro.build.date.utc=1391916317
ro.build.type=userdebug
ro.build.user=john
ro.build.host=john
ro.build.tags=test-keys
ro.product.model=Full AOSP on MStar Cedric3
ro.product.brand=Mstar
ro.product.name=full_mstarcedric3
ro.product.device=mstarcedric3
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=MStar Semiconductor, Inc.
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=cedric
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mstarcedric3
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_mstarcedric3-userdebug 4.1.1 JRO03C V1.0.1.0 test-keys
ro.build.fingerprint=Mstar/full_mstarcedric3/mstarcedric3:4.1.1/JRO03C/V1.0.1.0:userdebug/test-keys
ro.build.characteristics=nosdcard
# end build properties
ms.mstplayer=1
ms.mstplayer.logless=1
hw.ms.display.destination=3
hw.ms.sc1_sync_sc0=1
hw.ms.hdmitx_timing=480_60P
hw.ms.hdmitx_color=YUV
ro.ms.System.bDualScreen=true
debug.sf.electron_frames=1
ms.subchannel.audio=1
hw.ms.sytem.audio=0
persist.service.adb.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.sf.lcd_density=160
qemu.sf.lcd_density=160
dalvik.vm.heapsize=128m
ro.opengles.version=131072
mstar.mstplayer.bd=1
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
8188eu 581869 0 - Live 0x00000000
ntfs_3g 186713 0 - Live 0x00000000 (O)
mali 94915 18 - Live 0x00000000 (O)
ump 26175 25 mali, Live 0x00000000 (O)
RAM: 1024 MB (1014 MB available)
System RAM: 1014.000MB
Flash: 16 GB Build-in (14.676 GB actual); 8 GB (7.455 GB actual)
mmcblk0: 14.676 GB
sda: 7.455 GB
can anyone help me please.

Hello. I have same problem as yours, after long research including flashes from another similar models mstar based I gave up. So no more hopes, we are stuck forever on 4.1.1 API16 JB on these ugly toys unfortunately. Best regards.

katalinscrob said:
Hello. I have same problem as yours, after long research including flashes from another similar models mstar based I gave up. So no more hopes, we are stuck forever on 4.1.1 API16 JB on these ugly toys unfortunately. Best regards.
Click to expand...
Click to collapse
I have this also, I really don't know what 4.4 will bring... you can do everything in 4.1.1 unit...

Hi.
I have the same head unit. I put REDMOD firmware. Everything works OK, except volume lights to the left of the screen.
The radio app is necessary that you use the original, he does not keep well the stations, at least in my case.
Search the video of rom in youtube:
RedMOD 0.2.1
And this is my head unit:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have the same head unit, could you send me a copy of the MCU and the original firmware?

[ROM] [X01AD] [12L] [UNOFFICIAL] [Stable] CherishOS v3.9.5 [FINAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH :
-Reboot to recovery
-Wipe system, cache dalvik, data
-Format Data
-Flash the ROM
-Flash Magisk
-Format Data
-Reboot
DIRTY FLASH : (If on A12L based rom)
-Reboot to recovery
-Wipe system, cache dalvik, data
-Flash the ROM
-Flash Magisk
-Reboot
DIRTY FLASH : (If already on Cherish A12L)
-Reboot to recovery
-Wipe cache dalvik
-Flash the ROM
-Flash Magisk
-Reboot
Download ROM
click here
Click here
Credits:
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
-Others, I forgot to mention
Based on Android 12L
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound / vibration
Known issues
You tell me (none)
Cherish-OS Source
Kernel Source
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
CherishOS for X01AD
Device: Asus Max M2
Build Type: Unofficial
ROM Firmware Required: A10
Based On: AOSP
Android OS version: 12L
Security patch level: July 2022
ROM Developer: Hungphan2001
Version Information
Status: Stable
Current Stable Version: 3.x
SELinux Status: Enforcing

Was already gonna be happy but the camera is so buggy, it was also laggy, I can't take pictures properly, I want it fix badly, here is the logcat I hope you got that...
```
--- Exception 1 / 2
t.k
Camera is closed.
w :: t.b1 :: 1
h :: n.b0 :: 1
h :: y.g :: 13
l :: y.g :: 8
b :: androidx.camera.lifecycle.c :: 2
E :: j2.q :: 4
q :: app.grapheneos.camera.ui.activities.MainActivity :: 7
onTouch :: j2.j :: 1
dispatchTouchEvent :: android.view.View :: 14597
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3114
dispatchTouchEvent :: android.view.ViewGroup :: 2787
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
superDispatchTouchEvent :: com.android.internal.policy.DecorView :: 498
superDispatchTouchEvent :: com.android.internal.policy.PhoneWindow :: 1891
dispatchTouchEvent :: android.app.Activity :: 4202
dispatchTouchEvent :: d.r :: 1
dispatchTouchEvent :: com.android.internal.policy.DecorView :: 456
dispatchPointerEvent :: android.view.View :: 14860
processPointerEvent :: android.view.ViewRootImpl$ViewPostImeInputStage :: 6455
onProcess :: android.view.ViewRootImpl$ViewPostImeInputStage :: 6251
deliver :: android.view.ViewRootImpl$InputStage :: 5729
onDeliverToNext :: android.view.ViewRootImpl$InputStage :: 5786
forward :: android.view.ViewRootImpl$InputStage :: 5752
forward :: android.view.ViewRootImpl$AsyncInputStage :: 5917
apply :: android.view.ViewRootImpl$InputStage :: 5760
apply :: android.view.ViewRootImpl$AsyncInputStage :: 5974
deliver :: android.view.ViewRootImpl$InputStage :: 5733
onDeliverToNext :: android.view.ViewRootImpl$InputStage :: 5786
forward :: android.view.ViewRootImpl$InputStage :: 5752
apply :: android.view.ViewRootImpl$InputStage :: 5760
deliver :: android.view.ViewRootImpl$InputStage :: 5733
deliverInputEvent :: android.view.ViewRootImpl :: 8713
doProcessInputEvents :: android.view.ViewRootImpl :: 8664
enqueueInputEvent :: android.view.ViewRootImpl :: 8633
onInputEvent :: android.view.ViewRootImpl$WindowInputEventReceiver :: 8836
dispatchInputEvent :: android.view.InputEventReceiver :: 259
nativePollOnce :: android.os.MessageQueue :: -2
next :: android.os.MessageQueue :: 335
loopOnce :: android.os.Looper :: 161
loop :: android.os.Looper :: 288
main :: android.app.ActivityThread :: 7882
invoke :: java.lang.reflect.Method :: -2
run :: com.android.internal.os.RuntimeInit$MethodAndArgsCaller :: 548
main :: com.android.internal.os.ZygoteInit :: 1003
--- Exception 2 / 2
t.c1
Camera is closed.
run :: t.x0 :: 5
runWorker :: java.util.concurrent.ThreadPoolExecutor :: 1167
run :: java.util.concurrent.ThreadPoolExecutor$Worker :: 641
run :: java.lang.Thread :: 920

ImOnAdateWithLia said:
Was already gonna be happy but the camera is so buggy, it was also laggy, I can't take pictures properly, I want it fix badly, here is the logcat I hope you got that...
```
--- Exception 1 / 2
t.k
Camera is closed.
w :: t.b1 :: 1
h :: n.b0 :: 1
h :: y.g :: 13
l :: y.g :: 8
b :: androidx.camera.lifecycle.c :: 2
E :: j2.q :: 4
q :: app.grapheneos.camera.ui.activities.MainActivity :: 7
onTouch :: j2.j :: 1
dispatchTouchEvent :: android.view.View :: 14597
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3114
dispatchTouchEvent :: android.view.ViewGroup :: 2787
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
dispatchTransformedTouchEvent :: android.view.ViewGroup :: 3120
dispatchTouchEvent :: android.view.ViewGroup :: 2801
superDispatchTouchEvent :: com.android.internal.policy.DecorView :: 498
superDispatchTouchEvent :: com.android.internal.policy.PhoneWindow :: 1891
dispatchTouchEvent :: android.app.Activity :: 4202
dispatchTouchEvent :: d.r :: 1
dispatchTouchEvent :: com.android.internal.policy.DecorView :: 456
dispatchPointerEvent :: android.view.View :: 14860
processPointerEvent :: android.view.ViewRootImpl$ViewPostImeInputStage :: 6455
onProcess :: android.view.ViewRootImpl$ViewPostImeInputStage :: 6251
deliver :: android.view.ViewRootImpl$InputStage :: 5729
onDeliverToNext :: android.view.ViewRootImpl$InputStage :: 5786
forward :: android.view.ViewRootImpl$InputStage :: 5752
forward :: android.view.ViewRootImpl$AsyncInputStage :: 5917
apply :: android.view.ViewRootImpl$InputStage :: 5760
apply :: android.view.ViewRootImpl$AsyncInputStage :: 5974
deliver :: android.view.ViewRootImpl$InputStage :: 5733
onDeliverToNext :: android.view.ViewRootImpl$InputStage :: 5786
forward :: android.view.ViewRootImpl$InputStage :: 5752
apply :: android.view.ViewRootImpl$InputStage :: 5760
deliver :: android.view.ViewRootImpl$InputStage :: 5733
deliverInputEvent :: android.view.ViewRootImpl :: 8713
doProcessInputEvents :: android.view.ViewRootImpl :: 8664
enqueueInputEvent :: android.view.ViewRootImpl :: 8633
onInputEvent :: android.view.ViewRootImpl$WindowInputEventReceiver :: 8836
dispatchInputEvent :: android.view.InputEventReceiver :: 259
nativePollOnce :: android.os.MessageQueue :: -2
next :: android.os.MessageQueue :: 335
loopOnce :: android.os.Looper :: 161
loop :: android.os.Looper :: 288
main :: android.app.ActivityThread :: 7882
invoke :: java.lang.reflect.Method :: -2
run :: com.android.internal.os.RuntimeInit$MethodAndArgsCaller :: 548
main :: com.android.internal.os.ZygoteInit :: 1003
--- Exception 2 / 2
t.c1
Camera is closed.
run :: t.x0 :: 5
runWorker :: java.util.concurrent.ThreadPoolExecutor :: 1167
run :: java.util.concurrent.ThreadPoolExecutor$Worker :: 641
run :: java.lang.Thread :: 920
Click to expand...
Click to collapse
Will fix in next build but now
U can use gcam or gcam go or other cam (don't use stock camera) this problem is in stock cam only

Saif Stark said:
Will fix in next build but now
U can use gcam or gcam go or other cam (don't use stock camera) this problem is in stock cam only
Click to expand...
Click to collapse
I can still encounter the problem in variety of cameras(laggy(picture mode, not in video), doesn't capture (unless you tweak the settings), but it works well than the stock one...
Do you have a TG for this ROM? So I can send all possible problems there?
There's also a bug where Icons don't fit properly in the task bar if the "dp(smallest width)" is set to 600+ or tablet size...

Saif Stark said:
Will fix in next build but now
U can use gcam or gcam go or other cam (don't use stock camera) this problem is only in stock camera
Click to expand...
Click to collapse
Gcam go working fine i tested with gcam go u can join asus max m2 official telegram channel and ask there

Database Users

welcome

Battery drain!!! - Galaxy Note 3 Q&A, Help & Troubleshooting

Related

[TOOL] Nbench for Android

Bricked my lg d802 i think please help

{SOLVED} Note-4 DevEd LP Screen brightness bug

upgrade of firmware for Mstar Cedric3 full AOSP 4.1 Jelly bean to 4.4 Kitkat

[ROM] [X01AD] [12L] [UNOFFICIAL] [Stable] CherishOS v3.9.5 [FINAL]

Categories

Resources