Database Users

Why not a bigger swap?

Ive been thinking since we have always been told dont use a bigger than 32mb swap on any(most) hero ROMs
why not use a 256 mb swap to make the g1's internal ram to be "equal" to the htc hero
Maybe it would work or has this been tested before and end up being a total fail???
correct me please cuz im considering trying this out to see if it actually works
but am not sure if i want to, because of the obvious precautions.

Well, the phone won't kill off running applications until it's out of memory, so more memory = you end up with a hell of a lot more applications running, which is sortof pointless.
And it'll put a lot more preasure on the memory card.
But... loading an application from swap is probably faster than going through onCreate in most applications.

jf4888 said:
Ive been thinking since we have always been told dont use a bigger than 32mb swap on any(most) hero ROMs
why not use a 256 mb swap to make the g1's internal ram to be "equal" to the htc hero
Maybe it would work or has this been tested before and end up being a total fail???
correct me please cuz im considering trying this out to see if it actually works
but am not sure if i want to, because of the obvious precautions.
Click to expand...
Click to collapse
see this thread
http://forum.xda-developers.com/showthread.php?p=4124061
this post
#1902

toeshot said:
see this thread
http://forum.xda-developers.com/showthread.php?p=4124061
this post
#1902
Click to expand...
Click to collapse
The information in there is somewhat dated with regards to how swap works. Swap, back in the 60's, was program-by-program since multitasking wasn't what it is today. Now its in BLOCKS called MEMORY PAGES. The memory you save to swap is for RUNNING PROCESSES and is based on last-access time and access frequency.
Works like this;
You have 2 running processes, each uses 50 pages, total used is 100 pages. Lets say you have only 40 pages of physical ram and that each process has 10 active pages, that leaves 80 swappable pages, and 20 active pages. Obviously, not all can fit into ram, so 60 are dumped to swap. When one process tries to access memory that has been swapped to disk, there is a page fault and it loads that page from disk into memory and based on the algorithm used, it selects one of the in-memory pages and swaps it to disk.
Now the fun part: Lets say you try running 5 programs, each using 10 highly active pages and you only have 40 available. Now it starts THRASHING -- this is what kills performance, and on a multitasking OS, this is a very definite threat when the number of active memory pages exceeds the number available. When you increase your swap TOO MUCH, android will leave TOO MANY processes ACTIVE and you WILL GET THRASHING. Note that thrashing WILL KILL your sdcard FAST (though not necessarily any faster than you will get fed up with the slowness and reboot it).
Android has a very nice memory management feature where it kills those inactive processes. Having a huge amount of swap space will prevent this memory management feature from working correctly and will result in too many apps running, which will result in thrashing and poor performance. It is of particular importance to recognize this feature. Typical guidelines for setting swap space are not applicable to Android due to its memory management features.
Read this regarding paging (swapping):
http://en.wikipedia.org/wiki/Swap_space
http://en.wikipedia.org/wiki/Page_table

I am a little confused. I have read the links you provided, but I do not see anywhere were it says to decrease swap size. In fact after reading the articles I feel it supports my case even more. (See http://en.wikipedia.org/wiki/Thrash_(computer_science) Cause of Thrashing or even the overview)as for android killing sleeping process. that's not true either. here is an Process List of an idle G1 the S (Right Before the Process Name) stands for sleeping
# ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 292 208 c00ca8d0 0000caec S /init
root 2 0 0 0 c006c4bc 00000000 S kthreadd
root 3 2 0 0 c005bb94 00000000 S ksoftirqd/0
root 4 2 0 0 c00898bc 00000000 S watchdog/0
root 5 2 0 0 c008d1a0 00000000 S rcu_sched_grace
root 6 2 0 0 c0068620 00000000 S events/0
root 7 2 0 0 c0068620 00000000 S khelper
root 8 2 0 0 c0068620 00000000 S suspend
root 9 2 0 0 c0068620 00000000 S kblockd/0
root 10 2 0 0 c0068620 00000000 S kmmcd
root 11 2 0 0 c0068620 00000000 S btaddconn
root 12 2 0 0 c0068620 00000000 S btdelconn
root 13 2 0 0 c0068620 00000000 S kondemand/0
root 14 2 0 0 c0068620 00000000 S qmi
root 15 2 0 0 c0037830 00000000 D rpcrouter
root 16 2 0 0 c0068620 00000000 S detection/0
root 17 2 0 0 c00399f4 00000000 S krpcserversd
# ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 292 208 c00ca8d0 0000caec S /init
root 2 0 0 0 c006c4bc 00000000 S kthreadd
root 3 2 0 0 c005bb94 00000000 S ksoftirqd/0
root 4 2 0 0 c00898bc 00000000 S watchdog/0
root 5 2 0 0 c008d1a0 00000000 S rcu_sched_grace
root 6 2 0 0 c0068620 00000000 S events/0
root 7 2 0 0 c0068620 00000000 S khelper
root 8 2 0 0 c0068620 00000000 S suspend
root 9 2 0 0 c0068620 00000000 S kblockd/0
root 10 2 0 0 c0068620 00000000 S kmmcd
root 11 2 0 0 c0068620 00000000 S btaddconn
root 12 2 0 0 c0068620 00000000 S btdelconn
root 13 2 0 0 c0068620 00000000 S kondemand/0
root 14 2 0 0 c0068620 00000000 S qmi
root 15 2 0 0 c0037830 00000000 D rpcrouter
root 16 2 0 0 c0068620 00000000 S detection/0
root 17 2 0 0 c00399f4 00000000 S krpcserversd
root 18 2 0 0 c00979e0 00000000 S pdflush
root 19 2 0 0 c00979e0 00000000 S pdflush
root 20 2 0 0 c009cda8 00000000 S kswapd0
root 21 2 0 0 c0068620 00000000 S aio/0
root 24 2 0 0 c00388d0 00000000 S kadspd
root 36 2 0 0 c0068620 00000000 S panel_on/0
root 43 2 0 0 c01fb17c 00000000 S mtdblockd
root 44 2 0 0 c0201db0 00000000 S USB mass_storag
root 46 2 0 0 c0068620 00000000 S synaptics_wq
root 47 2 0 0 c0068620 00000000 S kstriped
root 48 2 0 0 c0068620 00000000 S hid_compat
root 49 2 0 0 c02ed850 00000000 S krfcommd
root 52 2 0 0 c0230fe8 00000000 S mmcqd
root 53 2 0 0 c01e5df4 00000000 S loop0
root 54 2 0 0 c01e5df4 00000000 S loop1
root 56 1 3332 156 ffffffff 0000e8f4 S /sbin/adbd
root 66 2 0 0 c014bc74 00000000 S kjournald
system 109 1 808 168 c0242cb0 afe0c45c S /system/bin/servicemanager
root 110 1 848 256 c00ca8d0 afe0c584 S /system/bin/vold
root 111 1 668 152 c02504d8 afe0cdec S /system/bin/debuggerd
radio 112 1 7896 696 ffffffff afe0cacc S /system/bin/rild
root 113 1 73092 13704 c00ca8d0 afe0c584 S zygote
media 114 1 24272 1248 ffffffff afe0c45c S /system/bin/mediaserver
bluetooth 117 1 1172 224 c00ca8d0 afe0d25c S /system/bin/dbus-daemon
root 118 1 800 192 c02cf988 afe0c1bc S /system/bin/installd
compass 120 1 3372 472 ffffffff afe0c45c S /system/bin/akmd
system 133 113 154716 23712 ffffffff afe0c45c S system_server
radio 168 113 107580 17276 ffffffff afe0d3e4 S com.android.phone
app_7 174 113 119796 20292 ffffffff afe0d3e4 S android.process.acore
app_62 208 113 99700 15032 ffffffff afe0d3e4 S com.p1.chompsms
app_1 221 113 110712 16964 ffffffff afe0d3e4 S com.google.process.gapps
app_20 234 113 98256 14464 ffffffff afe0d3e4 S android.process.media
root 267 2 0 0 c00386f0 00000000 D audmgr_rpc
app_36 310 113 95004 13496 ffffffff afe0d3e4 S com.android.alarmclock
app_21 344 113 106684 16440 ffffffff afe0d3e4 S com.htc.android.mail
root 368 1 4064 408 c00c3180 afe0c1bc S su
app_65 369 113 95608 13488 ffffffff afe0d3e4 S com.phonefusion.voicemailplus.android
app_54 418 113 95020 13692 ffffffff afe0d3e4 S org.freecoder.widgets.overclock
app_27 500 113 106180 15536 ffffffff afe0d3e4 S com.google.android.gm
app_7 561 113 98652 13564 ffffffff afe0d3e4 S com.android.inputmethod.latin
app_43 568 113 106064 15484 ffffffff afe0d3e4 S com.koushikdutta.klaxon
app_32 761 113 98412 15280 ffffffff afe0d3e4 S com.android.calendar
app_71 775 113 94428 13048 ffffffff afe0d3e4 S com.roundedlabs.widgets.gps
app_42 1058 113 94800 17008 ffffffff afe0d3e4 S com.twidroid:remote
root 1083 56 740 332 c0059630 afe0d08c S /system/bin/sh
root 1086 1083 884 340 00000000 afe0c1bc R ps
Now I don't have a swap partition active nor am I using swapper and I have 2k of free memory. If select on a 32mb for a swap partition that partition would fill quickly with the sleeping process, yes they would go to the swap partition However the swap partiton would not be completely filled to 32 meg because of the partition overhead. the memory that I freed up be partially available, meaning I would not see a full 32mb. however if I select 100mb swap partition it would not fill up, file swapping would better as there is more available space to put the sleeping programs until needed, freeing up more ram for the phone when I start to use it.
One thing to remember is that even though the android Cupcake will multi thread and multi task processes in the background it will not truly multi task applications. For example you can not open up a sms message and then open up google maps without the sms going into the background and going to sleepand if you don't have GPS on once the map is loaded it will go to sleep until you interact with it.

[Q] Phone keeps waking up - TyphooN CyanogenMod 7 vs. HyperDroidGBX-v12

I've gone from Typhoon CyanogenMod to HyperDroidGBX-v12 and it seems that Hyperdroid keeps connecting to wifi in intervals and waking up the phone which has taken a lot more battery over night than CyanogenMod did. I love the speed of Hyperdroid so I was wondering if there is anything I can do?
When I switched the phone on using Cyanogen I saw him switch off the mobile data connection and switch on wifi. Hyperdroid doesn't seem to manage it like that. Can I customize this?
edit: I found the option under wireless to switch if off when the phone is asleep but I don't think he's doing as he's told (my phone is male, in case you're wondering)...
I've attached a screen of my phone over night with HyperDroid. It kept waking up without the screen being on. I assume that's the root of all evil...
The only app that syncs on my phone atm is the GMail app, no facebook or others.
Any suggestions?
Thanks
edit:
I've searched some more and there were people who's wireless went to sleep when they didn't want it to, the opposite of my problem. I've done a clean install of HyperDroid again and the problem persists, at least the wireless not switching off. Since that worked with CyanogenMod I assume that's the root cause. I'm surprised this hasn't picked up on before, assuming other people have the same problem.
I guess I'd like to know if there are any simple file swaps I can perform like changing drivers between the two mods?
editv2:
Wireless seems to at least switch off now. I tried killing inactive apps. I'll see what happens from here.

