Quote:
Originally Posted by peterm20
Like I've written before If i wait for it to go to sleep and then wake it up the nav buttons work again for some reason.
If you put the wifi tether app from the hero on our phones it says something about missing components from the kernel. I would figure it would be netfilter/iptables modules.
It seems the current eclair branch out isn't making anything that is bootable for me. Anyone else trying to compile their own image? After doing a sync about 2 days ago since then it doesn't make a bootable image.
|
Building an image from the AOSP repo? I have not tried -- I sort of feel like I should, but it seems like a lot of work and a lot of waiting, and other people's have worked just fine thus far. Plus I have not even begun to try to figure out what needs to be tweaked from the basic repo to make it work on our devices.
Quote:
Originally Posted by karafa
OK, tried the new kernel. Touchscreen is certainly better. Much more usable. So, thanks a ton for that. However, I can't seem to get wifi to start. It just says 'Unable to start' when I try to turn it on. Not too sure why.. Just created a new data.img like two days ago, using the 2.18 build and the kernel from the first post, and used the kernel on it today. Would that be the reason wifi doesn't work?
|
I switched up the module-building code. Made a nice clean build script and grabbed the wlan driver directly from the android source, to make it easier for other people who want to build kernels to copy my work. It didn't throw any errors, so I thought it was fine.
...I guess I was wrong.
Quote:
Originally Posted by eyepoker
some info on the power collapse....
i have a seidio 2000mah battery. Left the phone fully charge last night at around 12:15AM. This morning at about 9:15AM power seemed to be at about 50% - the battery widget i have showed that the percent charged was bouncing from around 63% to 45%.
i started browsing ppcgeeks.com and noticed that the battery dipped way down while navigating pages - i would swap back to the home screen and notice that the widget reported a low of 18%. While i was watching it to see where it would bounce it actualy went back up to 53% and stabilized there, only going up or down by 1%. I went back to the browser and played some more - again the battery indicator dropped way down and again going back to the home screen i saw a low of 17% and then after about a few seconds it seemed to tabilize at a much higher value.
Related to the above, i tried to post this from my phone. i didn't have the patience to finish. Is there a way to disable the predicitve text thing that happens whhile you type? The phone was very slugish while typing. I'd wait for like 15-20 seconds before it caught up with me and then half of what i typed was what android thought i meant to type. I'm guessing that its realy taxing for android on this hardware to keep trying to figure out what you might be typing and then to show you what its guessing is the right word while you are typing. It can't keep up... maybe related to the phone being on for a long period of time?
Touch-screen.... seems to be better - i don't have to press as hard to unlock, just a simple swipe gets her done. Double/triple characters: It might be better, hard for me to say - the thing that android does with the predictive text is just throwing a wrench into typing in general... if i could turn that off I'd be really happy and then could focus on the real isues (2-3 character insertion).
About browsing... ppcgeelks.com realy tests the browser (related to the phone being on for 9 hours?)... Opera in WinMo 6.1 is a lot faster.
Wifi still works for me after updating with the 2/18 package. i didin't update everything, just the zimage and the modules.
|
Well, if you updated the modules and wifi is still working, then my previous guess might be wrong. I'll try to figure it out.
The battery fluctuations make sense if you look at the hacks we're using to calculate. The Windows Mobile battery driver takes actual account of the instantaneous battery discharge rate and battery charge rate (the draw and whether or not there's a charger). Unfortunately, we have an uncorrected value for charge, and a blank value for discharge. So you'll notice it jumps around a bit, but generally stays ok when you're charging... and jumps around a LOT depending on how much draw there is on the battery (3G active, wifi active, screen on bright), because we just have no way to factor that in to the calculations. That's why battery status is distinctly NOT in the 'working' column.
I'm with you on the software keyboards -- I can't handle them. Fortunately, the hardware keyboard is significantly FASTER in Android than in WinMo, so I generally just use that. Screen rotation's not so awful either.
Quote:
Originally Posted by SoCalSpecialist
i need help here guys..
i have a vzw touch pro and i cant get this working for the life of me.
i dragged and dropped all files onto my sd card and ran the HaRET exe and it stays stuck there.
is there a video possibly or if someone can take the time to sit and walk me thru step by step id really appreciate it thanks all!
|
Hi. We don't get a lot of VZW users, and the one dude who was working on the RAPH500 port got buried under schoolwork, I think, so he's no use. Where does the boot process die? Right at the start? Do you never even get the little tiny text scrolling by?
You could try contacting praxidike and seeing if he can tell you the changes he made... or you can grab his kernel over at the htc-android forums... but they are WAY out of date at this point.