yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DebauchedSloth:
Yes, I'm aware of that, but cannot install GTA to test.

That said, the new sdcard binary binary is not involved in the file system at all. When Google swapped to their new scheme, they needed to preserve the old /sdcard sematics, which were that file system permissions did not exist - so any program can access any other programs files on the sdcard. They did this by using something called fuse - and all file i/o routes through their sdcard binary (you can see the CPU usage, BTW.)

What the new sdcard program does is watch the /sdcard directories and, as soon as a file is created, makes it read/write for everybody. All file i/o is native and goes straight to the file system.

One hitch there is that it does make files case sensitive; on the old setup fu.bar is the same as FU.BAR - with the straight mount, they are different files. I suspect GTA3 is relying on that and, if so, there's no good fix.

Once I get it installed, I'll give it a whirl.
[Samsung Galaxy Nexus] paOol:
Before going to sleep, I decided to give bugless beast another try. I wiped, and flashed and installed the nightly 4 kernel. Turned on airplane mode, and went to sleep.

woke up this morning to this.

going back to rootzboat lol, bugless beast is no bueno.

EDIT: also, NFC was not working. don't know if its the rom or what.
[Samsung Galaxy Nexus] franciscofranco:
I'm aware of that awake issue. I think its caused by OTG, I'm having awake issue myself, showing OTG as holding a wakelock. I'm trying to track it down. It's not an easy thing to see.
[Samsung Galaxy Nexus] mDroidd:
I ordered my GN also now, at amazon.de

Well, I hope if you have your GN that your kernel will be higher in this section :P good work :)

Greets

____________

mDroid - Tapatalk

Phone: LG-P500

ROM: Nitrogen - Beta-V1b

Kernel: custom .35

Theme: ICS (Z25 - paid. ported by me :D)

Tweaks: ALL

Wishlist: Galaxy Nexus :)
[Samsung Galaxy Nexus] rabhw:
Really hope there's a way to fix the SD card hack to make GTA work.

I know it should technically be Rockstar fixing GTA to work with the SD card hack, but we know that won't happen :)
[Samsung Galaxy Nexus] DebauchedSloth:
Yeah, sure looks like they want case insensitive file names. Very messy.

I tried extracting all the file names and mapping them to what the code expects, but not easy going....
[Samsung Galaxy Nexus] beekay201:
reporting back about network signal drops, for general knowledge.

further testing with all 3 kernels i've been using, stock, franco's and matr1x led me to the conclusion, 4.0.3 has something that has been making network signal drop to out of service, i didn't have this on 4.0.2~. it's pretty random too.

could it be the baseband? i'll try that first. also, after this happens, right after communications are reestablished, try to switch 2g/3g. took like 1 min to switch, in my case. data call was active.

@francisco, what baseband are you using mate?
[Samsung Galaxy Nexus] craskman:
Francisco,

I am trying to access the source from you git link but keeps saying "You do not have access to this repository." Do I need to request you anything?

Also, on which OS are you compiling the kernel and what cross-compiler are you using (and version)?

Thanks
[Samsung Galaxy Nexus] franciscofranco:
I'm using the latest XXKK6.

Send me a PM with your email. I'm using Elementary OS 10.10 with Linaros 4.5.4.09.2011.
[Samsung Galaxy Nexus] mrcool007:
Hi, i have a strange issue. I don't know if it is kernel related or it is the ROM. I'm using AOKP build9 with your kernel and when i use landscape mode the UI is not smooth :/
[Samsung Galaxy Nexus] depths:
Setting draw animation to 'none' in draw settings using apex removes the lag.
[Samsung Galaxy Nexus] nikulogical:
This is true. Now I remember why I'm not getting this lag. I set my soft glow animation from normal to super quick in AOKP's ROM settings.
[Samsung Galaxy Nexus] spaceman860:
The Franco app is very useful a must have (support)

