NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery - Page 206

tiger2wander · #**2051** (**permalink**) 03-24-2011, 10:14 AM

I've just tested the new clean build and got same problem with recovery, and yes I think problem come from some key is not map correctly for RHOD500 and it simple get right way to go.

Are there any code to auto detect hardware board to load related keyboard map or we need to manual set it somewhere?

Don't get into recovery menu but I still can use adb to check something, but don't known where to check it LOL.

Is there anyway to restart adbd since it has PID = 1? I tried to kill it but failed, seen it has protected by kernel, because of init process :P

**[ACL]** · #**2052** (**permalink**) 03-24-2011, 10:46 AM

Quote:

Originally Posted by tiger2wander

I've just tested the new clean build and got same problem with recovery, and yes I think problem come from some key is not map correctly for RHOD500 and it simple get right way to go.

Are there any code to auto detect hardware board to load related keyboard map or we need to manual set it somewhere?

Don't get into recovery menu but I still can use adb to check something, but don't known where to check it LOL.

Is there anyway to restart adbd since it has PID = 1? I tried to kill it but failed, seen it has protected by kernel, because of init process :P

nope, you are getting confused with userland keyboard stuff. For recovery we use only the gpio keys which i already posted on the commit thats breaking it.

So the whole KB isnt working ? or what? remember i havent even ran this code and this is why i havent realeased a test kernel yet, so you are going to have to debug like the big boys do it

**Lmiller1708** · #**2053** (**permalink**) 03-24-2011, 10:55 AM

Quote:

Originally Posted by [ACL]

wowo you guys are fast.. i didnt even test it myself. I was just commiting stuff that we are behind on.

There was a haret patch that some key files around

Commit in linux-msm-rhod-nand in Linux on Qualcomm's MSM - Gitorious

May need to revert this then or fix it if this is the issue.

Revert Back to the old keylayout.

Top button = Home
Power button = screen off.

Thanks for keeping this updated!!!

tiger2wander · #**2054** (**permalink**) 03-24-2011, 11:10 AM

There are some keys not work such as: Fn, Caplock (still can function with some key), arrow keys. Almost remain keys are working, look like it has mapped with RHO400 or something else

I was test this in "Connect Bot" app.

@[ACL] I'm new with linux kernel and trying to dive into it

I'm good in shell but not good in kernel LOL

**[ACL]** · #**2055** (**permalink**) 03-24-2011, 11:40 AM

Quote:

Originally Posted by tiger2wander

There are some keys not work such as: Fn, Caplock (still can function with some key), arrow keys. Almost remain keys are working, look like it has mapped with RHO400 or something else

I was test this in "Connect Bot" app.

@[ACL] I'm new with linux kernel and trying to dive into it

I'm good in shell but not good in kernel LOL

not sure what you mean. But go ahead and knock urself out. I got more commits tonight so thanks for testing.

I commited a new tinboot this morning as well to remove the force cdma for gsmrs.

**[ACL]** · #**2056** (**permalink**) 03-24-2011, 11:42 AM

Quote:

Originally Posted by Lmiller1708

Revert Back to the old keylayout.

Top button = Home
Power button = screen off.

Thanks for keeping this updated!!!

Sounds like a plan. IF anyone has issues with us reverting back, speak now.

**arrrghhh** · #**2057** (**permalink**) 03-24-2011, 11:42 AM

Quote:

Originally Posted by [ACL]

not sure what you mean. But go ahead and knock urself out. I got more commits tonight so thanks for testing.

I commited a new tinboot this morning as well to remove the force cdma for gsmrs.

Nice, I'm sure they'll be happy

.

I was always curious tho, are we going to separate out GSM and CDMA builds like we do for WinMo? I was kinda hoping we could just detect, but if not... C'est la vie!

MassStash · #**2058** (**permalink**) 03-24-2011, 11:44 AM

recompileing this mourning, but i like key_home so my recovery went fine. I just had no service but i think i found my mistake, thus th recompile with tinboot commit...

I vote no revert! I see no real reason.... But i again, i like a da KEY_HOME, RHODIUM_END_KEY

ACL, props on the commits, lookin forward to tryin tonight's out as well

**[ACL]** · #**2059** (**permalink**) 03-24-2011, 11:51 AM

Quote:

Originally Posted by arrrghhh

Nice, I'm sure they'll be happy

.

I was always curious tho, are we going to separate out GSM and CDMA builds like we do for WinMo? I was kinda hoping we could just detect, but if not... C'est la vie!

its all detect and will be done by android and the recovery. So lets say ur ass for some reason wants to use gsm but u have a rhod 400. Well go to the recovery, advanced and boom force cdma. Cant get easier than that. Reboot and ur golden

edit: but this isnt done yet.. so ull have to wait :-p

**[ACL]** · #**2060** (**permalink**) 03-24-2011, 12:07 PM

Quote:

Originally Posted by MassStash

recompileing this mourning, but i like key_home so my recovery went fine. I just had no service but i think i found my mistake, thus th recompile with tinboot commit...

I vote no revert! I see no real reason.... But i again, i like a da KEY_HOME, RHODIUM_END_KEY

ACL, props on the commits, lookin forward to tryin tonight's out as well

haha.. good to know we have people with different points of views. But question, cant shit stuff be changed in android ? so yall dont have to run a custom kernel all the time? unless its hardcoded in android which i dunno about

nate/arrggg do you know?