Need Help: Application Testing for Nexus S - Nexus S Themes and Apps

I had extended the compass sample in the SDK to include the gyroscope. However, as I do not have a Nexus S, I was not able to try it at all.
Would anyone please check that the attached apk works properly in the nexus S for me.
It is a very simple application which does not read/write anything to the phone (just listens to sensors and plots a cube to the screen according to your orientation).
The compass part works properly (i checked it on my phone). I wonder whether it works or not when you toggle to gyroscope by clicking the toggle button on the screen.
I do appreciate any help.

who has balls to test this?
I sure dont
EDIT:
This guy below me does

retigi said:
I had extended the compass sample in the SDK to include the gyroscope. However, as I do not have a Nexus S, I was not able to try it at all.
Would anyone please check that the attached apk works properly in the nexus S for me.
It is a very simple application which does not read/write anything to the phone (just listens to sensors and plots a cube to the screen according to your orientation).
The compass part works properly (i checked it on my phone). I wonder whether it works or not when you toggle to gyroscope by clicking the toggle button on the screen.
I do appreciate any help.
Click to expand...
Click to collapse
Installs and gyro works fine while in landscape/portrait
But if you switch portait to landscape or landscape to portrait, it resets to the accelerometer.
I never realized how twitchy our accelerometer was. The gyroscope is amazing stable in comparison.

Thank you my friend.
You can't imagine how grateful I am.
Thank you very much.
PS: Thanks to your note, I realized that I forgot to disable the orientation in the manifest. (I had disabled it from the settings in my phone. That is why, I could not notice that).

Why does your app want to access Storage and Phone calls?
Also, do you mind trying to test the rotation vector sensor? I tried to do so, but it seems to lock up and turn into NaNs...

retigi said:
Thank you my friend.
You can't imagine how grateful I am.
Thank you very much.
PS: Thanks to your note, I realized that I forgot to disable the orientation in the manifest. (I had disabled it from the settings in my phone. That is why, I could not notice that).
Click to expand...
Click to collapse
Sure thing, let me know if I can be of any further help to ya.

I found this video today
http://www.youtube.com/watch?v=5JQz7EOHAwE
I would like to know what these guys are using to test the gyro on the NS.. Actually I am not sure this app is actually testing the app or the compass / accelorometer.
any ideas?

retigi said:
I had extended the compass sample in the SDK to include the gyroscope. However, as I do not have a Nexus S, I was not able to try it at all.
Would anyone please check that the attached apk works properly in the nexus S for me.
It is a very simple application which does not read/write anything to the phone (just listens to sensors and plots a cube to the screen according to your orientation).
The compass part works properly (i checked it on my phone). I wonder whether it works or not when you toggle to gyroscope by clicking the toggle button on the screen.
I do appreciate any help.
Click to expand...
Click to collapse
Works fine here. When changing the orientation. It resets back to ac c + compass.
Gyro so much smoother
Sent from my Nexus S

as everyone mentioned, its working well on Nexus S!
the gyro working is very fluid! if possible, can you please share the source code? i am mostly interested in how you filtered (low pass filter, kalman filter,etc?) the gyro data and how you mapped the gyro reading to the rotation of the cube? did you use the raw gyro data, or any of the other android function like getRotationMatrix(), get AngleChange(), etc.?

Related

album 3 fixed

Not sure how many people have figured this out, but I thought I would share.
You will need the diamond sensor 2 (sensorsdk 4) and g-config. You will need this to remove a couple apps that don't play well rotated. Camera for one. Install these 2, and you are good to go. Hope this has helped someone.
splxtreme said:
Not sure how many people have figured this out, but I thought I would share.
You will need the diamond sensor 2 (sensorsdk 4) and g-config. You will need this to remove a couple apps that don't play well rotated. Camera for one. Install these 2, and you are good to go. Hope this has helped someone.
Click to expand...
Click to collapse
This does not fix the auto rotation problem with Album 3. The view image still stucked at landscape regardless of the orientation. This seems to be a known problem with version 3. Anyone else confirm this?
I think this is how it is on the Topaz device also. The pictures are automatically rotated to "best fit". This is how I understood it worked.
bmb2n said:
This does not fix the auto rotation problem with Album 3. The view image still stucked at landscape regardless of the orientation. This seems to be a known problem with version 3. Anyone else confirm this?
Click to expand...
Click to collapse
I believe the fix is for zooming while in landscape mode, the picture will do a weird rotation while zooming. Album 3 automatically picks an orientation that best fits the picture, that is the way it was designed. I don't think that is something that could be changed.
dizzyraider said:
I believe the fix is for zooming while in landscape mode, the picture will do a weird rotation while zooming. Album 3 automatically picks an orientation that best fits the picture, that is the way it was designed. I don't think that is something that could be changed.
Click to expand...
Click to collapse
I believe the image is clipped monentary while zooming and it returns to full screen in landscape mode. You need to enable the accelerometer to remedy to problem. Enable auto rotate from Mailina2 also worked for me.
Anyone else has any other idea?

