yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] salugsog:
i had this too a while back. Likely it's your usb port. the pin in the middle is bent and touching one side. you can lightly bend it back with the tip of thin knife. just be careful. See the issue here, scroll down to the last post: http://code.google.com/p/android/issues/detail?id=39625
[Samsung Galaxy Nexus] thesebastian:
Is there a way to unlock GN bootloader without wiping my device? I'm on 4.3
[Samsung Galaxy Nexus] thegtfusion:
No it is not possible.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] jorgen2009:
Yes it is, when you did it at least once, for you need to be rooted.

https://play.google.com/store/apps/details?id=net.segv11.bootunlocker

You can then toggle your locktatus without wiping your device with this app
[Samsung Galaxy Nexus] osm0sis:
Or even if you lose root or can't boot, as long as you've still got a custom recovery you can use my Nexus BootUnlocker zip in my Odds and Ends thread:

http://v.ht/osm0
[Samsung Galaxy Nexus] ashclepdia:
are you SURE?

i know you cant if you use fastboot.

i believe you CAN as long as you are rooted.

and you don't need to be unlocked in order to root.

tho it is WAY easier to root if unlocked.

not sure if anyone found a way to root Gnex 4.3(without being unlocked)

this discussion might warrant its own thread actually ;) (in Q&A of course)

but honestly, instead of going thru all the 'trouble' they are better off just backing up what they want (onto PC and via Helium app) then unlock and do it up right!

edit again... I'm losing my mind... don't mind me
[Samsung Galaxy Nexus] Sik-1:
Bigmem version anyone??? Man I wish I could compile these things smfh, I ask an only so bcuz Franco's kernel has always been a beast on my phone, just wish it had a few other things I see out there on other kernels,

Can somebody anybody point me into compiling my own,
[Samsung Galaxy Nexus] osm0sis:
Hahah for the longest time I thought smh meant suck my hole. That's what I get for using Twitter. :laugh:
[Samsung Galaxy Nexus] Sik-1:
Lmfao that's tooo funny, I don't even use twitter and that's new to me lml lol
[Samsung Galaxy Nexus] cmstlist:
The one I had to look up on Urbandictionary was GPOY. Kids these days!
[Samsung Galaxy Nexus] metalspring:
There are lots of guides to compiling kernels around, you'd just have to use Franco's source (in op) and make sure to post sources and credit them if you ever decide to let others use it too (Google GPL)

I'll warn you it's not all that easy though starting out
[Samsung Galaxy Nexus] Sik-1:
I kno i be been trying for months, I got the stock kernel to compile but when it comes to adding things from git , all hell breaks loose, bunch of errors and it simply just doesn't biuild after that
[Samsung Galaxy Nexus] metalspring:
I'm no expert (maybe someone else can correct me) but try replacing the stock kernel source with Franco's source instead if you want to build his kernel and change it. And just Google any config options you would consider changing to see what they do
[Samsung Galaxy Nexus] osm0sis:
Just following up here. I was reading a few kernel changelogs the other night that mention Wi-Fi PM Fast isn't possible in JB4.3. That was for another device, but may apply to the GN as well?
[Samsung Galaxy Nexus] JBNex:
Cool, thanks!
[Samsung Galaxy Nexus] wavedashdoc:
Any chance we could see the HUGEMEM project ported to Franco? Fancy's latest now supports it!
[Samsung Galaxy Nexus] sajty:
Fancy kernel rulezzz :cool:

Sent from my GN
[Samsung Galaxy Nexus] pkgnex:
I've actually been running this today to see how it feels. I've tried Fancy before and it was pretty good, but not as good as Franco...

This one, though (r42 extended) is, admittedly, freakin' awesome - and it pains me to even say that since I've been a Franco loyalist for so long!

The "hugemem" work Boype did definitely does what he says it does - having the extra ~75 Mb free RAM makes the phone smoother and snappier, getting rid of even the very last few micro-lags still left on the device after flashing Franco's kernel. The only price to pay for the extra RAM that I have found is that 1080p video recording is no longer available, and since I always record at 720p anyway, I'm willing to pay that price. In fact, I've had my phone for 21 months and haven't recorded in 1080p yet.

Even aside from "hugemem", Fancy is also - for the first time - on par with Franco in terms of the benchmark performance and subjective fluidity. This is the first time this has EVER happened with any non-Franco kernel on my device, and I believe I have tried every Toro kernel available. Fancy and Franco now appear to be basically identical in benchmark performance, and I haven't found any subjective advantage with Franco anymore, either. I like to think this is at least partly a result of Boype incorporating much of Franco's hard work, Osmosis' efforts, and the rest of Franco's Dev Team's tweaks / optimizations, but it definitely seems like Boype has taken the baton and is running with it.

I would personally still highly recommend either kernel - but would lean toward Franco if you record video in 1080p, and toward Fancy if you run a lot of memory-hungry applications. I also still think all the other kernels lag behind these two. Just my opinion though.
[Samsung Galaxy Nexus] ChazzMatt:
The current Fancy hugemem kernel has problems with barcode scanners, as they access the camera. Even the QR Barcode scanner, which in the Fancy thread was touted as a workaround to other barcode scanner apps that do not work with hugemem. Every time I try to use it I have to reboot my phone.

The hugemem is a gimmick that degrades certain phone functions.

I don't care about 1080p video but I need the barcode scanner function.

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] Astug:
You might wanna check out this fix that [MENTION=4615478]boype[/MENTION] provided, a few posts before yours. I've tested it myself and the barcode scanner apps are working just fine now.
[Samsung Galaxy Nexus] ChazzMatt:
Sure I will check out the pre-release test kernel boype posted. Must be why I missed it. I downloaded the regular release, as I like stability. :silly:

What I have issue with is everything "new" is not always gold -- so should not be hyped until proven. If phone use is degraded, don't care how "fluid" the phone is. :)

But if the issues are fixed, and the extra RAM helps fluidity, then YES the extra mem option is welcome.

I also like how boype gives full credit to Franco and the Franco dev team for all the settings/features he has used from them. I also think Franco has even cherry picked some stuff from boype (and given credit).
[Samsung Galaxy Nexus] Astug:
The pre-release might be a good option than, since it fixes what wasn't stable in the regular release. Was just trying to help out.

I wasn't convinced about bigmem myself, but when discussing this in the Fancy kernel thread, another XDA member pointed out to me that every feature was once experimental.

But there's no harm in hyping it up, it creates attention, which allows for more people to get involved and to get the bugs out faster.

Sorry for the OT anyway, as this is a thread for f.K.
[Samsung Galaxy Nexus] xzilem:
Sorry mate, QR is working nicely for me even with flash. There is something different you do to make it unusable. What gapps are you using?
[Samsung Galaxy Nexus] ChazzMatt:
Slim ROM 4.3 GAPPS. With "Nexus Flashlight" app from the market to light the area because I was in a dark room. "QR Barcode Scanner" would work without the light, but gave error message with the light. And each time I had to reboot the phone. The light was necessary.

But besides that , the regular "Barcode Scanner" app did not work at all. The QR app was touted as a workaround and it did not fully work.

Going to try the pre-release test version.

______

RESULTS:

No, pre-release test kernel also did not work.

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] shawnaye:
If you have such a need to use barcode scanner, then just stick with Franco or an older release of fancy.

The devs have already weighed the pros and cons. And I mean.. He feels that the extra ram is so useful by just sacrificing 1080p camera.

So I guess not everyone can benefit. But the majority will.

Don't go around degrading the devs work that hugemem is a gimmick and what not, it's actually helping many others.

Just so happens that you have needs that the majority don't.
[Samsung Galaxy Nexus] demon2112:
Just clean cach and settings in system/apps/gallerie2

Its trys to open in 1080 hd butt in fancy he dropt a line that disable it and set it to 720 by default just clean cach and data in apps and its working
[Samsung Galaxy Nexus] ChazzMatt:
We are discussing it here in Franco, because some people are URGING Franco to get a bigmem version like Fancy.

I will honestly discuss overhyped features that do NOT WORK PROPERLY in a development thread. That is what a development thread is for.

I even honestly discussed it in Fancy thread, because it's a real development thread and I had results to report. It's NOT "degrading" devs work. OK?

If the feature matures and doesn't break apps, then it's no longer a gimmick.

__________

I flash other kernels to try them out. I liked Fancy 40-extended. Ran very well. So, I have nothing bad to say about boype. It the bigmem, hugemem kernel as released in his 41-extended that caused issues.

and even the pre-42.

Not honestly reporting results does the dev no good. He then cannot fix problems. I saw a lot of that in the AK thread in the Skull 250 series. "OMG. The Best!" But it overheats and causes reboots. "Shut up. It's the BEST!".
[Samsung Galaxy Nexus] xzilem:
Sorry Off-Topic. Hi there. Do you use Slim AIO gapps or the other one without photosphere? Can you try flashing another gapps like PA or can you try clean cache as suggested by demon2112.

I think Hugemem is doing great and for me it didn't break anything other than that 1080p. So i'm satisfied with it.
[Samsung Galaxy Nexus] ChazzMatt:
It's not bigmem after all. I'm mistaken. Wrong.

I flashed new version of Slim AIO and Gapps, same problem.

But then flashed Franco, after Osmosis kernel reset script -- and got same problem.

So, it's NOT bigmem issue. Something else.

Others are having problems with bigmem, but my issue of LED with barcode scanner does not seem to be related -- at least with pre-release 42.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3250376]ChazzMatt[/MENTION], I've had my camera hardware **** the bed on me too today. Only thing that I did differently was use the new headphone boost. So it might be related to that or just a freak occurrence; it happened once before earlier in the year. Gallery/Camera app kept FCing and the stack trace seemed to relate it thought the camera hardware was unknown/missing. This also applied to using the flash LED as a flashlight. Instant freeze. I cleared caches on apps and media storage, rebooted several times. Still no luck.

I think what worked this time (and last time if I recall correctly) was to power off, pull the battery, then reassemble. Things are working well here again, going to try and reproduce the issue by turning volume boost on again now.

Edit: Still working, despite me messing with the headphone volume boost some more, so I guess it was just another freak occurrence. I think the complete power off and battery pull allows the camera hardware to properly reset itself.
[Samsung Galaxy Nexus] wavedashdoc:
Yeah I'm back on Franco because i couldn't go a few hours without a random reboot on Fancy 41,42. Tried everything from switching io to changing voltages to match Franco. The only reason I kept at it was how much more responsive my device was. 250mb + of free ram always is amazing. Apps on faster and remember where you left them instead of reloading! I even had 340 at one point. On the same ROM and everything with Franco I'm lucky to have 150mb free. So Franco if you have the time to look into HUGEMem it does seem worth it. My GN was as fast as my N72013. Franco + HUGEMem would be unstoppable.
[Samsung Galaxy Nexus] ChazzMatt:
countdown to the end...

Franco could get bigmem straightened out if anyone can -- but the only problem is the gen3 Galaxy Nexus is running out of time for Franco support. 6 - 8 weeks more at most? When Franco gets his hands on the LG Nexus 5, GNex support will be dropped and even Nexus 4 will only receive sporadic support. Just like when he got the LG Nexus 4, Franco support of the Nexus S ended and the Galaxy Nexus was put on the back burner.

However, the Franco XDA dev team (Osomosis and others) stepped up to help supplement support. :good: THANK YOU to all who helped out this past year.

With 2GB RAM, neither the LG Nexus 4 nor the LG Nexus 5 need "bigmem" feature, and I doubt Franco would want to introduce and trouble shoot such a new feature just as he's saying goodbye.

I will be one of the first in line for the LG Nexus 5, so I will still be running Franco kernel. :D
[Samsung Galaxy Nexus] Godra:
I think franco updates kernel as long as device is supported by Google ( and AOSP)
[Samsung Galaxy Nexus] ChazzMatt:
NO, you are wrong. He supported gen2 Nexus S sporadically when he got the gen3 Galaxy Nexus. Then he warned us that the gen3 Galaxy Nexus was going on the back burner when he got the gen4 Nexus 4. And he dropped the Nexus S.

It's quite fair -- Franco gives one year full dedicated support to the current Nexus device, then 1 year partial support to the previous year's Nexus device. But he's only one man and can't do everything. He's also supporting the Nexus tablets...

So, over two years old gets dropped. Gen3 Galaxy Nexus is about to become 2 years old.

_____________

THESE ARE ALL FROM A YEAR AGO IN THIS THREAD:

And quite understandably, the Franco Nexus S thread died, while this one became less active, and all the focus was on the Nexus 4. That pattern will repeat itself with the Nexus 5.

Just move to the Nexus 5 and you will be fine! :)
[Samsung Galaxy Nexus] osm0sis:
Chazz, you may be right, but you should work on not being so inflammatory when you are.. ;)

Francisco's backburner plans for the GN have always been to release a milestone with all of the FDT work on interactive and the schedulers, and then show us a final bit of love by giving us the new auto-tune interactive he's developed on the N4 and N7 2012.

