yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mega] r1l_Alex_™:
[MENTION=4775530]Mukiai[/MENTION],

Did you want you qs shade to look like that?

I noticed it doesn't span across the screen... I had that happen when I started modifying my DPI for nougat from mm..

I prefer more screen real estate. So I wanted the same UI aspect and DPI I had from mm... What's cool now is that you can adjust Absolute Width in developer settings on the fly in N as well as DPI...

Started with my preferred persistent base DPI using ADB and set it in build.prop after clean flashing Sileshs first 7.1 build..

I wanted the smallest stable DPI threw out the UI... I would adjust test and test again... I had it to the point were the qs header wouldn't span across the screen and contacts would FC.. After some more adjustment I nailed it! It was harder to do in the M builds than N..

With the DPI now set, the next step was making it 100% persistent... I noticed in LP, And M that yes you could change DPI it in settings etc. But, I would get this weird resize anomaly where you could lock and unlock the screen or exit a app etc and things would resize but on a scale that was hardly noticeable.. Kinda like going from 220 to 226 and 230 etc. This even after dynamics and some manifest changes it would happen..

Now I make the changes, DPI and UI / CustomFont System Wide, Remove and Replace certain Applications etc , and ZIP it back up! Full Wipe ,Clean Flash along with Gapps in one shot and Reboot! Done.. Everything including DPI changes are done and all I do I proceed with the setup as normal.. Done.. :good:
[Samsung Galaxy Mega] Alamtab:
I have some trouble with this Rom. crash in apps after several minutes. any solution?
[Samsung Galaxy Mega] carlos974:
Read the first page of this forum!

Specify used ROM

Thanks
[Samsung Galaxy Mega] neilphetamine:
I'm running [MENTION=4551757]Silesh.Nair[/MENTION] 's latest build CM 14.1 as my daily driver. Its working really smooth. None of my apps crash.

How do you flash it?

Haven't you tried clean flash?

Dont forget to flash 'pico gapps' from OpenGapps.

But first thing first. Don't forget to read the forum from the 1st page.
[Samsung Galaxy Mega] Alamtab:
Thanks for answer.

full wipe

wipe cache/dalvik after flashing

How mean dirty and clean flash?

I flash Aroma Gapps but my choice in aroma, some option like pixel launcher and play games and etc.
[Samsung Galaxy Mega] Mukiai:
Hi :)

I didn't search that primary. My wanted was principaly the dpi look . but if you would share your method it would be nice I could play more deep:) as I did before (on my s5830 and at the beginning of my i9205.

For now I don't have any FC or problem, and I flashed with mini open gapps (for other people if you do this don't complain, I I know the risk to do another way that devs purpose. So please test its way or don't report :) ). All is working smoothly. The only problem I with assistant (so nothing to do with this particularly or phone) that don't want to train my voice. And second happen with DPI change : during call screen shut down (as normally) but whatever I do I can't wake up it. The only way is that my correspondant finish the call. If not I have to force power off/on the phone. But it's a daily driver ROM and phone for all the rest so I use it. And I really like my klwp way to use it too so I won't change for anything else :) I just wait for more custom, and for the first time, not another ROM than cm, but xposed and kernel : I wait them:) ).

Sent from my GT-i9205 (with assistant (so I have to train my English :) )
[Samsung Galaxy Mega] neilphetamine:
[MENTION=4551757]Silesh.Nair[/MENTION] recommend picogapps from opengapps for his build. How about you try it first.

Use TWRP (by silesh) to clean/wipe/flash rom.

Mine using pixel launcher + some form pixel apps too. If you look a few back pages in this forum, i already post some screenshot.
[Samsung Galaxy Mega] carlos974:
Information on the first page :

"Also note that when you flash Gapps, refrain from flashing full or stock versions as it is found to mess with smooth functioning of the ROM, like the dialer. If you use Open Gapps, the best bet is to flash the pico version. Rest of the apps can be downloaded from the Playstore."

@+ :D
[Samsung Galaxy Mega] neilphetamine:
CM14.1 20161114 update now available guys!

Remember, if anything happens.. just clean flash!

