Related
Even though JB is more or less feature-complete on Defy(+) there are still a few nits which will be hard to squash without having access to features which are only available in later kernels (eg. the ION memory allocator). Given that this board is frequented by people who (theoretically at least) should be able to give a hand in porting the required drivers/features to get a 3.X kernel up and running on Defy(+) I started making an overview of those missing bits. It should only take a relatively small group of willing volunteers, each responsible for a driver or feature, to get those bits ported.
From a quick glance at the configuration options used with the currently used 2nd-boot kernel I come to the following list of drivers/features which will need to be ported to 3.X. Some of these might already be available under different names in the kernel. Others might have been ported but are simply not part of the kernel tree I used to make this comparison (Quarx2k/jordan-kernel; branch 3.0.8-defy_display). Yet others might not be needed in the newer kernel because their functions are taken over by other drivers/features.
This is not a complete list of features needed to get a kernel running on the Defy(+) (see mapphone_defconfig in branch 2.6.32 for what is needed).
In the following list I marked potential replacements in bold type, usually followed by a question mark (?) to indicate I'm not sure they are fully compatible replacements for the 2.6.X drivers/features. The drivers/features are listed in 2.6.X menuconfig order using Kconfig names and symbols.
Drivers needed for Jordan w/kernel 3.x
Top level
Support for open firmware device tree (ARM port)
ARM_OF -> USE_OF ?
Support for device tree in /proc
PROC_DEVICETREE
DSP Bridge driver
MPU_BRIDGE
System Type
Motorola Android Platform Phone
MACH_MAPPHONE -> MACH_OMAP_MAPPHONE ? complete?
Motorola Android Platform phone 2nd-boot kernel modifications
MAPPHONE_2NDBOOT
Export DIE ID code under /proc/socinfo
OMAP3_EXPORT_DIE_ID
Device Drivers/Misc devices
AKM8973 Magnetometer
SENSORS_AKM8973_AKMD
KXTF9 Accelerometer
SENSORS_KXTF9
Bluetooth power control driver for TI wl127x
WL127X_RFKILL
Motorola OMAP Device Type Driver
OMAP_DEV_TYPE_DRV
Motorola Modem PM Driver
MODEM_PM_DRIVER
Motorola netmux driver
NETMUX_DRIVER
Motorola netmux link driver
NETMUX_LINKDRIVER
Motorola Camera Driver
CAMERA_MISC
Device Drivers/Multimedia support/Video capture adapters
HP OMAP3 Imaging/3A driver
VIDEO_OMAP3_HP3A
Video out driver
VIDEO_OMAP_VIDEOOUT -> VIDEO_OMAP2_VOUT ?
Device Drivers/Sound card support/Open Sound System (DEPRECATED)
Audio driver for OMAP3430 with CPCAP
SOUND_CPCAP_OMAP -> SND_OMAP_SOC ( = ALSA)
Device Drivers/USB support
CPCAP USB Transceiver Driver
CPCAP_USB
Device Drivers/USB support/USB Gadget Support
USB Gadget Drivers (MOTO Android Gadget)
USB_MOT_ANDROID
Device Drivers/Real Time Clock
CPCAP RTC
RTC_DRV_CPCAP
So... anyone here who is willing and able to take on one of these drivers/features? Within a reasonable time frame (weeks, not months)? Anyone who knows of existing ports for these missing bits?
Why wait for Quarx or any of the other already overworked developers to do all the work? Just join hands, sing Kumbayah and get porting - but post here which driver/feature you want to work on to avoid needless duplication of effort.
I'll wait a few days for others to take the fun projects, then I'll start on those which are left.
it's a great idea，but it seems so difficult for us to complete such a huge program.
one-piggy said:
it's a great idea，but it seems so difficult for us to complete such a huge program.
Click to expand...
Click to collapse
It is not as big as you make it out to be. The drivers already exist, they just need to be ported. The differences between 2.6.32 and 3.0.X (the first target) are not that big, so the changes needed should be limited. The number of drivers which need to be ported is also rather limited, especially given the potential number of volunteers. The difficulty level for porting these drivers is generally not that high, there are plenty of examples to be found for similar hardware which has already been ported.
The list contains 17 items. Several of them need to be checked for compatibility only (USE_OF, MACH_OMAP_MAPPHONE, VIDEO_OMAP2_VOUT, SND_OMAP_SOC, USB_MOT_ANDROID). This leaves 12 items. The CPCAP-related drivers might already be available (need to check later Motorola code). The procfs-related stuff should be easy to implement (PROC_DEVICETREE, OMAP3_EXPORT_DIE_ID) and might already be available under different names.
For OMAP-specific stuff (CONFIG_MPU_BRIDGE etc) there is linux-omap, more specifically several mailing lists frequented by people who have experience with porting to the linux-omap tree.
Porting the sensor drivers (SENSORS_AKM8973_AKMD, SENSORS_KXTF9) should be straightforward. The camera/video-related drivers might be more complicated as they'll need to be adapted to use ION. Then again, maybe they have already been ported? If not, there should be plenty of examples for similar hardware to base a port on.
I'm not saying porting these drivers/features will be effortless. Nor does it have to be. Porting ICS and later JB to Defy(+) wasn't effortless either yet still someone did it. By dividing the tasks needed to port these drivers/features the amount of effort needed will be limited. As said, I assume that there are several people frequenting this (part of this) site who should be capable of partaking in this effort.
YetAnotherForumUser said:
The differences between 2.6.32 and 3.0.X (the first target) are not that big
Click to expand...
Click to collapse
I second that. There's a huge misconception that 3.0.x a major change. But it wasn't. They just bumped up the version number.
Sent from my MB526 using xda premium
simmilar drivers in this repository
https://github.com/redyk/omap3630-3.0.8
Lg Optimus Black(sniper) 3.0.8 sources..
I found smmilar drivers but i don't know these drivers same them
quarx is already very far with the kernel. The actual problem is that he has no idea how to get display working.
If anyone can help with this that would be great.
junesoung said:
https://github.com/redyk/omap3630-3.0.8
Lg Optimus Black(sniper) 3.0.8 sources..
I found smmilar drivers but i don't know these drivers same them
Click to expand...
Click to collapse
LG Optimus Black 'sniper' kernel, 3.0.57:
https://github.com/TheMeier/lge-kernel-sniper-linux-stable
Has source for the following drivers, probably more - I just cloned the repository.
AKM8973 Magnetometer
KXTF9 Accelerometer
WL127X_RFKILL
m11kkaa said:
quarx is already very far with the kernel. The actual problem is that he has no idea how to get display working.
If anyone can help with this that would be great.
Click to expand...
Click to collapse
don't see a problem if someone wants to make a separate attempt. i think community effort has better chance in getting latest kernel up and running.
YetAnotherForumUser said:
LG Optimus Black 'sniper' kernel, 3.0.57:
https://github.com/TheMeier/lge-kernel-sniper-linux-stable
Has source for the following drivers, probably more - I just cloned the repository.
AKM8973 Magnetometer
KXTF9 Accelerometer
WL127X_RFKILL
Click to expand...
Click to collapse
Sounds good
GalaxySL use same cpu(omap3630)
It has 3.0 kernel too
You can find more drivers
Sent from my MB525 using xda app-developers app
Which is the base you intend to use as a starting point, test / compile against?
https://github.com/Quarx2k/jordan-kernel/tree/3.0.8-defy_display
This one?
May be this would help http://forum.xda-developers.com/showthread.php?p=33801839
http://forum.xda-developers.com/showthread.php?p=33710566
Sent from my MB526 using xda app-developers app
Comparison between Defy and LG Optimus Black kernel configuration
m11kkaa said:
quarx is already very far with the kernel. The actual problem is that he has no idea how to get display working.
If anyone can help with this that would be great.
Click to expand...
Click to collapse
The display subsystem in the LG Optimus Black seems to resemble that in the Defy(+), so for that purpose those sources can be useful.
For comparison purposes I attached a side-by-side diff of the default Defy(+) kernel .config and that for the LG Optimus Black.
domokos said:
Which is the base you intend to use as a starting point, test / compile against?
https://github.com/Quarx2k/jordan-kernel/tree/3.0.8-defy_display
This one?
Click to expand...
Click to collapse
That is the base I used to find missing drivers/features. For porting purposes it does not matter that much which base is used, as long as it is as close to baseline as possible. The linux-omap tree would be a good starting point as that is a) synchronized with baseline and b) where work on OMAP-related stuff takes place. As the purpose of the port is to get Android to run, the most recent Android-specific branch would be a good target. Of course there is much to say for taking the path of least resistance so if one of those other trees around here (Quarx 3.0.8-defy_display, LG, Samsung, a mashup of all three, etc) can get us where we want to be in less time that would be an option as well.
http://forum.xda-developers.com/showthread.php?t=1546102
maybe this will be helpfull?!
YetAnotherForumUser said:
Even though JB is more or less feature-complete on Defy(+) there are still a few nits which will be hard to squash without having access to features which are only available in later kernels (eg. the ION memory allocator). Given that this board is frequented by people who (theoretically at least) should be able to give a hand in porting the required drivers/features to get a 3.X kernel up and running on Defy(+) I started making an overview of those missing bits. It should only take a relatively small group of willing volunteers, each responsible for a driver or feature, to get those bits ported.
From a quick glance at the configuration options used with the currently used 2nd-boot kernel I come to the following list of drivers/features which will need to be ported to 3.X. Some of these might already be available under different names in the kernel. Others might have been ported but are simply not part of the kernel tree I used to make this comparison (Quarx2k/jordan-kernel; branch 3.0.8-defy_display). Yet others might not be needed in the newer kernel because their functions are taken over by other drivers/features.
This is not a complete list of features needed to get a kernel running on the Defy(+) (see mapphone_defconfig in branch 2.6.32 for what is needed).
In the following list I marked potential replacements in bold type, usually followed by a question mark (?) to indicate I'm not sure they are fully compatible replacements for the 2.6.X drivers/features. The drivers/features are listed in 2.6.X menuconfig order using Kconfig names and symbols.
Drivers needed for Jordan w/kernel 3.x
Top level
Support for open firmware device tree (ARM port)
ARM_OF -> USE_OF ?
Support for device tree in /proc
PROC_DEVICETREE
DSP Bridge driver
MPU_BRIDGE
System Type
Motorola Android Platform Phone
MACH_MAPPHONE -> MACH_OMAP_MAPPHONE ? complete?
Motorola Android Platform phone 2nd-boot kernel modifications
MAPPHONE_2NDBOOT
Export DIE ID code under /proc/socinfo
OMAP3_EXPORT_DIE_ID
Device Drivers/Misc devices
AKM8973 Magnetometer
SENSORS_AKM8973_AKMD
KXTF9 Accelerometer
SENSORS_KXTF9
Bluetooth power control driver for TI wl127x
WL127X_RFKILL
Motorola OMAP Device Type Driver
OMAP_DEV_TYPE_DRV
Motorola Modem PM Driver
MODEM_PM_DRIVER
Motorola netmux driver
NETMUX_DRIVER
Motorola netmux link driver
NETMUX_LINKDRIVER
Motorola Camera Driver
CAMERA_MISC
Device Drivers/Multimedia support/Video capture adapters
HP OMAP3 Imaging/3A driver
VIDEO_OMAP3_HP3A
Video out driver
VIDEO_OMAP_VIDEOOUT -> VIDEO_OMAP2_VOUT ?
Device Drivers/Sound card support/Open Sound System (DEPRECATED)
Audio driver for OMAP3430 with CPCAP
SOUND_CPCAP_OMAP -> SND_OMAP_SOC ( = ALSA)
Device Drivers/USB support
CPCAP USB Transceiver Driver
CPCAP_USB
Device Drivers/USB support/USB Gadget Support
USB Gadget Drivers (MOTO Android Gadget)
USB_MOT_ANDROID
Device Drivers/Real Time Clock
CPCAP RTC
RTC_DRV_CPCAP
So... anyone here who is willing and able to take on one of these drivers/features? Within a reasonable time frame (weeks, not months)? Anyone who knows of existing ports for these missing bits?
Why wait for Quarx or any of the other already overworked developers to do all the work? Just join hands, sing Kumbayah and get porting - but post here which driver/feature you want to work on to avoid needless duplication of effort.
I'll wait a few days for others to take the fun projects, then I'll start on those which are left.
Click to expand...
Click to collapse
Maybe this link can be useful: http://blackscratches.blogspot.ro/2012/04/how-to-build-android-kernel-308-for-ti.html it seems very explicit about porting kernel 3.0.8 on omap 3630 including drivers
Fight4Music said:
http://forum.xda-developers.com/showthread.php?t=1546102
maybe this will be helpfull?!
Click to expand...
Click to collapse
It might. For more stuff like that have a look at the Linux OMAP Kernel Project where you'll find more about the various OMAP-related development efforts. The above link points to one of the many branches of this tree:
http://git.omapzoom.org/?p=kernel/omap.git;a=summary
In the p-android-omap-3.4 branch there is a camera driver for the "Aptina MT9P031 Camera". The Defy+ (and Defy/Bayer) contain a camera based on the MT9P012. It stands to reason that there is a family relationship between all these mt9xyyy sensor drivers.
Working 3.0 kernel for Samsung Galaxy SL
The Samsung Galaxy SL shares quite a bit of hardware with the Defy(+). There now is a working (if not feature-complete) 3.0 kernel for this device.
https://github.com/dhiru1602/android_kernel_samsung_latona
Attached to this message is a side-by-side diff between the Defy default config and that for the latona (S G SL) as well as a side-by-side diff between the Optimus Black default config and that for the latona.
http://forum.xda-developers.com/showthread.php?t=1546102
Sent from my MB525 using xda app-developers app
junesoung said:
http://forum.xda-developers.com/showthread.php?t=1546102
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
See #14...
YetAnotherForumUser said:
See #14...
Click to expand...
Click to collapse
Oh, sorry;
Sent from my MB525 using xda app-developers app
TheXSample-SXELROM v3.5 for JXD S7300B (Firmware & Tincore Driver Update 18/05/2013)
Use of this article
It allows you to use this review, either by copying or referenciándola link to anyone who wants it, with the only condition that remains the author and a link to the original source of this review, which is cited in the following section .
Source and update the information in this article
The original article (in Spanish) is in my blog .
For updates on this article, I suggest visiting one of the links above.
_____________________________________________________________________
UPDATES
18/05/2013: THEXSAMPLE-SXELROM_3.5PATCH.rar
Mirror Mega
Change log
Firmware
- Kernel compiled from sources 3.0.50
- Improvements on system stability (must improve some hangs/freeze of devices)
- New frequency added. There is no need of SetCPU profile. Is recommended to clear application data and start again SetCPU, and choice "Autodetect frequencies"
- Governors smartass2, intelldemand, lagfree and lionheart was deleted, and replaced by the new ondemand, interactive and interactive2, that works better on the device.
- Potential Fix for Wakeup bug. Emulators now must run fine without issues about the screen rate, after wake up.
- Little improvements on 3D performance
- Added new option for reboot, from the power menu.
- JXD Mapping tool deleted. now will not appear in any way the mapping tool interface (Shift key will not open it)
Tincore Driver Update
- Fixed Sticks Dead Zones
- Sticks are Joystick by default from now (you must set manually if you need right stick as IJKL keys)
- Fixed initialization routine.
Installation:
- Extract the rar file. There are 3 files.
- Put on your miroSD card
- Boot the device in recovery menu
- Select "install zip from EXT"
- Browse and select the file you want to flash (each file flash different kernel speed. select the speed you want to use. (Recommended: 1200MHz)
- Reboot the system
_____________________________________________________________________
About this overview
This article is a summary, and contains only the most relevant features.
To read the full article, look at the link above.
Features
Here is a short list of changes included in this version of firmware.
Later in this article, there is a section with extended information about these changes.
Firmware
Include support for USB Bluetooth dongles
This includes new governors set for the console hardware
Tincore Driver
Calibration ajusatada for DPAD
Improvements and optimizations in the driver code, to get even less lag.
Tincore KeyMapper
Support for languages.
Minor improvements in UI tool
DEBUG Option
Creating online guide tool
Note on Bluetooth Support
Not all Bluetooth USB dongles behave the same way, and the clasificaré in 3 groups:
[*] Only some have 100% support, and able to connect, disconnect and work seamlessly with the device.
[*] Others may only work if you are connected to the console from the start of it, and if disconnected, they will not start until you restart the console.
[*] And others, very few, may not be able to work with the console.
That said, emphasizing that most dongles that we used in the tests correspond to Group 2 of the above list, and only one has been in group 1, but still the connectivity and operation we tested is suitable and practical, if we have the console plugged into a TV.
What's more, the videos I uploaded to show this feature, corresponding to a dongle in group 2, and as you can see works seamlessly with multiple devices.
http://www.youtube.com/watch?v=3CW4sjLxcjY
The video above shows the work in progress of this feature.
On connectivity Sixaxis
http://www.youtube.com/watch?v=uPhBS4FqUH4
(Using a SIXAXIS with the console)
Overall, there have been problems with device connectivity, but if identified and strange behavior is that when connecting Sixaxis controls, after a few seconds in some cases these are switched off (or when you connect a second controller is off the first), but not always the case and simply reconnect the tool again.
According to the evidence, it may be because, for some reason, the program does not work well when the controls are low on battery (below 50%).
http://www.youtube.com/watch?v=Men4LPPYFOE
(Console working with 2 sixaxis connected simultaneously)
Version Recustom
It has generated a TheXSample-SXELROM v3.0 release Recustom with the same characteristics as the original rom, plus some extra programs related withthe bluetooth.
Download Links
TheXSample - SXELROM v1.0
TheXSample-SXELROM Firmware v3.0 [Mega Mirror ]
For more links, see the original article of this release.
Credits:
As in previous updates, here is the work of many people, although it seems small upgrade, I can say it's quite achieving the advancement of Bluetooth and achievers who deserve all the thanks, and among which I will highlight a Skelton (great manager of the idea), Christian Troy, Lomax, Tincore (which never tires of implementing improvements) and myself, that force me to go out in the credits XD, plus I can leave out now .
We also wanted to give a thank you to the store Willgoo, that has been very helpful to give us the necessary support to add the option of accelerometer in the mapping tool (released in a previous patch), and now we have the "Wiimote style "to play some retro-gaming (it's great to play Mario Kart 64, tilting the console like a Wii steering wheel): D
The special thanks of this firmware is for the groups "The Mox", "Les Miserables", "Marilyn Manson" and Daft Punk (among others) for that because we had a lot of energy injected encouragement and strength to the long nights of testing that has taken this firmware.
Zalu2!
Deen0X
Thanks so much for your work on this! Super smooth and everything just works.
Also, thank you for posting this on XDA. Haven't seen too many S7300B posts here, so this is great.
jm77 said:
Thanks so much for your work on this! Super smooth and everything just works.
Also, thank you for posting this on XDA. Haven't seen too many S7300B posts here, so this is great.
Click to expand...
Click to collapse
nice to see people interested on this device here in XDA.
first post updated!
Deen0X said:
first post updated!
Click to expand...
Click to collapse
Thanks for posting this on XDA!
Looking forward to reporting back. Thanks for your hard work.
Hello, I was struggling with my a13 based tablet. I found almost a combination of working TS, wifi, camera and gsensor drivers for it.
All drivers I downloaded from thread (none of them have all working modules, most of them don't work at all for me) made by Inside4droid (big thanks for his great work because I flashed my rom without any problems to faaastjb 2.5 providing android 4.2.2 , before that none rom's were working for me) - http://forum.xda-developers.com/showthread.php?t=2447819
When I install these drivers: gt828_ts.ko+mxc622x.ko from "Single TS module" driver list from that faastjb topic, then my touchscreen works nice and wifi works smoothly. But there is no gsensor. Then I try - Ainol Novo7 Legend - from drivers listed as "Special TS module" and my touchscreen works also with multitouch, but I also get a working gsensor (it's messed up with rotation not working like it should, it's not calibrated right, but at least it works), the biggest problem here is that wifi is not working so good, it connects but it has trouble downloading anything from google play or even accessing a webpage, there is also a good camera driver which works fine. So my question is, how I can create my own driver pack like these provided with auto installation but with wifi drivers from the first pack I mentioned and touchscreen, gsensor and camera driver from the second one? (and how I can modify/calibrate gsensor to work properly? Is there any good app for such calibration?). I also don't know if these packs contain some graphic drivers, because when using the second one after rotating screen it's a bit "cut" in the horizontal position (for example you can't see space on virtual keyboard). If it's any help I found on techme forum some specs about my tablet version (it's sold as binatone appstar):
Release Codename REL
API level 15
CPU ABI Armeabi-V7a
Manufacturer Keenhigh
Bootloader Unknown
CPU ABI2 Armeabi
Hardware SUN5i
Board Nuclear
Display IMM76D
Host RD-SW-Server
Screen Res 800x444
Density 120dpi
Can somebody please help me with resolving problems I mentioned? Thanks in advice.
Hello community,
after many hours of research and different attempts to get ANT+ working with CM12.1 on my N9005 I want to start some kind of information exchange on XDA to bundle all previous experiences.
ANT+ is a low power bluetooth mode, which is used to connect professional sports/outdoor equipment like heart rate belts, speed or cadence sensors, powermeters and so on. BTLE (bluetooth low energy) mode is provided as an alternative, but most equipment manufacturers do no support BTLE because ANT+ is optimized for stability and durabiltiy and has some advantages over BTLE (i.e. optimized device protocols for lower energy expenditure).
There are two smartphone manufacturers out there which support ANT+ natively (depending on the built-in hardware) since some generations - Samsung and Sony. (I read about the OPO (One Plus One) got native ANT+ support in the meantime.)
The qualcomm edition of the Note 3 (N9005) uses a broadcom 4335 wifi/bluetooth chip which is capabable of ANT+. Samsung stock roms provide native ANT+ support but if you switch to a newer CM12.1 or CM13 rom (maybe because of the great performance or KNOX and other bloatware issues), you will unfortunately loose the native ANT+ support. The same goes for the S4 and S4 active too like mentioned in several threads and communities.
There were several attempts to get ANT+ working on CM12.1. One of te most important attempts was made by @christer12 which seemed to be successful:
http://review.cyanogenmod.org/#/c/110547/
http://review.cyanogenmod.org/#/c/110396/
Some days later he stated on his twitter page "ANT+ on hlte don't work properly, because ANT+ in cm-12.1 is not properly integrated for bcm4335.. =(".
ANT-wireless provides a kind of "reference architecture" for the inclusion of ANT+ in Android roms:
https://github.com/ant-wireless/ANT_in_Android
But when comparing this approach with the one used in Samsung stock roms there are some differences. Samsung does not use a native library called "libantradio.so". Their AntHALService (interface between vendor hardware drivers and common ANT+ software) is built on the broadcom SDK which uses the class package com.broadcom.bt (with it's own radio manager implementation). This package is integrated in the Samsung stock rom /system/framework folder as java archive (JAR).
So my intention was to switch to the samsung aproach and use the broadcom libraries (in combination with Samsung vendor libs) for a "custom" AntHalService. That worked out ok, but at the moment I'm experiencing some difficulties in testing. The virtual machine of my android studio does not support bluetooth out of the box and my device (CM12.1) show a runtime reference error (NoClassDefFoundError) while accessing the broadcom classes. All classes are in the APK/classpath but CM12.1 seems to behave differently.
As I'm interested in other experiences and new ideas I just wanted to start this thread.
Thanks in advance and regards,
B
Reserved
I found this very interesting thread of xda-user @iRant which shows neccesary changes in the CM mainline code and seems to be the base for the ANT+ support in CM11:
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
https://android-review.googlesource.com/#/q/owner:"James+Bootsma"+status:open
This solutions implements - amongst others - some vendor specific functions/commands (*VS) in the Bluetooth stack which were missing in the mainline code.
https://play.google.com/store/apps/details?id=com.z2software.antplus
Wasn't it working ?
newintage said:
https://play.google.com/store/apps/details?id=com.z2software.antplus
Wasn't it working ?
Click to expand...
Click to collapse
Sorry for the late reply. I messed up my phones CSC and had to reflash my phone several times. ?
Thanks for the link. ? I found some posts concerning ANT+ enabler but they did contain inconsistent results. So I did a little research and recognized that the last update from 2015/12/20 seems to fix some CM problems. Reading that I bought the app to try it out myself.
Results:
In general it seems to be working, but not really reliable yet. I got some "adapter not detected" messages and had to reboot my phone two times to reactivate bluetooth again. I will send an e-mail to the developer to analyze the problems.
As CM is open source a "commit solution" should be more "integrated" but I could live with a workaround if it's really reliable.
I am very interested in this as I was using my tablet (Samsung tab pro 10.1) to connect to my Garmin via ANT+. Since using a CM based custom ROM there is no longer any support. I was using a custom ROM on my Note 3 that was based upon a stock samsung one that included support for ANT+. If it can be included there then why not on CM ROMS?
ANT+ enabler used to work for CM 12.1 , but then it stopped working , i just tried it again and not working. if you flash Teamsek V17 , it starts working, but anything after 17.2 and things stop working. I have NOT tried CM13. (I assume the result is the same)
Hello everybody,
I have developed a working, native booting Ubuntu MATE 18.04 system for the T-Mobile LG V10. This device has not received enough attention in the development community, so I decided I'd go all out and get a fully open source Linux distribution to boot and run on this underestimated device. I have gotten most of the basic features working, except for Wi-Fi and audio output. I think this could be a great foundation for developing a fully functional GNU/Linux based operating system that can harness the true functionality and power the LG V10 offers.
As of now, this is what works:
- Display (fbdev , no hardware acceleration)
- Touch (Xorg natively supports it)
- Modem/ADSP/Venus subsystems brought up
- Microphones (using Alsa usecase files from LG G4)
- USB OTG ethernet
- rt2800usb wireless driver backported (connect with NetworkManager)
- Stable systemd support
- Udev detects charging/battery percentage
To do:
- Enable hardware acceleration with freedreno DRM/KMS
- WiFi working
- Get HDMI slimport output working with Xorg and freedreno
- Get audio output working
- Offset the second screen in Xorg
- Make ADSP sensors accessible to userspace
- Screen rotation
- Camera blob bringup with libhybris
- Mainline kernel support
For more information, read the README.md on my GitHub repository
If you want to contribute, or have a look at what I have done, here are the links to my GitHub repositories, and the rootfs:
Boot Images: github.com/doitaljosh/native-ubuntu-mate-pplus
Ubuntu MATE 18.04 rootfs archive: drive.google.com/open?id=1AjhBs_9HLO0KC3bFpka2ewpuJTmigimK
Kernel Source: github.com/doitaljosh/android_kernel_lge_msm8992
hey what does this do. that stock kernel don't do?
If you want an extra tester, I have another v10 laying around that could be used for stuff.
great effort. thanks for your time and contribution. i am waiting for my v10 to arrive from ebay. will test.
I'm getting an issue where when the tar is extracting it'll stop and say it was killed. I know that I didn't kill it, as I left it alone while it was extracting. Or is it just it's say of showing that it's done?