Ok,wtf, swap is working in stock rom but not in this??
WHY?
i will say this in a better way:
Could anyone compile a kernel which supports swap for this rom, i really need swap
Ok,wtf, swap is working in stock rom but not in this??
WHY?
Hello and thanks for your work!Updated Rom for those who are interested in, expect usual bugs. May Patchlevel LMY49J.
https://www.androidfilehost.com/?fid=24591000424955966
Sorry, but I think nobody will answere you because nobody cares about this phone.Hello and thanks for your work!
Could you please tell more detailed which are the "usual bugs" ?
Does this rom work smoother than CM11 nightly?
Because of the missing swap support its better to stay at stock htc rom?
Updated Rom for those who are interested in, expect usual bugs. May Patchlevel LMY49J.
https://www.androidfilehost.com/?fid=24591000424955966
You could try using a headset, see if that mic works.can anybody help me out please? i switched from stock rom to this yesterday, everything runs smoothly but facing a weird issue. i can make audio/video call through hangout/duo/imo but receiver cant hear my voice, although i can hear them. does anyone having this issue? Is it possible to overcome this or i need to switch back to stock rom?
btw i have flashed this rom, which is posted few pages back
nop thats not working as well. GSM calls working fine only voip calls not working. am i the only one who is facing this problem? anyway thanks for your help :good:You could try using a headset, see if that mic works.
Sent from my OnePlus 2 using Tapatalk
You're welcome. My M4 died suddenly over a year ago, along with all development. I was actually an active member of the M4 XDA community back then... Ah, good old days (-:nop thats not working as well. GSM calls working fine only voip calls not working. am i the only one who is facing this problem? anyway thanks for your help :good:
So I have build RR with Android 5.1
It seems like everything is working and is it quite smooth
Have fun with it
i'll report any bugs tho, THanksssssss:fingers-crossed:
Hey tombrazier the one bug that kind of came up when I flashed the boot.img by using the TWRP. After Iv'e done that the Notification area has Lost its transparency slider. It seems like there are Doubles of the Notifications when sliding it down. See in the images below. If this helps I flashed as image onto the Boot option in TWRP. Overall so far so good. The battery life while idle has lasted me 3 Days from 100% to 21% and that is a massive improvement from the Stock or any other ROMs that are available for this device.New boot.img: https://www.androidfilehost.com/?fid=745425885120734334
@ZiemlichUndead, it has the kernel you want with swap enabled.
It also has ZRAM enabled and low RAM improvements as recommended here: https://source.android.com/devices/tech/config/low-ram.
Also, battery charging is limited to 90% to save battery life (google for "battery university" to find out why). (You can undo that by removing "write /sys/class/power_supply/battery/full_level 90" from init.qcom.rc. Or ask, and I'll do it.)
Interesting. I had the same problem and eventually gave up on the latest CM ROM. Moved to the Resurrection Remix ROM posted by @Nous16, which is really good. Although I would not use the boot.img I posted with that.After Iv'e done that the Notification area has Lost its transparency slider.
You won't be able to edit it and change it permanently without creating a new boot.img. That's really easy if you know how (on Linux, I use abootimg to extract / create the boot.img file and you also have to use gzip and cpio to extract / create the initrd) but a pain if you don't.I would like to return to 100% of Battery but I seem to not be able to remove the line and apply it. I edit the init.qcom.rc by using the File Manager that CM Provides.
abootimg -x boot.img
mkdir initrd
cd initrd
cat ../initrd.img | gunzip | cpio -id
<edit init.qcom.rx to remove battery limit line>
find . | cpio --create --format='newc' | gzip > ../initrd.img
cd ..
<delete the "bootsize" line from bootimg.cfg>
abootimg --create boot.img -f bootimg.cfg -k zImage -r initrd.img
I am using the 2015/12/11 version of this ROM and its working fluently. As stated by the OP the only problem with it is the memory leaks. There is nothing else that I have found problems of. In conclusion thank you for making the boot.img with no battery charge changes that helped me a lot since I do not have time to learn all of this off for now. I am still new myself at much of the Android developmentInteresting. I had the same problem and eventually gave up on the latest CM ROM. Moved to the Resurrection Remix ROM posted by @Nous16, which is really good. Although I would not use the boot.img I posted with that.
You won't be able to edit it and change it permanently without creating a new boot.img. That's really easy if you know how (on Linux, I use abootimg to extract / create the boot.img file and you also have to use gzip and cpio to extract / create the initrd) but a pain if you don't.
Here's a version without the battery charge changes: https://www.androidfilehost.com/?fid=817550096634773113
For what it's worth here are the steps:
Code:abootimg -x boot.img mkdir initrd cd initrd cat ../initrd.img | gunzip | cpio -id <edit init.qcom.rx to remove battery limit line> find . | cpio --create --format='newc' | gzip > ../initrd.img cd .. <delete the "bootsize" line from bootimg.cfg> abootimg --create boot.img -f bootimg.cfg -k zImage -r initrd.img