Database Info

[MOD] Eclair dialer for AOSP. Easy Install (v1.4.1) [2009-12-16]

I've loved the Eclair dialer since the first screen shot I saw, so when the source dropped, I backported it... I'm just finally getting around to posting it. I haven't tested it anywhere but the latest Cyanogen mod, but it should work on any ROM that's based on AOSP. If you have any success installing it, let me know. Use ADB to push it over the old Contacts.apk in /system/app.
With Wysie's help, I've added more features than I'd originally planned to. Here's the latest one I've put together, I'm working on bringing in more of his features, as well as some others I've got planned. Stay tuned for more.
Now has support for T-mobile Visual Voicemail, Google Voice, YouMail, PhoneFusion, and HulloMail.
Also now featuring 'Navigate to' bit in contact details for those with the latest Google Maps.
Fixed self induced bug on keyboard opening. Also trying out a new install method. I was able to just scan the QR below, download, and install straight from my phone. See how it works for you.
Contacts.apk
checksum: 77ab538901e18738711b7213e29cacf5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
1.4.1
- Fix for keyboard bug.
1.4
- 'Navigate to' option
- PF Visual Voicemail and HulloMail added.
1.3
- Call log enhancements from Wysie
- Enable/Disable each enhancement in Settings
1.2
- Support for YouMail added
- All in one app
- Only shows options for installed VM handlers
- Added preference screen
- Option to use Voicemail button for voicemail or add to contacts
v1.1.2
- Backported Eclair call log for kewlguru
v1.1.1GV
- Voicemail handler changes to Google Voice.
v1.1.1
- Much better fix for keyboard FC. There's now a landscape dialer screen.
v1.1
- Launch Visual Voicemail (if installed) with voicemail button
v1.0.1
- Fixed FC when opening keyboard (it's crude for now, I'll work on it)
- Made dial and VM buttons do what they're supposed to
v1.0
- Backported the full Eclair dialer layout

Looks nice, but I think everyone uses Visual Voicemail if there on T-Mobile or so I'm lead to believe by the download numbers on Market. Still great work though.

will try it right now
thanks!!

Nice work... Thumbs up.

xsnipuhx said:
Looks nice, but I think everyone uses Visual Voicemail if there on T-Mobile or so I'm lead to believe by the download numbers on Market. Still great work though.
Click to expand...
Click to collapse
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?

ChainsDD said:
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?
Click to expand...
Click to collapse
yuuuuuup

ChainsDD said:
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?
Click to expand...
Click to collapse
YES then I would be all over this!

this works perfect on 4.2.5 cyan.

ChainsDD said:
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?
Click to expand...
Click to collapse
i was thinking that too. is there away so when you click that button it gives you the option to choose an app to open and then you can select visual voice mail app and then every time you hit it your vvm app opens.

I'll start integrating Visual Voicemail tomorrow, I'll have it done by the weekend. Should it be automatic, as in if the app is installed it launches that, or should I make it an option?

ChainsDD said:
I'll start integrating Visual Voicemail tomorrow, I'll have it done by the weekend. Should it be automatic, as in if the app is installed it launches that, or should I make it an option?
Click to expand...
Click to collapse
like i suggested before, you should make it allow the user to select the app because not everyone uses the t-mobile visual voicemail app. I'm sure if you got it to do that devs would start cooking it in their roms.
sidenote: i'm using TheOfficial AOSP rom. can you make this compatible or should it work how it is?
edit: just pushed it. it works on TheOfficial. The voicemail button however does not do anything. Tried long pressing it too.

automatic

I use google voice for my voicemail... any chance you could put an option in there for that as well?
Oh and great work! Nice to get a taste of eclair.. and this dialer is pretty cool. Anything else you plan to backport? Like a lockscreen...?

matt_stang said:
I use google voice for my voicemail... any chance you could put an option in there for that as well?
Oh and great work! Nice to get a taste of eclair.. and this dialer is pretty cool. Anything else you plan to backport? Like a lockscreen...?
Click to expand...
Click to collapse
if he made the option for you to choose then it would work good.

I use Google Voice as well. The dialer looks great too.

