mobimaks / stardroid Goto Github PK

In the provider/ephemeris folder there's file called :wq
Just mentioning it to keep things tidy.

Regards

If target device has Google Sky Map installed, ADB will fail to install 
Stardroid APK because of a INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES error.

Workaround is to uninstall Google Sky Map, however the Market will think that 
Google Sky Map is installed once the Stardroid APK is uploaded to the target 
device.

Didn't know if this should be changed in the source tree, or if it should be 
left as an exercise for the user?

Compiling with:
  -IntelliJ IDEA 11.0.1
  -Android 2.3.3 platform
  -JDK 1.6.0_29
  -stardroid-read-only SVN source from 1/20/2012

I really love SkyMap. Thanks to the developers for developing such a nice app.

This is no bug but a feature request. At the moment SkyMap can be used on 
devices without compass only in manual mode. In auto mode changing the back 
azimuth is not possible.

Still the acceleration sensor should provide enough information to align the 
screen to the pointing direction, even without compass. It just has to be 
aligned once which could be done in the manual mode. It would be nice if there 
was an option to enable such a feature. This option could also be automatically 
enabled if no compass is detected.

If you think this is not feasible feel free to close the request.

Suspect Path:

stardroid\trunk\app\src\com\google\android\stardroid\provider\ephemeris\.svn\tmp
\text-base\:wq.svn-base':

When running tests, both on Eclipse or on terminal, the testPositions test at 
RaDecTest.java yields an AssertionFailedError.

Here's the trace:
junit.framework.AssertionFailedError: expected:<173.25> but 
was:<172.99676513671875>
at 
com.google.android.stardroid.test.units.RaDecTest.testPositions(RaDecTest.java:7
7)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at 
android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:52
0)
at 
android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)

I tried to correct it, but I can't understand what the problem really is, since 
it is related to the planet's position.

Thanks for your help!

Basically i am missing any helper functions that will map a touch event's 
coordinates to an actual object.
Or am i just missing something?

The best place to go for it should be DynamicStarMapActivity.onTouchEvent(...) 
to get the click coordinates and then find which object maps to the touch event 
coordinates in the skyView GLSurfaceView. But i'm just unable to find any 
functions that might help here.

Any ideas?

Greets

What steps will reproduce the problem?
1. Enable auto mode to use compass and accelerometer
2. Position the phone to point directly east (or west)
3. Slowly move the phone straightly up toward Zenith (you can also put it on a 
table in landscape mode when moving to make sure your hands are not shaking)

What is the expected output? What do you see instead?

I expect to see smooth upward moving of the map. Instead of that I am getting 
upward movement + some small left and right shaking. 
The issue is not present if I am doing the same thing while looking north or 
south.

What version of the product are you using? On what operating system?

I am using the latest version from the source repository, revision 7.

Please provide any additional information below.

The current location does not seem to matter, I tried to manually set 0 
latitude and 0 longitude and the issue is still present. 
The issue also reproduces if you are looking east (or west) an go down towards 
Nadir in a straight line. But is OK with north and south.

Any idea were this shaking might come from?

I was able to reproduce this on a HTC Nexus One and a Samsung Galaxy S1.

Best regards,
Cristian

This is more of an enhancement request :) It would be nice if somebody could 
work on improving tracking by using the gyroscope in devices where it's 
available or a more complicated predictive filter (Kalman?)

What steps will reproduce the problem?
1.  Error when trying to build the source projet
2.  Message error "The import com.google.android.stardroid.R cannot be resolved"

What is the expected output? What do you see instead?
When trying to build the source project I got a message error when trying to 
import the class "com.google.android.stardroid.R"

What version of the product are you using? On what operating system?
android:versionCode="1112" android:versionName="1.6.4"

Please provide any additional information below.
I search through the project libraries and I didn't find the class 
"com.google.android.stardroid.R"

On my tablet the (north-south-) orientation sensor does not seem to work very 
well, independent from the direction I move the tablet to, the displayed star 
map does not change. Moving it up and down works. Means I always look to north, 
also when I rotate the tablet.

So I'd like to see an option where the sensor can be disabled completely and 
the user is able to move the displayed star map by dragging it manually.

Beside the effect that the ap could be used with some devices that have 
problems with the sensor, it would be easier to just to deposit the table 
without losing the current view (useful when one wants to have a look into the 
telescope in between).

With the current code, everything works after building with ant clean debug.

But if I make two additions to app/res/values/strings.xml, something gets 
weirdly corrupted.

Specifically, I added license and license_title test strings close to the 
beginning as follows:


    <string name="app_name" translation_description="Application Title">Sky Map</string>
    <string name="license_title">This is a
quick test</string>
    <string name="license">This is a quick test
license</string>
    <string name="menu_settings">Settings</string>


Then some of the app data gets corrupted.  One example problem can be seen as 
follows: Menu | Gallery | Omega Centauri | Find in sky.  Result: not found!  
(In other testing, I had other results, such as its showing Omega Centauri in 
the wrong part of the sky, near the Big Dipper.)


I don't know if it's some subtle bug somewhere in the code, or something wrong 
with my build environment.

Several bugs fixed

When ApplicationConstants.INITIAL_SOUTH and INITIAL_DOWN are being assigned to 
variables, this leads to these constants getting modified by the code.  
Wherever the constants are assigned to variables, there needs to be a .copy().

What steps will reproduce the problem?
1. Click on the search option
2. Start to type what you want to search

What is the expected output? What do you see instead?

A search box with a reasonable size and results that we could be possible to 
read.

What I see is a really small search box (where nothing that I type can be 
viewed) and a very small suggestion list below (that I also can't read).
See the attached screenshot for a search after typing "es"

What version of the product are you using? On what operating system?

Version 1.6.4
Android version is 4.0.4

It would be great to have an interface to computerized telescopes such as Meade 
Autostar. Just long press an object and the telescope will slew like in 
Stellarium.

Is it possible? If yes:

Connection will be made via Bluetooth Serial-Port-Profile.

I'm new to Android-development and java in general, so i don't know exactly 
where to implement this feature, but I can test/debug with my telescope.

I would like to be able to track the ISS using this application. Given that the 
moon exits, I take it is possible to add earth-orbiting stellar objects to the 
list of objects in the app.

What steps will reproduce the problem?
1. Install Sky Map on a device where the current language is not English  and 
for which there is a Sky Map translation available (e.g. Dutch)
2. Search for a constellation using its commonly known name (e.g.Sagittarius)
3. You get back 'No results found'

What is the expected output? What do you see instead?

You expect it to find the constellation. If you search for it using its Dutch 
name (Boogschutter), it finds the constellation (and Sagittarius is displayed 
in brackets after Boogschutter!!)

What version of the product are you using? On what operating system?
Google Sky Map version 1.6.4
Android 4.4.4

(This is my first post to code.google - please let me know if there is a better 
place to talk about these)

During time-travel in manual-mode, it is useful to fix the horizon and let the 
stars (and others) move in the background. This gives me an idea of what to 
expect(over time)in a certain section of the sky from where I am currently 
stationed.

I have made a very small change - locally - to AstronomerModelImpl for this 
feature and is working neatly. Also added a toggle for this feature in the 
menus.

P.S: I have a few other such code changes and enhancement requests - but I am 
not sure what the exact process is for getting these changes reviewed and 
submitting them. Could the project owners or someone else provide some 
direction?

Thanks!

Hi there,
if I change the date (both in the past or the future), search for a planet, 
then get back to current date, search directions get wrong

To reproduce:
1. Use the time machine to select a date (in the past or the future, it's the 
same outcome)
2. Search for an object (I searched Mars). The directions are right
3. Set back the time to "now"
4. The circle is still present, but following the directions will bring 
nowhere. Additionally, when approaching the supposed target, the arrow changes 
direction.

I'm running version 1.6.4 on a HTC Desire S phone

This is a feature request from an OEM who ships non-GPS Android device.

Sky Map uses ACCESS_FINE_LOCATION permission and it implies 
android.hardware.location.gps feature.
Thus this app is not shown in Android Market on their device because of Market 
feature filtering.
http://developer.android.com/guide/topics/manifest/uses-feature-element.html#per
missions

They want us to set android:required="false" so user can download the app from 
Android Market.

What steps will reproduce the problem?
1. Menu > Search > Centaurus
2. Go to Centaurus, you will find Rigel in Centaurus
3.

What is the expected output? What do you see instead?
The Rigel should be Riger Kenttaurus or Alpha Centauri

What version of the product are you using? On what operating system?
1.6.4

Please provide any additional information below.
The Chinese name is "南门二"

Not really an issue, sorry, but you might be able to help anyway.

What i'm trying to achieve is to check whether an object is above or below the 
horizon.

But i'm totally stuck here... How am i supposed to get the "position" of the 
horizon?

Goddchen

I believe two major issues are holding back the advancement of this app by 
others in the community:

1.  SVN versioning - not very friendly to collaborative work.  Patch submission 
review process is time consuming.
2.  Lack of social integration / loose coupling with various forks of the 
project - again, not easy to review / merge patches upstream given SVN and the 
current hosting on Google Code.  Also, not easy for one fork to merge 
changes/improvements from other forks, both because of SVN, and because if 
someone transitioned the project to Git, the repos aren't likely to have the 
same history.  As a result everyone starts from scratch when trying to update 
this project.

I think transitioning to Git and hosting the project on Github would help solve 
both of the above problems.  It would give the community a solid root project 
to fork and expand upon, and would also make it simpler (for both the current 
project maintainers and contributors) to submit improvements back upstream to 
this main project, and for one fork to merge improvements from other forks.

I've helped transition a few projects from SVN to Git/Github (including 
retaining the history), and I'd be willing to help with this process if needed.