yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] thracemerin:
Well, for 9.0 RC1, that doesn't guarantee there will be a stable release soon.
[Samsung Galaxy Nexus] lazaro17:
Is anyone getting crashes when trying to play a voicemail from within the call log?

You'd have to have the option in google voice settings checked on to allow voicemails to show up natively in call log. Has always worked for me but broken in last nightly.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Theshawty:
4.7, I believe.
[Samsung Galaxy Nexus] thracemerin:
Still 4.4.3, the 4.7 toolchains aren't merged yet.
[Samsung Galaxy Nexus] lazaro17:
Still 4.6 I think cause of change log

icu4c: Fix build with gcc 4.6 and -Werror

Pretty sure i read somewhere here that they want to test 4.7 out first before pushing those builds out to us.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ragnarokx:
bump
[Samsung Galaxy Nexus] thracemerin:
That just means it now works with 4.6, its still built with 4.4.3 according to what the kernel is telling me.

I forwarded your issue to some people who have a lot more android knowledge than I, when/if they can fix it is still unknown, if I find out anything worth telling you I won't keep it a secret, I promise.
[Samsung Galaxy Nexus] kelkelkel:
Just wondering if anyone else had tried this? Is this a known bug?
[Samsung Galaxy Nexus] dominoes20:
Wifi tether definitely doesn't work!
[Samsung Galaxy Nexus] Gregus59:
Do a full wipe... It works for me on the last build.
[Samsung Galaxy Nexus] teazgood:
Wifi tether works fine for me on latest build
[Samsung Galaxy Nexus] joelteixeira:
Guys, does anyone have a solution to limit the number of frequently called contacts? I have 25 contacts on this list and sometimes I'm looking for someone alphabetically and then I realize they are on the upper list. 5 would be so much better.

Sent from another Nexus
[Samsung Galaxy Nexus] mrasquinho:
Hello!

As I don't understand how to work with Gerrit, and I don't know how to pull a request, could someone pull this request for me?

Link: 1 - https://github.com/mrasquinho/andro...mmit/74b534a9df86543876ef004a6465968b6f493392

It adds "ç" to strip unicode, as it wasn't being stripped (thanks to dzo).

By the way, if someone does the above commit, could you please commit those two too?

2 - https://github.com/mrasquinho/andro...mmit/9586e91d8fdb580d0c90e80e5912980a556a92fa

3 - https://github.com/mrasquinho/andro...mmit/2e9bd24ce04349ce1b2abac9e34c7986669a8898

The most important is the FIRST one. If someone can do it, i'll be very thanked :) (I'll donate for you, for sure!)

Best regards
[Samsung Galaxy Nexus] thracemerin:
Shouldn't this be in the special cases lower down in the function rather than where it is? I can commit it, I just don't think this is the correct way to do this particular change.
[Samsung Galaxy Nexus] dave_t321:
gerrit is easy:

http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit
[Samsung Galaxy Nexus] joelteixeira:
The changes you made don't follow the Portuguese language agreement from 2009 January. Example: If I understood well, "seleccionar" is now "selecionar".

Take a look at:

http://www.portaldalinguaportuguesa.org/acordo.php?acordo&version=1990

Sent from another Nexus
[Samsung Galaxy Nexus] mrasquinho:
I'll explain.

I had a Huawei Ideos X5, and the developer DZO is maintaining ICS for this phone. I tried to add "ç" in the special cases, but it didn't work. Then DZO build that line, committed it and it started working. So that is the correct way :)

Here is the original commit: https://github.com/dzo/packages_apps_mms/commit/23e2c9ee87e577ac52098ebdb61d708a00fedaff

I didn't give you this one, because it has the remove "s = s.replace("ç", "c");", my bad attempt.

What is to commit is only this - https://github.com/mrasquinho/andro...mmit/74b534a9df86543876ef004a6465968b6f493392

Yes, I read it a couple of times, and tried to do myself, but as I'm starting now learning this, is kind of difficult for me yet :) Maybe in the future i'll do it myself!

Thanks for your both answers!

---------- Post added at 11:22 PM ---------- Previous post was at 11:20 PM ----------

I'm sorry! I didn't know that CM9 is already using "Acordo Ortográfico"! That way you're correct!

However, some sentences are still wrong! I think it is because of the confusion between

values-pt - for Pt Brazilian

values-pt_rPT - for PT Portugal

As I said in the above post, i was helping DZO with the Aurora for Ideos X5 PT translations, and that was a common confusion!

My bad :)
[Samsung Galaxy Nexus] 8BitVoxel:
changelog

Revert "Overclock GPU"

2012-06-12 at 20:32:21 (android_kernel_samsung_tuna)

To be in today's nightly, does this mean they are going to OC the GPU to 384 like the Franco Kernel? or give an option to do it manually? I'd really like the option or even the default to be OC'd in CM9 without having to install usually unstable kernel mods...
[Samsung Galaxy Nexus] thracemerin:
Nope, it was overclocked to 384, this reverts it to stock.
[Samsung Galaxy Nexus] 8BitVoxel:
Bummer. Has CM9 for the GNex always had the GPU OC'd? whenever I bother to fiddle with kernels such as Franco you can see an increase in GPU specific scores...
[Samsung Galaxy Nexus] thracemerin:
I can't find the commit that did the original overclock, but it appears it's been in for a while, unless it's hidden in something else.
[Samsung Galaxy Nexus] 8BitVoxel:
I hope the RC has the GPU back to 384 then, don't want to hang on to yesterdays build forever just to have it. I prefer just running stock CM9, there's always something screwed up with "3rd party" kernels or they just don't play nice with CM these days. I like Franco's, but it breaks CIFS which I use every day, and the color tuning is different to stock CM9, which took enough effort to get right.
[Samsung Galaxy Nexus] mrasquinho:
So please thracemerin, feel free to commit this change!
[Samsung Galaxy Nexus] 8BitVoxel:
Any thoughts on the impending Jelly bean release? Some say it's will be 4.1 not 5 and is likely to be announced or even ship at the end of the month with Google IO conference, and be on the Nexus 7 tab...

What will this mean for CM9? I fully appreciate (as a long time developer myself) the immense effort these guys are going to, to making the best custom rom they can, its a bummer that inevitably it just takes so long with such a massive task. Maybe/hopefully moving the code base from 4.0.4 to 4.1 would be as easy as the incremental Gingerbread builds were eg. 2.3.4 to 2.3.7 etc. with CM7.

Or maybe, big boss Andy Rubin and co have taken notice of the worlds most popular ROM and taken some of the nice little tweaks such as notification widgets and included them in JB.
[Samsung Galaxy Nexus] thracemerin:
Jellybean will likely be 4.1 and will probably be CM 9.1, just like they are on CM 7.2 with 2.3.7, but one never knows until its all officially announced and released.
[Samsung Galaxy Nexus] ragnarokx:
New Android version means new Cyanogen version, so Jelly Bean will be CM10.

Froyo (CM6) > Gingerbread (CM7) > ICS (CM9) > Jelly Bean (CM10)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thracemerin:
I will as soon as I figure out why my virtualbox hates me today.
[Samsung Galaxy Nexus] joelteixeira:
The agreement is 3 years old now, everyone should use it. I agree with some corrections, I was referring to the double "c" only.

You're not alone, we (pt-br) still getting used with the changes as well. ;-)

Sent from another Nexus
[Samsung Galaxy Nexus] 8BitVoxel:
Always looking forward to the future. Not too long now to see what JB is, iOS 6 was nothing massive really, Navigation was the only thing which stood out to me. And Siri? I have a real women to talk too when I get home. With JB being a point release I'm not thinking there will be any huge overhaul.

Will stop throwing unrelated CM9 Galaxy Nexus fodder up now. Thanks for your thoughts and replies.

