Please see this post in Xperia X forum and thread about AOSP9 builds for all Loire device, including Xperia X Compact / F5321
Thank you for the info, I will try it
Insane, thank you!!!
Fantastic news. Been waiting patiently for an update the past couple months. Just flashed this and it's working very smoothly, stable and no battery drain so far. Thanks for sharing!
20200307 build: 4.9.214 and 4.9.215 kernel updates
AOSP-9-F5321-20200307-4.9.214brcmfmac.zip
An updated clean build with 4.9.214 kernel (boot.img), and proposed 4.9.215 update (boot-4.9.215.img).
Please test 4.9.215 in priority, and in case of problem fallback to 4.9.214.
Both kernels have proposed wifi/brcmfmac update.
Not sure if flashing only the boot img over previous build will work: in case it doesn't, please do a complete/clean flash...
Is there anyhow fast charge available?
Hi everyone,
I am currently using AOSP 9.0-r46 with the 4.9.213 kernel. I compiled the image by myself following the build instructions provided by sony, so my problem meight not be reletated to the build of vknecht. Anyways, I have problems with the camera. No matter what app I am using (OpenCamera, AOSP-Camera or PhotoDirector) the auto focus fails to focus far away objects under bad light conditions. Objects near by can be focused without any problems. Also the focus of an landscape fails when it gets to dark.
I guess this is related to the proximity sensor, since the focus always fails if I cover it.
Does anyone have experienced the same problem or can reproduce it?
20200422 build: 4.9.219 kernel update
Posted updated build in Xperia X forum
vknecht said:
Posted updated build in Xperia X forum
Click to expand...
Click to collapse
Great job thanks for the update :victory:
---------- Post added at 11:52 AM ---------- Previous post was at 11:50 AM ----------
legenbaer said:
Hi everyone,
I am currently using AOSP 9.0-r46 with the 4.9.213 kernel. I compiled the image by myself following the build instructions provided by sony, so my problem meight not be reletated to the build of vknecht. Anyways, I have problems with the camera. No matter what app I am using (OpenCamera, AOSP-Camera or PhotoDirector) the auto focus fails to focus far away objects under bad light conditions. Objects near by can be focused without any problems. Also the focus of an landscape fails when it gets to dark.
I guess this is related to the proximity sensor, since the focus always fails if I cover it.
Does anyone have experienced the same problem or can reproduce it?
Click to expand...
Click to collapse
I haven't come across this issue before. Are you only experiencing it with AOSP? Is your phone case or rear cover perhaps blocking the sensor in any way?
20201003 update : new boot.img with kernel 4.9.230
Updated the release post with links to new boot.img including 4.9.230 kernel.
AOSP10 build with gapps
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
vknecht said:
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
Click to expand...
Click to collapse
I will try it soon.
vknecht said:
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
Click to expand...
Click to collapse
Excited to try this and thanks for still supporting kugo! I still use it as my primary device, running minextu's AOSP 10 (May security patch) but will flash yours too so see how it compares.
vknecht said:
If you feel like trying it, just uploading an AOSP10 build with included gapps for X Compact, please see this post.
Not super-stable (eg. reboots while booting), but should be at least as good as AOSP9 build, once it boots...
Non gapps build should follow later...
Click to expand...
Click to collapse
Thank you for my XC, will wait for non gapps build for testing.
I'll also wait for non gapps version. By the way I suppose you build with the kernel version which reduces reboots.
Enviado desde mi Xperia X Compact mediante Tapatalk
evilorb said:
Thank you for my XC, will wait for non gapps build for testing.
Click to expand...
Click to collapse
maluus said:
I'll also wait for non gapps version. By the way I suppose you build with the kernel version which reduces reboots.
Click to expand...
Click to collapse
Indeed, these builds are with latest-best-known-as-of-yet kernel (seen as 4.9.230 version)...
Here you go for non-gapps F5321 build :
e46ecc1d097b3c3645954b5d83d03f0e AOSP-10-F5321-20201101-4.9.230.zip
vknecht said:
Indeed, these builds are with latest-best-known-as-of-yet kernel (seen as 4.9.230 version)...
Here you go for non-gapps F5321 build :
e46ecc1d097b3c3645954b5d83d03f0e AOSP-10-F5321-20201101-4.9.230.zip
Click to expand...
Click to collapse
Just flashed this and so far so good! If you accept PP donations let us know. Thanks again!
wi-fi hotspot doesn't work. it turns off itself a few seconds after turning off. is this a known issue? Also bluetooh has a problem I guess. couldn't connect with pc. pairing is succesfull but when you try to connect. goes to pairing screen again. it seems good other than that. no battery drain so far.
Hey yes this is a known issue. Might be related to the kernel not sure. The previous aosp 10 from minextu has the same problem.
Related
Hey fellas,
I just start to compile a CM10 rom for my own use from the source and I wish to share with you guys.
So far so good, seems everything is working fine.
Instructions..
You probably know.. but just in case..
1. Boot to recovery (MANDATORY A TOUCH RECOVERY - I strongly recommend the RaymanFX's recovery (plenty of useful features): http://forum.xda-developers.com/showthread.php?t=1855686) (Thanks to RaymanFX)
2. Darkside super wipe - Thanks to him!
3. Wipe data/factory reset
4. Flash the rom
5. Reboot
6. Flash the GAPPS - http://goo.im/devs/Formula84/gapps-jb-20121012-4.1.2-JZO54K (Thanks to Formula84)
7. Reboot and have fun
Attention:
1. Do not install any kind of cpu manager, for now, like setCPU. Keep for now the stock frequencies. It can cause SODs and RRs.
2. When using Titanium Backup do not proceed restoration of data. It can be corrupted or even incompatible in some point to new releases. It can cause FCs.
Attention about to post a bug:
1. Before to post a bug, PLEASE, try to reproduce it at least twice.
2. Make sure that is not related to a bad and dirty flash, you can try to wipe cache and dalvik.
3. Be polite, after all, we are doing this for fun and for the pleasure of share, with no benefits at all.
4. You can contribute here with some debug methodology lol
Changelog (?!) (just a short description about what has changed in CM10 Source):
- Usual changes at the CM source. For more details http://review.cyanogenmod.com/#/q/status:merged,n,z (Thanks to krazeecracker)
- More about official CM changelog http://changelog.bbqdroid.org/#tf101cm10/next (Thanks to mobbarley)
- much more to come soon.. (just let me have some time to go through the kernel source code )
ROM
2013-02-12
http://goo.im/devs/erickwill/tf101/cm-10-20130212-UNOFFICIAL-tf101.zip
MD5SUM - dcb4a330156515d5f238fc4ee829033d cm-10-20130212-UNOFFICIAL-tf101.zip
For old releases:
http://goo.im/devs/erickwill/tf101/
ATTENTION
You DON'T need to install any other kernel. Everything works fine, at least in my end
As usual, THANKS everybody involved somehow in CyanogenMod development!
Hope you enjoy as I am enjoying this awesome branch.
PS. As also usual, I don't wanna get in flame with anyone over here. So please, any issue PM and I will, promptly, try to resolve any dispute or simply remove the content. I am posting this for fun and for the pleasure to share something that has been cool for me.
Oh, and please, just note that I am not responsible for bricked devices, dead SD cards and so on.
Have fun!
Guess I'm the only one in the mood to Flash a Rom tonight... So thanks
Mee too !! + 1
---------- Post added at 07:00 AM ---------- Previous post was at 06:43 AM ----------
And to be sure, what gapps are you using? Link please...
Very good.is dock working well and HDMI audio out put work?
Inviato dal mio Nexus S con Tapatalk 2
so I want to know if:
-NTFS R/W is working;
-HDMI A/V is working
-docking is working
-it is speedly
thanks a lot
Does this use my dock lid kernel space patch?
Hi,
Before trying, why all your links are for GS2 ? No risk for the Transformer ?
Caramel said:
Hi,
Before trying, why all your links are for GS2 ? No risk for the Transformer ?
Click to expand...
Click to collapse
We need to email cm team to they refresh/update/add tf101 device manteiners. We dont have one active for us anymore.
Caramel said:
Hi,
Before trying, why all your links are for GS2 ? No risk for the Transformer ?
Click to expand...
Click to collapse
Of course it's safe! I tried myself in my own tf101 otherwise I wouldn't post it here. Please check my signature and you'll read recognized dev okay?
prendomiao said:
so I want to know if:
-NTFS R/W is working;
-HDMI A/V is working
-docking is working
-it is speedly
thanks a lot
Click to expand...
Click to collapse
This is a compilation straight from the source, so as something is released from CM source it's available here, including fixes and other features
Enjoy
so they work?
Ahem..... Is the gapps update for 4.1.2?
Thanks.
Everything just works !! I am using the 4.1.1 gapps.....
Great ROM !
chappatti said:
Ahem..... Is the gapps update for 4.1.2?
Thanks.
Everything just works !! I am using the 4.1.1 gapps.....
Great ROM !
Click to expand...
Click to collapse
I'm using this version here. No problems to report on RaymanFX's Cyanogen 10 ROM. Formula84 always seems to have the latest GAPPS. I've used his previous two versions without issues.
grgmre said:
I'm using this version here. No problems to report on RaymanFX's Cyanogen 10 ROM. Formula84 always seems to have the latest GAPPS. I've used his previous two versions without issues.
Click to expand...
Click to collapse
Thanks, added this gapps at the op
[2012-10-14] [ROM - CyanogenMod 10 - JB 4.1.2 - UNOFFICIAL]
New release available:
ROM
2012-10-14
http://goo.im/devs/erickwill/tf101/cm-10-20121014-UNOFFICIAL-tf101.zip
Have fun!
What are the differences from just downloading the nightlies from get.cm?
st0nedpenguin said:
What are the differences from just downloading the nightlies from get.cm?
Click to expand...
Click to collapse
For now is pretty much the same thing, except by the way how each compiler gonna proceed in each compilation, I mean using different versions of JDK or tool chains..
I will be adding some cherries and my own stuffs pretty soon
[2012-10-14 - Revision 01] [ROM - CyanogenMod 10 - JB 4.1.2 - UNOFFICIAL]
Hey fellas,
Here you go the latest updates from the CM sources
ROM
2012-10-14 - Revision 01
http://goo.im/devs/erickwill/tf101/cm-10-20121014-UNOFFICIAL-tf101.r1.zip
Have fun!
Keeps Rebooting To Recovery
Flashed 4.1.2 with no errors. Everytime I reboot it goes to recovery. The only way I can get into the TF is a cold restart. Any suggestions?
erickwill said:
For now is pretty much the same thing, except by the way how each compiler gonna proceed in each compilation, I mean using different versions of JDK or tool chains..
I will be adding some cherries and my own stuffs pretty soon
Click to expand...
Click to collapse
The problem now with TF101 is to get a stable JB ROM, we have some nice nightly stuff like TeamEOS, JellyBro and RaymanFX CM10, but they're not really daily drivers, we need something like Megatron CM9, stable hi performance and battery saving ROM. And of course, kernel devs are so reaaly needed, since gevor hillness there's lot of ROMs out there but nohi powred kernels.
You said the magic word: cherries! If your way is to make a stable and smooth daily driver ROM count me in.
I have an idea to share/request: the CM10 wifi system is somewhat using an "old" scheme, maybe that could be tuned to "new"scheme, to work with Guevor CM10 kernel for instance.
Hope you continue this work, tf101 needs skilled devs.
So far I've got the basic A51x/A70x support added to my linux-tegra-nv-3.4 branch.
What works:
- The kernel boots
- Panel (partially?)
- USB
- Android is trying to start
Whatnot:
- everything else
So my first goal is to get display up. Currently, I've got a black screen after the bootloader logo, and the following logs:
dmesg
logcat
If anyone can help with this, hit me on hangouts, my g+ profile can be found on my xda profile. I'd appreciate any help, this would be a huge step forward for these devices.
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Agree on both
really awesome work
and we're already using hwcomposer.tegra.so from grouper
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Newer ones may be needed for 3.4, dunno... also, I may have just missed something simple...
Code:
W/SurfaceFlinger( 266): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 266): no suitable EGLConfig found, giving up
...
D/NvOsDebugPrintf( 270): NvRmPrivGetChipIdStub: Could not read Tegra chip id/rev
D/NvOsDebugPrintf( 270): Expected on kernels without Tegra3 support, using Tegra2
Anyways, I'm still working on 3.1, refactoring Acer's mess with the kernel files outside the kernel files... minimizing those changes will ease 3.4 development a lot, as it's confusing to watch out for Acer ifdef's all around the kernel
Hi, any news of this project?
chacal1906 said:
Hi, any news of this project?
Click to expand...
Click to collapse
I don't have the device ATM, so I can't do anything related to this.
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Hi, great to see you back. ?
My A510 is still alive. ?
The battery is not the best anymore, but it's is always ready to test your great work.
HornetRider said:
Hi, great to see you back.
My A510 is still alive.
The battery is not the best anymore, but it's is always ready to test your great work.
Click to expand...
Click to collapse
Great, I'm in need of an A510 tester message me on Hangouts
Ziyan said:
message me on Hangouts
Click to expand...
Click to collapse
Done [emoji106]
When will we see a working version?
Hi !
It's nice to see that someone is still working on A700/510 !
I have a A700 and if you need feedback, don't hesitate !
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Sterist said:
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Click to expand...
Click to collapse
TWRP3 ready
Kaban4ik86 said:
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Click to expand...
Click to collapse
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Ziyan said:
TWRP3 ready
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Click to expand...
Click to collapse
is the recovery mirrored somewhere? and what/where is this jenkins repository
Sterist said:
is the recovery mirrored somewhere? and what/where is this jenkins repository
Click to expand...
Click to collapse
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
This sounds great, I am already running the UA build on my Nexus, time to dust of the A700 !
Kaban4ik86 said:
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
Click to expand...
Click to collapse
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Sterist said:
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Click to expand...
Click to collapse
*.zip/META-INF/com/google/android/updater-script
Code:
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "36,0,32767,32768,32770,32849,32851,33341,65535,65536,65538,98304,98306,98385,98387,98877,106070,131072,131074,163840,163842,163921,163923,196608,196610,229376,229378,229457,229459,262144,262146,294912,294914,294993,294995,295485,313343") == "afd609f9867238c1cd370d82772817d744182c79" then
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "50,32767,32768,32770,32849,32851,33341,65535,65536,65538,66050,97792,98304,98306,98385,98387,98877,106070,106582,130560,131072,131074,131586,163328,163840,163842,163921,163923,164435,196096,196608,196610,197122,228864,229376,229378,229457,229459,229971,261632,262144,262146,262658,294400,294912,294914,294993,294995,295485,313343,313344") == "6b72a7b11b65c9ef1bb4c57ab78076d1ccd2e0e9" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
Overview:
Code:
[B]Experimental CyanogenMod 12.1 compiled with [URL="http://releases.linaro.org/14.10/components/android/toolchain/4.9"]Linaro 4.9 (14.10) Toolchain[/URL].[/B]
This is CyanogenMod 12.1 built straight from source with Code Review
cherry-picks and my own custom device trees and kernel.
CDMA carrier setup:
The following only needs to be done once to allow init to properly setup your carrier specific system properties.
This will set ro.boot.carrier to your specific carrier identifier and will persist through future flashes of this ROM.
Code:
From the bootloader issue the following commands depending on your carrier:
'fastboot oem config carrier verizon' (Verizon)
'fastboot oem config carrier pageplus' (Page Plus)
'fastboot oem config carrier reliance' (Reliance Mobile)
'fastboot oem config carrier sprint' (Boost Mobile)
Builds:
CM-12.1 06-08-2015 (MD5: (2414f09586228eb94bcda47c1f149ed0)
MMS Flashable Zip Fix Thanks @starkly_raving @Alberto97
TK Gapps Mini Modular 5.1 (05-30-2015)
Build Archives
Source Code:
codyf86/android_device_motorola_falcon
codyf86/android_device_motorola_msm8226-common
codyf86/android_kernel_motorola_msm8226 (Stock CM kernel Not even stock anymore kernel xD)
Code Review Cherry-Picks: (Latest build)
healthd: Use android blue for charge percentage
PowerManagerService: Fix updating of mUserActivitySummary
Add option to set default custom function to button recents (1/2)
Add option to set default custom function to button recents (2/2)
cmsdk: do not crash system if CustomTileListenerService isn't present
Note: When Items drop off the above list 9/10 they have been merged.
Changelog:
Code:
I don't believe in change logs; I believe in Github.
Please look above at the Code Review and also through
the source code commits to see what's changed.
The proof is in the [STRIKE]pudding[/STRIKE] Github.
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Yummy. Also trying this out for sure.
Edit: Sub'd, Muuahahaha!....Oh.
starkly_raving said:
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Click to expand...
Click to collapse
Feel free to post logs / bugs here. Mainly have time to build after work on weekdays. On the weekends is when I can actually work on fixing things.
For device specific things just post the bugs / logs here. For CM specific bugs I would use JIRA and post a link to the bug here. (More helpful/useful to the CM team to make an actual JIRA bug report.)
3 WORDS: STABLE AS ****!
thanks for the rom, this will forsure be my daily driver. only little problem is the no service icon (xt1031) but data is working. soft reboot fixes it though!
Can anyone please comment on the speed of this ROM since it is Linaro based? The other 5.1 ROMs on my phone are pretty responsive, but if even more speed can be gained with our limited hardware, that will be great.
@CodyF86,
Having a problem with the download link. Rom starts downloading but does not download the whole 251mb. Only partial download. Tried about ten times but still same result. Tried with a different browser but same result.
Edit: Nevermind. Downloaded the rom from my phone and copied it from download folder on phone to internal storage.
Hello there @CodyF86 ! Thanks for you work! One little request. Do you think you will be able to add a mirror or upload your work to another claudbased storage? Like MEGA or Mediafire or AndroidFileHost or whichever you want. This one you are using is insanely unstable for me. It gets interrupted every 5 minutes. I'll be really glad if you could change it or add other(s).
Cheers.
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
CodyF86 said:
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
Click to expand...
Click to collapse
Thank you very much! And sorry for bothering you with this. I really want to test your ROM since al Linaro builds seem gone from this forum. Thanks again. Drive safe
Cheers.
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
CodyF86 said:
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
Click to expand...
Click to collapse
thanks for both: new link and new build Can I dirty flash it over the build before? Just installed the first release lol
Cheers.
I've been dirty flashing; should be good to go.
Update: yes, this ROM is very fast indeed! Thanks for sharing.
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
starkly_raving said:
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
Click to expand...
Click to collapse
Same here. great work! Not as many customizable like other 5.1 based out there, but is enough fast and stable. Thanks.
just wondering what recovery you are using and do partitions need changed from stock?
What models are supported?
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Shawnsch said:
just wondering what recovery you are using and do partitions need changed from stock?
Click to expand...
Click to collapse
CWM 6.0.5.1 I think 6.0.4.7 is the last one posted on CMs website, I'll post the latest one in the OP tonight, but they're basically the same. Nothing needs to be changed from stock.
Orjakone said:
What models are supported?
Click to expand...
Click to collapse
Theoretically they all should work, but I need someone to the GSM version to try it out.
The_Poison said:
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Click to expand...
Click to collapse
Weird, I haven't noticed that, but tbh I haven't actually payed attention to what year my phone shows / I don't even have it set up to show me I'll have to look and see if mine does it also.
Will do another one tonight / it's the weekend can play around with it get some things done now.
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
What's working
Mostly everything except for those mentioned in not working list.
What's not working
Video recording (working but laggy if you want to watch it)
SELinux
How to install
1. Wipe system, data and both cache partitions
2. Install the ROM + GApps
3. Wipe again both cache partitions
4. Now you can boot to the system
Download
Unofficial LineageOS 15.1
sgspluss-gapps
Sources
github.com/sgspluss
Credits and Thanks
@sgspluss @Konstantinosj77 @galaxyfreak
Changelog
Code:
[B]lineage-15.1-20180722-UNOFFICIAL-eagle.zip[/B]
Sync with latest LineageOS sources
Some other device and kernel stuff
[B]lineage-15.1-20180707-UNOFFICIAL-eagle.zip[/B]
Fix low volume
Fix livedisplay
Fix kernel local version
Sync with latest LineageOS sources
Some other device and kernel stuff
[B]lineage-15.1-20180624-UNOFFICIAL-eagle.zip[/B]
Initial release
Troubleshooting
Video recording
Video recording is broken in stock camera, just install
https://play.google.com/store/apps/details?id=com.simplemobiletools.camera
as workaround for now.
Playstore show not certified
Try to clean app data and cache first, if its not working for any reason read this
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Low RAM Configuration
Add the four lines into your build.prop with any rootexplorer you want, save it and restart your phone to activate them.
Code:
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
If you need more information read this
https://source.android.com/devices/tech/perf/low-ram#intro
sgspluss said:
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
Information
This are unofficial builds made by myself, will fix things, resync and rebuild it if i'll find some free time.
What's working
Mostly everything.
How to install
1. Wipe system, data and both cache partitions
2. Install the ROM + GApps
3. Wipe again both cache partitions
4. Now you can boot to the system
Download
Unofficial LineageOS 15.1
sgspluss-gapps
Sources
github.com/sgspluss
Credits and Thanks
@sgspluss @Konstantinosj77 @galaxyfreak
Click to expand...
Click to collapse
did you fix some problems in this version?
i mean is there any different from the rom BETA 2?
and what abut laging? did you fix it?
Telephone works now, also timekeeping seems to work and not many lags faced yet.
Please try it on yourself, did not have much time to test every build because of my little family and work.
Every feedback is welcome!
thank you by the way to complete bulding this rom.what abt adding sony m2 stock cam app? from kitkat 4.4.4 maybe because its better than cam in v 5.1
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
sgspluss said:
Telephone works now, also timekeeping seems to work and not many lags faced yet.
Please try it on yourself, did not have much time to test every build because of my little family and work.
Every feedback is welcome!
Click to expand...
Click to collapse
great news..iam ready for start testing..i will report if i found somthing
hooooossamq said:
thank you by the way to complete bulding this rom.what abt adding sony m2 stock cam app? from kitkat 4.4.4 maybe because its better than cam in v 5.
Click to expand...
Click to collapse
snap is better because it uses newer drivers and open source (like the rom itself). and there is no point if you add sony camera because it is an AOSP rom, it meant to be pure android (except lineage tweaks)
Also @sgspluss , is this rom deodexed? if not, can you make it deodexed, it will make customisation easier
hooooossamq said:
what abt adding sony m2 stock cam app? from kitkat 4.4.4 maybe because its better than cam in v 5.1
Click to expand...
Click to collapse
Thats not that easy as you think, because need to port this app to the api, but apart of this i want to stay close as possible to lineage.
hooooossamq said:
Also @sgspluss , is this rom deodexed? if not, can you make it deodexed, it will make customisation easier
Click to expand...
Click to collapse
Afaik there will be no odex files, if there are one i will change it in next update. To be honest, did not check it.
Very nice to see new build But unfortunately I'll have time to play with it in this or next weekend :/
@sgspluss do you know why Magisk don't work on previous builds? M2 is no longer supported by Magisk or it's just fixable in the next builds?
after a test i notice these bugs:
1- laging so much after installing opera mini and es file Explorer.
2- over heating in charging bluged and using net for 10 minute.
3- in the screen setting / style/ auto day and night. itsnot working.
4- the lightbar not working even if i enable the light settings.
Hrustus said:
Very nice to see new build But unfortunately I'll have time to play with it in this or next weekend :/
@sgspluss do you know why Magisk don't work on previous builds? M2 is no longer supported by Magisk or it's just fixable in the next builds?
Click to expand...
Click to collapse
Sadly its not fixed, just test it now on myself and magisk not working, do you know any version where its working befor?
hooooossamq said:
after a test i notice these bugs:
1- laging so much after installing opera mini and es file Explorer.
2- over heating in charging bluged and using net for 10 minute.
3- in the screen setting / style/ auto day and night. itsnot working.
4- the lightbar not working even if i enable the light settings.
Click to expand...
Click to collapse
Are they also present in builds befor?
Sent from my athene using XDA Labs
sgspluss said:
Sadly its not fixed, just test it now on myself and magisk not working, do you know any version where its working befor?
Click to expand...
Click to collapse
Unfortunately no, but maybe somebody else remember version. Hmmm... Actually I am not sure that Magisc was working on LineageOS or on Ressurection ROM...
sgspluss said:
Sadly its not fixed, just test it now on myself and magisk not working, do you know any version where its working befor?
Are they also present in builds befor?
Sent from my athene using XDA Labs
Click to expand...
Click to collapse
the lag is much more in your bulid..light bar was working in BEAT 2.
style day and night bug was present in BETA 2..
i was test ALPHA 4 before.every thing working of the bug i say before expact the light bar.and its the most smoth version.. its lagy.. but most smother than all
About problem with magisk, we are also unable to install the magisk manager will look into it whats the reason.
About lags and bugs its strange because i am using same sources, as you can read.
If Something not working logs are helpfull otherwise it takes more time to figure out whats wrong.
What you can do about lags, install supersu from lingeage 14.1 (currently the one from lineage 15.1 and magisk are broken), go into your build.prop, search ro.config.low_ram=true, remove this line and safe build.prop, now restart your phone and test if lags are better.
Sent from my athene using XDA Labs
sgspluss said:
What you can do about lags, install supersu from lingeage 14.1 (currently the one from lineage 15.1 and magisk are broken), go into your build.prop, search ro.config.low_ram=true, remove this line and safe build.prop, now restart your phone and test if lags are better.
Click to expand...
Click to collapse
and here goes my report (very early report, i will add more information)
1-) without gapps, there is some frame dropping in animations and recent apps section (with or without android go mode) but it is same as beta 2, but a bit slower than 8.0 versions. i wonder is there a huge change under the hood between two versions
2-) no lag present in bootanimation, that's unexpected
3-) front camera video works
4-) dark mode works just fine
summary: our device can't handle gapps, that's what i see here. there are minimal frame droppings. also rom is odexed sadly
Just invest some minutes about the magisk problem, seems that we are not compatible yet or never was. But you can send the developer logs, he will look into it, it has nothing to do with rom, lucky me at this point.
About the .odex files that seems to be normal, also can be found on other devices, so there i can not do anything.
Also flashed Alpha4 doesnt be smoother its just uses more animations and some more graphic things related to not using go optimization, also takes more ram, because of not using go optimization so this will be preserved also in the future.
Sent from my athene using XDA Labs
sgspluss said:
Just invest some minutes about the magisk problem, seems that we are not compatible yet or never was. But you can send the developer logs, he will look into it, it has nothing to do with rom, lucky me at this point.
About the .odex files that seems to be normal, also can be found on other devices, so there i can not do anything.
Also flashed Alpha4 doesnt be smoother its just uses more animations and some more graphic things related to not using go optimization, also takes more ram, because of not using go optimization so this will be preserved also in the future.
Click to expand...
Click to collapse
go optimization is better for our device for sure, but this recent apps lag holds me back. but without go and using microg, rom holds up pretty good actually.
As written bevor try to remove ro.config.low_ram=true from build.prop and tell me if this problems you faced will be fixed. All other go optimizations are not changeable manually.
If this will solve the problem, will remove it for future builds, thats fixed for all.
Sent from my athene using XDA Labs
sgspluss said:
As written bevor try to remove ro.config.low_ram=true from build.prop and tell me if this problems you faced will be fixed. All other go optimizations are not changeable manually.
If this will solve the problem, will remove it for future builds, thats fixed for all.
Click to expand...
Click to collapse
as i said before, i am using rom with low_ram=false, and there is less lag compared to go enabled mode.
hello
Me too "low_ram=false" make my m2 less laggy
Thank you for your work
EXPERIMENTAL BUILD
First off this wouldn't be possible without mikeNG, TheMuppets, LineageOS team
I'm just the cook
Devices supported: R7f, ONLY
Do not flash this rom on any other R7 variants. It will brick the device
What works:
Unknown
Haven't tested it fully. All basic functions seem to be in working order.
Will update 'What works / doesn't ' later on.
What doesn't:
Camera issue - Sometimes the camera's color appears to be inverted. Switch HDR on/off fixes it.
Installation notes
Clean install required!
Perform a full wipe when coming from 14.1/15.1
Downloads:
LineageOS 16.0 for Oppo R7f
[Gapps -> ARM ->9.0]
*Don't use the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.1-0 or higher)
Be aware. It's a initial release. Do not expect everything to be working flawlessly. Do make a full backup prior of installing
If you're not fully comfortable/sure about installing an Experimental release than please don't. I'm not responsible for any harm done
**Reserved**
Temp: Please do report any device specific issues
Very good. I will try los16 soon
Holy **** you guys are amazing! After all this time you're still making updates for the Oppo R7 series! Really impressed.
I have an Oppo R7 Plus myself. Any word on if that'll be supported some time as well?
I've tried los 16.0
no meaningful bugs.
overall, I like it very much.
work
1. Cas vooc works
2. Dt2w works
3. The battery saving display is not red
4. Wifi, hotspots work
5. The cellular network feels more stable
Not work
1. Bluetooth sometimes doesn't work
2. Showing download and upload speeds do not work
3. The camera sometimes errors if hdr is on
The rest is quite satisfied with the performance of los 16.0. if there is less and more it will be notified later.
Cmiiw
Thank you very much
Hello I am just a cook as well (just a diff one) but here is an update!
md5sum: https://drive.google.com/open?id=1x1UVAq7mPKUud9iGis4Nyo4o_5x0UBuT
zip: https://drive.google.com/open?id=1jcR2kkAHBewxSdsqs2YNZTaW-RCqITGS
rmb to update if any device-speicific bugs appear
ph03nae said:
Hello I am just a cook as well (just a diff one) but here is an update!
md5sum: https://drive.google.com/open?id=1x1UVAq7mPKUud9iGis4Nyo4o_5x0UBuT
zip: https://drive.google.com/open?id=1jcR2kkAHBewxSdsqs2YNZTaW-RCqITGS
rmb to update if any device-speicific bugs appear
Click to expand...
Click to collapse
if it's more stable. I will try as soon as possible. thank you
ph03nae said:
Hello I am just a cook as well (just a diff one) but here is an update!
md5sum: https://drive.google.com/open?id=1x1UVAq7mPKUud9iGis4Nyo4o_5x0UBuT
zip: https://drive.google.com/open?id=1jcR2kkAHBewxSdsqs2YNZTaW-RCqITGS
rmb to update if any device-speicific bugs appear
Click to expand...
Click to collapse
I've tried your update. everything went smoothly. haven't found a bug. only internet speed can be moved from center to right ??
@ph03nae,
Great to see that you also cooked a v9.0! Do I understand correctly that everything works in your version, including bluetooth and the camera?
eximiusnl said:
@ph03nae,
Great to see that you also cooked a v9.0! Do I understand correctly that everything works in your version, including bluetooth and the camera?
Click to expand...
Click to collapse
I've tried it and used it until now. the camera and bluetooth are running well. haven't found a bug.
That's great!
Here's another update!
md5sum: https://drive.google.com/open?id=1avYrsAHwaNnl2ZJQeiKXf1WU1IHUyYud
zip: https://drive.google.com/open?id=1ohuu8j-zSuvcW7w8CZaIBGx0NPQ0e1Ux
Hi ppl, here's another update!
zip: https://drive.google.com/open?id=1I3nvdnSHWaiYnLlOfAOD_7biEbBBOVEr
md5sum: https://drive.google.com/open?id=13i3E3holmHzN4bJLvwmZDYFktrwiVVo2
enjoy
MAC addresse wrong
Thank you very much!
Yesterday I tried this ROM. Unfortunately, my device's MAC address was always rusty. 02: 00: 00: 00: 00:00. I did it with the latest TWRP program but I also tried the 3.2.1 recommended by you. If the original ColorOs returned, it was good again. I've always done a full wipe. What can I do wrong?
@ph03nae,
Thanks for the update!
What version of GApps do you use? I used the full version before, but since the LineageOS 16 release is bigger, I wonder whether it will fit.
eximiusnl said:
@ph03nae,
Thanks for the update!
What version of GApps do you use? I used the full version before, but since the LineageOS 16 release is bigger, I wonder whether it will fit.
Click to expand...
Click to collapse
For lineageOS 16, I have been using the mini version of GApps instead of the full version because an error sometimes occur saying that there is not enough space for the GApps full version installation. Hope this helps!
@ph03nae,
I followed your advice and also used the mini version of the GApps and installation went flawless.
I noticed that the Pixel Launcher does not work, so you have to use Trebuchet.
I also noticed that battery life is way better than with Android 8.1 !
Thanks for your work, the phone really works fine again.
Could someone please advise me how I can tell if I have an OPPO rplusf or an OPPO rplusg. I live in Australia. Thanks in advance
eximiusnl said:
@ph03nae,
I followed your advice and also used the mini version of the GApps and installation went flawless.
I noticed that the Pixel Launcher does not work, so you have to use Trebuchet.
I also noticed that battery life is way better than with Android 8.1 !
Thanks for your work, the phone really works fine again.
Click to expand...
Click to collapse
You're welcome! (But just to give credit to those who actually work on the code see https://github.com/LineageOS?utf8=✓&q=oppo&type=&language= )
Also, for the issue regarding Pixel Launcher, this is a fix I used (https://forum.xda-developers.com/android/apps-games/pie-pixel-stuff-t3846138) After flashing both zips according to the given instructions, the pixel launcher app can also be updated separately using .apk files.
---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------
mvjh01 said:
Could someone please advise me how I can tell if I have an OPPO rplusf or an OPPO rplusg. I live in Australia. Thanks in advance
Click to expand...
Click to collapse
Hi, you should be able to access this information by going into settings --> about and find a field for the device ID (or something similar) if you are on the stock rom.
ph03nae said:
You're welcome! (But just to give credit to those who actually work on the code see https://github.com/LineageOS?utf8=✓&q=oppo&type=&language= )
Also, for the issue regarding Pixel Launcher, this is a fix I used (https://forum.xda-developers.com/android/apps-games/pie-pixel-stuff-t3846138) After flashing both zips according to the given instructions, the pixel launcher app can also be updated separately using .apk files.
---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------
Hi, you should be able to access this information by going into settings --> about and find a field for the device ID (or something similar) if you are on the stock rom.
Click to expand...
Click to collapse
Thanks very much for your help but I have no such field or anything similar plus I had already looked through all 'about phone' settings. I've just tried installing this ROM via the instructions but Project Spectrum fails every time
mvjh01 said:
Thanks very much for your help but I have no such field or anything similar plus I had already looked through all 'about phone' settings. I've just tried installing this ROM via the instructions but Project Spectrum fails every time
Click to expand...
Click to collapse
Correct me if im wrong but I think only the oppo r7g version has Project Spectrum available.