yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] thingonaspring:
I've recently been reading up on and testing different values for the following registry key :-

HKLM\System\StorageManager\FATFS\CacheSize

By default in Tuma 1.3 this key is set to 4096, which agrees nicely with the maximum value in the following MS document on FATFS registry keys.

http://msdn.microsoft.com/library/d...tml/wce50confatfilesystemregistrysettings.asp

Having read this I decided to try some higher power-of-2 values to see if 4096 really was a hard limit on cachesize. To my surprise, setting a value of 32768 does work, and shows an increase in memory use after boot. (~37mb with 32768 cachesize, versus ~23mb with 4096 cachesize)

NOTE The next highest power-of-2 (65536) caused corruption of the today screen, so that should obviously be avoided.

Does anyone know if the extra space is likely to be actually used as cache? Or does this just allocate memory that is never used?

My Qtek 9090 does seem to respond faster, once the cache is loaded with recent apps, but I also know it's easy to delude youself that such "tweaks" are having a real effect.

Could someone else confirm this for me?

Obvious disclaimer - don't edit your registry if you're worried about turning your phone into a useless hunk of plastic.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Tuatara:
Yes, this is delibrately done to not 'push the device into undocumented territory.

The extra space is allocated, and it would be used - albeit rather slowly:

4096 = 2Mb, 8192 = 4Mb, 16384 = 8Mb, 32768 = 16Mb cache size. Applications (and data) need to fill this space to make it useful. Also, it's proven by your memory change from 23Mb to 37Mb = 14Mb ... exactly the difference between 16Mb and 2Mb (by coincidence? ;-))

Using more than 2Mb of cache space will in the short term possibly make your device run faster, however when the compaction thread needs to run (and stuff needs to get written back to flash), it will attempt to buffer as much as possible, and then take it's time while it 'locks up your device' and flushes 16Mb (possible) of data ... instead of 2Mb. Multiple smaller blocks will have less impact on the usability of the device - so there's been a careful balance done between performance and continuous usability. Sure you could make it faster in the short term ... but long term you'll hit those 10 second pauses.

In testing I've found 2Mb to be a good upper limit. Try 4Mb if you've got a lot of data intensive applications, but otherwise I can't see too much benefit in going larger. Also - the chance of losing something is greater ... a reset while things haven't been written to flash, and *poof* it's gone.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] thingonaspring:
Excellent info Tuatara, that explains a lot about why my device was running in stops-and-starts ;-)
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] orcish:
This is very interesting. I own a hx4700 device and rescently upgraded it to wm 5.0 (the nightmare begun). The information I found here is totaly oposite of what some wise heads are suggesting on other forums.. and this works. Lowering the cache (setting DataCacheSize to 0x100) made my device more responsitive when compaction runs (20 minutes every few hours!)

I have few questions about the compaction thread - Is the compaction process always taking constant time (depending on the size of the files on the device)?

Compaction always takes long time to finish - about 20-25 minutes on a 35megs free flash. Is this normal ? Block size of the flash reported by some hp utility is 128kb, in registry (and bootloader after lnb) shows 256kb. Could someone explain the exact logic of the compaction thread ?

I have another question - the msdn mentions that CacheSize is deprecated and should the folowing keys be used: FatCacheSize and DataCacheSize. Why are you still using the old reg key ?

If the compaction problem is solved in the hx4700 (and probably on the dell x50v) the device will be worth it's money.

Thank you for the great forums and the great community.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] orcish:
Whao! A reply beyond my expectations! Thank you!

Here is my questions:

Is this about the compaction thread or the disk defragmentation process? If it's about the compaction thread - probaly seting the Prio256 and PrioCrit256 to real time would make it almost interruptable (and make the device freeze for some time). If running time with critical priority takes effectivly less than my usual 20 minutes, it means that something is messing my compaction, right ?

I'm not fiddling with the priorities, and have no running applications (except acbPowerMeter or/and SuperTask to monitor the activity). When compaction hits I just close everything and watch it complete. When acbPowerMeter reports about 380mA usage - it's the Compaction. filesys takes about 90% cpu (10% taken by the SuperTask when it refreshes the screen with new readings). Activesync is stopped, disabled and etc.

Is it possible to monitor disk .. err.. flash activity ? All read/write calls? Probably a filesystem filter? (about filesystem filters I have a question below)

Is it possible to take some information about the compaction process itself, % done, blocks freed and etc. I suspect that there is something wrong - probably trying to compact a bad block or something like this. I have seen people complaining about this in the platformbuilder newsgroup.

Something that may be conneted to this issue is the filesystem filters I found attached to my storage devices. I have fsdspy and fsreplxflt. What are they? Some information points that fsreplxflt is for replicating ram to rom and fsdspy as an example!? Are they needed actualy?

Thank you for your reply, I have more questions and when I clear them in my head, I'll be more than happy to ask them to you.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] HiltonT:
Hi Tuatara,

Great explanation - clears up a few questions I had.

One question, however, remains. What's the easiest way to tell your device is compacting and hasn't just hung? I've had a few times when my device seemed to just hang solid - nothing worked, no buttons, no touchscreen, nothing. So I soft reset the device to bring it back up with no data loss. I assume this was a crash not a compaction.

Is there any way in TuMa 1.4 that you could make a "Compacting" icon or similar so that we can tell when compaction is being undertaken?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Tuatara:
You're welcome ... it's always better when things are 'demystified'.

Compaction runs at a lower priority than other tasks, so if you have NO response from it for 10 - 20 seconds ... especially wait longer after having been IDLE for a while ... then it has definately crashed. Just give it enough time to see if it will recover though ... large block erases can take time - especially when the filesystem is in a 'transitional' state.

We could have a 'task manager' which monitors the process list and then puts up a 'red light' when the CPU is being used for this task ... it may be a worthwhile project for someone to undertake. Unfortunately I don't know of anything like this at present ...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Tuatara:
I was just re-reading things from Mike (http://blogs.msdn.com/windowsmobile/archive/2006/03/16/552996.aspx) and realized that no matter what you do to those Priority registry keys, they will have no effect. *sigh*

I'm changing those keys in the boot.hv (XIP section) in TuMa ROMs, so I do have the ability to change those priorities directly, but this is not an end-user Registry thing.

If I get the time, I may look into the 4700 ROMs and see if there is anything which can be corrected/adjusted for these - either that, or someone who can modify these ROMs is welcome to PM me, and I can send them the full registry dump (boot.rgu) and they can attempt to merge in the settings themselves and see how that goes.

Again ... apologies, but it appears MSoft has decided that you're not permitted to mess with these settings. The TrueFFS registry settings may follow the same rule, but then again - I'm not entirely certain of this.
[Asus  Eee Pad Transformer Prime] hulkhaugen:
I'm trying to install [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][08/01/14].I have Unlocked bootloader with the Asus tool and i've installed rom manager and have CWM 5.8.3.4 (not touch) installed. I was looking for a specific CWM in OP's post, but didn't find any. Now, when i reboot into recovery, i see a text saying the device is unlocked, then it goes to the screen where the Android has the hood open and a red warning triangle above it. It stays like this for a couple of minutes, then i just reboots into stock JB. What am i doing wrong? BTW, don't have a dock, US pad...

EDIT: I fixed it with a fastboot installation
[Asus  Eee Pad Transformer Prime] Xerxes-3.0:
You fixed it? Intradesting, I had the same problem but then read here that CWM is no good, at least on the Prime, and fastboot-flashed TWRP instead.

This does work, however I cannot restore the Stock-ROM-Backup. Not sure whether this is TWRP's fault, though.
[Asus  Eee Pad Transformer Prime] hulkhaugen:
Quote from the CM11 Unofficial thread:

I think this is a modified version, but it works like a charm ;)
[G2 Q&A, Help & Troubleshooting] 4m3r:
I have LG G2 D802

Android 4.2.2

Baseband Version: M8974A-AAAANAZM-1.0.190036

Kernel: 3.4.0

Build number: JDQ39B

Software version: D80210a-TMO-XX

ROOTED and i want to remove root

I just want to know can i flash EUR rom or i must again download TMO rom ?

THX
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
Hey. I've got this problem with Bluetooth, where it just stops responding after a while. Suppose I just enabled Bluetooth (first time for this boot). Bluetooth will work for a while, but after some time (an hour or so?), it just stops working. It stops detecting new devices, devices already connected stop working, and disabling Bluetooth and trying to re-enable it gets stuck on "Turning on Bluetooth..." It's fixed after a reboot, but stops working again some time after enabling. This is pretty bad, since I use my Wiimote for gaming.

