yashsingh1/xdaforums huggingface dataset:
[M.O.J.O. Android Development] carp_be:
Hey K-Project,

I think that with the latest Lineage build (pure or AndroidTV variant) its clear that mojo is fully capable on running Android 6. I like AndroidTV as this is more limiting what the device can do and perfectly matches what most people do on a TV. The androidTV remote App is a huge addition for AndroidTV and works like a charm. With the latest build, the Bluetooth functionality has been improved so that the MOJO stock controller can also be activly used.

If I compare the AndroidTV based on AOSP_5.0 and lineage 13.0, then the lineage 13.0 build seems minimum equally stable. there are complaints that mojo is running "hot" and with android 6 we'll use more resources so this stress the SoC more which results in heat. But keep in mind that we also have a heat sink and that the SoC is protected against overheat. the SoC could be throttled down but dring my use in the last i've not seen any noticeable performance impact. So this clearly indicates to me that we have enough performance to run Android 6.

Currently I'm busy learning more about the linux Kernel and checking the improvements done on the ADT-1, it's also the starting point if I want to try Android N. So I definitely want to come up with improvements but I cannot give any commitment on a timeframe (the weekend only has 2 days and Sports are also important).
[M.O.J.O. Android Development] K-Project:
Hey thanks for replying!

I too like Android TV and agree it suits the device much better. I'm really pleased that you think the device can run Marshmallow and perhaps even Nougat further down the line. Despite my posts I don't want to give the impression that I want it all yesterday. I'm more than happy to wait while you folks figure it out. I think the problem was for me that my MOJO had absolutely and spectacularly crashed, rendering all my installed configured apps null. However, I've recently completely fresh installed CM12.1 and gotten that up to date so I'm happy for now.

I would still add that with Lineage 13 my MOJO got *really* bloody hot, so much so that I was worried about something happening to it. But then I hadn't done a fresh install, so maybe that didn't help either.

As for timeframes, well, I've said before, I think we're all just thrilled that someone is working on it at all. I'd rather you both took your time and got it right, than rushed anything out to tick a box, and I'm sure everyone else feels the same.

Thanks so much for your work carp_be, and also to Nono2lozere. :)
[M.O.J.O. Android Development] paulod1892:
Hi,

I'm currently running Remix 2.0 but my controller died and I replaced it with a Micro version and have since found that bluetooth needs to re enabled every start up which is a bit of a pain. From reading this thread it seems the bluetooth issue has been largely solved so I'm thinking of going for this ROM.

Would I need to revert to original set up or can this ROM be installed from Remix? I do have root access at present if thats any help.
[M.O.J.O. Android Development] carp_be:
No need to flash back stock - boot in recovery, advanced wipe (clear all) and flash this ROM. Please take into account that this is the androidTV ROM which will be al lot more limited compaired to Remix 2.0

