[01:08] chirp [01:40] Does it work ? with lotsa hours ? [02:52] It does so far. I won't know how long it actually lasts until I go through a few discharge cycles. [09:27] Morning [09:35] Morning. === JonathanS is now known as JonathanD [12:17] Morning peoples, dogs, turkeys and everything else === yoda_van is now known as jedijf [12:27] jedijf: Roling's Bakery is still open [12:28] I went by yesterday morning and they were open [12:32] darn === pleia2_ is now known as pleia2 === io is now known as IdleOne [18:14] I just compiled a C++ program on my phone. That is pretty neat. [19:16] phones can compile without tying up phone for hours and hours ? [19:17] And without draining the battery? [19:47] It compiled pretty quickly. I wrote Qt application of a few lines and compiled and ran it [19:47] idk about the battery drain. 99% of the time will be spent in the editor so I don't imagine that gcc will do much harm even if it is CPU intensive. [19:48] If you want to see for yourself then you have to get C4droid. [19:51] ChinnoDog: You seem to be confusing clock time with cpu time [19:51] When you're editing, the cpu spends most of its time idle and consuming very few resources [19:52] Yes, and the screen draws the most power [19:52] We were talking about compiling though [19:53] At least on my iphone, it's true that the screen consumes a lot of power. But the screen PLUS something else consumes a ton more. [19:53] e.g. running the gps for an extended period, it gets pretty warm [19:54] or trying to connect when I have a weak cell signal [19:58] The S3 battery drain from the screen is above average because of the technology in use. The drain while using the editor shouldn't be bad. Yes, I wouldn't want to do that all the time though given that I more than tripled my battery capacity yesterday I could probably get away with it pretty easily. === MutantTu1key is now known as MutantTurkey