yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] almahix:
YES and it's making me crazy. Apop recommended Swype and it works really well. No more disappearing keyboard!
[Samsung Galaxy Nexus] Kaptinkrunk:
but swype isnt themed up all pretty is it?
[Samsung Galaxy Nexus] dereaper:
do you want a pretty keyboard or a working one, I just use the Google keyboard from market and it seems to function perfectly
[Samsung Galaxy Nexus] apophis9283:
I use ai keyboard and im in love with it. Best keyboard hands down
[Samsung Galaxy Nexus] player911:
So the disappearing keyboard is just the AOKP keyboard being stupid?

I really love the stock AOKP keyboard. I've tried others and I guess it would be good to have a second keyboard as backup in case of emergency. I'm not a Swype fan. I've used AI KB. Might give that one a go. I'm also assuming it hasn't been resolved in the latest nightly?

I'm also debating on getting a Verizon G2 or just holding out on my GN. I've never kept a phone this long.
[Samsung Galaxy Nexus] dereaper:
well the Google keyboard. is pretty much the stock keyboard it just always works
[Samsung Galaxy Nexus] almahix:
Just not for everyone.
[Samsung Galaxy Nexus] Kaptinkrunk:
actually thats the keyboard i use with other phones but if its rooted ill use the stock swypy
[Samsung Galaxy Nexus] furiyk:
What causes a lan wakelock? I'm on the newest nightly and lean 8.3. I dirty flashed from the previous nightly but didn't have any lan wakelock.
[Samsung Galaxy Nexus] mightymegit:
Wait it out until the Nexus 5 is announced! Then make your decision. That's what I'm doing!
[Samsung Galaxy Nexus] almahix:
I finally caved and bought the G2. The nexus 5 may be juicy but vzw is the only viable carrier here. I liked the Note 3 but it was too large to comfortably hold, for my old hands anyway. I love the G2. It was easy to root and load twrp. I'm still stock but there are several custom roms, unfortunately no aokp afaik. Still have my trusty Gnex, but WiFi issues were making me crazy so I decided to use my upgrade. I lost unltd data, but I got 6gb for the same price, and that is way more than I use as I am on WiFi 99% of the time.
[Samsung Galaxy Nexus] apophis9283:
Ill be getting out a new build probably tomorrow. I was using linaro 4.7 for both rom and kernel, switched it to 4.8 for rom and kept kernel at 4.7. The kernel never boots if I use 4.8 for it so its staying at 4.7
[Samsung Galaxy Nexus] kinfolk248:
hey, new to this rom thinking about trying out....is this more of a feature packed rom or what?
[Samsung Galaxy Nexus] t1.8matt:
pretty much standard AOKP with optimizations and active display added in. a nice job done by Apophis, i'm sure you would like this rom if you like AOKP features.

---------- Post added at 09:16 PM ---------- Previous post was at 09:15 PM ----------

G2 locked down bootloader wise? no custom kernels ever going to be available for it?

edit: nevermind, answered my own question by looking. Pretty locked down. They do have AICP which is AOKP and Carbon for the VZW G2.
[Samsung Galaxy Nexus] almahix:
The bootloader is indeed locked, but the brilliant developers created a workaround allowing us to root and install twrp, and the new roms and kernels. I'm hoping for an AOKP, but I am grateful that some devs are already supporting the platform.

I am still going to maintain the gnex, but I will probably sell it or give it to someone who needs a phone and can't buy one. It is still an outstanding phone.
[Samsung Galaxy Nexus] t1.8matt:
I know the dev of Mpokang could use a new Gnex to get his kernels back up and running. Same with Amperific who make ASKP kernel.
[Samsung Galaxy Nexus] kinfolk248:
lol well im used to sourcery, and those guys had features out the a$$ but ya know...
[Samsung Galaxy Nexus] apophis9283:
I am obsessed with 80's music. That is all :)
[Samsung Galaxy Nexus] almahix:
The 80s music sucked! I'm reliving the 60s!
[Samsung Galaxy Nexus] apophis9283:
I consider all of you friends. lets do the S-s-s-s A-a-a-a F-f-f-f E-e-e-e T-t-t-t Y-y-y-y DANCE LMAO
[Samsung Galaxy Nexus] almahix:
Wwwww-Hhhhh-Aaaaa-Tttttt?
[Samsung Galaxy Nexus] apophis9283:
Yep, its that bad. Would you believe Im a huge Pantera, Manson, Avenged Sevenfold fan? I have the widest variety in music taste.

