Database Develop

Seesmic on Android - issues on CM 4.2.5 ?

I hadn't used the desktop app before so when I heard it was out for Android it piqued my interest. I downloaded it and although it has a few things missing (lists and hashtag searching I think is missing) they're not important to me. Anyway the purpose for me posting here is to check if anyone else using Cyanogen's Mod v4.2.5 has issues with notifications not happening. This, for me, is the second app that doesn't run as intended using CM ROMs and I don't like that one bit. Before I mention it to Cyanogen I want to see if I'm the only one having issues.

I'm having a few problems, too. Sometimes the program will crash when opening/closing the keyboard, sometimes it will freeze when switching tabs, etc.

I don't think it's CM's issue. I'm having a lot of FCs with it on Amon_RA's ROM as well, think it's just not stable enough.

I mentioned it to them via Twitter and they said they'd look into it. For an initial release the interface is really good I think but notifications are a must. To make sure it wasn't the ROM in general I've tried three separate ROMs now and ran another Twitter program at the same time, same interval updates and the other program (I Tweet) got all updates. Stupid thing is when I was reading them I got Seesmic telling me there were updates now. I'm sure they'll fix it but they better do it fast or the ratings will drop it.

Amiga Emulator for Android

Hi folks, I spent a good part of my sunday (and friday night, let's be honest) to port UAE4All for Android. So here's UAE4Droid. Most games are working fine, don't expect killer framerates though (it should be faster on a Droid). I don't plan to actively support this app, so here's the catch:
-no sound
-physical controls only (that's why I post here, you can configure them btw)
-no save states (the original project does not implement them, and I'm no good at understand basics of the 68000 emulation)
-should be ok starting from Android 1.5 but I didn't test it (Dream on Cyanogen here).
You need to own a rom copy and some disks to use this legally, of course. If there's some good feedbacks, maybe I'll put it in the market (already done a couple of emulators there). Enjoy !
Edit 12/27 : Now with sound and touch controls on the Android Market

damn you did this in one day?

make it one and a half
It's a port, not that hard, once you got some Android knowledge, the basics of the SDK-NDK interaction, and the open source works from several people. And I left some parts (sound and touch controls), quite buggy/boring to code

Did you ever know that you were my hero? Seriously, great stuff! If you could add sound this would be the best thing I have on my phone!

Amazing. Superfrog works pretty well. If I could just insert all floppies at once it would be completely awesome.
If you're not planning on supporting this too much in the future would you consider making it open source?
It's completely fun to put android next to my old ami500, old 1200 and turn on superfrog on each

Oh wow...that's pretty impressive. Superfrog on my phone would be awesome! I'll have to try it.

Ok, hate to leave work unfinished so I added the sound and touch controls. Watch the Market, it should appear there soon.
btw to enable the sound on a HTC Dream makes the emulator a little more sluggish, well now at least you'll have the choice (or buy a 2nd gen Android device )

Not working properly. App asks me to force close when I'm pressing MENU button... Previous build (from first post) works properly. Can I please to fix this bug?
After all, great job

Damn, I didn't make that much changes, could you get me a log trace ?

Hmm It's weird... After a couple of restarts of phone, the app is working correctly... I will leave a post (and logcat) when this problem come back.

Sadly doesn't Install on Eclair.
adb install gives Error Message "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE"

Kubax83 said:
Sadly doesn't Install on Eclair.
adb install gives Error Message "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE"
Click to expand...
Click to collapse
looks like a modded ROM issue to me (this emulator is compiled for ARM, no doubt about it). Try the one from the market

Wow this works really well, playing Superfrog on it now Any plans to add save states to this?
I wonder how much better performance is on the droid. Superfrog plays perfectly on my G1 with frame skip disabled and sound off, having it on made it more jerky.
Also would it possible to have the escape key mapped to something, like the shutter button or as a menu item, i'm sure some games needed it to get into the menu.
Thanks for porting this!!

5 stars from me
works great, played with it a little. kickstarted 3.0 ROM, loaded game with no problems - but Hero's hardware isn't up to it. Maybe on my next android, with faster CPU and proper keyboard...

Only problem I have had is it doesn't seem to like some of my Kickstart rom files, it works fine with one of the 1.3 roms I had with WinUAE, but says Invalid for most of the others including 3.1, all of which work in WinUAE, any ideas?

what's the exact size of the non working roms ?

Non working rom size is as follows:
3.1 - 524,299 bytes
Just thinking could it be because it is a rom from Amiga Forever from Cloanto, do they use a keyfile for the rom?

No, because I thought every roms was 524288 bytes long. Will update the market version tonight

Blazing fast on a Droid/Milestone! Thanks a lot. Just the Mouse-Control is still a little buggy. For Disk-Activity you could use the green/red led! =)

how keyboard is emulated
Hi,
I have successfully set-up UAE4Droid, tried my favorite game, but it(Pinball Fantasies) needs alt or shift to control the game. I could not figure out how to play the game because of this. (Pressing alt or shift on the G1 does not work. )
Anybody know how to use these keys?
Thanks
Sandor

What is the advantage of HC over others

What is the advantage of using android 3.0 have over 2.2. and 2.3?
Install all three and really see no difference beside the slight UI changes.

evilPERSOn,
I had not yet loaded HC, so my advice is pure speculation. HC has an entirely different interface which acknowledges the fact that a tablet is in essence a tablet and not an oversized phone. So, as such, it works a bit more like a computer with. The speed and streamlined interface of a tablet. As I write this I really wonder why I have not cobbled it up. Well, it is only a matter of time.
Have fun
~Leko

evilPERSOn2009 said:
What is the advantage of using android 3.0 have over 2.2. and 2.3?
Install all three and really see no difference beside the slight UI changes.
Click to expand...
Click to collapse
well for starters this should be in general not development
second HC isnt just a slight UI change, it was MADE for tablets so if you want your tablet to be a giant itouch running android than install 2.2/2.3 but if you want a tablet you should install 3.0

^My bad. I had two tabs open. General and Development. Must have started thread on the wrong location.

1. HC uses GPU interface rendering.
2. HC is meant for a system like a nook with few buttons (good for us)
3.But HC's source is not in the open (bad for us).

poofyhairguy said:
1. HC uses GPU interface rendering.
2. HC is meant for a system like a nook with few buttons (good for us)
3.But HC's source is not in the open (bad for us).
Click to expand...
Click to collapse
Hopefully the source will be released soon!

For me i thought i would try hc on the sd card and just go back to froyo. I was hooked. I used it for two days on a class 2 card then i flashed, and ive tried to go back to froyo and get flash but i cant. The UI is just perfect, the live app switcher key is wonderful and so great to use, probably my favorite feature. Not to mention i love that the task bar is on the bottom, reminds me of windows and keeps the clock and keys out of my face. Honestly i hate the top notification bar on other versions, ive always hidden it on my droid. Being on the bottom is so nice and out of the way.
Its got its downsides, but give it 2 months.. apps galore, source files..... it will be really good to run.
Edit: not to mention, ive never lost data like on my droid while switching apps. Ive come back to apps ive had open for over 24hrs and its still in the same state
Sent from one of those missing Droids

altimax98 said:
The UI is just perfect, the live app switcher key is wonderful and so great to use, probably my favorite feature.
Click to expand...
Click to collapse
i'm using the samuelhaff's eMMC HC and i noticed that i can't scroll the app switcher, so i don't have access to all my previously run apps. is this normal?
loving HC, so far. the fact that it's designed for no hard buttons is just awesome.

i don't think the app switcher even scrolls on the xoom yet.

I have only played with HC breifly. But from what i know about it these are the following reasons to use it.
1. Market. Honeycomb is the first android os that will support having the google market. This provides a few things. Any of us who have played with Ipods and ipads will know that there are specific apps built for ipad. Now that Android 3.0 is built for tablet form factor, and officially supports the market. We will now see Tablet applicatons that provide higher resolutions, or new features. These apps will be built around the 3.0 os, and may not work on older operating systems.
2. Built for tablets. Everything we have had up untill this has been a phone operating systme built for a 3" screen ported to something with a 7-10" screen. The os is clearly built for phones there are things in there that just dont work right, or should not be there, but are there, on a fundimental level in the operating system. By adding native support for larger screens, and removing the phone items, it provides for a cleaner higher performance interface.
3. Interface enhancements. The UI has been built to support the larger form factor. This will provide easier navigation as well as soft keys as mentioned above, since alot of tablets are just missing physical buttons.
Unfortunatly the OS has not been released to the public. My guess is there is some contract between motorola (xoom) and google for exclusivity on their tablet. but dont quote me on that.

1) The web browser is much improved - even over Dolphin
2) The email client is much improved - even over K9
3) Contacts sync seamlessly with Google contacts
4) The keyboard is much improved - has a TAB key, has a "handle" to move the cursor around in text, has cut and paste features.
All of this is enough to make me swich to HC.
Downsides:
1) Many of my favorite apps cannot be found or downloaded from the Market - even though they worked fine on 2.1.
2) From uSD card, runs a little slower than 2.1, but not enough to bother me.

