yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] freakshow999:
I was talking to my friend about it he said it may be related to the android code calling for a BT storage device also when this is enabled.

Unfortunately for me I use my tablet like a laptop most of the time with a BT mouse and keyboard.

You would think Google can get this to "Just Work" like the BT audio and OTG storage, as everyone knows these should be inherent features of the device....

Many thanks to the guys that have been working on this and I hope you get a chance to address my issues.

Sent from Keone's Nexus 7 using Tapatalk 2
[Nexus 7 Android Development] AndDiSa:
As I already wrote in my last post: all the issues/sucess stories you are discussing here are related to the kernel/boot-image which is flashed as a 'side effect'. If you have issues with bluetooth most likely the kernel doest not have support for those devices compiled in.
[Nexus 7 Android Development] freakshow999:
Stock kernel?

Maybe I'm missing something? Sorry if I'm being a newb about this but it seems a bit confusing that the devices work fine on the stock kernel and when I flashed the otg zip they stopped working. I'm running Scott's CleanROM 3.0 with the stock kernel it came with. Do I need to install the CM10 kernel?

I will read through the entire thread again...

Sent from Keone's Nexus 7 using Tapatalk 2
[Nexus 7 Android Development] AndDiSa:
The reason is: the zip is flashing a new kernel -> you are no longer on stock kernel ...
[Nexus 7 Android Development] freakshow999:
Thank you for the clarification. Is there a way to install the hack without changing the kernel? Or is that what the last file on the OP is for?

Sent from Keone's Nexus 7 using Tapatalk 2
[Nexus 7 Android Development] AndDiSa:
The last file of the OP doesn't work.
[Nexus 7 Android Development] michaelm_007:
@all

Updated ZIP-file in my OP :confused: Working this file with your bluetooth-devices?
[Nexus 7 Android Development] AndDiSa:
Can you tell me, what boot.img you are flashing? From where did you take it?
[Nexus 7 Android Development] delanvital:
Noob question

What does this patch do?

I have an OTG cable and I can plug in anything, and it works. Mouse, HDD, keyboard, whatever. Well, DVD-drive didn't work, but that was about it. I haven't patched anything. I usually run one of the latest CM10 nightlies.

Sorry for being daft!
[Nexus 7 Android Development] freakshow999:
It's for otg storage devices I.E. thumb drives. Other hardware like the ones you mentioned are activated on stock android, however, storage capabilities are not.

Sent from Keone's Nexus 7 using Tapatalk 2
[Nexus 7 Android Development] zolaisugly:
Can you tell me if this will work on stock ROM 4.2.1 and stock kernel.

I am rooted/open bootloader with twrp.
[Nexus 7 Android Development] alfeuss:
Read the OP...ie the first post in the thread.
[Nexus 7 Android Development] farhanito:
My Bluetooth mouse still no go for me..

Thanks anyway :)
[Nexus 7 Android Development] jauffre:
hi, i flashed the 4.2.x zip on my stock rooted nexus7, it can read the usb drive properly, but i cannot edit/add any file on it: when i try, it gives me a "EACCES (permission denied)" error.

does anyone else have the same problem? it should be due to the missing native sdcard support.
[Nexus 7 Android Development] Cosa44:
I just flashed it and no problems so far. I copied an .apk from the internal SD to my USB OTG just fine. I'm rooted running PD 2.99 Beta 6 /a17 M-Kernel. It doesn't show up under storage in the settings like I've had before, but its still a great find!
[Nexus 7 Android Development] alfeuss:
From what I read it replaces your kernel. You might what to check for that.
[Nexus 7 Android Development] Cosa44:
Yup, you were right. I reflashed the kernel and went back to stickmount. Thanks for the heads up.
[Nexus 7 Android Development] libb:
I can mount USB flash disk only when it is formatted as FAT32. Any chance to support NTFS or exFAT? I would to like transfer files freater than 4GB.
[Nexus 7 Android Development] AndDiSa:
Currently only fat is supported.
[Nexus 7 Android Development] alfeuss:
try root stick mount for now.