Force close in landscape
Switching to landscape or using contacts in landscape mode leads to a FC. You might want to be sure it locks itself into portrait mode.
I/WindowManager( 188): Setting rotation to 1, animFlags=1
I/WindowManager( 188): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3 keys=2/1/1 nav=3 orien=2 layout=18}
D/PhoneWindow( 782): couldn't save which view has focus because the focused view [email protected] has no id.
D/StatusBar( 188): updateResources
D/AndroidRuntime( 782): Shutting down VM
W/dalvikvm( 782): threadid=3: thread exiting with uncaught exception (group=0x4001e170)
E/AndroidRuntime( 782): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 782): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.DialtactsActivity}: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.TwelveKeyDialer}: java.lang.NullPointerException
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2401)
E/AndroidRuntime( 782): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2417)
E/AndroidRuntime( 782): at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:3502)
E/AndroidRuntime( 782): at android.app.ActivityThread.access$2200(ActivityThread.java:116)
E/AndroidRuntime( 782): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1798)
E/AndroidRuntime( 782): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 782): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 782): at android.app.ActivityThread.main(ActivityThread.java:4203)
E/AndroidRuntime( 782): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 782): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 782): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 782): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
E/AndroidRuntime( 782): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 782): Caused by: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.TwelveKeyDialer}: java.lang.NullPointerException
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2401)
E/AndroidRuntime( 782): at android.app.ActivityThread.startActivityNow(ActivityThread.java:2242)
E/AndroidRuntime( 782): at android.app.LocalActivityManager.moveToState(LocalActivityManager.java:127)
E/AndroidRuntime( 782): at android.app.LocalActivityManager.startActivity(LocalActivityManager.java:339)
E/AndroidRuntime( 782): at android.widget.TabHost$IntentContentStrategy.getContentView(TabHost.java:631)
E/AndroidRuntime( 782): at android.widget.TabHost.setCurrentTab(TabHost.java:317)
E/AndroidRuntime( 782): at android.widget.TabHost.addTab(TabHost.java:210)
E/AndroidRuntime( 782): at com.android.contacts.DialtactsActivity.setupDialerTab(DialtactsActivity.java:131)
E/AndroidRuntime( 782): at com.android.contacts.DialtactsActivity.onCreate(DialtactsActivity.java:79)
E/AndroidRuntime( 782): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
E/AndroidRuntime( 782): ... 12 more
E/AndroidRuntime( 782): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 782): at com.android.contacts.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:179)
E/AndroidRuntime( 782): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
E/AndroidRuntime( 782): ... 22 more
I/Process ( 188): Sending signal. PID: 782 SIG: 3
I/dalvikvm( 782): threadid=7: reacting to signal 3
I/dalvikvm( 782): Wrote stack trace to '/data/anr/traces.txt'
I/ActivityManager( 188): Process com.android.settings (pid 810) has died.
I/DumpStateReceiver( 188): Added state dump to 1 crashes
D/dalvikvm( 188): GC freed 4244 objects / 310128 bytes in 195ms
I/WindowManager( 188): Setting rotation to 0, animFlags=1
I/WindowManager( 188): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3 keys=2/1/2 nav=3 orien=1 layout=18}
D/StatusBar( 188): updateResources
I/Process ( 782): Sending signal. PID: 782 SIG: 9
I/ActivityManager( 188): Process android.process.acore (pid 782) has died.
I/ActivityManager( 188): Killing app com.google.process.gapps (pid 791) because provider com.android.providers.im.ImProvider is in dying process android.process.acore
I/Process ( 188): Sending signal. PID: 791 SIG: 9
I/WindowManager( 188): WIN DEATH: Window{43c88340 com.android.launcher/com.android.launcher.Launcher paused=false}

Oops... I'll have a look at that. I use a myTouch, so I completly forgot about the keyboard thing. I'll work out a fix for that before I start on the VM bits. Gonna have to wait 'till tomorrow tho, I gotta be up for work at 4...

matt_stang said:
I use google voice for my voicemail... any chance you could put an option in there for that as well?
Oh and great work! Nice to get a taste of eclair.. and this dialer is pretty cool. Anything else you plan to backport? Like a lockscreen...?
Click to expand...
Click to collapse
As much as I love the 2.0 lockscreen, I think backporting it is a little out of my skillset atm. Changing almost anything in framework-res.apk causes problems with some of the precompiled apps. After I work out the bugs in this and add the VM features, I'll have a look at it tho.

ChainsDD said:
As much as I love the 2.0 lockscreen, I think backporting it is a little out of my skillset atm. Changing almost anything in framework-res.apk causes problems with some of the precompiled apps. After I work out the bugs in this and add the VM features, I'll have a look at it tho.
Click to expand...
Click to collapse
I figured it would be quite a difficult task. But if it's possible, it might be worth it. As there's no telling when we'll be able to have a fully functional eclair rom on the dream. So hey, if you're up for it, go ahead and give it a look

The call and voicemail buttons don't do anything on my g1 running cm4.2.7.1

[APP] LockPicker - disable Exchange lock screen (OPEN SOURCED)

Update: I decided to discontinue work on LockPicker and therefore open source it. Find the code here. If anyone manages to make this work on Android 2.2+, please let me know!
Disables the Exchange lock screen when it's part of the server's security policy.
Works on HTC Sense only.
NOTE: Froyo is not supported!
Changelog:
v0.95: Added Wildfire (QVGA) support, automatic account detection, added korean translation, fixed chinese translation
v0.94: Android 1.5+ compatible
v0.93: Added es,fr,de,nl,cn
v0.92: Notifications optional
v0.91: fixed FC on startup
v0.9: initial release
Search for Market > Applications > Tools > LockPicker
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My thanks go to tamburylar for his find which inspired me to create the app!

Nice
Hey, thanks for creating this.
I know there are a few people out there that will appreciate it.
Unfortunately I can't give feedback myself since my exchange server, although asks for me to enable security doesn't ever enforce it, so I never get the lock screen problem.
Good work though and I hope it comes in useful for the other guys that aren't as lucky with their server.

alias_neo said:
Hey, thanks for creating this.
I know there are a few people out there that will appreciate it.
Unfortunately I can't give feedback myself since my exchange server, although asks for me to enable security doesn't ever enforce it, so I never get the lock screen problem.
Good work though and I hope it comes in useful for the other guys that aren't as lucky with their server.
Click to expand...
Click to collapse
Hey, no problem. Creating the icons was probably the most work!
It is idle under normal circumstances and consumes next to no resources, only a tiny amount of memory to run the service.
Only when the server pushes the policy again, it will quickly disable the lock screen and go back to sleep

