Database Develop

Hero With Bluetooth

First off sorry if I got your hopes up with the above heading
Anyways Now that I got your attention
I would like to know how do you undo all cache to the sd
I used the stupid @ss ta utility from the market trying to see if I could undo the marrket cache, that isn't revertable(< is this even a word???)I tried multiple methods searched found one posting that was a total fail
And now I'm looking into straight up commands to revert
I know uninstalling the app doesn't undo the changes it just leaves them alone and still keeps on telling the phone to push all cache to sd
So what's next deleteing the folder that stores the cache just causes force closes so what the hec?
I've tried reflashing, over the current settings but with no wipe cuz I don't want to lose my current setup
So anyhelp appreciated
Thanks In Advance

If you don't want to wipe you will need to remove the symlinks, copy the folders to internal memory, and reboot the phone.
BTW did you notice it took 10 hours to get a response. People aren't too eager to help after being mislead into reading. Next time try a subject that fits the post & I can almost guarantee you will get responses quicker.

Agreed. I just now checked this out after seeing ONE post maybe 1 or 2 more now that it reads 2 replies I thought this was someone asking if a hero rom had bluetooth support and was gonna laugh

All browsers crash without a "force close"

Hey all,
I've been an xda stalker for a while and have been using all sorts of roms for a while now, but now I am in need of my own question.
For a while now, my mother's G1 has been acting up, whether it be her own fault or a bug. But this one has me confused. Over the past three roms i flashed (dwang, cm, superd) this same problem is always around. Everytime I touch browser, dolphin, etc the page begins loading and then i see the home screen.
Everything else works as it should, which confuses me. Everytime I flash a rom, i wipe, wipe ext, repair ext, wipe, flash.
I'd be happy to post a logcat if someone would be so kind as to inform me how to dump to a txt file.
Hopefully this is something extremely easy so I can get her off my back hah

erkmasterflex said:
Hopefully this is something extremely easy so I can get her off my back hah
Click to expand...
Click to collapse
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM... I'm guessing its something you mucked up by going between builds without wiping, or not fixing permissions between builds, or some app on your ext didnt play nicely.
*oh yeah, wrong section, read stickys, or DIAF, your choice*

jmhalder said:
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM...
Click to expand...
Click to collapse
Nah I think he should install the RC29...just kiddin you should use Super-D or Enom's official. I kinda assumed this thread was about some kind of fix for browser problems.

Ace42 said:
Nah I think he should install the RC29...
Click to expand...
Click to collapse
well, the RC29 might actually force a wipe... and would update itself and have OTA keys... honestly probably not a bad way to go... Super-D is good, but honestly dont notice a huge difference between that and CM.

it was even not working when i reverted to complete stock. could this be a problem with the phone itself? Maybe revert to stock again and take it in to t-mo?
There should not be any problem with leftovers from previous roms, since i completely wipe data and ext as i mentioned in my first post.
Moderators, please move this to correct section. this seemed like the correct section since this seems to be more involved in the development side of things. Definately not Accessories but more involved than Q&A. Thank you

Phone ><---USB--->< PC/Laptop/Mac
adb logcat
watch text fly up screen ... make browser crash
quick !!!!! take a picture of that text.............
if you don't have a usb cable handy, a PC or the time to figure out how to get adb installed
go to terminal emulator on phone, and type
logcat|tee /sdcard/logcat.txt
( get the pipe "|" with alt then s )
make browser crash
go back to terminal press ball then C
Edit : the ball can be a bit of a pain, when in term do menu --> preferences --> control key , and set to which key you prefer, I like left alt as ctrl[\i]
now have a look at the logcat.txt file, it
less /sdcard/logcat.txt
you could just do logcat > /sdcard/logcat.txt
but it doesn't look as geeky
NB use >> instead of > to append > will make new file >> will add to file
to append to file with tee use tee -a file.txt[\i]
and yeah, wrong section

thank you very much for your assistance and the little linux command briefing ha
i decided to try every sort of wipe, repair, etc and do it multiple times. probably didn't do anythin, but worth a shot ha.
Ended up working! I removed the ext and swap partitions, wiped anything i could multiple times, flashed super d, didn't work, wiped a bunch, flashed htc recovery image, then cyan, and presto. For whatever reason it finally worked.
Shoulda done the logcat and posted it so y'all could see whatever was going on and hopefully help someone out later. but all is resolved for now.
If there is a next time, I will post in Q&A. I want to thank everyone for their input and wish all a good night.
-Eric

Moved as not Android Development.

Samsung site link affects S7