He keeps getting sidetracked by real life, and more interesting, bleeding edge stuff on the N4, but as far as I know those are still the plans. He even recently stated he wants to give us speaker volume boosts as well, he just needs to figure out which register to modify like he did for his recent recode of the headphone volume boost.
[Samsung Galaxy Nexus] ChazzMatt:
You know I am not dissing Franco in any way. ;) Exactly the opposite. I think it's commendable to give one year full support to the current Nexus and then still help out the previous version. I was just again warning people to not be shocked when updates stop soon on our 2-year old phone. I just don't think Franco is going to implement a brand new feature like bigmem as support for our phone is winding down.

And yes, I get a little ticked off when people who really know nothing about the subject being discussed pull answers out of their butt say I'm wrong. (oh, wait am I being inflamatory again? :p ) Franco can continue support as long as he likes, I'm just repeating what he's said and done in the past, which seems very reasonable.

No need to explain what is going on in Franco's life. I appreciate the kernels he has given us. I've been on Franco for most of the time (since July 2012) that I've had my two Galaxy Nexus phones (my wife uses the other one). I've also tried other kernels, just to see what's out there, but I always return to Franco. As you know, I've been very active in this thread for over a year. As I said in the countdown note, osm0sis -- I am also very appreciative of your work to keep the Galaxy Nexus kernel development going.

I hope you get the Nexus 5 and continue contributing in that new XDA Franco thread. :)
[Samsung Galaxy Nexus] wavedashdoc:
With how many great reviews the G2 is getting, the Nexus 5 should be a killer phone. And worth another 2 years of Franco and community development! The Gnexus has been a great phone, first phone I have ever stayed on instead of upgrading within a year.
[Samsung Galaxy Nexus] osm0sis:
Yeah, I'm definitely contemplating the N4v2 or N5 or N4 2013 or whatever you want to call it. ;)

It'll partially depend on the form factor though; I don't really want a phone that's too much bigger than the N4 (so if it's actually the N5, 5" screen, and larger to accommodate that)..

In the meantime, we should make it really easy for Francisco to knock out a milestone for us so he can get on with the more interesting ideas he's had for us.. We should start by making a list of stuff that he forgot to add back in with the JB4.3 rebase. :good:
[Samsung Galaxy Nexus] wavedashdoc:
Now if only Big Red would carry the next Nexus...I'd switch to at&t but I don't want to lose my unlimited data.
[Samsung Galaxy Nexus] shawnaye:
N5 without a doubt.
[Samsung Galaxy Nexus] osm0sis:
Not sure I'm liking the look of it..

