yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bradm23:
Franco,

I am very curious to ask this semi person question. You are a master of what you do and with all of your knowledge that you have it amazes me what you are not working for Google or another phone brand helping these phone. Have you even looked into getting a job with any of these companies? I am not sure what you currently do for work/income, however imagine if a stock phone came with a Franco kernel? You take what they release and make it wayyy better.
[Samsung Galaxy Nexus] nic85:
Can you fix memory app issue?

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] MarcLandis:
I am just doing a wild guess here but maybe this issue has something to do with the changes on the ramdisk?

Marc
[Samsung Galaxy Nexus] franciscofranco:
That's an interesting question. I'm about to be 22years old next month and I decided to go all out for Android. Samsung is very near to my home, about 10m on car and I'm planning to go there in the near future trying to get an internship. I've been writing articles about Android and the kernel for the best TI news website in Portugal, and they were able to grand me an invitation to give a conference for a pHD class about the Android Kernel last December, which was awesome. I talked a lot about the Galaxy Nexus, what I was doing, about other developers (Ezekeel for example), about how to kernel works, pieces of code that I created etc etc. Future seems bright and my family and my girlfriend are being supportive, which is awesome too =)
[Samsung Galaxy Nexus] ChosSimbaOne:
No thank YOU :-) Keep up the good work, this kernel is great!
[Samsung Galaxy Nexus] franciscofranco:
Fix what? You know Android is built to use all the available RAM?...
[Samsung Galaxy Nexus] rascarlo:
This is very good to know. I wish you all the best. And it's very important that you are having your family supporting you.

Hat off
[Samsung Galaxy Nexus] Felixpau86:
Congrats! Future looks bright for you
[Samsung Galaxy Nexus] nicandris:
https://plus.google.com/100317092290545434762/posts/dYSvAXyuDRL
[Samsung Galaxy Nexus] steve664npc:
Just catching up on the days threads and see you are apologising??? Jeez man you are one committed guy. I hate to think how many hours you've put in to this problem and I don't think it is appreciated by everyone. Yes 14.x has been a problem, in fact I've not been able to install any of them (bootloops), but I keep previous kernels on the phone (they are only 4MB each), so at every problem I've always been able to revert back to good ol' nightly 12. So thanks for all of your time and effort - a true dev and a nice guy
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the words =) #14.4 fixes it you can dive into it!
[Samsung Galaxy Nexus] steve664npc:
with AOKP 20 and franco nightly 12 regularly got 1-2% over night but only with aeroplane mode on
[Samsung Galaxy Nexus] nic85:
Franco look this screen.. There is something wrong :) many users have this issue.. O for all app.. And ramfree from 300+ now is 100 + or -

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] zybertooth:
Anybody noticed the increased file size of 14.3 & 14.4? Is it due to the boot animation? Not that I'm complaining.. just wondering..

Thank you franco for all your hard work..

Sent from my non-iPhone
[Samsung Galaxy Nexus] dwang:
Franco,

Can u verify that init.d is working?

On apex 1.0 rom, scripts in init.d aren't being executed at startup w 14.4.

Thanks!
[Samsung Galaxy Nexus] Gabriel Audemard:
Never mind my ringtone, probably you never did. I changed it. Its ok.

Galaxy Nexus, Franco 14.4, KL1, AOKP M2
[Samsung Galaxy Nexus] dr_drache:
thanks, I saw it in your tree, but couldn't see any reverts. FIOPS is amazing IMO (and if it can get better, sweet)