729 is better so you don't get signal drops when screen is off and sends the phone to sleep faster saves power. I use smart flex

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] KLUVJ:
Dont know about you guys, but i just reverted to 121 512 gpu and woww....r133 at 384gpu was super laggy for me. im thinking 121 to be my new milestone, at least until the next nightly blows things away.
[Samsung Galaxy Nexus] javi3k:
guys sorry to aks, but is this kernel oc by default ?
[Samsung Galaxy Nexus] chlehqls:
Hey guys, I just tried this kernel coming from the kernel that came with AOKP's b31 which I think is from faux's. After installing 133, I tried playing Anomaly HD (Pretty graphic intensive) and was getting stuttering to an eventual freeze.

What am I doing wrong? I reverted back and now there is zero lag in comparison.
[Samsung Galaxy Nexus] pewpewbangbang:
Might be because your phone can't handle the low voltage at 512mhz as I heard he lowered it. I can run it fine though playing temple run etc
[Samsung Galaxy Nexus] chlehqls:
Interesting. Further goes to show you that all phones are not created equal. Shame, I really liked the feel of this kernel for some reason. Maybe next time.
[Samsung Galaxy Nexus] pewpewbangbang:
Heres my battery life. First day using r133 and slim ICS. Can definitely hit 5+ hours of display time. That bad cell standby was from having no service for like an hour without realizing it.

View attachment 1000386

View attachment 1000387
[Samsung Galaxy Nexus] nklenchik:
Interactive or ondemand?
[Samsung Galaxy Nexus] pewpewbangbang:
hotplug with 384mhz min
[Samsung Galaxy Nexus] samizad:
It is set at 1228 MHz by default but it allows overclock to 1344 MHz using Francisco's app or other apps such as SetCPU etc.

There is also GPU overclock by default. Two versions: 384 Mhz and 512 MHz.
[Samsung Galaxy Nexus] BrUhNiGGs:
I may have missed it on the OP or something but could someone tell me exactly what SQLite is and what the option of 'set SQLite Defragment on boot' in Franco's app? Do many of you guys use that feature and is it reccomended to use it?
[Samsung Galaxy Nexus] KLUVJ:
＋1
[Samsung Galaxy Nexus] bryant_16:
My battery life seems to be bad after flashing to r133. Stock rooted rom here.

Should I switch back to r130?
[Samsung Galaxy Nexus] nklenchik:
I don't want to tell you what to do, but no.
[Samsung Galaxy Nexus] JcMalta:
Bryant strikes again!

Man ... the last 10 pages of this thread are FULL of discussion and tips of how to improve battery life - both via ROM and kernel configuration. Read those, experiment and decide what you feel is going to be BEST FOR YOU!
[Samsung Galaxy Nexus] nikulogical:
Yeah r121 is pretty much perfect foe me as well. R133 ended up giving me problems even with the gpu voltage fix. I'm testing imoyeson's new lean kernel right now though. He introduced live gpu oc.
[Samsung Galaxy Nexus] Gahh Its Lee:
Franco did that awhile ago but took it out.
[Samsung Galaxy Nexus] nikulogical:
Yeah I know, just the first time IMO introduced that and 512 gpu so I wanted to test it.
[Samsung Galaxy Nexus] BrUhNiGGs:
Could someone give me the voltage values for the GPU fix?
[Samsung Galaxy Nexus] KLUVJ:
link？
[Samsung Galaxy Nexus] schizophrenia:
http://xdaforums.com/showpost.php?p=24716477&postcount=11957

but it wont stick after reboot

need to set again
[Samsung Galaxy Nexus] nikulogical:
http://rootzwiki.com/index.php?/top...imalistic-Kernel-(3.2.1,-4/12/12)#entry320079
[Samsung Galaxy Nexus] spinkick:
Seems like most run 384 w/interactive now. Have we really done any testing to see if 700 really does allow for more sleep and less signal drop than 384? Is running 384 really worth the power savings over 700?
[Samsung Galaxy Nexus] GibMcFragger:
Try the lower clocked GPU version of the kernel before your give up on it. Same features, battery life and kick assness, just not the overclocked GPU. :)
[Samsung Galaxy Nexus] schizophrenia:
yes you are right.

but it feels a bit more choppy on games/graphics
[Samsung Galaxy Nexus] spreketek:
yey! i fixed the n133 gpu glitches in Temple Run by flashing n121 ;)
[Samsung Galaxy Nexus] Bavilo:
Can someone tell me which is better for battery life?

