yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] beekay201:
Oh nice, they've updated the wiki. :)

---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------

true, unless there's logcat, dmesg and last_kmsg.
[Samsung Galaxy Nexus] thracemerin:
I think I posted this in this thread before, but if i didn't here's how to report a bug: http://teamhacksung.org/wiki/index.php/How_to_report_a_bug
[Samsung Galaxy Nexus] beekay201:
I think you did.

Sent from my i9250
[Samsung Galaxy Nexus] thracemerin:
Yeah, but maybe by doing it every day or so, people might learn to make useful bug report posts instead of stuff like "mah phone dun broke", then again probably not :p
[Samsung Galaxy Nexus] andQlimax:
Bug report its only for RC and stable... not for nightly.. u should know

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] thracemerin:
You are correct that they are not taking official bug reports to the issue tracker, this doesn't mean that people shouldn't get logcat, dmesg and last_kmesg if they run into an issue and post it here.
[Samsung Galaxy Nexus] dislplin01:
Does anyone know if they are planning on making the Apollo music player sync with Google music cause all my music I sync and pay from there I don't store it on the phone
[Samsung Galaxy Nexus] thracemerin:
You could try contacting the author directly on G+, his info is on his website http://seeingpixels.org
[Samsung Galaxy Nexus] Nebucatnetzer:
I reckon the problem is that the APIs are still not open.

There are unofficial ones but I don't know if they're working properly.
[Samsung Galaxy Nexus] thracemerin:
For Google Music? closed APIs would certainly make things more challenging.
[Samsung Galaxy Nexus] Nebucatnetzer:
Pff some bugs make it interesting. Was getting a bit boring here ;).

But seriously are ICS ROMs so far less buggy then Android 2.3.x ones or are the devs just becoming so good.

---------- Post added at 12:20 AM ---------- Previous post was at 12:17 AM ----------

Yes from what I know they are still closed.

Here's the link to the unofficial ones.

https://github.com/simon-weber/Unofficial-Google-Music-API
[Samsung Galaxy Nexus] GreatBigDog:
Just flashed from 20120610 to 20120613, Is this new build on steroids or something? It's just flying along compared to my last nightly.
[Samsung Galaxy Nexus] nonameduck:
I fixed my signal drop issue.

Follow the instructions in here to view your current network type: http://xdaforums.com/showpost.php?p=20419243&postcount=11.

I remember mine used to be "GSM/CDMA auto (PRL)," but today it was somehow set to "WCDMA preferred." I switched it back to "GSM/CDMA auto (PRL)," and my issues went away.
[Samsung Galaxy Nexus] thracemerin:
Oddly enough, when I change mine it switches back if I leave the menu.
[Samsung Galaxy Nexus] Beny The Kid:
Anyone have any luck getting the battery percentage option or signal display options to work?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] qvert:
It's not fully implemented yet

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] rashidi_zin:
Is the built in performance settings working? I tried my CPU governor to ondemand but it still remain as interactive.
[Samsung Galaxy Nexus] imfloflo:
update-cm-9.0.0-RC0-GN-KANG-signed.01272012-0821.zip

* Boot animation: Custom made by @rascarlo

* FileManager

* Mms: SMS templates using gestures

* MediaScanner: Don't delete entries of secondary storage on shutdown

* Framework: Fix Settings option to disable bootanimation

* Framework: Bring back LCD disable brightness decrease

* Core: Allow 'system' user to modify cpufreq control files

* Core: Safely restart services to avoid race conditions

*** Temporarily supported until merged into Settings app ***

* CMSettings * Notification power widget: Add LTE toggle

* CMSettings: Configurable 0, 90, 180 and 270 degree rotation

* CMSettings: Onscreen controls customization
[Samsung Galaxy Nexus] qvert:
anyone tried to use a custom kernel i.e. franco kernel with the new version?

does it boot?
[Samsung Galaxy Nexus] zurchpet:
The FuguMod kernel has been adapted to run on AOSP and CM9 ROMs.

R67 runs well with the version 20120126 of yesterday...

going to try FuguMod with todays version 20120127...

EDIT: Yes, also works with the latest build of fitsnugly :)
[Samsung Galaxy Nexus] janjan:
what about face unlock? Is it work now or not. thanks
[Samsung Galaxy Nexus] zurchpet:
Works well here. I use it :)

But IMO easy to trick. Not a safe lock. just so you know ;)
[Samsung Galaxy Nexus] janjan:
Yes and thank you. going to try it now
[Samsung Galaxy Nexus] DynamicRam:
Kalim Merged the color control settings , you can now change the gamma setting on the fly
[Samsung Galaxy Nexus] slayp00n:
Does this mean I can make my screen stop looking like ****?

