Hi,
Having trouble with connecting Bluetooth with a Generic Android Tab KitKat 4.4.2
I used the app 'GoNext Update' and it says the tablet cannot update further than the 4.4.2 !
Okay just spoke PayPal Here Support and they said that if it connects and works with 1 device then the prob is not with the Reader.
It works with Samsung Note 5 os 7.1 but not with the Galaxy S4 (Android 5.0.1) which says I can't update.
She did say as far as she knows it should work with the Android KitKat 4.4.2 ( an Android Tab I have) and the Samsung Galaxy S4 which I also have.
The PayPal Here software app works but it is I cannot connect Bluetooth to the PPH Reader or have it stay paired..
Maybe the PPH reader can only be paired with 1 device at a time? Whilst not not connected in the PPH software app, it still shows as paired in all devices.
I am not sure what the Generic Tablet is as it is does not have a name.
These are its specs.
Model # ba 1078
Processor Quadcore-A33
Android 4.4.2
Firmware V2 (no updates available)
Kernel 3..4.39 [email protected]#44
Fri Oct 16 14:20:42 CST 2015
Build astar_ba1078-eng 4.4.2 KVT49L 20151016
Any help please?
Thanks
oz
Looks like I have found the problem.
No thinking it was a problem. I left the PPH reader 'paired' in all devices as I tried them all.
I unpaired them all then paired just the one I need (Generic Tablet) and it worked.
Problem is it drops off after a few minutes. Maybe when one or both 'sleep'.
Can one alter this 'sleep' time or turn it off totally?
oz
Hi !
A good method to avoid any device to go to deep sleep and interrupt some processes , though the bluetooth sholdn`t do that , is to keep the screen on until it finishes the job , always on preferable
Try it out
Many thanks..
Related
Hi!
I have a S2 (I9100G) since 2 years.
Before switching on CyanogenMod (2013 september), I don't had any problem to connect aWiimote to play some games (via Bluetooth).
Since 2013 september, I use a I9100g with CM (10.1.3 during january. Before I was in 10.1.3RC-1 and RC2 and before in 10.1.2).
Since, impossible to use Wiimote and WiimoteController, I have a error message.
So, I bought a Wamo Pro gamepad. It work on friends S2, S4 or android tablet. But impossible to connect the Gamepad (bluetooth paring) to my phone.
The phone see the bluetooth device, I select the device, it appears that connect, but no.
It seems there is bluetooth problem on cyanogenmod without solution (driver problem).
I try almost each nightlies, without succes.
Do you have any idea?
I don't want uninstall CyanogenMod...
Unfortunately, I can't post in the CM11 dev's topic, I don't have 10 posts at this time on this forum.
thanks for your help.
Any idea?
Hi,
I bought the SmartWatch 2 (SW2) and it arrived a week ago.
I have a THL w3 device, with Android 4.0.4 on it(built in; not a custom rom) and rooted.
When it first arrived about a week ago, I tried to connect it again and again and the SW kept displaying the SW->Smart Connect screen. the Smart Connect didn't show that popup window with a link to install the SmartWatch2 app, and even when I installed in manually there was no "edit settings" row in the Smart Connect app.
I tried to connect it to my friend's Motorola Atrix (Jelly Bean, not sure which one) and it worked, and then when I tried again on my phone it seemed to work. I was able to install some applications and even though whenever I turned the SW off and on or the Bluetooth off and on I had to unpair and pair the SW in order to connect it, not to mention that 90% of the times when I paired them there was no pairing request, the phone said it's paired, the SW got stuck on the screen "SW V phone"(connected) but they weren't actually connected.
A few days later, yesterday, I noticed that what i just described only happends when the phone is completely on and ready to use, because if I rebooted my phone and then when it turned on I emiddiatly paired them, it worked and there was a pairing request and everything. but only if I paired them before all the apps were ready, which meant that there was an app that caused the pairing to fail when that app is ready.
I used "Disable Manager"(from the Play store) to disable the Smart Connect app and then I was ablt to pair the phone and the SW properly, only now because the Smart Connect app is disabled I can't use the watch...
I hope I described what happened even though English is not my strongest language...
Summury:
My phone is not fully compatible ith the SW, and the fault is Smart Connect's.
The Motorola Atrix works perfectly with the watch. Is it because of the android version?
If you have any ideas please let me know.
-Reuven
Having trouble understanding, but if the problem is your device's stock rom you could look into trying a custom AOSP rom. Might aswell get something more recent than icecream sandwich. Get on kitkat. Get cyanogenmod 11 and use Gravity box with xposed modules.
Are there any custom mods for my device?
The problem is I couldn't find any custom roms for THL W3. it's not a popular device, and even though I really want a newer version(at least Jelly Bean...) I searched a bit and I didn't find anything.
Is cyanogenmod compatible with every phone? Are you sure that's the problem?
Hi,
I am trying to pair my Huawai mediapad m3 with my new Samsung gear S3. Unfortunately after installing the the gear manager on my Phablet it is not even recognizing the watch by scanning reachable devices .
Is their any possibility to make both devices communicate?
EMUI Version 4.1
Android Version 6.0
Anybody who could help me in this? :fingers-crossed:
Hi
Same problem here.
Did you manage to pair the watch?
The Gear Manager app isn't compatible with tablets. Not even Samsung's own tablets (including those that are fully functioning smartphones). I keep my watch remotely connected to a cheap phone that's permanently docked on my home wifi.
My Samsung S6 SM-G920I with Android 6.01 was working fine on mirrorlink connect to my Honda Jazz 2015.
But my phone can't connect to my car anymore after update to Android 7.0 nougat few days ago. My car touch screen shows " Smartphone not compatible" and my phone screen gone black with" Your device and car are connected via MirrorLink". I re-connect and restart my phone & car many times...no luck.
I tried change USB cable and repair Bluetooth, still doesn't work. I can not downgrade back to Android 6.01.
I contacted with Samsung Technical support Australia. Their answer is: "the mirror link no longer functioning since Android 7 Nougat update released, although Samsung phone's setting still has mirror link optional setup. They can not do anything about it. That is Google's problem." What?
Samsung should warn all the user such function will be removed before they update the firmware to Android Nougat 7.0.
Could anyone help me for this issue, please.
Thank you very much.
Same here; Updated to Nougat, Mirrorlink is no longer functioning. I purchased Sygic Navigation specifically because this was the only navigation app supported by Mirrorlink. Anyone got any ideas?
I have 2 galaxy s 7 one IS factory unlocked and other international unlocked international model still working after 7.0 update but US model no more working and I guess mirror link version might be different in my 2 devices. Hope once the mirror link in the vehicle is update possibly will work
@Louis Che
Louis, Did you find solution for this problem ?
Thanks.
When I plug in my Huawei E3372h-153 (with compatible Three SIM card), the head unit shows 'No service' and an empty signal meter in the status bar.
When I plug it into my tablet, it works instantly.
The USB dongle is out in the open and in a signal-covered area so this is definitely an issue with the head unit somewhere.
This is the unit (Dicola CHS7047X).
Rockchip PX5 (2017)
ARM Cortex-A53 Octa-core ≤ 1.5GHz (28nm)
PowerVR G6110 GPU (2014)
4 GB DDR3
AOSP Android 8.0
1024x600
STMicroelectronics TDA7388 audio power amplifier (2013)
STMicroelectronics TDA7786 AM/FM funer (2016)
In the software itself, it shows:
Manufacturer: rockchip
Model number: PX5
Android version: 8.0.0
Android security patch level: October 5, 2017
Kernel version: 4.4.93+; [email protected] #121; Fri Jan 26 10:41:07 CST 2018
Build number: px5-userdebug 8.0.0 OPG5.170623.007 eng.hct.20180126.113204 test-keys
MCU version: MTCE_CHS_V2.76_1; Dec 20 2017 15:49:46
CPU: 8 core 64-bit CPU Coretex-A53 @ 1.5G
Any ideas?
It's rooted, if that helps.
King Mustard said:
<post snipped>
Click to expand...
Click to collapse
Anyone have any ideas?
I use the app PPP Widget (3) for that. Install the app, place the widget (large enough, so stretch it if possible)
Then connect the dongle via usb and wait till something gets recognized. you may grant root access for the app on first click. Afterwards you can click onfiguration button and pu tthe needed information in there. If the connection works, you can enable the auto connect feature in the settings of the widget.
That is how i managed to get a 4g stick working just this morning
Iced-Earth said:
I use the app PPP Widget (3) for that. Install the app, place the widget (large enough, so stretch it if possible)
Then connect the dongle via usb and wait till something gets recognized. you may grant root access for the app on first click. Afterwards you can click onfiguration button and pu tthe needed information in there. If the connection works, you can enable the auto connect feature in the settings of the widget.
That is how i managed to get a 4g stick working just this morning
Click to expand...
Click to collapse
Trying to get it working.
Thanks for your suggestion!
King Mustard said:
Trying to get it working.
Thanks for your suggestion!
Click to expand...
Click to collapse
weird problems you mention in the thread there.
For me it acutally worked but after the reboot, it didn't. Need to figure out what is going on there. I'm pretty sure it has to do with the order of connecting the stick. Since it is already connected when booting up it does not get recognized correctly.
Good luck to you man!
... Late response, but maybe it will help others ...
I have a Huawei e3372h-153 dongle and a Dasaita PX5 4GB RAM and 32GB ROM with original ROM, and as mentioned in this thread, at first I was able to see the signal bar and that was all, no connection, no network type, nothing. I tried different apps in an effort to make the dongle work, like Activity Launcher or Android Hidden Settings, in order to access inaccessible/hidden network settings, but with no luck.
Finally I got the modem working by updating it with the firmware "2. E3372hUpdate_22.200.03.00.1134_M_HC_ADB_TLN_02" as mentioned here.
I updated the modem with that file only, and not with the rest of the files, as it was mentioned in the video, because the video is referring to e3372h-607, and I have the e3372h-153 version.
To resume, I have the original Dasaita firmware, updated to the latest version (currently Blue UI HA_px5_8.0_ota(20190428)), with the latest MCU (V3.10), working with e3372h by just updating my original modem firmware. Dasaita original firmware updates and MCU updates can be found here . Use them only for Dasaita, compatible devices.
The Head Unit will see the modem as an usb network device, so you will not have info in the status bar related to signal strength or network type, but otherwise it will work flawlessly.
Unfortunately I don't know what was the previous firmware installed on the device, because I tried a bunch of them, but most probably I had "E3372h-153_Update_22.323.01.00.00_M_AT_05.10".
My Web UI version before the "working" update and also the current one is 17.100.18.03.143-Mod1.21 . By default it will be installed in Russian but it could be changed to English easily. Keep in mind that material design is quite buggy, so I would not suggest you to use it.