yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pkgnex:
That's REALLY frustrating to hear!

I tried using f.Ku's monitor and CPU Spy+, and still no go on input boost for me.

To try and help trouble shoot / figure out what might be different on my phone, I tried going to the stock settings (700 hsf, 1000 ibf), same story. Tried putting ibf really low (537) and hsf high (1200), same story.

Tried increasing the boost time by a factor of 10 just in case the monitors were missing it (e.g. 5 full seconds!), same story.

Several permutations / combinations of the above, same story.

All three apps show the same thing - no matter how I set the boost frequency or boost duration, the input_boot frequency is virtually never used. In fact, it seems conspicuously like my device is actually AVOIDING the input boost frequency based on my trials since it is the one and only frequency that almost never shows up as being used, no matter what I set it to!

I've tried totally wiping trickster data, re-flashing several times, and everything else I can think of. r395 shows input boost working, r396 does not.

Really weird. I hope Franco's Flo commits make it to G-Nex some time and help this out.
[Samsung Galaxy Nexus] Jar3112:
Wifi tethering is not working for me..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BladeRider:
Mine is working fine. Check your ROM or try to reflash the kernel
[Samsung Galaxy Nexus] CYoung234:
Neither is mine. Fails with an error, and I have to reboot to get WiFi back. CM11 NIGHTLY 5-13-2014 ROM and Franco r396. Here is logcat.
[Samsung Galaxy Nexus] pkgnex:
Neither is mine - and this is the first time this has happened to me.

I'm pretty sure it's NOT this kernel or my ROM, though. I flashed back to r395 and still no tether, and I KNOW r395 and my current ROM worked with tethering a few weeks back.

Maybe the new Play Services update borked something?
[Samsung Galaxy Nexus] CYoung234:
t appears to be the kernel. I dirty flashed back to the CM11-NIGHTLY for 5/13 and tethering is working with the stock kernel. I will load Franco r395 to see if that works or not, and I will post another logcat if no.
[Samsung Galaxy Nexus] EDNYLaw:
Tethering failed for me on a current CM nightly with 396,when I clean flashed back to CM M4 with Franco 396 tethering works perfectly. It's definitely something with CM and not Franco kernel.
[Samsung Galaxy Nexus] pkgnex:
I'm on Shiny, (aosp based) and have never flashed a cm based rom or kernel. So it's NOT just a cm thing.
[Samsung Galaxy Nexus] EDNYLaw:
It must be ROM side. The only changing variable is the ROM, the kernel is static. Must be something in AOSP or some other common source between the ROMs.
[Samsung Galaxy Nexus] CYoung234:
r395 would not work either.Here is a logcat from that.
[Samsung Galaxy Nexus] metalspring:
Am I seeing this right [MENTION=3292224]franciscofranco[/MENTION] , you're getting an m8 to develop on?

https://plus.google.com/106873500108976028532/posts/dfqbmqhSJRb

My m8 purchase is looking better and better :P
[Samsung Galaxy Nexus] pkgnex:
Just flashed Dirty-V, and now tethering works. So to sum up, r395 snd r396 both don't work, but Dirty-V does with same Rom. It can therefore not be solely a Rom issue.
[Samsung Galaxy Nexus] osm0sis:
DirtyV uses the 3.4 Wi-Fi drivers and a custom hostapd required to make tethering work with them. Don't worry though, my DirtyV ramdisk cleans up after itself using init.d and restores the ROM's original files if you flash another kernel. Anyway, my point is you can't really compare the two with respect to Wi-Fi. :)

Try on my f.K fixed version? http://v.ht/osmod
[Samsung Galaxy Nexus] metalspring:
I think cm changed a few things in ramdisk recently so they may, once again, be borking things for everyone else

But on a bright note, I did see this which is nice lol

https://github.com/CyanogenMod/andr...mmit/3300e872b706e180e0967913d8599ac7ee158472

Also maybe this is the cause of the wifi issue?

https://github.com/CyanogenMod/android_vendor_cm/commit/fdf1aff5ad1bc5f22e05d26c301a93c443c36c3c
[Samsung Galaxy Nexus] osm0sis:
Well, just to be totally contrary, I can't get tethering past "Turning hotspot on..." using the latest DirtyV on Carbon 5-16, where pkgnex said it worked for him on Shiny, so there's definitely something weird going on.

I'll see if that IPv6 ramdisk commit fixes it on Dirty and go from there.
[Samsung Galaxy Nexus] metalspring:
see top commit here ;)

https://github.com/CarbonDev/android_vendor_carbon/commits/kk
[Samsung Galaxy Nexus] osm0sis:
Haha yup, I knew they'd added it. Here's hoping it's the fix. ;)

Edit: Nope still broken on Dirty. I'll take this to the Dirty side then, and hopefully pkgnex can still tell me if my f.K fixed version helps at all with f.K on his setup.
[Samsung Galaxy Nexus] DryEagle:
Franco, thanks for the continued work on the kernel.

I have 2 simple questions, and please explain in simple terms:

1. The ondemand governor was recently(ish) added, in which scenarios would it be recommended to use this? I mostly use my phone for watching youtube and twitch streams, as well as web browsing and some 3d games.

2. which tcp algorithm would you recommend? there are about 12 devices using my router, with usual signal strength around -65 or -70db.

Thanks much!
[Samsung Galaxy Nexus] Nuginuk:
edited*

sorry wrong post :(

too many tabs open
[Samsung Galaxy Nexus] etMind:
How should I get this working?

The OTG feature I mean. Tried StickMount but it won't detect although the flash drive LED indicator does blink when I connect it to the phone using a OTG cable.
[Samsung Galaxy Nexus] osm0sis:
Works for me even without stick mount.

It ends up in /storage/usbdisk

---------- Post added at 01:52 AM ---------- Previous post was at 01:50 AM ----------

ondemand is more aggressive than interactive. So things should feel faster at the cost of battery life.

Westwood is the default because Franco found it performed best (see the OPs). Others like cubic (Linux default), and Illinois.
[Samsung Galaxy Nexus] pkgnex:
sh$T. I was out of town all weekend - I'll try your fixed version tomorrow, [MENTION=4544860]osm0sis[/MENTION].
[Samsung Galaxy Nexus] pkgnex:
[MENTION=4544860]osm0sis[/MENTION], The fixed version you posted didn't help my tethering problem.

Here's what I did:

I was on DirtyV-R 5/3 and tethering worked.

For grins, I flashed r395, and tethering didn't work (hung up as you described, as expected).

I then flashed your fixed r396 and tethering still does not work (hangs up at same place).

This probably doesn't help you much, but let me know if you want me to try anything else.
[Samsung Galaxy Nexus] EDNYLaw:
I was having the tethering issue on CM nightlies. However, I flashed the 5/17 nightly with osm0sis's fixed 396 and tethering seems to be working (unrelated but good to know: this nightly also seems to have fix the horrible memory/system ui freeze and crash issue)
[Samsung Galaxy Nexus] Hungry Man:
What ever happened to GPU overclocking/ undervolting? I don't see it in the app on 4.4. IVA and GPU just disappeared at some point.
[Samsung Galaxy Nexus] mangusZen:
Hi [MENTION=1143630]osmosis[/MENTION], I just flashed your last fixed version over fancy, without flash rom first (carbon) and I have this in logs:

05-21 17:25:56.413 E/auditd (22329): Failed on audit_set_pid with error: Protocol not supported

Is this normal? Do I have reflash rom first? I know..im lazy ;p
[Samsung Galaxy Nexus] andronexus:
Idk why but my tethering works with Franco's r396. But since the osmod addresses the system freeze (happens every time I open the Google books app) issue I'll flash that anyways. Thanks in advance, [MENTION=4544860]osm0sis[/MENTION]
[Samsung Galaxy Nexus] osm0sis:
First I've heard of it. Googling it showed it's an error that has popped up for people before. Here's info on what it does: http://linux.die.net/man/3/audit_set_pid

I'm out of town for a couple weeks but I'll see if there's a ramdisk difference that could cause it when I get back. Do you have the issue with the original r396?

Let me know if it still works for you with mine, and what ROM you're on.
[Samsung Galaxy Nexus] andronexus:
It's still working. I've been using it for the past few hours. And btw, I'm using the latest Paranoid Android beta build. Although the system freeze, when I open a book in Google books is still there. I'm not sure if it's kernel related. Might just be the app causing it. Although it was working on the previous kernel version. Still have to keep using it and see if it's isolated to that one app. Everything else is working as it should.
[Samsung Galaxy Nexus] CYoung234:
Here is a bug report. Every time I install franco kernel, all of my paid applications get messed up. I need to uninstall and reinstall them. Here is a screen shot and a logcat.
[Samsung Galaxy Nexus] osm0sis:
Known, researched and fixed: http://v.ht/osmod

Blame CM, per usual.
[Samsung Galaxy Nexus] CYoung234:
Wow. Thanks for the fast response! Downloading now.
[Samsung Galaxy Nexus] osm0sis:
Buddy, I've really got a feeling it's a CM problem since it's working on AOSPA, but I know you're on Shiny which should be completely AOSP... So can you try reflashing your ROM and then flash r396-fixed to see if it works? Trying to rule out some inadvertent system file breakage from using kernels with 3.4 Wi-Fi drivers.
[Samsung Galaxy Nexus] pkgnex:
Yup. May have to wait a day for me to get it done.

Dirty flash ok, or do I need to wipe data and/or system?
[Samsung Galaxy Nexus] osm0sis:
Dirty flash should do it since it should wipe system. Thanks. :)
[Samsung Galaxy Nexus] pkgnex:
OK. Will do and report back.
[Samsung Galaxy Nexus] ashclepdia:
I'm just curious cuz this happened to me month ago on dirty, and I like to know WHY things happened vs just knowing it was fixed lol, but any link to a post with info on this or commit I can view that caused it to happen?

