I was just about to post the same question. I am on the final version PE11 on my Lenovo TB-X606F and the cover will not put the tablet to sleep. Opening the cover works. Everything else works great. So yes, same issue. Hopefully someone can help.
[GSI][UNOFFICIAL][11] Pixel Experience & Pixel Experience Plus
- Thread starter ponces
- Start date
Hey - wanted to ask how you got PE11 working on the X606F. I'm getting stuck at the Google logo with bar animation underneath during the first boot. Let me know your steps if you have a moment. Thanks.
It's a meh OS. A bit laggy on my Redmi 9T 5G overall. The 3 buttons at the bottom being replaced by inconsistent 'gestures' is very annoying and not able to turn them off. Not to mention it says Android 11 but I got Android 12 instead, which none of my custom recoveries support. At least earphones work.
Overall, pretty sluggish, floaty animations and not much QoL. Can't change call volume either.
Overall, pretty sluggish, floaty animations and not much QoL. Can't change call volume either.
Running the latest A12 version. Works perfectly with oneplus N10 5G. Very smooth. Haven't seen any major issues except NFC cannot be turned on. Please keep this ROM going and up to date. Thanks!
maybe this https://github.com/phhusson/device_phh_treble/commit/9e8679d273afe29b9bed6d48cb29cc6faf59af4a
bug should be fixed in v411 builds
Thanks Seems to be fixed, any idea how to fix the aligment of the status bar? since everything ive tried in DPI settings and phhe settings only gets it better but not center
Same issue here, on a Huawei Mediapad M5 - CMR-W09. It doesn't need VNDK, and even the "slim" image is too big.
I was able to overcome this issue with a tool called parted. I increased the system partition to about 3.5 GB and flashed the system image.
How to resize partitions on an android phone using Parted
This is a step by step guide showing how to resize partitions on an android phone using Parted. This guide will come in handy if you're trying to reduce the size of a partition e.g system partition an
forum.hovatek.com
I was able to overcome this issue with a tool called parted. I increased the system partition to about 3.5 GB and flashed the system image.
How to resize partitions on an android phone using Parted
This is a step by step guide showing how to resize partitions on an android phone using Parted. This guide will come in handy if you're trying to reduce the size of a partition e.g system partition an
Unfortunately, there is no working TWRP for the CMR-W09, so using parted isn't an alternative.
Thanks, the 3.2.1-GAGUGA works - despite being unable to decrypt /data, but that isn't an issue.
Now I need to find a working parted compiled for arm64, and make sense of the 66 (!!!) partitions. I'm guessing I'll need to enlarge system_a to 3.5GB (it's 2.7GB currently), move the preas, preavs, patch_a and reserved5 up, and reduce userdata.
Code:
fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): f9f21fff-a8d4-5f0e-9746-594869aec34e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071359
Number Start (sector) End (sector) Size Code Name
1 1024 2047 512K 0700 frp
2 2048 6143 2048K 0700 persist
3 6144 16383 5120K 0700 reserved1
4 16384 17407 512K 0700 reserved6
5 17408 18431 512K 0700 vrl
6 18432 19455 512K 0700 vrl_backup
7 19456 36863 8704K 0700 modem_secure
8 36864 49151 6144K 0700 nvme
9 49152 180223 64.0M 0700 oeminfo
10 180224 245759 32.0M 0700 secure_storage
11 245760 311295 32.0M 0700 modem_om
12 311296 319487 4096K 0700 modemnvm_factory
13 319488 327679 4096K 0700 modemnvm_backup
14 327680 352255 12.0M 0700 modemnvm_img
15 352256 360447 4096K 0700 modemnvm_system
16 360448 524287 80.0M 0700 splash2
17 524288 786431 128M 0700 cache
18 786432 1048575 128M 0700 odm_a
19 1048576 1052671 2048K 0700 bootfail_info
20 1052672 1056767 2048K 0700 misc
21 1056768 1122303 32.0M 0700 reserved2
22 1122304 1130495 4096K 0700 hhee_a
23 1130496 1146879 8192K 0700 hisee_fs_a
24 1146880 1179647 16.0M 0700 dfx
25 1179648 1212415 16.0M 0700 rrecord
26 1212416 1212927 256K 0700 fw_lpm3_a
27 1212928 1220607 3840K 0700 reserved3_a
28 1220608 1228799 4096K 0700 hisee_img_a
29 1228800 1253375 12.0M 0700 fastboot_a
30 1253376 1261567 4096K 0700 vector_a
31 1261568 1265663 2048K 0700 isp_boot_a
32 1265664 1294335 14.0M 0700 isp_firmware_a
33 1294336 1318911 12.0M 0700 fw_hifi_a
34 1318912 1335295 8192K 0700 teeos_a
35 1335296 1384447 24.0M 0700 erecovery_kernel_a
36 1384448 1449983 32.0M 0700 erecovery_ramdisk_a
37 1449984 1482751 16.0M 0700 erecovery_vendor_a
38 1482752 1515519 16.0M 0700 sensorhub_a
39 1515520 1564671 24.0M 0700 kernel_a
40 1564672 1589247 12.0M 0700 eng_system_a
41 1589248 1654783 32.0M 0700 recovery_ramdisk_a
42 1654784 1687551 16.0M 0700 recovery_vendor_a
43 1687552 1716223 14.0M 0700 dts_a
44 1716224 1720319 2048K 0700 dto_a
45 1720320 1724415 2048K 0700 trustfirmware_a
46 1724416 1839103 56.0M 0700 modem_fw_a
47 1839104 1863679 12.0M 0700 eng_vendor_a
48 1863680 1916927 26.0M 0700 reserved4_a
49 1916928 1933311 8192K 0700 preload_a
50 1933312 1937407 2048K 0700 recovery_vbmeta_a
51 1937408 1941503 2048K 0700 erecovery_vbmeta_a
52 1941504 1949695 4096K 0700 vbmeta_a
53 1949696 2113535 80.0M 0700 modemnvm_update_a
54 2113536 2179071 32.0M 0700 reserved7
55 2179072 2244607 32.0M 0700 version_a
56 2244608 3850239 784M 0700 vendor_a
57 3850240 5341183 728M 0700 product_a
58 5341184 5390335 24.0M 0700 prets
59 5390336 5406719 8192K 0700 pretvs
60 5406720 5799935 192M 0700 cust_a
61 5799936 11452415 2760M 0700 system_a
62 11452416 13762559 1128M 0700 preas
63 13762560 13828095 32.0M 0700 preavs
64 13828096 14237695 200M 0700 patch_a
65 14237696 14499839 128M 0700 reserved5
66 14499840 61071359 22.2G 0700 userdataDidn't want to risk having it destroy anything. When resizing partitions, I like to have manual control and visibility of what is going to happen - and, having said that, I'll see if that works in TWRP. But no idea how it is going to resize if there is no free space - my manual approach would be to move the start of userdata up by 800MB, move reserved5, then patch_a, preavs and finally preas to make 800MB free after system_a, and then resize it. No idea if TWRP's resize system will know how to do that.
Edit: Tried it now, but it doesn't work. TWRP seems to think that system has 0MB and can be resized to 0MB only
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
25
Pixel Experience for GSI
&
Pixel Experience Plus for GSI
What is this?
Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Their mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
What is working?
Almost everything
Known issues
Same issues of Phh's AOSP
Download
Github
Telegram
Pixel Experience
Phh Treble
Translation
Help with project translation
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces
- Build author: ponces
- Source code: PixelExperience
- Device source code: device_phh_treble
- ROM developer: jhenrique09
- Contributors: Pixel Experience Team, phhusson, AndyYan and eremitein - all credits should go to them
5First pixel experience that booted on my Samsung A505GN. And damn I loved it.
thanks for the hardwork5Pixel Experience Plus 11.0 v312 released!
Changelog:
- Fix Extreme Battery Saver SELinux denials
- Sync with Phh's AOSP v312
- Sync with August sources of PE+
4Pixel Experience 11.0 v313 released!
Changelog:
- Sync with Phh's AOSP v313
- Sync with October sources of PE
4Pixel Experience 11.0 v307 released!
Changelog:
- Fix build fingerprint properties
- Use PE device name property
- Remove Styles section and securize option from Treble App
- Add offline charging sepolicy
- All changes up to Phh's AOSP v307
