DROID BIONIC Jelly Bean Update

[SamuriHL]

ahhhhhh...."I see" said the blind man. By bootstrap, I thought you meant Bionic Bootstrap which I knew was a baaaad thing. I've alays called Clockwork....well, clockwork.

I'll get rid of "the other", read up on safestrap, and stop buggin' ya

CWM is just another version of bootstrap. And will in fact brick your phone again if you use it. So yea, get rid of it and go with safestrap. Then put a nice 4.2.2 kexec based rom on that thing and enjoy!

 

[SamuriHL]

Apps are easy enough to reinstall. But what about all the photos I have on the phone??

What about them? Throw them up in dropbox and install dropbox to your pc and keep them in sync.

 

[bacchus224]

The suggestion that no one ever likes and everyone who has a phone that isn't working right always spends more time avoiding than doing. FDR. Give it a clean start.

Even though I knew it wouldn't be fun I went ahead and did the FDR last night and then spent hours reinstalling apps. Unfortunately, the phone does not seem any better. Still a lot of lag, slow screen refreshes, apps slow to open, etc.

Any ideas?

Also, when I did the FDR, I DID NOT, select the option to erase the internal memory. Should I have in order to get a good reset?

 

[SamuriHL]

Even though I knew it wouldn't be fun I went ahead and did the FDR last night and then spent hours reinstalling apps. Unfortunately, the phone does not seem any better. Still a lot of lag, slow screen refreshes, apps slow to open, etc.

Any ideas?

Also, when I did the FDR, I DID NOT, select the option to erase the internal memory. Should I have in order to get a good reset?

Might not hurt. It can take a day or two for the phone to settle down, too.

 

[bacchus224]

Might not hurt. It can take a day or two for the phone to settle down, too.

I was wondering about the "settling down" issue as well. I will give it a few days. If I decide to FDR again I will definitely go the whole enchilada and delete the internal. I was also thinking that if I do FDR again, I might re-format the SD card. Problem is I can't figure how to do that.

 

[SamuriHL]

I was wondering about the "settling down" issue as well. I will give it a few days. If I decide to FDR again I will definitely go the whole enchilada and delete the internal. I was also thinking that if I do FDR again, I might re-format the SD card. Problem is I can't figure how to do that.

Should be an option in the storage settings.

 

[bacchus224]

Should be an option in the storage settings.

I have an option to erase and one to unmount. Will erasing and remounting re-format the card?

 

[roadpizza73]

I was doing great with the Linux thing until out said to ensure my Bionic was connected via wifi.

I've found no way to connect my bionic to the Linux box via wifi. Bionic wifi doesn't see the Linux wifi. I even setup an add-hoc network on the Linux wireless adaptor but bionic wifi doesn't see it. There's no home wifi network to use here, soooo

Sent from my DROID BIONIC using Android Central Forums

Edit/add: Dr. S, I posted this hoping i was missing something stupidly simple. Following this and other forums, I'm unwilling to bother you for hand-holding until I've exhausted all other options.

I'm actually enjoying re-familiarizing myself with Linux and routers.

I later found a new-in-box router in my junk piles, and actually got the phone and Linux box pinging each other, so there is/are other issues that I'll continue to seek and attempt to resolve on my own if possible.

Thanks for the assurance of assistance! A safety net makes me feel better!

I believe I'll have enough of a block of time this weekend to start from scratch, prolly fxz and all.

I've not used a computer since getting this Bionic (a personal 'can it need done' thing) but now seeing how far Linux has come, I'm sure I'll be tinkering with it more, this from a person who started with C/PM, or was it CP/M, gollee, gitin' old's a bear sometimes

Hoping to not needing to bug y'all,

rp

Sent from my DROID BIONIC using Android Central Forums

 

[SamuriHL]

I have an option to erase and one to unmount. Will erasing and remounting re-format the card?

Not sure. I'm guessing so.

 

[SamuriHL]

Edit/add: Dr. S, I posted this hoping i was missing something stupidly simple. Following this and other forums, I'm unwilling to bother you for hand-holding until I've exhausted all other options.

I'm actually enjoying re-familiarizing myself with Linux and routers.

I later found a new-in-box router in my junk piles, and actually got the phone and Linux box pinging each other, so there is/are other issues that I'll continue to seek and attempt to resolve on my own if possible.

Thanks for the assurance of assistance! A safety net makes me feel better!

I believe I'll have enough of a block of time this weekend to start from scratch, prolly fxz and all.

I've not used a computer since getting this Bionic (a personal 'can it need done' thing) but now seeing how far Linux has come, I'm sure I'll be tinkering with it more, this from a person who started with C/PM, or was it CP/M, gollee, gitin' old's a bear sometimes

Hoping to not needing to bug y'all,

rp

Sent from my DROID BIONIC using Android Central Forums

One thing I've been recommending to most people who are using the Linux exploit, and this is really screwing with a lot of people's success rate, is to AT LEAST flash the system.img from 98.72.22 FXZ before doing the Linux exploit. Better, obviously, is to use the HoB 10.1 with the 98.72.22 FZ (NOT the 246 FXZ) and use the FXZ Keep Data option to give it a fully clean start. Then once you get all the connection issues solved the exploit tends to simply work.

 

