yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] decimalman:
BetterBatteryStats is the usual suggestion, though I'm sure there are other apps as well.

That's probably a bogus reading. You can check directly with a root file manager: look at /proc/sys/kernel/random/entropy_avail.

Are you running any kind of entropy mod (Seeder, CrossBreeder, Operation Killjoy, etc)? dkp doesn't see much benefit from them, and they tend to cause trouble.
[Sprint Samsung Galaxy S III] remotehugger:
Not using any mods or tweaks - entropy_avail shows 0 as well - actually,under all folders under kernel and random show 0.00b -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
That's normal. You'll need to open entropy_avail with a text editor. Sorry for the confusion.
[Sprint Samsung Galaxy S III] remotehugger:
I opened the entropy_avail with the ES editor - that's the first pic I posted - it showed a zero - and I just tried it with ROM Toolbox Pro's editor and it also showed a zero -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
So you did. Oops. :o

My guess is that qrngd isn't running. The likeliest cause would be a poorly-behaved entropy mod, but you're not using one. :confused: It might take anywhere from rebooting to (dirty) re-flashing your ROM to get qrngd working again.
[Sprint Samsung Galaxy S III] remotehugger:
OK thanks - I'll try both -

OK - rebooted - no luck - dirty flashed ROM - no luck - cleaned flashed ROM - no luck - flashed stock kernel, entropy was active, low (390's and climbing) but active - re-flashed latest dkp and entropy back to zero - not sure what's up - probly my stupid phone - lol -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] erad1:
This is what shows for me running the latest kernel on CandyKat ROM...
[Sprint Samsung Galaxy S III] marcran75:
Just checked this on both my S3's. One running CM11 and one running stock 4.3. AOSP kernel showed 4096 entropy available and TW 4.3 kernel showed 0 entropy available.

Edit: Reverted to 12/26 and still showing 0 entropy available.
[Sprint Samsung Galaxy S III] dirkdigles:
I'm on latest dkp TW 4.3 and also read 0 entropy.
[Sprint Samsung Galaxy S III] decimalman:
So apparently this is a widespread issue. :( I'll flash back to TW and see what's up.
[Sprint Samsung Galaxy S III] remotehugger:
And of course its only TW - lol -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] the_original_teknikl:
mod please delete
[Sprint Samsung Galaxy S III] remotehugger:
I'm running the MK5 build on VM and I am using latest dkp - I'd say you should be fine -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] ssmercurys:
Is this kernel build different than that of the one in the OP? I see they are both labeled 2/13 but I dont know which one came first.
[Sprint Samsung Galaxy S III] CNexus:
So I was reading through the posts from a couple days back, and the ideas on initlogos got my attention...especially the ones about a "random" logo each boot

So...I spent the day implementing it (why not :D) and it.should be ready soon ;):cool::D:D
[Sprint Samsung Galaxy S III] remotehugger:
So a different splash each boot instead of each flash ? If so, that would be killer !!

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
So apparently TW 4.3 no longer uses qrngd? I must be going crazy. I don't see it in the ROM I'm running now or whichever of CNexus' stock zips I happen to have handy.

Nope. The 2/13 builds are all the same.

Beat you to it. :D The current dkp installer picks a random PNG from the zip or a custom PNG or RLE from internal storage, converts it as needed, and splices it into the ramdisk. The whole process runs deceptively quickly thanks to a purpose-built, multi-threaded update-binary. EDIT: more-hyphens! :p
[Sprint Samsung Galaxy S III] CNexus:
Yup :good:

There will be 3 modes available:

random - random splash of the ones includes in the boot.img

static - choose one of the initlogos packed in the boot.img (according to number) and set it as permanent boot logo (at least until you change the mode)

cycle - cycle between all initlogos available, in order

Ah, but this one does it every boot, not just when the installer runs ;)
[Sprint Samsung Galaxy S III] decimalman:
I see. Sounds like an interesting project. :good:
[Sprint Samsung Galaxy S III] remotehugger:
[MENTION=4932679]decimalman[/MENTION] - so does this mean TW may benefit from CB now or do you think it still wouldn't play nice ? Or is there something you can do to get entropy back up ? Or is it strictly ROM related ?

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
At present, TW would benefit from your choice of entropy mods. I'm in the process of testing a few ideas for an in-kernel entropy daemon, so the next build won't need entropy mods.
[Sprint Samsung Galaxy S III] remotehugger:
Ok awesome ! Thank you - will keep an eye out for a release -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] dirkdigles:
Newest kernel seems to be draining battery in idle faster than previous kernel (12/26). Overnight my battery was draining at 3% / hour, phone idle, good reception, all data services / wifi off.

I checked BBS, phone reported no significant wakelocks, deep sleep just fine.

Guessing deep sleep isn't actually happening although it's being reported?
[Sprint Samsung Galaxy S III] csmasn:
So phone choose to stop sleeping.

What can be happening? It was upped by 50.

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] decimalman:
Wakelocks? ROM name and version? Anything at all to help track down the issue? The CPU Spy screenshot at least tells me what kernel version you're using, but that's not nearly enough to tell what's wrong.

EDIT: Looks like I haven't checked my threads in a while...

You're on TW, right?

Deep sleep specifically means that the processor is in standby, and it's usually reported correctly. Much more likely is that one of the driver updates in the latest build is leaving some piece of hardware in a higher power state than it should. Since it's new and relatively untested, I'm guessing it's the voice processor driver. I'll look for anything out of place and possibly add some code to guarantee it's suspended properly.
[Sprint Samsung Galaxy S III] csmasn:
Sorry for the lack of info.

The rom is MOAR 8. I know my phone doesn't play well undervolted so I upped it to +50, it works ok.

Now I set the voltage to +25 & rebooted. It's deep sleeping again.

GSam didn't show any wakelocks.

Will report back.

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] dirkdigles:
Yup - on Cnexus' stock 4.3 TW.
[Sprint Samsung Galaxy S III] bodyshop:
Which version. Is for wicked sensations 4.3 version 0.5?

sent from my Wicked 4.3 hybrid
[Sprint Samsung Galaxy S III] cbrox:
The DKP kernel provided for Dazes Wicked 4.3 v5 is a kernel provided specificity for his rom with a dedicated DKP kernel boot splash screen and a dedicated specific boot image.

dkp-tw43-d2spr-d2vmu-20140216.zip is the same kernel minus the dedicated kernel boot splash screen(has a rotating one each time you flash it) and specific boot image.
[Sprint Samsung Galaxy S III] lvpre:
You can also flash the latest TW kernel with Dazes' rom. He has been working on the voice processor, so it would be an improvement over the one packaged with the rom. Just remember to make a nandroid before trying again. But cbrox is correct, you'll get an updated kernel, but the splash screen will probably change. Unless your phone is completely unstable and unusable, I would just wait a little bit until everything is figured out...mostly the voice/dialer issue. They are making huge strives, but unless you are comfortable with flashing and nandroids, I would just hold off for a bit.
[Sprint Samsung Galaxy S III] decimalman:
WS already includes an up-to-date TouchWiz 4.3 build of dkp.

I've got a build for you (and anyone else feeling adventurous) posted in the usual place. I looked through the a2220 driver, fixed a few issues, and added some code to make absolutely sure the hardware is suspended when it's supposed to be. If it doesn't fix the drain you were getting, let me know.

The new build also has lots of new code for all things entropy: two new entropy sources, some huge changes in the hardware random number generator driver, and more. Feedback is welcome.
[Sprint Samsung Galaxy S III] dirkdigles:
Wheeeee will check it out. Note that I'm one of those Sprint GS3 users that's flashed to a verizon MVNO. Not sure if that matters for the voice processor but wanted to note it.

Will flash the new test and see how it fares.

I'm assuming the file is this guy: dkp-tw43-d2spr-d2vmu-20140220-180057-dkp-4.3.zip ?

EDIT: Installed, entropy upon boot is 3848
[Sprint Samsung Galaxy S III] Ramer:
I assumed the filename. Running MOAR 8.1 and so far no problems, the phone seems to be smooth as silk.
[Sprint Samsung Galaxy S III] remotehugger:
flashed latest - entropy up to 3080 - nice work - dialer and call quality still excellent - phone feels slick and smooth - thank you decimalman -

edit : entropy up to 3894 now - not noticing any more stuttering or lag when scrolling through home screens -

edit edit : entropy now pegged at 4096 - very nice -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] enzoevo:
I don't think vmin is getting set. I checked 00dkp-vmin and it's set to 1000(best I can do with this phone). However, /sys/devices/system/cpu/cpufreq/dkp/vmin has a value of 1150. I don't think init.d scripts are running.
[Sprint Samsung Galaxy S III] tmcwilliam01:
I am seeing similar behavior.

