yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] dictatorkara:
Partitioning is not working correctly, when I partition my SD card which is 64GB it only shows 9GB available when I plug it into my PC. Also, I can't use the ext file systems for some reason, only FAT32. I can partition it if I plug it into my old phone but when I put it back into the phone I am currently using it still shows only 9GB. I want a 50GB partition for music and other media and a smaller partition for apps and app data. Is there a way I can get this set up correctly or is there a way to put app data on the SD through the terminal?

Edit: I figured out a workaround. Still having the SD card problems but I can ignore that now. I set the download location to the SD card using the terminal, allowing me to move apps from within the settings menu. Then I used FolderMount to move the data of apps that have a lot of it, like Facebook, Spotify, etc.
[Sprint HTC One (M8)] asacado:
I've been looking for a kernel for AOSP/AOKP/CM11 based roms for our phone that supports USB fast charging. Thankfully almost all the roms I find are unified builds for the roms and most kernels support sense or GPE. Is there a kernel that supports this feature? The only one I've come across is furnace kernel, but as far as I can tell, it doesn't support the feature.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] turboed dragon:
I'm on the Hybrid X-Edition NK2 Rom. Tried using my camera to take a picture of some thing and the camera just stays blurry and doesn't try to refocus itself. Anybody else have this problem or know how to fix it?
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] dschachm:
Maybe try wiping cache and data. If that doesn't work try reinstalling the ROM or another rom. If that doesn't work go back to stock and take the phone to sprint.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] turboed dragon:
Pretty much sums up every thing I thought I needed to do. Just needed a 2nd opinion. Thanks.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] dschachm:
And did it work?
[Galaxy S 4 Mini Android Development] lombartz:
[GT-i9195][cm11] - [ROM](Feb.2016)&amp;[kernel](ECOACTIVE &amp; ECOPLUG)(OC/UV)(20151210)

This is a GT-I9195 CM11 kernel highly optimized to best possible performance and energy efficiency.

It may work on Slim (confirmed), AICP (confirmed) and Carbon Rom (confirmed) as well.

It will not work on any Samsung Stock based ROM.

- built from latest avalable CM sources

- CPU OC: 1998 Mhz (light: 1782 MHz) (default and max.)

- reworked freq- tables (unique 108 MHz-steps) for fast scaling

- CPU UV: -50mv (light: -25mv) (default, adjustable)

- GPU OC: freq steps changed to 192-400-608 MHz (light: 192-400-554 MHz)

- L2 OC/UV for extra performance (stock setting is a bottleneck, especially with OC)

- improved bus scaling

- RAM UV

- adjusted msm_thermal to prevent too much thermal throttling under heavy load

- added new "ECOACTIVE" governor and set as default

- added new "ECOPLUG" hotplug driver and set as default

- added FIOPS IO Scheduler and set as default

- added some more commonly used IO schedulers

- added fast random (and enabled via init.d)

- built with official gcc 4.8 with -O3 flags

"ECOACTIVE" is the ultimate governor for lag free performance and good battery life at the same time. It's based on interactive governor. It has a special input gain including the menu, home and back buttons. Separate input gain, fullspeed and eco/screen off phases minimize the use of high frequencys whithout slowing down the device noticably. The upscaling is more agressive during the input phase (default 1s). In the following fullspeed phase (default 10s, set to 0 for unlimited) full performance is allowed. The third phase is configured for battery saving usage while reading, watching videos, music listening or when the screen is off. This ensures maximum responsiveness and best gamig experience along with best possible battery life when reading, listening to music etc.

"ECOPLUG" is an alternative hotplug driver based on AutoSMP. It works much snappier on our device than the stock msm-mpdecision. On default setting second core is down when screen is off.

Everything is fully "pretweaked".

Flash from recovery, enyoy... no need to adjust anything via init.d or app.

Dont flash this kernel if you don't know how to fix problems after flashing !

Make a backup before flashing this kernel !

The hardware parameters are adapted near to the limits of my phone. This means this kernel will not work if your devices hardware cannot handle the OC/UV.

If you are lucky you run the fastest kernel available for your phone :D

If your phone doesn't run with the "lombartz kernel" you may try the "lombartz light kernel" with less agressive OC/UV.

My latest pure CM11 ROM build (Feb. 2016):

