[20180521][UNOFFICIAL] CM12.1 for Mad Catz M.O.J.O - M.O.J.O. Android Development

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?