Just had a few questions to the cooks out there maybe can help me solve why porting the Iolite rom to the tilt is becoming an epic failure for me. I have tried xip porting three different ways with all the same results. First two i get a double beep than tap screen, but i can not tap the screen to get it to go on. Third way got single beep than tap screen and once again no response from the screen. I copied the sys over and g'relocd it. I have tried this with the 3.34 base. Do i need anything else? Is it necesarry to have the manila 2d included? Also on another note I tried with the AT&T rom as a base which works fine except the folders are empty and I can not make any data connections.
how did you port the SYS?
sounds like an SYS issue
I copied the SYS from the Iolite rom and ran g'reloc to the proper values. Unless im doing something wrong there. I have done the same when porting the blackstone roms minus the dpi192 folders. For this I just copied it all. Must i keep the dpi96 folders from the original rom for it to work. If so I feel noobish lol. on another note I also did try just copying the gwes.exe and the other per your sys porting guide (Thanks Mbarvian) and had the same results. Unless my XIP porting is not happening correctly.
vonmolk said:
Just had a few questions to the cooks out there maybe can help me solve why porting the Iolite rom to the tilt is becoming an epic failure for me. I have tried xip porting three different ways with all the same results. First two i get a double beep than tap screen, but i can not tap the screen to get it to go on. Third way got single beep than tap screen and once again no response from the screen. I copied the sys over and g'relocd it. I have tried this with the 3.34 base. Do i need anything else? Is it necesarry to have the manila 2d included? Also on another note I tried with the AT&T rom as a base which works fine except the folders are empty and I can not make any data connections.
Click to expand...
Click to collapse
Well, I can confirm this issue. See my post here.
http://forum.xda-developers.com/showthread.php?t=478647
I thought it was a SYS issue as well. However, I re-ported the SYS, didn't change anything in it. Just g'relocd, and went on. There is just one difference, I only had the touch screen not respond once. Every other time, no problems. Just still receiving that stupid double beep before the tap screen message. I can up a zip of my kitchen for anyone that wants to take a look at it. :/
Hey KMFM$
Yeah the double beep thing is weird. The only time I did not get the double beep was when I used the XipportEx thats posted on the forums, but every single time im getting no response from the touchscreen Really want to get a rom going. I want to develope a nice rom for the community to use, but I have much learning to do before I release something out. Currently I want to do release something with both a HTC and an AT&T base rom.
vonmolk said:
Hey KMFM$
Yeah the double beep thing is weird. The only time I did not get the double beep was when I used the XipportEx thats posted on the forums, but every single time im getting no response from the touchscreen Really want to get a rom going. I want to develope a nice rom for the community to use, but I have much learning to do before I release something out. Currently I want to do release something with both a HTC and an AT&T base rom.
Click to expand...
Click to collapse
Yeah, that double beep is just driving me nuts. Off hand, do you know if you're using the XIP porting utility from ervius' (from the XIP Porting Tutorial in Dev&Hacking) or the similar one posted by lennysh? Also, are you using the SYS supplied in anryl's kitchen thread?
Hopefully, we can find an answer for this soon. I would like to release this ROM, but this is just one bug that I cannot deal with.
KMFM$ said:
Yeah, that double beep is just driving me nuts. Off hand, do you know if you're using the XIP porting utility from ervius' (from the XIP Porting Tutorial in Dev&Hacking) or the similar one posted by lennysh? Also, are you using the SYS supplied in anryl's kitchen thread?
Hopefully, we can find an answer for this soon. I would like to release this ROM, but this is just one bug that I cannot deal with.
Click to expand...
Click to collapse
The three i have used are lenny's which produces the double beep
The manual from post http://forum.xda-developers.com/showthread.php?t=438676 also has the double beep.
Finally the one from ervius does not do the double beeping.
I extracted the iolite rom using htrcie than the packagebuilder. It has worked for me many times.
Still can't figure out why with the HTC rom no touchscreen, but the AT&T rom base works, but is seriously crippled.
Interesting. I'm using the XIPPorterEX from Ervius' and I'm receiving the double beep. I'm currently using the XIP and SYS supplied from anryl's kitchen thread. I'm having the hardest time finding the original files for porting. I don't know if I'm just searching the wrong thing or what. Oh well.
KMFM$ said:
Interesting. I'm using the XIPPorterEX from Ervius' and I'm receiving the double beep. I'm currently using the XIP and SYS supplied from anryl's kitchen thread. I'm having the hardest time finding the original files for porting. I don't know if I'm just searching the wrong thing or what. Oh well.
Click to expand...
Click to collapse
I downloaded it from this post here http://forum.xda-developers.com/showthread.php?t=476828
Unless I extracted the XIP incorrectly or the rom itself. Not sure. Could go with the AT&T base and have no data connection and empty folders
alright,
I just manually ported the XIP and the SYS from the same ROM that you mentioned, and posted them here:
http://forum.xda-developers.com/showthread.php?p=2953748
please give it a try and let me know if it works
good luck cooking
mbarvian said:
alright,
I just manually ported the XIP and the SYS from the same ROM that you mentioned, and posted them here:
http://forum.xda-developers.com/showthread.php?p=2953748
please give it a try and let me know if it works
good luck cooking
Click to expand...
Click to collapse
Thanks, mbarvian! I'll give it a go and report back.
mbarvian said:
alright,
I just manually ported the XIP and the SYS from the same ROM that you mentioned, and posted them here:
http://forum.xda-developers.com/showthread.php?p=2953748
please give it a try and let me know if it works
good luck cooking
Click to expand...
Click to collapse
Thanks mbarvian! I'll give it a shot once I get home from work
Hmm. Just tried your port, mbarvian. It put me in the same boat as vonmolk. It doesn't make it past the splash screen. I'll try another kitchen and test again. Just for info, I'm using the 3.34 OEM and cmonex's 3.29Hard2 SPL.
@mbarvian: Note, I just took the folders as you had them, mbarvian, and added the OEM. Did you G'reloc the SYS folder? I didn't so I'll give that a try and test next.
EDIT After g'relocing, the ROM works. HOWEVER, I'm still getting the two chimes (beeps) before "Tap screen to setup device" displays. I'm going to try anryl's or abusalza's ports and see if those give the double beep before the "Tap screen" text. Thanks for the help, mbarvian.
KMFM$ said:
Hmm. Just tried your port, mbarvian. It put me in the same boat as vonmolk. It doesn't make it past the splash screen. I'll try another kitchen and test again. Just for info, I'm using the 3.34 OEM and cmonex's 3.29Hard2 SPL.
@mbarvian: Note, I just took the folders as you had them, mbarvian, and added the OEM. Did you G'reloc the SYS folder? I didn't so I'll give that a try and test next.
Click to expand...
Click to collapse
Yes, I started with the 3.34 SYS folder, ported over the SYS (everything except the .VM folder), G'Reloc'ed it, and ported the XIP.
that's weird that it doesn't work, I'll look into it
KMFM$ said:
Hmm. Just tried your port, mbarvian. It put me in the same boat as vonmolk. It doesn't make it past the splash screen. I'll try another kitchen and test again. Just for info, I'm using the 3.34 OEM and cmonex's 3.29Hard2 SPL.
@mbarvian: Note, I just took the folders as you had them, mbarvian, and added the OEM. Did you G'reloc the SYS folder? I didn't so I'll give that a try and test next.
EDIT After g'relocing, the ROM works. HOWEVER, I'm still getting the two chimes (beeps) before "Tap screen to setup device" displays. I'm going to try anryl's or abusalza's ports and see if those give the double beep before the "Tap screen" text. Thanks for the help, mbarvian.
Click to expand...
Click to collapse
Just my $0.02, tested Hyperdragon's version of the Iolite ROM and the two beeps before is present...
talonz55 said:
Just my $0.02, tested Hyperdragon's version of the Iolite ROM and the two beeps before is present...
Click to expand...
Click to collapse
Yeah noticed that when I tried his ROM out. Just no idea what is going on that is preventing a successful port over of this rom to the kaiser. I see two roms the hyperdragon and anryl's rom out there. Tried your port mbarvian and I get the same results
vonmolk said:
Yeah noticed that when I tried his ROM out. Just no idea what is going on that is preventing a successful port over of this rom to the kaiser. I see two roms the hyperdragon and anryl's rom out there. Tried your port mbarvian and I get the same results
Click to expand...
Click to collapse
you have to G'Reloc the SYS again for some reason, before cooking and flashing it
mbarvian said:
you have to G'Reloc the SYS again for some reason, before cooking and flashing it
Click to expand...
Click to collapse
Thanks for posting another base...something else to work with while we wait for 6.5.
mbarvian said:
you have to G'Reloc the SYS again for some reason, before cooking and flashing it
Click to expand...
Click to collapse
Okay so run g'reloc once close and re-run it or just click do it and than do it again?
I'll give it a shot when i get home tonight.
Thanks Mbarvian for the help and the inspiration to get me start cooking when the tutorial post.
vonmolk said:
Okay so run g'reloc once close and re-run it or just click do it and than do it again?
I'll give it a shot when i get home tonight.
Thanks Mbarvian for the help and the inspiration to get me start cooking when the tutorial post.
Click to expand...
Click to collapse
yes, just Open G'Reloc, and click "Doit!" until all of the modules are relocated (shown at the bottom of the window). You may have to do it twice or thrice.
No problem, I'm glad to be of assistance where I can be
good luck cooking
Related
... since this problem is bugging us with aku3.x and crossbow roms.
Especially with the crossbow rom, this seems to be the only problem. The other issues are already fixed, or are easy to get fixed (since they have already been fixed in earlier roms).
In addition to this, I think that if we work together we have greater chances of solving this frustrating issue.
So this is what I have tried (with no success):
1) replace the battdrv.dll with one from a prophet
I get the common result where the device will charge only when you softreset with the cable inserted. You also get a square in the "Model No" in device information (Module address conflict?) Someone solved the square issue in an aku 3.x rom. I would like to know how it was fixed.
2) replace the battdrv.dll with one from an HTC artemis
No charging/status indication. Model No is reported as "WIZA200"
3) I unloaded camera and keyboard driver to see if there are any conflicts with them - no difference
andrew_sh said:
... since this problem is bugging us with aku3.x and crossbow roms.
Click to expand...
Click to collapse
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus
ikarus said:
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus
Click to expand...
Click to collapse
Thanks for the info.
I just tried it.
Result:
I get the square in the device info.
No charging/no battery status.
Strange isn't it? I wonder why the model no gets f**d up.
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
I tried replacing this file. The result is that activesync stops working completely.
MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus
ikarus said:
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus
Click to expand...
Click to collapse
ahh, thats a handy tool, thanks for the tip !
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
ikarus said:
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
Click to expand...
Click to collapse
Thanks ikarus, i'll try tomorrow.
So have you tried this? Did you find out what was causing the problem?
andrew_sh said:
So have you tried this?
Click to expand...
Click to collapse
MusicMike tested it, but it needs more testing hehe
andrew_sh said:
Did you find out what was causing the problem?
Click to expand...
Click to collapse
not yet... in part yes, but i don't want to write explanations which could turn out to be wrong...
I'm back, testing it now
Jesterz said:
I'm back, testing it now
Click to expand...
Click to collapse
Welcome back! hehe damn it's been a long time
HELP
okay i have the japnease wm6 rc7 both files its all in jap appantly the battrey issue is fixed and all the other problems can someone help me to convert the language into english and then i can test on my prophet we may have a fully working wm6 rom here guys please need help for final stages.
WM6 100% working on prophet
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly i need a hero to covert the language into english please can someone help
c3l5o said:
so I was just wondering what does the app change in my phone to make it work... I didn't eve have to soft reset it once...
Click to expand...
Click to collapse
jutley said:
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly...
Click to expand...
Click to collapse
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus
anyone sucess pls post...
i'll try tomorrow
ikarus said:
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus
Click to expand...
Click to collapse
Ok thanks ikarus! Really is a smart and slight solution
guitarz said:
anyone sucess pls post...
i'll try tomorrow
Click to expand...
Click to collapse
It IS working indeed
This fix tested and working on Qtek S200! Its one of the 2,2 clean roms from a few months ago. The battery problem has been my biggest annoyance! Thanks!
I also tried XDADev_BatFix on my 818Pro with AKU3.3-Jester-b1 ROM.
Looks like it really solve the battery charge problem.
Thanks ikarus!
Worked
It Worked on I-mate JamIn, Thanks.
some times the device do not wake up after it sleeps
The weirdest thing has been happening after I build any ROM based on 5.2.1413... at about 99% the RUU exits.. i keep having to use different builds with my ROMs and I would like to use .1413.. any ideas/suggestions? also how do you add a different package to the BuildOS app and change registry while building? Thanks everyone!
-Nstefanelli-
nstefanelli said:
The weirdest thing has been happening after I build any ROM based on 5.2.1413... at about 99% the RUU exits.. i keep having to use different builds with my ROMs and I would like to use .1413.. any ideas/suggestions? also how do you add a different package to the BuildOS app and change registry while building? Thanks everyone!
-Nstefanelli-
Click to expand...
Click to collapse
which kitchen are you using? I didn't have this issue with the Pandora setup. Might check it out. http://rapidshare.com/files/35699228/5.2.1413_OS.zip
Check the OEM Package in my kitchen in the sig. It has a bunch of examples.
nstefanelli said:
The weirdest thing has been happening after I build any ROM based on 5.2.1413... at about 99% the RUU exits.. i keep having to use different builds with my ROMs and I would like to use .1413.. any ideas/suggestions? also how do you add a different package to the BuildOS app and change registry while building? Thanks everyone!
-Nstefanelli-
Click to expand...
Click to collapse
yes, this is simple... Your rom is too big (too much stuff in it!). What I do is after I get my nk.nbf built, and before flashing, I use XP's explorer and do a properties on the nk.nbf. If the size (with splash screens) is 57.3MB or larger its too big and this is what will happen. If you don't have splash screens, it needs to be 57.0MB or smaller.
Those numbers are my rule of thumb. May not be exact but larger than that seems to always fail for me.
KitChenROM Core 5.2.1908 Build 18508.0.7.0 :
New OEMs :
1. HTC Home New Version (Show HTC Home in Today)
2. Skin WMP.
3. PP=6MB
http://rapidshare.com/files/5396981...CTAIVOI_Core_1908_Build_18508.0.7.0_PP6MB.rar
Good stuff! Thank you . But can anyone share a mirror? Rapidshare's just really too slow!
Great! Thanks
Great job! Thanks.
Just a small note: the version of esmertec java is a bit outdated 20070425. I can prepare a OEM package with 20070802 if you want.
Thanks again
PS: has this rom been completely ported, i.e. all dll rebased and so on?
Great thanks boy_de_ghet great job!!
risidoro said:
Great job! Thanks.
Just a small note: the version of esmertec java is a bit outdated 20070425. I can prepare a OEM package with 20070802 if you want.
Click to expand...
Click to collapse
OK, it seems that the files in your oem package (2007_04_25) and the ones i got in this forum (2007_08_02) are the same. The only differences are in the registry keys, i don't know which keys are the correct ones but i suspect that the ones in your oem package cannot work since they associate jad and jar files with \windows\joedek.exe but there's no such file in \windows. The correct association is with \windows\jbed.exe. Your oem package will probably run ok but it won't let you start midlets installation right from the browser/file manager.
I'm attaching a slightly revised OEM package with correct file association, a link to jbed help in \windows\help and some missing png files added to initflashfiles.dat
Bye
thanks!
...time to light the fire
great job, as usual!
Can you provide some more info?
Which applications are added?
Screenshots?
Thank you very much!
risidoro said:
Great job! Thanks.
Just a small note: the version of esmertec java is a bit outdated 20070425. I can prepare a OEM package with 20070802 if you want.
Thanks again
PS: has this rom been completely ported, i.e. all dll rebased and so on?
Click to expand...
Click to collapse
This KitChenROM haved Esmertec Jbed 20070802.
boy_de_ghet said:
This KitChenROM haved Esmertec Jbed 20070802.
Click to expand...
Click to collapse
Yep, i realised soon after my post. The registry settings however are incorrect (they reports version 2007-04-25 and associate jad/jar to jeodek.exe instead of jbed.exe)
Great work BTW! Thanks
is it real QVGA version of AKU0.7.0 or mix of Universal's VGA AKU0.7.0 with older QVGA resources?
I've just flashed a new rom made with this kitchen. It is BY FAR the fastest rom ever tried!!!
BUT THERE IS A GREAT problem: i cannot access any SIP input methods from any application. All the SIPs (keyboard, letter recogniser and block recogniser have vanished).
EDIT: no more a problem, it went away after a soft reset
i did not read whole post.
i have one question, that "someone" could answer to...
HOW the hell use OLD commgr and OLD dialpad in that one.....i need 100% method for REPLACEMENT of these.
also - how to implement OLD no(fockin) touch touch driver...
I ran the buildos.exe but after finish, I don't see the 80040000-OS.nb in the temp folder anywhere. There's a dump file with all the stuff in it. Gimme a clue someone.
run the CreateRom.bat file...it should be in the same directory with the BuildOS.EXE
thanks, it works now.
problems
i built a rom with this kitchen and after i built it and flashed it to my wizard it will start to boot up for the first time and it will get to where u calibrate the screen and turn itself off and restart...in a endless cycle....this isnt hte only time ive had this problem its happened with other kitchens...i just dont know what the problem is...or how to fix it.....any ideas? any help would b great appricated! thanks!
jug6ernaut said:
i built a rom with this kitchen and after i built it and flashed it to my wizard it will start to boot up for the first time and it will get to where u calibrate the screen and turn itself off and restart...in a endless cycle....this isnt hte only time ive had this problem its happened with other kitchens...i just dont know what the problem is...or how to fix it.....any ideas? any help would b great appricated! thanks!
Click to expand...
Click to collapse
We need to know exactly which options did you enable and which not.
my bad ur right hmm let me see
i deleted(not non selected but actually deleted from the oem folder)
EsmertecJava
Eye on Privacy
Hibernate
Camera
and then added my own oems
coolcam
wm6 Palm Threader
all other options were enabled
palm threader i made myself but i know it works bc ive used it b4...the issue might b with the coolcam...or that i deleted the oems....idk...but ive had this issue b4.
thanks for ur help!
jug6ernaut said:
my bad ur right hmm let me see
i deleted(not non selected but actually deleted from the oem folder)
EsmertecJava
Eye on Privacy
Hibernate
Camera
and then added my own oems
coolcam
wm6 Palm Threader
all other options were enabled
palm threader i made myself but i know it works bc ive used it b4...the issue might b with the coolcam...or that i deleted the oems....idk...but ive had this issue b4.
thanks for ur help!
Click to expand...
Click to collapse
Use the kitchen and don't delete anything or add anything. If that ROM works, start by removing the stuff from the OEM folder and build again. If that works, then you know the problem lies with one of your custom apps.
jug6ernaut said:
my bad ur right hmm let me see
i deleted(not non selected but actually deleted from the oem folder)
EsmertecJava
Eye on Privacy
Hibernate
Camera
Click to expand...
Click to collapse
DO NOT REMOVE CAMERA!!!
It's not a clean package, it includes also some files and reg settings needed elsewhere in the rom. The other packages you listed can be safely removed. bye
helloooo,everybody
i used ImgfsTools 2.1rc1 and followed bro Tadzio's introduction to cook my rom based on helmi_c's rom~
everything goes well
after NBMerge, i used dutty's tool to generate the os-new.nbh
and flashed it with pof's KaiserCustomRUUv1
but just 1%,my device rebooted and the KaiserCustomRUUv1 tells:
error 244: INVALID MODEL ID
it was still though i didnt modify anything in 'dump' directory
if i flash helmi_c's rom directly,that would be successful
what's wrong i have done? any tips?
forgive my broken Englsh pls...
REGARDS
Sheng
did you flash HardSPL to your Kaiser first?
heh... I had the exact same problem as yours (invalid model id). Using HTC Rom tool, I forgot to set Kaiser as the target ID for the nbh & it defaulted to hermes (I've since edited the ini file to change this).
yea.
i've got HSPL already and i have flashed the other roms many times, thats no problem.
fortunately that error just made my tytnII reboot and i can enter today screen,nothing change at all.
regards
Sheng
i believe your question was just answerd above and i also take it as SLEUTH getting a kaiser? thats cool man welcome to the new club house
woohyuksheng said:
helloooo,everybody
i used ImgfsTools 2.1rc1 and followed bro Tadzio's introduction to cook my rom based on helmi_c's rom~
everything goes well
after NBMerge, i used dutty's tool to generate the os-new.nbh
and flashed it with pof's KaiserCustomRUUv1
but just 1%,my device rebooted and the KaiserCustomRUUv1 tells:
error 244: INVALID MODEL ID
it was still though i didnt modify anything in 'dump' directory
if i flash helmi_c's rom directly,that would be successful
what's wrong i have done? any tips?
forgive my broken Englsh pls...
REGARDS
Sheng
Click to expand...
Click to collapse
Better than dutty's NBH tool, get the Dark Simpsons tool here with Kaiser support...
http://forum.xda-developers.com/showthread.php?t=311909
Cheers.
austinsnyc said:
i believe your question was just answerd above and i also take it as SLEUTH getting a kaiser? thats cool man welcome to the new club house
Click to expand...
Click to collapse
Thanks.... the Hermes was getting too reliable (boring)
Seems thats also now the case with the Kaisers lol... Tazdio's tools work great now after about 2 weeks of flashing roms that didnt work lol...
Oh I dunno... that pesky gps acquisition bug needs fixing and the PIE scroll freeze issue is a cooked in only patch so far. Tadzio is going to send me an updated toolset too itnf hopefully.... I'm itching to flash up a quick personal version with reghacks/PIE fix & maybe a different External GPS app. I may even adapt the hermes GPS RIL shim to express the Kaiser GPS on COM7 so the hermes external GPS applet can handle it.
so that scroll freeze issue in PIE doesn't just happen to me?! what a freakin relief!!!!
It's a real PITA for sure.... I've tried to make a cab to fix it but my initial attempt trashed my phone's RIL for some reason. I'll look at the dependencies more soon...
Recently I download a few tools from here and follow the introduce I tried to cook my first Kaiser ROM, although every thing got all right a lucky greenhand failed to brick his Kaiser, my new rom tell me "NO BLUETOOTH DEVICE DETECTED", I checked files "BlueTooth" and "BlueTooth_Lang_0804" and even replaced it with same files from other rom but it just simply do not work...
I'll be greatful if somebody can spare his time to help me.
BTW, I'm using 20273 Main OS.
BTW2, Please, make your words foreigner friendly.
Thanks all the same.
Why my post can't be seen from the list?
Where did the OEM part of your kitchen come from?
You can get a ready made 20270 kaiser kitchen from ppckitchen.org. Updating that to 20273 is trivial, or you can wait for ppckitchen.org to release it. Not much noticeable difference between 20273 and 20270, however.
A chinese Kaiser form, the developer just said his OEM was not well modified. So I'll have to wait...
Thanks for your attention.