yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metalspring:
He meant its fixed in the kernel source, franco just has to compile a new kernel build for it

https://github.com/franciscofranco/Tuna_JB_pre1/commit/367db9ed9e3a79ef0805a270de97fe683d224547
[Samsung Galaxy Nexus] skizofrenic:
Uuuuu

Thanks for link :D
[Samsung Galaxy Nexus] JazzMozz:
Yesterday I upgraded my GNex from 4.2.2 to 4.3. I'm on stock android and rooted. I also flashed franco kernel for GNex (first time ever that I flashed a kernel).

Since yesterday I have a massive battery drain. I use BBS and Wakelock Detector and they show that Google Services in general and NlpCollectorWakeLock and NlpWakeLock in particular are the culprits.

I think that there may be three possibilities:

1. the battery drain is caused by the upgrade from 4.2.2 to 4.3

2. the battery drain is caused by franco kernel

3. the battery drain is caused by Google Services going bonkers (see http://www.androidpolice.com/2013/11/19/its-not-just-you-google-play-services-seems-to-be-a-battery-hog-today/

I have searched the internet and XDA forums but the results aren't conclusive. Most people advise to disable

1. Location -> Wifi and mobile network

2. Google Settings -> Location -> Location reporting and Location history (I left Access to Location enabled)

I find it strange that the settings I mentioned above were all enabled when I was on 4.2.2 and I did not have any battery drain issues back then. Let's see what results these changed settings may deliver. In the mean time, do you have any suggestions what is going on here?
[Samsung Galaxy Nexus] saeed14i:
Did u do a full wipe (factory reset + "format" system) before upgrading from 4.2 to 4.3? If not then that may be a basic reason of the problem. No battery drains reported due to franco kernel so far. I had no such issues as well.
[Samsung Galaxy Nexus] fabrizziop:
Hey guys, I'm on fully stock 4.3, no root (had to flash factory image), only unlocked bootloader. Should I pick the r392 or the r392-fixed from osmosis?. And, is going back to stock kernel too much trouble (could I just flash boot.img from the factory image?). Thanks.
[Samsung Galaxy Nexus] JazzMozz:
No, I did not. I just did the regular OTA.
[Samsung Galaxy Nexus] saeed14i:
Strange issue. May be try a factory reset and hope things go your way. No other suggestion come to my mind at this time. Sorry :silly:
[Samsung Galaxy Nexus] ChazzMatt:
r392-fixed. It has some issues fixed that Franco has not addressed yet, but will in the next release.

If you use Flashify -- which is free -- you can back up your current stock kernel .img and re-flash it at any time.
[Samsung Galaxy Nexus] JuanG:
I flashed my first kernel some weeks ago. I tried stock paranoid 3.99 RC2 kernel, franco and finally I'm with fancy. I had some problems with battery drain, disconnections of wi fi signal and some lags. I rebooted the system many times but nothing changed. Finally, I decided to turn off and turn on the phone and everything was different. The battery has the normal behavior, few wakelooks, and no lags. Strange behavior but I think that the hardware can enter in conflict with different drivers when a new kernel is flashed if the device is not turned off. The software reboot doesn't reset the chips. I don't know but this can be the explanation.
[Samsung Galaxy Nexus] JazzMozz:
Thanks for the tip. I will certainly give that a try.
[Samsung Galaxy Nexus] JuanG:
You're welcome! Please don't forget to post your experience.
[Samsung Galaxy Nexus] gordonbennet:
For the longest battery life, which kernel do you think is most optimised towards that? Franco or Fancy kernel (big memory version with extra ram)?

Really interested in knowing experiences on both.
[Samsung Galaxy Nexus] metalspring:
You have to try different ones and different settings to see, every phone can be different
[Samsung Galaxy Nexus] Vekhez:
Either, I have used both, and I personally get better battery life on Franco.Kernel, but that is if I crazy underclock (729mhz), but without that, it's a matter of minutes.
[Samsung Galaxy Nexus] Tommolo:
I'm running aokp. If I install the r392 build, i've got the "process android.com.phone has been interrupted" on every boot and I can't get into the system. Why?
[Samsung Galaxy Nexus] AutomaticFailure27:
Download osm0sis' fixed version to have compatibility with CM based roms.
[Samsung Galaxy Nexus] ChazzMatt:
old version of FKU?

Selling my GNex, since I got the Nexus 5 earlier this month. Setting it up with custom 4.3.1 ROM and r392-fixed so buyer will have a great experience. Where can I get the older free version of FKU app apk -- like 10.3, 10.3.1 -- to put on this phone and change settings? I want the OMAP color control stuff back -- plus I don't want to download FKU from Google Market because I am deleting my personal data and apps off this phone.

I've flashed the kernel and ROM, I just can't change any settings without the FKU app. Surely there someplace on the internet I can find it? The older free version, not the paid. Not trying to cheat Franco. (Besides I've already paid twice for the app, for me and my wife's phones).

All I've found are dodgy sites which offer me downloads with "exe" extensions. :rolleyes: RIGHT. I'm not stupid.
[Samsung Galaxy Nexus] osm0sis:
There never was a free version of f.Ku that let you change settings. The free versions only allow you to update the kernel when a new nightly comes out. Use Trickster or init.d scripts.
[Samsung Galaxy Nexus] ChazzMatt:
OK, didn't know that. Used paid versions since almost after I got both Gnex July 2012.

_______

Sent from my Nexus 5 (LG-D820)
[Samsung Galaxy Nexus] JazzMozz:
I shut down my device, pulled the battery and waited for 4 minutes. Then I booted again but the wakelock behaviour is like before the shut down. No change at all. I disabled Wi-Fi and mobile location reporting which solves the problem. But now my apps that require location data (e.g. weather apps, Google maps etc.) do not function to the full potential which is a shame of course.
[Samsung Galaxy Nexus] Tommolo:
Where do I find it for the gnex maguro?
[Samsung Galaxy Nexus] h1ghland3r:
In this thread. ^^
[Samsung Galaxy Nexus] Edward Stanbury:
http://d-h.st/users/osm0sis
[Samsung Galaxy Nexus] JuanG:
It seems a very strange behavior. How is your system now? Stock rom 4.3 and franco kernel? Try disabling all google services, autosync, google play auto update, location, back up, etc.

Check with BBS the alarms that wake up your device.
[Samsung Galaxy Nexus] dracon6ai:
You can always use the Trickster Mod app. It'll do most (95%) of the adjustments Fku would and it's free.

***Laziness is nothing more than the habit of resting before one gets tired.***
[Samsung Galaxy Nexus] bigknowz:
Location Location Location

I had massive drain over the weekend. Solved by putting location on in Google Settings app and in Settings. Never had the issue before, maybe it has something to do with the latest update to Search Anyway, seems counterintuitive, but working so far.
[Samsung Galaxy Nexus] JazzMozz:
I'm on stock 4.3 rooted with Franco kernel. I froze Google search with Titanium Backup but enabled all my location settings. Left it for the night and it seems the wakelocks have returned to normal but maybe that's because my device was idle during the night. Will report if wakelocks return
[Samsung Galaxy Nexus] JazzMozz:
Hmmm, this is not getting any better.

What I did until now:

- Upgraded from 4.2.2 to 4.3

- Flashed franco kernel

- Disabled Google Settings -> Location -> Location Reporting and Location History (left Access to Location enabled)

- Left Location sources (GPS and Wifi/mobile network location) enabled because I want my apps to have access to location (I use weather apps and an app that toggles my Bluetooth when I'm moving in a car)

- Used AppOps to disable Location -> Google Play Services -> Location

- Froze Google Search (because it is linked to Google Now and I have the impression that this app has a lot to do with the device not going into deep sleep much)

BBS now gives me 48 minutes of NlpCollectorWakeLock (16,9% of time since last boot). 60,4% of deep sleep, 29,5% of 384 MHz, 7,9% of 537,6 MHz and then some of the higher frequencies. 4,7% depletion per hour. This has all been with very light usage.

OK, it has improved somewhat but I'm still disappointed by the battery usage and get the feeling that I cannot see the full potential of the franco kernel.

At this moment I'm out of ideas how to fix this. I find it frustrating that, even after reading tons of posts on several fora across the internet, I haven't found the holy grail. :crying: Maybe I have to come to grips with the idea that there is no solution. Hopefully it is less problematic when I will swith to the Nexus 5 in a few weeks.
[Samsung Galaxy Nexus] saeed14i:
You can always go back to square one and flash stock image all over again as explained in the following thread:

http://xdaforums.com/showthread.php?t=1626895
[Samsung Galaxy Nexus] JuanG:
GPS location is a high battery drainer when you are in an indoor places. Try disabled it and enable wifi/mobile network only.

Which app are you using to toggle the bluetooth? Check issues with android 4.3. Google has changed some API's in android 4.3.

I would try this (in order):

- wipe cache and dalvik

- Freeze any app running which use location (weather, facebook,etc)

- Reinstalling or wipe data of any google app and apps which use location

- do a clean installation of stock rom

There are much people reporting similar situations.
[Samsung Galaxy Nexus] osm0sis:
I get bad NLP (Network Location Provider) wakelocks as well. That's what you get for using Google Now basically. If you turn off Google Now and disable Location Reporting and make it Wi-Fi location only, battery is good and apps are still location aware.

I'm at 0.8%/h idle drain right now. NLP has a count of 1500+ so it's not good and is the cause for deep sleep only being 90% (which still isn't too bad). Before switching to the Google Home launcher and enabling Google Now I was at 0.4%/h and 96-98%.
[Samsung Galaxy Nexus] JazzMozz:
Thank you very much for all your contributions.

Yes, but that's the ultimum remedium. I don't think I will get there in the end because I'm about to order a Nexus 5. Assuming that it will ship in a few weeks (like everywhere it is sold out in my country and we do not have the Google Play Store so I cannot order it directly with Google), I will be putting aside my trusty Gnex soon.

I use BlueRoad for toggling Bluetooth when I'm in the car. That way I do not have to toggle it manually every time I get into the car.

What use would it be to freeze any app that uses location? Yes, obviously it would prevent the app accessing location data. But it would also make my GNex pretty useless because many apps will have less or no user value.

I froze Google Now so that won't access the location data.
[Samsung Galaxy Nexus] osm0sis:
Doesn't matter, it has background system services, so you need to actually go into Search settings and set Google Now Off. Location History and Reporting also need to be set to Off in the settings while you're there.

Hangouts/GTalk services are also notoriously bad for wakelocks.
[Samsung Galaxy Nexus] JazzMozz:
Thanx for your suggestions. However, Google Now was already set off, as were Location History and Reporting. Then I froze Google Search.

I also froze Hangouts.
[Samsung Galaxy Nexus] osm0sis:
Fewest wakelocks I ever had were when I removed Hangouts completely. I use stock ROM so I uninstalled it through Titanium Backup. Even disabled or frozen isn't enough for these apps sometimes, if they're just present on the system. Not the way it should be, but oh well.
[Samsung Galaxy Nexus] JazzMozz:
Is it safe to uninstall Hangouts? And what about Google Currents
[Samsung Galaxy Nexus] osm0sis:
You can uninstall whatever you want pretty much. Google Currents behaves a lot better if you just disable its background sync. Also good to disable Photo Sync/Picasa Uploader.
[Samsung Galaxy Nexus] andreskafe:
With SlimBean 4.3 this is my favorite kernel

In 4.4 works? Which version?
[Samsung Galaxy Nexus] DonDizzurp:
I was just about to ask this. SIO is probably the simplest and most efficient I/O scheduler for Android. I'm using the old Lean Kernel (for 4.2.x) just for SIO.

---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------

This is more ROM related and not anything with the kernel. Either way, pretty much all Google products can be removed safely.
[Samsung Galaxy Nexus] franciscofranco:
Ok I just pushed r394 with the stamp of approval of osm0sis. Hope it treats you all well and osm0sis will bug me again sometime if there's something new to add, but I can consider this one the milestone of milestones. Since I don't label milestones anymore we can all say its everything I could do for this device to enhance its user experience. osm0sis contributed with a couple patches because I have no more time to keep working on this actively since there's really nothing else I can improve without some harder work. It works on 4.4 roms AFAIK.
[Samsung Galaxy Nexus] Edward Stanbury:
Thank you and osm0sis for your hard work ! I love this kernel so much I cannot leave it ! Truly the best in my eyes :) haha and your hard work has paid off and made this device we'll over x2 faster and brings new life to this aging girl ;) hope to join ya on the n5 forums soon also !
[Samsung Galaxy Nexus] sd3993:
Has anyone tried r394 with cm11? It kept bootlooping for me :/
[Samsung Galaxy Nexus] wisefreakz:
Yes... Loops at bootscreen... Using kitkang....
[Samsung Galaxy Nexus] Hupro1971:
Bootloops on XP 4.4 ROM aswell
[Samsung Galaxy Nexus] sd3993:
I guess it still comes with the 4.3 ramdisk.

I think we have to wait for [MENTION=4544860]osm0sis[/MENTION] to modify it to remove the ramdisk...
[Samsung Galaxy Nexus] Edward Stanbury:
Cm tends to break many custom kernel support unless the ramdisk has the correct changes etc try with a 4.4 aosp ROM otherwise let's hope osm0sis kindly comes to the rescue :P
[Samsung Galaxy Nexus] franciscofranco:
I don't know anything about CM11, it works on stock 4.3 and on PA 4.4 I tested and it worked fine, that I'm sure.
[Samsung Galaxy Nexus] h1ghland3r:
Thanks for r394 franciscofranco!

Soon I'll get my N5, but my GNexus would be nothing without your custom kernel ^^
[Samsung Galaxy Nexus] andreskafe:
Same here. Bootloop in Slimkat 1.6.
[Samsung Galaxy Nexus] sd3993:
umm could you please be kind enough to post a version without the ramdisk? the same way osmosis made a 4.4 version of ur 392? that way ee can use it on cm too. Thank You :)
[Samsung Galaxy Nexus] chikimonke:
Agreed, would not boot on latest SlimKat
[Samsung Galaxy Nexus] metalspring:
When I opened up the franco ramdisk it seems to be missing the healthd binary that 4.4 uses for battery stats?

Could that be the issue?

I'll see if I can get a logcat or dmesg in a few minutes once I do a backup
[Samsung Galaxy Nexus] movelbit:
Wow. R394 is out

Cook :)
[Samsung Galaxy Nexus] sd3993:
wouldn't it be possible to simply add the healthd binary from the cm kernel to this one? sorry if i sound like a noob. very amateur in kernel stuff :p
[Samsung Galaxy Nexus] metalspring:
thats basically what I just tried lol...

