• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Themed ROM] NexFro 1.0.1 - Android 2.2 FRF57 (WIFI FIXED)

Thanks for deciding the name!

  • NexFro

    Votes: 115 86.5%
  • NexCream

    Votes: 22 16.5%

  • Total voters
    133
It's kind of maddening and makes no sense. A reboot should clear things up, if anything, but in my case it appears to mess things up.

Yes I was thinking the same thing, and it used to be like that... A reboot would clear things up and it would run better... However the exact opposite has been my experience with every reboot on 2.2 it is worse right after you reboot and gets better the longer you run it...

Could this be JIT related? Like maybe JIT is trying to get everything ready to run faster?
 
Upvote 0
Yeah, Fab is like that, keeps doing stuff that we don't expect, but love. :)

I've tried just what you suggest multiple times...I make a nandroid when things are working perfectly, and when I reboot as a part of the nandroid process things start to go south almost immediately. Then I restore the "good" backup (again, made when things were running perfectly), and it then this "perfect" backup goes south in exactly the same way.

It's kind of maddening and makes no sense. A reboot should clear things up, if anything, but in my case it appears to mess things up.

I've also wondered if the nandroid process was causing the problem, but can't see how making a nandroid copy of my setup could do that.

I guess what I'll test tomorrow is:

1. Simple reboot - see if things still work

2. Create nandroid backup - see if things still work

Wish in this case I was a lot more average....

Hmm. I know this is causing you headache upon headache, but a good test would be to put a virgin ROM (non themed like the FRF57 leak) and after putting it on there, go to the sign up and skip it and then reboot the phone three or four times.

If it still farks up with no apps and no Google account attached, I'd say you have a major hardware issue.

Also, I know you've done battery pulls, but try leaving the battery out for a ridiculously long time - like, say, half an hour or an hour. After that is over, first connect the power cored (to wall charger, not USB) and then insert battery - and let it boot.

Of course, right now after all your trials and tribulations, you're probably thnknig "F it!" and I would not blame you - I would be opting for a ROM that just works right now too. However, if I were you right now, I'd be using SD Lite and putting 2.0 stock, letting it auto update to 2.1 and then taking it to VZW / calling Motorola and asking, nee, demanding a replacement for faulty hardware.

I talking about every time I reboot... not just after the initial restore... It is weird, like I said it is almost like the phone is trying to catch up to the ROM... I was just thinking that it might be because I have my SetCPU main setting at 250/1100, maybe it is staying too long at the lower end when it boots...

OK, was just making sure.
 
Upvote 0
Ska- are you talking about a reboot after initial restore, or are you talking about a reboot after everything is restored, apps installed, and all?

cause RedFlea is talking about what, in this case, would really be a 'second' reboot - after all his apps are back, his setting sin place, etc.

Yeah, it kind of depends on how you look at it. My troubles start w/the first reboot after I have installed the ROM and all apps/accounts/settings are in place.

1. Install Nandroid
2. Reboot to new ROM and complete all setup/config
3. Boot to recovery to create nandroid
4. Reboot to ROM after nandroid and things go crazy

I talking about every time I reboot... not just after the initial restore... It is weird, like I said it is almost like the phone is trying to catch up to the ROM... I was just thinking that it might be because I have my SetCPU main setting at 250/1100, maybe it is staying too long at the lower end when it boots...

That's really interesting...sounds a little similar, but my problems don't ever seem to go away...five minutes, 30 minutes, multiple reboots as things go haywire...symptoms include lockups of the home screen and other apps I try to launch, and eventually the screen goes dark and nothing will wake it and I have to reboot again and things never start working again.

The next time I reboot will try letting things just sit for longer than I usually do and see if that helps.
 
Upvote 0
*edit* i've had no luck with them. has anybody else?

in case anybody cares, these just came out which i've been waiting for butt nakey:

Jake's Froyo Kernels - Jake and Boostdscoob - AllDroid Public Board - Jake's Froyo Kernels - Jake and Boostdscoob - AllDroid Public Board - Forum

might help your wifi problems ;)

best,
rf

I don't know how long it's gonna hold up and how stable it's going to prove to be but I'm seeing unprecedented benchmarks. I had noticed that while MFLOPS have increased, the old SetCPU shortbenches hadn't. Until now. I had OCed to 1GHz and got a 129ms! When I kicked it up to 1.2GHz, I got a 114ms!! And yes, there's a huge diff in speed at that setting.

Ok, it doesn't look like 1.2GHz is gonna be stable for me. I can get it to work, but it'll freeze periodically. Too bad. But man, 1Gig is plenty fast. This is gonna be fun. Thanks for the new options!
 
Upvote 0
Umm ya mototorch doesn't work for me either.

Then your install is b0rked. Or you're not running FRF57, you're running the previous release.

or else you need to uninstall and reinstall Mototorch.

The ROM is no longer interfering with Mototorch as of FRF57, so if yours is not working, you've got an issue on your phone.
 
Upvote 0
I've been getting random reboots ever since I updated to froyo with the original and with this one.

The phone works completly fine and fast but it will just reboot out of nowhere. It never seems to happen while i'm using it only when it sits idle for a while.
It doesn't happen on the charger
If I restore to one of my 2.1 roms it doesn't do it
It happens with the stock 2.2 backup and with the 1.1ghz kernel

Is anybody else having this issue
 
Upvote 0
Then your install is b0rked. Or you're not running FRF57, you're running the previous release.

or else you need to uninstall and reinstall Mototorch.

The ROM is no longer interfering with Mototorch as of FRF57, so if yours is not working, you've got an issue on your phone.

I am running frf57 I think I would know lol. If something was wrong with m phone I would be the only one having issues but I'm not. O and I have reinstalled it as well.
 
Upvote 0
Try uninstalling and reinstalling it.

Also, did you use TiBu to move it to the SDCard? I didn't...

I didn't move it, just restored it. I tried uninstalling and reinstalling and that didn't work either.

I haven't tried LED Flashlight, and while I'm not opposed to it, I want to get MotoTorch working. There's got to be an issue somewhere as there's at least a couple of us having a prob w/ this. Maybe we're not doing something we should be.
 
Upvote 0
I didn't move it, just restored it. I tried uninstalling and reinstalling and that didn't work either.

I haven't tried LED Flashlight, and while I'm not opposed to it, I want to get MotoTorch working. There's got to be an issue somewhere as there's at least a couple of us having a prob w/ this. Maybe we're not doing something we should be.

I did I tried like 4 different ones all the same result.
 
Upvote 0
Unfortunately, the majority of us report that it started working with FRF57, and you and Yankee report that you're still having issues.

It is more than likely that both of you are experiencing issues on your phones rather than the rest of us experiencing issues with our phones that makes it work, yanno?

Very likely. Which would P me O b/c I finally got this thing up and running beautifully, w/ a kernel that's giving me amazing results. And I really need MotoTorch b/c that's something I use a lot.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones