yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Bavilo:
Seems like #999 doesn't want to deep sleep.

Anyone having the same problem?
[Samsung Galaxy Nexus] beama:
No problems, great performance good battery life.

And the app get updated and does now save the color values

All good :D

sent from my liquid smooth Galaxy
[Samsung Galaxy Nexus] Timmyfoxeh:
Not me, CPU spy reporting 12½ hours of deep sleep out of 17 total. Sounds quite accurate to my usage pattern the last 2 days.
[Samsung Galaxy Nexus] rmcsc:
I have to say that on my device it's quite the contrary. 999 has deep slept like it never did on 158 or 157 before it.
[Samsung Galaxy Nexus] jnr21:
Install BetterBatteryStats and check if there's any wakelocks.
[Samsung Galaxy Nexus] Stretlow:
did someone say you can get the #999 test kernel on franco's G+ page?
[Samsung Galaxy Nexus] cchant:
I'm suddenly getting a lot of data drops on #999

Everything is as shipped. No voltage change sr on hot plug off. Full power profile

http://pastebin.com/p72vEPqk
[Samsung Galaxy Nexus] rmcsc:
Well, he did.
[Samsung Galaxy Nexus] Stretlow:
:) is it the blind test file on there?
[Samsung Galaxy Nexus] rmcsc:
Yes, that's the one. That magical file that makes your phone ooze coolness.
[Samsung Galaxy Nexus] Stretlow:
Im not a complete dunce with this stuff but im also no expert but im presuming thats a file you flash in Fastboot and not in CMW and the reason Franco's dont that is to deter people from messing their phone up?
[Samsung Galaxy Nexus] jnr21:
cwm zip: http://db.tt/0y27u4p6
[Samsung Galaxy Nexus] drawde40599:
999

999, Using few days now at 100% stock Franco settings ( full power setting ) No UV /OC, I have no heat issues haven't seen it get over 52°c ( fanco app) getting 4 + hours screen on time with 70% bright, GPS, data, Gmail sync all on, stock battery , games working perfect, its fast 100% stable, no.data drops, no.reboots no SoD No issues at all!! Running liquid 1.35 rom and 4.0.4 current factory radio and bootloader ( Google image )

Thank u!!
[Samsung Galaxy Nexus] kkazakov:
Bluetooth mouse

I'm having problem with a bluetooth mouse and this kernel ... mouse does not show up and does not work at all :(

I've tried Imoseyon's kernel, and the mouse pointer works there flawlessly. The only problem I have with his kernel is the battery.

Imoseyon 3.4.0-exp4-230 kernel:

D/BluetoothEventLoop( 220): Device property changed: 11:81:02:90:25:B4 property: Connected value: true
I/BluetoothEventLoop.cpp( 220): agent_event_filter: Received method org.bluez.Agent:Authorize
I/BluetoothEventLoop( 220): First check pass for incoming HID connection from 11:81:02:90:25:B4
D/BluetoothEventLoop( 220): onAgentAuthorize(/org/bluez/299/hci0/dev_11_81_02_90_25_B4, 00001124-0000-1000-8000-00805f9b34fb) = true
I/BluetoothDeviceProfileState( 220): handleIncomingConnection:6:true
D/BluetoothService( 220): allowIncomingProfileConnect: 11:81:02:90:25:B4 : true : 33074008
D/EventHub( 220): No input device configuration file found for device 'Bluetooth Mouse'.
I/EventHub( 220): New device: id=7, fd=233, path='/dev/input/event6', name='Bluetooth Mouse', classes=0x80000008, configuration='', keyLayout='', keyCharacterMap='', builtinKeyboard=false
D/BluetoothEventLoop( 220): Input Device : Name of Property is: Connected
I/InputReader( 220): Device added: id=7, name='Bluetooth Mouse', sources=0x00002002
D/BluetoothInputProfileHandler( 220): InputDevice state : device: 11:81:02:90:25:B4 State:0->2
D/BluetoothService( 220): CONNECTION_STATE_CHANGE: 11:81:02:90:25:B4: 0 -> 2
V/BluetoothEventManager( 4328): Received android.bluetooth.input.profile.action.CONNECTION_STATE_CHANGED
D/CachedBluetoothDevice( 4328): onProfileStateChanged: profile HID newProfileState 2
I/BluetoothDeviceProfileState( 220): Entering ACL Connected state with: 102

