yashsingh1/xdaforums huggingface dataset:
[Nexus S General] rrohanjs:
hey buddy can you please add this rom in the development section, i am sure it will become the most downloaded rom especially those notification widgets wow ...

and plus it would be easier for all your rom users to interact and ask for help under one thread .. can you ? or allow someone else to post it and give credit to u
[Nexus S General] bearsblack:
wow, I have not discovered this part of xda recently and this is exactly what I wanted to post about I am running build 14 right now and it is excellent so far. I just can't register to rootzwiki from my phone and comment on how nice their work is. I wanted to say that I thank them and Eugene for the kernel it is awesome.

ns4g via xda app
[Nexus S General] HAKA:
Nice ROM.....welcome to the future of CM guys!
[Nexus S General] jblazea50:
Those running this rom on the NS4G with Eugene's kernel, does the map/navigation work without any freeze or lag?

Thanks
[Nexus S General] Romanbb:
I don't have a nexus s so I won't post the builds here. They're available at rootz for the time being. JonathanGrigg may be posting it here at XDA at his leisure. He is taking care of all the crespo specific things for the ROM.

Someone can setup an [INFO] thread like some of the others if you guys want if at xda.
[Nexus S General] decalex:
So far, yes, still lag with maps and Eugene's kernel. I shoulda tried it with the stock kernel, but forgot..

All that aside, I f'in love this rom.

•°NS4G • ICS°•
[Nexus S General] syntax_gosong:
I guess it have been posted on xda. Is it the same with this :

http://xdaforums.com/showthread.php?t=1432408
[Nexus S General] rrohanjs:
it came after i posted the link here .. :) or rather seeing this link it came ther today ..
[Nexus S General] SComp23:
How do I get them there notification drop-down toggles? I can't find them.
[Nexus S General] rrohanjs:
system settings - rom control
[Windows Phone 7 Q&A, Help & Troubleshooting] Stitch19:
I am planing to get HTC titan in few weeks and I want to ask few questions:

1. Can you turn off threaded messeging? I just want normal messeging dont want FB and other messages to mess with my text messeging.

2. I heard in win mob 7 you cant forward messeges? True or anything to do about it?

3. My country (Cyprus) isnt supported in xbox live etc does that mean I cant buy games from the market but only free ones? Any workaround that?

Thanks :)
[Windows Phone 7 Q&A, Help & Troubleshooting] XboxOmac:
1. Sorry, threaded messaging is what is there in every Windows Phone.

2. Of course you can forward.

3. I'm not so sure about this, but I'm sure you'll still have games to download even without Xbox Live.

Sent from my Samsung Focus Windows Phone using Board Express
[Windows Phone 7 Q&A, Help & Troubleshooting] Stitch19:
So I cant have a conversion over text message with someone without having facebook and any other **** cramed inside the chat and making me confused?

Wow I thought turn off option wasnt that hard for a giant like Microsoft.

I guess no windows phone for me.. I had win 6 on hd2 and had the option to turn off threaded messeging LOL...
[Windows Phone 7 Q&A, Help & Troubleshooting] dtboos:
You don't have to have facebook chat turned on. Keep yourself signed off.

How is it confusing to keep your messages from somebody in the same thread from different sources? If you'd rather go back and forth between different apps to converse with the same person feel free.
[LG Optimus 2x] Barnabe619:
Hello everybody !

I saw that some phones (iPhone 4, Galaxy note, Samsung omnia7) had a GPS chip which also allows to use Glonass (Russian GPS). I've also seen (while searching for information about this glonass) that having 2 times more geo-localisation satellites would make the GPS lock 3 times faster.

So is it possible to enable glonass support in our phone ?

Thank you for your answers !
[LG Optimus 2x] redjge:
which phone model are you referring to?

glonass support starts from the chip itself. so if you unit's support is only GPS, then you can't enable glonass.
[Motorola Droid RAZR] facinater:
I can barely hear music thru my motor by headset. Calls are OK though.

Any fix?
[Motorola Droid RAZR] SallyC:
I have the? Motorola Sliver and no problems with volume at all. In fact, I must keep it turned down. What do you have?
[Motorola Droid RAZR] Deleted member 4177996:
Download and try the free version of Volume+. BE CAREFUL with it. It allows you to amplify sound beyond the specs listed for the phone. Use it gradually (try +1, then +2, etc. if necessary). It has individual settings for headsets, bluetooth, and the regular speaker.
[Motorola Droid RAZR] seanmcd72:
Bluetooth through my car radio (alpine cda-105 with a KCE-400BT) is kind of low, but I paired it with a new 2012 VW and it was perfect. So I don't think it's the phone.
[Motorola Droid RAZR] zelet:
I've noticed that the phone automatically adjusts the volume down to about half when it's paired with a bluetooth media device. Then when you turn up the volume the volume level displayed on the phone will go up but the sound doesn't get louder. There are three fixes I found that work depending on the circumstances:

1) Hit the volume down button. This might get the volume level displayed to drop to half immediately. If that's the case then you can turn up the volume like normal and the sounds should go up to normal.

2) If the first one doesn't work try to un-pair and re-pair the devices.

3) Next try to delete the bluetooth pairing completely and start over.
[Motorola Droid RAZR] jiwengang:
What headset you have? I hope its not the LG one...
[Motorola Droid RAZR] facinater:
The latest leaked update fixed my volume issues.
[Samsung Galaxy Nexus] ro_explorer:
Ok .. so, seeing many questions w/o real answers regarding the power consumption of the GN under various circumstances, I decided to create some testing conditions and generate some data.

The original idea and requirement started on Franco's kernel development thread but as this topic might be of interest I decided to create its own thread.

Test conditions:

- device: Galaxy Nexus i9250 - GSM version

- rom: bigxie's rom

- kernel: Franco kernel

*************************

1. IDLE test

2. MP3 play test

3. DISPLAY test

4. CPU Power test

5. Still image test

6. MKV play

7. Additional Display, MP3 play, YouTube and TuneIN media streaming

*************************

If you have any suggestions of tests you would like to see, please drop me a PM so I can make a list and implement them (depending on my possibilities).

*** Original post was heavily modified due to inaccurate measurements. The replacement posts linked here are the ones that matter ***
[Samsung Galaxy Nexus] c00king.c0w:
Why exactly did you decide not to run tests with wifi and 3G/2G, like grabbing and playing a youtube video?
[Samsung Galaxy Nexus] ro_explorer:
That was the plan but seeing that I don't have enough resolution for this run, I decided to keep the test as simple as possible.

In few hours I'll do a more detailed run, with 1mA reasolution and I'll include online media too, as well as wifi versus 3g power comparison. It looks like a long friday night for me :)

// sent from my green robot //
[Samsung Galaxy Nexus] c00king.c0w:
Haha! Well... I'm already looking forward to those higher res tests... don't forget to include 3G vs 2G as well, because I'm really not sure if there is much of a difference since you take so much longer to load... oh, maybe not a late friday but an early saturday? :p
[Samsung Galaxy Nexus] RogerPodacter:
thanks for doing these tests, its a great idea and cant wait for more results.
[Samsung Galaxy Nexus] @rbiter:
Yes. Thanks. Definitely need more.

My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
[Samsung Galaxy Nexus] ro_explorer:
Thank you for support guys :).

I've managed to build the new test circuit. I can now read the current with 1mA steps.

As a first set of measurements with the new setup - idle power :).

Kernel and rom - see first post.

HotPlug function is a feature of Franco's kernel to turn off CPU 1 while phone is in sleep mode (in case some of you are wondering). It is supposed to be a feature to save power while phone is idle.

Voltage constant at 3.9V over all set.

1. AIRPLANE MODE - any governor, both 350-1200 and 700-1200 frequency range:

1.1. HotPlug OFF - 3 mA steady

1.2. HotPlug ON - 3/4 mA - the multimeter was unable to choose a value

So .. in airplane mode, the standby power is between 11.7 - 15.6 mW

2. 3G mode,WiFi - OFF, interactive governor

2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA

2.2. Freq: 700-1200, HotPlug - OFF - 4/5-8 mA

2.3. Freq: 350-1200, HotPlug - ON - 4-8 mA

2.4. Freq: 700-1200, HotPlug - ON - 4-7 mA

3. 3G mode,WiFi - OFF, conservative governor

3.1. Freq: 350-1200, HotPlug - OFF - 3-8 mA

3.2. Freq: 700-1200, HotPlug - OFF - 3-8 mA

3.3. Freq: 350-1200, HotPlug - ON - 3-7 mA

3.4. Freq: 700-1200, HotPlug - ON - 3-6/7mA

4. 3G mode,WiFi - ON, conservative governor

4.1 - 5GHz WiFi