http://www.neowin.net/news/images-of-google-nexus-5-running-android-44-kitkat-leak
[Samsung Galaxy Nexus] thegtfusion:
Maybe its just a early stages look. I also hope it will be improved.... If it isnt beautiful i wont buy :(
[Samsung Galaxy Nexus] wiki_warren:
Has anyone lost root after updating to the latest version from GooglePlay? Noticed that after rebooting, my root access was lost. I have re-rooted and flashed stock kernel now and still have root after rebooting. Going to reinstall 391 and see if the issue returns

Edit: I'm going to hold off on reinstalling 391 until this gets resolved.
[Samsung Galaxy Nexus] osm0sis:
It's resolved.

Use my fixed version: http://d-h.st/users/osm0sis/jb4_3/tuna/
[Samsung Galaxy Nexus] shawnaye:
You're not digging the look?

I personally think it's fine, i just know i'll love the soft touch back since that's what the entire Nexus line is turning out to be.
[Samsung Galaxy Nexus] bigknowz:
BFQ

My vote is for BFQ.
[Samsung Galaxy Nexus] parkson:
Tried using your fixed 391 a few times but it never boots. Right after boot ani ends I get kicked back into recovery (using PA)
[Samsung Galaxy Nexus] The Gingerbread Man:
I have noticed that today, I thought it might have been to using the xposed framework. Apparently not lol
[Samsung Galaxy Nexus] osm0sis:
Working great for months here.. Bad flash? Try again?
[Samsung Galaxy Nexus] parkson:
Redownloaded 391 fixed and flashed over clean install of latest PA+gapps, still a no-go

[edit] using the cwm zip and SuperSU v1.65
[Samsung Galaxy Nexus] rene_r:
Same here, always boots into recovery.

Br
[Samsung Galaxy Nexus] osm0sis:
Try the fastboot flash then? Maybe there's something weird going on with the zip.. Though I'm sure we would have heard about it long before the current ~200 downloads if this were a universal issue. :confused:
[Samsung Galaxy Nexus] parkson:
Same result with the fastboot img
[Samsung Galaxy Nexus] Edward Stanbury:
try wiping cache, dalvik and system (under the mount/storage settings in cwm not sure about twrp) reflash rom gapps kernel etc you wont loose any data and see if that fixes anything :P
[Samsung Galaxy Nexus] The Gingerbread Man:
It doesn't happen often, I only noticed when I starter using the xposed framework and the gravity box module yesterday so I thought one of the APM was playing up or sending wrong command. Is there a log we could get?
[Samsung Galaxy Nexus] wiki_warren:
I was able to flash your 391 fixed zip on stock 4.3 JWR66Y with no issues using TWRP. After flashing, I wiped dalvik cache and it booted fine. After the reboot, I reinstalled Franco Kernel updater app with no issues also.
[Samsung Galaxy Nexus] garuhhh:
Same as G.man, I also noticed that when I reboot or boot, my phone it goes directly to CWM. I have xposed framework as well, and Im not sure if this started happening after installation of xposed or before.
[Samsung Galaxy Nexus] The Gingerbread Man:
Sounds like its the framework is the common denominator here then. Someone should report it to the dev. Out if interest which modules are you running? Just so we can see if its a particular module acting up or the installer
[Samsung Galaxy Nexus] AutomaticFailure27:
I know this isn't exactly about Franco kernel, but you guys are some beyond intelligent people, so any help is appreciated.

Not sure if this is a kernel issue or something with AOSPA, but if someone could shed some light on it, if possible. This has now happened between Fancy and Faux Kernel.

Sometimes, when I update the kernel (or reboot about 3/5 times also) I go through the normal wipe dalvik/cache - install - wipe dalvik/cache again - reboot process. Everything seems fine, never has failed me before, I see the prompt that Android is upgrading but, when it's complete, my SystemUI gets reset to stock, my home button gets removed as a button (the icon is still there), and most of the settings revert back to stock...

This has now happened when upgrading Faux and just now going from r42 to pre43. Try dirty flashing the rom but everything still stays the same. The only way I can fix it this, is to clean flash my rom again and restore apps using TiBu.

It seems to be sparatic and doesn't happen with every upgrade/flash. I'm not sure what could be the cause of this issue since kernels like Lean / Franco I have never once encountered this and it has only happened since the 4.3 upgrade.

Only thing I could come up with is the implementation of the LZ4 cache/ram thingy since, afaik, these are the only two kernels using such.

Thanks again for any insight or suggestions that come.
[Samsung Galaxy Nexus] parkson:
I've never used Xposed and I have problems booting with 391 fixed, so I'm not sure that's the cause.

One thing I did try was flashing a different kernel with its own ramdisk (fancy) and phone just got stuck on boot ani (no getting kicked back into recovery). Only way to rectify is to reflash ROM+gapps
[Samsung Galaxy Nexus] garuhhh:
I only use the App Settings. Use it to change the resolution and DPI settings of Calendar. That's it. No other.
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah that can happen when kernels do stuff with ram disk. Best practice is flash stock kernel before flashing another.

Seems it could be the installer then, whether or not its gnex specific I don't know. Iv asked on the gravity box thread to see if they can help.
[Samsung Galaxy Nexus] osm0sis:
Yup. Catch the reboot before it goes to recovery with the bootloader key combo then flash something working (original recipe Franco?) and boot, then grab me /proc/last_kmsg

Again, this is only useful if you stop it from booting recovery first, otherwise the last_kmsg will be from the recovery.
[Samsung Galaxy Nexus] ChazzMatt:
Same thing happening here, but I thought it had something to do with either new Slim ROM I flashed a few days ago. Xposed framework was another suspect. :)

About this same time, I also flashed Franco 391-fixed, changing from Fancy hugemem kernel, and used the osmosis kernel reset script.

So, a lot of stuff going on... hard to pin down what caused it.

Would boot into recovery, or when rebooting from recovery would often reboot BACK INTO RECOVERY. Sometimes took 2 or 3 reboots before booting correctly.

Tried several things, nothing worked.

I fixed it today by re-flashing my bootloader. Used KK15. (Cleared cache and dalvik first, then flashed bootloader. That step may not be necessary -- just reporting what I did.)

Now my GNex boots correctly everytime. Still don't know what caused the issues, but re-flashing bootloader solved it.

Find file here:

http://xdaforums.com/showpost.php?p=24567636
[Samsung Galaxy Nexus] osm0sis:
Also try out this, it's my absolute latest repack (switched back to Franco's default CM/AOSP? contexts files):

http://d-h.st/t3D

If you still have problems then definitely get me the last_kmsg like I outlined in my last post and I'll see what I can figure out.