yashsingh1/xdaforums huggingface dataset:
[LG Optimus Black] ttheodorou:
hello guys. i have a problem with my blacky that i want your help. my phone gone mad. what i mean is that every few minutes when i use my phone random things open and closes by their self.

for example if i am in es file explorer i see the phone scroll up and down entering files and opening option menu by it self. another example is when i turn on the phone is trying to unlock the screen by it self.

the problem started when i installed led notifications on izs rom (don't know if is a problem of the program). since then i re flashed the rom a few times even flashed other roms. when i changed the rom the problem was there expect two times that the problem appeared a few days later.

i have read somewhere that some users had the same problem when the phone was charging with a non lg charger.

has anybody an suggestions how to fix the problem???

anybody know if this is a hardware problem??

thx for reading my problem, any help is really appreciated!
[Samsung Epic 4G Touch] xpanmanx:
Hey gang, help me out here...

If I've got this right, we have three places from which to get GB27 (Keis nonwithstanding):

http://bit.ly/XcZWt2 -- garwynn

Available dls include unrooted/rooted/wipe/no-wipe/one-click

http://bit.ly/11nUQvc -- kobridge

Available dls include odexed/deodexed/zip

http://bit.ly/102OFLP -- crawrj

Available dls include odexed/deodexed/no-wipe/wipe/zip/tar

All of these devs say theirs is a 100% stock ROM except for root or deodexing.

I can see that if I want an unrooted one-click, Garwynn's the one. Likewise if I need a deodexed, no-wipe TAR, crawrj is where I begin. And if I want a deodexed ZIP, I can go with kobridge or crawrj.

Here's my Q: is that really all there is to it? Are these ROMs so similar in all other respects?
[Samsung Epic 4G Touch] -EViL-KoNCEPTz-:
They're all identical with the exception of root, odex/deodex and method of installation. The rest is exactly as Samsung released it. For future reference if a rom is labeled STOCK it would be just as the device would be had you never modified it from when you opened the box, with the exception of either injecting root, or deodexing the /system apps. Pure stock is odexed and unrooted, obviously.

☆SoA: Son's of Android™☆

I like to break stuff! :D
[Samsung Epic 4G Touch] xpanmanx:
Excellent. Thank you. I was just confirming that I had my head in the right place and not up my aaaaaaaaaaaaa.......whoa there! :)
[Samsung Epic 4G Touch] -EViL-KoNCEPTz-:
Lol.

☆SoA: Son's of Android™☆

I like to break stuff! :D
[Galaxy S III Original Android Development] DerTeufel1980:
This Kernel is based off the sources of AndreiLux Perseus Kernel (alpha35).

If you consider to thank me, please also consider to thank him http://xdaforums.com/showthread.php?t=1927852

This kernel supports only Samsung 4.1.2 and Aosp based roms up to Android 4.3.1

Android 4.3.x roms need to be installed as primary for now!

Many Thanks to:

- RichMD

- Gokhanmoral

- Andreilux

- DAGr8

- simone201

- ptmr3

- Stratosk

- RolloS

- kasper_h

- Philz (for his recovery source, although i had to implement my own touch)

- all the others mentioned in the changelogs
[Galaxy S III Original Android Development] DerTeufel1980:
more to come ...
[Galaxy S III Original Android Development] nfsmw_gr:
OMG! :D

Loved this on the i9000!

It's awesome to see it on the i9300 too!

I've got two questions though...

1)Trickster mod configures everything right now or some things are not configurable?Thanks for the STweaks support too!

2)You mention this is based on perseus...that means that screen calibration is available on devil kernel too right?is it configurable too like on perseus?

Many thanks man! :highfive:

EDIT:

Flashed right now and my questions were both answered.Sorry to spam,but i was on a stable setup and didn't want to ruin it. ;)

This kernel feels fast and smooth!

It rocks man,simply awesome! :)

EDIT 2:I just finished going through advanced configuration and oc/uv it.

Also i run some benchmarks,everything's good.

No bugs or anything so far too.

Could i make just one wish please?

