963 replies to this topic

[chrisp6825]

Do you use a tool for building flashable zips, or just type them up? The way you mention "remove frame in add and delete but overlooked it in add" makes me think you're using a tool. Some Windows utility? Not too sure why I haven't bothered in looking at flashable zips yet, with all the small tweaks and mods I do on my own. 

 

I don't mean to hijack or derail this thread, feel free to pm me if you want.

[Bama]

i use a blank theme shell zip..add the apks i want and then rewrite the script for the apks i used using notepad

[chrisp6825]

Been running this ROM for about 2 weeks now, I'm really enjoying it.

Just wanted to stop by and give team litespeed my thanks.
After removing some apps and some personal tweaks, I haven't been interested in running anything else on my bionic. I hope you guys stick around while the bionic continues to fade away elsewhere

sent from a Bionic

[B.E.McAllister]

Been running this ROM for about 2 weeks now, I'm really enjoying it.

Just wanted to stop by and give team litespeed my thanks.
After removing some apps and some personal tweaks, I haven't been interested in running anything else on my bionic. I hope you guys stick around while the bionic continues to fade away elsewhere

And since we're thanking, not only an I thankful for this great ROM but I'd also like to thank you for helping fix my Wi-Fi issue with the Mac addresses. Thanks again

Sent from my DROID BIONIC using Tapatalk 2

[dagalicic]

There were a few things I found while messing with this. I'll send you my notes in a few
-
You must turn wifi off, and run these commands as root in a terminal/adb shell.
 
These are the 3 nvs.bin files I found on my system. You can run the calibrator command on each to determine which is holding the MAC address that your system is reporting :

Please Login or Register to see this Hidden Content

/data/misc/wifi/firmware/wl12xx-nvs.bin
/system/etc/firmware/ti-connectivity/wl12xx-fac-nvs.bin
/system/etc/firmware/ti-connectivity/wl12xx-upd-nvs.bin
 

then to set it :

Please Login or Register to see this Hidden Content

I then rebooted before turning wifi on, turned it on after boot, and checked in system settings. The file wl12xx-upd-nvs.bin was the one that held my current address on my system. The file wl12xx-nvs.bin held an old MAC address, one that sticks even between FXZ's in my experience (it had the shared ICS mac). The only way I found to reset the true MAC address before this, was to FXZ back to 905 GB, then back to the ICS leak I was running, though that's no longer possible.
sent from a Bionic

 

 

Hello all,

 

I am not a developer nor do I know much about the Android OS but I would like to give some feedback here, as I am enjoying this ROM and would love to load it on the girlfriends Bionic also.

 

I also have noticed a different MAC address on this ROM verses the stock ROM.

 

I am also test-driving the Eclipse v5.1 build 5 found here…

Please Login or Register to see this Hidden Content

 

I believe they have figured out how to use the hardware MAX address. Their MAX address is the same as stock MAX address.

 

 

Again, I am not a developer of any ROM's. I just want to give some feedback. Hope this helps.

 

 

 

Go Team LiteSpeed - thanks to all involved great work well done!

[chrisp6825]

I believe the reason the MAC address is not affected in Eclipse (or any AOSP/kexec ROMs) is because this is a shared issue, due to shared base code used in blur ROMs.

It was explained to me that the ICS moto blur ROMs were built on top of the same forked code as each other, thus sharing this bug. If I'm correct, it's the same circumstance with the JB blur ROMs.

If I'm not correct, please feel free to let me know.

sent from a Bionic

[B.E.McAllister]

I believe the reason the MAC address is not affected in Eclipse (or any AOSP/kexec ROMs) is because this is a shared issue, due to shared base code used in blur ROMs.

It was explained to me that the ICS moto blur ROMs were built on top of the same forked code as each other, thus sharing this bug. If I'm correct, it's the same circumstance with the JB blur ROMs.

yeah the way i see it is when the original dioxided was made it was like a snapshot in time that everyone else built off of

Sent from my DROID BIONIC using Tapatalk 2

[dagalicic]

so the question remains...can this be fixed or are we not able to have the same "ICS moto blur ROMs" on two Bionics on the same wifi?

[chrisp6825]

The manual fix I posted should fix the problem, per ROM you apply it on. B.E.McAllister was able to have both his Bionics on this FlyingJelly ROM at the same time on the same WiFi, after doing the fix on one.

The problem is that a router will basically become confused when two devices share the same MAC, constantly redeciding which device is leasing that particular IP address.

Giving one device/bionic a new/different MAC will solve the problem.

