yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
Well mobile data works OK, once in a while though it just completely fails and when it does I haven't been by a computer to debug it before it goes away in the logs or something. The failure happens more frequently when Airplane Mode and/or LTE are toggled from what I've seen. When it does fail like that, turning on Airplane Mode for a couple minutes and then turning it off seems to fix it, also toggling just mobile data might work too. It looks like it's a problem with CyanogenMod 10.2 and/or Android 4.3 in general, however a few changes I made seem to make it happen less frequently and 3G <--> 4G LTE handoffs also seem to be improved.

ROM development update... I'm currently trying out building AOKP (Android 4.3-based), will update on how it goes after I get home from work, I leave in a little less than an hour and will probably be there at least 5 to 6 hours. It's funny how minimum wage jobs often require more physical labor than jobs paying twice as much for you to just sit in a nice comfy chair at a desk all day! :laugh:

EDIT: Got home from work, the AOKP build didn't complete successfully but it got much further than I thought it would and I know how to fix the error it ran into. So, good and bad news I guess? :)
[Samsung Galaxy Nexus] MWisBest:
Alright, AOKP looks like it will finish building successfully right now. Whether or not it boots is another story, but getting it built first is the important part. I put up a poll as I'm wondering what the current users of the ROM think I should work on.

I could keep building both CyanogenMod and AOKP, or I could do just one of the two. Doing only one would allow me to focus on that particular thing, rather than both things (however AOKP uses numerous CM sources so it'd be more like 1.5 things instead of 2). It would probably result in speedier fixes for issues and less work for me to do in general, but I don't want to stray away current users of the ROM who might prefer CM over AOKP.

The voting will not completely decide which I choose to do, but it will influence it greatly. Another option I could do to even out the load would be to focus on, say, the CyanogenMod build for a few days to a week and then switch over to working on the AOKP build for the same amount of time I did the CyanogenMod build. Major bugs would be fixed regardless of which build I was devoting time to at that moment, so if the AOKP build had a huge issue while I was working on CyanogenMod then I wouldn't just put off fixing it until it was time to work on the AOKP build.

Jeez, I certainly rambled on here, sorry lol. Just let me know what you guys think, thanks. :)
[Samsung Galaxy Nexus] 7175:
Hey MWisBest, really appreciate your work on your builds you've introduced, and your focus on improving data connection, something grossly overlooked. I really like the idea of some AOKP action, my pink unicorn does too. :) I just can't do the navbars in CM builds that are missing the side arrows for text cursor movement.

As for the data problems, I have some input from tests today. It's definitely useful for people who may be having 3g/data connection issues on groove ip, may the search results be with you!!.. I was messing around with the regulator voltages on styr's prima kernel. Basically lowering VUSIM, VAUX1, V1V2, or VANA below 2000mV resulted in a connection loss from groove IP, it absolutely wouldn't reconnect until all were at 2000mV+. I'm not sure what CM's stock values are hard coded to, but it might be worth checking out.
[Samsung Galaxy Nexus] MWisBest:
I double checked Fancy Kernel's code and all of those (I assume by V1V2 you meant V2V1, as I didn't see a V1V2) are hardcoded above 2000mV from what I can tell, and shouldn't be able to be lowered below it. Thank you for the idea though, I never really considered looking at the kernel as the culprit.

EDIT: Quick heads-up, I might be posting up a test build of AOKP 4.3 really soon. Flashing it now, if it boots I'll put it up.

EDIT2: Didn't even get a boot animation, haha. I think I might know why, I'll test now if I can fix it before I fall asleep! Pretty late here... *yawn*

EDIT3: Well I'm gonna call it a night and start building the hopeful fix so it's ready in the morning to test. Sorry for maybe being a *tad* too confident in this working right away, haha.
[Samsung Galaxy Nexus] modernbummer:
My preference would be for you to maintain CM only, but I suppose it depends on how ambitious you are. I'd hate for you to get burned out on a hobby...
[Samsung Galaxy Nexus] swarlesbarkely:
Obviously both would be cool but definitely not if its gonna be a ton of work. Its supposed to be fun to mess with your phone not work.
[Samsung Galaxy Nexus] Rushead:
I had just purchased the phone off swappa and it had been returned to stock, locked.

If you need a new sim, why would you not go back to stock? This has to be the absolute easiest phone to unlock, ever. I would back up all your stuff to a pc & wipe everything. Get your new sim & don't look back.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] hawkinsandponcho:
Flashed 9/10 build and ran into some MMS problems last night (not going through) and this morning. Fixed with a reboot.

I voted both CM and AOKP but I have almost no experience with AOKP and your CM builds have been great to a phone I thought was done from dying hardware. So CM would be my preference if I had to choose one.
[Samsung Galaxy Nexus] t1.8matt:
I know. It's just time consuming. The only reason I need one is from loading up roms back on 4.2 and for some reason at the startup screen they would automatically dial that *228 number or something and screwed my PRL up. I don't need it that badly and to get one and have a rom do that again and Mrs up my new sim card, I'm wondering if I should take that chance.
[Samsung Galaxy Nexus] MWisBest:
The new AOKP build didn't fix it, but based on where it's failing I think I know what the problem is, and it might be something applicable to the CyanogenMod build as well (might fix the troubles I was having with the ondemandplus governor and sioplus i/o scheduler, doubt it will effect much else though).

I do appreciate the feedback you guys have given about doing either AOKP, CM, or both.

I am thinking of another possibility now which I'd want you to vote on and provide feedback as well, I'll add it as a separate poll if it lets me. I'm thinking of maybe "mixing" AOKP and CM, merging in some of the cool features AOKP has with the rock-solid stability of CyanogenMod. This might be easier to do than getting AOKP alone working. The result and feedback from the poll on this will be very influential of my decision (like, 90% of my decision on this would be based on the feedback, with the 10% pretty much just being a tiebreaker) as it would result in the changes effecting every user of the ROM rather than offering a choice of which to use.

While this is a hobby, I really don't have a lot going on so I usually have a bunch of free time to just do whatever, and I enjoy computer programming and electronics in general so anything I do in my free time is usually related to that stuff anyways. I plan on majoring in Computer Science in college and I've already gone through all the classes they offered for it at my school, and took the AP Computer Science test and scored a 5 of 5, and nobody from my school has scored higher than a 2 before! I ended up being bored in Computer Science class at school as I had already learned a lot just from doing stuff like this, so projects I do like this end up benefiting me in life as a whole. :)

EDIT: Yeah, it won't let me add another poll as far as I can tell.
[Samsung Galaxy Nexus] bluerez79:
I like the idea of mixing the two ROMs together.
[Samsung Galaxy Nexus] modernbummer:
I'll second that. Although I'd like to keep CM's QS tiles for the camera tile.
[Samsung Galaxy Nexus] swarlesbarkely:
I think a merge would be awesome
[Samsung Galaxy Nexus] nitsua98:
CMKP: CyanogenMod Kang Project.
[Samsung Galaxy Nexus] swarlesbarkely:
That's legit
[Samsung Galaxy Nexus] Rushead:
Let's shorten it a bit...

CyanoKang Project?

Sent from a frequent flasher.
[Samsung Galaxy Nexus] nitsua98:
CyMoKaPr
[Samsung Galaxy Nexus] swarlesbarkely:
How about SFU -- Sid Forked a Unicorn
[Samsung Galaxy Nexus] MWisBest:
You shouldn't get any new issues if you are on super super old radios, but honestly I don't think there's any disadvantages of using the newest radios. Check out this thread here for some more info: http://xdaforums.com/showthread.php?t=1890585

From what I can tell, cMetal is just built with the Linaro toolchain (in somewhat better English, the code compilers) and not with all the changes Linaro makes to Android itself. Using the Linaro toolchain doesn't improve anything much by itself, it's all the changes that Linaro makes to Android to allow the compiler to optimize the code more that results in the top-notch performance of Linaro.

After I first flashed the ROM and switched to ART, it was a little laggy, but after a few minutes it seemed to level itself out. That could've just been what was going on.

Personally, I use the mini version of PA's gapps, and they have an 11/26 build of them out now which I'm using.

I'll look at the Expanded Desktop some more, maybe CM just isn't finished with it yet. As for burn-in... there's really not much you can do once it sets in. My phone seems to be doing alright screen-wise, but I got it in January of this year so it's a little under 11 months old, and it's a newer hardware revision so the screen may have been improved since the Galaxy Nexus's original release. How old is your phone?

