yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mike1986.:
It is mate, confirmed that GSM zImage is not working with LTE device.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for confirming. I'm making fool of myself having a supposed LTE version in my OP. =(
[Samsung Galaxy Nexus] mike1986.:
Don't worry mate, once LTE kernel source is out the situation will change ;)
[Samsung Galaxy Nexus] DDM123:
Ah good, so I'm not crazy and/or stupid.
[Samsung Galaxy Nexus] franciscofranco:
Not at all mate.

@everyone I'm working with the kernel as we speak, doing some final testing before releasing an update.
[Samsung Galaxy Nexus] hosmsdos:
/system/lib/egl/libGlES_android.so

I cant find this file, I'm on android revo hd gsm
[Samsung Galaxy Nexus] meilstone:
Can someone help me again, with the init.d script for hotplug?

My old Script worked fine. But after the location of the hotplug has changed my script does not work.

BUT ive changed the location of hotplug in my script. But after reboot it changes again to "0".

#!/system/bin/sh

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

This is how mine looks like. Maybe some can show my little mistake? :) The file is located in /system/etc/init.d/ permission are set.

What settings seem to fit good in colour control?

Ilove this kernel. great work btw franco! Always up to date. Feels like heaven after coming from the Moto Milestone ;)
[Samsung Galaxy Nexus] ro_explorer:
Guess what ... mine is also set to 0 even if the set-up on boot was activated with Franco's application. Maybe is a bug in kernel ? ... I have no idea.

By unticking and ticking again the respective check-box, the status is being set to 1 but the value will not stick afer a reboot.

---------- Post added at 05:03 PM ---------- Previous post was at 05:02 PM ----------

As for the color control, check my previous post: http://xdaforums.com/showpost.php?p=21352535&postcount=3365
[Samsung Galaxy Nexus] meilstone:
Well seems like ive change it manually through root explorer to "1". Because ive not purchased francos App, due to lack of a credit card .
[Samsung Galaxy Nexus] Redflea:
NFC is working fine for me on 12...running Winner00's CM9 Kang ROM, CDMA.
[Samsung Galaxy Nexus] Sayan1987:
How did u do that? with root explorer i open the file, but can't edit..

and it's mounted as r/w.
[Samsung Galaxy Nexus] franciscofranco:
Maybe I forgot something on the permissions side. Will check later when Im back home, wasting my time atm on Ikea -.-

Currently thinking about an exportable setting for users to manually change the GPU clock, via sysfs and/or app. Still unsure if this OC works or not so having it exported to the userspace users will have control over it and test at will. Feedback on this?
[Samsung Galaxy Nexus] sluflyer06:
I'd be greatly interested in this so we can do testing on a large scale and see if it does indeed work and get some feedback.
[Samsung Galaxy Nexus] balders27:
Don't know y? But not working on Monaco ir9
[Samsung Galaxy Nexus] Thracks:
ROM issue. Not kernel issue.
[Samsung Galaxy Nexus] skdubg:
will nightly #13 patched to 3.0.17 or kernel version 3.2.1?

thanks
[Samsung Galaxy Nexus] franciscofranco:
3.0.17
[Samsung Galaxy Nexus] cchhat01:
Can you tell me which version of francos kernel your gnex is running along with bootloader/radio (assuming you're still on AOKP Milestone 2).

thanks.

chigs
[Samsung Galaxy Nexus] kara mustafa:
I am using interactive governor and I still have a unlock lag... Can anyone provider a solution of this problem?

Wysłane z mojego Galaxy Nexus za pomocą Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
I have no lag or stutter, so I cant fix something I cannot reproduce.
[Samsung Galaxy Nexus] Stretlow:
The only thing ive noticed is if you turn the screen off on homescreen 1 its always 100% unlocks with no lag.

If you unlock it when you've locked any other homescreen it "sometimes" lags and if youve got an app open and you shut the screen off, then unlock the device it pretty much always has a bit of lag.

I am nothing that even comes close to being experienced so am giving you this information from a novice user view.

Might be helpful... probably not...

Stret
[Samsung Galaxy Nexus] jenicekk:
franciscofranco: is there any way how to calibrate WHITE COLOR on the screen ?

color calibration in your kernel only calibrates dark and other colors, not white...
[Samsung Galaxy Nexus] Redflea:
I can't replicate either of these issues....primary home screen, secondary home screen, app open, all unlock the same for me, no issues....on conservative gov, 700 minimum.
[Samsung Galaxy Nexus] deezid:
Same here ;)

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Puzzlegirl:
Yep, still on Milestone 2, bootloader: KL01, radio: XXKK6, Kernel #12
[Samsung Galaxy Nexus] loudaccord:
Just an idea for your next app: Auto-tuning kernel.

