yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] nigelhealy:
[IMG="ext4 vs f2fs benchmarks"]http://cdn-www.xda-developers.com/wp-content/uploads/2014/03/f2fs.png[/IMG]

Now I know /system is read-only, I know as I have to remount readwrite to modify it, so based on the these benchmarks focusing on the reads, ext4 is faster at reads so we are better leaving /systems as ext4?

I also think fs2fs is buffering writes as I get fast writes initially then a stutter then slow, this just copying via MTP over USB
[Nexus 10 Original Android Development] Khaon:
I am using only data and cache with f2fs but I would defo go to all f2fs if I was flashing system weekly
[Nexus 10 Original Android Development] nigelhealy:
Why do people format frequently?
[Nexus 10 Original Android Development] Khaon:
Well some like to run lastest nightly builds. Since ext4 formatter takes age to wipe out the data. They prefer running f2fs which is almost instant. Especially if you formatting every day (well maybe not the best idea for battery life lol).

It is up to you. But I guess whether or not you use ext4 you won't even notice any significant performance gains.
[Nexus 10 Original Android Development] nigelhealy:
Interesting, but you can install ROMs without wiping data anyway so in the example of nightlies you only really formatting small partitons anyway. I've been flashing a few ROMs recently to test stability and my large /data is not affected. e.g. /sdcard/Movies remains in tact.

According the benchmarks, if I use f2fs on the read/write partions like /data /cache I will get some gains and I am best using ext4 for /system.

[IMG="benchmarks"]http://cdn-www.xda-developers.com/wp-content/uploads/2014/03/f2fs.png[/IMG]

I been on Thunderkat now for >1 day and it seem good so far stability and performance, a bit faster than CM and this f2fs is probably helping.

I'm finding my N10 more tempermental than my N7 2013, I suspect the smaller RAM but also it is slower and hoping this f2fs gives a bit of boost. I'm also using greenify to suspend apps, it seem to offer the biggest overall gain for effort.

FYI I made the move from using a laptop to using Android and VNC to the laptop as most of my apps are now Android so I'm more using Android all the time and so this matter more for me, N10 is my main system and I'm keeping most apps which hog cpu and memory on my phone alongside.
[Nexus 10 Original Android Development] Khaon:
Sorry I was meaning the data inside your system partition.

Next release will support ukms and updated zram driver. :)

Envoyé de mon MI 2S en utilisant Tapatalk

Édit : btw take a look at the op I posted few benchmark. Couldn't check your image but if it's xda bench it is kinda old
[Nexus 10 Original Android Development] nigelhealy:
Khaon, thanks for putting in the effort.

Two questions - is it faster to leave /system as ext4 or make it f2fs?

Zram - I thought it a bad idea as Android purges memory blocks better than the cpu can compress pages?

My N10 is the smallest memory Android device I have, 1GB vs N7 2GB and OPO 3GB, so I'm more focused on performance for my N10.
[Nexus 10 Original Android Development] Khaon:
Honestly I have no idea 'only empirical test would answer I guess . but theoretically ext4 is much more mature and should be thus more stable and reliable. However ext4's read speed seems slower. I ll let you pick what you want. I run ext4. Choice was made in regards of reading speed.

About zram I would like to try out lz4 compression algorithm instead of lzo. About efficiency it depends how you tune zram i guess I would like it to start working at around 10-20 %memory left. I have to read more stuff before enabling it so I can't give you a straight answer yet p

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] ericp2:
slow start and crash logs thunderkat .103

Hi,

Please find included:

- catlog showing slow start. it actually took 5s for lock screen to show.

- a last_dmsg log after an actual crash. this was triggered while using chrome on the following site http://phylo.cs.mcgill.ca/ . it seems the amount of javascript interactions is high in this. i first experienced slow touch response, and then suddenly a crash. clearly, it's hard to say if this is related to kernel, or chrome.

Note that previous keyboard slowdown was actually triggered when i tried to reply to one post here using the tablet! it seems that chrome has issues with keeping up with textarea after a while. display lags, which i circumvented by moving away from page and back.

Hope this helps.
[Nexus 10 Original Android Development] Khaon:
Lately I have been noticing slow behavior on chrome and chrome beta however this doesn't occur with any other browser (opera ff etc). Anyway I still stick with it.

