Mourta

Members
  • Content count

    586
  • Joined

  • Last visited

  • Days Won

    70

Mourta last won the day on October 8 2016

Mourta had the most liked content!

Community Reputation

712 Excellent

1 Follower

About Mourta

  • Rank
    Addict
  • Birthday 08/02/1970

Profile Information

  • Location
    Stockholm

Previous Fields

  • Your Current Device(s)
    LG Optimus 4x HD

Recent Profile Visitors

3,338 profile views
  1. That is the sole reason, people like you. Wastes of space that can't figure out how to follow simple instructions. The BitBucket is updated (the only repository that is updated for our phone is mine, others are not following the GPL and apparently that is suddenly OK) and people are compiling it (i know Alogim is) and probably releasing it elsewhere (he asked permission to do so, i agreed) but i won't just because of complete arseholes such as yourself. I don't get your problem, i stopped releasing compiled code, what the hell else do you want from me?
  2. Nope, the solution has always been to let it boot fully, shut down, remove battery and wait a minute and then start it up. This problem is caused by a difference in regulators between the recovery (3.1 based) and my kernel (3.10 based). However, there are newer versions of everything, 6.0 does work, i am just not releasing new stuff because... well people would complain without reading instructions such as doing exactly what i said to do above and started whining about how when they badword it up with scripts it doesn't work as intended. You only have to do the remove battery procedure once, after that it works just fine until you reboot to recovery after which you'll have to do it again, it's not hard and it's not weird, it's just a mismatch problem. Also, you have to give it time, the optimization done in the background does take time and it won't sleep until it's done, this is also a one time thing. Also, any changes to anything what so ever is not supported and WILL NOT be supported, ever, i build ROM's that i use, if you feel that i have not done enough to optimize the gee whiz of the craptard in the bunkular or whatever the hell your fancy downloaded scripts say they will do then this is not a ROM for you. It's as is, try to butt heads with it and it will bite you in the arse.
  3. The space needed varies and as ccache fillls up it grows while compile time decreases. Good for you. You can now build pretty much any ROM you want to with minor fixes to the device tree and patches.
  4. Repos updated, don't forget to sync before you build, we're now using open source security services which means no more adaptations from user. Yeah, you read that right, no more of the bullshit, you compile it and you're done, you want to make changes then be a dev, test your changes and push them upstream, it's the only way to fix it.
  5. Remove device/lge/p880/patches/frameworks_opt_telephony. These patches are already in the Vanor Repo now. Then just run the build again.
  6. Depends on what hardware he's sporting. With enough memory and a decent CPU it may only take 3-6 hours. ;) Of course, you'll need about 20 or so cores to achieve a result under 6 hours and with most hardware it will take 12-15 hours. Just install Linux, you can install it as an application right there in windows and run it on a loop file on your windows partition that will expand with the amount of stuff you use in Linux.
  7. You'll need another 50GB to build it and preferably another 10GB for ccache. You'll only download that much once though, after that it's a few MB's that get downloaded every time you run ./build-mourta.sh
  8. Yeah, the hard work lies in making everything work together, after that it's just a waiting game.
  9. A simple way to build Vanir using my sources so you can change optimizations, settings or add to the project. You'll need a Linux version that is capable of building Android (it has to be 64bit), i recommend and use Ubuntu 16.04. Setting up your build environment: First of all, let's ensure you have the correct version of Java by removing whatever version you have: sudo apt-get remove openjdk-* icedtea-* icedtea6-* Then we'll install the correct version of java: sudo add-apt-repository ppa:openjdk-r/ppa sudo apt-get update && sudo apt-get install openjdk-7-jdk Now get the rest of the tools we need to build it: sudo apt-get install git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng maven Now let's get the tool we'll use to download all of the code: mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo Next up, let's ensure we can use "repo" and enable "ccache" by adding the following to ~/.bashrc: echo export PATH=~/bin:$PATH >> ~/.bashrc && echo export USE_CCACHE=1 >> ~/.bashrc Ensure that ~/.bashrc is read to activate the new variables: source ~/.bashrc Get the code: First make a directory to store the code in: mkdir -p ~/Source/Vanir Change to that directory: cd ~/Source/Vanir Now set up the repository: repo init -u git://github.com/VanirAOSP/platform_manifest.git -b m6 Get the code, this is over 50GB to download: repo sync Now get my stuff: curl -L -o .repo/local_manifests/roomservice.xml -O -L https://bitbucket.org/mourta/build-mourta-vanir/raw/005e513dfda3e9e04347edd3aeb2822a7f793a95/roomservice.xml && curl -L -o build-mourta.sh -O -L https://bitbucket.org/mourta/build-mourta-vanir/raw/005e513dfda3e9e04347edd3aeb2822a7f793a95/build-mourta.sh Sync it up again with my repos: repo sync Vanir needs to have vanir.mk under vendor/vanir/products/vanir_p880.mk to lunch properly so let's copy it to there: cp device/lge/p880/vanir.mk vendor/vanir/products/vanir_p880.mk Now build it, depending on your hardware this may take anywhere from 1 hour to 9 hours. ./build-mourta.sh You'll find your ROM in ~/Source/Vanir/out/target/product/p880/ when it's done. Happy building.
  10. If i release something new there will be a new thread for it.
  11. You could just not read my posts, that may be easier if me reporting what the testing version is capable of is causing these grave anger issues for you.
  12. Well given that i can use all new stuff from 6.0.1 in 4.4 it won't offer any benefits at all. Things like the new ART are easily backported to 4.4 so it will be better.
  13. You may be interested in knowing that Vanir 6.0.1 has been in testing for a while and while it's not 4.4.... I have to say that compared to Slim it's like night and day. Not quite done with the adaptations for a solid base yet but when we do reach that point it will be released in one version. Then NothingSerious updates come into play and i am banging my head at a wall for not realizing this sooner but the ROM actually has to be specifically built with that to work, most notably, our phone has to fake a Tegra4 in some cases, this is done by a very very simple patchup to allow it to create sync fences. With that and my new powermanager as well as the new tegra code (suspend to idle) we are going to have a very nice time with battery life and performance (the scores are fairly low but consistently over 23 000 which is promising since i haven't added one line of optimized options for this build yet. Well, except hardfp, Tegra4 GLES is hardfp so not using that is just silly.
  14. Perhaps if you try that question in the correct forum?
  15. No, i'll release it when i have time to finish and release something. It's up now and it's far from stable, it's a first look at what a good device and vendor will look like, i haven't even had the time to test it at all but i published it because i knew you wanted to build using my kernel (even though you proclaim it's your "new" kernel). I'm not in a good mood so don't push me. I've spent several months in a badword bunker and you ARE getting on my nerves with this "mourta is so easily offended so don't ask" bullshit.

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.