https://drive.google.com/open?id=0B-1RyGtdRvCwWEVfc0ZhTTRzdXc

If you use Xposed framework you need to flash XposedFix after ROM.

regards,

lombartz
[Galaxy S 4 Mini Android Development] lombartz:
...updated.
[Galaxy S 4 Mini Android Development] andreux84:
this kernel is amazing but i have a problem when i connect the smartphone at bluetooth radio. In this case my smartphone freeze and always reboot.

sorry for my english
[Galaxy S 4 Mini Android Development] lombartz:
Hi, thanks for yor feedback Have you already checked if you have the same problem with the last official CM11 kernel from 20150105 ?

regards,

lombartz

edit: tested with my laptop as bluetooth- speaker with no problems. My actual Version is heavily tweaked at the Moment but nothing changed with audio or bluetooth.

Anyone else with bluetooth- playback issues out there ?

edit: found a possible reason for the problem. hope it's fixed in new version (see OP)
[Galaxy S 4 Mini Android Development] bongster:
Thank you for this. Any chance to include f2fs into the kernel?
[Galaxy S 4 Mini Android Development] lombartz:
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.

regards,

lombartz
[Galaxy S 4 Mini Android Development] bongster:
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
[Galaxy S 4 Mini Android Development] lombartz:
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.

If this one boots your phone doesn't like my OC/UV settings...
[Galaxy S 4 Mini Android Development] bongster:
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?

I never tried it...
[Galaxy S 4 Mini Android Development] lombartz:
Yes.
[Galaxy S 4 Mini Android Development] bongster:
No luck. I also tried flashing the latest cm11 nightly with no luck.

If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
[Galaxy S 4 Mini Android Development] spixy:
20150212 working nice with latest Carbon 4.4.4 :)

can you please add option to underclock min CPU to 162/270 MHz?
[Galaxy S 4 Mini Android Development] lombartz:
This is a technically useless placebo feature and doesn' t save any energy.

The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.

br,

lombartz
[Galaxy S 4 Mini Android Development] lombartz:
Hmm, the reason is the fstab.qcom, /cache and /data is expexted to be ext4.

Can be changed but I dont know how to allow both fs at the moment.
[Galaxy S 4 Mini Android Development] spixy:
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you :)

but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)

But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
[Galaxy S 4 Mini Android Development] lombartz:
I suppose you mean 50 mV ? The lower UV limit is reached at about 384 MHz anyway.

Youre right with hfpll. Only at 384 MHz the CPU runs with pll8.

If you undervolt @ 384 manually as much as possible you will find that you cannot go noticeably lower if you clock down further.

At the Moment I am testing other tweaks that should be more effective an give some extra performance.
[Galaxy S 4 Mini Android Development] lombartz:
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.

If it boots you are a tester for all the new changes ...

This Version will not run with ext4 /cache and /data partitions.
[Galaxy S 4 Mini Android Development] bongster:
Thank you very much!

After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.

Update:

I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
[Galaxy S 4 Mini Android Development] lombartz:
I am sorry. Should not publish something I did not test myself...

What OC Values did you use with f4ction ?
[Galaxy S 4 Mini Android Development] bongster:
No problem. I'm aware of the issues that can happen.

Normally I use f4ction as it is with 50uv. For the test I oc'ed to 1998mhz.
[Galaxy S 4 Mini Android Development] lombartz:
Thanks, i'm using xposed module for that atm.

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
Hi [MENTION=5119352]lombartz[/MENTION]

I have a problem with few wakelocks after Lombartz_ECOACTIVE_CM11_Kernel_20150622_a.zip installation: mmc1_detect, suspend_backoff and bam_dmux_wakelock. Please see attached screenshots

Lombartz_ECOACTIVE_CM11_Kernel_20150622_a.zip was installed by me 3 times in last days alternately with Lombartz_ECOACTIVE_CM11_Kernel_20150618_a.zip and every time wakelocks appears again on 0622 build.

For now i have returned to Lombartz_ECOACTIVE_CM11_Kernel_20150618_a.zip and wakelocks are gone.

/edit/

ROM: VanirAOSP

Modem: I9195XXUCNK5
[Galaxy S 4 Mini Android Development] AndroidxWolF:
Can I get an OTG support when I flash this ROM ?
[Galaxy S 4 Mini Android Development] lombartz:
Yes, but you need an Y adaptor for supplying the connected device with power.

