Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 17 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 12 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 21 hrs ago - more...
| The Following User Says Thank You to RobbieThe1st For This Useful Post: | ||
 |
|
2010-09-13
, 10:27
|
|
Posts: 160 |
Thanked: 33 times |
Joined on May 2010
|
#172
|
Originally Posted by RobbieThe1st
hm ok
It should be all one line, from the "for.." to the "...done".
However, while those files exist, I just tried it as root... it works(it changes the values), but doesn't seem to do anything. Unless you try with the keyboard half closed(with the lights by default off), then it blinks.
Makes me think that something else is controlling those lights by default, at least in Maemo.
In Bootloader mode, it should work.
edit:
Ok, question for you all:
I'm going to be splitting up my massive shell script into smaller "includes", and I'll have 6-12 smaller sh files.
Where should I put them? - Whats the "appropriate" place to put them, on the rootfs?
i try to find all files to let the keyboard shine and write a pm to MohammadAG.
Perhaps he can help us a little
Greetz
Erazor
|
|
2010-09-13
, 10:35
|
|
Posts: 326 |
Thanked: 335 times |
Joined on Feb 2010
|
#173
|
Originally Posted by RobbieThe1st
Great works Robbie
It should be all one line, from the "for.." to the "...done".
However, while those files exist, I just tried it as root... it works(it changes the values), but doesn't seem to do anything. Unless you try with the keyboard half closed(with the lights by default off), then it blinks.
Makes me think that something else is controlling those lights by default, at least in Maemo.
In Bootloader mode, it should work.
edit:
Ok, question for you all:
I'm going to be splitting up my massive shell script into smaller "includes", and I'll have 6-12 smaller sh files.
Where should I put them? - Whats the "appropriate" place to put them, on the rootfs?
I'll suggest to put them in a simple new directory called beckupmenu in the main root
Or maybe in a directory in /usr/share .. where there are the directory of a lot of programs
By the way ... we all are waiting for your gorgeous work
In my small community i'm continuing to record
cases of successes and failures due to errors, seemingly always related to bad sectors ..
It seems that restoration is successfull on 50% of devices.
Last edited by Dany-69; 2010-09-13 at 10:54.
|
|
2010-09-13
, 11:36
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#174
|
Originally Posted by Dany-69
Yea, the /usr/share/ is probably the best option, but I don't know much about where you are "supposed" to stick such files, though that looks like it.
Great works Robbie
I'll suggest to put them in a simple new directory called beckupmenu in the main root
Or maybe in a directory in /usr/share .. where there are the directory of a lot of programs
Originally Posted by Dany-69
Hm, that's interesting.
By the way ... we all are waiting for your gorgeous work
In my small community i'm continuing to record
cases of successes and failures due to errors, seemingly always related to bad sectors ..
It seems that restoration is successfull on 50% of devices.
But I -am- rebuilding it, with new, better methods. I actually got it to backup once, but now I have to figure out why tar stopped backing up with a read-error. *sigh*.
-Rob
|
|
2010-09-13
, 12:01
|
|
Posts: 326 |
Thanked: 335 times |
Joined on Feb 2010
|
#175
|
ps: is there a way to fix the problem of the "version" of the system.. ?
Flashing with the fiasco, the system informations (firmware pr ecc ecc )
..
Flashing with a custom image it doesn't .. :/
There shopuld be a file somewhere in some other partition ...
That fu.cked chip has 1 thousand partitions -.-'''
The one for the root ... the one for the kernel ... some other one per these informations.. 2 balls -.-
Flashing with the fiasco, the system informations (firmware pr ecc ecc )
..
Flashing with a custom image it doesn't .. :/
There shopuld be a file somewhere in some other partition ...
That fu.cked chip has 1 thousand partitions -.-'''
The one for the root ... the one for the kernel ... some other one per these informations.. 2 balls -.-
|
|
2010-09-14
, 04:00
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#176
|
Originally Posted by Dany-69
Wait, what exactly are you talking about?
ps: is there a way to fix the problem of the "version" of the system.. ?
Flashing with the fiasco, the system informations (firmware pr ecc ecc )
..
Flashing with a custom image it doesn't .. :/
The firmware version?
Have you tried installing a new kernel(or reinstalling the current one) to see if that fixes it?
|
|
2010-09-14
, 10:50
|
|
Posts: 326 |
Thanked: 335 times |
Joined on Feb 2010
|
#177
|
The same with every kernel :/
Even flashing with a clean root image created with backupmenu... no informations in the menu /settings/informations (i don't know the exactly english traduction in maemo ... but you have already understood me) .
Even flashing with a clean root image created with backupmenu... no informations in the menu /settings/informations (i don't know the exactly english traduction in maemo ... but you have already understood me) .
|
|
2010-09-14
, 11:28
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#178
|
So a device at PR1.1, when flashed with a PR1.2 image doesn't have information in some info screens...?
If so, this isn't an issue. PR1.1 and PR1.2 are different; PR1.2 updates the firmware of several pieces of hardware in the N900 like the GSM chip.
You would probably want to flash PR1.2, then load the image.
If so, this isn't an issue. PR1.1 and PR1.2 are different; PR1.2 updates the firmware of several pieces of hardware in the N900 like the GSM chip.
You would probably want to flash PR1.2, then load the image.
|
|
2010-09-14
, 11:35
|
|
Posts: 326 |
Thanked: 335 times |
Joined on Feb 2010
|
#179
|
Flashing with the fiasco yes, the informations appear.
But flashing with a custom root made by backupmenu (even if this "custom root" isn't really customized, but only cleaned) , with no variations of kernel .. the informations don't appear ..
It seems that something more is flashed with the fiasco ...
Some files put somewhere in the chip .. but not in the common partition that we call root..
Like it happens with the kernel (but it isn't the same of the kernel because even not touching it, the problem remains)
But flashing with a custom root made by backupmenu (even if this "custom root" isn't really customized, but only cleaned) , with no variations of kernel .. the informations don't appear ..
It seems that something more is flashed with the fiasco ...
Some files put somewhere in the chip .. but not in the common partition that we call root..
Like it happens with the kernel (but it isn't the same of the kernel because even not touching it, the problem remains)
|
|
2010-09-15
, 07:59
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#180
|
Wait. Can you tell me the exact steps needed to reproduce this issue? Like "install this", "copy this", "go to settings > x > y"?
However, while those files exist, I just tried it as root... it works(it changes the values), but doesn't seem to do anything. Unless you try with the keyboard half closed(with the lights by default off), then it blinks.
Makes me think that something else is controlling those lights by default, at least in Maemo.
In Bootloader mode, it should work.
edit:
Ok, question for you all:
I'm going to be splitting up my massive shell script into smaller "includes", and I'll have 6-12 smaller sh files.
Where should I put them? - Whats the "appropriate" place to put them, on the rootfs?
Last edited by RobbieThe1st; 2010-09-13 at 09:22.