Related
This was the thread that got Android started on Vogue, use it now for all discussions about kernel development.
The first 400 pages or so are just for historical interest
Hi All,
I've managed to get Linux and Android up and running on Vogue. I've put everything you need at http://cs-alb-pc3.massey.ac.nz/vogue. Just download the latest android zip file, copy system.img and data.gz to the root of your sd card and all the other files anywhere you like, run haret.exe, click run and wait a while. This is with my New Zealand Vogue (Branded as OKTA Touch) but it seems to work on all Vogues, (e.g. Sprint Touch). This has no chance of working on any phone without an MSM7X00 CPU. Newer kernels (i.e. those with audio and power collapse) will only work properly if you have an updated radio, I am using 3.42.50 so update to this if you can.
Volume Down is the Menu Button, Volume Up is Back, Power is Home (on recent kernels) and the Camera button displays the keyboard.
This will not damage your phone in any way and is very safe, it doesn't touch the NAND flash memory so can't mess up anything, just soft reset (or press and hold the end call button, then select power down) to restart windows mobile.
To add Android apks, put them into a directory called AndroidApps (must be capitalised correctly) in the root of your SD card.
Update: Touchscreen now works, people have also had some success running this on Kaiser and Titan.
Update: Radio works, see post 187.
Update: Now has an onscreen keyboard, see post 303. (http://forum.xda-developers.com/showpost.php?p=2213637&postcount=303)
Update: Can now make and receive audio calls, see post 312.
Update: SMS now works, see post 330.
Update: Backlight can now be turned off and the browser works well.
Update: Better keyboard, working clock and charging, see post 436.
Update: SD driver works, see post 539
Update: New SDK boots, network and calls work, no SMS yet.
Update: New SDK works much better, SMS works, audio works, now has full screen keyboard, see post 867
Update: Power Collapse works, battery meter works.... in fact it's pretty much usable now.
Update: Camera works (with some quirks), network can be connected and disconnected.
Update: Runs the android cupcake release with on screen kbd.
Update: Screen brightness works.
Update: USB works (adb only)
Update: GPU works.
Update: Audio input works.
Thanks.
Note: This will only work on Vogue, Please don't ask about other devices, they should have their own threads.
There is now an irc channel (#vogue-android) on freenode to chat about this port.
My Paypal is here if you want to support this project:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
I tried with my Sprint Touch. Apparently it boot up ok. I saw the GUI of Android with contact/dial/all shown in the lower right corner of the screen.
However, none of the buttons are working, including d-pad, volume up/down.
Ah I see the problem, I copied an older initrd to the site, download initrd-android again (should be 19595944 bytes) and it might work.
cool. All the buttons work now.
AMAZING! I've been looking forward to Android since before it was announced, and to be honest, I'm super impressed that someone's already gotten it working on a ppc. I'll have to try it out sometime this weekend.
Don't get too excited, it's not usable as a phone. If anyone wants to help get the radio working though all the source is on the site.
wow now that is impressive. is this the real thing? that is...almost unbelievable. it took people longer to get wm6.1 running than this lol.
2 things tho:
1. could we maybe get some screenshots please?
2. how many others know about this? im sure if we posted in the appropriate areas here, at howardforums, and on ppcgeeks we would see some real progress.
EDIT: any ETA on how long till the touchscreen function is functional?
Hi, it is real, that's the beauty of open source.
I don't have any screenshots, it looks just like the emulator though and I'm sure somebody will post pics soon enough.
Nobody else knows about it, I just got it working today. I'm working on the touchscreen but it won't be much use really because there's no on screen kbd yet for android. More difficult is the radio though because the android kernel source uses a more recent version of AMSS (the qualcomm radio software) and somebody will have to reverse engineer the version in our phones. Should be possible though.
USB doesn't work but there is a driver so that shouldn't be too hard.
The other thing it needs is an SD driver, at the moment it boots out of a large initramdisk so there's no persistent data.
Have fun.
dzo said:
Hi, it is real, that's the beauty of open source.
I don't have any screenshots, it looks just like the emulator though and I'm sure somebody will post pics soon enough.
Nobody else knows about it, I just got it working today. I'm working on the touchscreen but it won't be much use really because there's no on screen kbd yet for android. More difficult is the radio though because the android kernel source uses a more recent version of AMSS (the qualcomm radio software) and somebody will have to reverse engineer the version in our phones. Should be possible though.
USB doesn't work but there is a driver so that shouldn't be too hard.
The other thing it needs is an SD driver, at the moment it boots out of a large initramdisk so there's no persistent data.
Have fun.
Click to expand...
Click to collapse
WOW. i REALLY must say i am REALLY excited and amazed at all this!
so one more quick question: is this currently only for the vogue? the porting of the android os/whatever device-specific i assume?
we really ought to have this moved to the vogue upgrading sub-forum in order to get more exposure
i assume you dont mind or you wouldnt have posted here, so im gonna post this over at ppcgeeks.
if you do mind though, be sure to let me know!
No problem posting elsewhere. It should work on titan (but might be short of memory and keys may not work), doesn't work on kaiser because the hardware is slightly different.
you're going to be famous if you get this working
...i'd get some advertising revenue from your website organised if I were you!
MS are going to be really upset if it proves easy to get a WM phone and blow off WM for Android. I'd love to run Android on my Artemis.
dzo said:
I'm working on the touchscreen but it won't be much use really because there's no on screen kbd yet for android.
Click to expand...
Click to collapse
Do you have a CPLD gpio extender on Vogue ? It's certainly there on kaiser and titan.
Is the touchscreen a TSC2003 on i2c or something on a MSM ADC ?
touchscreen is i2c, i don't know about the cpld stuff. the only gpios i used are for the buttons and they were quite obvious. the hard part will be the radio because it looks like it uses rpc over the shared memory. Same for clock control and pm.
Great work. It's good to see progress being made. Unfortunately I can do absolutely nothing to help
Bravo! I wish I knew more About Linux/Android to help
dzo said:
touchscreen is i2c
Click to expand...
Click to collapse
The TSC2003 linux driver is already available.
i don't know about the cpld stuff.
Click to expand...
Click to collapse
You may check the 0x9* physical address range, or dump the SPL from SRAM,
or look at the 'dump mmu' output.
Same for clock control and pm.
Click to expand...
Click to collapse
The clock control registers are known.
can somebody tell me what button to press to end a program and go back to "home" screen on Android?
dzo said:
No problem posting elsewhere. It should work on titan (but might be short of memory and keys may not work), doesn't work on kaiser because the hardware is slightly different.
Click to expand...
Click to collapse
alright great. im gonna try and post it in the titan sections here and at ppcgeeks and see what happens with this "It should work on titan (but might be short of memory and keys may not work), doesn't work on kaiser because the hardware is slightly different." in mind and posted. i suppose it couldnt hurt.
since my knowledge is far too limited to provide assistance here, i might as well try and recruit some more help! though it looks to be that cr2 knows what hes doing (thanks!)
must say, it's nice to see a post from the guy that is doing this. I've been using your website as a base for my titan.
Note to the titan users, in the default text you'll want to change the machine type to 1463 (MTYPE = 1463)
My quick question is, if i run haret and happen to boot up android, will i end up requiring a hard reset? I know some people say yes and some say no, but I figured I'd ask someone using the newest haret on one of our phones. (it's a pain for me to reflash, as i have to reboot into windows and do it).
Hi,
Don't change the mtype, it definitely won't boot if you do that.
This runs entirely from RAM so it won't do any damage to your phone and you won't have to reflash it. I've booted this kernel hundreds of times and the worst that has happened is that I lost my contacts list once and had to resync, i guess the wince filesystem is not that robust to crashes.
You will have to reset the phone after you're done playing with android by poking the stylus into the button on the bottom; but i'm sure wince uses are used to doing that.
I didn't map the home key but volume up will go back.
I've updated the initrd to include the api demos now.
Thanks,
OK, I have been waiting to play Monkey Island 1 again for a very long time, and that dream has been semi-realized now that ScummVM is in the Market. I have the (I think) correct data files on my sd card. The only problem is when I choose Add Game it takes me to a directory listing that won't let me scroll up and down and when I select a directory it dumps out of the program.
Is it just buggy right now, or am I doing something wrong?
i dont know, i have installed scummvm in my phone and i only have problems with LOOM.
this version have a problem, with this phone we dont have a stylus and the bottons from the scroll are small.
I know this sounds very dum but if you head over to the scrummvVM site and check out the list of data files that are needed for each game that will probly help, you could also double check the compatibility.
http://www.scummvm.org/compatibility.php
Took me a while but to my suprise i got broken sword working, was very happy. Only downside to these games is that they require rather precise clicking....there are specifial stylus you can purchase for the G1 im looking into
Sorry, I replied to the message i got on my G1 thinking it would reply here but I guess not. I just wanted to say that I was wrong and it does work. the problem I was having is that scrolling down to choose the sdcard folder is VERY VERY HARD! You essentially have to keep hammering on the screen for a few minutes until it registers the button press enough times to show the correct folder. It is so difficult to do that it appeared to be locked up when in reality it wasn't. Once you add the game it runs fine!
I tried typing the name and it was much easier to add. It still needs a more accurate pointer though. My fat finger is not cutting it.
I'd agree with the "fat fingers" problems. It's definitely something that would work much better with either a stylus or some sort of trackball mouse pointer.
I've tried Loom, Gobliiins, and Day of the Tentacle. Loom is the only one that freezes on open (after speaking one file). Too bad it's my favorite game. lol
Now all we need is freeSCI for Hero's Quest and I will want nothing more
the navigation menu of scummvm is very slow, but i got monkey island working fine, im already on the island
so ya i love this app!!!!!!
has anyone tried one of the iPhone styli for this?
bommel0815 said:
has anyone tried one of the iPhone styli for this?
Click to expand...
Click to collapse
Bought one from Ebay for around £9. Was very unresponsive and requires hard-pressing to work....It is my understanding that the G1 requires some kind of peripheral so that the screen can recconise it....not heat I think its a tiny electrical charge.
loooooom
I thought maybe i had a bad copy of loom, but everyone seems to have the same problem. Any ideas for a fix?
Any help would be grateful on this one
I have just changed the heat sink on my 9300 wifi ITX motherboard GF9300-D-E.
It will not boot windows as it gets to the starting screen and stops. Then when i tried linux it will kernal panic and not boot that either.
I thought it was memory and removed one of the sticks. This is when things started to get strange. The bios screen did not fit my monitor as it should, has done previously, also there are strange flickering on this as well.
So i have tried it with both sticks in one stick [both tried]
Now I am a little stuck as to what it can be. I have also reset the bios to a default state to see if that was the problem and it was not.
There is also the issue that on some boots the bios will not fully load up.
If this is not an issue with the motherboard then i am sorry but i am a little stuck for the reason at the moment.
So anyone any ideas on this as I'm a little stuck. Any other info will be added if you think its necessary but i think its all covered.
Please help I miss my desktop, my ageing 5 yr laptop really does not cut it any more
have you tried safe mode? press f8 when windows is starting. if you get a blue screen post what the error message is.
Yeh the one time i got that far i had
Page_access_in_non_paged_area
That was also on a recovery boot of windows.
Next time nothing happened...
Also i get weird graphics glitches on the memory test from ubuntu. if that means anything to anyone
chris10230 said:
Yeh the one time i got that far i had
Page_access_in_non_paged_area
That was also on a recovery boot of windows.
Next time nothing happened...
Also i get weird graphics glitches on the memory test from ubuntu. if that means anything to anyone
Click to expand...
Click to collapse
i need the stop code. it goes like this 0x000000 and so on.
Yeh i would love to post that error message but i cannot get that far until it crashes
I got to the windows system recovery hit enter, then it stopped working
Now it wont even give me a video output! Really starting to think its hardware, but what hardware i do not know. Later im gonna try some RAM from my house mates pc and see if it does any better. If that doesn't work then i think i may be RMAing the motherboard as its the only other thing it can be!
If you have any more ideas joe then i would be welcome to hear them as i would rather not go down the RMA route...
Wish id noted down that bluescreen when it came up now
sounds like your video card. is your video card onboard or add in?
on board but i can disable if i have an external one, i can try this as well house mate has a spare will get back to you when i have tried that one as well.
If it is that then def an rma job. Also i would not be surprised it has been idling at 70/80 degrees C for about 8 months due to the passive cooler i had on it.
Hey,
I had this error, and a range of other ones, stuff like Memory_Error etc (can't remember codes), on my laptop earlier this year.
I tried memtextx86, and burnin, as I suspected it was an issue with ram - I also tried 3 different sets of rams, with different combinations of sticks. Nothing worked.
Unfortunatley, I took it back to the manufacturer and it was the motherboard had gone faulty.
I hope this isn't the case for you, but those 2 programs may be worth trying. Just as a note, neither reported any issues with the ram.
When in windows (vista at the time) I could not be in for more then 20mins without a system hang and crash. Although I did have video out.
Hope this helps
Stu
If the only thing you changed before it started to play up was the heat sink, its probably the cause.
If its turning on and then playing up after a period of time for no apparent reason it could be heat.
Is the heatsink on the right way? I put my amd stock heatsink on backwards when I installed it, didn't notice for 2 months, it wasn't touching the processor at all. Funny when I look back on it.
Did you put thermal paste on it? I once thought it would be a great idea to clean all of that gunk off my cpu, not so good in hindsight.
Hope it helps,
They say you learn from your mistakes, an I've broke more computers than I can count.
stu i shall try at the weekend one more exam and im free for another year!
and mercianary yeh i did clean the paste off, i did apply paste, but going back is a good point as i think there may be slight sizing issues with the heatsink i changed it for. As for temps, not real problem i think as i want from a passive heat sink to one with a fan so it must be cooler, that was the idea anyway.
It was idling at 45-55 if it did anything that needed the whole chip, its a 3ghz core2duo it hit 65 easy and it starts to underclock at 70 so i wanted it to be cooler so i could use all the power all of the time! In hindsight a bad idea.
Also on the grounds of the stock cooler that is broken as it kinda got stuck on the motherboard when i put it on one of the clips went straight through and jammed....
anyway everyone who has replied thanks i will come back when i have done some testing.
Not sure anyone will be able to help with this -- it's a weird set of circumstances. But maybe someone's got an idea.
I've got a Vogue that the camera button has stopped responding on. When I press it, it gives no resistance, like the button/spring has just fallen out or moved. I'd like to take it to the sprint techs and see if they can pop it open and make sure everything lines up again (this is, after all, the reason for keeping an equipment protection plan).
However, I'm not going to bring it in running Android, so I need to flash it back to stock. How to do that? Bring up bootloader mode by holding, you guessed it, the camera button (and volume down) at startup.
I know that the RUU application can trigger a reboot into bootloader mode from WinMo -- but I'm sure it has to be hooked up to activesync to do so, so that's not much use.
Is there some other way to get from Android to bootloader? Or... is there any other way to... sort of sideload a WinMo ROM from linux, without going through the bootloader mode? (I seriously doubt that part, but I'm grasping here.)
Or is there another way to get into the bootloader that I haven't thought of? I guess I should ask this in less specific vogue forums. Searching has provided me no clues.
Thanks for any ideas.
http://forum.xda-developers.com/showthread.php?t=708376
OK, so clearly my line about searching doing no good was premature. I'm a little embarrassed now. (I failed to search this particular forum, so I feel like a heel.)
Then again, that thread doesn't do me any good... it just confirms the bad.
Anyway, thanks. So that sounds like a pretty firm no. Ugh, stepping down from 5 buttons to 4 on this phone is not a pleasant proposition. Even with the camera button, it's pretty cramped.
The EnterBootloader.exe tool (which I assume is the same as BootLoader.cab in that thread) should be able to do it... unfortunately, I do not have the disassembly chops to figure out how to replicate its functionality.
makkonen said:
OK, so clearly my line about searching doing no good was premature. I'm a little embarrassed now. (I failed to search this particular forum, so I feel like a heel.)
Then again, that thread doesn't do me any good... it just confirms the bad.
Anyway, thanks. So that sounds like a pretty firm no. Ugh, stepping down from 5 buttons to 4 on this phone is not a pleasant proposition. Even with the camera button, it's pretty cramped.
The EnterBootloader.exe tool (which I assume is the same as BootLoader.cab in that thread) should be able to do it... unfortunately, I do not have the disassembly chops to figure out how to replicate its functionality.
Click to expand...
Click to collapse
hey, makk - can you open the case enough one time to get to bootloader, flash to winmo, then take it in? you don't need it to work forever, right? just enough to get it repaired? heck, even if you shorted it closed it might work.
Yeah, that's the option I'm considering now. Just need to pop the case open... which doesn't look like tons of fun. Anyone have any advice on that count? I actually have that tiny torx screwdriver, but that's about as far as I've gotten.
Edit: Searched and found a nice looking guide. See, I can search!
Edit2: Popped it open, jammed a paperclip into the camera button, got the bootloader up, back to WinMo, easy peasy. (OK, actually, horribly frightening. I hate ribbon cables.) Thanks, guys.
Though I no longer need it, building a linux EnterBootloader executable would be pretty nice -- especially since kernel updates are a pretty common occurrence -- it'd be nice to have a utility that'd grab the voguimg.nbh, put it on the sd card, and initiate the reboot all in one fell swoop. (...after doing some pretty thorough checks to make sure you're ready to go messing with your boot partition, of course.)
I took a look at the executable in ida, hoping that it might be simple enough for me to start to get a grasp of (that'd be very simple, for the record)... it was not. That program is the purest essence of confusion (at least to this assembly noob).
Anyway, if anyone has disassembling knowledge around here, and wants to give it a look, it might be pretty simple. (It also might be not simple -- I don't really have much way of knowing.) It's attached here.
makkonen said:
Though I no longer need it, building a linux EnterBootloader executable would be pretty nice -- especially since kernel updates are a pretty common occurrence -- it'd be nice to have a utility that'd grab the voguimg.nbh, put it on the sd card, and initiate the reboot all in one fell swoop. (...after doing some pretty thorough checks to make sure you're ready to go messing with your boot partition, of course.)
I took a look at the executable in ida, hoping that it might be simple enough for me to start to get a grasp of (that'd be very simple, for the record)... it was not. That program is the purest essence of confusion (at least to this assembly noob).
Anyway, if anyone has disassembling knowledge around here, and wants to give it a look, it might be pretty simple. (It also might be not simple -- I don't really have much way of knowing.) It's attached here.
Click to expand...
Click to collapse
COUGHdzoCOUGH
I don't think I'd want to go up on the roof and turn on the dzo-signal for something so trivial as this.
I have a HP Touchpad 32gb. I am a novice and I know enough to be dangerous. I had the same problem as everyone else- no charge and a dead tablet. I figured it was a goner and bought a Samsung 10.1. I came across my old HP and decided to see if there was a solution. I used the J Sullens debrick. I got through it and I am now stuck on the language screen. Won't respond to touch and I can't get any further. I have read the threads about OS doctor and all. I have downloaded everything but I'm in over my head. Would like to change to Android, but I'm at a stand still right now. Can anyone give me specific newbie instructions to get this device operating. Computer does not recognize it as a USB device, but I hear the tones as something being connected to the computer. When I extract files it shows as a F drive. I know I am close. And at this point I'm on a mission.