Franco r152:

D/BluetoothEventLoop( 223): Device property changed: 11:81:02:90:25:B4 property: Connected value: true
I/BluetoothEventLoop.cpp( 223): agent_event_filter: Received method org.bluez.Agent:Authorize
I/BluetoothEventLoop( 223): First check pass for incoming HID connection from 11:81:02:90:25:B4
I/BluetoothDeviceProfileState( 223): handleIncomingConnection:6:true
D/BluetoothService( 223): allowIncomingProfileConnect: 11:81:02:90:25:B4 : true : 3077416
D/BluetoothEventLoop( 223): onAgentAuthorize(/org/bluez/324/hci0/dev_11_81_02_90_25_B4, 00001124-0000-1000-8000-00805f9b34fb) = true
D/BluetoothEventLoop( 223): Input Device : Name of Property is: Connected
D/BluetoothInputProfileHandler( 223): InputDevice state : device: 11:81:02:90:25:B4 State:0->2
D/BluetoothService( 223): CONNECTION_STATE_CHANGE: 11:81:02:90:25:B4: 0 -> 2
I/BluetoothDeviceProfileState( 223): Entering ACL Connected state with: 102

Same happens with a bluetooth keyboard. Works on Imoseyon, doesn't on Franco's kernel.

It also happens with the latest franco kernel. I'm on AOKP Milestone 5, but it was the same on previous AOKP versions ...
[Samsung Galaxy Nexus] rmcsc:
You sure you've not read this thread already? That's precisely the reason. :p
[Samsung Galaxy Nexus] Theshawty:
I know this isn't kernel related, but Franco, could you please overlook your app? With the latest version, downloading is dead. :/
[Samsung Galaxy Nexus] franciscofranco:
I'll take a look thanks.

Yep, I know the reason. Will fix it.

It works fine, I just tried downloading every version and its fine.
[Samsung Galaxy Nexus] Bavilo:
I just tested r158 again, After 10 seconds of screen off it goes straight into deep sleep.

on #999 it was still stuck on 384mhz even after 2 hours of screen off....
[Samsung Galaxy Nexus] jhericurls:
I have a weird problem with #999, google play didn't work, keep saying no data connection, yet everything else works ie browsed, emails. Reflashed 158 and is working fine again.
[Samsung Galaxy Nexus] nodstuff:
I just did your test on 999 and for 10 seconds screen off (roughly, I counted) I got 10 seconds of deep sleep.

I reset timers in CPU spy too to be sure of good results.

So your set up is the problem, check wakelocks etc.
[Samsung Galaxy Nexus] Bavilo:
im sure there are no wakelocks...I just tried the 2 kernels, I didn't change anything else :(
[Samsung Galaxy Nexus] nodstuff:
Flash it and boot then reboot it again.

See if that works.
[Samsung Galaxy Nexus] CaspaTheGhost:
Did you wipe cache and davlik?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
The kernel doesn't touch connection to Google's server.
[Samsung Galaxy Nexus] Timmyfoxeh:
I believe that's an issue with Android 4.0.4 (or possibly the radio firmware) rebooting the phone should be all you need to do to solve it.

Also, if I may ask Franco, where are you planning to reveal the secret behind r999? I remember you said you'll give it another day and that was last night.
[Samsung Galaxy Nexus] franciscofranco:
After my dinner, which should be in about 1h or something.
[Samsung Galaxy Nexus] nklenchik:
What time is it over there? Right here in NY it's 16:22
[Samsung Galaxy Nexus] franciscofranco:
Yep, its 5h difference. It's 21:23 here.
[Samsung Galaxy Nexus] hotnikkelz:
Ok bought the app. What exactly am I looking for? I don't know what wake lock is about :-D
[Samsung Galaxy Nexus] Stretlow:
Colours still not sticking for me :(
[Samsung Galaxy Nexus] CaspaTheGhost:
So, full day at work today and r999 has done the business!

View attachment 1061074

You can see I had some really dodgy service at the gym and it still held up.

View attachment 1061072

Over 3hrs is impressive as I normally test at the weekend when I'm on wifi for the vast majority of the time.

Usual setup for me, so interactive, 729/1344, SR on.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm currently at 15% battery with around 1.5 hours screen on and 5.5 on battery. All 3g. No huge wake locks but audioout_1 or something similar is giving me like 14 mins of wake lock. Any ideas?
[Samsung Galaxy Nexus] dpaine88:
Exactly the same here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
Audio out wakelock is exactly what it sounds like, any sound made by the phone: screen lock sounds, touch sounds, dial pad sounds, notifications, ringtones, music playing, videos, YouTube etc.

Any sound whatsoever!

So hopefully that has explained that! :)
[Samsung Galaxy Nexus] neopeek:
Hi Franco,