[Robert Tucker2]

CWM is just another version of bootstrap. And will in fact brick your phone again if you use it. So yea, get rid of it and go with safestrap. Then put a nice 4.2.2 kexec based rom on that thing and enjoy!

Well, once again, "you da' man!". I have safestrap and have backed everything up so I can start playing. I tried safestrap a while back and didn't like it, but the new UI is very nice (awe he**, it could look like crap as long as it works LOL)

I'll be trying out LiquidSmooth 2.2.1 this weekend if the kids will leave me alone.

 

[804hokie]

Sam,

What are some ROMs I might look into, should I want to try JB 4.2.2? Not saying I don't like the one I have now, but always looking to enhance my Bionic.

 

[SamuriHL]

Sam,

What are some ROMs I might look into, should I want to try JB 4.2.2? Not saying I don't like the one I have now, but always looking to enhance my Bionic.

Don't know. I don't do roms on the Bionic. Never have. You'll have to take a look and see what's out there. The beauty of SS is that you can drop a few of them into different slots to compare and see what works for you. Switching between them is like seconds from what I understand. But I've always been stock on the Bionic.

 

[moonlightinwhite]

What are some ROMs I might look into, should I want to try JB 4.2.2? Not saying I don't like the one I have now, but always looking to enhance my Bionic.

Check out: Droid Bionic Android Development - xda-developers

AFAIK, the 4.2.2 ROMs aren't any different now than they were prior to the JB OTA. I'm hoping there will be a non-KEXEC AOSP 4.1 ROM out soon. Seems to me that KEXEC ROMs can't be as stable or fast as one using the native kernel, but I don't have any evidence to support that, just my own assumptions.

 

[SamuriHL]

Not a good assumption at all. The kernel that someone is working on for the kexec stuff will soon surpass the stock kernel as it will be overclockable and give new choices for governors.

 

[moonlightinwhite]

Not a good assumption at all. The kernel that someone is working on for the kexec stuff will soon surpass the stock kernel as it will be overclockable and give new choices for governors.

Fair enough

I suppose I figured that KEXEC ran on top of the native kernel and so you're essentially running two kernels...which seems inefficient. If nothing else, you have to dedicate at least SOME resources to the "real" kernel, don't you? Perhaps I just don't understand how it works.

 

[SamuriHL]

Fair enough

I suppose I figured that KEXEC ran on top of the native kernel and so you're essentially running two kernels...which seems inefficient. If nothing else, you have to dedicate at least SOME resources to the "real" kernel, don't you? Perhaps I just don't understand how it works.

You do not. So let me see if I can open your eyes a bit.

Normal boot sequence (VASTLY oversimplified for illustration purposes):
-mbmloader boots up
-kernel loads into memory
-kernel initializes
-system boots up

Now let's take a look at how kexec works:
-mbmloader boots up
-kernel loads into memory
-kernel initializes.....kexec hooks the init process and initiates a Kernel EXECution (see where kexec comes from?) to cause the following:
o) New kernel is loaded into memory, overwriting the existing kernel (this is the key)
o) New kernel is initialized
o) System boots up with new kernel in memory

Again, I've vastly oversimplified this just so you can see the chain of events and how kexec works. But since we can't physically overwrite the bootloader partition to install a new kernel, kexec simply waits for the kernel to load and start initialization and hooks that process to cause a second kernel to overwrite the first in memory. There are NOT two kernels running....it's a memory replacement.

 

[moonlightinwhite]

You do not. So let me see if I can open your eyes a bit.

Normal boot sequence (VASTLY oversimplified for illustration purposes):
-mbmloader boots up
-kernel loads into memory
-kernel initializes
-system boots up

Now let's take a look at how kexec works:
-mbmloader boots up
-kernel loads into memory
-kernel initializes.....kexec hooks the init process and initiates a Kernel EXECution (see where kexec comes from?) to cause the following:
o) New kernel is loaded into memory, overwriting the existing kernel (this is the key)
o) New kernel is initialized
o) System boots up with new kernel in memory

Again, I've vastly oversimplified this just so you can see the chain of events and how kexec works. But since we can't physically overwrite the bootloader partition to install a new kernel, kexec simply waits for the kernel to load and start initialization and hooks that process to cause a second kernel to overwrite the first in memory. There are NOT two kernels running....it's a memory replacement.

Ah, thanks for the crash course! I definitely thought both the native and second kernel were running in parallel (and furthermore, that the first was necessary for the second to run at all times).

Neat.

 

[SamuriHL]

Ah, thanks for the crash course! I definitely thought both the native and second kernel were running in parallel (and furthermore, that the first was necessary for the second to run at all times).

Neat.

kexec - Wikipedia, the free encyclopedia

 

[bpeter35]

Did an FDR the other day. Not happy with performance of phone after a couple of hours of use. Assuming a program was not releasing its cache memory. I did check the clean internal memory option. I did not do this after the upgrade from ICS, so could have also been issues left behind from previous OS. On day three after FDR and battery life and snappiness is great. Do have one question though. Is anyone else able to disable the text messaging app native to the phone? If so, how. I googled this, but not really finding anything. Thanks ahead of time.