[CLOSED][APP][2.1+] DiskInfo

Status
Not open for further replies.
Search This thread
By:
Advanced…
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
sordna said:
I noticed one peculiar thing though, the cache, system, and data aliases are displayed capitalized (Cache, System, Data) why is that?
Shouldn't the alias be displayed in the same name and case as the symlink file in the by-name directory ?
Click to expand...
Click to collapse

Good catch ;) They are capitalized because this is how it worked before I introduced the aliases from by-name directory. Now it may make more sense to not capitalize or leave it up to user via settings. I'll think about it. Thanks.
 
sordna

sordna

Senior Member
Dec 12, 2012
1,262
647
M.Q. said:
Good catch ;) They are capitalized because this is how it worked before I introduced the aliases from by-name directory. Now it may make more sense to not capitalize or leave it up to user via settings. I'll think about it. Thanks.
Click to expand...
Click to collapse

I wouldn't put a setting for it, it seems overkill to let the user decide the first letter capitalization :)

BTW on an older samsung captivate phone I noticed it has 2 platform directories, xxx.2 and xxx.3 (I forget the platform name) where xxx.2 only had by-num and xxx.3 had both by-num and by-name. Just letting you know.
I don't think your app found the aliases (they were all 2 letter aliases by the way).
So there could be a worst case with some device potentially having 2 or more directories that also have by-name, would you have a way to tell which one to choose? The previous case is easier, if multiple platforms, pick the platform that has by-name in it.
 
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
sordna said:
I wouldn't put a setting for it, it seems overkill to let the user decide the first letter capitalization :)
Click to expand...
Click to collapse
Yes, right - that would be an overkill :)
sordna said:
BTW on an older samsung captivate phone I noticed it has 2 platform directories, xxx.2 and xxx.3 (I forget the platform name) where xxx.2 only had by-num and xxx.3 had both by-num and by-name. Just letting you know.
I don't think your app found the aliases (they were all 2 letter aliases by the way).
So there could be a worst case with some device potentially having 2 or more directories that also have by-name, would you have a way to tell which one to choose? The previous case is easier, if multiple platforms, pick the platform that has by-name in it.
Click to expand...
Click to collapse
Right, there are cases with more than one subdirectories in /dev/block/platform - e.g. if you use a usb drive via usbhub that it is shown in a separate subdirectory. Anyway, my app reads them all so as long as they include by-name, it shall be able to get aliases.
I'm not sure why my app did not found the 2 letter aliases. I can send you a version with logging enable and we can try to debug it if you want.
 
sordna

sordna

Senior Member
Dec 12, 2012
1,262
647
M.Q. said:
Yes, right - that would be an overkill :)

Right, there are cases with more than one subdirectories in /dev/block/platform - e.g. if you use a usb drive via usbhub that it is shown in a separate subdirectory. Anyway, my app reads them all so as long as they include by-name, it shall be able to get aliases.
I'm not sure why my app did not found the 2 letter aliases. I can send you a version with logging enable and we can try to debug it if you want.
Click to expand...
Click to collapse

Sure, I'll be happy to run a debug version, if you like. Here's what I see in the filesystem, and further down is screenshot of the Diskinfo 4.1 output missing the aliases:

Code: 
app_118@android:/dev/block/platform $ ls -lR

.:
drwxr-xr-x root     root              2013-08-18 19:47 sdhci-tegra.2
drwxr-xr-x root     root              2013-08-18 19:47 sdhci-tegra.3

./sdhci-tegra.2:
drwxr-xr-x root     root              2013-08-18 19:47 by-num
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk1p1 -> /dev/block/mmcblk1p1

./sdhci-tegra.2/by-num:
lrwxrwxrwx root     root              2013-08-18 19:47 p1 -> /dev/block/mmcblk1p1

./sdhci-tegra.3:
drwxr-xr-x root     root              2013-08-18 19:47 by-name
drwxr-xr-x root     root              2013-08-18 19:47 by-num
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-08-18 19:47 mmcblk0p9 -> /dev/block/mmcblk0p9

./sdhci-tegra.3/by-name:
lrwxrwxrwx root     root              2013-08-18 19:47 AP -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-08-18 19:47 CC -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-08-18 19:47 ES -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-08-18 19:47 HD -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-08-18 19:47 IS -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-08-18 19:47 LX -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2013-08-18 19:47 MC -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-08-18 19:47 MM -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-08-18 19:47 OA -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-08-18 19:47 SS -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-08-18 19:47 UA -> /dev/block/mmcblk0p6

./sdhci-tegra.3/by-num:
lrwxrwxrwx root     root              2013-08-18 19:47 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-08-18 19:47 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-08-18 19:47 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-08-18 19:47 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-08-18 19:47 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-08-18 19:47 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-08-18 19:47 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-08-18 19:47 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2013-08-18 19:47 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-08-18 19:47 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-08-18 19:47 p9 -> /dev/block/mmcblk0p9
app_118@android:/dev/block/platform $
 

Attachments

  • di_samsung.jpg
    di_samsung.jpg
    77.7 KB · Views: 201
K

killoid

Senior Member
Feb 5, 2013
1,266
442
in the settings,the options r shown 2x time! i mean after 'troubleshooting' ,it again showing the same options again from the 1st line as 'row display preferences,partition filter' etc. :confused:
 
Neejay

Neejay

Senior Member
Jul 29, 2009
1,016
148
Atlanta, GA
Maguro here. I get a force close now, free version.

I tried clearing app data as well, to no avail.

logcat:

Code: 
I/ActivityManager(  459): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000
 cmp=me.kuder.diskinfo/.ItemListActivity} from pid 10962
I/ActivityManager(  459): Start proc me.kuder.diskinfo for activity me.kuder.diskinfo/.ItemListActivity: pid=18230 uid=1
0157 gids={50157, 1028}
D/AndroidRuntime(18230): Shutting down VM
W/dalvikvm(18230): threadid=1: thread exiting with uncaught exception (group=0x41fbd700)
E/AndroidRuntime(18230): FATAL EXCEPTION: main
E/AndroidRuntime(18230): java.lang.RuntimeException: Unable to start activity ComponentInfo{me.kuder.diskinfo/me.kuder.d
iskinfo.ItemListActivity}: java.lang.RuntimeException: java.lang.NoSuchMethodException: <init> [class android.app.Activi
ty, int]
E/AndroidRuntime(18230):        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2350)
E/AndroidRuntime(18230):        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2400)
E/AndroidRuntime(18230):        at android.app.ActivityThread.access$600(ActivityThread.java:153)
E/AndroidRuntime(18230):        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1269)
E/AndroidRuntime(18230):        at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18230):        at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(18230):        at android.app.ActivityThread.main(ActivityThread.java:5295)
E/AndroidRuntime(18230):        at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18230):        at java.lang.reflect.Method.invoke(Method.java:525)
E/AndroidRuntime(18230):        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
E/AndroidRuntime(18230):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:555)
E/AndroidRuntime(18230):        at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:112)
E/AndroidRuntime(18230):        at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18230): Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: <init> [class android.a
pp.Activity, int]
E/AndroidRuntime(18230):        at com.actionbarsherlock.a.a(Unknown Source)
E/AndroidRuntime(18230):        at com.actionbarsherlock.a.f.g(Unknown Source)
E/AndroidRuntime(18230):        at com.actionbarsherlock.a.f.setContentView(Unknown Source)
E/AndroidRuntime(18230):        at me.kuder.diskinfo.ItemListActivity.k(Unknown Source)
E/AndroidRuntime(18230):        at me.kuder.diskinfo.ItemListActivity.onCreate(Unknown Source)
E/AndroidRuntime(18230):        at android.app.Activity.performCreate(Activity.java:5271)
E/AndroidRuntime(18230):        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime(18230):        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2304)
E/AndroidRuntime(18230):        ... 12 more
E/AndroidRuntime(18230): Caused by: java.lang.NoSuchMethodException: <init> [class android.app.Activity, int]
E/AndroidRuntime(18230):        at java.lang.Class.getConstructorOrMethod(Class.java:423)
E/AndroidRuntime(18230):        at java.lang.Class.getConstructor(Class.java:397)
E/AndroidRuntime(18230):        ... 20 more
W/ActivityManager(  459):   Force finishing activity me.kuder.diskinfo/.ItemListActivity
W/ActivityManager(  459): Activity pause timeout for ActivityRecord{435e72a0 u0 me.kuder.diskinfo/.ItemListActivity}
I/Process (18230): Sending signal. PID: 18230 SIG: 9
I/ActivityManager(  459): Process me.kuder.diskinfo (pid 18230) has died.
 
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
Neejay said:
Maguro here. I get a force close now, free version.
Click to expand...
Click to collapse
Thanks for reporting.
The fix is already published - v.4.3.1
It turned out that after updating to newest Android Studio, somehow the wrong proguard settings have been used to make an apk. Sorry about that.


Sent from my NexusHD2 using Tapatalk 4
 
F

Firepsychcan

New member
Apr 4, 2014
1
0
Shows internal SD card as unmounted

Hi
Installed the free version to try it out on my Asus Memo HD 7 tablet. I like the programme, but it show my internal SD card as unmounted. I can access this drive with many other programmes (e.g., Device Storage Analyzer) with no problem, but it doesn't show up unless I choose the option of displaying an unmounted drive. Not sure what is wrong. Can this be fixed?
 
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
There is a new version available. Few bugs have been fixed (including the one described in the previous post), also added more details of swap (swappiness, etc.)

Sent from my Nexus 7 using Tapatalk
 
  • Like
Reactions: Firepsychcan and sordna
R

RogerInCH

New member
Jun 10, 2014
1
0
Diskinfo PRO Not convenient for Android 4.4.2

Diskinfo Pro runs under Android 4.3 without problem. It's marvellous.

BUT under 4.4.2, it does not recognize the extSdCard first partition (fat32). It recognizes the second partition (ext4 format).

My Note 2 is rooted. I use SDFix. For information, under same conditions, the application "App Backup & Restore" gives an error message: "No removable storage mounted". Once the backup path has been entered, it runs correctly but don't save the new backup path : storage/extSdCard/App_Backup_Restore.

This application is wonderful but we need and upgrade for KitKat.

Thanks.
 
Chucktr

Chucktr

Senior Member
Oct 4, 2012
445
345
Glendale, AZ
www.trcompu.com
Shared memory

Hi there,
I became the new OP for the HTC Rezound and we have a problem. Our Camcorder does not work correctly. It will only record 3 or 6 vids depending on the settings of:
-#define KERNEL_SMI_SIZE 0x700000
+#define KERNEL_SMI_SIZE 0xE00000 /* 14MB */
-#define SIZE_ADDR1 0x2FA00000
+#define SIZE_ADDR1 0x2F261568 /* 754MB */
Now then, I don't want you to fix it -but- what I would like to know is how deep do you go in your mapping? Do you show anything about the shared mems?? Like ashmem and/or PMEM?? I know ... I'm really pulling but trying to find any tool that will help. Looks like your free version will not be good enough -but- IF your paid version will get the info I desire, I will purchase it.
Thanks,
-Chuck
 
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
Chucktr said:
Hi there,
I became the new OP for the HTC Rezound and we have a problem. Our Camcorder does not work correctly. It will only record 3 or 6 vids depending on the settings of:
-#define KERNEL_SMI_SIZE 0x700000
+#define KERNEL_SMI_SIZE 0xE00000 /* 14MB */
-#define SIZE_ADDR1 0x2FA00000
+#define SIZE_ADDR1 0x2F261568 /* 754MB */
Now then, I don't want you to fix it -but- what I would like to know is how deep do you go in your mapping? Do you show anything about the shared mems?? Like ashmem and/or PMEM?? I know ... I'm really pulling but trying to find any tool that will help. Looks like your free version will not be good enough -but- IF your paid version will get the info I desire, I will purchase it.
Thanks,
-Chuck
Click to expand...
Click to collapse

No, unfortunately I can't help you. Diskinfo will not show the info you are looking for.
 
  • Like
Reactions: Chucktr
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
New version with some bug fixes is now available (i.e. showing ext SD card info should be more reliable now) .
Please report if you have any issues with this update.

Thanks!
 
M

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
  • Like
Reactions: sordna
cdmackay

cdmackay

Senior Member
Aug 11, 2009
985
273
Cambridge, UK
I just bought the Pro version, thanks very much, looks like a nice app.

One request, please...

For partitions with filesystems that are mounted via FUSE, your app shows only "fuseblk" for the filesystem type.

It is possible to get more information, e.g. using "blkid", so would you please consider adding that in?

For example, on my Samsung Note 3, running CM, the external microSD card is mmcblk1p1.

It has an exFAT filesystem on it, and the ROM I'm using mounts it via FUSE. Your app shows "fuseblk" as the filesystem type.

One way to find the real fs type is to use blkid:

Code: 
blkid /dev/block/mmcblk1p1

which shows "exfat" as the type.

so would it be possible for your app to do that, and display the result? e.g. in my case it could say: "exfat [FUSE]", or similar?

