Development [ROM][13.0][hanoip] PixelExperience [AOSP][G60/G40F]
- Thread starter Raghu varma
- Start date
Or maybe the car expects certain devices. Maybe it's just not compatible. It would be interesting to test with an actual Pixel device.
View attachment 5726823Last time his aosp13 did the same, I thought it was caused by its bluetooth failure, it seems that his ROM itself does not support Android
not just the rom itself it's like the android auto feature disappeared after i updated the car entertainment system and when i downgraded it android auto came back i would have to leave the rom in order to use android auto
Unfortunately I've got no car to test this with... So I can't really confirm that.
I will try los20 once and if that doesn't work I will go back to the official European ROM
Oh... This might be country related.... Mine is showing up perfectly fine. But unfortunately I can't really test if it's actually working or not.
This is so stupid.... Have you tried changing the country to something else?
pe? I'm already on los and it doesn't exist on aosp13 and pe13 but it doesn't work
I'm already downloading the original ROM because the firmware of the previous 2135-2 is invalid. I want to try to use the 2135-1. I don't know what is the difference between them. Can they be universal?
Unfortunately, I can't read Chinese. So I have no idea what does this screenshot say.
About xt2135-1 vs xt2135-2, they're for different markets. One is Single SIM, the other one is Dual SIM. The builds are not universal for as far as I know. And I never tried to flash it like this. But...I guess you could try. I'm not sure the reception will work.... You can try this only if you're absolutely certain you know what you're doing.
In my opinion, the problem is not the ROM. It's probably the country.
For side by side comparison, you can try to take a look here.
大约 18 年谷歌改变了他们的规则，系统必须带有谷歌套件和 Android auto 相关软件才能运行 Android auto 这个错误代码指出 ROM 不能使用 Android auto，但是 aosp13 和 PE13 虽然带有 Android auto 和 Google 套件，但是他们似乎在某个地方有一个错误，阻止了 Android 自动被激活
In about 18 years Google changed their rules, the system must come with Google suite and Android auto related software to run Android auto This error code states that the ROM cannot use Android auto, however aosp13 and PE13 although with Android auto and Google suite , but they seem to have a bug somewhere that prevents Android auto from being activated
Of course, but I flashed back to pe13 for the last test. If it doesn't work, flash back to the official website immediately.
Well, if it works with the official ROM, but doesn't work with this one...then it could be an issue with this ROM. Maybe someone else can test that too.
) I'm sorry. Hope I didn't wake you up. We live in different parts of the world, so it wasn't that late over here. But I hope you're ok, and keep seeing the good in people. By the way, you know I don't ask for ETAs and stuff. Cause I know how it is when others are doing it.
But I am only curious, did you have the time to check PE sources recently? Do they have any news on the potential Google Pay/Wallet issue we're seeing with this ROM (and probably others, too)? If so, and if there are any relevant commits to fix this, would it be too much to ask if you could maybe update this ROM, as well, so we can be able to use contactless payments? If there's no relevant change for this, then never mind.
Same for Android Auto. There was someone who tried to use it and there were some issues with that. Not sure if the issue is on Google's side...or the ROM's side. But you know, just in case there's something about it.
Thank you very much! And...just steer away of drama, bro. There's no point. It doesn't help anyone. People who care about this, about your work, don't really care about all the drama.
We all have our own share of drama in our lives. And we're not coming here to get some more. We're coming here to find people who love tech, who love Android, and gadgets, and customisations. It's just sad that people find it so hard to put away their differences and instead of going against each other, work together.
Anyway...this is just my opinion. And I might be one of the few to think like this. But I choose to see the good in my life. So...keep up the good work.
Last edited:
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
2
Do you have an SD Card? If so, it would be a lot easier to do it.
If not, you'll have to push the ROM onto the internal memory (or sideload).
Here's the instructions. I'll try to clarify where needed.
Guide for the rom which has Google apps:
----------------------------------------
1. connect phone to computer
2. enable developer options & usb debugging
3. Open command prompt in platform tools latest. ( Don't use minimal adb tools )
It refers to this. You need to download the zip for your platform, extract and place it somewhere on your computer. Let's say it's on your C:\ drive if you're using Windows.
So it will be C:\platform_tools\adb.exe for example.
Also, don't use Minimal Adb. It's a software.
Copy-paste ROM.zip and TWRP.img to the platform tools folder.
To open a cmd prompt inside the platform_tools folder, you just navigate to that folder using File Explorer, and in the path bar (up top where you can see c:/platform_tools), type "cmd" and press Enter.
This should open a command prompt window with the destination already set to your folder.
4. Type adb devices
In that window, you need to type: "adb devices"
This should return your serial number if it's connected properly.
5. Type adb reboot bootloader
This will reboot the device into bootloader mode. You can achieve the exact same thing by booting the device with Volume Down and Power button pressed together.
6. Check your phone connected and triggered in fastboot mode or not using ( type fastboot devices )
To make sure the device is connected in fastboot mode as well, in the command prompt window, type: "fastboot devices"
This should, once again, return your device.
7. Download TWRP to flash my builds
8. type "fastboot -w" -> inside the cmd prompt window
9. type "fastboot erase userdata" -> inside the cmd prompt window
10. type "fastboot boot twrp-name.img" -> inside the cmd prompt window. This will temporarily boot you into TWRP recovery so you can browse your ROM and flash it..
You need to rename the TWRP.img file to "twrp-name.img" if you're planning to use the command above as it is. If not, you can just rename it to "twrp.img" and use command:
"fastboot boot twrp.img"
11. push ROM.zip to internal storage via using command prompt by typing (adb push ROM.zip /sdcard)
or copy paste to internal storage if it is accessible from file explorer on your computer.
In order for this to work, I think TWRP needs to be in adb mode. Once booted into TWRP check the Advanced section. I think the ootion was somewhere in there.
This is about using command "adb push ROM.zip /sdcard" from Cmd Prompt (again, you'll have to rename the ROM zip file to match the command or change to command to match the filename). This is just to copy the ROM to the device.
Unfortunately, I couldn't get this part to work. The path is different. I can't figure out what would be the right "sdcard" address in this case, but it doesn't work as it is.
So, here you'll have to improvise.
Either you try to copy-paste the file onto your internal memory, from File Explorer or as I said above, use an sdcard. It is A LOT easier with an sd card.
Alternatively, you can use "adb sideload ROM.zip".
12. flash ROM.zip ( by default skip digest check will be enabled so don't untick & don't tick anything extra )
If you used the adb sideload command above, you don't need this step anymore. If you didn't, and you just copied the file onto your device, this is the part where you need to browse through TWRP to get to it, and then flash it.
13. swipe to flash -> again, refers to flashing from TWRP
14. reboot system -> this is self explanatory.
So, looks like the biggest challenge is getting the ROM onto the device. And, once again, my recommandation would be to just use an external SD Card for this.
Then, all you have to do is:
1. erase and wipe userdata with commands:
"fastboot -w"
and
"fasbtoot erase userdata"
2. boot into TWRP
3. browse for the ROM.zip file
4. flash it.
5. reboot.
The thing is that, these installation steps assume that you already know what a Cmd Prompt is, how to open one in a specific location, what is platform_tools and how to get it, how to set PATH for it, in case you need to, and all that. These are all unrelated things for the ROM itself. They're just setup parts. But they need to be done. Most people already know that, so...that's why instructions like these don't go into too many details. They don't have to, cause it's unrelated to the ROM.2Changelog - Tue Jan 10 07:05:35 UTC 2023
============================
• Based on android-13.0.0_23
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!21
I haven't tested them. Since you posted here, you can try the PixelExperience ROM.1
For as far as I know, the ghost touch issue is a hardware issue, so it's not gonna be fixed with a software patch.
However, I don't have it. Never had it. But it is a known issue indeed. -
11
PixelExperience for Moto G60 & G40
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our 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 13
Whats working?
Wi-Fi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
NFC
Fingerprint
FM radio
Face unlock
Sound
vibration
Bugs
Double tap to wake
NOTE - DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Installation process
Click Here for Installation process
Credits
* PixelExperience Team for rom source
* Motorola for kernel source
- Android OS version: 13.0
- Security patch level: 2022-11
- Build author: Raghu varma
- Kernel source code : android_kernel_motorola_sm6150
- Source code: https://github.com/PixelExperience
6Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Fri Sep 30 04:15:01 UTC 2022
============================
• Initial Android 13 PixelExperience build
• Based on android-13.0.0_r4
• Improved system stability
• User interface enhancements
• Google security patch 2022-09
• Selinux enforced
• Vendor built from Source
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!4Okay I flashed this rom on my G40F, and I can already see some new animations and some minor changes.
Changes I noticed soo far:
> Face Unlock is added and work flawlessly (Very quick)
> WiFi calling works, tested that!
> Cool new animations when you get notification and the screen wakes up!
> New LTE+ icon when you use 4G data
> Seems like the stable android 13 (unlike the previous one which was BETA)
Everything seems to work flawlessly, no bug/issues found yet!3Hello Raghu, the pixelexperience team already has a stable version of android 13 on some devices.
Will you update the Moto g60?
Android 13 Stable21) Does Google Pay work on this rom if my phone isn't rooted?
Hi there thanks for stopping by.... I had the same confusion before installing on my phone but thanks to all the people here I gained enough knowledge.....
Okay so as per your question I would like to explain few stuffs
Okay so as I researched there's something called SAFETY NET on mobile phone which basically tells if your mobile is encrypted and secure and all banking apps and contactless payment stuff depend on it.... so PIXEL EXPERIENCE ROM doesn't break SAFETY NET and as I installed this ROM I am able to use GPAY , PHONEPAY and everything else .... As for contactless payments you don't need to worry about all those as you don't have NFC..... So yeah there's that.....
All this if your phone is non rooted .... If it is rooted maybe it breaks everything but even then you can use MAGISK to hide your root and then use banking apps the way they are used to without any problem.......
So yes all banking apps will work on your phone after installing this ROM.....
NOTE : Not all Custom ROMS protects the SAFETY NET from breaking .... This PIXEL ROM doesn't break it but there are tons of ROM that breaks it . So always research before installing a rom .... HAVE FUN INSTALLING THIS ROM ..... Please drop a message if you face any problem at any step
