Guest chil360 Posted April 25, 2015 Report Posted April 25, 2015 SlimLP 5.1 sources are out and buildable but they are a long way behind cm12.1. Only a few of the features and fixes have been merged into 5.1 so far and it is not yet ready for daily use. Today, I have published device tree changes and a local manifest to build SlimLP 5.1 in it's current state. There isn't much point in publishing builds at this point but as soon as Slim start weeklies again I will do the same for our devices.
Guest fonz93 Posted April 25, 2015 Report Posted April 25, 2015 SlimLP 5.1 sources are out and buildable but they are a long way behind cm12.1. Only a few of the features and fixes have been merged into 5.1 so far and it is not yet ready for daily use. Today, I have published device tree changes and a local manifest to build SlimLP 5.1 in it's current state. There isn't much point in publishing builds at this point but as soon as Slim start weeklies again I will do the same for our devices. Hey, i saw you switched to CyanogenMod's hardware_atheros_wlan, is it for a specific reason?
Guest chil360 Posted April 25, 2015 Report Posted April 25, 2015 Hey, i saw you switched to CyanogenMod's hardware_atheros_wlan, is it for a specific reason? Not really, just that the cm repo is a few commits ahead of mine (ignoring unsupported commands) and actively maintained. No point keeping our own repo if the cm one works.
Guest Jairus1998 Posted April 25, 2015 Report Posted April 25, 2015 @chil360 Can I know when you going to publish the SlimLP 5.1. An estimation will do
Guest chil360 Posted April 25, 2015 Report Posted April 25, 2015 @chil360 Can I know when you going to publish the SlimLP 5.1. An estimation will do That's a question you need to ask Slim not me. I have no idea how long it will take them to add the rest of the features and get the rom into a state fit for everyday use. I can't see much point in releasing builds until the Slim weeklies start.
Guest Kiodo1981 Posted April 26, 2015 Report Posted April 26, 2015 I'm trying to build it but this error occured. $ source build/envsetup.sh including device/generic/mini-emulator-x86/vendorsetup.sh including device/generic/mini-emulator-mips/vendorsetup.sh including device/generic/mini-emulator-arm64/vendorsetup.sh including device/generic/mini-emulator-x86_64/vendorsetup.sh including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh including device/huawei/msm7x27a-common/vendorsetup.sh applying bionic to bionic Applying: cortex-a5 support applying build to build Applying: msm7x27a support applying external_wpa_supplicant_8 to external/wpa_supplicant_8 Applying: wpa_supplicant: reduce scan timeout to workaround ar6000 problem applying frameworks_av to frameworks/av Applying: Add msm7x27a for DirectTrack and legacy audio Applying: libstagefright: Enable meta mode for 7x27a video encoder Applying: Don't store metadata in video buffers - we don't support it. applying frameworks_native to frameworks/native Applying: Select texture target based on pixel format applying hardware_libhardware_legacy to hardware/libhardware_legacy Applying: wifi: add support for custom Wi-Fi implementations applying system_core to system/core Applying: Add path for wifi firmware applying system_netd to system/netd Applying: Update Huawei SoftapControllerATH for 5.0 including vendor/slim/vendorsetup.sh including sdk/bash_completion/adb.bash [casarch@casarch android]$ brunch u8951 including vendor/slim/vendorsetup.sh Trying dependencies-only mode on a non-existing device tree? ============================================ PLATFORM_VERSION_CODENAME=UNOFFICIAL PLATFORM_VERSION=5.1.1 SLIM_VERSION=Slim-5.1.1.alpha.0.1-UNOFFICIAL-20150426-1140 TARGET_PRODUCT=slim_u8951 TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a-neon TARGET_CPU_VARIANT=cortex-a5 TARGET_2ND_ARCH= TARGET_2ND_ARCH_VARIANT= TARGET_2ND_CPU_VARIANT= HOST_ARCH=x86_64 HOST_OS=linux HOST_OS_EXTRA=Linux-3.19.3-3-ARCH-x86_64-with-arch HOST_BUILD_TYPE=release BUILD_ID=LMY47V OUT_DIR=/home/casarch/android/out ============================================ ============================================ PLATFORM_VERSION_CODENAME=UNOFFICIAL PLATFORM_VERSION=5.1.1 SLIM_VERSION=Slim-5.1.1.alpha.0.1-UNOFFICIAL-20150426-1140 TARGET_PRODUCT=slim_u8951 TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a-neon TARGET_CPU_VARIANT=cortex-a5 TARGET_2ND_ARCH= TARGET_2ND_ARCH_VARIANT= TARGET_2ND_CPU_VARIANT= HOST_ARCH=x86_64 HOST_OS=linux HOST_OS_EXTRA=Linux-3.19.3-3-ARCH-x86_64-with-arch HOST_BUILD_TYPE=release BUILD_ID=LMY47V OUT_DIR=/home/casarch/android/out ============================================ File "build/tools/findleaves.py", line 95 print r ^ SyntaxError: Missing parentheses in call to 'print' File "build/tools/findleaves.py", line 95 print r ^ SyntaxError: Missing parentheses in call to 'print' File "build/tools/diff_package_overlays.py", line 88 print r ^ SyntaxError: Missing parentheses in call to 'print' PRODUCT_COPY_FILES frameworks/base/data/keyboards/Generic.kl:system/usr/keylayout/Generic.kl ignored. PRODUCT_COPY_FILES frameworks/base/data/keyboards/AVRCP.kl:system/usr/keylayout/AVRCP.kl ignored. PRODUCT_COPY_FILES frameworks/base/data/keyboards/qwerty.idc:system/usr/idc/qwerty.idc ignored. PRODUCT_COPY_FILES frameworks/base/data/keyboards/qwerty2.idc:system/usr/idc/qwerty2.idc ignored. PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored. PRODUCT_COPY_FILES device/generic/goldfish/camera/media_profiles.xml:system/etc/media_profiles.xml ignored. PRODUCT_COPY_FILES device/generic/goldfish/camera/media_codecs.xml:system/etc/media_codecs.xml ignored. PRODUCT_COPY_FILES hardware/libhardware_legacy/audio/audio_policy.conf:system/etc/audio_policy.conf ignored. No private recovery resources for TARGET_DEVICE u8951 make: *** Nessuna regola per generare l'obiettivo "/home/casarch/android/out/host/linux-x86/bin/mkbootimg", necessario per "/home/casarch/android/out/target/product/u8951/boot.img". Arresto.
Guest luca020400 Posted April 26, 2015 Report Posted April 26, 2015 (edited) I'm trying to build it but this error occured. You are using archlinux so you have to create virtual venv cd android virtualenv2 venv ln -s /usr/lib/python2.7/* venv/lib/python2.7/ . venv/bin/activate Before every build . venv/bin/activate Archlinux use by default python 3.4 but android build system supports only python 2 Next time read thw wiki PLEASE Edited April 26, 2015 by luca020400
Guest Runjaun Posted April 28, 2015 Report Posted April 28, 2015 Can i install cm12 without deleting data?. I am using slimlp
Guest fonz93 Posted April 28, 2015 Report Posted April 28, 2015 Can i install cm12 without deleting data?. I am using slimlp No
Guest killadroid Posted April 30, 2015 Report Posted April 30, 2015 (edited) check www.slimroms.eu for info on new builds Edited April 30, 2015 by killadroid
Guest herrdeh Posted May 1, 2015 Report Posted May 1, 2015 (edited) Hi friends, months ago I said goodbye to google and removed play services, play store, maps and all that stuff. For localisazion services, I'm using UnifiedNlp: https://github.com/microg/android_packages_apps_UnifiedNlp Google's accuracy is better - but UnifiedNlp costs way less battery and cpu power. And with many people supporting it, results will improve. There are some apps which wont work with UnifiedNlp's localisazion service, the reaons are described here: https://github.com/microg/android_packages_apps_UnifiedNlp/issues/36 As a play store replacement, I'm using aptoide: http://aptoide.com Now I have just one payed app which will not work - all the others do, and I get updates as well. Really amazing to me is, how much more responsive my phone is without gapps, all the laggyness is gone - and how much battery duration has improved. At little usage, I came up to 40hrs, at normal usage, 24hrs is no problem with a now more that 2 years old battery. For bare navigation, I like mapfactor navigator: http://navigatorfree.mapfactor.com/en/ Quite slimline and fast, and for me (mainly being a pedestrian and cyclist, hardly ever a car driver) the OpenStreetMap base is ideal, as it contains much more of the small pathways than google maps does. A real flaw is that I didnt find a good replacement for a location based search engine as google maps. But it was so extremely slow on my Y300, that I'm only crying very few tears about it. I can use it on Opera mobile (not mini!) browser - but not really well. German yellow pages dont work well either. Conclusion. I'm happy without gapps, the advantages do surmount the disadvantages for me. Cheers, Wolf PS: I'm using 4.4.4. still - and looking forward for LP reaching beta status Edited May 2, 2015 by herrdeh
Guest dkr84 Posted May 1, 2015 Report Posted May 1, 2015 After using this rom for couple of days without gapps I must say that this one is phenomenal! No random reboots, ridiculously smooth.. One question concerning battery drain issue.Sometimes I have 1 30 h on screen time, sometimes 2 h, but it's almost always below 2h on screen time without using that much wifi and almost no 3g. Is it going to be fixed with 5.1 update? Or is this issue going to persist on lollipop roms for our phone in all future updates?
Guest pinky0978 Posted May 1, 2015 Report Posted May 1, 2015 Herrdeh, try navfree for maps, works offline so much quicker than Google maps, not sure if it will work with network location though??
Guest juanpablocastillo Posted May 1, 2015 Report Posted May 1, 2015 Herrdeh, try navfree for maps, works offline so much quicker than Google maps, not sure if it will work with network location though?? Or OSMAnd, it's open-source, it has a offline mode and is very fast, for me at least. :P
Guest herrdeh Posted May 2, 2015 Report Posted May 2, 2015 I added some remarks on navigation above. What I'm really missing is a location based search engine, which I thought was a main purpose of google maps.
Guest Kiodo1981 Posted May 8, 2015 Report Posted May 8, 2015 (edited) Chil360, could you please build just the new kernel? Any WiFi bug or black screen? I can build it if someone gives me the instructions Edited May 8, 2015 by Kiodo1981
Guest TheNemesis584 Posted May 9, 2015 Report Posted May 9, 2015 Chil360, could you please build just the new kernel? Any WiFi bug or black screen? I can build it if someone gives me the instructions U can use his sources from the Github
Guest chil360 Posted May 9, 2015 Report Posted May 9, 2015 (edited) @Kiodo1981 I have uploaded a kernel build based on my currently published sources to basketbuild: chil360-kernel-20150509-2043-slimlp.zip. Wifi is more stable but can have blackscreens. Black Screen Issue: It has been suggested that my recent mega kernel update of CAF commits may have introduced this black screen problem. These commits were added to bring the memory management up to date with CAF kk_2.7-stable and to fix the zram 'Error writing to swap device' issue. As the black screen issue is difficult to reliably reproduce, I have just uploaded to 2 test kernel builds to basketbuild and I ask if you all could test them and report back if you see black screens. chil360-kernel-TEST_1.zip - This is built from my lp5.1 branch at this commit. This point in the commit history is about the minimum to fix the zram 'Error writing to swap device' issue. chil360-kernel-TEST_2.zip - This build contains everything from test 1 plus most of the mm/cma/dma commits. The main thing I have left out are all of the perf commits. Edited May 9, 2015 by chil360
Guest dkr84 Posted May 9, 2015 Report Posted May 9, 2015 (edited) Do I need a repack of these kernels for Cm 12.1 and F-AOSP? Edit: Obviously Edited May 9, 2015 by dkr84
Guest juanpablocastillo Posted May 9, 2015 Report Posted May 9, 2015 Do I need a repack of these kernels for Cm 12.1 and F-AOSP? Edit: Obviously Nope, because fonz used exactly the same kernel source for compile those ROMs. Currently testing TEST 2 kernel. I will report later
Guest dkr84 Posted May 9, 2015 Report Posted May 9, 2015 Nope, because fonz used exactly the same kernel source for compile those ROMs. Currently testing TEST 2 kernel. I will report later Ok. Thanks. I'm gonna try CM 12.1 with these kernels...
Guest chil360 Posted May 9, 2015 Report Posted May 9, 2015 They would need to be repacked for other roms so that they use the correct ramdisk.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now