181 pagesV  « < 175 176 177 178 179 180 > »  
 
REPLY
> Linux kernel from the inside | all questions about Linux kernel
coolkaas
Message#1
20.11.14, 20:40
viewer
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 5969
Check in: 09.11.10
Xiaomi Redmi 4X 3/32

Reputation:-  849  +

All answers to android nuclear questions: how the Linux kernel is organized in general and for Android in particular, the interaction mechanisms inside the kernel, kernel programming, discussion of various errors that occur during kernel assembly and operation, general kernel configuration rules and other system issues.
It discusses the kernel at the source level. Because of this, it is recommended to attach a link to the repository with the kernel sources, protocols (dmesg) in text form to your question.
It is better to set questions for assembling kernel images and packaging these images into a specific loader format for a specific device in a specialized topic.section. For example,Self-compiled kernel from source, Android 4.4.x (KitKat) / 5.x.x (Lollipop) / 6.x.x (Marshmallow) / 7.x.x (Nougat) kernel build for MTK processors, Assistance in the development and porting of Android OS on MTK devices, Developing Android 6.0 kernel and firmware for Asus Zenfone Go, Development and porting for devices on the Spreadtrum SC7731 platform, Development of kernels and firmware Redmi 4 (prada), RockChip rk3188 and newer, kernel build and moreetc.
The topic has grown from here:Shell scripts for Android. The parent theme discusses the system issues of the functioning of Android in the user space (userspace): the initial start, low-level interaction with the system components of the Android.

Linux kernel regulatory materials
  • The founding document on the Android device internals, Android Interfaces and Architecture, contains a sectionKernelwhich outlines the basic requirements for the core from the Android side, highlights the issues of configuring the kernel, optimizing individual components of the kernel, etc.
Some materials of the topic:

For questions of filling and updating the topic header, the Curator is always ready to help you.username11

Post has been editedusername11 - 26.07.18, 15:29
Reason for editing: Added section with regulatory materials
username11
Message#3522
04.03.19, 13:11
User
*********
[offline]

Topics Curator
Group: Curators
Messages 11477
Check in: 04.07.11
HTC Desire S

Reputation:-  2190  +

* lifeketsvilWell, if you have kernel sources, you can build any module from there. Accordingly, if - no, then - no. The question is whether all this will work. But it can and then decide.
Dbim4iko
Message#3523
04.03.19, 21:01
Smoke
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1669
Check in: 03.09.11
Xiaomi MiPad

Reputation:-  1044  +

user11 @ 03/04/19 13:11*
well, if you have the kernel source, you can build any module from there. Accordingly, if - no, then - no. The question is whether all this will work. But it can and then decide.

Without a root, it seems like it is impossible to load the kernel module, and since the boot is locked, then there is probably no root either, and for this you probably don’t have to assemble a module, but if there is a root, then yes it is possible.
* lifeketsvil,
And even if there is a root, but there are no kernel sources for your device, then you can simply take the kernel sources (preferably from the android branches in the Google repo) of the same version as your kernel, and compile the module in it. the success rate of loading and proper functioning will be high, but not one hundred percent and problems may occur.


--------------------
<<| DEVICE:Xiaomi MiPaD Blue 16GB |ROM: LineageOS 14.1 SHIELD BLOBS | KERNEL:SmokeR24.1 |>>
username11
Message#3524
05.03.19, 12:51
User
*********
[offline]

Topics Curator
Group: Curators
Messages 11477
Check in: 04.07.11
HTC Desire S

Reputation:-  2190  +

* Dbim4iko1. If there is no root, why write here? I reasoned like that. 2. Not "problems can be observed", but problems will be observed. At least because of symbol versioning. Here, by the way, nobody was able to overcome them, although the task is not so difficult.
bober87
Message#3525
05.03.19, 14:25
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 77
Check in: 21.09.16
BQ-mobile BQ-5202 Space Lite

Reputation:-  22  +

help to find all the ways to initiate a physical record from userspace: (assuming that the cache is infinitely long and large, the system does not go into sleep mode, does not restart and does not turn off, the fs log is disabled, commit = many)

