Develop Bugs

SkyRaider 3.3 + KxK #5 question.

I just flashed SkyRaider 3.3 and KingxKernel #5 and I was wondering if that's a good combination for battery life ? Thanks
Sent from my ADR6300 using XDA App

You tell us. Is it?

It's super fast but the thing is y just installed set CPU cause I guess your not suppose to have it when you kings kernel
Sent from my ADR6300 using XDA App

G_Lowaslike said:
I just flashed SkyRaider 3.3 and KingxKernel #5 and I was wondering if that's a good combination for battery life ? Thanks
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I ran that same combo for a while and IMO the battery did what it does best: SUUUUUUUUCK%$#^& ! .......that been said it's been like that pretty much all the time, if you really use the phone that is, not complaining at all, just saying. That's why I always carry a spare one. There are way too many variables and setup preferences that might differ from one user to the next and if you overclock the thing uses even more juice. Really love the 3.3 Rom but the lack of 3G deal in my case forced me to reflash in a different direction........Good Luck !

What do you mean by lack of 3G ?
Sent from my ADR6300 using XDA App

G_Lowaslike said:
What do you mean by lack of 3G ?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Exactly that......no 3G, very very poor signal if any, I thought it was just me but after reviewing the ongoing 3.3 thread I found out that some people are experiencing this issue too, very small % though. In my case I was with T-Mobile for quite a while, fantastic service but poor signal-coverage at my business location so I switched to Verizon which really rocks signal-coverage-wise until now......sooooo......I really love the ROM and really hope for a feasible fix to get back to it.

it has to be a downed tower or old prl the rom/kernel dont control the phone calls so id say to check with vzw and run the appropriate updates, hope it gets fixed for ya

I'm using KK BFS #5 and the latest SkyRaider and I've got no such issues. No 3G troubles, no battery suckage, no weird stability issues...
Seems all ok for me. I'm happy with the combination. Sedio 1750 battery, BTW.
I do have SetCPU installed, interactive governor, and a profile to lower the clock speed to 612MHz when the screen is off. When awake, the phone is overclocked one notch to 1036MHz.

G_Lowaslike said:
It's super fast but the thing is y just installed set CPU cause I guess your not suppose to have it when you kings kernel
Click to expand...
Click to collapse
Not too sure where you heard this from. Could you post a link? I've used nothing but KingXKernel's on various Sense-based ROM's, and I've used SetCPU to tweak each and every one of them.
rayporsche said:
I ran that same combo for a while and IMO the battery did what it does best: SUUUUUUUUCK%$#^& !
Click to expand...
Click to collapse
I've been running KK#5-BFS on SR 3.3, and my battery life (stock battery) has been pretty fantastic. Of course, that's completely relative, and I'm not a super heavy user, but with all other variables being constant, my battery life has definitely improved since going with this combo. You just have to be intelligent with your SetCPU settings, profiles, and phone settings.
rayporsche said:
Exactly that......no 3G, very very poor signal if any...
Click to expand...
Click to collapse
I initially had the same 3G issues with SR 3.3, but ihtfp69 has since fixed these problems with 3.3.1, and my 3G has been flawless ever since.

I use king kernel BFS #5 with setcpu and i get some pretty amazing battery life

I am running the same combo with ROM and kernal minus the SetCpu and forget to charge my phone overnight. So for over 24hrs I was at 29% battery life. This is the best combo I've experienced so far for great battery life. Make sure you do a full system wipe, once you Flash the ROM..

does anyone find that charge times have increased after installing king's kernel 5? It may be just my imagination but I wanted to see if anyone has seen the same

[Q] cpu governors that dont exist on kernal

is it possible that because i had a cpu governor set from an older kernal still active, that it could cause big problems for my battery [i had some smartass governors from net 4.2.1 and changed back to 4.1.9, also bfs to cfs] and ive been noticing my battery dying beyond rapidly, from 100 to 40 in just 4 hours with nothing more than a few..hundred.. texts, but usually that only eats up about mabey 20% battery, and the governor was the only thing i could find to possibly cause to problem.

It's possible that an application is keeping your phone on wakelock.
Download system panel and spare parts so you can see which app's and using all the juice up. I highly doubt its an old governor from another kernel.

crazyloof said:
It's possible that an application is keeping your phone on wakelock.
Download system panel and spare parts so you can see which app's and using all the juice up. I highly doubt its an old governor from another kernel.
Click to expand...
Click to collapse
probably shoulda mentioned, i checked all that, im not new to my battery dying but its just never been so horrible in my life and that was literally the only thing out of the norm i could find anywhere. could it have been a bad kernal flash? it was probably the first time ive not flashed after a fresh install and mabey something went wrong?

envoykrawkwarrior7 said:
probably shoulda mentioned, i checked all that, im not new to my battery dying but its just never been so horrible in my life and that was literally the only thing out of the norm i could find anywhere. could it have been a bad kernal flash? it was probably the first time ive not flashed after a fresh install and mabey something went wrong?
Click to expand...
Click to collapse
what hardware are you on? could be the rom that your running no offense to any of the devs but myns is running on 3.30 and that has had some bad battery effects for people with any phone running 0003 and below unless your your phone came with 3.30

