Related
Hi,i would like to install Rosie onto my G1, I believe its called rooting?
Ive read that Rosie is unstable and allot of things don't work on it, And then ive read other places it all works now. Is there any good full functional releases? I would love to have a flash player on this phone. Also where can i find good tutorials on how to install a different ROM such as Rosie?
Ive never done nothing like this , but i'm sure with a good tutorial i can do it.
Robert916 said:
Hi,i would like to install Rosie onto my G1, I believe its called rooting?
Ive read that Rosie is unstable and allot of things don't work on it, And then ive read other places it all works now. Is there any good full functional releases? I would love to have a flash player on this phone. Also where can i find good tutorials on how to install a different ROM such as Rosie?
Ive never done nothing like this , but i'm sure with a good tutorial i can do it.
Click to expand...
Click to collapse
You need to follow the guides on here to root your phone, then you need to update to a special radio and the newest spl. These guides are readily available on here if you look: I found them, i'm sure you can too.
Rosie is a part of the ROM for the HTC Hero, HTC's latest phone with Android underpinning it. It is essentially an alternative 'home' for Android based on their Touchflo interface which they've been using in a lot of their Windows Mobile devices.
The Rosie UI has a lot of cool widgets, along with a nice multitouch browser with flash support - HOWEVER it is only Flash 9, and I found a lot of sites just don't work. there is also multitouch in the gallery in some of the releases I've tried, along with some much improved apps, such as the music player.
There are some MAJOR drawbacks at the moment though:
1: slowness - the ROM is not designed for the G1, and it is recommended that one uses App 2 SD to move applications to the SD to free up memory. This does help a bit, but lag is still an issue, particularly if you want to use lots of widgets. I personally don't like using Apps to SD, so I'm waiting for a slimmed-down ROM
2: SMS - a LOT of people (myself included) are suffering lost SMS messages in these ROMS. I have been forced to move back to The Dude's Cupcake ROM until a proper fix is found, since I'm a big texter and dont like the idea of losing messages and not knowing about it.
3: Bluetooth. As far as I'm aware there is no Hero ROM available yet with working bluetooth. This may or may not be important to you. I quite like having it to hand but I can live without it.
4: LED notifications. The LEDs with these ROMS are completely non-functioning. There was a semi-fix in one of the ROMS but this was removed and at the moment there is still no sign of a ROM with fully-functioning LEDs - annoying if you like to be able to glance at your phone and see if you have a message without turning the screen on.
These are the only MAJOR issues I've come across in my use of these ROMs, any other problems were fixable, or corrected with updates
Thank you for your reply, Maybe i will wait.
Are there any other roms you might recommend ?
I'm sure I'm setting myself up here, but what advantages are there to the custom ROMs at this point?
I'm running stock Froyo 2.2 (I did update the radio to 5.08, though), stock bootloader, and I'm not rooted. I'm on T-Mobile in the Tampa, FL area.
I'm not sure if it's a coincidence, or just because most people that are posting on XDA are running custom ROMs, but I don't really have ANY of the problems most people on here have. My battery life is great, and the phone is overall VERY stable. I've tried other launchers, themes, etc., but I always prefer the stability of the stock setup over aesthetics.
The few issues I have had I can attribute to poorly written apps (force closes, battery vampires), or known hardware problems (mediocre 3G connectivity at times, etc).
I can understand if you have a phone like the MyTouch that never got any official updates after 1.6, or you want to try the next leaked software on your phone. But the Nexus One has had tons of official support and updates up to this point. Before Froyo was officially released, I found myself better off with stock recovery to load the latest, greatest Froyo build.
Sorry for the rambling, but I would greatly appreciate any education I can get on what's packed into these custom ROMs that everyone gets so excited about.
THANKS!
Don't really feel like typing all the reasons haha, but there's a lot of stuff to enjoy with custom roms. If stock works for you that's great. I don't know anyone that's ever gone custom and wanted to go back but I'm sure it happens. End of the day it's whatever makes you happy. A lot of us want more than just a great experience, we want to see what's possible. You can view the changelog for the latest Cyanogenmod(most popular custom ROM) build here http://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
1. More control over the appearance of the OS. Get rid of that ugly white notification bar and replace it with a sexy black one, for example.
2. Removing the stock apps from the phone that you don't use or want. Why have them sitting there taking up space and potentially resources for no reason? Sure they don't take up much in terms of storage space, but if you use a lot of apps, every little bit counts.
3. Undervolting and over/underclocking. Get that extra little performance boost, or cut it back. When I was UV'd to 800mV and UC'd to 806mhz, I noticed no performance difference or problems (note: I don't play 3d games on my phone) and my battery life was insane. 24 hours of normal use would put me to 65% give or take.
4. Relating to number one, more control over other things. I've ripped stock, but customized, apps from random ROMs and pushed them to my phone. Black Facebook & Twitter widgets (white ones are ugly), darkened (black & dark grey) stock messaging interface with white text, etc.
5. Trackball Alert Pro.
I'm sure that others can add more, but the above are the main reasons I rooted mine.
A tiny little thing called Apps2SD+, for example.
Multiple audio/video decoder support.
Lots of Linux binaries bundled.
Lots of modifications to stock software (contacts, browser) that increase their usefulness (for example, do you really like to type "about:debug" each time you want to change browser client after reboot?).
etc etc.
Thanks for all the great info.
The underclocking sounds interesting. I don't play any games on my phone, and extra battery life is always nice.
I'm not too interested in customizing the appearance too much. Coming from an iPhone, I'm pretty happy with the looks of the stock Froyo UI compared to that.
Again, thanks for the time you guys took to give me some information. I greatly appreciate it!
Sent from my Nexus One using XDA App
Ryjabo said:
1. More control over the appearance of the OS. Get rid of that ugly white notification bar and replace it with a sexy black one, for example.
...
5. Trackball Alert Pro.
Click to expand...
Click to collapse
This was reason #1 and 2, 3, 4, 5, 6, 7 for me, respectively
Track ball skip song.. Enough said.
If I install a custom ROM, when a new one comes out, do I have to install the ROM from the start and I loose my setings etc. or do I just update it?
Depends on the ROM maker. Most make their ROMs backwards-compatible, so you can upgrade. Going between different makers' ROMs you mostly need to wipe and start fresh (though there are apps that can back up and restore pretty much everything).
I am thinking to try Cyanogenmod ROM, bot I don't wan't to cofigurate all the things when a new ROM comes out.
Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.
Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any TOPAa-specific tweaks that others should be made aware of!
Update to this - I changed around how topic 4 is done. Feel free to re-read that section.
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
metho88 said:
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
Click to expand...
Click to collapse
For the pm disable stuff? If you find an app that does it, more power to you. I want to control Android directly, hence the reason I went with a script that utilizes that concept. The pm disable stuff is obnoxious I know - so if you do find an app that'll do it for you, have at it. I didn't want to add any more apps into the mix if it wasn't necessary .
Rhod400 in startup.txt
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
1edge1 said:
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
Click to expand...
Click to collapse
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
arrrghhh said:
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
Click to expand...
Click to collapse
yeah i do use the startup for topaz. Was just wondering. haha. thanx for clearing it up
So, i've tried many different roms out there on my SGS. Never got any major issue with flashing or setting them up. Supposedly a custom rom has something improved but there was one think i kept thinking they all fail and i was wondering if anyone else feels the same.
I see random posts all the time telling how great multitasking in android is. But all these roms i keep using try their very best to close just about everything i have running. As far as i can tell, a few seconds after i switch to anything else, my first app gets closed. For example, everytime i'd leave browsing to manage what im listening to or sort out files on some file manager i'd find i needed to open my browser again instead of being there opened and waiting for me to return.
After searching for a while, the best explanation i could find out is to prevent battery drain from opened apps and to keep things smooth by having free ram, which kind of makes sense. Goes against what i read in a paper from google about android multitasking but fair enough.
Except the other day i happened to returned to a froyo stock rom (JS8 with darkcore 1.4) on my SGS and found out this does not happen. Apps stay open for the most part, except when i run something really heavy (like a game). And i dont really notice any performance decrease or extra battery drain from my usual usage.
Granted, i could be just told something along the lines "well dude, just use whatever works for you" and i totally plan on doing so, hence me experimenting, but thats not really my point. What i'm going for is, are custom roms being overzealous? because this really spoils any attempt at multitasking...
Again, this is not a rant of any sort, i was just wondering what are other people's thoughts about it
I'm suffering same problem
i want to have the browser and messenger at the same time
it close one after swetching to the other
i have 80mb free ram
I had the same problems, although lack of multitasking appeared on my stock rom, not a custom... sgs couldn't handle faceboom messager, viber, and a browser at the same time, everytime I switch from my browser to something else - it gets killed, which is frustrating
at the same time I saw how nexus s work, and how much free memory it has, compared to mine, the difference was huge!
I tried cyanogen at first, which was very close to stock nexus s, but it doesn't work good with sgs's camera and crashes once in a while
so eventually I installed JVT with voodoo and uninstalled different samsung stock apps, which gave me about 50mb of additional RAM compared to stock, and there doesn't seem to be any aggressive memory cleaners working, so I can now finally switch between all the apps I need
If you want the best roms for multitasking, go for the final builds of Froyo 2.2.1. They have plenty of free ram and are very smooth. I'd recommend Froyo ZSJPK. You can download it from XDA.
I think it depends on the ram settings in your ROM. The way android works is there are a bunch of system settings on how much ram to keep clear, and if it drops beneath certain values they start killing apps.
It's highly possible these values were tweaked in the custom roms, to improve the perceived smoothness and so on, but at the same time reducing multitasking. There's a trade off between performance and multitasking (guess why apple was so reluctant to add multitasking?)
I'm not really an expert on it, but I'm sure some quick searches around will find out where those values are and how to change them.. some rom/app probably even allows you to tweak them to your liking.
All Gingerbread roms do the same, closing apps after moving away from this, don't know why, but froyo didn't do this and ginger does.
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
MaoJie said:
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
Click to expand...
Click to collapse
ok i downloaded galaxy tuner but idk how to change threshold
Hello all very long time lurker but am here now for some help. So a few questions and description of what i wish to achieve.
I have a POS iPod touch 4th gen that I have had 2 and half years or something and really want to replace. Also have an Xperia X10 and shortly will have an LG Optimus 2X. The X10 will function for phone duties until the Xperia TX become available in Australia.
Back the the O2X though. Now turning an android phone into a Portable Media Player (PMP) is something I have been wanting to do for a while now. Naturally though this brings up a few things that will not be needed.
For the music front end I will be using Player Pro and Pics and videos will primarily be held and viewed in QuickPic.
The phone will still need to retain wifi and bluetooth capabilities, however I want to fully disable all other forms of connectivity as I will have no need of it and will not be using a sim in the phone as this will be dedicated to music, movies and pics. So does anyone know the best way gor me to go about that?
I will also have a hell of a lot of unused and unwanted apps. I would love to be able to really strip the phone back and free up as much space as possible. Now in the past I have been able to uninstall pre-installed apps from my X10. I am just unsure how to go about it on the O2X. Does anyone know how I would go about completely removing the phone, contacts, calander, stock music, stock gallery and other assorted apps?
I would also need to be using a kernel with the voodoo sound mods for the wolfson DAC. Now I was wondering if there was any recommendations there?
Finally I would also like a recommendation of the most stable ICS based ROM to go with the voodoo kernel. I would like the ROM to also include a modifiable set of notification bar widgets so I can easily turn on and of things like wifi, bluetooth, gps, airaplane mode and adjust brightness. Anyone know of anything that would fit the bill?
Must also come with a working camera app (does not need to has video recording working or panorama just basic camera duties please). Any other suggestions that you may think of feel free to post them.
Thanks for taking the time to read this and hope some of you can help me out here on my project to make an Android PMP out of a great little Android Phone.
Stoner
Note to mods: hope I am posting in the right section, feel free to move it if I am not.
Since connectivity is already built in into the android OS, you can't disable it, but I think keeping your phone in airplane mode all the time should do the trick. Anyway, taking out the sim card already disables all connectivity that involves telecommunications.
If you want to remove system apps, you have to root your phone first. The forum already has so many guides on rooting. Then all you have to do is use any root file manager, go into system/app and delete the apps there. Not everything can be deleted though, some are crucial for the functioning of the phone.
The other way is to download a rom, open the zip and delete everything you don't need that's under system/app and install it. No guarantees that your phone will boot up though, if you happen to hit an app that is crucial for the rom to work. Then you can flash the rom and it's done.
There are many kernels that use voodoo, just find one that fits any rom of your choice.
Finally: ICS roms still have some bugs, seeing that you are going to use it as a PMP, I recommend not upgrading to ICS or later until roms made from LG's sources start popping out. I hear that CM10 (that runs on jellybean) will be released shortly after LG releases their ICS update.
Almost all roms have a camera app, no worries there!
TL;DR Install any rom you'd like that seems to fit the bill. Root your phone, open the particular rom's zip file and remove apps you don't need that are in system/app, flash it to your phone (with recovery mode of course). Flash kernel to your liking.
Looks like LG is no better than Sony when it comes to OS Updates haha
shall look at stock based Rome for now then. Try and find a JB skinned one if possible.
Then play trial and error with what apps I can remove before flashing and which I have to leave and possibly just freeze. New it was something simple but its been a while. I hope I can remove all the basic apps that make it function like a phone otherwise I guess I will make do with freezing and hiding them. Love removing all clutter possible.
Will be waiting to see if CM10 can come along much less buggy than all the CM9 and ICS ROMs that I have looked at. Silly LG hampering the development of ROMs because there isn't an official ICS update to work off and its late 2012 already. Hoping for some good news though with what I have read about SK and them getting ICS.