459: Chapter 459 Android System Crash: Rice Test

At first, it was just abroad, and only a few minor posts; after all, large companies still need to go through approval processes!

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

By 11 PM, domestic developer forums were in chaos.

Guo Feng, an independent video player developer who was 'generating electricity for love,' started cursing directly on the forum.

"Initially, I saw the announcement and thought Google had finally caught up with the schedule, so I was very excited to pull the project onto the 4.4.3 emulator. But as soon as I entered full-screen playback, I was stunned."

"The SurfaceView drawing area was directly misaligned. On an 18:9 screen, the video image only showed the middle two-thirds, the top and bottom were cut off abruptly, and the progress bar was thrown directly outside the screen."

"I thought it was because I hadn't added settings, so I added resizeableActivity according to Google's documentation, but that turned out to be even more ridiculous."

"I want to ask, did Google's engineers shove their brains into a septic tank? When switching to Full-screen Display, it forces hard decoding, causing a black screen, and even the system status bar freezes."

"If this were accidental, I would let it slide. But after I flipped 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 touched."

"The measurement logic for the display area wasn't changed, the window management layout rules weren't changed, and even the hiding logic for virtual buttons was forcibly shielded; there were no interfaces reserved for Full-screen Display gestures at all."

"This is what you call native support? This is just changing the resolution and trying to fool ghosts."

Not long after Guo Feng's post was sent, many developers appeared in the comment section, some of whom felt the developer's level was insufficient and hadn't fully grasped Google's adaptation rules.

After all, new technology always requires learning, but more and more developers came to the forum to complain.

"We make tile games, and the touch coordinates for the virtual button area are completely offset in Full-screen Display mode."

"When we tested, we clicked the attack button in the bottom right corner, and the system judged it to be in the middle of the screen, leaving the character standing there getting beaten continuously."

"We spent months on planning, and now it's all wasted?"

"You can't believe a word Google says!"

"The stuff made in three months having this effect is already pretty good! After all, it takes time for our United States masters to reform the resolution!"

"I finally see it clearly; Google is just using all developers as testers!"

"Release first, let us find the bugs, then fix it in the next update—it's the same old routine."

"It shouldn't be worse than this, after all, they paid you this time!"

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

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

"All developer forums are in chaos!"

"Almost all developers are reporting serious bugs in the Full-screen Display adaptation, and our official developer community has been flooded with complaint posts."

At first, Dave Burke was still a bit stubborn: "What are you panicking about? They definitely didn't adapt according to the official documentation. Ask technical support to send out a specification guide and emphasize the configuration file writing again."

"Then we will start fixing bugs tomorrow!"

Dave Burke certainly knew how garbage this system, rushed out from storage, was, but the external announcement had to be strong...

He could not admit any problems, otherwise they would face a huge crisis.

"It's not that, sir." The assistant's voice became more urgent. "Now, because some people are trying to adapt, the probability of system crashes has risen from 20% to 60%."

"Most people crash directly when testing!"

"The problem is more serious than we imagined!"

After speaking, he took out some materials he had organized.

Dave Burke instantly sobered up. He knew his own affairs, and he knew how big the problems were inside.

But he didn't expect it to crash so severely!

This was no longer a system with bugs; this was a system framework built on top of bugs.

"Notify the core team, meeting immediately."

Dave Burke immediately started to act.

"Also, copy all the public architecture that Transsion open-sourced. As long as it can make our Full-screen Display system stable, that's fine!"

"Burke, we have already copied everything we could copy, and we even copied some things we shouldn't have. So now we must change it from the beginning!"

Dave Burke, who had just arrived at the office, finally knew exactly where the problems were.

Including but not limited to games, social networking, input methods... in short, all kinds of apps had problems.

All manufacturers were cursing them because everyone had to pay the price for their problems!

Meanwhile, when the crisis broke out, Hong Feng of the Dami Company MIUI R&D department had originally considered layoffs, after all, the current MIUI didn't need so many developers!

But the success of Android's Full-screen Display gave them huge support, and Lei Jun even asked them to complete the development work within two months!

Although the time was a bit tight, as a 'senior trash' handler, Hong Feng patted his chest and guaranteed in Lei Jun's office:

"General Manager Lei, don't worry."

"Although I haven't seen Google's original package, I believe the system produced by Google and Microsoft definitely won't be bad..."

"Of course, this is something rushed out in three months after all, so there might be a bit more debugging to do."

"But don't worry, I will definitely fix it at the first opportunity!"

As for why Hong Feng dared to guarantee it, it was because this time Google gave a lot of authority, allowing them to change things at will without needing approval.

However, Google would have sharing rights for the modified technology, used for maintaining the stability of Android.

This was a double-edged sword, but it was good news for Xiaomi; after all, they were all their own people, and they could use these things for free anyway, and now the situation was even better...

Lei Jun was very happy at the time; after all, his co-founder hadn't embarrassed him!

Now Transsion was nothing to fear!

So he directly asked the administrative team to hold a send-off banquet for everyone, and promised to give everyone a bonus after the adaptation was completed.

Therefore, after eating, all employees 'spontaneously' chose to work overtime.

Around 10 PM, they finished pulling the Android 4.4.3 source code and began to port core modules like MIUI's desktop notifications and settings.

At that time, all developers felt that Google had already done the hardest part of the underlying layer, and they were just doing what they did before—putting on a skin, which was easy.

But at 11 PM, the first 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 the first time MIUI lit up the Full-screen Display.

The publicity department, which was cooperating on the side, had already adjusted the time on the camera to 12:30, ready to record the exclusive scene of Xiaomi system staff working overtime to develop it for everyone, so they could promote it well later.

As a result, the Xiaomi LOGO on startup gave everyone a head-on blow.