yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] FaithCry:
try using that magnifying glass and search "app density changer" on the play store.

it might give you something. :rolleyes:
[Samsung Galaxy Nexus] navodwickra:
reporting a bug:

Gmail breaks the LED notification :confused:

how to replicate. reboot your phone and send yourself an email this will break the LED notification until you clear it from the notification bar. after that it all comes back to normal
[Samsung Galaxy Nexus] Beny The Kid:
So, I found a bit of an odd quirk. It would seem that whenever I tap on a phone number link in an email, the phone goes to the dialer but also reads the number and says it's a number link. Looked in accessibility and the explore by touch is off. Turned it on, rebooted and the acted like the setting was on touch wise but wouldn't speak anything as I touched it. Turned the setting off and rebooted and all was normal again, except it still read out the number from the link when I pressed it. Reinstalled the update and same thing.

* edit* so this has now migrated to everything I do in the browser. The phone tells me where I am and what I'm doing. Checked accessibility settings for the phone and the browser and can't find anything to turn off. Anyone else?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] afilopou:
I think you are wrong.CM settings are only in cherry picks from fitsnugly.There is no merge in ics branch (or i can not find any).Same for notification power widget settings.I build from source some time now and there is no cm settings in my kanged rom
[Samsung Galaxy Nexus] Beny The Kid:
CM settings is in the app drawer on our kang nightlies. Was taken out of system settings for now. Notification power widget settings is in there. Honest ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] afilopou:
Speaking for different things

You speaking for the nightlies from here .Nightlies of fitsnugly from first post (cm settings till now is cherry pick from fitsnugly).I am speaking for the commits merged in ics branch of cyanogenmod and i compiled the rom from source .I can not see cm settings in app drawer

Am i wrong?
[Samsung Galaxy Nexus] M3drvr:
I have cm settings in the app drawer. Always have on this build.
[Samsung Galaxy Nexus] afilopou:
You download the rom from first post right?fitsnugly.correct?
[Samsung Galaxy Nexus] efex:
Yes, and CM Settings is in the app drawer (I use the notification power widget). :)
[Samsung Galaxy Nexus] hanschke:
i cannot confirm that the settings will work. i have done it but no app will get su.

i cannot update the su and if i want to flash it with recovery i got an installation error.

http://rootzwiki.com/topic/11406-cm...810-strange-things-are-afoot-at-the-circle-k/

i read it too from other users!

will there no new build today?
[Samsung Galaxy Nexus] jmdsdf:
hanschke, if you haven't figure it out yet: settings/developer settings/enable root access. This probably should be in the first post of this thread.
[Samsung Galaxy Nexus] zephiK:
CM9 and "euroskank" are SOPA striking.

8 PM Eastern Time it'll be back.
[Samsung Galaxy Nexus] joeski27:
Uh, its now 8:30PM eastern time, and still nothing. Hope their "protest" makes a massive and noticeable impact. :rolleyes:
[Samsung Galaxy Nexus] Beny The Kid:
so further investigation leads me to believe it's a setting called "car mode" which I can't seem to disabled. Pressing on the Button in the browser menu just brings me to a page search.

* edit* in accessibility, I had install web scripts checked. Unchecked it and cleared cache in the browser and all is normal again.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stesmi:
So what is the latest - what GApps is the one to use with this rom? I'm asking because I have read several things and several maybes).

// Stefan
[Samsung Galaxy Nexus] hanschke:
back to 01142012-0915. build from yesterday dont work too

---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------

thats done but dont work :p
[Samsung Galaxy Nexus] foreman31:
was this mentioned at all?

I thought the rom was borked
[Samsung Galaxy Nexus] AnalogXDA:
Ask 'em for your money back, champ...
[Samsung Galaxy Nexus] imfloflo:
update-cm-9.0.0-RC0-GN-KANG-signed.01182012-2307.zip

* Boot animation: Custom made by @rascarlo

* CMSettings / FileManager

* Camera: enable face detection

* Mms: SMS templates using gestures

* Settings: Rename CM category to Interface

* Settings: Add preference for enabling root access

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

* CMSettings: Onscreen controls customization

* Notification Power Widget: LTE toggle

* Tuna: Update kernel to 3.0.16

* Dev Tools: New Icon

* Vendor: add camera effects videos

* Trebuchet: PagedView: Fix possible OOB Exception

* Trebuchet: Workspace: Fix Offset X

* Browser: Open in incognito tab on link longpress

* Framework: Hiding media from folder with .nomedia file