thanks much indeed...
 
  • Like
Reactions: M.Q.
Status
Not open for further replies.

Similar threads

C
  • Locked
[APP]SuperOneClick v2.3.3 - Motorola Exploit Added!
Replies
7K
Views
16M
vanessaem
vanessaem
Team Vanced
  • Locked
[CLOSED][APP][MOD][ROOT/NONROOT] Vanced
Replies
21K
Views
4M
Timmmmaaahh!
Timmmmaaahh!
R
  • Locked
[APP] z4root
Replies
3K
Views
7M
TRusselo
TRusselo
HootanParsa
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
Replies
44K
Views
7M
Ultramanoid
Ultramanoid
PerfectSlayer
[APP][ROOT/NONROOT][OFFICIAL] AdAway v6.1.1
Replies
18K
Views
7M
S
Sgtmack

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 19
    M
    M.Q.
    DiskInfo lists all partitions and all mount points on you device showing disk usage and very detailed partition information. It can also display total and available memory (RAM) and Swap (e.g. zRam).

    It supports:
    • mounted and unmounted partitions,
    • device-mapper / loop partitions,
    • LVM partitions (DiskInfo PRO)
    • temporary mount points
    • * UBIFS (beta)

    For each partition, you can display the following information:
    • total size, used and free space
    • partition name, partition alias, partition type, partition number
    • device name and type
    • block size
    • mounted file system type (also for FUSE in DiskInfo PRO), mount paths, mount type (ro/rw)
    • logical volume group and attributes (DiskInfo PRO)

    All shown in clean, human readable format.

    Root access is NOT required.

    Download:
    https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en

    Screenshots:




    Change log:
    Code: 
    4.5.3 (11/09/2014)
+ Initial UBIFS support
* Bug fixes

4.5.2 (07/28/2014)
* Bug fixes

4.5.1 (07/26/2014)
* Fixed bug with sd cards on some kitkat devices
* Other small bug fixes

4.5 (05/26/2014)
+ Italian translation (credits: bovirus)
    
4.4.2 (05/12/2014)
* Bug fixes

4.4.1 (05/07/2014)
* Bug fixes

4.4 (04/22/2014)
+ Details for SWAP - swappiness, dirty ratios, etc.
* Fixed issue with missing internal partitions on some devices
* Other small fixes

4.3.4 (24/1/2014)
 * PRO: Fixed issue with SDcard missing in widget config (xperia z)
 * Fixed issue with 'unkown size' on some devices
 * Other small fixes

4.3.3 (17/10/2013)
* Small optimizations for tablets (e.g. added size in bytes)

4.3.2 (14/10/2013)
* Small bug fixes

4.3.1 (10/4/2013)
* Fix FC

4.3 (10/3/2013)
+ PRO: Support for root mounts (i.e. StickMount USB devices)
+ PRO: Swap can now be displayed in a widget
+ Better handling of partition nicknames and labels (aka aliases)
* PRO: Fixed issue with widget size on some devices
* Several small fixes

4.2 (9/2/2013)
+ PRO: Added more details (vendor, model for USB devices; manf. date, CSD, CID, OEM ID, manf. ID, revisions and serial numbers for SD cards)
* Fixed issue with duplicated settings
* Fixed issue with partition labels not showing on some devices (thanks sordna!)
* Fixed issue with duplicated device names
* Partition labels are now case sensitive
* Compact Mode: Free percentage now better visible
* Small tweaks here and there...

4.1 (8/22/2013)
+ Better support for partition labels (thanks sordna!)
+ Multiple swap partitions are now supported and marked in the list view
* Performance tweaks

4.0 (8/4/2013)
+ DiskInfo PRO now available (home screen widgets, compact mode, LVM support)
+ MicroSD/USB/ExternalSD support (Asus Inifinity)
* Performance tweaks
* UI tweaks (new pie chart, new font, new animations, etc.)
* Many small enhancements

3.1
+ Added ability to show device type (NAND, SD, MMC. etc..)
* Fixed issue with missing partitions on LG and Samsung devices
* Fixed issue with boot0 and boot1 partitions
* Better support for partition aliases

3.0.2
* Fixed issue with ExtSdCard on some devices

3.0.1
* Reduced apk size