Did you try lastest version? I posted this night all f2fs until I debug unified ramdisk

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] b1g.p0ppa:
Just tried it. It booted! Unfortunately battery shows 0% even after a couple of reboots. TWRP reports it's at 79%.
[Nexus 10 Original Android Development] Khaon:
Whats the rom you are running?
[Nexus 10 Original Android Development] b1g.p0ppa:
Omni nightly.20140915. Your thunderkat kernel 103 reports battery correctly.
[Nexus 10 Original Android Development] capitansky:
for update or change rom is required reformat partition? I'm running f2fs data/cache
[Nexus 10 Original Android Development] b1g.p0ppa:
F2FS won't require that you format either partition for either ROM update or ROM change, but you would probably want to format cache for both activities and quite possibly data when switching ROMs just as a best practice.
[Nexus 10 Original Android Development] CazeW:
For me Chrome/Chrome Beta has always been a little bit of a "meh" experience on the N10. It's the best browser but it can sometimes have some strange slowdowns, have long waiting times until the keyboard comes up and occasionally opening the wrong link (this happens easily if you press on a link right after scrolling the page). But besides those Chrome "features", I haven't noticed any unusual slowdown.
[Nexus 10 Original Android Development] Khaon:
New build online, it fixes few bugs.

Change log :

Kernel:

Compiled with 2014.06 linaro 4.7 a15

bfq : corrected max raising time and applied better values for nand drives

VM_READAHEAD increased to 512 kbytes

Add missing -O3 flag plus BS try_to_freeze() to make Linaro behave

f2fs : updated to upstream version

Merge branch 'fixes' into google_mainline

Merge remote-tracking branch 'common/android-3.10' into google_mainline

Merge remote-tracking branch 'common/bcmdhd-3.10' into google_mainline (both using ours strategy)

mm : ukms : initial support ukms is an improvement upon KSM. Some basic data structures and routines are borrowed from ksm.c

Ramdisk :

Corrected dynamic mounting (script inspired by [MENTION=4325945]ktoonsez[/MENTION] 's kt-sgs4

Battery display corrected

Decreased sleep times for uksm
[Nexus 10 Original Android Development] capitansky:
The new build can be used for both allF2F2 and data_cache
[Nexus 10 Original Android Development] b1g.p0ppa:
New build working on latest omni. All F2FS. Battery %age is right too!
[Nexus 10 Original Android Development] Khaon:
This is the fastest and smoothest build I released, I think, your feedbacks are welcome.
[Nexus 10 Original Android Development] b1g.p0ppa:
I agree with your assessment. This build is indeed super fast and smooth! Have not encountered any problems at all. Thank you so much for this!
[Nexus 10 Original Android Development] ericp2:
+1 no wakeup problems, and indeed very fast.
[Nexus 10 Original Android Development] nigelhealy:
Using updated kernel on Thunderkat ROM, f2f data cache.

No issues
[Nexus 10 Original Android Development] Khaon:
New build online !

Hello all, new build online !!

Might be unstable !!

Kernel is updated to linux 3.4.103, from my testing it seems there is no longer slow behavior. Feedback welcome if it is unstable.

Change log :

Linux 3.4.103

Makefile : compiling with graphite

frandom: A fast random number generator as a kernel module for Linux.

Vibration interface goes LIVE

F2FS :

Merge remote-tracking branch 'common/android-3.4' into origin/google_mainline:

I am using cm11 compiled with linaro and with optimized compilation flags, dunno if anyone would be interessted that I share it?
[Nexus 10 Original Android Development] Fidelator:
Always in for anything that can make our N10 faster
[Nexus 10 Original Android Development] Malnilion:
Hell yes, I'd certainly be interested!
[Nexus 10 Original Android Development] ericp2:
Hi Khaon,

Many thanks for .103 update. i have installed it, so far so good. it also shows the fastest ever score on Antutu 5, 28100.

Note however that wake from sleep is still sometimes slow, this may have to do with governor/io scheduler maybe (interactive-bfq)? wake up time may vary from nothing to 4-5s. I had the same with previous release, but strangely only after a few days. Another explaination maybe related to wifi state.... i really don't know.

As others, I am also interrested in optimized CM11. however, since i tend to install nightlies at least once a week, will you provide those as well?
[Nexus 10 Original Android Development] Khaon:
Weird didn"t had any slow waking up, however I am running ext4 on system. I assume you are running f2fs on system? I am running interactive/bfq. Did you run your bench with interactive? If yes try performance.

I can compile a rom on a weekly basis. It doesn't take that long.
[Nexus 10 Original Android Development] b1g.p0ppa:
I've had no slow wake up problems on .103 and I'm running F2FS /system. Fresh full internal storage wipe (don't ask :P ) on latest omni. [MENTION=4577448]Khaon[/MENTION], I wonder if you should open a new thread for your cyanogenmod ROM. I could see this running away t

with comments unrelated to kernel or recovery...

---------- Post added at 08:31 PM ---------- Previous post was at 08:08 PM ----------

EDIT: in thinking about it, though, I would be interested in such a project and it would be easier to have only one thread to follow. I too would like to try your ROM.
[Nexus 10 Original Android Development] Khaon:
Yeah if I add a ROM support I would merge all into one "kitchen" thread. I just hope I won't be asked for specifics ROMs builds :P. There is on mediafire my lastest ROM compiled with this build set up. The rom was built with linaro 4.8.4. There is only the glitching bugs inside the play store( apps' icons are bugged).

Now I am aiming to compile both the rom and kernel with 4.9.x then I ll make it official
[Nexus 10 Original Android Development] b1g.p0ppa:
I did try your ROM and it booted up just fine once I realized I also needed to flash your kernel :-/ . Everything seemed to work just fine but I realized that I personally prefer omni so I went back to it. Nice work though! Thanks for all the efforts.
[Nexus 10 Original Android Development] Khaon:
New build online

Minor update to f2fs's upstream revision

Changelog :
[Nexus 10 Original Android Development] CazeW:
Have had a couple of reboots with the newest kernel. Went back to an older one to see if the reboots were because of the kernel or because I switched to ART. I've attached the last_kmsg but didn't see anything interesting there.
[Nexus 10 Original Android Development] Khaon:
The log refers to this kernel

Linux version 3.4.39-g9aa8b83-dirty (khaon@khaon-pc) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Fri Sep 12 21:04:21 CEST 2014

.

This seems to be the recovery kernel
[Nexus 10 Original Android Development] CazeW:
Hmm, you're right. I flashed the older kernel straight after the reboot and didn't think of that the last_kmsg was going to be overwritten when doing that. :p
[Nexus 10 Original Android Development] brGabriel:
Excellent work on this project. Finally took the plunge and switched over to f2fs. Running great!

What do you think about adding more TCP Congestion algorithms and GPU overclock to the kernel?
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4577448]Khaon[/MENTION], with both 9/23 and 9/26 kernels I'm having games crash. Attaching logcats. Hope they're useful.

