See this...
xxx.youtube.com/watch?v=b_vCp7gj7W8
Does this mean something?
maybe it will give you guys some ideas...
I guess there is a way to do this, but maybe need change some codes...
In the PSfreedom wiki I see a lot of devices compatibles yet, including Nokia, Palm and HTC phones.
We need a guy with the knowledge to make this port for the Kaiser, and here is the most probable place to find him!
Port kernel psfreedom on HTC Kaiser
Hello;
I also have a Kaiser with the Kaiser rom CyanogenMod 6 [RLS5.2] and kernel-kaisimg panel2-240x320-2.6.32-tilt-froyo-02-09-10_16.nbh.
But when I try to load the module with "insmod psfreedom.ko su", you get an error "insmod: can not insert 'psfredom.ko': invalid module format".
I wonder if someone could not compile a kernel with the module in order to load the module to the application.
a developer want to try?
How much of the source is device specific?
Very little is device specific, you basically need to implement two very small functions, the problem is getting these two functions to work!
[edit] How hard is it to port it to a new device ?
The device specific code is separated from the core so it’s quite easy, there are mainly two functions to write, one to get and one to set the USB address.. two other functions that only return some static result depending on the configuration of the controller (the name of the endpoints, and whether the controller supports high speed or full speed mode). The real problem is that some controllers can be tricky and may not work as you would expect...
Read the README file provided with PSFreedom, and check the psfreedom_machine.c file for specifics on what to implement.
[edit] How can I port it to a new device ?
First, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’, you can use the ControllerList to help you, if it doesn't, then extend it!
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL and HIGH speeds are both unavailable.
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it… If the controller you are porting to doesn't have an endpoint matching the endpoint description requested, then you are allowed to return a different endpoint as long as you properly modify the endpoint description to set the bEndpointAddress to the correct address address of the new endpoint (but you still have to respect the direction of the endpoint of course!)
Click to expand...
Click to collapse
://psfreedom.com/wiki/index.php?title=FAQ
I spent some time working on this. I am sure it is possible.
I think there are two things that would have to happen.
1. A custom kernel. - I know there are a few things that must be disabled in the kernel. ADB USB Functionality, USB Mass Storage Functionality, Tethering, and on some devices WiFI. (I forget where I read that these must be disabled, but I did read it)
2. Changes to the code.
I am no expert at this, I think I am proficient at doing SOME things. I created a zImage last night. I know I am missing something tried to create a custom NBH and put it on my kaiser no go.
So, think I'll be spending more time on this. Anyone had any luck working on this at all?
UPDATE:
I did some pocking around, this is what I found in msm72k_udc.c for the closest thing to SET_ADDRESS (It was USB_REQ_SET_ADDRESS)
Code:
writel((ctl.wValue << 25) | (1 << 24), USB_DEVICEADDR);
I will be honest unsure if this is the driver for the controller due to the fact that on the device the usb driver is msm_hsusb. However, I tend to be wrong more than I am right so....
This phone is capable of it i'm sure. I just tried every other psfreedom releases and experienced different behaviours with each one of them. Though i know that zImage needs to be modified. I'm no programmer so i can't really help anyone with this.
So let's hope someone work something out.
OK I think It is not the msm72k but the msm_hsusb, when you look at the device it shows that in the usb driver folder.
Based on the psfreedom site is "in progress". Hopefully someone smarter than I is working it bc dont think Ill get far.
i'm looking for a tytn2 port too! Thanks for all of you that's working for it.
sugestion...maybe put this thread as an official for psfreedom kaiser info?
thanks!
diamond port finished http://wiki.psfreedom.com/wiki/HTC_Raphael
this version can help for kaiser porting?
Yep as far as i know this is a good start...
Hi guys just passing by to show you something...
http://xdandroid.com/wiki/Supported_Devices
This android port works with kaiser as you can see in the compatibility table.
Is there anyone who's able to modify zImage for us?
I think we're getting close. The only problem so far is the usb driver.
Come on guys you can do it!
don't work on kaiser, kaiser is tilt no tilt2
pavo87 said:
don't work on kaiser, kaiser is tilt no tilt2
Click to expand...
Click to collapse
Oh man can someone remove number 2 from that table please just so i can sleep well tonight?
lol
but there are someone that is working on the porting?
sorry for my bad english
There is someone working on the msm_hsusb usb driver yes.
Let's wait and see
I think the usb on kaiser working.. mean someone tell me it work on linux.. but in WXP can it fork too I think.. someone can use usb on W7 x64. But I can't get it work there...
Can anyone tel me how get it fully work on W7 x64? Thanks
Sent from my HTC Kaiser Ion using XDA App
come on guys, u can do it!!!!!
Is still on development?, or nobody will continue?, its a shame, kaiser is very usefull on android Roms, maybe is not that easy to port.
By te way, is a port for HERO on the wiki, and kaiser runs several roms from Hero smartphone, is this useful?
http://wiki.psfreedom.com/wiki/Device_compatibility_list
Regards.
msm_hsusb is just an other driver for the MSM72K controller, which is used in older kernels.
http://wiki.psfreedom.com/wiki/Device_compatibility_list
Milmirex said:
By te way, is a port for HERO on the wiki, and kaiser runs several roms from Hero smartphone, is this useful?
Click to expand...
Click to collapse
I think so but we need a kind soul who can edit zImage for us to boot it with Haret...
Related
Is there way to use the native WM5 "Device Lock" function directly used by quickapp.exe? I would like to call it directly via path...
I know there are great addon execs allowing to lock the device for certain conditions like "Yet another device lock application" :?
http://forum.xda-developers.com/viewtopic.php?t=45953&highlight=device+lock
Any help appreciated.
Thanks,
m.
What do you want to do, lock by command line?
I think my old version, VJDeviceLock, does that. Just launch it from any launcher and it should lock.
On my website or here:
http://forum.xda-developers.com/viewtopic.php?t=45851
V
Hi vijay555,
Thank you for your reply! I am currently using VJDeviceLock
and forgot to mention it... Besides it works like a charm
I am just curious if there is a WM5 supported/possible command line way?
Reading the forum comments I guess not...
There probably is a way, programatically. I remember it can also be enabled by a certain keypress, although I forgot which one. I foudn this out with VJKeyPress
My Mio A701 comes with an app like VJDeviceLock that enables the lock in the same way. I'll have to reverse engineer it one day.
V
Thanks for your help...
Damn. Got a new test device Samsung SGH-i320 w. WM5. VJDeviceLock does not seem to work any longer: "Installation of vjdevicelock.cab was unsuccessful. The installation file is not intended for this device." :roll:
Hi vijay555,
Do you have any planned betas of VJDeviceLock / modified CAB. that runs on my Samsung WM5?
Thanks,
m.
muck3d: unfortunately I don't have access to the device, so can't develop specifically for it - although I would love to support it. If you know where there's a rom dump, that might get me started, but otherwise, I can't promise any time frame for now
If you feel competent to do a bit of (safe) system hacking, you might be able to help me get something working... PM me if you think you could help out.
V
After a long period of very use of my trinity , updated to the various updated ROMs, used to have a lot of power in my hands and a lot of applications and functions , now my Boss force me to use , as separate device , a blavkberry 8700 .
What a stupid device is it in comparison !!
I read some thread about BBconnect , but could anybody help to find the way to install what need into my trinity to ADD it the Blackberry performance , transferring in only 1 device all my needs?
Thanks for your help , comment , info
HELP
Really ANY answer nor comment ?
Thanks....
tower5 said:
Really ANY answer nor comment ?
Thanks....
Click to expand...
Click to collapse
I'm in the same situation...I tryes BBConnect, but it makes the Trinity too slow...and furthermore I didn't get the appropriate account set up, in fact no way to sync with MS xchange...
It would be great having a fast way to "replicate" the account from my BB...and dismiss it 4ever!
Anyone else?
I tried BBConnect 4.0 without success, i missed to activate the option on sim card.
androme said:
I tried BBConnect 4.0 without success, i missed to activate the option on sim card.
Click to expand...
Click to collapse
why won't it work?
BBConnect 4.0 should be available for download from the carriers.
Will your IT staff let you?
tower5 said:
After a long period of very use of my trinity , updated to the various updated ROMs, used to have a lot of power in my hands and a lot of applications and functions , now my Boss force me to use , as separate device , a blavkberry 8700 .
What a stupid device is it in comparison !!
I read some thread about BBconnect , but could anybody help to find the way to install what need into my trinity to ADD it the Blackberry performance , transferring in only 1 device all my needs?
Thanks for your help , comment , info
Click to expand...
Click to collapse
Have you confirmed with your internal technology straff that they will allow you to use a non-Blackberry device with the Blackberry service? I know there are now ways to use non-Blackberry devices with the Blackberry service (even if they don't work well), but your internal IT people will have to configure your account to do so.
I asked my IT people to do that for me and they completely refused. The reason they use Blackberry (instead of Microsoft exchange, etc.) is because with Blackberry, they have total control over how I use my Blackberry, so they can close any security holes and otherwise restrict my use of the device. For example, we can't use the SD card on our phones, can't use Messaging, and can only use the Blackberry browser for the Internet. While this sucks as a user, it lowers their cost to support since there is much less chance that I will install a rogue application or otherwise screw up my Blackberry and then expect them to help.
If they're willing to let you use it, I'd definitely say go for it, but be aware that at some point you're probably going to have tot tell them that they need to update their server information to start sending the mail to a new device ID. When you do this, they're probably going to ask why, which could open a whole can of worms...
Good luck!
Mike
I would like to use my P3600 i.o. the BB. In this case I could avoid having 2 devices...I asked my IT dept and, as you stated, they did not support it. Now, is there a way to use BB on my P3600 with no help rom the IT dept?
I have the P3600, the BB, and 2 TIM wih the same number (1 normal +1 twincard). Obviuously, I do not want to dismiss my P3600 and use only the BB!!! PLEASE HEEEEEEEEEEEEEEEEELP!!!!
any other help ?
please....!!!
As far as I know, you can have BB connect working, by using the DOPOD WM5 ROM and BB Connect version 2.1.2.52
You should try, it will work.
BBConnect will work with WM6 on Trinity.
Search this forum for bbconnect_wm6_professional_bb_4_1_.0.0.90.exe this is the BBConnect install for Trinity WM6
Ensure that your SIM has been enabled for Blackberry before you install. The rest is easy.
Good Luck!
Hi,
For those interested in the effort to port Android to the Excalibur, wing-linux android 0.4pre4 has been released with support for the Excalibur. Installation should be pretty easy (must install to the micro SD card).
For details and download: http://sourceforge.net/apps/trac/wing-linux/wiki
This project is looking for more developers, so you're welcome to join.
Please Note: to reset your device after using android you'll have to take out the battery. As mentioned, the software does not install to the phone's ROM, so it's nice and safe no flashing!
Biggest issue is that sound doesn't work yet. GSM works if your SIM card has no pin. For information on setting up GPRS, please see the wing-linux forum.
Please test all you can, and report back either here, or even better at the wing-linux forum.
Cheers,
Update:
To fix the problem that the console is rotated the wrong way, after installing, go to the linux folder on the SD card and edit the "default.txt". In the CMDLINE variable, remove "fbcon=rotate:3".
For those of you that want a normal linux console, i.e. so Android doesnt start automatically, change the "4" on the end of this line to a "3" (this is the runlevel)
help
Can you hel me? I want to know if i can to install this so on my excalibur telcel (mexico) and how can i install it?
thanks
uccellino said:
Hi,
For those interested in the effort to port Android to the Excalibur, wing-linux android 0.4pre4 has been released with support for the Excalibur. Installation should be pretty easy (must install to the micro SD card).
For details and download: http://sourceforge.net/apps/trac/wing-linux/wiki
This project is looking for more developers, so you're welcome to join.
Please Note: to reset your device after using android you'll have to take out the battery. As mentioned, the software does not install to the phone's ROM, so it's nice and safe no flashing!
Biggest issue is that sound doesn't work yet. GSM works if your SIM card has no pin. For information on setting up GPRS, please see the wing-linux forum.
Please test all you can, and report back either here, or even better at the wing-linux forum.
Cheers,
Click to expand...
Click to collapse
Hey great news......
Good going ..........
Hats off to all the geniuses on this project,
and a special thanks to UCCELLINO to get it on our beloved DASH
Hey Just one question ,
Is it the same cab for all the models ?
Tested
Tested!
And...
Success!
It works...
Since it is nowhere near finished ill mention only the cool things...
D-pad works and all of the other buttons too... (qwerty including)
Amazingly good integration for non touch screen phone... (I could almost imagine using it)
I would played bit more with it but to my biggest disappointment
THE SCREEN IS INTERLACED AND FLASHING(flickering) ALL THE TIME
Tested on MDA Mail
I almost forget: Thanks to all the involved geniuses...
I still can't believe it works, simply amazing
woohoo!!!!!!!
cant get it to start it fails and takes me to command prompt
Anyone has screenshot of this new Wing Linux?
Hi,
Thank you for doing this testing... the interlaced screen issue does not happen on my device... maybe there really are different models. I will check this out - it is probably a problem with screen timings. If you want to help, check out the Excalibur forum on the wing-linux forum and try another device profile.... Once I know what other device worked better for you, I can try and support it better within the Excalibur profile.
For other people: there is one main cab to install and then another smaller one to set it up for the Excalibur.
Once again, thank you to all for the help in testing! Next step is working audio and then we can really be on our way
istosevski said:
Tested!
And...
Success!
It works...
Since it is nowhere near finished ill mention only the cool things...
D-pad works and all of the other buttons too... (qwerty including)
Amazingly good integration for non touch screen phone... (I could almost imagine using it)
I would played bit more with it but to my biggest disappointment
THE SCREEN IS INTERLACED AND FLASHING(flickering) ALL THE TIME
Tested on MDA Mail
I almost forget: Thanks to all the involved geniuses...
I still can't believe it works, simply amazing
Click to expand...
Click to collapse
What process did you go through exactly... this may be a bug can you give me any more info?
Just some points:
it must install to the micro SD, which needs atleast 250+ MB free available
you must install two cabs, the main one and then a little one for the Excalibur
in theory, if you do get to a command prompt, you can log in and use linux to start android.
Login is as follows:
username: root
password: wing
trinidad716 said:
cant get it to start it fails and takes me to command prompt
Click to expand...
Click to collapse
Sorry, no screenshots as yet. But it runs Android Cupcake, and pretty fast too (for an old phone). Really, this project is going somewhere, and Android is very usable on the device with such a great keyboard.
Perhaps a very techy person could make a little video?
All you need is an micro SD card, may be 30minutes and being prepared to pull your battery when you're done...
If you're a linux programmer, that'd be cool too.. I desperately need info on how to reset the Excalibur in software
Cheers
10507 said:
Anyone has screenshot of this new Wing Linux?
Click to expand...
Click to collapse
uccellino said:
What process did you go through exactly... this may be a bug can you give me any more info?
Just some points:
it must install to the micro SD, which needs atleast 250+ MB free available
you must install two cabs, the main one and then a little one for the Excalibur
in theory, if you do get to a command prompt, you can log in and use linux to start android.
Login is as follows:
username: root
password: wing
Type "/android.sh" to start manually (from memory)
Click to expand...
Click to collapse
Which is the main one....i found the small one for excalibur...
This is how it looks like on my MDA Mail
http://www.youtube.com/watch?v=Vk3myrxh-5g
is functional??? thanks in advance!!
rafaelgsm said:
is functional??? thanks in advance!!
Click to expand...
Click to collapse
tested by me... crashes when incoming call... best than anothers versions... progress is notorious , thanks in advance
I cant get it to work, I installed both cabs to my card and when I launch it all I get is different colors shifting on the screen :S
HUGE progress!
How long did it take you guys on first boot?
hello geniuses,
Does any one have an idea abt how to feed in the APN in this version of android, so that we can have a feel of the browser.
Please Help....
wow great work! the screen is flickering and is interlaced mode, but it's pretty nice and works! I could not make a call, but sent sms from messaging. keep going!
Hey, I like to use multitouch to get more intuitive input on the touchscreen like to emulate a virtual ThumbStick and some buttons working on the same time.
It's easy to get multitouch working using the WindowsMessages HTC_Zooming, HTC_End_.... But now, the fingers must be set on the screen nearly at the same time or it won't work. That's fine to implement some rotation or zooming cap but it's not enough for a game...
Does anyone know how to get multitouch, like the HTCAlbum does support?
An interesting fact is that the HTCAlbum app is in the blacklist of the Pinch cap in the registry and to get the PinchToZoom-Messages you must be registered in the whitelist...
Thanks
If you send me one HD2 for testing, I'll find it out hehe
HTCAfe.dll
Hey guys
I'm doing some research in the dependencies of the htc apps on my hd2 to get real multitouch. Now I need to analyze htcafe.dll but I can't copy it from my device 'cause it's cooked in the rom.
How do I get that lib on my pc or could anyone send me a copy?
Thanks
Sure, here you go!
Fast?
EpiphanyNL said:
Sure, here you go!
Click to expand...
Click to collapse
thanks for that quick help!
You can usually copy out rom modules with either Cotulla's romextractor.exe or dotfred's task manager (the Depends tool-extract rom library).
DirectShow?
Hey guys
I'm sorry for the long dead time. It's really tricky 'cause I've no idea of directdraw/show on winmo? I figured out that you have to create a htcscene out of htcafe.dll and there you probably get the real multitouch-events.
Could some one send me a good tut for directdraw/show?
cheers
Got it!!!!
I got it working now!!! After spending hours, I found out how the HTCAlbum does it and I think it's the best way to do it without rewriting the whole driver and that stuff....
If anyone is interested in how to do it, i will write a sdk for .net and maybe a tut for native coding... (So if you're writeing a game... I can't wait to see multitouch ingames!!!)
For the moment I'm done, but I will soon post a sample game (some stuff like AirHockey or Pong)... (if I find time....)
Cheers
Some sample would be nice =)
Is it really something different from "HTC_Zoom_Begin" etc?
As for me, I prefer native code sample, but .net sample is ok as well.
How is this different from the multitouch already enabled on many hd2 apps? For example, fpsece, the playstation emulator has had multitouch for a long time, at least in the donators version. Is this a better implementation of multitouch?
Sent from my HTC HD2 using XDA App
zarathustrax said:
How is this different from the multitouch already enabled on many hd2 apps? For example, fpsece, the playstation emulator has had multitouch for a long time, at least in the donators version. Is this a better implementation of multitouch?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Firsteful, there are now three approaches to get multitouch working (as far as I know). The first is the simplest, I think the multiouch skins for morphgear uses this trick. If the second finger is pressed, you get (I don't know exactly how, cause it was never an option for me...) the point in the middle, and you asign two buttons to this point.Well, It's fake multitouch, but it works.
The second option is to write the PenTrac.dll and activate MultipointDemo (or what so ever) key in the registry and send some window messages (they often abuse the standard mouseevents...)...
The last option is to use HTC_Zooming-messages and so on (in my opinion the best, cause this function is already there, so no overheat is made...). And this is what I do. But in all samples I got before (like I described in the first post of this thread...) , you needed to press both fingers at the same time. I figured out, how to avoid this problem. And that's the difference...
And in the end, I just wanted to make a really easy-to-use sdk. So that even beginners are able to get multitouch working.... I found it quite hard to start with all the p/invoke stuff or change from c# to native code. I hope I can help you with the sdk.
Here's the thread of my sdk. Feel free to leave feedback.
http://forum.xda-developers.com/showthread.php?t=906068
Chabun
Anyone that thinks I may be right should "thank" me for this post...
I see 2 problems keeping development down on this device (Raphael)...
1. Memory mapping has to be done. I see no progress in this area. If I had the proper GUI or even DOS program I might be able to help. Of course, lack of development could be related to...
2. Noone really wants to pay to unlock their phone for development reasons. I can understand hard work, but MTTY and Task2a aren't really all that hard to use.
Thoughts, ideas, complaints?
Are you talking about flashing to NAND?
A few RHOD devs have started it, and it seems BLAC has picked up a new kernel dev and they have it booting to about he same state as all GSM RHOD's (no service..)
I would like to see NAND on all devices, but in reality a dev with each device needs to take up the cause... No dev with a RAPH has tried AFAIK. I would certainly love to facilitate any flow of knowledge necessary from the RHOD NAND project. I'm certainly not a developer on the project, but I do help with testing and I work closely with the devs (as closely as I can )
I am speaking of putting it on NAND. Seeing as we have squeezed an entire install plus data and apps onto a Kaiser, I'm fairly sure we could get a working build pretty quickly if someone could port the Kaisers kernel and change the memory map.
I propose this...
1st partition for kernel, no more than 5mb in size. The kernel we use on the Kaiser is only 3,092kb, so this would fit even if we had to add anything to the kernel such as accelerometer support and FM radio drivers.
2nd partition for /system files, just to keep it relatively close to the kernel partition. This one could be set to 128mb to allow the larger builds room to "breathe". Also, the extra drivers needed for the extra hardware will need room, hence partition size increase.
3rd partition will need 32mb for /cache. One of the drawbacks to running Android on the Kaiser was that if anything failed and the phone crashed, you would lose data. This was mostly due to having a live cache partition built inside the /data partition.
Scooter1556 has found a way to make a 20mb partition using part of the /data partition. Yes we lose 20mb out of 110, but the gains in stability and data integrity are well worth it, and newer builds of Android require a 30mb cache partition.
4th partition for /data. Do the math; could you fill 347mb of data on your WM6.1-6.5 phone? Not music, not movies, actual data? Apps from the Market, your contacts, text messages (if you save them), and anything else related to data? I couldn't, but that might be from running a phone with 40-50mb available for data...
I might be pissing in the wind but I think it's quite possible to do, just don't see much demand for it.
PoXFreak said:
I am speaking of putting it on NAND. Seeing as we have squeezed an entire install plus data and apps onto a Kaiser, I'm fairly sure we could get a working build pretty quickly if someone could port the Kaisers kernel and change the memory map.
I propose this...
....
I might be pissing in the wind but I think it's quite possible to do, just don't see much demand for it.
Click to expand...
Click to collapse
If you're willing to do it, so be it. It's just not easy and there aren't many devs with the device - I think everyone (well, mostly everyone) would prefer to be rid of WinMo and just boot Android... but that's a big task, converting from HaRET...
After doing some much needed research, I found out something..
The HTC Dream/G1 uses the EXACT same processor, GPU, LPDDR RAM, phone controller, BT, WiFi and GPS module as the Raphael.
Whats missing, you ask?
A trackball and memory map to match. The Raphael actually has better specs than the G1 and I see cooks building roms based on 2.3.5 (Gingerbread) for that device.
There are a few extra keys on the keyboard which need mapping (swipe from HaRet version, maybe?), and the trackball would have to be converted to a D-pad. Everything else matches!
May not even need to build a kernel, the HTC Dream Dev edition has their ROMs' and radios online... I already downloaded them and will play more tomorrow.
(Crossing my fingers)...
PoXFreak said:
After doing some much needed research, I found out something..
The HTC Dream/G1 uses the EXACT same processor, GPU, LPDDR RAM, phone controller, BT, WiFi and GPS module as the Raphael.
Whats missing, you ask?
A trackball and memory map to match. The Raphael actually has better specs than the G1 and I see cooks building roms based on 2.3.5 (Gingerbread) for that device.
There are a few extra keys on the keyboard which need mapping (swipe from HaRet version, maybe?), and the trackball would have to be converted to a D-pad. Everything else matches!
May not even need to build a kernel, the HTC Dream Dev edition has their ROMs' and radios online... I already downloaded them and will play more tomorrow.
(Crossing my fingers)...
Click to expand...
Click to collapse
Good luck. I'm not sure that stuff is identical & translatable directly, but have at it - just be careful, when playing with NAND there's very special portions of the memory that you should not touch, lest you have a brick.
Again, MTTY is not very hard to negotiate, and since the processor is similar to the Kaiser I should have no problems there.
I am looking into the "boot.bin" file right now to see where the signatures are and to see if there are "way points" for the memory mapping.
Will report back soon but I also need to grab the memory map from the WM6.1/6.5 build ROMS, so it could be an all-day affair...
PoXFreak said:
Again, MTTY is not very hard to negotiate, and since the processor is similar to the Kaiser I should have no problems there.
I am looking into the "boot.bin" file right now to see where the signatures are and to see if there are "way points" for the memory mapping.
Will report back soon but I also need to grab the memory map from the WM6.1/6.5 build ROMS, so it could be an all-day affair...
Click to expand...
Click to collapse
Rome wasn't built in a day.
Good luck! I wish you well
Got the memory mapping done, just have to figure out how to post to the kernel and figure out how to CID unlock without PAYING for it...
Memory map as follows:
Code:
457.75M (0x1c9c0000) DSK1:
| 3.12M (0x31f000) Part00
| 4.50M (0x480000) Part01
| 126.50M (0x7e80000) Part02
| 323.63M (0x143a0000) Part03
I wish l1q1d and scoot were looking, this is about as far as I will get without help.
Raphael & G1 screens
PoXFreak said:
After doing some much needed research, I found out something..
The HTC Dream/G1 uses the EXACT same processor, GPU, LPDDR RAM, phone controller, BT, WiFi and GPS module as the Raphael.
Click to expand...
Click to collapse
Does the G1 also have the same screen than the Raphael? That could help fixing the "never sleep" problem that arrrghhh said on this discussion.
Different screen but same exact GPU...
Dream G1 is 320x480 @ 16BPP 180.9 Dot pitch and uses Qualcomm Adreno 130.
Raphael is 480x640 @16BPP 290.3 Dot pitch and uses Qualcomm Adreno 130.
The "never sleep" issue is only a command, but that command also slows the core speed of the CPU down to save power as well since the GPU is also controlled by the CPU. The problem with not waking up is because Android has a wierd way of holding the panel command on or off.
P3 Droid (a clock speed mod) had a way to not only overclock but underclock the Droid. In an attempt to port this to the Kaiser it would fall back but never return to full speed, locking the phone up and requiring a soft reset. Once I restored my build back to normal it went back to a somewhat normal operation (back then we still had kernel issues and alot of other bugs).
What I need now is a full phone unlocker for thr Raphael that doesn't require an IMEI number... anyone have one?...
PoXFreak said:
Dream G1 is 320x480 @ 16BPP 180.9 Dot pitch and uses Qualcomm Adreno 130.
Raphael is 480x640 @16BPP 290.3 Dot pitch and uses Qualcomm Adren 130.
Click to expand...
Click to collapse
So for that (among many other) reason(s) you can't just plop a G1 kernel onto our devices and expect it to work. I would think that anything that can be borrowed, has been. I know they look at that device, the Hero, and I believe the Sapphire... Not sure what others, maybe Tattoo?
I don't think there's a single Android phone with these paltry RAM/CPU specs and such a high-resolution screen. I think that may be one of the reasons graphics are so poor, it has to work so much harder to render!
PoXFreak said:
What I need now is a full phone unlocker for thr Raphael that doesn't require an IMEI number... anyone have one?...
Click to expand...
Click to collapse
You mean more than just HSPL...?
Yes, more than HSPL... I need to CID unlock the phone because even with "unsigned" roms they can't flash. I'm guessing the phone is looking for that CID, and if it either isn't there or doesn't match it will not flash.
I tried using HTC's diagnostics SD from the Artemis and Hermes, neither worked because the CID doesn't match, even after I stripped the CID identifier from the diagnostics tool.
Will dig in more tonight, 2 days on this so far and I'm burnt...lol.
PoXFreak said:
Yes, more than HSPL... I need to CID unlock the phone because even with "unsigned" roms they can't flash. I'm guessing the phone is looking for that CID, and if it either isn't there or doesn't match it will not flash.
I tried using HTC's diagnostics SD from the Artemis and Hermes, neither worked because the CID doesn't match, even after I stripped the CID identifier from the diagnostics tool.
Will dig in more tonight, 2 days on this so far and I'm burnt...lol.
Click to expand...
Click to collapse
Yea, always a good idea to take a break and hit it fresh another time.
As for the CID unlock, I'm not sure I can help you with that - first because I don't know how, and second if it's illegal.. don't ask on this site .
CID unlock is only a "security" lock from a manufacturer to keep people from flashing the wrong rom to their device, IE flashing a Diamond rom to the Raphael.
If I had it unlocked, I could try flashing the original Dream bootloader for 1.6 to the Raphael. If I brick it I can get it back through MTTY and OEMSPL.
BTW,
the screen resolution and DPI is set in the kernel BEFORE any boot even takes place. If someone had enough "cahones" to mess with it in HEX editor they could find the values and change them to 480x640 16BPP 290DPI.
PoXFreak said:
CID unlock is only a "security" lock from a manufacturer to keep people from flashing the wrong rom to their device, IE flashing a Diamond rom to the Raphael.
If I had it unlocked, I could try flashing the original Dream bootloader for 1.6 to the Raphael. If I brick it I can get it back through MTTY and OEMSPL.
BTW,
the screen resolution and DPI is set in the kernel BEFORE any boot even takes place. If someone had enough "cahones" to mess with it in HEX editor they could find the values and change them to 480x640 16BPP 290DPI.
Click to expand...
Click to collapse
Heh. All you dude, you seem to have all sorts of cahones .
Keep it up, RAPH users need hope like this .
Sorry guys and gals, been way too busy in MTTY trying to unbrick my secondary Kaiser... Almost done though. Will also be able to CID unlock the Raphael with this as well.
What I need is to see how much interest there would be in developing a custom-compiled OEMSBL for the Raphael, possibly crossing over to other phones.
I would want to use either the LK Pistachio or, for obvious reasons, the newer OLK4 v3.0 MicroKernel, to be used to run the Dream/Magic bootloaders and at least Android 1.6, or even "cupcake" for that matter.
There is enough development in the Dream G1 forum to run with after that.
WHO WANTS IN?
There is enough documentation on the MSM7201A and MK to do this, I just don't have the compiling skills in Linux to do it. Matter of factly, there's not too much difference between the MSM7201A and the 7200A, being they are the same family but different build processes (65nm vs 90nm, i believe), AT commands are the same via what I've gleaned from their respective build sheets (I have both in .pdf format).
Hope I get some help because if I don't phones will be installed in teeth by the time I get done with it...lol.
I just realized something...
The memory map for the Kaiser is similar in the fact that OEMBL (microlinux) goes into PART 0, the kernel (nand install) goes into PART 1, /system can go into PART 2 and /data can go to PART 3 with a 30mb /cache partition at the beginning or end.
I need help porting this, changing the Kaiser kernel to read CNG_003 and remapping memory. The only other thing would be getting the proper drivers for the D-pad (non-touch, never liked that anyway), the screen size is a non-issue since whatever you feed it it will display, at least thats how it works on the Kaiser...
PoXFreak said:
I just realized something...
The memory map for the Kaiser is similar in the fact that OEMBL (microlinux) goes into PART 0, the kernel (nand install) goes into PART 1, /system can go into PART 2 and /data can go to PART 3 with a 30mb /cache partition at the beginning or end.
I need help porting this, changing the Kaiser kernel to read CNG_003 and remapping memory. The only other thing would be getting the proper drivers for the D-pad (non-touch, never liked that anyway), the screen size is a non-issue since whatever you feed it it will display, at least thats how it works on the Kaiser...
Click to expand...
Click to collapse
Nice! I like seeing posts like this .
Have you talked with any of the folks on #htc-linux or #xdandroid? There's usually someone there that's knowledgeable and can help. Not always, but usually .
Here's what I've figured out so far...
Since no "open-source" CID unlock tool exists for this phone, noone can unlock it's capabilities by using Android to it's full extent. I looked into decompiling a paid unlock tool but I don't have C++ installed on any of my machines just yet. When I do I'll go hunting again.
I would have to create a new rootfs or just use the tinboot with a partition layout similar to what I posted above. The motivation is there, I just lack the tools to do it correctly and efficiently.