Unofficial CrDroid-OSv6 Android 10
- Thread starter khalvat
- Start date
New build 2020-07-15 is Available
Fixed screen recorder
Improved ril for some regions
Edit: Updated lineage recovery to 2020-07-18
Fixed screen recorder
Improved ril for some regions
Edit: Updated lineage recovery to 2020-07-18
Last edited:
Hi,
nice ROM, much snappier than the last official stock (5.0.1).
However, compared to stock, the battery melts away. I turned off everything (Wifi, Bluetooth, NFC, weather service) and switched the mobile network to GSM only. The phone is clean, e.g. does not have any apps installed.
Attached is a BetterBatteryStats dump for approx. 2 hours of idling. The only suspicious thing I see is this one:
What kernel power management options are available with the ROM? What other info can I provide to help debug this?
nice ROM, much snappier than the last official stock (5.0.1).
However, compared to stock, the battery melts away. I turned off everything (Wifi, Bluetooth, NFC, weather service) and switched the mobile network to GSM only. The phone is clean, e.g. does not have any apps installed.
Attached is a BetterBatteryStats dump for approx. 2 hours of idling. The only suspicious thing I see is this one:
Additionally, TeMeFI says the CPU was never in the lowest state (300 MHz).
What kernel power management options are available with the ROM? What other info can I provide to help debug this?
Code:
===================
General Information
===================
BetterBatteryStats version: 2.3-248
Creation Date: 2020-07-25 02:31:00
Statistic Type: Screen Off to Screen On
Since 1 h 58 m 20 s
Note:
VERSION.RELEASE: 10
BRAND: samsung
DEVICE: ks01ltexx
MANUFACTURER: samsung
MODEL: GT-I9506
OS.VERSION: 3.4.113-Khalvat-MBA-g5dd7c1ca7
BOOTLOADER: I9506XXUDRB1
HARDWARE: qcom
FINGERPRINT: samsung/ks01ltexx/ks01lte:5.0.1/LRX22C/I9506XXUDRB1:user/release-keys
ID: QQ3A.200705.002
TAGS: release-keys
USER: khalvat
PRODUCT: ks01lte
RADIO: I9506XXUDRA1
Root perms: true
SELinux Policy:
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -12%(67% to 55%) [6.1%/h]
Voltage lost [mV]: (3712-3617) [48.2%/h]
===========
Other Usage
===========
Deep Sleep (): 1 h 57 m 41 s 99.4%
Awake (Screen Off) (): 34 s 0.5%
Screen On (): 5 s 0.1%
Doze Interactive Time (): 5 s 0.1%
Doze Idle Mode Time (): 1 h 55 m 9 s 97.3%
No Data Connection (): 1 h 58 m 20 s 100.0%
Moderate Signal (): 1 h 58 m 18 s 100.0%
Good Signal (): 2 s 0.0%
Screen dark (): 0.0%
Screen medium (): 5 s 0.1%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
deviceidle_maint (crDroid System): 10 s Count:8 0.1%
AnyMotionDetector (crDroid System): 7 s Count:16 0.1%
AudioMix (1041): 2 s Count:0 0.0%
================
Kernel Wakelocks
================
PowerManagerService.WakeLocks (*api*): 22 s Cnt:(c/wc/ec)30/0/0 0.3%
[timerfd] (*api*): 14 s Cnt:(c/wc/ec)124/0/0 0.2%
PowerManagerService.Display (*api*): 5 s Cnt:(c/wc/ec)1/0/0 0.1%
PowerManager.SuspendLockout (*api*): 5 s Cnt:(c/wc/ec)1/0/0 0.1%
resume_wakelock (*api*): 3 s Cnt:(c/wc/ec)34/0/0 0.0%
smdcntl0 (*api*): 2 s Cnt:(c/wc/ec)41/0/0 0.0%
radio-interface (*api*): 1 s Cnt:(c/wc/ec)7/0/0 0.0%
event18 (*api*): Cnt:(c/wc/ec)68/0/0 0.0%
PowerManagerService.Broadcasts (*api*): Cnt:(c/wc/ec)1/0/0 0.0%
event0 (*api*): Cnt:(c/wc/ec)68/0/0 0.0%
event3 (*api*): Cnt:(c/wc/ec)156/0/0 0.0%
ipc00000002_rmt_storage (*api*): Cnt:(c/wc/ec)13/0/0 0.0%
event19 (*api*): Cnt:(c/wc/ec)68/0/0 0.0%
sec-battery-monitor (*api*): Cnt:(c/wc/ec)34/0/0 0.0%
event18-800 (*api*): Cnt:(c/wc/ec)34/0/0 0.0%
KeyEvents (*api*): Cnt:(c/wc/ec)79/0/0 0.0%
event0-800 (*api*): Cnt:(c/wc/ec)34/0/0 0.0%
event3-800 (*api*): Cnt:(c/wc/ec)78/0/0 0.0%
event19-800 (*api*): Cnt:(c/wc/ec)34/0/0 0.0%
qcril (*api*): Cnt:(c/wc/ec)19/0/0 0.0%
rmt_storage_-1482706384 (*api*): Cnt:(c/wc/ec)1/0/0 0.0%
rmt_storage_-1481653712 (*api*): Cnt:(c/wc/ec)1/0/0 0.0%
NETLINK (*api*): Cnt:(c/wc/ec)24/0/0 0.0%
ApmOutput (*api*): Cnt:(c/wc/ec)6/0/0 0.0%
qpnp-iadc-19 (*api*): Cnt:(c/wc/ec)1/0/0 0.0%
qmuxd_port_wl_0 (*api*): Cnt:(c/wc/ec)44/0/0 0.0%
eventpoll (*api*): Cnt:(c/wc/ec)272/0/0 0.0%
battery (*api*): Cnt:(c/wc/ec)12/0/0 0.0%
ipc0000000f_time_daemon (*api*): Cnt:(c/wc/ec)2/0/0 0.0%
=========
Processes
=========
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BBS): Uid: 10201 Sys: 10 s Us: 41 s Starts: 0
system (crDroid System): Uid: 1000 Sys: 11 s Us: 18 s Starts: 0
surfaceflinger (crDroid System): Uid: 1000 Sys: 7 s Us: 10 s Starts: 0
com.android.systemui (com.android.systemui.System UI): Uid: 10186 Sys: 1 s Us: 5 s Starts: 0
kworker/u:5 (0): Uid: 0 Sys: 5 s Us: Starts: 0
kworker/u:6 (0): Uid: 0 Sys: 4 s Us: Starts: 0
kworker/u:2 (0): Uid: 0 Sys: 4 s Us: Starts: 0
kworker/u:8 (0): Uid: 0 Sys: 4 s Us: Starts: 0
kworker/u:1 (0): Uid: 0 Sys: 4 s Us: Starts: 0
logd (1036): Uid: 1036 Sys: 1 s Us: 2 s Starts: 0
ksoftirqd/0 (0): Uid: 0 Sys: 3 s Us: Starts: 0
kworker/u:4 (0): Uid: 0 Sys: 3 s Us: Starts: 0
kworker/u:7 (0): Uid: 0 Sys: 2 s Us: Starts: 0
com.android.launcher3 (com.android.launcher3.crDroid Home): Uid: 10182 Sys: Us: 2 s Starts: 0
ueventd (0): Uid: 0 Sys: Us: 2 s Starts: 0
com.android.phone (Phone Services): Uid: 1001 Sys: Us: 1 s Starts: 0
mdss_fb0 (0): Uid: 0 Sys: 2 s Us: Starts: 0
irq/330-synapti (0): Uid: 0 Sys: 2 s Us: Starts: 0
audioserver (1041): Uid: 1041 Sys: Us: Starts: 0
[email protected] (crDroid System): Uid: 1000 Sys: Us: Starts: 0
[email protected] (crDroid System): Uid: 1000 Sys: Us: Starts: 0
kworker/u:0H (0): Uid: 0 Sys: 1 s Us: Starts: 0
[email protected] (com.android.nfc.Nfc Service): Uid: 1027 Sys: Us: Starts: 0
irq/334-SSP_Int (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
rmt_storage (9999): Uid: 9999 Sys: Us: Starts: 0
servicemanager (crDroid System): Uid: 1000 Sys: Us: Starts: 0
rild (Phone Services): Uid: 1001 Sys: Us: Starts: 0
statsd (1066): Uid: 1066 Sys: Us: Starts: 0
system (0): Uid: 0 Sys: Us: Starts: 0
mmcqd/1 (0): Uid: 0 Sys: Us: Starts: 0
migration/0 (0): Uid: 0 Sys: Us: Starts: 0
healthd (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:3 (0): Uid: 0 Sys: Us: Starts: 0
irq/256-msm_sdc (0): Uid: 0 Sys: Us: Starts: 0
kworker/0:1 (0): Uid: 0 Sys: Us: Starts: 0
ip6tables-restore (0): Uid: 0 Sys: Us: Starts: 0
iptables-restore (0): Uid: 0 Sys: Us: Starts: 0
com.android.inputmethod.latin (com.android.inputmethod.latin.Android Keyboard (AOSP)): Uid: 10195 Sys: Us: Starts: 0
logcat (0): Uid: 0 Sys: Us: Starts: 0
lmkd (1069): Uid: 1069 Sys: Us: Starts: 0
netd (0): Uid: 0 Sys: Us: Starts: 0
kthreadd (0): Uid: 0 Sys: Us: Starts: 0
qmuxd (Phone Services): Uid: 1001 Sys: Us: Starts: 0
jbd2/mmcblk0p26 (0): Uid: 0 Sys: Us: Starts: 0
init (0): Uid: 0 Sys: Us: Starts: 0
thermal-engine (0): Uid: 0 Sys: Us: Starts: 0
[email protected] (crDroid System): Uid: 1000 Sys: Us: Starts: 0
[email protected] (crDroid System): Uid: 1000 Sys: Us: Starts: 0
irq/195-ngd_sli (0): Uid: 0 Sys: Us: Starts: 0
flush-179:0 (0): Uid: 0 Sys: Us: Starts: 0
adbd (com.android.shell.Shell): Uid: 2000 Sys: Us: Starts: 0
time_daemon (crDroid System): Uid: 1000 Sys: Us: Starts: 0
com.android.cellbroadcastreceiver (com.android.cellbroadcastreceiver.Wireless emergency alerts): Uid: 10133 Sys: Us: Starts: 0
======================
Alarms
======================
android (): Wakeups: 10 (5.1 / h)
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: TIME_TICK
Alarms: 6, Intent: DeviceIdleController.light
Alarms: 3, Intent: DeviceIdleController.deep
Alarms: 0, Intent: GraphicsStatsService
Alarms: 1, Intent: JS idleness
Alarms: 0, Intent: *job.delay*
Alarms: 0, Intent: *job.deadline*
======================
Network
======================
==========
CPU States
==========
2.27 GHz (): 39 s 0.6%
Deep Sleep (): 1 h 57 m 41 s 99.4%
==========
Sensors
==========
(crDroid System): Sensor: K330 3-axis Accelerometer(1), wakeup=false, Time: 6 s
Sensor: SAMSUNG Significant Motion Sensor(10), wakeup=true, Time: 41 m 1 s
Sensor: Linear Acceleration Sensor(1600940398), wakeup=false, Time: 0 s
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats.services.EventWatcherService)
Active since: 1 m 2 s
Last activity: 5 m 18 s
Crash count:0
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 4 s (Wl: 2 elements; KWl: 53elements; NetS: 0 elements; Alrm: 0 elements; Proc: 119 elements; Oth: 13 elements; CPU: 2 elements; Sensors: 1 elements)
ref_screen_off: Reference ref_screen_off created 4 m 55 s (Wl: 4 elements; KWl: 70elements; NetS: 0 elements; Alrm: 2 elements; Proc: 127 elements; Oth: 15 elements; CPU: 3 elements; Sensors: 1 elements)
ref_screen_on: Reference ref_screen_on created 2 h 3 m 16 s (Wl: 5 elements; KWl: 72elements; NetS: 0 elements; Alrm: 2 elements; Proc: 128 elements; Oth: 15 elements; CPU: 3 elements; Sensors: 1 elements)
ref_current: Reference ref_current created 2 h 3 m 17 s (Wl: 5 elements; KWl: 72elements; NetS: 0 elements; Alrm: 2 elements; Proc: 128 elements; Oth: 15 elements; CPU: 3 elements; Sensors: 1 elements)
------ human readable part end hereHave you checked how doze is doing within TeMeFI? Not sure how the OS reports the CPU while the phone is in doze. I know my phone (different ROM) sits the whole day in deep-idle, but the CPU reports lots of other activity. I haven't checked the numbers, but I think the CPU state logs, do not include doze. Otherwise I think mine would look very different.
I am guessing you are running: https://forum.xda-developers.com/showpost.php?p=80185720&postcount=122
you can also use the graphs and reports to drill down into times when battery is draining, or NOT, ummm NOT draining... https://forum.xda-developers.com/showpost.php?p=82136035&postcount=37010
One thing to remember, as soon as you add any apps over the default ROM, it could be caused by your changes.
Not possible to store photos with cameras on SD card
Hi,
The build is fantastic, but I am not able to save photos from camera app to SD card.
With internal storrage it works fine.
My SD Card is Samsung 256GB
Any idea how to solve it?
Hi,
The build is fantastic, but I am not able to save photos from camera app to SD card.
With internal storrage it works fine.
My SD Card is Samsung 256GB
Any idea how to solve it?
The folder /storage/AA4A-BD0A/DCIM/Camera/ is empty.
There is a lot of errors in logcat:
View attachment log.zip
New build 2020-08-07 is Available
Merged august security patch
Fixed AOSP screen recorder
Improved performance
Merged august security patch
Fixed AOSP screen recorder
Improved performance
Any possibility of developing RR Q for this device?
Would've been awesome...
Would've been awesome...
I haven't updated to the latest build so am still on the previous build, but yesterday I made a phone call on the previous build using a headset (NB: its a spare/test phone and not my daily), The call volume was too loud, so I tried to turn it down, but none of the volume sliders actually lowered the volume. If anyone else has a headset, could they confirm the same, and if it is possibly fixed in the latest build.
When I get a chance to flash the latest build, if its still there, i'll get a logcat to see if there are any clues in there.
---------- Post added at 12:19 ---------- Previous post was at 12:01 ----------
Are there specific features that RR have in Q, that are not present in crDroid Q? A few years back I was building multiple ROMs for another device (XT907 and also to a lesser extent the Nexus 5) and I could not understand why people loved crDroid so much, when RR had everything that crDroid had (customisation wise), plus more. BUT that was specific to the version of Android. As it moves up, the balance of features also moves between ROMs. And hence, my current daily is Havoc OS Oreo; it has more features in Oreo than RR, which was the only ROM I would run previously.
RR had a lot more customization in previous versions of android. But, things have changed.
SPECIFICALLY which customisations does RR have that crDroid does not?
I know the one I want is not in crDroid OR RR
Any reason or is there something missing from the camera built into the ROM?
I am still testing, so I don't use it as a daily, but was really surprised by just how featured the camera that comes with the ROM actually was.
Can someone please re-upload the correct modem zip, the other link is corrupted. Error reading line 207 or something. Thanks. Tried 7 times from sammobile, all failing.
For me this link from the first post ist working:
Recomended Bootloader/Modem : https://androidfilehost.com/?fid=3700668719832239236 (I9506XXUDRB1_I9506XXUDRA1)
New build 2020-09-11 is Available (Final build)
Not incuded september security patch
Updated Lineage recovery
Updated offmod charge image
Fixed some bugs
Not incuded september security patch
Updated Lineage recovery
Updated offmod charge image
Fixed some bugs
Is this latest update for this device or I'll be more updates ?
Thanks for ur great work
Regards.
Android 11 Alpha build here 2020-09-25
https://androidfilehost.com/?fid=8889791610682945917
its only for test
Working
Ril
Wifi
Sounds
Sensors
Bluetooth
EDIT: link moved in new page
its only for test
Working
Ril
Wifi
Sounds
Sensors
Bluetooth
EDIT: link moved in new page
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone