yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] nikolas1274:
For su permissions yes it is normal because you have to give su permissions from magisk now

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] lyolic:
No, I'm talking about such permissions as Storage, Contacts etc
[Galaxy S III Android Development] acroreiser:
No. But it is not kernel-side problem. Kernel not affect app permissions.
[Galaxy S III Android Development] Ashraf Iraqian:
Hi

thanks for trying to give us more stable kernel but since i installed this kernel on my LOS ROM i have issue on call

when i receive calls my screen stay sleeping for 5 - 7 seconds.

i am sure it is related to this kernel.

can you fix it please
[Galaxy S III Android Development] acroreiser:
My dear friend. This issue related to all 7.x ROMs and not a kernel. Anyway you can revert to stock, or install another kernel to check it.
[Galaxy S III Android Development] acroreiser:
Waiting for updates? :)
[Galaxy S III Android Development] Pasindu88:
Is this kernel support to mokee rom?. It has fixed hwc
[Galaxy S III Android Development] Ashraf Iraqian:
Hi

is Mokee Rom fixed hwc issue?

what about rom thread? it is closed https://xdaforums.com/galaxy-s3/development/mokee-rom-t3563827/post73014919

Strange! even i found the download zip file from mokee open source site and it is today nightly update 20180212,

can you pm me the threat link please.

Regards
[Galaxy S III Android Development] acroreiser:
Mokee has NOT fixed HWC. So, Koffee is compatible with this ROM.
[Galaxy S III Android Development] Pasindu88:
Ty for the info. I installed koffee kernel and it's working fine in mokee rom
[Galaxy S III Android Development] kosmasgr:
Did you try last mokee ?
[Galaxy S III Android Development] acroreiser:
Is Mokee relate to Koffee?
[Galaxy S III Android Development] Ashraf Iraqian:
no i didn't , i am just asked him if he is tested the ROM but he is also was asking for the fix.

sorry
[Galaxy S III Android Development] kosmasgr:
LMAO :) maybe .

Latest mokee works great with latest Koffee :p
[Galaxy S III Android Development] ar_156:
does it fix battery drain on S3 with RR?
[Galaxy S III Android Development] acroreiser:
Announce (build 4?)

Current changelog:

1. Added MSM Hotplug driver (screenshot 1)

2. Applied some patches

3. Disabled l2_hsic wakelock

4. Readded conservative and bfq

5. Kernel version gets +1
[Galaxy S III Android Development] ar_156:
OK, that's a no.
[Galaxy S III Android Development] acroreiser:
Just for you - NO. I'm not a telepat to detect reason of your battery drain. You're not provide me any additional info (installed apps, BetterBatteryStats log or dump).

Аnd reason can be not kernel-side. It can be ROM, installed apps, wrong settings or even just you.

Why you write about this here?
[Galaxy S III Android Development] Gu6tera:
Boeffla Config V2 can't apply profile

Hello, I'am currently useing the kernel on dnd rom, I also applied the low ram zip, as stated in the title, I'am experiencing problems with the configurator, if we can't reslove the problem, can you suggest other options to config the kernel.
[Galaxy S III Android Development] kosmasgr:
Awesome :) can we enable hotplug on boeffla app or need kernel adiutor ?
[Galaxy S III Android Development] acroreiser:
>> "I'am experiencing problems with the configurator"

What issues?

I must autodetect your problems?

Okay, but please make me a telepath first!
[Galaxy S III Android Development] acroreiser:
On latest builds Intelli-plug active by default.

From 44 you can switch between hotplug drivers via Kernel Adiutor.
[Galaxy S III Android Development] kosmasgr:
Thanks :) Touch key led controlled by kernel support by kernel Adiutor ? :) because I see this setting only on boeffla app
[Galaxy S III Android Development] Gu6tera:
As I stated in the title of my previous post ''Boeffla Config V2 can't apply profile'', this is what happens (I think the XDA app doesn't display titles), I'm trying those system tweaks in the configurator could it be the problem ? The koffee build is 41.

PS

