yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] pyroguysf:
The short version is a change in drivers- both ROM and kernel need to be on the same page for what drivers they're using. Since CM on the DNA is still under development, occasionally major driver changes happen. An exaggerated example would be trying to use an AMD video card driver for an Nvidia graphics card- it's still a graphics card driver, but they're not going to be compatible. The kernels you mention are from an AOSP device- ours only has official support for HTC's Sense, so to make a kernel compatible with AOSP on our device, it's almost like writing for a new device.

As for performance, etc- it's all good, but there's always room for more optimization, especially since there's still major development going on.
[HTC Droid DNA] -DroidIsDNA-:
Long and short, this new version won't work until the new cm is up and the other ROMs update with commits.
[HTC Droid DNA] Upstreammiami:
So why post it lol
[HTC Droid DNA] djh816:
Because this is a development forum and the git code has what is needed for those that really want to build and run it..
[HTC Droid DNA] crpalmer:
As someone else pointed out, we are not at a stable build. Chad previously patched our kernel to an intermediate version which was better than where we were but still out of date relative to what CyanogenMod is really expecting. The changes that were pushed move to a newer version of the video code which matches up with what CM is expecting to be built against. Being a major version change, it involved changing the interaction between the kernel and the rest of the code.

In general, kernel changes are being added to add or update functionality that is needed by the CyanogenMod code. This means that they will continue to be tightly coupled with changes to the other software.
[HTC Droid DNA] crpalmer:
Because it was either now or not likely to happen until much later this week/weekend as I'm not going to have much development time until then...
[HTC Droid DNA] johnwaug:
Thanks for the knowledge and the killer builds. I appreciate you explaining the process you are undertaking. We are all lucky to have such great developers.
[HTC Droid DNA] t1gartist:
Why do u wanna change clocks is 192 not low enough and is 1728 not fast enough?the reason not is over clock heavy is for stability reasons but if u want to heavy over clock or device pull source make clock changes and compile I am slightly clicked higher and a few other things changed also but palmer does have the best battery life
[HTC Droid DNA] d08speed3:
Your newest kernel runs amazing! Its definitely feels smoother! Thank you! Didn't think it could get better. :D

His: HTC DNA

Hers: LG Optimus G
[HTC Droid DNA] -DroidIsDNA-:
You liking the new cm with this kernel?

BTW love your SIG. My girl just switched from iPhone 5 to s4 so I might throw her a bone :p surprise surprise, she adores it...

Back on topic, I plan on flashing this tomorrow. Thanks for your work palmer :) enjoy your rest
[HTC Droid DNA] d08speed3:
Yes I'm loving it. Has a slight edge over his last kernel. My lady had a iPhone 4 and I finally got her to switch over to Android. She's rooted, unlocked, and running the latest CM. Now she's hooked and always bugging me about "any new updates" haha!

His: HTC DNA

Hers: LG Optimus G
[HTC Droid DNA] -DroidIsDNA-:
Hahahaha. There's a one click root for the at&t s4 I'm gonna convince her to try it :)
[HTC Droid DNA] planedoc:
I'm on flyhalf 7/8 build and crpalmer latest kernel. System tuner shows that only one core is online, other three are offline, is system tuner reading this right or is something wrong here?

Edit: I guess it wasn't just using them at the moment.:confused:
[HTC Droid DNA] tman23:
Are you on the latest cm?
[HTC Droid DNA] danielhall2689:
Sorry I kind of sounded like a jerk with that one. Just trying to protect the awesome devs that we have. See if Google will teach you how so whenever it happens again you can just pull it real quick :)
[HTC Droid DNA] djh816:
+1 for screen of death on CM10.1 7-04 build with interactive, noop. Sorry I'll get a logcat when I can.
[HTC Droid DNA] crpalmer:
You want /proc/last_kmsg if the phone reboots.
[HTC Droid DNA] d08speed3:
Been running fine since yesterday with new build and kernel. I have no screen of death. Things are flawless and no random reboots.

His: HTC DNA

Hers: LG Optimus G
[HTC Droid DNA] jbarcus81:
I don't think the issue is the kernel.. I ran stock CM 10.1 .. The latest build and experienced the reboots and lock ups when screen is off attempting to turn the screen on.. It's strange.. I even tried to pull a log .. but my last_kmsg is always empty.. Very odd indeed.. :D
[HTC Droid DNA] -DroidIsDNA-:
They had to clean the liquid thread too. Cmon guys, keep the drama off the interwebz. Palmer, I might have to jump in and do some logging. Hopefully I can reproduce these issues.
[HTC Droid DNA] jbarcus81:
The easiest way I found to replicate was to just simply lock, then unlock.. a few times and it will eventually lock. Sometimes I wouldn't have to do this and it would just never wake up, and reboot.. The logging? I have no idea.. I can't get it to work at all.. Only thing I can get is a logcat but crpalmer wants a specific log.. the last_kmsg I think.... Mine is always empty..
[HTC Droid DNA] crpalmer:
If you are having problems with reboots / screen not turning on, please try doing a clean flash of this ROM (it's what I'm running). Do not install my kernel, just use the built-in one and let me know if you are still having problems

http://d-h.st/hJK
[HTC Droid DNA] brennam7:
Odd, I honestly can't seem to replicate this issue. So here's my background on the flash.

Wiped everything (data/cache/dalvik/system)

Flashed the ROM(latest cm) gapps, then the latest kernel from palmer.

Only thing I have seen that MAY affect it is the screen off animation, mine is off.

If I get it to happen, I'll be sure to pull the kmsg. (/proc/last_kmsg if anyone is wondering/looking)
[HTC Droid DNA] -DroidIsDNA-:
I'm sorry to report I have no issues. Hahah.

Clean flash, didn't flash your kernel. Turned animations off as usual.

Then I flashed your kernel and no issues...improvement actually.

Not saying these people are lying, but maybe its hit or miss. I'd hit you with a kmsg, log cat, video, screenshot, interpretive dance, whatever if I could
[HTC Droid DNA] jbarcus81:
Downloading.. Will report.. And if I still have issues I'll try again to get you that log ... :silly:
[HTC Droid DNA] jbarcus81:
Same issue for me.. I still can't get a log. Exports as a blank txt file.. Sorry!
[HTC Droid DNA] crpalmer:
Can you try using adb

adb shell su -c "cat /proc/last_kmsg"

?
[HTC Droid DNA] jbarcus81:
Yeah I tried man... Pulls a blank file.. I needed to charge my phone so I flashed a Sense rom but I can get back into this and try to troubleshoot even more for you... But using adb and Lumberjack.. The TXT file is blank.. :crying:
[HTC Droid DNA] orangechoochoo:
Does this happen on the stock kernel?
[HTC Droid DNA] jbarcus81:
Yes.. All I flashed was the rom and gapps.. Maybe try without gapps?? I still can't get the log that will help these guys choochoo!!
[HTC Droid DNA] orangechoochoo:
Then it's probably a problem with the rom. I wonder if the changes to CM disabled reporting on the kernel via last_kmsg, hence your blank logs.

---------- Post added at 07:22 PM ---------- Previous post was at 07:18 PM ----------

Can you try crpalmers kernel.

Gorilla never said if the problem occured on the stock kernel but he said it happens on crpalmers kernel. It would be nice if you can corroborate it.
[HTC Droid DNA] brennam7:
Could you try wiping everything? (See previous posts of mine)

Also, I'd try to download the ROM and kernel again and see if its a bad download
[HTC Droid DNA] jbarcus81:
Yeah... Been wiping and installing for a few years now, I've tried wiping, formatting... rebooting recovery and repeating just in case though I know it does nothing.. I just .. I'm going to try and flash TWP recovery... then start all over and get these logs... So crazy these logs are blanked out...
[HTC Droid DNA] orangechoochoo:
And try crpalmers kernel too.
[HTC Droid DNA] brennam7:
Damn, that is weird. Didn't mean to call experience in to question. I'm literally breaking my power button trying to replicate this, still no dice.

