Related
By custom ROM I mean like Cognition or CyanogenMod.
Are there any advantages to these over the stock ROM on my Rooted Device?
Such as more features or whatever else?
Am I just better off waiting for FroYo to be released?
I kinda miss flashing ROMs from the good ol'days of WinMo =]
Sometimes, it's the little things that make a world of difference. Cognition, for example, makes my battery indicator give me a number, the percentage of power left. Much better than having to make a fuzzy guess based on a tiny blue/yellow/red battery graphic. It also comes packaged with a nice lagfix as well as app sideloading - things I can and did do for myself, but are nice to not have to redo with a new ROM.
And in general, my phone is just smoother with the new kernel and everything else. So I don't regret flashing a custom ROM at all; it was worth it.
Do I need a Lag-fix?
This is my first android device so I have no idea what slow is haha.
I think I already enabled sideloading, I did something with a command prompt window and my computer, thats kinda sad that I don't remember what lol.
If you edited a database file in something like SQLite Manager, you enabled sideloading.
And I totally recommend a lagfix. There are several wonderfully technical reasons as to why one's good to have, but practically speaking, I like it because the phone is noticeably more responsive. Although, watch which one you get... I had one that utilized a program called SL4A, and removing that lagfix broke my phone for the day. -_- I had to do an Odin3 flash to make it usable again.
I have noticed that lag when I try to resume the phone from stand-by. The lag-fix doesn't have any negative side affects to the phone like over-clocking does?
First, I apologize if this is an issue that has already been discussed; however, I did look through the stickied threads and didn't find anything that really answered the question I have.
I have tried several different Froyo 2.2 ROMs on my Dream, and they always seem to run a fraction of the speed of Donut ROMs. Loading the home screen, applications, and webpages always seems to take a lot longer, and there just isn't that quickness that Donut has.
Am I doing something wrong? Anyone else have the same experiences?
I actually have to stick with this fact. Also i did notice that the rom i tried "passing through" the process of moving on from Android 1.6 to Android 2.2.1 (was JF if i recall) was kinda faster then the Biff mod i have on my G1 now.
But i don't think that it is anything wrong about it, i think that frankly the g1 start to be an obsolete piece of hardware.
Maybe i am wrong but just so that you know i tried to download "Angry Birds Lite" and start it...well it's kinda a shame as it stutters terribly. Is it a matter of ROM MOD or just that the G1 isn't a young quicky fella anymore ?
The hardware is outdated .
It's just interesting then how so many people appear to be running these Froyo 2.2 builds. Do they not realize how sluggish they have made their phones?
Why shouldn't we M!x. Me, on my hand, i have a G1 blocked by my phoning company and sold me an 1.1 Android HTC Dream...so awful...i couldn't even use my camera as a video recorder (and they didn't release not 1, not only 1 update!)
And as long as i am flashing and modifying everything i don't find why shouldn't i update my phone to the latest version of this wonderful OS.
N4R4Y4N said:
Why shouldn't we M!x. Me, on my hand, i have a G1 blocked by my phoning company and sold me an 1.1 Android HTC Dream...so awful...i couldn't even use my camera as a video recorder (and they didn't release not 1, not only 1 update!)
And as long as i am flashing and modifying everything i don't find why shouldn't i update my phone to the latest version of this wonderful OS.
Click to expand...
Click to collapse
Why shouldn't you? Because it's slow? Have you tested Android 1.6 vs Android 2.2? You don't notice the significant slowdown? Taking 5 seconds to bring up the dialpad?
ok wait wait wait...
Oh well...i dont know if u intend that literally takes 5 seconds...but with the Biff mod it's not THAT slow...
i only joined up in the topic cos i found the phone slow in some occasions but not that it jeopardize the overall use.
-
i guess your the two among the fews who didnt get their phones up and running froyo fluently.
checkout the OTA and after that the more bareboners/tweaked roms, read through the corresponding forums, and try to admit that you have to abandon having fancy stuff on yer phone.
as for me im right now running the OTA the one available here:
http://forum.xda-developers.com/showthread.php?t=811620
with cpu set 122-614mhz, using modified radio hack to gain +14mb of ram and modified lowmemorykiller values.
ive been running the system since weeks with no hangups,and is snappy az should be.
done these not with with third party apps but adding an initscript that sets these values at boot time WITHOUT needing running yetanother app running.
i dont even have to use compcache.
must mention that i use ADW home manager with only 2 desktops, no dockbar and so, minimized fancy in order to keep its memory consumption low, using only the calendar widget and Quick Settings in notification bar.
i have even found out recently that switching on the animations lets you feel your phone more snappy since it takes your attention while loading or switching between views/screensD
[it does work indeed!]
so snappy and stable that i am afraid of trying new so said tweaked roms like:
http://forum.xda-developers.com/showthread.php?t=825716&page=48
or
http://forum.xda-developers.com/showthread.php?t=929678
i guess more and more G1 users/developers are trying to strip down and tweak froyo to get the max out it since this may be the last stable rom available for our devices.
and no, i dont think that our devices are outdated, definitely not for normal day use.
so keep up finding the best way for yours!
cheers
:GY
M!x said:
First, I apologize if this is an issue that has already been discussed; however, I did look through the stickied threads and didn't find anything that really answered the question I have.
I have tried several different Froyo 2.2 ROMs on my Dream, and they always seem to run a fraction of the speed of Donut ROMs. Loading the home screen, applications, and webpages always seems to take a lot longer, and there just isn't that quickness that Donut has.
Am I doing something wrong? Anyone else have the same experiences?
Click to expand...
Click to collapse
You make these claims without telling what roms you've tried.
Have you tried this one: http://forum.xda-developers.com/showthread.php?t=811620 ??? Because this one *IS FAST*. At least it is when combined with the 2708 memory hack.
I'll surely give it a shot, thank you guys
Thanks for the information guys, I will certainly try these ROMs. I have, by the way, tried standard builds of Froyo, CM6, SuperF, with disappointing results. They worked "OK," but had a fraction of the performance of Donut.
You guys can try my Froyo rom. Only complaints I get is about the Bloatware,lol. No drag, almost like a donut rom in speed. I have over 3000 downloads. The link is on my signature or on the G1 development section. Let me know what you think!
Hi guys, as you can see from my sig I owned a few HTC in these years and I moved on from WM to Android about 2 years ago.
I'm writing this post as a request of suggestion from you as I don't have any experience with how Android behave on Tytn II and it's not for me but for my dad..!
He's been using his Tytn II for quite some time so far and I wanted to know if you would suggest me to flash for him Android on his device.
Please before answering considere that it's not for me, it's for a man of a certain age (around 60) that doesn't want any complication and doesn't have any time to dedicate to solve any issue that my come from the process.
So if this would bring him an increase of its device performance and usability I would definetely go for it, but don't want to hear him complaining all the time bout me having ruined his phone because of FC or random reboots or whatever ...
Is there any ROM free of issues and stable enough?!
I enjoy changing kernels, roms and radios of my devices, but you got what I meant before right? Once again: it's not for me..!
Thanks everybody in advance for your suggestions
First of all, before recommending anything.
I understand that your dad is as you say "a man of a certain age (around 60)". Is he savy on learning how to use new things? Meaning navigate his way around using things. IE: with his WM.
As far as if problems will arise, these things will happens (IE: FC, etc...) Depending on how he use it too. But it can be control to the minimum.
From my experience all ROMs are pretty much the same as far a being stable. It will depends on features and a few other things.
BeenAndroidized said:
I understand that your dad is as you say "a man of a certain age (around 60)". Is he savy on learning how to use new things? Meaning navigate his way around using things. IE: with his WM.
Click to expand...
Click to collapse
Well..he use his Tytn II as he would have used any "old style phone". No app or whatsoever installed a part from a navigator (which I installed..) ....and once that something was not working properly he didn't anything for about 6 months till I discovered it, PIM backupped everything and made a hard reset to get it back to its functionality...so I'd say: yeah if he need to he will learn, but he won't search by himself any workaround..
And the main problem is that we don't live anymore together, I'm currently at them just till Feb and then I'll b back to Athens where I live...so I won't be here to help him out..!
That said, he's quite tech friendly, he's on his PC all day long and part of his job is to build different sites for various committents...
But from your words I can understand it need far more attentions than I think my dad would like to give to this thing..
Best way is to ask him.
my 2 cents
Well, as far as I can see,
my TyTn II with android is faster, more reliable and overall most usable.
The touch screen feels more like a capacitive touchscreen rather than a resistive one (wich is actually what the TyTN has).
Regarding the "age" of your father, I think it's not a problem.
mine has the same age of yours and he's arguing with Samsung Bada Os every day...so I showed him how "easy" is Android regarding Bada and he was amazed.
the counterpart is that, if he want to move to Android, you have to set up the whole thing in every little piece:
Android version, htc overclock, hiding "dangerous" icons from the drawer (such as the root app ) so he can't cause any "damage" by hitting something wrong.
I'm currently running under Froyo on mine, and it's pretty faster as I said BUT...
sometimes it FC (well, I'm like an addicted to customisations, so it's pretty normal... xD), it freezes for a while, Launcher Pro will FC (I personally hate ADW), my battery drains fast (but again, is because I put all kind of custom on it...IE: live wallpapers, custom lockscreen etc etc)
IMO if you go to a pretty simple version (such as 1.6 or alike) it won't have any kind of problems...
I give you a tip:
google for simosoft project...
he developped an Android "emulator"... install it on his device and see his reactions... from there you can do everything: phone calls, text messaging, emailing (because it basically uses the WinMo programs ) and it's not a flashing rom, it's just a installable .cab file.
try and see
I think this is the best thing you can do to avoid any kind of "stress"...
otherwise, for instance, you can make a huge backup, flash a rom, make him try
and then, if in few days/weeks he can't go on with Android (wich IMO is impossible) you can revert it back to the useless WinMo
let me know :-D
Thanks for all the advices..I'll think about it & I'll let you know
Sent from my brain with Beats Audio using my psychic powers
I'd suggest leaving him with a good stable WM ROM. There are still newer ones but I my favorite was an old one by shifu. You might look for a WM rom that has not a lot of extras, good stability, and updated versions of any "aftermarket" apps.
Or, give him a haret install. If he likes it but complains that it is too slow, you can get more speed by installing nand. But don't do that until you know he likes it.
I have my G9 for about 2 years now, and it's the first generation 512mb G9 1.0ghz.
All these years I updated every firmware that Archos released, so also used to the bugs and problems that sometimes occured.
Using 4.0.28 a long time now, but I think it's not repsonsive and has a lot of lag. Sometimes waiting quite a while to start an app for example.
I know that's also caused by the 1.0ghz and 512mb, but I want to try a custom rom IF that's faster.
I know all the custom firmwares are based on the official firmware, I read almost all the topic about them, but I'm not sure which firmware to choose. Hope someone can give me some clues if installing another firmware could make my G9 faster. And if so, which of the firmwares should do the trick? Somewhere I read the 4.0.7 should cause less lagging on the older generation tablets.
hars73 said:
I have my G9 for about 2 years now, and it's the first generation 512mb G9 1.0ghz.
All these years I updated every firmware that Archos released, so also used to the bugs and problems that sometimes occured.
Using 4.0.28 a long time now, but I think it's not repsonsive and has a lot of lag. Sometimes waiting quite a while to start an app for example.
I know that's also caused by the 1.0ghz and 512mb, but I want to try a custom rom IF that's faster.
I know all the custom firmwares are based on the official firmware, I read almost all the topic about them, but I'm not sure which firmware to choose. Hope someone can give me some clues if installing another firmware could make my G9 faster. And if so, which of the firmwares should do the trick? Somewhere I read the 4.0.7 should cause less lagging on the older generation tablets.
Click to expand...
Click to collapse
I'd be interested in that answer also, I'm on Surdu's custom ROM which was great at first, but now it's lagging like crazy. I can't see anything running in the background that would cause it.
hars73 said:
Using 4.0.28 a long time now, but I think it's not repsonsive and has a lot of lag. Sometimes waiting quite a while to start an app for example.
I know that's also caused by the 1.0ghz and 512mb, but I want to try a custom rom IF that's faster.
Click to expand...
Click to collapse
Although there are a few 'custom' ROMS that have some features like overclocking... overall, the VERY SMALL increase in performance of them simply is not worth it (at least not to me).
The slow down is also not really due to having only a 1GHz CPU and/or only 512MB of RAM either. It's a combination of 2 things...
#1) The totally STUPID way Archos changed their Media Center apps (Video and Music) so that the device constantly starts 'indexing' files (even when it should not do so). Heck, it even tries to 'index' pictures, music, or video files of certain game apps when you try to install them. When your device is 'lagging' take a look down in the lower right notifications to see if there is circular arrows indicating it is 'indexing'. If it is, that will slow the device down to a snails speed until it gets done.
#2) Many of the new Google updates (Google's own app updates) are now becoming far to over bloated with foolish (and, as far as I'm concerned totally unnecessary fluff).
The best solution to #1 (on my end anyway) was to simply go back to 4.0.7, but there is some extra clean up work needed to get that all straightened out. Even then you can still end up with the #2 problems (simply because Google wants everyone to buy new devices so that they and everyone else can make more money).
Sorry, I'm just way too tired and about to fall asleep here to explain all the details about how to get back to 4.0.7 and clean things up right now. All I can say for now is that I am far more happy with 4.0.7 than ANY other firmware on my end. YMMV.
55mls said:
Although there are a few 'custom' ROMS that have some features like overclocking... overall, the VERY SMALL increase in performance of them simply is not worth it (at least not to me).
The slow down is also not really due to having only a 1GHz CPU and/or only 512MB of RAM either. It's a combination of 2 things...
#1) The totally STUPID way Archos changed their Media Center apps (Video and Music) so that the device constantly starts 'indexing' files (even when it should not do so). Heck, it even tries to 'index' pictures, music, or video files of certain game apps when you try to install them. When your device is 'lagging' take a look down in the lower right notifications to see if there is circular arrows indicating it is 'indexing'. If it is, that will slow the device down to a snails speed until it gets done.
#2) Many of the new Google updates (Google's own app updates) are now becoming far to over bloated with foolish (and, as far as I'm concerned totally unnecessary fluff).
The best solution to #1 (on my end anyway) was to simply go back to 4.0.7, but there is some extra clean up work needed to get that all straightened out. Even then you can still end up with the #2 problems (simply because Google wants everyone to buy new devices so that they and everyone else can make more money).
Sorry, I'm just way too tired and about to fall asleep here to explain all the details about how to get back to 4.0.7 and clean things up right now. All I can say for now is that I am far more happy with 4.0.7 than ANY other firmware on my end. YMMV.
Click to expand...
Click to collapse
In know about the stupid indexing service. I can see it running after rebooting my tablet, but almost never when using it.
Maybe I'm going to install the official SDE from Archos (that can also be installed on 4.0.28 since a few months) and after that install a rooted 4.0.7 and then disable all the services I don't need. That might help a bit.
I suggest 4.0.28 or 4.0.7. 55mls hates firmware after 4.0.7 but .28 has been good for me. I don't store any media files so indexing doesn't affect me. Prior firmware have bugs with some games for example too.
Also on my 80 G9, I think 4.0.7 has some wifi strangeness. Disconnects occasionally.
Alternatively you can roll back to 3.2.80. This one works quite well overall functionally. However it's certainly not the fastest. The GUI seems slower to me than with the 4.x OS. Honeycomb also has some caveats like occasional lack of app support and the fact that it's sort of a Android 4 prototype in general. On the other other hand, Honeycomb is an interesting bit of history and I like its UI theme.
having the same tablet here (also with ""only"" 512mb ram).
i'm running 4.0.7. now, which works a lot better than 4.0.28 for me, but still has some lags from time to time..
I guess I should have also mentioned a 3rd reason in my previous post that some people may not be aware of...
When installing apps, some do require extra 'temporary file' and/or 'cache file' storage space. By default, Android normally will pop up a "memory low" notification when the amount of memory drops below 500MB. Of course, that means the systems has already gotten so low on memory that it can no longer operate correctly.
On my end (and my devices) I've found that things start to slow down already even when the 'free space' gets down to 1GB. In general, if you can keep the 'free space' up to at least 1GB (preferably 1.5 or more) then there is very little of any slow down.
Of course, now days, almost all the newer devices come with at least 16GB of flash memory and 2GB of RAM (not to mention quad core processors) simply to be able to handle all of the extra fluff Google keeps adding into things with their own upgrades.
Since Google is making the exact same mistakes Microsoft did years ago (taking a good OS and cluttering it up with so much extra fluff that nobody wanted/needed)... well, I've pretty much lost all interest in Android now. I bought my Archos G9 tablets for only one reason and that is to do what Archos claimed they did at the time. I did not expect, nor did I ever want them to end up having to go thru multiple upgrades (from either Archos or Google) to do anything more or less than that. Unfortunately, every upgrade now seems to actually lower (or even restrict) being able to use my Archos devices BELOW what I originally could use them for.
55mls said:
On my end (and my devices) I've found that things start to slow down already even when the 'free space' gets down to 1GB. In general, if you can keep the 'free space' up to at least 1GB (preferably 1.5 or more) then there is very little of any slow down.
Click to expand...
Click to collapse
This seems to be something all devices have a problem with. It's probably a flash RAM issue. When the flash gets near full, it needs to do more erases+writes to store new data and this just kills write performance.
swaaye said:
This seems to be something all devices have a problem with. It's probably a flash RAM issue. When the flash gets near full, it needs to do more erases+writes to store new data and this just kills write performance.
Click to expand...
Click to collapse
My son installed a lot of games on my Archos in the past and there was not a lot of free memory left. This week he bought a Asus MemoPad HD7, so I uninstalled all the games on my Archos.
And it seems my Archos is a lot more responsive now and has less lags. :good:
Still on the official 4.0.28, but this is good enough for now.
hars73 said:
My son installed a lot of games on my Archos in the past and there was not a lot of free memory left. This week he bought a Asus MemoPad HD7, so I uninstalled all the games on my Archos.
And it seems my Archos is a lot more responsive now and has less lags. :good:
Still on the official 4.0.28, but this is good enough for now.
Click to expand...
Click to collapse
Another thing you can do, especially if you have a 512MB device, is to keep watch for apps that run extra background processes. For example, do a reboot and load the system monitor app and see what is loading automatically on boot up. The 512MB devices really don't have enough RAM to go around beyond the basics.
Hi guys!
So I'm probably not as good with phones as you, but I learned to install a ROM, I've tried many of them but then returned to CyanogenMod ROM that was offered on their site. The performance is not that good, it lags often and battery life is too bad! The questions I want to ask you are:
1. Which ROM do you think is the most stable and would be a better alternative to Jelly Bean CyanogenMod?
2. What ROM are you using and why? Experiences etc.
Thank you!
Kind of in the same boat, just three meters further out. Have been putting off buying a new pho.... embiggened touch-pad device with phone capability and less battery life, that should in a reasonable world come with a carrying case with a shoulder-strap, and a stock portfolio for the handset maker... for a few years. But finally caved in, and bought something on sale with a really good screen, a replaceable battery, and a 3,5mm jack not made exclusively out of conductive rubber.
But. Now that I had a new phone pad, I wouldn't have to worry about bricking my old phone. All that much. So I went through a bunch of excruciating testing and failing yesterday to get something without ram-crippling bloatware and google applications that essentially force the 4x to run constantly at max speed.
What I seemed to be running into was two types of problems: a lot of the roms (custom firmware) were made by someone who was simply testing something new at the time, experimented a lot, and then left the project behind (or simply focused on other handsets). That's not necessarily a problem, but it can mean that you have stability issues you might not expect, and that has not been tested or reported while the project was active. And that might actually stop you from getting far enough to install some app that changes cpu-governor, ram-handling, and so on (even things like the standard keyboard/language variant.. kind of essential that that works). Install instructions also tend to link to outdated bootloaders, or have workaround suggestions that worked at the time, but now are obsoleted completely. The second problem was the OpenGapps - some of the core apps conflict with the builds' own apps.
And then there's the fact that the kernel in these roms tend to be from when the project was last maintained. I can't seem to decipher exactly what's going on, but I think a lot of the early roms were based on an old kernel with inserts (like the original one from LG). While the older builds on new kernel branches tend to have better support, but then have certain types of functionality simply gone completely. I don't know why that is, but the experience with this on linux laptops and android devices is what made me hold off until I had something that could replace the 4x before starting to try out some of the experiment builds people have.
So I went through getting the bootloader unlocked, trying a billion different methods before realizing they were all workarounds for the non-eu handsets - just use the oem-unlock method with fastboot. It's really as simple as it sounds. Use the "all in one" thing on the forum, set up the drivers, get root, and things like that - and then install a new, updated bootloader. I think after one of the official LG updates, everyone can actually use the oem-unlock.
Then I chose the wrong bootloader, apparently.. the cwm touch thing - superb bootloader. But apparently has some quirks that prevents it from installing certain firmware packages. I think it has something to do with consistency checking. I liked the idea of a multiboot, and didn't see why that wouldn't be extremely easy on android (with a storage size vs. cfw package being basically infinite to naught). But apparently what you want(need) is the twrp bootloader, and it has to be the last version. I don't know why that is, but you really don't want to be stuck - after basically wrecking your only boot - with an uninstallable image on your sdcard. So if you try something else than the "best one", just be prepared for an exit strategy with a backup and things like that before trying to install new images. There's also no way on these bootloaders to simply run a test first, nor is there a very easy way to partition the on-phone storage without having to start configuring install packages, so this is kind of awful if you're not actually deep into the development toolchains already.
I'd really love it if some of the tutorials said things like: our build really doesn't need a thorough wipe, and you can happily choose the file system you'd like, and the one that actually makes sense. For example. Or "for this cfw, you can just install gapps later on, that's going to work perfectly - don't force the install before you get through our own intro stage", etc. Alas.
Then I went through slimkat, an aosp lineage based rom, an old 4.1 rom, a new 5.1 rom, which all had different game-breaking problems. One refused to install gapps (note: you'll need the gapps that fit with the android version - but some packages simply won't install, period), another build had no sound other than on the speaker. One hanged randomly, another didn't scale the processor cores.
The good news is that this isn't really a problem - once you're set up you can just keep wiping and installing new ones. But it might be a really good idea to make a backup of your initial rom/custom firmware, just in case (i.e., you root, install the bootloader, and once you're in the bootloader, you make a backup of your current "rom" that is installed now. Then you can just revert to that without any problems later. I obviously didn't do that, because I was just fumbling around).
Some of the issues I ran into also might have workarounds, but I don't know - how would I, there's no way to actually tell what the problem is, or what it's related to. The most useful ones in the end seemed to be Vanir 6.0-based, and the one I ended up with, something called Euphoria on lollipop/5.1. That one seems to have all the hardware functions and benefitting a lot from a later kernel. I haven't done incredible amounts of testing on it yet, but it seems to work a lot better than the original firmware ever did.
And when you choose a gapps package, just go with the pico version. You can install everything you need after that from the store (and it takes less time than pre-installing the infinite amounts of crap in the stock package).
In sum - while you can get pretty far with the 4x on just rooting it and uninstalling some of the infinitely memory-hogging google crap, along with installing a new governor for the cpu and things like that. You can actually get something extremely neat by installing a new "rom"/cfw, that doesn't necessarily have the "oh, but you just have to forgo feature X, Y and Z because open source" problems.
I'm sure a cfw-developer is going to see this one day and roll their eyes back in their heads. And will have some very sharp words about the kind of effort that went into making a specific kernel, insert and build combination to even boot. But the later kernels seem to work really well.
And thanks to that Euphoria thing, I'm probably not going to use my new padphone-thing as much as I would. Because that one is over the "just testing stuff, getting it to work" stage. There's things with the home-button bar lighting up when there's notifications, things like that, that kind of show someone who used the handset was maintaining the build.
Anyway - I really recommend that you try out some different types to find these really good roms that works well. I'm sure there are lots of unknown cfw packages out there that work.. you know, for the 300 people who use it every day. That might be some of the early cfw variants with old kernels. And it might clearly also be some of the new ones, which I really didn't expect. Honestly, was kind of expecting stripes across the screen and hangs, but that didn't happen.
Optionally, a dev who actually knows what they're talking about could maybe suggest a list of cfw that have the later kernels that work, or the same kernels that Euphoria has Really, trying to search the net now, and find possible candidates was not easy.