yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] simonbarsinistr:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/28/13] [UNOFFICIAL]

I don't get that anymore! I'm still looking to improve my phone and stay as current as I can while maintaining functionality. But then I have other devices that I flash just for fun cause I don't have to rely on them!

I like the additions you've been talking about, and you show good judgment about your builds. You note your additions on the OP, so no one should be caught by surprise by any of the changes. I'm definitely going to try the new build now! Not having the lte toggle wasn't bad, but it's convenient to have it for sure!
[Samsung Galaxy Nexus] jlvlawrence:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/28/13] [UNOFFICIAL]

I'm all for the LTE toggle!

Rock Chalk Jayhawk!
[Samsung Galaxy Nexus] rmonjay:
I installed the new custom build and it works great. The LTE toggle works as it should and everything else is like butter.
[Samsung Galaxy Nexus] Grizzly420:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/28/13] [UNOFFICIAL]

Sounds good to me. I am done cracklashing for awhile. I just need something to update once a week or so and everything pretty much work lol
[Samsung Galaxy Nexus] simonbarsinistr:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/28/13] [UNOFFICIAL]

I'm getting some artifacting on some animations, including with PIE on white bachgrounds. Anyone else seeing anything like that? I'm just using this rom all stock (lte toggle version).
[Samsung Galaxy Nexus] jreyno10:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/28/13] [UNOFFICIAL]

Yeah I've noticed it some in the recent apps window. Especially in tablet ui. No big deal for me though. Everything else is working perfectly.

Sent from my Nexus 10
[Samsung Galaxy Nexus] simonbarsinistr:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/28/13] [UNOFFICIAL]

Yeah, you're right, it's much better in phablet UI. I use expanded desktop, so the only reason I use tablet is for the pop up notifications, but they're not a big deal since I have a pebble anyeay, and I get the notifications on my wrist.
[Samsung Galaxy Nexus] fairct:
I haven't noticed any artifacts, but that doesn't mean they aren't there.

Thanks for the feedback guys! I'll keep toggles in, and get to work on making that bluetooth audio revert zip I said I'd make. I'll update the OP with the changes I've made from stock.
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

Same here, no artifacts at all.

Sent from my AK Diamond Powered AOSPA 3.15 Galaxy Nexus
[Samsung Galaxy Nexus] sickopsycho:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

Question... is this AOSPA build similar enough to jaybobs build that I can dirty flash this over it? I'm just wondering because I like the frequent updates of this thread and would like to jump over but I don't really want to do a fresh install. I suppose if no one really knows I can make a backup and Guinea pig it...
[Samsung Galaxy Nexus] rmonjay:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

I have moved back and forth between the two threads by dirty flashing with no bad results so far (knock on wood)
[Samsung Galaxy Nexus] sickopsycho:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

Sweet, thanks for the input. I'll give it a shot.
[Samsung Galaxy Nexus] Nephilim:
They are pretty much the same build although I like fairct's better and it is updated frequently. If you ever have an issue with slowdown checkout the 3rd link in the hidden part of my signature. ;)
[Samsung Galaxy Nexus] Droidlovinyogi:
Thanks for another fantastic build!
[Samsung Galaxy Nexus] jlvlawrence:
Re: [ROM - AOSPA - 4.2.2] PARANOIDANDROID 3.15 [Toro] 25-MAR-2013

I'm getting great battery life with the latest build and latest diamond kernel. The only kernel setting that I changed was to over clock to 1.35. I'm using the 2100mah extended battery. 2 1/2 hours of screen on time. I'll take it!

Rock Chalk Jayhawk!
[Samsung Galaxy Nexus] dp917:
Anyone have trouble seeing the Google Search update? I just flashed this today along with the latest PA Gapps (32913) and did doesn't show up. When looking online at the play store it stays incapable with my device. I came from the official aospa and am pretty sure it showed up then. The app does work. Also when searching all available google apps all I get are voice search, google+, play magazines, and translate.
[Samsung Galaxy Nexus] sickopsycho:
Is this possibly because they are installed via the gapps flashable .zip as system files and therefor do not show updates on the play store? Just a shot in the dark... I'm pretty sure that when you flash the gapps package that all those apps ARE installed as system apps and you can't update them regularly like you would from the play store. Correct me if I'm wrong, but I believe you either have to not flash the gapps package and then download all your apps from the play store or if you DO flash the gapps package then you need to wait for the next flashable package to come out in order to update those apps.
[Samsung Galaxy Nexus] dp917:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

