Opera Mobile 9.51 beta 2 into custom ROM

[Guest klicker4546]

Hi,

does anybody know whether it's possible to integrate OM 9.51 beta 2 into a custom ROM? I've spent many hours without success. The browser seems to start, but crashes after a few seconds.

I'd be grateful for any help.

Thanks,

klicker4546

Edited November 26, 2008 by klicker4546

[Guest kafer]

does anybody know whether it's possible to integrate OM 9.51 beta 2 into a custom ROM?

what for? imho it would be better to remove opera from the ROM to make other people choose whether to install 9.51b2 or another verion

[Guest klicker4546]

You ask what for? I'd say for browsing the web. B)

Seriously, It's just that I don't like the version which is shipped with the official ROM-builds. My impression is that the newer build works better. I think it's not that hard to remove Opera out of the ROM, but as it seems it's pretty hard to integrate the build I mentioned. But it's actually a good idea to totally remove it totally and try to install the OM 9.51b2 afterwards. Maybe that'll work.

what for? imho it would be better to remove opera from the ROM to make other people choose whether to install 9.51b2 or another verion

[Guest somedude]

imo the version that comes shipped with the roms is way better than the crappy beta.

the beta gives you that small default keyboard every time you need to type something and that drives me insane!

[Guest klicker4546]

I'm a little confused now. What small default keyboard? The one which comes from Windows Mobile itself? Or do you mean the standard Samsung keyboard?

If you mean the WM 6.1 default keyboard, I never experienced the problem you're describing here with OM 9.51b2. It works fine for me otherwise I wouldn't want to integrate it into a custom ROM.

Therefore my question is 'how-to-integrate-it' and not rather 'why-to-integrate-it'. B)

imo the version that comes shipped with the roms is way better than the crappy beta.

the beta gives you that small default keyboard every time you need to type something and that drives me insane!

[Guest iTnkD4iAm]

How are you integrating the opera related files to your custom ROM? Copying them all to the \windows or following the file structure described in the installer?

[Guest black-DraGon]

dudes, he dont integrate nothing!!! he just wants to know how to integrate opera beta in a new rom!!!

it couldnt be possible that no one knows that... so comeon and help him!

[Guest lastnikita]

the hard part should be to remove properly the built-in opera

to cook the new beta in, it should just be as any other cab->package

[Guest iTnkD4iAm]

dudes, he dont integrate nothing!!! he just wants to know how to integrate opera beta in a new rom!!!

it couldnt be possible that no one knows that... so comeon and help him!

He said he already tried it for hours so I'm assuming he already integrated it unsuccessfully. As to "how" he integrated it is the question which could help in identifying the problem he's facing.

[Guest black-DraGon]

you are right iTnkD4iAm but he cant build it right so he is just on the start point and needs to know how to... ^^

the hard part should be to remove properly the built-in opera

to cook the new beta in, it should just be as any other cab->package

it is really hard to do that... i want to do that too but i almost failed and some bugs appeard... so i dont try it longer... PaSSaO said that flas3.1 almost work with the build in opera... but i dont know how... he dont answer to that question so i dont try to install it...

[Guest klicker4546]

Hi guys,

that's exactly the probly I'm experiencing. I've already tried to integrate it, unsuccessfully so far. I removed related files and also some entries in a rgu-file and initflash.dat related to the version of Opera Mobile which is shipped with the official ROMs by Samsung. Then I used a tool named 'cab2oem' in order to create an OEM package. I placed this package in the folder OEM and created a custom ROM. After flashing the ROM to my Omnia I've started the browser. The splash screen shows up for a few seconds and next to the Start-button somtimes appears 'Opera Mobile' before the application is crashing and closing silently.

So, I'm eager to find a solution for this issue. Maybe there's anything that I've forgotten to edit or something is missing or needs further editing. If anybody has a hint that would be gorgeous.

It might be that my question was not clear enough, if so, I'm sorry.

He said he already tried it for hours so I'm assuming he already integrated it unsuccessfully. As to "how" he integrated it is the question which could help in identifying the problem he's facing.

[Guest iTnkD4iAm]

Hi guys,

that's exactly the probly I'm experiencing. I've already tried to integrate it, unsuccessfully so far. I removed related files and also some entries in a rgu-file and initflash.dat related to the version of Opera Mobile which is shipped with the official ROMs by Samsung. Then I used a tool named 'cab2oem' in order to create an OEM package. I placed this package in the folder OEM and created a custom ROM. After flashing the ROM to my Omnia I've started the browser. The splash screen shows up for a few seconds and next to the Start-button somtimes appears 'Opera Mobile' before the application is crashing and closing silently.

So, I'm eager to find a solution for this issue. Maybe there's anything that I've forgotten to edit or something is missing or needs further editing. If anybody has a hint that would be gorgeous.

It might be that my question was not clear enough, if so, I'm sorry.

I'm not familiar with cab2oem but you should check the initflashfiles.txt and the registry files that's created for opera. And I'm not sure if the opera downloaded from opera.com can run from \windows like the one that came w/ samsung so check if the proper directory structures are created and the files are copied accordingly (ie. \program files\opera 9.5 beta, \application data\opera 9.5 beta, etc) As for the registry, you may want to copy the entries that came from the samsung opera (opening HTML files and setting download agents) except for HKLM\Software\Opera\Info

[Guest klicker4546]

Great, that's what I gonna do. Thanks a lot! Problem regarding path settings could be that I was using a German ROM, where you have slightly different names, e. g. Programme\Opera 9.5 Beta. Application Data\Opera 9.5 Beta is the same though.

The bad factor now is only time, as there is not that much of it for me right now. B) But I'll give it a try. Maybe the best to modify an English ROM. B)

Thanks for your help!!! I'll let you know whether I can fix it.

I'm not familiar with cab2oem but you should check the initflashfiles.txt and the registry files that's created for opera. And I'm not sure if the opera downloaded from opera.com can run from \windows like the one that came w/ samsung so check if the proper directory structures are created and the files are copied accordingly (ie. \program files\opera 9.5 beta, \application data\opera 9.5 beta, etc) As for the registry, you may want to copy the entries that came from the samsung opera (opening HTML files and setting download agents) except for HKLM\Software\Opera\Info

[Guest klicker4546]

I've tried it now and there's still no success. That's why I'll give up for now as it is a matter of time.

Great, that's what I gonna do. Thanks a lot! Problem regarding path settings could be that I was using a German ROM, where you have slightly different names, e. g. Programme\Opera 9.5 Beta. Application Data\Opera 9.5 Beta is the same though.

The bad factor now is only time, as there is not that much of it for me right now. B) But I'll give it a try. Maybe the best to modify an English ROM. B)

Thanks for your help!!! I'll let you know whether I can fix it.