Thank you!
I didn't know that word. Thank you! Yes, there is. But it's either that or having the user rename the kernel to boot.img and putting it in IMG. Now, I don't have to tell you that doesn't work, do I?
I would rather have users learning these commands than create a batch script to make their life easyThank you!
Yes, there is. But it's either that or having the user rename the kernel to boot.img and putting it in IMG. Now, I don't have to tell you that doesn't work, do I?
Users want a quick and simple solution. This is slightly dirty, but it works. Users will just have to be told to only put one kernel in IMG.
.Well, having looked at a lot of the ROMs, a lot of the ROM builders do all their work in Windows. So there are often a Thumbs.db in quiet a few of the directories in the zip-file. That's not the bad news. Though, it isn't exactly good either (takes up space, adds unnecessary files to the phone). But a lot of scripts... Obviously a lot of ROM builders, who use Windows, have NO IDEA what linux is or how it works. Hence my nagging about the busybox/toolbox and symlinks. A lot of ROMs even have a bunch of copies of toolbox named as ls, cat, etc. in /system/bin. And then on top of copying toolbox with all those names they symlink it all back to toolbox as well. No wonder so much space is wasted!
/
. Suppose there were no ready to cook batch scripts on Windows ,it would have prevented 100's of "cooks" from creating such "ROMs" ...Yeah, heh, I remember one file I downloaded and thought about installing. It was a keyboard with a single file or some single thing like that. So, like I always do, I looked at the script file. Luckily... What the hey?! They had just copied the regular rom-script with a bunch of symlinking to toolbox. I symlink as much as possible to busybox (has more options, ls gives nice colours, etc). Had I installed that package the normal way it would have broken a lot of things for me./
And you have Kitchen Batch scripts to blame for that
This is really wonderful ROM with Sony based... Your Kernel_Flasher really helps.. Thanks for your effort..
.. But no help in Light sensor.. Anyway I don't care much about Light sensor... 
I'm glad to hear you're not complaining this time. Not even a little!
- though I have no idea what you are refering to? If you are thinking about the updater-script (the thing that says "*camera" upon installation) then it has nothing to do with CyberShot. It sets execute-bit on a few files in /system/bin. Not sure if it HAS to be done, but rather than not finding any problems my self, changing that, and then everybody reports back on some problem I didn't find, I instead opt for the old, "if it ain't broken don't fix it".Try a standard kernel first, so we can rule out whether it is the kernel or the device-files that are at fault.
Try going to control panel and check that the xperia keyboard is set as active and not just google voice.
I don't personally have any ANT+ so I can't verify either way. All I know is that this is the regular Kappa kernel (with battery fix). So if it works in Kappa it might be some library missing here. I am not sure. Like I said, don't have it, can't tell 100% for sure.
Happy to be of service!
You can try. Copy the zip-file. Look inside it. There are some files in system/app called "systemui.apk" amongst other things. Copy the same files from the zipped helium-light over to the new copy. Rename it to sysui-backup.zip. If it doesn't work you can always flash back the sysui like it was and thus no harm has been done. : )
Hmmm... That's an interesting error. I have not experienced this. Problem is, I don't have the same phone.
The regular one is the same one. Device files updated (I hade a script in the helium rom that changed build.prop, but I put that build.prop in the device-files package so it's not in system when the rom script is run. Gah! Silly me!).
