Develop Bugs

Going back to Stock ROM - Done!

I am sure this topic has been beaten to death already but I still wanted to share my experience with custom ROMs and finally going back to the STOCK ROM. If beginners want to try out Custom ROMs, may be they can read this beginner's post.
First the ritual - Android community is great. ROM developers are great minds at work! Thanks for doing all the hard work and showing me whats in the Custom ROM world.
I started out with simple rooting of my phone to get tethering (cheap on my part but I think I pay more than what my carrier offers). After rooting, custom ROM was just so tempting. So I tried a few - CM, AOKP, Carbon. Honestly, out of all, CM10.0 was the most stable for me. Things I loved:
1. Battery Life - Can't say enough. There is so much junk that runs in background on STOCK ROMs.
2. 4.2.2 JB - Better than 4.1.2 but then, not by miles.
3. Ability to flash ROMs over the weekends You know it.
4. Utilities like Titanium backup and others that needed Root access.
5. Tether - super like.
Things I hated:
1. Force closures - OMG I couldn't understand how the STOCK ROMs are so robust or Is it that the Apps are tested on Stock ROMs very well that they don't crash. Countless failures for Instagram, Email, Camera, BT etc.
2. Camera functionality - I give 10 out of 10 to Samsung in creating great camera app. I am a heavy smartphone camera user. The 4.2.2 camera app was so laggy on my GS3. The user interface sucked (circle). No meter mode. Bad panorama mode, HDR mode and worst low light photos.
3. On one of the custom ROMs, I had horrible issues with making and receiving phone calls (Yes it can go that bad).
4. Bluetooth pairing with devices. BT crashed a lot while music was interrupted with incoming calls.
All in all, I am now happy that I am back to the STOCK ROM with This Link Many thanks to the Member.
There is a lot of excitement and good things about the Custom ROMs but if you are like me who is not a super power user, there is a lot to consider before jumping.
Happy Monday!

In CM 10.1, the FC issues were fixed for me. This applies for most current AOSP roms. I have not had any issues with camera lag either. I will admit that the stock camera is more robust with options but there are third party apps that help minimize the feeling of loss.
Regarding testing, this is what goes on here. The difference is you see the testing phases while you do not with the manufacturer. In addition, many of the drivers and hardware info is proprietary so developing drivers that are stable can be a hit and miss affair.
On the same note, not every phone and user is the same and the experience will be different for each. ROMs will possibly work differently across the same models of phone due to minor variations in quality which are nearly impossible to catch during the manufacturing process due to nearly microscopic differences.
Sent from my SAMSUNG-SGH-I747

aybarrap1 said:
In CM 10.1, the FC issues were fixed for me. This applies for most current AOSP roms. I have not had any issues with camera lag either. I will admit that the stock camera is more robust with options but there are third party apps that help minimize the feeling of loss.
Regarding testing, this is what goes on here. The difference is you see the testing phases while you do not with the manufacturer. In addition, many of the drivers and hardware info is proprietary so developing drivers that are stable can be a hit and miss affair.
On the same note, not every phone and user is the same and the experience will be different for each. ROMs will possibly work differently across the same models of phone due to minor variations in quality which are nearly impossible to catch during the manufacturing process due to nearly microscopic differences.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Totally agree with the slight variations in experiences with Custom ROMs. But for some reason, my jump to 10.1 was not smooth with FCs and I quickly made a u-turn to 10.0 and then ultimately to the STOCK ROM. Camera Apps like Camera Zoom are very good and they do provide more options like Metering and time lapse (missing in STOCK), they are still not complete (simple example - I can't enable Panorama from CamerZoom). Nevertheless, the experience can be really amazing when things work out but really frustrating when they don't. STOCK has its problems like I am missing my Solid Battery life today :crying:

I think I'm about to go back to stock as well. While I love all the extra features that custom roms offer, all the tinkering and occasional bugginess can take away from the overall experience. At least for me, anyways.
I also had been doing it long enough that I felt really comfortable with all the flashing that I was doing, but would still make the occasional mistake (look at the hilarity I posted in the stupid questions thread today). I'm thinking I'll play it safe, at least for now, before I do something I regret.
Sent from my SGH-I747M using xda app-developers app

newmind02 said:
I think I'm about to go back to stock as well. While I love all the extra features that custom roms offer, all the tinkering and occasional bugginess can take away from the overall experience. At least for me, anyways.
I also had been doing it long enough that I felt really comfortable with all the flashing that I was doing, but would still make the occasional mistake (look at the hilarity I posted in the stupid questions thread today). I'm thinking I'll play it safe, at least for now, before I do something I regret.
Click to expand...
Click to collapse
It is in my opinion that even the stock roms have bugs. At seemingly random times, my alarm clocks on my AT&T S3 just didn't work when running stock. I was almost late for work 3 days in a row because of it (my alarm is set to repeat 5 times a week every week at the exact same time. I never turn it off). In addition, I get the occasional random battery drop that seems to have something to do with the switch between H+ and LTE when on a phone call.
I stuck with the stock rom for a while but now that AOSP roms are stable, I have switched. Whatever bugs are present do not affect me or they are so minor I work around it. It really comes down to what you find to be acceptable for you.
As far as being comfortable and making mistakes, I have done it as well. Being a flashing fiend has made me overconfident a few times and I botched several installs. Luckily I have been so busy of late, that my flashing desire has been on hold.

Never had any force closes.
Never had any lag
Never had any problems on custom Roms.
If you're experiencing and lag, force closes, you're MORE than likely doing something wrong on your end.
This phone doesn't lag. It should lag whatsoever. 1.5Ghz and 2Gs of ram does not create lag.
Touchwiz runs a LOT more stuff in the background.
Just follow instructions on how to flash, what to flash, and what to tweak. And I can guarantee you an awesome experience.
The camera as well. Just took some amazing lightning shots with 4.2.2 camera, on burst mode with 20 pictures taken in less then 3 seconds. No lag what's so ever.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

jayRokk said:
Never had any force closes.
Never had any lag
Never had any problems on custom Roms.
If you're experiencing and lag, force closes, you're MORE than likely doing something wrong on your end.
This phone doesn't lag. It should lag whatsoever. 1.5Ghz and 2Gs of ram does not create lag.
Touchwiz runs a LOT more stuff in the background.
Just follow instructions on how to flash, what to flash, and what to tweak. And I can guarantee you an awesome experience.
The camera as well. Just took some amazing lightning shots with 4.2.2 camera, on burst mode with 20 pictures taken in less then 3 seconds. No lag what's so ever.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I concur
Sent from my SAMSUNG-SGH-I747

techmine said:
I am sure this topic has been beaten to death already but I still wanted to share my experience with custom ROMs and finally going back to the STOCK ROM. If beginners want to try out Custom ROMs, may be they can read this beginner's post.
First the ritual - Android community is great. ROM developers are great minds at work! Thanks for doing all the hard work and showing me whats in the Custom ROM world.
I started out with simple rooting of my phone to get tethering (cheap on my part but I think I pay more than what my carrier offers). After rooting, custom ROM was just so tempting. So I tried a few - CM, AOKP, Carbon. Honestly, out of all, CM10.0 was the most stable for me. Things I loved:
1. Battery Life - Can't say enough. There is so much junk that runs in background on STOCK ROMs.
2. 4.2.2 JB - Better than 4.1.2 but then, not by miles.
3. Ability to flash ROMs over the weekends You know it.
4. Utilities like Titanium backup and others that needed Root access.
5. Tether - super like.
Things I hated:
1. Force closures - OMG I couldn't understand how the STOCK ROMs are so robust or Is it that the Apps are tested on Stock ROMs very well that they don't crash. Countless failures for Instagram, Email, Camera, BT etc.
2. Camera functionality - I give 10 out of 10 to Samsung in creating great camera app. I am a heavy smartphone camera user. The 4.2.2 camera app was so laggy on my GS3. The user interface sucked (circle). No meter mode. Bad panorama mode, HDR mode and worst low light photos.
3. On one of the custom ROMs, I had horrible issues with making and receiving phone calls (Yes it can go that bad).
4. Bluetooth pairing with devices. BT crashed a lot while music was interrupted with incoming calls.
All in all, I am now happy that I am back to the STOCK ROM with This Link Many thanks to the Member.
There is a lot of excitement and good things about the Custom ROMs but if you are like me who is not a super power user, there is a lot to consider before jumping.
Happy Monday!
Click to expand...
Click to collapse
I tend to go back and forth between CM10.1 and Stock.
The biggest thing CM misses for me is the camera. Call me a fanboy but I really like what Samsung did to their camera optimizations in TW.
That being said, I don't like TW very much but a custom launcher and a few minor tweaks can make TW tolerable.
For apps running in the background I highly recommend Greenify for keeping apps dormant when you're not using them.
Titanium Backup also has a feature called Freeze that basically does the same thing as Greenify except it takes the app and prevents it from being used at all.
This is good for apps that you never use that come preloaded on the GS3 (AT&T and Samsung bloatware).

stable aosp rom?

hi all.
tried a few aosp roms. all great. just some annoying random reboots. im not a heavy customizer. i just like the feel of vanilla android. and also i like smaller dpi settings. currently running ptmr3's jedi rom. excellent rom, havent experienced any reboots. though its a nice rom, i like aosp roms. any out there without random reboots?
also with the kitkat update our note3 is getting, will future roms be more random reboots less or none at all? im suppose to meet someone this coming wednesday to trade my note3 for his nexus5. or should i wait til new roms are cooked up based on the kitkat update for better aosp roms?
also trying to figure out how to remove this damn widget on lockscreen. cant seem to get rid of it.
thanks all

simpl3lang said:
hi all.
tried a few aosp roms. all great. just some annoying random reboots. im not a heavy customizer. i just like the feel of vanilla android. and also i like smaller dpi settings. currently running ptmr3's jedi rom. excellent rom, havent experienced any reboots. though its a nice rom, i like aosp roms. any out there without random reboots?
also with the kitkat update our note3 is getting, will future roms be more random reboots less or none at all? im suppose to meet someone this coming wednesday to trade my note3 for his nexus5. or should i wait til new roms are cooked up based on the kitkat update for better aosp roms?
also trying to figure out how to remove this damn widget on lockscreen. cant seem to get rid of it.
thanks all
Click to expand...
Click to collapse
I've been on the unified Note3 CM11 builds and have been enjoying them quite a bit. The only reboots (and lockups) I got were from tweaking my CPU settings...apparently the only parameter that was pissing my phone off was the conservative governor. Also clk_min won't stay at the floor...but aside from slightly compromised battery life CM11 has been near perfect. I'll take the very slight battery life reduction for AOSP...also, the ART runtime is wayyyyyy better than Dalvik. Worth it for that alone. I just enabled that "for good" today but I already expect enough battery life savings to make up the difference (which was admittedly small).
Performance is top notch (even when underclocked to 960mHz), the ART runtime seems to make scrolling, chrome, maps and all around navigation snappy as hell...and I don't have to deal with TWiz. To each their own, touchwiz ain't for me. All the important stuff appears to work (LTE, WiFi, Bluetooth, camera, 1080p video recording...I can't even remember the things I used to worry about...everything works fine, even the 'settings bug' is resolved now...)
YMMV, of course.

daneurysm said:
I've been on the unified Note3 CM11 builds and have been enjoying them quite a bit. The only reboots (and lockups) I got were from tweaking my CPU settings...apparently the only parameter that was pissing my phone off was the conservative governor. Also clk_min won't stay at the floor...but aside from slightly compromised battery life CM11 has been near perfect. I'll take the very slight battery life reduction for AOSP...also, the ART runtime is wayyyyyy better than Dalvik. Worth it for that alone. I just enabled that "for good" today but I already expect enough battery life savings to make up the difference (which was admittedly small).
Performance is top notch (even when underclocked to 960mHz), the ART runtime seems to make scrolling, chrome, maps and all around navigation snappy as hell...and I don't have to deal with TWiz. To each their own, touchwiz ain't for me. All the important stuff appears to work (LTE, WiFi, Bluetooth, camera, 1080p video recording...I can't even remember the things I used to worry about...everything works fine, even the 'settings bug' is resolved now...)
YMMV, of course.
Click to expand...
Click to collapse
Thanks. I will try it out after i play around with gummy. Yah im not a fan of touchwiz either. How do i enable ART? i have never tinkered with that. Also regarding cpu tweaking. I dont really bother with that and i still get reboots and lock ups. Most times i just leave the kernel that came with the rom alone and not change it.

im a flashoholic. & i truley hate touchwiz roms. but ive been a week on AOSB v1.30 (longest ive ever stayed on one rom lol) its smooth & zippy, it has some amazing battery life. also vanir isnt a bad rom.
also switching runtimes is available in developer options under "apps"

r333xxh4v0k said:
im a flashoholic. & i truley hate touchwiz roms. but ive been a week on AOSB v1.30 (longest ive ever stayed on one rom lol) its smooth & zippy, it has some amazing battery life. also vanir isnt a bad rom.
also switching runtimes is available in developer options under "apps"
Click to expand...
Click to collapse
thanks. i only had my tmo note3 for about two weeks now. the AOSB v1.30 is not on the TMOBILE NOTE 3 development threads (i did find it). are we allowed to use those roms for our tmo note3? is there anything special i need to do to install roms from there?

simpl3lang said:
thanks. i only had my tmo note3 for about two weeks now. the AOSB v1.30 is not on the TMOBILE NOTE 3 development threads (i did find it). are we allowed to use those roms for our tmo note3? is there anything special i need to do to install roms from there?
Click to expand...
Click to collapse
The AOSB rom is a universal. Just flash rom + gApps & you're set to go!
Sent from my SM-N900T using Tapatalk

WOW. i think i just found me a stable rom to use. installed and been running this rom for more than an hour now with all my usual tweaks and apps installed. and so far no reboots. usually on other aosp rom, i would have had a few reboots already. this is awesooooome. well besides the fact that app settings (xposed) doesnt seem to work since temasek integrated his own lcd density changer on the settings menu. also he just announced yesterday that he is putting his development on hold (temporarily, hopefully). damn!
temasek's UNOFFICIAL CM11 BUILD
so far loving it. will update if any issues occur
peace

simpl3lang said:
WOW. i think i just found me a stable rom to use. installed and been running this rom for more than an hour now with all my usual tweaks and apps installed. and so far no reboots. usually on other aosp rom, i would have had a few reboots already. this is awesooooome. well besides the fact that app settings (xposed) doesnt seem to work since temasek integrated his own lcd density changer on the settings menu. also he just announced yesterday that he is putting his development on hold (temporarily, hopefully). damn!
temasek's UNOFFICIAL CM11 BUILD
so far loving it. will update if any issues occur
peace
Click to expand...
Click to collapse
temesek is very nice work, glad to hear you found a rom!

any completely stable finished roms available?

hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3

lasuazo said:
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
Click to expand...
Click to collapse
ok thanks lasuazo ;--)

I guess omni and cm11
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice

thefusor said:
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
Click to expand...
Click to collapse
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.

Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!

I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.

Makshow said:
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
Click to expand...
Click to collapse
like i said in my first post, i do really appriciate the fact that people spend Alot of time cooking theese roms, and it easy for me to come along and moan about them, but i have found over the years that after using a custom rom for a couple of weeks or so, its like the ram seems to gradually get eaten away, the device gradually slows down, becomes laggy and ultimately unuseable (not just this fone, and not just me that says this). im not saying all are like this, just many i have used, mainly because they never get finished.
i am very open though to people suggesting that i am doing something wrong, and maybe you have picked up on that something.. you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
also thank you for the erase data tip for trebucket, i will try that.. i have not used the google now launcher yet, but i tried using miui launcher but when i went back to trebucket the lockscreen stayed as the miui lockscreen, which has happened on past cm roms, so i just deleted it.
just gets a bit frustrating when you spend hours getting everything working/setting up personalisation, then the phone just seems to start getting worse day by day, but maybe like you say, its cos i "dirty flashed"?

linuxguy42 said:
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Click to expand...
Click to collapse
i did think that, and im sure you are right, but i have had every app/folder/widget dissappear twice now, then, randomly over several restarts, some widgets/apps will replace themselves over the top of the new ones i have just newly placed there.. strange, but i have came across this before on cm roms, so im sure there is a bug there somewhere, even if it is not too common..

jmpcrx said:
you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
Click to expand...
Click to collapse
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
the device gradually slows down, becomes laggy and ultimately unuseable
Click to expand...
Click to collapse
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!

Welll here are some tip which have helped me
jmpcrx said:
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Click to expand...
Click to collapse
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .

Makshow said:
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Click to expand...
Click to collapse
ok thanks, i cleared the data in trebucket, and started again with placing apps/widgets on home screen, and i also have deleted the hacked version of adobe flash that you install with dolphin browser, and, supprisingly after a couple of days of testing, my apps/widgets are not deleting themselves, the phone is significantly less laggy, and i have had no switch offs, so, im very pleased with that! so id suggest against downloading that version of flash player with this rom..
thefusor said:
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Click to expand...
Click to collapse
some good tips there, thankyou, i havent tried any of them yet, but i will have a go at some of them and see what happens.. thanks thfusor..

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.

etherfish said:
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
Click to expand...
Click to collapse
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice

jmpcrx said:
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
Click to expand...
Click to collapse
Well, you learn by doing, I believe. Also, I have a classy - for a flip phone - Motorola Razr2 v8 kicking around I can always put my SIM into if I've managed to hose my captivate glide. Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions. So, a number of things have piqued my curiosity.
So, first of all, this surprised me in the logs:
Code:
I/Launcher( 2263): onCreate(): product model family:U1 product model : GT-I9221
I'd always wondered why I had an SGH-I927 when other phones, like the remarkably similar Galaxy R, are GT-I9103. Is/was GT-I9221 an internal reference?
Also, there are other inconsistencies, for example:
Code:
D/RILJ ( 426): [1718]> REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ ( 426): [1718]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
If you jump into the debug/field test menu system, (dial *#*#197328640#*#* ) you can bring up the list of neighboring cells in both GSM and WCDMA modes... So, why is the request marked not supported? Furthermore, why didn't samsung disable the request in the first place if they went to the trouble of disabling it from working. I imagine this has a reason, but I doubt it's a terribly great one.
And the FM receiver? I do believe our broadcom BCM4329 is a bluetooth+wifi_in_an_sdcard (well, SDIO really, but still, not pci-e and not usb.) and has an FM receiver built in, but it's omitted and hidden?
Code:
W/AudioPolicyManager( 112): FM radio recording off
Oh, the conspiracy theories. And then there's the weird lines you discover if you dump the string identifiers from /system/bin/drexe!
For example, these lines are all sequential:
Code:
broadcast -a android.provider.Telephony.SECRET_CODE android_secret_code://767*3855
InvokeOemRequestHookRaw broadcast factorst OK
InvokeOemRequestHookRaw factorst fail %d
/system/.configure.txt
(what's with /system/.configure.txt???)
Do not type 767*3855 into your phone. It's the factory wipe code or possibly part of it. I do believe drexe is the DataRouter you often see spamming the logs with:
Code:
E/DataRouter( 107): usb connection is true
E/DataRouter( 107): DSR is ON. Don't send DTR ON.
And we find these strings in drexe:
Code:
__initialize_usb_ipc
/data/.usb_stream
usb connection is true
InvokeOemRequestHookRaw usbstatus true is success
oh, and:
Code:
pipe failed (%s)
fork failed (%s)
child pid = %d.
execute sh.
system/bin/sh
execl fail %d
What do you think? Why does drexe seem to have code to support and start a shell? Well, if nothing else, thank you for reading.
P.S. I don't suspect anything the least bit conspiracy like, malicious, or devious. I've worked for some huge companies; i don't think it'd be likely.

etherfish said:
Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions.
Click to expand...
Click to collapse
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...

Makshow said:
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Click to expand...
Click to collapse
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
Other than those couple of things its been great!
im HOPING down the road for an un-buggy or at least minimally buggy version of 4.4. well see what happens with that i guess.

Some help
Pawprints1986 said:
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
.
Click to expand...
Click to collapse
well i always say stock is best cause it IS optimized however there are things like keep and total Google integration that i like so i updated to kit kat
for screen caps if they dont work i could maybe suggest an application called super manager its pretty loaded it has screen cap and may even give you prox sense wake up for device.
also customizing the drawer hmm.. i guess you could try xposed framework but please be careful and make a backup before
as for who texts you and the content of the text you could try dash clock its able to do a lot

hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock. I completely removed all the system bloat with link2sd, uninstalled all att crap. Can anyone recommend me something since I feel the ram consuption still to high... battery so far is doing kind of good almost as in crdroid
But i believe it can be improved. Any recommended settings or something else i can do? Already tried lite kernel but it gave me some issues. Rather keep stock. Any recommendations please guys. Also if you know a "ok google" like app or something as a swifty assistant would be nice. Please recommend. Thanks in advance

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
Hi,
well that depends.. on what you mean with "finished"
I have tested all (3 months ago) available ROMs for the Glide. IMO the best available ROM is PACman but as said it depends. I used pac_i927-milestone.1.RC1.4.zip for a long time (months) without having any issues besides Bluetooth Headset which is a general problem in JB and higher version). I have tried other PACMan ROM versions as well but the above one was the best of stability and battery life (in my case).
So it depends what features you really need or are a must-have for you. If you do not have bluetooth headsets I would recommend the above otherwise .. well I would recommend sediROM
Regards
xdajog
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
lasuazo said:
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock.
Click to expand...
Click to collapse
Haven't done that before but would be rooted ICS stock also ok for you?
If so:
--> search for thread ID 1994902 or search for: [ROM] Stock UCLJ3 Rooted, Deodexed, Zipaligned
(sorry not allowed to post links..)
Regards
xdajog

Hype, Forget, Stay...

...when it should be something like Hype, Compare, Choose.
I'm just posting this because it's crazy how we become kind of addicts to the cutting edge versions of Android, no matter how it really works on our device, it is just awesome because it works, on our beloved 3 years old nexus.
I'm the kind of guy who really search for smoothness, all around the system. I just can't stand a frame drop. It's kind of creepy. No, seriously, I look for details, and there's some things in KitKat I don't like. But all that said, and as I once read, if your eyes see at 15 fps it's not my fault lol. So, here they are:
- Notifications panel / Quick settings animation. Yes, guess what, the frame drop here is aweful. It stutters like hell. Just do it, expand the status bar and hit the tile many times, that's not smooth at all.
- RAM usage. They can say KK is optimized and bla bla, but real thing is that there's less free RAM than JB. It's a fact. You can go all the way of how Android manage memory and stuff, well, I rather more free RAM.
- Home button responsiveness. It just lags. Test it, open an app, something heavy e.g. Facebook app, and press home button. Now do the same but use back button. Give it a few tries if you didn't notice the difference at the first time.
- High battery drain.
There are some other things but you get the point. I felt less responsiveness in general, when multitasking, etc. So I decided to go back to Android 4.3.1 JB, CM 10.2.1 in my particular case. Oh yes, this feels awesome. Notifications panel / Quick settings animation is fully smooth, I've more free ram, Home button reaction is fast again, multitasking is great. I also realized that I missed the Vanilla ui. This is definitely where I'm staying.
So my conclusion is, you can follow the hype but don't stay just with the new things, make your own judgement, compare and choose what's your most suitable rom/android version out there
NOTES:
- I've been watching a lot of YouTube videos looking for this issues I've mentioned, so I discard problems with my Maguro in particular.
- I'm comparing both Android versions with the same apps (around 140 total apps), so there's no factory reset placebo effect.
- They're all present on different roms i.e CM, PA, and some others, so its KK related I guess.
- A particular thing about CM 10.2.1 is that it cames with a modified phase beam live wallpaper that slows down the launcher/system, don't get wrong this first bad impression , try another live wallpaper and you'll see how smooth is it. It runs great, using live or static wallpapers. What I did was delete the phasebeam.apk and push the stock 4.3 phasebeam.apk, that works good :good:.
- Hey! There's some good KK themes for old Theme Chooser if you want the KK look.
Anyway, here's another reason to not to ask what's the best rom for my GN.
This is just my personal opinion.
Hope you've enjoyed the post, and go try yourself!

Kustaa said:
...when it should be something like Hype, Compare, Choose.
I'm just posting this because it's crazy how we become kind of addicts to the cutting edge versions of Android, no matter how it really works on our device, it is just awesome because it works, on our beloved 3 years old nexus.
I'm the kind of guy who really search for smoothness, all around the system. I just can't stand a frame drop. It's kind of creepy. No, seriously, I look for details, and there's some things in KitKat I don't like. But all that said, and as I once read, if your eyes see at 15 fps it's not my fault lol. So, here they are:
- Notifications panel / Quick settings animation. Yes, guess what, the frame drop here is aweful. It stutters like hell. Just do it, expand the status bar and hit the tile many times, that's not smooth at all.
- RAM usage. They can say KK is optimized and bla bla, but real thing is that there's less free RAM than JB. It's a fact. You can go all the way of how Android manage memory and stuff, well, I rather more free RAM.
- Home button responsiveness. It just lags. Test it, open an app, something heavy e.g. Facebook app, and press home button. Now do the same but use back button. Give it a few tries if you didn't notice the difference at the first time.
- High battery drain.
There are some other things but you get the point. I felt less responsiveness in general, when multitasking, etc. So I decided to go back to Android 4.3.1 JB, CM 10.2.1 in my particular case. Oh yes, this feels awesome. Notifications panel / Quick settings animation is fully smooth, I've more free ram, Home button reaction is fast again, multitasking is great. I also realized that I missed the Vanilla ui. This is definitely where I'm staying.
So my conclusion is, you can follow the hype but don't stay just with the new things, make your own judgement, compare and choose what's your most suitable rom/android version out there
NOTES:
- I've been watching a lot of YouTube videos looking for this issues I've mentioned, so I discard problems with my Maguro in particular.
- I'm comparing both Android versions with the same apps (around 140 total apps), so there's no factory reset placebo effect.
- They're all present on different roms i.e CM, PA, and some others, so its KK related I guess.
- A particular thing about CM 10.2.1 is that it cames with a modified phase beam live wallpaper that slows down the launcher/system, don't get wrong this first bad impression , try another live wallpaper and you'll see how smooth is it. It runs great, using live or static wallpapers. What I did was delete the phasebeam.apk and push the stock 4.3 phasebeam.apk, that works good :good:.
- Hey! There's some good KK themes for old Theme Chooser if you want the KK look.
Anyway, here's another reason to not to ask what's the best rom for my GN.
This is just my personal opinion.
Hope you've enjoyed the post, and go try yourself!
Click to expand...
Click to collapse
I agree with the problems you mentioned and i do want speed, stability and smoothness.
I noticed those things when i first upgraded to KK.
To overcome those challenges, i tried all the roms (CM Remix, Cm11, PA, Omni, Omni FML, geyers, AOKP, etc..) with stock kernels and then with DIRTY V and Fancy.
More ram is available with dirty v, fancy and stock PA kernel.
Afterall, i choose my personal set up which is smooth and stable for my device. i am satisfied with it now.
With Android you always have a choice of tweaking, upgrading or downgrading from JB > KK. so choose whats best for you :good:

Even I've been thinking of try CM 10 for a while but I just can't leave KitKat. For me, latest Android version is important but this lag makes me feel bad. So I try to manage the performance using better kernel and not using apps like Facebook but it isn't enough. There is still lag in some or the other screen.
I bought Galaxy Nexus in last 9 months only so I couldn't use Android 4.3 roms much and thus I don't have much info about them. What do you think, should I give it a try? Also, which rom would you recommend?
Thanks.

hemantv said:
Even I've been thinking of try CM 10 for a while but I just can't leave KitKat. For me, latest Android version is important but this lag makes me feel bad. So I try to manage the performance using better kernel and not using apps like Facebook but it isn't enough. There is still lag in some or the other screen.
I bought Galaxy Nexus in last 9 months only so I couldn't use Android 4.3 roms much and thus I don't have much info about them. What do you think, should I give it a try? Also, which rom would you recommend?
Thanks.
Click to expand...
Click to collapse
As I said, you'll have to try my friend
If you want my opinion, CM 10.2.1 Stable is awesome. Rock solid. You should make a nandroid backup of your current rom and go try some 4.3 stuff! In worst scenario you'll be restoring the nandroid and that's it!

hemantv said:
Even I've been thinking of try CM 10 for a while but I just can't leave KitKat. For me, latest Android version is important but this lag makes me feel bad. So I try to manage the performance using better kernel and not using apps like Facebook but it isn't enough. There is still lag in some or the other screen.
I bought Galaxy Nexus in last 9 months only so I couldn't use Android 4.3 roms much and thus I don't have much info about them. What do you think, should I give it a try? Also, which rom would you recommend?
Thanks.
Click to expand...
Click to collapse
try the paranoid 3.99 based on 4.3
I remember it was really smooth

Kustaa said:
As I said, you'll have to try my friend
If you want my opinion, CM 10.2.1 Stable is awesome. Rock solid. You should make a nandroid backup of your current rom and go try some 4.3 stuff! In worst scenario you'll be restoring the nandroid and that's it!
Click to expand...
Click to collapse
I agree with you on everything you said. I think I even went back to CM 10.X (not sure the exact one), but it was much better than anything I had before. I am on PA 4.44 and my data loses connection often and not sure why. The version of CM though, I would put it on airplane mode and my battery would still be drained the next day when other versions I didn't have that issue. That's one reason I went to another ROM, but it appears I am just going through ROMS like crazy trying to find the one I like most. To me...battery life is the most important.

decisions.
when i stopped using google framework with all those apps you dont have to use...
i found my battery lasting much longer
setting my kernel to lazy...while turning up voltage and over hertz. gives it enough speed...with enough "crash"
to stay up for 3 to 4 days, just sitting there
and 1 to 2 while in normal use.
and using up my data....well no one is going to get much up time like that

Anyone here still using CM11?

Just got a bit tired of little bugs in the CM13 based roms and thinking about switching back to CM11. The only concern is the lack of security updates after the maintainers abandoned the projects for newer android versions.
Did anyone here try downgrading? Or maybe never upgraded? Is it wise to do so?
Some of my issues with CM13 based roms which have put me off:
Insane lag when reciving calls
Adopting Storage doesn't work half the time
Front Camera crashes
Mobile Data issues
Lock Screen Wallpaper Issue
Music suspend bug
Battery drain Issue

LOL brother. I am still using CM 11 build 14/11/15 with Xcelerate kernel build 4/12/15.
I still used this OS as it gives me atleast 500+mb ram which I require a lot for gaming.
At battery 100%............(with airplane mode on)...wifi on After 3hrs of continuous wifi gaming my battery drops to around 20%.
So I guess battery life is good.......though i haven't activated any sim cards(that would be a different story)
I don't have any voice(call) related problem though. Only bug is HDR. Once a picture is clicked with HDR on, you have to exit camera to click again in HDR mode
I actually need a CM 13 rom which provide such performance.(I was thinking about Slim rom 0.4 by Aniket Lamba)
So if anyone can suggest me better rom then please let me know. For me stability & usability matters more than recent builds.
I always will appreciate any information whether good or bad

I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
amangupta53 said:
Some of my issues with CM13 based roms which have put me off:
Insane lag when reciving calls
Adopting Storage doesn't work half the time
Front Camera crashes
Mobile Data issues
Lock Screen Wallpaper Issue
Music suspend bug
Battery drain Issue
Click to expand...
Click to collapse
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...

NightRaven49 said:
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
Click to expand...
Click to collapse
Hate towards KK is only because most of the apps are working great in >LP than in KK. If MIUI with LP is given then it can be easily a great choice for armani. MIUI ram issues have sorted out but only thing is standby time(wifi on) is low.

NightRaven49 said:
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
Click to expand...
Click to collapse
The music bug persisting after the downgrade is what's keeping me back. I, too, don't use Adoptive storage for all the bugs it brings - even on AOSP. But this means I'm running out of space by the end of the month because of necessary evils like WhatsCrap.
The gravitybox mod is good to know, although I don't use xposed, but really is simply a hassle to effectively change your wallpaper - especially when I'm changing them every other week.
I've recently tried disabling MPDecision - the music seems to be playing fine but I can't help but notice sightly degraded performance all around.

slst said:
Hate towards KK is only because most of the apps are working great in >LP than in KK.
Click to expand...
Click to collapse
Funny when there was a time when apps couldn't run properly on ART...
amangupta53 said:
I, too, don't use Adoptive storage for all the bugs it brings - even on AOSP. But this means I'm running out of space by the end of the month because of necessary evils like WhatsCrap.
Click to expand...
Click to collapse
Adoptive Storage is a hassle to set up: you need to format your SD card (which meant I had to shift everything out before converting it), and TWRP has no way to read such encrypted storage, so I didn't use it after the first time I tried it. Also you could do with regular housekeeping of your phone's storage; usually I keep WhatsApp images for a year before deleting them (after keeping the important ones and archiving the rest).
amangupta53 said:
The gravitybox mod is good to know, although I don't use xposed, but really is simply a hassle to effectively change your wallpaper - especially when I'm changing them every other week.
Click to expand...
Click to collapse
Xposed is very helpful, but if you don't want to use it then I won't force you.
Generally in those CM12/13 ROMs if I wanted to switch between lockscreen wallpapers I would leave a couple of those wallpapers in the /data/system/users/0 folder, just renamed to let me know which file is which wallpaper. Whenever I wanted to change them I just renamed them to the proper filename.
amangupta53 said:
I've recently tried disabling MPDecision - the music seems to be playing fine but I can't help but notice sightly degraded performance all around.
Click to expand...
Click to collapse
You don't have to leave MPDecision off the whole time: just disable it when listening to music, and re-enable it afterward.

Thank you everyone for your valuable comments:good:. It seems I can finally move on to CM 13:fingers-crossed:.(mostly slim6 version)
Note: I don't have music stop bug in CM11 though( may be related to firmware version or kernel. don't know why different people have different bugs:silly

Dr. Joy Das said:
Thank you everyone for your valuable comments:good:. It seems I can finally move on to CM 13:fingers-crossed:.(mostly slim6 version)
Note: I don't have music stop bug in CM11 though( may be related to firmware version or kernel. don't know why different people have different bugs:silly
Click to expand...
Click to collapse
What I think is that the KK firmware/modem we all flashed for CM13 builds has something to do with the music suspend bug. This is probably the reason why downgrading back to CM11/12.1 doesn't seem to fix this issue.
Anyway, seems like I'll just stick with CM13 for now.

NightRaven49 said:
Funny when there was a time when apps couldn't run properly on ART...
Click to expand...
Click to collapse
Sorry my friend i think its past now.

amangupta53 said:
What I think is that the KK firmware/modem we all flashed for CM13 builds has something to do with the music suspend bug.
Click to expand...
Click to collapse
Well not really, as the same v7.0.5.0 is used for CM11, 12 and early 13 builds. It's most likely a kernel issue, given that disabling MPDecision fixes it somewhat.
slst said:
Sorry my friend i think its past now.
Click to expand...
Click to collapse
I totally didn't know that, like totally dude
/sarcasm