glad it wasn't just me or a mistake, looking forward to your improvements
[Samsung Galaxy Nexus] lynx_deb:
same problem here :(

AOSKP build 21 and kernel 14.4
[Samsung Galaxy Nexus] sishgupta:
79MB Free (limit is set at 80 but it does 79) is exactly what AOKP's minfree taskkiller is set to.

Why you would want more ram free is beyond me. You want the device to use as much ram as possible.
[Samsung Galaxy Nexus] superbobup:
i can also confirm this happening to me...i didn't wipe going from b19 -> b21 in AOKP but i didn't seem to have this issue on 14.2 or test1 kernel
[Samsung Galaxy Nexus] Puzzlegirl:
Wow, go Franco! I'm sure you'll achieve your dream since you are so focused and determined and never give up. Very best of luck to you!
[Samsung Galaxy Nexus] ChongoDroid:
Having support from the gf is.. so important
[Samsung Galaxy Nexus] lynx_deb:
the problem is that all apps report 0byte of memory used
[Samsung Galaxy Nexus] mistermojorizin:
is there any way to get an older nightly zip? specifically would like to try 13.1
[Samsung Galaxy Nexus] bimo2700mf:
how to activate cifs module

hi,

could anyone help me , how to activate cifs module on franco kernel?

ive recently bought usb on the go but i can't use it under franco's kernel

thanks
[Samsung Galaxy Nexus] IINexusII:
was already posted before, but http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] oli20021978:
+1

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
And? It doesn't mean it's not used, it's just a reporting number, means ****. If I open my System app remover all the apps show with 0.0B size and I know they range between 1-10mb. This is not an issue and I WON'T give support for a problem that DOESN'T exist. RAM in Android works a lot differently than normal computers.

If one doesn't know that then I'm so sorry, tweaking a device is not for you.
[Samsung Galaxy Nexus] iceandfire:
Anyone has offsets for color control to remove the purple tint from the screen?
[Samsung Galaxy Nexus] festermania:
Must wait for next kernels version... ?
[Samsung Galaxy Nexus] superbobup:
no worries franco, just wanted to point it out in case it meant something else :)
[Samsung Galaxy Nexus] franciscofranco:
I just emailed Colin Cross about the random reboots. I hope to get an answer soon.
[Samsung Galaxy Nexus] atsavlis:
Franco, I read about a heap randomization that might be causing a higher battery drain. I dont think it has been mentioned here before, have you looked into it by any chance??

A second question I have, is it normal that my phone only drops to 2-4 mA at nights when I sleep, and during the day even if it is not been used, it idles at about 55-80mA? How long does it take for the phone to step into deep sleep?
[Samsung Galaxy Nexus] ericmc:
Need help.....Just flashed 14.4 and im stuck at the boot logo screen

Not exactly sure what i did wrong here....
[Samsung Galaxy Nexus] wayneb02:
Did you wipe cache/davlik cache?
[Samsung Galaxy Nexus] MrAdamH:
Same problem. Could a dev please take a look at this: http://xdaforums.com/showthread.php?t=1469417 ?
[Samsung Galaxy Nexus] superbobup:
are you on 4.0.3 rom?
[Samsung Galaxy Nexus] nic85:
So why with all previous kernel build was all good and graphic issue started with 14?

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] MS.:
Hi Franco, first of all i wanna say thanks for your hard work, really appreciate it. Few minutes ago i found this thread and it scared me to death as today i have seen very similar graphical glitches on my phone. I was more lucky (knocking to the wood) then "Pawnda" and simple phone reboot solved this issue. Also i've noticed that after updating to 14.2 (and same on 14.4) phone gets MUCH hotter when i'm playing Pocket Legends.

Can this be because of quite high GPU overclock? I know, some people using even 512MHz, but still...
[Samsung Galaxy Nexus] ellesshoo:
Anyone else not able to load cifs.ko module? Franco?
[Samsung Galaxy Nexus] franciscofranco:
Look into my ramdisk, I already have that heap thing disabled

This is only for 4.0.3...been said 90 million times.

