yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] danarama:
No it doesn't look the way it should. You do have a lot of network stuff though, Multidpd. Your secril should no way be that big. I'd recommend trying turning off fast domancy using the fast domancy toggle to see if ti makes any difference to that particular wakelock (by comparison, the biggest mine has been is 3 minutes).

As for what else is happening there, I can't really tell.

multidpd eitehr means you've downloaded a lot, or your phone keeps polling teh network to check for a new ip address. At home I combat this by setting a static IP.
[Galaxy S III Original Android Development] Teura:
I disabled FD now, let's see how it goes. Network usage for that perioid wasn't even that high actually, less than 10 megabytes total. But anyway, thanks for your help this far :)
[Galaxy S III Original Android Development] danarama:
There's something happening behind the scenes. I'd doubt fd accounted for much
[Galaxy S III Original Android Development] nfsmw_gr:
DerTeufel1980, any updates you're working on?

I think normal perseus is a bit dead since Andreilux got his S4...:/
[Galaxy S III Original Android Development] DerTeufel1980:
My work does not depend on what andreilux is doing.

I am about to finish my dualboot kernel for the note2. After this normal development will take place again

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Scarface1991:
I hope that you will take a look at the lag when scrolling in some Apps. For example in the XDA Developers App or the Android Hilfe App.
[Galaxy S III Original Android Development] nfsmw_gr:
I didn't mean it to sound like that, sorry.

Okay, i'll be checking the thread as always. :)

Thanks for your work.
[Galaxy S III Original Android Development] lorenzo220580:
I want impruve my battery drain but i don't know how:somebody can help me?

I'm using davil kernel on paranoid android .

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Scarface1991:
Download the DevilTools App and make changes to your CPU like Underclocking and Undervolting. I underclocked my CPU from 1400Mhz to 1200 Mhz for example. You could start to undervolt by -25 mV , if that goes well go to -50mV and so on. It will become unstable at some point and Android will freeze. So go slow when messing with undervolting. Some people can even go to -100 mV but I wouldn`t recommend it, so try -25mV or -50mV. Do a Nandroid backup before starting with CPU tuning.

Also download the Greenify App and hibernate Apps like Facebook or Google Maps which both are known battery-drainers.
[Galaxy S III Original Android Development] lorenzo220580:
Where can i find daviltools app?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Scarface1991:
Right here: http://xdaforums.com/showthread.php?t=2276036
[Galaxy S III Original Android Development] danarama:
By reading post 1..
[Galaxy S III Original Android Development] DerTeufel1980:
updated kernel. changelog post 2
[Galaxy S III Original Android Development] danarama:
I think I love you..
[Galaxy S III Original Android Development] ThePureHeart:
I think I love you too :') :3

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
Next time I hear "Where is the love?" by Black eyed peas on the radio, I'm gonna shout out this URL :)
[Galaxy S III Original Android Development] lukaaa47:
i have FC with gallery and UCCW with new kernel update, also huge battery drain by android OS (1h~20%)
[Galaxy S III Original Android Development] nfsmw_gr:
I can't seem to find display settings in devil tools...

Are the controls not implemented yet?

EDIT:

Any chance to enable stereo downmix for speaker?

Lots of songs sound very bad if only one of the two channels play...:(

Also a weird thing...i tweaked the speaker amplification offset and the control dissapeared right in front of my eyes!

It's not there anymore...o.O

I'll reboot and post back.

EDIT 2:

Found the cause.

I rebooted and the control was there in devil tools, i set it at +2 and it was still there, but when i set it at any minus value the control dissapears afterwards.

Can anyone try this too to confirm it?
[Galaxy S III Original Android Development] Scarface1991:
Thanks a lot for the update. Very smooth and fast so far with Temasek`s latest CM10.1 ROM. Too early to say something about battery life.

However the scrolling in some apps like the XDA Developers app is still very laggy for some reason.

Can confirm huge Android OS drain (higher than display drain) but I did a full wipe before updating to Temasek`s newest ROM so I will let it settle over the night and see how it`s going to be tomorrow. Too early to say now.

I don't know, is the Android OS drain connected to the Kernel or the ROM? Or even both?

