Database Info

Hardware button to open new note?

Ultimately, I want to press a hardware button on my phone, and have it open a new note, ready for my scrawling. Basically, to emulate the "New -> Note" function.
I'm assuming I need to launch notes with some kind of command line parameter, but I don't know what.
I've read -new launches a new note, but it dosen't. I've tried putting in a path to an existing note, with no luck. I keep getting "Cannot open note. It has been renamed, moved, or has been deleted." Yes, I am using quotation marks.
I've had a look at the new menu in the registry, but all it seems to have is a GUID key for each option, which containts a string for the selection title, and a binary option of "enable".
I have a feeling there's something simple I'm missing. Anyone got any ideas?

What command line are you using that isn't working with -new?
v

\Windows\Notes.exe -new
"\Windows\Notes.exe" -new
\Windows\Notes.exe "-new"
"\Windows\Notes.exe" "-new"
All give the error I described. This is when using a shortcut. The button software I have allows you to specify the exe, and "optional parameters" to pass to the executable. It gives the same error. Gnnnnargh!

Use -n parameter. Work fine for new notes
Bye

Edit Lockscreen Text - Not Carrier Text - CM7

Apologies in advance if I am posting in the wrong section.
I've been talking to some people over on the CM forums about this and we haven't found an answer yet.
If you look in my screenshot, right below the alarm, my name is on my lockscreen. This was put here using an old setting on CyanogenMod 6.1.2 on my HTC Evo 4g. You did this on CM6 by going to Settings > Location & Security. Then there was a checkbox to "Show Custom Message". You then put in text!
Does anyone know which file stores this value on CM7/Android 2.3? I've pulled the eri.xml file from my phone and I can edit my carrier text but I have not been able to find my name. I like being able to edit that text and I wanted to update it to something new but the settings no longer exist under CM7. Thanks for looking!

I have found a ton of utils for editing carrier text but nothing for the text pointed to in the red arrow.

.
.
.
.
.
.
.
*bump*

re
Not the answer you are looking for here but wouldnt it be easier and less annoying and stressful to just flash back to the rom where you could change it, change it to what you want and then flash back ?
that is if i am understanding you correctly and your name shows up now of course with the new rom...
i would think if you changed your name to whatever you wanted then you could go back to the new rom and it would appear the way you want it.

I'm going to give that a try tomorrow. Not sure if it sticks through an upgrade or not but worth a try. Im just curious at this point what confit file it is. Wish there was a filemon or similar tool for Android. Although, if can dump all the files off the phone before and after I should be able to do comparisons....hrm. Project for tomorrow.

OK, finally took the time to work on this a little further.
I reflashed CM6, booted and confirmed there was no lockscreen text. Took a nandroid and copied off the system.img
I then put a lockscreen text in - used a custom phrase that would not be in any of the config files normally. Rebooted, took a nandroid and copied off this system.img.
Extracted both system.img files using unyaffs.
I did a binary and CRC comparison off all the files, no differences. So apparently this setting is stored somewhere else. Hrm......

AHA. Found the little bugger finally.
Had to pull the data.img and extract that. The setting is located in
/data/com.android.providers.settings/databases/settings.db
lock_screen_custom_msgTESTTEXT
lock_screen_show_custome_msg1
These are the two options that I found. So, now to see if I can safely edit that DB file and modify the text on CM7. I already have the text on my screen so the data fields are in the DB file already so I suspect I can just edit that file and then replace it on my phone.

Hm. Editing is no good. Blew away all my settings and I not longer can enable any lockscreen.

Hah. Got it! Using ADB works. Instructions:
adb shell
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
.tables (you should see a secure table listed)
.header on
.mode column
select * from secure;
Now scroll through the results. Find the "lock_screen_custom_m" item under name. Note the ID number to the left. Write the ID number down.
update secure set value='your custom message here' where _ID=NN;
NN is the ID number you wrote down.
.quit
Reboot your phone.
There you go, just in case anyone else is interested.

jdostal said:
Hah. Got it! Using ADB works. Instructions:
adb shell
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
.tables (you should see a secure table listed)
.header on
.mode column
select * from secure;
Now scroll through the results. Find the "lock_screen_custom_m" item under name. Note the ID number to the left. Write the ID number down.
update secure set value='your custom message here' where _ID=NN;
NN is the ID number you wrote down.
.quit
Reboot your phone.
There you go, just in case anyone else is interested.
Click to expand...
Click to collapse
Nice find!
I used a derivative of your method to reset the alarm notification on the GB lockscreen when the buggy POS alarm app G-Alarm left it there after removing all the alarms and uninstalling it.
That one is in system instead of secure, and it can be set to a blank string per http://developer.android.com/reference/android/provider/Settings.System.html#NEXT_ALARM_FORMATTED to clear it

Neat! Glad it could help someone out.

jdostal said:
Neat! Glad it could help someone out.
Click to expand...
Click to collapse
Yup, much appreciated! Also great to learn how to edit databases on Android.
Also, I didn't have a USB cable so I did it with the terminal editor. For convenience (i.e. having a real keyboard) I used Webkey for PC access to my phone and its built-in terminal editor to make the changes.

That sounds painful!
I don't know where I read the guide, but definitely use ADB. With ADB you can basically connect to the shell on your phone from your PC through a command prompt. Makes doing this sort of thing MUCH easier!

jdostal said:
That sounds painful!
I don't know where I read the guide, but definitely use ADB. With ADB you can basically connect to the shell on your phone from your PC through a command prompt. Makes doing this sort of thing MUCH easier!
Click to expand...
Click to collapse
Did you miss the part where I didn't have a USB cable?

[TIP/TRICK] Double tap home to launch... anything!

