I figured it's kinda pointless seeing it in daylight... so I just switched it on (it's 1am, plenty dark enough i suspect)
oh and just to explain... I'm using 2n2222's and no "current regulation" each npn can deliver around 800ma, so I use a 68 ohm resistor to the base pin for each segment, this rougly supplies 120ma per color which is well within spec of the transistor... I purposely kept it low knowing that when the LED heats up, i expected the current to rise up to 200 maybe 300ma, in which case it's well within spec of the 800ma limit of the transistor AND within the 300ma per RGB channels from the 10 watt.
So, 120ma * 3 * 5 = 1.8amps or 21watts.
The multimeter reads 1.8 - 1.9 amps...
Now, because I have no current limiting resistor on the emitter/collector side of the LED, it relies just on the 68ohm resistor, I originally was going to use something like a 30-40ohm resistor and 1/4watt was not up to the job, so i stuck with the 68 ohm resistor and *hoped* that once the LED's warmed up, it would draw more current to get to the 300ma mark.
And (as I suspected) ... No.
The heatsink keeps the LED's cool and sadly (even in 45c / 100f+) heat, still no... maybe if i run it for a few hours instead of 30 - 40 minutes the current will slowly creep up? - good because I like bright.
next time i'll use 1/2watt resistors and push the 50watt boundy, as it is 21watts is bright enough.
Over the weekend, I finally got around to finishing a similar thing, except i used 5 of them... potentially it can supply over 50 watts of light but I decided to limit the current, it pulls around 2amps at 12v (or 24watts) and decided that's bright enough.
But i also did what you did using an attiny85 for the bedroom, they certainly beat 5mm LED mood lights you get from shops..
The none delay works like someone using a stop watch, so you get the millisecond count and at some point you get it again, you compare the two time stamps (oldtime-newtime) gives how long it's been running for, be 5 seconds or 5 hours.
Java for one objective c (why?? Whyyy apple why!) For the other.
I decided to learn java myself and develop for android, I hate the way java is structured, all the try, excepts, crashing if you don't give it the right permissions, the fact that the app will terminate if it becomes unresponsive, the lack of asynchronous sockets (you need to thread everything) just well I hate it but it's an evil I must learn!
If it had windows style messaging life would be nice.. so the ANR and how everything must be threaded or it can crash is a downer.....
To answer your question.... if you want a write once, compile once and then distribute it to both android and ios, take a look at delphi XE5 I like it but my computer is getting on the tad old side so I stuck with java (for now) but Delphi will allow you to write apps for all the major platforms without you lifting a finger...
But, it's bloated, all of it's runtimes are embedded into the apk file, while it's true you could knock up a program in 5 minutes vs a few hours in Java, it comes at a cost in filesize...
When I make a fortune from java, I'll buy a super computer just so I can compile and run apps from delphi xe5