yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Robalboa:
I use this on md4 device status normal

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] bigwillyg:
Hopefully he can get it to work for the nd8 update.
[Android Q&A, Help & Troubleshooting] nikolaaaa:
Hardware: roamer2

Model: ZTE Kis Lite

Build number: P752D01_EUROPEV1.0.0B05

Build date UTC: 20121219-163244

Android v: 2.3.6

Kernel v: 2.6.38.6-perf + zte-kernel@Zdroid-SMT

Baseband v: P752D01_EUROPEB01

I've tried almost all of the rooting methods, including Superoneclick, MTK droid root & tools, ZhuoDaShi, Unlockroot, and many more but nothing. Can anyone please tell me how can i root this chinese crap?

Tnx
[Android Q&A, Help & Troubleshooting] ecsike:
Anyone has any solution, impossible to put up root and recovery?
[Android Q&A, Help & Troubleshooting] Brna1:
My need same help.

Сент фром му ЗТЕ усинг Тапаталк 2
[Android Q&A, Help & Troubleshooting] knifey_au:
seems like everything i try doesn't work including

http://xdaforums.com/showthread.php?t=2138234

^ which doesn't mention KIS I/II/III/LITE/PLUS so.....
[Android Q&A, Help & Troubleshooting] knifey_au:
if you download that rooting app i mentioned, extract it to every directory of superoneclick, run superoneclick it will install a driver. then run the rooting package. i did a million things but i think that was it.
[Android Q&A, Help & Troubleshooting] tsiridim:
my solution on root for ZTE Kiss Lite V790 is here www . filedropper.com / d_4

I have a mobile ZTE Kiss Lite V790 and i managed to make it root.

follow thw instractions here.

www . filedropper.com / d_4

I have a mobile ZTE Kiss Lite V790 and i managed to make it root.

The procedure i followed is:

I download the file www . filedropper . com / rootv790 rootv790.zip

and unziped its files on my c:\temp

I also downloaded and install the www . filedropper . com / ztedriver driver file.

then i should manage to run one 中兴V788D一键ROOT .BAT executable file but i could not.

so ,i instead of running it, I edit copy the 中兴V788D一键ROOT .BAT text in the Microsoft Word and

change the language so that i could read the code. and i understand some of the commands inside the

中兴V788D一键ROOT .BAT file which i run on CMD (DOS) :

these commands was:

adb kill-server >NUL 2>NUL

adb wait-for-device >NUL 2>NUL

adb reboot bootloader ------->Here the phone stopsand goes waiting. So i installed again the device "android" driver.

fastboot boot Superboot.img

ping 127.0.0.1 -n 15 >NUL

adb wait-for-device >NUL 2>NUL

ping 127.0.0.1 -n 5 >NUL

adb remount

adb shell rm /system/bin/su >NUL 2>NUL

adb shell rm /system/xbin/su >NUL 2>NUL

adb shell rm /system/app/Superuser.apk >NUL 2>NUL

adb shell rm /system/app/superuser.apk >NUL 2>NUL

adb push su /system/bin/su

adb shell chown 0.0 /system/bin/su

adb shell chmod 06755 /system/bin/su

adb shell ln -s /system/bin/su /system/xbin/su

adb push Superuser.apk /system/app/Superuser.apk

adb shell chown 0.0 /system/app/Superuser.apk

adb shell chmod 0644 /system/app/Superuser.apk

adb push RootExplorer.apk /system/app/RootExplorer.apk

adb shell chown 0.0 /system/app/RootExplorer.apk

adb shell chmod 0644 /system/app/RootExplorer.apk

adb reboot

adb kill-server >NUL 2>NUL

------------------------------------------------

* A trick that i need to do is after the phone restarts, the phone,stayed and waiting me (with the green figure)

until i sow that another device "android" was not recognized at the devices place, so i again manualy installed it.

as google.inc , ZTE kernel debug interface.

look the photos if they help you..

sorry for my bad english writing.

image 1 www . filedropper . com / 1_5

image 2 www . filedropper . com /2_2

I Hope i helped you.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Welcome to decimalman's kernel playground!​

As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.

Features:

Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)

Underclocking down to 54 MHz, with stability improvements

Undervolting compatible with most apps

Fast charge without unplugging first

Glorious animations for the notification and softkey LEDs

Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)

freelunch and tierservative governors for optimal battery life without sacrificing responsiveness

Automatic mpdecision and auto-hotplug are only enabled when needed

Adjustable minimum voltage for stability on finicky processors

Optimized UKSM to free up some extra memory

Code optimizations for size and speed

Compiler optimizations (-O3, LTO, and more) because faster is better

Donors: Thanks, everyone! Your generosity is much appreciated. :good:

drpenguino, 0xScott, vmancini3 (twice! :good:), Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict

Remember:

Nandroid!

last_kmsg and/or logcat or it didn't happen.

Other kernels have their own threads or forums. Discuss them there.

Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.

Be silly. We're here to have fun.

Installation:

Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called. :p

Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).

Reboot.

Undervolting:

Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).

Downloads:

MediaFire:

All Downloads

dkp-vmin-XXX.zip

Solidfiles (Make sure you have an adblocker!):

All Downloads

dkp-vmin-XXX.zip

Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Bugs:

Let me know.

Stable changelog:

3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.

4/8/13 (3.0):

FauxSound support

Strip more useless stuff

A few bonus optimizations

4/8/13 (3.4):

Port everything except erandom from 3.0

Enhance cpufreq for easier configuration

4/24/13 (3.4):

Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.

Lots of CM/CAF/Linux updates

Working AssWax governor

Trinity colors support

sio, zen I/O schedulers

erandom is back!

Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness :p

Probably lots more, but there's hundreds of commits to sort through...

5/29/13 (3.4):

Bugfixes: better overclocking support, better hwrng support, etc.

Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface

Automatic auto-hotplug

New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain

6/14/13 (3.4):

Bugfixes: fix several critical bugs in the 5/29 release.

9/7/13 (3.4):

Fixes for OC, UV, auto-hotplug.

A few new optimizations.

Synced up with CM.

9/20/13 (TW):

Ported everything from AOSP to TW.

9/20/13 (4.3):

Merged 4.3 from CM into the existing 4.2 code.

Current experimental branches:

Nothing interesting at the moment.
[T-Mobile, Samsung Galaxy SIII] kruse1944:
Look promising :)
[T-Mobile, Samsung Galaxy SIII] decimalman:
Wow you're quick!

Let me know how it works for you. Happy flashing!
[T-Mobile, Samsung Galaxy SIII] kasinger:
Thanks for your work:good:
[T-Mobile, Samsung Galaxy SIII] darjama:
Is it just me or is the voltage table backwards, higher voltages for lower cpu speeds?
[T-Mobile, Samsung Galaxy SIII] akapaul26:
Am I missing something? Where do I dl d2tmo?

Sent from my Wicked fast SGS3!
[T-Mobile, Samsung Galaxy SIII] robertd0619:
You download the att one. Works for tmo.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Thanks for helping out. :good: I'll change the file name to be more obvious shortly.

Bizarre. The tables are all correct and should display correctly, but your app is probably expecting a slightly different format. What app are you using? I'll try to figure out what's going on.
[T-Mobile, Samsung Galaxy SIII] tsjoe2:
This kernel works great thanks I'm on pac rom. Thanks

aaaaaaaaahhhhhhhhhhhhhhh help me
[T-Mobile, Samsung Galaxy SIII] ayysir:
just took a look at your acpuclock tables, the first table uv to 1400000 but others don't match. nomal and fast should match up with one another from my experience. The multipliers seem good tho
[T-Mobile, Samsung Galaxy SIII] decimalman:
The tables I'm using are the stock tables from CM & Samsung (obviously with extra frequencies added as well). I've deliberately kept the standard voltage setup (minimum voltage, different voltage tables for each PVS bin, etc.), although by default I disable the minimum voltage during boot.

On the other hand, at 2106 MHz, the PVS bin probably doesn't matter, and all three bins probably need the full 1.4 V. My processor undervolts nicely, so I don't have a good sense for what voltage is required when overclocking. If anyone provides me tables that work for them, I'll update the higher voltages.

LOL the multipliers should be fine except the ridiculous 2.5 GHz typo that should never have been committed. :o
[T-Mobile, Samsung Galaxy SIII] ayysir:
hmm your correct just took a quick gander at cm's tables. I say try increase the voltages accordingly and see if it makes a difference in readings
[T-Mobile, Samsung Galaxy SIII] darjama:
I'm using set cpu. Thanks for looking into it.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I'm guessing this was an oversight on my part. I don't actually have the app, but I'm testing a bunch of fixes for a handful of different apps now. I'll push a test build (hopefully) later today that should get Voltage Control, Kernel Tuner, and maybe even SetCPU all working properly.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test build should get SetCPU working properly. If you get a chance, will you try flashing this test build and letting me know if it works for you?
[T-Mobile, Samsung Galaxy SIII] darjama:
That seemed to fix it, thanks!
[T-Mobile, Samsung Galaxy SIII] decimalman:
Great! If I don't run into any problems with the changes I made, I'll merge everything and it'll be in the next release.
[T-Mobile, Samsung Galaxy SIII] akapaul26:
I figured as much. But was not 100% thanks

Sent from my Wicked fast SGS3!
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Decimal the note3 is screaming your name man..
[T-Mobile, Samsung Galaxy SIII] decimalman:
The AOSP build worked fine for me, but apparently the TW build isn't booting for anyone. :( I'll look into it tonight.
[T-Mobile, Samsung Galaxy SIII] silverton:
I didn't notice any abnormal battery drain on 10/08 kernel for 4.3 running the freelunch governor, kind of excited to see what kind of battery life I get now.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I wish. :( Unfortunately, I'm broke, and the MVNO I'm on doesn't subsidize phones (or even offer the Note 3 yet).

New (fixed) TW test builds are on their way up. I actually tested them this time.

Changelog:

Fixed the freeze during boot.
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
You have it dude
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Yea
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
Aw i hate you right now lol
[T-Mobile, Samsung Galaxy SIII] razielpr:
I'm running the latest TW test build and it's running perfect but I have one question why not update the kernel to the latest version 3.0.99 or 3.0.100 why leave it at 3.0.31

infected to the bone T999.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Because I'm lazy. :p Good news, though: new TW test builds are on their way.

Changelog:

This happened.

Fixed the bug where frequencies show incorrectly. I think.

Finally updated FauxSound to the latest version. I forgot about TW when faux updated it.
[T-Mobile, Samsung Galaxy SIII] razielpr:
I'm running the latest version of the TW test build and so far it's running perfect one of my is going offline and the other is [MENTION=1089301]384[/MENTION]mhz so I think it's all good for now I will give it a day or two and report back THANKS FOR YOUR WORK.

infected to the bone T999.
[T-Mobile, Samsung Galaxy SIII] razielpr:
I just noticed that when the phone goes to deep sleep it freezes and I have to pull the battery and reboot.

infected to the bone T999.
[T-Mobile, Samsung Galaxy SIII] :
I have to say that this is the most underrated kernel out there. I've used KT before with mixed results. This kernel is rock solid. Bluetooth connects/disconnects quickly with no wakelock issues (as far as I can tell). Wifi is solid. GPS connects in lightning speed (no need for me to use any GPS mods). "Freelunch" governor just rocks!

Thanks so much for the awesome work, decimalman.
[T-Mobile, Samsung Galaxy SIII] silverton:
dkp-aosp43 2013-10-09 testing makes CM10.2 10/19 nightly go crazy. boot animation is all glitchy, phone is super slow and gets hot, the display almost seems like the colors are inverted but blink normal colors occasionally, and the app drawer is just stuck at the spinning loading animation and never shows the apps.
[T-Mobile, Samsung Galaxy SIII] :
Something weird happened today. I went to use the GPS to navigate around town. I use GPS Status to get a faster lock. Got the GPS lock and then went into Maps. Got my route, and as I started to head off, I heard "GPS Signal Lost". I went back into GPS status and it had to search for the GPS lock again.

Tried it again later - it seems to lose the GPS lock after a few seconds.

Logcat enclosed.
[T-Mobile, Samsung Galaxy SIII] decimalman:
CM updated the video drivers again. New test builds are going up, and the usual warning for updated video drivers applies: if your ROM hasn't merged in the updated drivers, do not flash this build; wait a couple days for your ROM's next build to come out. Anything built on 10/19 or later should be fine.

Changelog:

Synced up with CM
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Hey if you don't mind can you not put spaces in the zip name in the future? Rom manager can't flash those so I have to edit it every time. And thanks a million for the update, most kernel devs haven't updated for cm in a while!
[T-Mobile, Samsung Galaxy SIII] decimalman:
I'd like to address a few issues related to the most recent TW and 4.3 builds.

The most recent TW build includes a massive update from Linux 3.0.31 to 3.0.100. It exposed a number of bugs, mostly affecting the GPU driver. I am aware of them, and am working on them. In the meantime, I recommend not running the most recent build! The previous build is dramatically more stable.

The only change in the most recent 4.3 build was to support the updated, unstable drivers in the recent nightly builds for a few ROMs. These updated drivers break a few transition animations and cause frequent GPU crashes that require a reboot to fix. No other changes were made in the most recent build, and therefore the only reason why you should update is for compatability with updated ROMs. Please do not request that your ROM devs merge in the updated drivers. Asking your ROM devs to break their ROMs in order to support an otherwise identical kernel build is senseless.

Will do. It's pretty easy to change.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I think I tracked down the issue causing underclocking to get unstable. I've been running a minimum frequency of 54 MHz (at 725 mV!) for a few days now, without any obvious stability problems. Signal around here is awful, so I can't tell whether battery life has improved.

New 4.3 test builds are coming out. Feedback is appreciated, especially if extreme underclocking is unstable.

Changelog:

Underclocking (finally) added

Slightly tweaked freelunch defaults to work better when underclocked. Note that increasing overestimate_khz may prevent freelunch from using your lowest frequency.

Synced with CM, updated to Linux 3.4.67

Updated toolchain. I still haven't put my compiler laboratory back together, so it's still vanilla Linaro.

EDIT: Looks like I forgot to merge in the updated freelunch tunings. Oops.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
Is the 10/16 TW kernel the one to stay away from?
[T-Mobile, Samsung Galaxy SIII] leetone:
Does this kernel work for 4.1.2?
[T-Mobile, Samsung Galaxy SIII] :
4.1.2 TW yes. I'm running the 9/26 kernel as we speak on Dandroid 4.1.2.

I recommend staying away from the test builds and go with the 9/26 stable build.
[T-Mobile, Samsung Galaxy SIII] leetone:
Does anyone know how do I fix the static I am getting with my sound (speaker and headphone)? I have this sound static problem when installing this kernel and kt747 kernel.

Any help will be appreciated.

Edited: I'm using a TW Rom called Dandriod.
[T-Mobile, Samsung Galaxy SIII] Ch4m3l30n:
Hey dude, you definitely deserve some donations for your excellent work supporting the community with this kernel.

I sent some money your way. Hopefully others who have benefit from your efforts will do the same.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Thanks! :good: Donations and positive feedback are always greatly appreciated. :highfive:

Since you're having problems on multiple custom kernels, I suspect it's caused by a voltage issue. Try flashing dkp-enable-vmin.zip from the OP. I'll turn the stock kernel's voltage limits back on, which should sort out any issues that are caused by the lowered voltage limits in dkp.

EDIT: Sounds like this might not be the problem. I'm flashing over to TW to look into it.
[T-Mobile, Samsung Galaxy SIII] decimalman:
A few people have reported "static" or "crackling" audio on the TW builds. I haven't been able to reproduce this, so if anyone is having issues, a logcat and dmesg would be helpful to track the issue down.

I happened to notice that TW is a month behind AOSP features-wise, so clearly it's time for a new test build. There's also a new (hopefully) stable build for AOSP on its way.

TW Changelog:

Reverted the huge Linux update. I haven't tracked down why it breaks everything, so it's back to 3.0.31 for now.

Enabled underclocking down to 54 MHz

Borrowed a few CAF fixes for major security holes

Updated freelunch to the current AOSP version

AOSP Changelog since last stable build:

Enabled underclocking down to 54 MHz

Added "color temperature" setting in Trickster

Updated freelunch

Linux 3.4.70, updates from CM
[T-Mobile, Samsung Galaxy SIII] :
FYI: Just flashed the latest 11-21 AOSP 4.3 stable build on LiquidSmooth 2.37 and my phone couldn't find my IMEI information. However, a reboot brought it all back.
[T-Mobile, Samsung Galaxy SIII] terencebh:
Your SuperUser app may be outdated. I had the same issue and after updating SU it worked for me.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
I've had 4 lockups now since flashing the new TW kernel 4 days ago.

1st - touchscreen and menu/back buttons were unresponsive - held power to reboot.

2nd - screen went black - held power to reboot

3rd - locked up during shutdown, blue LED on, screen off - held power to reboot.

4th - galley locked up. The sliders of MicroCPU Monitor app continued updating but everything else was frozen - Rebooted via ADB. I have logs for this one. I can PM if you want them.

I'm running S3Rx ROM. The previous version TW kernel was running solid. I think it added ~20% to my screen time over the ATT MG2 kernel. Good stuff.

After the first two lockups I raised the min freq. from 54Mhz to 162Mhz.

After the 3rd lockup I raised the min freq. to 384Mhz.

After the 4th lockup (about 4 hours ago) I cleared data for the gallery app.

3 out of the 4 of my lockups have involved the gallery app so maybe there's something funny going on there.
[T-Mobile, Samsung Galaxy SIII] NeoWave:
Does this work with TW 4.3 ?

thanks!!
[T-Mobile, Samsung Galaxy SIII] decimalman:
Thanks for reporting this! :good:

Sounds like something in the kernel is deadlocking. I flashed over to TW to try to duplicate the lockups, but I haven't had any problems yet. Sadly, last_kmsg doesn't work well on TW, but I'll take any logs you've got.

EDIT:

Probably not. I grabbed the 4.3 sources, but I haven't started merging everything. TW 4.3 ROMs only showed up for Sprint a couple days ago, and I haven't grabbed one to test with yet.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Super-duper experimental builds for TW 4.3 are going up. I haven't run into any issues yet, but I've only got everything building an hour ago. Feedback is greatly appreciated, especially since it's Thanksgiving and everyone has more important things to do. :p
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
Here's 2 sets of logs. One extracted with ADB while it was locked up and the other taken with SysLog right after I rebooted.

Is this the best way to get logs to you? I was going to PM them to you but couldn't figure out how to do it. Either you can't attach to PM's or I'm a dummy. Probably the latter.
[T-Mobile, Samsung Galaxy SIII] imilleson:
Well I'm running stockMOD 4.3 for the t999 and I am in need of a better kernel than stock. I just downloaded the test kernel and am thinking of flashing. I'm sure the urge will become too great before the days end causing me to flash! Thank you!
[T-Mobile, Samsung Galaxy SIII] NeoWave:
SO far so good on 4.3 !! thanks!
[T-Mobile, Samsung Galaxy SIII] imilleson:
Same here! My reason for flashing was to improve battery life and to eliminate lag. So far I think it is helping in both aspects.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
I've been running 3 days without a hiccup now. After the last lock up I switched my scheduler from zen to row. Not sure if that would have anything to do with it or not.

I'm underclocked down to 162mhz now too.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
I knew this would happen. As soon as I wrote that everything was going great.

Unplugged from the charger this morning, checked some email, then went to click on the calendar widget and the touchscreen locked up. Unresponsive to touches.

The screen still appeared to be updating. Wiffi icon was indicating data traffic, MicroCPU sliders were moving around.

I pushed the power button and the screen went off, but I couldn't get it on again. Unfortunately I didn't check the other buttons first, home/back/menu. I would guess like before all the cap touch buttons were dead and the hardware buttons still worked, but that's just a guess.

Here's a logcat and dmesg is you're interested. It's a relatively short time of unplugged state where it went flakely on me, probably less than 10 minutes.

EDIT: zip deleted
[T-Mobile, Samsung Galaxy SIII] decimalman:
Another round of TW 4.3 test builds is on its way. There's a lot of bugs fixed, and I'd recommend everyone update. I enabled SELinux, but I'm open to the idea of disabling it again since it can be troublesome. If you flash over a kernel that boots in permissive mode, it'll carry over.

Changelog:

Re-enabled SELinux

Fixed frequencies not changing correctly

Fixed several bugs in the thermal throttling code

Fixed a few shortcomings in the hotplug management code

Fixed CPU initialization code not using the correct frequency

In the near future, I'll port most of these fixes to the 4.1kernel as well.
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
Had to go back to the 11/28 build because the 12/1 wouldn't boot
[T-Mobile, Samsung Galaxy SIII] decimalman:
Thanks for the heads-up. Looks like everyone except Sprint is having all kinds of issues with the new build. :( I'm going to look into it tonight.