Great
j0bro said:
Hey, no problem. Creating the icons was probably the most work!
It is idle under normal circumstances and consumes next to no resources, only a tiny amount of memory to run the service.
Only when the server pushes the policy again, it will quickly disable the lock screen and go back to sleep
Click to expand...
Click to collapse
Nicely done. It'll be interesting to see how people get on with it. The security enforcement seems to be a massive annoyance for those suffering from it.

j0bro said:
Hi all,
I just whipped an app together that disables the Exchange lock screen as soon as the server has enforced its policy by using a background service and an observer on the system setting. This requires no polling, scripting, etc. and survives reboots/enforcements.
Search for Market > Applications > Tools > LockPicker
Any comments/issues are appreciated
Click to expand...
Click to collapse
Sounds great, but I don't see it in the marketplace ?
BTW, is it just for the stock exchange client, or will this work with Touchdown etc
Thanks

gudge said:
Sounds great, but I don't see it in the marketplace ?
BTW, is it just for the stock exchange client, or will this work with Touchdown etc
Thanks
Click to expand...
Click to collapse
You must have Android 2.1 running, since this is made natively for that version (Exchange integrated)

j0bro said:
Hi all,
I just whipped an app together that disables the Exchange lock screen as soon as the server has enforced its policy by using a background service and an observer on the system setting. This requires no polling, scripting, etc. and survives reboots/enforcements.
Search for Market > Applications > Tools > LockPicker
Any comments/issues are appreciated
Click to expand...
Click to collapse
Thanks, works perfect

Downloaded this for my Milestone running 2.1. At first it seemed to work. After I rebooted though the application forcecloses (right at boot). When I start the application after booting it seems to keep running (though I'm not sure if I can actually see the service in my task manager) but does nothing to prevent me from having to enter that stupid password : (
I'm happy to help if I can do anything to help you with this issue. Don't know if it's possible to access log files on Android and perhaps send it or something.

I have FC after reboot but LockPicker still works well.

Found out how to log errors in application. Here is a piece of the log file relating to lockpicker:
Code:
I/ActivityManager( 1281): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=nl.fotoniq.android.lockpicker/.LockPicker }
I/ActivityManager( 1281): Displayed activity nl.fotoniq.android.lockpicker/.LockPicker: 329 ms (total 329 ms)
I/NotificationService( 1281): enqueueToast pkg=nl.fotoniq.android.lockpicker [email protected] duration=0
I/NotificationService( 1281): enqueueToast pkg=nl.fotoniq.android.lockpicker [email protected] duration=0
E/LockPickerService( 1837): Setting not found
E/LockPickerService( 1837): android.provider.Settings$SettingNotFoundException: lockscreen.lockexchange.enable
E/LockPickerService( 1837): at android.provider.Settings$System.getInt(Settings.java:656)
E/LockPickerService( 1837): at nl.fotoniq.android.lockpicker.LockPickerService.disableExchangeLockscreen(LockPickerService.java:101)
E/LockPickerService( 1837): at nl.fotoniq.android.lockpicker.LockPickerService.onStartCommand(LockPickerService.java:67)
E/LockPickerService( 1837): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2873)
E/LockPickerService( 1837): at android.app.ActivityThread.access$3500(ActivityThread.java:119)
E/LockPickerService( 1837): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1926)
E/LockPickerService( 1837): at android.os.Handler.dispatchMessage(Handler.java:99)
E/LockPickerService( 1837): at android.os.Looper.loop(Looper.java:123)
E/LockPickerService( 1837): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/LockPickerService( 1837): at java.lang.reflect.Method.invokeNative(Native Method)
E/LockPickerService( 1837): at java.lang.reflect.Method.invoke(Method.java:521)
E/LockPickerService( 1837): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/LockPickerService( 1837): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/LockPickerService( 1837): at dalvik.system.NativeStart.main(Native Method)
Seems lockpicker can't find the settings on my device or something.

abats said:
Found out how to log errors in application. Here is a piece of the log file relating to lockpicker:
Code:
I/ActivityManager( 1281): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=nl.fotoniq.android.lockpicker/.LockPicker }
I/ActivityManager( 1281): Displayed activity nl.fotoniq.android.lockpicker/.LockPicker: 329 ms (total 329 ms)
I/NotificationService( 1281): enqueueToast pkg=nl.fotoniq.android.lockpicker [email protected] duration=0
I/NotificationService( 1281): enqueueToast pkg=nl.fotoniq.android.lockpicker [email protected] duration=0
E/LockPickerService( 1837): Setting not found
E/LockPickerService( 1837): android.provider.Settings$SettingNotFoundException: lockscreen.lockexchange.enable
E/LockPickerService( 1837): at android.provider.Settings$System.getInt(Settings.java:656)
E/LockPickerService( 1837): at nl.fotoniq.android.lockpicker.LockPickerService.disableExchangeLockscreen(LockPickerService.java:101)
E/LockPickerService( 1837): at nl.fotoniq.android.lockpicker.LockPickerService.onStartCommand(LockPickerService.java:67)
E/LockPickerService( 1837): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2873)
E/LockPickerService( 1837): at android.app.ActivityThread.access$3500(ActivityThread.java:119)
E/LockPickerService( 1837): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1926)
E/LockPickerService( 1837): at android.os.Handler.dispatchMessage(Handler.java:99)
E/LockPickerService( 1837): at android.os.Looper.loop(Looper.java:123)
E/LockPickerService( 1837): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/LockPickerService( 1837): at java.lang.reflect.Method.invokeNative(Native Method)
E/LockPickerService( 1837): at java.lang.reflect.Method.invoke(Method.java:521)
E/LockPickerService( 1837): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/LockPickerService( 1837): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/LockPickerService( 1837): at dalvik.system.NativeStart.main(Native Method)
Seems lockpicker can't find the settings on my device or something.
Click to expand...
Click to collapse
Seems to me that you either don't use the integrated Exchange client of Android 2.1 or your Exchange server doesn't enforce the lockscreen as part of its policy. Makes any sense?
I'll include a check for the setting in the next version, thanks.

