howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views
I think the problem with this is that processes in Android drop in and out of memory. So, for example, Rosie will be dropped out of memory to make way for the browser and a heavy web page. Applications that are dropped have their state saved, so when you go back to them you are taken back to the position you were in. However, big processes like Rosie take a noticeable time to get back to where they were.
I think the key to speeding up Hero is increasing "memory" so that processes don't need to get dropped. Hence why I've been looking for that elusive perfect Compcache build. If we can make 100Mb of usable memory work more like 200Mb or more, then that might do the business.
ahh i see, but would not doing this speed up the pick up time of the for instance rosie apk?i can see where you are coming from because if we had more memory we would not need to drop the rosie out of memory, im thinking tho if you had both more memory and a process manager it could be some speedy stuff...hmm
Changing process priority probably wouldn't help, because (using Rosie reloads as an example) there isn't a process to prioritise - Rosie isn't actually there any more to give increased priority to. Maybe you could give priority to the process that does the reload but the subjective speed increase would be I think negligible, because loading from sd or memory is going to depend on the speed of the memory, not how much processor grunt the reload process gets.
A nice idea but I think the way Android works would make it problematic.
cool cheers for the insight into android glad someone knows there stuff lets hope someone comes up with a working solution
hmmm. also i think that android itself is doing it's job not sooo bad. i can't imagine that loading back the rosie process is not getting enough cpu time, that would be a huge design failure ...
correct me if i'm wrong, but i really hope, that android is intelligent enough to do this on it's own.
Has there been any optimization of hero or just a straight port?
bademasta said:
hmmm. also i think that android itself is doing it's job not sooo bad. i can't imagine that loading back the rosie process is not getting enough cpu time, that would be a huge design failure ...
correct me if i'm wrong, but i really hope, that android is intelligent enough to do this on it's own.
Click to expand...
Click to collapse
but what ur missing is that hero is not built for the magic with 192mb of ram is it now? so somewhere u are guna have to make some OPTIMIZATION
Android is very good at managing resources and applications...
Having developed some Android applications, I can't really think of a good way to improve on the current system. Perhaps all I could suggest is running a Manual Process Manager... and closing applications/Services which you no longer are using but are still running.
A quick tip would be, when you are running an application and no longer need it... use the back button, not the Home button.
If you use the Back button, the application will Destroy... the Home button will 'Pause' the application and assume that you will want to come back to it later.
Android maintains a chain of open Activities, you can keep opening new Activities and it will maintain the old one you were running in a 'Paused' State. If you keep moving forward and opening new applications, but never go backward... you will end up with a lot of things running... so each time you open something, it may need to free up some memory by closing an application that has not been used for a long time which is still in a paused state.
You could speed things up in that scenario by running a task manager and killing processors... or I usually just reboot my phone...
Here is a diagram which shows the Life cycle of applications. Services have a slightly different Life cycle.
{
"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"
}
You can read more here
Hopefully this info helps, sorry for wandering a little bit bit off topic...
Hello,
Before tweaking Android to try to run Rosie properly, perhaps we can try to optimize Rosie ?
For example, in the first roms we found here, Rosie.apk was about 4Mo. Now in the Qtek 1.2 swap, it is only about 690Ko. Here, we can find a 330ko version.
But perhaps some people can do the same job to optimize all the UI of Rosie, i think about all the widgets ,the browser, the keyboard ...
The more lighter UI Rosie is, the less memory Rosie need ?
Scargoll.
I did that but it's not finish yet. i just use a png optimizer so i can make every apk a bit smaller but my problem is that i don't really know how to sign an .apk file
when i know how to do that will have an fully working hero rom with compcache about 60 mb ...
MarcoNieddu said:
I did that but it's not finish yet. i just use a png optimizer so i can make every apk a bit smaller but my problem is that i don't really know how to sign an .apk file
when i know how to do that will have an fully working hero rom with compcache about 60 mb ...
Click to expand...
Click to collapse
Good news !!!
I don't know how to sign apk files, but i found this, perhaps this can help ?
http://www.anddev.org/signing_your_apk-application_for_release_keytooljarsigner-t3069.html
Scargoll.
I follow this tutorial more than 3 times now. when i want to install the signed apk to my phone there ist always an error -- > can't install ...
You're trying to install an app that's already running. You need to flash it with an update.zip+script or copy it with ADB when your device is in fastboot.
Ill see if I can optimize rosie's images, I brought down the HTC_IME size down by 25% just by optimizing the png images.
Sizes of the IMAGES in rosie.apk, not total size.
141 KB smaller than the original. Good result if I say so myself!
bump.
No one wants to continue? I'll optimize any image I can find and reduce the size of all images by 20% as well ending up with a probably faster running phone
Can you post directions on how to optimize???
A lot of people have already done some work trying to optimise Rosie. Speaking personally, the ne thing I always do when I install a new Hero build is to push the Rosie from
http://forum.xda-developers.com/showthread.php?t=532822
onto the phone. It's the stablest I've found that manages to do everything in a small-ish footprint without making it crash prone and buggy. There's a 300-odd K one in the same thread that I've never been able to get to work. There's also a 300-odd K one that came with Drizzy's 1.2 Hero release which was buggy - his next release took the file size back up to 3.5Mb!
tl;dr: there are already optimised Rosies, but not all of them work particularly well.
Has anyone been able to tweak the drivers to get slightly better fps or anything?
briggs81 said:
Has anyone been able to tweak the drivers to get slightly better fps or anything?
Click to expand...
Click to collapse
I wonder this too.
sibbor said:
I wonder this too.
Click to expand...
Click to collapse
My main phone is an HTC device running Android on sd card.. developers were able to get the fps to run up to 24, which is about 6-7 lower then a stock Magic.. not bad.. for a 2 year old phone!
Perhaps when other things are going smoothly someone with that type of knowledge will be able to play with driver software or something.
I think right now, Magic users get about 27-29 fps.
Related
AutoKiller
This app is designed to help make your phone run mutch smoother by configuring systems internal memory management routines.
It also features a full-powered process manager which lets you control your whole system.
Features:
- process manager
- simple/advanced mode
- presets
- shortcuts to presets
- settings reapply on boot (no init file hacking, i use a service)
- pages/mb views
- statistics
i plan to add a few more features, your feedback is welcome.
{
"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"
}
reported to work on:
-Nexus One
-Hero
-Spica
-G1
-MyTouch/Magic/G2
-Liquid
-Milestone/Droid
-Behold II
-IE 6010
-I 7500
-LG GW620
-Pulse
-XT800
-...
official homepage has a lot more info.
Thank you for your support, and for your kind donations thus far.
If you like my work, and can afford to donate a couple of dollars to buy me a beer, please use the link below!
rs
Seems to make a bigger difference on resource hogs like the Sense UI. I tried it running MoDaCo's Desire ROM and it seemed to be faster. I don't notice as much of a difference on Cyanogen ROM's. I am still keeping it installed, even running CM. It hasn't given me any problems and the phone does seem pretty snappy (Although not much better than before, with the Desire exception).
ccunningham83 said:
Now maybe it is just me, but in your "reported to work on:" section in your post, it never mentions the Nexus One. That is kind of important when you are posting in the "Nexus One" sub-forum.
Click to expand...
Click to collapse
you are right, of course i wouldn't post it here if it couldn't run on N1
post is fixed now.
Been using this the day I got my Nexus One. Does it work? I have no idea! I have no reference points to compare it with.
It's small though and certainly isnt causing any problems. Worst case it does nothing, oh well, best case it helps alot. Pretty sure thats a no-lose scenario.
Incoming flood of posts about "killing apps is bad for your phone"
Shouldn't these types of things be posted here?
Paul22000 said:
Incoming flood of posts about "killing apps is bad for your phone"
Click to expand...
Click to collapse
And I guess I'll be the one to start.
Read my signature. 39 apps running and 0 apps running have the same responsiveness. Killing apps does nothing but free unneeded RAM.
dumbestcrayon said:
And I guess I'll be the one to start.
Read my signature. 39 apps running and 0 apps running have the same responsiveness. Killing apps does nothing but free unneeded RAM.
Click to expand...
Click to collapse
Task Killers are needed, just not what some people are using them for. For example, the speedtest.net app has a bug where when you back out of the app, it still uses your gps draining your battery, having a task killer will allow you to close that program without having to reboot your phone.
McFroger3 said:
Task Killers are needed, just not what some people are using them for. For example, the speedtest.net app has a bug where when you back out of the app, it still uses your gps draining your battery, having a task killer will allow you to close that program without having to reboot your phone.
Click to expand...
Click to collapse
Lol that's funny because that app is the only reason I use a task killer. It is definitely needed for killing apps with bugs but not for keeping apps out of the RAM for no reason.
dumbestcrayon said:
And I guess I'll be the one to start.
Read my signature. 39 apps running and 0 apps running have the same responsiveness. Killing apps does nothing but free unneeded RAM.
Click to expand...
Click to collapse
A bit misleading....
I thought the video showed someone with 39 apps running comparing to 0 apps running.
=\
dumbestcrayon said:
Lol that's funny because that app is the only reason I use a task killer. It is definitely needed for killing apps with bugs but not for keeping apps out of the RAM for no reason.
Click to expand...
Click to collapse
unfortunately there are many applications which cannot sleep properly, or don't release resources. (the most annoying I met with was TasKiller itself!!!) if you have the time to find out which are these one bye one, you can kill them any time you finish using them. but if you don't want to mess with this, setting lowmemory killer is the best approach as a fix.
"free" memory is not useless: it is always filled up with cache of your most used applications. so you get resource-consuming applications killed, and got cache with preloaded data your phone will probably use.
AutoKiller 2.0 is out
changelog:
* process manager added
* new ui
* lots of stability and speed improvements
* mb view by default
Does running Advanced Task Manager alongside this app make sense? Is it redundant, helpful or hurtful?
McFroger3 said:
Task Killers are needed, just not what some people are using them for. For example, the speedtest.net app has a bug where when you back out of the app, it still uses your gps draining your battery, having a task killer will allow you to close that program without having to reboot your phone.
Click to expand...
Click to collapse
You can just use the built in task killer to do that... menu, settings, apps(programs in a Desire ROM), manage apps, select the app(might want to hit menu, then select running apps only)... then force stop.
Granted, a task killer makes it quicker and easier to bring this list up, but it calls on the built in task killer to actually kill the task.
To the OP, great work! Looks nice! The ability to change how aggressive you want the auto task killing is nice to have, and it is nice to have eye candy when killing a rogue app. All though I don't ever use these sorts of apps, I like what you have done with yours!
whodatfever said:
Does running Advanced Task Manager alongside this app make sense? Is it redundant, helpful or hurtful?
Click to expand...
Click to collapse
if you use ATM to kill apps, id is redundant, AK can do it too. ATM may hav some advanced features you need, please check it.
AutoKiller 2.1 is out
changes:
* process manager is on steroids
* stability improvements
Description dev says: "root required for all features to work"; does this mean some features work on the unrooted Nexus as well, or nothing at all??
I don't feel like rooting my Nexus, but am looking for a good taskkiller..
bmszabo said:
Description dev says: "root required for all features to work"; does this mean some features work on the unrooted Nexus as well, or nothing at all??
I don't feel like rooting my Nexus, but am looking for a good taskkiller..
Click to expand...
Click to collapse
Actually process manager part fully works without root (keep alive function connects to minfree and it wont work obviously) but it will just doesnt work, no FC or strange behaviour I also would like to ask you to report back how it behaves on a non rooted device, as i could only test it in dev environments.
--egyébként meg üdv itt --
ratson said:
Actually process manager part fully works without root (keep alive function connects to minfree and it wont work obviously) but it will just doesnt work, no FC or strange behaviour I also would like to ask you to report back how it behaves on a non rooted device, as i could only test it in dev environments.
--egyébként meg üdv itt --
Click to expand...
Click to collapse
ATM just uninstalled (last weeks getting slower, FCing apps, not sure if it was ATM's behavior), installing AutoKiller; I'll keep You posted on experience on a not-rooted, stock Google N1!
Greetz,
Köbüki, a harmincadik századi rokon
AutoKiller 2.2 is out:
* ordered presets
* custom preset
Geek 4 Me is proud to release
Fresh Toast v1.1 by toastcfh and flipz
First off let me remind everyone that this is a dev rom. Meaning it is a proof of concept type rom and is NOT going to be fully functional. This is built on the .27 kernel which means no camera and no light sensor (causing bottom lights to not come on). With that said...!
New features in 1.1:
Full scaling overclocking. You can now use setcpu to set the speed. Anywhere from 245mhz to 767mhz - toast. Thanks to phh and maejrep for their help. Download setcpu from the market for $1 or free here. Note: When you set it up and asks for device, scroll all the way to the bottom and pick custom!
BFS (Brain **** Scheduler) version 316 has been added and customized. This dramatically reduces latency on the phone. While it doesn't increase benchmarks it will really increase the usability and smoothness of the phone. Go here to learn more. -- toast. Thanks to maejrep for help.
Fixed apps2sd and ext4 not working together
Removed AutoKiller. It will likely still show up on peoples phones because it's on your /data/ partition but I decided to remove it after I realized it was reporting location and who knows what else. I already created a modified version that leaves the ads for the developers sake but strips the Flurry reporting however it's not playing nicely with installing. I'll get an update.zip posted when I figure out it's problem. -- flipz
Found and fixed a bug in HTC/Sprints code that was causing 99% cpu usage, draining battery, and causing overall slowness. This bug doesn't seem to affect everyone however it was affecting me big time. It exists in every Sprint 2.1 RUU based build. --flipz
Features:
Custom kernel -- toast
OVERCLOCKED to 767mhz -- toast, with help from phh and madcoder
Compcache and ramzswap enabled -- toast and flipz (? and ? if you don't know what they are. **read warning below)
Ext4 support -- toast (has many benefits over ext3. ? for more info)
Fixed vanilla lock screen (including airplane mode/emergency call glitch) -- flipz
Some modified artwork (toolbar and selector, because toast loves it) -- flipz
Newest autokiller (more info on this app: http://geekfor.me/faq/autokiller)
Disabled home screen menu from popping up when using menu button to unlock --flipz ( patch to disable menu to unlock if you prefer: http://geekfor.me/fixes/bugfixes-requests-lock-screens)
Uses Fresh Rom 2.0d as it's base so all other fresh rom features are in here -- flipz
Not working:
Camera
Light sensor (causing bottom lights to not come on)
Please don't ask when these will be fixed. The short answer is they require the new kernel to work on Android 2.1, however we can't enable all these cool features on the new kernel until we get the source from HTC... again. But as always, toast is working on fixes. So buy him some coffee.
Compcache/ramzswap questions:
How do I make it work? Your sdcard must be partitioned with a swap partition. Most anyone running apps2sd will have this already. Other than that it's automated.
How do I know if it's working? Open an adb shell and type in "free". If you have "swap" listed with any numbers next to it, it's working.
What is required to run it? A class 6 sdcard is highly recommended for speed and stability
How do I disable it? Just delete or rename the script at /system/etc/init.d/compcache.sh to anything else and reboot
**Will this wear out my sdcard? Just like apps2sd, ramzswap puts extra strain on your sdcard. If you are using a decent sdcard then it shouldn't be a problem. Many professional grade HD video cameras use sdcards as their medium, and they don't burn out. If you are using a low quality card then this may cause it to prematurely fail. Do not blame us. You have been warned!
Overclocking questions:
How do I know if it's working? This is hard to prove, other than to say you can run benchmarks and clearly see it. Any CPU applications (including setcpu and OC widget) are going to continue to report the stock speed of 528mhz. Full scaling IS coming soon which will allow you to select the correct max speed.
Will this hurt my phone? Toast and I have been running this for days with no ill effects, even when stress tested for hours. There were no crashes, no errors, and no significant heat gains. However, like always, you are doing this at your own risk and we can't be held responsible.
Do I need to use setcpu/oc widget? They will provide you 0 benefit. The phone has HTC's power manager enabled which means it will throttle up the CPU when it's needed, and throttle it down when it's not. As mentioned above, full scaling is coming soon which will allow you to adjust the speed through those apps if you choose.
Make sure you are using a temperature monitor if you are overclocking and watch your temps.
How do I flash this rom?
It is very likely that you can flash this rom on top of Fresh 2.0d without a wipe and have it work without any issues, however the following procedure would be recommended (assuming you have a class 6 sdcard).
Boot in to RA and do data wipe
Format your sdcard with 32mb swap, 512-1gb ext2, and the rest fat32
Convert ext2 to ext3, and then ext3 to ext4
Flash the rom and reboot
Download: http://geekfor.me/new-release/fresh-toast-v1-1/
Info:
...................................
Yess been waiting on this bout to flash
You all are amazing.. Im downloading now.
by fixing the lockscreen vanila you mean you can change wallpapers? is it asop?
magicalan said:
by fixing the lockscreen vanila you mean you can change wallpapers? is it asop?
Click to expand...
Click to collapse
No, sorry about the confusion. Just meaning it has the working vanilla lock screen including the fix where the emergency call button would show up after being in airplane mode. And no it's not AOSP, it's based off of fresh rom. It says that.
Goodnight all!
It does seem faster especially in sense
Love it and you all, in a very manly way!
You guys are bad ass, flashing now. Thank you!
BENCHMARKS
Best scores received so far Will be updating if I get better- Screen shots might be different
Linpack: 5.022 mflops
BenchmarkPi: 6298 ms
Neocore: coming soon
{
"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"
}
How's battery life?
Yeah the question above me ^^^^^^^
Try it and see?
Technically battery life should be about the same as whatever you're getting now. The speed increase is 'on demand' so unless you spend all day doing cpu intensive tasks (and no, phone calls aren't cpu intensive ) you should be fine.
I'm going to wait for the .29 kernel source to be released before I play with this. Unfortunately I need my camera.
Jus10o said:
BENCHMARKS
Best scores received so far Will be updating if I get better- Screen shots might be different
Linpack: 5.022 mflops
BenchmarkPi: 6298 ms
Neocore: coming soon
Click to expand...
Click to collapse
Nice! Would you mind sharing your settings/setup? You are currently kicking my phone's trash.
Trying it just to give it a shot but not keeping it till I get a class 6 card. Noone in my area sells them. Max is 4 atm. Hate living in an area where technology can only be acquired online.
smw6180 said:
Try it and see?
Technically battery life should be about the same as whatever you're getting now. The speed increase is 'on demand' so unless you spend all day doing cpu intensive tasks (and no, phone calls aren't cpu intensive ) you should be fine.
I'm going to wait for the .29 kernel source to be released before I play with this. Unfortunately I need my camera.
Click to expand...
Click to collapse
I spend all day using Google Nav
Costa276 said:
Trying it just to give it a shot but not keeping it till I get a class 6 card. Noone in my area sells them. Max is 4 atm. Hate living in an area where technology can only be acquired online.
Click to expand...
Click to collapse
I am surrounded by retail stores and I only buy technology online. Amazon and Google Shopping are your friends.
I am enabling JIT now to see if I can get some more competitive benchmark scores.
danknee said:
I am enabling .jit now to see if I can get some more competitive benchmark scores.
Click to expand...
Click to collapse
Me too! Just waiting for it to d/l. 5MFLOPS just with the clock is amazing enough, I can't wait to see what it hits with JIT.
Mad props guys!! Nice work.. hope you guys can get it on .29 kernel
abcdfv said:
Me too! Just waiting for it to d/l. 5MFLOPS just with the clock is amazing enough, I can't wait to see what it hits with JIT.
Click to expand...
Click to collapse
I'm positive that Jus10o's scores are with JIT enabled. Without it, I can't even get close to those scores.
Some of you might remember the free windows mobile game Shift. It was really easy to play, but extremely addictive.
I waited for an android port for more than a year, and finally when i didn't see it ported i decided to do it myself So, no matter if you spent long hours with this game, of if you never heard of it before, here's a chance to play it on your phone/tablet/ereader/microvave oven or other android device
The game mechanics and scoring system are identical to windows mobile version, however the graphics and coding were redone from scratch since i didn't have sources for the original shift anymore.
I don't have an android market account and it's not likely i'll be getting one any time soon, so grab it here:
http://slideme.org/en/application/shift
{
"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"
}
Or in the post attachment.
And some screenies:
One day, i'll have to make a youtube video of the game, but i didn't get around to this so far.
Initially, i developed it for myself, but now that i'm satisfied with the results i see no reason not to share it. After all we all love and use freeware apps
It's my first android app and i was learning java, android api and the engine i was using as i went, so it might not be exactly perfectly optimized. But it does work smoothly on a G1, and the graphics turned out rather nice. It also scales properly to other screen sizes (though graphics won't be as crisp of course): I tested it on a motorola milestone and the android emulator with a few other screen resolutions.
I don't really plan to develop it much further, since i'm rather satisfied with it. Sure, i have a few ideas on how to make it work even better an some tricks i learned along the way, but that would probably take a complete rewrite and right now i'm not really in the mood for that So the game is provided as-is, but i might try to fix any really serious bugs.
If you feel like buying me a beer (or helping me get an android market account), the donation button is right above my avatar
By the way, if you think about trying to write your own android game, don't forget to check out andengine. That's a really powerful, and yet easy to use 2D game engine.
I'm getting an Access Denied message when clicking on the link.
Yes, me too.
And I really like this game too. Was playing it while it's available for WM6.1 QVGA screen. It didn't work on my WVGA HD2 last time. So, happy that it's coming to Android..
nijnvy said:
I'm getting an Access Denied message when clicking on the link.
Click to expand...
Click to collapse
Oops, sorry about that. It seems that the link worked for me only because i was logged into SlideMe. I'll fix that later, and meanwhile i uploaded the game as an attachment to the fist post.
[EDIT]
It turned out that the app wasn't visible publicly until it got approved by slideMe. The link should work now.
[/EDIT]
Very cool game! Thanks for sharing!
Nicely made game. Thanks!
great port! i'll try it later. thank you!
btw, you should really put this in the market, or it might get stolen.
http://forum.xda-developers.com/showthread.php?t=900923
Thanks! Pretty fun game!
The Link for the WM version its very old! i want to try in my tp2! the version WM, you can upload the wm too pls!??
nice game.... works great on MyTouch4G
Very cool interface. Enjoyable with a high chance of replay.
I second the other member's notion to place this into the market. Your current version is AOK for release.
Perhaps there's another reason why you wont?
this game is fantastic!!! it runs amazingly on my hero, and I love trying to get huge combos!! 5 stars!!!
Sent from my HERO200 using XDA App
EDIT : there seems to be a bug in the app. sometimes when I switch to another app via homescreen or long holding the home button, the gray bar underneath the notification bar that tells the name of the app doesn't go away. and you should put this on the market so we could get the updates.
!!!!!!!
If I'm not mistaken I remember this from my last WM phone (samsung omni) This is a fun game!
Excellent remake.
Makes me wonder though that what this game would be like if it had a mode with accelerometer enabled "physics". Tiles would fall freely to the tilted direction (only one direction at a time in tetris-like fashion) Angle of the tilt would off course relate to falling speed.
It would be the core mechanic with a little bit of action and accuracy.
I tested your game out and it is really good (never played the original), all I can say is make sure you put it on the market as XDA devs have had their apps uploaded to the market by someone else trying to make some quick $$
Cool thanks.
Thanks for the feedback, i'm glad it works on your phones and you like it
As for the accelerometer control, i thought about it, but i'm afraid it would be just something you try and disable, as it will get in the way of the gameplay instead of enhancing it. But if i ever get around to rewriting this game to properly support high-res screens i might try implementing something like that. For now i think gestures control is easy enough. And just in case you didn't notice, the gesture can be performed anywhere on the screen and doesn't have to be long - only the width of a single block is enough.
hecthork said:
The Link for the WM version its very old! i want to try in my tp2! the version WM, you can upload the wm too pls!??
Click to expand...
Click to collapse
Yeah, i know the project website is down, but it's still easy to find. However i'm afraid it might not work well with VGA or higher res screen. At least the winMo version didn't work on a HTC Diamond. But i guess there's no hurt in trying.
KLBrey said:
Very cool interface. Enjoyable with a high chance of replay.
I second the other member's notion to place this into the market. Your current version is AOK for release.
Perhaps there's another reason why you wont?
Click to expand...
Click to collapse
Yeah, i'm aware of that a**hole stealing other people's work. But right now i don't feel like paying 25 bucks registration fee without even a potential way of getting the money back - google doesn't allow selling apps from my country (yet).
Hi
I remember Shift very well (played it on Ipaq h3970)
Unfortunately I can't run it on Samsung Spica (i5700)- FC right after starting, logcat attached.
Phone config:
-Samdroid 1.3.1(deodexed Eclair, info)
-kernel- Xmister's STD Eclair (info)
-graphic drivers- mixed files from other devices v3 (info, as one of developers I've tested those drivers on everything I could and there were no problems with other apps)
gen_scheisskopf said:
Hi
I remember Shift very well (played it on Ipaq h3970)
Unfortunately I can't run it on Samsung Spica (i5700)- FC right after starting, logcat attached.
Phone config:
-Samdroid 1.3.1(deodexed Eclair, info)
-kernel- Xmister's STD Eclair (info)
-graphic drivers- mixed files from other devices v3 (info, as one of developers I've tested those drivers on everything I could and there were no problems with other apps)
Click to expand...
Click to collapse
I'm afraid it might be a problem between the engine i used and your device. Could you try running the following app and one attached to this post?
http://www.appbrain.com/app/andengine-examples/org.anddev.andengine.examples
The one above is a demo of the engine's capabilities, and should be compiled against the latest engine version. The attached app is just some random quick test i was doing but it uses the same lib version as shift. So if one works and the other doesn't it will mean that compiling with newer engine version might fix the problem. It will take some time but it's possible. However if none of these work, then i won't really be able to do anyting about it
mr_deimos said:
Could you try running the following app and one attached to this post?
Click to expand...
Click to collapse
The one from AppBrain- always FC when starting ShapeModifiers and Irregular ShapeModifiers (both demo and benchmark):
Code:
W/dalvikvm( 8065): threadid=3: thread exiting with uncaught exception (group=0x4001b180)
Rest of tests works fine.
Attached apk- works fine
i know this was discussed before but i'm asking now after months and weeks of usage
is the device affected by the small amount of avilable ram ????
does this small amount of memory lead to lagging or reboating ??
i m going to get the device soon so i m worried about that issue
I wouldnt say it has a "small" amount of memory, just less than others.
I would consider myself a moderate user, I learned on WM5 and up to 6.5 to keep my unused apps down and my memory clear so I have not run into any problems here.
I have seen a few very brief frame drops in a game while something is going on in the background but it was very minimal and did not detract from my joy of the device.
The built in task manager does not accurately read the available ram as the advanced settings does which can be mis leading. Cleaning out of lot of running processes clears up even more. Sense eats a fair amount but I personally like it.
This is my first main Android experience and it has been nothing but a pleasure so far. Again I am a moderate user tinkering with a new to me OS. I email a lot, text a lot, read RSS regularly and surf the web a little bit. The rest is with the apps. Things have always loaded quickly and so far not crashed.
It has enough RAM. I had a MyTouch 4G for 8 months and now the Sensation, both have 768MB of RAM and neither phone has slowed or froze at all. A lot of phones only have 512MB of RAM.
honestly, if you need a gig of ram, you're either a dev who needs the resources, or your desktop PC is as cluttered as your closet/garage and cant be bother to clean it
xdafun4all said:
does this small amount of memory lead to lagging or reboating ??
Click to expand...
Click to collapse
what does "reboat" mean?
nccu_eagles said:
what does "reboat" mean?
Click to expand...
Click to collapse
he means rebooting
People need to stop thinking of Android in terms of their Windows desktop or WinMo. It handles memory completely different. Android sees unused ram as a wasted resource. Android will free up more ram if it needs it. If you look in the notification area you may only see ~100mb free. Then look in the "running applications" tab under settings-applications and you may see well over 200mb available to android. That's because Android has cached about 100mb of data to make it readily available because Android knows there are some programs/processes you use a lot and by caching it in available ram you can access them quicker without slowdown. But this 100mb of pre-cached "stuff" android will kill if it needs additional ram. That's why it shows it as available in Android settings.
Take a look at the Pre-gingerbread running services menu, it actually used to spell out how much was unused and how much was in running services Android knows it can kill to free more memory if needed. A sign of your phone really running low on memory is if your phone has to re-launch Rosie every time you press the home screen. This happened a lot on early builds of Sense 3.0 on the G2 because the G2 just didn't have enough ram to run Sense 3.0. Your phone won't lag/stutter just because it's low on memory. In fact killing a lot of these pre-cached items will be the cause of your phone's apparent lag as your phone attempts to relaunch a process or service that you killed.
{
"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"
}
thanks for reply , but in some videos i noticed that the device is too laggy !!!!
how can u explain this ????
i mean during multitasking like this http://www.youtube.com/watch?v=XKfbXqJbXZQ
xdafun4all said:
thanks for reply , but in some videos i noticed that the device is too laggy !!!!
how can u explain this ????
i mean during multitasking like this http://www.youtube.com/watch?v=XKfbXqJbXZQ
Click to expand...
Click to collapse
Its early software. Wait for an OTA or for it to be rooted and CID unlocked and then you will be able to remove Sense.
If I can say one thing about HTC, they support their phones much longer than ANY other company out there - hell they're one of the first to provide GB on a launch device - and they are also excellent about maintaining their own software (ie, Sense - the bloat hog on any Android or WinMo 6.5 device - as anyone can tell you, Sense 2.0 took at least 75MB of RAM to run - 3.0 has to be worse) so you can rest assured that your device will definitely speed up one way or the other.
but dont u think after all that it is a problem that the desire hd had more free ram than the sensation
i hope it can be solved with an update as i cant immagine it without sense :S
Go to a store and play with the phone....it's that simple. Watching a YouTube video about the phone can be misleading you have no idea what type if settings the guy was using
Sent from my HTC Sensation 4G using XDA App
xdafun4all said:
but dont u think after all that it is a problem that the desire hd had more free ram than the sensation
i hope it can be solved with an update as i cant immagine it without sense :S
Click to expand...
Click to collapse
I have 220MB of RAM free and I'm running Scruff, A4A Radar, and a number of other apps in the background. Looking at my G2x, with the same apps running and NO Sense, I have 148MB free and the Sensation is not lagging like the G2x is.
Hello, I've put this guide together to explain most of the tweaks that i see on each ROM's page, as i needed someone/something to explain those so i think most people would want what the heck all of those tweaks mean,cuz i was all like
{
"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"
}
so they may look at the tweaks list like this.
1 - tweak 1
2 - tweak 2
3 - tweak 3
NOT like this:
1 - herp
2 - derp
3 - i have many tweaks, just flash the goddamn thing already =_=
UGH
This guide will include memes, and funny stuff because i can't go through a convo without using them, and hopefull they'll make this read a little less boring.
So here goes:
Optimized .9.png Images
basically put, a .9.png is an image with guides that tells Android where the image can be stretched and where the content will be placed inside the image. An easy example is a button, some fit only one word and others stretch across the whole screen and Android will put the text in the middle of the button. Optimized 9pngs mean less visual artifacts and more stability, as many people mess up when editing those and this can lead to android armageddon.
http://forum.xda-developers.com/showthread.php?p=21267311#post21267311
And5 2.3.durp - HTC Blabla.hurrdurr.herpderp - Runnymede
Runnymede is the codename for the HTC Sensation XE, basically when you see this it means that the ROM was based on the latest ROM of that phone, as HTC,logically, will deliver the fastest/latest updates to their latest phone, when a ROM is based on the latest, it is less likely to have bugs, and more likely to perform better (you're basically stealing the pamper HTC is giving to it's latest hugearse phone), the downside to this imo is that because the Base ROM wasn't designed for our device (HTC Desire S) then it's less likely to be battery/performance efficient as the ones specifically made for our phone, i could be wrong, It's like Taking windows se7en and dumping it on a vista-ready machine, if the analogy makes sense.
Rooted (Unsecured boot.img)
Rooting is the process by which you regain administrative access to your phone. Even though Android is an open source operating system you still don’t have full “root access” to do what you please. Back when the iPhone launched in 2007 the hardcore techies quickly realized the true potential of the device, and the cruel software limitations that Apple had sealed it with. What became ‘Jailbreaking’ on iPhone was quickly translated to other platforms as well, and when the world saw the first Android back in 2008, the term “Rooting” was born.
From my understanding an unsecured boot.img allows you to do adb remounts,which is necessary for some patches/derps to the phone
BusyBox 1.19.3
Busybox allows you or programs to perform actions on your phone using Linux (copied from Unix) commands. Android is basically a specialized Linux OS with a Java compatible (Dalvik) machine for running programs. The Android kernel is a modified version of the Linux kernel (that is why the Android kernel must always be open source). Busybox gives functionality to your phone that it does not have without it. Many programs, especially root programs such as Titanium Backup, require busybox to perform the functions of the program. Without busybox installed your phone is much more limited in what it can do.
Disable bootsound
See the....erm...Hear the music that plays when you boot up your phone? this tweak disables it, useful when you're turning on your phone in lectures or in exams.
Zipaligned, De-Odexed & Optimized
When devs say they optimized there rom or framework etc... It means they ran a tool such as apk manager (what I use) to compress all the images in an apk to be the smallest size they can get them without losing quality. This will speed up the build for maximum performance and less ram usage.
Other people say there apks are Reengineered. This means that there apks have all unused lanuages removed for even better performance.
Odexing means Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes). Odexed builds such as stock roms cannot be themed for the most part.
Zipalign is an archive alignment tool introduced first time with 1.6 Android SDK (software development kit). It optimizes the way an Android application package (APK) is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and overall the whole system much faster. Execution time is minimized for zipaligned applications, resulting is lesser amount of RAM consumption when running the APK.
/etc/init.d script support
Adds init.d support to the kernel, so you can run custom scripts at bootup, those are used for many stuff, including (but not limited to) auto-zipaligning, Almost ALL of the tweaks included in most Roms run here, they run on boot and do stuff.
add Nano editor
When getting used to the command-line, Linux novices are often put off by other, more advanced text editors such as vim and emacs. While they are excellent programs, they do have a bit of a learning curve. Enter Nano, an easy-to-use text editor that proves itself versatile and simple. Nano is installed by default in Ubuntu and many other Linux distros and works well in conjunction with sudo, which is why we love it so much.
This means that this editor has been recompiled (Ported) to work on android
add Bash (command shell)
basically, it's a shell used in terminal emulator that makes it easier to write scripts and commands and stuff. this would mainly be used by developers.
Extended Quicksettings
This means that the developer modded the systemUI.apk to add Moar options to the page here, Moar toggles, MOAR (because you can never have too much settings, solution? MOAR!)
Rosie/Notification Tweaks
These are tweaks for Rosie A.K.A Sense Launcher and sense's notif......Oh ok screw this
, What the hell is this again?
Beats Audio Mod
"People aren't hearing all the music.
Artists and producers work hard in the studio perfecting their sound. But people can't really hear it with normal headphones. Most headphones can't handle the bass, the detail, the dynamics. Bottom line, the music doesn't move you.
With Beats, people are going to hear what the artists hear, and listen to the music the way they should: the way I do."
Beats audio gives the beat to the music, this is an attempt to port the effect to other devices than the Sensation XE, Will sound best with an official Dr.Dre Beats Audio Headphone, but who can afford those? not me. it gives a nice effect though.
seriously though.
SuperUser
Its the program that requires you to give a program permission to run root functions. the thingy that pops up whenever a program asks for permission and prompts your highness if thou shalt allow thine app to aquire Root permissions.
I.e. keeps programs from messing up your phone without your permission
Ultra Smooth Rosie mod applied!
All sense 3.x ROM's have a smoothness problem during page scroll, its always eratic and never locked in smoothness, this is caused by HTC's 3D widgets taking their toll on the GPU especially when populated with data
However if you press home and scroll back to the default screen you notice all the widgets gets frozen/flattened and scrolls back at liquid locked 60fps smooth, You will also notice that the 3D carousel home screens are seen in the background, this mode is called QuickScroll
What these mods will do is invoke QuickScroll during normal page scroll and eliminate frame rate issues caused by the 3D widgets, its available in two flavors:
Super Smooth Rosie:
This will keep the 3D widgets in the intial screen you begin scrolling from and freeze/flattens all the other pages until you stop scrolling
It will satisfy those who don't want to completely lose the 3D widgets
There might still be a very slight frame rate drop during the initial 3D flip depending on the complexity of the widgets.
This mod hacks the FxWorkspace.smali file
Ultra Smooth Rosie:
This mod goes even further by completely disabling 3D layered widgets by flattening and freezing all homescreens during scroll
The homescreens will still rotate in 3D space, only flattened
Liquid smooth locked 60FPS!
http://forum.xda-developers.com/showthread.php?t=1302914
RCmix Tweaks
This app has tweaks mostly related to the UI on sense, you can switch themes and stuff, far as i know >o>
GPU rendered UI
Much of the discontent around UI responsiveness and animation smoothness in Android versions before ICS has revolved around the fact the OS does a lot of its rendering through software — meaning that the processor, instead of a dedicated GPU, is handling the visuals. That's an inefficient way to do things and takes away CPU cycles that could be used elsewhere, but the point here is that it's not in itself the cause for sluggish performance. If you have a fast enough CPU, you can deal with some software rendering without a hitch.
This fixes the problem by making the gpu go like this:
Which should make stuff quicker, this tweak is arguable though.
more : http://www.extremetech.com/computing/107995-the-truth-about-hardware-acceleration-on-android
Hope this has been helpful, there are tons of mistakes and misconceptions, and lots of stuff to be added, Thanks for reading.
and seriously, just don't x'D i'm only doing this 4 gr8 Justice
Keep the thread clean, if you want to use the thanks button just do it so you won't spam the thread with "thank you" comments, those take up space.
Wow!! That's a long one!
I haven't been able to go through that in entirity but it looks informative. Will come back it and read the entire thing in detail soon.
Thank you for taking the time.
Sent from a Desire S powered by The Reaper.
bookmarked!! useful information for android newcomers like me
ammenRA said:
bookmarked!! useful information for android newcomers like me
Click to expand...
Click to collapse
If you're a newcomer to android i'd suggest you read This guide, it's the best really
Welcome to android
if there are any other terms that you see vague, just write them here and i'll try to explain them XD
already download it my bro beat you to it..