Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
ICS .244 leaked for Bionic (pulled from staging server)
Well it's looking kind of not good for those sources and better for Thom Little, it seems we have ICS .244
*edit*
I have .244 up and running, it is rootable
Last edited by dautley; September 12th, 2012 at 01:56 PM.
The Following User Says Thank You to dautley For This Useful Post:
From what I am reading, .242 was rejected because flash is still broken. .244 was then created, but it continues to have flash issues just like the previous builds. For some reason, it appears Verizon is hung up on the fixing of flash before they will sign off on a build.
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
Quote:
Originally Posted by Thom Little
I added 6.7.244 to the reference document. Is 6.7.244 still locked?
I keep wondering what "SMP PREEMPT" means.
... Thom
Same security as 235 and up, I know SMP stands for Symmetric Multiprocessor System, (basically two or more cores) and preemption has to do with the way/modes the Kernel handles task the but not really sure what the "SMP PREEMPT" is exactly.
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
Quote:
Originally Posted by Maddog241
From what I am reading, .242 was rejected because flash is still broken. .244 was then created, but it continues to have flash issues just like the previous builds. For some reason, it appears Verizon is hung up on the fixing of flash before they will sign off on a build.
Waiting for .246 then I guess!
Honestly, if Adobe quits supporting flash on Android and Google quits supporting flash on Jelly Bean it should be a hint, you would figure Verizon would pick up on it.
The Intern Verizon put in charge of Bionic development must really like his/her flash videos!!
Last edited by dautley; September 10th, 2012 at 10:01 PM.
Device(s): Bionic (98.72.22)
Droid X (4.5.621 root)
Carrier: vzw
Thanks: 885
Thanked 938 Times in 667 Posts
Quote:
Originally Posted by dautley
Same security as 235 and up, I know SMP stands for Symmetric Multiprocessor System, (basically two or more cores) and preemption has to do with the way/modes the Kernel handles task the but not really sure what the "SMP PREEMPT" is exactly.
Adobe isnt supporting flash anymore for android so i dont see VZ's problem with flash it's all nonsense to me.
To you and the rest of us as well. Allegedly the same thing happened with the Razr build (flash problems) and it created a support nightmare with complaints, so the belief is Vzw is trying to avoid a repeat of that.
But, like you said, flash is basically dead in the water anyway.
In computing, preemption (more correctly pre-emption) is the act of temporarily interrupting a task being carried out by a computer system, without requiring its cooperation, and with the intention of resuming the task at a later time. Such a change is known as a context switch. It is normally carried out by a privileged task or part of the system known as a preemptive scheduler, which has the power to preempt, or interrupt, and later resume, other tasks in the system.
User mode and kernel mode
Kernel preemption
In any given system design, some operations performed by the system may not be preemptible. This usually applies to kernel functions and service interrupts which, if not permitted to run to completion, would tend to produce race conditions resulting in deadlock. Barring the scheduler from preempting tasks while they are processing kernel functions simplifies the kernel design at the expense of system responsiveness. The distinction between user mode and kernel mode, which determines privilege level within the system, may also be used to distinguish whether a task is currently preemptible.
Some modern systems have preemptive kernels, designed to permit tasks to be preempted even when in kernel mode. Examples of such systems are Solaris 2.0/SunOS 5.0[1], Windows NT, the Linux kernel 2.6 and 3.x, AIX and some BSD systems (NetBSD, since version 5).
Preemptive multitasking
The term preemptive multitasking is used to distinguish a multitasking operating system, which permits preemption of tasks, from a cooperative multitasking system wherein processes or tasks must be explicitly programmed to yield when they do not need system resources.
In simple terms: Preemptive multitasking involves the use of an interrupt mechanism which suspends the currently executing process and invokes a scheduler to determine which process should execute next. Therefore all processes will get some amount of CPU time at any given time.
In preemptive multitasking, the operating system kernel can also initiate a context switch to satisfy the scheduling policy's priority constraint, thus preempting the active task. In general, preemption means "prior seizure of". When the high priority task at that instance seizes the currently running task, it is known as preemptive scheduling.
The term "preemptive multitasking" is sometimes mistakenly used when the intended meaning is more specific, referring instead to the class of scheduling policies known as time-shared scheduling, or time-sharing.
Preemptive multitasking allows the computer system to more reliably guarantee each process a regular "slice" of operating time. It also allows the system to rapidly deal with important external events like incoming data, which might require the immediate attention of one or another process.
At any specific time, processes can be grouped into two categories: those that are waiting for input or output (called "I/O bound"), and those that are fully utilizing the CPU ("CPU bound"). In early systems, processes would often "poll", or "busywait" while waiting for requested input (such as disk, keyboard or network input). During this time, the process was not performing useful work, but still maintained complete control of the CPU. With the advent of interrupts and preemptive multitasking, these I/O bound processes could be "blocked", or put on hold, pending the arrival of the necessary data, allowing other processes to utilize the CPU. As the arrival of the requested data would generate an interrupt, blocked processes could be guaranteed a timely return to execution.
Although multitasking techniques were originally developed to allow multiple users to share a single machine, it soon became apparent that multitasking was useful regardless of the number of users. Many operating systems, from mainframes down to single-user personal computers and no-user control systems (like those in robotic spacecraft), have recognized the usefulness of multitasking support for a variety of reasons. Multitasking makes it possible for a single user to run multiple applications at the same time, or to run "background" processes while retaining control of the computer.
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
Thanks for clearing that up as I thought it referred to Symmetric Multiprocessor System, (basically two or more cores) and preemption had to do with the way/modes the Kernel handles task, but I really have no idea about this stuff, I still use a original Motorola Flip Phone man!
Device(s): Bionic (98.72.22)
Droid X (4.5.621 root)
Carrier: vzw
Thanks: 885
Thanked 938 Times in 667 Posts
Quote:
Originally Posted by dautley
Thanks for clearing that up as I thought it referred to Symmetric Multiprocessor System, (basically two or more cores) and preemption had to do with the way/modes the Kernel handles task, but I really have no idea about this stuff, I still use a original Motorola Flip Phone man!
Long? Yes but necessarily so for older less techie people like me to understand. I have been reading about pre-emptive for several days not sure of the exact meaning and you explained it clearly. Thank you very much for your excellent and thorough reply.
Lew
Dautley can clarify if I'm wrong but QA quality assurance is still a stage where they are looking for bugs and working them out, staging would be one step closer to an actual full scale release to customers.
Quote:
"Normally before deploying an updated version of software to the production environment, the update has been tested in the staging environment. The staging server will resemble the production environment where the clients can do the user acceptance testing activities. Tests on Staging server/site should be passed before deployment of system on live server, i.e. production environment."
I installed the .230 leak on my Droid Bionic phone. How do I upgrade to the new .244 build? I'm aware I may need to roll back to GB to do this, but I wasn't quite sure how to do that. The .230 build is very, very buggy and has significant lag. Not as bad as GB, but a lot more lag than what ICS should typically have.
@dave1812 - Google Chrome for Android does not support Adobe Flash at all.
I installed the .230 leak on my Droid Bionic phone. How do I upgrade to the new .244 build? I'm aware I may need to roll back to GB to do this, but I wasn't quite sure how to do that. The .230 build is very, very buggy and has significant lag. Not as bad as GB, but a lot more lag than what ICS should typically have.
@dave1812 - Google Chrome for Android does not support Adobe Flash at all.
/facepalm. Way to state the obvious, sport. FYI: Chrome sucks, and Flash works with several browsers such as Dolphin 8.5.1. sigh...
BUMP! How do I get my Droid Bionic updated from the .230 build to the .244 build? If I need to go back to Gingerbread to do it then that's fine. I just need to know the easiest and quickest way to get the .244 build on my phone.
Device(s): Droid Bionic (was rooted but no longer thanks to JB); Asus Transformer TF300T
Carrier: Not Provided
Thanks: 40
Thanked 68 Times in 49 Posts
Quote:
Originally Posted by techguy378
BUMP! How do I get my Droid Bionic updated from the .230 build to the .244 build? If I need to go back to Gingerbread to do it then that's fine. I just need to know the easiest and quickest way to get the .244 build on my phone.
You do not want to go past 232 on ICS. Anything higher than 232 and you can not go back to GB and the work around to get the OTA update is rather complicated from what I have seen some talk about.
BUMP! How do I get my Droid Bionic updated from the .230 build to the .244 build? If I need to go back to Gingerbread to do it then that's fine. I just need to know the easiest and quickest way to get the .244 build on my phone.
This thread should have what you need. I would suggest reading through it completely and NOT going beyond 6.7.232. Builds beyond that one have a different level of security and you can't go back to GB. I have been running .232 since it came out and it is a decent build.
If there is something in the process you don't understand, let me know.
BUMP! How do I get my Droid Bionic updated from the .230 build to the .244 build? If I need to go back to Gingerbread to do it then that's fine. I just need to know the easiest and quickest way to get the .244 build on my phone.
HOB is much easier to install/use than it use to be. Just read everything and don't skip any steps, know there is a chance (a very small chance) something in the final OTA could cause this method to fail and if you flash higher than .232 you are off of Gingerbread forever. If you run into problems Samuri is usually quick to offer support, but if you don't follow directions, don't have the asked for logs on hand, or don't do exactly what he says do, just be prepared to have your ego bruised a little bit in the process.
If .244 turns out to be soak, I'll be glad to post it and it can be flashed from your SD card with stock recovery from 100% stock .905 (root should be okay but no custom recovery)
But it would be irresponsible to post it until then.
Samuri is a good guy, made an amazing update program but may be a bit harsh sometimes. However, he did CLEARLY explain what to do & not skip any steps. I appreciate his work
Device(s): HTC Droid Eris rooted and running Xtrasense. Possibly moving over to KaosGingerbread.
Carrier: Not Provided
Thanks: 19
Thanked 13 Times in 11 Posts
OK, so I'm missing something here. I found the post the other night on what I needed to download and so forth in order to do ICS. Now I can't find the thread. Could someone point me in the right direction please? I would much rather ask my questions on that thread than post them in the wrong one and have them be off topic. Thanks!!!
OK, so I'm missing something here. I found the post the other night on what I needed to download and so forth in order to do ICS. Now I can't find the thread. Could someone point me in the right direction please? I would much rather ask my questions on that thread than post them in the wrong one and have them be off topic. Thanks!!!
If anyone does this be sure to read everything in the HOB OP twice, there are risks involved and you will never be able to go back to .905 so for now you will be off the official upgrade path as .244 isn't official yet.
When the Motorola Droid Bionic was first announced at CES 2011, it featured a 4.3-inch qHD display, NVIDIA Tegra 2 dual-core processor clocked at 1GHz, and support for Verizon's 4G LTE high-speed network. After the handset was delayed, Motorola... Read More