Develop Bugs

Titanium backup pro. Total failblog.

I bought the pro version of this software after hearing a lot about it. I live on the edge and support software developers.
Experience 1. Free version looks OK so I pay for the pro version. It tells me I don't have root. I clearly do. I'm running CM 10.2. I have root. I try several things it suggests, nothing works. Reboot and it works.
Experience 2. Try to actually back something up. It tells me I have insufficient free space. I have 9 gigs free on the internal card, have a brand new 32 gig SD card, and I'm trying to backup one small app. Searching the Internet shows dozens of the same complaint. I tried a few suggestions and none worked so far. I'm giving up for now.
Total failblog as far as I'm concerned. WTF? Am I just unlucky? People rave about this software?

For reasons unknown, you are having a bad experience. I have used titanium backup religiously across several different android devices dating all the way back to the original galaxy s 1 running eclair android version 2.1. And in my experiences, due to the complex nature of TB, its really more than just checking if the device has basic root access. If the device is not properly rooted or missing other required configurations, it will not work properly. And considering that you are running CM which isnt even stable yet on this device, its likely an issue with the ROM. If you run what I am running or stock, TB works just fine. Or you can troubleshoot the issue in the ROM thread you are running.
Sent from my GT-N5110 using Tapatalk 2

Are you rooted? If yes, did you grant it permissions for root access when prompted? Did you configure it to backup to your SD card?
Sent from my GT-N5110 using Tapatalk 2

ExploreMN said:
Are you rooted? If yes, did you grant it permissions for root access when prompted? Did you configure it to backup to your SD card?
Click to expand...
Click to collapse
I had done all of those things except configure the backup path to the SD card. But I had lots free on the device too so it made no sense.
But changing the path to the SD card fixed the error so I'm in business.
Thanks and sorry for the rant.

I am having a little trouble with titBU. I just installed a rooted kitkat rom stock and CivZ sphereKat- Rev4.2-n5110by civato kernel. Root is confirmed by rootchecker pro.
TitBU is working, but when I try to BU my apps it fails with the message -Batch BU interrupted. Insufficient free storage space.
The path is to my 64 gb external sd card with 40 gb free and the phone sd card has 1/2 the space remaining.
Anyone have an idea what the problem is? Thanks for any feedback.
****************************************************************************
Found this thread about my specific problem. http://forum.xda-developers.com/showthread.php?p=54077178 However, none of the fixes have worked for me

[FIX] TMO N900TUVUCNB4 External SD Card Write FIX

> > > TMO N900TUVUCNB4 External SD Card Write FIX: < < <
tekhd.com/downloads/tmo_kk_extsd_fix.zip
I just ask for a simple thanks...
This will make Titanium, Root Explorer or any app be able to write to external SD Card...
-> Just flash this zip file via TWRP or CWM...

TEKHD said:
TMO N900TUVUCNB4 External SD Card Write FIX: (TMO OFFICIAL 4.4.2 KK)
tekhd.com/downloads/tmo_kk_extsd_fix.zip
I just ask for a simple thanks...
This will make Titanium, Root Explorer or any app be able to write to external SD Card...
Click to expand...
Click to collapse
FIRST!
Damn, well that was fast. Thank you!
Also, I don't think this should be in "Themes and Apps." This isn't a theme nor an app.

Looks like only 1 line was changed in the following if I am correct. I just edited/compared. I only saw the one change though.
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>

NMonster69 said:
Looks like only 1 line was changed in the following if I am correct. I just edited/compared. I only saw the one change though.
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Click to expand...
Click to collapse
Yes... correct...

TEKHD said:
TMO N900TUVUCNB4 External SD Card Write FIX: (TMO OFFICIAL 4.4.2 KK)
tekhd.com/downloads/tmo_kk_extsd_fix.zip
I just ask for a simple thanks...
This will make Titanium, Root Explorer or any app be able to write to external SD Card...
Click to expand...
Click to collapse
This is awesome... can this be applied using a stock bootloader?
(Basically, install instructions for us newbs would be greatly appreciated)
Thanks!

Store on External Card and install via TWRP?

sacky73 said:
Store on External Card and install via TWRP?
Click to expand...
Click to collapse
yes