[MENTION=3292224]franciscofranco[/MENTION]

here is the part of the logcat that seems to show why it wont boot on many 4.4 roms, not sure about the healthd binary though, since there were no errors about it but I think 4.4 still needs it-

D/dalvikvm( 3989): Unable to stat classpath element '/system/framework/framework-pac.jar'

D/dalvikvm( 3989): Unable to stat classpath element '/system/framework/telephony-msim.jar'

D/dalvikvm( 3989): Trying to load lib libjavacore.so 0x0

D/dalvikvm( 3989): Added shared lib libjavacore.so 0x0

D/dalvikvm( 3989): Trying to load lib libnativehelper.so 0x0

D/dalvikvm( 3989): Added shared lib libnativehelper.so 0x0

D/dalvikvm( 3989): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init

E/dalvikvm( 3989): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...

I/dalvikvm( 3989): "main" prio=5 tid=1 NATIVE

I/dalvikvm( 3989): | group="main" sCount=0 dsCount=0 obj=0x415edd50 self=0x2a00d3a8

I/dalvikvm( 3989): | sysTid=3989 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=1073824084

I/dalvikvm( 3989): | state=R schedstat=( 0 0 0 ) utm=24 stm=8 core=1

I/dalvikvm( 3989): #00 pc 000013e0 /system/lib/libcorkscrew.so (unwind_backtrace_thread+255)