I want to make a heavy metal version of Push It by Salt N pepa....
[Samsung Galaxy Nexus] almahix:
Variety is the spice of life. I am not only an Android fan, I'm also a 60s rocker. I also sing opera. When I wasn't writing software for the Navy I was performing Gilbert & Sullivan, Strauss, Mozart, Offenbach, etc. Today I sing in the shower. (And the car. Hopefully no one is watching.)
[Samsung Galaxy Nexus] kinfolk248:
this rom have halo??
[Samsung Galaxy Nexus] apophis9283:
No, hit the thanks instead of reply....
[Samsung Galaxy Nexus] apophis9283:
I should be updating today, hopefully I dont havd any issues

Like I said, I also updated the ROM to build with Linaro 4.8, not sure if its going to have a huge impact or not. Well see.
[Samsung Galaxy Nexus] kinfolk248:
if this rom had halo it'd be perfect but hey if my hummer got 35 mpg so would it but hey.....

ps - i dont have a hummer lol
[Samsung Galaxy Nexus] apophis9283:
looking like a tomorrow release
[Samsung Galaxy Nexus] Skurvy_Pirate:
RAM issues

Anyone else having RAM issues? Since going from 4.1 to 4.3 I have been having issues with RAM. I think 4.1 is more notorious for memory leak issues so it's funny I never saw it on 4.1, but am seeing it on 4.3, go figure....

Anyways, under running apps I usually have <20 MB free, which is good because the system is using it right? Except that it is killing apps that I am currently using. A lot of times as soon as I let an audio player lose focus (go to desktop) it will stop playing audio. Tasker keeps getting killed and restarted, and the majority of the running apps are always in the "restarting" state.

If I calculate how much RAM they are using, it doesn't come anywhere close to the ~685 MB that it says I am using (I know system uses a lot too). But just watching the running apps, they are constantly getting restarted and when something dies and frees up memory, it instantly gets used. For example, my audio app just died, the free RAM jumped to ~40 MB, then got sucked down to ~5 MB, then some more stuff got killed and it went up to ~25 MB, then right back down to 8 MB.

I am running aokp_toro_jb_mr2_unofficial_2013-10-17 and have tried reflashing with no success.

Edit: I have a Tasker task that reboots my phone every night from when I had the slow memory leak issues on 4.1. Rebooting helps in this case too, but it gets back into the bad state pretty quickly
[Samsung Galaxy Nexus] drxikh:
I'm actually seeing the same things happen, but I'm using the 10.22 build with Fancy Kernel pre-44 big. I also experienced it with mpokang build 9 1080.

I could not use pandora and navigation at the same time. When I tried to switch to one the other one closed.
[Samsung Galaxy Nexus] jonstrong:
What launcher are you guys using? Maybe not at all related to what you're describing re: memory leak, etc, but: I had been a confirmed Apex Pro fan for a long time. Also have Nova Prime, and had switched back and forth and, finally a few months ago, settled on Apex for my toro and manta. In recent months, though (maybe since 4.3?) Apex seems to start redrawing a LOT more often than I ever saw before, even though I've got it set to stay in memory. I had this on both the N10 and the GNex. Out of curiosity, I replaced Apex with Nova on the N10 -- and this seems to have stopped happening on that device -- but with Apex on the GNex, I continue to see Apex restarting, maybe as often as 10 times in a day, and, btw, the device becomes sluggish shortly before the restart.

Going to try Nova on the GNex and see how it compares once again.
[Samsung Galaxy Nexus] almahix:
I too went back and forth between Nova and Apex, but decided a while ago to stay with Nova. It just seemed the most responsive.
[Samsung Galaxy Nexus] Skurvy_Pirate:
I'm using Nova. I get redraws when I got to desktop now, but haven't before in a long time (except rare ocassions). Now it is happening every time, guessing because the launcher is getting killed just like any other app when it isn't in the foreground.
[Samsung Galaxy Nexus] apophis9283:
This next build has a lot of stuff to it. Its still linaro 4.7. Next build will hopefully be sabermod 4.9, which should be a lot better than linaro 4.7.
[Samsung Galaxy Nexus] drxikh:
Yea same for me. I think this has only been happening since the 10.22 build for me though.
[Samsung Galaxy Nexus] apophis9283:
New build up. Try that out and see if it continues. Next build will hopefully be compiled with SaberMod 4.9
[Samsung Galaxy Nexus] apophis9283:
Hell yeah! ROM compiled with SaberMod 4.9 and kernel with Linaro 4.7 (13.09) and it compiled fine with 0, thats right 0 issues. It boots!
[Samsung Galaxy Nexus] kinfolk248:
0 issues meaning data reconnects, ram leaks plugged, and whatever else i cant think of lol?
[Samsung Galaxy Nexus] apophis9283:
Thats not related.
[Samsung Galaxy Nexus] apophis9283:
I will have another build up soon, no changelog. Know that its compiled with SaberMod 4.9 and it does have more stuff than the last build. A lot of fixes that were reported to AOKP and some gallery2 stuff... As long as it doesnt error out compiling although good so far.
[Samsung Galaxy Nexus] kinfolk248:
Hmmm interesting, wondering what he means by more stuff... Lol
[Samsung Galaxy Nexus] apophis9283:
There were 2 frameworks base commits that fixed some user complaints and a dalvik commit with the same. Some gallery2 stuff as well
[Samsung Galaxy Nexus] jonstrong:
Looking forward to this...but it's 12:15am here, my alarm goes off at 5:30...and I do this more nights than not (big mistake). I'll have to wait till morning to give it a spin... :(
[Samsung Galaxy Nexus] apophis9283:
Its uploaded, enjoy!
[Samsung Galaxy Nexus] furiyk:
The lte toggle still is broken :( and the install script still says linaro, but so far so good
[Samsung Galaxy Nexus] apophis9283:
I pushed 2 build very close together. I know the script needs to be changed. I have no clue why the LTE toggle isnt working.....

Edit: Fixed the script to reflect SaberMod. Now. Can someone get me a logcat of the LTE toggle? Maybe just maybe I can find an error.
[Samsung Galaxy Nexus] t1.8matt:
What's the benefit of having sabermod? Better than linaro?
[Samsung Galaxy Nexus] nalanotae:
Lock screen wallpaper not sticking

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] apophis9283:
Sabermod is apparently specifically made for aosp.
[Samsung Galaxy Nexus] apophis9283:
Im not understanding why toro builds are having so many issues. My note 2 is flawless running like a scalded dog. Now, I havent tested lockscreen wallpaper but I will to test
[Samsung Galaxy Nexus] nalanotae:
I was going to deal with the airplane mode bug but I got frustrated when my lock screen wall paper wouldn't stick. From what I could tell tho it seemed to run smooth. If you get the lockscreen wallpaper fixed I will retry

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] apophis9283:
Its hard for me to diagnose. I dont have mine anymore. I honestly should have kept the device.
[Samsung Galaxy Nexus] stalls:
I can tell u that the new build fixed the audio headphone Jack from disconnecting every half second... But yes the lte toggle still is a problem. Thanks man! Keep it up

:edit: never mind it had to do with headphone volume boost
[Samsung Galaxy Nexus] Skurvy_Pirate:
Tried the new build and I get no cell connection now and my wireless connection will stay gray. Flash it again and the whole wireless icon is gone now:

Also the keyboard was crashing whenever I tried using the built in "swiping" to type. I guess I will try a complete wipe and clean install now. I am not sure if I should stick with the newest or go back to a previous version?
[Samsung Galaxy Nexus] apophis9283:
Im wondering if the fact that the toro never got an official bootloader has something to do with some of these issues
[Samsung Galaxy Nexus] chaoslimits:
Maybe these are dirty flash issues? I don't have any issues with the latest build. I always clean flash new builds.
[Samsung Galaxy Nexus] metalspring:
as far as i know the bootloader is identical for all galaxy nexuses, same as kernels?
[Samsung Galaxy Nexus] Skurvy_Pirate:
After doing a completely clean flash (wiping everything except SD card), I am getting WiFi and Cell service now. There were also some previously installed apps that were missing before...that was really weird.
[Samsung Galaxy Nexus] apophis9283:
I dont think so. Your talking gsm and cdma. There has to be differences
[Samsung Galaxy Nexus] apophis9283:
Guys please remember. I dont want any bug reports unless you clean flash.
[Samsung Galaxy Nexus] almahix:
I have always clean flashed unless it specifically says it isn't necessary. I used the galaxy nexus wipe tool as twrp was said to have thorough wipe issues.
[Samsung Galaxy Nexus] apophis9283:
The only thing that everyone seems to be having issues with is the LTE toggle. Which I have no idea why its not working. Nothing I modify should affect it
[Samsung Galaxy Nexus] t1.8matt:
bootloaders are the same throughout the variances of the Gnex.
[Samsung Galaxy Nexus] quezpr123:
I was running marclandis 10/25 build before your latest with the same LTE issue. LTE toggle has been this way for aokp 4.3.1 on toro since it was updated from 4.3, from what I can recall at least. Point is it's not something you did. It's something the team has to fix. Or maybe I'm wrong

EDIT: before that I was running whitehawk 10/22 build and it had the LTE toggle issue
[Samsung Galaxy Nexus] quickstang:
Going from build to build I never clean flash. No reason to. Dalvik & cache are all you need. I load my nightly or whatever in goo manager, select the kernel, banks gapps, photosphere & flash away.

If I was going to a different individuals rom I'd clean flash. AOKP back & forth, not needed.

apop, tested the lte for the heck of it & yeah, it doesn't work. Never use it, or could care less if it works or not, but I know some use it.

Sent from my iphone killing Galaxy Nexus running whatever kernel & rom I feel like. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] apophis9283:
Yeah not sure whats going on. Kinda weirded out
[Samsung Galaxy Nexus] apophis9283:
I need you all to tell me what network mode you are using. Im looking at the lte toggle code now. No promises
[Samsung Galaxy Nexus] Beamer9408:
I always wipe /system cache and dalvik cache but that's just me I have seen problems from not wiping /system. That's still considered a dirty flash.
[Samsung Galaxy Nexus] drxikh:
anyone having problems flashing fancy kernel pre-44 big? i'm getting the com.phone.android not found (or something like that)...i got mpokang v10 to work.
[Samsung Galaxy Nexus] t1.8matt:
Does anyone that flashed the newest build have working data? I flashed it and had no bars and no data connection. I might try another reflash in a little bit.
[Samsung Galaxy Nexus] jonstrong:
Clean flash?
[Samsung Galaxy Nexus] t1.8matt:
yup, i don't do the dirty
[Samsung Galaxy Nexus] apophis9283:
Someone else had that issue but was fixed with a clean flash. Try flashing again.
[Samsung Galaxy Nexus] t1.8matt:
i'm gonna give it another go tomorrow. i'm too tired to be messing with my phone right now. i feel like i'm getting burned out on flashing lately.
[Samsung Galaxy Nexus] almahix:
Some say it doesn't make a difference but I believe otherwise, from experience. Especially if one doesn't and something goes wrong.
[Samsung Galaxy Nexus] chaoslimits:
So is there a trick to transparent navigation bar? I can't seem to get it to work this time.
[Samsung Galaxy Nexus] quickstang:
No issues here. Dirty flashed. You may check network settings. Sometimes the data section gets unchecked for some reason.

Sent from my iphone killing Galaxy Nexus running whatever kernel & rom I feel like. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] mrdunn:
my first flash was dirty from the earlier one yesterday and no data. Reflashed clean and data has been great, no hand off problems
[Samsung Galaxy Nexus] dereaper:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

well this is by far the best release yet ! XD thank you
[Samsung Galaxy Nexus] apophis9283:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Dont be mad, but Im getting ready to release a newer build in about 30 minutes. I will have a non-Aroma build and an Aroma build. Some new stuff in there. Not alot though.

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] dereaper:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

awesome lol why would I get mad bro I've been running this build all day just didn't have time to reply at work
[Samsung Galaxy Nexus] joeyc1123:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

I know u don't recommend it but if I were to dirty flash this, should I flash the non-aroma?
[Samsung Galaxy Nexus] apophis9283:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Ive never dirty flashed. I say this. Its 100% fine with me if you dirty flash. Issues caused by dirty flashing should not be posted. As far as which one to use. I honeslty dont know. Its going to be a trial and error type thing. As I personally dont dirty flash, I honestly dont know.

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] joshuajones:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

