Turn on developer mode Clara HD

[hansel_]

I am trying to turn on developer mode on my Clara HD running 4.8.10959

I am trying to type devmodeon in the search bar as recommended but nothing comes up.

I have also tried dev mode on developermodeon developer mode on

I have however had a menu show up when I type in demomodeon so I know that works.

Please advise and thanks in advance.

[PeterT]

As far as I know there is no feedback when you've done this. Just go to settings and check on the "Device information" screen for the "Developer options" to be visible.

[JSWolf]

I tried this when I was running 4.7.x. It does work in the current 4.15.x firmware. But the one downside is that having developer mode on writes to log files and there is no way that know of to turn that off other then turning off developer mode.

[NiLuJe]

Logging *should* be controlled by one of the settings, although I've had mixed results with that (i.e., it often logs when I don't want it to, and doesn't log when I want it to ;p).

That may be FW-specific, and/or a random quirk I encountered in my hasty testing of those features. Never bothered to actually look into it, as, more often than not, on current FW versions, it doesn't log, which suits me just fine.

(I happen to always enable it via the config file, and not the search, which may be factor here, so, I'd double-check the config file after the search trick).

[JSWolf]

Originally Posted by NiLuJe

Logging *should* be controlled by one of the settings, although I've had mixed results with that (i.e., it often logs when I don't want it to, and doesn't log when I want it to ;p).

That may be FW-specific, and/or a random quirk I encountered in my hasty testing of those features. Never bothered to actually look into it, as, more often than not, on current FW versions, it doesn't log, which suits me just fine.

I had it logging and none of the options allowed me to turn that off.

[NiLuJe]

At a very quick glance, on 4.17, it doesn't log anything on its own (to a file, I mean). I can save logs on demand from the Developer Options menu (in fact, that's what's at the top of it).

The devmodeon trick *does* set EnableDebugServices=true, and playing with those log settings created an empty Log= entry, since I left everything unticked.

I usually never enable EnableDebugServices myself when I enable some stuff manually, so, make of that what you will .

EDIT: Ooh, shiny. What ticking those checkboxes did is enable a *lot* of extra logging to the syslog, yummy .

[JSWolf]

Originally Posted by NiLuJe

At a very quick glance, on 4.17, it doesn't log anything on its own (to a file, I mean). I can save logs on demand from the Developer Options menu (in fact, that's what's at the top of it).

The devmodeon trick *does* set EnableDebugServices=true, and playing with those log settings created an empty Log= entry, since I left everything unticked.

I usually never enable EnableDebugServices myself when I enable some stuff manually, so, make of that what you will .

EDIT: Ooh, shiny. What ticking those checkboxes did is enable a *lot* of extra logging to the syslog, yummy .

Does this mean with the logging, you'll maybe be able to do some nice shiny new hacks/mods?

[NiLuJe]

Not necessarily (but it certainly can't hurt). I just like logs .

[davidfor]

Originally Posted by NiLuJe

At a very quick glance, on 4.17, it doesn't log anything on its own (to a file, I mean). I can save logs on demand from the Developer Options menu (in fact, that's what's at the top of it).

The device also writes to the log file when you connect to USB. At the most, it writes 512KB. And unfortunately it doesn't do this when you shutdown the device.

The devmodeon trick *does* set EnableDebugServices=true, and playing with those log settings created an empty Log= entry, since I left everything unticked.

I usually never enable EnableDebugServices myself when I enable some stuff manually, so, make of that what you will .

EnableDebugServices enables other things such as the GUI options and telnet. Though I thought it was necessary for writing the files.

EDIT: Ooh, shiny. What ticking those checkboxes did is enable a *lot* of extra logging to the syslog, yummy .

Yep. The basic logs are noisy, but, you can easily get to the point where nothing useful is seen because the log file is to small (unlike my work servers were the log files are to big to be searched easily). Occasionally, I think of looking into how to send them to a syslog server, but, so far I have come to my senses in time and read a book instead.

For the record, I run my devices all the time with EnableDebugServices=true. Pretty much the only time it isn't on is when I do a factory reset or buy a new device. The latter probably happens far to much (and I took time while writing this reply to put the debug and feature settings sections into the config file of my new Libra H2O). I tend to have the SQL, leak and one of the WiFi or Sync related options on. But, change depending on what I'm looking at.

[NiLuJe]

@davidfor: Oh. USB. That would certainly explain it. Thanks .

Random thought: 512KB might be the actual size of the syslog ringbuffer, which is why I usually follow it somewhere when I'm not sure if I'm going to have enough backlog in a single "after the fact" logread call .

(In practice, that usually involves a logread -f in a shell over USBNet, or over WiFi w/ ForceWifiOn for USB-related stuff).