j0bro said:
Seems to me that you either don't use the integrated Exchange client of Android 2.1 or your Exchange server doesn't enforce the lockscreen as part of its policy. Makes any sense?
I'll include a check for the setting in the next version, thanks.
Click to expand...
Click to collapse
I use the integrated exchange client, there is nothing else on Milestone 2.1. My account is set up through accounts->corporate etc etc.
My company does enforce the lockscreen, there is no way for me to get around it. Before this I used a windows mobile phone and it was forced on there aswell. Big difference is unlocking on a windows mobile device was much faster.
If there is more I can do to help you track the behaviour on my phone of this application please let me know.

abats said:
I use the integrated exchange client, there is nothing else on Milestone 2.1. My account is set up through accounts->corporate etc etc.
My company does enforce the lockscreen, there is no way for me to get around it. Before this I used a windows mobile phone and it was forced on there aswell. Big difference is unlocking on a windows mobile device was much faster.
If there is more I can do to help you track the behaviour on my phone of this application please let me know.
Click to expand...
Click to collapse
Ahh wait, it is integrated in HTC Sense rather than Android 2.1 itself; this may explain why it wouldn't work on your Motorola. Any luck with LogCat output?

I don't know exactly how you app is meant to work, but there are differences between Vanilla Android and HTC's Sense mail. AFAIK, they don't use the same frameworks, so changes that affect the HTC one will probably be designed to patch over an HTC change. I don't know about vanilla, but I think the app would need to be designed for this.

It's giving me a FC on this ROM after reboot
http://forum.xda-developers.com/showthread.php?t=654030
But after that it seems to work fine again.
An example of what anon2122 ment i guess ?

an0therus3r said:
It's giving me a FC on this ROM after reboot
http://forum.xda-developers.com/showthread.php?t=654030
But after that it seems to work fine again.
An example of what anon2122 ment i guess ?
Click to expand...
Click to collapse
Yup saw that happening as well; found out that it is illegal to log with a tag of more than 23 characters. The logic/humor of this requirement escapes me though
Check for an update shortly in which I will have fixed this.
EDIT: update is on the Market right now.

I Love you, dude works perfect.

not work on my Moto Milestone

ricky119 said:
not work on my Moto Milestone
Click to expand...
Click to collapse
Actually I am working together with another Milestone user to get it working on that as well. Stay tuned!

j0bro said:
Actually I am working together with another Milestone user to get it working on that as well. Stay tuned!
Click to expand...
Click to collapse
thanks man,
BTW, I found theres another similar app which is under testing and seems can work on milestone.
Maybe you can talk and discuss with the author.
http://forum.xda-developers.com/showthread.php?p=6072131#post6072131

[App]Llama - Location Aware Mobile Application

Hey guys,
I've been playing about with android for about a year now and I've written this app. It's a location and time-based profile application, so you can set ringer volume, vibrate mode and ring tones for when you are asleep or at work.
It's like an extremely light-weight version of Locale with very few features
Eventually I'll put it on the Market, so I'm trying to figure out if there's going to be enough interest for it.
-Would you pay 60p-£1 ($1 to £1.50) for it?
-If I put it on there as free and ask people to donate, will enough people bother at least to cover the Market fee... do people actually donate beer-money if they know they can get it for free?
-Let me know of any bugs or suggestions (Note: I'd like to keep it simple, if you want lots of features, then I'd suggest a different app)
-This version will expire mid February. I'll hopefully have decided how I want to proceed with it after mid February.
Cheers all!
Usage Instructions:
Llama comes with a predefined set of Profiles, but you can customise these.
Llama uses 'events'. Each event has a set of conditions and actions. When all of the conditions are met, the actions are run. Llama comes with some default events, but you can customise them appropriately. One of the events is named 'Quiet at night', and is based on the fact that you are at home, and the time is after 10pm. This means that when it is late and you are at home, it will turn the ringer to a lower volume. However, if you are at the pub and it's after 10pm, it will leave the ringer alone (NOTE: this is assuming that your home and the pub are suitably far away. Llama works best in built up areas with lots of phone masts). You can also create an event that disables/enables APN mobile data, so your phone isn't pointlessly checking your email overnight
Llama uses no data whatsoever, so you have to teach it the IDs of the phone masts near your home and workplace. Doing this is easy. Just go to the 'Areas' tab and long-press to tell the app to 'start learning' your home or workplace. Tell it how long you plan to be at home or work and it'll make a note of the phone masts that it finds. Then do the same for when you are at work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
1.2011.01.28.1330
-Donation button added
-Help text added
-Import/Export/Apn On-Off menus condensed into a popup
-Package name changed so it can be uploaded to the market after some evil person uploaded it to the market without my permission
1.2011.01.25.1500
-Wifi action can be set to only turn off wifi if not connected to a wifi network
-Improvements/hacks to the keylock action, because the API misbehaves if the service gets killed between disabling then reenabling they key lock
1.2011.01.22.1710
-Charging/Discharging condition
-Run application action
-Disable keylock action
-Confirm deletes in area, events and profiles
-Option to set whether 'no signal' causes Llama to leave an area
-Stuff is sorted alphabetically now
-Now expires 15th Feb
1.2011.01.12.2110
-Cdma network dump if you turn on Debug -> Write to LlamaLog.txt
(Not that exciting)
1.2011.01.10.2120
- Fix for Cdma networks (hopefully)
1.2011.01.09.1940
- Added Bluetooth toggle
- Added Day of the week condition
- Added a way to remove cells from an area
- Logging and data import/export goes in /sdcard/Llama
- Added free warning for twats that like to charge other people money for applications they have not written
1.201012262100
- Added Wifi toggle
ATTACHMENT REMOVED
Go get it from the market now