would it be possible to tweak WiFi via your kernel? I know you really care about battery life but if you know some way to increase WiFi signal strength a lil' bit I would like to ask you to do so, plz.

Thx in advance.
[Samsung Galaxy Nexus] nodstuff:
You can do that in his app.
[Samsung Galaxy Nexus] franciscofranco:
Tweak Wi-Fi what? I already added a toggle for PM_Fast and PM_Max, theres not much more I can do. If you want more Wi-Fi signal get closer to the router.
[Samsung Galaxy Nexus] Gahh Its Lee:
Well I have basically every sound except for keyboard on... Although I've never had that wake lock before.
[Samsung Galaxy Nexus] Langduscher:
THE best was r156-384 so far - #999 is slightly better.

999 being mostly better on 3G - wifi can't be beaten I guess.

Can't wait for the changelog :D and more nighly/ test builds. Your kernels make the most impact to my Gnex - and it only keeps better & better.

Cheers - I'm drinking one to your health young man! Have a good one :) thanks for all ur time!
[Samsung Galaxy Nexus] darrendm:
Getting signal drops with #999 and Imoseyons 3.6.0 (Don't remember if present with 158). Must be something to do with the lowest frequency. I'll try min on 700 and see how things turn out.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I'll be dropping a proper nightly in a few hours (just for numbering sake), but the changelog for r999 is pretty surprising:

* sched: Fix nohz load accounting -- again! - from 3.0.31

* OMAP4: Workaround the OCP synchronisation issue with 32K synctimer. - reintroduced (I reverted it in r158)

* 10 OMAP4 patches that were merged in android-omap-3.0

* usb: musb: handle nuked ep dma interrupt

* cpufreq: interactive: restart above_hispeed_delay at each hispeed load

* cpufreq: interactive: fixup trace of string params

* tuna-wifi: do not randomize MAC if bootloader doesn't pass it - patch from imoseyon

* LMK pushed to 3.4 kernel version. Picked from Fugumod repository.

* board-tuna.c: VAUX3 and VUSIM voltage increase a little bit to get rid of dmesg error logs

* RCU Boost enabled again

So as you can see I did nothing besides applying 3rd party patches, so all the credits go to Texas Instruments team and Google engineers. The OMAP patches just prove that most of the feedback that I get is just poor testing or just random **** pulled out from the ass (this is refering to when I had tons of OMAP4 patches and some people complained about bad battery life, high temperature or something they decided that was broken). I had these patches before. This r999 (soon to be official r160) is probably going to be Milestone 4.
[Samsung Galaxy Nexus] thegtfusion:
holy **** man!! thiss thread got nearlyy 2million views!!

good job franco!!, I will be running this kernel when I get my GN :D
[Samsung Galaxy Nexus] hotnikkelz:
Bought the app now what? I have no idea what the wake lock gibberish is about

@franco

You thanked my post but it wasn't directed at you lol. I got your app ages ago when I started using your kernel. This was for a batterystats app someone told me to get cuz I cannot understand how so many people are getting great idle battery time while I cannot :-)
[Samsung Galaxy Nexus] dwang:
Was r999 512gpu or 384gpu? It felt like 512gpu even though it said 384gpu.
[Samsung Galaxy Nexus] franciscofranco:
384GPU just like its written in the kernel version string.
[Samsung Galaxy Nexus] dpaine88:
Hahaha too funny...its crazy how much of this kernel stuff can just be in our heads

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Mabey, but I don't no what any of that $@#& is or what it means, any data / feedback I have given is from 100% experience using the phone, only issue I've ever had was heat and it was 100% real I could feel and see it in your app, 999 as been nothing but perfect,so something is different.