Yea they show as system apps when looking online. I think it has something to do with that new version of gapps, I have the last version on my Nexus 7 and it seems fine.
[Samsung Galaxy Nexus] rmonjay:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

You can delete the apk from the system/app folder and then install from the play store. Actually, I'd move the apk to the sd card so you can put it back if the play store version doesn't work for you.

You will have to redelete it if you reflash.
[Samsung Galaxy Nexus] fairct:
I didn't flash the ROM today, but I did pull down the search update today. It seems to work OK for me, not that it's much consolation.
[Samsung Galaxy Nexus] dp917:
Re: [ROM] [4.2.2] AOSPA 3.x TORO PARANOIDANDROID (SEMI)NIGHTLIES [03/28/13] [UNOFFICI

Okay I seem to have it working. Tried uninstalling and download from play but didn't work. I restored my official pa and 30913 gapps backup and it was still messed up. There were other none Google apps that weren't showing up too. I reinstalled this pa with the 32913 gapps again and so far play store is working right. Doesn't make sense why it didn't even work on my back up but is now on a dirty flash.
[Samsung Galaxy Nexus] Nephilim:
Hey if I am using the 3/28 build there is no need to update to the 3/29 build you have on the front page right? Everything is working fine for me.
[Samsung Galaxy Nexus] Natef53:
I just wanted to say, thank you! I had never heard of "team baked" so I just downloaded their rom and pulled the mms apk. This thing is amazing.

I've had a hard time finding 4.2.2 mms apk's that have emoji support and work 100% (picture sending/receiving issues).

This one works perfectly with PA, with the added ability to customize bubbles, chat colors, backgrounds, etc.

I uploaded just the APK if anyone else wants to try it without having to pull it from the rom.

BlackBean MMS

All credit to "team baked" http://bakedrom.com/
[Samsung Galaxy Nexus] fairct:
Nope, no reason to flash unless you want the LTE toggle and bluetooth audio quality fix baked in.
[Samsung Galaxy Nexus] Nephilim:
Nice, thanks, that's what I figured. BTW, anything new showing up for AOSPA on GIT?
[Samsung Galaxy Nexus] fairct:
There was a bit 2 days ago. I actually ran a build but haven't gotten around to actually uploading it lol. Between working 9ish hours and having a cold this week, I'm pretty wiped.
[Samsung Galaxy Nexus] Nephilim:
It's all good man. Was just curious. I've been getting my ass handed to me with projects for the last week and a half at work myself. ;)
[Samsung Galaxy Nexus] fairct:
We've got a site redesign launching in September, so I'm basically slammed until then... I don't like to think about it. :eek:
[Samsung Galaxy Nexus] Nephilim:
Gotcha.

As for updates, just throw one out when you think the update is significant enough, no point in building every other day with no noticeable change involved between updates. ;)
[Samsung Galaxy Nexus] yakitori2:
I flashed the 3/28 build and I have the LTE toggle...is there something different between that and the 3/29 besides the bluetooth fix?

I have pesky bluetooth connections issues that are driving me nuts...like random disconnects from my head unit in my car. Unsuccessful pairing that continually requires me to toggle BT on and off again...which sometimes it hangs turning off for a minute to two before it actually allows me to toggle again.

Does the 3/29 build fix any of those?

On another note....why does XDA admins randomly delete posts that contain any negative information about a user experience in relation to the rom. I posted a couple pages ago about my BT issues and it mysteriously disappears. Stuff like that IMO should be available for other potential users to read. its about making an informed decision
[Samsung Galaxy Nexus] Nephilim:
Lol, did you read any of the last 4 or 5 posts? I already asked if there was a difference between 3/28 and 3/29 and the answer was given. Make sure to read the thread before asking something. ;)
[Samsung Galaxy Nexus] yakitori2:
Did you read mine? I saw your question and the answer from fairct...which is why i posted asking for a bit more detail on the difference.

I know he said the LTE toggle and BT revert was included...but thats it. That doesnt tell me much in regards to my question which was " the 3/28 build HAS the LTE Toggle for me" and "will the 3/29 build fix the BT problems of random disconnects and unsuccessful pairing"

The original answer to your question was too vague. Therefore I am entitled to post and ask if the dev is willing to elaborate on it. I would flash the 3.29 build to fix my BT problem. I have the LTE toggle on the 3.28 build...so is that really a "difference"

see below...Build for 3.28...has LTE toggle. Am I missing something? Is there a "different" LTE toggle in 3.29?
[Samsung Galaxy Nexus] Nephilim:
Actually the answer was perfectly posted. I asked if there was a difference between 3/28 and 3/29 and he said nothing besides the BT and LTE Toggle, that basically answered your question about BT, he said that was one of the two things that was added in 3/29.
[Samsung Galaxy Nexus] tattedupboy:
I've had two sleeps of death today on the latest nightly build. I did a totally clean install and I'm running this with the AK 020 Diamond kernel. Anyone else having this issue?
[Samsung Galaxy Nexus] yakitori2:
i dont even see a 3.29 build. Is that just the upload date? Is the build still named 3.28?
[Samsung Galaxy Nexus] Nephilim:
v020 is outdated, try updating the kernel to the newest version on the AK thread. Also, SOD's are never related to the rom. ;)

I assumed since the link on the OP's filename is 3/29 that is what it is. I did not download to check because I am content with 3/28 and got the response I needed from fairct stating the changes, neither of which I need. :)
[Samsung Galaxy Nexus] fairct:
It is indeed the upload date. Since I didn't clobber the output between builds, it kept the original datestamp for the file name. So the build is named 3-28, but the upload date is 3-29. If you're having wonky bluetooth issues, you can a previous build and see if it's the bluetooth fix causing you trouble. I intend to create a zip to revert this, but haven't had the time.
[Samsung Galaxy Nexus] tattedupboy:
I'm not so sure about that. This is the only ROM I get them on, and I've used a LOT of different ROMs.
[Samsung Galaxy Nexus] Nephilim:
It's a proven fact that SOD's cannot be caused by a rom, it is either a kernel or settings for a kernel. Many developers have already come to this conclusion.
[Samsung Galaxy Nexus] tattedupboy:
I wish someone would tell my phone that then. I'm using the same kernel and kernel settings for this ROM that I use for all the others, and I swear, this is the only ROM I get SODs on.
[Samsung Galaxy Nexus] Nephilim:
That means that the kernel is not playing nice with this rom using the settings you have. I have only used AOSPA since the first version was released last year and I have used every AK Diamond Kernel on AOSPA without a single SOD, I am in fact a beta tester for the AK Kernels. I suggest you update to the newest AK Kernel on the AK Thread and then try running it for a bit with stock settings. Most likely you won't get an SOD, then after that just modify stuff little by little. ;)
[Samsung Galaxy Nexus] tattedupboy:
I'll try anything to get the SODs to stop. In the attached screenshot are my current kernel settings. What are the recommended settings?
[Samsung Galaxy Nexus] Nephilim:
First suggestion is that you download Trickstermod from the Play Store and delete no frills. AK Kernels are recommended to be used with Trickstermod for adjustments. If you want to try out settings for good battery and performance give my settings a try, they are on the bottom of my signature. They seem to be a big hit with most that use AK Kernels. Here is a link in case you are using an app on your phone and cannot see my signature:

http://xdaforums.com/showpost.php?p=38030897&postcount=13473

Remember, get rid of No Frills app and install Trickstermod to adjust AK Kernel. That might be the problem with your SOD's itself.
[Samsung Galaxy Nexus] dirtsky:
I've been using your settings since I got my nexus and battery life is great. I'm still using cylon 801 which has been the most stable for me.

Sent from my Paranoid Galaxy Nexus
[Samsung Galaxy Nexus] tattedupboy:
I applied your settings and after a reboot, there's definitely a noticeable difference in the smoothness of the ROM. And I sure hope it's as good for battery life as others are saying. Battery life has always sucked for me on this phone.
[Samsung Galaxy Nexus] simonbarsinistr:
Trickster mod is nice since it runs the kernel settings as init d scripts instead of having to apply them after boot. Sort of like how lean tweaks worked with lean kernel, but with a nice GUI instead of doing everything through terminal emulator.
[Samsung Galaxy Nexus] Nephilim:
Trust me, you'll see a viable improvement in battery. :)