enjoy flashing :)
[M.O.J.O. Android Development] carp_be:
dubble
[M.O.J.O. Android Development] EdoNINJA93:
What exactly are the Android TV limitations compared to the stock LineageOS 13, carp_be? :)
[M.O.J.O. Android Development] paulod1892:
Thanks for the reply, tried last night and apparently I don't have root, Remix says I do, Flashify says I don't :(

I've tried various versions of Kingroot but haven't had any success, is there a definitive version or am I best using the USB cable and my laptop?
[M.O.J.O. Android Development] krikit:
Wow, I can't wait to try this. Does this version have the same limitation of the sd card (as unable to be read by the system) that unjustified's original adt-1 port had? I'm itching to get some increased storage back on the MOJO.
[M.O.J.O. Android Development] krikit:
Great Android TV ROM, carp_be. I had a lot of fun looking around... until I noticed I have no sound! It may be due to my old 720p Visio tv. My MOJO has always had a weird relationship with it. YouTube and Pluto TV are also playing videos way too fast. I'm a little split on my focus right now, so my troubleshooting (for what it is, at least) may be lacking.
[M.O.J.O. Android Development] carp_be:
Heya, I would try out my first build "lineageos-13.0-20180101-UNOFFICIAL-mojo-AndroidTV" this rom uses an pre-builld audio drivers, might work better for you. SD card support should be functioning on both versions, but please take care that the Wi-Fi driver can become non functioning (same as with UJD build).

Maybe you did not grant Flashify root access ? I'm anyhow alwayse using the USB cable most stable for developing.

The main limitation is that the apps on AndroidTV need "leanback" support. Very simply said, they must be easy controllable with a "controller" (not mouse/touchscreen).

So on the Playstore you'll only find app with leanback support - which is represent ? 1 - 10% ? of all android Apps.

You still can side load all non-leanback apps on the AndroidTV rom but once you start using the "AndroidTV remote" (for me a keyboard/mouse on the mojo doesn't make sense if your on the couch :/) You'll feel that you need a leanback-app to have smooth control.

Beside this there is practically no difference.

Hope this gives you a bit more insight.
[M.O.J.O. Android Development] carp_be:
I also notice that the "hotplug" functionality is not always as stable on the latest rom. If you turn on your MOJO make sure that the HDMI cable is attached. Sometimes if you plug in the HDMI after you turn on the MOJO - sound could be lost. rebooting solves this in my situation.

I didn't notice that Youtube is playing to fast on my device :/ but I'm also having audio - could be that in your case the mediasever act strange which causes this side effect.
[M.O.J.O. Android Development] EdoNINJA93:
Thanks for your insight! :)

For example, I created some app backups thorugh Titanium Backup when I was using the CM12.1 on my Mojo.

Can I restore them on your Android TV rom and open them without any issue? Will I still be able to move a mouse cursor inside the apps using the C.T.R.L. controller?
[M.O.J.O. Android Development] K-Project:
Yes to be fair this also happens with the Raspberry Pi. If your TV isn't on or the HDMI cable isn't plugged in when you switch it on, you'll get nothing, even after you quickly plug the cables in/switch the TV on.

Ah, now this I did not know, so thank you for the information. I always admired the Android TV interface and thought it would suit the MOJO very well, but I did not realise it came with these limitations. I suppose it makes sense in some ways, but I would be very upset at losing so many apps and I wouldn't really fancy having to sideload so many.
[M.O.J.O. Android Development] EdoNINJA93:
Yup, IMHO the most annoying thing isn't the sideloading of the apps, but the fact that you have to also manually update them (by installing a newer apk version) every time, since the Play Store won't recognize them... :rolleyes:
[M.O.J.O. Android Development] Beaky77:
I have updated to this but have no sound at all, has anyone else had this problem?
[M.O.J.O. Android Development] krikit:
The Aptoide TV app typically solves this issue for me. Just be careful not to enable auto updates (in aptoide) since you may end up messing up some of the stock app installs.

---------- Post added at 08:47 AM ---------- Previous post was at 08:31 AM ----------

Yeah, posted about it on the previous page, in fact. Afterward, carp_be advised me to try his initial release (will do today). Is video streaming for you at normal speeds? Streaming too fast (looks like fast forward) was the other issue I had.
[M.O.J.O. Android Development] Beaky77:
Video streaming seemed perfect just no sound, do you know how to root this again since I flashed it it’s says it’s not rooted. Originally I used towelroot but this doesn’t work on this image. Thanks.
[M.O.J.O. Android Development] paulod1892:
Superuser also says I don't have root access so I'm unable to allow access to anything via that. I've reverted back to the original mmm rooting method via usb cable which seems to work, boots back into Remix with an 'Android is upgrading' progress bar but still no root access after loading:mad: it's doing my head in.

Is there any way to get back to stock and start from scratch again or am I stuck in Remix forever?

Edit - I've tried both towelroot and Kingroot with no success
[M.O.J.O. Android Development] krikit:
Thanks carp_be! This version worked perfectly! Audio's back, and video plays at normal speed now (for whatever reason). I haven't even tried Wi-Fi yet because the ethernet works really well. Thanks for pointing me in the right direction!
[M.O.J.O. Android Development] Beaky77:
My windows 10 pc is not seeing the mojo in ADB, I’m sure I have the right drivers installed has anyone got a link for me to make sure.
[M.O.J.O. Android Development] carp_be:
Can't you flash TWRP via USB and then boot into recovery ? Once you are in TWRP you can flash all you want :)

If you want to go to stock - you"ll need to download the latest OTA for the Mojo and flash this.

Lineageos doesn't work with towelroot. you need to install the SU addon (https://download.lineageos.org/extras)

I'm currently using the samsung ADB drivers on Win10 (installed via device manager)- this seems to be working fine.
[M.O.J.O. Android Development] paulod1892:
Noob question, do I not need to be rooted to flash TWRP? I did try that last night via usb but if failed so assumed I needed root.

If you could point me in the direction of an idiots guide that would be great. Once I'm in TWRP I'm fine it's just getting to that point on the mojo that beats me.

Also my Remix install has decided it is short of storage even though there is over 7GB left on internal and keeps prompting me every 30 seconds so I have to change regardless now.
[M.O.J.O. Android Development] EdoNINJA93:
You don't need to be rooted to flash TWRP, but you need to flash TWRP to be rooted (simple as that ;) )

1) Put the Root SuperSu flashable zip inside your Mojo (or its SD card)

