Database Develop

21/09/2010 [Xperia X1][FroyoRedux-Port][CM6][Testers needed][Neopeek]

http://www.neopeek.com/en/forum/14-Android-ROMs/364-Xperia-X1FroyoRedux-PortCM6
check this neopeek testers need again....

Installing as I type! Can't wait the original kernel to get the battery related patches!

I am having a wired problem - after a while on standby, upon waking up the phone, it freezes. Clock doesn't advance and phone does not respond on buttons/slider. So I do a soft-reset after which in winmo I get a message sdcard is not formatted, do I want to format it. and indeed file system is damaged. And this happens for a second time in a row now! I havent had problems like that with other distributions, at least ones that require ext2 partition. Anyone have advice?
Sent from my Milestone using XDA App

well, i cant charge

So far, it's perfect. Two issues that need to be resolved before I use it permanently is the charging and the battery drain.
Getting really close!

So far, it's perfect. Two issues that need to be resolved before I use it permanently is the charging and the battery drain.
Getting really close!
Click to expand...
Click to collapse
Ok so far so good! BUT: Would you provide us a lil bit of more info!
Which kernel did you use? Included one (=21/8) or that from SuperFroyo??

vatoloco said:
Ok so far so good! BUT: Would you provide us a lil bit of more info!
Which kernel did you use? Included one (=21/8) or that from SuperFroyo??
Click to expand...
Click to collapse
Sorry, was in a bit of a rush
Working: Marketplace, WiFi, GPS, battery meter, sound, messaging, gmail app, browser, ( bluetooth, I think )
Not: Camera, charging, power management
Used: Only the included files, nothing more.

May anyone please test this kernel?
Test-Kernel
I am awaiting your feedback

Hey guys, my Galaxy S should arrive tomorrow.
@all Developers:
Thank you very much for the good work, keep it up
@the rest:
I wish you good luck, that you can enjoy android on your X1 as i will do it on my new phone.
Maybe i'll look back in here from time to time, to see the progress.
Best regards from germany
See ya!

report?
Total performance is smooth
My location , Wi-Fi, Market , Battery Meter , GMail, Sound, Music is working
other function. i didn't use it.
Overall performance is good, but Force Close dialog is too much show..... when i try to do anything. there's a delay (about 5~10sec?)

All of you guys should really post which kernel you are using. It will be very helpful for the developers!
I am downloading at the moment, will try the kernels and post the results
Original kernel + points about FroyoRedux:
- Charging works (I had it plugged when I launched Android, actually does increase WM battery percentage, too)
- Battery meter shows too much, but I think it will calibrate itself if I finish charging
- Speaker bug is there, headphone plug and unplug fixes that
- A bit faster than CyanogenMod6 with Tremere's kernel
- Nice theme
- Mass storage does not work (should I install a driver or something?)
- Sometimes stops responding to any other key than the top power button = home
- 3D does not work
- Sound and calling work fine, cannot adjust in-call volume (possibly due to the keys not working, but I had this problem with CM6+Trem too)
- Pretty much every app works, YOUTUBE TOO (lags a bit, but works)!
New testkernel:
- Phone reboots when first screen of android comes up
- I just replaced files, it crashed at lockscreen
- Ran a new installation, it crashed at black android system (title) -window
SuperFroyo kernel:
- Fastest one, menu scrolling is pretty nice with this kernel
- 3D does not work, Neocore crashes
- Sound works
- Youtube works, and lags less than with original kernel
- Charging does not work, battery meter shows what comes to it's mind

