[KERNEL] - {} Beast Mode 2.35 {} - N900T
- Thread starter cun7
- Start date
-
- Tags
- development
- Status
Yes I got it.
Also, not sure what ROM you were really on, or if you didn't clear data, or what you did... but I'll tell you right now that halfway through this log I can tell that you are causing whatever issues you are having
Example, right here:
Code:
02-20 01:14:05.833 E/OCApplication(4251): cannot detect color type
02-20 01:14:05.833 E/OCApplication(4251): cannot detect vibration type!
02-20 01:14:05.833 E/OCApplication(4251): cannot detect sweep2wake type!
02-20 01:14:05.843 E/OCApplication(4251): cannot detect fastcharge typeAnd here...
Code:
02-20 01:14:05.993 E/OCApplication(4251): setup cpu!
02-20 01:14:05.993 E/OCApplication(4251): fix cpu permissions!And here...
Code:
02-20 01:14:06.293 I/RootTools v2.6(4251): [rw, relatime] AND rwSo.... if you just flashed tweaked, and did a full data wipe, why is Root Tools app installed? Tweaked doesn't come with it.
Code:
02-20 01:14:07.763 E/OCApplication(4251): loaded gpu settings!
02-20 01:14:07.773 E/OCApplication(4251): setup voltage!
02-20 01:14:07.773 E/OCApplication(4251): fix voltage permissions!There are errors all over this log... that indicate user related issues. Your reboot issue is not because of the kernel. Your logs even indicate that you didn't even pull this log from tweaked ROM after a fresh install... I'm just confused.
Code:
02-20 01:14:07.823 E/OCApplication(4251): setup iosched!
02-20 01:14:07.823 E/OCApplication(4251): fix iosched permissions!
02-20 01:14:07.853 D/WifiDirectBR(4709): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.STATE_CHANGED
02-20 01:14:07.853 E/SELinux (4740): selinux_android_seapp_context_reload: seapp_contexts file is loaded from /seapp_contexts
02-20 01:14:07.873 I/IOSchedulerFragment(4251): fix permissions...
02-20 01:14:07.873 E/OCApplication(4251): loaded ioscheduler settings!
02-20 01:14:07.873 E/OCApplication(4251): setup color!
02-20 01:14:07.873 E/OCApplication(4251): color is NULL!
02-20 01:14:07.873 E/OCApplication(4251): setup vibration!
02-20 01:14:07.873 E/OCApplication(4251): vibration is NULL!
02-20 01:14:07.873 E/OCApplication(4251): setup mdnie!
02-20 01:14:07.873 E/OCApplication(4251): fix mdnie permissions!
Code:
02-20 01:14:08.273 E/OCApplication(4251): loaded socPower settings!
02-20 01:14:08.273 E/OCApplication(4251): setup thermal!
02-20 01:14:08.273 E/OCApplication(4251): thermal is NULL!
02-20 01:14:08.273 E/OCApplication(4251): setup fastcharge!
02-20 01:14:08.273 E/OCApplication(4251): FastCharge is NULL!
02-20 01:14:08.273 E/OCApplication(4251): setup lowmemkill!
02-20 01:14:08.273 E/OCApplication(4251): fix LowMemKill permissions!
02-20 01:14:08.333 I/LowMemKillHelper(4251): fix permissions...
02-20 01:14:08.333 E/OCApplication(4251): setup misc!
02-20 01:14:08.333 E/OCApplication(4251): fix misc permissions
02-20 01:14:08.383 I/MiscHelpers(4251): fix permissions...
02-20 01:14:08.383 E/OCApplication(4251): setup governor!
02-20 01:14:08.383 E/OCApplication(4251): fix governor permissions
02-20 01:14:08.383 W/GGovHelper(4251): fixPermissions: governor name mismatch
02-20 01:14:08.383 E/OCApplication(4251): setup appcontrol!
02-20 01:14:08.383 E/OCApplication(4251): setup zcontrol!
02-20 01:14:08.383 E/OCApplication(4251): fix z-control permissionsThere is also a line in there to disable the checkJNI... a popular useless build prop edit that I know dwitherell does not use...
I need you to not waste my valuable time. I don't know what your motive is here, or why you feel the need to pretend you did something when you clearly didn't, but I don't even see a reboot in the log.
You are on your own. I have yet to see one device have an issue with this kernel, and like I said, I've been on it for weeks now, so have others with zero issues... over clocked, undervolted, etc....
I have no reboots and rotation working as it should Running better than other kernels much snappier and color looks betta dont know about battery life yet great kernel thus far thanks running like a champ 
Sent from my SM-N900T using Tapatalk
Sent from my SM-N900T using Tapatalk
Been running for a couple days now & haven't had any issues with the kernel. It's incredibly snappy & stable, plus I've seen a slight improvement in battery life. Definitely my new favorite Kernel, thanks for sharing Op!
Sent from my SM-N900T using xda app-developers app
Sent from my SM-N900T using xda app-developers app
All I did was install tweaked. I don't even know what the app is that you mentioned.im not trying to troll or anything. Maybe I didn't do the log correctly? Maybe it's cause I'm using fauxclock?
What he is saying is that, when you fresh install a rom you wouldn't receive those type of errors on the logs. Namely being a Root Tools app that by what the logs says its installed. That app is not included on Tweaked Rom. Either you didn't do a fresh install or you did and restored apps and data which is why is showed up in the logs you posted.
I never backup and restore apps though. My apps installed from the play store when I logged in but that's it. I didn't even open anything but Twitter
I'm going to do another completely clean install and try again. Is there a recommended kernel control app?
Last edited:
Then you shouldnt have reboot issues. Im running this kernel now with tweaked and everything works fine. Personally I use trickster
Sent from my SM-N900T using Tapatalk
I shall try that as well.
---------- Post added at 10:39 AM ---------- Previous post was at 10:22 AM ----------
If I'm reading it right, it's saying that the app I use to control the kernel(faux clock) is causing issues?
It could be your app, yes.
And I saw the part of your log where you opened twitter.... You had zero tweets... Lol
I can't help users that cause their own issues tho you know? Not trying to be a **** by that, it just takes too much my time.
Start by removing the faux clock app
Sent from another galaxy
Of course. I can understand that. The thing is, I didn't know that I was causing issues. I was just using my phone the way I have in the past. Right now I just did a clean install of Tweaked again and I've only install the log app and trickster. No issues so far. I'm relatively new to logs so I didn't know that it was user error. I just wanted some help.
Also, the reason I was so upset about having issues is that the kernel is awesome. It's so smooth, yet battery efficient that I was super upset when I hit a problem because I didn't want to have to switch kernels.
Last edited:
well, 19 minutes in... I would say in 6 hours if you hadn't had an issue... then problem solved.
And you followed through and provided a log - that is just as useful to a developer as being able to read it yourself. Interpreting them isn't always so cut and dry. Like I said your log didn't show a reboot. I've just been doing this a while to know it was something else.
Thank you for the help. I have another question, if you don't mind.
I read in the op that there are sound tweaks in this kernel, so if I use something like Viper4Android to tweak my audio will it cause problems?
I just like to EQ the headphone settings and I like the surround sound feature that Viper has.
You should try an app like power amp then, just replace your music player as a whole. You are then guaranteed to have your app that you paid for work across multiple platforms, setups, etc
Well, any goal when adding a new kernel... you are seeking performance. They are all pretty equally battery friendly unless there is an issue. However, there are certain logging features disable to save some power and with the under volt capability you are you only limited to what your own particular device can handle.
I managed to luck out and get a decent cpu bin so I can clip 25 mv off the scaling steps across the board and not have any issues. For me it is a very power friendly performance monster.
2.57 - 2.64 GHz max frequency seems to be a good sweet spot for the max frequency allowed. The reason for this is because not only are over clock steps added, but the cpu's cache memory speed (l2 table) is also positively adjusted above the stock 2.2 GHz step. Performance comes from many places when talking about raw processing power - this kernel is very well balanced, and very fast.
Alright kewl, I currently use ColonelX and have used it since its was WonderChild. And that kernel is great AT Both Performance/Battery.
Ill test this out and report on my findings how it works out thanks for the reply.
- Status
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
9
I've known about CPU binning before I even had an Android phone because I am a quality engineer with a PE license in two different respects of engineering. This type of quality inspection is not new to me. And it does not "change" either. It is a hardware attribute that follows the manufactured part around during its service life.... Which is why the kernel reads it from the device then calls it out in the dmsg log during boot to apply proper voltage tables.
I've probably flashed a ROM more than a thousand times on various different Qualcomm devices. They have been using CPU binning for as long as I can remember, and not once have I flashed something, ROM, theme, kernel, and had my pvs number magically change. So, not sure what you think you are doing in my thread calling people idiots... Which will now get a mod on you... I'm going to keep my response very civil and just tell you to get out of my thread before things get ugly for you. And they will get very ugly.
Know what you are talking about before you spout off next time.4
That's probably it.
Do me a favor... just real quick to make sure... download tweaked ROM then boot to recovery and make a full back up of your ROM you are on now (just system and data).
Wipe data and system in recovery then flash tweaked, then flash the Beast kernel 2.35
Boot up, and tell me if it reboots during a rotation.
Thanks, it would be really helpful.4
Yes I got it.
Also, not sure what ROM you were really on, or if you didn't clear data, or what you did... but I'll tell you right now that halfway through this log I can tell that you are causing whatever issues you are having
Example, right here:
Code:02-20 01:14:05.833 E/OCApplication(4251): cannot detect color type 02-20 01:14:05.833 E/OCApplication(4251): cannot detect vibration type! 02-20 01:14:05.833 E/OCApplication(4251): cannot detect sweep2wake type! 02-20 01:14:05.843 E/OCApplication(4251): cannot detect fastcharge type
And here...
Code:02-20 01:14:05.993 E/OCApplication(4251): setup cpu! 02-20 01:14:05.993 E/OCApplication(4251): fix cpu permissions!
And here...
Code:02-20 01:14:06.293 I/RootTools v2.6(4251): [rw, relatime] AND rw
So.... if you just flashed tweaked, and did a full data wipe, why is Root Tools app installed? Tweaked doesn't come with it.
Code:02-20 01:14:07.763 E/OCApplication(4251): loaded gpu settings! 02-20 01:14:07.773 E/OCApplication(4251): setup voltage! 02-20 01:14:07.773 E/OCApplication(4251): fix voltage permissions!
There are errors all over this log... that indicate user related issues. Your reboot issue is not because of the kernel. Your logs even indicate that you didn't even pull this log from tweaked ROM after a fresh install... I'm just confused.
Code:02-20 01:14:07.823 E/OCApplication(4251): setup iosched! 02-20 01:14:07.823 E/OCApplication(4251): fix iosched permissions! 02-20 01:14:07.853 D/WifiDirectBR(4709): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.STATE_CHANGED 02-20 01:14:07.853 E/SELinux (4740): selinux_android_seapp_context_reload: seapp_contexts file is loaded from /seapp_contexts 02-20 01:14:07.873 I/IOSchedulerFragment(4251): fix permissions... 02-20 01:14:07.873 E/OCApplication(4251): loaded ioscheduler settings! 02-20 01:14:07.873 E/OCApplication(4251): setup color! 02-20 01:14:07.873 E/OCApplication(4251): color is NULL! 02-20 01:14:07.873 E/OCApplication(4251): setup vibration! 02-20 01:14:07.873 E/OCApplication(4251): vibration is NULL! 02-20 01:14:07.873 E/OCApplication(4251): setup mdnie! 02-20 01:14:07.873 E/OCApplication(4251): fix mdnie permissions!
Code:02-20 01:14:08.273 E/OCApplication(4251): loaded socPower settings! 02-20 01:14:08.273 E/OCApplication(4251): setup thermal! 02-20 01:14:08.273 E/OCApplication(4251): thermal is NULL! 02-20 01:14:08.273 E/OCApplication(4251): setup fastcharge! 02-20 01:14:08.273 E/OCApplication(4251): FastCharge is NULL! 02-20 01:14:08.273 E/OCApplication(4251): setup lowmemkill! 02-20 01:14:08.273 E/OCApplication(4251): fix LowMemKill permissions! 02-20 01:14:08.333 I/LowMemKillHelper(4251): fix permissions... 02-20 01:14:08.333 E/OCApplication(4251): setup misc! 02-20 01:14:08.333 E/OCApplication(4251): fix misc permissions 02-20 01:14:08.383 I/MiscHelpers(4251): fix permissions... 02-20 01:14:08.383 E/OCApplication(4251): setup governor! 02-20 01:14:08.383 E/OCApplication(4251): fix governor permissions 02-20 01:14:08.383 W/GGovHelper(4251): fixPermissions: governor name mismatch 02-20 01:14:08.383 E/OCApplication(4251): setup appcontrol! 02-20 01:14:08.383 E/OCApplication(4251): setup zcontrol! 02-20 01:14:08.383 E/OCApplication(4251): fix z-control permissions
There is also a line in there to disable the checkJNI... a popular useless build prop edit that I know dwitherell does not use...
I need you to not waste my valuable time. I don't know what your motive is here, or why you feel the need to pretend you did something when you clearly didn't, but I don't even see a reboot in the log.
You are on your own. I have yet to see one device have an issue with this kernel, and like I said, I've been on it for weeks now, so have others with zero issues... over clocked, undervolted, etc....4
Your CPU bin is the result of your device's inspection and test criteria at the Qualcomm factory. Basically a high bin CPU like a 5 or 6 is a very well made chip. Very little imperfections in the manufacturing process. What this means for a HIGH bin is that the chip requires less voltage to operate at any frequency than, say, a bin 1. This is why you see some people having reboot issues when trying to under volt. Their processor becomes unstable... Too little juice.
Think of it as friction. If you have a well oiled arm on a machine, and part of that arm's job is to force it's way through an opening repeatedly, and the tolerances on the arm and the opening are just slightly off... Well, for that "more out of tolerance" one to do the same amount of work as one that's parts were machined perfectly, it would require more force. Think of the machine as the CPU, the force of the arm as the voltage required to do the work, and the tolerance of the parts as the same - just a different type of force being applied.
A higher CPU bin is generally speaking a more stable chip. Bus frequency, RAM speed, GPU speeds... Everything is bumped slightly on a high binned CPU because it was built better, is more stable, and chip can handle it.
Here is an interesting article that most people will find shocking. Look at the difference is clock rates of low and high binned chips:
http://www.androidbeat.com/2013/09/difference-snapdragon-800-2-2ghz-2-3ghz/#.Uwdf2p_TnqA
A 3 is actually not bad. More rare. Highest I've seen in a note 3 is a 5... Couple of 4's.... I think 2 is the most common from what I have seen. I am going to start a thread talking about it, what it means exactly, etc
Sent from another galaxy
