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

[MassStash]

nah, latest compile for me makes MORE buttons work for me lol vol buttons didnt work before the latest kernel updates, and now they do. you change anything? i changed key_end to key_home. turns out recovery doesnt work any buttons if there's no key_home because of acl made it look for key_home. so worked for me without notice of this broken part....

[acl], maybe they blocked irc.... haha

[natemcnutty]

Originally Posted by MassStash

nah, latest compile for me makes MORE buttons work for me lol vol buttons didnt work before the latest kernel updates, and now they do. you change anything? i changed key_end to key_home. turns out recovery doesnt work any buttons if there's no key_home because of acl made it look for key_home. so worked for me without notice of this broken part....

[acl], maybe they blocked irc.... haha

Thanks, that confirms what I was wondering. That means ACL has to compile a new recovery that uses the updated button mappings. I've looked through the recovery files, and this must be compiled into android.recovery because I can't find it being analyzed by any of the scripts.

[Lmiller1708]

Originally Posted by natemcnutty

Thanks, that confirms what I was wondering. That means ACL has to compile a new recovery that uses the updated button mappings. I've looked through the recovery files, and this must be compiled into android.recovery because I can't find it being analyzed by any of the scripts.

'Is this with the current Mapping? Or the old ones?
'He will only have to recompile if they are the New ones... Which would be a waste of time when he goes back to the old keymapping.

[MassStash]

to work as off current commit, you have to make key_end = key_home. So to keep the same key mapping, acl need to release updated ASR... with advanced menu hopefully... :_)

[natemcnutty]

Originally Posted by Lmiller1708

'Is this with the current Mapping? Or the old ones?
'He will only have to recompile if they are the New ones... Which would be a waste of time when he goes back to the old keymapping.

Well, he actually committed the change to the new ones the way XDAndroid on Haret is. I don't know if we plan to revert it back to the old way or not, but the way it sits on the git right now, we need to recompile recovery.

[Lmiller1708]

Originally Posted by [ACL]

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

^^^^

Originally Posted by natemcnutty

Well, he actually committed the change to the new ones the way XDAndroid on Haret is. I don't know if we plan to revert it back to the old way or not, but the way it sits on the git right now, we need to recompile recovery.

It looks like he is already going to revert back.
I talked with him earlier today too and is the path he was taking...

Reason being is with the new keymaps (like Haret) we will lose the "recent items menu" and not be able to turn on the screen by the top button (it will just end the call, very annoying!).

[[ACL]]

ahh fellas.. there was a reason why i didnt auto-build this. It was because i didnt test, so come on give me a break with all the questions. If you roll your own kernel, im going to assume you know how to fix it. Its a simple fix, anyone can roll back.

Ok, i think i missed what nate said earlier about deploying the navipad file. That does not sound like a bad idea to me. I say this because if anyone wants some whacky layout, we simply android update the file and viola. Problem solved. So navipad for everyone. With that said i will have to leave the kernel as is for now and the install script needs to be modded.

Ok on to business. Nate did you test the mtd parts you posted? sure it does not break wifi ?

anyone test the new ril on the old build ?

[natemcnutty]

Originally Posted by [ACL]

ahh fellas.. there was a reason why i didnt auto-build this. It was because i didnt test, so come on give me a break with all the questions. If you roll your own kernel, im going to assume you know how to fix it. Its a simple fix, anyone can roll back.

Ok, i think i missed what nate said earlier about deploying the navipad file. That does not sound like a bad idea to me. I say this because if anyone wants some whacky layout, we simply android update the file and viola. Problem solved. So navipad for everyone. With that said i will have to leave the kernel as is for now and the install script needs to be modded.

Ok on to business. Nate did you test the mtd parts you posted? sure it does not break wifi ?

anyone test the new ril on the old build ?

Thanks ACL. Yes, the mtdparts I posted are perfect and cause no issues with wifi. I posted a test NBH, arrrghhh test it out when I first posted those a few days ago. I'd love to hear feedback from others that are compiling their own right now, but it has been great for me for a few days so far. I flashed about 20 times the other day seeing how low I could go without running into the protected area, and that was what I ended up on.

As for the navipad, I just know stinebd added that to rootfs when we made the button map commit that I posted earlier. When I compiled the kernel with that commit but didn't update rootfs, I ended up with buttons not functioning, so I figured we needed to add the navipad file once that commit was made.

[natemcnutty]

Originally Posted by Lmiller1708

^^^^



It looks like he is already going to revert back.
I talked with him earlier today too and is the path he was taking...

Reason being is with the new keymaps (like Haret) we will lose the "recent items menu" and not be able to turn on the screen by the top button (it will just end the call, very annoying!).

Thanks buddy, somehow I missed that post! I swear I've read every single post in this thread, but man have we been putting on the miles lately...

[MassStash]

[acl], currently on new ril old kernel and ev-er-reee thangs good

sorry if i helped in shmobing the forum, just tellin dudes ill be makin alt keymappin so they cant stop ASKING haha