I want to confirm this is more then RGB?
[Samsung Galaxy Nexus] dyndragon:
Could we make sure that this revert gets into the next build?

http://review.cyanogenmod.com/#change,12133

This change was causing other kernels not to boot the CM9 kang build.
[Samsung Galaxy Nexus] fitsnugly:
That revert has already been in the builds, that's not the issue.

This commit ( http://review.cyanogenmod.com/#change,12006 ) altered the ramdisk and if kernel devs want to support CM9, they need to alter their ramdisk as well (ie FuguMod kernel already has updated theirs).

Should also probably ask your favorite kernel dev to include the SAMOLED color hack ( http://goo.gl/Or0Mv ) so it doesn't break the GNParts gamma controls.
[Samsung Galaxy Nexus] afilopou:
just cooked.The screenshot of in application
[Samsung Galaxy Nexus] blunden:
Is anyone else having issues with scanning mifare nfc tags using NFC TagInfo or TagInfo from Market? Android Beam works fine but I get no reaction at all when trying to scan tags I know a GN running stock 4.0.2 can scan.
[Samsung Galaxy Nexus] Shaquiel Harris:
I can't access the team douche website from my phone to download the rom it keeps pushing me to a different website. The hell?
[Samsung Galaxy Nexus] blunden:
Well, it's not on the team douche site yet so that doesn't really matter. You want the euroskank link.
[Samsung Galaxy Nexus] M3drvr:
I'm gonna try a fresh install of this rom again. I couldn't get the market to work before. Kept getting fc every time I'd click on an app. Even with the mentioned gapps package. But I'll try again. I love cm builds and willing to put up with issues as long as main processes work good.
[Samsung Galaxy Nexus] qvert:
Franco kernel 14.4 is now working again on cm 9

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] imfloflo:
http://fitsnugly.euroskank.com/skan...cm-9.0.0-RC0-GN-KANG-signed.01282012-1008.zip

* Boot animation: Custom made by @rascarlo

* FileManager

* Mms: SMS templates using gestures

* MediaScanner: Don't delete entries of secondary storage on shutdown

* Framework: Fix Settings option to disable bootanimation

* Framework: Bring back LCD disable brightness decrease

* Framework: Statusbar slide brightness control

* Core: Allow 'system' user to modify cpufreq control files

* Superuser: Fix FC when checking for su binary update

* Camera: Fix setting of video and camera mode

* Dalvik: Basic KSM Support

* Tuna: Change sysfs permissions to allow user control KSM

* Settings: Add KSM settings

*** Temporarily supported until merged into Settings app ***

* CMSettings

* Notification power widget: Add LTE toggle

* CMSettings: Configurable 0, 90, 180 and 270 degree rotation

* CMSettings: Onscreen controls customization
[Samsung Galaxy Nexus] nonameduck:
Oh, I forgot to mention. Switch it to your new choice, then press the button to turn the radio off and then turn it back on. That should save the setting.
[Samsung Galaxy Nexus] thracemerin:
Still doesn't save, that's odd, oh well.
[Samsung Galaxy Nexus] nadiros:
Mine doesn't save either, it seems depending on your radio it will revert to it's own default. . . that's the drift I got from the radio thread anyways

I'm on LA4 and it reverts always to WCDMA preferred.

anywhoo... OT :rolleyes:
[Samsung Galaxy Nexus] 8BitVoxel:
I happened to go a clean install (factory reset)on 20120612, something I haven't done since I first flashed this GNex with many CM nightlies. I have not had a single issue with the the 12 build except for crazy performance, it may be that the Linaro changes are deep enough that a clean install is the only way to ensure a bug free experience, just putting it out there. I haven't tried build 13 because they apparently un-overclocked the GPU.

I will do another clean install for the RC release.
[Samsung Galaxy Nexus] soder:
If I want to do a full wipe, is there a way to also backup my icons and widgets I got om the homescreen?

I will do backup and restore with Titanium Backup for all my apps, but would like to do the same for some some system apps to.

/Söder
[Samsung Galaxy Nexus] thracemerin:
The linaro changes (at least the ones that would affect performance most) aren't in yet, so any performance upgrade is from other things.

I'm running the nightly with the GPU back at standard clock and I dont notice a difference, but i also don't play a lot of 3D games on my phone so you may notice it more.
[Samsung Galaxy Nexus] ch33kybutt:
With regards to GPU back to stock speed, it's because Imoseyon's GPU userpspace control was implemented many builds ago. So GPU speed is user configurable.

echo X > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
(where X = 0 for 307, 1 for 384, 2 for 512)
[Samsung Galaxy Nexus] 8BitVoxel:
I'll probably be trying tonight's build, just cause there seems to be a little more going on there. Regardless of which Linaro patches were used or not yet, the number of Linaro related fixes and non-related clean-ups in build 11 - 12 and a little 14 appear was pretty significant compared to previous nightlies, that is how it looked anyway from the changelogs.

Either way, I was not directly attributing my performance boots to Linaro, some of it probably is, some it a clean install, and the rest just the clean-up that appears to happening as we approach RC.

We're just so lucky that such a community and platform exists for improving the experience on our beloved handsets.

---------- Post added at 02:55 PM ---------- Previous post was at 02:52 PM ----------

Really, that's great. Thank you, trying it now. Do you think they'll add a inbuilt toggle for this then, like with CPU performance?
[Samsung Galaxy Nexus] thracemerin:
Be glad you own a Nexus device too, because the Linaro stuff should be fully compatible with at least this generation of Nexus devices, other devices may not be compatible at all based on their proprietary drivers, etc...

Probably, for now you can use an init script to have it set on boot and if you need to switch it dynamically you can echo it in terminal emulator.
[Samsung Galaxy Nexus] 8BitVoxel:
I just checked this with build 12, and it was already set to 0, so the gpu was stock anyway. And now I now this is why the Franco 384 kernel gave such significant 3d specific score variance. I don't think the gpu has been OC'd in the stock kernel for a long time...

Will just changing the 0 to 1 directly in a text editor make this change permanent?

---------- Post added at 03:13 PM ---------- Previous post was at 03:07 PM ----------

ok, actually from what people are saying here and the change in build 13, this file in build 12 probably doesn't do anything right? changing this to 1 or 2 from 0 will only do the oc in build 13 and 14 right?
[Samsung Galaxy Nexus] thracemerin:
Correct, it was hardcoded to 384 prior to the 13th build. Editing the file, or echoing from terminal editor will not be permanent, it will reset on a reboot, you would have to use an init script to make it permanent.
[Samsung Galaxy Nexus] ArmanUV:
As of now, I don't think linaro patches are contributing to performance. The patches merged so far are only code styling fixes which eventually allow the build to be compiled with more modern toolchains (gcc 4.7 and linaro gcc 4.7). However, since many parts of CM are still incompatible (kernels, graphics, ...), the official builds are compiled like before (gcc 4.4 I think).

I think it'll take a few more weeks for everything to come together.

Regardless of linaro, CM9 has been improving performance-wise. It may be the kernel I'm using (CMplus) but interactive 350-1200 is amazingly smoother than before for me.
[Samsung Galaxy Nexus] 8BitVoxel:
thracemerin

Thanks, thracemerin.

Just made my script and tested on reboot if it modifies the file between the various 0,1,2 settings. And it worked, now to put this method to work on tonight's 14 build.

Cheers.

---------- Post added at 03:43 PM ---------- Previous post was at 03:36 PM ----------

ArmanUV,

I'm going to give CMPlus a try now. If I like it, and use with tonight's 14 build I won't need to run any o/c init script either.

thanks.
[Samsung Galaxy Nexus] brunswick000:
Sorry, but I've been searching and maybe it's because it's so late and my eyes are crossing, but I can't find where to download the alternate cmplus kernel.
[Samsung Galaxy Nexus] Vangelis13:
Send you a pm. It's been requested to not clutter the thread with other kernel discussions. :)
[Samsung Galaxy Nexus] Angelakaro:
Boot animation still laggy :(

Edit: also,apollo need some fixes: album covers' quality is very low! And i noticed that in last nightlies the google play music lockscreen widget cuts album covers..

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] leelaa:
I had a little bug eith latest build, notification bar was blanc, no date, time or power widgets.

A reboot solved it though.
[Samsung Galaxy Nexus] Angelakaro:
Another bug: open settings>memory will force close the app settings

Edit: solved using stock kernel

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] sago62:
If don't use stock kernel it is possible...
[Samsung Galaxy Nexus] andQlimax:
work fine here with stock kernel