Interactive with generic hot plug or hot plug governor? Has anyone tested it yet?
[Samsung Galaxy Nexus] raubkatze:
Now using interactive governor with generic hotplug.

r133 (512)

1344

729

no uv
[Samsung Galaxy Nexus] ehcan:
My experience is like darkmanx2g, I feels that r130 is smoother (placebo effect because the transition is smoother? i.e.: slower).

Yesterday, the r133 while doing relatively light work at 0 brightness, browing internet, it drops 20% in a matter of 30 minutes. Maybe it was a fluke, I have revert back to the r130 to see if there is any changes.
[Samsung Galaxy Nexus] Tommy_FIN:
Last night my battery drain was only 2% in seven hours. That pretty good, right?

I'm using:

AOKP b31, Franco 133 with 384 gpu, ondemand, generic hotplug, 384min 1228max, smartreflex

Will report back with the screentime later today.
[Samsung Galaxy Nexus] stereoprologic:
AOKP build 31

franco r121 @ 384 GPU

ondemand 384 - 1228 MHz

Generic Hotplug on

SmartReflex on

I love it. :)
[Samsung Galaxy Nexus] LKNim:
I leave franco kernel because it oppose the voodo color:(

http://xdaforums.com/showpost.php?p=24783215&postcount=110
[Samsung Galaxy Nexus] samizad:
I've decided that my phone doesn't like generic hotplug. The battery drain in idle deep sleep seems about double that without hotplug.
[Samsung Galaxy Nexus] raubkatze:
2x? Surprisingly... What ROM and kernel build (384 or 512) do you use?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kin24173493:
Seems that the kernel drain quite a lot battery. I'm on r133 384－1224 ondemand generic hotplug enabled no gpu oc.
[Samsung Galaxy Nexus] RensoreK:
First of all, thank you for taking the time to post some great info. I use AUTO brightness but my levels are custom set to low brightness values myself, except a certain threshold when it goes straight to full. This is because I do work under fluorescent lighting but I wanted it full brightness when I go outside (since I live on a Caribbean island.). I constantly check processes and partial wakelocks using betterbatterystats (support his app if you can {from market} definitely worth it!).

Now the 3G isn't too much of a problem because I have juicedefender to only turn it on for 2 minutes every 30mins. So not even 2G is on when i'm idle, and I still get regular texts (mms have to wait until syncs). I am usually between work/home where I have 3/4 bars minimum in both places (as shown from my mobile network) its usually green all the way through. Going to try and set brightness to 0% one day and see if thats the reason, I JUST flashed Liquid ICS today coming from AOKP. Maybe the more slim lightweight ROM will help some! :D
[Samsung Galaxy Nexus] relax24:
I noticed when I set my minimum to 384mhz, when im looking in setcpu, the frequency is always jumping between 384 and max. When i up the minimum to 784, it stays at 784 and hardly moves. Is this because I'm actually looking at setcpu that its constantly changing, or is it because it actually needs 784mhz?
[Samsung Galaxy Nexus] nspusmc:
Is anybody running this kernel with Revolution HD 3.0? If so, what config do you you prefer?
[Samsung Galaxy Nexus] samizad:
Maybe a bit less than twice.

CM9 with r133 at 512 and On demand governor.
[Samsung Galaxy Nexus] raubkatze:
I'm using CM9 and r133 (512)... but only with interactive governor.

Try. Maybe it helps you.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mrfrag1337:
I think previous nightlys drain less battery than r133 in both ondemand nd interactive governors.

Onscreen time seems lower.
[Samsung Galaxy Nexus] ced8120:
Is anybody have solutions for apply voodoo apk ( http://xdaforums.com/showpost.php?p=24783215&postcount=110 ) with the franco kernel ?
[Samsung Galaxy Nexus] gdmlaz:
So every-1 recommends min cpu set at 729Mhz ? also how do change gpu values ? noob question im using franco app :D
[Samsung Galaxy Nexus] pewpewbangbang:
I'm using 384mhz.....i'm pretty sure it will save more battery as it undervolts lower than 729mhz. But 729mhz may help if you have issues.
[Samsung Galaxy Nexus] gdmlaz:
thanks for the suggestion...... ill switch over to 384mhz see how it behaves lol
[Samsung Galaxy Nexus] relax24:
Try monitoring the cpu whilst your screen is on. Does it jump from 38mhz to your max cpu frequency every half second. Mine does

I'm thinking of setting up a profile in set cpu for 729-max with generic hot plug

Screen off profile = 384 - max

Any guys who know this stuff better than me - Any reason not to do this?
[Samsung Galaxy Nexus] pewpewbangbang:
Yea....now that you mention it, it does go up to 1228mhz every now and then when screen is on. Weird....would definitely cause CPU to drain more.

This is when it's idle too with screen on. It'll go up like 2 seconds for every minute or so. In general, doesn't spike up that much. Right now I have 4 minutes on 384mhz and 18 seconds on 1228.
[Samsung Galaxy Nexus] Stretlow:
I agree, ran r130 and r133 for a few days r121 gives me more screen on time
[Samsung Galaxy Nexus] franciscofranco:
Going back home later today with lots of goodies. App will be puushed to 4.0 and kernel with support for SuperCurio screen apk. ;)
[Samsung Galaxy Nexus] kashix:
OMG can't wait for this one!
[Samsung Galaxy Nexus] leelaa:
Cant wait, may i ask what supercurio screen apk is?
[Samsung Galaxy Nexus] jnr21:
http://xdaforums.com/showpost.php?p=24783215&postcount=110
[Samsung Galaxy Nexus] triStateMindgate:
http://xdaforums.com/showthread.php?t=1504584
[Samsung Galaxy Nexus] vomer:
Just when you think it can't get any better!! Awesome franco :)
[Samsung Galaxy Nexus] Stretlow:
Im still non the wiser :o:o:o
[Samsung Galaxy Nexus] theMaDHakkeR:
I love you! Sorry just sorta came out..
[Samsung Galaxy Nexus] Antob125:
Yea I don't get it either

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] spinkick:
Its a more powerful screen color/gamma adjustment app.