Yesterdays 12 build on a clean install is so incredibly perfect on my GNex btw.
[Samsung Galaxy Nexus] thracemerin:
While I would tend to agree with you, the time between ICS and JB is very short, I don't see it being a full version ahead, but I could be wrong, sad thing is it will likely be the end of updates for a lot of non-Nexus devices that began life before ICS release if JB is in fact a full version jump.
[Samsung Galaxy Nexus] 8BitVoxel:
If JB is going to be CM10, then we'll need to wait another year for that. (I understand the time it takes, I'm not making a negative sentiment) It'd just be a shame that if JB arrives so early/soon CM9 will probably never go final, and in a few weeks this will be the "[ROM] [NIGHTLY] [GSM] CyanogenMod 10" thread.
[Samsung Galaxy Nexus] mrasquinho:
Ok, thanks! :)

Despite of having 100% sure that it works, I would like to test it again. However, I don't know how to compile an apk :p

Best regards and thanks once again
[Samsung Galaxy Nexus] colocynth:
Cm9 needs a stable release. Not all users are 'flasholic', as me. :D
[Samsung Galaxy Nexus] thracemerin:
Cyanogen hinted at some RCs (for select devices, Nexus devices are almost certainly on the list) possibly coming as early as late this week on twitter and it was reposted on the CM Google+ this this morning, I posted a quote of the post in this thread earlier this afternoon.
[Samsung Galaxy Nexus] NCguy:
Not to get off topic since this could easily be its own thread, but do you really think that google would announce a new os version when it only has an adoption of barely 10% on ICS?
[Samsung Galaxy Nexus] ragnarokx:
Very true. And I can't recall any Android version that got a new name that wasn't a significant update, so perhaps we'll get a bump in version number while retaining the ICS name? Like Android 2.0 and 2.1, which were both Eclair.
[Samsung Galaxy Nexus] thracemerin:
Well, Asus hinted at a new Nexus Tablet running Jellybean being announced soon, so that's where the rumors are coming from, what this actually means is up for debate and as you said, probably not in this thread.

Android version numbering is very strange

2.0 and 2.1 were Eclair

2.2 was Froyo

2.3 was GB

3.0, 3.1 and 3.2 were Honeycomb

4.0 is ICS

who knows what Google is doing or thinking when it comes to names and numbers.
[Samsung Galaxy Nexus] lazaro17:
Wouldn't be surprised if many handset makers skip ICS and go to Jellybean altogether. Pretty sure similar things have happened before.

Also lets keep in mind the amount of old handsets that are probably not ICS capable and will never see ICS are also accounted for in the OS shares.

Considering this might end up being an incremental update and Google's new stance of having one update a year the timing kind of makes sense.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Molitro:
What I don't know is why everyone is asuming that JB is coming with the tab presentation.

I wouldn't count on it, but on an update to ICS, what is, by the way, what google should do.
[Samsung Galaxy Nexus] thracemerin:
Rumors lead to speculation, speculation is what the internet is best at. :D

If you believe the internet the Iphone 4s would have been the Iphone 5, Galaxy Note sized and curved, running IOS6, etc... I could probably find examples for most devices, it's just the one that came to mind first.
[Samsung Galaxy Nexus] 8BitVoxel:
Sorry, I converted this "GSM Galaxy Nexus CM9 Nightly" thread into a "What version will JB be and when will it arrive, and how will it affect CM9/10" thread :)

The internets seem to say that JB is fast approaching, will be announced at Google IO, and will ship on the Nexus 7 Asus tablet. I've got an early (but retail) TF700T coming next week, I know that it has ICS on it, but I guess this will also be one of the first devices to get JB.

So yeah, hmm about that GSM Gnex....
[Samsung Galaxy Nexus] Vangelis13:
On topic, please? ;)
[Samsung Galaxy Nexus] mrasquinho:
When you commit the change, please tell me!

