yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
*cricket*

*cricket*

How has there been five hours of silence with no posts.... :eek: Weird.
[Samsung Galaxy Nexus] RoscoeDpG:
i was thinking the same thing.......but maybe the silence will be fallowed by something great :fingers-crossed:
[Samsung Galaxy Nexus] Misledz:
Hey franco, been a loyal user to your kernel and I think you're doing a great job aswell as everyone on optimizing interactive and everything to your need, I stopped using the kernel past 27x only because I've been looking for a kernel with cfq I/O I know it sounds ridiculous but CFQ is amazing when it comes to typing/texting and I feel no typing lag of any sorts. I don't know if anyone else tends to use their smartphone religiously but I get about 420+ texts in a day and I tend to type back at 52WPM (thanks to SwiftKey) the only problem occurs with certain IO being unable to keep up with my speed.

I've paid for both Trinity and Franco toolboxes since I believe both are doing a fine job, but I felt a little down when I had to make the change to Trinity just for CFQ. If you could include CFQ as one of your liable IO Schedulers I would highly appreciate it :)
[Samsung Galaxy Nexus] irminsul:
Hey. Ivjust flashed r298 and I'm getting some really strange wifi drain while asleep. It drained from +- 70% to 20% in 9 hours, so the same was yesterday. While at work I don't get any heavy drain, it seems to be a poor connection (for as long as you can trust 'how many bars').

I used to run kernels I based on thalamus source, so close to stock. My phone drained only 5 per cent overnight so it must be something in the kernel. Is there anything changed to wifi in any latest nightlies that could change the reception ? I'm in love with the smoothness and non-wifi drain of this kernel.

I've checked up any rogue apps (sleeping as supposed) and I'm on the latest BuglessBeast.
[Samsung Galaxy Nexus] derPianist:
Hey guys.

Does the Kernel hast something to do with the Hardware Buttons?

For example when you cant do Screenshots anymore could it be kernel related?

via Google Galaxy Nexus
[Samsung Galaxy Nexus] aimcr7:
It should be rom related, not kernel
[Samsung Galaxy Nexus] usmankh10:
i have faced similiar kind of issue as my battery reach 20% it drains within few minutes even if phone is idle

Another issue wen i restart my phone pull out battery nd put it back ,when device boot up there is a sudden drop in battery % ,today i restarted nd my battery fell from 31% to 9% :/

i m using CA 3.8 with r298 nightly
[Samsung Galaxy Nexus] Fenvarien:
I'm silent because of the pure awesomeness of this kernel! No issues at all, ultra smooth and fantastic battery life thanks to Franco's kernel sorcery :)

GNex with franco.Kernel r298/ MiNCO ROM v5
[Samsung Galaxy Nexus] Hans QC:
Same problem here. I got a new 3800mah battery for 15€ recently and I thought it was the cheap battery playing up. Are you using stock battery?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] gt-kingz:
Dunno what ya all have. I never had better battery since r298.

I reach ~ 10 hours screen on time. ( see attachment) while chatting + surfing via Hspa, msg'ing and calling.

I use dyninteractive.
[Samsung Galaxy Nexus] johno86:
10 hours of on-screen time on what battery?
[Samsung Galaxy Nexus] gt-kingz:
Stock battery using cm10.
[Samsung Galaxy Nexus] johno86:
LOL. Okay.

Moving along...
[Samsung Galaxy Nexus] amf100:
While on the charger... lol
[Samsung Galaxy Nexus] derPianist:
I also posted two month ago a Screenshots with 10h 40m screen on while reading e books on black background with lowest brightness, airplane mode, everything Turned off and lowest possible CPU clock.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] obsanity:
Large drop in battery percentage is always a result of corrupted battery statistics file.

Reboot into recovery and wipe battery stats. It should come back to where it was.
[Samsung Galaxy Nexus] goabunny:
I am with CNA rom latest version and wanted to use francos kernel and bought the app from play store as well. I like the kernel in every aspect but the call volume. I tried to change the sound settings in the app but no help. I am not able to use the phone for calls without using wired headset. Volume is really low without headset and as well as Bluetooth headset.

Any suggestions or tips to increase the call volume through the phone headset and or Bluetooth would be greatly appreciated.
[Samsung Galaxy Nexus] b1337:
Lol another one of you eh let's see all your screen shots bosss...
[Samsung Galaxy Nexus] osm0sis:
Nothing has changed for wifi in r29x so I'm not sure what could be going wrong on your end... do you have large wlan_rx_wake locks? I used to and there was no app I could trace them to, so I worked around it by changing the wifi policy to off when sleeping and it got my sleep stat back up over 90% and my idle drain under 1.0%.

Oddly enough that wakelock went away when I converted to takju. Possibly a system app gone rogue is the only thing I can think of since all my user apps and everything are exactly the same (restored via TiBU), so it must have been the data clearing on the system apps.
[Samsung Galaxy Nexus] franciscofranco:
Does that low call volume happen with other kernels? I have no issues with call volume, its pretty high on mine.
[Samsung Galaxy Nexus] ksancho442:
We all may be grown ups (but that doesn't mean we don't get into trouble) I suggest you implement a failsafe (perhaps similar to SetCPU) in the form of a revovery flashable zip that disables the set on boot state of the franco.kernal app. (unless of course you have already tought of this or some better failsafe method... Either way thanks for your hard work and dedication)
[Samsung Galaxy Nexus] shawnaye:
+1, I MYSELF, would really need something like this. haha.
[Samsung Galaxy Nexus] osm0sis:
Yep very good idea.
[Samsung Galaxy Nexus] irminsul:
No strange wakelocks at all, so I thought it maybe was bad reception, just when you're in a bad covered cell region.

I flashed milestone 6, will check if the drain still persists.
[Samsung Galaxy Nexus] goabunny:
I tried faux and the volume is good. I tried trinity, Franco and faux. Faux it better at call volume but not the battery compared to Franco. So I am trying to get some help improving the cakk volume so that I can keep the Franco.
[Samsung Galaxy Nexus] drose6102:
Yes am sure it works. I just verified on both Nexi. I do have the paid version, not sure if that makes a difference or not but it does boost the speaker volume. I am running sourcery 2.2 on the galaxy and Bugless beast on the 7. Latest Franco 298 and build r22 on the 7.
[Samsung Galaxy Nexus] franciscofranco:
Thats true, **** happens, happened with me yesterday, set the wrong voltages, forgot it was with set on boot and boom :) I'll add a flashable zip (downloadable from the app) that wipes the app's data in case something wrong happens.
[Samsung Galaxy Nexus] scarmon25:
One thing I'm noticing. In the Franco app it shows my CPU temp always above 100°F even when the phone is idle and cold to the touch. Possible issue in app? maybe temp reporting?

Edit. So I checked with a temp app from the market. When it showed 107°F the Franco app showed 135°F. So maybe the app just isn't reporting correctly. Nothing huge just something I noticed
[Samsung Galaxy Nexus] Jeffu:
Hi Franco,

Thanks for the work you do; happy customer of your kernel updater. :)

I'm not sure if this is related to your kernel or not but I thought I'd ask.

I'm on a Galaxy Nexus, 4.1.2, rooted. Let me know if I need more details (might have to explain how heh).

Yesterday I tried flashing this http://xdaforums.com/showthread.php?t=1969488 and found it did not work, gallery would force close etc., so I fastbooted the 4.1.2 system.img I had previously, which seemed to fix things.

For some reason suddenly my screen went very green. Eventually I was able to fix it by discovering that the RGB Gamma Green slider in your kernel updater was all the way to the right, and slided it back to the middle. It was fixed, I thought.

However I've noticed now that when my screen starts to automatically dim (after not touching it for a bit of time), it goes green again. Touching it to 'wake' the screen causes it to go back to normal.

Do you have any suggestions?
[Samsung Galaxy Nexus] morfic:
100°F is only 37.8°C

Most apps in market show only the (mostly lower) battery temp.

135°F are 57.2°C a normal CPU temperature after some use.

Stock kernel reaches 65°C far quicker than Francisco's will.

Seems all is working normal.
[Samsung Galaxy Nexus] ajm786:
I figured out what was causing this.

franco, yellowdie, or osm0sis, your input would be greatly appreciated.

So last night, I switched to 298 to try and find out the problem. Here's what i did.

1. Force stopped the franco app, and cleared the data completely.

2. Manually flashed 298 (with the zip in CWM).

3. Upon restarting, high pitched sound was still there.

4. Downgraded to 290. High pitched sound was now present!!!

5. Found that the option in the app "Turn high performance sound - headphones only" was unchecked. Rechecked it and the high pitch sound went away!

6. To confirm, when that option is checked, there is no high pitched background sound. When unchecked, the sound comes back.

I remember in 292 franco said that he took the option away and made high_performance enabled by default. Well, it looks like in my case, that is not happening.

One of the things I tried doing to mitigate this was making the headphone output sound 0, but then the sound is too low.

Can you guys help me figure out what's causing this? If anything, can you at least show me where the high_performance parameter is so that I can see if the switch is actually on or off?

Thanks, and I look forward to hearing from you!
[Samsung Galaxy Nexus] osm0sis:
Interesting! And very good work troubleshooting. We need more people willing to read, learn, tinker and figure **** out like you on the forums here. :)

The commands you're looking for is in the 2nd post of the thread:

Since highperf is enabled by default though, it might not be changable via sysfs, ie. might be overridden by franco somewhere outside of userspace, but it's worth a shot.

To find the current setting you can cat those locations, ie. cat /sys/devices/virtual/misc/soundcontrol/highperf_enabled
[Samsung Galaxy Nexus] ajm786:
Thanks so much for responding!

I'm assuming I would run these commands in Terminal? I have that installed with CM10.
[Samsung Galaxy Nexus] osm0sis:
You got it. Highperf is the one you're concerned with, I just put both sound ones in case.

You can cat them from the user prompt ($) but you'll need to type "su" to do the echoes from the root prompt (#). :good:
[Samsung Galaxy Nexus] ajm786:
Yep, did exactly that!

I will try it right now and let you know how it goes!

---------- Post added at 12:33 PM ---------- Previous post was at 12:24 PM ----------

Ok, when I run the command, I get the following error:

"can't create /sys/devices/virtual/misc/soundcontrol/highperf_enabled: No such file or directory".
[Samsung Galaxy Nexus] sk8oldschool74:
For all the glitcherz out there before complaining try this... I noticed after several tests on my device if I have lag if I reinstall kernel and instead of playing w/ it if I let it set for at least 10 minutes first and let it settle the lag gone... just what I have noticed you can try couldn't hurt may save you from a complaint not needed...
[Samsung Galaxy Nexus] osm0sis:
You're right. Franco must have completely removed the userspace sysfs interface for it since he force enabled it. Sorry, guess we'll have to wait for the next version to see if it's toggleable again.

Yup, never base your observations off immediately after a boot. There are always things happening in the background for a little while that need to settle down, just as with any OS. ;)
[Samsung Galaxy Nexus] TinyFeather:
Why isn't this kernel compiled with linaro?

Can someone explain me?!
[Samsung Galaxy Nexus] ajm786:
osm0sis, when I run the command, I get the following error:

"can't create /sys/devices/virtual/misc/soundcontrol/highperf_enabled: No such file or directory".
[Samsung Galaxy Nexus] gautam_nexus:
Because as per Franco it's not worthy
[Samsung Galaxy Nexus] franciscofranco:
Whats your current Color settings?

Hmm.. current kernel has the default high_performance mode like it comes on stock kernel. I removed the option to change it because it caused some issues. Do you confirm that pitch sound happens with r298?

Because its useless. Its compiled with Google's 4.6.2 toolchain, thats what they use for compiling stock kernels.
[Samsung Galaxy Nexus] ajm786:
Franco, yes, I confirm that it happens with r298. Basically, it's the exact same high pitched sound as r290 with high_performance set to OFF.
[Samsung Galaxy Nexus] Leegalaxy:
I love how everyone freaked out about the Linario toolchain when it came out and demanded that their kernel devs start compiling with it. That lasted about a week if I remember correctly.

I remember it being worse. If it ain't broken...
[Samsung Galaxy Nexus] franciscofranco:
Did that happen with any kernel pre-290?

Yep. People get all crazy when they see someone showing crazy high bench numbers, but it was mostly unrelated to kernel stuff.
[Samsung Galaxy Nexus] ThunderWolf78:
This might be the wrong thread to post this but I just flashed r298-384 on my Gnex and the thing is flying high like never before! Aws00m work Franco! :D

Tapatalked from my h4x0r3d up Maguro.
[Samsung Galaxy Nexus] luculuc:
What are your values? Is it ok to use set cpu along with francokernel?
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco I was reading up on audio stuff in the nexus 4 forum and came across this by ctenorman and I was wondering if making this could help and if you did something with this kernel related if it stick on boot?

Full post from here http://xdaforums.com/showthread.php?t=1962872

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ajm786:
No. Just starting with 292 and after (which is when you made the change to the high_perf code/option). I've been on 290 since.
[Samsung Galaxy Nexus] osm0sis:
I think franco wanted to know if you still got the high pitch noise when it's disabled on pre-r290, since that's the real issue.
[Samsung Galaxy Nexus] ajm786:
Oh! Sorry about that.

Yes, when high_perf is DISABLED, you get the high pitched noise. Now, the noise is not high pitched in the sense that it breaks your ear drum, it's high pitched background noise, like electronic oscillation noise. It's very discernible when switching back and forth between the modes (high_perf on and off).
[Samsung Galaxy Nexus] osm0sis:
Okay. And can you find a previous build where that isn't the case? Try r277.
[Samsung Galaxy Nexus] ajm786:
That's going to be hard because there are simply so many nightlies. :laugh:

I'll try 277 and let you know.
[Samsung Galaxy Nexus] Jeffu:
Color Multipliers:

200

199

195

RGB Gamma

-1

-1

7

Content Adaptive Brightness - Off/Not checked.

Trinity Contrast

-2

Omap4 Gamma

1.0

Installed kernel, if it helps:

3.0.49-franko.Kernel-nightly-384GPU, #298

Thanks in advance. :)

EDIT: Okay, I decided to try uninstalling your app and discovered that the issue was gone. I reinstalled the app, and it seems to be gone. Not sure what happened. Either way, thanks for your work. :)
[Samsung Galaxy Nexus] osm0sis:
It's because of your RGB Gammas. Green has a bug where it can't go below 0. The only thing that makes it possible is jacking up your Trinity Contrast, which is probably why you were able to but ran into inconsistencies. Keep Green gamma at 0 and you should be fine going forward. :)

Oh and CAB is actually enabled when its unchecked, you'll notice the option is named "Disable CAB". ;)
[Samsung Galaxy Nexus] Crwolv:
he is totally write an awesome exclamation can't wait for the green to be fixed, kudos man thanks for the help

---------- Post added at 06:08 PM ---------- Previous post was at 05:49 PM ----------

I tried to thank everyone for helping with the sound issue with jelly bean on the Nexus which is a problem everyone has but I'm only allowed aight thanks today which sucks, so thank you everyone ! :) nothing has worked though lol
[Samsung Galaxy Nexus] The Gingerbread Man:
To quote myself here, after trying this listening to The Prodigy 'Lost Beats' (mini 4 track album) sound quality I'd say definatley seems improved listening through headphones, also used DSP manager (from minco mods thread by Vomer) and used recommended settings by who ever I quoted

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] whitedragonz83:
It feels like input boost freq doesn't keep the CPU at that value long. Is there a setting for how long it stays at that speed?
[Samsung Galaxy Nexus] AutomaticFailure27:
You can use setcpu along with franco, just don't set the governors/cpu stuff in franco. Or if just make sure they match
[Samsung Galaxy Nexus] nardone24:
Def gonna have to check this kernel out. Thanx man
[Samsung Galaxy Nexus] ajm786:
Ok, I tried a few random nightlies. r268, r277, and r290. All of them do the same thing: high pitched background noise when high performance is disabled (unchecked), and almost no noise (just slight hiss) when high performance is enabled (checked) in the app.

Flashing to r292+, the option disappears in the app, and the same background noise that can be heard when high_perf is disabled is present.
[Samsung Galaxy Nexus] osm0sis:
Alright and do you have the high pitch noise with stock kernel?
[Samsung Galaxy Nexus] ajm786:
My honest answer? I don't know...the first day in May that I had this phone, I immediately rooted it and put franco kernel on it. :D

I'm scared now to put the stock kernel, because I don't know what it may do to my phone. I've heard horror stories of people putting the stock kernel on and it messing up their phone.
[Samsung Galaxy Nexus] Dr Byte:
FWIW, my first sortie into UV land with my GN...

Freq Default SRcalib LowestStable
192 1000 830 750
384 1025 830 750
537 900 850 800
729 1150 970 900
1036 1225 1090 1000
1228 1250 1250 1250

384-729 Wheatley, Scr.Off=537

I usually run at 384-1036, and do not expect any dramatic change, given that it is already hard to measure the actual drain reliably :) Differences may show up on the 5-50 hour timeframe though.

There was an occasional 'glitch' when changing frequency ranges; voltages that had 'worked' before froze/crashed the phone as I was shifting from one narrow frequency range to another... the only consistent feature was that there was a large difference in the low-high freq and corresponding voltage, suggesting a 'settling' issue... so I added 25mV to compensate. Which seems to work.

One final observation: if the voltages were marginal, toggling 'disable MPU Smartreflex' twice would usually precipitate a hang/crash.

I didn't bother with the high frequencies; 1228MHz doesn't undervolt on my phone, and I rarely use it anyway - and never above.
[Samsung Galaxy Nexus] velis74:
@Francisco: A bit of a developer question: is it possible to "browse" through all /sys/... paths such as /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq so that one could attempt to find the path he wants?

In my case, I'd like to get to my light sensor path so that I could read its current reading. I'm already doing that through standard Android sensor interface, but I also need this method for an experiment or two :)
[Samsung Galaxy Nexus] nuwan32:
Try increasing go highspeed load
[Samsung Galaxy Nexus] Schneewitzchen:
See the post of yellow above! I think he has made a great summary to all values for governor control!
[Samsung Galaxy Nexus] akash3656:
If you use a rom like Rasbean, it comes with completely stock aosp kernel. I believe the EOS roms are the same too.
[Samsung Galaxy Nexus] despard:
Hi Francisco,your kernel r298 has been treating me well since it was released, but I just got a reboot out of nowhere.

http://db.tt/KxwgQDww

Thanks mate.
[Samsung Galaxy Nexus] osm0sis:
Nonsense. I did it last week to test something, it should never cause any problems. Just extract the boot.img from the latest Google factory image and put it in /sdcard/kernel_backups/ then use Franco's app to restore to it; after just use the app's downloader to go back to his latest. Easy as pie.

