Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Wont get past the xda boot screen....

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

I was having the same issue until I disconnected the phone from usb.
It works great!

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Yup that was my issue too

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Not sure if this is just a problem with my end or this new kernel but since I installed this new kernel and module Ive been having a small problem with the keyboard. When Im typing on the physical keyboard sometimes one of the keys will get stuck and make a lot of ex.vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
at lot. I didnt notice this happening on any of the other builds I've used just this one it could be my end though just pointing out what Im experiencing.

Thanks for this awesome build tho its nice not having to memorize the keyboard anymore :)

Sprint Xandroid using 1/2/11 build

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

I spoke with WisTilt2 about this, we're betting it's the same issue we've had all along, just exacerbated by the system_server bug we're encountering. I'll mention it to him again, just to see if any of the hooks he's employing could cause this... as I had the same probelm, and that's basically the answer he gave me - that this bug is existing. I have a feeling there's something in his code that's making it worse tho. Thanks for pointing it out ;)

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Its not a problem I just delete them I just wanted to provide some feedback. Thanks for all the hard work arrrghhh

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Well, I feel it is a problem, and I do appreciate your report. We have a feeling it's related to that system_server bug as I stated earlier, which honestly seems like it's going to be difficult to track down. I have faith in our wonderful dev community... I just have a feeling this one is going to take a while to sort out.

We'll get there. Making leaps and bounds with hardware, just need to clean up all the code methinks!

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

I only get the repeated letter issue when my phone is just booted and before I do they voice mail trick. The voice mail trick always fixes that bug on my phone.

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Yea, I think that just reaffirms our suspicion of it being related to that durn system_server bug. Man I hope that gets fixed soon...

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

my rhod500 often lost signal when i use 1/2 and 1/1 kernel. i try on fxr03 xdandroid and neopeek r5 build. i dont know how to fix it :(

Re: [TESTING] New Kernel (Speakerphone/autobl)
 

not sure if this is important, but i just noticed that you never have to touch the screen to wake it up if it is plugged in and charging.

Re: [TESTING] New Kernel (Speakerphone/autobl)
 

Because it's never sleeping ;)

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

nice build.. only problem is that i ran angry birds and graphics are glitchy(color banding),but fast..

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Use this one!


http://forum.ppcgeeks.com/tp2-androi...ally-well.html

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Ah, about time I bumped this thread... first post updated guys.

Here's what's new - fixed touch to wake, caps/FN lights. More panel deinit stuff - should get significantly better battery drain compared to 1253 (assuming both kernels are sleeping - LED=GREEN!)

Enjoy, let me know how it goes!

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Wooohooo!!! Thanks bud!!

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

NP!

I did find an issue, at least on my RHOD400 - caps/FN LEDs are reversed, and the caps lock doesn't necessairly always show the correct state. I'll let WisTilt2 know... other than that, let me know what you guys find!

I'd also be curious if the buttons are reversed for all devices - or if it's just the 400. I'm betting the 300 will be flawless, I'm curious about the 100/210 guys.

Update - Seems the touch to wake issue is still present for me as well... again, I'd be curious to see if anyone else experiences this - when the phone is sleeping (green LED) you have to touch the panel where the lock swipe is to wake the phone.

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Just installed this, will be running it for a while to give it a spin and provide feedback.

Initial impressions, I can confirm that the rhod400 buttons are reversed.

Also, FN doesn't always show the correct state either. This can be seen by a simple test. Press FN repeatedly until Android disables FN again, observe that the light stays on. Same works for the Caps.

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Yup, sorry just noticed didn't mention FN has the same behavior as caps. First round, and unfortunately I didn't test this with WisTilt2 like I usually do... he posted it around midnight, and I was already in bed ;).

Enough excuses tho - I'll let him know this initial feedback, and hopefully he'll crank out another test kernel.

Thanks guys!

Update - seems I might have spoke too soon on the touch-to-wake issue... still needs some work, but if I'm patient the screen usually does come up - but sometimes it takes so long it just goes right back off... Yet another thing to put on the list of things to mention to WisTilt2 ;).

Confirming results of ahhh. Also does not stay on for double press aka always on fn/cap.

Thank you ahhh (wiz prollly wont see this....)

Rhod400 FRX04 test 1253 kernel

Re: [TESTING] New Kernel (Speakerphone mic/keyboard bl!!!)
 

Am I now "ahhh"? lol.