I/dalvikvm( 3989): #01 pc 0006f7be /system/lib/libdvm.so (dvmDumpNativeStack(DebugOutputTarget const*, int)+41)

I/dalvikvm( 3989): #02 pc 000602ce /system/lib/libdvm.so (dvmDumpThreadEx(DebugOutputTarget const*, Thread*, bool)+309)

I/dalvikvm( 3989): #03 pc 00060398 /system/lib/libdvm.so (dvmDumpThread(Thread*, bool)+27)

I/dalvikvm( 3989): #04 pc 0003a89c /system/lib/libdvm.so

I/dalvikvm( 3989): #05 pc 00001dba /system/lib/libnativehelper.so (jniRegisterNativeMethods+105)

I/dalvikvm( 3989): #06 pc 0004dfd6 /system/lib/libandroid_runtime.so (android::AndroidRuntime::startReg(_JNIEnv*)+41)

I/dalvikvm( 3989): #07 pc 0004e074 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+111)

I/dalvikvm( 3989): #08 pc 00000f08 /system/bin/app_process

I/dalvikvm( 3989): #09 pc 0000e738 /system/lib/libc.so (__libc_init+55)

I/dalvikvm( 3989): at dalvik.system.NativeStart.main(Native Method)

I/dalvikvm( 3989): at dalvik.system.NativeStart.main(Native Method)

