yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] laureanop:
That's what I always say before buying every new phone, but then as soon as I get the shipping notification the frantic search for rooting methods and the most popular Rom begins. Can't help it either

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] Citizen_Snips:
Lol I knew how to root my Droid X, Droid X2, Stratosphere and Nexus before I had any of them :p

On topic, this ROM is still running fine. I downloaded a new file nice and fresh. Going to flash later today and see if it fixes the TabletUI force closes I had.

To anyone else who had issues, did you flash a custom kernel or use the stock built in one? I flashed fancy r39 prior to first boot. I'll try again without flashing a kernel this time I'll keep you posted!
[Samsung Galaxy Nexus] fcisco13:
Tried other kernels but nine run as fast and smooth as stock.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] swarlesbarkely:
Any way to take screenshots? The only thing I found was in navring targets and that didn't work.. The target just doesn't show up
[Samsung Galaxy Nexus] nitsua98:
Press and hold volume down and power simultaneously.
[Samsung Galaxy Nexus] The Race To Die:
That's a problem with koush's superuser. If you flash chanfire's 1.51 there is no need to change anything
[Samsung Galaxy Nexus] swarlesbarkely:
Learn something new every day. Thanks!
[Samsung Galaxy Nexus] qwas7899:
Nice rom DHO. Good work. Thx
[Samsung Galaxy Nexus] DHO:
In the works,.... I think there is a test fix in the gerrit. My build box has been down sinc yesterday, and I am testing a new phone. So my attention is somewhat divided.

Thanks :)

Tons more to come.. Once I get my build box put back together will begin testing for B58
[Samsung Galaxy Nexus] t1.8matt:
I keep losing service when the screen is off with the ROM and every other 4.3 ROM. Anyone else seeing this? The only ROM I have left to try is Slim Bean and I have a feeling its going to do the same thing.
[Samsung Galaxy Nexus] chrisexv6:
Stock kernel?

I had a lot of wonkiness on Leankernel with this ROM for some reason. Also make sure you have a new(ish) version of your recovery, to make sure its clearing stuff where it should for 4.3 (or whatever version you are coming from). My recovery was old and apparently didnt like clearing the cache partition(s) from 4.2.2 so when I went to 4.3 all heck broke loose. Updating that and reflashing and leaving stock kernel seems to have made it more stable.
[Samsung Galaxy Nexus] t1.8matt:
I've been running latest ASKP and GoldenKernel. I've notices it mainly while its charging with my portable charger in my pocket, but it will do it without it too. I dunno. I'm gonna run it tomorrow since I won't be connected to WiFi at work and see what happens.
[Samsung Galaxy Nexus] konjiki7:
Gold kernel really made this rom come alive. Especially when you setup its governors.
[Samsung Galaxy Nexus] chrisexv6:
Trying it right now, getting more data wonkiness again. Really strange, stock kernel was great but every other kernel Ive tried the data acts flaky.

Unless its just a network thing in the area of my house (which has never been the case before).
[Samsung Galaxy Nexus] swarlesbarkely:
I'm having issues with performance settings. Specifically voltage control boot settings not applying and the boot animation not disabling

Is there a way to set voltages via a script or something similar?
[Samsung Galaxy Nexus] christianpeso:
Are people aware that the Toro Binaries are released?

https://developers.google.com/android/nexus/drivers#torojwr66v

Should have newer radios that will hopefully help out with signal issues.
[Samsung Galaxy Nexus] classic7876:
Not sure about the rest but ive tried changing the boot animation and it failed i think its a 4.3 thing
[Samsung Galaxy Nexus] Sheetzie03:
Sure hope so. I was just asking if/when we will have 4.3 flashable radios in the vzw radio sticky http://xdaforums.com/showthread.php?p=44963222 and some were saying theyd be very surprised if we would see them because of the declining support of the gnex by vzw. If this is what this means, its awesome.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrisexv6:
Would be a great day if thats the case! Im amazed at the life that devs can breathe into this phone....which is a big part of the reason I refuse to get a locked S4.

While *VERIZON* might not be supporting the GNex anymore, maybe Samsung hasnt completely given up on it yet.
[Samsung Galaxy Nexus] Sheetzie03:
When will we know for sure if well have flashable 4.3 radios? Does that link mean its for sure?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrisexv6:
Patience young Padawan
[Samsung Galaxy Nexus] nitsua98:
It's not up to Samsung to update our phone.
[Samsung Galaxy Nexus] Rushead:
Exactly.