Accelerometer mimicing on Vogue

A while back someone posted some sort of app, or a script of some sort that allowed the Vogue's D pad to mimic the presence of an accelerometer in the phone. Anyone have a link to this still?
TheKartus said:
A while back someone posted some sort of app, or a script of some sort that allowed the Vogue's D pad to mimic the presence of an accelerometer in the phone. Anyone have a link to this still?
Click to expand...
Click to collapse
That was DZO, he wrote a driver for it. seach under his posts. I believe that the sysinit.rc will have to be updated for it as well.
Hey guys, I heard this is added to the present version - how do we access it? Thanks!
touch the screen where you want to 'go'
mrkite38 said:
touch the screen where you want to 'go'
Click to expand...
Click to collapse
Cool thanks, I'm still trying to figure out the Google Sky Map so maybe I just don't understand the app. I'm going to play with it some more - Thanks!
Some of the papi series games from the market still prompt the lack of an accelerometer and I can't seem to do any movements after forcing start but Armadillo roll is working great with the sensors tho.
Another greay game the works well with the sensors is jumpyball 3D

[APP] Photaf 3D Panorama

https://market.android.com/details?id=obg1.PhotafPro
I wanted to notify the Xoom community that I'm working with the author of this application using a unique method of actually making a video clip of what I'm doing with my Xoom so that he can actually watch and see how the device is reacting to his application.
Our results so far in 2 exchanges of e-mail have been to put it simply, outstanding.
First the product worked but with a few minor glitches, and I think that very soon he will update the market with something that is much more "Xoom Friendly".
The primary reason for me to post this thread is not just to let people know "hey there's a cool panorama app out there" but also to let you guys know that if you have an app or something that is not working just right on your Xoom you might be suprised by what a simple polite e-mail request gets you. If you're willing to put out the extra effort, you may even get faster than expected turn around
I purchased Photaf 3D Panorama to use on my Xoom last night. I really like the panorama pictures but for some reason I am forced to take the pictures manually. In “auto mode Photaf takes the first picture than after that I just get the right and left arrows and the second picture is never taken. If I run it in manual mode and just take a picture everytime the box around the thumbnail image turns green it works with no problems.
This is a cool app. I am surprise there is not more people interested in this.
Really cool, now that it have the ThunderBolt I missed that feature from the Fascinated. Thanks
Sent from my Xoom using Tapatalk
dixonwa said:
I purchased Photaf 3D Panorama to use on my Xoom last night. I really like the panorama pictures but for some reason I am forced to take the pictures manually. In “auto mode Photaf takes the first picture than after that I just get the right and left arrows and the second picture is never taken. If I run it in manual mode and just take a picture everytime the box around the thumbnail image turns green it works with no problems.
Click to expand...
Click to collapse
I suspect that has to do with the dev tinkering with it to get it to work. Since I have an open dialog with him I will mention this.
OK we have everything working well in landscape but the dev is having a hard time with portrait I think it has to do with the compass while in portrait. Any developers have input on that?
Sent from my Xoom using XDA Premium App
Thanks for notifying the developer cwizardtx. I updated to the new version in the market today (2.6.3) but I am still having problems with the “Auto” mode. Before the red/green box at the bottom moved as I rotated the device allowing me to take pictures manually but since the update the box no longer moves correctly. The “Box” stays around the first picture then makes huge jumps, no longer moving in sync as I turn the Xoom. If anyone knows if a good screen shot / screen video taking program I will be happy to share my issue if it will help.
dixonwa said:
Thanks for notifying the developer cwizardtx. I updated to the new version in the market today (2.6.3) but I am still having problems with the “Auto” mode. Before the red/green box at the bottom moved as I rotated the device allowing me to take pictures manually but since the update the box no longer moves correctly. The “Box” stays around the first picture then makes huge jumps, no longer moving in sync as I turn the Xoom. If anyone knows if a good screen shot / screen video taking program I will be happy to share my issue if it will help.
Click to expand...
Click to collapse
I'm seeing the same issue
Sent from my Xoom using Tapatalk
I have used this app just a little bit, but I am impressed. Even more impressed that the developer is reaching out to the user base. Kudos!
dixonwa said:
Thanks for notifying the developer cwizardtx. I updated to the new version in the market today (2.6.3) but I am still having problems with the “Auto” mode. Before the red/green box at the bottom moved as I rotated the device allowing me to take pictures manually but since the update the box no longer moves correctly. The “Box” stays around the first picture then makes huge jumps, no longer moving in sync as I turn the Xoom. If anyone knows if a good screen shot / screen video taking program I will be happy to share my issue if it will help.
Click to expand...
Click to collapse
I have a version that may correct that issue but I think he may have already released it. Could you check that you are using version 2.6.4 for me?
Additionally: The only thing that functions "properly" is landscape mode. If you try to shoot anything in portrait mode you need to use manual mode for shooting only because the first shot never fires. We have been working back and forth on it and he feels like it has something to do with the accelerometer in the Tegra 2 chipset and is doing some research on it.
So to recap:
v2.6.4: - Landscape shooting should be working properly but portrait is only manual (and the auto-align preview box does not work at all in portrait, you have to wing it).
That all said - ALL functions work 100% properly on my Nexus One, so this is definately a device issue but we are working on it!
PS: I say "we" very loosely because I have no access to any source code or anything like that, I am simply making videos and screenshots and emailing him back and forth with testing and stuff as he sends me builds.
jvs60 said:
I'm seeing the same issue
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
I suspect that all of us will have identical issues and successes if we're using the same version
If anyone happens to know any of the particulars in regards to handling landscape and portrait on the Xoom feel free to chime in.
I have the current market version 2.6.3
I have installed this on my evo also, works great on it.
I've subscribed to this thread, please post when he's got all the kinks worked out and it's XOOM optimized. I will definitely buy it then
v2.6.5 is released
What I see:
- Bigger buttons on the Xoom
- Automatic shooting in landscape is corrected
- Automatic shooting in portrait is not working properly and needs to be done manually
v2.6.5 is released
What I see:
- Bigger buttons on the Xoom
- Automatic shooting in landscape is corrected
- Automatic shooting in portrait is not working properly and needs to be done manually
Tried this again today after the updates, wow, this is a nice app! Very easy to use. Auto mode works great! I am impressed.
Cool, I wish I knew more about coding and how the accelerometer worked to help the guy out.
Same here; did the update today and everything working good now. Thanks for your help Cwizardtx
The developer of Photaf 3D Panorama emailed me today, he finally got his hands on a honeycomb tablet (an Asus but if it fixes the app I dont care) and finally squashed the last really annoying bug: Automatic picture taking in portrait mode. Works like a champ now, compass orientation is fixed and the app rocks

