yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] eriknors:
As a matter of fact I did flash back to stock in-between flashing both kernels and that's y I posted what I posted.

I try not to come on here and post anything not worth sharing. If I do something wrong and I am getting errors I know its my own stupidity and its irrelevant to any development.
[HTC Droid DNA] dsb9938:
Two things make all cores stay on. You told them to in some app, or you flashed a different kernel after the non-stock Cubed without restoring stock.

That's it.

D

.
[HTC Droid DNA] eriknors:
Okay then if an app set it for me would u be able to tell me from my kmsg? (Just for kicks I went ahead and reflashed stock kernel then reflashed this one and I'm still having all 4 cores actively running.

Cubed stock

Ondemand

Cfq

Max and min at 1.512 (in no-frills app) in system tuner it shows min384 max1.512

Only other modification I've added was v6 script to adjust oom but just looked and the script hasn't ran due to the kernel changes I've made.(flashing)

Here's my kmsg as well

http://db.tt/6InOlNuU

Hope this info helps
[HTC Droid DNA] elkay:
If you set max and min both at 1.512, doesn't that effectively disable throttling? If I'm understanding you correctly, I think that's your problem. I don't think it's based on core utilization alone and it's not going to power down a core that hasn't been throttled down to a lower state. I could be wrong, so take it as hearsay without confirmation from dsb, but how I explained it makes sense to me and maybe it's something to try until he jumps in to correct me lol.
[HTC Droid DNA] eriknors:
I'm not setting it at that I think no-frills is just showing it incorrectly.
[HTC Droid DNA] elkay:
Gotcha. I was probably wrong anyway lol.
[HTC Droid DNA] dsb9938:
And where did you get the "stock" one you flashed? did you flash the modules file that goes with it?

D

.
[HTC Droid DNA] elkay:
People seem to miss that one a lot, huh?
[HTC Droid DNA] dsb9938:
That, and they think they can just flash any copy of a "stock" kernel they find, as opposed to the specific package in the other thread, like they are supposed to.

D

.
[HTC Droid DNA] eriknors:
I got it from this op and yes I flashed the modules.

---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------

This isn't my first rodeo.
[HTC Droid DNA] dsb9938:
Oh, I'm so glad I waited a few seconds to reply. So I could know it wasn't your first rodeo. That helps so much.

THERE IS NO FILE IN THIS THREAD.

Soooooo . . . .

I have no idea what you did. And I just stopped caring.

Have a nice day.

D

.
[HTC Droid DNA] orangechoochoo:
Just to be clear, you flashed the return to stock kernel and modules posted in the OC kernel thread, and then you flashed the writeable kernel and modules?

If you didn't flash the return to stock files then this stock writeable kernel will have issues. If done right the stock writeable kernel has absolutely no issues because the only thing changed was the ability to write to the system, that's it, so it should behave normally otherwise.
[HTC Droid DNA] orangechoochoo:
The other cores occasionally come online, are they all locked together?
[HTC Droid DNA] eriknors:
Yes they are all locked at 384. I was poking around my system files and I'm curious can a script that's in the init.d file that was put there by the rom developer over ride kernel settings? If so that may be my problem

---------- Post added at 09:34 PM ---------- Previous post was at 09:30 PM ----------

I just d/l the new codis rom so I'm gonna flash that and see if this issue persists
[HTC Droid DNA] bakemcbride21:
This may or may not help...but from my experience on my phone, switching and upgrading back and forth with so many kernels, even with flashing the stock modules first then flashing the sotck boot img and then the stock modules again, I have found better and more consistant performance if I mount system in recovery before flashing any modules...

in theory you shouldn't have to i think...but I would get REALLY odd behavior switching kernels prior to using that method.
[HTC Droid DNA] spinkick:
What's the best way to clear kernel settings?

I flashed your back to stock boot image from your other thread

Then flashed the modules in the back to stock file

Rebooted

Flashed this stock but writeable boot. Img

Flashed the modules.

Cores are all online in system tuner. Could I have missed something?
[HTC Droid DNA] madAdam6LOVE:
I noticed the exact same thing here.

Then I installed UKB 1.3 after a full wipe. Flashed the Stock Writable modules. Now cores are going offline.

Maybe it was the full wipe that did it.
[HTC Droid DNA] spinkick:
It has to be that..

I just flashed back the back to stock modules and boot.img, and still cores are online. So something else is amiss.
[HTC Droid DNA] spinkick:
Flashing back to the custom kernel fixes the sleep problem, but I'm stuck on it of course. Just for info purposes
[HTC Droid DNA] hkbladelawhk:
Random ??. I saw on the UKB thread that this supports init.d. Is that correct? I ask because I'm having the issues mentioned with volume wake and deep sleep using this. Trying to avoid the ukb kernel due to no system write (?).
[HTC Droid DNA] madAdam6LOVE:
This kernel is perfect with UKB. Writable. Volume wake works. It is rock solid. Not a single freeze or reboot.

Be sure to flash the modules after flashbooting the boot.img.
[HTC Droid DNA] hkbladelawhk:
Hmm, Volume Wake never works in DS.
[HTC Droid DNA] Papa Smurf151:
I have cleaned up this thread a little. Lets all try to be polite and get along. I dont mind cleaning here and there but going at each others throats is not gonna help the development of this kernel one bit
[HTC Droid DNA] elkay:
Amen and thank you!
[HTC Droid DNA] hkbladelawhk:
Edit. Reread back. And confirmed to try a full wipe.
[HTC Droid DNA] jdec529:
when returning to dbs stock, i seen a file to flash first. do i have to extract the boot, and flash modules with that, or just flash the zip. Thanks
[HTC Droid DNA] elkay:
There are two files in the zip. One is the boot.img to flash with fastboot, the second is the modules zip file that you need to install from recovery.
[HTC Droid DNA] jdec529:
That's what I thought. Thanks!

VENOMIZED DNA
[HTC Droid DNA] Jorry:
Flash this kernel on to of Cubed custom kernel

I'm currently on Cubed Kernel 2.4.2 and want to flash this kernel but I have seen in first post to flash a 'Return to Stock' ZIP first. Is this still valid? Where I can find it? Thanks.
[HTC Droid DNA] elkay:
First post on the other Cubed thread.
[HTC Droid DNA] -4ndr01d-:
I am positive that I installed cubed 2.4.2 after running cubed stock.

After weeks of using and having the random reboots and SODs I decided to come back to cubed stock.

I am positive that I did not flash this "return to stock' file... I simply just pulled the boot.IMG, and flashed via fastboot... went into recovery and flashed the modules

everything is and has been running fine since.

But if the DEV says do it...do it! I just overlooked it lol
[HTC Droid DNA] elkay:
This can cause problems with WiFi and CPU throttling. Maybe it somehow is working for you, but dsb's procedure involves installing the back to stock modules zip and I would listen to him.
[HTC Droid DNA] elkay:
Guy and gals,

I've been able to take dsb's source for this kernel and compile it with the source patch added by me for the msm_hsic_host fix for the wakelock battery drain on this kernel. HTC's kernel has the bug, too, so it's nothing dsb did wrong, in fact it's the same fix that dsb put in the full Cubed kernel. Going to run it for a few days and see how it goes. As long as dsb is ok with it, I'll post it in a few days if all works out. This will be a great test to see if the HSIC wakelock fix is causing the SODs. Hoping (REALLY hoping) the SOD isn't due to the fix. Will keep you updated.
[HTC Droid DNA] orangechoochoo:
Can't wait to hearthe results!
[HTC Droid DNA] ML417:
just want we needed, someone who understand how to write this stuff to do it instead of dsb who is currently sick. I hope he doesnt mind either
[HTC Droid DNA] elkay:
There's no replacing dsb. He's a wiz with this stuff and I'm hoping as much as everyone else that he gets better soon.
[HTC Droid DNA] spinkick:
How is it running so far? Did you have to push the modules for stock or just the cubed stock ones again?
[HTC Droid DNA] elkay:
No crashes so far, but I only got about 1 (sometimes 2) a day on the full Cubed. Will take a couple days of use for me to be able to say it's likely working without SODs. The modules are also compiled by me, so the install method will be the same as doing dsb's from scratch (boot.img via fastboot and modules zip file from recovery). That also means you'll need to install dsb's "return to stock" module zip from recovery first if you're on anything that's not stock.
[HTC Droid DNA] spinkick:
Cool. Do the power savings seem intact?
[HTC Droid DNA] elkay:
Unfortunately, the DNA is my current phone and I've had a bunch of calls and texts over the past few hours, so I haven't been able to test the standby much at all yet. No crashes, though.
[HTC Droid DNA] spinkick:
PM me if you need another tester!
[HTC Droid DNA] elkay:
Left my DNA unplugged overnight on my customized kernel while I slept.

No freezes/crashes/SODs since I flashed it yesterday. Still needs a bit more testing on my end before I'm confident it's clean, though.

:)
[HTC Droid DNA] orangechoochoo:
Can you make an overclock version too?

Btw, how's the work coming along on the CM kernel?
[HTC Droid DNA] scumpoop:
I too would like to test! :)
[HTC Droid DNA] elkay:
The end goal would be to include that, too. My primary focus is absolute stability, so overclocking won't be coming right away (but it will be on the short list). Since I'm going to have to follow the GPL in order to provide the kernel to you guys, I'm going to go official and set it up on github which might take a couple days since I'm also busy with a few real life things at the moment, too. I'm going to be splitting off from this thread for the release since it won't be this "stock" kernel anymore and I'm getting dsb's ok to include his system write patch in it. Between getting the source on github and ensuring that I've tested the stability thoroughly myself, I'm going to say probably Friday I'll start the new thread with my kernel ready for download.
[HTC Droid DNA] spinkick:
Gimmie!!! :)
[HTC Droid DNA] calbruc:
Elkay - Any plans to enable quick-charging?

That would kick all kinds of ass.
[HTC Droid DNA] spinkick:
That would be awesome
[HTC Droid DNA] elkay:
That will be on the list, too. Like I said, one thing at a time. My main concern is stability so things will be put in and tested one by one.

I had a little extra time so the github is already set up and I have the build ready to go. No reboots or lockups in 2 days and I was at 50% battery after 20 hours unplugged, 6.5 hours while I was sleeping and the rest was a normal day of usage for me.

