Rom building & a script question.

[stal2k]

I'm wondering about .ko and .so files, I'm assuming they are both drivers, but are the .so files loaded at boot automatically? reason I'm asking is because out of the box my mk808 would not work with a random logitech webcam I plugged in, but I downloaded camera+ ics on a whim and after I run that app, other apps can recognize the camera, I decompiled it and found the lib files it used. is there an easy way to bake that into my startup?

also for a script, I am sure some of you have the ipazz remote with the mic/headset built in. is there an init.d script someone posted I missed to set the default audio to hdmi in soundmanager on boot rather then going in and changing it?

PSA as well, I'm working on getting together my xbmc repo that will have some common direct launching of android apps so you can use them from programs/menus just like the nuska ones.... any requests?

[leolas]

I'm wondering about .ko and .so files, I'm assuming they are both drivers, but are the .so files loaded at boot automatically? reason I'm asking is because out of the box my mk808 would not work with a random logitech webcam I plugged in, but I downloaded camera+ ics on a whim and after I run that app, other apps can recognize the camera, I decompiled it and found the lib files it used. is there an easy way to bake that into my startup?

also for a script, I am sure some of you have the ipazz remote with the mic/headset built in. is there an init.d script someone posted I missed to set the default audio to hdmi in soundmanager on boot rather then going in and changing it?

PSA as well, I'm working on getting together my xbmc repo that will have some common direct launching of android apps so you can use them from programs/menus just like the nuska ones.... any requests?

I think .ko are drivers and you need to install them by insmod, and if your rom has init.d support(all Finless rom i know had it) then the .ko can be added in it. Otherwise .so are libraries ,like dll in windows systems,they must be in the right place to be used by the system, programs or drivers, and with the correct permissions. Usually the .so files are in /system/lib

[stal2k]

I think .ko are drivers and you need to install them by insmod, and if your rom has init.d support(all Finless rom i know had it) then the .ko can be added in it. Otherwise .so are libraries ,like dll in windows systems,they must be in the right place to be used by the system, programs or drivers, and with the correct permissions. Usually the .so files are in /system/lib

ok thanks that makes sense, I was worried about just tossing .so in the mix and winding up in a bootloop from hell. you would'nt happen to know what the deal is with this fake landscape deal we got going on the mk808 in the build.prop? It wreaks havoc with a few apps and its a bitch to fix. I even decompiled and changed one .apk to try to fix it but no dice, forced landscape with an app too. it's the sensorLandscape call that wanks it.

[leolas]

ok thanks that makes sense, I was worried about just tossing .so in the mix and winding up in a bootloop from hell. you would'nt happen to know what the deal is with this fake landscape deal we got going on the mk808 in the build.prop? It wreaks havoc with a few apps and its a bitch to fix. I even decompiled and changed one .apk to try to fix it but no dice, forced landscape with an app too. it's the sensorLandscape call that wanks it.

Sorry english is not my native language and i cant understand it, pls can you explain it clear? thanks.

[stal2k]

I was thanking you for your information because the .dll made things clear for me!

then I was asking if you knew how to fix the other two issues I had. One is in the build.prop of finless 1.7
there is a "ro.sf.fakerotation=true" and "ro.sf.hwrotation" this causes problems with some apps, did'nt know if there was a workaround.

Also in settings every bootup I have to go to sound device manager and change audio to rockchips hdmi, I have ipazz remote with build in speaker/mic but I don't want it defaulting to that, I'm still learning the whole script/init.d aspects of android and it seems like that could take care of it. (I am setting this up for someone who is computer literate enough to work a calculator)

I really appreciate your help, especially not being able to fully understand my rambling

[leolas]

I was thanking you for your information because the .dll made things clear for me!

then I was asking if you knew how to fix the other two issues I had. One is in the build.prop of finless 1.7
there is a "ro.sf.fakerotation=true" and "ro.sf.hwrotation" this causes problems with some apps, did'nt know if there was a workaround.

Also in settings every bootup I have to go to sound device manager and change audio to rockchips hdmi, I have ipazz remote with build in speaker/mic but I don't want it defaulting to that, I'm still learning the whole script/init.d aspects of android and it seems like that could take care of it. (I am setting this up for someone who is computer literate enough to work a calculator)