I just never figured out WHY it happened(i was able to reinstall all my paid apps after I went in and deleted them all from /data/app-asec or something like that so it's not an issue for me anymore, like mentioned I'm always curious lol)

tia

EDIT::::

I stopped being lazy and went back few pages and see it was some SElinux ramdisk changes that could have caused it for me back when it happened maybe. :)
[Samsung Galaxy Nexus] marccastle:
I had the dreaded tethering problem and once it started, nothing worked. I flashed kernels, wiped system, dirty flashed Shiny rom, wiped cache, dalvik cache.....Nothing made the tethering work again. Until I uninstalled and deleted Busybox then UN-rooted the phone, and uninstalled SuperSU. Then, in recovery, I dirty flashed the Shiny rom again, rebooted, checked tethering, (it worked) then booted into recovery again, installed R 395 optimized kernel, rebooted, tethering still working, then I flashed SuperSU to root, rebooted...all good, then installed busybox. Everything is good. Don't know which part of what I did fixed the problem, but I suspect that either busybox or being rooted was causing the conflict. Good luck!
[Samsung Galaxy Nexus] LibertyMonger:
I have noticed, and this may not be related to the tethering problem, I don't tether so I wouldn't know but lately when I have dirty flashed I get network data issues and I have to hit airplane mode on and off to get it to work or reboot. When I clean flash I no longer have that issue.
[Samsung Galaxy Nexus] mangusZen:
I got the same with the original 396..

I dont think auditd is running.

I flashed original over yours , do I need to reflash rom first for ramdisk?
[Samsung Galaxy Nexus] pkgnex:
[MENTION=4544860]osm0sis[/MENTION],

Great news - I have wifi-tethering back on franco.kernel!

I first tried just flashing the "return to stock aosp kernel" zip balwinguy77 supplies for his ROM since this has cleared up issues for me in the past. Tethering worked on the stock kernel (that has the 3.0 wifi drivers), so I was hopeful, but when I flashed your r396_fixed tethering still didn't work.

So, I then did a complete dirty flash of the ROM - wiped /cache and dalvik and even did a forced format of /system (but NOT /data) before flashing. Flashed the ROM, SuperSU (stayed with 1.94), and the battery % mod and rebooted. Tethering still worked (still on stock Shiny ROM kernel at this point).

