Database Develop

Serious Tilt Problem

Ive Noticed Ever Since Purchasing My Tilt (about 3 Weeks Now) I Have Had To More And More, Have To Sleep On The Couch (my Wifes Doing). Is There A Rom Or Hack For This Problem.
......sorry I Could Not Resist.......

Maybe you should see if there's a CAB available that will remove her. I know there's a Yellow cab ready at all times
Also, see if you can find a registry hack that will disable the annoying capitalizing of every word in your posts. We Don'T Have To Capitalize Every Word Cause It's Annoying, and it wont qualify you for better parking if your CAPS lock is only partially disabled.

KD8DNS said:
Ive Noticed Ever Since Purchasing My Tilt (about 3 Weeks Now) I Have Had To More And More, Have To Sleep On The Couch (my Wifes Doing). Is There A Rom Or Hack For This Problem.
......sorry I Could Not Resist.......
Click to expand...
Click to collapse
I have had the same problem! And it got pretty bad for a few days, until I figured out a solution.
This is a bit complicated so pay very close attention (or you may want to jot these instructions down to refer to later):
1. turn the phone to look at the right side of the unit
2. locate a tiny button with a little red symbol on it. (You may have used this jewel of a button to awake your awesome Kaiser (a.k.a. at&t Tilt) phone when it has fallen asleep (while you got distracted for a few moments).
3. PRESS this button for only 1-second and release. I have learned - through trial and error - that this button also turns OFF the phone. BUT DONT WORRY! It's not really off, its just sleeping and you will still receive calls, text messages and even calendar event reminders (whew I worried about receiving these!).
I know these instructions can be very stressful, but they may have saved my marriage. I would highly consider you trying this procedure at least once an evening (like during meals, when your spouse is trying to communicate with you, and especially (grin) at 1am while your laying in bed browsing the xda-developers forums for all the cool tools, cabs and Roms out there and your wife rolls over and says, "don't you ever put that thing down??!!"
;-)

Sorry about the caps i wa not paying attention.

KD8DNS said:
Sorry about the caps i wa not paying attention.
Click to expand...
Click to collapse
I thought your post was funny. This place can use more light-hearted comedy.

ronfin44 said:
Maybe you should see if there's a CAB available that will remove her. I know there's a Yellow cab ready at all times
Also, see if you can find a registry hack that will disable the annoying capitalizing of every word in your posts. We Don'T Have To Capitalize Every Word Cause It's Annoying, and it wont qualify you for better parking if your CAPS lock is only partially disabled.
Click to expand...
Click to collapse
You have to make sure you get the right kind of cab though... It can be confusing because here in the DC area yellow cabs aren't yellow, they are bright orange??? You must be very careful because you must be sure you really want to do that before you run the cab. It is usually very painful, difficult, and expensive to uninstall the wife update. Even then if you manage to partially uninstall the wife, if you have added new devices to your PAN while the wife update was installed then it may take up to 18 years to fully uninstall the wife. It wrecks havoc with your network settings, and often once uninstalled the wife update will often take half of your network resources and permissions with it (sometimes all of them!). Also be very careful of MIL.dll. It often installs itself in the background when the wife update is being installed. MIL.dll is often considered spyware, nagware, and often it falls within both categories, but there is often nothing much that can be done about MIL.dll without uninstalling the wife update. Some feel it is worth starting all over again with just a bare-bones system, but most feel that the benefits of the wife update outweigh the negatives. It is better to live with the occasional problems that the wife update may cause, than to try and remove it.

Try hard reseting her. Hold down both of her soft nipples and stick your stylus in her butt. That should get quick results. haha

ronfin44 said:
Try hard reseting her. Hold down both of her soft nipples and stick your stylus in her butt. That should get quick results. haha
Click to expand...
Click to collapse
I knew I was doing something wrong, I kept putting her in bootloader mode but she said she'd never done that before!
Mike

ronfin44 said:
That should get quick results.
Click to expand...
Click to collapse
I thought sticking your stylus in the wrong hole caused permanent damage to your pins?!

Steve-C said:
I thought sticking your stylus in the wrong hole caused permanent damage to your pins?!
Click to expand...
Click to collapse
I'm using Dutty's special Bottylicious ROM. Works great with softcore resets like that! haha

LMAO! Maybe you could just install another cab Iv seen around, It's called abitontheside.cab, it can be simply installed without going through all the bother of unstalling the wife update. Just make sure you dont run both at the same time as Iv heard they can conflict with each other.

I bought my wife an iPhone, now she can't say anything because she spends just as much time surfing the web and playing with the other 4 things you can do with an iPhone

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,

Screen-> Fade to White-> Temporarily

From what I've been able to find from searching, I think my Tilt is about to bite the dust, but thougth I'd post the symptoms and see if anyone has any good info.
My screen has been occasionally fading to white. Not sure how else to describe it. It just sort of starts getting white, and within 2-3 seconds will be completely white. It is still working, that is, I can place a call (using MS Voice Command); I can play music.
I have SPB Mobile Shell on it, and a button assigned to go to the home screen. I can press that, and it will go to the home screen and display normally. If it is a hardware problem, I find it interesting that I can go back to the main screen. I suspect it is close to gone.
Any thoughts?
If so, anyone know what it costs to repair, and where to do that?

Sounds like a software thing to me, I hate to say it but try a hard reset. Do you have a 6.5 rom?

I've been thinking of doing a hard reset anyway, My memory is about used up. I'm not quite sure why. Probably should get it cleaned up.
No, I'm not on 6.5. I've been reluctant to make the move. I did some rom updates some time ago, and then the person working it decided to stop. I decided to stay with MFGR based roms after that.

ewingr said:
I've been thinking of doing a hard reset anyway, My memory is about used up. I'm not quite sure why. Probably should get it cleaned up.
No, I'm not on 6.5. I've been reluctant to make the move. I did some rom updates some time ago, and then the person working it decided to stop. I decided to stay with MFGR based roms after that.
Click to expand...
Click to collapse
Good thinking.

Likely NOT software but hardware -- could be the screen is going bad, or perhaps just the ribbon cable than connects the screen is broken or not seated properly.

burtcom said:
Likely NOT software but hardware -- could be the screen is going bad, or perhaps just the ribbon cable than connects the screen is broken or not seated properly.
Click to expand...
Click to collapse
So the hardware problem is just scared of the button he has assigned?
I have SPB Mobile Shell on it, and a button assigned to go to the home screen. I can press that, and it will go to the home screen and display normally.
Click to expand...
Click to collapse
Try putting the phone in the bootloader screen and let it sit there, that should let it go around the software.

Erm, yeah -- I guess that wouldn't be indicative of a hardware problem

Well, I am doing the hard reset. So far, no white.
Hmmm...lordy...I have a lot of stuff I try to put on this phone.
I wonder how much memory, both types, I need to keep available.

Don't put anything on the phone that you REALLY REALLY don't need. This is a taste phase and you need the least amount of BS on there.

Well, I've got most of what I need loaded, and have 61MB storage, and 63MB of Program memory free. Much better than before.
But I am still getting the fade to white occasionally.
I'm thinking hardware.
Anyone know if checking the 'ribbon' cable is user capable thing? I don't see it easily. I'll so some searching in the meantime.
Also, any feedback on cost and where for a new screen? Or do I just trash it when it finally goes?
[EDIT]
I am noticing that it particularly does it when I click the Windows (lower left) hard button on the front. I'm thinking it is related to a problem with that button.

Could be when you press that button you are flexing the cable enough to make it lose connection and go white -- this could be good news -- there are instructions scattered in this forum on how to take the phone apart. I'd recommend doing that and makeing sure the cable is firmly seated -- you should also inspect it for cracks.
Hopefully it's just a loose cable and making sure its in all the way will fix it -- if not you'll have to track down a new one.

Thanks. I'll do some searching for those instructions.
In the meantime, I called HTC just to get their thoughts on repair. First thing they told me was to upgrade the rom to the latest which is 3.57.502.2 .
I haven't been following ROM discussions. I need to check that out too. I wish I had seen or thought of that before I just spent a day with the hard reset/reinstall

did this get resolved?
I have the same issue. was it the ribbon cable?
update. I loaded a stock rom, and this appears to have solved the fade to white

Sorry...beeen away a bit.
I have not resolved the issue. It is intermittent, and hasn't happened for a few days now.
I searched and have found some instructions about taking the screen apart, but have not tackled that yet.
In my case I can't imagine changing roms making any difference, as I've had this rom for many months and it is just recently starting this.
I have found new LCD screens for this for ~ $30. I'm wondering if replacing the screen may be an ultimate solution or, if it is possible/likely that it is somethign else hardware related.
Been busy, and don't have the tools yet, so it may be a bit (or when it goes permanenly white forcing action) before I get any further on this.

It is definitely a hardware issue, my wife's tilt did the same thing, then it went permanent white. I first took it all apart looking for a bad ribbon cable or connection because it had taken a few good falls. But that was not it. So I bought a screen for about 30.00 online and shazam that was it!

Thanks for that info. I was thinking of ordering the screen, but concerned it could be something other than the screen (even though logically it would make sense that it is the screen.)

[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.

is there any way to reconfigure or disable the hardware power button during lock?

This might be completely impossible but basically I'm trying to make it as difficult as possible for someone to shut down the phone without entering a passcode (I have an HTC m8 so they can't pull the battery).
There's apps that will prevent someone from using the shut down menu but that doesn't solve the issue of a hard reset. I'm aware you can reconfigure what the buttons do when using the phone but I'm skeptical if that will effect it on that low of a level.
So is there any way at all to completely reconfigure the switches or is that basically built into the hardware? I looked around and haven't found much.
I know this is probably a stupid question but it's worth a shot. I can turn on the screen in many other ways so I'm not too worried about that.

First, this is the M7 forum.
Second, I doubt it. I am pretty sure that the hard reset functionality is hardwired or at least coded into hboot, otherwise it wouldn't be much good for rescuing a frozen phone. Why would you want that anyway? What do you plan to do if the phone freezes up?

iElvis said:
First, this is the M7 forum.
Second, I doubt it. I am pretty sure that the hard reset functionality is hardwired or at least coded into hboot, otherwise it wouldn't be much good for rescuing a frozen phone. Why would you want that anyway? What do you plan to do if the phone freezes up?
Click to expand...
Click to collapse
Doh! You're right, sorry for posting in the wrong place. I was at work and rushing to type this all up on my break.
You're wrong though, I found a solution. It's called Xposed Additions. And yea if my phone freezes up I basically have to wait until it dies. I'm willing to deal with that. I've had several phones stolen so now I have a phone that can not be shut off, can be tracked through GPS remotely, can take pictures remotely, and can listen to the microphone remotely.
Steal my **** again you lazy assholes. See what happens >

tstanley0426 said:
Doh! You're right, sorry for posting in the wrong place. I was at work and rushing to type this all up on my break.
You're wrong though, I found a solution. It's called Xposed Additions. And yea if my phone freezes up I basically have to wait until it dies. I'm willing to deal with that. I've had several phones stolen so now I have a phone that can not be shut off, can be tracked through GPS remotely, can take pictures remotely, and can listen to the microphone remotely.
Steal my **** again you lazy assholes. See what happens >
Click to expand...
Click to collapse
Make sure USB debugging is disabled also or adb could be used to bypass lock or reboot to bootloader.. [emoji14]

tstanley0426 said:
You're wrong though, I found a solution. It's called Xposed Additions. And yea if my phone freezes up I basically have to wait until it dies. I'm willing to deal with that. I've had several phones stolen so now I have a phone that can not be shut off, can be tracked through GPS remotely, can take pictures remotely, and can listen to the microphone remotely.
Click to expand...
Click to collapse
That is interesting. I wonder, though, if it truly disables the (hypothetical) hardware/hboot level controls should the phone freeze up, since Xposed would no longer be running.