Looks good - I'll have a play and report back any feedback
It'd be handy to be able to turn wifi on/off at certain locations - no point having it on in the office when there's no open wifi to connect to.
Any chance of an option to hide the notification icon from the titlebar (show it only shows in the dropdown?)

Thinking some more, it'd be handy to be able to have location categories - something like:
* Home (category)
- My house
- Parents house
* Work
- London's office
- Cambridge office
That way I can have events assigned to "home" or "work" without having to duplicate rules, or merge multiple locations together.

I've added a WiFi toggle. I'll have a think about the area grouping. The point of the notification is so you can see what profile is active by the number of dots on the icon. You can completely hide the icon in the settings. I'm not certain that Llama is the kind of application you need constant access to via the notification bar.

This reminds me of sman application which was there on my p910i. I have been lookinh for this.
Will it be possible for you to add triggering some event such as sms or ringtone. ?
Sent from my X10i using XDA App

Force close. Android 2.1. =[ was looking fwd to this app.
[ send from my huawei ascend | ipodify.net ]

dEris said:
Force close. Android 2.1. =[ was looking fwd to this app.
[ send from my huawei ascend | ipodify.net ]
Click to expand...
Click to collapse
It will have written an error report to your SDCard. Can you send me a copy of the LlamaLog.txt that appears on your SDCard to [email protected].
ta

Kebab3000 said:
EDIT: attachment removed because some unsavoury person decided they'd publish it on the market for me. still, nice to know it would get '< 50 downloads'
Click to expand...
Click to collapse
Ack. As far as I can tell it's been deleted now (at least I couldn't find the fake version when searching) - Do you still have plans to release this? I'm finally using it properly now I'm back at work and have found it to work perfectly so far, so it'd be a shame for it to expire on me now.
I'd happily pay £1 for it

benjymous said:
Ack. As far as I can tell it's been deleted now (at least I couldn't find the fake version when searching) - Do you still have plans to release this? I'm finally using it properly now I'm back at work and have found it to work perfectly so far, so it'd be a shame for it to expire on me now.
I'd happily pay £1 for it
Click to expand...
Click to collapse
I emailed the bloke and he removed it. I also reported it to Google who haven't done much about the rest of his probably stolen apps/themese. He's DavinciDevelopers by the way. If anyone's bored, buy his apps, give them 1 star, then refund
I'm still not 100% sure if I'll release it, but it's likely I will in some form. I need to decide about whether to have it as just a paid version or free+donate. There's still 3 weeks before it expires, and I'll happily extend that if I haven't decided by then.

Cool - glad you've not lost heart after that
I noticed another issue - there doesn't seem to be a way of removing a cell from a location - I accidentially added a cell to both "Home" and "Work". Ended up deleting and recreating the "Home" location.
This is using the (1.20101226) build, as I didn't get a chance to grab the newer version

Yep, known issue I'll probably add an item to the long-press menu to remove a cell from an area.
That does have the downside that you have to have seen the cell recently to remove it. If I just show the cell IDs in an area, then you wouldn't know which to remove.

Any way you could use the Google APIs to get a vague description of the antenna location?
Though I'm happy with just spotting it in the recent list, as that's where I accidentally added it

Kebab3000 said:
I'm still not 100% sure if I'll release it, but it's likely I will in some form. I need to decide about whether to have it as just a paid version or free+donate. There's still 3 weeks before it expires, and I'll happily extend that if I haven't decided by then.
Click to expand...
Click to collapse
Sad to see it's gone. I just discovered this thread.

I just discovered it, I wish I knew about this app man id love to try it n heh I would buy it too or donate
Swyped using SuperSonic

So is this basically just your version of Tasker?
Tasker is an application for Android which performs Tasks (sets of Actions) based on Contexts (application, time, date, location, event, gesture) in user-defined Profiles, or in clickable or timer home screen widgets.
Click to expand...
Click to collapse

DiGi760 said:
So is this basically just your version of Tasker?
Click to expand...
Click to collapse
Pretty much. It started out as a university project 5 years ago on Series 60, and I reimplemented it when I switched to android. There's plenty of apps already like it on the market, so I don't want to completely replicate the functionality of Tasker.
benjymous said:
Any way you could use the Google APIs to get a vague description of the antenna location?
Click to expand...
Click to collapse
That'd mean it would need to use data. Llama's unique "selling" point at the moment is it doesn't need any data and it just sits there looking at cell tower IDs
tdusen said:
Sad to see it's gone. I just discovered this thread.
Click to expand...
Click to collapse
It'll be back when I have time to put a 'If you bought this off a douchebag on the market you should demand a refund' dialog box

Kebab3000 said:
It'll be back when I have time to put a 'If you bought this off a douchebag on the market you should demand a refund' dialog box
Click to expand...
Click to collapse
...and it's back. Keep the feedback coming

