Related
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've been running the rooted GB leak since it came out. So far the battery life is great and it is very stable.
*Edit* I should clarify that I am running 4.5.606 installed as the 2 part rooted zip, I am going to also install 4.5.607 to see if it changes anything.
I have noticed a couple of bugs so far.
I am running on GSM, the signal strength indications are 2 bars lower than they were under Froyo using Fission. The actual signal strength is the same, it is just the indication that is out.
If I turn the phone off and then on again without waiting for 20 seconds the GSM radio fails to initialise on the reboot. It tells me there is no network and asks if I want to switch to Global mode.
Sometimes the camera takes partial pictures, the first third is there the remainder is black.
Sometimes I answer a call and it is silent, no audio. It only happens from a few numbers, it always happens to the same numbers. I had the same issue on a Galaxy S and it was quite common. The entire time that I was running Froyo on the D2G I only found one other number that was a nokia mobile on the same network as mine where there would be no audio every time I called him or he called me. On this build I have had the no audio issue from a landline number, this is a first!
Vz have put a block into the firmware that prevents call diversions being made using the standard codes (ie. **62 etc) It pops up a message saying "Call forward is disabled outside the verizon wireless network"
The only issue you listed that I can confirm is the signal strength indicator for GSM. However, it was working in exactly the same fashion on stock 2.2.
I have noticed quite a few bugs.
1. Sometimes when a text message gets a certain length the keyboard stops working. You have to press home and open it again.
2. Keyboad LED sometimes doesnt come on.
There are a few others but I can't remember. I don't know what the problem is but I'm thinking of flashing back to 2.2 because it's so frustrating.
You can also try 4.5.607.
Gasai Yuno said:
You can also try 4.5.607.
Click to expand...
Click to collapse
Where can I find this? and can I flash it from 606?
http://rootzwiki.com/showthread.php?3406-Gingerbread-leak-D2G-Updated-to-4.5.607!
You need to follow the instructions here. I have been running 606 and it is excellent with just a couple of minor issues, but nothing show stopping. The biggest PITA for me at the moment is the inability to set up call diverts from my phone due to the Vz lock in 606, I am just about to install 607 to see if it changes anything.
4.5.607 is the soak test update; you can find it @ RootzWiki.
To install it, you must be on stock 2.4.330, no root, no bootstrap recovery.
There are no major changes in it. Call forwarding options are still available on VZW only.
wifi ad-hoc also not working properly!
BlueTooth Issues Anyone?
It seems I've lost the ability to connect to my phone over bluetooth serial port from my PC. Can anyone confirm this, or deny it? I've tried 2 PCs, with different BT dongles so far. I've had this problem on GB 606 and now 607. Man bluetooth is a pain. Might try SBF, reverting, but it does become tedious after a while.
(also, if it's just me, any suggestion on how to fix?)
I have flashed back to 2.4.330 and then installed the 4.5.607 update.zip and then rooted with the droid 3 script. No changes that I can see from 4.5.606.
Bluetooth audio works perfectly both ways. I can send a file from my PC to the phone using bluetooth. I can browse the device over bluetooth, but only after installing a 3rd party app. I am running Ubuntu so I can't comment on the windows bluetooth stack, but the linux one seems to perform normally.
SPP
I know BT Audio works. My concern is, did the BlueTooth Serial Port Profile and DUN go away? I used to be able to connect to my phone over BlueTooth and send AT commands to it. Now, no port, no connection.
I'm sure I didn't have DUN support on stock 2.4.330.
Not sure about the BT device which Windows fails to find drivers for, though.
No Call Audio.
mactherapy said:
Sometimes I answer a call and it is silent, no audio. It only happens from a few numbers, it always happens to the same numbers. I had the same issue on a Galaxy S and it was quite common. The entire time that I was running Froyo on the D2G I only found one other number that was a nokia mobile on the same network as mine where there would be no audio every time I called him or he called me. On this build I have had the no audio issue from a landline number, this is a first!
Click to expand...
Click to collapse
Mine did the same thing every other day on GB. I couldn't hear anything and neither could other person on the line. Only way I had been able to fix this is by rebooting the phone. Got very annoying. Went back to Hexen Froyo for now...
So I'm off travelling the world and using my d2g for internet access. I probably should have tested it before I left ;-)
It turns out the USB tethering does not appear to work, I get a connection and an IP address via DHCP, I can ping the gateway on the phone and resolve DNS info if I use the gateway as the server, but I can not get any traffic to pass through the phone.
Wireless tethering won't even connect using the built in App.
I tried Opengarden and the latest beta of the wireless tether app, no joy yet.
Funnily enough the bluetooth networking connected straight away and works perfectly.
I am running linux on my laptop, I guess I will have to boot into windows to see where the issue lies.
I don't claim to know anything, and currently don't have the motivation to go back to Froyo, but SPP and DUN are listed for the Droid2Global on here:
(not allowed to post link to MotoDev specsheet for Droid2Global)
I had SPP on Froyo. Now I don't. Don't know if it's GB, or just me.
In this thread i am only referring to the WiFi/Bluetooth clash that seems to affect some of us but not all of us.
ie; The problem appears to be with the WiFi, WiFi fails to disconnect when leaving the ssid area. Wont reconnect when returning to the area, the WiFi connection just cycles, hunting and hunting, never connecting..... until i turn the Bluetooth off, then it connects within seconds. Switching off the Bluetooth appears to eliminate a 2.4ghz clash between the wifi and Bluetooth, allowing the WiFi to operate freely.
Other phone manufacturers have had to deal with this, its not uncommon.
I've been evolved in a bit of discussion about wifi this week, And i have found I have the WiFi/Bluetooth clash on my twin-core. but not the quad-core.
so i thought we should distribute the version numbers that are trouble free, that seems to me to be a better place to start than with just random testing like i have had to do to get my result... .. so a bunch of test roms later, here are the rom versions i use, and have turned out to be trouble free.
Twincore - Now runs "CleanROM 3", based on build version 1.88.707.2, now runs problem free. I had previously tryed Asian roms 1.77.708.3 & 1.77.708.2, the Modaco IR1(1.29.401.11), all had the W/BT problem.... there were some others that didnt work either but i lost track.
I also tried the wifi fix provided by JSLenterprises but got no relief from that, not on any of the versions i tested.
(To be fair to JSLenterprises, i dont even know if his fix was for this issue, i just tryed it because i was testing anything WiFi for my solution!)
Quadcore - Still running factory 1.29.728.12, always ran problem free!
Anyone else got some build numbers that you know are trouble free? we might be able to narrow down weeks of research for others trying to resolve this bluetooth/wifi clash.... or else wait for the proposed offical update of course.
And anyone having familiar problems might want to flash these versions i suggest, just to make sure i didnt just get lucky.
lets solve this sh..!
You had bluetooth issues, and flashing cleanrom 3.0 fixed them?
what issued did you have? my bluetooth is terrible.
Was person calling me hearing their echo when im on bluetooth one of these problems?? Just bought bloototh for car and receiver hears their own voice, big echo they say
I had no issue with the bluetooth itself...
explanation in opening post........
I am starting this thread to be a place for Terrain owners to come for the latest info on how to root and flash their phones. The Terrain is one of the best "rugged" phones on the market, but it has been abandoned by it's manufacturer, leaving owners to find their own solutions to problems and upgrades. This is actually a good thing price wise as you can now buy a brand new Terrain for less then $85. The Terrain has about as of hardware specs as any other ruggedized smartphone on the market currently, but at one third or a 1/4 of the cost. This makes this phone a huge attraction to anyone who is looking for a rugged waterproof phone on a budget and is why this guide is essential for users.
The NEC Terrain still has plenty of life left and this is why we need to come together and find solutions for it. Please feel free to post you success stories in rooting and flashing your terrain to this thread for the benefit of all. Hopefully, will be able to form a complete guide from all the information that get's posted here.
Thanks.
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
gamerka said:
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
Click to expand...
Click to collapse
Thanks for the post and the links. It appreas that much of the information on these links are still a work in progress. Hopefully this work will continue and we can create a How To guide from this.
For those that may be interested. You can buy the NEC Terrain Unlock on Amazon for $79.99. Here is the link.
http://www.amazon.com/NEC-Terrain-UNLOCKED-WaterProof-DustProof/dp/B00KZPI04S/ref=sr_1_1?s=wireless&ie=UTF8&qid=1405614968&sr=1-1&keywords=nec+terrain
For full specs on this great phone you can go here.
http://www.gsmarena.com/nec_terrain-5553.php
Well, I almost bricked it few days ago. :good:
I read a thread about a patch to unlock GSM in CDMA phones and saw there a code to enter some hidden menu. I entered that menu and messed a little with band settings (wanted to get LTE to work with my operator). Next thing I know Terrain stopped receiving any GSM signal and for next hour I tried to fix it. Factory reset got me 2G signal and that's all.
It turned out that the only way to fully fix it is to re-flash firmware or radio module and as we know that can't be done.
Well, this is not about unlocking or flashing, but it is a solution to another problem I and many other have been having with the predictive text bar blocking critical function keys from being accessed. The predictive txt bar is a function of the Adaptxt keyboard app and disabling it does remove that bar, but the keyboard also loses all special character function, upper case letters and numbers. After trying more then a dozen keyboard apps to replace adaptxt, I found one that works and brings back all keyboard functions without the stupid predictive text bar. It is called TouchPal.
https://play.google.com/store/apps/details?id=com.cootek.smartinputv5&hl=en
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI. The PC can connect to the phone, however the connection in Windows 7 always is shown as being limited (no internet access), while internet on the phone works fine.
GMail - as well as some other functions of google also rarely sync and basically just do so on request, while they sync just fine when being connected to Wifi. And no, background data are not restricted in the settings.
Has anyone experienced something similar?
laserdrome said:
device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI.
Click to expand...
Click to collapse
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
iDomino said:
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
Click to expand...
Click to collapse
Well actually I know that message as well. For me changing the APN helped. You could also try to restart the phone. I just remember I also had this problem sometimes. But like I said - even without that particular message I would not get tethering to work.
iDomino: Do you also experience the problem with syncing that I had?
That's funny, actually I haven't noticed syncing problems untill I read your posts. I myself have all the same problems that you mention.
Even more of that, Terrain has some silly feature that TURNS OFF WI-FI if it thinks that that hotspot has no internet connection. It is massively annoying and can drain all your data traffic. The only solution that I found is to install the app "Smart Wi-Fi Toggler", it constantly turns wi-fi on if terrain turns it off, but only in places where I turned wi-fi on myself (like home and work).
It's a pity the phone has so many flaws and due to its tight security and the locked down NEC mobile devision no one can do anything about it. I wonder if this just affects the users who use an unlocked phone outside the US or if people in the US have similar problems. I have tried contacting NEC about this - actually about providing us with some kind of unlock mechanism - but all I got was this:
"Dear Sir,
Thank you for inquiry.
We, however, regret to inform you that our phone is not available about your request.
If you have any issue, would you try to contact the company or shop where you have purchased this model, who might be of help to you.
Thanks and Best Regards,
Fujii /NEC"
By the way, I discovered a new bug: When Roaming the actually used Network-Provider is not shown and I also didn't find a way to choose one...
Do you also experience the problem with syncing that I had?
Click to expand...
Click to collapse
I had some sync problems and I don't know working methods to fix it.
First time I solved it this way:
turning off apps sync -> open Gmail app -> it will show notification offering to enable synchronization -> use it -> sync works.
But this solution worked just once. (
Other time sync turns on by itself after one day disabled.
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Battery life
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
iDomino said:
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Click to expand...
Click to collapse
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
FFDA said:
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
Click to expand...
Click to collapse
My phone works about 25-30 hours (30 min. calls, 5-10 sms, 30 min. messaging, 2 hours e-mail, internet & other applications. No video/gaming/music at all).
Infinite loop. Removing "modemmanager" helps! Thank you! :laugh:
Also got spontaneous rebooting after installing FTP Client made by Zifero. :silly: Removing app solved the problem.
Dreaming about root and working wi-fi tethering.
Who have usb driver of nec terrain? I need it, thanks
zolahn said:
Who have usb driver of nec terrain? I need it, thanks
Click to expand...
Click to collapse
Maybe this topic will help.
Cpu-z shows only 665MB RAM on device... Where are another 335MB???
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
Another Terrain user here!
Hi guys!
i am Kharl
i am another Nec Terrain user here!
due my lifestyle, i needed a phone which could gives me reliability and power under ANY circunstance, that could be done by any rugged phone, BUT i needed querty keyboard, fm radio, gps, gyroscope, accelerometer, loud speakers, that could work worldwide and touchscreen... the only one with those features was the Terrain... and with the extra, that it is amazingly cool, i dont know opther but i find this phone really cute, very sober and elegant design.
well, i live outside USA so, for me, to work it couldnt be locked to ATT, so i was able to get one unlocked.
my phone has almost all the problems you mentioned, althught i am still happy with it and i am not going to change it because its problems does nto interfere a lot with me, BUT of course id like to get those problems sovled.
trying to solve the problem i bough three of thes phones and all the three had the same problems
the first one was by mistake, locked to att, but it had the same problems, random restart and locked hotspot, i sold it, i got a second one, works with any sim, everything fines, but with the same problem, random restart and no hotspot, i bought a third one to see if the problem was with my particular phone... and n luck the same problems.
it has some other minors problems, like no stereo audio recording despite it has two mics and IT STATES IT CAN record in stereo, but thats not a problem, i can deal with that, and sometimes the people at the other side (while in a call) says my voice sounds like from within a box (lack of trebble or too much bass) and when i press the check too much to the phone boddy there is also clarity sound problem.... but thats ok....
regarding the two main problems
random reboot and hotspot
many of us suspect what the cause is
for the random reboot many could think it is a installe app which is causing it... NO, because it does it at factory state, to solve that i dotn think root is needed, there is a certain factory process that is causin to reboot, the reboot is VERY random, could doit threee times in a day or could happen only three times in a week, what i have notice is that it happe lessoften in cold weather.
the hotspot problem IT IS cause because att locked that function, even when the phone is ulocked, that part remain locked because ATT.
what about you guys?
u can try hard reset for begging
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again