StickMount can utilize the "ntfs-3g" and "mount.exfat-fuse" binaries to add support for ntfs (untested) and exfat, but these are not included. If you place the "ntfs-3g" or "mount.exfat-fuse" files in the root of your internal storage ( /sdcard ), StickMount will automatically use them.
[Nexus 7 Android Development] Cosa44:
Yup, what he said.
[Nexus 7 Android Development] Cosa44:
[Well it looks like i spoke too soon. Using Stick Mount i tried to connect my Western Digital 2TB external hard drive and It WORKS!!! The file system is NTFC and it was listed under /SD Card/USB Storage/SD1. Has anyone else been successful with this? I can post a screen capture once i download an app for that. ATTACH]1545642[/ATTACH]
[Nexus 7 Android Development] sparksco:
Stick Mount also works fine for me.
[Nexus 7 Android Development] AZKJS:
Works fine on mine. Running cm10 4.2.1
[Nexus 7 Android Development] drakenabarion:
Oops! Sorry accidental post
[Nexus 7 Android Development] Ahres:
Hi. I used this OTG patch on motley kernel and my antutu benchmark drops for 500 points. it rewrite kernel part with modded cm kernel or its just library addon? Sorry for my noob question but im wonder about benchmark point loose.
[Nexus 7 Android Development] the1soulhunter:
Stock JOP40D Restore

Hi!

I tried to update from Stock JOP40D to JDQ39 by OTA yesterday, but update process failed due to system file errors caused by this patch, so I download and unpack the JOP40D original system/boot images, and build a uninstaller/restorer package.

This package also restores stock kernel (boot.img).

Tested on JOP40D 32GB Wifi.
[Nexus 7 Android Development] gpstar:
just a heads up, anybody flashing this on 4.2.2, this will break the dock functionality with charging, etc due to the boot.img contained in these zips. To fix, all you need to do is flash the boot.img with fastboot from the 4.2.2 JDQ39 nexus7 factory images.
[Nexus 7 Android Development] AndDiSa:
Even if michaelm_007s patch was not working as expected, his idea was not too bad. In my blog I wrote a small tutorial on what to do to enable native USB OTG support for the Nexus 7.I wrote also a little update.zip which, applied to a Nexus 7 with the current Android (JDQ39), will enable native support for USB OTG.
[Nexus 7 Android Development] daveheart14:
Hi,

I tested your patch and it does not work completely.

The key is recognized because when I removed the notification there is one but I can not navigate it. Folder mnt / usb-otg is empty.

In addition, there is a forced close when I go into Settings / Storage.

I emptied the cache and dalvik-cache.

Hoping to give you useful information, of course, if someone else can confirm ....
[Nexus 7 Android Development] AndDiSa:
AW: [PATCH] Enable native USB-OTG access on Nexus 7 (grouper) (02/12/12)

What model do you have and what Android version is installed?

Do you have installed a custom kernel /some other patches?

It's strange, that you have force closes, that's an indication to me, that your Android version is not fully compatible.

Going to settings / memory you should see a second entry USB storage. Here you can activate / deactivate (mount/unmount) your stick.
[Nexus 7 Android Development] daveheart14:
I'm on stock 4.2.2 Nexus 7 wifi and I installed the patch MultiROM.

Your patch is installed well, since I found out your boot.

I will do more tests in the day.

I will notify you.

Thank you.

Edit :

Hello,

Ok, it works. I found the problem. The two key usb (FAT32, 64 and 16GB) that I used do not work with the patch but they work with stickmount. If I insert them at the start of the tablet, I have forced close of the settings / storage.

If I start without and inserts after startup, not forced close but option "Install USB storage" remains gray.

I have a third key is detected and the memory storage usb option works well.

I also tried with my hard disk 2.5 (fat and ext), it tells me that the USB storage is empty and if I press the notification, a dialog box opens and asks if I want to format memory.

I did these tests on a system 4.2.2 with boot and system clean. I also tried with bootloader 4.13 and the 4.18.
[Nexus 7 Android Development] AndDiSa:
AW: [PATCH] Enable native USB-OTG access on Nexus 7 (grouper) (02/12/12)

