Related
Hi: I've super-upgraded to TuMa 1.3 with very good happy time till now!
Many thanks guys, especially Tuma!!
i just have one problem, when typing on my keyboard, sometimes, not all the time, keys stick and after pressing a key i get something likeeeeeee thissssssssssssssssssssssssssssssssssssssssssssssssssssssss
or, even worse, the backspace key gets stucked the same way and it erases all EAAARRRHHHGGGG!!!
is this fixable??, is anyone else having this problem???
I use the keyboard big deal...
Have the exact same problem with helmi 1.3
tehCORE said:
Have the exact same problem with helmi 1.3
Click to expand...
Click to collapse
So, I see now that upgrading (something I had planned) to helmi 1.3 doesn't repair this problem. I would like to know where this problem originates to find a solution. I'm using now Pocket Hack MAster with the device running at 597 Mhz and the problem is still there! :evil:
Some advice??
EDIT: I've removed the CPU Meter on the upper bar. It seems to work faster and better. Still waiting to see if the problem arises again..
i'm on helmi_c 1.1b and have this problem too. May be that is hardware problem or driver time bomb?
change the keyboard repeat settings, and delay settings, I have had this problem with every wm5 rom, and by changing the settings it appears to fix this prob.
tesing.. thanks for reply...
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
I've had success with changing the keyboard repeat settings but it comes back eventially. I've had the problem on every WM5 ROM, but less-so on the most recent Helmi ROMs with the AKU update.
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Black6spdZ said:
its not the keyboard repeat settings causing this.. something to do with the device driver priority.. it happens less when you overclock.. I have to stay at 590 to make keyboard typing bearable or else some letters don't register or the repeat sticks..
Click to expand...
Click to collapse
I'm now using Pocket Hack Master with the feature of using different speeds for different apps. It happens less, so, could be the driver priority on CPU intensive apps. Because the SMS app now seems to need more CPU power than before :? :? (bar & text space redraw or something), it is one of the apps I've selected to run at 590 Mhz:shock:.
Black6spdZ said:
its only in the built-in mail program... try typing in O2 SMSPlus or IE or something else
Click to expand...
Click to collapse
I'm having this problem with other programs also (i.e.: Softmaker TextMaker, Pocket MindMap). Also, someone said that when using the e-mail (nor the SMS) part of the program the problem doesn't happens.. I've not tried myself as I don't currently use e-mail on my device.
xykosomatik said:
probably something to do with the ROM as well... it was present on Tuma 1.3 and Helmi AKU 2.3, but after flashing AKU3.0 1.2 keyboard is working fine, be it 200mhz or 570mhz using xcpuscalar.
Click to expand...
Click to collapse
Please, xykosomatik, confirm so. I would be eager to upgrade if this problem is solved on this ROM, as I use the keyboard typing 80% of the time on my device.
Thanks all.
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
It seemed to make an improvement for me, but time will tell. This issue seems to come and go on my phone.
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Tuatara said:
arieltools said:
I can't try this right now. Doesn't have the device with me. Someone can report on this helping with the problem, please?
Black6spdZ said:
someone else try this and see if its not just my imagination but this seems to help significantly
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QwertyKey]
"Priority256"=dword:00000001
Is it the apps use of cleartype?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*** DANGER WILL ROBINSON ***
If people continually try tweaking the Priority of drivers to ABOVE Real-Time or OS/Services level, and then claim that it makes things better - go right ahead. Sure, it "might" make it seem to operate better - BUT THAT'S ONLY BECAUSE IT'S SERVICING YOUR KEYBOARD AT REAL-TIME RATES ABOVE THE OPERATING SYSTEM ITSELF! ARRGH!
Have fun, enjoy playing with task/thread priorities, and don't complain when your device locks up because your keyboard driver is above the RAM driver, and locks up your device waiting on RAM access.
PLEASE ... read the MSDN articles on Priority settings before posting silly suggestions like setting the Priority to 1. Not even the OS is running at priority 1.
Click to expand...
Click to collapse
maybe we could do a compromise, i little higher than the OS priority
the keyboard problem is really annoying
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
*sigh* ... why do people still keep punching in random numbers into the registry without checking what the values could or should be? *sigh*
Black6spdZ said:
haven't had any lockups yet.. and anything to make the damn keyboard usable in wm5 is good in my opinion
Click to expand...
Click to collapse
gh0st said:
maybe we could do a compromise, i little higher than the OS priority
Click to expand...
Click to collapse
Ok ... before this gets out of hand, and other people start doing "silly" and "stupid" things with Priority256 ... especially without understanding what you're changing, READ THIS! Otherwise you WILL cause untold problems for your device.
http://msdn.microsoft.com/library/d...html/wce50conRealTimePrioritySystemLevels.asp
To give you the comparison for Windows XP ... just open Task Manager, select an application which is using 100% CPU, running at Normal Priority, and switch it to Real-Time. Then enjoy how "responsive" the one application is (unless it's accessing the video display and/or disk - i.e. try doing it to an explorer window file copy! ;-)). You'll enjoy a "locked" machine, and admire how you're unable to do anything else - even open the start menu! You may have to hard-reset your machine depending on the application you choose to make Real-Time.
THANKFULLY ... the Keyboard Driver (QwertyKey) has a FORCED time-delay in it (debounce delay) which ensures it can not take 100% CPU time, and through this ... and ONLY through this fact, it hasn't killed your device. Had you done this to ANY other device driver, I'm sure your device would need a hard-reset, and you could start re-installing everything again.
By raising the priority above everything ... ALL you are doing is making the QwertyKey device driver get serviced AHEAD of any other pending interrupt. While this MAY make a slight difference, it will only do so at the expense of EVERYTHING else in the OS. (Like WiFi, Network, USB, ActiveSync, Memory Management, Compaction, etc ...)
gh0st said:
the keyboard problem is really annoying
Click to expand...
Click to collapse
Yes, I have had the same issue, but there is a LIMIT to which you can go with the driver Priority in order to "fix" what is fundamentally a hardware and driver problem.
gh0st said:
what would be a decent value for this, just to raise the priority to a decent level to get a good response from the keyboard?
Click to expand...
Click to collapse
In my testing, and throughout the TuMa ROMs I've used 0x81 - or a priority of 129. This was carefully chosen to be below the Wave device (which was or should be set at 0x80 or 128 for best performance on the BA - again due to driver issues), so that sounds/rings happen at a higher priority than the keyboard. Yes, this is eventhough BOTH Priority256 values for these drivers were tweaked above the default recommendations from MSDN.
If you're finding that the keyboard is causing you grief, you could try inverting these two devices, and setting the keyboard HIGHER than the sound driver - i.e. to 0x7F or 127, and see if the system sound servicing is the cause of the keyboard stuttering delay. However, you may introduce stuttering into the sound output at this point ... i.e. even when you're NOT using the keyboard (which is most of the time).
At the ABSOLUTE HIGHEST level I would even consider, would be just below that of the touch-screen (0x6D). At this level (or above) would cause handwriting recognition issues, as the touch-screen would not be serviced at the correct rate to track the line drawings.
Never even consider going above the Power Manager Resume Priority Level ... if the driver supports power management, and is taking too much CPU, then the power management thread will never be able to "shut it down", and/or wake it up ... ever. Result = lockup.
So ... in summary:
QwertyKey: 0x81 ... or 0x7F to invert priorities
Wave Device: 0x80
I'd still like to test all this with the latest AKU3.x ROMs and see if the Priority settings are still valid, but for the moment, I'll assume that they are.
Good luck to anyone using priorities outside "sane" values ... you will create "priority inversion" conditions, where a driver is waiting on another driver to run, but it never will, since the priorities are reversed. You have been warned ... but enjoy playing with it anyways. Device recovery is only a hard-reset away.
Thanks for clearing this up Tuatara, good post!
oops! i'm reverting the priority values....
Thanks for the post, @Tuatara. it was very enlightening.
my nexus one is charging on a regular basis around 106-7 F. I know there is another thread about this issue but the question was not resolved. So does anyone have experience with this issue. Is it a defect or dangerous? I have OSmonitor installed, this si where I am reading my temps. I also notice the CPU usage is pegged around 98-99%..is this normal?
I heard using setCPU with a charging profile can solve this problem if you have root?
No, it is not normal for the cpu to be maxed out while charging. Are you using the car dock or a wall charger?
nexous one
mine does the same thing all the time its not going to damage your phone at all
my phone has got about 120 F on car doc
my phone is perfect just set your set cpu for fail safe and your all good
You probably could use SetCPU to solve this problem, but the fact that your CPU usage is so high in the first place means there is something going wrong - my guess would be a rogue app.
Try downloading a task killer from the Market. Kill each app running one at a time then check your CPU usage. You'll soon find the culprit.
sn95chico said:
my phone has got about 120 F on car doc
Click to expand...
Click to collapse
Yeah I'm starting to see the problem with the phone having a metal casing. Not good when it's summer and you have to place it under direct sunlight for extended amounts of time, while using navigation AND charging
That thing can get burning hot alright.
Are you using froyo 2.2?
I have had the same problem; I also have random periods of high cpu use when not charging as well. This issue is not caused by problem apps either. I must reboot to fix the issue, sometimes I must reboot several times until the cpu load is back to normal.
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
I will also try to reapply the 2.2 update.
Marine6680 said:
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
Click to expand...
Click to collapse
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
frandavid100 said:
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
Click to expand...
Click to collapse
I bet your heat issues are related to cpu loads or staying at high frequencies like mine. Sometimes the phone does not feel like it is really running as hard as the system monitors say, though it may still get hot.
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
I am re-flashing the leaked 2.2 update to make sure there was no issue with the original install. I am also using the copy my GF downloaded when I sent her the instructions on the off chance that my download was corrupted in some small way; unlikely but hey. I do think that the original flash may have gone wrong, as mine hung and never rebooted after the flash was complete; I had to manually reboot. Lets hope this fixes it.
This issue may be more widespread than we realize, as many people do not actively monitor their cpu or notice/worry about the heat after charging. I do believe that these leaked ROMs send debug data to google, I remember reading something along those lines; these are internal test ROMs after all. Maybe this is a reason that 2.2 is not out yet, this and other bugs found during real world use.
Marine6680 said:
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
Click to expand...
Click to collapse
What I did was follow this guide up to the point where you have a stock eclair rom, then not upgrade to Froyo. Keep using that for some time, see whether the phone gets hot or not, THEN (if you want) move back to Froyo.
I am using the wall charger hat came with the nexus one. I am also running Froyo 2.2... can I set a CPU fail safe without my phone being rooted? Also what is a quick to check if my phone is rooted? I just bought this Nexus One from someone. I know on my G1 it was rooted bc I had Superuser permissions.
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
The fastest way I can think would be installing Lamppu, then trying to use it to light up the camera flash. If it works your phone is flashed, if it doesn't it's not.
As for your other questions... sorry, i don't know. I hope someone else can help you.
foethalove said:
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
Click to expand...
Click to collapse
Thats a system process so you can not kill it.
Going to test my GFs nexus and see if she has these issues as well.
I restored my N1 to the factory image, the updated back through each update to 2.2; so far so good. My GF's N1 has been running fine since I really started watching it, so I figured it would hurt to try to restore and redo the update.
No 100% cpu load during charging any more!
i am using the Motorola charger and my phone is not getting hot at all. with the charger that comes in the box for the N1 it seems to heat up.
Still had the CPU load get stuck at 100% today; though charging is not forcing 100% loads any more.
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
frandavid100 said:
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
Click to expand...
Click to collapse
System monitor apps, some will even put a little icon in the notification tray that shows current cpu load.
I have had my phone for about 2 weeks now, and this has been an issue since about day 1. I will set my phone aside while doing other things. When I want to use it I pick it up and press the power button to activate the screen. It seems that about 20% of the time the phone is non-responsive. I can't even receive calls/texts/email while it is in this state. I end up pressing the power button for 10 seconds or pulling the battery to get it to reboot. Everything seems to work fine.
I have heard that this could be a result of a reception issue, and that an update would be released in September to solve this issue. Is this information correct? Has the update already been released? I believe I am running the most current version, 2.1 update 1
Is there a software fix? Do I have a defective unit that needs to be sent in for repair? Is there a setting I need to look at? Any assistance would be appreciated.
you are describing the typical scenario of too many background services and apps running taking up too much resources thus making the phone non reponsive
install Auto Run Killer http://forum.xda-developers.com/showpost.php?p=8123924&postcount=40
then tick all the apps to disable reboot your phone
then you can choose which apps you really want to let lose for it to run in the background
It's also entirely possible it's faulty though
I don't think it is a matter of apps running because there are no active apps running when I am not using my phone.
I guess I am looking for an answer that tells me that this is an known issue with this model and I wiould be better off with a different product, or if I will be safe to get it replaced/repaired.
Ideally I would love to hear it is only a matter of a software patch or something similar.
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Well that was a pretty useless post. The only idea my mind is set on is to get my hands on a dependabel phone, preferably the one I have. You suggested too many apps running, fine, but unless they run automatically on reboot and/or the 'active applications' window that runs by default is inacurate, there aren't too many resources being used and nothing running.
you'll be surprised what runs under the hood
you can run this and find out
http://forum.xda-developers.com/showpost.php?p=8156087&postcount=58
Android System Info
another good thing to disable is the Media Scan
AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Don't be so quick to assume your suggestion was correct either, AllGamer:
http://forum.xda-developers.com/showthread.php?t=775017
Thus far nothing in that thread has suggested taxing the system too far. In fact, hardly installing anything at all from a fresh factory reset still has this problem and no one yet has really worked out why aside Samsung saying the hardware is damaged. I was on the phone to them today, same thing said.
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
AllGamer said:
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
Click to expand...
Click to collapse
I see no truth in the signal claim I've said why in the other thread. But this is the point, it is an issue a few of us are having from all over the place but as of yet there is absolutely no distinguishable pattern. As I say, a completely fresh phone with official firmware and no installs also has the problems. It's a very frustrating situation because no one can conclusively point to software or hardware yet. Samsung keep saying the same thing, send it in, send it in..
it's true the only way to diagnose those will require to be hands on, and run tests to pin point exactly what is causing that.
Eclair doesn't have the option to auto upgrade, so that's definitely not it
Lag is likely, but what, or which stock apps can cause so much lag?
signal even when the phone is having a hard time switching and scanning for a new signal it shouln't keep the phone unresponsive for such a long period of time unless it's lagging
my Old Treo did that, anytime it lost signal and regained signal there was a minor pause, or a looooooong pause if the phone was lagging
if this is the same case with the SGS we just need to figure out which App is running in the background that is dragging the entire system down.
it could be the internal SD which might have become defective, thus locking up the phone, similar to those people that can't get past the boot screen
i can't think of any other plausible causes at the moment.
Well, I can tell you: having experienced the problem a number of times, it is almost certainly not the lag scenario you have described - this is a proper lock-up. My guess (since it does appear to have some correlation to cell switching, or other signal-related issue) is a bug in the baseband drivers, or something similar, resulting in a panic. I might see if there's any way to get a dump out of this thing to prove it, but at the moment it's just a guess, so I'm not going to tell you that's the definitely the reason, or that you're stupid if you don't agree, even though I'm more qualified to do so, since I've actually experienced the problem.
AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Android is designed to not need auto task killers. It is purely a myth that they are needed whatsoever. This is linux we're talking about here, not windows.... It's possible he has a single app installed causing the issue, but the ideal fix would be to figure it out one app at a time and get rid of the faulty app.
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
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?