yashsingh1/xdaforums huggingface dataset:
[Nexus 5 General] ElwOOd_CbGp:
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
[Windows 10 Mobile] Opus Dei:
Guys can I install xbmc app on lumia 640...10581?

Thanks
[Windows 10 Mobile] myrcello:
Nops, build 10581 lacks project astoria
[XDA Assist] XDA Visitor:
cmw for vivo y28 plese thatnku in advance
[XDA Assist] OfficerJimLahey:
Hello, and welcome to XDA! :cowboy:

There isn't much about your device, but can ask this question in the following thread:

> Android Development and Hacking > Android Q&A, Help & Troubleshooting > Please Help Me for Root Vivo y28 bbk-y28 4.2.2 jb5 bbk

Please note, you will need to have registered for an XDA account to be able to post there.

And if you know how to root this device, feel free to share that info with the original poster. ;)

Hope this helps, and good luck! :)
[T-Mobile Samsung Galaxy Note5] Raul69.atl:
Is this fine or too much??? I think is too much. Idle for 1 hour and 48 minutes it drop 6 % battery just on idle.
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
thats not normal
[T-Mobile Samsung Galaxy Note5] malnash52@gmail.com:
Wipe cache partition
[T-Mobile Samsung Galaxy Note5] Raul69.atl:
I did a factory reset and got my sim card changed and I got better results... I'll post a picture when I get 1% left
[T-Mobile Samsung Galaxy Note5] Raul69.atl:
There it is. Better results.
[Nexus 6P General] davwman:
Someone ease my mind as I just dropped 650 for the 128gb version directly from huawei. This nexus is what I've been waiting for spec wise.
[Nexus 6P General] MrDSL:
I bought my girl one and shes been using it for a week..we both like it so much i just bought myself the 64 graphite.
[Nexus 6P General] SocksNUrToaster:
I've had mine for a few days and its flawless, fast, and the screen is great

You made no mistake. You made the best decision of your entire life.
[Nexus 6P General] Banggugyangu:
In order to "ease your mind", we would need to know what your reservations are.
[Nexus 6P General] jcsww:
I bought the 64GB silver from Google and don't have any regrets so far. Yes, the speaker volume is slightly slower on the bottom speaker but it isn't something you would normally notice at louder volumes, at least with my unit.

Coming from a Nexus 6 though... I am not sure I needed the upgrade. That literally is the only thing I can suggest that people should think about. The Nexus 6P's processor is definitely a step up and you notice this more with games and bloated applications, as they all load significantly faster (5+ seconds). If you are a heavy user of the Nexus 6 and find the battery just didn't make it a full day, then you will also appreciate the battery life of the Nexus 6P, as it is significantly better. The Nexus 6 provided just enough battery life for my average day but I can get close to 2 full days out of the 6P. I haven't used the camera enough to really notice much of a difference as of yet.
[Nexus 6P General] tacosrdelicioso:
You would feel a lot better if you ordered from Google. But you'll get yours eventually
[Nexus 6P General] [hfm]:
Shouldn't you ask this beforehand? Not to mention the litany of threads you can use for this already.
[Nexus 6P General] micmars:
Of course this is a relative question as others have stated, but perhaps these things may provide you with a somewhat neutral metric (I own the 128 GB model as well)...

1. The device is blazing fast, with amazing battery life

2. You get no skimping on hardware, IMHO, screen is top of the line, crisp and beautiful

3. You have an unlocked device

4. You get damn good support from Google

5. It's 200 USDs less than any device with comparable specs (I know that the Exynos 7420 is faster, but it has closed sources, so good luck running anything but TouchWiz anytime soon)

6. 128 GB is truly ample storage...you'll never find yourself needing or wanting extra storage

7. All similar devices are gimped in other respects, and cost about 100-150 USDs less

8. The software/hardware integration must be mentioned, because it is a feature of solely this phone

In sum, you'll be hard pressed to find a better value for your money.

I wish you luck in your search, but please remember, the technology merry-go-round is one of insanity...all technology loses value the second you take possession of it...and if you keep waiting for the next best, you'll never actually own a phone.

Yeah, I'd have liked a Snapdragon 820, but I don't really care. I have a device that makes Shamu feel like a bad memory.

Sent from my 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P General] UniversalGC:
The only mistake you made was ordering from Huawei instead of Google.
[Nexus 6P General] Darth:
There's a few threads already open that talk about quality, opinions, reviews... Etc... Etc.

Please bring the discussion to one of those.

Thanks,

Darth

Forum Moderator
[YU Yureka Android Development] #akadroid:
After a long wait here is the first cyanogen mod 13 Today we bring you the latest version of android which is marshmallow on Yu yureka. We bring you this release in the form of CyanogenMod 13 which is a custom rom based on latest AOSP. Being a initial release there are plenty of bugs accompanied along with it and should be solved eventually.

Release notes :

1:-Initial CM 13 release based on latest google release tag r26

2:-Some basic regular CyanogenMod features. ( Includes theme engine )

What works ?

1 Wifi

2 Bluetooth

3 Internal storage ( SD seems to be broken )

4 All functionality of RIL ( except data connection which seems to be broken )

5 Camera ( Picture works. Video recording doesn’t )

6 All other basic functionalities ( Basic apps seem to be working )

7 Titanium backup works fine

8 You say more !

A huge thanks to

1- cyanogen mod team

2-google

3- please let me know if i have missed somone who deserve thanks

Flashing procedure :

1 Copy the zip to ur sd card. ( Download link available below in downloads section )

2 Wipe data/cache

3 Wipe dalvik

4 Install zip\ flash gapps (not necessary installing apks are recommend)

5 Reboot and have fun

Downloads :

MOD EDIT: links removed

Don't forget to hit thanks button below this post

Enjoy

HIT THANKS

SCREENSHOTS COMING. SOON

HIT THANKS
[YU Yureka Android Development] #akadroid:
RESERVED
[YU Yureka Android Development] CCD:
This ROM is originally built by [MENTION=5480061]Santhosh M[/MENTION] and you have just copy pasted it and want people to hit thanks button

Please Close This Thread
[YU Yureka Android Development] srjlulla:
Did u take permission from Santosh before posting it here?

Sent from Yu in love with

www.trendingus.com
[YU Yureka Android Development] Whiskey103:
Thread closed, looking into things.
[ONE Android Development] DerRomtester:
Have you already tried marshmallow with f2fs? I dont get it working. Cache on f2fs is bootlooping and data on f2fs shows that the phone is encrypted. And it wants a pw. to decrypt it.
[ONE Android Development] Phoenix Wright:
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
[ONE Android Development] DerRomtester:
The fstab should be ok. I use the same kernel in 5.1.1. I will inform you if i get it working. It is time to debug.
[ONE Android Development] therahmaniac:
Hey am still facing the same error upon attempting to mount cifs. I believe it's not due to your mod but some dumb thing I might be missing. Can you post using what tools you mount cifs using the command you specified on the sultan thread?

UPDATE I tried using adb shell(which i guess you would've) and still get the same "No such device" error. dmesg doesn't show anything useful (atleast to my knowledge). But 'cat /proc/filesystems' does NOT show cifs(it does show f2fs). Is it normal?
[ONE Android Development] j1i2a3n4g5:
Links?
[ONE Android Development] therahmaniac:
Check the downloads tab / section... Not sure if it works on tapatalk.
[ONE Android Development] DerRomtester:
I tried sultans mm version with f2fs. And this log looks quite interesting. I am running f2fs on cache and data but it is looking for ext4.

EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/system,target=/system,type=ext4)=0
EXT4-fs (mmcblk0p28): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/userdata,target=/data,type=ext4)=-1
fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/platform/msm_sdcc.1/by-name/userdata for mount /data type ext4 )
EXT4-fs (mmcblk0p16): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=-1
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/msm_sdcc.1/by-name/cache at /cache options: barrier=1,data=ordered,noauto_da_alloc,errors=panic error: Invalid argument
EXT4-fs (mmcblk0p15): recovery complete
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/persist,/persist,ext4)=0: Success
fs_mgr: check_fs(): unmount(/persist) succeeded
fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck: e2fsck 1.42.9 (28-Dec-2013)

e2fsck: /dev/block/platform/msm_sdcc.1/by-name/persist: clean, 29/320 files, 1088/1280 blocks

EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic

Edit i know the problem already :)

I guess it is a ramdisk problem

ramdisk/sbin/mkfs.f2fs