It could be yes. I'll remove GPU OC again I guess.
[Samsung Galaxy Nexus] franciscofranco:
The random reboots might've been caused by the extra mhz in the buses. I just reverted that patch hoping it will fix it :)
[Samsung Galaxy Nexus] popophobia:
See this as well. It bugs the hell out of me though. I think i'll try to change the clock (am to pm) to see how it goes later.
[Samsung Galaxy Nexus] samizad:
You may have had a bad download. Start again from scratch. Download a ROM and check the MD5 checksum. In recovery, wipe data/cache/dalvik and flash ROM again.

See if that fixes it.

I think it is premature to link the problem in Pawnda's thread to this kernel. Thousands of people are using this kernel with GPU overclock without any problems.
[Samsung Galaxy Nexus] IINexusII:
nooo dont :( read my post here http://xdaforums.com/showthread.php?p=21934123#post21934123, im pretty sure it has nothing to do with GPU. its more likely the bus clocks? i duno
[Samsung Galaxy Nexus] franciscofranco:
Ok Colin answered me. This is directed to the users that sent me the dmesg logs with the reboots:

Framework restarting means it's a rom problem.
[Samsung Galaxy Nexus] yeeson:
#14.4 in update-cm-9.0.0-RC0-GN-KANG-signed.01282012-1008.zip below，many functions cannot achieve。

For example:Color Gamma Tuning and Kernel samepage merging

Don't know if it can solve？

Thanks franco Great god！

PS：My English is not so good:)
[Samsung Galaxy Nexus] franciscofranco:
KSM is already added into my ramdisk for CM9 compatibility - comes in #15.

Color Gamma Tuning, well I already have ColorControl from Ezekeel, does the same thing, but I guess it doesn't work for CM9 so I guess I'll add their code instead or I'll get 500 thousand hate emails.
[Samsung Galaxy Nexus] rockingwing:
i know its rather a small issue, but i noticed this "0,0B used" bug on my phone as well...

fix inc?
[Samsung Galaxy Nexus] yeeson:
Too good！

Thanks franco Great God！
[Samsung Galaxy Nexus] chakra:
Thanks Franco I'll keep checking your app for 15. :)
[Samsung Galaxy Nexus] dr_drache:
I would worry about adding what YOU want to add, does their code work better? then include it. if not... I'd say issue a patch for roms devs. CM9 roms can then get patched. no reason to waste you time.
[Samsung Galaxy Nexus] Kaboosey:
Hello franciscofranco!

Been using your kernel for my first android phone, Huawei U8800! :D Moved on to Galaxy S2 (but you're not there) and now using Galaxy Nexus and I'm glad you're here!

I have bought your updater app to support you. :)

Thanks and keep it up!
[Samsung Galaxy Nexus] franciscofranco:
Ahah you have a point there.

By the way, a little information for you guys about the GPU clocks, this is from Colin Cross:
[Samsung Galaxy Nexus] dr_drache:
BUT, can you undervolt the 384 to 307 voltages? with that information, obviously it seems moot. have we looked at the bus speeds at all? (can we even touch them?) I believe you did bus under volting, but can we do anything else? (obviously, this may take MUCH more time than it's worth it, just ideas in the wind)
[Samsung Galaxy Nexus] dpaine88:
As far as ROM issues goes....can you confirm you are still on AOKP Franco?

Sorry dude I am a tad bit intoxicated but would prefer to stay on the ROM of my fav kernel dev to avoid issues,
[Samsung Galaxy Nexus] StuMcBill:
Flashed to 14.4 and my battery seems to be draining faster than normal?

I have left it in an area with signal, where I would normally get 1-2% of drain over night and tonight it has went down 5% in 3.5 hours?

Can't see any Kernel or Partial Wakelocks that could be causing this, and I have no evidence of any apps misbehaving, so just wondered if anyone else was experiencing the same?

Stewart
[Samsung Galaxy Nexus] yeeson:
When update #15？
[Samsung Galaxy Nexus] StuMcBill:
When its ready!
[Samsung Galaxy Nexus] samizad:
With #14.4, I am getting 1% battery drain every two hours, in idle mode!!! That's 8 hours and only just went down to 96% :)
[Samsung Galaxy Nexus] d3rutat:
So we'll be returning to stock values? :D
[Samsung Galaxy Nexus] ChongoDroid:
I'm getting some really good battery life on this aokp21 with franco. Will report near the end of my charge but I'm aiming for 4.5 hours display time.
[Samsung Galaxy Nexus] IINexusII:
Hmm makes sense i guess..
[Samsung Galaxy Nexus] ChosSimbaOne:
thanks man, guess I will post pastebin in room thread then :-) what room are you using, Just so I can avoid stupid ROM related issues ;)