is the video accelerated? I could not take cm7..so slow.

winkler1b said:
is the video accelerated? I could not take cm7..so slow.
Click to expand...
Click to collapse
No. Same problem effects both I think.

Well, I switched and got my nook to recognize the sd (Class 2) partition. I expanded the image to use the 16 gigs too. I love it. The Live App switching is nice. It actually feels more like true Linux (I am thinking KDE) than any other droid system. I just can't handle the lag when booting apps (probably a combination preview/sd card). I am a teacher and grade on my Nook, so I need speed. But, I am excited about this. Thanks a lot Deeper Blue. This will be stellar.
The true app switching is almost priceless as is the efortless interface.
~Leko

[Q] Disable auto-closing apps

Well i searched around XDA a bit and found many threads related to this bt all for WM and not android.
Multi-tasking is getting a bit tough. Apps get auto-closed after sometime.
Samsung Galaxy SL i9003
Stock firmware and everything stock, nothing chngd much. Only apps installed from the Market.
Say m surfing the opera, and even if a small app like messaging is open and aftr some roaming around when i return of opera, it has closed.
PS - Above is jus an example so dnt claim Opera is a power-hogger so it wil b to open up ram for other apps and all......
So any way of disabling the auto-closure of apps?
Love XDA

@ mod who moved it...
Its related to i9003 nt i9000.
Anyways tnx for moving. Wil get more views here....