/system/bin/fsck\.f2fs
[ONE Android Development] joefso:
Formatting fo f2fs takes a long time
[ONE Android Development] ph1dft:
I tried it with the latest 12.1 ROM from 01112015 and it works very fast!

When there's trick to do it with the 6.0 ROM I will try.
[ONE Android Development] DerRomtester:
It works with my (Tyr) kernel and Sultans CAF 6.0 Rom.
[ONE Android Development] joefso:
interesting, when I use disc info (without executing the ramdisk command) I see that both /data and /cache are show as f2fs. Curious to know if you still belief it is nessesary to solve the ramdisk problem?

---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------

A question for everyone, why would you chose for f2fs on /data has it not be shown that f2fs is not faster than ext4 on /data and only has benefit on /cache?
[ONE Android Development] DerRomtester:
Already solved the ramdisk problem. :)

I think the benchmarks on android are similar. http://www.phoronix.com/scan.php?page=article&item=linux-40-ssd&num=2

Also Antutu scores are proofing that.
[ONE Android Development] ph1dft:
Tried the rom and it works, but not for daily use. Multirom and f2fs doesn't seem to work so back to 5.1.1. Thanx anyway!
[ONE Android Development] manup85cupra:
sorry where is the download link? :D
[ONE Android Development] sychim:
The links are on Downloads tab. Don't use Tapatalk though. This was discussed a few posts above yours.
[ONE Android Development] Phoenix Wright:
I added a new version. I just added two bug fix commits for F2FS from the dev-test branch (one of them is a fix to potential data corruption), and switched to CM's version of Google GCC (previously I used the one from the Google repos).

Also, I added a version for CM13. Functionality of the kernel is the same (latest CIFS, UTF8, latest F2FS & fstab, OTG-Y). However, I don't use CM13 yet so I'd need testing :) This zip *doesn't have* an updated "fsck.f2fs" binary, as that would require downloading the CM13 source tree (25GB) and I can't do that. I'll do it when I switch to CM13. [MENTION=4804871]DerRomtester[/MENTION] I saw your kernel replaces the whole boot.img, I don't think it's wise to do (the ramdisk contains some binaries - adbd, the sepolicy binary etc. and configuration files which get updated frequently). You can use my script to automate fstab replacement if you want!
[ONE Android Development] therahmaniac:
Hey [MENTION=2968096]PhoenixWright[/MENTION] I used your command

busybox mount -t cifs -o username=xxxx,password=yyyyy,rw,noatime,iocharset=utf8,noperm,nounix,noserverino,sec=ntlmssp,dir_mode=0775,file_mode=0775,uid=1023,gid=1023,context=u:object_r:fuse:s0 //192.168.x.x/yourshare /data/media/0/CIFS

after flashing your latest zip. While it mounts without any errors, the folders are not visible on any file manager.

But i can cd into the directory from terminal and it displays the files.

Any suggestions to get it viewable on file managers?
[ONE Android Development] DerRomtester:
Yeah i know. But on sutlans kernel it is necessary to edit init.rc because otherwise the device says it is encrypted if you are using f2fs.

ramdisk/init.rc

and i dont know a different way to do that with anykernel ramdisk.

https://github.com/DerRomtester/ramdisk_one_plus_one/commit/8dff26584ea6fc7fa82214d2835264975e6ead5c

I also do update my kernel frequently :)
[ONE Android Development] sas.mar:
A noob question here: does it affect battery life? I experience faster battery drain than usual. Like much faster than the one I had with ext4. Have no wakelocks to fix.
[ONE Android Development] Phoenix Wright:
First possibility: those id/gid (1023) doesn't match media_rw in your install. You have to check it. Go to the emulated SD with the CM file manager, check a random file's properties, go to permissions and note the number next to media_rw. Then adjust it in the command.

Second possibility: While I was looking for the options to use, I saw that they said that SuperSU has such issues. Personally I use the built-in CM "su", I guess that could be the reason...

Try this. Wipe /system from recovery (necessary to get rid of SuperSU), re-flash the ROM, then the kernel, then the "root restorer" I attached here (and gapps/xposed/whatever). Then try that command again.
[ONE Android Development] therahmaniac:
Works perfect! Thanks a lot man! Just curious is root restorer required when flashing new version of sultans rom?
[ONE Android Development] Phoenix Wright:
I'm glad it works. Yeah, it is. Flashing a new release overwrites what it does.
[ONE Android Development] manup85cupra:
Hello [MENTION=1581416]Phoenix Wright[/MENTION]. have you in mind to update latest Sultan kernel with F2FS? Thank You
[ONE Android Development] Phoenix Wright:
I posted an update:

- Added other bug fix commits for F2FS from the dev-test branch

- Updated Sultan's kernel sources for both CM12.1 and CM13

- CM13 build should actually be functional now (thanks to [MENTION=4804871]DerRomtester[/MENTION] for the init.rc)

- Recovery has been rebuilt from sources, it now uses the Sultan CM12.1 kernel mod and source tree for his ROM (this is because I'm lazy and I didn't want to build 3 kernels each time lol)

By the way, the previous version only missed the prima bug-fix commit from the latest Sultan CM12.1. The other changes were already merged or were in the dtb (which this doesn't replace).:D
[ONE Android Development] ksigit:
Don't you think its time to add multirom support for CM12.1 and CM13 version? ;)
[ONE Android Development] Phoenix Wright:
I posted a new version, it's just an update to the CM13 kernel sources and I merged Sultan's bug fix for the rare touchscreen unresponsiveness after waking in the CM12.1 kernel.
[ONE Android Development] wxGold:
Hey guys, so just to be clear.

I have sultan's CM 13.0 6.0 rom installed right now and some apps I have installed.

1. boot to twrp and flash sultanF2FS1125-CM13.zip

2. without reboot, format /data and /cache to F2FS and then just reboot

I assume all my installed apps will be deleted, right?

do i need to wipe dalvik cache too?

if there will be an update to this f2fs Current Stable Version: 11/25, do i need to flash again and wipe /data and /cache?

if sultan will update his rom, it wont affect these f2fs partitions?

thanks!
[ONE Android Development] steven8590:
If you are going to change filesystem you are going to lose all the things on your phone so you better have a copy of your storage on your pc. First change the filesystem, then copy back all the files etc that you had transferred to the pc. Download Sultan's ROM, follow [MENTION=4804871]DerRomtester[/MENTION] instructions found here http://xdaforums.com/oneplus-one/development/kernel-tyr-caf-3-4-v33-8-11-2015-t3244058, flash this kernel after you flash the rom and you are good to go.
[ONE Android Development] Phoenix Wright:
Bad news: both me and my brother (who was using the F2FS code from October 15th, so just very few - and tiny - commits from the 3.4 branch) had data corruption, without no crashes whatsoever. One of my apps just stopped being detected despite being in /data/app (the logcat reported issues with its lib folder), and he had corruption with the Facebook app (couldn't reinstall it and there were multiple folders for it in /data/app).

At first I thought I would revert to ext4, and then I remembered that Motorola maintain their own F2FS code branch for their Moto G/X/E devices (as far as I could see, they do cherry picks of bug fixes and rarely add new features): https://github.com/MotorolaMobilityLLC/motorola-kernel/tree/lollipop-5.0.2-release-falcon (this is the branch for Moto G, which is the most recent for a device using a 3.4 kernel).

So, in this new release, other than introducing the latest changes from sultan in the CM12.1 kernel (touchscreen driver fixes, new CPU boost logic) and updating the CM13 kernel, I'm switching to the Motorola driver (from the branch I linked).

I'd recommend making a nandroid backup, formatting and restoring. This driver is technically older than upstream, and it might have issues with inlined dentries (the new fstab reflects the mount point configuration of the Moto X 2014 - so no inline_dentry).
[ONE Android Development] Holymartyr:
Well, I'm sad to hear about the data corruption - but that might explain some of the wierdness I've encountered on a few occasions over my past few months with the F2FS system. I've now found this thread, and am running your patch along with your modified TWRP - and already I've run into an issue where a file that was able to be backed up by TWRP yesterday is now throwing an error and halting the backup process. Thinking it might be time to throw in the towel and leave F2FS for good =( I love the performance, but it sure is feeling like F2FS is to blame for the issues.
[ONE Android Development] Phoenix Wright:
Yeah, probably it's not wise to use upstream code for the filesystem.

I doubt Motorola's F2FS branch has instabilities though, as they use it for the /data partition in the Moto X/G/E phones. I think they primarily focus on stability.
[ONE Android Development] Holymartyr:
Oh, if I'm understanding you right - I did a full wipe of my phone and a fresh re-install with your code yesterday. And verified your TWRP version would work backing up, and it did. Now today I tried again, and a file that I can see in yesterdays file succeded in backing up, and today it is throwing an error.

I:addFile '/data/data/com.android.externalstorage/lib' including root: 1
setting selinux context: u:object_r:app_data_file:s0
E:Error adding file '/data/data/com.android.externalstorage/lib' to '/data/media/0/TWRP/BACKUPS/cf2a19c6/2015-11-29--14-16-38_LMY48Y_release-keys//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/cf2a19c6/2015-11-29--14-16-38_LMY48Y_release-keys/data.info'
E:createTarFork() process ended with ERROR=255
Backup Failed.
[ONE Android Development] Phoenix Wright:
Oh:(

To check if I understood it correctly:

- you formatted /data from within the latest recovery (which has also the Motorola F2FS) - NOT in the Wipe menu as that doesn't create a new filesystem, but with the "Format Data" option, the one which makes you type "yes" and then shows "mkfs.f2fs";

- you didn't restore from a previous backup;

, you reconfigured the phone and then made a TWRP backup;

- today you attempted to backup again and it gave you an error.

Is that correct? If it's so, I'm out of ideas. I guess F2FS is a lost cause, but then why does Motorola use it on the stock kernel? (This is the *exact same* as the F2FS code they use for the /data partition on Moto G, from the 5.1.1 release).:confused:
[ONE Android Development] Holymartyr:
What I specifically did in order is this:

1. Flashed and launched your version of TWRP

2. Went into Wipe -> Advanced Wipe -> And tried wiping the System, Data, and Cache partitions

3. The operation appeared to hang on wiping the Cache partition, so I did a hard restart (phone seemed to be responsive, but was still stuck formating the Cache partition after over 10 minutes with mkfs.f2fs)

4. Tried reverting my Cache partition from F2FS back to EXT4, threw an error

5. Tried repairing Cache, another error

6. Tried reverting Cache back to EXT4 a second time, succeded this time

7. Then reformatted it again back into F2FS SUCCESSFULLY this time

8. Did one more wipe using Advanced Wipe of System, Data and Cache

9. Installed in this order using TWRP: Sultans latest build, your patch, SuperSU, GApps, Xposed, and my modem of preference

10. Everything loaded fine, proceeded to install all my apps, configured almost all of them (with proper restarts)

11. Restarted into TWRP, made a backup, it succeeded, then promtly restored that backup to verify it worked, restarted, plugged my phone in, slept overnight

12. Started off the day doing the final config on my apps and phone, figured I was finally finished, went into TWRP to make another backup, got that error

I've now done a full wipe of my phone again, reverting back to EXT4. I really just want a stable phone right now lol, and I can only remember having my problems with backups and random OS freezes since I moved to F2FS.
[ONE Android Development] Phoenix Wright:
OK, since you wiped /data from the "Wipe" menu, it didn't actually format/create a new filesystem: it basically did a "rm -rf" (delete recursively) for all directories except for /data/media (the internal storage/"emulated SD card"). This is done to preserve the contents of the internal storage, which would we destroyed with a proper /data format.

However, I'm not exactly sure how F2FS works at a low level, but I can guess that if there was corruption in the file table beforehand, it might have led to further issues. I did a format and I still haven't gotten any corruption. I'll try to be careful though, if it happens I'll just ditch F2FS altogether.
[ONE Android Development] Holymartyr:
Ah yes, I see - that makes sense. How else would I be able to keep my 'internal storage', whilst still wiping the data partition without doing something similar to rm -rf. Understood. Well good luck, and I'll be watching this thread hoping for good news in the future =) I already miss my speed with F2FS. Goodness knows if I run into any hangs or issues while using EXT4 I'll be swapping back to F2FS immediately lol.
[ONE Android Development] manup85cupra:
new kernel incoming? :P

edit: (CM 12.1) BTW i didnt notice that you have updated your kernel on 28 but it's a first time that when i move to a new version im not able to pass fastboot screen. it's stuck on oneplus one logo. coming from 11-18 version to 11-28 with a wipe of cache and dalvik. i had to revert to 11-18. im using latest Phils Recovery to avoid any Firmware upgrade issue. please let me know what im wrong.

Thank You