You can wish in one hand & crap in the other... See which one fills up first.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] chrisexv6:
Who is it up to (serious question, since I dont really know)

And how does it work for "Google Play Edition" phones? Who is supposed to update the radios? I always figured it was the hardware manufacturer (in Gnex case, Samsung)
[Samsung Galaxy Nexus] nitsua98:
It's up to Verizon and I doubt they'll release 4.3 because from their perspective they probably think they already did us a favor by releasing 4.2.2.
[Samsung Galaxy Nexus] DHO:
Yep :) We are up-to-date on an nexi

I agree :/ We are lucky VZQ kept up with the Gnex as long as they did. I bet the b/c all support for unlockable devices....
[Samsung Galaxy Nexus] chrisexv6:
So if Verizon is afraid of unlocked phones any suggestions on what to replace the Gnex with?

Not having much luck with 4.3 and data so far and my upgrade is here
[Samsung Galaxy Nexus] chrisexv6:
Is anyone else having bluetooth issues with this ROM? Im trying to figure out if its the ROM, the kernel (Golden Kernel) or kernel settings, or a combination of those.

Streaming audio to my car, it connects up OK when I start the car, and can stream just fine while driving. I pause the music when I pull into a parking spot (since automatic-pause has been broken forever), and that works fine. Once I come back in the car and start up again, the phone will freeze when the head unit tries to re-connect. Phone doesnt respond, and about 30-45 seconds later it reboots itself.

Ill try to get a logcat the next time I have my laptop with me, I think thats going to be the only helpful way to see whats going on. Just wondering if anyone else has seen this issue.

Thanks

-Chris
[Samsung Galaxy Nexus] DHO:
Themes! Use direct link or Mirror 1 + Mirror 2 (use last) <-- NEW

Commotio Lock + Halo - Credit JFay22

Vanir Lock + Halo - Credit JFay22

http://goo.im/devs/DHO/8-addons/Themes/
[Samsung Galaxy Nexus] DHO:
Thats why I invested in a S4 yesterday,... I found one with an mdk bootloader. I am not hoping for much mroe from the N5. I would recommend it

Also if you reallly reallly stay on top of things you can get a Moto X Dev edition on Vzw. But they seem to only sell dev editions under the cover of night in almost impossible to find places.

I'll try to replicate tomorrow going to work. If you catch a log,... that would help alot :)
[Samsung Galaxy Nexus] chrisexv6:
Hehe, you're telling me about those dev versions! Its nuts how fast the S4 dev version went away.

Im not thrilled with the idea of paying full price (or basically full price) for an S4 in the hopes of getting an MDK build. While I complain about the high cost of VZW, I like not having to dump 600.00 at one time for a new phone. I know, I know, no 2 yr lock in if I buy outright but the way I look at it is Ill be with Verizon at least that long anyway...every other carrier isnt a great option around here apparently.

And I will try my hardest to get a logcat of the Bluetooth issue. I already have a traces.txt and a possible logcat from when it happened. There are a lot of references to Slacker, so Im wondering if the issue is more with the Slacker app than anything else, but Ill keep looking. I havent tried streaming with anything else to see if it still happens, I will give that a shot too.

-Chris

---------- Post added at 10:27 PM ---------- Previous post was at 09:29 PM ----------

DHO - I *think* the logcat here here shows the freeze. I didnt take this recently but I did capture it earlier today. Not sure why logcat doesnt show timestamps by default so I cant be sure but looking through it it seems like at some point the phone freaked and rebooted. Search the text for "E/ActivityManager(13531): ANR in com.slacker.radio" to see where I think it started happening.

-Chris
[Samsung Galaxy Nexus] chrisexv6:
OK, good log here: https://dl.dropboxusercontent.com/u/14958505/logfile2.txt

Seems like when the phone is paused on Slacker, and then I attempt to start my car (with the bluetooth source selected), it downloads the phonebook then chaos ensues. The log linked above is right after the phonebook is downloaded (left out names and numbers to protect the innocent :) ).

I kept logging while it was crashing, and stopped logging once the Commotio screen came back up (the phone reboots itself after a while of not responding to anything....I cant even wake up the screen while its doing its thing). The phone cant be COMPLETELY frozen because I still get an LED notification if there was one before the incident occurs. But eventually it just reboots itself. Interestingly enough, after it rebooted this time is instantly froze again (i assume trying to connect to the head unit), and the only way I could get past the bootloop was a clean reflash. I tried wiping cache and dalvik, flashing a new kernel and even a dirty flash of this ROM but nothing worked.
[Samsung Galaxy Nexus] chrisexv6:
Was able to start re-creating this at will, at home.