[MENTION=4196889]DerTeufel1980[/MENTION]

Since your kernel is based on the Perseus Kernel, do you think it would be possible to port Andrei`s Sound Engine to your Kernel or is there no interest from your side? Your Voodoo implementation is great but Andrei`s Sound Engine gives the best music quality without distortion in my opinion.
[Galaxy S III Original Android Development] lukaaa47:
Can anyone try this too to confirm it?

Me^^

Since your kernel is based on the Perseus Kernel, do you think it would be possible to port Andrei`s Sound Engine to your Kernel or is there no interest from your side? Your Voodoo implementation is great but Andrei`s Sound Engine gives the best music quality without distortion in my opinion.

I personaly like this way more ...

...another thing i noticed on this kernel is that music player uses CPU whole the time (im using apollo)..that drains battery pretty fast?
[Galaxy S III Original Android Development] Scarface1991:
Scratch the Android OS drain. It was caused by the ROM. I switched to the Sentinel ROM for testing and Android OS drain was gone.
[Galaxy S III Original Android Development] alirezaafkar:
I'm on Carbon ROM and when i flash this kernel ADB root doesn't work for me ! just APP root works ! any solution ?
[Galaxy S III Original Android Development] lmulli:
I take it that you have set it up for root access for both app and adb in dev options in settings? Also if that doesn't work change your computer connection from MTP to ptp in storage on your device - I couldn't get root through adb earlier and changing this solved the problem. (I'm assuming that USB debugging has already been ticked)
[Galaxy S III Original Android Development] nfsmw_gr:
[MENTION=4196889]DerTeufel1980[/MENTION]

Are you busy mate?

Could you take a look at the issues i reported earlier please?

Thank you. :)
[Galaxy S III Original Android Development] alirezaafkar:
Unfortunately it didn't help

After flashing this kernel I haven't root access in developer options but with other kernels it's there
[Galaxy S III Original Android Development] MrxSiN:
2ghz.. Safe?
[Galaxy S III Original Android Development] danarama:
Safe? Depends on the voltage. Voltage causes heat. High clock + heat = physical damage

Stable? Unlikely.

You've been here a while. I'm surprised you had to ask :)
[Galaxy S III Original Android Development] MrxSiN:
quite suprise that y im been asking y there will be 2ghz on i9300. Even on 1.8ghz not stable. y push it to 2ghz.
[Galaxy S III Original Android Development] danarama:
Maybe stable for some, but a very VERY small amount of people.
[Galaxy S III Original Android Development] lukaaa47:
http://xdaforums.com/showpost.php?p=41338478&postcount=1

Can u pls solve issuw with androod os.... Ur kernel is fantastic but this is really bad thing and im forced to change kernel for now
[Galaxy S III Original Android Development] guillots:
hi, im new with this kernel...there is an option to undervolt all values at the same time?
[Galaxy S III Original Android Development] danarama:
This is a bad idea. You must set each value individually. I would also recommend setting min and max to same clock speed that you just modified and stress testing... withheld 200mhz you also want to leave it idle for long periods to test
[Galaxy S III Original Android Development] guillots:
thanks for the advice,

i dont understood when you said "setting min and max to same clock speed"
[Galaxy S III Original Android Development] danarama:
So normally min clock is 200mhz and max is 1400mhz. If you change voltage for 400mhz, you need to ensure the voltage is stable at 400mhz under load. So to do this, you stress test...

However, if you stress test a CPU, it will ramp up to Max 1400 so you haven't really tested 400 at all. What you have to do is set min and max to 400 to stress test it properly...

Then you change voltage at 500, so you set min and Max to 500 and stress test. Do this for each frequency you're changing. If it reboots or freezes, the voltage is too low.
[Galaxy S III Original Android Development] RuralGalaxy:
For me this kernel is great! But drains the battery.... I don't know why, my friend jbejarano had 5 hours screen....

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] danarama:
Instead of people saying "this kernel drains the battery", could they please provide bbs results or something contextual?
[Galaxy S III Original Android Development] RuralGalaxy:
I feel that... I don't know the reason! But I use this kernel, because I like it, I hope with some cicles will go better! It was great with S1 good moments.....

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] lukaaa47:
i did but got no reply
[Galaxy S III Original Android Development] ThePureHeart:
No, you didn't. You provided screenshots.

