icon123

I agree. I would say it must be something with my headset, but it works on every other rom stock or custom. When it doesn't pair after FCing, it gives a "couldn't pair with this device" something about wrong pin or passcode. Let me know if there is something else I can do to test.

darkxsun

Do you have another device you can attempt to pair with your phone?

darkxsun

Experimental bluetooth fixer. Backup before trying, please.

EDIT: updated: byron_bluefix.zip

Last edited by darkxsun; March 1st, 2011 at 11:35 PM.

darkxsun

Regarding wifi tether: It seems that I had a false positive. If you install (in normal /data space), then flash a /system version overtop of it, it will continue to work. However, it's still not working if you flash from the beginning. I have no idea why.

icon123

Mediafire is not liking me this morning, can you post it here?

Edit - Mediafire is working with you other links, so it must be something to do with this one.

Edit2 - My car BT doesn't like Byron either, did the same thing as my earpiece. Obviously, haven't tried the 'fix' yet.

Last edited by icon123; March 2nd, 2011 at 08:18 AM.

darkxsun

The file is fine, working for me at work. Are you using the updated one or one you got via email subscription to this thread? The latter would no longer work.

I'm attempting to attach the file here.

Attached Files

byron_bluefix.zip (3.0 KB, 5 views)

icon123

When I click on the download link within media fire, it goes to a 403 forbidden page. Maybe because I don't have an account with them. Like I said all your other MF links work fine, just that one.

Anyhow, since I don't subcribe to this thread, I downloaded the latest one that you attached to your last post.

It nows says that pairing was refused by my earpiece. When I try it again it FCs. Definetly different then what it did before. It did the same thing via my nandroid backup or fresh Bryon lite install.

Edit - BTW, do you not have a BT device or are you just not having problems with it?

Corki2

I have a similar problem. I can pair with my bluetooth headset fine, but when I attempt to pair with my laptop, it will FC. When I initiate pairing from my phone, it phone finds my laptop, but can't pair with it. I get "unable to pair HP rejected..." When I initiate pairing on my laptop, it displays the choose your pin, etc. but as soon as I select "enter pin" and hit next, it FC on my phone. I downloaded the bluetooth fix, but have no idea what to do with the file. I'm new to all this. I'm running Bryon Full, BTW. It worked before I rooted and flashed.

darkxsun

@icon123 - bt works as expected for me in every imaginable test
@corki2 - flash it like a rom, using recovery, over byron

Corki2

Thanks darkxsun. I flashed the BT update but it had no effect. I finally figured out it was an issue with my laptop, not the ROM. I had to reinstall my BT drivers. It's working fine now. I love this ROM.

darkxsun

icon, do you have the Voice Dial addon installed? Try installing that, then connect again.

icon123

Reinstalled rom and addon, just to make sure. Although it didn't seem to FC as much, it did say that it was rejected by my headset more. I tried it with your voice dial add-on and with and without the BT fix you posted a couple of days ago.

In never gets to the confirmation point where it asks if you want to connect with BT device. These error messages happen right when I click the BT device to pair.

I appreciate your dilegence, but since no one else seems to be having this same problem, you can let it go. Thanks for trying.

pyroticshadow

Thread is old, but problem I'm having isn't listed so I thought I'd add.

After flashing with Byron Bare on my LG Ally 2.2, it boots fine, except I get to the "Welcome to Ally" screen and my touch screen no longer works.

Do you have any idea of how to fix this? I've tried other roms, I've tried a nandroid restore, I've tried stock rom, I've tried taking battery out, push power 5 times to reset, I can get into my recovery mode to launch the roms from my SD, but that's the extent of anything I can do otherwise.

ANY ideas, would be wonderful. It sounds to me like something within' one of the roms (not specifically yours) changed some radio setting or otherwise that I'm unable to change back without the knowledge of how. If not that, I'm not sure what to do.. I know it's not permanently bricked as all the hardware keys work and nothing happened that would have damaged the touch screen, it just isn't being loaded during boot (my assumption).