EDIT: I'm running f2fs all but this happens also on ext4 /system. Apologies in advance if this isn't kernel related.
[Nexus 10 Original Android Development] Pjodor:
So, if I don't convert system to f2fs I can use a ROM that doesn't have f2fs? Like official pa.

Skickat från min Nexus 10 via Tapatalk
[Nexus 10 Original Android Development] nigelhealy:
When you go into "wipe" you have these:

cache

data

system

If you leave system as ext4 (default) then you can use ANY ROM without modification.

The minimum suggestion:

change cache to f2fs

change data to fs2fs

leave system as-is ext4

erase everything

install your preferred ROM

install Gapps if required

install this kernel

boot!

"all f2fs" is when you also do system as f2fs then you must have a modified ROM which knows system is fs2fs, that is trickier, I not done that. I'm currently using Thunderkat ROM with no modification and this kernel with cache and data as f2fs and left system as ext4 and its been stable and fast
[Nexus 10 Original Android Development] Khaon:
Little update !

Now there is two kernels, slightly the same, the only difference is that one is Google's is running linux 3.4.67 whereas the other one is merged with linux 3.4.104.

The idea is to find out if 3.4.67 could be more stable at the cost of less patches.

Changelog :

Btw now f2fs support fstrim() function !
[Nexus 10 Original Android Development] nigelhealy:
So what are you wanting us to do? Try both?

FYI on khaon_kernel_manta_linux_mainline-10-01-2014.zip
[Nexus 10 Original Android Development] Lokian69:
I would just like to say thank you for developing this Khaon :)
[Nexus 10 Original Android Development] zamula:
Don't know if the new versions are supposed to work with ext4, but with the latest Vanir (ext4) they cause a boot loop.
[Nexus 10 Original Android Development] Khaon:
You mean non boot instead of boot loop right?

If it is a non-boot there was a mistake in the else statement of the mounting cache partition and it is corrected now. Thx u for reporting this
[Nexus 10 Original Android Development] zamula:
Yes, non- boot is correct. Anyway the latest version is working great so far. Thanks!
[Nexus 10 Original Android Development] ericp2:
Hi, i don't know if i missed the update (I downloaded after reading this) but i get into a bootloop

