yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] techdog:
As requested.....
[Sprint Samsung Galaxy S III] enzoevo:
Are you still running ktweaker? I would remove it, if so. Not sure that will fix your issue, however.

---------- Post added at 03:44 PM ---------- Previous post was at 03:40 PM ----------

@decimalman - I see this message in my logcat a lot. Is this something to be concerned about? Is this an SELINUX issue, or just a harmless artifact?

W/ActivityManager( 763): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL

E/DatabaseUtils( 763): Writing exception to parcel

E/DatabaseUtils( 763): java.lang.SecurityException: Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL

E/DatabaseUtils( 763):	at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:13090)

E/DatabaseUtils( 763):	at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:2038)

E/DatabaseUtils( 763):	at com.android.providers.settings.SettingsProvider.callFromPackage(SettingsProvider.java:607)

E/DatabaseUtils( 763):	at android.content.ContentProvider$Transport.call(ContentProvider.java:279)

E/DatabaseUtils( 763):	at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:273)

E/DatabaseUtils( 763):	at android.os.Binder.execTransact(Binder.java:388)

E/DatabaseUtils( 763):	at dalvik.system.NativeStart.run(Native Method)
[Sprint Samsung Galaxy S III] techdog:
Uninstalled it... As you foretold, didn't make a difference....
[Sprint Samsung Galaxy S III] the_original_teknikl:
hey decimalmane, what program do you use to create the custom splash/boot logo screens?

could ya post a link?

ive tried creating one and i just get a boot loop.

please and thank you ;)
[Sprint Samsung Galaxy S III] decimalman:
As far as I know, that's just TW being TW.

The dkp installer takes care of everything for me.

I've heard that splash screens aren't behaving well on recent dkp builds, but I don't know what's causing problems. Because there's so many different splash screen zips, I can't offer any support for them. The only officially supported method of installing a custom splash screen on dkp is as follows:

1. Open your internal storage in your file manager of choice

2. Create a new folder named "dkp"

3a. If you're using an existing splash screen, extract initlogo.rle from the zip file into the "dkp" folder you just created, then rename it "splash.rle"

3b. If you're using a PNG file, copy it to the "dkp" folder you just created, then rename it "splash.png"

4. Re-flash dkp
[Sprint Samsung Galaxy S III] cbrox:
Do you still have any of the KT's scripts for his kernel in your init.d directory?
[Sprint Samsung Galaxy S III] techdog:
Yes, but I checked those out and those are just scripts for the initial governor and OC settings for during early startup. Those are overridden by Trickster when Trickster starts up.

I wouldn't expect that those would inhibit the ADBlock functions.

I also re-flashed the original kernel and re-flashed the dkp kernel to remove the Ramdisk, hence no init.d, and the ADBLock still is not working - the current CrossBreeder does not need init.d to run, or so I have been lead to believe.

Also, the DNS Boost functions are not working, I noticed.
[Sprint Samsung Galaxy S III] imaconeheadXD:
That is completely related to Crossbreeder and not DKP, Crossbreeder bypasses the "hosts" file and uses it's own "master" file through the DNS modifications causing the issue. On Android 4.3 and above, you needed to flash another zip or add some other file to Crossbreeder to make that function correctly, I just can't remember what the name of it is, but you could find it in the Crossbreeder thread. To fix your issue, either run the disable dns boost script in the crossbreeder directory or find and flash the other required file in the crossbreeder thread.
[Sprint Samsung Galaxy S III] techdog:
Thanks. I took another look at the CrossBreeder thread. I have it working, now.... I was trying to disable the randomization in CB since [MENTION=4932679]decimalman[/MENTION] has built it into the dkp kernel. However, in doing so, I also disabled the DNS boost and ADBlocking. I found a CB flashable zip that contains only the DNS boost and Ad Blocking and that is working great.
[Sprint Samsung Galaxy S III] decimalman:
It's been a while, so let's do some new builds for both AOSP 4.4 and TW 4.3. Still no love for TW 4.1 (are enough people using 4.1 to justify continuing support?), and I still haven't fixed up the bluesleep driver that's been causing bogus wakelocks on AOSP (it really needs to be rewritten).

EDIT: Wifi isn't working on the AOSP build.

EDIT 2: Fixed builds are up!

TW Changelog:

Major overhaul to erandom, msm_rng, and all things entropy:

A new entropy daemon, plus a new touchscreen entropy source

Major speedup for erandom

Bugfixes and a major speedup for the hardware random number generator driver

Cleaned up (among other things) erandom initialization

Enabled network block devices

Swapped in a new splash screen

AOSP Changelog:

Synced up with CM, Linux 3.4.82

Major overhaul to erandom, msm_rng, and all things entropy (everything from the TW changelog is included)

Added code to save some entropy across reboots

Enabled network block devices

Swapped in a new splash screen

If you're not sure what network block devices are or why you'd want them, you probably don't have much use for them. I enabled them at the request of Phil_Suz, who's been working on an interesting multiboot system (there should be a thread in the General subforum for your device). NBD support opens up some very interesting possibilities, especially when paired with multiboot.
[Sprint Samsung Galaxy S III] dirkdigles:
Awesome! Would this new build be different than the 2/20 test?
[Sprint Samsung Galaxy S III] GreyCelt:
On the AOSP build I'm only getting 56 bytes on the download. I've tried several times and each time the same... 56 bytes.

Sent from my Xposed CM11 SGS3 on Virgin Mobile
[Sprint Samsung Galaxy S III] decimalman:
Yep. Nothing has changed dramatically, but erandom is considerably faster (45 MB/s vs 25 MB/s sustained read speed), and the various random number generators are initialized more securely.

Clear browser cache and/or try a different browser? :fingers-crossed:
[Sprint Samsung Galaxy S III] GreyCelt:
Hey, thanks! I don't know why I didn't think of that first. Next Browser was giving me the issues. I downloaded Chrome and tried it through that... PROFIT!

Sent from my Xposed dkp CM11 SGS3 on Virgin Mobile
[Sprint Samsung Galaxy S III] wetbiker7:
New AOSP build has wifi working just fine. Just flashed it and will continue testing. So far so good bro.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] techdog:
New kernel for TW4.3 is working great. Thanks so much!

Is there an explanation anywhere for the freelunch governor settings? I would like to experiment with tweaking some of the settings but would rather do so having some type of understanding of each of the settings and their acceptable parameters.

Thanks.

Update: Never mind. Found it. Thanks.
[Sprint Samsung Galaxy S III] enzoevo:
Flashed latest TW, so far so good!
[Sprint Samsung Galaxy S III] remotehugger:
+1

flashed latest 4.3 TW and so far running great - entropy pegged at 4096 - scrolling smooth as butter - very nice so far -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] Advertize:
The Kernel runs great but is there a reason I cant flash a different init splash screen without crashing:confused:

By crashing I mean I get a bunch of garbled graphics and the phone goes into a constant reboot situation. I can reflash another kernel put the new splash screen on with no problem. Any Ideas what has changed and is causing this?
[Sprint Samsung Galaxy S III] decimalman:
On AOSP, there's a good reason why splash screens don't work, but it would require repackaging the splash screen to fix. On TW, I hear they're not working either, but I have no idea why.

I posted the easiest method to use a custom splash screen with dkp here. It only applies to that last couple builds, but those are the ones causing the most problems anyway.
[Sprint Samsung Galaxy S III] Advertize:
I have no problems with any AOSP roms but I have on Touchwiz with your kernel for the past 2 or 3 weeks!
[Sprint Samsung Galaxy S III] joeyddr:
2/26 I lost wireless
[Sprint Samsung Galaxy S III] techdog:
Does anyone have any freelunch tweaks they would like to share? Personally, I am looking for increased battery savings primarily and not too much performance degradation, although I will take a small hit on performance if it means increased on-screen battery life.

Also, does anyone know how to upload/download governor settings into trickster? I can save them but I don't know where they are saved.

Thanks.

Sent from my dkp energized Samsung Galaxy S3.
[Sprint Samsung Galaxy S III] mawst95:
I couldn't connect to my work wifi with latest kernel.

Slimkat 3.2. Refreshed rom, kernel, wiped wifi data, wouldn't connect until I reflashed 2/13 kernel. Said authentication failed.
[Sprint Samsung Galaxy S III] wallythander:
You sure you are flashing the 2/26 update? That is exactly what happened to me on the 2/25 build. Authentication failed. I am also using Slim 3.2. I did a factory reset before I installed 2/25 and Slim 3.2, I thought I had messed something up. However 2/26 fixed it.
[Sprint Samsung Galaxy S III] mawst95:
Ah. Didn't realize there were two consecutive versions on 2/25 and 2/26. Thought there was only one. I had 2/25. Downloading 2/26 now. Thanks for your help!
[Sprint Samsung Galaxy S III] decimalman:
The memory layout on AOSP changed recently, and it's probably going to cause problems with splash screens on custom kernels in the near future. :(

My thoughts exactly. I overlooked a small difference between the TW and AOSP kernels and accidentally scrambled the wifi MAC address. The 2/26 build fixes it.

EDIT: I guess I should remove the 2/25 build.
[Sprint Samsung Galaxy S III] joeyddr:
the 2/26 build my wifi would not turn on.
[Sprint Samsung Galaxy S III] sinisin:
I have the custom splash set up. I use philztouch with Aroma File Manager. I keep a copy of the splash file on my sd. Anytime I have to completely wipe I just push the file back to system before I reboot. My splash is always working. Tho once in a while it hangs and I have to pull battery. On 2-26 and CM11 2-17 Build because the unified builds are whack.

Edit: Pretty sure running freelunch and sioplus is dangerous. About 10 minutes after I moved from sio to sioplus my phone froze and wouldn't do anything but bootloop. I was one step away from giving up in the mad flash process that ensued. I first just tried the kernel cleaner script, then the same with a manual dalvik and cache wipe. Neither time fixed it. So then I reflashed the ROM and dkp 2-26 and ran KC. No dice. Had to try just reflashing the rom to change back to stock. Still no dice. Because I forgot to run KC. Did that and I finally got back to booting up. Could possibly be more then the choice of govenor/scheduler. Not sure. Was fine until then. Was also running at 162 min but never had an issue before.
[Sprint Samsung Galaxy S III] cbrox:
Been running freelunch and sioplus combo with DKP TW versions 02/20/2014(4.8 days), and 02/25/2014(30+ hrs) paired with Dazes wicked 4.3 v5 with no issues(no freeezes, no bootloops, no SOD's).

Its ran solid for me. liked it alot

my setup was as follows:

UV'ing by -75 across the board

freelunch = gov

sioplus = sched

4096 = RABS

yeah = TCP Congestion Control

54000 = Min

1512000 = Max
[Sprint Samsung Galaxy S III] remotehugger:
I also had freeze ups on sioplus/freelunch combo - but runs awesome with regular sio scheduler -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] tmcwilliam01:
A quiet kernel thread = solid kernel

Thanks for your hard work!

I've got MOAR!
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
Exactly what I've been thinking since yesterday when I've noticed a couple days in a row with no new posts.

Congrats decimalman!
[Sprint Samsung Galaxy S III] remotehugger:
yea man - been very happy w/ latest TW 4.3 - running sio/freelunch - UV'd 50mv across the board - great battery life w/o a hit on performance - entropy pegged at 4096 at all times - only thing that could be better is a random splash screen at boot instead of at flash - I've flashed a couple times and have stuck with the gears for now - awesome work decimalman - thank you -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] marcran75:
Due to issues I was having earlier I reluctantly had to switch to another kernel. After reading recent feedback I decided to make the switch back to dkp and I'm glad I did. Everything is running perfect. Great job [MENTION=4932679]decimalman[/MENTION].:thumbup::thumbup:
[Sprint Samsung Galaxy S III] andee39:
I am on 2/26 version and haven't made any changes. Last time I tried (with much appreciated help from [MENTION=2672641]meyerweb[/MENTION] and video) I couldn't get it exactly like I wanted and kept experiencing issues with TuneIn Radio app. I'm waiting for MOAR 9.0 to drop and then will see where I stand and will start again if necessary with some adjustments. One question I wanted to ask is would kernel issues explain lag when entering pin on home screen? :confused:

Thanks!
[Sprint Samsung Galaxy S III] MikeWjF:
Frustrating, this kernel runs flawlessly in every way, except after a day or so it seems to break Wi-Fi after a normal reboot.
[Sprint Samsung Galaxy S III] Papa Smurf151:
Hey [MENTION=4932679]decimalman[/MENTION] I cant remember if you ever mess with the ramdisk on this kernel but if you do please make sure you add the new bootpath for msim that cm implemented a few days ago or there will be non stop fc through all cm based roms
[Sprint Samsung Galaxy S III] decimalman:
Break how? I've been messing with the wifi driver lately, but I didn't think there were any issues left in the most recent builds.

Thanks for the heads-up. :good:

I splice in a new splash screen, but otherwise leave the existing ramdisk untouched. dkp usually doesn't have issues with ramdisk changes, and hopefully this will be no different. :fingers-crossed:
[Sprint Samsung Galaxy S III] upconvert:
I'm on the 3/6 PACROM build and the 2/26 dkp. No problems at all!
[Sprint Samsung Galaxy S III] MikeWjF:
Suddenly it won't connect to any network, it may or may not even activate at all, when it does it seems to see networks that aren't near me at the time. Even switching kernels yields the same results, wifi works on first boot, than after a reboot it goes bonkers again. It's happened to me running this kernel before. The only thing that fixes it is a nandroid restore or fresh install. I was running it on Slimkat 3.0.
[Sprint Samsung Galaxy S III] wetbiker7:
Just wanted to pop in and say that the AOSP kernel has been running great with Carbon. Thanks again for all your hard work Decimalman. It is greatly appreciated.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] nealecj954:
I've tried multiple times to flash the latest TW kernel, 02/25. I've redownloaded the zip a number of times and it constantly falls. Won't flash. Other zips flash fine though, only seem to have issues with this zip. Running wicked 0.5
[Sprint Samsung Galaxy S III] cbrox:
I'm running wicked 4.3 v5 paired with the 02/25-d2spr-d2vmu version. I don't have any issues re-downloading and re-installing it or the 02/25 specific boot image made for Daze. Just got done testing them both by installing by phone only and by PC/transfer to phone. Both ways worked with no issues.

Sounds like to me you have some corruption going on, on your side.

A little more info would be helpful.

What is your complete setup including recovery? When you flash it in recovery are there any errors or is it when you try to boot it that it hangs? When you say other zips, are they previous versions of DKP(list them) or are they different kernels?

...cbrox
[Sprint Samsung Galaxy S III] nealecj954:
I am running wicked sensations 0.5 as it comes. I am using TWRP 2.6.3.0. I am able to flash other zips like an updated app or a volume mod. When I tried to flash the updated kernel it just says failed. I don't have any other issues that I've noticed. No freezing, no reboots, everything seems to run great. I just can't seem to get the newest kernel flashed. The only thing I haven't tried is downloading on comp and then transferring, although I download other stuff with my phone and it flashes fine.
[Sprint Samsung Galaxy S III] prboy1969:
Are you DL'ing over the Network, or WiFi ? I try to never DL files over the network. The slightest interruption can cause a corrupt DL. Are you checking the MD5 checksum ?
[Sprint Samsung Galaxy S III] upconvert:
The consensus seems to be that Philz recovery is the way to go with our phones. If you have verified your download, and it still won't flash, I'd try Philz.
[Sprint Samsung Galaxy S III] cbrox:
+1 on what prboy1969 said!

The stock kernel that comes with v5 is the DKP specific boot image made for Daze by decilmalman.

One thing you can try is re-flashing your recovery or flashing a newer version of the recovery or flashing a different recovery . I've had recoveries scramble before or i've accidentally turned on a setting(fat fingered) somewhere that is an impediment to the flashing.

I'm using Nadicts flashable TWRP version v2.3.1.0 which is working fine on my phone.

---------- Post added at 11:36 AM ---------- Previous post was at 11:23 AM ----------

That's rubbish. Their is no "consensus" of that. It's whatever recovery works best with your phone! For some its TWRP, for some its PhilZ. If its TWRP, use TWRP. If it's PhilZ use PhilZ, if it's something else use it.

There is no need to badmouth one recovery over the other in these threads.
[Sprint Samsung Galaxy S III] nealecj954:
I tried over the network and on wifi repeatedly. I guess I just kept getting corrupt downloads. This morning it finally flashed. I think I downloaded it about 20 times. I don't even know which one worked...over the network or wifi...but it flashed and seems to be working fine now.
[Sprint Samsung Galaxy S III] prboy1969:
The method I've always used that rarely fails is to DL to the Laptop / PC over WiFi / Hardline. Then to transfer to the phone. Also a very important step, always verify the MD5 checksum. It only takes a minute, and can save you a lot of headaches.
[Sprint Samsung Galaxy S III] nealecj954:
Thanks everyone for your help and input. Got everything working fine. I think I'll just stick to downloading to pc then transferring. And I'll make sure I check the md5
[Sprint Samsung Galaxy S III] bradley129:
Your touchwiz 4.1 test kernel is running great thanks man. I have made dkp the only kernel I use of even think of using its so stable and packed full of features.

