Database Users

application idea: make thiefs return my MDA-Pro

Hallo, I have a cool applcation idea that I plan to implement that would probally make thiefes return my MDA-Pro after they stole it.
For that reason I need to be able to run an application or show a clickable screen on the MDA-Pro BEFORE login. That screen is supposed to be shown EVERYTIME the MDA-Pro is turned on. You can only proceed to the login screen from there with a certain keybaord shortcut. Also doing a reset should not disbale this feature. Can that be done some how ? If so how ?

I saw somewhere a password screen that was a picture and you had to click in just the right spot of the picture to gain access. I imagine that your message could be a picture to accomplish this. As for a hard reset solution, you'd have to add it to the ext rom so it would be re-installed automatically.

Tron_Of_Borg said:
I saw somewhere a password screen that was a picture and you had to click in just the right spot of the picture to gain access. I imagine that your message could be a picture to accomplish this. As for a hard reset solution, you'd have to add it to the ext rom so it would be re-installed automatically.
Click to expand...
Click to collapse
do yu have any more info on that passwordscreen ?

PicturePassword for Pocket PC
http://microsoft.handango.com/Platf...2&productId=102126&sectionId=5606&catalog=30&

Try http://www.picturepassword.com/
and my recommedation, 1pass by Omega One
http://www.omegaone.com/pass/default.htm
This can be nicely resource edited to match your theme.
However, I've stopped using all such programs because they reset your hardware button settings if you're using AEButton Plus or any third party mapper (eg ButtonMax).
I don't think this will get your phone back. I'm writing a program that might though. Working on it, I'll keep you posted. In the mean time, check out IIWPO.
V

Maybe I should be more specific:
I have already finished an app that does what I want:
It it has a little embedded window showing what the video conference camera currently sees. It displays some fake government info and an animated GPS localisation icon. It has several other little scary acting features (such as a windows that pops up after a short random while, saying "EuroSecure GPS localisation data and video sequence sucessfully transmitted!" ) and the thief can see the adress where the device should be returned too. That application can only be cancelled with a certain keycombination. Now my only problem is getting this application to ALWAYS run BEFORE the login screen.

Eclipse and Android SDK

Hey all, i am starting to find out about creating apps. I have started with creating a simple webview app that shows a website.
What i am having trouble with is after editing the files in eclipse i hit run an in the SDK emulator all i get is a black screen wit android write on it.
Any ideas?
NOTE: i am very new to this

Be patient it takes like 10 mins or more for the emulator to load

Novice here.
Yes, it will take sometime. Here it starts quickly (core i5 notebook). But it may take a long long time.
You can also use your phone to debug and deploy. It's very very quick, takes virtually no time to load, like the emulator. At least here.
Good luck!

Thanks all it did take a while was juts me being inpatient.

Follow-up question: When debugging an app in eclipse, if you change your source during a debug session, it should restart my app/activity/whatsis, right?
Yeah.. not getting that at all, and my current dev box leaves something to be desired in the horsepower department. Those emulator restarts are killing my interest in working on this pet project of mine.
I found a link that should let me use my Evo directly, hopefully that will do the trick.
--Mark
Sent from my PC36100(Evo) using XDA App

Update:
Grr. I installed the HTC Sync 2.blah, so I can actually connect to my Evo now from within Eclipse but I'm still running into problems. Eclipse still isn't automagically updating my app when I change-n-save. Am I just expecting too much here?
Oddly enough, it DID update the changed app when I unplugged my evo from my laptop and plugged it back in. This took several seconds to catch up, but it beats the hell out of waiting for a new emulator to boot. Ouch. We need some way to freeze/save the emulator state so we can relaunch it with it's memory and so forth already in place.
I'd mangled my first hand-rolled "hello world" app (started monkeying with stuff without knowing what did what), so it no longer ran. Note To Self: "Test Only" flag seems to mean "emulator only". That was a snag.
So I whipped up a demo app (the "Skeleton App" for 2.1) project. Installed and ran fine. I changed a couple buttons to Log.d(...) instead of What They Did, and after the unplug-plugin trick, the app updated. The buttons no longer performed their original tasks... instead they now do what looks like NOTHING! LogCat isn't showing my debug messages at all (which wasn't a problem previously when I was just using the emulator).
Am I just missing the boat here or what?

