yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DerTeufel1980:
That's normal. You can see the version by using cpu spy for example

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
Can I get some help with my screen problem?

All the colours have lost contrast/saturation. Please see my post above.

Is appreciate any help.

Thank you.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DerTeufel1980:
Maybe you changed something in the screen tab of trickstermod? If not, try changing things there.

There should not be any colour modification by default though

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
Nope, I haven't changed anything.

I noticed this change as soon as I flashed Devil Kernel. I've flashed Siyah but screen is still the same.

I've played about with the settings but I can't get my screen back to normal. I'll probably have to flash my ROM again.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DerTeufel1980:
Then it is not kernel related. There is no way, the kernel could permanently change your colors, after you flashed another one.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
But it happened as soon as I changed kernels. I didn't add any apps, change any settings.

Very confusing.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, it's strange. Did you reflash your rom?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
I'm just about to - I'll report back soon.

Sent from ThePureHeart's I9300 Boss Edition

---------- Post added at 12:01 PM ---------- Previous post was at 11:49 AM ----------

Flashed PA 3.15, flashed Devil Kernel again and colours messed up.

I'm not sure why this is happening - probably the ROM.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DerTeufel1980:
And just pa restored them? What kernel is included with pa?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
Yeap:)

CM10.1

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
Just to be clear, I am a PA user and I don't have this issue.
[Galaxy S III Original Android Development] Haano:
Lost-saturation? Mine did this as well when i enabled master sequence. So i disabled it.
[Galaxy S III Original Android Development] MuertoKo:
Actually that's the idea of Master sequence ;) Correctly calibrate the screen, and as the screen is way over saturated (if you are using Dynamic screen profile it simply set red to BURN) you lose that by enabling the master sequence ;)
[Galaxy S III Original Android Development] DerTeufel1980:
That's what I thought, too. But he said he didn't change anything...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
Isn't it applied by default with your kernel? Some kernels do and use init.d scripts for that if I remember correctly, maybe a silly init.d file but... still weird he keeps the efect after reflashing ROM on Cm 10.1 kernel, that shouldn'e happen at all...
[Galaxy S III Original Android Development] danarama:
He doesn't keep the effect does he? i thought he said it restores to normal.
[Galaxy S III Original Android Development] MuertoKo:
Might be but I can't really say it from his post. If that's the case then it is just having the master sequence enabled by default, and when he flashes a Master-sequence capable kernel it triggers. Can't remember if it was enabled by default on this ROM or whatever, but maybe Trickster is messing him, or any other Tweaking app that can change that value.

Anyway, he can just disable master sequence and all good again
[Galaxy S III Original Android Development] danarama:
You have to put all th posts together in a chain to see the answer unfortunately.

It's not the ROM, I know that for certain.
[Galaxy S III Original Android Development] DerTeufel1980:
No, by default the colors aren't modified by the kernel.

Most probably there has been an init.d script left.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
Nope - I used CM recovery to delete all init.d scripts then reflashed ROM & Devil Kernel

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] DerTeufel1980:
Have you checked if the master sequence setting got enabled ?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ThePureHeart:
I enabled it and disabled it - no change.

There must be a conflict with my specific device since others on PA ROM don't have the issue.

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] arsalanaly:
does it work on MIUI V5 on S3 ?
[Galaxy S III Original Android Development] RohanAJoshi:
Dev...

I realy want to use your kernel..

But please fix wakelock problem..

.

I tried 3 times on sammy rom and aosp, something keeping phone awake..

Not any app, cause i tested with full wipe also..

This is not happening with any other kernel.

.

Other users, please use bbs and check it.
[Galaxy S III Original Android Development] DerTeufel1980:
Were you using touchwake with delay set to 0 (=unlimited)?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
I have normal wakelocks.

If you use bbs, you should be able to see what wakelock you have. This is pretty salient information to have/give
[Galaxy S III Original Android Development] RohanAJoshi:
Touchwake not activated..

---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------

Actual that is problem..

See my screenies above, bbs only show mass wakeup but not showing it in partial, alarms or process..

