yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jkoljo:
Yeah, it does not work. Just goes back to home screen when I try to launch it.
[Samsung Galaxy Nexus] franciscofranco:
It works for me, just tried it.
[Samsung Galaxy Nexus] salivaman:
Same here. But I managed to solve it by clearing the app data and reinstalling the game. And it lags real bad. I'm using the non-384mhz version of the r141.
[Samsung Galaxy Nexus] leelaa:
Franco, will there be another 512 gpu release before the next miledtone? Iam on 142 at the moment and its running great. Just miss the 512. I suppose its not a big deal though.
[Samsung Galaxy Nexus] milander:
Franco's latest nightly already included the 4.0.4 drop fix. You do not have to install the OTA update.

Sent from Galaxy Nexus using Tapatalk 2
[Samsung Galaxy Nexus] Moz007:
You can't creat a .zip for apply stock values in recovery ? Or a .bat with adb command ?

Can we have the smartassv2 governor, best governor in benchmark i see...
[Samsung Galaxy Nexus] raubkatze:
For me gta3 works fine without any lags. r141 (512).
[Samsung Galaxy Nexus] franciscofranco:
No, 95% of the users will cry anyway. I'm not going to be flexible with this.

No go for Smartass2 as well.
[Samsung Galaxy Nexus] bigeyes0x0:
@people want to apply UV at boot: You can just create an init.d script to apply these UV values at boot, you don't even need the app for this. People who knows how to create these scripts should know how to take care of themselves once problem occurs anyway.
[Samsung Galaxy Nexus] jan-willem3:
Some nice looking stuff I came across accidently.

https://gitorious.org/gcx/staging/commit/8eccca54d2fe40a4de1d7c0dfc0ac87a3c4fabe3

https://gitorious.org/gcx/staging/commit/286400383ea9b05e82baf53af58827d47d000b3d

https://gitorious.org/gcx/staging/commit/1845cede5893256c2f82a500e17f9763a4f41850

In the git are maybe some more useful ones, some of them were already included in your git as far as I could see.
[Samsung Galaxy Nexus] emerica243:
Whats the LAZY governer? Also does anyone have problems receiving calls when they have CPU1 shutdown on screen off checked?
[Samsung Galaxy Nexus] franciscofranco:
I have the first two. The last one isn't for our battery driver.
[Samsung Galaxy Nexus] raubkatze:
http://xdaforums.com/showpost.php?p=25064087&postcount=12975

I have not problems with receiving calls.

Franco, thanks!

r142 is amazing! Now awaiting new milestone and 512 gpu oc release based on r142.
[Samsung Galaxy Nexus] vomer:
Franco can you comment on r142 in liquid? Is it 384 or 512 gpu?

I flashed r141 to test and wondering if 142 is the same? If not are you able to post a download? Thx!
[Samsung Galaxy Nexus] raubkatze:
384 - http://xdaforums.com/showpost.php?p=25148725&postcount=13225
[Samsung Galaxy Nexus] vomer:
Thnx man! Dammit should not have flashed 141.
[Samsung Galaxy Nexus] momomok:
I have made a flashable zip for r142 nightly

Since it is extracted from the Liquid ROM, it is a 384 GPU version - don't ask for 512 GPU version, I just pack the kernel to save others' time, I don't build kernel

http://dl.dropbox.com/u/23739553/franco.Kernel-r142.zip

CRC32: CD56FCC0

MD5: 13D990CB529CA48AC3FE4E7C17EDC44F

SHA-1: 75F28EFA14032E7D8AD967B129AA7F7D837D1096
[Samsung Galaxy Nexus] vomer:
thanks man! works great!
[Samsung Galaxy Nexus] mikespe:
Ya may want to check with Franco & the Liquid Team to see if this is OK to do...probably fine but it is courtesy
[Samsung Galaxy Nexus] bigeyes0x0:
Heh I made that long ago but didn't post it because I think franco want ppl who uses liquid to test it out as limited beta and liquid ppl might want to use franco kernel as a promotion. I tried it with stock IMM76I pretty nice.
[Samsung Galaxy Nexus] schizophrenia:
experience with Mytrack

So this is my testing.

After charging (see battery graph) I turned on Mytrack and after 2 hours or so battery went down from 88 to 30 something. During the 2 hours almost the entire time was on max clock except the first 23 minutes. The phone then went really got. It was 99% screen off during the testing 2 hours.

It worked fine when I was on stock a bit more than a month ago. And there have not been any Mytrack update either.

Seems its the kernel? Possible?

Now on aokp b32 and franco r41 512 interactive. Tried general hotplug on and Lazy governor and it was all the same.

Any insight?

Sigh. Feel bad I can't track my travel as I have always been.
[Samsung Galaxy Nexus] momomok:
Thanks for the reminder. Just dropped them a message, hope they would agree on this... :)
[Samsung Galaxy Nexus] leelaa:
They might do, but iam pretty sure if he wanted us to use it he would of released it. :confused:
[Samsung Galaxy Nexus] six_dfx:
I think franco is very well aware of what the GPL is and what it implies regarding code redistribution ... of course it's always nice to ask, but you really don't have to by the kernel license terms.
[Samsung Galaxy Nexus] leelaa:
Youre absolutely right, but franco is a great dev and works extremely hard at what he does, the least we can do is wait for him to push his own kernel out.
[Samsung Galaxy Nexus] Moz007:
Can you explain me how to do that for all values please ?
[Samsung Galaxy Nexus] franciscofranco:
Like I said its ok by me. I didnt release it because it was just a small change and not worth my trouble and I knew it would be M3.
[Samsung Galaxy Nexus] bigeyes0x0:
Well UV with the app then go check this directory /sys/class/misc/customvoltage/

There'll be three files there: core_voltages, iva_voltages and mpu_voltages. You need to echo mV value for each OPP from highest to lowest, e.g.

echo "1250 1127 962" > /sys/class/misc/customvoltage/core_voltages

You can do the same for iva_voltages and mpu_voltages. Put these echo commands into text file then copy it to /system/etc/init.d and set it permissions to 755 and you're done.

An example of the file:

#/system/bin/sh
echo "1250 1127 962" > /sys/class/misc/customvoltage/core_voltages
echo "x x x x" > /sys/class/misc/customvoltage/iva_voltages
echo "x x x x x" > /sys/class/misc/customvoltage/mpu_voltages

Change x to any value you want, remember they are mv values which are for highest to lowest frequencies.
[Samsung Galaxy Nexus] leelaa:
Franco, iam on liquid with 142, i want 512 would you recomend going back to 141 or wait for your next release?
[Samsung Galaxy Nexus] raubkatze:
I tried r141 (512) on liquid 1.3. Works fine.
[Samsung Galaxy Nexus] Serious_Beans:
The next release is going to be M3 which will be 384 gpu, gonna probably have to wait until the next nightly or go back to 141.
[Samsung Galaxy Nexus] leelaa:
Thanks mate, will flash now.
[Samsung Galaxy Nexus] Emilius:
Ha, ha very funny. What is wrong with this frequencies anyway? Post like this is really helpful.

First you are giving wrong information that something is wrong without further explanation but it's simply nothing wrong here.

Second you trying to be funny and rood in same time. Probably reason for that is because you don't see me here so often so my reputation is lower then yours around here. Is that it?

...and third, how you helping me or anyone else with this anyway? After I saw your comment I just got big question mark above my head WTF

Just grow up my friend, nothing else to say...
[Samsung Galaxy Nexus] tcchuin:
Don't feed the troll
[Samsung Galaxy Nexus] Dmw017:
You just did .....
[Samsung Galaxy Nexus] ArmanUV:
offtopic: how do you like the one x franco? worth the upgrade?
[Samsung Galaxy Nexus] audibalso:
Check his g+ page. He wrote about his experiences with the one x. But to paraphrase I believe he thinks its the best Android phone currently.
[Samsung Galaxy Nexus] neotekz:
franco can you make the cpu and gpu voltages apply at boot? i know you probably did this for safety but thats what cwm is for.
[Samsung Galaxy Nexus] leelaa:
Go back a page or two, its allready been answered.
[Samsung Galaxy Nexus] Emilius:
Is it possible to apply voltages like 3 minutes after boot so user have a chance to restore it back in case something is wrong? Also this 3 minutes can be user choice?