[Q] Metro apps crashing due to "sharing" of app data folder

Some of my Metro apps either no longer launch or launch but do not load or work once loaded.. Here's what I did:
I recently discovered how much I liked the Music app so I decided to import some music by adding libraries through "computer" and "libraries" and "properties". For some reason some playlists were being picked up so I did something very dumb and allow sharing of my whole C: in hopes for it to pick up some music that the Music app had a hard time finding.
Well that royally screwed some things up and stopped my Metro apps from opening. I guess messing with sharing permissions wasn't a smart idea. I couldn't find any way to un-do so what I did so I tried to do a system restore to a restore point from earlier that day. After restoring I noticed some Metro apps on the had a little "x" in the bottom right corner of the tile. I clicked on it and it took me to a message saying that the app could no longer run because my developer license had expired. Funny, but I never had a dev license to begin with nor do I know what that has to do with anything. So naturally I uninstalled the apps that wouldn't work (approx. 6) and re-installed them. Most worked, some still did not.
Once re-installed I noticed that "Tweetro" (twitter app) opens but no longer shows anything but the logo on the top left corner. Just a black screen. I can access the charms bar but nothing else. So I tried another twitter client which just opened but wouldn't allow me to sign in, just kept showing the "click here to sign in" no matter how much I clicked sign in.
The Sports app just auto closes if I try to launch it. Same with the News app. When I go into Ebay now it just shows "loading" on all the tiles. I've no confirmed that it was in fact a problem I created due to allowing sharing of the C drive. Apparently the hidden folder "app data" is the culprit and causes this problem when shared. I'd like to know how to un-do this problem without a refresh or reset of Windows. Apparently undoing sharing privileges from the "app data" folder does not resolve things.

[Q] Last read confusion

I'm using the stock nook reader and renate's Library.apk. How can you make sure the last read icon on the top bar corresponds to the last read file in the library?
I am not sure where this icon gets its link. It doesn't seem to always open the last read file.

I've been thinking about asking this question (although I am using the stock reader AND library apps). My "reading now" button is getting really cranky of late. It often just goes to the first page (cover) or sometimes it goes to the first page AND displays a two-option message about the different current reading positions in two Nook readers (!) and which one do I want (generally neither is correct). Right now the only sure way to get to the correct page is to go to the Library screen and select the book from there. So the Nook does remember, but the Reading Now button is not functioning properly.
For a time I had a number of B&N apps disabled (renamed ".bak") and gradually discovered the imponderable connections that seemed to render little things inoperable. I've had to restore quite a few of the apps to running to keep everything functioning except Nook Community (because the constant "nagifications" drove me crazy) but this button behavior has me baffled (as does the reference to two Nook readers!)
I wonder, are you using any sort of "cleaning" app? I am using Clean Master and find it helpful in freeing up memory but I'm beginning to think that some of the data it is throwing out might just contain the info that the button needs to function properly. It certainly messes with Tasker.

The "Last Read" icon on the status bar sends out the intent com.bn.nook.launch.LAST_BOOK
This would normally be handled by Home.apk
If you deleted Home.apk and are using my Library.apk it has its own receiver for that.
Depending on which version Nook software you have it will query
content://com.bn.nook.reader.providers.lastreadingpointprovider/
content://com.bn.nook.reader.common.providers.lastreadingpointprovider/
The LRP database is maintained by the Reader(RMSDK).apk.
Checking for the latest modification gives you the last book read.
My Library.apk sends an intent out to open that book.
Currently Library.apk does not update the order of books displayed in "Last read" unless the refresh button is hit.
Two things to look for if you are having problems:
If you let the battery die and the WiFi is always off the clock time will be wrong.
If you crash or shutdown improperly Reader(RMSDK).apk will not get a chance to update the LRP.
P.S. I just noticed a possible anomaly if you read PDF's in the reader too.

