Related
I've spent a lot of time the last week or so on trying to figure out if it's possible to enable bluetooth on whistlestop's CM7 without having to rebuild the kernel. I've made some progress - if it's possible - or I've just wasted a lot of my time and learned a little about Linux and Android if it's impossible.
Where I am now:
Thanks to whistlestop's guide, I have a working build of CM7 for Kindle. I've got a Kindle running CM7 but have been unsuccessful in loading btwilink.ko via insmod so far. Dmesg shows several unknown symbols which I think may be related to not having st_drv.ko loaded first. insmod fails in init_module with "No such file or directory". I do not currently have a st_drv.ko built for 2.6.35.7+ but I haven't really tried to find it yet.
uim-sysfs seems key but I'm not sure where it comes in - if I load it and it loads the drivers or vice-versa.
What I have found:
Device driver info for a WiLink solution in Android: http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution
btwilink built for 2.6.35.7+ ARM: http://www.angstrom-distribution.or...le-btwilink_2.6.35.7-r113c_omap4430_panda.ipk
Source for uim-sysfs: https://github.com/CyanogenMod/android_device_bn_encore/tree/gingerbread/uim-sysfs
Firmware: https://gforge.ti.com/gf/download/f....1-P2-Pandroid-1.0-Linux-x86-Installmentioned
Interesting thread that may or may not apply here discussing loading btwilink.ko: http://e2e.ti.com/support/low_power_rf/f/307/t/115891.aspx
Questions:
How different are kernel versions 2.6.35.7 and 2.6.35.7+? The "+" tacked on doesn't comply with the kernel version numbering scheme I read up on. Is this just an android thing, a CM7 thing or a TI/OMAP thing?
I am assuming that a driver built on the same architecture and for the same kernel version should work even if the kernel and driver didn't happen to be built together. Is this a safe assumption?
Is the kernel in whistlestop's CM7 derived from a CM7 for a device which has bluetooth? (ie. was it built with bluetooth enabled?) I don't know how to tell conclusively...
Even if it's not possible to load the drivers via insmod, might it be possible to tweak a working CM7 build tree with the drivers, firmware and some editing to get the drivers to load at boot? I've been assuming that if it's possible to use these drivers in a build tree, it should be possible to just load them post-boot since either way I didn't build them.
Is building the linux kernel for Android difficult? I've been avoiding even starting down that road, thinking that this would work with the drivers loaded via insmod - am I spending a lot of time avoiding something relatively easy?
Is this a lost cause without building the kernel? If so, why? I'm leaning towards the answer to this question being yes based on the first link here. It sounds like there may be some config options set and structures or entry points defined at kernel build time that, if not done, will make it impossible for the kernel to load and/or communicate with the drivers.
Good luck on the bluetooth.
im pretty sure the kindle fire has no bluetooth
symbiiote said:
im pretty sure the kindle fire has no bluetooth
Click to expand...
Click to collapse
It does have bluetooth. It just was not activated on the stock rom.
If there will be no way to activate the bluetooth, im going to smash my kindle so hard, its gonna wish it's not even made.
Hardware question
I appreciate the effort you are putting forth, I would really enjoy using my BT headphones w/pandora on my Kindle. Are you sure that the bluetooth on the chip is even enabled? It wouldn't surprise me if they disabled the connection on the die when they made the chips (licensing fees/fair competition/etc.) As a community we may need a hardware expert to pull a device apart and check connectivity across the paths before anything on the software end is even explorable.
Not trying to be a downer, just a thought. Please prove me wrong with your efforts
biglama said:
I appreciate the effort you are putting forth, I would really enjoy using my BT headphones w/pandora on my Kindle. Are you sure that the bluetooth on the chip is even enabled? It wouldn't surprise me if they disabled the connection on the die when they made the chips (licensing fees/fair competition/etc.) As a community we may need a hardware expert to pull a device apart and check connectivity across the paths before anything on the software end is even explorable.
Not trying to be a downer, just a thought. Please prove me wrong with your efforts
Click to expand...
Click to collapse
that has been done. There is discussion in the CM7 ROM thread about bluetooth with links to teardown. Whistlestop CM7 developer thread.
http://forum.xda-developers.com/showthread.php?t=1390773
Discussion on bluetooth in CM7 thread.
http://forum.xda-developers.com/showthread.php?p=20283669&highlight=bluetooth+teardown#post20283669
Here is the teardown:
http://www.ifixit.com/Teardown/Amazon-Kindle-Fire-Teardown/7099/1
Using Tapatalk on a Kindle Fire w CM7 ROM
wow guess you learn something every day. Well in that case i wanna use Bluetooth o.o
Sent from my LG-VM670 using XDA App
Let me set things straight.
-There is bluetooth hardware in the Fire. The WiFi module has bluetooth, WiFi, and FM radio on the same chip.
-The module needs additional connections to the CPU above and beyond what's needed for WiFi to make BT or FM work.
-The module does not need another antenna for bluetooth. There is a second chip in the module that multiplexes the one antenna for WiFi and BT.
-You will not be able to just build the drivers and make them work without knowing where the connections are located. If they exist at all.
-There are two sets of connections needed to the CPU. The first is a high speed serial channel. Because of the choices made by Amazon for other UARTs on the Fire, this must be ttyO2. The second is an enable signal to turn power to the BT subsystem on and off. This could go to one of dozens of signals, and would need to be probed for.
-The module is a BGA package, and many of the connections are done through blind vias. In English, that means that the connections between the chips cna only be seen if you desolder them. This would mostly destroy the Fire, but would allow existence and location of those connections to be confirmed.
Has any one else experienced the issue that the Fairphone performs a soft reboot when turning on USB storage, effectively making it impossible to transfer files to/from your phone the normal way? I have disabled the mood background, so that can't be it...
As a workaround, for now I'm transferring files through adb, but that's far from ideal.
Vinnl said:
Has any one else experienced the issue that the Fairphone performs a soft reboot when turning on USB storage, effectively making it impossible to transfer files to/from your phone the normal way? I have disabled the mood background, so that can't be it...
As a workaround, for now I'm transferring files through adb, but that's far from ideal.
Click to expand...
Click to collapse
Same problem here. Today I recognized that there is no connection via USB possible anymore. Didn't use this function for some days but always I try right now it leads to softreboot. Still using 1.1 Caju.
Reproducible. Possible workaround:
Yes, this is reproducible.
What works for me: turning on USB debugging, turning of XPrivacy and GravityBox, re-initialise XPosed framework, hard-reboot.
I figured it might have something to do with XPrivacy, but I'm not able to do further research at the moment.
I also got no time to edit the Wiki - could someone please do that? If you've got an account here, you can edit the wiki, folks! If you do, could you consider adding info on this thread for faster A-GPS locks?
/backtowork
boondiordna said:
Yes, this is reproducible.
What works for me: turning on USB debugging, turning of XPrivacy and GravityBox, re-initialise XPosed framework, hard-reboot.
I figured it might have something to do with XPrivacy, but I'm not able to do further research at the moment.
I also got no time to edit the Wiki - could someone please do that? If you've got an account here, you can edit the wiki, folks! If you do, could you consider adding info on this thread for faster A-GPS locks?
/backtowork
Click to expand...
Click to collapse
Since there's no real solution yet, what should we put on the wiki and where? Here?
Since I use XPrivacy and GravityBox as well, it might be related to (one of) those. Another partial workaround I have is to connect the phone to my computer, then in the notification drawer touch "Touch for other USB options", and then select either "Media device (MTP)" or "Camera (PTP)" as opposed to the default "USB storage". This will only be useful when you want to transfer media (audio, pictures, videos, ...) to and from your device though...
Hey guys, I have searched high and low for a solution to this problem but have come up empty so far. I just got a joying head unit and everything, including the easy connected app, seemed to work without issue. I decided well since I had the headunit running next to my pc that I would flash Malaysk's custom rom before installing it. After that, I reinstalled the app from various sources including the oem app but none of them seem to allow me to connect my same exact devices anymore.
Why is this important for me? I had planned on controlling a tablet in the back seat for my son who is still to young to put on show without trouble. Essentially, this would allow me to never have to reach back there to help him out.
I have read, from joying, that it would no longer work after flashing new firmware but that seemed to not be the case from some things I had read here (please correct me if I am wrong on that). Tried different cables and ports but no luck. I did read that a license might need to be carried over but not sure what that entails as I can find ZERO info on this easy connected app/problem. I hope that this is a very simple fix and that I did not jump the gun again for the chance to flash a new device (its addicting and I blame XDA for my problems...).
I did try and find some other apps that might allow me to do the same thing. RemoDroid seemed promising but didn't function. Most other ones are meant for controlling from a pc or browser and just weren't useful for the task at hand. I am open to solid suggestions. I use all Android devices and avoid the Apple juice. Any insight you guys can offer will help a tired Dad out. Thanks!
Edit: Solved-ish
The easy connect app seems to function now intermittently. Not sure there was a specific thing that I did to fix it. Seems to work when I launch easy connect app right after booting up and nothing else. Messing with other apps seems to cause a problem for my devices. Also, switching between my devices(phone and tablet) may also have been causing a problem, not sure yet. I suppose I'll just keep trying to make it work reliably until I break it again.
On the previous version of the easy connect app, you were able to disable Drive Mode from launching. Not so on the newer version with Android WiFi. If anyone has a solution to that I would appreciate it as the Drive Mode app is useless for my needs.
Note 4 - USB - works great. I have yet to try over wifi
Note 10.1 N8013(lollipop rom) - USB/Wifi - works great (disable smooth mode, remote device screen cannot be turned on with easy connect "Home" button)
http://forum.xda-developers.com/and...1024x600-rk3188-joying-try-uploading-t3262030
I tried several different apk's but they all have similar results and end with a connection failure.
I haven't yet tried going back to stock firmware so that might be worth trying. I installed the headunit in my car so I'm not as willing to keep flashin it as I have to park down the street from my house.
So not sure what magic I used but I was able to get it working for a moment and then it stopped again. USB and Wifi android mirroring were working so I know my current firmware/setup is functional!! Once I got it working I started configuring some other apps and when I went to run it again it wasn't connecting. I guess I'll just keep messing with it until I can figure out what got it working again.
With the newer version of the easy connected app, I can no longer disable launching of drive mode on connect. Is there a way to disable that option with the 1.4 version?
Hi.
Is it possible mirror in wifi with android?
Can you explain the way?
Inviato dal mio SM-G920F utilizzando Tapatalk
Hi, as the title says, had a question about using GSI's now that treble is available for our phone. I understand that in order to use treble, we must first flash the newest build of Lineage, and then install a GSI. My question is, if Lineage is installed, does it somehow serve as a base that the GSI installs over, or is installing it only pertinent for updating the partition layout? I guess more specifically, if I install the new Lineage, and then flash a GSI over it, will I experience the same bugs in Lineage in any potential GSI installed?
In my case, it's with android auto, since it doesn't seem to work/project over USB with any car I've tested on any of the currently available ROMs. The app works in Lineage, and the phone can connect via Bluetooth to a car, but it doesn't recognize that it's physically connected to a car at all via USB, so it fails to project to the vehicle's display, meaning I need to constantly look down to where it's plugged in at to interact with it instead of through the vehicles built in touch screen, keeps me going back to stock honestly because it's a feature I need access to.
If I install a GSI where auto is properly working, should it work for me as well or no because Lineage doesn't support it currently and that was flashed before the GSI was?
Thanks
davehasninjas said:
Hi, as the title says, had a question about using GSI's now that treble is available for our phone. I understand that in order to use treble, we must first flash the newest build of Lineage, and then install a GSI. My question is, if Lineage is installed, does it somehow serve as a base that the GSI installs over, or is installing it only pertinent for updating the partition layout? I guess more specifically, if I install the new Lineage, and then flash a GSI over it, will I experience the same bugs in Lineage in any potential GSI installed?
In my case, it's with android auto, since it doesn't seem to work/project over USB with any car I've tested on any of the currently available ROMs. The app works in Lineage, and the phone can connect via Bluetooth to a car, but it doesn't recognize that it's physically connected to a car at all via USB, so it fails to project to the vehicle's display, meaning I need to constantly look down to where it's plugged in at to interact with it instead of through the vehicles built in touch screen, keeps me going back to stock honestly because it's a feature I need access to.
If I install a GSI where auto is properly working, should it work for me as well or no because Lineage doesn't support it currently and that was flashed before the GSI was?
Thanks
Click to expand...
Click to collapse
I think that is kernel side as our HDCP goes to the greybus instead of USB-C for the projector mod. I know through wireless it works. Tried it on my friend's 2016 Hyundai Santa Fe.
GSI's will have the same bugs via vendor and boot. Also, unless the GSI supports moto mods, those won't work either.
Uzephi said:
I think that is kernel side as our HDCP goes to the greybus instead of USB-C for the projector mod. I know through wireless it works. Tried it on my friend's 2016 Hyundai Santa Fe.
GSI's will have the same bugs via vendor and boot. Also, unless the GSI supports moto mods, those won't work either.
Click to expand...
Click to collapse
Oh, I didn't think motomods had anything to do with android auto. It doesn't use the pins on the back or anything, just usb, but I can't project via USB, it just brings up the USB select menu (charge, mtp, ptp) and neither of my cars support wireless android auto. I didn't think there were any cars out yet that actually support wireless android auto.
Oh well, guess stock it is for now, thanks for the info.
Edit:
@Uzephi hey, sorry to be a bother, you said you were able to use wireless android auto on a friend's vehicle. I'm assuming that means it's enabled on custom ROMs since it doesn't appear to be on stock. Do you happen to think a mod like this would work?
https://forum.xda-developers.com/ge...droid-3-0-proxy-gateway-android-auto-t3813163
Just curious, because if I could use wireless projection for it that would work just as well to me.
davehasninjas said:
Oh, I didn't think motomods had anything to do with android auto. It doesn't use the pins on the back or anything, just usb, but I can't project via USB, it just brings up the USB select menu (charge, mtp, ptp) and neither of my cars support wireless android auto. I didn't think there were any cars out yet that actually support wireless android auto.
Oh well, guess stock it is for now, thanks for the info.
Edit:
@Uzephi hey, sorry to be a bother, you said you were able to use wireless android auto on a friend's vehicle. I'm assuming that means it's enabled on custom ROMs since it doesn't appear to be on stock. Do you happen to think a mod like this would work?
https://forum.xda-developers.com/ge...droid-3-0-proxy-gateway-android-auto-t3813163
Just curious, because if I could use wireless projection for it that would work just as well to me.
Click to expand...
Click to collapse
Android Auto uses video over USB. Our ancillary video output is rerouted to the greybus for the projector. Only way to get SElinux to work correctly on aosp was to keep that routing and nix USB video.
I honestly don't know. I did it for kicks to see if his Android Auto app on his Santa Fe would Sync with my phone and it did. It wasn't any projection, it was just the two apps talking to each other. Is that how yours is or is your phone running android auto and the radio is taking the phone's screen as a projection? Because I could be wrong. That is the only thing I could think of why yours wouldn't work.
Uzephi said:
Android Auto uses video over USB. Our ancillary video output is rerouted to the greybus for the projector. Only way to get SElinux to work correctly on aosp was to keep that routing and nix USB video.
I honestly don't know. I did it for kicks to see if his Android Auto app on his Santa Fe would Sync with my phone and it did. It wasn't any projection, it was just the two apps talking to each other. Is that how yours is or is your phone running android auto and the radio is taking the phone's screen as a projection? Because I could be wrong. That is the only thing I could think of why yours wouldn't work.
Click to expand...
Click to collapse
Ahh gotcha, that makes more sense now.
I can pair the device to the vehicle over bluetooth and use the android auto app that way to play music and stuff, but yeah, normally it takes the phone's screen as projection, so I can use the car's 7in display for android auto without having to play around with my phone. Understanding that video over USB is disabled makes sense as to why auto isn't working. I'm guessing this means it won't work on custom ROMs without a custom kernel, and that would have to disable SELinux and reroute video to USB, correct?
Thanks for all the info, always good to learn something.
davehasninjas said:
Ahh gotcha, that makes more sense now.
I can pair the device to the vehicle over bluetooth and use the android auto app that way to play music and stuff, but yeah, normally it takes the phone's screen as projection, so I can use the car's 7in display for android auto without having to play around with my phone. Understanding that video over USB is disabled makes sense as to why auto isn't working. I'm guessing this means it won't work on custom ROMs without a custom kernel, and that would have to disable SELinux and reroute video to USB, correct?
Thanks for all the info, always good to learn something.
Click to expand...
Click to collapse
Yes that is correct. The Z2 development crew tried but the workaround would have been messy and not true SElinux enforcing which makes me wonder about stock rom tbh.
Hi,
I'm looking for a developer to implement features into a ROM. The features are as follows:
Note: An Ethernet adapter (with a charging functionality) will always be physically connected to the device.
Switch on the device once the power source has been switched on.
Enable Ethernet Tethering (ET) after boot-up and check its status frequently in the background e.g if it's off at some point, then enable ET
Implement an icon to show that Ethernet Tethering is enabled in the top bar.
Replace the stock boot-up animation with a custom animation/image.
Turn off the device after some minutes once the charging source has been switched off.
Unfortunately with Android 11+, Ethernet Tethering is a limited functionality relative to checking status, enabling on boot/charging.
I recently used a macro with Tasker/Automate but I'm not happy with the reliability of the result. I have tasks such as check/enable ET after boot, after AC charger input (because the Ethernet adapter has a charging port as well), and check/enable ET after unlock. This is all done via the UI and obviously has its bugs and limitations. So my only other option (that I know of) in terms of greater reliability would be to root the phone and implement the features, as mentioned, into the ROM.
In terms of the ROM and Android device, there is a probability that the device will change over a long period of time. After doing some research, I understand that a GSI ROM would therefore be more suitable. What do you think?
If you are interested, please PM me and we can discuss the financial side of this project.