Here's a odd one!
I was using my S7 to research an issue with my Samsung LED Smart TV. I found a How To, noticed a file path at the top of the page and backed up one page. It had several links, one of which was "How to Power Cycle a Customers Network". That sounded interesting so I clicked on it.
As soon as I clicked on the link my S7 turned OFF. I turned it back ON and it was stuck on the Dell logo. I pinned holed and tried again. It stuck again.
I booted into the recovery menu and tried to boot from there but it again got stuck. I had to do a factory reset. I use My BackUp Pro with a external SD card, it wasn't that painful and other than my email to setup, I'm back up.
Anyone see anything like this before?
Here a link to the nasty page for the brave to try: http://support-us.samsung.com/cyber/popup/iframe/pop_troubleshooting_fr.jsp?idx=151038&modelname=&modelcode=&session_id=P7mLwJcB60VpLrLWp3vgvhhXtfh2XSS3p78q2QlvhT3McsST29T1%21-1964052360%211228160092%211329276619709

Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install

cdzo72 said:
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
Click to expand...
Click to collapse
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.

wptski said:
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
Click to expand...
Click to collapse
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.

cdzo72 said:
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
Click to expand...
Click to collapse
I'm sure that a reset must wipe everything out, true? A reset barely a month ago. Your saying that monthly maintenance is needed?
I don't reinstall Windows monthly as that's a last resort at any time.

NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.

cdzo72 said:
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
Click to expand...
Click to collapse
Both for rooted devices and no good for me.

wptski said:
Both for rooted devices and no good for me.
Click to expand...
Click to collapse
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please

cdzo72 said:
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
Click to expand...
Click to collapse
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??

wptski said:
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
Click to expand...
Click to collapse
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes

cdzo72 said:
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
Click to expand...
Click to collapse
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.

wptski said:
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
Click to expand...
Click to collapse
Then you definitely had/have a corrupt package and the renaming is a sign of a read only problem trying to surface sounds like to me

[Q] Data use question

