Shockingly, a counterfeit factory has produced a 3-nanometer chip.

Chapter 459 Android System Crash: Rice Test

At first, it was only overseas, and just a few small posts, since large companies still need to go through approval processes!

But within a few hours, the fire had completely ignited.

By 11 p.m., domestic developer forums were in chaos.

Guo Feng, an independent video player developer who works out of passion, directly started cursing on the forum.

"When I saw the announcement, I thought Google had finally caught up with the progress, so I excitedly dragged the project to version 4.4.3 and ran it on the simulator. But when I entered full-screen mode, I was dumbfounded."

The SurfaceView drawing area is directly misaligned. On the 18:9 screen, only the middle two-thirds of the video is displayed, with the top and bottom ends abruptly cut off, and the progress bar is thrown off the screen.

I thought it was because I hadn't added any settings, so I added resizeableActivity according to the Google documentation, but that only made things more absurd.

I'd like to ask, have Google's engineers put their brains in a cesspool?

When switching to full-screen mode, the screen goes black due to hardware decoding, and even the system status bar freezes.

"If this is just a coincidence, then so be it."

However, after looking through the source code, I was surprised to find that Google's so-called native support was just changing the default aspect ratio from 16:9 to 18:9, and nothing else was changed.

The measurement logic for the display area has not been changed, the layout rules for window management have not been changed, and even the hiding logic for virtual buttons is forcibly blocked. There is no reserved interface for the convergence of full-screen gestures.

This is called native support; this is just changing the resolution and trying to fool people.

Shortly after Guo Feng posted his post, many developers appeared in the comments section, some of whom felt that the developers were not skilled enough and had not fully grasped Google's adaptation rules.

After all, new technologies always require learning, but more and more developers are coming to the forum to complain.

"We make texture-based games, and the touch coordinates of the virtual button area are completely offset in full-screen mode."

During our testing, when we clicked the attack button in the bottom right corner, the system automatically positioned the character in the center of the screen, causing them to stand there and continuously take damage.

"We've been planning for months, and now it's all ruined?"

"You can't trust even the punctuation marks in Google's posts!"

"For something produced in three months, this level of quality is already quite impressive! After all, even we Americans need time to improve resolution!"

"I see now, Google is using all developers as testers!"

They release it first, then tell us there are bugs and we'll find a fixed version, and they'll update next time—the same old routine.

"It shouldn't be any worse than this, after all, we gave you money this time!"

Meanwhile, in Silicon Valley, the Android team also saw these complaints.

"Mr. Dave Burke, the situation is more serious than we thought."

All the developer forums are in complete chaos!

Almost all developers are reporting serious bugs in the full-screen adaptation; our official developer community is flooded with complaint posts.

At first, Dave Burke was a bit stubborn: "What's the panic? It must be that they didn't adapt according to the official documentation. Let the technical support issue a specification guide and emphasize the way the configuration file is written."

Then we'll start fixing the bugs tomorrow!

Dave Burke was well aware of how terrible this hastily constructed warehouse system was, but the public announcement had to be forceful…

They cannot admit any problems, or they will face a huge crisis.

"No, sir." The assistant's voice became more urgent. "Now, because someone is adapting the system, the probability of it crashing has increased from 20% to 60%."

Most people experience crashes during testing!

The problem is more serious than we imagined!

After he finished speaking, he took out some materials that I had compiled.

Dave Burke instantly snapped to reality; he knew his own situation best and understood the magnitude of the problem.

But he never expected to break down so badly!

This is no longer a system with bugs; it's a system framework built on top of those bugs.

"Notify the core team to hold a meeting immediately."

Dave Burke immediately took action.

"Furthermore, we copied all the public architecture provided by Transsion, as long as it makes our full-screen system stable, that's fine!"

"Burke, we copied everything we copied, and even some things that shouldn't have been copied."

So now we have to start all over again!

Dave Burke, who had just arrived at the office, finally learned exactly which problems were at play.

This includes, but is not limited to, games, social networking, input methods... in short, all kinds of apps have problems.

All the manufacturers are criticizing them because of their problems, and everyone else has to pay the price!

At the same time, when the crisis broke out, Hong Feng, the head of the MIUI R&D department of DaMi Company, originally wanted to consider layoffs, since the current MIUI does not need so many developers!

However, the success of Android's full-screen display also brought them tremendous support, with Lei Jun even enabling them to complete the development work within two months!

Although time was a bit tight, as a "veteran" waste disposal expert, Hong Feng patted his chest and assured Lei Jun in Lei Jun's office:

"Mr. Lei, don't worry."

Google's original package—although I haven't looked at it yet—I believe that the systems developed by Google and Microsoft are definitely not bad.

Of course, this was something that was rushed out in three months, so there might be a lot of debugging involved.

Don't worry, I will fix it as soon as possible!

As for why Hong Feng dared to make such a guarantee, it's because Google granted him considerable authority this time, allowing him to make changes at will without needing approval.

However, Google must have the right to share the modified technology in order to maintain the stability of Android.

This is a double-edged sword, but it's good news for the rice (Chinese people), since they're all family and friends. They were already using these things for free, and now the situation is even better.

Lei Jun was very happy at the time, after all, his co-founder had not let him down!

Now, the ability to transmit sound is no longer a threat!

So the administrative team threw a send-off banquet for everyone, and promised to give everyone a bonus once the adaptation was complete.

So after dinner, all the employees "spontaneously" chose to work overtime.

Around 10 o'clock, we finished pulling the source code of Android 4.4.3 and started porting the core modules of MIUI, such as desktop notification settings, into it.

At the time, all the developers felt that Google had already done the hardest part of the underlying system, and they could just easily put on a skin, just like before.

However, at 11 p.m., the first version of the ported system package was officially flashed into the test machine.

Hong Feng pressed the power button, and all the developers gathered around, waiting to see what MIUI would look like when it first lit up the full screen.

The publicity department, working alongside them, had already set the camera time to 12:30 AM, ready to record this special moment of the Rice System team working late into the night to develop the system for everyone, so they could promote it effectively.

The rice logo that appeared when the machine was turned on was the first thing to shock everyone.