Uses some sort of interactive bench where it tests each frequency... adjusts the voltages automatically and saves them at the end of the bench. Just an idea I had last night and have no idea how to create it lol.
[Samsung Galaxy Nexus] psxsnake:
i means is impossible to download from franco app 8.0.10
[Samsung Galaxy Nexus] Fenvarien:
+1

WEP at my office is no problem, I can connect with r328.
[Samsung Galaxy Nexus] syncopy:
It's not yet supported. Getting there, eventually. Flash the .img file or the zip for now.
[Samsung Galaxy Nexus] Khizar:
oh yeah you cant do that yet.. i thought meant you couldnt restore the img file
[Samsung Galaxy Nexus] wilbur-force:
to clarify i have the paid version and its not accessible through there either ;)
[Samsung Galaxy Nexus] ChazzMatt:
I would question why you are stuck with WEP in multiple places? The only people using WEP nowadays -- infamously cracked for a dozen years now -- are the ignorant and the criminally minded (like dodgy internet cafe owners who steal personal information and re-sell it).

I know people get upset at this topic, but as we pointed out before there are many, many people who are actively seeking out WEP wi-fi signals for malicious purposes -- because they see an easy victim. In this post I gave examples in the news. And these are just a two or three that made the news (were reported).

http://xdaforums.com/showpost.php?p=31722491&postcount=27202
[Samsung Galaxy Nexus] Piemo:
Today first and only crash. I was at uni with a mate playing a simple game (dragon fly) in mute mode. At a moment all the phone studied and started ringing at high volume (dunno why). Had to take out battery faster as I could.. LOL

Is it r328 related?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] syncopy:
There's no way to know.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ReAlives:
n00b question

how to install the img file ?
[Samsung Galaxy Nexus] Roscopcoletrain:
Just flashed 328 myself on Rasbean. Won't connect to our office wifi wep network either. So you're not alone.
[Samsung Galaxy Nexus] SahilC:
Anyone have any idea why my screen on time is this low?

Xylon 006 + Franco 328

I have velis auto brightness on as well.

Mobile data never on, only wifi. Airplane mode for 5 hours in the day.

Any other info needed?
[Samsung Galaxy Nexus] bioan:
Just posting some battery stats. Using rasbean jelly and franco 325. Thank you Franco!
[Samsung Galaxy Nexus] Khizar:
fastboot or put it in the backup folder of the FKU app and restore it
[Samsung Galaxy Nexus] yellowdie:
This is

not

an official statement.

Franco has not confirmed his final decision yet, but just to appease the weeping WEPers: there is a CHANCE (I make no promise) that Boss Man may release two versions of each kernel that comes out from now on. One with stock wifi and one with 3.4 wifi. You would then chose which to install just like you do with 384 vs 512 GPU.

Again: I make no promise (because I can't keep it) and please do not ask for any more info until Franco is set to release it. I'm just saying this so people don't worry about WEP or Tethering issues.

:):D:laugh::good:
[Samsung Galaxy Nexus] mohaimed:
What is your screen on time?
[Samsung Galaxy Nexus] supernova_00:
I wouldn't waste my time doing that. What are they going to do when phones are released with the new drivers? Let them start the *****ing now to get companies to change from using such crap "security".
[Samsung Galaxy Nexus] bioan:
See first photo. It was around 2h 20 min.
[Samsung Galaxy Nexus] CheesieOnion:
I don't see a choice between 384 and 512 GPU I can make.
[Samsung Galaxy Nexus] shawnaye:
I'm quite sure there won't be any more 384 versions.
[Samsung Galaxy Nexus] Phoenix Wright:
WEP is a non-issue, but wifi tethering is a real one:rolleyes:

And these problems only exist because the new drivers haven't been optimized by Google.
[Samsung Galaxy Nexus] RayGarden:
For me.......a Good Batt Life
[Samsung Galaxy Nexus] Invicta:
Why not anymore 384 versions?
[Samsung Galaxy Nexus] alexdemonumber3:
Because 512mhz is now stable and Franco determined it doesn't make too much a difference with battery life.
[Samsung Galaxy Nexus] yellowdie:
The 3.4 drivers are designed to work on the N4 radio, not the GNex radio (two different manufacturers entirely). Therefore the ported drivers we have are not what they are on new devices. So when someone upgrades phones and gets the new drivers, they'll work properly because they're designed for that specific phone. :)
[Samsung Galaxy Nexus] osm0sis:
CRAZY TALK :silly::cyclops::eek::mad::rolleyes::cool: :confused: :cowboy::angel::o;):fingers-crossed::D
[Samsung Galaxy Nexus] Chairizkuro:
NFS Most Wanted FIX

