yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] aarmstrong23:
9 nov build with squid kernel work like a charm for me! Great job!!!

Envoyé de mon XT1563 en utilisant Tapatalk
[X Play Original Android Development] polobunny:
I can't get in recovery either, as somewhat expected since flashing the 9th of Nov release.
[X Play Original Android Development] madcat1990:
After the 9th Nov release, I've been seeing errors saying :

E:Unable to stat '/data/data/com.android.browser/app_webview/old_Cache_000/index'

And running fsck_f2fs gives me a 255 error?

Any idea what's going on [MENTION=6485916]squid2[/MENTION]?

EDIT :

I ran a fsck.f2fs on /dev/mmcblk0p42

it found a lot of errors, so I ran it with the -f flag

Rebooted TWRP, still having this issue.

EDIT 2 :

I wiped my /data partition (This also wiped my internal storage :C ) by making it an ext4 partition then back to f2fs

Seems to have solved the issue (In a somewhat forceful manner )

Could this be related to the issue of people not being able to go to TWRP in the Nov 9 Release? F2FS corruption?
[X Play Original Android Development] shanthasorooban:
Anybody hitting issues with nov 9 build?
[X Play Original Android Development] Zobat:
I don't but please read the few messages above your post. Did you read anything before you posted this question?
[X Play Original Android Development] shanthasorooban:
GApps missing some apps

Yes bro. Successfully Flashed Nov 9 Build with r10f Squid Kernel.

But When i flash GApps some apps are missing.

I dont use any Gapps-config changes.

But still some apps are missing. For ex, Now maps, youtube, translate are missing.

I had no problems with tk_gapps. I didn't use cos they are outdated.
[X Play Original Android Development] Zobat:
maybe you installed a small gapss. Check the market for missing apps.

regards
[X Play Original Android Development] Lennyz1988:
Then you installed the 'wrong' gapps. Completely rom unrelated.
[X Play Original Android Development] shanthasorooban:
How to find the correct gapps. And new problem. Theme packs cannot be installed. Help please

---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------

Flashed stock gapps package. Also log shows everything installed. But not found.
[X Play Original Android Development] LuizHenrique91:
First post links a GApps package.
[X Play Original Android Development] shanthasorooban:
I used ARM - 5.1 - Stock.

If that's not correct, please tell which is the suitable one.

One site says to select ARM64. What can i di now?
[X Play Original Android Development] Zobat:
Do not use ARM64
[X Play Original Android Development] ephumuris:
Flashed 9th build with latest squid. Working great.
[X Play Original Android Development] LuizHenrique91:
delete
[X Play Original Android Development] squid2:
November 11 Build

This build patches a security vulnerability in the Pronto WLAN driver, and has gone back to an older version of f2fs. For the last (November 9th) build, I tried out a new f2fs version staged for Linux 4.4 backported to Linux 3.10. While it may or may not be the culprit, I had TWRP break on me after the first time I booted the ROM with the new f2fs driver. After erasing userdata (fastboot erase userdata) and rebooting the ROM, the ROM reformatted f2fs and everything has been working fine since. I have a suspicion that filesystems formatted with an old f2fs version got damaged by the Linux 4.4 f2fs.