And in battery under settings, it shows adroid os is higher drain.

Same in aosp and sammy, tried full wipe also..
[Galaxy S III Original Android Development] danarama:
There are no screenies.
[Galaxy S III Original Android Development] RohanAJoshi:
http://xdaforums.com/showthread.php?p=41164397
[Galaxy S III Original Android Development] danarama:
Hard to see anything when you have set it to "screen off". Really BBS needs to be set at Since Charged or Since Boot to give anything meaningful

Tried wakelock detector?
[Galaxy S III Original Android Development] RohanAJoshi:
Since start or since boot don't give you actual screen off wakelock, thats why i set it to screen off.

And i am talking about screen off wakelocks by android os.

About wakelock ditector, same as bbs, not showing mass wakeups, only normal wakeups.

Plz, you also check your screen off wakelocks.
[Galaxy S III Original Android Development] danarama:
It's useless. It only means anything if you show them in context to the whole device since charge / boot.

Wakelock means something stopping the device going to sleep so what wakelocks do you expect to see when screen is on?

If you set wakelocks to screen off, it keeps resetting everytime you wake up / sleep the device. It gives no context and means nothing. Perhaps you are actually reporting normal behaviour.

You don't get wakelocks unless screen off, because screen on means device awake, not trying to sleep. So no lock can prevent sleep.
[Galaxy S III Original Android Development] RohanAJoshi:
why I want to show whole from boot or unplugged if I can show you exactly from screen off ?

Of course, i want to reset it every time when screen is on, this gives me actual screen off result of that period, not whole.. its good for testing..

The main problem I explaining is unknown android os wakeups when "Screen is off"..

as you can see in screens, My phone's screen off for 13 min and it stay awake for 6 min.

Thats it, its clear, phone staying awake without any reason and this happen only with this kernel, not others.

.

Just forget everything and look at screen on time is 4s and awake time is 6m, thats big difference, in other kernels, awake time about to 30 to 40 seconds.

this is odd behavior i m talking about.

you can try yourself and tell me, reboot your phone, keep screen off for 15 min and check bbs.

compare results with other kernels.
[Galaxy S III Original Android Development] danarama:
Ok then. If you say so.

Yet problem follow you. Not rom. Hmmmmm

Well we cant help unless you supply descent info. Either set to charged or boot or forget about it
[Galaxy S III Original Android Development] RohanAJoshi:
K bro, tell me then what exactly you need ?

Screenshot from boot or since unplugged ?

Of how much time ?
[Galaxy S III Original Android Development] danarama:
Yes please, for as long a period as possible. All day of normal usage?
[Galaxy S III Original Android Development] DerTeufel1980:
new build uploaded

Kernel app (alpha stage): http://xdaforums.com/showthread.php?p=41346443#post41346443
[Galaxy S III Original Android Development] arhant:
hey will this kernel work on cm10 like on miui which is currently jb v4.1.1 ?
[Galaxy S III Original Android Development] Kord:
First thanks man for this great kernel!

Probably I have found a bug.

Actually I'm on CM 10.1 and on original CM kernel LED is much more brighter than on your Devil kernel. Also on Syiah kernel LED brightness was ok, like on stock ROM or CM kernel.

Thanks for any help!
[Galaxy S III Original Android Development] DerTeufel1980:
I'll check this

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] kabalix:
CM kernel is set brighter than original Samsung. In Yank kernel you can choose the brightness in aroma. It's not important option for me, just want you to know.
[Galaxy S III Original Android Development] Kord:
Oh, and there is another, visual, bug.

Instead of kernel version there is a text that says " unavailable " :)

Look at the SS, m8

http://db.tt/yeOFSCGg
[Galaxy S III Original Android Development] sherlock5545:
Is there a way to control the zram size with this kernel? With TricksterMod there's the option to enable it but no size settings is given.
[Galaxy S III Original Android Development] kabalix:
...