Sent from my AK Diamond Powered AOSPA 3.15 Galaxy Nexus
[Samsung Galaxy Nexus] Visegrad:
Just so your not alone, I get sod as well... and oddly, around the same time/battery level each day. I'm going to keep playing with settings in trickster to see what works best for me. I already mostly use nephilim's settings, but I have to have a higher screen off setting or the screen doesn't come on until after the second ring on a call.

Sent from my Hitchhikers Guide to the Galaxy
[Samsung Galaxy Nexus] sickopsycho:
Funny you should mention that... I have that sane issue. Never thought to adjust screen-off CPU speed, I'll give it a whirl. =)

what do you have your set to? I was at 203 and it barely gives me an opportunity to see the caller before it's too late
[Samsung Galaxy Nexus] xain713:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

I stopped getting text messages second day in the ROM anyone else having a issue?

Edit : nvm deleted old text then all missed text flooded in
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

That's totally strange. Do you have a look limit set on your MMS app?

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] droidgyrl6:
Is the incoming call screen off center for anyone else???

More specifically, like this:
[Samsung Galaxy Nexus] xain713:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

Limit was 500 I had only 300

I think it was probably me and my gf text at the same time and something lagged up but once I deleted the thread all her messages came in at once thank god it was on vibrate lol I have loud notification sound
[Samsung Galaxy Nexus] fairct:
Ran into a snag with tonight's build. Finished fine, flashed after I came back from dinner, and... didn't boot. Based on the github and the G+ page, it shouldn't require a custom kernel anymore. I started another build, but I won't post one that doesn't work like I expect.

Sorry! :confused:

EDIT: Yep, flashed it with a custom kernel and it booted ok. It shouldn't need that though...
[Samsung Galaxy Nexus] jeffcavicchi:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

No worries! The one from yesterday is working great!
[Samsung Galaxy Nexus] fairct:
Not a lot of changes should have made it into tonight's, really. New kernel, and some of the phone settings from CM (vibrate every 45 seconds, vibrate on hang up, etc.).
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

Eh, not really worth your effort. ;)

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] Tone_Capone:
Nephilim,

Does it take a few hours for the AK Dummy kernel to set in? Everytime I've tried it (even with your settings) my phone sucks down the battery like none other. I don't have this problem with LeanKernel. Just looking for some advice!

Thanks!
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

If you are on Aospa you should be using cylon not dummy. Dummy is 4.2.1.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] Tone_Capone:
Ok. Ill give that a shot. Thanks for the tip!

Edit: I just wanted to add that I had this same luck when on the 4.2.1 builds as well. Hopefully this will fix it for me since I've heard nothing but awesome things about this kernel!
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

Yep, 3.1 is a 4.2.2 ROM so you need a 4.2.2 kernel. Cylon v710.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] TemplesOfSyrinx:
I just wanted to thank fairct for these builds. This is the best part of the custom ROM community and Android. I am not an expert by any means, but I'm not a novice either. I have never learned how to make a build from the git, but if I ever get a computer that is fast enough to do it I will probably learn.

Thanks to fairct, nephilim and all the others that make this a great forum.
[Samsung Galaxy Nexus] 00negative:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [02/27/12]

Paranoid androids site has a great write up on setting up the build environment. But it still shows the old way for actually compiling paranoid its actually easier than that write up now.
[Samsung Galaxy Nexus] fairct:
New nightly posted!

Not a lot of changes, and no official changelog. Superuser is now in place of SuperSU, and it lives in Settings. Pretty slick :)
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/02/12]

Thanks! Did they fully integrate the 4.2.2 code since it went aosp yesterday?

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] jeffcavicchi:
Hey Neph - did you ever confirm whether we can skip flashing Gapps every time?
[Samsung Galaxy Nexus] Nephilim:
Going to try with this update after I am done doing a nandroid. ;)
[Samsung Galaxy Nexus] jeffcavicchi:
That's what I am going to do, too.

