yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] santod040:
Not currently, no.

This one is for jelly bean 4.3 sense 5.5.

The one linked to in the post right above yours should.
[HTC Droid DNA] santod040:
UPDATED for KitKat!

OP updated with new stock builds based off o official sources, for kitkat based Sense and GPE based roms.

No real extra features just yet, this is just the first version and intended to be very stock.

Mainly just removed Perf Lock for now.

Will be adding new revisions with more features as time permits... :good:
[HTC Droid DNA] jamiethemorris:
[MENTION=1331268]santod040[/MENTION] since it appears HTC did not included a defconfig or a config.gz, what did you use? Do you think you could send me your .config?
[HTC Droid DNA] santod040:
It's in there, it's the apq8064_defconfig.
[HTC Droid DNA] jamiethemorris:
That was quick! Don't know how I missed that... Right at the top of the list. Thanks!
[HTC Droid DNA] santod040:
No problem. :)
[HTC Droid DNA] santod040:
UPDATED!

v2.0 posted​

Compiled using official kitkat sources

Wake features added

Governors added

Compiled with SaberMod 4.7.4 custom toolchain

​
[HTC Droid DNA] iHateWebOS:
What did you merge for this? Ya got one commit that changes 89 files and deletes 54. Try n do one change per commit so you can follow your changes better, and isolate issues those changes may cause.

Edit: just realized this may have come across as rude. Didn't mean any [emoji7]
[HTC Droid DNA] santod040:
The commit does not really include a whole lot and is fairly straight forward I thought.

I made local changes which added governors and wake options.

In that commit, 89 files were changed or modified and 54 deletions were made.

A deletion doesn't mean a whole file, it can be as little as removing ; from a line. That is one deletion.

Once the changes I wanted to make were done, I compiled and committed.

Sorry, not everyone will like my Git repos.

If it's a problem, I don't mind closing the thread.

It's certainly not necessary that I make and post kernels.

Just thought Id share what I made for myself to use.
[HTC Droid DNA] BBEgo:
You do great work [MENTION=1272062]santod[/MENTION], and we appreciate it.
[HTC Droid DNA] iHateWebOS:
Being ignorant is not necessary either. No offence was intended at all. GPL compliance is met with your commit. It's just not good practice to make squashed non credited commits. I didn't mean to offend you, but to be honest your sensitivity offends me. I wouldn't suffer at all from you pulling your kernel, Just your loyal followers would. Now then, let's ignore me and carry on with our lives.
[HTC Droid DNA] santod040:
Wasn't trying to be ignorant or sensitive. :(

It was an honest, from the heart response.

Please see my apologies from the original OP, which is now in post#2 regarding my Git Repos.

I know that my methods aren't the most preferred or desirable for other devs.

If my commit history bothers folks or is going to create issues, I'd rather not have it posted is all.

Basically my point was, if there is gonna be drama from me posting a kernel, then I won't post it.

Pulling it wasn't meant as a punishment to anyone, but rather me stating I do not need or want issues over it and if it is going to cause any, then I have no problem taking it down to avoid said issues.

Not sure what you wanted me to say or how that was taken as being ignorant or sensitive.

One thing I can say for sure though, as a Dev, I never tell another one how to do what he chooses to do.

Maybe in a PM, if I feel it's super critical or poses a threat to users devices in some way.

Although you choose to do so, I feel my answer was appropriate, sorry you didn't.

To each his own I suppose. Moving on now....? :fingers-crossed:

Feel free to PM me, if you feel this discussion should continue.
[HTC Droid DNA] iHateWebOS:
Moved on, just a miss understanding. The whole taking it down thing made me think you were upset by my comments, and I reacted as such. My apologies.... Hug it out?
[HTC Droid DNA] santod040:
Wifi N - 5Ghz - Feedback

If anyone tries this on my Sense 6 rom or GPE, and can test wifi n, please let me know if this alone fixes it for you or not.

Then I will know if I need to update some binaries in the rom for the next update.

Best way for me to test both right now.

Feedback is appreciated. Thanks! :good:
[HTC Droid DNA] Bsanborn:
5Ghz N Works now on your NuSense 6.0 Rom, but it seemed to have broke SMS. I can't send picture messages. It keeps failing.
[HTC Droid DNA] santod040:
Good to hear it fixes 5G.

My mms still work though, so that seems odd and likely unrelated to the kernel.

Thank you for the response, much appreciated.

That tells me it was kernel as we suspected earlier.

I was starting to wonder, now we know.

Sounds like the firmware I had in the rom was all good then. :good:

Thanks again and I hope you can resolve your mms issue.

