[rom][cm12.1] Last Hope Rom - Best Rom Ever? ;)


Damn, I remember the BLX thing from i9000 ;) Long time .... Completely forgot about that. I'll check if it's necessary for us ;)
I use it (Khaon's kernel) more than a year, all i can say is my battery stands still pretty damn good, more than 5 hours screen on time with the 2000 mah battery! A standard feature on most laptops also these days.It would be a useful feature if you manage to add this.Good luck with your CM13 rom man! :)
 
No you don't. Believe me ;)
I have Nexus line device and huge problems with battery drain because of Wifi (many things are on the Internet about that). I never seen drain that big before on any version.
Well i test the buggy ivan mi2 (mi2a port) 6.0 rom and i think battery was the only thing that was working fine and a friend with a nexus 5 told me that battery life was good again ....
i dont know why but i love new roms even if its a 5.1.0.1
 
Could you let me know steps to reproduce this problem? I've switch battery profile in settings -> battery -> battery profiles to power save then balanced and looks fine. Don't you go to performance? As I can see this could mess a little and will be fixed in RC4 ;)
The former method - in settings // battery // Battery mode.

Actually, I tried to look for "Performance" section now and cannot even find it. It used to be in the bottom section of the Settings near developer options in CM11, but things apparently changed in Lollipop...

EDIT: if you cannot reproduce the laggy behaviour, let me know, I would do a nandroid backup and retest.
 
Last edited:
I installed the rom 3 days ago, and everithing went fine till I restarted it :)

The only problem is that my "storage" partition is not mounted, and I dont really want to wipe and repartition my device again...
I tried mounting it from adb (and after its work searching a more persistent fstab or initscript like solution), but nothing work...

I tried:
root@aries:/dev/block # mount -t auto /dev/block/mmcblk0p27 /sdcard/sd2
mount: No such device

It would be enought for me if I just can mount it to somewhere where I can write it from computer and read it from VLC.
Any idea?

I'm using the old partition table (I get that rom, I never used miui, so I must be on the old partition system) with system+system1 blocks, modified system1 block (I made it bigger). I disabled tdb, flashed the rom to system2 in cwm so it has 1700mb, I resized my data and storage partitions to 4gb and 7gb, I see only the data partition. After my first boot there was 2 storage in windows when I connected the phone, now I only see the 4gb.

Code:
root@aries:/dev/block/platform/msm_sdcc.1/by-name # ls -la
lrwxrwxrwx root    root              2016-01-23 18:59 DDR -> /dev/block/mmcblk0p8
lrwxrwxrwx root    root              2016-01-23 18:59 aboot -> /dev/block/mmcblk0p9
lrwxrwxrwx root    root              2016-01-23 18:59 bk1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root    root              2016-01-23 18:59 bk2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root    root              2016-01-23 18:59 bk3 -> /dev/block/mmcblk0p21
lrwxrwxrwx root    root              2016-01-23 18:59 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root    root              2016-01-23 18:59 boot1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root    root              2016-01-23 18:59 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root    root              2016-01-23 18:59 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root    root              2016-01-23 18:59 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root    root              2016-01-23 18:59 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root    root              2016-01-23 18:59 m9kefs3 -> /dev/block/mmcblk0p16
lrwxrwxrwx root    root              2016-01-23 18:59 m9kefsc -> /dev/block/mmcblk0p14
lrwxrwxrwx root    root              2016-01-23 18:59 misc -> /dev/block/mmcblk0p10
lrwxrwxrwx root    root              2016-01-23 18:59 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root    root              2016-01-23 18:59 modem1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root    root              2016-01-23 18:59 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root    root              2016-01-23 18:59 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root    root              2016-01-23 18:59 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root    root              2016-01-23 18:59 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root    root              2016-01-23 18:59 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root    root              2016-01-23 18:59 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root    root              2016-01-23 18:59 storage -> /dev/block/mmcblk0p27
lrwxrwxrwx root    root              2016-01-23 18:59 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root    root              2016-01-23 18:59 system1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root    root              2016-01-23 18:59 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root    root              2016-01-23 18:59 userdata -> /dev/block/mmcblk0p26

root@aries:/dev/block/platform/msm_sdcc.1/by-name # df
Filesystem  Size  Used  Free  Blksize
/dev  962.3M  52.0K  962.2M  4096
/sys/fs/cgroup  962.3M  12.0K  962.3M  4096
/mnt/asec  962.3M  0.0K  962.3M  4096
/mnt/obb  962.3M  0.0K  962.3M  4096
/system  503.9M  472.2M  31.7M  4096
/cache  375.5M  6.2M  369.3M  4096
/data  4.4G  3.3G  1.1G  4096
/persist  7.9M  4.1M  3.8M  4096
/firmware  85.0M  50.6M  34.3M  16384
/data/qcks  20.0M  5.1M  14.9M  4096
/mnt/shell/emulated  4.4G  3.3G  1.1G  4096
/mnt/shell/emulated/0  4.4G  3.3G  1.1G  4096


root@aries:/ # ls -la | grep sdcard
lrwxrwxrwx root  root  2016-01-23 18:59 sdcard -> /storage/emulated/legacy
drwxr-x--x root  sdcard_r  2016-01-23 18:59 storage
 
How about trying to mount p27 in TWRP? (adb from PC, its mount command and file manager, or its shell.)
Alternatively, you can get some older bootloader made by Micha, which allowed to expose the complete emmc device to PC via USB and try to debug from linux.
 
I can mount it from CWM, but I want to see/reach those files on the phone too. So the partition is not broken just I cant reach it or mount it in a booted up device. I want to find a solution to this problem. (I have basic knowlage on linux type systems, but I have not enought knowledge in android systems and roms and there inside working and my friend; google cant help me)
(sorry if i was not clear in my first question)
 
Ah, sorry, I thought you just wanted to backup the internal storage to your PC.
I wonder if your problem is due to the old fs layout. Lollipop probably expects data and storage to be on a single partition (aka unified in Micha's flashtools).
Sorry, I do not know which files (properties) must be updated to get it work. It is probably not worth the effort, since you would have to modify them every time after CM update.
 
Ok and this is something I play for few hours last days ;) Everything is working except cellular but I'm chasing the problem (maybe someone have some experiences with debugging RIL? - Please PM me).

Anyway RC4 is on the way in next days. Stay tuned ;)


Screenshot_20160121-012106.png
Thanks to you,it's a real surprise.
And I know a bug in aosp6.0/6.01. It is named standby. Will you fix it in your CM13? Thank you.
 
I am not a developer,and I do not know what is the"standby".So it is just my guess.
My app after a period of time would be crazy to exit(killed), including qq and input methods as well as some other app, and then I reboot my device, everything has been running.
 
(probably lollipop bug)
After some hours of usage, about 1 day without reboot, background apps are killed more frequently, I have almost 800mb free ram, example:
- using browser for 20 seconds, when I return to home, launcher has been already killed (tried with trebuchet and nova) and take some time to reload
- using Tapatalk, go to other app, when I return to Tapatalk it has been already killed and seems not cached in ram
If I reboot all return normal
No xposed, clean install of rc3
Excuse for my English

Inviato dal mio MI 2S utilizzando Tapatalk
 
(probably lollipop bug)
After some hours of usage, about 1 day without reboot, background apps are killed more frequently, I have almost 800mb free ram, example:
- using browser for 20 seconds, when I return to home, launcher has been already killed (tried with trebuchet and nova) and take some time to reload
- using Tapatalk, go to other app, when I return to Tapatalk it has been already killed and seems not cached in ram
If I reboot all return normal
No xposed, clean install of rc3
Excuse for my English

Inviato dal mio MI 2S utilizzando Tapatalk
I have this problem too!
 
  • Like
Reactions: DaRoni and bialabs
I experienced this behaviour after I changed the Battery mode (see few posts earlier). Nova launcher and calender widget always redrew when coming back to Home. I reinstalled RC3 eventually... So may be the lagginess might actually be caused by terminated apps.
EDIT: well, it was probably just a coincidence of two issues at once. I still get home launcher redraws (inc. some widgets) but overall the phone is not laggy.
 
Last edited:
  • Like
Reactions: DaRoni
The terminating and applagging bug is come to me after take my phone to energy saveing mode, and switch it back to balanced. When I rebooted it, everything went fine again.


About my partition problem:
I can now mount the partition on adb (with mount -t ext4 /dev/block/mmcblk0p27 /sdcard/sd2) but the apps cant see the folder as a folder with my files, they just saw its original content (I gave permissions to the sd2 folder, but the phone and the adb sees diferent things :( ).

My questions:
Can I use some mount command that can make an fstab like "auto mount"?
How can I run an equivalent of "mount -a" on android after I tried to edit my fstab?
Can I edit something that can persistently overwrite the fstab.qcom file (as the / is a ramfs its cleard on shoutdown)?
Any idea how can I hack back the phone to automount both data and storage partition?
 
@EronHun Look at the thread of Ivan's Lollipop and compare what is different between the two versions. while fstab might work, Android uses fuse and deals differently with permissions.

[quote uid=133618 name="antoniosavio96" post=271166]Me too. I also tried the Mokee 5.1.1 "Double tap", but the battery drain is too high. This rom is the best Lollipop porting for the Mi2s! Now i get the last update (i had a old version, now i'm gonna see what's new with new 5.5.7!)[/quote]<br /><br />please note that 5.5.7 build linked in OP is the same as 5.5.3, but made for old partition layout [unmerged data - unmerged system].<br />5.5.3 build is for unmerged system - merged data.<br/>
 
(probably lollipop bug)
After some hours of usage, about 1 day without reboot, background apps are killed more frequently, I have almost 800mb free ram, example:
- using browser for 20 seconds, when I return to home, launcher has been already killed (tried with trebuchet and nova) and take some time to reload
- using Tapatalk, go to other app, when I return to Tapatalk it has been already killed and seems not cached in ram
If I reboot all return normal
No xposed, clean install of rc3
Excuse for my English

Inviato dal mio MI 2S utilizzando Tapatalk
Same here. Also, in opera (and probably other browsers), background tabs will reload when selected. I did not notice any of the above behaviour using Last Hope prior to RC3.