yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DerTeufel1980:
the logcat is showing an error about cam...i just dont have an idea right now. thank you for the logs

yes, please always get last_kmsg and logcat, if something strange happens.

cleancache and zram are still enabled by default (by andreilux), but i am not sure, if ill keep it this way.

i am unsure, if devices like s3 or even note2, really need things like this
[Galaxy S III Original Android Development] hanspampel:
Yep Video playback doesnt work correctly. Batterydrain is very high. 1.8-3.5% per hour. Normal by is 0.3-0.9%. Btw the deep sleep of that kernel is not really good. I get only 30% of DS. In other Sammy kernels, like my previous one from AndreLux, Alpha 35, i got over 90%. Maybe somone hold the S3 awake to never go to sleep.

But i must say, i think my S3 is a little bit snappier as with other kernel. I hope you sorted it out.
[Galaxy S III Original Android Development] DerTeufel1980:
I can't do anything against any bug (like video playback) without the needed logs.

Please, if there is something wrong, always get a logcat and last_kmsg (this one, after you do a reboot) .

And please also always post, if samsung rom or aosp based. I don't know all these roms. Just the name is no information for me

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] davtse:
Which would help for the deep sleep issue? Logcat or Last_kmsg?
[Galaxy S III Original Android Development] DerTeufel1980:
Against deep sleep, normally a data wipe. :P

You can try to find details by using the app: better battery stats. Please don't ask me how to use it. I don't know. I just know, it might help.

The logs are needed for cam/video fixes

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
No battery drain issue at all, and yes, normally a wipe fixes it :P (FULL wipe, no cache no dalvik placebo stuff).

Devil maybe could be a good idea to put some words on OP claiming how to report a bug? (not a full tutorial, there's a post for that, but at least something like a little formular, "ROM type: AOSP / Stock ; Issue: XXXXXX; Logs: XXXXX)

It might be a hell if every bug report comes as the late ones, without specifying ROM type, saying weird names, no logs.... Looking forward to the first stable version, will try to pull some logs myself today if I get time to test!
[Galaxy S III Original Android Development] davtse:
I've tried it all, data wipes, clean, fresh installations of just rom + gapps, with nothing installed except for BBS to monitor the wakelocks. somehow something is causing the CPU to not go into deep sleep. The wakelock isnt reported on BBS either, which is really weird. When I go into the systemUI battery entry, it just says "Android OS" - 50%.

I'll switch around a few kernels and see if this is a Rom related issue or a kernel related issue and report back.

What ROM are you on btw? Could this be an AOSP related issue?
[Galaxy S III Original Android Development] MuertoKo:
Using stock ROM, so might be. For a proper use of BBS you should wipe and bla bla bla, ones you hit normal boot, install the app, open it, grant Root permisions and then fully charge and REBOOT your phone, ones you reboot open BBS ones more and then let your phone flat somewhere (perfect test is after full wipe on plane mode, to avoid issues with data or something that might nerf your battery.

After this, if you see anything unusual kernel related I guess you'll be more than welcome to post report in here, but usually deep sleep issues (at least this big issues) are never related to kernel stuff, unless you found a huge bug on AOSP!

Keep reporting and if you need any more tip on BBS please call me on PM, don't wanna flood this thread now that it's growing!
[Galaxy S III Original Android Development] DerTeufel1980:
Since I own this device, i was running samsung roms just for testing (maybe 2 days all together), and I didn't realize a battery drain related to aosp.

Please report back after you have done further testing

Btw: using touchwake with very high timeout of course also causes long wakelocks

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] davtse:
Roger on that. For now I'll do a benchmark with my usual kernels first +blank roms to extablish if it might be the rom that's causing the problem, not the kernel.
[Galaxy S III Original Android Development] nfsmw_gr:
Okay,here are the logs.

Please don't disable those features,or atleast zRam because it gives good multitasking potential(at least it made my phone multitask better).

If someone doesn't want it there's a switch in trickster mod. :)

Also i searched about zCache and cleancache on perseus thread and the only thing i found was this discussion:

http://xdaforums.com/showthread.php?t=1691401&highlight=cleancache&page=489

So i guess only zRam is enabled right now..?

EDIT:Guys my battery usage and deep sleep are fine too,maybe something loads your cpu?

Try this to see what's the cause...(play store link,free)

https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=el
[Galaxy S III Original Android Development] jeebspawnshop:
Bro, I've been using Devil kernel since you first started it back on the i9000. I think you're a great dev, that really cares for his code AND his users.

The only reason I've not yet installed this kernel is cuz the ABB on Perseus has really made a difference for my overclock and voltage settings.

I follow your thread like a hound, though, just in case you ever implement it ;) Cuz when you do, I'm switching over SO FAST.

But you should never stop developing your kernel just cuz there may be a few people that don't want to make a big leap and switch their recovery.

Keep up the amazing work, dude.
[Galaxy S III Original Android Development] danarama:
He never said anything about ceasing development of the kernel
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. Seems to be working fine besides the error messages :)

Which recovery are you using normally, and which options are you missing in mine?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
I use philz. For me there's loads of options I use, including theming.

I'd probably prefer to manage this using bash shell tbh.
[Galaxy S III Original Android Development] DerTeufel1980:
Can you tell me more about the fake flash and hijack options?

Fake flash is an option in stweaks? And hijack really flashes the recovery?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
Also http://xdaforums.com/showthread.php?t=2002953PhilZ Recovery here. Seems one of the most complete Recoveries out these days. DerTeufel1980, as already stated, please don't get me wrong. Many kudos for your hard work on this really cool kernel. It's just that i need my phone for everydays use and so I'm maybe a little too careful sometimes. I wasn't aware that gm left off without sharing the promised sources with you. Thats sad indeed. However, I hope you'll keep further development, m8.

Cheers, Olioaglio
[Galaxy S III Original Android Development] danarama:
Yeah in siyah you can hijack which replaces recovery. You can also boot into pro/sec roms from stweaks. You can also boot into the recovery without flashing.

If it helps, koush and Paul O'Brien a few years back invented fake flash. It was originally an update.zip you flashed by stock recovery. Perhaps the script within will help?

http://www.modaco.com/topic/310795-...unching-recovery-on-your-device-without-a-pc/
[Galaxy S III Original Android Development] Olioaglio:
I

Exactly. In Stweaks you can choose to reboot into dual recovery without having to physically flash it. It's just for the one next reboot (ramdisk?). If you (also in Stweaks) choose to "hijack" the recovery it's been flashed (out of Stweaks) to recovery partition and resides there as your main recovery which can be booted with known key combination even without any rom installed.

Edit: found this video on YouTube which demonstrates the fake flash (reboot into 2nd rom utils from siyah out of Stweaks)

https://www.youtube.com/watch?v=EdhshPTwzT0

Olioaglio

Sent from my SGS3
[Galaxy S III Original Android Development] danarama:
The download link on the page I posted has gone but luckily I never purge my drop box.

So from 2011, here you go ;)

http://db.tt/NM44iQyW
[Galaxy S III Original Android Development] DerTeufel1980:
Don't get this wrong. Gm already helped much with his hints. He asked once, if I wanted to have his source, but I guess he never was reading my answer.

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

The dual boot version I tested the other day, does that have all those changes too? Is it the same version I mean. You don't mention dual boot.
[Galaxy S III Original Android Development] DerTeufel1980:
It's similar, besides the wifi change.

I didn't mention dual-boot as it is not working without the recovery

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Gotcha. But it is working with the recovery. Its a great accomplishment. It definitely deservers to be in the change log. Sure, some may not want to change their recovery and that's something they / we / you can overcome later ;)
[Galaxy S III Original Android Development] MuertoKo:
New update working good so far :D

I just love the scheduler in this kernel that Fiops! Works way better than others, glad you did upstream and drop exFat to include this!

Will try dual boot some day but I'm not pretty interested in it although I may try it just for debug purpose!

Thanks once again!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
I am also going to add fuse exfat support, then no one has to reformat its sdcard

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
Great to hear ^^ Wish some ppl come to this kernel to this it out so you can get more testers for the dual-booting stuff!

Could you take a look in the random "bootloop at boot" issue? Wasn't able to pull any logs... It just... happens sometimes on the booting sequence, same in perseus and no idea why, just pretty annoying not a major issue after all :D Guess you couldn't as afaik you don't own the device and so it might be pretty hard to debuf something like this without logs U.U Guess this isn't happening on Note 2 community though?
[Galaxy S III Original Android Development] XGX5309:
Maybe just me, but my camera wasn't working with this kernel. I loved it though, otherwise. And I really like the config app.
[Galaxy S III Original Android Development] optmkleung:
AOKP M2, Same issue.
[Galaxy S III Original Android Development] MuertoKo:
Unless you are more specific like adding logs and explaining the issue Teufel will hardly be able to solve it
[Galaxy S III Original Android Development] DerTeufel1980:
Was it working previously? What's the error you get?

Just wondering cause I didn't change mali stuff between last two versions

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Ah man still no zzmoove update!
[Galaxy S III Original Android Development] Olioaglio:
FYI, Camera working fine here with 27.x version on Wanam 6.5 (sammy).

Olioaglio
[Galaxy S III Original Android Development] XGX5309:
Logcat of failure... (CM10.1 Nightly 7.20.13)

EDIT: It worked before, yes. It also works on other kernels.
[Galaxy S III Original Android Development] DerTeufel1980:
thanks.

can you please also try this kernel:

http://xdaforums.com/showpost.php?p=43440931&postcount=711

it's the last i have built before starting updating for the .27.x kernels
[Galaxy S III Original Android Development] XGX5309:
Sure can. I'll report back in a few minutes.

EDIT: Yes, the camera works in the .25.6 version.
[Galaxy S III Original Android Development] DerTeufel1980:
thanks. we'll find the issue :)

had forgotten this one. can you please also try. thx

http://xdaforums.com/attachment.php?attachmentid=2128781&d=1374269365
[Galaxy S III Original Android Development] XGX5309:
Yep. Works on .26.1 as well.
[Galaxy S III Original Android Development] DerTeufel1980:
try this one please
[Galaxy S III Original Android Development] XGX5309:
Nope. Same crash as the other .27.x kernel. I'll get you a logcat in a bit...

Basically, it's first exceptions are when it looks at the Mali libs. Then it can't acquire a live preview. Then it just kills the thread and releases the camera.
[Galaxy S III Original Android Development] DerTeufel1980:
No need for a logcat, there have not been many changes between the last working one, and the crashing one.

I'll just revert one after another till it works again.

It's just weird cause none of the changes seems to be causing it, although one has to be ;)

Gesendet von meinem SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
new try
[Galaxy S III Original Android Development] Olioaglio:
Erm, but why does the camera it's work perfectly on my device with 27.1 dual kernel? Just tried again with stock camera app, perfectly clear and paper cam. All are working well. Also video :confused: But confused now.

Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
Idk. It's also working fine for me, but for other users with note2 it is the same issue as described here.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
You are using Stock based ROMs, right? No issues on stock sammy roms afaik. It happens on AOSP isn't it? I have no issues as well and I'm running Samsung based.
[Galaxy S III Original Android Development] Olioaglio:
Ah ok, thanks. Thought so, but it wasn't mentioned anywhere, so i wanted to get sure, that only AOSP roms are affected.

Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
Anyone on aosp tried last one?

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

Camera works. Anything else that has to be tested? I don't use my device that much these days...
[Galaxy S III Original Android Development] DerTeufel1980:
Nice to see you :) how are you?

