Related
As the thread title.
Can we, polaris user, make the opera 9.5 zoom in and out by the "wheel" just like diamond?
It we can, that would be nice~
Thanks~
i'm interested too !
i tried to modify the input.ini, and changed up and down key to zoom in and zoom out, but no effects....
anybody can post input.ini found on diamond ?
titus07 said:
anybody can post input.ini found on diamond ?
Click to expand...
Click to collapse
Voilà.......
So does that allow us to use the wheel for zooming?
hambola said:
So does that allow us to use the wheel for zooming?
Click to expand...
Click to collapse
No I think it needs some editing first!
a thought....
Hi!
I have just installed the Opera 9.x and my Cruise as you know comes with a older version. My question is how can i redirect all opera or even better ALL browser calls to my new Opera 9?
ToddeSwe
L10nH34Rt said:
No I think it needs some editing first!
Click to expand...
Click to collapse
Yeah I figured that much. Let me re-phrase, have you been able to modify the file to allow it to zoom with the wheel. I see the references to the zoom in there but haven't tried playing with it.
udK said:
Voilà.......
Click to expand...
Click to collapse
thank you
it seems that the wheel send + or -, on the cruise it sends up and down
i'll try to modify the file, and y say you what !
May be you succeed...Pl let us know..
So, what can we do to the input to make it work?
Can anyone help?
Thanks~
titus07 said:
I'll try to modify the file, and y say you what !
Click to expand...
Click to collapse
Did you succeed ? Let us know !
no more success with version 9.5 build 1409
i put
[Browser Widget]
Down = Zoom out, 10
Up = Zoom in, 10
it works but the display is not refreshed and all characters are not redrawed->big pixels
O thanks, then let me try in the previous build~
Thanks~
titus07 said:
no more success with version 9.5 build 1409
i put
[Browser Widget]
Down = Zoom out, 10
Up = Zoom in, 10
it works but the display is not refreshed and all characters are not redrawed->big pixels
Click to expand...
Click to collapse
I've tried this in several different builds, and sadly, had the same results...
Looking at the Diamond original file, it seems that those commands should be in the [Application] section, but it is ignored...
Any new info on this? I tried messing around with input.ini, but no luck... any fresh ideas?
Hi Guys,
I cooked a WM6.5.5 ROM build 23541 based on RUU_Rhodium_S2_HTC_Europe_2.07.401.1
Most of things currently works perfectly, with the exception to the incoming call screen position. This is a small gap from the top which looks not very good.
I tried to apply fixes ex. here: http://forum.xda-developers.com/showthread.php?p=5910397#post5910397
This solved for me the scroll bar and the softpad overlap issues but the incoming call screen is still wrongly positioned.
Could anybody help me in solving this issue?
Thank you in advance and best regards!
Lissek said:
Hi Guys,
I cooked a WM6.5.5 ROM build 23541 based on RUU_Rhodium_S2_HTC_Europe_2.07.401.1
Most of things currently works perfectly, with the exception to the incoming call screen position. This is a small gap from the top which looks not very good.
I tried to apply fixes ex. here: http://forum.xda-developers.com/showthread.php?p=5910397#post5910397
This solved for me the scroll bar and the softpad overlap issues but the incoming call screen is still wrongly positioned.
Could anybody help me in solving this issue?
Thank you in advance and best regards!
Click to expand...
Click to collapse
You should replace
cprog.exe
pimstore.dll
tpcutil.dll
from 235xx builds.
Pre-tested on 28232, 23106, 21636
At 23106 and 21636 should be replaced and lockscreen.dll
b16b said:
You should replace
cprog.exe
pimstore.dll
tpcutil.dll
from 235xx builds.
Pre-tested on 28232, 23106, 21636
At 23106 and 21636 should be replaced and lockscreen.dll
Click to expand...
Click to collapse
he said he was cooking 23541, why should he replace those dll files to fix position of incoming call screen? i assume the "fix" you are telling him to do is for the caller id problem with 231xx, 216xx, ect. but that isnt what he was asking.
as for helping you Lissek, sorry but i dont know a solution and as far as i know nobody has figured it out yet. you can try opening phcanrc.dll and some of the other dlls in the phone canvas pkg with a resource editor like restorator, this is how the scrollbar on dialpad was fixed...maybe there is something that can be done im just not sure.
twopumpchump said:
he said he was cooking 23541, why should he replace those dll files to fix position of incoming call screen? i assume the "fix" you are telling him to do is for the caller id problem with 231xx, 216xx, ect. but that isnt what he was asking.
as for helping you Lissek, sorry but i dont know a solution and as far as i know nobody has figured it out yet. you can try opening phcanrc.dll and some of the other dlls in the phone canvas pkg with a resource editor like restorator, this is how the scrollbar on dialpad was fixed...maybe there is something that can be done im just not sure.
Click to expand...
Click to collapse
yes you are right
i just read it fast..
do you have fix for 6.5.x and landscape incoming call?
First of all thank you guys for your help!
twopumpchump, I flashed your ROM and I see that you don't have a problem with incoming call screen position in your ROM. This is positioned perfectly well.
Mine is positioned a little bit too low and I simply see the fragment of the screen with the operator name in that gap.
I have that problem only on incoming call screen, dialer is positioned ok.
I tried to compare dialogs from phcanrc.dll you use with the one with my ROM and I see no difference.
Have you ever observed that in your ROMs?
Might it be related to the kitchen I use? I don't think so, but.. when I use osKitchen my ROM boots ok, but when I use EVK my ROM hangs on the first use screen once the progress bar reaches the end.
Lissek said:
First of all thank you guys for your help!
twopumpchump, I flashed your ROM and I see that you don't have a problem with incoming call screen position in your ROM. This is positioned perfectly well.
Mine is positioned a little bit too low and I simply see the fragment of the screen with the operator name in that gap.
I have that problem only on incoming call screen, dialer is positioned ok.
I tried to compare dialogs from phcanrc.dll you use with the one with my ROM and I see no difference.
Have you ever observed that in your ROMs?
Might it be related to the kitchen I use? I don't think so, but.. when I use osKitchen my ROM boots ok, but when I use EVK my ROM hangs on the first use screen once the progress bar reaches the end.
Click to expand...
Click to collapse
you are using fix from alex this package:
PACKAGE_RHODIUM_S2_Phone_Canvas_Enhancement_Fix_4_ 2_51720111829_0
and you still have the problem???? :S
B16b: unfortunately yes... I applied alex fix, but this solved only scroll bar and softpad overlap but NOT incoming screen position...
maybe you are using dialer from quilin or another? this is not a very big issue, but you know, I'm quite curious how to fix ;-)
anyway, I flashed recent NRGZ28 energy rom and saw that he has the same problem, so maybe this is somehow generic problem...
but at least I have my own 23554 based on EUR stock ROM, quite stable, and only with modifications that I really need and like
best regards b16b!
try putting this pkg to run after your phonecanvas pkg in kitchen.
twopumpchump said:
try putting this pkg to run after your phonecanvas pkg in kitchen.
http://forum.xda-developers.com/attachment.php?attachmentid=303452&d=1270305669
Click to expand...
Click to collapse
I'm trying to open the link but I'm getting info that I've no permission to access this...
you can get it here...
reversmoded your dll and replaced in the phone canvas package but it did not solve the incoming call position.. works the same way as with my previous one...
I use stock Rhodium Phone_Canvas_Enhancement_4_2_51720111829_0 with fixes from Alex. Do you use the same package?
Lissek said:
reversmoded your dll and replaced in the phone canvas package but it did not solve the incoming call position.. works the same way as with my previous one...
I use stock Rhodium Phone_Canvas_Enhancement_4_2_51720111829_0 with fixes from Alex. Do you use the same package?
Click to expand...
Click to collapse
i use the one i gave you, exactly nothing else....thats it.
Problem solved
I have finally solved the problem by disassembling phcanhtc.dll and hex editing the file.
For anybody interested in technical details of the solution:
http://forum.xda-developers.com/showpost.php?p=6258611&postcount=15249
Lissek said:
I have finally solved the problem by disassembling phcanhtc.dll and hex editing the file.
For anybody interested in technical details of the solution:
http://forum.xda-developers.com/showpost.php?p=6258611&postcount=15249
Click to expand...
Click to collapse
glad you got it worked out so is this one better than the one i gave you i guess? ive never noticed having the problem in my rom but i gave you the files i use and they didnt work for you upload the one you modded i want to compare to mine.
twopumpchump said:
glad you got it worked out so is this one better than the one i gave you i guess? ive never noticed having the problem in my rom but i gave you the files i use and they didnt work for you upload the one you modded i want to compare to mine.
Click to expand...
Click to collapse
Hi twopumpchump
We may use different ROM base and/or different patches... Maybe you use some solution like ameba for windows repositioning? But once again thanks a lot for your willing to help in solving the problem
Please find my file attached, the change is one byte at the address 1E494 (from 0x34 to 0x23).
Lissek said:
Hi twopumpchump
We may use different ROM base and/or different patches... Maybe you use some solution like ameba for windows repositioning? But once again thanks a lot for your willing to help in solving the problem
Please find my file attached, the change is one byte at the address 1E494 (from 0x34 to 0x23).
Click to expand...
Click to collapse
can you do the similar modification on this file from my HD2?
Incoming Call in Lanscape w Rhodium Phonecanvas!
Lissek said:
Hi twopumpchump
We may use different ROM base and/or different patches... Maybe you use some solution like ameba for windows repositioning? But once again thanks a lot for your willing to help in solving the problem
Please find my file attached, the change is one byte at the address 1E494 (from 0x34 to 0x23).
Click to expand...
Click to collapse
Just wanted to say thank you. Now have incoming call in landscape with rhodium phonecanvas.
Just use the new Phone Canvas 5
WBR
Siemens Lover
SiemensLover said:
Just use the new Phone Canvas 5
WBR
Siemens Lover
Click to expand...
Click to collapse
I couldnt get landscape to work on that. Did you happen to have landscape working on it?
ai6908 said:
I couldnt get landscape to work on that. Did you happen to have landscape working on it?
Click to expand...
Click to collapse
NO landscape support!
WBR
Siemens Lover
Hi
Been playing with build 23112 with standard 2.53 packages on my Topaz (Touch Diamond 2) and apart from the standard workarounds with scrollbars, callerID etc which I sorted, I am stumped on one thing..
The fonts in some HTC applications, particularly EZinput and some of the phone canvas are displayed in a very heavy font. While this is somewhat cosmetic, it can make some symbols hard to work out.
I have tried replacing system fonts with several cabs available, playing with the Helvetica fonts and reg keys to no avail.
Has anyone got a solution?
Thanks
Craig
There's no solutions for it yet. I think it discussed in Fixes thread already.
You can try replacing gwes.exe and see if that helps. I havent tried it, just suggesting....
do you have htcfontlink installed?
Hi,
I haven't tried replacing gwes.exe tbh but in Googling its replacement came up with a fix for an issue with camera fonts so may try that thanks..
Yes, I cook in HTCfontlink, and even tried replacing it with HTCFontlink from the HD Mini ROM but didn't fix it..
Thanks
Craig
ok, I asked because it sounds to me as if the app is not loaded. maybe you can check the init launchxx and dependxx values to see if it is launched (i asume you also have the htc launcher apps, cant recall the names)
cruiserrr said:
ok, I asked because it sounds to me as if the app is not loaded. maybe you can check the init launchxx and dependxx values to see if it is launched (i asume you also have the htc launcher apps, cant recall the names)
Click to expand...
Click to collapse
Yeah, I tried launching it manually from the file explorer but that didn't work. Yeah, my ROM is the stock Topaz ROM with the HTC messaging mod and a T9 tweak. All other packages are unchanged.
[edit] Checked, and it has the same init launch and depend values as the stock Topaz packages
[edit2] Just been through the HD Mini ROM dump and found a package that replaces the system fonts Its FontGastEnhancement.. May try that!
Thanks
I have the same issue on the Omnia i900, but for the camera app. Seems most recent non-COM2 and non-COM5 builds are affected.
Tried removing the registry entries but didn't work (ended up with no fonts )
Related registry entries:
[HKEY_LOCAL_MACHINE\System\GDI\FontFiles\TrueType]
"EXT0"=multi_sz:".ttf",".ttc"
"EXT1"=multi_sz:".ac3"
[HKEY_LOCAL_MACHINE\System\GDI\FontDrivers\Microsoft TrueType]
"File"="\\windows\\mgtt_o.dll"
"Order"=dword:10
[HKEY_LOCAL_MACHINE\System\GDI\FontDrivers\Microsoft AC3]
"File"="\\windows\\decompdll.dll"
"Order"=dword:10
Changing GWES.exe does help though. Still trying to find an alternative solution.
Hi ock
Tired cooking in the FontGastEnhancement - Didn't work
GWES.exe from the HD Mini - Didn't work
Cooking the whole 23106 SYS XIP from HD Mini / modded EXT from Topaz
GWES.exe from 23557 - Does work!! Breaks fancy menus
Thanks
Please could you upload pictures or additional details where the bold fonts is solved or not with the GWES.EXE from 23557?
If you try to cook a pure 23557 the bold font problem existing.
Afraid I cant upload pictures, flashed bk to 21887 soon after.
Using GWES.exe from 23557 and 23563 (tried both) solved the bold fonts in HTC apps issue but introduced and issue where the "pivot" tabs in WM apps were not being rendered properly. These are the fancy arrows at the top of say a WM control panel screen. They appear transparent with the labels rendered on top of each other. The navigation still works though, you can swipe around and even touch the bar to navigate but it just gets more messed up..
I believe flashing a whole ROM of 23557 works fine as there are loads of examples and not many font complaints.
Craig
have you tried 23114 it doesn't have the over bolded text on IME
fards said:
have you tried 23114 it doesn't have the over bolded text on IME
Click to expand...
Click to collapse
I haven't been able to get hold of the SYS XIP packages for 23114 yet.
Is that with HTC EZInput 2.1?
Just cooked a ROM with 23563 SYS XIP and all is fine currently
Craig
Problem still exists in 23114.. With and without HTCFontLink
Craig
So none of the above tips work to fix the font issue uh!
Nope, doesn't seem like there is a solution, its something deep down in Windows. I'm running my ROM on 23563 and all seems stable and good.
craiglay said:
Problem still exists in 23114.. With and without HTCFontLink
Craig
Click to expand...
Click to collapse
You can give 23118 a try, I had some bold font issues in Omnia's Camera but problem's fixed for me in this build.
ock said:
You can give 23118 a try, I had some bold font issues in Omnia's Camera but problem's fixed for me in this build.
Click to expand...
Click to collapse
I've tried 23118 earlier today, same bold fonts in EzInput (it's all i look at)
Here it is: http://hotfile.com/dl/44675589/fc7d5f3/Manila_2.5.2013.rar.html
thanks for sharing...
Provide us more details about changes and from which ROM is those packages
Is it possible to cook it with EXT packages from 2.13 or 1.7x leaked rom?
Also the Manila_Footprints is missing.
many thanks for sharing,Cloudyfa
i cooked in my Rom -works perfekt
Best regards
Thanks for the share!
Thread added into the repositories list Thanks Cloudyfa you always got amazing news
thanks for sharing...
Well... I got to tell you all that it's from a CDMA2000 device so it lacks some function on GSM network. It's an operator customized Manila 2.5 and if you truly want to use it, don't use the Manila People package in it.
leonore said:
many thanks for sharing,Cloudyfa
i cooked in my Rom -works perfekt
Best regards
Click to expand...
Click to collapse
Did you use the packages as they are or did you change something.
If I just add the packages the homescreen is not starting. I just get the message "Launching HTC Sense..." then after a while I get "Tap here to launch HTC Sense"
Trying it on a Topaz with ROM 2.54 SYS 21904 EXT 21891
edit:
In the reg file of Manila core it says "Rhodium S2", wondering why it doesn't work on the Topaz.
It's working perfectly on my HD2 with 23569 - it's certainly not operator customised. It looks very similar to the Rhodium 20121225 (full landscape) version I was using before.
Thanks for sharing
It is working perfect for me too....
Cloudyfa said:
Here it is: http://hotfile.com/dl/44675589/fc7d5f3/Manila_2.5.2013.rar.html
Click to expand...
Click to collapse
Thks a lot
christonabike said:
It's working perfectly on my HD2 with 23569 - it's certainly not operator customised. It looks very similar to the Rhodium 20121225 (full landscape) version I was using before.
Thanks for sharing
Click to expand...
Click to collapse
It certainly is. The People tab MASD is CS_Manila_People, the MASD in the packages may be changed. And these packages come from a operator customized ROM.
cnzqy1 said:
It certainly is. The People tab MASD is CS_Manila_People, the MASD in the packages may be changed. And these packages come from a operator customized ROM.
Click to expand...
Click to collapse
I'm sorry, maybe I should have qualified my statement further:
Although this manila version may have originated from a Rhodium, operator customised ROM, there is no outward appearance of customisation.
Visually, and functionally, there is no difference to the Rhodium 2012 1225 manila I used beforehand.
If you can elaborate as to the CDMA customisation that breaks functionality on the people tab for GSM users, we would be very grateful (as it appears to work perfectly in all areas).
Thanks again to Cloudyfa for sharing!
christonabike said:
I'm sorry, maybe I should have qualified my statement further:
Although this manila version may have originated from a Rhodium, operator customised ROM, there is no outward appearance of customisation.
Visually, and functionally, there is no difference to the Rhodium 2012 1225 manila I used beforehand.
If you can elaborate as to the CDMA customisation that breaks functionality on the people tab for GSM users, we would be very grateful (as it appears to work perfectly in all areas).
Thanks again to Cloudyfa for sharing!
Click to expand...
Click to collapse
I didn't cook it in, but since the People tab is from a world phone(CDMA GSM dual mode), there should be functions missing or unneeded in the People tab. So I recommend changing the People tab.
Isn't this too small??
file removed please reup
Can anyone tell me what the latest build (both latest and stable versions please) of the old WM6.5 interface (the one where you need a stylus to use) are? Also, is it somehow possible to turn a WM6.1 (or WM6.0) nk.exe into a WM6.5 nk.exe that can take advantage of slots 60 and 61 without intervention from the OEM (the reason I ask is because I'm cooking for an Asus device which doesn't have an official WM6.5 or later rom)?
You can't turn a 6.1 kernel into a 6.5 kernel; you'll just have to get by with what you have. You could always try playing around with 6.5 kernels from newer devices with similar hardware, but it probably (>99% chance) won't work.
In that case, does anyone know the latest (stable and latest versions) builds of the old WM6.5 interface (the one which you needed a stylus for) are?
Steven855 said:
In that case, does anyone know the latest (stable and latest versions) builds of the old WM6.5 interface (the one which you needed a stylus for) are?
Click to expand...
Click to collapse
Com2 Latest build is actually 21916
You can find it here:
http://forum.xda-developers.com/showthread.php?t=650783
Ciao
21820
Personally, the most stable old version of WM 6.5 that I've played around with is Build 21820. I was able to use to use the kernel from WM6 when cooking a WM6.5.3 ROM somehow. However, doing so your device will be very buggy. I ended up with a WM6.5 "Classic" kinda UI that crashes every once in a while.
Steven855 said:
Can anyone tell me what the latest build (both latest and stable versions please) of the old WM6.5 interface (the one where you need a stylus to use) are? Also, is it somehow possible to turn a WM6.1 (or WM6.0) nk.exe into a WM6.5 nk.exe that can take advantage of slots 60 and 61 without intervention from the OEM (the reason I ask is because I'm cooking for an Asus device which doesn't have an official WM6.5 or later rom)?
Click to expand...
Click to collapse
The advantage of stylus has nothing common with old or newer 6.5 build. I cooked for Asus until 23152 - no difference. Using 6.0 nk.exe also does not cause any problems.
If you mean narrow lines saying "stylus" - just do the following:
[HKEY_LOCAL_MACHINE\System\GWE]
"TouchAutoLayout"=dword:00000001
You can also play with
[HKEY_CURRENT_USER\\Software\Microsoft\Today\Menu]
"MenuSelectorThemeImageBottomPadding"=dword:00000001
"MenuSelectorThemeImageTopPadding"=dword:00000001
To change the size of free space in Menu items, and standard size of open file dialogue:
[HKEY_LOCAL_MACHINE\\System\GWE\Commctrl]
"TreeviewExtraItemSpace"=dword:00000001
"TreeviewPlusMinus"=dword:0000000A
Play with parameters in these registry keys and choose the most wanted ones for you.....
This will not affect all the lines and dropdown menu but half of them - will definitely be fixed.
The only tip for your nk.exe - if you have ASUSMisc.dll in your OEMXIPKernel - move it from XIP to IMGFS.
P.S.
****, Steven855 asked his question in December.... My answer is just a waste of time....
AndrewSh said:
The advantage of stylus has nothing common with old or newer 6.5 build. I cooked for Asus until 23152 - no difference. Using 6.0 nk.exe also does not cause any problems.
If you mean narrow lines saying "stylus" - just do the following:
[HKEY_LOCAL_MACHINE\System\GWE]
"TouchAutoLayout"=dword:00000001
You can also play with
[HKEY_CURRENT_USER\\Software\Microsoft\Today\Menu]
"MenuSelectorThemeImageBottomPadding"=dword:00000001
"MenuSelectorThemeImageTopPadding"=dword:00000001
To change the size of free space in Menu items, and standard size of open file dialogue:
[HKEY_LOCAL_MACHINE\\System\GWE\Commctrl]
"TreeviewExtraItemSpace"=dword:00000001
"TreeviewPlusMinus"=dword:0000000A
Play with parameters in these registry keys and choose the most wanted ones for you.....
This will not affect all the lines and dropdown menu but half of them - will definitely be fixed.
The only tip for your nk.exe - if you have ASUSMisc.dll in your OEMXIPKernel - move it from XIP to IMGFS.
P.S.
****, Steven855 asked his question in December.... My answer is just a waste of time....
Click to expand...
Click to collapse
No, you're fine. I was waiting (and checking) until someone could give me a definite answer to my questions. Anyway, I'm curios as to why you mentioned ASUSMisc.dll (what does it do, exactly?). Am I moving this to imgfs to increase device performance or is this something that has to do with the nk.exe that can be changed or upgraded? Also, could there be some reason why my Asus A626 (which is a landscape device with native resolution 320x240) has a really slow framerate while in portrait mode, but has a fast framerate in landscape mode? This is a problem with the stock rom as well as any custom roms (so far) that I make. This is really apparent when I use a program that uses both gdi functions and gapi functions (such as pocketgnuboy, where the on-screen v-pad doesn't show in gapi mode, but still registers where I touch the screen). I did find a gxdma.dll in OEMDrivers.
Hi.
BTH of this thread because I can not see definite answer. Could I take any of higher xip's for example 28244 and port it to WM 6.5 not 6.5.x system ?
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Hi.
BTH of this thread because I can not see definite answer. Could I take any of higher xip's for example 28244 and port it to WM 6.5 not 6.5.x system ?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
Are you talking about the shell (interface) or the internal parts (like drivers and kernel stuff)?
fxdjacentyfxd said:
Hi.
BTH of this thread because I can not see definite answer. Could I take any of higher xip's for example 28244 and port it to WM 6.5 not 6.5.x system ?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
I can not really understand what you mean. What kinda advantage are you waiting from using XIP and SYS that do not match?
And what do you mean by "higher" XIP? Higher than what?
Concerning your question - you can not use 6.5 and 6.5.x components simultaneously - using XIP from 6.5 and SYS from 6.5.x or vice versa will cause unbootable rom.
Steven855 said:
Am I moving this to imgfs to increase device performance or is this something that has to do with the nk.exe that can be changed or upgraded..
Click to expand...
Click to collapse
As I told you - I don't have your model in hands and never cooked for it. I can only describe general Asus-related things.
Moving ASUSMisc.dll to IMGFS reduces OEMXIPKernel size and saving free space in slot0. Besides - ASUSMisc.dll is unmovable module when it's in XIP and you are porting new XIP for your device. That means you should move other modules around it to escape gaps and overlapping.
fxdjacentyfxd said:
Hi.
BTH of this thread because I can not see definite answer. Could I take any of higher xip's for example 28244 and port it to WM 6.5 not 6.5.x system ?
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
Yes but with bugs. I just experimented.
emo-dudes said:
Yes but with bugs. I just experimented.
Click to expand...
Click to collapse
Thanks. It seems I have to look for any highest ( best ) XIP for WM6.5
Regards
fxdjacentyfxd
AndrewSh said:
I can not really understand what you mean. What kinda advantage are you waiting from using XIP and SYS that do not match?
And what do you mean by "higher" XIP? Higher than what?
Concerning your question - you can not use 6.5 and 6.5.x components simultaneously - using XIP from 6.5 and SYS from 6.5.x or vice versa will cause unbootable rom.
Click to expand...
Click to collapse
Hi.
Maybe "higher" is not good word but what are the reasons there are so many xips ? I guees new functionality is supported, bugs are removed, perhaps stability and speed is improoved too. Thay is why I asked for best xip for WM6.5
I am not going to change SYS in my WM6.5. I only look for best xip.
Regards
fxdjacentyfxd
fxdjacentyfxd said:
Hi.
Maybe "higher" is not good word but what are the reasons there are so many xips ? I guees new functionality is supported, bugs are removed, perhaps stability and speed is improoved too. Thay is why I asked for best xip for WM6.5
I am not going to change SYS in my WM6.5. I only look for best xip.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
I guess people are confused because the xips tend to be connected to the sys builds. I don't think anyone talks about the best xip, personally; if they do, perhaps they're talking about changing oemxipkernel builds. Mixing and matching sys's and xip's seems like a good way to run into instability, not to improve the stability of a build.
Farmer Ted said:
I guess people are confused because the xips tend to be connected to the sys builds. I don't think anyone talks about the best xip, personally; if they do, perhaps they're talking about changing oemxipkernel builds. Mixing and matching sys's and xip's seems like a good way to run into instability, not to improve the stability of a build.
Click to expand...
Click to collapse
Maybe I am wrong but it does not have to be necessary that only one possible "pair" of xip and sys exists. Xip is a kernel so if it fulfills what upper layers needs ( device drivers, higher level dll's and applications ) it should work. Anyway porting prodecure ( creating new xip suitable for cooked system ) is based on existing SYS so maybe it is not so "black" scenario as some people say.
Is it true that in worst case I can only not boot my device but not brick ?
Regards
fxdjacentyfxd
Yeah, in the worst case scenario, you'll just get a non-booter. Not a big deal, but it's always disappointing. I just remembered that I have mixed and matched msxipkernels with sys's before-by accident. When I switched to OS Builder, I didn't know the proper way to port xips, and I think I was using the 23653 msxipkernel with all sorts of other builds, like 216xx, 231xx and 282xx. The roms were ok, but I did have issues with S.O.D. for the only time. I was really glad when I figured out what I was doing wrong, things have been smooth sailing since then. So, in my experience you can do it, but you probably don't want to do it.
I tried making a basic 6.5 stable ROM using COM2 (21916) build. But the screen becomes irresponsible once in the file explorer or the messaging. I can't tap on anything except the start menu and the X to end. Navigation is possible through the d-pad, but it is kinda annoying when you have a 2.8inch screen to play.
Can anyone help?
Shreyas Jani said:
I tried making a basic 6.5 stable ROM using COM2 (21916) build. But the screen becomes irresponsible once in the file explorer or the messaging. I can't tap on anything except the start menu and the X to end. Navigation is possible through the d-pad, but it is kinda annoying when you have a 2.8inch screen to play.
Can anyone help?
Click to expand...
Click to collapse
I'm not sure on that one. I guess if a soft reset can't cure it, you should try a hard reset (and if that fails, you might just have to go and reflash a more stable rom).
Steven855 said:
I'm not sure on that one. I guess if a soft reset can't cure it, you should try a hard reset (and if that fails, you might just have to go and reflash a more stable rom).
Click to expand...
Click to collapse
no ... i tryed that many times ...
shreyas use opal maybe wich needs nk.exe ... i couldn't find that any where
maybe we can use Ervius kitchen but i could't flash roms wich i cooked by ervius kitchen
some of opal developers use Flash Player ... use that and report shreya
tanx