I won't be around most of tomorrow evening, so I'm pondering whether to release tomorrow or not. There's nothing crazy to support, so I might. It flashes/installs the same as this kernel and I'm fairly confident in the stability at this point.
[HTC Droid DNA] madAdam6LOVE:
Coming from this kernel, will we need to flash Back to Stock before flashing yours?
[HTC Droid DNA] elkay:
No, only from the full Cubed. There is a modules zip file with my kernel, too, but it's the same files touched as this one so you can just simply flash my zip over this one.
[HTC Droid DNA] abn.geek:
You can't say something like that and then leave us all drooling for a few days, you cruel, heartless man.
[HTC Droid DNA] rajuabju:
1) I am VERY excited for this

2) Have you obtained DSB's permission? If not, you should, prior to posting anything.

3) Did I say how excited I am about this? VERY.
[HTC Droid DNA] orangechoochoo:
Just release it, no one is going to take your beer if the phone gets bricked.
[HTC Droid DNA] spinkick:
+1,im sure dsb would not mind and would actually appreciate it
[HTC Droid DNA] trebb:
What exactly is causing the msm_hsic_host wakelock issue? Just curious.
[HTC Droid DNA] iOSh8er:
Get permission like you said earlier, its the right thing to do.

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] Danzoman:
Imho not releasing it is about $. Why would D do all this work for free,something that one of qualcoms engineers who probably makes a 6 figure income to steal and implement in a future ota. Make them fix it.

But at the end of the day I hope all is ok and we can benefit from this soon.

Via Viper DNA Beta
[HTC Droid DNA] elkay:
Bug in Qualcomm's code that was originally delivered to Google for the Snapdragon S4 Pro processor that is causing wakelocks on cellular activity. It's preventing the phone from going or staying in deep sleep, which is why "Phone idle" is so low in battery statistics. Qualcomm has since fixed it with a couple patches, but there's no word from HTC as to when (or if) we'll see the fix delivered via OTA. Most people think the standby battery life is good considering the size of the battery and they just don't know any better. The Nexus 4 is experiencing the same issue.

---------- Post added at 04:12 PM ---------- Previous post was at 03:58 PM ----------

It's not dsb's nor my patch. It's a patch directly from Qualcomm. You can't blame Qualcomm or Google at this point, either, as the fix has been accepted and merged into Google's repository. From this point forward, it's up to HTC to merge the patches into their source and deliver it to Verizon for testing, so the ball is now in one of their courts. I'm simply doing the latter part on my own with a custom kernel. dsb hasn't responded to my PM yet, but his repository only has the system write change in it and is otherwise the same as the kernel source that HTC posted for everyone to work off of, so in the end I don't think it will be a big deal that I forked from this kernel's source as long as I give him credit for the system write change. It only saved me the step of pushing the completely stock HTC source and then merging in his one system write change. If I took his Cubed kernel with all the mods he's already done to that one and tried to call it my own, that would be a different story.
[HTC Droid DNA] Danzoman:
Sorry I thought he personally fixed it. Never mind then lol :p