Best regards and thank you
[Samsung Galaxy Nexus] thracemerin:
http://review.cyanogenmod.com/#/c/17583/
[Samsung Galaxy Nexus] mrasquinho:
Nice'n'quickly! Thanks!
[Samsung Galaxy Nexus] thracemerin:
Even if you don't feel 100% comfortable sending stuff in for review, you could join the Gerrit so you could answer questions, since you're more likely to be able to answer them than me :)
[Samsung Galaxy Nexus] nonameduck:
Has anybody started experiencing issues with signal starting a day or two ago? Every few minutes, the signal bars will turn grey before switching back to blue. This is also killing my battery life. I've tried two different radios, and I'm experiencing the issue on both.
[Samsung Galaxy Nexus] io53:
I don't know about your wife, but mine does not check wolfram alpha if I ask her a tricky question :D.
[Samsung Galaxy Nexus] jeremysv:
Has anyone else noticed that Foursquare locks up and refuses to run since the 20120612 nightly? I've tried 2 devices, reinstall with reboots, and deleting the Foursquare directory.

It runs OK on < 20120612. I couldn't see anything useful in logcat.
[Samsung Galaxy Nexus] dj_ghosie:
I can confirm that both WiFi and USB tethering are working, magical!

I'm using 0612 build.
[Samsung Galaxy Nexus] galakanokis:
I have. About half a dozen times since this morning when I flashed the latest nightly. Completely stock CM.
[Samsung Galaxy Nexus] thracemerin:
For those who are having signal drops, CM9 appears to ship with the XXLA2 RIL, if you are not using the XXLA2 modem you may run into some radio related issues, my suggestion is try GetRIL https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5zaWJib3IuZ2V0cmlsIl0. and download the correct RIL for the modem you are using, it may not fix the problem, but it's worth a shot.
[Samsung Galaxy Nexus] snapilica2003:
For some reason GetRIL doesn't work on my Nexus. When I open it it freezes completely. Didn't bother wiping phone just for an app, so I don't know what's wrong.

LE: Nevermind... just started working all of a sudden.
[Samsung Galaxy Nexus] thracemerin:
It has a tendency to lag really bad when you first start it, a couple of times i thought it crashed, but it eventually worked.
[Samsung Galaxy Nexus] galakanokis:
Thanks for this. Hadn't checked it in awhile and sure enough they were mismatched. Will see if that helps.
[Samsung Galaxy Nexus] nonameduck:
This did not help my signal issues.
[Samsung Galaxy Nexus] Theshawty:
Then your carrier may have ****ty reception where you are, or you can try flashing another radio. :)
[Samsung Galaxy Nexus] soder:
Is GetRIL and flashing a Radio the same thing? I though that GetRIL only got some special settings for the radio....

/Söder
[Samsung Galaxy Nexus] mrasquinho:
And how can I do this?
[Samsung Galaxy Nexus] colocynth:
No, flash a radio first. Then run getril to check if the ril match. If not, you may use getril to download a correct one.

Sent from Colocynth's Galaxy Nexus
[Samsung Galaxy Nexus] sago62:
with build 0613 the data are often disengaged ....:mad:
[Samsung Galaxy Nexus] joeyfong:
The problem is occurred since 0611 build
[Samsung Galaxy Nexus] andQlimax:
the problem is just random, u will experience it even with the stock rom

it doesnt depend from the rom, it depends from the ****ty radios/ril..no one work correctly as it should..blame samsung
[Samsung Galaxy Nexus] sago62:
In fact until yesterday worked .......
[Samsung Galaxy Nexus] andQlimax:
that what i mean by random..the fact that u flashed a new nightly, it a coincidence

it depends from many factors about the newtork and ur locations..im having problems too with the singnal today, but i have the same nighlty as yesterday
[Samsung Galaxy Nexus] sago62:
strange though .... I never had problems like this ... so I wonder :why so many are complaining now?
[Samsung Galaxy Nexus] joeyfong:
Before is only drop, and will be back after a while, now is completely blocked.:(
[Samsung Galaxy Nexus] zenzip:
In wich way i can change the size of navigation bar like in aokp?

thanks

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] navodwickra:
There is no such option as in AOKP
[Samsung Galaxy Nexus] jenzy1985:
How can download the standart Torch LED App ? My CM9 Nightlies Build doesn´t have it :confused: Thanks
[Samsung Galaxy Nexus] Angelakaro:
Next nightly will (or should) finally fix bootanimation lags :)
[Samsung Galaxy Nexus] zenzip:
I hope!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] zenzip:
so +1 for aokp :-) maybe in 2 day i leave this ROM and come back to aokp best rom on gnex for now!