Hope it works out for you man
[HTC Droid DNA] orangechoochoo:
Also try crpalmers pre 7/7 kernel too.
[HTC Droid DNA] jbarcus81:
Nothing like that.. I've just thrown every trick at this thing I know.. Not giving up!!

//

Sideloading gapps now.. It's time to get this going..

//

Same behavior.. No log will generate.. I quit for the night.
[HTC Droid DNA] jbarcus81:
There is a new build labeled cm-10.1-20130709-NIGHTLY-dlx.zip... I'm going to try it.. see what happens.. I was awaken by shooting severe pain in my lower left jaw and took a look to find a wisdom tooth is deciding to come in and looks to be sideways ... Going to be a long night and a long day tomorrow.. Might as well see what this new build will do for me..
[HTC Droid DNA] skynet11:
Question for jbarcus81: have you tried an on-phone logcat app like Logcat Extreme from the Play Store? I've had success using it to generate logcats on my DNA before.
[HTC Droid DNA] TonyStark R.I.P.:
Not sure if people missed this... or just didn't care!

~So, to make it clear~

This is a kernel Development thread

In this thread, there is no need for

~asking about other peoples settings

~asking "how does this compare to....."

~NEVER ask about updates, they will be posted when available.

~ asking, can xyz be added.

~ Posting a problem without a clear issue or logcat

~Saying Thanks, cool, great job... That's what the thanks button is for:svetius:
​

Thread cleaned... back to development please

Thank you
[HTC Droid DNA] jbarcus81:
Yeah.. I posted a logcat in the other thread for CM10.1 ... But the log they need is the last_kmsg .. I tried using ADB and an application called Lumberjack that I've used in the past but it's always blank..
[HTC Droid DNA] d08speed3:
So is there any way possible you can include the patches needed in your kernel so we can use the FauxSound app? This app let's you successfully increase in-call volume and speaker volume. I use the app on my ladies LG Optimus G on CM10.1. She was having the same low volume issue. The kernels they have on development use the patches needed to run the FauxSound app. Her volume is so loud now!

https://play.google.com/store/apps/details?id=com.teamkang.fauxsound

I know I'm asking a "Can you add question" but this is a direct fix for our CM10 low call volume. :D

His: HTC DNA

Hers: LG Optimus G
[HTC Droid DNA] crpalmer:
Nope.

Right now my understanding is that we don't have a great AMP setup. I don't know anything about how that hardware/kernel interface works and I don't want to be responsible for screwing something up and blowing someone's speaker...
[HTC Droid DNA] brennam7:
I'm assuming when you view the kmsg on the phone its blank as well?
[HTC Droid DNA] jbarcus81:
Yeah.. completely blank.. Nothing is being entered at all.. I haven't tried while running sense...

I just ran one while on Sense.. Works fine.. Log is full of info.. :confused:
[HTC Droid DNA] brennam7:
Man that's weird. Just checked mine (had to make sure lol) and its full
[HTC Droid DNA] jbarcus81:
But this is a new day!! I haven't stopped trying.. But I'm gonna stop posting until I find out something useful to not clutter crpalmer's thread up more than I have already.. :highfive:
[HTC Droid DNA] armydog13:
Lumberjack has not worked for me either. Haven't tried adb. But opening the file in ES file explorer gives me a full log file.
[HTC Droid DNA] jbarcus81:
Here it is!! Finally!

Never give up guys! I just hope this helps in some way.. But, here is my last_kmsg log after my phone rebooted on its own after not waking via the power button.. If plugged in to a power source, and you disconnect, the screen comes on fine.. It's when hitting the power button to wake... But here it is..

View attachment 2107917
[HTC Droid DNA] crpalmer:
What happened? Did you hit power off and then as soon as the screen went black hit power on and it then immediately rebooted?
[HTC Droid DNA] Gorilla*:
Palmer what happens for me is when the phone is plugged in charging, the screen is off, you hit the power button yo wake and the screen won't come on, causing a power cycle.