Don't use the same audio engine perseus uses,it's a bit buggy(atleast for me) and doesn't have many more features than the one used in siyah...plus the latter one runs fine,so keep the one you're using now please. :)
[Galaxy S III Original Android Development] squirtsy:
Doesn't seem to boot on mcbytes rom without a wipe :(
[Galaxy S III Original Android Development] nfsmw_gr:
It works fine on ultima v12,i see no reason why wouldn't this work on mcbyte rom...?both are sammy based.

try to flash again mate!
[Galaxy S III Original Android Development] LovelyDay:
Not boot

Report

ARHD 25.0 using Devil Kernel Not boot :(

kernel Flashing before /data/.perseus delete and wipe cache and Dalvik Cahce

But Not boot
[Galaxy S III Original Android Development] proxuser:
Works fine with grisza monster beam 8.0

Installed with cwm without wipe anything
[Galaxy S III Original Android Development] ghul21:
Hi Dominik :D

Finally we have u here :p only thing i'm missing is the sign of the kernel in settings ,see screenshot. And one more, mybe some sharpness tweaks. Or i just miss this in settings ;) thank u for your work :thumbup:

Edit:

Big bug. Using the camera make reboot every time. Trying on two roms, both aosp. With previous kernel no problem :confused:

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
Can you please send me the last_kmsg after device booted up again.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Leicxan:
i flashed this kernel,but it doesn't support exfat..
[Galaxy S III Original Android Development] davtse:
Hope this helps. It also crashes when running benchmark applications like antutu benchmark
[Galaxy S III Original Android Development] funeralcrows:
+1 on sticking to Siyah's sound mod. Everything else is just buggy and doesn't really give any better sound.
[Galaxy S III Original Android Development] DerTeufel1980:
updated the op with a new kernel.

- added support for exfat (as long as it is working, it is fine for me. i am not going to miss improvements to keep compatibility to a propietary driver)

- higherd the mem reservation of fimc driver, to hopefully prevent camera crashes
[Galaxy S III Original Android Development] MuertoKo:
Good to know the "i am not going to miss improvements to keep compatibility to a propietary driver", you might already be aware of this or maybe I missunderstood it some time ago, but I think Andrei ported his kernel to Linux 3.4 (or 3.3??) and added a new i/o scheduler some time ago, but had to revert it back to recover ExFat compatibility... maybe worth cheking!
[Galaxy S III Original Android Development] scheichuwe:
Camera still crashes.
[Galaxy S III Original Android Development] davtse:
Camera still crashing, and when I try to flash back to my old kernel it bootloops. Flashing back to your kernel allows it to start up again. This is with cache/davik cache wipes.
[Galaxy S III Original Android Development] MuertoKo:
Please say if you are using CM or Sammy bases if posible (even with a last_ksmg is more than enough), just to let users as well as dev where are the posible bugs and trigger them to solve them with more logs :D
[Galaxy S III Original Android Development] davtse:
Erm.. I did upload a last kmsg if you notice.

Anyway, on AOSP slimbean rom
[Galaxy S III Original Android Development] scheichuwe:
I already did, but on another Forum. Sorry for this.

Here you are:

stock EMC3

https://www.dropbox.com/s/rc0fdeuueq86wts/last_kmsg.txt.zip

:)
[Galaxy S III Original Android Development] nfsmw_gr:
Hmm..weird things about the camera...

It works fine on my S3 on Ultima v12.
[Galaxy S III Original Android Development] STAticKY:
May i ask what the new tunable is and also where is the info on zzmoove? Do does it come straight from the repo? Because i cant find much info on it around theese ways..

Sent from my portable powerhouse
[Galaxy S III Original Android Development] DerTeufel1980:
zzmove is based off conservative governor.

mialwe was adding two lookup tables to it, to ensure fast up/down scaling, without the need of calculating target frequency. this also made it very smooth.

i think katoonz has added hotplug functions and named it zzmove

regarding the tunable:

all current governors are using the actual load to calculate up or down scaling.

now it compares the actual load with the previous one. if the difference is above grad_up_threshold, it scales already up, before the normal up_threshold is reached, assuming, that a steep change is causing to raise load above up_threshold anyway.

this means, the cpu is scaling up one sampling rate earlier. because of this, load should get reduced one sampling rate earlier, too. hence, no difference in battery, but smoother.

