yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Android Development] muiriddin:
I'm running R14 with infected's CM12 build built on 1/06. This morning my alarm clock (alarm clock extreme) when it was playing music had a nasty buzzing noise along with the music. I have not had any other audio issues with this so far (but I haven't really run it through its paces yet). However I thought I would post and ask if anyone else had an audio issue of some sort
[G Pad 8.3 Android Development] vimesUK:
This is the first time I have used this kernel, and thus kept to a 4.4.2 base with the latest Cyanogenmod ROM. As yet it has seemed fine but I have not test much of the audio aspect of this release.

When I used ckrets kernel there was a buzzing issue then which I noted during Youtube video playback....

[YOUTUBE]nUaEhe26dN8[/YOUTUBE]

you can here a small one in the above video around 16 secs or so in.
[G Pad 8.3 Android Development] muiriddin:
That does appear to be a similar sound to what I heard this morning in the alarm. It was not happening with the previous version of the kernel. I'll test things some more in the coming days and see what I can find out...
[G Pad 8.3 Android Development] MSephiroth:
Thanks Rick Roll for you work. I tried this last kernel and found out two bugs: location based on ONLY network didn't work for me, maps continued saying that my location services were disabled. Everything ok instead if i select GPS + network location. The other one concerns the brightness of the display: if i select adaptive brightness in screen setting, then i'm not able to use the slider anymore to change brightness level.

Those 2 bugs are not present on the previous version of the kernel. (and by the way, I have 4.4.2 base).

Rick you have one pm from me. Hope you can help me.

Keep up the good work I love your kernels ;)

Ciao
[G Pad 8.3 Android Development] DSC05:
I have the same location issues on infected cm12 stock kernel since a few nightlys.
[G Pad 8.3 Android Development] MSephiroth:
So probably it's a bug of cm stock kernel since r14 is built from that! try previous redkernel (r13), it's working for me
[G Pad 8.3 Android Development] ckret:
cm kernel was not update for a month now

it is propably rom related
[G Pad 8.3 Android Development] MSephiroth:
oh well I don't know but if i take last nightly and flash r13 i don't have the bug

Edit: my fault...with last nightly i have the bug even using r13 ckret you are right ,probably is ROM related

Edit2: a reboot fixed brightness issue!
[G Pad 8.3 Android Development] muiriddin:
I haven't changed my config, but it has only happened the one time and over the weekend I was using multi-media capabilities on my tablet. For me this sound issue is rare...

The primary sound things I do with the tablet are netflix, games, poweramp and alarm clock extreme. I've only had the strange sounds one of the mornings I've use the alarm.
[G Pad 8.3 Android Development] Maxxd01:
Thanks for the work.

Can I install this over AOSP 5.0.2 ?
[G Pad 8.3 Android Development] Darkmasterhk:
No, this kernel is cm based, if you flash it on aosp you will get some graphic glitches.
[G Pad 8.3 Android Development] King_Rat:
Nice work dev ^^ running on CM11 latest snapshot... Brightness bug at boot sorted (initial boot, yet to reboot) audio glitch with video gone =)

10x

Sent from my Kin[G]_Pad ™
[G Pad 8.3 Android Development] cobra698:
hi,how can I get whites whiter?i have 255 255 255.I have to change this value?thanks
[G Pad 8.3 Android Development] dabizb:
Hello, I want install this kernel. It install like another zip with recovery??. And how revert it if not run well?. Thanks.

Enviado desde mi LG-V500 mediante Tapatalk
[G Pad 8.3 Android Development] Darkmasterhk:
yeah you can flash it like any other kernel from recovery.

if you want to revert to stock just flash your rom again.

oh and make sure your rom is cm based.

and for some reason sometimes i get weird fc's when i'm not wiping

dalvik/cache after flashing this kernel, even thought it normally shouldn't be

necessary.
[G Pad 8.3 Android Development] dabizb:
Thank. Yes, I have alternatively nightlys CM12 or infected Cm12

