Develop Bugs

audio jack

Please dont flame me i have been searching for awhile, what is the trick to get the audio jack or bluetooth to work i read something that you can send all noises through one of the two? i looked everywhere even google and am having a hard time finding this fix? any help would be great

reeshmd23 said:
Please dont flame me i have been searching for awhile, what is the trick to get the audio jack or bluetooth to work i read something that you can send all noises through one of the two? i looked everywhere even google and am having a hard time finding this fix? any help would be great
Click to expand...
Click to collapse
Neither work.
The 3.5mm jack used to kinda work, but it would break all other audio. IIRC I directed someone on how to set it up, and it didn't work - so it seems that doesn't work anymore either.
BT never worked, but it is close to being fixed.
You can get an extUSB dongle off ebay for like $2 and use it - that does work, although it's far from flawless - some have reported severe sluggishness after unplugging it.

I picked up this and it works great:
http://www.amazon.com/gp/product/B001P0IFXI

killerz298 said:
I picked up this and it works great:
http://www.amazon.com/gp/product/B001P0IFXI
Click to expand...
Click to collapse
What is interesting is I have the same exact adapter and although it works great when using it, as arrrghhh mentioned as soon as I unplug it my Sprint TP2 gets extremely sluggish...that does not happen to you? I'm assuming you have a Sprint TP2? What kernel, RiL etc are you using?

pdawg17 said:
What is interesting is I have the same exact adapter and although it works great when using it, as arrrghhh mentioned as soon as I unplug it my Sprint TP2 gets extremely sluggish...that does not happen to you? I'm assuming you have a Sprint TP2? What kernel, RiL etc are you using?
Click to expand...
Click to collapse
It's a bug, I don't think any particular combination will resolve it - any kernel will either have the partially broken code that causes the sluggishness, or if you go far enough back the code will simply not be present, and it won't work at all.
Has anyone taken logs or narrowed down what is the cause of the sluggishness? I can't seem to find my extUSB dongle. It's a pretty minor issue I know, but I don't know if anyone has investigated it.

thanks for the replies looks like its better to wait. i have been trying out slingplayer on android and its better picture quality than the windows mobile one the headphone jack working would be just to awesome. thanks again guys

arrrghhh said:
It's a bug, I don't think any particular combination will resolve it - any kernel will either have the partially broken code that causes the sluggishness, or if you go far enough back the code will simply not be present, and it won't work at all.
Has anyone taken logs or narrowed down what is the cause of the sluggishness? I can't seem to find my extUSB dongle. It's a pretty minor issue I know, but I don't know if anyone has investigated it.
Click to expand...
Click to collapse
I wouldn't call it a "minor issue" - for me, this is the one issue that prevents me from using Froyo full time. I've gone back to the auto-build kernel, as that seems to avoid the sluggishness problem. But support for external audio via the USB dongle is still very troublesome. I never know when the audio will work and when it won't.
One fairly consistent failure is that connecting audio via the dongle seems to turn off the TP2's microphone.
When I get into the car, I put my phone into its holder and plug the audio into the car radio. That way, I can talk handsfree - the audio comes from the car speakers, and the phone's microphone picks up my voice very nicely from the driver's seat. But it only works in Windows - when I boot to Android, the mic gets disabled and no one can hear me when I call.
So it may be a minor issue to some, but to others of us it is the only thing forcing us back to Windows.
Rightfully, if I'm going to complain, I should jump in and try to help. But I'm swamped with other work at the moment, so I'll be lurking and hoping that someone is able to focus on this eventually. Sorry I can't do more.

Gilliland said:
I wouldn't call it a "minor issue" - for me, this is the one issue that prevents me from using Froyo full time. I've gone back to the auto-build kernel, as that seems to avoid the sluggishness problem. But support for external audio via the USB dongle is still very troublesome. I never know when the audio will work and when it won't.
Click to expand...
Click to collapse
Ok, so it's a big issue for you - and as much as I would love to have the 3.5mm jack working, it's certainly not earth-shattering like the RIL issues were. The main problem - there's only two RHOD's that have the 3.5mm jack. That's probably the #1 reason that it is not a higher priority - we're in the minority among Rhodium owners.
It'll get fixed eventually, there's just a lot of things being worked on - and a lot of our devs are spreading themselves too thin. We do need moar help, but it's not easy work!