this got implemented by stratosk, to ondemand governor for i9000. i just ported it.
[Galaxy S III Original Android Development] Perka:
Zzmoove

http://xdaforums.com/showpost.php?p=40405578&postcount=603
[Galaxy S III Original Android Development] DerTeufel1980:
nice to see you around here :) did you solve your dma_cma issue? if not, cm has pushed a fix for it.
[Galaxy S III Original Android Development] dongfangri:
usb MTP doesn't work. Windows cannot find SAMSUNG_Android driver.

Kernel: Devil 0428
[Galaxy S III Original Android Development] DerTeufel1980:
Please try switching usb debugging on /off, reboot and fix_permissions.

I know about this sometimes happening for Note2, but for the s3 you are the first.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Perka:
Yes It got fixed, got a patch from yank555.lu :) now I battle with getting source compiled with Linaro :P lol
[Galaxy S III Original Android Development] DerTeufel1980:
Take a look at perseus github. He patched two days ago

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ZaneZam:
thx perka but in this case the relevant part is at the bottom of the source file :)

as stated there in fact it was me who made the modifications on top of mialwes smoove governor and called it zzmoove governor :)

HERE is the initial announce and HERE the announce for verion 0.3

anyways nice to see it here in this kernel too and nice to see that u devil have made stratosk's "momentum" modifaction which i had on the scope for the next version (0.5). btw. may i use your work and may i contact u per pn about some other questions? ;)

thx in advance

ZZ
[Galaxy S III Original Android Development] drew071:
Hi again. Just installed your new kernel on hellybean and I'm still getting freezes when scrolling through apps. especially on xda. Is there anything you recommend trying.I've tried a change in governor but it doesn't help.
[Galaxy S III Original Android Development] Hbohd:
Eagerly waiting for Stweaks support !
[Galaxy S III Original Android Development] DerTeufel1980:
Which governor and scheduler are you using normally?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] RuralGalaxy:
Nice to see you again in the S3! :thumbup::thumbup:

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] RuralGalaxy:
It's possible? Only charge 50% in 7 hours? :confused:

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] danarama:
Can be if your cable is bad. Can test using "Trickster Mod" from play "ignore unstable power detection" in specific > Charging control. I'm not sure if it's implemented though.
[Galaxy S III Original Android Development] RuralGalaxy:
The charger works good, with other kernels charge full battery normal...:confused:

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] danarama:
The detection seems to work differently across different kernels. Have you tried another cable? If not, do. Or also try what I already suggested. Then if you rule these out, perhaps you can provide some logs for the dev.

I had this issue with my Samsung cable on Perseus, as many others did too. That's why Andrei introduced the disable unstable charger detection.
[Galaxy S III Original Android Development] RuralGalaxy:
Ok, thanks friend, i will do some tests... But this kernel works great! ;):thumbup:

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Original Android Development] jbejaranogarcia:
I was a follower of yours in S1 and I'm glad you come to develop your kernel in S3.

Sure you go up the level of kernels on this device, which by now is high, but you will be even better.

Thanks a lot for your work Master! ;)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] amppen:
Hi! I was checking out this kernel for the first time and haven't had the time to go through this thread completely, but I can say a word or to about changing / disabling throttling temperatures even though it's a little off topic I guess.

First of all, it's not unheard of, when I had a HTC Sensation it was business as usual. I had a tweaking app called kernel tweaks or something, and with it it was possible to change three different throttling temperatures and throttle frequencies linked with them in many kernels, and I saw that different devs had different stock values for these. Sometimes I would pump the temperatures up a bit if I felt the dev had been too cautious when setting them, but I never experimented much with it.

My point is: it's possible and doable, but not sure if it's necessary or beneficial.

Texted with my Nokia 5110
[Galaxy S III Original Android Development] torrentship:
Hi,

Thanks for your work on this kernel and hellybean.

I can confirm jittery scrolling in xda app.

Is there any possibility for microphone gain control in dsp settings like there was on the i9000? Or must we wait for voodoo sound app to be ported?

