Hi,
I want to try to make a phone call using the RIL on a smartphone.
Is it possible ?
How can I get the ril.lib ?
If someone has already developed such a service please send me thoe source .
in tstril.zip from http://xda-developers.com/RIL/ there is a ril.lib file.
you can create it your self by running
Code:
lib /def:ril.def /machine:arm
the ril.h is far from complete. maybe someone has the time to copy
them from the patents.
the constants are more work, you need to do some reverse engineering to find those.
and the patent may not be exactly what has been implemented.
Where is the ril.def ? Have I to define it by myself ?
Where is the complete ril.h ? Is it the same as in tsril ?
In fact I want to use the RILDial function and I need to know
the syntax of this function.
Thanks for your answer
XDA developer Itsme said:
in tstril.zip from http://xda-developers.com/RIL/ there is a ril.lib file.
you can create it your self by running
Code:
lib /def:ril.def /machine:arm
the ril.h is far from complete. maybe someone has the time to copy
them from the patents.
the constants are more work, you need to do some reverse engineering to find those.
and the patent may not be exactly what has been implemented.
Click to expand...
Click to collapse
have you looked in the tstril.zip archive on that page?
itsme said:
in tstril.zip from http://xda-developers.com/RIL/ there is a ril.lib file.
you can create it your self by running
Code:
lib /def:ril.def /machine:arm
the ril.h is far from complete. maybe someone has the time to copy
them from the patents.
the constants are more work, you need to do some reverse engineering to find those.
and the patent may not be exactly what has been implemented.
Click to expand...
Click to collapse
i looked for it ,but have no that page ...........
As a developer, I started to explorer more my device.
I created a small application to expose all RIL messages.
This app is still in development but feel free to use it.
Ideas are welcome.
Thanks.
RIL Lib
I found an update RIL.H.
I have updated the DEF file and created a new LIB file.
Note: I have updated DEF based on MSDN and not based on the H file. Maybe some reference to certain API are still missing on the H file.
Related
Hi!
There a lot of kitchens avaialable for ROM building. Now this one is to ease TouchFlo3D building.
This kitchen uses the knowledge and works of 6Fg8, D-MAN666, xboxmod, chainfire and many others who are involved in Manila hacking.
If you use this kitchen and/or any of the decompiled scripts then be so kind and share back the source code of your modified scripts too!
This kitchen (v1.5) has the following utilities included:
6Fg8's mode 9 editor (v3.3.0.1)
sztupy's mode9 converter (v1.0)
chainfire's CFC compressor (v0.46)
MKT: a tool for batch converting/compressing/compiling mode9,qtc,png,xml,lua files (v1.1)
LuaDec (2.0)
A work in progress lua and xml IDE
And various other tools
In the center of this kitchen stands MKT aka manila_kitchen_tool, which is like 'make' but for manila kitchen developement.
It has the following functionality:
split hased _manila files back to their original filenames
join a bunch of files in a directory back to their hashed form
mass decompile mode9 files back to xml and save their lua scripts
mass convert qtc files to/from png files
mass compile lua files
It works like 'make' in sense that only the modified files will be recompiled/recompressed so after the firts setup it might be ideal for manila development.
The output of the kitchen was tested with the Rhodium manila (WVGA version) on a HTC raphael device and it works, so this project is no longer a prototype, but is still considered beta stuff
Kitchen set up
I uploaded a complete Rhodium2 Manila kitchen in case you want to use that as a base (download both the kitchen and the rhodium files, then copy them to the same directory), but of course you can use any other manila pakcage you get across. To set up the kitchen copy the package into the 'pkg' directory then run:
Code:
mkt split
to split the hashed files back into their filenames. (For this conversion it uses the same table as m9editor uses.)
You will get a "bin" directory. This will hold all "compiled" stuff, so here you will find all the files that don't need more preprocessing, and can be hashed/installed to the device
Next you want to get some editable files out from the luac, mode9 and qtc files, so use:
Code:
mkt -x bin frommode9
To decompile mode9 files back to XML (it will also extract the scripts out of the package)
Next:
Code:
mkt -c d,qp fromqtc
or
mkt fromqtc
Will convert all qtc files to png files. (the first type will work on cfc compressed qtc files, the second will work on non cfc compressed files)
After this only the scripts are remaining. Unfortunately these can't be decompiled easily, so grap the decompilation of someone (like me ), and put these files into the "insrc" directory. After this run
Code:
mkt -d insrc -o src split
so all the hashed _manila files will be converted back to their original filenames to ease searching through them.
After this you're ready with your prepared kitchen. These things were already done with the Rhodium manila so you might use that package to start manila modding.
Compiling
You can use tomode9, compile and toqtc commands to compile these files back to their binary counterpart. Alternatively you can use:
Code:
mkt -c pq,c,p make
to run this three command after each other. It's like a Makefile, so it will only compile things that have changed. Of course you might want to 'make all':
Code:
mkt -a -c pq,c,p make
This will build all files from the "src" directory into the "bin" directory
Creating the package
After you're done you can use
Code:
mkt -o outdir join
to hash all files from the bin directory back to hashed form, and put it into the 'outdir' directory. Next add the binaries and you're ready to flash
Alternatively I included createpkg that will create a cab package from the OEM apckage found in the 'pkg' directory
Download and other stuff: http://winmo.sztupy.hu/manilakitchen.html
Sounds great! Downloading now. Thanks sztupy!
Yeah, good job sztupy, this will be a great addition.
nice...gotta buy a bigger house...so many kitchens
pcarvalho said:
nice...gotta buy a bigger house...so many kitchens :d
Click to expand...
Click to collapse
roflcopter
pcarvalho said:
nice...gotta buy a bigger house...so many kitchens
Click to expand...
Click to collapse
what you need is a microwave
sztupy said:
Missing functionality / bugs:
Embedded decompiled scripts can't be re-embedded into mode9 files automatically (this would need a command line mode9 editor
Click to expand...
Click to collapse
I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.
6Fg8 said:
I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.
Click to expand...
Click to collapse
I hoped so
unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...
sztupy said:
I hoped so
unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...
Click to expand...
Click to collapse
hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.
6Fg8 said:
hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.
Click to expand...
Click to collapse
your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine
And a command line CFC compressor is also needed
sztupy said:
your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine
And a command line CFC compressor is also needed
Click to expand...
Click to collapse
mode9 is basically binary XML, so i had no choice
The easiest way (at least for me) is byte positions just kidding ...
I'm on vacation next week, maybe i'll get struck by an ocean of light while skiing on one of the wonderful austrian mountains
CFC compressor .... I've that lying around somewhere here, shouldnt be a problem to adapt it.
an ambitious project... thank you
nice work great addition
Scripts update addon with the newest decompiled stuff.
Kitchen is now tested and considered BETA. Also added a great new tool: MKT to the kitchen. Read first post.
sztupy said:
Kitchen is now tested and considered BETA. Also added a great new tool: MKT to the kitchen. Read first post.
Click to expand...
Click to collapse
Just downloaded kitchen and getting ready to start playing. Just wondering, will this make a installable cab file for rhodium manila for touch pro? Of course with vga adapted files. I've noticed that previous attempts of making a cab for it have failed, but oem packages work when cooked in. I'm making a theme, which shouldn't require a full install, but would be nice to know.
showaco said:
Just downloaded kitchen and getting ready to start playing. Just wondering, will this make a installable cab file for rhodium manila for touch pro? Of course with vga adapted files. I've noticed that previous attempts of making a cab for it have failed, but oem packages work when cooked in. I'm making a theme, which shouldn't require a full install, but would be nice to know.
Click to expand...
Click to collapse
I tried to install it as a cab on NATF's ROM I'm using, and it worked flawlessly. It might break on a stock ROM though. The whole convert to cab thingy is alpha currently, but hopefully it will be solved.
sztupy, So how do you go about fixing the main function? I have the LUA file I've been working on done except for the main function and all the Q16.16 instances. But looking at the src.lua file, it appears chunks of the main are scattered throughout the file. Literally, I have code parts at the beginning of the file, in the middle and at the end of the file.
That's how the luadec output that you ran for me (because luadecguess was inaccurate) outputted the decompile.
So I'm stuck because I'm not sure how to proceed with fixing it. What do you do, just leave it where it's at and search for what it's referring to and fix it where you find it? Or do you cut/paste (move) it at the top of the src code in the order it's supposed to be in?
EDIT: never mind, left the code where it was and just searched out and fixed what it referenced. Other then the Q16.16 lines, everything is good.
Hi sztupy. Excellent work. Im poor and unemployed so although Id like to, I cant donate any cash at the moment. I like this project enough to offer body parts though, if any of yours fail
EDIT - bug report removed. was related to luaconv.exe. moving to another thread.
smotrs said:
sztupy, So how do you go about fixing the main function? I have the LUA file I've been working on done except for the main function and all the Q16.16 instances. But looking at the src.lua file, it appears chunks of the main are scattered throughout the file. Literally, I have code parts at the beginning of the file, in the middle and at the end of the file.
That's how the luadec output that you ran for me (because luadecguess was inaccurate) outputted the decompile.
So I'm stuck because I'm not sure how to proceed with fixing it. What do you do, just leave it where it's at and search for what it's referring to and fix it where you find it? Or do you cut/paste (move) it at the top of the src code in the order it's supposed to be in?
Click to expand...
Click to collapse
You can consider every function in the file as a value. It's just like a number or a string in this case, because in the main body you assign functions to some variables. So if you find something:
Code:
SomeStuff = function(foo)
lots of stuff
lots of stuff
lots of stuff
end
SomeOtherStuff = function(bar)
lots of stuff
lots of stuff
lots of stuff
end
Then in the main body this will translate to:
Code:
SomeStuff = funtion1
SomeOtherStuff = function2
And in the disassemlby to something like this:
Code:
R0 := Function(f1)
SomeStuff := R0
R0 := Function(f2)
SomeOtherStuff := R0
And of course the definitions of these functions will be put after the main body (just as with any other inlined function, the only exception is that compare/luadec and the other tools I made will handle these functions separately to ease decompiling). So if you have to fix the main body you have to only look at the part of the script which is not in a function...end body
Hi,
I'm currently working on a few tools, and want to know what features would be liked by cooks/users or anyone really.
The first tool is an exe generator for hot fixes. Simply put, you plug some files into it, and it generates an exe that can be run on the target device which will do all the hot fixes.
The advantages it gives:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Since it's written in native C++, it should run without a hitch on WM5+ devices, whether or not they have .Net whatever...
The second tool is an AutoRun/UC/whatever like system that simply searches through a folder, finds all cabs/xmls/provxmls and then installs them. This means there's no reliance on autorun for parsing config files, or any other requirements. Again, it's written in native C++ so is better
Any suggestions/ideas would be welcome!
Oh, and once I've got slightly further, both these will be released as open source. Probably.
l3v5y said:
Hi,
I'm currently working on a few tools, and want to know what features would be liked by cooks/users or anyone really.
The first tool is an exe generator for hot fixes. Simply put, you plug some files into it, and it generates an exe that can be run on the target device which will do all the hot fixes.
The advantages it gives:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Since it's written in native C++, it should run without a hitch on WM5+ devices, whether or not they have .Net whatever...
The second tool is an AutoRun/UC/whatever like system that simply searches through a folder, finds all cabs/xmls/provxmls and then installs them. This means there's no reliance on autorun for parsing config files, or any other requirements. Again, it's written in native C++ so is better
Any suggestions/ideas would be welcome!
Oh, and once I've got slightly further, both these will be released as open source. Probably.
Click to expand...
Click to collapse
Wow, this sounds very very promising. Can't wait!
dwizzy130
yeah some user friendly and easy to understand specialy editing the rom or making add/remove programs EASILY is the best specialy to noobs like me when cooking ROMS all in one tool with advance AI for error checking
Sounds very attractive. go on my friend.....
Sounds good mate
I'm looking for a tool to easily make a setup.dll. Like setup.dll maker/generator/wizard.
Seems the only tools I can ever found is from e-pocketsetup, but that company was sold to another company and the product was never available since then.
I know cooks hate a cabs with a setup.dll. But seems without setup.dll a cab installer can not execute some little complicated actions. And it is impossible to make a setup.dll without grasp a computer language like c++.
Edit: Found another one: setupdllcreator , but it's not strong enough and not freeware.
Edit: If these can be realized, a setup.dll maker is much less needed:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Click to expand...
Click to collapse
But we need above mentioned fubctionalities to be DYNAMIC, like:
Can detect availability of certain reg entries or installed apps, base on the result to decide which variants of install files to be installed, or whether some supporting apps like netcf or mortscript to be installed. Or can detect device id, resolutions, drivers to decide what to do.
Otherwise it still can not completely replace setup.dll.
But if dynamic actions can be executed, wow that's a dream of developers & hackers and even common users can benefit from that, a real revolution !
woww can wait for realese
l3v5y said:
Any suggestions/ideas would be welcome!
Click to expand...
Click to collapse
So I'm posting my requests again, the idea is this: It will be much helpful if I can know what is happening/changed in the registry after I did anything to my WM devices. So maybe you can develop a tool to monitor & log the real-time changes of registry. Or at least we can have a registry-comparision tool on ppc.
Another thing is it seems we don't have a file structure viewer on ppc, not the stuff like total commander etc., want to export the file structure to a file like .txt or .jpg.
Update: Now my idea is clearer for this, what I suggest would be a System Snopshot program to realize this:
Can make a system snapshot to record the registry content, file structure, ram usage etc.
The snapshot can be initialized in the similiar way of CapSure screen capture program, i.e., a hardwre button, a fixed time, a screen tap, a program launch, etc., defined by user.
Can choose a full system snapshot or only on selected part of registr, file system etc.
Can generate a file containing the recorded system condition.
Can compare any two system snapshot result and generate a comparision chart/change log.
So I've posted my requests as per your request, whether or not you'll do it is not my business lol.
Update: Found SK Tracker, cost EUR9.95, so forget this one. Why I did not know it in the past?!
I'm looking for a command line decompression utility for WM6.x platform. Unzip/unrar/uncab anything could be OK.
Anybody knows if such utility available?
tomal said:
I'm looking for a command line decompression utility for WM6.x platform. Unzip/unrar/uncab anything could be OK.
Anybody knows if such utility available?
Click to expand...
Click to collapse
idk if it can do EVERYTHING you want but try mortscript, it has built in winzip support and you can add winrar support to it also.
gzip, zip are easy to be implemented in .Net CF. Maybe will work for CAB also... for RAR no ideas.
you need this for scripting or to integrate in an application ? if it's for application you may find components available on the net, for scripts mortscript looks to be a good direction to look at...
I believe pocketrar (made by the winrar guys) does cmd line as well as gui.
Da_G said:
I believe pocketrar (made by the winrar guys) does cmd line as well as gui.
Click to expand...
Click to collapse
nice to know... thanks for the tip, will test it tomorrow (here is almost midnight) but should be nice to make my device downloading RAR files and uncompress them automatically (just need to automate rapidshare now lol *private joke*)
Thanx mate.
I'll try all of them. pocketrar should be nice if that really works for silent unpack.
The idea behind is: I want to integrate it into the kitchen process.
A list of files/packages will be packed during rom build and they will be unpacked only at first call/run of the associated application. But the unpack process should be silent and command line decompression is the best deal in my opinion....
i have heard lots of about mortscripts use,,
but plz can someone elaborate how??
like how can i add new taskbar icons??
how to create flder?
and finally where the hell to put it??
sorry..
if someone already know then plz give the link..
hi, mortscript is a scripting language
you can build a file with extension .mscr and when you double click it instructions will be executed. you can do anything with mortscript: write/read to registry/files, run programs, send commands to the operating systems, send events to the queue...
mortscript is a simple language so you can be up and running in little time. there is no GUI so it is a language very descriptive.
the program can be downloaded at the author's page. There is a complete and concise pdf manual.
in xda there is are two reference threads: mortscript examples acumulation and mortscript source compendium.
rather than ask for that or that code, learn by doing...the machine will do what you want to.
cruiserrr said:
hi, mortscript is a scripting language
you can build a file with extension .mscr and when you double click it instructions will be executed. You can do anything with mortscript: Write/read to registry/files, run programs, send commands to the operating systems, send events to the queue...
Mortscript is a simple language so you can be up and running in little time. There is no gui so it is a language very descriptive.
The program can be downloaded at the author's page. There is a complete and concise pdf manual.
In xda there is are two reference threads: Mortscript examples acumulation and mortscript source compendium.
Rather than ask for that or that code, learn by doing...the machine will do what you want to.
Click to expand...
Click to collapse
can i cook them??
Like wher i have to put them to execute???ext folder??shared folder or in folder with mname zzzz
Here's a mortscript package. Just put it in your EXT directory. As for the scripts themselves, do whatever you want. I use them during customization (unzipping; creating my start menu..), so you need to put the commands into an add2config.txt file. I also have a few that I use for backing up/restoring files, or exporting reg keys. I just have links to them in my start menu.
you can cook both the app (as says previous post) and the scripts you create or reuse. you can use scripts that build (or copy) the shortcuts at boot time or do anything you want. this is not a quick shot, I recommend you take some reading on mortscript, there is a lot here at xda.
thank u thank u all of u..
There is a WIKI with some examples too. See my Sig
RoryB said:
There is a WIKI with some examples too. See my Sig
Click to expand...
Click to collapse
and RoryB is another mortscript WIKI himself !!
Hi all!
I'm a fairly inexperienced one-man developer, and I'm looking to make my apps viewable in different languages, in order to increase its popularity/usefulness in other countries.
My apps are quite text-heavy, so ideally it could be as simple as re-directing to text files with the proper language included, but I honestly have NO idea and I haven't been able to find any step-by-step tutorials simple enough to make sense to me.
Can anyone here help? Or at least point me in the right direction?
Thanks.
Also, if this topic is in the wrong section, please feel free to move it....
You can use resources files in Visual Studio. Create a folder named AppLocalResources for just a folder in you project and a folder named App_GlobalResources for your entire solution. In this folders you can add a Resource file name like your objects. See more on MSDN
TrivialPanPan said:
You can use resources files in Visual Studio. Create a folder named AppLocalResources for just a folder in you project and a folder named App_GlobalResources for your entire solution. In this folders you can add a Resource file name like your objects. See more on MSDN
Click to expand...
Click to collapse
thanks for your help .
Here is a link in MSDN :
http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff637520(v=vs.105).aspx
hope to help you