Let's get this out of the way, I'm not responsible for anything more than a kernel panic.
Now that we've got that over with, I introduce to you - Zest Kernel. This ain't your average kernel on XDA. Zest Kernel is tuned down to every last mmap() to ensure that your device runs as fast and smooth as your hardware permits. No longer are the days of your battery dying on the bus, slow network speeds at home, or lags when swiping on those hot, new Android 11 gestures. Zest Kernel will revamp the experience of your device.
Spoiler: Here's what you get with Zest Kernel ꜰᴏʀ ʀᴇᴅꜰɪɴ.
Boot Time
By shrinking the kernel's size with Dead Code Elimination (DCE) and removing a bloat of debug and unused drivers, we decrease boot times [1].
LLVM Tools
Zest Kernel is built exclusively with the LLVM toolchain and tools, which allows us to utilise a wide range of security and performance features as well as satisfying my LLVM fanboy needs.
Networking Performance
Due to the addition of the rmnet_perf and rmnet_shs drivers from Qualcomm, cellular networking performance can see improvements due to network aggregation.
Performance
Through backporting mainline improvements to mmap() and locking, the kernel's core code receives improvements in performance and works to reduce jitter and improve system responsiveness. The return of BPF JIT allows us to improve performance with eBPF programs that Android utilises. As well as these changes, Danny (kdrag0n)'s efficient frequencies and Sultan's latency reduction patchsets are included which improve system fluidity and performance. LTO is also enabled, improving overall kernel performance. Tuning for ext4
Security
Zest Kernel utilises Clang's Control Flow Integrity (CFI) to protect against undefined behaviour that tries to subvert the kernel's control flow. Clang's ShadowCallStack, which protects programs against return address overwrites such as stack overflows, is also switched on and enabled with virtually mapped call stacks. All locals that are automatically initialised with zeros instead of patterns, which is safer for strings, pointers, indexes, and sizes. WireGuard is also included to provide a secure, performant VPN tunnel for those who wish to use it.
[1] - The first boot may take longer as F2FS (the filesystem we use) needs to check for corruption every time the kernel is changed for safety measures. Subsequent boots should be much faster.
Spoiler: How to install Zest Kernel ꜰᴏʀ ʀᴇᴅꜰɪɴ.
1) Make sure you're on the December or January SP.
2) Download Zest Kernel from the link below.
3) Enter fastboot (not fastbootd) with adb reboot bootloader or another method.
4) fastboot boot ZestKernel-Installer-P5<DATE>.img where <DATE> refers to the release date of the specific kernel.
5) Yes, I said boot not flash. I hope you read that correctly.
6) Read my beautiful installation header and wait for your device to boot up.
Spoiler: Download Zest Kernel ꜰᴏʀ ʀᴇᴅꜰɪɴ directly from my site.
Visit https://www.thezest.dev, click on "builds", then get the latest build from the relevant folder (Zest Kernel/redfin, in this case).
Releases are named in the form of ZestKernel-Installer-<Device Name><ISO 8601 Date>.img.
Spoiler: Where to get the source code of Zest Kernel ꜰᴏʀ ʀᴇᴅꜰɪɴ.
GitHub - lazerl0rd/tryme_redbull: A kernel for the Google Pixel 5 tuned to enhance system responsiveness, efficiency, and security.
A kernel for the Google Pixel 5 tuned to enhance system responsiveness, efficiency, and security. - GitHub - lazerl0rd/tryme_redbull: A kernel for the Google Pixel 5 tuned to enhance system respons...
github.com
Spoiler: Some screenshots of Zest Kernel ꜰᴏʀ ʀᴇᴅꜰɪɴ.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Notable credits for Zest Kernel ꜰᴏʀ ʀᴇᴅꜰɪɴ.
Sultan Alsawaf (kerneltoast/@Sultanxda) for his patchsets which help to improve the fluidity of graphics and more.
Danny Lin (@kdrag0n) for kramflash (the kernel installer) as well as a load of useful patches.
Jason Donenfeld (@zx2c4) for WireGuard.
***
If you enjoyed Zest Kernel, please donate to help keep up maintenance at https://paypal.me/paydiab. I'm strict on quality, and give each release it's quality time and care (possibly even more so than your OEM). Having a small income from these kernels gives me a better incentive to keep pushing them out for y'all.
***
Can i use this Kernel with ProtonAOSP?
I've installed it, let's see what it can do.
Edit: It got stuck on "Google" logo...
Edit2: My phone data just got corrupted, great.
MarcoG: said:
Can i use this Kernel with ProtonAOSP?
Click to expand...
Click to collapse
Yupp, I actually use ProtonAOSP myself.
2biT92 said:
I've installed it, let's see what it can do.
Edit: It got stuck on "Google" logo...
Edit2: My phone data just got corrupted, great.
Click to expand...
Click to collapse
Are you running a Pixel 4a 5G? If so, this is specific to the Pixel 5 (see the title).
LazerL0rd said:
Are you running a Pixel 4a 5G? If so, this is specific to the Pixel 5 (see the title).
Click to expand...
Click to collapse
I own a Pixel 5 unlocked with January SP. What kind of question is this ?
2biT92 said:
I own a Pixel 5 unlocked with January SP. What kind of question is this ?
Click to expand...
Click to collapse
I'm just double checking, as I have five users (other than myself) running this exact kernel. For most kernels, the Pixel 5 and Pixel 4a 5G share one kernel image (as well as Stock) but I've decided to split them for Zest Kernel in order to cater to their individual needs.
May I ask if you fastboot flash'd or fastboot boot'd this kernel?
EDIT: I'm going to assume you did the former, which is a mistake on your behalf (read the instructions properly). This kernel is running fine on multiple users' devices and the last build that ever broke boot never left my laptop (neither did it corrupt anyone's data). Feel free to correct me if I'm wrong.
Hell yea, thanks for being a Kernel Dev...Stock Android good enough for me, just need a smooth kernel, I dont think you can tune this thing to be faster, just smoother.
Vio281 said:
Hell yea, thanks for being a Kernel Dev...Stock Android good enough for me, just need a smooth kernel, I dont think you can tune this thing to be faster, just smoother.
Click to expand...
Click to collapse
Thanks for your kind words, though I'm not sure what you meant by your comment. Zest Kernel does indeed improve system fluidity (what you call smoothness), though "faster" is a wide term and can mean anything from "better benchmark scores" to improved system responsiveness - which Zest Kernel provides.
LazerL0rd said:
I'm just double checking, as I have five users (other than myself) running this exact kernel. For most kernels, the Pixel 5 and Pixel 4a 5G share one kernel image (as well as Stock) but I've decided to split them for Zest Kernel in order to cater to their individual needs.
May I ask if you fastboot flash'd or fastboot boot'd this kernel?
EDIT: I'm going to assume you did the former, which is a mistake on your behalf (read the instructions properly). This kernel is running fine on multiple users' devices and the last build that ever broke boot never left my laptop (neither did it corrupt anyone's data). Feel free to correct me if I'm wrong.
Click to expand...
Click to collapse
Indeed I flashed it, then I booted it. Maybe this is why it bricked.
2biT92 said:
Indeed I flashed it, then I booted it. Maybe this is why it bricked.
Click to expand...
Click to collapse
That is exactly why you bricked your device. That image is not an Android boot.img. It is a ramdisk containing a bootable version of Alpine Linux which in turn flashes the kernel and device tree to your device. The instructions explicitly state to not flash the image but boot it.
To solve your dilemma, you'll need to flash the boot.img corresponding to your firmware (and patch it with Magisk Manager, if you like) then fastboot boot my kernel image.
2biT92 said:
Indeed I flashed it, then I booted it. Maybe this is why it bricked.
Click to expand...
Click to collapse
soft brick...not hard you can fix it.
2biT92 said:
I've installed it, let's see what it can do.
Edit: It got stuck on "Google" logo...
Edit2: My phone data just got corrupted, great.
Click to expand...
Click to collapse
2biT92 said:
I own a Pixel 5 unlocked with January SP. What kind of question is this ?
Click to expand...
Click to collapse
Why are you so damn rude? Pay respect to other members, especially a developer having developed such a great kernel!
Thanks @LazerL0rd , first impression is so amazing, didn't think you could make this device even faster
Hecke92 said:
Thanks @LazerL0rd , first impression is so amazing, didn't think you could make this device even faster ❤
Click to expand...
Click to collapse
On the contrary, I was wondering if it's even possible for Google to make the Stock kernel any slower.
Will this work on the stock image? Also I wonder why all those great modifications were not implented by default, any idea? After I flash it how do I rollback if I want to? Flash stock image as easy as that?
Well done! Very impressed so far. Not a big Sultan fan. But whatever you did works really well. Thank you for this.
Very good job on the kernel. Works great so far.
itista7 said:
Will this work on the stock image? Also I wonder why all those great modifications were not implented by default, any idea? After I flash it how do I rollback if I want to? Flash stock image as easy as that?
Click to expand...
Click to collapse
yes
LazerL0rd said:
Thanks for your kind words, though I'm not sure what you meant by your comment. Zest Kernel does indeed improve system fluidity (what you call smoothness), though "faster" is a wide term and can mean anything from "better benchmark scores" to improved system responsiveness - which Zest Kernel provides.
Click to expand...
Click to collapse
what I meant is the score on synthetic bench wont jump 100 points, it just make things more fluid.
Hecke92 said:
Why are you so damn rude? Pay respect to other members, especially a developer having developed such a great kernel!
Thanks @LazerL0rd , first impression is so amazing, didn't think you could make this device even faster ❤
Click to expand...
Click to collapse
Sometimes I can't stand it, I was mad because I've lost all my photos and app data that I had on my phone, but it was my fault because I've "flashed" it wrong. I apologize...
Related
I'm starting this thread as I'd like a place to talk about the Fresh Toast kernel as it doesn't look like one has been started yet. If flipz decides to make his own thread at some point then we can delete this one.
The Following is from http://geekfor.me/evo/21/fresh-toast-experimental/
Geek For Me is proud to release:
Fresh Toast Custom Kernel for your Sprint Evo 4g
Experimental, and only available through Fresh Updater.
Fresh Toast was a popular collaboration rom by toastcfh and myself for the CDMA Hero. I am proud to announce that it’s now available for the Evo! Rather than being offered as a separate rom it is now going to be offered as an update/patch for Fresh Evo. If you are running Fresh Rom 0.5.3 or 1.0.0 (testers/donors only right now) then you can get the update by enabling experimental roms in Fresh Updater (more info below). There are 0 changes made to the rom itself other than drivers, all of the changes are in the kernel.
The release notes on this are going to be very brief right now, and so is support. Please report any issues that you guys come across but don’t be too surprised by that due to it’s experimental nature. You all are the testers!
Fresh Toast Features:
* CompCache / ramzswap
o This is actually already included in Fresh Evo, but thanks to the new kernel it is hard coded in there and works a lot better.
* Overclock available up to 1.27ghz, however it doesn’t seem to totally function above about 1.15ghz.
o Only tested with SetCPU. Should also work fine with Overclock Widget. Neither are included.
o If you are reporting OC issues then make sure to say which application you are using. And don’t report it if it’s related to problems when going above 1.1ghz.
* Undervolt — http://en.wikipedia.org/wiki/Dynamic_voltage_scaling#Undervolting
o This lowers the voltage required by the processor at lower clock speeds, thus reducing heat and battery drain.
* Ext4 support — http://en.wikipedia.org/wiki/Ext4
o If using apps2sd then you can convert your ext partition to ext4. Read the wikipedia article for noted benefits.
o You can use AmonRA to convert from ext3 to ext4 without any data loss, just keep in mind that if you try using another rom that doesn’t support ext4 then it won’t be able to read it. Going from ext4 back to ext3 will require re-partitioning your sdcard.
* Both kernels contain extensive tweaks related to speed, power, VM, etc. More details and information to come on all of those tweaks.
* Brain F**k Scheduler aka BFS (optional) – http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
o One version of the kernel includes BFS and one doesn’t. BFS will definitely make your phone run faster but it’s done with a possible side effect of stability. Test it out and see if you have any issuers.
o If you are reporting any problems with Fresh Toast then make sure and say if you are using the BFS kernel or not.
o If you aren’t sure what a scheduler is: it’s basically what is responsible for queuing up work for the processor to do. From an engineering standpoint even though we can multitask on our phone, the CPU is technically doing only one thing at a time. A scheduler is what controls which job the CPU is working on and which ones are next. This replaces the stock android one with BFS.
Reporting an issue? Please give us which kernel number you are using (#13 or #20 — you can get this by going to Settings < About Phone < Software Information < Kernel Version) and also which overclock application you are using.
Download:
This can only be downloaded through Fresh Updater, and only if you are on Fresh Evo 0.5.3 or 1.0.0 (testers/donors only for now). Users coming from Fresh Evo 1.0.0 should not have to worry about wiping or doing anything special. If coming from 0.5.3 then a wipe might be required to get it booted, I didn’t test. Fresh Updater also has the kernels included with Fresh Evo so that you can go back to them if you have any issues with Fresh Toast. As always make sure you do a nandroid.
You must enable experimental roms in order to have them show up.
Fresh Updater > Menu > Configuration > Rom Update Settings > Display Experimental Roms — Then check for updates.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm currently testing out the fresh toast kernels on the DC 3.2.3 rom, I'll post back about my findings soon.
edit: So far it doesn't appear to be working with the DC rom. It's just hanging on boot. I'll give it a bit longer but its already
been sitting on the intial htc EVO 4g logo for 5 minutes.
edit2: I've been unable to get the DC Rom to boot with either of the fresh toast kernels. even with a data wipe. i'm going to try
again.. if anyone else gets it working please post.
Does this have the fps uncap? N if so for which hardware?
madunix said:
Does this have the fps uncap? N if so for which hardware?
Click to expand...
Click to collapse
it does not. given the tearing problem that the toast + epson fps fix kernel has, at this point I just want a kernel
that will enable over/underclocking. the fresh toast kernel fills that niche.
Actually we have been testing this Rom since it came out. Check the last pages of posts here.http://forum.xda-developers.com/showthread.php?t=700448&page=254
cds36 said:
Actually we have been testing this Rom since it came out. Check the last pages of posts here.http://forum.xda-developers.com/showthread.php?t=700448&page=254
Click to expand...
Click to collapse
that thread is about the fresh rom, this thread is about the fresh toast kernel
OneStepAhead said:
it does not. given the tearing problem that the toast + epson fps fix kernel has, at this point I just want a kernel
that will enable over/underclocking. the fresh toast kernel fills that niche.
Click to expand...
Click to collapse
How is it functioning on DC 2.3.2?
blassilando said:
How is it functioning on DC 2.3.3?
Click to expand...
Click to collapse
so far its not booting. i'm going to try a data wipe, but i didn't think that was necessary with kernels.
Relax just saying it is being talked about in his fresh rom thread. http://forum.xda-developers.com/showthread.php?t=700448&page=248 anyone else can reference that as well as this thread.
cds36 said:
Relax just saying it is being talked about in his fresh rom thread. http://forum.xda-developers.com/showthread.php?t=700448&page=248 anyone else can reference that as well as this thread.
Click to expand...
Click to collapse
sorry if i said something to offend you.. it was not my intention at all
OneStepAhead said:
sorry if i said something to offend you.. it was not my intention at all
Click to expand...
Click to collapse
No not at all man, no worries good to have a thread just for this rom. Flipz is doing some amazing work. I have installed a few roms and fresh has been the most stable for me. With this new kernel Rom for the first time I have seen a huge improvement in battery life. Can't wait to see what version 1 brings
does this kernel support the cams? didnt read anything one way or the other yet.
mr_black03 said:
does this kernel support the cams? didnt read anything one way or the other yet.
Click to expand...
Click to collapse
Both work correctly.
If u wanna use my binary in dc or anything else ull have to extract the binary kernel from the boot.img and compile it with the ramdisk from the Rom u are going to flash it to. Also ill need to modify the ramdisk to run compache/ ramzswap scripts and grab the modules from the fresh toast build also. Add all that to ur build and flash the newly compiled boot.img and u should be toasted up
No Problems
No problems here - Flashed using Amon_RA recovery. Running Fresh 0.5.3 ROM.
Quick question - I've been running the Fresh Toast kernal with BFS pretty nicely for about a day now, but I'm still unsure about a few things. How does the undervolting work? Is it automatic if I underclock the CPU, or is it always undervolted? Right now I have SetCPU set to a max of 1152.
nowhere2010 said:
No problems here - Flashed using Amon_RA recovery. Running Fresh 0.5.3 ROM.
Click to expand...
Click to collapse
which one of the kernels are you using
toastcfh said:
If u wanna use my binary in dc or anything else ull have to extract the binary kernel from the boot.img and compile it with the ramdisk from the Rom u are going to flash it to. Also ill need to modify the ramdisk to run compache/ ramzswap scripts and grab the modules from the fresh toast build also. Add all that to ur build and flash the newly compiled boot.img and u should be toasted up
Click to expand...
Click to collapse
thanks, sounds like i have some more learning to do before I could pull something like that off. i'm unemployed at the moment so time is on my side
OneStepAhead said:
which one of the kernels are you using
Click to expand...
Click to collapse
I'm using the one with no BFS.
I just flashed the bfs kernel coming from the latest fresh Rom. I went toast CPU and my max is at 599????
I ported Cyanogenmod 9 for the Hero build by Jordfaz. (Thanks to him!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloadlink: Cyanogenmod 9
Installation:
- Flash Lights_format_all (See other thread!)
- Flash CM9
- Reboot
- 32B: Flash a 32B kernel after flash of the ROM
After installation
- After boot: Go to ADWSettings - system - advanced - enable wallpaper hack and scroll cache: low quality --> This will fix your UI.
- To disable CRT-animation: Displays - animation OFF (Thanks toi SaySpaceman! ;p)
Working:
- Calls/SMS
- Data
- Youtube!
- Screenshot!
- Perfect rotation!
- ...
Not working:
- Bluetooth
- GPS
Changelog:
Code:
-- Cyanogenmod 9 --
v1.0
* Initial release
Hit the THANKS button, if you use this ROM!
I will complete this thread at a later time, but for the next month I'll have to study a lot , so maybe no time for uploading and completing thread.
You can disable the CRT animation. You go to Settings->Display->You turn off the Screen off animation.
I haven't found any bugs yet, everything works very smooth and even YouTube works! :good:
I think this is the best ROM for our "legacy" device
SaySpaceman said:
You can disable the CRT animation. You go to Settings->Display->You turn off the Screen off animation.
I haven't found any bugs yet, everything works very smooth and even YouTube works! :good:
I think this is the best ROM for our "legacy" device
Click to expand...
Click to collapse
Thank you! Didn't know you could manually enable/disable it.
i really want to try this rom in my old htc magic!
I would like to know wich recovery do you use and recommend to flash your rom.
another question is the funcionability of the apps with this rom
thank you for all your work for "our" device.
stiker said:
i really want to try this rom in my old htc magic!
I would like to know wich recovery do you use and recommend to flash your rom.
another question is the funcionability of the apps with this rom
thank you for all your work for "our" device.
Click to expand...
Click to collapse
I think you can only flash it with CWM recovery.
All apps that work on GB, will work in ICS.
But the Play Store will show a lot more apps, but a lot of them will force close when you try to open them.
But in general, everything should be smoother.
ok. This rom is good. But it is slow when download from playstore. Thanks!
Thanks for CM9, i was looking for some stable rom
I will try this ROM and will let u know my findings
Thank you for porting this over. I have neglected my HTC Magic for quite some time now, finally got it out, dusted it and went through the flashing bits for this. Stable and much smoother than I expected to have on a (relatively) dated device. Are the processor options under 'Performance' settings disabled or is it meant to be on 'ondemand' all the time?
Yanguang said:
Thank you for porting this over. I have neglected my HTC Magic for quite some time now, finally got it out, dusted it and went through the flashing bits for this. Stable and much smoother than I expected to have on a (relatively) dated device. Are the processor options under 'Performance' settings disabled or is it meant to be on 'ondemand' all the time?
Click to expand...
Click to collapse
You can't change any options in Performance. I'll see if I can change that, because now, if the displayed CPU speeds are right, the CPU is constantly running on 710 Mhz when you used it.
Default cpu frequence 710MHz is not stable enough to bootup my phone, could you please lower down to 650MHz please?
jejer said:
Default cpu frequence 710MHz is not stable enough to bootup my phone, could you please lower down to 650MHz please?
Click to expand...
Click to collapse
Did you try to flash it? My phone doesn't run on 710 either, but it does boot.
Yes, I flashed it. During boot, cat /proc/cpuinfo get 710MHz and boot failed. After set it to 620MHz, it bootup success.
Your ROM works great, thanks!
jejer said:
Yes, I flashed it. During boot, cat /proc/cpuinfo get 710MHz and boot failed. After set it to 620MHz, it bootup success.
Your ROM works great, thanks!
Click to expand...
Click to collapse
Ok, thanks! I'll set it to a lower speed in next version.
I would really advise against overclocking by default. The majority of these devices can overclock to acceptable speeds, but others can't do much at all. My mytouch 3g, for example, would freeze at anything above 595mhz, and it was most stable at 537 or below. So even with that lower overclock you decided on, I still wouldn't be able to use this without modifying the rom.
There are plenty of ways to make this recommended, but optional. You could put an oc script in a separate zip to flash. Or you could start using the fancy Aroma installer. Ezterry's yesno binary is really easy to implement.
tvall said:
I would really advise against overclocking by default. The majority of these devices can overclock to acceptable speeds, but others can't do much at all. My mytouch 3g, for example, would freeze at anything above 595mhz, and it was most stable at 537 or below. So even with that lower overclock you decided on, I still wouldn't be able to use this without modifying the rom.
There are plenty of ways to make this recommended, but optional. You could put an oc script in a separate zip to flash. Or you could start using the fancy Aroma installer. Ezterry's yesno binary is really easy to implement.
Click to expand...
Click to collapse
I didn't know the cpu was running at a higher speed. I thought it was a bug in performance section, who was showing the wrong speed, since my HTC Magic normally freezes at 710 Mhz.
It's been years since I last flashed a MyTouch3G (32B)... Just got back one that I'd gifted away two years ago, it decided not to boot around Christmas and I brought it home to wipe/reflash.
Glad to see work still being done on this old device! It's ahead of my G2X in Roms.. That's effin sad.
Now if I can just remember how you flash a kernel on this thing....
EDIT:
I'm a bit confused about the kernel.... the thread linked doesn't actually seem to be any specific kernel??? More "how to flash a kernel safely" and hboot/radio files. I already have the required hboot/radio! So which kernel do I use??
EDIT 2:
N/m.... can't be assed to sit here all night trying to figure out which kernel to use on an antique phone. Went with Gingerbread instead.
tutorial and links - SPL/radio/ROM
lotherius said:
It's been years since I last flashed a MyTouch3G (32B)... Just got back one that I'd gifted away two years ago, it decided not to boot around Christmas and I brought it home to wipe/reflash.
Glad to see work still being done on this old device! It's ahead of my G2X in Roms.. That's effin sad.
Now if I can just remember how you flash a kernel on this thing....
EDIT:
I'm a bit confused about the kernel.... the thread linked doesn't actually seem to be any specific kernel??? More "how to flash a kernel safely" and hboot/radio files. I already have the required hboot/radio! So which kernel do I use??
EDIT 2:
N/m.... can't be assed to sit here all night trying to figure out which kernel to use on an antique phone. Went with Gingerbread instead.
Click to expand...
Click to collapse
<<Check my signature below!>>
<<Goog flashing>>
Edited post (correction below)
Sorry for the wrong info on flashing your 32B device, I did not notice that your device was not a 32A sapphire but the 32B instead!
I think the answer you're looking for is here:
[ROM][WIP] United ICS - http://forum.xda-developers.com/showthread.php?t=1647493
"kernel -
ezterry's kernel + ics patches and some performance tweaks (enabled 710mhz overclock and other things) http://www.mediafire.com/?py8asp6ab109dyl
ezterry's ezgb 1.5.2 http://sandbox.devnull.name/android/ezgb-kernel/ezgb-2636-v1.5.2_S.zip "
<< info from tvall - http://forum.xda-developers.com/member.php?u=3038499 >>
lotherius said:
It's been years since I last flashed a MyTouch3G (32B)... Just got back one that I'd gifted away two years ago, it decided not to boot around Christmas and I brought it home to wipe/reflash.
Glad to see work still being done on this old device! It's ahead of my G2X in Roms.. That's effin sad.
Now if I can just remember how you flash a kernel on this thing....
EDIT:
I'm a bit confused about the kernel.... the thread linked doesn't actually seem to be any specific kernel??? More "how to flash a kernel safely" and hboot/radio files. I already have the required hboot/radio! So which kernel do I use??
EDIT 2:
N/m.... can't be assed to sit here all night trying to figure out which kernel to use on an antique phone. Went with Gingerbread instead.
Click to expand...
Click to collapse
You have to take a working 32B kernel, preferably a flashable zip. The link in the opening post isn't directing to a kernel, but search for it in the G1 section and you will find a lot kernels.
ICS is much faster, so I would suggest you try it.
Can you point me into the right direction? My dad has an old Magic 32B with Radio 27.08. What Kernel should i use? Or what ICS Version are you talking about?
Thanks in advance.
when is out the final version?
With a few requests from tab-plus owners, I started building ROMs for tab-plus. I don't want to ignor anyone so built for all models.
I can't reply all post because I don't have the tab to test. However, I tried to answer all PMs as detail as possible. Once a while in these few months, I received a few hostile PMs, calling me names, etc. I might have asked too many questions. I don't have the ability to guess what model or which ROM if they are not mentioned. I don't know why asking for a screen shot, a video or details would be too much for someone.
Anyway, I over estimated myself to support a device I don't have. I have spent too much resource and I don't think I can do this any more. Bye.
*** Lollipop is out so my development for Kitkat is done. As a closure, I included all tab-plus models in this final build***
for some unknown reason, download provider is missing in the final build
Patch didn't work and I need to rebuild. Hoping this is really the final.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonRom is another aftermarket ROM having its unique features. I have been playing with Carbon for sometime. It has some unique features like CarbonFibers and ActiveDisplay. Another cool ROM worth trying. Cheers!
goo.im is up again!
Release Note:
2014/8/2
Just finished the GPU performance settings. In case some tabs might have lower tolerance, I lowered the GPU default min. and max. freq.
I also enable the Carbon performance tool. You can flash kernel and recovery from there. zRAM can only be enabled by TricksterMod. Old methods doesn't work on Kitkat. This build included all Carbon features. Enjoy!
2014/7/2
With help from @zombiezoom, the Carbon 4.4.4 build proved working on Tab plus. I do a sync before building for 7.7. It was a bad move. Carbon has an incomplete commit which cause me 12 hrs. to make the build pass.
On request from the local friends, link for Alipay is added in Donation.
2014/4/19
There are a few bugs in CarbonRom for our tab since day one. SystemUI crash, Some pages in CarbonFibers crash...etc. I finally fixed them this weekend! So it's time for me to share. It include all the fixes in my Kitkat roms.
Change log: :victory:
Code:
Official Carbon [URL="https://carbon-rom.com/changes/"]Change log[/URL]
[COLOR="Blue"]2014/8/2[/COLOR]
- Latest CarbonROM source
- Android 4.4.4r2 KTU84Q
- kernel update for GPU O/C and zRAM
- add GPU settings in performance
- include performance tools
- zRAM support
- major Bluetooth update from Bluez
[COLOR="Blue"]2014/7/2[/COLOR]
- Latest CarbonROM source
- Android 4.4.4r1 KTU84P
[COLOR="Blue"]2014/4/19[/COLOR]
- Latest CarbonROM source
- Android 4.4.2r2 KVT49L
- Fix crash in SystemUI
- Fix crash in CarbonAbout
- Fix crash in CarbonFibers
- Fix in QuickSettings (mess up after change QSTile position)
Know issues:
Only minor issues:
1. Lock screen stay at landscape with Rotaion Lock is ON
2. A few apks (eg. Browser) with distort screen after rotation. (Can be recovered by selecting from recent menu again)
Downloads: :highfive:
goo.im: http://goo.im/devs/daniel_hk/rom/carbon
AFH: http://www.androidfilehost.com/?w=files&flid=13972
mirror: http://pan.baidu.com/s/1GjnUQ#dir/path=/carbon
Recovery requirement
** CWM6, TWRP 2.3.1 or above is OK.
Most of the 4.4 Roms require the latest reovery with file_contexts and set_metadata support.I have patch the update-binary to work with old recoveries.
** See my thread to patch any gapps or ROMs with set_metadata fail **
Source:
kernel & device trees will update the new kernel soon after testing
github: https://github.com/danielhk?tab=repositories
Credits: :good:
** The CarbonROM team!
** All those who donate to me. Giving me the resources to upgrade my PC and accessories!
** All those who help our cool tab's developments!
Donations:
I just cannot believe it man! You are unstoppable and I REALLY LOVE YOU
Thank you so much for this ROM..downloading it right now and I think it's gonna be better than OmniROM in terms of features :good:
Thanks daniel, how to access the old internal storage, cause the path changes to "storage/emulated" (whatever i forgot)
I cannot see my data, cause the old internal storage in "mnt/shell/sdcard"
so I must manually move all data to new path internal storage ?
ravhi1044 said:
Thanks daniel, how to access the old internal storage, cause the path changes to "storage/emulated" (whatever i forgot)
I cannot see my data, cause the old internal storage in "mnt/shell/sdcard"
so I must manually move all data to new path internal storage ?
Click to expand...
Click to collapse
Of course not. I don't have a Tab Plus to test but there are links to /sdcard, /storage/sdcard0, etc.
I don't know why you say you can't access. Apks will find the data themselves. You have to be more specific. Which apks, what do you want to do, etc.
At least you have to tell which model you have in order to get helps from others.
Good luck!
Sent from my Nexus 7 using Tapatalk
Oops, system UI crashed and I can't access anything other than settings via quick menu.
I have a p6200 WiFi+3G and now I am back to the latest build of OMNIRom
I already did 3 wipes but same problem exists
zombiezoom said:
Oops, system UI crashed and I can't access anything other than settings via quick menu.
I have a p6200 WiFi+3G and now I am back to the latest build of OMNIRom
I already did 3 wipes but same problem exists
Click to expand...
Click to collapse
Can you or anyone provide a logcat?
Thanks.
Sent from my Nexus 4 using Tapatalk
daniel_hk said:
Can you or anyone provide a logcat?
Thanks.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Done.
Messed my tab
This ROM did a really big mess on my tab. Been flashing roms since gingerbread, but this rom is a big mess.now my p6200 have a really screwed file system. i don't recommend using this.
phangs23 said:
This ROM did a really big mess on my tab. Been flashing roms since gingerbread, but this rom is a big mess.now my p6200 have a really screwed file system. i don't recommend using this.
Click to expand...
Click to collapse
I don't know what you meant by messing your file system?
I think you meant the content of the internal sdcard was moved to the folder 0. This is the way android handle multi user since 4.2. Your experience might only upto 4.1.2. There were similar misunderstandings early last year when 4.2 launched.
Flashing might corrupt the /data and/or /system partition. If it is interrupted during flash, partition info might be corrupted. Internal sdcard is inside /data and the content will be gone. But that would be a very rare situation. I would say one in a thousand.
Although there are over a thousand downloads all together, I haven't received a single success. I don't have a Tab-Plus to test so I decided to drop this build for Tab-Plus.
daniel_hk said:
I don't know what you meant by messing your file system?
I think you meant the content of the internal sdcard was moved to the folder 0. This is the way android handle multi user since 4.2. Your experience might only upto 4.1.2. There were similar misunderstandings early last year when 4.2 launched.
Flashing might corrupt the /data and/or /system partition. If it is interrupted during flash, partition info might be corrupted. Internal sdcard is inside /data and the content will be gone. But that would be a very rare situation. I would say one in a thousand.
Although there are over a thousand downloads all together, I haven't received a single success. I don't have a Tab-Plus to test so I decided to drop this build for Tab-Plus.
Click to expand...
Click to collapse
NO NO NO! PLEASE MAN! You can test anything with mine, just tell me what you want. I already provided a logcat.
This is the best rom yet, it has amazing features.
zombiezoom said:
NO NO NO! PLEASE MAN! You can test anything with mine, just tell me what you want. I already provided a logcat.
This is the best rom yet, it has amazing features.
Click to expand...
Click to collapse
Normally, there would be a missing resource (for the resolution of your tab) causing crash but I can't find any error in your logcat. If systemUI crash, how can you use it...
I don't know how you got the logcat.
If systemUI crash, you can only get the log via a PC.
Type:
adb logcat > logfile
will dump the log to the file logfile in your current directory.
A clean flash will clear the debug from PC. Try a dirty flash to keep the debug privilege.
Sent from my Nexus 4 using Tapatalk
daniel_hk said:
Normally, there would be a missing resource (for the resolution of your tab) causing crash but I can't find any error in your logcat. If systemUI crash, how can you use it...
I don't know how you got the logcat.
If systemUI crash, you can only get the log via a PC.
Type:
adb logcat > logfile
will dump the log to the file logfile in your current directory.
A clean flash will clear the debug from PC. Try a dirty flash to keep the debug privilege.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, the logcat I provided was done from my Linux laptop. Now, I only saw SystemUI crash warning once but everytime I boot the device I see a black screen no home! just the toolbar and softkeys.
So, if you need another one, I'll make another.
daniel_hk said:
Normally, there would be a missing resource (for the resolution of your tab) causing crash but I can't find any error in your logcat. If systemUI crash, how can you use it...
I don't know how you got the logcat.
If systemUI crash, you can only get the log via a PC.
Type:
adb logcat > logfile
will dump the log to the file logfile in your current directory.
A clean flash will clear the debug from PC. Try a dirty flash to keep the debug privilege.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Screenshots after a clean flash uploaded and you can see that I cannot access Home or Apps drawer
I also attached a ZIP of 3 logcat files.
Thank you so much for taking time to build for our tab
Downloading now!
Edit: the AFH link leads to the galaxy 7.7 downloads!
Edit: Fixed.
Thank you Daniel, everything is working as it should. But sometimes when restarting the tablet, it gets stuck on the CarbonRom logo. That's the only problem I encountered so far. I will update this post if I found any other problems.
EDIT: seems like it was fixed by flashing Minimal GApps ^^
Which Kernel to use?
I have tried all of the kernels available on the download link on the first post, but none work with my P6210. They all fail with a getprop error.
Is there a newer kernel somewhere? I am trying to use CM-11 unofficial or carbonrom.
Thanks!
Can folks please post experiences on the p6200, I've been using the 7.7 version which is fantastic, the most usable daily rom but if this is good enough on the plus, I'd really like to suggest this rom to a friend who is still stuck with 4.1 jb
xaadilhx said:
Can folks please post experiences on the p6200, I've been using the 7.7 version which is fantastic, the most usable daily rom but if this is good enough on the plus, I'd really like to suggest this rom to a friend who is still stuck with 4.1 jb
Click to expand...
Click to collapse
I am currently using the latest version and it's so amazing, ROCK stable. I have no problems with it. It's the best for Tab Plus so far.
EDIT: BTW a lot of people here -and I don't know why- don't appreciate the massive work that Daniel has made for Tab Plus. You could see a lot of downloads being counted but only a few people who would comment with reviews or even a thank you!
I'm extremely great full for daniel_hk's work but i think it would be great is somebody would test all P6200 roms and test them on common every day app and games and give feed back and benchmark scores as i have no idea what rom to try first ??? just look at the choices just from daniel_hk
this one is on my list to be tested just saying keep up the great work
Can we have some screenshots ram usage and benchmarks scores from somebody that uses it already? might cause more downloads and more replies
Thanks for your feedback on the plus zombiezoom, great to hear.
I've been trailing mainly P6800 (7.7) rom mods for about a year now. Its fantastic to be able to get access to these roms and everyone's hard work particularly Daniel, I must say he has so many roms posted and its great to trial them. I've been looking for a stable alternative to stock now for a while and I think I've found it.
I think people who use the roms are likely following guides from other sites, they just download, trial and don't comment here. To get everything working efficiently we do need to focus comments here to help the developers/ and ultimately ourselves by getting a nice working rom.
@ this point to have wifi, bluetooth, mobile function and other major functions to be working reliably is great. I'm sure those who make the switch from stock and remain would likely consider donations. I said on the 7.7 topic, that I rather less fancy functions and features and more stability. This way we can all leave the stock rom behind just like samsung left us there and turn to our rom of choice. Once we do that we then can support our developers who can in turn keep our devices stable and alive.
Thanks
THIS IS NO LONGER BEING UPDATED
This was just about a direct copy of the ROM here I created due to the dev including opengapps in his builds: http://forum.xda-developers.com/nexus-7-2013/orig-development/p-aosp-n-7-0-google-shame-t3448008
They are no longer doing that, so I am focusing on contributing to that. The v0.6 build there is equivalent and a bit better than the v0.6.1 build here. Just use their's. (Leaving the links here for now, but really don't use them. )
Full credit to @DevSwift1 for all his work on this thus far. (and the other contributors listed below). Seriously, the work they have done is a thing of beauty and I'm only doing this out of necessity of doing the right thing. (I'd rather not be, but I said I would and it may be fun.)
What works:
Audio
Brightness
GPU Acceleration
Bluetooth
Wifi
GPS
NFC
Location services
Camera and video recording
Video playback
MTP
Sensors
Bugs:
- very poor 1080p video recording quality
- Google seems to think you are using a 2012 N7. I pulled part of the fix for that since it was only part and broke the build. It should be worked out next build. (or, the next build)
You can dirty flash, but you may need to uninstall and re-install any Google Apps you installed from the Play Store.
Change Log
V0.6.1
- Uses kernel that is not vulnerable to CVE-2016-2059. (@zaclimon's with @DevSwift1's patches to compile it on GCC 4.9. The stock N7 kernel was never vulnerable to that CVE and neither was that one which isn't heavily modified from it.)
V0.6
- Updated to Android-7.0.0_r6, NRD90U, Sept 6, 2016 Security Patch. (I think r4 was actually the security patch. Not sure if there is more in r6.)
- Note that this is missing the fix for CVE-2016-2059 which was part of the Sept Security Update, but resides in the kernel which isn't part of the AOSP build. I'm fixing that and will have an updated ROM or flashable kernel soon. (Hopefully. Building the kernel is new to me)
V0.5.1
- Fork of DevSwift1's V0.5 with Gapps removed.
- Location Services works with wifi
Sources:
https://github.com/nbehary/manifest
Download:
v0.6.1
V0.6
Very Unsupported, experimental Download for Deb
This builds correctly from my fork of Devswift1's stuff which included Deb. I have no idea if it works.
v0.6.1 (Just the new Kernel for CVE-2016-2059)
V0.X (it should be about v0.6 if it works. Same sources except the parts that are different between the devices.)
Get Gapps from here: (The Micro Edition is the largest that will install due to size constraints on the System partition.)
http://opengapps.org/
contributors:
DevSwift1
zaclimon
parrotgeek1
nbehary said:
Get Gapps from here: (I recommend the nano package. It works. There are issues with them being too large.)
http://opengapps.org/
Click to expand...
Click to collapse
I was able to get micro Gapps installed with about 90m free space using the original ROM..(Will that cause issues ?? ) . Actually downloaded minigapps ,but created a gapps-config to install micro . I noticed that without Google search being a system app ,it gets killed quite quickly and takes time to load .That seems to have gone
Sent from my Lenovo X3a40 using Tapatalk
vkk178 said:
I was able to get micro Gapps installed with about 90m free space using the original ROM..(Will that cause issues ?? ) . Actually downloaded minigapps ,but created a gapps-config to install micro . I noticed that without Google search being a system app ,it gets killed quite quickly and takes time to load .That seems to have gone
Sent from my Lenovo X3a40 using Tapatalk
Click to expand...
Click to collapse
Doing that should be fine I'd think. The only issue is running out of space and as long as you aren't doing that there shouldn't be issues. (I only recommend nano since that is what I have been using and it worked for me so far.)
Unless the ROM itself gets 90mb bigger in future updates, micro should always fit. Technically, nothing should be writing to /system after install since it's usually locked anyways. Any free space in that partition just sits idle, unused.
Any custom kernels works on it? Because stock is garbage. I saw nexus 5 reports of 6.0 versions working on 7.0
- There are reports of location not working without a GPS lock, for good reason. Play Services wasn't listed as a location provider.....common thing. I think I fixed it maybe, but in a effort to release this quickly, I haven't tested much. Please let me know if you still have issues.
Click to expand...
Click to collapse
You can mark this as fixed @nbehary
Thanks to you and to @DevSwift1 this has been posible thanks to him and i encourage him to continue working on this port, it's amazing so far and there are many users out there that thank you for your hard work and for giving this rom to the community. Thanks!
Also thanks to the rest of developers.
Beautiful widgets now locates correctly, and so many other apps like Waze or Meteogalicia (local weather apps) Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this when flashing. Afterwards attempting to flash gapps indicates that I'm still on Android 6.0.1.
Never mind. Just had to boot into the system and flash gapps afterwards.
I've been following all of these 7.0 ROM threads since the beginning. It looks like enough fixes have been done to this rom (thanks to the work of ALL the devs involved) for me to finally install it. Great job everyone!
DISCLAIMER FOR THE REST OF THE POST: Not for noobs or the faint of heart
I just dirty flashed this right over the last official MM and full device encryption enabled. For the most part things went smoothly. The only thing (and it's quite a lot for me) I had to do was uninstall and re-install, through the Play Store, just about everything from Google. The only app that didn't crash was Play Games - almost anything else with a Google account crashed, including MightyText (I originally suspected this was because I used nano GApps, which removed most GApps from /system - but YouTube Creator Studio and MightyText debunk that theory). After doing this everything seems to be running smoothly, but I'll continue to monitor battery usage. AOSP Calendar and Contacts have been disabled, in favor of the Google versions.
The biggest reason I wanted N was so I could use Night Mode and get rid of Twilight. The option is still baked into AOSP even though it won't appear in the Quick Settings shade. Download Night Mode Enabler from Play Store and the option returns.
Clean flashed 0.5.1, immediately rebooted back into recovery and flashed OpenGapps Pico and SuperSU 2.78 while wiping Dalvik and Cache between each step.
Everything works perfectly including the restoring of my Titanium app backups.
Thanks for supporting this device!
binglejellsx2 said:
The biggest reason I wanted N was so I could use Night Mode and get rid of Twilight.
Click to expand...
Click to collapse
Sorry for being off-topic, but Twilight is really bad compared to Chainfire's CF.lumen. Twilight adds a kind of overlay, while CF.lumen does it with root and a driver, which makes the screen not look washed out or blurry like Twilight. It's free, too. Otherwise there's the live display one in every CyanogenMod based rom.
FingerMove said:
Sorry for being off-topic, but Twilight is really bad compared to Chainfire's CF.lumen. Twilight adds a kind of overlay, while CF.lumen does it with root and a driver, which makes the screen not look washed out or blurry like Twilight. It's free, too. Otherwise there's the live display one in every CyanogenMod based rom.
Click to expand...
Click to collapse
Thanks, but now that Im on Nougat, I have a native solution available. The reason I used Twilight is because I don't root anymore. I'm aware of other solutions, but these days I'm looking for the simple stuff.
This ROM is exactly what I was looking for.
Can I skip tracks with volume keys?
Any get system ui tuner working?
Sent from my Nexus 7 using Tapatalk
dadymon53 said:
Any get system ui tuner working?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes. Just help the settings wheel down for a few seconds, nothing too crazy. Just use it to display battery percentage
V0.6 is up on the main page. It just merges in the Sept Security Update.
Extreemator said:
Any custom kernels works on it? Because stock is garbage. I saw nexus 5 reports of 6.0 versions working on 7.0
Click to expand...
Click to collapse
Going to say likely not. I just tried ElementalX, with all default settings, and it boots to recovery. There may be ones that will (in theory there can be, this uses the stock 6.0 kernel far as I can tell).
It really is in the kernel dev's wheelhouse to fix things for a new Android release. I totally don't want to get into that world. Did enough messing around in the Linux Kernel in the 90's.
That said, if there are things on the AOSP side I can do to help things work, I can look into that.
nbehary said:
Going to say likely not. I just tried ElementalX, with all default settings, and it boots to recovery. There may be ones that will (in theory there can be, this uses the stock 6.0 kernel far as I can tell).
It really is in the kernel dev's wheelhouse to fix things for a new Android release. I totally don't want to get into that world. Did enough messing around in the Linux Kernel in the 90's.
That said, if there are things on the AOSP side I can do to help things work, I can look into that.
Click to expand...
Click to collapse
So it boots to OS with elementalX? Or boots only to recovery?
Glitch kernel has a version that is compatible, but I have not used it yet
Extreemator said:
So it boots to OS with elementalX? Or boots only to recovery?
Click to expand...
Click to collapse
It boots to recovery. I think it got as far as showing the logo for a split second before rebooting into recovery. (I also was wrong about this being stock maybe. It was compiled too recently, and not by Google. Not sure where it came from, since it is just a Binary in the repos. Could still be a very slightly modified, if at all, 6.0.1 stock.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATED FOR April 21st 2023
I am not affiliated with the official Evolution-X team.
link to kernel source: https://github.com/psybernetiq/kernel_google_redbull_tiramisu-pixel
my other repos for the device and vendor are there as well.
downloads:
EvolutionX-13 - Google Drive
drive.google.com
flash the vendor_boot img. Then adb sideload the zip file in recovery.
Notes:
BACKUP YOUR DATA FOR THIS BUILD. YOU WILL PROBABLY HAVE TO RESET YOUR DEVICE TO FLASH THS ROM. SORRY FOR INCONVENIENCE.
I make reference to 9.9.9.9 (quad9 dns) rather than 1.1.1.1 (cloud flare) to 1 part in the code under bionic/libc/dns/net/getaddrinfo.c.
I added bromite webview support (does not require you to be rooted)
I added a flag called TARGET_IS_PIXEL_5 := true so that this device gets a hit to make persist.sys.disable_rescue=true. Without this, the device will boot but then reboot to recovery within ~10seconds.
I did not add wireguard support to the kernel this time. Let me know if you want me to add it back in.
passes safety net
The screen on my pixel 5 cracked back in March and I got a Pixel 7 Pro. I still have the pixel 5, though, and I tested this rom on the device before uploading and sharing here.
The March update was super late coming from Google, and the Evolution-X team was making a bunch of changes during this time (and they still are.) So consider this release an off-cycle release.
I was also having trouble building the ROM for a few weeks due to my laptop's RAM (32GB) being fried but not really making it clear to me that that was the problem. I had been using Qubes as my OS but have since gone back to good 'old Linux Mint. I liked Qubes but it's kinda a pain to constantly fuss with allocating the USB drives and I suspect the constant use of my 32GB of RAM to run all the virtual machines therein contributed to the premature death of my RAM cards (~1 yr old).
I build this ROM in the same tree as for my Pixel 7 Pro, so I should continue to make updates going forward for the Pixel 5. I'm planning on adding the Pixel 3XL and OG Pixel ("sailfish") as well, since I own all those phones, too.
Due to this trouble with my PC, the pathways to my keys (the ones you can see in /system/etc/security/otacerts.zip, you can see it includes the entire pathway where the keys are actually located in my PC) changed and I think that's why you have to clear data on this ROM. I'm also using a different Github repo now, too, as part of a rebranding process I'm doing.
Enjoy!
Can we flash this on top of your unbound rom without a factory reset?
screenshots of just some of the features
elong7681 said:
Can we flash this on top of your unbound rom without a factory reset?
Click to expand...
Click to collapse
I dont' know...sorry about that
aleph.mercury said:
I dont' know...sorry about that
Click to expand...
Click to collapse
Thanks for your fast response
elong7681 said:
Can we flash this on top of your unbound rom without a factory reset?
Click to expand...
Click to collapse
Asking the same question. Waiting for brave soul to try it.
saxmydix said:
Asking the same question. Waiting for brave soul to try it.
Click to expand...
Click to collapse
If the worst that could happen is having to factory reset and start over if it doesn't work then I'll give it a shot.
elong7681 said:
If the worst that could happen is having to factory reset and start over if it doesn't work then I'll give it a shot.
Click to expand...
Click to collapse
This is my main and only device, too lazy to backup at this point.
Why another thread? Why just update an old thread. just one question. Bluetooth volume up?
saxmydix said:
This is my main and only device, too lazy to backup at this point.
Click to expand...
Click to collapse
My only device too but I will try it after work
elong7681 said:
My only device too but I will try it after work
Click to expand...
Click to collapse
I just did, update on top of previous without wiping. Working good.
saxmydix said:
I just did, update on top of previous without wiping. Working good.
Click to expand...
Click to collapse
Awesome thanks for letting me know, so to update the rom would I just sideload it in recovery?
saxmydix said:
I just did, update on top of previous without wiping. Working good.
Click to expand...
Click to collapse
Please, cann you try bt headphone volume? On prew build was litlebit low.
got some freezes here and there when adjusting quick settings and had to reboot, but all in all seems to be a nice rom.
only thing i'm missing are advanced navbar settings like "force close active app when holding back-button"
also "connectivity thermal power manager" apparently draws way to much battery
@aleph.mercury I really do enjoy this rom but is there any chance that we can get Now Playing working on this ROM? I tried to enable it through the settings and it does nothing.
elong7681 said:
@aleph.mercury I really do enjoy this rom but is there any chance that we can get Now Playing working on this ROM? I tried to enable it through the settings and it does nothing.
Click to expand...
Click to collapse
I'll look into it. I never tried to use it before, I'll see what I can do
aleph.mercury said:
I'll look into it. I never tried to use it before, I'll see what I can do
Click to expand...
Click to collapse
Thank you
Aospmods magisk module will add some stuff you guys need
[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+
This is a mixed Xposed+Magisk module, which is made to allow customizations that are not originally designed in AOSP (Android Open Source Project). Features: Currently, AOSP Mods offers customizations on different aspects of system framework and...
forum.xda-developers.com
badaas said:
Aospmods magisk module will add some stuff you guys need
[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+
This is a mixed Xposed+Magisk module, which is made to allow customizations that are not originally designed in AOSP (Android Open Source Project). Features: Currently, AOSP Mods offers customizations on different aspects of system framework and...
forum.xda-developers.com
Click to expand...
Click to collapse
I want to say that I tried to install it on the unbound evolution x rom and it didn't work I ended up in a bootloop, have you tried it on this rom yet
Edit: It works on this rom
seems that "connectivity thermal power manager" and "com.android.hbmsvmanager" are drawing way to much power. together they drew like 50% and i had to recharge my phone midday, which usually never happens