Any dev der? Help!
Sent from my GT-I9003 using XDA App

Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???

Exactly.
There's an app on the market, Spare Parts, in it ders a option on hw android handles suc apps.
There r two options. Normal and aggressive. Keep it normal and try and c if it helps.
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Exactly.
I hv migrated frm Symbian, and m a hard multi-tasker, and disappointd with Android jus cos of tis...
paleozord said:
Personally, I cannot believe that this doesn't get complained about a lot more vocally and a lot more often, especially as it is common across ALL Android devices running 2.2 or beyond, not just the Galaxy S. It is a MAJOR usability issue in the operating system and one that is a complete dealbreaker for me.
Since 2.2 any application left running in the background is automatically closed by the system after a few minutes of inactivity, regardless of memory availability/needs or power consumption. This approach is far from acceptable for things such as EBuddy or any other msn-style instant messaging client which the user may want to leave open in order to stay logged in, so as to remain constantly available and reachable by other parties using the same service. This is just one example of a type of application I might want to leabe open and running in the background, but there are plenty of others.
The fact that the entire Android platform has essentially removed multi-tasking as a feature of the OS as of version 2.2 is astounding and appalling to me, and it's very surprising not to find more people just as offended by this on a more regular basis. What's worse, no matter how rooted or custom-ROM'd your device might be, there seems to be absolutely no way to override or disable this behavior as it is hard-coded into the OS kernel at a fundamental level. We basically have a first generation iPhone on our hands now, thanks to this latest innovation.
Closing apps when memory and system resources are low is one thing, but closing them just because the user hasn't attended to them in the last five minutes or so? Ridicullous. If you wouldn't want your desktop computer shutting down all your open/background applications every time you go for a coffee break or take a 10-minute phone call, what makes the Android developers think users want this done on their smartphones???
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Is this the reason why I have to constantly log back into Evernote, and Tweetdeck every time i wanna have a look at them?
The whole concept of syncing periodically doesn't work anymore because they are constantly logging out on me.

Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.