Not sure what you mean by that, I don't have anything added for that...
[Samsung Galaxy Nexus] jrk190:
My phone is a revision 10. My friend has a revision 14, and he's got the problem, but not as severe. I'm not sure how old the phone is, I bought it off of Swappa about a week ago.
[Samsung Galaxy Nexus] bunklung:
How are data drops on this ROM? Does 4G drop out? I specifically set my phone to 3G now, because the 4G dropping is such an annoyance. I assume it's because we are still on 4.2 radios.
[Samsung Galaxy Nexus] MWisBest:
I'm going to guess that it's the 16GB model you have then? ^.^ Welcome to the small club of 16GB VZW Galaxy Nexus owners, lol. I wasn't aware there was a revision 14 (0xE)... unless that's toroplus (the Sprint model)?

I haven't had any issues with 4G LTE and hand-offs between it and 3G on 4.4, 4.3 was definitely more problematic than 4.4 is.
[Samsung Galaxy Nexus] David 617:
Does PGM work with this ROM? Does anyone know of a 4.4 kernel that supports PGM?

Thanks
[Samsung Galaxy Nexus] jrk190:
Nope, it's a 32Gb. The 14 is a Toroplus.
[Samsung Galaxy Nexus] vitokes:
Is anyone having trouble playing back recorded videos? Running latest build with no custom kernel or anything else. Using full gapps from pa
[Samsung Galaxy Nexus] sickopsycho:
Are you trying to play back videos you recorded with the camera in the gallery app? Ive found that any videos I record will open fine if i navigate to them in a file explorer, but gallery app has given me trouble watching a video.
[Samsung Galaxy Nexus] vitokes:
Yeah exactly like that record one and then swipe to the right and see it and then says it can't play video. Oh and I just saw I don't have original gallery for some reason but I got quickpic and it says the same. Also Google photos but I haven't checked with that.

---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------

Yup same problem from all my gallery apps. None will play the video. And I've tried to change the quality and still no playback.
[Samsung Galaxy Nexus] jrk190:
That's weird, mine is fine.
[Samsung Galaxy Nexus] xFaultx:
By kernel setting I mean like performance settings. It used to be on the settings page. Like what min, what max, whether you want it PowerSave or Ondemant or Interactive, etc
[Samsung Galaxy Nexus] vitokes:
Get trickster mod kernel settings in the play store. You can do that or go to performance in the settings.
[Samsung Galaxy Nexus] xFaultx:
Thats what I mean, performance isnt under settings in the latest version
[Samsung Galaxy Nexus] vitokes:
Weird... Mine is right there.

Sent from my Immortal Nexus!
[Samsung Galaxy Nexus] rice923:
From what I remember, it's always been there
[Samsung Galaxy Nexus] skylordusa1:
I might be missing something but did something change with google now in this latest build 12-2-13? I loaded the build with the latest full pagapps and I can no longer swipe to the left from my homescreen to access google now. I can swipe up from the home button and it brings up the ok google search screen but does not ask me to activate google now. Sorry if this was discussed already.
[Samsung Galaxy Nexus] Fluey18:
I'm on the latest build and just checked my Google Now. Works both from swiping to the right and from the home button.
[Samsung Galaxy Nexus] skylordusa1:
Did you do something to activate it. Like the first time you tried to access it did it ask you to activate it? Thats normally what it does for me and I say yes and then its available/enabled. But this time it didnt do it. It was working on the last build. Thats weird.
[Samsung Galaxy Nexus] Fluey18:
I did a dirty flash that might be why
[Samsung Galaxy Nexus] vitokes:
It might be possible that is turned off under settings... I do full wipes every time and it always starts turned off.

Sent from my Immortal Nexus!
[Samsung Galaxy Nexus] skylordusa1:
Ok yeah thats weird I did a clean install. But I just went in and clear data for google search and when I went back into search by swiping up on the home button it had the little message in there that said get google now. So I got it and its working now. All is right in the world. Thanks for the quick replys. I should have tried that first before posting hahahahha.
[Samsung Galaxy Nexus] lablunk:
I'm getting a Status 7 error when installing. But when I check the updater script it lists the toro. Ideas?
[Samsung Galaxy Nexus] Fluey18:
Do you have the latest recovery installed?
[Samsung Galaxy Nexus] sickopsycho:
This kernel does not have many options as far as overclock. Actually it doesn't have many options period, its pretty standard. I normally use mpokang kernel and trickstermod to adjust.

Changing gears I'm sure I'm missing something but under the setting for expanded desktop the option to turn it on is greyed out. Can't enable it... Could be related to my adjusted DPI? Idk...