the bootanimation speed up changes are not yet enabled to the build for the GN
[Samsung Galaxy Nexus] Angelakaro:
Copy about the memory bug.

Why bootanimation speed up is not yet included? The changelog says that it has been merged :confused:
[Samsung Galaxy Nexus] MistaBishi:
I have never understood why people complain about the boot animation... Do you purposely reboot just to see it or what? Who cares if its choppy, it boots faster.
[Samsung Galaxy Nexus] andQlimax:
its a generic change

it need to be "enabled/activated" for each device that CAN get improvement from that..it will be enabled later after some testing maybe (on some devices its already got enabled)

i dont care about the bootanimation anyway
[Samsung Galaxy Nexus] Angelakaro:
I'm not forcing developers to fix a problem that it's annoying only for me,but will be great to have a 100% stable and functional rom. Since the best part of galaxy Nexus is the screen,i'd like to see everything concerning the screen working as well as other roms. I know it's only a nightly build,but we have a forum exactly to report our personal experiences about what we test.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
I see,thanks. Me too actually don't care about it too much but,as i said before,will be nice to have a rom smooth in every feature

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] niamul:
cm9

baseband i9250XXLA2

kernel: 3.0.34-cyanogemod-g051e7e6

cyanogenmod version: 9-20120613-nightly-marugo

