Related
Searched but found nothing..
Is it possible that after flashing so many ROMs and upgrading and wiping and stuff that it can affect your phones performance and compatibility?
Like is it good to just RUU and re-root when u find a ROM you really like and are going to stick with to provide a "fresh" start? kind of like formatting and reinstalling windows?
We only have 256 megs to fragment lol.
I have found that run ruu in the past has fixed issues, but have't had to do it in a while - at least since we found the 2.1 root method.
I have done this a couple times and haven't noticed any improvements in performance or smoothness on my phone. Not saying it won't happen, just saying that it didn't happen for me so I assume this is likely the case for others too. My inexperienced answer would be to not worry about wasting your time with doing it. But also know that it won't hurt a thing either
I`ve had my SGS for a few months now and I`ve played around with this and that, but the only thing I have`nt tried (and I`m not sure of) is flashing a new ROM and or Kernel.
Would I gain anything if I changed my stock 2.1 Eclair kernel?
I noticed I have some options in OLCF, is it as easy as selecting one and see if it improves anything?
As for the ROM`s I know there thousands out there, but do any of them increase performance in anyway shape or form?
It can be soul draining searching and looking through all these forums, sometimes its just easier to get a professionals option.
Cheers.
Would I gain anything if I changed my stock 2.1 Eclair kernel?
Yes do you not have the Froyo update for the phone yet .
As for the ROM`s I know there thousands out there, but do any of them increase performance in anyway shape or form?
Again yes but many ROMs are a work in progress rather than a finished article .
You need to read all the sticky s relative to ROMs and flashing before looking at a new ROM . To many dont understand and brick the phone .
Personally i would be looking to your official upgrade to Android 2.2 via Kies .
jje
Yea, I bought my SGS GT-I9000 with Optus during early Dec 2010, after installing the latest Kies program on my PC it connected fine and updated to Android 2.2 Froyo.DTJP5 (later in Dec) fine.
Haven't rooted nor tried to apply any Lagfixes.
Have reset it to factory default settings a couple of times.
I am quite disappointed with the general performance of the unit - often slow menu navigation and app options selections & closing etc., and surprised such apparent slowness is so significant.
Am researching and browsing various sites about it, and will certainly take steps to improve it at some stage, hoping in the short term that Samsung will include improvements to the file system "stuttering" and other reported slowness in the next official firmware update.
I`ve read a few post`s saying that Froyo 2.2 was`nt that much different and really not that worth getting, I`ve rooted mine and applied OCLF and it does fly, no and again it slows down a bit but I`ve apps going in and out of it like a porno movie.
That`s the main reason I dont change doing a ROM myself, cause I`m afraid I`d "brick" it. Maybe in time custom ROM`s will be made "official" and safe, even to idgits like me.
There`s only some much reading on here I can do before me brain goes qoiwehfdowjdbcw.
Thanks for the advice, I dont want to reck me phone yet, the wife will kill me!
Wanted to use kies, but am running win 7 64bit,kies doesnt see my phone, gave up, and finally odin hacked it.
Well worth it, now it is a real phone.
Sent from my GT-I9000 using XDA App
mloc33 said:
I`ve read a few post`s saying that Froyo 2.2 was`nt that much different and really not that worth getting, I`ve rooted mine and applied OCLF and it does fly, no and again it slows down a bit but I`ve apps going in and out of it like a porno movie.
Click to expand...
Click to collapse
that was exactly what I thought until I upgraded to a custom ROM (Darky in my case, but any will do). The speed and functionality improvements are amazing. Aside of that, you'll get updated stock apps and a much improved Market.
Be sure to read a lot and back up everything, though.
So what are the key things I need to know in order to get the right ROM?
From what I`ve read so far, I get ROM Manager, install CWM through this and select what ROM I want?
Is it that easy? I already have a Titanium backup....
I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks
lchiu7 said:
I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks
Click to expand...
Click to collapse
I have a rooted N1 that I bought in February of 2010, a month after they became available. It was rooted when I bought it on eBay and running one of the CM ROMs. I don't know how to root a phone, sorry.
I DO know how to load ROMs and have variously updated and modded the phone myself. I have been fortunate in that my power button has never failed, but while I was running a series of OTA ROMs (ROMs based on the pure Android released from Google) I noticed that the latest ones disabled the trackball wake feature, meaning that the power button was the only way to wake the phone. I had gotten used to trackball wake with the first CyanogenMod ROM, and so once I learned that the power button was a weak spot, I decided that a CM ROM or a modded AOSP ROM was the only option.
As there were some issues with CM ROMs that took months to work out (see WONK), I went with an AOSP ROM that I found here http://forum.xda-developers.com/showthread.php?t=1121595 . It's now a dead thread, but the links to the 3.1 version of the ROM is still there. I use the apps2SD version of the 3.1 ROM.
There are several more ROMs that are more recent, but this one is the best one I have ever found. You will need to root your phone and install a custom recovery (like AmonRA or ClockworkMod) to use it, but I have found that everything works well and it is extremely stable. I have over 70 apps on my phone with over 80MB of internal memory still available.
The only problem I have ever had is an intermittent battery drain, which I was able to fix by wiping the cache files (Dalvik and regular caches). The custom recoveries have the ability to do this. Apparently any corruption of the cache files causes excessive battery drain, but wiping them (which causes the phone to rebuild them on the next boot - a 4 minute process!) gives you fresh cache files and fixes the problem.
If you are willing to learn how to root your phone and install a custom recovery, I can recommend that ROM. Once the first part is done, loading a custom ROM is as easy as putting the zipped ROM file on your SD card, getting to the bootloader and telling it to install the zip.
Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.
addam360 said:
Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.
Click to expand...
Click to collapse
Thanks. I never expected the new ROM to fix the touch input problems. That is a fundamental hardware issue.
I was thinking along the same lines regarding ICS. It's gone AOS now and I now see somebody has built a port for the N1 already. So if I wait a bit if I choose to install some custom firmware, if the reports suggest ICS runs fine on the N1 (to confirm that Google didn't release it because there was a performance issue with the N1 and ICS) then that's the route I will take. In for a penny, in for a pound I guess!
lchiu7 said:
(to confirm that Google didn't release it because there was a performance issue with the N1 and ICS)
Click to expand...
Click to collapse
The issue is not because of performance, its the system partition size is not enough... Gosh! Did u know Galaxy Nexus's system dump is 600MB+
I don't own a i9000 myself. My GF, however, does. And she's getting kind of tired of the lags, the reboots and so on with the stock ROM. I've plenty of experience with rooting and custom ROMs (well, enough any way), but I don't know anything about the i9000 - and I must say, this has to be the subforum with the worst documentation (or lack thereof) on the whole of xda! Reading up on the device is difficult - seeing as all the sticky threads were last updatet in 2011 - or even 2010. The ROM-threads mention NOTHING about anything special, no FAQ, no bug list, no nothing, and yet, as I read more in mor and more threads, apparantly most of them have one of thre (or four) different partition layouts and/or data/adata/cahce or whatever "fix" - without mentioning at all until some poor user post a problem which is due to one of these (completely unmentioned) fixes.
This probably works well for someone who has been coming here twice a week since 2010, and you, of course, do as you wish! But for me it is impossible to get a grip of anything with this device, as there are no real proper sources for information (a least not stickied) and I can't really read some thousand forumpages in the hopes of getting a glimpse of knowledge now and then. So I am totally dependent on some of you guys to help me (and my GF) out. Iæve listed some questions/topics below, and hope you can answer some of them. Alo, sorry for the wall of text before even reaching the questions.
NAND:
Q1: There are two different versions of the i9000, one with one small fast NAND chip and a big slow one (only /system partition on the fast one)? There are most of the latter?
Q2: Beacause of this, different ROMS have different partitions to put some of the data on the fast partition?
Q3: There are no way to know which partition layouts a ROM uses unless t mentions it (which they very seldom seem to do)?
Q4: Are there two or more different partition layouts for putting something on the fast partition?
Data fixes
Q5: There are multiple ways to handle that here aren't enough space on the fat nan for all app data. Is there an up-to-date description and comparison between them, or could someone enlighten me about the key differences?
Q6: Are there any of them who doesn't require any manual intervention to move app data to and from the fast partition, so it doesn't fill up? Or at least has a GUI to manage it?
Q7: Would a i900 with a fast nand benefit from having a ROM without any of these fixes and such?
Q8: Anything else i9000-specific I should know?
10: Doe anyone have a suggestion for a low maintenance ROM or ROM+kernel combo? The clue here is that it should require no maintenance and be a stable as possible. Speed and gaming performance is not an issue as long as it isn't worse than stock.
11: Is it possible to "re-stockify" the pone if it needs to be sent in for repair, without a trace of rooting. (This, I could probably search for an answer to myself, but while I'm here...
This was a lot! I still hope some of you could find the time to post an answer to a question or two. I'd really appreciate it!
You don't have to know anything
naguz said:
I don't own a i9000 myself. My GF, however, does. And she's getting kind of tired of the lags, the reboots and so on with the stock ROM. I've plenty of experience with rooting and custom ROMs (well, enough any way), but I don't know anything about the i9000 - and I must say, this has to be the subforum with the worst documentation (or lack thereof) on the whole of xda! Reading up on the device is difficult - seeing as all the sticky threads were last updatet in 2011 - or even 2010. The ROM-threads mention NOTHING about anything special, no FAQ, no bug list, no nothing, and yet, as I read more in mor and more threads, apparantly most of them have one of thre (or four) different partition layouts and/or data/adata/cahce or whatever "fix" - without mentioning at all until some poor user post a problem which is due to one of these (completely unmentioned) fixes.
This probably works well for someone who has been coming here twice a week since 2010, and you, of course, do as you wish! But for me it is impossible to get a grip of anything with this device, as there are no real proper sources for information (a least not stickied) and I can't really read some thousand forumpages in the hopes of getting a glimpse of knowledge now and then. So I am totally dependent on some of you guys to help me (and my GF) out. Iæve listed some questions/topics below, and hope you can answer some of them. Alo, sorry for the wall of text before even reaching the questions.
NAND:
Q1: There are two different versions of the i9000, one with one small fast NAND chip and a big slow one (only /system partition on the fast one)? There are most of the latter?
Q2: Beacause of this, different ROMS have different partitions to put some of the data on the fast partition?
Q3: There are no way to know which partition layouts a ROM uses unless t mentions it (which they very seldom seem to do)?
Q4: Are there two or more different partition layouts for putting something on the fast partition?
Data fixes
Q5: There are multiple ways to handle that here aren't enough space on the fat nan for all app data. Is there an up-to-date description and comparison between them, or could someone enlighten me about the key differences?
Q6: Are there any of them who doesn't require any manual intervention to move app data to and from the fast partition, so it doesn't fill up? Or at least has a GUI to manage it?
Q7: Would a i900 with a fast nand benefit from having a ROM without any of these fixes and such?
Q8: Anything else i9000-specific I should know?
10: Doe anyone have a suggestion for a low maintenance ROM or ROM+kernel combo? The clue here is that it should require no maintenance and be a stable as possible. Speed and gaming performance is not an issue as long as it isn't worse than stock.
11: Is it possible to "re-stockify" the pone if it needs to be sent in for repair, without a trace of rooting. (This, I could probably search for an answer to myself, but while I'm here...
This was a lot! I still hope some of you could find the time to post an answer to a question or two. I'd really appreciate it!
Click to expand...
Click to collapse
If like I understand this is not your device, then you just have to know that it's going to work well, without any rebots or lags.\
I cen ensure you she's going to engoy the new system, like you probably know.
she can use eather the official cm10http://get.cm/?device=galaxysmtd
official thread
with stock rom, it's good.
also if she has the new line of galaxy s then you can get the fishers version of cm10 in the official thread
it's good, it's not your device so don't mess with that, just install ones and that it.
ps remember to save all data and make sure she knows the google name & password!.
It works great dont wory
Thank you. Heh, you are right, essentially I just want stable everyday user experience for her. So with CM10 there are no need for manually altering anything to run out of space, like it was in CM9? I know it doesn't use a "data ix" anymore, but there is no info about partition layout (or anything else for that matter...) in the CM10 OP. Which seems to have angered someone in the thread that I asked about.
I was thinking of installing CF root first and then backup all of her stuff using Titanium Backup and move pics etc to external sdcard, as I read somewhere that installing cm10 will delete internal SD. Does it? Because the CM10 OP doesn't mention anything about it, and that would be a serious omission. Will external SD in any way be affected?
Sd won't be formatted by itself, but thorough backup is always recommended. If it were my wife's phone I was handling, I'd backup that sd card in a heartbeat
To make a long story short, there's two different partition layouts, one which is best suitable for the newer line of sgs to utilize the faster chip, which fishears cm10 rom has, and one which is sort of a compromise between system space and speed. Check first posts of fishears thread to see if you have the fast chip. Both partition layouts should give you no trouble with storage space, and data fix as in cm9 is a thing of the past.
Seems you've got the right idea, start with gingerbread and cf root in Odin with repartition, then go down the road with your rom of choice. Good luck.
Sent from horseback.
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
Mind you, I'm only talking about cm10 based roms here, different partition layouts is not an issue with gb or ics roms.
Sent from horseback.
Hi,
I hope I won't get blasted for my questions having been asked before but I did search and couldn't find anything exactly touching on what I wanted to ask about...
So I have a Galaxy note, n7000 model, and at one point I did flash a custom ROM, but for some reason or other the phone stopped functioning properly.
So I then went back to my original ROM (I'm in the UK), and the phone's performance is extremely sluggish, even right from a reset, everything lags, launching the app menu, loading apps, switching between main screen pages, etc.
I don't know why the phone has become so slow it used to be a fast competent phone for basic OS functionality I've described.
My question is, does anyone know why this might be?
I don't believe I reflashed a stock kernal when flashing the original ROM back on, could this be the problem?
Or is there any other reason the phone might now be slow?
And any advice as to how I can get it working with the performance it used to have, would be much appreciated.
Thanks again for