209 replies to this topic

[VOODOOS!L]

is there some way to make the Work/home switch button usefull? I would prefer not using some extra loaded application like AEButton. Can we put some exe file with some specific name in the windows dir that will be executed by this button?

[daskalos]

RainerRabe2, on Mar 15 2010, 10:29, said:

so, after some hours, it is working well, some observations/questions:
1. the chainfire x-button fix does not work, i.e. applications do not close - maybe I am doing something wrong (just installed the cab and rebooted)

2. the "alarmwatcher" exe seems missing, even if I reinstall tclock from the CAB - so no alarm sounds AND (!!!) the device does not boot automatically if an alarm is set - which is a cool power saving feature of the SAMSUNG, any chance to get that also in a cab..?

3. THINGS TO DO AFTER INSTALLING THIS ROM
1. Install .NET Framework 3.5 (Cause there's no .NET CF installed) - why? do not need that?
2. Install Samsung SDK STD 2.2 - Why? do not need that?
3. Install Auto Close patch - where is that, did not find in the list of cabs/patches
4. Enable X button to close apps - done
5. Install Adobe Flash 3.1 - why? alternative to google youtube app?
6. Chainfire Autoclose Fix - see point 1, did install but did not work...made the whole thing slower somehow, I think

4. same in all ROMS, not sure what is the problem: when running TOMTOM 7.91x, and you open contacts while it is in the background, you see no contacts.

txs for your feedback, folks!

1. Just a clarification, Chainfire autoclose patch does not closes programs by x-button. What it does is disable auto closing of programs when memory reaches 30mb
2. Seems the cab needs to be repacked.

Other concerns

1. .Net Framework- it is needed by some applications, OEM or third party
2. Samsung SDK- needed by auto rotate and some applications only made for i8000
3. It's there
4. Well it doesn't work in 6.5.5
5. Because adobe flash is removed from the ROM
6. It's slower because you must have menu applications running in the background, close them completely with task manager

[RainerRabe2]

daskalos, on Mar 15 2010, 10:26, said:

1. Just a clarification, Chainfire autoclose patch does not closes programs by x-button. What it does is disable auto closing of programs when memory reaches 30mb
2. Seems the cab needs to be repacked.

Other concerns

1. .Net Framework- it is needed by some applications, OEM or third party
2. Samsung SDK- needed by auto rotate and some applications only made for i8000
3. It's there
4. Well it doesn't work in 6.5.5
5. Because adobe flash is removed from the ROM
6. It's slower because you must have menu applications running in the background, close them completely with task manager

thanks for the quick clarification, obviously I had mixed some things up...

[vjin]

KLmun started another topic, but ill post it in this one anyways...

He was right about the sleeping beuaty problem.
I just tried to reboot mine but it got stuck at windows phone wallpaper.
its the first time in a whole day of rebooting so i dont really mind, but i thought id let you all know

oh and daskalos thnx for the answer on the xbutton issue...but my question was how to remove battery icon from taskbar

[VOODOOS!L]

strange, I have more free memory with this 6.5.5 Megalite than the rom I used before (6.5.3) but I have the feeling it is much slower now. Like when using TomTom or opening the startmenu I notice some delay that I didn't had before. Maybe some drivers?
I have installed all basic stuff of the first page (no apps from batch 2).
Anyone else has the same feeling?

[daskalos]

VOODOOS!L, on Mar 15 2010, 13:32, said:

strange, I have more free memory with this 6.5.5 Megalite than the rom I used before (6.5.3) but I have the feeling it is much slower now. Like when using TomTom or opening the startmenu I notice some delay that I didn't had before. Maybe some drivers?
I have installed all basic stuff of the first page (no apps from batch 2).
Anyone else has the same feeling?

Maybe its a pagepool thing...i could adjust the rom to have more pagepool but it will lessen the free available ram (as before)

or

Tomtom is not really compatible with 6.5.5 build...

-------------------------------------------------------------------------

If you don't want AEButton, you can try MortScript and use scripts that will act as shortcut to an application (Mortscript runs discreetly and doesn't eat RAM/processes much)

--------------------------------------------------------------------------------------------------------------------------

About the not waking up thing... I really can't say a solution cause I haven't experience it till now...

Well there are some few factors that can be the cause:

1. The amount of RAM
     Since the Xbutton doesn't work on the 6.5.5 build, when we tap x on applications, it is really not terminated, just minimized. Unnoticeable, an accumulation of apps might be running and discreetly using RAM and processes, which can have complications on waking up the device.

2. Samsung SDK 2.2
      Well it is known that samsung SDK 2.2 causes sleeping beauty, so you can try uninstalling it and monitor your device. Or try installing it in Device, not on My Storage or Memory Card.

3. The 10Mb temp file fix
       I put a dummy .tmp file in \windows so that the 10mb sized .tmp file doesn't generate. You can delete _memmap_.tmp in \Windows and monitor device.

4. The Lock
       Some suggested that enabling the classic Windows lock causes waking up problems. Try enabling WM 6.5 slide lock and monitor the device.

6. The different versions of our Phone and CSC.
        Since most of us only flash the PDA part, we end up with the same ROM version but different CSC's, Phone and eBoot versions. I'm not really sure if our device will be stable teamed up with a different CSC's etc. But this is what I'm sure of; there is surely a reason why our original PDA part is teamed up with a particular CSC,phone and eboot version. Mixing them up is like ingredients for a salad, you might end up with a great tasting dish or end up throwing your plate.

5.  Some third party apps
         Well is you are a long time WinMo user, you perhaps know what am I talking about.

6. This is a BETA build
          All new builds available out there that does NOT come right out from the box (I mean when you bought a brand new WinMo device) is always a BETA.
Beta which means it is still an experimental working build. Build 6.5.5 23545 is not an exception, so there might be some issues affecting it.

Well the above are just theories. I really can't be sure since I'm using the ROM and isn't facing the sleeping problem anymore. Since this incident happens very, very randomly now (unlike before which the "sleeping beauty" problem happens almost as early as 5mins of sleeping to all who flashed that version) and only 2 people reported about this out of 86 who downloaded version 1 and 87 who downloaded version 2 (as of this time) , the root cause might not be the ROM itself, and may not be very alarming.

Well good luck, I apologize I might don't really have all the answers to all your questions. But I'll try my best to help concerns

Edited by daskalos, 15 March 2010 - 02:07 PM.

[fier03]

is there some way to make NPS recognize the phone??

cause it says "unknown model connected"

[vjin]

daskalos, on Mar 15 2010, 14:21, said:

Maybe its a pagepool thing...i could adjust the rom to have more pagepool but it will lessen the free available ram (as before)

or

Tomtom is not really compatible with 6.5.5 build...

-------------------------------------------------------------------------

If you don't want AEButton, you can try MortScript and use scripts that will act as shortcut to an application (Mortscript runs discreetly and doesn't eat RAM/processes much)

--------------------------------------------------------------------------------------------------------------------------

About the not waking up thing... I really can't say a solution cause I haven't experience it till now...

Well there are some few factors that can be the cause:

1. The amount of RAM
     Since the Xbutton doesn't work on the 6.5.5 build, when we tap x on applications, it is really not terminated, just minimized. Unnoticeable, an accumulation of apps might be running and discreetly using RAM and processes, which can have complications on waking up the device.

2. Samsung SDK 2.2
      Well it is known that samsung SDK 2.2 causes sleeping beauty, so you can try uninstalling it and monitor your device. Or try installing it in Device, not on My Storage or Memory Card.

3. The 10Mb temp file fix
       I put a dummy .tmp file in \windows so that the 10mb sized .tmp file doesn't generate. You can delete _memmap_.tmp in \Windows and monitor device.

4. The Lock
       Some suggested that enabling the classic Windows lock causes waking up problems. Try enabling WM 6.5 slide lock and monitor the device.

6. The different versions of our Phone and CSC.
        Since most of us only flash the PDA part, we end up with the same ROM version but different CSC's, Phone and eBoot versions. I'm not really sure if our device will be stable teamed up with a different CSC's etc. But this is what I'm sure of; there is surely a reason why our original PDA part is teamed up with a particular CSC,phone and eboot version. Mixing them up is like ingredients for a salad, you might end up with a great tasting dish or end up throwing your plate.

5.  Some third party apps
         Well is you are a long time WinMo user, you perhaps know what am I talking about.

6. This is a BETA build
          All new builds available out there that does NOT come right out from the box (I mean when you bought a brand new WinMo device) is always a BETA.
Beta which means it is still an experimental working build. Build 6.5.5 23545 is not an exception, so there might be some issues affecting it.

Well the above are just theories. I really can't be sure since I'm using the ROM and isn't facing the sleeping problem anymore. Since this incident happens very, very randomly now (unlike before which the "sleeping beauty" problem happens almost as early as 5mins of sleeping to all who flashed that version) and only 2 people reported about this out of 86 who downloaded version 1 and 87 who downloaded version 2 (as of this time) , the root cause might not be the ROM itself, and may not be very alarming.

Well good luck, I apologize I might don't really have all the answers to all your questions. But I'll try my best to help concerns

no needs for apologies whatsoever!! youre doing a great job and youre doing it for free  
really appreciate your input  
can i ask what csc pda and phone you are using?

[JaW-PL]

Streaming Player still not working... (ROM V2).

[daskalos]

JaW-PL, on Mar 15 2010, 21:44, said:

Streaming Player still not working... (ROM V2).

New  working Streaming Player installation cab posted in the first post...

----------------------------------------------------------------------------------------------

I'm using