I wonder y others @xda & @google dnt feel tis....
paleozord said:
Unfortunately neither Spare Parts nor any such custom tweaking app seems have any effect on this berhaviour under Froyo or Gingerbread. And yes, the system auto-close is the reason that re-logging into connectivity apps every time you open them is necessary. Since they have been shut down and are no longer running, you are essentially re-launcing them anew each and every time. Hardly ideal.
Previous "old school" smartphone platforms like Symbian and Windows Mobile 5/6 had multi-tasking incorporated into their basic functionality. It's really a shame that shiny new operating systems like Android/iPhone make it such a struggle. Up until and including Eclair (2.1) leaving apps open in the background was completely possible, but as of the present moment WebOS is the only "new age" smartphone OS that still allows it, and unfortunately it hasn't moved along in other development areas very quickly at all.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Erm....why do you think people flash custom roms?!
GTi9000 insanitycm010/insaneglitch

slaphead20 said:
Erm....why do you think people flash custom roms?!GTi9000 insanitycm010/insaneglitch
Click to expand...
Click to collapse
Custom ROMs do not change or affect this system auto-close functionality in any way. At least I've never seen any that did so successfully. It seems to be coded too deeply into the OS to be changed, from what I can tell. That is, I'm sure theoretically it *could* be changed, but most custom roms I've seen tackle far more surface-level interface issues and not the way the kernel manages processes in the background.

I didn't realise this happened after 2.1... I already was thinking why all apps were getting closed so fast after I updated my i9000 to froyo and then to 2.3. I just bought i9100 mainly because of the 1gb ram and still, with 400mb free ram, apps getting closed after couple of hours. (Not minutes, or even seconds like i9000, thankgod).
Autokiller lets you manually change some value of a running app, so it won't get killed... unfortunately this isn't automated so it's no use.

The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.

Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
paleozord said:
The time before auto-closure can sometimes vary from device to device.. I've tested on two Froyo devices other than the Galaxy S, each from different manufacturers as well, and apps rarely make it past ten minutes before being shut down on any of them. I've never seen anything make it a couple of hours so that's a new one.
I've actually gone back to my Motorola Defy running 2.1 for now, specifically to be able to multi-task again. Sadly there is a 2.2 update available over-the-air for it, but I keep declining because I just don't want to lose the ability to multi-task. Unless some future version like Ice Cream Sandwich restores control to the user, Eclair may very well be the last edition of Android I ever use.
Or should I say AndroIPhone, since that is what it has become.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

ggclanlord said:
Eclair actually allows u to multi-task normally?
No issues lik froyo?
Working lik "old-school" OSes's multi tasking?
Click to expand...
Click to collapse
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).

Tats really Awesome!
paleozord said:
Correct, applications are left open and running in the background indefinitely until the user chooses to close them. Using a good multitasking app like TaskSwitcher or Smart Taskbar you can switch back and forth between open apps as much and as often as you like, or go away for hours without anything ever closing on you. I'm doing it presently on my Defy with no issues at all, just like older operating systems allow(ed).
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

ggclanlord said:
Tats really Awesome!
Click to expand...
Click to collapse
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!