Enviado desde mi LG-V500 mediante Tapatalk
[G Pad 8.3 Android Development] tekka-maki:
cm base & aosp same same? is it ok w/ sliimkat 4.4.4 and 4.2.2 base on V500? seems 4.4.2 base preferably, but i thought aosp roms like slimkat preferred 4.2.2?

---------- Post added at 10:05 PM ---------- Previous post was at 09:59 PM ----------

[/COLOR]

i've had ths problem throughout many roms and kernels and have come to live with it. i thought it was a hw bug.
[G Pad 8.3 Android Development] Darkmasterhk:
If I get this right you mixed up some stuff, since lollipop we have aosp

Roms, which result in graphic glitches when you flash an cm kernel to them.

This is not related to the base files from 4.4.2 and 4.2.2 these work on different

Partitions and I have no idea what they exactly include (firmware?).

And for slimkat, yeah with stock kernel you should use 4.2.2 base with

Red or Mani 4.4.2, but I'm not sure if the newest red kernel will work on

Slimkat, cause it's for lollipop.
[G Pad 8.3 Android Development] dabizb:
I have a problem. I loss the recovery when flash redkernel and I can't flash the CM12 updates. How restore the recovery??? Thanks.

Enviado desde mi LG-V500 mediante Tapatalk
[G Pad 8.3 Android Development] muiriddin:
Recovery should not disappear from flashing a kernel. Have you tried adb reboot recovery when connected to computer?
[G Pad 8.3 Android Development] tekka-maki:
thanks for feedback!

i think 4.2.2 is jellybean bootloader.

so to be clear,we can't run 4.4.2 kk bootloader on slimkat but we can a certain version of red kernel? i thought this kernel required 4.4.2 but what do i know... I'd actually like to move to 4.4.2 as i have a couple of issues i hope it will resolve plus i wanna uv & better governors than stock. namely, my problems are sometimes gpad sporadically doesn't wanna wake from deep sleep, so need to hardboot (biggest problem), the audio glitch (no biggie, i think its hw related), &... fu*k, i cant even remember right now. But I think this brilliant kernel & new base might fix things plus better battery life.

Anyway, i don't wanna brick this thing again (stupid effin bootloader!), so... i thought it was red kernel (which? no clue) then kk 4.4.2 base & hopefully no brightness bug.

Just don't wanna avoid rebuilding w/ new rom, too time consuming! arrrrgh... help anyone?

---------- Post added at 08:08 PM ---------- Previous post was at 07:48 PM ----------

i know what i forgot. when running slimkat official, stock kernel, & 4.2.2 base, it won't allow me to switch to ART runtime, major drag, love ART on my phone. i reckon this is bootloader related...
[G Pad 8.3 Android Development] tekka-maki:
ok, installed redkernel 110 on slimkat 4.4.4 build 9 weekly 8326, no hiccups, nice to have undervoltage; so many optimized governors which is nice.

it still won't allow me to select ART runtime, gotta be that 4.2.2 base bootloader. wonder if i should just slam 4.4.2 on there... any audio glitch and deep sleep hang still tbd...
[G Pad 8.3 Android Development] Darkmasterhk:
Sorry it's probably related to my English, that it doesn't came out clear:

Slimkat on stock kernel needs 4.2.2

Slimkat on red kernel needs 4.4.2

The aosp/cm thing was only related to lollipop roms.

Normally art should work just fine, I've used slimkat on art until the first cm12 rom for our tablet came out.

And i never had any deep sleep issue, which slimkat are you using? Stock/infected?

About audio glitch, I think I read something about it a few pages back.

In case you want to switch your base files it might be necessary to format your external SD.
[G Pad 8.3 Android Development] tekka-maki:
Interesting. So, I'm running latest stock SlimKat weekly now w/ base 4.2.2, all appears fine, except maybe a (well reported) amped up brightness issue. So maybe doesn't need, but works better? I'll install v4.4.2.

that format issue, yes... I've heard some talk about that, but still seems like anecdotal yes? i should still be able to copy its contents over to computer prior even after base change right? Because I'd prefer not to bother unless it seems to be true that it is drastically slower or something.