2) Connect your MOJO to your PC using a male-to-male USB cable and launch the ADB interface

3) You have to type a specific command in order to flash TWRP to your MOJO

4) Type another command to directly open TWRP interface on your Mojo, flash the SuperSU zip and reboot your console

Follow this guide from minute 2:04 -> https://www.youtube.com/watch?v=fBzbGe-P2vE
[M.O.J.O. Android Development] paulod1892:
Thanks so much for the help, got it sorted now just going through first boot.

Thanks also to carp_be for his help, much appreciated :good::good::good::)

Getting loads of errors, apps not starting/ stopping etc, guess my install is corrupted. Really like the look of it though, will reinstall tonight using TWRP 3.2.1 now that I know what I'm doing :)
[M.O.J.O. Android Development] carp_be:
I think you probably didn't do a full wipe (all except external SD) ? Also take into account the Android TV room has gapps so don't flash any opengapps on this ROM.

Good luck !
[M.O.J.O. Android Development] carp_be:
Had 2 busy weekends so no updates yet. Bought a new HDD to install Ubuntu in dual boot instead of a virtual machine , was more challenging than I remember :p.

Next up would be kernel changes/patches from ADT-1 or HP Bowser kernel to improve stability. Will be a slow slow process but I hope to learn a lot on kernel development. I'll keep you all tuned.
[M.O.J.O. Android Development] EdoNINJA93:
Really thank you, every effort is VERY MUCH appreciated! :)

And what do you think about the vanilla LineageOS 13 for the Mojo? Is there any room for improvement also for it?
[M.O.J.O. Android Development] paulod1892:
Yep reinstalled earlier and all working fine this time around. Found the reason i couldn't install TWRP 3.2.1-0 was a typo on my behalf :o

Really liking the look of this and everything I've tried has worked fine, only issue I have is Play Store seems limited but can work round it by searching in the browser and I've now installed most of the apps I use now
[M.O.J.O. Android Development] paulod1892:
I'm having loss of audio issue, tried rebooting, unplug and restart and with tv on and off and it hasn't came back on. I think I read earlier in thread to try one of the earlier builds, can I flash over current set up or is it best to wipe and start from scratch and if so which build would be better

Thanks
[M.O.J.O. Android Development] dotlee:
Try removing the YouTube update
[M.O.J.O. Android Development] EdoNINJA93:
Mmmh, it sounds strange that an older build seems to work better than the newest one... :confused:
[M.O.J.O. Android Development] carp_be:
It sounds indeed strange, but compared to the initial build , de device drives were updated + "sound driver" is now build from open source code. So quite some changes were done. The more that is changed the more that could go wrong unfortunately :(.

The sound driver code is in-line with what the ADT-1 device is using. But there they don't have the sound issue.

I noticed that mainly the "hotplug" of HDMI can cause no sound. So I each time boot with HDMI already attached. Besides this limitation, sound is working find on my MOJO.

Currently I'm busy reading in on Kernel development, I'm at the moment not that succesfull as nono2lozere on kernel modifications as my kernels are not yet working. Quite convinced that with the correct kernel patch the Sound should be fix, I only need to find it:/
[M.O.J.O. Android Development] EdoNINJA93:
No problem with that, we'll wait as much as it's necessary :)
[M.O.J.O. Android Development] carp_be:
I've got a beta build available , but I need some more feedback on the audio/video output as I made some big kernel changes. On my TV, the audio & video worked and the mojo didn't get "super" hot.

changes:

- enabled kernel feature UID_CPUTIME - should allow better CPU management between process

- updated Tegra4 video drivers to be inline with ADT-1 drivers