Anyway, just to be safe and stay close to stock for the default CM kernel, I went back to the f2fs driver used by Motorola (which isn't too old anyway). I did some testing to confirm that there are no noticeable issues when going from the Linux 4.4 f2fs to the f2fs version featured in this build.
[X Play Original Android Development] madcat1990:
I was wondering why my /data corrupted! Thank you Squid!

Edit :

Still can't get an IP on stock CM kernel. Switching to your 10F
[X Play Original Android Development] shanthasorooban:
Help me in selecting GApps. Please.
[X Play Original Android Development] LuizHenrique91:
I always flash TK GApps with no problem. They're outdated, but you can update everything on Play Store and the Play Store itself and Google Play Service update automagically anyway.
[X Play Original Android Development] shanthasorooban:
Then what to use bro? What i used was correct or not?
[X Play Original Android Development] aarmstrong23:
Use this bro

I use micro but you can choose the one you want

Envoyé de mon XT1563 en utilisant Tapatalk
[X Play Original Android Development] manan001:
Why dialer crash while opening it.. Using version 9 November.
[X Play Original Android Development] dictionary:
Have a theme enabled other than stock?
[X Play Original Android Development] madcat1990:
My Phone keeps stuttering once in a while and I see this in its CPU usage:

irq/215-410000

Any ideas what this means?
[X Play Original Android Development] manan001:
Yes you are right using different theme other then stock
[X Play Original Android Development] dictionary:
Any benefits to the 4.4 f2fs? I am running the Nov 9 with no discernable issues. Would I be losing much by updating?
[X Play Original Android Development] madcat1990:
You could get what I did. Slight corruption in my /data.

I'd trust his judgement and just update to the 4.4 F2FS
[X Play Original Android Development] ephumuris:
Will the corruption occur at random? Or only at install time. I've had 9th build and latest squid kernel installed all day and had no problems so far.
[X Play Original Android Development] dictionary:
I'm already using the 4.4 f2fs with his Nov 9 build. That's why I'm asking if I'll lose anything by updating to the new build with the old f2fs. I haven't had any issues so far with the Nov 9 build. I clean flashed and flashed his 10f kernel right after before a reboot.
[X Play Original Android Development] ephumuris:
I'm still not sure why some people have issues other than the f2fs issue obviously.

Clean install of November 9th rom. Installed open gapps. Squid latest kernel. Moto camera. SuperSU. No issues at all today running great.

Not sure if its the new kernel but my max battery life has been around 5-6 hours screen on. Today has been mostly WiFi as I sometimes do but I'm at 5 hours screen on with 32% battery left! I think I could actually squeeze 7-8 hours screen on. .

No WiFi disconnecting or anything.
[X Play Original Android Development] Zobat:
Delete it so we can rule out things

My 2c
[X Play Original Android Development] squid2:
My "Squid Kernel" uses Linux 4.1 f2fs rather than the 4.4 version. The Linux 4.1 version is well tested and stable. The Linux 4.4 one is newer and more bleeding-edge, but might have bugs. The difference between the Linux 4.4 and 4.1 versions consists of optimizarions, bug fixes, and additional caching and garbage collection modes (that we aren't using). The Motorola version of f2fs is something else yet again (doesn't correspond to an exact kernel version), but the LPD23.118-22 version is fairly recent too.

From the period that I played with the 4.4 f2fs, I suspect but am not certain that it might have corrupted my userdata partition on first boot when I was running a filesystem that was originally formatted by the Motorola f2fs and has been accessed by various other f2fs versions since. CyanogenMod seemed to run fine and TWRP also mounted the partition fine, but TWRP's GUI would fail to complete initialization until I erased the partition. When I reformatted the partition and only accessed it with my r4 TWRP (Linux 4.1 f2fs) and the November 9 stock CM kernel (Linux 4.4 f2fs) it seemed to work perfectly with no observed corruption. I have no firm evidence to indicate that f2fs 4.4 was even to blame for any of the trouble I had with TWRP failing to start. It's just a guess, and I wanted to avoid causing problems for others in case the new f2fs was to blame. You don't really lose much by going to the older f2fs version.

The reason I had started taking new f2fs versions early on from Kernel.org was that the surnia 5.0 stock ROM shipped with a buggy f2fs version that had known data corruption issues. The newer f2fs version I took (from Linux 4.0 at the time) had patched the bug and included other improvements. I later upgraded my "Squid Kernel" to the Linux 4.1 f2fs since that was to be a long term support release. I then stopped upgrading f2fs there since everyone (myself included) was happy with the 4.1 version (and I still am).

When I was redoing the stock CM kernel for lux earlier this week, I just thought to mysefl "why not take the latest f2fs?" so that's what I did. There's no other major reason and no great benefit to it.
[X Play Original Android Development] shanthasorooban:
Thanks bro. And which theme are you using?
[X Play Original Android Development] shanthasorooban:
If you use Deep Darkness Themes, the dialer will crash.

I also faced the same issue. Not with other themes. Now using DeepBlack.
[X Play Original Android Development] MacLaughlin:
Something seems to be wrong with your new upload squid. Incomplete? Corrupt?
[X Play Original Android Development] Davirus849:
I'm amazed about the performance and stability using both, Squid ROM and Kernel.

Your work have given a new life to this phone and with your custom Kernel I got rid of some bugs.

I'm really glad we got you as developer for this phone, I mean it.
[X Play Original Android Development] shanthasorooban:
I faced two screen deaths within 20 minutes with 11-nov build and squid's kernel r10f.

Attched files caught from sys\fs\pstore
[X Play Original Android Development] manan001:
Let it be stable than you can continue

Using latest rom and kernel release it is working fine till now.
[X Play Original Android Development] aarmstrong23:
Im using dark element blue free

Envoyé de mon XT1563 en utilisant Tapatalk
[X Play Original Android Development] pyr0sphere:
I also had two screen deaths last night. I was using the Nov 9 build with CM kernel having come from the Oct 1 build

However my sd card unmounted itself about an hour before this happened, and I actually couldn't even force reboot the phone without taking the sd card out first. I feel like my sd card got corrupted somehow

Edit. Nvm just got another screen death
[X Play Original Android Development] Davirus849:
I experienced the same with an Adata, that indeed, died in less than 2 weeks.

I got a SanDisk Extreme Pro now and its a lot better now, let's see if it manages to live longer since I even got a performance boost with this new card.
[X Play Original Android Development] goodrench:
I got another sod lastnight after updating to Nov 11th and 10f *edit* 10g not 10f. No kernel modifications. Again, I used the phone for a few minutes after I unplugged from the charger and when the screen went to sleep I had to reboot. Will upload pstore files later today. Pstore files uploaded.
[X Play Original Android Development] pyr0sphere:
I've been using a Samsung EVO Class 10 64gb. Doing a full wipe and flashing the 11/11 build. Probably won't fix my microSD card but might as well flash to the latest version anyway

EDIT1:

Welp. Bootloop on unlocked bootloader screen.

Had to restore nandroid. Not sure why I couldn't boot 11/11 build with default kernel after a full wipe

EDIT2:

Full wiped again but flashed Squid Kernel 10g. Still can't get past unlocked bootloader screen. Maybe errors with the build or bad download by me. Or the f2fs issue survives even with a /system wipe
[X Play Original Android Development] prsilveira654:
Guys, help-me! The messege in TWRP ' No OS Installed! Are you sure you wish to reboot? " How to fix this?

I tried other Roms else happens the same. Strange thing is that when it comes to flash INSTALLING very fast rom. Already Gapps is much more time consuming. I returned to the Stock. Some help?
[X Play Original Android Development] madcat1990:
The problem is that, AFAIK, the TWRP 'wipe' does an rm -rf instead of a mkfs.f2fs command.

( I had an issue where /data had ghost folders, that I could not remove or fix, wiping solved it)

Best way to make it really wipe the partition is to either change it to EXT4 and back to F2FS like I did, or open a terminal in TWRP and using the command yourself.

Btw, have you tried the repair feature?

Are you using V3 of TWRP? There was a build made by squid that fixed some roms not installing properly.

Here's a LINK for it, took it out of [MENTION=6485916]squid2[/MENTION]'s Kernel thread
[X Play Original Android Development] pyr0sphere:
Very casual user here so most of what you said flew over my head unfortunately. I have seen the repair feature in TWRP but I didn't try it. Re. the conversion, can you advise how to do this through TWRP or the other method? Whichever is simplest would be preferable

It seems every person who flashed the 11/9 will need to do go through this then to flash later builds?
[X Play Original Android Development] prsilveira654:
well, I do not know. Where can I find the right one for INSTALLING?
[X Play Original Android Development] madcat1990:
OK I can help you with that!

Is your card in F2FS? If so, go to the wipe menu, choose your SD Card, and tap the 'REPAIR OR FORMAT' button.

Try a repair, see what happens. if there's any red, let me know!

If this doesn't work, we'll have to probably wipe, so if you can, backup your data beforehand.

I linked it on the bottom of my post! :)