Please visit the bbs thread to learn how up get a proper log.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danieleb89:
Sorry but with aosp&sammy you mean that it works both with aosp roms and for example latest Samsung leak?

Inviato dal mio GT-I9300
[Galaxy S III Original Android Development] RuralGalaxy:
I'm using Miui v5 Note2 Edition by Muchopoli. I will put screenshots of next cicle.

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] danarama:
Same as all other kernels. Samsung 4.1 2

there will be no samsung 4.2 kernels until samsung release the kernel source code, some time after 4.2.2 is official
[Galaxy S III Original Android Development] insanix:
This is probably best kernel till now combining display, speed and battery life. Battery life is abnormal! I don't know about sound much and only one bug exists when connected on win7 it is not recognized as MTP though easily bypassed using the UMS 1.8 app.
[Galaxy S III Original Android Development] Teura:
Again I'm back here with two new problems. The new kernel version fixed all my wakelock problems, and I'm happy now with ~5% waketime and rest in deep sleep. But it brought new problems also.

First is that when the phone isn't in deep sleep, it's 4 cores @ 1400 MHz. There is minimal usage for states 800-1300 MHz and rest is in 1400 MHz. States 200 - 700 MHz are completely unused. There's two screenshots from BBS attached, first showing the now normal deep sleep / wake ratio, second is from CPU states showing how it's only the highest state that is used.

Second is that for some reason, my computer doesn't recognize my phone with the new kernel. Phone normally starts charging when I plug it with USB, and the battery screen reveals it is recognized to be charging via USB. But my computer shows no indication of having connected to the phone. Running W7, and there's no sound for new device plugged in, and ADB can't find the device either.

As for the specs, they were PACman (4.2.2, 31.05 nightly) with 29.05 version of this kernel.
[Galaxy S III Original Android Development] danarama:
Are you sure you haven't accidentally set min to 800?

What governor are you using?

I'm using devilq with pacman 28th may and use full range 200-1400

If you flashed rom and kernel at same time, hard to tell what the problem is. What previous version of pacman did you have? Maybe flash that back with this kernel and test
[Galaxy S III Original Android Development] Teura:
Minimum is set to 200 as it should, and gov is devilq. Previous version of the rom was from 27th, and both the new nightly and kernel were flashed in the same go. But I'll try with the previous and see how it goes.

Edit: Flashed in 27.05 nightly, both problems still persist.

Edit2: Seems that CPU usage never goes below ~25% while the phone is awake, and that seems to be keeping the frequencies maxed. Looking through terminal emulator, Process #1, /init, is the one eating the CPU.

Edit3: Digging even deeper, it seems that both of the bugs I listed might be related. I'm finding references to old bug where /init was eating all cpu. It'd stop if USB debugging is turned on, but problem is that I can't seem to turn it on. I usually have it on all the time, but now when I turn it on and reboot, it is again turned off. Probably it never even goes on, since I remember Titanium Backup whining that it is missing after I had it turned on. And during all this, the computer still doesn't show any indication of phone being conneced to it even though it is (and I've reconnected it several times, so it's not that either).
[Galaxy S III Original Android Development] spakkkk:
[MENTION=4196889]DerTeufel1980[/MENTION]

r u planning to "port" last perseus settings like abb into your kernel?

i did a bootscreen for your kernel@i9000, u will use my wonderful work in this kernel? eheh joking
[Galaxy S III Original Android Development] RuralGalaxy:
Here mi last cicle....

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] danarama:
Ok so this problem is specific to your handset. Perhaps a full wipe and format of sdcards is in order.... I have 28th nightly and latest kernel no issues
[Galaxy S III Original Android Development] Teura:
Decided to give it a go. Backed up my current system, and then did full wipe from recovery (Philz), including a format on /sdcard. Then I installed nightly from 31st, gapps and devil from 29th in that order. After that I booted, went straight to terminal emulator and it's still there, /init eating 25% of CPU while Performance Control shows 1400 MHz constant. And computer shows no signs of recognizing the phone when connected via USB.

Guess I'll retest with nightly from 27th that I also have. With the previous version of this kernel (13th of May), that build worked fine except for the constant wakelocking. Which I also experienced with older builds, so they were not specific to that build.

Edit: Same behavior with 27th. Again with full wipe and /sdcard format. One last try with 28th as it seems to work for you.

Edit2: Still no dice with 28th. Afterwards, I again wiped / formatted and installed just 28th and gapps with no devil, and there was no /init drain, cpu speed was as it should and computer immediately recognized the phone. So it really has something to do with the kernel.

Edit3: And once more, I again installed 31st and gapps. Booted and verified everything was ok. Back to recovery, flashed Devil (29th) and it still works just fine. Intrigued by this, I went back to recovery and installed all three again in the same go and bam, /init drain with all the other symptoms is back. So I really can't say anymore where the problem lies, except that if I install rom and kernel on separate visits to recovery, it will work fine. So guess I'll do that from now on :D. Sorry for all the trouble.
[Galaxy S III Original Android Development] invinciblecc:
When u say it works on boh aosp and sammy doss it mean jt has dualbooting too though I doubt there will be but still asking
[Galaxy S III Original Android Development] MuertoKo:
Yep I did notice, that's why i stated it's enough with a last_ksmg, was using you as a good example of bug reporting actually, sorry if I expresed myself wrong :)

It's just to avoid people thinking camera is having issues on Sammy based rom's in case it doesn't or something like that (not the case I think, EMC3 reported to have issues just 2 posts above :P)

---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------

What camera are you using in Ultima v12? It has a bunch of cameras to install in Aroma if I'm not wrong
[Galaxy S III Original Android Development] davtse:
ah... no worries. I was more concerned that the file didnt upload properly or something. Cheers!
[Galaxy S III Original Android Development] ghul21:
Camera crash on aosp roms. No matter if u using system or third party app. For me no ksmg log file :confused: even with terminal. No Such file or directory :( i'm not at home to make full adb logcat

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Logcat probably won't help because it doesn't include what the kernel is doing.
[Galaxy S III Original Android Development] nfsmw_gr:
Unfortunently ( :P ) the stock official one,as the other modded apks make the camera lag on my phone(with any kernel).

---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------

@DerTeufel1980

Also btw when i flashed the new version,trickster mod settings reseted to default.

Was that supposed to happen?Could you warn us next time,or disable this? :)

Also the multicore power saving and the input boost frequency should be only enabled using all governors except pegasusq,which is Andreilux's custom governor and those two settings conflict with the governor i think.

Don't get me wrong man,i'm just trying to help make this better nothing else,i loved it on my S1. :)
[Galaxy S III Original Android Development] LovelyDay:
Nothing Boot.. please solution..

0.6 version and 0.8 version not work...

i use Andrioid Revolution HD 25.0

CWM 6.0.31

flaahing success and reboot now

Samsung GALAXY S3 logo and Screen Off and repeat S3 logo lotation...

i have not use kernel.. :(

Help me
[Galaxy S III Original Android Development] DerTeufel1980:
well, this is a weird issue with the camera....as i have built it on top off perseus source (which is i9300 by default), with added aosp/sammy support from gokhanmoral (which also is s3)...but there are no issues for note2...lol

please try this new one now
[Galaxy S III Original Android Development] WiwiPouPou:
Totaly agreed!
[Galaxy S III Original Android Development] DerTeufel1980:
trickster mod is not written by me. it seems to reset itself, if the kernel version changes, to prevent issues.

i have reverted andreilux lcdfreq boost modification, which was the one, conflicting with touch boost. i prefer touch bosst, as it is availble for all governors, not only pegasusq
[Galaxy S III Original Android Development] LovelyDay:
Uhmmm Same

Boot logo - Screen Off - Boot logo - Screen Off :(
[Galaxy S III Original Android Development] davtse:
Still no luck. Camera crashes.
[Galaxy S III Original Android Development] DerTeufel1980:
Thx. Found the issue. Next update in few minutes is going to fix it

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] nfsmw_gr:
Hmm...i see.

Thanks for pointing those out. :)

