Related
Hello there,
I've tried Googling and searching these threads, and I can't seem to find anyone else with the same problems as me, so if anyone can help me I'd be really grateful!
Basically, I've had a rooted G1 for about 6 months now, started off using JesusFreke, went on to CM and now I'm running the latest ROM with an 8 gig class 6 SD card. Anyway, everything runs smoothly except for a few niggly things. As far as I can remember I've always had most of these problems since rooting, and now they're worse than ever and starting to grate. I don't think it's my particular handset, as this is the second G1 I've had - although as I said, I haven't read of these problems with other people, so I don't really know. The problems in question are:
1. Email isn't very 'pushy' anymore - when I first got my G1, and for a while after first rooting, I was amazed at the push Gmail...I loved it, and it often worked faster than my computer email client could retrieve emails with its 5-minute interval. However, now my G1 seemingly only downloads emails when it can be bothered, and more often than not I'll do a manual refresh to find about 6 emails waiting for me. It's somewhat annoying really.
2. This is another major thing: Locale just won't recognise where it is anymore. I'll go into Locale for a few seconds, it'll snap on to 'home' or 'work', I'll come out and after about five minutes, it'll jump straight onto the default settings again. I'll do this again, and it happens again, etc. My phone knows where it is, as the maps work perfectly, and I'll even tried leaving GPS on all day, but to no avail. This is a major annoying niggle, and it seems to get better/worse with different updates. Has anyone experienced this? At the moment, Locale is virtually unusable.
3. Since I'm asking for help, the other little niggle is that to add shortcuts to my desktop takes an age...I'll do the longpress, click 'shortcut'...and then wait. And wait. As far as I can remember my phone's always done this (even the old one), but if anyone knows what I'm doing wrong it'd be really good.
In fact, if anyone can help me with any of the problems I've described I'd be really happy...the email and Locale thing are starting to become a big nuisance, and I'm starting to think about changing my handset over it, despite my love of Android, the G1 and the excellent CM updates that Cyanogen tirelessly sends out.
Thanks so much in advance,
Mark
I've never had any of those issues the gmail issue is the only one that woulg get me... what rom did you go with this time around?
Hi, I've just got the standard CyanognMod ROM with the latest 4.2.9.1
I have the same Gmail problem.
No idea how to fix it.
I'm going to say it's probably two things together:
1. Low memory. Having had your G1 for a while, you've installed lots of apps. Each app uses RAM. Low RAM makes everything sluggish and buggy. Uninstall anything you don't use regularly. Doing a full wipe and reflash of the htc update image, and then the latest cyanogenmod, will give you a blazing fast phone again, with everything working beautifully (but you'll have lost ALL your installed apps, saved sms, settings, etc.).
2. Task-killing app. You probably use Taskiller, Close Everything, or something like that. It is killing Gmail so it doesn't refresh, killing locale's location service so it doesn't know where it is, etc. Make sure you exclude ANYTHING that runs in the background constantly to work. Basically, anything that does something automatically, or generates a notification, or anything. Email, gmail, messaging, etc.
Not cool
You can't say niggly, only we can say niggly.
gmail push
there is a way to 'Set download frequency' by default.
oneofone1 said:
You can't say niggly, only we can say niggly.
Click to expand...
Click to collapse
'Niggly' is a word of Scandinavian origin which in this context essentially means 'irritating'. It is in no way related to similarly spelt offensive words, which is what I think you're getting at.
Anyway, many thanks to all those who posted help, I deleted a load of programs and it helped greatly. I had no idea that having too many apps, even in an apps2sd setup, would impact performance that much.
Still can't get Locale to work properly though. I'll delete a few more apps and see if that helps.
markdjj said:
'Niggly' is a word of Scandinavian origin which in this context essentially means 'irritating'. It is in no way related to similarly spelt offensive words, which is what I think you're getting at.
Anyway, many thanks to all those who posted help, I deleted a load of programs and it helped greatly. I had no idea that having too many apps, even in an apps2sd setup, would impact performance that much.
Still can't get Locale to work properly though. I'll delete a few more apps and see if that helps.
Click to expand...
Click to collapse
I think he is quoting "Something Something Something Darkside" It is the new Family Guy movie.
spigatelli said:
I think he is quoting "Something Something Something Darkside" It is the new Family Guy movie.
Click to expand...
Click to collapse
+10 pts for being spot on.
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
Just absolutely the worst rom I've ever had on my phone, and I've ran Pulse roms and half built sense UI roms.
I wiped my phone and cleared the partitions but it was always the slowest thing in the world.
The wifi never stayed connected
Gps never ever ever worked
after an amount of time using the rom
it would suddenly not accept incoming text messages
Tons of bogus **** like that.
Anyone else have this problem? I'm currently on speed team Eclair and it's working marvelous, just like the htc clay / fast test 1.6 roms with the 10MB hack.
(mind you these were his new releases, not so much his every day nightlies, but his stable and unstable ones)
Icebergxx said:
Just absolutely the worst rom I've ever had on my phone, and I've ran Pulse roms and half built sense UI roms.
I wiped my phone and cleared the partitions but it was always the slowest thing in the world.
The wifi never stayed connected
Gps never ever ever worked
after an amount of time using the rom
it would suddenly not accept incoming text messages
Tons of bogus **** like that.
Anyone else have this problem? I'm currently on speed team Eclair and it's working marvelous, just like the htc clay / fast test 1.6 roms with the 10MB hack.
(mind you these were his new releases, not so much his every day nightlies, but his stable and unstable ones)
Click to expand...
Click to collapse
Its the kitchen sink problem.... which has two forms;
1) The more bloated big crap you throw down the kitchen sink, the more plugged up it becomes.
2) If you throw in even the kitchen sink, then you've gone WAY too far (related to the phrase "everything but the kitchen sink", which is to say you've packed too much useless crap).
In other words, it is a big fat pig. Just picture yourself a 350 pound fat woman waddling down the street. There's CM ROM for you. Moves just as fast.
Funny you should say that SpeedTeam Eclair is actually themed/botched/molested CM5 (which ran like crap for me ).
I'd suggest trying a straight-up AOSP Froyo ROM which does not use CM kernel.
I also am having many issues with Cyan's roms these days. I'm not even running Froyo, I'm running CM5. Random stuff will happen a while after wiping/flashing. Last time all my Google apps would just force close no matter what I did. This time the Market stopped working. Logs say it ran out of memory and was killed. I killed all non-essential services (which only give me 20-25mb of memory) and cleared app data for market, cleared caches in recovery. I'm just getting fed up with it.
I want a new phone so I can get some stable-ness back in my life, but Tmobile isn't releasing many cool phones like the others (Tmobile's Galaxy S design was disappointing).
Can anyone suggest another rom to run on my EOL G1 until something good comes out? =\
Icebergxx said:
The wifi never stayed connected
Gps never ever ever worked
after an amount of time using the rom
it would suddenly not accept incoming text messages
Tons of bogus **** like that.
Anyone else have this problem?
Click to expand...
Click to collapse
Yep. I'm running CM6 and it is super slow and unresponsive, constantly crashes, no apps2sd so it runs out of space immediately and won't accept incoming text messages, apps won't install or update, background notifications don't work in any app? etc. Swap makes the phone run so much better, but Cyanogen says "Don't use swap" with no explanation. I don't understand why this 3D gallery is installed by default when it can barely crawl along on this processor. Did they even test it on a Dream?
Man I have had nothing but problems. Now the browser won't connect to the web, but Gmail still updates. I can't install anything in the Market, it just says "Download paused". etc etc etc. I tried uninstalling so I could reinstall, but that doesn't work. So now I don't have Titanium Backup because I uninstalled it and can't reinstall it. >:[
I've had a 16gb Samsung Galaxy S on Three in the UK since they launched last year, and it's the only Android phone I've used.
It's pretty laggy, but since I'd read a lot about Galaxy lag online, I assumed this was to be expected.
However, I had to help a colleague with a problem on their HTC Wildfire today (a lower spec phone, as far as I know), and was amazed how much more responsive than my Galaxy S.
It didn't seem to show any of the laggy, hanging-ey behaviour I experience. I have more apps installed than the Wildfire, but I'm quite careful not to install anything that's going to run at startup or cause problems (mostlly just games, no widgets, etc.)
As an example, if I turn the phone on clean, wait for everything to be loaded and ready (media scanning to finish, etc.) then poke the "Market" button, it takes 28 seconds for it to be loaded and responsive. Close that, poke the Facebook button, over 20 seconds until I'm shown the news feed. Sometimes when the phone rings on my desk, I literally won't be able to get it to respond enough to answer the call before the caller hangs up. If I try to switch from program to program, I end up getting quite a lot of frustrating 20-30s hangs and pauses. This is all on a decent wifi connection, so the problem isn't data related.
The question is - how laggy should a Galaxy S be? Would it work better if I added an SD card (with the 16gb phone memory, I didn't see the need)? Is it worth installing a lagfix under Froyo (I tried one back on 2.1, but didn't notice a huge amount of difference)?
Any help would be greatly appreciated!
I think its sometimes very busy rebuilding it's wifi connection. Or some other process.
Am not sure.
Sent from my GT-I9000 using XDA App
I didn't see any speed difference with SD card IN/OUT so i don't think you will have faster phone by inserting it (SD card).
Why don't you try a reset and see if that works? Also are you on eclair or froyo because that would make a world of difference if you upgraded
I just got my sgs from bell Canada last Tuesday. It has all stock with launcherpro and a few Widgets. So far (knock wood) its been a big step up over my HTC dream. I experience maybe 10 seconds of startup lag and then for the rest of the day its awesome. My firmware version is the newest one bell offers (jl2 Frito). What android version are you running?
Sent from my GT-I9000M using XDA App
monkeyhat said:
Any help would be greatly appreciated!
Click to expand...
Click to collapse
That's exactly my experience. The only way to solve it is with a good lagfix and/or flashing JPY firmware
This will get almost instant loading of apps and only minor lags when switching apps. It's still slow when scrolling icons and such... my previous phone, iphoe 3g, is still faster than this crap-phone
Cheers,
Soulbrighter
My Galaxy S was laggy as hell brand new out of the box. Sometimes it would hang for what seemed like 10 seconds. I didn't like the Samsung launcher anyway, so I did my homework, made sure I could get into 3-button download mode, and then rooted, wiped and flashed a custom Froyo ROM. I've tried a few ROMs since then and have landed on Insanity with EXT4 lagfix.
Now my Galaxy S is _awesome_ ... I don't even bother overclocking it, everything is smooth.
try a task killer and set it up to auto kill when screens goes off done a few tests with it ,one with no killer and one with and the one with was faster and had no lag fix running too go to the market and get quadrant standard try it for yourself and see
What's the current firmware you're using ? I suggest flashing to JPY and testing it out.
Update to JPY!
If not possible, install a lagfix on your current ROM/kernel.
The amount of lag you describe is terrible, I have never seen it that bad...
I don't think the lag should be that bad, I did experience some occassional lag back on eclair, but never exceeded 5-10 seconds. Usually after loading whatever that app was once, it'd be okay on the next open too.
Since I've upgraded to JPY i see 1-2 second lag extremely rarely.
Maybe you can get a task manager and see if anything is hogging memory?
Thanks for all the responses. The firmware is FROYO.XXJPO, so I'll definitely try flashing to JPY and will report back! Thanks so much for the tip!
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!