Plug PC speakers directly into headset port on phone, plug phone into USB port on PC. Fire up Slacker, stream a few songs. Unplug USB, pause Slacker, unplug speaker cable.

Go to car, turn on head unit (put car in accessory mode, doesnt need to be running). Head unit says "connecting to Galaxy NexusCDMA", it gets the bluetooth track data for the track that is paused in Slacker and thats it. Phone doesnt wake up (although notification LED still blinks), and eventually it seems to be a soft reboot - not a complete system reboot, the boot ani comes up for not long at all then you get to the home screen. Data connection is lost though (like on a cold boot) and has to re-acquire.

This is with a barebones install of the ROM (stock kernel) and Slacker radio, nothing much else.
[Samsung Galaxy Nexus] konjiki7:
Well I say your not the only one with this issue. It's been happening to me a lot since got back on this ROM.

Cycling data off and on helps but can be tedious
[Samsung Galaxy Nexus] t1.8matt:
I think something else was perpetuating the problem because I didn't have the that problem for a while after I posted that.
[Samsung Galaxy Nexus] chrisexv6:
Still messing with the bluetooth issue. I tried a different ROM (GASP!), ParanoidAndroid built by FairCT, and it doesnt seem to have the issue.

I stumbled on a post from forever ago about someone having a similar issue...it turned out they needed the stock music player installed, or else everything would go bonkers on bluetooth connect. I noticed PA seems to have that (assuming stock music player is Google Play Music), but Commotio does not. Im going to try a fresh install of Commotio, adding Google Play Music and see if that helps. Im also wondering if DSP Manager being the only installed sound manager might cause an issue (I think 4.2 ROMs were that way too and never had an issue so that could be a stretch).

As far as data issues, theyve pretty much cleared up. I wonder if VZW was tweaking stuff, or just ticking us off because they can.
[Samsung Galaxy Nexus] Citizen_Snips:
Try it on another ROM. Maybe official PA or CM10.2 and see if the error happens. Just because fairct includes a mod or two that isn't in official PA. One being a LTE quick setting toggle and a Bluetooth fix. It could just work on his build because of that fix while it's just a 4.3 issue? My car doesn't have a head unit (stock/crap) and I can't test it out. Only thing I have is a PS3 v2 headset and that works fine for me.
[Samsung Galaxy Nexus] chrisexv6:
Yeah will try that tonight.

The funny thing is, PA seems to run slow as a turtle on my phone, but Commotio is lightning fast. Would REALLY REALLY like to get the bluetooth thing resolved on Commotio since my phone seems to love being on Vanir-based ROMs.
[Samsung Galaxy Nexus] Citizen_Snips:
I hear ya. I tried fairct builds, official PA, stock AOSP, CM10.2 and a PAC nightly or two. Always end up back here though. Too much about this ROM that I love. DHO does a great job with it.

[MENTION=2633294]DHO[/MENTION] I figured out the FC in tablet mode I reported earlier. It was actually pretty easy. I noticed a FC of SystemUI in ANY UI mode when clicking a spot that would normally open the calendar. So I opened the app drawer and looked for calendar and it wasn't there at all. I took the Calendar.apk out of 8/22 PA gapps. I forget if I installed it as a regular app or if I moved it to /system/app but once installed I cannot get the UI force close to come back in any UI mode. Just need the calendar installed. :)

Just saw your post about working on B58. Can't wait, thanks for developing for the gnex still
[Samsung Galaxy Nexus] chrisexv6:
Yeah, really digging Commotio (and ATOM when its out)

I noticed some newer nightlies of Commotio so I might give them a shot to see if its resolved there.
[Samsung Galaxy Nexus] chrisexv6:
It looks like the Bluetooth fix from fairct is for audio quality... Nothing to do with connections but maybe it somehow affects those too.

Will try official cm or pa tomorrow hopefully
[Samsung Galaxy Nexus] heXacode:
I don't have Bluetooth issues at all. I don't even have the stock music player either. Everything I flashed is what DHO provided. I always do a full wipe manually and then flash the AR Superwipe script before flashing any ROMs and gapps. Even if its just a minor ROM update. I can't even remember the last time I dirty flashed a ROM. I know some think its an overkill but I rarely see issues versus others who don't wipe enough or dirty flash and have issues.