I'm glad to see this is back. Looks like a great app.
Sent from my HTC Glacier using XDA App

Wanted to try this out but it just force closes on my gingerbread rom
Sent from my ADR6300 using XDA App

FC for me also.
Here's the exception from logcat
Code:
I/ActivityManager( 104): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10
200000 cmp=com.kebab.LlamaDroid/.LlamaUi }
I/ActivityManager( 104): Start proc com.kebab.LlamaDroid for activity com.kebab.LlamaDroid/.LlamaUi: pid=1265 uid=10089 gids={3001,
1015}
D/AK8973 ( 72): Compass Start
D/Sensors ( 104): open_akm, fd=147
I/LlamaDroid( 1265): InitCellListener
I/LlamaDroid( 1265): androidID=2125c55ace0a96e5
I/LlamaDroid( 1265): starting to listen
I/LlamaDroid( 1265): requesting update
D/AndroidRuntime( 1265): Shutting down VM
W/dalvikvm( 1265): threadid=1: thread exiting with uncaught exception (group=0x40025a38)
I/global ( 1265): Default buffer size used in BufferedWriter constructor. It would be better to be explicit if an 8k-char buffer is
required.
E/AndroidRuntime( 1265): FATAL EXCEPTION: main
E/AndroidRuntime( 1265): java.lang.RuntimeException: Unable to create service com.kebab.LlamaDroid.LlamaService: java.lang.ClassCast
Exception: android.telephony.cdma.CdmaCellLocation
E/AndroidRuntime( 1265): at android.app.ActivityThread.handleCreateService(ActivityThread.java:3140)
E/AndroidRuntime( 1265): at android.app.ActivityThread.access$3300(ActivityThread.java:135)
E/AndroidRuntime( 1265): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2202)
E/AndroidRuntime( 1265): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1265): at android.os.Looper.loop(Looper.java:144)
E/AndroidRuntime( 1265): at android.app.ActivityThread.main(ActivityThread.java:4937)
E/AndroidRuntime( 1265): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1265): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1265): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1265): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1265): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1265): Caused by: java.lang.ClassCastException: android.telephony.cdma.CdmaCellLocation
E/AndroidRuntime( 1265): at com.kebab.LlamaDroid.LlamaService$2.onCellLocationChanged(LlamaService.java:495)
E/AndroidRuntime( 1265): at com.kebab.LlamaDroid.LlamaService.initCellListener(LlamaService.java:527)
E/AndroidRuntime( 1265): at com.kebab.LlamaDroid.LlamaService.onCreate(LlamaService.java:105)
E/AndroidRuntime( 1265): at android.app.ActivityThread.handleCreateService(ActivityThread.java:3125)
E/AndroidRuntime( 1265): ... 10 more
W/ActivityManager( 104): Force finishing activity com.kebab.LlamaDroid/.LlamaUi

[WIP] Cowon D3 port

I began porting the Cowon D3 music player's UI. It is a very cool one, a lot of added widgets, and such, but I got one big problem. Cowon implemented a new way of blocking the run of their apps on other phones. It is a multi-layer device checking library, included in a framework.
What I got so far is from the disassembled code is that it checks for /dev/block/ndda's exist, and then another check goes on /proc/cpuinfo for "Hardware : COWON D3". This last string in the source is in three parts: the hardware title, the ":" and the "COWON D3" one.
Could someone with knowledge hack this library to include ALL devices in the check?

I really wish I could be of help but I don't have any knowledge that would be of any help... I think the UI is really interesting and hope you have success porting it! I was also "dreaming" if the BBE+ sound effects of Cowon devices could be ported as well... I would be willing to pay upto 80 dollars for that lol