I've got MOAR!
[Sprint Samsung Galaxy S III] remotehugger:
I didn't think dkp had init.d support ?? maybe I'm confused ??

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] enzoevo:
What's the best way to set vmin then?
[Sprint Samsung Galaxy S III] csmasn:
To enable init.d there's an app here in xda named universal init.

But how do I set minimum to 1150? Flashing the dkp-vmin-xxx?

TIA

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] enzoevo:
The default is 1150.

To set it to something else, change the xxx to the value you want and then flash.
[Sprint Samsung Galaxy S III] marcran75:
[MENTION=4932679]decimalman[/MENTION] made a modded ramdisk for init.d and boot animation support here: http://xdaforums.com/showthread.php?p=47981129

Post #640 @ the bottom of the page:thumbup:

Edit: Just realized you were on MK5 but as long as long as you are running this 4.3 kernel it should be fine.
[Sprint Samsung Galaxy S III] enzoevo:
Unfortunately that thing kills my phone every time I flash it. I was hoping it wasn't required anymore.
[Sprint Samsung Galaxy S III] dirkdigles:
I'm still getting some sort of drain. It's not huge, but it's there.

Looking at the info tab in Trickster and letting the phone sit idle, CPU usage never drops below 15% or so. The cores stay at minimum frequency / offline most of the time (when idle), however CPU stays pegged at 15%, sometimes jumping up to 40% and staying there for a bit.

Same reports from System Panel.

I did the Top command from within terminal and got this process:

PID TID PR CPU% S VSS RSS PCY UID Name Thread

107 107 1 16% S 0K 0K root uksmd uksmd

Whatever uksmd is, it's chewing up CPU for no apparent reason, 100% of the time.

EDIT: addt'l details: I'm using freelunch governor, sio scheduler.
[Sprint Samsung Galaxy S III] decimalman:
It still is. I haven't set the installer up to add init.d support on TW ROMs yet. Unfortunately, init.d is required for the vmin zip to work, and there's not an elegant way around that.

I think a dmesg might illuminate whatever is causing it. "su -c dmesg >/sdcard/dmesg.txt" or similar will dump the log to internal storage.

uksmd scans for duplicate memory in the background. On TW, it generally frees up an extra 200-300 MB. You can disable it ("echo 0 >/sys/kernel/mm/uksm/run"), but doing so is unlikely to fix any drain you're seeing.
[Sprint Samsung Galaxy S III] dirkdigles:
I was also thinking perhaps I should let the kernel run for a day or 2 before I make assumptions whether it's draining that much or not.

Anyway I did the dmesg command and posted the log here:

http://pastebin.com/auLL8a96
[Sprint Samsung Galaxy S III] remotehugger:
hey all- can I ask what the "glorious animations" refers too or what it means exactly ? :confused:

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] enzoevo:
[KERNEL][4.3/4.4/TW4.1/TW4.3] dkp - d2spr - 2/16/14

That's cool. There are a few init.d work arounds out there which I'll play with, but for now I'm just using ROM Toolbox's scripting to run the vmin script at boot.

Otherwise, this kernel is rock solid for me. Provided I don't undervolt too much. I've noticed significant improvement with dialer stability.

Great job [MENTION=4932679]decimalman[/MENTION]:good::good::good::good::good:
[Sprint Samsung Galaxy S III] marcran75:
I believe you are referring to the soft key backlights. I didn't notice it at first but after asking I was told that instead of the backlight just cutting out they fade out slightly. "Glorious" is a little bit of an overstatement but it's a nice touch.
[Sprint Samsung Galaxy S III] decimalman:
Yup.

The lack of animation on the softkeys had been bothering me an unreasonable amount, literally since I unboxed the phone. Getting the keys to animate on and off was essentially the Holy Grail of hardware changes for me. When I finally noticed that I'd overlooked something and I could manipulate the voltage on the LEDs and manually animate the brightness, I was thrilled. :victory:
[Sprint Samsung Galaxy S III] dirkdigles:
I think my initial reports of drain might have been inaccurate. Overnight, last night, data / wifi off, I lost about 8% battery over ~9.5 hours. So <1% per hour on standby. Not bad at all!
[Sprint Samsung Galaxy S III] dirkdigles:
Well I've run into some problems with the latest TW. Now my phone is freezing while it is idle (i.e. I go to unlock it and the screen won't turn back on). Only thing that fixes it is a hard reset or battery pull, and then goes back to the same behavior within an hour or so.

I tried flashing back to 12/26 but the problem somehow still remains.

