[2.1] all custom builds after Mar 8, will fail to start - core.js script to big

[GoogleCodeExporter]

Your model / PRS+ version?
PRS-650 / Nightly R.039

What steps will reproduce the problem?
1. Following Wiki instructions, make a 
http://code.google.com/p/prs-plus/source/detail?r=3d47d5dcec0de8f3afb2fad79c3de6
04ff35282e (R.039) build.
2. Install it.
3. Look at your PRS. You get Sony software with some PRS+ touches. But PRS+ 
itself is missing (no More menu, no PRS+ Settings, ...)
4. I've reverted to R036 (installing 2.0.18 through exe and then R036). (My 
guess: issue introduced in R037 or R038?)

Original issue reported on code.google.com by alr...@gmail.com on 12 Mar 2012 at 9:14

[GoogleCodeExporter]

Thanks for reporting, but on Ben's 650 (600?) and my 505 & 650 it's up and 
running. (R38/ Rev bf3212f3effe for me)

If you can spare the time please:
create a folder /Beta/ in the root of IM
putting in a file  "user.config" (template is user.config.650)

with just this two (4 with comments) lines in user.config
// what to log and what not, possible values are: all, trace, info, warn, error
config.defaultLogLevel = "trace";
// where to log
config.logFile = "/Data/prsp_script.log

and post prsp_script.log

To get rid of a FUBAR version you can always:
1) reset the reader or shut it down
2) start it up connected to USB
3) remove runonce.sh if present
4) put on PRSPInstaller - Folder of a known good build
5) disconnect -> you will be in "Safe-Mode" = standard Sony UI without PRS+
6) shut-down (Settings - shutdown)
7) restart w/o USB connected 

Original comment by Mark.N...@gentlemansclub.de on 13 Mar 2012 at 7:36

[GoogleCodeExporter]

also reported be TJ27 for a 350 over at MR
http://www.mobileread.com/forums/showpost.php?p=2002251&postcount=3533

Original comment by Mark.N...@gentlemansclub.de on 13 Mar 2012 at 10:16

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Here you go. Build R038 (not 039)

Failed to load core Too big script!
core file was /opt/sony/ebook/application/resources/prsp/core.js
error in localize invalid type
Failed to load addons invalid type
Failed to load addons1 invalid type
Failed to load addons2 invalid type
Failed to load addons3 invalid type
in overriden readPreference invalid type

Original comment by alr...@gmail.com on 13 Mar 2012 at 3:22

[GoogleCodeExporter]

Thx,
to quote kartu (over at MR)
Quote:
  Failed to load core Too big script!
  core file was /opt/sony/ebook/application/resources/prsp/core.js
  So even compressed file fails to load. 
/Quote

As temporary work around you can remove core_zabout.js from /core/

Original comment by Mark.N...@gentlemansclub.de on 13 Mar 2012 at 3:43

[GoogleCodeExporter]

As Mark said, PRS+ works fine on my 650.  (I haven't installed it on my 600 
yet.)  Does anyone know why the core is too big on some readers and not others? 
 Granted, I use a personal build but I wouldn't think I'd changed anything in 
core...

Original comment by ben.chen...@gmail.com on 13 Mar 2012 at 4:14

[GoogleCodeExporter]

I have only customized lang.ods and Spanish assets.xml. Can it be related? 
(Although both files produce a perfect build with R036).

(Don't worry about workarounds. I'll stick to R036 till it's solved).

Original comment by alr...@gmail.com on 13 Mar 2012 at 4:49

[GoogleCodeExporter]

@Ben,

to be honest I have /Beta/ in IM for the 650 and on SD-Card for the 505, both 
without core_zabout.js. This might be the reason for my "working" builds.

Original comment by Mark.N...@gentlemansclub.de on 13 Mar 2012 at 8:26

[GoogleCodeExporter]

Latest version build from git https://prs-plus.googlecode.com/hg/ neither don't 
work from my 505

Original comment by surkizu@gmail.com on 14 Mar 2012 at 1:17

[GoogleCodeExporter]

@Mark,

I remembered that I have actually modified core_zabout.js (I deleted all the 
lines about translations / translators).  So that would explain why mine works.

Is there some way perhaps to change core_zabout.js into an addon?

Sincerely,
Ben.

Original comment by ben.chen...@gmail.com on 14 Mar 2012 at 4:12

[GoogleCodeExporter]

Issue 324 has been merged into this issue.

Original comment by Mark.N...@gentlemansclub.de on 14 Mar 2012 at 7:17

[GoogleCodeExporter]

Original comment by Mark.N...@gentlemansclub.de on 14 Mar 2012 at 7:19

• Changed title: [2.1] all custom builds after Mar 8, will fail to start - core.js script to big

[GoogleCodeExporter]

@ Ben,
as "core" is kartus work, and he knows best about the internal organisation, it 
will be up to him to lead the way.

But as core_ui_menu and core_key_bindings are initialized like addons, e.g. 
they call core.addAddon(), it should be save to move them to a addon-folder

Original comment by Mark.N...@gentlemansclub.de on 14 Mar 2012 at 7:45

[GoogleCodeExporter]

@Mark,
That makes sense.  And both of those are "big" so the space saving would be 
significant.

Original comment by ben.chen...@gmail.com on 14 Mar 2012 at 7:53

[GoogleCodeExporter]

Hi,
I was successfully able to shift following core-files to "/core1" on my 
650-beta-pack
core__popup.js
core_archiver.js
core_convert.js
core_key_bindings.js
core_zAbout.js
while calling core1 like addons form prsp.js

But when moving "core_ui_menu.js" I will get:
  error when calling method onInit on MenuCustomizer: invalid type

But anyway, above would free up enough space to go on.

@kartu: should this be pushed to the default repository?

Original comment by Mark.N...@gentlemansclub.de on 14 Mar 2012 at 7:57

[GoogleCodeExporter]

Hi Mark,

yes please. Thanks a lot for the effort!

Original comment by msukhias...@gmail.com on 16 Mar 2012 at 7:46

[GoogleCodeExporter]

Done with rev: 7a1556bcb169
Tested with 650 and 505

Original comment by Mark.N...@gentlemansclub.de on 17 Mar 2012 at 7:19

• Changed state: Fixed