Can anybody reproduce this, and can anybody help? I don't think it matters, but the game I'm playing is Beach Buggy Blitz, and the Wiimote app I'm using is Wiimote Controller by C.C.P. Cre@ions. Thanks.
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
Bump; nobody? Oh, come on!
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Hey,

Sorry for the late reply. I must have overlooked it :silly:

Now: my Bluetooth problem is even worse. It does connect with devices(and it stays till I turn it oof), but it refuses to transport data! I noticed when I wanted to use my dockstation. My friend was there, and I wanted to play some music with loud boxes. It started connecting, and said: ''connected''. But it refused to play music. My Phone would vibrate and say: 'can't play audio''.

I tried to connect with my firends Samsung Galxy SIII. Again, it would connect, but it didn't transfer data. I tried with my mom her phone, but no. No data transfer.

So yeah. I'm stuck here. In stock, bluetooth works fine, but on CM10 not. Count in the baseband and battery bug, and I'm losing my interest in this ROM! Let's hope CM11 will fix all of this. I have no solution whatsoever, and allthough my problem differs a bit, I also have a bluetooth problem!

Have a nice day.
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
Guess nobody tried Bluetooth when they said only video recording is bad, right? :P

I would switch to stock, as soon as I can make GravityBox to work on it. Till then... CM10 it is.
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
Yeah, I can live without Bluetooth, but it can be very annoying. And yes, I would describe Bluetooth failure as a large bug...

Have a nice day.
[Sony Xperia Miro, Tipo (Dual), J, E] CtrlAltDelIrl:
Why don't you just logcat it to find what the problem is?
[Sony Xperia Miro, Tipo (Dual), J, E] CtrlAltDelIrl:
If you built a rom how long would you test BT and on how many devices before you claimed it worked?

Get with the program for gods sake!
[Sony Xperia Miro, Tipo (Dual), J, E] NSDCars5:
...Good point.

What do you mean by this?
[Sony Xperia Miro, Tipo (Dual), J, E] Deleted member 5439257:
I guess he means the logcat.

Have a nice day!
[Galaxy S 4 Q&A, Help & Troubleshooting] iDpC1:
Can somebody port ColorOS rom for i9505. Its nice rom, but the only support i9500 :(
[Galaxy S 4 Q&A, Help & Troubleshooting] MistahBungle:
No. You've got the wrong site. You need xda-we-do-requests-for-every-n00b-who-asks-developers.com

Hint: Learn to code
[Galaxy S 4 Q&A, Help & Troubleshooting] iDpC1:
Hahaa
[Galaxy S 4 Q&A, Help & Troubleshooting] DSA:
My post of the month....cheers fella :highfive:
[Galaxy S 4 Q&A, Help & Troubleshooting] Diazz72:
Next time use search: http://xdaforums.com/showthread.php?t=2748022

Plz. do not troll.
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
I shattered the screen on my Nexus 5 so I ordered a replacement from Google and before switching to the new one, I made a nandroid backup using TWRP.

I put my SIM in the new Nexus, transferred my nandroid backup, and restored it to my new phone.

Now, I cannot connect to AT&T due to my IMEI showing as 0.

I think I have narrowed down the problem to restoring the EFS partition on the new phone when I wasn't supposed to? So far, I have tried restoring the phone to stock (from this guide). I even tried manually changing the IMEI to the correct number (but it doesn't stick, just reverts to 0).

Is there something else that needs to be wiped in the stock restore process that's not covered in that guide? What am I missing? Any help is greatly appreciated.
[Nexus 5 Q&A, Help & Troubleshooting] CRIME INC.:
Sounds like you're gonna need another replacement

sent from my HAMMERHEAD neXus
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
You're hosed. You can't transfers the imei to another phone
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
Ouch....

Is there anything I should have done differently? Just not flash the EFS partition? I normally setup from scratch but I loved how I had my other setup and just wanted to retain that configuration.
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
I wasn't intending on transferring the IMEI. I just want to get the phone's IMEI corrected so it works.
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
By restoring the efs partition you did try. It's contained in there. That's where things went wrong and there isn't anything you can do about it
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
Great.... SO there is no way to reset the EFS partition, I'm guessing?
[Nexus 5 Q&A, Help & Troubleshooting] EddyOS:
Just goes to show if you don't know what you're doing you should stay well clear!

You're going to have to buy a new one as there's no way Google are going to RMA it

