I´m having quite a frustrating problem. Tried to search the net for hours, only finding a handful of people with the same issue but no solution. So, I wondered if anyone can help me out here? The problem is that my clock is not updating while screen is off. Naturally, this affects all alarms and notifications as well.
20:15 -> I adjust alarm to 20:30 and put the screen off. I press power right after the screen has gone off, and see the lockscreen.
Lockscreen informs it´s 20:15 and the alarm is set at 20:30.
20:30 -> Nothing happens.
20:45 -> I press power. Clock says 20:15 for a second. After one second, it shows 20:45, and the alarm starts ringing.
So the problem is quite easy to identify- the clock doesn´t get updated when screen is off. The moment I switch it on -seeing the lockscreen- it gets updated and acts accordingly if any alarms or notifications were to ring at the period it was not updating. However, it´s much less easy to find out what´s behind it. Could anyone spare me a hint here?
I´m running a rooted P7300 with CM10, 30/10 build. Using Tasker to underclock while the screen is off in order to preserve battery life. I thought that caused the problem, but while leaving the CPU untouched....
01:00 -> Switching tablet off, putting alarm at 9:00
09:10 -> Wife wakes me up instead of the alarm. I press power.
Clock says 8:48 for a second. After that second, it gets updated, shows 9:10, and the alarm starts ringing.
I´m getting a little clueless here, so any help would be appreciated.
Running rooted P7300 with CM10 (30/10 build).
Cheers, Henu.
EDIT: Ok, I´ve come to the conclusion that this freezing happens when entering Deep Sleep. If that could give anyone any clues?
Works on CM10 version 11-11
Hi,
I can confirm that it works correctly in CM10 from 11-11.
I only have one weird problem left: the device drains more power when turned of than in standby.
I have been running the 11_11 build since it was released and had not had clock issues until today. I am not overly technical and have no clue why it is happening again. But for as smooth as this rom is I will live with it.
When mine gets confused on time it will not reset itself once i wake the tablet up, it stays messed up until I manually fix it.
Sent from my GT-P7310 using Tapatalk 2
Launcher ?
Do you use the stock launcer? Mine did strange things when using the apex launcher. No problems with stock launcher from cm10.
I am using the stock launcher but have installed nova and thinking about giving it a try
Sent from my GT-P7310 using Tapatalk 2
You could try the clock sync app from the play store. It worked on my phone when it had clock sync issues with a rom. Unfortunately, i'm new to xda, so I can't post the link, but just go to the play store and search for clock sync. It's by Sergey Barinov.
Thanks, but unfortunately none of this methods helped- I´m still having the same issue even with the 11/11- build, running Clock Sync as well. Anyone could shed any light here? I wish I wouldn´t have to go back to some (yuck) stock version.
I don't know if this will help but I just resolved this issue for myself. I did a factory reset. And also wiped all caches and system before flash. Then immediately after flash before rebooting system I wiped everything again except system. And then I started up and there was no issue with the clock. I'm running cm 10. I hope this helps.
Sent from my HTC One X using xda app-developers app
Sounds like voodoo but I´m all in for trying even that. I will post the results tomorrow.
To confirm:
1) Basic superwipe procedure (factory reset/ system, cache, dalvik)
2) flash OS -> don´t boot yet up to OS like normally
3) wipe cache & dalvik
4) THEN reboot -> to OS?
Voodoo, baby.
It worked. Seriously, what the hell. My wild guess is that some file(s) might be corrupted in the actual package- and when the system notices they are missing at the first boot, it will replace them with working ones. Then again, I´m no Android/ Linux expert.
With a clean install, I ran alarm after 8 hours. Worked. Then I added Apex Launcher, waited 2 hours. Alarm went on. Installed everything again with Titanium Backup, put alarm after an hour. Still worked. So I can confirm that it´s not app- dependant but OS- dependant. However, it worked, so thanks a goddamn zillion!!!
Congratulations. Just happy to help.
Sent from my HTC One X using xda app-developers app
I´m going to snap this piece of junk into half soon.
The problems came back, no reason why. I´m now trying one more thing, which is completely disabling Tasker, as it´s basically the only thing running while the screen is off. If that doesn´t help, i´m clueless.
EDIT: What a surprise, it didn´t help. So, it´s either non- functioning CM10 or stock ICS. I could had settled with CM9 easily, but that gave me the battery bug after two weeks. Seriously, this whole me- buying- a- tablet- and- getting- it- to- work has been a living joke. I just would love to have a stripped down OS with a Kernel supporting "all sorts of stuff" like processor speed, running app restriction, tweakable backlight etc.
Ok, so I wiped cache and dalvik and it worked for a couple of hours. Then last night the clock froze again. And this was quite interesting..
Alarm set at 10:30
I wake up 11:15 (hey, it was New Year´s Eve )
I press power and the clock says 11:15 and next alarm is set "tuesday 10:30".
Two seconds later the alarm hops into "wednesday 10:30".
Two hours later I press power, and the clock is 11:15 for a second and jumps to real time. So it´s definitely broken again.
I was just wondering- maybe I could try replacing the clock with another kernel´s version, would that be possible? Any help would be much appreciated.
EDIT: I also tried -once again- without automatic time& date (as my connectivity is set to cut off while the screen is off) and it still didn´t alarm me until I manually pressed the screen on.
EDIT2: Ran A1 kernel, no effect, still bugged.
EDIT3: Ran Tracid´s official ICS. Worked for a day, then bugged. Same thing with A1 kernel. I also had some serious issues with MTP connection and bootloader, so I restored stock and brought it back to the store where I got it for warranty repair. They think it´s a faulty MoBo.
I´m shamelessly bumping this. I ran the stock firmware with Odin and took it to the repair, as I wrote earlier.
Got the tab from warranty repair, seems that the only thing they had performed was "software update" . Very useful for someone who is constantly switching ROMs etc... like I hadn´t tried that before.
After returning to stock and all, I installed CM10 again. And "surprisingly", the problems started again. With or without apps, launchers, cachewipes, younameit. I´m now giving this a test with the stock ROM for a couple of days. I actually hope it doesn´t work, because that would be the only reasonable thing now. If it works with the stock ROM, I´m getting clueless. Does that mean I have some sort of issue which happens only in flashed ROMs instead of the stock one? That would be just....awkward.
Related
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?
Hi there everybody
I've installed [ROM][ICS 4.0.3][Unoffical Port] AOKP Build23 by vibranturk ROM.
Problems I found
1. android.media.process crashing always /almost every minute/
2. cant get in to market /meaning couldn't install any app yet/
3. cant get in to gallery
4. cant get in to music player
4. cant take secreenshot by default setting
5. sound is enabled but doesn't work. /not even play ringtones /
6. screen brightness not enough for day light
7. cant take photo by camera /android.media.process crashing/
Actually ROM is amazing. But without market its feels nothing.
Has anybody have same problem and about how to solve etc?
PS: I flashed 2 times.
You should start from fresh cuz not one problem that you stated has occured to me.....only bug is that when i reboot the batt % is off..
market works perfectly
...everything does atually
idk but just start fresh and wipe wipe wipe between flashes
i wipe before and after the flash
even flash twice just to make sure
***Dont mind the sig pic... im running this rom at the moment and its working flawlessly
jayRokk said:
You should start from fresh cuz not one problem that you stated has occured to me.....only bug is that when i reboot the batt % is off..
market works perfectly
...everything does atually
idk but just start fresh and wipe wipe wipe between flashes
i wipe before and after the flash
even flash twice just to make sure
***Dont mind the sig pic... im running this rom at the moment and its working flawlessly
Click to expand...
Click to collapse
OK. I'll try tomorrow. Thanks for quick reply.
I've been fighting with this 2 days. Today is day off for me.
Well. Today I installed again. This time it works fine. Everything went normal. Only one unusual thing is my cappy feels slow. asphalt 6 freezing sometimes. is there any way speed up my ICS?
ganaa1221 said:
Well. Today I installed again. This time it works fine. Everything went normal. Only one unusual thing is my cappy feels slow. asphalt 6 freezing sometimes. is there any way speed up my ICS?
Click to expand...
Click to collapse
Use Glitch v14, the included has some slight lag and glitch fixed it up. You can also LiveOC which allows for overclocking of the CPU and GPU.
signal
Has anyone found the solution for the gray\blue signal switching? So far as I can tell it is caused by the wifi; whenever I go from mobile network to wifi data, the signal bars go gray. The only work-around has been to switch airplane mode on and off. Would switching to the newly released glitch kernel do the trick?
EDIT: I have found out the Google services problem (gray vs. blue signal) is only happening when I join a network which requires a redirect authentication OR if the power saver is enabled.
Just got this phone and flashed it with - AOKP Build23 by vibranturk ROM
I have been reading for awhile now before I received the phone. Thanks vibranturk for all the development here! Excellent roms!
1) When I start the camera app from app on homescreen and from unlock - the phone goes into a black screen
The camera app worked fine again after a reset (just turning off and back on) but after awhile it does the same thing - black screen.
During the black screen, I can press the home button to return back to homescreen
** Resetted again, and all seems well at the moment and still fine after 1 hour!
2) I am not sure if this is the rom or just my screen. Did not notice it at first when i flashed the rom. Turning on the screen to unlock the phone, ie when the light starts, i get this bright green full screen flash for like a second. It does not happen everytime and no pattern of when it happens either.
Anyone else having these problems?
Can someone please update the 'AOKP thread in Captivate Android Development' with my issues, just trying to help with the development.
For the signal blue/grey thing, Seems like it goes blue for me when i have data signal coming in, either wifi or data enabled - lights up both wifi signal (only if wifi is on) and signal bars blue.
I have power saver is enabled as well.
My only issues so far are: vibrate + sound doesn't work, touch screen is over sensitive on certain games, and sometimes using Swype in messaging doesn't input if app was already in foreground when replying.(can be fixed by minimizing and reopening the app) otherwise it's works great. fast/smooth and great battery life.
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
It might have been a bad flash. Try redownloading the rom and flash again. Also, make sure that you do not have too many apps installed. How much free space do you have on system?
The only apps that I had were the ones that came with the ROM itself, didn't download anything before or after flashing it.
may i know does this rom support audience cancelling noise?
thx
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
scrypt said:
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
Click to expand...
Click to collapse
ICS ones, but the Dev thread tells that & more.
I don't miss Nandroid when I'm backing up with Super Manager, Super Backup for data, apks, call logs and SMS.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
When my screen first appears after a reboot it does that, too, shows half the screen, then the other half, but only for a couple of seconds, I figured it's because it's still reading media, loading widgets, screen, etc. Doesn't last more than 2 seconds, fortunately.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
Were you still running the Glitch kernel that installs with the ROM?
It's odd that it went from working to not working. It sounds like something changed something which caused a conflict or corruption... it wouldn't have boot looped otherwise.
If not had any issues like this...
It was a fresh install of the ROM itself, was running for ~ 5 minutes. I didn't install anything via the Market or anything like that....
Un-invert Calendar?
I like Doc's V5 ROM a lot. Best I've used so far. However, I don't care for the inverted apps and am using the "Revert Inverted Apps to Stock" tweak mentioned here. It works just as expected except for the Calendar app - it remains inverted.
Can anyone else confirm so I'll know it's not just me?
Does anyone have a solution?
Thanks!
Bob
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Anyone have vibration issues when receiving texts?
battery life
Battery saving settings - LiveOC 126%, MaxCPU=800*1.26=1008MHz. Nexus KB3 Modem. No deep idle sleep, no screen state settings, no internal voltage settings, ARM voltages are OC/UV. Power saver in ROMSettings enabled.
Boraltis said:
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Click to expand...
Click to collapse
has any one experienced having a feedback loop in either your end or their end when using either the speaker phone or a headset?
Sent from my SGH-I897 using XDA
I am having an issue with the system time. It won't update automatically. Just gets stuck at a particular instance like 3:45 and won't update until I manually change the clock from 24 hours to 12 or vice versa. The happens after long sleep periods like two hours. After this the problem is persistent until I flash a new kernel.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
xThe Enforcer said:
Anyone have vibration issues when receiving texts?
Click to expand...
Click to collapse
Yes I am having this same problem no vibration with texts
no vibration with texts
Yeah. Same here. No separate vibration for SMS. But if you turn "Vibration only" system wide - it works for SMS.
Awkward.
scrypt said:
Yes I am having this same problem no vibration with texts
Click to expand...
Click to collapse
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Well anybody having an issue with time???please read my previous post^^ and tell me if it's sounds familiar , thanks
It happens when you switch a kernel as well? Try switching ROMs and see if it does it then go back to this, I haven't used this ROM since this incident ( OP ), using DK3 atm =p
b-eock said:
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Click to expand...
Click to collapse
I love you.
Sent from my SGH-I897 using xda premium
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues！
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...
Third Android phone and also 3rd older phone I've upgraded to 4.x. I basically went from stock, rooted, switched to new BL and fixed internal storage all using the O2X AIO tool, and finally flashed Slimkat (this http://forum.xda-developers.com/showthread.php?t=2551925).
It was great for about 30 minutes but then started to slow down badly so I froze a bunch of packages I don't use and have frozen on other devices without issue (using performance control tools). Speed went back up. But 30 minutes later it's back in the crapper. We're talking 30 seconds from power button to lock screen showing up. Stock camera takes a good 2 minutes to be ready to take a picture. Just now I was trying to set something in GPS Test and literally the statusbar clock was at 11:00 until at least 11:03 before I was like ok battery pull.
Anyone have any suggestions? Did I miss a step? I've been through all the related posts and everyone seems to love Slimkat. I'm coming from phones even older than this so I'm used to slow but come on...
Really appreciate any advice! Thanks!
Edit: I should mention I have installed FB Messenger with some modified permissions, Gmail, Now Browser, Root Browser, and Touchpal keyboard... That's all.
Hi. You should try to change to dalvik. ART is terrible for our phone!
Dalvik is default in the latest build
leekohlbradley said:
Dalvik is default in the latest build
Click to expand...
Click to collapse
I think that the memory is maybe running full, FB Messenger isn't always the best on memory usage/Battery usage and about the other apps I dont know, But There are apps which are resyncing, rerunning and which stay in background so it doesn't completely closes even if you do so.
Thanks for your reply! Actually afterward I switched OOM to aggressive (or something more aggressive, can't remember). Seems to be a lot better. I don't care about battery, I just want speeeeeeeed Oddly enough I still need to "double tap" the power button (!) to get it to wake. Weirdest thing.
If you're finding Slimkat at all slow then stop suffering and flash CM11 here http://forum.xda-developers.com/showthread.php?t=2769730
So much better! I used the 7/16 M1 version. Brilliant so far. GPS (my no.1 need) is also very fast.
But the date of you post ...
Sent from my LG-P990 using XDA Free mobile app
leekohlbradley said:
If you're finding Slimkat at all slow then stop suffering and flash CM11 here http://forum.xda-developers.com/showthread.php?t=2769730
So much better! I used the 7/16 M1 version. Brilliant so far. GPS (my no.1 need) is also very fast.
Click to expand...
Click to collapse
Sure ? Do u think that latest builds are fast ?
I haven't tried anything later than the June release by TonyP... There are other ppl putting out weeklies or something but honestly I'm looking for stable not bleeding edge
But the date of my post?
leekohlbradley said:
But the date of my post?
Click to expand...
Click to collapse
When I red first time, it was wrong (some day in 2007); now is right.
---------- Post added at 10:57 AM ---------- Previous post was at 10:50 AM ----------
leekohlbradley said:
Third Android phone and also 3rd older phone I've upgraded to 4.x. I basically went from stock, rooted, switched to new BL and fixed internal storage all using the O2X AIO tool, and finally flashed Slimkat (this http://forum.xda-developers.com/showthread.php?t=2551925).
It was great for about 30 minutes but then started to slow down badly so I froze a bunch of packages I don't use and have frozen on other devices without issue (using performance control tools). Speed went back up. But 30 minutes later it's back in the crapper. We're talking 30 seconds from power button to lock screen showing up. Stock camera takes a good 2 minutes to be ready to take a picture. Just now I was trying to set something in GPS Test and literally the statusbar clock was at 11:00 until at least 11:03 before I was like ok battery pull.
Anyone have any suggestions? Did I miss a step? I've been through all the related posts and everyone seems to love Slimkat. I'm coming from phones even older than this so I'm used to slow but come on...
Really appreciate any advice! Thanks!
Edit: I should mention I have installed FB Messenger with some modified permissions, Gmail, Now Browser, Root Browser, and Touchpal keyboard... That's all.
Click to expand...
Click to collapse
I had the same problem, so I had to uninstall it.:crying: