• Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by adeii

  1. Lineage OS (rebranded CyanogenMod) 13.0 Unofficial builds for Huawei Y300/G510/G330 Disclaimer: CyanogenMod and I are not responsible for any damages to your device. Download: -!F1hmmICR!22r532OdQ_gwphqHy9kwCg (G330 has extra - overclocked kernel to 1.3GHz) GApps: I would recommend microG as workaround replacement for GApps, but you can use Opengapps (ARM/6.0) Pico and got a long lags. Using GApps slows the phone considerably so I would advise using minimal GApps editions. With Opengapps, it must be installed at the same time as the rom. Installing at a later time causes FC's when the phone is rebooted. OpenGApps Note: To fix AOSP keyboard with opengapps pico remove the file: /system/lib/ Current Status: Working so far: It boots successfully, display works, touchscreen & buttons all work ok GPS Wifi Bluetooth Audio Video playback (software decoding) Internal & External SD Card - Internal set as primary storage, External is adoptable. <-- DON'T "erase and format SD" from system! Use PC or recovery mode or aparted app. Phone/Data - Needs testing! Rild & libril now built from source using custom libril based on CM13 hardware/ril-caf with a commit from LegacyHuawei. <-- It works with CM13 RIL! Camera @ 5MPx Not Working: Video playback (hardware decoding) FM Radio - still no audio output Comments/Known Issues: Wifi: When configuring wifi during the setup wizard, wifi connects to the access point but sometimes doesn't make an internet connection. Skip through the setup wizard, go to Settings -> Wifi, turn off wifi, turn it back on and it will connect successfully. Mobile Data: If mobile does not connect when enabled, turn on aeroplane mode, wait a few seconds then turn off aeroplane mode. When the phone reconnects to the network it should also successfully connect the mobile data. Now that the initial connection has been made, you should be able to disable and enable mobile data as required and it will connect. Sources: CyanogenMod - Device Tree - Kernel - Credits: chil360 CyanogenMod Dazzozo TeamHackLG Christopher83 moddingg33k mrg666 srfarias fonz93 wbrambley ... and many more contributors!
  2. I dont know what the fault with microG and Magisk. But try new build, ported june build with deodexed apps and frameworks from october build. MicroG works definetly, booting is long, but all works (except FM).
  3. Thanks for idea: compressing .png but in source, before building? apps are already odexed to speed up execution, but take more space on /system.
  4. ok. 1) flash ROM and reboot to system*, 2) restart to recovery and flash, 3) then go to settings > apps > advanced > app permissions > spoof package signature > enable microG Service Core and Google Play store** 4) go to microG settings: google device registration to ON, google cloud messaging to ON, google safetynet to ON, unifiedNlp settings - click on configure location backends, enable mozilla location service*** later, back to configure address lookup backends and enable nominatim. go to self-check and all items under Signature spoofing support and Installed packages should be checked/enabled. Enable all 4 items under Permission granted. Now enable mozilla location service. And thats all. * if you flash rom and microG, you must login to google to finish initialisation, since you don't enabled spoofing and various permissions, login last to eternity. ** sorry for bad path, you got spoof pack.sign. AFTER installing microG. *** can not be enabled for now, leave it for the end. Also try Resurrection Remix 5.7.4 rom - there microG works fine.
  5. I dont get it - in new build, BT and Camera do not work, for the first time in LOS! That is offen problem with kk or mm roms for our phones. UPDATE: rebuild with clean build, no errors, but BT/Camera still dont works. Also tried to port october build (apps, framework, priv-apps) on march build, these still dont work.
  6. Hello, Carontes. /framework/services.jar and /priv-apps/Settings/Settings.apk is already patched in june and next october build. Since those are odexed roms (apps got fewer *.apk part and additional *.odex part, frameworks got little *.jar and big *.odex part etc), those roms can not be patched. Have you already enabled signature spoofing for microG framework and google play store? If not, go to settings > apps > advanced > signature spoofing (only in patched rom) and enable both apps. Also in microG settings, enable logging-in, google cloud messaging, safety net, uln settings etc.
  7. Yepp, new approch in MM. Now it use serial numbers of sd cards as identifier. You can use /mnt/media_rw (or /mount/ .... or else) but still got 3257-984D and 91B7-C9FA. But /sdcard is for internal sd. Maybe apps like Folder Mount or Apps2SD can make symlink from /storage/3257-984D to /mnt/sdcard0 or /storage/sdcard0... I dont know correctly. For making 128MB swap from /cache, try script from this post or App2SD for few swap files on /system, /data, /sdcard0 etc. Google updated MM to 6.0.1_r81, so new LOS 13 build should be made till the end of October.
  8. I meant just NanoMod-microG-14.3.x (~30 MB), not need for whole pack (~188 MB). Does microG settings work well?
  9. @Einsam Teufel, try to add +128 MB cache with this script. (if you need BusyBox, newest 1.27.2 for ARM by YashdSaraf ) newest NanoMod microG binaries (flashable) by Nanolx Last one, 14.3.x should works on LP/MM/N roms, in Archive can be found and 9.x that works on KK roms also. Also in Settings > Apps > advanced, enable Signature spoofing for Google Play services and Google Play store, and enable all check-ins in microG settings to got full functional gapps replacement (store, youtube, gmail, hangouts old ver. 10.x works).
  10. exactly! nor after call. You can use touchpad and screen during call i.e. to see call duration, contact no. or to finish call. With enabled sensor, phone "forget" to turn on screen on distance or after call.
  11. Constant restarts

    this post
  12. MM roms have them rarely. If you experience BS during and after call, that can be cause by proximity sensor. In RR 5.7.x roms, sensor can be disabled in Dialer - Settings - Calls... for others, can block whole sensor with script.
  13. - Do you have problem with Nova only? Any other launcher work well? Do you use zRAM or cache for virtual memory? Max. zRAM can be 128 MB (in Kernel adiutor 120 MB). Wipe /cache partition from recovery mode and try again Nova. RR 5.7.4 is signature spoofed, so you can use microG (NanoMod microG is better), instead pico OpenGapps. Mini, micro, even nano OpenGapps are massive for our phones. ...
  14. Do you use Email app of Exchange app from ROM? Or you had install GMail without OpenGapps or microG ?
  15. OK. Newest SlimKat 9.1, android 4.4.4_r2.0.1, Display-legacy, BT-caf, audio/media-caf, NFC-caf, without any additions is build: (yes, for G330 and Y300 users too!) Kernel is compiled with UberTC 4.9, like SlimKat 9.1 CAF and SlimLP and OctOS KK and DU 8.2 and AICP 7 etc. I don't know if NFC works (G510 only), BT works from second boot pritty OK. And we got usual uploading problem - phone reboot/restart on wifi uploading. on example after 33kB. If you flash chil360's kernel for SlimKat 9.0, compiled with gcc 4.7, uploading works OK, NFC should works too. (SlimKat9L-kernel-v0.53 on download folder) I did test: repack sk91 kernel with ramdisk files from sk90 kernel ( /sbin and /wifi folder, default.prop and init ), and zImage remain from sk91 ubertc4.9 as SlimKat91L-kernel-mixed = wifi uploading works! . So, now we have SlimKat 9.1 Legacy working. Maybe the repacking with MM (LOS 13) kernel, someday, can solve SlimKat 9.1 CAF's problem with wifi uploading (and all other derivates' problem)!
  16. Does someone had problem with wifi uploading that restart phone?! Problem solved - repacked boot for latest u8951 build, with MM kernel (from Lineage 13 u8951) work well for Y300 and G510! download from AFH and flash it.
  17. I dont know, but it is official build. Should work.
  18. I guess it is for ported rom from G300 to G510. G300 device tree do not have NFC drivers/firmware to load. Do you have NFC tagging problem with SlimKat 9.0 legacy, SlimKat 9.1 CAF for G510? At the first, bluetooth also didn't work, because g510/y300 load driver from /system/lib/ and g330 load from /system/vendor/lib/, and overwriting g510/y300 *.so to /vendor/lib/ make BT works. Maybe NFC *.so from /system/lib/ (libnfc*.so ) need to be copied to /system/vendor/lib/ to work. If not, slimkat 9.1 legacy for g510 had to be built, but I have no time to do it....
  19. This one is better :)
  20. Yes, can be done soon. Just using slimkat u8951 9.0 legacy as base, in stead of u8833. UPDATE: G330 and G510 builds are done and uploaded at G510 users - all working for now, but NFC tagging. G330 users - all should work, there are hardware diff in audio and RIL, so I can not test them on Y300 (no RIL and no audio at mine)
  21. Hi and sorry for late answer. To re-enable proximity, you need to delete file /system/etc/init.d/98-disable-sensor and reboot. After reboot be sure that file /dev/proximity have no 000 file permissions, but exp. 755.
  22. I tried to made new MM roms for our huawei device, but got almost the same severe errors - bluetooth can not be turned on, camera brokes every time, no ril (phone/sms/gprs), no root! NOTE: Roms are CAN NOT be using for daily use, roms are not fully working, flash on your responsibility! This thread is made just for few people that want to experience new rom, repack some framework/module/bin/lib from working 6.0.1 roms or suggest patches for these or even recompile rom to working one. OMNIROM 6.0.1 - problems: no root*, no BT, no camera* download OMNI-u8951 . . . device tree crDroid 6.0.1 - problems: no BT, no camera download crDroid-u8951 . . . device tree CarbonRom 6.0.1 - problems: no root*, no RIL, no camera, no CarbonFibers (custom settings panel) download Carbon-Lux-u8951. . . device tree OctOS 6.0.1 - problems: no root*, no BT, no camera download OctOS-M-u8951 . . . device tree * rooting can be fixed, if you are using CWM-6.0.x.x recovery, cause it has "fix root?" option after flashing rom, before reboot. After first start, you can flash SuperSU system mode only to works! Regular is systemless mode and can not work. If you using TWRP-3.x.x recovery, recovery reboots before finishing rom flashing, because of supersu (flashing modd image to boot), to non-root system. Without supersu, works fine as non-root. * camera may works on omni, if you install open camera, xposed framework and marshmallow sd fix module (set all apps to yes).
  23. Vanir AOSP 6.0 - problems: no BT, no camera but rom ported upon LineageOS (march build), works good: download vanir_u8833 . . . device tree
  24. SlimKat 9.1 display-legacy ported for Y300 --> - mister wbrambley made slimkat 9.1 legacy on 30.jan.2016. for Huawei G300, thanks to him! - I use the latest chil360' slimkat 9.0 legacy for Y300 as base and overwrite app/frameworks/media/priv-app from 9.1 legacy. - Changes between G300 and Y300 are in audio driver, audio policy and bluetooth driver (and maybe kernel) - Now, we got fully woking SlimKat 9.1 legacy for G510/Y300 (G330 user should use audio_policy.msm7x27a and audio_primary.msm7x27a from G300 build). - ONLY bug is that bluetooth can not be turned on only on the first boot. After restart all works normally. - additions: proximity sensor and media scanner are disabled, 128 MB cache and fstrim are added, busybox is updated.
  25. Y300 roms to G330

    Well, these 2 files should be kernel (boot.img) and lib/hw/audio.primary.msm7x27a Extra: should be lib/hw/audio_policy.msm7x27a, system/etc/audio_policy.conf, lib/ + change /build.prop line gsm.version.baseband=1040

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