chil360

Members
  • Content count

    332
  • Joined

  • Last visited

Community Reputation

661 Excellent

About chil360

  • Rank
    Diehard

Previous Fields

  • Your Current Device(s)
    Moto G3, Huawei Ascend Y300

Recent Profile Visitors

4533 profile views
  1. For this week's build, I thought I would try building with a different set of toolchains. Previous build have been built with Uber 4.9 for the kernel and stock google 4.9 toolchain for the rom (Using Uber for the rom causes a bootloop). The toolchains used in today's build are BenzoSM Sabermod 4.9 toolchains for both rom and kernel, built by me, and configured specifically for msm7x27a devices (cortex-a5, neon-vfpv4). Let's see if it makes any difference. If anyone else is interested in using these toolchains, I have uploaded them here.
  2. Today's build is delayed. The build failed and I'm still trying to fix it. Update: Should now be fixed. Just started a fresh build.
  3. Switchable Internal/External SD as Primary storage There have been a number of posts here recently about using the external SD card as primary storage, especially as the 'Adoptable' storage feature just doesn't seem to work with problems re-formatting the card. I have wanted to make a way to switch the storage from Settings without reformatting and encrypting for a while (just like we had in our kitkat & lollipop roms) but could not work out a way to do it. I have finally thought of a way to implement this and have added it to this weeks build for you to try out - just toggle the switch from Settings -> Storage & USB and reboot. Please try it out and let me know how it goes. Implementation: For those interested in how I did it... @dmitr posted this zip which installs a boot.img where the SD card entries have been switched in the 'fstab.huawei' file. This works but I would like to be able switch from Settings without having to flash any extra zip files. My approach is to have 2 fstab files, 'fstab.huawei' & 'fstab.huawei.switched' and patch vold to choose between the 2 files when it initializes based on a property that can be toggled from Settings. This seems to work without any side effects. Other approaches I tried worked to switch primary storage but caused problems accessing the cards with MTP. The changes to implement this have been published in my github repos.
  4. I had kind of given up on Slim. Since their 'Slim Zombie' phase (see 'Slim Zombie?' post on https://slimroms.org/), they haven't released any official build for any device and the development has been incredibly slow. But now, they have just started publishing official weekly builds of Slim6 for a few devices - although there's hardly any features added to it yet. I have made a test build for the Y300 but haven't decided if I want to publish it yet. One reason is that I cannot fully test it as I no longer have a correct sized sim card (I now have a Moto G which uses a micro sim). I know I could get an adaptor but I just haven't so far and I don't want damage my micro sim by trying to use it in my Y300. If there is interest, I could publish a build of Slim6 or at least publish the device tree changes so someone else could build & support it.
  5. No, it's not included in today's build. I intended to test it this week but just didn't get the chance. It would help if some more people could test it this week and report back if this does indeed fix the problem. If it does, I will include it in next week's build.
  6. Thanks for sending this - I will try it and see what happens. I have had a look inside and see that you are replacing mpdecision & sensorservice. Replacing mpdecision won't have any effect as the kernel has been configured to use intelliplug instead so mpdecision has been disabled by default. For sensorservice, I would prefer to build from source so if you have the code changes that would be good or is this taken from an old android build?
  7. If you send me what needs to be changed or create a pull request through github then I will test it out and add it to the rom. It would be great to have a proper fix for this issue.
  8. @knoelli Wifi: Try enabling 'Use legacy DHCP client' from Developer Options and rebooting. This can help in some cases to stabilize the wifi connection.
  9. All of the source code for my builds are in my github repos here (device trees) and here (kernel). See the local_manifest repo for build instructions.
  10. hello What to do, if proposes on my y300???

  11. Feel free to take over the builds then, @Nemesix2! I have been working on this device for a long time and have been unable to fix the problems that remain. So, if someone wants to take over, then go ahead.
  12. @Nemesix2 The lib file I mention in the first post is installed by OpenGapps. It's not compatible with AOSP Keyboard so causes the keyboard to crash. I currently have the latest 14/02 build installed on my phone without gapps and the keyboard is working fine.
  13. No. I have tried building with Snap camera and it works ok for taking photos but fails when trying to record video. It crashes out then you get the 'can't connect to camera' message. I'm going to experiment with it some more this week to see if I can get it working.
  14. The permissions system in Marshmallow has changed significantly. The apps that fail probably need updating to work properly with the new Marshmallow APIs.
  15. True, but if I start customizng the rom people could complain that they use something that I have removed or demand their preferred alternatives to any apps that I add. It's better to keep it stock CM and use file-based rom zips so people can customize it themselves if they wish to.

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