3.0
+ Rewritten mechanism to get list of partitions and mount points:
   + Partitions categorized by device (Internal, SD card, etc.)
   + List both mounted and unmounted partitions
   + List multiple mounts per single partition - no more duplicated entries
   + List device-mapper / loop partitions
   + List temporary file systems
+ New, more accurate mechanism to get available memory
+ New UI
   + Tablet mode
   + New details view with pie chart
   + many, many more...

2.2 08/27/2012
+ Amount of Swap memory is now displayed in the memory section (only if it is present)

2.1.3 08/17/2012
+ Size is displayed using floating-point numbers

2.1.2: 7/31/2012
* Fixed issue with free RAM calculation

2.1.1: 7/31/2012
* Fixed issue with Gingerbread devices

2.1: 7/30/2012
+ More details for each partition (file system type, mount type)
+ New window for details
* Fixed issue with SD-ext partition not displaying on some devices.
* Fixed issue with mount points not displaying on some devices.

    XDA:DevDB Information
    DiskInfo, App for the Apps & Games

    Contributors
    M.Q.

    Version Information
    Status: Stable
    Current Stable Version: 4.9.1
    Stable Release Date: 2015-10-05

    Created 2014-11-09
    Last Updated 2015-10-09
    View
    2
    M
    M.Q.
    .xxx. said:
    Hey i tesred the app.. some info what it gave me were not correct like the sd card free space left and ram used.
    Sent from my LG-E730 using Tapatalk 2
    Click to expand...
    Click to collapse
    Thanks for testing it!
    Can you please provide me more details so that I can investigate the issue? What does DiskInfo show for your SD-card and what is the real free space? How did you measured your real free space?
    View
    2
    M
    M.Q.
    version 4.0.1

    New update is available - https://play.google.com/store/apps/details?id=me.kuder.diskinfo
    I hope you like it and find it useful.

    Changelog for version 4.0:
    Code: 
    + DiskInfo PRO now available (home screen widgets, compact mode, LVM support)
+ MicroSD/USB/ExternalSD support (Asus Inifinity)
* Performance tweaks
* UI tweaks (new pie chart, new font, new animations, etc.)
* Many small enhancements
    View
    2
    sordna
    sordna
    identify boot, recovery, bootloader, etc partitions

    M.Q. said:
    New update is available - https://play.google.com/store/apps/details?id=me.kuder.diskinfo
    I hope you like it and find it useful.
    Click to expand...
    Click to collapse

    Hi, nice app! However I noticed it doesn't identify partitions such as boot and recovery partitions. It shows mmcblk0p6 and mmcblk0p7 if I choose to display unmounted partitions but without any label or indication that they are boot and recovery... such partitions are pretty important, and other apps like .img flashers, and recoveries like CWM, TWRP, identify them just fine.

    Your app should be able to find such partitions by looking at "by-name" directory, for example on my Nexus 4 I can do this:

    ls -l /dev/block/platform/msm_sdcc.1/by-name/boot
    lrwxrwxrwx root root 2013-08-17 22:50 boot -> /dev/block/mmcblk0p6

    ls -l /dev/block/platform/msm_sdcc.1/by-name/recovery
    lrwxrwxrwx root root 2013-08-17 22:50 recovery -> /dev/block/mmcblk0p7

    There are other noteworthy partitions, for bootloader, etc, here is the full list, can your app be enhanced to identify and display the important ones with their appropriate designation ?

    thanks in advance!

    Code: 
    lrwxrwxrwx root     root              2013-08-17 22:50 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              2013-08-17 22:50 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2013-08-17 22:50 abootb -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2013-08-17 22:50 boot -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2013-08-17 22:50 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2013-08-17 22:50 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              2013-08-17 22:50 m9kefs1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-08-17 22:50 m9kefs2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2013-08-17 22:50 m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-08-17 22:50 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2013-08-17 22:50 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2013-08-17 22:50 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-08-17 22:50 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2013-08-17 22:50 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-08-17 22:50 rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-08-17 22:50 rpmb -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2013-08-17 22:50 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-08-17 22:50 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-08-17 22:50 sbl2b -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2013-08-17 22:50 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-08-17 22:50 sbl3b -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2013-08-17 22:50 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2013-08-17 22:50 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-08-17 22:50 tzb -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2013-08-17 22:50 userdata -> /dev/block/mmcblk0p23
    View
    2
    M
    M.Q.
    Thanks for the useful tip. I will add ability to read the "by-name" directory. Stay tuned!

    Sent from my Nexus 7 using Tapatalk 4
    View

New posts