I usually restart my phone when charging and in 95% forget about voltages LOL
[Samsung Galaxy Nexus] Antob125:
From my understanding Milestone builds are 307 gpu which is stock. Correct me if I'm wrong.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
Yes, you're right. Milestone with stock gpu and usually 2 nightly with 384 and 512 gpu oc.
[Samsung Galaxy Nexus] Ma5heen:
Franco's app allows users to set maximum battery capacity above the default 96. It allows it to be set higher than 100. Would a value higher than 100 do anything?
[Samsung Galaxy Nexus] Moz007:
Thank you very much this is very very helpfull !

I can now start to find my best uv.

A session of 10min in temple run is a good stress test for stability or do you have a better test ?
[Samsung Galaxy Nexus] raubkatze:
Is this possible to charge the battery more than 100%?
[Samsung Galaxy Nexus] bigeyes0x0:
@Moz007: I forgot a character there

#[B]![/B]/system/bin/sh
echo "1250 1127 962" > /sys/class/misc/customvoltage/core_voltages
echo "x x x x" > /sys/class/misc/customvoltage/iva_voltages
echo "x x x x x" > /sys/class/misc/customvoltage/mpu_voltages
[Samsung Galaxy Nexus] neverhappy:
I would like to give the Liquid Rom a try. Can someone direct me to the proper download location? Hopefully there is a version for CDMA.
[Samsung Galaxy Nexus] Langduscher:
Check Rootzwiki mate :)

---

OK so I'm not impressed with r141, feels more laggy than r140 :confused:

Ran r140 on Bamf 1.2 and it was golden. On Liquid 1.3 r142 didn't do it for me either :confused: so flashed r140. All (but the browser) was good again. HATED the laggy browser so flashed GlaDOS and it seems a little better, but not by much.

N/M, I'll go and nag in the rom thread now :D
[Samsung Galaxy Nexus] Metallice:
Franco Kernel nightly #142 with 512mhz GPU and Vibration Control

Built from source.
[Samsung Galaxy Nexus] leelaa:
How u get this? Is this official?
[Samsung Galaxy Nexus] drawde40599:
Says HE built from source right on it o_O ,
[Samsung Galaxy Nexus] zephiK:
His post says, "built from source."
[Samsung Galaxy Nexus] leelaa:
Sorry i didnt see that i just seen the first part, and then boom..fiteworks

:)
[Samsung Galaxy Nexus] franciscofranco:
Although its ok by GPL to built whatever you want from sources and re distribute having different franco kernel kernels around with different abilities create a bit of fragmentation. Think about it ;)
[Samsung Galaxy Nexus] alphaola:
Nice one mate, like the way you constructively address that. Seen issue like that blown out of proportion. Franco seem like an open guy, quick pm to him could do wonders.think about it lol.
[Samsung Galaxy Nexus] Gahh Its Lee:
My app keeps force closing once I toggle generic hot plug. Any ideas? Never did before I've cleared data and cache for it.

Also I found out I can run the 512 kernels if I disable sr. Would that make my battery life a lot shorter?
[Samsung Galaxy Nexus] franciscofranco:
Aye. No harm done with posting my kernel compiled from sources, the only issue is the fragmentation it can create, then I get tons of emails, tons of bad rating on my app because compiled kernel francomod something crashed etc etc. My user base is so big that I cant afford fragmentation. If all the users used their brains there wouldnt be a real fragmentation because they would separate the official release from some Mod compiled from sources. Sadly this isnt the case so its not good for me. :) I hope Im not offending anyone, its just my insight.
[Samsung Galaxy Nexus] leelaa:
Franco i know this is not the right thread but i could use your help, i asked in liquid thread but got no answer.

Would using the gpu acceleration option in prop builder setting increase performance, or what are the benefits?
[Samsung Galaxy Nexus] franciscofranco:
Nah dont bother with that option to be honest. I seriously have to take a look into Liquids control app, some options dont make much sense. Anyway next time send me an email ;)
[Samsung Galaxy Nexus] leelaa:
Ok thanks mate, and sorry i didnt think to send one, will do next time though.