Sent From My Samsung Galaxy SIII on Metal ROM.
[Sprint Samsung Galaxy S III] upconvert:
My bad. I wasn't trying to badmouth any recovery. I love TWRP, and have used it for years. It was the first recovery I put on this phone and it worked great. That's why I have never said anything bad about it. When KitKat Roms started coming out, however, it couldn't flash them. A lot of problems ended up being fixed by PhilZ. If the md5 had checked out, I think it would have been a good thing to try.
[Sprint Samsung Galaxy S III] wetbiker7:
Don't sweat it man. I had the same thing happen on my phone. I love TWRP and have ran it for a few years now. I've had great luck with it up until a few months ago. I was running Wicked Sensations using it and it worked fine. I started running the 4.4.2 ROMs and that's when my problems with TWRP started. I couldn't get several of the ROMs I had to flash. I switched over to Philz and they flashed perfectly. I've talked with several others who have experienced the same problem so it's not an isolated issue.

Sent from my d2lte using Xparent Purple Tapatalk 2

---------- Post added at 11:39 PM ---------- Previous post was at 11:09 PM ----------

Don't sweat it man. I had the same thing happen on my phone. I love TWRP and have ran it for a few years now. I've had great luck with it up until a few months ago. I was running Wicked Sensations using it and it worked fine. I started running the 4.4.2 ROMs and that's when my problems with TWRP started. I couldn't get several of the ROMs I had to flash. I switched over to Philz and they flashed perfectly. I've talked with several others who have experienced the same problem so it's not an isolated issue.

As for bad mouthing a recovery, you did nothing of the sort. Nowhere did I read where you had written a cross word about any recovery. As for Philz, I am in agreement with you. It flashes every ROM I throw at it. When TWRP is able to do so I'll probably switch back over. Until then I'm sticking with Philz. :thumbup:

Sent from my d2lte using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] marcran75:
Installed MOAR V9 last night and was wondering how do I change the splash screen that comes with the ROM. I still have one of your splash screens I was using before in dkp folder. How do I get it to apply?
[Sprint Samsung Galaxy S III] decimalman:
MOAR has its own installer which doesn't include the fancy splash screen stuff from dkp's installer. You'll need to flash a regular dkp zip over MOAR to get your usual splash screen back.
[Sprint Samsung Galaxy S III] marcran75:
I have it as dkp/splash.png/dkp-splash6.png. Tried to flash dkp over MOAR and it isn't working. Do I have the folders wrong?
[Sprint Samsung Galaxy S III] decimalman:
It should just be dkp/splash.png, i.e. drop the PNG into dkp/ and rename it.
[Sprint Samsung Galaxy S III] marcran75:
Idk where I got the idea of the 2nd folder. Worked like a charm. Thank you. That bright green was clashing with my black and white theme. Lol
[Sprint Samsung Galaxy S III] apexone4697:
post latest zip

Can someone post latest kitkat aosp zip. Bad DL from site.
[Sprint Samsung Galaxy S III] FatalIll:
How do I get my CM11 Splash screen back?
[Sprint Samsung Galaxy S III] decimalman:
Clear browser cache and/or try a different browser?

There's not (yet) an easy way to leave the stock splash screen alone. I'll add something to the installer for the next builds.

For now, you can download the CM initlogo.rle, create a folder named "dkp" on your internal storage, copy the initlogo.rle into it, rename it "splash.rle", and then reflash dkp.

EDIT: Derp. There might be a bug in the old installer that breaks splash screens installed this way.
[Sprint Samsung Galaxy S III] mikek753:
is MHL HDMI supported?

hi,

is MHL HDMI supported by this dkp kernel?

thanks
[Sprint Samsung Galaxy S III] imaconeheadXD:
Yup, used it a whole lot just last week :)
[Sprint Samsung Galaxy S III] mikek753:
no fastcharge when HDMI is on ...

Hi,

I'd like to have "fast charge" while I use GPS/BT/LTE in my car, but it doesn't work for me while phone outputs video over HDMI to car touchscreen.

My phone is connected to MHL that is connected to 2A USB charger and HDMI video to car head unit (HU).

Yes, I enabled in Trickster fastcharge.

I don't see any positive charge as battery level just keep going down about 1% per 10 min.

What I can use to troubleshoot charging current?

Anything else I'm missing to enable fastcharge?

Thanks.
[Sprint Samsung Galaxy S III] bradley129:
Fast charge means nothing works but charging.... it would eliminate the use of fast charging If it outputted video.
[Sprint Samsung Galaxy S III] mikek753:
thanks for the reply.

Does it mean that fastcharge is just disabled by HDMI connection?

Any ideas - How I can use my S3 for 5+ hours car trips, while my phone is GPS navigator that outputs video to car dash HU and BT for calls and data (LTE) provider for emails and IMs?

Phone battery drains in 3 hours in this mode :crying: