Database Users

Addressing the G-Sensor calibration issues

http://forum.xda-developers.com/showpost.php?p=7067687&postcount=53
That appears to address a similar issue - perhaps it would work? My tablet gets here tomorrow, so I'll give it a try. Until then, if someone else has looked into the problem at all, maybe we could get a thread going on how it can be fixed. Has anyone made any headway?

JRowe47 said:
http://forum.xda-developers.com/showpost.php?p=7067687&postcount=53
That appears to address a similar issue - perhaps it would work? My tablet gets here tomorrow, so I'll give it a try. Until then, if someone else has looked into the problem at all, maybe we could get a thread going on how it can be fixed. Has anyone made any headway?
Click to expand...
Click to collapse
No report on this yet? I'm very interested as this issue affects the pic gallery.
BTW, TNT Lite v2 FTW!

I checked it out but the file he is referring to isn't there, used rootexplorer
Also the sensor app shows absolute 0 way off, it does seem as if this can be fixed, or at least changed

This depends on which accelerometer the system is using. gTab may not have this accelerometer.

in regards to orientation issues:
It's actually right. I found this the other night and just haven't had a chance to post it yet: nvidia developer pdf.
It seems that the orientation being 90 degrees off is correct (link, page 6). Somehow we need to fix the transforms to get us from the correct orientation to the phone-standard orientation that apps seem to be written on (have a look at page 7 of the pdf).

TNT lite 2.0 seems to have fixed the issue
I've loaded TNT lite 2.0 and then started up the game Raging Thunder and it works perfectly.
Warning on TNT lite 2.0. Make sure you have clockwork mod loaded first. My machine went into a boot loop and I had to use clockwork mod to get out of it.

Raging Thunder 2
NeuronFlash said:
I've loaded TNT lite 2.0 and then started up the game Raging Thunder and it works perfectly.
Warning on TNT lite 2.0. Make sure you have clockwork mod loaded first. My machine went into a boot loop and I had to use clockwork mod to get out of it.
Click to expand...
Click to collapse
Raging Thunder 2 has never been an issue for me, and is one of the smoothest running games...it's obvious that they have done something different. Maybe it can be used to fix other games.

robertged2 said:
Raging Thunder 2 has never been an issue for me, and is one of the smoothest running games...it's obvious that they have done something different. Maybe it can be used to fix other games.
Click to expand...
Click to collapse
I have Raging Thunder 2 and works great on my Incredible, but on Gtablet, shows only half screen at the title and never gives options to load up. How did you get it to work?
Reports are it is an Nvidia issue and the current patch does not cover the problem. Did not for me, so I can agree with that assertion.
I am using TnT Lite 2.0.

Anyone else notice that is they hold the tablet upside down as using it while lying on your back, the touch screen has issues, very laggy, have to hold down my presses many times for it to register, like accessing apps I have to try three+ times to get it to work. When I rotate the device back to on my lap everything works great. Wondering if this has something to do with the G-Sensor hardware/software.

t3h_g3n3r4l said:
It's actually right. I found this the other night and just haven't had a chance to post it yet: nvidia developer pdf.
It seems that the orientation being 90 degrees off is correct (link, page 6). Somehow we need to fix the transforms to get us from the correct orientation to the phone-standard orientation that apps seem to be written on (have a look at page 7 of the pdf).
Click to expand...
Click to collapse
That 's what we concluded in our group too.
The G-sensor is not a defect, it 's the game design that use a different orientation.
If you look at Tom Clancy 's flight game and Raging thunder 2, the G sensor works properly.
What we worry the most is that if we do switch the machine's G-sensor output, we will have problem with newer game which designed with Tablet orientation in mind.
One of the developer in our group are actually mod the game itself so that the x-y axis are switched in the game app. This seems to be working quite well. He did about 10~15 games already.