4.1.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA

4.1.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA

4.1.3. Freq: 350-1200, HotPlug - ON - 4-7/8 mA

4.1.4. Freq: 700-1200, HotPlug - ON - 4-6/7 mA

4.2 - 2.4 GHz WiFi

4.2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA

4.2.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA

4.2.3. Freq: 350-1200, HotPlug - ON - 4/5-8 mA

4.2.4. Freq: 700-1200, HotPlug - ON - 4/5-8 mA

When NOT in airplane mode, my phone has data and sync ON, and (over night at least) only Google services are being synced - gmail, g+, gtalk.

The measurement with data on/off, sync on/off are identical to the data on, sync on, when there is no activity that is. So, the the only way the phone will consume more power when data/sync is on is exactly when an event is being synced .. the rest of the time the radio being idle, identical with data/sync off.

Conclusion regarding IDLE (in my case at least): best power saving while phone idle is with WiFi off while screen off (or on only when plugged), conservative governor, 700-1200 freq. range and HotPlug - ON. Of course these values are experimental and are specific to my device but the numbers are looking reasonable.

I did not take any video of the above measurements because it was really boring .. put device at sleep and wait for it to really sleep (about 2 minutes for each test). But I'm attaching a photo of the test bench :).

... to be continued with awake tests with video capture also ...
[Samsung Galaxy Nexus] aron7awol:
Awesome work!

I can think of one more scenario that's worth testing: when the screen is off but there is a wakelock keeping the CPU awake. This would give us a baseline of CPU awake but screen off, which would tell us exactly how much juice is going to the screen and CPU when the device is on.
[Samsung Galaxy Nexus] ro_explorer:
Would MP3 play in background meet your expectations?
[Samsung Galaxy Nexus] aron7awol:
Wakelock but idle would be ideal I think, but actually an MP3 playing might be perfect if you can compare MP3 playing with the screen on in one of the previously tested states and MP3 playing with screen off. Then some simple subtraction should tell us everything we need to know.

I'd like to be able to calculate how much is used when the CPU is awake due to a wakelock, and how much power is saved by getting out of that wakelock ASAP to get back to power collapsed state. It might turn out that ideal screen off profile is 920 or even higher.
[Samsung Galaxy Nexus] silow:
Good stuff. Glad someone is taking their time to collect this data.

Something to try: Loop a program to browse site content with white (light) heavy colors vs black (dark) heavy colors.
[Samsung Galaxy Nexus] RogerPodacter:
excellent info. if anyone's interested we did a similar test with the nexus one where we were able to use the actual resistor in the fuel gauge chip within the battery. so we did various testing scenarios, and that phone pulled very high currents. seems like our galaxy nexus is actually more efficient with some of those screen tests.

here's the link, prob boring though since it's not our shiney new GN.

http://xdaforums.com/showthread.php?t=998544
[Samsung Galaxy Nexus] ro_explorer:
This is my simple, yet efficient circuit (and quite precise I might say).

As you can see, the sense resistor is quite small not to interfere with normal operations and I think the 1% tolerance is making it perfect.
[Samsung Galaxy Nexus] ro_explorer:
MP3 test

This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no

Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).

I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.

Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU

Values from this second test:

~0.62W consumption with screen ON, autobrightness, showing homescreen

~0.72W when mp3 is started (70% volume, headphones)

~0.155W with screen off/playing mp3

~0.05W with screen off, no mp3 play and a software waiting for input (in this case, poweramp's lockscreen)

~0.011W in standby - airplane mode.

The above values are with 350-1200MHz freq range, conservative gov.

The frequency CPUs have used during screen-off play was 350MHz. If I'm increasing the min. frequency to 700, the average consumption is increasing with an average of 2-3mA.
[Samsung Galaxy Nexus] aron7awol:
Perfect. Thanks so much for taking the time to do this. I had been trying to come up with a semi-scientific way to measure some of this stuff and you just hit it out of the park with this.

Do you know what frequency the CPU was at when playing the MP3 with the screen off?
[Samsung Galaxy Nexus] ro_explorer:
Display test

This is the hi-res (1mA) display test: http://www.youtube.com/watch?v=cqSQ5QE-4S0

Values (with device awake, of course):

- auto brightness, relative low light conditions, dark homescreen: 162mA / 3.87V = 0.14W

Maximum brightness:

- white screen: 380mA * 3.8V = 1.44W

- red screen: 287mA * 3.83V = 1.1W

- green screen: 295mA * 3.82V = 1.127W

- blue screen: 327mA * 3.81V = 1.246W

- gray screen (50%): 240mA * 3.84V = 0.92W

- black screen (but awake): 147mA * 3.87V = 0.57W
[Samsung Galaxy Nexus] ro_explorer:
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application :) ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.
[Samsung Galaxy Nexus] aron7awol:
Thanks, my guess is that this CPU can play an mp3 at 350 MHz just fine :)
[Samsung Galaxy Nexus] ro_explorer:
I've solved the mistery :) ... above post updated.

The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.
[Samsung Galaxy Nexus] aron7awol:
Sorry to keep bothering you for more, but do you also know the CPU usage playing the mp3 at each frequency?

The final question I'd like to be able to answer is: Is getting to idle faster at the expense of using a higher frequency to get there beneficial?

I guess to answer that question we need to separate how much power the CPU uses at 100% CPU usage at 350 MHz, 700 MHz, 920 MHz, etc.
[Samsung Galaxy Nexus] twilightrevenant:
Love the new data! awesome awesome work.
[Samsung Galaxy Nexus] ro_explorer:
You're not bothering me .. this is the intent of this thread .. to bring as much light as possible regarding power. Let's try to do that :).

I'll start testing, I'm not sure how can I reliably do these tests but let me try.
[Samsung Galaxy Nexus] aron7awol:
It's probably difficult to get values for 100% CPU usage with screen off, but a simple benchmark that pegs the CPU to 100% and does nothing else should work. I'm thinking something like SetCPU stress test with screen at minimum brightness and testing with min/max at 350, 700, 920, etc. Get an idle baseline right before starting the stress tests to be able to subtract out the power going to the screen.

The data for "race to idle" has to be at 100% because the whole point is to get the work done ASAP in order to get back to sleep. Of course, the fact still remains that when our devices are awoken, it's not always for a CPU intensive task, but this would at least tell us about the cases when it is.
[Samsung Galaxy Nexus] RogerPodacter:
this phone seems to get excellent idle power draw around 0.01 W.

the power draw with all black screen display seems to be around 140 mA at min brightness...i wonder how low it could really get.
[Samsung Galaxy Nexus] voxigenboy:
You know, one thing with the LTE version(yeah i know you're talking about the GSM one) is that people always go "the LTE is draining the battery! switch to 3G mode!"... I've noticed that regardless if LTE is on/off, the battery drain still isn't much different at all. Whereas with past LTE devices that was a different story. It seems at least now the LTE drain issue has been patched up a bit for this phone.

I decided to test it out recently and watched the same video twice(with LTE on, and with LTE off). With LTE off there was only a drain difference of 4%. That and of course, according to 'battery usage', the screen seems to be eating up all the juice.
[Samsung Galaxy Nexus] ro_explorer:
CPU Power test

Ok .. so, by request, this is the CPU power consumption under 0/100% load at different frequencies.

For start, when screen is OFF and the phone is idle, the CPUs are also OFF because I get 3mA consumption no matter what fixed frequency I'm choosing (except 1350MHz where I get 3/4mA, unstable reading).

Now, for the screen ON these are the conditions:

- antutu benchmark, CPU and Memory test only

- idle and full values are while the screen is showing the antutu test screen

- brightness at minimum

- minimum (for idle) and maximum (for full utilization) values recorded

IDLE:

350MHz: 152mA * 3.98V = 0.6W

700MHz: 163mA * 3.98V = 0.649W

920MHz: 166mA * 3.96V = 0.657W

1200MHz: 167mA * 3.95V = 0.66W

1350MHz: 168mA * 3.94V = 0.662W

FULL:

350MHz: 240mA * 3.95V = 0.948W

700MHz: 380mA * 3.9V = 1.482W

920MHz: 503mA * 3.85V = 1.936W

1200MHz: 770mA * 3.75V = 2.887W

1350MHz: 880mA * 3.7V = 3.256W
[Samsung Galaxy Nexus] ro_explorer:
You can say that loud and repeat it :) ...

As you can see from my tests so far, the CPU will eat up serious juice only when is really really heavy loaded ... but the screen will draw about 1W of power every time you're using it ....
[Samsung Galaxy Nexus] @rbiter:
I am curious to how low it can get with a viewable picture still. But i think this would be likened to stock voltages for cpu's. A common denominator voltage where every thing is stable and works still. Some people exhibit anomalies with low brightness, and some people fare better than others. I'm sure mine could go a little bit lower still before graininess or lines but until the 32GB comes out and it is in my hand, I'm not willing to try until somebody else does. Lol.