after all cache has been rebuilt in Cyanogenmod, on the .107 version

I am running f2fs on cache and system only.
[Nexus 10 Original Android Development] nigelhealy:
So f2fs on /system. Are you running a f2fs version of CM?
[Nexus 10 Original Android Development] ericp2:
oups.. my bad.. i meant data+cache only, system is ext4 as doing CM updates is too annoying otherwise!
[Nexus 10 Original Android Development] nigelhealy:
OK. Well I'm baffled then I tried a number of ROMs.

You've installed the Koush recovery (f2fs formatting capability). You're wiping dalvik, cache,data,system, then wiping advanced cache data as f2fs, then installing CM then installing Koush kernel (to replace the CM non-f2fs kernel) ? It should then work perfectly fine. Miss a step? If done all those steps then need logs as might be bug.

---------- Post added at 07:18 AM ---------- Previous post was at 07:16 AM ----------

CM updates replaces the kernel. Have to download CM update as recovery zip, then in Koush's Recovery flash CM update zip then Koush kernel zip then boot. Otherwise you'll get a boot loop.
[Nexus 10 Original Android Development] ericp2:
I actually do this with TWRP 7.1+ which supports f2fs. what i do (and this always works)

1. To update CM, i flash the cm.zip and the f2fs kernel, and clear cache/dalvik, then reboot

2. To update kernel alone, i flash the kernel and clear cache/dalvik, then reboot

for 1., indeed, since CM updates come with their own kernel which is not f2fs aware, it is always necessary to flash the kernel again.

for 2. maybe clearing cache/dalvik is not needed, but i prefer doing it.

here, I only did 2. with .107 kernel version , and cm went into a boot loop.
[Samsung Galaxy Nexus] Silverbrain:
Having heard the latest news that Apple was going to be pushing DuckDuckGo instead of Google as their search of choice, I decided to give the site a go, see how good it was. My latest general search inquiries have been about Cyanogenmod on my Verizon Galaxy Nexus (toro) and it didn't take me very long to come to my conclusion upon using the site.....:laugh:

Apparently it completely skips Cyanogenmod, and focuses on Toro...I have a feeling I wouldn't get much help going this route. Google has XDA first up.

Thought this was funny, thought I'd share. :good:
[Samsung Galaxy Nexus] charlie95113:
Its all privacy at the end man I can see why apple would go that route, they gotta keep track somehow
[Samsung Galaxy Nexus] Silverbrain:
And I get that. But I personally am willing to give up some of my info to get more pertinent results that save me time / money. It's the trade off, privacy for efficiency.

Just to test, even if I pop into Google in a virtual machine, no history, not logged in and type "cyanogenmod tor" the next word suggestions are toroplus, toro m5, and toro gapps. 1st link is the download, 5th link down is XDA. So it's duckduck isn't even close on the very first search I throw at it. Granted, it is a technical search for people not inclined to use Apple in the first place. im rambling. hope you get where im going. :)
[Samsung Galaxy Nexus] charlie95113:
Well it depends on what you search my friend but look at the bright side maybe now that apple will support it it will eventually expand
[Samsung Galaxy Nexus] Silverbrain:
Competition is always healthy! Cheers.
[Samsung Galaxy Nexus] faber_93:
you're right :good:
[Samsung Galaxy Nexus] ashclepdia:
that's what I was thinking

I believe duck duck go is the default search on Linux mint firefox also though already for a while now, or at least USEDto be, I haven't tried new releases yet of mint. granted it isn't as popular as Apple products, but with more and.more using it, maybe they will be able to improve their search algorithms. it's hard to compete with Google search. hell even Bing seems to face adversity in becoming VERY widely used(I'm talking to the point that people use the name as a VERB... i.e "just Google it" lol) and Microsoft throws Bing in your face everywhere you turn, with a rewards program where you get points for free gift cards and such JUST for USING bing search for ANYTHING :D

so we can see that it's tough to build a good algorithm for searches when you aren't being used nearly as much as all the competition that have been around for a while already(namely Google, yahoo, Bing, come to mind along with others)

would be nice to see a privacy focused search company able to become easier to use and a viable alternative....aaannnd I'm ramblings again lol
[Samsung Galaxy Nexus] latenightchameleon:
Whatever. Either way Google's monopolized the search engine industry for a while
[Samsung Galaxy Nexus] Silverbrain:
Good point about Bing, never heard anyone say 'i yahoo'd it' or 'i askjeeved it'