* Superuser: Prompt user to enable root access
[Samsung Galaxy Nexus] zurchpet:
Hmm... Maybe I didn't notice it before.

But now that I have...

When booting while plugged in to USB, right after vibrating that boot has finished, still on bootanimation right before the PIN unlock appears, the LED flashes twice. Only happens when plugged in to USB not when plugged in to AC.

Also it doesn't happen when booted not plugged in. the LED flashes then once when USB is plugged in.

Am I the only one experiencing that behavior?
[Samsung Galaxy Nexus] hanschke:
now the superuser appdrawer icon is gone but market told me that su is installed but i cannot open it.
[Samsung Galaxy Nexus] imfloflo:
Don't ask for ETA,

Devs make this as a passion on free time.

Back on topic please CM9 Kang features/bugs
[Samsung Galaxy Nexus] mariotme:
kinda interesting :D

Hope someone would be able find cure for that annoying bug.
[Samsung Galaxy Nexus] Headcase_Fargone:
I'm not sure if this is specific to this build of CM9, CM9 itself, or ICS in general, but when I get an incoming call while streaming music over A2DP (or with Bluetooth connected in general) the phone defaults to Bluetooth when I pick up. Is it possible to change the default to the phone's earpiece so I don't have to manually change it before talking?
[Samsung Galaxy Nexus] Herman76:
Yes, just uncheck 'phone audio' in Bluetooth settings for the device you are connected to.
[Samsung Galaxy Nexus] PhaseBurn:
How do you think us moderators feel? The CM official forums are even worse :-\ Just try to keep in mind most people chew others out over the "no ETA" thing because it isn't the answer they want to hear. As much as it sucks, they do tend to shoot the messenger.
[Samsung Galaxy Nexus] tonker83:
Well Samsung might have built the phone, but Google designed it. Everything in it is what Google wanted.
[Samsung Galaxy Nexus] Theshawty:
I'm pretty sure Google didn't want a defunct radio :p
[Samsung Galaxy Nexus] thracemerin:
Yes, I was in a particularly crabby mood earlier and I want to apologize if I unintentionally offended anyone.

I think the FM chip is part of the bluetooth chip, since on the SGS2 when you turn the FM radio on it also turns bluetooth on, it may be that including this chip includes the FM capability even if it was never intended to be functional.
[Samsung Galaxy Nexus] PhaseBurn:
Turning on/off features in hardware that process an audio stream is also entirely different than implementing the same feature in software. The SGS II may indeed have such a toggle that turns on/off the noise cancellation chip. This would require a kernel driving for a generic device and an interface to activate/deactivate it. Since the hardware processes the audio stream before Android ever sees it, it wouldn't require any other changes to the OS. The audio input received from the microphone would either be noise canceled (if the driver was enabled) or not (if the driver was disabled). It's still analog audio input to Android either way.

As far as Google and Samsung goes, on a Nexus device, the manufacturer works with Google to build a device to Google's specifications which acts as a prototype device for the next iteration of Android. While the manufacturer loses the control they usually have over certain things (Google has final say over every aspect), the phone itself is usually based on technology that is present in a number of that manufacturer's devices. This benefits the manufacturer in many ways when it comes time to design more devices running the next version of Android, as the OS already has drivers for the technology found in the Nexus device, and the design team is already familiarized with the new OS as well.
[Samsung Galaxy Nexus] PhaseBurn:
Most Bluetooth chips also provide FM radio capabilities. Have since the debut of the Nexus One. It's not common they're advertised, or that a driver to access that part of the chip is provided. I remember CM 6 being one of the first mods that enabled FM on the Nexus One - something Google never did officially. Then the CM team wrote/borrowed the MIUI radio app to add it to the official mod. FM radio also was present but disabled on the original HTC EVO 4G for instance - same reasons.
[Samsung Galaxy Nexus] whatsek:
Calendar on lockscreen in the comming nightly! Its getting better and better!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Enhanced:
Awesome. Someone post a screenshot when it's available! I'm curious to see how CM has implemented it.
[Samsung Galaxy Nexus] jcurtis369:
are they still working on the led flashlight toggle or is it just me that is missing something?
[Samsung Galaxy Nexus] snapilica2003:
There is still no flashlight... it'll come eventually.
[Samsung Galaxy Nexus] navodwickra:
Pretty sure this is how it's going to be.
[Samsung Galaxy Nexus] KSTu:
there is new build but is available only on rom manager......
[Samsung Galaxy Nexus] mullemulle86:
I just want to know:

Is the cm kernel included or do i have to flash it seperate?
[Samsung Galaxy Nexus] KSTu:
is included! :):p
[Samsung Galaxy Nexus] Theshawty:
I'm gonna leave CM9 now. Too tired with the **** that isn't working (led light is one thing) and also too tired with the ****storm they blew up regarding kernels and ****.
[Samsung Galaxy Nexus] navodwickra:
it's still a nightly at the moment not even a RC so yes there are bugs. What's thi LED bug? probably the same one which I have
[Samsung Galaxy Nexus] :
Funny, all the "****ty" things you're complaining are working for me. CM9 is the leading rom for my gnex! I'm with cm now for really a long time (HTC hero, desire, nexus one and gnex), and I really appreciate the great work the cm team is doing!
[Samsung Galaxy Nexus] Molitro:
Yeah, the only led notification that wasn't working for me was whatsapp, and it appears now is working consistently...
[Samsung Galaxy Nexus] Theshawty:
I like to have a torch toggle in the statusbar but for some reason the CM team hasn't merged that option yet. Then I also missed a few features from AOKP, like to remove the sound when you adjust volume, and the "IME Switcher" icon in the statusbar when you open a keyboard.

I appreciate the work they're doing as well and CM9 is a wonderful ROM, it's just that no kernel developer here no longer support CM9 for a certain reason I don't wish to explain. It's all explained by Ezekeel.
[Samsung Galaxy Nexus] whatsek:
Not yet, patience my young padawan... ;-)

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] KSTu:
i dunno if is a bug or not but clock from status bar does not change automatically....
[Samsung Galaxy Nexus] CMNein:
Haven't experienced that at all, regardless of time settings. Mine says 3:15am, and I'm at the office already :(

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zurchpet:
Nikademus. Developer of the FuguMod kernel fully supports CM9 and will stick to it, since in the end you all are going to run CM sooner or later.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Theshawty:
I don't even get what it's all about, even though I read what Ezekeel wrote. I'm sure the CM team has a damn good reason for doing so.
[Samsung Galaxy Nexus] luizffgarcia:
They are only making their lives easier, no other reason as far as i can see...

Makes since they are only doing this for fun, but is a shame how much we will all lose as far as custom kernels go!

I understand their decision, don't agree with it, but understand...
[Samsung Galaxy Nexus] Theshawty:
So basically there's no idea in using a custom kernel. Are we better off using CM's CM9 kernel or what?
[Samsung Galaxy Nexus] luizffgarcia:
Basically they are not building CM9 to be used with other kernels, you can if you want but the kernel developers will have to adapt every time for CM9.

It's really up to kernel developers to do the extra work if they want to support CM9.
[Samsung Galaxy Nexus] Razer(x):
What's this thing about kernels? where can i read about it?
[Samsung Galaxy Nexus] mihkohuy:
hi.... can u take a look at ringtone issue?? it forces me to a ringtone even if i changed it,the name is different, the ringtone rings out the same song!!! Then i deleted that song , my GN even rings no sound at all!!!
[Samsung Galaxy Nexus] luizffgarcia:
http://rootzwiki.com/topic/26156-the-egocentric-decisions-of-the-cm-team-why-hurt-independent-devs-and-the-community/
[Samsung Galaxy Nexus] dhuberto:
Friends, waited yesterday to discharge the battery in CM9 ... I connected the charger and the device did not care more: (... so ... I left ... and charging the battery after 4 hours ... I took the battery from the nexus ... I pressed the power button and put the battery again .. then it started :)
[Samsung Galaxy Nexus] Theshawty:
This isn't fun at all, considering franco makes awesome kernels but won't support CM9 anymore. To think I even bought his control app.

Now what am I gonna do? I tried running AOKP again a bit yesterday but I had to return to CM9 as it's the only ROM right now that appeals to me. The stock CM9 kernel sucks in comparison to Franco's/Ezekeel's/Morfic's.
[Samsung Galaxy Nexus] navodwickra:
I am on Franco too didn't come across any kernel related problems though.
[Samsung Galaxy Nexus] luizffgarcia:
I am running CM9 with Franco and it works great. The only problem we will face is custom implementations of the custom kernels.

For me, if the Kernel is stable, fast and battery friendly i don't care if i can't change custom settings...
[Samsung Galaxy Nexus] Theshawty:
True, but I can't have it that way, to have a kernel whose developer hates CM9. I'm gonna roll with AOKP for a while using GLaDOS or Franco kernel. :)

AOKP is the only ROM but CM9 which appeals to me. If not those, then stock.. I can't bother with the other gazillion ROMs out there even though they might be good as well.
[Samsung Galaxy Nexus] crytic:
Please, tell us more about how this free, community-built not-even-beta-yet rom sucks because it has so many bugs and hates custom kernels!

