yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] GGL-Daz:
Been using it for a day now, really good man keep it up. But why does my screen look grainy?
[Galaxy S III Android Development] tokariew:
Wifi direct don't work for me on Archikernel on aosp. Guys on cm forum say it kernel thing
[Galaxy S III Android Development] EP21:
Since when is cm responsible for aosp project? Or maybe i don't know something?
[Galaxy S III Android Development] _master_:
Hi! I`m using Archidroid 1.7.18 on my S3, which kernel should I use? Aosp or Samsung?
[Galaxy S III Android Development] konohanz:
Because of AD 1.x base on stock so you should choose A.K for Samsung :o
[Galaxy S III Android Development] Tyrigi:
Possible to add this feature to the kernel? http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344
[Galaxy S III Android Development] Moster2:
Useless for us. It would only drain battery. And having a timeout on it like touch2wake would make the function itself useless.
[Galaxy S III Android Development] cradonale:
how to enable 'tap to wake' even while locking with power button ??
[Galaxy S III Android Development] Tyrigi:
mmmh ok :good:

This feature isn't included in this kernel, if you need it try arter97 kernel
[Galaxy S III Android Development] mendozaram:
Hello, which version must be used with Slimkat?

AOSP or AOSP_R4P0 ?

Thx
[Galaxy S III Android Development] marenp:
AOSP version :)
[Galaxy S III Android Development] Erazerr:
Hi everybody. I'm kinda new to this all flashing kernels stuff, been flashing roms for couple years now, but never kernels. So I wanted to ask. I've installed CM12 Alpha 4 on my GS3, but previously I tried installing Nameless rom, but after finging out that wifi doesn't work there, I found this one. The problem is, Nameless uses custom kernel and after reflashing cm12 it didn't go away. So I was wandering if I should reflash to cm11, then back to cm12 and only then flashing kernel? From what I've read, flashing custom kernel over custom kernel is a big risk of bricking device.

Thanks and take care :)
[Galaxy S III Android Development] TrashSlash:
Awesome kernel i am using it with qs 4.4.2 NI3 and runs perfect i have a great performance and great battery life. Thanks a lot for youre work
[Galaxy S III Android Development] Moster2:
Nameless does not use a custom kernel and flashing a rom will overwrite your current kernel. So, I dont see why you would want to go such a strange way to flash cm12.
[Galaxy S III Android Development] Erazerr:
*Sheesh* I can't link you to the screenshot I've made, but basically what it says is:

Kernel Version:

3.0.64-Nameless-g71c893e

bob@bob-System-product-name#1

Mon Dec 1 15:28:58 CET 2014

So this is wrong info I've got going on? I assume from what you've said, I can flash the kernel without worrying about it.

Thanks.

P.S. If I remember correct, you're one of the developers for i9300, I wanted to thank you for not giving up on this device :)
[Galaxy S III Android Development] Jsouza11:
Working in the 5.0.1?
[Galaxy S III Android Development] Moster2:
Its simple. On cm12 we are currently using nameless kernel. Obviously you will see nameless in the kernel name, although I changed that specific line already. So newer builds of cm12 will show cm there ;)
[Galaxy S III Android Development] laura almeida:
How do i enable touch-to-wake feature ?
[Galaxy S III Android Development] Targaeryan:
Is this what you're looking for?

Sttweaks-screen tab [emoji14]
[Galaxy S III Android Development] laura almeida:
I have enabled both touch-to-wake and knock-code.

But no change !

Where is the pattern for knock-code is saved ?
[Galaxy S III Android Development] RoelD92:
s3 doesn't support true knock-on. It would require keeping the phone always awake, draining the battery. That knock-on entry in sTweaks only works for the period for which you specified toch to wake (in this case 5 seconds if touch 2 wake is enabled).

This has been explained over and over again in this thread. Would have been easy to find
[Galaxy S III Android Development] you_man:
Hi [MENTION=5161352]JustArchi[/MENTION].

It has long been asked to add profile PegasusQPlus-balanced.

You can do this in the near upgrading the kernel?
[Galaxy S III Android Development] Metaldroidiano:
Hi guys!

i really love this kernel, but i have a simple question:

in the first tab, i choose the governor. For example i choose zzmoove-yank-battery. OK.

So i decided to go to the settings tab "zzmoove". OK. Now, if i change something here, and i apply the changes, what stweaks does?

- Are this settings separated from zzmoove-yank-battery settings or they are complementary?

- when i change something in the specific governor tab, this modification overwrite the settings of the governor in the first tab or not?

i don't understand if I choose a governor, means that it automatically changes setting in the specific tab, and if i not put the default governor like zzmoove in the first page, making some modification in the specific tab of zzmoove it's a big mistake!

help me, sorry but i'm little bit confuse because i don't know any section where i can find actually applied settings.:confused:
[Galaxy S III Android Development] Veyrontarga:
I have a weird problem with archikernel, it seems to break headphone and earpiece audio, and also make it very laggy! If I go back to stock CM12 it works fine. Anyone else experience this?
[Galaxy S III Android Development] zapty:
Clock speed !!

JustArchi This kernel clocks the CPU to 1.6 GHz , will that be a problem as S3 has the clock speed of 1.4GHz
[Galaxy S III Android Development] ste22032:
Nope, a 1.6 GHz overclock is completely safe for our device, even for a long period.
[Galaxy S III Android Development] zapty:
Won't this clock speed affect the battery life ?
[Galaxy S III Android Development] Hawaiihemd:
With respect, that is the same as asking if an engine with 50HP more than another will use more gas. Depending on the engine, yes it will, but how much gas you actually need not only depends on how powerfull the engine is. It depends mainly on your way of driving, road conditions, etc.

Same goes for cellphone batteries. Almost EVERYTHING affects battery life. Highest clock speed is IMHO not the main factor.
[Galaxy S III Android Development] zapty:
Oh yeah I got that !!

but having we overclocked this chip , Would that affect the life span of the chip , or harm the phone in any way ? .
[Galaxy S III Android Development] EP21:
If done correctly it will produce more heat, but will use more or less the same amount of power as stock 1,4ghz, Also your comparison is next to false as well, since if the mods are put correctly then those 50hp will be just released ponies from a crappy build with next to no extra fuel usage.
[Galaxy S III Android Development] Hawaiihemd:
Exactly my point... that was why I compared 1,4 to 1,6 and normal to +50HP. Almost no impact... But let's not argue on semantics.
[Galaxy S III Android Development] Metaldroidiano:
anyone?:crying::crying::crying:
[Galaxy S III Android Development] JustArchi:
You should ask [MENTION=4604352]Moster2[/MENTION] about that. It's STweaks-related, which I don't like that much myself. I prefer standard oldschool way, or third-party apps like trickster mod.

That is not kernel-related, also AK doesn't support F2FS regardless.

OC of SGS3 chip to 1.6 GHz is completely safe and standard value for our chip. That is the maximum possible value that is proven to work stable, and is used by default e.g. in Note 2.

Higher battery usage is negligible. In fact, 1600 MHz step uses 1400 mV voltage, as opposed to 1300 mV on 1400 MHz step. However, just "increasing" maximum frequency doesn't change anything, it's the governor which chooses which frequency is good for you at the moment. Good governor, e.g. ZZmoove on Battery Plus preset saves battery much more than just being on 1400 MHz.

Setting maximum frequency doesn't mean that your device will use it whole the time. Governor makes decision when it should be used, and when not. If you want to monitor that, CoolTool is just one sample app. And I'd strongly suggest to learn & experiment with governors before disabling OC. It is enabled by default in AK because it's the governor who should balance batery & performance, and not the chip which specifies maximum "safe" value, because the safe value for us is 1600, hence, it's available by default.
[Galaxy S III Android Development] ubikt:
stiil have problems with bluetooth playing music, a lot of breaks!
[Galaxy S III Android Development] prabhjots:
I can't seem to download. Getting blank page at the redirect.viglink page. Any help?

Edit: never mind, Tapatalk issue.
[Galaxy S III Android Development] JustArchi:
It doesn't happen on other kernels? Especially Boeffla NG?
[Galaxy S III Android Development] eatsleep:
Great stuff going on!

I wanted to ask that can you make the lmk values tweakable?

Cm 12 kills apps like crazy... Is that a bug or something?
[Galaxy S III Android Development] MD500:
Will AK work in sammy korean ports? (4.4.4)?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] ste22032:
Yes, if you flash the correct version, that is Samsung_R3P2 :).

Sent from my GT-I9300 powered by ArchiDroid V3.0.0
[Galaxy S III Android Development] JustArchi:
LMK is android stuff, not the kernel.

You can tweak them already with various third-party apps, and adding such addition to STweaks is not being considered at the moment.
[Galaxy S III Android Development] megen:
I have tested AK on QS 4.4.2 rom but there were some stability problems. Performance was good but there were some connection issues with data.
[Galaxy S III Android Development] ara1370:
+1
[Galaxy S III Android Development] JustArchi:
Kernel can't be a reason of broken data, especially if it works properly on KK, and now also on LP.

It's more likely that ROM is the problem.
[Galaxy S III Android Development] MD500:
Archi. Im trying to flash the kernel (r3p2 samsumg ) in sammy korean rom 4.4.4 but it says error:

Mon Dec 22 15:57:32 GMT 2014
INFO: ArchiKernel flasher ready!
INFO: Safety check: ON, flasher will immediately terminate in case of ANY error
INFO: Pulling boot.img from /dev/block/mmcblk0p5
INFO: Unpacking pulled boot.img
BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE 10000000
BOARD_NAME smdk4x12
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 01000000
BOARD_TAGS_OFFSET 00000100
INFO: Ramdisk found!
INFO: Detecting ramdisk format...
INFO: GZIP format detected
INFO: Extracting ramdisk...
16260 blocks
INFO: Detected Samsung variant
INFO: Overwriting ramdisk with custom content
INFO: User is flashing the kernel for the first time!
INFO: Combining ArchiKernel zImage and current kernel ramdisk
INFO: newboot.img ready!
INFO: Flashing newboot.img on /dev/block/mmcblk0p5
failed with error: -1

i put the kernel in /data/media/0 using philz touch recovery and this rom comes with enki kernel(espdesarrolladores). Is the custom kernel causing the issue?

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] cba1986:
@JustArchi i can't wait to try this in the latest nameless's alpha....
[Galaxy S III Android Development] RoelD92:
DON'T. It won't boot. The latest nameless alpha is based on r3p2 again with a lot of modifocations. Wait for a new version.
[Galaxy S III Android Development] Moster2:
So, he can just use the normal aosp version...
[Galaxy S III Android Development] megen:
I don't mean the problem is kernel. Maybe rom is incompatible with AK. Currently I am using another custom kernel and there is no data disconnection after a phone call. I just shared my experience.
[Galaxy S III Android Development] cba1986:
i know. [MENTION=5161352]JustArchi[/MENTION] said that support for nameless rom will be very soon.....

i don't if it will work. Because [MENTION=2875964]dhiru1602[/MENTION] used sources from N7100 and [MENTION=5161352]JustArchi[/MENTION] is based on I9300 source if i recall correctly.
[Galaxy S III Android Development] RoelD92:
Ah. Didn't know that. I thought it would require a new version of the kernel
[Galaxy S III Android Development] JustArchi:
Sounds like kernel is too big to fit on the partition.

And yes, custom kernel may be the issue as well, hence it's required to flash AK on top of stock kernel.
[Galaxy S III Android Development] cba1986:
[MENTION=5161352]JustArchi[/MENTION] can the AOSP version of your kernel be used in nameless?
[Galaxy S III Android Development] JustArchi:
AFAIK [MENTION=4604352]Moster2[/MENTION] already added PegasusQ-Plus governor, and profile is just a set of values.

I'm not touching STweaks stuff at the moment.

You can try, in worst scenario kernel won't boot. Personally I think that kernel should work properly, but it has SELinux enabled and may not boot with the alpha ROM, as it may have missing SELinux context, at least this is what we have.

I'll prepare working kernel for lollipop soon.
[Galaxy S III Android Development] cba1986:
Thanks for the answer. :good:

i will better wait, i am at work now and i need my phone.

Sorry to bring this up but that ROM is the point of breaking beta status. A lot of features missing and the 2g<->3g is a little funky but besides that it works fine.
[Galaxy S III Android Development] MD500:
Latest boeffla kernel have LPM fixed. Is possible to implement this fix?

Enviado desde mi GT-I9300 mediante Tapatalk

---------- Post added at 04:27 PM ---------- Previous post was at 03:43 PM ----------

Ahh. Anyone know why /data/media/legacy is empty? I have /sdcard symlinked to /storage/emulated/legacy (with all data),same data and link in /storage/sdcard0,But all my data is in /data/media/0 , /storage/emulated/0 or /storage/legacy?(which are not symlink with all data) could anyone explain this and the correct permissions including extsdcard? And the only symlink in my external sd is in /mnt/extSdCard symlinked to /storage/extSdCard

Im very confused how android handle the data.

Sorry for OT.

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] JustArchi:
https://github.com/ArchiDroid/ArchiKernel/commits/m0

Already on our roadmap, I just need to check if it doesn't break sammy.

Somebody please check LPM on Sammy. LPM is about charging the phone from "cold", from turned off device. It should work properly in current release, this one has some fixes for AOSP bundled in, and I'm wondering if they should be in all trees or only in AOSP variants, thanks.
[Galaxy S III Android Development] Jsouza11:
This is for beta 1
[Galaxy S III Android Development] cangcan:
dhiru is using github. omg. BTW is there any guide on how to download zip file based on AOSP or Sammy archi kernel? i mean like AD2x experimental/ AD3x experimental on github where we can click the 'Download Zip' button on it.. Sorry if it sounds nooby, i really dont understand on how to look and use github, tried to learn but it just so complicated to understand the github language such as repo fork commit pull push etc...
[Galaxy S III Android Development] cangcan:
and one more thing..sorry for another noob question..i've been using archikernel and other kernel and i found an issue..when i tweak charge rate to 1300ma, in the apps of galaxy charging rate it only show 1000ma for max and average charging current..but in arter and agni kernel..it shows both 1300ma in max and average charge current..so my question is the charge current is limited to 1000ma only in archikernel?
[Galaxy S III Android Development] Hydrony:
I have a strange Problem. Im using latest archikernel in combination with slimkat and everytime i reboot it loses my wifi information. So i am not able To Connect to my wifi network without reentering my wifi password. Any solution to this?
[Galaxy S III Android Development] JustArchi:
This is not connected with the kernel at all.
[Galaxy S III Android Development] Hydrony:
Hmmm quite interesting. I used boeffla kernel before and everything worked fine. Thanks for your reply.
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
Can I use this on liquid smooth 5.0.2 rom?
[Galaxy S III Android Development] Oiram_37:
I flashed this Kernel build by [MENTION=4604352]Moster2[/MENTION] with disabled SELinux posted in this thread ----> Moster2 build

Is there a big difference to this one build by [MENTION=5161352]JustArchi[/MENTION] ----> JustArchi-Kernel

Greetz

Oiram_37
[Galaxy S III Android Development] Moster2:
Ye, one is for samsung, the other one for lollipop cm12.
[Galaxy S III Android Development] Oiram_37:
Ah, ok. Don´t noticed that :o

Thank you. Your quick build is running fantastic under CM12 :good:
[Galaxy S III Android Development] Mostafa Wael:
can i use the AOSP version for latest nameless ROM ?

i mean the ArchiKernel_AOSP "not the AOSP_R4P0 one "
[Galaxy S III Android Development] JustArchi:
ArchiKernel V1.7

Download, changelog, and cookies

Merry christmas :cool:.
[Galaxy S III Android Development] vwong:
Great Job as usual.

Merry christmas to you as well :cool:.
[Galaxy S III Android Development] Arifcatalyst:
Black screen in latest nameless. 23/12/2014. Doesn't go past S3 logo.

Logs attatched.
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
Is this work for liquid smooth ROM.
[Galaxy S III Android Development] JustArchi:
This log doesn't help.

Have you flashed LP variant?

It works fine on CM12.
[Galaxy S III Android Development] Arifcatalyst:
yes for sure.

I can reproduce it to provide you with a log, but when it's in black screen "log> dmesg" and "last>kmsg" is empty.

So I gave you last>kmsg after completely booting up with nameless kernel.
[Galaxy S III Android Development] JustArchi:
It doesn't make any sense to me. Sounds like HWC conflict, but the same kernel works for my CM11 powered AD with HWC as well. [MENTION=4604352]Moster2[/MENTION]
[Galaxy S III Android Development] Arifcatalyst:
Then how to provide a reasonable log when it's black screen ?
[Galaxy S III Android Development] Moster2:
Im unsure, but I guess that surface flinger crash fix shouldnt be in the new lollipop version.
[Galaxy S III Android Development] JustArchi:
You can't.

Test the attached kernel please.
[Galaxy S III Android Development] habylab:
Backlight is rather annoying, will have to swap for now. Any method to change charging settings? I thought I saw Boeffla charging engine in this? That includes safe margin etc., non?

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] JustArchi:
Yes it includes Boeffla charging interface and if you know what you're doing you can echo sysfs values to achieve what you want. But there's no app which will provide you with an easy way.

Pro tip:

/sys/kernel/charge_levels/ignore_unstable_power

/sys/kernel/charge_levels/ignore_safety_margin
[Galaxy S III Android Development] habylab:
Thank you, I am not sure on that so will leave it. Kernel is very good though.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] solar666:
And what about arter97 Kernel?
[Galaxy S III Android Development] JustArchi:
Did you look inside source code? Because I did.
[Galaxy S III Android Development] habylab:
It shows. This kernel seems much smoother. The only lags I get now are either because of the ROM or the 1.4ghz clock speed.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] JustArchi:
smdk4x12 sources upstreamed to Update13 are NOT the same as basing purely on Update13 sources. This rom is for AOSP while based on Sammy sources.
[Galaxy S III Android Development] habylab:
Gonna guess you have the first item, but the second one sounds interesting. This is from Boeffla changelog!:-

- Updated mali drivers from r3p2 rel3 to r3p2 rel4 (credits to JustArchi)

- Speedup late resume for faster wakeup of the device (credits to Yank555)

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] cassote:
since omni's been having some issues.....would you advise changing into other rom?
[Galaxy S III Android Development] dyval:
You should ask that question to the OmniRom thread. This is a kernel thread for AOSP made by OP.
[Galaxy S III Android Development] habylab:
Wrong thread, but give SlimRom weeklies or CM M7 a try.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] cassote:
well i kinda posted this in a hurry and ended not beeing clear...... i mentioned omni having some troubles with ARCHI's kernel.....what i wanted was the most compatible rom with his kernel :D ( appologise if i just posted looking like a purelly rom question....)

and i was kinda divided between slim and CM's..... so, once again,.....any suggestion more apropriated for this kernel ?
[Galaxy S III Android Development] solar666:
No, I did not. It was just a question and no offense.

Anyhow, thanks for the answer.
[Galaxy S III Android Development] JustArchi:
Currently, noone. This kernel is in alpha and is not suitable for daily driver yet.

When it will be suitable, it will be V2.0.
[Galaxy S III Android Development] szotaa:
I've been using ArchiKernel 1.0 since its release so I can report now my toughts about this brilliant piece of work. (im using it with official cm nightly, clean flash)

Pros:

-very stable (no random reboots, never noticed any soft or hard reboot, device never hanged)

-battery life (can easily compete with stock touchwiz rom)

-UI is very smooth

-Camera focus is finally acting like it should :>

-Screen colors are so nice idk why

Cons:

-Video recording is not working properly (horizontal lines and low framerate of recorded videos)

-Video playback is buggy (I often need to reboot my device to even start a movie, tried with stock cm galerry app and with mx player with HW/HW+/SW decoders)

-"cant connect to the camera" error is present

-Screen is sometimes "oversharp", edges look pixelated

However I think that in the future this is going to be a good competitior to the boeffla-kernel-masterpiece
[Galaxy S III Android Development] supreethms:
Hey, [MENTION=5161352]JustArchi[/MENTION] , Yesterday i wanted to try out your kernel so badly and i did.

And i found some plus points and i wanted to report some bugs.

Plus Points -

1. Really smooth. (It lagged a little as soon as the phone was started)

2. I loved the display sharpness. I like it that way actually.

Bugs -

1. Just like everybody is reporting - Video recording and playback.

2. The Capacitive buttons light stays continuously on. It is a little irritative and it also drains battery. On PA RC2 Freshly installed.

It is a very nice kernel for being in the alpha stages. Maybe if these are done, it can be made fully customizable like you mentioned about the kernel control app of your own.

Thanks for your works dude! Respects.
[Galaxy S III Android Development] JustArchi:
Video recording, I mean interlacing icons (because framerate is Omni bug) probably won't be fixed in near future simply because I have no idea where the problem may exist. This may be connected with the ROM, relying on exact specification of the kernel sources (some very dirty and nasty workarounds/hacks, I hate these). Don't expect this to be fixed in very near future, especially because I have no idea even where to start.
[Galaxy S III Android Development] d1rekt0r:
There is no Video Recording or playback bug in CM . Not related to kernel at all.
[Galaxy S III Android Development] habylab:
What ROMs are you guys on? Had the stock kernel before flashing this?

The lost above mine indicates CM does not have this issue.

Edit: noticed Supre is on PA Rc2, could be a bug in that maybe.
[Galaxy S III Android Development] szotaa:
I was on official cm11 nightly (clean flash) ans had the video rec issue. Now im on cm linaro build and issue is still present.

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] Arifcatalyst:
Nope! It won't go past S3 logo.
[Galaxy S III Android Development] JustArchi:
I'm out of ideas then. Deal with it, or ask Dhiru. Or wait until we find out.
[Galaxy S III Android Development] Arifcatalyst:
[MENTION=2875964]dhiru1602[/MENTION]

Btw , he has reverted back to old style zip flashing, I am able to increase my data partition.( Thanks to him)

Only drawback is a bit slow flashing.