Related
Request is in the title - the LG Optimus One from Orange UK contains the Orange Signal Boost (UMA) software that would be useful to get working on other android phones with networks which support UMA. The topic is here but I've cross-posted here in case the topic gets lost in the general forum.
Here you go, This should be the original Orange V10C_00 firmware for your phone:
Code:
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AORUBK/V10c_00/V10C_00.kdz
I was thinking maybe someone with the Optimus One could just backup the apk for Orange Signal Boost and post that. I have tried expanding the rom posted in the link and have got as far as the mbn files and boot.img etc but I don't know how to get at the apk's...
Bump
Could any owner of optimus one share that app with us ?
please
Again, please anyone! We just need a backup of the apk to get started!
Sent from my HTC Desire using XDA App
Ok, I managed to unpack the KDZ file but still couldn't find a way extract the Orange Signal Booster apk from boot.img file; so if anyone has backup of the apk it would be greatly appreciated.
I tried the same thing but had no luck. If you had the handset you could use a number of different apps (astro, titanium backup) to make a backup of the .apk file with very little technical knowledge.
It would be god send if we could get this app running on other handsets...
Here is the APK!
OK here is the APK which I have extracted from the ROM image. I tried installing it on my desire and it FCs as soon as I attempt to run it. If anyone else wants to get onboard with this please do!
Hi ballandbiscuit, many thanks for the APK. Tried it on my HTC DHD and had the same FC result as you. As far as I can tell, this is not a hardware restriction but possibly the result of other system services required by the app not installed on the handset.
I really wish someone from Orange with a bit of technical knowhow would get involved and assist us with this much needed feature.
what about some kind of logging? maybe it say something...
Sent from my LG-P500 using XDA App
Here is some data from logcat
Code:
I/ActivityManager( 167): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.kineto/.kineto }
I/ActivityManager( 167): Start proc com.android.kineto for activity com.android.kineto/.kineto: pid=1695 uid=10103 gids={3003, 3002, 3001, 1015}
W/dalvikvm( 1695): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/android/kineto/kineto;.<clinit>
W/dalvikvm( 1695): Class init failed in newInstance call (Lcom/android/kineto/kineto;)
D/AndroidRuntime( 1695): Shutting down VM
W/dalvikvm( 1695): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
E/AndroidRuntime( 1695): FATAL EXCEPTION: main
E/AndroidRuntime( 1695): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1695): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 1695): at java.lang.Class.newInstance(Class.java:1429)
E/AndroidRuntime( 1695): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime( 1695): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
E/AndroidRuntime( 1695): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
E/AndroidRuntime( 1695): at android.app.ActivityThread.access$2300(ActivityThread.java:125)
E/AndroidRuntime( 1695): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
E/AndroidRuntime( 1695): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1695): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1695): at android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1695): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1695): Caused by: java.lang.UnsatisfiedLinkError: Library kineto not found
E/AndroidRuntime( 1695): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 1695): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 1695): at com.android.kineto.kineto.<clinit>(kineto.java:1552)
E/AndroidRuntime( 1695): ... 15 more
W/ActivityManager( 167): Force finishing activity com.android.kineto/.kineto
W/ActivityManager( 167): Activity pause timeout for HistoryRecord{46506b50 com.android.kineto/.kineto}
I/ActivityManager( 167): No longer want com.google.android.apps.uploader (pid 653): hidden #16
I/Process ( 1695): Sending signal. PID: 1695 SIG: 9
W/InputManagerService( 167): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 167): Process com.android.kineto (pid 1695) has died.
Not sure if this is relevant but earlier in the logcat...
Code:
W/PackageManager( 167): Not granting permission android.permission.DEVICE_POWER to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Not granting permission android.permission.UPDATE_DEVICE_STATS to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Unknown permission android.permission.INJECT_EVENT in package com.android.kineto
Having looked at some other posts regarding the T-Mobile US UMA app, which is also Kineto based I think it will take a lot of work to get this functioning. It appears to need some libraries such as...
libkento
linganril
librilswitch
and also some changes to the kernel as per this thread
http://forum.xda-developers.com/showthread.php?t=807116
I don't know if this was ever ported to devices other than the N1. It is shame that it requires more than just an app. Orange should be pushing this to all Android handsets. I don't use my phone at home for calls or texts because the signal is too weak, this is a loss for both myself and Orange because they don't get to charge me for calls I don't make. My wife has a Vodafone Sure Signal box which is brilliant but Orange don't offer such a device...
Okay, I just had a little luck with the UMA application.
Not quite there yet though.
BASICALLY, I have come to understand that the application extracted from various Roms FC cuz they are missing other files they depend on from the ROM.
I was using Orange Signal Boost apk from the Orange Desire S rom (am attaching it) on my HTC Legend.
Then I came across stories of someone in US who had extracted an apk from so Tmobile Rom for wifi calling and made it to work on a Nexus 1. I downloaded that files (also attached). This file was a modded version of original apk and had all the dependant files. (and consequently was 3mb vs 600kb of Orange signal boost)
So what I tried was
1. Install tmobile wifi app
2. Install Orange signal boost on TOP of it. It will ask you that this progam will replace another older program on your phone. Clcik okay.
3. What this does is leave old installed files needed from tmobile app and this time LO AND BEHOLD, signal boost app launches without FC
Here comes the problem though, it doesnt work, cuz somewhere hardcoded in the files that the tmobile app installs is the network info and naturally, our sims being orange are recognized as invalid sim.
Me and a LOT of other people would REALLY appreciate it if someone with any knowhow can look at this and figure it out for us
I am very happy to propose you my first custom rom for the HTC JetStream! This rom is based on the released rom from AT&T 1.30.502.1 and should work for both American and Canadian tabs. The system has been made as light as possible and all "unnecessary" application has been removed.READ CAREFULLY:
This rom does NOT include any kernel but works exclusively with DoomLord Kernel v1
Installing this rom will WIPE your device but can be done if this feature is needed
You need [URL="http://forum.xda-developers.com/showthread.php?t=1418084"]ClockWorkMOD [/URL]to install this ROM
You are doing this at your own risks
Rom Description:
This rom is my daily driver, I like my tablet, clean without any bloatware or unneccessary app or widgets from AT&T or HTC
Zipaligned / Deodexed
Rooted - latest version
Removed all unnecessary applications - see second post
Latest version 2.03.10:
Careful, this version will WIPE your device, make a backup!
Careful, the new version will WIPE your phone, make a backup!
I am not asking for donation but press the thanks button and please Vote for this thread tooCredits:
DooMLoRD for the kernel and CWM
mendozinas, for his online kitchen
dsixda, for his kitchen
Before asking a question, use this button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and watch this , thanks:
v2.03.10
New Boot animation
Roboto fonts included
Battery in %
Ad-Away an No-Frill included
All bloatware removed
Phone functions enabled
Tethering activated
Rooted
Latest Market
Busybox installed
Zipaligned
Fully de-odexed
Frequently Asked Questions:
Will this rom work with the default kernel?
Most probably yes but...
Wi-Fi will be broken
Can I revert to the default kernel on this rom?
Yes now you can! but follow the steps and I won't babysit
Download the file from my site called: Jetstream_OsiMood_DefaultKernelFiles.rar
Inside you will find 2 files JetStream_OsiMood_DefaultKernel_WiFi_Module.zip and defaultBoot.img
Once those two files unzipped in a folder
Move the zip file to your SD-Card
Once done, reboot in bootloader: adb reboot bootloader
Now time to flash the default kernel: fastboot flash boot defaultBoot.img
Now go in recovery and install the attached zip, the patch will install the correct WiFi module and wipe your cache
Reboot, you have now the default kernel running and WiFi working
Try to reboot in recovery if it does not work just re-install the DooMLoRD recovery
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
tyrannos said:
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
Click to expand...
Click to collapse
I know for the link, working on it... will let you know when back up
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Simply because it is working smoothly for me @1.8ghz and that is more than enough
The link is up
Downloading now, looking forward to trying this one!
Wait, so this will still work with the stock kernel, right?
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
Click to expand...
Click to collapse
I am going to see what I can do for that as it seems I am also facing some random reboots
Market
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Click to expand...
Click to collapse
You can now roll back to the default kernel
juannicolas said:
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
Code:
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
Click to expand...
Click to collapse
No clue why, empty the cache of the app and try again
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
for CWM - reset the device - and after the screen goes black press and hold vol. down.
so to install this rom we need to install the doomlord kernel and then go back to stock? or we can just install it over the stock?
can anyone actually work with the doomlord kernel to improve it? i think it was great at its base..perhapes just removing the voltage control..i think that's the problem it had.
CarpeNoctem said:
You can now roll back to the default kernel
No clue why, empty the cache of the app and try again
Click to expand...
Click to collapse
Tried that but since the app have never being opened there is no clean/clear cache option active for it.
NJFM said:
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
Click to expand...
Click to collapse
the simplest way, install this: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
CarpeNoctem said:
I am going to see what I can do for that as it seems I am also facing some random reboots
Click to expand...
Click to collapse
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Sent from my HTC Rezound™ using xda premium
k2trill said:
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Click to expand...
Click to collapse
Now you have the choice at least you, stock or DooMLoRD
its a fact that some devices sufford random reboots only when using the kernel. i think the kernel has a great base, and my device never ran faster - but it still crashed him.
i think it's got something to do with the Voltage control, but i can't really be sure.
Hey,
Ive got a Galaxy Tab 10.1 running stock 3.2. I encountered a strange problem with my tab today.
An app froze(google maps) - I could click the clock and the menu would roll up, it had a black screen and did nothing, so I reset the tab by long pressing power.
After this the tab got stuck at the SAMSUNG logo for a long time, so I tried another reset and then another after cleaning the connectors - the slot wasnt dirty but just in case. After I gave up and left the tab with the SAMSUNG logo for about 10 minutes it finally booted. But the weird part is that it booted like I have just performed a factory reset, but all my data is still there, all apps, heck even my background is the same.
Only thing is, that any app that has some connection to any account stored in on the tab is force closing. Its as if the accounts got corrupted.
Now this happened twice, first time I factory reset the tab and it was then ok, but a second time? I dont want to lose saved games, and stuff...
My question is, has this ever happened to anybody else? Can it be solved without data loss?
radqooo said:
Hey,
Ive got a Galaxy Tab 10.1 running stock 3.2. I encountered a strange problem with my tab today.
An app froze(google maps) - I could click the clock and the menu would roll up, it had a black screen and did nothing, so I reset the tab by long pressing power.
After this the tab got stuck at the SAMSUNG logo for a long time, so I tried another reset and then another after cleaning the connectors - the slot wasnt dirty but just in case. After I gave up and left the tab with the SAMSUNG logo for about 10 minutes it finally booted. But the weird part is that it booted like I have just performed a factory reset, but all my data is still there, all apps, heck even my background is the same.
Only thing is, that any app that has some connection to any account stored in on the tab is force closing. Its as if the accounts got corrupted.
Now this happened twice, first time I factory reset the tab and it was then ok, but a second time? I dont want to lose saved games, and stuff...
My question is, has this ever happened to anybody else? Can it be solved without data loss?
Click to expand...
Click to collapse
It happened to me 3 weeks ago, and all the applications were force closing. I had to uninstall them all, and then reinstall. I did not lose any document though.
Now, I feel that the default browser seems corrupted; Everytime I log in to Facebook, it asks me to to identify the current device.
ace81 said:
It happened to me 3 weeks ago, and all the applications were force closing. I had to uninstall them all, and then reinstall. I did not lose any document though.
Now, I feel that the default browser seems corrupted; Everytime I log in to Facebook, it asks me to to identify the current device.
Click to expand...
Click to collapse
That would make sense, the first time it happened I had the browser opened. I opened logcat to see what are the reasons of force closing, and its talking something about a corrupted database.
Here is an extract what happens when I want to run dropbox.
E/AndroidRuntime( 3182): FATAL EXCEPTION: main
E/AndroidRuntime( 3182): java.lang.RuntimeException: Unable to create application com.dropbox.android.DropboxApplication: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file
E/AndroidRuntime( 3182): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3702)
E/AndroidRuntime( 3182): at android.app.ActivityThread.access$1200(ActivityThread.java:122)
E/AndroidRuntime( 3182): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1065)
E/AndroidRuntime( 3182): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3182): at android.os.Looper.loop(Looper.java:132)
E/AndroidRuntime( 3182): at android.app.ActivityThread.main(ActivityThread.java:4126)
E/AndroidRuntime( 3182): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3182): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3182): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
E/AndroidRuntime( 3182): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
E/AndroidRuntime( 3182): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3182): Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:983)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:956)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:1021)
E/AndroidRuntime( 3182): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:772)
E/AndroidRuntime( 3182): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:221)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:149)
E/AndroidRuntime( 3182): at com.dropbox.android.provider.g.b(panda.py:185)
E/AndroidRuntime( 3182): at com.dropbox.android.DropboxApplication.onCreate(panda.py:59)
E/AndroidRuntime( 3182): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:968)
E/AndroidRuntime( 3182): at android.app.Ac...
Questions go in the Q&A section
Android Wear allows pairing to a new/second phone only after you perform factory reset of Android Wear: "You can switch which phone or tablet your watch is paired with, but you need to reset your watch to factory settings first. Then you can pair your watch to the new phone or tablet." Google Support
It's ok for most people but some just have more devices and want to switch them from time to time. Performing factory reset means compiling apps to aot, retransferring all apps the need to reconfigure all apps (Wear Mini Launcher, anyone?).
There used to be an app BeeLink but it stopped working and was removed.
There's actually way faster way how to set up connection with a new phone - in a minute. Just delete application data of "Google Play Services Wearable" app and reboot. All the 3rd party apps with their configurations, all watch faces with configurations, Google Fit data, and basically everything else will be kept.
Step by step
Wear is connected with phone A so turn off Bluetooth on this phone.
Execute following command on Wear (with ADB enabled - doesn't require root) or run attached app (root on watch required).
Code:
adb shell "pm clear com.google.android.gms && reboot"
Power on Bluetooth on phone B.
Depending whatever devices were paired previously, confirm pairing code or initiate new pairing using following command (thanks @matejdro) or also use the wear app for that
Code:
adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE"
Finish setup, let it work for some time and restart both phone B and your watch to properly apply all changes. Done.
Attached apk is for installation on mobile phone (it contains and installs the actual Wear app). It's not on Play Store yet. Let's try it and get some feedback first.
Hi,
Thanks for making this for those of us who know nothing about adb. Unfortunately, I could not get this to work, but I'm certain the error is at my end. I downloaded and installed your apk, but I can't get it to open or find it in the app drawer. Excuse my ignorance. Could you please inform me as to how I can run the apk after installation? I downloaded it on to phone B, which does not have android wear installed, as per your instructions. However, I never got passed step 2 of your guide for the above mentioned reason.
Thank you kindly
moneytoo said:
Android Wear allows pairing to a new/second phone only after you perform factory reset of Android Wear: "You can switch which phone or tablet your watch is paired with, but you need to reset your watch to factory settings first. Then you can pair your watch to the new phone or tablet." Google Support
It's ok for most people but some just have more devices and want to switch them from time to time. Performing factory reset means compiling apps to aot, retransferring all apps the need to reconfigure all apps (Wear Mini Launcher, anyone?).
There used to be an app BeeLink but it stopped working and was removed.
There's actually way faster way how to set up connection with a new phone - in a minute. Just delete application data of "Google Play Services Wearable" app and reboot. All the 3rd party apps with their configurations, all watch faces with configurations, Google Fit data, and basically everything else will be kept.
Run the following command on your pc (with Wear connected and ADB enabled - this doesn't require root) or use my app for switching on-the-go (it requires root on Wear).
Code:
adb shell "pm clear com.google.android.gms && reboot"
Step by step
Wear is connected with phone A so turn off Bluetooth on this phone.
Execute above command or run attached app (root required).
Power on Bluetooth on phone B.
Depending whatever devices were paired previously, confirm pairing code or initiate new pairing.
Done.
Attached apk is for installation on mobile phone (it contains and installs the actual Wear app). It's not on Play Store yet. Let's try it and get some feedback first.
Click to expand...
Click to collapse
rekil goth said:
Hi,
Thanks for making this for those of us who know nothing about adb. Unfortunately, I could not get this to work, but I'm certain the error is at my end. I downloaded and installed your apk, but I can't get it to open or find it in the app drawer. Excuse my ignorance. Could you please inform me as to how I can run the apk after installation? I downloaded it on to phone B, which does not have android wear installed, as per your instructions. However, I never got passed step 2 of your guide for the above mentioned reason.
Thank you kindly
Click to expand...
Click to collapse
this App needs to be Sync'd to the watch so download it to Phone A, which is already paired.
wait until it syncs or manually sync Apps in Wear App on phone A.
when it's availalbe on your watch, then start this procedure.
hmm, just tried this (both ADB command and App installed on watch) with a new phone and I couldn't get it to pair. had to do the watch reset
Not working for me either. Will try the adb route when I can and report back
Finally a solution to my problem.
When i flash a new ROM i have to pair my moto 360 again... And to do this i allways do a reset on my watch...
Next time i will try it and give a feedback.
Not working on moto 360 5.0.2, rooted?
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
matejdro said:
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
Click to expand...
Click to collapse
Hi, my SW3 was connected to my Mi 4, setup done and working fine. I used Titanium Backup to backup Android Wear and all the watch faces apps.
After I flashed a new custom ROM, used Titanium Backup to restore Android Wear and watch face apps, and also Bluetooth connections on my Mi 4. When SW 3 is connected to my computer, in Adb, it says unauthorised.
Since it is unauthorized, I can't run the ADB command.
Any suggestions?
I don't think there is anything you can do at this point. You should have authorized your PC when you still had working watch connection.
any plans to update it
matejdro said:
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
Click to expand...
Click to collapse
Using Minimal ADB, I had to run as admin to make this work, but then it worked perfectly. Thanks very much!
nothing. doesn't work with 5.1.1 g watch rooted, the app gives me black screen (dismissable with swipe)
Just using app from OP is apparently not enough anymore on 5.1.1.
I just made tutorial on reddit on how to reset 5.1.1 watch: https://www.reddit.com/r/AndroidWear/comments/3c4qf8/tip_how_to_switch_phones_without_hard_reset/
I updated the Wear app (v0.2) with support for requesting Bluetooth discoverable mode as well.
Did you guys see this: https://developer.android.com/training/wearables/apps/bt-debugging.html
Yes! I'm so glad something like this has been developed! Worst part about switching ROMs is resetting android wear now. Thanks so much!
Performed the clean in the watch.
It works, and is possible to link the watch with another phone without perform a data wipe.
Then only problem that I've encontered is that the installed watchfaces aren't visible in the Android wear app (in the phone), and I can't set from the phone or hide some.
Thanks
EDIT: Sometimes, due to the watchfaces issue, Android wear app UI generates a FC
Code:
E/AndroidRuntime( 6255): FATAL EXCEPTION: main
E/AndroidRuntime( 6255): Process: com.google.android.wearable.app, PID: 6255
E/AndroidRuntime( 6255): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.content.ComponentName.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.loadWatchFaces(WatchFacePreviewFragment.java:261)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.onWatchFacesLoaded(WatchFacePreviewFragment.java:209)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:198)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:33)
E/AndroidRuntime( 6255): at android.os.AsyncTask.finish(AsyncTask.java:636)
E/AndroidRuntime( 6255): at android.os.AsyncTask.access$500(AsyncTask.java:177)
E/AndroidRuntime( 6255): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
E/AndroidRuntime( 6255): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 6255): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 6255): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 829): Force finishing activity 1 com.google.android.wearable.app/com.google.android.clockwork.companion.StatusActivity
bartito said:
Performed the clean in the watch.
It works, and is possible to link the watch with another phone without perform a data wipe.
Then only problem that I've encontered is that the installed watchfaces aren't visible in the Android wear app (in the phone), and I can't set from the phone or hide some.
Thanks
EDIT: Sometimes, due to the watchfaces issue, Android wear app UI generates a FC
Code:
E/AndroidRuntime( 6255): FATAL EXCEPTION: main
E/AndroidRuntime( 6255): Process: com.google.android.wearable.app, PID: 6255
E/AndroidRuntime( 6255): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.content.ComponentName.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.loadWatchFaces(WatchFacePreviewFragment.java:261)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.onWatchFacesLoaded(WatchFacePreviewFragment.java:209)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:198)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:33)
E/AndroidRuntime( 6255): at android.os.AsyncTask.finish(AsyncTask.java:636)
E/AndroidRuntime( 6255): at android.os.AsyncTask.access$500(AsyncTask.java:177)
E/AndroidRuntime( 6255): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
E/AndroidRuntime( 6255): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 6255): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 6255): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 829): Force finishing activity 1 com.google.android.wearable.app/com.google.android.clockwork.companion.StatusActivity
Click to expand...
Click to collapse
Did you also try reseting app data of both Android Wear and Google Play on the phone (& restart)?
moneytoo said:
Did you also try reseting app data of both Android Wear and Google Play on the phone (& restart)?
Click to expand...
Click to collapse
yes, performed a reboot in the wear and also a wipe in the phone
After trying to boot my phone several times with an almost empty battery the phone won't boot any more. The boot process hangs in the Jiayu logo (the phone is a Jiayu S3). The phone gets hot, so maybe it is doing something CPU intensive??? I can connect to the phone via adb. Command "adb logcat" shows several messages flowing constantly. The most severe message as far as I can tell is the following:
Code:
E/AndroidRuntime( 841): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 841): java.lang.RuntimeException: Unable to find android system package
E/AndroidRuntime( 841): at com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java:2069)
E/AndroidRuntime( 841): at com.android.server.SystemServer.startBootstrapServices(SystemServer.java:500)
E/AndroidRuntime( 841): at com.android.server.SystemServer.run(SystemServer.java:338)
E/AndroidRuntime( 841): at com.android.server.SystemServer.main(SystemServer.java:241)
E/AndroidRuntime( 841): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 841): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 841): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959)
E/AndroidRuntime( 841): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754)
E/AndroidRuntime( 841): Caused by: android.content.pm.PackageManager$NameNotFoundException: android
E/AndroidRuntime( 841): at android.app.ApplicationPackageManager.getApplicationInfo(ApplicationPackageManager.java:286)
E/AndroidRuntime( 841): at com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java:2051)
E/AndroidRuntime( 841): ... 7 more
I think that the error comes from this line in com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java):
Code:
ApplicationInfo info =
mSelf.mContext.getPackageManager().getApplicationInfo(
"android", STOCK_PM_FLAGS);
Is there a fix for the message "Unable to find android system package" (package "android")? For example, would re-installing an .apk (which one?) fix this?
I would rather not reflash the ROM. I would like to preserve the data I have, such as text messages, WiFi passwords and WhatsApp contents.
I have already tried twice wiping cache and Dalvik cache.
My phone is Jiayu S3 with stock Android 5.1. It is rooted and has TWRP.
Now only fastboot, adb and TWRP Terminal work for my phone (Jiayu S3). Android user interface won't start, it just shows the Jiayu logo. Is there any command (in fastboot, adb or TWRP Terminal) which would reset the Android user interface so that I could boot into the graphical user interface again?
The phone is the "Jiayu Deutschland" version and it has TWRP 2.8.7.0 and Android 5.1.1. I do not have the original ROM files so I can't just reflash it.
I still haven't made any progress. Android boot just shows the logo and does not open the normal UI. adb logcat displays repeated error "Unable to find android system package". The only things that work are fastboot, adb and TWRP. So basically I have the command line, but not the graphical user interface.
How could I debug error "Unable to find android system package"? Are there any helpful logs? So far I have looked at adb logcat, dmesg and files in /data/anr.
How can I verify that CLASSPATH is OK during boot? What file contains the android system package, how can I verify it? Should I try regenerating dex files? I have already wiped cache and Dalvik cache.