Database Info

Question for All Devs Regarding Camera Issues

As a long time Rogers 32A user, my experience with most "ported" roms has been rather shoddy. Namely, the issue of camera FCs on most Dream/32B ported roms (Cyanogenmod has been a long time pain for this one).
For those of you who are unfamiliar with the bug, it essentially causes the camera to load properly about 3/5 times. Factors such as unplugging the phone or extended use cause the camera to open to a black screen before rebooting the phone. I've attempted to isolate the problem using logcat, but most of the time it doesn't really show anything useable.
The issue is mostly in all Donut roms that I have tried (Cyanogenmod, RA Donut, SuperD) as well as some of the new Ecalir ports (xRom). The only roms which don't seem to have this problem are any Sense based roms (Cursordroid, Hero ports), Sanpei's AOSP Eclair, and the stock Fender rom by Cursordroid. At first, I thought it was an issue with software (maybe something with Barcode Scanner/Google Goggles/etc.) but I found that this problem still exists on even fresh installs.
Now, this has led me to start thinking about what factors could possibly lead to this outcome. I was wondering, is it possible that there is some part of the rom that is still specific to Dream boards that causes the camera FC? Is there maybe something that we could be doing different in our ports to maybe fix these issues?
It seems that roms that were either made specifically for 32A devices (Fender) or those that use HTC's camera (Sense roms) are the only ones that seem to be immune to this behavior (at least for me and probably another dozen users or so). If some of the dev's could weigh in on this, maybe we could finally stamp out this bug.

have we looked at the difference between the kernels from the htc dev site? i'll take a look now and tell you what differences i spot

nevermind it's not as simple as the hero one... doesn't come with a premade config

Switching to Cyanogen Mod

Hi guys I'm currenting running BAMF 2.0 and I'm having a lot of problems with charging and USB mounting and so I was wondering if I should switch to CM7. What problems have you guys been having with CM7? Also what kernel and radio should I flash when I run it? Thanks!

krnsushiman said:
Hi guys I'm currenting running BAMF 2.0 and I'm having a lot of problems with charging and USB mounting and so I was wondering if I should switch to CM7. What problems have you guys been having with CM7? Also what kernel and radio should I flash when I run it? Thanks!
Click to expand...
Click to collapse
You need to use a Froyo radio (like the one in my signature). Also CM7 does have it's own issues: see the CM7 thread for more. I'm using leanKernel2.5.2+tun and it works great. Make sure to flash the kernel in recovery and not in ROM manager or Kernel Manager -- it can cause issues. Some of the charging issues I've seen with the GB Sense Leak seem to have something to do with the kernel, or so I've read in the leanKernel thread. May want to check that out before you switch.
Good luck!

I've been using CM7 as my daily driver since the newest build came out and have had very few problems. The most annoying issue is that in order to get 4g you have to turn 3g on first, then switch to 4g and it will connect, but won't show you how many bars you have. Aside from that everything is working pretty flawlessly for me. I think that it is way better than any of the sense based roms and it's definitely cool to have an AOSP rom since I upgraded from the OG DROID.

I wouldn't say I've been having zero problems, I don't have the updated baseband above (care to point me where I can find that/noob instructions?) but overall I have mixed feelings with the update - most of them are stock-android issues I think. The radios are a mess, I lose 3g regularly and have to restart, gps problems, and bluetooth is a complete disaster (as it was on sense). Other than that, I've had issues with exchange, issues with my contacts (may have been a backup problem), issues with some widgets. Generally it is MUCH faster than sense on bootup, but some games are laggy with nothing else running.
Also: Netflix!
Really looking forward to future updates, once the kinks are worked out I will be pretty happy. Very glad I'm off sense and all that VZ crap is gone.

Why is there a lack of Kernels for the One s

So, i know its a newer device, and if thats the reason, great! But i was wondering why there is such a lack of available Kernel options (especially for AOSP roms)? Even Sense Kernels are few and far between. I just was wondering if its something HTC has not released ( i know they havent released the source for US Kernel, but wouldnt the international one be VERY similar?) or done that they should be or if it was just that its new and these things take time?
It just seemed like every other phone that i had, even newer phones, had kernels being developed almost immediately which i am really not seeing for the one s.
Again, not *****ing, just curious. THANKS.

Which ICS Roms have the SMS delay fix?

I recently flashed my first rom, going from stock 2.3.3 to Fallout 4.4.0. I always had the sms delay issues on 2.3.3, since flashing Fallout 4.4.0 I've still got the issue, but I also have text messages going missing as well.
Do any of the ICS custom roms have the SMS delay fix built in? Or is there a way to apply the fix to any rom I use?
Thanks

I've never had any issue with text messages going missing or any delay issues, either on stock or (currently) on CM9.
Are you sure it isn't a hardware issue with your particular phone instead of software?

It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.

FlexiPack said:
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
Click to expand...
Click to collapse
I do vaguely remember something to do with this issue, but I think it was solved by an HTC update a long time ago. I can't imagine that any current ROM has this issue - it was a base software fix, not an add-on fix AFAIK.
If you are getting this now then I suspect it is something other than the ROM causing the problem.