Cheers
[Galaxy S III Original Android Development] Glebun:
Hey, just thought you should know - flashing your kernel yesterday (done it multiple times before) somehow messed up my EFS, and now I have nothing more than a paperweight, the service center says they need to replace the motherboard and it's out of warranty :(

Just kidding, of course I had a backup and it's all good now
[Galaxy S III Original Android Development] amppen:
LOL you're mean, I felt bad for you when I started reading this :D

Texted with my Nokia 5110
[Galaxy S III Original Android Development] danarama:
I've been running this for a little while now.

I must say, its definitely smooth. I'm just working out new undervolting levels as what I had on siyah is not as stable here. I do like it though. Can't wait for stweaks support. Trickster is getting annoying. Keep up the good work. It is appreciated. This is going to be a great kernel. Its my daily driver
[Galaxy S III Original Android Development] DerTeufel1980:
Maybe I am too dumb to use stweaks, but for me, it's not working well. It's taking ages to load, and it does not seem to realise, if i change the governor. It always displays the same governor settings.

Is this the way it works? Never used this app before.

If it is, I have to use my own app...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
It certainly does take ages to load on Non-Siyah kernels. eg Perseus, yep it takes a long time to open.

I'm really not sure about the governor. I set that as standard. I use SetCPU for all CPU and iops operations, including voltages anyway. I really use Stweaks for charging voltage, screen and audio adjustments etc.

If you're not fully supporting that, I'm cool with that - it's a great kernel but Trickster is a no go for me because every couple of reboots, it resets everything.

I'm actually happy to set everything else in innit.d, so if you get chance some time to document what can be done via terminal / bash, I'd love to see it

:)

Thanks again, good work!
[Galaxy S III Original Android Development] zodiaxe66:
Stweaks loading time depends on how many tweaks the kernel support..perseus take ages while Adam kernel loads immediately.if you got another app for controlling govenor/scheduler that is executed after stweaks and therefore these settings is applied..
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks for the information.

I didn't get your second part. What do you mean by the quoted part.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] amppen:
I'm sure he means that there is another option or tweak that sets governor to something else than the one that you choose in STweaks. Like another kernel manager app, an init.d script, the baked in performance control...

Could be anything that gets executed later during the boot sequence or after boot completed so that it will overwrite the option chosen in STweaks.

I like STweaks myself for the fact that it doesn't assume anything. It checks what your kernel can do and cannot do and gives you the options accordingly.

Texted with my Nokia 5110
[Galaxy S III Original Android Development] DerTeufel1980:
Ah, you mean, he answered in regard to my issue, with wrong governor settings showing? It wasn't an other app. I mean, I switched from pegasusq to lulzactiveq, but I still had the options of pegasusq displayed...