please consider this app as a preview, as it is also still missing some of my own kernel options (I'll add them soon).

Edit:

http://xdaforums.com/showthread.php?p=41346443#post41346443
[Galaxy S III Original Android Development] MuertoKo:
Hey Teufel, one little question, what might be causing a different behaviour on the GPS from this kernel to Perseus? It's quite hard to debug, but I'm completly sure it's kernel related. I tested playing Ingress (hardcore player here) and with this and perseus kernel it just... behaves different :S
[Galaxy S III Original Android Development] danarama:
Latest version?
[Galaxy S III Original Android Development] sherlock5545:
Oh sorry, I'm one version behind, gonna update now, then.

Sent from I9300 - Paranoid Android
[Galaxy S III Original Android Development] Rikul:
I m having lags on scrolling

Am i the only one.??
[Galaxy S III Original Android Development] ThePureHeart:
I've managed to fix the washed out screen issue!

I just had to change mDNIe mode to either Dynamic or Standard.

Currently using your kernel with your app. I've limited it to two cores and on devilq. Let's see how it goes :) great work (Y)

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] zodiaxe66:
Wasn't that fast, smooth and had a bit of microlag after flash, but after a few reboots,my gs3 is fast,stable and smooth as j-lo's butt..;)

After (only) 8 hours of use,i have no complaints so far..

Battery life,no idea yet:rolleyes:
[Galaxy S III Original Android Development] orangerot.:
Hey,

nice to see you back here on the GS3 :) Your S1 Kernel is still running perfectly with Helly Bean on my old S1 ;)

Now as you're here I wanna ask you something^^ Is it possible to add Dual-Boot to your Kernel? I'd love to have a Sammy Rom(cause of All-Share, S-Note[...]) and a PA(cause of halo^^) running on my S3.. Other Dual-Boot solution don't have those great features of yours..

Just a suggestion.. Would be great if you can add it!

Ah and one last question^^ Does ex-fat only work on samsung roms or on aosp too? :D
[Galaxy S III Original Android Development] zodiaxe66:
This is by far your best release yet.got the smoothness of siyah, but faster and this is after 10min of use..definitely a keeper.thanx:good:
[Galaxy S III Original Android Development] DerTeufel1980:
Nice to see you, too :)

Yes, I'll add dualboot for sure at some point. It's just modifying the initramfs, as the patches are already applied.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] orangerot.:
Perfect thanks! then we'll finally have a dualboot kernel which isn't missing other great features.. :)

And another feature to add came in my mind:

Did you think about adding xbox 360 controller support? I think it's funny to play games like modern combat 4, gta(...) with a real controller :D
[Galaxy S III Original Android Development] FadeFx:
Can't wait to see that, as i still depend on dualboot for some reason and can not switch from siyah as long as it is not available on other kernel...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] FadeFx:
Btw, anyone willing to test or already running my Scoobycntrol app on this kernel? id like to add it to the compat list on my thread

http://xdaforums.com/showthread.php?t=2156460
[Galaxy S III Original Android Development] rlorange:
Ditto! Would LOVE dual boot... need it!
[Galaxy S III Original Android Development] Kord:
This version fix lower brightness on LED?

I mean, in this version LED is brighter than in previous version?

Thanks for any help! :)
[Galaxy S III Original Android Development] danarama:
I dont quite understand.

Am I unsetting this settting, flashing the kernel, booting, then setting it again? even if I do not touch GPU?
[Galaxy S III Original Android Development] sherlock5545:
So do we use Devil tools or TricksterMod?

Sent from I9300 - Paranoid Android
[Galaxy S III Original Android Development] DerTeufel1980:
If you were using it before, voltage is stored as mV. Now the voltages are multiplied by 1000 again, to keep trickstermod compatible. If your old settings get applied, voltages are way too low, and device freezes.

It's up to you, which one to use

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Got you. So because I didn't use it, no need to do anything
[Galaxy S III Original Android Development] DerTeufel1980:
Yes

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] sherlock5545:
Is there a way I can save the kernel profile for TricksterMod? Whenever I flash a newer version of it, it always reset all the settings.

