Just a sneak preview of what I've started working on. Nowhere near being even remotely ready for public consumption though. Hopefully I've have something more usable a month from now.
{
"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"
}
So HTC doesn't need to provide kernel source code ?
Sent from my HTC 10 using XDA-Developers mobile app
george241312 said:
So HTC doesn't need to provide kernel source code ?
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
They do, but I've started with a prebuilt kernel.
Saw this thread and started crying. Am on a Verizon LG G4. Jumping back to Tmob soon and hopefully the 10. But seeing your thread made me wonder how non stock ROMs would handle the encryption on whatever partitions. Sorry if dumb question will be new to HTC. Have been on Sammy for 5 phones now. Thanks!
Sent from my VS986 using XDA Premium 4 mobile app
Does this mean we'll have CM soon? Will it be as painful to develop on as the Galaxy series?
if you guys get aosp running ill buy this device. nice work.
Status Update
I've continued my work on porting CyanogenMod to this device, and have made significant progress. A usable release will still be a while away though.
You can watch my progress here:
https://github.com/sultanqasim/android_device_htc_pme
https://github.com/sultanqasim/android_vendor_htc_pme
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
I haven't yet gotten to trying to get the RIL or fingerprint sensor working, and there are obvious things yet to be done on them. They are on my to-do list for this week. I also plan on looking into certain issues with source built SDM libraries (I'm currently using prebuilt sdm libs to workaround the issues with rendering layers).
For the camera, I've fixed the obvious types of issues (missing symbols and dependencies) though it isn't working right now. How much effort it will take to fix is hard to predict. If anyone would like to try fixing the camera, any assistance would be welcome.
Audio is the big roadblock. HTC has a history of messing with audio hardware, and this device is no exception. HTC used a similar combination of rt5501 and tfa9897 (like) amplifiers for the M7, M8, M9, and A9 (and maybe other devices). A bunch of other devices from other manufacturers also use similar amplifiers. People may recall a lot of time and effort going into fixing audio on these devices, particularly on the original One M7. The subsequent devices in the family all built on work put into the M7.
For this device, HTC switched to a new amplifier, the TFA9888, and dropped the rt5501. The TFA9888 is a very new chip, with no public documentation (other than an uphelpful short data sheet) or available drivers. Thus, I will need to do a lot of fresh original reverse engineering to build a custom amplifier HAL. This will be a time consuming process. I'm waiting for kernel sources so that I can build a kernel with special logging to see what the stock ROM does to configure the amplifier. I will then try to understand and mimic the operation of the stock HAL. I will also see if I can obtain documentation and/or drivers through other means.
Sneak Preview Build
For the morbidly curious, I've uploaded my latest test build. I do not recommend flashing it. As described in the previous post, critical functionality, such as audio, RIL, and camera are broken. If you're still curious and don't depend on your device being functional, you can try this build.
Flashing instructions:
In TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
In TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
Flash CM13, and optionally gapps
Reboot
If it gets stuck on the boot animation for over 10 minutes, you can try going back to TWRP, and then using it to zero out your userdata partition (run cat /dev/zero > /dev/block/bootdevice/by-name/userdata for a few minutes). After zeroing out userdata, try to boot CM13. If it bootloops without getting to the boot animation, hold Vol+ and Vol- together to enter the booloader menu, go back into TWRP, and reformat userdata as ext4 again. It should boot after doing this.
Once again, I don't recommend flashing this. This is very broken pre-alpha quality software. I am not responsible for rendering your device inoperable.
Download link: http://www.mediafire.com/download/980dvfvlu7zdzjx/cm-13.0-20160516-UNOFFICIAL-pme.zip
At least kernel source is out now, so you can start working on that .
Wow, that's incredible. Thanks for your hard work!
Also, the CAF source from which the HTC kernel is based is this: https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.18/?h=LA.HB.1.3.1_rb1.11
(in case you didn't have it already)
EDIT: As identified in logcat -
Code:
05-10 12:33:51.073 1901 2282 I Adreno : QUALCOMM build : 4d8478c, I7b6ba47bd6
05-10 12:33:51.073 1901 2282 I Adreno : Build Date : 02/09/16
05-10 12:33:51.073 1901 2282 I Adreno : OpenGL ES Shader Compiler Version: XE031.07.00.01
05-10 12:33:51.073 1901 2282 I Adreno : Local Branch : mybranch18178856
05-10 12:33:51.073 1901 2282 I Adreno : Remote Branch : quic/LA.HB.1.3.1_rb1.11
05-10 12:33:51.073 1901 2282 I Adreno : Remote Branch : NONE
05-10 12:33:51.073 1901 2282 I Adreno : Reconstruct Branch : NOTHING
Looking forward to this mind you I'm quite happy with sense ui
Captain_Throwback said:
Also, the CAF source from which the HTC kernel is based is this: https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.18/?h=LA.HB.1.3.1_rb1.11
(in case you didn't have it already)
EDIT: As identified in logcat -
Code:
05-10 12:33:51.073 1901 2282 I Adreno : QUALCOMM build : 4d8478c, I7b6ba47bd6
05-10 12:33:51.073 1901 2282 I Adreno : Build Date : 02/09/16
05-10 12:33:51.073 1901 2282 I Adreno : OpenGL ES Shader Compiler Version: XE031.07.00.01
05-10 12:33:51.073 1901 2282 I Adreno : Local Branch : mybranch18178856
05-10 12:33:51.073 1901 2282 I Adreno : Remote Branch : quic/LA.HB.1.3.1_rb1.11
05-10 12:33:51.073 1901 2282 I Adreno : Remote Branch : NONE
05-10 12:33:51.073 1901 2282 I Adreno : Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
Kind of surreal that we still see commits from Linus Torvalds.
Ajfink said:
Kind of surreal that we still see commits from Linus Torvalds.
Click to expand...
Click to collapse
Well, yeah kinda. But he is being sponsored by the Linux Foundation so he can work full-time on improving Linux and he still is the Big Daddy of Linux kernel.
Who's Linus Torvalds? Man... That name is ancient founder of Linux....
request a audio hal from htc? reverse engineer is meh but hey if you can get it to be 100% to stock then why not.
camera hal would be nice to look at too given the crappness of CyanogenMod Camera app no idea if it improve over Snap but hey would nice to see the progress, also I never own a HTC device are the bootloader unlock by default ? what is S-OFF etc
Love how fast HTC gets kernel source out. Can't wait to see the progress of CM. Thanks mate your work is greatly appreciated!
Sent from my HTC 10 using Tapatalk
Captain_Throwback said:
At least kernel source is out now, so you can start working on that .
Click to expand...
Click to collapse
That's great to hear. I had been checking their site every couple days but had no idea when it would come out. I'll be at it this weekend. HTC stripped comments from a lot of the kernel as usual, though I'm prepared with a script I wrote a while back to add back stripped comments.
EDIT: My stock kernel with git history and comments added back is now up: https://github.com/sultanqasim/android_kernel_htc_msm8996/commits/stock_1.21.617
OK. I'm SUPER lost in this,i heard that if you wiped the data partition you lost signal permanently??and is there a fail-safe like Odin??I know this might be the wrong forum but I really want some light on this if you don't mind sharing
Awesome work dude cant wait till it becomes usable.= :good:
Related
{
"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"
}
TripNDroid kernels for the HTC Endeavoru
Introduction:
The kernel released in this topic is a true 3.1.10 kernel based of the latest nVidia Tegra reference source. Please keep this in mind when using my kernel. This kernel isnt in any way related to HTC, neither to sources released on htcdev. This kernel -does- include stuff from HTC tough, for example camera, mhl and parts from the usb drivers. This was the first kernel builded from scratch and i hope you enjoy this as much as i do. A long the way more HTC stuff will be removed and my own stuff will be introduced to replace it. For the most important thing was (and is) that the "core" is completely my own work. With core i mean the power supply board file. From now on the Endeavoru will run on static regulators and not switched gpio regulators, for those who dont know much stuff about developing, this means that the power supply system is 1:1 compatible with the Linux mainline kernels. The advantage of this speaks for it self offcourse.....
Features:
- True 3.1.10 kernel
- Tegra reference pinmux support (w.i.p.)
- Linux mainline compat. power supply
- True Jelly Bean kernel
- Custom hardware drivers
- Fully unlocked speedo, sku, skuid as per Tegra ref.
- GPU OC 520mhz
- Synchronisation Framework
- Much more!
The list above will be updated along the road.
Tegra ref. pinmux
This gives us the possibillity to disable hardware pins or put them in low power mode when they are not used by the One X mainboard. As you can guess, without knowledge of hardware its extremely hard to configure them correctly. The major difference is that HTC just connects pins by let the mainboard choose where to connect them. Search for RSVD in last_kmsg from 2.6.39.4 and you know why we need the Tegra ref. method here lol.
For now the kernel will most likely only work on Jelly Bean or ICS AOSP roms. There will be support for HTC Sense based roms. It could be working allready on HTC Sense but i didnt test them so i only guarentee a working kernel on AOSP roms. If you want to try it on Sense just repack them and give it a go.
Synchronisation Framework
Android Synchronisation framework enables the framework for synchronization between multiple drivers. Sync implementations can take advantage of hardware synchronization built into devices like GPUs.
Installation:
- Download zip file and place it on youre sdcard
- Extract boot.img from the zip file
- Flash the boot.img manually via "fastboot flash boot boot.img"
- Go into recovery and flash the downloaded zip there
- Reboot
- Enjoy the TripNDroid Mobile Engineering kernel!
Downloads:
Jelly Bean AOSP:
http://tripndroid.bindroidroms.com/TripNDroid_Unleashed_3.1.10-022A.zip
http://www.tripndroid.com/downloads/kernel/3.X/Kernel-3.1.10-022A.zip
ICS AOSP:
see Jelly Bean AOSP
HTC Sense:
unavailable
Old kernel:
If you have issues you can downgrade youre kernel here:
EXP AOSP 031:
http://tripndroid.bindroidroms.com/TripNDroid-endeavoru-jb-031-exp.zip
STABLE AOSP 021:
http://tripndroid.bindroidroms.com/TripNDroid-endeavoru-jb-021.zip
Source:
https://github.com/TripNRaVeR
Credits:
Special thanks to show-p1984 for teaching git and providing information
BinDroid for providing webspace
is this the same kernel used with your jb 005 rom?
Is this one included in your ROM? And would you consider it stable?
DarkNe0441 said:
Is this one included in your ROM? And would you consider it stable?
Click to expand...
Click to collapse
Yes this version is stable, and yes this is included with my 005 release. Only this kernel will get more updates then my rom seeing i almost work daily at my kernel. My rom will contain always the latest version with each update ofc. Now you just have the option the update earlier :silly:
Thanks for your awesome work mate ...
Cool. Cool cool cool.
Is it possible to uv/uc??
Trip, I'm still having slow music playback when screen-off. Attached last kmsg.
http://db.tt/K0uRd3Ah
I also tried cranking the minimum clock to 340 but problem still there.
EDIT:Scratch that, seems better now after setting the 340 minimum.
Tapatalked from my HOX
Another awesome development by a great developer. Will definitely keep a watchful eye on this one. Using your rom, and it will be nice to have a complete package with your kernel as well.
Now that you are working on a standalone kernel. Will you be able to uncap the gpu like faux and kohlk did? Just very curious.
Code:
E/WifiHW ( 419): Supplicant not running, cannot connect
E/WifiHW ( 419): Supplicant not running, cannot connect
E/WifiStateMachine( 419): Failed to setup control channel, restart supplicant
D/CommandListener( 184): Setting iface cfg
D/CommandListener( 184): Trying to bring down wlan0
E/wpa_supplicant( 4773): Could not set interface wlan0 flags: Invalid argument
E/wpa_supplicant( 4773): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 4773): wlan0: Failed to initialize driver interface
D/Beautiful Widgets(4110100)( 1635): WidgetRefreshService
D/dalvikvm( 1635): GC_CONCURRENT freed 1543K, 73% free 3407K/12288K, paused 11ms+1ms, total 29ms
D/dalvikvm( 1635): WAIT_FOR_CONCURRENT_GC blocked 4ms
E/WifiHW ( 419): Supplicant not running, cannot connect
E/WifiHW ( 419): Supplicant not running, cannot connect
i can't activate my wifi, i'm on the cm10 preview 8 rom from tbalden, and wanted to try your kernel, i flashed the boot.img, erased cache and flasched the modules!
What do you think, can I build/compile the kernel anytime form source (i.e. when I see a fix/commit that I must have asap ^^), or is that too risky and should I wait for your "official" kernel built?
And to make it easier to coordinate that "build-it-yourself", could you mention the last included commit (hash) in the changelog of your provided built? Thanks
Rycon33 said:
Trip, I'm still having slow music playback when screen-off. Attached last kmsg.
http://db.tt/K0uRd3Ah
I also tried cranking the minimum clock to 340 but problem still there.
EDIT:Scratch that, seems better now after setting the 340 minimum.
Tapatalked from my HOX
Click to expand...
Click to collapse
I also having this issue....but I manage to solve it by re-install the rom.... :victory:
forgot to mention that I'm using poweramp for my music.
Just tried this kernel, no luck. Wi-Fi is very slow. I tried with Trip's 005
Trip
phone doesn't seem to charge using the 002 kernel using with 005 ROM.
vickysud said:
Trip
phone doesn't seem to charge using the 002 kernel using with 005 ROM.
Click to expand...
Click to collapse
Guess why he posted to use the new boot.img 005 ?? Flash 005 and you are good to go
n3ocort3x said:
Guess why he posted to use the new boot.img 005 ?? Flash 005 and you are good to go
Click to expand...
Click to collapse
check this out
Trip himself suggested to use updated kernel sadly this kernel has battery charge problems where as kernel with 005 ROM doesn't
http://forum.xda-developers.com/showpost.php?p=29435454&postcount=1121
Using kernel 002 phone is charging for me, although it's getting warmer than usual while being charged.
For me no charging issues either, will give the charger port max power in next release
TripNRaVeR said:
For me no charging issues either, will give the charger port max power in next release
Click to expand...
Click to collapse
Lol at max power. Just hope it doesn't explode.
Sent from my HTC One X using xda premium
Trip
Phone is charging but very slowly takes almost 20min or more to increase a %.
{
"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
Xperia ZL/ODIN/C6503 CYANOGENMOD 11 LINARO/SABERMOD WEEKLY BUILDS
Weekly Build 20140422 is ONLINE
Build/Sync Date: April 22 0xh:xx GMT+1 Lisbon
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.10.0 201404 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.3 201404 toolchain
FEATURES
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
sqlite fsync hack by dorimanx
white kk UI
CHANGELOGS
(check build/sync date and compare)
http://www.cmxlog.com/11/odin/
http://changelog.bbqdroid.org/#/odin/next
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 16 "Petra" x64 3.11.10)
HOMEPAGE
http://infectedbuilds.net
DONATIONS NEEDED
if you can, please make a small donation... not for my work, 'cause this is a hobby for me, but to keep website and dedicated server up and running, so i can deliver fast and unlimited downloads, and host the builds.
thank you all,
regards.
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
latest linaro arm-eabi-4.10.0 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.3 toolchains to compile ROM code
Special Thanks
CyanogenMod Rom Dev Team
{
"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"
}
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod 11 for the Xperia ZL/odin.
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.8.3 14.03 (kernel code) & boosted-tc arm-linux-androideabi 4.8.3 14.03 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
Looks good, I'll try it out later and report findings.
Will try exactly after two weeks.
Sent from my C6502 using xda app-developers app
Using this ROM now. however i am facing a problem. where touch response stops. Only reboot using key helps to make it work again
coolrevi said:
Using this ROM now. however i am facing a problem. where touch response stops. Only reboot using key helps to make it work again
Click to expand...
Click to collapse
i also faced this but only on lockscreen
quick inquire:
how many users of the samsung i9505/jflte are in this thread?!
just press thanks.
Been using this for about a week or so, pretty good so far.
Testing !!!
When installing the (any)CM11 based rom, I did have a LTE connection, could send/receive SMS but no internet on LTE Mobistar (Belgium).
After some googling, I found apns-conf.xml in the /system/etc/ folder. I checked the values for internet and MMS.
These are the correct values for the /system/etc/apns-conf.xml.
There is no username or password and for internet there is no proxy or port. And there is a PAP authenticationtype.
<apn carrier="Mobistar MMS" mcc="206" mnc="10" apn="mms.be" mmsc="http://mmsc.mobistar.be" mmsproxy="212.65.63.143" mmsport="8080" authenticationtype="PAP" type="mms"/>
<apn carrier="Mobistar Internet" mcc="206" mnc="10" apn="mworld.be" authenticationtype="PAP" type="default,supl"/>
Please adapt it in your builds, so that I don't have every-time when installing the nightly builds, I have to fix it manually
Where is recovery?
suleymanovemil8 said:
Where is recovery?
Click to expand...
Click to collapse
sources issues.. try official. happens the same thing.
regards.
infected_ said:
sources issues.. try official. happens the same thing.
regards.
Click to expand...
Click to collapse
Same on official
Hi boss is app2sd working on this rom?
Sent from my Xperia ZL using Tapatalk
imkentoy said:
Hi boss is app2sd working on this rom?
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
never tried it. you have to find out by yourself ..
infected_ said:
sources issues.. try official. happens the same thing.
regards.
Click to expand...
Click to collapse
Hey,
is your CWM recovery gone, too? Any idea in how to get it back?
lordsony said:
Hey,
is your CWM recovery gone, too? Any idea in how to get it back?
Click to expand...
Click to collapse
flash a boot.img from a build before 20140508 ..
infected_ said:
flash a boot.img from a build before 20140508 ..
Click to expand...
Click to collapse
cool, thank you! I suppose I should flash it via fastboot?
infected_ said:
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
why i can't write in fastboot mode? is there important if in settings was checked the debugging mode? my ZL is soft brick, I can flash just with flashtool, but after each flashing i have no erros but still remain the first version of ftf before bricked. do you know why it cannot replace it? pc companion do the same, no errors but still not fix my phone.
[BUG FIX] [ Jiayu S3 & Others ] StageFright [LP 5.1] [MT6752 & MT6732 & MT6735]
{
"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 there
On this thread, you'll find the Fix for the Stagefright Bug(s) for the Jiayu S3 LP 5.1 based Roms
It should also work without any issues on others MT6752 /32 based devices, running Lollipop 5.1
Confirmed working on the following MT6752 SoC Devices
Jiayu S3 (dah ! )
iOcean Rock MT6752
ZOPO ZP920
Lenovo K3 Note
Confirmed working on the following MT6732 SoC Devices
UMI Hammer
Elephone P6000
Confirmed working on the following MT6735 SoC Devices
Kingzone N5
Please give feedback, if your using another MT6752 /6732 device
What is the Stagefright bug(s) ?
Read This:
http://www.xda-developers.com/stagefright-explained-the-exploit-that-changed-android/
Which stagefright bugs are patched by this ?
ALL the present StageFright known bugs are patched
CVE-2015-1538
CVE-2015-1539
CVE-2015-3824
CVE-2015-3827
CVE-2015-3828
CVE-2015-3829
CVE-2015-3864
How can i check If im vulnerable ?
Download the Stagefright Detector by: Zimperium INC
--> Play Store
After Patching, should be like this:
How to install?
Make a backup first (just in case) ...
You'll need a custom recovery for LP (TWRP / CWM , etc)
Just flash the JiayuS3_Stagefright_LP5.1_fix_v3.zip
Reboot
For other devices that don't use the mmcblk0p17 as /system partition:
The flash may fail, if that's your case, simply extract all the files, and push via adb to your device.
This was (of course ) compiled from source ...
Download:
Build: v3
https://www.androidfilehost.com/?fid=24052804347811921
Older Downloads
Build: v2
https://www.androidfilehost.com/?fid=24052804347807886
Build: v1
https://www.androidfilehost.com/?fid=24052804347807532
ChangeLogs:
Build v3
Fix Video dec / enc issues
Fix: Other small issues related to MTK's OMX
Build v2
Youtube Videos Decoding, now working
MxPlayer / VLC , etc will decode videos (SW only), HW is still Broken
Build v1
Initial build
Your most welcome, to included this on your Rom(s), this is an severe exploit(s), but, do give credits, and please leave a link to this thread ...
Thanks to:
Zimperium for finding the exploits
CyanogenMod, for providing the commits
Myself for compiling it
DerTeufel1980 & Jiayu Deutschland, for all the help
Cheers
Thank you
Awesome man! Thanks for your effort.
Feeling much better now
I kind of wonder how the Stagefright Detector by Zimperium INC works though, sure must be clever, not?
Doesn't exactly work on mine. Running official AOSP 5.1 and it created distorted graphics on a game after patching.
Replaced it with original files and it was okay again.
mze1 said:
Doesn't exactly work on mine. Running official AOSP 5.1 and it created distorted graphics on a game after patching.
Replaced it with original files and it was okay again.
Click to expand...
Click to collapse
Yeah unfortunately this happened with me too, Stagefright was of course fixed but so I tried to see a video on youtube and the video was distorted, checked the ones inside gallery same problem. So reverted back to stock files and it worked again.
Rom: 5.1 Unofficial 01072015 with Xposed v72 5.1 (don't know if it matter)
Issue: Distorted graphics
Attached a picture of a video playing in my gallery to give a good idea of what is happening.
The same for me. Bad graphic for all videos, with stock player as well as vlc
Looking into it...
Better Graphics glitches then stagefright
Skickat från min JY-S3 via Tapatalk
Doesn't work on IOcean M6752 - distorted video issue.
---------- Post added at 09:58 AM ---------- Previous post was at 09:39 AM ----------
How to revert back to stock files? I dont have backup.
ask somebody who has got your same rom, to send you the file /system/lib/stagefright.so
Same graphical glitches with P6000 (MT6732).
So if i understand this correctly, it only creates an issue on videos as i have only tried a game after applying the patch.
The graphical issue was indeed on a video part within the game. I haven't tested it further and directly replaced those files.
I may be wrong though.
I suppose those glitches are caused by using "aosp" mediatek sources as base, instead of modified customer sources.... We (more superdragonpt than me) are trying to fix it. No promises though.
DerTeufel1980 said:
I suppose those glitches are caused by using "aosp" mediatek sources as base, instead of modified customer sources.... We (more superdragonpt than me) are trying to fix it. No promises though.
Click to expand...
Click to collapse
^^ This
Plus, The Mediatek OMX and the 64arm makes it harder to properly check.
New patch Build:
ChangeLogs:
v2
Youtube Videos Decoding, now working
MxPlayer / VLC , etc will decode videos (SW only), HW is still Broken
It was a long night, getting around this... it's already 12h here... need to sleep
cheers
@superdragonpt So we are going to have a V3 that completely fixes the issue?
Metrino said:
ask somebody who has got your same rom, to send you the file /system/lib/stagefright.so
Click to expand...
Click to collapse
and (#1) /system/lib64/stagefright.so
and (#2) all 57 other /system/lib*/stagefright*.so
Dior DNA said:
and (#1) /system/lib64/stagefright.so
and (#2) all 57 other /system/lib*/stagefright*.so
Click to expand...
Click to collapse
I checked modified files, I found just stagefright.so was modified.
I think even stagefrighthw.so could be touched by superdragonpt's patch, others are probably called from the previous ones, so they does not affect the issue and are not patched.
Metrino said:
I checked modified files
Click to expand...
Click to collapse
look in the zip archives and its updater-script
First version touched just libstagefright.so, under lib and under lib64 folder
Second version touched all files you mentioned.
cryptonent was asking how to revert from first version patch
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Important:
Official build are now available
What's working :
Boots
Wifi
Audio ( Record and Playback )
What's partially working:
Bluetooth
Video Playback
Camera
Camcorder
Flash
GPS
Nfc
What's not working :
SELinux enforcing
HWcomposer is buggy(rendering is made by gpu in order to avoid artifacts)
Instructions :
Download the latest build and gapps
Reboot to recovery
Do all wipes
Flash the latest build and gapps
Downloads :
Latest Build : LineageOS-16
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Sources
linckandrea - Repositories
Andrea Pucci. linckandrea has 46 repositories available. Follow their code on GitHub.
github.com
Credits :
LineageOS Team
if you want to offer me a coffee or anything else check this
reserved
nice, i never thought we would get another android pie attempt, Ill try soon
I just installed it and it works fine, but pls add sources. I already found them, but you should add them in your post.
and ofc thanks for all the effort you made @linckandrea
I am the first person to soft brick my N9 ig. To be fair, I installed Magisk, dirty flashed, ran undecrypted, everything not ideal circumstances, but here are ramoops as it now only boots to recovery saying "RescueParty".
cant share logs due to size limitations in xda, pastebin and hastebin. If you have a telegram acc it would make things easier.
Thanks for releasing 16.0. While I did have a bootable 16.0 back in March 2021, I couldn't fix the hwcomposer problems.
With your 16.0 build, Clash Royale completely froze and locked up after 15 minutes (roughly 5 games, each is 3 minutes long). adb logcat shows running low on memory? I can play same game on 15.1 with no problems.
After getting the logcat, I tried to start Clash Royale again, but the entire device locked up again and I get the same System UI isn't responding that I reported earlier.
Code:
5585 06-23 18:42:44.198 264 355 E ActivityManager: ANR in com.android.systemui
5586 06-23 18:42:44.198 264 355 E ActivityManager: PID: 661
5587 06-23 18:42:44.198 264 355 E ActivityManager: Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 1. Wait queue head age: 6085.9ms.)
5588 06-23 18:42:44.198 264 355 E ActivityManager: Load: 4.6 / 2.01 / 1.62
5589 06-23 18:42:44.198 264 355 E ActivityManager: CPU usage from 0ms to 22509ms later (2021-06-23 18:42:21.538 to 2021-06-23 18:42:44.047):
Here's the output of top from adb shell. BTW, there's no rush to look at this. I know you are still fine tuning your changes locally and on github. Thanks.
Code:
Tasks: 198 total, 1 running, 197 sleeping, 0 stopped, 0 zombie
Mem: 1879792k total, 1306832k used, 572960k free, 816k buffers
Swap: 786428k total, 158840k used, 627588k free, 553684k cached
SirRGB said:
I just installed it and it works fine, but pls add sources. I already found them, but you should add them in your post.
and ofc thanks for all the effort you made @linckandrea
Click to expand...
Click to collapse
source link added(i missed when created the thread but they were already present(with git history) on my github account)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
retiredtab said:
Thanks for releasing 16.0. While I did have a bootable 16.0 back in March 2021, I couldn't fix the hwcomposer problems.
With your 16.0 build, Clash Royale completely froze and locked up after 15 minutes (roughly 5 games, each is 3 minutes long). adb logcat shows running low on memory? I can play same game on 15.1 with no problems.
Click to expand...
Click to collapse
due to broken hwc display composition is made by only the gpu
(this means that every heavily gpu apps will perform bad as the gpu does all the work)
retiredtab said:
Here's the output of top from adb shell. BTW, there's no rush to look at this. I know you are still fine tuning your changes locally and on github. Thanks.
Code:
Tasks: 198 total, 1 running, 197 sleeping, 0 stopped, 0 zombie
Mem: 1879792k total, 1306832k used, 572960k free, 816k buffers
Swap: 786428k total, 158840k used, 627588k free, 553684k cached
Click to expand...
Click to collapse
Would you say that @linckandrea 's v16 release is more up-to-date than your v15.1 release?
Obviously v16 > v15.1 but I wonder if the functionality is the same?
Having used both releases, would you say this one is more stable than your own?
Your last update for v15.1 was as of June 13, 2021.
Does this v16 update include both the security updates AND the hardware fixes in yours?
Such as improving the GPU rendering, etc?
I would assume that because it's v16, it would include all previous fixes from v15.1? Am I wrong in thinking this?
Or is the hardware decoding of video or say, YouTube; still an issue?
Also related/unrelated to these ROMs, have either of you (or other users reading) had the issues with the NEXUS9 related to crashing prior to installing any ROM; and then having those issues be resolved with the installation of this or any other ROMs? I'd like to know if this is a hardware-based or software-based issue.
If my NEXUS9 is still going to crash, I don't think it's worth my time installing any ROMs, etc.
Will there be any more development of Android 9? I am asking because your repos werent updated since June 24th and I dont know of anyone else, that is working on it...
SirRGB said:
Will there be any more development of Android 9? I am asking because your repos werent updated since June 24th and I dont know of anyone else, that is working on it...
Click to expand...
Click to collapse
i'm actually using a custom build of los15.1 of my nexus 9,
the hwcomposer bug is due by outdated display blobs(there's no tegra k1 device that has an oem pie build(this means that this issues will never be resolved))
so it is worth fixing the remain bugs when the performance will sucks no matter what?
probably not
and yes even on los17.1/18.1 display blobs would be the same
I currently run los16 just to try it and it runs quite nicely (only minor bugs e.g. livedisplay broken like A8, permissive selinux, ?fullscreen issue?). Ig dirty flashing was the reason it didnt work properly back then... Just wanted to note: a lot of people are using your build, so thanks for all your work.
LineageOS Statistics
stats.lineageos.org
When i power off, the device is in some sort of sleep not true power off. I power off and there was 50% battery and when i switch it on weeks later battery is depleted. I noticed this with another rom i installed before. Any way around this ? To get a true power off. Apart from this, the rom works great.
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?
hastebin
I use your dt, kt and vt
SirRGB said:
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?
Click to expand...
Click to collapse
I'm not an expert in compiler flags, but if I'm understanding this correctly ...
Code:
In file included from external/tinycompress/compress.c:57:
In file included from bionic/libc/include/fcntl.h:95:
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error) {
it's complaining that 'O_TMPFILE' is not declared. You can bypass this by removing line 7 at
https://github.com/LineageOS/android_external_tinycompress/blob/lineage-16.0/Android.bp#L7
The "-Werror" according to
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
"Make all warnings into errors."
So by removing that flag, it should compile now.
Hm, I understand, but sadly it didnt work. In the end I nuked all flags and removed the out folder, but nothing changed...
Try renaming the external/tinycompress/Android.bp file to Android.bp.old as a test. That won't build that library at all then. You may also have to grep through the device/htc/flounder directory for instances of libtinycompress and comment it out.
I haven't tried to build 15.1 yet so I don't know if I will be affected by this or it's just in the 16.0 tree or it's specific to your build environment.
SirRGB said:
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?
hastebin
I use your dt, kt and vt
Click to expand...
Click to collapse
You used the wrong kernel branch... Pick lineageos-16...