Is there a kernel cleaner script I can run to clean whatever modifications were made and start afresh? I have a nandroid from a few months ago which is basically the same config as I have now (minus the new kernels), however I'd prefer to clean the kernel out and retain my current setup if possible.

I've also had issues with the touchscreen not functioning when waking up the phone; the screen turns on but then I can't do anything, forcing me to reboot.

Any ideas?
[Sprint Samsung Galaxy S III] imaconeheadXD:
Try clearing cache and dalvik, I'm running newest tw kernel as well but not having those problems

Edit : Also try raising the voltage if you undervolted
[Sprint Samsung Galaxy S III] dirkdigles:
So I ran ktoonsez kernelclaner script (which I believe just wipes caches & permissions), also wiped cache, then reflashed the newest TW kernel and the vmin-enable file.

No dice. Phone just randomly rebooted (has been doing that as well). No idea what's happened, but something between flashing this newest kernel and the 12/26 one has royally screwed things up. (the only modifications I have done to my phone during this time frame has been flashing those 2 kernels).

Any ideas of other places I could look / things to wipe? Or perhaps run a log to see what is happening?
[Sprint Samsung Galaxy S III] remotehugger:
could it have something to do with the vmin-enable zip ? i thought i had read that you need init.d support for that to work ?? not sure, just throwing it out there --
[Sprint Samsung Galaxy S III] marcran75:
You are correct. Post #1256 on the previous page.
[Sprint Samsung Galaxy S III] dirkdigles:
Huh. So would that imply that my phone is currently using lower voltages than stock?

The behavior seems very similar to what I experienced when I used to attempt undervolting with my phone (which is rev 0).

Trickster Mod reports that "Override Minimum Voltage" is "On" - i.e. stock voltages are being used. Could this be incorrect? If so, is there a way to fix?
[Sprint Samsung Galaxy S III] marcran75:
dkp is undervolted by default. That's the reason for the vmin.zip file. If you look back a page or two you will find a link I posted for the modded ramdisk from [MENTION=4932679]decimalman[/MENTION] that will enable init.d thus enabling you to use the vmin.zip provided in the op of this thread. It will reset you voltage settings to stock.
[Sprint Samsung Galaxy S III] enzoevo:
[MENTION=3224138]dirkdigles[/MENTION]

I've had the issue with the lockscreen not responding. It does appear to be related to undervolting, but it might also be associated with setting too low a min frequency or a combination of the 2. Maybe it's deep sleep related.

I believe the latest kernel however is not u/v'd by default (see post #1202). If you are using trickster, and u/v is disabled then stock (1150) should be your min voltage. You can confirm this by looking at the /sys/devices/system/cpu/cpufreq/dkp/vmin file.

You may want to try flashing stock kernel then flash back to dkp (wipe cache/dalvik).
[Sprint Samsung Galaxy S III] dirkdigles:
The dkp/vmin file reads 1150.

I just wiped cache and re-flashed stock kernel. Will leave it on this for a few days and see if problems persist; if not I'll flash back to dkp.

Update: Wow, I flashed CNexus' stock kernel (from his OP for the MK3 rom) and now Wifi straight up won't turn on. I flick it on and it immediately goes back to off. I think it's time for a nandroid restore at this point. Damn.
[Sprint Samsung Galaxy S III] enzoevo:
Wrong kernel. Post 724 for the link to kernel with the fixed Wi-Fi driver.
[Sprint Samsung Galaxy S III] dirkdigles:
There's no link in that post. I flashed the file wifi_fix_mk3.zip - which, according to several posts, is just the stock MK3 kernel (post 997 says this). After flashing that my wifi was completely borked.

Anyway I restored my nandroid so everything is back to normal now. Gonna do a new nandroid and then try the newest dkp again.
[Sprint Samsung Galaxy S III] marcran75:
He meant #724 of this thread. He didn't specify so I checked both threads. It's there.
[Sprint Samsung Galaxy S III] decimalman:
dkp's minimum voltage is a bit more complex that a lot of people realize. The default at boot is (and always has been) to enforce the stock 1150 mV minimum, but older builds included an initscript to lower it. Without that initscript (or without init.d support) the 1150 mV minimum stays in effect, so the stock voltages are used. If Trickster is showing "Override Minimum Voltage" turned on, the 1150 mV minimum is still enabled (if you open Trickster immediately after boot, it's possible but unlikely that the initscript hasn't run yet). Newer dkp builds don't remove the old initscript, so the old, lowered default will carry over to newer builds.

