[ROM][AOSP][LolliRock][v.2.1]

[zulu99]

I just got my otg cable tonight, and my k400 and logitech wireless mouse work fine, keep trying. I do have the problem with the play store not letting me install a lot of the apps I want, like twitch tv and various others.

you can install it manually with the apk. some apps require also portrait functionality from google play. this firmware have only landscape as it must be. but you can install the apk manually without problem if the app can run in landscape. 97% of the apps

 

[gullatec]

ADT-1

Any upcoming love for the ADT-1?

 

[KalenXI]

Has anyone else been having bluetooth issues with this firmware? It started for me last night and persists even after a full reset with the factory image. The only thing I've found that can occasionally solve it is to reflash the kernel but that doesn't always fix it and when it does it only fixes it for 10-15 minutes.

From the logs it seems like the bluetooth IC keeps freezing and not responding to commands after which the OS restarts the bluetooth controller:

E/BTLD    ( 2376): ######################################################################
E/BTLD    ( 2376): #
E/BTLD    ( 2376): # WARNING : BTU HCI(id=0) command timeout. opcode=0x200c
E/BTLD    ( 2376): #
E/BTLD    ( 2376): ######################################################################
E/bt-hci  ( 2376): Num consecutive HCI Cmd tout =2 Restarting BT process

But it does this every 30 seconds or so and so I can't get anything to pair.

Does anyone have any ideas as to what could change that would survive a factory reset and reinstalling the factory firmware?

 

[zulu99]

Has anyone else been having bluetooth issues with this firmware? It started for me last night and persists even after a full reset with the factory image. The only thing I've found that can occasionally solve it is to reflash the kernel but that doesn't always fix it and when it does it only fixes it for 10-15 minutes.

From the logs it seems like the bluetooth IC keeps freezing and not responding to commands after which the OS restarts the bluetooth controller:

E/BTLD    ( 2376): ######################################################################
E/BTLD    ( 2376): #
E/BTLD    ( 2376): # WARNING : BTU HCI(id=0) command timeout. opcode=0x200c
E/BTLD    ( 2376): #
E/BTLD    ( 2376): ######################################################################
E/bt-hci  ( 2376): Num consecutive HCI Cmd tout =2 Restarting BT process

But it does this every 30 seconds or so and so I can't get anything to pair.

Does anyone have any ideas as to what could change that would survive a factory reset and reinstalling the factory firmware?

Bluetooth stuff in kernel and in firmware is pure AOSP. I not have problems with bluetooth, but i not use frequently the bluetooth.
If you have flashed also the stock firmware, nothing remain of the old one.
Can be your bluetooth external device the problem ? or dead batteries that cause strange disconnections and provocate this bug ?

 

[KalenXI]

Bluetooth stuff in kernel and in firmware is pure AOSP. I not have problems with bluetooth, but i not use frequently the bluetooth.
If you have flashed also the stock firmware, nothing remain of the old one.
Can be your bluetooth external device the problem ? or dead batteries that cause strange disconnections and provocate this bug ?

I don't think it's the bluetooth device cause it won't pair with any device I've tried. I'm beginning to think something's gone wrong with the bluetooth chip itself.

 

[zulu99]

I don't think it's the bluetooth device cause it won't pair with any device I've tried. I'm beginning to think something's gone wrong with the bluetooth chip itself.

I would not want to advertise myself, but you give me the assist. I don't have bluetooth problems with any android tv box because i use DroidMote. When i want connect an hardware controller because in some games the soft gamepad is not sufficient, i connect it to the bluetooth of the phone or via otg cable to the phone and the command of the hardware controller are forwarded from droidmote client to droidmote server like the controller was connected phisically to the server without lag. Is implied that your hardware controller is already working on the client device, regardless DroidMote Client. In this way i can play with games with controller support and also with games that accept only touch actions.
sorry for this ads, but can be useful for someone.

however, your problem is strange.

 

[KalenXI]

I would not want to advertise myself, but you give me the assist. I don't have bluetooth problems with any android tv box because i use DroidMote. When i want connect an hardware controller because in some games the soft gamepad is not sufficient, i connect it to the bluetooth of the phone or via otg cable to the phone and the command of the hardware controller are forwarded from droidmote client to droidmote server like the controller was connected phisically to the server without lag. Is implied that your hardware controller is already working on the client device, regardless DroidMote Client. In this way i can play with games with controller support and also with games that accept only touch actions.
sorry for this ads, but can be useful for someone.

however, your problem is strange.

Yeah I actually already bought DroidMote. That's how I was able to debug the bluetooth so I could have ADB connected via USB and control via DroidMote since I couldn't get the bluetooth to connect. I didn't know it could forward input commands from a hardware controller on the client to the server though I'll have to check that out.

 

[midnightzak]

Do LolliRock and unleashed kernel play together?

 

[zulu99]

Do LolliRock and unleashed kernel play together?

a boot.img is composed ramdisk + kernel + commands

my ramdisk is the aosp version + libhoudini stuff + mtp,adb support. Then i proposed to defconoi to chose the better collabotation. the kernel can be used and i'm also happy that other can do part of the work. But ramdisk is necessary to have things in the firmware. i 'm fully open to all kind of collaboration. i'm not the classic firmware developer, i work only to have a better nexus device for TV. My work is the work of all.

 

[zulu99]

I don't think it's the bluetooth device cause it won't pair with any device I've tried. I'm beginning to think something's gone wrong with the bluetooth chip itself.