arrrghhh said:
Ok, so it's a big issue for you - and as much as I would love to have the 3.5mm jack working, it's certainly not earth-shattering like the RIL issues were. The main problem - there's only two RHOD's that have the 3.5mm jack. That's probably the #1 reason that it is not a higher priority - we're in the minority among Rhodium owners.
It'll get fixed eventually, there's just a lot of things being worked on - and a lot of our devs are spreading themselves too thin. We do need moar help, but it's not easy work!
Click to expand...
Click to collapse
I understand and agree. Without a doubt, the RIL issues are more important.
For the record, I'm not talking about the 3.5mm jack on the phone - I know there isn't a lot of work being done there. I'm talking about using the USB port with a dongle. I'm still using a 3.5mm cord to connect to the car, but I'm connecting it via a dongle into the phone's USB port. I think that the USB connection for audio is common across all of these phones, right?

Gilliland said:
I understand and agree. Without a doubt, the RIL issues are more important.
For the record, I'm not talking about the 3.5mm jack on the phone - I know there isn't a lot of work being done there. I'm talking about using the USB port with a dongle. I'm still using a 3.5mm cord to connect to the car, but I'm connecting it via a dongle into the phone's USB port. I think that the USB connection for audio is common across all of these phones, right?
Click to expand...
Click to collapse
Oh, yes. That works - is it inconsistent? ACL wrote the kernel code for that, and it didn't get a lot of attention when he first wrote it... so he's kinda ignored it, I don't think anyone has specifically addressed issues related to it.
As I have asked before (perhaps in another thread) do we have logs of these situations?
If you're having audio routing issues, there's a lot of changes coming related to audio routing...

arrrghhh said:
Oh, yes. That works - is it inconsistent? ACL wrote the kernel code for that, and it didn't get a lot of attention when he first wrote it... so he's kinda ignored it, I don't think anyone has specifically addressed issues related to it.
As I have asked before (perhaps in another thread) do we have logs of these situations?
If you're having audio routing issues, there's a lot of changes coming related to audio routing...
Click to expand...
Click to collapse
As I reported above, plugging in an audio cable seems to disable the phone's microphone. So my typical usage (audio routed to the car stereo, mic active on the phone) isn't possible in Android (though it works fine in Windows).
There may also be other inconsistencies, but I'm too swamped with other work to be able to troubleshoot and log it. That's why I tend to lurk rather than post - I can't properly participate in the process as I'd like to.
I wish I could give you better info. You guys are doing amazing work, and I really can't expect you (or anyone) to worry about the external audio if it isn't important to you.
If I can find some spare time, I'll try to do some testing and logging. But I said the same thing two weeks ago, and it hasn't come true yet. Between my day job and trying to get this house on the market, I'm swamped.

Gilliland said:
As I reported above, plugging in an audio cable seems to disable the phone's microphone. So my typical usage (audio routed to the car stereo, mic active on the phone) isn't possible in Android (though it works fine in Windows).
There may also be other inconsistencies, but I'm too swamped with other work to be able to troubleshoot and log it. That's why I tend to lurk rather than post - I can't properly participate in the process as I'd like to.
I wish I could give you better info. You guys are doing amazing work, and I really can't expect you (or anyone) to worry about the external audio if it isn't important to you.
If I can find some spare time, I'll try to do some testing and logging. But I said the same thing two weeks ago, and it hasn't come true yet. Between my day job and trying to get this house on the market, I'm swamped.
Click to expand...
Click to collapse
Real life can be a real ***** sometimes .
I still haven't been able to find my dongle from my old RAPH, I might just have to break down and buy one to test with! ACL's been pretty busy too, I heard he bricked his phone the poor guy... I'm not sure if he got another one yet or not, NAND threads have been eerily quiet...

arrrghhh said:
Ok, so it's a big issue for you - and as much as I would love to have the 3.5mm jack working, it's certainly not earth-shattering like the RIL issues were. The main problem - there's only two RHOD's that have the 3.5mm jack. That's probably the #1 reason that it is not a higher priority - we're in the minority among Rhodium owners.
It'll get fixed eventually, there's just a lot of things being worked on - and a lot of our devs are spreading themselves too thin. We do need moar help, but it's not easy work!
Click to expand...
Click to collapse
I think even a larger minority among kernel-hacking devs... Do any of the kernel guys have 500s/400s?

Entropy512 said:
I think even a larger minority among kernel-hacking devs... Do any of the kernel guys have 500s/400s?
Click to expand...
Click to collapse
The guy that wrote the extUSB patch, ACL.
I think bzo has a 400 as well... To be honest, there's only a handful of active kernel devs. Some are more active than others as well .

I happen to have a RHOD500 and am particularly interested in getting this functionality working. I'm brand new to this smartphone/android scene and unfortunately I know ****all about how to do any of this. I do have some very rudimentary programming knowledge and a willingness to learn. If there is anything I can do to be of help in getting this feature working correctly, I'd be glad to help. Any suggestions on anything I could do to try to be of service?

SgtMac02 said:
I happen to have a RHOD500 and am particularly interested in getting this functionality working. I'm brand new to this smartphone/android scene and unfortunately I know ****all about how to do any of this. I do have some very rudimentary programming knowledge and a willingness to learn. If there is anything I can do to be of help in getting this feature working correctly, I'd be glad to help. Any suggestions on anything I could do to try to be of service?
Click to expand...
Click to collapse
With... the audio jack? It's all working now, other than the "advanced" feature headsets AFAIK.

SgtMac02 said:
I happen to have a RHOD500 and am particularly interested in getting this functionality working. I'm brand new to this smartphone/android scene and unfortunately I know ****all about how to do any of this. I do have some very rudimentary programming knowledge and a willingness to learn. If there is anything I can do to be of help in getting this feature working correctly, I'd be glad to help. Any suggestions on anything I could do to try to be of service?
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/android-tp2/146375-mic-detection-3-5mm-rhodw-only.html
ACL is working on those advanced features arrrghhh mentioned. I don't know if you have both a extusb and 3.5mm headsets, or even if ACL needs more than just the one tester, but the above thread requests such testers. After that, ACL might be the one to talk to on aiding with 3.5mm code.

Thanks for the suggestion. I don't have any of that hardware he's looking to test. I got my RHOD500 second hand and the only headsets I'm using are standard headphones with no buttons or mic.

[Q] Bluetooth disconnects?

I can't seem to find any mention of this anywhere else, and I have looked. My wife and I both have E4GT and are both experiencing this issue everyday and we both have different Bluetooth headsets.
We will walk away from our phones far enough that our headsets disconnect. Once we close enough, sometimes they connect back up, but most of the time, we have to shut off the Bluetooth radio in the phone and turn it back on before it will connect again. Once in a while we are right next to the phone and it will disconnect for no reason at all.
My wife has a cheaper Rocketfish headset and I have a more expensive Jawbone.
Anyone else having this problem?
both our phones are rooted and we're both running Caulkins rom. She is running an older 2.8.0 and I am sporting 2.8.1. I have asked this in his rom thread, but twice have gotten no responses. I can't find anywhere if there is a Bluetooth radio driver update like with modems.

Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App

davidc23 said:
Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
HAHA, I knew someone would ask that!
To be honest with you, we got these phones and two hours later, I had them rooted and flashed, so I couldn't say. I've been rooting and flashing roms since we had our first Droid 1 phones and I just can't seem to leave well enough alone.

