[Q] [NEED HELP][WIP]Firefox OS for Lg L3 (e400) - Firefox OS Q&A

Hello to all, im trying to port Firefox OS to the LG L3 (e400) phone
From now, i forked various repos of b2g and other to github (http://github.com/kprkpr) (if repos doesnt sync right,try in some hours,and if still occurs,say it please) and with the great help of feherneoh now we can start to modify and build more and great!
Here the alpha builds, a zip for use with cwm https://drive.google.com/open?id=0B6ydSl9VOrADU094c0J0S3dYeUk (Kernel and some fixes by Deeiko )
Steps to build it yourself:
first install dependencies (look here for look at) https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites
Create a folder called firefoxos
Enter to firefoxos folder
Open terminal there (in firefoxos folder)
Commands:
$ git clone https://github.com/kprkpr/B2G.git
$ cd B2G
$ ./config.sh e400
##Maybe the "./config.sh e400" command has to be executed more than one time becuase random errors of download##
$ ./build.sh
And later install the zip that are in /release folder
Maybe there is a error when starts to build of android.config, solution:
create file android.config in /external/wpa_supplicant_8/wpa_supplicant/android.config with this inside:
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_SIM=y
CONFIG_EAP_AKA=y
CONFIG_EAP_PSK=y
CONFIG_EAP_SAKE=y
CONFIG_EAP_GPSK=y
CONFIG_EAP_PAX=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_IKEV2=y
CONFIG_DRIVER_HOSTAP=y
CONFIG_DRIVER_WEXT=y
Click to expand...
Click to collapse
Thanks for reading, I hope that with help we can get full Firefox OS to L3
(This thread of building can help..is for cm9 but it solves some errors for b2g too http://forum.xda-developers.com/showthread.php?t=1980379)
Now editing sources and files to try again, a LOT of thanks and credits to feherneoh!
For now works the touch, ui, music, bt, ril (some) ,and i think gps too. no wifi(doesnt turn on,but in some builds by adb can search wifi,but not connect), no camera(FC), ui big
CAPS by TheMasterMaind
{
"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"
}
Note: Proyect abandoned because I changed my phone months ago,sorry But sources still there,maybe someone can use and make changes and make work better, I would like it

feherneoh said:
Can you try if this one works?
http://d-h.st/2TC
Click to expand...
Click to collapse
WOW, I installed this using CWM and it boots! No wifi, no sim, no camera, ui big and gliched in settings, but it loads photos, no music but videos loads 1 sec.. desktop works
How you did it?!?!?
Edit:Hehe, I flashed my imgs using your boot.img and doesnt work too..Maybe is because you use a zip and I use .img , you you did the zip??

feherneoh said:
I have my own customized source (FoXperia) and I added some stuff from CM, so basically I should be able to build these buggy versions for any CM9 supported devices. I make zips using make otapackage or build.sh (modified)
You should check my sources: https://github.com/feherneoh
Click to expand...
Click to collapse
You are great! Yes, I will view now your sources
Thankssss

feherneoh said:
I have my own customized source (FoXperia) and I added some stuff from CM, so basically I should be able to build these buggy versions for any CM9 supported devices. I make zips using make otapackage or build.sh (modified)
You should check my sources: https://github.com/feherneoh
Click to expand...
Click to collapse
Hi, i were reading your sources (they are great!) And, I was coping, forking and modifying my repos with your repos.. Later I intent to build from my computer with your sources forked..but not build, it builds almost all I think, but it says that has two errors,one relaccioned to Nswindow.o and other of
Out/target/product/e400/obj/DATA/gecko_intermediates/gecko .(it says error 2)
Enviado desde mi LG-E400 mediante Tapatalk

feherneoh said:
make clean, then try again
I use patched gecko, but those patches are for battery/dpi
Click to expand...
Click to collapse
I do that and doesn builds...
Maybe is a problem of system.. I use Lubuntu (Ubuntu) 13.10 64 bits
I repeated the steps using you repository directly
$ git clone https://github.com/feherneoh/B2G.git
$ cd B2G
$ ./config.sh e400
$ ./build.sh
And fails.. same errors Nswindow.o and the other of out/target/product/e400/obj/DATA/gecko_intermediates/gecko ..
How you compiled it¿?
Note: When I start compilng ever tells this before start
"awk: fatal: no se puede abrir el archivo «sdk/files/tools_source.properties» para lectura (No existe el archivo o el directorio)
find: «../../external/apache-http/src/org/apache/http»: No existe el archivo o el directorio
find: «../../external/apache-http/src/org/apache/http»: No existe el archivo o el directorio
find: «../../external/apache-http/src/org/apache/http»: No existe el archivo o el directorio
find: «../../external/nist-sip/java»: No existe el archivo o el directorio
find: «../../external/apache-http/src»: No existe el archivo o el directorio
find: «../../external/libphonenumber/java/src»: No existe el archivo o el directorio"
Is normal??

feherneoh said:
I can still build for e400, but nsWindow.o error appeared for all of the other devices
Click to expand...
Click to collapse
Oh...
My computer continues no building for e400 I tried 5 times erasing the folder and doing ccache --clear ..You have any idea about the nswindow.o error??

feherneoh said:
New file in sources, old file in patches
I'm currently trying to build it with unpatched nsWindow.cpp
Click to expand...
Click to collapse
Oh,oki, if you build right without the patch or anything else, tell me please
Thankss

feherneoh said:
Fixed. 'rm -rf out' then start again with './config.sh e400'
Click to expand...
Click to collapse
Thankss! Now builds without errors

feherneoh said:
Fixed. 'rm -rf out' then start again with './config.sh e400'
Click to expand...
Click to collapse
feherneoh... Your new build of ffos for lg l3 http://d-h.st/INo , and a build I do using your repos..(they are equal builds, same size) and doesnt boot, it passes from lg logo but it doesnt works, it white screen and restarts..
Maybe the fail I view in the reports of the build command that missing b2g files like:
"Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:461: Missing file(s): bin/defaults/profile/prefs.js
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:513: Missing file(s): bin/libnssdbm3.so
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:524: Missing file(s): bin/crashreporter
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:525: Missing file(s): bin/crashreporter.crt
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:528: Missing file(s): bin/crashreporter-override.ini
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:536: Missing file(s): bin/chrome/icons/
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:540: Missing file(s): bin/libomxplugin.so
Warning: /home/kprkpr/firefoxos/B2G/out/target/product/e400/obj/objdir-gecko/b2g/installer/package-manifest:562: Missing file(s): bin/components/DownloadsUI.js"

feherneoh said:
Neither of them works?
Click to expand...
Click to collapse
Only worked your first build of days ago (this: http://d-h.st/2TC ) , but http://d-h.st/INo and the build of mine using your repos, doesnt works..only pass from lg logo and white screen, and then restart..

feherneoh said:
Okay... The update that broke the builds was released since that, so maybe I only have to fix manifests
Click to expand...
Click to collapse
oh..Good luck, I hope you will repair this rare build bug soon

you must be running cm9 on your e400 before attempting this
cd /path/to/your/directory/
git clone https://github.com/feherneoh/B2G
cd B2G
./config.sh e400
if you want a specific version like 1.1 and not the latest, change the last line to -
Click to expand...
Click to collapse
Code:
BRANCH=v1-train ./config.sh e400
adb pull /system backup-e400/system
cd /path/to/your/directory/B2G/
./build.sh
feherneoh, any chance of some stable builds being put up, ffos is currently on v1-train / v1.1.0 and your builds are creating v1.4.0 see https://wiki.mozilla.org/Release_Management/B2G_Landing
it would be worth running at the same speed as Mozilla so that if bugs are encountered we know it's device specific and not because we are bleeding edge.
all cm9 vendor lge e400 files are here: https://github.com/cybojenix/android_vendor_lge_e400
I'm going to have a look at this in the morning.
Edit: successfully built 1.4.0.0, lets see if ril and wifi can work, now trying to build v1-train
http://www.mediafire.com/download/hw506bc2y9j3b75/ffos-e400-philip-131225.zip
md5sum 1994e4a701db4ac99fec3cbdaf777b08

feherneoh said:
You can try older versions too
vendor files are downloaded by repo, so no need to do that, but you can try. I'm using vendor from github.com/TheMuppets
That system backup is used to get the vendor files, isn't it?
Sent from my MyAudio using xda app-developers app
Click to expand...
Click to collapse
System backup is done automatically for the ZTE Open, included for completeness.
If I try to change Branch, your repo-manifest advises it cant find any of them.

hecatae said:
you must be running cm9 on your e400 before attempting this
cd /path/to/your/directory/
git clone https://github.com/feherneoh/B2G
cd B2G
./config.sh e400
Code:
BRANCH=v1-train ./config.sh e400
adb pull /system backup-e400/system
cd /path/to/your/directory/B2G/
./build.sh
feherneoh, any chance of some stable builds being put up, ffos is currently on v1-train / v1.1.0 and your builds are creating v1.4.0 see https://wiki.mozilla.org/Release_Management/B2G_Landing
it would be worth running at the same speed as Mozilla so that if bugs are encountered we know it's device specific and not because we are bleeding edge.
all cm9 vendor lge e400 files are here: https://github.com/cybojenix/android_vendor_lge_e400
I'm going to have a look at this in the morning.
Edit: successfully built 1.4.0.0, lets see if ril and wifi can work, now trying to build v1-train
http://www.mediafire.com/download/hw506bc2y9j3b75/ffos-e400-philip-131225.zip
md5sum 1994e4a701db4ac99fec3cbdaf777b08
Click to expand...
Click to collapse
Hi, I installed your build and it only shows a white screen, black screen, white screen,.... Logcat: http://pastebin.com/x1y16m0p
And a logcat for the first build that did feherneoh(http://d-h.st/2TC), the unique that boots.. http://pastebin.com/w9EwBj3w
I think only will work builds using b2g sources that are not the lastest..

suggested hack to get icons to a better size:
https://groups.google.com/forum/#!topic/mozilla.dev.b2g/yrSLfHEuwYc
Code:
So the GetDefaultScaleInternal() method will return a
GAIA_DEV_PIXELS_PER_PX=1.0, according to
https://mxr.mozilla.org/mozilla-central/source/widget/gonk/nsWindow.cpp#532
Maybe the fix would be to hack GetDefaultScaleInternal(), make it return
0.5 in this case, and update the icons accordingly ?

hecatae said:
suggested hack to get icons to a better size:
https://groups.google.com/forum/#!topic/mozilla.dev.b2g/yrSLfHEuwYc
Code:
So the GetDefaultScaleInternal() method will return a
GAIA_DEV_PIXELS_PER_PX=1.0, according to
https://mxr.mozilla.org/mozilla-central/source/widget/gonk/nsWindow.cpp#532
Maybe the fix would be to hack GetDefaultScaleInternal(), make it return
0.5 in this case, and update the icons accordingly ?
Click to expand...
Click to collapse
I think for resize icons it has to add to build part GAIA_DEV_PIXELS_PER_PX=0.75 , not? "GAIA_DEV_PIXELS_PER_PX=0.75 ./build.sh" ¿?
But..if dont boots (only pass from lg logo and any else last builds..), its a bit absurd to have the icons good.....

I view that the revision of the build can be (supposedly) changed too changing revision in gaia, gonk-misc and rilproxy
<project path="gaia" name="gaia" remote="b2g" revision="v1-train" />
<project path="gonk-misc" name="gonk-misc" remote="b2g" revision="v1-train" />
<project path="rilproxy" name="rilproxy" remote="b2g" revision="v1-train" />
Click to expand...
Click to collapse
And..i discovered a mirror of gecko in github here: https://github.com/mozilla/gecko-dev that has a lot of revisions like master, b2g, release GECKO2501_2013111218_RELBRANCH, etc etc..
<project path="gecko" name="mozilla/gecko-dev" remote="github" revision="release" />
Click to expand...
Click to collapse
Feherneoh and hecatae, you said that maybe using v1-train or other less new revision maybe builds not??
I'm trying but I'm sure that you have more idea..

feherneoh said:
I noticed something: permission errors in non-working version's logcat
Click to expand...
Click to collapse
In your logcat http://pastebin.com/w9EwBj3w are some permissions errors too.. (line 1483 more or less)
E/GeckoConsole( 102): [JavaScript Error: "PermissionsTable.jsm: expandPermissions: Unknown Permission: video-capture" {file: "resource://gre/modules/PermissionsTable.jsm" line: 357}]
I/Gecko ( 102): PermissionsTable.jsm: expandPermissions: Unknown Permission: video-capture
E/GeckoConsole( 102): [JavaScript Error: "PermissionsInstaller.jsm: 'video-capture' is not a valid Webapps permission name." {file: "resource://gre/modules/PermissionsInstaller.jsm" line: 123}]
I/Gecko ( 102): PermissionsInstaller.jsm: 'video-capture' is not a valid Webapps permission name.
Click to expand...
Click to collapse
But the error in hecatae build I view maybe is this (line 2681) http://pastebin.com/x1y16m0p
I/GeckoDump( 318): Crash reporter : Can't fetch app.reportCrashes. Exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://browser/content/shell.js :: shell_reportCrash :: line 124" data: no]
E/GeckoConsole( 318): [JavaScript Warning: "Unknown property 'backgroud-color'. Declaration dropped." {file: "app://system.gaiamobile.org/style/wrapper/wrapper.css" line: 16 column: 17 source: " backgroud-color: grey;"}]
E/GeckoConsole( 318): [JavaScript Warning: "Error in parsing value for 'font-weight'. Declaration dropped." {file: "app://system.gaiamobile.org/style/shrinking_ui/shrinking_ui.css" line: 9 column: 15 source: " font-weight: medium;"}]
Click to expand...
Click to collapse
after that various apps died..

how you installed the zip file on my sits on a black screen
please help me

marcos_l3 said:
how you installed the zip file on my sits on a black screen
please help me
Click to expand...
Click to collapse
Yes..from now almost the result of all files is a black/white screen.. Only this build works: http://d-h.st/2TC
Only install in CWM, doesnt works if you have sdmerge installed

Related

[CMC-GUI] [DAILY] [PPA] Cyanogenmod Compiler Daily [Depreciated]

Cyanogenmod Compiler (CMC) GUI
Build cyanogenmod with a gui.
{
"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"
}
Known issues:
- Currently no multi-threading, which means when you press sync or compile, there is no loading bar (app looks like its failing, its not.). I am working on that.
(If you want to watch the output of the sync or compile, just open a terminal and type "cmc", I log all to the system.)
- When locking the CMCompiler to the unity launcher you have to logout and log back in refer: ubuntu bug 916098
- Currently there isn't great error logic and dialogs to warn you about everything. Something that is still being working on. Just run from the terminal if you have an issue that you need to report.
- Missing make clean and make installclean. These will be added in the future.
Found bugs to fix v0.1:
- No "/" at the end of custom repo string path.
- Error checking for compile start
*Please any issue that should arise, I apologize in advanced. Please let me know with as much detail as possible to replicate the issue and I will resolve it.
Please read:
I have thought maybe times different ways I was going to go about this. Ads, donate version, paid app, etc. I choose to keep the project open, as that's how I roll. I do ask that if you enjoy the application that you try to donate something. This was my first gui project and took a lot of time and effort to even get it to where it is right now. I hope everyone enjoys the app as much as I enjoy working on it.
Install:
Note: If you are using the old ppa then look at post # 2 on how to remove it before adding this.
Code:
sudo apt-add-repository ppa:lithid/ppa
sudo apt-get update
Install daily dev builds:
Code:
sudo apt-get install cmcompiler-daily
Install beta builds:
Note: Not yet available.
Code:
sudo apt-get install cmcompiler-beta
Install stable builds:
Note: Not yet available.
Code:
sudo apt-get install cmcompiler
Note: You cannot have daily and stable at the same time. You can only use either or.
Source code | Bugs | Answers
Build info:
daily-builds
Enjoy some signatures from SavocaFTW:
You can follow me on google+ I tend to talk about it a bit on there as well.
Cyanogenmod Compiler (CMCompiler) HALP!
Error Codes:
Error: Need to sync first - After choosing compile, the program didn't find the needed .repo folder in your repo path. This assumes you never ran sync, so you never downloaded the code. You could have also renamed the .repo folder to something else, which would cause this error as well.
Error: device not found - Your device was not found in the repo, might be unsupported.
Error: Adb isn't running - First time running compile, you will need to have your phone connected and ADB running in order to pull off needed files from your phone.
Error: Extract-files came back False - This means a script called extract-files.sh failed to pull off those needed files from your phone.
Error: Compile error please check - This indicates that your build failed. You will need to run cmcompiler via terminal to get why.
Error: Repo Script needs setup - You don't have the repo script installed. Install it.
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
sudo mv ~/repo /usr/local/bin/repo
Error: No device configured - Appears there is no device configured, just select one from the setup menu.
Removing old ppa:
Code:
sudo apt-get remove cmcompiler-daily
sudo apt-get install ppa-purge
sudo ppa-purge ppa:long-jeremie/ppa
About Cmcompiler CLI
** If you are still using the CLI version, I have not updated it in sometime. I might get back to that but for right now the gui is my main focus. Please understand. You could always clone and make edits to the CLI here
This changes everything, again.
Great idea. Thanks.
Awesome! Thank you very much
this is neat! good job
Is there any support for pulling propriety files from a new phone or is that too specific?
Sent from my M9300 using xda premium
Jamin13 said:
Is there any support for pulling propriety files from a new phone or is that too specific?
Sent from my M9300 using xda premium
Click to expand...
Click to collapse
Currently there is only support for devices from within the CM repo. There could be a plugin created though for specific devices that are not "supported" by cm. You would still need someone to write that plugin for that device since prop files are different for each device.
lithid-cm said:
Software for compiling on ubuntu:
32 bit:
Code:
git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
64 bit:
Code:
g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
Click to expand...
Click to collapse
lib32readline5-dev has been replaced by lib32readline-gplv2-dev on 11.10
And "gcc-4.3-multilib g++-4.3-multilib" aren't used from 11.04 and up - not needed.
Nice work though!
lithid-cm said:
If you are wondering how you can use this software its easy. You can clone my repo for now. and run the CMCompiler script:
Code:
git clone https://[email protected]/lithid/CMC.git
cd CMC
./CMCompiler
Click to expand...
Click to collapse
Hmmmm.
Code:
git clone https://github.com/lithid/CMC.git
cd CMC
./CMCompiler
Now we're talkin'!
Novek said:
lib32readline5-dev has been replaced by lib32readline-gplv2-dev on 11.10
And "gcc-4.3-multilib g++-4.3-multilib" aren't used from 11.04 and up - not needed.
Nice work though!
Click to expand...
Click to collapse
Updated second post. Thanks!
aorth said:
Hmmmm.
Code:
git clone https://github.com/lithid/CMC.git
cd CMC
./CMCompiler
Now we're talkin'!
Click to expand...
Click to collapse
I fixed that. No idea why I put that in their like that. Thanks!
lithid-cm said:
Currently there is only support for devices from within the CM repo. There could be a plugin created though for specific devices that are not "supported" by cm. You would still need someone to write that plugin for that device since prop files are different for each device.
Click to expand...
Click to collapse
Thanks.
If I could just figure out how to do it normally, I'd be fine.
unfortunately I can't seem to find anything about doing that.
Sent from my M9300 using xda premium
TEH KANGENAT0rZ!!!!1on1on1oneone!!
Jamin13 said:
Thanks.
If I could just figure out how to do it normally, I'd be fine.
unfortunately I can't seem to find anything about doing that.
Sent from my M9300 using xda premium
Click to expand...
Click to collapse
If you are looking to build on a new device. Go to cms github and grab a device tree from a similar device. Then you can see how everything is working... gather the stuff you need along with the device specific edits and hours and hours of trial and error. You will eventually get it... Its a learning process.
optedoblivion said:
TEH KANGENAT0rZ!!!!1on1on1oneone!!
Click to expand...
Click to collapse
King Kang?
This looks awesome! Thank you! I'm gonna try this out sometime this week. Thanks again!
This is a really cool project. For those of us who are uninitiated in using Git/Repo, will this make "making changes" to CM easy for us? Obviously, I see "Update Repo" as an option, but it will really take care of the rest for us?
Shidell said:
This is a really cool project. For those of us who are uninitiated in using Git/Repo, will this make "making changes" to CM easy for us? Obviously, I see "Update Repo" as an option, but it will really take care of the rest for us?
Click to expand...
Click to collapse
As of this moment. This doesn't support the needed bits for when you need to commit the code back to cm gerrit. This is something I am working on for my stable release. At this current state you can download the repo, assign a device, compile and update without any work needed done by the end user. When the rom is done downloading it gets placed in your home directory. I am not sure if that answered the question or not...
Soon there will be an option to make changes to the repo. This would enable repo start it would wait until you press enter again once changes are done and then commit them with repo upload. Of course this is still being worked out though.
Awesome--yeah, that answers my question. Thanks!
Nice job. Thank you for it.

[DEV-ONLY] [ROM] [JB] Unofficial MIUI V5 Xperia P (Stock Based)

Hello guys, devs
I've been looking to create MIUI V5 based on stock rom this whole months but have lots and lots of problems!
however I could manage so much problems (HUGE THANKS TO MUNJENI! ... feel free to press thnx on here) but still have networks and wi-fi problems (screen resolution fixed somehow! and there is no battery drain )
SO:
Not Working:
- WIFI NOW WORKING!!!
- bluetooth WORKED VERY WELL!!!
- Network (get fc on Phone.apk, Phone.apk related ... fixed telephony smali!)
- get FC on Provision.apk (to fix this first we need to fix telephony smalis)
- get FC on SEMCSetupWizard (Resource ID problem)
- get FC on Note (Overlay Problem)
- get FC on many app (Overlay and Resource ID Problem)
- some miss resolutions (fixed on phone, massages, lockscreen and more but still have problem on top of the other app that contains multi-page, see this
- get FC on radio! (Still overlay or Resource ID conflict problem)
Working? everything else! (every single settings tested)
and there is no battery draining! (at least not without network)
Kernel Git: https://github.com/sijav/patchrom_nypon_kernel
OTA ZIP UPLOADED:
here's the link (you need 7z to unpack this)
PART1: http://www.mediafire.com/download/9brhxkia07oo3s8/out.7z.001
PART2: http://www.mediafire.com/download/4dh2a073ioqxtx9/out.7z.002
OR
the fullota flashable zip in 1 part : http://bayfiles.net/file/QWo5/cCxjzW/fullota.zip
the LATEST fullota flashable zip (BUILD 1.100 and latest MIUI Version) in 1 part : http://bayfiles.net/file/SBDz/ApZbtU/fullota.zip
enjoy
so here I am giving you all my works and files created in github you can use that for creating a rom using linux (ubuntu 12.04 is preferred and 64 bit is a must)
Attention: this rom is not released yet so you need still waiting for a release ... do not post: waiting for release, nice jub, great jub (press the thnx button is just enough )
for discussion or other question please take it to here => [P] .::| the official unofficial MIUI discussion thread |::.
this thread has been made for devs to come and contribute to this great rom
here is link to github => https://github.com/sijav/patchrom_nypon
remember:
. First you need to full wipe your phone (wipe dalvik cache and data and also cache)
. After flash do not wipe any data ( it will cause fc and auto reboot), Do not flash gaaps (it will cause your home button not working!)
. you may want to flash boot.img first then flash your rom but that doesn't necessary
. adb has been enabled on start so you can have adb logcat after the splash screen!
. adb is not activated during splash screen and in recovery ( for activating this in recovery I need to recompile recovery again and that I can not do but if anyone willing to do pm me I will send some information what he have to do)
. fix_patchrom.sh will rename framework2.jar to framework_ext.jar so everytime you update your miui framework2.jar will be updated and you need to do fix_patchrom.sh again for framework2 update!
Readme from github:
HTML:
Get started
----------------
$ mkdir micode
$ cd micode
$ git clone -b jellybean git://github.com/MiCode/patchrom_android.git android
$ git clone -b jellybean git://github.com/MiCode/patchrom_build.git build
$ git clone -b jellybean git://github.com/MiCode/patchrom_miui.git miui
$ git clone -b jellybean git://github.com/MiCode/patchrom_tools.git tools
$ git clone -b master git://github.com/sijav/patchrom_nypon.git nypon
- for patchrom fix run:
$ ./fix_patchrom.sh
Export path
-----------
$ . build/envsetup.sh -p nypone
$ export PATH=$PATH:/path_to/micode/tools
Build your rom
--------------
$ cd nypone
$ make fullota
- you will get error on compiling the framework-miui-res.apk so enter this code:
$ ./fmr.sh
After everything is compiled, you need to manually fix updater-script from zip! (this isn't nessesary)
- Please do look in temp folder for conflicts and try to fix remaining bugs, Thnx.
- for now Phone.apk and Provision.apk are not working, deleting them and SEMCSetupWizard.apk will make rom booting.
- after installing you need to run these command as some files won't have the right permissions if you don't fix the updater-script from zip:
adb shell chmod 06755 /system/xbin/*
adb shell chmod 755 /system/bin/*
- there is a folder named changes it containes the changes that has been made to the untouched frameworks until the first initial import
{
"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"
}
"MIUI is one of the most popular Android ROMs in the world. It is based on 4.1.2 featuring better experience and richer themes.
and MIUI offers alot of Free and Paid Themes, clocks and wallpapers. It is very customizable."​
mine
also mine
current bugs and issues ?
percy_g2 said:
current bugs and issues ?
Click to expand...
Click to collapse
Sorry and thnx forget this one
added
sijav said:
Hello guys, devs
--
Click to expand...
Click to collapse
Good job! I'm working on miui too
sijav said:
Sorry and thnx forget this one
added
Click to expand...
Click to collapse
Wifi rfkill drivers are related to kernel .which kernel you used ?
Sent from my Xperia P using Tapatalk 2
sj8023ld said:
Good job! I'm working on miui too
Click to expand...
Click to collapse
great,
care to share your experience over miui and that how far did you go? what have you made and is the telephony works for you too? (specially if you have xperia P?)
thnx
percy_g2 said:
Wifi rfkill drivers are related to kernel .which kernel you used ?
Sent from my Xperia P using Tapatalk 2
Click to expand...
Click to collapse
Stock!
the very stock kernel!
just put some init.d support and a recovery from nemesis (I think)
sijav said:
great,
care to share your experience over miui and that how far did you go? what have you made and is the telephony works for you too? (specially if you have xperia P?)
thnx
Stock!
the very stock kernel!
just put some init.d support and a recovery from nemesis (I think)
Click to expand...
Click to collapse
I'm working on xperia tx, and I'm not good at this ,so I hope we can help each other if possible
sj8023ld said:
I'm working on xperia tx, and I'm not good at this ,so I hope we can help each other if possible
Click to expand...
Click to collapse
Sure, that's why xda are for! to help each other
Sry dude I don't have any IDEA
And please no ask for ETA thnx
by the way you can use this thread for discussion or further question => [P] .::| the official unofficial MIUI discussion thread |::.
Progress: I'm working on CM based and look for fixing it ... maybe I could manage to fix some smali by looking at the cm smalis made ... but really not sure what am I doing!
OTA ZIP UPLOADED (at last!)
here's the link (you need 7z to unpack this)
PART1: http://www.mediafire.com/download/9brhxkia07oo3s8/out.7z.001
PART2: http://www.mediafire.com/download/4dh2a073ioqxtx9/out.7z.002
enjoy
sijav said:
OTA ZIP UPLOADED (at last!)
here's the link (you need 7z to unpack this)
PART1: http://www.mediafire.com/download/9brhxkia07oo3s8/out.7z.001
PART2: http://www.mediafire.com/download/4dh2a073ioqxtx9/out.7z.002
enjoy
Click to expand...
Click to collapse
your kernel source?
percy_g2 said:
your kernel source?
Click to expand...
Click to collapse
used STOCK ... + nemesis recovery
(I have already told you that though)
Edit: If you mean what did I just uploaded I upload the rom made by patchrom that can be flashed by recovery and is booted and all but have no wifi and network and problems that have been said and so on
sijav said:
used STOCK ... + nemesis recovery
(I have already told you that though)
Click to expand...
Click to collapse
you have to upload the kernel source according to GPL and it will help me fix kernel related issues .
percy_g2 said:
you have to upload the kernel source according to GPL and it will help me fix kernel related issues .
Click to expand...
Click to collapse
I didn't compile the kernel! ... but will upload the touched ramdisk asap
Edit: @percy_g2 I just used the stock kernel ... decompile it's ramdisk, added shelld service and recovery and rngd and white balance and init.d support by doomlord in init.rc ... add recovery start in init.st-erricson.rc , added sbin and res folder from nemesis kernel ... and that's all then I put everything together=>
I packed the ramdisk using this command =>
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.gz
I maked the kernel by added ramdisk cmdline and zImage to python by using this command =>
Code:
python mkelf.py -o boot.img [email protected] [email protected],ramdisk [email protected]
then I opened stock kernel and patched one by hex editor and copied these from 0X00000094 to 0X000004E6 from stock rom then put '04' to 0X0000001D,
(that's all I did )
percy_g2 said:
you have to upload the kernel source according to GPL and it will help me fix kernel related issues .
Click to expand...
Click to collapse
kernel uploaded:
https://github.com/sijav/patchrom_nypone_kernel
flashable fullOTA.zip in one part from bayfiles
http://bayfiles.net/file/QWo5/cCxjzW/fullota.zip
sijav said:
kernel uploaded:
https://github.com/sijav/patchrom_nypone_kernel
flashable fullOTA.zip in one part from bayfiles
http://bayfiles.net/file/QWo5/cCxjzW/fullota.zip
Click to expand...
Click to collapse
I've seen your ramdisk source . I think there's no need to add a cert into kernel
sj8023ld said:
I've seen your ramdisk source . I think there's no need to add a cert into kernel
Click to expand...
Click to collapse
well somebody report that if there is no cert in kernel for stock rom we will see a huge battery drain but it was for GB and ICS so I thought maybe in this rom for not having cert we may encounter battery drain ...
anyways with or without cert the rom is booting but wifi and bluetooth not working so implenting cert is not a much big deal! ... I'm working to see if I can make CM running and borrow smalis from there
sijav said:
well somebody report that if there is no cert in kernel for stock rom we will see a huge battery drain but it was for GB and ICS so I thought maybe in this rom for not having cert we may encounter battery drain ...
anyways with or without cert the rom is booting but wifi and bluetooth not working so implenting cert is not a much big deal! ... I'm working to see if I can make CM running and borrow smalis from there
Click to expand...
Click to collapse
To fix the phone services is related to the radio interface layer, I think we can skip to patch the phone services

[Q] Need help compiling Liquid Smooth!

Hey guys!
I finally did it and downloaded the liquid smooth's and device's repos. But now when I type 'make otapackage -j4 -i' after 4 hours(!) of compiling it stucks at a certain file and then I can't move the mouse, type someting or anything, Ubuntu 14.04 freezes and I have to press the power button to force the PC close.
Please anyone help? I'm posting a picture with my PC:
{
"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"
}
lefterios said:
Please anyone help? I'm posting a picture with my PC:
Click to expand...
Click to collapse
You might have a corrupted gvfsd-metadata. Do pkill gvfsd-metadata, rm -rf ~/.local/share/gvfs-metadata.
And compiling time depends on the computer specs and can easily take more than 3 hours on an average core processor(i3).
MasterAwesome said:
You might have a corrupted gvfsd-metadata. Do pkill gvfsd-metadata, rm -rf ~/.local/share/gvfs-metadata.
And compiling time depends on the computer specs and can easily take more than 3 hours on an average core processor(i3).
Click to expand...
Click to collapse
Okay I'll try it today I'll report if this worked.
I have an Intel core i5 with 3GB Ram and I think that it's quite long...
But thanks anyway!
Okay so I compiled again and now no freezes. Unfortunately however when it was going to end an error occured:
The weird thing is that all folders like system, recovery etc are there
Can you help?
lefterios said:
Okay so I compiled again and now no freezes. Unfortunately however when it was going to end an error occured:
The weird thing is that all folders like system, recovery etc are there
Can you help?
Click to expand...
Click to collapse
Can you paste the error here? With screenshots I can really help you. Just paste the error like this:
Code:
Error
GeekyDroid said:
Can you paste the error here? With screenshots I can really help you. Just paste the error like this:
Code:
Error
Click to expand...
Click to collapse
Ok sure:
Code:
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files",line 1123, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files",line 1091, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files",line 539, in WriteFullOTAPackage(OPTIONS.input_tmp,"BOOT")
File "/home/lefteris/working/build/tools/releasetools/common.py", line 361, in GetBootableImage
info_dict))
File "/home/lefteris/working/build/tools/releasetools/common.py", line 836, in __init__
self.size = len(data)
TypeError: object of type 'NoneType' has no len()
make: [/home/lefteris/working/out/target/product/golden/liquid_golden-ota-userdebug.lefteris.zip] Error 1 (ignored)
Sorry I may have made a mistake because I copied from the image. If you want full changelog you can right-click the image and press 'open image in a new tab'
lefterios said:
Ok sure:
Code:
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files",line 1123, in
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files",line 1091, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files",line 539, in WriteFullOTAPackage(OPTIONS.input_tmp,"BOOT")
File "/home/lefteris/working/build/tools/releasetools/common.py", line 361, in GetBootableImage
info_dict))
File "/home/lefteris/working/build/tools/releasetools/common.py", line 836, in __init__
self.size = len(data)
TypeError: object of type 'NoneType' has no len()
make: [/home/lefteris/working/out/target/product/golden/liquid_golden-ota-userdebug.lefteris.zip] Error 1 (ignored)
Sorry I may have made a mistake because I copied from the image. If you want full changelog you can right-click the image and press 'open image in a new tab'
Click to expand...
Click to collapse
Did you type make -i (ignoring the errors?) If you did that, the zImage might not have been built because of errors and the boot image is not built due to this. It might also be because of fs size constraints. In your out folder of your device, check if you have the kernel and the root directory.
And in the py file the typecasting might have been done wrong since it says "object of type 'NoneType' has no len()"
MasterAwesome said:
Did you type make -i (ignoring the errors?) If you did that, the zImage might not have been built because of errors and the boot image is not built due to this. It might also be because of fs size constraints. In your out folder of your device, check if you have the kernel and the root directory.
And in the py file the typecasting might have been done wrong since it says "object of type 'NoneType' has no len()"
Click to expand...
Click to collapse
Ιn the out folder I have the root directory but not the kernel... And yes I typed -i because there were many errors and I couldn't build the ROM. So what do I have to do now? Please note that I'm beginner and I don't know very much for ROM development...
lefterios said:
Ιn the out folder I have the root directory but not the kernel... And yes I typed -i because there were many errors and I couldn't build the ROM. So what do I have to do now? Please note that I'm beginner and I don't know very much for ROM development...
Click to expand...
Click to collapse
As I said the error must have been in the kernel and ignoring that will not build the kernel, you will have to fix it manually the errors you face in the kernel building stage, post it here.
MasterAwesome said:
As I said the error must have been in the kernel and ignoring that will not build the kernel, you will have to fix it manually the errors you face in the kernel building stage, post it here.
Click to expand...
Click to collapse
Sorry I don't know how to do that :crying:
A question: Can I build the ROM with existing kernel image(boot.img) from another ROM? I don't make changes to kernel...
lefterios said:
Sorry I don't know how to do that :crying:
A question: Can I build the ROM with existing kernel image(boot.img) from another ROM? I don't make changes to kernel...
Click to expand...
Click to collapse
Yes you can, in the boardconfig.mk add a flag
TARGET_PREBUILT_KERNEL := $(DEVICE_FOLDER)/prebuilt/kernel
Be sure to define the DEVICE_FOLDER at the top of the make file.
Although its deprecated. But it'll work in your case if the kernel is a kitkat kernel.
MasterAwesome said:
Yes you can, in the boardconfig.mk add a flag
TARGET_PREBUILT_KERNEL := $(DEVICE_FOLDER)/prebuilt/kernel
Be sure to define the DEVICE_FOLDER at the top of the make file.
Although its deprecated. But it'll work in your case if the kernel is a kitkat kernel.
Click to expand...
Click to collapse
I tried it but again no luck What am I doing wrong? It produces all files and folders except kernel!
lefterios said:
I tried it but again no luck What am I doing wrong? It produces all files and folders except kernel!
Click to expand...
Click to collapse
I believe you forgot to remove the kernel directory flags from the board config.mk. attach it here.
MasterAwesome said:
I believe you forgot to remove the kernel directory flags from the board config.mk. attach it here.
Click to expand...
Click to collapse
Ok I attached the file found under ~/working/device/samsung/golden. I hope you can help me. I created the folder prebuilt and I put there a zImage. Is that right?
lefterios said:
Ok I attached the file found under ~/working/device/samsung/golden. I hope you can help me. I created the folder prebuilt and I put there a zImage. Is that right?
Click to expand...
Click to collapse
You named it as zImage and specified it as prebuilt/kernel. It should be $(DEVICE_FOLDER)/prebuilt/zImage.
MasterAwesome said:
You named it as zImage and specified it as prebuilt/kernel. It should be $(DEVICE_FOLDER)/prebuilt/zImage.
Click to expand...
Click to collapse
Firtsly is everything alright with the boardconfig file? So should I rename the file to zImage and that's it? And also which difference there is between kernel and zImage and which should I use?
lefterios said:
Firtsly is everything alright with the boardconfig file? So should I rename the file to zImage and that's it? And also which difference there is between kernel and zImage and which should I use?
Click to expand...
Click to collapse
Everything else seems fine... The path must be the path to your kernel or what ever you renamed it as.
I'd recommend you try and compile the kernel alone to check if it work
MasterAwesome said:
Everything else seems fine... The path must be the path to your kernel or what ever you renamed it as.
I'd recommend you try and compile the kernel alone to check if it work
Click to expand...
Click to collapse
I compiled the kernel alone and it didn't show any error. It made a zImage file successfully. So where is the problem?
lefterios said:
I compiled the kernel alone and it didn't show any error. It made a zImage file successfully. So where is the problem?
Click to expand...
Click to collapse
Trying doing a "make" without the -i and see where the build stops.

[ROM][CM11][dev only] cm-11-UNOFFICIAL-d620 Alpha

CyanogenMod 11 for the LG G2 mini D620r
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
All Credits so far go to Quarx and his project CM11 for LG L90
What i have done so far:
Setup Ubuntu on my Laptop
Installed CM dev environment like described here!
Made a new device folder following THIS guide and build some recoveries.
Took the sources from CM11 for LG L90 and integrated them to my build environment.
CM11 for LG L90 builds fine but i can not test it.
Took the files i thought we need from L90 and put them to my d620 tree.
Trial and error till it compiled for d620.
For the kernel i use original LG sources extracted to kernel/lge/msm8226.
Switched to kernel source from Quarx and tweaked it for d620.
Find sources i use here.
Unfortunately the kernel i have build leads to boot loops. (Yes i have wiped everything)
If i only install the system with the original LG stock kernel i get an security error.
How can i find out why the kernel boot loops?
(had to use the dt.img from stock kernel because mine didn't work, phone gets stuck in fastboot)
Kernel now boots with recovery.
Touch only works if i copy the FW to system folder.
CM11 now works quit well.
Known issues:
- NFC not working at all
- Vibration not working at all
- Back/Main camara has overexposure on bright scenes
- LTE can only be activated by adding quick setting for LTE
Testers welcome.
Video review from simo14
Alpha: Download
{
"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"
}
Any help appreciated.
Port rom!!
Good job! I think You can port rom l90 for g2 mini. Read it: http://forum.xda-developers.com/showthread.php?t=2545618 (my English is bad, sorry!!)
I think we need a "extract-files.sh" to extract device proprietary files with connected and enabled usb debbuging. I do some research but didnt luck. My English is weak and i don't know how to do this script. I know its necesary for boot and compile with success.
Maybe Quarx can help us.
Probably kernel boot loops because you compile with CM source and that its not compatible with stock rom.
Regards.
this is great progress
im trying like hell to make a custom recovery.
take a look at this zaaap
http://forum.xda-developers.com/android/help/building-kernel-error-lg-g2-mini-t2853390
maybe you could help me out a bit?
I'm extracted a system folder from TWRP backup and try to port by paste>copy method. I need a META-INF folder for our phone. I don't know how to make it.
Ok i found it.
I make four builds with AndroidKitchen but its always a update-binary script error.
Any help?
make -j4 otatools give me that error.
/media/radek/bee9f4ae-71a6-4ed8-9153-7dd674ea803d/CM11/out/target/product/generic/obj/APPS/SignatureTest_intermediates
"ebtables is disabled on this build"
find: `src': Nie ma takiego pliku ani katalogu
grep: /build/target/board/generic/recovery.fstab: Nie ma takiego pliku ani katalogu
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
make: Nie ma nic do zrobienia w `otatools'.
/build/target/board/generic/recovery.fstab exists in the directory.
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
partyzant_x said:
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
Click to expand...
Click to collapse
w7ds is an LG L90 dual sim.
Go to your kernel folder /arch/arm/configs and look for a g2m... ...defconfig where the name fits your device.
Try to compile with the g2m defconfig should work.
You might be missing touch and other hardware if you didn't get all property blobs needed for our device.
This is the point where I got struck at the moment.
/tmp/ccfkEagn.s: Assembler messages:
/tmp/ccfkEagn.s:166: Warning: swp{b} use is deprecated for this architecture
/tmp/ccfkEagn.s:192: Warning: swp{b} use is deprecated for this architecture
CC arch/arm/mach-msm/smd_private.o
CC arch/arm/mach-msm/smem.o
CC arch/arm/mach-msm/smd_init_dt.o
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
I'm try to compile the LG source with:
Run following scripts to build kernel
a) cd kernel
c) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
Zaaap can you share your device tree?
Ok. I fixed the errors. Now I have "zImage" how flash that?
What did you do to fix the errors? And wich toolchain did you use?
The zimage comes with some .ko files? You have to make a .zip file of those and flash it through custom recovery or a flash app from market! Like rashr
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
Don't flash the zImage as it is only a part of the needed boot.img.
There is a command like 'make boot.img'. I'll have to look for it.
I'll explain more later when I get to my laptop.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Now I'm trying to create a device tree manually. A bit of getting lost in this. Zaaap can share with your device tree. Rather than create new ones we can work on one and make any fixes.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
where did you find the readme.txt where it said wich toolchain you should use?
invaderjohn said:
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Click to expand...
Click to collapse
Give me: Error executing updater binary in zip.
Downloaded kernel source from lg site. Unpack it and there is two files readme.txt and packed kernel source, unpacked it copy kernel folder to cm source then cd kernel and:
make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
When I have error for example:
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
Then open smd_init_dt.c find line with smd_private.sh. Its look include <smd_private.sh> and change it to include "smd_private.sh".
Sorry for my English.
Make boot.img
Here you can find the official doc about making boot.img: HERE
I took the device tree from Quarx found here made a copy in a new folder 'd620' but i think 'g2m' would have been correct for phone.
Find my device folder here.
Find my vendor folder here.
The kernel source is located under kernel/lge/msm8226
I normaly compile a recovery and see if the kernel works with it.
Thus i don't risk a semi brick because if the kernel is bad, then recovery may not start but system will start and i can flash an other recovery with a new kernel.
If recovery boots, i can use adb to get dmesg.log and see what works and what not.
On my last try, touch didn't initialize complete.
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
partyzant_x said:
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
Click to expand...
Click to collapse
It boot, but takes long to do so and there is no touch.
This is the same problem i have.
We need to get the correct touch firmware + patch.
Find log attached.
Kernel boots with touch
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Zaaap72 said:
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Click to expand...
Click to collapse
partyzant_x said:
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Click to expand...
Click to collapse
okay so root is good
look in /proc for
/proc/config.gz
it might be there it might not. i need the stock boot.img please. looking through source right now and unsure of which defconfig.
your modules also depend on libraries in system/vendor - you need that entire directory for your device tree. you may also need
manufacturer/device specific/proprietary libraries from system/lib
starting in /system/vendor type in terminal
strings [nameoflib].so | grep "\.so"
these will bring up a list of additional libraires needed. the ones you already have in vendor don't worry about. the ones you
will find in system/lib are the additional ones you need to get for your device tree. go to the thread i'm working in with restl3ss and read through the whole thing but please do not post any questions there. post here use the mention function @moonbutt74
or pm me or click reply button below any of my posts in this thread and i will know by email.
m
on defconfig readme suggests w7ds_open_cis_defconfig but will try g2m_global_com_defconfig

Help building LineageOS for LeEco (LeTV) LeMax 1 (X900/Max1) CN

If you're in a hurry and just want to know the latest news, follow this link:
https://forum.xda-developers.com/showpost.php?p=80393641&postcount=58
Keep reading for some background info.
Hi there!
So... I'm trying to port LineageOS (version 15.1) from OnePlus - OnePlus2 device to the LeEco LeMax 1 phone.
Why I've chosen this device to port from?
It has the MSM8994 (Qualcomm Snapdragon 810) SoC, which is the same as Max1, so (supposedly) a kernel compile would not be too much hassle. Besides it also has many similarities in terms of hardware.
What I did for device dir:
I took the tree from https://github.com/LineageOS/android_device_oneplus_oneplus2 and modified it to meet max1 requirements.
Current tree: https://github.com/alexsmithbr/android_device_letv_max1
What I did for vendor dir:
I compared the tree with Max1 tree, excluding everything that was not found in Max1. The plan is to add more vendor stuff if necessary.
Current tree: https://github.com/alexsmithbr/android_device_letv_max1
What I did for kernel dir:
I downloaded Le_Max_OpenSource.zip from opensource.le.com (in fact, as the site is down, I got a copy from http://web.archive.org/web/20180626053054/http://opensource.le.com:80/ and, from there, I found the file I needed was named Le_Max_OpenSource.zip. I got it from here.
The kernel config in this zip file is exactly the same I get from the device itself, with adb pull /proc/config.gz.
Current tree: https://github.com/alexsmithbr/android_kernel_letv_max1
Interesting related threads:
https://forum.xda-developers.com/showpost.php?p=78690008&postcount=7
https://forum.xda-developers.com/le.../cm-14-1-android-7-1-unofficial-letv-t3530173
Other possibly useful resources:
http://web.archive.org/web/20180626053054/http://opensource.le.com:80/
https://forum.xda-developers.com/showpost.php?p=78676206&postcount=2402
These are thanks to @rico69310, specifically this post:
https://www.mediafire.com/folder/ff7hbpa62ivsg/
https://yadi.sk/d/RPfdh3glmhzarw
https://cloud.mail.ru/public/GP9g/cWpyeYbuK/
Another useful resource, in case you brick your X900. This is thanks to @Phsh:
https://forum.xda-developers.com/showpost.php?p=75157516&postcount=2375
Current status
I can build LineageOS 15.1 completely, but, once flashed, the kernel doesn't boot and phone enters bootloader (the penguin screen) and stay there.
What I need
It's pretty obvious I need the ROM working...
But the focus now would be to have a working boot.img. I really don't know what I'm doing wrong.
I can't get any logs, as LeEco patched the kernel so that we don't have a last_kmsg. Instead, they apparently put last_kmsg into another partition in /dev/block/platform/soc.0/f9824900.sdhci/by-name/letvconfig2. You can check this in the kernel, file kernel/printk/last_kmsg.c, line 124:
Code:
#define DEFAULT_KERNELLOG_FILENAME "/dev/block/bootdevice/by-name/letvconfig2"
char *kernlog_file = DEFAULT_KERNELLOG_FILENAME;
Well, I tried to give an overview of all steps I took. Please feel free to ask anything or give hints.
Together we can make LeEco LeMax 1 live longer!
Thought it would be nice to describe my build process.
Basically I'm following these instructions: https://wiki.lineageos.org/devices/oneplus2/build
Of course these instructions are for oneplus2, but the step-by-step is pretty much the same for any device.
I'm using Ubuntu 18.04.1 LTS, in which I created a user specifically for building LineageOS.
I followed all steps on the above link until breakfast oneplus2, since, at this point, I had to create my own device/vendor/kernel tree, so that I can breakfast it.
To do this, I did:
Code:
# clone max1 device
cd ~/android/lineage/device
mkdir letv
cd letv
git clone https://github.com/alexsmithbr/android_device_letv_max1.git max1
# clone max1 vendor
cd ~/android/lineage/vendor
mkdir letv
cd letv
git clone https://github.com/alexsmithbr/android_vendor_letv_max1.git max1
# setup kernel
cd ~/android/lineage/kernel
mkdir letv
cd letv
# change <path_to_file> to the correct path to Le_Max_OpenSource.zip
# you downloaded from the link on the previous post.
unzip <path_to_file>/Le_Max_OpenSource.zip -d max1
# as the zip has unnecessary subfolders, I just moved them
# to their correct names and deleted other rubbish.
mv max1/LeMax_kernel/kernel/ max1/msm8994
rm max1/LeMax_kernel/ -R
In the end, you need a structure like this:
Code:
~/android/lineage/device/letv/max1
~/android/lineage/vendor/letv/max1
~/android/lineage/kernel/letv/msm8994
Finally, put config.gz in its dir:
Code:
adb pull /proc/config.gz /tmp
gunzip /tmp/config.gz -c > ~/android/lineage/kernel/letv/msm8994/arch/arm64/configs/msm8994-max1-perf_defconfig
Okay, now everything is set up for the build to start.
Code:
source build/envsetup.sh
breakfast max1
export USE_CCACHE=1
ccache -M 50G
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
croot
Just before start building, I choose which kind of build I want:
Code:
choosecombo
Build type choices are:
1. release
2. debug
Which would you like? [1] 1
Which product would you like? [lineage_max1]
Variant choices are:
1. user
2. userdebug
3. eng
Which would you like? [eng]
Now, if you want a normal build, you can enter:
Code:
brunch max1
But, if you want a really verbose log (very useful to debug build errors), you can enter:
Code:
mka -j 4 showcommands
Note that -j 4 means 4 simultaneous jobs. You can specify another number. A rule of thumb is to use <number_of_cpus> * 2.
Now the system should build...
At this point:
https://github.com/alexsmithbr/andr...tree/0f9134dd09c269b2da9008c5598060b9d19ac2ef
https://github.com/alexsmithbr/andr...tree/9ece561a945867ab2af733c5ef890b6df5438a8b
The system builds and mka -j 4 showcommands bacon will build flashable lineage-15.1-20190128-UNOFFICIAL-max1.zip.
Unfortunately, when flashing this zip, and restarting the phone, it will vibrate twice when showing the LeEco first screen, then it vibrates twice again and shows me the penguin screen (bootloader).
No luck up to now.
Keep up with the good work... I hope you get the kernel working.
Spunkination said:
Keep up with the good work... I hope you get the kernel working.
Click to expand...
Click to collapse
Me too!
It's so hard to get any help... I've been to freenode as well and nobody wanted to help there. :/
So it feels like a very lonely path. But I'm still on to it.
Currently I'm recompiling everything, now getting "my" tree a bit closer to @ABM30 tree, adapted to LineageOS, instead of CyanogenMod.
Let's see what happens next.
No luck. Boots to penguin (bootloader) screen again.
---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------
I'm cheering for you. I would very much like 8.1 Good luck ! Good work!
htimsxela said:
Me too!
It's so hard to get any help... I've been to freenode as well and nobody wanted to help there. :/
So it feels like a very lonely path. But I'm still on to it.
Currently I'm recompiling everything, now getting "my" tree a bit closer to @ABM30 tree, adapted to LineageOS, instead of CyanogenMod.
Let's see what happens next.
No luck. Boots to penguin (bootloader) screen again.
Click to expand...
Click to collapse
Hope you are good friend?
How is the build going?
I updated the git repositories. The current version compiles as well and I get a ROM at the end, but unfortunately it doesn't boot. I'm probably missing something in the kernel build. I'm still investigating, but I don't even get to the LineageOS logo. When I turn on the phone, it goes straight to bootloader (penguin) screen.
I'll keep trying. Since a build involves a lot (really!) of variables, there's always something new to try.
And it's good that we keep this thread active. Maybe someone with more knowledge shows up and is able to help.
My biggest issue is I can't find a way of seeing what's wrong, since LeEco patched the kernel in a way there is no /proc/last_kmsg file, nor /sys/fs/pstore/console-ramoops. LeEco implemented it in a way the logs would be written to a partition called letvconfig2, but even there I cannot see any logs.
I read another way of seeing kernel logs would be to use the phone's serial port, but then I'd have to reach its main board, which is not an option currently, since this is my only phone.
In other words, my options now resume to keep trying.
Tomorrow I expect to have some time to resume the work. Will give it some more tries. I'm even thinking about checking out a previous version of LineageOS (when it was still called CyanogenMod), then, once I get it working, try to make my way to newer versions.
Stay tuned!
And again: any hints are more than welcome!
I really believe this thread may become kind of a roadmap to compile android for any unsupported device.
Update: by looking at recovery.img and comparing to the recovery partition on device, I noticed the kernel being built by LineageOS doesn't contain any DTBs. Without DTBs, the kernel won't be able to identify the phone's hardware.
How I checked this:
Code:
$ mkdir /tmp/boot
$ cd /tmp/boot
$ unpackbootimg -i ~/android/lineage/out/target/product/max1/recovery.img -o .
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-5 androidboot.selinux=permissive buildvariant=userdebug
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 4096
$ split-appended-dtb-master/split-appended-dtb recovery.img-zImage
ERROR: Appended Device Tree Blob not found!
I'll try to find out how to automatically add DTBs to the images.
I know there was a variable called TARGET_KERNEL_APPEND_DTB, which should be set to true on older (cyanogenmod) versions, but it is now deprecated. So deprecated that even the "deprecated" messages have been removed by now.
As far as I could figure out, now the action of appending/not appending DTBs to the kernel image is guessed by variable BOARD_KERNEL_IMAGE_NAME. For example:
To add dtb to kernel image, one would do:
Code:
BOARD_KERNEL_IMAGE_NAME := Image-dtb
To don't add dtb to kernel image, one would do:
Code:
BOARD_KERNEL_IMAGE_NAME := Image
I was hoping this would change something, as for me that variable was defined without the -dtb suffix, but I figured out I broke the kernel build:
Code:
make[1]: *** No rule to make target 'Image-dtb'. Stop.
I guess this is because the original kernel is too old (3.10.84) and it's AndroidKernel.mk still relies on TARGET_KERNEL_APPEND_DTB, as we can see on line 68:
Code:
ifeq ($(TARGET_KERNEL_APPEND_DTB), true)
$(info Using appended DTB)
TARGET_PREBUILT_INT_KERNEL := $(TARGET_PREBUILT_INT_KERNEL)-dtb
endif
Patch the kernel? Wow! This is going deep...
* unpackbootimg is part of the android_bootimg_tools. I got it from here: wget https://storage.googleapis.com/goog...d-serialport-api/android_bootimg_tools.tar.gz
* split-appended-dtb is this tool: https://github.com/dianlujitao/split-appended-dtb
Turns out there are two ways of adding DTBs.
{
"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"
}
By checking my current recovery partition, I noticed DTBs are attached to partition, not to kernel. I also noticed it is not using a compressed kernel. So I'll configure BoardConfig.mk as:
Code:
BOARD_KERNEL_IMAGE_NAME := Image
If I wanted it gzipped, I'd make it Image.gz. If I wanted the DTBs attached to kernel (not to image), I'd do Image.gz-dtb.
Apparently no kernel patch will be needed... Anyway I created a git repository for it, just in case I need to change something.
Again, the build works, but it doesn't boot.
As I'm focusing on testing the kernel, I'm using the recovery partition.
I just dumped a copy of it with:
Code:
host$ adb shell
phone$ su
phone# cp /dev/block/bootdevice/by-name/recovery /sdcard
phone# exit
phone$ exit
host$ adb pull /sdcard/recovery
and I'm flashing it over and over to test.
To do this, I do
Code:
host$ adb reboot bootloader
# phone reboots
host$ fastboot flash recovery /path/to/recovery.img
# it flashes, then, holding volume-up, I type:
host$ fastboot reboot
Phone will reboot into recovery and test my image (up to now, I only get back to penguin screen (bootloader)).
To flash back my working recovery image, I do the same as above, just changing the path to recovery image.
Bless you and your work
Dude, I would definitely-definitely liked to help; I understand and root for your hard work. But unfortunately I don't possess any knowledge in this area. Yeah, I can flash using manual, but I'm lamer in terms of programming, not even close to IT.
htimsxela said:
Hi there!
Click to expand...
Click to collapse
I rarely meet such wonderful and persistent people like you. I sincerely hope you will succeed and achieve your goal! :good:
Santey Maas said:
Dude, I would definitely-definitely liked to help; I understand and root for your hard work. But unfortunately I don't possess any knowledge in this area. Yeah, I can flash using manual, but I'm lamer in terms of programming, not even close to IT.
Click to expand...
Click to collapse
Thanks, mate! I didn't give up yet. Each try brings more knowledge and I hope I'm able to share all I'm learning. Sort of paving the road for newcomers.
Tircon said:
I rarely meet such wonderful and persistent people like you. I sincerely hope you will succeed and achieve your goal! :good:
Click to expand...
Click to collapse
Thanks! My hope is that - if I succeed - more people can benefit from my work and give these phones a longer life.
LeEco Le Max (max1/x900) Secret Codes
A bit off-topic, but here it goes... While looking for a way to debug kernel boot, I came across those famous secret codes you can type on phone screen to access secret/test menus... This site, for example, says you can use code *#*#76937#*#* to have access to a menu where you can enable/disable some log, debug and AT commands options. I tested and it worked with my phone. Not happy enough, I did a
Code:
grep 76937 / -rl
on the phone and found out system/app/LetvDebugUtil/oat/arm64/LetvDebugUtil.odex was the only place where it occurred. Inspecting the file, I found, right next to the occurrence, the code 9439. Just to test, I entered *#*#9439#*#* on the phone and got to a Chinese menu (see attached picture). The translation of these Chinese stuff is "Launch China Telecom Network (CDMA)". I didn't check that box to see what happens.
Current known codes
*#*#76937#*#* - Menu where you can enable/disable some log, debug and AT commands options.
*#*#9439#*#* - Launch China Telecom Network (CDMA)
*#*#8888#*#* - Advanced settings. Here you can turn on logging of App, Modem, Net, Kernel, Bluetooth, GPS and WiFi. Logs are stored in /sdcard
*#0000# - About phone. Information about each card slot.
*#06# - MEID & IMEI numbers.
If you're having this error while trying to build LineageOS:
Code:
FAILED: /bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/android_build/android/lineage/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_l.cpp system/tools/aidl/aidl_language_l.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/android_build/android/lineage'
You're probably having the same issue I'm having with Flex. The easiest option is to recompile it. And it's easy.
Code:
$ cd prebuilts/misc/linux-x86/flex
$ mkdir flex-2.5.39-src
$ cd flex-2.5.39-src
$ tar zxvf ../flex-2.5.39.tar.gz
$ ./configure
$ make
$ cp flex ../flex-2.5.39
$ cd ..
$ rm flex-2.5.39-src -R
The above commands will recompile Flex for your architecture and everything should be fine (with Flex).
Some news regarding the overall progress with LineageOS.
I checked out the repo from cm-14.1 (cyanogenmod 14.1) and am now trying to build for it. If it builds, at least we'll have Android 7.1.x running on device. And - I believe - it could bring some light to start a port to a newer version (Lineage 15.1).
Up to now, I faced the same compile errors I got when compiling for 15.1, so it's being straight forward. I'm anxious to see if it'll boot. :fingers-crossed:
As usual, I'll keep you posted.
htimsxela said:
Some news regarding the overall progress with LineageOS.
I checked out the repo from cm-14.1 (cyanogenmod 14.1) and am now trying to build for it. If it builds, at least we'll have Android 7.0.1 running on device. And - I believe - it could bring some light to start a port to a newer version (Lineage 15.1).
Up to now, I faced the same compile errors I got when compiling for 15.1, so it's being straight forward. I'm anxious to see if it'll boot. :fingers-crossed:
As usual, I'll keep you posted.
Click to expand...
Click to collapse
Thanks for your effort!
This phone is great and it's pity that it was left without support..
htimsxela said:
Some news regarding the overall progress with LineageOS.
I checked out the repo from cm-14.1 (cyanogenmod 14.1) and am now trying to build for it. If it builds, at least we'll have Android 7.0.1 running on device. And - I believe - it could bring some light to start a port to a newer version (Lineage 15.1).
Up to now, I faced the same compile errors I got when compiling for 15.1, so it's being straight forward. I'm anxious to see if it'll boot. :fingers-crossed:
As usual, I'll keep you posted.
Click to expand...
Click to collapse
BTW if someone is curious out there, here's the CyanogenMod 14.1 branch I'm working on: https://github.com/alexsmithbr/android_device_letv_max1/tree/cm-14.1
It was based on CyanogenMod 12.1 and the code is almost three years old (last commit), so I'm spending some time updating obsolete code, etc.
Donnie2Darko said:
Thanks for your effort!
This phone is great and it's pity that it was left without support..
Click to expand...
Click to collapse
Yeah, let's see if I can help changing this scenario.

Categories

Resources