Anyways great kernel glad its working right thank u!!
[Samsung Galaxy Nexus] dwang:
Interesting, nenamark2 gave me 31.5fps on r999.

Thats what I got with the 512gpu in your previous releases.

Eager to try out 512gpu with these new changes and see if nenamark2 gives even better numbers.
[Samsung Galaxy Nexus] franciscofranco:
Oh no, it's 512GPU... I was convinced it was 384GPU. Anyway even better, people reporting awesome results with 512GPU is ironic. Ihihihi

I'm still laughing sitting in front of my computer...I thought r999 was 384GPU... or maybe I did it on purpose...we'll never know.
[Samsung Galaxy Nexus] dwang:
Ok.. yeah I can definitely notice the performance diff between 384gpu and 512gpu and r999 really did feel like 512gpu.

Glad you confirmed it.
[Samsung Galaxy Nexus] nklenchik:
Can't for r160 with a 512 gpu :D
[Samsung Galaxy Nexus] nodstuff:
512mhz gpu but it said 384mhz in the kernel name in settings.....

We underestimated the sneakiness...... :D

Why the hell is my phone so weird??!?! So nightlies work on my phone with 512 and others just give me artifacts e.g. r156 512mhz worked and r158 512mhz didn't.

Voltage changes??

It has me discombobulated.....
[Samsung Galaxy Nexus] rmcsc:
Holy sheep. No wonder the phone felt so smooth. Not that 384 isn't smooth, don't get me wrong.

999 has been incredible, Franco. I'm glad you've found another step for a milestone.
[Samsung Galaxy Nexus] chlehqls:
Power of placebo and deceit helps build awesome kernels.

True story. :]
[Samsung Galaxy Nexus] leelaa:
Franco i am a bit lost, are you saying that r999 will be the next nightly with no changes?

Edit: cancel that question, i know now.
[Samsung Galaxy Nexus] rmcsc:
It has changes. He just posted the list.
[Samsung Galaxy Nexus] republitarian:
Color multipliers still resetting upon reboot. Another thing I noticed is my frequencies are being reset as well every reboot.

Any help will be greatly appreciated. I tried removing the franco updater in its entirety and reinstalled it but still to no avail.
[Samsung Galaxy Nexus] dpaine88:
I think he was talking about additional changes before r160

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
r999 will be official r160 with 0 changes, just a rename for official release.
[Samsung Galaxy Nexus] franciscofranco:
I'll take another look, but it works for me.
[Samsung Galaxy Nexus] The Gingerbread Man:
Cheers, just rebooted and had to set them up again. Using 999

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] republitarian:
weird it seems 4.7 has fixed the problem for some people but for some others it hasn't.

Update: Okay about the frequencies and governor resetting upon boot, IF i choose a power profile and alter any of its settings it WILL keep them upon boot. However if choose "None" and create my own settings it resets them every time to 384-1228 ondemand...

Color multipliers still a problem for me even whether I choose power profile or not.

running aokp build 35 / 384 nightly(158) on my i9250
[Samsung Galaxy Nexus] nodstuff:
5 hours screen on today, not bad! :)

1344/729 ondemand

95% up threshold

20000 polling time

Wifi on, data off, sync on and off during the day.

Uv'd on mpu, iva and core.

#999

It just gets better and better!! Thanks Francisco!
[Samsung Galaxy Nexus] AdamZA:
I knew I wasn't going crazy when I thought it was 512 mhz GPU :P It's a shame though because I was hoping that it was actually the 384 mhz GPU version so I could look forward to the phone running so smoothly!

Maybe I should swap Nexus's with someone :P
[Samsung Galaxy Nexus] patass:
With today's app update im getting ridiculous battery drain, and my phone that has been stable for days crashed once. I'm currently on milestone 3, and will be flashing the latest nightly after I post this. Yesterday I went 14 hours and was at 32%, today I went 7 and was at 10%. Sameish usage.
[Samsung Galaxy Nexus] jcmm11:
What about the tether/dhcp problem I found? It's definitely the kernel since reverting to 158 fixes it. And I haven't run into a problem on any of your previous kernels.
[Samsung Galaxy Nexus] Dr Byte:
What I forgot to mention on this post was a couple of other "patches" I had in mind, also targeting better long-term battery life (ie wear):

