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

[arrrghhh]

Originally Posted by [ACL]

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?

I'm not sure if there is a way to remap all of the buttons - I'll have to look into it...

Originally Posted by [ACL]

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

Yup, that couldn't be easier. Thanks!

[natemcnutty]

Originally Posted by [ACL]

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?

When XDAndroid decided to change the button mappings, I looked into a program for Android that would let us re-assign the keys, and I wasn't able to find anything useful.

Also, if we made the button mapping commits, then we have to add the navi_pad keylayout copy to the install script for the rhod400/500.

[[ACL]]

Originally Posted by natemcnutty

When XDAndroid decided to change the button mappings, I looked into a program for Android that would let us re-assign the keys, and I wasn't able to find anything useful.

Also, if we made the button mapping commits, then we have to add the navi_pad keylayout copy to the install script for the rhod400/500.

So these button changes on xdandroid require a recompile ? Thing is there is two ways to change this right. One, we fool the kernel like we do now, or just tell android to deal with it like it should. I rather do it android wise and if that doesn't work, then we can just revert?

im ok either way.. yall can decide.

[natemcnutty]

Originally Posted by [ACL]

So these button changes on xdandroid require a recompile ? Thing is there is two ways to change this right. One, we fool the kernel like we do now, or just tell android to deal with it like it should. I rather do it android wise and if that doesn't work, then we can just revert?

im ok either way.. yall can decide.

I agree that making Android handle it is probably best practices, and really, you are the one that has to remember how things are programmed, so I think the call is up to you

From what I remember, I had to git revert the button mapping change in the kernel, then make the changes in the rootfs. I'm not sure how that translates over, but I guess we should stick to whatever XDAndroid is doing.

[neopeek]

(19:08:01) neopeek: yap i heard it but I think with the build.prop trick (not verified) it's not neccessary
(19:08:10) neopeek: you should have missed it
(19:08:19) neopeek: for e.g.
(19:08:32) neopeek: i will post you some lines from zte blade device
(19:08:35) neopeek: to show you
(19:08:40) arrrghhh: k...
(19:08:59) neopeek: ril lines and how the handle it (did tell this also to acl but he may have missed it too)
(19:09:37) neopeek: many devices do it like this:
(19:09:41) neopeek: rild.libpath=/system/lib/libril-qc-1.so
(19:09:41) neopeek: rild.libargs=-d
(19:09:41) neopeek: /dev/smd0
(19:09:50) neopeek: you are noticing smd part??
(19:10:06) neopeek: once I remove this args from sysinit.rc from NAND on Rhod
(19:10:12) neopeek: it boots up on my GSM Rhiod
(19:10:37) neopeek: so I think once we merge it into build.prop instead of sysinit.rc it will do the trick
(19:10:41) neopeek: will have to verify it
(19:10:45) neopeek: hope you got me!
(19:11:56) neopeek: you guys over @ppcgeeks can still count on me but last days cm7 was a real nightmare for me and therefore I didn't even touch my Rhod300
(19:12:10) Nautis: ive seen that in some build.props
(19:12:30) neopeek: yes it's quite popular
(19:12:33) Nautis: I was wondering waht all that was about but that makes sense
(19:12:40) neopeek: and seems it was first introduced with Froyo

Not verified by myself yet but will do soon if still necessarry

[MassStash]

ya my service is not working for some reason.... you say it's supposed to be a auto-mateek?

and i think the keyboard is frivolous at this point. If it's not broke, don't try to go crazy and fix it hardcore yet? lol I'm fine with recompiling, more hands on.

[[ACL]]

Originally Posted by neopeek

Not verified by myself yet but will do soon if still necessarry

I have a new ril for you waiting actually. It no longer is affected by the cmd line.

Anyways, try out the ril i posted before. And see if it helps you. If the variant detection is working, then it will know you are gsm and not force cdma ..

As for your chat log listed.. doesnt make sense to me .. sorry. i dont know if you are proposing a change? Also did you look at the args we take on the ril in the code?

Edit: to make it easier.. here is the link.

http://htcdevs.wirelesstcp.net/files...generic-ril.so

wistilt i think is working on a new ril so im trying not to do much work on it :-p .. but ill post the code if needed.

[[ACL]]

Originally Posted by MassStash

ya my service is not working for some reason.... you say it's supposed to be a auto-mateek?

and i think the keyboard is frivolous at this point. If it's not broke, don't try to go crazy and fix it hardcore yet? lol I'm fine with recompiling, more hands on.

Try to debug bro.. you are compiling untested code right now so see if you can make sense of the logs..

[MassStash]

well whats good with ASR(android system recovery) advanced menu or something? do i just need to pop force cdma back in the tinboot? haha

[natemcnutty]

By the way, I just cleaned up the history of the initrd.lzma. Had to do a clean pull today and can't believe how much bootenv has ballooned in size because of the binary files. I'll do a garbage collection on it tomorrow so that new clones take much less time.