Nandroid is a wonderful thing!
[Samsung Galaxy Nexus] Nephilim:
I always do one before every update, TWRP's newest update made nandroids super fast now too!!!

---------- Post added at 11:16 AM ---------- Previous post was at 10:17 AM ----------

I can confirm that by just flashing the rom and not gapps the only things I lost were the blue google calendar from the market and gmail. Both I just installed off play store and are working normally. I think that with the next update they will be there though since I installed them directly from the play store. We'll see. :)
[Samsung Galaxy Nexus] Visegrad:
I find 525 does the trick for me.
[Samsung Galaxy Nexus] tattedupboy:
So far, I've been on Nephilim's settings for one day------and while I haven't had any SODs, I am experiencing considerable lag at times. I switched the governor setting from conservative to interactive, and same issue. Any suggestions? I really like this ROM and will do whatever is necessary to make it run well.
[Samsung Galaxy Nexus] rmonjay:
If you can describe these times, we may be able to provide insight. Right now, I just assume you mean when the play store is updating or you are doing something else that taxes the CPU or depletes the available ram.
[Samsung Galaxy Nexus] tattedupboy:
Switching between apps, launching apps, etc. Pretty much the universal definition of lag.
[Samsung Galaxy Nexus] rmonjay:
So, you don't want help. You are just looking for a place to complain? Provide details. You said that "at times" you are experiencing lag. what differentiates the times that you are experiencing lag from those other times whne you are not. Is it right when you wake your phone? Is it when the play store is updating? Is it intermittent, where everything is gravy one minute and toast the next and back without rhyme or reason? Right now all I know is that your user experience sucks, but I have no details to figure out if it is the rom, the kernel, the phone or the user.
[Samsung Galaxy Nexus] simonbarsinistr:
Yeah, try to experiment to see when it's the worst, maybe even go into developer options and turn on the cpu use overlay, so you can see exactly what it's saying when you do normal operations (not even sure this is a helpful idea). Because we know it's not the rom, we all have the same phone, with the same rom, and it's awesome for most. I'm running stock battery, stock kernel, and no tweaks and it's very smooth with around 10 hours on battery with near 2 hours screen time on 3g consistently when I'm down to 20% left. I am very pleased with it.

So we just need to figure out what's causing the conflict. All phones vary in how the chips respond to oc and uv, but with all those settings stock, there shouldn't be widespread lag.

I must say, I've used seeder app on a few devices, and even with newer os versions, it still seems to help. Although it really shines on GB and older phones.
[Samsung Galaxy Nexus] tattedupboy:
It's not my goal to complain. It's my goal to get this darn lag to stop. There seems to be no rhyme or reason to it; Google play updates aren't the cause because I haven't updated any apps in a few days. I'm running the latest nightly of this ROM, the latest AK Diamond kernel, and Nephilim's settings (except for the governor, which I set to Interactive, but only after not liking the performance with the conservative governor).
[Samsung Galaxy Nexus] rmonjay:
I would try a few things. First overvolt up 10 or 15 steps of 5. Your phone may just require extra voltage. Next turn off the multi core savings option. Your phone may not be activating the secord core properly at times. If neither of those work, I would raise the off screen and min to 350.
[Samsung Galaxy Nexus] magnum870:
If you're using his settings exactly as posted, you may want to modify. He underclocks a lot, so if you were to bring the clock speeds back up that may make a difference.
[Samsung Galaxy Nexus] Nephilim:
You were misreading, I am using "ktoonservative" governor, which is a yet unreleased experimental governor for the beta testers not "conservative", I added in small red text to use Interactive with "hispeed_freq" set to 525000 in "Governor Control" if you don't have Ktoon governor. I have since reverted back to Interactive as my main governor due to Ktoon being instable still and needed to be tested more.

I also suggested that if you have any issues undervolting MPU by 50 to keep it where it's at. Did you take my advice and remove no-frills and then replace it with Trickstermod? If not I can't help you with AK Kernels because Stefano the developer insists on Trickstermod for the best results.

I used to underclock to 920mhz but have since bumped it up to 1060mhz for performance improvements without sacrificing battery life. ;)