Usually it's apps polling for updates.
This includes Facebook, Twitter etc. Are you using Google Latitude? That can wake the device every few minutes.
To check for wakelocks
Code:
cat /proc/wakelocks

It happened again last night that the phone appears awake for quite some time. I've got the wakelocks (which I don't know how to interpret). I'll post them and a screenshot of battery. I'm hoping to either hear a solution or that it's normal.
It seems like he had a much more quiet night tonight. I wish I had paid more attention to it while using Cyanogen. I've installed the battery current widget so that should be interesting as well.
Cheers.
Code:
name count expire_count wake_count active_since total_time sleep_time max_time last_cha
nge
"alarm" 957 0 0 0 23959014779 21546905463 384429936 9723528995498
"wlan_wake" 19027 0 49 0 86119018687 44324798717 1083984373 9683300205212
"main" 17 0 0 0 7736565871862 0 5511280593319 9680620426163
"event4-252" 34973 0 0 0 3475555677 0 6408692 9680155307754
"msmfb_idle_lock" 54032 0 0 0 4743530364 0 278686529 9680154453261
"ds2746-battery" 667 0 0 0 9070099039 8503753803 39886474 9679912631970
"alarm_rtc" 562 8 0 0 63026972383 63025843229 1034118654 8779276859239
"KeyEvents" 35993 0 0 0 4014678958 84869382 86914061 9679667270643
"event3-252" 216 0 0 0 124999996 73455813 16967773 9679666141493
"gpio_input" 52 0 9 0 528106698 122161869 10437012 9679665958387
"event5-252" 284 0 0 0 16235353 0 762939 9675881534557
"usb_mass_storage" 1 0 0 0 229509429930 0 229509429930 9228090579970
"power-supply" 135 0 0 0 70007320 41687016 2685547 9673667392715
"power-supply" 7 0 0 0 6774905 3875733 2532958 9673667209609
"power-supply" 7 0 0 0 10894774 2655028 5859375 9673667087539
"wlan_rx_wake" 1078 1078 0 0 1729369137961 185800921021 21577879641 9670940219862
"qmi" 17 17 0 0 8471907985 1995538327 509357909 9670940189344
"SMD_DATA5" 563 563 120 0 491717996183 412869000741 9329598383 9670940189344
"event0-252" 35776 0 0 0 2916259736 0 3112793 9603342624641
"gpio_kp" 83 0 2 0 14742034892 22491454 1275268561 9585008335097
"AudioHardwareQSDOut" 16 0 0 0 94738861105 704864502 20176086427 8977790592174
"audio_pcm_suspend" 14 0 0 0 211352722187 422058099 35328094487 8977790500621
"audio_pcm_idle" 14 0 0 0 211352630634 0 35328094487 8977790500621
"SMD_RPCCALL" 7382 0 555 0 636077998 468994259 26184081 8977783267956
"rpc_read" 214 0 0 0 6530761 457767 1831054 8977783237438
"ApmCommandThread" 56 0 0 0 1433898924 0 895629880 8825111423477
"radio-interface" 38 0 0 0 41765899679 4004455570 1961944580 8786906162243
"rpc_read" 4429 0 0 0 192779566 184631377 244141 8779275638536
"rpc-interface" 537 0 0 0 889831583 863678015 41290284 8239455598513
"rpc_read" 535 0 0 0 1028228754 170288083 348480225 8239453920046
"AudioHardwareQSDIn" 9 0 0 0 147654846199 0 32158020026 7760196196386
"proximity" 1 1 0 0 3892520753 0 3892520753 5763470148164
"event1-252" 8 0 0 0 274658 0 91552 5734318414763
"mmc_delayed_work" 3 2 0 0 13576922628 0 8541424561 5511892785725
"msm_camera" 2 0 0 0 12680633542 0 10539916988 5504792504962
"msm_camera_wake" 2 0 0 0 12680633542 0 10539916988 5504792504962
"s5k3e2fx" 2 0 0 0 12293823244 0 10387512209 5504791894611
"flashlight" 1 0 0 0 116271973 0 116271973 5472884484944
"rpc_read" 2 0 0 0 70556639 0 41900634 56937371906
"event2-252" 0 0 0 0 0 0 0 0
"SMD_DATA7" 0 0 0 0 0 0 0 0
"SMD_DATA6" 0 0 0 0 0 0 0 0
"port_list" 0 0 0 0 0 0 0 0
"vbus_present" 0 0 0 0 0 0 0 0
"msm_serial_hs_dma" 0 0 0 0 0 0 0 0
"msm_serial_hs_rx" 0 0 0 0 0 0 0 0
"audiojack" 0 0 0 0 0 0 0 0
"headset" 0 0 0 0 0 0 0 0
"microp_i2c_present" 0 0 0 0 0 0 0 0
"rpc_server" 0 0 0 0 0 0 0 0
"rpc_read" 0 0 0 0 0 0 0 0
"vdec_suspend" 0 0 0 0 0 0 0 0
"vdec_idle" 0 0 0 0 0 0 0 0
"i2c" 0 0 0 0 0 0 0 0
"unknown_wakeups" 0 0 0 0 0 0 0 0
"deleted_wake_locks" 193 0 0 0 117065426 0 32287599 0
"kgsl" 2981 0 0 1068695066 4845796179890 688535376655 128397308351 9725263797740
"PowerManagerService" 1061 0 0 52465057371 7525105867782 1338152315208 5239685516362 96738674
65953
"vbus_present" 2 1 0 740221282954 5984945089112 108139678944 5244723806158 8986111270887
"SMD_DS" 176 176 0 0 103807277355 31379227646 1803994144 9680271884899
#

