Hmmm...
Yes I know, again stupid Question.
Why we can not use SHW-M130K "Modem" or part from it?
S8500 not start ?
S8500 explode ?
Any Logfiles exists?
Later I will write more... need to check again SHW-M130K files and JTAG Dump...
Its long long time ago...
Best Regards
It's so old... I have forgotten where my files stored.
http://forum.xda-developers.com/showthread.php?t=1133736
Here seems Firmware still active for SHW-M130K...
http://pspmaster.tistory.com/48
I have forgotten which files inside...
In bada Firmware amss.bin is mandatory file for Call.
This files is huge, more then 12 MB...
If you write own Code, then you know why I wrote huge... for 12 MB...
Samsung Android handset need file modem.bin...
Don't punish me, if wrong name...
In actual bada Android Port... modem.bin is complete DISABLED/or ignored by zImage ...
SHW_M130K_0x00000000_OK.rar this is JTAG dump I have for study...
No idea, if I remember correct, modem.bin from SHW-M130K is near 7 or 10 MB...
Damn, if I find my files I know it correct...
Best Regards
Short checked I9000 Firmware...
But here is baseband from Infineon... instead Qualcomm...
modem.bin is bigger then 12 MB...
I have taken this one for "research"...
GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip
Now I will download SHW-M130K WC21 from here:
http://pspmaster.tistory.com/48
Soon more ...
Best Regards
adfree said:
Short checked I9000 Firmware...
But here is baseband from Infineon... instead Qualcomm...
modem.bin is bigger then 12 MB...
I have taken this one for "research"...
GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip
Now I will download SHW-M130K WC21 from here:
http://pspmaster.tistory.com/48
Soon more ...
Best Regards
Click to expand...
Click to collapse
I really wish i learn to develop softwares nt unfortunately nt nw... So jst tell me in plain words gud news r bad news...i think u shud check for oldr samsung android phones....
M130K-HOME-GB-REV04-WC21
Short checked...
modem.bin bigger then 15 MB...
This time it is Qualcomm related... and also QSC6270...
Next...
For AMSS, this is your Modem... you need NVM knowledge...
NV items is also NO Kindergarten...
Minimum knowledge is Qualcomm related Tools like QPST and if more advanced. Then QXDM...
http://forum.xda-developers.com/showthread.php?t=899023
So you need advanced users with deep Qualcomm knowledge about AMSS, NVM... for instance like our pro Unlockers... GSM...
No Link to forum...
But this Forum is nice... Maybe you find here ""enough"" stuff for study.
http://www.finetopix.com/
Here are smart users with deeper knowledge...
Best Regards
Summary...
For successfully Modem integration you need expertS with:
- deep Qualcomm knowledge about AMSS, RF, NV...
this include working with Tools like QXDM...
- coding skills alone are nice... but not enough to manage all problems...
As modem.bin is 10 MB of perfect matching data... this is like rocket science.
This means many years of experiences in this GSM/CDMA business...
So in my opinion we have at the moment nobody... who can finish this in 2012...
1 man can't finish this...
Best Regards
QXDM overview from Qualcomm
Feel free to clicking around.
https://support.cdmatech.com/qxdm/1_START_HERE.htm
Here Call related...
https://support.cdmatech.com/qxdm/CallManager/CallManagerindex.htm
Here some NV...
https://support.cdmatech.com/qxdm/NVbrowser/NVindex.htm
Now maybe you can understand, how complex AMSS/Modem is...
Best Regards
https://jobs.qualcomm.com/public/jobDetails.xhtml?requisitionId=1888000&page=jobSearch
Such users we need also.
Embedded Software Engineer - GSM/EDGE Modem Physical Layer
Click to expand...
Click to collapse
http://www.qualcomm.com/careers
Clicking around and you will see. How long some jobs require...
3 years of experience...
Maybe after 3 years we will have someone, who is able to finish succesfull Modem functionality...
Maybe someone is able to make visible progress in 2013.
After hard, hard, hard learning process...
Best Regards
after seeing all this i have lost hopes for modem. drivers to be written from scratch.
only hope is that some modification of other android modem.bin gets fit to our modem.
or else we can hope for an optimised 3.3 inch android tab.
god bless wave.
Yes,its seems that modem writing is not an easy job...
especially for 1 person...
anyways,Adfree...u did a fantastic job by finding all this stuff...
only hope is with some trick or shortcut by which we can modify some other android modem...(my weird thought)
but for now,well done
Regards,
WaveGuru
http://www.youtube.com/watch?v=IWSCdpAeONA
Found this here:
http://code.google.com/p/docl4amss/wiki/ReferencePage
Btw...
Someone has this Doc found ?
80-VE263-25-MSM7200A-BasebandTopics.pdf
And normally for each Qualcomm Chip...
Full AMSS Source Code exists...
Several hundret MB...
Maybe someone has found something... MSM6xxx or older ?
Pudn is very good site to find interessting stuff...
Best Regards
http://bb.osmocom.org/trac/
OsmocomBB is an Free Software / Open Source GSM Baseband software implementation.
It intends to completely replace the need for a proprietary GSM baseband software, such as
drivers for the GSM analog and digital baseband (integrated and external) peripherals
the GSM phone-side protocol stack, from layer 1 up to layer 3
In short: By using OsmocomBB on a compatible phone, you are able to make and receive phone calls, send and receive SMS, etc. based on Free Software only.
Over the past 12 months, we've been making very good progress. Most of the hardware drivers have been written, and a relatively complete layer1, layer2 and layer3 exist.
No work has yet been done on any sort of UI on the phone. The only user interface is a telnet-based command line.
Click to expand...
Click to collapse
Our chipset is not listet... but maybe interesting for research...
Best Regards
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
Actually Oleg used some modem.bin and it seems like it worked but
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something. My battery seems to be pretty well "worn out" and my fuel gauge totally decalibrated, it keeps showing fake values all the time and at all my battery keeps power for ~20hours, I will put a warning in kernel thread.
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
Click to expand...
Click to collapse
There are few Fake IMEI... kind of "Emergency IMEI" somewhere in AMSS...
In theory we can have all the same IMEI for Calling...
I remember from my AMSS journey from 2006... QC Standard IMEI bla...bla
Will look into my old stuff...
Also I think we have enough space... to create more NV items...
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
I know few sources... but never seen complete AMSS package...
Also my brain is tooooo small to use these sources for something usefull.
I need this only for my QC collection. :angel:
Best Regards
http://blog.csdn.net/yili_xie/article/details/5656608#comments
Here seems few QC related infos... maybe more...
Request to other users.
Please.
1.
I need AMSS source for Download.
No idea, 300 or 400 MB ZIP or more...
Maybe this is something in this kind... Google Power. :angel:
https://www.codeaurora.org/git/proj...ions/db2575e163152f681668800744c99f287f77a8ef
Best Regards
How about Samsung Galaxy 3 I5800 ?
004400152020000
This is IMEI from SXG75, EF81, SL91 ... handset from 2006 with MSM6250...
If NV item 550 was lost/empty/blocked...
There are hundrets of such devices...
Also this IMEI can be found on other manufacturer, if QC AMSS...
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
Click to expand...
Click to collapse
For Android you could define new NV ID for IMEI... instead NV 550...
Best Regards
Rebellos said:
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
Actually Oleg used some modem.bin and it seems like it worked but
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something. My battery seems to be pretty well "worn out" and my fuel gauge totally decalibrated, it keeps showing fake values all the time and at all my battery keeps power for ~20hours, I will put a warning in kernel thread.
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
and what about tablet like this
http://www.androidtoitaly.com/goods.php?id=368
or this
http://it.aliexpress.com/product-fm/591540997-2012-new-android-tablet-sim-card-slot-wholesalers.html
they also have QSC6270...
also many renesas tablet have QSC6270, here some firmware/skd
http://www.chinadigitalcomm.com/opa...enesas-android-tablet-pc-firmware-t10398.html
Rebellos said:
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
...
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something.
...
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
Rebellos, the modem control the battery? or them is related someway? kinda creepy
How to edit AMSS.bin or Modem.bin??
Hi
Could anybody point me in the direction of sourcing, locating and compiling a kernel module please? I have found many guides but they all seem to start halfway in the process ("assuming you have already managed to...", "assuming you are already proficient with...")
I have a cheap Android Chinese TV box. It came without joydev.ko so I can't use it with joypads/sticks, which is a pretty big limitation considering it has 4 usb ports which work fine with keyboards, mice and webcams.
I already have an Eclipse environemt set up which I use for Java/Android development but I've never dabbled with anything like this before.
I guess the steps required are something like this:
Locate source code for my particular Android version (Android 4.2.2, Kernel 3.3.0) - where do I do that? Do I need the entire source or can I just download and compile the module by itself?
Set up the cross compiler - is this a standard thing, or does it depend on my hardware? My chipset is an Allwinner A20 ARM Cortex-A7(Dual Core)
Compile the module.
So, have I got the steps right? If not, please correct me. If so.... how do I go about doing the above?
Hello everybody,
I have the new Clio 4 Medianav system, is based on WinCe 6.0 embedded, i found a lot of application for this windows system...but the majority parts is for ARM processor :crying:
Can you help find me MIPS application?
Offtopic:
I would like to try programming on wince but I have no idea how set visual studio 2008 for do it..
I usually program website, PLC and microprocessor PIC... I know what does it mean the "Programming" word :angel: )
Thank you!
forna91 said:
Hello everybody,
I have the new Clio 4 Medianav system, is based on WinCe 6.0 embedded, i found a lot of application for this windows system...but the majority parts is for ARM processor :crying:
Can you help find me MIPS application?
Click to expand...
Click to collapse
Who should spend the time? DIY!
Just for info:
Windows CE isn't a desktop OS where peripherals use a common set of busses and addresses and a single OS build that knows how to integrate all of these. There isn't a "Windows CE Image" for just any given processor, the OS image must be built for your exact hardware. Memory maps, peripherals, drivers and a load of other things can change from board to board, even with the same processor.
These "differences" are encapsulated in what's known as a BSP or board support package. You generally must have that for your target hardware, then you can generate a new OS image containing the OS features you want for that hardware.
The short of this is, that no one can tell you whether there are applications out there that are compatible with the OS image used on your Medianav system.
Windows CE for devices with ARM CPU is standarized, because the underlaying hardware is mostly identical. So hundreds of applications for this OS image exist. And it's very easy to write your own.
jwoegerbauer said:
Who should spend the time? DIY!
The short of this is, that no one can tell you whether there are applications out there that are compatible with the OS image used on your Medianav system.
Windows CE for devices with ARM CPU is standarized, because the underlaying hardware is mostly identical. So hundreds of applications for this OS image exist. And it's very easy to write your own.
Click to expand...
Click to collapse
I found the technical datasheet of motherboard with cpu processor type and all the hardware (cpu is a AU1320 all exe are programmed for an R4000 cpu) but the problem is one...I'am a noob on windows embedded..I would like to learn it bit I don't think to find too many people who wants teach me it :crying:
forna91 said:
I'am a noob on windows embedded..I would like to learn it
Click to expand...
Click to collapse
Perhaps this Microsoft book
https://www.microsoft.com/learning/en-us/book.aspx?id=11064
takes you one step further.
This practical, authoritative, popular reference now in its fourth edition shows developers how to develop applications for the newest generation of mobile and embedded devices. Focusing on the core operating system of Windows Embedded CE 6.0, this guide covers memory management, files and file systems, registries, databases, notifications, communications, and more. It s based on the author s extensive experience training developers focused on embedded technologies how to use Windows CE to its fullest capabilities, and covers the latest features in Windows Embedded CE 6.0. The book includes a link to a companion Web site with extensive sample applications in Visual C++.
Thank you for this book...now I see if buy it
There are lots of older MIPS apps (CE 3 and older) that can work. A lot of info and many downloads can be found at hpcfactor.com. I have two MIPS devices using a similar processor (Au1250) and a slightly older OS (CE 5.0): the Viliv X5 and Cowon P5, about which I have posted threads in the Windows CE 5.0 section of hpcfactor.com. (I can't post the links because I'm still considered a newbie here, but just go to the forum list on hpcfactor.com and you'll see that section.)
Because a lot of apps in the Windows Mobile forums here at xda-developers.com were written for the .NET Compact Framework 2.0 and 3.5, installing MIPS versions of .NET CF 2.0 or 3.5 (if they are not already installed on your device) may allow many of those apps to work on your device as well. There's some discussion of this as well in the two threads I mentioned above. (Check which version of .NET CF is on it already first, though. If it has 2.0 already, after installing 3.5 make sure that both versions are activated in the registry under HKEY_LOCAL_MACHINE/Software/Microsoft/.NET Compact Framework.)
well thank you for that site!! I found now a regedit...tomorrow i try it because others don't works :crying: fortunatly there is a debug usb in the radio and with visual studio I think that we can read it :good:
Have you had any succes on doing so? I also have the MediaNav Evolution system (v9.1.4) and I have something in mind... But im totally lost!
P.S.: Would you mind sharing the technical datasheet of the motherboard and CPU?
Hi Folks,
I'm not sure exactly where to put this question but here goes. It looks like my monitor (HannsG HT231HPB) touch screen capabilities are not supported by default by my TV box (Stoga Kbox MXIII Amlogic S802) and I want to get it going. I'm not really interested in maintaining functionality of this TV box. My objective it to get an app that needs android 4.2 or above to run on it in conjunction with my touch screen. The app uses a touch screen to control music software. I have numerous questions as follows.
1) If I need to alter a couple of lines of code of existing parts of the kernel is there a way to inject these updated changes i.e. update ko files or something?
2) If this is not possible can I compile and update just the kernel or a module?
3) If I've got to recompile the whole lot, bearing in mind I don't need the existing functionality of the software on the TV box, can I just use the basic Android OS such as Kitkat and just worry about what I need just to run app, touch screen and USB.
4) If that is not possible how likely are similar source codes for devices likely to run on another device. There are various incarnations of MXIII boxes and I can't find the source code that seems specific to my box.
5) Any other ideas!
I know this is a bit general and convoluted but I've already wasted a lot of time on this and could do with reducing options.
Thanks in advance
Mark
Hi
Did U find something to make it works ?
I've the same configuration (MXIII + HANSSG HT231) and impossible to use touchscreen.
Thanx for your help
MacCarel said:
Hi
Did U find something to make it works ?
I've the same configuration (MXIII + HANSSG HT231) and impossible to use touchscreen.
Thanx for your help
Click to expand...
Click to collapse
No in short. I think the problem is a couple of lines of the Kernel. If they are not there you will get no reaction on touchscreen no matter what you try. The only solution is to alter a couple those lines of code and rebuild/compile the kernel. Therefore you need a compatible kernel for device and work out how to do this. I've stopped trying for now but I was looking at trying to find a custom ROM based on a different compatible kernel and hope it has support built into kernel automatically. Good luck..
Hi there,
I want to port a Lollipop ROM to an Android device which has only a KitKat ROM. In order to find the fitting Lollipop drivers, I would like to know the exact HW specs (like cam, display, WiFi+BT, GPS, etc..). Then I plan to inject these driver files in the template LP ROM.
So I had the idea I could find out the exact HW specs by disassembling the libraries from the base ROM. So I checked several files (libcam.so, wifi... .so, etc.) in the base KK ROM, but could not find any hints.
Can anybody help me, how I can identify the exact HW of the critical components by the ROM?
Thanks in advance!
Nobody an idea?