Edit: no brightness issue in fact. seems great actually. not sure if i should even bother, though i like the idea of the newer 4.4.2 20D that Deltadroid posted, especially because it doesn't tough aboot or recovery (though i suspect i would still need to install the TWRP for 4.4.2 base).

Dunno what I would gain 'cuz SlimKat on red kernel doing great w/ 4.2.2 :/ hmmm...
[G Pad 8.3 Android Development] jonup:
I've used this kernel on both slimkats with either base without noticing any issues. Only worry about it if you have an issue.

I don't understand why you guys still even discuss this. I guess some people spent their entire life preparing for the rain and never enjoy the sunshine
[G Pad 8.3 Android Development] tekka-maki:
Love the sunshine sir. Also love an unbricked gpad for kiddo's movies during daily commutes. i slapped 4.4.2 on this morning, so far so good.
[G Pad 8.3 Android Development] Rick Roll:
r015 released for CM12 based roms!

Download: https://www.androidfilehost.com/?fid=95916177934524088

Full changelog on github.
[G Pad 8.3 Android Development] beroid:
wait for AOSP based roms?
[G Pad 8.3 Android Development] Cal:
All good here w/Infected's CM12-2.5.2015. Very smooth & battery seems as good as r014 ! :)
[G Pad 8.3 Android Development] atlharp:
Running very nice with the 2/6 Commotio build.
[G Pad 8.3 Android Development] Darkmasterhk:
hey [MENTION=4575133]Rick Roll[/MENTION] i just saw, you added blu_plug to your kernel and i'm quite curious about it,

i love code blues hotplug on my n5, how does it do on our tablet, is it as smooth as on the n5.

and are you thinking about adding the governor, too?
[G Pad 8.3 Android Development] Jansxel:
Hey [MENTION=4575133]Rick Roll[/MENTION] can you upload the kitkat version on androidfilehost or just the latest version of redkernel on kitkat
[G Pad 8.3 Android Development] Bronando:
How do you enable bluplug?
[G Pad 8.3 Android Development] Darkmasterhk:
it's not in the kernel, yet.

I just saw it on git, but it seems [MENTION=4575133]Rick Roll[/MENTION] reverted it again.
[G Pad 8.3 Android Development] Disrupthor:
[MENTION=3083704]rick[/MENTION] Roll, could you add more TCP congestion controls specially Westwood? Also with me r15 is having troubles handling streaming videos via Wi-Fi and audio thought Bluetooth on a2dp simultaneously.
[G Pad 8.3 Android Development] Rick Roll:
r016 Released!

Full changelog on github.

Download CM: https://www.androidfilehost.com/?fid=95916177934540435

Download AOSP (5.1 tested): https://www.androidfilehost.com/?fid=95916177934540431
[G Pad 8.3 Android Development] davebuk:
Hi all

Running r016 without issues. One question though, my Bluetooth headset connects during the pairing cycle and works, but when I switch the tablets Bluetooth off and on, even when I click on the paired device, it tries to connect but fails. The only way to re connect is to forget the paired device and re pair every time.

Is this something that is kernel related or a CM12 issue? I tried mani kernel and had the same issue so may have answered my own question, but any advise would be grateful.
[G Pad 8.3 Android Development] jonup:
This is a long shot, but it might have something to do with your BT devices and not the tablet. As in the BT device still thinks it's connect to that connection. Have you tried restarting the BT device after switching BT off and on on the tablet?
[G Pad 8.3 Android Development] davebuk:
Hi. I've tried tablet bluetooth on then device on, device on first then tablet, device off and back on while tablet bluetooth still on etc and every time the same. Tablet shows the device as an already seen before and paired device, tries to connect then nothing more.
[G Pad 8.3 Android Development] davebuk:
Tried this morning after flashing 20150315 nightly so kernel is back to CM stock. Same bluetooth behaviour so I guess its a CM12 issue rather than kernel.
[G Pad 8.3 Android Development] timnolte:
Yes, this has pretty much been the problem I've had since day one of using even the unofficial CM12 nightlies. It's pretty annoying to say the least.
[G Pad 8.3 Android Development] nytral:
Hi,