-->HERE IS THE LINK AGANI<--
[X Play Original Android Development] pyr0sphere:
My SD Card seems to have corrupted last night so everything will need to be done through internal storage. Re. your first question, I do not know the answer unfortunately. I am currently on the 11/9 build which I have a nandroid backup of in internal storage
[X Play Original Android Development] madcat1990:
Well, when you go to that repair / format menu it tells you the current file system.

In TWRP:

Tap WIPE -> ADVANCED WIPE -> [ Choose MicroSD Card ] -> REPAIR OR CHANGE FILE SYSTEM

WITHOUT TOUCHING ANY OTHER BUTTONS

, tell me what the current file system is (Should specify it on the top )
[X Play Original Android Development] pyr0sphere:
It shows vfat
[X Play Original Android Development] madcat1990:
Do you have a backup of its contents? (I.E: is it ok to format it? )
[X Play Original Android Development] pyr0sphere:
I don't have a backup. I cannot access the SD Card at all, either through Android or with the phone connected to my computer through USB. It simply isn't recognized

I just want to clarify, are we trying to fix my corrupted SD Card or fixing the F2FS issue (which I assume is causing me to be unable to flash the 11/11 build)? Both would be fine with me :)

But it's fine to format as I believe the card is corrupted
[X Play Original Android Development] madcat1990:
Follow these instructions at your own risk!