I then checked some normal post-flash things and noticed that the Stericsson Busybox app said busybox was not installed, so I did that (latest stericson). The busybox install was abnormally fast, probably under 2 seconds whereas it usually takes about 20, which I found weird, but tethering still worked.

I then booted into recovery, flashed r396_fixed (no wipes of anything), and after rebooting, tethering now works on r396_fixed.

So, I guess I'm all set. From what I can deduce, my issue must have either been:

Something in /system that was not over-written by flashing the stock kernel but was over-written when dirty flashing the ROM and re-flashing SuperSU.

or

A busybox issue that wasn't causing any other noticeable problems.

Maybe this will help you figure out the specific issue, but regardless I think other (AOSP, maybe not CM) users with tethering problems may be able to get tethering back by re-flashing their ROM and root, re-installing busybox, and then flashing r396_fixed.

---------- Post added at 09:22 AM ---------- Previous post was at 09:05 AM ----------

Just noticed this...

It sounds like the common thread between our methods that solved the issue is a busybox uninstall / reinstall. I did not need to un-root or uninstall SuperSU....
[Samsung Galaxy Nexus] demoncamber:
So while using intelliactive gov, I've noticed that I get random heavy stuttering playback of YouTube. I've been playing around with the gov settings and so far if I bump up the sync frequency once to 1190 it no longer will stutter. Is there anything else I would be better of changing in there that may be the actual cause of this issue?

Sent from my LG-D801
[Samsung Galaxy Nexus] pkgnex:
Pretty sure you're in the wrong thread / forum.
[Samsung Galaxy Nexus] osm0sis:
I just got it working on CM-tree based ROMs as well! The issue is SELinux needs to be set to Permissive so that hostapd/softap can write to its files in /data/misc/wifi; but franco.Kernel sets SELinux to Enforcing by default. :eek:

Can you confirm tethering works with Enforcing on AOSP?

[MENTION=4328678]metalspring[/MENTION] any chance you could recompile your optimized versions with permissive added to the command line then repost here for everyone with my fixed ramdisk? :)

This in an init.d should fix tethering for anyone in the meantime:

su -c setenforce 0
[Samsung Galaxy Nexus] pkgnex:
Tethering is currently working for me, and "su getenforce" returns "Enforcing".

So, as far as I can tell, AOSP ROMs (I'm still on Shiny 4.4.2) allow tethering while SELinux is set to Enforcing.
[Samsung Galaxy Nexus] CYoung234:
I did a full wipe and install of the CarbonROM 5/27 Nightly. Everything works fine until I install Franco kernel, then the FCs start a while after. I am attaching another catlog. Oh, the version of franco (r396 fixed) I am using worked fine up until about the 5/24 Nightly. This is also the fixed version of franco that resolves a couple of issues people were having with it. I am attaching a copy of it as well.

I am posting this both here and on the Carbon ROM forum, along with the logcat and the franco version I was using, which came from Osmosis.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2346499]CYoung234[/MENTION] I'm seeing the auditd issue and it keeps mentioning framework-pac, which it shouldn't. How long does it take to happen? I haven't seen that on mine yet. Since it started on 5-24, I'll see if they (or more likely CM) changed something.

Edit: I see in the Carbon thread you found it was just a ROM thing. :good:
[Samsung Galaxy Nexus] CYoung234:
Yes, sorry, it had to do with that Ubuntu.apk font pack. Very strange, but I am happy that is is sorted out now.
[Samsung Galaxy Nexus] metalspring:
[MENTION=3292224]franciscofranco[/MENTION] [MENTION=4544860]osm0sis[/MENTION]

http://xdaforums.com/showpost.php?p=53059514&postcount=9632

About time? Lol
[Samsung Galaxy Nexus] sunscape:
Optimized and ram speed? :D
[Samsung Galaxy Nexus] hp13:
Anyone has link to 4.2.2 franco kernel ? OPs directory has no file.
[Samsung Galaxy Nexus] lollipop:
this is the last version with fixed ramdisk by osm0sis

http://d-h.st/fap
[Samsung Galaxy Nexus] CrotaNexus:
Hi guys, someone know where is situated the kernel file that contains list of avaiable GPU governors? Thanks in advance.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
CPU? cat the scaling_governor file: http://xdaforums.com/showpost.php?p=34977868

If you did mean GPU, this device has 2 GPU frequencies so there's no GPU governor in stock/most forks, and sort of pointless to add one.
[Samsung Galaxy Nexus] pattyboi:):
deleted
[Samsung Galaxy Nexus] aliesz:
Does the r396 kernel for 4.4 support 1080p videos?
[Samsung Galaxy Nexus] pianistaPL:
Yes.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4328678]metalspring[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=2838735]aosp[/MENTION] [MENTION=3685904]ak[/MENTION] [MENTION=5658634]apb_axel[/MENTION]

/Users/Chris/Desktop/android-todo.txt:

[strike]- update fK-tuna with mpok commits, etc.[/strike]
- email [MENTION=3292224]franciscofranco[/MENTION] again re: updates
- fix DirtyV metaltest Synapse
- add DirtyV ramdisk files to f2fs-test2
- create unified DirtyV ramdisk for f2fs and ext4
- update DirtyV AnyKernel2 with unified ramdisk files
- rewrite ADB Screenshot for v2.0
- sync mkbootimg patches and add board support to unpackbootimg
- finish AIK v1.9, AIK-mobile + AIK-Linux v1.3
- update AnyKernel2 with board support
- test Moto X + HTC One M8 GPe 4.4.3 optimized Dalvik on N7 '13
- test OnePlus One 4.4.3 optimized Bionic/Dalvik on N7 '13
- find original download of new Adreno Beta drivers and test on N7 '13
- vet [MENTION=2777334]TKruzze[/MENTION]'s PA GApps GPs zip and test out signing + zipfixers
- test Xperia Z Ultra + One M7 4.4.3 NFC files on GN
- fix MX Box ramdisk root remains rw
- tweak MX Box I/O scheduler
- force MX Box Dalvik to /cache by default (with disabling)
- add Synapse support to MX Box ramdisk
- benchmark MX Box with + without EGL hack
- add GFS, SELinux, build.prop tweaks, ?new UKM stuff, ?plasma-a5 stuff to DirtyV Synapse
- update AIK Loki add-on with official unlok binary and full repack support
- research weird Galaxy Tab 4 image issues with AIK
- update local Android files
- examine Wallet APK for replaceable methods to allow all options outside the US
- check N7 '13 touchscreen for loose connector
- test N7 '13 boot-ts firmwares to fix ungrounded touches
- look into writing "Flashify" Script zip for recovery
- investigate addon.d script breakage in Carbon 05-31+
- remove workaround in DirtyV Unified ramdisk+AnyKernel2 with updated busybox

https://github.com/franciscofranco/Tuna_JB_pre1/commits/nightlies-4.3

...1 down... :p ;)
[Samsung Galaxy Nexus] metalspring:
You might want the full history of the ram speed commits though (there are only 2 other commits)-

https://github.com/metalspring/DirtyV_tuna/commit/c2de87aaa60b109b84b4336f70160fb049d164fe

https://github.com/metalspring/DirtyV_tuna/commit/89181e3b5fafc97709aabc9b29d204a15cf0bb0c

Also, you left out adding f2fs support to franco kernel :P (Franco himself will probably have to look into it since they rely upon other commits to build).

Btw, once I pull in your latest updates I should have a new optimized fk build out, I already added the mpok commits myself lol
[Samsung Galaxy Nexus] osm0sis:
The OFFSET_MASK one was already squashed in I think, and the other one is entirely superseded by mpok's so I'll skip it. :)

Awesome man, looking forward to it. Thanks! My poor laptop was the only thing I would have been able to set up building on and it died before Christmas. :o

