CyanogenMod 12.1 - Lollipop - Discussion

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
Anyone have issues watching video on YouTube? Mine is garbled, shakey and hangs, but the audio keep playing.
works fine here. on 7/18, latest youtube from Play. tested planet earth and bumped it up to 1080p (720p was also fine). SD content appeared ok too (quick test).
 
  • Like
Reactions: tschmid

beady_uk

Senior Member
Jul 22, 2010
235
54
0
This rom is awesome but I can't copy any file larger than 2gb to any storage (internal nand or external SD). I have ran a terminal and typed "mount" and it shows system, cache and data are mounted as ext4. Logcat does not show anything

Does anyone know how to solve it?

Thanks
 
Last edited:

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
This rom is awesome but I can't copy any file larger than 2gb to any storage (internal nand or external SD). I have ran a terminal and typed "mount" and it shows system, cache and data are mounted as ext4. Logcat does not show anything

Does anyone know how to solve it?

Thanks
i used MTP (windows to tab) via USB to transfer a 3.24GB File. Seemed ok.
 

beady_uk

Senior Member
Jul 22, 2010
235
54
0
Can you try within the tab? ie. Micro SD to internal.
I tried cm file manager which crashed around 2gb and es file explorer which just failed at 2gb.
Thanks
 

beady_uk

Senior Member
Jul 22, 2010
235
54
0
i used MTP (windows to tab) via USB to transfer a 3.24GB File. Seemed ok.
Can you try within the tab? ie. Micro SD to internal.
I tried cm file manager which crashed around 2gb and es file explorer which just failed at 2gb.
Thanks
So i have transfered some movies to my micro sd card using a USB adapter on windows. The problem now is that when i play them they crash, at around the 2gb point. something is very strange with this. Has anyone else got this problem?

Thanks
 
Last edited:

beady_uk

Senior Member
Jul 22, 2010
235
54
0
So i have transfered some movies to my micro sd card using a USB adapter on windows. The problem now is that when i play them they crash, at around the 2gb point. something is very strange with this. Has anyone else got this problem?

Thanks
So i have now done a full wipe and i am still getting this issue, but to make it more confusing - i can copy from the dock SD card to the internal nand. but not from dock sd to dock usb or micro sd. I cannot copy from dock USB or the micro sd card to nand.
Is there anything i should look for? Im not sure what else to try.
Thanks
 
Last edited:

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
So i have now done a full wipe and i am still getting this issue, but to make it more confusing - i can copy from the dock SD card to the internal nand. but not from dock sd to dock usb or micro sd. I cannot copy from dock USB or the micro sd card to nand.
Is there anything i should look for? Im not sure what else to try.
Thanks
ill do some testing to see if i can reproduce this on my end and get back to you.
 
  • Like
Reactions: beady_uk

beady_uk

Senior Member
Jul 22, 2010
235
54
0
ill do some testing to see if i can reproduce this on my end and get back to you.
Thanks for the help.

Not sure if its related but I tried TWRP touch recovery a few weeks back but got errors when trying to do wipes so I moved back to CWM 6.0.5.1. And now when I flash ROMs I get a message saying "patching system image unconditionally".
 

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
"patching system image unconditionally".

that 'should' be ok for CWM the last time I checked (which was some time ago).

you can flash with CM recovery if you have doubt.
 
  • Like
Reactions: beady_uk

beady_uk

Senior Member
Jul 22, 2010
235
54
0
"patching system image unconditionally".

that 'should' be ok for CWM the last time I checked (which was some time ago).

you can flash with CM recovery if you have doubt.
Thanks
Is there anyway i can "reset" everything, like partition tables, to stock and then start again. Just incase TWRP has messed anything up cos i have never seen "patching system image unconditionally" untill i tried TWRP touch recovery.
 

beady_uk

Senior Member
Jul 22, 2010
235
54
0
"patching system image unconditionally".

that 'should' be ok for CWM the last time I checked (which was some time ago).

you can flash with CM recovery if you have doubt.
Thanks
Is there anyway i can "reset" everything, like partition tables, to stock and then start again. Just incase TWRP has messed anything up cos i have never seen "patching system image unconditionally" untill i tried TWRP touch recovery.
OK so after more investigation i dont think this is rom related. I tried zombi-pop rom and i still get this issue. Although that is based off cm12.1 i think this is a problem with my tab. Is there anyway i can flash the whole thing back to stock and start again? this has only happened since i tried TWRP.