Thanks for the info and the time you spend on my problem :-)
[Samsung Galaxy Nexus] mohitrocks:
Hey Fransico Franco,

I just wanted to let you know some people using this kernel with AOKP are experiencing major issues.

These can be exhibited here and here

I'm not saying that this kernel is the direct culprit of these issues but I just wanted to let you know, as it could be.
[Samsung Galaxy Nexus] atsavlis:
Morning Franco,

Thought I would mention something that might help you with all the request you get. Before the galaxy nexus, I had the HD2, and I was running a rom and kernel developed by a guy called Dorimanx.

Now because half his users wanted for example 2 way call and the other half didnt, or some liked to have swap activated and other did not, he developed his kernel zip in a way that when you flash it with recovery, it gives you the option to choose what u want done.

Maybe implementing something like that in your kernel could help you out with all these requests for UV, color mods, cm9 mods etc, etc... One file that has options for all users?

Here is a link to his Dorimanx's work, hope I helped out.

http://xdaforums.com/showthread.php?t=1322639
[Samsung Galaxy Nexus] Vangelis13:
Who is this Colin Cross guy & why is his kung fu so strong..?
[Samsung Galaxy Nexus] ro_explorer:
I have great battery results with 14.4 kernel, even if the drain in sleep mode is sometimes spiking at ~double that what I consider as "normal".

The display time is 2Hours ... (the charging status is because I just plugged the phone right before taking the snapshot).
[Samsung Galaxy Nexus] offenberg:
Yeah. I actually managed to get my phone back to life by pressing all three buttons while inserting the battery. I got the bootloader and flashed google image via fastboot. So. She is alive again. But I might never flash this kernel again. Sorry, but it freaks my out that my phone just dies after flashing this kernel. And some users still didnt get their nexus to work again.

I knew the risk when I flashed this kernel. So no blaming on you franco. But people need to know this
[Samsung Galaxy Nexus] franciscofranco:
Thanks I will take a look.
[Samsung Galaxy Nexus] franciscofranco:
He is from Google Android team.
[Samsung Galaxy Nexus] franciscofranco:
Im sorry to disappoint you but I dont see where this is caused by the kernel and without proof I dont thinks its good to say its caused by my kernel, in fact I wasnt very happy to read this posts. People change roms and kernels like they change their underwear, so the chance that its caused by my kernel is like one in a million.
[Samsung Galaxy Nexus] Shetlander:
Franco,

That explanation would explain my testing results. Using An3DBenchXL I tested 3 GPU speeds. 307Mhz, 384Mhz and 512Mhz. Only the first test "Double dragon" saw an increase in framerates with increase in clock speed. All the other tests recorded nearly identical rates which I assume can only be down to a lack of bandwidth.

I think you are correct in removing the GPU oc as it seems to have very little real world benefit vs the power hit.
[Samsung Galaxy Nexus] JcMalta:
Fear of Franco?

I think it is unavoidable that with a kernel as hugely popular as Franco's, someone, sometime will suffer from a bricked device.

Right now, people are swapping kernels and ROMS, playing with Overclock/Undervolt often many times a day. At some point something very bad is guaranteed to go wrong for some unlucky person - and for any UNKNOWN and perhaps RANDOM combinations of Kernel/ROM/Flash changes.