How are you doing your wipes? What are you flashing in order after wipes?
[Samsung Galaxy Nexus] chrisexv6:
Same here, using the AR wipe script. I dont think Ive ever dirty flashed anything.

I use TWRP, add the AR wipe zip then the Commotio zip. Thats it (since Gapps is built into Commotio)

Bluetooth connects just fine, I think its also just fine on re-connect *as long as Slacker isnt running*. If I pause Slacker at my desk then walk to my car and start it, the phone freaks out when trying to reconnect to the head unit.

This DOES NOT happen in fairct ParanoidAndroid build. I havent tried the official PA or CM yet, but at least in his build I can play Slacker, pause it, go to the car and on connect it works fine. So there is something different between Commotio and fairct PA in regards to what is used during that connection. I would say its the Slacker app but the fact it works OK in another ROM leads me to believe thats not the case. Ive also tried different kernels with Commotio and it still happens, so it seems like something in the ROM itself.

I dont doubt it will get worked out in Vanir/Commotio, I just wanted to provide as much info as I could if they are in fact troubleshooting the issue behind the scenes.
[Samsung Galaxy Nexus] heXacode:
What build are you on if I may ask?
[Samsung Galaxy Nexus] chrisexv6:
Commotio? The "official" one released in this thread (B57). Im going to try a nightly when I get a chance today, along with the official builds of PA and CM.
[Samsung Galaxy Nexus] heXacode:
Yeah I know Commotio. When I mean build I mean B57 or whatever else. You're running the Aug 18th build?
[Samsung Galaxy Nexus] chrisexv6:
Yeah, B57, released 8/18. Not sure if the nightlies since then hold any changes or not that might fix the issue Im seeing.

I was asking if you were talking about my Commotio build, Slacker version or TWRP version (just to be sure...but I figured you were talking about the ROM)
[Samsung Galaxy Nexus] heXacode:
Well I was trying to see what you were currently running since I don't have Slacker. We must be running a slightly different version.
[Samsung Galaxy Nexus] chrisexv6:
Another thing I'm going to try is Pandora.

What streaming apps do you use?
[Samsung Galaxy Nexus] heXacode:
Just Pandora. I was unable to replicate your problem by downloading slacker and using my laptop to plug and play and also stream to it wirelessly. Including pausing and streaming to my Bluetooth Kenwood radio in my truck. I tried your steps with that. I use Pandora only. Never really cared for Slacker. I have the hacked version of Pandora. I also tried the same steps including your steps and still couldn't replicate your problem.
[Samsung Galaxy Nexus] chrisexv6:
Someone is having the same issue as mine on slim bean ROM. Not sure what changes caused it but it must be common if it happened to two ROMs

EDIT: one of the Slim Bean devs said its fixed in an upcoming build....the BT connection was going null for some reason and the code wasnt checking it before it got re-used. DHO - not sure where the fix needs to be made, but it looks like its something simple.
[Samsung Galaxy Nexus] DHO:
Thanks for the logs.... the error is no mystery there

Failed on audit_set_pid with error: Protocol not supported

This could be kernel related. Also some BT share devices,... just mess with toro. They work perfect on other devices, but toro.... I find disabling MMS/SMS support on my car helped a bit.

I have this on the to look into list. I will grep my source for this later

Your log was missing,... :/

Cool, I will look over there
[Samsung Galaxy Nexus] chrisexv6:
Yeah sorry about the missing log, took it down because I realized there was phone history in there.

I suppose protocol not supported could be the phone, but up until 4.3 its worked just fine. A little quirky in regards to control (it doesnt auto-pause when the car shuts down, etc), but it was always stable on disconnect/reconnect.

I think BT was completely redone in 4.3? That might explain possibly regressing to not working state.
[Samsung Galaxy Nexus] DHO:
Okay,.. I cherry-picked eveything remotely related to BT and some other NPEs from slim

hopefully that does it. otherwise I need a lead of what commit they added
[Samsung Galaxy Nexus] chrisexv6:
I *think* what they were referring to was in A2DPservice.java ("add null pointer check")
[Samsung Galaxy Nexus] DHO:
I grabbed that

But having to build from a clobber. x18 devices,.. takes a damn LONG time
[Samsung Galaxy Nexus] chrisexv6:
Heh yeah, I saw someone on the Vanir G+ commented about how its the only ROM where a repo sync pulls 2.2GB worth of stuff for new devices everytime :)

