https://plus.google.com/+ParanoidAndroidCorner/posts/RbrCXacYqES
TL;DR ?? Here is the interesting part
We are also announcing that with the help of Sony and their Open Devices Project we will be able to support all 22 Xperia devices on the SonyXperiaDev GitHub Instance. This initial Sony release is for the Shinano family, but the Rhine, Yukon and Kitakami platforms are expected to follow shortly. This is really exciting news for us and it allows us to give you the Android experience we all love on a much wider range of devices.
Click to expand...
Click to collapse
Konstantinosj77 said:
https://plus.google.com/+ParanoidAndroidCorner/posts/RbrCXacYqES
TL;DR ?? Here is the interesting part
Click to expand...
Click to collapse
ok but where is their github tree...when searching, i cannot find anything on github for AOSPA nor Paranoid Android, only AOSParadox, which i guess is not the same
quake73 said:
ok but where is their github tree...when searching, i cannot find anything on github for AOSPA nor Paranoid Android, only AOSParadox, which i guess is not the same
Click to expand...
Click to collapse
Sources are not up yet,only the OP devices kernels and trees https://github.com/AOSPA
Also their manifest is broken,already tried
Konstantinosj77 said:
Sources are not up yet,olnly the OP devices kernels and trees https://github.com/AOSPA
Also their manifest is broken,already tried
Click to expand...
Click to collapse
i admit, this is a little off the subject but...any idea of how to build a caf rom? or any idea of how to make sense of the caf tree names? I tried to compile some 'frankenstein' roms, combinations of caf+aosp but without success...i mentioned aosparadox, there is some guy, TheQuiche that supposedly 'maintains' the device tree for eagle for aosparadox but he only appears once in every 2-3 months. Have you seen/tried to build? I have tried but failed miserably every time Is there any point in trying anything with caf? I've read that it is the purest source/kernel for qcom devices
and this for example: https://github.com/AOSP-CAF? any idea if it is worth trying? (i already tried but failed )
quake73 said:
i admit, this is a little off the subject but...any idea of how to build a caf rom? or any idea of how to make sense of the caf tree names? I tried to compile some 'frankenstein' roms, combinations of caf+aosp but without success...i mentioned aosparadox, there is some guy, TheQuiche that supposedly 'maintains' the device tree for eagle for aosparadox but he only appears once in every 2-3 months. Have you seen/tried to build? I have tried but failed miserably every time Is there any point in trying anything with caf? I've read that it is the purest source/kernel for qcom devices
and this for example: https://github.com/AOSP-CAF? any idea if it is worth trying? (i already tried but failed )
Click to expand...
Click to collapse
I just checked his sources...there is no point in trying,he uses the same sony sources as everybody. (1.2.2 kernel branch)
Konstantinosj77 said:
I just checked his sources...there is no point in trying,he uses the same sony sources as everybody. (1.2.2 kernel branch)
Click to expand...
Click to collapse
yeah, i actually managed to build but got only a blank screen on my phone....and yes, i noticed his kernel, from sonyxperiadev. Tried to blindly guess and used some of the caf kernels, some went well but, black screen again.
quake73 said:
yeah, i actually managed to build but got only a blank screen on my phone....and yes, i noticed his kernel, from sonyxperiadev. Tried to blindly guess and used some of the caf kernels, some went well but, black screen again.
Click to expand...
Click to collapse
Let's wait for AOSPA
Maybe is the begingin of the stable roms on the xperia m2!
Enviado desde mi Xperia M2 Aqua usando Tapatalk
Sources are up!
https://github.com/AOSPA for builders sync the marshmallow branch. Still needs some edits thought....
Working/not working: Same as every other MM rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Konstantinosj77 said:
https://github.com/AOSPA for builders sync the marshmallow branch. Still needs some edits thought....
Working/not working: Same as every other MM rom
Click to expand...
Click to collapse
I admit the defeat this time, you got me this time, I was trying to build this one, too.
quake73 said:
I admit the defeat this time, you got me this time, I was trying to build this one, too.
Click to expand...
Click to collapse
Hahaha well i won't upload the build cause it's a bit hacky...let's wait for the official one
Konstantinosj77 said:
https://github.com/AOSPA for builders sync the marshmallow branch. Still needs some edits thought....
Working/not working: Same as every other MM rom
Click to expand...
Click to collapse
Srsly I prefer a fully working Lollipop build than an unstable Marshmallow...
I will try to build and test this rom when i get home
I hope they could make something stable
Enviado desde mi Xperia M2 Aqua usando Tapatalk
quake73 said:
I admit the defeat this time, you got me this time, I was trying to build this one, too.
Click to expand...
Click to collapse
Can you upload that when your build is over ?
vinz156 said:
Can you upload that when your build is over ?
Click to expand...
Click to collapse
sure, you can find it here (pa_eagle-6.0.1-20160627.zip) but wait first, it is uploading now, should be there in less than an hour (my upload is slow).
https://1drv.ms/f/s!AgjGxeMsjY4Ky3eAIsZX5og3_rkf
quake73 said:
i admit, this is a little off the subject but...any idea of how to build a caf rom? or any idea of how to make sense of the caf tree names? I tried to compile some 'frankenstein' roms, combinations of caf+aosp but without success...i mentioned aosparadox, there is some guy, TheQuiche that supposedly 'maintains' the device tree for eagle for aosparadox but he only appears once in every 2-3 months. Have you seen/tried to build? I have tried but failed miserably every time Is there any point in trying anything with caf? I've read that it is the purest source/kernel for qcom devices
and this for example: https://github.com/AOSP-CAF? any idea if it is worth trying? (i already tried but failed )
Click to expand...
Click to collapse
Hi there!
We (the AOSParadox team) were indeed working on bringing CAF to eagle. A friend of mine owned the device and i found the stock ROM really bad and the available ROM options at the time (i don't know how it is today.) were lacking aswell so for a while we were working on it but then my friend dropped his device and it broke, thus we didn't work on it anymore.
PS: I'm TheQuiche
Related
Hello.
Right now as I am typing this message, the source files for Cyanogenmod 11.0 are being synced to my computer, and I am trying to make a build for our device. I have a few questions though that would affect my development:
1) On a guide I was reading (http://forum.xda-developers.com/showthread.php?t=2060017), it says "MAKE SURE YOUR PHONE IS ON OFFICIAL LATEST CYANOGENMOD ROM". But trebon isn't officially supported. Would it still work if I put in trebon, or do I need to do other steps?
2) Do I have to code something after downloading the Android sources, or do I just have to build it instantly?
Any help on these would be greatly appreciated. I'm willing to create a ROM for our device if I can get the help I need, since I have nothing better to do anyway.
Thanks!
Liam D. said:
Hello.
Right now as I am typing this message, the source files for Cyanogenmod 11.0 are being synced to my computer, and I am trying to make a build for our device. I have a few questions though that would affect my development:
1) On a guide I was reading (http://forum.xda-developers.com/showthread.php?t=2060017), it says "MAKE SURE YOUR PHONE IS ON OFFICIAL LATEST CYANOGENMOD ROM". But trebon isn't officially supported. Would it still work if I put in trebon, or do I need to do other steps?
2) What's the minimum RAM requirement for Cyanogenmod? If OmniROM or AOKP is lighter, I would switch sources.
2) Do I have to code something after downloading the Android sources, or do I just have to build it instantly?
Any help on these would be greatly appreciated. I'm willing to create a ROM for our device if I can get the help I need, since I have nothing better to do anyway.
Thanks!
EDIT: After doing some research, I switched to AOKP instead of Cyanogenmod 11 because it is lighter. Apparently, according to the Cyanogenmod 11 Google+ post, they require a minimum of 512MB RAM, which our phone does not have. Syncing right now is AOKP source code. If some people would like to help me make a build, I would appreciate it if you would answer the questions above.
Click to expand...
Click to collapse
me :good:.. i want to help
Thanks, Androidoo.
To anyone who wonders, I got some help from @streambinder and right now I just finished downloading the Cyanogenmod 11 sources. I'll be whipping up a new build within the week and would love to have other users test it out for me (if I ever get to finish it). I've been using TheWhisp's sources for Cyanogenmod 11 for Galaxy Mini and when the ROM I built goes live, I'll be sure to upload it here and give him credits for his sources.
I need a little help here, possibly from @giugiu19 @smartandroidtech @streambinder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried Googling for answers but I got no luck with this. Can you help me out with that?
Thanks!
I think you must refer this guide as it is much more detailed.
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
If you have any question then you can ask the OP of that guide.
kk9999gada said:
I think you must refer this guide as it is much more detailed.
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
If you have any question then you can ask the OP of that guide.
Click to expand...
Click to collapse
Thanks kk9999gada! I'll take a look at that.
Success! I've managed to make a build with no errors.
I'll be testing this now, and if all goes well, expect a release soon!
Liam D. said:
Success! I've managed to make a build with no errors.
I'll be testing this now, and if all goes well, expect a release soon!
Click to expand...
Click to collapse
grea work man excited:fingers-crossed:
Androidoo said:
grea work man excited:fingers-crossed:
Click to expand...
Click to collapse
Thanks!
Right now, everything works fine, except for WiFi. I'm still trying to figure it out, and it looks like I might have to change kernels.
Liam D. said:
Thanks!
Right now, everything works fine, except for WiFi. I'm still trying to figure it out, and it looks like I might have to change kernels.
Click to expand...
Click to collapse
which kernel u tried?
Androidoo said:
which kernel u tried?
Click to expand...
Click to collapse
I tried the SpeedMod kernel, the phone boots fine but WiFi doesn't work. I tried Triprex's kernel, and the phone would not respond at all.
Liam D. said:
I tried the SpeedMod kernel, the phone boots fine but WiFi doesn't work. I tried Triprex's kernel, and the phone would not respond at all.
Click to expand...
Click to collapse
kernel problem.. cn u try for logcat any devs cn help this may be or u trying somethig more>??
Androidoo said:
kernel problem.. cn u try for logcat any devs cn help this may be or u trying somethig more>??
Click to expand...
Click to collapse
It's finals week in the university, so I'm putting it on hold. On Friday I will resume development. I have a logcat ready here and I'm studying it to figure out the problem. I'm 99% sure this is a problem with the kernel, probably a broken module.
If anyone's interested, I have a working copy of the ROM, but WiFi and Camera doesn't work yet. If you want I can upload the ROM. I'm doing a project for school right now. After I finish (in about 1 more hour), I'll upload some screenshots of my ROM.
Here are the screenshots of the ROM I built:
Liam D. said:
Here are the screenshots of the ROM I built:
View attachment 2980442 View attachment 2980443
Click to expand...
Click to collapse
GREAT WORK BUDDY PLEASE START A THREAD its jus perfect with new theming engine
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Liam D. said:
It's finals week in the university, so I'm putting it on hold. On Friday I will resume development. I have a logcat ready here and I'm studying it to figure out the problem. I'm 99% sure this is a problem with the kernel, probably a broken module.
If anyone's interested, I have a working copy of the ROM, but WiFi and Camera doesn't work yet. If you want I can upload the ROM. I'm doing a project for school right now. After I finish (in about 1 more hour), I'll upload some screenshots of my ROM.
Click to expand...
Click to collapse
Start A thread and take as much time you need:fingers-crossed:
Thanks.
Uploading a build right now (the one where camera and WiFi doesn't work yet). I'm also downloading a new kernel build to my PC to experiment with (kernel 3.4.x from TheWhisp's jenad build).
{
"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"
}
Team Exodus and our ROM are an open-source project coded by professional level developers with additional support from the community, focusing on improved versions of common features and improvements found in the open-source community while bringing new improvements and original coding with the highest standards.
Be rooted w/ a custom recovery
Download EXODUS Rom & Gapps for your device and move them to your phone
Reboot to Recovery
Wipe (Full wipe if coming from another Rom)**
Flash the Rom
Flash the Gapps**
Reboot to System
Setup and Reboot System
These directions are not necessary after the first install if you use the Exodus Updater, included in the ROM. It can notify you of updates, download, and install them for you automatically.
**This is automated if coming from a previous Exodus build (Dirty Flashing).
EXODUS - official: http://www.exodus-developers.net/exodus-5.1/
2.16 built by me: https://mega.nz/#!eAkwTAiL!JHYMtIc5fgLzl37wBleQTcg05sYqm5PSHQqOh5BIe-4
GApps: Any 5.1.x GApps of your choice
Rom source: https://github.com/TeamExodus
Gerrit: http://exodus-developers.net:8000
For additional support, info, and updates please join us in the official Google+ community:
https://plus.google.com/communities/106801227383087889476
Website:
http://www.exodus-developers.net/
Crowdin project:
Help us with translating to support your native language!
Thank you to all the members, contributors, and maintainers on the Exodus Team. Please
see our source for an unabridged list of contributions, authorship, and cherry-picks.
If you would like to thank us for our hard work or help support server costs you can do so here:
MartinRo (Server hosting)
Primedirective (Team Leader / Main developer)
Some videos created by savadam (all credits to him):
XDA:DevDB Information
TeamExodus rom, ROM for the HTC One S
Contributors
phoenixita, Martin_Ro, The whole Exodus Team
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.15 HBOOT
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-06-11
Last Updated 2015-07-13
I'm still alive
Can make for 2.16 ?
Winstarshl said:
Can make for 2.16 ?
Click to expand...
Click to collapse
Unfortunately I can't cause rom is semi-closed source and it's being built by a buildbot.
I can't believe no one tried it...is the One S community dead?
No Camera
sib_rock said:
No Camera
Click to expand...
Click to collapse
You can download it from the play store.
https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera&hl=it
phoenixita said:
I can't believe no one tried it...is the One S community dead?
Click to expand...
Click to collapse
I tried building several Roms. Many failed. Don't think i've tried this one.
Sent from my One S using XDA Free mobile app
mmarkvoort said:
I tried building several Roms. Many failed. Don't think i've tried this one.
Sent from my One S using XDA Free mobile app
Click to expand...
Click to collapse
Give it a shot. Go into dev settings and watch out for the morph feature. You can choose if you want to use exodus features, cm features or stock aosp features. 3 roms in one.
The rom is snappy as it is barebones. But I have this problem, Can't connect to camera. Some times it works fine (Camera).
By the way, used Google Camera.
letsurock said:
The rom is snappy as it is barebones. But I have this problem, Can't connect to camera. Some times it works fine (Camera).
By the way, used Google Camera.
Click to expand...
Click to collapse
That is the general camera bug present in all LP ROMs. The CM fix for it may have not be included
Rapier said:
That is the general camera bug present in all LP ROMs. The CM fix for it may have not be included
Click to expand...
Click to collapse
I don't experience it in RR and Candy5.
letsurock said:
I don't experience it in RR and Candy5.
Click to expand...
Click to collapse
There was a fix but not all ROMs have it. Candy and RR have the fix
Sent from nowhere over the air...
letsurock said:
The rom is snappy as it is barebones. But I have this problem, Can't connect to camera. Some times it works fine (Camera).
By the way, used Google Camera.
Click to expand...
Click to collapse
I just found this camera fix on play store. Don't know, if it really works, I haven't installed it myself yet. Maybe you want to give it a try.
EDIT: was a bit curious, so I tried it out. For me it does not work, the app doesn't even open. So I guess this won't help.
derkleinebroicher said:
I just found this camera fix on play store. Don't know, if it really works, I haven't installed it myself yet. Maybe you want to give it a try.
EDIT: was a bit curious, so I tried it out. For me it does not work, the app doesn't even open. So I guess this won't help.
Click to expand...
Click to collapse
The fix is via a commit (or more) that should be cherry-picked to be included in the build. Don't think that an app can solve the bug.
Sent from nowhere over the air...
Rapier said:
There was a fix but not all ROMs have it. Candy and RR have the fix
Sent from nowhere over the air...
Click to expand...
Click to collapse
Thats pleasing to hear. Therefore, exodus is not recommended as daily driver as of now.
Btw, thank OP for the ROM and making it official, looking forward to use it after fix. Now back to RR latest.
letsurock said:
Thats pleasing to hear. Therefore, exodus is not recommended as daily driver as of now.
Btw, thank OP for the ROM and making it official, looking forward to use it after fix. Now back to RR latest.
Click to expand...
Click to collapse
I will say this to Dave. Have you tried morph mode?
@Rapier could you link mi this fix? Was it made in the device tree or in some other project?
phoenixita said:
I will say this to Dave. Have you tried morph mode?
@Rapier could you link mi this fix? Was it made in the device tree or in some other project?
Click to expand...
Click to collapse
I really don't know. It was just that at some point, it was fixed in CM and some other CM based ROMs have picked it as well. But I don't know the commit(s) for that. I don't even remember when it was but it is some time ago, I think before even 5.1 was out. That camera/flashlight bug was since Android 5.0.x.
Rapier said:
I really don't know. It was just that at some point, it was fixed in CM and some other CM based ROMs have picked it as well. But I don't know the commit(s) for that. I don't even remember when it was but it is some time ago, I think before even 5.1 was out. That camera/flashlight bug was since Android 5.0.x.
Click to expand...
Click to collapse
Will investigate. Anyway exodus is based on cm the commit should be in here.
phoenixita said:
I will say this to Dave. Have you tried morph mode?
@Rapier could you link mi this fix? Was it made in the device tree or in some other project?
Click to expand...
Click to collapse
Nopes (didn't try Morph Mode). Just tested the basic functionality and reverted back to RR.
A Better Camera good work for me
MTK Development TeamDear Devs and Users from Pure XL community
For a year I was trying to get Android 6.0 working on our devices but without luck. There were always problems with booting.
Now I want to work in a bigger team so I've started a new GitHub organisation called MTK Development Team.
About the project
Why?
The goal is to make a working (booting!) Android 7.1 custom ROM. With the power of the team it will be much easier than working on my own.
Custom ROMs
You know the best custom ROM to start a big adventure with was CyanogenMod. Since it will not be supported (read more here) we will be focusing on Lineage OS.
{
"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"
}
Supported devices
As you may know BLU Pure XL is just rebranded Gionee Elife E8 which is also the same phone as Allview X2 Soul Xtreme - there is no difference in making custom ROMs for them. Personally, I have the X2 Xtreme, that is why there are repos mostly for this phone. There is android_device_mediatek_mt6795-common repo which is the base for mentioned phones.
Keep in mind that these repos are still in the development and may be incomplete but I will update them as soon as possible.
Being part of the team
Just before application
It would be very helpful if you had Allview X2 Soul Xtreme/BLU Pure XL/Gionee Elife E8 on your own or had an access to it. Then you could test every changes you have made to the repos on your own device.
Application
If you wold like to be a part of the MTK Development Team, please fill this form:
https://goo.gl/forms/fkMUGcv3JtKEF71Y2
I would like to invite every developer or savvy user who would like to help me making this real.
Useful links:
MTK Development Team GitHub
Lineage OS - GitHub
That's pretty much it. Thank you for your attention and I hope some of you would like to take a part in this project. This thread will be updated.
Thanks!
I would like to send special invitation to:
@Moyster
@zrgravity
@root-expert
@acheron1502
Well thanks for the invitation Bem. I actually don't own any of these phones so I don't know if i can help that much.
I can contribute to the project if you want though.
Chris
root-expert said:
Well thanks for the invitation Bem. I actually don't own any of these phones so I don't know if i can help that much.
I can contribute to the project if you want though.
Chris
Click to expand...
Click to collapse
I know you have helped very much with CM12.1. If you feel you can help there's already pending invitation to the GitHub organisation.
Thanks
i'm following this project
i want to see how you workaround for blobs as mt6795 hasn't ever got a nougat build
andrea210701 said:
i'm following this project
i want to see how you workaround for blobs as mt6795 hasn't ever got a nougat build
Click to expand...
Click to collapse
I know it will be hard af but I want to try. I bought this phone because of decent specs so I can't loose my chance.
andrea210701 said:
i'm following this project
i want to see how you workaround for blobs as mt6795 hasn't ever got a nougat build
Click to expand...
Click to collapse
Well that's not going to be a big problem we will probably be missing a lot of symbols but we can always shim our libs and get past those errors.
root-expert said:
Well that's not going to be a big problem we will probably be missing a lot of symbols but we can always shim our libs and get past those errors.
Click to expand...
Click to collapse
fair enough,even tho this won't make a magically stable cm14.1
andrea210701 said:
fair enough,even tho this won't make a magically stable cm14.1
Click to expand...
Click to collapse
Yeah that's true I'm afraid
What seems to be the problem? Have you tried to build cm12?
Sent from my Life Max using Tapatalk
vampirefo said:
What seems to be the problem? Have you tried to build cm12?
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
cm12.1 (non booting)
tbirdguy said:
cm12.1 (non booting)
Click to expand...
Click to collapse
Bringing that tree forward, and applying lineage 13 or lineage 14 patches, should be able to compile a workable rom.
Sent from my LIFE X8 using Tapatalk
vampirefo said:
Bringing that tree forward, and applying lineage 13 or lineage 14 patches, should be able to compile a workable rom.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
Feel free to get it up and working! you will be a gentleman and a scholar and a god among men!
tbirdguy said:
Feel free to get it up and working! you will be a gentleman and a scholar and a god among men!
Click to expand...
Click to collapse
Send me the phone, I will take a crack at it.
Sent from my LIFE X8 using Tapatalk
vampirefo said:
Send me the phone, I will take a crack at it.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
cant do that; but if you want to build i will be your official tester... im fluent in the device, its the rom cheffing i suck at... been around since days of cm5 on Nexus one... but have yet to compile a working rom (last thing I actually compiled was PASCAL code in high school circa 1992)
tbirdguy said:
cant do that; but if you want to build i will be your official tester... im fluent in the device, its the rom cheffing i suck at... been around since days of cm5 on Nexus one... but have yet to compile a working rom (last thing I actually compiled was PASCAL code in high school circa 1992)
Click to expand...
Click to collapse
No, I don't build on any device I don't own.
Good luck to you all.
I will be releasing LineageOS 13 for Blu Life Max in the next few days, then work on Lineage 14.
Sent from my LIFE X8 using Tapatalk
ignore
vampirefo said:
No, I don't build on any device I don't own.
Good luck to you all.
I will be releasing LineageOS 13 for Blu Life Max in the next few days, then work on Lineage 14.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
Well thanks for being a stuck up douche, even if i cant benefit directly, I appreciate your doing what you do to help who you can!
TheLastCanadian said:
ignore
Click to expand...
Click to collapse
Your comment was very rude and uncalled for, you sound like a spoiled child.
This community nor myself owns you anything crybaby.
Sent from my Life Max using Tapatalk
vampirefo said:
Your comment was very rude and uncalled for, you sound like a spoiled child.
This community nor myself owns you anything crybaby.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
Oh, ok, I tried to take the high road in this, but if you want to be an asshole:
Heavy pressure on a guy to send a $350 phone to you so you can "have a go at it." Forgive me if that sounds extremely suspicious. THAT was what I thought better of and wrote "ignore" for. So go **** yourself.
IUNI U3 KERNEL 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"
}
Code:
Disclaimer:
It's still under development.
I waive all liability... Thermonuclear war will happen whatever you use this kernel or not.
Feel free to contribute, share, participate, post or help it would make me great pleasure!
Introduction
This project aim to develop a kernel for the IUNI U3 able to turn on the latest version of Android and to meet the challenge proposed by IUNI.
The purpose of this post is:
Highlight the development progression.
Log the errors and bugs remaining to be fixed.
Transmit solutions of issues encountered to help those who will have the same kind of error to fix it.
Exchange and learn all together and find out how to fix those bugs.
Click to expand...
Click to collapse
Sources code
Official kernel source: https://gitlab.com/iuni/u3/tree/master/gionee/alps_drv/kernel
Kernel source: https://github.com/Abdess/android_kernel_iuni_msm8974
Device tree & other: https://github.com/Abdess?tab=repositories
Click to expand...
Click to collapse
How-to compile it
Just follow this GUIDE and this README
Click to expand...
Click to collapse
Good to know
About official source code:
The original CAF kernel source code is downloadable HERE
Common drivers are located at gionee/alps_drv
IUNI U3 specific drivers are located at gionee/project/NBL8910A
IUNI U3 Mini specific drivers are located at gionee/project/NBL8905A
The repo use a special script to compile Android with specific "GN_FLAGS" who're located into the gn_project folder, those flags are added on-the-fly and are not integrated into the kernel.
Click to expand...
Click to collapse
State
Working:
Everything
Semi-working:
Nothing
Not working:
Nothing
?:
Nothing
Click to expand...
Click to collapse
Logs
XDA:DevDB Information
IUNI U3, Kernel for all devices (see above for details)
Contributors
Abdess76, Angel_666, feroxxx, alecuba16, 蝴蝶剑
Source Code: https://github.com/Abdess/android_kernel_iuni_u3
Kernel Special Features:
Version Information
Status: Alpha
Created 2017-08-31
Last Updated 2018-01-29
Changelog:
September 4th, 2017:
Kernel:
*Internal storage works
Logs:
dmesg
recovery
Click to expand...
Click to collapse
Original dmesg for comparison
Old changelogs:
August 31, 2017:
*Initial release
Because ADB doesn't works and I can't do an UART, the only way to extract logs of the compiled TWRP recoveryimage is to go into ADVANCED -> TERMINAL and type:
Code:
dmesg
Then take pics of important part of the log
Log pics are uploaded HERE
Log pictures:
1:
2.
3.
4.
5.
6.
7.
8.
Click to expand...
Click to collapse
Miscs
How it looks:
Nice work, might have a play with this over the weekend, although my skills are pretty limited.
Hi! Any news? seems that there no new step forward
Hi, anyone here who want to sell his IUNI U3?
I like it very much but left sim Slot for 4G is not
working and no one can repair.
Hello. That there on the kernel?
I thought the release of the code source would boost developers but it seems nobody wants to work on the U3 anymore, too bad
Hi,
Sorry for not giving any news for a long time, I sorely missed free time.
The kernel is now 100% functional on Android N. There are still some small issues and optimisations to fixes before everything is perfect.
It remains to complete the device tree and blobs to be finally ready.
The project was able to move forward with the help and support of several developers who generously gave their time to help and answer questions:
- @Sultanxda : The kernel is entirely based on his work, and moreover he helped me with all questions and technical problems.
- @feroxxx : It is thanks to him that LineageOS 14.1 is almost fully working on IUNI U3
- @nathanchance : Thanks to his documentation and availability to answer to the questions on the forum he has expanded my knowledge and awareness of security.
- @jerpelea and @GalaticStryder : They helped me to understand some technical and theoretical aspects of the kernel.
And of course also to all those who contributed to all these open-source projects without whom this project would never have emerged.
Thanks, thanks and thanks and thanks again!!!!!
Qidamin said:
Thanks, thanks and thanks and thanks again!!!!!
Click to expand...
Click to collapse
:highfive:
I'll have to update the thread with more details and more regularly, like a log. The goal is to highlight the path used in the development of the kernel. The mistakes made, by which means they were solved.
The intention is to provide answers to questions that a person might ask if he wants to undertake a similar project.
When starting a project for the first time, there is often this famous stage of vast questioning and gray area. With a large amount of documentations, wondering where to start, where to go. Reading the practical experience of others could be a shortcut in the learning journey and have an idea where to start and where to go.
Soon there will be a key to the surprise that IUNI was talking about.)))
Hi, Abdess. When to expect firmware release?
Zewius21 said:
Hi, Abdess. When to expect firmware release?
Click to expand...
Click to collapse
Most likely when it's ready.
Zewius21 said:
Hi, Abdess. When to expect firmware release?
Click to expand...
Click to collapse
Hi, Zewius21. I am sorely lacking time to work on it.
It may take time, unless someone wants to join me in the development.
Zewius21 said:
Soon there will be a key to the surprise that IUNI was talking about.)))
Click to expand...
Click to collapse
They released their surprise and a secret message.
mikeysteele said:
Most likely when it's ready.
Click to expand...
Click to collapse
Haha, exactly.
Ok the kernel source code for LOS 15.1 is available here: https://github.com/Abdess/android_kernel_iuni_msm8974/tree/lineage-15.1
There's a weird issue, everythings looks to works fine (adb, storage, brightness)... into the log... However the display doesn't works but it's acting like working.
It looks like I've to check the MDSS drivers and device tree.
Hi @Abdess76, I just tried building Lineage 14.1 off your sources. It built OK but it doesn't boot . It appears ADB isn't running despite building with user-debug and I can't seem to find any logs in /proc/last_kmesg. Any suggestions as to what I'm doing wrong?
Thank you for adding me to contributors,but how do you find my id in xda?Besides,How is the kernel going?
mikeysteele said:
Hi @Abdess76, I just tried building Lineage 14.1 off your sources. It built OK but it doesn't boot . It appears ADB isn't running despite building with user-debug and I can't seem to find any logs in /proc/last_kmesg. Any suggestions as to what I'm doing wrong?
Click to expand...
Click to collapse
Good question, we can see this together on hangout.
蝴蝶剑 said:
Thank you for adding me to contributors,but how do you find my id in xda?Besides,How is the kernel going?
Click to expand...
Click to collapse
I do not remember how I did to find you. lol
I had to make another break because of the work. Everything works however there is always this display bug. I must find the cause.
https://github.com/Abdess/android_k...mmit/3e0db6ef96f5beac8504d6b8bf157b1c38248425
Abdess76 said:
Good question, we can see this together on hangout.
Click to expand...
Click to collapse
Ok sounds good, although we'll have to find a time which works coz I'm on the other side of the world to you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Since the moment you decide to read and install stuff from this post your phone warranty is lost. Im not responsible of any damages or whatever happens to your device. All this said enjoy and remember post any bugs you find.
As i have seen PixelExperience here aosp based i wanted to share another AOSP base rom , this time ( more coming for sure....) GZOSP. As far as i have tested ( i do not have much time to test cuz of studies) everything is working. As i know all of you are willing to test it i´ll go to the point.
Download the rom
IMPORTANT - I have used mindthegapps and its working. I havent tested with opengapps so..if you try tell us if its working.
Device tree is from PsyMan ( Thanks a lot for your work ) , kernel is from PsyMan too , Vendor Too .
It works with opengapps too.
Since all is from psyman and pixel experience, what makes this rom different?
Im asking in a curious kinda way, not a condescending one
Does proximity sensor works?
obtuce said:
Since all is from psyman and pixel experience, what makes this rom different?
Im asking in a curious kinda way, not a condescending one
Click to expand...
Click to collapse
With all due respect, devices, kernel and vendor might be from PsyMan but the whole rom source is different so... Totally different rom. As alike and as different as any other aosp rom out there I guess...
albertoduqe said:
With all due respect, devices, kernel and vendor might be from PsyMan but the whole rom source is different so... Totally different rom. As alike and as different as any other aosp rom out there I guess...
Click to expand...
Click to collapse
I think he meant what features does this Rom have, since you have not explained like the other posts?
abdullamu said:
I think he meant what features does this Rom have, since you have not explained like the other posts?
Click to expand...
Click to collapse
Is this a Validus type setup rom?
Ultraman666 said:
Is this a Validus type setup rom?
Click to expand...
Click to collapse
It´s from the same team that has tesla , validus and etc...Mostly AOSP roms use gzosp repos so...it can be said that this rom was meant to be a base for the rest of aosp based rom.
EvangelineDEV said:
It´s from the same team that has tesla , validus and etc...Mostly AOSP roms use gzosp repos so...it can be said that this rom was meant to be a base for the rest of aosp based rom.
Click to expand...
Click to collapse
Exactly
Sorry to go off topic but Evangeline: would you care to tell me if you plan to release here your Atomic builds? I have it compiled and working too but would be glad to forget about them if a real dev goes for it
albertoduqe said:
Exactly
Sorry to go off topic but Evangeline: would you care to tell me if you plan to release here your Atomic builds? I have it compiled and working too but would be glad to forget about them if a real dev goes for it
Click to expand...
Click to collapse
Yeah , i have planned to do it . Rhong told me to release it here too so i´ll do it. I´m going right now to build a new one with some fixes i did (remove some lag and better battery use) so if you wish to wait ill finish building it asap.
EvangelineDEV said:
Yeah , i have planned to do it . Rhong told me to release it here too so i´ll do it. I´m going right now to build a new one with some fixes i did (remove some lag and better battery use) so if you wish to wait ill finish building it asap.
Click to expand...
Click to collapse
Uh no problem Wasn't planning on releasing just yet anyway as I'm working on Xenon and updating Cardinal too and having some build problems there. So if we have your Atomic soon that'd be great. I will try and compile some new one
EvangelineDEV said:
It´s from the same team that has tesla , validus and etc...Mostly AOSP roms use gzosp repos so...it can be said that this rom was meant to be a base for the rest of aosp based rom.
Click to expand...
Click to collapse
Ok I may give it a go then thanks
unfortunately again no proximity
Hen Ry said:
unfortunately again no proximity
Click to expand...
Click to collapse
Well crap
Hen Ry said:
unfortunately again no proximity
Click to expand...
Click to collapse
Not easy to implement on an AOSP rom... Needs qcom/audio-caf project from lineage and several things can be broken. Also needs a provisional not merged modification in kernel, otherwise you get soft reboots from doze...
I am not implementing in Cardinal yet either
Anything new coming to the rom? Like custom tweaks etc?
Ultraman666 said:
Anything new coming to the rom? Like custom tweaks etc?
Click to expand...
Click to collapse
Hahahaa!!!
albertoduqe said:
Not easy to implement on an AOSP rom... Needs qcom/audio-caf project from lineage and several things can be broken. Also needs a provisional not merged modification in kernel, otherwise you get soft reboots from doze...
I am not implementing in Cardinal yet either
Click to expand...
Click to collapse
Actually it's easier then you can think
Psy_Man said:
Actually it's easier then you can think
Click to expand...
Click to collapse
Well I think I have it working for Cardinal so yeah, it can't be that difficult...