I tried it last time and it didn't work. Google setup was messed up. So I would clean flash if you want to switch to non - Aroma build
[Samsung Galaxy Nexus] apophis9283:
Also, when you see the changelog dont flip out. They have officially merged most of the stuff. So its still there.
[Samsung Galaxy Nexus] joeyc1123:
Re: [2.12.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Thanks guys. I will try with non aroma (just makes better sense to me) and if it fails i will do a clean. On another note, i must say that i personally benchmark ROMS by playing graphically intensive games(i.e. modern combat 4) and i dont know if it is because of linaro but this ROM definitely gets the best FPS. I just wanted to give the dev(i know u dont consider urself a dev) mad kudos on this project. Really though, awesome job on this ROM!!!
[Samsung Galaxy Nexus] apophis9283:
Thank you kind sir. Glad you enjoy it.

Edit: OP has been updated.
[Samsung Galaxy Nexus] skrowl:
Latest AOKP (MR1 build 3) has a confirmed wifi bug that keeps wifi from connecting. Has anyone had a chance to test wifi with this kang?
[Samsung Galaxy Nexus] apophis9283:
Wifi is fine on this build. I just said something in that thread about wifi is fine here.
[Samsung Galaxy Nexus] skrowl:
Sorry. I did 'search this thread' before I posted but I must have missed it. Downloading now!
[Samsung Galaxy Nexus] joshuajones:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Actually I have noticed it. I wasnt able to connect to my wifi and it said "avoiding poor connection", even though I have that setting disabled.

Only happened twice, and rebooting fixed it..
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

I swear ive have never had an issue with wifi. Not 1 time. It always connects on the first try. This is the first time ive ever heard this.

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] skrowl:
http://xdaforums.com/showthread.php?t=1844777&page=121 WiFi broken posts starts around the 3rd post from the bottom
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

I was talking about my build.

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] joshuajones:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

I switch between wifi and 4g like 10 times a day without a problem other than those two times. And even then I was rather far from my router, so I didn't think much of it
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

I added a commit the should help with 3g to 4g switching and handling. Would like to get feedback on that. Although it may be hard to see a "big" difference.

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] t1.8matt:
downloading now. thanks for giving us the non aroma version.
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

As long as you all are happy. Im happy.

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] apophis9283:
Ugh, how i feel about compiling sometimes
[Samsung Galaxy Nexus] apophis9283:
I will probably be moving to a different site soon. If you would like to follow me I will post links.
[Samsung Galaxy Nexus] jonstrong:
Please do!
[Samsung Galaxy Nexus] cat_patrol:
Where ya thinking?
[Samsung Galaxy Nexus] apophis9283:
Probably android-edge. As I have posts already there. I know the owner. Crap hit the fan in my i605 thread and I feel I was treated wrong. Facism is the only word that comes to mind about the situation.
[Samsung Galaxy Nexus] almahix:
Lead on. We'll follow! Well, I will anyway.
[Samsung Galaxy Nexus] apophis9283:
Moved to droid hive
[Samsung Galaxy Nexus] jonstrong:
See you there! :good:
[Samsung Galaxy Nexus] drxikh:
for the lazy link us please =].

edit. nvm found it...linky
[Samsung Galaxy Nexus] apophis9283:
MODS, please shut down this thread
[Samsung Galaxy Nexus] Jonny:
Thread closed at OP's request.
[Samsung Galaxy Nexus] donnyp1:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Damn man! Your fast. Last nights build is doin fine. Is there enough changes to update?
[Samsung Galaxy Nexus] apophis9283:
Damnit something went wrong and not all the changes ended up in the changelog. Theres more changes than whats in the changelog. Ill see if I cant find my changelog. The changelog from Aroma shoudl be correct. Ill see if its right and if it is ill re-do the op changelog.

Edit, just looked at the aroma changelog, its not right either

Edit - Edit. I am burning an Xbox game on my PC at the moment. When it's done I will boot into Linux and see if the original is still intact
[Samsung Galaxy Nexus] shpitz461:
here's my consumption with the build from 2/1
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Ok guys. Heres whats up. Download an install lockscreen policy from the market. Thats a temp workaround until i come out with a build with that merged commit. This workaround came from aokp themselves

Expect a build tomorrow with this fix

http://gerrit.sudoservers.com/#/c/5515/

TBH I may work on it tonight, no promises though

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Tested the fix. Works perfectly

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] shpitz461:
Are you referring to the memory issue?
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Yes. This 100% fixes the ram issue. My builds have never had an issue with wifi. As soon as I can merge the fixes. This build will be back to 100%

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] shpitz461:
Man, you are a machine! :)
[Samsung Galaxy Nexus] apophis9283:
Re: [2.13.13] [rom] [aokp] [aroma] [linaro] [lots of options]

Just use the fix as stated above. Download that apk from the market. Turn everything off and my build will be quick as it used to be

Sent from my Gnex running the most awesome AOKP build
[Samsung Galaxy Nexus] shpitz461:
I'm going to wait for an official build :)

There's not rush, it's the wife's phone anyway and she really likes the build from 2/1.

I plan to reflash hers tomorrow night or over the weekend, no rush :)