Can someone hint or at least point in the right direction how to fix the MMS issue so that more roms can be ported from from the evo 3d to the evo V. I don't have a ton of time, but I might jump into this as an "after work" project.
I'm not sure if I should ask here or in the original XDA thread. ROM seems fine except there is no boot animation. I just have a glaring white screen with the HTC logo for the two or three minutes it takes the phone to boot. The earlier version from June had an animated Android with big teeth which I didn't care for much but at least it made me feel like my phone was doing something. Any idea what's wrong with my ROM? Should I just try to flash over what I have?
I'm not sure if I should ask here or in the original XDA thread. ROM seems fine except there is no boot animation. I just have a glaring white screen with the HTC logo for the two or three minutes it takes the phone to boot. The earlier version from June had an animated Android with big teeth which I didn't care for much but at least it made me feel like my phone was doing something. Any idea what's wrong with my ROM? Should I just try to flash over what I have?
Thanks I knew there was a build prop entity that controlled boot animation but couldn't find it.
Unfortunately that wasn't the issue. Good news, figured out what caused it. I was using the live dmesg and live logcat apps. They worked well with stock and the June release of MeanROM but don't seem to work with this current new release. Going into those apps and having the live logcat removed brought back the boot animation.
But I'd rather the live logcat/dmesg. Any idea why it worked with the June release but not the new August one?
Thanks I knew there was a build prop entity that controlled boot animation but couldn't find it.
Unfortunately that wasn't the issue. Good news, figured out what caused it. I was using the live dmesg and live logcat apps. They worked well with stock and the June release of MeanROM but don't seem to work with this current new release. Going into those apps and having the live logcat removed brought back the boot animation.
But I'd rather the live logcat/dmesg. Any idea why it worked with the June release but not the new August one?
I've got no idea man, maybe it conflicts with the bootanimation or disables it for some reason, but I'm glad you found your source. You'd have to ask someone smarter than me
I'll take a look at it when I get back to my computer.
UPDATE: Alright, I'm downloading it now. I'll ask the dev to see if I can post it here with the port, if not then I'll have to post a patch. Looks like AOSP MMS doesn't work on the original ROM, which means you'd have to use a third party app to send MMS.
A few things I've found that do NOT work in this 2.6 version (based off sprint firmware 2.89) are:
1) Speaker phone
2) Data usage monitor (in stock rom)
I'm assuming the rom wants the new kernel, and given we're using the old shooter kernel for hboot <1.58 (e.g. eng hboot), that probably provides cause to these issues.
A few things I've found that do NOT work in this 2.6 version (based off sprint firmware 2.89) are:
1) Speaker phone
2) Data usage monitor (in stock rom)
I'm assuming the rom wants the new kernel, and given we're using the old shooter kernel for hboot <1.58 (e.g. eng hboot), that probably provides cause to these issues.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.