Sent from I9300 - Paranoid Android
[Galaxy S III Original Android Development] DerTeufel1980:
This is why I wrote deviltools

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] sherlock5545:
Alright, then I'm switching to it, thanks!

Sent from I9300 - Paranoid Android

---------- Post added at 05:19 PM ---------- Previous post was at 04:47 PM ----------

Isn't there an option to turn on the master sequence, using Devil Tools?

Sent from I9300 - Paranoid Android
[Galaxy S III Original Android Development] rlorange:
Dual-boot me up T! ;)
[Galaxy S III Original Android Development] TheFaixy:
this kernel has swap support for this?

http://xdaforums.com/showthread.php?t=1888081
[Galaxy S III Original Android Development] Kord:
According to my previous post about LED brightness and bug with "About Phone"

Sorry, my mistake, LED brightness is ok, but when battery is low Red Fading LED is less brighter than on CM or Stock and when I plug phone to charger LED is also less brighter than in other kernel. In fact, when in first time LED fades to red ( When battery is low ), there is a one brighter blink - and that's why I'm asked before about brightness level in this kernel, because i't looked like there is something broken with, I don't know, drivers or something :)

Or this is a feature of this kernel? If anyone knows it would be great :)

Second, there is a small bug with version of kernel, look ( If you seen this before, sorry - my bad :) )
[Galaxy S III Original Android Development] RuralGalaxy:
Last version working great! Nice work like always! :thumbup::D:beer:;)

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] torrentship:
Great work thanks.

Compared to the I9000, the Mic Gain is very high - I'm hoping that this is just a register in the Wolfson chip and doesn't need a huge amount of effort to change? Is there a quick way of hacking this?

Cheers again.

W>
[Galaxy S III Original Android Development] zodiaxe66:
:eek:

As this is based of Perseus kernel,i think all he has to do is enable it in devtool.

If i remember correctly.:confused:

Edit: i was wrong,it's in boaffla kernel you can adjust mic level.. .sorry:rolleyes:
[Galaxy S III Original Android Development] slaydown:
Sup guys i have a question , i dont have the ac charger , just the usb cable and the wall adapter and this adapter is 1,0A output , if i set to 1000mha the usb current charger it will works properly or i ill have any problem?
[Galaxy S III Original Android Development] danarama:
The usb cable + wall adapter IS the ac charger.

If you plug it into the ac mains with the wall adapter and usb cable, it will be 1000mah. If you plug into a pc, it will be 475. You can increase the pc mah but 1000 is way too much. Many pc USB ports aren't protected so pulling too much power can break them.
[Galaxy S III Original Android Development] jbejaranogarcia:
Last version Devil 0.20.2 as always (known in sgs1) so fast and smooth....

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Teura:
I seem to have bit of a battery draining problems with this kernel. Running PACman as my rom (4.2.2, AOSP / AOKP / PA-hybrid), and everytime I install this kernel my phone has problems staying in deepsleep.

Of the attached images, there's 4 images from BetterBatteryStats. First one shows the default kernel which has ~4,5% of waketime during a period one day and few hours, just for comparasion. Then I installed this kernel, and that is shown in second screenshot which has ~38% waketime during a period of 16 hours. Last two images show the wakelocks screens for Devil. The ratio between wake / deepsleep just isn't normal, and that causes extra battery drain I'd like to get rid of. While still keeping with this kernel, of course.

As for kernel settings, pretty much all I've done is enable master sequence (via Trickster) for better colors and some undervolting for CPU / GPU (via Deviltools).

If there's any more info I can provide, I'd be happy to.
[Galaxy S III Original Android Development] danarama:
I found my wakelocks reduced when I stopped undervolting, oddly.
[Galaxy S III Original Android Development] amirbd:
Hi

Thanks for the Kernel and your hard work

Does It work on UFME3?
[Galaxy S III Original Android Development] MuertoKo:
No, no kernel can posibly work until sources are released
[Galaxy S III Original Android Development] STAticKY:
Except siyah for some reason Lol. it runs, just. Well I should say it walks, no actually, it crawls. No idea why siyah boots these leaked roms but it does. I probably shouldn't be saying this though as people of lesser knowledge could get easily confused.