darkxsun

Does this happen with other ROMs? There's no really good reason I can think of that the touch screen wouldn't be loaded during boot. This sounds like a hardware issue.

If this happens in all ROMs, then the best thing to do, I think, is to use the LG-sanctioned tools to go back to stock, and if things work, work your way back up to rooted 2.2. If not, you've got busted hardware.

Valkerie

It happens on occasion with Velocity 1.0 for me too.

__________________
Incredible 2 - AOKP ICS Build 31

Nook Color - unofficial CM9 nightlies

LG Ally - StormDroid 2.0(retired)

darkxsun

Is there a solution?

pyroticshadow

It does happen with all ROM's, but was working FINE before I flashed it. It does it with Velocity, byron, etc. I've even tried the "I need a volunteer who wants to go back to completely stock" instructions, it goes through to the same screen "Welcome to Ally" but I can't touch the screen, it doesn't respond.

I've tried everything I can think of, but I don't have a clue what steps to take next.

darkxsun

Sounds like hardware.

I definitely think you should try the LG way rather than that flashed-stock way though.

pyroticshadow

I know I've heard of simple hardware failure before, being in IT this happens frequently, but it happened subsequently after flashing the rom, so I still believe it's fixable.

How do you suggest I go about doing that? I can't get into USB Debugging mode for the computer to see the phone. The only way I can access things is in aloha recovery usb-ms.

darkxsun

Use the instructions here: [GUIDE] FroYo 2.2.1 for Root Users! (Updated 3/3/2011 at 3:40 pm EST - NOW EASIER THAN EVER!) to get back to v6 (don't go farther than using KP500-Utils, at first, until you find out of your screen will work in v6).

If it's software, that's essentially the biggest gun you have. If that doesn't work, I have very little hope.

pyroticshadow

But it asks to enable usb debugging as the 3rd step, I cannot do that. I cannot access that menu.

darkxsun

Isn't Byron set to be in that mode automatically? I can't remember now. If not, I feel like one of the other ROMs around here is set that way...

Regardless, give it a shot anyway. If that doesn't work, try starting it from recovery. If that still doesn't work, try flashing different ROMs to find one pre-set that way.

pyroticshadow

Velocity is supposed to be, but it isn't. I've tried all the roms available for Ally and none of them do it. They all flash fine and boot fine, and get to that screen and I'm done I can't go any further.

I'll keep that link on hand.

Would I be better off if I could flash the STOCK recovery? Would I have more options? or is the aloha recovery going to do better off for me right now. That's about the only thing I haven't tried, currently I'm restoring a v6 stock nandroid, in hopes that'll work. Likely won't. Nope. Goes through a boot loop, hits the Verizon logo, flashes a blue light and reboots and repeats til I pluck battery.

Damn it, this is getting frustrating. As easy as everyone else made flashing sound, I feel like a complete imbecile.

darkxsun

The stock recovery has *no* options. You can't do anything other than flash a signed ROM from LG if it's in the predefined place with the predefined name. No menus, no nothing.

pyroticshadow

Alright.

Well, I think I'm out of options, I decided to use the stock recovery flash before I read your reply, now it won't even boot to anything but boot loop. When I try to boot to recovery it brings up the Android and the Package installing icon, then reboots. So that failed as well.

Off to Verizon to get a replacement.

Sorry to bother you.

darkxsun

That's exactly what the stock recovery is expected to do. You should still be able to boot the normal way.

pyroticshadow

Had I been informed of that utility I may have been able to restore the phone, but now that I did that last flash, it won't. It doesn't stay on long enough for the application to do anything.

Damn it, Damn it, Damn it.

darkxsun

What utility? What application?

pyroticshadow

The link you provided.

Anyhow, I returned the phone and got a replacement. What is the safest "rooting" procedure, with the Ally? I refuse to flash the rom again after what happened, but I'd like to at least have root capabilities. I used Super One Click, last time. But I hear that it's not the safest/best route.

Input?

darkxsun

Super One Click? I don't even think this is supported on 2.2 on the Ally. In my first post, I said this ROM was for people who had gone through a specific 2.2 rooting procedure.

I don't think you spent enough time doing your research before you dove in, and then when you messed up your phone of your own accord, you left LG to pay for it (Verizon did the exchange, but they were a middleman to LG's warranty). I don't agree with this. If you followed the approved process, linked in a sticky at the top of this forum, I don't believe you'd have ended up where you did, and I don't think the route you took to fix it was right. When you tinker outside of approved methods, you take responsibility.