Edit: No wait, you were right about the OFFSET_MASK one, even though the way I resolved mpok's it added it in too. Hmm.. I think I'd have to rebase to add it in, right? Ughh.. I'll try to add it in tomorrow. Oh well, at least I cherry-pick everything correctly. :p
[Samsung Galaxy Nexus] rajputrajat:
Thanks bro, for keeping on the momentum of so many awesome projects..
[Samsung Galaxy Nexus] osm0sis:
Just force-pushed with that history intact (I decided the comments at least were valuable since they were clearly where mpok got the idea). Thanks for catching that! :good: :)
[Samsung Galaxy Nexus] angourakis:
[MENTION=4544860]osm0sis[/MENTION], can you share the new kernel with the improvements? =)
[Samsung Galaxy Nexus] osm0sis:
Be patient, and please read next time. [MENTION=4328678]metalspring[/MENTION] only has so much free time and he's kindly volunteered to compile these test versions for us. :)
[Samsung Galaxy Nexus] metalspring:
Only one test version right now (and already done), but I cant even test since I'm on f2fs and I couldnt get f2fs support working :(

osm0sis will have to be the tester I guess lol
[Samsung Galaxy Nexus] angourakis:
[MENTION=4544860]osm0sis[/MENTION] I didn't mean to rush or anything else, so sorry! Just getting used to my new life in Toronto so no time to read through the pages >< college is consuming a lot of time =P

[MENTION=4328678]metalspring[/MENTION] take ur time man! Meanwhile I'm sending good vibrations to you guys, you rock! I'm currently using the latest version of SmittyV + Vanir ROM (fixed version) on F2FS so if you need any test, that I will be able to help!

Regards
[Samsung Galaxy Nexus] metalspring:
Adding f2fs to franco is beyond me lol, it has dependencies franco doesnt have (it errors when building) and I dont know what they are :(
[Samsung Galaxy Nexus] pattyboi:):
is it that req thing again like in askp? if so i found the commit we need
[Samsung Galaxy Nexus] CakraMas:
I don't know why my boot animation still in the previous one, not change to the franco's boot animation.

I'm using the latest bigxie's ROM.
[Samsung Galaxy Nexus] Cutting-TM:
Do you mean the message that your mailbox number isn't set ?
[Samsung Galaxy Nexus] minipaolo:
Is there any way to check if hotplug is actually working?

I don't see any difference :(
[Samsung Galaxy Nexus] jhericurls:
My voicemail has been switch off, so my calls can't go to voicemail.

But I'm getting voicemail notifications and I know I don't have any voicemails.
[Samsung Galaxy Nexus] wilbur-force:
Ive flashed this over the Bigxie Apex ROM and Im still getting the Apex Bootanimation.

Anyone got a link to the bootanimation as a separate item for pushing across ?
[Samsung Galaxy Nexus] jsuresh:
franco, 14.3 bought back the nighmares of 14 .. when the screen is off, data connection is completely lost...pls fix this. this is killing.

for the moment, back to 14.2
[Samsung Galaxy Nexus] sishgupta:
This is pretty slick.

Do you think you could make an inverted one? White on Black?
[Samsung Galaxy Nexus] aimetti:
the heck!

I am on aokp build 20.

Was fine on 13.1 , 14/14.1 i had signal drop when screen turns off for a bit , 14.2 was perfect. Now on 14.3 its again giving me signal drop when screen is off .

Anyone else having this?

Im bout ready to format everything and reflash it all.
[Samsung Galaxy Nexus] jhericurls:
So, why don't you flash it back to 14.2?

Newer doesn't always mean better.
[Samsung Galaxy Nexus] Nebucatnetzer:
You already have the bootanimation. Extract the kernel zip. It's in one of the folders either system/media or data/local.
[Samsung Galaxy Nexus] Nebucatnetzer:
This would be really cool. Is this possible?
[Samsung Galaxy Nexus] MultiCulti:
thanks again ... even if i had NO issues, neither with 14.1 nor with 14.2 :thumbup:

but i also still have my bootanimation, so not yours after flashing 14.3

beamed in through my brain ...
[Samsung Galaxy Nexus] Mondfahrer:
14.3 is working just fine on my GN now without any bootlops :p

After setting min. freq. to 700, there is no signal issue anymore, hope it have no impact on battery drain.

Which governor is recommended?
[Samsung Galaxy Nexus] aimetti:
Well I could do that but many others are on aokp with no issues so it has to be something with mine.