:)
[Samsung Galaxy Nexus] mikespe:
That's why I mentioned to check with you first. He may have compiled the zip file but you'll get stuck holding the bag. I'm not bashing the guy (sorry I forgot who it was already! :confused: who ripped your kernel from Liquid...it was actually nice of him to do
[Samsung Galaxy Nexus] The Nexus Project:
141 is definitely running blazin hot. I hope a fix is in the works

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] Metallice:
No problem. Probably won't happen again, just people wanted liquid's 142 with 512 MHz gpu so I decided to help. I figured it wouldn't cause any issues for you as only crackflashers would check the forums and download a modded kernel anyway. Also the only difference from your "official" release is the vibration control, which doesn't matter unless you have the know-how to change it anyway. I understand the concern with fragmentation, and I don't plan on uploading any more kernels.
[Samsung Galaxy Nexus] franciscofranco:
Like I said there is no problem from me, you can do it, you're free to do it :)

By the way I got some users complaining about Lazy governor causing them reboots sometimes, did it happen with you?
[Samsung Galaxy Nexus] ragnarokx:
Lazy has been running like a champ for me. No reboots on 141 since it was released.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Razer(x):
Is fast charging safe? no cons?
[Samsung Galaxy Nexus] stellaryt:
I use Lazy 3 days with r141 and r142,everything works fine here.
[Samsung Galaxy Nexus] Metallice:
I've been using lazy since build 135 or so and have never had an issue.

The only thing I've noticed is increased time at 384 and decreased time at max frequency with no performance loss. :)
[Samsung Galaxy Nexus] Metallice:
Even so... too much work haha.
[Samsung Galaxy Nexus] Unlawful:
Yep, its fine. It will only drain how much your output puts out.
[Samsung Galaxy Nexus] drawde40599:
Using the 512 kernel u put up, appreciate it!!!
[Samsung Galaxy Nexus] franciscofranco:
#4.2

* Add Governor Control - lets you to change governor parameters as your own taste. Currently only supports Ondemand and Interactive. Values don't stick on reboot for now, but they will on future updates

* Export RGB gamma values to be visible in their EditTextPreferences for easy check

* Others small fixes and improvements
[Samsung Galaxy Nexus] rookie8155:
I just read it on www.mobilesyrup.com that Galaxy Nexus users getting OTA update to fix screen-off signal problems. I hope this will be fixed in next kernel update?
[Samsung Galaxy Nexus] franciscofranco:
XDA -> Search -> Search this thread - it's been answered before.
[Samsung Galaxy Nexus] jeeholim:
Damn, fine job you did sir. After flashing your kernel (r141), all of my games started running smooooooth. Gangstar Rio, Asphalt 6, they all were laggy, but now it's smooth as butter. Thank you.
[Samsung Galaxy Nexus] samizad:
I've been wondering just how big this kernel is. I know your app has has 11,000+ downloads but do you get a count of how many phones are running with one of your Milestones/Nightlies?
[Samsung Galaxy Nexus] Metallice:
Awesome! Stupid Play store shows an update, click it, only get open and uninstall options... ARGH.

Edit: Alright now it worked... I guess I was too quick for it.

Oh and just because everyone else does it... Franco 142... End of the day... battery - 70%... On Screen time 1:20... Freq 384 - 1036 on Lazy. That will do I suppose.
[Samsung Galaxy Nexus] heo_con184:
I updated just fine.

Hope M3 will be coming real soon.
[Samsung Galaxy Nexus] javi3k:
hi just some offtopic i just bought your app from market i have to say so great all the features that you can do, i have some dude about color multipliers and gama, the values that you recomend in the app affect battery life and screen longetivity
[Samsung Galaxy Nexus] Gahh Its Lee:
Huh?
[Samsung Galaxy Nexus] heo_con184:
I guess he wants to ask if the recommended gamma values in Franco's app will affect battery life and screen on time (comparing with stock values).
[Samsung Galaxy Nexus] lwclam:
Google Play no update shown