I/dalvikvm( 3989):

E/dalvikvm( 3989): VM aborting

F/libc ( 3989): Fatal signal 6 (SIGABRT) at 0x00000f95 (code=-6), thread 3989 (zygote)

I/DEBUG ( 130): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
[Samsung Galaxy Nexus] rajputrajat:
394 zipped using anykernel - working on kitkat

If anybody interested, I have created a zip of v394 using anykernel method.

Working great on "eurokang's kitkat" rom. And should work any 4.4 / 4.3 rom.

Enjoy !!! :highfive:
[Samsung Galaxy Nexus] metalspring:
...Franco has a lot of ramdisk optimizations so if you only use the zImage you will miss out on a lot of what makes franco kernel what it is...
[Samsung Galaxy Nexus] sd3993:
Well atleast something's better than nothing. Ofcourse when we get the full thing working for CM11 we all will shift to that anyways :P
[Samsung Galaxy Nexus] Vekhez:
So we are still going to get the odd update every now again and what not :D

Thank you so much btw, I really haven't voiced much in this thread, but this kernel is really, really amazing.
[Samsung Galaxy Nexus] sd3993:
Yep. Once in 2 months maybe. With [MENTION=4544860]osm0sis[/MENTION] dropping his mods once in a while ;)
[Samsung Galaxy Nexus] Vekhez:
That's fine :P just as long as we get the odd updates with the new patches.