https://drive.google.com/open?id=1_nUAC4kn39vEowW-q9yUcSOkfQ7DYBNK
[M.O.J.O. Android Development] EdoNINJA93:
I'm testing it right now and I see an improvement both in audio stability and CPU management, even though the audio still disappeared 1-2 times in 5 reboots...
[M.O.J.O. Android Development] carp_be:
thanks for the feedback :) I didn't see the sound unavailability yet with the driver update. I'll check if I didn't include some older patches from ADT-1.

In the mean time I've been busy "downgrading" the device blobs back to the ADT-1, these we're for most people more stable and for me to. Due to the downgrade or something else the androidTV remote is atm not functioning :( without that support it make no sense to release an update.
[M.O.J.O. Android Development] EdoNINJA93:
What do you mean, exactly? :(

Thanks carp_be for your constant support, anyway! :o
[M.O.J.O. Android Development] carp_be:
That I first need to fix this issue ;)

ps: Everyone who want's correct/working casting support I would suggest to download/install this APK :

https://play.google.com/store/apps/details?id=com.ionitech.airscreen

Been testing this and I've not seen any issues with casting.
[M.O.J.O. Android Development] EdoNINJA93:
Oh, now I understand ;)
[M.O.J.O. Android Development] carp_be:
My development MOJO box broke down this week - HDMI connector is loose so I'll need to solder that back on. Hope I can fix it next week on my work.

I did manage to fix the androidTV remote issue so I'll upload my latest build - this uses the previous device drivers from ADT-1 which are in my view more stable.

Next step is so investigate the sound issues as I also had sometimes no sound.
[M.O.J.O. Android Development] EdoNINJA93:
I'm sorry for your HDMI problem... :(

So you experienced some sound issues also with this new build?
[M.O.J.O. Android Development] carp_be:
probably yes but due to my not so properly working HDMI connection I cant be sure.
[M.O.J.O. Android Development] KraZy_SkitZy:
Is there any way to get the google play store to to allow me to download tegra games? As games like doom 3 and half life should be accessible but aren't for me.
[M.O.J.O. Android Development] carp_be:
From ROM PoV , the mojo should be detected as a Tegra4 device , but I don't know if doom 3/Half-Life are compatible with a Tegra4 chipset (Shield has Tegra ?X1/K1 ?) .

you could always try : https://www.xda-developers.com/how-to-legally-install-unsupported-android-tv-or-nvidia-shield-games-on-any-android-device/ though it might not be as "legal" as the article describes.

Hope this helps
[M.O.J.O. Android Development] carp_be:
new update available - should increase sound stability !
[M.O.J.O. Android Development] EdoNINJA93:
Great! :D

I'll test it soon!

I think we are almost done with this ROM for the Mojo...
[M.O.J.O. Android Development] carp_be:
Nice hope you come to the same conclusion as me :)

If so i'll create a non-TV variant to - as the it's been a while to

in regards of life-time of this ROM, I still have things to do but this will be mainly in preparation of Nougat (no warranty but this is my next target)
[M.O.J.O. Android Development] EdoNINJA93:
Yeah, usually the non-TV variant is the most preferred by users because it hasn't the same app and UI limitations as the Android TV one, but I find it very cool anyway! :)

Really THANK YOU again for the time you are dedicating to this tiny, little, old and troubled console :cowboy:
[M.O.J.O. Android Development] K-Project:
Thank you from me too for your continuing hard work on our much misunderstood console. I'll be installing this over the Easter weekend. :)

(I spotted your typo btw, and was just about to say "but... the MOJO is a Tegra4 device not Tegra3"! Thanks for correcting and at least avoiding my confusion!)
[M.O.J.O. Android Development] K-Project:
Hey Edo, have you had a chance to try this build yet, and is it very stable for every day use? I'd love to reset the MOJO as my main media player/retro console in the living room but really need a stable ROM for it first. I'm curious to know your experiences (or anyone's really) before I take the plunge myself. Thanks.

Hey what happened to nono2lozere? Has he abandoned the console now?
[M.O.J.O. Android Development] EdoNINJA93:
I'm trying it right now (fresh and clean install, with root add-on flashed)...

- Both Wi-Fi and sound seem to work sometimes, but other times they won't after a reboot... also there seems to be a huge performance slowdown when this happens

- The Play Store sometimes crashes without any reason

- I tried Snes9X EX+ emulator and it works fine, but the Back button directly closes the app and it won't take me to the main screen in order to change the game/settings (the multitasking function doesn't seem to work well)

In general I think that sometimes the ROM doesn't run well at all, and you have to reboot it because it's unusable...