DISCLAIMER: **This is not my work, I just found it, all credits to the Modder (hamdir if i'm not wrong). I'm not responsible for any damage to your device, a nuke falling in on you lap, or missing stars in the sky**

Here We Go. Someone finally did it. Need for Speed Most Wanted Lag Fix. The game runs much better on Franco r328 than any other kernels. Please follow the link below. Install the apk and put the 130000 file at the root of sd card for optimal fps and quality.

Download here: http://bit.ly/U12t6x

Enjoy the game in all its glory! :good:
[Samsung Galaxy Nexus] Un4got10:
wi-fi tethering doesn't work with r328

Galaxy Nexus Maguro yakjuxw (in past)
[Samsung Galaxy Nexus] osm0sis:
Franco has already commented on it. He said he knows (clearly he would, it's mentioned on every page for 50 pages), and that he's hoping to have it working again in an upcoming version. So there is no need for posts like this unless you've got a logcat or something to help out with. ;):good:

That's awesome! People could even use one of the lower speed files like 800000 if they don't feel the performance is good enough with 1300000 :good::D Great find man. I'm sure you just made a lot of people in this thread very happy. :highfive:
[Samsung Galaxy Nexus] Ronaldo Forenucci:
I'm still on r318, but will be flashing r328 after this post. I had some GPS peculiarities this morning, that rebooting seemed to solve. But for future reference, is GPS handled by the kernel or the ROM? (I'm on Rasbean Jelly). Thanks,

RF
[Samsung Galaxy Nexus] Chairizkuro:
Thanks... I was pointing to the same solution earlier in this thread. Well.. someone did it for us... *cheers* :)
[Samsung Galaxy Nexus] Angelakaro:
Does it work only for nfs?
[Samsung Galaxy Nexus] osm0sis:
They hacked the NFS apk to look for a file to tell it what mode to run in, so yeah.
[Samsung Galaxy Nexus] tetrakinitis:
You're my man :eek::eek::D:D:D:D:D

Thanxxxxxxxxxxxxxxxxxxxxxxxxxxx

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] osm0sis:
Yeah everyone go thank him! He did the searching and reading so you don't have to. He might be new but we need more like him around! :):good:
[Samsung Galaxy Nexus] franciscofranco:
Btw 4.2.1 is being pushed to AOSP. I dunno if it only contains the December fix or anything else, but the OTA update its 1,1Mb I think. Just a notice.
[Samsung Galaxy Nexus] osm0sis:
Yeah looking forward to it. Here's what they changed for the N4. Quite a few files getting patched so hopefully fixes for a few things.
[Samsung Galaxy Nexus] haasgo:
Is CRT-Animation ANYHOW (and I am just asking the big man to be sure) related to kernel?

Am asking cause it looks weird to me and is not due to franco kernel, but was introduced from 4.2 upwards which makes me wonder if stock kernel is already kinda whacked....

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
They ****ed it pretty much on 4.2, lags when turning the device on/off.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the file list. I'm compiling a build for me at the moment but I couldn't see what changed, so thanks.
[Samsung Galaxy Nexus] osm0sis:
No it's part of the ROM. And I agree the CRT animation doesn't look as good in 4.2 as it did in 4.1.x and before; it's like they dropped some frames.

OTA URL has already leaked for the N7, so we can't be far behind. Who knows maybe it will fix that too. :D
[Samsung Galaxy Nexus] haasgo:
So I am not alone with this annoying bug. I hate it when ppl only release stuff just for the matter to have released something. I hate to say that google kinda messed up the whole release of the new base and the new devices....:thumbdown:

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] gummie:
I don't believe it. OMG some one actually did this. THANKS!
[Samsung Galaxy Nexus] nuwan32:
I love you man! Getting 60 fps on 384 gpu!
[Samsung Galaxy Nexus] grognaz:
ive been using this kernel for quite some time now and for the last month or so with the same rom (cna 3.8). and i noticed that after some time, a day or so, everything gets really slow and laggy until i reboot the device.

after that the blazing speed is back.

so i was wondering if that could be related to some part of the kernel?

and does anyone else have this issue? and maye possible solutions for it?

