Hello everyone,
This is my first post, but I have been lurking in the shadows. Thank you for everything you guys have done for the Android community.
I am running CM 4.2.1, and after loading some silly SPL from some guide, messed things up, wiped and reflashed. Having done that I installed only a few programs. SAM (SlideMe Application Manager) gives me the following warning.
"WeatherFirst App warning!"
If you have installed WeatherFirst application, there has been a security warning issued. Recommended to remove
The notification remains there all the time. From the limited info available I have concluded it is a botnet, or some variation used for this website: "wunderground.com," which is where I get my weather on my PC and accessed once on Android. The information I found, and the first result on Google is the following:
hxxp://mobilecomputingauthority.com/?p=111 (sorry I cannot post links, so you'll have to copy/paste and change the x's)
I would like to know how to remove it.
Any help is appreciated.
Funkz
WeatherFirst clarification
Hi Funkz. As the author of your referenced blog post at MobileComputingAuthority,I thought I might chime in and help to clarify the post, this app, and ease your fears a bit; at least as far as I understand it.
In the post I said that the WeatherFirst app was a proof-of-concept application demonstrating how users might be tricked into downloading and installing an application that might be malicious. The app uses the GPS receiver to get your current location, then transmits that information to a server. The server then converts the coordinates into a zip code and submits the weather request to wunderground on your behalf. This interaction is itself harmless, but demonstrates that there is an opportunity to do something malicious on the server or to transmit data (GPS coordinates in this example) without your knowledge or consent. I'm unclear about whether the use of the GPS was disclosed or not.
So the gist of this is that the WeatherFirst application is not a malicious application (ie botnet client). The researchers that made it, DID make a malicious version, but that version was never released to the public according to their statements and I don't have any reason to question that.
Hope that helps clarify things and thanks for reading MCA!
Bill
According to Android 1.6 specs the accelerometer should be able to log data at at least 50Hz (see page 18 on android-1.6-cdd.pdf)
However, the GT540 sensor rate - number of times per second you can get the sensor values - seems to be stuck to about 10Hz, i.e. just 10 values are gathered per second.
For programmers, the following lines are not producing any effect when registering the listener:
Code:
registerListener(this, sensorAccelerometer, SensorManager.SENSOR_DELAY_GAME);
registerListener(this, sensorAccelerometer, SensorManager.SENSOR_DELAY_FASTEST);
it seems the default value is stuck to SensorManager.SENSOR_DELAY_UI.
This of course should have impacts on applications using the accelerometer other than for just rotating the UI (pedometer, speedometer, nice games,etc...)
I asked other owners to test the accelerometer and so far all the feedback I received are consistent: the GT540 does ignore any settings and always logs data each 100ms...
Example how to test this bug:
1. install the free AccelerometerValues app from market (it is a single word)
2. click Settings: set Log interval (ms) to 50ms, flag "log values to file" and "file format cvs"
3. start the log for 2-3 secs
4. using Astro go to /sdcard/accelerometervalues and open the log file
You'll should see a line each 50ms but...
Any idea? Any hack to enable a faster rate?
Sensor is a BMA150 and is capable to report data at a rate much greater than Android specs...
gspeex said:
According to Android 1.6 specs the accelerometer should be able to log data at at least 50Hz (see page 18 on android-1.6-cdd.pdf)
However, the GT540 sensor rate - number of times per second you can get the sensor values - seems to be stuck to about 10Hz, i.e. just 10 values are gathered per second.
For programmers, the following lines are not producing any effect when registering the listener:
Code:
registerListener(this, sensorAccelerometer, SensorManager.SENSOR_DELAY_GAME);
registerListener(this, sensorAccelerometer, SensorManager.SENSOR_DELAY_FASTEST);
it seems the default value is stuck to SensorManager.SENSOR_DELAY_UI.
This of course should have impacts on applications using the accelerometer other than for just rotating the UI (pedometer, speedometer, nice games,etc...)
I asked other owners to test the accelerometer and so far all the feedback I received are consistent: the GT540 does ignore any settings and always logs data each 100ms...
Example how to test this bug:
1. install the free AccelerometerValues app from market (it is a single word)
2. click Settings: set Log interval (ms) to 50ms, flag "log values to file" and "file format cvs"
3. start the log for 2-3 secs
4. using Astro go to /sdcard/accelerometervalues and open the log file
You'll should see a line each 50ms but...
Any idea? Any hack to enable a faster rate?
Sensor is a BMA150 and is capable to report data at a rate much greater than Android specs...
Click to expand...
Click to collapse
sorry to say this but sound like bs cuz it works perfectly fine here
RDilus - I would love if this were bs... , can you a try as described above and post the result? Which Android version are you running?
Make sure to set the interval to 50 or 10ms.
Mine looks like:
Code:
Time;X;Y;Z
80;1.253072;1.0215261;9.602345
173;0.9942854;0.7627395;10.528529
275;1.0623871;0.8036005;10.56939
378;0.9942854;0.8308412;10.147159
480;1.1032481;0.6810174;10.378705
583;1.0623871;0.6810174;10.56939
685;1.0215261;0.7218784;10.378705
788;1.0623871;0.7218784;10.2152605
941;1.0623871;0.6810174;10.446807
...
you can see, I get a value each ~100ms (first column is in ms).
Thanks
gspeex said:
RDilus - I would love if this were bs... , can you a try as described above and post the result? Which Android version are you running?
Make sure to set the interval to 50 or 10ms.
Mine looks like:
Code:
Time;X;Y;Z
80;1.253072;1.0215261;9.602345
173;0.9942854;0.7627395;10.528529
275;1.0623871;0.8036005;10.56939
378;0.9942854;0.8308412;10.147159
480;1.1032481;0.6810174;10.378705
583;1.0623871;0.6810174;10.56939
685;1.0215261;0.7218784;10.378705
788;1.0623871;0.7218784;10.2152605
941;1.0623871;0.6810174;10.446807
...
you can see, I get a value each ~100ms (first column is in ms).
Thanks
Click to expand...
Click to collapse
im runing 2.1
and i dont gonna change some values most stupid thing you can do
RDilus you are missing the point, changing the rate is a functionality of the sensor and it should work in that way...
pls. don't spam on this thread if you don't know what it is about...
gspeex said:
RDilus you are missing the point, changing the rate is a functionality of the sensor and it should work in that way...
pls. don't spam on this thread if you don't know what it is about...
Click to expand...
Click to collapse
dont tell me what todo lol....
but it seams ur the only one so...
this can be closed or moved anyway
Well my accelometer works perfect, havent seen any problems nor in games nor in Apps. Not going to try that app to test it tho :]
Since most replies you got are way off base, I'd tell you my findings: yup, stuck at 100ms.
corran, thanks a lot for having done the test, this confirms the issue - stucked at 100ms
m4nu4l, you might not realize the problem until you start to use applications that leverage on the accelerometer in a "fine" way. The current behaviour is ok for just rotating the screen, showing a lever, and maybe for some games. But try to use a speedometer or games that are supposed to detect minor movements: the application would seems to work, you would not realize the issue but just the movement detection is 5-10 times less precise that what it should be according to Android specification.
I wrote to LG and they suggested to upgrade to 2.1 as soon as it is released, but from other users, I got the confirmation it does not seem to solve the problem
gspeex said:
I wrote to LG and they suggested to upgrade to 2.1 as soon as it is released, but from other users, I got the confirmation it does not seem to solve the problem
Click to expand...
Click to collapse
Should've mentioned I'm at 1.6 still also.
As i already told you, games run with my axxelomwter flawlesly (nfs shidft, asphalt series... abduction, i just dont understand how better it could be. I cant seem to notice any lag with it nor 100ms delay. Im using 2.1 afterall ...
If it works a-okay for whatever games is not quite the point of this. Google has, as the TS said, required for vendors to comply with
Accelerometer
Device implementations MUST include a 3-axis accelerometer and MUST be able to deliver events at 50 Hz or greater. The coordinate system used by the accelerometer MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
Click to expand...
Click to collapse
This is taken from 2.1; if the device don't follow the stated requirements you're not complaint - i e apps, games, and whatever can fail or not work correctly. Thus, it is important to adhere to the "standard", else we will end up with what Steve Jobs called fragmentation - developers can't guarantee anything anywhere.
My 2.1 results:
336
444
541
643
746
So, same here.
@corran, you got exactly the point, I couldnt have phrased it better. Thanks for the message
@m4k4ve1icro, thanks for the test.
Our nice LG phone has a flaw that can limit its usage... you might not realize it now but the next android killer app might not work as expected. Actually the application I was interested on can't run since it has too little data from the accelerometer to compute correctly - and that's why I started the investigation and opened this thread.
What's next? I've been opening support requests to LG but they replied to wait and upgrade to 2.1 when available for my country: I already know it is not working. I replied to pass the request to the tech group but the answer was vague- so I'm insisting again...
If you can, pls. do the same: hopefully LG will realize the issue and patch it.
In the meantime I'm going to contact google to raise the non compliance of the device... this might help as well since google can claim access to Android market if a device does not pass the compliance test.
thanks
I read the Nexus had some issues with the AK8973 stepping in to take the accelerometers role, but at least in the LG Eclair sources all the
#define SMB380_BW_25HZ, SMB380_BW_50HZ, SMB380_BW_100HZ, SMB380_BW_190HZ, SMB380_BW_375HZ, SMB380_BW_750HZ, SMB380_BW_1500HZ
Click to expand...
Click to collapse
seem to be were they should. Luckily I don't use the accelerometer in my little projects
Good luck hunting this down!
Hi All,
To anyone out there who may require this information I wrote 2 decent length posts in the Chromecast Reddit around region locked country access and setting up source based routing on DDWRT for VPN of the chromecast device.
***mod edit
I'm unsure if linking to something I've written in a different medium violates any rules so if it does I'm sorry and I'll remove anything as needed.
if anyone has any questions about anything I wrote please feel free to ask - I spent a long time going through different services and networking configurations to set up a number of chromecast devices.
(P.S. as some of you are smarter than myself in areas if you believe I'm mistaken in any knowledge or should add anything please let me know!)
Why not post that information here instead of driving people to reddit?
You may find existing threads for it.
Reposting from where I previously put this, on the suggestion that folks here might have more idea what I am talking about.
Yes, this is a question but I couldn't see that it fit in better to one of the other forums. If I am wrong please accept my apologies and redirect me, thanks.
I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, onTouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi
Hey everyone,
I'm wondering what is everybody doing to stay on top of competing apps and other app market changes? What tools do you use? I've been working on a project to solve this problem and I'd love some input and feedback.
Thanks!
Here are some basicly tools for it: (1)appinner.com, it is an app internal data analysis platform, with it you can find which advertising platform sdk your competitor choose, how does they construt their apps,etc.
(2)flurry. it is a tool to track your apps performance, give you detailed insight in your users count, session length etc. （3）appannie. you can check the keywords and ranking List of apps.
https://sensortower.com is a must check. It will give you very valuable insight on what to do and what not about keywords and rankings (with a pretty cool daily email that reports you all you need to know about your app and his ranking).
As JimmyG20 said too, appannie is a must check too.
4 Simple Ways to Monitor Your Competitor's -
1. Sign up to receive their email or newsletter
2. Explore their website
3. Like and follow on social networks
4. Give them a call.
Useful sources to track
Hey,
These may be:
Sensortower with TOP charts
Appannie - also store stats
Statista sometimes publishes the stats abour certain apps