Oh! It just occurred to me one thing.
I remember opening a book that you have been reading already and it opens at page 1.
This was tied to opening the book in different ways.
There are different ways to open a book:
Through the "Last Read" icon and stock Home.apk
Through the stock Library.apk
Through my Library.apk
Through a file manager application
The LRP database is /data/data/com.bn.nook.reader.activities/databases/lastreadingpoint.db
Code:
CREATE TABLE lastreadingpoint
(_id integer primary key autoincrement,
ean text, // file URI
luid text,
offsetrmsdk text, // subfile path fragment
lastupdated long, // Unix milliseconds last read
bookdna int, // always 1?
sync_status int // always 1?
);
ean (which normally might stand for European Article Number, i.e. "UPC") is a URI, not a path.
Code:
sqlite> select ean from lastreadingpoint;
file:///sdcard/Books/aboveall.epub
...
There may be cases where a single book gets different ean's.
If you could look at LRP and see if this is so?

I actually managed to locate that db file on my own (!) and what seemed to be a companion with related information (readerlocal.db). They seemed to be full of junk info (books that had since been removed, etc.) although there were no duplicate entries, which is what I had suspected.
Anyway, I got a little "brave" (i.e., foolhardy) and decided to clean up both files in a parallel way. Then I pushed them back, reset the permissions and rebooted.
Yikes. My Nook is set to go to the B&N Home screen only on reboot. That screen flickered and flashed, never filling in any of the images. I could still use the "N" button to access other parts of the system and they were working fine, but any return to the Home screen via the Back button showed it was still in distress.
So....restore from backup...again.
It seems OK for now. I have noticed that the little "refresh" button in the Library does sometimes seem to go on and on and on without any accomplishment. I have suspected the issue was how I accessed the book-in-progress as you described. Since I sometimes read more than one book at a time, I'm all over the place with how I do things (including a Library icon in my App home screen). I'm going to try being more disciplined for a while and see how it behaves.

nmyshkin said:
I actually managed to locate that db file on my own (!) and what seemed to be a companion with related information (readerlocal.db). They seemed to be full of junk info (books that had since been removed, etc.) although there were no duplicate entries, which is what I had suspected.
Anyway, I got a little "brave" (i.e., foolhardy) and decided to clean up both files in a parallel way. Then I pushed them back, reset the permissions and rebooted.
Yikes. My Nook is set to go to the B&N Home screen only on reboot. That screen flickered and flashed, never filling in any of the images. I could still use the "N" button to access other parts of the system and they were working fine, but any return to the Home screen via the Back button showed it was still in distress.
So....restore from backup...again.
It seems OK for now. I have noticed that the little "refresh" button in the Library does sometimes seem to go on and on and on without any accomplishment. I have suspected the issue was how I accessed the book-in-progress as you described. Since I sometimes read more than one book at a time, I'm all over the place with how I do things (including a Library icon in my App home screen). I'm going to try being more disciplined for a while and see how it behaves.
Click to expand...
Click to collapse
Would it be possible to write an app that simulates opening the last read book from only one of the Library apps and then map that to the last read icon to simplify this whole system?

mergen3107 said:
Guys, if you are concerned about why sometimes the last read option goes to the 1st page, then it was already fixed by our forum users somewhere here. (I could hardly remember and trace where it all started but finally it was successfully solved)
Just install a file this package (internal.db deep in the 'data' folder. You could delete 'system' folder - this is hyphenations dictionary for Russian) through cwm or replace it manually (the zip contains detailed path) and here you go.
Click to expand...
Click to collapse
Now that was an interesting trip! Once I had Google do some translating there were a number of really interesting posts that were (mostly) intelligible. I'd want to compare that modified internal.db file with what's already on my Nook before I did any replacing. A lot of the work from that site is "russified" (not surprisingly) and there may be other changes there not really needed/wanted, but it's a good start.
I noticed in another posting there that someone said there is a related issue with in what state the Nook is connected via USB. Apparently the hypothesis is that if you don't connect while in the Library you stand a good chance of scrambling the "reading now" database entry. I've certainly been hooking up with my Nook in all kinds of states, so if that's correct, no wonder my database file was so messed up!