Firstly, to have an option to disable charging above x% - so if you "have" to dock your phone at 93% charged, it won't push the battery chemistry with the initial high-current surge. Li Ion batteries shouldn't be fast-charged below 40% nor above 90%.

Secondly, to force a slow charge and/or disable charging entirely (which dove-tails with the 100% charge-hold from the original suggestion). Your kernel has a way to "force" a fast charge (at the maximum rate supported by the input current, anyway) but a long, slow charge is the best for longevity.

Since I charge the phone while I sleep, a "long, slow charge" is my preferred choice. I've only looked briefly at your drivers, but I haven't yet seen how the "FAST" option is enabled - I know there's an extra module involved (to set the flag), but don't see (yet) how the two communicate. Haven't seen how BLX ties in either.

In my "ideal" driver, unless you "force" FAST mode, it would limit the charging current at <40% and >90%, and not even start until it drops below 90%.

All of this is moot, if the hardware is too 'dumb' to implement it :( I had this all mapped out to add to the CM7/ManU kernel a few months ago, but never quite sat down to do it before ICS and the GN caught my attention some months back. Then my hardware buttons started glitching...

Here's hoping they perfect and commoditise the LiFeSi battery quickly - much faster charging, much higher capacity in the same volume... and it may even make Electric Cars viable... and a phone you can charge in minutes that lasts all week :).
[Samsung Galaxy Nexus] Emilius:
Nice work man. Looking forward to test this baby :)

BTW I know you are not pulling random **** out from that place but if you can make my phone last forever like with r121... oooh man, this is now really killing me. I try all ROMs possible to install on GN but always the same. r121 amazing, anything newer 3 times quicker battery drain. WTH is going on here. Is it my phone or something? Just look at this shoots (r121)... Get it? Just amazing results. Sure, my next move is to test r160 soon is out.
[Samsung Galaxy Nexus] rmcsc:
ONE hour of screen time for three days of use? Jeez, use your phones, people! You pay a monthly bill for them. :screwy:

Hey Franco, that Power Save mode is amazing. Thanks for that.
[Samsung Galaxy Nexus] Emilius:
Well, for surfing I use 27" screen LOL. That is my normal use of the phone. Music, calls, msg, G+ etc.
[Samsung Galaxy Nexus] SupWiz17:
Its nice to know that I can use the 512mhz gpu kernels now. I was never able to before or the 460mhz kernels either but I was using r999 perfectly. I only noticed artifacts during the boot animation and it was very minor. I hope it runs the same as r160 or maybe franco tricked my phone too :confused:
[Samsung Galaxy Nexus] monkey hung:
I think 158 is the best kernel you have made. Better than M3 which no one should be on right now because this is better.
[Samsung Galaxy Nexus] nklenchik:
Sync off? Eh...haha

r999 is 384mhz, not 512
[Samsung Galaxy Nexus] nodstuff:
Francisco said that it is 512mhz.
[Samsung Galaxy Nexus] republitarian:
Franco was mistaken it is 512 read a page or two back
[Samsung Galaxy Nexus] nklenchik:
Weird... Does it say 384 if you look in your settings?
[Samsung Galaxy Nexus] loudaccord:
I plan on using as is... left the gov to 'on demand' also. I have Set CPU but didn't change anything.
[Samsung Galaxy Nexus] marc.tulley:
I got 6542 with APEX 1.35ghz kernal but Francisco's kernal has far more useful advantages

Just about to flash #7 Franco, looking forward to it! This was the most eagerly awaited because of the uber power saving teasers you've been planting!

Keep it up mate
[Samsung Galaxy Nexus] Lobo13:
Hi,