---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------

So is anyone really seeing any power savings from running 300 mhz vs 700? Its kind of nice running at 700 and cant tell much of a difference power wise.
[Samsung Galaxy Nexus] Tommy_FIN:
Gets my vote for next milestone...
[Samsung Galaxy Nexus] raubkatze:
Really I didn't see the large difference.
[Samsung Galaxy Nexus] robto:
;) agree
[Samsung Galaxy Nexus] Schiehallion:
How do you find the time for francofriscky with gal when new goodies coming?
[Samsung Galaxy Nexus] bjames2785:
First of all i know it's kernel not kernal. I just didn't catch the auto correct when it changed. Thank you so much for replying without actually being productive!
[Samsung Galaxy Nexus] franciscofranco:
You have no idea...
[Samsung Galaxy Nexus] olivercervera:
Hi Franco, where I can read the changes of the latest nightly?

I'm using the Milestone2, but i'd like to try the last nighty.. :p
[Samsung Galaxy Nexus] franciscofranco:
From my app or from the ftp. I dont have access to the direct link now, on the train home.
[Samsung Galaxy Nexus] Langduscher:
Since r133 I get A LOT of "prx_wake_lock" under kernel wakelocks in BetterBatteryStats and it's eating battery .. I cannot find any intel on this particular wakelock :confused:

Does anyone know what it is and how I can stop it?

(More infos on my device in my sig - kernel is the 512mhz one)
[Samsung Galaxy Nexus] leelaa:
Safe travel franco
[Samsung Galaxy Nexus] leelaa:
I dont know, i would google it myself, iam pretty sure someone else in the world has had it. :)
[Samsung Galaxy Nexus] Langduscher:
Thanks for replying :) but before posting here I tried Google already with no luck
[Samsung Galaxy Nexus] leelaa:
Iam not sure if i quite understand, are we expecting a new kernel and an app update tonight, or just an app update?
[Samsung Galaxy Nexus] M7amad90:
Ok, so i am going to ask a Noob question :)

