Database Develop

Linux and Android for Vogue [kernel thread]

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,

What's In This Directory

So, i've been working tirelessly to get my camera going again, a number of people have had this same problem, so, I'd like to fix it for them as well. I've finally found my starting point, so, first off, could someone with a working camera please tell me what's in this directory
/dev/msm_camera/control0

Well in the /msm_camera/ folder I have 3 files:
config0
control0
frame0
each with a size of 0, and no extension... and I am unable to copy them anywhere... hope it helps somehow...

Those are device files. Pipes into or out of the HARDWARE DRIVER.
Pipes don't take up space. They can be READ if your device is pumping data out, and the driver can READ data that you send into them.
If you don't know what they are for, chances are good that you should just IGNORE them. In fact, I can guarantee that you should just ignore ***EVERYTHING*** in the /dev path.
dev = short for "device", which is another word for HARDWARE.
EDIT: judging from the file names, the frame0 file is an output -- take a picture and it shows to be read from frame0. The other two appear to be inputs -- configuration (i.e. resolution, mode), and control (i.e. focus, aperture, etc.).

thaquestion said:
So, i've been working tirelessly to get my camera going again, a number of people have had this same problem, so, I'd like to fix it for them as well. I've finally found my starting point, so, first off, could someone with a working camera please tell me what's in this directory
/dev/msm_camera/control0
Click to expand...
Click to collapse
I just want to say I was having camera problems and decided to send it in under warranty. It took me less than an hour to unroot and get Donut back running. They sent me a new (or refurb) one, I put mine in the box, and done. If you still have warranty left, I recommend that path.

[Q] A couple of things

Hi, hi. I don't recall if this is my first post or not, but my original intent was to post on the developer's forum. I then found out I couldn't. So I'll post here and include a couple of questions/comments I have.
1. Have you noticed that XDA looks like a really happy dude puking the first letter of the alphabet? (That's totally an aside, just getting it out of the way.)
2. Due to some ridiculousness, I now have two Cricket Zios. One of them is working, the other one not. I've had the old one for a few months now and all this time I've been wondering what the heck to do with it. To specify: It went nuts when I tried the update on it (it originally had 1.6) and the corporate store flashed it when I brought it to them. Now when you turn it on, it shows the Android android and tells you to touch it (with the disembodied hand appearing, moving over it, then disappearing, as it's supposed to), but it ignores all input. Have to pull out the battery to shut it off, even. I can then turn it on (so at least I know the End Call button works and I *think* I've tried some combinations that work) and go through the process all over again. The good thing is that I now have a spare battery (go, me). In reading all the threads where developers are unsure of certain things, like whether or not the trackball can light up and whatnot, I'm wondering if it might be worth it for me to take the damn thing apart and take detailed pictures. At the very least, people would be able to see chipsets, individual chips, connections, lights, etc. Does anyone think this would be worth the effort? And, of course, complete loss of the device, though possibly I could use parts in other projects. (The screen, for instance, might be cheap, but it'd be REAL handy used as a miniature second/third monitor like those Liliput monitors.)
3. As a Linux user that doesn't give a damn whether a Windows OS can communicate with my microSD card, is there a reason I should not just format the entire card to something better than fat32?
4. As we all know, the trackball input on the Zio sucks like the Spaceball 1. Could this be improved by replacing the ball itself? It feels cheap anyway and I'm wondering if I could, for instance, take the ball out of a MyTouch 3G and put it in my Zio.

The FCC already has detailed pictures of the zio available, so that would be a waste of a phone.
If your 2nd phone doesnt work, you can always send it to me as a guinea pig phone -- it _really_ would be helpful to have an extra phone to develop with (provided I could get it working -- no guarantees but I'd be willing to try for the following reasons)-- being as any release, mod or anything for that matter I wish to test for you guys has to be done on my main phone, which Im sure any tester could tell you, is a major pain in the ass. lol. So if you really wanna help the cause, that would help me greatly
As for formatting the SDcard -- dont. Your phone saves all data to FAT. The only thing you _may_ wish to do is partition 512Mb off as an ext3 and use link2SD to symlink ur apps to the ext partition.
As for the trackball -- you can try taking it out (if you have the right screwdriver for it), cleaning the contact points, and putting it back together -- that might make it respond better (as I have no problems with my trackball.).
Hope that helps.
~Cheers!

Thank you very much! And I'll totally donate to you the phone (I appreciate a lot of what you've done anyway). Would you mind getting it without the battery?

