Problem: For non-CyanogenMod users who are still interested in the development of CyanogenMod for their devices, it would be convenient to have BBQLog remember the device selection across sessions.
Example: My Xperia Z identifies itself as c6603 to BBQLog, and as this is not the ID used in CyanogenMod builds (which use the codename yuga instead), I am forced to select Sony and then Xperia Z every time I want to see what's going on (which is quite often currently :P).
Solutions: I see two possible solutions,
Save a default device setting somewhere. (Could cause trouble if TitaniumBackup or similar is used to restore settings and the user doesn't realise he is looking at his old device)
Create a more extensive device database where, if no match is found on reported codename, a connection can be made between the internal name, and the name that device has at CyanogenMod. Manufacturer 'Sony' and device 'c6603' would give the CM codename 'yuga' in this case.