there is a lot of lag with home screen and overall with everything.

radio is stable so far

gps not working at all. could somebody tell me if there is a zip file for the gps or not and where i could get it?

i was on stock 4.0.4 but switched to cm9 hoping the gps issue would be fixed.

and where do i turn on torch from or set it to turn on if i hold the power button or in the status bar somewhere?

tia
[Samsung Galaxy Nexus] blowtorch:
you need to go back and wipe everything first, you cant just flash cm9 over stock. on cm9 everything works except torch at the moment the application is being rewritten and will be in a future release.

sigh
[Samsung Galaxy Nexus] dr.m0x:
The torch other roms have is an ugly hack which can cause compatibility issues with camera apps. It has been discussed in the thread only a day or two back. If you want it bad just download a flashlight app.

Sent from my Cyanogenmodded GNex
[Samsung Galaxy Nexus] Jiia:
I was wondering if there are data drops with CM9 nightlies? On AOKP I lose all signals twice a day and have to reboot no matter what kernel, baseband or RIL. So if your experiences of CM are better then I might consider changing my daily driver.
[Samsung Galaxy Nexus] Gregus59:
The cause of data drops is bootloader and radio, you must flash the newest.
[Samsung Galaxy Nexus] andQlimax:
there is no one radio that work as it should untill now...

all the radio around are same..there is no difference at all for me..

the problem is just randomic (some time never happen for weeks, some time it happen much often..even with the stock rom)..im also starting to think that is related to some bug in the 4.0.4 update..is like the phone sometimes is not able to find the network, untill u move to a different area for a while...
[Samsung Galaxy Nexus] blowtorch:
You need the proper Bootloader and Baseband for a 4.0.4 rom! This must have been said 100 times. For 4.0.4 you need PRIMEKL03 Bootloader and I9250XXLA02 Baseband. Please see the following from GOOGLE http://source.android.com/source/building-devices.html . Pay attention to the bootloader and radio compatibility section and notice 4.0.4 is not "Also possible" with "all previous versions"
[Samsung Galaxy Nexus] Theshawty:
That is invalid. You need the PRIMELA03 bootloader, not KL3, if such even exists. At least LA03 is the one offered in the IMM76D and IMM76I factory images from Google.

EDIT: Strange. On that link, the KL3 is suggested, but LA03 is in the factory images.
[Samsung Galaxy Nexus] clefster:
Has anyone experienced a very slow Messaging app (mms.apk)? I think I started having the problem after moving from a build from 26th May to 3rd June. The Messaging app would take ages to display the list, or send a new message sometimes.. once it had fully loaded it seems faster.. but eventually will have to hang for a while again (ie 10-20 seconds before it responds).
[Samsung Galaxy Nexus] andQlimax:
the last international update IMM76I has I9250XXLA02 baseband and PRIMELA03 bootloader..i have both those

i saw that link, but must be wrong..wher is the PRIMEKL03 bootloader?? is not in any google image i think :confused:
[Samsung Galaxy Nexus] Theshawty:
PRIMEKL03 is older than PRIMELA03 and thus it is suggested to use PRIMELA03.
[Samsung Galaxy Nexus] andQlimax:
i know that..but 2 possible things:

1) there is a typo in the google link

2) that bootloader is really the suggested one

I'm about sure is a typo, but anyway, someone can upload the PRIMEKL03 booloader? in which ota was contained? i googled, but can't seems to find a downlaod link for it..

sorry for the off topic anyway..if someone have a download link, pm me..thanks