Installation of the internal.db file from the Russian source will not work. I've tried a side-by-side comparison of the file with the one from my Nook (FW 1.21) and there are differences (beyond the region identifier, which is easily changed). It's not at all clear what changes have been made or from what firmware the modified file came. In any case, it causes havoc when exchanged for the native internal.db
The Russian discussion points to this thread on XDA which approaches (and apparently solves) the problem another way. I'm going to give it a try.

nmyshkin said:
Installation of the internal.db file from the Russian source will not work. I've tried a side-by-side comparison of the file with the one from my Nook (FW 1.21) and there are differences (beyond the region identifier, which is easily changed). It's not at all clear what changes have been made or from what firmware the modified file came. In any case, it causes havoc when exchanged for the native internal.db
The Russian discussion points to this thread on XDA which approaches (and apparently solves) the problem another way. I'm going to give it a try.
Click to expand...
Click to collapse
Do I read this correctly, http://bit.ly/Q7MytN from that thread there should be no problem if renates Library.apk is used exclusively and the stock Library.apk has the bug?

Blackberry APK

Hi everybody
I hope this is the right section for my question, if not, please don't kill me.
I'm a Blackberry Q10 user. We can run Android apps on Blackberry because there is a emulator that comes with the phone. Most applications run very smoothly, although there is one that doesn't work. And I just don't know why...
The Z10 (the bigger Blackberry) can run "The Simpsons Tapped Out" without any problems, although the Q10 (the Blackberry with touch and keyboard) cannot. When you launch the application it will show the splash screen (EA logo, etc) and then it will turn black for infinite time.
First I thought it was a resolution issue. I decompiled the standard APK from the Play Store, changing the resolution with some success. The splash screen is now the "normal" size for the screen (720x720). Rest is still the same. Then I thought, it might be a data issue. I've downloaded all the data, extracted it, etc. Without success.
Now, I am clueless, I'm not a programmer and I tried for several hours fixing the problem. I just can't, I need help on this on.
Would anyone here be so kind, helping me in this process of finding out why the screen turns black?
Kind regards

namenamename111 said:
Hi everybody
I hope this is the right section for my question, if not, please don't kill me.
I'm a Blackberry Q10 user. We can run Android apps on Blackberry because there is a emulator that comes with the phone. Most applications run very smoothly, although there is one that doesn't work. And I just don't know why...
The Z10 (the bigger Blackberry) can run "The Simpsons Tapped Out" without any problems, although the Q10 (the Blackberry with touch and keyboard) cannot. When you launch the application it will show the splash screen (EA logo, etc) and then it will turn black for infinite time.
First I thought it was a resolution issue. I decompiled the standard APK from the Play Store, changing the resolution with some success. The splash screen is now the "normal" size for the screen (720x720). Rest is still the same. Then I thought, it might be a data issue. I've downloaded all the data, extracted it, etc. Without success.
Now, I am clueless, I'm not a programmer and I tried for several hours fixing the problem. I just can't, I need help on this on.
Would anyone here be so kind, helping me in this process of finding out why the screen turns black?
Kind regards
Click to expand...
Click to collapse
You have to logcat, but since this is a BB device it's hard to help, maybe some libraries are missing in the emulator

mohamedrashad said:
You have to logcat, but since this is a BB device it's hard to help, maybe some libraries are missing in the emulator
Click to expand...
Click to collapse
The emulator comes standard with BlackBerry OS 10. The APK runs fine on a Z10 but not on a Q10. Is log cat an application?

Logcat is a program that tracks all system actions, you can read the log to debug your rom or apps
for your prblem i suggest that the game need specific resultion that is not avaiable on the small q10 screen

mohamedrashad said:
Logcat is a program that tracks all system actions, you can read the log to debug your rom or apps
for your prblem i suggest that the game need specific resultion that is not avaiable on the small q10 screen
Click to expand...
Click to collapse
I call bull**** on the last one.
Thanks for nothing XDA.