I guess so it'd b more effective if tis is wrttn to Google...
paleozord said:
It's certainly a saving grace for Android that Eclair devices still provide multi-tasking functionality for those who insist upon it, though at the same time it sucks to see all these super powerful, souped up Froyo and Gingerbread devices being released monthly and having to snub them because of the deficiency in the newer OS.
Please, please fix this in Ice Cream Sandwich or Chocolate Souffle or Lemon Tart or whatever desserty moniker the 2.4 flavour of Android takes on. Or at the very least give the user the option to select an operational mode (auto-close or manual manage) just like many devices offer for battery management, with performance mode versus smart-saver mode etc..
It's hardly a smart phone without multi-tasking!!
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Cn any1 tel me whthr tis issue is der @GB o nt?
M on Froyo cos GB nt yet released for my device (only a Dev update yet)

I can't say with 100% certainty but I'm reasonably confident it's the same under Gingerbread (2.3). Google considers this "feature" of the Android operating system to be a significant improvement and benefit, so they're not likely to remove it on their own anytime soon unless they get a massive influx of complaints about it.
The best we can hope for is probably a user-controllable setting of some sort that determines the degree of system aggressiveness in auto-closing background applications. There are already plenty of third party root-based utilities available in the market with similar settings, but they only affect their OWN auto-closing tendencies and do not override the system itself's default auto-close behaviour. I know this because I have tried them all at the lowest possible setting levels, and everything still gets closed in the background just the same.

[APP][UPDATE 2.7.12]FireFox 12 Alpha 1

Im testing firefox11alpha 2
Its fast and very smooth even smoother than stock ICS browser at times
lots of feature like syncing your desktop firefox bookmarks with mobile Device, addons, Flash support
Remember its still alpha not beta but should be beta soon seems really stable so far
also firefox alpha builds are codenamed Aurora in case you get confused with the app name
test youtube desktop view on both browsers firefox was really smooth were stock lagged
Download link
http://ftp.mozilla.org/pub/mozilla....a-android/fennec-12.0a2.en-US.android-arm.apk
if link above goes down or want to check for latest alpha build
https://wiki.mozilla.org/Mobile/Platforms/Android#Download_Aurora
EDIT
updated to 12

It's still horrible for me. Here's why:
I can't get any add-ons to work because they aren't updated...that's to be expected since this is an alpha...but even the ones that are updated, like ab+ aren't installing.
many pages take FOREVER to load, and the ones that do load don't load the whole page.
If I scroll down on a long page, the rest of the page loads, but the top of the page will unload.
Text takes forever to become clear enough to read, and text reflowing takes even longer.
The tab button only works once out of every dozen or so times I press it.
aurora constantly runs in the background unless I freeze the app, and it's killing my ram.
Until every single one of these issues is fixed, I won't even consider using this at all....not even as an alternative. It's really sad to see that the top-dog on PC is so horrible on mobile, because all the potential is there...they just can't understand that most people don't have 80MB extra ram on their android to dedicate to web browsing!!

this is a huge leap in the right direction compared to previous mobile versions
Its alpha so expect things to be ironed out eventually
Everything loads fast and refresh fine for me (im using wifi)
I did noticed it uses almost double resources than stock browser but still its alpha
desktop firefox they significantly drop the ram usage im sure they will do the same with this
also yea one thing i noticed is when page refresh when swiping fast on long pages im sure it will be fixed doesn't really bother me it pretty much refreshes instantly
and yea i noticed it still runs in background and with the resources is uses it could be a problem for some people
I have 185 ram open i just go to recent app and swipe it away it will close

Bump new alpha 12

I don't know why firefox seems destined to suck on mobile devices when it's so good on PC's. Every version I've tried has just been so far behind its mobile counterparts that it's just sad.
Mozilla should take some pointers from the new Chrome beta - I just started using Chrome on my Nexus and it is an amazingly fast and smooth browser that also offers desktop sync.

Perfect for pc. Still trash for mobile.