Thank you, [MENTION=4551757]Silesh.Nair[/MENTION]
[Samsung Galaxy Mega] Mr.Obsolet:
just in case of questions *smile*

Clean flash -> wipe cache, dalvik, data and system, flash ROM and gapps

*gasp* by reading the changelog ....

"140b75e homebutton: make key configurable"

i cross my fingers! Oh yeah :)
[Samsung Galaxy Mega] r1l_Alex_™:
About to clean flash now :victory: I personally don't mind setting everything back up! I always test new things, different applications etc.. I always say, I'm going to clean flash the next build anyway so what's it gonna hurt? Lol..

Have fun guys! Thank you again Silesh!
[Samsung Galaxy Mega] Mr.Obsolet:
no luck.... setup wizard keeps crushing.

#### new clean flash with new pico gapps and...

and again no luck, setup wizard is crushing right from the start.
[Samsung Galaxy Mega] r1l_Alex_™:
Logs?

If your backed up, restore the previous build if possible and dirty flash up to 1114, reboot, let it boot and rest for a min or 2... Then restart in recovery and flash the current Open Pico's , Wipe Dalvik/Cache when prompted and let me know what happens..

I know it's not recommended but for testing try it..

Anyone else having Fcs? I had a few but everything's fine now... Past setup... It will take me a few to get screens up... Neil what about you? Everything good?
[Samsung Galaxy Mega] Mr.Obsolet:
that sounds realy dangerous, Alex
[Samsung Galaxy Mega] r1l_Alex_™:
Well then we need log data... Lol... I'm working on the build now, it's gonna be a while before I'm done..

I've done the above mentioned in the past and everything was fine..

If your uncertain that's fine.. It's not gonna hurt anything, at worse you would loop... Then you would either clean flash the previous build and dirty flash 1114 or just flash your backup..

Or

Wait till everyone else comes back up and confirm... Silesh will chime in soon.. :)
[Samsung Galaxy Mega] Mr.Obsolet:
i am already on my way to backup my system...
[Samsung Galaxy Mega] r1l_Alex_™:
Oh... You didn't backup everything before you flashed? If not then everything I said would be pointless...

Try clean flashing 1114 without the Gapps as well... Let it boot up ,re_boot into recovery and flash Gapps... I flashed Nanos on mine...
[Samsung Galaxy Mega] Silesh.Nair:
Can't be of much help without the device or logs.

You guys are not seeing the cm setup wizard right? It is the aosp setup wizard that is fc'ing?

If fresh flash doesn't work, dirty flash without gapps. Note that for dirty flash, only rom flash is required. There is a backup script in the rom file that will backup your gapps, flash the rom and restore the gapps back. Has anyone tried this?
[Samsung Galaxy Mega] r1l_Alex_™:
Mine went good... I'm setting everything back up... I had a few FCs on startup "Setup Wizard" but they cleared as they did before and I Proceeded just fine..

Im going to take my 3rd Device and clean flash it to replicate...I'll see what happens on that one...
[Samsung Galaxy Mega] Silesh.Nair:
But cm setup wizard should not be seen as I have removed it. You should see the aosp setup wizard.

This screen. http://dl-1.va.us.xda-developers.co....png?key=3geIdCmqm6sB_vhp2bMrDg&ts=1479137094
[Samsung Galaxy Mega] Mr.Obsolet:
ME! ... and it works!

i returned to the last build and than flash the new one directly.

So far so good, everything is fine!

[MENTION=7086325]Alex'sEvolution[/MENTION]

thanks... i will also try to improve my englisch for you. everytime i write with you i am thinking that i do not express myself good enough.

@
[Samsung Galaxy Mega] r1l_Alex_™:
I apologize I ment AOSP.... My FCs had to do with GSM and PlayServices causing issues with SW, not SW itself... Fixed the prior post...

Mr. Obsolete clean flashed and had FCs... Problem is I don't know if he had current NAND.. If not then it would be pointless for him to dirty flash ..He would need to CleanFlashe the previous build and Gapps.. Set everything backup and then flash up to 1114 dirty...

Seems he did and dirty flashing up has worked for him... Waiting for everyone else to show up first... Like I said it's recommended that everyone dirty flash up to 1114 for now...
[Samsung Galaxy Mega] Silesh.Nair:
That's really strange. Anyways, users know what to do to get it going. DIRTY FLASH WITH ROM ONLY. NO GAPPS.
[Samsung Galaxy Mega] Mr.Obsolet:
Sorry... it was not the CM Wizard, it was the google wizard.

but the home-button is not answering calls.
[Samsung Galaxy Mega] Silesh.Nair:
All those features are yet to be added.
[Samsung Galaxy Mega] carlos974:
No Wipe, update CM14.1 20161114 to 20161107 without GAPPS !

no problems everything works fine.

A big thank you to Silesh !!! :good:

superb ROM:D
[Samsung Galaxy Mega] r1l_Alex_™:
Flashed the 14.1 20161114 build on 2 different devices and both of them are fine... Doing good!

1. First device was "Clean Flashed" with Open Picos and like stated earlier, had a few minor FCs but none like what Mr. Obsolete experienced.. I "full" wiped the device Dalvik, System, Data, Cache, Internal Storage and Flashed away...

Device is good. :good:

2. Second device was Dirty Flashed up to 20161114 along with 1114 Picos and everything is good as well.. Didn't wipe ****, Flashed ROM, Gapps ,Wiped Dalvik/Cache Rebooted !

Everything is good as well!!! :D :eek:
[Samsung Galaxy Mega] neilphetamine:
Dirty flash from previous build + updated pico gapps and device boot up without any problem.

Do some replacement some apps that i used recently, still works perfectly.

Will continuing play with this build.

Thank you, [MENTION=4551757]Silesh.Nair[/MENTION]
[Samsung Galaxy Mega] lehuutai130:
Guys just wonder any of you experience the problem with promixity sensor for galaxy mega. Everytime I make a phone call or sb calls me. The screen just black out and I cant do anything to turn it back on during the call. So it is really annoying for me as I wish to flash the newest rom. It happens since I start flashing android 5.0 and higher. However, everything is good for stock rom. If u guys have any fix for this, plz let me know
[Samsung Galaxy Mega] Silesh.Nair:
Check if your proximity sensor is working.
[Samsung Galaxy Mega] lehuutai130:
It works fine on stock rom 4.4.2 . However it just stop functioning as I flash any rom higher than marshmallow.
[Samsung Galaxy Mega] Saiful98:
[MENTION=4551757]Silesh.Nair[/MENTION]

'2c1bab2 Enable Round App Icons'

What does it mean...?

Will you enable the rounded icon...

Just asking...:o
[Samsung Galaxy Mega] Mr.Obsolet:
it´s the first time i read that someone got same issue i have.

I remember, that my sensor problem starts with MM Roms.

But: when i do an proximitty test, the sensor failed and is always showing that something is "near". Thats why i think the is dust or something else on it, or, it´s broken. (because i already cleaned it).

Sometimes... i got normaly functionality. . . once in a month a call is ringing, the screen is still on, i can slide the buttons, put the device to my ear an back (and screen turns on/off).

The other time i use the power button to end calls, and the home button to answer them (which is actually not enabled in CM14.1-1114).

but...i am not alone :)
[Samsung Galaxy Mega] Silesh.Nair:
That's for my g4 build. I'll add it for the mega in the next build. All google apps will have round icons.
[Samsung Galaxy Mega] lehuutai130:
Yeah thats so weird. It just start with android 5.0, 6.0 and now 7.0. With kitkat stock rom it works perfectly fine. It seems like an internal conflict between mega hardware and the lollipop rom
[Samsung Galaxy Mega] neilphetamine:
Do you mean this? Just works fine here.

By waving my hand, device screen off and on back.
[Samsung Galaxy Mega] lehuutai130:
Nope not that. Even I wave my hand or press the power button, the screen still black out. The call is still going on but no wag to turn on screem during call. It just got back to normal when the call is ended
[Samsung Galaxy Mega] wire103:
Lots of FC upon setup here too, just let it lie on the table half an hour and it seemed to clear up. Pico OpenGapps.
[Samsung Galaxy Mega] r1l_Alex_™:
:good:

That's what I had explained back a few pages. :rolleyes:

On a clean flash on initial startup you will see some fc's realated to google. Etc.. On setupwizard..

If you let it sit for 5 to 10 mins after the initial start, they WILL clear.. Log data showed that PlayServices and Phonsky ie PlayStore etc, basically were awaiting Permissions for sync and WIFI/Data to be set, and Backup Sync to start..Simply...

On my devices clean flashed, I make a lot of changes to the build before I flash. One of those had to with "preferred network" on startup via build.prop

By default now :confused:

ro.telephony.default_network=3

Needs to be this :highfive:

ro.telephony.default_network=9

On the last clean flash I tested last night for 20161114 I also flashed 1114 Pico's with it...I didn't get any errors, fc's etc on initial start...None!!

But until I confirm this "if" You Clean Flash .. Let the damn thing sit for a few mins and walk the hell away from it don't touch Anything... When you come back start your setup , clear the FCs and it will run threw!!! :D
[Samsung Galaxy Mega] Mr.Obsolet:
Is there any information i can provide for that proximitty issue that might help and maybe solve the problem for me and my other buddy. .

Otherwise i am still able to wait till i can handle calls with power/home-button...
[Samsung Galaxy Mega] neilphetamine:
Have you try this app? Hope this can help you to fix it

https://play.google.com/store/apps/details?id=com.vrognaas.proximityfix
[Samsung Galaxy Mega] Maxikinq:
Thx everybody for your quick response and a lot of help :) Now the newest version works perfectly after I clean flashed it. Thx for the great ROM :good:
[Samsung Galaxy Mega] Mr. Obsolet:
Neilphetamine,

Let s have a try

Gesendet von meinem GT-I9205 mit Tapatalk
[Samsung Galaxy Mega] masterkey101:
Android wear not working. Anything I can do?

Thank you!!
[Samsung Galaxy Mega] lehuutai130:
Let me know the result Mr Obsolete. So tempting to get out this old kitkat for android N
[Samsung Galaxy Mega] Mukiai:
Here, update 14-11 on previous without wiping before or after, without flash gapps' update, and....... All is smooth no problem at all. Thank you again and once more
[Samsung Galaxy Mega] lehuutai130:
Just test it with the lastest build and the problems still on. Have to go back to 4.4.2 stock rom

Not sure any guys got the problem when flashing, my screen always start with initial error. Then I have to wait a bit then press the home button to set up google.
[Samsung Galaxy Mega] Silesh.Nair:
https://code.google.com/p/android/i... Priority Owner Summary Stars Reporter Opened
[Samsung Galaxy Mega] masterkey101:
Thank you, Silesh! Changed ro.build.type from userdebug to user and wear works again!

Perfect support!! :)

Regards, Martin
[Samsung Galaxy Mega] aaronguest:
Just got Google Assistant to work on this CM14 build. Works great!

[IMG="Assistant"]https://s12.postimg.org/jnwjcckr1/Screenshot_20161116_152056.png[/IMG]
[Samsung Galaxy Mega] Gibbon_999:
Make sure your hardware is working 100% as well:

http://xdaforums.com/showpost.php?p=69470868&postcount=450
[Samsung Galaxy Mega] varsay:
The setup wizard is constantly stalling what you need to do.
[Samsung Galaxy Mega] Mr.Obsolet:
There were some positive results yesterday, but i can not reproduce them today.

So that App-Patch is not working.
[Samsung Galaxy Mega] Silesh.Nair:
This question has been answered 10 times in the last couple of pages. Read and find out.
[Samsung Galaxy Mega] varsay:
I solved this problem by trying the pico releases ve

step by step

Wipe data factory reset

Wipe cache

Wipe dalvik cache

Reboot system now

Thank you for your help and study
[Samsung Galaxy Mega] Mr.Obsolet:
[MENTION=4150506]Gibbon_999[/MENTION]

Dammed!

...squeezing solves the problem. .. thanks... now i got a idea how to solve it.

