Hi all,
Thanks to itsme's code here, i managed to get the RIL functions working:
Getting signal strength etc... works, however, RIL_GetCellTowerInfo() doesn't.
So I tried through AT-commands, as shown by itsme's second piece of code here. The AT commands, given through the RIL_DevSpecific() command seem to work, they give me a result callback. However, lpData points out to be 0 after a "at+creg=2"(26) in this reply? Shouldn't it point me to a celltowerinfo structure or an array of some kind like RIL_GetCellTowerInfo() does?
Calling RIL_GetCellTowerInfo() after issuing the AT-commands still gives me an error reply.
Is there anyone with experience on this subject, or who has succeeded in this on the Alpine with Windows Mobile 2003 SE? I've been on this for a few days now, any help would be much appreciated. Could it be that it just isn't supported? And in that case, is there another way of getting the Cell ID? Source snippet attached.
Kind Regards,
xgmorkx
The fnGetCell function from this post seems to do the trick! Gonna walk some blocks now to see if it changes
try this one:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
files to download:
MDA AT
mdaatcom.dll
mdaGetCellDll.dll
Homepage:
http://develop.ipeng.de
more info on->
http://www.spv-developers.com/forum/showthread.php?t=229[/url]
will this work on a blue angel?
Sample App to get cell id
I tried to download the tsril.cpp and make a project to work on my iPaq Pocket Pc Phone edition, but the ril.lib I have must be bad. The compile shows the following link errors:
CellRill.obj : error LNK2019: unresolved external symbol _RIL_DevSpecific referenced in function "bool __cdecl EnableCellBroadcasts(bool)" ([email protected]@[email protected])
CellRill.obj : error LNK2019: unresolved external symbol _RIL_GetCellTowerInfo referenced in function "bool __cdecl RequestCellTowerInfo(void)" ([email protected]@YA_NXZ)
CellRill.obj : error LNK2019: unresolved external symbol _RIL_Initialize referenced in function "unsigned long __cdecl DoRIL(void *)" ([email protected]@[email protected])
emulatorDbg/CellRil.exe : fatal error LNK1120: 3 unresolved externals
please help
:roll:
WIN32 mode
I got past the link problems and run the code, I print out the errors using DoError function contained in the tsril.cpp sample code.
It tells me that the following functions are only availiable in WIN32 mode ?
EnableCellID
RequestCellTowerInfo
Any ideas what this means and how to get around it, I need to get this Cell ID.
Related
Hi !
i tried to read my saved 3.14-ger rom from my SD card (saved as boot+ce)... but XDArit (new version) says: Did not find correct flash signature, aborting!
Why ? what did i do wrong?
Jabba
what does it display in the first page ?
does it start with 'HTC$WALLABY' ( if so what number follows? )
or does it say 'FLASH KEY'
or does it say 'FAT16'
nothing was displayed.
was very weird... i installed some win2k-drivers on my winxp for the sd-card, now it works !
my one see FAT16 it not 'HTC$WALLABY' WHAT I MAKE WRONG >?
WHAT ARE U MORE INSTALL ON TO XP ? PLEASE TELL ME I NEED TO FIX THIS PROBLME TOO
if you see 'fat16' that means your sd card is still formatted for normal use.
after xdarit or your bootloader have written data to your sd card,
you will see 'HTC$WALLABY' in the first bytes.
the 'FLASH KEY' is what you would see with bootloader 5.17, I am not sure
if xdarit supports this correctly.
I didn't need to install anything on XP, I just plugged a usb cardreader
in my pc, you see some popups about windows finding new hardware, and drivers. and after about 1 minute it worked.
the new ver 1.2 of XDArit.exe
when i use it Write a image to sd card,it 's return a error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same Here
I get the same message in XDArit.,
Also. recently installed the latest program A update 3.17 from O2 to my UK XDA all went well, then (before I discovered this website!!) I foolishly (it now seems) went to the Program B uprade. this hubg up in mid flash!!
Now my poor XDA is in a sorry condition does wird and wonderful things, random backlight on off, responds to ocasional button pushes.
where can I get the GSM ROM to flash into it?
I also receive XDARite error with version 1.0.2.....
I have tried three different card readers and all of them give me this error....
Todd
Hi!
Do you know if there is a working x86 emulator for our pocket PC devices?
I don't need speed, just compatibility. I'd like to use some special tiny program, that was written for windows 95, on my Wizzard.
I know some guys were installing some old "ordinary" windows on pocket pc devices, so there should be hope for me?
any information welcomed.
greetings from slovenia!
Admit it, you just want to play Star Flight.... I miss that game
Mamaich has a working version of Bochs I think, on his website. However, I don't think you'll get windows installed.
Where have you seen old windows binaries running on the PDA?
V
Veloxi on the WM platform...I'd buy that for a dollar!
I just have to add this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this:
V
I saw a russian site where they guy had a dos emulator. but I do not belive it emulated the hardware needed for Win95. You are better off with a terminal service session on WinVNC, which I ise from my phone to a server in my data center.
I found this site (in German) showing pics of working windows 95 on a PPC:
http://people.freenet.de/renmi/ppc/
now we just have to find some manual describing how to do that
best
LOL...that looks cool but man, that has to be slow! Should be interesting to see what comes of it.
Guys, you can see that it says that it uses Bochs. As I said above, I think Mamaich has a release of it, or at least it should be generally available. That's a free, open source x86 emulator.
V
bochs - failure
hi. I am trying to play with bochs and dlxlinux
I have downloaded everything needed [except bochscr.txt - cant find it] but I think bochsrc.bxrc included with dlxlinux is good for me.
when I try to run it from dos box [functionality of pocket contoller] cpu grows to 100% for 1-2 sec and falls back to normal[0-3%].
every configuration I try cause same effect. on dos box nothing happens. no log produced [it is in configuration].
any ideas? anyone tryed it with success?
I run it with ..\bochs -q -f bochsrc.bxrc. ofcourse all files are correct.
Files are from http://mamaich.uni.cc/fr_pocket.htm
Hello,
A while ago I've managed to cross-compile a basic web server, resulting in a native ARM executable (you can find it here) that allows any other device to connect to port 80 (or whatever) and browse the contents of the phone.
Easy to exchange photos at a cafeteria which has wifi and both phones are connected - for example. No need for an FTP client, slow bluetooth, and so on...
However, I wanted more and since webserver was only handling GET (no POST / no CGI), I've started looking for an alternative that did the job.
Below, you will find a native ARM executable of micro-httpd, a light weight web server that supports CGI.
Download
Use it at your own risk!
mini_httpd_1.19.arm.tar.gz
It supports .htpasswd files to restrict access to folders - and it comes also with its own utility htpasswd which manipulates the password files.
micro-httpd website: http://www.acme.com/software/mini_httpd/
micro-httpd configuration options: http://manpages.ubuntu.com/manpages/maverick/man8/mini-httpd.8.html
You can use almost any CGI interpreter you want, minus PHP. The PHP 4 Android (a native implementation of PHP) has only CLI (command line support) and even if you could change the PHP code of the scripts to output the missing headers. BUT! It also outputs debug messages that you cannot control, in the output of the script!
Those messages are are considered errors in HTTP / CGI.
The creators of PHP interpreter say that is only meant for Scripting Languages for Android (SL4A) which works with what they have. You can read more here: http://groups.google.com/group/php-for-android/browse_thread/thread/79d0b5f856189675?pli=1. This topic also mentions an alternative (CGI this time) from GroomDroid but that is also unstable.
Enter PERL!
I had good success with Perl 4 Android
I can how host a blog on my phone - I've set up a big tutorial on how to configure everything here Running native CGI scripts (perl) with micro-httpd on Android.
Result
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next step would be to try out a file manager and test file upload, then go even deeper to see if I can access various phone details and offer a sort of management interface for them on the web.
Source code
You will find the source code and the license (free) on the tutorial website above.
Seems interesting !
Description
Once, I was playing with a number of Chinese tablets and trying different ROMs on them as they are technically the same hardware (HSG X5A variants).
I've had some problems getting the hard buttons to work though, so I wrote this application to detect key events and print them out. It will print out the following:
KeyEvents: The KeyEvents as Android understands them (KeyUp, KeyDown, KeyLongPress, KeyMultiple)
LogCat: Any relevant messages in logcat. Its filtered based on keywords declared in arrays.xml
Kernel: Any relevant messages in the kernel log. Its filtered based on keywords declared in arrays.xml. Kernel log parsing needs root.
The three checkboxes at the top control what information will be displayed.
This is a personal debug tool, but I hope it will be of some use to someone else.
No Ads.
Notes
While the application is running, the only "hard" keys which should work is "Home" and power. All others will produce their keycodes.
The SU request is to read the kernel log, so I can check if any keyevents are thrown by the kernel.
The location of keylayout files in Android is /system/usr/keylayout.
Kernel log parsing needs root
Both logcat and kernel log monitoring will only display lines containing words from two arrays in arrays.xml (i.e. you need to recompile the app to change them at the moment)
Currently the filters are:
Logcat:
HwGPIOE->GPDA
keycode
keycharacter
Kernel:
HwGPIOE->GPDA
keycode
keycharacter
Permissions
READ_LOGS: Used to access the Logcat log.
WRITE_EXTERNAL_STORAGE: Used to write the exported data to the SD card.
Changelog
v0.0.1: First public release.
v0.0.2: Improved stability, added Exit button.
v0.0.3: Code updates.
v0.0.4: Changed drawables, added sharing, added more info in export text
Acknowledgements
Original icon by OCAL (http://www.clker.com/clipart-style-paintbrush.html).
Licence
Licensed under the Apache Licence 2.0: http://www.apache.org/licenses/LICENSE-2.0.txt
Links
Market link: https://market.android.com/details?id=aws.apps.keyeventdisplay
Webpage: http://aschillings.co.uk/html/keyevent_display.html
Github: https://github.com/alt236/KeyEvent-Display---Android
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
|
This could be handy for anyone trying to redesign an apple BT keyboard for use with Android.
Smali Viewer(“SV”) is a free APK analysis software, regardless of the depth or breadth of analysis from the point of view, are designed to meet user needs, making the process in the APK in your analysis , more handy.
SV for Android mobile smart device applications APK files reverse , for the analysis of mobile application software code , using a variety of methods to determine the suspected samples for screening , such as certificate information , permissions information sensitive SP number information , Android Manifest , the function flowchart (CFG), a string table resource file information, sensitive information behavior , dynamic behavior , and so comprehensive determination .
Operating Environment:
Need to install java 1.7 and above
Installation:
Download SmaliViewer.Zip package, extract the installation directory in the specified folder open SmaliViewer .
Start method :
Click SmaliViewer.bat under windows system to run the program ; under Linux Click SmaliViewer.sh run the program. The first time you run the program , agree to " user agreement ."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2 Workspace
View the work area through the operation menu and shortcut menu , you can open the following eight working window , the window through which eight kinds of work , to show you the results of the analysis contained SV depth and breadth of the APK 's :
Work area is divided into four regions, see the following picture :
1 - menus and toolbars .
2 - the main work area .
3 - Operation log and status display area.
4 - class structure display area.
5 - member list display area
We are committed to APK analysis,and want to make APK analysis easyer.
Welcome to download it & Send your suggestions to us
DOWNLOAD:http://blog.avlyun.com/wp-content/uploads/2014/04/SmaliViewer.zip
Contact us:
Email address: [email protected]