lets stop discussing about this

EDIT: is confirmed to be a typo, the suggested is la03 (that page will be updated)
[Samsung Galaxy Nexus] clefster:
Does anyone know if it's possible to download older nightlies? I want to track down where this regression occurred but the get.cm page only goes back 7 days.
[Samsung Galaxy Nexus] dj_ghosie:
http://xdaforums.com/showthread.php?t=1571715
[Samsung Galaxy Nexus] farfromovin:
Alright, code freeze has started :D
[Samsung Galaxy Nexus] andQlimax:
someone read what i wrote? LOL

i was searching PRIMEKL03 (if it exists)

not PRIMELA03..i already have this.

EDIT: is confirmed to be a typo, the suggested is la03 (that page will be updated)
[Samsung Galaxy Nexus] CMNein:
I was never able to find it, the only place I've seen it mentioned is on the recommended bb/bl page, and people asking where they could find it.
[Samsung Galaxy Nexus] hev88:
I was gonna post this last night... thought it was already gonna be old news. Im kinda surprised no one else has mentioned it.

I smell RC1 around the corner :D

Sent from my Maguro

... P.S. logcat or it didn't happen :)
[Samsung Galaxy Nexus] triStateMindgate:
That's good news, took a while to get everything together. Not surprised at all considering new framework and all, but it's nice to see the next step to a RC. CM9 has been stable for a while anyways .:)
[Samsung Galaxy Nexus] dipole:
What is a good kernel to run with this rom? I only ask because I thought I read somewhere that Franco and some other kernel were at odds with CM9? Is Trinity ok? Any workarounds I need to be made aware of with either Franco or Trinity? Sorry if it's been raised before, I'm just trying to get my head around it as I just switched to this ROM from AOKP.
[Samsung Galaxy Nexus] niamul:
understood this is the nightly rom, i have an error to report

i am currently using

maguro	nightly	cm-9-20120614-NIGHTLY-maguro.zip

133.91 MB	2012-06-14 05:35:16

on stock kernel with gapps-ics-20120429-signed

wifi is terrible. i'm 20 feet from my router and i get no bars.

was getting better reception with yesterdays nightly (20120613)

also, gps is still not working :(
[Samsung Galaxy Nexus] FaithCry:
dunno about the AOKP threads but outside kernels are not supposed ot be discussed here as the CM team makes their own custom kernel. so talking about outside kernels clutters the thread. you can use the search or ask in Q&A but the people in this thread are pretty picky about talking about kernels.

each one is different for every person so try everyone out. but if you get bugs, dont report it unless you're using the stock kernel.
[Samsung Galaxy Nexus] thracemerin:
What's funny about all the people who are saying "YAY CODE FREEZE" is, that while the code will be frozen and an RC will get built, this won't stop there from being new nightly builds. So, if you switch to the RC build you won't get the latest updates except for bug fixes to the RC (which will also be in the nightly), so you'll actually end up with an older version of CM than those who continue to flash new nightly builds, I guess that's your choice, the whole joy about RCs confuses me though.
[Samsung Galaxy Nexus] sago62:
They stopped work for rc1? So they say ....
[Samsung Galaxy Nexus] thracemerin:
They don't stop work, they just freeze the current code, look at CM7, there were plenty of changes in the nightlies after they froze for RCs.
[Samsung Galaxy Nexus] sago62:
So the project is not developed Linaro? I understand you correctly?
[Samsung Galaxy Nexus] thracemerin:
Linaro isn't going to be in this RC, at least not based on the comments I've seen, it will probably end up in the nightly builds one of these days and possibly be in a later release.

Codeworkx pointed out in another thread that only Samsung device users have this obsession with RC and Stable builds, all the other manufacturers that CM produces for don't have threads full of "when's the RC?" "when's the stable?", given that RC/stable builds are just the same code as nightly builds frozen at a certain point and bug fixed slightly more I don't get why people think it's some sort of magic milestone where the nightly sucks and the RC is gonna be the holy grail of ROMs.
[Samsung Galaxy Nexus] sago62:
I agree with you ....there is caller rc the first build that kitchen .... Eh eh eh
[Samsung Galaxy Nexus] hev88:
Its not the fact that its an rc its just nice to clean up the code... you know smash lil pesky bugs. Our device is pretty damn stable but I'm sure others are not up to par woth ours and it gives them a chance to clean house, have a "more stable" base and continue work and add more features with all the previous features being flawless

Sent from my Maguro

... P.S. logcat or it didn't happen :)