Make sure you have the Messages set as default and I usually check auto-retrieve while roaming.

I don't know if that helps you any.
[HTC Droid DNA] Bsanborn:
Did you flash the new radio and firmware? That's the only other thing i could think of that would have caused the MMS issue.
[HTC Droid DNA] santod040:
Yes I am running latest firmware,radio,hboot...
[HTC Droid DNA] Bsanborn:
Is that the "nobootimg_firmware" one in the second post of the rom/radio thread? I thought you said we didn't want to flash the boot?

EDIT: Nvm, I got it. I had to set the max size to 1M. Thanks for the help.
[HTC Droid DNA] santod040:
hboot is not boot.img

If you are on NuSenseSIX and so am I, then we both have the boot.img from that rom.

We also both now have the kernel I posted here from official sources.

The hboot is the white menu loading screen you use for fastboot, etc,..

It is not the Ramdisk and kernel(boot.img)

The firmware does not contain a stock kernel(because I removed the secure one), it does contain the new hboot.

Ok cool, glad you got it worked out. :)
[HTC Droid DNA] IcyAgitator:
Nevermind lol
[HTC Droid DNA] santod040:
He figured it out, had to lower message size in settings.

I did this on the m7 as well and forgot to fix it back to Vzws limits on this one.

Set it to 1mb and you will have no problems.

I need to lower the sizes again and make 1200KB's the max size like Vzw permits, although it's working for me on 2MB's.

But their limit is 1200.
[HTC Droid DNA] IcyAgitator:
This kernel works on NuSenseSix Dna?

Which would be better for that rom; , stock or this one?

Thanks
[HTC Droid DNA] santod040:
Yes, the first post was updated with kernels based on new kitkat Dna stock sources.

I have stock based builds and one with features added.

Either one works just as well on NuSenseSIX.

Just depends on if you want the added wake features and extra governors or not.
[HTC Droid DNA] amathophobia:
Thank you very much [MENTION=1331268]santod040[/MENTION]. This kernel finally gives me working WiFi at home. Do you have any plans to add voltage control or OC?
[HTC Droid DNA] santod040:
Probably, I generally tend to try and stay close to mainline when I can, but it's definitely not out of the question to add some variables there.

Glad to hear it's working out and happy that HTC released sources so soon after kitkat release. :cool:
[HTC Droid DNA] nycqns983:
Does mhl work with this?
[HTC Droid DNA] santod040:
It should, if it works on the new stock kernel it should also work on this.

As this was compiled using the newly released kitkat sources for the DNA.

I have no means to test it though.
[HTC Droid DNA] ubigdumy:
I just installed this kernel on the new stock updated Rom and dt2w isn't working, anybody else having this issue
[HTC Droid DNA] santod040:
Did you enable it using something like Trickster Mod or another kernel control app?

It's not on by default. It's intended to be switched on and off.

In Trickster, it's under the specific tab > Wake controls
[HTC Droid DNA] ubigdumy:
My fault, I thought since sw2w was already working that it was already on. I,ve been on volume to wake for so long I didn't remember I could change settings.

Thanks for your work.
[HTC Droid DNA] xXminiWHOOPERxX:
[MENTION=1331268]santod040[/MENTION] , May help you with mostion gestures
[HTC Droid DNA] mr4r4n:
Now that the kernel will be from DNA sources will this resolve issues like hangouts and such in the other KK based sense Roms ?
[HTC Droid DNA] voxuanvy:
How to flash kenel for my HTC Droid DNA ? please
[HTC Droid DNA] santod040:
Put the kernel zip on your device

Boot to recovery

Locate the kernel zip to flash

Reboot

Profit
[HTC Droid DNA] voxuanvy:
Now, i see, thanks santod040 very much
[HTC Droid DNA] nycqns983:
Fantastic! Has anyone tried this on Viper?
[HTC Droid DNA] pyroguysf:
What happened to touch sensitivity? I have to smash the screen to get it to register any touch and half the time it still doesn't even respond, so this is completely unusable for me. I've tried the stock ROM you posted with it's included kernel, and I've tried all 3 posted versions of this kernel on the stock ROM, NuSense, and UnSense with the same results, all clean flashes. Any other kernel + ROM works perfectly fine (Sense or AOSP).

Something's definitely screwed up in the kernel, but since you've kept it stock that means it's probably a bug directly from HTC? I really don't want to go all the way back to S-On/locked to be completely sure though. Any ideas, or anyone else experiencing this?
[HTC Droid DNA] santod040:
First anyone has mentioned anything like that and I have not had any issues.

You may be dealing with hardware on its way out, I don't know.