So to sum up. Siyah boots the leaked 4.2.x ROMs bit it is far from stable or usable.

So trust me when I say don't even bother trying.

I'll shut up now.

TP.
[Galaxy S III Original Android Development] danarama:
haha. I don't think what we see with Siyah fits with the definition of a working kernel.
[Galaxy S III Original Android Development] DerTeufel1980:
If it boots, but running slow, it's possibly related to the way cm handels vsync.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] STAticKY:
But stock is not cm???

TP.
[Galaxy S III Original Android Development] danarama:
Yes but it has components of both kernels in the source
[Galaxy S III Original Android Development] STAticKY:
I see

TP.
[Galaxy S III Original Android Development] DerTeufel1980:
In gokhanmorals source, there is just a decision between sammy4.1 mali drivers and the ones for all the rest.

Anyway, the vsync does not seem to be causing it... No idea then. Let's just wait for the sources

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rlorange:
OK so what I don't understand is that if you guys who are capable compile a test kernel which uses CM 10.1 Mali drivers instead of the old Sammy ones from 4.1.2... AND the kernel boots but runs slow because of the old drivers... then why doesn't it work with the new drivers?... CM 10.1 uses lib blobs from the leaked roms which matches the kernel derivers available already in the source for CM 10.1 so why wouldnt a kernel made this way work?
[Galaxy S III Original Android Development] STAticKY:
I think because that's not all that's broken/missinf

TP.
[Galaxy S III Original Android Development] DerTeufel1980:
Did you try placing the cm blobs into the leaked Rom, and boot it with siyah kernel?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rlorange:
No but they are the same blobs. CM trabsplanted them from the leak and prior to that from the 4.2.1 leak...

But wouldn't you need to tweak the kernel to make it use the newer kernel drivers on The Sammy ROM or would this happen automatically because it is a 4.2.2 ROM?
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, I need to modify the kernel for the leaked rom, initramfs is missing for it.

In siyah the initramfs is already added.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rlorange:
Googy tried without succuss... just a hope it might work because Siyah boots I hoped the CM 10.1 kernel drivers could be taken from the CM 10.1 side of kernel code and added to the Sammy side...
[Galaxy S III Original Android Development] Teura:
Didn't work. Still ~40% waketime with rest spent in deep sleep.
[Galaxy S III Original Android Development] danarama:
Can you post more up to date screen shots please? Perhaps one for each type? Alarms etc...

Looks like you're also using fast dormacy on a network that doesn't support it?

Also streaming music?
[Galaxy S III Original Android Development] DaReDeViL:
Yeah and i retried again yesterday with no success. I tried completing the ramfs and playing with kernel mali ... complete waste of time !
[Galaxy S III Original Android Development] rlorange:
Damn!! Well thanks heaps guys for trying so hard
[Galaxy S III Original Android Development] Scarface1991:
+1

In some Apps there is lag when scrolling. One example is when I use Dood`s Music Streamer and scroll through the list of songs it starts to lag. I tried to change the Governor and the lag would improve a bit but still it`s not what you call smooth. I think it is a Kernel issue because I tried the Googy Max Kernel and the scrolling lag was gone. This Kernel however gives me better battery life, so I can live with a bit of lag in some apps. More important is good Battery life.

This is the only issue that I have, everything else works great :)
[Galaxy S III Original Android Development] Teura:
As requested. I don't see any need for screens other than current, wakelocks and alarms since none of the others have anything relative to the drain. As for Fast dormancy, my network does support it as far as I am aware. For reference, previously I've had Ultimarom (Samsung 4.1.2) with Perseus, from which this kernel is derieved from, and I never had any problems with it.

As for what I did with this cycle, there was one longer conversation in Whatsapp and a couple of races in Carmageddon. Also no streaming or listening to music. Looking at ratios of deep sleep / awake / screen on, it still doesn't look the way it should.