As far as reincorporating this "fix" back into custom BLUR ROMs goes, I can't comment on that. Surely it's possible, but it's likely it's not easy, or simply not a priority to the Dev.
It's such a one-off problem, I wouldn't see much purpose in fixing the issue.

I'm currently teaching my self app development. I'm sure I could write one up to apply the fix, or at least a front-end to a script. I'm not sure about putting in the market, but I could certainly post a link to the app and source in these forums.

sent from a Bionic

[B.E.McAllister]

I haven't updated SS yet. Did we ever get a patch or whatever was needed to update the ROM to work with the new SS?

[Eiht]

I haven't updated SS yet. Did we ever get a patch or whatever was needed to update the ROM to work with the new SS?

I haven't tried this one yet but 3.60 let me flash Raging Bionic which was 3.11 only so I would think so.

Sent from my Bionic

[uconnpat]

Is there a minimum size on the partition size?  Because I'be tried it in both slot 2 and slot 1, and did thorough wipes and it just hangs at the boot animation (and by hang I mean 20 minutes)...

[nobe1976]

Is there a minimum size on the partition size? Because I'be tried it in both slot 2 and slot 1, and did thorough wipes and it just hangs at the boot animation (and by hang I mean 20 minutes)...

Partition size doesn't matter. What are you running on your stock side does and which SS recovery you are running.

$3π+ £®m€ ×X× BiOπI¢ oπ $ø|/|£ťhïñğ ¢ű$ț¤|/|

[uconnpat]

Partition size doesn't matter. What are you running on your stock side does and which SS recovery you are running.

$3π+ £®m€ ×X× BiOπI¢ oπ $ø|/|£ťhïñğ ¢ű$ț¤|/|

I kind of thought that... I'm running 4.0.4 stock and ss3.11 in slot 3 I have liquid smooth which is 4.2.2 and I'm about to update my stock to Blur_Version.6.7.246.XT875.Verizon.en.US but I'm a little nervous as I don't want to lose root and a pageplus flash

[nobe1976]

Yeah in order to run this you will have to be on the Blur_Version.98.72.22.XT875 update to run the updated Blur ROMs. Don't know much about the PagePlus addition. You might need to research that first before taking the leap.

[uconnpat]

Yeah in order to run this you will have to be on the Blur_Version.98.72.22.XT875 update to run the updated Blur ROMs. Don't know much about the PagePlus addition. You might need to research that first before taking the leap.

Thanks I am trying to update it now but yeah I think I'm gonna have fix the pageplus thing again... but I know for a fact that there is a guide to do that

[mjs27541]

My signal just completely crapped out.  Tried rebooting a couple times with no effect.  Also got a SIM error message earlier too, but shutting down and pulling and replacing the SIM fixed that.  4G signal is fine on stock slot.  Gonna try reflashing the ROM in a few (after I get through the 33 app updates on stock side...).  Anyone else seeing this? Update: Cache wipe fixed it

[Eiht]

My signal just completely crapped out. Tried rebooting a couple times with no effect. Also got a SIM error message earlier too, but shutting down and pulling and replacing the SIM fixed that. 4G signal is fine on stock slot. Gonna try reflashing the ROM in a few (after I get through the 33 app updates on stock side...). Anyone else seeing this?Update: Cache wipe fixed it

That's why I keep auto update off on stock. If I have to pop over there for a second I don't want to wait for all the updates to lag like crazy.

Sent from my Bionic

[chrisp6825]

So I've found the Bluetooth-freezing bug exists here as well.
I can't seem to escape it, though I'm not too interested in testing on a pure Stock ROM so I'm not sure if it's a device bug or Bionic bug.

I'm curious cause this bug follows me on AOSP ROMs as well as stock-based ROMs.

The bug/freeze happens randomly while using Bluetooth paired to my car radio. It may not happen during a days use, but I've found it tends to happen after about 4 songs sometimes (20~25 mins). The device freezes and will reboot after about 2 minutes, then all its fine (on AOSP ROMs I'd have to disable then re-enable the Bluetooth service, not just the toggle).

It seems to happen less often on this ROM, so I'm a bit of a happy user. Just wish I knew what the crap is going on here..


Sent from my DROID BIONIC using Tapatalk 2

[nobe1976]

After you ruining any type of over clock scripts or extra governors? The only reason I ask is I use a LG wireless headset that connects just the same audio and media. I have had the same issue only when the display times out when running extra governors. $3π+ £®m€ ×X× BiOπI¢ oπ $ø|/|£ťhïñğ ¢ű$ț¤|/|