Now I tried without those system tweaks, it loaded the profile, but why wouldn't load with them ? A$teroid I was at school, so i haven't time to test without the tweaks, sorry for the limited inf I gave earlier.
[Galaxy S III Android Development] DarkPulsar:
I can't find the latest build (44) in your google drive (i have b41 ). Thanks for the amazing kernel !
[Galaxy S III Android Development] kosmasgr:
It was announced not released yet ;)
[Galaxy S III Android Development] DarkPulsar:
Thank you! I didn't notice!
[Galaxy S III Android Development] lyolic:
How many RAM does it(build44) has in Settings-Memory-Total memory?
[Galaxy S III Android Development] ArdaCsknn:
Should I switch from Experimental to Official build for better battery?Because battery drains while phone idling.
[Galaxy S III Android Development] acroreiser:
No. But I planning to drop BCv2 in future
[Galaxy S III Android Development] acroreiser:
Reread the OP:

>> Please, do not use tweakers!
[Galaxy S III Android Development] acroreiser:
You can try after next Koffee build, I'll disable some wakelocks
[Galaxy S III Android Development] acroreiser:
Memtotal = 832MB
[Galaxy S III Android Development] ArdaCsknn:
OK.I will try because it's a huge problem for me.Can't stop drain.Mobile data destroys my battery.It is worse than Wi-Fi.I will provide a screenshot later.
[Galaxy S III Android Development] rocciacoraggiosa45:
my phone is crazy , i have try everything downclock , change hotplug , undervolt ecc but i do every times 4 1/2 hours of SoT XD
[Galaxy S III Android Development] Ashraf Iraqian:
wow , That is Cool :) because Mr. Andy said he will not giving any support for i9300 if we got Android O in future. Maybe you will stay giving support to our phones.

Big thanks for his kernel and God bless You :good:
[Galaxy S III Android Development] Samofr:
What can be affected after this ?
[Galaxy S III Android Development] acroreiser:
Nothing. As result we have slightly better sleep.

----

Also who wants to test 44, can write me PM.
[Galaxy S III Android Development] kosmasgr:
Awesome work :)

Combination with crdroid ;)
[Galaxy S III Android Development] Nightraven13:
Hah, I only get 3 hours and 30 mins with Atila 4.4.4 ROM and Boeffla 7.9. Lucky man.
[Galaxy S III Android Development] froycard:
Removed
[Galaxy S III Android Development] acroreiser:
What you forgot in Koffee kernel thread?
[Galaxy S III Android Development] rocciacoraggiosa45:
can you set pegasusq default governor for battery profile work? ty
[Galaxy S III Android Development] acroreiser:
No.
[Galaxy S III Android Development] kosmasgr:
Hello again :) build 44 seems awesome. Deep sleep and battery drain on standby is excellent also ;)

So release the craken ???
[Galaxy S III Android Development] rocciacoraggiosa45:
sorry why no?
[Galaxy S III Android Development] froycard:
oops sorry... my bad... I was reading two thread at the same times... I will remove my post from this thread.
[Galaxy S III Android Development] ArdaCsknn:
Do you know the differences between Experimental builds kernel and official builds kernel?