Don't mind at all -- it'll be plugged in 100% of the time.
Not home atm, but Send me a pm m8.
Sent from my Zio using XDA App

Nice! as an openZio user I thank you

@ SilasMortimer :
Any updates m8? Havent heard from you in a while.
Cheers.

Heya. Sorry I disappeared. I kind of forgot to come back. I think I need to change my settings so I get email notifications.
It'll be sent soon.

Phone Freeze , Lag, Touch screen unresponsive , Internet connection not stable

This is my second time bought an AT&T Samsung Focus, and again...it suck!!
My first Focus has the Network problem, returned it already to the seller..
Bought another one, and it gives more complicated issues...aaarrgghhh...
Phone very often Freeze , Lag when I swap between apps, Touch screen unresponsive , keyboard freeze and then suddenly typing on its own like crazy...Internet connection unstable..
I got the Focus still on Window 7, updated to 7.5 (7.10.7720.68) from Zune, thought it will fix the issues but it is not.
Can someone show me how to fix this ? Load custom ROM or whatever to make it works again? I'm going to sell this crap once it fixed
Sorry for my language..It's totally drive me crazy

I'm not aware of any 'custom ROMS' that are available for WP7 devices, since the various bottom layers have not yet been cracked, as far as I know.
That said, I'm not sure that the device is at fault, and definitely not the O/S. There are plenty of us around using the Focus (it was one of THE most popular WP7 devices ever) with no problems -- certainly not the ones you are experiencing.
Your signature/profile don't say where you are or which provider you are using -- but many of the problems you describe could be due to problems at the service provider end, not the device itself. Obviously it is frustrating when the phone does these things, but I'm not sure there is a quick fix available here for you.
BTW, this forum is for the Focus S -- there's a separate one for the original Focus unit.

drtolson said:
I'm not aware of any 'custom ROMS' that are available for WP7 devices, since the various bottom layers have not yet been cracked, as far as I know.
That said, I'm not sure that the device is at fault, and definitely not the O/S. There are plenty of us around using the Focus (it was one of THE most popular WP7 devices ever) with no problems -- certainly not the ones you are experiencing.
Your signature/profile don't say where you are or which provider you are using -- but many of the problems you describe could be due to problems at the service provider end, not the device itself. Obviously it is frustrating when the phone does these things, but I'm not sure there is a quick fix available here for you.
BTW, this forum is for the Focus S -- there's a separate one for the original Focus unit.
Click to expand...
Click to collapse
Opss...Sorry... I must be crazy already
Please Mod, remove this to the Samsung Focus thread ?

I am experiencing similar issues on the original Focus and am scouring the forums for a solution.
I shall report back if I find anything.
(This post also serves as a "watch this thread" for me)
jt

jt3204 said:
I am experiencing similar issues on the original Focus and am scouring the forums for a solution.
I shall report back if I find anything.
(This post also serves as a "watch this thread" for me)
jt
Click to expand...
Click to collapse
I don't know if I'm allow to continue this thread as it is on the wrong section but this concern me alot and would appreciate any fix.
I found that there's Roger Rom, what I'm thinking is if it's possible to flash it to get a new fresh Rom installed and hope the problem would gone?
I read some thread on it but still not sure what steps should I do. Also if there's thing I should aware due to flash it to non AT&T Rom, maybe that I would not be getting an official update or whatever.
As long my focus is behaving correctly that is what I'm asking since I'm only using it to get my emails as a replacement of my blackberry. It freeze alot when I type and really annoying.

