yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] Ave_Hornet:
As for now, I did not notice any error in HWMEM=64 , but if I think well, that if the will not be any errors ,such modification will be commonplace in Your Kernel?

:silly: Btw. You Are CRAZY [MENTION=5695278]ChronoMonochrome[/MENTION] :) :good: :good:

Edit1. Searches for the network, but nothing works related to the Internet ,Anyone can confirm that ?
[Galaxy Ace II Android Development] ChronoMonochrome:
Damn it, it was too fast. I've seen some errors in kmsg and camera randomly FCs. I'm afraid that some errors in logs also can evidence about damage FS. I had to restore CWM backup to avoid camera FC, but even on usual kernel with orig HWMEM size I still have errors in kmsg when taking a photo:

<4>[ 54.664611] CM_NO_MORE_MEMORY domainId: 22, memType 7, wordSize 61440, alignement 15
<4>[ 54.664642] ALLOCATOR Dumping allocator "scratch" [0x00058800:0x00068800]
<4>[ 54.664642] Error: CM_NO_MORE_MEMORY: CM_AllocMpcMemory() failed
<6>[ 55.954864] dma dma0chan22: allocated logical channel (phy 3)

But I should say that I've previously used more unstable HWMEM size as low as mentioned 16 MB - and I've had some crashes which probably caused memory corruption(I do not mean the RAM, as is a non-volatile memory). The problem is that I've used dynamic fsync - now I came to conclusion that we should forget about using it - even simple app FC can cause problems, which persists until you restore full CWM backup. Does anyone have camera FC or errors in kmsg like above?
[Galaxy Ace II Android Development] ace2nutzer:
Yeah, exactly the same what i had said for some weeks.. it makes no sense.... kernel default is "0" Fsync ON and i've removed NT-APP Permission to make it fail-safe (for this tweak)..

usually it's no problem if we have a fresh cwm backup.. simply format /data and restore only /data .. in 99% of cases the system works normal again.. ;)
[Galaxy Ace II Android Development] xo.en:
Why was clear since beginning, but i remember talk about HOW to change it you-know-where over year ago :)

Now this topic is extremly interesting.

Vodka, will you make SAME kernel that's used in slimkat with HWMEM=64?

I fell off my chair seeing how this rom with your kernel works, this is totally unreal, man(14760 pts in antutu at 1.1ghz - also - machine works now at 500mhz like at 800mhz before).
[Galaxy Ace II Android Development] fluffi444:
Outstanding! Simply outstanding! :good:

Sorry to be without any information in this post. But this news must be celebrated.

EDIT

Using 68M without any issues... Camera/Video are working fine... with incredible RAM of 647 MB :good:
[Galaxy Ace II Android Development] shaqman89:
I could confirm this :good::good:

Edit:

Btw, would this work for any kernel [MENTION=5695278]ChronoMonochrome[/MENTION]? Or is it specific to yours?
[Galaxy Ace II Android Development] yowanvista:
Why not simply use dynamic memory allocation through CMA for all ION heaps to free up more RAM when not used by surfaceflinger, audio or other subsystems? Afaik legacy memory allocators like PMEM, CMEM, HWMEM were all deprecated when the unified memory manager (ION) was introduced in Android 4.0.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, I thought about dynamic memory allocation too. Unfortunately, with one thought it ended up. I do not have much experience in programming to do so. Too many things use HWMEM - if I'm not wrong, mali also use it. It doesn't seem to me a simple.

There are nothing specific to my kernel. As I said, it just adds new parameters "hwmem" and "mem" to the end of cmdline(it's much simplier to don't override old parameters but just do as it done). Therefore, it should work with every kernel.
[Galaxy Ace II Android Development] Devel0per95:
Should i flash the zip after chronokernel version 2.19 or no?
[Galaxy Ace II Android Development] ayas02:
HI [MENTION=5695278]ChronoMonochrome[/MENTION]

Take a look at "hwmem=72M@256M mem=55M@328M". 72M means size of HWMEM, "@256M" - its physical address. The same is for "mem" - 55M is size of nearest RAM bank.

if i change hwmem from 72 to 70 or 71 and mem from 55 to 60 or 56 its good for ace 2

and how i change this hwmem and mem ?

thanks sorry if my english is bad
[Galaxy Ace II Android Development] str3tch72:
I want to test it on my Ace 2. What is most stable value for our phone? And can You tell me how-to-do-it with noob-friendly tut? :D
[Galaxy Ace II Android Development] fluffi444:
A user with over 2000 post is not allowed to ask for an "noob-friendly how-to".

If you do so anyway you are just only to lazy to search or to lazy to switch brain to ON. :D :D

*just kidding (a bit)* :highfive:

Just flash complete Kernel - HWMEM changes are hardcoded in kernel...

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/mem_repart/

chrono_kernel_R2.21.2_hwmem68.zip is the latest with HWMEM68 which gives you 640 of RAM.

But be warned - Sooner or later some apps starting to FC without any obvious reason.
[Galaxy Ace II Android Development] sorset:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Good job , thnaks.

I remember , when we upgrade Android 2 to 4 , there was two partitions named param and normal , that shoud be replaced in order to increase memory from 500MB to 624 , so what was that?

Here is that thread
[Galaxy Ace II Android Development] ChronoMonochrome:
624MEM_V2.tar.md5 replaces bootloader, but 624MEM_V1.tar.md5 doesn't... It should be interesting itself, but I haven't any idea how it can work without replacing bootloader and its cmdline.

UPD. Maybe cmdline isn't hardcoded in bootloader, but written somewhere in param.lfs.
[Galaxy Ace II Android Development] ace2nutzer:
Right now flashed my Kernel with HWMEM=68 (646MB RAM) .. and now i just want to ask u how long i need to wait till some Apps starts to FC ?? :) - Of course just approxx. maybe after 1 day of usage ??? :D
[Galaxy Ace II Android Development] ChronoMonochrome:
Try to play with camera/player - there are chances, that camera will begin to (not, no FC, but message "unable to connect to camera" might appear). Within some hours or days also may happen sudden sound loss. Also some users faced signal dissapear. Better if you'll monitor dmesg - if you don't see failed memory allocations, it's fine, but usually everything is opposite.
[Galaxy Ace II Android Development] xo.en:
Cam is broken for two years(tbh - cam works flawlessly ONLY with stocks - 2.6.x, 4.x.x).

Hm..maybe i am wrong..
[Galaxy Ace II Android Development] ace2nutzer:
Yes i can confirm.. everything opposite :laugh:

Okay.. i did now some Tests with various HWMEM Values and ....

even on 68M i had after 3 Hours of usage ---> playing 2D Games, internet, whatsapp.. etc.. and then started camera again .. before after boot everything was working.. even video rec... many times treid... and then video rec didn't work.. ---> FC ..

dmesg showed me: some errors with: NO_MORE_MEMORY lol :laugh:

Now i decided to use HWMEM 74M ... and see for some days if everything goes well .... It's only +10MB RAM .. (for me: 640MB) not super much... but, better than nothing ! Thanks again for this great Hack ! :good:
[Galaxy Ace II Android Development] fluffi444:
Dont be too happy too early. I was also the opinion that everything works. And it did for some days.

But without any reason the apps FC story began... :rolleyes:

But its better to make you own experience.
[Galaxy Ace II Android Development] shaqman89:
Yeah, you should try it. :D

Now I do wonder why I never experienced the fc when I was on it. None at all. *grin*
[Galaxy Ace II Android Development] Paul L.:
I realized that this may have been posible since a long time ago, I theorized this when I enabled CONFIG_CMDLINE_EXTEND (you know, for SELinux, from this patch https://github.com/TeamCanjica/Samsung_STE_Kernel/commit/990ea488092ab55cf9d0e1ca27f7545a2ddc1d38), I didn't want to touch it because I wasn't given the blessing from cocafe (lol)

It may be useful to say: vmalloc (from the cmdline vmalloc=264M) is the reserved space for the kernel and kernel-mode stuff (as far as I know), which some megabytes may not be actually in use at any time (you may be able to take 20mbs at the very best, 3mbs at worse), because Samsung maybe was expecting to release one more OTA (and therefore reclaiming more memory from vmalloc, or use it for a newer kernel/newer kernel modules for a newer android version) before ending the support for our device(s).
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for advice. I didn't wan't to touch vmalloc before, cause I didn't know what for it's responsible or how big it should be. I looked into this, well, 264MB seem is quite many as for ~630MB memory in use.
[Galaxy Ace II Android Development] ace2nutzer:
I'Ve already tried to set vmalloc to 260mb.. And the Phone stuck at Samsung logo.

But maybe i did it wrong.

Till now no fc with hwmem 74.
[Galaxy Ace II Android Development] ChronoMonochrome:
Update

Update to this method. Today I've found a way to change size of HWMEM without recompiling kernel. By this method, however, we will edit hardcoded value directly in zImage. Probably this method can be applied even to editing ramdisk, but since there is much simplier way with swapping external files boot.cpio, I haven't tried it yet.

Okay, lets cut to the chase, first of all, everything following we'll do using any Unix-based system. Unfortunately, I haven't found yet lz4 binary for windows/cygwin, that produces same format of lz4-compressed data, that linux's one does. Referring to some technical details, we'll need to pass arguments "-l -c1" to lz4c binary later( https://github.com/ChronoMonochrome...d40#diff-06b18acd83dba8e491010a0a240901ecR140 ), which windows one doesn't have. I don't know what exactly does these parameters, you even won't see any explanation in help message by executing "lz4c -h". I have found these parameters in this commit:

https://github.com/chronomonochrome...ac7#diff-f52be68e05a33ad993242e2ffc601a11R295 .

First you need to install package liblz4-tool:

sudo apt-get install liblz4-tool

Second, you need to install python interpretator, if you haven't already:

sudo add-apt-repository ppa:fkrull/deadsnakes
sudo apt-get update
sudo apt-get install python2.7

I haven't tested command above, as I have python already installed on Mint 17.

Now download script "set_hwmem.py" from my github: https://github.com/ChronoMonochrome/utilities/commit/d0d50604123af7c4b18931d0b6281d8beccc6d40

Finally, download this kernel, that support following manipulations with HWMEM.

It has very simple usage: all you need is extract boot.img from package to the same folder where's set_hwmem.py and run command:

./set_hwmem.py boot.img 74

74 - size in MB, which we want to set. Note: kernel should have this patch https://github.com/ChronoMonochrome/Chrono_Kernel/commit/7d8299a85cb067d5baf0ddc331141b0d01230eef to support such manipulations with it. This probably should work with whatever kernel, that has patch above, however I haven't checked it. For now only lz4 compressed kernels supported.
[Galaxy Ace II Android Development] ChronoMonochrome:
Have you used CONFIG_CMDLINE_FORCE? Because it seem, vmalloc size can't be overriden, like HWMEM one. I made test builds with appended "VMALLOC=192M" and "VMALLOC=128M" to the end of cmdline. For now I can't believe, that it can be decreased so dramatically. :)
[Galaxy Ace II Android Development] ace2nutzer:
Yes. i've tried the same way like HWMEM ..

Do u mean CMDLINE_EXTENTED ?! - But very cool that it's working for u ... and now how much RAM ?? :D

EDIT: And how do u check if the new Value is applied ? - last_kmsg ? ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
Nope, I mean exactly CMDLINE_FORCED. CMDLINE_EXTENDED doesn't do any work here, as it adds parameters to the top of cmdline - it would be overridden by parameter vmalloc passed by bootloader.

This doesn't show difference in free RAM, cause (AFAIK) vmalloc is allocated dynamically. And as I said, it doesn't seem that here was any difference at all. To make sure, that your changes are applied, check /proc/cmdline. Later I'll experiment with this a bit more.
[Galaxy Ace II Android Development] ace2nutzer:
Does it mean, reducing vmalloc will not improve performance in ram ? - i mean in making more addressable userspace ram ...
[Galaxy Ace II Android Development] ChronoMonochrome:
No, it won't. However, it probably can make more free RAM for apps.
[Galaxy Ace II Android Development] ace2nutzer:
Hmm i believe it makes no sense to change vmalloc size ... i did an AntuTu Bench with Stock vmalloc=264M and one with vmalloc=128MB and there was zero difference :(

I did this:

https://github.com/ace2nutzer/Samsung_STE_Kernel/commit/edfeaab49658c1aef7476c22ddcbcd174613fb0f

and was applied correctly after checking cmdline over cat /proc/cmdline

And by using cmdline_force ... Recovery don't work.

@ HWMEM: After 2 Days of normal usage.. (phone was on, no shutdown) with HWMEM=74M camera/rec was still working .. and so far no one FC for apps .. but on second Day i opened "Gallery" and i was shocked .. :eek: No one Photo ! --- After reboot, Photos where showed again... therefore i've reverted that commit, and i've also reverted that commit for vmalloc ..

I did this just for showing u, what i did...

and now.... btw .... i became an idea for S6D User @ CWM Blackscreen ...

The idea is this:

CONFIG_CMDLINE="lcdtype=8"
# CONFIG_CMDLINE_FROM_BOOTLOADER is not set
CONFIG_CMDLINE_EXTEND=y
# CONFIG_CMDLINE_FORCE is not set

With that trick the LCD Type S6D is recognized as early possible .. and maybe the fix for blackscreen Bug on CWM.

If somebody like to test this possible Fix, just post here and i'll make a testbuild with this Parameters ...

Don't forget to post the needed kernel variant ... e.g. codina ext4 etc...

btw2: @ Chrono of course u can also build a testbuild with this idea for S6D Users + Chrono Kernel ... maybe helps :fingers-crossed:
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't think that it'll make much difference. These parameters, passed by cmdline, are already being applied as soon as possible. And moving it on top of cmdline probably only can save few milliseconds.
[Galaxy Ace II Android Development] ace2nutzer:
Hmm.. the idea is also if the bootloader is maybe the main cause of blackscreen ... .. ---> wrong programmed lcdtype or just wrong detection ;)

And an other thing is also if the kernel did some messed up (wrong detection) after the the lcdtype was correctly recognized ... u know ??

Maybe it'll help ;) Because the Blackscreen appears after the Kernel is loaded.. that means wrong detection from bootloader ... let say as WS2401 .. and then the kernel say: okay .. it's WS2401 .. and apply the WS2401 driver instead of S6D .. --------> Blackscreen !
[Galaxy Ace II Android Development] manthes:
I will try if you make a build for f2fs codina. If you make more than one builds it will be better to make for odin. If you make just one it doesn't matter
[Galaxy Ace II Android Development] Toni5830:
I saw this thread and your commit some time ago and I tried to apply the changes to my S Advance. It worked (CONFIG_HWMEM_SIZE_MB=68) but the problems I had where exactly the same you have: camera not working.

But last week surfing github for new commits I saw that in this kernel https://github.com/mkaluza/Samsung_STE_Kernel highmem was disabled and it used CONFIG_VMSPLIT_2G instead of 3G. I tried changing:

-CONFIG_VMSPLIT_3G=y
-# CONFIG_VMSPLIT_2G is not set
+# CONFIG_VMSPLIT_3G is not set
+CONFIG_VMSPLIT_2G=y

and

-CONFIG_HIGHMEM=y
+# CONFIG_HIGHMEM is not set

while using CONFIG_HWMEM_SIZE_MB=70 and....camera works without any problem!

I don't know if this was caused by changes in vmsplit or disabling highmem, but I can confirm I have no more problems with media/video component.

P.S. a short reading about highmem and vmsplit http://unix.stackexchange.com/questions/4929/what-are-high-memory-and-low-memory-on-linux
[Galaxy Ace II Android Development] ace2nutzer:
Yes.. but how long did u test ??

Let the Phone for at least 3 days on .. and then check if Gallery, Camera, icl. rec, works .. and also if u don't loose Wifi connection.. (i mean wifi is connected, but no internet access)

And re-enabling HIGHMEM isn't a good idea ... it's for more than 4GB RAM .. we've only 768MB ... :)

An it'll also reduce performance with highmem
[Galaxy Ace II Android Development] Toni5830:
I've been using my kernel for a week and in particular now my phone has been on for 2 day (48h 30m).

I forgot to mention that this kernel http://xdaforums.com/galaxy-s-advance/help/mk-kernel-stock-discussion-t3047609 has 650 free mb and nobody complained about videos/gallery etc..

I also saw you and ChronoMonochrome use the same settings in your kernel, so maybe it's related to something else.

or simply Janice rules:D:D:D:D:p
[Galaxy Ace II Android Development] Paul L.:
As I understand, the vmalloc value is a reserved area of memory (alloc means allocated, but on boot), within it, the kernel can do whatever it needs with the RAM, to actually check it, you should check the first lines of dmesg; specifically, when the kernel checks the offsets assigned as kernel space (the offset should change in this case)

(Also, we have 800-ish megabytes of RAM, depending on the RAM chip of the devices, some is reserved for hardware as we know, and the rest for the kernel, everything else is user-space)

Sent from my Moto G
[Nexus 6 Q&A, Help & Troubleshooting] boball:
A few weeks/months back I did some setting in my Nexus 6 that sets the screen unlock pattern whenever the phone boots.

i.e. when the phone boots, it asks you to enter you screen unlock pattern in order to boot.

Now I want to disable that so that I don't have to unlock my screen in order to boot. But I am not able to find that setting... I don't remember where it was. I looked under Security...Smart Lock...etc... can't find it. :( Where is that setting?

I haven't rooted or unlocked the phone. So it must be some default setting (which I am not able to find now).
[Nexus 6 Q&A, Help & Troubleshooting] Masum56k:
In security- Change Screen Lock to None or Swipe.. This'll release your problem..

Then check in pattern lock again. There is the option available, which you mentioned..
[Nexus 6 Q&A, Help & Troubleshooting] boball:
Thanks! I should have looked at that.
[Nexus 6 Q&A, Help & Troubleshooting] holeindalip:
This will be the option
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] MarcosMarquez:
Hello.

I have a big Problem after this update. I used before the Rom 1.20.162.3.

Since i updated it to the new version, i have problems with video calls.

i start the video call but i cant see the other person on the phone. he can see me and i don't hear it.

With Rom 1.20.162.3 i don't have this problem. Can someone help me please?
[Android General] nitesh7860:
Lollipop Themed Rom

Released for Lava Iris X1[IMG="Lollipop Themed Rom For Lava Iris X1"]http://s24.postimg.org/g1ctpmx39/android_lollipop.jpg[/IMG]

FEATURES

Android L Themed

New Android L Settings UI

Android L Keyboard

Material File manager

Customization in System

Lollipop egg Easter

And Many More... :laugh:

Bugs

No Bugs

Screenshot

Instructions

-Download ROM and and Replace Boot.img

-Put it in External SD

-Start CWM Recovery Mode.

-Take full backup in recovery

-Wipe data or factory reset.

-Install ROM

-Enjoy!!

Download

Link 1 :-https://drive.google.com/file/d/0B5mh3Ehmj1O6ZEw1T1k0Ti1Va1k

Link 2:- Coming Soon

Special Thanks To Aslam Kasmani,Ayush Kushwaha, XDA Team and Please Dont Forget to Hit The Thanks Button​

:good::good::good::good:

Fix For White Statusbar :- Fix

An Experimental Update:- Experimental Update

Note :- Try Experimental update.. I made some changes in framework-res.apk and systemui.apk to make it more lagless.!!
[Android General] Rifat555:
bro lava iris x1 which mtk?
[Android General] nitesh7860:
this is for lava iris x1 [Broadcom]
[Android General] javid.vaza:
Great work dude
[Android General] shub4m:
gooood job

hey thanku bro :D :p
[Android General] akhil8826:
How to extract tar file

extract 7zip file with pc or es file manager in ur phone.. if it ask u for plugin just download the 7zip plugin... then extract it and again compress in zip n flash
[Android General] nitesh7860:
you cant extract from both pc or mobile(es file explorer). :good:
[Android General] smartyimrann:
Nice ROM

hi bro ... :good::good:

nice rom but material design is not like Android L ...

and other features are ok

Thanks for the rom

we are waiting for update with material design ...

Thanks

:good::good:
[Android General] kachavarapuajay:
Update Screenshots

Screenshots are not looking Good. Soooo Tiny.
[Android General] Anil6975:
Someone plz tell me how to replace boot.img in zip file and which software to use
[Android General] dhruv1234:
Help

I don't know how to replace boot. Img please help
[Android General] nitesh7860:
Post updated.
[Android General] sunnysup:
Dude the White status bar fix does work but not completely. when u open an app it remains white sometimes unless you tap it or scroll it down. Please look into it and keep updating.. Nice ROM :)
[Android General] shub4m:
please update the white statusbar link... i need it

---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------

if u hv fix can u upload it
[Android General] Preetham stan:
I can't get the download link its showing the file removed and does not exist please send me the correct link for that lollipop themed rom plzzzzz
[Android General] AKAHsh:
provide a new link plzzz.. this link is not working
[Android General] firephoenix3:
4gb variant

Can I flash this ROM in 4gb variant..?:confused:
[Android General] Emran162:
link not working :(
[Android General] djxyon:
dead link, if not fixed soon.

Close thread!
[Android General] anonymous.namit:
please update all the links, page not existed!! snapshots seem cool, thanks fr the rom! bt plz update the links :)
[Android General] shubzz25:
Help needed

bro can u plzz help me to port a rom for lava iris x1
[Android General] Ritik169:
bug

It does not support during recorder help me I need it for live stream on YouTube please help me XDA or gave me another to. That support during recorder.thanks
[HTC EVO 3D] QA Bot:
Q&A for [UNBRICK] HTC Unbricking Project

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [UNBRICK] HTC Unbricking Project. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[HTC EVO 3D] tonyjustme:
I hate to ask, but, does this work on a Nokia Lumia 520?

I have a lot of experience running Linux-based distros, but don't know if this works for my Lumia as well.

I was trying to downgrade from an official developer preview down to the official windows phone 8.0 os when I got stuck with my phone in QHSUSB_dload mode pretty much.

Any ideas anyone?

Thanks.
[G 2014 Q&A, Help & Troubleshooting] rajj_k2:
after flashing all the custom ROMs in my XT1068 I found that the Titan Prime from Shawn is the most stable and user friendly ROM out there.

Now if there is any other ROM which you think is better than TITAN PRIME please mention it in the comments because im really looking for a stable and bug free ROM for this device.
[G 2014 Q&A, Help & Troubleshooting] moby90:
atm the best is kk stock+xposed for performance stability and personalization
[G 2014 Q&A, Help & Troubleshooting] rajj_k2:
yes i agree but there are a lot of features in lollipop which is find really useful and these are missing on kk. for example guest mode screen pinning etc