My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
[Samsung Galaxy Nexus] aron7awol:
So based on all of this awesome data the ro_explorer collected:

Device is in deep sleep, something wakes it up to fetch a small amount of data from the internet, using a tiny bit of CPU. You definitely want your device at 350 MHz in this case to save power while the CPU is idle or lightly being used. The time the device spends awake is more dependent on data transfer in this case, so ramping up the CPU doesn't help us get back to sleep any faster.

Device is in deep sleep, something wakes it up to do something extremely CPU heavy. Let's say it's a task that will take 100% CPU usage at 350 MHz for exactly 60 seconds. Is it better to have the device stay awake for the full minute at 350 MHz, or should the system ramp up the CPU speed higher to "race to idle" faster? Let's assume performance scales linearly with clock speed even though that isn't 100% true and see how much power is used in 60 seconds in each case...

350 MHz for 60 seconds @ 0.398 W = 23.88 Ws (Watt-seconds)

700 MHz for 30 seconds @ 0.932 W = 27.96 Ws + 30 seconds @ 0.012 W = 28.32 Ws

920 MHz for 22.8 seconds @ 1.386 W = 31.60 Ws + 37.2 seconds @ 0.012 = 32.05 Ws

1200 MHz for 17.5 seconds @ 2.337 W = 40.90 Ws + 42.5 seconds @ 0.012 = 41.41 Ws

1350 MHz for 15.6 seconds @ 2.706 W = 42.21 Ws + 44.4 seconds @ 0.012 = 42.74 Ws

Since you don't care about "responsiveness" when the device is off, this data says you want the CPU at the lowest possible frequency to save power. Getting back to sleep at the expense of additional power is not beneficial. This makes screen off profiles with a low maximum frequency make a ton of sense to me.

I have to run to dinner now, but if anyone has any questions about how I got some of the values above, I'll be happy to respond to them later.
[Samsung Galaxy Nexus] @rbiter:
I run my screen off profile @ 350/700. Twice the frequency at a small cost. I noticed an improvement. In heat also. No heat at all in sleep when I changed to max 700. But this could also be a ymmv.

My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
[Samsung Galaxy Nexus] ro_explorer:
Still image display test

So .. another one ... still image test: http://www.youtube.com/watch?v=ad7uVQK-ViU

The CPU was locked at 350MHz so the jumping around in frequencies should not alter the readings. The image viewer used id Quickpic

The only variable here is the screen brightness:

- 0% : 166mA * 3.94V = 0.654W

- 30% : 190mA * 3.93V = 0.746W

- 50% : 208mA * 3.92V = 0.815W

- 75% : 232mA * 3.91V = 0.907W

- 100% : 254mA * 3.9V = 0.99W

- auto : 179mA * 3.93V = 0.70W

Conclusion: manual brightness at ~30% is the most recommended for viewing pictures. (and to use the screen under "normal" conditions).

Why 30%? because at this point the whites are white and grays are grey on this amoled display (or not disturbing, anyway). Also, at 30% the power consumption caused by the screen is still reasonable.
[Samsung Galaxy Nexus] ro_explorer:
MKV play

This test is very simple and straight forward. No conclusion here .. just average numbers for you to take into consideration when planning to have a long airplane/bus/car/yacht trip.

http://www.youtube.com/watch?v=HNk780X2ChA

Auto brightness, cpu on conservative gov, 350-1200 freq. range.

Player: Dice Player - is using Hardware Acceleration to render movies.

720p: average 1.4W

1080p: average 1.45W

The GPU is working indeed :) ...
[Samsung Galaxy Nexus] twilightrevenant:
If you have time, do you mind flashing franco's kernel #8 and compare idle battery drain?

I was testing yesterday, and I could get down to -12~-14ma (according to battery monitor widget) as compared to -36ma on kernel #10

Using an update frequency of every 5min. But my results may not be reliable
[Samsung Galaxy Nexus] ro_explorer:
Sure, but not today. I'll do also this test when I'll resume testing, tomorrow.

// sent from my green robot //
[Samsung Galaxy Nexus] @rbiter:
Wouldn't video be running off the iva3 video chip and not the gpu in this case. I'm not 100% but maybe you or somebody else could enlighten us.

My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.