ARCHIVED: [DEAD ROM] ThundeROM V1.8.3 4/5/2011

Status
Not open for further replies.
Yup, I was just able to duplicate the force close using note to self with voice.

Cool. This Rom will be flawless in no time. I've never seen a Rom so solid on it's first release like ThundeRom .. Impressive team they have here.
 
this version seems much faster, and the hotspot app is more reliable. The one thing I miss is the access controls from the old hotspot app.
 
Is the phone supposed to have higher running temps with the newest ROM? I just switched from stock rom to this one and ran the same live wall papers and apps and found that the temps were a little higher than normal via BatStat (usually 87-90F). I'm seeing temps going up to 100F and it's getting a little too warm for my hands...
 
Last edited:
Hi and thanks for this awesome ROM! I am completely new to a droid phone and I am wondering how much battery life does this ROM improve and is it noticeable? This is my main interest for attempting to use this ROM since I just want my phone to last longer. Also if anyone can inform me on what the Android Wireless tether is that would be great. Thanks a lot!
 
I think I found a bug. It's when I use Voice Action.."note to self".. The voice prompt pops up and records per usual. However, upon routing it to the Gmail app, I can repeat a force close everytime. This is a stock rom flash, too. If nobody else has this problem, perhaps I have a bad checksum/download and I can redownload it. Other than that.. GREAT ROM! You guys rule.

Easy fix. We won't do a special release for it but will certainly address in the next general release.

Cheers!
 
Hi and thanks for this awesome ROM! I am completely new to a droid phone and I am wondering how much battery life does this ROM improve and is it noticeable?

We can't tell you how much it will improve because that's a situation that's unique to each phone and is determined by things like signal strength, apps installed, and phone usage. That means it's not possible for anyone to make a general statement of "it will go from 26 hours to 29". What i can say is we have made changes that will improve the battery life. Battery improvements on cell phones can't be measured the same way processor benchmarks are measured. Also, this phone is great on battery straight from the factory so it's like going from great to greater :p

Also if anyone can inform me on what the Android Wireless tether is that would be great. Thanks a lot!

HERE You can use your phone as a wireless access point.
 
I am still testing, but so far all is well with the additional speed tweaks. With this and the OC kernel, I am scoring over 1200 in Quadrant.
 
I think I found a bug. It's when I use Voice Action.."note to self".. The voice prompt pops up and records per usual. However, upon routing it to the Gmail app, I can repeat a force close everytime. This is a stock rom flash, too. If nobody else has this problem, perhaps I have a bad checksum/download and I can redownload it. Other than that.. GREAT ROM! You guys rule.

Got the same error. Waiting for the fix, although not important as I didn't even know about this feature :)
 
So- Stagefright has been "added" to the recent releases of the ROM, which I find surprising... was it not included on the default?

I recall that early 2.2 builds had issues with stagefright that cause awful AAC decoding issues, and I recall fixing the Pandora quality on an EVO by reverting back to opencore.

I'm curious- has stagefright been fixed? I just flashed the phone last night and haven't had time to listen to music or test anything with that yet.
 
So- Stagefright has been "added" to the recent releases of the ROM, which I find surprising... was it not included on the default?

I recall that early 2.2 builds had issues with stagefright that cause awful AAC decoding issues, and I recall fixing the Pandora quality on an EVO by reverting back to opencore.

I'm curious- has stagefright been fixed? I just flashed the phone last night and haven't had time to listen to music or test anything with that yet.

The issue wasn't with stagefright perse, the issue was with streaming audio companies not wanting to switch their coding to support it. Those same streaming audio companies rely on add revenue from people using their product (app) ... don't support the audio format on Android devices and guess what happens? People don't use the product which translates into loss of revenue. Though reluctant, all the big boys have changed their tune (see what i did there) in the name of $ and audio works just fine.

That's all rather old though, they switched months ago. Here is a great article about that topic from Jerry Hildenbrand.
 
Last edited:
The issue wasn't with stagefright perse, the issue was with streaming audio companies not wanting to switch their coding to support it. Those same streaming audio companies rely on add revenue from people using their product (app) ... don't support the audio format on Android devices and guess what happens? People don't use the product which translates into loss of revenue. Though reluctant, all the big boys have changed their tune (see what i did there) in the name of $ and audio works just fine.

That's all rather old though, they switched months ago. Here is a great article about that topic from Jerry Hildenbrand.

Fascinating and informative. Hats off to you, sir.

EDIT: Actually, after reading his post, I'm not sure I agree at all. He is saying that there was a bug in stagefright that caused lower-bandwidth AAC to sound bad, but when streaming over WiFi of 4G, the newer codec that uses more bandwidth was ok. How is that the fault of the streaming radio companies? And how is that still not a bug on behalf of Google for alienating users of the older codec (which, by the way, is hardly obsolete compared to, say mp3s).

This whole "moving forward means not having to support legacy codecs" sounds a little ridiculous to me. AAC is not legacy, and is still used in a lot of streaming media (heck, most of my encoded movies from previous phones have audio in lower quality AAC. I am NOT interested in having to re-encode all of them because of a known bug in Google's decoder!). Pandora refused to update their Windows Mobile 6.x software because WM was difficult to build AAC support for (I had a chat with one of their chief technology officers almost a year ago) and re-encoding their library for another format to be used by a single (and slowly dying) specific OS was just not cost effective. Meanwhile, Google actually has support for it, breaks it, and we all blame Pandora for not keeping up?

Feh. I don't want broken codecs in my OS! I want to know that I can play my streaming audio from whatever source, my encoded movies, etc, and not have to worry if it is compatible with "google's new way of doing it" (which he's not specific about in the article either- why does the new way break the old one?).

/end off topic rant

Meanwhile, it doesn't say anywhere in that article that the bug is fixed now. Is it? Or is everyone expected to re-encode their stuff now if there is a problem? Because if the latter, I'm not sure I'd want to keep stagefright in my ROM... benchmark scores be damned!
 
Last edited:
We can't tell you how much it will improve because that's a situation that's unique to each phone and is determined by things like signal strength, apps installed, and phone usage. That means it's not possible for anyone to make a general statement of "it will go from 26 hours to 29". What i can say is we have made changes that will improve the battery life. Battery improvements on cell phones can't be measured the same way processor benchmarks are measured. Also, this phone is great on battery straight from the factory so it's like going from great to greater :p



HERE You can use your phone as a wireless access point.

Thanks, I'll definitely try getting this ROM onto my droid :cool:
 
Fascinating and informative. Hats off to you, sir.

EDIT: Actually, after reading his post, I'm not sure I agree at all. He is saying that there was a bug in stagefright that caused lower-bandwidth AAC to sound bad, but when streaming over WiFi of 4G, the newer codec that uses more bandwidth was ok. How is that the fault of the streaming radio companies? And how is that still not a bug on behalf of Google for alienating users of the older codec (which, by the way, is hardly obsolete compared to, say mp3s).

This whole "moving forward means not having to support legacy codecs" sounds a little ridiculous to me. AAC is not legacy, and is still used in a lot of streaming media (heck, most of my encoded movies from previous phones have audio in lower quality AAC. I am NOT interested in having to re-encode all of them because of a known bug in Google's decoder!). Pandora refused to update their Windows Mobile 6.x software because WM was difficult to build AAC support for (I had a chat with one of their chief technology officers almost a year ago) and re-encoding their library for another format to be used by a single (and slowly dying) specific OS was just not cost effective. Meanwhile, Google actually has support for it, breaks it, and we all blame Pandora for not keeping up?

Feh. I don't want broken codecs in my OS! I want to know that I can play my streaming audio from whatever source, my encoded movies, etc, and not have to worry if it is compatible with "google's new way of doing it" (which he's not specific about in the article either- why does the new way break the old one?).

/end off topic rant

Meanwhile, it doesn't say anywhere in that article that the bug is fixed now. Is it? Or is everyone expected to re-encode their stuff now if there is a problem? Because if the latter, I'm not sure I'd want to keep stagefright in my ROM... benchmark scores be damned!

We're clearly just going to have to agree to disagree on this. There are several statements i would love to approach in that paragraph but for the sake of not cluttering the thread with a debate that's way off topic ...

For your answer, I don't think the code has been released to many if any phones, what has been done is the companies allowed their apps to stream higher quality music over the 3g network. Because you know ... those companies who already supported the higher quality audio (that's right ... technically they had to change not a single thing apart from letting their app stream high quality over 3G ;) ) sure do care about how much data your putting across your mobile network that you pay the bill for :confused:
 
Just wanted to thank you guys for developing this ROM.

Unfortunately, I switched back to the stock rom (sprint) after I saw it was not as responsive on my phone and also had overheating issues. I did see my quadrant scores jump to around 944 (vs. 440 on stock) while on the ThunderROM. But for some odd reason it was not as responsive to me as the original rom moving from homescreen to other screens. I'll eagerly wait for the next revision and hopefully try it again.
 
Ksmithinny I think there is a blip in the lock screen running thunde rom 1.3 with nothing just stock I press the sleep button and it frezzes when you close it and press it on again its when I am looking at the apps drawer go to lock it and it shows the apps dark gets stuck then I have to press twice to wake up the phone just wanted to see if this was a issue that anyone else has had thanks for your help
 
Ksmithinny I think there is a blip in the lock screen running thunde rom 1.3 with nothing just stock I press the sleep button and it frezzes when you close it and press it on again its when I am looking at the apps drawer go to lock it and it shows the apps dark gets stuck then I have to press twice to wake up just wanted to see if this was a issue someone else has had thats for your help

hmmmm ... i haven't personally noticed this. I'm trying to duplicate it without any luck right now. I did noticed some funky issue with the lock screens on installs where i did not do a full wipe but they were few and far between and i had only noticed them on dirty installs, never on a clean install.

Let me get the pattern down in my head of what your listing above and I'll def keep trying to see what I come up with. If you notice a different way to duplicate it post that as well so i have a couple of different ways to try.
 
@dishe

If you want to disable stagefright, are you all set with knowing how to do it? Its pretty straight forward but if your not comfortable with it we can probably make you a flashable zip to only change that.

Just let me know and I'll throw something up for you.
 
Ksmithinny I think there is a blip in the lock screen running thunde rom 1.3 with nothing just stock I press the sleep button and it frezzes when you close it and press it on again its when I am looking at the apps drawer go to lock it and it shows the apps dark gets stuck then I have to press twice to wake up the phone just wanted to see if this was a issue that anyone else has had thanks for your help

Don't have this problem. I did a full wipe, loaded the ROM and restored from Titanium backup. Not seeing the issues you are seeing. Did you do a full wipe before flashing?
 
Status
Not open for further replies.

Trending Posts

Members online

Forum statistics

Threads
956,903
Messages
6,970,528
Members
3,163,646
Latest member
Chris34728