Related
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
I'm running SS 3.05 and have been able to flash several roms (all GB because I need a camera) that others rave about. I have not gotten good performance out of any of them. The worst ones seem to cause almost non-stop force closes on apps while the "best" ones function but my phone runs very hot even when not being used. Just tried Steel Droid 5 over the weekend and I at least got it up and running but the phone was noticeably hot even when just sitting on the counter with the screen off.
I've uninstalled and reinstalled Safestrap a couple of times, deleted and recreated rom slots repeatedly and have just had no success. Is it possible that there is something weird about my phone? Is it just wonky? It does run normally on the stock rom, or at least as normally as any D3 can run but I'd love to run a meaner, leaner rom on my phone.
If anyone has any ideas I'd love to hear them.
JoeHockey said:
I'm running SS 3.05 and have been able to flash several roms (all GB because I need a camera) that others rave about. I have not gotten good performance out of any of them. The worst ones seem to cause almost non-stop force closes on apps while the "best" ones function but my phone runs very hot even when not being used. Just tried Steel Droid 5 over the weekend and I at least got it up and running but the phone was noticeably hot even when just sitting on the counter with the screen off.
I've uninstalled and reinstalled Safestrap a couple of times, deleted and recreated rom slots repeatedly and have just had no success. Is it possible that there is something weird about my phone? Is it just wonky? It does run normally on the stock rom, or at least as normally as any D3 can run but I'd love to run a meaner, leaner rom on my phone.
If anyone has any ideas I'd love to hear them.
Click to expand...
Click to collapse
Weird. Minimoto ran great for me. I wonder if it's an app you install?
Maybe you just have a bad app or two. You can try loading the phone stock and install only an app or two at a time and see if the phone runs better. Maybe after loading one particular set of apps you'll notice a problem.
I run minimoto as well. I don't get the miracle battery savings that others report - mine is essentially the same as running stock for me - but it is rock-solid stable, unlike stock, which tends to go wonky on me after about 5 days or so.
1
I have noticed something like that, I´m on XT862 and I have better baterry performance on Steeldroid 5.0 and If I give a try with Minimoto I have noticed higher battery drain and hot back of my device. So I always went back to SD 5.0. Strange that people have different experiences =).
doogald said:
Maybe you just have a bad app or two. You can try loading the phone stock and install only an app or two at a time and see if the phone runs better. Maybe after loading one particular set of apps you'll notice a problem.
I run minimoto as well. I don't get the miracle battery savings that others report - mine is essentially the same as running stock for me - but it is rock-solid stable, unlike stock, which tends to go wonky on me after about 5 days or so.
Click to expand...
Click to collapse
Would a app that tracks battery usage by app possibly give me that info as well? Slowly adding apps one at a time will be a major chore...
JoeHockey said:
Would a app that tracks battery usage by app possibly give me that info as well? Slowly adding apps one at a time will be a major chore...
Click to expand...
Click to collapse
Settings-applications-battery use
I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night
The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.
Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.
goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.
Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.
EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.
Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.
Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?
Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.
I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4
Hello,
For the last 6 months or so, I've experienced many lag issues with my device. At the begging, I had a CM11 ROM installed on my phone, so I decided to revert back to the V20B official european firmware because I thought those lags were related to the ROM. But nothing changed, and as of today I still have responsiveness issues.
This lag issue appears from time to time, and makes my device basically unusable. It feels like the whole CPU is hogged by an application, or like I underclocked my device to 53mhz on purpose. During these lags, trying to wake up my device will take up to 5 seconds, and navigating the main screen will be nearly impossible. Also, my phone will get very hot which would imply that my CPU is indeed used by an application. Sometime the issue will disappear by itself after a few minutes, but I usually reboot the device which temporarily fixes the problem.
I have tried to disable LG MLT, and I think it helped but the lag still occasionally occurs.
I don't really use third party applications either.
I think these lags might be related to the Google Chrome browser, but it doesn't make any sense as it is an official app.
Anyway if any of you have an idea on how to fix the issue or how to find the application/service/whatever hogging the CPU I'd be grateful
Thanks !
I did experience such lags in CM11 after a few days of usage.But talking about stock, these freezes sound bit weird.You might want to check your installed apps.Download watchdog lite from play store and let it watch on agressive mode.Also check if your phone is hot when these freezes occur, might be the throttling kicking in.
I also experienced this kind of lags due to bad gapps I had installed back in the day, though stock ROM comes with gapps so it's not that.
Thanks for your reply,
I installed Watch dog lite and I'm now waiting for an alert. I hope it will give me the name of the culprit
If you are rooted which i assume you are. You can try app from playstore called "lagfix" (fstrim)
Sometimes really helps. Sometimes it doesn't
I've noticed lately that my G920T has a terrible time keeping GPS lock. Definitely a pain when I'm trying to use Waze or other GPS apps. It seems to be significantly worse in my car but overall, GPS Status reports that most satellite signal health is bad. I don't have a case on my phone, so I really have no idea what could be the issue. I've tried resetting AGPS to no effect.
I'm currently on XtreStoLite 3.3.1, running Arter's kernel, but I have experienced this issue on other kernels as well.
I've been noticing this too. Especially when driving. It seems to happen most when an app installs/updates in the background. Toggling GPS on and off in quick settings fixes it, but it's inexcusable and impossible to do while driving, when you need it most.
socal87 said:
I've noticed lately that my G920T has a terrible time keeping GPS lock. Definitely a pain when I'm trying to use Waze or other GPS apps. It seems to be significantly worse in my car but overall, GPS Status reports that most satellite signal health is bad. I don't have a case on my phone, so I really have no idea what could be the issue. I've tried resetting AGPS to no effect.
I'm currently on XtreStoLite 3.3.1, running Arter's kernel, but I have experienced this issue on other kernels as well.
Click to expand...
Click to collapse
Are you running greenify? You'd have to toggle doze off... If not download the gps conf files from online and use the appropriate one for your geographic region.
I've experienced similar, as well as some other random stuff that I won't get into here, started about 5 weeks ago. Basically seems to come down to having power saving enabled and maybe screen off (I'm almost always running power save). Francis might be onto something with doze, but it shouldn't be disabling GPS while it's actively running in an app (navigation, fitness trackers, etc) whether PS enabled or screen on or not. I've had this phone since last October, done a few different ROMs, but I'm currently stock (EPF1) with just root, no other mods and have been in that state for several months (because I've been lazy), no updates or anything. Tried removing apps that might have been installed recently at the time, to no avail. No clue what the deal is, but I'm gonna flash some custom ROMs again, which hopefully solves whatever bug issue this is.
Don't think I provided any solution, but wanted to give some input as I had similar issues.
I discovered the problem. I was using Arter97's kernel. Re flashed the kernel that comes with the ROM; GPS works much better.
socal87 said:
I discovered the problem. I was using Arter97's kernel. Re flashed the kernel that comes with the ROM; GPS works much better.
Click to expand...
Click to collapse
So that's what's going on