regards,

lombartz
[Galaxy S 4 Mini Android Development] lombartz:
Hi,

i tried to reproduce your problem for a few hours but no success. The problem is not caused by the kernel itself but something in combination with your ROM, settings or an app. I made a special version for you with two reverted commits wich may be the reason for wakelocks in your case. Please test and report ...

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
Thank You

Will test today
[Galaxy S 4 Mini Android Development] piskor:
With this special version wakelocks still occurs, but please don't worry about it for now

I will try to investigate, if it is my ROM / configuration problem, especially if other users do not have such problems
[Galaxy S 4 Mini Android Development] lombartz:
I don't think you have a real problem, especially the bam_dmux_wakelock extremely varies with the signal strenght from day to day on my phone. Didn't you use a huge mmc read ahead buffer ? This may have something to do with your mmc1_detect_wakelock.

Btw your piskor_20150625 version has screen on/off depending scaling and wakeup gain. If screen switches off the phone will run in eco_mode immediately and scaling up faster after screen turns on.

That feature was added after the 20150622 version.

I will have a look at the sources if i can't find any other change that may explain your issue.

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
[MENTION=5119352]lombartz[/MENTION]

One more time many, many thanks for Your great work.

Yesterday I switched to Lolipop based ROM and now I am eagerly waiting for your turn in that direction :)
[Galaxy S 4 Mini Android Development] Youpy:
lombartz first many thanks for the CM11 ROM it works really nice ! I wasn't able to find another up to date cm11.

Now I'd like to use your ecoactive kernel. In case I have trouble with it I suppose I just have to flash back the cm11 stock kernel with CWM. Or may I get bigger issue ?
[Galaxy S 4 Mini Android Development] lombartz:
Make a backup of the rom an all your data before flashing the lombartz kernel the first time. There is a small risk of data corruption if your phones hardware is overstrained. If your phone boots fine don't tune any of the kernel parameters for the first few hours. If you have trouble flash the stock kernel from OP.

If your life depends on your phone don't use this kernel ... ;)

regards,

lombartz
[Galaxy S 4 Mini Android Development] Youpy:
Thanks again lombartz. As you can see I'm still alive ;)

