Related
I cannot pair my vehicle's headunit to a CM-powered device, starting with CM6 RC2. (RC1 worked as expected).
I would like to build the stock Android Bluetooth stack and replace that portion of CM with it, in an effort to see if it resolves this problem for me. I'm also curious how the new Bluetooth stack in Gingerbread will behave, as it's apparently received an overhaul.
Ultimately, I'd like provide a package so that CM users could easily "flash" a new BT stack if they're having problems with CM's modified version.
I'm a junior developer, and I have Ubuntu on my machine, as well as AOSP Gingerbread and CM6/7, all building correctly. However, I lack the knowledge (or even a starting point) on what I need to do to accomplish this.
Anyone willing to offer some advice?
Additionally, if anyone else out there is having problems, please post here--once I get this working, I'll need test candidates to see if it helps resolve their issues as well.
EDIT: Starting here. http://source.android.com/porting/bluetooth.html
Never had an issue with bluetooth and my vehicle or a couple of others while running CM 6.x or any of the nightly builds of cm6. Sometimes a kernal I flashed would break it, but otherwise it worked fine. I done this one both a alpine blue tooth module and factory ones.
What are you syncing to?
aduljr, the type of headunit I have is called "BlueConnect", and is built-in to my 2009 model year Hyundai Elantra. This is the manufacturer's website: http://www.autointelligence.com/
Like I said, it worked with CM6.0.0 RC1, but stopped working starting with RC2 and hasn't worked since.
So far I've started reading about the BlueZ stack, but haven't made more progress than simply reviewing some make files.
As always, if anyone has any pointers (or if anyone is also having BT-related problems), please post.
Thanks.
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
timwoj said:
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
Click to expand...
Click to collapse
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Shidell said:
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
have you tried updating to cm6.1 and trying with a stock kernel?
jsseidel1 said:
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
Click to expand...
Click to collapse
Interesting, and appreciated. I'll look into a Google Group, although for now I'll work out of this thread unless this grows into a large project.
BrianDigital said:
have you tried updating to cm6.1 and trying with a stock kernel?
Click to expand...
Click to collapse
I have tried 6.1 with an alternative kernel (Kings) to no avail. Do you have a kernel you'd suggest I pair with 6.1 for testing purposes? I'm more than willing to do so for testing purposes.
Shidell said:
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
Basically, I'd like to be able to tether my phone over BT. The Evo doesn't provide a DUN or PAN service that OS X can see (never tried windows), so things like Android-Wifi-Tether don't work in bluetooth mode.
does you phone work with any other bluetooth device?
aduljr said:
does you phone work with any other bluetooth device?
Click to expand...
Click to collapse
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
BuddaBelly said:
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
Click to expand...
Click to collapse
+1 I have this same problem. CM has a much weaker bluetooth connection than Sense ROMs. I would love to be able to flash something over CM7 to increase bluetooth reliability, even if it hurts battery life (you could always turn bluetooth off when you need to save battery).
Shidell said:
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
Click to expand...
Click to collapse
ill try this as i have the cutting out issue as well
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
allroy1975 said:
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my wifi is never on. and even when it is it doesnt do it on sense roms.
zikronix said:
my wifi is never on. and even when it is it doesnt do it on sense roms.
Click to expand...
Click to collapse
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
BuddaBelly said:
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, wouldn't it be easier to look back into the git commits for the CM repository. And see what changed in the bluetooth files after 6.0.0? That way you should be able to drop in the older bluetooth stuff, and have it work. Then you can try to convert that stuff to work in CM7?
timwoj said:
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
Click to expand...
Click to collapse
If you use AWT and set it to Bluetooth mode and then turn it on, the PAN service will magically be created, but only while tethering is turned on. However, I still wasn't able to get Bluetooth tether to work because of some kind of IP address error in AWT. I think AWT wasn't able to set an IP address for the Bluetooth PAN adapter. My computer was able to see the Bluetooth PAN but wasn't able to pull an IP address to fully complete the connection.
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
slacka-vt said:
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
Click to expand...
Click to collapse
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
nadiros said:
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
Click to expand...
Click to collapse
I'm glad to see I wasn't the only one bugged by the 3G signal showing in the status bar on Wingray. It wasn't a huge deal, but one of those little things you always notice once you see it the first time. There were a few other things, but overall it's a nice build.
I also use AOKP on my Nexus S as a daily driver and I'm very happy with it. No big issues to call out. Once the wingray builds progress a bit more and those few little bugs are worked out, I'll most likely switch to it as my main rom.
Build 25 - 3G icon bars still there.... feels superficial however I didn't test much further . I will continue to periodically check in on them... but like I said - for this aspect to be overlooked then they're not paying attention to wingray for some reason
I am used the Kang rom for a while primarily because it has volume button wake built in. But after a while that tweak just stopped working so now I'm back on Bugless Beast for Xoom.. There's still plenty room for improvement for the Kang rom so I'll try it again at a later stage.
I've built from source and removed the 3G radio icon. It's something I'm sure they'll get to. I noticed someone posted a bug report on that to them already. I posted what they need to do to get rid of it. I might post my build but only after getting permission to do so from them. Run's great with my oc kernel.
Well from what I see they (Team Kang) have discontinued their Wingray builds. Rootz wiki has a pitiful thread that has dwindled and I see only a Stingray release for Xoom as far as the latest build 30.
WTF !
Anyone know whats up?
Great so far but one question to those using it.
Allow apps to write to SD card is in the feature list.
How do I access this? Using various apps I can only write to media memory. Even if I change the path to /mnt/external1/. It just creates that folder within the internal memory.
Any help would be appreciated.
Is there any major milestone that must be overcome in order for the cyanogenmod team to officially support the HOXL? Are we just waiting for ROM cooks to take initiative? I know S-off is nice to have, but I don't believe it's a requirement.
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
jordanetodd said:
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Seems like ther'es been a fair amount of work as far as ROMS and mods and things go, but the Kernel source is the reason that there are working JB roms for the GS3 and we don't even have CM9 fully working yet....
I believe the developer interest come from a few factors.
1) There are few developers that get paid nothing and porting CM9/10 is a lot of work.
2) There are hundreds of devices how do you pick which one gets the CM9/10 .... sales.
The HTC One XL is a nice device but as a LTE device and from HTC it is likely not the strongest selling phone in North America
shorty6049 said:
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Click to expand...
Click to collapse
There's definitely more people on the One X international version. People will find that most phones with kernel source available and unlocked bootloader will draw more developers... But in this case quantity =/= quality. I've had several android phones over the years and yes, while it's nice to have a giant land of developers with pages and pages of roms to look through, they lose their luster to mediocrity. You'll find some of the best devs who weren't discouraged by the locked down devices such as this one, and as a result, the product (ROM, kernel, etc) will always be top-notch. And a smaller, more intimate dev community encourages more interaction and community support, making the overall experience that much better.
I think we already have pretty solid support, given that there's still no kernel source available.
We have great Sense-based ROMs (the CleanROM family, amongst others) as well as pretty-solid alphas of CM9 and AOKP. Personally I've been very tempted to try either CM9 or AOKP, but I haven't made the plunge yet. A friend of mine is using CM9 has his daily driver without issue.
I believe the team working on CM9 has plans to incorporate their currently-unofficial branch into being officially a part of CM9 (or CM10) once kernel source is released and the remaining issues are resolved.
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
pearlbrian said:
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
Click to expand...
Click to collapse
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
stnguyen09 said:
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
Click to expand...
Click to collapse
Sorry, i didn't mean functional. I meant, like you said, 100%.
pearlbrian said:
Sorry, i didn't mean functional. I meant, like you said, 100%.
Click to expand...
Click to collapse
yeah, my issue is that the few things that ARENT working are the things I want the most. Frustrating that this is as good as it can get unless HTC releases that source (which it's sort of staring to look like they may get away with not doing at all)
I think source will come. It's just sad that i have JB running on my old as bones Captivate while my shiny new one x is stuck with Sense :crying:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
kleeman7 said:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
SkizzMcNizz said:
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
Click to expand...
Click to collapse
Not quite sure what you mean,
The tablet would get Internet from my phone, then I'd use the tablet to stream music to my stereo via bluetooth
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
stnguyen09 said:
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
Click to expand...
Click to collapse
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
shorty6049 said:
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
Click to expand...
Click to collapse
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
I got it to work using CleanRom (not a photo, it told me it didn't support receiving large files) . I might flash something new tonight... I really just want something that does wifi tether (which I'll have to read into more... I feel like it's tougher to get that feature working on this phone than it was on my Evo) and NFC (so I can automatically turn on tethering when I get in the car) . I'm alright using a sense-based ROM if I have to since anything is pretty fast on this phone and cleanrom is relatively AOSPish
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
Sending Photos only works on JB. With ICS you can you can send contact info and Youtube links. Works between CM9 on One X and my N7 running JB.
Hello, I am typing this thread to ask the XDA community the following questions-
#1-Is it possible to port hostapd config from the Relay's stock ROM to the CM 10.2 ROM?
#2-If the above is true, then could it result in better or worse functionality?
#3-I have attached a PDF saved from a website that has the potential to explain this process, but it's a handful for even my brain and I need a little help breaking it down. It's 17 pages.
It essentially explains how to modify and what not to do when configuring hostapd.conf and its surrounding files and dependencies.
According to the similar threads list, this starter is one of a kind.
Please feel free to pipe in and help out.
Why?
Sent from my SGH-T699 using Tapatalk
this is why
Nardholio said:
Why?
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Well, I actually liked my hotspot configuration and setup from 4.1.2 'BMC5, but I also enjoy the perks of CyanogenMod. I'm just trying to find a way to get the best of both worlds, if that's possible in this case.
in android 4.3, the hotspot setup is constricted compared to my stock ROM. But the disadvantage is that the ROM is bloated and I hate it for that reason. i had CM until recently, but plan to reinstate it on Christmas day after a disaster with my Wi-Fi amid other issues in a cm11 nightly.
I hope this answers your question, and it's certainly nice to get a reply from Team ApexQ so quickly.
furboom1240 said:
Well, I actually liked my hotspot configuration and setup from 4.1.2 'BMC5, but I also enjoy the perks of CyanogenMod. I'm just trying to find a way to get the best of both worlds, if that's possible in this case.
in android 4.3, the hotspot setup is constricted compared to my stock ROM. But the disadvantage is that the ROM is bloated and I hate it for that reason. i had CM until recently, but plan to reinstate it on Christmas day after a disaster with my Wi-Fi amid other issues in a cm11 nightly.
I hope this answers your question, and it's certainly nice to get a reply from Team ApexQ so quickly.
Click to expand...
Click to collapse
In the end, T-mobile doesn't want to allow tethering freely, so the Stock Image is built around that -- This means that the methods in use between Stock and Cyanogenmod are essentially incompatible. Sure, you can go through a lengthly, 17 page process to hack it in, but to be frank, your time would be likely better spent getting us logs and descriptions of this 'disaster and other issues' with your cm11 nightly so that we can work on the problem, especially since using Cyanogenmod is your end goal Also keep in mind that nightlies are going to have problems from time to time, it's the nature of nightlies.
I understand, but...
Magamo said:
In the end, T-mobile doesn't want to allow tethering freely, so the Stock Image is built around that -- This means that the methods in use between Stock and Cyanogenmod are essentially incompatible. Sure, you can go through a lengthly, 17 page process to hack it in, but to be frank, your time would be likely better spent getting us logs and descriptions of this 'disaster and other issues' with your cm11 nightly so that we can work on the problem, especially since using Cyanogenmod is your end goal Also keep in mind that nightlies are going to have problems from time to time, it's the nature of nightlies.
Click to expand...
Click to collapse
About the t-mo tethering, I have a plan that perfectly satisfies me. I'm using it now. T-Mo was aggressive about this until about one month after I joined. (I joined 8/7/2013) They've become more flexible, and I am grateful, as I can use an unlimited data plan with my hotspot now. Combined with my UA Switcher, I can keep it longer.
Also, the code in the t-mo hostapd file is so simple, I chuckled. It's got only 8 lines of code. The CM variant has almost 3 screens or more of code. Please help me understand this difference.
Aboit CM11, I'm not going to get it. CM 10.2 is fine with me and my hardware/software items (BT Headset, apps, etc.) I am currently unable or unaware of the ability to create a log (yet). I'll read up on it.
And don't worry, I realize the nature and danger of nightlies more than ever, now. But you seemed to throw it in the bag with CM 10.2 (in a good way).4 Months for a stable? Genius efficiency! Let's hope you can do that for CM 11, too, then I'll definitely be on board!
Again, thanks for your replies.:fingers-crossed:
Another way of saying this is: We're not going to attempt to reconsile the differences between the CM config and the TW config. They're two different animals. You can try to drop in the config from TW on top of CM, but you're on your own. Thankfully, if you take a proper backup before starting, it should be easy to revert if this does break for you (And likely it will) The PDF you've posted is irrelevent. Linux and Android have moved on from the versions being discussed there.
furboom1240 said:
in android 4.3, the hotspot setup is constricted compared to my stock ROM.
Click to expand...
Click to collapse
What exactly do you mean by this?
Stock hotspots are always better and...
I mean that it has more features than cm. Examples include channel select, n compatibility (to avoid crossing BT wavelength) and a Mac address filter, plus the ability to know who's on it.
And, by the way I am back on cm 10.2, effective two hours ago. But I salvaged the WiFi folder from my old ROM. I'll attach it upon getting on my laptop. Also my dialer had failed to start. just can't win can I?
Sent from my SGH-T699 using xda app-developers app
PS here is the attachment in zip form. It contains all the files (except wlan0 and the like) required for an awesome hotspot. Again, I will re-state that despite its history, T-Mo has eased on hotspot restrictions. I have a $70 plan with hotspot, by the way, and am using it to type this response.
Thank you for your interest!:good:
furboom1240 said:
I mean that it has more features than cm. Examples include channel select, n compatibility (to avoid crossing BT wavelength) and a Mac address filter, plus the ability to know who's on it.
And, by the way I am back on cm 10.2, effective two hours ago. But I salvaged the WiFi folder from my old ROM. I'll attach it upon getting on my laptop. Also my dialer had failed to start. just can't win can I?
Sent from my SGH-T699 using xda app-developers app
PS here is the attachment in zip form. It contains all the files (except wlan0 and the like) required for an awesome hotspot. Again, I will re-state that despite its history, T-Mo has eased on hotspot restrictions. I have a $70 plan with hotspot, by the way, and am using it to type this response.
Thank you for your interest!:good:
Click to expand...
Click to collapse
What you are looking to do then, is to use the T-mobile tethering app, which only works on TouchWiz, and only on the T-mobile tethering paywall. It, as far as I recall, uses Samsung specific frameworks, and cannot be ported As for the caveat you have listed with n compatiblity there, that's resolved in the CM-11 builds as near as I can figure what you're talking about. If there's a specific problem with with CM 10.2 or 11 you're trying to get fixed, get us logs. Google 'How to take a logcat', that should get you started.
Eureka, I've got a LOGCAT!
Here is the logcat. I do not know how long they are supposed to be, but since it kept going, i cut it off at at about one minute. If there is anything this can tell you (or me, for that matter), then I am grateful. I just hit "THANKS" to Mr.Gentleman for his picture-perfect help pages for installing the JDK and SDK.
Hope this works.
Sent from SKYVALE (my laptop)
All right. If I cannot create a perfect hostapd file, can someone from Team ApexQ tell me how to safely edit the existing file in /system/bin/hostapd? There must be a middle ground somewhere.
Thanks so much for your feedback once again!
I hope Nardholio still isn't upset from earlier...I'd really like to hear from you again on this issue. I promise- no more irrelevant attachments!
Sent from my SGH-T699 using xda app-developers app
I've searched the forum, and I've read the threads related to CM11 for Xoom that I was able to find. If I missed the answer to this somewhere, please redirect me to it.
I have a Stingray / MZ602 device for which I no longer use Verizon's service. It is a WiFi Xoom for all intents and purposes.
Historically, I recall that Wingray ROM's would work on Stingray devices, just the mobile data wouldn't exist. However, upon trying to install CM11 4.4.2 Wingray ROM on the Stingray I get a massive amount of FC's upon booting the device. I can't even get my Google account signed in because Google Play Services FC's at launch. I have tried the Feb. 16th, March 9th and March 12th versions of the ROM and have the same failed results.
The reason I want the Wingray ROM instead of Stingray is because even with Mobile Data toggled off the lockscreen still displays "Searching for Service" and various mobile-data related services are eating 12-15% of the battery on a daily basis. And that's WITH mobile data toggled off.
Any suggestions on what I can do to get Wingray to install, or otherwise solve the data-using-battery issue?
Thanks.
thx
The for this topic really informative
proxpert said:
The for this topic really informative
Click to expand...
Click to collapse
The what is really informative?
The title is clear: Stingray device with a Wingray ROM. It's a Xoom (explicitly stated, and implied by the Stingray/Wingray reference.) It's CM11, Android 4.4.2.
The body is clear: I state my goal (use less battery, stop searching for cellular data signal.) I state my attempt to resolve the issue (install Wingray ROM on a Stingray device.) I state that this worked historically, but does not for this ROM. I stated my attempt to search and inquired for search suggestions/links if I simply missed it. And I request advice for resolution.
razorbuzz said:
The what is really informative?
The title is clear: Stingray device with a Wingray ROM. It's a Xoom (explicitly stated, and implied by the Stingray/Wingray reference.) It's CM11, Android 4.4.2.
The body is clear: I state my goal (use less battery, stop searching for cellular data signal.) I state my attempt to resolve the issue (install Wingray ROM on a Stingray device.) I state that this worked historically, but does not for this ROM. I stated my attempt to search and inquired for search suggestions/links if I simply missed it. And I request advice for resolution.
Click to expand...
Click to collapse
I leave mine in airplane mode with WiFi on and I have great battery life.
Sent from my HTC6435LVW using xda app-developers app
webeougher said:
I leave mine in airplane mode with WiFi on and I have great battery life.
Click to expand...
Click to collapse
Great advice! I thought of turning off the mobile data but not full airplane (then turn on what I actually use). This removed the "Searching for Service" warning on the lock screen (which was an annoyance - I like a clean screen). "Cell Standby" in battery stats has been greatly reduced from the 12-15%, but it still eats around 4-5%.
Not a huge deal, I get pretty decent battery life. More of an annoyance at this point and something I probably wouldn't be aware of had I not been so hell-bent on getting the "Searching for Signal" removed from the lock screen.
There is an answer
razorbuzz said:
I've searched the forum, and I've read the threads related to CM11 for Xoom that I was able to find. If I missed the answer to this somewhere, please redirect me to it.
I have a Stingray / MZ602 device for which I no longer use Verizon's service. It is a WiFi Xoom for all intents and purposes.
Historically, I recall that Wingray ROM's would work on Stingray devices, just the mobile data wouldn't exist. However, upon trying to install CM11 4.4.2 Wingray ROM on the Stingray I get a massive amount of FC's upon booting the device. I can't even get my Google account signed in because Google Play Services FC's at launch. I have tried the Feb. 16th, March 9th and March 12th versions of the ROM and have the same failed results.
The reason I want the Wingray ROM instead of Stingray is because even with Mobile Data toggled off the lockscreen still displays "Searching for Service" and various mobile-data related services are eating 12-15% of the battery on a daily basis. And that's WITH mobile data toggled off.
Any suggestions on what I can do to get Wingray to install, or otherwise solve the data-using-battery issue?
Thanks.
Click to expand...
Click to collapse
I have a Verizon 3G MZ600 That I am running with wingray roms. For the most part these seem to be working pretty well. The latest cm11 Big Part Roms seem to be far more stable (March 17,19,21,23)than the earlier ones. However, there seem to be issues with a lot of Google apps. Honestly though, as I've check out all of the "stable" upgrades, I find that the Omnirom Roms seem to be more stable and are more compatable with Google apps, with much less chance of crashing than the CM11 Roms. I have no issues with searching for service, and with my screen running at full brightness, my CPU at 1700 I'm running a solid 11,500 on Antutu, and getting a real 5½-6½ hours, solid, hard work out of my battery on a full charge.
There are a lot of programs that don't work or play well with either CM11, or Omnirom yet. Just give our developers time. (They're really good guys). Pay close attention-You and I may be able to see some of the things that would help them produce even better custom roms in the future, or that we could even learn enough from them to help them with the programming ourselves
Thanks for the reply, Kingsman1
Kingsman1 said:
Just give our developers time. (They're really good guys). Pay close attention-You and I may be able to see some of the things that would help them produce even better custom roms in the future, or that we could even learn enough from them to help them with the programming ourselves
Click to expand...
Click to collapse
I absolutely agree! The developers are fantastic. By no means did I intend anything that I said to come as negative towards them nor their product. It's a minor annoyance, but absolutely not a problem. :good:
Hanging tight with Stingray CM11 for now. I should have time in a couple weeks to run through some fun testing with the device. The other odd problem that's keeping me from doing it now is that BigPart/TWRP's nandroid's fail to restore and I can't do without the tablet at the moment.
I do wonder if I should give ART a shot just to play though. But now I'm just rambling.
**I hope this doesn't come off as defensive. Truly, I'm appreciative of their product and wanted to add extra praise into it.