Thanks for the info, I will investigate further, but I think I have an idea:

Do you have several partitions on those sticks / hard disk?

I did not check that behaviour, probably vold needs some hints.

Edit:

I think I found the reason: if the partition is formatted with NTFS it's not recognized and you are asked to format the partition. I think I will provide another version with NTFS support.

Edit2:

NTFS is supported by the kernel, but the reason for not recognizing NTFS partitions is the vold build in to Android. It expects a vFAT partition to be mounted, so currently there is no chance to add NTFS support without patching and providing a different vold.
[Nexus 7 Android Development] suchavibrantthang:
confirmed working on CleanROM 3.0 but tested bt and does not work. for now, i'll go back to stock kernel cuz i need my bt.
[Nexus 7 Android Development] AndDiSa:
AW: [PATCH] Enable native USB-OTG access on Nexus 7 (grouper) (02/12/12)

what is working on CleanRom?

The patch I am providing in my blog is intended to be used on stock Android 4.2.2 only. Nevertheless Bluetooth is working for me, even tethering with another phone.
[Nexus 7 Android Development] AndDiSa:
A small update to my progress of providing a working patch to enable native OTG-USB support: Today I've updated the patch and it supports NTFS now , currenty read only. The patch can be downloaded either from my AndDiSa Android Blog, or directly from otg-usb-enable-20130221.zip.

Please note: this patch is woking on a Nexus 7 (grouper), stock Android 4.2.2 only and it will break future OTA updates, i.e. upgrade must be done manually or you have to go back to stock Android 4.2.2 before.
[Nexus 7 Android Development] lightdesiny:
hi, the patch works really great, thank for your work, there only a little thing, when i unmount the usb and remove the usb stick, appear a persistent notification saying to insert a new media, how can i disable or make this notification not be persistent?, is not the big deal but it's annoying
[Nexus 7 Android Development] AndDiSa:
AW: [PATCH] Enable native USB-OTG access on Nexus 7 (grouper) (02/12/12)

Unfortunately this is the standard behaviour and I didn't find a simple solution yet to remove it. If I find something, I will post an update.
[Nexus 7 Android Development] legiong:
I've tried this on my Nexus 7 running 4.2.2.

Works great, even with NTFS which was my primary purpose!

I just have one issue:

When I eject, I go to storage and select to unmount USB storage, then I disconnect the OTG cable. After doing this I get a notification to "USB storage removed. Insert new media".

The only way I can get rid of this message is either reboot the device or long press on the notification, go to app info (System UI) and force close it.

Sorry if this has been discussed already but I didn't see it.
[Nexus 7 Android Development] FitAmp:
Literally right above your post...

Beamed via NFC
[Nexus 7 Android Development] legiong:
F*%k I am blind.
[Nexus 7 Android Development] tobyax:
Don't work on my nexus7 with paranoid android 3.16
[Nexus 7 Android Development] AndDiSa:
Works only with the original 4.2.2 ROM because the kernel will be exchanged.
[Nexus 7 Android Development] tobyax:
ok, thanks...

any alternative? I used stickymount, but does not work

sorry for my bad english
[Nexus 7 Android Development] rydog66:
so this ONLY works for STOCK STOCK STOCK..right?

Stock Rom

Stock Kernel

4.2

Just wanna be absolutely clear.

Thank you!!

Cheers,
[Nexus 7 Android Development] pissos13:
Used This and mounts fat32 USB pens.

To mount NTFS, i Used stickmount, and copied the ntfs-3g file to /sdcard as stated in description of stickmount.

I have 4.2.2 stock rooted.
[Nexus 7 Android Development] carabao72:
slimbean n7000 ?

Supprimé
[Nexus 7 Android Development] vmaxdragon:
How to install...

Hi all,

i'm have had a untouched nexus 7 before (JB 4.2.2).

But I'm wish to use the otg function and so I've rooted my tablet with nexus root toolkit.

Can I install this patch with this toolkit? Only with this zip file?

best regards,

