Related
Location Aware is an automatic volume profile switcher.
This application works out of the data received from GSM signals.(NO CDMA)
so almost all windows mobile devices can use it.I developed it on my elf and it seems it is working
Requires GSM network, Windows Mobile , .Net CF 3.5
1. Battery Friendly, No active background process.
2. No GPS needed.
3. User configurable interval to check for location.
4. Can save settings automatically v0.3
Well it works like this: (May change per version)
1. Install it.
2. Open the Location Aware(from programs)
3. When ever you start the app it will vibrate the device 2 times and then asks "Add this Location".
4. Click OK and it prompts to save the volume level for this location and save.
5. Adjust the volume level as you desire from the Slider on right hand side of screen.
6. Then goto Menu and Save Location Mode, this should save the setting for this location(Prompt will be displayed).
7. Now you can let the application run itself every X mins to check for new location and prompt you whenever a new location is found.
8. To set the interval time goto Menu -> "Stopped" this should open up a panel to enter the interval time, fill it and click set. "Stopped" should be changed to "Running". Now you can Exit.
9. If prompt is not dismissed or OKayed within 1 min(Automode). It dismisses itself and will prompt again if new location is found after next X mins.
10. The limit for interval is 2-60 mins, that means the app will run itself after every X mins and check for location, if a new location is found it vibrates
and then asks you to save this location or not, in case you dont respond to it, it will close itself after 1 min.
and in case the location was already saved it will automatically apply the volume profile.
Basically as you keep on using it the database keeps on growing and in parallel profile settings gets more customized.
PS: You may notice that the taskbar volume indicator is not changed, but that is normal. The volume setting is still applied as per your choice this issue is fixed in v0.3
V0.2
1. No alert popup will be displayed to inform select n save the location.
2. Save the location mode directly by clicking the volume level image.
v0.3
1. Reflect the volume level changes in the taskbar volume icon
2. New mode added "AutoSave", enabling it makes the app save new location automatically with the last volume preference, whenever a new location is found.
PS. AutoSave mode works in Scheduled mode, if you have set the app to run after a scheduled interval with autosave mode enabled and it detects a new location it will prompt a message-box, if you don't give it a response i.e ignore it, it will add the location automatically after 1 min and will dismiss itself.
for users of previous versions:
It will use the already existing database of location settings, just install it over the previous version.
PCBuddy
This app is used to plot all the collected points by the location aware app on google maps.
Unzip the files and then copy the locations.db file from your device to the same folder on your system. Once the file has been copied Run CreateMap.exe this should generate a html file in the same folder. Run that and see for yourself
Please replace the dll in PCBuddy with the one in 64Bit.zip in case you are using a 64Bit Windows
Suggested setting:
For the first time I suggest to keep the interval at around 5 mins so that it can grab almost all the desired locations. once you feel it is having settings for your daily use u may turn the interval to a higher(suggested 15 mins) so that it can apply the volume settings for the known locations.
SUPPORT LATE NIGHTS- DONATE!
No comments???
Great idea !
By using GSM signal to get your position you avoid to use the gps which take more time to get position + a little battery consumption.
We certainly can find a lot of functions linked to this automatic profile/location system
I will try your app
Vesperial said:
Great idea !
By using GSM signal to get your position you avoid to use the gps which take more time to get position + a little battery consumption.
We certainly can find a lot of functions linked to this automatic profile/location system
I will try your app
Click to expand...
Click to collapse
Thanks Vesperial, hope it works out fine
Hmmm
hmmm and I thought this was useful
it is a nice idea
but as a nice addon it would be cool, if it would be possible to add names for specific cell id locations and if the app would be a today plugin
diboze said:
it is a nice idea
but as a nice addon it would be cool, if it would be possible to add names for specific cell id locations and if the app would be a today plugin
Click to expand...
Click to collapse
thanks diboze,
well your ideas are nice but since i want to keep the user inputs to minimum i went on this way and about making it a today plugin...hmm i m not sure how to do that with a C# app
but suggestions are always welcome
Great Concept!!!!
Just saw your P.S. that the volume icon will not change accordingly...but it works as intended. (Please Fix) Is there a radius on the set locations? I work across the street from our main mall, is why I ask.
I love this concept as I saw the other O.S. had a similar app. (Sweet Dreams)
~PLUR~ Peace Love Unity Respect
~DJyoSNOW~
djyosnow said:
Just saw your P.S. that the volume icon will not change accordingly...but it works as intended. (Please Fix) Is there a radius on the set locations? I work across the street from our main mall, is why I ask.
I love this concept as I saw the other O.S. had a similar app. (Sweet Dreams)
~PLUR~ Peace Love Unity Respect
~DJyoSNOW~
Click to expand...
Click to collapse
Hi djyosnow,
understood your concerns about the radius thing but thaz not in myhands as that thing is dependent on lot of factors like, your disance from tower, signal strength etc. But still you may experiment if you get new location alert in case you are at your office.
n yes this is really nice ~PLUR~
Peace Love Unity Respect
Very good application, specially like me who travel a lot from office to client to mall and to our factory
I will give my comment after i use it...
devya said:
Very good application, specially like me who travel a lot from office to client to mall and to our factory
I will give my comment after i use it...
Click to expand...
Click to collapse
Sure will wait for your inputs. n hope you find it useful
v0.2 Out
Some modification in GUI and user interaction
Re mohitsapru,
i tested your app on my HD, it worked well
I have one suggestion to ease the way we can use it, an option like 'Save the actual sound profile automatically when a new unknown position is found'
Then we can move without thinking about it but it will be good as an enabled/disabled option.
Good job !
Vesperial said:
Re mohitsapru,
i tested your app on my HD, it worked well
I have one suggestion to ease the way we can use it, an option like 'Save the actual sound profile automatically when a new unknown position is found'
Then we can move without thinking about it but it will be good as an enabled/disabled option.
Good job !
Click to expand...
Click to collapse
Thanks Vesperial,
well about your suggestion it sounds good. right now it is dismissing it after 1 min i need to save the location automatically.. hmm sounds OK... will do it next time.
Thanks,
Mohit
Does this app able to detect the change of location if the device switched off(suspended) by power button?
For example:
1. Save volume setting at location A and location B
2. At location A, press power button to turn off the device
3. Move the device from location A to location B
4. Will the volume be changed automatically (without turning on the device) at location B?
ahlok_hk said:
Does this app able to detect the change of location if the device switched off(suspended) by power button?
For example:
1. Save volume setting at location A and location B
2. At location A, press power button to turn off the device
3. Move the device from location A to location B
4. Will the volume be changed automatically (without turning on the device) at location B?
Click to expand...
Click to collapse
Yes, it does. But dont forget to exit whenever you save a location setting
hey there,
this looks brilliant! ill try this out tomorrow!
thanks a lot
MG
MysticGenius said:
hey there,
this looks brilliant! ill try this out tomorrow!
thanks a lot
MG
Click to expand...
Click to collapse
Thanks MG,
Do let me know of your suggestions and experience using it.
Thanks,
Mohit
I have run it on my Samsung I900 Omnia and i think it works perfect.
But here some ideas:
It would be great if you can add 2 or more cells to 1 location (Because i have here to cells at home, and if I use UMTS 3G i had another one)
If you write the cell id a little bit greater.
And expert mode were you add name for cells (i see this wish earlier here, too), and can add more things.
Dtrieb said:
I have run it on my Samsung I900 Omnia and i think it works perfect.
But here some ideas:
It would be great if you can add 2 or more cells to 1 location (Because i have here to cells at home, and if I use UMTS 3G i had another one)
If you write the cell id a little bit greater.
And expert mode were you add name for cells (i see this wish earlier here, too), and can add more things.
Click to expand...
Click to collapse
Hi Dtrieb,
Thanks for trying it out.
Well i will think about the other two options/suggestions but i am not able to get what you meant by the first suggestion Which 2 cells are you referring to?
Check out my free app in the Marketplace: AppFinder
AppFinder is the fastest way to find apps by name bar none.
Start typing the name of an app or publisher, and the search results are shown instantly.
tap one of the results to go to the marketplace page for the app.
Check it out and let me know what you think
Been using it last couple days, its a big help! Thanks!!!
I'll check it out thanks!
Thank you - it's very fast like the marketplace search should be. Good for quick looking apps if you know the name.
Are there any improvements coming? Like the Top Downloads or anything else?
appfinder feedback
thanks for the feedback - I'm on it
Great app, thanks!
BTW I can't find HTC Hub...
I think you need an HTC device for that sorry buddy
zukа said:
I think you need an HTC device for that sorry buddy
Click to expand...
Click to collapse
Yeah but some guys were able to find it...
AppFinder
Ok, v1.1 has been submitted to the app marketplace and is ready for testing - should show up in the marketplace as an update within a few days
ebadger said:
Ok, v1.1 has been submitted to the app marketplace and is ready for testing - should show up in the marketplace as an update within a few days
Click to expand...
Click to collapse
does this fix the crash where it closed and wouldn't reopen for me (even after soft reset)?
I had to uninstall, reinstall to get it working again.
I don't think so.
Although I think I know the cause. I will have to roll the fix into another update.
I think there is a small window where the downloaded data file can be corrupted if the writing to flash is interrupted. It will be simple to fix. For now, if you hit it, uninstall reinstall is the only option.
nice find. but did you know while in maketplace you can use the search button to find apps as well?
jimecm said:
nice find. but did you know while in maketplace you can use the search button to find apps as well?
Click to expand...
Click to collapse
Of course I do
AppFinder is all about making apps discoverable in the fastest way possible.
I think if you're not in the top 20 apps in the marketplace under any one of the categories, then as a developer you're invisible. AppFinder seeks to make it easier to find apps via search, and with the update, via browsing as well.
Update is in the hopper, still waiting for testing to complete...
jimecm said:
nice find. but did you know while in maketplace you can use the search button to find apps as well?
Click to expand...
Click to collapse
the annoying thing is that it searches music and video as well. i can't just search for apps alone
locales
Ok, so I just figured out I've only been indexing the en-US locale
I've updated the data to include
{ "en-US", "en-GB", "en-IE", "en-CA", "en-IN", "en-AU", "en-HK", "en-SG", "de-DE", "fr-FR", "fr-BE", "de-AT", "de-CH", "it-IT", "en-NZ", "es-ES", "es-MX" };
this change is effective immediately as it is a data update. Still waiting for the update to make it through the approval process. It seems that the holiday has slowed things down a bit
The update finally arrived
Nice new features and still very fast. But unfortunately, in my case, it wont load after the second app start (even at first start if I switch the section). I always have to deinstall/reinstall again once the app was started.
Maybe you can take a look? Feels like a caching problem or something like that. I'm using a Samsung Omnia 7 in germany - if that helps
Feature wishlist:
1. add a settings screen to edit:
a.) the number of list entries on one page (10, 20, 50) to keep the app fast enough
b.) the section on loading (and maybe you also can set this to no section just for fast look-up app search - I used the app for this before the update)
2. Maybe you can use the OS-typical "left-to-right-scrolling-loading-dots" instead of the big ones?
3. New logo if there is enough time
PrivateJoker said:
The update finally arrived
Nice new features and still very fast. But unfortunately, in my case, it wont load after the second app start (even at first start if I switch the section). I always have to deinstall/reinstall again once the app was started.
Maybe you can take a look? Feels like a caching problem or something like that. I'm using a Samsung Omnia 7 in germany - if that helps
Feature wishlist:
1. add a settings screen to edit:
a.) the number of list entries on one page (10, 20, 50) to keep the app fast enough
b.) the section on loading (and maybe you also can set this to no section just for fast look-up app search - I used the app for this before the update)
2. Maybe you can use the OS-typical "left-to-right-scrolling-loading-dots" instead of the big ones?
3. New logo if there is enough time
Click to expand...
Click to collapse
Private Joker,
Thanks for the feedback.
First - there was a bug that only impacted the German locale! I was trying to save bandwidth by truncating unnecessary leading zeros in the price and this caused an exception when the locale was set to German. I've updated the data to include the leading zeros and this fixes the problem for Germans. You will have to uninstall and reinstall though to get it to work. I am very sorry for the inconvenience, and I really appreciate you taking the time to give me your feedback even though the app was not working for you at all. I hope you will try again given that the data has been fixed.
Regarding your feedback -
I think you are right on the mark for #2 and #3
I don't understand 2b.
regarding 1a.
perf should not be impacted by the number of items that are shown -
Appfinder actually transfers the marketplace data to the device and indexes it locally. I do this because the network is really, really slow. Aside from having artists and albums mixed up with apps in the marketplace search results, I also was tired of waiting for results to load. Scrolling through the apps means waiting.
The delay at the beginning is caused by reading the marketplace data from flash and indexing it in RAM. Occasionally the loading dots will appear after launching (like the first time that you use it) because AppFinder has transfered a new data file and needs to parse it again. Instead of delaying every 10 or so apps in the list, there is one delay at the beginning (which is relatively small). Right now parsing the file takes about 4 seconds.
Perf could be greatly improve if I had access to memory mapped file APIs. Further compressing the data would help as well - The really slowest part is really reading from the flash. I can improve perf when a network update occurs by reading from the flash in the background before blocking - this would drop the update delay from ~4 seconds to ~1 second.
I could also not query as you're typing -- Waiting until the enter button has been pressed would reduce CPU load and any chunkiness - pressing search would just render the apps instantly.
Anyway, really appreciate your positive attitude and willingness to give feedback in light of what must be a frustrating experience. Please give it another try.
Thanks,
Eric
I found solution for LiveView connection issues and had it posted in Sony Ericsson LiveView™ Issues Thread on xda-forum.com . Unfortunately it hasn't been noticed by users untill now that it has been ripped from this forum and posted on www.robot-home.it on 30th December(http://www.robot-home.it/blog/2010/...i-comunicazione-e-al-blocco-dello-smartphone/) but as their own invention what made me really furious (Luckly it was corrected). It took me time to figure it out.
Link to original post form 23rd December: http://forum.xda-developers.com/showpost.php?p=10025306&postcount=190
This is the solution:
First of all delete LiveWare Manager, which causes our phones to crash all the time, and gives only one feature in return (shows all available liveview plugins which you can find manualy in the market). Then remove any kind
of Task Killer etc. Next step is to instal MinfreeManager (keep in mind that it requires root premissions). I recommend using Mild/Agressive preset but you have to change Secondary Server values very low (for example 6mb). By setting Secondary Server values to very low LiveView Application and all of the plugins will be kept alive all the time, which will prevent any disconnections. After this I used this solution http://forum.xda-developers.com/show...&postcount=493 posted by adolfotregosa. Now my LiveView works pretty fine with my SGS running CM 6.1 Nightly. Even if you'll go out of the bluetooth range and then want to reconnect it will happen more or less instantly.
Optional:
Instead of removing Advanced Task Killer you can leave it just set Security Level in Options to Low and then set following processes to ignore:
1. com.android.providers.drm
2. LiveViewApplication
3. OpenWatch
4. com.android.bluetooth
AND all of the processes from plugins you have (they have "liveview" in their name)
For me better option is with Advanced Task Killer enabled but everyone can decide for themselves.
I hope all of LiveView Users will now be able enjoy using this device.
Thanks to adolfotregosa for his discovery with OpenWatch which is the part of this solution.
Thanks a lot! right now I can use it... Now the only problem is the battery life...
omg ive been ready to though this thing out of the window, after a google search this post came up.
I had to downgrade then root my htc desire hd then ran that little program, and so far the machine is working as it was advertised!!!
you are a saint for finding this - so far 2hrs and counting connected, before hand i was lucky to get 3 mins!!!.
happy days!!
thankyou again
Fantastic find! I just did all as described and it has been connected for a good 30mins so far and no disconnects and/or reboots! LOVE IT!
Now I must find a replacement watchband hehe...
LockeOn said:
I found solution for LiveView connection issues and had it posted in Sony Ericsson LiveView™ Issues Thread on xda-forum.com . Unfortunately it hasn't been noticed by users untill now that it has been ripped from this forum and posted on www.robot-home.it on 30th December(http://www.robot-home.it/blog/2010/...i-comunicazione-e-al-blocco-dello-smartphone/) but as their own invention what made me really furious (Luckly it was corrected). It took me time to figure it out.
Link to original post form 23rd December: http://forum.xda-developers.com/showpost.php?p=10025306&postcount=190
This is the solution:
First of all delete LiveWare Manager, which causes our phones to crash all the time, and gives only one feature in return (shows all available liveview plugins which you can find manualy in the market). Then remove any kind
of Task Killer etc. Next step is to instal MinfreeManager (keep in mind that it requires root premissions). I recommend using Mild/Agressive preset but you have to change Secondary Server values very low (for example 6mb). By setting Secondary Server values to very low LiveView Application and all of the plugins will be kept alive all the time, which will prevent any disconnections. After this I used this solution http://forum.xda-developers.com/show...&postcount=493 posted by adolfotregosa. Now my LiveView works pretty fine with my SGS running CM 6.1 Nightly. Even if you'll go out of the bluetooth range and then want to reconnect it will happen more or less instantly.
Optional:
Instead of removing Advanced Task Killer you can leave it just set Security Level in Options to Low and then set following processes to ignore:
1. com.android.providers.drm
2. LiveViewApplication
3. OpenWatch
4. com.android.bluetooth
AND all of the processes from plugins you have (they have "liveview" in their name)
For me better option is with Advanced Task Killer enabled but everyone can decide for themselves.
I hope all of LiveView Users will now be able enjoy using this device.
Thanks to adolfotregosa for his discovery with OpenWatch which is the part of this solution.
Click to expand...
Click to collapse
I wrote you an email and wrote you two posts but you ignored me. I'm happy to help people writing solutions on my blog. I wrote something by myself and sometimes I take, solutions on other sites (normally in english) and I translate into Italian to diffuse them.
Every time I take a solution on other sites I put a link to the source, as in your case... there are also thanks to you and Fregosa... did you read it again? I never said it was an invention of mine... I'm not used to take works made by other people and pass them as mine.
I'm sorry you do not understand it, but it is not my fault... maybe italian to english translations do not work very well.
WHat if I dont use any taskkiller? would I have a problem with Liveview?
Myzhar said:
I wrote you an email and wrote you two posts but you ignored me. I'm happy to help people writing solutions on my blog. I wrote something by myself and sometimes I take, solutions on other sites (normally in english) and I translate into Italian to diffuse them.
Every time I take a solution on other sites I put a link to the source, as in your case... there are also thanks to you and Fregosa... did you read it again? I never said it was an invention of mine... I'm not used to take works made by other people and pass them as mine.
I'm sorry you do not understand it, but it is not my fault... maybe italian to english translations do not work very well.
Click to expand...
Click to collapse
Sorry I haven't write You back but I have been really busy with exams. I understand this whole situation was misunderstanding and I am glad that it has been corrected, thank You for that.
There is no need to use takskiller, it is just an option because some people are using that.
LockeOn said:
Sorry I haven't write You back but I have been really busy with exams. I understand this whole situation was misunderstanding and I am glad that it has been corrected, thank You for that.
Click to expand...
Click to collapse
I'm happy to read this words.
This evening I tried "Task Killer" configuration on my Galaxy Tab and I need to say that works a lot better than "minfreemanager".
I'm writing another post on my blog to allow italian user to get it, I'm also making a few screenshoot to allow a better understand of the configuration step, feel free to take them (when the article is ready) and put them here
Now I'm sure that the only problem on no-sonyericsson device is the managing of the memory and of the apps in background
what i mean is what step above i need to do if I dont use task killer
I never use one
in case i want to buy Live View, would i have a problem with the disconnection? or not?
Justin^Tan said:
what i mean is what step above i need to do if I dont use task killer
I never use onesw
in case i want to buy Live View, would i have a problem with the disconnection? or not?
Click to expand...
Click to collapse
I do not use any task killers. But to answer your question the connectivity issue still remains, even with this fix. You'll need to live with this issue for now until Sony Ericsson addresses the issue or some dev here can come up with a permanent fix.
Myzhar said:
I'm happy to read this words.
This evening I tried "Task Killer" configuration on my Galaxy Tab and I need to say that works a lot better than "minfreemanager".
I'm writing another post on my blog to allow italian user to get it, I'm also making a few screenshoot to allow a better understand of the configuration step, feel free to take them (when the article is ready) and put them here
Now I'm sure that the only problem on no-sonyericsson device is the managing of the memory and of the apps in background
Click to expand...
Click to collapse
Acctualy I think You got me wrong. The optional configuration with Task Killer contains everything that the regular option does so:
1. Delete LiveWare Manager
2. Instal MinfreeManager (keep in mind that it requires root premissions). I recommend using Mild/Agressive preset but you have to change Secondary Server values very low (for example 6mb).
3. Use this solution http://forum.xda-developers.com/show...&postcount=493 posted by adolfotregosa.
AND:
4. Install Advanced Task Killer, set Security Level in Options to Low and then set following processes to ignore:
a) com.android.providers.drm
b) LiveViewApplication
c) OpenWatch
d) com.android.bluetooth
+ all of the processes from plugins you have (they have "liveview" in their name)
So as You can see in both configurations MinFreeManager is used, but the optional configuration is enriched with Advanced Task Killer.
kpjimmy said:
I do not use any task killers. But to answer your question the connectivity issue still remains, even with this fix. You'll need to live with this issue for now until Sony Ericsson addresses the issue or some dev here can come up with a permanent fix.
Click to expand...
Click to collapse
It sad but it's true. This is just a PARTIAL fix, which makes LiveView more or less usable (sometimes it is great, sometimes You just want to threw it out) it will not make all of connection issues dissapear. But I have to say that with the newest firmware update vie SE Service Update and with this fix it is really good.
LockeOn said:
It sad but it's true. This is just a PARTIAL fix, which makes LiveView more or less usable (sometimes it is great, sometimes You just want to threw it out) it will not make all of connection issues dissapear. But I have to say that with the newest firmware update vie SE Service Update and with this fix it is really good.
Click to expand...
Click to collapse
Shoot I didn't even know they released a new firmware update. I have my unit at work so I won't be able to update and test until next week. Lockeon, is the update pretty straightforward? D/L the update software, select x10 mini, connect usb, press both top buttons and that should connect it right?
Thanks again for the heads up on the new update!
kpjimmy said:
Shoot I didn't even know they released a new firmware update. I have my unit at work so I won't be able to update and test until next week. Lockeon, is the update pretty straightforward? D/L the update software, select x10 mini, connect usb, press both top buttons and that should connect it right?
Thanks again for the heads up on the new update!
Click to expand...
Click to collapse
Yup, just do everything You mentioned and it will update the device, at the end it will give You "Instalation failed" message, but don't worry next time You connect liveview and run service update it will display that You have the newest firmware.
Task manager is to be used because when Android goes down of memory it kills background processes, included bluetooth manager and LV plugin applications. This is why LiveView Application loses connection, it does not find bluetooth process until you do not try to connect LV again and Android re-activate it.
To be sure that memory is not managed by Android I set Auto kill frequency to 30' and at Crazy level... then I do not have disconnections
Sent from my GT-P1000 using XDA App
Myzhar said:
Task manager is to be used because when Android goes down of memory it kills background processes, included bluetooth manager and LV plugin applications. This is why LiveView Application loses connection, it does not find bluetooth process until you do not try to connect LV again and Android re-activate it.
To be sure that memory is not managed by Android I set Auto kill frequency to 30' and at Crazy level... then I do not have disconnections
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Acctualy that is not entirely true, because if You open some kind of game or use flash in browser it will eat your memory faster than Advanced Task Killer can free it, and You will lose connection with LiveView. To reconnect You would have to start LiveView Application once again. To prevent Android from killing bluetooth manager and LiveView stuff it is important to set Secondary Server values to very low (that is why MinFreeManager is needed). Advanced Task Killer helps keeping high RAM level better than MinFreeManager which prevents phone and liveview from lagging but it won't protect LiveView and bluetooth stuff from beeing killed by Android.
LockeOn said:
Acctualy that is not entirely true, because if You open some kind of game or use flash in browser it will eat your memory faster than Advanced Task Killer can free it, and You will lose connection with LiveView. To reconnect You would have to start LiveView Application once again. To prevent Android from killing bluetooth manager and LiveView stuff it is important to set Secondary Server values to very low (that is why MinFreeManager is needed). Advanced Task Killer helps keeping high RAM level better than MinFreeManager which prevents phone and liveview from lagging but it won't protect LiveView and bluetooth stuff from beeing killed by Android.
Click to expand...
Click to collapse
Yes, you are right. As you can read in my last blog post I say to make your first procedure as first step (not real, first step is LV update ).
The secondo step on my post says:
"Se non l’avete ancora fatto eseguite la prima procedura di stabilizzazione della connessione di LockedOn riportata nel mio primo post"
translated:
"If you did not make it yet, follow LockedOn's first connection stabilization procedure, as written in my first post"
As we say in Italy "Advanced Task Killer" is the "ciliegina sulla torta"... the thing that makes a good work become a excellent work!
I have a doubt: when I open MinfreeManager I always get default values instead of the one I set. Is it right or is there something wrong in my "root"?
For "rooting" in used Z4root
Man I really wished that the Liveview would at least retain the time and then update when reconnected to the phone. I can't use it unless the phone is attached to me! Eh...my lil gripe I guess lol...
Hi!
After a lot of investigation and searching, I eliminated connection problems with LiveView, but it still remains almost unusable, because its damn "LiveView Application" crashes the whole phone randomly. Where is that famous "linux stability" if one small app can easily crash the whole OS...
I've found out already, that this happens if the application's process gets killed by Android (thanks to XDA forum, I managed to correctly setup task killers). I googled for solutions, and found these:
1 - "There isn't a way to prevent this directly, without a rooted device." - SO! There IS a way to prevent this on a rooted devise! Does anyone know about it?
2 - "The app needs to put itself in the Notifications bar in order to keep from getting killed when it's in the background. This is what apps like Music or Pandora do in order to keep playing music and not get killed when they are backgrounded" - well, is there some tool to selectively "give" some running app the notification bar icon? Because if we wait for SE to implement this, we may as well wait for Apple to produce iPhone watch
3 - "HOWTO: Change Process Priority Using the Nice Command" - I'm not quite sure if this applies to Android, but I've found it on Motorola Droid forum...
Well, is there a developer ready to look into this? After all, ALMOST everything is working fine, the only thing that needs to be fixed - keeping process alive no mattaer what...
Best regards,
Draco.
I've been working on fixing the GPS data validity bug (where positions are reported at a lat/long of approximately 0,0 prior to lock)
Attached is a version of libhardware_legacy.so that should do the following:
Improve debugging of GPS operation (change printf()s in the main GPS library file to Android logging macros)
Fix/workaround the 0,0 bug (I say workaround because I have yet to identify the root cause of the issue - however it is "fixed" from the point of view of an end user
A few "under the hood" cleanups/fixes
Things that are NOT implemented/fixed in this library:
XTRA (driver/library support for QuickGPS data loading)
Obtaining satellite status prior to GPS lock on Rhodiums (behavior on non-Rhodium unknown, but this should not change actual behavior at all except for the false 0,0 fixes)
Any methods for improved lock speed - all this does is prevent you from appearing south of Africa prior to lock
To test this fix (Intended for FRX05, may work with other 2.2.2 based builds that are derived from xdandroid FRX05):
Unzip the attached zip file
Place libhardware_legacy.so somewhere on your SD card. For organization, I use bindfiles/system/lib/libhardware_legacy.so
Open conf/froyo.user.conf in your favorite text editor
Within the custom_shells{} section of froyo.user.conf, add:
mount --bind /sdcard/bindfiles/system/lib/libhardware_legacy.so /system/lib/libhardware_legacy.so
Restart, and at this point:
1) 0,0 false locks should go away
2) You'll see lots of new GPS debugging info in ADB logcats
Edit: For testing, I usually use the "GPS Status and Toolbox" app from the market, since Google Maps does not show sat status.
With the stock GPS libraries, GPS Status and Toolbox will immediately report a 0,0 fix on startup
With this library, you should see that funky "wait for it circle" in the lower status area until you are locked. As mentioned above - you will not see satellite signal strength reports prior to lock
I was just looking at setting up the kernel build environment myself the other day.
The main useful reference I found was this:
http://forum.ppcgeeks.com/tp2-andro...modules-tinboot-nand-boot-more-beginners.html
However, that one's a bit of a firehose, too, since it deals with a lot of stuff specific to NAND.
In short clone these two repositories into the same directory:
Code:
git clone git://android.git.kernel.org/platform/prebuilt.git
git clone git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm.git
The first is the vanilla kernel, and the second is the XDAndroid kernel modifications. You'll need the first to compile.
From that guide, compile:
Code:
cd android
mkdir modules
cd linux-msm
make clean
make ARCH=arm htc_msm_android_defconfig
make ARCH=arm CROSS_COMPILE=~/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- INSTALL_MOD_PATH=~/android/modules zImage modules modules_install
Follow that guide for putting together the modules for wifi and the location of your compiled files.
Thanks! I will take a look at that, although I get the impression from reading through things that that GPS handling is at a layer somewhere above the kernel but below where we start having to deal with Java. I just can't quite figure out where since I have never done any Android development before.
I am probably going to poke at the kernel at some point though to try and fix the LED behaviors. It is clear from the "sleep of death fix" test kernels that there is knowledge of how to change these behaviors - at the very least I want to make it turn things *off* when in deep powersave. (Seems nonsensical to me to indicate that the device is in a deep power save mode by turning on a bright power-burning LED, although maybe the LED consumption is negligible even when the device is asleep.)
Entropy512 said:
Thanks! I will take a look at that, although I get the impression from reading through things that that GPS handling is at a layer somewhere above the kernel but below where we start having to deal with Java. I just can't quite figure out where since I have never done any Android development before.
I am probably going to poke at the kernel at some point though to try and fix the LED behaviors. It is clear from the "sleep of death fix" test kernels that there is knowledge of how to change these behaviors - at the very least I want to make it turn things *off* when in deep powersave. (Seems nonsensical to me to indicate that the device is in a deep power save mode by turning on a bright power-burning LED, although maybe the LED consumption is negligible even when the device is asleep.)
Click to expand...
Click to collapse
Whoops, didn't read carefully enough at where you'd narrowed the problem down to. I haven't gotten around to setting up an environment for the system build yet, sorry I couldn't be more of a help!
Yup, http://gitorious.org/xdandroid/hardware_libhardware_legacy/blobs/master/gps/gps_msm7k.c is my first target. There may also be issues in gps-rpc.c
http://xdandroid.com/wiki/Getting_the_Source goes thru how to build the system image. It starts with getting the source and cascades all the way thru building a system image.
I'm setup to build it as well, and I've always wondered how we could fix this problem... Love to see it squashed!
Thanks! I'll start working on that, although probably not until after the weekend is over at this point.
The ghetto approach as an interim fix would be to not set GPS_LOCATION_HAS_LAT_LONG if both are exactly zero - This is not the right way to do it, but the chances of it affecting anyone before a proper validity condition is identified are slim. (Even if you ARE near lat/long of 0/0, there will be enough noise in the GPS solution that you'll almost never actually be blanked).
Probably should assume that all of the other validity flags should not be set if we don't have a position fix. (Assumption: The MSM7k GPS does not take inputs from the magnetometer or accelerometer, if the Rhodium even has a magnetometer, didn't think it did.)
Of course, I haven't quite figured out how GPS_LOCATION_HAS_LAT_LONG and such roll up to higher levels. There's some odd interactions in terms of when SV status becomes available, for example.
Entropy512 said:
Thanks! I'll start working on that, although probably not until after the weekend is over at this point.
The ghetto approach as an interim fix would be to not set GPS_LOCATION_HAS_LAT_LONG if both are exactly zero - This is not the right way to do it, but the chances of it affecting anyone before a proper validity condition is identified are slim. (Even if you ARE near lat/long of 0/0, there will be enough noise in the GPS solution that you'll almost never actually be blanked).
Probably should assume that all of the other validity flags should not be set if we don't have a position fix. (Assumption: The MSM7k GPS does not take inputs from the magnetometer or accelerometer, if the Rhodium even has a magnetometer, didn't think it did.)
Of course, I haven't quite figured out how GPS_LOCATION_HAS_LAT_LONG and such roll up to higher levels. There's some odd interactions in terms of when SV status becomes available, for example.
Click to expand...
Click to collapse
Yup, definitely no magnetometer in the Rhodium.
Good luck with this, it'll be a nice little fix if you can get GPS to stop reporting locks before it has one.
Source downloaded, have a build going. (First an unchanged one...)
I'm working on a Froyo tree for the moment, since I think in the Gingerbread alphas GPS is simply "not working", although the degree of "not working" was not defined. Once I'm more familiar with the GPS handling code I might take a look at how it works for Gingerbread.
A few notes about the Froyo repo in its current state:
The URL for Google Apps that device/xdandroid/msm/unzip-files.sh is outdated. cyanogen-mirror.local.host.name does not exist any more. android.local.host.name does but doesn't have the HDPI Froyo apps. I forget which mirror I used - the list is in the CyanogenMod wiki if you search for gapps
The froyo build scripts direct you to http://source.android.com/download - URL no longer exists, it is http://source.android.com/source/download.html now
The process for installing Sun Java 5 on Ubuntu 10.10 is in the URL above - you need it to do a froyo build.
Also, the wiki instructions are missing lib32readline5-dev as an Ubuntu package that needs to be installed (it's in the source.android.com docs tho) - I'll try to update the wiki later.
Entropy512, glad to see someone is interested in looking at the GPS code. I helped phh with it in the last go around to get the RPC messaging part working working, but nothing has been done since.
The NMEA parsing stuff you see in the current gps lib is unused, all the data comes from RPC. Before getting the data directly from RPC was working, we took advantage of the fact that NMEA is output to smd27 and parsed that string data. In any case, once the GPS is brought up, that NMEA data is still viewable by catting /dev/smd27.
If you want to check out other similar code, look at the vogue gps code. I think it supposed to work pretty well, and the RPC behind it is similar. Theirs is a bit different in that they split the gps processing across the kernel and userland, where ours is all userland.
Ultimately, this stuff needs a bit of a rewrite, because the libhardware_legacy interface to GPS that the current lib is written to, is gone for Gingerbread. If we could just get the RPC stubs generated, we might be able to plug into the reference Qualcomm implementation and take advantage of that well sorted code. Check out the cyanogenmod libhardware gps to see what that looks like.
Thanks for the additional pointers bzo.
I'm at the stage where I managed to build the froyo tree, but have not yet had a chance to test the built system ext2 image. That's a goal for tomorrow.
OK, dumb question - Since I'm now trying to understand that RPC code - Where do all those printfs in gps-rpc.c print to?
edit: Never mind, figured it out - it's buried in the logcat... Was trying to go back in time using Android System Info, but adb logcat lets me view it as it happens.
edit 2: Nope, those are D() statements in gps_msm7k.c - don't know where the printf()s in gps-rpc.c are going - nowhere? Should these be D() statements???
those printfs were from when that code was a console test application. Not surprising that they wouldn't show up by default in the logcat. I'm sure there is some way to make them show up. Dunno off hand, but some googling on android debug logging and redirection of stdout and such may dig up that info.
bzo said:
those printfs were from when that code was a console test application. Not surprising that they wouldn't show up by default in the logcat. I'm sure there is some way to make them show up. Dunno off hand, but some googling on android debug logging and redirection of stdout and such may dig up that info.
Click to expand...
Click to collapse
Ah. That makes sense why they aren't D() statements like in gps_msm7k.c
I tried changing as many of the printf()s to D() macros as I could, I'll test it tonight.
Edit: Had a chance to test it this morning. No output from any of the printf()s that I changed to D()s. Either I did something wrong, or none of those code paths are hit in a no-signal/low-signal situation prior to lock. Doing a make clean followed by a rebuild to make sure.
Those debug statements don't display by default. You'll have to change some compile and/or android settings to have them show up.
btw, if you're not already doing this, building just the gps lib and doing a mount --bind with just the lib in your startup.txt is a big timesaver, as opposed to updating the entire build
bzo said:
Those debug statements don't display by default. You'll have to change some compile and/or android settings to have them show up.
btw, if you're not already doing this, building just the gps lib and doing a mount --bind with just the lib in your startup.txt is a big timesaver, as opposed to updating the entire build
Click to expand...
Click to collapse
Hmm, got any pointers in this regard? They are working for gps_msm7k.c, but not my changes to gps-rpc.c - these are built by the same Makefile and components of the same library as far as I can tell. Is there a log tag filter somewhere?
Thanks for the mount --bind tip - will try that on my next build attempt.
if you copied over the same #define for D(...) from gps_msm7k.c, it seems like it should work the same in the other file. I haven't looked that much into android logging though.
For some reason my copy-and-pasted #defines for D() were failing.
Using LOGD() directly works.
I'm adding another set of LOGD()s now - It appears that something is calling update_gps_location() with bogus data.
BINGO! - It appears we are receiving PDSM_PD_EVENT_HEIGHT and PDSM_PD_EVENT_VELOCITY events prior to a position fix. No clue why - but even though GPS_LOCATION_HAS_LAT_LONG is not set, apps assume lat/long is valid when an update_gps_position() callback occurs.
Going to make it so we only do the update_gps_location() callback when GPS_LOCATION_HAS_LAT_LONG is set. Also going to try and figure out the right situations where we can call update_gps_svstatus() - right now it is only done when we get a PDSM_PD_EVENT_POS.
bzo said:
btw, if you're not already doing this, building just the gps lib and doing a mount --bind with just the lib in your startup.txt is a big timesaver, as opposed to updating the entire build
Click to expand...
Click to collapse
This is a good suggestion, but the bind mount statement would go in the froyo.user.conf, not the startup.txt .
arrrghhh said:
This is a good suggestion, but the bind mount statement would go in the froyo.user.conf, not the startup.txt .
Click to expand...
Click to collapse
yea, yea, that's what I meant , thanks for the correction
using MyFiles, saw it in the main file directory.
GROWTH_TEST
was empty, deleted it.
anyone come across this?
Here also but the file is filled with connections blocked log.
raul6 said:
connections blocked log
Click to expand...
Click to collapse
interesting! what creates this log? is this system-related or a specific app?
Filled with following:
com.android.volley.NoConnectionError: java.net.ConnectException: Failed to connect to ureca.samsungapps.com
Me too. Info from Growth-Test Log Text.
com.android.volley.NoConnectionError: java.net.UnknownHostException: Unable to resolve host "ureca.samsungapps.com": No address associated with hostnamecom.android.volley.VolleyError: Network Disconnectedcom.android.volley.VolleyError: Network Disconnected
Sounds like it is a host. Could we be hacked? I have had issues since last august!
L .J.629 said:
Me too. Info from Growth-Test Log Text.
com.android.volley.NoConnectionError: java.net.UnknownHostException: Unable to resolve host "ureca.samsungapps.com": No address associated with hostnamecom.android.volley.VolleyError: Network Disconnectedcom.android.volley.VolleyError: Network Disconnected
Sounds like it is a host. Could we be hacked? I have had issues since last august!
Click to expand...
Click to collapse
It's apparent that it is a log file for an app on the phone.
Could your phone be hacked? if you truly were then you wouldn't see a log file. Let alone a log file saying that something couldn't connect to a samsung server.
If in doubt perform a full factory data reset and set the phone back up without using a backup. Do not install anything on the phone other then updates to what was on the phone originally. Use it like this for half a week to a week... if the log fle appears then it's probly from one of the apps on the phone.
Your issues are probably (80-90% likely until you make a proper new thread asking for help) entirely seperate from this.
Chances are either you have outdated firmware/software, hardware failures/problems, expectation/reality matters, or just need to do a factory data reset. If you choose to do the factory data reset then avoid using a backup to restore apps and settings (cuz if the issue was from an app or setting then the issue is most likely included with the backup).
I found some weird things in Hidden Sys apps as well: "Circular ver1.0" five instances of it 0.0B, "Filled" - also 5 instances, "Gestural Navigation Bar" - 10 times, "Rounded" x4 and some other 0.0 B apps., does anyone know what for are they and why they propagate in so many instances? Thanks in advance.
It was really bothering me that I couldn't find solid information on this. I went pretty deep down the rabbit hole this morning. So far, this is what I've found out:
Worth Noting;
-- If you crawl the subdomains for the logged domain samsungapps,com it's related to Samsung Galaxy Apps.
-- ureca subdomain was registered in 2009 (first Galaxy phone release)
-- "Growth" seems to be related to marketing via the Galaxy Store.
-- There seems to be Knox relations as well. I will speculate further down below.
After sorting through a ton of data, as if it couldn't be safely assumed by the domain, the ureca URL is embedded in the Samsung Apps, Theme Store, and Game Launcher, that I've found so far. Take a look at some interesting strings I found in the APKs;
Package Name
com.samsung.android.themestore
Internal Version
520110303
Displayed Version
5.2.01.10303
]https://ureca.samsungapps.com/collect/billing_usage_log
]https://ureca.samsungapps.com/collect/theme_sa_log
]https://cn-ureca.galaxyappstore.com/collect/theme_sa_log
Package Name
com.sec.android.app.samsungapps
Main Activity
com.sec.android.app.samsungapps.SamsungAppsMainActivity
Internal Version
450509140
Displayed Version
4.5.05.9
]https://ureca.samsungapps.com/collect/iap_usage_log
(There are also iap subdomains @ samsungapps too, fwiw)
BUT, I have no idea what devices these are coming off of. Some APKs are varying wildly. Some report spyware, trojans, etc, too. Most by only 1 AV vendor though. If anyone has more time than me, take a look. Not sure if Knox is the "backdoor", the 'diamond' and 'zirconia' subdomains looked interesting. Or if it's a false hit, the Chinese govt, or if the APKs are from a repo and they're malicious. Didn't look into it in the slightest.
VirusTotal
VirusTotal
www.virustotal.com
Or if anyone already discovered exactly the source of the "GROWTH_TEST" folder, please let me know so I don't revisit this. But I'm pretty sure it's Galaxy Store Market related stuff.
FWIW - Me
Galaxy S10+, OEM Unlocked.
June 1st security update. USA
My Growth Test folder contained 2 files,
appsUsageLog.txt: (1 "volley can't resolve ureca.samsungapps.com")
optin_trace.txt: (1 "volley network error")
You're probably over thinking this.
Pretty sure I've seen it before too.
If you're still running on Pie Karma Firewall will let you monitor and block internet connections.
Shows you which apks are busy sucking up bandwidth and battery.
Scan any questionable apks online with Virustotal.
AM Radio said:
using MyFiles, saw it in the main file directory.
GROWTH_TEST
was empty, deleted it.
anyone come across this?
Click to expand...
Click to collapse
Any updates to this? I too have the Growth_test folder with appGrowthLog.txt in it.
Edit: in the appGrowthLog.txt file says "com.android.volley.NetworkErrorcom.android.volley.VolleyError: Network Disconnected".