1- can i flash any kernal or this kernal on my Gnex if i am running a stock 4.0.4 ICS ?

2- Will i have problems like having different file systems ( EFS , EXT etc ) so i won't be able to flash the stock room back again! ??

3- how can i revert back to the stock kernal ( just in case ) ??
[Samsung Galaxy Nexus] sishgupta:
Do you have a proxy Configured?

Prx is usually short for proxy
[Samsung Galaxy Nexus] nklenchik:
Idk if this was just a fluke thing but I went to bed with 35 percent battery and work up 4 hours later with 33, not bad.

Then after that I woke up 4 more hours later with 22. Weird right?
[Samsung Galaxy Nexus] pewpewbangbang:
Nah, standby has been kinda weird. Not as good IMO, but I can still knock out 5+ hours of screen time throughout my day before needing to put it on a charger.

Might go back to r121 and try the new Gummy 1.0 build out with it

Just flashed the new Slim ICS 3.3 with r133 and it's been performing good so far. Wi-fi seems more stable now compared to the norm, but time will tell for that as wi-fi has been kinda wonky on the Galaxy Nexus.
[Samsung Galaxy Nexus] isinisterx:
I'm back on r121 I didn't like 133 that much... Screen on time wasn't as good
[Samsung Galaxy Nexus] spaceman860:
Francisco my battery just won't die :D

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] nklenchik:
Do you see a difference performance wise? Think I may head back there
[Samsung Galaxy Nexus] nikulogical:
r121 is the new 13.1
[Samsung Galaxy Nexus] drawde40599:
I went back to 121 few days ago, agree its better than 130's, 133 is best for battery but 121 just feels smoother/ cleaner. (Yes to me even after upping voltage per franco
[Samsung Galaxy Nexus] isinisterx:
I agree I feel 121 much smoother. Almost like a new milestone and I find the battery to be better
[Samsung Galaxy Nexus] zok-star:
same as above! I find r121 a little smoother!
[Samsung Galaxy Nexus] franciscofranco:
If r121 is that good I can revert everything back to it, no problem :)
[Samsung Galaxy Nexus] nklenchik:
Idk I feel like r133 was smoother (only slightly) but r121 maybe has better battery life? I have to give it another couple of days to fully test
[Samsung Galaxy Nexus] pewpewbangbang:
honestly, they all feel smooth. I think I got better battery life on R121 though
[Samsung Galaxy Nexus] nikulogical:
The only thing better on r133 over r121 was benchmarks for me.

Battery life went down, caused problems with gaming, smoothness or fluidity was the same.
[Samsung Galaxy Nexus] Antob125:
Franco didn't you say 121 was based off 4.0.3 and since most of us are on 4.0.4 now that kernel wouldn't do much for us?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Antob125:
Off topic. Weird question but how does everyone exit apps? I usually hit the return key till I get to home screen cause I was used to doing that on my Blackberry and DroidX. If I hit the home button will it jeep stuff open and kill the battery? Cause I kinda just want to hit the home button Cause sometimes when I hit the return let repeatedly it kills app since I have the ROM set to kill apps holding return key. Any insight would be helpful.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] FC1032:
Also a fan of 121 and 130.

There is nothing wrong with 133, just that those two were better (130 battery life was impressive, after lots of backups, reboots there was minimal drain, 121 had good performance and was ok with battery life.)
[Samsung Galaxy Nexus] franciscofranco:
No, r121 is 4.0.4.
[Samsung Galaxy Nexus] raubkatze:
Many men, many minds. So many factors: individual usage, cellular network kind, battery health etc etc.

For me r121 was better with ondemand and r133 is better with interactive. I don't like r123 and r130 for the less standby battery life... But it's only my mind and only on my experience.
[Samsung Galaxy Nexus] theMaDHakkeR:
Just hit the home key and then clear any apps your not using by swiping them off with the multitasker. ICS will just store them in cache and free up your ram.

This is also more for the Q&A section.