Just like the above poster indicates.
[HTC Droid DNA] -DroidIsDNA-:
Agreed, it is more likely to happen while charging
[HTC Droid DNA] jbarcus81:
The 2 posts above are correct.. It only seems to happen while charging.. Like I said, if I unplug the cord the screen comes on just fine by itself .. But, while plugged in, you hit that power button to get the screen on, you get nothing, and a reboot about 10 or so seconds later..
[HTC Droid DNA] Gorilla*:
Yep yep. I think we located the problem
[HTC Droid DNA] crpalmer:
Unfortunately, I really can't reproduce this. I haven't had a single crash with the new display changes.

Is there anything special about your charger? Original wall charger? I've tried turning the display off and on repeatedly when plugged into my laptop, wireless charger and wall charger and nothing ever crashes.

Can you try this kernel and let me know if it happens to fix it? I pulled some small changes from CAF related to how the clock are set. Nothing in there looks like it should fix the problem, but you never know....

Version 2.0.38-cm8
[HTC Droid DNA] Evilmonstertruck:
Are you undervolted or overclocked at all?
[HTC Droid DNA] crpalmer:
[MENTION=2793130]jbarcus81[/MENTION] isn't even running my kernel (using the one from the cm 10.1 build) so he is definitely not undervolted or overclocked.
[HTC Droid DNA] Evilmonstertruck:
Sorry. my bad, didnt realize that.
[HTC Droid DNA] jbarcus81:
Stock charger/cable.. Will test this and let you know.. give me just a bit, I work from home and it's kinda busy today.. But I'll get it..
[HTC Droid DNA] KyJelly69:
Then why are we having this discussion here?
[HTC Droid DNA] jbarcus81:
I'm rebooting [MENTION=3857343]crpalmer[/MENTION] ...

And please.. Not this crap again.. Just let it be? It's a discussion I've been having with crpalmer...

//\\

Still doing the same thing.. I flashed everything before initial boot.. I'm going to leave it unplugged and see what happens.. see if the same thing happens while not charging..

//\\ Same results while unplugged...
[HTC Droid DNA] crpalmer:
As in that didn't fix anything?

Want to try one more test kernel?

Version 2.0.38-cm9
[HTC Droid DNA] jbarcus81:
Sure.. No fix... Flashing new kernel..

//

After flashing that kernel... I think you fixed it!!! I can't replicate it now!!!!!!!!!!!!!
[HTC Droid DNA] Gorilla*:
Sweet. Now I can use Palmers newest kernel if jbarkus confirmed its working.. Now does anyone know the latest sm build that's stable ? I heard the build today still has broken SMS/mms
[HTC Droid DNA] jbarcus81:
Yeah, I think it's fixed now.. I'll confirm with [MENTION=3857343]crpalmer[/MENTION] so we can move back over to the right department for the rest... ;)
[HTC Droid DNA] KyJelly69:
Then maybe you should be using pm instead posting all this off topic stuff. Or perhaps discuss it in the cm thread where it actually belongs.

You can't have a "discussion" in a public forum and expect to be afforded the rights of privacy.

And don't tell me you don't want to hear it. How many times have we had these threads cleaned already?

If I have to follow the rules then everyone else does to. And I will reply to whatever ridiculous comment you make next. How bad do you want to feed the troll?
[HTC Droid DNA] -DroidIsDNA-:
Palmer helps develop cm with chad. This an experimental kernel for said ROM. Also, its a DEVELOPMENT forum which they are doing...Its none of your business, its Palmers, and he doesn't have a problem with jbarcus, oh, just confirming a fix. What have you done? If you have something useful to say, do it. Since you don't, just let the people actually helping talk. Thanks!

Looking forward to the merges guys, thanks palmer for your hard work and jbarcus for the endless testing with the tooth pain :)
[HTC Droid DNA] jbarcus81:
It's been fun..
[HTC Droid DNA] djh816:
Clean up your posts everyone.. this is starting to look like the Rezound forum...Keep the drama in PMs.