harry
[Nexus 7 Android Development] slicingtaco:
Hi OP, any chance of this being able to port over to another device with the same specs (Hisense Sero 7 Pro)? Also is that the stock kernel included in the OP or modofied for OTG?
[Nexus 7 Android Development] Slevin911:
Does it work on Nexus 10?
[Nexus 7 Android Development] slicingtaco:
Just use Stick Mount from the Market
[Nexus 7 Android Development] Cerbumota:
Be carefull with Nexus 3G

I have just installed that in my Nexus 7 with JB 4.2.2. Not only not work, also my 3G conection too. Be carefully with that, because you can get a problem. My 3G system don't work. I'm going to update to JB 4.3. I hope the update solve this problem...
[Nexus 7 Android Development] AndDiSa:
You should have read / noticed that this is for grouper, i.e. the WiFi Nexus ...
[Nexus 7 Android Development] AcuraKidd:
anyone know how to get this working on 4.3?
[Nexus 7 Android Development] ryanjv:
seconded for stock 4.3
[Nexus 7 Android Development] theoctavist:
Yes please. Vanir.
[Nexus 7 Android Development] shikhar623:
will it work on the stock kernel?

thanks
[Nexus 7 Android Development] ZenInsight:
Anyone try this on stock (rooted) 4.4 yet?
[Nexus 7 Android Development] AndDiSa:
It will not work ...
[Nexus 7 Android Development] fmmsf:
So what exactly does this do? If the custom kernel im using supports USB otg already, should I still flash this?
[Nexus 7 Android Development] slicingtaco:
This package has a custom kernel that enables mounting storage devices. Along with drivers and other modified drivers to enable OTG. Keep in mind this patch was meant for the nexus 7 back in the 4.1 (or 4.2, I think... idk:what:). So don't worry about it.

Sent from my M470BSA
[Nexus 7 Android Development] fmmsf:
Thanks, man :)
[Nexus 7 Android Development] slicingtaco:
I believe native USB OTG drivers were added to N7 back in 4.3. So by now I believe OTG is supported natively by 4.4. No need of this anymore. You might need the stickmount app for mounting flash storage.
[Nexus 7 Android Development] AndDiSa:
StickMount is always a solution but the "native" modification was to eleminate all those external tools and added ntfs-support, too. I don't know currently whether the 4.4 already mounts external devices out of the box and currently I do not a propriate development environment set up, so do not expect updates. Nevertheless in my blog the modifications done are documented, so if someone wants to give it a try ...
[Nexus 7 Android Development] bland.life:
From this thread it looks like stock 4.4 has no USB-OTG support.
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
I have a Galaxy S3 I9300 for a couple of weeks now and I love it, other than the fact that I keep having a strange issue with the Bluetooth connection with my carkit. I've been searching forums for similar issues and I found a variety of carkit related problems, but none of the ones I found describe the same problem as what I'm having:

- Initially the Bluetooth connection works fine and I can play music or make a call through the carkit just fine

- When I switch off the car's systems and don't use any apps on the phone in the meanwhile, and then start the car's systems again, it establishes the Bluetooth connection just fine again

- When I switch off the car's systems and I use other apps for a while and then start the car again, it won't work. Bluetooth does appear to connect, but after that it just doesn't play ball. When I try to play a song at this point, the phone shows the song is playing, but neither the phone nor the car audio produces any sound

So anyway, every morning before leaving to work and every evening before going home, I reboot my phone first. Then I step into the car and it establishes the Bluetooth connection just fine. But if I don't reboot the phone first, it just won't work. Now I guess I could setup a tasker profile to automatically reboot the phone, but I'd rather just get the problem fixed.

I run a Galaxy S3 I9300 with stock Android 4.1.1, rooted. I have already tried to run the "Bluetooth Fix Repair" app and afterwards had to pair the phone with the carkit again, but that made no difference.

Any help would be greatly appreciated!
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
*bump*
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
Some additional info:

This issue has now also happened a few times while driving. While music (through Spotify) was playing over the bluetooth carkit, it would sometimes just stop working when I opened a different app (like for example opening an SMS). Spotify was still running (and the song was still ongoing) and also the bluetooth connection still showed as being connected, but it just wouldn't produce any sound anymore.