If you were to consider the overall percentage failure rate it's probably EXTREMELY LOW and certainly not significant enough to point a finger at an expert developer's efforts in a highly specialised area of the phone's operation.

When you consider the more general changes in a typical custom ROM (often these changes are "simply/blindly" copied/pasted from elsewhere) it seems to me that for "code coverage" ROMs are perhaps more suspect for battery drain, weird behaviour, crashes and even bricking than any finely crafted kernel.

Franco has generally been against most OC/UV activities - he has really only stood firm on the 700 MHz CPU minimum - for good and fully explained reasons. GPU overlcock is another thing Franco has generally been against - that opinion only recently confirmed by a core Google engineer. I am sure he only gave people the "high risk" options to change these values via his kernel through a minority but "highly vocal/whining" demand.

I have also noticed some ROMs are now including OC/UV interfaces that seem to encourage people to "play" with these values. These user changes should be accompanied with a "LARGE FLASHING RED WARNING - YOU COULD KILL YOUR PHONE"

Personally I believe OC/UV/GPU changes to be solely in the kernel domain and people should listen to and respect the views of all expert kernel developers in these matters.

On my side .. I have been running Franco for many months - NEVER played with OC/UV - the evolving kernel and ROM combinations I use have been more than good enough for me - I do not want to chase the last 1% in speed or battery life to get benchmark scores or whatever by thinking I can do better than obviously clever people by "pushing this up by 25MHz or reducing this by 25mV" ... I am totally happy with where I am sitting using their best, and safe advice.
[Samsung Galaxy Nexus] franciscofranco:
Quoted for truth, thanks for taking the time for writing this.
[Samsung Galaxy Nexus] IINexusII:
Yeah, youll get better results overclocking the cpu than the gpu
[Samsung Galaxy Nexus] offenberg:
Didnt say it was your kernel. Just saying it happened after flashing it. And I never flashed any other kernel then yours on my nexus. And the only custom rom I ever flashed was aokp.

So the chance is one in three. It could be your kernel. And it could be aokp. Or it could be some hardware problem. I just thought it would be a good idea to mention this in your thread when users are getting issues after flashing your kernel. But ofcourse your kernel is perfect.
[Samsung Galaxy Nexus] JcMalta:
>> But ofcourse your kernel is perfect.

Maybe not "perfect" - but certainly one of the very best, the most cared for and supported. Can you do better?
[Samsung Galaxy Nexus] offenberg:
If it is one of the most supported, then tell my why I cant post here when I have issues. Im sure you would write the same if your nexus was a brick.
[Samsung Galaxy Nexus] barryflanagan:
I couldn't agree more. Well said. I have never felt the need to second guess Franco and have found his kernel in combination with AOKP to be virtually flawless.

-Barry
[Samsung Galaxy Nexus] JcMalta:
Into my ignore list. You obviously have personal issues.

</SubjectClosed>
[Samsung Galaxy Nexus] darrendm:
Have you ever thought maybe you had a dodgy nand chip? Because think of the hundreds (or thousands) of people that use AOKP+Franco's kernel together and have never experienced a problem at all (including myself).

I would be very angry if my phone bricked (as yours has) but then it's all done now. Flashing anything comes with a risk and it's sad to say that you was an unlucky one. Thanks for coming here and sharing your bad experiences and hopefully it won't happen to any more of us. I hope you get your phone replaced and are not scared to flash again, because kernels as such as this have really evolved my phone in terms of battery life and performance.
[Samsung Galaxy Nexus] offenberg:
You created your own subject. No one ever asked you to share your thoughts. Maybe you should mind your own business. I just replied kindly to your post.
[Samsung Galaxy Nexus] IINexusII:
It happens, had the same problem with my S2 where the nandchip failed simply after wiping data in recovery. Thats why we have warranties on our phonrd
[Samsung Galaxy Nexus] offenberg:
Thank you. Yeah it might be the chip. I just thought I'd share it here, as it happened right after flashing this kernel. Im not angry at anyone, and I think franco is a gift for this forum Sorry if I offended anyone.