Thanks for testing

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] scheichuwe:
I'm fine thanks :)

Still missing a good app to configure your kernels settings though :p
[Galaxy S III Original Android Development] tolis626:
Yeah...Regarding that,why not STweaks?Yeah,it's slow and stuff,but it gets the job done every time as far as I'm concerned.TricksterMod is too restricted at times and DevilTools is as WIP as it goes.I'd suggest something like using STweaks until DevilTools is completely ready.That's just me though...
[Galaxy S III Original Android Development] XGX5309:
Yep. That last one works nicely. Thank you!
[Galaxy S III Original Android Development] arbi97:
Try on CM 10.1. Works great, but in settings, the Kernel Name is Unavaiable. Why? In Quadrant, whe i want to see my settings phone, he get your name kernel, but in settings is not.
[Galaxy S III Original Android Development] DerTeufel1980:
Because aosp decided to mess up the kernel version. Don't ask me why...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Again, latest confirmed with Camera on AOSP. I didn't test camera before so didn't realise was an issue but tyested before update just to be sure. All good, thank you.
[Galaxy S III Original Android Development] Yank555:
You don't happen to have a space in the kernel name somewhere, happened to me once by mistake, gave that exact symptom...

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta3 (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] DerTeufel1980:
There is no space... I really don't know what the commit was good for. CM committed it as: fix display kernel version or similar, but actually it did the opposite...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Strange, didn't see that commit ... is it old ?

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta3 (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, I guess it's half a year. I can search it for you.

https://github.com/CyanogenMod/andr...mmit/8ff810faaa7bca5b8401baca42f74b3166ce6010

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] trein91:
Anyone else getting lags on zzmoove governor? Using any other ones like pegasusq or devilq works fine though. zzmoove one stutters sometimes.
[Galaxy S III Original Android Development] Yank555:
Oh, it's a ROM side commit :D Ok, I thought a kernel side one... This one will be impossible to fight off, since it will be in every ROM out there :(

Strange, it's showing up just fine for my kernel. What is the exact string it should be displaying for your's ?

JP.
[Galaxy S III Original Android Development] DerTeufel1980:
It's a very long string:

Devil-DEVICE-Dual-VERSIONNR_DATE

Too bad I am not good at regular expressions and I don't understand what the commit actually changes. Otherwise I could make my kernel fit these criteria

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
OK, this time I actually looked closer at that commit code, but ... :cyclops:

Looks like some random characters to me :D

I guess I'm just too much into C and not into Java at all, even though I promised myself to go have a look at Java sometime...

I'm now actually rather thankful that my kernel name seems to meet those criteria, as I wouldn't indeed know what to change to make it fit either :silly:

JP.
[Galaxy S III Original Android Development] DerTeufel1980:
Update :)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Don't mind if I do....

;)

Waits for haby's post!
[Galaxy S III Original Android Development] brujo55:
awesome,thx.:good:
[Galaxy S III Original Android Development] MuertoKo:
Working great so far on Sammy ROM ^^
[Galaxy S III Original Android Development] habylab:
The update is nothing special...... ;)

Oi!
[Galaxy S III Original Android Development] danarama:
He he :)
[Galaxy S III Original Android Development] DerTeufel1980:
:p

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] habylab:
:D the master has delivered as per usual!

:) Happy Hab.
[Galaxy S III Original Android Development] Olioaglio:
Absolutely awesome update. I'm very impressed, indeed. I hope, also p33t-r and colleagues will realize, that this kernel ABSOLUTELY ROCKS. IMO the only real competitor to Boeffla. Great work again, DerTeufel1980. The last bastion to take is the Devil Config app to ged it rid of Trickster and built in fake flash option to soft boot the dual recovery. Some time ago Phil stated that he will implement Dualboot feature into the great PhilZ Recovery some day, but unfortunately it seems to have very low priority for him.