Also, what are the chances of using the 3.4 kernel if its released?
[Samsung Galaxy Nexus] sd3993:
Well once the glitches in kitkat were fixed i lost interest in the 3.4 kernel. Maybe there will be a theoretical increase in speed when using 3.4 but you never know till it's actually tested :)
[Samsung Galaxy Nexus] Vekhez:
The 3.4 should theoretically increase battery. Theoretically.
[Samsung Galaxy Nexus] sd3993:
Yes. We'll just have to wait and watch i guess :p
[Samsung Galaxy Nexus] osm0sis:
Weird that it works with PA4.4 to be honest; it definitely requires a completely different ramdisk for all the other KK ROMs.

This is still a JB kernel so I think it's fine. I'll repack it with my KK ramdisk to make a hybrid, and I'll look into AnyKernel properly soon so we can have one build to rule them all but with all the f.K optimizations added to whatever ramdisk you need. Once I've figured out the script for that I'll email it to you and we can do r395 and call it a year. ;)

Thank you for all the work over the last 2 years Francisco. This kernel remains exceptional.
[Samsung Galaxy Nexus] metalspring:
Tiny kernel has a script that does exactly that built in lol

editramdisk.sh

#!/sbin/sh

#unpack ramdisk

mkdir /tmp/ramdisk

cd /tmp/ramdisk

gunzip -c ../boot.img-ramdisk.gz |cpio -i

MODIFIED=`cat init.rc | grep "mount cgroup none /dev/cpuctl cpu,timer_slack"`

if [ "$MODIFIED" ];

then

echo "Done already"

else

sed -i 's#mount cgroup none /dev/cpuctl cpu#mount cgroup none /dev/cpuctl cpu,timer_slack#' init.rc

fi

#build new ramdisk

find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz
[Samsung Galaxy Nexus] sd3993:
ok one more standard feauture i found missing was ASRAM. Dont think it has anything to with RamDisk does it? I hope it's included in the hybrid! :)
[Samsung Galaxy Nexus] metalspring:
Its not a ramdisk change and it should already be included

https://github.com/franciscofranco/Tuna_JB_pre1/commit/a5200bf56b02453da6d8d33e83baf2e51f014845

changelogtext>

New! Add the memory reclaim feature from mpokwsthsand boype (reclaims 50Mb from the YUV Tiler).
[Samsung Galaxy Nexus] sd3993:
I knw abt that commit. It was there in r392. But i get 694mb ram in the AnyKernel version of r394 posted here. :(
[Samsung Galaxy Nexus] metalspring:
Did you use it on a 4.4 rom? I believe 4.4 reserves more memory for the os than 4.3 did, so with ASRAM you are just making up for it
[Samsung Galaxy Nexus] aR_ChRiS:
Is there a way to add back OMAP gamma/contrast settings back to the FK.U because I miss that function and have to resort to trickster mod for now :(
[Samsung Galaxy Nexus] xiyuanhai:
Is it fit for Mokee ROM ???
[Samsung Galaxy Nexus] sd3993:
Other kernels with ASRAM gave 743 mb of memeory on 4.4. But the new franco gives me 694 only. :/
[Samsung Galaxy Nexus] rajputrajat:
+1

I was using zImage of 392 and had 743 MB of memory, but with 394 it is 694 (using same ROM - Eurokank - CM11)

so it is not 4.4.
[Samsung Galaxy Nexus] Vekhez:
There is one above that should work on ANY ROM. The stock one from Franco with all his mods, is only working on PA 4.4 and Stock Android (not CM since it's change).
[Samsung Galaxy Nexus] Godra:
What happened to extra RAM :(
[Samsung Galaxy Nexus] cuboc:
the touch control is not working, then we expect that the creator has updated software, or you could add in the kernel?
[Samsung Galaxy Nexus] ChazzMatt:
So, no longer "big mem"?

_______

Sent from my Nexus 5 (LG-D820)
[Samsung Galaxy Nexus] sd3993:
I wonder too. But i don't see any commits on franco's github reverting ASRAM. Maybe [MENTION=4544860]osm0sis[/MENTION] can throw some insight on this. I'll just wait patiently for him :)
[Samsung Galaxy Nexus] dracon6ai:
From the creator, always from the creator.

***Laziness is nothing more than the habit of resting before one gets tired.***
[Samsung Galaxy Nexus] osm0sis:
My only guess is one of the Linux kernel revision bumps somehow indirectly disabled ASRAM. I'm seeing a bunch of weird warnings from system ui in log cat too, so I'll email Francisco.
[Samsung Galaxy Nexus] sd3993:
I also noticed right now. Im unable to switch to ART using franco r394 on cm11! i could be wrong. Can anyone please confirm??
[Samsung Galaxy Nexus] thesebastian:
One question, How do you install r394 on CM11?
[Samsung Galaxy Nexus] sd3993:
Flash this

http://xdaforums.com/attachment.php?attachmentid=2419488&d=1385618982
[Samsung Galaxy Nexus] ux50jp:
deleted
[Samsung Galaxy Nexus] creeve4:
Is anyone sharing their 4.4 PA builds for maguro?
[Samsung Galaxy Nexus] gummie:
Was so happy to see an update but then I saw that BigMem was gone. I'm gonna wait for few more days to see if Mr. Franco did forgot or intentionally left it out.
[Samsung Galaxy Nexus] Edward Stanbury:
its strange because here's the change log: http://192.241.177.15/GalaxyNexus/4.3/appfiles/changelog.xml

something must have happened ;)
[Samsung Galaxy Nexus] pegox:
Does the touch boost drain our battery faster?:)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] sd3993:
Not really. :)
[Samsung Galaxy Nexus] pegox:
Thank you man:)

Another question if I can. Do you have a great battery life? :)
[Samsung Galaxy Nexus] sd3993:
Average i would say. Around 2.5 hours of screen on time approximately with moderately heave usage.
[Samsung Galaxy Nexus] pegox:
Wow, awesome! I flash it now;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] arshum:
I haven't tried 394 yet, does touch control not work in this version?