Sent via Galaxy Nexus Life completely Forked.
[Samsung Galaxy Nexus] Fluey18:
Which area of settings are you looking at? In Interface or Fn Buttons/Power menu? It must be turned on in Interface before you can add it to the power menu.
[Samsung Galaxy Nexus] MWisBest:
The problem is now having the latest recovery installed, you need TWRP 2.6.3.1 or CWM 6.0.4.3.

Also, the Performance settings in the Settings menu is there, you just have to enable Development Settings in order to see it I think (go to About Phone and keep tapping on the Build Number thing until it enables Development Settings).

BTW, I was sliiightly wrong about the Fast Charge thing: It does require activating it via the sysfs interface like before, however it does NOT take away the ability to use USB MTP, ADB debugging, etc. while in use. Rather than making the phone think it's connected to an AC charger, it simply makes it charge at full power on USB (while still treating it as USB).
[Samsung Galaxy Nexus] metalspring:
Where did you find that commit? I've been looking for that type of fast charge commit for awhile and never can find it
[Samsung Galaxy Nexus] sickopsycho:
derp. thanks =)
[Samsung Galaxy Nexus] xFaultx:
Odd I dont have it, but I had it in the previous build. I did an install right ontop of the old OS, so possibly that caused a problem
[Samsung Galaxy Nexus] chris157:
Since updating to the latest build I can't get get the camera or gallery to install. I've tried the full gapps package and the photosphere add-on but they won't install it. Any suggestions?
[Samsung Galaxy Nexus] Nephilim:
Flash the photosphere zip found here in my Android Drive folder, it's modified specifically for Toro, should give you back gallery and camera with working photosphere. ;)

https://drive.google.com/folderview?id=0B_HqOdvKZoQheGJYMlpjZmZTT0k&usp=sharing
[Samsung Galaxy Nexus] kb8no:
Exactly same problem. Full and full modular both fail to install gallery and camera. What's the deal?
[Samsung Galaxy Nexus] Nephilim:
See my post above yours. ;)

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] kb8no:
I'm sorry but... /rant

Spent hours tonight trying to trouble shoot something very important like camera and gallery. I read every post but maybe missed something. Shouldn't this be in the OP? /shrug. Tired. Hope I didn't offend anyone.
[Samsung Galaxy Nexus] Nephilim:
I modified the script in that myself. If it fixes the problem for anyone with an issue I don't care who puts it where. :)

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] kb8no:
It works. Thank you!
[Samsung Galaxy Nexus] Nephilim:
Glad it helped. ;)

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Enter The Nexus:
Does this work with BaNKS?
[Samsung Galaxy Nexus] kb8no:
Just exactly where do I toggle quick charge? I don't see it in trickster.
[Samsung Galaxy Nexus] kb8no:
Where or how do you engage fast charge?

Sorry for the double post. Tapatalk issue again.
[Samsung Galaxy Nexus] hotrodwinston:
Trickster changed the way it is laid out - tap the three lines by the app name in the action bar up top.
[Samsung Galaxy Nexus] Rushead:
Yeah, not a fan of removing functionality. Why take away the ability to swipe?

Sent from a flashead cracker.
[Samsung Galaxy Nexus] Shadowlore:
Ok.. so ran into a weird quirk between last night and this morning.

Brief Rundown:

Was running the Nov 25th build, Mpokang v10, PA Gapps (Full)

Device was running very smooth, no bugs, hitches or anything.

Anyhow.. last night, was on the phone with my mother and mid-conversation the phone rebooted. Ok.. fine.. it happens.. simple bug.

I went through the rest of the night, using the phone after reboot and went to bed. As I plug my phone in, next to the bed, I always hit my tasker toggle for 'Sleep' mode. (Turn off wifi, Bluetooh, turn off sync, set brightness to low as possible)

Anyhow.. my alarm wakes me up this morning, and par usual, while I'm getting dressed, I hit the 'Awake' tasker shortcut. (Turns on wifi, BT, enables sync, brings brightness up to 30%, and finally... reboots the phone, so I have a nice clean start up every day)

Now, this is where it gets quirky...

It finishes rebooting, I unlock it.. and... I'm staring at the CM Setup screen again. Thinking this might just be another bug.. I reboot the phone again, manually this time.... and it comes back to the CM setup screen again.

Ughm.. ok.. maybe the thing is doing an auto update.. if so.. kind of cool... if unexpected. Walk through it, and there's not much to the steps, just asking me to select my region/language, do I wish to enable error reporting and GPS.. and then it launches into the home screen again.

GEL is still there... all well and good...except.. something is wrong.

After double checking.. some of my apps are missing. I don't mean broken, or corrupt.. I mean.. completely missing (gone without a trace, not even in the system). Other apps have been mysteriously reset to an earlier point in time.

List of issues so far:

Beautiful Widgets,

Tasker,

Email is completely reset,

Google Currents is finally gone (Even though, when I'd try to go into it even since it was 'integrated' into Newsstand, it'd just launch Newsstand)

Newsstand just marked everything since Nov 25th as 'New'

Google Rewards has been reset

Gmail has lost all of it's custom setup I've done to it, and has reported any/all emails since Nov 25th are 'new'

Falcon's Donation link is still there, but Falcon Pro has been removed

Facebook reset

Google+ Reset itself back to Nov 25th status

Many Root level apps have no SU permissions now (in fact, SuperSU is the only one that DOES still)

Other things are working without a hitch.... so.. yeah.. no idea what happened.

Going to update to the latest build today, but damn if this isn't the weirdest thing I've seen happen in awhile.
[Samsung Galaxy Nexus] metalspring:
Disable dynamic fsync

What you are describing seems to be a case of data corruption due to fsync being disabled (Dynamic fsync enabled means fsync is off while the screen is on but fsync is on while the screen is off)

Disabling dynamic fsync makes sure fsync is always on to prevent data corruption in the event of an unexpected reboot or power down (like a random reboot, pulling the battery while phone is on or the battery dying)

Edit: you may want to do a full wipe when flashing the newest build to ensure none of the corrupted data is left to cause issues
[Samsung Galaxy Nexus] Shadowlore:
From what I recall, however, it wouldn't be normal for fsync to lose a full weeks worth of data, would it? I've seen dynamic fail in the past on another device, and I lose a day of data (slightly annoying, but recoverable) but losing a week seems a bit more extreme.

Will try to disable it, regardless (I believe Trickster has a method to do so).. and yeah, I never do dirty flashes.. always do clean installs from scratch when I can. (A lot easier to avoid problems that way :)
[Samsung Galaxy Nexus] jrk190:
So today I'm getting much better battery life. 3 hrs and still at 87%, which is my best so far. I'm going to compare it to another GNex soon. Also going to update an SII and GNex to CM10.2 Stable. Looks like official builds will be out soon.
[Samsung Galaxy Nexus] snowcraig:
Anyone else getting an error when flashing PA Gapps full? I am on the latest TWRP.
[Samsung Galaxy Nexus] MWisBest:
What in the hell... I honestly have no idea how that can happen. The only thing I see is that for some reason you're using SuperSU... Superuser is included with the ROM, it's built right into the Settings, so installing SuperSU is not only pointless but probably a bad idea overall.

As for toggling Fast Charge, /sys/kernel/fast_charge/force_fast_charge is the "file" that is modified... it is (by default) 0, which means to not force fast charge, but changing the 0 to a 1 will turn on fast charge. In the Terminal Emulator I think you can just do:

echo "1" > /sys/kernel/fast_charge/force_fast_charge

as root to turn it on.

I'm thinking of turning on fast charge by default in the next build, any objections to that?
[Samsung Galaxy Nexus] Shadowlore:
*chuckling* Glad to see I'm not the only person who uttered those words this morning when I saw what happened ;) I'm in the process of re-installing everything from scratch right now with the newer build. Once installed, I'll do a full nandroid of it and not only attempt to not use SuperSU (though, I'll freely admit, I trust Chainfire) but I'm going to look into disabling dynamic fsync if the issue rears its head again.

Thanks :)
[Samsung Galaxy Nexus] sickopsycho:
Ok can't remember if I read it here or elsewhere but I just experienced the "recent apps" bug. Went to open quick pic and it opened hangouts. Closed hangouts, tapped quick pic icon and again, hangouts. Wtf? Had to back back back up and finally got to quick pic. I had shared a picture in hangouts so when I tried to open quick pic hangouts kept opening since that's the last place I was in quickpic

Sent via Galaxy Nexus Life completely Forked.
[Samsung Galaxy Nexus] sickopsycho:
Do it. =)