When it boots fine, there is still the Play Store issue...

I haven't had a chance to try YouTube, still...
[M.O.J.O. Android Development] EdoNINJA93:
I've also tried the stock LineageOS 13 (fresh and clean install, root add-on flashed) and I found it a bit more stable than the Android TV version, except for the HDMI audio which never activated in at least 5-6 reboots...
[M.O.J.O. Android Development] K-Project:
Thanks for replying Edo. Your experiences are much appreciated. :)

Bit of a shame however. It doesn't sound ready for regular use at this stage. :( I'll keep an eye on developments for now I think.

I did reinstall CM12.1 a few weeks ago and it was fine for a (very) short while, but then the MOJO started freezing all over again when the Play store was updating. I tried a different launcher thinking that might be the issue, but that just got it stuck in a bootloop.

MOJO sure knows how to break your heart... :( I honestly don't know what to do with it now. :( :(
[M.O.J.O. Android Development] EdoNINJA93:
I discovered that ALL Robert Broglia emulators now at 1.5.37 version cause the crash/bootloop on the Mojo in CM12/12.1...

So sad... :(

In my opinion the stock LineageOS 13 has a lot of potential, but the HDMI sound disappearing and the semi-reboot problems are too much annoying to live with...

I currently reverted back to CM12.1 (the updated version of 26/12 by carp_be) and I installed just the essential apps: RetroArch, ePSXe, Mupen64Plus FZ, PPSSPP, Drastic, YouTube, Kodi, VLC, ES File Explorer and a few others (all updated to the latest version through the Play Store... just be careful to uncheck the option to automatically update your apps)...

I hope it stays good as long as possible, waiting for a proper new CFW...
[M.O.J.O. Android Development] K-Project:
Wow, all the Robert Broglia apps cause this issue??? I would never have thought it. How did you figure this out Edo? I always have all Robert's apps installed on my MOJO, though Retroarch is my main go-to app.
[M.O.J.O. Android Development] EdoNINJA93:
The latest March update of all Broglia emulators (version 1.5.37) cause issues with CM12/12.1 because I tried this morning to isolate the app which was causing me the boot-loop/crash of the system...

And I've found it was Snes9x EX+ 1.5.37 (I also tried with GBA.emu 1.5.37 and it caused me a lot of problems with any file manager app)...

I think the only way is to keep the old 1.5.34 version, but the newest build improves the emulation a lot...

I think I'll stick with RetroArch, which thanks to his cores is still the best emulation app for Android... (at least for 8/16/32 bit retrogames)
[M.O.J.O. Android Development] Blaggah:
Just flashed the rom and it's indeed a good rom compared to cm12.1 which I had running on it before. However, I can't seem to get audio at all. No sound through YouTube, Kodi, or any other streaming apps. And video also plays fast.
[M.O.J.O. Android Development] EdoNINJA93:
Reboot your MOJO a few times, and you'll notice that you'll get different results on every boot...
[M.O.J.O. Android Development] Blaggah:
So true

You're absolutely right, i rebooted after my first initial and sound was working. However, i think my twrp might've gotten screwed up.. I can't seem to see anything when i click on either storage. And i think that i might've happened to me getting the prompt to make my sd card as internal. All i wanted to do was flash the addonsu in order to get full root access.. What do i do now? I really didn't wanna have to start over :fingers-crossed:
[M.O.J.O. Android Development] EdoNINJA93:
I flashed the root add-on just after wiping the device and flashing LineageOS while in TWRP...

Without root access you can't reboot in TWRP recovery anymore through the MOJO interface... you have to connect it to your PC and manually root it through ADB...
[M.O.J.O. Android Development] Blaggah:
That's what I was trying to avoid. It's been years since I've done that adb mumbo jumbo on the mojo. Cared to direct me to a tutorial to achieve that? I'll have to flash the newer TWRPin order to sort things out within twrp. Thanks in advance.
[M.O.J.O. Android Development] EdoNINJA93:
Follow the video instructions from minute 2:05

https://www.youtube.com/watch?v=fBzbGe-P2vE

Then enter this command:

fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img

while in ADB interface to boot your Mojo and directly launch TWRP recovery (it has to be connected to your TV while doing this)

I also suggest you to stay on TWRP 2.8.2 and avoid the other versions (2.8.2 never gave me any problem, and it can flash everything, even the newest LineageOS 13, both stock and Android TV versions)...