Unofficial cyanogenmod7.2.0 rc for malata t8 mcc nvflash mode with sod fixed

[only mcc models
First flash ota 20110524 to return at original cwm and do wipe data and wipe partion cache
This will make clean instalation
unrar archivehttp://www.mediafire.com/?adu3kmqhxkb8hfi
run nv flash
go recovery
format system
wipe dalvik cache
mount usb
copy update
copy gapps
copy kernel
flash them with same way
done
lcd density at 120
Stable with pershoot tweaks preload
Major bug have been fixed
Sound improved with beats audio
external sdcard fixed
Sleep fixed
Hd video and mkv video format playable with external. Player like mx video
System improved with init.d tweks
new theme ics
camera work with skype
bravia engine drivers added
set 775 permission system/etc/be photo
set 775 permission system/etc/be movie
Kill app via long press choice will help you
To my daughter Jan
malata t8 unofficial cyanogenmod 7.2.0 RC nvflash mode for mcc device
congratulation goes whyberg for that wonderfull work
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Use at your own risk its not my responsibility if brick your device
download firmware
http://www.mediafire.com/?p66bpjp1qeug6vs
download latest gapps
http://www.mediafire.com/?zglnipcv34kdt49
Click to expand...
Click to collapse
unpacks the archive
includes device "-" + "power" (APX mode)
running the batch file download [1GB | 512MB]
after the device goes into overdrive long press power off
includes device "+" + "power" (recovery mode)
now you must input and export usb cable in & out with usb mount from recovery mode until computer regognize your tablet as storage
copy the update zip and gapps zip into
pour through recovery archive with firmware update-cm-7.2.0-RC0-smb_a9701-KANG-signed.zip & and latest gapps on SDCARD
set after "install from SDcard" both before reboot
Click to expand...
Click to collapse
libcamera.so.ziphttp://forum.xda-developers.com/attachment.php?attachmentid=896892&d=1328950465
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Manual
With root explorer paste libcamera.so into
System/lib and give read write permission as the other
Before reboot
Via recovery(libcamera.so-update.zip)http://forum.xda-developers.com/attachment.php?attachmentid=896903&d=1328951238
Skype 2.6.0.95 version worked!!!
Gtalk video not! but in`s not a camera problem...
Click to expand...
Click to collapse
not working
video accelerator
as all gtablet must install externall video code
like
mxvideo apk
Click to expand...
Click to collapse
Best flash player with this rom is 10.3
Working you tube like a charm
New google play without errors
http://i.minus.com/1331477283/iiYu2AW7DQxVWHgoI7qIbA/dJCxyuh2eNq0W.apk
Click to expand...
Click to collapse
you must be carefull
do not partion sd
do not fix permission
it may brick
enjoy
Click to expand...
Click to collapse

confirmed working!!!!!!!
Thanks geowolf........ youre the man
I'd go as far as to say.... Best Malata zpad t8 rom I've found and was easy to install (as per instructions above you need to install zip files BEFORE first boot)
Shame about no camera. Does anyone know of a fix?
I'm off to 4pda. ru to check for updates

camera fix found
hXXp://cyanogenmod.googlecode.com/issues/attachment?aid=44480005000&name=CM07CameraFix.zip&token=HIEuD7abnRfewkHvEaa8YkZSjZg%3A1328138144361
just copy .so files over /system/lib using root explorer and set permissions same as other files
reboot
install included camera.apk if needed
Happy days

Anything for us poor mcb owners?

Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks

cociuba said:
Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks
Click to expand...
Click to collapse
Hello
There three models mca. Which doesn't use interval memory and was the easy way to upgrade any ron
Mcb its little confuse what type of nand type are use in previous update of official firmware was problem to install mcc nand type sound errors and. Not compatible firmsware
Only if know what type of you use proceed to this
and mcc with interval memory the things are very dangerous .this nvflash regognize your interval memory as SD card and sdcatd turns as emcc folder
Ihave test it to emmc models.
Under the tap of sim card has the type of memory that you use
Open the tap. And has a specification note with numbers
Something like that ( emmc34567886)

i cant find the serial under the gsm tap, is there another posibility of finding it?

cociuba said:
i cant find the serial under the gsm tap, is there another posibility of finding it?
Click to expand...
Click to collapse
At settings
About option
Give a report

Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!

this is the result from using one of the updates for the tablet, it seems that the update uses the emmc.bat
c:\neura\neura [email protected]>download_EMMC_1G.bat
c:\neura\neura [email protected]>"nvflash.exe" --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_ 333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct --setbct --bl bootloader.bin --configfile android_fastboot_emmc_full_more.cfg --odmdata 0x3c0c0011 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411c040a08297
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file:Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct - 4080/4080 bytes sent
Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct sent successfully
odm data: 0x3c0c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
945472/945472 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Click to expand...
Click to collapse
EE

bungadudu said:
Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!
Click to expand...
Click to collapse
One more
Is rooted ?
If open root directory with root explorer is any directory like emmc. emmb ....
China Malata 3g models are mmc
But Russian 3q models has been moderate with erricson 3g spare even are, or not 3g
Maybe and the Romanian models has been modified
With 3g
Try with root explorer to find mount points
And from market android system info has an option to find mount points
Check it out .
Its to early for ice cream

cant find the mount points but I attached diskstat and partition file
diskstat
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
179 48 mmcblk3 17433 44474 1532199 120670 136737 577806 3635982 18924640 0 1974930 19139480
179 49 mmcblk3p1 4495 282 286484 26080 3 0 6 20 0 15010 26080
179 50 mmcblk3p2 12 61 290 10 133 6864 27988 57350 0 11350 57360
179 51 mmcblk3p3 9 61 278 20 8 1 36 550 0 550 570
179 52 mmcblk3p4 0 0 0 0 0 0 0 0 0 0 0
179 53 mmcblk3p5 0 0 0 0 0 0 0 0 0 0 0
179 54 mmcblk3p6 9475 27970 846506 75240 115761 534552 2610508 14212670 0 1796540 14288720
179 55 mmcblk3p7 5 0 10 10 0 0 0 0 0 10 10
179 56 mmcblk3p8 3432 16100 398591 19310 20832 36389 997444 4654050 0 276190 4766740
254 0 dm-0 40 0 1066 340 0 0 0 0 0 130 340
254 1 dm-1 805 0 74867 14710 0 0 0 0 0 7710 14710
254 2 dm-2 34 0 478 30 0 0 0 0 0 30 30
254 3 dm-3 406 0 37090 4450 0 0 0 0 0 2180 4450
254 4 dm-4 80 0 6210 1040 0 0 0 0 0 330 1040
254 5 dm-5 118 0 6850 3190 0 0 0 0 0 810 3190
254 6 dm-6 635 0 47366 5750 0 0 0 0 0 2640 5750
Click to expand...
Click to collapse
partition
major minor #blocks name
7 0 2111 loop0
7 1 48888 loop1
7 2 2111 loop2
7 3 30177 loop3
7 4 4190 loop4
7 5 7308 loop5
7 6 24980 loop6
179 48 15648768 mmcblk3
179 49 327680 mmcblk3p1
179 50 65536 mmcblk3p2
179 51 32768 mmcblk3p3
179 52 1 mmcblk3p4
179 53 32768 mmcblk3p5
179 54 2097152 mmcblk3p6
179 55 8192 mmcblk3p7
179 56 13081600 mmcblk3p8
254 0 2110 dm-0
254 1 48888 dm-1
254 2 2110 dm-2
254 3 30177 dm-3
254 4 4189 dm-4
254 5 7308 dm-5
254 6 24979 dm-6
Click to expand...
Click to collapse

cociuba said:
cant find the mount points but I attached diskstat and partition file
diskstat
partition
Click to expand...
Click to collapse
The most important is that previous update you use was emmc

ok, so I can use your build?
if yes please explain one more time the steps, thanks.
also is it possible to use clockworkmod? or how can i make a backup of the rom that I am using

Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english

@whyberg -does gsm work?

cociuba said:
@whyberg -does gsm work?
Click to expand...
Click to collapse
voice? i don't know, F3607gw can't support voice calls
gprs/edge/umts data worked well

whyberg said:
Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english
Click to expand...
Click to collapse
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...

I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?

geowolf1000 said:
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...
Click to expand...
Click to collapse
View attachment libcamera.so.zip
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Via recovery(View attachment libcamera.so-update.zip)
Skype from market last version worked!!!
Gtalk video not! but in`s not a camera problem...
cociuba said:
I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?
Click to expand...
Click to collapse
Download stock rom from hardware developer website and reinstall it
What device you have?
My working computer under debian

[Q] Android Wallpaper Service on Nook Simple Touch (the removal of)

Hi all,
On a Nook Simple Touch (E-ink reader), there is a service I am unable to locate and delete.
The details:
Code:
Label: Android System
Name: system
Flags: PERSISTENT, SYSTEM
Clients: I
Package: android
Pack. label: Wallpaper
Pack. details: android/com.android.internal.service.wallpaper.ImageWallpaper
While I accept that the system requires resources, this service degrades the performance of the e-reader every now and then to irritatingly slow levels. When it is persistently using CPU time, the screen is very noticeably unresponsive, perhaps once a day or so.
grep reports that this service is a "Default built-in wallpaper that simply shows a static image. "
Added to the rather odd fact that I do not recall having a wallpaper beyond a sheet of white, which I would gladly sacrifice in return for a reliably responsive system.
I additionally don't know how a wallpaper service takes almost more memory than my web browser.
I have been unable to locate documentation on this service, what it does, where it resides and how to disable it.
If anyone could provide any insight on this service, it would be greatly appreciated.
Thanks
(tl;dr: Android's imagewallpaper service uses more RAM/CPU than a web browser, and I would like to kill it or understand why)

The service you mention is the default and very simple implementation of a WallpaperService.
Basically, it gets an intent to use a drawable as a background and draws it when needed.
It really should not be using any CPU or memory.

But it is, and using 10-20% of CPU and about a quarter of my RAM.
How would one go about diagnosing the root cause, and subsequently disabling it?
I tried 'pm disable servicename' but it only shifted the exact same CPU and RAM usage to the Google checkin service, and after I disabled that, to the Android system itself.
What might be causing this?

Where are you getting these statistics from?
Are you getting these statistics over ADB without an app running?
What are you using for a launcher?
Do you have any widgets on the desktop?
What does logcat say?
What does ps say?

Renate NST said:
Where are you getting these statistics from?
Click to expand...
Click to collapse
From the task manager built into Relaunch (nookdevs . com/ReLaunch), a barebones file manager/launcher without animations nor wallpaper.
Renate NST said:
Are you getting these statistics over ADB without an app running?
Click to expand...
Click to collapse
This is persistent over a week-long period of regular usage, as in, the resource consumption is constant regardless of what I am doing with the device (ie. fresh boot, web browser, reading).
I am unaware of the command to pull these statistics over ADB, though I suspect they will be similar.
Renate NST said:
What are you using for a launcher?
Click to expand...
Click to collapse
Relaunch (nookdevs . com/ReLaunch)
Written for the Nook, spartan feature set includes only file manager, basic app selection, wifi and battery information.
UI is simplistic, about what you'd expect from a file manager.
No animations.
Renate NST said:
Do you have any widgets on the desktop?
Click to expand...
Click to collapse
I have a listing of files in the current directory, beyond that nothing.
Renate NST said:
What does logcat say?
Click to expand...
Click to collapse
pastebin . com/j4EWAH0R
(Does not seem to have anything relevant, but the lagging problems only manifest themselves once a day or so.)
Renate NST said:
What does ps say?
Click to expand...
Click to collapse
Code:
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 552 248 c00d4988 0000d6cc S /init
root 2 0 0 0 c0078ee4 00000000 S kthreadd
root 3 2 0 0 c006925c 00000000 S ksoftirqd/0
root 4 2 0 0 c0090d48 00000000 S watchdog/0
root 5 2 0 0 c0075624 00000000 S events/0
root 6 2 0 0 c0075624 00000000 S khelper
root 12 2 0 0 c0075624 00000000 S suspend
root 127 2 0 0 c0075624 00000000 S kblockd/0
root 133 2 0 0 c0075624 00000000 S cqueue
root 143 2 0 0 c0075624 00000000 S twl4030-irqchip
root 144 2 0 0 c01a4b54 00000000 S twl4030-irq
root 170 2 0 0 c0075624 00000000 S omap2_mcspi
root 177 2 0 0 c0075624 00000000 S ksuspend_usbd
root 182 2 0 0 c01df4e4 00000000 S khubd
root 187 2 0 0 c0075624 00000000 S kmmcd
root 218 2 0 0 c00a573c 00000000 S pdflush
root 219 2 0 0 c00a573c 00000000 S pdflush
root 220 2 0 0 c00aa36c 00000000 S kswapd0
root 222 2 0 0 c0075624 00000000 S aio/0
root 230 2 0 0 c0075624 00000000 S epd-su/0
root 231 2 0 0 c0075624 00000000 S epd-dspck/0
root 371 2 0 0 c01f7818 00000000 S usb_mass_storag
root 385 2 0 0 c0075624 00000000 S zforce_wq
root 404 2 0 0 c0075624 00000000 S kondemand/0
root 416 2 0 0 c0075624 00000000 S hid_compat
root 485 2 0 0 c0215cb8 00000000 S mmcqd
root 716 2 0 0 c0215cb8 00000000 S mmcqd
root 720 2 0 0 c012dcdc 00000000 S kjournald
root 724 2 0 0 c012dcdc 00000000 S kjournald
root 725 1 700 276 c017e784 afe0c74c S /system/bin/sh
root 728 1 836 360 c00d4988 afe0cb14 S /system/bin/OMXPolicyManager
root 729 1 1900 360 ffffffff afe0c7ec S /system/bin/OMXResourceManager
root 734 1 216 64 c007dd0c 0001413c S /system/bin/bridged
system 735 1 764 264 c022646c afe0c9ec S /system/bin/servicemanager
root 737 1 816 400 c00d4988 afe0cb14 S /system/bin/vold
root 738 1 628 244 c0248ce4 afe0d37c S /system/bin/debuggerd
root 740 1 171004 8552 c00d4988 afe0cb14 S zygote
media 741 1 28516 1820 ffffffff afe0c9ec S /system/bin/mediaserver
bluetooth 742 1 1068 348 c00d4988 bef345b4 S /system/bin/dbusdaemon
root 743 1 756 328 c02ab6e8 afe0c74c S /system/bin/installd
keystore 746 1 1600 272 c0248ce4 afe0d37c S /system/bin/keystore
root 754 2 0 0 c0075624 00000000 S pvr_timer/0
root 782 2 0 0 c0075624 00000000 S pvr_workqueue
root 790 1 16832 12172 c016e7e8 afe0c74c S /system/bin/omap-edpd.elf
system 810 740 353844 54808 ffffffff afe0c9ec S system_server
root 820 2 0 0 c0075624 00000000 S pvr_display_syn
system 1003 740 258112 16916 ffffffff afe0d974 S com.android.settings
root 1008 2 0 0 c0075624 00000000 S sdio_wq
root 1015 2 0 0 c0075624 00000000 S tiwlan_wq
wifi 1032 1 1988 668 c00d4988 afe0cb14 S /system/bin/wpa_supplicant
app_2 1043 740 245724 12396 ffffffff afe0d974 S com.android.inputmethod.latin
app_3 1108 740 249840 11984 ffffffff afe0d974 S com.bn.cloud.svc:svc
system 1134 740 252272 18352 ffffffff afe0d974 S com.bn.devicemanager
system 1181 740 261060 10192 ffffffff afe0d974 S com.bn.waveformdownloader.svc
app_22 1201 740 249236 11240 ffffffff afe0d974 S com.android.vending
app_23 1558 740 308052 62676 ffffffff afe0d974 S com.UCMobile
app_29 1742 740 253832 15392 ffffffff afe0d974 S com.eink.norefresh
app_29 1756 1742 636 344 c0227544 afe0c74c S /system/bin/logcat
app_34 3105 740 259656 21560 ffffffff afe0d974 S com.harasoft.relaunch
dhcp 3173 1 304 164 c00d4988 0000ee6c S /system/bin/dhcpcd
app_30 3247 740 250176 15752 ffffffff afe0d974 S siir.es.adbWireless
root 3289 1 3372 184 ffffffff 0000f444 S /sbin/adbd
root 3369 3289 700 328 c017e784 afe0c74c S /system/bin/sh
root 3370 3289 636 344 c0227544 afe0c74c S logcat
app_17 3395 740 251488 11776 ffffffff afe0d974 S com.google.process.gapps
app_20 3413 740 244860 10292 ffffffff afe0d974 S com.android.setupwizard
root 3442 3289 700 328 c0066b58 afe0d61c S /system/bin/sh
root 3446 3442 844 340 00000000 afe0c74c R ps
Thanks
Edit: The PID/UID of the problematic process is 810/1000, which corresponds to "system 810 740 353844 54808 ffffffff afe0c9ec S system_server" from the ps result. I'm searching for insight on system_server.

Thanks, oops, sorry. I meant to say "top".
If you are running something that displays stats constantly it could be causing the wallpaper to constantly redraw.
Try a top from ADB, I'm sure that it will show zero usage.
You do have some wackiness going on in your logcat.
The UMSServer is going crazy. Is there a problem with your SD card?

Cross-referencing the PID with the processes reported in the task manager appears to point the issue at "system_server"
I'm not sure of the relevance of this, but it appears other Android devices have encountered issues with this particular process, with symptoms similar to mine.
However, their solutions (disabling GPS, replacing 'system_server' with its 2.3/4.0 counterpart) do not seem to apply, or cause more issues in this case.
The UMS messages only show up during physical USB connection, not during logcat when there is only a wireless connection, so it should be unrelated.
Could you clarify 'top'?
Your explanation makes sense, but it doesn't fully explain why the system slows to a crawl for about ten to twenty minutes out of the blue every now and then, seemingly caused by this process.
However, this may just be an unrelated factor.
I have, in my search for what 'system_server' does, discovered what happens if you replace said file with its 2.3/4.0 counterpart, should anyone wish to know.
Regular functions are unaffected, resource usage by the process is slightly diminished, however the tablet is unable to wake from sleep.
Additionally, removing most of the Google and B&N system services has somewhat circumvented the issue.
Thanks for your help, by the way, wouldn't have gotten past the whole figuring out what ImageWallpaper was without it.

I looked at the code for UMSServerActivity quickly and jumped to the conclusion that it was for mounting of the SD card.
It's actually the USB Mass Storage mounter.
I looked at logcat with a USB drive plugged in and I don't get any of those messages that you have.
From a shell in ADB:
Code:
# top
User 0%, System 0%, IOW 0%, IRQ 0%
User 3 + Nice 0 + Sys 1 + Idle 300 + IOW 0 + IRQ 0 + SIRQ 0 = 304
PID CPU% S #THR VSS RSS PCY UID Name
24453 0% R 1 876K 388K fg root top
2 0% S 1 0K 0K fg root kthreadd
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K unk root watchdog/0
and so on for another 50 lines...

There is a somewhat more pressing issue, is there a way to have Android save logcat data automatically regardless of system state and ADB connection?
Right now it only has ADB over wifi, which is terminated soon after the device sleeps.
The reason I ask is that right now if I leave it for too long it refuses to wake up, I assumed this was an issue with the replacement of "system_server" in "/system/bin/", as the reverting those changes initially did away with the problem, but it just manifested itself twice over the span of five minutes and I'd like to track
down the source.
Thanks

aliastral said:
I assumed this was an issue with the replacement of "system_server" in "/system/bin/"
Click to expand...
Click to collapse
Um, if you start indiscriminately swapping out system parts you are bound to cause wackiness.
For example: I've been having problems with "mediaserver".
It crashes all the time, but what is in /system/bin/mediaserver is just a stub that gets a bunch of processes running.
I wouldn't think of trying to swap out /system/bin/mediaserver.
The problem probably lies in a bug in one of the audio libraries in /system/lib

Android N beta, big cores always sleeping.

There is a bug with the latest android N, only the little cores seems to work. You can check it with cpu-z and a stress test.
Also, more info here: https://code.google.com/p/android/i...porter Opened&groupby=&sort=-opened&id=206819

Do you think this will be a quick patch or stay like it until the next developer preview?

It's stil a beta, maybe there will be a patch or in the next preview...the performance overall isnt that affected. You can also change the kernel .

Enrolled in beta last night did OTA to N will check cpu z see if same battery life still sucks 6am - 1:30pm and 17% left ?
Sent from my Nexus 5X using Tapatalk

i don't have this bug i don't know why
i ceched it with elemental x app

I don't have this issue either. All six cores running properly.

took the OTA from DP2 to DP3 and can confirm its happening to me too. i'll try installing the system image and see if that fixes it.

I'm not sure this is a problem with N but rather a problem with the apps you're using to measure the CPU cores themselves.
There's a command: adb shell cat /proc/stat
Type that in terminal with your phone connected and check it out
Now i'm no wiz at android or anything, but the columns it gives back are readings of how long the cpu cores have spent in certain states.
The meanings of the columns are as follows, from left to right:
user: normal processes executing in user mode
nice: niced processes executing in user mode
system: processes executing in kernel mode
idle: twiddling thumbs
iowait: waiting for I/O to complete
irq: servicing interrupts
softirq: servicing softirqs
Tayos-Mac-Pro:~ TayoOnabule$ adb shell cat /proc/stat
cpu 29779 16626 40322 263858 3638 5754 3666 0 0 0
cpu0 11365 9362 17248 101562 2611 2185 1182 0 0 0
cpu1 6731 3452 9271 30395 319 846 700 0 0 0
cpu2 6258 2891 7887 31142 243 708 572 0 0 0
cpu3 1245 391 3335 33573 216 458 469 0 0 0
cpu4 2344 377 1433 33444 130 1422 299 0 0 0
cpu5 1834 150 1146 33740 116 133 440 0 0 0
intr 2777034 0 3 0 3 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 618895 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 96044 0 0 0 0 0 0 0 343 0 0 136 0 0 0 0 0 2236 2 5 0 0 0 0 0 12538 0 0 0 0 0 0 0 0 0 0 274 0 0 0 0 2 416 2 0 2 0 0 0 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22521 0 0 0 0 0 0 0 0 0 0 0 0 26715 0 0 0 112 12660 0 346 0 25 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 381885 0 0 0 0 0 0 0 1413 0 0 0 0 0 0 1011 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12595 0 6 0 0 0 0 20317 7011 0 0 0 121135 0 0 1141 0 0 0 0 0 0 0 0 1 0 0 14757 619 0 0 0 0 0 548 0 1839 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6983 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9189 0 0 0 0 52677 0 0 0 0 0 0 288 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 529 26 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 94 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 21 0 0 0 0 0 0 0 0 0 0 0 303 0 0 0 0 292 0 2147 3 66 509 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 341 3643 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 131 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 161 0 0 0 0 0 0 0
ctxt 5896731
btime 1463686046
processes 11422
procs_running 1
procs_blocked 0
softirq 1957987 1198 375954 3331 23764 1198 1198 288344 370196 1092 891712
Tayos-Mac-Pro:~ TayoOnabule$
Click to expand...
Click to collapse
Edit: I also can't see the big cores working in CPU-Z, but doing this command it is obvious that they are actually working... apart from anything else N is so buttery smooth they must be working

/proc/stat actually shows that the 2 big cores are working. Cpu-z or cpu-x seem slow (or even fail) to update core speed. Try same with Antutu's cpu info (Info > cpu info > more) or tinycore (cpu profil, system info) and run a cpu heavy task that doesn't get low priority or stops when in background. Both should show actual values while on cpu-z/-x the big cores are still marked sleeping/stopped.

Are you sure this isn't thermal throttling? After the image first installed the cores temp was too high so it throttled the large cores off... once temps stabilized the big cores came back online. I think this is just a CPUZ bug to be honest.

It's just CPU-Z.
You can't expect every application to function properly on developer previews.

What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk

DoobyDroid said:
What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I can answer that one! just go back to the enrol page and click unroll device from beta your phone will receive a ota for latest build , unfortunately its a wipe so back up important tack first.........

Yeah my Android N is rooted i use kernel auditor with the stock supersu kernel and it shows cores working.

very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline

meisking1 said:
very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline
Click to expand...
Click to collapse
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
{
"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"
}
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.

Joms_US said:
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.
Click to expand...
Click to collapse
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running

meisking1 said:
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running
Click to expand...
Click to collapse
CPU stats does for me.
On stock system thermal throttling kicks in early and big cores are meant as short time boosts not permanent speed up. So you'll see relatively little use anyway

The animations of Android N in slowmotion
http://www.bitfeed.co/page/the-animations-of-android-n-in-slowmotion-video