Side note: dkp-enable-vmin.zip just deletes the initscript, which keeps the 1150 mV minimum enabled during boot; the newer dkp-vmin-XXX.zip modifies the initscript, which means it only works with init.d support.

Last time I checked, the stock and wifi fix zips don't include kernel modules, which means wifi won't work if they're installed over a custom kernel. Reflashing your ROM (assuming it uses a stock kernel) is the easiest way to return to the stock kernel. EDIT: I forgot that rompnit put together a kernel with the modules included; it'll work fine if flashed over a custom kernel.

Phone not waking up (aka sleep of death) is almost always caused by undervolting and/or underclocking, and the easiest fix is to make sure you're using stock settings (i.e. enable "Override Minimum Voltage" and set minimum frequency to 384 MHz). You may also want to delete /system/etc/init.d/00dkp-vmin if it exists. If it's still happening with the default settings, I need more information to know what's happening. To start with, does your phone make any indication that it's alive (e.g. LED lights up when connected to a charger)? If so, I need the kernel log (see below). If not, the processor isn't resuming correctly, which leads back to voltage and/or frequency settings.

Touchscreen not responding has been reported by a few different people, but I haven't been able to reproduce it. I can't fix it until someone provides me with debug information. Since the touchscreen isn't working, you'll need a computer with adb installed; "adb shell su -c dmesg >dmesg.txt" will dump the kernel log.
[Sprint Samsung Galaxy S III] enzoevo:
Thanks for clarifying all of this. The stock_kernel zip I was referring to was linked in this thread by romnpit when I had the exact same issue trying to go back to stock.

In the case where my phone wouldn't wake from the lockscreen, the screen would come on via home or power buttons but would not respond to any input. Had to reboot to recover. Every time it's happened I've been away from home so I couldn't adb into it.

If it does happen while I'm at home, I will certainly try to get more info. I just add another 25 mv until it stops happening. So 1025 is my vmin now. It seems to be more of an art than a science. :)
[Sprint Samsung Galaxy S III] remotehugger:
I guess I'm still a little confused - lol - just flashing latest TW dkp, my min. frequency is 54 and min. MV is 850 - I haven't messed with UV yet - but going to start and see what I can get down too -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] decimalman:
I forgot about the kernel rompnit put together.

I was thinking the touchscreen driver was just running into an error, but if the buttons aren't working either, it's something else entirely. When you get the chance, could you take a logcat as well? It shouldn't be needed, but you never know. Thanks for offering to help. :good:

1000-1050 mV seems to be the sweet spot for a lot of people. Of course, "all phones are different," as they say.
[Sprint Samsung Galaxy S III] techdog:
I just installed the new kernel - seems great!

I was just testing the kt747 kernel and using CrossBreeder for blocking ads... When I switched back to dkp, the CrossBreeder AdBlock stopped working. Is there any reason that should happen? Seems to me like there shouldn't be any dependency there.

What do you think? Anyone else have issues or notice this? Anyone have a solution?
[Sprint Samsung Galaxy S III] dirkdigles:
I noticed that I couldn't get adaway to work; was working on stock, doesn't seem to work now (not sure if that's related to dkp or not). It just hangs at downloading hosts file / updating.
[Sprint Samsung Galaxy S III] marcran75:
I'm pretty sure Crossbreeder requires init.d support. If you read back a few pages I posted how to enable init.d which is not included in the kernel.

Edit: This was meant for [MENTION=2597290]techdog[/MENTION] above you. Quoted wrong person.
[Sprint Samsung Galaxy S III] techdog:
if you mean using the modified ramdisk, I am using that. I flashed the permissive ramdisk after flashing the kernel and before flashing CrossBreeder.

There was another reference, which I didn't think was posted by you, to something available from the Play store for enabling init.d but I haven't tried that.

I wrote a small script to test and init.d support is definitely there...
[Sprint Samsung Galaxy S III] marcran75:
When you ask for help it is best to post more details like you did in this post. That will enable ppl to better help. The more info you give the better someone trying to help can pinpoint what the issue could be Since you say you have init.d it would probably be best to ask your question in the Crossbreeder thread.
[Sprint Samsung Galaxy S III] techdog:
I have posted it there. I posted it here because all I changed was from KT747 to dkp and AdBlock was no longer working. My guess is that it is either something in dkp or in the modified ramdisk since that is all that I changed.

However, unlike an earlier poster, Adaway is working for me.
[Sprint Samsung Galaxy S III] enzoevo:
Are you able to post a logcat?