CSC B7610NXTCIL3
Phone b7610xxik1

Edited by daskalos, 16 March 2010 - 03:16 AM.

[JaW-PL]

daskalos, on Mar 16 2010, 04:15, said:

New  working Streaming Player installation cab posted in the first post...

Yes, now working.
Big thx

[Freezy1982]

Question: How much work will it be, to create this ROM in multilanguage? I think some others would prefer using their own language as well..

Your ROM seems to be the best for now - awesome free RAM and stable

Thanks for your restless work!  

[CJMonty]

daskalos, on Mar 15 2010, 14:21, said:

4. The Lock
       Some suggested that enabling the classic Windows lock causes waking up problems. Try enabling WM 6.5 slide lock and monitor the device.

Please, can you tell me how to do this? I like more the 6.5 slider lock and I don't want to install some 3rd party procuct for this.

And one more thing when I'm making a call proximity sensor turns off display, but when I want to end call, display turns on but phone is locked. It's not a big deal, but it's a little annoing.

Thanks for help and for this great ROM.

[daskalos]

CJMonty, on Mar 16 2010, 13:07, said:

Please, can you tell me how to do this? I like more the 6.5 slider lock and I don't want to install some 3rd party procuct for this.

And one more thing when I'm making a call proximity sensor turns off display, but when I want to end call, display turns on but phone is locked. It's not a big deal, but it's a little annoing.

Thanks for help and for this great ROM.

just install this http://www.4shared.c...5_Lock_Scr.html
wait a few seconds and soft reset

[new2city]

CJMonty, on Mar 16 2010, 20:07, said:

Please, can you tell me how to do this? I like more the 6.5 slider lock and I don't want to install some 3rd party procuct for this.

And one more thing when I'm making a call proximity sensor turns off display, but when I want to end call, display turns on but phone is locked. It's not a big deal, but it's a little annoing.

Thanks for help and for this great ROM.

I can't seem to find the registry keys anymore to enable the 6.5 slider lock, so just try this from AC  
http://acs2.mstreme....5DeviceLock.cab,

hah, just shows how screwy my internet connection is.. 6 minutes difference and I still didn't see Daskalos' post until I posted my solution..


Finallly, I found the registry key to revert back to 6.5 lockscreen..  for those who hate cab files but like registry settings..

HLKM\Software\Microsoft\Shell\LockScreen\Enable  
Enable = 1 will restore the Win6.5 lockscreen
Enable = 0 will restore the Classic lockscreen

surprisingly, no soft reset required...

Edited by new2city, 16 March 2010 - 01:49 PM.

[CJMonty]

new2city, on Mar 16 2010, 13:51, said:

I can't seem to find the registry keys anymore to enable the 6.5 slider lock, so just try this from AC  
http://acs2.mstreme....5DeviceLock.cab,

hah, just shows how screwy my internet connection is.. 6 minutes difference and I still didn't see Daskalos' post until I posted my solution..
Finallly, I found the registry key to revert back to 6.5 lockscreen..  for those who hate cab files but like registry settings..

HLKM\Software\Microsoft\Shell\LockScreen\Enable  
Enable = 1 will restore the Win6.5 lockscreen
Enable = 0 will restore the Classic lockscreen

surprisingly, no soft reset required...

Thanks a lot!!! This registry solution works perfect.

@ Daskalos: Thanks but your .cab file didn't work. I tried to reinstall it but still no effect. May be I'm doing something wrong... Or maybe it could cause that I didn't install Samsung SDk 2.2 because of sleeping problems which I encounter when it was installed. Also in V2 ROM.

[daskalos]

oh...  I tested the cab...you don't have to soft reset

So Samsung SDK is really the culprit....

[RainerRabe2]

still working great after some days. curious for your new build !!  

question: did anyone in the meantime manage to create an "alarmwatcher.cab" ? otherwise tclock is quite useless...

txs!

[jero1ste]

@daskalos;
Thx, for this great rom!
Is it possible to cook a multilanguage rom?

[daskalos]

jero1ste, on Mar 17 2010, 06:28, said:

@daskalos;
Thx, for this great rom!
Is it possible to cook a multilanguage rom?

At this point of time, making a multilanguage ROM, is impossible. A more practical way is dumping your ROM with your language, disassemble it, replaced some language files and build it again.

For some thorough explanation, read about cooking multilanguage ROM by wes58 below:

Quote

You can't make a multilanguage ROM. You would have to build a samsung .mst file which we can't do. This file has a basic rom (without language files) and language pack with files for different languages. As you know, when you flash mst file it is stored on a hidden partition on 'My Storage'. When you change the language, samsung software creates an rom image out of a 'basic rom' and a selected language files and it is flashed to the phone ROM (R-ead O-nly M-emory).
You can make roms for different languages but they will be separate roms (.nb0 file). You have to replace for example english files (0409) with other language files.