No2Chem nueROM 2.0 (WM6.1) Thread

[TraderStav]

Originally Posted by Jim

Not Flaming or anything...but if tethering for primary internet becomes widespread...I fear Sprint will be "fixing" that problem so everyone that tethers because their hotel doesn't have broadband, or on vacation, or as a backup if their main ISP goes down...will no longer be able to do so without huge charges or a high monthly plan.

Again, not pointing fingers, but I hope you at least have a tethering plan if you are going to use the phone as your primary ISP.

Point taken. I respectfully disagree though, if this was a concern of theirs then the feature would be more diligently addressed. I purchased the phone and copied a 100k file to the device. With no hacking I was able to utilize it in this manner. I call this use as intended, regardless of how they want to code it otherwise. If I had to reverse engineer to do so, I would agree with you. If they thought the same way it would be much more difficult to get this to work.

Not a debate for this thread however.

Originally Posted by saumaun

I would THINK this is normal if you are tethering for long periods of time. The program uses ALOT of battery, and it is possible that your phone overheated. If that happens, I would make sure to let the phone cool.

I was utilizing this same feature with my Touch for several months over USB and never had an issue. This leads me to believe that it is either hardware or ROM centric as problem.

[marky-b]

Originally Posted by marky-b

Alright, so i reflashed with build 5059, and i let it go through the installation, and the phone reset itself.

However, after it restarted, it now freezes on the 'HTC smart mobility' screen, after the rom and radio versions post, and disappear.

I've soft and hard reset with no luck

Any suggestions or fixes?
Thanks.

alright, i zipped back into the bootloader and reflashed. all is working now

Originally Posted by jamesus

Read the stickies in the Upgrades forum, as they provide all of the information that you are looking for.

Thanks! I will go there, now.

[[sammich]]

Originally Posted by TraderStav

I was utilizing this same feature with my Touch for several months over USB and never had an issue. This leads me to believe that it is either hardware or ROM centric as problem.

The OP of the question said he was using the WiFi portion. USB doesn't seem to get the phone hot at all, and when I can, I use that.

Originally Posted by TraderStav

Point taken. I respectfully disagree though, if this was a concern of theirs then the feature would be more diligently addressed. I purchased the phone and copied a 100k file to the device. With no hacking I was able to utilize it in this manner. I call this use as intended, regardless of how they want to code it otherwise. If I had to reverse engineer to do so, I would agree with you. If they thought the same way it would be much more difficult to get this to work.

Not a debate for this thread however.

And I do agree with you on this issues as well.

[TraderStav]

Originally Posted by saumaun

The OP of the question said he was using the WiFi portion. USB doesn't seem to get the phone hot at all, and when I can, I use that.

And I do agree with you on this issues as well.

I am the OP. Perhaps I'll have to move over the USB if this method is unreliable. Not ideal, but not terrible either.

[[sammich]]

Originally Posted by TraderStav

I am the OP. Perhaps I'll have to move over the USB if this method is unreliable. Not ideal, but not terrible either.

Is the lock-up issue constant?

I'd say use wired when you can, WiFi when its necessary. That way you can balance any issues that arise.

[TraderStav]

Originally Posted by saumaun

Is the lock-up issue constant?

I'd say use wired when you can, WiFi when its necessary. That way you can balance any issues that arise.

Today was the first trial as I received the phone yesterday. It seemed fairly consistent. One thing to note though is that I discovered that the plug it was using was loose and for some period of time was working off of its battery. I don't know if that has an impact. As I posted it in this thread, would this be a potential Rom-centric problem or other? If other I'll keep nue on here and start using the wired. If it is could you recommend another rom to try for my purposes?

[no2chem]

Originally Posted by Jeff Kirvin

No2Chem,

Please, don't make using the official PPCgeeks kitchen a requirement to build future ROMs. It's nice that your basekit is compatible, but given the egos involved on that project and their insistence on using user-hostile "features" like the login requirement that does nothing and makes the kitchen impossible to use behind corporate proxies, I'd like be able to continue using the wonderful innovations you provide without being forced to use their product.

the basekit isn't dependent on any specific kitchen. it just happens to be buildos compatible. and seeing that I actually use buildos, theres no reason for me not to support it. and theres plenty of support out for buildos - i see that people in the kitchen thread trying to help you out.

if you don't like buildos, theres nothing stopping you from dropping my basekit into another kitchen. granted, if it uses any version of imgfstonb that i know of, it'll probably crash. of course, you can manually fix it, but i'm not about to walk people through that, since I can't seem to get it right myself anymore.

however, I'm not going to support any other type of kitchen, because its too much work on my part to make sure the basekit works with any configuration out there. besides, i've already included the \rom, \sys and \oem dirs making it pretty simple to drop into any kitchen...

[Jeff Kirvin]

Thanks for taking the time to respond.

[jbbosu]

Quick question from an fellow no2chem-user.

I've already read the Kitchen Sticky and still am curious:

What exactly is this new "19202 build?" How is that different from the general 5059 build ROM? Is it just improvements to the OS or something?

Thanks for the patience.