Skip to content

Liechtenstein Seek

FireBoard
Welcome, Guest
Please Login or Register.    Lost Password?
pre market future Updating a pre-installed application (1 viewing) (1) Guests
Go to bottom Post Reply Favoured: 0
TOPIC: pre market future Updating a pre-installed application
#3005
John Seghers (Visitor)
Click here to see the profile of this user
Birthdate:
pre market future Updating a pre-installed application  
Actually, if your app needs some functionality from the device that is not part of the platform, the proper way to do this is to put it in a shared library like this that the application uses (and the OEM implements).  This may just be what you want to do anyway. Our application doesn't actually need anything specific provided by the OEM for the app to run, but our app provides a service and content provider that the OEM then uses to obtain information. Since this integration is a key element of our product, it doesn't make sense to put it on a handset that doesn't have the OEM-level support. So I've created a project with a single class com.cequint.platform.CequintConfig . I've run dx on the resulting class files and packaged it in to a JAR file with a MANIFEST.MF similar to that in other .jar files I see in /system/_frame_work. Indeed, I just copied the MANIFEST.MF from monkey.jar. So my jar file is named com.cequint.platform.jar and contains: /_meta_-INF/MANIFEST.MF /classes.dex This jar file layout is the same for monkey.jar and com.google.android.maps.jar. I then remounted /system on an OEM development phone and pushed com.cequint.platform.jar into the /system/_frame_work directory. I added <uses-library android:name= com.cequint.platform / to a test application's <application section. When I try to install the test application, I get an error from adb install : Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY] What am I missing here?
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#3006
John Seghers (Visitor)
Click here to see the profile of this user
Birthdate:
pre market future Updating a pre-installed application  
Actually, if your app needs some functionality from the device that is not part of the platform, the proper way to do this is to put it in a shared library like this that the application uses (and the OEM implements).  This may just be what you want to do anyway. Our application doesn't actually need anything specific provided by the OEM for the app to run, but our app provides a service and content provider that the OEM then uses to obtain information. Since this integration is a key element of our product, it doesn't make sense to put it on a handset that doesn't have the OEM-level support. So I've created a project with a single class com.cequint.platform.CequintConfig . I've run dx on the resulting class files and packaged it in to a JAR file with a MANIFEST.MF similar to that in other .jar files I see in /system/_frame_work. Indeed, I just copied the MANIFEST.MF from monkey.jar. So my jar file is named com.cequint.platform.jar and contains: /_meta_-INF/MANIFEST.MF /classes.dex This jar file layout is the same for monkey.jar and com.google.android.maps.jar. I then remounted /system on an OEM development phone and pushed com.cequint.platform.jar into the /system/_frame_work directory. I added <uses-library android:name= com.cequint.platform / to a test application's <application section. When I try to install the test application, I get an error from adb install : Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY] What am I missing here?
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop

Newsflash

 Norwegian Minister of Justice did not sit at home and dived in the waters of the Arctic. I must admit that bad for the minister!


 

Login Form






Lost Password?
No account yet? Register

Syndicate

Who's Online

We have 21 guests online

The head of the robot on the dashboard - better than GPS

Sensitive to human emotions robot's head, mounted on the dashboard of a car should be - according to plastics Polish Pottery used cars developers - a better option than a modern GPS. The controversial idea informs the New Scientist. Audi specialists from the company and scientists from Massachusetts Institute of Technology are working on car that understands driving detox Used cars polen habits and emotions in order to better show his way. AIDA is a device placed on the joints of five "neck" wedge-shaped head, which was fashion trends iknowthatgirl toreuse.com placed inside the laser projector the size of a deck of cards. Projected image on the surface of the head mimics facial expressions suitable for the "mood" robot. Movement of the head and change "facial expressions" allow to express emotions - for example, fear associated with not wearing a seatbelt for the driver. To not worry about the car, you need to fasten belts - the method Steroids used cars used cars should be more effective than the typical warning buzzer. Numerous sensors provide data on the system, the mood of the driver - for example, forces with which squeezes the steering wheel or the conductivity of the skin, which is growing panic. GPS allows you to memorize your favorite places and Directions to find the best route. However, the system requires much more work if it is villas for sale Tag replica watch chiptuning really helping, and not interfere with driving.

kamieniarstwo warszawa
kamieniarstwo warszawa, kamieniars…
Komputery Apple
Komputery i akcesoria Apple
Suwnice
Urządzenia dźwigowe PANDA
projekty domów
projekty domów
przyroda
GotLink.pl