Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

42 Excellent

About Fagulhas

  • Rank

Previous Fields

  • Your Current Device(s)
    Huawei Ascend G300

Recent Profile Visitors

616 profile views
  1. I have my own kernel and device tree. I will release it at some point
  2. My antutu score gone from 5054 to 5287 @ 1200mhz , it does improve slightly. but not 200% ;)
  3. Already compileda few builds with these tweaks, the "speed" increase is minor and some minor issues pop up, tho those can be solved.
  4. Fagulhas

    [In-Call Volume Too High Problem]

    They are included in all recent builds, although in-call sound is far from fixed, it just lowers the volume a bit more, making the distortion less noticeable at higher volumes because well, its not that high anymore :P
  5. Fagulhas

    [In-Call Volume Too High Problem]

    I've been looking around that issue since the early days of CM development and its still with us today. Hours if not days were spent trying to fix it with no results so far. I haven't been around much to do a few more tries and changes, but maybe one day i will hop around to help a bit more.
  6. If the usb is in fact broken, how do you charge the phone?
  7. Yeah its clear and also yes, all we can get is the complete image and we are not able to read it. We can hex edit it and see a few things and from a quick diff we can see several differences tho we cannot tell what they actually affect us.
  8. No because the bootloader runs every single time you start the phone and if you re-lock it, you will soft-brick it and get "signature verification failure".
  9. The boot loader ultimately has to: Bring the kernel (and all the kernel needs to bootstrap) into memory Provide the kernel with the information it needs to work correctly Switch to an environment that the kernel will like Transfer control to the kernel On the x86, the boot loader runs in Real Mode. Consequently it has easy access to BIOS resources and functions. Therefore it's a good place to perform memory map detection, detection of available video modes, loading of additional files, etc. The boot loader will collect this information and present it in a way the kernel will be able to understand. From - http://wiki.osdev.org/Bootloader
  10. No. Here's the deal folks. Starting with ICS, Huawei locked all bootloaders, meaning the only way for us to install a custom recovery & rom was to use the gingerbread bootloaders that are NOT locked. The most common used gingerbread bootloader was from a "really old build", maybe even from the B888 days. This one is from B895, the last official version of a gingerbread rom for most carriers. And before anyone says, no its not optimal to use a old bootloader, but its what we have and the only way to do it so far. We already asked Huawei to add our model to the unlock bootloader page at http://www.huaweidev...ethod=preUnlock Also bear in mind that these issues MAY not be related to the bootloader, tho as shown from a few users, it can help.
  11. We don't "tweak" & "create" ROMS by editing zip files and whats inside them. Use ubuntu or any other linux distro if you want to avoid case-sensitive problems with files.
  12. There's no need to decompile when the source is available? All the CM work is compiled from freely available sources.
  13. Please give me the exact error message it appears to you. Also make sure the zip files you are trying to install are not corrupted after copying to your sdcard or internal storage.
  14. Yeah you are, unless you are still on gingerbread.