Active Topics

 


Reply
Thread Tools
Posts: 41 | Thanked: 6 times | Joined on Apr 2008
#301
Originally Posted by Underscore View Post
Mine was automatically set at 1024 (no settings restored). You're right, though. It used to be almost instantaneous, but now it takes a few seconds. It does load faster than the first time going to the page, though.
I think it's done that way to save memory in general. I know in Firefox 2, it would use up to x amount of memory for the old pages.

However, our tablets have very limited ram so it would be smart not to cache the last pages [in memory] as much or at all.
 
Posts: 41 | Thanked: 6 times | Joined on Apr 2008
#302
Originally Posted by mytimes View Post
Scythe ! you are awesome ....the instructions you gave "works" , now I am on Diablo !

Thank you very much !
You're very welcome

Glad I could help you out
 
Posts: 609 | Thanked: 232 times | Joined on Dec 2007 @ the end of my rope
#303
Originally Posted by Scythe View Post
However, our tablets have very limited ram so it would be smart not to cache the last pages [in memory] as much or at all.
Can we adjust some setting in order to see allowing a cached last page
affects the stability of the browser?
 
Posts: 41 | Thanked: 6 times | Joined on Apr 2008
#304
Originally Posted by lm2 View Post
Can we adjust some setting in order to see allowing a cached last page
affects the stability of the browser?
I don't know the preference off the top of my head, but I do know it's in about:config (I've had to speed up low-memory linux terminal's running only ffx)

Look up memory fixes for Firefox 2 on google, and there should be some property keys people change in the about:config to cache more or less.
 

The Following User Says Thank You to Scythe For This Useful Post:
Posts: 48 | Thanked: 3 times | Joined on Apr 2008
#305
Originally Posted by lm2 View Post
After a new flash to diablo, you'll have to update your kernel. But you won't have to update it again after you use PB's diablo-friendly install-tools deb to clone diablo to sd. But you will have to reinstall xomap, xrandr, and the automatic install, as the install-tools deb seems to remove these. See here for more.
Oh Ok. I assume the updated kernel is on Fanoush's page? Or is it the same kernel that I was already using for chinook?
Thanks again.
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#306
Originally Posted by mytimes View Post
Version of 'sw-release': <no version>
This looks suspicious, it should normally report the version of the previous firmware. Perhaps some of the earlier tries damaged something... Don't worry though, as long as your bootloader works (and obviously it does) you should be able to get the device running again.

I would suggest flashing it with a previous version to fix this (it should work, as the initfs will fit your current initfs mtd partition), and then trying again with the diablo image.
 
Posts: 609 | Thanked: 232 times | Joined on Dec 2007 @ the end of my rope
#307
Originally Posted by supergadgetman View Post
Oh Ok. I assume the updated kernel is on Fanoush's page? Or is it the same kernel that I was already using for chinook?
Thanks again.
Yes. Links to Kernel, as well as instructions for implementing rotation, can be found here. Read this also, before starting.
 
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#308
For anybody wondering about the flash-and-reboot, kernel-diablo-flasher and initfs flasher dependencies. This message from Marius Vollmer on -users explains it rather nicely.
The osso-software-version-rx44 package exists twice: once in your device
and once in the "Nokia System Software Updates" repository. These two
instances of the package have the same version, but different
dependencies (stupid, I know, see below). The
osso-software-version-rx44 in the repository additionally depends on the
three packages that you list in the subject.

Apt-get uses the information from the repository, which results in the
error message you see. Running apt-get -f install will fix it. The
Application manager is not affected by this, it simply ignores the
problem and carries on. After the first OS update, the problem goes
away.

It's a bug of course that the two instances of
osso-software-version-rx44 are not identical. The additional
dependencies in the repository instance are used to (as you might have
guessed to control flashing of the kernel and initfs during a OS
update. The osso-software-version-rx44 instance in the flash image does
not need them, and I didn't see the problem with this because I wasn't
thinking. (I don't reflash my devices anymore, so I didn't run into
this problem myself...)

Yep, it's a bit embarassing, but should have no bad consequences other
than having to run "apt-get -f install" once (or disabling the "Nokia
System Software Updates" repository) before you can use apt-get on the
command line.
 

The Following 8 Users Say Thank You to GeneralAntilles For This Useful Post:
Posts: 186 | Thanked: 56 times | Joined on Mar 2008
#309
Random observation: OMG Songza.com is usable now!
Before, the browser hung up terribly with its transparent menus. Completely smooth now
 
fpp's Avatar
Posts: 2,853 | Thanked: 968 times | Joined on Nov 2005
#310
Originally Posted by joepagiii View Post
at the rate this is going...you'll be overwhelmed....
I already am, as you can tell from this reply being on page 31...

On the bright side, you just can't be over-overwhelmed, now, can you ? :-)
 
Reply


 
Forum Jump


All times are GMT. The time now is 17:27.