Seriously though, you guys rock. Ive yet to find something else that runs so smooth and fast on my phone
[Samsung Galaxy Nexus] chrisexv6:
BTW the whole "failed to set PID" error is prevalant throughout the logs (not just the spot where the BT stuff went wacky). The phone works normally even with those messages all over the place so Im thinking thats NOT the source of the issue.
[Samsung Galaxy Nexus] Citizen_Snips:
Got a notification from goo. Just checked your server. Just downloaded B58! Thanks!!
[Samsung Galaxy Nexus] C.Hatfield:
I just went checking for a probable update to Commotio just yesterday (?) & there wasn't anything new .....

I'm glad someone else is just as vigilant - appreciate the heads-up !!!

DHO THANKS SO MUCH for the ONLY REAL 4.3 build to date, now B58 - YOU ROCK DOC !!!

*~^^~* TEAM VANIR *~^^~*

Ya simply CAN'T F&CK w/ THEM, especially my main homies

DOC [DHO] & PRIME DIRECTIVE

- there are vastly superior forces at work & at play with Team Vanir !!!

*~^^~* \m/- FTW -\m/ *~^^~*

**I ~KNOW~ I'm NOT ALONE in thinking knowing the

REALITY

that these dudes simply don't f&ck around - they quietly have amassed a verrry loyal (& well-deserved) following by flying under-the-radar !!! Anyone who feels as I do, I am only singing to the choir - those who DO NOT KNOW .... all I can say is .... I hope they find the vanir "enlightenment" & have a MUCH RICHER Android experience !!
[Samsung Galaxy Nexus] chrisexv6:
More detailed logcat: http://db.tt/nBp4SvLS

Cranked the logging level up to 5 on all BT related stuff. I personally still cant see whats going on, but hopefully this helps.
[Samsung Galaxy Nexus] cujo6801:
Look man if you got something to say just say it....

I hate people who beat around the bush....

sent from the DOG pound
[Samsung Galaxy Nexus] fcisco13:
No **** lol "i like the rom, thanks" would've done it.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] bigbear6708:
great ROM, just flashed..running great so far. love the theme! just one question..can anyone give me a practical use for the dialer option "hang up and call back on incoming call"...LOL, its an instant redial...i dont get it!

also, it seems that the nav bar is overlapping the lock screen so to speak. when widget is maximized, you can only "grab" the top portion of the lock.
[Samsung Galaxy Nexus] DHO:
:D

Thanks checking out

Yea,.. we use CM's dialer. As they did a nice job on the new variant of T-9 for 4.3. I do not use 75% of the enhancements
[Samsung Galaxy Nexus] frostysax:
This rom is by far the smoothest thing I have ever run on my phone hands down!!! You guys have done an excellent job on this one. My phone has become slippery with buttery smoothness.....keep up the great work!!!
[Samsung Galaxy Nexus] JFay22:
Well put. DHO's builds are like Vanir on steroids...but my battery doesn't pay the price. Perfect balance of features and performance. Thanks.
[Samsung Galaxy Nexus] t1.8matt:
Whenever I flashed B58 I noticed it's having the same truncated apps problem that PacRom is having. The bottom of some apps are getting cutoff. Anyone else notice this?
[Samsung Galaxy Nexus] MoNsTeReNeRgY22:
Yup, I noticed this as well.

The LTE quick toggle is also wonky. Always will stay on even if I click and turn it off.
[Samsung Galaxy Nexus] Citizen_Snips:
Phone will not boot after flashing golden kernel on b58. Didn't try other kernels yet, anyone else have any luck?
[Samsung Galaxy Nexus] lexdad86:
Worked fine for me with a clean install of b58 let it boot and settle down then rebooted into recovery and wiped dalvik and flashed newest golden without any issues and running so smooth
[Samsung Galaxy Nexus] Citizen_Snips:
Yeah, did that. Try rebooting the phone. Mine worked at first. Then rebooted and my phone nuked itself.
[Samsung Galaxy Nexus] trini.s2k:
whats the difference between software and hardware floating? i dnt understand what the meaning is ?
[Samsung Galaxy Nexus] lexdad86:
Yeah I've rebooted the phone multiple times with out issues on b58 with newest golden
[Samsung Galaxy Nexus] christianpeso:
How is data on this ROM? Switching between 3g and 4g? Switching from wifi back to regular signal? And coming out of airplane mode?