I just flashed your kernel, installed a game (that's better to confirm it works), made phone calls ... everything is running fine with default parameters for one day and half.
[Galaxy S 4 Mini Android Development] lombartz:
Thanks for the report and thanks.

Seems not many downloaders survived the flashing ...

If you like to test the latest version i send you a download link.

regards,

lombartz
[Galaxy S 4 Mini Android Development] soseono:
Thank you

I just went from the stock 4.2.2 to SlimKat, PA-gapps Nano and your kernel. So far, so good! Things feel super snappy and the battery seems to last longer. I do get a bunch of the "Unfortunately Google Play Services has stopped" error after reboot, but it happens only after a boot-up so I can live with it. I just wanted to say thank-you for your good work! :good:
[Galaxy S 4 Mini Android Development] Youpy:
Ok Lombartz, I'll test it, but next week only, not before Monday.

I can't do anything wrong with my phone before the end of the weekend :)
[Galaxy S 4 Mini Android Development] lombartz:
I don't think your problem is kernel related you can test that by flashing the stock kermel from OP. I think there's something wrong with your gapps installation.

Thanks for report.

regards,

lombartz
[Galaxy S 4 Mini Android Development] lombartz:
Please stay at 20150622 atm there are problems to solve in the test version.

regards,

lombartz
[Galaxy S 4 Mini Android Development] soseono:
Actually, I agree. It's most likely a gapps + rom issue because I've seen others with similar reports. I just wanted to say that that's the only problem I've seen so far and everything else is fine. Again, I do appreciate your work. It almost feels like a different phone!
[Galaxy S 4 Mini Android Development] soseono:
fast_charge?

Would you please, please add fast_charge to your kernel? I loved your kernel very much, but moved to the f4ktion kernel recently only because of the USB fast_charge. I got a quick charge adapter and the fast_charge (set at 1500) and the adapter (1800 max) cut down charging time by half. The only thing is, except for that, I really miss your kernel... :(

Please...? :crying:
[Galaxy S 4 Mini Android Development] lombartz:
I tested that a few months ago but it broke the battery charging with OTG device connected. I removed that because i don't want only partially working features in my kernel.

Please test with f4ktion kernel if your battery gets charged while using an external USB HDD at the same time and report here.

I will have a look at that then.

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
Hi [MENTION=5119352]lombartz[/MENTION]

Still on Kitkat? Don't you think sometimes about switching to CM12.1? :D

I miss your kernel :crying:
[Galaxy S 4 Mini Android Development] soseono:
Uh... I don't have USB OTG setup so I can't test it, but I can see how drawing a large amount of current can be a problem in such a situation. I agree it's a partially working feature. One thing I found was that the kernel setting won't stick, so I had to let Tasker modify the setting after every boot.

Meanwhile, I flashed back your kernel and got reminded of why I loved your kernel in the first place: the stability, no unnecessary overload, no heat, good battery life, etc. Thank you again for your work. I think I'll stick and won't change again. Bye bye fast charge :crying: :crying:

---------- Post added at 05:34 AM ---------- Previous post was at 05:27 AM ----------

A question just occurred to me after I wrote the previous message. Is there a way to detect whether the charging current is coming from an AC source or a USB host/OTG source? If not, I guess the matter is closed. If yes, though, is it possible to set up fast charge on AC current but not on USB/OTG?

I know next to nothing about Android kernels, so please bear with me if this question was too basic. According to this source, it looks like USB and AC states work separately, hence my question.
[Galaxy S 4 Mini Android Development] lombartz:
The setup is as follows: The phone is connected via an y- adaptor to an external HDD and a power supply.

The power supply delivers the power for both the phone and the drive.

The kernel must detect that and enable OTG and charging mode at the same time in that situation.

This did not work properly for me with f4ktion kernel and in my kernel with fastcharge support. The phone just showed the battery charging but in truth it was still running on battery.

If someone reports this working properly with actual f4ktion kernel i will consider to add fastcharge to my kernel.

Thanks for your nice rating ....

regards,

lombartz
[Galaxy S 4 Mini Android Development] lombartz:
;)

Hi piskor,

yes, still on kk and will stay there, but already downloaded the 12.1 sources ... :p

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
Hurray!

repo sync && .... :)

Will be watching your threads. Thanks
[Galaxy S 4 Mini Android Development] andrisrozkalns:
Update?
[Galaxy S 4 Mini Android Development] andrisrozkalns:
[MENTION=5119352]lombartz[/MENTION] Are you alive?
[Galaxy S 4 Mini Android Development] lombartz:
Hi,

yes of course. I'm still looking

reguarly here.

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
And still on Kitkat? :)
[Galaxy S 4 Mini Android Development] lombartz:
Hi piskor,

yes because it's running absolutely smooth and error free.

I gave up the LP Kernel because of annoying repo sync errors.

Sorry ...

regards,

lombartz
[Galaxy S 4 Mini Android Development] piskor:
No problem. Maybe someday ... :)

All the best in real live
[Galaxy S 4 Mini Android Development] lombartz:
Update

... cheers,

lombartz
[Galaxy S 4 Mini Android Development] haloass65:
Have a problem

Hello

I have a Problem but let me tell you my story first.

I used your kernel and i never had a problem except random rebootss (the random reboots was okay , 2-4 random reboots in one day)

Then i hardbricked my phone (my fault) and sent it to Samsung

They changed the Hardware and i root my phone and flashed cwm after that.

I tryed to install your kernel after cm 11 clean flash but when i ever open my phone i cant use it properly beacuse i get freeze,randoom reboots every 5 seconds :/

Btw; are you german :D
[Galaxy S 4 Mini Android Development] lombartz:
2-4 random reboots per day are a serious problem. You should not use this kernel if you have random reboots. Try the cm stock kernel from the OP. If you have reboots even with that one your problem is not caused by the kernel, otherwise your phones hardware cannot handle the lombartz tweaks and you should live with the cm stock kernel.

Jo, deutsch:cool:

regards,

lombartz
[Galaxy S 4 Mini Android Development] haloass65:
Lol cool :D

Also bevor ich meinen smartphone gehardbricked habe konnte

Ich mit 2- 4 randoms reboots pro Tag leben aber nachdem Saturn bzw. Samsung meine Hardware gewechselt hat funzt es gar nicht. Jede 5. Sekunde startet mein Handy neu

(Nur auf deutsch^)

