Database Users

eh17 reboots - narrowing in on the issue

from what i've noticed
it happens when closing the keyboard under certain circumstances
possibly only during sms messaging
i was able to duplicate a reboot sending/receiving a couple messages today
i had just received messages and then closed the keyboard
immediately i noticed the samsung logo
just seeing if this strikes anyone else's memory as being the point of occurrence
this was with eh17 and mkasick kernel
i have also seen one random reboot with my phone just sitting there
that was eh17 with eh17plus kernel from chris41g
but i also got the sms keyboard close reboot then as well at least once
i posted a kmsg for mkasick but he didn't see anything
just hoping to document the occurrences to help narrow in on the exact issue.
save the whining for another thread...thanks
i have a lot of bloat removed.
launcher pro
no animations
2 minute screen timeout with keyboard set to same as screen
auto rotate off in both settings and launcherpro
stock sms app

Sounds more like you have a loose battery. Random reboots occur in GB leaks when phone is sitting idle. It was found to be a voltage and deep sleep transition during partial wakes that was causing it. The fix was posted in this forum using Tegrak and SetCPU combination.

kennyglass123 said:
Sounds more like you have a loose battery. Random reboots occur in GB leaks when phone is sitting idle. It was found to be a voltage and deep sleep transition during partial wakes that was causing it. The fix was posted in this forum using Tegrak and SetCPU combination.
Click to expand...
Click to collapse
+1
Here's what works for my phone:
SetCPU
OnDemand 100mhz/1000mhz
Screen Off: 100mhz/200mhz
Tegrak (Make sure you buy it for the newest version.)
OnDemand 100mhz/1000mhz
100mhz @ 1000mV
200mhz @ 1025mV
Edit:
If it is a loose battery, you can always jam some cardboard back there to make sure. I can't remember where the link is to the SetCPU/Tegrak, so I just posted my own settings for ease. It does seem to vary per phone, just like overclocking/undervolting, so a bit more reading/tinkering might be required.

my reboot issues happened a lil over 2 minutes into a phone call on every rom I tried so I went back to eg22

The fix for reboots is a page or 2 down here in General called "Possible fix for random reboots"
Sent from my SPH-D700 using XDA App

eigerzoom said:
from what i've noticed
it happens when closing the keyboard under certain circumstances
possibly only during sms messaging
i was able to duplicate a reboot sending/receiving a couple messages today
i had just received messages and then closed the keyboard
immediately i noticed the samsung logo
just seeing if this strikes anyone else's memory as being the point of occurrence
this was with eh17 and mkasick kernel
Click to expand...
Click to collapse
Also running "stock" EH17 with the mkasick compiled kernel, and haven't had any reboots in the last 4 days. I use the keyboard to send sms many times without problem. Sounds like a mechanical problem to me. I've heard other people with loose batteries or worn battery contacts have exactly the same issue. Try wedging a thin piece of cardboard into the space along the bottom of the battery and see if the problem goes away.

definitely a loose battery
i'm dumb
i'm running the 3000mah with extended door
i just set it down with a bit of extra force and yep reboot
thanks people

didnt know there was a fix for the random reboot.. i have 2 try that out its funny that it doesnt happen while plugged in

makipsee said:
didnt know there was a fix for the random reboot.. i have 2 try that out its funny that it doesnt happen while plugged in
Click to expand...
Click to collapse
It doesn't happen while plugged in because it runs constantly at 100 Mhz and does not go into deep sleep. That is how we narrowed down the issue in that other thread and added the screen off profile to SetCPU.
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=1276417

kennyglass123 said:
It doesn't happen while plugged in because it runs constantly at 100 Mhz and does not go into deep sleep. That is how we narrowed down the issue in that other thread and added the screen off profile to SetCPU.
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=1276417
Click to expand...
Click to collapse
ahhh ok... yea i was looking in that thread before thanks

I fixed my loose battery by sliding a half credit card ... Actually an old Kroger card... In the back of the phone. Tighter and zero reboots. Specific to the battery anyway. Cm7 does not reboot.
Sent from my SPH-D700 using XDA App

For me at least, the mkasick compiled kernel on EH17 doesn't reboot either. With the standard kernel it rebooted within a half hour of install.

delay between Ringtone and Screen

Hi All,
I have a weird issue.
When someone is calling me, there is a delay (several seconds) between the ringtone sound and the number appearing on the screen.
Its occur especially after at least 5 minutes of not operating the phone.
Any help?

Yeah me too facing same issue. it takes 1-2 secs to wake up while ringing.

are you using Abyss kernel and under clock CPU to minimum 100mhz ?
I had this problem with Abyss Kernel and set minimum speed of CPU to 100mhz.
using CF-Root kernel now, this problem is gone.
could be 100mhz wake up latency.

Does it work with Rocket v20?

