yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] shawnaye:
Haha, love the idea of the updater, but honestly, i check XDA so oftenly that i don't even need an updater app to remind me!
[Samsung Galaxy Nexus] boype:
Thanks for mentioning that. I'll see if I did something wrong somewhere.

Meanwhile, a manual reboot has the same effect :)
[Samsung Galaxy Nexus] standa75:
No unexpected reboot on slim beta 2 too.:)
[Samsung Galaxy Nexus] chikimonke:
So does this mean we should give it a reboot of our own after the initial boot?
[Samsung Galaxy Nexus] FutureGamerz:
Wow... Just updated to R39.

Wipe Cache -> Flash -> Wipe again

The problem is... Why it boots up so fasttttttt??????

For my phone, it normally takes a couple of mins at 'X' logo before it gets into "Android is upgrading". It takes only 1/2 mins this time.

Normal?
[Samsung Galaxy Nexus] ronald_loulan:
Im having the same thing too...

I think Boype did something to reduce the bootup speed?? :victory:
[Samsung Galaxy Nexus] zeppelinrox:
What exactly is different in the memory management in 4.3?
[Samsung Galaxy Nexus] MBQ_:
*a wild zep appears*
[Samsung Galaxy Nexus] safendi:
Why with all fancy kernel i have a lag when i open gallery?
[Samsung Galaxy Nexus] MBQ_:
This literally helps nobody dude.

For all we know, you could be using a super conservative governor underclocking it to the max or something
[Samsung Galaxy Nexus] safendi:
I use the default setting but the max freq is 1350. I use rasbean 4.3
[Samsung Galaxy Nexus] siealex:
Try to undervolt at least 75 mV at high frequencies, this will reduce thermal throttling.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] wasdf:
Ahh.. I want to ask a problem about thermal throttling, I can only set up to 80oC with Twister Mod. However i want to set it to 90oC instead, if I use init.d script to set it it will override by Twister Mod after boot in to system, do you know how can i set it correctly?
[Samsung Galaxy Nexus] Prasad:
I'm having some lag issues while gaming... For example, in iron man 3, the accelerometer and screen refuse to promptly take input at times and I lose. Any advice? r39, stock settings.

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] wasdf:
Hi, Did you changed the compassion of boot.img? I can't unpack it with Android Image Kitchen by osm0sis but I can unpack it till r38,

Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: boot.img

Setting up work folders . . .

Splitting image to "/split_img/" . . .

BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE 80000000
BOARD_PAGE_SIZE 2048
BOARD_RAMDISK_ADDR 81000000

Unpacking ramdisk to "/ramdisk/" . . .

Compression used: ERROR

Done!

for some reason I need a secure boot image. Can you provide a version which with ro.secure=1 ro.debuggable=0 persist.service.adb.enable=0 ? Big thanks :good:
[Samsung Galaxy Nexus] okanb3:
I don't know why you need to unpack the kernel but i suggest you to build from source. It's the easier way for me
[Samsung Galaxy Nexus] wasdf:
I don't know how to build it from source lol Nevermind, I done it with dsixda Kitchen. Actually do I have to wipe cache and dalvik cache if I update from r38?
[Samsung Galaxy Nexus] zeppelinrox:
So is your next post gonna say how you didn't have that problem on 4.2.2 when it was SuperCharged?

Yes, I'm having a laugh at your expense.

heh

ha... it's fun seeing people put their foot in their mouth tho.
[Samsung Galaxy Nexus] paarthdesai:
relax ;) why this sudden appearance and getting on a single user?

:o
[Samsung Galaxy Nexus] infectedorganism:
Would those of us still on 4.2.2 benefit from the updated SIOplus tunables?
[Samsung Galaxy Nexus] shawnaye:
Well, seeing that he probably won't release anymore 4.2.2 kernels.

I would say, no, you won't benefit.

Flash 4.3 and enjoy.