I'll just wait for the STweaks support then!

Also i'll try to backup with titanium backup and restore trickster mod after i flash the next version.Hope that works!

There are too many settings to tweak every single time...:p
[Galaxy S III Original Android Development] DerTeufel1980:
cam should be fixed now. thx to cm team for the commit, me was missing ;)
[Galaxy S III Original Android Development] davtse:
Fix confirmed! will be testing it for a while.

About another issue, I tried flashing back to my original kernel just now but had bootloops. But reflashing your kernel allows me to boot back up, any idea why?
[Galaxy S III Original Android Development] DerTeufel1980:
No, I have no idea. The kernel does not permanently change anything.

Maybe it's to prevent users from flashing back :P

Which kernel was it? Samsung or aosp?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] davtse:
AOSP kernel. I noticed the same thing with NEAK a while ago. Needed to reflash the system to be able to reflash other kernels again.
[Galaxy S III Original Android Development] Leicxan:
Flashed 12.11，exfat still broken and camera is not working...I'm using stock XXEMC2 with jkay mod

sorry for my english..
[Galaxy S III Original Android Development] FD10:
This also happens flashing another kernel when you have Boeffla and don't use wipe options in boeffla app...

DerTeufel1980, what do you mean by saying "Reverted LED Control"?
[Galaxy S III Original Android Development] davtse:
I'm guessing the boeffla wipe is not just a simple cache+davik cache wipe? because I do that religiously before every kernel flash but no avail. But good to know that there is a solution.
[Galaxy S III Original Android Development] Teura:
No doalboot in this kernel. When it works on both it just means that the same kernel can be used in both Samsung 4.1.2 and various 4.2.2 roms (but not the Samsung leak).
[Galaxy S III Original Android Development] insanix:
No MTP bug!

On another win7 box I connected today it was instantly recognized as MTP and really fast too! So there is no bug, probably some problem at the two other windows 7 boxes I tried last week.
[Galaxy S III Original Android Development] DerTeufel1980:
Sorry for not posting last few days. At first my device got broken, now my pc (which is even more bad, because i cant code anything for now :( )
[Galaxy S III Original Android Development] ThePureHeart:
If we can help, please let us know

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you very much. At first i need to know what is broken. Guessing it's the power supply or Mainboard. ..

Last thing i did was putting the pc into energy saving mode. Maybe it's a sod :p too bad i cant pull the battery ...
[Galaxy S III Original Android Development] nfsmw_gr:
Take a look at this article.

I hope it helps you. :)

http://www.pcworld.com/article/41661/article.html
[Galaxy S III Original Android Development] Teura:
It seems that I just can't get everything working with this kernel. First I had the wakelocks, then the latest kernel update brought me the /init drain which I solved, though with /init there was no wakelocks at all. But immediately after solving the /init drain, the wakelocks are back.

Again there's a dump of images from BBS, showing the unusual ratio between deep sleep / awake, with the relevant subpages. Still running PACman (4.2.2, nightly from 31st) with Devil from 29th.
[Galaxy S III Original Android Development] danarama:
Logs?
[Galaxy S III Original Android Development] ThePureHeart:
What is it with people thinking it's okay to post screenshots? Lol

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] Teura:
What is is with people thinking that everybody knows as much as you do?

Which logs you want?
[Galaxy S III Original Android Development] ThePureHeart:
Goodness, can't make a joke on here without people crying.

Charge your phone to full.

bbs - settings - Dumpfile - select all. Enable root features.

Unplug and leave alone for at least 4hrs so bbs can give an idle log (necessary). Then open bbs, press the share button and select 'text dump'. Post that log file here.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
Screenshots are a good start, but sometimes we need more... The logs may give an indication where the problem is where in this case, the screenshots only say "yep, there IS a problem"
[Galaxy S III Original Android Development] habylab:
Wow, this appears to be the ultimate stock kernel, seems to be so cutting edge, love it!
[Galaxy S III Original Android Development] bajica:
When can we expect updated version, there is new cm kernel with update9 sources with new emmc fix