Formatting the SD Card :

1) Go to TWRP

2) Make sure SD card is NOT mounted

3) Tap..

ADVANCED -> TERMINAL COMMAND

4) then browse your way to '/dev/block/'

5) Tap SELECT

6) Type in

EXACTLY AS I SPECIFY

in the terminal :

mkfs.vfat mmcblk1p1

7) Reboot, and good luck!

PSA : This is an aggressive way of formatting, don't use this willy nilly!

----------------------------------------------

Formatting internal storage :

1) Go to TWRP

2) Make sure DATA is NOT mounted

3) Tap..

ADVANCED -> TERMINAL COMMAND

4) then browse your way to '/dev/block/'

5) Tap SELECT

5.5) Realize this may cause Cyano to think your internal storage is encrypted and refuse to boot. Make sure after wiping your sd card that it has a zip file of the rom amongst any other things you might need to completely wipe your rom! :)

6) Type in

EXACTLY AS I SPECIFY

in the terminal :

mkfs.f2fs mmcblk0p42

7) Reboot, and good luck!
[X Play Original Android Development] pyr0sphere:
This is to try to fix the SD Card corruption right? And not related to the 11/11 build not being able to boot for me?
[X Play Original Android Development] madcat1990:
Fix corruption : yes.

You're basically re-creating your file system from scratch.

Fix Boot : I'm not sure if your bad /data is causing it or /sdcard.

I wiped my /data and it worked fine after that.

My SD Card never got corrupted (I don't see why vFat would ever get corrupted as it is a fairly old and well understood FS. )
[X Play Original Android Development] pyr0sphere:
When I boot up TWRP, I assume SD Card is NOT mounted by default?

I entered the command and got:

/dev/block # mkfs.vfat mmcblk1p1

mkfs.vfat: can't open 'mmcblk1p1': No such file or directory

I went into the Mount screen and tapped Micro SD many times but I can't select it to do anything either
[X Play Original Android Development] madcat1990:
'No such file or directory' <-- Means it can't detect the SD card.

Tell me what happens if you type :

ls | grep -v mmcblk0 | grep mmc

instead of the mkfs.vfat command, and tell me if you find any mmcblk# in that list.
[X Play Original Android Development] pyr0sphere:
I assumed I should select the same dev/block directory

I do not see a single mmcblk entry in the list unfortunately

The SD Card is indeed in the phone, and under Storage in Android, I have options to Mount and Wipe Data. I have tried both and neither do anything. When I remove the SD Card, both items are greyed out

EDIT: Oh command got edited. I'll try again

EDIT2: Noting happens when I type that command. It just accepts it without any response
[X Play Original Android Development] madcat1990:
Ok, that confuses me, because usually, the internal is mmcblk0 and the external is mmcblk1 or higher.

If what you say is true, then TWRP cannot find any other device other than its internal storage.

(It doesn't need to be mounted to show up in this list, and if it just 'accepted the command' without any response, then it means there just isn't a memory card your phone is detecting).

Which, again, confusing. Are you able to take the SD card out?
[X Play Original Android Development] pyr0sphere:
Yup I can take it out. I think Android itself recognizes a physical card being present because I have entries under Storage which are related to the SD card, that are greyed out when the card is removed

Maybe the card is just completely damaged. I didn't even drop the phone or anything either. It just disconnected when I did the chop chop gesture for flashlight. But when I removed the SIM tray, the SD card was seated perfectly
[X Play Original Android Development] madcat1990:
Android knows there's an SD card reader (That's why you have that SD Card section). Whether or not Android recognizes you have a card there, that's another story.

This is really odd, the only thing I can think of is for you to turn off your phone, take out the SD Card, try re-inserting it, see if TWRP can detect it.
[X Play Original Android Development] pyr0sphere:
No I don't just mean entries being present. When the card is in, the entries are "clickable" and when the card is out the entries are greyed out. I think this difference shows Android seeing the card being present. I've removed the SD Card about 4 times spanning from last night to this morning