[Update]Proximity Fix for Kexec Kernels! - All Sensors

First things first, I'd like to wish you all hello, as this is my first post here and to XDA in general.
That being said, after getting much out of XDA over the years I figured I would try to give something back while experimenting with android!
I give you..
Droid 3 Custom Sensors Module
This enables/fixes our proximity sensor on hashcode's awesome kexec kernel so the phone screen blanks during calls!
The issue is with the sensors.solana.so proprietary library that comes with our phones from motorola.
So I compiled for us a new sensors.solana.so to use which is compatible with Kexec kernels.
Note: This library only controls accerometer sensor, light/prox sensor and orientation/magnet sensor so theoretically it should work the same, just with proximity working. But without more use I can't be sure.
Also in theory this should work for any flavor of Kexec releases, but I can only confirm cm10 currently...
Update[12/13/12]:
-Akm module is now working (Magnetic Field sensor / compass)
-Why is this useful?
Google maps should work better in terms of orientation
Compass apps should work now, along with any others that use rotation vector
-This required a driver edit to get it pointing in the right direction, so v2 includes newest hashcode kernel with the edit. i sent the code to hashcode, so hopefully if he incorporates these changes then this will no longer be needed.
Installation:
1. Download Custom-SolanaModule-v2[Kexec].zip
2. Install it like any other zip in ss3
Removal:
2. Download Stock-SolanaModule [Kexec].zip
2. Install it like any other zip in ss3
More Notes:
Attached also is the source code I used. I cannot claim writing most of it, as its more of a collaboration of various files that I found online for our sensors with a couple various tweaks.
Edit[12/13/2012] For anyone looking to implement this, just unzip v2 source code into root directory of your repo, files should go where needed.
Obviously a big shoutout/thanks to Hashcode/dhacker/jonpry and everyone else that got our D3's to the place they are now. This is just one more step in the right direction hopefully.
Thanks dudeeeee!! Someone should pm this to hash! It's great!
Enviado desde mi DROID3 usando Tapatalk 2
Confirmed. Good work.
Sent from my XT862 using xda app-developers app
Nice, one step closer.
Who twittered Hash?
I tweetered.
Thank you Jarveson!
I'll get this into new builds w/ a credit to you for getting this together.
Sweet! Good to hear that it works for you guys also! Ill try to see if I can get magnet and orientation working when I get some more free time.
Also, Thanks Hash! I forgot to say that it would be awesome if you were able to incorporate this in your new builds, it was really late/early when I typed that up initially
jarveson said:
Sweet! Good to hear that it works for you guys also! Ill try to see if I can get magnet and orientation working when I get some more free time.
Click to expand...
Click to collapse
Orientation is already working not sure about magnet
DoubleYouPee said:
Orientation is already working not sure about magnet
Click to expand...
Click to collapse
Is the magnet the way the dock is detected? If so, it's working. Both my car and home dock are detected that the appropriate app (CarHome Ultra or Bedside) are launched.
hm, I dont believe orientation and magnetometer sensors work, at least not fully, here's why
If you download for example android sensor toolbox or elixir 2 you can go to sensors and see that magnetometer isn't reporting anything, which orientation relies on, which the rotation vector relies on. Unless i completely screwed up my test build ive been using :/
djbolden said:
Is the magnet the way the dock is detected? If so, it's working. Both my car and home dock are detected that the appropriate app (CarHome Ultra or Bedside) are launched.
Click to expand...
Click to collapse
Thats actually really interesting, but it might be that there is a separate magnet relay/switch used for docks
I almost have them working, issue currently is getting the compass to flop its yaw values, some reason magnetmeter x and y is swapped. Fairly certain its going to require a kernel/driver patch
jarveson said:
hm, I dont believe orientation and magnetometer sensors work, at least not fully, here's why
If you download for example android sensor toolbox or elixir 2 you can go to sensors and see that magnetometer isn't reporting anything, which orientation relies on, which the rotation vector relies on. Unless i completely screwed up my test build ive been using :/
Thats actually really interesting, but it might be that there is a separate magnet relay/switch used for docks
I almost have them working, issue currently is getting the compass to flop its yaw values, some reason magnetmeter x and y is swapped. Fairly certain its going to require a kernel/driver patch
Click to expand...
Click to collapse
Well, when I tick auto-rotation it works for me on CM10. But yeah the magnet might be broken.
I do want to add that the qwerty landscape/portrait mode is buggy. When I open my keyboard sometimes it's still in portrait mode.
DoubleYouPee said:
Well, when I tick auto-rotation it works for me on CM10. But yeah the magnet might be broken.
I do want to add that the qwerty landscape/portrait mode is buggy. When I open my keyboard sometimes it's still in portrait mode.
Click to expand...
Click to collapse
Oh yes, that mode uses the acceleration sensor, which shows how tilted the phone is. Think of orientation sensor more of a compass.
I dont think ive experienced the issue you are talking about, I know some apps dont flip when you open the keyboard, but thats the app. Any specific times it does it ?
jarveson said:
Oh yes, that mode uses the acceleration sensor, which shows how tilted the phone is. Think of orientation sensor more of a compass.
I dont think ive experienced the issue you are talking about, I know some apps dont flip when you open the keyboard, but thats the app. Any specific times it does it ?
Click to expand...
Click to collapse
Ye sometimes when I wake the screen it's in landscape. Or other way around when I open the keyboard it doesn't wake. If I then press a key it wakes but is still in portrait.
Btw, I also need to reapply auto brightness occasionally because it doesn't stick to my custom light sensor settings. But that might be some bug because the sensor itself works fine
Oh, thanks for the work btw. Only camera "sensor" left now
Ok, i can see the magnet works now in GPS toolbox, thanks!
I should've mentioned that I'm not using auto-rotate - so the problem I described is probably not related to these sensors.
It seems that sometimes, it doesn't recoqnize that the QWERTY keyboard got closed or got opened, and therefore it sticks the either landscape or portrait.
This doesn't happen in GB, so it's not a hardware fault on the slide mechanism.
What is libsensors? and do I need to install libsensors to use your custom proximity sensor?
Own Demon said:
What is libsensors? and do I need to install libsensors to use your custom proximity sensor?
Click to expand...
Click to collapse
Libsensors in a nutshell is basically a translation library that takes readings from some various sensors on your phone and translates it into android events.
Any recent cm10/cm10.1 build should have all this built in at this point so manually installing this isnt needed anymore
jarveson said:
Libsensors in a nutshell is basically a translation library that takes readings from some various sensors on your phone and translates it into android events.
Any recent cm10/cm10.1 build should have all this built in at this point so manually installing this isnt needed anymore
Click to expand...
Click to collapse
Thanks for the information. But I think yesterday or day before yesterday hash himself said that he will include all these addition in his next build( If I read carefully).
Own Demon said:
Thanks for the information. But I think yesterday or day before yesterday hash himself said that he will include all these addition in his next build( If I read carefully).
Click to expand...
Click to collapse
Coming after the 1/23 nightlies or do we know when?
Well actually i think nxt build well include this.
Sent from my XT862 using xda app-developers app