FlexiPack said:
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
Click to expand...
Click to collapse
That link also points to the software update that brought the Android version up to 2.3.5 as fixing the issue, why didn't you upgrade to 2.3.5? I still think it has something to do with your hardware and the fact it is only some would make me think that even more.

I presumed that any rom after 2.3.5 would have the fix but it was still happening on the ICS rom I tried. Today I have flashed 2.3.5 (version 2.10.401.9). I've still got sms delay
It's looking like it's not a software issue but I don't understand how it could be a hardware issue. Surely a hardware fault would mean they either do come through or don't, not the occasional delay or one going missing. So far my phone doesn't seem to have dropped signal when idle, so it 'may' have fixed something at least!

If my memory serves me correctly then the issue was related to the radio that came with the 1.47 update many moons ago
Sywepd form my DsereiS

That's interesting. Perhaps I could update to a custom rom and change the radio. So far the delays have been very short and none have gone missing so it's definitely better than before. I'd hate to be stuck on gingerbread though.

Jellybean Roms

With all the Jellybean Roms popping out for the Infinity, it's a little confusing to choose which ones are going to blend well with ones personality and usage... I'm not sure if this also applies to some, but it would be great if we could get some testimonials from those who have tried the different roms... probably post their pros and cons or maybe certain things and features that are not working with that Rom...
Hope someone could share their experiences here with the roms.. this might enlighten some users who are still contemplating whether to unlock their devices or not

shadow071506 said:
With all the Jellybean Roms popping out for the Infinity, it's a little confusing to choose which ones are going to blend well with ones personality and usage... I'm not sure if this also applies to some, but it would be great if we could get some testimonials from those who have tried the different roms... probably post their pros and cons or maybe certain things and features that are not working with that Rom...
Hope someone could share their experiences here with the roms.. this might enlighten some users who are still contemplating whether to unlock their devices or not
Click to expand...
Click to collapse
I haven't tried a lot of ROMs for the tf700 yet, but I have noticed EOS' ROMs are basically stock-based, with some tweak to make the performance better and to OC. You can also slightly personalise things (like the statusbar color) or use a CM10 theme.
However, they are usually very stable, which is why I have been using them for months now on my Xoom, and chances are I'll use them on the tf700 as well
If you are really into customisation, you should have a look into most CM10-based ROMs or OAKP.
They really try to get as many features crammed in the ROM as possible!
I myself don't need that customisation and have found that stock based ROMs, with tweaked kernels usually do the trick.
(Maybe a little OC as well, but that's not even a must for me.)
It really depends on what you want.
But since most JB roms are in pretty early stages, I'd recommend to have a look into one of the ROMs you seem to like, read the latest pages of the threads and see if there are many issues or not. Most common issues are also mentionned in the first post of the ROM thread!
Maybe if you really want a daily driver, you should go and use Zeus first, and when the JB are really stable, you can switch to those?

All the JB roms are using the same alpha base... no gps and other bugs/performance issues. If you are looking to run JB I would wait awhile longer.

Trying new custom ROM's is something you have to like. If you really want to have a nice and stable system you probably better
wait for a stable version. But if you want to experience the early stages of what will be coming, installing new ROM's is a lot of fun.
I currently have the CM10 ROM installed compiled by Hiemanshu. Still have issues but i am amazed by the performance of Jelly Bean.
When i bought my TF700 i was kind a dissapointed by the perfomance of ICS but now i have had an insight of Jelly Bean i am totally happy again!
That's exactly why installing custom ROM's is worth the effort.

FWIW my experience is a little different. I tried the EOS and Baked Bean ROMS and like them both, but had an issue with the Portrait bug as one of my companies main apps requires Portrait if I want to use it on a Tablet. Also, even though I don't really need it, it did bother me that there was no GPS, and the wallpaper bug was just annoying. I figured that any issue with bootloader would eventually be fixed so I then did the TF700 version of the 300 build. Could not be happier. None of the bugs I just mentioned, Good performance, and I just installed Lux to address the brightness issue so that is not a problem either.

pbrauer said:
FWIW my experience is a little different. I tried the EOS and Baked Bean ROMS and like them both, but had an issue with the Portrait bug as one of my companies main apps requires Portrait if I want to use it on a Tablet. Also, even though I don't really need it, it did bother me that there was no GPS, and the wallpaper bug was just annoying. I figured that any issue with bootloader would eventually be fixed so I then did the TF700 version of the 300 build. Could not be happier. None of the bugs I just mentioned, Good performance, and I just installed Lux to address the brightness issue so that is not a problem either.
Click to expand...
Click to collapse
Did you apply the .30 update to get the TF700 bootloader back?

pbrauer said:
FWIW my experience is a little different. I tried the EOS and Baked Bean ROMS and like them both, but had an issue with the Portrait bug as one of my companies main apps requires Portrait if I want to use it on a Tablet. Also, even though I don't really need it, it did bother me that there was no GPS, and the wallpaper bug was just annoying. I figured that any issue with bootloader would eventually be fixed so I then did the TF700 version of the 300 build. Could not be happier. None of the bugs I just mentioned, Good performance, and I just installed Lux to address the brightness issue so that is not a problem either.
Click to expand...
Click to collapse
Might have to give that a shot later now that we can go back to ICS.