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

Status
Not open for further replies.
I can't uninstall because it is not found in the phone.


Edit: I did go to /system/app and I found com.google.android.apps.map-1.apk I tried installing it using root explorer and I received and error(Parsing error)
Also I can't download it Google Maps from the Android Market.


Edit 2: I found the fix. I had to go into recovery and wipe dalvik-cache. Once that was done I rebooted and there was Google Maps 5.3 working perfectly.

Also, I forgot to mention ThundeROM 1.8.3 is awesome. The read and write speed is incredible. Thank you
 
Last edited:
Im having this weird problem where everytime i reboot, all my widgets on home screen for adw ex launcher becomes "Problem loading widget". And when I try to re add them some widgets are missing from the list such as ATK, NoLED and Extended control. The apps are still on my phone but i dont see the widgets.

running 1.8.3 AWESOME
 
Have to love forums. Just did the SD card speed adjustment on my nook color earlier today and I really see a difference (especially in games and loading gallery). Was going to try it on optimums too, instead can just update TR.

"Winning!!!"

Sent from my NookColor using Tapatalk
 
1.8.3 is up.


-SD card read write speed changed from 128kb to 2048kb. Holy crap. That is all. Use SD tools (free in the market) for a before and after.

Anyway, enjoy.

EDIT- Corrected typo

Awesome! Been leary on grabbing a class 10 card because of seeing that other phones weren't able to fully adapt to the cards full ablilities....now I feel more confident that i can justify spending the cash on one....using a class 4 16g sandisk now and can't wait to see the new benchmark score. Thank You!!
 
I'm really liking 1.8.3. My SD card is only a class 6 but there is a huge difference when viewing pictures in my gallery. Keep up the great work!
 
Ksmith, I was looking through the build.prop for 1.8.3 and did not see the changes:

Maximum events window manager can handle per second raised to 60
Proximity sensor debounce time reduced to 25

Did you work them in a different way?
 
Ksmith, I was looking through the build.prop for 1.8.3 and did not see the changes:

Maximum events window manager can handle per second raised to 60
Proximity sensor debounce time reduced to 25

Did you work them in a different way?

Nope, accidentally put up the link to a version without those changes (that's the only difference). I changed the link out to the version with those settings in the build.prop but i dug in a little bit last night and am now 99.99% sure those are controlled by the kernel or drivers so changing them in the buildprop will have no impact. So, no harm no foul. Any "improvement" by these changes would be placebo. But if people enjoy them, eat up because they also don't cause any harm :D
 
Ever since 1.8 my Adfree has not been working. It says it's been granted superuser perms when I boot the phone up but I still get ads in Angry Birds, euchre, and everywhere else. I tried unistalling and reinstalling. Grrrrr

Same here. I cant seem to figure it out either. Anyone thoughts? :mad:
 
Nope, accidentally put up the link to a version without those changes (that's the only difference). I changed the link out to the version with those settings in the build.prop but i dug in a little bit last night and am now 99.99% sure those are controlled by the kernel or drivers so changing them in the buildprop will have no impact. So, no harm no foul. Any "improvement" by these changes would be placebo. But if people enjoy them, eat up because they also don't cause any harm :D

So hypothetically speaking, if I changed the proximity delayed to 500 let's say. Then if it was controlled in the build prop it would delay the screen coming back on while on a call correct?

Sent by Tapatalk ----- Optimus s
 
running great on 1.8.3 :) great job (did have issues with market not working initally but then wipped everything, including sd card then replaced zip file and placed my backups back on the sd drive, now no issues with anything im running) havent noticed any speed difference though but then again havent used anything that needed more speed
 
Is anyone else having issues of the screen not waking up when pushing the buttons after the update?

Sometimes when I push the buttons only the lights on the buttons illuminate. The only way I can get the screen to come on is by holding down the power button until the menu comes up (and at times this doesn't even work).

Also it doesn't happen every time. I did flash the stock layout buttons file. I don't remember it happening before the stock layout buttons file was installed. Would it be safe to Flash ThundeROM 1.8.3 over the top of ThundeROM 1.8.3 with stock layout button?

Sent from my LS670 using Tapatalk
 
Last edited:
Thanks for the update. Seems great.

Shinedown, TR 1.8.2 was my first ROM, but only the power button "woke up" the display on mine. I actually liked that fact because it prevented accidental wake ups in my pocket. Thought it was a feature of the ROM. Edit: I see where the stock buttoms layout link is on the first post. Never tried that myself. Sorry, newb here.
 
Is anyone else having issues of the screen not waking up when pushing the buttons after the update?

When I push the buttons only the lights on the buttons illuminate. The only way I can get the screen to come on is by holding down the power button until the menu comes up.

Also it doesn't happen every time. I did flash the stock layout buttons file.

It doesn't happen

Sent from my LS670 using Tapatalk

I just now noticed that too actually.
 
This is the same bug that's been with the phone since launch day. Flash the ROM, use it for a period of time (usually a day) flash the rom right overtop of itsself again and it usually goes away for good.
 
  • Like
Reactions: 64fairlane
This is the same bug that's been with the phone since launch day. Flash the ROM, use it for a period of time (usually a day) flash the rom right overtop of itsself again and it usually goes away for good.

Great, thanks! Flashing now. Thanks for your hard work.
 
So hypothetically speaking, if I changed the proximity delayed to 500 let's say. Then if it was controlled in the build prop it would delay the screen coming back on while on a call correct?

Sent by Tapatalk ----- Optimus s

I just think that its funny that ever since I changed my delay its worked perfect.
 
Glad to see the delay changed in this version. Thank you much. Music player is way better IMO as well. Thanks for all the good work! Ima test the Screen Lock issue more now that i flashed the new ROM.
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,900
Messages
6,970,520
Members
3,163,644
Latest member
roneginsberg