Results 1 to 3 of 3
  1.    #1  

    I need the knowledge from our mighty webos-internals hackers... or anybody else, that might know something like that...

    I want to read the com.palm.message:1 database from a node.jsjsjs $service$. $The$ $easiest$ $way$ $to$ $get$ $access$ $to$ $the$ $db$ $is$ $to$ $just$ $name$ $the$ $service$ $somethig$ $with$ $com$.$palm$. $in$ $the$ $beginning$. $So$ $far$, $so$ $easy$...

    The issue now is, that it seems that node.jsjsjs $services$ $with$ $com$.$palm$.* $in$ $the$ $beginning$ $of$ $their$ $name$ $are$ $not$ $able$ $to$ $run$. $I$ $get$ $a$ $strange$ $activity$ $manager$ $issue$ $whenever$ $I$ $try$ $to$ $call$ $my$ $service$, $no$ $matter$ $if$ $that$ $is$ $from$ $an$ $app$ $or$ $via$ $luna$-$send$ $or$ $anything$...

    Other people seem to have the same issues:

    Is there an easy solution to that?

    I'm currently wondering a bit how mighty impostah is accessing all the databases without a com.palm.* name... hm.

    I hope somebody can shed some light on that for me.

  2. #2  
    I think Impostah uses a custom service to do the heavy lifting. You could try adding your app into the permissions by updating the DB kind (I think... I'm sort of mixing up service permissions and DB permissions), but you'd have to get a privileged app to do that first...
  3.    #3  
    Yes, that's true.. If I add the permissions to read from the db with my custom not-com.palm-app id everything works as expected... so I'd need a second app for that.. *sigh* Or I'd need people to do that from the command line with luna-send, like I did for my tests

Posting Permissions