Related
Greetings,
When the phone is idle and I get a text message the sound stutters. Are more people experiencing this problem?
Regards,
Xionax
Do you have anything running in the background that may have a higher priority than sound playback?
Mine works fine but there's nothing run in the background.
Just a thought.
I've noticed mine does the same thing.
It starts, then pauses for a few split seconds and then finishes.
How long is your message tone? I seem to remember this is a windows mobile thing, something to do with waking up out of standby and having to bring all the drivers up. There's an MSDN post somewhere.
[EDIT] Found it here, the important part is:
"The issue is that it takes a "long" time to go to sleep and a similarly long time to wake back up. When a PocketPC goes to sleep, we have to notify every device driver so that they can each save any important information (their "state") and shut off the hardware they're controlling. Then, on wake up, we need to notify every driver again and have them turn all their hardware on. This process can take up to three seconds in each direction."
AND
"Imagine that your device receives a SMS message. The sleeping PocketPC will need to run the CPU for around six seconds to handle it. The Smartphone will do the same task in a few milliseconds. Waking up is much more efficient on a device that doesn't sleep. It turns on only the devices necessary, uses them for the minimum amount of time needed, and then immediately shuts them back off."
I could be wrong of course, but interesting non the less!
G
galvinize said:
How long is your message tone? I seem to remember this is a windows mobile thing, something to do with waking up out of standby and having to bring all the drivers up. There's an MSDN post somewhere.
[EDIT] Found it here, the important part is:
"The issue is that it takes a "long" time to go to sleep and a similarly long time to wake back up. When a PocketPC goes to sleep, we have to notify every device driver so that they can each save any important information (their "state") and shut off the hardware they're controlling. Then, on wake up, we need to notify every driver again and have them turn all their hardware on. This process can take up to three seconds in each direction."
AND
"Imagine that your device receives a SMS message. The sleeping PocketPC will need to run the CPU for around six seconds to handle it. The Smartphone will do the same task in a few milliseconds. Waking up is much more efficient on a device that doesn't sleep. It turns on only the devices necessary, uses them for the minimum amount of time needed, and then immediately shuts them back off."
I could be wrong of course, but interesting non the less!
G
Click to expand...
Click to collapse
Interesting but still "s*cks". I mean... thats not my problem that they have issues with the way drivers are handled. The phone should do its job and not stutter or anything. If so.. change it. (IMHO)
I was thinking about this last night, what type of file are you using (mp3, WAV) as a message tone and where is it stored?
galvinize said:
I was thinking about this last night, what type of file are you using (mp3, WAV) as a message tone and where is it stored?
Click to expand...
Click to collapse
I agree that its a windows mobile thing... i have got this stutter problem too.. FYI, i am using .wav file (245kb). and for the sms notification sound, i put the file under \windows folder
joseph.sapri said:
I agree that its a windows mobile thing... i have got this stutter problem too.. FYI, i am using .wav file (245kb). and for the sms notification sound, i put the file under \windows folder
Click to expand...
Click to collapse
After rom upgrade seems to run better
After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)
No issues here. Clean install.
I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.
FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.
I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.
gmail stopped working properly for me.
I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.
I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App
I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.
My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App
1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.
nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.
Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)
What is going on here? It either freezes when:
1) slide-to-unlocking
2) switching between programs
3) google sync icon shows up in notification bar
4) in apps
Need to pull battery all the time! What's going on?
I've had this ever since the FRF50! I'm so annoyed and want to go back to 2.1, but I do love the battery life I'm getting with FRF91.
Any help please?
Sorry, realized I posted this in the wrong forum. Can MODS transfer the thread to Q&A?
I'm getting freezes on the same situations you have posted. However not with the same frequency as you. Mine is 1-2 daily.
Sent from my Nexus One using XDA App
strange, my phone is stock and ive had none of these issues, i actually thought my battery life had worsened since 91. It seems like the green meter doesnt drain as quick but the actual percentage drains faster than ever for me, at least i think so
This should unusual and should not be happening. Wipe everything and reflash.
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
galaxys said:
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
Click to expand...
Click to collapse
Yepp, same here! Never had a single freeze/lock-up since I manually updated to FRF91 from EPF21.
Hardware Issue
Seem to me you either have a defective apps or widget, a defective SD or a hardware issue like defective video ram or something like that, you could try to use a benchmark app like quadrant this may help pinpoint the exact subsystem that cause crash (video, cpu, ram) and try running stock OS with almost nothing loaded ...
This is assuming you are running from a clean install, When you have issue it's always a good idea to clean install (full wipe etc...)
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Mine is stock and sometimes it freeze when I tried to unlock. I had to turn the screen off and on 1-2 times to make it work again
Following your advice and let me monitor for a day or so. If doesn't work I will wipe everything and reflash.
Thanks!
mingkee said:
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
wipe everything and flash both FRF91 and the latest gapps.
1. How many app you have and 2 are they on your SD? If you have alot of apps ittaking up your internal space causing you to freeze.
Sent from my Nexus One using XDA App
I actually installed spare parts the same day i installed stock frf91, so i am not sure who is the culprit. It didnt happen today, but froze yesterday and the day before.
turned off all the animations (transition/window) to get maximum speed out of my n1 using spare-parts maybe thats causing the craziness no?
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
still froze twice today....wiped + reflashed FRF91..now resetting up my phone .... hope this will stop the freezes...will report back
Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I think I found a solution.
Go to email account, settings
Auto check->off
DarkDvr said:
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
Click to expand...
Click to collapse
Thanks, It works
Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk
I'm not sure if my 2 month old Note has had the following problem since day 1 but it's been doing if for a long time now.
The problem is there with a stock standard rom and any of the other custom roms and kernels that I've tried. I'm currently using Rocketrom with Speedmod kernel. I've also used Checkrom and Abyssnote kernel.
If the Note had been asleep for about 15 minutes or more when I wake it up then try to do anything like opening an app, closing an app that's already open etc there's a 2 to 3 second lag the first time I try to do anything. Everything is then normal until the next time that the Note has been asleep then it's the same story again.
Can anyone give me a clue as to what is going on here? I'm starting to think that it's hardware related, but apart from this problem the Note functions perfectly normally.
Also, if I have a CPU monitor installed, like URsafe CPU Monitor, when the lag is happening the monitor shows that the CPU is working hard.
Help please!!!!!
Does this happen after a complete hard reset with no apps installed?
Does this happen on Stock ROM?
Are you using WiFi?
Sounds like WiFi is sleeping when the screen is off, and either it is trying to connect and/or some app is wildly trying to connect using it.
Try seePU++ can tell you what the most active app is, but IIRC you have to pay for that that feature. There may be others.
PoisonWolf said:
Does this happen after a complete hard reset with no apps installed?
Does this happen on Stock ROM?
Click to expand...
Click to collapse
Yes, it happens on stock rom with no apps installed. I'm not totally sure what you mean by a complete hard reset. Can you please tell me how I do that? I'm willing to try anything to get rid of this problem.
jeromepearce said:
Are you using WiFi?
Sounds like WiFi is sleeping when the screen is off, and either it is trying to connect and/or some app is wildly trying to connect using it.
Try seePU++ can tell you what the most active app is, but IIRC you have to pay for that that feature. There may be others.
Click to expand...
Click to collapse
The problem still happens with WiFi disabled. On top of that it doesn't matter how long I leave it after I wake the phone up till I try to do something like launching an app. The problem is still there the first time I do anything with the phone.
I have rocket rom and sometimes when I turn on the screen the screen wont work. The physical buttons work but the screen is wont respond to touch.
Turning on and off the screen fixes this.
Very annoying.
Makes me appreciate Apple more.
CorruptedSanity said:
...snip...
Makes me appreciate Apple more.
Click to expand...
Click to collapse
Ban him!
appro77 said:
Yes, it happens on stock rom with no apps installed. I'm not totally sure what you mean by a complete hard reset. Can you please tell me how I do that? I'm willing to try anything to get rid of this problem.
Click to expand...
Click to collapse
Do a clean stock ROM with no root or anything.
Do a factory reset and erase your USB storage as well (i.e., tick the option when you're factory resetting).
Remove your microSD card.
Now, does the problem still occur? If it does, get your phone exchanged/repaired. It sounds like a hardware problem.
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
Really? I haven't noticed this at all on my phone. Any specific apps I can test this on?
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
Same here, totally normal.
Sent from my GT-N7000 using Tapatalk
1902 said:
Same here, totally normal.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Just not getting that myself. I am not terribly patient, and generally the most I have to wait is a second for an app to respond after waking the phone, and that is not often.
Stock unrooted HK version, never seen anything like that delay, mine works instantly on waking
Sent from my GT-N7000 using Tapatalk
Same delay here. Stock ROM, and rooted.
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
I dare say this is not normal, the only time there is a delay in opening the dialer/contacts application is when you initially boot the device and have both of those running for the first time subsequent runs have no delay what so ever on my end ( when i still had the note )
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
If this is normal it's incredibly bad that Samsung would design something like this. The wake up lag is bad enough let alone this. Can't see how it can be normal though. My SGS2 didn't have it and some other users aren't seeing it. I think I'll hang out for ICS and see if it goes away before I take any further action.
Strange issue, seems it occurs for some but not all...
Once again, I unlocked the screen after 2 hours of no use, when pressing contacts, there was a 2 second delay and when attempting to call someone there was a good 2-3 decond delay...
jeromepearce said:
Just not getting that myself. I am not terribly patient, and generally the most I have to wait is a second for an app to respond after waking the phone, and that is not often.
Click to expand...
Click to collapse
Luky you :banghead:
Sent from my GT-N7000 using Tapatalk
Despite being my first Android device I have come to accept that this is normal for this OS.
Unfortunately I have become a big whiner on this forum because of this same issue.
The day before yesterday there was an update on the kies ,LA4,after updating it felt a bit faster overall but the wake up and the incredibly annoying Contacts lag is still there.
I myself am not any particular OS follower or a fanboy of any certain brand for that matter.
So I'm stuck with Android for the time being, since I don't like both iTunes and izunes dependency, besides no big screens there.
However I suspect that this is an Android thing, as far as I know Android is based on Java and Java is known to be laggy,so until a very powerful CPU is available for mobiles, for me its either live with it or Leave it !! and since there is no alternative for now will wait and see how good ICS does and decide accordingly.
I'm on stock ROM and unrooted.
The Note seems to do this once or twice but when a program/app has been opened once it usually reopens them instantly.
This morning when turning on my Note for the first time, there was a few second delay when attempting to call someone, another delay when opening contacts and another slight delay when viewing sms messages.
However, the second time I attempy to open something it's usually immediately.
There should not be ANY delay when opening programs/apps and Ice Cream Sandwich should fix this wake up issue which some users such as myself am experiencing.
It's a shame, really since I'm getting no other lag/delay. The phone is super fast in every possible way, only sometimes it's a little slow at waking up!!