I read in others threads some people with bluetooth problems on stock firmware. One thing is sure, the android tv firmware, handle the bluetooth with a non standard bluetooth app to permit things with the little hardware remote. Instead LolliRock based on AOSP handle the bluetooth in the standard android way. i propose to you do do other tests, because you are able to do and then i can see also the bluetooth drivers part if need some additions / corrections like the audio part already freed.

But my priority for now is:
the hwcomposer overlay problem
webcam video HAL

But let me be clear, the serious work will begin on January 2, 2015. Now it's time to celebrate the new year, for me, for you and for all.
Happy new year to all.

 

[defconoi]

Do LolliRock and unleashed kernel play together?

I'm not sure I haven't tried, if there is ramdisk modifications I'll have to add that to unleashed

 

[zulu99]

I'm not sure I haven't tried, if there is ramdisk modifications I'll have to add that to unleashed

if you want you can make two versions, one with stock ramdisk, one with my ramdisk.
my ramdisk is the AOSP version + mtp,adb in init.fugu.usb.rc and i added ro.dalvik.vm.native.bridge=libhoudini.so in default.prop

but you know how to extract the ramdisk from my boot.img and add it to your kernel.

i explain for others: the ramdisk can be decompressed and all files inside can be readed.

But if you prefer, i can get also your kernel and add to my ramdisk. It is not useful to do two jobs in the same direction.
If you like work on kernel, i'm very happy and i trust your work.

 

[defconoi]

if you want you can make two versions, one with stock ramdisk, one with my ramdisk.
my ramdisk is the AOSP version + mtp,adb in init.fugu.usb.rc and i added ro.dalvik.vm.native.bridge=libhoudini.so in default.prop

but you know how to extract the ramdisk from my boot.img and add it to your kernel.

i explain for others: the ramdisk can be decompressed and all files inside can be readed.

But if you prefer, i can get also your kernel and add to my ramdisk. It is not useful to do two jobs in the same direction.
If you like work on kernel, i'm very happy and i trust your work.

feel free to use my kernel for the next release, I'm out of a computer atm mobo died, awaiting newegg shipment for next update

 

[midnightzak]

I'm finding some app compatibility issues on LolliRock, for instance Hearthstone launches and crashes, and World of Warriors (which sort of worked on stock) also crashes. Any ideas or am I just expecting too much too quickly?

Either way, thank you for your time and work on this build!

 

[zulu99]

​

I'm finding some app compatibility issues on LolliRock, for instance Hearthstone launches and crashes, and World of Warriors (which sort of worked on stock) also crashes. Any ideas or am I just expecting too much too quickly?

Either way, thank you for your time and work on this build!

Don't forget that the Nexus Player is an x86 device, thanks to houdini can work also arm-only app because translated, but we can't do miracles. In little time, many more apps wil be updated to support intel 64 bit cpu devices but also now the compatibility with this firmware is very good.

 

[zulu99]

Good news for the hwcomposer overlay problem, that in some apps make a popup menu black etc. Aka when you install Chrome and you see the first popup completly white etc.

If in developer options, you check "Disable HW overlays - Always use GPU for screen compositing" the problem disappears.
This problem is present also in the android tv firmware, but in android tv you can't check this option in developer settings i think. But now we know the problem and will be solved.
Someone with better english can report also the bug in AOSP bug reports.

Attention the checked option restore the default value after reboot but when is checked all work without this annoying problem.

 

[KalenXI]

Good news for the hwcomposer overlay problem, that in some apps make a popup menu black etc. Aka when you install Chrome and you see the first popup completly white etc.

If in developer options, you check "Disable HW overlays - Always use GPU for screen compositing" the problem disappears.
This problem is present also in the android tv firmware, but in android tv you can't check this option in developer settings i think. But now we know the problem and will be solved.
Someone with better english can report also the bug in AOSP bug reports.

Attention the checked option restore the default value after reboot but when is checked all work without this annoying problem.

I wonder if it could be related to this bug report: https://code.google.com/p/android/issues/detail?id=32564

Sounds like hardware overlay over HDMI requires 3rd party driver support and without that it will just fail to render. Doesn't look like there's much hope for it being fixed though since the bug has been open since 2012 and is apparently an issue in the HDMI drivers rather than AOSP itself. Though they should at least detect if HDMI is attached and disable the overlay if it's not compatible.

 

[zulu99]

I'm finding some app compatibility issues on LolliRock, for instance Hearthstone launches and crashes, and World of Warriors (which sort of worked on stock) also crashes. Any ideas or am I just expecting too much too quickly?

Either way, thank you for your time and work on this build!

For World of Warriors and some others unity games arm-only get the linked file libEGL.so and copy in the folder /system/lib/arm/nb/

assign 644 permissions to libEGL.so
with es file explorer you can assign the permissions like others .so files from more -> properties -> permissions

will be added to the next version. Thanks for your post.

https://mega.co.nz/#!nAYjTIpK!TXMqVjTchcRqVOSKVlSUlrU5TRgjEi5MKJQJFeh_Acc

Sorry this was my forgetfulness

 

[KalenXI]

I found a more permanent way to disable HW overlays. You can either use Tasker and the Secure Settings plugin to set it on boot. Or use Tasker's shell action to run "service call SurfaceFlinger 1008 i32 1" as root on boot.

 

[mattrb]

On my plasma TV. I cannot see the top pull down menu bar. How can I perform scaling?