sorry if this should have gone in the general or q&a section but i felt heres the right place to ask:eek:
[Samsung Galaxy Nexus] The Gingerbread Man:
Osmosis I have a question, this back up script you say Franco has incorporated for power.tuna.hal.conf (or what ever it was) to make a back of original. Would you mind explaining how it works again? Is the file moved during Franco kernel install automatically so we have to put the backup file into the original location? I'm asking as preparing for OTA and will need to flash back to stock file you posted before the ota hits at some point as the slightly older 4.2 Franco kernels before 328 came about didn't make this back up of original. So what I intending on doing at some point was flash the stock kernel and fast boot boot to custom recovery flash your file then restore 328.IMG and then I should have a back up of this stock file on my system along with my stock kernel to be all set for ota :) should work right?

Sent from my Galaxy Nexus

---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------

I tend to reboot once a day anyway just to clear out the memory and ram and stuff to maintain good performance, doesn't hurt to reboot once in a while :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Alrighty.. The trick of it all is the script is run on every boot. That way it's not tied to install method. What it does is check to see if /system/lib/hw/power.tuna.so.fkbak exists, if it doesn't then it copies the existing power.tuna.so to .fkbak. Then the script copies Franco's modified version in. Of course if you started using f.K on stock 4.2 before r325 then it'll back up the modified one instead and you should flash that zip I posted awhile back; no need to go back to stock kernel when you do this. And yes you'd want to delete the modified one and rename the backup to it's original name to pass any OTA asserts.

All that said though, try flashing the OTA first. I just did on my N7 and it doesn't even check for stock kernel (i.e. no new kernel is included) so I didn't have to revert anything. Might be the same for us. Try it first, then if it fails on power.tuna.so you know what to do. :good: :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Gotcha, thanks :):thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I can confirm that nothing franco.Kernel related needs to be reverted for the JOP40D OTA to flash. :D

Only thing I had to redo after were the permissions of my init.d script. :good:
[Samsung Galaxy Nexus] njiki11:
Nobody kick my ass or report me for asking but does this work on Sprint LTE?
[Samsung Galaxy Nexus] Savant:
Yes it does and it will work perfectly for it.
[Samsung Galaxy Nexus] franciscofranco:
Yes it works just fine, all 3 variants of Tuna share the same kernel ;)
[Samsung Galaxy Nexus] emd2009:
What's the change log for r300
[Samsung Galaxy Nexus] yellowdie:
Increased awesomeness. :):D:laugh::good:
[Samsung Galaxy Nexus] Khrushy:
Franco could just put that as the change log for every release and save himself some time. ^^
[Samsung Galaxy Nexus] garuhhh:
Still on r328, and reporting some reboots. I was able to get the last_kmsg.

cleared fkU data and cache, did not do anything with the voltages, CAB unchecked, and got these two reboots this morning while reading from the browser. here are the last few lines from the 2 last_kmsg:

here are the two files: here and here.

I'm off to work now, and I'll read the last few pages of the thread later.
[Samsung Galaxy Nexus] calibachrome:
Why are the sound control options not available in the f.k. app. I flashed #328

but I see no options to raise the volume, did I miss something?
[Samsung Galaxy Nexus] neo-X:
I believe Franco has removed this option and just raised the volume or is going to.
[Samsung Galaxy Nexus] Phoenix Wright:
they have to be reworked for 4.2:)
[Samsung Galaxy Nexus] calibachrome:
Cool thanks, I'm new to all this stuff... thought I wasn't doing something right.
[Samsung Galaxy Nexus] Darkje:
Anybody tried the 4.2 kernels on CM10.1 nightly (euroskank). What ever kernel i flash of the 4.2 series it keeps stuck at the bootlogo.

Suggestions please
[Samsung Galaxy Nexus] Sik-1:
I haven't gotten it to work with cm either, the zen kernel works tho i think the v8 version, i haven't tried the latest so far!
[Samsung Galaxy Nexus] chickentuna:
It's a known issue. Stay on stock kernel for now

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pipposs2007:
Thanks franco for your work. XD
[Samsung Galaxy Nexus] gianton:
R328 on AOKP 1126 nightly, running rock stable with great battery life.

View attachment 1518567 View attachment 1518571 View attachment 1518574 View attachment 1518575
[Samsung Galaxy Nexus] musashihatred:
how to put the power button on the navigation bar ?:D
[Samsung Galaxy Nexus] chickentuna:
It's rom dependent, in his case he's using AOKP which has the nav bar customizations
[Samsung Galaxy Nexus] gianton:
Exactly.
[Samsung Galaxy Nexus] duduzinho15:
Euroskank ? Can you give me the link?
[Samsung Galaxy Nexus] GrenW:
Look for Roman's dev account on goo.im. Pretty much daily Maguro builds
[Samsung Galaxy Nexus] gianton:
Here mate http://goo.im/devs/roman/aokp_maguro/
[Samsung Galaxy Nexus] gerberman:
Anyone else having issues with color control? I'm setting a certain contrast level and after reboot it appears for s minute or so and then changes back to normal contrast level

