Search results

try to change the filesystem to vfat and change it back to ext4 afterwards. This has the same effect has formatting it.

this doesn't change. but you can use the single layouts to remove the system1 functionality in advantage of a bigger system1 partition.

that's not possible(easily) because the partitions are in use while flashing zip's. Miflash should be pretty easy though.

The ROM works with the old partition layout as is. You just don't have much space for internal storage because the partition is mounted as a virtual SDCard now.

new? I published this before we could use CM. it's a modified 4.1 ROM.

If you still have that problem: I wrote a sensor HAL wrapper that emulates the Proximity using the light sensor. Needs some fine tuning but at least the screen doesn't stay black anymore :)

I'm not sure if this is a driver problem or not but you could give Miflash4Linux a shot(using a live cd e.g. Antergos).

thx :) It's hard to keep the balance between life and development because I tend to give up real life completely to work on a cool project. the reason why the time between my updates got that long is that I need to catch up on many real life stuff like learning for university.

hard to tell. as all people on miui.com he violates opensource licenses.

http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=102413&pid=2509935

well afaik he just downgrades the bootloader. why this wouldn't work anymore?

Well I don't have to trash all work. The multiboot init process still can be use. Also I got a lot of experience with bootloaders this way. Unfortunately there's no fully working G4A code. Both LK and GRUB will successfully bot, GRUB will inject the multiboot stuff into the ramdisk and will boot...

The bootloader is not related to your recovery problems. Everytime you install a MIUI ROM all bootloaders, modem and recovery get overwritten. G4A can protect itself(and any other partition) though thx to the live ramdisk patching technology. G4A has come very far, but when I started to...

this is not reliable on cm12 because it emulates one big partition even if u have two.

well first, this is totally untested and it could mess things up if you have the old partition table. secondly, CMRecovery aka SimpleReovery is intended for OTA only. CWM is dead.

then u won't have a bootloop anyway

no idea why u guys think that. the problem is totally unrelated(as far as I can say now). I never tested the ROM on merged partition layouts before publishing it - I am using the old one. But the ROM supports both layouts.

I think it's a PCB problem so it's impossible to fix it by replacing hw.

you're one of the lucky few then. Most people have very clean or even new screens and experience this bug every 15 minutes.

this is a different problem. what u are describing is the normal wet screen issue every device with a capacitive screen has. But this topic is a bout sth. completely different. Your screen is totally clean and dry and you're not touching your phone at all and the phone still acts like you'd be...