Every kernel moves forward. Haha.
[Samsung Galaxy Nexus] stevensoaj:
I believe he was asking if he would benefit from inputting the new tuneables manually via trickster etc into a 4.2.2 version of fancy.
[Samsung Galaxy Nexus] infectedorganism:
I will move to 4.3 eventually. I was referring to this commit referenced in the most recent changelog:

https://github.com/boype/kernel_tuna_jb43/commit/7b061b72bb442d0f1fdaac1a0b18c314409cc3ac

Those values can be changed via TricksterMOD. I just wasn't sure if those changes were tuned for 4.3 specifically, or they were just better in a universal sense.
[Samsung Galaxy Nexus] motorazrv3:
Too bad that fancy for 4.2.2 has reached its eol.

Now I have to find a good new 4.3 rom.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] chikimonke:
I'm currently running Slim and had CM before, both treated me well. I like the options in Slim personally though.
[Samsung Galaxy Nexus] Prasad:
Yeah, that's a great sense of humor! SuperCharger made gaming impossible, but was most essential on low free RAM ROMs at the time.

Ontopic: r39 prevented my phone from waking up from deep sleep... Battery pull was required.

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] kaiyoto123:
the performance drops on r39 only get 26 fps on nenamark 2
[Samsung Galaxy Nexus] MBQ_:
http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/

---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------

Benchmarks dont mean shhhhh
[Samsung Galaxy Nexus] :
Great kernel.. Thanks for update ...

Benchmarks doesn't mean nothing... Fancy makes my gnex fly! ;)
[Samsung Galaxy Nexus] safendi:
I don't have thermal throttle problem, I have this problem with all kernel Fancy, 4.2.2 and 4.3, with Franco,askp,AK,Golden not problem
[Samsung Galaxy Nexus] nmlssit:
I am reporting a freeze and reboot if Max Freq is set to 1536000.

r39ext on Paranoid 3.97.

› Paranoid Nexus
[Samsung Galaxy Nexus] boype:
33.5 fps for me @ 384 MHz GPU, 1228 MHz CPU, CM10.2 ROM.

That's quite an overclock... Since the 1.5 GHz is still kindof smartreflex calibrated with this kernel (unlike other kernels), the 1.5 won't work good for some.
[Samsung Galaxy Nexus] Steelskinz:
Good choice ! :o
[Samsung Galaxy Nexus] nmlssit:
That's strange, i had no problems at all with r38 :P

› Paranoid Nexus
[Samsung Galaxy Nexus] fiftyclick:
Amazing! This is exactly what I was looking for! I might try to integrate this into Tasker and will post back here if I get it figured out.

Thanks!
[Samsung Galaxy Nexus] kaiyoto123:
I think the issue is related to rom i'll try a clean flash ,thanks;)
[Samsung Galaxy Nexus] zeppelinrox:
I was notified of a mention so read a few posts... and I have a low resistance when it comes to scratching itches lol

not too much adds up as your opinion is all over the map.

Great on 4.2.2 but gaming impossible and whatnot.

My conclusion is you haven't used any recent version anyway and didn't experiment enough to find settings that work for you.

So... I just provide a menu.

You figure out what you're gonna eat.
[Samsung Galaxy Nexus] mangusZen:
Please let's keep this thread nice and in-topic

Thank you

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] Prasad:
It's not so much opinion as it is inference. You've made a great tool. Not sure why you're so conscious and defensive about it. My only opinion here is that it was useful with 4.2.2 ROMs, not so much with 4.3 since the SystemUI lag was fixed and the biggest downside if ever to poor memory management was lag, which is now natively unseen anyway.

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] r3act:
CM10.2 latest nightly;

Stable 38: random freeze and reboots

Stable 39: just got another reboot...

Leankernel does not have this problem...
[Samsung Galaxy Nexus] jonstrong:
Doesn't necessarily reflect on the kernel though -- CM10.2 nightly on the 18th was flakey (BT / Exchange / Email FC's), although 17th and 19th were good. I know we're all sharing info about working combinations and configs. I would just be hesitant to imply issues with a particular kernel based on the stability of a CM nightly build...

I may sit out this CM build and check back tomorrow! Yesterday's is running beautifully for me (manta and toro).
[Samsung Galaxy Nexus] Fenvarien:
I don't have any freezes or reboots with R38 and R39, just great performance, battery life and stability. Please check your installed apps, settings and possible overclock/undervolt.
[Samsung Galaxy Nexus] thomstrack:
[Off-topic] - The Galaxy Nexus have used much RAM after 4.1.2. Before, I navigate in web, listen music, twitter, Facebook, instagram in the same time without freezes.

There is any thing (more) to make for "better" this?

-

[On-topic]

Suggestion for FancyKernel [MENTION=4615478]boype[/MENTION]

The whitelist control to add and remove apps.

About r39: Awesome. Smooth, fast and best battery drain.
[Samsung Galaxy Nexus] zeppelinrox:
Wait till you have your usual number of apps installed.

Memory management, as far as I know, was barely modified going from 4.2.2 to 4.3. (there was actually quite a few little changes between 4.12 and 4.2.2 but nothing too drastic)

However, despite not being supercharged, you're still getting teh lags in games.

There's a few things you can try.

Some users report lower minfrees actually help with gaming (i assume because there is less app killing/activity going on in the background)

do engine flush

maybe bulletproof the game your playing.

dont use swap or zram (or use low end settings like swappiness=10 or 20)

use ondemand governor

lower vfs_cache_pressure

Anyway, maybe KAK would help a bit with various sysctl settings.
[Samsung Galaxy Nexus] ChavitoArg:
Hi boype, can u add to OP the way to remove whitelist thing on terminal using "touch"? I dont remember it and also think that it should be on the first post.

Edit:

su

touch /data/nowhitelist

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] 7175:
Yeah I definitely get what you're saying with the minor changes in memory management. I've noticed some good 'recovery from oom' in terms of smoothness and memory freeing that I didn't see in 4.2.2. Got about 130 apps now. I keep my system pretty clean of bogware, events management, I firewalled unnecessary network activity, but I feel I definitely need my crond and sysctl memory VM management. I'll definitely check out your scripts, appreciate it. ;)

[MENTION=2961427]Prasad007[/MENTION] [MENTION=320897]People[/MENTION] going too close to the oom event horizon: Still doing some tweaking and bench on maxPayne. I find these mods to fancy's VM/sysctl settings can be useful though (goes in /system/etc/sysctl.conf. First four can be tweaked some, vanir uses > 90, 45~55, 750, 1500 which works well.

## fancy stock 0
vm.dirty_ratio = 90
## fancy stock 0
vm.dirty_background_ratio = 55
## fancy stock 200
vm.dirty_expire_centisecs = 400
## fancy stock 0
vm.dirty_writeback_centisecs = 200
## fancy stock 45
vm.vfs_cache_pressure = 20
## fancy stock 3398?
vm.min_free_kbytes = 1442
## fancy stock 0
vm.drop_caches = 3

Probably need to 'enable' sysctl in /system/etc/init.d: Add a file 17sysctl or whatever wherein you have:

#!/system/bin/sh
## Enable Sysctl.conf
sysctl -p /system/etc/sysctl.conf

## Set sdcard readahead
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo 1024 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi

2nd entry sets sdcard readahead. I use 1024 readahead in games, which having a lot of reading. 1024 or 1280 has always been best for me.

Oh yeah, fancy r39 running great for me on slim and beanstalk 4.3 betas. No FCs or anything so far. Batt drain is really good. Ondemandplus is running a lot better with less 1228 cpu spikes. Not sure if I missed something regarding ondemandplus' io_is_busy=2?

My toro UV's (minUV + 25~45mV) if interested and system is stable:

1228=1175 mV
1036=1075 mV
729=950 mV
537=850 mV
384=800 mV
192=775 mV

VAUX3_6030=2800
[Samsung Galaxy Nexus] boype:
Will add it to the OP later. Thanks, I forgot about that :)

Oh I forgot to mention that in the change log. I added io_is_busy 2 functionality to ondemandplus... io_is_busy=1 simply treats all io time as busy time and therefore causes more CPU time in higher frequencies. io_is busy=2 only adds half of the io time as busy time. It is just a moderate io_is_busy if you will. Anyway, it seems like it does exactly what I intended it should be doing :)
[Samsung Galaxy Nexus] ReMuSeR:
Something is wrong with updater apk it says new update when u press refresh says its up to date
[Samsung Galaxy Nexus] siealex:
Confirmed, it throws such notifications every time I reboot or switch on Wi-Fi.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] parthipanramesh:
Update: Fancy Updater

- fixed issue with notifications
[Samsung Galaxy Nexus] -Jesco-:
is being stuck at "Android is upgrading" part of the long boot of this kernel ?
[Samsung Galaxy Nexus] siealex:
No, it must not freeze at this message.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] gizmoid:
Freeze and reboot with r39. Back to r38. Except WiFI high perf. and changed color is all stock.
[Samsung Galaxy Nexus] siealex:
Notifications arrive much more frequently :'(

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] mrdevil_25:
Not sure if it is kernel related, but since flashing r39 ext, my google accounts dont sync properly anymore (the H+ icon is constantly gray). Dirty flashed over r38ext. Same rom.

Have tried deleting google account and adding it back in and still no go.
[Samsung Galaxy Nexus] DroidOnRoids:
OP says don't report bugs without wiping cache and dalvik cache first. Try doing that first and see if it fixes itself.
[Samsung Galaxy Nexus] matteventu:
I'm having SOD with r39, perfectly cleaned flash with all wipes.
[Samsung Galaxy Nexus] lparcshinoda:
I've been getting 3-4 random shutdown on 39-ext (with stock settings, adactive brightness and zram activated and factory 4.3 rom) only today in 3 hours.

Just for report: I've used to get some rare (let's say 1 each 2-3 days) severe data drop and SOD/lag on wakeup using all of pre-39 versions... haven't tested if these bugs were present on stable 39-ext too because the shutdown thing was for me a killer and I'm thinking about going back on stock kernel (which didn't give me ANY problem apart from more battery consumption than fancy) or stable 38-ext (saying bye to PGM for now).

I still think that Fancy Kernel is a great improvement on the gnex kernel scene (and I surely miss an ondemandplus governor thing on my Nexus7).

Thanks for the great work boype. Will be happy to provide more info / logcat if necessary to help you isolate these bugs I'm reporting.
[Samsung Galaxy Nexus] shawnaye:
Those of you getting SODs, could you try a different scheduler such as deadline to see if you still get SODs?
[Samsung Galaxy Nexus] lparcshinoda:
I'm trying with ZRAM=off for now... let you know
[Samsung Galaxy Nexus] mrdevil_25:
sorry ddint make myself clear. I wiped cache and dalvik after flashing kernel.
[Samsung Galaxy Nexus] Fenvarien:
ZRAM is working fine here with r38 and r39, swappiness = 40. My current scheduler is deadline (8,1,1,250,2500).

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] infectedorganism:
Would someone who is on the latest kernel version (r39) post screenshots of the default settings for SIOplus and OndemandPlus?

Thanks in advance.
[Samsung Galaxy Nexus] Prasad:
256kb read ahead buffer

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4615478]boype[/MENTION]

Question for you..

Is the following init.rc line change required to have timer slack working correctly, or is the kernel commit enough?:

mount cgroup none /dev/cpuctl cpu,timer_slack

Thanks in advance! :)

Edit: This from your .sh too, same question:

# set cgroup_timer_slack for bg_non_interactive tasks
$bbox echo 100000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_ns
[Samsung Galaxy Nexus] bluerez79:
Did you try wiping databof Google play services and Google framework?
[Samsung Galaxy Nexus] Ci-Fi:
If that doesn't work try deleting your Google account, REBOOTING and adding it again.
[Samsung Galaxy Nexus] osm0sis:
I wouldn't wipe the framework, ever. Breaks push notifications for all apps until you reinstall those apps.
[Samsung Galaxy Nexus] boype:
The kernel commit is not enough. It just adds the basic functionality. Values for timer_slack control need to be assigned to specific task groups. I chose to use the cgroups that are already defined by the android OS anyway (apps / background_non_interactive). The first line you quoted there mounts the timer slack controller into the (virtual) file system: you'll find it in every cgroup listed in /dev/cpuctl/ then. The second line you quoted then applies an actual value of 100ms timer slack to the background_non_interactive cgroup.

In order to make timer slack work, you need all of this. Also, you need the follwing patch when you enable timer slack, or the logcat will be full of errors:

https://github.com/boype/kernel_tuna_jb43/commit/dc82a0f06c57ba903d775a5efa95d6c44c1d9c6b

After this, it'll work just fine :)

Swappiness is set to 0 after some seconds after boot automatically. That is UNLESS you enable zRAM on boot via init.d or an app like trickster. When you enable it manually later, swappiness will already be 0 and zram won't have any effect. Bottom Line: set zram to be enabled on boot and reboot the phone.

