Jump to content

unaszplodrmann

Members
  • Content Count

    393
  • Joined

  • Last visited

Everything posted by unaszplodrmann

  1. I had Hynix memory on a previous board. After an accident involving cursor keys, backspace, enter and dd, I got a replacement board under warranty... Luckily this one has Samsung flash. Serendipity, eh! Good find Ge... err, Paul... err, Daz ;)
  2. An entertaining read - hats off to those who went down the garden path. Looks like Qualcomm specified 4.2 MR1 for a reason, eh. Yes, the userland changes depend on kernel side updates, hence the reference to particular CAF builds.
  3. Pot. Kettle. I simply stated that there is a reason why the CM threads are stickied. They provide a useful pointer for infrequent visitors to orient themselves amongst the mass of minor variants on Huawei's offerings in order that they find 3rd party firmware actually produced and maintained by capable developers. As for those who say it's all merely a matter of opinion; we're talking technology, not philosophy, Daz's CM ports are technically superior.
  4. Thats an edit. The original build.prop was accidentally left in the repack as build.prop~ :lol:
  5. I was actually looking at another B952 CWM repack, when I thought I was looking at the international (WW) version - I need to cleanup these folders of unpacked roms ;) So it seems that there at least 2 different versions of B952. I see the same differences as you looking comparing the WW CWM repack.
  6. Interesting. Which B952 version are you comparing with? I compared with the 'WW' release and the badge dumps are identical to B960.
  7. Nice one, Jack :) Just had a look at B960 in comparison to B952; there are changes to audio libs and the libbcc JIT library, and the kernel is also different. aapt reckons all the APK versions are the same.
  8. There is a reason why the CM threads are stickied.
  9. I've not read every script in that package - I can't be bothered - but I do know that daft stuff like automatic re-zip-aligning, clearing the cache and forced dexopt are not worth any impact to the boot time, whatsoever. Thats purely a negative tradeoff.
  10. In other words, no: It is a developer preview - it serves a useful function to developers and as curio for those who fancy having a play with a debian based distro running natively on the phone. For everyone else, it serves no function at all.
  11. I tested it a couple of days back and the patch set does not apply cleanly to 4.2.2. Autopatcher instead uses a prebuilt, in-place... Which may or may not cause issues. Given that 4.2.2 isn't officially supported yet, its definitely a case of YMMV at the moment.
  12. It is enabled, both for 2D and 3D rendering. It is however - as I understand it - disabled/non-functional for certain UI rendering operations. In short, you're not asking the right question.
  13. It will impact boot times, that's for sure. I'm quite surprised that the "SD speed tweak" still does the rounds, but then again, what has the opinion of senior kernel devs - or indeed that of the guy who created the thing - have to do with anything?
  14. Oops! You could try scanning the partition and automatically fixing errors: Boot into recovery. Connect via ADB and do the following /sbin/e2fsck -p /dev/block/mmcblk0p13 If it finds a problem that it can't/shouldn't automatically correct, it will notify you. If so, post the output here. Afterwards, you can try to mount it from the command line mount -t ext4 /dev/block/mmcblk0p13 /data As before, post any errors here.
  15. Sorry, I mean't /proc/version, not cpuinfo - derp. OK, so your kernel version doesn't have a localversion appended; its is just 3.0.8-perf, which makes life easier. From what I can tell, you're getting 'tun: no symbol version for module_layout' because module.symvers is not being generated before the modules are built. Where it says: make modules ARCH=arm CROSS_COMPILE=arm-eabi- O=build KERNELRELEASE=2.6.32.9-perf You need to remove 'modules', so it's just 'make ARCH=arm...' That command will build both the kernel image and the modules, so there no need do a 'make modules' afterwards.
  16. If that is what you typed, it won't work. You should use the following command to check the version of string of your kernel: uname -a The version string shown by 'modinfo tun.ko' must match that of your kernel (i.e. 3.0.8-perf-alphanumeric_string). You can also get the kernel version string from /proc/cpuinfo. Information on matching this string in your kernel build is provided in post #8. Also note that you will need to run 'make' to do a full kernel build, rather than 'make modules'.
  17. More likely some disco queen from Dance Central 3... Sorry, but if you don't understand the matter of case sensitivity, I doubt you'd find the process as easy as making cake, which in actuality, can be something of a complex art form. Then again, I suppose you're essentially talking about eating cake, rather than making it.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.