vatoloco said:
May anyone please test this kernel?
Test-Kernel
I am awaiting your feedback
Click to expand...
Click to collapse
Tried copy/paste of those two files straight into root of SD-card (can only guess as it's not written anywhere). Phone reboots as soon as it comes to PIN-code page. Tried to restart a couple of times but nope.
Tried the SuperFroyo-kernel as well. Much faster in comparison to kernel from tremere's build 21/8.
Else, nothing more to add other then lkoljo wrote.
Big thx!

tried this kernel
xperia-xdandroid-kernel-20100922
Sound didn't work??

I'm useing the test kernel now, and it booted up without any problems
Gonna test Battery life for 2 hours, then switch back to vm to see if it gives good result's

Did you use the test-kernel from scratch. I mean when first booting up? or did you try first included kernel then after booting up you replaced kernel? I ask this because it's just not clear for me: You say it works w/o hassle and others report that they can't even get into the Launcher or that they have a black screen. I am just confused now

I did first use Tremere's Kernel with your build, and then i just copied the test kernel start from vm and booted it up. It's fast and stable it seems, i did use Android in standby mode for one and half hour. Well i did look around in system meny and such tried calling it but no signal just vibrate wich i did turn on. Battery used in android is 20% from fully charged 100% Switch back to vm says 78% so the meter seems almost correct. Tried original charger but it didn't work, Then tried pc usb charging and it seems to work Gonna try Xdandroid's new kernel now released today. Will get back to you tomorrow
I have now tested the new Xdandroid kernel released 23/9/10 for one and half hour now, switched back to vm and guess what?
i had 100% when i started android, used it for one and a half hour and then i switched back to vm it had only used 9% battery
Thats the best result i ever had using android, so hey if only sound/ mic problem gets fixed then this would be great
Grab the new kernel from thier Xdandroid wiki

I have tested 21/09/2010 [Xperia X1][FroyoRedux-Port][CM6] with the latest kernel from xdandroid (23/9/10) and it works very well, stable and fast. And the battery is a big improvment!!
I also overclocked it to 640mhz and the UI is then superfast.
Keep up the good work

winkgw said:
I have tested 21/09/2010 [Xperia X1][FroyoRedux-Port][CM6] with the latest kernel from xdandroid (23/9/10) and it works very well, stable and fast. And the battery is a big improvment!!
I also overclocked it to 640mhz and the UI is then superfast.
Keep up the good work
Click to expand...
Click to collapse
you use zimage to?

FYI: In the next days there will be heavy updates regarding some of my builds. Fixed almost everything I could! Just trying out today some of the kernels released lately and then I think we will have a really really good CM6-Ports ready for all of you! Everything that's working in XDAndroid "Final" should then also work for us! So maybe I will call my builds "Pre-Final". Another thing that I should mention is that user ferlanero from xda-devs has today shipped over his X1 from Spain to Germany (my location). Once I receive it I will be going to try some NAND-related stuff!
X1 from user sequester will be my porting-device to test ports and latest nightlies from Cyanogen
X1 from user ferlanero will be my nand-test-device
Be prepared to get the proposed updates (see above) on this weekend. Again speical thanx to sequester and ferlanero for supporting me! This really motivates me in doing all this stuff!

Yes zimage to at lest i did

[Kernel][Request] - HTC Stock Sense kernel with GPU+ 5pt multi touch?

Would any dev or anyone who knows a bit about compiling be able to do this? I've tried some other kernels, and generally love some of the features and performance they bring, but none of them has been 100% stable for me. Stock kernel is 100% stable, but lacks the 5 point multitouch which I do use for emulators, and GPU+ which makes a noticeable difference in 3D graphics smoothness.
The closest I found was HeyItsLou's #8 (I might have the number wrong) which runs great, has the multitouch, but no GPU+ Lou's has some other good features that seem to help smoothness and battery life too.
Maybe Lou or someone could throw GPU+ into that kernel? Or just take the stock kernel and add GPU+ and multitouch? Would anyone else be interested in this?

Um what about the. 32 incredikernel?
Sent from my ADR6300 using XDA Premium App

That's what I'm running now but it will randomly peg the CPU (system panel shows Android System as maxed out) and slow the phone to a crawl, requiring a reboot. And no, I'm not running SetCPU. That is the ONLY problem I have with that kernel, but I've never had that happen on the stock kernel. I don't want to deal with the random lockups anymore.
Ziggy's kernel doesn't have the lock ups, but doesn't run as smooth either, and I notice a lot of stutters while gaming.

I don't know why that would be. I compiled it for someone a few days ago and he loves how it runs.
Sent from my ADR6300 using XDA Premium App

what is 5pt multi touch?????

jdog94 said:
what is 5pt multi touch?????
Click to expand...
Click to collapse
Just that, you are able to use five fingers (or "points") simultaneously.
From my understanding, multitouch is affected by the touch panel you have, and also the way it is flashed. There was a compatible recovery floating around a while ago, but it's no longer maintained.

Yeah not all phones support 5pt
Sent from my ADR6300 using XDA Premium App

Phydo - I've actually been running your undervolted version of Chad's kernel for the last few days. I'm still having the same issue. In Chad's thread, there were actually a few people having the exact same issue. It was thought that SetCPU was somehow to blame, but again, I don't even have that installed.
From a performance standpoint, Chad's kernel is the one I've had the best results with and keep going back to, but this issue with the CPU getting stuck at 100% load happens regularly, every 24-48 hours.

bast525 said:
Phydo - I've actually been running your undervolted version of Chad's kernel for the last few days. I'm still having the same issue. In Chad's thread, there were actually a few people having the exact same issue. It was thought that SetCPU was somehow to blame, but again, I don't even have that installed.
From a performance standpoint, Chad's kernel is the one I've had the best results with and keep going back to, but this issue with the CPU getting stuck at 100% load happens regularly, every 24-48 hours.
Click to expand...
Click to collapse
I'd be willing to bet your problem is the ProcessStats.java bug documented in Issue 9733. It is exacerbated by kernels that add extra frequencies. Some ROMs work around the issue by making the time_in_state file unreadable, but SetCPU undoes this workaround every time you open it. 24-48 hours seems about right for the time it was taking for me to run into this problem. I'm now running with an init.d script that redoes the chmod 600 every 5 minutes just in case I open SetCPU and the problem has gone away.

Aweaver33 - would this be something I could easily incorporate into my own ROM? I'm running a mostly stock ROM that I customized by adding an earlier Evo framework and taking out some stuff I didnt want. Would I be able to flash your init.d script? Or since I don't run setcpu, could you explain or point me somewhere I could figure out how to make time_in_state unreadable?
EDIT: nevermind.... aweaver you are awesome for posting that link. I will try to chmod the time_in_state file as outline in that thread and see if I can make it 48 hours without it making the cpu.
Do you know how specifically this is kernel related? I've had this issue with Chad's kernel, and the old KingKlick kernels. I have NOT had the issue on the very old Hydra kernel or any of the stock kernels. I guess its just the number of frequencies they enable? Man if chmod'ing that file is all it took to fix that bug.... you are my friggin hero dude. I've been mostly using Chad's kernel since December and love it but MAN I hated the phone locking up every two days!

bast525 said:
Do you know how specifically this is kernel related? I've had this issue with Chad's kernel, and the old KingKlick kernels. I have NOT had the issue on the very old Hydra kernel or any of the stock kernels. I guess its just the number of frequencies they enable?
Click to expand...
Click to collapse
Yeah, it's mostly just the number of frequencies they enable. Also a potential, but smaller, contributor would be governor settings that result in a more even distribution of frequencies, which would result the overall file size getting larger more quickly. I first noticed this issue when I was doing stability testing that intentially created an even distribution of frequencies and made it less than a day before triggering the bug.

Well, I'm at 36 hours of running now, so far no issues. I did open the time in state file and noted it is still updating, though the permissions were correctly changed.
My only problem now is the leaked GB roms that popped up today... I want to flash one but I REALLY want to see if after six months of dealing with this very annoying bug, if it is finally fixed. I gonna TRY to resist flashing til tomorrow.

Any way to make the change in permissions to the time in state file stick? It undoes the changes on reboot

bast525 said:
Any way to make the change in permissions to the time in state file stick? It undoes the changes on reboot
Click to expand...
Click to collapse
That's where the init.d script comes in. Put the following in a file in /etc/init.d/ and set permissions to 755:
Code:
#!/system/bin/sh
while [ 1 ]; do
chmod 400 /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
sleep 300
done

If there is no /etc/init.d folder, and I create and throw that file in there will it work?
EDIT: nevermind... tried it, didn't work. Created the folder, put the file I'm there, rebooted. Let phone sit five mins, looked at permissions for time in state file, they were still at default. Does it need to have an extension? I just named it "fix".

Sorry, it looks like the /etc/init.d/ directory is not standard Android. The following is the last line in my /bootcomplete.inc.rc file, which looks like what enables running the scripts in the /etc/init.d directory:
Code:
/system/xbin/busybox run-parts /system/etc/init.d
I'm not sure if that line was automatically added when I installed busybox, or if something else put it there.

It's cool, I found an alternate method. There's a very small app in the market simply called "Autostart", to use it you create a script, name it autostart.sh, drop it in a folder you create in /data/, and it runs at boot same as if it were in init.d. I took your script and modified it a bit to make it not repeat every 300 seconds. I don't run SetCPU so I only need it to run once at start up.
I still haven't let the phone run for 48 hours straight to verify this fixed it, but still man thank you for the info, it is greatly appreciated. After reading that Google bug thread you linked, I have very high hopes that this is the fix I've been looking for for six months now.
Thanks again man and I'll report in a day or two as I have no more reasons to reboot for a while.

48 hour mark just passed and still running like a champ

Performance tweak

Hi...
First, I will take no credit nor blame for the success or failure of your beloved DS7 as a direct result of applying the tweaks....
I am simply posting a link of a performance tweak that I found that seems to help with how my tablet is performing.
I applied the tweaks to my WiFi DS7 running ICS B4 and although I have only been using it for the last couple hours, I can certainly tell that it's performing much smoother.
I have not yet explored all the changes the tweaks has made to my system so be warned that the mileage may vary.
http://forum.xda-developers.com/showthread.php?t=1353903
I applied the tweaks (version 6 - the newest one) via CWM.
I downloaded the zip file but since it's saved to my internal card, I had to first copy it over to my external card so CWM could see it. So once that's done, simply boot into recovery mode and flash.
I hope this helps and if it does, please hit the thank you link...
I will be posting our results of this tweak to the OP to give him proper credit.
Good luck.
BTW.. I am running this on my Samsung Galaxy Player 5.0 also with favorable results so far...
Edit: So, I used this tweak package for about a day now and it seems to help out with the performance a lot. The only thing is, it froze my DS7 a few times initially. I upped the idle CPU Freq. limit to 312 (under CM9 Performance tab in settings) yesterday afternoon and so far no more freezes. I did this because one of the system freeze event took place in idle. It would freeze where only a hard reset (pin hole next to SD slot) would shut it down. Other than that, I am liking the smoother UI now.

Interesting I'll give it a go and see where the chips land for me

[KERNEL][AOSP] mamarley's BETA Droid Incredible ICS HWA kernel

This is a kernel for designed for recent builds of drk.hd's and invisiblek's CM9 builds. It is based on the "stock" Evervolv kernel used in those ROMs, but it has more features like USB Fast Charge, HAVS, and support for the 128mHz CPU speed. It is also compiled with GCC 4.7 instead of 4.4.
This kernel is only compatible with drk.hd's a9 build, invisiblek's 5/29/2012 nightly, or later. This is because of incompatibilities between the versions of the Adreno drivers and libraries used in the ROM and kernel.
Lite kernels: The lite kernel is similar to the regular kernel, except it has "unnecessary" features such as zRam, swap, KSM and most of the CPU governors and IO schedulers removed. If you use smartassv2 and SIO and you don't use zRam or KSM, these kernels are for you.
All the releases here are classified as beta, so there may still be problems to work out. If you run into anything, please let me know.
All of the releases may be downloaded here: https://github.com/mamarley/android_kernel_htc_qsd8k/downloads
Changelog:
8/12/2012: Regular Lite
Compile with "-O3 -fno-tree-vectorization" for more speed
Quiet down the light sensor driver so it doesn't spew quite so much spam into the kmsg log
7/24/2012: Regular Lite
Pull in a few more optimization flags from the Evervolv kernel
Enable the TCPMSS iptables target because it appears to be used during tethering
7/7/2012: Regular Lite
Fix the first-touch lag issue that occurred when the phone was woken up on battery.
Package the "zram" executable with the Regular version of the kernel
7/6/2012: Regular Lite
Make USB Fast Charge setting changes take effect immediately
7/4/2012: Regular Lite
Sync changes from Evervolv kernel
Update configuration to hopefully fix the last few charger lockups
Re-enable IPv6 netfilter so that IPv6 traffic will show up in the statistics
6/29/2012: Regular Lite
Update to Linaro 12.06
Sync changes from Evervolv kernel
Add "lite" kernel with removed zRam, swap, and all governors/IO schedulers except smartassv2 and sio
6/20/2012: Regular
Allow compiling with GCC 4.7 (thanks to drewis and michaelh (http://seabright.co.nz/2012/06/11/kernel-not-booting-with-linaro-gcc/))
Compile with Linaro GCC 4.7
6/6/2012: Regular
Revert power-related changes in the OJ driver, hopefully fixing the decrease in battery life from the last version
Update configuration to hopefully fix WiFi tethering
Reduce WiFi voltage, should increase battery life slightly
6/1/2012: Regular
Update AMOLED/LCD panel driver to latest version (improves panel resume time)
Update BMA150 accelerometer driver
Update Atmel touchscreen driver
Re-enable 10-point multitouch (Should work at the kernel level, but does not work at the ROM level currently)
Update Optical Joystick driver (This one is for all you Replica Island players out there )
5/31/2012: Regular
Add the Intellidemand and Lazy CPU governors (Thanks tiny4579 for getting them to compile)
5/30/2012: Regular
Initial release based on Evervolv qsd8k ICS kernel (https://github.com/Evervolv/android_kernel_htc_qsd8k)
Add USB Fast Charge support (thanks tiny4579 and chad0989)
Add HAVS support
Add support for 128mHz CPU clock operation
Add lagfree, interactiveX, and smartass CPU schedulers. Set smartassV2 as default
Add SIO IO scheduler and set it as default
Make a few minor configuration changes to reduce binary size
Kernel Source:
https://github.com/mamarley/android_kernel_htc_qsd8k

marley, not to be rude.. but there really is no difference between this and the incredikernel hwa beta 2 kernel right?

Gorilla* said:
marley, not to be rude.. but there really is no difference between this and the incredikernel hwa beta 2 kernel right?
Click to expand...
Click to collapse
they're completely different kernel sources. This is meant to be a more stock AOSP kernel with extra features mamarley. If you were fine with the stock kernel from the most recent CM9 builds, this is similar to that with a few extra useful features.
mamarley, you should add lazy governor. It's just a thought.

tiny4579 said:
they're completely different kernel sources. This is meant to be a more stock AOSP kernel with extra features mamarley. If you were fine with the stock kernel from the most recent CM9 builds, this is similar to that with a few extra useful features.
mamarley, you should add lazy governor. It's just a thought.
Click to expand...
Click to collapse
I tried to add lazy, but I kept getting all sorts of compile errors. Here is an example, but there are many more along the same lines:
drivers/cpufreq/cpufreq_lazy.c:538:6: error: 'sampling_rate_max_old' undeclared here (not in a function)
I applied exactly the same patch that you applied to Incredikernel, so I am not sure what is going on there.

mamarley said:
I tried to add lazy, but I kept getting all sorts of compile errors. Here is an example, but there are many more along the same lines:
drivers/cpufreq/cpufreq_lazy.c:538:6: error: 'sampling_rate_max_old' undeclared here (not in a function)
I applied exactly the same patch that you applied to Incredikernel, so I am not sure what is going on there.
Click to expand...
Click to collapse
Try adding the following to include/linux/cpufreq.h:
#define cpufreq_freq_attr_ro_old(_name) \
static struct freq_attr _name##_old = \
__ATTR(_name, 0444, show_##_name##_old, NULL)
#define cpufreq_freq_attr_rw_old(_name) \
static struct freq_attr _name##_old = \
__ATTR(_name, 0644, show_##_name##_old, store_##_name##_old)
Or modify the code in cpufreq_lazy.c to work with your existing cpufreq.h.
First option is easier I think. I think those defines are not standard. Not sure how I ended up adding them or in which commit. Adding them manually would be easier here.

Thanks tiny4579, that did it.
There is a new release out that has the intellidemand and lazy governors added.

New release out with some updated drivers

Awesome ill give it a shot! Thanks!
Sent from my ADR6300 using XDA

mamarley said:
New release out with some updated drivers
Click to expand...
Click to collapse
I suggest you release the multitouch as an optional download because it will not play nice with some phones.

nfiniti9 said:
I suggest you release the multitouch as an optional download because it will not play nice with some phones.
Click to expand...
Click to collapse
Are you having problems? There is some logic in the touchscreen driver that should automatically switch to 2- or 3-point multitouch on phones that don't support 10.

mamarley said:
Are you having problems? There is some logic in the touchscreen driver that should automatically switch to 2- or 3-point multitouch on phones that don't support 10.
Click to expand...
Click to collapse
This could be the same problem I had a while back when I implemented multitouch on gingertiny-v2. Since the multitouch selection automatically reverts to 2 or 3 point there really isn't a need to set that value to 10 in the config_T9 array. This is assuming you're using the multitouch selection patch. I know for a fact setting that value to 10 broke it for some devices for me. Try reverting that and seeing.

Been using the 6/1 version for a few days now. Battery life isn't nearly as good as 5/31.

thekendog said:
Been using the 6/1 version for a few days now. Battery life isn't nearly as good as 5/31.
Click to expand...
Click to collapse
I thought I had noticed that too. Let me do some testing to figure out which driver update caused the issue.

I just posted another update. The new version should fix the battery life issue and the WiFi tethering issue.

Marley, lol, I was having lock ups and freezes with incredikernel, so i flashed your 6/1 kernel, then just as I booted into the OS and realized your kernel works! You posted an update lol..
At the same time i decided to upgrade my Radio to 8.08
Now im gonna flash your 6/06 kernel
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
The big thing I already notice about your kernel is it works!
Its responsive.. When i ask the phone to reboot it does.
With incredikernel it would hang there, at the boot menu then bootloop then come back into the OS before it executed a command.. and
Unplugging from a power source would cause a freeze..
So far so good, Im gonna check wireless tether now.
---------- Post added at 01:31 PM ---------- Previous post was at 01:21 PM ----------
so far so good with the 6/06 kernel as far as smoothness but..
WIFI TETHER IS STILL BROKEN WITH 6/06

Gorilla* said:
Marley, lol, I was having lock ups and freezes with incredikernel, so i flashed your 6/1 kernel, then just as I booted into the OS and realized your kernel works! You posted an update lol..
At the same time i decided to upgrade my Radio to 8.08
Now im gonna flash your 6/06 kernel
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
The big thing I already notice about your kernel is it works!
Its responsive.. When i ask the phone to reboot it does.
With incredikernel it would hang there, at the boot menu then bootloop then come back into the OS before it executed a command.. and
Unplugging from a power source would cause a freeze..
So far so good, Im gonna check wireless tether now.
Click to expand...
Click to collapse
I never had any of those issues with incredikernel. I'm on marleys now and its running well. I did have one reboot on ik but I wasn't using the phone so I have no clue why it happened. Have not had any lag or reboots since using marley's. I have never had a reboot unplugging usb. Although I rarely use usb, I almost always plug it in a ac. I assume people having issues are actually plugging it into a computer usb port. And I'd be willing to bet most of those people are using laptops with a bit of software that monitors the usb for media devices.

Sorry, but I am out of ideas for the WiFi tethering. I have all of my network configuration options set the same as Incredikernel, so I don't know what is going on.

nfiniti9 said:
I never had any of those issues with incredikernel. I'm on marleys now and its running well. I did have one reboot on ik but I wasn't using the phone so I have no clue why it happened. Have not had any lag or reboots since using marley's. I have never had a reboot unplugging usb. Although I rarely use usb, I almost always plug it in a ac. I assume people having issues are actually plugging it into a computer usb port. And I'd be willing to bet most of those people are using laptops with a bit of software that monitors the usb for media devices.
Click to expand...
Click to collapse
I don't have an issue with USB and with fast charge on in incredicontrol with incredikernel. No reboots or freezes. I wonder if it doesn't like some phones. Doesn't make it a bad kernel.
Sent from my Galaxy Nexus using Tapatalk 2

mamarley said:
Sorry, but I am out of ideas for the WiFi tethering. I have all of my network configuration options set the same as Incredikernel, so I don't know what is going on.
Click to expand...
Click to collapse
WiFi hot spot works for me. As long as I remember to turn on mobile data. Don't use tether so I can't test that.
Sent from my GT-P7510 using Tapatalk 2

pmsrefugee said:
WiFi hot spot works for me. As long as I remember to turn on mobile data. Don't use tether so I can't test that.
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Good. I don't know what was going on with Gorilla. I don't have a data plan (Page Plus for the win!), so I can't test either myself.

General [ROM][12]Pixel Experience

**Edit** Post taken down**
Look for Senior Member/Dev(s) post for A12L(great job on PE+)

Esb1809 said:
Haven't seen any posts or heard anyone mention it yet but Pixel Experience on 5a is now official build(link below). Flashed it last night from A13 DP1 & pretty damn happy with all aspects (stability, set-up, looks/feel)
https://download.pixelexperience.org/barbet
Click to expand...
Click to collapse
Thank you for posting new rom link. What differences you noticed between this rom and stock? Is battery life better?

pawlik79 said:
Thank you for posting new rom link. What differences you noticed between this rom and stock? Is battery life better?
Click to expand...
Click to collapse
Honestly, for 90%+ of things/time it's almost identical to stock with tiny tweaks here & there. Biggest difference by far is exactly what they advertise as having... STABILITY. It just feels like a rock solid mirror image of A12 on a Pixel which is exactly what I was looking for, Magisk can tweak the rest.
For battery life, seems like it's definitely on par or better but I run LSpeed on all my devices so that's just my opinion, no proof.

Esb1809 said:
Haven't seen any posts or heard anyone mention it yet but Pixel Experience on 5a is now official build(link below). Flashed it last night from A13 DP1 & pretty damn happy with all aspects (stability, set-up, looks/feel)
https://download.pixelexperience.org/barbet
Click to expand...
Click to collapse
Finally got this flashed with twrp and it's very stable. Passes safetynet out the box without magisk and face unlock is a nice addition. Hopefully they make an official thread for it soon

syrkles said:
Finally got this flashed with twrp and it's very stable. Passes safetynet out the box without magisk and face unlock is a nice addition. Hopefully they make an official thread for it soon
Click to expand...
Click to collapse
+1. I additionally flashed with fsociety tribute kernel and love it.

flashed with unoffical twrp in adb sideload gave errors but i just ignored them. booted up no problems. went through setup. rebooted back to bootloader flashed fsociety tribute kernel with unoffical twrp adb side load. so far no problems.
anyone know how to get magisk to work?

rchris494 said:
flashed with unoffical twrp in adb sideload gave errors but i just ignored them. booted up no problems. went through setup. rebooted back to bootloader flashed fsociety tribute kernel with unoffical twrp adb side load. so far no problems.
anyone know how to get magisk to work?
Click to expand...
Click to collapse
Reboot to twrp and adb sideload magisk.apk

interesting. i always changed magisk.apk to magisk.zip and tried to flash it. never tried adb sideload the magisk.zip. worked like a charm. thanks! now it makes me want to reroot my nvidia shield.

i was actually surprised how easy it was to compile their rom. their instructs are fairly straight forward. skipped the ccache stuff first time. 2nd time i enabled it with compressing made it a little slower. compiled on debian 11 both times with no problems. process is long with the ccache and compression. 1hr 30min to 1hr 40min on my duel cpu 32 cores total running at 3.6ghz and 160gb of memory with a wd sn750 1tb nvme drive.
i think i have found rom that i will stick with until a really customized one comes along. barely any google garbage loaded on it. anything else i can root with magisk and use system tools android to strip out the few remaining google garbage apps.
best part is it's on A12 so the unoffical twrp seems to work without too many problems.

rchris494 said:
i was actually surprised how easy it was to compile their rom. their instructs are fairly straight forward. skipped the ccache stuff first time. 2nd time i enabled it with compressing made it a little slower. compiled on debian 11 both times with no problems. process is long with the ccache and compression. 1hr 30min to 1hr 40min on my duel cpu 32 cores total running at 3.6ghz and 160gb of memory with a wd sn750 1tb nvme drive.
i think i have found rom that i will stick with until a really customized one comes along. barely any google garbage loaded on it. anything else i can root with magisk and use system tools android to strip out the few remaining google garbage apps.
best part is it's on A12 so the unoffical twrp seems to work without too many problems.
Click to expand...
Click to collapse
How is the battery life? I have tested for a week and the battery life is not that great

jimmy16 said:
How is the battery life? I have tested for a week and the battery life is not that great
Click to expand...
Click to collapse
i stripped out a lot of apps. chrome, play store ar, calendar, digital wellbeing, pixel launcher (replaced with nova 7), gboard (replaced with openboard), safety, record, android auto (worthless i drive a 78 k10 and have a 2 knob radio), google support services (backdoor for google) and a few other useless apps that i can't think of at the moment. all can be removed once rooted with magisk and i use system tools android (the only app i have found that removes them and not hides them) to strip out the system apps. i use greenify (gotta get the beta from app mirror to use it on 12) to kill the apps as soon as the screen shuts off. i loaded fsociety tribute kernel. no tweaks i think i bumped the max cpu 24 mhz just to smooth it out a little more. i don't use the phone a lot. connected to wifi most of the time. gone from 100% to 77% in 22hrs about. i have only had the rom installed for a little over 24hrs. the battery drain seems about the same as stock. i did a dirty flash of my build of pixel experience and had to reroot in that 22hrs. so most of that 22hrs is standby time. mostly i check my miner and the price of crypto every so often and clean up my junk emails.
i guess i will know more as the week goes on. i usually get about two days of my type of usage before i get down to about 36% or so and charge again.
my main reason for switching is because i could not update any apps on the stock rom. if i updated messages. the keyboard would disappear or not show up. just before i flashed to this one. i would get the text message notice and when i went to the app. there was no new message. i would have to close and reopen the app to see the message, maps if i started a nav and because i use 3 button gestures. i couldn't close maps when i was done or it would split screen and hang up so you couldn't use the phone. phone and contacts app would work about 1/2 the time. camera app i would be lucky if it opened. problem with all of these apps for me have been going on since the A11 first release. i kept flashing new stock rom after stock rom hoping they would fix their garbage rom. that never happened. it got worse not better each factory rom flash. not really a LineageOS fan. nothing wrong with it. just its on A11 and the unoffical twrp seems to work a lot better on an A12 so i figured i would give this one a shot.

Anyone else having any form of A12/L/QPR3/ROM reduce their WiFi features down to just a toggle that, in true Google fashion, doesn't seem to toggle anything??
After the enjoyable game of "who gets pissed & hangs up on who first", I know it's baffling the hell outta whatever grade school they outsourced their tech support to..

Updated to 2022/3/30 build using updater. Stuck at 50% finalizing update. After uninstalling Magisk finalizing update was completed. Reinstalling and patching boot.img to get root back caused boot loop. What did I do wrong?
EDIT: forgot to add that used factory img from previous February build to patch. Do boot.img change every build?

Esb1809 said:
Haven't seen any posts or heard anyone mention it yet but Pixel Experience on 5a is now official build(link below). Flashed it last night from A13 DP1 & pretty damn happy with all aspects (stability, set-up, looks/feel)
https://download.pixelexperience.org/barbet
Click to expand...
Click to collapse
The question is, there are headphones, they have support for aptx adaptiv, a Google pixel 5a phone, the processor supports the codec, but there is no support in the system, can the PE developer include this codec in the firmware?

fackstrot said:
The question is, there are headphones, they have support for aptx adaptiv, a Google pixel 5a phone, the processor supports the codec, but there is no support in the system, can the PE developer include this codec in the firmware?
Click to expand...
Click to collapse
I'm not affiliated with PE ROM in any way, other than posting the link to give people an option besides LOS18.1, so that'd be a question for the dev(s).
I know there were a few Magisk modules floating around on Github but support for A12+ would be the kicker, could be a quick fix...
**Also PE+ should drop any day now for the Pixel 5a but haven't had time to actually read up on what's different with PE vs PE+**

fackstrot said:
The question is, there are headphones, they have support for aptx adaptiv, a Google pixel 5a phone, the processor supports the codec, but there is no support in the system, can the PE developer include this codec in the firmware?
Click to expand...
Click to collapse
you probably would get a better answer to that question in their telegram group. as this thread is started by a regular user not one of their developers.