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

[slammurai]

I tried going into market and got. Application launcher (in process com.modaco.android.launcher.gb) is not responding. I tried going to astro web page and using their external link to market as well
.

 

[beezy]

Could the moderators/somebody please point me in the right direction on this?

I just seen your other post earlier about the kernel and all that. I meant to reply already but i grabbed the update and had a hell of a time getting back to a usable phone.lol Give me a little time to go back and read your last post and then ill reply with everything i can to help out.

 

[beezy]

I tried going into market and got. Application launcher (in process com.modaco.android.launcher.gb) is not responding. I tried going to astro web page and using their external link to market as well
.

try going into settings and clearing the data on the launcher. Are you restoring another launcher with ti backup?

 

[beezy]

Got the Optimus U and T source from lg opensource. Found out that the directory kernel/drivers/media/video/msm differs from the S soucre, including at least one file with exposure-setting code that just isn't in the S sources at all. I want to replace the entire S msm directory with that from the U and compile the kernel as per LG's readme:

Beezy and ksmithinny, is this how you build the kernels you make available? I have a feeling there are also some non-kernel files, like android/external/kernel-headers/original/media/msm_camera.h, which may need to be changed too - does that mean I'd need to follow the entire Android system build instructions?

Thanks!

Could the moderators/somebody please point me in the right direction on this?

I would try build/working in the msm from the v source and compiling to see if that works then try working out from there if it's fails. You might have to edit and try building that into aosp.
You can build the kernel that way just have to edit your config if there's any changes to be made to the build process.

 

[slammurai]

what I did was wipe data cache and dalvik and reflashed tr I didn't restore anything. what I did try was take my sdcard and used it in my friends phone I dled nrom and flashed it and have no problems. what I did notice was his phone started acting up on with my sd so I formatted sd after that I redownloaded tr and flashed it so now everything is great. must have been when I transfered some tunes from my buddies laptop to my phone.

 

[jakemuse]

I would try build/working in the msm from the v source and compiling to see if that works then try working out from there if it's fails. You might have to edit and try building that into aosp.
You can build the kernel that way just have to edit your config if there's any changes to be made to the build process.

Building now (right now compiling arm-eabi-toolchain https://github.com/jsnyder/arm-eabi-toolchain for mac os x). I successfully booted and used an Optimus V rom to make a call, but it didn't give me exposure control in the camera, so I'm using the U's msm folder.

There shouldn't be changes to the build process if all I'm doing is dropping in a different msm directory with its own makefile, right?

 

[beezy]

Building now (right now compiling arm-eabi-toolchain https://github.com/jsnyder/arm-eabi-toolchain for mac os x). I successfully booted and used an Optimus V rom to make a call, but it didn't give me exposure control in the camera, so I'm using the U's msm folder.

There shouldn't be changes to the build process if all I'm doing is dropping in a different msm directory with its own makefile, right?

Your right i just didn't know if there was any changes that require you to make edit to the config. Ill have to take a look at your git later.

 

[KSmithInNY]

Holy macaroni, this thread has broken 100k views

This seems like a time for celebrating! Cheers!!

 

[cmags]

Holy macaroni, this thread has broken 100k views

This seems like a time for celebrating! Cheers!!

 

[ke4tzn]

I just put ThudeROM 1.6 on my Optimus and I got 1030 from the bench mark test. So far so good.

 

[jakemuse]

Your right i just didn't know if there was any changes that require you to make edit to the config. Ill have to take a look at your git later.

The toolchain didn't compile successfully from that git. Also tried to do it through macports, but it's arm-elf-toolchain rather than arm-eabi-toolchain. Trying to figure it out. Downloading android ndk right now. Is that what I'm looking for to cross-compile the kernel?

 

[WHYDavid]

I usually just lurk and read but I need to break silence to thank the developers of ThundeRom. It is awesome! Thanks to all the info here (yes, I read it all!), I rooted my phone and installed TR 1.5 the day I got it (a while back) with no problems. I'm on 1.6.2 now and feel guilty for not thanking you sooner.
You guys are great!

 

[jakemuse]

The toolchain didn't compile successfully from that git. Also tried to do it through macports, but it's arm-elf-toolchain rather than arm-eabi-toolchain. Trying to figure it out. Downloading android ndk right now. Is that what I'm looking for to cross-compile the kernel?

Kernel built. Now I have a zImage. What do I do with it? My inclination: extract xionia_kernel_005.zip, replace kernel/zImage with my new one and replace system/lib/modules with the modules my build created, zip it back up, and flash it. The xionia zip file appears to have all the utilities and scripts needed to do the complicated stuff described in HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki or http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html on its own.

I know there will probably be some kind of certificate/signing problems. How do I get around that?

 

[glitchsta]

BuildProp Deluxe?

Is it best not to install the buildprop deluxe after you install 1.6.2 because before buildprop i was getting 9 mflops now I am getting 7 mflops after flashing the deluxe buildprop...is it needed for the HW acceleartion and such still?

 

[jakemuse]

Kernel built. Now I have a zImage. What do I do with it? My inclination: extract xionia_kernel_005.zip, replace kernel/zImage with my new one and replace system/lib/modules with the modules my build created, zip it back up, and flash it. The xionia zip file appears to have all the utilities and scripts needed to do the complicated stuff described in HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki or http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html on its own.

I know there will probably be some kind of certificate/signing problems. How do I get around that?

Successfully signed the zip using the program provided here Creating an Android Update.zip Package ? RobMcGhee.com . Flashed kernel. No effect on camera. Damn. Next steps - copy camera header files? Copy the entire kernel from a different phone? Anyone have any ideas?

 

[Queueyou]

Will this new maintainance update be brought into TR so that we get the minor 'fixes' or were they already included?

 

[lionedas]

Will this new maintainance update be brought into TR so that we get the minor 'fixes' or were they already included?

Ditto

I have been suffering with the screen jitters that seem to only effect
a lucky few of us, and was hoping that these updates could be merged in to the rom.

I had to back down to TR 1.5 to get my phone stable enough to make calls with out having screen issues.

 

[slammurai]

what do I do with this update that my phone wants me to reboot. for

 

[acromack]

what do I do with this update that my phone wants me to reboot. for

don't. it looks like as of now it will unroot you and if you're on a custom rom possible brick you as well. wait until it's all sorted out - nothing critical that you absolutely need to install to fix right now, but i'd still stay away from it until you're absolutely certain what it will do to your custom setup.

 

[tmeader]

So, I accidentally hit "More Information" on the Update prompt screen (update just showed up about an hour ago). It didn't install thankfully, but now there's an icon up in the Notification bar that won't go away, and it never gives me the choice to "Install Later" again. Ugh. Is there any way to get rid of this icon? Can I manually delete the update file by clearing the cache with Recovery? Any ETA on an update for this or Lego in order to keep these update notifications at bay?

Thanks.