Did you have any progress?
I tried to get the Launche working, but is has everytime a fc.
Here is some of my log and it seems there are missing some functions...
Code:
D/dalvikvm( 8925): GC_EXTERNAL_ALLOC freed 85K, 50% free 2829K/5639K, external 0K/0K, paused 184ms
I/dalvikvm( 8925): Could not find method android.provider.MediaStore.set_highspeed_clock, referenced from method com.cowon.home2d.CustomGridView.startScrollIfNeeded
W/dalvikvm( 8925): VFY: unable to resolve static method 381: Landroid/provider/MediaStore;.set_highspeed_clock ()I
D/dalvikvm( 8925): VFY: replacing opcode 0x71 at 0x0008
D/dalvikvm( 8925): VFY: dead code 0x000b-001f in Lcom/cowon/home2d/CustomGridView;.startScrollIfNeeded (I)Z
I/dalvikvm( 8925): Could not find method , referenced from method com.cowon.home2d.CustomGridView.onTouchEvent
W/dalvikvm( 8925): VFY: unable to resolve static method 381: Landroid/provider/MediaStore;.set_highspeed_clock ()I
D/dalvikvm( 8925): VFY: replacing opcode 0x71 at 0x0082
D/dalvikvm( 8925): VFY: dead code 0x0085-0111 in Lcom/cowon/home2d/CustomGridView;.onTouchEvent (Landroid/view/MotionEvent;)Z
I/dalvikvm( 8925): Could not find method android.os.Environment.getNandStorageState, referenced from method com.cowon.home2d.CWSlidingDrawer$MemoryStatus.externalMemoryAvailable
W/dalvikvm( 8925): VFY: unable to resolve static method 350: Landroid/os/Environment;.getNandStorageState ()Ljava/lang/String;
D/dalvikvm( 8925): VFY: replacing opcode 0x71 at 0x0000
D/dalvikvm( 8925): VFY: dead code 0x0003-000a in Lcom/cowon/home2d/CWSlidingDrawer$MemoryStatus;.externalMemoryAvailable ()Z
I/dalvikvm( 8925): Could not find method android.os.Environment.getNandStorageDirectory, referenced from method com.cowon.home2d.CWSlidingDrawer$MemoryStatus.getAvailableExternalMemorySize
W/dalvikvm( 8925): VFY: unable to resolve static method 349: Landroid/os/Environment;.getNandStorageDirectory ()Ljava/io/File;
D/dalvikvm( 8925): VFY: replacing opcode 0x71 at 0x0006
D/dalvikvm( 8925): VFY: dead code 0x0009-001e in Lcom/cowon/home2d/CWSlidingDrawer$MemoryStatus;.getAvailableExternalMemorySize ()J
I/dalvikvm( 8925): Could not find method android.os.Environment.getNandStorageDirectory, referenced from method com.cowon.home2d.CWSlidingDrawer$MemoryStatus.getTotalExternalMemorySize
W/dalvikvm( 8925): VFY: unable to resolve static method 349: Landroid/os/Environment;.getNandStorageDirectory ()Ljava/io/File;
D/dalvikvm( 8925): VFY: replacing opcode 0x71 at 0x0006
D/dalvikvm( 8925): VFY: dead code 0x0009-001e in Lcom/cowon/home2d/CWSlidingDrawer$MemoryStatus;.getTotalExternalMemorySize ()J
D/AndroidRuntime( 8925): Shutting down VM
W/dalvikvm( 8925): threadid=1: thread exiting with uncaught exception (group=0x40018560)
E/AndroidRuntime( 8925): FATAL EXCEPTION: main
E/AndroidRuntime( 8925): java.lang.NoSuchMethodError: android.os.Environment.getNandStorageState
E/AndroidRuntime( 8925): at com.cowon.home2d.CWSlidingDrawer$MemoryStatus.externalMemoryAvailable(CWSlidingDrawer.java:1300)
E/AndroidRuntime( 8925): at com.cowon.home2d.CWSlidingDrawer$MemoryStatus.getTotalExternalMemorySize(CWSlidingDrawer.java:1333)
E/AndroidRuntime( 8925): at com.cowon.home2d.CWSlidingDrawer.updateAvailableStorage(CWSlidingDrawer.java:485)
E/AndroidRuntime( 8925): at com.cowon.home2d.CWSlidingDrawer.updateIndicator(CWSlidingDrawer.java:374)
E/AndroidRuntime( 8925): at com.cowon.home2d.CWSlidingDrawer.setLauncher(CWSlidingDrawer.java:316)
E/AndroidRuntime( 8925): at com.cowon.home2d.Launcher.setupViews(Launcher.java:644)
E/AndroidRuntime( 8925): at com.cowon.home2d.Launcher.onCreate(Launcher.java:288)
E/AndroidRuntime( 8925): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 8925): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime( 8925): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
E/AndroidRuntime( 8925): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime( 8925): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime( 8925): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8925): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 8925): at android.app.ActivityThread.main(ActivityThread.java:3839)
E/AndroidRuntime( 8925): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8925): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 8925): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 8925): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 8925): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 6767): Force finishing activity com.cowon.home2d/.Launcher
W/ActivityManager( 6767): Activity pause timeout for HistoryRecord{40714fb8 com.cowon.home2d/.Launcher}

So, where are the Cowon D3 Music Player??? This works still WIP?

Sadly no more work can be done, the app is too much bound to Cowon's framework :S

Any progress man?

This?!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MB525 using Tapatalk 2 Beta-5

Download link?

fonix232 said:
Sadly no more work can be done, the app is too much bound to Cowon's framework :S
Click to expand...
Click to collapse
Did no one see this!? There is no download link because it is not possible for him to do it.
Sent using Tapatalk

iJimaniac said:
Did no one see this!? There is no download link because it is not possible for him to do it.
Sent using Tapatalk
Click to expand...
Click to collapse
http://db.tt/22IlGHUY
Use this
Sent from my MB525 using Tapatalk 2 Beta-5

oh, it works

Needs a bit more work, but it's cool!
If only someone could port the JetEffects Equalizer....

Say hello to Jetpack, a better app drawer [Updated!]

My first Android app, mostly to fix a lack of vertical launchers in the Market. I'd love to know what you think of it!
Upcoming updates
First priority: hiding apps.
Second priority: running apps and more
Update: Added an icon to indicate apps in external storage.
Click to expand...
Click to collapse
Third priority: long press menu (app info and whatnot)
Click to expand...
Click to collapse
JetPack is an app launcher that is scrollable like Contacts: slide to the right letter and pick your app! Simple, efficient and much easier to read than a grid layout.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jetpack is an application drawer replacement that can be used with your favorite launcher. Instead of using the standard grid layout, Jetpack displays your apps in a list to make them easier to find. Just like in Contacts, you can use the scrollbar to get to a specific letter in the list.
This application is not a home replacement, only an application launcher. To use it, create a shortcut on your home screen or your dock.
Click to expand...
Click to collapse
https://market.android.com/details?id=com.nicolasb.shuttle

Now if you put there keyboard with T9 searching, that will be good idea! (Like in Touchpal Dialer for example, but for apps).

I had the same idea! That being said, it's my first app and I need to practice a bit.