wireless.tech.expert said:
Does it work with Rocket v20?
Click to expand...
Click to collapse
not sure, you can consult with the peeps in the Rocketrom thread, sure they can help you .

Currently on darky rom. not seeing this

[Guide][Theory] Samsung Galaxy Note ICS Build SOD Fix!

I have found the fix for SOD's on ICS builds (based on i9220 leak kernel)!!
THIS YOU DO BY YOUR SELF! I TAKE NO PART IF YOU HAVENT READ THIS THRU AT LEAST 2 TIMES BEFORE DOING THESE STEPS!
First of I had a theory of the i9220 kernel and its CWM that in one way it does not represent our hardware right. It has its differences and they are more on a file level then anything. This can be shown easy by trying to format /system. By doing so you will get in to a world of trouble (so don't try it, just trust me)
So my first thing as I have never had a SOD was try to RECREATE a SOD. So my theory is/was that the kernel provided for the i9220 is the real culprit in this scenario and that by flashing RADIOS with its built in CWM is a MISTAKE!
And boy was I right! I installed a random N7000 radio .zip thru CWM (Now when I say CWM I do NOT mean some crappy .apk or app that does it FOR you. I mean the CWM you enter by starting the phone with Power + volume up + home button) and rebooted the phone.
I played around with it and let it rest for 30min. When I was going to wake it up again... SOD!!
Mission Accomplished!! Recreated Error!
So now ... how to fix it...
First off wee need to learn how Mobile Odin works and why this method works to fix it. When Mobile Odin is instructed to flash a ROM or anything else (like a radio) it boots to ITS OWN KERNEL! That is the file that Mobile Odin downloads on first run!
Now IF you are going to use Mobile Odin while on any ICS build (except the original i9220leak! Important! Mobile Odin will NOT work on stock i9220 leak!) you have to be 100% sure that you are PROPERLY ROOTED!
So Steps...
Step1: Get ZCLP1.zip Radio from the Radio Thread and extract the modem.bin file.
Step2: Get Mobile Odin and just flash modem, nothing else. The modem.bin you just extracted.
Step3: It should reboot and enter the Blue Odin Droid Kernel and flash radio.
When its done it will reboot again. And you will probably be SOD Free!
Hit the thanks button if this worked for you guys. Thanks for reading.

Oh btw I don't think that it is locked to use only that modem. I had la3 radio before and I didn't suffer any sods so don't get to blind on just the Chinese radio...
| GalaxyNote ICS | Tapatalk |

im on midnight 2.0 ics.i done what u said in the post.i just had a sod.
here is how it happened.i pressed wifi in pull down notification.it was stuck ..wifi would not turn on after the screen turned off and try to awake by using power button.it was dead.it would not do anything.had to hold power button for couple of min to restart.

Im currently on gb, used ics for a couple of weeks since chinese leak. Im not a 100% sure, but i really think it has something to do with wifi. I never really tested but I always had the most sod at home while connected. Rarely had sod at work, which was cellular data H+.

There is another method and that is to increase min CPU speed from 200 to 500mhz. Has worked for some...
| GalaxyNote ICS | Tapatalk |

Thanks mate, i'm gonna try some of that.
These SOD are making me crazy :/ Some day i can have 0 SOD and the day after 1 per hour...

You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA

super_sonic said:
You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA
Click to expand...
Click to collapse
But wouldn't that drain the battery faster?
Sent from my GT-N7000

I only get sods when wifi doesn't activate too. If it doesn't switch on immediately then the phone won't come out of sleep. I just restart manually when this happens instead of letting it sleep.
Sent from my GT-N7000 using XDA

I get SOD with or without wifi completely randomly. I'm going to try increase CPU see if that works.

excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx

It's not specific to the radio. I've done Mobile Odin Pro to try many different radios. Each time, I'd get an SOD.
Folks have also reported getting an SOD WHILE in Airplane mode. This completely puts the baseband issue out of the picture together.
If it's in airplane mode, it can't be a WIFI issue too.
The kernel itself is just bad and it has its quirks.
Due to the inability to get a logcat when it is in a SOD state, it makes it very hard to pinpoint what is causing the SOD.

MaZaGnGy said:
excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx
Click to expand...
Click to collapse
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!

robmeik said:
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!
Click to expand...
Click to collapse
Nope, it's Sleep Of Death. The rest is correct
Sent from my GT-N7000 using XDA

We need a SOD-off app

Look for wake lock power manager in play store. It creates a wake lock, preventing deep sleep, and consequently a SOD. For the price of a low battery autonomy.

I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.

masiullah said:
I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.
Click to expand...
Click to collapse
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.

Akiainavas said:
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.
Click to expand...
Click to collapse
Is there any way or app which stops using certain frequencies.

[issue] Need some feedback from GB users

hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.

ellokomen said:
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
Click to expand...
Click to collapse
This has never happened to me, but maybe try to turn off the device and take the battery out, leave it for a minute and reinsert the battery and restart. Then try to reproduce the problem.

Never happened to me or even heard of it
Sent from my GT-I9100

have you tried to see if this bug would occur without power saver mode on?,i never had this issue before nor heard of it

thanks everyone for your answers and concerns, the problem has been isolated:
It was a bug caused by a underclock that I did have that so far only occurs on the circumstances that I had on my phone.
When your phone turns off the screen, it will go to sleep mode or deep sleep mode depending on the running apps you have in that moment, these modes allow the CPU to low the frequencies (CPU Clock) in order to preserve battery life.
Comes to public interest that when using the camera app, the phone uses a high frequency clock to process photos and videos taken with the camera.
As because I did have a custom kernel that tweaks the CPU in order to gain more battery life, when battery saver option (which slow the max freq. clock of the CPU) was ON in my phone, the phone couldn't jump directly from sleep mode to max freq mode to keep camera app running and the CPU kept "slept"
If serves as interest of anyone, the kernel I was using was Siyah Kernel (don't remember which version, just check out the date this thread was posted and compare it with siyah kernel log to know by that date which was).

Often not getting notifications in Standby

Hi everyone,
I've got a very annoying problem with my S5, but I think it was already there with the S4...
The thing is: When my phone is in "standby", then I often don't get notified if a new Hangouts message or email arrives. This is happening on CM 12.1, but I'm pretty sure it was also happening on official Samsung 5.0 ROM. I thought it might be my Pebble (or rather it's corresponding app) that caused this, but I now have a Sony SmartWatch 3, and it seems the problem is still there. If does not always happen, sometimes it can be OK for a day, but then it's back the next day. Sometimes it takes 5 Minutes for the Notification to appear, somtimes 1-2 hours. Sometimes all the backlogged notifications get pushed to the phone when I leave house and the WiFi connection changes over to LTE, sometimes it triggers when I turn on the screen, and occasionally I have to turn on the S5, unlock, open Hangouts, select a conversation thread, wait a minute, and then the backlogged messages will appear.
It seems, that Android randomly decides "not to bother" looking for new incoming messages. It just collects them on the server, but doesn't push them to the phone.
This completely erratic behaviour is driving me nuts, and I have no idea how to fix it. I'm not using any batterysaver, RAM-wiping or other potentially interfering apps, no "Priority mode" or anything. The problem has persisted more or less unchanged through several OS transitions and factory resets.
I'd be eternally grateful for any help!
Thanks!

Do you use which S5 version? G900F?

Yes, 900F

Go to the advanced wifi options and check such settings named like "wifi standby" or "wifi sleep".

Wifi is "always on" in standby. At least that's what the setting says.

Ok and you use a custom rom or stock?

Currently CM12.1 latest nightly, but pretty sure it happened on Stock as well.

I use a custom kernel and can change the governor. After that change the notifications comes without an delay. Is that an option for you?
If you want you can change the governor without a custom kernel. You have to install this app: Trickster Mod
Enable root in the developer options from CyanogenMod. Trickster Mod needs root.

Thanks. I'll try that. What Hovernor do you use? I liked Intelliactive when I ran custom kernel.

I use the Boeffla kernel. In this kernel the zzmoove governor is available. That's the best gov in my opinion.
The Interactive gov is a good option too or the intelliactive how you said.

Damn. Kernel was already on Interactive ...

Than change it to another. Do you have some more options?

I'll try that. I just used an app to check for problems with connectivity, but that came up with nothing. The phone does not lose connection (app checks every minute to ping a certqin server) , the notification service simply seems to pack up.
Maybe I'll revert to TouchWizz and see how it goes there... Oh dear... I hate TouchWizz...!

TW is crap. Try another governor and give me a short feedback.
Here you can read more about all govs:
http://forum.xda-developers.com/showthread.php?t=1767797

I know about governors, but don't have any decent ones in CM at the moment. I'll look for a custom kernel.

Flash the Boeffla kernel. Boeffla at its best! Take the newest test kernel and not the stable, because the stable is not stable [emoji6]

Ok, I'll give it a go. I sort of doubt it'll be the answer, because this feels more like a problem buried somewhere in CM than a Kernel issue, but I might get lucky. It's really extremely annoying!!!

The strange is that nobody has such problems like you with original CM kernel. I used the original kernel 2 weeks and there was no problems with the notifications.

I found a promising lead, something about a new Wifi optimizasion (arp offloading) that could be turned off in KK but no longer in LP and causes problems like this. Trying to turn it off manually now. Also, apparently there are problems with IPv6, so I'll try to turn that off as well if I can find out how...

OK please let me know when you find it and if it works or not [emoji3]