your kernel looks great. Can I flash it on MCR lr8?
[Samsung Galaxy Nexus] razzbaronz:
Should we flash back to 6? I'm happy without CIFS for now as long as battery is great.
[Samsung Galaxy Nexus] franciscofranco:
No. I just flashed something without CIFS. Everything was fine until I compiled this released kernel with CIFS. If I get enough evidence it was caused by CIFS I'll update this today. Just gotta be sure that it was caused by this cifs ****.
[Samsung Galaxy Nexus] razzbaronz:
As far as I know this will work on any ROM based on 4.0.3, which that one seems to be. Maybe someone else can give you a definitive answer.
[Samsung Galaxy Nexus] sefirosu0522:
I did and it worked. Thank you.
[Samsung Galaxy Nexus] jhericurls:
MCR Ir8 runs 4.0.3 Kernels no problem.
[Samsung Galaxy Nexus] sefirosu0522:
Ok I just flashed this and it worked. What should I do next? Sorry I'm a total noob when it comes to this. Is there settings you can change on this or just let it run as is?
[Samsung Galaxy Nexus] luffyp:
Does the stock kernel have CIFS? If not, it's not much of a loss I'd say.
[Samsung Galaxy Nexus] sefirosu0522:
Ever since I flashed this my computer won't recognize my phone. Any ideas?
[Samsung Galaxy Nexus] inffy:
Noticed this too. Using OS X and the file transfer app from Google doesn't recognize my phone
[Samsung Galaxy Nexus] yyz71:
Hey franco the kernel seems to disable connection from phone to pc!! any ideas?
[Samsung Galaxy Nexus] sefirosu0522:
I hope this gets fixed soon. I'm glad it's not just me.
[Samsung Galaxy Nexus] franciscofranco:
It does? Give me a sec.

Yes my fault, sorry. Build up in a few, I just gotta make sure the drain is caused by this cifs ****.
[Samsung Galaxy Nexus] sefirosu0522:
Thanks for the quick reply!
[Samsung Galaxy Nexus] Andrmgic:
It's not broken.. it just unchecks MTP for some reason.

Go into settings>storgage>usb computer connection and check off MTP.
[Samsung Galaxy Nexus] loudaccord:
Franco, you're one of the most responsive developers out there, much appreciated.
[Samsung Galaxy Nexus] Redflea:
So can't tell...has build 7 been updated to resolve the CIFS drain and pc connect issues?

Loving this kernel, excellent performance and best battery life I've had.
[Samsung Galaxy Nexus] yyz71:
Just enable MTP in settings and your good to go even do a reboot and it wont auto disable...
[Samsung Galaxy Nexus] nodstuff:
Ya but he said that was mistake, or intentional, its mystery.

All we know for sure is that he said it was 512mhz.
[Samsung Galaxy Nexus] jericho7:
r999 is definetly 512mhz due to the artifacts I get lol. Interestingly enough, I can actually use this kernel since I only experience artifacts during games and benchmark, before that my phone would show massive artifacts everywhere and wouldn't make it past 10-15 secs after the bootscreen before rebooting
[Samsung Galaxy Nexus] nklenchik:
Oooh okay so there's no point in me updating to r160 then (technically speaking) :P
[Samsung Galaxy Nexus] SupWiz17:
Thats exactly how my phone would act on a 512mhz kernel. The screen would be breaking up and covered in artifacts no matter what I did and I couldnt get rid of it. Now though its completely different and definitely usable which is very nice.
[Samsung Galaxy Nexus] rmcsc:
If I understood right, r999 = r160.
[Samsung Galaxy Nexus] Emilius:
Franco can you add option to go back and install older versions of your kernel to your app?
[Samsung Galaxy Nexus] bongostl:
I did notice that the phone ran hotter than on 158...battery didn't seem different
[Samsung Galaxy Nexus] drawde40599:
On 999? I cant get it to go over 48°c ( Franco app) no matter what i do, the latest 4.0.4 stock android kernel / rom don't even run this cool ( every phone different I guess
[Samsung Galaxy Nexus] isinisterx:
I'm on r158 and I'm loving it. Battery life is amazing. Thanks
[Samsung Galaxy Nexus] BrUhNiGGs:
Wait I'm confused...people are saying that 999 is 512mhz gpu when in about phone it says 384mhz gpu
[Samsung Galaxy Nexus] Neejay:
Just found it myself.
[Samsung Galaxy Nexus] drawde40599:
Its 512 read back few pages Franco said he thought 384 labled wrong its 512
[Samsung Galaxy Nexus] SNaReX:
What is the different between 384 and 512? Which one is better for less battery drain?