This is a trick I came across (originally seen here, I think). Of course there are apps that can do this for you (see here, for example), but I like to do things without extra apps, if possible. I will use the stock Task Manager as an example (since that is why I looked into this in the first place)..
What you will need is:
-root
-SQLite Editor (or equal)
-Root Explorer (or equal) <-- may or may not be necessary depending on how you find your app names and processes.
-your desired app's full name and process
-resourcefulness
First, check your "Double tap home launch" settings in Settings>Applications to make sure the app you want to launch is not already listed.
Then, locate and note the full app name and process of your choice (it will need to be in this form: <full app name>/<full app process>). For example, this is what one would need to launch the stock Task Manager (which is all anyone should need as far as a task-killer, if you ask me):
com.motorola.PerformanceManager/com.motorola.PerformanceManager.PMAdvancedViewTab
I've looked everywhere for finding the right process name, but where I ended up finding it was in the AndroidManifest.xml in the apk (this is where Root Explorer would be necessary). Your apks are located in the /system/app folder for system apps, and /data/app for user apps (View apk, then view the AndroidManifest.xml file).
The full app name should be basically the first entry listed as <manifest package="app_name_here" versionCode=blah,blah...>. The process name is a bit trickier, but should be found a little further down in the manifest under <activity configChanges="###" label="resource_blah,blah,blah" name=".app_process_name"... The process name will start with a ".", and you need to tack that on the end of the app name, as shown above for Task Manager.
Once you have the info you need, open SQLite and open Settings Storage (the com.motorola.android.providers.settings one, with a hammer & wrench icon). Open the settings.db, then settings (should be very familiar if you've tried the tether hack), and find the line for "double_tap". Edit the value as necessary using app_name/app_process format (there should be no spaces in the value that you enter), save, close, then double-tap home to test it.
Here are a couple apps/processes that I find useful:
Task Manager
com.motorola.PerformanceManager/com.motorola.PerformanceManager.PMAdvancedViewTab
Root Explorer
com.speedsoftware.rootexplorer/com.speedsoftware.rootexplorer.RootExplorer
I started making a list on my sdcard, but it proved to be too much hassle finding the proper processes - if anyone knows of an easier way to locate these, PLEASE post! Also, if people are interested in this, please post the apps/processes that you find so we could compile a reference list.
(Holy crap - I did not realize how long this post is becoming...)

its another way to show how friendly the original coder/(mana)gers/corp. is
Sent from my ME865 using XDA

[Completed] Multi-Window App Instructions/Fix Crashes For Dummies

THIS IS FOR SAMSUNG DEVICES THAT ARE NOT ROOTED AND HAVE THE MULTI WINDOW FEATURE.
I really wasn't able to find anything on why app crashes happen in multI window mode for some apps when using mw-pen on devices that are not rooted. So I wanted to post a blurb on how to manually stop the crashes as well as how to manually enable an app, and get things working. Again this is for devices that are not rooted, though it will work with rooted devices. There really is no point in doing it this way on a rooted device unless your bored or you are just slightly insane.
Since your not rooted you will lose all current app data that is not hosted in the respective applications cloud. As well you will need to recompile new packages when updates are released if you want new features or the program will no longer connect, etc. Updating directly from the app store will kill the multiwindow feature on the respective app. If you are user of MW-Pen app enabler skip step 9. and as MW does this already. If you just didn't want to use mw pro......or are again slightly insane.... then do step 9.
All of the steps below will be carried out on Android device.
You will need the following software:
1) File exploration program with zip support (JRUMMY Root Browser works great)
2) Apk Editor (Free version should be fine although I use pro)
We will assume you have the previously mentioned software installed. If it is not you should do so AFTER reading this post.
1) Create an independent folder in "/sdcard/APKeditor/(My project)/" , additionally I created ./backup & ./new (./ representing the working parent directory).
2)Once the folders are in place, go to Settings>Applications>All Applications>YourTargetApplication I recommend stopping your application and clearing any data or at least cache. Although the information should not transfer over it would really bite if you were the one random exception in this vers, and you were giving copies out. Do not disable the application only stop it.
3) Now you will want to backup your target app. To do this fire up "Apk Editor" select the option to pick an apk from a currently installed app select the option for common edit. Click through until you see the save button on the top right corner. THIS IS BACK UP!! SO DO NOT CHANGE ANYTHING!!
4) Once it has completed successfully I recommend flipping back to your application manager and uninstalling the target app. Then flip back over to APKeditor and install. Test the app to verify nothing became corrupted and the app functions normally with a backup only. This will help in your trouble shooting.
5) Once you have the app installed and everything is good you will want to again go to to your app manager, stop the target app and clear data or at least cache. Stop do not disable.
6) Now open your File Browser of choice that met the requirments and navigate to "./sdcard/APKEditor/" you shold see an apk named "_Base" with the icon of your target app. That is your know good backup so you will want to move the apk file to its respective backup folder created earlier
7) Once the backup is secure go back into APKeditor and again select the option apk from app. This time instead select the Full Edit option (Resource Rebuild).
8) The fun part! This part should take you no more than 15 seconds if it takes longer than that your messing up (JOKE). From the edit screen you will see 3 buttons in the bottom. Go to the last button or "tab" it is labeled "Manifest". Once selected go ahead and long press an entry under <intent-filter> any entry really should be fine but let's be safe. On the menu that pops up you will see the option "Open In New Window" select it. Take a minute at first to look things over and familiarize yourself with the patterns at first it may seem a bit overwhelming. There is a logical structure to the file it is telling things what to do and where they belong. The top will have the permissions required followed by accessing features pertains to those permissions. We don't care about that however. The main areas you should look through (just look at to get familier) are the <intent-filter> entries along with what preceded the entry and the structure and what follows and again and again until you see the pattern. What we will be doing in the next step (The 10 second step) is adding entries under the <intent-filter> sections.
9) So your 15 seconds is up and now you feel like your ready for the 10 second step. Now that your ready we need to go into a less obvious view. You will now see the reason why I had you look at the code in the first view until you were comfortable. So go ahead and click on the pencil icon in the upper right corner. The first edit will be slightly different than the rest. You will see ano entry that says <application> followed by icon, labels, name, theme, those kinds of things. They should be followed by <activity> then <intent-filter> and then <action>. Under the last <action> item in the grouping and before </intent-filter> is where your entry will go. (<whatever> is the starting point for instructions and </whatever> is the closing point. So if we input in <activity-alias> or <program> then that is where our command would sit. In some random place never meeting up with us for our scheduled date). So we will go below the last action entry in the first grouping, and input the following:
<category android:name="com.sec.android.intent.category.MULTIWINDOW_LAUNCHER" />
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
Rinse, wash, and repeat, Rinse, wash, and repeat, Rinse, wash, and repeat......You get the idea... Be sure that </intent-filter> is the line after everytime you make an entry.
10) Now we need to review the document for oddities and/or anomalies to the general rule and what causes app crashes in MultI Window the majority of the time. Typically this happens when overlay singular windows are called from the app and are independent of the general <activity> <intent-filter> <action> rule. In these cases we have to put on our detective hats and poke around. Normally we already know screen the app crashes in so that will is our first clue, so we need to start to look for something to do with that window. If it is a chat window look for a chat window call, etc. In that set of instructions for your crashing window you will want to add in the calls as you have done before you may need to add the first <intent-filter> now you can test. Save the document off to the side and save the apk. And install in real-time. Test the app. You if it was done correctly your app should no longer crash. Unfortunately this is the grey area and things will vary from application to application and this is where detective hats need to be on tight. Look for things like "launchmode=singletask". These can be dead giveaways your in the hot zone of your issue.
11) save the new working apk to the "./new" directory created earlier inserting the app version number after. You can find the new file under the APKeditor folder you should see a new "_Base" File.
*At the end of process 10 you will get an error message when saving saying the file is not authentic etc etc. Ignore the message and continue on.
*As a side note if you follow these instructions, have done trial and error, and things still are not working. Then and ONLY then post below. I can not insure promptness but I will respond when able.

joutcast said:
THIS IS FOR SAMSUNG DEVICES THAT ARE NOT ROOTED AND HAVE THE MULTI WINDOW FEATURE.
I really wasn't able to find anything on why app crashes happen in multI window mode for some apps when using mw-pen on devices that are not rooted. So I wanted to post a blurb on how to manually stop the crashes as well as how to manually enable an app, and get things working. Again this is for devices that are not rooted, though it will work with rooted devices. There really is no point in doing it this way on a rooted device unless your bored or you are just slightly insane.
Since your not rooted you will lose all current app data that is not hosted in the respective applications cloud. As well you will need to recompile new packages when updates are released if you want new features or the program will no longer connect, etc. Updating directly from the app store will kill the multiwindow feature on the respective app. If you are user of MW-Pen app enabler skip step 9. and as MW does this already. If you just didn't want to use mw pro......or are again slightly insane.... then do step 9.
All of the steps below will be carried out on Android device.
You will need the following software:
1) File exploration program with zip support (JRUMMY Root Browser works great)
2) Apk Editor (Free version should be fine although I use pro)
We will assume you have the previously mentioned software installed. If it is not you should do so AFTER reading this post.
1) Create an independent folder in "/sdcard/APKeditor/(My project)/" , additionally I created ./backup & ./new (./ representing the working parent directory).
2)Once the folders are in place, go to Settings>Applications>All Applications>YourTargetApplication I recommend stopping your application and clearing any data or at least cache. Although the information should not transfer over it would really bite if you were the one random exception in this vers, and you were giving copies out. Do not disable the application only stop it.
3) Now you will want to backup your target app. To do this fire up "Apk Editor" select the option to pick an apk from a currently installed app select the option for common edit. Click through until you see the save button on the top right corner. THIS IS BACK UP!! SO DO NOT CHANGE ANYTHING!!
4) Once it has completed successfully I recommend flipping back to your application manager and uninstalling the target app. Then flip back over to APKeditor and install. Test the app to verify nothing became corrupted and the app functions normally with a backup only. This will help in your trouble shooting.
5) Once you have the app installed and everything is good you will want to again go to to your app manager, stop the target app and clear data or at least cache. Stop do not disable.
6) Now open your File Browser of choice that met the requirments and navigate to "./sdcard/APKEditor/" you shold see an apk named "_Base" with the icon of your target app. That is your know good backup so you will want to move the apk file to its respective backup folder created earlier
7) Once the backup is secure go back into APKeditor and again select the option apk from app. This time instead select the Full Edit option (Resource Rebuild).
8) The fun part! This part should take you no more than 15 seconds if it takes longer than that your messing up (JOKE). From the edit screen you will see 3 buttons in the bottom. Go to the last button or "tab" it is labeled "Manifest". Once selected go ahead and long press an entry under <intent-filter> any entry really should be fine but let's be safe. On the menu that pops up you will see the option "Open In New Window" select it. Take a minute at first to look things over and familiarize yourself with the patterns at first it may seem a bit overwhelming. There is a logical structure to the file it is telling things what to do and where they belong. The top will have the permissions required followed by accessing features pertains to those permissions. We don't care about that however. The main areas you should look through (just look at to get familier) are the <intent-filter> entries along with what preceded the entry and the structure and what follows and again and again until you see the pattern. What we will be doing in the next step (The 10 second step) is adding entries under the <intent-filter> sections.
9) So your 15 seconds is up and now you feel like your ready for the 10 second step. Now that your ready we need to go into a less obvious view. You will now see the reason why I had you look at the code in the first view until you were comfortable. So go ahead and click on the pencil icon in the upper right corner. The first edit will be slightly different than the rest. You will see ano entry that says <application> followed by icon, labels, name, theme, those kinds of things. They should be followed by <activity> then <intent-filter> and then <action>. Under the last <action> item in the grouping and before </intent-filter> is where your entry will go. (<whatever> is the starting point for instructions and </whatever> is the closing point. So if we input in <activity-alias> or <program> then that is where our command would sit. In some random place never meeting up with us for our scheduled date). So we will go below the last action entry in the first grouping, and input the following:
<category android:name="com.sec.android.intent.category.MULTIWINDOW_LAUNCHER" />
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
Rinse, wash, and repeat, Rinse, wash, and repeat, Rinse, wash, and repeat......You get the idea... Be sure that </intent-filter> is the line after everytime you make an entry.
10) Now we need to review the document for oddities and/or anomalies to the general rule and what causes app crashes in MultI Window the majority of the time. Typically this happens when overlay singular windows are called from the app and are independent of the general <activity> <intent-filter> <action> rule. In these cases we have to put on our detective hats and poke around. Normally we already know screen the app crashes in so that will is our first clue, so we need to start to look for something to do with that window. If it is a chat window look for a chat window call, etc. In that set of instructions for your crashing window you will want to add in the calls as you have done before you may need to add the first <intent-filter> now you can test. Save the document off to the side and save the apk. And install in real-time. Test the app. You if it was done correctly your app should no longer crash. Unfortunately this is the grey area and things will vary from application to application and this is where detective hats need to be on tight. Look for things like "launchmode=singletask". These can be dead giveaways your in the hot zone of your issue.
11) save the new working apk to the "./new" directory created earlier inserting the app version number after. You can find the new file under the APKeditor folder you should see a new "_Base" File.
*At the end of process 10 you will get an error message when saving saying the file is not authentic etc etc. Ignore the message and continue on.
*As a side note if you follow these instructions, have done trial and error, and things still are not working. Then and ONLY then post below. I can not insure promptness but I will respond when able.
Click to expand...
Click to collapse
XDA Assist is not the place for this post.
Thread closed.

Wildcard and DateTime syntax in Android Automate app

Hi,
I'm new to Android programming and I want to automate a process in an LG phone (Android 5.1.1) with the Automate app. I want it to take a picture at a set time of day and send it by email to a recipient. I have it running ok, just without image file attached because the app expects an absolute file name for the attachment. The problem is that the camera uses the date and time as the filename which of course changes with each image. Is there a way to use a wildcard like 'DCIM/Camera/IMG_*' (btw this doesn't work) to select the just created file which is deleted after the email is sent. So there is only ever the new file that should attach to the next email in this folder when the flow runs, but always with a new filename. I've tried various versions that I found online like GLOB'[IMG_]*' and 'IMG_#' but it always errors with 'NoSuchFile'...
Another way would be if I could give each new image file the same name, that would eliminate deleting the just sent file because it would overwrite the old one and I could set an absolute filename for the attachment in the email template. But i have not found a camera app that allows me to define the filename nor a way to automatically change the name of the saved file.
The other thing I'd like to do is insert the current date and time as the subject line. Here too I have tried various versions that I've found like =DateTime() which either just display the code in the email when I put them in " " (I guess as they should) or error already when I try to save them in the app.
Any help would be much appreciated!
Regards,
Jimmy