pcmtse said:
That 's what we concluded in our group too.
The G-sensor is not a defect, it 's the game design that use a different orientation.
If you look at Tom Clancy 's flight game and Raging thunder 2, the G sensor works properly.
What we worry the most is that if we do switch the machine's G-sensor output, we will have problem with newer game which designed with Tablet orientation in mind.
One of the developer in our group are actually mod the game itself so that the x-y axis are switched in the game app. This seems to be working quite well. He did about 10~15 games already.
Click to expand...
Click to collapse
Ummm which games...

xmr405o said:
Ummm which games...
Click to expand...
Click to collapse
check pm and try it out

You all are all correct to some point. The logical fix would be a sensor orientation option built into settings, since changing the orientation will fix some games and probably result in others being broken. Raging Thunder 2 is an example.

Where can we get said games?

I bought Raging Thunder 2. Nice game on G
You are probably referring to the modded games... Yeah- where do we get them?

I also have the sensor issue in my gallery. It makes it quite difficult to make selections. If it is just those games having this issue, how can I fix it in gallery?

rushless said:
I bought Raging Thunder 2. Nice game on G
You are probably referring to the modded games... Yeah- where do we get them?
Click to expand...
Click to collapse
hmmmm....................
I don't think it's good to post here right?
I will pm you all

I would also like a pm with games. Thanks

Would you please PM me those also,,, Thanks

i'm curious about said games as well.

[Q] MIUI Rom wont use certain applications?

Hey guys, I have posted this in another forum but didnt get much luck.. wanted to try it here before I gave up and hung myself.
Very briefly: I have just flashed my fourth rom, this time I went for MIUI. Fantastic, really good speed, very aesthetically pleasing, etc.
Anyway, I have tried to run some GBA emulators and they havent worked. They flash the black screen for about 5 seconds, and the game plays in the background but it minimises the program; it says it is still running in the notification area but when I try to access it it just minimizes again.
Is this a common problem on MIUI? Has anyone else had a similar issue? Im sure its MIUI related as I have had the program running on several different ROMS..
Please dont make me choose between this awesome rom and being able to play Mother 3!!
Thanks guys;
Vincent.
Edit:
Turns out it is a gingerbread incompatibility. Can be fixed by installing a compatible emulator *facepalm*

Navigation Volume too low

Hi guys, I have an issue with Sat Nav volume. I will try to break it down simply:
Sat Nav [CoPilot and Navigator tested]
Music app [PowerAMP and HTC Music tested]
Audio cable [3.5mm audio jack - plugged into car stereo]
Sound settings all full [set in Quick Settings and also manually set Navigation Volume when Google Navigator is running]
Audio is fine when any music app playing [with or without cable]
Audio is fine when any Sat Nav voice playing [with or without cable]
Audio is fine when any Sat Nav + any Music app both playing (music cuts out and voice becomes audible) [WITHOUT CABLE]
--- Sat Nav voices becomes too low to hear when both Sat Nav and Music playing with cable plugged in ---
This was working perfectly fine on stock HTC (both Froyo and GB) with kernel Buzz OCUV 1.0.6.
I have only seen this issue since flashing Android Revolution HD 5.1.9 > 5.1.10 > 5.1.11 . I have tried different kernels ( Stock ARHD > UnityV2 > UnityV3 ) and also retried Buzz OCUV 1.0.6 but the issue still remains.
Does anybody have any ideas as to what could be the problem?

Anybody have any ideas at all?
Sent from my Desire HD using XDA App

I've always had this issue too, All I have been doing is lower the music volume to half, set Navigation Volume to Full and then increase the car volume instead
According to google support forum, It looks like the issue is caused by GB 2.3.3, 2.3.2 does not have this problem so it seems downgrading is the only fix.

I have the same exact problem unfortunately.

I'm guessing you're using Google Navigation instead of HTC's Locations Premium Navigation?
I'm currently on 2.3.3, and I don't really have a problem with any bad navigation volumes. If you're not okay with paying to try out Locations Navigation, don't worry, you have a 1 month worldwide navigation license which you can activate and use for free without any restrictions.