Anyway, what are the most important settings for you? Cpu oc/UV, gpu, charging, sound?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
For me, sound, display, charging.. I prefer set cpu for cpu stuff
[Galaxy S III Original Android Development] DerTeufel1980:
Why setcpu?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
I always used SetCPU because I like the widget. I bought it for the widget and the profiles (which I don't use so much any more). Initially the voltage control was better than stweaks too. Stweaks has caught up, but since I want SetCPU controlling the CPU anyway, no point splitting CPU control over multiple apps.
[Galaxy S III Original Android Development] zodiaxe66:
Extweaks (by xan & GM) was my prefered tool,but xan was gone for a while and couldn't update the app, so GM made stweaks..

Andromizer has become quite good too.. but is more an overall tweak tool

Sound/screen/voltage control,i don't care about oc,this phone is monster fast at stock clock speed..

Thanx amppen,that was exactly what i meant.
[Galaxy S III Original Android Development] amppen:
I've been on Temasek kernel for a long time, but I'm curious about this one, I think I'll make a "deal with the devil" at some point LOL. With Temasek's I've been using STweaks for UV, ABB, charging, audio, screen, CPU hotplug, I/O and whatnot.

The devil has quite a many interesting features :good:

Texted with my Nokia 5110
[Galaxy S III Original Android Development] RohanAJoshi:
This is best kernel for cm, using it...

Thanx dev..

Mainly its solved speaker distortion problem in cm by tweaking sound dsp..

.

Found one unusual bug..

U kept phone on charging, but did not update battery percent while in sleep.

Rebooted and came to real stats.

.

Is there any way that we can take backup of trickster settings ?

In stweaks, we can take backup of default profile from data..

.

Waiting for update
[Galaxy S III Original Android Development] DerTeufel1980:
I am making my own app. I am not satisfied with trickster nor stweaks...

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

I've had to go back to siyah for some testing. Had some stability issues (black screen, blinking led) which I never had before. Just need to confirm it doesn't happen on siyah first. When I come back, what is your preference for a proper bug report? I have to pull the battery. Is a last_kmsg sufficient? After battery pull?
[Galaxy S III Original Android Development] RohanAJoshi:
That's nice...

.

Between my gf just said that my voice coming too low to other side when I m on on call and Sammy's headset with mic is connected, I need to speak more loudly..

Its not happened with tema's kernel..

Plz do something about that..
[Galaxy S III Original Android Development] DerTeufel1980:
Did you overclock or undervolt?

After battery pull, there is no last_kmsg :(

I didn't change in call volume. Maybe there is a mod in temasek kernel?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] .c0dy:
I had this too with CM/AOSP/AOKP ROMs. Didnt thought it was kernel related as i had this a few months back too. Thats why im still on Sammy Rom

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Yes I did undervolt. At first I thought this was the cause so I gradually started raising the voltage. I had the issue again at 875 mv for 200mhz. I know its a different kernel but on Siyah I am at 825 mv with no issue but I know voltages differ across kernels.

I'm just going to confirm siyah is stable at these voltages for a week before I come back and do some more testing. When is last_kmsg wiped? At android boot? Can I adb pull via recovery?
[Galaxy S III Original Android Development] DerTeufel1980:
Well, i don't think undervolt is useful in any way... If you get one crash because of this, you already have lost more than you can save.

Regarding the last_kmsg, it does not get deleted. The kernel is constantly writing to proc/kmsg. In case of a kernel panic, the last action before the reboot is to copy the kmsg to last_kmsg.

In your case, this copy does not take place

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] RohanAJoshi:
I m using this kernel from yesterday, nice experience...

I did same undervolt with cpu, int, mif, gpu as i was on tema and perseus..

No crash or anything, working smooth..

.

Yesterday i had doubt that my phone no sleeping, but today its confirmed.

.

Android os is keeping phone awake without any reason..

I have same apps and same settings as i was on tema kernel..

Specialy, bbs and other apps are not detecting actual process of wake, only showing waketime.
[Galaxy S III Original Android Development] DerTeufel1980:
Please make a nandroid of your system, and perform a wipe, just to be sure, it's not app related.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] RohanAJoshi:
Yes, i did and failed..

Then tried to return on tema's kernel, failed, got in bootloop..

Finaly restored boot and system from nandroid..

Edit : i just restored boot and system, and no more android os wakelocks..

Confirmed that its kernel related.
[Galaxy S III Original Android Development] DerTeufel1980:
You still can reflash the kernel. It does hold own wakelocks, which don't get summarised to android.os

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Well Same happened on Siyah.

I'm back now ;)

I will try without undervolting at all (Standard voltages). Hopefully it is undervolting that is the causem because if not - no idea what it can be.
[Galaxy S III Original Android Development] ThePureHeart:
I just flashed this - performance is nice!

My screen colour however looks... well it looks flushed, very little contrast. It's okay for a few seconds after boot, but the my screen refreshes and all the wonderful colours go away :(

Trickster mod drops settings after a few reboots - can't wait for your own app! :)

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Original Android Development] danarama:
Damnit, it's not undervolting. It's happened again on standard voltages. Happens when "sleeping". Just doesn't wake. Black screen. Sometimes Blue flashing LED. Battery stats make it appear off.

I don't think its the kernel as it's happening with Siyah now too. I'm sorry for this Off topic, but anyone got any ideas of how I can find out what's causing it? maybe I just need to write a tasker task to write kmesg. I had this before.
[Galaxy S III Original Android Development] Haano:
Going to use this kernel for a few days instead of yank. Will let you know how it goes!

Edit

Flashed this on PA 3.15 and under kernel version it says unavailable??