I realize there's plenty of threads with more or less the exact same topic. But I haven't found an answer in any of them that helps my situation.
Alright here's the deal:
I'm getting the "Storage space running out"-notification. And apps are starting to FC.. My phone is a i9505 and I'm currently running Carbon. But this was a problem with CM 10.2 too.
Here's what confuses me:
Code:
[email protected]:/data # busybox df -m
Filesystem 1M-blocks Used Available Use% Mounted on
...
/dev/block/platform/msm_sdcc.1/by-name/userdata
9351 9300 50 99% /data
...
/dev/fuse 9351 9300 50 99% /mnt/shell/emulated
...
/dev/block/vold/179:33
30688 25851 4837 84% /storage/sdcard1
Those should be the interesting bits (I'm showing off my 32GB external card here as well). Right, so I'm using 99%, or 9300MB.
Now here's how I check what's taking up the space:
Code:
[email protected]:/ # du -d1 -m /data
1 /data/dontpanic
3404 /data/media
1 /data/misc
1 /data/local
252 /data/data
1 /data/app-private
176 /data/app-asec
203 /data/app-lib
939 /data/app
1 /data/property
1 /data/ssh
1 /data/radio
321 /data/dalvik-cache
1 /data/resource-cache
1 /data/lost+found
1 /data/drm
1 /data/mediadrm
1 /data/security
4 /data/system
1 /data/wpstiles
1 /data/wiper
1 /data/shared
1 /data/fota
1 /data/time
1 /data/bluetooth
1 /data/audio
1 /data/.ssh
1 /data/tombstones
1 /data/nfc
1 /data/user
6 /data/qcks
1 /data/backup
1 /data/anr
5302 /data
du sums it up for us: 5302MB on /data
DiskUsage is showing me "System data" is taking up the space, but it doesn't tell me what or where:
{
"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've checked solutions mentioned in related threads (all over the internets):
* The "/datadata" issue - I don't have this directory
* The "lost + found" - It's 1MB as you can see
* The "/data/log" issue - I don't have this directory
So what am I missing?
Well wouldn't you know. After a reboot the usage is down and df reports the same as du. I'm still confused as to what took up the space though.. I even got Java exceptions (from DiskUsage) saying the disk was full.
Related
Hello XDA :victory:
I just finished making a simple yet useful backup app for Android 4.0.3+ (Root needed)
It can:
Make a Nandroid backup of the following partitions: /data, /cache, /android-secure, /sd-ext, /system
Copy all user installed APK's into the sdcard
Simple, yes, but somewhat useful
Screenshot:
{
"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"
}
Change log:
7/26
-Option to make a full Nandroid backup
-Changed some GUI
To install:
1. Install this APK.
2. copy this file AND this file to system/bin and set permissions as 655, or run this in adb:
1. "adb push xdevilium_onandroid_data_backup system/bin"
2. "adb push xdevilium_onandroid_backup system/bin"
3. "adb shell chmod 655 system/bin/xdevilium_onandroid_data_backup"
4. "adb shell chmod 655 system/bin/xdevilium_onandroid_backup"
Credits: The creator of "onandroid" script (sorry, i forgot the username )
I see that you are using an old version of Online Nandroid. I would really appreciate if you could keep it upto date.
Btw, great attempt at an app.
ameer1234567890 said:
I see that you are using an old version of Online Nandroid. I would really appreciate if you could keep it upto date.
Btw, great attempt at an app.
Click to expand...
Click to collapse
I can't, sorry, I lost the source code and I'm working on Newgen and XDA ROM HUB now
Is it similar to the "App2zip"?
Two issue, i can download apk file but i can't download other 2 files, i receive a text web page.
Eg:-
echo "##########################################"
echo "XRH Nadroid Data Backup"
echo "* This tool backups /data partition."
echo "* It is fully compatible with nandroid."
echo "* Based on 'onandroid' By Ameer Dawood"
echo "##########################################"
echo ""
# Define constants
path="/sdcard/clockworkmod/backup"
safety=7
name="none"
tz="u"
req_power=10
sdcard_temp_mount="/mnt/sdcard4nandroid"
logfile=/data/local/tmp/onandroid.log
# Logging function
mkdir -p /data/local/tmp
[ -f $logfile ] && busybox rm $logfile
logmsg(){
message="$*"
dtime=`busybox date +%T`
echo -e "$dtime $message"
echo "$dtime $message" >>$logfile
if [ "`busybox which log`" != "" ]; then
log -p i -t onandroid "$message"
fi
}
# Process arguments
if [ $# -gt 0 ]; then
if [ $1 == "--help" ]; then
# Display usage instructions
clear
echo ""
echo "Usage: xrh_backup_script [OPTIONS] [NAME]"
echo ""
Click to expand...
Click to collapse
android addicts said:
Is it similar to the "App2zip"?
Two issue, i can download apk file but i can't download other 2 files, i receive a text web page.
Eg:-
Click to expand...
Click to collapse
Right click, save page as
I'm having trouble getting this to work. Is there anyway you can all the install steps into the app for me
Sent from my SCH-I800 using Tapatalk 2
i have install " BOCHS APP" on my device and i make Image for windows xp using virtual machine
after i copy file " XP " and run BOCHS win xp not working i make all change on file bochsrc.txt
and still not working
Code:
###############################################################
# bochsrc.txt file for DLX Linux disk image.
###############################################################
# how much memory the emulated machine will have
megs: 384
cpu: count=2, ips=6000000, reset_on_triple_fault=1, ignore_bad_msrs=1
# filename of ROM images
romimage: file=BIOS-bochs-latest
vgaromimage: file=VGABIOS-lgpl-latest
vga: extension=cirrus, update_freq=50
pci: enabled=1, chipset=i440fx, slot1=cirrus
# what disk images will be used
#floppya: 1_44=W98RUS.img, status=inserted
#floppyb: 1_44=floppyb.img, status=inserted
# hard disk
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata1: enabled=1, ioaddr1=0x170, ioaddr2=0x370, irq=15
ata0-master: type=disk, path="xp"
#ata0-slave: type=disk, path="d.img"
ata1-master: type=disk, mode=vvfat, path=/sdcard/hdd, journal=vvfat.redolog
#type=cdrom, path="RUSW95B_USB.ISO", status=inserted
# choose the boot disk.
boot: c
# default config interface is textconfig.
config_interface: textconfig
#config_interface: wx
#display_library: x
# other choices: win32 sdl wx carbon amigaos beos macintosh nogui rfb term svga
# where do we send log messages?
log: bochsout.txt
sb16: enabled=1
# disable the mouse, since DLX is text only
mouse: enabled=1
# enable key mapping, using US layout as default.
#
# NOTE: In Bochs 1.4, keyboard mapping is only 100% implemented on X windows.
# However, the key mapping tables are used in the paste function, so
# in the DLX Linux example I'm enabling keyboard_mapping so that paste
# will work. Cut&Paste is currently implemented on win32 and X windows only.
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-us.map
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-fr.map
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-de.map
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-es.map
there any help how i can make config for note 3
sorry for my bad english
you renamed c.img to xp here
ata0-master: type=disk, path="xp"
#ata0-slave: type=disk, path="d.img"
ata1-master: type=disk, mode=vvfat, path=/sdcard/hdd, journal=vvfat.redolog
#type=cdrom, path="RUSW95B_USB.ISO", status=inserted
# choose the boot disk.
boot: c
Click to expand...
Click to collapse
... why ?
U should rename it back to c.img
ata0-master: type=disk, path="c.img"
#ata0-slave: type=disk, path="d.img"
ata1-master: type=disk, mode=vvfat, path=/sdcard/hdd, journal=vvfat.redolog
#type=cdrom, path="RUSW95B_USB.ISO", status=inserted
# choose the boot disk.
boot: c
Click to expand...
Click to collapse
and rename xp img you made to c.img and put it on SDcard/SDL/ (device storage not external) like this :
{
"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"
}
and you should be able to run it
tips :
Change ram to 512 or 1024 or even 1536
# how much memory the emulated machine will have
megs: 512
Click to expand...
Click to collapse
U can add files and folders to drive d:/ on win xp by copying them to sdcard/HDD
Reply if it worked or not
....
If its possible , can you uploud xp img cuz i tried w98 and it worked but it's very old
Hello all,
I used to install install custom ROMs since i got my nexus 4, note I'm on the official lollipop update, but i noticed that the data partition size changed from 12.x to 5.7 GB which is too small.
I have root access, and found there are 25 positions including my data partition, is this normal?
How can i repartition and get my full size data?
Code:
[email protected]:/ # ls /dev/block/mmcblk0p
mmcblk0p1 mmcblk0p14 mmcblk0p19 mmcblk0p23 mmcblk0p5
mmcblk0p10 mmcblk0p15 mmcblk0p2 mmcblk0p24 mmcblk0p6
mmcblk0p11 mmcblk0p16 mmcblk0p20 mmcblk0p25 mmcblk0p7
mmcblk0p12 mmcblk0p17 mmcblk0p21 mmcblk0p3 mmcblk0p8
mmcblk0p13 mmcblk0p18 mmcblk0p22 mmcblk0p4 mmcblk0p9
[email protected]:/ #
The number of partitions is normal. You can't re-partition the device. If you try you'll brick it.
Sent from my Nexus 9 using XDA Free mobile app
Backup your data and reflash the stock factory image (flash-all.bat). It's the only fix i know of.
Thanks @greg17477 and @jd1639.
Actually the lollipop official had a bug with creating new corporate google apps account, so I had to make that account on kitkat then do OTA update.
Will the backup reserve the corporate account?
tarekeldeeb said:
Thanks @greg17477 and @jd1639.
Actually the lollipop official had a bug with creating new corporate google apps account, so I had to make that account on kitkat then do OTA update.
Will the backup reserve the corporate account?
Click to expand...
Click to collapse
It should, but I am not 100% sure.
I have the same issue, total space on my 16GB N4 is 5.67GB. It seems to be a problem with the 5.0.1 OTA update.
Device:
-Mako 16GB rev10
-Stock ROM (flashed 5.0 from factory image, then received OTA 5.0.1)
-No root
-Install DiskUsage : it didn't see the missing storage space
-Clear cache from recovery : didn't solve it
-Factory Reset : didn't try yet, but doubt it will work
-Flash factory image LRX22C : will do when I get home
{
"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"
}
Hi guys, my heart rate monitor sensor is not working and the sensor doesn't even light up, which means it's not working AT ALL! And recently I even noticed Antutu and CPU-Z(Sensor Section) doesn't even detect it! (Screenshot below) What may be the cause of this?
Here is the logcat output of the BioSensor:
Code:
E/EnterpriseSharedDevicePolicy( 1132): isSharedDeviceEnabled
E/SensorService( 1132): Error activating sensor 18 (Operation not permitted)
E/SensorService( 1132): Error activating sensor 18 (Operation not permitted)
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/led_current
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/led_current2
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/lib_ver
E/audio_hw_primary( 338): [MAXIM] setDSM_tx_Control()....dsm_enable : 0, dsm_opened : 1, adev->mode : 0
E/LocSvc_libulp( 1132): I/int ulp_msg_process_system_update(UlpSystemEvent): systemEvent:5
E/LocSvc_libulp( 1132): I/int ulp_msg_process_start_req(), at ulp state = 1
E/LocSvc_ApiV02( 1132): I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 125 QMI_LOC_GET_BEST_AVAILABLE_POSITION_REQ_V02
E/LocSvc_libulp( 1132): I/int ulp_brain_process_zpp_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*), report ZPP position to providers,report_position = 1
{
"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"
}
Was your heart rate monitor working before? Have you tried doing a hard factory reset to see if it will help?
DarkGuyver said:
Was your heart rate monitor working before? Have you tried doing a hard factory reset to see if it will help?
Click to expand...
Click to collapse
I didn't try the heart sensor before, never really gave it much thought...
Yes, I've tried to do a Hard Reset, I even flashed new firmware via Kies and made the Soft Reset (Take of the battery, press power btn for 1 min, yadayada) and it still doesn't work... I've uploaded a logcat check 1st post.
I'd take your phone to a Samsung Service Center and ask them to fix it for you. Or take it back to the retailer for repairs as it maybe faulty.
Btw did u get the solution b/c I have same problem
I was wondering if someone could help me with settings to use in the Dose Config Settings in the OmniGears menu to replace the Forcedoze app.
Is it possible to force Omni to doze by using some more agressive settings in the Dose Config, so Omni would go into deep sleep after switching the screen off and not looking to the sensors?
And when the answer is yes, what settings are preferabele then?
You have to use another kernel then default for this because you have to block the wakelock sensor_SMD for this with EX kernel manager (or another kernel manager ofcourse).
Unfortunately it is not possible to block wakelocks with the default Omnirom kernel so I am using Mady's Xtended Kernel for this in combination with the following doze settings in the OmniGears doze menu:
light_after_inactive_to = 0
light_pre_idle_to = 0
light_idle_to = 0
inactive_to = 10
sensing_to = 0
locating_to = 0
motion_inactive_to = 0
idle_after_inactive_to = 0
idle_pending_to = 30
idle_to = 1800
{
"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"
}
Jan_L said:
You have to use another kernel then default for this because you have to block the wakelock sensor_SMD for this with EX kernel manager (or another kernel manager ofcourse).
Unfortunately it is not possible to block wakelocks with the default Omnirom kernel so I am using Mady's Xtended Kernel for this in combination with the following doze settings in the OmniGears doze menu:
light_after_inactive_to = 0
light_pre_idle_to = 0
light_idle_to = 0
inactive_to = 10
sensing_to = 0
locating_to = 0
motion_inactive_to = 0
idle_after_inactive_to = 0
idle_pending_to = 30
idle_to = 1800
Click to expand...
Click to collapse
so I can change the values, but it has no effect, if i use the offical omni with his own kernel?
Master_TC said:
so I can change the values, but it has no effect, if i use the offical omni with his own kernel?
Click to expand...
Click to collapse
When the motion sensor is active, the device will come out of deep sleep.
Because in the mean time I have switched a lot in ROM's and kernels, I am using Forcedoze now again, but indeed, another kernel with wakelock blocking would do the job.
I would suggest HolyDragon kernel or Luiskernel, both are very good. Drain of Luiskernel is the lowest I could find until now (even better then Mady's).