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,
Related
Hello all,
I'm just now debating on whether or not I need to exchange my new Tilt in for another one, or if this is just normal break-in behavior.
The scroll wheel is very erratic, sometimes when scrolling down it will go up instead and reversing the scrolling motion will cause it to freak out (go down once then scroll up like crazy). Also pressing the scroll wheel in to select/click on something often doesn't work forcing me to try several times to "click" on what I have selected.
The scrolling action is nowhere near as smooth as my Hermes, is anyone else having these issues?
******* separate but related issue *******
If it is indeed a hardware issue, does anyone know of a way to restore the bootloader back to AT&T's ... I flashed HardSPL and think I should probably put it back to stock.
Thanks,
Dave
same problem
i am having the same issue, wondering if i should go back to that nasty blue slut of a rom
FEATURES
SuperCID / Security Level=0
Does not check NBH signatures
Based on 1.50 MFG bootloader, rtask enabled
Accept any password
Model ID check only 4 chars
SPL overwrite DISABLED (to bypass, use SSPL-KAIS.exe)
I guess using the SSPL-KAIS.EXE and then flashing an AT&T om would solve that.
Cheers,
Cactus
reitjam said:
i am having the same issue, wondering if i should go back to that nasty blue slut of a rom
Click to expand...
Click to collapse
I was having the same problem with the AT&T ROM, but admittedly was not running it for very long before pof released HardSPL.
That's what makes me think it's hardware related.
le_cactus said:
FEATURES
SuperCID / Security Level=0
Does not check NBH signatures
Based on 1.50 MFG bootloader, rtask enabled
Accept any password
Model ID check only 4 chars
SPL overwrite DISABLED (to bypass, use SSPL-KAIS.exe)
I guess using the SSPL-KAIS.EXE and then flashing an AT&T om would solve that.
Cheers,
Cactus
Click to expand...
Click to collapse
Thanks Cactus,
I haven't checked the SSPL thread today, I saw that pof closed it last night because it was bricking a lot of phones. Thought he mentioned that he was going to try to get a working one out soon.
Thanks again for the reply.
sirsycho said:
******* separate but related issue *******
If it is indeed a hardware issue, does anyone know of a way to restore the bootloader back to AT&T's ... I flashed HardSPL and think I should probably put it back to stock.
Click to expand...
Click to collapse
SSPL v1 is just fine to flash an SPL or a splash screen, it will not work if you flash a full NBH containing OS becuase the NBH buffer is smaller on 0.92.
thanks pof!
Erratic scroll wheel persists across ROMs
Well I flashed back to AT&T ROM this morning and have been playing with it all day, and the erratic behavior is still there.
Given that only one other person complained here, I think it might be my device. Gonna go see my AT&T guy about an exchange.
Thanks for bearing with me.
sirsycho,
Let me know if you got a new device and it is better, please. I am having issues with having to click the scroll wheel really hard to get it to register at times. On another note, unlike all the other keys on my Tilt keyboard, the 's' key barely goes down when you press it and it doesn't click like all the otthers. This causes me to instinctively hit it multiple timessss so I get a lot of Ss in a row. Anyone else?
I have the same problem. It sometimes works and sometimes it dont.
willieb9000 said:
sirsycho,
Let me know if you got a new device and it is better, please. I am having issues with having to click the scroll wheel really hard to get it to register at times. On another note, unlike all the other keys on my Tilt keyboard, the 's' key barely goes down when you press it and it doesn't click like all the otthers. This causes me to instinctively hit it multiple timessss so I get a lot of Ss in a row. Anyone else?
Click to expand...
Click to collapse
My new device is on the FedEx truck for delivery today... I'm going to try it out with the standard AT&T ROM for a bit to get a good baseline and then flash to HTC's... I'll try to post an update tonight.
Thanks.
sirsycho said:
Well I flashed back to AT&T ROM this morning and have been playing with it all day, and the erratic behavior is still there.
Given that only one other person complained here, I think it might be my device. Gonna go see my AT&T guy about an exchange.
Thanks for bearing with me.
Click to expand...
Click to collapse
Not you're device. I had this issue prior to unlocking, then with the htc rom and again now with the att rom. To me, it looks either hardware issue, or something lower level is the OS that is common to all current roms. PErhaps the sensitivity of the wheel needs tweaking somehow.
I had issues with my scroll wheel as well. Coming from an 8525 I was like WTF did they do to this wheel? Sometimes the click wasn't registering, but either it's broken in, or I've adjusted my habits because it seems OK now, though not as solid feeling as the 8525 was. I'm sitting here with both the 8525 and Tilt in my hands and the wheel on the 8525 is definitely better.
I'm experiencing the same problem. The wheel feels scratchy when rotated, unlike my Hermes which was smooth. Usually wheels of this type are metal contacts against a circuit board, which use a binary gray code to register direction. I'm thinking its been designed poorly. Perhaps the Hermes unit was $.02 more money.
I wonder if we can replace it with a Hermes unit?
thanks sirsycho.. Update us once you get your new one.
Update with new Tilt and ATT ROM
ok... I'm still running the ATT ROM and still having the scroll wheel issues. Exactly the same things mentioned by others here... scrolling doesn't always register and when pressing in on the wheel I have to do it a couple times before it actually works.
On a side note, it seemed to be getting better on the older device before I switched, but as was mentioned above, that might just be me getting used to the substandard hardware (both of my Hermes work sooo much better).
I'll probably try this out through tomorrow before I flash the HTC ROM... I'll post again if anything improves.
Same scroll wheel problems for me (I have a Tilt). It sounds like maybe it improves as you break it in, so I'll give it a few more days before returning. Grrr....
Same problem here with my first Tilt. I returned the next day because this thread hadn't popped up yet so I thought it was just me and one defective unit. I subsequently got one that (knock on wood) has performed much better. Still notice a few jutters here and there, but the wheel doesn't feel as "scratchy" as mentioned before.
When I had my first Tilt, I noticed it much more when moving the wheel slowly. Here's hoping the problem doesn't start again because so far so good with my new one.
hello i'm using htc Tytn II
rom version : 1.81.707.0 WWE
rom date : 09/05/07
Radio version : 1.27.12.11
Protocol version : 22.45.88.07H
CE OS 5.2.1620 (Build 1825.0.4.2)
and everything works fine up,down and push.....
cheers
Just got a Tilt 3 days ago
Just got a Tilt 3 days ago and Im having the same erratic scroll wheel problem.
I see that this is an old thread, so I'm wondering if any conclusion as to this being a hardware or software problem have been made?
Thanks
I noticed on the Hermes page there is a HTC Home version 2.1 available for the Hermes that has been patched.
Is this available for the Kaiser? Noticed for a number of them it states uninstall previous version, but I dont really have the option to on my Vario 3.
I would like to know this too. Is there any info about it?
It works just fine.
So installing 2.1 the hermes version from:
http://forum.xda-developers.com/showthread.php?t=327646
Will be ok?
How can you check your current version?
Electronic Punk said:
How can you check your current version?
Click to expand...
Click to collapse
htc home customiser by pocketemu.com will tell you what verision of htc home you have.
Jygar said:
I noticed on the Hermes page there is a HTC Home version 2.1 available for the Hermes that has been patched.
Is this available for the Kaiser? Noticed for a number of them it states uninstall previous version, but I dont really have the option to on my Vario 3.
Click to expand...
Click to collapse
Is it a official release? Dont wanna have "self-made" junk..
Bram87 said:
Is it a official release? Dont wanna have "self-made" junk..
Click to expand...
Click to collapse
then you won't get much, everything here is ripped from other roms and updated to fix bugs or enhance the original design. The original HTC Home had many issues such as weather was only for Euorpe, the email link never opened the correct folder, it would jsut open whatever was last opened, and there were other issues too. Someone fixed those issues, repackaged, and posted here. HTC HOme 2.1 fixed the weather app to allow any city to be added to the weather XML file.
Note: HTC Home is an offical release, but slightly modify in ver 2.1 with help from some of the users here.
I dont know what I would do without the "self made junk" it all works fantastically!
Well I will be looking to install 2.1 tomorrow over my vario 3 htc home 1.5.
Hey, I have a novel idea, lets all show up, start posting, and insult the developers and cookers here (who absolutely kick the arses of the OEM developers) and accuse their intense and brilliant efforts as being "home made junk".
I bet we get A LOT of good advice and help!
ALL ABOARD!!!!!!!!!!
Ok. lets not fight.
Does it or Doesnt it work for the Kaiser. Has anyone installed and tested it?
Does it work properly? are there any delays (processing wise)?
Does it actually make a difference, do you see and feel a difference?
Would you recommend it?
bluemamba said:
Ok. lets not fight.
Does it or Doesnt it work for the Kaiser. Has anyone installed and tested it?
Does it work properly? are there any delays (processing wise)?
Does it actually make a difference, do you see and feel a difference?
Would you recommend it?
Click to expand...
Click to collapse
It DOES work with Kaiser.
It DOES work properly, no delays.
Hm.. tricky one
Yes.
gabriel31337 said:
It DOES work with Kaiser.
It DOES work properly, no delays.
Hm.. tricky one
Yes.
Click to expand...
Click to collapse
Thanks for your answer
Aye it does work, god bless the cookers!
So, which one do you intall on a kaiser?
1. Install on HTCHome Dir and With Brghtnes Fix for Hermes
or
2. Install on HTCHome with NO Brightness Fix
in my Kaiser Home 2.1 wil not install. Certificate Error or deny permission is the "error code".
Both on phone memory and Storage card
HELP!!!!
help needed, i have broken my htc touch phone...
first i downloaded the htc home v2.1 hermes cab and installed it , which all went fine but then i noticed that the brightness tab was working so i went and downloaded HTC Home v2.1 Directory And Brightness Fix and thats when things went really bad.
my phone rebooted and the screen turned off. when i plugged it into the pc after a timeout the screen came back on but if i touch it instead of getting brighter it turns off until it timesout again.
i un-installed both versions via the pc (although the UI didnt go back to the old 3 button tab home screen - still has 6)
this time a little better , screen does turn off when i touch it but it doesn't turn on either when i push the on button at the top until after the timeout.
dont know what to do now?
jimmypop said:
help needed, i have broken my htc touch phone...
first i downloaded the htc home v2.1 hermes cab and installed it , which all went fine but then i noticed that the brightness tab was working so i went and downloaded HTC Home v2.1 Directory And Brightness Fix and thats when things went really bad.
my phone rebooted and the screen turned off. when i plugged it into the pc after a timeout the screen came back on but if i touch it instead of getting brighter it turns off until it timesout again.
i un-installed both versions via the pc (although the UI didnt go back to the old 3 button tab home screen - still has 6)
this time a little better , screen does turn off when i touch it but it doesn't turn on either when i push the on button at the top until after the timeout.
dont know what to do now?
Click to expand...
Click to collapse
No idea what you did. Just back everything up without touching the screen and perform a hard reset. Hopefully you have an automatic installer when rom boots back to its original state.
can some1 test if igo8 is working nog with this home version?
thnx
NoFatePPC said:
can some1 test if igo8 is working nog with this home version?
thnx
Click to expand...
Click to collapse
This home version is probably cooked in the rom you're using.
This phone is making me like...crazy!
and this is why:
I synct some playlists to the phone with windows media player 10, suddenly all playlists on my diamond are empty.
When i removed all the playlists on windows media player 10 to sync them again, it deleted all my songs!
now i got all my songs onto the device again, and wanted to alter 1 playlist, it took windows media player 6 minutes, to just alter, replace, 1 pooping playlist!\
Its not possible to remove a playlist created in the touchflo music player itself.
Not able to select it and then delete it.
Half of the icons in the games folder are ****ed up, we already have a thread with solutions(i tried all of them), but none of them worked.
And the performance, even with the tlr rom or whatever the name was, the diamond still goes slow!
And the battery depletes quickly, with auto attach off, and incoming beam off.
Cant receive a file with bluetooth, with incoming beam on or off, it keeps saying my pc is a new device and asks if i want to set a password, no matter if i set a password or not, it goes back to the menu, and still says my pc is a new device
And i used a mod of the diamond tweaks thread, to auto lock my diamond when the screen goed off.
Well, 1/5 times, it autounlocks itself when i turn the screen back on. not good...
And finally, the opera browser is sometimes not doing what i want. sometimes goes to a random place on the page, if i move and let the stylus go, it moves back to that random page, to fix this i need to quit, then restart opera.
This happens about 1/5 times i use opera.
Is this where i payed 481 euro's for...?
Any ideas how to fix this sh!t is welcome, i already did a hard reset to try getting rid of some problems.
borgqueenx said:
This phone is making me like...crazy!
and this is why:
Click to expand...
Click to collapse
Nothing to complain about the phone?
marco899 said:
Nothing to complain about the phone?
Click to expand...
Click to collapse
what do you mean?
theres a whole list of bad things there.
btw: forgot to mention that the diamond stylus made some nasty scratches on the screen when wiping over the screen in opera to scroll page, or goto next photo in touchflo, ect.
Got a protector included for that.
Install a fresh rom, I don't have any of your problems.
I use bluetooth a lot:
Sending files (goes hell fast), don't want to use cable when using .cab files here
For my parrot
For use as a modem (have reached 120kbyte/second) when online with phone!
All flawless.
I have very very good results with HTC's own new rom update via e-club.
TLR nr. 2 was quite buggy at my phone.
GOod luck!
borgqueenx said:
This phone is making me like...crazy!
and this is why:
...
Any ideas how to fix this sh!t is welcome, i already did a hard reset to try getting rid of some problems.
Click to expand...
Click to collapse
Spare yourself next trouble to come and sell it, as I did with mine
czbird said:
Spare yourself next trouble to come and sell it, as I did with mine
Click to expand...
Click to collapse
what have you got now may i ask?
Humbly returned to my previous P535.
I must admit that apart from Diamond, there is currently not many devices to choose from on the market... Was thinking about getting P750, but still unsure...
Xperia scares me, mainly because of the unusual screen resolution (dunno how all the apps will handle it) and that also is supposed to be made by HTC...
Maybe Diamond Pro will not suffer from these newborn diseases that my Diamond had - will see...
i think im going for the iphone 3g. will be expensive though...
the touch diamond really disappoints me...
borgqueenx said:
Its not possible to remove a playlist created in the touchflo music player itself.
Not able to select it and then delete it.
Click to expand...
Click to collapse
Use the hardware buttons beneath the screen. You can navigate to the playlist you want to delete, and hold the 'enter' button to get the menu to get the 'right mouse button menu'.
Using your fingers it is impossible as it automatically selects the playlist if you press it. No menu will pop up.
borgqueenx said:
i think im going for the iphone 3g. will be expensive though...
Click to expand...
Click to collapse
What do you mean? It will be much cheaper than the Diamond.
I wonder if you're expecting to install applications on that phone, or do any customization...
Mwahahahahahha!!!!
Another Winer! XD
I'd give this post 5/5 for creativity, 6/5 for whining and -1 for usefullness ^^
you can almost FEEEL that you joined only after buying the phone, and I'd guess that it's your first WM one..
Anyway, regarding your problems..
If your phone really is that bad, it's probably broken (pre-production, grey, some dimwit dropped it in the shop or any other reason). In any case, return it by warranty, and get a new one..
Having so many people love this phone, and being able to fix the issues.. and only you and a handful of others run around whining.. Surely it's obvious that it's either a lack of hands.dll or a simple hardware failure..
I mean you should be smart enough to grasp it.... ermm.. right?
Cheers
P.S. Oh, and please don't be offended by this post.. It was mainly inspired by your post anyway, but it was written half-jokingly as I couldn't really answer seriously to that amount of QQ
@ 205_laCoste...
You're my hero.
Had a lot of trouble removing two playlists, but using the hardware buttons solved it right away....
Thank You!
I'm ready to throw my diamond out the window, for pretty much the same reasons. I paid way too much money to have so many problems. And I shouldn't have to flash a new rom. It should be good to go out of the box.
Before I'm also accused of being a whiner, there is a plethora of posts of people having the same problems....with no solutions. The bluetooth issue is a biggie. I tweak my phone to enhance it, but I shouldn't have to be a programmer to simply make it function properly. To suggest that is just arrogant.
There are things that I absolutely love about this phone, but simply as a phone it sucks.
most of the time it is not the fault of the phone but the person
using it.
a lot of people have come here after having a normal phone and
dont understand how to use this one.
treat it more like a computer than a phone.you dont have to be
a programer you just have to know how to read a thread and
follow the directions.
if you have a 1.37 rom you need to upgrade it to a 1.93.
1.37 is crap.okay it shouldnt have been but it was that why
it was upgraded to 1.93.
if you still dont get it then sell the phone.go buy a fruit
phone and get ripped off just like all the other sheep out there.
I have to stand up for nursie here. I've returned my diamond several months ago (yeah, it was driving me nuts) and am happily living with my P750... these offenses are absolutely not necessary and untrue as well as uncritically extolling the device - gee, it's just another PDA
czbird said:
I have to stand up for nursie here. I've returned my diamond several months ago (yeah, it was driving me nuts) and am happily living with my P750... these offenses are absolutely not necessary and untrue as well as uncritically extolling the device - gee, it's just another PDA
Click to expand...
Click to collapse
I have to agree, to an extent.
It's generally accepted on here that the Diamond is badly configured out of the box, which is why new users are recommended to flash a new ROM. This is not a good thing, although it's great we have such a good community of chefs to help solve the problem.
What's less well accepted is that much of the HTC software on the Diamond is slow and awkward. I'm talking about TF3D and the HTC dialer in particular, get rid of them and you can make the Diamond a great little phone just like your P750.
964rs777 said:
most of the time it is not the fault of the phone but the person
using it.
a lot of people have come here after having a normal phone and
dont understand how to use this one.
treat it more like a computer than a phone.you dont have to be
a programer you just have to know how to read a thread and
follow the directions.
if you have a 1.37 rom you need to upgrade it to a 1.93.
1.37 is crap.okay it shouldnt have been but it was that why
it was upgraded to 1.93.
if you still dont get it then sell the phone.go buy a fruit
phone and get ripped off just like all the other sheep out there.
Click to expand...
Click to collapse
I upgraded to 1.93. And I'm quite proficient at reading and researching. I'm also very proficient with current technology. I get it. What you don't get is that a consumer spending big bucks on this phone shouldn't have to resort to advanced tweaks (which I understand, BTW...you won't find me here asking newbie questions) in order to bring the phone up to basic performing standards.
Again.....yours is a fine example of ignorance masking itself as arrogance.
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.
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.