I was going to release this as a ROM, but as you may know Rox is pretty busy these days so he hasn't replied to me yet to my request for permission to fork CM11 (if you're reading this, don't feel offended and take your time!) so I chose to reward the DIYers by releasing the differences from it... and of course devs that share my view of the ideal ROM will hopefully reuse them ~
So yes, this is basically an expansion pack for CM11. After downloading the sources, just before `brunch codina` you extract the zip over them.
What does this do anyway? What's included?
The main feature is that partitions 8 and 9 (sdcard/UMS and preload/HIDDEN) are ignored. You can completely delete them and get a 3 GB /data partition for ART or whatever. Unlike swapping storages (or not swapping them!), this doesn't confuse apps written with only one media partition available.
Camera photos, your songs, OBBs and ASECs from apps that use them, archived apps, ... all go to the card you can always remove from the phone if you want to sell it or need service (keep in mind though it's not 100% sure that nothing on it never ends up on NAND), likely formatted in FAT32 with loads of multiplatform undelete tools available, easy to swallow if you feel the CIA is nearby... (do not try this at home)
There are also some other minor tweaks that I consider a core part of my Android experience, see the text file in the zip for more details or just read this box ↓
Code:
External SD only (on sdcard0) with [STRIKE]ASEC, apps2sd,[/STRIKE] OBB, camera, card hotswap, mass storage all working
/preload disabled
device/samsung/codina/overlay/frameworks/base/core/res/res/xml/storage_list.xml
device/samsung/codina/rootdir/*
device/samsung/u8500-common/common.mk
packages/apps/DeviceSettings/src/com/teamcanjica/settings/device/fragments/AdvancedFragmentActivity.java
packages/apps/DeviceSettings/res/xml/advanced_preferences.xml
BUG: Mass storage mode creates an empty drive, I suspect this can be fixed by playing with the LUN setting in u8500 boardconfig
"battery saving" profile limits clock to 800MHz
device/samsung/codina/rootdir/*
200dpi default resolution
device/samsung/codina/system.prop
Default screensaver after 2 minutes
device/samsung/u8500-common/overlay/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
Browser autocomplete window size increased
packages/apps/Browser/res/values/integers.xml
So if you want to have a look you can grab it there!
Good job!
However i have two suggestions:
1. You should separate "storage" part from other tweaks... It's great that we have somebody with creativity but not everyone wants to apply all that tweaks (and even less will want to separate that tweaks from storage part (considering that potentially interested in your patch are very few in count)
2. Do you have github account? is "githubish" version of your tweaks?
I played a bit with storages in that overlay (storage list) some time ago, but no success on that time... so i'm really interested in those changes.
When i try to compile stock OC kernel - i had to repartition my long time used custom partition scheme. And then i tried to recreate it without UMS partition but it ended with "no sd card" issue (you cannot take pictures for example) after memory swap... So i need something like your patch, but i don't have time to separate it from other tweaks...
judas1977 said:
Good job!
However i have two suggestions:
1. You should separate "storage" part from other tweaks... It's great that we have somebody with creativity but not everyone wants to apply all that tweaks (and even less will want to separate that tweaks from storage part (considering that potentially interested in your patch are very few in count)
2. Do you have github account? is "githubish" version of your tweaks?
I played a bit with storages in that overlay (storage list) some time ago, but no success on that time... so i'm really interested in those changes.
When i try to compile stock OC kernel - i had to repartition my long time used custom partition scheme. And then i tried to recreate it without UMS partition but it ended with "no sd card" issue (you cannot take pictures for example) after memory swap... So i need something like your patch, but i don't have time to separate it from other tweaks...
Click to expand...
Click to collapse
1- Just remove all the unrelated files, I listed the names for a reason (to leave maximum clock at 1 GHz, in device/samsung/codina/rootdir/init.samsungcodina.rc you can see 2 pairs of lines near the end with "scaling_max_freq" to be removed)
storage_list.xml → the highest level part, basically defines the functionality of settings/storage
fstab.samsungcodina → remove internal SD, change voldmanaged= part of external to match mount name in storage_list.xml, if you didn't rename it just change "sdcard1:auto" to "sdcard0:auto"
init.samsungcodina.rc → remove 3-line block related to internal SD, edit name and paths to fit previous configurations
u8500_common → remove swap option from build.prop
AdvancedFragmentActivity.java → remove swap feature from NovaThor Settings
advanced_preferences.java → remove swap option from NovaThor Settings
2- Nope, I don't know how to use git (or any equivalent) and if I was to add the extreme confusion of configuration files assembled from multiple places and quite illogical arrangement of stuff in the sources to a friendlier but completely different system as seen in the repos...
(and github doesn't seem to offer what I would be most interested in - highlighting differences from a previous version)
judas1977 said:
Good job!
However i have two suggestions:
1. You should separate "storage" part from other tweaks... It's great that we have somebody with creativity but not everyone wants to apply all that tweaks (and even less will want to separate that tweaks from storage part (considering that potentially interested in your patch are very few in count)
2. Do you have github account? is "githubish" version of your tweaks?
I played a bit with storages in that overlay (storage list) some time ago, but no success on that time... so i'm really interested in those changes.
When i try to compile stock OC kernel - i had to repartition my long time used custom partition scheme. And then i tried to recreate it without UMS partition but it ended with "no sd card" issue (you cannot take pictures for example) after memory swap... So i need something like your patch, but i don't have time to separate it from other tweaks...
Click to expand...
Click to collapse
Hmm.. Im thinking the author whom you said stopped working on oc stock kernel is you :/
Sent from my GT-I8160 using Tapatalk
Ryccardo said:
1- 2- Nope, I don't know how to use git (or any equivalent) and if I was to add the extreme confusion of configuration files assembled from multiple places and quite illogical arrangement of stuff in the sources to a friendlier but completely different system as seen in the repos...
(and github doesn't seem to offer what I would be most interested in - highlighting differences from a previous version)
Click to expand...
Click to collapse
github is quite logical and well organized . Beside of this, it would be easier to manage your patch when files that you modified will be modified by @Rox or other TC member: You will have to make your patches again or accept that their changes will be overwritten by your patch...
When you click on last (or any) commit you'll see the difference in code it made, btw.
And I try to implement your changes to github code as a commit (should be easy if the sources weren't changed in the meantime).
teddytsen said:
Hmm.. Im thinking the author whom you said stopped working on oc stock kernel is you :/
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Well, I never lied on that subject, never .
UPDATE:
https://github.com/judas77/android_...mmit/139b9d446ea13299b311a82c1973c177d24256e2
OI just compiled new carbon build using your tweaks...
Everything seems to work good (i was really happy), but then...
It seems you cannot install (from google play, from Titanium backup) apps that write additional data on SD(1?):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
judas1977 said:
OI just compiled new carbon build using your tweaks...
Everything seems to work good (i was really happy), but then...
It seems you cannot install (from google play, from Titanium backup) apps that write additional data on SD(1?):
Click to expand...
Click to collapse
Just checked a little better, there is a problem with ASEC creation (vold doesn't create disk images claiming something is mounted read only), cheap workaround is to use Link2SD or `pm` to force everything to install to internal storage
@judas1977 I think I found the problem, I should have confirmation in 5-6 hours
Ok, I'll wait for the info...
judas1977 said:
Ok, I'll wait for the info...
Click to expand...
Click to collapse
keeping all other changes I sent you, in fstab try changing the microSD line (sdi0[...]mmc1) so that it ends with noemulatedsd
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p3 /system ext4 ro,noatime,errors=panic wait
/dev/block/mmcblk0p2 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p4 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p7 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p5 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=/efs/metadata
# Vold managed volumes
/devices/sdi0/mmc_host/mmc1/mmc1 auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
# Recovery only
/dev/block/mmcblk0p15 /boot emmc defaults recoveryonly
# ZRAM
/dev/block/zram0 none swap defaults zramsize=104857600
I haven't managed to try it on last evening's Omni or CM11 as they both got stuck on bootanimation and I can't say if it's this mod or something from 4.4.3 still unpolished...
:good: :good: :good:
That did it. with "noemulatedsd", everything works fine including ASEC (and thus apps2sd)... the job is done :highfive:
So this should do the job?
https://github.com/judas77/android_...mmit/63aa54bd7e0465f8b3881184fd237188657c30ab
judas1977 said:
So this should do the job?
https://github.com/judas77/android_...mmit/63aa54bd7e0465f8b3881184fd237188657c30ab
Click to expand...
Click to collapse
Nope, noemulatedsd goes at the end (after voldmanaged=sdcard0:auto) :fingers-crossed:
Of course, that's because of that long lines
Wysłane z mojego GT-I8160 przy użyciu Tapatalka
judas1977 said:
Of course, that's because of that long lines
Click to expand...
Click to collapse
well, the latest diff you posted is wrong
Yes, i know
Wysłane z mojego GT-I8160 przy użyciu Tapatalka
So if i install that patch, i will not see again the error "could not install on usb storage or sd card" ?
There is patch only for disabling internal sdcard or i have to apply patch with tweaks?
Thanks
nikolas1274 said:
So if i install that patch, i will not see again the error "could not install on usb storage or sd card" ?
There is patch only for disabling internal sdcard or i have to apply patch with tweaks?
Thanks
Click to expand...
Click to collapse
You mean the bug where you swap storages but Google Play still checks the free space from the internal memory?
No problem with this method :good:
Ryccardo said:
You mean the bug where you swap storages but Google Play still checks the free space from the internal memory?
No problem with this method :good:
Click to expand...
Click to collapse
Yes i am talking for this.
Thanks
Hi!
As I see, TeamCanjica has changed the structure of the init scripts recently, so the changes you've made in "init.samsungcodina.rc" have to be applied in "u8500-common/rootdir/init.u8500.rc"
Bela
Related
[DEV] data2"XYZ" general filesystem discussion (Updated Dec 20 - Benchmarking)
I will rewrite this posting soon. As for now please check the scheduler Benchmark:
http://forum.xda-developers.com/showpost.php?p=9959265&postcount=257
================================================================
data2btrfs (this is DEV status so don't ask how to install - there is (little) linux expirience required)
Update about btrfs dec 15: Still testing btrfs and im REALLY amazed. Battery life has no difference to ext4 but performance is FAR better then ext4. I do still get lags in some cases (like fast! downloads) but this is simply a hardware issue which can not be addressed. Im using a class 2 sd only and i dont think that this can get ANY better. I think btrfs should run like HELL on a class 6+ card.
Update dec 14: Atm i'm using btrfs with "ssd_spread" (for ssd harddisk with older controllers. The controllers in SD should suck compared to some modern SSD so this will effect SD-Cards even more than "ssd" optimization (more info). And im amazed. It is even more smooth than nilfs (maybe less cpu) and so far the smoothest expirence i had with data2sd/data2ext. Even compared to EXT4 without journaling.
Why btrfs?
1. Btrfs is "copy-on-write" filesystem and i think that "copy-on-write" or logbased (like nilfs) will be the future.
2. Btrfs and nilfs are both better for "old" or "cheap" SSD-Drives because they are optimized for it. While this will decrease the performance of a modern SSD-Harddisk (since they are getting better and better in emulating a rotating device like a classic HD) it will INCREASE the general performance on ssd like an sd-card because their controllers is a lot worse than one of a state-of-the art SSD-Harddisk. So these optimization.
3. MeGoo (a linux made for smartphones) already has chosen it as default even though its still beta and i think they have some good reasons for this.
4. Btrfs has the same (and theoratically it should be even less - tiny) battery consumption. Other then nilfs wich had horrible battery (over 1%/h on its own even when phone was idle). Thats why i moved to btrfs from nilfs.
EDIT: Removed something really stupid xD
Safety concerns about data2btrfs
script: Considering the script i addressed ALL safety conserns that there are at present. This is based on the findings of the SGS devs and mounting directly on /data is even more save then cyanogen's app2sd+ (at least for the desire which unmounts /data - SGS doesn't). Only dalvik-cache is symlinked and a data corruption there is unimportant and can be helped by a simple wipe of the cache. So no concerns about this. (But note: the script is still "young" and there might be still errors - thats why i also don't provide a zip for ext4 yet)
btrfs is indeed still in an experimental state. But speaking FOR MYSELF ONLY (everyone should estimate this on its own) i don't have any concerns. The reasons are:
-experimental state is almost over and i doubt that there are any major bugs present.
-many Linux already use it and its default for MeGoo
-I have backups for all sensible data on my computer (like license keys - this can be lost if you backup already corrupted data with titanium/etc)
How to use it
(experienced linux users who know what they do ONLY)
- (recommended for ~ +20% speed) Delete your old ext partition create a new primary partition if it is not aligned yet. Gparted has a "align to mb" option wich makes alignement increadibly easy. Since 1024kb alignement is enough for sd there isn't anything else you need to care about.
- Make a btrfs partition with your favorite linux distribution (im still a ubuntu noob ) with btrfs utils.
- Make sure you flash a Rom that doesn't need sd-ext for installation (check the META-INF/../update-script for "copy_package XYZ SD-EXT:XYZ" - delete or format sd-ext there isn't a problem you will get an error (like on leedroid) on install but this doesn't matter)
-make sure you have Kernel with btrfs support (see below for this)
Kernels with btrfs support (SENSE ONLY for now)
-NeoPhyTe.x360 's (ext2, ext3, ext4, reiserfs, xfs, jfs, btrfs, nilfs2)
-Coutts99 Kernels (chose the btrfs-test-kernel ofc ;-) )
Known Issues
no btrfs support in recovery this means:
-no backup of the sd-ext partition (it isn't ext anymore ;-) )
-wont work with ROMs that need sd-ext for installation (some HD roms)
Thanks
- cyanogen who made app2sd+ in the first place.
- sibere and ownhere who started all the data2sd.
- supercurio and Unhelpful of SGS' Voodoolagfix (#Project-Voodoo on freenode) for their helpfull script tipps.
- Coutts99 and Neophyte for their Kernels.
- woti23 for all those test's in this thread.
- All devs of XDA in generall for all this nice stuff that is done here
Further Plans for the script
- Changing scheduler settings depending on results in the btrfs thread to get the last out of your SD while assuring safety (thanks woti23 for all the testing).
- Trying to add support to delete the ext partition and create it new with an 1024k alignement (~ +20% more speed)
- Mounting /app-cache to /cache or internal data partition (8 MB more RAM since its mounted on RAM)
- Changes for the mount options of the internal YAFFS2 Partition to optimize the speed of the "dalvik-cache" (have to look into YAFFS2 what can be done)
- Adding some lines of code to clear up any present symlinks on first boot to make it ROM upgrade compatible
- Adding e2fsck with check on every boot (script is quick edit of my script for btrfs - no e2fsck yet)
- Other changes based on the results in this or other threads about data2ext/data2sd
- Remove the errors i made ^^
---------------------------------------------------------------------------------------
Remark: i moved the data2ext4 script to my other script and set the dev tag again. I also added UBIFS discussion to the title. I also removed the nilfs utils and the data2ext4. The data2ext script can be found here. If someone wants to test nilfs you can PM me (but battery SUCKS incredibly )
---------------------------------------------------------------------------------------
Changelog: :
(dec 15): One minor change in assigning a variable. Doesn't change ANYTHING in actual behavior but code it's more "logical" (assigning the output of "busybox ls" to the variable instead of the command ^^ d'oh)
(dec 15) Fixed a stupid error that could lead to exit code (2) ....... and uploaded the proper file for btrfs (not the ext one). Sorry.... -.-
(dec 16) Fixed the fix ....
(dec 16) the scripts create now the folder it needs if it is not present yet (sorry i also forgot this in required ... was only there in the ext4 thread ^^)
=========================================================================
DISCLAIMER: BTRFS is still under development and thus an EXPERIMENTAL filesystem. Please refer to the btrfs wiki for more information.
melethron said:
Quick Info: NILFS2 - data2nilf2 will be much faster then data2ext and won't have Lags.
Long info:
After some thought's how to make things better for data2ext i started to think about how a flash based memory actually works.
Your Sd-card isn't a HDD (as you may have noticed ^^). It is actually a NAND based flash memory wich is divided into pages of 2-4kb and they are grouped to blocks of 128kb-512kb (!). But you will never see these. And you cant never change these (mkfs -b as much as you like ^^). This is done in hardware by a controller. All you will see is - you may call it an emulation - the LBA provided by the "flash translation Layer" (FTL). While the FTL can read/and write per page (2-4kb) it can't overwrite it. It needs to delete the data first AND THIS CAN ONLY BE DONE PER BLOCK !!! (Thats why read mb/s is higher then write mb/s).
What this means. Your filessystem should be aligned on the Blocks and should also avoid the need to erase blocks.
So forget every filesystem that my rock on your HDD (it may prefer e rewriteble sector if it's close f/e. If you "emulate" a filesystem through the controller it should respect the "true nature" of the hardware. A logbased filesystem would be far better since it will more likely take advantage of erased blocks. Also you may want that the blocks of the FS fit on the blocks of the NAND (alignement - but this mathes for every fs).
... Well long story short ... you need NILFS2
Links
http://www.usenix.org/event/lsf08/tech/shin_SSD.pdf
and this:
http://forum.xda-developers.com/showpost.php?p=7647224&postcount=21
(For germans: http://www.hardwareluxx.de/community/f227/os-optimierungen-fuer-flash-ssds-543445.html#post10373042)
Btw: In the XDA thread linked use it for the internal sd in samsung galaxy S for a LAGFIX. Wasn't lag the reason data2ext sucks atm.
My 2nd partition would already use this by now but there are 2 things needed:
-Kernel Support
-mount binary
Im to noobish to provide both ... so .... help ... anyone .... pls ?!
Click to expand...
Click to collapse
Ill try and sort a kernel
http://mirror.couttstech.com/android/bravo/kernel/nilfs_test_kernel.zip
Usual [email protected] kernel with NILFS built-in
As for mount binary. busybox mount might work. I've just been playing with aufs and normal mount worked for that.
coutts99 said:
Ill try and sort a kernel
Click to expand...
Click to collapse
NICE! looks far more promissing than btrfs (at least for flash memory)
melethron said:
NICE! looks far more promissing than btrfs (at least for flash memory)
Click to expand...
Click to collapse
I was going to have a play with this but forgot to bring home my spare sd card and my sd card adaptor
Sent from my HTC Desire using XDA App
Another One Nilfs2+Reiserfs
http://neophyte.vipme.com/ftp/_Extras/NeoPhyTe-2.6.32.26_Nilfs2_Reiserfs_v70.zip
coutts99 said:
http://mirror.couttstech.com/android/bravo/kernel/nilfs_test_kernel.zip
Usual [email protected] kernel with NILFS built-in
As for mount binary. busybox mount might work. I've just been playing with aufs and normal mount worked for that.
Click to expand...
Click to collapse
Thanks x 3 times.
About binary
"Mount -t auto" didn't work with nilfs2 with ubuntu. "Mount -t nilfs2" calls mount.nilfs2 i think.
EDIT: Did you add nilfs or nilfs2?
melethron said:
Thanks x 3 times.
About binary
"Mount -t auto" didn't work with nilfs2 with ubuntu. "Mount -t nilfs2" calls mount.nilfs2 i think.
EDIT: Did you add nilfs or nilfs2?
Click to expand...
Click to collapse
Nilfs2
Sent from my HTC Desire using XDA App
NeoPhyTe.x360 said:
Another One Nilfs2+Reiserfs
http://neophyte.vipme.com/ftp/_Extras/NeoPhyTe-2.6.32.26_Nilfs2_Reiserfs_v70.zip
Click to expand...
Click to collapse
Neo, have you got mount binary cross compiled for arm?
Sent from my HTC Desire using XDA App
coutts99 said:
Neo, have you got mount binary cross compiled for arm?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Not, we need this, but I havent got source of this.
need mkfs.reiserfs, and mkfs.nilfs2
http://forum.samdroid.net/f55/i-o-p...e-your-spica-ext2-2218/index44.html#post44349
NeoPhyTe.x360 said:
Not, we need this, but I havent got source of this.
need mkfs.reiserfs, and nilfs2
Click to expand...
Click to collapse
OK, if no one makes any progress tonight ill get on this tomorrow.
Thanks Neo!
Sent from my HTC Desire using XDA App
NeoPhyTe.x360 said:
http://forum.samdroid.net/f55/i-o-p...e-your-spica-ext2-2218/index44.html#post44349
Click to expand...
Click to collapse
Ah good link!
Sent from my HTC Desire using XDA App
I would just like to mention here that I made a special note about bloc alignment on sd card on my thread. I provided a link for that and FAT32 can be aligned to the actual bloc 128kb/512kb size of an sd/usb flash memory. This is the reason why I use 2 fat32 (aligned) partitons.
Sent from my HTC Desire using XDA App
melethron said:
Thanks x 3 times.
About binary
"Mount -t auto" didn't work with nilfs2 with ubuntu. "Mount -t nilfs2" calls mount.nilfs2 i think.
EDIT: Did you add nilfs or nilfs2?
Click to expand...
Click to collapse
ubuntu:
you maybe want to install nilfs2-tools first
then it mounts without -t option
am i the only one who is a little scared about this:
#> mount /dev/sdb1 /mnt/nilfs2
mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
sibere said:
I would just like to mention here that I made a special note about bloc alignment on sd card on my thread. I provided a link for that and FAT32 can be aligned to the actual bloc 128kb/512kb size of an sd/usb flash memory. This is thefbreason why I use 2 fat32 (aligned) partitons.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I still don't get the point using FAT for the 2nd partition. Also did you see what ownhere posted here:
Why create a small loopback device? the reason is item 3. But I found some bug with this case, any data write to loopback device need twice kernel IO command, one virtual one real, so the cpu usage will be high
Click to expand...
Click to collapse
About the 512kb. Are sure this is the max size "erase block" size for microsd?
melethron said:
I still don't get the point using FAT for the 2nd partition. Also did you see what ownhere posted here:
About the 512kb. Are sure this is the max size "erase block" size for microsd?
Click to expand...
Click to collapse
I have used loop so far because I have run some I/O test on my phone (not quadrant) and I always had a better result with loop than with direct format.
ownhere post is great but he's not always 100% right. For instance, the fact that ext2 partition when mounted on /data is not unmounted properly by the system in wrong. You can read my post here http://forum.xda-developers.com/showpost.php?p=9704670&postcount=9 to see the tests I did. I do confirm that the FS is unmounted by the system on shutdown.
About ext4 4K block size, you can do the same with EXT2 (my actual bloc size is 4096).
But I'm reading with great interest the thread about alternatives FS for NAND data storage. The erase block size is different for different devices and manufacturers. But at least if you align blocks to a multiple of 128kb, you will get a noticeable improvement in I/O than no alignment at all.
woti23 said:
ubuntu:
you maybe want to install nilfs2-tools first
then it mounts without -t option
am i the only one who is a little scared about this:
#> mount /dev/sdb1 /mnt/nilfs2
mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
Click to expand...
Click to collapse
y i have nilfs2-tools. I only meant that -t auto doesn't work. -t nilfs2 works fine.
I also got scared by the warning and googled the warning: http://www.spinics.net/lists/linux-nilfs/msg00595.html
Quoting a dev:
NILFS2 is almost stable. We have a record of nine months operation on in-house samba servers and a webDAV server.
> There is still still warning when mounting verbosely though:
> mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
> mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
>
> As per the first message, Is the on disk format expected to change any
> time soon?
Well, I don't want to change disk format in a way that breaks
compatibility. I'm considering to remove the above message at the
next utility release.
Click to expand...
Click to collapse
Reading this im willing to use it.
sibere said:
ownhere post is great but he's not always 100% right. For instance, the fact that ext2 partition when mounted on /data is not unmounted properly by the system in wrong. You can read my post here http://forum.xda-developers.com/showpost.php?p=9704670&postcount=9 to see the tests I did. I do confirm that the FS is unmounted by the system on shutdown.
Click to expand...
Click to collapse
ownhere got this (wrong) information from me don't blame him...
You proofed me wrong on this and i admit that i was only guessing ....
After reading cyanogens post i thought that he tried to mount on /data before or tried to create an init.d/rc0.d to make a clean unmount. I didn't dare to think that any good dev would just say "... give a **** about a proper umount and use a journling fs". I mean wtf ....
melethron said:
ownhere got this (wrong) information from me don't blame him...
You proofed me wrong on this and i admit that i was only guessing ....
After reading cyanogens post i thought that he tried to mount on /data before or tried to create an init.d/rc0.d to make a clean unmount. I didn't dare to think that any good dev would just say "... give a **** about a proper umount and use a journling fs". I mean wtf ....
Click to expand...
Click to collapse
Do you mean that you/he/they stated without trying ?
I never take a guess for granted
This is just a relay thread but, please, full read it and then, if you dare, jump to the master one!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doc_cheilvenerdi.org said:
Free Memory to > 1Gb!
How to Increase your Internal Memory Size with very low effort!
NOTICE: This method works both on Rooted and NOT Rooted Phones!
You simply need to meet three easy requirements:
Stock Firmware installed on the Phone (custom ROMS not supported ...They don't need to!)
A microSD with two primary formatted partitions inside (the former 'to FAT32' and the latter 'to EXT4' filesystems)
Ready to Flash to your Galaxy Mini via Odin
NOTICE: The following Black Box Howto is explained deep inside in post n. 2 and from post n. 52 to post 54!
...
Click to expand...
Click to collapse
Last Year, on December 18, I started the quoted thread for Galaxy Mini, showing a tweak useful to Increase the Internal Memory Size on Stock ROMs simply switching the data filesystem to the second partition of the microSD...
Benefits and disadvantages of this tweak are fully explained and discussed in the quoted Thread.
Question: Why I'm posting here, then?
Answer:
I received requests about tweaking the FIT boot images too...
I studied the FIT kernel vs Mini one and figured out that they are pretty equals (actually they full-match each other but only few stuffs related to post boot hardware detection)
I tried and made few images for FIT, which are shared in post n. 56 of the quoted thread, but - owning a Galaxy Mini - I was not able to test them...
...till now...
...
Angry about that and waiting for beta testers for them, I compared deep inside Galaxy Mini and Galaxy FIT...
Surprise: If I call them TWINS, the mistake is not so a mistake:
...At Kernel Layer they match each other...
...the bootloaders call the kernel at same memory address...
...boot sequences via ramdisk completely equal...
...system libraries are exactly the same...
...system software and leftovers too...
The only hardware differences don't really need to modify the boot sequence!
THAT'S ALL: I simply tested the FIT images on my Mini and they ends up and running...
THEY WORK!
What's Now?
I'll not repeat the Flashing procedure with Odin - you can read it on the quoted thread - but here are the FIT boot images actually modded and shared:
PDA=S5670DDKT3
PDA=S5670DXKPB
PDA=S5670DXKT4
PDA=S5670JPKQ7
PDA=S5670LUBKP6
PDA=S5670LUBKPI
PDA=S5670XWKTI
PDA=S5670XXKPQ
Your firmware is not listed? ...let me know!
Obviously you need Odin and Ops file ready for your phone model and not the Mini one...
- - -
Doc_cheilvenerdi.org said:
How does it Work:
Scenario 1:
I switch on the Phone, without a MicroSD slotted in or with a microSD with a single FAT32 partition (broken or damaged microSD also suite this scenario...); GingerBread boots as usual!
No Difference!
Scenario 2:
I switch on The Phone with a microSD slotted in (with the second partition formatted as EXT4 filesystem but still EMPTY); Ginger boots acting as if
/data
is completely moved outside to microSD but just WIPED (not true obviously, and the original /data is safe inside the phone), so it resettle it from beginning...
NOTICE:
...If your second partition is 1Gb wide...
...your new Internal Memory will be 1Gb wide...
Scenario 3:
I switch on the Phone with the second partition of the microsd (EXT4) up and running (already resettled up for use and with my userdata on it); Ginger simply boots with
/data
moved outside to microSD with your userdata there and tons of apps just installed from the market...
Click to expand...
Click to collapse
- - -
Doc_cheilvenerdi.org said:
NOTICES & ADVICES:
If I want to remove the microSD from the slot, FIRST I NEED TO SWITCH OFF THE PHONE!
When I install apps from the Market, Ginger Misunderstands the actual new Internal Memory SIZE and puts the apk files to External Storage anyway! I simply need to move them "to the phone" via "Settings menu" immediately after!
When I switch on the Phone without the microSD, I boot using the original /data inside the phone, actually loosing all the apps installed onto the external one untill next boot with SDcard; and, of course, loosing my sms stored there and others personal userdata too.
Unfortunately this boot image heavy conflicts with Link2SD (great app anyway!), so you must choose one: This Boot image or Link2SD... not both... sorry!
Click to expand...
Click to collapse
- - -
Don't You Like the boot image just installed and You want to revert without flashing the full firmware to the Phone?
Here are the original images ready for Odin:
PDA=S5670DDKT3
PDA=S5670DXKPB
PDA=S5670DXKT4
PDA=S5670JPKQ7
PDA=S5670LUBKP6
PDA=S5670LUBKPI
PDA=S5670XWKTI
PDA=S5670XXKPQ
Thread News!
Have you got an "unsigned update.zip capable recovery"?
Here a list of update.zip files ready to flash without Odin:
PDA=update-S5670JPKQ7.zip
PDA=update-S5670XWKTI.zip
I'm from Europe. I have installed S5670XXKPQ. Can something be done for this firmware?
Nice! Thank you, you made it for latin america version
Enviado desde mi GT-S5670L usando Tapatalk
New Image Added!
ZmisiS said:
I'm from Europe. I have installed S5670XXKPQ. Can something be done for this firmware?
Click to expand...
Click to collapse
NEW BOOT IMAGES ADDED!
Just added this boot.img (First Post for downloads):
S5670XXKPQ (2.3.6)
Doc_cheilvenerdi.org said:
NEW BOOT IMAGES ADDED!
Just added this boot.img (First Post for downloads):
S5670XXKPQ (2.3.6)
Click to expand...
Click to collapse
Thanks for this.
I forgot to mention that I have installed OC 844 MHz Kernel. Because it does not work for me. I have to reinstall and then try.
Don't work for me.
SD Make-up!
When you get true internal memory size even after tweak, something went wrong while making 2nd partition on SD...
You should first check How you made the second partition on your SD Card...
You can resize the first one (FAT32) or start from scratch (two new empty partitions); anyway, They both must be primary and the 2nd must be EXT4 newly formatted (mandatory).
If you feel you've done right, you could check what's happened with an app I just wrote to check the 2nd filesystem for errors. You can find it here; it's a Beta Version but fully working...
Read carefully the post and, eventually, give it a try.
P.S. It seems, otherwise, that you shoud partition your SD out of the phone (USB or MMC adapter needed). Actually Everybody who asked me for the same troubleshooting, solved it using Minitool Partition Wizard on Windows or GParted on Linux, BUT acting on the SD outside of the Phone!
P.S.2 No need to flash again! If the phone booted, the image is up and running fine...
I used USB, opened Mini Tool Partition Wizard, wiped all the SD, Apple, made a primary FAT32 partition, created a primary ext4 partition, Apple, waited till everything is over and that's it.
The problem remains the same.
Again flashed PDA S5670XXKPQ = (2.3.6) and same problem again.
apple style partition?
---------- Post added at 02:42 PM ---------- Previous post was at 02:42 PM ----------
MBR/GUID wont work?
Thanks! Gud work!
Doc_cheilvenerdi.org said:
When you get true internal memory size even after tweak, something went wrong while making 2nd partition on SD...
You should first check How you made the second partition on your SD Card...
You can resize the first one (FAT32) or start from scratch (two new empty partitions); anyway, They both must be primary and the 2nd must be EXT4 newly formatted (mandatory).
If you feel you've done right, you could check what's happened with an app I just wrote to check the 2nd filesystem for errors. You can find it here; it's a Beta Version but fully working...
Read carefully the post and, eventually, give it a try.
P.S. It seems, otherwise, that you shoud partition your SD out of the phone (USB or MMC adapter needed). Actually Everybody who asked me for the same troubleshooting, solved it using Minitool Partition Wizard on Windows or GParted on Linux, BUT acting on the SD outside of the Phone!
P.S.2 No need to flash again! If the phone booted, the image is up and running fine...
Click to expand...
Click to collapse
Now work. Thanks.
Doc_cheilvenerdi.org said:
This is just a relay thread but, please, full read it and then, if you dare, jump to the master one!
- - -
- - -
- - -
Click to expand...
Click to collapse
thnx for your thread..
Btw can u tell me wat lines or files should v add in boot.img to have this memory hack ..??
using G FIT
Everything shared!
amn_grg said:
... wat lines or files should v add in boot.img to have this memory hack ..??
Click to expand...
Click to collapse
It's all explained in post n. 2 and, deep inside, from post n. 52 to post 54 of the master thread referenced in the beginning.
There you can find links to scripts, source codes and binaries that I used...
...Everything you need to do it on your own!
i m from indonesia S5670DXKPB
Is this true?? Add more size my internal memory or......???
Sent from my GT-S5670 using XDA App
Added Image and Thanks!
NEW BOOT IMAGE ADDED!
Just added this boot.img (First Post for downloads):
S5670DXKPB (2.3.4)
CREDITS:
And many Thanks to Maleficus90 cool who helped me out, while testing SDcard's performance on LUBKP6 PDA boot image!
i m from romania S5670XWKQ(2.3.4)
spaga said:
i m from romania S5670XWKQ(2.3.4)
Click to expand...
Click to collapse
I think that you can use S5670XXKPQ (2.3.6) and S5670XWKT2 (2.3.6). It is for Europe.
S5670XXKPQ is official firmware. I checked on the KIES Samsung.
New images...
NEW BOOT IMAGES ADDED!
Just added this boot.img (First Post for downloads):
S5670DDKT3 (2.3.6)
i am using cyanogenmode 7.2 and my baseband version is ddkt2...so can i use ddkt3 boot.image?
Original Post | CWM
Guys check this out
Best result on Android 4.+
Description
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Click to expand...
Click to collapse
Quote Original Post link - Click Here
UPDATE: Seeder_v7 is out, as suggested by pepoluan, it now detects for qrngd (built in rngd for Qualcomm Snapdragon-based devices), if it is there, then it will not start as rngd may conflict with it...the rngd binary is also using the latest version (it is turned off when screen is off)...users of previous versions can just flash it over...
INSTALLING
You need init.d support for this!
Download and flash:
http://www.androidfilehost.com/?fid=9390248398092764755
Here is a mirror... http://d-h.st/REX
How to use this script?:
After flashing, launch terminal emulator and type
Code:
su
seeder
You will get a menu like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: There will be NO app after flashing! This only installs the necessary binaries and scripts...
For those who cannot install via recovery:
You get a status 0 error -> replace the update-binary in Seeder_v6.zip with one from another zip that works with your device
OR
Use the new installation method!
Instructions:
1. Download Seeder_v7_non-CWM.zip from here:
http://www.androidfilehost.com/?fid=9390248398092764756
2. Extract the zip, you will get a folder named "install"
3. Place the folder in the root of your sdcard (/sdcard)
4. Launch terminal emulator, type:
Code:
su
cd /sdcard/install
sh install.sh
5. Ignore any error messages (those are only warnings, only happens to current users)
6. You are done! The script will auto-delete the "install" folder as it is not required anymore...
Sample output:
UNINSTALLING:
And now for the way to clean up Seeder_7:
Via recovery:
Flash Seeder_v6&7_Uninstall.zip:
http://www.androidfilehost.com/?fid=9390248398092764753
Via terminal:
1. Download Seeder_v6&7_Uninstall_non-CWM.zip:
http://www.androidfilehost.com/?fid=9390248398092764145
2. Extract it to the root of your sdcard (/sdcard), you should get a file named uninstall.sh
3. Launch terminal emulator and type this:
Code:
su
cd /sdcard
sh uninstall.sh
4. You are done! Everything gets cleaned up, including uninstall.sh...
Click to expand...
Click to collapse
Flash now works, you can now type in terminal to turn off/on and also easier remove. Up to u if ud like to try. Note" it may drain battery more" so please do not be going all against tweak. Thanks
FLASH THIS ON GINGERBREAD!?!?!(v1.4.0)
Thanks to Zen Arcade for making a flash for Gingerbread! His Post Here!
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Sorry if this is a n00b question, but if you just install the .apk do you still need to change the permissions or does it take care of it for you?
dginsd said:
Sorry if this is a n00b question, but if you just install the .apk do you still need to change the permissions or does it take care of it for you?
Click to expand...
Click to collapse
Is best to just fix Perm to brr safe, easiest way to do so if you just install the app is to go to recovery/advanced/fix permissions and reboot
Sent from my SGH-I997 using xda premium
I stumbled upon this myself a few days ago and have been looking into it... I can easily implement it into my source builds, but want to see how it reacts first before doing so. And btw bradman... CM10.1 is smooth as **** with nothing needed... but if this makes it even better, then thats good to hear.
Anyone tried this on 2.3.6?
im aware its smooth good job! i was just testing it on infuse and i currently had ur rom so i just gave it a try to confirm it working on infuse
wawaweewa said:
Anyone tried this on 2.3.6?
Click to expand...
Click to collapse
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
bradman117 said:
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
Click to expand...
Click to collapse
I updated OP so that if flash doesn't work i have download files to manually do
bradman117 said:
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
Click to expand...
Click to collapse
that is what i am doing now! im on saurom jvu atm thanks for the quick reply ill let you know how it turns out
EDIT: i hope it works so my online game will run smoothly!
I must say, this relatively minor tweak provides a noticeable boost. I'm currently using Liquid Smooth RC9.11 with no further tweaks. After applying this tweak I've noticed faster loading times for a couple games, Google maps is much more responsive to massive view changes, web browsing is snappier, and as stated above almost no redraw delay when returning to the launcher after running a large app (like a game). I must say this under-powered and under-RAMmed little Infuse just keeps getting better and better thanks to all the work the devs here. Keep up the good work!
deathblade said:
Is best to just fix Perm to brr safe, easiest way to do so if you just install the app is to go to recovery/advanced/fix permissions and reboot
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for the tip
dginsd said:
Thanks for the tip
Click to expand...
Click to collapse
so i just have to flash the zip in recovery then fix permission and that's it?
just flash it will do permission
Working CWM Flashable for Infuse GB
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
UPDATE - 2012/01/03
I've confirmed the documented improvement in speed at which Maps re-tiles the map display when making big location changes. Still testing other apps. Some games appear a big less laggy, although some disruptive lag events still occur (I suspect due to file system i/o scheduler delays rather than from lack of random/entropy data as addressed with this enhancement). I'll do some benchmarking over the weekend and report back with results.
Zen Arcade said:
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd?
Click to expand...
Click to collapse
I currently cant test this but if it turns out to work ill put it on OP. i did hear from someone that the biggest difference on GB but i cant say that for y self because i have not tried yet
I gotta say, it's very smooth so far.
Works fine on Scott's CM10. PS shows the rngd process running. Thanks
Zen Arcade said:
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Sent from my SGH-I997 using xda premium
Heyyy Scott, check out this guys find
lordvincent 90 posted it..
Originally Posted by zeppelinrox
So I did a bit of digging and a bit of research and a bit of testing.
I really dunno if the tweak makes that big of an effect but I did discover a nice trick to have a nice fat entropy_avail with zero overhead.
One of the first pages I skimmed was http://linux.die.net/man/4/random which mentioned at the bottom these other files:
read_wakeup_threshold contains the number of bits of entropy required for waking up processes that sleep waiting for entropy from /dev/random.
write_wakeup_threshold contains the number of bits of entropy below which we wake up processes that do a select() or poll() for write access to /dev/random.
Normally, read_wakeup_threshold is 64 and write_wakeup_threshold is 128
I also wondered why most users report that their entropy_avail was by default in the 200ish range while mine was always by default over 300.
I had also found this page at linuxinsight. I had used that site alot when researching Kick Ass Kernelizer's sysctl tweaks.
So I thought, hey I wonder if I can use sysctl to set good values and low and behold, I looked in my script and I already have settings for both lol:
Code:
busybox sysctl -e -w kernel.random.read_wakeup_threshold=128;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=256;
As you can see, I had doubled the default values - and that's why my entropy_avail was always over 300.
So I decided to mess with sysctl a bit.
Connected the phone to the laptop.
In one command prompt I watched the entropy_avail with this one liner:
Code:
while :; do cat /proc/sys/kernel/random/entropy_avail; sleep 1;done
In a second command prompt I did the sysctl thing...
I found that write_wakeup_threshold didn't effect entropy_avail at all.
But read_wakeup_threshold is a totally different story
I did
Code:
busybox sysctl -w kernel.random.read_wakeup_threshold=2048
The entropy_avail just started climbing....
All the way up to 3600+ and just stayed there. Never went down at all.
Actually, the more I did stuff with the phone, the faster the level would climb.
So it would never go down and would never get used.
I thought well maybe I should lower it so it does get used.
I kept lowering read_wakeup_threshold until it got down to 1200 and finally entropy_avail dropped to 2400+ and kept climbing until 3600 and then would drop to 2400 immediately and up again and so on...
I played with different values.
Setting it to 1000... entropy would go up to 3000 and then drop to 2000 and up to 3000 again....
Setting to 750.... entropy would go up to 2250 and drop to 1500 and up to 2250 again...
So the pattern is:
max entropy_avail=read_wakeup_threshold * 3
min. entropy_avail=read_wakeup_threshold * 2 (ie. read_wakeup_threshold * 3 - read_wakeup_threshold)
So it builds up 3 times the read_wakeup_threshold and then when it hits that limit, it drops the value of read_wakeup_threshold.
If you want to lock it it at the highest possible value (4096), you'd do:
Code:
echo 1366 > /proc/sys/kernel/random/read_wakeup_threshold
Or
Code:
busybox sysctl -w kernel.random.read_wakeup_threshold=1366
You can add either of those to any init.d script.
However, on my device, it won't go over 3600 so you can test for yourself how high yours will go.
If all you can get is 3600ish just go with 1200 (ie. 3600/3)
In Kick Ass Kernelizer I'm gonna make it like so:
Code:
busybox sysctl -e -w kernel.random.read_wakeup_threshold=1024;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=2048;
That will make it bounce between 3072 max and 2048 min.
I'm making write_wakeup_threshold twice the amount of read_wakeup_threshold simply because that's what it is by default.
But hey, maybe I can save battery life if I make it 1280 just so it stays locked in at 3600+ and it doesn't have to keep rebuilding entropy_avail lol
So conclusion is: since there is a definite pattern on how entropy was being built up to a pre-determined level and dropped to a pre-determined level, it wasn't actually being used. That's just how it's programmed.
If the setting isn't there to "hold" all the entropy, it just drops/flushes it and force feeding it entropy won't make it not spit it out
So at least I found the setting that will make it hold it in lol
Maybe somebody would like to give it a try and test to see if it actually saves battery by setting read_wakeup_threshold to 1366.
Click to expand...
Click to collapse
lordvincent 90 posted it..
Just adding this, after reading the whole thread here it seems like this may be a simpler solution (and better on battery life)
Click to expand...
Click to collapse
Post Link -- http://forum.xda-developers.com/showpost.php?p=36208713&postcount=32
Zen Arcade said:
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Anyone tried this?
Btw brad im on jvu saurom and flashed it fix permission but this is what i get
Tweak
This relatively minor tweak provides a noticeable boost. I'm currently using Liquid Smooth RC9.11 with no further tweaks. After applying this tweak I've noticed faster loading times for a couple games, Google maps is much more responsive to massive view changes, web browsing is snappier, and as stated above almost no redraw delay when returning to the launcher after running a large app (like a game). I must say this under-powered and under-RAMmed little Infuse just keeps getting better and better thanks to all the work the devs here. Keep up the good work!
BR
*/Haters gonna hate/*
ROM currently "DISCONTINUED". But, the init.rc tweak remains :fingers-crossed:
Hi to all those who are reading this! Lemme answer a few questions before I get started.
First of all, What kinda name is this???
TBH, I haven't yet thinked of a name for this... So, I just named it Stock ROM MOD
And, the name has been thought of! The name is... CyanicSense! Why this name? More details later
What does this do?
Though this is gonna be as stock as possible, the major feature that I had planned out for this is reversed-mount. As you might know, stock ROMs definitely do have mounts2sd (which might give some trouble in setting up), but, complete reversed-mount (i.e. the /sd-ext partition mounted as the /data partition as the int2ext script does, hasn't been achieved yet (on stock ROM). So, practically, this does that stuff.
How is this even possible?
Believe me. This ain’t no magic. Simple init.rc tweak… Mounting the mtdblk0p2 partition, which is basically the sd-ext partition as we better know it, in the /data folder does the trick. In CyanogenMod, this is done via the famous int2ext script…This is a more or less similar command, done during startup. Just make some changes to init.rc, and Voila!!! Your sd-ext is mounted in the /data partition.
So, why make a new thread for this???
Erm, but that ain’t the end of story here. I am planning on some more features. Current features are minimal, reversed-mount, and updated apps. Yep. Updated apps, not one but all of them. I can assure you that you will have every single update including Google Play Store v4.0.xx in this ROM. Also, applications which were basically “stub’s” have also been updated, so that you wouldn’t have to download any more apps. P.S. I have added a small file explorer, named “Explorer”, by Speed Software, the same people who brought about “Root Explorer”. Planning to replace it with OI File Manager in next build, if people prefer it
So, those were the two features of this ROM. Also, I am planning to work on some other features, which mainly include, init.d script support, and, removing bloatware. Currently, there are around 10 apps which I don’t use, and presume that most other users wouldn’t be using it either. So, I am gonna either make them uninstallable, or remove them completely, so that one can get more /system space More features might come up too. You can request new features, but… be reasonable
Is it safe???
I can’t answer that question, but, I am guessing the answer is yes. Why I think so??? Because I am using this as my daily driver for the past few days. Also, “reverse-mount” via scripts like int2ext, and mounts2sd do the same thing, so, I don’t think its gonna create problems
Will it make my phone laggy?
Not sure. Works fine in my Class 4, 8 GB memory card. Anything Class 4 and above, I assure you it wouldn’t “visibly” lag.
What about gaming?
Well, this is the part where you come in. I don’t use my phone for gaming, so, I can’t be sure whether Temple Run 2 is lagging, or its I who can’t play it properly But, one fact can be sure that Stock ROM isn’t always the best choice for gaming.
Anything else left?
Yeah… This build is… kinda heavy. 160+ MB is definitely too big for the “stock” ROM. It is because of all the updated apps which were included. I will try to make subsequent builds lighter, and more bloatware free
Now that Q&A Section is over, let’s get back to business. The simple init.rc tweak is explained in the next post.
Instructions:
Pretty basic. Wipe everything, except SD-Card, and flash the ROM.
The following video might give you a slight idea
P.S.: Recovery used: TWRP 2.5.0.0 (http://forum.xda-developers.com/showthread.php?t=2123503)
Bugs:
I need help with that If you encounter any bugs, please report immediately in this thread.
Downloads:
Link: http://www.mediafire.com/?8grcxx1rbngr6g2
Here is the link… 162 MB approx. Why so big? You are the typical TLDR case. Read the Q&A section above.
Beta Link: http://forum.xda-developers.com/showpost.php?p=41966646&postcount=19
Any issues, please post in this thread. I will try to fix it, ASAP
init.rc tweak that I used:
First of all, get a stock boot.img, and boot_img tools from here: https://github.com/sakindia123/boot-image-tools
Unpack it to some location safe, and, copy-paste the boot.img into this folder.
Then, run the following commands:
Code:
mkdir -p unpack
Code:
./unpackbootimg -i ./boot.img -o unpack
Code:
mkdir -p boot
Code:
cd boot
Code:
gzip -dc ../unpack/boot.img-ramdisk.gz | cpio -i
Code:
cd ../
Thus, you will have the ramdisk of your boot.img in the "boot" folder. Open up that folder, and open "init.rc" with any of your favourite editor.
Now, search for this line:
Code:
mount yaffs2 [email protected] /data
Replace that line with this:
Code:
mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
Now, I know you are confused... I too was, at first. So, let me make things clearer for you...
This is basically a mount command, which is executed in this order
mount [type of partition] [partition] [mount directory] [options]
So, the partition type is ext3, to be made more compatible with most devices.
/dev/block/mmcblk0p2 is the sd-ext partition.
/data is the folder we are going to mount the partition in.
nosuid and nodev: Allow an ordinary (i.e., non-root) user to mount the filesystem if one of his groups matches the group of the device.
noatime and nodiratime: Access timestamps are not updated when a file is read. So, there is no writing on the partition everytime the disk is read.
barrier=0
This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance penalty. The ext3 filesystem enables write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure.
data=ordered
Specifies the journalling mode for file data. Metadata is always journaled.
commit=15
Sync all data and metadata every 15 seconds.
noauto_da_alloc
does give a slight performance increase, especially when working with databases..
nouser_xattr
Support "user." extended attributes (or not).
errors=continue
Define the behaviour when an error is encountered.
Reserved, for screenshots
Yo, screenshots will occupy this post
Reserved,
in case i forgot anything to say
i admit, i typed this in a hurry...
credits are yet to be given, so... please don't flame here
Nice work bro.
For I understand it, is a stock ROM with memory script by you only, yes?
Sorry my english lvl xDDD....
Good job
Edit: well.. must say brother you did good work..
Rom is purely stock with only this tiny mod..
No bugs till now
This ain't no memory script.
TBH, I haven't even enabled init.d support yet. This is solely related to boot.img's init.rc... Which initiates reverse mount when you start your phone.
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Yes.
@rcane said:
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Stock ROM, version: 1.43.720.2
Brother.. here's a big problem..
The data folder of the Rom is now empty and all the app's apk files and app data installed can't be accessed using the root explorer..
And it is no where.. o can't find them..
Did you make a link to the data folder while mounting the ext partition to data..??
Sent from noob machines
I recommend using another application.
P.s. you will find it in the data folder only. It won't be in the sd-ext folder.
P.s. sorry for the short reply. I ain't at home currently
Sent from my HTC Explorer A310e using xda app-developers app
I used solid explorer..
I got them.. but on es file explorer.. the folder is still empty..
And also there is no sd-ext folder in root... Because you didn't make one..
Sent from noob machines
Did you enable Root Explorer or so...
AFAIK, even in the latest update, root exploration should be first enabled.
Press menu key, and in tools option, there will be the "root explorer" option, or a similar option.
Enable that, and then, you will be able to browse the data partition.
P.S.: if you don't get a superuser request, it will not work.
OK got it...
Thanks brother...
I got my mistake... it works now..:good:
Ohk, tiny flashable zip's coming up!!! HELP NEEDED!
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
me..
vineethraj49 said:
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
Click to expand...
Click to collapse
if u find something i can do , feel free to tell..
Thanks
artistaditya said:
if u find something i can do , feel free to tell..
Click to expand...
Click to collapse
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
I have this..
vineethraj49 said:
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
Click to expand...
Click to collapse
Sorry i dont have access to all the roms but i can give you information on Nextgen and jaggyrom..
--JaggyRom [specific version 3.2.1 lite]
1.) init.d support - yes
2.) apps2sd script used [without gui]
boot.img here- jaggyrom_boot.img
--NextGen [specific version 1.5]
1.) init.d support - yes
2.) mounts2sd script used [without gui]
boot.img here- nextgen_boot.img
Note to Beta testers! Cyanic Sense Beta is out!
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Screenshots
vineethraj49 said:
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Click to expand...
Click to collapse
Seems the OP forgot to add the "obligatory" screenshots
No worries here I am xD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Seems OP is working great,waiting for future updates!
Finally...
The update to Android M is finally here!
If you can't wait any longer, here's how you can update any version of the H955 (A,P ...) or you Korean G Flex 2 (F510L) to 6.0.1!
*Thanks to ap3rs, we now have a video about the MM update here!
*KNOWN ISSUE
Some users get after every boot an error. This 'error' is nothing more than a reminder your KDZ is not the official network provider one's. As we have no root, there's no fix for this. If you can't live with this error, I suggest you stay on LP for a few more days and wait for the OTA update . Again, this error isn't actually a problem or anything, it won't do anything.
*Before posting any benchmark results or throttling issues:
Right after the installation, it is normal that your battery is draining, the UI is slow, the SD810 heats up and throttles and your benchmark scores are low.
Let the battery drain itself completely, and charge it in time fully to 100%. This will re-calibrate the battery. Post your opinion after a full day of use .
MisterOne1's benchmark went up by 15% after Android was settled.
*Step by step instructions:
*Make sure you unroot first, because there isn't root (yet) on MM.
0. Charge your device to at least 30%
1. Make a backup with LG Backup Service in settings (ON EXTERNAL SD)
2. Remove SD CARD
3. Download the KDZ for your device:
H955 here
F510L here, thanks to @Kevin3688
4.1 Download LG UP ( https://mega.nz/#!JtRFkD4Y!u3QgNNaUc-q9w86bBYVoLa9bDBIKA4IZAC57m3rFcsI )
4.2 Download the SD810 drivers ( https://mega.nz/#!VhpDxKoI!Mo0LcQOVOjcM337Vs2X87KoEMvE3HApYgpFNMYEl4XU )
5. Install both
6. Connect your phone to your pc (with USB debugging disabled!) and launch the LG UP
7. Select UPGRADE
8. After clicking on the three dots on the right side next to BIN FILE, select the KDZ
9. Click on start
10. Let it cook for a while :
11. profit!
Also don't forget to disable LG MLT, as it is known to drain battery like ****, and uses A LOT of background resources!
1. Dial *#546368#*955# if in your phone app
2. Click on SVC
3. Open up "LDB"
4. Uncheck the "Enable, MLT will run after booting"
*Noticeable changes so far:
less lag
apps open a bit faster (imo)
Camera app is the same
New UI design (much smoother, closer to stock and more beautiful)
New Settings app
New Gallery app
Flashlight toggle (finally lol)
Far better readability in broad daylight
New dialer app
New contacts app
Quicker and better camera
No more overheating issues
New notification design
New option to eliminate background usage in battery saving mode
Massively increased overall performance
Increased multitasking performance
Google Now On Tap!
*My phone was EXTREMELY laggy on LP, even after optimizing and tweaking. Now, the lag is gone and my phone's overall performance improved massively
*The Update installs 1 bloatware-carrier app, but you can easily uninstall it
*Battery update 06/17
On Lollipop, my SOT was really bad (2,5H)
On Marshmallow, my SOT increased massively! With heavy usage, and games like Asphalt 8 and Temple Run 2, I got nearly 4h of SOT.
With light usage, I could get even more. Bluetooth was on all the time (Pebble watch ) and either Mobile data or Wifi was on. Also, I left location services on and recorded 12 minutes in 4K
*Benchmarking
I got on LP an Antutu score of 62k, as you can see in the screenshot, that increased to 76k. Marshmallow did some crazy stuff with my device.
On Geekbench 3, my results were a tiny bit higher than the screenshots in the following post. I got an SC score of 1270 and MC score of 3470. The second Geekbench test, I got even higher: SC score of 1277 and MC score of 3837!
View attachment 3786186
*DPI Change!
UPDATE: After changing the DPI, the app drawer icon of the stock LG launcher will bug out. I recommend using a different launcher (Google Now launcher, Nova Launcher ...), as this solves the issue. I think the 'compromise' of using Nova instead of the stock launcher is nothing compared to the difference it makes in the UI. I'll add some screenshots soon.
This post is getting quite big
The most important reason for me to root on LP was to change the DPI, as I find the stock 650'ish DPI unusable. Now on MM, without root, DPI change is possible through ADB and Fastboot! Here's how:
1. Enable USB Debugging in developer options
2. Install ADB and Fastboot ( http://forum.xda-developers.com/showthread.php?t=2317790 )
3. Connect your phone to the pc and open the ADB shell
4. copy and paste the following command (without the "$" ofc), and change 'DPI' to whatever you like! (I have mine set on 420)
$ adb shell wm density DPI && adb reboot
5. Enter
6. Let your phone reboot and enjoy!
Examples:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: (Thanks to: this user)
To change your DPI back to stock, use the following command:
$ adb shell wm density reset && adb reboot
*How to enable adoptable storage!
(Big thanks to this user on reddit and this post .)
So, I've finally managed to get adoptable storage working. However, be careful, as you can lose all of your data, if you accidentally erase the wrong volume.
Warning: this wil format your external SD --> you'll lose all the data stored on your external SD!
DRAWBACK: You can't acces the merged storage by PC nor third party android File Managers.
You can adopt your SD Card in 2 ways:
1. The whole SD card is merged, so if you've got an 64GB SD, you get 16+64GB internal storage:
1. Enable USB Debugging in developer options
2. Install ADB and Fastboot ( http://forum.xda-developers.com/showthread.php?t=2317790 )
3. Connect your phone to the pc and open the ADB shell
4. Copy and paste the following commands
$ adb shell
$ sm set-force-adoptable true
$ sm list-disks adoptable
This will give you the number of your (adoptable) external SD card. In my occasion, it resulted in:
disk:179,64
5. Following, partition the SD card as internal storage:
$ sm partition disk:179,64 private
6. Now, list the volumes
$ sm list-volumes all
That should result in something like:
private:179,66 mounted <a strange code>
private mounted null
emulated mounted null
emulated:179,66 unmounted null
The 2 volumes with a code looking like your disk, are the volumes of the SD.
7. Reboot through:
$ reboot
8. Disconnect your phone, and head over to 'Storage and USB' in the settings
You should see that the Internal storage is merged with the SD card storage!
2. The SD card is partitioned, so that you have a chosen part being merged, and the other one being external storage
This one is a little bit trickier. Don't try if you don't know what you're doing. This tweak depends on your skills, as you may encounter some issues that you need to solve yourself. If you don't know the "sm" commands yet, type in the adb shell: $ adb shell sm help
1. Make sure the SD card is empty, and has ONE or NONE partition
2. Insert SD card and format it through settings>storage options>external SD card>options>format
3. Follow step 1-4 from above
3.1 Execute the following command
$ sm list-volumes
4. Perform the following command (this might take a while!)
$ sm partition disk:179,64 mixed xx
and replace the xx by a percentage. This is the percentage of the SD card you want to keep as external storage! E.G. 64GB SD and 25 will result in 48GB merged and 16 extern.
5. List volumes again and note the difference
$ sm list-volumes
You should see two new partitions, with a comparable number to your disk.
6. Officially, this is it. But I've noticed that on my phone, the merged partition always seems to be corrupt. This is the fix:
7. Format the public:xxx,xx volume (this is the external storage partition, replace ofc the x's with the correct number)
$ sm format public:xxx,xx
8. Format the private:xxx,xx volume (this is the merged partition! THIS TAKES SOME TIME! On my phone, A 48GB partition took about 10minutes to format!)
9. You might get an error, but don't worry! Open up the storage setting on your phone, you should see that the merged partition is still formatting!
10. DO NOT DISCONNECT FROM YOUR PC! This might result in a broken SD card!
11. Wait till the formatting is done. The state of the partition changes in unmounted (=unassigned). Exit the adb shell, and safely eject you phone from the pc!
12. Click on the merged partition on your phone, your G Flex 2 will ask if you want to mount it. Click on accept, and now you should have two separate partitions. One being merged, the other one being external storage!
13. As a safety precaution, it's recommended to reboot, to let all the apps recognize the merged partition.
However...
If you want to acces your files on external SD through a external file manager, or by pc; neither will recognize your 'merged SD' or 'merged partition'. This is why I've described two options to merge the SD Card.
UPDATE: My pc suddenly detected the merged partition! But I wouldn't count on it, because I don't know why it suddenly detected it
Some users reported of errors after partitioning a disk as private/public (timeout issue). This is the same issue as I described in step 9 of way 2. Just let it do it's thing. After a while, when you're sure it's done, just reboot. You will get the wanted result, no matter what the error was.
*Downgrade to 5.1.1
Thanks to michele955 and shakeyabooti!
michele955 said:
Downgrading from mm (20a) to lollipop (15e) works with LGUP
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient
credits to @shakeyabooti
Click to expand...
Click to collapse
So if you decide to try MM and you don't like it, downgrade is possible!
LP KDZ files can be found here
I've worked hard to make this post being what is it now. Please don't copy pieces out of it, without referring to the people I thanked and me.
Alarm works for me!
I've attached some benhmark tests.
MisterOne1 said:
Alarm works for me!
Click to expand...
Click to collapse
Android M battery saving kicks in after a while
I'll let you know tomorrow morning if it still works
EDIT:
Alarms indeed do still work
Thanks for your tutorial.... Could you provide any benchmark tests.... Like antutu, geekbench 3 etc.
And did LG improve the brightness adjustments.
Gesendet von meinem LG-H955 mit Tapatalk
assyriska said:
Thanks for your tutorial.... Could you provide any benchmark tests.... Like antutu, geekbench 3 etc.
And did LG improve the brightness adjustments.
Click to expand...
Click to collapse
The brightness is the same. I'll run some benchmarks and I'll post screenshots
MisterOne1 said:
The brightness is the same. I'll run some benchmarks and I'll post screenshots
Click to expand...
Click to collapse
you are wrong my friend...i test the brightness outside and now in sunlight legibility are improved...more bright, not a lot but the necessary to see better when outside! BTW, GPS is way way faster to lock than before...mine locks in less than 10 seconds.
xtreamer91 said:
you are wrong my friend...i test the brightness outside and now in sunlight legibility are improved...more bright, not a lot but the necessary to see better when outside! BTW, GPS is way way faster to lock than before...mine locks in less than 10 seconds.
Click to expand...
Click to collapse
Ok, I couldn't test maximum brightness because of thermal throttling, but the minimum brightness is the same, at least on my phone.
57.000 in antutu, and on lolipop i had 76.000, but for example NFS unlimited works far better then lollipop. The only problem i have is that the phone is hot every time i used for fb+messenger+instagram...that problem i never had on 15b
Camera Quality is far better, more sharp photos. Overal i love it, apps are starting faster, and no lag till now in menu and other apps.
Does it overheat the same as before?
djtinxo said:
Does it overheat the same as before?
Click to expand...
Click to collapse
Mine didn't overheat on lollipop, due to Kernel Auditor adjustments. Now, without root, the phone stays cool. I noticed my phone got a bit warm when charging and gaming at the same time.
Tomorrow evening, I'll post some screens of the battery usage and the new updated apps.
Sent from my LG-H955 using XDA-Developers mobile app
Downgrade to lollipop 5.1.1 is probably working, like LG G4, or brick the device?
Someone make a video of mm update and upload to YouTube!!
hey man can you tell me what version of opengl es have from antutu? open antutu -info -display section -opengl es driver version?
please
thank you
nikos5800 said:
hey man can you tell me what version of opengl es have from antutu? open antutu -info -display section -opengl es driver version?
please
thank you
Click to expand...
Click to collapse
OpenGL ES 3.1 [email protected]
jmd.desai08 said:
Someone make a video of mm update and upload to YouTube!!
Click to expand...
Click to collapse
What part of the tutorial don't you understand ? I'd be happy to help
Sent from my LG-H955 using XDA-Developers mobile app
Simonally said:
What part of the tutorial don't you understand ? I'd be happy to help
Sent from my LG-H955 using XDA-Developers mobile app
Click to expand...
Click to collapse
Not about the tutorial. He wants a review video of the update.
le grande magnetto said:
Not about the tutorial. He wants a review video of the update.
Click to expand...
Click to collapse
Yes review video!!
Guys any chance to flash this on H950 AT&T?
Manual camera shutter speed on other apps (like Proshot or Camera FV-5) it is limited yet to 0,6 seconds in this update?
My review:
Nothing special!
Sent from my LG-H955 using Tapatalk