Sent from my Paranoid Powered Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
That "blink" is due to the time elapsed between the stock color settings at boot and the time that FKU is granted SU permissions and change the color to your actual setup. Not sure if that's the behavior you are reporting, though.
[Samsung Galaxy Nexus] Khizar:
you still using the same settings? cuz i have been getting slightly bad battery life on all version after r318.. 318 was perfect then battery started getting worse and on r328 its noticeably bad compared to 318.. if you are using different settings would appreciate if you could pm me :good:
[Samsung Galaxy Nexus] Neejay:
1127 now, but same here...no issues.
[Samsung Galaxy Nexus] osm0sis:
Yup. There are two separate noticeable "blinks" for color then contrast, then a "glitch" if you have omap gamma set. I personally have them all set via init.d script so my device is seamless. I also think setting during boot gives different results. The colors are more rich somehow.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
I don't get too involved with battery life tweaking, but I have Battery Widget Reborn? Pro, and it gives you a timer for 1% drain. Usually it's about 20-30 minutes per %. Last night, after flashing r328, I left it off the charger with everything enabled (phone/wifi) and I had a 45 minute per % drain, so that is awesome for me. My N7 on r25 does about 50-75 minutes per %. Don't know how scientific it is, but that's how I judge battery life.

RF
[Samsung Galaxy Nexus] markop90:
Dear franco,

I've been using your kernel for a long time, and it ran always very well. I've also bought your app on play store, very comfortable.

I wanna ask you a fix for a bug present on the newer GNexuses (including mine).

In these "nexuses" there is the SAME bug of the nexus 7 v4.1.1 jelly bean: after filling the internal memory reaching 2gb of free space or less, phone starts to hang a lot, becoming unusable; freeing internal memory is useless. Only flashing factory image solves the problem.

This issue is documented here: http://code.google.com/p/android/issues/detail?id=39154

Since I read that you managed to solve this issue before Google did (activating trim or discard mount option, I don't remember well) , could you prepare a kernel for us? This problem is killing me :(

I'm on Android 4.2.1, and this problem is still present since 4.1 (never tried with ics because when I bought the phone upgrading was my first thing I've done).

Thank you in advance!
[Samsung Galaxy Nexus] osm0sis:
This is about sdcard free space, and was fixed by Google in 4.2. But it can't fix if you already filled it presenting the issue, and neither can Franco. Incidentally there's an app for that. It fills the free space and then removes those files so the trim errors are gone. I'll see if I can dig it up again.
[Samsung Galaxy Nexus] gerberman:
not talking about the blink... i'll try explaining it again...

i boot up - i get the stock color

a few sec later the kernel color management kick in and i get the kernel color

about a minute later i'm back on stock colors and it stays that way
[Samsung Galaxy Nexus] Ronaldo Forenucci:
What does "CAB checked or unchecked?" in the troubleshooting form mean?

RF
[Samsung Galaxy Nexus] markop90:
When I flashed android 4.2 I factory-reset my phone before, and I have cleaned the free space with the tool you said (I don't remember the name), but nothing the bug is still present

EDIT: forever gone is the name of the app
[Samsung Galaxy Nexus] yellowdie:
Whether or not you have "Disable Content Adaptive Brightness" checked or unchecked under the Color Control option. It can cause reboots right when the phone boots up (if you turn it on and don't unlock the phone or touch it at all). It works for some and not for others. It was just for troubleshooting. :)
[Samsung Galaxy Nexus] pmbabu:
Could be one of your apps that are conflicting with Franco's settings. Trickster MOD in the market has an option to set delay for its settings (including color control) allowing other apps to finish first. Not sure if FKU supports such an option.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Thanks, will update my entry.

RF
[Samsung Galaxy Nexus] gerberman:
hmmm i dont have any app that does that other then the Franco updater
[Samsung Galaxy Nexus] osm0sis:
Well I dunno man. That's the bug, and between 4.2 and that tool (thanks for remembering the name for me) it fixed the issue on all the N7s in the Lag thread over there. It wasn't even supposed to be an issue on the GN if I recall correctly. It was just an issue with the N7. So I think you've got another unrelated issue. :(
[Samsung Galaxy Nexus] markop90:
Yes it was an issue present on all N7s, and as what I can see in the newer GNexuses.. I guess they used the same memory chips of N7s and the trim problem is present... Phone lags as hell :(
[Samsung Galaxy Nexus] gianton:
Exact same settings mate. I had bad battery life on most 4.2 ROMs, but AOKP 4.2 is excellent combo both in smoothness and battery life. You should give it a try.