Related
When I dial a call all that happens is it places the call through verizon and not google voice any one else have this issue?, The guy at the store ran the ota before I was even handed the phone...
*Update 1 (4:13 pm): google voice seems to crash when rebooting =\
*Update 2 (4:23 pm): ADB Logcat output with grep on voice
Code:
[email protected]:~/Desktop/****/SDK/android-sdk-linux_86/tools$ cat adb.log | grep voice
W/PackageManager( 74): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
D/HtcCdmaPhoneApp( 111): voice privacy setting=1
D/HtcCdmaPhoneApp( 111): voice privacy status=-1
I/ActivityManager( 74): Start proc com.android.voicedialer for broadcast com.android.voicedialer/.VoiceDialerReceiver: pid=336 uid=10042 gids={3002}
D/VoiceDialerReceiver( 336): onReceive Intent { action=android.intent.action.BOOT_COMPLETED comp={com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver} }
D/RecognizerEngine( 336): deleteCachedGrammarFiles /data/data/com.android.voicedialer/files/openentries.txt
D/GooglePartnerSetup( 341): voicesearch client id: ms-android-verizon
I/ActivityManager( 74): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=348 uid=10049 gids={3003}
E/dalvikvm( 348): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
W/dalvikvm( 348): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent;)V
W/dalvikvm( 348): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
W/dalvikvm( 348): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver;)
E/AndroidRuntime( 348): java.lang.VerifyError: com.google.android.apps.googlevoice.BootUpReceiver
I/ActivityManager( 74): Process com.google.android.apps.googlevoice (pid 348) has died.
-Chr1831
Yes it started crashing here after the MR2
Snakehn said:
Yes it started crashing here after the MR2
Click to expand...
Click to collapse
I can confirm this on my end as well. After the first OTA update there was no issue, but MR2 screwed with it. I found I can launch the application after the initial boot crash, but haven't confirmed that it is working as it should on my phone.
I get GV FC's on startup but then again I only use it for voicemail and its working pretty good.
I got version 2.5 to work just not 3.0 hopefully the (htc) update on the 22end will address this bug
Still some issues for me. It FCs on boot. All though most functionality is there..
When I call out things are strange, contact pics don't work and the outgoing number is not the dialed number its the GV "bridge" number.
Both of the above issues do not exist on my moto droid.
I wish it was fixed.
Wifi Calling now working! This is a T-Mobile US only feature as your phone carrier must have the architecture on their end for this to work.
Wifi Calling still uses your minutes as if you were connected to a tower.
Wifi Calling turns off your cellular radio when it's connected. This saves power and will also show -113dB signal.
Wifi Calling also sends SMS and MMS over wifi.
[11/10/10 v1.0]
-fixed kineto_ko kernel module. its now included and loads on bootup, compiled from cyanogenmod-exp kernel
-should make it easier for everyone past and present to get wifi calling up and running.
-temporarily disabled bundled kineto app, it was causing problems so until I figure it out I'm not including it with the update.zip
Thanks to Rsotbiemrptson for getting the Libraries and everything into an update.zip.
Thanks to intersectRaven for the kernel mod's regarding kineto and applying the WiFi PM FAST patch.
Thanks to Myshkinbob for the research and creating PM FAST patch.
To Install
1)If you don't have the 5.08 or 5.12 radio installed you MUST install that first!
2)Download and flash the Wildmonks or intersectraven kernel(before flashing kineto!)from the links below
3)Download and flash kineto-n1-bundle attached below.
4)Download and install MS-HTCVISION-KNT20-02.apk
5)If you install any kernel, 720p hacks or mods it can break wifi calling.. any time you flash an update.zip re-flash the kineto bundle. There are important libraries linked in build.prop that must be in or there will be problems. You can attempt to make a custom build.prop or post in the forum for help.
5)Enjoy!
Known Issues
-Bluetooth - Calls are not being connected to a bluetooth at this time.
-Bootloops on enabling wifi - Update your radio! 5.12 or 5.08 is required.
-After flashing if you still experience call problems it will be necessary to change your setcpu screen off profile to 245min 384max.
-Volume is low
-Sporadic MMS sending problems(APN related)
intersectRaven Kernels
CM Based Kernel 20101108_1328 - http://www.mediafire.com/download.php?4obtdv52efkvece
NON-CM Based Kernel 20101108_1328 - http://www.mediafire.com/download.php?urv9wl2ek0fae9c
wildmonks Kernels
http://forum.xda-developers.com/showthread.php?t=693375
dekips said:
Credit to the G2 OTA Update thread and Stryf3 for the APK extraction. I've installed this but I keep getting "Please wait while connecting to T-Mobile". I figured I'd upload it here for fellow N1's while I played with it.
*Update with logcat:
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
E/KINETO ( 312): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 312): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 312): onReceive Exit
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 312): onReceive Enter
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
E/KINETO ( 312): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 312): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 312): onReceive Exit
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
D/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
E/KINETO ( 312): KLOG0C3- xmk_QueryOSQueue SDL Queue empty : WAIT_FOREVER
E/KINETO ( 312): KLOG0A3- ibs_os_GetMsg: Timeout forever for UKCC qHnd 0x814310a4
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 312): onReceive Enter
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
Click to expand...
Click to collapse
same here stuck on enabling.....please someone fix...keep us posted please
From the looks of things, there is an underlying app that the Wifi Calling app connects to. Any thoughts?
dekips said:
From the looks of things, there is an underlying app that the Wifi Calling app connects to. Any thoughts?
Click to expand...
Click to collapse
Kineto apk has a oss.html which calls out files used for IPSec VPN connections. I suspect some VPN magic at work.
daijizai said:
Kineto apk has a oss.html which calls out files used for IPSec VPN connections. I suspect some VPN magic at work.
Click to expand...
Click to collapse
It's possible there is a tunnel which it is trying to establish, I'd like to think that it would only do that when the wifi calling is enabled. I'm getting a crazy flow from logcat of it trying to connect even when wifi calling is off and wifi is off.
There is a local daemon or missing piece of software it can't connect to. Is this application in the radio or is it another apk?
Ive stripped it down and am in the process of reading, but it needs to be set to try to connect to something or somewhere, without the datafile that tells it where to connect to it just cycles a connect to localhost
the package just loops trying to connect to 127.0.0.1
Viralblack said:
Ive stripped it down and am in the process of reading, but it needs to be set to try to connect to something or somewhere, without the datafile that tells it where to connect to it just cycles a connect to localhost
the package just loops trying to connect to 127.0.0.1
Click to expand...
Click to collapse
I'm in the process of getting a full update.zip.. no luck tonight so I'm calling it and goin to bed
I want to guess that it *could* possibly be in a host file.... It seems like it is doing a port loopback, to the radio... I assume...
do we have an IRC to talk to the guy that pulled this out of his phone?
It could be in the hosts file. I hope we get this soon, because I have like zero service in my apartment and this will be amazing
iria said:
It could be in the hosts file. I hope we get this soon, because I have like zero service in my apartment and this will be amazing
Click to expand...
Click to collapse
can someone get a line in to the guy(s) that has the file?
same problem
im getting same as everyone else
Here's a quote that might clarify some things:
So here’s the update on yesterday’s reported OTA update to the G2, which brought Wi-Fi calling and mobile hotspot creation to a very small set of users. T-Mobile released this official statement to clarify its position:
“Wi-Fi Calling and tethering Wi-Fi sharing are not currently supported on the T-Mobile G2. T-Mobile knows these features are important to consumers and we’re working to deliver them to G2 users in the future. We have nothing further to announce at this time.”
It’s pretty much what they’ve said before on the subject, and it doesn’t tell us much. It could mean that the update we saw yesterday was just a test and won’t be rolled out to the rest of G2 owners. Or it might be a test sample to see how these features affect data traffic, in order to help T-Mo with pricing. Or maybe they really are rolling it out to everyone and just haven’t put the support feautres, etc. in place yet.
via PhoneScoop by way of TmoNews
Click to expand...
Click to collapse
Just installing the apk won't be enough. There are a few libraries that will be needed as well. The kineto libraries and module(s) will be needed as well. The path to the RIL will have to be redirected also. This is likely changed via the build prop. A full system dump from a WiFi calling equipped G2 would be needed.
I still have not been able to source the original G2 OTA update.zip nor have I any luck finding someone with an updated G2 to pull specifics on the Kineto app configuration. If anyone has any luck with any of the above please post.
dekips said:
I still have not been able to source the original G2 OTA update.zip nor have I any luck finding someone with an updated G2 to pull specifics on the Kineto app configuration. If anyone has any luck with any of the above please post.
Click to expand...
Click to collapse
A co-worker recently obtained a G2. I will see if he has gotten the update, and if so, if he will help us
bennettm89 said:
A co-worker recently obtained a G2. I will see if he has gotten the update, and if so, if he will help us
Click to expand...
Click to collapse
yeah he should have the same problem and once they go online meaning tmobile it will and should automatically configure itself like ota
Weird thing is that I installed this and it actually worked, or at least looked like it worked for a minute. I got a new icon on the taskbar when calling with it enabled, and the call went through fine.
I turned the wifi calling off and then back on and now it is acting like everyone else's now... stuck on enabling.
Not sure if it actually was working for that one call, but it sure seemed like it. Wish I would have thought to grab a screenshot.
I'm stoked. I really need this at home.
Same here. When I originally installed the app, I had WiFi turned on and was at home near my UMA router. Worked fine until I disabled the application and attempted to re-enable it. Now stuck on enabling like everyone else.
Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!
Hey guys,
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time. (yes I set the permissions to 0644)
Does anyone ... has anyone tried moving / porting this?
Pulled the Dialer from here
http://www.androidpolice.com/2013/1...n-doesnt-show-up-in-my-app-tray-what-can-i-do
Sparatan117 said:
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time
Click to expand...
Click to collapse
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.
I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.
What do I win for being right.. ?
ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3
.
fffft said:
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.
I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.
What do I win for being right.. ?
ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3
.
Click to expand...
Click to collapse
You know, I would have loved if it had worked, but it didn't ...
I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache
... still force close... thoughts?
EDIT:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Edit 2: Nevermind haha
Resorting to flashing via Recovery. See if this works
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Sparatan117 said:
You know, I would have loved if it had worked, but it didn't ...
I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache
... still force close... thoughts?
EDIT:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
Are you using a stock unmodified rom?
Like with just towel root or something similar?
Sparatan117 said:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
Okay, I get it.. you don't want to pay off the bet.
=8-0
Sure, whatever. Glad it's working for you though. And it works for the rest of us too.
Good enough.
.
---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------
Sparatan117 said:
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Click to expand...
Click to collapse
Seriously? That doesn't make any sense.
I installed it on two systems and it was super easy and has been super stable. And there are 100+ comments on the original article without anyone there having issues either. Write out a detailed description of all the steps you took to install it so we can see where you went wrong.
.
Yeah well I guess pretty close to stock
I have Beans NF6 Factory build (upgrade without wiping data)
I have Chainfire's autoroot
Flashed TWRP recovery
Flashed the file via this ( http://www.androidfilehost.com/?fid=23269279319196848 ) file.
Wiped Dalvik/Cache via TWRP
Rebooted
Wiped data in App Manager
Started.
[insert picture of dog poop]
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Sparatan117 said:
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Click to expand...
Click to collapse
Okay, two of you ran into problems trying to install it. Still just a minor glitch.
To troubleshoot this though, we need you to be a lot more detailed. You didn't mention a lot of things.. e.g. you didn't say anything about checking permissions in your description.. so did you? And what was the result? Did you check the md5? Did you wipe the cache from the Application manager.. you only mention wiping the data. I know, picky, picky. But troubleshooting is all about the details. And we need to those things if we are to pin down the cause.
I'm also wondering about the order you wiped the data /cache. It's normally done in the reverse and that may be causing you problems. Wiping Dalvik should be the last step.
This procedure works. I've tried it three times now:
Check md5 of download
Move dialer to /system/priv-app
Confirm that permissions are 0644
[you can try running it at this point if you want to. it will force close at this point]
Open the Application manager i.e. Settings > Applications > Application Manager > All > Google Dialer
Force Stop > Clear cache > Clear data > OK
Reboot to recovery mode > wipe cache + Dalvik
Reboot to system
Open app drawer, click on Google Dialer & observe that it works properly
.
bumpkiss
Code:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): returning null in getPersonasForUser
E/MotionRecognitionService( 746): mReceiver.onReceive : ACTION_USER_PRESENT :: UNLOCK SCREEN
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_ANIMATING: true
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_EXPANDED: true
E/ActivityThread( 4896): Failed to find provider info for com.dropbox.carousel.CuOwnerCheckProvider
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_COLLAPSED: false
E/PersonaManagerService( 746): Unable to read user list
E/ActivityThread( 5740): Failed to find provider info for com.amazon.dcp.settings
E/Watchdog( 746): [email protected] 2
E/ConnectivityService( 746): Attempt to connect to mobile_mms failed (dataEnabled).
E/PersonaManagerService( 746): Unable to read user list
--------- beginning of /dev/log/main
E/MTPJNIInterface( 6390): Status for mount/Unmount :mounted
E/MTPJNIInterface( 6390): SDcard is available
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]
E/ ( 6390): [mtp_init_device] After open the MTP fd = 59 and line = 678...
E/MTPJNIInterface( 6390): Getting gadget reset status0
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false
E/SMD ( 257): DCD ON
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/MTPRx ( 6390): state from USB_STATE event DISCONNECTED
E/MTPRx ( 6390): ignore this event
E/DataRouter( 267): USB Interface is open with 0x9
E/SMD ( 257): ***Received data notification[DR->SMD]***
E/SMD ( 257): Path set is DATA_PATH_DR_SMD_MANAGER
E/SMD ( 257): Message:
E/SMD ( 257): Sending data to SMD: Len = [3]
E/SMD ( 257): buffer = []
E/SMD ( 257): Wrote 3 chars to SMD PORT fd=7 ch = 81
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/MTPRx ( 6390): state from USB_STATE event CONNECTED
E/MTPRx ( 6390): state from USB_STATE event DISCONNECTED
E/MTPRx ( 6390): stop observing and calling usbRemoved
E/MTPRx ( 6390): sendbooster is false!
E/MTPRx ( 6390): In usbRemoved Status bar enabled
E/MTPRx ( 6390): Sending Broadcast
E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false
E/MtpService( 6390): onDestroy.
E/MtpService( 6390): Unregister Mtp disable Receiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): Unregister mtpEmergencyReceiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 6390): Receiver not registered: [email protected]
E/MTPJNIInterface( 6390): noti = 3
Sparatan117 said:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
Click to expand...
Click to collapse
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.
Meanwhile, the dialer works here.
.
fffft said:
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.
Meanwhile, the dialer works here.
.
Click to expand...
Click to collapse
Does it work if you click the call button?
aooga said:
Does it work if you click the call button?
Click to expand...
Click to collapse
Yes it does (just tried it)
Sorry, I did follow your procedure to the letter, and the last post I posted was the result.
I'm thinking it's just not going to happen. Maybe a full system wipe is needed... or something. Who knows. Thanks for trying though.
Hi everybody,
I have installed Android-x86 on a Virtual Box VM. I'm trying now to activate bluetooth capability on it.
I plugged-in my usb bluetooth dongle, I mounted it in my VM. Everything is ok so far.
On Android side, I can detect my dongle through the hciconfig and scan with it with hcitool.
The problem appears when I try to enable it in the graphic interface. It always shows me Bluetooth as off.
When I try to move the button on the right to activate it - nothing happens... It completely ignores my attitude.
It is also not possible to enable it through the applications: when an app asks me for an authorization to allow bluetooth, I authorize it to do so but it doesn't succeed.
The error I observe through the adb logs is as follows:
723338-01-21 11:02:23.948 1378 2327 D BluetoothManagerService: enable(com.android.systemui): mBluetooth =null mBinding = false mState = OFF
723474-01-21 11:02:23.948 1378 2327 D BluetoothManagerService: enable returning
723549-01-21 11:02:23.949 1378 1415 D BluetoothManagerService: MESSAGE_ENABLE(0): mBluetooth = null
723644:01-21 11:02:23.949 1378 1415 E BluetoothManagerService: Fail to bind to: Intent { act=android.bluetooth.IBluetooth }
But it doesn't help me much...
Please, if you have any idea how to solve this issue or progress in locating the problem, it would be great.
Thanks in advance for your time!