Hi all,
I've been following all the Froyo hoo-hah with increasing amounts of anxiety. I'm on T-Mobile in the UK (so don't have it yet anyway) but what I'd like to know from an XDA expert is what's the best advice for me at the moment. The things I'm curious about are as follows:
My Eclair version appears to be JF3, how can I get it up to date?
Is the stock Froyo actually any good and worth upgrading too? - reports suggest it's no major improvement and in some cases actually a step back e.g. increased battery drainage, no GPS improvement, worse lag than Eclair etc
What is the current route (not root) of choice for getting the best performance from the SGS? for example, would the stock Froyo with the voodoo lag-fix be an adequate route or is there something better. If I was starting from scratch, assuming I'm relatively technical, what would you suggest?
Is Odin a better solution than Kies (I'm only using Kies for updating purposes anyway).
Last question, is it worth using a backup app or just a combo of appBrain and Kies?
My main concern is just reducing the, what seems to be increasing, lag on my current version (with OCLF installed). There's nothing more annoying when you're trying to show your phone off than it hanging.
Sorry for all the questions and I know some of you would say "Go search the rest of the threads!" but sometimes that just creates more questions than answers.
I must say though that it seems more and more that Samsung's software guys aren't really that competant.
I really very much ppreciate any help or advice anyone can suggest
Hey guys, as far as the Nexus One and CM 7 goes, what are the optimal settings to keep checked in CM settings, and what's the best kernel/settings for speed, but great battery life? I downloaded and installed Pershoot's kernel. Please let me know because I need the phone for long periods of time for two weeks, but I can't get an extended battery. I'm new to the N1, hence why I ask you all and can't test on my own. Thanks!
CM7 is pretty well pre-configured for great battery life and great performance. I don't know if there is much you could change that would show any benefit within the install.
I think redstar has been creating some of the most popular kernels as of late. Great performance and battery life (from what I read).
Also, if you aren't running the nightlies, I can highly recommend it. There have been some substantial performance enhancements and battery savings that have been a result of some major bug fixes. Build #87 has been working great for me.
bassmadrigal said:
CM7 is pretty well pre-configured for great battery life and great performance. I don't know if there is much you could change that would show any benefit within the install.
I think redstar has been creating some of the most popular kernels as of late. Great performance and battery life (from what I read).
Also, if you aren't running the nightlies, I can highly recommend it. There have been some substantial performance enhancements and battery savings that have been a result of some major bug fixes. Build #87 has been working great for me.
Click to expand...
Click to collapse
Thanks so much, but could anyone else please provide me with further/specific/good cyanogen mod settings for the N1, such as what to check, how much VM heap, etc?
I'm gonna stick with pershoot for kernels, as i use him for the G2, and before the G1.
I freakin' love nightlies, BUT, the reason I'm running stable is because I'm leaving the country for two weeks, and I won't have access and the freedom to change my ROM due to not having a computer all the time. Hence the stable version - I do love nightlies though!
To reiterate, what are the best CM settings for CM7? Thanks in advance, guys!
Well, if you are going to run stable, do a search for the "wonk fix" and flash that zip. It is one of the major fixes in the nightlies that improves battery life.
I'm still not sure that there are any settings you could really play around with that would show any tangible benefit.
And with build #87, it has been rock solid for me. I thought the ADW EX transistions in the past were smooth. You don't need to constantly update the nightlies if you can find a good one. Just sit it out until you feel like updating again. And #87 is a great one to be at.
bassmadrigal said:
Well, if you are going to run stable, do a search for the "wonk fix" and flash that zip. It is one of the major fixes in the nightlies that improves battery life.
I'm still not sure that there are any settings you could really play around with that would show any tangible benefit.
And with build #87, it has been rock solid for me. I thought the ADW EX transistions in the past were smooth. You don't need to constantly update the nightlies if you can find a good one. Just sit it out until you feel like updating again. And #87 is a great one to be at.
Click to expand...
Click to collapse
Sounds good, man. Thanks for your help and telling me about the wonk fix! Although I'm not 100% sure what it's for.
Should home and messaging in memory be checked?
One more issue, when I nees to press the capacitive home, menu, back, and search button, I always have to tap a bit higher than where thee keys are actualy located on the screen.everything else about the touch screen is fine. what's the reason for this?
isikh said:
Sounds good, man. Thanks for your help and telling me about the wonk fix! Although I'm not 100% sure what it's for.
Should home and messaging in memory be checked?
One more issue, when I nees to press the capacitive home, menu, back, and search button, I always have to tap a bit higher than where thee keys are actualy located on the screen.everything else about the touch screen is fine. what's the reason for this?
Click to expand...
Click to collapse
The wonk fix was an issue that plauged CM for quite a while on the N1. It caused hard lockups of the microphone and the screen. Also, because of it, the microphone was never able to enter its low-power sleep state. With the wonk fix, you won't have any issues with the mic, and the phone will reach its low-powered sleep state.
I have never enabled the keep in memory options. My understanding is these settings were more for devices that had limited RAM (like the G1), because Android would dump these programs to free up memory for other apps, so when you went to them, it would take a while for the system to restart them. I haven't ran into a need to do this on the N1. The heap size limits the amount of ram that an app can use. Unless you are running some crazy memory intensive apps, there is really no need to adjust this. It won't help most of the apps that are out there.
As for the capacitive buttons, welcome to the wonderful world of the N1 digitizer (touchscreen). I don't know of any way to adjust this, but you get used to it pretty quickly.
bassmadrigal said:
The wonk fix was an issue that plauged CM for quite a while on the N1. It caused hard lockups of the microphone and the screen. Also, because of it, the microphone was never able to enter its low-power sleep state. With the wonk fix, you won't have any issues with the mic, and the phone will reach its low-powered sleep state.
I have never enabled the keep in memory options. My understanding is these settings were more for devices that had limited RAM (like the G1), because Android would dump these programs to free up memory for other apps, so when you went to them, it would take a while for the system to restart them. I haven't ran into a need to do this on the N1. The heap size limits the amount of ram that an app can use. Unless you are running some crazy memory intensive apps, there is really no need to adjust this. It won't help most of the apps that are out there.
As for the capacitive buttons, welcome to the wonderful world of the N1 digitizer (touchscreen). I don't know of any way to adjust this, but you get used to it pretty quickly.
Click to expand...
Click to collapse
Okay - I'll keep those disable then, and yay digitizer. Also, I don't know if it's the wonk fix, but my camera is force closing now
isikh said:
Okay - I'll keep those disable then, and yay digitizer. Also, I don't know if it's the wonk fix, but my camera is force closing now
Click to expand...
Click to collapse
No, the wonk doesn't affect the camera. What is your radio version (aka baseband)? With the N1s we usually just refer to the two sets of numbers after the underscore "_" (eg 5.08, 4.06, etc). The 5.08 is the version that google sent out with the Gingerbread update and overall seems to be the best consistent performer for the phones. The 4.06 seems to crash the camera and/or camcorder. The 5.12 seems to be really hit or miss. Some phones it runs great, others they get all sorts of issues. I usually recommend the 5.08.
bassmadrigal said:
No, the wonk doesn't affect the camera. What is your radio version (aka baseband)? With the N1s we usually just refer to the two sets of numbers after the underscore "_" (eg 5.08, 4.06, etc). The 5.08 is the version that google sent out with the Gingerbread update and overall seems to be the best consistent performer for the phones. The 4.06 seems to crash the camera and/or camcorder. The 5.12 seems to be really hit or miss. Some phones it runs great, others they get all sorts of issues. I usually recommend the 5.08.
Click to expand...
Click to collapse
Okay, and my apologies, with college I've missed and forgot key things about android - how do I find my radio version? Boot into fastboot or the bootloader?
EDIT: Under basband version, on the about phone menu, it says:
32.24.00.22U_4.03.00.21_2
Is that baseband 4.03?
Yes, the radio on your phone is 4.03. I would highly recommend updating it to 5.08. There is a basic guide in the wiki for it, or you can hit up the N1 wiki on xda for a more in depth guide.
the wonk fix and and kinda directly related to that fix greatly fixed some battery issues which kinda makes running the last stable version not worth it. the newest nightly is so much improved on battery idle current draw that its something needs to be emphesized. its that good where you can be unplugged for 8 hours and lose 3% battery idle standby, wifi on. 3-4mA current draw.
that aside, pershoots kernel is great, redstar too. there's not much i do anymore with settings on cm7 cause its so good lately.
bassmadrigal said:
Yes, the radio on your phone is 4.03. I would highly recommend updating it to 5.08. There is a basic guide in the wiki for it, or you can hit up the N1 wiki on xda for a more in depth guide.
Click to expand...
Click to collapse
Where is said wiki located?
I'd like an in depth, detailed noob guide as to avoid messing up the phonee
Also, thanks for the info Roger. I'm gonna stick with nightly #87 since peeople are saying the battery life is great and it's stable.
isikh said:
Also, thanks for the info Roger. I'm gonna stick with nightly #87 since peeople are saying the battery life is great and it's stable.
Click to expand...
Click to collapse
that's the perfect choice, you will be very happy.
isikh said:
Where is said wiki located?
I'd like an in depth, detailed noob guide as to avoid messing up the phonee
Click to expand...
Click to collapse
I'm on my phone so it is hard to do links, but if you go into the Nexus One General forum, I think it is one of the first few stickys in there.
Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Hey
I just updated my Galaxy S to firmware 2.3.3, JVQ through kies
I was just wondering if there would be any dramatic performance advantage if i used a custom ROM or something?
Also another question, when i updated through kies i didnt do a factory reset, Should i do one now? would it make any difference to my phones poerformance?
Thanks for any help
If you are currently experiencing nothing out of the ordinary (errors, lag, etc.) then I don't feel doing a factory reset would help in any way.
Custom ROMs are made for plenty of different things. If you like what Samsung has to offer, keep at it. If you feel you'd enjoy more speed, power, etc., then try a custom one. That's literally why people make one—to improve on an area where they feel could use improving. Personally, I use CM7. If you're after power, that's the ROM for you.
Thanks for your reply, I do sometimes get a little bit of lag, sometimes apps freezing up...
What im really asking is how noticeable would the difference in performance be?
Shotdog said:
Thanks for your reply, I do sometimes get a little bit of lag, sometimes apps freezing up...
What im really asking is how noticeable would the difference in performance be?
Click to expand...
Click to collapse
I use CM7 with Glitch's kernel, and I usually have my phone running at 1.2 GHz. I never, ever experience lag in the launcher—opening the app drawer, transitioning between homescreens (filled with widgets); for the most part, my phone doesn't lag when using/multi-tasking between apps (although some apps still take time to load, of course); I virtually never, ever have any lag whatsoever when browsing the web (I use Opera Mobile); and I rarely have any stuttering in games, although I simply bump my CPU up a bit more if I need the extra power (some games are fairly intensive).
For the most part, I don't experience lag. When I do, I feel like I haven't tweaked my phone quite right. I quickly jumped off the Samsung boat once I realized that there were different, more performance-oriented ROMs available—and I must say that I am extremely pleased with both the performance and elaborated settings menu of CM7, which leaves for a truly customizable experience. If you're at all interested in an experience like this, I'd start looking into custom ROMs. It takes a little bit to wrap your head around it all, but once you learn the basics and set your phone up just right, you'll have a much more enjoyable experience. I certainly have.
I found ram tweaks had the most effect, there's a thread in the dev section on optimizing your phone, or you can use the simplicity rom, I think it has those tweaks all pre done.
Hi guys
I got an x1 few days ago. I'm very happy with the phone and I updated it to the new firmware 14.1.G.2.257.
In the last 3 days, after the update, I got 3 random reboots. I don't know if it was happening also with the old firmware cause I used it just for few hours.
Now I'd like to understand if it is a software problem so I need just to wait for a new firmware or it is an hardware issue so I need to return the phone.
Thanks to anyone would help me.
j0sh0 said:
Hi guys
I got an x1 few days ago. I'm very happy with the phone and I updated it to the new firmware 14.1.G.2.257.
In the last 3 days, after the update, I got 3 random reboots. I don't know if it was happening also with the old firmware cause I used it just for few hours.
Now I'd like to understand if it is a software problem so I need just to wait for a new firmware or it is an hardware issue so I need to return the phone.
Thanks to anyone would help me.
Click to expand...
Click to collapse
in all honesty since having this phone i have not had one random reboot. When ever i upgrade firmware i always do a fullwipe to rule any issues out. But one thing i have seen happen is some apps can cause reboots, some apps cause wakelocks and some apps can cause battery drain. What i would do as a test is reflash firmware and dont install any other apps other than your standard google apps, see how that goes
sofir786 said:
in all honesty since having this phone i have not had one random reboot. When ever i upgrade firmware i always do a fullwipe to rule any issues out. But one thing i have seen happen is some apps can cause reboots, some apps cause wakelocks and some apps can cause battery drain. What i would do as a test is reflash firmware and dont install any other apps other than your standard google apps, see how that goes
Click to expand...
Click to collapse
thanks my only concern is about hardware but I don't think this is the case... maybe there is a bad memory management in this firmware? I read about other people having issues like this.
j0sh0 said:
thanks my only concern is about hardware but I don't think this is the case... maybe there is a bad memory management in this firmware? I read about other people having issues like this.
Click to expand...
Click to collapse
I really dont know, i keep hearing so may contrasting issues with this phone. I have not had 1 issue with the phone, but everywhere i see soo many issues, im certain theres a bad batch of z1's out there. I don't think its a hardware issue in your case, i cant really be sure about the memory management becuase this newer firmwares changelog included better memory management. i really think you should start from scratch as a test, and slowly add other apps, this way you can slowly eliminate whats causing this issue.
sofir786 said:
I really dont know, i keep hearing so may contrasting issues with this phone. I have not had 1 issue with the phone, but everywhere i see soo many issues, im certain theres a bad batch of z1's out there. I don't think its a hardware issue in your case, i cant really be sure about the memory management becuase this newer firmwares changelog included better memory management. i really think you should start from scratch as a test, and slowly add other apps, this way you can slowly eliminate whats causing this issue.
Click to expand...
Click to collapse
It does make sense... I'll try
Hello everyone,
I never messed around with my Samsung GT-S5300 a lot, I wrote some apps and rooted it, but that's about it.
One thing I always disliked about my phone was the lack of support for Droidwall (which I believe uses iptables?).
Another thing I disliked is how slow it becomes in the long run.
As a result of browsing this forum, I have a few questions. There is just so much choice and information I have no idea where to start.
What Kernel should I use if I'm ONLY interested in having Droidwall support? Or is there a slightly better Kernel which makes the responsiveness of the phone in overall faster as well. I rarely do anything with it, WhatsApp, some browsing and some calls now and then so I just want the interface to be responsive. I'd prefer a custom kernel, but if someone knows a Rom which fulfills all of these desires, I'd be happy to hear about it.
Last but not least, if I'm only installing a new kernel, does that work on my current installation (latest Dutch firmware provided by Samsung) or will I have to reinstall first? If so, are there means of easily backing up all my texts and contacts, I honestly don't care about anything else.
Thank you in advance!
Lennard
Bump! None able to help me on my way?
LennardF1989 said:
Hello everyone,
I never messed around with my Samsung GT-S5300 a lot, I wrote some apps and rooted it, but that's about it.
One thing I always disliked about my phone was the lack of support for Droidwall (which I believe uses iptables?).
Another thing I disliked is how slow it becomes in the long run.
As a result of browsing this forum, I have a few questions. There is just so much choice and information I have no idea where to start.
What Kernel should I use if I'm ONLY interested in having Droidwall support? Or is there a slightly better Kernel which makes the responsiveness of the phone in overall faster as well. I rarely do anything with it, WhatsApp, some browsing and some calls now and then so I just want the interface to be responsive. I'd prefer a custom kernel, but if someone knows a Rom which fulfills all of these desires, I'd be happy to hear about it.
Last but not least, if I'm only installing a new kernel, does that work on my current installation (latest Dutch firmware provided by Samsung) or will I have to reinstall first? If so, are there means of easily backing up all my texts and contacts, I honestly don't care about anything else.
Thank you in advance!
Lennard
Click to expand...
Click to collapse
You can use infuzion or vM00 or even riskeykernel kernels...