DR1000 Patch for DR1000 firmware

[rvs]

I was gonna check if this schema was already there, but I forgot and just installed it, so can't check anymore.

It didn't do anything to the safely remove problem (as you already suggested), and the last apps functionality was already working before.

Originally Posted by Mackx

The missing keys in gconf could explain the black-screen during start-up, the keys are read and maybe the code (that I added) does not handle the 'keys not available' situation correctly, causing a crash of (the patched) ctb...
If this is the real problem, the code above should solve that.

To be clear: I didn't have this problem (but others did I think).

Btw. Do you know if there's an easy way to read the contents of gconf (besides gconf-editor)? Is it stored in one file or in multiple files?

[Mackx]

Originally Posted by rvs

To be clear: I didn't have this problem (but others did I think).

Yes, I know, but I was almost ready typing the story when I realised that no code was executed during card-removal so I finished it.

Originally Posted by rvs

Btw. Do you know if there's an easy way to read the contents of gconf (besides gconf-editor)? Is it stored in one file or in multiple files?

I am not a linux expert, but I know that the data in gconf is (also?) stored in a directory structure in /home/root/.gconf (if I remember well). But I am not sure if it is really a directory structure or that the file-system shows a file-structure. It will probably not be safe to change settings there directly.

[rvs]

Originally Posted by Mackx

I am not a linux expert, but I know that the data in gconf is (also?) stored in a directory structure in /home/root/.gconf (if I remember well). But I am not sure if it is really a directory structure or that the file-system shows a file-structure. It will probably not be safe to change settings there directly.

You're probably right. Will try to restrain myself

[fekhner]

after lots of tries it finally works ! great !

I installed iterm and mc as suggested by dima, indeed there were plenty of strange hidden files, probably due to stuffit expander, so I removed all of that,

I tried all the above including the changed apply.sh and adding the open_files schema, it did not seem to work until I copied these files with mc, it was only then that the installation icon changed to mackx hack instead of patch as in the old version (even though it was clear before that some of the new version was installed), now everything seems to be there, but I still have to use it!

off-topic: when I try to lock sensors, either from the menu or from the settings, nothing happens, anyone seen this problem ?

[rvs]

Originally Posted by fekhner

off-topic: when I try to lock sensors, either from the menu or from the settings, nothing happens, anyone seen this problem ?

I've not had any problems. To be sure: you know you have to do both, right? You choose the sensors you want to be able to lock in the settings, then you lock them using the menu.

Did this problem start after you installed the patch?

[Mackx]

Originally Posted by fekhner

after lots of tries it finally works ! great !

Great! I hope the new features are worth the troubles/effort you had.

[Gertjan]

Originally Posted by rvs

Btw. Do you know if there's an easy way to read the contents of gconf (besides gconf-editor)? Is it stored in one file or in multiple files?

gconftool-2 is the preferred way to interact with gconf settings.

The settings are stored in an folder structure with XML files under /home/root/.gconf, but changing them directly is not recommended as it bypasses caches, type validation and sanity checks.

[Gertjan]

Originally Posted by fekhner

off-topic: when I try to lock sensors, either from the menu or from the settings, nothing happens, anyone seen this problem ?

There appears to be some confusion about the way sensor locking works.

The settings page defines which sensors are disabled when the "Lock Sensors" is chosen from the menu (or the Lock icon is clicked). It does not engage the lock itself. When none of the boxes are checked, the Lock Sensors option disables none of the sensors, which is actually quite useless.

[fekhner]

Originally Posted by Mackx

Great! I hope the new features are worth the troubles/effort you had.

they definitely are. while playing with it, I realize that set as startpage, last-app and re-ordering of folders works beautifully, what is still corrupted (from some old installation or because of missing files ?) is the applications, xjournal, install views, they just do not appear contrary to what happened in patch 4. (i did put the apply_sh and the additional openfiles schema) I think that with 1 more cycle of erasing, putting the official firmware and then copying and applying the pacth everything will go ...

btw, concerning the manual, I wanted to read it while not connected to my computer so i copied it from rxvt from

/media/mmcblk0p1/Programs/_mackxpatch/docs/MackxPatch\ User\ Manual
to
/media/mmcblk0p1/Help
using the stylus,

considering the fact that you have to re-type the whole thing when you mis-spell cd instead of cp, and it actually works after that, the feeling of power and affection for the device a pervert like myself gets out of this simple feat is amazing, beats any entertainment you can get with whatever ipad app out there

[fekhner]

Originally Posted by Gertjan

There appears to be some confusion about the way sensor locking works.

The settings page defines which sensors are disabled when the "Lock Sensors" is chosen from the menu (or the Lock icon is clicked). It does not engage the lock itself. When none of the boxes are checked, the Lock Sensors option disables none of the sensors, which is actually quite useless.

thanks a lot, i finally figured it out also after the post by rvs

[ThR]

Originally Posted by fekhner

btw, concerning the manual, I wanted to read it while not connected to my computer so i copied it from rxvt from

/media/mmcblk0p1/Programs/_mackxpatch/docs/MackxPatch\ User\ Manual
to
/media/mmcblk0p1/Help
using the stylus,

"MidnightCommander" is your friend in this case.

[bokjeid]

At first, thanks for your lastest update, mackx! I saw it a little lately, anyway it really helps now..
I also set 'RecentlyRead' as startpage, but when start-up, 'Indexing files' screen doesn't disappear, just stays. So I should click the screen once to make it away. It usually occurs only on my device? Or how can I solve this..?

[Mackx]

Originally Posted by bokjeid

At first, thanks for your lastest update, mackx! I saw it a little lately, anyway it really helps now..
I also set 'RecentlyRead' as startpage, but when start-up, 'Indexing files' screen doesn't disappear, just stays. So I should click the screen once to make it away. It usually occurs only on my device? Or how can I solve this..?

I have not heared from someone else who has the same problem. Does it happen with every start-page or only with the RecentlyRead? How many files are in the recently read folder?
Timing seems to be critical during startup, it seems that some event is missed (or too early).

[ThR]

Originally Posted by bokjeid

At first, thanks for your lastest update, mackx! I saw it a little lately, anyway it really helps now..
I also set 'RecentlyRead' as startpage, but when start-up, 'Indexing files' screen doesn't disappear, just stays. So I should click the screen once to make it away. It usually occurs only on my device? Or how can I solve this..?

a) Check your SD-Card-Filesystem, e.g. with scandisk (windows) and let it repair the errors
b) After that, put the device on ac-power and let it do the indexing over night. Be patient...

[Mackx]

Originally Posted by ThR

a) Check your SD-Card-Filesystem, e.g. with scandisk (windows) and let it repair the errors
b) After that, put the device on ac-power and let it do the indexing over night. Be patient...

It was not clear that the indexing would not disappear (indexing keeps continuing), or that it would disappear when the screen was tapped (screen was not properly refreshed).
@bokjeid: can you clarify?