Hi guys, I created this thread to ask for help at the port of Cyanogenmod 11 for Optimus L3 II, specifically the E435.
Now this topic will be to discuss how to solve the bugs of this ROM, so soon I'll post it for better development
Follows the Device Tree, Vendor Blobs and the local_manifests.
Device Tree: https://github.com/Caio99BR/android_device_lge_e435
Vendor Blobs: https://github.com/Caio99BR/android_vendor_lge
Kernel: https://github.com/Caio99BR/android_kernel_lge_p715
Local Manifest: https://github.com/Caio99BR/local_manifest
Last releases!
Help?
Is there no one who can help me?
If anyone can help, would appreciate, not just me.
Note: I am now using the kernel of LG L9 II (Varcain) only have to bring the device settings from the old kernel repository (not the boot) for this new repository.
https://github.com/Caio99BR/android_kernel_lge_e435
After reviewing the defconfig found that there was a line in which he says the color depth so I configured RGB565.
Thanks for anyone helping me still.
Caio99BR said:
After reviewing the defconfig found that there was a line in which he says the color depth so I configured RGB565.
Thanks for anyone helping me still.
Click to expand...
Click to collapse
vc ainda esta portando a rom? eu ñ sei mexer muito nessas coisas mas se quiser cobaia eu to aki
@victoraraujo2 in english please?
@victoraraujo2 Use the google translator, i use and also learn a bit more to eat you too.
Translation
@victoraraujo2 Use o Google translator, eu uso e também aprendo um pouco mais comesse você também.
So, thanks @laufersteppenwolf by moving the topic and @victoraraujo2 by being willing to test the ROM
The problem is that time of the kernel does not boot.
Even after alterations, the kernel is not the boot.
I think I'll get the original kernel and the jellybean repo and try to make and give'm doing CM 10.1, 10.2 to 11.
Note: I'm still using TeamHackLG/lge-kernel-Iproj changed.
What your opinions?
fine by me, I just wanted a more pure android because that LG can not stand it..... LG E435
CM 10 or 11
If I try to port the CM10, result bugs and unsupported dual chip.
Now if I carry the CM 11'll have to inspect the original kernel and put the kernel D605 (aka LG Optimus L9 II) which is the KitKat, besides the bugs.
CM 10: 3h or more
CM 11: indeterminate
CWM workers after build from source!
CWM worked after trying to change the original kernel, soon I'll soon be uploading the same and trying to build a ROM
First Help!
Some hint
Code:
target thumb C++: libmemalloc <= hardware/qcom/display-caf/libgralloc/ionalloc.cpp
hardware/qcom/display-caf/libgralloc/ionalloc.cpp: In member function 'virtual int gralloc::IonAlloc::alloc_buffer(gralloc::alloc_data&)':
hardware/qcom/display-caf/libgralloc/ionalloc.cpp:83:18: error: 'struct ion_allocation_data' has no member named 'heap_mask'
hardware/qcom/display-caf/libgralloc/ionalloc.cpp:84:46: error: 'ION_FLAG_CACHED' was not declared in this scope
make: ** [/home/caio/windows/32/Caio_Files/system/out/target/product/e435/obj/SHARED_LIBRARIES/libmemalloc_intermediates/ionalloc.o] Error 1
make: ** Esperando que outros processos terminem.
Probaly fix
Using diff viewer meld together with the repo TeamHackLG/lge-kernel-lproj I'll probably be able to solve most problems
Maybe you can port 4.4 from LG L20?
Probaly
Ops...
Sorry!
In my translation without the translator google, I get to port it to that device, more than the hardware is totally different.
Package Complete: /home/caio/windows/32/Caio_Files/system/out/target/product/e435/cm-11-20141110-UNOFFICIAL-e435.zip
{
"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"
}
Where is download? It will work on e430?
kernel error
Kernel error, last_kmsg log in next post
Log have 7 minutes.
Other log
Black issue.
Probaly kernel
Related
Hi,
i would like to build an .apk from source with eclipse, but when i port the source project of "keyguard", i've got so many errors (1271) so i can't build it !
Anyone know what can i do without correct all errors ? :/
Screenshot:
{
"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"
}
Thank you in advance.
After searching a bit I found the following topic: hxxp://stackoverflow.com/questions/17487777/using-internal-android-classes (can't post clickable links yet).
From your screenshot it looks like you're trying to use "LockPatternUtils" which is part of "internal android classes".
ArcaneHammer said:
After searching a bit I found the following topic: hxxp://stackoverflow.com/questions/17487777/using-internal-android-classes (can't post clickable links yet).
From your screenshot it looks like you're trying to use "LockPatternUtils" which is part of "internal android classes".
Click to expand...
Click to collapse
So what can i do ? :/
Thank you for your answer !
NOTICE: I can upload the keyguard folder if you want more informations
Could you share the project you're trying to compile, the official website if it has one? Please keep in mind that while I'm a developer I'm by no means an expert on Android. I'll give it shot but it's probably not going to do much good.
ArcaneHammer said:
Could you share the project you're trying to compile, the official website if it has one? Please keep in mind that while I'm a developer I'm by no means an expert on Android. I'll give it shot but it's probably not going to do much good.
Click to expand...
Click to collapse
Link with Keyguard (extract it)(I just changed an opacity value compared to the original one in KeyguardViewManager.jar) :
http://www.mediafire.com/download/9h1jo9i9b545zdl/keyguard.zip
AOSB Page:
http://probam.net/
AOSB Github:
https://github.com/AOSB/
Source where i downloaded Keyguard (to download it, i had to download all framework source):
https://github.com/AOSB/android_frameworks_base/tree/kitkat/packages/Keyguard
Thank you for yoru help !
Apparently there is a thread about this project from the developer: hxxp://forum.xda-developers.com/showthread.php?t=2377129
Given the Android.mk in the code tree I think you may require the NDK. Here is a tutorial for how to set this up: hxxp://mindtherobot.com/blog/452/android-beginners-ndk-setup-step-by-step/
I've not done any NDK development, so this goes way beyond my skillset.
Hi friends,
I'm trying to build CM 13 for a ZTE's N918St, an MSM8916-based device. The stock ROM is Kitkat based, so the kernel source ZTE released is for Kitkat (version 3.10.28).
In the process of compilation, there were quite some errors about missing declaration of certain structs and so on when it came to compiling code related to hardware. And I found that these missing things are present in the kernel for Marshmallow from CM. I replaced the header files containing the missing things with the ones from CM's kernel source. The compilation continued but the resulting ROM was not booting. The phone simply returns to RECOVERY after flashing the ROM and restarting. If I replace the boot.img with the boot.img from a working Lollipop based ROM for this device, the phone just stays at the ZTE logo and never continues.
The working Lollipop ROM for this device is ported from a sibling device (N958St) of N918St, which is based on MSM8916 also. Both devices are using the stock kernel which is for Kitkat in this Lollipop ROM. So I guess the same can be done to Marshmallow since some of the missing things are also needed in Lollipop (e.g. the header file MSMCAL_HWDEP.H in INCLUDE/UAPI/SOUND of the kernel source). There must be something I'm missing. Any help please?
Any advice is appreciated. Thank you in advance!!
godspirit00 said:
Hi friends,
I'm trying to build CM 13 for a ZTE's N918St, an MSM8916-based device. The stock ROM is Kitkat based, so the kernel source ZTE released is for Kitkat (version 3.10.28).
In the process of compilation, there were quite some errors about missing declaration of certain structs and so on when it came to compiling code related to hardware. And I found that these missing things are present in the kernel for Marshmallow from CM. I replaced the header files containing the missing things with the ones from CM's kernel source. The compilation continued but the resulting ROM was not booting. The phone simply returns to RECOVERY after flashing the ROM and restarting. If I replace the boot.img with the boot.img from a working Lollipop based ROM for this device, the phone just stays at the ZTE logo and never continues.
The working Lollipop ROM for this device is ported from a sibling device (N958St) of N918St, which is based on MSM8916 also. Both devices are using the stock kernel which is for Kitkat in this Lollipop ROM. So I guess the same can be done to Marshmallow since some of the missing things are also needed in Lollipop (e.g. the header file MSMCAL_HWDEP.H in INCLUDE/UAPI/SOUND of the kernel source). There must be something I'm missing. Any help please?
Any advice is appreciated. Thank you in advance!!
Click to expand...
Click to collapse
Please share with us how to install stock rom in n918st.. Badly need.. This phone stuck on logo after hard reset.. Please help me...
{
"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"
}
- Marhaba Mobile's -
{
"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"
}
What is AOKP?
AOKP stands for Android Open Kang Project. It is a custom ROM distribution for several high-end Android devices. The name is a play on the word kang and AOSP (Android Open Source Project). The name was sort of a joke, but it just stuck, just like our infatuation with unicorns.
We fork the source code of Android that Google puts out in the open with every major version release, and we then add the magical unicorn bytes (read: we add some of the coolest features that are both useful and make your ROM awesome).
With AOKP, you can generally do a lot more with your device than what you could do with the original firmware that came installed on it.
Why AOKP ?
We were waiting for when you'd ask this.
There are a variety of reasons why a hilly billy Android user, on a bright sunny day, would suddenly start using AOKP and loving it.
For one, AOKP is lightweight. Most OEMs provide a heavy UI layer over Android and have loads of bloatware (i.e. apps that not everyone use every day, but you cannot remove because they're "baked in" by default). Since AOKP is built upon vanilla Android source, it has neither of the above.
Also AOKP has features that you will not find on your stock firmware. You can have a multitude of toggles to quickly flip a lot of your phone's settings right at your fingertips, or you can launch apps quickly from any screen using our Ribbons.
You can change almost each and every aspect of the OS, from its looks to the way it functions, with total freedom. And did we tell you, AOKP helps you make tacos?
Flashing Instruction
Copy the downloaded ROM to your phone.
Boot into your recovery
Back up your ROM
Enter recovery
Make a full wipe (system, data, cache, dalvik)
Install the ROM
Install GAPPS package(Micro/nano)
Reboot - the first boot can take up to 5 minutes
Bugs:::
You tell me!
Download links:
ROM: https://drive.google.com/open?id=0B1u3Aa5vykKSRlRxb0xVSEhsRjg
Gapps: http://opengapps.org/
XDA:DevDB Information
AOKP, ROM for the Samsung Galaxy Grand Prime
Contributors
pramod1221
Source Code: https://github.com/AOKP
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 5.1.1
Based On: AOSP
Version Information
Status: Alpha
Created 2017-06-01
Last Updated 2017-06-11
for 530h bro...
devjish said:
for 530h bro...
Click to expand...
Click to collapse
no
just G531H boy
Screenshots
اسماععیل said:
no
just G531H boy
Click to expand...
Click to collapse
lol bro...
Iam asking "when AOKP lanuches for 530h" ??
Update
good rom, the only problem that i have is when i turn on the torch, the phone get freeze . Any solution?
Es una buena ROM. Noté que cuando se conecta el SM G531H a un cable auxiliar de audio la reproducción del audio es de muy mala calidad. No se escucha el audio, solo los instrumentos si se trata de musica. Esto lo he observado cuando se reproducen archivos mp3. No he probado con otros archivos de audio.
Will it work on sm-g531f?
link does not work
Link doesn't work.
Link is dead
{
"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"
}
Project Proposals
Based on AOSP with improvements from many other projects! GApps included! The proposal is to provide the best experience in using a low Android with only basic customizations. Focused on battery stability and fluidity.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, ALREADY INCLUDED
D O W N L O A D
Download ROM
FLASHING STEPS
•Boot to Custom recovery
•Flash Rom
•Format data
•Reboot System
•Once you see bootanimation, Hold the power button to force reboot (To avoid bootloop on first boot)
Android OS version: 11.0.0_r29
Security patch level: March 2021
Source code: https://github.com/AOSPK
Kernel Source: https://github.com/Redmi-MT6768
Build Author: Communos
Awesome,which recovery is suggested,the unofficial TWRP?Cheers!!!
-CALIBAN666- said:
Awesome,which recovery is suggested,the unofficial TWRP?Cheers!!!
Click to expand...
Click to collapse
Yeah
SElinux permissive?
.0.. said:
SElinux permissive?
Click to expand...
Click to collapse
Mhm
Screen shot please
Another room. Thank you for the hard work.
Is there any ROM without GAPPS por only with mircoG?
alasse_cala said:
Is there any ROM without GAPPS por only with mircoG?
Click to expand...
Click to collapse
Sakura project, unofficial lineage OS
eOS
hi, awesome rom,
however i get a bootloop when trying to format an sd card, i had to force shutdown and reboot normally
I just flashed that custom rom 10 minutes ago and it looks clean, love it, thank you for publishing it!
Maybe as additional info: (In my case) The flashing also worked with the PitchBlack Recovery for the Redmi 9 (the unoffical TWRP CN has some touch input issues on my device, I don't know why) from stock MIUI 12 Global.
Edit: OS still runs seemingly stable, but like already in other roms for that device the known issue about the unstable/not working video recording also happened for me here.
Can you pls post a Link without gapps?
When the phone goes into hibernation it does not answer calls..So later it gives a message that they tried to call you ...
help please
Hey
How many posts you write about this issue,one is enough.Believe me,u are not the only one.Cheers!!!
hey you have a solution to this problem???
is this rom abandonned ?
The download link is dead
hi everybody, i want flashing lineageos based custom roms.
twrp recovery is currently available, but unfortunately, a stock android based or lineageos based, custom android roms has not been released. I can't support development because I don't know coding or have no command of these issues. Can you add a list of custom roms under this topic? Thanks everyone
There seems not much, you can limit this device thread to "Development":
{
"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"
}
There are just two, one ROM, one recovery...
systmrrr said:
I can't support development because I don't know coding
Click to expand...
Click to collapse
Excuse my wise words but then perhaps it would have been better to look first what's available (as in custom ROMs) and then buy accordingly.
Sounds tedious but I always crosscheck my buys beforehand with
https://wiki.lineageos.org/devices/
That usually saves you from rare and unsupported/unsupportable devices (like those based on Mediatek SOCs).
Developers will prepare custom roms when source codes are released by manufacturer xiaomi
sedat2934 said:
Developers will prepare custom roms when source codes are released by manufacturer xiaomi
Click to expand...
Click to collapse
Is that right? I thought, they cannot prepare customs before code is released by manufacturer... slight but noteworthy difference, right?
SigmundDroid said:
Is that right? I thought, they cannot prepare customs before code is released by manufacturer... slight but noteworthy difference, right?
Click to expand...
Click to collapse
Custom roms cannot be prepared without releasing the source code. I am impatiently waiting for the day when I will upload custom rom. When will the source code be released?
Poco F4 GT kernel source · Issue #4044 · MiCode/Xiaomi_Kernel_OpenSource
Please open the source code for Poco F4 GT kernel. We need it!
github.com