I wasn't insinuating you were stealing, but it wouldn't be fair for paid engineers to steal from someone that does this as a hobby.

Via Viper DNA Beta
[HTC Droid DNA] elkay:
Nope. A lot of the patches applied by devs for all of these Android devices are straight from manufacturers. That's the pro/con of an open source project. While the paid engineers occasionally benefit from the work of volunteers, us end users also benefit from the volunteers fixing problems that the engineers might have taken longer to fix on their own. Also, when the handset is not locked down, we can test and have these fixes before carriers push the updates through their lengthy approval process.

A small setback - my data connection dropped and I had to reset my phone to get it back. Apparently this has been happening with other kernels including those with CM10 on other devices, and those kernel devs are backing out their HSIC changes. I'm in contact with a dev that has the msm_hsic_host fixes in place and doesn't have the data drops, and he's saying it's because there are a few additional patches that have been released that those devs may not have applied that could be fixing that small data drop issue. Rather than revert (no point as that's my only real change so far) I'm going to start applying additional patches to see if I can come up with the one(s) that fix that issue. I'll still release the kernel in its current state, but likely as 0.9.0 instead of 1.0.0 because of this known issue. It may not affect everyone (apparently it has something to do with LTE handshakes between towers), so perhaps some people won't even experience the issue. They're just beginning to deploy LTE by me and it was while I was just leaving my house area that it happened, so I would tend to believe that's the reasoning. According to VZ's LTE map, LTE is within a mile of reaching my house now.

Anyway, just wanted to give you the update. At least there are no lockups or reboots, I'm pretty certain of that now. It's just that the initial release will have a little asterisk/warning next to it now. I'll keep digging for you guys until I get to the bottom of it.
[HTC Droid DNA] ML417:
have you tried charging the phone overnight? that seemed to be the most common occurrence of reboots.

try having a clock on (i use desk dock personally) and have it on all night while charging.
[HTC Droid DNA] elkay:
Yep, 2 nights of charging overnight. I had reboots 3 times overnight on the Cubed kernel, and no reboots yet on mine with the HSIC patches. I'm confident it's not going to freeze or reboot in its current state. Just need to track down that loss of signal fix.
[HTC Droid DNA] S121Guy:
I think u need to make your own own thread :)

Would be easier to track your updates.

Plus I would hate to see others getting upset over thread jacking.

sent from my rooted DNA
[HTC Droid DNA] spinkick:
Good idea, just let us know. I'm eager to try it out. I miss that extra battery life.
[HTC Droid DNA] elkay:
New kernel is posted in its own thread. Take the discussion there. :)
[HTC Droid DNA] dsb9938:
Added the HSIC fix to this so the stock folk can save some battery.

D

.
[HTC Droid DNA] usopen:
Welcome back DSB!!! Hope you are feeling better!!!
[HTC Droid DNA] elkay:
Thanks for adding this, since the kernel I'm working on is going to be going a bit further than this.
[HTC Droid DNA] wpsantennas:
I just wanted to say that I appreciate all of the work both of you have put into all of your kernels.
[HTC Droid DNA] CISGS:
If I flash the boot img, do I lose any data or apps?
[HTC Droid DNA] iOSh8er:
No

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] dreamdoggy:
Can you confirm the md5? My tests do not match. I'm thinking the OP still has the original md5?
[Transformer TF300T Q&A, Help & Troubleshooting] aletheus:
has anybody gotten an xbox 360 wireless controller working?
[Transformer TF300T Q&A, Help & Troubleshooting] schkeet:
Try Sixaxis controller app its like 2 bucks hooks up ps3 controllers throu bluetooth...

i use it all the time best money ive spent in the market by far and its pretty easy to set up
[Transformer TF300T Q&A, Help & Troubleshooting] funnel71:
Xbox isn't Bluetooth so I doubt it would work. I think some kind of adapter would be required, but uncertain if there's one that works with android.
[Transformer TF300T Q&A, Help & Troubleshooting] aletheus:
yes and i have it working great on my Note 10.1, but my buddy has an xbox 360 controller and an asus tf300t so i figurednid comb his devices forum as hes not so tech saavy.

Sent from my GT-N8013
[Transformer TF300T Q&A, Help & Troubleshooting] s2_d2:
This is a useful article on getting your wireless Xbox controller to work with your tablet. You will need a wireless receiver, which can be bought for around £7. I wasn't able to get it working exactly, or was missing a file, so I downloaded the USBJoyService app. It detected my controller and and had to map the buttons in MD.emu (MegaDrive emulator).

