Announcements

ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.

Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

The way I see it is this - the last two is for if you're extremely hardcore kernel hacker, it would be handy alright, but on the face of it, we're already in an Android environment and those things would be pointless, so what if the handset is rooted or not, either way, for the average user, they're hardly going to see that...

I, myself, like to tinker and have been pondering about those in the list above....

Share this post

Link to post

Share on other sites

Nice thread, hopefully it will get the attention of the devs. Very interesting, keep up the good work! :P

Thanks :D

I have spotted a few things that's making my head spin....

Forgive the questioning of it...

Clockwork recovery seems to overwrite the original kernel build's command line on boot, with this one, and its different - question is "Is Clockwork recovery boot up procedure hardwired to specify this - rdinit=/init console=ttyDCC0 console=ttyMSM2,115200", I am under the impression that using ttyMSM2,115200 will allow you to somehow see the kernel boot messages whizzing by? How does one do it, this would be a useful thing to have to determine if everything is hunky-dory... nonetheless, the compile type build of the kernel has this "CONFIG_CMDLINE="init=/sbin/init root=/dev/ram rw initrd=0x11000000,16M console=ttyDCC0 mem=88M"

On another ROM - I think it was Customised BladeVillain (Eclair), there was a setting under Applications to not to charge the battery when plugged in, in Modaco's ROM that is not present - any chance of putting that back into it - this could be useful to be able to share files via cable without screwing up the battery by constantly plugging it in and defaulting to charging...

I have integrated the driver for Atheros R6000 driver for the chipset so that it can be built, the github page for the kernel... The only thing about this is, "where and how did Paul get the binary firmware and patch for that Modaco rom - is it needed as the core driver is now available and can be recompiled?" there's a wifi directory under /system, that has

athtcmd_ram.bin

athwlan.bin.z77

data.patch.hw2_0.bin

Would they be needed? Hmmm.... I will have to find out and re-do up the Modaco ROM for further investigation....

Finally, run a diff on the configuration used with the one I've attached in the linky above in which you have to follow to get at the attached tweaked_config.gz

You will see how much noise is generated by the kernel... am thinking, increase in performance, battery saving as those noises can cost a lot of overhead in terms of milliseconds, may not be noticeable to us mere mortals....

Share this post

Link to post

Share on other sites

Clockwork recovery seems to overwrite the original kernel build's command line on boot, with this one, and its different - question is "Is Clockwork recovery boot up procedure hardwired to specify this - rdinit=/init console=ttyDCC0 console=ttyMSM2,115200", I am under the impression that using ttyMSM2,115200 will allow you to somehow see the kernel boot messages whizzing by? How does one do it, this would be a useful thing to have to determine if everything is hunky-dory... nonetheless, the compile type build of the kernel has this "CONFIG_CMDLINE="init=/sbin/init root=/dev/ram rw initrd=0x11000000,16M console=ttyDCC0 mem=88M"