Related
I searched around and haven't seen a thread about this yet but I think we should look at the slowness of the plugin. I know that on my G4 which was OS flashed to Crossbow it's totally bogged down now. Seen some reports of others. Is this a memory leak or conflict or just a case of code needing to be optimized? I've tried a few different configs so far but can't get past it.
ive noticed the same thing about mine. mines a g3 and it was very fast before but now its slow as heck after i installed the plug in. im not sure how to fix it. just confirming the problem on another phone.
It's fine on my HTC Touch
alanp23 said:
It's fine on my HTC Touch
Click to expand...
Click to collapse
Fine on my hermes too...
small lag on prophet,when i press the softkeys....But overall phone speed is ok!
Processors
Hermes has a 400mhz processor, so it should be ok on there!
However, I have a Wizard, which is only 200mhz, and it is absolutely crawling using this plugin!! But it's (as far as I know) the same processor as the Touch, so what is it that's causing it to run so slowly?
myk_83 said:
Hermes has a 400mhz processor, so it should be ok on there!
However, I have a Wizard, which is only 200mhz, and it is absolutely crawling using this plugin!! But it's (as far as I know) the same processor as the Touch, so what is it that's causing it to run so slowly?
Click to expand...
Click to collapse
I think the problem is with the access to \windows\ folder, try to open the folder and see how many time it takes...
The only problem I have with that theory, is that I assume the HTC Touch doesn't run this slowly all the time, yet that has the same processor as the Wizard and must have the same amount of files in the Windows foler?
Hermes has a faster processor, and Prophet is probably similar in design to the Touch, so they might mask the problems a bit better than the Wizard I guess. But there must be some way of making it run faster!
Already done it.Without HTC Home Plugin 5- secs,with the plugin 10+... I don't use the weather item,so i'm going to delete the weather pics.... and i will post results...
Same thing...lag... BUT i hard resetted,then installed HTC Home Plugin,and it was running full speed!then installed the HTC Touch pad and lag again....
Lagging on wizard G3
I have a G3 wizard and I'm having an incredible slowdown (both reboot and executions)
I installed the Home plug, comm man, dial pad (directly after the flash) and then installed spb pocketplus and netfront! That's all..
I can access the /windows folder in +/-13 secs
I reverted to my previous backup without the new HTC apps, and WOW!
Windows folder shows up almost instantly. Everything is alot smoother than with the Touch today plugin. But it is uglier as well.
What ROM is everyone using? Has anyone installed this on faria or most beautiful?
I know on Crossbow it slows down with just the today plugin installed.
Homeplug disgustingly slow on prophet here (latest Pdaviet rom, 234mhz), ....And then after I put the touch dialler on as well....Ugh! ...
ended up having to keep soft resetting just to stop unwanted dialling from tapping!
Interesting about the windows folder as for me, xp is taking forever to open this folder too. Looks like a hard reset is due....then I'll try again
triplejay said:
Homeplug disgustingly slow on prophet here (latest [...]....And then after I put the touch dialler on as well....Ugh! ...[...]
Click to expand...
Click to collapse
In fact, it seems every Touch application (dialer, htc home plugin, maybe even the sound manager?) slows the device a factor, but the home plugin is the worst.
I played with installing and uninstalling them after a hard reset. I agree it seems like the fuller the \Windows folder, the slower the device, but indeed that makes no sense.
Using Faria's latest, err, lets call it "10.1.0.811 WWE" on my Wizard. XM6?
Expander said:
In fact, it seems every Touch application (dialer, htc home plugin, maybe even the sound manager?) slows the device a factor, but the home plugin is the worst.
I played with installing and uninstalling them after a hard reset. I agree it seems like the fuller the \Windows folder, the slower the device, but indeed that makes no sense.
Using Faria's latest, err, lets call it "10.1.0.811 WWE" on my Wizard. XM6?
Click to expand...
Click to collapse
it has tons of pngs that it loads into the /window folder which lead to the explorer taking a lonfg time to open it
Just wanna report the same slowness on my MDA Vario [email protected] wonderfull XM6. But the looks are great, the slowlyness sucks. So does this mean that the plugins have to be optimized or can it be done through the registry?
After hard-reset I installed Dialer, and the phone was sluggish again, even without the today homeplug...
I guess it also has something to do, like already was said, with the graphical aspect of it. Many png's in the windows folder which are loaded for displaying everything that nice.
will one of you see if chabging the attributes of the png (to hidden,system,...) will change anything?
fallenczar said:
will one of you see if chabging the attributes of the png (to hidden,system,...) will change anything?
Click to expand...
Click to collapse
My windows folder is taking 31 sec to load up. I made all png files (about 1.4 meg worth) both hidden and system. Windows folder still takes 30 seconds to load. General responsiveness of the device did seem to get faster but I can't tell if it's that or the fact I flashed the official MS WM6 rom. Seems like since the plugin still references them it's taking up resources. Any way we can pack those into the plugin exe or would placing these in rom or extended rom speed up the process?
The plugin with official wm6 seems faster then xm6. Not talking smack, just an observation. I can't try NBD 7.0 since it won't flash properly but I've heard that's the fastest w/ plugin so far.
I need some help debugging the kitchen with the touchflo files.
For those who are sent the new kitchen; as you test and find solutions, please post what you did.
I wanted a sperate thread for just these specific objecives.
Here is the objectives:
To retain the ability to build a ROM with or without TouchFlo
To have only ONE seperate camera package that will work in any configuration
To allow portions of the touch software to work seperately should TouchFlo not be installed
I know there are other threads dedicated to debugging the touch software, however this is targeted at just the kitchen integration.
Current issues (v2):
Streaming Media isn't showing up in Programs, won't open.
Speed Dial hasn't been confirmed working or not.
No images for Beam - still need pictures!!!
Windows Live won't connect. Cab fixes issue. Need to find missing entries
Black Keyboard doesn't show numbers across top row. Need to find setting.
The power button will put phone into "standby" mode (basically screen and Wifi off), but won't power down.
318
I'll be glad to test. I was working on a 318 Kitchen but didn't get very far.
Too many Duplicate files.
Going back to work on my own kitchen I was much further along than what you have here.
My suggestions:
1) You should at start by deleting duplicate files. I can build a rom and flash it with my kitchen, I can't build with yours w/o getting one dup file error after another.
Please update, I will try to devote some time to your kitchen.
Thanks
NP. I'll update shortly.
My Files
I deleted dup files in my kitchen but I think I deleted one to many, now I can build, and I can flash using shelltool but it gets stuck at splash screen. Damm where did I go wrong??? I feel like a dumbass!
Hopefully this one will work a bit better. another 30 mintues till it's up.
The boot issue is probably related to the files in the OEMAPPS folder. There are some dll's in there that I found are super sensitive to this build - too bad I wasn't more careful in documenting what they were.
Documenting.
Started documenting now! Too much going on now not to, especially after my last mistake.
Test
So have you actualy built and started testing a rom with your kitchen?
I've been doing that for days... but I've tried a number of different combinations and this one seems most promising - though by no means is it ready. 1413 has by far been the easiest, but I still believe the 318 is the best choice.
I'm gonna be out until Monday night, so this is my last attempt for a few days
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Whiterat said:
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Click to expand...
Click to collapse
If you could, it would be much appreciated. Anything to help get closer to a fully functioning setup
Ok, so i tested the oem folder from the reTouched Beta thing. I included everything in there but my problem is that TouchFLO does not function the way it is supposed to. With what you guys are doing, have you verified that TouchFLO even operates correctly?
I thnk the touch flo isn't all its cracked up to be..I ran the reTouch wasn't a fan..its not as fast as any rom..only thing I like is the dialer and the cube
I actually have a good feeling about it. I ran the french rom for a couple days - and other than not knowing most of what it said (glad I know the OS and took 2 years of french in high school) I was very pleased with the performance. Specifically the speed at which the screen "rotated", responsiveness, and how quickly the contacts scrolled on the screen was impressive. Enough to keep me interested well into the night
so matt, think you can make a cab from it? the cube that is lol.
Here you go:
http://rapidshare.com/files/40068930/OEM.rar
Click to expand...
Click to collapse
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
So if what you are saying is true I should be able to create cabs from the correct?
AFAIK It wont be possible due to the touch driver not being replacable, you might be able to rename touch.dll and then update the registry entry.
cleaning up
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
hanzieman said:
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
Click to expand...
Click to collapse
For what I see whiterat folder are some reg tweaks that you'll probably use anyways, and as far as folders to remove it might be less of a hassle to simply add the packages that you use that are not there.
Hey guys,
So I finally got this outstanding TNT running and I'm getting to know it a little more everyday!
Now here's my little dilemma; I don't like WMP, never have. So on my TNT 19199 rom TCPMP was great. But on this TNT Pro (19213), it just isn't working! I downloaded the latest TCPMP that came in the fun pack, I tried the FLV patch, tried selecting all file associations on the program, even did the registry edit! Still, nothing.... IE runs wmp for vids or audios. I want TCPMP.
Is there anyway to deactivate WMP if all else fails???
Phil
P.s. - I little bit off subect here, but what is the best setting for the Pocketsnes? It runs real slow and for some reason, the buttons are never right! I like to play in landscape with the keypad.
Also, the connection between some bluetooth devices and my pda is a bit screwy. Is there some sort of patch to perfect the connection, make it more clear?
Last thing, what does A2DP do? Is that what I should use for my BT problem? And how do we set up the SDAutorun? I much appreciate that programs run off my SD card rather than clutter the pda's main memory...
By the way...
By the way guys,
I'd like to know how to release the ie touch. I don't know how to explain it, to be able to move the screen around like on opera or on the ie touchflo.... I don't want to install touchflo, just have that option on ie. I think there was a registry edit for that, although I can't remember where...
Also, I just saw a vid on youtube about the google android software on his wizard. The guy was running his wizard at 312mhz! Is that ever possible???
Phil
...?
Uhhmmmm,
Anyone?
Whats up Men! or Girl?
So I dont know... jeje sorry.
here I go...
1.- TNT 19213 has too much issues like HTC audiomanager in htc home doesnt works, no IR beam file for push it like obex, no HTC cube contacts face, this little issues makes me unhappy so i started to search fixes, NO FIXES instead!.
2.- The TCPMP is a great app, in this version from fun pack .81 RC if the flv option doesnt exist, instal the two files that are atached to this post uncompress the 2 FLV files and copy them to: storage... or root ...progam files/tcpmp/ folder that has every codec, if there is the square on file association check it! and exit the program by FIle menu... exit. and turn off the device and so... soft reset, it will function at all.
3.- It doesnt seems to be a fix for change the wmp to tcpmp plug in PIE but if you wish try the original app from streaming media cab in cabs for tnt roms forum right here on this thread.
4.- Because our poor speed processor the emulating is awfull! really awfull! none can turn landscreen on emulators, this 320 mhz omap processor maybe a 8525 device wizard like but it isnt wizard is a HERMES it has much PUNCH! i can retrieve you a most functional emulator but slow cause our processor its attached too.
5.- A2DP is stereo sound via bluetooth headset it came since aku 2 in WM5 is old but good, the issues for bluetooth that you are experimenting are normal because the new platfrm WM6.1 and ftp app.... and celphones with obex file tranfer, and other PPCs with other operative systems, this sucks but its truth.
6.- The sd autorun works simply but some programs wont be installed on your sd card, so if you don want this, its better that you can obtein cabs with options to install the program on SD or Main memory. thats cause the cab construction not for the UC capable Roms with SD autorun.
7.- For PIE touchy jeje you cant turn it touchy its better te Netfront 3.3 free version or 3.5 beta trial version. the 3.5 trial beta version has touchy settings its nice but beta trial, just change your date and enjoy for ever!
I hope to be usefull for you attending your PM, see you soon.. Men or GIRL?
I will try pda viet 19213 right here it seems to be great! jeje
http://forum.xda-developers.com/showthread.php?t=403425
Oh it hasn't splash screens!
Watch it, all 3 splash screens can be mod! amazing this is some thing i did.
the pda viet roms dont has splash screens just the last one but is awfull jeje try this.
what an enthusiasm, wow.
have fun..
btw...
just try fockin OLD 0.81 tcpmp + whole set of 'good' plugins.
OK guys - no doubt there are others like me who will try this.
TLR has created an uninstallable CAB for Manila in his 2.08.07.01 ROM, so yes, I gave it a go on my Uni.
First-off, before you all rush to download the CAB, I didn't get it to work. I tried with the 'extras' (see later), but it still failed to start. I have no doubt that when/if I do get it to work it'll be unusable, but I gotta see for myself
So - for all of you just as bad as me, here it is:
TLR's uninstallable Manila: http://rapidshare.com/files/128492592/HTCManila_TLR.CAB
The 'extras' that may help: http://rapidshare.com/files/128492945/Manila.zip
There's obviously more needed to even get this to run, but it's late, and I haven't the time tonight to 'play' further with it (especially since it takes around 20min to install, and even *longer* to uninstall!!).
If you do try it, be sure you've got plenty of Storage and RAM available. It takes about 16MB of Storage, and since it didn't yet work for me, I'm not sure how much RAM.
If you do get it to run (albeit no doubt *very* slowly), please let me know how.
-PJC.
I don't think we can ever make manila with 64Mb Unis.
I have a version that takes a lot RAM, and works so looow on my uni...
teixeirabmb said:
I don't think we can ever make manila with 64Mb Unis.
I have a version that takes a lot RAM, and works so looow on my uni...
Click to expand...
Click to collapse
I don't expect this to work *properly*, but would like to see it for myself on my Uni, since it's the full Diamond version.
-PJC
As pointed out by by good fellow teixeirabmb, HTC Manila v1.0.0103.0 from one of the forums here runs in Uni.
Tried it once and yes it grabs so much memory & speed is slow in 64 MB devices. However slow, frame rate in our Uni is much better than QVGA devices tested. Besides, you're right the version above is uninstallable & a hard reset is necessary to restore old setup.
Btw, in order to make it run you need dwmapi.dll & libGLES_CM dll I think in the Win directory. Just my guess. It run the first time I tried after soft reset. Tha app is cool & fun but not for keeps.
Tested this on an ATHENA (which is as fast as a diamond in most aspects).
No luck. It seems its just made up for Diamond and works on basis of the drivers therein...
Regards
ROM DEVELOPMENT CLOSED/ I NO LONGER COOK FOR THE HTC KAISER/ TREAD DEAD
So here it is guys, after much brain storming as to rather to release or not my Rom i finally decided to do so. Bare in mind this Rom i never though of releasing as its my own personal Rom with my Own taste, that being said this is somewhat rough and very unprofessional and most stuff is in the start menu. The Rom is called Unholly because that's the name i use on forums now a days, siulmagic is a very old one that unfortunately i cant change here
The Reason i released the Rom is that i never got the D3D drivers to work with any Rom(no offense to other Cookers), so i Decided to cook my own
PS; i can recook rom with 101 RAM and upload if enough request are made, but its mostly unstable, do to it not having the MEMFIX
now to the good Stuff
BTW if you want more Free memory you can disable manila 2d it gives you like 49-50mb free of memory, and if you want little bit more delete poutlook.ink and sddaemon.ink from startup folder in windows folder( that kind of rimes)
What's included:
Task Manager
[WM6.5] HTC 2DManila 2.0.19191432.04.WAlien.cab
At0mAng Enhanced D3D Driver
HTC-CA-Kaiser-Drivers
SJ SamsungOmnia_Driver_D3D
DragonWorld TopBar Icons Rev3
Youtube app
Games that work 100% out of the box
Call of Duty 2
Quake 3 CE
Xtract
Whats Removed:
Alot of stuff that i cant remember right now, remember this a stock like rom(if you cant find something then that means it's been removed sry)
Bugs: Download Camera Fix Below
Camera is almost useless you can take a shot but it wont save the photo, it seems the oemdrives i use to make D3D Drivers work render camera useless, so yea i cant fix that way beyond my knowledge,if i ever find a fix or if any of you do, pm me and il update the rom
Also the task bar thats supposed to come up when you touch the upper right corner is bugged(its a build related bug i cannot fix that)so yea you have to access the com manager from start menu, also because of that there no way that i know of to tweak the volume so im gona link a very simple app to do so
Thanks to:
Da_G for providing us with every rom
OndraSter for hes amazing kitchen with out it this rom would not have been posible
drkfngthdragnlrd for letting me use hes top bar icons
jjblaster3 for telling me how to make the D3D drivers work on WM6.5
and who ever i forgot to mention XD
Special thanks to:
My Brother RaffyVitto without him i would have never gotten interested in Wm phones
Screen Shoots:
Download Link
http://www.zshare.net/download/6683936049882852/
Volume App
http://handheld.softpedia.com/get/Audio/Volume-Control-35536.shtml
Camera fix
http://www.mediafire.com/download.php?gbnuw2mnmz2 (big Props to team T.i.R. for Camera Fix, you guys are the best)
"Double Comm Manager icons in start menu(also do not know hot to fix sry)"
Check your app.dat files (plus initflashfiles.dat in oem\oem_lang_0409 plus initflashfiles.txt in camera folder if you have it in OEM instead of EXT). If they move Camera.lnk into \Windows\Start Menu\Programs, delete the line
"Camera auto starts on first boot(dunno y and dont know how to fix it XD)"
Do the same again, but check for folder \Windows\StartUp. If it isn't there, check for HKEY_LOCAL_MACHINE\init whether there isn't anything about camera.lnk (LaunchXXX "Camera.lnk") and if yes, again, search for it in rgu and provxml files.
Happy to see new chef. Congrats on first release
OndraSter said:
"Double Comm Manager icons in start menu(also do not know hot to fix sry)"
Check your app.dat files (plus initflashfiles.dat in oem\oem_lang_0409 plus initflashfiles.txt in camera folder if you have it in OEM instead of EXT). If they move Camera.lnk into \Windows\Start Menu\Programs, delete the line
"Camera auto starts on first boot(dunno y and dont know how to fix it XD)"
Do the same again, but check for folder \Windows\StartUp. If it isn't there, check for HKEY_LOCAL_MACHINE\init whether there isn't anything about camera.lnk (LaunchXXX "Camera.lnk") and if yes, again, search for it in rgu and provxml files.
Happy to see new chef. Congrats on first release
Click to expand...
Click to collapse
Thx for the reply, were exacly is the app.dat files? i francly dont know were they are, also the initflashfiles.dat i also dont know were that files is so if you can gide me to it id be more than happy. also were would i go to check my kitchen registrys
welcome new cheef !
btw - athenOS has 101mb ram and d3d already. so - we wait new rom`s from you.
obaz said:
welcome new cheef !
btw - athenOS has 101mb ram and d3d already. so - we wait new rom`s from you.
Click to expand...
Click to collapse
im shure he does but game's dont run accelerated as he probly uses the MEMFIX, witch render D3D driver useless
interesting!!!
nice to see someone addressing the latent potential for gaming in the kaiser!!!
i'd try out the ROM for myself but don't have the time currently...
i'm curious to know, what kind of framerate do you get in q3 on this ROM ? i'm a HUGE quake 3 fan (and an excellent 1-on-1 player and ctf flag snatcher too ), notice my custom q3a theme/lock screen in my signature below
anyway, i hope you can iron out the kinks in the ROM so that it can be made good for regular use also...and do let me know some fps numbers for q3 on the ROM!
cheers!
app.dat in all EXT folders, initflashfiles.dat in OEM\OEM_Lang_0409 and if you have Camera in OEM instead of EXT, search in OEM\<camera folder name>\initflashfiles.txt
I was looking for a rom just like this. Siulmagic, if you can fix those minor problems, I'd switch to this rom.
Too many roms come with 101 ram hack, that makes 3D acceleration useless.
Great release bro ehehehe, im guilty of charge , i created an awsome chef LOL.
hey guys sorry for not replying sooner aion has got me playing like a friken crack head XD,about the rom il try to fix some of the bugs in it, but i cant promise anything il try and start fixing them tomorrow thats if im not still playing aion, goh what a time for me to start playing an mmorpg
btw: im glad i got some ppl interested in it heh never expected that
D3D drivers wont work good cooked in, if you have memory hack. But if you install it after, then it should work just fine. At least thats what Anryl used to say!
I tried to install drivers after I flash a 101MB ROM, and it doesn't work at all. The only WM6.5 rom that would work is T.i.R. v16 K, but it's using a relatively old WM6.5.
I've tried to run GLbenchmark, and it won't work unless you don't have 101MB. To even complete the benchmark, you need to replace the DLL "ahi2dati.dll" with a renamed copy of "ahi2dati_dm.dll".
Also worth to note that by installing 3D drivers, you can't run Opera Mobile 9.7. Though, I don't see this as a problem right now, since Skyfire is much better anyway.
ai6908 said:
D3D drivers wont work good cooked in, if you have memory hack. But if you install it after, then it should work just fine. At least thats what Anryl used to say!
Click to expand...
Click to collapse
thats what i used to belive, but then i said meh what the heck il cook em in and see how it goes, and you guessed it they work exacly as i would have installed them manually.
btw about the rom still ironing out the bugs, i just cant seem to know how to fix the damn camera button not launching the camera like its supposed too
To Ondraster:
i think i managed to fix the double com manager icon(need to flash rom to verify)
about the camera startup bug, i search in my \OEM\OEM_Lang_0409 directory and theres no initflashfiles.dat file there so i dunno whats wrong, tho what i would really like to fix is the camera button to launch the camera instead of the album(or i think it does , because it dosent even open it just says it in the task bar, it likes opens for a few seconds then closes)
siulmagic said:
thats what i used to belive, but then i said meh what the heck il cook em in and see how it goes, and you guessed it they work exacly as i would have installed them manually.
btw about the rom still ironing out the bugs, i just cant seem to know how to fix the damn camera button not launching the camera like its supposed too
To Ondraster:
i think i managed to fix the double com manager icon(need to flash rom to verify)
about the camera startup bug, i search in my \OEM\OEM_Lang_0409 directory and theres no initflashfiles.dat file there so i dunno whats wrong, tho what i would really like to fix is the camera button to launch the camera instead of the album(or i think it does , because it dosent even open it just says it in the task bar, it likes opens for a few seconds then closes)
Click to expand...
Click to collapse
Congrats on release
Have you tryed in Settings\Buttons to map it? and see if opens up Camera.
If does the REG to set buttons is:
HKLM\Software\Microsoft\Shell\Keys
stylez said:
Congrats on release
Have you tryed in Settings\Buttons to map it? and see if opens up Camera.
If does the REG to set buttons is:
HKLM\Software\Microsoft\Shell\Keys
Click to expand...
Click to collapse
thats the problem is that the camera is mapped to the correct button, but when i push the camera button all it does it open pictures a videos for a brief moment and then closes, i am going to try that reg key if it works il add it as a fix i guess
There has to be an initflashfile, do you have show hidden files and stuff in the pc? If you dont, then you wont see initflashfiles.
Also run camera.exe from windows folder and see if camera opens. If it does, then then you camera.lnk file got messed up.
ai6908 said:
There has to be an initflashfile, do you have show hidden files and stuff in the pc? If you dont, then you wont see initflashfiles.
Also run camera.exe from windows folder and see if camera opens. If it does, then then you camera.lnk file got messed up.
Click to expand...
Click to collapse
thats exacly what it does it only open from the shhortcut in start menu or form windows folder, and yea il check if i got hidden files off but i doubt it(maybe im wrong win7 turn it back on)
Hey siulmagic, any progress on your rom?
sorry about the late reply but just today i took a break from aion, so i decided to tackel some of the bugs from my rom and i managed to fix the camera button bug, the only bug that remains is the one were it takes like a minute to save photos you take with camera(i have no idea y that happens) so yea as soons as i figure how to fix it or if anyone know's how to fix it do tell, untill then i cant release the rom, but stay tunned for future releases =)
ok guys the next rom release is coming nicely iv ported xip 23060 so now the rom is up to date, but still the camera bug is there until i can fix that no release sry, so stay tuned guys wish me luck