Defenestratus said:
This is awesome... can this be applied using a stock bootloader?
(Basically, install instructions for us newbs would be greatly appreciated)
Thanks!
Click to expand...
Click to collapse
Only through custom recovery. If you don't have a custom recovery, but are rooted, you can add the missing line. Use a root file explorer, go to: ~/system/etc/permissions, then edit the platforms.xml with the root file explorer's text editor, and add the missing line <group gid="media_rw" /> (as in post #3). Reboot, and test if apps now have access to external storage (Don't quote me on these steps. Maybe Google them to make sure how to do it). The details to do it manually are more involved, and you need to know exactly what you are doing. That's why the OP has posted the awesome zip. Flash, and done.

bobbyphoenix said:
Only through custom recovery. If you don't have a custom recovery, but are rooted, you can add the missing line. Use a root file explorer, go to: ~/system/etc/permissions, then edit the platforms.xml with the root file explorer's text editor, and add the missing line <group gid="media_rw" /> (as in post #3). Reboot, and test if apps now have access to external storage (Don't quote me on these steps. Maybe Google them to make sure how to do it). The details to do it manually are more involved, and you need to know exactly what you are doing. That's why the OP has posted the awesome zip. Flash, and done.
Click to expand...
Click to collapse
This worked great. Thank You!
(I need to find a recovery that will flash to the new 4.4 N900T - CWM wont)

Defenestratus said:
This worked great. Thank You!
(I need to find a recovery that will flash to the new 4.4 N900T - CWM wont)
Click to expand...
Click to collapse
This is the only recovery that works with 4.4 as of now. Download the tar, and ODIN it to your phone:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte

Anyone else having problems with this? I installed, i see the lines of code, but apps like swiftkey cannot access to write. Any ideas?
Sent from my SM-N900T using Tapatalk

aerichards1977 said:
Anyone else having problems with this? I installed, i see the lines of code, but apps like swiftkey cannot access to write. Any ideas?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
yup, i see the lines but the phone doesnt recognize the card.
edit: turns out my card was bad, got a new one and its working great!!!!

Works Great!:good::good::good:

Could be my card is bad, but after using this fix for a few days my card became read-only. Like, period. I can't format it on my PC or my phone. I can access all files, but I can't delete or modify them. Any clues? I've asked around on XDA and there's one other person with this issue, but no fixes. I will try to get my card replaced through warranty in the meantime.

I have an lg gpad and a note 3 this works on the note 3 but gpad I havent tried this yet.I flashed a rom based on stock and card doesnt write to apps only lg apps the rom claims it has the sd card fix but doesnt work like my note 3 my queation is if I flash this on the gpad will it mess anything up.The devs dont seem to be making any roms so Im stuck looking elsewhere
Sent from my SM-N900T using Tapatalk

Nice!
Sent from my SM-G900W8 using XDA Premium 4 mobile app

Thanks!

I'm still unrooted (damn Knox!) but rapidly coming to the conclusion that I just can't work on an unrooted phone any more, warranty or not.
Is there a non-root fix for this issue (as I know that apps like ES Explorer manage to bypass it on stock phones).
Andre

Thank for help to bring back ownership of my Memory Card to me
I'm again owner of my 64GB card- not Google ! My PlayerPro no more were updating ratings for songs ( end developer of PP was to lazy to try created designed folder on the card for the music ?) This was one of the reasons why I rooted the phone;so after I added this line (<group gid=”media_rw” />) everything is working again like was before update 4.4.2 on my Note 3- N900T.
Another thing what I looking for- is increase volume of my Bluetooth stereo headset. I successfully increased volume for wired headset and speaker (speaker- mono- is not strong side of this phone) with edited: mixer-paths.xml, but I can't find line or solution for the bluetooth, maybe someone can help me with it ?
Note: all changes I did using Root Explorer; could be done also with ES File Explorer

Changed permissions for media write and still does not work
TEKHD said:
Yes... correct...
Click to expand...
Click to collapse
I changed the permissions for the WRITE_EXTERNAL_STORAGE. I used different apps that automate this task and Xposed installers HandleExternalStorage. The permissions are changed and everything works for a little while as it use to. I delete files I no longer need and they are gone only to show back up in their old directories again as if I never deleted them. I can't save my music or delete old music from the external storage either. When I delete old photos or the entire DCIM directory on the external storage is goes away only to return about 40 minutes later. I have been dealing with this for several days and am getting a bit ticked off. Now I have a new Note 3 with 32gb internal storage and 32gb external storage except the external storage is not writable, I could have had that with an iPhone. The reason I went with an android was the flexability of storage but that looks like it is gone.
Anyone else have this problems? As I said the file permissions were changed and look good.
Thanks

[Serious Bugs] Android 4.4.2 Galaxy Note 2

Hello, folks
Recently I upgraded to Android Kitkat 4.4.2 (Indian Version) on my Samsung Galaxy Note II, I have come across a serious BUG after upgrading to Android 4.4.2.
BUG Details: Memory card cannot be read internally
For Instance while connected to Winscp via SSHDroid new folder cannot be created in Memory Card but at the same time new folder can be created in Phone Memory
I guess writing has been restricted
It's not over..... While downloading videos via YouTube Downloader 4.2 (Dentex) when custom folder chosen to memory card downloading gets failed
Again I guess writing has been restricted
I tried 3-4 different memory cards guessing problem might be in memory card (formatted as well)
Flashed my Note II via Hard Reset
Tried all ways and I have come to conclusion the BUG is in Android 4.4.2 Kitkat (Indian Version)
Kindly share if you have encountered same BUG as well (Specially Indian Consumers)
Regards,
Note II

Galaxy Note II said:
Hello, folks
Recently I upgraded to Android Kitkat 4.4.2 (Indian Version) on my Samsung Galaxy Note II, I have come across a serious BUG after upgrading to Android 4.4.2.
BUG Details: Memory card cannot be read internally
For Instance while connected to Winscp via SSHDroid new folder cannot be created in Memory Card but at the same time new folder can be created in Phone Memory
I guess writing has been restricted
It's not over..... While downloading videos via YouTube Downloader 4.2 (Dentex) when custom folder chosen to memory card downloading gets failed
Again I guess writing has been restricted
I tried 3-4 different memory cards guessing problem might be in memory card (formatted as well)
Flashed my Note II via Hard Reset
Tried all ways and I have come to conclusion the BUG is in Android 4.4.2 Kitkat (Indian Version)
Kindly share if you have encountered same BUG as well (Specially Indian Consumers)
Regards,
Note II
Click to expand...
Click to collapse
It's not a bug, it is included in the Kitkat update for security purposes.
There is a fix for that but you have to be rooted.

anesterian said:
It's not a bug, it is included in the Kitkat update for security purposes.
There is a fix for that but you have to be rooted.
Click to expand...
Click to collapse
Bro What kind of security is it? I cannot copy my own files into my memory card
iQuran cannot read my memory card in which has supporting files
I cannot save/download videos from YouTube Downloader to my memory card

What rom are you using?
You can simply transfer your files using a comupter...
Then paste it to your memory card..
That's what I did when I'm on Stock Kitkat ROM...
If you want to apply the SD Card fixed root your phone first.
Sent from my GT-N7100

anesterian said:
What rom are you using?
You can simply transfer your files using a comupter...
Then paste it to your memory card..
That's what I did when I'm on Stock Kitkat ROM...
If you want to apply the SD Card fixed root your phone first.
Sent from my GT-N7100
Click to expand...
Click to collapse
Take a look at my signature

They did what. You can't copy from internal to external memory. Omg i see no 4.4 on my device.
Edit : ok i understand now.
Sent from my GT-N7100

you can copy or move anything with stock file manager My Files..only third party application has no permission to write.

xplore file manager can handle files in sd card too...

Google chose to block write access, for third party apps (those not pre-installed), to external storage; except in their own directories.
There is currently a loophole which some developers have updated their apps to use, but with future iterations of android this will likely be blocked.
This change has been primarily to keep the sdcard clean; un-installing third party apps had left orphaned files the sdcard and resulted in a poor user experience. Personally I'm not sure how viable an explanation this is when you weigh it up against the affect to the user experience of preventing 3rd.P apps from accessing anything outside of their own granted space, or the space granted to a partner app. I think this is either google being evil, trying to lower the value of an sdcard slot to drive OEMs to make devices without one (for various profitable purposes) OR because google goofed on their first time really deciding what access they should have (previously there was no formal access rights definition, it was a free-for-all.)
Hold this space

You can install my apks from play store to back up apk in external card and quick office for editing and saving dox in external card without rooting from play store..enjoy
Sent from my GT-N7100 using XDA Premium 4 mobile app

you are right,writing of sdcard has been restricted in android 4.4.2

Is it possible to revert back to 4.3?

wrena said:
Is it possible to revert back to 4.3?
Click to expand...
Click to collapse
The easiest solution is getting root access and using the sdfix app; reverting is overkill if you just want 3p rw access back.

Happened to me yesterday. I was goin to format my fone, so i took a backup of some apps on helium(Since im not rooted)on my sd card. I formatted my fone. After that wen i went in carbon folder, it was empty. No data.

[Q] Lollipop - Titanium backup ext_sd error

Hope I'm not repeating a question here. I couldn't find anything in this forum. I just finished updating my international m8 to lollipop ota. After installing titanium backup from the market, I noticed my previous backup on ext_sd are reported as not writable by titanium. I was under the impression that the new android L would rectify this Kitkat issue. Is there any work around for this issue yet? Thanks.

So I found a test version of titanium backup for Lollipop http://bit.ly/1v0njNa. Unfortunately I'm getting Documents crashes when I selected the extsd after switching to documentprovider storage. So I'm still unable to assign the backup directory to my external sd. Any input would be appreciated. Thanks!

mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Thread link forum.xda-developers.com/showthread.php?t=2617921
Working ok.

Thanks for the reply. I did use that solution when I was on 4.4 but lollipop has a different documentprovider solution now. I finally figured out what was happening. The issue isn't with titanium backup up but with how documentprovider was accessing my ext_sd. For some reason the documents will crash if I left ext_sd unnamed. I ended resolving the issue by naming my sdcard and it's been working as expected. Weird little bug in lollipop... In addition to the DNS issue.

Thanks for that solution. I had the same issue.
After naming the SD card using my laptop, the HTC Documents application no longer crashed and I can allow write access to the application (ES fileexplorer in my case.).
I guess it is an HTC bug, the documentsprovider shows the label/name of the ext SD card on the button to be pressed to allow access, and apparently it can't handle an empty SD card name.

Adoptable storage with CMD prompt help?

I tried following the steps for the S7 to convert my SD card to internal storage, but when I get to the part where I'm supposed to type in "sm partition disk:179,32 private" it doesn't do anything. It just loads up the shell prompt again. I know the S7 and the Galaxy Tab S are different, but I assumed these steps would be the same. I was apparently wrong, or did something wrong. Anyone tried this and got it to work?
ADB Shell > sm list-disks > sm partition disk:179,32 private

Yes I tried it but no luck
Sent from my SM-T815 using Tapatalk

Porox009 said:
I tried following the steps for the S7 to convert my SD card to internal storage, but when I get to the part where I'm supposed to type in "sm partition disk:179,32 private" it doesn't do anything. It just loads up the shell prompt again. I know the S7 and the Galaxy Tab S are different, but I assumed these steps would be the same. I was apparently wrong, or did something wrong. Anyone tried this and got it to work?
ADB Shell > sm list-disks > sm partition disk:179,32 private
Click to expand...
Click to collapse
Tried with ":" instead ","?

Yeah tried it both ways, no luck

Try with root essential app on play store, there's a specific option to re enable adoptable storage. Try it and report back.

Does not appear to work, does not format external, both internal and external still show as separate, keep wifi on while running or you get advert block notice that freezes the program.
EDIT: It askes you to select external disk, it only shows 1 and size seems wrong far too small, so maybe it formatting the wrong drive?
John
zooster said:
Try with root essential app on play store, there's a specific option to re enable adoptable storage. Try it and report back.
Click to expand...
Click to collapse

I don't have yet MM on tab S so I can't try but something is fishy here, pheraps Samsung completely removed the module.

Hello,
I also tried with ADB with no results. I will try to root mine today night, and give you feedback about Root Essentials.
BR

I just installed the latest SuperSU with TWRP and i am now rooted on MM 6.0 NZ.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
John.
riwaly said:
Hello,
I also tried with ADB with no results. I will try to root mine today night, and give you feedback about Root Essentials.
BR
Click to expand...
Click to collapse

Tinderbox (UK) said:
I just installed the latest SuperSU with TWRP and i am now rooted on MM 6.0 NZ.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
John.
Click to expand...
Click to collapse
Thanks!
Are you sure Root Essentials does not work for you? I have been looking for any other option, and there is not. ADB method has been disabled by Samsung for sure, and I was hopeful Root Essential with Root permission would work.

I have used ADB on the ASOP MM and it looks different, it showed one drive when connected to my notebook, when using RE it showed 2 drives, and i installed it twice, though it has setting, auto, internal, external storage, i left it on auto for where downloaded files go, I downloaded a couple of files and they went to the internal storage, why a choose if the internal and internal are now one, seems fake to me, and it was supposed to format my external 128gb micro sd, and it did not do even that.
John.
riwaly said:
Thanks!
Are you sure Root Essentials does not work for you? I have been looking for any other option, and there is not. ADB method has been disabled by Samsung for sure, and I was hopeful Root Essential with Root permission would work.
Click to expand...
Click to collapse

Tinderbox (UK) said:
I have used ADB on the ASOP MM and it looks different, it showed one drive when connected to my notebook, when using RE it showed 2 drives, and i installed it twice, though it has setting, auto, internal, external storage, i left it on auto for where downloaded files go, I downloaded a couple of files and they went to the internal storage, why a choose if the internal and internal are now one, seems fake to me, and it was supposed to format my external 128gb micro sd, and it did not do even that.
John.
Click to expand...
Click to collapse
Can you send a snapshot of Settings/Storage screen. In the web pages where ADB process was explained, it was told that storage information was not accurate, although adoptable storage was working. In my view, if after enable adoptable storage option in Root Essential, there is any change in Settings/Storage info, it will seem to work. Otherwise not.

I remove RE, cats asleep in front of my keyboard so not easy to type at the moment, we need another member to try RE ADB and see if they think it is working, I think ABE should work like RAID in computers, 2 drives in to 1, seemless.
John.

Tinderbox (UK) said:
I just installed the latest SuperSU with TWRP and i am now rooted on MM 6.0 NZ.
Click to expand...
Click to collapse
So did I. I installed TWRP and Supersu from the links you provided in another topic. My main reason for looking forward to MM on my Tab S is adaptive storage. 16gb of internal storage is ridiculous. I have a S7 Edge I'm but not using adaptive storage on the S7 yet because 34gb at this point suffices. It's nice to know I have that option with the S7 if needed. I just hope the Dev's find a way to enable it on our tablets.

You can use the Vanilla version of 6.0 MM, there is no TouchWiz but it has Adoptable Storage, I installed it myself and it works, but i like TouchWiz
http://forum.xda-developers.com/gal...android-6-marshmallow-tab-s-10-5-lte-t3219759
John.
Eddie Hicks said:
So did I. I installed TWRP and Supersu from the links you provided in another topic. My main reason for looking forward to MM on my Tab S is adaptive storage. 16gb of internal storage is ridiculous. I have a S7 Edge I'm but not using adaptive storage on the S7 yet because 34gb at this point suffices. It's nice to know I have that option with the S7 if needed. I just hope the Dev's find a way to enable it on our tablets.
Click to expand...
Click to collapse
---------- Post added at 05:58 PM ---------- Previous post was at 05:15 PM ----------
I wonder what owners of the Tab S2 are doing, do they have an AS fix, and will it work on the S1
John.

Tinderbox (UK) said:
You can use the Vanilla version of 6.0 MM, there is no TouchWiz but it has Adoptable Storage, I installed it myself and it works, but i like TouchWiz.
Click to expand...
Click to collapse
I could take or leave TouchWiz, either way is OK. I checked into that version. It appears some people are having issues with it. Maybe now that an official T800 firmware is out the Dev can work out any bugs. I'll pass for now. Thanks

If you have a problem with Google Play crashing, a member has posted an alternative OpenGApps later in the thread, and that one works fine.
Also there an an ASOP Vanilla version of Android 7.0 Nougat, but i think it`s a bit buggy, so i have not tried it, though others says it fine.
John.
Eddie Hicks said:
I could take or leave TouchWiz, either way is OK. I checked into that version. It appears some people are having issues with it. Maybe now that an official T800 firmware is out the Dev can work out any bugs. I'll pass for now. Thanks
Click to expand...
Click to collapse

Tab S with official MM Rom with custom recovery and Rooted following given instructions!! Thx!! These are the good news. Bad news are that Root Essential seems to do the same thing as ADB procedure but automatically, so it does not work either. We hope Dev's community will find a solution soon. It seems that Samsung was not interested in giving us easily more internal storage, in order to be potential clients of a new Tablet in a future!!! Samsung, do not count on me for sure!!

It's highly likely Samsung have removed the necessary framework for this to even work due to the S7 hack.
I should imagine all future updates for all devices will be the same including the S7.
Unless someone convinces Samsung to reinstate it or is able to patch the rom with the necessities it's just not going to work any more.

ashyx said:
It's highly likely Samsung have removed the necessary framework for this to even work due to the S7 hack.
I should imagine all future updates for all devices will be the same including the S7.
Unless someone convinces Samsung to reinstate it or is able to patch the rom with the necessities it's just not going to work any more.
Click to expand...
Click to collapse
I know that's not out of the realm of possibilities, but it just doesn't make sense to me. I totally get that Samsung is worried about receiving support calls from people that don't understand what adoptable storage is and that may have turned it on by mistake. Though turning it on via the shell on its own demonstrates that the user knows exactly what they're doing. Nobody is going to stumble into that. So, what would be the value in blocking that? I sincerely hope that someone finds a workaround.