Cheers, Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
I wanted to submit my dualboot changes to philz. I guess he was talking about this.

For now it's not ready to be added to his recovery, because it is very hacky

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Exciting stuff though. He was looking at dual boot support a while ago but not sure what happened.
[Galaxy S III Original Android Development] Olioaglio:
After using the Devil 28.0 kernel for a full day now with trickster tweaked opt. zzmoove 0.6 governor (tweaking values from Boeffla thread), i have to state that this is by far the best kernel i have ever used. Blazing snappy, full featured, superior battery life, master sequence, dual boot capabilities, no freezes, glitches, reboots, lags. Let me say, that kernel is a master piece in S3 kernel development and definitely a daily driver.

Cheers, Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. I'll try to add some bugs next time :D

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Oh, oh, if you're taking requests, please could you add the bug where the screen doesnt come back on when waking from deep sleep? I love that bug ;)
[Galaxy S III Original Android Development] trein91:
What settings are you using for zzmoove? I use the default but it's giving me lags from time to time (delayed touch responses).
[Galaxy S III Original Android Development] dmourao:
That one is great and really underrated. :thumbup:
[Galaxy S III Original Android Development] Melhisedek:
I double this :) What settings do you use mate?
[Galaxy S III Original Android Development] tolis626:
Since we're throwing bug requests around,I would humbly ask for the return of the good old Windows blue screen of death.When the phone crashes (Due to e.g. overclocking),the usual black screen has become boring,and it needs more brain activity to realize what's wrong.A blue one will be easier to comprehend and will have more style.Couple it with a "What are you doing to me you idiot?" on-screen message,and you have a killer bug/feature. :D
[Galaxy S III Original Android Development] Olioaglio:
Here you go m8s...

Used the following values in Trickster governor settings. For perfect touch response i set the touchscreen touch frequency to 1000 mhz (so if screen is touched it jumps up to at least 1000 mhz) this may lower battery life time though. But it's a perfectly fast beast :D

Btw., there are also settings for performance and battery optimized.

Cheers, Olioaglio

Spoiler content hidden.
[Galaxy S III Original Android Development] trein91:
800000 or 8 for freq_limit_sleep?

Also where do I edit LCDFreq scaling?
[Galaxy S III Original Android Development] danarama:
In a script like you quoted!
[Galaxy S III Original Android Development] spoonymoon:
So fast and great new update woow its fast never seen anything like this.. It simply flyes, no matter what you do..:victory:

Cant wait for a update that makes devil config working, really looking forward to try

And dunno about touchwake, it works perfect, also never seen here before - but it makes a serious wakelock that stops device from entering deep sleep.

Maybe rhis is just a temporary bug or?

Wonderfull work as akways Devil thx:D
[Galaxy S III Original Android Development] danarama:
Hi [MENTION=4196889]DerTeufel1980[/MENTION]

Would you consider tweaking zzmove a little please? If possible, I'd like to be able to set higher down thresholds / sleeps
[Galaxy S III Original Android Development] DerTeufel1980:
For now i don't know a way to remove the wakelock. It's needed to keep the touchscreen powered.

I need to take a look at the source more deeply. Also, me was reading about a newer version already.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] habylab:
I see in Googy Max that dynfsync has been updated to 1.2, is this required or not? Running great so far. Cannot set lcdfreq with Trickster, however.
[Galaxy S III Original Android Development] DerTeufel1980:
I have added this over a month ago ;)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] dmourao:
Ninja'd!
[Galaxy S III Original Android Development] habylab:
Haha, I expected no less!
[Galaxy S III Original Android Development] FPSKunal:
Guys any idea why android os is taking up so much juice?

"Sent from Westeros using a Raven"
[Galaxy S III Original Android Development] habylab:
I have much less, try a wipe if not too much hassle.
[Galaxy S III Original Android Development] XGX5309:
Disable Google Talkback. It seems to cause CPU wakelocks in some cases.