---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------

Not unless you backed up the new one first, no
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
That's what I thought. I usually back up everything before doing anything. I just got in a rush....
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
Speed kills

---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------

Speed kills
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
Thanks for the help guys. Luckily, I still have my old with the cracked screen. I'm just going to have to take the screen off the new one and put it on my old one..which is what I was trying to avoid.

Beats having to buy another one due to my screw up.
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
LOL...says the guy with a Porsche!
[Nexus 5 Q&A, Help & Troubleshooting] EddyOS:
It's a harsh lesson :(
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
Alright, so I swapped the motherboards of the phones, booted up my new phone, restored from nandroid (avoiding the EFS this time, just in case) and I'm back up - crack free.

Thanks for the info guys, lesson learned.

"What do we do when we fall"?
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
Glad you got something working
[Nexus 5 Q&A, Help & Troubleshooting] WoodburyMan:
Yea. All guides need to make sure to post a warning and a link to the EFS backup thread. http://xdaforums.com/showthread.php?t=2514095

First thing I did was make a backup of mine and store it away in a safe place as well as on the phone. I've flashed two friend's N5's with CM as well, and I did the same with their EFS just in case something happens.

One other route you could try is restoring the phone to factory default, relock the bootloader so the mod trip isn't set, and send it back saying it wont connect to cell network, and take your chances RMAing it. However the display swap may be easier. Either way once you swap your display back, do a EFS backup with that link and save the files it makes in a safe place.
[Nexus 5 Q&A, Help & Troubleshooting] Shanks:
Somewhere in xda there is a guide to create an imei,i don't have the link to the thread, I'll see if i can find it for you or you may Google it
[Nexus 5 Q&A, Help & Troubleshooting] qwen3579:
Yeah, I found a guide CATing the IMEI to /dev/pttycmd1 - that didn't work. Most are hesitant with sharing info on changing IMEIs, which is understandable. It's just frustrating knowing what the problem is and not being able to fix it.
[Galaxy S 4 Q&A, Help & Troubleshooting] luiwii:
If I make a s4 i9505 and I love the roms GE, but for a while it happens that any GE put, that is me going on all the app fouldermount misses the obb folder and can not pass the data in that folder the SD, which is really the problem, the role of the kernel or my phone, and not to think as roma AOSP cm11 not pass me, only in GE, grace
[Galaxy S 4 Q&A, Help & Troubleshooting] luiwii:
I've been testing it and it only works well fouldermount with faux kernel on any rom GE GE, which is no problem if the roms kernels, should begin by telling kt and alucard, what happens is that even I can not respond to his son, sorry for my bad English
[Android Q&A, Help & Troubleshooting] Velltuspro:
Hello. Dear developers, please help how to make it work BLUETOOTH DONLGE via OTG cable?

Device - the tablet Prestigio PMP5780D (Prime DUO) 8.0, android version - 4.1.1 Processor - RockChip 3066, kernel version 3.0.8 +

On the computer is defined as Generic Bluetooth Adapter. I beg you to respond to a request for help, because I do not know how to solve this problem.I apologize in advance for any errors, I do not know the English language and use an interpreter who translates certainly very bad and maybe not entirely clear. :(
[Android Q&A, Help & Troubleshooting] Sexy Devil:
Hello, I looked at the specification of you device. It says bluetooth is not supported.

I guess you cannot use bluetooth dongle through OTG Cable.
[General Questions and Answers] pmcma:
Hi I was following the steps in this tutorial http://xdaforums.com/showthread.php?t=1335548 to unlock my GT-S5830. I've managed to get the bml5.img and searched for the HEX string mentioned in the article. I got the code 47462791 from the search but it doesn't seem to work unlocking the phone from the original carrier. Can someone else search the file to verify this code is correct? ATM I have rooted my GT-S5830 installed CWM and a Custom ROM do I need to enter the unlock code on original Samsung firmware? hopefully I've attached this file ok. Thanks in advance.
[Xperia Z1 Q&A, Help & Troubleshooting] Don_Perrignon:
Simple question.
[Xperia Z1 Q&A, Help & Troubleshooting] jamespmi:
The glass is scratch resistant, not the screen protector. It's just a plastic film...
[Xperia Z1 Q&A, Help & Troubleshooting] Vaith:
It's not just screen resistor. This "plastic film" keeps your phone screen in one piece if your phone fall. Taking of this "plastic film" void your warranty.

Screen should be scratch resistant as Sony said.
[Xperia Z1 Q&A, Help & Troubleshooting] jamespmi:
Good point. But... The warranty is lost anyway if I breack the glass...
[Xperia Z1 Q&A, Help & Troubleshooting] dlads:
It is but if you don't and you need to send it off then you can't if you remove it, so you should really leave it on.
[Xperia Z1 Q&A, Help & Troubleshooting] Don_Perrignon:
The warranty is irrelevant. We know as tested the screen is scratch resistant?
[Xperia Z1 Q&A, Help & Troubleshooting] raptuz:
I got a nice scratch only a day or two after removing the ASF. It's not nearly as scratch resistant as the screen on my galaxy s3 or s4 or my glass-m protector for the Z1.
[Xperia Z1 Q&A, Help & Troubleshooting] jamespmi:
This is nonsense. There are tons of youtube videos proving the contrary.

This french video shows scratch and drop tests. Once the protector is pealed it's totally scratch resistant.

http://youtu.be/PkYlFne52yM?t=20m17s
[Xperia Z1 Q&A, Help & Troubleshooting] Don_Perrignon:
See, lol, I keep getting back and forth answers when searching.
[Xperia Z1 Q&A, Help & Troubleshooting] raptuz:
I thought so to, that's why I didn't bother putting on a new protection when I removed the original one. I also watched the videos, and I still think it will do just fine against the blunt keys and coins.

I got the scratch from normal use, carrying it in my pocket, laying on the desk and in the car. And this is the only screen I've gotten any scratches on for the last two years... The Glass-M for the Z1 is the first protector I've ever put on a phone, because I never felt the need for one until now.
[Xperia Z1 Q&A, Help & Troubleshooting] jamespmi:
Hm, miracles with this phone, like the bending story... sorry for you then...
[Xperia Z1 Q&A, Help & Troubleshooting] Don_Perrignon:
Got off the phone with Sony. They say that it is scratch resistant as well as the back, though not as well
[Xperia Z1 Q&A, Help & Troubleshooting] Minibull:
I thought both panels of glass on the Z1 are DragonTrail glass? Seems like it's tough stuff.

I've seen a couple of scratch tests on youtube, and they both went very well. One used a scalpel as the final tool though, and IIRC that started to scratch it up.

I'd always leave the ASF film on the phone, and if it starts to get scratched up, I'd just pull it off and replace it with a new one. Keeps the glass in perfect condition, plus if the glass did shatter after a drop, you would be able to keep using the phone without risking cutting your fingers up. Makes sense to me...
[Xperia Z1 Q&A, Help & Troubleshooting] Don_Perrignon:
Talked with T-Mobile Tech support and specifically asked them if they know for sure the glass under the screen is scratch resistant. The rep I talked to said specifically he has seen were people have lifted the plastic and tested it and while it is not has good as Gorilla Glass, it is indeed scratch resistant.

Funny enough, I went to the Sony store and the guys there had no idea.
[Xperia Z1 Q&A, Help & Troubleshooting] eclyptos:
It's a tempered glass and as a glass is well scratch resistant but I will not pretend to much.
[G2 General] omegajester:
I'll take this one just in case
[G2 General] prking07:
Nice!, just remember to thanks tangjun269 as the zips are made are his gflex patches just edited.
[G2 General] ManyouRisms:
This is awesome.

Much needed love for the Canadian variants.
[G2 General] omegajester:
Added! :good:
[G2 General] Odiumvex:
What roms can be used? I can't seem to find 803 ones.
[G2 General] Aviras:
I *think* he answered this in the OP:
[G2 General] omegajester:
Download any rom you like from whatever thread you want (D800/801/802 etc) flash it, an then flash one of the kernels provided here immediately afterwards.
[G2 General] Dene_Bluesman:
Flashed the D803 modem for the heck of it on my Bell D803, Lost LTE on stock, CleanRom 2.0, and PA. Just to be sure if speeds retained I did a speed test on each rom. Worse speeds ever. Flashed back to bell modem and all was well. I was bored lol
[G2 General] omegajester:
I can see that lol. I wouldn't mess around with radios too much, it's super easy to cripple your phone if you do. Now kernels, you can mess with them all you want. Bad comes to worse, you'll end up in fastboot, but just flash a working kernel and you're game.