Thanks for your 'input' Vious, but the issue remains no matter what satnav is used, premium or not.
It is a confirmed 2.3.3 issue with multiple threads on the google code forums
Sent from my Desire HD using XDA App

I hope they fix this soon. Such a GIGANTIC issue... i can't believe this isn't at all critical for them.

Same problem for me, Copilot support could not fix it for me also, claiming it was a problem with android not them. Used to work on Version 8.x.x.606

If this affects all versions of Android above 2.3.2 then it looks as if I have little choice but to buy an iphone or wp7 phone next, Google are unbelievable sometimes!
6 months and still no fix, I love Android and would hate to switch but this is a complete joke!!!
http://code.google.com/p/cyanogenmod/issues/detail?id=3165
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=794d84c209f5ad2d&hl=en
http://code.google.com/p/android/issues/detail?id=15690

I know this is an old thread, but I wanted to share my solution for this same problem that I've been having since upgrading to the new gingerbread. Note though that this is no longer an issue if you're using the latest google navigation app, but if you're like me and you like to use an offline nav app like CoPilot, then this solution should work for you.
Since this problem was introduced in gingerbread 2.3.3, I thought I would try replacing the libaudiopolicy.so library with one from a gingerbread 2.3.2 rom I had laying around and voila, that seemed to have solved the problem! I haven't tested this thoroughly, but it seems to be working so far. I hope this helps anyone else out there that is still suffering from this issue.

Could you post the file? Also, have you encountered any issues so far?
Perhaps post this in the previously mentioned google code pages for more testers....
Sent from my Desire HD using XDA App

Here you go! This one is for sense based roms.
No issues so far!!
Perhaps when I have a little bit more time, I'll post a link to this thread in those referenced google pages.

hexion said:
Here you go!
No issues so far!!
Perhaps when I have a little bit more time, I'll post a link to this thread in those referenced google pages.
Click to expand...
Click to collapse
Nice one I'll give this a try

I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.

rgrover said:
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
Click to expand...
Click to collapse
Yes, sorry, forgot to mention that. I've updated my post so now it won't confuse anyone else.
I'm glad the one from CM7 worked for you!

hexion said:
I know this is an old thread, but I wanted to share my solution for this same problem that I've been having since upgrading to the new gingerbread. Note though that this is no longer an issue if you're using the latest google navigation app, but if you're like me and you like to use an offline nav app like CoPilot, then this solution should work for you.
Since this problem was introduced in gingerbread 2.3.3, I thought I would try replacing the libaudiopolicy.so library with one from a gingerbread 2.3.2 rom I had laying around and voila, that seemed to have solved the problem! I haven't tested this thoroughly, but it seems to be working so far. I hope this helps anyone else out there that is still suffering from this issue.
Click to expand...
Click to collapse
Thanks hexion, you see this is exactly what I have been trying to say all this time - it must be something slightly changed in some audio file somewhere between 2.3.2 and 2.3.3 . I just have no idea about Linux / Android so never knew where to look for such things.
Now all we need is to compare these to see where the changes lie and try to patch the most current libaudiopolicy.so with only the previous Navigation settings, leaving all other new things as is.

rgrover said:
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
Click to expand...
Click to collapse
Hey rgrover, I'm also on CM7.1 Nightly. I tried renaming old file to libaudiopolicy.so.bak and copied the file you supplied into system/lib but now my device will not load past white HTC screen after reboot. Any advice?
UPDATE: it's OK it seems it was just a permissions problem. Everything working fine now

Hexion, you f**king treat !
My DHD is now pure perfection, with CM7.1 installed and this Sat Nav fix. Everything works at it should and I need nothing else from a phone (apart from battery life, but hopefully I can get Daemon Controller on CM7 at some point with better kernel).
If I had mone I would buy you a bottle JD (actually I would buuy myself one lol, maybe share with you XD )

Apparently, this fix for sat nav apps does not work for Google Navigation and TuneInRadio according to chykal1 on the google page. Music will not be lowered when the nav voice comes on. So if you use TuneInRadio a lot, you probably shouldn't apply this fix. Maybe when someone patches the latest libaudiopolicy.so, then we'll have a true solution.