Just sayin.. @p
[Samsung Galaxy Nexus] franciscofranco:
We'll see. I'll stay in this path for a few more releases, but the patch window is decreasing, I'm mostly applying fixes and small bug patches, we'll see what happens.
[Samsung Galaxy Nexus] BryanChung:
Oh no. :( I update to the latest 133 on b31 and this was what I got (as attached). The screen is like messed up. After a while my phone will hang too.

I did a clean wipe then after that flash b31 again (without 133), it was fine. Until again I flash 133 then got this problem. Not usable for me. :(

Any idea why?
[Samsung Galaxy Nexus] pewpewbangbang:
Your phone might not be able to handle the low GPU voltage......franco lowered them I believe

flash 384mhz or do the fix, you can search the thread for the temporary fix
[Samsung Galaxy Nexus] raubkatze:
Yes we'll see as we'll test it again and again) I like your kernel as it's a great work and I can wait for the best results.
[Samsung Galaxy Nexus] BryanChung:
Oh I see. Sorry I was away from computer for a week so coming back, I quickly flash it and did not read the threads. Guess I'll just go back to 130 for now.

Thanks for quick reply.
[Samsung Galaxy Nexus] kashix:
Artifact bro. You flashed the 512 version? Just simply revert to the 384 version and your problem will clear up or simply apply the tweak to the voltages by franco posted back in the thread here.
[Samsung Galaxy Nexus] BryanChung:
I went back 10 pages and still did not see the tweak. I'm way off the updates now after a week without computer. Ha.
[Samsung Galaxy Nexus] raubkatze:
Here is the fix - http://xdaforums.com/showpost.php?p=24715288&postcount=11948
[Samsung Galaxy Nexus] kashix:
I can't stop laughing about your avatar and mine :P
[Samsung Galaxy Nexus] BryanChung:
So I use a command prompt or in Recovery to do

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

?

---------- Post added at 09:38 AM ---------- Previous post was at 09:38 AM ----------

Yours cuter :D
[Samsung Galaxy Nexus] raubkatze:
Using terminal or edit file using root explorer eg.
[Samsung Galaxy Nexus] BryanChung:
ok thank you... :) but i'm afraid my phone cannot even last that few minutes to edit those lines. Ha. :D
[Samsung Galaxy Nexus] CaspaTheGhost:
Not the best of days for me battery wise, was testing out Interactive and got about 3hrs screen on time. Gonna try again tomorrow and then back to Ondemand Sunday.

Unless we have goodies from Franco that is! :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] borneanheadhunter:
Any body experienced tears during vertical scrolling in pulse app with franco kernel 133? I tried the kernel with Liquid (makes the rom very lag during screen transitions), BAMF (white pixel spots all over the screen) and tear as mentioned on top when applied with AOKP build 31.
[Samsung Galaxy Nexus] franciscofranco:
Thats been discussed for the last 100 thousand pages ;)
[Samsung Galaxy Nexus] borneanheadhunter:
Thanks Franco. Will look it up. :D
[Samsung Galaxy Nexus] franciscofranco:
Will be fixed on next release though. Just finishing coding the app now, I found some bugs, shouldn't take too long to squash them ;)
[Samsung Galaxy Nexus] spinkick:
One might say its an artifact of this huge thread
[Samsung Galaxy Nexus] nklenchik:
Ohhhhhhhh snappp
[Samsung Galaxy Nexus] spinkick:
hahahaha
[Samsung Galaxy Nexus] heo_con184:
I finally got back to r12 - 512mhz GPU while waiting Franco to put his magic in the next release.

Thanks for your hard work. And your app's getting better and better.
[Samsung Galaxy Nexus] franciscofranco:
#4.0

* New root check system triggered every time the app is opened

* New IVA and CORE voltage interface specially built to work with both Milestone and Nightly releases - this values WON'T be set on boot for security purposes. You'll thank me later

* New BLX setting - the default is 96 just like in the Kernel. The value will stick on reboot

* Changelogs are scrollable again

* GAMMA EditTextPreferences open the numeric keyboard by default

* General fixes and improvements all across the app
[Samsung Galaxy Nexus] mazubo:
Updated app doesn't show in market.... did I jump the gun?

:-D