After clear the cache, it updated.
[Samsung Galaxy Nexus] javi3k:
this hehe sorry my english is not that good
[Samsung Galaxy Nexus] audibalso:
Give it a little time. It's there... happens to me sometimes. Google play is can be a little testy
[Samsung Galaxy Nexus] Gahh Its Lee:
No worries and no the values are all 200 or under so they shouldn't impact negatively at all
[Samsung Galaxy Nexus] Emilius:
This is not working for me. After reboot all voltages are back to default. What I am doing wrong? The name of the file could be anything right?

---------- Post added at 05:14 AM ---------- Previous post was at 05:11 AM ----------

nice, thanks for that Franco
[Samsung Galaxy Nexus] SrTapir:
In the Ezekeel post says it's between 0 and 101%.

But later on in Bugfix 3, he says he has adressed the mod with the "100% charging fix" (but I think it has to be not letting the batt to be overcharged)..

[MOD][KERNEL] Battery Life eXtender (BLX)
[Samsung Galaxy Nexus] GNEXc:
is r142 available ? I dont see it on Franco Kernel Updater ..
[Samsung Galaxy Nexus] Gahh Its Lee:
Am I the only one who's phone still goes to 100% when blx is at 96%?
[Samsung Galaxy Nexus] jnr21:
I get 100% too.
[Samsung Galaxy Nexus] mazubo:
Check this screenshot out! I thought it was kewl, since it probably won't happen again.......

Edit: latest vs. Installed

:-D
[Samsung Galaxy Nexus] jnr21:
:facepalm:

Liquid installed? ;)
[Samsung Galaxy Nexus] mazubo:
Yup! I wasn't too sure how long it would take for someone to figure it out! :D

:-D
[Samsung Galaxy Nexus] jnr21:
Franco released 142 just for liquidrom.

https://docs.google.com/document/d/1EypCE65prJM4JLjgXbFwKq3oEX1__660uxqOlkV3SYc/edit
[Samsung Galaxy Nexus] mazubo:
I know! It was cool to see the app info vs. The installed that's all!

Cheers,

:-D
[Samsung Galaxy Nexus] jan-willem3:
More people have high drain when playing music it looks like it stays @1228 mhz instead of 384.

Also when I use the app to set it @max 384 mhz it doesnt really feel like it is running @ 384mhz.

Maybe its because I am still at android 4.03

Sent from my nexus
[Samsung Galaxy Nexus] SrTapir:
I think because the "96%" that BLX reads is the nominal 100% that everyone have as the "full charged" battery.

If you remove this protection you'll have also a 100% charge reading (I think the UI does not have icons for more than 100%), but in real it will be a little bit more, maybe you'll have to re-calibrate to have a real batt indication.
[Samsung Galaxy Nexus] tishfire:
Having a good battery status on 135
[Samsung Galaxy Nexus] tixed:
On nightly 141, sudden kernel FC (reboot) when trying to launch Play Music from playlist icon. Sent you a crashlog from your app, hope it'll be helpful.

(never before submitted crash logs, so ask me for any additional info if you need it)
[Samsung Galaxy Nexus] rubino90:
My phone when stay screen on temperature CPU stay around 47 celsius is normal smartflex is enabled
[Samsung Galaxy Nexus] jnr21:
Screen on time?
[Samsung Galaxy Nexus] sago62:
Now I 142-512 ... From 140 the telephone has SOD at least 4 times a day .... Many times when i remove the phone from the net220-usb
[Samsung Galaxy Nexus] leelaa:
Franco, will we be expecting any new release anytime soon?, 142 running great with LAZY.
[Samsung Galaxy Nexus] Antob125:
Umm Franco has released experimental builds ahead if builds that were released plenty of times. If this excites you sorry to take it away.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Doesnt feel like its a kernel crash, I never had FCs caused by a kernel.
[Samsung Galaxy Nexus] Stretlow:
Isnt 142 - 384?
[Samsung Galaxy Nexus] leelaa:
Someone else built from source, and this is what franco dosnt want to happen in his thread, (people reporting crashes etc) for a kernel that he has not released.
[Samsung Galaxy Nexus] tixed:
Well, maybe my terminology isn't right - I've got reboot without the first part (with google logo), fast one. Maybe that doesn't count as FC. Assumed only kernel rebooted then.
[Samsung Galaxy Nexus] loudaccord:
142 is working fine for me. Finally got the app too... I just did echo commands since it was simple. Figured getting the app was a good way to show support though. Keep on rockin.
[Samsung Galaxy Nexus] asim0:
LEET