Gta III on Milestone/Droid

Hey guys, I'm wondering if someone managed to play gta III.
I tried every version: v1.0, v1.1 and v1.2
v1.0 closed after I pushed the "new game"-button
v1.1 and v1.2 stuck at the loadingscreen after I started a new game, the progress bar just doesn't move any more..
thank you for every tip.
edit:
I tested on HO!NO! CM7.1.2

I have gta III v1.2 in my milestone [ROM] iceandfire v4 aka Ultimate Milestone v1.0 Beta1 and i have installed chainfire 3D (REDUCE TEXTURE QUALITY , REDUCE TEXTURE SIZE)... Delete audio folder! Working smooth.

Which data do you use? The one thats automatically downloaded by the app?

I have data from v1.0 automatically downloaded This data working on v1.2

i don't know why i have fc....using latest cm7

app 1.2; data 1.0; no audio folder; chainfire: reduce texture quality + reduce texture size.
cm 7.1.4
freezes after 30sec of gameplay

I ve got this same , on 1ghz OC , deleted audio folder, and cm7 7.1.4

Try my gta 3.set low disatance ,low resolution, low detail. And save 100%. all this files put in gta3 directory.

Even with v1.3 can't get it running. I've the same problems I had with v1.1 and v1.2 your gta 3.set doesn't help me either because I can't get further than to a 3/4 loaded bar.
sry for my bad english, I hope you can understand me
Thank you very much.
In a few days I'll try it with another rom. (still on CM7.1.2-HO!NO!)

L3ibnitZ said:
Even with v1.3 can't get it running. I've the same problems I had with v1.1 and v1.2 your gta 3.set doesn't help me either because I can't get further than to a 3/4 loaded bar.
[...]
Click to expand...
Click to collapse
I have got the same problem here. Trying all the methods mentioned here still does not work ...

I can get it working with latest CM 7 (purge assets enabled, lock home disabled, lock sms disabled)
> Draw distance Low
> Audio folder deleted
> No chainfire
But, the game is slow. And after that the game FC in the middle of the gameplay ?

?
someone has tested the new version of Nadlabak 7.2Rc0 CM7??: Confused:

I have a workin one somewhere on my PC, let me search for ya'll. It worked without deleting anything and without ChainFire, tho it wasn't that smooth. I'll search for it and post a link here as soon as I find that.

Still searching?
Sent from my Milestone using XDA

Doesn't Work At All For me

L3ibnitZ said:
Still searching?
Sent from my Milestone using XDA
Click to expand...
Click to collapse
Sorry just had some technical issues my upper neighbour just flood our kitchen, one of her pipes got broken and all the water comes down to our kitchen where i left my laptop so....lol...but i will post it later today. Sorry once again

GTA3 for Moto Droid? I ran it. 2FPS. Don't bother.
I'd upload it for you stuborn folks that like to see for yourself, but its Illegal so
Not that i care about the law, i care about the rules of this site, wich im certain is against piracy

Bunie89 said:
GTA3 for Moto Droid? I ran it. 2FPS. Don't bother.
I'd upload it for you stuborn folks that like to see for yourself, but its Illegal so
Not that i care about the law, i care about the rules of this site, wich im certain is against piracy
Click to expand...
Click to collapse
Send to my email [email protected]

[help] CM10 g-sensor does not work in games (only in games)

I've got a problem with CM10:
After flashing it every thing is OK...besides g-sensor. NFS (and other games using g-sensor) see the tablet only in vertical position! It happens only in games (menu etc. is OK horizontally). I've found a fix for that but it was for 2.2 and it did not work. I've tried reflashing it, changing auto-rote etc but it also did not work. Please help me.
Can U also tell me if CM9 is better than CM10? I was using it at the beginning but it seemed to be not as good as CM10... Maybe I was wrong and it's good to go back to CM9?