I quite like it. It's a bit laggy but I think that's due to the sheer amount of apps I have installed. It's certainly quicker to load than appdrawer.
What I think will make this better is to have letters running along side, it should make jumping to the apps much quicker. In case you don't know what I'm taking about, have a look at ios and miui contacts.
Thank you for the work you put in on this, I will be using it myself .
Best of luck with the development.

I like the idea.
Things I wish to brainstorm:
1)
on the right there's so much space. It's cool and fine, but perhaps something can be done with it...
for example, based on already logged infos (just the ones BetterBatteryStats uses), you could show a mini-icon on the right of those apps who are wakelocking too much. This way, users know which apps do tey need to report/look for a replacement, easy.
Concept is:
Your app is all about the apps. Perhaps, it could be even more, by providing slick, non-intrusive, only-where-needed informations.
2)
an option to add a (very) little more padding between rows
3)
an option to 1.5x icons size
4)
For particular apps, like gMail, an icon to go directly to "Compose new mail", maybe only text, maybe even only when the 1.5x option os on.

Nice app and idea. A bit of lag on tmobiles galaxy s2. Also a letter selection would be good like on stock touchwiz.
——————————
Deebo took your bike too?

It does have some lag but i think that I'd because off the transparency, you might want to try going without or at least having an option. I've noticed the same thing with themes that have a transparent background in various menus that seem to lag but when i go back to an opaque theme its smooth. But other than that its very nice. I can see this bring my app drawer replacement.

Some suggestions!
Add the ability to completely replace the app drawer with it.
Increase icon and text size.
Add the letters on the side like in contacts.
Add searching to the features.
Add a background option.
Optimize it a bit. Slightly laggy on my Motorola Photon.
Still a great start! I cannot wait for it to become more known!

Aww crud:
Code:
E/AndroidRuntime(25714): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.nicolasb.shuttle/com.nicolasb.shuttle.AppList}: java.lang.StringIndexOutOfBoundsException
E/AndroidRuntime(25714): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
E/AndroidRuntime(25714): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
E/AndroidRuntime(25714): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime(25714): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime(25714): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(25714): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime(25714): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime(25714): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(25714): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(25714): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
E/AndroidRuntime(25714): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
E/AndroidRuntime(25714): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(25714): Caused by: java.lang.StringIndexOutOfBoundsException
E/AndroidRuntime(25714): at java.lang.String.substring(String.java:1651)
E/AndroidRuntime(25714): at com.nicolasb.shuttle.AppAdapter.<init>(AppAdapter.java:40)
E/AndroidRuntime(25714): at com.nicolasb.shuttle.AppList.onCreate(AppList.java:22)
E/AndroidRuntime(25714): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(25714): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime(25714): ... 11 more
W/ActivityManager( 173): Force finishing activity com.nicolasb.shuttle/.AppList
Update
This will happen if you have installed an app that doesn't have a proper name, only a package name.

this is quite nice thus far...
my only suggestion would be to have the ability to hide apps....

That would have been my second priority (after performance is fixed), but it seems search takes the cake. I also want to hide a few apps in there.

jasonevil said:
this is quite nice thus far...
my only suggestion would be to have the ability to hide apps....
Click to expand...
Click to collapse
And add that to the list of my suggestions!

I like this app launcher very much.
The features i would like to see have already been said by others, keep up the good work.

cyansmoker said:
Aww crud:
Code:
E/AndroidRuntime(25714): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.nicolasb.shuttle/com.nicolasb.shuttle.AppList}: java.lang.StringIndexOutOfBoundsException
E/AndroidRuntime(25714): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
E/AndroidRuntime(25714): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
E/AndroidRuntime(25714): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime(25714): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime(25714): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(25714): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime(25714): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime(25714): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(25714): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(25714): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
E/AndroidRuntime(25714): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
E/AndroidRuntime(25714): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(25714): Caused by: java.lang.StringIndexOutOfBoundsException
E/AndroidRuntime(25714): at java.lang.String.substring(String.java:1651)
E/AndroidRuntime(25714): at com.nicolasb.shuttle.AppAdapter.<init>(AppAdapter.java:40)
E/AndroidRuntime(25714): at com.nicolasb.shuttle.AppList.onCreate(AppList.java:22)
E/AndroidRuntime(25714): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(25714): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime(25714): ... 11 more
W/ActivityManager( 173): Force finishing activity com.nicolasb.shuttle/.AppList
Update
This will happen if you have installed an app that doesn't have a proper name, only a package name.
Click to expand...
Click to collapse
This is now fixed (or at least should be). Thanks for the heads up!

Application updated to 1.1:
Considerable performance improvements
Bigger icons
Search and type-to-search
Click to expand...
Click to collapse

Oops! Forgot to click "Activate"!
1.1 is now up on the Android Market. If it's not yet updated in your browser, use the download link in the first post.

Good update. Just a suggestion for faster search. When pushing the searchbutton insted of a searchbar there is a grid with letters that shows, then you just tap the letter for the app name your looking for. Kinda like windows phone 7 has for contacts.
Thanks

Nick_Hrh said:
Good update. Just a suggestion for faster search. When pushing the searchbutton insted of a searchbar there is a grid with letters that shows, then you just tap the letter for the app name your looking for. Kinda like windows phone 7 has for contacts.
Thanks
Click to expand...
Click to collapse
That's on my priority list! I also noticed searching is too many taps away. Instead I might just pop the keyboard or use T9 to "dial" apps.