aptX is an advanced bluetooth codec.
The flashable zip should work on all devices supporting bt >=4.0, but since I only tested this on my chagallwifi, I'm posting in this forum.
I verified the mod is working on a chagallwifi with Teufel Move BT (c). If I use a source coded lossless (I used a flac file) the difference is hearable with the Move BT.
The zip just copies over the three libaptX* files to /system/vendor/lib and sets their permissoins to 644.
Just reboot after flashing and AptX is working. To get AptXHD working, add this line to /system/build.prop:
Code:
persist.bt.enableAptXHD=true
Finaly: Reboot.
many thanks, if this works it is brilliant :fingers-crossed::good:
I guess it is only working on LineageOS and LOS based ROMs?
If yes it should also work on other devices running LOS, such as my galaxy S5?
regards
j1gga84 said:
many thanks, if this works it is brilliant :fingers-crossed::good:
I guess it is only working on LineageOS and LOS based ROMs?
If yes it should also work on other devices running LOS, such as my galaxy S5?
regards
Click to expand...
Click to collapse
nvertigo67 said:
The flashable zip should work on all devices supporting bt >=4.0
Click to expand...
Click to collapse
Since it's "just another codec" it should work on ALL devices with sufficient bt support - that's my technical guess. I terms of copyright law it's only allowed to use this on aptx licenced devices. Check the box of your device for the AptX logo or search here for your device. But since the zip does not check for devices...
BTW: lineageos for all exynos5420 based devices will have aptx support build in from the next realese on, thanx to @DarkExistence: https://forum.xda-developers.com/showpost.php?p=75200352&postcount=1201
Is this zip obsolete if the ROM you use already has APTX support on board?
I was asking in the Samsung galaxy S5 LineageOS thread and there it was implemented about one year ago but I could not find the line you mentioned in my build.prop
Regards
Sent from my SM-G900F with Tapatalk
j1gga84 said:
Is this zip obsolete if the ROM you use already has APTX support on board?
I was asking in the Samsung galaxy S5 LineageOS thread and there it was implemented about one year ago but I could not find the line you mentioned in my build.prop
Regards
Sent from my SM-G900F with Tapatalk
Click to expand...
Click to collapse
Sorry, I only have detailed knowledge of devices I have my hands on. In this case chagallwifi (sm-t800). If you use @DarkExistence official lineage builds or mine (see sig) you have NOT to do anything, because the zip is included in the blobs and the buildprop is edited.
Sammy is different from the other childrens - especially, but not limited - on audio. The audio implementation on stock sammy roms is completely different from aosp/los. When I first brought up cm11 @Barracuda77777 and me had a hard time on getting the xml files for audio correctly migrated. Later @Schischu did a great job on making a script for this task.
If you look at a stock t800 rom, you will not find any files named libaptX*so though it supports aptx.
Keeping that in mind, the s5 los builds may support aptx, though neither the build.prop line, nor the libs named libaptX*so are present. Before flashing this on s5, just check, if it's already supported ("logcat -d|grep -i -e aptx -e audio" - you need a posix complient grep for multi expresaions! Included in my builds, or run two timesmwith only one expression.).
Last but not least: if you just flash this zip without editing build.prop you will have full aptX support. The build.prop edit is to enable aptXHD. So the missing build.prop edit is no indicator for aptX support.
For completeness this is @Schischu's script.
I hope this is clearifying some points.
Did not found any logo for aptx connection!! Used on tfz air king with T805
Who cares about license... i don't. just do whatever you want if it's pleasant to you and ok 4 us
toufiq47 said:
Did not found any logo for aptx connection!! Used on tfz air king with T805
Click to expand...
Click to collapse
there isn´t.
Check the bluetooth settings for the currently connected device, it may show "HD audio: Qualcomm aptx (-HD)"
But as far as i remember, this zip in here is only designed for android 7.
Android 7 doesn´t fully support aptx and doesn´t show any info about it.
Android 8 and up does natively support aptx, aptx-HD and i think even Ldac.
So as soon as compatible binarys were found, it can use it (and shows if the connected device is using the codec).
If you´re looking for aptx for a more recent android version, take a look at my signature and you may find something
Related
I'm wondering, would it be technically possible (apart from being illegal) copying apt-X codec to another Android device with A2DP support?
I've already posted this question on Optimus 4X Q&A forum, so here's details.
magickone said:
I'm wondering, would it be technically possible (apart from being illegal) copying apt-X codec to another Android device with A2DP support?
I've already posted this question on Optimus 4X Q&A forum, so here's details.
Click to expand...
Click to collapse
Hi
I'm also interested in keeping the Apt-X support on my GS3 while moving away from the stock rom, but the rom I use, AOKP, will not implement a proprietary codec.
Could it be as simple as extracting the libbt-aptx-4.0.4.so from /system/lib of the default rom and copy it into the /system/lib of the desired rom with the same permissions?
Thanks
Beng
Background:
Ant+ and Health/Sport accessories are not very widespread among smartphone users, but it was one of the major reasons a which I moved from the Nexus 4 to Galaxy S4.
While S4 on 4.3 works great with my Garmin Heart Rate Monitor(HRM), I'm not satisfied with Touchwiz and Knox.
My S4 feels laggy, slow and I want to use stock android, or even any of those KitKat releases.
Many Xperia devices have Ant+ support, and it seems that they manage to cook it into custom roms successfuly.
Target:
Assemble a flashable zip which would allow anyone with an S4 already flashed to 4.3 to use the Ant+ receiver.
Research:
I've spent some time embeddint the Ant+ files (com.dsi.ant.antradio_library.jar and .xml, and the AntHalService.apl) on MakTail's 4.3 GE but ran into an issue that blocked further investigation:
The AntHalService tries to enable bluetooth, can't find the method and reboots the device.
The version is 3.0.0 which is supplied on Stock ROM, and there is already a 3.1.1 available from Ant Alliance which removes the requirement for enabling bluetooth.
I got the source code and compiled the apk, but I can't run it as a System App, so I got stuck. Spent some time trying to workaround it, but no success.
I guess that even when I get hold of a working 3.1.1, there will be new issues, and I'm a complete newbie on ROM cooking.
So I would like help from others, maybe suggesting next steps or getting hands on with me on this project.
XDA:DevDB Information
Ant+ Support for Non-Stock ROMs, a Tool/Utility for the Samsung Galaxy S 4
Contributors
AdrienC
Version Information
Status: Testing
Created 2013-11-25
Last Updated 2013-11-25
Attached is a file with the system files required for ant which I could find after some investigation.
Links:
Here is the source code for the AntHalService.apk which I couldn't run as System service.
https://github.com/ant-wireless/Android_ANTHALService
And the slooow forum:
http://www.thisisant.com/forum/viewforum/30/
to run as system app if you are rooted just manually copy apk to /system/apk
lgkahn said:
to run as system app if you are rooted just manually copy apk to /system/apk
Click to expand...
Click to collapse
won't work due to the signature I guess. Even when I signed with debug keys didn't work. Maybe due to SELinux?
Code:
I/PackageManager( 707): /system/app/AntHalService.apk changed; collecting certs
W/PackageManager( 707): Signature mismatch for shared user : SharedUserSetting{42a56d98 android.uid.system/1000}
W/PackageManager( 707): SELinuxMMAC.assignSeinfoValue
E/PackageManager( 707): Package com.dsi.ant.server has no signatures that match those in shared user android.uid.system; ignoring!
I am going to flash 4.4 GE edition by Jamal http://forum.xda-developers.com/showthread.php?t=2544474 and will try to survive with my Suunto USB Ant+ stick on OTG to allow me to spend more time trying to make this work.
Will update with any progress/issues.
Well, I send a cry for help to @broodplank1337 and got his awesome reply showing availability and this was my reply, which I decided to share as while I waited for help I made some pretty good advance!
While I was waiting for your reply I made some progress....
I replaced the classes.dex from my compiled apk(from java source) into the samsung apk and that was enough to bypass the cert check ( I was pretty sure I tried that before, but must've done something wrong).
I found out the source code is referencing a kernel module that doesn't exist for Galaxy S4, so I ran Dex2Jar and Java Decompiler and I'm now analysing the source code and I think that it somehow passes the instructions directly to the chip.
I'm thinking about trying to change the bluetooth methods it uses to the ones available on AOSP, which is why the 3.0.0 was failing initially.
It'll probably still take some work, but it might be feasible.
The main issue is that I'm new to android coding, and not a java expert, but used to be a programmer and I'm finding my way (and some joy) hacking thru all this code.
Click to expand...
Click to collapse
I'm attaching the source code for AntHalService.apk from Samsung stock roms (version 3.0.0).
I guess I'll have to work over it, as the 3.1.1 I got from AntWireless references an antradioservice.so which Sammy don't have and causes a bootloop.
I am now comparing the smali code between the 3.0.0 and the 3.1.1 to see if I can do an easy patch, but it's not looking very likely...
Lets see how this goes.
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Guys, an update. I kinda gave up for a while. ANT Forums are helpless, and I got kinda tired of looking around. I'll need to have some free time and motivation to dissect the code and try to make it work on the AOSP bluetooth stack.
A good workaround I found is to have a dual boot solution, so you can switch to the Touchwiz ROM for a training.
karimero said:
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Click to expand...
Click to collapse
blue6800user said:
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Click to expand...
Click to collapse
blue6800user said:
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Click to expand...
Click to collapse
Thanks, hope to eventually come with good news, got kinda sad to hit a wall. But meanwhile, use your favourite rom and dual boot a Touchwiz ROM.
I'm now back to the last released version of 4.3 for Brasil to soon extract the libs and apk's to build a slim TW ROM just for dualbooting.
It'll be an easier workaround. For those with 32GB S4's don't even need to go down this path, just dual boot and be happy!
Thanks for working on this, got the S4 the other day coming from a Bionic that was had ANT+ chipset, but they never turned it on. I too would love a CM 11 with ANT+ support. I will happen, eventually.
ant+ apps on the app store
Hi I'm running 4.4.2 Echoerom on my S4 and just discovered that I'm lacking ANT support despite installing the ant service and apps from the store. Did you try these apps, were you able to make any progress?
Any updates on this ?
I'd like to use ANT+ on my s4 running AOSB.
Any updates for ant+ support in CM11?
The solution of dual boot seems very messy for only that
any news with that?
I'm super late with this, but if anyone is still looking at building ANT+ in to custom ROMs, I have had success building from the ANT Wireless source: check the ANT hardware thread
I DO NOT OWN THE ROM.
The developer of this rom is kumajaya on MIUI forum and thanks to him for his work.
MISSION:
Embarrass Xiaomi because refuse to release Redmi 2 kernel source
BUG:
Before you install this ROM, check your device magnetic sensor. Currently YAS537 not supported!
Still under development, built from sources, no hidden sources, not a binary dirty hack ROM
The following will not be supported in this thread:
- Custom Kernels
- Mods, including CPU management mod or any strawberry mod
- Modified system files
- Xposed
If you reuse even a part of my work here, a proper credit is a must, keep it open source also a must
Download:
Cyanogen and TWRP recovery: https://goo.gl/cDJQXI
CyanogenMod 12.1 ROM: https://goo.gl/zhGZjQ and https://goo.gl/5sqZGp
For better Google experience, install TK GApps Nano: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Don't create any mirror without a permission!
Cyanogen recovery above just like a standard AOSP recovery without a lot of features compared to TWRP, but you can temporary boot it using "fastboot boot cyanogen-recovery-wt88047.img" command to check if CyanogenMod 12.1 ROM possibly working on your device variant.
Don't even try this ROM on Redmi 2A variant!
Sources:
CyanogenMod source tree: [url]https://github.com/CyanogenMod[/URL]
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech
Changelog:
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047/commits/cm-12.1
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916/commits/cm-12.1-amss-1.0.2-wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech/commits/cm-12.1
Credits:
Google, AOSP, Cyanogen, CyanogenMod community, Qualcomm's CodeAurora @balika011, @zwliew, @Flour_Mo
Introducing me: XDA Recognized Developer, CyanogenMod contributor
My wife, she always believed I could restore back her device in minutes
Some tools: Kate (text editor), Kompare (diff viewer and generator), qgit (git GUI)
Smarfren Indonesia for Andromax Q source code
Micromax India for Yuphoria and Yureka source code
Current status:
Boot to Android, this is my first ROM that really boot on the first try
Touchscreen works, all hardware button mapped correctly
No screen flicker, fluid graphics
Voice call and SMS works, data over WiFi and GSM works (radio config in build.prop fix previous GSM issue)
Vibration and screen rotation works
All sensors seem works including GPS and compass but light sensor still need a fine tuning
Both camera working, the author found a super clean solution
No boot animation (fixed, kernel issue) Disable splash screen break Android boot animation but if I enable it, Cyanogen recovery covered by Tux the penguin logo in the center. The workaround solution, move Tux to the top right of the screen
No sound (fixed, kernel and user space issue) This also fix slow boot because of logcat flooding. BUG: Speaker output ignore headset jack insertion, sound out from both speaker and headset
Bluetooth file transfer fail (~42MB zip, failed at 17%) WiFi file transfer way faster
FM radio works
WiFi hotspot works
YouTube and local video 720p works
LED driver working great, multi color and blink
Remember, no contribution from Xiaomi yet. That's the reason why I try to avoid "Xiaomi" string in my source as possible but Wingtech.
I use CyanogenMod resources as much as possible, including common MSM8916 device tree and kernel. Maintain device source tree and leave common part to CyanogenMod community. I'll strictly follow CyanogenMod coding style and source structure. This is about source code quality.
AGAIN, I DO NOT OWN THE ROM.
Will try it soon. And I hope Xiaomi will release the kernel like Redmi 1s.
kumajaya and zwliew are the most stable CM12.1 roms for our phone. I hope they reach 100% full working version in near future.
Thank you both!
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
How about some screenshots?
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
crzlloid said:
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
Click to expand...
Click to collapse
There is a link in my post about the changelog and the YAS537 is still not yet supported.
zwliew said:
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Sorry, but I have already talk to kumajaya about it. Then he ask me to help him on requesting an official sub-forum for our device. Anyways, if anyone here oppose me about posting this thread, then maybe I should delete this.
wow, using this in 2020, 5 years later.
Announcing Sailfish for the Sony Xperia Z3 Compact!
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone.
Special thanks to:
rss351 and locusf for the collaborative effort in porting SailfishOS to the Z3 compact
Everyone from the SailfishOS team/community, sledges and mal- in particular.
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Known issues:
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Sensors dont work (auto-adjust brightness, etcetera)
The Jolla account/store functionality is not enabled. This is being worked on by Jolla. In the meantime: use openrepo's warehouse (see bottom of this post)
What works:
Booting, basic usage of the OS itself (browsing, etc)
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi (both 2,4 and 5 GHz)
Power management seems to work fine (not tested much though)
Looking around and getting a feel for SailfishOS
Using your phone to develop and debug SailfishOS apps.
Installation guide/checklist:
Insert default warranty void message here. Your warranty is now void
Make a backup (just to be sure)
Depending on what you need from your phone, this may not be a rom suitable for daily driving with. But installation is non-destructive to your existing rom, so if you're curious, give SailfishOS a try
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an official Sailfish OS build, and the Xperia Z3c is not a Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, this thread is perfectly fine for that.
BEWARE: this image is NOT optimized for security. The phone boots in development mode by default. There is a root shell on telnet port 2323. This is not secure and will give anyone who wants it remote access to your phone. When the port matures this will be fixed.
The Sailfish OS image does not provide recovery, and since the Xperia Z3c does not have a recovery partition, you need a bootimage with recovery on it to flash cm/stock/sailfishos upgrade. I highly recommend using Nut's Xperia files for this. Use the boot.img from your Cyanogenmod installation.
The Sailfish OS image is based on a recent version of Cyanogenmod 12.1, so update your Cyanogenmod installation while you are at it. Use cm-12.1-20160523-NIGHTLY-z3c.zip if you encounter issues with other versions. Using another rom is not guaranteed to work, even if this rom is based on Cyanogenmod.
You can find the required zip in this Mega folder: https://mega.nz/#F!ucoRnDjD!WAHNWgxLQX5SK1Vdu8MRWw
Use your favorite recovery (but not CM's recovery since that checks for signatures, which this image does not have) to flash the zip.
If you want to return to Cyanogenmod, extract boot.img from your cm-12 zip and flash that with fastboot. Alternatively you can restore a previous backup. There is no need to re-flash Cyanogenmod because it was not removed by installing SailfishOS. You can remove the /data/.stowaways/sailfishos/ folder afterwards to reclaim disk space.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Contributing
If you think this is awesome, and want to help fix the issues currently open: come by in #sailfishos-porters on irc.freenode.net!
Sources
You can find all used source code (may not be up-to-date to the latest image, but all key components are there) here: https://github.com/xperiasailors/
Installing OpenRepos warehouse
OpenRepos warehouse is like what F-Droid is versus Google's Play store. An unofficial, community-driven repository of open source apps.
Go to settings->developer options and set a password. Then open a terminal or connect over ssh to your phone (ssh [email protected]_of_phone).
Download the latest version of the warehouse app from here: https://openrepos.net/content/basil/warehouse-sailfishos
When you are asked to terminate packagekit anywhere in the steps below, answer yes.
Code:
$ devel-su
# zypper rr adaptation0
# zypper in <location_of_rpm_you_downloaded>
After this Warehouse app will be in your app launcher.
Impressive work! :good:
Sent from my Sony Xperia Z3 Compact using XDA Labs
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
mrrflagg said:
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
Click to expand...
Click to collapse
Probably, yes.
SailfishOS uses libhybris for hardware communication, which in turn uses the existing Cyanogenmod installation for drivers and proprietary blobs. But hybris is compiled against a certain Cyanogenmod version, so using other roms as a base might fail.
I've updated the TS and put the exact CM version I used in there, that should work fine.
There are any news? The project is in development?
Alexander3273 said:
There are any news? The project is in development?
Click to expand...
Click to collapse
No news, I don't spend much time on this port, every now and then I fiddle around with it an evening.
I'm currently trying to get AOSP based Sailfish port because Cyanogenmod for Z3c seems unmaintained, but progress is very slow.
Thank you for the info. Do you know when a version (sailfish port) comes out?
Hello! Thanks for your work. May i know the progress ?
it would be great to see a real "european" OS coming out of the dust...
i hate the thought that any company from the other side of the atlantic are wheels in the monster of patriot act...
@maikoool Any news about new build or something?
Yes, look here:
https://nokius.net/SFOS/scorpion/PreAlpha/
But still no Cam, no BT, No Sensors and No video playback
AFAIK is the 'scorpion' the Z3 Tablet compact, so not the Z3 compact. The base images will probably be the same.
I've recently rolled a build using AOSP 5.1 from the Sony Xperia developer pages, but my Z3c has developed an issue where the top and bottom of the screen don't function, so I cannot test properly.
Aries is device name, right? What's scorpion ?
kskarthik said:
Aries is device name, right? What's scorpion ?
Click to expand...
Click to collapse
Aries = Z3 compact, Scorpion = Z3 Tablet compact
I'm waiting eagerly to see SFOS on aries Do you know anything about our device support on jolla's list ?
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
As active user of the MadCatz MOJO, I found it pitty that rom development halted, mainly because the Android-TV rom from Unjustified Dev has some limitations.
As a result I've done quite some reading on "how to create an android rom from source" in the last 4+ weeks, in the hope that I could improve the work of Unjustified Dev.
In my attempt to understanding building the android source code to create my "own" Android-TV rom, I was succesfull in creating my first CM ROM (took 2h30)
(Big thanks to the source on https://github.com/TeamRegular?utf8=%E2%9C%93&q=mojo )
changelog:
Code:
[B][U]cm-12.1-20171226-UNOFFICIAL-mojo[/U][/B]
- fixed media server crashes, audio is again functional :)
- included the Tegra note 7 - widevine L1 DRM libraries (testing required)
[B][U]CM-12.1-20171222-UNOFFICIAL-mojo[/U][/B]
- Fixed hardware identification
- added DRM libs to support for widevineDRM
[U][B]BUG [/B][/U]: No audio - mediaserver crashes :(
[U][B]cm-12.1-20171216-UNOFFICIAL-mojo[/B][/U]
- changed boot animation to google animation (I like it more then the CM one)
- changed default dpi = 240
- removed not functioning multi rom code
[STRIKE]- synced media profiles to be inline with ADT-1 and cm-13 tree[/STRIKE]
[STRIKE]- added google media_codecs_performance[/STRIKE]
- applied some cm-13 changes to sync tree.
[B][U]BUG[/U][/B]: Play store seems broken,
[U][B]cm-12.1-20171208-UNOFFICIAL-mojo[/B][/U]
- Included nvcgcserver - should fix chrome issues with streaming.
- Applied kernel patch to increase from 3.4.57 -> 3.4.59
[U][B]cm-12.1-20171203-UNOFFICIAL-mojo[/B][/U]
- The update is a minor Android build update : LMY48G -> LMY49J
- Security level set to November 2016
[URL="http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html"]http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html[/URL]
Location of the ROM:
Code:
File name : cm-12.1-20171226-UNOFFICIAL-mojo.zip
[URL="https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy"]https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy[/URL]
File name : cm-12.1-20171208-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2"]https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2[/URL]
File name : cm-12.1-20171203-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l"]https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l[/URL]
Next step:
- fix issue : https://forum.xda-developers.com/showpost.php?p=69887922&postcount=393 the post should contain enough info
- gaining more ROM development skills
- build AndroidTV-5.1 rom or CM13
Side note: I'm not as experienced as Unjustified Dev, so a "mayor" update can take a while,
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Mad Catz M.O.J.O.
Contributors
carp_be, EdoNINJA93
Source Code: https://github.com/dide0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 5.1.1_r37
Beta Release Date: 2017-12-03
Created 2017-12-04
Last Updated 2018-05-21
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Wmapa said:
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Click to expand...
Click to collapse
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
carp_be said:
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
Click to expand...
Click to collapse
Will you work on cm13? It is way better than android tv if we use toplauncher it is very tv friendly
Thank you so much, OT!
Yeah, I also would prefer a Marshmallow or Nougat based ROM, since you can do more stuff with them and you can get an Android TV experience whenever you like by simply using 3rd party launchers.
Keep it up the good work!
Main fixes I'd like to see:
- Chrome fix (I know you just have to put a separate file inside a specific folder, but it would be better to fix it by scratch by installing a fresh new and optimized ROM)
- Netflix fix
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
New release
cm-12.1-20171208-UNOFFICIAL-mojo now available As I don't have Netflix/Amazon , please let me know if the this new build fixed the streaming issues in Chrome. I checked the forum posts, they mentioned setting the permissions on this file. I check the source code and this should be done by default in the building process.
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
Click to expand...
Click to collapse
thanks
For me it's indeed a hobby project for the weekend, I really like programming but besides writing some simulation software for work projects, I'm not in the programming/embedded development business. I already did a lot of reading in the Github changes/commits on the ADT-1 (molly) and TeamRegular repo's. It should be possible to create a CM13 rom as the ADT-1 has a working rom, CM14 is not working atm on the ADT-1 so I don't expect that I could provide such update.
Currently I'm focusing on the CM12.1 branch as there is a working "rom" (see above ) and trying to add Android TV on this. The ADT-1 has such ROM, so it must be possible on the MOJO. I'm busy merging the changes from ADT-1 to MOJO but atm my build is stuck in a boot loop.
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
Click to expand...
Click to collapse
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
I have experienced this on both CM12.1 and Remix OS. Two things can happen:
Firstly, if you are using an SD card in your MOJO and you have this plugged in at boot, it's a lottery as to whether or not the console will boot up with any WiFi. I'm no expert at all, but by this I mean that it appears that the WiFi module doesn't even load into the system. It cannot be turned on or off as it is all greyed out. As I say, this doesn't happen on every boot up, but is very annoying when it does.
Secondly, if you decide to fix this by not using an SD card in your MOJO, the WiFi will be better but still not great compared to the stock OS. Sometimes it never connects on fresh boots, meaning I have to go into WiFi settings and switch off and on again several times before it connects properly. Then on other times very odd things happen when it does connect. For example, quite often I have experienced when downloading big app updates for example, it seems to "flood" the WiFi if that doesn't sound silly, which results in every one in the house complaining that our router has kicked all their devices off the WiFi and they can no longer get any connection. The MOJO itself also disconnects when this happens. The only thing I can do then is to reboot the router.
I am assured none of these things happen on the stock OS.
Good luck with your builds. I myself would love to see CM13, as I use a modified TV Launcher to polish things off. My fear with the Android TV system is it won't recognise my 2TB external drive, which would mean I couldn't use it. Remix had issues with it also. CM12.1 has no problems at all mounting it and allowing me access to my media files.
Great work ! Tested - nothing broken
Keep going !
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
EdoNINJA93 said:
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
Click to expand...
Click to collapse
I've not seen this on the AndroidTV build of Unjustified Dev, so i'll diff it once with my build and see if there are driver changes.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
Could you please provide a feedback about Netflix and Wi-Fi issues?
carp_be said:
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
Click to expand...
Click to collapse
Replace
Code:
persist.sys.usb.config=none
by
Code:
persist.sys.usb.config=adb
in default.prop and build.prop, this will enable usb debuging during boot.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
More info plz!
Is WiFi any better? What apps do you use?
K-Project said:
More info plz!
Is WiFi any better? What apps do you use?
Click to expand...
Click to collapse
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
rahsoft said:
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
Click to expand...
Click to collapse
The playback issues could be related to DRM content. I saw that the CM build don't have the "google widevine" libraries included, while the AndroidTV build has. I'll include this in the next update,might solve the issue. Otherwise If you get a logcat file, the exception thrown by the app could shed some light what is needed.
besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
DPI can be changed to 240, will do (need to adjust ro. sf.lcd_density in system.prop file) .
Log
View attachment 2017-12-12-17-54-04.txt
Made little log - maybe will help
Please look at:
Process com.google.android.youtube (pid 10272) has died
Process com.lolapp.lolapptv (pid 22409) has died
Process ru.norgen.homevideo (pid 26606) has died
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
K-Project said:
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
Click to expand...
Click to collapse
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="[COLOR="yellowgreen"][B]1980[/B][/COLOR]x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="[B][COLOR="YellowGreen"]1920[/COLOR][/B]x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Are you sure?