After several install of a ROM (namely BCM from zero-cool), my /data/data dir begins to grow out of control.
I suspect some data are not used anymore, but this dir is not wiped by a new install (that's better like that BTW).
How could I know which directories are not needed anymore by the installed applis?
Any ideas, fellows?

ivanoff7 said:
After several install of a ROM (namely BCM from zero-cool), my /data/data dir begins to grow out of control.
I suspect some data are not used anymore, but this dir is not wiped by a new install (that's better like that BTW).
How could I know which directories are not needed anymore by the installed applis?
Any ideas, fellows?
Click to expand...
Click to collapse
What? I'm sorry but i don't understand your question? Your data partition grows? Did you try a full wipe?

race55 said:
What? I'm sorry but i don't understand your question? Your data partition grows? Did you try a full wipe?
Click to expand...
Click to collapse
Yes of course, I could do a wipe but I would have to configure all my apps again.
But maybe I can backup the data and restore it app by app, whenever an appli is installed. Not very practical but probably efficient.

[DEPRECATED] Migrator - Android Backup Solution and Data Migration Utility

THIS PROJECT IS DEPRECATED. I HAVE AN ALTERNATIVE HERE.
Documentation: https://github.com/VR-25/migrator/blob/master/README.md/
Releases: https://github.com/VR-25/migrator/releases/

Reserved for jokes.

It seems really interesting, thumbs up man :good::good::good:

Okay I still don't quite understand the method technically even after reading the description.
The thing is if dev say clean flash(wipe data,system,cache,dalvik) is a must before installing a rom,etc.Then will this adk solution can be used instead of titanium backup?Because you wrote that adk more efficient than tb maybe I'll use this instead of tb

handers1234 said:
Okay I still don't quite understand the method technically even after reading the description.
The thing is if dev say clean flash(wipe data,system,cache,dalvik) is a must before installing a rom,etc.Then will this adk solution can be used instead of titanium backup?Because you wrote that adk more efficient than tb maybe I'll use this instead of tb
Click to expand...
Click to collapse
All you really need to understand are the setup steps. This module prevents app data from being deleted when you use TWRP's "wipe data/factory reset feature".

This sounds too good to be true, lol almost like a proof of concept. Can just binding the new dir with the old make it so there are no issues whatsoever? Will test later this week cause I romhop a lot.

My phone's storage is almost full.The thing i want to ask is if this procedure will need more data space inside /data/media.

alvinator94 said:
This sounds too good to be true, lol almost like a proof of concept. Can just binding the new dir with the old make it so there are no issues whatsoever? Will test later this week cause I romhop a lot.
Click to expand...
Click to collapse
And indeed it is true. No issues whatsoever -- I'm using it myself.
foxmcc8 said:
My phone's storage is almost full.The thing i want to ask is if this procedure will need more data space inside /data/media.
Click to expand...
Click to collapse
No extra space is taken, as data is moved, not copied.

I installed this and it erased all my app data, ironically enough. Make sure you have a backup before installing.

After typing "adk" it finds all the apps, but after typing "." it lists every app with "pm: not found". After a reboot, the apps are not installed. Am I doing something wrong?

soren25 said:
I installed this and it erased all my app data, ironically enough. Make sure you have a backup before installing.
Click to expand...
Click to collapse
Lmao same thing happened to me. Figured the module was buggy and uninstalled it. Maybe i did something wrong too, which im not sure how considering how easy the install instructions are

soren25 said:
I installed this and it erased all my app data, ironically enough. Make sure you have a backup before installing.
Click to expand...
Click to collapse
jungle35 said:
Lmao same thing happened to me. Figured the module was buggy and uninstalled it. Maybe i did something wrong too, which im not sure how considering how easy the install instructions are
Click to expand...
Click to collapse
That's really f**ked up... same to me. I think there was no error on my side while following the "install-reboot-forget" process. Only the lib folders had been moved/binded somehow to the SD folder, no base.apks and no odex-blobs(?).
The result was a totally broken system. Sorry, but IMHO the Dev should not proclaim it that way as long as the script seems to be in pre-alpha ... All log files in /data/media/adk/logs/ are empty, too!
Really don't know whether LMAO or :crying:
Sent from my OnePlus3T using XDA Labs

Please add an alpha into the title. Same happens to me.... and titanium can't restore accounts anymore...

The XDA link in the module description takes you to the forum section rather than this thread.

Seemed interesting and installed
But I lose all app data ,
found no logs and nothing just like fresh install of everything
Keep a backup before trying this
I was on magisk 16.7 ,
Redmi note 3 AEX N

Do not install! I lost everything like everyone else. Pictures I just took on vacation of my kids gone. All texts gone. All app data gone. Wtf man. This needs to be pulled. I lost 3gig of data

JohnFawkes said:
Do not install! I lost everything like everyone else. Pictures I just took on vacation of my kids gone. All texts gone. All app data gone. Wtf man. This needs to be pulled. I lost 3gig of data
Click to expand...
Click to collapse
Never ever try magisk stuff without nandroid or other backup in backhand.

I, like everyone else posting here, fell for this extension and lost all my app data.
I'm not sure if this extension is buggy or if we are simply too stupid to get it running but here is what I did:
install
reboot
forget (about all my app data as all apps seem to have lost their data)
I then opened a terminal, typed adk as instructed and am getting:
permission denied. Can't create /data/media/adk/logs/res_apks_verbose_log.txt: permission denied
typing su before adk does indeed give me a list of apps which seems to get longer every few minutes.
Maybe its still busy copying? I'll give it some more time. Not sure what's up though, are we supposed to wait for the ap to copy all app data over then do an initial restore? Or is it not correctly "linking" the apps to the new app data storage?
###edit###
I did not immediately remove this extension as I thought to give it some time. I then rebooted and its now hanging at the boot screen saying: "Starting up ... please wait" - this section usually only takes a few seconds but I've been staring at this screen for minutes now. I'll give it 30 minutes, maybe it is still busy copying all my APKs and app data to the SD card? I mean I was already wondering how this can only need one simple reboot to be ready...
I'll update this thread if I have any new findings as the extension description sounds quite logical so maybe we're all doing something wrong

Dev RECOMMENDED app data backup in first step even BEFORE INSTALLING it through magisk or twrp.
I think nobody is doing it

J4jks said:
Dev RECOMMENDED app data backup in first step even BEFORE INSTALLING it through magisk or twrp.
I think nobody is doing it
Click to expand...
Click to collapse
you're right he did. I didn't say I don't have a backup I only said the extension isn't behaving as advertised OR I don't get how to use it.
Also, he should change that sentence from "recommended" to mandatory if his app wipes app data
---------- Post added at 02:36 PM ---------- Previous post was at 02:18 PM ----------
I have disabled the extension and rolled back my backup. I'm still wondering what went wrong here as the extension actually created the right folders on my SD card. Somehow the links seem to have been missing. I didn't dare try a restore via "adk ." as it was unclear what else could have gone wrong.
I would however appreciate some feedback and clarification from the author.