thanks for the kernel, it works nicely so far! May I ask for F2FS support? it's always nice to have, I am spoiled by using it on other tablets :silly:
[G Pad 8.3 Android Development] Deltadroid:
[MENTION=4575133]Rick Roll[/MENTION] I was looking at your kernel installation script and it seems like it would be possible to use it as a universal kernel patcher to edit the boot command and set the kernel permanently into permissive mode to test selinux policy. I tried to write my own script, but I wound up with a soft brick a few times. Could you help out? I thought the script would just use dd to get the current boot.img, unpack it, then pack it back with a modified boot command that appends "androidboot.selinux=permissive". What do you think?

I'm noticing that there are a bunch of selinux denials with the latest cyanogenmod, and I thought it would be nice to have the option of permanently enabling permissive mode to avoid selinux problems on stock cm roms.

best regards.
[G Pad 8.3 Android Development] aicjofs:
That's actually my script, ckret started using it, and then Rick Roll.

If I am understanding you are you just trying to add it to the end of the kernel command line? So that (as just an example)

console=ttyHSL0,115200,n8 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 lpj=67677 androidboot.hardware=awifi vmalloc=400M no_console_suspend

becomes

console=ttyHSL0,115200,n8 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 lpj=67677 androidboot.hardware=awifi vmalloc=400M no_console_suspend androidboot.selinux=permissive

?

If so you would need to edit the mkbootimg.sh file in the kernel directory of the installer and find this line

echo /tmp/mkbootimg --kernel /tmp/zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"$(cat /tmp/boot.img-cmdline)\" --base 0x$(cat /tmp/boot.img-base) --pagesize 2048 --ramdiskaddr 0x82200000 --output /tmp/newboot.img >> /tmp/createnewboot.sh

On that line edit this

--cmdline \"$(cat /tmp/boot.img-cmdline)\"

to this

--cmdline \"$(cat /tmp/boot.img-cmdline) androidboot.selinux=permissive\"

make sure there is a space between "cmdline)" and "androidboot"

You may actually be doing it right, I haven't looked at Rick Roll's kernel config but there might be a flag that needs set for SElinux to be able to stop enforcing.
[G Pad 8.3 Android Development] Deltadroid:
Yes, I might also have to append something to turn off selinux. For example:

androidboot.selinux=permissive selinux=0

Thanks, BTW, for the fast and detailed response. It helped a lot.

edit:

Ive created a universal kernel boot command line patcher that will take any kernel that is installed and make it boot into permissive mode.

v500-universal-selinux-disabler-loki-signed.zip

NOTE: This flashable zip is to enable permissive mode for kernels that use loki tool only.

This will append "androidboot.selinux=permissive selinux=0" to the current boot command line. Do not apply this script twice to the same kernel, or this will be appended twice.

Note: this fixes bluetooth headset not connecting after restarting bluetooth service or rebooting the device. Otherwise, selinux is blocking the bluetooth service from opening files.
[G Pad 8.3 Android Development] Deltadroid:
[MENTION=4575133]Rick Roll[/MENTION]

Please add this to your kernel device tree to fix bluetooth denials.

http://review.cyanogenmod.org/#/c/93433/

I would like to fix the other denials, but I need help. Can you help me?

I'm wondering what these denials are....