Seems like one of the recent memory handling commits screws up for some users. Funny, because no one reported any issues in the last test version :eek:
[Samsung Galaxy Nexus] gizmoid:
False report, not kernel issue. It`s happened with r38, r39 and r390. (The last 1 is kernel from Franco).
[Samsung Galaxy Nexus] mick.li:
Dunno if it has been mentioned, but the app crashes if no fancy kernel is found. I had tiny kernel installed when starting the app. It did not crash after flashing fancy kernel manually.

Mick
[Samsung Galaxy Nexus] SuperSalvo:
Hey i have good results with your settings. Are you using the same as you post me for a while or did you change something? Are you getting the same results?
[Samsung Galaxy Nexus] stevensoaj:
Yeah, I haven't had any issues whatsoever. Running default kernel settings except zRAM is enabled and I have undervolted -100mV across the board on MPU. Also, [MENTION=4615478]boype[/MENTION] , how do you feel about the LZ4 compression that faux has added to his kernel? I'm just curious what you think about it.
[Samsung Galaxy Nexus] AbhishekS:
Does undervolting save a LOT of battery? As in undervolting every MPU level by 100?
[Samsung Galaxy Nexus] boype:
I cannot give you anything precise, like 'it will save you X percent'. But in general, the battery savings of undervolting are overestimated.

Opinions may vary of course.

I can provide you a fact, though: Undervolting by 5%, for example, will not give you 5% of energy savings. The savings are considerably less.

And, with our phone, most people only undervolt the CPU. As the CPU is only one of many battery-eaters in the whole system, you get the picture how much undervolting really benefits you.
[Samsung Galaxy Nexus] osm0sis:
Ah haha okay I guess we don't have it properly enabled on any of the franco.Kernels right now. :p Francisco had only merged the original commit.

Thanks for the info!
[Samsung Galaxy Nexus] Jar3112:
Undervolting is definitely more useful for reducing CPU overheating while overclocking, IMHO.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stevensoaj:
I realize it doesnt save much battery, but it does save some! And every little bit helps in an area with horrible reception. I also do it to help keep my phone running cooler, not that it normally runs hot, but cooler is always better imo.
[Samsung Galaxy Nexus] siealex:
Swappiness is still zero even if I set zram on boot. I need to set it separately in Android Tuner.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] boype:
OK, I'll increase the delay after which swappiness is set to 0 then
[Samsung Galaxy Nexus] boype:
pre40-1

Hi,

here's pre40-1-ext.

Changes:

trying to fix random reboots some users reported

increase time after which swappiness is set t 0 after boot (so scripts have a chance to enable zram properly)

some changes to see if it can get any smoother

http://boypetersen.de/fancykernel43/tst/fancy_kernel-tuna-4.3-pre40-1-ext.zip

Have fun and please report!
[Samsung Galaxy Nexus] siealex:
Set it at least one minute.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Rushead:
Please?

Sent from a frequent flasher.
[Samsung Galaxy Nexus] siealex:
Trickster actually sets the "on boot" settings approximately 2 minutes after bootup even if no delay is set in it

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] mrdevil_25:
deleted. comment is way to out-dated.
[Samsung Galaxy Nexus] Citizen_Snips:
Mine sets fine. About 10/15 seconds after my phone boots I get the TricksterMod "Set On Boot Completed" notification. My delay is set to 0.

Never had any reboots or freezes on r39. Using ondemandplus and sioplus. I think 1028 rab. WiFi HP is ON, MPS-2. Battery life extender 100, smart reflex OFF for MPU. MPU UV -100 all frequencies. GPU at 384

Edit: stock frequencies except for max which is down to 1.0 from the stock 1.2
[Samsung Galaxy Nexus] siealex:
Does this kernel support init.d scripts? Android Tuner puts this script to /etc/init.d named 99_at_oom:

#!/system/bin/sh

chmod 666 /sys/module/lowmemorykiller/parameters/minfree

echo "4096,6144,8192,10240,12288,16384" > /sys/module/lowmemorykiller/parameters/minfree

But it does not work: the oom limits are not changed.

Sent from my paranoid fancy galaxy nexus

---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------

This script works properly if called from a script manager.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] mixtapes08:
Damn I miss your kernel boype. I wish you have an n4.:)

Sent from my Nexus⁴
[Samsung Galaxy Nexus] zoomy942:
So this kernel is the only one properly using it?
[Samsung Galaxy Nexus] Sparx639:
Mine never sets for some reason, so I always do it manually.
[Samsung Galaxy Nexus] nitsua98:
Mine gets set about 0.5 seconds after boot.
[Samsung Galaxy Nexus] boype:
I'll see if I can reproduce this

At the moment, it seems like that

LZ4 is cool stuff from what I read. Some days ago, I made an attempt to pull-in the 3.6 kernel zRAM updates manually (without plain-copying faux123's commits) but zRAM ended up not working somehow. When I have some time, I'll make another attempt with zRAM. When it succeeds, LZ4 is next.

P.S.: I feel like I need to give faux123 some 'bro love': He's a guy who knows what he's doing and keeps looking for new stuff to implement for the Galaxy Nexus. He's definitly pushing the GNex development.
[Samsung Galaxy Nexus] stevensoaj:
You and him both boype! Keep up the great work!
[Samsung Galaxy Nexus] 7175:
Definitely agree there, every bit helps. The biggest gains I've noticed ever have been from regulator UVs, particularly VAUx3_6030, VUSIM (affects LCD Vin and I think some radio) From some tests I ran yesterday, dropping VAUX3 to 2500 from 2800 gives a ~23%/hr less screen drain. So it can add an hour to screen on time. MPU UVs are good and do produce significant savings, but you might not notice the difference unless you're under load. Core UV is significant but smartreflex already does a good job with it. Could never push manually below smart reflex's UVs with daily driver stability.
[Samsung Galaxy Nexus] DaNi_!:
Logo

Hello guys, I liked this kernel so much so I thought maybe I can create some mockups for a new logo.

[MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] siealex:
VAUX3 is 2800 by default? My trickster always shows 3100.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] stevensoaj:
Mine shows 3100 as well.
[Samsung Galaxy Nexus] paarthdesai:
umm logo for? :o

yea the boot up logo like ak kernel would be great.. ;) [MENTION=4615478]boype[/MENTION]

and maybe a signature banners also :D

i would feel proud to flash it on my signature :)
[Samsung Galaxy Nexus] Seraz007:
Unfortunately encountered a reboot when set to 2500

But all's well on 2800 :D

+1 :confused:
[Samsung Galaxy Nexus] siealex:
What is VUSIM? I do not have such entry in trickster.

Sent from my paranoid fancy galaxy nexus