Hi,
the android filesystem gives me headaches. since the last update of Titanium Backup the app doesn't work any more on two of mine devices (nexus 4 and nexus 10), it allways fails with insulficient storage. on my nexus 7 (2013) however it works perfect, so i started to investiage, what's the difference and came uppon the storage folder path. on the nexus 7 its storage/sdcard0/TitaniumBackup and on the nexus 4 & nexus 10 its storgae/emulated/legacy/TitaniumBackup. whit the version of TB before the last update it was possible to select storage/emulated/0/TitaniumBackup, which worked for those devices but since the last update this path gets allways converted to legacy and the developer doesn't react to this issue. so i started to play arount in the file explorer and noticed, that on both nexus 4 and 10 when i navigate to storage/emulated/0/ the sdcard content appears, while when navigating to storage/emulated/legacy/ or storage/sdcard0 nothin appears. on the nexus 7 on the other hand the content appears in storage/emulated/legacy and storage/sdcard0 while storage/emulated/0 doesn't even exist.
I know, that most of this folders are simlinks but how to tell which one is a link an where the real data is stored - and how to adapt the filestruktur of the nexus 7 to the other devices so that backup will work again? don't think copying from emulated/0 to storage will work, or?
Thanks for any help!
Anyone?
Please, I need to get TB back up working since I can't use Helium/Carbon, because it absolutely sucks (not possible to backup all apps, automation not possible when using a pin like everyone should, not as reliable as TB was).
Related
I partitioned my SD card in huawei u8150 everything for me is ok but when I look in cyanogenmod settings then application the check box in the expanded internal expanded storage is not clickable please help
ROM: CYANOGENMOD 7.2 STABLE
Sent from my U8150 using xda app-developers app
Don't know the specific device but when running into similar issues I usually do the following
1 back up everything
2 back those backups up somewhere other than the SD
3 reformat the SD with the device you intend to use it for
4 check if re-partitioning is needed
4a if not then; skip to 5
4b if so then; re-partition and go to 5
5 check that things seem ok, try moving an app to SD, try reading/writing/deleting a few junk files
6 if all is ok then move backed up data back to SD card and chock it up to the oddness of electronics, if all is not ok then perhaps your ROM or kernel or device has something sooooo check for bug reports on the sites that you get those from and or check the lists of features.
Currently I run cm 7 on my HTC device and have a multi-partition set up on the SD card, no issues other than Android only seeing the first one in the list.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey
S0AndS0 said:
Don't know the specific device but when running into similar issues I usually do the following
1 back up everything
2 back those backups up somewhere other than the SD
3 reformat the SD with the device you intend to use it for
4 check if re-partitioning is needed
4a if not then; skip to 5
4b if so then; re-partition and go to 5
5 check that things seem ok, try moving an app to SD, try reading/writing/deleting a few junk files
6 if all is ok then move backed up data back to SD card and chock it up to the oddness of electronics, if all is not ok then perhaps your ROM or kernel or device has something sooooo check for bug reports on the sites that you get those from and or check the lists of features.
Click to expand...
Click to collapse
I can move applications but the sd card partition does not increase my internal memory which is 163 mb by the way thanks bro for your help in advance
bonsoljoshua said:
I can move applications but the sd card partition does not increase my internal memory which is 163 mb by the way thanks bro for your help in advance
Click to expand...
Click to collapse
I mean that if i can move the full application in that partitioned aprt of the sd card that would increase my memory
I've written a few guides here and there, if you search hard enough you'll find one about
Folders plug
http://forum.xda-developers.com/showthread.php?t=1502893
that I wrote once about that app... I think so anyways if not then here is a quickey to save time for all readers that stumble across this work around
1. Get some warnings out of the way
~ this app is in beta (currently)
~ requires root
~ use at your own risk
~ don't use on system apps (like your phone or contacts)
~ don't use on apps that you rely on (anti theft apps for example)
~ I'm not the dev of the app just a supporter
~ make a backup (nandroid style) then back all that up and what ever you value on you sdcard somewhere else
~ I've done some hard testing with this app and put two devices into boot loops / simi-bricked states. So know how to recover from this and be careful.
~ I have yet to fully brick any device ever, even with this app, so it might be safe when used properly.
2. Provided the warnings don't bother you, then download and install the above app
3. Open the app and be presented with a few options
~ under menu + Preferences = Mount on boot
~~ I would not use this until playing with the other options first and seeing how your device responds
~ under menu + Edit = a screen that will say something like "no mount points selected"
~~ this is where the magic happens, move to step 4
4. Under 'menu + Edit'
4a~ now press menu and then "Insert"
~ this is where things may be confusing
4b~ For source folder you may want to make a new folder on your sdcard with an app like root browser (hint this app comes bundeled with ROM Toolbox; another fantastic app) I put mine under '/sdcard/Adev/Internal_Spoof/' and then make a new folder path per app from there
4c~ For Target folder things get a bit complex; you've got to find the folder on the device's internal folder structure (root browser for the win on this again) that contains the apps data.
... be back to edit the rest in in a sec, just posting to ensure you know I'm still here
5. Before finalizing any links you should probably back up the app data somewhere else too. For example '/sdcard/Adev/Internal_Spoof/backups/'
6. So you've got a good target for both now there are more options.
6a~ you can press accept and then press and hold on the connection you've just made and then select mount
6b~ or after setting a bunch up the main screen with the red plug icon can be pressed like a button to activate all the ones in the list that have a green check box next to it at once.
7. Once you've tested this... for example I used;
~ for Source I used '/sdcard/Adev/Internal_Spoof/download
~ for Target I used '/data/download'
And kinda get what's going on here and know where you app data is saved (hint I think mine is under '/data/data' but yours maybe different) it's time to make it useful for your quest for more space to install apps (among other things too maybe?)
7b~ so if an app like Pandora is under 'data/data/com.pandora' and you map it like so--
~ source '/sdcard/Adev/Internal_Spoof/Pandora'
~ target 'data/data/com.pandora'
-- and back the data from '*/com.pandora' to '*/Internal_Spoof/Pandora' and then activate the link... then nothing will look different... except when you view the available space that its
8. Rinse and repeat for each app and don't forget to copy the data (otherwise it'll brake the app till you un-link and copy the data ) and remember not to do it to certain apps.
9. Once you've verified that it's all good and your apps run with ok levels of lag you can try testing the "mount on boot" option that I told you not to use yet. If it works after a reboot then opening and interacting with the affected apps, then rebooting again and interacting again and rebooting again, then it's time to do something dangerous...
10. Provided that your with me so far and things are good on your device its time to do the risky bit; deleting the data from 'data/data/com.pandora' and running it strait from sdcard and re-testing for broken apps with a reboot.
This will effectively open real system memory back up for other tasks but like I said use at your own risk.
final edit before seeing any feedback- this work around may seem a bit complex at first but once you've got a list of apps that work when short-cutted like this it can make a big difference in how much available space can be accessed, however, this may cause force closures on some apps, and may degrade the life of your sdcard. Furthermore in some usage scenarios I had better battery life but that's for another guide on another day
I'll be linking in a google doc version of this guide when I get it shairable and maybe link in screen shots or screen casts for better guidance. If I've really helped then consider hitting the thanks button and happy hacking and modding.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the manta (Samsung/Google Nexus 10) - Native Boot
Working:
Wi-Fi (with NetworkManager)
Audio (requires manual intervention)
Not Working:
Bluetooth
2D & 3D Accelerated Graphics
Installation (to a subfolder of the /data partition)
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_manta_20141210_root.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
mkdir /data/local/arch
tar -C /data/local/arch -xpzvf /data/media/0/arch_manta_20141210_root.tar.gz
Booting
Since there is no workable multiboot solution for the Nexus 10 yet, you can take one of two routes to boot this thing:
Option 1: Flash the arch_boot.img to either the recovery or the boot partition of the internal flash chip. Due to risk of BRICKING if you flash to the wrong partition, I will not provide instructions here. I might make a flashable zip later on. Note that this removes access to Android.
Option 2: Use Fastboot to tethered boot the provided kernel from another computer where it is installed:
Code:
fastboot boot boot_arch_manta.img
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
To make audio work after booting and logging in, run "fix_audio.sh" in a terminal.
Read Me
If you WIPE DATA, it will also WIPE OUT THIS PORT, all its applications, and any files you may have stored within it!
Downloads
root filesystem archive: https://drive.google.com/file/d/0B4WUjKii92l2Qkd6S3c3M2tDcTQ/view?usp=sharing
kernel for fastboot or flashing: https://drive.google.com/file/d/0B4WUjKii92l2UGhIWTlVam5vSk0/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_manta
Also available for:
Nexus 7 2013: http://forum.xda-developers.com/nex...fficial-archlinuxarm-release-n7-2013-t2969301
Galaxy S3 LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Free space required?
Started with 5GB+ before downloading the 1.5 tar.gz, thought it will be enough but I'm supposed it wasn't cuz I'm getting "No space left in the device" although I still have 537MB free left.
Hmm, shouldn't do that. The archive itself is 4,060 MB uncompressed according to gzip -l.
Try booting it anyway, maybe? Also, perhaps I uploaded a truncated archive. I'll have to check.
Edit: Wait, you'd need upwards of 5.5 GB free to have both the archive and the extracted files on /data.
So, I deleted my nandroid backup and was able to install it. Actually it runs very well, I think even better than when ubuntu was being officially developed by canonical for the nexus 7. Of course it was easier to run because of the MultiRom solution, always wonder why Nexus 10 it's not supported, like Nexus 4, 5, 7 and even som non-nexus devices.
tavocabe said:
So, I deleted my nandroid backup and was able to install it. Actually it runs very well, I think even better than when ubuntu was being officially developed by canonical for the nexus 7. Of course it was easier to run because of the MultiRom solution, always wonder why Nexus 10 it's not supported, like Nexus 4, 5, 7 and even som non-nexus devices.
Click to expand...
Click to collapse
I don't know, honestly. After I'm done with the HD2 flash-image port of this, I'm looking at porting kexec hardboot from a random old Epic 4G kernel to my kernel_manta on github, because that's the only ready-made Exynos hardboot patch I can find through google. Then, we could boot this with a script similar to the Galaxy S III LTE port, and someone could theoretically port MultiROM, though that someone is probably not going to be me.
Thank you, Castwilliam! It run good , with some gitch on screen, but better than ubuntu phone devReview .
But when I run pacman -Syu ( update packages), reboot and it become blackscreen, try many taps in middle touch screen, intensity light of screen is something change. What wrong when update packages in pacman ?_?.
Is the booting option 2 temporary? Can I just turn off nexus and boot back to android? Can I unplug the nexus from PC while running linux?
I have no idea what I am doing here (and you probably dislike dealing with noobs flooding forums with questions right? :silly: )
Dri0m said:
Is the booting option 2 temporary? Can I just turn off nexus and boot back to android? Can I unplug the nexus from PC while running linux?
I have no idea what I am doing here (and you probably dislike dealing with noobs flooding forums with questions right? :silly: )
Click to expand...
Click to collapse
Yes, yes and yes
Hello,
This is awesome work! It booted properly, connected to a network, and programs run just fine. But as the tablet's pixel density is pretty high, it isn't too comfortable to use. I tried adding a new resolution using xrandr, but it throws something along the lines of "failed to get gamma size for display default". I've tried googling for it, but nothing worked. What can I do to resolve this?
Thanks,
Vedanth
Hi,
With Nexus 9, I can use my flash driver by the OTG cable.
However, the files like: ebooks on this files ALWAYS BEING COPIED TO TEMPORARY FOLDER on the Nexus before it can be used.
(With nexus 7, I just can used any ebook files DIRECTLY from otg flash driver)
SO, am I doing something wrong with my Nexus9 or it is THE WAY THE NEW ADROID OS (5.x) works.
Pls share if you have a way so that I can use the ebook files directly.
PS: the movie files seems to be ok (no copying process displayed)
so far I notice only the ebooks files (I tried PDF files)
Thank you for your reading.
It sounds like it may filter by size, could you try a small (~pdf size) movie file and see if it acts the same as the pdf does? (To tell if it is filtering by filesize or filetype)
Is your Nexus 7 rooted and the Nexus 9 isn't?
Dr. Hurt said:
Is your Nexus 7 rooted and the Nexus 9 isn't?
Click to expand...
Click to collapse
Yes, my N9 isn't rooted yet.
So, would it mean that rooting will solve the problem. I will try.
Thank you.
nguoidungnq said:
Yes, my N9 isn't rooted yet.
So, would it mean that rooting will solve the problem. I will try.
Thank you.
Click to expand...
Click to collapse
Yes, because without root the os can't mount the volume natively and thus has limited access to your otg files via android APIs.
Hello,
I recently got a new phone OnePlus3 and trying to move my old messages from viber to the new one. The application doesn't support this process so I'm using a backup of the two applications along with the help from Android Backup Extractor. The process is described in the web so a google search would provide some more information.
The problem lies on the adb backup command as the package which is extracted from the device is kinda empty.
The old phone is a Nexus 4 with stock Android (rooted) version 5.1.1. The commands I'm using are:
Code:
adb backup com.viber.voip -f ./viber-old.ab
The resulting file is 54 bytes in size and when I unpack it with Android Backup Extractor it's an empty tar file.
I've tried with adb version matching the one on the phone (version 32) and with latest (36) downloaded from the android SDK. I've also tried setting a password for backups and not use empty one.
Since I've been trying with no success I tried on OnePlus3 and on Nexus 5X with no results either. The final size might be different but it's the same issue either 0 bytes or 54 bytes. (which includes just the manifest file). Previously around X-mas I have done the process successfully and moved my messages from Nexus 4 to my Nexus 5X so it's either a new permission policy in Android or Viber application doesn't allow backups?
Happy to debug further if one has some suggestion.
Thanks
The backup to Google Drive option doesn't work to restore on another device? Seems silly...
https://www.youtube.com/watch?v=anMx7W2-gLk
Truth to be told I didn't try that. I'll give it a go when at home - thanks
Sent from my Nexus 5X using Tapatalk
Just want to start out by saying, I HATE HATE HATE how Android has to keep everything so secretive and hard to access. Android works great, but when you want to do something as simple as grabbing files from an app, everything tries its hardest to stand in your way from root access bs to apps detecting if Magisks non functional anti hide is on the system. Enabling root and using root file access apps are so damn useless and crash all the time. Worst part is, they don't even show the files you are looking for when you find the right directories so wtf, what's even the point. /rant
I have a game/app that stores files on my expanded SD card storage. The files get downloaded *somewhere* and my phone detects the 5 GB of storage its using. How can I find the exact directory my phone is using that calculates the size of the files, and how can I gain access to these files to copy over FTP / USB / ADB etc to my computer.
I've spent so many hours trying to figure this out. Closest I got was making ADB backup pulls for the app but the archive is corrupt / incomplete every time so nothing will extract in full.
My device is a Samsung Note 3 running Android 7.1 Lineage.
Figured I would come here for help since I bet there's some Android developers that know a simple trick or two to just extract some simple unencrypted files. Very very much appreciated for any tips or guidance!
blalnstk200 said:
Just want to start out by saying, I HATE HATE HATE how Android has to keep everything so secretive and hard to access. Android works great, but when you want to do something as simple as grabbing files from an app, everything tries its hardest to stand in your way from root access bs to apps detecting if Magisks non functional anti hide is on the system. Enabling root and using root file access apps are so damn useless and crash all the time. Worst part is, they don't even show the files you are looking for when you find the right directories so wtf, what's even the point. /rant
I have a game/app that stores files on my expanded SD card storage. The files get downloaded *somewhere* and my phone detects the 5 GB of storage its using. How can I find the exact directory my phone is using that calculates the size of the files, and how can I gain access to these files to copy over FTP / USB / ADB etc to my computer.
I've spent so many hours trying to figure this out. Closest I got was making ADB backup pulls for the app but the archive is corrupt / incomplete every time so nothing will extract in full.
My device is a Samsung Note 3 running Android 7.1 Lineage.
Figured I would come here for help since I bet there's some Android developers that know a simple trick or two to just extract some simple unencrypted files. Very very much appreciated for any tips or guidance!
Click to expand...
Click to collapse
There is a note 3 section
https://forum.xda-developers.com/galaxy-note-3/help
Sent from my mata using XDA Labs
sd_shadow said:
There is a note 3 section
https://forum.xda-developers.com/galaxy-note-3/help
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
? I need help with Android the software, not Note 3 hardware
blalnstk200 said:
? I need help with Android the software, not Note 3 hardware
Click to expand...
Click to collapse
Every manufacturer implements Android differently
Sent from my mata using XDA Labs