cat full_selinux.log
<4>[ 1993.439392 / 04-04 23:44:31.994] type=1400 audit(1428183871.994:168): avc: denied { getattr } for pid=18626 comm="toolbox" path="/factory" dev="mmcblk0p19" ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:unlabeled:s0 tclass=dir permissive=0
<4>[ 1993.439971 / 04-04 23:44:31.994] type=1400 audit(1428183871.994:169): avc: denied { getattr } for pid=18626 comm="toolbox" path="/mpt" dev="mmcblk0p31" ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:unlabeled:s0 tclass=dir permissive=0
<4>[ 1993.440368 / 04-04 23:44:31.994] type=1400 audit(1428183871.994:170): avc: denied { getattr } for pid=18626 comm="toolbox" path="/persist" dev="mmcblk0p25" ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:persist_file:s0 tclass=dir permissive=0
<4>[ 1993.440765 / 04-04 23:44:31.994] type=1400 audit(1428183871.994:171): avc: denied { getattr } for pid=18626 comm="toolbox" path="/persist-lg" dev="mmcblk0p15" ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:unlabeled:s0 tclass=dir permissive=0
<4>[ 1993.441131 / 04-04 23:44:31.994] type=1400 audit(1428183871.994:172): avc: denied { getattr } for pid=18626 comm="toolbox" path="/sns" dev="mmcblk0p16" ino=2 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:sensors_persist_file:s0 tclass=dir permissive=0
<4>[ 1993.446563 / 04-04 23:44:32.004] type=1400 audit(1428183872.004:173): avc: denied { getattr } for pid=18612 comm="Thread-750" path="/data/tombstones" dev="mmcblk0p36" ino=565249 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:tombstone_data_file:s0 tclass=dir permissive=0

Running the logs through audit2allow gives:

cat full_selinux.log | grep denied | audit2allow -p sepolicy

#============= untrusted_app ==============
allow untrusted_app persist_file:dir getattr;
allow untrusted_app sensors_persist_file:dir getattr;
allow untrusted_app tombstone_data_file:dir getattr;
allow untrusted_app unlabeled:dir getattr;
[G Pad 8.3 Android Development] Rick Roll:
r017 Released!

Changes:

Updated toolchain

New touchscreen driver for AOSP kernel. (Knock on is on by default)

New default hotplug driver: dyn_hotplug by [MENTION=3750240]stratosk[/MENTION]

GPU: Synced with 5.1 kernel sources from mako.

This kernel is now bumped with livebump script by [MENTION=2174433]Skin1980[/MENTION]

Download CM version: https://www.androidfilehost.com/?fid=95916177934554992

Download AOSP version: https://www.androidfilehost.com/?fid=95916177934554994
[G Pad 8.3 Android Development] Darkmasterhk:
just flashed and noticed 2 things:

1) did you drop synapse support? doesn't work on a clean flash.

2) could it be that on the new hotplug the cores don't sleep anymore? (two screenshots right new, left intelli)

or is it maybe related to trickster or something?

(i know the uptime isn't really long, but it didn't change while writing here.)

the rest seems to work quite fine (really smooth) and i like the bumped script. :D
[G Pad 8.3 Android Development] Rick Roll:
It's sleeping fine here (by default, the minimum for this hotplug is 2 cpus online and you can change it with synapse), for synapse support you need to flash the universal kernel manager from This thread.
[G Pad 8.3 Android Development] Darkmasterhk:
i know about ukm and flashed it still nothing, what rom are you on? maybe its related to euphoria?

i actually have nothing installed expect trickster so i guess its not app related.

and yeah i too know about the min of to cores (used this setting even for msm)

Edit:

On cm12.1 everything seems fine, will try the new euphoria update.

i played a bit around could you try the following: change your governor to interactive, make sure it sticks on boot, reboot.

booting on ondemand solves the problem for me (tried it with 6 reboots)

synapse seems to be euphoria related
[G Pad 8.3 Android Development] Deltadroid:
I just tested r017 with latest cm12.1 nightly and it's working well. Although, I noticed that the sdcard is unmounting when the device is in sleep mode. Ckret fixed this problem in his kernel by reverting to the stock v500 driver. Which sdcard driver does this kernel use?