Thanks for the fix cpalmer, confirmed no screen of death here :)
[HTC Droid DNA] crpalmer:
[MENTION=2793130]jbarcus81[/MENTION] was very helpful in installing test builds of my kernel to hopefully resolve a problem that several people were seeing. It was a very productive.

Everyone, please ignore off topic inflammatory posts so that we can continue good development here.
[HTC Droid DNA] crpalmer:
New release:

Version 2.0.39-cm1: July 12, 2013: Linux 3.4.52

* Updated clock code from CAF

* Do not let the video driver control our regulator (fixes crash when turning device on?)

* Fix vsync timing issue

* Regulator / voltage / frequency tweaks (closer to CAF / stock)

Please do not use yesterday's test version any longer.
[HTC Droid DNA] KyJelly69:
Omnomnom, fed.

I would agree, if it were a kernel issue. It, however, is not. Why is that so hard to understand? crpalmer does not make the rules for this forum. This is off topic for this thread. Simple. No matter how much you don't like what I have to say.
[HTC Droid DNA] crpalmer:
Please try to be factual when you're trying to make a point. This is the *kernel* commit in my github that we were testing yesterday:

https://github.com/crpalmer/dna-kernel/commit/bd135774775dcdc5913b645288adaf47a015d7a6

Now please stop this thread of conversation.
[HTC Droid DNA] Gorilla*:
Yum... By tonight I will be running palmers latest kernel with today's build of cm10.1 if fly half sneaks a build out today with the commits to fix SMS/mms..

Thanks Palmer. <3
[HTC Droid DNA] 123421342:
Thanks for fixing the issue so quickly crpalmer:good:
[HTC Droid DNA] -DroidIsDNA-:
Palmer, I am not seeing /sdcard/crpalmer-cpufreq-max. I see the min, governor, volt, and light sensor however, Is there a reason? I would like to set settings on boot and not use a cpu tuner anymore :) I know how to do the adb su -c echo stuff, I just don't see it >:(
[HTC Droid DNA] crpalmer:
It doesn't get created by the kernel, you have to create it....
[HTC Droid DNA] armydog13:
I have had a couple random reboots with screen off. last _kmsg looks like it just powered off. Idk. Here's the last one http://db.tt/NZsgOliz
[HTC Droid DNA] crpalmer:
Are you using 2.0.38-cmX? That looks like the screen on crash that we were debugging here and that should be fixed in the latest version.
[HTC Droid DNA] armydog13:
Running 2.0.34-cm2 haven't updated my kernel because I am running carbon which hasn't been updated to the latest cm fixes

---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------

Wasn't sure the newer kernel versions would work
[HTC Droid DNA] crpalmer:
Are you under volting? That's the most likely cause of a log like that (other than a problem introduced in the last major set of display changes, which is after the version you are running).
[HTC Droid DNA] jbarcus81:
Copy that...

Makes sense.. thanks for doing it!!
[HTC Droid DNA] crpalmer:
Mostly Chad's work though. He's doing great things for the CM port!
[HTC Droid DNA] jbarcus81:
This is true.. very true..
[HTC Droid DNA] crpalmer:
What exactly are you looking at? I don't see anything that controls things like force fast charge.
[HTC Droid DNA] mopartonyg:
CR its in settings right above above phone. Performance control for cpu and stuff.
[HTC Droid DNA] crpalmer:
Yeah, that's the performance menu, but in there I just have Processor, I/O scheduler, Memory management, 16bit transparency, Surface improvement. Nothing about fast-charge.
[HTC Droid DNA] mopartonyg:
I am on Pac in my performance menu at the top there is cpu settings which shows cpu stats and if u scroll the whole screen to the left I get advanced settings and the fast charge is about half way down.
[HTC Droid DNA] crpalmer:
Glad to hear it works on PAC. :)

I'm running CM10.1 and that's something that they must have added in PAC... I suspect that either the PAC ROM has a script that controls this by default or it 's not reporting it correctly. Can you do:

adb cat /sys/kernel/fast_charge/*

which is what the kernel really thinks are the settings.
[HTC Droid DNA] mopartonyg:
not getting a response, maybe user error. if I enable fast charge it will not connect to my computer
[HTC Droid DNA] pio_masaki:
No

No Port

Discharging

0

No

It can be toggled in trickster mod though I doubted it did anything if it wasn't added to the kernel.

Tapatalked from my HTC DNA - ReVolt
[HTC Droid DNA] brennam7:
There's a fast-charge toggle in kernel tuner? Is that what were looking for?
[HTC Droid DNA] pio_masaki:
Not really if its there, just if its doing anything if it is there. I know it shows up on this kernel on revolt in trickster.

Tapatalked from my HTC DNA - ReVolt
[HTC Droid DNA] 123421342:
adb cat /sys/kernel/fast_charge/* does not work it just gives me the list of valid options(ubuntu 13.04). I did a logcat just for kicks and I notice that I get

W/GoogleAnalyticsTracker( 6173): Problem with socket or streams.
W/GoogleAnalyticsTracker( 6173): java.net.ConnectException: failed to connect to www.google-analytics.com/127.0.0.1 (port 80): connect failed: ECONNREFUSED (Connection refused)
W/GoogleAnalyticsTracker( 6173):	at libcore.io.IoBridge.connect(IoBridge.java:114)
W/GoogleAnalyticsTracker( 6173):	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
W/GoogleAnalyticsTracker( 6173):	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
W/GoogleAnalyticsTracker( 6173):	at java.net.Socket.connect(Socket.java:842)
W/GoogleAnalyticsTracker( 6173):	at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
W/GoogleAnalyticsTracker( 6173):	at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
W/GoogleAnalyticsTracker( 6173):	at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
W/GoogleAnalyticsTracker( 6173):	at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingHits(Unknown Source)
W/GoogleAnalyticsTracker( 6173):	at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
W/GoogleAnalyticsTracker( 6173):	at android.os.Handler.handleCallback(Handler.java:725)
W/GoogleAnalyticsTracker( 6173):	at android.os.Handler.dispatchMessage(Handler.java:92)
W/GoogleAnalyticsTracker( 6173):	at android.os.Looper.loop(Looper.java:137)
W/GoogleAnalyticsTracker( 6173):	at android.os.HandlerThread.run(HandlerThread.java:60)
W/GoogleAnalyticsTracker( 6173): Caused by: libcore.io.ErrnoException: connect failed: ECONNREFUSED (Connection refused)
W/GoogleAnalyticsTracker( 6173):	at libcore.io.Posix.connect(Native Method)
W/GoogleAnalyticsTracker( 6173):	at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:85)
W/GoogleAnalyticsTracker( 6173):	at libcore.io.IoBridge.connectErrno(IoBridge.java:127)
W/GoogleAnalyticsTracker( 6173):	at libcore.io.IoBridge.connect(IoBridge.java:112)
W/GoogleAnalyticsTracker( 6173):	... 12 more

I realize my adblocker is redirecting it to 127.0.0.1 but I was wondering if there is a way to find the origin of this? On another note, you reduced the power consumption of the kernel by 40%(gsam battery stats now shows my screen as taking 25-40% of the power as opposed to 5-10)! Great job!
[HTC Droid DNA] jonesin:
U know what 127.0.0.1 is right?
[HTC Droid DNA] 123421342:
Yes thats why I mentioned it. Its failing because it will obviously not go anywhere. I was asking if I can find the source as in- what app is causing it.
[HTC Droid DNA] crpalmer:
Right now, you have it turned off (the 0 is 0 == off, 1 == on, 2 == on but only if there is no usb device attached).
[HTC Droid DNA] amit_sen:
Working really smooth :thumbsup

This is the first/experimental version, cant imagine what u will comeup with after a few iterations.

Kudos bro !!
[HTC Droid DNA] skynet11:
It works so far on TheDanimal's AOKP build, though I haven't really messed with any of the settings.
[HTC Droid DNA] waxta:
Is the download link down? I am getting page not found.