sorry i let the geek in me out:cool:
[Samsung Galaxy Nexus] franciscofranco:
I'll have to throw out one last nightly r143 for stability, had to do some reverts from stupid code and interactive patches keep coming up from android-omap-3.0.
[Samsung Galaxy Nexus] leelaa:
Cant wait, thanks for all the hard work franco.
[Samsung Galaxy Nexus] tishfire:
39% as displayed.. loving this combo...
[Samsung Galaxy Nexus] raubkatze:
He meant screen-on time in hh:mm -)
[Samsung Galaxy Nexus] joeyfong:
Can't wait for 143.
[Samsung Galaxy Nexus] sago62:
I'm trying everything .... When the phone Out of charge does sod .... Ideas?
[Samsung Galaxy Nexus] Metallice:
Alright man, be careful not to change too much. It's working so great right now that I'm afraid any changes might break some of the awesomeness :D. Just getting fantastic screen-on time.
[Samsung Galaxy Nexus] raubkatze:
Rom, kernel build, kernel settings etc?
[Samsung Galaxy Nexus] Metallice:
From your previous post it sounds like your using the unofficial kernel I posted earlier. Please do not request support/help when using unofficial kernels without FIRST testing the official release.

However, that said, the only difference between official 142 and the one I posted is the addition of vibration control (and 512 GPU but that's normally standard), so its unlikely that switching to the official build will solve your problem. STILL, you need to try using the official build before anything else.
[Samsung Galaxy Nexus] sago62:
From 141 ... Now unofficial 142...With almost 512 gpu, cpu 384-1228, various governor .. CM9 kang!
[Samsung Galaxy Nexus] drawde40599:
Never m, oops
[Samsung Galaxy Nexus] tishfire:
Ohh I didnt noticed I could see it until you've mentioned.

fingered from Galaxy Nexus...
[Samsung Galaxy Nexus] leelaa:
143?
[Samsung Galaxy Nexus] raubkatze:
I have the same question...
[Samsung Galaxy Nexus] franciscofranco:
I havent released r143 yet didnt even pushed the patches to my git. I absolutely HATE when users provide false information, and I'm being serious.
[Samsung Galaxy Nexus] leelaa:
Must of been a typo, he's corrected it :p
[Samsung Galaxy Nexus] spinkick:
Get rid of the unofficial 142 before asking a single thing. :rolleyes:
[Samsung Galaxy Nexus] raubkatze:
You flashed it at your own risk. Reflash to official.
[Samsung Galaxy Nexus] akellar:
This is a 4.0.3 kernel.
[Samsung Galaxy Nexus] franciscofranco:
With a logcat it should be easy to see, but its odd indeed.
[Samsung Galaxy Nexus] Audionut11:
Ok cheers. fwiw, different roms, different kernels, they all have had this issue.

I'll do some research into logcat and see what I can see.

Cheers again.
[Samsung Galaxy Nexus] altimax98:
I love your kernels but it kills my ability to play GTA. I've noticed that your kernel is the only one that modifies the SD card binary.. what is it in there for? And is it safe to remove?

Thanks!
[Samsung Galaxy Nexus] DebauchedSloth:
I've describe what it does (and why) earlier in this thread. In a nutshell, the system binary uses something called FUSE, and runs all sdcard file I/O. This adds quite a bit of overhead. The new one just lets the filesystem access the sdcard directly, and makes all files readable by everyone (which is what the system version does, slowly.)

It's utterly safe to replace it with the system sdcard binary. You don't want to just remove it, you'll lose your sdcard.

A version which plays nice with GTA is just about ready.