Related
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?
With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.
don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry
I run VC 1.6 US and have never had a problem with it. I always install it in main memory.
I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..
<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..
Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!
VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...
never had a problem. Installed in a few different roms. works fine
installed to main memory.
wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.
I've got a Kenwood BT-200 bluetooth handsfree car kit and have found the following issues with it;
1. Everytime a call is completed, the phone book downloads all over again and takes over 10 minutes, preventing making follow on calls till complete.
2. The received and dialed calls list doesn't work
3. Cannot initiate a call from the head unit unless the phone screen is on (was working perfectly on previous HTC Touch Cruise).
4. Unable to initiate voice dialing on Phone using Microsoft Voice Command whereas with previous HF kits it was as simple as pressing and holding the call button.
Anyone else use the same Touch Pro - BT200 combination? Or experience similar problems with other HF kits?
I have Pioneer BT unit. I can not connect, but I installed Hands-Free Config from JETware Mobile Software and it solved all my problems. There are many setting options which should help you...
Hi Pritman,
I just went through the same thing after upgrading to the Touch Pro from the Dopod 838Pro (Hermes).
There's a firmware update available for the KCA-BT200 which may well fix your issues (certainly did mine).
I created a post about this earlier today (didn't see your post here).
http://forum.xda-developers.com/showthread.php?t=440494
The firmware flash is very easy to do. You will just need a laptop with a bluetooth adaptor.
Codenix.
Kenwood have released another update.
See my other post at http://forum.xda-developers.com/showthread.php?t=440494 for details.
Codenix.
Wow, never thought I would fine anyone else with the combination of Kenwood DNX-7100, KCA-BT200 AND the touch pro. I am having similar issues.
DNX-7100 with BT100 worked fine with touch pro.
"upgraded" to BT200, and I have nothing but headaches.
I have tried two different BT200, and both have been flaky.
I have tried BT200 firmware 1.60 and 1.70, and both have been flaky.
My problem is similar to the ones you folks have been experiencing, mainly it is constantly downloading, and the interface is super sluggish when downloading. I can retrieve a name and phone number from the BT200's memory, but when I call out it will say downloading and do nothing. Sometimes it won't "pair" with the phone automatically unless I manually select my phone from the DNX-7100, and sometimes it will just drop the connection. I used the BT100 for about a year, and it was solid 95% of the time. I am running stock Telus rom, btw. I have also played around with the dip switch on the BT-200. From the shipped manual, DNX-7100 belongs in group F, which is off, off, on for dip switch 1, 2, 3. But when I searched online, some of Kenwood's info listed the DNX-7100 under group G, which has dip switch off, on, off, just to add to the confusion. I have also tried removing the "wireless stereo" profile as well as the "serial port" profile, but that fixed nothing. Lastly, just to kick me when I'm down, when it list the numbers, sometimes it list them as first name, then last name, but sometimes it list it as last name then first. This is super irritating as you can't be sure where anyone is listed ..... so far my experience with the BT200 has been nothing but horrible. I am on the verge of flashing my touch pro to a cooked ROM just to see if it is due to the stock Telus rom's bluetooth (I went back to stock as the juggalo rom I used became corrupt after a few weeks).
So, did you guys finally find a solution that worked 100% of the time?
Idea
Hi Guys, I'm glad there are more people out there with my combination.
Upgrading the BT 200 to 1.70 has improved things significantly but not as good as it would be with another handset like a Nokia N95. The download delay and sluggishness still exist.
I recall when I paired the TP, a notice came up on the TP that the BT 200 is requesting access to the phonebook or contacts and prompted me to allow or deny. I'm wondering what would happen if I deny? I do know that when I first paired the N95 with the older firmware, it wouldn't syncronise the contacts and I had to manually send the contacts to the BT 200. If this can be done with the TP, it may eliminate the constant downloading, perhaps.
Anyone else willing to try this. I may not be able to do this till later this weekend so if any of you do manage to test this before me, please post the results.
Good luck!
If you don't give it access to the phonebook, I suspect it can't download your phonebook automatically, and you would have to manually push the phonebook over, which defeats the purpose of the BT-200, effectively making it a BT-100. After trying a 2nd BT-200 for 3 days, I have given up and chalked up the BT-200 as extremely flaky, and is easily the worst purchase I have ever made as:
1) Half the time it won't pair with the phone automatically
2) The other half when it does pair, you can't dial out as half time time again when you want to make it call, it decides to do a download from your phone instead (never mind that it already "downloaded" when it paired already. Half x half = quarter.
3) Half the time when it does manage to make it call, it magically drops the bluetooth pairing and drops the call.
If you're keeping track, we are at half x half x half, which is 0.125, or this damn thing only works 12.5% of the time. This is not a time saver, nor a gadget of convenience/safety. It is the ultimate source of anxiety, danger (as you're trying to get the damn thing to work), and a big disappointment. Kenwood, shame on you for putting out such flaky products, and especially for not fixing it (look at the first post, it is from Oct 08).
I am going to return both of my BT-200 to Clutchfield, and am going back to my 99% stable BT-100. BT-100 actually is not as horrible with the TP as TP runs WinMo 6.1, which lets you push multiple phone book contacts at once (not like the older WinMo where you had to push contacts ONE BY ONE!!!). The only caveat with the BT-100 is if you need to delete or modify any contacts, you can't, and you have to delete all the entries for a particular phone and repair and push all contacts again, which takes 1 minute now as oppose to half an hour with pre-WinMo 6.1. When I buy a HU next time, I don't think I will consider Kenwood again due to:
1) Flaky software/interface.
2) Poor documentation.
3) Poor service support. Kenwood Canada actually NEVER REPLIED. I only received the auto-gen email notification indicating they received my email. Clutchfield Canada has been very supportive, and I will pay more to buy from them in the future solely due to their strong customer support.
Hi Johnnysks,
As far as the Touch Pro is concerned, I understand your frustration and totally support your argument.
On the other hand, I have tested the BT-200 with a Nokia 96 & my previous Touch Cruise, works like a dream! I've had good responses from Kenwood UK but whenever I contact HTC, I alway get vague responses, which to me suggests that Kenwood must have been making the effort but keep getting let down by HTC. Ultimately the BT-200 works with majority of the handsets out there.
I will still keep trying for a solution though as I really do like the TP and the BT-200!
I have no doubts the BT-200 works with other phones, and I know my TP works with my BT-100 flawlessly. I also know from prior personal dealings with Kenwood Canada's technical support that:
1) They're rude, have a bad attitude, and unprofessional (as my first inquiry for a different product from a year ago was met with a reply that was condescending, unhelpful, and was not even in proper English). I'll be more than happy to dig up my old email for you if you have any doubts.
2) They're not responsive. It's been over a week, and they never replied to my current inquiry regarding the BT-200 (funny. They used to be rude and unprofessional. Now they're missing in action)
Perhaps Kenwood USA, Kenwood UK, or Kenwood Japan are doing an awesome job. However, I can only go with what I have personally experienced.
Anyone find a fix for this? I have the same problems with my DNX8120. Tried Jetware, no luck, I would try BTRestore, but it won't work with .net 3. My biggest complaint is that even if it is connected via bluetooth, it won't start a call from th eheadset unless the phone is not in standby. Next biggest issue is that it drops the connection after hanging up from a call.
Very f*&%*g annoying!
FYI, worked with 2 different ETEN's
I was having a few issues with my Touch Pro2 freezing up and not turning on. The reset button did nothing. Then, I discovered my problem and I wrote about it:
http://www.medicalsmartphones.com/2009/09/touchpro2-wont-turn-on-use-right-power.html
You can see that the actual power button icon is also on the red "hang up" button.
Makes more sense for someone coming from a regular phone as most devices actually use the same button to turn on and off the phones.
I'm still not convinced of this... i've been seeing issues with the TP2 on sprint using WM 6.5. It enters one of the following states... and the only way to recover is carry out a reset (remove back cover and press the 'reset' button).
1) Device will not power on, but orange charge light is visible
2) Device will not active sync and becomes locked, and cannot be powered down
3) Device repeatedly shuts down and restarts when connected to a PC via active sync..
Its all with the sprint rom that came with the phone.
Darkseed said:
I'm still not convinced of this... i've been seeing issues with the TP2 on sprint using WM 6.5. It enters one of the following states... and the only way to recover is carry out a reset (remove back cover and press the 'reset' button).
1) Device will not power on, but orange charge light is visible
2) Device will not active sync and becomes locked, and cannot be powered down
3) Device repeatedly shuts down and restarts when connected to a PC via active sync..
Its all with the sprint rom that came with the phone.
Click to expand...
Click to collapse
Yep, same issue with the "Official VZW 6.5" update for my Verizon TP2...
Updated, when was it out, Thursday? Finally got all my sync issues fixed (Vista/Myphone/6.5 were not playing nicely) and starting reloading my Rhapsody stuff... Working good... Lovin' the 'Sense UI' update (minus the lag - but workable) and then... DUN DUN DUHHHHH!
Sunday morning I woke up to a completely frozen phone. Charge light was stuck on, frozen at the TP2 startup screen.
First try, power button - no response...
Second try, reset button - reboots to stick at the TP2 startup screen again...
Third try, battery pull - back to the startup screen again...
Finally booted to boot mode where 6.1 went right back on that puppy - works like a dream again!
Something weird in 6.5 land!
zcarman said:
Yep, same issue with the "Official VZW 6.5" update for my Verizon TP2... Something weird in 6.5 land!
Click to expand...
Click to collapse
+1. My phone NEVER did this with 6.1.
Flashed to 6.5 thursday. Started re-installing cabs sort of fast and loose. Had the phone go into the sleep-of-the-dead five or six times over the next 24 hours. Power was on (pressing end/power button gave me the green arrow telling me to wake the phone using the top button. Pressing anything else wouldn't work and only a battery removal or soft reset would do the trick.
Hard reset Friday and started doing .cabs with a little more care (Sense off/install/reset/Sense back on). and I've gone three days without it happening again. Coincidence? Don't know. But I'll be watching these threads (here & XDA) carefully and keeping my fingers crossed.
zcarman said:
Yep, same issue with the "Official VZW 6.5" update for my Verizon TP2... .
Finally booted to boot mode where 6.1 went right back on that puppy - works like a dream again!
Something weird in 6.5 land!
Click to expand...
Click to collapse
Where did you get 6.1? Verizon is sending me a new phone, I hope it comes with 6.1. I got my phone on Friday and Flashed offical VZW 6.5 to it, as a matter of fact I think they would have suggested that I upgrade today if it wasn't already at 6.5. They had me check version and said yep that's the latest version, that's the one we need on your phone.
Of course they don't admit there is a problem.
One time when it was "sleeping" and couldn't wake it up I tried calling it.... it vibrated, the lights came on, but no way to answer it just wouldn't "wake up"
Totally unacceptable.
immjg said:
Where did you get 6.1? Verizon is sending me a new phone, I hope it comes with 6.1. I got my phone on Friday and Flashed offical VZW 6.5 to it, as a matter of fact I think they would have suggested that I upgrade today if it wasn't already at 6.5. They had me check version and said yep that's the latest version, that's the one we need on your phone.
Of course they don't admit there is a problem.
One time when it was "sleeping" and couldn't wake it up I tried calling it.... it vibrated, the lights came on, but no way to answer it just wouldn't "wake up"
Totally unacceptable.
Click to expand...
Click to collapse
All the stock ROMs can be found here http://forum.ppcgeeks.com/showthread.php?t=91940
If you like wm6.5 other than the issues you have had, i suggest trying a custom 6.5 ROM such as MightRom( http://forum.ppcgeeks.com/showthread.php?t=79579)
However before flashing make sure your phone is unlocked. This can be done here: http://forum.xda-developers.com/showthread.php?t=578660
If you live in verizon's 1x network and keep getting an error every five seconds or so, the fix can be found here: http://forum.ppcgeeks.com/showpost.php?p=1472842&postcount=107
Custom ROMs are faster and in many cases much more stable than verizons 6.5 update. I am currently using MightRom with no problems. No freezing or anything.
Opened a thread on this issue over at PPC Geeks:
http://forum.ppcgeeks.com/showthread.php?t=106799
Pretty clear this issue is NOT related to carrier, not isolated to any one ROM (yes, even Mighty ROM has experienced this, too), nor is it solely seen with WM 6.5.
I have my opinions and theries... but who knows. No definative solution is apparent as of yet.
Still happening with my VZW TP2 WM 6.5. Never happened with 6.1. My current theory is that it has something to do with Active Sync. I never start it, but it is often found running on my phone and I cannot find where to shut it off. This was not the case w/ 6.1. I don't know enough about the phone internals to say any more than this, or to test the theory.... Still looking and listening for answers, will post here if found.
Why would ActiveSync need to run when the phone is not hooked up to a PC??
Looks like an old thread, but I have a touch pro 2 w/ sprint. Activesync is always running. I have to kill it with the task manager. Haven't nailed down what's triggering it to fire but it takes up valued resources. I'm finding pother apps running when I thought I exited gracefully, like email, messaging. I'm thinking it's a setting somewhere??. I figured out for my case why Active sync kicks off on it's own.
QuickGPS significantly speeds up the time for determining your GPS
position. QuickGPS downloads ephemeris data from Web servers, instead of from satellites, using your
device’s Internet connection via Wi-Fi, ActiveSync or GPRS/3G. Now any location related service like the weather update is lijghting up ASync and I have to kill it with the task manager util. To prevent it from happing I'd have to turn off data services.. so fark it. I increased the weather update time and kill the app if I use it.
QuickGPS significantly speeds up the time for determining your GPS
position. QuickGPS downloads ephemeris data from Web servers, instead of from satellites, using your
device’s Internet connection via Wi-Fi, ActiveSync or GPRS/3G.
I think when the phone uses an app that requires location, like weather active sync is getting woken up. In my case I get weather updates every 2 hours. Presto - evertime I kill activesync then update weather acltivesysnc starts up again. So, what I'm saying is for my case if I don't have wifi or evo or a strong signal, and I update weather activesync lights up. That supports what the manual says about QuickGPS.
Activesync is used several things including exchange email. If you set up push email with exchange server then even if you turn off activesync with the task manager it will automatically turn back on.
Anyone have this issue or a fix? BT connects perfect, works, perfect, but the command to hang up on the BT device dosen't properly hang up, and the phones returns the #777 error.
It does answer from the BT device properly. It does with with my other cell phones.
TP2 VZW
I had the same problem with my Voyager Pro headset and found that if I hit the button once, wait a second and hit it a second time it hangs up. Maybe it will work for you.
I have the same issue.
Using Moto HT710 and VZW stock ROM
same issue in w/ 09 bmw nav/bt connection. I have to grab the phone and press the end button as it never hangs up.
cab might fix it
Over at PPCGeeks.com some have fixed the issue using the cab in this thread: http://forum.ppcgeeks.com/showthread.php?t=90155
I am having the issue with my Ford Sync system. I will test the results of the cab this afternoon and post them. Hopefully this works because it is fairly annoying.
Here is the cab if anyone wants it.
Well it didnt work for my Verizon TP2 and the Ford Sync system, hopefully someone else has better luck with it.
This seems to work for me. It hangs up almost instantly now. Thanks for the find.
rsbrown69 I am glad I could help, could you post which version of the TP2 you have (verizon, tmobile, ATT). I just want to know if it worked on another verizon phone or not, if so I will hard reset and give it another shot.
wlawyer said:
rsbrown69 I am glad I could help, could you post which version of the TP2 you have (verizon, tmobile, ATT). I just want to know if it worked on another verizon phone or not, if so I will hard reset and give it another shot.
Click to expand...
Click to collapse
I am using the mostly stock Sprint TP2. The only main modification I have done is the Touch Pro 2 cleanup http://forum.ppcgeeks.com/showthread.php?t=88640
Looking at the thread on PPCGeeks it looks like mostly sprint users having luck with the cab as well. Hopefully something will come along for the verizon version as well.
I have the Sprint version and have installed the cab. I do not see any improvement. I experience intermittent problems with or without the cab. It doesn't seem to make a difference. FWIW, I use the Jawbone Prime and Jawbone 2. Same with either.
Just out of curiosity did you do a soft reset after the install? I remember someone mentioning that in the original PPCGeek thread.
Yes, I did a soft reset. Actually, a soft reset with or without the cab seems to solve the problem....for a while. Then it shows up again. It is a bit strange.
doesnt work
I tried it on my Sprint TP2 and it does not work either. I installed it and did a soft reset and it still does not work for me either.
It would be the best thing that happened if it did work cause I use my BT all day and this sleep mode BT thing on the TP2 is cool for battery life but it sucks for using the BT feature which to me is more important than battery life and I have car chargers and usb chargers so I would rather have a working BT.
Does anyone have a cab or fix that will allow the BT to function like the old Touch Pro? That phone had a great BT even if the battery life was poor.
Thanks for the attempt to fix the issue but it is a no go here.
Does not work on stock VZW rom
Didn't work on my TP2 VZW either.
The one person that has responded that it worked had the cleanup cab installed. I am going to try a full reset and put only the cleanup cab and the bluetooth cab on and see if I can get results. Yeah this bug is that annoying to me. http://forum.ppcgeeks.com/showthread.php?t=88640
Ok I did a hard reset, programmed the phone, installed the cleanup cab, installed the bluetooth cab, joined the phone to my ford sync system, made a call, and guess what... the phone hung up beautifully using my standard steering wheel control for sync. There must be something in that cleanup cab that is either A) the actual fix or B) a necessary piece of the fix. Sorry but I am not going to hard reset again to test it, mine is working so hopefully this info can help you guys as well. On a side note that cleanup cab is pretty nice but read the thread to make sure you want/need all that is included.
wlawyer said:
Ok I did a hard reset, programmed the phone, installed the cleanup cab, installed the bluetooth cab, joined the phone to my ford sync system, made a call, and guess what... the phone hung up beautifully using my standard steering wheel control for sync. There must be something in that cleanup cab that is either A) the actual fix or B) a necessary piece of the fix. Sorry but I am not going to hard reset again to test it, mine is working so hopefully this info can help you guys as well. On a side note that cleanup cab is pretty nice but read the thread to make sure you want/need all that is included.
Click to expand...
Click to collapse
The cleanup cab alone hadn't fixed the problem for me so that is when I tried this threads fix. So far it works more often than not but it still does not hang up every once in a while. Must be a combination of things between the cleanup cab and this one but still not the correct fix, better but not enough.
Mine worked none of the time before, I basically had to wait for the caller to hang up or pull my phone out of my pocket and press end, so any improvement is huge for me. I am traveling this weekend and next week so hopefully I will have more info to report at least with my setup with Sync (never got into the earpieces, so not testing that).
I must say i love the phone as in battery life and the camera also gives some nice pictures.
But what started it to not love the phone anymore is the notification problem.
I installed Whatsapp and as soon as the lockscreen was active or a few minutes later it stopped to receive notifications.
This also was for Telegram and my home automation app.
I have searched for topics and found quite allot of these similar notification problems with tips.
What i have done is set by every application that needed to be running in the background :
Enable autostart
Turn of battery saving mode - no limitation
Lock the app in the screen where you can empty / close the running apps.
Also found a topic and application that should "fix" some notification problems for MIUI.
https://github.com/FabioCZ
Not sure if this completly works but i am starting to get most notifications on whatsapp/telegram etc.
What does not work at all is my video doorbell,
the application is Hik-Connect.
Got my older samsung phone laying next to the note 10 and press the ring button.
Only samsung rings, the note 10 doesn't work at all.
ofcourse i have installed them both from the playstore, used the same settings on the xiaomi to keep it running.
Nothing
Is there anyone that has an idea, because the whole handy thingy is gone now.
maybe a custrom rom will solve it,but since i have no idea how to make it thats a no go
I did unlocked the phone , installed orange fox and magisk to use titanium backup.
Can say that this didn't work flawless also, getting magisk giving the toast message to give certain apps root acces etc etc.
whats even worse, can't return the phones ( got 2, 1 for me and for m girlfriend)
Well hope someone has an idea.
Thanks
edit: i am using nightskeeper to automatically turn of the sound at a certain time and turn it on.
Give some contacts rights to still call trough the audio block.
But also this application does not work anymore, i get this notice every time but its already active.
When i enter ok, and turn the permissions on it works again for a few hours or so and then its gone.
its getting a bit frustrating , hopefully my alarm clock will still stay working
try this setting
Sylar82 said:
try this setting
Click to expand...
Click to collapse
try to put a system sound, the same thing happens when I put an mp3 or music sound
thanks guys,
the sound trick was indeed a good one because it could not find the audio file that was set from my samsung phone ( used titanium backup to install WA again)
It does seem that 9 of 10 times i do get the notices.
Also got my Hik-Connect app finally running and ringing when i press the doorbell.
Now comes the strangest part, the settings that i have put in my phone are identical to the phone of my girlfriend.
And my phone works with most of the services that i want but the phone from my girl doesn't.
Also bumped into another thing, wifi tethering .
I have a android radio in my car, what i got set with Tasker for years is :
1 - jump in the car
2- bluetooth makes a connection to the radio/phone .
3- tasker notices this, starts wifi tethering / hotspot
4- radio will connect on the hotspot of the phone and live traffic naviation / streaming radio works.
That was how it was supposed to work, now i get a notice from tasker that its not working, need a extra application and root.
I have root / installed the wifi tasker tether application. Also found the module that should do the same and installed this in magisk.
But still a no go
i do like fiddeling around with my phones, but it has to work eventually haha.
Would come in handy if i know how to write code and make my own fix for this.
Ah well anyway, im going to make a full backup from my phone and try to set this 1:1 on my girls phone.
Hopefully the notifications and the doorbell will work then.
Thanks guys
Im using notifybuddy for notifications and it's a life changer.
Hello Vincenttot, I have bought a PocoX3 PRO mobile and the same thing happens to you.
What does not work at all is my video doorbell, the application is Hik-Connect. But on other phones it works fine.
Have you found any solution?
Thanks guys