metie said:
I don't know if I'm allow to continue this thread as it is on the wrong section but this concern me alot and would appreciate any fix.
I found that there's Roger Rom, what I'm thinking is if it's possible to flash it to get a new fresh Rom installed and hope the problem would gone?
I read some thread on it but still not sure what steps should I do. Also if there's thing I should aware due to flash it to non AT&T Rom, maybe that I would not be getting an official update or whatever.
As long my focus is behaving correctly that is what I'm asking since I'm only using it to get my emails as a replacement of my blackberry. It freeze alot when I type and really annoying.
Click to expand...
Click to collapse
You could try that. For me, I want to avoid reflashing the ROM.
I have the Rogers ROM on my phone at the moment (it was a Rogers phone) and can assure you that they do provide the official updates (although no Tango yet).
If you're comfortable with the flashing process and don't mind losing all of your data, a fresh ROM could be a bit of a blanket fix.
jt

Bluetooth Fix

Hi to all
Suddenly my bluetooth won't find any other devices even though it's on it says searching, it can't be seen either even if it's set to be always visible, tried searching through service menu no luck either, my phone is only 2 months old and was working great with my Nokia Bluetooth headphones with my cars audio system, and of course other phones.
Allready repaired phone with Sony pc companion with no luck there, everything else works fine.
Please any help or tips to fix bluetooth please can't afford to get a new phone, in my country there no Sony service center.
Thanks in advance
Sent from my C5502 using xda premium

http://talk.sonymobile.com/t5/Xperia-Z-ZL-ZR/Bluetooth-not-working-in-Xperia-ZR/td-p/346565
http://talk.sonymobile.com/t5/Xperia-Z-ZL-ZR/my-xperia-zr-bluetooth-problem/td-p/372859
http://forum.xda-developers.com/showthread.php?t=2419326

All ready tried everything from the link still not working
Plz any other help much appreciated
Sent from my C5502 using xda premium

is your bootloader locked? or unlocked?
you can report here about your problem and please do explain it http://forum.xda-developers.com/showthread.php?t=2530747

My Xperia ZR gets the same problem around a week after purchasing.
Recently I found a way to temporarily solve it (most of the time it stop working right after I release my fingers).
My English is not good. Hope the following elaboration is clear enough.
Use the thumbnail to give some force on the right side (when looking at the back) of the flashlight over the NFC icon, and at the same time use another finger to give force at the edge on the left side of the front camera (when looking at the front).
The Bluetooth usually works when I do so.

YES! it does work i did the same thing looks like something is loosy in there there should be a connection problem i will open up my phone tonight and report it back, i just came here to say its a hardware problem in my guess cuz cyanogen rom didnt solve the problem either thank you sir
for those who dont know where to push, open the back cover and put some pressure on where you see "2nd MIC" push on the whole of microphone itself

dragunov_lq said:
YES! it does work i did the same thing looks like something is loosy in there there should be a connection problem i will open up my phone tonight and report it back, i just came here to say its a hardware problem in my guess cuz cyanogen rom didnt solve the problem either thank you sir
for those who dont know where to push, open the back cover and put some pressure on where you see "2nd MIC" push on the whole of microphone itself
Click to expand...
Click to collapse
Thanks for confirming!
Hope you could give us some guidance in fixing it ourselves. My phone is still within warranty but I doubt if the service centre will listen to my explanation of the problem or would simply try fixing it by reflashing the firmware and then tell me it is not fixable.

yes the bluetooth does starts working when pressing at the back near the nfc icon..thnx for the temporary solution..:good:

You are welcome.
The solution doesn't help much as Bluetooth will soon stop working (on my phone it stop working once I release my fingers), but it may show that there have been some problems in the manufacturing process as a lot of people encounter this problem.

ok what i think is this is a weak connection point in there and i wanted to disassemble the phone but some parts of it are attached with some kind of tape that makes it water proof, so i dont wanna lose the water resistance option on this phone at all and i stopped right there till i find a disassembly guide somewhere before i go further
and if anyone found something please let us know
thank you
and yes its just a temporarily fix to push in there and push a little harder to make it last longer but again not permanently!
EDIT: ok guys check this out
http://www.etradesupply.com/blog/sony-official-reveals-waterproof-cellphone-repair-process/
i dont think that we can fix this problem by ourselves, it needs special equipment and we dont have anything like these so ummmm no option for fixing it by ourselves i guess ...

Thanks to everyone luckily pressed in the right place and bluetooth is working again, so helpful even if it's not a permanent fix, now is it possible to identify which group of phones have this issue??? May be by date or color of phone or place it was manufactured....
Sent from my C5502 using xda premium