I have used franco's kernels for a long time on my nexus s. So I know he is a great dev.
[Samsung Galaxy Nexus] franciscofranco:
You have not offended anyone, and I'm thankful for your post. The problem is that 90% of the persons would read this "OK FRANCOS KARNAL BRIKED PHONES DUN FLASH IT MOAR OR IT WILL MAKE YAR PHONE EXPLODES LIKES AN ATOMIC BOMBS", where in fact you were just reporting an issue that occurred to you. I hope you can fix your problem through your warranty and enjoy the GN once again!!
[Samsung Galaxy Nexus] darrendm:
Back on topic now :D

Franco, I understand you've been against the GPU overclock but you've put it in to keep some users happy? Personally I think its overkill and there have been some posts stating you see no real improvements even with a 512MHz overclock.

My phone also gets quite hot (in the top corner) with this current overclock, it was definitely a bit less warmer with the GPU set to stock. (Not that I'm worried about adverse affects, it's just a bit unneeded to be getting hot when playing games which look quite low graphically.)

Sorry for bringing this up once again because I know people keep going on about it but, will the oc be kept in all future builds? Will your app have a custom interface to control GPU overclock in the future?

Thanks for everything once again bro.
[Samsung Galaxy Nexus] mfish123:
On 14.4, stock settings, other than hot plug enabled, ruining aokp b20 (no mods and not using power control).......I was streaming pandora music and listening over head phones and after a half hour, my screen would not turn on although the music kept playing. Sorry I don't have a log. Also on 13.1, 14 and 14.1 id get ocasional random reboots. Id get them to a lesser extent on 14.2 (never tried 14.3). I'm back on old trusty 12 running stable as a rock.

Not sure if any conclusions can

be drawn from this info but I did want to share my recent experiences.
[Samsung Galaxy Nexus] kva:
First about UV: sometimes it is good to have possibility to UV, cause everybody wants to have more batter life... On SGS2 I got 15% more batter life with UV.

About OC: do not like OC, but GN currently IS NOT WORKING as it should be. UI lags. Even GTalk in landscape mode lags. Think that OC will help a little bit in that case, but it will not eliminate problem. I hope that this will be fixed some days.

Some kernel testing: the only two kernels which have no UI lags in GTalk landscape for me are Glados (with 110/110 version) and Trinity 512b version for me.

Franco, what is the best way to build ramdisk ? Compiled kernel from your sources, want to play with my phone a little...
[Samsung Galaxy Nexus] franciscofranco:
I don't care if people cry again about GPU OC, I have Colin's email to prove my point. I'll build this as I will, either users like it or not.

Thanks for this.

Get a boot.img and unpack it and you'll have your ramdisk.
[Samsung Galaxy Nexus] nic85:
agree with GPU@stock 304 mhz. :cool:
[Samsung Galaxy Nexus] franciscofranco:
#15 will also feature two different governors based on Conservative: francoGazelle and francoTurtle. The first is a tuned conservative for performance while maintaining some battery balance. The second one will be tuned for battery.
[Samsung Galaxy Nexus] nic85:
Which one of these two is more similiar to this "normal" version?

will you fix that 0bytes issue in app ram info?
[Samsung Galaxy Nexus] Nebucatnetzer:
Thanks for staying to your line. The way YOU build the kernel is the reason why I like your kernel. I'm happy that you gave us the option to undervolt but I would still use the kernel without it. What I have been doing with the previous versions.

I wanted to thank you as well for the two governors. It's great to have the choice.

Keep up the good work and have a nice weekend.
[Samsung Galaxy Nexus] franciscofranco:
Probably francoGazelle will be alike this current version with a little tunes.

What bug in the app ram info? There is no bug, apps are behaving normally.