I think I'll need to order a new one from Amazon. This one is relatively new too (bought it September 2015) and is a Samsung EVO Class 10 64gb from Amazon. Assume it's a legit card but never ran any speed tests on it

Thank you for all of your help though. I really do appreciate it a lot!!
[X Play Original Android Development] madcat1990:
is there another card you can try?
[X Play Original Android Development] pyr0sphere:
Unfortunately I only have one SD card. I bought it specifically for use with this phone actually
[X Play Original Android Development] mikber18:
Once a phone will go to 0% battery. It won't boot unless via Recovery

Hi

I'm experiencing a bug that's quite irritating. If I let my phone's battery run down completely the phone will not boot, nor give me any indications of the fact that it is charging.

In such case the only way to revive the phone is to hold down power and vol. down to revive the phone via recovery.

Please could you suggest a solution that would solve this issue and let the phone charge and start-up automatically like it should?
[X Play Original Android Development] madcat1990:
You know that letting your battery drain that low is bad for your battery, right?

Either way, that's not related to Cyano, please go to the Q&A section and start a thread there.
[X Play Original Android Development] pyr0sphere:
So I removed the SD Card and did a full wipe in TWRP (Advanced Wipe > Data, System, Dalvik, Cache) and then tried to flash the 11/11 build again. Still can't get it to boot past unlocked bootloader screen. Do you know if mounting system is required in TWRP? I remember doing that back in ClockworkMod Recovery
[X Play Original Android Development] madcat1990:
Unnecessary.

Do older versions of cyano work for ya?
[X Play Original Android Development] squid2:
The external SD card shouldn't affect bootup. I didn't have any f2fs related issues upgrading from the November 9th build to the November 11th, though experiences may vary there. One thing I suggest doing is "fastboot erase cache" (not just a TWRP wipe). If that still doesn't resolve your issue, try backing up all valuable data from your internal storage using TWRP, then nuke it all by running "fastboot erase userdata". Erasing through fastboot gets rid of the filesystem entirely rather than just deleting the files. I've configured to CyanogenMod to automatically reformat userdata and cache on bootup when the partitions are erased through fastboot.
[X Play Original Android Development] pyr0sphere:
Yup every single version I've tried has worked as expected up until 11/11. 11/9 is the last working one for me

---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------

Fast boot erase cache before flashing 11/11 build correct?
[X Play Original Android Development] squid2:
Before or after flashing doesn't really matter, but my suggested sequence is:

Use TWRP to wipe system, data, dalvik, and cache

Install the ROM zip with TWRP, then reboot into the fastboot mode

Run "fastboot erase cache"

Try to boot up the ROM. If it works, great, you're done.

If it doesn't work, back up anything to want to back up, then run "fastboot erase userdata" to erase all your data

Now try booting CyanogenMod again, and hopefully it will work
[X Play Original Android Development] pyr0sphere:
Fastboot erase cache did not work unfortunately

If I make a TWRP backup as you recommended earlier, can I copy that to my desktop and then back to the phone once the wipe is completed? I'm not sure if there will be any issues with mismatching device IDs or anything like that

Will fastboot erase userdata remove TWRP by any chance?
[X Play Original Android Development] squid2:
Just to be clear, if you flash any CM version prior to the November 11th version, it boots? That would be very strange.

Running fastboot erase userdata won't remove TWRP or the ROM. It will only erase your files on the userdata partition. When a device is acting up, I usually recommend a clean install. What I meant when I mentioned backing up was saving any valuable photos, music, or other such files (as they'll be deleted by doing the userdata erase).
[X Play Original Android Development] pyr0sphere:
I've been restoring the 11/9 build through a nandroid backup every time I've failedto flash 11/11. I haven't actually been flashing any ROMS. I went from the Oct 1 build to the Nov 9 build no problem. Problems started when trying to go from Nov 9 to Nov 11

I'm curious about my TWRP question though. I've saved my TWRP nandroid in internal storage. I assume this is part of the items that get erased through userdata. Do you know if it's possible to copy the entire TWRP folder to a computer and copy it back onto the phone at a later time? I don't mind having to back items up, but I'd like to have a TWRP backup in case things don't go well. I do not have a microSD card unfortunately
[X Play Original Android Development] Zobat:
try run it as root (on linux)

---------- Post added at 11:08 PM ---------- Previous post was at 11:07 PM ----------

Its strange because i am having no problems at all with last build with latest squid kernel