Aus irgendeinen Grund ist mein English am *****

---------- Post added at 08:21 PM ---------- Previous post was at 08:12 PM ----------

Es ist schon schade das ich deinen Leistungsstarke Kernel nicht mehr benutzen kann. :/
[Galaxy S 4 Mini Android Development] lombartz:
Probiere den cm stock kernel vom 1. Post, wenn es damit geht, ist Deine Hardware mit dem lombartz kernel überfordert. Wenn nicht, hast Du ein anderes Problem als den Kernel. Dein Handy darf keine Autoreboots machen.

Gruß,

lombartz
[Galaxy S 4 Mini Android Development] lombartz:
Update

Added 20150923_c Version to OP.

Optimized usage of low(est) frequency(s) for better battery life.

Seems to work well without affecting performance.

Tell me what you think ...

regards,

lombartz
[Galaxy S 4 Mini Android Development] haloass65:
Stock kernel funktioniert. Und kernel update funzt nicht.

Na ja dann geht es halt nicht :/

Trotzdem Danke :)

Keep up the good work ?
[Galaxy S 4 Mini Android Development] haloass65:
Idee

Könntest du den Kernel zu 1.7 GHz begrenzen

Vielleicht könnte es funktionieren :)

Gruss
[Galaxy S 4 Mini Android Development] lombartz:
Update

Removed some of the extreme power saving stuff, was causing stuttering in games and video recording and not saving as much juice that it was worth that.

ecoactive switching to idle timer only when screen is off now

regards,

lombartz
[Galaxy S 4 Mini Android Development] Member123456:
Rebooting issues

Hi..i flsahed this kernel on latest cm11. The phone runs well first 30min/1 h later on it starst rebooting continuously. I dont know why. Please help me cuz id like to uae this kernel. Its really fast btw
[Galaxy S 4 Mini Android Development] lombartz:
Thanks for your Report. If your phone runs for a certain time try to set the max CPU Frequency to 1782 or 1890 MHz and/or increase the CPU Voltage by 25 or 50 mV. If your phone runs with that settings please report here.

Maybe this kernel is just a little bit overtuned for your phone. In this case you should better use the stock kernel.

I don't know how many users are out there who are interested in a mild version for weaker hardwaee. I would build one if there are testers and I get a bit more thanks for my work.

regards,

lombartz
[Galaxy S 4 Mini Android Development] Member123456:
Thanks for replying. I dont know much about this stuff. u said i should increase voltage by 25 or 50 but i dont know where i can do that. Btw i tried to put max frequency on 1890mhz on ecoactive perfomance but it still reboots. I have noticed also that when i use the device intensly it starts rebooting in continuous.
[Galaxy S 4 Mini Android Development] lombartz:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
[Galaxy S 4 Mini Android Development] Member123456:
Ok thanks..so its still rebooting. Idk if it cuz i use it too much or what!?
[Galaxy S 4 Mini Android Development] lombartz:
look at OP, please:

The hardware parameters are adapted near to the limits of my phone. This means this kernel will not work if your devices hardware cannot handle the OC/UV.

If you are lucky you run the fastest kernel available for your phone.

Seems you are not lucky, sorry....
[Galaxy S 4 Mini Android Development] lombartz:
Update

introduced ECOPLUG hotplug driver.

Seems noticeably snapier than the msm-mpdecision.

regards,

lombartz
[Galaxy S 4 Mini Android Development] Kopaxi:
Deleted

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] RuffBuster:
Tried latest version of kernel with the last September release of cm11 and reboots a couple of seconds after loading lock screen. When trying previous versions of your kernel with the cm11 version linked in your op things were working OK. But that version of cm11 is vulnerable to stage fright attacks so won't be testing that version unfortunately.
[Galaxy S 4 Mini Android Development] lombartz:
Thanks for reporting. I didn't notice there are new cm11 builds.

I will have a look at that and remove the link to my build.

regards,

lombartz
[Galaxy S 4 Mini Android Development] RuffBuster:
Although there is a new build because of the stage fright security flaw, Google F'd up as there is still a stage fright v2 bug present which is worse than the first security flaw. And so far CM team hasn't yet released a new build to combat this. The patches have been released and I know that Didierk is currently trying to build the new CM11 with all the latest patches. Maybe wait on him? But I look forward to being able to run your kernel.