Jbcarrera said:
what hardware are you on? could be the rom that your running no offense to any of the devs but myns is running on 3.30 and that has had some bad battery effects for people with any phone running 0003 and below unless your your phone came with 3.30
Click to expand...
Click to collapse
it is 0003 so you think so? i mean i love my rom but if thats whats keeping it down i could always try another i guess or go back to an older version on myns

Screen flickering issue

I recently had to get a replacement Evo . I rooted it and installed Myn RLS5 then installed Net 4.3.2 More Havs SBC kernel on the phone . I woke up one morning to find the screen was flickering when I pushed the power button to check the time and weather . When I unplugged from the charger it was fine afterwards . Since then I have unrooted and went back to completely stock . My HW003 never had issues with kernels and Im not even sure if this is a result of a kernel . The flickering I expierenced were long strips going the full length of the screen that flickered as if they werent getting enough power or something like that . I was wondering if anyone else has seen this issue before . But like I said since flashing back to bone stock I have had no issues .........as of yet. Does this sound like a potential hardware issue or more of a software issue ?

Sounds like screen tearing, which is usually (if not always) the result of using an incompatible kernel for the ROM your on.

I had thought maybe that might be another possibility , I had this set up with the HW003 setup . Same kernel same rom and had no issues like this before . Unless Im suffering from the "some phones handle certain software differently then others" even though they are suppose to be the damn same thing . Hmmmm I wonder if Skynet is taking over ROFL !
Also I always though screen tearing occured when moving from one screen to another . This flickering was on the home screen .

I had the same issue with a custom or stock rom. Also, mine had a grey area on the screen that looked like there was water in it. So took it to sprint, it was something with the screen itself. Got a replacement screen in two hours and the same phone under warranty. And now on Myn's RLS5 and Netarchy 4.3.2 CFS- nohavs-nosbc. No issues.

It happens some times, no need to worry until it becomes consistent. If turning the screen on and off solves the problem for the day it is normal. Also, it might be a kernel with too much undervolting.
Sent from my PC36100 using XDA App

Ill reroot tonight and try a less aggressive undervolting kernel . It hasnt done it since I went back to stock so maybe it was the kernel and the undervolting

I have this same issue sometimes running myns with SBC Kernals. I noticed it doesnt happen when I flash and use an HTC kernel. Are these safe to use?

dw3bb10 said:
I have this same issue sometimes running myns with SBC Kernals. I noticed it doesnt happen when I flash and use an HTC kernel. Are these safe to use?
Click to expand...
Click to collapse
I have always ran SBC kernels with no issues . I did switch to a lower undervolting kernel from Net 4.3.1 cfs havs sbc . It fixed the issue , Im going to assume this kernel doesnt undervolt as much as the more havs kernel does .

Kernal for sure
I root phones all the time. After rooting and custom roms I put the most aggressive undervolting HAVS SBC I can find and install. The very first thing I do on the first boot after the new kernal is look for the screen issues you describe.
Sometimes they are wild and obvious and other times it is just a slight flicker and hard to see. Either way, it just means the undervolting is not jiving with the phone. Switching to "less" instead of "more" usually does the trick.
The crazy part it I can have two EVO's with identical hardware, software, Hboot, radios etc. and sometimes one will freak out on the kernal and the other loves it. Its a trip.

[Q] advice on Undervolt/havs and overclocking

Yesterday I put the netarchy havs less kernel on my phone and with some stress testing and general testing found that it worked well at 1.15 mhz. I carried it around all day messing with it no problem. Today, the real test came when I ran GPS on my phone in my car. The phone lasted about 3 minutes of GPS before it started rebooting. Then my 4g was broke from it somehow. Anyhow, I restored my phone and all seems well now.
I still want to mod the voltage and clock speed. Any advice on this? The phone always gets hot when I use GPS because it uses a lot of processor, frequently its on the charger and possibly in sunlight. When it was not overclocked or undervolted my phone NEVER reboots not once since I've had it.
Is the problem the undervolting, overclocking or both? Should i give up on this due to the way I use my phone?
Thanks in advance.

Try different kernels. I use netarchy sbc 4.2.2 more havs, works great. I also use his 4.3.4 more havs sbc. They both work for me. Battery life is awesome and gps works good. No prob here. Try those out and see what happens. Hope this helps.
Sent from my HTC EVO Phone, should'nt we all have one?

Okay so is there any danger to this? It seems like every time my phone starts rebooting from overclocking or undervolting apps start disappearing from my phone and stuff stops working.
I use amon RA 2.3 and every time I recover it works again but I was just wondering how dangerous it is for me to experiment they way I have been. I have already recovered my phone 3 times from issues like this that broke it.

Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.4 more havs, overclocked to 1190 and it's as stable as can be on my phone. However, if I go over 1190 it immediately locks up and reboots.
Sent from my HTC EVO 4G with Tapatalk