Anyway, it seems clear to me that this is a bluetooth issue, but I have no idea how I can troubleshoot this beyond what I've already done.

I would be happy to pay whoever can fix this problem..
[Galaxy S III Q&A, Help & Troubleshooting] ItzCrooK2UxD:
With an issue like you are describing it may be helpful to list the headunit model too. I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.

Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
My car is a Renault Megane RS, the carkit was built in. I believe it's called Renault Carminat TomTom.

I've covered everything like that in about 100 different ways, none of which made any difference.

Good point. It does have an SD card slot, but as far as I know that's only to update the maps of the navigation system. I'll see if I can figure that out.

Thanks for the tips!
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
[Galaxy S III Q&A, Help & Troubleshooting] ItzCrooK2UxD:
It is in fact very possible that it is your phone, but wanted to throw it out there that bluetooth headunits can be troublesome on their own. Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me. Also do you have other bluetooth devices in the car, such as the 3GS you mentioned?

Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
Yeah I had read that too in some other thread (I went through just about every bluetooth related thread I could find, before I posted this topic). Mine saves up to 5. It didn't have anything in there except for my previous phone, which I had cleared. I also tried re-pairing the S3 several times, that didn't make any difference either.

Now, I just read somewhere that some people are having disconnection issues on the same carkit. In their case, in the end the problem turned out to be that their carkit will import all of their contacts from their phone (so you can call people even while your phone is in your pocket), and this would cause trouble when there are contacts without a phone number associated with it (just like my thousands of Exchange contacts). The people in question are talking about random disconnects though, whereas in my case it happens after doing some stuff on my phone. So it's probably unrelated, but I'll give that a try anyway just to rule it out. I just need to figure out a way to stop the carkit from importing contacts, because removing thousands of email contacts is obviously not an option.

I'll keep this topic updated with any progress. If anyone has any other ideas, please keep em coming. Thanks for the help so far! :)
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.

I've installed alogcat just now. Does it just keep running automatically in the background?
[Galaxy S III Q&A, Help & Troubleshooting] ItzCrooK2UxD:
It reads a file that is being constantly updated (which happens to be the logcat file). Typically I will clear it right before doing what it took to cause the failure, like in your case in your car with the bluetooth on.
[Galaxy S III Q&A, Help & Troubleshooting] YoghurtPL:
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
Yep - I have that too. The weird thing is that in that situation the phone does seem to think it is connected, while it really isn't. Just to be clear: this is not the only way to cause this issue (because it also happens when trying to reconnect the Bluetooth while on the phone it hasn't been disabled in the meanwhile).

So far I haven't been able to pull anything related from the logcat.

Also, while reading up on common bluetooth issues, I came across some posts of people who were saying that some phone/carkit combinations are having trouble with 2-way communication (because I can stream music from the phone to the carkit, but I can also change a song using the carkit or initiate a phonecall from the carkit). I'm going to try to only use communication initiated from the phone, and see whether that makes any difference. In the meanwhile: does anyone happen to know anything about 2-way communication issues with bluetooth, and how to overcome such issues?
[Galaxy S III Q&A, Help & Troubleshooting] Apoc_:
Update:

- Updated carkit to latest firmware. No change, still same problem

- Have not been able to capture anything unusual in the logs

- I have a Bose Soundlink now, which is a wireless speaker. Whenever my S3 is connected to the Soundlink (with bluetooth), wifi doesn't work. Upon turning off bluetooth, wifi instantly works fine again. So this definitely confirms this is a problem with bluetooth on the phone, not on the carkit.

- Wanted to upgrade to Android 4.1.2 but Samsung won't let me, as it says the device is modified (rooted). Triangle away isn't helping. Damn you, Samsung. This is *the* reason I moved away from Apple, as I don't like companies who don't let you use your stuff any way you like. And now Samsung is moving down the same route. Idiots. Anyway, I guess the only option left, is to start using a custom ROM.

Does anyone happen to have experience in terms of solving bluetooth problems by using a custom ROM? I'm thinking of using Cyanogenmod 10.1