aokp: more custom option, best power consumption, best stability, good compatibility with franco kernel(my fav) - cm9: for now only more responsiveness than aokp!

last question...where i can find changelog of lastest nightly?

ps.

waiting for linaro...

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] rashidi_zin:
BBQLog or Appspot.
[Samsung Galaxy Nexus] Slurpino:
I have a little problem with cpu.. latest two nightly CPU always 1350 and +50%.. with 11/06 I haven't this problem.. anyone have same problem?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] mrasquinho:
A little bit "offtopic"

Could someone help me? To start the repo for CyanogenMod9, if i write

repo init -u git://github.com/CyanogenMod/android.git -b ics

i have a repo command not found message!
[Samsung Galaxy Nexus] bragih:
I still cannot enable Torch :(

It's greyed out
[Samsung Galaxy Nexus] m.is.for.michael:
with a question asked this frequently, you'd think might implement a search function or something... LOL.

The torch app doesn't work on tuna boards (all flavors of galaxy nexus) so this is normal.

In the interim, i have a torch app from the market as a lock screen shortcut.
[Samsung Galaxy Nexus] soder:
Try press harder?

/Söder
[Samsung Galaxy Nexus] Theshawty:
How come it's like that in CM9 when it works perfectly fine in like AOKP? You'd think teamdouche would have had a solution to this by now.

You're kidding, right?
[Samsung Galaxy Nexus] jventura:
Hi Miguel,

you have to copy your "repo" file to ~/bin, and set it as executable..

Check this topic at modaco to help you get started: modaco.com/topic/353188-compiling-cm9-for-blade/

Ignore the "Zte Blade" specific things as they are for the ZTE blade
[Samsung Galaxy Nexus] dyndragon:
The CM team does not like the current implementation of torch. It requires a dummy camera window to be open in order to turn the LED on. That is probably how the apps and AOKP are doing it.
[Samsung Galaxy Nexus] snapilica2003:
Because CM developers actually spend time developing code from scratch that works properly. AOKP pretty much Kang's (thus the name) whatever they find, stuff it in there then go about fiddling and making it work. The current implementation requires a hack to open the camera app and hide the window just so you can turn on torch. Do you feel it's OK to use a hack like this?

It's similar with the whole Nexus One issue Ricardo Cerqueira tried to explain on G+

Everything that's not inside CM9 already is because either it's not committed code yet or it's not achievable in an elegant and clean manner up to CM's standards.
[Samsung Galaxy Nexus] Theshawty:
I didn't know it had a open the camera app just for this. Even though it works, I don't find it acceptable, and I accept why teamdouche hasn't fixed it yet. Makes sense to code everything from scratch :)
[Samsung Galaxy Nexus] jventura:
Miguel,

as you can see in all translations pt-rPT in CM9, and while using CM9, that CM9 is *not* using "Acordo Ortográfico". To maintain integrity for pt-rPT, don't use the political agreement known as "Acordo Ortográfico" in CM9, as you only will add double ortographies (?) to a cohese system, and then someone (possibly me) will have to correct your translations to pre-"Acordo Ortográfico".

The "Acordo Ortográfico", as I explained in a gerrit comment, is a political agreement ratified by the Portuguese President *without* any consultation or referendum to the real owners of the Portuguese language, the people. As such, only the public institutions are forced to apply it, and all its errors and double ortography words (a real mess, may we all say).

So, since Google is releasing its strings in pre-"Acordo Ortográfico", there are many proeminent writers/linguists/etc., and more than 99% of the PT population not applying the agreement, and rumours that some parts of it will be changed in the current times, we (pt-PT) should refrain from using it, and messing even more with the errors that are being done..
[Samsung Galaxy Nexus] danibravo:
I am... i am currently on nightly 6-12... i am about to upgrade to the latest.. let you know if i still have the problem...

dominoes20 -

i updated to latest nightly, didnt fix the sync. so i decided to take a look at the settings under accounts & sync and notice a bunch of items were unchecked... this ended up fixing gmail. ( i guess that last nightly removed them somehow... strange)
[Samsung Galaxy Nexus] LuPellox85:
is this the version with the linaro improvements?
[Samsung Galaxy Nexus] CMNein:
Most of them merged, but the "game changers" aren't merged, and the toolchain is not 4.7
[Samsung Galaxy Nexus] Herman76:
It would be cool if the new boot animation would start with the old Android logo (the fatter one) and getting it transformed to the new one when the wheel spins. As a symbol of the evolution of the OS. :)
[Samsung Galaxy Nexus] ragnarokx:
Here you go.
[Samsung Galaxy Nexus] dr.m0x:
Linaro isn't really stable yet as far as I know it breaks gps and the Cyanogenmod video drivers don't like it much either

Sent from my GNex
[Samsung Galaxy Nexus] thracemerin:
GPS is fine, the guys compiling it on XDA aren't doing it right.
[Samsung Galaxy Nexus] Vangelis13:
Incognito surfing..? :sly:
[Samsung Galaxy Nexus] Bosio91:
Do you know where can I find a release with a working GPS?

Sent from my RasTrinity powered Galaxy Nexus
[Samsung Galaxy Nexus] Nebucatnetzer:
What is your question exactly?
[Samsung Galaxy Nexus] thracemerin:
Not with linaro enhancements, at least none that I'm aware of, I think the issue is that the CM script to extract the proprietary modules isn't pulling the GPS blobs so there's no driver support in their build, I could be wrong but that appears to be the issue.
[Samsung Galaxy Nexus] wai10691:
+1 for this. As I know that guy from Rootzwiki was the compiler for aokp and linaro and merged it together as b38-O3

And gps is broken in that build
[Samsung Galaxy Nexus] Vangelis13:
Since when is that there, sorry. Clicked submit accidentally.
[Samsung Galaxy Nexus] soder:
=) Wasn't that obvious?

/Söder
[Samsung Galaxy Nexus] akira02rex:
It's been there for a long time, ever since Android 4 was introduced.
[Samsung Galaxy Nexus] CMNein:
The only thing that may have changed is the icon for it, I don't remember it not being present. Might have been under settings in CM7 (?)

It's a good feature for avid pr0n enthusiasts.
[Samsung Galaxy Nexus] Theshawty:
Kinda, but I still had to ask. :p
[Samsung Galaxy Nexus] Vangelis13:
Yeah, the icon must be a recent thing. Didn't have a clue.. :o
[Samsung Galaxy Nexus] beekay201:
I7db574d9

---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------

instead of

just

be aware that currently extract-files.sh is looking for gps.omap4.so in the wrong location, see above post.
[Samsung Galaxy Nexus] goTouch:
For now, I'm going to stick with 20120610 version. To many bugs the last three versions. I think Linaro is going to be a long way to get stable.
[Samsung Galaxy Nexus] mrasquinho:
Thanks! But now it says "Line 23: python not found"!
[Samsung Galaxy Nexus] :
+1

Linpack shows instabilities (never had this before), programs like android weather widget doesn't work any longer (esp. the location service) ... 20120610 is working fine
[Samsung Galaxy Nexus] beekay201:
You'll need python2 in your path, as building conflicts with python3.x
[Samsung Galaxy Nexus] thracemerin:
http://wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Compile_CyanogenMod_(Linux)

Follow the instructions in that guide to get it all set up to build, if all you want to do is gerrit, it's the same basic procedure down to the point where you actually initialize the build.
[Samsung Galaxy Nexus] andQlimax:
Bugs = user errors

:D

(Anyway the rom is not yet build with linaro toolchain)

Inviato dal mio Galaxy Nexus con Tapatalk 2