We can't flash kernels because it's incompatible.If I am not wrong Simon said it is based on Note 2.But is it effecting the phone any battery drain wise?I want to use LOS because it is really smooth and fast.4.3 feels so laggy and slow while using.In any Los rom battery drain makes me crazy just because this device my daily device.Phone services was keeping device awake.Installed some 3rd party app-ops(can't disable through privacy guard) and disabled it.Any idea how to stop drain?
[Galaxy S III Android Development] acroreiser:
This is not thread of experimental lineage.

This an the Koffee's thread. Koffee is not an experimental lineage.
[Galaxy S III Android Development] fonfox:
V4.4 is smooth and stable. Better than V4.1

good battery life, awesome deep sleep.

Screen shot is with 1h40m SOT
[Galaxy S III Android Development] ArdaCsknn:
I know I am asking because isn't HWC about Kernel.I thought you are knowing differences with experimental and official.I will flash official LOS for your kernel right now.I hope I can live with crashing HWC.
[Galaxy S III Android Development] acroreiser:
HWC, HWC.

H. W. C.

Nope.

How Works Coffee?

Huh. Koffee isn't needed fixed hwc.

And not an hwc causes troubles in official ROMs.

It is KSM. Kernel Samepage Merging. I drop this and completelly forgot about issues with camera and video.

You can live on LOS with Koffee as I live on crDroid with Koffee (45).

Also. I want to release kernel as more quickly. But I need to fix and implement some cpu-related stuff before release. 46 will be more battery-friendly.

----

To testers: how your experience from kernel with msm hotplug? What you think about replace Intelli-Plug with it?
[Galaxy S III Android Development] Noobkid77:
It's unfortunate Koffee experiences deep sleep in RR 5.8.5 with Super SU with WiFi left on
[Galaxy S III Android Development] fonfox:
the msm hotplug is standard active in the v4.4 yes I have not changed anything and think that he works brilliantly.
[Galaxy S III Android Development] acroreiser:
How to reproduce this?
[Galaxy S III Android Development] ArdaCsknn:
You don't need to be angry.I'm just trying to find why my battery drains so much on not SAM based roms.Sorry for bothering but I just want to use LOS without problems.
[Galaxy S III Android Development] acroreiser:
Just try it. You always can backup your ROM via TWRP.
[Galaxy S III Android Development] acroreiser:
My battery stats.
[Galaxy S III Android Development] froycard:
Hey, mr... I flashed your Koffee kernel... but it didn't work for me, I am using Resurrection ROM (RR) and because it has some serious problems with deep-sleep bugs, I just wanted tried your solution. I had MAGISK root app, that also it doesn't work with RR.

I removed MAGISK and installed SUPERSU for root permit. I flashed your kernel and afterwards I installed Boeffla Config App... but this application cannot find any kernel compatible with it. I removed your kernel and install the original one... and it worked!...

I am skipping any step that prevent your kernel from running on my cellphone (S3-I9300)?

Спасибо
[Galaxy S III Android Development] acroreiser:
Just flash ROM and kernel.

SuperSU is unneeded.
[Galaxy S III Android Development] froycard:
Sorry? maybe I sound like a newbie here... but Boeffla Config App requires root privileges in order to run or not? Each time I run it, on the top of the screen it shows the # notifications that states Boeffla Config is having root permit to run. Magisk doesn't work so I had to install SUPERSU for root permit.

and now you say I don't have to use SuperSU? I'm baffled... can you elaborate more?

Thanks
[Galaxy S III Android Development] acroreiser:
Magisk is built-in ResurrectionRemix. You are flashed lineage-su-addon?
[Galaxy S III Android Development] froycard:
yeah I did that too,,, and it didn't work since under settings I couldn't enable root access since it doesn't show in Settings->Developed Options (that option appears in Lineageos Rom, but not in RR)
[Galaxy S III Android Development] acroreiser:
You must flash only RR ROM and Koffee to get this work. No lineage-su, no supersu. Then install BCv2
[Galaxy S III Android Development] froycard:
ok roger that... thanks for your support
[Galaxy S III Android Development] Noobkid77:
Well it's pretty easy to reproduce I have Super SU not Magisk so if you leave WiFi on for more than 30 minutes the phone will not wake up.
[Galaxy S III Android Development] acroreiser:
Okay, I'll check it.
[Galaxy S III Android Development] acroreiser:
Cannot reproduce. I replaced Magisk with SuperSU and leave phone with wifi enabled. After 7 hours device successfully waked up and work normally.

Please check next things:

1. You're using Koffee kernel (not stock/Boeffla/other kernels)

2. Is your bug reproduceable with Magisk

3. Is bug not caused by other installed apps or mods
[Galaxy S III Android Development] acroreiser:
Koffee build 46 (19.02.18)

Changelog:

1. Intelli-plug replaced with MSM hotplug

2. Disabled l2_hsic wakelock

3. Readded bfq and conservative

4. Reducing cpu freq when screen is off for interactive governor

5. Some patches

6. Kernel version bumped
[Galaxy S III Android Development] kosmasgr:
What did you make sir ? Boot time significantly decreased here :laugh:
[Galaxy S III Android Development] Noobkid77:
That's strange since you can't reproduce it anyway I don't have any mods instead i uninstalled boeffla kernel and flashed Koffee Kernel then left WiFi on. And I haven't really tried it with Magisk because I uninstalled Magisk because of sleep issues before you made Koffee Kernel. So I only really tried it with SuperSU my brother but it's ok if you can't reproduce the sleep issues maybe it's my phone with the bug.
[Galaxy S III Android Development] froycard:
could anybody give some thoughts or review on this new version of this Kernel? Bugs? slowdown? reboots? it hangs?

I will appreciate that

:rolleyes:
[Galaxy S III Android Development] froycard:
yeah, I mean the Kernel... my bad. Corrected in my post
[Galaxy S III Android Development] MacLeod100:
Well... My dear S3 is flying with tis kernel ( i was using boeffla before ) and in stand by the battery life is amazing I ❤️ it !
[Galaxy S III Android Development] froycard:
What is the best governor that could be used for this kernel? The default is Pegasusq / standard... I am looking for performance, smooth use. Any suggestion for a best performance governor or settings?
[Galaxy S III Android Development] kosmasgr:
Interactive / standard , default settings
[Galaxy S III Android Development] acroreiser:
Default is interactive with MSM hotplug.
[Galaxy S III Android Development] froycard:
thanks for your reply,,, I will give it a shot...

---------- Post added at 11:13 PM ---------- Previous post was at 11:07 PM ----------

thanks for your reply...

sorry for the newbie question: what is MSM hotplug?
[Galaxy S III Android Development] acroreiser:
CPU hotplug puts unneeded CPU cores to sleep and wake sleeping cpus when more performance needed.
[Galaxy S III Android Development] acroreiser:
Better idling :)

