Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 1 hr, 37 mins ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 1 day, 22 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 2 days, 19 hrs ago - more...
| The Following User Says Thank You to MyPhoneHasWaifu For This Useful Post: | ||
|
2014-10-10
, 16:19
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#2
|
Originally Posted by MyPhoneHasWaifu
It used to be so in older versions of ubiboot so that if the device was powered off and inserted to a wall charger, it went to repair mode instead of charging mode.
However, I was using ubiboot as my bootloader since I had nemo installed on the device prior. Since the changes to the ways I can use the device, I decided that I don't need that anymore (and the hassles of dealing with it like charging to 10% via flasher if it's 0% (due to it trying to mount all the filesystems instead of charging if I just plug it in the wall???))
This was corrected in version 0.3.0 however, so if you have this problem you either have too old ubiboot or the configuration is wrong.
(There is a configurable parameter to enable/disable this feature...)
Originally Posted by MyPhoneHasWaifu
Well, you can also just load up ubiboot without flashing it, by pushing it to device with flasher.
This is where my problem comes up. The "N9 Tour".
The "begin the tour" button is exactly on the area of the screen that is not responsive.
I remember there being a dotfile in ~/MyDocs which had information stored whether the user has gone through the tour or not. I tried to mount the filesystem onto my machine but that ended with no success.
If there is any way to access the device's root filesystem I could probably figure out how to remove the tour application in the first place.
If anyone has any ideas or suggestions on how to fix my problem, please respond. Thank you.
When it boots up you get the filesystem exports and capability to telnet to the device.
| The Following 2 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2014-10-10
, 19:49
|
|
Posts: 291 |
Thanked: 435 times |
Joined on Apr 2011
@ RO
|
#3
|
drop your n9 in the ocean and by an n900 until u wil have a second hand neo900
|
|
2014-10-11
, 09:25
|
|
Posts: 16 |
Thanked: 5 times |
Joined on Mar 2013
|
#4
|
Originally Posted by juiceme
Thank you very much. I've managed to mount the filesystems.
It used to be so in older versions of ubiboot so that if the device was powered off and inserted to a wall charger, it went to repair mode instead of charging mode.
This was corrected in version 0.3.0 however, so if you have this problem you either have too old ubiboot or the configuration is wrong.
(There is a configurable parameter to enable/disable this feature...)
Well, you can also just load up ubiboot without flashing it, by pushing it to device with flasher.
When it boots up you get the filesystem exports and capability to telnet to the device.
However, there is one last thing I need to ask.
I haven't found the dotfile so far in ~/MyDocs (or ~/), so I can only assume it's created only after the tour is finished. If you could, I would appreciate you finding such a file in your own device, and telling me what it is called, and what are the contents of it.
Thank you, again.
Last edited by MyPhoneHasWaifu; 2014-10-11 at 09:36.
| The Following User Says Thank You to MyPhoneHasWaifu For This Useful Post: | ||
This is where my problem comes up. The "N9 Tour".
The "begin the tour" button is exactly on the area of the screen that is not responsive.
I remember there being a dotfile in ~/MyDocs which had information stored whether the user has gone through the tour or not. I tried to mount the filesystem onto my machine but that ended with no success.
If there is any way to access the device's root filesystem I could probably figure out how to remove the tour application in the first place.
If anyone has any ideas or suggestions on how to fix my problem, please respond. Thank you.