766 pagesV  1 2 3 4 5 6 > »  
 
REPLY
> Development and porting of GSI firmware
bullik01
Message#1
11.03.18, 18:51
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

Development and porting of GSI firmware

Supported Devices
Important!
Description
What is Project Treble?

Project Treble shares low-level drivers and the rest of the operating system so that manufacturers and third-party developers can release updates faster and easier. For devices with Android 8.x Oreo "out of the box" support for Treble is a must, and for older smartphones and tablets the option is available.
Instructions
Firmware
Android 10.x.x
Android 9.x.x
Android 8.x.x
Problem solving
Useful
Embellishments

Topics Curatorrozetkin, for updating and updating caps contactQMS


K




Post has been editedrozetkin - Today, 00:47
Reason for editing: Android q beta 2
Displax
Message#2
18.10.17, 22:30
Absolute
*********
[offline]

Group: Honorary Gameday
Messages 17054
Check in: 18.04.14
Xiaomi Mi A1 4/64

Reputation:-  5005  +

About "A / B" partition structure and "seamless" updates
Or the answer to the question: "What is wrong with my device? Why is it not like everyone else?"


Let's start. You've probably heard that some devices use some kind of outlandish A / B partition structure. It differs from the structure in most Android devices.
On it, updates are installed in some strange and unusual way, right when the system is running (O_o). Inside the OTA images is a different, unreadable structure. The installation of TWRP is accompanied by some, not previously encountered, difficulties, additional manipulations and is significantly different from everything that "I" have seen before. Everyone is talking about some letters "A", "B", "B", slots, two and systems, and other, incomprehensible "me" things.Well, let's try to figure it all out.


Начнем с общих вопросов: download


Q: Well, who invented all this? Damned manufacturers simple geeks complicate life?
A:New structure "A / B sections"developed directly by Google as part of the global changes in the architecture of Android. It is successfully used in Google Pixel smartphones of the first and second generations, Essential Phone and various other devices. In the future, more and more devices from third-party manufacturers will use it. this is not, on the contrary, many new opportunities are opening up.

Q: So what is the A / B partition structure?
A:Speaking quite simply - inside your device there are two at once (and depending on the implementation and more), independent among themselves, systems. Something likeMultiROM(if you heard about this), only with a much more thoughtful implementation at a lower level. If you are interested in specific information explaining all aspects, please continue reading.


Section table on the example of Google Pixel:
In order to visually display the theory outlined above, and see the differences compared to other devices, let’s look at the Google Pixel table of sections.
If you are not familiar with the structure of partitions in Linux-like systems, and Android in particular, I advise you to search for information about this in Google, since it is complete.

We are interested in specific sections that exist in two copies for clarity and demonstration.
So (we open the code completely):
/ dev / block / bootdevice / by-name / aboot_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / apdp_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / bootlocker_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / cmnlib32_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / cmnlib64_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / devcfg_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / hosd_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / hyp_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / keymaster_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / msadp_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / pmic_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / rpm_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / tz_a # Partitions of the first bootloader (Slot "a")
/ dev / block / bootdevice / by-name / xbl_a # Partitions of the first bootloader (Slot "a")

/ dev / block / bootdevice / by-name / aboot_b # Partitions of the second bootloader (Slot "b")
/ dev / block / bootdevice / by-name / apdp_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / bootlocker_b # Partitions of the second bootloader (Slot "b")
/ dev / block / bootdevice / by-name / cmnlib32_b # Partitions of the second bootloader (Slot "b")
/ dev / block / bootdevice / by-name / cmnlib64_b # Sections of the second bootloader (Slot "b")
/ dev / block / bootdevice / by-name / devcfg_b # Sections of the second bootloader (Slot "b")
/ dev / block / bootdevice / by-name / hosd_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / hyp_b # Partitions of the second bootloader (Slot "b")
/ dev / block / bootdevice / by-name / keymaster_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / msadp_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / pmic_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / rpm_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / tz_b # Second bootloader partitions (Slot "b")
/ dev / block / bootdevice / by-name / xbl_b # Second bootloader partitions (Slot "b")

/ dev / block / bootdevice / by-name / modem_a # Section of the first modem / radio module (Slot "a")
/ dev / block / bootdevice / by-name / modem_b # Second modem / radio section (slot "b")

/ dev / block / bootdevice / by-name / boot_a # The first kernel partition (Slot "a")
/ dev / block / bootdevice / by-name / boot_b # Section of the second kernel (Slot "b")

/ dev / block / bootdevice / by-name / vendor_a # First proprietary partition (Slot "a")
/ dev / block / bootdevice / by-name / vendor_b # Second proprietary partition (Slot b)

/ dev / block / bootdevice / by-name / system_a # First system partition (Slot "a")
/ dev / block / bootdevice / by-name / system_b # Second system partition (Slot "b")
As can be seen from the excerpt above, there are two, independent among themselves, slots, namely “partition groups”, which contain the main,upgradeable componentsfirmware.

The two slots presented consist of:
Bootloader (loader) - 28 partitions (14 for each slot).
Radio / Modem (radio module) - 2 sections (one per slot).
Boot (core) - 2 sections (one per slot).
Vendor (drivers) - 2 sections (one per slot).
System (system) - 2 sections (one per slot).

The remaining sections, not listed in the table, are presented in one copy as superfluous as they are divided.
note user storage section (userdata) always alone ! That is why You can not simultaneously use two completely different firmware. Perhaps the simultaneous use of the same type of firmware.


The principal differences compared with other devices:
With duplication of sections and, structure as a whole, understood. However, you may have noticed (if you looked through the full partition table) the absence of the “/ recovery” and “/ cache” sections familiar in any device. Yes, they really do not.

Q: Stop. But if there is no partition for Recovery, and Recovery itself is (He is, right?), Where is he located?
A: The recovery system (Recovery) is included in the kernel image (boot). Therefore, the presence, absence and type of installed recovery directly depend on the system kernel. Switching to it (Recovery), as before, is performed by a special flag in the "/ misc" section.
This is precisely the problem with the TWRP installation - somehow it needs to be thrust into the core. Therefore, TWRP is first temporarily loaded (there is no place to install it), and then from the TWRP, with a special script, the kernel is unpacked and TWRP is sewn into it. The same scheme of "repacking the kernel on the fly" is used when receiving "systemless" root-rights through SuperSU and Magisk.

Q: Well, what happened to the "/ cache" partition?
A: In familiar devices, it is necessary only for storing OTA updates and system logs of Recovery, in this case, due to the use of the new scheme of these updates (see below), the section simply became “not needed”. That's from him and got rid of.

Q: That's all well and good, but surely this partitioning option uses a lot more flash drive volume?
A: By no means. Of course, there is a difference in favor of the increase, but it is not as big as it may seem at first glance. In view of the refusal of the above sections and the reduction of the system partition, the difference is almost leveled. Visual illustration of markup and memory consumption:
Screenshot
Attached Image

Manual slot switching:
Naturally, besides the slots themselves, there must be a way to manually interact with them. And he is. To manually switch the current active slot, you need to use the fastboot utility. Commands:
fastboot set_active a
fastboot set_active b
You can also switch to another slot in the corresponding TWRP item (Reboot ->Slot A / Slot B).


Results and regulations:
1. Between the slots, both the system and the user can switch.
2. Initially (from the factory) the slots are completely identical with each other. Differences appear after applying any OTA system updates.
3. Slots are isolated between themselves. The state and integrity of one slot does not affect the other. Except for the use of OTA updates. (see below).


"Seamless" update system:
So, the sections and slots are sorted out. But what about the updates, surely they were also affected by the change, in view of the above?
Yes, OTA updates on devices with an A / B structure are completely different from what we can see on other devices.

Results and regulations:
1. All OTA updates are installed in an inactive, opposite slot. I mean - only one slot is updated.
2. All OTA updates are installed in the background with a working system, without rebooting the device.
3. All OTA updates are installed in two steps: "Step 1" - Download the update. "Step 2" - Background application of the update in an inactive, opposite slot.
4. After installing the OTA update, when the device is rebooted, it will automatically be loaded into the updated slot (previously inactive).

Android 8.0+ - broadcast updates:
Starting with the version of Android 8.0, it is possible (but not necessary) to partially implement the broadcast of updates with their simultaneous use (direct recording).
This means that updates do not need to be preloaded, but are applied on the fly.
At the moment, this technology is not used anywhere, and its working implementation is expected with the release of Android 9.0.

Post has been editedDisplax - 09.10.18, 01:23
andrwgldmn
Message#3
11.03.18, 19:03
I will see you in hell ...
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 4120
Check in: 14.10.14
Apple iPhone SE

Reputation:-  937  +

* YTrildA,
link please?
* bullik01,
add Xiaomi Mi5 to the list


--------------------
Forever true
Forever black
666
bullik01
Message#4
11.03.18, 19:08
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* YTrildA,I am going to soon add it to Russian
* rocker123,add now


--------------------
David_Black
Message#5
11.03.18, 19:47
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 4890
Check in: 03.12.13
Sony Xperia XA1 Ultra

Reputation:-  1140  +

bullik01 @ 03/11/18, 19:51*
We write the command:

And nothing shows vasche silence


--------------------
Windows 10 1809 (17763.437)
Linux Mint 19.1 Tessa (64-bit)
crDroidAndroid-9.0
bullik01
Message#6
11.03.18, 19:49
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* David_76,Updated the cap. ;)


--------------------
David_Black
Message#7
11.03.18, 20:03
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 4890
Check in: 03.12.13
Sony Xperia XA1 Ultra

Reputation:-  1140  +

* bullik01,
And what is there ...!?
Attached Image
Does this topic not roll what?


--------------------
Windows 10 1809 (17763.437)
Linux Mint 19.1 Tessa (64-bit)
crDroidAndroid-9.0
powar19
Message#8
11.03.18, 20:04
Chef
*********
[offline]

Group: Curators
Messages 3288
Check in: 18.08.13
Xiaomi Mi A2 4/64

Reputation:-  1000  +

Add Xiaomi Redmi Note 4X to the list of supported devices)


--------------------
bullik01
Message#9
11.03.18, 20:05
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* David_76,it means there is no Project Treble support in your firmware ... :(
* powar19,now add :)


--------------------
LLITOPMuk
Message#10
11.03.18, 20:11
Coward, stupid, experienced.
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 914
Check in: 03.01.11
Asus ZenFone 5 ZE620KL

Reputation:-  58  +

bullik01 @ 03/11/18, 21:05*
David_76, then in your firmware there is no support for Project Treble ..

This is not the point. This check only works on the 8th android.
bullik01
Message#11
11.03.18, 20:13
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* LLITOPMuk,He has a device on the 8 android. Not every firmware has Project Treble support (it has been implemented in few places so far ...)

While slowly adding to the list of supported devices in the header ...


--------------------
LLITOPMuk
Message#12
11.03.18, 20:14
Coward, stupid, experienced.
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 914
Check in: 03.01.11
Asus ZenFone 5 ZE620KL

Reputation:-  58  +

bullik01 @ 03/11/18, 21:13*
Not every firmware supports Project Treble

then the meaning of this test is not clear. If interested manufacturer added or not option - it is possible. And so soon the themes will multiply on XDA for devices.

Posted 11/03/2018 at 20:15:

bullik01 @ 03/11/18, 21:13*
While slowly adding to the list of supported devices in the header ...