CrDroid × Koffee × microG
[Galaxy S III Android Development] GalaxyS3only:
Dear A$teroid,

first thanks a lot for your work on Koffeekernel for our old but gold S3, keep up the good work!

I was waiting long time for a fix of sleepofdeath-bug under LOS with magisk and you just did it :good:

I'm running LOS+Magisk+ViperFx-& Dolby-Soundmodules.

Runs fine but I got problems with (really bad) stuttering music playback after my screen turns off (i think). Player is Odyssey.

Could it be the interactive governor, cause viperfx etc. need more cpu as usual musicplayback after screen went to sleep? Which governor/configs should i try for more performance in this case?

thx for help of any kind, if i can solve this i got my perfect SIII ;)
[Galaxy S III Android Development] froycard:
I thanked you for your information...

cool man... thanks for your application
[Galaxy S III Android Development] acroreiser:
Try to change governor to ondemand.

Interactive has hook for screen off state which reduce cpu frequency to 600MHz

OR remove ViperFX. It's well-known crap which hogs your cpu and battery at cost of slight sound quality increasing
[Galaxy S III Android Development] YoungRandyy:
What is MicroG? what does it do?
[Galaxy S III Android Development] acroreiser:
Koffee build 48 (01.03.18)

Changelog:

1. Task scheduler now more aggressive

2. Magisk deep sleep fix v3 (hopefully, better than v2)

3. Fix for panic, founded by opening large page in Chrome (exists in other kernels)

4. Some IO-related patches

5. Some CPU and CPU-cache related patches

6. Regenerated .config
[Galaxy S III Android Development] ArdaCsknn:
Do you know why mobile data have an effect on play services.I couldn't fix that keep awake problem even I disabled it from app ops.
[Galaxy S III Android Development] acroreiser:
Firstly, I am not a Google's engineer and Google Mobile Services is proprietary software.

Second. I use microG GMS implementation and has not any sleep issues.
[Galaxy S III Android Development] ArdaCsknn:
I tried microG but couldn't able to run youtube on my device.That's why I'm still using gapps sadly.Sorry for bothering.Can I compile your kernel to 4.3 somehow?
[Galaxy S III Android Development] lyolic:
I'm not shure that it is connected with new version of Kernel, but in my case central "Home" button and left "menu" button stoped working as expected approximatly in time when I installed latest kernel.

PS I use latest LineageOs
[Galaxy S III Android Development] acroreiser:
He he he he, why it works on my s3?

Что я делаю не так?
[Galaxy S III Android Development] acroreiser:
Install Boeffla or stock.
[Galaxy S III Android Development] heisenmark:
Hello [MENTION=7907521]A$teroid[/MENTION] , first of all I would like to thank you for the wonderful work you are doing with this kernel, thanks to you we can use magisk on S3 and enjoy a super smooth experience with the phone.

I have seen this screenshot and I am very surprised about your battery stats. Can you share with us your kernel configuration?

Thanks
[Galaxy S III Android Development] zarere:
Great kernel 10x a lot [MENTION=7907521]A$teroid[/MENTION]

I'm using this ROM

https://download.lineage.microg.org/i9300/

For more info

https://lineage.microg.org/

P.S. I use this battery

https://www.amazon.com/7200mAh-Extended-Battery-T-Mobile-Cellular/dp/B00GNSJU90
[Galaxy S III Android Development] acroreiser:
Defaults
[Galaxy S III Android Development] GalaxyS3only:
thx for your help, changed to ondemand, but there's slight musicstuttering even with screen on oO...

I'll try zzmove - relax and report.

And yes i know viperFX is buggy but as magiskmod with dolby the difference in music is amazing! So i'll try till someone names an alternative soundmod ;)
[Galaxy S III Android Development] ArdaCsknn:
I know it runs with it but I couldn't able to do it.Doesn't have any idea why.When I tried to open youtube it keep saying google play services not detected.
[Galaxy S III Android Development] Ashraf Iraqian:
try clean install the rom without installing official gapps.

About 4.3 stock rom boeffla kernel already have version 5.11 on EOL page

http://kernel.boeffla.de/sgs3/boeffla-kernel/Stable_jb43/Series 5.x/5.11/
[Galaxy S III Android Development] ArdaCsknn:
Nope I used it without gapps.I asked because l2_hsic wakelock is a big problem.Reduced wakelocks always better :)
[Galaxy S III Android Development] lyolic:
If SafetyNet check in latest magisk works with latest kernel?
[Galaxy S III Android Development] nobuteru:
On my S3 no it isn't working
[Galaxy S III Android Development] acroreiser:
Yes.
[Galaxy S III Android Development] nobuteru:
On my i9300 after lineage weekly update it isn't working. Before that yes

I am using Lineage OS 14.1 i9300 with gapps, v16 magisk stable, boeffla kernel version 6.0 stable with flashed over koffee build 48 and low ram zip

Magisk Hide function works, safety net now not...

Maybe I did something wrong after lineage update and re flash everything
[Galaxy S III Android Development] rocciacoraggiosa45:
my s3 freeze when i set max frequency 1.6ghz 1.7ghz only with this kernel all stock
[Android Q&A, Help & Troubleshooting] barrack1:
Updating apps through google playstore causes my rooted phone (Redmi1s) running a customized Cynogenmod 13 to bootloop. I think the internal storage is flaky and is causing updates to start bootlooping. Is there a tool for testing internal storage like disk drive scanning utilities?

When I tried to update the apps one by one, I thought I narrowed it down to a single problem app but when the bootloop issue happened again and I narrowed it down to a common app (Degoo 100Mb) so I think the internal storage could be faulty. I tried disabling xposed modules and uninstalling the xposed framework but it doesn't help.

What could be causing the bootloop problem during updates and does it make sense that the internal storage could be faulty?

edit:

I think the issue is caused by the customized rom not throttling the cpu well enough and the overheating will cause a crash/bootloop while updating many apps at once. Running updates manually on a few apps and fstrim will help avoid the issue but it looks like going back to stock rom is best thing to do.
[Kindle Fire Q&A, Help & Troubleshooting] joeldf:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.

I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.

I already rooted it and was then going through the process outlined in this thread:

https://xdaforums.com/showpost.php?p=54124313&postcount=3

so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.

And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.

It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.

I was going to try to load regular android on it, but now that seems out of the question.

Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.

Thanks,

-Joel
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
When it's in fastboot mode, use fastboot commands, not adb
[Kindle Fire Q&A, Help & Troubleshooting] joeldf:
Thanks,

The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.

So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned

FAILED (status read failed (Too many links))

finished. total time: 0.031s

But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.

Still, thanks. I guess it wasn't stuck or bricked after all.
[Kindle Fire Q&A, Help & Troubleshooting] joeldf:
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.

Moral of the story, do this kind of thing without interruptions... :D

I did re-watch your video all the way through and I see that what happened was normal.

Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.

Next thing is trying out a new rom.

Thanks again.
[Kindle Fire Q&A, Help & Troubleshooting] concorduser:
MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device
[G3 Q&A, Help & Troubleshooting] abdellahboughrom:
Is this normal? I click on power and volume down when logo apears i release then click again. Factory reset always shows after twrp. I want to go directly to twrp without factory reset. Thanks