Since afaik duckduckgo just pulls anonymous search results from various different search engines, google included, it's going to be up to the bing and yahoo that still do crawling to improve their results in order for duckduckgo to improve.

Cheers.
[Samsung Galaxy Nexus] Shadow Death:
Anyone else think that the only reason why Apple is pushing DuckDuckGo is because Google is a direct competitor in the Mobile market?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] vinsen:
This tweak is a neat little one that I first discovered (and posted about) a while ago now :)

HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\OperatorNames

use the 'New' function to create a new value of type 'String'.

and

The name of the value needs to correspond to the Operator's Number (which in Orange UK's case is 23433).

Example : Indonesia Operator's "Indosat Satelindo" code is 51001

To find the Operator Number for your Operator, click here to view a list at http://kbs.cs.tu-berlin.de/~jutta/gsm/gsm-list.html

Once you've entered the name, and your alternate text, you will need to reboot to see the change.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] xan:
yea, nice trick, I discovered that just yesterday, browsing my registry :D
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] baeshin81:
Not working for Cingular Wireless
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] GerardNL:
Nice. Works great for me.

Finally something else then the usual "21201" which I normally see on my display.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] xan:
It just can't work. U must have another operator code.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
it DOES work with Cingular! i just did it! you just need the correct code for it!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] baeshin81:
oh yea...there are 4 codes for cingular.

\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames

310380 AT&T Wireless

310150 Cingular(Bell South)

310170 Cingular(Pacific Bell)

310410 Cingular Wireless

310380 T-Mobile
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] sarvesvara.dasa:
Cool... this works ;)
[G2 Q&A, Help & Troubleshooting] makgun:
I saw a site on google that is http://item.taobao.com/item.htm?spm=a230r.1.14.8.39FeWl&id=38422919812&ns=1#detail

I wondered that if this real or not ? And if it is ok, HOW DO I BUY it via the paypal ? because there is no option for our country (TURKEY).

Google Result: ¥ 800,00 = 7,8088 U.S. dollars.

Thanks from now...
[Moto X Q&A] T&C:
Have had LTE in our area for years just noticed the other day both Moto X phone connecting on 4G?

Only setting I find is Auto and or 2 G

Under settings, Data, other, mobile network, preferred network type.

I'm I missing some other setting or trick ?
[Moto X Q&A] Darth:
Pretty sure 4g is LTE. Some devices just say 4g.

Correcte if on wrong anyone. ?
[Moto X Q&A] aptalca:
Tmobile rom says 4g for hspa and 4g lte for lte. Usually when I'm in a call, it switches to 4g (hspa) and after the call it switches to lte

---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------

Could be a temporary network problem with tmobile in your area
[Moto X Q&A] samwathegreat:
I can second this. My GSM Moto Xs say "4G" for both LTE and HSPA+

Interestingly, the Moto "G" shows "3G" while on HSPA+

One really useful app for checking which network type you are on is called "LTE Discovery" - free from the market. It will let you know if you are on LTE, or HSPA+ (or even EDGE).

You can also go to Settings > About Phone > Status and the network type will be listed under "Mobile Network Type".

Good Luck
[Moto X Q&A] SymbioticGenius:
I posted a decent response in your other thread.

http://xdaforums.com/showthread.php?t=2778254

I opened this thread and almost my mind cause I knew I responded last night. Can I mod merge these threads please.

Thanks
[One (M7) Q&A, Help & Troubleshooting] egybecks:
Hello

I Have M7 AT&T Unlocked using it in Egypt, So I can't update because there's no AT&T coverage here, Still 4.1

Can I update to Another virsion than the AT&T but still stock ?

"When I request *#*#4636#*#* it says CID = 17169
[One (M7) Q&A, Help & Troubleshooting] clsA:
http://xdaforums.com/showthread.php?t=2659374
[One (M7) Q&A, Help & Troubleshooting] egybecks:
Thanks

Would you please tell me the procedures
[One (M7) Q&A, Help & Troubleshooting] clsA:
How to install an OTA update is posted all over the forums

you need stock recovery and a unaltered system

your still on 4.1.2 have you s-off yet ? you need to do that first.

after your s-off flash the AT&T RUU I posted in the link I already gave you.

then flash the 4.4.2 update followed by the sense 6 update.