You can make a spoiler by manufacturers, then it will be easier to navigate.
bullik01
Message#13
11.03.18, 20:17
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* LLITOPMuk,Well, it was added to check if there is support for this project in the firmware or not. It is possible to switch to another "Required" from such firmware, etc.
* David_76,well ... I see now ... Project Treble is supported only on OREO firmware ..

Post has been editedbullik01 - 02.09.18, 13:49


--------------------
David_Black
Message#14
11.03.18, 20:19
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 4890
Check in: 03.12.13
Sony Xperia XA1 Ultra

Reputation:-  1140  +

* LLITOPMuk,
Well, of course, well, then I will restore my backup 8.1 now and what will it give meProject treble?
Nothing not to understand the bourgeois : D


--------------------
Windows 10 1809 (17763.437)
Linux Mint 19.1 Tessa (64-bit)
crDroidAndroid-9.0
bullik01
Message#15
11.03.18, 20:21
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* DenZsavagemessiahzine.com,I took information from there and took it. There is nothing special except news ...
* David_76,Well, you can check: D
In general, it will be easier to get updates and switch to different firmware ...

Post has been editedbullik01 - 11.03.18, 20:23


--------------------
LLITOPMuk
Message#16
11.03.18, 20:23
Coward, stupid, experienced.
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 914
Check in: 03.01.11
Asus ZenFone 5 ZE620KL

Reputation:-  58  +

David_76 @ 03.11.18, 21:19*
Now your backup is 8.1 and that will give it to me Project Treble

yet nothing will. This project serves to get updates as soon as possible (android).
the Android framework will be separated from the customized part of the third-party manufacturer
DenZsavagemessiahzine.com
Message#17
11.03.18, 20:23
Do good deeds!
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1739
Check in: 22.09.08
T-Mobile Touch HD2

Reputation:-  233  +

David_76 @ 03.11.18, 20:19*
and what will Project Treble give me?
On Oreo, only a few vendors have released firmware with PT support.
It was said earlier that if out of the box the device is sold with Oreo, then yes, it should support PT, but it is not.


--------------------
Device: Samsung Galaxy SIII; ANDROID RR-mod 14.1
Tablet: SmartQ X7 ANDROID CM 10.1 (4.2.2) compile CM, compiled DT and zip
My selection of books:Android Library 2019
David_Black
Message#18
11.03.18, 20:24
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 4890
Check in: 03.12.13
Sony Xperia XA1 Ultra

Reputation:-  1140  +

bullik01 @ 03/11/18, 21:21*
can be checked

And then what ...!? : girl_prepare_fish:
bullik01 @ 03/11/18, 21:21*
it will be easier to get updates and upgrade to different firmware ...
I have stock 5.1.1 last support.

Post has been editedDavid_76 - 11.03.18, 20:25


--------------------
Windows 10 1809 (17763.437)
Linux Mint 19.1 Tessa (64-bit)
crDroidAndroid-9.0
bullik01
Message#19
11.03.18, 20:24
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* David_76,I edited the post there. Look again;)

Poll results
Poll # 1 from 7/24/2018 to 02.09.2018
Attached Image




Post has been editedbullik01 - 02.09.18, 14:04


--------------------
LLITOPMuk
Message#20
11.03.18, 20:24
Coward, stupid, experienced.
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 914
Check in: 03.01.11
Asus ZenFone 5 ZE620KL

Reputation:-  58  +

DenZsavagemessiahzine.com @ 11.03.18, 21:23 *
should support PT

I must say about it every noname, DNS, homtom and others)))
bullik01
Message#21
11.03.18, 20:28
Teamsavagemessiahzine.com
*********
[offline]

Group: Curators
Messages 6838
Check in: 31.07.12
Oneplus 5T 8/128

Reputation:-  2247  +

* LLITOPMuk,Well, at least they will have updates ... And then they will release the device and forget about its existence in 3 months ...


--------------------

766 pagesV  1 2 3 4 5 6 > » 


 mobile version    Now: 02.05.19, 07:41