Database Users

USB Driver for Galaxy S and Misc Info

Taken from http://forums.hardwarezone.com.sg/showthread.php?t=2806456
For those that do not want to download Kies, here is the driver. I did not try others except I know it works on Win7 x64
http://db.tt/ErGVyE
deckcard said:
Galaxy S Meminfo
Code:
MemTotal: 333416 kB
MemFree: 28220 kB
Buffers: 5700 kB
Cached: 112080 kB
SwapCached: 0 kB
Active: 92292 kB
Inactive: 165804 kB
Active(anon): 48956 kB
Inactive(anon): 92160 kB
Active(file): 43336 kB
Inactive(file): 73644 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 140336 kB
Mapped: 55228 kB
Slab: 13220 kB
SReclaimable: 3240 kB
SUnreclaim: 9980 kB
PageTables: 11976 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 166708 kB
Committed_AS: 7187348 kB
VmallocTotal: 286720 kB
VmallocUsed: 78580 kB
VmallocChunk: 154628 kB
Click to expand...
Click to collapse
deckcard said:
Galaxy S mountpoints
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse

/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
huh !?!?! /system mount in rw mode ? does this mean that no need to root?

worldicez said:
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
huh !?!?! /system mount in rw mode ? does this mean that no need to root?
Click to expand...
Click to collapse
born to be RW !? wow!

That link just tells me they don't have a revision history for the file?
If I use the original link, I just don't see how where I get an actual download link!?!?
Please help

some mirrors:
http://www.multiupload.com/A3VUGCKIIJ

u can find the drivers here:
http://forums.hardwarezone.com.sg/showthread.php?t=2812085

hmmm.. or you can extract the contents of the latest Kies application from the Samsung website using 7zip and save it on your computer.
..check the folders and you will see there a folder which contains the "USB driver".. copy that folder and save it someone.. as for the rest you can safely delete them.
.. that is what I did before.. Kies is to laggy for me and takes a long time to respond/load.. "drag and drop" works wonders for me.
**note: you must enable "show hidden.." from folder options so that you will be able to see the Appdata.. haven't tried directly typing on the adrress bar the direct location.. "C:\Users\<user account name>\AppData\Local\Temp\Samsung\"..
**oh yeah.. this is for Windows 7.. should be the same for Vista i guess.
{
"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"
}

SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1600.0.exe
http://www.multiupload.com/ZQIEJHSRSI
this is from the samsung kies_win.exe package released on 2010/11/11
works with Win7 x64

Thank you, fixed my [nearly] bricked Captivate!

convert ztjp8 stock rom to ext4

FLASH STOCK ROM then overcome kernel 3.1.0
it works
Sent from my GT-I9100 using XDA App

serious , how you make it work ? ?
Edit : i was kidding with ya ... perhaps , i don't know what i say ..

compare eur jq1 initramfs with jp8 just little different
it just works
Sent from my GT-I9100 using XDA App

owh that is so new !!!!!!

screen capture
{
"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"
}

we need "Microscope" to look at it .. btw what you posted is not new !!!! perhaps for some other ppl ...

simple howto - no guarantee. try at your own risks
Get P1000ZTJP8 ## http://www.samfirmware.com/WEBPROTECT-p1000.htm
Unrar the file downloaded and get the gt-p1000_mr.pit and P1000ZTJP8_P1000ZTJP5_P1000BRIJP8_HOME.tar inside
flash stock rom with re-partition using Odin3 (repeat once more if you install http://forum.xda-developers.com/showthread.php?t=1074759 Overcome ROM v2.0.1 Hermes before to make it really clean)
download Overcome Kernel V3.1.0 http://overcome.mimzo.com/wp-content/plugins/download-monitor/download.php?id=4
Heimdall flash the zImage inside. Be patient but there are some voice telling you the progress and it can take few minutes
Cons:
Try at your own risks and no guarantee
As expected most Overcome features will not work
Pros:
Has Superuser
Quandrant rating is 1567
ext4 mount
Code:
$ mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 ro,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=12288k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /preload vfat ro,nodev,noatime,nodiratime,fmask=0133,dmask=0022,codepage=cp437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gi
d=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf
8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime
,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=10
00,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixe
d,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

some hard work . really

[Q] sdcard not mounted in recovery

Galaxy Tab 10.1 GT-P7510 32GB, stock, not yet rooted
kernel: #1 SMP PREEMPT Mon Jun 6 08:59:10 KST 2011
PDA: KF3, phone: KF3; CSC: KF3 (XAB)
Starting down the path to root the phone, I encounter an issue that I haven't seen on the fora.
If I boot to recovery, I get to menu about "reboot system now", "apply update from /sdcard" and so on, but if I pick "apply update from /sdcard" it can't find what I've put in /sdcard. I get an error "E: unknown volume for path [/sdcard]".
While in this recovery state, if I adb shell, do "mount", I see that nothing is mounted on /mnt/sdcard:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk0p4 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
In normal running state, if I adb shell "mount" I get:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm quite surprised that /mnt/sdcard is not mounted in a mode where it's supposed to be able to do update.zip things from there.
Am I being stupid? (No surprise if that turns out to be the case.)
--bogoid

I am having the exact same issue with my Galaxy Tab 10.1. Anyone help would be greatly appreciated.
Adam

Ditto - have you guys found a fix yet?

Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING

msm903 said:
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
Click to expand...
Click to collapse
That did the trick! Thank you!

Galaxy Camera Voodoo Report :)

This is a Galaxy Camera. This device has not been releaed yet.
{
"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"
}
I managed to set up a wifi hot spot on my galaxy Nexus, connect the Galaxy Camera to the wifi hotspot, then log in with my google account, then get voodoo report. I emailed it to myself and then came back to the hotel to get on a computer and upload it. Please enjoy
http://forum.xda-developers.com/attachment.php?attachmentid=1417104&stc=1&d=1350751053

I was able to take a look at some of the things that interest me today.
Kernel Version: Linux version 3.0.31-338593 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Tue Oct 16 07:50:58 KST 2012
dhd 425998 0 - Live 0x00000000
btlock 1576 0 - Live 0x00000000
exfat_fs 17079 0 - Live 0x00000000 (P)
exfat_core 59635 1 exfat_fs, Live 0x00000000 (P)
Specs:
Width: 720
Height: 1184
Refresh rate: 60.003
Pixel Format: 5
3.97G Internal Storage
Processor information
Code:
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1592.52
processor : 1
BogoMIPS : 2786.91
processor : 2
BogoMIPS : 2786.91
processor : 3
BogoMIPS : 2786.91
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
Chip revision : 0011
Hardware : SMDK4x12
Revision : 000b
Serial : defd8f4f4790b1b8
Sensors:
Code:
Accelerometer:
vendor: STMicroelectronics
name: LSM330DLC 3-axis Accelerometer
Magnetic field:
vendor: Asahi Kasei Microdevices
name: AK8963C 3-axis Magnetic field sensor
Orientation:
vendor: STMicroelectronics
name: iNemoEngine Orientation sensor
Gyroscope:
vendor: STMicroelectronics
name: LSM330DLC Gyroscope sensor
Gravity:
vendor: STMicroelectronics
name: iNemoEngine Gravity sensor
Linear acceleration:
vendor: STMicroelectronics
name: iNemoEngine Linear Acceleration sensor
Rotation vector:
vendor: STMicroelectronics
name: iNemoEngine Rotation_Vector sensor
Rotation vector:
vendor: Google Inc.
name: Rotation Vector Sensor
Gravity:
vendor: Google Inc.
name: Gravity Sensor
Linear acceleration:
vendor: Google Inc.
name: Linear Acceleration Sensor
Orientation:
vendor: Samsung Inc.
name: Orientation Sensor
Gyroscope:
vendor: Google Inc.
name: Corrected Gyroscope Sensor
looks like a International Galaxy S3.
Mounts:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /tdata ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Looks Cool!
So it's an Exynos?
If it has 3G can you make calls with it??

The trick is that, AFAIK, calls are blocked in SW. While HW is probably fully capable of doing them.

E:V:A said:
Looks Cool!
So it's an Exynos?
If it has 3G can you make calls with it??
Click to expand...
Click to collapse
I added that image to the OP so there's no confusion.
I'm so anticipating this device!

Rebellos said:
The trick is that, AFAIK, calls are blocked in SW. While HW is probably fully capable of doing them.
Click to expand...
Click to collapse
Great, so let's not talk about that any more over here...before they actually release this thing.

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