I don't mean to sound like a jerk, but this is my feeling on the subject.

Since this is no longer about the ROM (indeed, you "refuse to flash the rom again"), please look for help elsewhere. This thread is no longer the place.

pyroticshadow

I didn't spend enough time doing my research, and yes SuperOneClick does work to root 2.2 on the Ally, I just did it with my replacement.

Yeah, it was out of line to cause LG to land up with the dead phone on behalf of my stupidity, I don't deny that and I haven't denied that. I know where I went wrong and I'm sure I could avoid that, but I'm not going to try again until I do tons more research. I'm sorry I offended you in that manner.

Thank you for your time and your patience.

Take care,

odbo255

Thank you so much for your hard work!

I'll second the requests for Voice Search and Pandora.

Also, if an odexed app updates itself from the market, will it still be odexed?

Oh, one more app request: Titanium Backup

Last edited by odbo255; February 5th, 2012 at 09:17 AM.

darkxsun

Unfortunately, all versions of Byron are legacy and unsupported. I was working for a while on a project built on 2.2.2 which I was calling ponder, which would have become (something like) Byron 5, but it never became completely official.

Odexed apps, when updated, are stored deodexed in /data in the same way they would be if they were not system apps to begin with. This is why I was pretty diligent about updates during Byron's small popularity. Unfortunately, as that popularity faded, so did the project.

I hope you can still enjoy the work. If you are somewhat adept at tinkering (not necessarily a dev, but comfortable flashing and working at the command line), I can find a way to provide you my last version of ponder.

odbo255

Thanks for the reply and clarification on the affect of updates. When I installed Byron I had to scramble the first time entering the market to prevent the odexed apps from auto-updating.

I'm running a full install of Byron with the apps I'm not interested in backed up and then frozen by TiB.

I'm encountering an issue with the Wireless Tether app, it force closes when it tries to initiate the hotspot. Superuser has never prompted me to grant it root permissions so I suspect the app is attempting to perform "root-only" activity without the required permission grants. Any thoughts on how to resolve this? I downloaded a very similar app of off the market: Open Garden Wifi Tether and that one doesn't have an issue and super user did the initial prompt for permissions as expected.

Thanks again for all of your hard work. I am tentatively interested in seeing if I can continue to support Byron, I sent you a PM.

Last edited by odbo255; February 6th, 2012 at 11:57 PM.

verizonuser13

Any screenshots of the ROM??

xepicxacidx

It looks like the stock rom like it says its "Odexed" meaning it cant be themed

verizonuser13

So it's only an updated Stock?? Sounds convenient for people who want stock with dumb apps removed. I'll stick with velocity though lol

darkxsun

Are you using the Wireless Tether package from the first post? I had on-and-off problems with it... It's something related to files in /data not getting the correct permissions when installed as a system app (thus, the binaries that actually enable tethering can't be installed, and therefore it doesn't get so far as asking for root). The same app is available here: android-wifi-tether - Wireless Tether for Root Users - Google Project Hosting and works if you install normally.

I'll get all of my files together and get back to you. At the moment I'm up against deadlines at work.

The intent of this rom was never unclear---it's stock-like. I would call it "optimized" rather than "updated".

Feel free. Byron does not directly compete with Velocity, they have distinct goals.