I have the same issue with a Jawbone Era.
Has happened on stock roms as well as Caulk's and UnNamed.
What happens with my Era is that it will just stop working. Phone will show that it is still paired, but I get no audio to the device. The only way to fix it is to turn off the Era headset, and turn off bluetooth on the phone. Then turn BT back on, followed by the headset.
It's a real PITA. I got this headset after reading several reviews on the webs saying that it was a great unit.
It is, when it works. Unfortunately this happens at least once a day.
I am looking for a solution as well, and I was even thinking of getting a different headset but after reading that it's happening with completely different headsets makes me think that won't solve anything.
I'll try to report back if I find anything.
One other note, the Jawbone Companion app also is very flaky. Most of the time it will not detect the Era headset even when the phone is connected and it's working fine. This too happens on both stock and custom roms.

Bluetooth
Make sure your phone is set to always discoverable and when you get back in range of your phone try hitting the call/end button on your bluetooth, this should help it re-connect without having to restart the program in your phone.

I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!

jb8301 said:
I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!
Click to expand...
Click to collapse
I'm seeing a pattern here. It appears from what I'm reading, that it does not matter what Bluetooth headset you have or what rom you're running, it's happening to a few people. Makes me think it's the phone or Gingerbread itself that's the issue. Maybe when ICS is ready to be a daily driver, it'll change.
In one respect it makes me feel better as my wife and I don't have to replace our headsets!!
I am not comfortable in leaving our phone "discoverable" as this opens our phones to possible unwanted access from unscrupulous people.

Why is everyone avoiding LK8?

It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?

Wifi issues, and until recently the inability to go back to older firmware mostly.

Interesting, I haven't seen any WiFi issues. Samsung devices always have crap radios, and LK8 seems on-par with the other releases.

Jellybomb, H20 and MIUI are great Roms and that's why they're on LK8. Hehe
Sent from my SPH-L900 using xda app-developers app

It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.

JellyBomb is great in function, but on every device I've ever used it on, the theming causes problems. Fonts covered, hidden, etc due to the blue. Guess I'll try it again.

Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
This. And also simply because the devs don't want to work with a leak. Who would? Also I prefer few roms with less bugs than a variety with problems.
Sent from my SPH-L900 using xda premium

ScrapMaker said:
It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?
Click to expand...
Click to collapse
LJC works with fewer issues more often for more people than lk8. Many devs stick to it because of all the bugs that stem from lk8.
Sent from my SPH-L900 using Tapatalk HD

I know a lot of devs only upgrade to official releases and newer doesn't always equal better as well
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition

Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
Compared to my HTC Evo series (any of them,) I'd say it's pretty obvious all the radios are quite inferior. That's good information that this firmware might contribute to that though. Thanks!

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol

thunderwagn said:
The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol
Click to expand...
Click to collapse
I was one of the early catchers of that bug, and was vocal about getting some dev involvement. At the time it was a permanent error, and a pain in the a$$, I had the choice of LJC with HFA/chameleon FC errors (permanent, no matter how it was wiped back to stock), or no wifi.
Thanks to Garwynn, EvilKoncepts, a pal that did testing for them (can't remember his name), there is now a verified fix for it. (Has to do with LK8 changing carrier partition).
So right, most devs don't want to mess with leaks for official releases.
I won't touch it, at least not for now. LK8 has some nice little features, but I'll hold out for a bit, hope a (better? official?) version gets posted by Sammy for SxTp to bring us.

personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.

t3project said:
... the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
normally, I might agree with you, having seen most issues caused by user negligence/ignorance. and fixed by proper procedure being used to reapply a ROM/Odin a stock. but in my (and several others) case, this was on Stock rooted, with the SxTp Stock leak applied. Wifi died for no reason after aprox 24 hrs use. No amount of wiping/resetting to fact-default would fix it.
But going back to LJC did, while bringing other (well documented) problems with it.

t3project said:
personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
The only real bug I've found in lk8 is the wifi issue, it seems to not like certain wifi frequencies or channels, as it will connect to some routers but won't connect to others. Could possibly be an issue with the wifi supp or wifi conf files. The other big issue is the carrier partition upgrade in lk8 causing issues when going back to ljc
I like to break stuff!

I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.

ScrapMaker said:
I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.
Click to expand...
Click to collapse
I don't have any issues with BT or audio over the 3.5mm jack. Although I don't have BT in my car I use a headset while I'm working and will have headphones on in the other ear and it switches back and forth just fine
I like to break stuff!

I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.

ScrapMaker said:
I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.
Click to expand...
Click to collapse
I'm using ljc. Was stock but I've been building my own rom off of the stock OTA and haven't even messed with anything BT or audio out related and have no issues. Maybe it has something to do with your BT device itself, perhaps it and the phone aren't communicating properly after its been idle for a while. I had an old Motorola BT headset that would go idle/sleep and never wake up unless I pressed a button on it so I'd have to answer the call with the phone then press the button on the headset to switch over
I like to break stuff!

Mic Mute/Cut Out Problem Still Exists!

I love nearly everything about my Verizon G'Nex, except for the fact that it sucks as a telephone. Voice quality is mediocre, at best, when the phone actually works. Meanwhile, my mic will typically mute itself in mid-conversation leading to "can you hear me?" and "you're hard to hear!" exchanges.
I have tried multiple ROM's and Radio's, including the latest stable CM and the latest stable AOKP. Each flash was clean, as I don't like taking chances with a dirty flash.
I have tried the app "SoundAbout," and the Wired Headset Detection setting is on "IGNORE Plug In/Out Detection (helps if phone is sending invalid plug in/out signals that shut off the speaker/mic)."
I have searched high and low on messageboards (XDA, Androidforums, etc.) to find a solution with no success. It seems that the problem either disappeared for most people and/or people have moved onto other phones. Literally, most threads and posts are from late 2011/early2012.
Issue happens whether I am home, away at work, or in a random parking lot somewhere. Contrary to popular belief, I don't think it is location-related, but rather, is hardware related.
I have 4G turned off.
Does ANYONE know if a fix exists?
On another related note, I am considering picking up a used SGIII from Swappa. I have to go the Used route since I want to keep my Unlimited Data Plan for as long as humanly possible. Does the SGIII have the same mic mute issues? Are there any other poweruser used phones that I should consider?

Comp625 said:
I love nearly everything about my Verizon G'Nex, except for the fact that it sucks as a telephone. Voice quality is mediocre, at best, when the phone actually works. Meanwhile, my mic will typically mute itself in mid-conversation leading to "can you hear me?" and "you're hard to hear!" exchanges.
I have tried multiple ROM's and Radio's, including the latest stable CM and the latest stable AOKP. Each flash was clean, as I don't like taking chances with a dirty flash.
I have tried the app "SoundAbout," and the Wired Headset Detection setting is on "IGNORE Plug In/Out Detection (helps if phone is sending invalid plug in/out signals that shut off the speaker/mic)."
I have searched high and low on messageboards (XDA, Androidforums, etc.) to find a solution with no success. It seems that the problem either disappeared for most people and/or people have moved onto other phones. Literally, most threads and posts are from late 2011/early2012.
Issue happens whether I am home, away at work, or in a random parking lot somewhere. Contrary to popular belief, I don't think it is location-related, but rather, is hardware related.
I have 4G turned off.
Does ANYONE know if a fix exists?
On another related note, I am considering picking up a used SGIII from Swappa. I have to go the Used route since I want to keep my Unlimited Data Plan for as long as humanly possible. Does the SGIII have the same mic mute issues? Are there any other poweruser used phones that I should consider?
Click to expand...
Click to collapse
No one, eh?

I had the problem when my Nexus was on 4.0. When I was updated to 4.2 (stock) the problem went away.
I'm assuming it had more to do with the radio updates then then ROM update.
Sent from my Galaxy Nexus using xda app-developers app

I'm on the latest CM which is 4.2.2, and it uses the latest radios, too.
The only other thing I can think of is that my headphone jack might be triggered due to tiny pieces of lint. However, the "SoundAbout" app should be ignoring the jack to begin with.
(Trust me, I'd rather keep the G'Nex rather than spending $300-$400 on a used SGS3, but that seems like the only option considering I can't hold phone conversations anymore).
Sent from my Galaxy Nexus using Tapatalk 2

[Q] SM-P600 with 3G USB Key?

Hello,
I have a SM-P600 with Android 4.4.2 (Note 10.1 2014 Edition) and would like to use my 3G USB Key (Huawei E1752) ; This 3G stick works fine on my old TF101.
I've tried to use it with my SM-P600 but infortunetely, it doesn't seem to work, even with the "PPP Widget" apps. PPP Widget displays the famous "No driver found" issue. Josh, "PPP Widget" developer, told me ther eis no way for the moment to make his apps working because there is no loading module (.ko file).
So I wonder if I could use a SM-P601 ROM (SM-P600 with 3G) on my SM-P600 to get the right modules or flashinf P601 ROM on P600 means "brick"?
Otherwise is there another way to make a 3G USB key working on this tablet?
Best regards.

Unfortunately...
Part of the problem is that a custom kernel module would need to be loaded with root, via insmod, and this would need to be coded and constantly reinjected on boot. As far as I know most of these fobs do not make their drivers open-source, specifically, although I could see a possibility in modifying one of the generic drivers from a typical linux full install (likely heavily modified). Even with a ko/kernel module, however, it's possible that the fob might not be able to get enough power from the tablet, itself; I'm not sure what the power draw is, but I have a few laying around; I could probably check that later on.
All of that said, while it may be possible to try to hack something up to work with OTG (for instance I know it CAN be done with external network devices in general (there have been successful drivers built for external Alfa wifi usb-based adapters, but that's wifi), my suspicion is that even if 1) and 2) here were fulfilled, there'd need to be support in other ways built into the ROM itself (I'm wondering if a bunch of the code for this could be pulled from the existent 605 ROM though, which is a consideration). I'm not sure if, for instance, even if JB/KK on the Galaxy Note 2014 were to be made to recognize it, you wouldn't have to disable other things to make it work; I know for the external USB wifi devices, a hack was needed to disable the onboard wifi within the device.
If I had the time or the money I'd certainly be willing to try to make something custom in general. That said, I'm wondering if linuxonandroid (search the forums, or check out linuxonandroid.org) might support it out of the box on the full system img's (given functionality, Kali's kernel probably has the best chance of any of the current available ones, but I don't really know; I'm grabbing the image later on tonight to see what happens if I try)...
In general, though, I suspect that even if this somehow partially works, there are going to be a lot of problems that only a real custom ROM would solve. Though frankly, I can't figure out why nobody has yet. Maybe, like me, people just don't have enough time, and the people who do have time and the skill don't really need a specialized ROM enough.
I'm still kicking myself in the butt for not getting the 3G version for development purposes, personally; hundreds of dollars more for what one could get in a USB fob for 20-30 bucks only sounded like a bad deal til I wanted the functionality; your best bet may be to get a crapper of an android phone for under a hundred dollars and just let it be a hotspot. It's what I finally just gave in to doing. The one upside is decent battery life; if the P600 could supply enough power for the USB 3G dongle to work, all USB-dongled devices, to the best of my knowledge, kill batteries faster than anything built-in would.
Good luck.

Yes... You're probabably right. Don't know.
And I could use an old phone to be a hotspot or something else like that, but it's not what I want :cyclops: Just one device for all will be better.

Kasimodo said:
Yes... You're probabably right. Don't know.
And I could use an old phone to be a hotspot or something else like that, but it's not what I want :cyclops: Just one device for all will be better.
Click to expand...
Click to collapse
I'd really prefer the same thing, myself. I generally carry around a phone with my other stuff anyway and don't use it for much in the way of voice calls, so it's not too much of a burden. There's also hostapd in linux, or any of a number of mobile routers you can boot up in vbox, if you're carrying a laptop around at the same time; I really hate that our devices, and android in general, won't do 'ad-hoc' networks. I think that's one of my biggest gripes.
I suspect once Ubuntu touch is fully stable it'll be our best option; at a minimum I'm pretty sure I could easily crank out a driver for that. Android, I'm not sure. I'll let you know if I find the time to dig around with with droid though; I've been meaning to learn more about device driver support in Android anyway, now that it's finally pretty much mature.