Anyhoo, seems the RHOD300 (aka Tilt2) is the only device where the FN/Caps lock is correct. I haven't heard from any 500 users, but I'd venture to bet theirs is reversed as well.

I've passed on the info to WisTilt2, I'll hopefully see (well, at least talk to) him tonight!

Re: [TESTING] Updated 1/26/11 New Kernel (Caps/FN LEDs)
 

just the fact that this, How to control any Android phone from Windows / Mac OS X / Linux via USB | GadgetLite - Latest gadgets and technology news, works, is almost "good enough" for me lol sitting here playing with this complete with jaw on floor with happiness. yea yea, i'm a lil behind on it for sure....

Re: [TESTING] Updated 1/26/11 New Kernel (Caps/FN LEDs)
 

Just loaded up on my RHOD 500, and here's the behavior I observed for the FN/CAPS lights:
- Illumination is reversed (FN turns on CAPS light, and vice versa).
- Light extinguishes after first keypress (even if CAPS lock or FN lock is set).
- No problems with repeating keys or symbols.
- When waking from sleep mode, the screen requires a touch to illuminate, unless you wait approximately 5 seconds. It will immediately go back to sleep unless you touch it within 1 second of it coming awake.
- After waking, the brightness level is dimmed substantially. Using the brightness slider under display settings restores the brightness to where it should be.
- Keyboard illumination works like it should.
- Angry Birds seems fine (only checked one level).

I'm always impressed with the progress being made - although this doesn't seem to work quite right for the RHOD 500, just the fact that you're hooking the lights seems to be a major accomplishment! I'll watch for the next build and see how it performs. =D>

Gremlin

Re: [TESTING] Updated 1/26/11 New Kernel (Caps/FN LEDs)
 

New kernel folks. WisTilt2 mostly fixed the Caps/FN - they almost always reflect the correct state. The only time I find they don't is if you hit the button 3x - basically cycling thru completely, the LED stays on until you type a key.

Might be good to note, whatever userland Android actually shows is what is accurate. We're just trying to get the LEDs to match ;).

Let me know what else you find - WisTilt2 is already aware of this issue. Other than that, they seem to work great for me!

He also included some more power management fixes, but they're only slight - he wanted to see if anyone noticed a difference in drain. I don't watch it that closely, but if any of you guys do let me know if you see a diff. Thanks!

Re: [TESTING] Updated 1/26/11 New Kernel (Caps/FN LEDs)
 

TO ALL!!!

Grab the kernel I _just_ posted in #1. WisTilt2 said he missed a few things in the last kernel, and that's probably causing the issue with resets to WinMo.

Basically a timing value on the screen timeout. So please, grab the new kernel and send it thru the ringer!

Re: [TESTING] Updated 1/26/11 New Kernel (Caps/FN LEDs)
 

Thanks for the update. Like you said, for the most part things are working correctly now.

I peered at the IRC kernel logs, and it seems like he's just coding it into the kernel when to light the lights for now as opposed to actually hooking it into Android, and will be saving the real hook-in until later.

In light of that, I'd say that the lights are working perfectly fine now. There's a variety of ways to easily to cause them to become misaligned from Android (press fn followed by shift, press fn/shift on the home screen and then bring up a text box, hold fn/shift and press a letter, slide the screen closed after pressing fn/shift, etc.), but it doesn't really seem worth his valuable time to worry about it.

Re: [TESTING] Updated 1/28/11 New Kernel (Caps/FN LEDs)
 

Regarding the CAPS Lock/Fn Lock lights, I can (happily) report the same results on my RHOD 500 - lights illuminate when they should, and stay on. The only problem is the (already noted) issue where if you press the button three times (or just once after you've been in CAPS Lock or Fn Lock), the light does not extinguish until another key is pressed.

Unfortunately, I'm still having the same problem with the screen after the phone sleeps - it will not wake until it is touched, and if it's not unlocked (I have the pattern lock on) within a few seconds, it goes back to sleep. The issue with the brightness setting being reduced after sleep is also still present.

Re: [TESTING] Updated 1/28/11 New Kernel (Caps/FN LEDs)
 

Yet another kernel guys. FN/Caps should be completely fixed, except for ironically the RHOD300/Tilt2. It now has reversed LEDs, until WisTilt2 can incorporate a detection method (which is fairly simple, just needs to be done ).

Additional fixes to try and improve touch-to-wake issue. Enjoy!

Re: [TESTING] Updated 1/28/11 New Kernel (Caps/FN LEDs)
 

Thanks, running this now, and works as advertised. Everything is smooth so far.

Re: [TESTING] Updated 1/28/11 New Kernel (Caps/FN LEDs)
 

getting great performance with this on the 1-28 froyoX. This build of sys is seriously out of control different. gotta give it a whirl argh if ya haven't yet, curious to hear how much you have neg on it cuz it has to be getting slim.

anyhow, panel comes on without touching the screen EVERY SINGLE TIME. Press power, backlight only for ~2secs, then panel reinit to unlock screen. and i caught that wis added a second to the reinit i believe so this behavior is expected in the 29th edish. Reminder I am NOT oc'ed, alter only button wake and home/power in freshest rootfs, and running dudes froyoX 29th edish.

summed up version: what touch the panel to wake issue? haha


update: booting to android with spkphn on to get TiKL to work was interesting, talking went a lil longer than normal it felt. The boot process stopped right before "__________________ANDROID__________" in haret, (which could be the right place as always, just noticed today tho), then just changed to the way it operates in android with static for no reason. open line, complete with static and a lil of cool craaaazy noises. yay for radio waves! which makes one wonder what the inside of our heads sound like.... boots all the way up with static and is chillin at home screen, get a txt and the skphn test was kinda interupted/made this discovery of the skphn gettting shut off by the notification sound for the txt message

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

On my rhod400, if they phone is in sleep with a green LED, 100% of the time, it will turn on the backlight and then not power up the screen in time to prevent the lock screen from shutting itself off again.

If the phone is in orange screen off mode, it manages to pull up the screen 100% of the time, but some times when it is slower, the screen will only be visible for a split second before turning itself off again.

Question, does Windows Mobile just not fully shutdown the panel or what? Power on is instant in WinMo.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

Question to you - are you overclocking? I'm going to try not OCing to see if the panel wake issue is any different.

To answer your question - I'm sure WinMo correctly (fully) shuts down the panel. It's not correctly (IMHO) being brought up in Android at the moment. WinMo (for me at least) gets pretty good battery life when the screen is off. We're getting close to that point when Android is sleeping - not sure we're there yet, but I'm getting plenty of battery life to run all day. In sleep, I'm getting just about 1% drain, maybe less.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

Nope, no overclocking here.

I think with this kernel I might actually be getting better battery life than I remember getting in WinMo. It's been so long since I've run WinMo I kinda forget, but I remember running out of battery before a day was over sometimes even without heavy usage. With this kernel, when it's sleeping I see pretty amazing battery life. I just took it out for a few hours just now and my battery life is consistent with yours, maybe 1% an hour, maybe less even.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

wrong thread.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

My results are somewhere between manekinekos and yours arrrghhh. About 20% of the time the panel wakes properly, the rest of the time I have to tap the screen to keep it on long enough to swipe. I am also not OCing, I'll try turning on the OC and see if it helps.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

Well that makes me feel a little better. I was trying to figure out why MassStash's RHOD400 was waking perfectly and mine wasn't. The only thing we could figure out is that I was OC'd and he wasn't...

However, WisTilt2 said on his RHOD300 that panel wake was working 99% of the time, and he's OC'd to 700mhz. Oh well, I'll bug him about it next time I see him, we'll get it workin!

Edit: I had been running nearly 18 hours off the charger, and I was still at 70%. Amazing... Granted I wasn't using it a bunch, but sync was on and it wasn't 18 hours of sleep either. Then the tragic SoD... so I'm not sure how long it would've gone, perhaps 2 days? I'm going to see if that last_kmsg has any goodies in it, I want to get rid of this SoD and system_server issue so bad... I think I could easily do Android 100% of the time with those issues gone...

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

Turning on OC didn't fix my wake up, it still doesn't wake up fast enough most times, I can't really say whether it helped or not, if it helped it didn't help significantly.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

New kernel guys.

Somehow, WisTilt2 says even better battery life... I know, unbelievable.

Better panel wake as well!

RHOD300 FN/Caps still reversed... Sorry.

Re: [TESTING] Updated 1/29/11 New Kernel (Caps/FN LEDs)
 

I'm getting maybe a 50% success rate with waking up fast enough. Getting closer. Obviously too soon to comment on the battery usage.

Dl'ed the 30th pack n should the files be dated from the 28th??

Yea, still 99% panel init for me, friggin awesome. Oh how I long for this panel response on nand....


FROYO X, Tapatalk