I didn't find it 100% responsive. It felt laggy. I would prefer to either go for a wired Xbox controller, or get a PS3 controller, as it has bluetooth (though are expensive).
[Nexus 7 Accessories] czonin:
While searching for a case that's slim, good looking, folio, and doubles as a stand I stumbled upon the Moko Slim Shell Folio on Amazon. Others suggested the Moko Slim Fit which didn't seem slim at all, and the Poetic case which I ordered first. I found the Poetic case to be unnecessarily thick on the back piece and it just felt cheap overall. Compared to the Poetic the Moko Slim Shell felt better made, the plastic case was noticeably thinner, and although similar to the Poetic in appearance, the subtle changes make it look more premium. Just like all other cases with a "smart cover" it doubles as a stand in two positions; a more laid back typing position, and a vertical position for watching movies or playing games. It triggers the sensor on the Nexus 7 perfectly to put it to sleep when closed and wake when opened. The previous version of the case had an issue where the device would go to sleep when folding the cover all the way back, but it has been revised and no longer suffers from that issue. Lastly the case comes with a lifetime warranty from BSCstore and at $15.99 it is almost $10 cheaper than the Poetic, so there is no comparison in my opinion.

Amazon: http://www.amazon.com/gp/product/B009UPDSFU/ref=oh_details_o00_s00_i00

Pictures:
[Nexus 7 Accessories] wavrunrx:
crappy reviews:

http://www.amazon.com/MoKo-Magnetic...dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1
[Nexus 7 Accessories] czonin:
Both reviews were regarding the problem that was fixed in the revision.
[Nexus 7 Accessories] Troute:
Lifetime warranty they say so it doesn't matter, if you have a problem you just get another.
[Nexus 7 Accessories] nickriley:
It does look good, the price seems to be fine... I'm just wondering if the front glass will get scratched in time from the metal thingy on the front cover..
[Nexus 7 Accessories] czonin:
That was my only worry but the magnet on the case part is slightly raised so the metal tab doesn't come into contact with the glass.
[Nexus 7 Accessories] geniustheanimal:
Bought this for my wife for Christmas. There was still an issue with the magnet turning the screen off when it was opened all the way. Emailed the original seller about it and they said it was a defective unit that was missing the shielding. They're now sending me a replacement for her, one for me, and gave me instruction on how to remove the magnet from the old one to use as an interim case while waiting on my replacements.

ObamaNotBad.jpg
[Nexus 7 Accessories] PawleysJim:
I bought the MoKo slim fit case. It's very good....and the magnets work great

http://www.amazon.com/MoKo-Slim-fit-Google-Android-Tablet/dp/B008FLYROG/ref=pd_cp_pc_1
[Sony Xperia Miro, Tipo (Dual), J, E] zawawi:
Hey guys, i just updated to the latest firmware of the xperia miro, im trying to find how to root it, but it needs the older firmware.. So anyone knows how to downgrade the firmware?? Please help? Im desperate to root my miro thank you
[Sony Xperia Miro, Tipo (Dual), J, E] SammiSaysHello:
Flash an older firmware with flashtool :p

Sent from Xperia Arc S
[Sony Xperia Miro, Tipo (Dual), J, E] zawawi:
Can you give me a link to flash tools?
[Sony Xperia Miro, Tipo (Dual), J, E] SammiSaysHello:
here :)
[TouchPad Q&A, Help & Troubleshooting] tk_xda:
I have a touch pad with current version of WebOS and would like to install Android for the first time on it. I know I am late to the game.

I was looking here and found a tutorial, but it has bad links for the required files. With all the ROMs, tutorials around here and the dying links, can someone share link to a tutorial that is current and the required files still present for installing a stable version of Android. ICS or Jellybean preferred, if that can run stable, otherwise, I would consider going older. I am already familiar with Android, having a rooting Android phone, but somewhat overwhelmed about which information here I should pay attention to, versus what is obsolete.

Thanks
[TouchPad Q&A, Help & Troubleshooting] tk_xda:
I found this tutorial with what appears to be complete set of required files

http://michaelkizer.com/Blog/tabid/...86/Installing-Android-on-the-HP-Touchpad.aspx

This is from September. Should I still be using this version of CM9, or is there a more recent one that would be better.

The tutorial says CM9 seems to be the most mature and well supported version. Should I expect all hardware on my touchpad including the camera to be working with this?

Should I use the google apps bundle from April he supplies, or another one?

Thanks