kd0axs said:
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.2 more havs, overclocked to 1190 and it's as stable as can be on my phone.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah but the reboots are hurting my phone! I have to restore it due to the problems the reboots and freezing causes (sometimes I have to battery pull due to full lockup). 2 times when I pulled battery due to full lockup apps went missing from phone memory but the available space on the phone was as if the apps were still there. Another time my 4g wouldn't turn on.
Is that abnormal? Can it mess up my phone in a way that recovering wont be able to fix or is recovering generally a sure shot?

The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.

gpz1100 said:
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
Click to expand...
Click to collapse
Because I use the 1-1-1 power management system (see sig) my main concern is performance. I love my phone and when I use it I want it to be fast and smooth. I would *prefer* if the extra speed didn't dramatically change my battery life but I'm okay with a small decrease in battery life if the speed gain is reasonable for the tradeoff. Anyhow I thought a lot of people ran HAVS along with overclocking to have both to a degree.
Only time I charge my battery is when I am using it in the car with my car charger. At home I charge all my batteries on an external charger - my phone is a mobile device I prefer to never be bound to a cord. I sleep with my phone next to me off the charger lol.

Okay so my phone is running more HAVS now and it seems the same as before so I guess my friend is HAVS friendly. I will run this for a day to check if any reboots happen and aim for tomorrow to overclock again. It may have been the 1.19 mhz that caused the issue. I will drop it down to 1.15 or 1.1 and see if its stable.

Sleep Of Death ("SOD")

I haven't seen anyone post about this yet, so I am going to take the plunge. I have a finicky device. Regardless of what kernel I put on, if I overclock at all, I will eventually get an SOD. I have tried Perseus and Core, all flavors, and started various times all the way from clean, Triangle-Away'd stock via Odin...same thing. It is really frustrating. The best results I get seem to be when I don't mess with the voltages at all, but eventually, SOD strikes. Sometimes I can go days. Today, I tried overclocking the new Perseus to 1.8 with stock voltage (after running it vanilla for 2 days with no issues), and within 2 hours, I had an SOD. I am currently on Clean 4.5, but have had the issue in every ROM.
Anyone else have a super-sensitive Note II with kernel overclocking? Anyone else seen SODs at all, under any other conditions?

What are you max screen-off and phone-on speeds clocked to? That could easily be the issue--I leave mine at 500MHz.

T.J. Bender said:
What are you max screen-off and phone-on speeds clocked to? That could easily be the issue--I leave mine at 500MHz.
Click to expand...
Click to collapse
Oh man, I am embarrassed to say I don't know...I am using STweaks currently with Perseus, and don't see where to set these values. I know that I was able to use profiles in SetCPU...
Where can I check these values? Appreciate your help!

I switched to SetCPU for now and created a couple of profiles. We'll see what happens.
Sent from my CLEANed Note II

Can't say that I get the SOD, but if the weather gets TOO cold (which it has for the last few weeks), my phone would reset itself and will be stuck at the "Samsung Galaxy Note II" screen until I pull the battery. Unlike your situation, I'm an extreme underclocker so it's easy to fix my issue (just give it a bit more juice!).

meatlocker said:
I haven't seen anyone post about this yet, so I am going to take the plunge. I have a finicky device. Regardless of what kernel I put on, if I overclock at all, I will eventually get an SOD. I have tried Perseus and Core, all flavors, and started various times all the way from clean, Triangle-Away'd stock via Odin...same thing. It is really frustrating. The best results I get seem to be when I don't mess with the voltages at all, but eventually, SOD strikes. Sometimes I can go days. Today, I tried overclocking the new Perseus to 1.8 with stock voltage (after running it vanilla for 2 days with no issues), and within 2 hours, I had an SOD. I am currently on Clean 4.5, but have had the issue in every ROM.
Anyone else have a super-sensitive Note II with kernel overclocking? Anyone else seen SODs at all, under any other conditions?
Click to expand...
Click to collapse
Coming from the Galaxy Nexus (and yes, I did my share of undervolting and overclocking with it) I know some of the dice used in making the cpu/gpu are not the same for every Galaxy Note 2. For example, where you got SOD problems used Perseus and Core, I could flash Perseus and Core on mine and not have the same problems at all. Best thing to do is try a different kernel till you find one that does not give you the SOD. Also, it is better to not flash a different kernel when you flash a new ROM as the kernel that is in the ROM usually works the best with it.

yes sod
I get the sod periodically irritating at times
I kept the phone unrooted and stock for 6 weeks or more, and i got the sod even then
I''ve rooted and have been using scottsroms for several weeks now, and get the sod about the same
I'm now wondering if it is a defective unit?

Anyone getting the sod probably has a bad phone. I would return it to be fixed. I personally never had the sod on any rom I have been on.
Sent from the TermiNOTEr 2!