I really appreciate your help, especially not being able to fully understand my rambling

ahh your welcome, about your rambling its my fault, my english is not so good so sometimes i fail understand it.

The fake rotation issue maybe this could help:

http://www.armtvtech.com/armtvtechforum/viewtopic.php?f=6&t=352&start=10

Pay atention in posts by FinlessBob about services.jar and timitom answers too.
More here :

http://www.freaktab.com/showthread.php?4061-Portrait-Mode

About sound problem I dont know how set default sound driver so i cant help

[stal2k]

ahh your welcome, about your rambling its my fault, my english is not so good so sometimes i fail understand it.

The fake rotation issue maybe this could help:

http://www.armtvtech.com/armtvtechforum/viewtopic.php?f=6&t=352&start=10

Pay atention in posts by FinlessBob about services.jar and timitom answers too.
More here :

http://www.freaktab.com/showthread.php?4061-Portrait-Mode

About sound problem I dont know how set default sound driver so i cant help

ya I may dig in to that later, I think/hope it could be it, when I look at logcat it actually tries to change it to a resolution much higher then device, then down lower (gameloft game) so I have a tiny window where the interactive UI elements and ART don't matchup, it's wierd. I've been playing with the Xposed framework which is pretty handy but did'nt solve problem, I decompiled the APK in question and in the
manifest.xml file I see it call Landscape, then sensorLandscape, and I've narrow that to where
the problems occur. methinks the real fix is the developer but I don't see that happening so maybe I'll just be happy and leave well enough alone before I smoke my install and have to spend another 6 hours nailing the XBMC config.

[Finless]

Can you explain what APP your having issue with and what exactly is happening?
Fake rotation and rotation in build.prop work on later ROMs but rotation is locked so an APP should not be able to rotate the screen. Earlier ROMs the rotation lock was done differently. Basically it would not honor what build.prop said and in fact if you mod rotation in build.prop on those early ROMs it would cause a bootloop.

Bob

[stal2k]

Re: Rom building & a script question.

Can you explain what APP your having issue with and what exactly is happening?
Fake rotation and rotation in build.prop work on later ROMs but rotation is locked so an APP should not be able to rotate the screen. Earlier ROMs the rotation lock was done differently. Basically it would not honor what build.prop said and in fact if you mod rotation in build.prop on those early ROMs it would cause a bootloop.

Bob

Sure I'll post a log cat with pics, be best way to explain it without confusing everyone.

Sent from my IdeaTabA2109A using Tapatalk HD

[stal2k]

ok here is what I got sorry for sizes. I don't think it's trying to rotate it, it's resizing it as if it's in portrait, I saw from the apk itself it calls it two different ways, landscape /sensorlandscape, figured it had something to do with the fake rotation. here ya go

1. normal
2. happens mid asset load (same pic)
3. ingame, full screen but the UI overlay is chopped you can see the glow of button (should be way further to the right, also top left corner the "buff" graphic is a few inches to the right of it's anchor/background.
4. that about shows whats getting cutoff ingame

I noticed in log it is rendering 1280/627ish and then a 980/600 resolution, so it's like the OpenGL and UI showed up to two different parties. I'm assuming it has to do with the fake rotation because this existed on both 808 and 808b, and stock/finless/cm/armtv roms

[Finless]

To me this game appears to not adjust to resolution of the TV. like it expects a max resolution for a tablet like 1024x960 or something.

However you can force portrait with my ROM. Edit build.prop and change ro.fs.rotation=0
This will rotate to portrait.

Now run the game and see what it does.

Bob

[stal2k]

To me this game appears to not adjust to resolution of the TV. like it expects a max resolution for a tablet like 1024x960 or something.

However you can force portrait with my ROM. Edit build.prop and change ro.fs.rotation=0
This will rotate to portrait.

Now run the game and see what it does.

Bob

ya thats what I thought too but
[ 03-08 11:27:43.339 22802:22815 I/GLF ]


[AndroidResizeScreen] app_android_.hpp:506 (4/5) AndroidResizeScreen 1280x672

that looks about right, it's the overlay UI thats borked. I tried changing to portrait, it did but it was sideways on my TV lol, it did'nt work the game was still messed up. I have another theory I'm going to try and if it works I'll feel like a big dummy