But I definitely don't have any touch sensitivity issues and I believe this and the stock kernel are both just fine.
[HTC Droid DNA] pyroguysf:
I really doubt it's failing hardware seeing as I can flash anything else and it works 100% with the lightest touch, but as soon as I flash the new kernel it barely registers anything. I'm on your newest firmware too, FWIW. I remember there was something quite a while back where different screen hardware between devices was causing differences (I think it was with crpalmer's early kernels). I'm guessing it's something like that where it's only be certain panels affected.
[HTC Droid DNA] santod040:
That's possible.
[HTC Droid DNA] jamiethemorris:
[MENTION=1331268]santod040[/MENTION] it looks like you added some new drivers and some large additions to files I'm not familiar with in your most recent commit? Are those needed for the m8 based ROMs or something? I'm working on my own but I've only tested it on the stock ROM. Just wondering if I need anything else besides what comes with the stock kernel source to work properly on your ROMs.
[HTC Droid DNA] santod040:
You don't have to have the added wake features, extra governors and i/o schedulers.

Stock source and config works just fine.
[HTC Droid DNA] jamiethemorris:
Actually what I meant was that I saw some things like drivers/input/touchscreen/himax_852xD.c and I didn't know what it was for.

But if you say it will work just fine then than you, that answers my question. Does that include your m8 gpe port?
[HTC Droid DNA] santod040:
Yes, stock works for Sense 6 and GPE.

That touchscreen driver was actually for a different device/project I've been experimenting with.
[HTC Droid DNA] jamiethemorris:
Good to know. Thanks santod.
[HTC Droid DNA] Sutko82:
I am too having sensitivity issues. You have to really press hard when you trying or even using back button! This started when I flashed New kernel! I like the features but this lag unresponsivenes is bad [MENTION=1331268]santod040[/MENTION]

---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------

Typing****
[HTC Droid DNA] pyroguysf:
Also happens on the kernel iHateWebOS just posted too, so I'm assuming it's a bug introduced by HTC :(

I'm no dev or anything, but besides a driver issue, isn't there a value that sets the voltage for the touchscreen that may have been lowered? I doubt it's that, but I'm just spit-balling. Going to try to see what HTC support says.
[HTC Droid DNA] BBEgo:
I too am seeing the reduced sensitivity of the buttons. It's not too big of a deal, but I do have to press MUCH harder to get it to respond.
[HTC Droid DNA] jamiethemorris:
I noticed the back button thing as well, I'm not sure why they did that but I noticed if you press it a little higher up it feels a little bit better.
[HTC Droid DNA] pyroguysf:
Mine's completely unusable. No matter where I tap, the back button works about 1% of the time. Pretty much anywhere else it's about a 65% chance my touch will register when I mash the screen, and swiping is impossible since it loses my touch before I can complete enough of a swiping gesture. On any other kernel, the screen is sensitive enough to register a tap with my finger just barely hovering over the screen. Seems like it's a bit worse for me than others.
[HTC Droid DNA] iHateWebOS:
The kernel of mine you flashed was a test kernel from yesterday. I accidentally uploaded it. Its bone stock with just over clock and voltage control. Neither of those changes affect sensitivity. Your mystery continues.
[HTC Droid DNA] pyroguysf:
Good to know, thanks. Seeing as there's a handful of people with the problem now, and it's consistent and exclusive to the new kernel while anything else works 100% as expected, it looks like it's a bug from HTC. I'm assuming it's only affecting a certain display panel, since I know there's been more than one.
[HTC Droid DNA] seeingwhite:
Voice input with google now and regular keyboard voice are not working. Doesn't seem like the mic is on at all.

Also, the speaker output in Google Hangouts is severely distorted... almost like it is being overdriven, but it does it through both the speaker or headset.

Running InsertCoin sense 6. Thanks for all the hard work!

BTW, touch sensitivity is fine for me with this Kernel.
[HTC Droid DNA] santod040:
Any sound issues would be Rom related.
[HTC Droid DNA] seeingwhite:
Ok, thanks santod. The dev originally replied that it was kernel related. Thanks for clarifying, guess I'll have to switch ROMS then.
[HTC Droid DNA] alejobog:
edit.
[HTC Droid DNA] santod040:
Yes it certainly did. Those guys are great!

Motion Gestures are now enabled for my m7vzw version of NuK3rn3L and NuSenseSIX rom.(not for the Dna)

I will look into adding it here next... :good:
[HTC Droid DNA] zou14:
Can you share the VOIP fix ?

Thanks
[HTC Droid DNA] santod040:
VOIP was an issue with roms audio files and libs, wasn't really kernel related.

Not every rom is gonna have the same wrong files either, so fix may be different for one then it is another.
[HTC Droid DNA] xXminiWHOOPERxX:
Thanks for responding. Didn't know if you seen it so I had to show you. And with how everyone sees you as a saint here I'm sure you'll get it on the DNA :) patients is the key to success.
[HTC Droid DNA] rayjr13:
Indeed! fail on the first one gotta keep the warm bodies coming

Thanks santod gonna try it out on NuSenseONE-Max-dlx_RC2.0_011814
[HTC Droid DNA] alejobog:
Since installing this Kernel, will I damage the phone sound is heard very bad, I'm using the rom NUSenseSix to solve install the ROM again and reestablished all, full clean sound and is corrupted,

any help?

install other ROMS and still sound bad.

Before NUNSENseSIx worked perfect with the ROM
[HTC Droid DNA] santod040:
Not sure I understand.

This kernel works fine with NuSenseSIX and sound is fine also.

If you are having issues, make sure your radio and firmware are up to date.
[MDA III, XDA III, PDA2k, 9090 General] zebra:
Sorry if this is a faq, but searches don't turn up anything.

I now have a Sony Ericsson K750i as well as an XDA IIs. I carry most of my MP3 music for the XDA on SD cards, but it would be nice to transfer a selection to the Memory Stick Pro Duo card in the K750i while on the road.

Is there an adapter I can use for this, which would be simplest, or (thoughts) both have infa red and both have bluetooth ... but how do I make it work. Thanks.
[MDA III, XDA III, PDA2k, 9090 General] Stabilo:
23 in 1 card reader

Paid £15 incl delivery from Far East on Ebay for a 23 in 1 card reader. It takes CF MD SD MMC SM MS & Memory Stick Pro. Also is a one to three port USB hub.

Just remembered £15 was for 2 units not 1.
[MDA III, XDA III, PDA2k, 9090 General] zebra:
Thanks. But I have a card reader. The problem is I need a PC to transfer the files from one card to another, don't I? But I want to do it on the road. Meanwhile have managed to make transfer using Bluetooth on the two phones. Not fast, but it works. Thanks and cheers. A
[Verizon Samsung Galaxy S III] RBarnett09:
I recently came off of the MB1 radio to the newer MF1 radio.

Has anyone been using the new ML1 and compared results of which radio receives the best reception?

I know it may very by geographic location but am interested in what others find.
[Verizon Samsung Galaxy S III] MrBrady:
Both seem the same to me. The biggest difference I noticed is ML1 drops down to 3G much more often. I almost never saw 3G with MF1 as it would stay in a low 4G instead. I'm guessing they opted to drop down to 3G for a better user experience if it was stronger than a weak 4G.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] RBarnett09:
This would also improve battery life... makes sense.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I really don't see any difference and I am on my phone heavy every day from morning to night. I also don't travel much outside of the normal work, shopping, mall, etc areas by me in NY. Furthermore, 4G is very prevalent in my area. I am rarely on anything less than 4G and even in my home, I have 4-5 bars of 4G at all times. #LoveMyBigRed :good:
[Verizon Samsung Galaxy S III] Lord_Tardis:
Do not use ML1 unless you go to a touchwiz 4.3 rom. If you are staying on 4.1.2 or AOSP stick with MF1. If you go to the touchwiz 4.3 you will need the ML1.
[Verizon Samsung Galaxy S III] RBarnett09:
I'm on AOSP 4.4.
[Verizon Samsung Galaxy S III] Lord_Tardis:
Then stick with the MF1 unless you notice connection issues. I was on Nottas PA 4.4 with MF1 and it was great.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I'm sorry but you really don't know what you are talking about. You could use the ML1 modern on a 4.1.2 ROM if you wanted. That's OK. What you should NOT do is use an older modem on a newer Android Version (e.g. MB1 on 4.4).
[Verizon Samsung Galaxy S III] twistedillutions:
Im in Cen-Cal i was on ML1 i didn't notice a difference fone still rang mms still went out my status showed the same signal numbers
[Verizon Samsung Galaxy S III] beepea206:
Agreed about the similar performance. Except LTE is a more efficient protocol than CDMA is... however if there's a low LTE signal and the phone is smart enough to stop trying to ping the LTE band, that could save some juice. The constant polling and searching, be it data to wifi, drains the battery more than a constant or static location connection.
[Verizon Samsung Galaxy S III] jamesn2k:
Speaking from my own experience my ping time on speed test have improved drastically. Call quality is a bit better as well. I still get the same speed test results ranging from 25Mbps down to 72Mbps down. Text are sending and receiving a bit faster as well for me.
[Verizon Samsung Galaxy S III] RBarnett09:
On MF1 or ML1?
[Verizon Samsung Galaxy S III] jamesn2k:
ML1, I ota'd so I'm running the whole new sha'bang.
[Verizon Samsung Galaxy S III] Sean Z:
Hi guys

So from what I've read on this thread, it seems that you have an option of either MF1 or ML1. However I think I have both? I'm such a noob at this. Here's a screenshot. And just to confirm, MF1 gives a better reception/call quality?
[Verizon Samsung Galaxy S III] BadUsername:
You have mf1.

The build number is simply the name of the rom, the developer put the base it was built on in the title, which is ml1.

Your baseband says what you're currently running, which is mf1.

Radio choice is subjective, if you're getting poor reception on mf1 try flashing the ml1 radio and see if it improves. It's reported to improve signal specifically on a ml1 base.
[Verizon Samsung Galaxy S III] Sean Z:
Thanks man!
[Verizon Samsung Galaxy S III] beepea206:
+1.

I haven't seen any improved reception with ML1, but each device is different and it's really subjective, so you may find it performs better than MF1 does.
[Galaxy Note II Q&A, Help & Troubleshooting] keith456:
hi i'm helping a friend upgrade his telstra galaxy note lte to 4.3

how do i use odin is there like a how to thread ?

what rom should i use to get a full generic experience and is safe to flash on this version of the galaxy note 2 ?

in the likely event of the device not flashing properly or getting bricked /soft bricked how do i recover the device ,(any how to thread ?)?

i'm new with samsung devices so i am sorry if my questions sound dumb

thanks
[Galaxy Note II Q&A, Help & Troubleshooting] Spitwista:
The easiest and safest route to root, get recovery and rom is to use a toolkit(search on xda mskip made a good one) or you can follow one of Dr. Ketans very easy and helpful guides.
[Galaxy Note II Q&A, Help & Troubleshooting] keith456:
not after root or custom roms , i am trying to manually upgrade the phone via odin as the update is not available on telstra version of the phone .... the reason i have asked is because i have read things dont update properly etc
[Galaxy Note II Q&A, Help & Troubleshooting] :
If you just want to update go to sammobile and download the appropriate firmware for your model/area and flash as pda with odin. I think you have to install the drivers first so either install kies or you can use the toolkit all ready mentioned. If you need any guides then Dr ketan is the person so search for. He has written a guide on everything note 2
[Nexus 7 (2013) Q&A] Mosharraf29:
I have searched the entire forum for the similar problem i am facing but couldn't find any and had to write to you in private.

I have bought my device 3-4 months ago from Bangladesh and cant claim any warranty or replacement. My device screen is flickering more often day by day at the bottom right corner. Its like a screen shot of the top or any other portion of the tab that is flickering at the bottom right corner. I tried the brightness issue, didn't work. Then I factory reset my device thought might be a bug but still no luck. Now i am worried whether this is a hardware problem or not. But i never dropped the device. So shouldn't be one.

I recorded the problem with my mobile to be more precise. Video attached herewith in zip file.

I would be really grateful if anyone can help me out with a solution.

Thanks.
[Nexus 7 (2013) Q&A] Abel669:
It seems like your CPU/GPU is burning out... I had the same problem when over clocking my old Galaxy Ace..

The problem may not be the same, but its all I can think of.

EDIT: it could possibly be because the ribbon cable that connects the Screen to the MoBo is loose?
[Nexus 7 (2013) Q&A] Mosharraf29:
Ribbon cable...i thought of that too...hope that is the prob..it shouldn't be a great problem then. What if CPU/GPU is burning out...what will be the solution then? Thanks for your reply though.:good:
[Nexus 7 (2013) Q&A] Abel669:
If the ribbon cable is loose, power off you device and pull the back cover off and have a look.

If the CPU/GPU is burning out, the only thing I would suggest would be a moderate under clock of both units and pray that your device will last, alternatively, throw your device at a wall to preemptively break it before they do die and your device becomes a really crappy decorative ornament.

Seeing as you cannot get a replacement, your only option is to try and keep it from happening by any means.. It is only a matter of time.

OR,

I'm wrong.
[Nexus 7 (2013) Q&A] Mosharraf29:
Last night i showed my device to a professional and as this device is not much available in Bangladesh, they are not expert enough. Though he suspected it might be the cable issue but he cant be sure. He might get it right if he gets another same device to test. So m left with very few options :crying:. I got to wait for the parts to be available or i got to contact the Asus product importers but fingers crossed. Disappointing...its just a couple of months and lot of money for me.

Anyway...thanks for all the help and support. Appreciate it.