CM devs are not disabling the usage of custom kernels. They just defined a standard in which custom settings have to be set up in sysfs, which is a VERY UNDERSTANDABLE move if you want to support >80 devices.
[Samsung Galaxy Nexus] androidtoy09:
Best way to respond to this problem is just ignore them.
[Samsung Galaxy Nexus] luizffgarcia:
It was taking too long for the shi**y posts about a serious and interesting metter to begin...
[Samsung Galaxy Nexus] snapilica2003:
Thank you for this reply! I couldn't have said it any better.

It's all a question of:

-should the kernel devs adapt to CM's implementation and help the kernel unification that CM is trying to achieve (given that CM is now THE most widely used custom Android ROM (official+kanged), and at the end of the day there's a huge chance that every other ROM out there has some patch of code taken from CM or it's based on the git completely)

or

-should CM team revert to the previous implementation for the sake of the dozens or more kernel developer for each and every device out there "helping" the android kernel fragmentation.

---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------

It's not a ****ty post... go and read that entire thread that was linked above and come back and tell us that he is wrong.
[Samsung Galaxy Nexus] luizffgarcia:
I was the one who posted that link just now, i can assure you i read it carefully...

"Please, tell us more about how this free, community-built not-even-beta-yet rom sucks because it has so many bugs and hates custom kernels!"

If this isn't a shi**y post i don't know what it is...

Anyway, i am done discussing this, if you read the comments of the people involved in the original discussion on that link, such as Franco himself, you will see that they have a really good point...

There are many ways of dealing with one problem, ignoring everyone and deciding something arbitrarily, IMO is not the best one.
[Samsung Galaxy Nexus] snapilica2003:
There's also this other post here http://xdaforums.com/showthread.php?t=1669134 about this situation in which Steve has his input on the matter.

A user said it very well over there: You cannot suppose that CM has to change their standards to adapt to other devs. Its like Samsung asking AOSP to change their code standards to adapt to Touchwiz.

And yes, that first part of the post was a bit rude but people are starting to get pretty annoyed by this.

Instead of ranting on two different forums they could just (as Steve said) posted a patch on CM Gerrit instead of doing all this backchannel nonsense and have it reviewed (and probably rejected) there.
[Samsung Galaxy Nexus] mbroeders:
Are we gonna start the discussion again? Although it's interesting, please, let's keep it development related here. If anyone wants to go because he or she is unhappy with CM9, do so by all means. But there is no need to tell anyone. Unless he or she can provide some logcats or stuff like that to unravel the problem at hand.

I know, I'm not a moderator, but this thread is getting pretty messy right now and that's a shame...
[Samsung Galaxy Nexus] snapilica2003:
I agree.

This thread is 40% filled with kernel talk (which should I use, why should I not use, why doesn't it work, etc.). That's why I had my little rant above, I don't want to hear this "CM9 sucks because of the kernel/mods/<insert other stuff here>" and "Why doesn't CM9 has this <insert feature here> that AOKP has? AOKP is so much better!!11oneone" stuff anymore.
[Samsung Galaxy Nexus] bbgt2:
Amen.
[Samsung Galaxy Nexus] dj_ghosie:
CM set a standard. If u wanna join and build customized kernel, follow it; if not, stay out of it.

If u wanna play in other's house, u play by the house's rule.

Standardization is the fastest way to track and crush bugs.
[Samsung Galaxy Nexus] overthinkingme:
No nightly posted yet? Is that normal?
[Samsung Galaxy Nexus] CMNein:
They've been built, but many not uploaded to the mirror for some reason.

---------- Post added at 08:43 AM ---------- Previous post was at 08:23 AM ----------

Yes! I'm looking forward to Andrew Dodd's response, that gentleman knows his battery.

http://review.cyanogenmod.com/#/c/16878/
[Samsung Galaxy Nexus] bbgt2:
As am I, never been one of the "faithful" to only flash at 100%, always thought this battery stat was useless. Never flashed at 100 % (who can wait) and never had an issue with battery life since I been flashing starting with the Crappy.
[Samsung Galaxy Nexus] CMNein:
Nor have I; glad they're looking at cleaning up CWM. Andrew Dodd is a wealth of information, so I'm looking forward to a dissertation on why wiping stats is useless.
[Samsung Galaxy Nexus] Theshawty:
A question. How is it that CM9 + CM9 kernel yields roughly 1900-2200 in Quadrant while CM9 + Franco kernel yields roughly 3300 in Quadrant + feels lightyears more snappy?
[Samsung Galaxy Nexus] CMNein:
The CM9 kernel has fsync enabled, so it scores lower on the IO part of the Quadrant bar graph. Not sure what difference a huge IO score makes at the end of the day.
[Samsung Galaxy Nexus] Theshawty:
Looks like I should focus less on Quadrant scores ^^
[Samsung Galaxy Nexus] bbgt2:
Oh noes, here we go with Quadrant scores now. Great.
[Samsung Galaxy Nexus] thracemerin:
All the benchmarks (Quadrant, Antutu, CF Bench) can be "faked" with a few kernel flags, most of which don't really make a significant different to the actual performance of the phone despite making the benchmark scores looks amazing.
[Samsung Galaxy Nexus] navodwickra:
I am not bothered about Quadrant scores but definitely Cm9+Franco feels more snappier
[Samsung Galaxy Nexus] Enhanced:
When setting the LED option for a notification to "always on", it stops working entirely. Anyone else have this issue?

I have to resort to using "very long" and "very short" as a work around instead.

I like keeping the LED on so I don't miss anything.
[Samsung Galaxy Nexus] DasEtwas:
Can this rom enable the Mass Storage mode for my GN? Its shown but not alvailable, any place to turn that on? :)
[Samsung Galaxy Nexus] thracemerin:
Nope, the GNex doesn't come with the appropriate drivers to enable UMS, only MTP and PTP.
[Samsung Galaxy Nexus] mako.sk:
download link

pls. download link not work...:confused:
[Samsung Galaxy Nexus] DasEtwas:
Damn you Samsung...
[Samsung Galaxy Nexus] Rogi_tcz:
Use torrent link.
[Samsung Galaxy Nexus] Blacksceada:
Awesome work. Realy impressive...

Also the Apple Magic Mouse works well ;-)

Is there a way to integrate a mouseicon chooser like the one on at Transformer if keyboard docked? Because the mouseicon is realy small and holo-blue only...
[Samsung Galaxy Nexus] thracemerin:
Doesn't mean it can't/won't be added, just means that the appropriate driver would have to be scratch built or ported from another device, so don't expect it soon.
[Samsung Galaxy Nexus] ragnarokx:
I've noticed it stops working after a reboot, and I have to disable/enable it for it to work again.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Molitro:
Samsung?

That's hardly Samsung fault I think.

Sent from my GNex on CM9 pills
[Samsung Galaxy Nexus] thracemerin:
Samsung didn't provide the appropriate driver with the GNex, so it is their fault.
[Samsung Galaxy Nexus] gravis86:
From what I remember the last time this came up...

All wiping battery stats does is clear the data that android uses to run the "Battery" screen in settings (where it tells you what percent has been used by screen, OS, etc).

So of course it's not needed.

Just like wiping cache is part of the updater script when flashing a new nightly, but everyone seems to think you need to wipe the cache manually first anyway...

Or thinking benchmark scores actually matter in some way.

We believe what we want to believe, because it makes us feel good, and we generally disregard the facts.
[Samsung Galaxy Nexus] thracemerin:
Most of the fuel gauge chips used in newer phones don't even write/read the battery stats file or provide that information to the OS, it's an old file from an earlier time that the OS designers never removed and people are under the mistaken belief that it still does anything.
[Samsung Galaxy Nexus] Molitro:
Wouldn't that be Google?

Sent from my GNex on CM9 pills
[Samsung Galaxy Nexus] thracemerin:
Nope, hardware manufacturers provide drivers, Google doesn't manufacture hardware, they made the calls on what hardware but Samsung built the hardware.

In the case of the GNex

Graphics - ImgTech

Wifi/Bluetooth - Broadcomm

RIL/Boards/Other - Samsung
[Samsung Galaxy Nexus] Molitro:
True.

Anyway Google probably didn't care for ums, and didn't demand drivers from Samsung.

Pointless comments anyway, you can ignore me.

Sent from my GNex on CM9 pills
[Samsung Galaxy Nexus] louyaorong:
Can anyone tell me how can I make the nav bar transparent?
[Samsung Galaxy Nexus] G0belet:
It's not a matter of drivers, it's a matter of partitions. /data, /system and the rest are all clumped together as one big partition, meaning you can fill your /data with 16GB of fart apps if that is what you want. Now UMS expects complete control over the memory device, meaning you would need to hand over /data to your computer, which would render the phone inoperable. That's the reason. Advantages are that if /system needs to grow because Jelly Bean is bigger or something, they can.