Regards.
[G Pad 8.3 Android Development] Feed Me:
No unmounts here with the same setup.
[G Pad 8.3 Android Development] Deltadroid:
It seems to only be a problem with specific cards
[G Pad 8.3 Android Development] papa_cadillac:
So if this version now has the "bump" script integrated, does the twrp need to be as well, or can this kernel still be flashed with the ROM per usual and function normally?
[G Pad 8.3 Android Development] nytral:
Hi, I also have sdcard unmounting after a while with latest build that did not occur with r016. It's a 64GB SanDisk.

Thanks for looking into this when you have a chance :)
[G Pad 8.3 Android Development] mekoneko:
twrp has it's own kernel and it can be lokified or bumped, doesn't matter.
[G Pad 8.3 Android Development] Rick Roll:
r018 Released!

Changes:

Bring back msm_hotplug (off by default).

New Conservative governor by [MENTION=3292224]franciscofranco[/MENTION]

Download CM version: https://www.androidfilehost.com/?fid=23991606952593982

Download AOSP version: https://www.androidfilehost.com/?fid=23991606952593981
[G Pad 8.3 Android Development] dirlan2001:
High

I've a question :) Flashing theAOSP LollyPop 5.1.1_r1, I found it carried the 3.4.104 kernel... This kernel only shows up as 3.4.0... What are the differences and can it cause problems ?

TIA

Dirk
[G Pad 8.3 Android Development] mekoneko:
Frankly both kernel versions are ancient. 3.4 is from spring 2012.
[G Pad 8.3 Android Development] dirlan2001:
Yah, if I remember well, it was called 'goldfish' .... And that development is sll using 3.4.x

Cheers,,

Dirk
[G Pad 8.3 Android Development] bokoy:
Sorry for the noob question but... If I'm running the 20d I should use the aosp?

Thanks in advanced
[G Pad 8.3 Android Development] Xup8:
If you are on stock rom i think you can't flash either aosp or cm!
[G Pad 8.3 Android Development] bokoy:
Yep, you are right. I tryed anyway because i was going to flash 5.0.2, gamma got messed and working wrong in general, at least it booted.
[G Pad 8.3 Android Development] Rick Roll:
Changes:

Updated with latest CM sources

Removed dyn_hotplug and intelliplug

New default hotplug driver: msm_mpdecision by [MENTION=4195844]show-p1984[/MENTION]

Built with UBER Toolchain

Download CM version: https://www.androidfilehost.com/?fid=23991606952603380

Download AOSP version: https://www.androidfilehost.com/?fid=23991606952603381
[G Pad 8.3 Android Development] Disrupthor:
Could you do a Stock version?
[G Pad 8.3 Android Development] nytral:
SD-card unmounting itself still an issue with r19 (latest OK was r16). Thanks in advance for fixing it =)
[G Pad 8.3 Android Development] onolox:
Can you put exFat support in the kernel?
[G Pad 8.3 Android Development] Deltadroid:
It seems like r015 is the last build on the lollipop branch and then r016 was rebased against cm12. So, during that rebase with cm12, there was something changed that and is causing these BSOD's. Any clue what it could be, [MENTION=4575133]Rick Roll[/MENTION]? Obviously, the problem is something from the CM12 branch.

This is the changelog
[G Pad 8.3 Android Development] zacharias.maladroit:
Part of the answer is that he used different branches:

https://github.com/victormlourenco/red_kernel_lge_v500/commits/lollipop

http://xdaforums.com/showpost.php?p=58672236&postcount=246

(15)

vs

https://github.com/victormlourenco/red_kernel_lge_v500/commits/lollipop-rebase

http://xdaforums.com/showpost.php?p=59390002&postcount=255

(16)

not entirely sure yet where the exact changes happened

@Rick Roll

obviously is in a position to answer that easier

hopefully we'll know soon what could be the culprit in producing these black screen, "black outs"

Thanks
[G Pad 8.3 Android Development] Rick Roll:
This BSOD only happens on video playback?
[G Pad 8.3 Android Development] Deltadroid:
No, it can happen any time, with just about any application. Although, using vlc seems to trigger it within a few minutes.

Edit: I have not had a bsod when using hardware accelerated video decoding. I think it only happens when using software video decoding. It also happens often when using the news reader.