ARCHIVED: [DEAD ROM] nROM v1.6.3

[Nick7]

Just flashed this rom over top of ThundeRom and it's frozen on the nRom loading image.

Edit: Removed battery and the load image is no longer frozen. Taking a really long time though. Now it loads for a long time and then the screen flashes and the load bar starts moving again then freezes.

Go into recovery and:

adb shell
mount data
rm -rf /data/dalvik-cache
mount cache
rm -rf /cache/dalvik-cache

OR

From recovery, clear dalvik-cache and format cache. Either way works. Sorry for the delayed response; I just took an insane power nap.

Nick7, enjoying nROM. Came over from TR 1.6 due to system lag when tethering. Just curious, why include the Wireless Tether app when it does not work on the Optimus S? I've never been able to get any wireless tethering app to work other than the built-in hotspot functionality.

I like the options that the program has. Does the tethering app work for you now?

 

[s33ker]

I like the options that the program has. Does the tethering app work for you now?

Sorry for not being clearer. No, it does not. You're telling me it works for you?

 

[quantum_futurist]

Go into recovery and:

adb shell
mount data
rm -rf /data/dalvik-cache
mount cache
rm -rf /cache/dalvik-cache

OR

From recovery, clear dalvik-cache and format cache. Either way works. Sorry for the delayed response; I just took an insane power nap.

Ok, I've managed to get ThundeRom to boot up again. Do I clear Dalvik-cache before flashing nRom?

 

[Nick7]

Sorry for not being clearer. No, it does not. You're telling me it works for you?

Yes, where does it mess up for you?

Ok, I've managed to get ThundeRom to boot up again. Do I clear Dalvik-cache before flashing nRom?

You can but I usually only do it for troubleshooting purposes.

 

[xtacocorex]

Wow that is the craziest thing. I just tested and confirmed this! I'll look into it, but until then don't mess up! lol.

Glad you were able to recreate and it wasn't just me.

As a point of reference, this worked properly in 1.3.3. At least there are bounds to the issue so you don't go off on a wild goose chase tracking this down over multiple versions.

I did switch to the default screen lock for the time being.

If you need help testing a fix, let me know, I'll be a guinea pig for you.

 

[s33ker]

Yes, where does it mess up for you?

At the very least it's not broadcasting an SSID. My notebook nor Palm Pre detect it.

 

[xtacocorex]

Sending from my macbook over wireless tether. If this shows up, I believe it works. Could it be one of your settings?

 

[xtacocorex]

At the very least it's not broadcasting an SSID. My notebook nor Palm Pre detect it.

Here are my settings (with exception to SSID name and encryption key):
Enable Wi-Fi Encryption: Checked
Encryption Setup Method: Auto
Channel 01
Reduce Transmit Power: Disabled
Enable Access-Control: Checked
Client Notification Mode: All Clients
Vibrate on Connect: Checked
Disable Update Check: Checked
Disable Wake Lock: Checked
Disable Screen Lock: Checked
Battery Temperature: Fahrenheit

 

[srthimsen]

Here are my settings (with exception to SSID name and encryption key):
Enable Wi-Fi Encryption: Checked
Encryption Setup Method: Auto
Channel 01
Reduce Transmit Power: Disabled
Enable Access-Control: Checked
Client Notification Mode: All Clients
Vibrate on Connect: Checked
Disable Update Check: Checked
Disable Wake Lock: Checked
Disable Screen Lock: Checked
Battery Temperature: Fahrenheit

Have you tried switching channels? I know it's a long shot, but there may be serious interference on the frequency you're trying.

My other question is if you've tried without encryption.

Sent from my LS670 using Tapatalk

 

[s33ker]

Sending from my macbook over wireless tether. If this shows up, I believe it works. Could it be one of your settings?

Default settings, no go. xtacocorex's settings, no go. Barnacle never worked either. Not a huge deal as the hotspot functionality works but just odd that I seem to be the only one with the issue.

 

[DoesItMatter]

I'm running 1.4 and also experience the occasional stuck boot.

I upgraded from 1.2 -> 1.3.2 and a couple times, it would just sit at the nRom logo

Went from 1.3.2 -> 1.4 -- same thing - its rare but it does happen.

It usually happens on reboots only.

I.e. - if you power off, then power on - it never happens.

but if you did some update or the phone rebooted on its own, it has a chance
to get stuck on the nRom boot logo and just sits there til you pull the battery out.

 

[Nick7]

I'm running 1.4 and also experience the occasional stuck boot.

I upgraded from 1.2 -> 1.3.2 and a couple times, it would just sit at the nRom logo

Went from 1.3.2 -> 1.4 -- same thing - its rare but it does happen.

It usually happens on reboots only.

I.e. - if you power off, then power on - it never happens.

but if you did some update or the phone rebooted on its own, it has a chance
to get stuck on the nRom boot logo and just sits there til you pull the battery out.

That's strange. Try going into recovery and:

adb shell
mount data
rm -rf /data/dalvik-cache
rm -rf /data/boot-cache
mount cache
rm -rf /cache/dalvik-cache

 

[DoesItMatter]

That's strange. Try going into recovery and:

adb shell
mount data
rm -rf /data/dalvik-cache
rm -rf /data/boot-cache
mount cache
rm -rf /cache/dalvik-cache

OK

I did this and booted into the phone - I'll try a few reboots and see
if the hanging continues, or if this fixed it.

I know it never does it from a power off, it was only occasionally
happening whenever the phone did a reboot.

 

[DoesItMatter]

That's strange. Try going into recovery and:

adb shell
mount data
rm -rf /data/dalvik-cache
rm -rf /data/boot-cache
rm -rf /cache/dalvik-cache

I removed the "mount cache" line as I did not need to do it on my phone.

When I tried - it kept saying resource in use.

I just did the next rm -rf line and it worked, so it wasn't needed on my phone.

Since doing these removes, I've done maybe 8+ reboots.

Reboot from the phone power button, reboot into recovery,
reboot from recovery, power down then power back on, etc, multiple times.

I don't seem to get the stuck phone bootup anymore - but I'll keep watching.

Looks like this resolves the problem for now!

 

[Nick7]

I removed the "mount cache" line as I did not need to do it on my phone.

When I tried - it kept saying resource in use.

I just did the next rm -rf line and it worked, so it wasn't needed on my phone.

Since doing these removes, I've done maybe 8+ reboots.

Reboot from the phone power button, reboot into recovery,
reboot from recovery, power down then power back on, etc, multiple times.

I don't seem to get the stuck phone bootup anymore - but I'll keep watching.

Looks like this resolves the problem for now!

Great! Yeah, if the mount commands error out that means that whatever you are trying to mount is already mounted.

 

[DoesItMatter]

Nick,

I was using Root Explorer to browse /data and /system and found some dupes.

Under /system/app - there is a SuperUser and Superuser apk, exact same file.

Under /data/app - there is RealCalc and then the .com.Realcalc apk's

Under /data/app - two copies of the EStrongs file explorer

I found a couple other dupes as well that I went and removed, but can't remember what.

I also went into dalvik and deleted those individual ones that were dupes.

Just letting you know if you wanted to trim some stuff from the next rom.

Oh - and you can free up an additional 2MB by moving the new vending apk from /data/app into /system/app
and deleting the old Vending.APK file.

 

[Nick7]

Uhh yeah the extra files are from the patch. I'll fix that in the next release. Thanks for the report

 

[quantum_futurist]

My wireless isn't working. It scans, says it connecting and the says disconnected. I've tried turning it off and restarting the phone.

Thanks

QuFu

 

[Nick7]

My wireless isn't working. It scans, says it connecting and the says disconnected. I've tried turning it off and restarting the phone.

Thanks

QuFu

Hmm, my WiFi seems to be working properly. My only suggestion to you at this point would be to reflash nROM. Keep me posted.

 

[rodcpierce]

I have one for yah. Set a pattern lock screen. Lock the phone and enter in the wrong pattern. Let me know what happens