[Q] Fix or workaround for QR-scanning issue (SlimKat))

Hello you guys,
I've been using SlimKat on the p880 for a while now, and I really like it. The four latest builds (current build: 6.9) had one big (at least for me) problem, though. Regardless of the QR-code reader I use, no QR- or barcodes are detected!
On screen, the codes look sharp and focused. I tried different settings (auto-rotation, camera light, etc.) and different codes. Video recording works fine, by the way.
Is there any way to fix this without abandoning SlimKat?
Thx,
hmpfz
hmpfz said:
Hello you guys,
I've been using SlimKat on the p880 for a while now, and I really like it. The four latest builds (current build: 6.9) had one big (at least for me) problem, though. Regardless of the QR-code reader I use, no QR- or barcodes are detected!
On screen, the codes look sharp and focused. I tried different settings (auto-rotation, camera light, etc.) and different codes. Video recording works fine, by the way.
Is there any way to fix this without abandoning SlimKat?
Thx,
hmpfz
Click to expand...
Click to collapse
take a picture, and scan from picture. that should work afaik.
its the grouper blobs that are causing the issue, if you're interested.
Flying_Bear said:
take a picture, and scan from picture. that should work afaik.
its the grouper blobs that are causing the issue, if you're interested.
Click to expand...
Click to collapse
Thanks a lot!
Sadly, this workaround is not always an option. Threema, for example, uses qr-codes for contact verification and needs a live image for it...
There is no other way for roms based on grouper blobs, unfortunately. You can always try another rom based on official cm11 sources
I actually managed to scan the barcode, using these steps ;
Force closed the app
Wiped data
Scanned barcode (no success)
Force close
Scanned barcode (success)
But it rarely works even with these steps and I have no idea if steps above even help, but it worked twice for me.
@Flying_Bear
Is neoreader capable of doing that, if not what scanner do you recommend? Thanks in advance
ottomanhero said:
I actually managed to scan the barcode, using these steps ;
Force closed the app
Wiped data
Scanned barcode (no success)
Force close
Scanned barcode (success)
But it rarely works even with these steps and I have no idea if steps above even help, but it worked twice for me.
@Flying_Bear
Is neoreader capable of doing that, if not what scanner do you recommend? Thanks in advance
Click to expand...
Click to collapse
i'll check out which one supports it, but i think qr barcode scanner (https://play.google.com/store/apps/details?id=appinventor.ai_progetto2003.SCAN&hl=en) should be able to do it.

Categories

Resources