Also, you're telling me you've had that high pitched noise since May?
[Samsung Galaxy Nexus] rommel500:
Do you have to upgrade your bootloader to run this Kernal?
[Samsung Galaxy Nexus] inffy:
No but it is recommended byvgoogle for 4.0.3 based roms.
[Samsung Galaxy Nexus] EddyOS:
Where's this nightly #12 then? ;)
[Samsung Galaxy Nexus] inffy:
Not released to public yet.
[Samsung Galaxy Nexus] EddyOS:
Gathered that, just wondering when it's out...hence the ;)
[Samsung Galaxy Nexus] phone_user:
Please continue developing Nexus S franco.Kernel. We miss you more than you know.

from Nexus S users
[Samsung Galaxy Nexus] rommel500:
So currently I am running bootloader Primekk15 and I am running the CM9 Kang without any noticeable issues. What version of the bootloader should I be running for this Kernal?
[Samsung Galaxy Nexus] franciscofranco:
I am, just not good enough for public release yet ;)
[Samsung Galaxy Nexus] luffyp:
PRIMEKL01. You can find it here.
[Samsung Galaxy Nexus] Elganja:
will this wipe your phone?
[Samsung Galaxy Nexus] EddyOS:
No as it doesn't touch your data
[Samsung Galaxy Nexus] Elganja:
so just apply and none the worse in terms of my current rom and kernel?

sorry for the noobish posts, i just want to confirm
[Samsung Galaxy Nexus] phone_user:
Thanks, great dev :)
[Samsung Galaxy Nexus] PeterGuru:
Does Hotplug Enabler affect Wifi?

I had an issue a few days ago with an app called PhoneWeaver, which can be set-up to change profiles. Certain profiles, for example, have Wifi on, while others don't (all established by me through the app).

Here's the problem ...

As I said, this happened a few days ago, but hasn't happened since I disabled the Hotplug Enabler.

I have one profile I use for work, where Wifi is ON. Then, if I move far enough away from my Wifi signal to cause a disconnect, such as when leaving the office to drive home, the profile changes to one called CAR. My CAR profile has Wifi turned off.

The other day, when I was at work, everything was working well. I have my PhoneWeaver app set-up to make a sound when a profile changes. However, I was continually getting the "Profile Change" sound every minute or so. I thought, hmm, perhaps the Wifi signal is lost and it thinks I've left the office, but that wasn't the case. I thought that maybe when cpu1 is shutdown every time the phone goes to sleep, it disables Wifi, so that when I wake up the phone, Wifi is re-enabled and PhoneWeaver once again thinks I'm at work.

Question: Does using Hotplug Enabler shutdown Wifi when the phone's asleep?

NOTE: I already have Settings/Wifi/Advanced to ALWAYS Keep Wifi on during sleep.

Any ideas?

Thanks,

Peter
[Samsung Galaxy Nexus] rommel500:
Do you just flash through CWM?
[Samsung Galaxy Nexus] drtrmiller:
Lightflow seems to respond differently when it's a foreground app (default) as opposed to a background one. Since I unchecked the foreground app box AND reset the device, my phone finally goes into deep sleep, all the wakelocks from lightflow cease, and lightflow still functions normally.

I am using latitude.

Google plus probably instantly uploaded pics taken on the camera while the screen was off. This shouldn't have taken but a minute.
[Samsung Galaxy Nexus] spovat:
edited (ignore)
[Samsung Galaxy Nexus] droopy8424:
I have tried to use a USB Jig that i made to get past the screen in the image attached but it doesn't work. Does anyone know what to do?
[Samsung Galaxy Nexus] rommel500:
I just flashed per the instructions on the page, loaded just fine. Thank you for the help!
[Samsung Galaxy Nexus] mfish123:
Light flow is an app, right? It's different than just having pulse led notification enabled in android system settings correct?
[Samsung Galaxy Nexus] Hans QC:
Still laggy

My GNex is still very laggy. I found lots of 'PVR: ShrinkPagePool' messages in dmesg. The ShrinkPagePool function seems to be located in the GPU driver, so I'm back on 384 to see if this helps.