thanks
 

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
OK so after more investigation i dont think this is rom related. I tried zombi-pop rom and i still get this issue. Although that is based off cm12.1 i think this is a problem with my tab. Is there anyway i can flash the whole thing back to stock and start again? this has only happened since i tried TWRP.

thanks
Take any media off of /data/media if you have any.

1. Enter Bootloader
2. fastboot boot CWM
3. flash latest stock rom (from droidbasement (only US available)) using CWM (from droidbasement).
4. reboot to bootloader
5. fastboot flash latest stock recovery (from droidbasement)
6. factory reset from bootloader
7. Boot in.

to go back:
1. fastboot boot CM recovery
2. adb shell, mount /data and transfer latest rom and gapps (if you use them; link on droidbasement) via ADB.
3. flash rom and [gapps]
4. Boot in.
 

beady_uk

Senior Member
Jul 22, 2010
235
54
0
Take any media off of /data/media if you have any.

1. Enter Bootloader
2. fastboot boot CWM
3. flash latest stock rom (from droidbasement (only US available)) using CWM (from droidbasement).
4. reboot to bootloader
5. fastboot flash latest stock recovery (from droidbasement)
6. factory reset from bootloader
7. Boot in.

to go back:
1. fastboot boot CM recovery
2. adb shell, mount /data and transfer latest rom and gapps (if you use them; link on droidbasement) via ADB.
3. flash rom and [gapps]
4. Boot in.
Pershoot,
Once again thanks for all the help.
I have not yet followed your steps above but now I'm sure it IS a CM12.1 problem. I have just flashed your cm11 rom and everything works as it should. Also as sbdags's zombi-rom is based on cm12.1 I guess that's why it also had the problem.

Hopefully you can take a look into this if you have the time.

Thanks again
 

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
Pershoot,
Once again thanks for all the help.
I have not yet followed your steps above but now I'm sure it IS a CM12.1 problem. I have just flashed your cm11 rom and everything works as it should. Also as sbdags's zombi-rom is based on cm12.1 I guess that's why it also had the problem.

Hopefully you can take a look into this if you have the time.

Thanks again
pls go back up to CM12.1 (latest is 7/26 (filename is 7/27)) but use CM recovery to do it. Then observe...

i'll see if i can reproduce your issue over here this week.
 
Last edited:

mitchum67

Senior Member
Jun 1, 2009
98
31
0
with 07/26 the battery indicator shows correctly in the statusbar. pershoot, thanks a lot for your awsome work !!!!!

send from my TF701T, powered by pershoot!!
 

sbdags

Inactive Recognized Contributor
Jun 24, 2007
12,753
15,556
0
Kenilworth, Coventry
Pershoot,
Once again thanks for all the help.
I have not yet followed your steps above but now I'm sure it IS a CM12.1 problem. I have just flashed your cm11 rom and everything works as it should. Also as sbdags's zombi-rom is based on cm12.1 I guess that's why it also had the problem.

Hopefully you can take a look into this if you have the time.

Thanks again
Also zombi is not cm12.1 based it is omni based.

It is more likely to do with the way twrp mounts and formats partitions. It seems less forgiving of data errors.
 

beady_uk

Senior Member
Jul 22, 2010
235
54
0
pls go back up to CM12.1 (latest is 7/26 (filename is 7/27)) but use CM recovery to do it. Then observe...

i'll see if i can reproduce your issue over here this week.
Also zombi is not cm12.1 based it is omni based.

It is more likely to do with the way twrp mounts and formats partitions. It seems less forgiving of data errors.
Pershoot, Sbdags

I have done as pershoot described and have fastboot flashed CM recovery, Full wipe and flashed latest CM12.1 (28th). I still have this issue but have figured out that it only effects NTFS storage. I have my Micro SD partitioned as NTFS so my laptop can transfer files onto it and also my 1tb USB hdd and my 64gb USB stick are NTFS that i use, which all crash at the 2gb point whether copying to or from, or playing videos from. Any file less than 2gb is fine
I have now tried a micro SD card in fat32 which works fine.
This was never a problem in CM11 so hopefully this helps you locate this issue and is a simple fix for you.

Thanks again for all your help
 
Last edited: