{
"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"
}
Hi all!
After all the mess I had while testing MR2 on our Xperia S using the legacy video drivers, I decided it's time to get us a proper base on which all future Nozomi developments can be based. I want this to be a community project, so I'd like to encourage any available developer to contribute, and of course we also need testers to get proper bug reports, logcats, kernel logs. If these sound familiar to you, and you know what you're doing, you might be the person we are looking for!
Before you start reading the following, let me be very clear about one point here:
Never underestimate the power of open source.
The Xperia S (Codename Nozomi) is based on the Sony Fuji board which itself is based on the Qualcomm msm8660 (8260) platform, which features a Snapdragon S3 CPU chip and together with the Adreno 220 GPU and the integrated tavarua radio forms the SoC.
As of MR1/Android 4.2.X, the msm8660 chipset is officially abandoned by Qualcomm. This means: No official support from CAF for our chipset anymore, which, on a further note, means that we have to adapt >=msm8960 drivers to match the >=MR1 userspace grahpics drivers.
Related to the msm8660 ASoC, we are using MDP 4.1 compatible hardware, whereas recent CAF kernel branches focus on >=MDP 4.2 support for newer chipsets.
Paying attention at the driver merge in the kernel should be top priority, in combination with excessive debugging and hard work, we can achieve a better running system than some other 'officially' supported devices on MR1/MR2, like the Xperia T (msm8960).
Long story short, here is the current progress on my current CAF based kernel:
What is (basically) working:
msm_fb - framebuffer (upgraded to match MR2, sync point support)
msm_vidc - video encoding/decoding drivers (upgraded to match MR2, 1080p support)
msm_rotator - image rotator (upgraded to match MR2, sync point support, fast YUV not yet enabled for msm8660)
msm_kgsl - KGSL driver (upgraded to match MR2 (jb_2.5))
msm_gpu/adreno driver (upgraded to match MR2 (jb_2.5))
msm_iommu - page mapping (upgraded to match MR2 (jb_2.5))
msm_qdsp6v2 (upgraded to match MR2 (jb_2.5))
sound/soc (upgraded to match MR2 (jb_2.5))
What needs to be tested:
ION memory allocation (upgraded to match MR1 (mako) - unsure if it needs to be patched)
What definately needs to be worked on:
msm_fb fence syncing - causes massive lags
..? - Soft reboots when browsing Gallery
Now coming to the resources that I (preferably) use to upgrade our kernel, there are various kernel sources that don't quite match each other's APIs, so please pay special attention when contributing:
1) Samsung Galaxy SII (Skyrocket Board, msm8660): GitHub reference
2) Sony Xperia T (Blue board, msm8960): GitHub reference
3) More to come...
If you take a look at my kernel source, you can easily see the first thing I did was bringin up our kernel space video drivers to jb_mr1_chocolate. Despite being compatible to Android 4.2.X, (and the best branch to do the dirty bringup, because chocolate branches are meant for stabilization) there are a few crucial things to watch out for:
#1 - Do not mess with the ION allocation API unless you really want to change the API kernel-wide. By default, jb_mr1_chocolate uses a different ION api than our mako-based ION and IOMMU drivers. If you just blindly merge LK 3.0.y sources into our LK 3.4.y branches, be prepared to end up having various page mapping/allocation faults.
#2 - Watch out for mdp/rotator IOMMU split changes. In all our current kernels, we use IOMMU domain splitting to gain finer granularity which is needed for secure playback. A very good example on what to look out for is a commit I made recently to patch jb_mr1_chocolate video drivers to use the domain splitting technique again: https://github.com/OpenSEMC/android_kernel_sony_msm8x60/commit/4fed72fb2e12d16df1d137247c63b45477bad624https://github.com/OpenSEMC/android_kernel_sony_msm8x60/commit/4fed72fb2e12d16df1d137247c63b45477bad624
#3 - Watch out for buffer mapping changes (display_iova). As shown in the commit above, jb_mr1_chocolate by default uses diferent code to map framebuffer memory than our LK 3.4.y kernel does.
You can find my current kernel sources at OpenSEMC's GitHub repository:
ALPHA ---GitHub
BETA ---GitHub
I am actively contributing to and mainting this branch. The final goal is to have a kernel that matches the requirements of the latest Android iteration available. It'll be a long way until we reach that goal, but I am sure we can do it.
XDA:DevDB Information
CAF kernel for Fuji boards, a Kernel for the Sony Xperia S
Contributors
RaymanFX
Kernel Special Features:
Version Information
Status: Beta
Created 2013-09-27
Last Updated 2013-10-03
PROGRESS!
[09/28/2013] It boots! Graphic drivers are quite stable, no random reboots. Switching the project over to BETA stage.
[09/30/2013] Succesfully backported msm_vidc and KGSL/Adreno driver from jb_2.5!
[10/02/2013] Upgraded KGSL/Adreno driver to jb_2.6
[10/02/2013] Modified msm_rotator to improve the compability to our video drivers
[10/03/2013] Merged CAF's jb_2.5 sources into our kernel
[10/03/2013] Upgraded sound/soc and qdsp6v2 to jb_2.5
[10/03/2013] Upgraded msm_iommu to jb_2.5
[10/03/2013] Imported UHID driver from Linux 3.8
I'm not a dev,but i'm really happy about the caf, long live this project.
Sent from my LT26ii using XDA Premium 4 mobile app
Awesome! This could be a huge thing, I'll certainly keep an eye on it, sign me up for some testing!
More kernels are always good.
it must be a great job !
@RaymanFX Good Work! Bro.. Looking forward in your Sources.
---------- Post added at 09:37 AM ---------- Previous post was at 09:11 AM ----------
[/COLOR @RaymanFX recommended to add this At XDA News. Thanks.
TrinityHaxxorX said:
@RaymanFX Good Work! Bro.. Looking forward in your Sources.
---------- Post added at 09:37 AM ---------- Previous post was at 09:11 AM ----------
[/COLOR @RaymanFX recommended to add this At XDA News. Thanks.
Click to expand...
Click to collapse
Yeah.. Good work on the recommendation bro.. This is really worth it.. :good:
We reached BETA stage!
I managed to get a cm-10.2 rom with latest CAF display drivers booting!
There are some issues to be fixed, e.g. some minor animation stuttering (probably related to fence syncing) and broken video playback (easy), but this project advances way quicker than I expected it to.
I updated the source links and fixed all compilation errors. You can now build the project yourself
A public beta test version should be out soon!
RaymanFX said:
We reached BETA stage!
I managed to get a cm-10.2 rom with latest CAF display drivers booting!
There are some issues to be fixed, e.g. some minor animation stuttering (probably related to fence syncing) and broken video playback (easy), but this project advances way quicker than I expected it to.
I updated the source links and fixed all compilation errors. You can now build the project yourself
A public beta test version should be out soon!
Click to expand...
Click to collapse
Gooodjob! .
Sent from my LT26ii using xda app-developers app
OMG A GOOD 4.3 GOING TO BE OUT SOON!!!
Sent from my LT26ii using XDA Premium 4 mobile app
Great work, looking forward to it.
Sent from my Xperia SL
RaymanFX said:
We reached BETA stage!
I managed to get a cm-10.2 rom with latest CAF display drivers booting!
There are some issues to be fixed, e.g. some minor animation stuttering (probably related to fence syncing) and broken video playback (easy), but this project advances way quicker than I expected it to.
I updated the source links and fixed all compilation errors. You can now build the project yourself
A public beta test version should be out soon!
Click to expand...
Click to collapse
You are truely a ninja my friend.
Update from today:
* Backported VIDC, IOMMU, ION and KGSL from jb_2.5, so we're on par with recent high-end devices.
This will also save us the hassle of the untested ION/IOMMU stuff (which is on a MR1 level currently anyways.
Additionally, it will bring us proper graphics drivers (atleast I hope so, I did some early testing with GTA III, and it played just fine).
The new msm_vidc encoder/decoder drivers will also allow us to use CAF OMX libraries instead of mako ones which were patched to work with the CAF display drivers.
The next patches will also bring back Bluetooth keyboard support for Jellybean (UHID was needed).
Things are getting proper !
RaymanFX said:
I updated the source links and fixed all compilation errors. You can now build the project yourself
Click to expand...
Click to collapse
I tried and indeed the ROM builds without errors. I can flash it and recovery seems to be working.
But it will not boot. After the "OpenSEMC" boot splash there is no CM-bootlogo and a black screen forever.
I used "cm-10.2" manifest and changed kernel to "jb_mr2_chocolate_beta" prior on sync.
DeJe63 said:
I tried and indeed the ROM builds without errors. I can flash it and recovery seems to be working.
But it will not boot. After the "OpenSEMC" boot splash there is no CM-bootlogo and a black screen forever.
I used "cm-10.2" manifest and changed kernel to "jb_mr2_chocolate_beta" prior on sync.
Click to expand...
Click to collapse
It Just Mean it use dif.. Display drivers. that happens with me before.
TrinityHaxxorX said:
It Just Mean it use dif.. Display drivers. that happens with me before.
Click to expand...
Click to collapse
Well, what are these mysterious dif. display drivers? Do you have a solution or just say it isn't possible to build bootable ROM with current cm-10.2?
DeJe63 said:
Well, what are these mysterious dif. display drivers? Do you have a solution or just say it isn't possible to build bootable ROM with current cm-10.2?
Click to expand...
Click to collapse
Different display drivers?
To a man still learning, if it doesn't say exactly what is meant, then it doesn't mean that.
A lot of words start with dif...
And yes, it is possible to build a bootable ROM. Check the CM10.1 thread, somebody shared his build there.
DeJe63 said:
I tried and indeed the ROM builds without errors. I can flash it and recovery seems to be working.
But it will not boot. After the "OpenSEMC" boot splash there is no CM-bootlogo and a black screen forever.
I used "cm-10.2" manifest and changed kernel to "jb_mr2_chocolate_beta" prior on sync.
Click to expand...
Click to collapse
I havent checked myself but maybe use hardware/qcom/display-caf and audio-caf from cyanogenmod?
Sent from my LG-D802 using xda app-developers app
Related
Versioning explained:
>>>>>>>>>|0.92*|>>>> alpha>>>>>>beta>>>>RC>>>>1.0>>>>>
*0.92 will be removed as an option once RC comes out
This ROM is a spin-off from Mr. Linscue's and CyanogenMod sources.
What makes it different is that it is built with Linaro toolchain, current 4.7., instead of Google supplied one.
It's a product of my curiosity, Mr. Linkscue's extensive patience with helping me to understand the whole picture and his work so far on our devices. This wouldn't be possible without him.
To be able to build with Linaro toolchain there is a lot of CM source editing and git cherry-picking to make code fit for Linaro's GCC so the final ROM can actually be compiled. Thanks to Open Source, Android, internet and XDA-devs, I have been able to make it real by collecting the info and conveying it to this ROM.
I have to remind you, this is my personal build, it was never intended to be released to the wide public, I'm not a programmer/coder and there is no warranty.
Few notes:
1
The build: This is a first functional build through Linaro for this phone. It's compiled with -O3 flag, so /system (ROM) side is 90% optimized. I' m continuing to find proper code snippets that will further improve the build.
2
Battery life. Kernel used is prebuilt Lenovo, therefore battery life should be similar to official ROM, bar the specific LenovoPower settings, however if you are installing CM you are expected to know how to manage your phone. Without Lenovo's updated kernel sources, further optimizations are not possible, either for performance or extending battery life. If you are experiencing poor battery life, there are two things, 1. You have just I nstalled the ROM, give it a few days for system to settle in. There are few things going on during first day or two that might deteriorate your battery life 2. You have an app installed that is keeping your phone awake, preventing it to go to deep sleep. You can install BetterBatteryStats from here: http://forum.xda-developers.com/showthread.php?t=1179809 and find the offending app.
3
If you like it, use it. We are fixing general bugs as we go, and we know what those are. You may report them here but don't expect them to be fixed. Any app addition request or AOKP/MIUI/whatever port will not be entertained. As I said in the beginning, this is my personal build and I'm just sharing it with you.
4
Why name it SENNA: Ayrton Senna: “And so you touch this limit, something happens and you suddenly can go a little bit further. With your mind power, your determination, your instinct, and the experience as well, you can fly very high.This rom was made possible thanks to:
1.
linkscue
2.
zuncun
3.
xda-dev usersDJLamontagneIII, @Dri94
4.
OpenSource
5.
Linaro
Sharing is caring, so if you want to repost this ROM to other places, I don't care but I do ask you kindly to refer to http://bbs.lephone.cc/k860/t570716/
Since 99% of the work is by Mr. Linkscue,take your time and drop by his thread: http://bbs.lephone.cc/k860/t553805/1/ and give him some kudos.
That's all.
Two releases:
SENNA 0.92
Latest CM source
Reverted the codecs to official, now video is ok
Updated busybox binary
Special thanks to linkscue on his continued support
SENNA beta 1
Kernel is built from Lenovo old source and adapted for JB
Both kernel and ROM are built with Linaro at O3 optimization level
Samsung's gralloc, hwconverter, fimg and kernel mali drivers, readjusted memory use, replaced ion libs.
Bloetooth works.
Disable HW overlays to have video working in landscape mode
(Current result on Antutu is 21605) (I have to note here that I have noticed performance deterioration, the number you get varies and drops on subsequent tests)
SENNA beta 1
[bugfix] *Wireless hotspot - so far ONLY open network is supported
*replaced Bluedroid stack with Bluez - core to UI - BT works now,
****please report special use cases if there are bugs.****
[enh.] *Screen off animation
alpha6 / kernel 3.0.40
* corrected schedulers in cgroups (oops)
* Latest lowmemorykiller
* lowmemorykiller autodetect oom_adj values
* added CPU topology patch
* added compaction and migration
* CPU unaligned access path
* Patched CRC32
* Replaced TreeRCU > jRCU (Read/Copy/Update)
* Replaced SLUB > SLQB memory allocator
* WasActive page flag
* Makefile optimizations
* disable preemption in machine_shutdown
* synchronize_rcu_expedited instead of synchronize_rcu
* patched fimg
* completely updated kernel internals
* completely updated net and fs layer
* completely updated memory management
* [bugfix] long press on touchscreen during charging has been fixed
alpha5 / kernel 3.0.15
* Added SIO IO Scheduler
* Added BFQ IO Scheduler
* zram enabled (one zram device in use)
* KSM enabled in kernel, use menu to on/off its use
Beta 1: http://pan.baidu.com/s/1892bL
md5: af12fd4fc63542858cba978a8b7f6f51
0.92: http://pan.baidu.com/share/link?shareid=1733734082&uk=2184427820
md5: 25dffc77e3e269656497fa382a3897ba
Google stuff:
If you visit Mr. Linkscue's thread here http://bbs.lephone.cc/k860/t553805/ there is a link to Gapps preload partition.
http://dl.vmall.com/c0zc102rqh
Flash it as you would do with the ROM and then go to Settings/Advanced/K860(i) Install gms. Reboot. All should be there. In the same menu you are also able to lock the MAC address so it doesn't change on reboot.
Github is here:
https://github.com/jason013?tab=repositories
Good job. Running on my k860 with no issues. I hope you try to keep updating this ROM.
I will update you with issues I face.
{
"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"
}
Sent from my Stuttgart using Tapatalk 2
finch.****break said:
Good job. Running on my k860 with no issues. I hope you try to keep updating this ROM.
I will update you with issues I face.
Sent from my Stuttgart using Tapatalk 2
Click to expand...
Click to collapse
Thanks for liking it. I will keep it updated as much as possible. There are few bugs remaining on the platform and we are working on fixing them.
Definitely let me know if you have any problems with the ROM.
Good Job
This rom so good ! Waiting next update !
great room :victory:
waiting next update
finch.****break said:
Good job. Running on my k860 with no issues. I hope you try to keep updating this ROM.
I will update you with issues I face.
Sent from my Stuttgart using Tapatalk 2
Click to expand...
Click to collapse
btw how about gmaps? its work? coz i try to cm 10.1 phone reboot after i open gmaps,
Thanks before :good:
Harmalah said:
btw how about gmaps? its work? coz i try to cm 10.1 phone reboot after i open gmaps,
Thanks before :good:
Click to expand...
Click to collapse
Maps work for some time now.
first to vote for 5 star YAY
easily a 5 star for me since i dont know any programming/coding and im too lazy to do so...almost no support on lenovo ROM side so this addition is very much welcome...please keep it updated and kudos/respect to you my sir :good::good:
my only request would be a transparent and small on screen button for more screen orientation (see attached of my current screen)
you can get the systemUI here http://bbs.lephone.cc/thread-556541-1-1.html thanks thanks
Wow cool...will try ASAP
Sent from my Lenovo K860 using xda premium
innocence07 said:
easily a 5 star for me since i dont know any programming/coding and im too lazy to do so...almost no support on lenovo ROM side so this addition is very much welcome...please keep it updated and kudos/respect to you my sir :good::good:
my only request would be a transparent and small on screen button for more screen orientation (see attached of my current screen)
you can get the systemUI here http://bbs.lephone.cc/thread-556541-1-1.html thanks thanks
Click to expand...
Click to collapse
I'm sorry, you are talking about transparent taskbar? That iis as much as I could understand from the pics you posted.
To put it bluntly, what is going on now is trying to build kernel from source to match 4.2.2 and then cleaning up of proprietary files. Any UI polishing/additions I might consider at later date. So far, it seems to be a very far date But hey, it is functioning so far and sorry, but no..
relevant_placeholder said:
I'm sorry, you are talking about transparent taskbar? That iis as much as I could understand from the pics you posted.
To put it bluntly, what is going on now is trying to build kernel from source to match 4.2.2 and then cleaning up of proprietary files. Any UI polishing/additions I might consider at later date. So far, it seems to be a very far date But hey, it is functioning so far and sorry, but no..
Click to expand...
Click to collapse
yes both the onscreen button and the taskbar...its ok your the boss here anyways...and again thank you for sharing
i have another question uhm can i use this gapps http://wiki.cyanogenmod.org/w/Gapps since your rom is missing google play and other such gapps TIA
innocence07 said:
yes both the onscreen button and the taskbar...its ok your the boss here anyways...and again thank you for sharing
i have another question uhm can i use this gapps http://wiki.cyanogenmod.org/w/Gapps since your rom is missing google play and other such gapps TIA
Click to expand...
Click to collapse
Ok, I had skipped few tips here. If you visit Mr. Linkscue's thread here http://bbs.lephone.cc/k860/t553805/ there is a link to Gapps preload partition.
http://dl.vmall.com/c0zc102rqh
Flash it as you would do with the ROM and then go to Settings/Advanced/K860(i) Install gms. Reboot. All should be there. In the same menu you are also able to lock the MAC address so it doesn't change on reboot.
relevant_placeholder said:
Maps work for some time now.
Click to expand...
Click to collapse
btw how to fix USSD and change animated while charging ?
1. i try ussd not working and i used rillibrary.rar to fix ussd its working but signal bar not fully detect (how to fix)
2. and i could not charge if handphone is trunoff (how to fix)
thanks berfore
Harmalah said:
btw how to fix USSD and change animated while charging ?
1. i try ussd not working and i used rillibrary.rar to fix ussd its working but signal bar not fully detect (how to fix)
2. and i could not charge if handphone is trunoff (how to fix)
thanks berfore
Click to expand...
Click to collapse
Phone board/bootloader recognizes several operating modes like off charge, on, off, test etc. Mr. Scue identified them and it is working, however there is a problem that when you boot the phone after charging it in off mode, screen will turn white around the edges sometimes. For safety of your devices this part of functionality is not included yet.
I'm not familiar with the USSD problem yet. Will have a look into it, but if it wasn't working in official release, it could take time to make it working here.
relevant_placeholder said:
Phone board/bootloader recognizes several operating modes like off charge, on, off, test etc. Mr. Scue identified them and it is working, however there is a problem that when you boot the phone after charging it in off mode, screen will turn white around the edges sometimes. For safety of your devices this part of functionality is not included yet.
I'm not familiar with the USSD problem yet. Will have a look into it, but if it wasn't working in official release, it could take time to make it working here.
Click to expand...
Click to collapse
:good: thanks for explain
relevant_placeholder said:
Ok, I had skipped few tips here. If you visit Mr. Linkscue's thread here http://bbs.lephone.cc/k860/t553805/ there is a link to Gapps preload partition.
http://dl.vmall.com/c0zc102rqh
Flash it as you would do with the ROM and then go to Settings/Advanced/K860(i) Install gms. Reboot. All should be there. In the same menu you are also able to lock the MAC address so it doesn't change on reboot.
Click to expand...
Click to collapse
ive done all there is to do but still youtube dont work...em i missing something or youtube doesn't really work ???
innocence07 said:
ive done all there is to do but still youtube dont work...em i missing something or youtube doesn't really work ???
Click to expand...
Click to collapse
Ok, this questions now are going out of topic but let's chase this rabbit down the hole.
I am not familiar with the workings of youtube app (I assume you have successfully installed Play store and had it installed from there) so I am not sure what video/audio codecs it uses.
I can tell you right now one thing, related to video playback and Samsung's OMX codecs (the ****ty opensource ones) hw accel. video on this ROM is currently broken. I will soon reissue the ROM with files from official ROM to have that part working again, until I sort out what gets broken on OSS ones.
Currently I'm hands deep in kernel, I managed to transplant updated mali drivers into the old source to make it run on 4.2.2 and did some ugly hack job on HAL layer to have CM working, I have it at system stable level now. I'm tired and sorry for not being of much help, please google yourself and see what exactly are youtube app dependencies to make the videos run. If it uses on board hw codecs, I already told you what is the problem.
EDIT: try to disable GPU rendering for a test, in Developer options. just to see.
I flash several times this rom and always the same 2 problems ! Wifi doesnt work ! Stays there it said "turning wifi on..." and the 2nd camera program ( i dont remember the name ) always force close !!! Thanks
Sent from my K860 using xda app-developers app
what a great rom !! i hope you can fix the youtube problem and others minor problem soon!! :good:
Yup tried with GPU rendering disabled, HW accel enabled disabled.. Not just with youtube, videos don't work on many video content apps like imdb etc..
---------- Post added at 01:15 PM ---------- Previous post was at 01:15 PM ----------
However, wifi and focal seems to be fine
{
"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"
}
Bug list:
GPS & FM
What is working:
Media (IT IS FIXED) But Youtube can be dead
Audio (IT IS FIXED)
RIL (baseband) (IT IS FIXED)
Touchscreen xD
Image decoding
MTP
Webview
Camera
Sensors
Houdini
Wi-FI
Rom features:
It was build from fresh CM12.1 source (November stagefright patch is included)
I used proprietary files from WW 3.24.40.87
I used device tree by quanganh2627 for building so this way community will get all fixes
Custom kernel which was built from X Anwar sources so it has underclock, DT2W, million governors and i/o stuff.
How to flash it:
Step 1:
You should download files for flashing:
File with CM12.1 rom:
Google Drive
ADB v1.0.32: Download from Google Drive
TWRP 2.8.7.0 recovery by quanganh2627 (new December build): Download from Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom and gapps to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery new-zen5-reco.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should instal package with rom.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
Bug reporting:Attach logcat and detailed describe the issue. Send this to me (tank0412)
Credits:@quanganh2627 (i used his device tree for building)
USING MY ROM AS BASE FOR YOUR ROM IS DENIED
IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD
But you can use my kernel only without any problems.
XDA:DevDB Information
CyanogenMod 12.1 by tank0412, ROM for the Asus Zenfone 5
Contributors
tank0412
Source Code: https://github.com/tank0412/android_device_asus_a500cg-1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked bootloader
Based On: CM
Version Information
Status: Beta
Current Beta Version: 2.3
Beta Release Date: 2016-03-16
Created 2016-01-04
Last Updated 2016-03-21
Changelog(16.03.2016):
Trying to update Stagefright patch
Re-add Google Camera
Fixing writing to external memory card using Pixelmaster Camera.
Changelog(14.03.2016):
Apply vibrator.patch by @quanganh2627
Re-add camera app
P.S. I applyed patch but i do not know is it work. (hardware of vibrator is dead on my phone)
Changelog(13.03.2016):
Camera was fixed so it can make video without any problem
More fixes for media
Changelog(12.03.2016):
Audio was fixed
Media was fixed (but you can have few troubles with Youtube)
Changelog(04.02.2016):
Using blobs files from WW V3.24.40.87
And more
Changelog(10.01.2016):
DT2W was enabled
Unsuccessful attempt to totally fix Camera
Unsuccessful attempt to fix audio & media
Anyway, i am working on it.
Changelog(06.01.2016):
Latest fixes from quanganh2627s repo were applyed (commit #b953942e748b4d88f27b202abfc318dbd49161ea)
Changelog(05.01.2016):
Using fresh CM12.1 source
Minor fixes and improvements for audio, (i built libtinycompress and libtinyalsa libs from source, but audio is stay partly dead.)
Removed trash from Asus stock (only Asus Camera is included)
A tonn tweaks by @TecnoTailsPlays was added. (commit #56f91ca1fd3dc3e58d02d48b136a97c3a62567a1 )
Chagelog(04.01.2016):
Initial release
Reserved
Hot-fixesFix of MTP:
https://drive.google.com/file/d/0B-Fin8UxrD6PZWt6UWIxQmdMT3M/view?usp=sharing
Flash it via fastboot (drodiboot)
awesome, i waiting for upload good luck tank0412
milano88 said:
awesome, i waiting for upload good luck tank0412
Click to expand...
Click to collapse
I uploaded it few minutes ago. xD
tank0412 said:
I uploaded it few minutes ago. xD
Click to expand...
Click to collapse
i started download , after finish will immediately install thanks for your work
edited:
Anyone review?
Sent from my ASUS_T00J using Tapatalk
Running on Recreated Remix Ultra 7.2
Dont know,this is the most suitable CM 12.1 based for me,after trying almost all of cm12.1 rom here.
Less freeze after few days using...
Just 3 or 4 times freeze while charging
ShuviterDjogja said:
edited:
Anyone review?
Click to expand...
Click to collapse
Just trust me.
tank0412 said:
Just trust me.
Click to expand...
Click to collapse
Always trus the dev sir
[emoji106]
Always follow the threads..
Sent from my ASUS_T00J using Tapatalk
Thanks for this. I assume this is compiled from the latest source code (as of 2016-01-03), right?
Would you mind putting this on the OP, especially when you has an update version in the future.
I haven't tried this rom, waiting for audio fixed.
One thing that I don't understand, I see other offical cm12.1 rom size is about 250MB, but why zen5 get double size?
Firstly, I thought we will get a very small minimum rom size but it seems not that much different to Asus stock (after remove bloatware).
baszu said:
Thanks for this. I assume this is compiled from the latest source code (as of 2016-01-03), right?
Would you mind putting this on the OP, especially when you has an update version in the future.
I haven't tried this rom, waiting for audio fixed.
One thing that I don't understand, I see other offical cm12.1 rom size is about 250MB, but why zen5 get double size?
Firstly, I thought we will get a very small minimum rom size but it seems not that much different to Asus stock (after remove bloatware).
Click to expand...
Click to collapse
I could not download latest CM source so it was built from October source.
Many trash from Asus stock were added by quanganh2627's device tree.
I agree that this trash must be removed.
tank0412 said:
I could not download latest CM source so it was built from October source.
Many trash from Asus stock were added by quanganh2627's device tree.
I agree that this trash must be removed.
Click to expand...
Click to collapse
why you can't download the lastest CM source ?
i wait for the bug fixed, and will download this ROM. But right now is to much CM12.1 build for Zenfone 5 so i'm confused which one i must flash on my devices.
Awesome. Hope u will build CM13
Is it really that hard to fix GPS and FM Radio for AOSP based ROMs?
I'm dying for a clean AOSP based ROM but I can't flash it in these circumstances; no audio and no GPS :/
gusbalaa said:
why you can't download the lastest CM source ?
i wait for the bug fixed, and will download this ROM. But right now is to much CM12.1 build for Zenfone 5 so i'm confused which one i must flash on my devices.
Click to expand...
Click to collapse
Threre are only THREE CM12.1 builds. First build was made by Tran Huu Tin, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Parliamert said:
Is it really that hard to fix GPS and FM Radio for AOSP based ROMs?
I'm dying for a clean AOSP based ROM but I can't flash it in these circumstances; no audio and no GPS :/
Click to expand...
Click to collapse
I plan to fix audio but nobody can fix GPS because Broadcom and Asus have not published enough source code for this yet.
tank0412 said:
Threre are only THREE CM12.1 builds. First build was made by Knone, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Click to expand...
Click to collapse
Okay thanks, so i will prepared for download your build if stable versions is released, with fixed bugs.
But what about this one ?
http://forum.xda-developers.com/showthread.php?p=63910968
tank0412 said:
Threre are only THREE CM12.1 builds. First build was made by Tran Huu Tin, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Click to expand...
Click to collapse
I'm confused now. Do you mean your compile is also based on Tran's and Knone's source.
If this the case, it is not different to those then.
For sync source code, do you mean your internet provider block github or it is too slow to download latest source?
If it is latter, maybe, someone can help sync source and upload it to other website?
baszu said:
I'm confused now. Do you mean your compile is also based on Tran's and Knone's source.
If this the case, it is not different to those then.
For sync source code, do you mean your internet provider block github or it is too slow to download latest source?
If it is latter, maybe, someone can help sync source and upload it to other website?
Click to expand...
Click to collapse
I denied using my build as base for other custom roms. So nobody will use my build as base for their custom rom.
My build was really compiled from CM source like Knones build or Tran Huu Tins build.
My provider block repo tool so i can not use it. If somebody upload latest CM12.1/AOSP 5.1.1 code to other website, i will download it and this way i will use it for custom rom building.
gusbalaa said:
Okay thanks, so i will prepared for download your build if stable versions is released, with fixed bugs.
But what about this one ?
http://forum.xda-developers.com/showthread.php?p=63910968
Click to expand...
Click to collapse
It is just modificated build by Knone. It was not built from source.
AOKP MM 6.0.1 unofficial + nightly + official
DISCLAIMER
You need to have an unlocked bootloader to use this ROM & kernel. Also I or any contributor in the software DOES NOT take responsibility of damages caused to your phone due to this ROM.
{
"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"
}
1. Copy ROM zip and gapps zip to sdcard
2. Flash any kernel which has recovery (Use the boot.img in this ROM - It has TWRP)
3. Reboot device and go to recovery by pressing Vol-UP when LED is pink
4. If coming from 5.1 or below ROM wipedata/factory reset your phone
5. Flash ROM zip
6. Flash OpenGapps ARM zip
7. Reboot and enjoy.
Official NIghtlies (automatically built every 4-5 days) :
Basketbuild
Unofficial Test Builds (will contain experimental changes for testing) :
Mirror : Uploaded.to
Mirror : self hosted
Gapps :
http://opengapps.org
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to AOKP
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Latest merges on Gerrit
http://gerrit.aokp.co/#/q/sony+status:merged,n,z
Check out the ROM source on github. Open source, in the spirit of community kangage.
CREDITS
Thanks to all device maintainers of Sony devices on CM/AOKP/Omni/PA/PAC as everyone working on the device helps each other into making better ROMs.
Also thanks to Sony Mobile for being so helpful to developers.
XDA:DevDB Information
AOKP MM 6.0.1 unofficial + nightly + official, ROM for the Sony Xperia Z1
Contributors
championswimmer
Source Code: http://github.com/AOKP
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOKP
Version Information
Status: Alpha
Created 2016-02-09
Last Updated 2016-03-10
thanks for your works
Good work brother keep it up
I`ve found a unreleased cm13 build in your server can i use it?
built in twrp included in that version? @championswimmer
Luncer said:
Good work brother keep it up
I`ve found a unreleased cm13 build in your server can i use it?
built in twrp included in that version? @championswimmer
Click to expand...
Click to collapse
That cm13 build does not have TWRP.
feel free to download and use camera doesn't work on it though
@championswimmer can you tell me which kernel did you use as I have built bliss 6.1 and temasek 4.0 both based on Android 6.0.1 using cm13 kernel and everything is working except for WiFi.
markakash said:
@championswimmer can you tell me which kernel did you use as I have built bliss 6.1 and temasek 4.0 both based on Android 6.0.1 using cm13 kernel and everything is working except for WiFi.
Click to expand...
Click to collapse
Even camera ?
championswimmer said:
Even camera ?
Click to expand...
Click to collapse
@championswimmer No no camera is not working yet . Only working on aosp 6.0.1 built by crdroid but it lags a lot on camera. In my Roms I m having WiFi issue as it wont turn on. Can you help me to solve this issue if u have time?
I m sure its kernel issue as I flashed crdroid boot.img n WiFi worked but it stopped detecting my simcard.
Unfortunately I have bad news
1.In your aokp build camera doesn't work for me
2.Can't turn WiFi on
3.Auto brightness is buggy when screen turns on after phone lock (lock screen)
ROM Installed with twrp3.0.0
From cm12.1 nightly latest build
@championswimmer
Sent from my Xperia Z1 using Tapatalk
Luncer said:
Unfortunately I have bad news
1.In your aokp build camera doesn't work for me
2.Can't turn WiFi on
3.Auto brightness is buggy when screen turns on after phone lock (lock screen)
ROM Installed with twrp3.0.0
From cm12.1 nightly latest build
@championswimmer
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
-Sony camera blobs for marshmallow not released
-getting a dmesg log for OP would probably help him fix WiFi if it's a kernel issue
Sent from my C6903 using XDA Forums
Wifi shall be fixed in next release.
It is an selinux issue. It has been fixed.
We are working on open source camera
Hello, thanks for the rom.
The pros for now : very smooth, all my apps work, very good.
The cons (not repeat previous said) : i can't pair with my bluetooth car.
Thanks a lot to give MM to my Z1.
championswimmer said:
Wifi shall be fixed in next release.
It is an selinux issue. It has been fixed.
We are working on open source camera
Click to expand...
Click to collapse
New build up. Wifi and Bluetooth should be working now
championswimmer said:
New build up. Wifi and Bluetooth should be working now
Click to expand...
Click to collapse
I have installed the new version, and i have the message 'no sim card', the wifi doesn't activate.
Thanks
Same here WiFi and bt not working
Same here Wifi not activating and no Sim Card shown.
okay folks, next update will have wifi/sim/bt/cam all working BUT I am holding out on next update till some new changes get merged on CM.
There area lot of changes pending on CM tre. cdesai and kali- are testing a whole bunch of changes to move to using AOSP blobs instead of Sony vendor blobs for many parts.
You can check topic:aosp on review.cyanogenmod.org.
Once they are tested and merged, we will have a lot of things working then,
championswimmer said:
okay folks, next update will have wifi/sim/bt/cam all working BUT I am holding out on next update till some new changes get merged on CM.
There area lot of changes pending on CM tre. cdesai and kali- are testing a whole bunch of changes to move to using AOSP blobs instead of Sony vendor blobs for many parts.
You can check topic:aosp on review.cyanogenmod.org.
Once they are tested and merged, we will have a lot of things working then,
Click to expand...
Click to collapse
Great news buddy
If you want a tester im in[emoji6]
Sent from my Xperia Z1 using Tapatalk
Luncer said:
Great news buddy
If you want a tester im in[emoji6]
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Just to correct the record: there is no such thing as AOSP vs Sony blobs for rhine devices. All blobs are vendor (Sony) blobs. What was switched is 3.4 to 3.10 kernel and CM tree to Sony AOSP tree. And they are attempting to make it fully work with Sony blobs. Note that the reason nothing works on AOKP is that they are using CM tree. Everything is already working on Sony AOSP tree, but camera's quality is horrible, not to mention freezes, simcard issues etc....
optimumpro said:
Just to correct the record: there is no such thing as AOSP vs Sony blobs for rhine devices. All blobs are vendor (Sony) blobs. What was switched is 3.4 to 3.10 kernel and CM tree to Sony AOSP tree. And they are attempting to make it fully work with Sony blobs. Note that the reason nothing works on AOKP is that they are using CM tree. Everything is already working on Sony AOSP tree, but camera's quality is horrible, not to mention freezes, simcard issues etc....
Click to expand...
Click to collapse
Thanks for being a smartass.
The reason Wifi/BT did not work in the AOKP builds is Selinux (using permissive kernel will make them work).
What I mean by AOSP blobs is using blobs extracted from FXP's aosp releases.
What was switched is 3.4 to 3.10 kernel and CM tree to Sony AOSP tree.
Click to expand...
Click to collapse
I don't even know what you mean by that.
Now next time you try to act like an encyclopedia, you better know the **** you are talking about.
championswimmer said:
Thanks for being a smartass.
The reason Wifi/BT did not work in the AOKP builds is Selinux (using permissive kernel will make them work).
What I mean by AOSP blobs is using blobs extracted from FXP's aosp releases.
I don't even know what you mean by that.
Now next time you try to act like an encyclopedia, you better know the **** you are talking about.
Click to expand...
Click to collapse
First, please forgi-i-i-ve me for offending your ego. Second, if you don't know what others are talking about (like the difference between cm and sonyxpdev device trees), then you might do well educating yourself. Third, extracting FXP blobs does not make them AOSP blobs, since AOSP stands for android OPEN source, as opposed to blobs being CLOSED/PROPRIETARY. For this reason the term "aosp blobs" is absurd. And fourth, xda rules require you to post sources for kernel and I haven't seen those anywhere in this thread or on AOKP github.
Best regards
{
"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"
}
Hi guys, this is stock Android, also known as the Android Open Source Project (AOSP).
Welcome to the cleanest rom of them all. This project is a collaboration with @updateing and a continuation of his 7.0 builds.
Our goal is to provide the most solid taste of Nougat we can possibly give you. We may run into problems that we will not be able to fix because this is AOSP with necessary changes to build/boot the rom.
Current Known Bugs:
- Your recovery might be replaced with stock recovery (just reflash your recovery)
Current Fixed Bugs:
- Hardware buttons light up
- AUX problems have been fixed
- Tethering issues have been fixed
Downloads:
Latest ROM build (probably compatible with MultiROM)
7.0 builds
GApps
Source (working branch is nougat-mr1, or nougat-mr1-sultan if it exists)
Kernel Source
Screenshots:
XDA:DevDB Information
AOSP for the OnePlus One, ROM for the OnePlus One
Contributors
kwoktopus, updateing, Evolitist, freshgiammi
Source Code: https://github.com/aosp-bacon
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-10-30
Last Updated 2017-02-21
Notes on the sources:
local manifest
- Some fixes are really "dirty" (as I'm not able to find a proper way)...
- Some JNIs fail to build (lots of C++ symbols no found). You may try linking C++ libs dynamically (c++_static -> c++_shared) to avoid this. See 20160828 patches, packages/inputmethods/LatinIME for example.
- Some apps require android-8 ndk, but the earliest version in the tree is android-9. A symlink will do (or you can change the Android.mk in app) but I'm not really sure this will not introduce any bug.
- Android N split mediaserver into multiple processes to improve security, such as cameraserver, mediacodec, etc. But camera blobs and old HALs were not designed like this. They assume they run in the same process, thus a buffer created by blobs are being used everywhere, which will cause illegal memory access under Android N. I reverted lots of patches about this, forcing camera and codec services to run in the mediaserver process as before - security compromised with functionality, again.
Tnx ;D
kwoktopus said:
Notes on the sources:
local manifest
- Some fixes are really "dirty" (as I'm not able to find a proper way)...
- Some JNIs fail to build (lots of C++ symbols no found). You may try linking C++ libs dynamically (c++_static -> c++_shared) to avoid this. See 20160828 patches, packages/inputmethods/LatinIME for example.
- Some apps require android-8 ndk, but the earliest version in the tree is android-9. A symlink will do (or you can change the Android.mk in app) but I'm not really sure this will not introduce any bug.
- Android N split mediaserver into multiple processes to improve security, such as cameraserver, mediacodec, etc. But camera blobs and old HALs were not designed like this. They assume they run in the same process, thus a buffer created by blobs are being used everywhere, which will cause illegal memory access under Android N. I reverted lots of patches about this, forcing camera and codec services to run in the mediaserver process as before - security compromised with functionality, again.
Click to expand...
Click to collapse
Thanks man, I love your work.
:good:
Does flashing root save the recovery? Thanks for this build for our old bacon.
Everybody just delete recovery from boot in system after flashing and before booting up if you're recovery is wiped.
Looking forward for the build with the camera fix. :good::good:
3rd party app work like zcamera, camu, footag camera??????
A$h!$h said:
3rd party app work like zcamera, camu, footag camera??????
Click to expand...
Click to collapse
Next build should have camera fixed. Current build is missing a commit that I missed when pushing the changes to GitHub.
kwoktopus said:
Next build should have camera fixed. Current build is missing a commit that I missed when pushing the changes to GitHub.
Click to expand...
Click to collapse
Camcorder will already be fixed, I presume?
SirSoviet said:
Camcorder will already be fixed, I presume?
Click to expand...
Click to collapse
If camera is fixed, then video recording should be fixed as well :good:
NEW BUILD OUT!!!
More stable? ---- way more stable, camera is fixed as well
More features? ---- Hardware button configuration and navbar enabler
Daily driver material? ---- sure, I guess :silly:
Bugs? ---- please test for bugs
Better performance? ---- improved rom side performance
Camera is fixed, video recording works as well
Hardware buttons light up now
Navigation bar can be enabled as well
Please continue to test for bugs.
Also, please do not request for features.
This rom is AOSP based, and will stay as stock as possible
aosp_bacon-ota-eng.kwoktopus_20161030.zip
crisis_trustee said:
What about Pure Nexus builds on base of Android 7.1?
Click to expand...
Click to collapse
Do not ask about Pure Nexus in this thread anymore, first and final warning before I get mad D:<
kwoktopus said:
Do not ask about Pure Nexus in this thread anymore, first and final warning before I get mad D:<
Click to expand...
Click to collapse
Hahaha, kwoktopus, relax and a double thumbs up for a good job in both your ROMs, that guy has been impatient here and also in your thread over at forums OnePlus one. :laugh:
Edit: this guy has been spamming in the other threads too. Same question about 7.1 . He's asking to be banned??!:laugh:
Is root included or do we need to flash along with ROM
Sent from my A0001 using XDA-Developers mobile app
You are too fast man. Subscribed! Thank you..
ambient display is not working
Does this rom support fast charging?
lalith sai said:
Does this rom support fast charging?
Click to expand...
Click to collapse
rom is under test so you can test and report ^^ but i think not yet
{
"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"
}
PixelExperience for Redmi Note 8/8T
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0 / 11.0
DON'T FLASH GAPPS, ALREADY INCLUDEDDownload
Screenshots
Credits
- All those who helped me to build
- ghostrider_reborn for trees
- All the testers for testing my rom
Source Code - https://github.com/ghostrider-reborn
https://github.com/whyredfire https://github.com/caf-ginkgo
Rom Source Code - https://github.com/PixelExperience
XDA:DevDB Information
Pixel Experience Rom, ROM for the Redmi Note 8
Contributors
whyredFire
ROM OS Version: Android 10 / Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 10 Beta or Stable Firmware
Version Information
Status: Stable
Current Stable Version: 11.0
Stable Release Date: 2020-11-04
Created 2020-11-04
Last Updated 2020-12-12
Update 1: Initial R Build
- Everything is working initially
- Encryption doesn't work, #BlameCAF
Download
Update 2: Second R Build
• Fixed Notch overlay
• Switched to QuicksilveR
• Kernel Upstreamed to Linux v4.14.212
• Added Kcal Support in Xiaomi Parts
• Added ACC Support in Kernel
• Updated Xiaomi Parts Translation
• Merged December Security Patch
• Synced with the latest PE Sources
• Other fixes and Improvements
Download
Reserved 2
I don't think so
Manolo's build is already good, other than dt2w isn't working but can be fixed with flashing other kernel.
Question is, what significant differences are there?
Did or will manolo drop his PE and you aiming to replace?
Still, Good to see people still building pe roms and gapps builds.
Why???
Jaiiiiiiiii said:
Manolo's build is already good, other than dt2w isn't working but can be fixed with flashing other kernel.
Question is, what significant differences are there?
Did or will manolo drop his PE and you aiming to replace?
Still, Good to see people still building pe roms and gapps builds.
Click to expand...
Click to collapse
video recording is broken too lol
and he doesnt care about bug and all feedback from user. manolo build is g*y
---------- Post added at 11:34 PM ---------- Previous post was at 11:34 PM ----------
CheepPlüm said:
Why???
Click to expand...
Click to collapse
No why, if he can build with better experience than official, why not?
Jaiiiiiiiii said:
Manolo's build is already good, other than dt2w isn't working but can be fixed with flashing other kernel.
Question is, what significant differences are there?
Did or will manolo drop his PE and you aiming to replace?
Still, Good to see people still building pe roms and gapps builds.
Click to expand...
Click to collapse
His build has video recording broken, also his build is based on Los Device Tree and mine on Arrow Based. I have experienced roms based on Arrow device tree are smoother than the ones based on Los. Although this is my personal observation. I think he will drop PE with R releases but I have no plans for replacing him whatsoever.
I was busy with other stuff, so sorry for late reply
Note 8T
Overall feels much better than "official" release
Flashed over ResurrectionRemix with data wipe, everything seems good so far except for NFC module (greyed out in quick access menu, nowhere to be found in settings)
Is it just me and I have to do a clean flash or something with ROM? : )
HDR in Gcam Bug
So, today I installed this custom rom.
I'm installed the gcam, but when i turned on HDR my camera absolutely messed up with purple color
I hope u still support this rom!
Thank you.
TheGuy.030 said:
So, today I installed this custom rom.
I'm installed the gcam, but when i turned on HDR my camera absolutely messed up with purple color
I hope u still support this rom!
Thank you.
Click to expand...
Click to collapse
Yes, I know exactly what's causing that. But unfortunately my exams are very near and there is no hotfix for this one. But will try my best to do another build with this thing fixed and will give you a smoother ui experience as compared to this one. Also november security patch is here, so I might do a build this weekend with the fixes.
MichaelMay said:
Cheers, Since eleven is here I'm wondering if you want to take the official on this rom, the guy who stepped in for bad code walk seems to be out of the picture.
Click to expand...
Click to collapse
Yeah you should take it
MichaelMay said:
Cheers, Since eleven is here I'm wondering if you want to take the official on this rom, the guy who stepped in for bad code walk seems to be out of the picture.
Click to expand...
Click to collapse
Thanks for your kind and humble support . But only if it was possible. I just got into building roms and arguably this is the first rom that I compiled. I'm glad you all are liking it so far. As for eleven, either a new maintainer would step up, or the past one would improve theirs. And if none of them happen, I'm be still here to do that. We can't replace existing maintainer untill and unless he kangs stuff, else it'll be disrespectful for him/her.
I hope you understand.
Although since Android 11 is still new and in works, I'll release an EOL build with Android 10 which should fix the known issues.
the plus version when?
MichaelMay said:
I've built a few ROM's and as long as you keep your dev tree open and kernel stable going it's going to be fine. There are a lot of us that can help out with reviewing, adding and testing. I'm mainly doing C so my thing is mostly just backporting for kernel and making some new solutions.
My personal builds are based on your tree (from your github) but with a few changes that no one else will use anyway because users don't want to learn how to make a swap file on external memory or how to move caches from memory to disk when it isn't ever... ever... ever... used. A bit of that is resolved with the new PSI patches for 11 but that's for a later time.
You take care and trust me, I am nothing if not kind. My main concern originally with the PE dev was that he/she or her family was in trouble, as many are these days. I doubt he'd be "kanging" stuff (which to the best of my understanding is including things proclaiming them as your own in your commits rather than using the actual commits as are and then adding your own commit to fix them if need be). I think that when it comes to FLOSS programming and the Github system we all use we are honest about what we're doing.
Click to expand...
Click to collapse
I'm sorry just because I am seeing this one too late, was too busy with my school stuff. I just did another build for EOL and if everything goes fine, will release it asap. This time we have a big changelog coming.
UserJobLuigi said:
the plus version when?
Click to expand...
Click to collapse
I am doing this on my personal server. I can't afford to build two roms at the same time. I am doing PE because that's the one which gives the vanilla feel of a Pixel Device, so in conclusion I won't be able to do PE Plus anytime soon.
Thank you! Keep working
I installed ver android 11. Thanks for your work! Keep working
very nice i have install the ferst build and now i m downloading the update thanks Keep working
Ime haid options android 11???????????????
Exfat microsd suport ???????????