yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Xi2wiked:
Np, tried setting share settings via my phone while pasting links, but apparently google drive doesn't like my phone. Had to grab my laptop.... :eek:
[Nexus 7 Android Development] joe2316:
This is bloody lovely, thanks!
[Nexus 7 Android Development] ziggary:
This is what I use and love it :)
[Nexus 7 Android Development] ejchis:
I'm really enjoying this rom. Thanks for posting. Do you plan to update as AOSP updates?
[Nexus 7 Android Development] Xi2wiked:
More than likely, yes.
[Nexus 7 Android Development] removesstains:
After putting it into tablet ui this is my favorite rom so far. LOL I flashed 4 roms and each one had something that wasn't right. I knew I should have tried this 1st.

My favorite features of pure aosp are:

Rotation on home screen in tablet ui, (I set my density to 160)

AOSP browser

And no annoying custom animations

Thanks
[Nexus 7 Android Development] patmw123:
This is exactly the kind of ROM that I prefer. Thanks for your hard work and I look forward to new updates when AOSP gets updated. :)
[Nexus 7 Android Development] Valerianus:
Will I need a custom recovery to flash this? Or can I just use the default recovery?
[Nexus 7 Android Development] Xi2wiked:
Flash you preferred custom recovery, and make a nandroid backup before flashing. Always get a backup. :D
[Nexus 7 Android Development] rsxtypes72:
I have one question. Did you fix the camera?

I figured it out
[Nexus 7 Android Development] grimez:
I made the jump to rooting my Nexus 7 when I saw this ROM, and I'm loving it so far... However, I have run into a few problems.

Usually, I can use Solid Explorer or Total Commander to delete files out of /system/app/ , but I haven't been able to successfully do this on my Nexus 7. I tried to rm via the android emulator, but it said the system needed to be write accessible. Anyone have an app that can get this done, or the command for making system write accessible? I am after this because of the 2x Gallery apps and the 2x music apps... just trying to clean it up a bit. Really loving everything else about the ROM though, Thanks!
[Nexus 7 Android Development] ejchis:
I use Root Explorer.
[Nexus 7 Android Development] joe2316:
Use ES file explorer and enable rw for system in settings.
[Nexus 7 Android Development] nawoa:
Hi, my N7 just arrived (finally!) so I'm looking forward to trying this out. Not much I want different really, I just need root so I can set the launcher to auto-rotate. I might try CM10 when there's a stable version out but this should be more than adequate until then.

Could you please provide an MD5 for each of the downloads?
[Nexus 7 Android Development] simms22:
nice clean rom, a breath of fresh air. thank you Xi2wiked :)
[Nexus 7 Android Development] jalyn02:
Can we keep Jelly Bean boot animation please. What's with the boot animation from the MyTouch 3G???!
[Nexus 7 Android Development] simms22:
that's the default android boot animation if there isn't one. just pull the bootanimation.zip out of any jelly bean ROM that has the jelly bean boot animation out of /system/media/ and paste it into your /system/media/ with root explorer. it shouldn't take you more than a minute to do.
[Nexus 7 Android Development] nawoa:
Hi, I have a couple bugs to report, sorry if they've already been mentioned:

- The lockscreen gives me the option of launching a camera app, which doesn't make sense. When I selected it just out of curiosity to see what would happen, it gave me the choice of launching one of two stock Gallery apps. This leads into my second problem...

- ...From a clean wipe and format of all partitions, I somehow ended up with two stock Gallery apps after installing this ROM, Google Apps, and SU. I'm not sure but I think the "second" gallery may have only appeared after I attempted to launch the camera from the lockscreen. I can pick either of the two Gallery apps, go to App Info, and disable it. This leaves me with one functioning Gallery app so it's not really an issue anymore but it would be nice if it was fixed.

Other than that, this ROM seems really solid. I can't help but feel that animations and in particular list scrolling in Google Play aren't as smooth as on my Galaxy Nexus (running 4.1.1 stock) though. Maybe there are some Tegra optimizations that aren't enabled by default or something, I might try one of the custom kernels later.

edit: There's one more issue but I'm not sure if you even have any influence over. I have Google Music installed (from gapps I assume), but I'm not allowed to update it as it says it's not available for my region. It's true, Google Music isn't available in Canada, but devices that come with stock Android (Galaxy Nexus as well as Nexus 7) DO come with Google Music and it CAN be updated on those devices. To be clear, I had Google Music on my N7 when it arrived stock and it was possible to update it. Any ideas?
[Nexus 7 Android Development] walaway:
Can someone link beats binary/equalizer and bravia engine? I just want to add that to this rom when I flash it
[Nexus 7 Android Development] nawoa:
I was able to resolve the problem with Google Music not updating by installing it directly from the Google Play site. This brings me to a new issue: Google Play doesn't have any idea what my device is. It calls it "Unknown Full Android on Grouper"... can you fix this please?

This name is also what is presented in bug reports you submit. How's a developer supposed to interpret a bug report that says it came from a "Full Android on Grouper"?
[Nexus 7 Android Development] simms22:
you can change that line in your build.prop to whatever you want it to say. use a root file explorer like root explorer. its in /system/build.prop/. change it then reboot for it to take affect.
[Nexus 7 Android Development] nawoa:
What do I need to change it to so that apps will recognize my device as a real Nexus 7? N.O.V.A. 3 for example says it's incompatible with my device even though it's verified to be compatible with N7 tablets. It should just be fixed properly so this isn't an issue and doesn't result in lots of confused users and developers.
[Nexus 7 Android Development] simms22:
changing these lines to this worked for me and nova 3..

ro.product.model=Nexus 7

ro.product.brand=Google

ro.product.name=nakasi
[Nexus 7 Android Development] nawoa:
This worked, thanks.
[Nexus 7 Android Development] bpingry:
This may not be super important, but for anyone wondering, this ROM seems to be Deodexed...correct me if I'm wrong, but I attempted a manual deodex and it came up saying there were no .odex files in the system apps.
[Nexus 7 Android Development] ronlsjr:
Look in the system folder all the apps are listed there. The rom has no .odex files.
[Nexus 7 Android Development] leelaa:
I here aosp has been updated to 4.1.1 r4.
[Nexus 7 Android Development] rsxtypes72:
All AOSP roms are deodexed. That's how they are compiled.
[Nexus 7 Android Development] R1ptide:
True but tilt sensor and light sensor don't appear to be working

Sent from my SGS2
[Nexus 7 Android Development] Bosio91:
Any news about this ROM? Updates or such?

I've been running it for the past two days, and I simply love it. What kernel are you guys getting best results with when paired with this ROM? I used the latest Trinity nightly, but I noticed the animations to be all a bit laggy and flickery. I switched to the latest faux123 beta, and everything was smooth and buttery again :)
[Nexus 7 Android Development] espionage724:
Anyone else confirm this?
[Nexus 7 Android Development] x-alina:
I compile AOSP, too. How has you solved the Problem that rotation doesn't work? (and Camera, GPSs, ...)
[Nexus 7 Android Development] simms22:
everything works, everything. but to enable autorotation on your home screens add this line to your build.prop and reboot launcher.force_enable_rotation=true

if your build the can, GPS etc is broken, I suggest that you join the android building google group, you'll find help there http://groups.google.com/group/android-building/topics
[Nexus 7 Android Development] trevd:
damm you simms22 for suggesting google groups LOL, you've got me started answering questions on there now. :laugh:

Speaking of answering questions.... Hi there x-alina, I saw JBQ offered you up an answer to your question. I suspect you were after a solution rather than a just an answer. I've got the camera, gps, drm ( libwvm.so, That is part of the drm I think?!? ) and faceunlock ( pittpatt ) working on my aosp build ( JRO03R ). I just pulled the missing binaries from the JR003S image posted here this seems to work a treat. :)

Hope that helps you out!
[Nexus 7 Android Development] :
Sorry for off-topic, but can someone instruct me on how to get the files from my Nexus 7 when compiling AOSP.

I'm able to compile it from source, but it never includes any apps. :confused:

I've read there's a script in the CM source for extracting these, are you using that?
[Nexus 7 Android Development] jamesst20:
Looking too :( How do I get my Camera/Accelerometer/GPS and stuff working :( ?
[Nexus 7 Android Development] trevd:
Hi There

Like I mentioned, just pull the missing binaries from the factory image..... I'd hazard a guess that any factory image will do you at this early stage.

The missing binaries I speak of are located in the /system/vendor and the /system/lib/hw directories. That will get the gps and the camera working, I think the accelerometer and the additional sensors require more files namely /system/lib/libsensors.lightsensor.so, /system/bin/sensors-config there maybe more I'm just testing it now..
[Nexus 7 Android Development] jamesst20:
Thanks you, I just merged the files that I had missing from /system/lib and everything is alright ! Thanks :D !
[Samsung Galaxy Nexus] farfromovin:
**Disclaimer** I love Cyanogen, I support Cyanogen, and I will not "learn to do it myself". I'm not bashing CM, so don't bash me lol.

So, the question is why doesn't CM kernel support USB fast charge? I didn't know where to put this, but questions go here so... I'm talking about Chad's fast charge mod to make your phone charge at AC rates when hooked up to a USB port (or car charger, or lots of other chargers without the pins shorted inside or in the cable itself if I understand that correctly). Every kernel here on XDA AFAIK supports it, but not the king of options, aka CM :confused:

Is it just to prevent damage to some poor saps pc with 500ma USB hookups? I mean, they let us overclock our phones CPU and that would probably have as much damage potential as the fast charge mod, but that's just me thinking out loud. So, does anybody really know why? Has anyone seen any G+ or Twitter posts saying "Why" they decided against this?
[Samsung Galaxy Nexus] RogerPodacter:
I don't know, sometimes its just a matter of submitting the code to their repo. Maybe nobody's done that yet.
[Samsung Galaxy Nexus] XlAfbk:
bump

would really love to have a cm10 stock kernel + fast charge. that really is the only reason i flash other kernels though I'd prefer cm stock
[Samsung Galaxy Nexus] Jubakuba:
CyanogenMod pride themselves on building stable and very functional roms.

I know that when a new android user wants to "root and rom" his phone I would generally recommend CyanogenMod. They're roms are functional and not over-the-top with settings that the general public doesn't understand.

If they built fastcharge into their kernel...they'd probably also want a toggle.

If they built a toggle for it; the "pseudo-noob" user that installs the rom would suddenly be baffled by the fact that they can no longer get files to/from their PC. If they didn't implement a toggle but implemented the mod any user who downloaded a third party application could have said functionality available to them again; and be baffled once more.

Also, the USB port is only going to push out as much power as it was built to. By enabling this mod, you're only telling the PHONE that it's OK to pull more than it normally would from a USB port. The USB port still decides how much to push...so the hack may not even affect some ports at all.

This is my take. It isn't an official statement, but I assume they've known about the mod and had plenty of time to implement it but choose not to.

TL;DR

CyanogenMod is a Rom founded on stability and ease-of-use. This option would probably confuse the general public and is therefore left out.
[Samsung Galaxy Nexus] jjmcc2:
Fast Charge

Easy fix, Have the fast charge code test for data and if it see's data the disable fast charge mode.
[Samsung Galaxy Nexus] kevinjgray88:
Ask them
[Samsung Galaxy Nexus] Nv1dia:
Hi guys. I tried looking for info on this but I'm not sure if it even exists. In any case what I'm trying to ask about is cm9's and cm10's color multiier. I a. In the navy and at night we can't be outside with white light. In order to use my phone outside I have to make the phone monochrome red. I used to accomplish this with chain fire 3d on my old epic 4g touch. After converting to jellybean I noticed chain fire doesn't work. So I've gone to cm10. The alpha builds at least. What I want to do is create a profile that when switched to will switch my screen to the new multiplier settings. To accomplishmy mono red I just turn all other colors to 0. Is there a way to save one of these presets? An app maybe? I just wanna be able to hit a profile and boom there it is. Anyone have any ideas?
[Samsung Galaxy Nexus] hankarun:
I made a simple widget works exactly as you sad. It is in beta. I only tested with franco kernel but i assume it works with all kernels which have color multiplier. You can get it from google play Night Mode Widget Beta. Thanks.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Isriam:
anyone have fixed inverted gapps for note? new theme doesnt work well with standard gapps.
[HTC Rezound] 996:
So I had my Rezound for about one whole month before I decided to purchase an extended battery for it. I decided to go with the safe route and purchase HTC's OEM extended battery which is 2750mAH. The battery makes a difference. I notice it. The thing I want to change is the size increase of the whole phone. The extended battery adds so much bulk and it is getting to be annoying at times. The phone weighs too much and etc.

I want an extended battery that has the OEM fit. No bulkiness. Just sits flush with the original back casing. I know of Mugen which sells the 1900mAH. I was wondering what some of your guys' setups were with extended batteries.

Thanks in advance. Opinions and suggestions would be greatly appreciated.

996
[HTC Rezound] Evocm7:
The mugen batteries are awfully expensive for very little gain. The HTC battery is nice. There are bigger batteries but they add size. Right now Verizon has batteries 50% off. $30 for the OEM HTC extended is a good price. And the backplate looks just like stock. The only thing I hate is the way the backplate attaches and it doesnt fit firmly enough so it creaks but not like its going to fall off or anything
[HTC Rezound] AshtonTS:
Its generally not wise to use a non OEM battery.They are usually cheaply made, and I've heard they can have bad side effects on phones
[HTC Rezound] Evocm7:
That is true as well. I would trust mugen and Seidio since they are actual companies but I know the seidio for the of evo 4g claimed to be 3500mah and was ~$80 and it was tested and only had a capacity of 2800ish which was only 200 more than the sprint 2600mah for $50. $30 more for 200mah is stupid and not likely to notice that difference. As for the slim 1900, I don't believe in those because how do you fit 300 more mah into the same physical space? :screwy:
[HTC Rezound] 996:
Yeah. I bought my OEM HTC extended battery for 30 with the back cover. The cover does squeak. It does not have the solidity of the normal back cover that came with the phone. The battery does help. I was just looking for a thinner one.

I have heard people getting good results with Mugen.

But then again. I have no idea until I try it out.

Don't know if it is worth it -__-
[Samsung Galaxy Nexus] defconoi:
Hey Guys, I've seen people's color settings all over for the Galaxy Nexus, we have different tools, different kernels and different ways to improve the Purple/Red/Tint Issues with Franco's App, Morfics, as well as free tools like Trickster Mod's App and the new CM10 Color Multiplier, Color Gamma Tuning, and Color Hack presets.

Goal: Have all this information in one place

I have created a Publicly Accessible Spreadsheet on Google Docs that you can edit without sign-in, please either

A:Edit the doc with your color settings or

B: Reply to this thread with your color settings for each different kernel and app and one of us in the thread may update the spreadsheet. Also only reply if you can provide useful information regarding these issues.

I know allot of people are stuck with their Galaxy Nexus, so lets all work together on sharing our settings and tips/tricks regarding this since samsung still has not fixed the issue and still sends out devices with this issue. I've heard people go through 5-6 replacements, ouch.

Checkout the format of the spreadsheet, and feel free to improve it.

Collaborative Nexus Color Spreadsheet here

Other useful Screen Color Links:

[Tips] Screen Color Calibration for the Galaxy Nexus

Galaxy Nexus - Purple Tint + Grainy Screen

Trickster MOD app

Color Calibration. Before / after

Galaxy Nexus grainy and vertical banding screen!

Edit: If requested, I could make a Google Docs form to auto populate the spreadsheet

Anyone know of a way to disable the screen dimming on the notification drop down? When it dims on low brightness the notification and background is purple.
[Samsung Galaxy Nexus] happymouse:
No clue how to get rid of the screen dimming on drop down. You should watch out when running the higher contrast numbers, burn in is a spooky thing. I'm glad that a list of some type is being made (suggestion gathering has been abysmal), although every screen has it's own inherent faults and oddities, it will be very interesting to see the results. Thanks man.
[Samsung Galaxy Nexus] Tikerz:
Good idea. I added a couple.
[Samsung Galaxy Nexus] TyroneLT:
Thanks for this list. I've been messing around with color settings for awhile now with no success. I always felt like the screen had a tinge of green that I couldn't get rid of.
[Samsung Galaxy Nexus] osm0sis:
Adding some red should help that. My problem is that there are a couple "hot spots" of yellowing and magenta that I have to strike a balance between. Went through a few different settings but posted my current to the spreadsheet.

Previous:

200,215,280

-2,0,15

-23

And I added a Gradient Fix column since I find using that mod changes what you need for color settings to make things nice.

Also worth mentioning that in some apps the OMAP Gamma runs on a 1.0-2.0 scale (by 0.2s) and in others 5-10 (by 1s), these are equivalent however.
[Samsung Galaxy Nexus] CADude:
Finally a useful idea for a thread.
[Samsung Galaxy Nexus] 8mileroad:
Just wondering, isn't every screen at least slightly different? I'm pretty sure that's why there's color calibration, or the screens would come calibrated perfectly.
[Samsung Galaxy Nexus] CADude:
There isn't a HUGE variation in the differences. Each screen isn't a special snowflake. There's a relatively small, finite number of different screen settings that work for all screens.

This will give people a narrowed-down list to try first instead of spending hours experimenting.
[Samsung Galaxy Nexus] defconoi:
Im finding my self having OCD in getting this perfect lol, just added another setting that I found pretty nice but there is still slight purple at 1-5percent brightness. Thanks guys for adding your settings to the spreadsheet, I think with enough data we can average the setting variables and find a good base setting

For me color is only an issue below 20 percent and sometimes lower depending on gamma settings, im finding that gamma and contrast seem to help more than the actual color multipliers

Edit: Just updated the spreadsheet with more settings others have shared on XDA, credits go to isinisterx, amit_sen

ÜBER™, for sharing their settings in other threads
[Samsung Galaxy Nexus] exzacklyright:
This worked wonders for me
[Samsung Galaxy Nexus] vkamicht:
Really, the only purpose to document all these settings is for statistics. To show that more Nexus screens come with x-color tint than y-color. Even then, you're trusting people to know what white and gray are supposed to look like. I've seen how most people set up their TVs - they're usually wrong.

It doesn't take hours, it's a pretty easy process:

Color multiplier is white balance, which also affects overall color tone. Get two things: a blank white screen, and a pure black screen with white text (settings is easy if you have gradient disabled.) Use these, and go with what you think white should be, unless you have a good reference or a calibration tool. For example, I dropped red/green because my screen was too yellow stock. I then found that I could still almost see the individual red pixels sticking out of text (best way I can describe it), and looking at my home screen felt a little too "pink", dropped red a little more until it looked fine.

Next is gamma/offset/whatever which is the adjustment of everything in between white and black. This one can be trickier because grays can easily look too red/brown, too blue, too yellow, etc. and on these screens the gray balance will change depending on brightness. Yes, sometimes drastically (see: purple tint) This can be a pain if you need to lower greens because green can't be lowered (the screen goes nuts), and the colors don't scale the same, so if you increase red and blue by the same amount one will probably be stronger than the other.

Just from my experiences. And yes, each screen is a special snowflake. Most people are just happy enough with canned settings.
[Samsung Galaxy Nexus] strumcat:
The only thing I would add to that is if you are going to eyeball the whites and grays without a reference, it's better to do it in soft, indirect daylight instead of artificial light, which has various color tints depending on what kind of bulb you use.
[Samsung Galaxy Nexus] exzacklyright:
What brightness setting should we test this on? My colors look fine it's just it's a bit dark on auto brightness which is at like 1/3 brightness

Mandated from Stannis Baratheon
[Samsung Galaxy Nexus] harveydent:
I usually calibrate at maximum brightness, then double check if the settings are ok at 50% and minimum brightness.

You probably should do this on the brightness setting you're most regularly at.
[Samsung Galaxy Nexus] vkamicht:
I personally did my calibration at 50% as I almost never go above that (unless in direct sunlight.) I read in another calibration thread someone mentioned that with default settings 50% brightness is quite close to a "standard" brightness level (measured in IRE) - so I'm going on someone's word, but it looks good and natural to me.

Agreed with this, it'll be different for everyone
[Samsung Galaxy Nexus] exzacklyright:
I think mine looks better setting the trinity contrast to 10...but then again when i add a widget i can't even read anything.

Mandated from Stannis Baratheon
[Samsung Galaxy Nexus] osm0sis:
Screenshots don't really prove anything.. It's all in how your screen looks in person after compensating for the "special snowflakiness" ;)

Take a photo if you want to show us how different settings are affecting things.
[Samsung Galaxy Nexus] exzacklyright:
I just noticed... haha true.. But that's the issue. I can't read the black on the gray.... while looking at my phone. What should I adjust?
[Samsung Galaxy Nexus] exzacklyright:
Still can't figure out what to change. The colors are fine but the darks are dark and hard to compare them to against each other

Edit: I'm stupid! I was using the lowest omap gamma..should be 1 right :/

Mandated from Stannis Baratheon
[Samsung Galaxy Nexus] deepayanneogi:
Currently using Paranoid 1.9.4 which is based on CM10 early preview , so comes with CM 10 default kernel : 3.0.36 .

Color multiplier : 1 , 1, 1

Gamma : RGB : 9:0:16 with DSS gamma : off

No trinity contrast applied ,