DROID BIONIC Jelly Bean Update
- Thread starter Ry
- Start date
But isn't that the whole reason they made Google current? I could have sworn that was the plan all along.
Sent from my DROID BIONIC using Android Central Forums
SamuriHL
Well-known member
- Feb 22, 2011
- 2,084
- 81
- 0
Maybe. But I use reader non-stop throughout the day on both my laptop and my tablet. It stays in sync. It's great. Idjits.
I use Es File Explorer to back up my apps then email the apk to myself. There may be an easier way to do it, but it works.
Sent from my DROID BIONIC using Tapatalk 2
Lol that is probably easier than how I do it. Which is to create a backup...hookup to the computer and copy the backup file to the pc desktop...then hookup the Kindle to the pc and copy it on t
Sent from my DROID BIONIC using Android Central Forums
copy it on the Kindle from the pc. I'm going to give the email route a try.
Sent from my DROID BIONIC using Android Central Forums
Sent from my DROID BIONIC using Android Central Forums
Just read this and thought you might be interested: Feedly could save Google Reader clients with cloned API
http://www.theverge.com/2013/3/13/4101534/feedly-clones-google-reader-api
Sent from my DROID BIONIC using Android Central Forums
The one thing I noticed on my wife's Razr is in text messaging since the update the conversation boxes are now completely even compared to how they looked on ICS and how it currently looks on my Bionic. It's a minute change but it looks much more crisp & clear. Is that part of project butter?
Sent from my DROID BIONIC using Android Central Forums
Sent from my DROID BIONIC using Android Central Forums
SamuriHL
Well-known member
- Feb 22, 2011
- 2,084
- 81
- 0
Not sure. But one thing I want to remind people about the Moto JB builds for OMAP4 phones. It's 4.1.2. It's NOT 4.2.x. There is a big difference between the two versions. 4.1.2 is fine, but, it lacks multi-user stuff and a lot of other enhancements that those on nexus tablets or other devices that are on 4.2 take for granted.
Not sure of the exact timeline on the releases but is it because 4.2 was after they already started working on the moto jb builds, something technical, or just not wanting to put those resources towards devices that were nearing EOL.
Sent from my DROID BIONIC using Android Central Forums
Going back to my lack of understanding about the bootloader and kernel and stuff...do you know if 4.1 and 4.2 share (or would share, were we getting 4.2) a bootloader and/or kernel? As someone comfortable with ROMs, I'm thinking forward to whether or not we could (eventually) see a stable 4.2 ROM out of an official 4.1 release. There's an active CM10.1 ROM out there, but it's pretty buggy (which is to be expected, of course).
SamuriHL
Well-known member
- Feb 22, 2011
- 2,084
- 81
- 0
Well, the locked bootloader means there is not ever going to be a native 4.2 kernel for the bionic. So any fixes that would be required to be added to the kernel to get things to work (usually BT, camera, etc) won't be there. As a result, 4.2 roms will have the same problems that 4.1 roms have trying to run on the kernel that shipped with ICS. Your only hope is the work being done on Kexec kernels. If they get that process working well, you can install safestrap and install a Kexec based rom that replaces the kernel in memory with a second init. It's as close as you're going to get on a locked device.
Okay, so then a new kernel is needed for an new API level (regardless of the device)? I ask because I was under the impression that 4.0.3 and 4.0.4 used the same kernel (but they're of the same API). I guess 4.1 and 4.2 are different APIs.
SamuriHL
Well-known member
- Feb 22, 2011
- 2,084
- 81
- 0
Remember that kernel versions are independent of the OS version....HOWEVER, what they typically do is add fixes to a kernel to ship with a new version of an OS. If the framework changes, as what happened from 4.1 to 4.2, then kernel fixes will be necessary. And without being able to flash a new kernel, it's difficult to get things working. That being said, I'm told that the very latest test release of the Kexec kernel for the Bionic's CM 10.1 release (4.2.2) has almost every problem solved. Camera's working, BT's working, etc. Small bug with the speakerphone but I'm sure that'll get cleaned up before it's added as an official CM 10.1 build. They can do this by using second init to replace the kernel in memory, thus somewhat bypassing the locked bootloader. Not that it does *NOT* change anything on your phone. It's not bypassing the security of the partitions on your device and modifying them. It's simply loading a second kernel in memory after the official kernel loads. It's close, but, not a perfect solution. However, that's all we're going to get on the Bionic.
Well, seems like the S4 looks pretty good.
Fortunately I was able to interpret these feelings correctly: loss of essence.
Fortunately I was able to interpret these feelings correctly: loss of essence.
SamuriHL
Well-known member
- Feb 22, 2011
- 2,084
- 81
- 0
But then again I bought a Bionic; so I am a little prone to hype.
Fortunately I was able to interpret these feelings correctly: loss of essence.
SamuriHL
Well-known member
- Feb 22, 2011
- 2,084
- 81
- 0
I'm looking through the hype at the phone itself and I like what I see. If they have a dev version that works on VZW's network I'm very possibly there. If they give me time to take a hard look at Ghost, then they may lose the buzz they just created. I will *NOT* wait 6 months for a dev phone to come out.
Sure, looks good. But I'm not convinced. If HTC One was on Verizon I'd pick it over the S4. Also, I still have high hopes for whatever Motorola brings out. I'm the type that doesn't like being with the crowd, so S4 is unappealing in that way too.
Facebook
Twitter
Instagram