Bro, can share the link to V6 SuperCharge? I didn't bookmark it.

Alrightly!

Loading is slow, curi-ing neighbour's wifi, probably the cause that I can't "find" it on 1st page.

Our bootloader is not locked, so there's no reason to replace it aside from using stock bootloader.

If your concern was recovery, then no. M5 or most of the custom ROM's don't replace our recovery. You have to do it yourself through fastboot or download .zip recovery, which ironically, flashed through recovery. lol.

Hope these answer your questions.

Call me wannabe, but I have replace AOKP's bootanim to CM9's. lol.

EDIT: the lacked of carriage return in Mms.apk has been replaced with Emoji. lol. So, it's either you keep the emoji, or you keep the carriage return. I wished there are both option.

This post has been edited by Harddisk: Apr 29 2012, 11:02 PM

Yes, it does, for the reason of needing the root capability, as well as the mounting points required for CWM to work properly.

I guess that's as far as I can understand. There might be more.

When I was doing manual flashing from non-yakju to yakju 402, and from 402 to 404 (mistake), there was a bootloader primela03 that came with IMM76D. boot.img aside, which is the kernel where all the magic happens, but I haven't seen anyone deployed bootloader.img file with their custom ROM.

So I can safely assume, manually flashing bootloader is not necessary unless specified. And since our phone is not Seluar-ON like HTC, we don't have to bother about this at all, which is awesome. You wouldn't want to go through Seluar-OFF-ing Sensation XE which was running on HBOOT 1.27. It was a PITA...to say the least.

It ended up with an HTC supporter saying, "I will not get another HTC phone anymore."

This post has been edited by Harddisk: Apr 29 2012, 11:39 PM

I did my NLD. Wifi working fine, BT earpiece is working too. Haven't tried tethering though. Luckily everything works now. Can use with peace of mine.

Bro, this is the 4EXT Recovery I was talking about.

http://forum.xda-developers.com/showthread.php?t=1377759

---

Added on April 30, 2012, 1:01 amMy iP4s friend can see my emoji, but I can't see theirs.

---

Added on April 30, 2012, 1:05 amConsidered that cheap. Imagine the kind of research you have to go thru to get your Seluar-OFF. lol.

Earlier HBOOTs were easier. When you reach v1.27, you have to get physical with the phone. It's worse than getting a jig for Galaxy S or S2.

---

Added on April 30, 2012, 1:07 amEvo 3D HBOOT can downgrade? That's the phone my colleague has and he can't get ICS into his phone due to Seluar-ON. Got 1 instruction in xda though, but got risk of hard bricking the phone. lol.

This post has been edited by Harddisk: Apr 30 2012, 01:07 AM

Yup, now I can see the emoji. But it also lacked the feature of splitting SMS with pagination, which is really neat.

If only these features are put into 1 Mms.apk, in order of priority:
1) timestamp correction (last time requires app)
4) carriage return
3) SMS split/pagination
4) Emoji

If anyone wants the CM9 boot anim.

https://docs.google.com/file/d/0B2U1dOkc_2a...FRGM/edit?pli=1

File ... Download (or just press Ctrl+S) on supported browsers.

---

Added on April 30, 2012, 2:49 amLatest package by AOKP doesn't have GMail (2012-04-22). But I have no problem installing 1 off Play Store without running any Market Unlocker or anything.

This post has been edited by Harddisk: Apr 30 2012, 02:49 AM

Hmmm, my owner info is not showing on M5. Can anyone verify this?

Found another bug, auto brightness not working.

This post has been edited by Harddisk: Apr 30 2012, 01:27 PM

I recall seeing both battery status and owner info both on previous build.

D'oh. I'll slap myself if I didnt already.

Why oh why, M5 still buggy? Though not critical.

Another thing. After reboot, lock screen always show 100% battery first. lol.

I read about that on b32, it's either batter or calendar, then can't show owner info.

Previously, I had to show battery without calendar cause charging the time, battery won't show on homescreen. I guess I can off it now as it shows battery during charge. But on AOSP, while battery % was shown, owner info is still visible, isn't it?

---

Added on April 30, 2012, 1:42 pmAnyone tested auto brightness?

EDIT: fine now after rebooted. No idea what causes it to fail. Probably 1 of the settings.

---

Added on April 30, 2012, 1:46 pmAlready happened to me previously but nobody bothered when I said my signal drops again then I checked that OC/UV settings all gone.

Didn't you can hibernate one. I only standby, cause still consuming little energy.

---

Added on April 30, 2012, 1:51 pmAuto brightness bug still there. Let you guys test first, then I'll explain what I found just now.

EDIT: I think the auto brightness works right after you tick enable it in settings and just for the initial reading. Any subsequent changes in brightness will not be read. Can test by going outdoor, set to minimum, then tick enable. It turn brighter.

Untick it, block sensor, tick again. Leave for about 5 seconds, maybe less. Remove hand, screen remained dark.

So o can only assume it stopped checking brightness sensor after initial read. Maybe have to enable custom brightness tweaking to solve this.

Anyone?

This post has been edited by Harddisk: Apr 30 2012, 02:01 PM

Previously when IMM76D was out, it was haunted by disconnection issue. Then custom ROM/baseband was claimed to fix this problem. Actually, they don't, unless you OC it.

I OC soon after I flashed to b32, haven't enough time to confirm the claim that it actually fixes disconnection issue. So I was happily using it with OC/UV enabled. Until after a period of time, disconnection start to surface again. First thing I check was the OC setting. Yes, they were all gone and OFF.

Can test auto brightness using table lamp.

Need it, lazy to adjust brightness level all the time.

Bro, can double tap home, then scroll to left. 1 of the slider is brightness.

Interesting findings. Will consider the manual tweaking when I have time.

Worst news I heard all day.

Maybe it's time to hang around Blackmarket already.

It only happens if you hit another key too soon after you clicked "send". It happens to me often on WhatsApp. So just slow down a little. Otherwise, change keyboard, it could be the ICS keyboard thing.