*issue closed*(for me)
[Samsung Galaxy Mega] lehuutai130:
Can you be more specific about the solution of the problem ? What does it mean by squeezing it ? Thanks
[Samsung Galaxy Mega] Mr.Obsolet:
by squeezing the device on the top (where the sensor is located) the functionallity is given. Screen turns on/off. The sitting is loose, so i am thinking about a solution for that.
[Samsung Galaxy Mega] lehuutai130:
Oh I see. I tried that method couple of times. It works for first time but now it is useless now.
[Samsung Galaxy Mega] varsay:
I've had the same problem and have solved it the following way

settings

notifications

phone

Shift importance level to the right and do not disturb disable :good:
[Samsung Galaxy Mega] jordan_tyson:
the the new built (14-11) have theme engine :confused:
[Samsung Galaxy Mega] varsay:
when the application is overloaded

Not enough storage space

What could be the problem?
[Samsung Galaxy Mega] jajaxor:
Hi, (sorry for my bas english..)

I'm testing since yesterday. all works fine. big thanks ;)
[Samsung Galaxy Mega] neilphetamine:
What could be the problem? Already answered by yourself. "Application overloaded"

Just install the application that you used.

I'm running custom rom for the looooong time, never had "not enough storage space" thingy
[Samsung Galaxy Mega] Mukiai:
Happened to me . it depends on how many apps you use. And for that the sd storage have to be as internal. And if you update your ROM (just update, no wipe, no clean, just update), using your SD as internal, you'll see you storage (in setting section) in negative way. And for that, some app could detect a less storage than reality. My SD in screenshot is 32gb not 7,*GB . the last is real internal storage.. for me it's not a problem as I know that. But a young "ROM customer" can be a little lost with that for example. ;):silly:
[Samsung Galaxy Mega] r1l_Alex_™:
[MENTION=6608674]silesh[/MENTION] :good: update on the 1024 Project ;)

True Chainfires Newer Systemless v278_SR4 Running

Attempted to merge Masquerade... Ehh..

Running Legacy for now...

Lightly Spiced with a KA Tune!!

Running awesome.. ! Fast as ****!!!

Oh sorry.. Lol Cm14.1 20161114 Running good here as well both clean and dirty!!
[Samsung Galaxy Mega] VimanAdrian:
Do you know how to fix the negative storage thing? I have the same problem and i can't install hearthstone on my sd-card because of it.
[Samsung Galaxy Mega] Mukiai:
Well, mmmh for me I don't have problem for moment, even with the place even with number of apps download. But the best way for you is to clean flash. I know what I do and what I risk when I update. But the best way to use custom ROM, at any stage, is to listen dev's instruction. And he said to clean flash to be sure. So... :)

Have you tried to check external at the bottom of the list in developer settings ?
[Samsung Galaxy Mega] r1l_Alex_™:
Just wanted to share this with you guys... I apologize in advance for the semi OT...

I've been getting messages questioning about my Screen Size/Density... So I figured I let everyone know here...

If you decide to change it, I'm letting you know now, if you make a mistake or don't know what your doing and mess something up I'm NOT going to be responsible for it... Also the adjustment takes into account the Kernel Tuning as it's stock for now. :fingers-crossed:

I make the changes of this nature via ADB/Fastboot on either a LinBox and a WinBox it just depenends on where I'm at.. If you need information on how to setup for ADB/Fastboot as well as commands on both platforms, and size calculations research it.. Google is you friend...

ADB can also show you the wm used ranges on the current setting as well a scale etc... I'll edit the post later for the view commands...

Physical Size on 9200/9205s 720x1280 (160mm)

6.3" PPI 233/Density 240 Default at 30fps

I didn't like the Size/Scale "Density" long ago so decided to change it for good.. During the experimentation I worked on 2 Size Overrides and Several Densitys before my preferred "stable" ratio was set.. Stable meaning No fc's, Random Reboots, Performance Hits,or Overscan issues etc.. Also this LOCKs ranges on N builds so that all applications are forced to use the setting and not a RANGE. You'll notice that if you were to do this In display settings, developers options "width" and or Build.prop you will get size anomalies..

People Requested In windows the command changes c:\ .. I prefer a Linbox but, Ehh..

Prepare.. Plug Device, USB Debuging checked, Console up. check device connection ..

adb devices

1.Clean Slate.

adb shell wm size reset

adb shell wm density reset

adb reboot

2.Size Override was set via ADB settings "experimental" my prefered.. Without modifying vsync

adb shell wm size 1080x1920

adb shell wm density 295

adb reboot

Test...

Note:

This setting was used on Sileshs OC kernels in the MM builds because this allowed tuning for the performance hit the device would take on that resolution... Simply, This setting would NOT be optimal for a stock N build.. OC Kernels yes, when that day comes..

Advanced settings to lock Screen Size Range as well will not be discussed here.. It's a bit more complicated and I don't want anyone messing something up doing it..

This is "my preferred".. Absolutely "Optimal" setting on [MENTION=6608674]silesh[/MENTION]s N builds as no OC Kernels are available yet.. This is the smallest you can go without adverse side affects... Seems to lock Range as well. Verified Under: sys/class/graphics/fb0/virtual_size

adb shell wm size 720x1280

adb shell wm density 198

adb reboot

Test... Enjoy :good:

If you don't like it you can set it back using the commands listed under clean slate.. I hope this helps you guys that requested it via PM.. :highfive: Thank You!
[Samsung Galaxy Mega] Silesh.Nair:
Miui ROM lovers. Miui 8 is out.

http://miuirom.xiaomi.com/rom/u941039572/6.11.18/miui_mega_baby_6.11.18_9194c5b045_6.0.zip

All credits to [MENTION=6967309]Aabyebaby[/MENTION].
[Samsung Galaxy Mega] PapkaOtec:
Thank you very much
[Samsung Galaxy Mega] KarlosLosMentos:
Can you give here link on miui 8 rom and not only for download, i want to know whats working and what not yknow [emoji57]
[Samsung Galaxy Mega] Mukiai:
I think that "i'd like to know" is a better way than "I want to know". In respect of devs' hard work but also in life . :) little out of thread but .... :) and link for download is yet give
[Samsung Galaxy Mega] KarlosLosMentos:
It give me error

And i'd like to see ROM info page if exist :( i try it once again and tell :(
[Samsung Galaxy Mega] neilphetamine:
Will gonna give a try this rom as soon i got my 2nd mega arrived. But one question, [MENTION=4551757]Silesh.Nair[/MENTION] . Do have to flash kernel or flash with old build twrp like previous miui rom? Its mention by [MENTION=6967309]Aabyebaby[/MENTION] in his simple instructions on xda thread too.
[Samsung Galaxy Mega] Silesh.Nair:
I got no clue. Follow his instructions.
[Samsung Galaxy Mega] neilphetamine:
Running CM-14 as my daily use.

Can say its stable.

No ghost touch and heating detected untill today.

Others not working is known issues as state in OP.

Really impressed the battery life
[Samsung Galaxy Mega] Saiful98:
Yeah...quite impressed with the battery life too

Something with doze on the go i guess

Cant thank enough to silesh n arco
[Samsung Galaxy Mega] jajaxor:
Hi !!

I don't want test for this moment sorry. it's finish for me the betatest (Linux) test...

thanks for this rom ;)

all works ? Camera (switch photo/vidéo with google application or opencamera ?), sound ? network ? sdcard ? etc...
[Samsung Galaxy Mega] Mr. Obsolet:
[MENTION=7453180]jajaxor[/MENTION],

Rtfm ;)

Gesendet von meinem GT-I9205 mit Tapatalk
[Samsung Galaxy Mega] Silesh.Nair:
Issues are mentioned in the OP.
[Samsung Galaxy Mega] Silesh.Nair:
Build 4

Download from here. AFH is down, so uploaded to google drive.

md5sum : 574bb70e0e2d0d60b57b4387dae36fe8

Changelog : https://github.com/sileshn/changelog/blob/master/cm14/14.0-20160914.txt
[Samsung Galaxy Mega] neilphetamine:
Dirty flash, [MENTION=4551757]Silesh.Nair[/MENTION] ?