umount, remount
/ proc / sys / vm / drop_caches
sync, fsync, fdatasync, msync
munmap (?)
open with O_SYNC, O_DIRECT flags

except for a completely exotic, I did not miss anything?
Dbim4iko
Message#3526
05.03.19, 14:48
Smoke
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1669
Check in: 03.09.11
Xiaomi MiPad

Reputation:-  1044  +

user11 @ 03/05/2019, 12:51*
* Dbim4iko, 2. Not "problems can be observed", but problems will be observed. At least because of symbol versioning. Here, by the way, nobody was able to overcome them, although the task is not so difficult.

From my experience, the modules worked correctly and stably, but not all, some influenced the stability of the system, or the performance of the module itself with the corresponding. error messages in the log. For example, the module ttl, worked fine, for a long time.

Post has been editedDbim4iko - 05.03.19, 14:57


--------------------
<<| DEVICE:Xiaomi MiPaD Blue 16GB |ROM: LineageOS 14.1 SHIELD BLOBS | KERNEL:SmokeR24.1 |>>
username11
Message#3527
05.03.19, 14:59
User
*********
[offline]

Topics Curator
Group: Curators
Messages 11477
Check in: 04.07.11
HTC Desire S

Reputation:-  2190  +

* bober87, 1. "Physical record from userspace" where? On the block device? Why and for what? 2. / proc / sys / vm / drop_caches to write exactly no sideways. About the rest - after the question becomes clear.
bober87
Message#3528
05.03.19, 15:21
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 77
Check in: 21.09.16
BQ-mobile BQ-5202 Space Lite

Reputation:-  22  +

* bober87, 1. "Physical record from userspace" where?

Yes. on the block device. looking for the culprit who dumps dirty pages. sync'and disabled at the level of libc.
about drop_caches re-read man, understood, thanks.

I found this:
blockdev --flushbufs / dev / XXX
hdparm -F / dev / XXX
adm_
Message#3529
05.03.19, 15:47
#define false rand ()% 2
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 3105
Check in: 10.12.08
Zopo ZP980 +

Reputation:-  261  +

* bober87,
in mount any left / wild commit'y not present? / system not in rw, an hour?
... I prescribed commit = 600, there are no glitches on the kitcat ...

Post has been editedadm_ - 05.03.19, 15:52


--------------------
When asking a question, it is necessary to know the percent answer at 70. Otherwise, it is meaningless to ask it: nothing will be clear from the answer anyway.
bober87
Message#3530
05.03.19, 15:55
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 77
Check in: 21.09.16
BQ-mobile BQ-5202 Space Lite

Reputation:-  22  +

adm_ @ 03/05/19 16:47*
in mount any wild commit'y are not observed?
... I registered myself commit = 600, no glitches ...

which prescribe, they are observed. let's say 900. and in fact, in practice, I did not notice the difference with different values, even c 5 by default. it definitely does not mean recording everything every five seconds. but something else.
username11
Message#3531
05.03.19, 16:59
User
*********
[offline]

Topics Curator
Group: Curators
Messages 11477
Check in: 04.07.11
HTC Desire S

Reputation:-  2190  +

* bober87, 1. Well, the modified data is modified and in order to quickly write them back, not really clicking the beak. In this sense, the “culprit†may be the core as a whole. 2. And so, all of the above, taking into account the levels, of course: umount, remount, sync, fsync, fdatasync, syncfs - file system level and buffer cache, msync, munmap - that part of the buffer cache that is mapped into the process, blockdev - -flushbufs - the level of the block device driver (not applicable to all such devices, say, with mmc it makes no sense to Android), hdparm -F - at the level of the hardware of the block device itself (disk, i.e., past Android). 3. If you want to find the culprit, you will have to, I fear, dance straight from the kernel, the block device driver / IO scheduler, going higher and higher, up to the userspace, until the culprit is found. 4. On Android, one of the possible culprits is vold.

Posted 05/03/2019, 17:03:

* bober87, if "fs log is disabled", what other "differences with different values"? commit in the appropriate mount option means journal commit.
shuchvadim
Message#3532
15.03.19, 12:19
Banned
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 14238
Check in: 05.03.14
Xiaomi Redmi Note 5A 2/16

Reputation:-  1238  +

* username11Hello! Will there be a performance boost if the processor is overclocked but the voltage is not raised? Ie if the frequency is raised and the phone is independent at the last voltage, then so go? Or does the voltage rise above that at the previous frequency necessarily?
username11
Message#3533
15.03.19, 13:20
User
*********
[offline]

Topics Curator
Group: Curators
Messages 11477
Check in: 04.07.11
HTC Desire S

Reputation:-  2190  +

* shuchvadimSuch questions should be sought in the documentation on the processor, only there the working conditions of the processor are stated.
lzittod
Message#3534
23.03.19, 02:24
Local
*****
[offline]

Group: Friendssavagemessiahzine.com
Messages 393
Check in: 03.10.18

Reputation:-  13  +

Advise what the reason may be - the incorrect work of the custom kernel and under the native and modified governer interactive.
Lenova's body on msm8939v2, kernels and firmwares on it from some one .. collected from source codes 8916.
Oreo firmware, Kernel custom, with
irregularity is the reluctance to reduce the frequency and consumption in the absence of any load - that is, When the settings tab or another application is open, if there are no running applications, the body eats as if under a video player. Literally 5-10min tinkering in the settings takes out 10% of the battery, but the kernel falls asleep.
Moreover, when turning on ThunderhoPCMark + for + Android + Benchmarktplag in the bark mode, all 8 or 4 there is no practical reduction in consumption.
after all sorts of choices for setting options of the governor, oddity appears - first, when loading and accepting settings, the body rises to the frequency settings of the gover-ra, but after the screen is turned off, the screen raises the frequency by 1-2 bits and 1-2 liters to max and does not reset. both the av window and the use shedul in both 0 and 1. are interleaved, if you run the antutu in this gover setting, PCMark + for + Android + Benchmark or cinema - the frequencies are controlled and fall in minutes.
Anyways, I just don't understand what's wrong with this body.
in fact, without any load, he eats almost the same way as under tests or load.
* shuchvadim
Yes, I tried others, but by the results of the tests I thought of putting interactive.
I did not think about the log ... and I don’t know what to look there. Now I looked at the output of dmesg in another kernel, and ...
It was the case, they advised me to look at the bugreport, but this did not say anything to me, well, yes, what and when it was launched, and how much it consumes. Yes, and the file turned out 2.8mb

* username11,
The question is actually fundamental: we have:
Dragon-Elite-v1.4-Oreo Kernel with Thunderplus
when it is turned on (generally in all modes), for example, frequency 200, threshold 85, per-core mode.
In the adiutor kernel, the settings are set interactively to keep the body at rest at 1–2 hkor per 400 mg (well, 3-5 cortex twitches, connects, raises the frequency after launching which thread, such as an antitude in the background.
type all good ...
but, the PCMark + for + Android + Benchmark_2.0.3716_apk-dl.com test on the battery showed gave an hour less life than without a hotplug. I tried the lower frequency of 50 and 10 and 150 against the default of 500 (this is the frequency of a hotplug campaign) and a greater 85% threshold for picking up other bark. paid for it by half the low result of the antitu 7.1.
so the question is how to understand this ??? Equally, and without HP, the body eats at these settings like a goblin, as well as under load, that it’s just an open window at rest.

Now for the logs.
I pulled out 2019-03-24_015939_logcat. 740kb and 2019-03-24_022530_bugreport
in the last
Total PSS by process
Total PSS by process:
113,651K: system (pid 1716)
63,093K: com.android.systemui (pid 4365)
61,452K: com.android.settings (pid 1762 / activities)
61,280K: us.koller.cameraroll (pid 9790 / activities)
45,981K: com.antutu.ABenchMark (pid 10050 / activities)
45,086K: com.google.android.apps.nexuslauncher (pid 5664 / activities)
36,807K: surfaceflinger (pid 398)
23,539K: com.kerneladiutor.mod (pid 3728 / activities)
20,679K: com.android.inputmethod.latin (pid 4349)
20,657K: com.UCMobile.intl (pid 10718)
18,142K: com.UCMobile.intl: channel (pid 29294)
16,466K: com.UCMobile.intl: resident (pid 29328)
16,420K: com.antutu.ABenchMark: push (pid 10244)
16,183K: com.UCMobile.intl: collapsed (pid 12406)
15.660K: com.android.phone (pid 4721)
10,782K: com.UCMobile.intl: RemoteBackgroundProcess (pid 10664)
9,288K: com.android.systemui: screenshot (pid 9216)
9.006K: com.UCMobile.intl: bgprocess (pid 28179)
7,453K: com.android.webview: sandboxed_process0 (pid 10176)
7,446K: com.antutu.benchmark.full (pid 7967)
6,390K: com.android.packageinstaller (pid 9598)
6.037K: webview_zygote32 (pid 4426)
6,020K: android.process.media (pid 7912)
6,006K: zygote (pid 353)
5.683K: zygote64 (pid 352)
5,614K: rild (pid 420)
4.256K: rild (pid 407)
4.137K: org.omnirom.omnibrain (pid 5610)
4.023K: com.android.musicfx (pid 8124)
3,916K: mediaserver (pid 416)
3,902K: logd (pid 300)
3,822K: mm-qcamera-daemon (pid 422)
3,817K: audioserver (pid 409)
3,808K: org.omnirom.omnijaws (pid 1719)
3,763K: media.extractor (pid 414)
3,533K: com.cyanogenmod.settings.doze (pid 5623)
3,492K: com.android.smspush (pid 5676)
3,491K: com.custom.ambient.display (pid 5636)
3.216K: media.codec (pid 419)
2,367K: media.metrics (pid 415)
2,326K: / init (pid 1)
2,093K: netmgrd (pid 406)
1,802K: dumpstate (pid 15385)
1,635K: su (pid 6402)
1,548K: drmserver (pid 410)
1.511K: netd (pid 351)
1,488K: ueventd (pid 274)
1,474K: vold (pid 310)
1,429K: installd (pid 411)
1,428K: thermal-engine (pid 403)
1,120K: hwservicemanager (pid 302)
1,009K: [email protected] (pid 389)
997K: keystore (pid 412)
954K: imsdatadaemon (pid 445)
879K: qmuxd (pid 405)
873K: time_daemon (pid 423)
855K: dumpsys (pid 15392)
841K: wificond (pid 418)
825K: gatekeeperd (pid 425)
823K: [email protected] (pid 391)
796K: magiskd (pid 324)
793K: storaged (pid 417)
781K: [email protected] (pid 387)
778K: mediadrmserver (pid 413)
746K: adbd (pid 400)
743K: servicemanager (pid 301)
728K: thermalserviced (pid 399)
726K: [email protected] (pid 388)
724K: lmkd (pid 397)
714K: healthd (pid 392)
707K: imsqmidaemon (pid 408)
702K: sh (pid 6407)
697K: sh (pid 15382)
692K: [email protected] (pid 386)
646K: [email protected] (pid 390)
632K: ip6tables-restore (pid 362)
617K: iptables-restore (pid 361)
615K: vndservicemanager (pid 303)
613K: logcat (pid 339)
613K: [email protected] (pid 385)
602K: [email protected] (pid 384)
592K: rmt_storage (pid 394)
529K: bugreport (pid 15384)
510K: vm_bms (pid 347)
484K: wcnss_service (pid 402)
481K: qseecomd (pid 443)
457K: tombstoned (pid 433)
402K: magisklogd (pid 330)
359K: qseecomd (pid 393)

Total PSS by OOM adjustment:
133,595K: Native
36,807K: surfaceflinger (pid 398)
6.037K: webview_zygote32 (pid 4426)
6,006K: zygote (pid 353)
5.683K: zygote64 (pid 352)
5,614K: rild (pid 420)
4.256K: rild (pid 407)
3,916K: mediaserver (pid 416)
3,902K: logd (pid 300)
3,822K: mm-qcamera-daemon (pid 422)
3,817K: audioserver (pid 409)
3,763K: media.extractor (pid 414)
3.216K: media.codec (pid 419)
2,367K: media.metrics (pid 415)
2,326K: / init (pid 1)
2,093K: netmgrd (pid 406)
1,802K: dumpstate (pid 15385)
1,635K: su (pid 6402)
1,548K: drmserver (pid 410)
1.511K: netd (pid 351)
1,488K: ueventd (pid 274)
1,474K: vold (pid 310)
1,429K: installd (pid 411)
1,428K: thermal-engine (pid 403)
1,120K: hwservicemanager (pid 302)
1,009K: [email protected] (pid 389)
997K: keystore (pid 412)
954K: imsdatadaemon (pid 445)
879K: qmuxd (pid 405)
873K: time_daemon (pid 423)
855K: dumpsys (pid 15392)
841K: wificond (pid 418)
825K: gatekeeperd (pid 425)
823K: [email protected] (pid 391)
796K: magiskd (pid 324)
793K: storaged (pid 417)
781K: [email protected] (pid 387)
778K: mediadrmserver (pid 413)
746K: adbd (pid 400)
743K: servicemanager (pid 301)
728K: thermalserviced (pid 399)
726K: [email protected] (pid 388)
724K: lmkd (pid 397)
714K: healthd (pid 392)
707K: imsqmidaemon (pid 408)
702K: sh (pid 6407)
697K: sh (pid 15382)
692K: [email protected] (pid 386)
646K: [email protected] (pid 390)
632K: ip6tables-restore (pid 362)
617K: iptables-restore (pid 361)
615K: vndservicemanager (pid 303)
613K: logcat (pid 339)
613K: [email protected] (pid 385)
602K: [email protected] (pid 384)
592K: rmt_storage (pid 394)
529K: bugreport (pid 15384)
510K: vm_bms (pid 347)
484K: wcnss_service (pid 402)
481K: qseecomd (pid 443)
457K: tombstoned (pid 433)
402K: magisklogd (pid 330)
359K: qseecomd (pid 393)
113,651K: System
113,651K: system (pid 1716)
89,914K: Persistent
63,093K: com.android.systemui (pid 4365)
15.660K: com.android.phone (pid 4721)
4.137K: org.omnirom.omnibrain (pid 5610)
3,533K: com.cyanogenmod.settings.doze (pid 5623)
3,491K: com.custom.ambient.display (pid 5636)
45,086K: Foreground
45,086K: com.google.android.apps.nexuslauncher (pid 5664 / activities)
3,492K: Visible
3,492K: com.android.smspush (pid 5676)
74,113K: Perceptible
45,981K: com.antutu.ABenchMark (pid 10050 / activities)
20,679K: com.android.inputmethod.latin (pid 4349)
7,453K: com.android.webview: sandboxed_process0 (pid 10176)
16,466K: A Services
16,466K: com.UCMobile.intl: resident (pid 29328)
61,280K: Previous
61,280K: us.koller.cameraroll (pid 9790 / activities)
29,449K: B Services
16,420K: com.antutu.ABenchMark: push (pid 10244)
9.006K: com.UCMobile.intl: bgprocess (pid 28179)
4.023K: com.android.musicfx (pid 8124)
183,707K: Cached
61,452K: com.android.settings (pid 1762 / activities)
23,539K: com.kerneladiutor.mod (pid 3728 / activities)
20,657K: com.UCMobile.intl (pid 10718)
18,142K: com.UCMobile.intl: channel (pid 29294)
16,183K: com.UCMobile.intl: collapsed (pid 12406)
10,782K: com.UCMobile.intl: RemoteBackgroundProcess (pid 10664)
9,288K: com.android.systemui: screenshot (pid 9216)
7,446K: com.antutu.benchmark.full (pid 7967)
6,390K: com.android.packageinstaller (pid 9598)
6,020K: android.process.media (pid 7912)
3,808K: org.omnirom.omnijaws (pid 1719)

Total PSS by category:
246,417K: Native
86,485K: .dex mmap
43,970K: .App vdex
39,372K: .Boot vdex
3,143K: .app dex
81,255K: .so mmap
69,399K: Dalvik
57,354K: .heap
5,617K: .Zygote
4,668K: .LOS
1,760K: .NonMoving
45,224K: EGL mtrack
43,131K: .apk mmap
41,861K: .art mmap
40,981K: .Boot art
880K: .App art
33,464K: Unknown
31,296K: .oat mmap
28,387K: Dalvik Other
15,087K: .LinearAlloc
8,064K: .JITCache
2,752K: .IndirectRef
2,484K: .GC
0K: .CompilerMetadata
15.566K: Gfx dev
14,872K: Stack
7,520K: Other mmap
2,304K: .jar mmap
1,768K: Ashmem
945K: Other dev
859K: .ttf mmap
0K: Cursor
0K: GL mtrack
0K: Other mtrack

and
DUMPSYS CPUINFO (/ system / bin / dumpsys -t 10 cpuinfo -a)
7.355s was the duration of 'DUMPSYS MEMINFO' ------
------ DUMPSYS CPUINFO (/ system / bin / dumpsys -t 10 cpuinfo -a) ------
Load: 4.16 / 3.76 / 3.59
CPU usage from 65659ms to 805ms ago (2019-03-24 02: 24: 39.210 to 2019-03-24 02: 25: 44.063):
7.7% 29328 / com.UCMobile.intl: resident: 1.1% user + 6.6% kernel / faults: 2604 minor 7 major
6.7% 1716 / system_server: 4.5% user + 2.2% kernel / faults: 8462 minor 3 major
4.1% 4365 / com.android.systemui: 2.9% user + 1.1% kernel / faults: 10111 minor 2 major
2.8% 10050 / com.antutu.ABenchMark: 2.2% user + 0.5% kernel / faults: 2561 minor
1.2% 258 / uksmd: 0% user + 1.2% kernel
0.7% 398 / surfaceflinger: 0.4% user + 0.3% kernel / faults: 369 minor
0.6% 5664 / com.google.android.apps.nexuslauncher: 0.5% user + 0% kernel / faults: 2352 minor 20 major
0.4% 4721 / com.android.phone: 0.3% user + 0.1% kernel / faults: 2152 minor
0% 10176 / com.android.webview: sandboxe: 0% user + 0% kernel / faults: 2085 minor 40 major
0% 1762 / com.android.settings: 0% user + 0% kernel / faults: 3184 minor
0.2% 7 / rcuc / 0: 0% user + 0.2% kernel
0.2% 241 / mmcqd / 0: 0% user + 0.2% kernel
0.2% 9790 / us.koller.cameraroll: 0.2% user + 0% kernel / faults: 1499 minor 1 major
0.2% 9 / rcu_preempt: 0% user + 0.2% kernel
0.2% 29294 / com.UCMobile.intl: channel: 0.2% user + 0% kernel / faults: 2587 minor
0% 4349 / com.android.inputmethod.latin: 0% user + 0% kernel / faults: 3635 minor 1 major
0.2% 12406 / com.UCMobile.intl: collapsed: 0.2% user + 0% kernel / faults: 1071 minor
0.2% 3728 / com.kerneladiutor.mod: 0.2% user + 0% kernel / faults: 2321 minor
0.2% 10718 / com.UCMobile.intl: 0.2% user + 0% kernel / faults: 1204 minor
0.2% 10664 / com.UCMobile.intl: RemoteBackgroundProcess: 0.2% user + 0% kernel / faults: 1149 minor
0.1% 28179 / com.UCMobile.intl: bgprocess: 0.1% user + 0% kernel / faults: 3058 minor
0.1% 210 / cfinteractive: 0% user + 0.1% kernel
0.1% 7912 / android.process.media: 0.1% user + 0% kernel / faults: 1642 minor
0% 7967 / com.antutu.benchmark.full: 0% user + 0% kernel / faults: 1882 minor
0.1% 301 / servicemanager: 0% user + 0% kernel / faults: 277 minor
0.1% 14766 / kworker / u16: 3: 0% user + 0.1% kernel
0.1% 15196 / kworker / 0: 1: 0% user + 0.1% kernel
0.1% 3 / ksoftirqd / 0: 0% user + 0.1% kernel
0.1% 300 / logd: 0% user + 0% kernel / faults: 2 minor
0% 5623 / com.cyanogenmod.settings.doze: 0% user + 0% kernel / faults: 3254 minor
0% 5676 / com.android.smspush: 0% user + 0% kernel / faults: 3198 minor
0% 9598 / com.android.packageinstaller: 0% user + 0% kernel / faults: 1483 minor
0.1% 10244 / com.antutu.ABenchMark: push: 0.1% user + 0% kernel / faults: 866 minor
0.1% 1719 / org.omnirom.omnijaws: 0.1% user + 0% kernel / faults: 2061 minor
0% 5610 / org.omnirom.omnibrain: 0% user + 0% kernel / faults: 3091 minor
0% 5636 / com.custom.ambient.display: 0% user + 0% kernel / faults: 3088 minor
0% 8124 / com.android.musicfx: 0% user + 0% kernel / faults: 3181 minor
0% 9216 / com.android.systemui: screenshot: 0% user + 0% kernel / faults: 1163 minor
0% 65 / kworker / u17: 0: 0% user + 0% kernel
0% 351 / netd: 0% user + 0% kernel / faults: 123 minor
0% 14768 / kworker / u16: 6: 0% user + 0% kernel
0% 100 / system: 0% user + 0% kernel
0% 389/[email protected]: 0% user + 0% kernel / faults: 11 minor
0% 405 / qmuxd: 0% user + 0% kernel / faults: 39 minor
0% 14791 / kworker / u16: 8: 0% user + 0% kernel
0% 19 / rcuc / 2: 0% user + 0% kernel
0% 409 / audioserver: 0% user + 0% kernel / faults: 12 minor
0% 20 / ksoftirqd / 2: 0% user + 0% kernel
0% 67 / kworker / u17: 1: 0% user + 0% kernel
0% 274 / ueventd: 0% user + 0% kernel / faults: 20 minor
0% 400 / adbd: 0% user + 0% kernel / faults: 254 minor
0% 420 / rild: 0% user + 0% kernel
0% 14877 / kworker / u16: 9: 0% user + 0% kernel
0% 1 // init: 0% user + 0% kernel / faults: 44 minor
0% 12 / migration / 0: 0% user + 0% kernel
0% 13 / migration / 1: 0% user + 0% kernel
0% 14 / rcuc / 1: 0% user + 0% kernel
0% 18 / migration / 2: 0% user + 0% kernel
0% 63 / kworker / u16: 1: 0% user + 0% kernel
0% 179 / hwrng: 0% user + 0% kernel
0% 189 / kgsl_worker_thr: 0% user + 0% kernel
0% 200 / irq / 13-ft5x06_t: 0% user + 0% kernel
0% 289 / jbd2 / mmcblk0p30: 0% user + 0% kernel
0% 339 / logcat: 0% user + 0% kernel
0% 347 / vm_bms: 0% user + 0% kernel
0% 403 / thermal-engine: 0% user + 0% kernel
0% 406 / netmgrd: 0% user + 0% kernel / faults: 192 minor
0% 407 / rild: 0% user + 0% kernel
+ 0% 15339 / mdss_fb0: 0% user + 0% kernel
+ 0% 15382 / sh: 0% user + 0% kernel
+ 0% 15384 / bugreport: 0% user + 0% kernel
+ 0% 15385 / dumpstate: 0% user + 0% kernel
+ 0% 15392 / dumpsys: 0% user + 0% kernel
24% TOTAL: 12% user + 10% kernel + 0.8% iowait + 0% softirq
------ 0.025s was the duration of 'DUMPSYS CPUINFO' ------

I just stuck it in different bug reports - of this and other kernels, including from the wonderful kernel with mtk - but I didn’t drive there?
so the percentages of the CPU load never explain its zhor.
I understand that the work of hp itself is a cost as a process or whatever is in the kernel, but so much so!
I already think, maybe it's a freaky screen consumption? but, even for fhd, this is zinadto at 5inch.
username11
Message#3535
23.03.19, 19:49
User
*********
[offline]

Topics Curator
Group: Curators
Messages 11477
Check in: 04.07.11
HTC Desire S

Reputation:-  2190  +

* lzittod, 1. The main problem is that if you do not know what to look in the log, then the advice that you will be given here is unlikely to help you. 2. According to your mind, you need to take the source code and the dmesg of the stock kernel, look at what is happening there, compare it with the custom one.
shuchvadim
Message#3536
25.03.19, 07:18
Banned
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 14238
Check in: 05.03.14
Xiaomi Redmi Note 5A 2/16

Reputation:-  1238  +

* username11no herehttps: //www.qualcomm.c...ssor-product-brief.pdfnothing detailed. This is about the voltage and frequency, and why the hotplug is not used (by the way, other phone manufacturers on this processor also do not use it, I asked). Where else can I see the documentation on this chip?
sngvy
Message#3537
25.03.19, 11:54
Designer Translator
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 3412
Check in: 09.12.11
Honor 8X JSN-L21

Reputation:-  598  +

* shuchvadimBut how does the flyer to the technical documentation? You need datasheet


--------------------
Honor 8X Premium Phantom Blue JSN-L21
alek.spv
Message#3538
26.03.19, 12:48
Local
*****
[offline]

Group: Friendssavagemessiahzine.com
Messages 115
Check in: 12.03.11
Xiaomi Redmi Note 4X Snapdragon 3/16

Reputation:-  4  +

Prompt, don `t know just even where to ask, I think it would be appropriate here.
Samsung SM-J510FN recovery, kernel with F2FS support
I wanted to translate the system partition to F2FS.
Unpacked the kernel, in fstab.qcom changed ext4 to F2FS
/ dev / block / bootdevice / by-name / system / system f2fs ro, barrier = 1 wait, recoveryonly
Restored backup via twrp with a tick "Use rm -rf instead of formatting"
The phone at startup constantly goes into Download mode, if everything is returned to ext4 then there is no problem.
What else needs to be changed in the core? or is it some kind of samsung boot mechanism or qualcomm secure boot? which checks the type of system partition?
* sngvy,
* shuchvadim,
The partition is formatted in twrp on f2fs.
I’ve also dug up that with the 8th android the mount system has changed, like project treble is called, fstab should be on the path / system / vendor / etc
But on this custom firmware pie 9 Samsung fstab is not there, it lies in the boot.
On redmi note 4x is also a custom pie 9 firmware, I looked in the boot there is no fstab, found it in / system / vendor / etc
Generally confused


--------------------
Verizon HTC Touch Pro2 (CDMA + GSM)>>HTC Desire A8181 Bravo SlimKat [4.4.4] + (microG)>>Huawei Honor u8860 cm-11 [4.4.4] + (microG)>>Xiaomi Redmi Note 4x LoS 14.1 [7.1.2] + (microG)
shuchvadim
Message#3539
26.03.19, 15:25
Banned
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 14238
Check in: 05.03.14
Xiaomi Redmi Note 5A 2/16

Reputation:-  1238  +

* username11, good day . In the core, can anything be changed in relation to the sound by passing through bitterness and discridation? The bottom line: the rattling of low frequencies of reproduction, while it happens on their elongated reproduction and not on fast (that is, for example, the bit is normal, but let's say the bass guitar is rattling). Or should we look for reasons and solutions in another? I changed the firmware from other manufacturers, the situation has not changed (the only thing that comes from the drain is the audio from hw and mixer paths)
shuchvadim
Message#3540
26.03.19, 15:31
Banned
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 14238
Check in: 05.03.14
Xiaomi Redmi Note 5A 2/16

Reputation:-  1238  +

* username11By the way, you are right, the manufacturer is smarter)) I tried to turn on the player at night with one core and 4 with a fixed frequency of the CPU and the result is the same for the consumption of acb. So hotplag is from the category of those not boring oboin))
sngvy
Message#3541
26.03.19, 16:17
Designer Translator
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 3412
Check in: 09.12.11
Honor 8X JSN-L21

Reputation:-  598  +

alek.spv @ 03.26.19, 12:48*
Restored backup via twrp with a tick "Use rm -rf instead of formatting"

Do not bother you that the drive requires formatting?

Posted on 03/26/2019 4:19 PM:

shuchvadim @ 03.26.19, 15:25*
rattling low frequencies

And the core here is what side, I wonder?
First, headphones; second, effects libraries.


--------------------
Honor 8X Premium Phantom Blue JSN-L21

181 pagesV  « < 175 176 177 178 179 180 > » 


 mobile version    Now: 05/20/19 07:45