Related
Hello all,
A long time ago I got bored of the stock ROM on my Desire HD and ended up rooting and installing CM7.2. That was a fantastic move as the phone was now faster, smoother and had more features than the stock ROM ever had. However, as Android has progressed onwards I've looked wistfully at 4+ phones and wished I had a slice of that goodness. So, over the past few months I've experimented with a couple of ICS and Jelly Bean ROMs (PACman, JellyTime, TrickDroid). However, despite these ROMs all being fully functional, performance was always often so frustratingly bad that I always ended up going back to CM7.2. The interesting thing is that individual applications generally tend to work very well. For example, a good portion of the time, web browsing on the stock browser on PACman is fantastic - smooth, fast, better than anything I'd experienced on the DHD. However, when loading and switching between apps (including sometimes when using the keyboard), going back to the homescreen etc, the performance would often be molasses slow. Reverting back to CM7.2, sadly, always feels like a breath of fresh air!
The only thing I noticed was that the device reported twice as much free RAM in CM7.2 as it did in the 4+ ROMs (between 200-300MB, compared to less than 150MB). Interestingly enough, in PACman when you go into the AOKP settings you can enable a RAM counter in the application switching interface. This always reported much less free RAM available than the the stock RAM counter that you can find in Settings->Apps->Running Apps (why is that?). But regardless of that, that counter was very frequently showing very little free RAM (a few MBs) when the phone was acting super slow. I tried messing around with memory management settings (enabling zRAM, enabling the shared kernel paging option etc), but to no noticeable effect. The only performance tweak I make to all the ROMs is to overclock the CPU to 1.5GHz...other than that, I just use the ROM.
Is this just an expected side effect of using 4+ ROMs on such an old phone? Or are people able to get super-smooth, never-frustrating, always-responsive performance with these ROMs by tweaking/changing stuff etc? Any thoughts?
Amr
I haven't experienced any problems using CodefireX. Did you make sure to fully wipe everything when you reinstalled the ROM?
Quarsar said:
I haven't experienced any problems using CodefireX. Did you make sure to fully wipe everything when you reinstalled the ROM?
Click to expand...
Click to collapse
Thanks for the CodefireX suggestion - I'm downloading it now. And yes, I always do a full wipe before installing a ROM.
Some users have reported auto rotation issues with just flashing the stable releases..currently there are two options I know of. One is to download a stock ROM than dirty flash a jb rom soon after..the directions I gave you for that one are probably out of sync. Than there's another option such as flashing codefire nightly than dirty flash the latest codefire stable release. I flashed nightly 20130219 than dirty flashed the latest stable release and auto rotation works for me. What surprised me the most is I came from a low end smartphone. That being a LG optimus one and even that had a cm10 ROM but I never messed with it so I'm not sure if it had the same problems as the ones I flash now on my I4G. Than again that LG only had 512 mb of memory
Sent from my Desire HD using xda premium
If you want more ram and you don't need many programs to be working in the background you can just set max backgr processes to 4 in dev options
Sent from my HTC Desire HD using Music Player
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).
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
We're all here because we want better roms than what our phones came with, upgraded roms etc. Idealy we'd want the most stable version with the last junk so it's the most responsive. As I upgraded more and more roms, I started to feel that the phone is showing it's age in processing power, and just like computers, you can't just install a newer stronger OS on older hardware, at some point you aren't gaining performance, you start to lose it because the hardware is struggling to keep up. I went from stock to 4.2 roms, then 4.4 roms, (pacman, mokee, CM, etc etc ). I eventually went back to 4.4 stock and it gave me the least trouble and quite snappy. Of course it had the OEM bloat from Verizon. Its been going strong for maybe a year, and now it too is starting to crash with a lot of bugs, probably from installing so many apps, but also I see a lot of built in apps taking up memory. So my main question is, if you still the Razr M and still using roms, what have you settled with ? What has been the most stable and fastest for you so far? For me so far it turned out to be the stock 4.4.2. So my options are to start over again with a fresh 4.4.2 or maybe a stripped 4.4.2, or one of the new 5.1 builds. I mainly use it for Navigation + music + calls, generally nav + music at the same time. Someone mentioned that CM12.1 couldn't handle that because of memory issues so that scared me off, but I love the CM12.1 on my galaxy tab pro. I do use the Bluetooth when im riding, and the camera from time to time, and the stock just had everything working.
If I can't find a stable build/rom, it might be time for me to move on to a newer quad core 2ghz + phone, browsing on the razer m is ok, but admittedly a little slow. The battery isn't what it used to, but it still gets through the day, and there are (albeit dodgy quality ) replacement batteries on amazon to hold out longer... The phone was basically free over 2 years ago, I've never been one to shell out $300 for a phone, but that oneplus one is mighty tempting to switch carriers for. ATT failed me on signal at this house so Verizon has been great, but i'd be willing to try tmobile if im forced to pick a new phone.
TLDR: Which rom has been the most stable for you ? ( rom name and build/version ).
vo_danh said:
So my main question is, if you still the Razr M and still using roms, what have you settled with ? What has been the most stable and fastest for you so far?.
Click to expand...
Click to collapse
Stock 4.1.2 (with uninstalled bloatware), as 4.4.2 has broken audio on (some?) Rev.B phones.
I have been on stock jelly bean, rooted stock kitkat (debloated with permissions removed for batt life), cm12.1 (our device is just too limited) and now cm11 snapshot 12 on kitkat boot loader. So far cm11 is my favorite.
Sent from my DROID RAZR M using XDA Free mobile app
For me stock kitkat debloated runs smoother, although is very sluggish sometimes: for example when I'm swapping messenger, whatsapp and running music player at the same time, it's almost impossible...
Ice tested cm when was 5.0,and was terrible. Pac man Kk, not as good as stock.
Sorry for this ugly link, I'm on my phone, but this post and the thread overall has a lot of good tips:
http://forum.xda-developers.com/showpost.php?p=53724034&postcount=17
In the last 2 and a half years I've been through:
Stock 4.1.2 (rooted after 1 day, debloated, Safestrap)
Eclipse Rom v1.2 (Safestrap)
CM10.1 (Unlocked BL)
CM10.2 (Unlocked BL)
CM11 (Unlocked BL, JB Kernel)
Stock 4.4.2 (rooted, debloated)
CM11 (Unlocked BL, KK Kernel)
CM12.1 (Unlocked BL, KK Kernel)
Best user experience for me? Sad to say but I had it with the Stock 4.1.2: overall smoother than all the rest. Then after some months my Razr M started a bootloop, so I unlocked the bootloader and tryed the CM ROM: the CM Power Widgets were an overkill at the time (mainly the 2G/3G toggle)...
After all the CM ROM that I've used, the second place goes to CM11 (with JB BL).
Right now I'm testing the latest CM12.1 builds, and they seems ok. I've installed onlyt the apps that are strictly necessary to me (gmail, maps, onenote, osmand, dropbox, wikipedia, Room Toolbox Pro, SuperSu, calendar, meteo, etc...). Everithing seems fine but I liked more the old KK style (lockscreen, quick settings). Everything is working, even if sometimes the data, Wifi and GPS signals are erratic. The performance are acceptable too.
So far a vote for CM11, and stock unlocked debloated. That's what i was heading towards too, stock debloat, and probably 4.1 it still has the best performance really. I mean the custom roms look great and all, but at the cost of performance which, after the initial wow factor, I think we would all prefer performance. Back when I had my HTC my favorite and most stable rom was jacko's most basic slim version ( he had like 1-5 tiers of peformance and features ). If I go back to stock and it lasts me another year or two i'll take it.
I'm trying out CM11 Snapshot 12 right now. I was already on 4.4.2 stock with unlocked kk bootloader so it made sense to try it first. Its already a lot smoother than what it was, freeing up half the memory. I noticed the dialer doesn't go all the way up sometimes, you have to push back and hit the keypad icon again. Otherwise very smooth so far. I'll report back after I get some use out of it and if I ever decide to go back to 4.1. I might need a new battery though, if I'm using it it doesn't last through a day.
*Update - I went from having basically no free memory left to about 50% free memory. I think my battery life increased dramatically with so much less running in the background. Maybe by 20-50%.
I took one phone call and updated a few apps, about mid day through the work day. was 12h by the end of the day and a few calls and some browsing w/o having to charge. Definitely gave new life to the phone. Very minor dialer bugs, sometimes the number pad doesn't come up correctly the first time.
Android 4.1 has various security issues that won't be fixed anymore, so that's not really an option.
But I don't think there are big differences in battery life anyway (see this).
After testing a lot of CM11, using Performance settings, changing memory settings, having a very poor battery performance, I've come back to the 4.4 backup with all the apps I had. The difference was incredible, now my phone feels snappier than an iPhone, and sincerely, i don't know why!! I think that doing a restore sometimes can help a lot.
Yeah the last time I did a fresh install of 4.4.2 stock it was great. After a while though with all my apps installed + the oem bloat the phone had very little memory left and became sluggish. My best options right now seem like going back to stock, either 4.1 or 4.4 and trying to do manual debloat.
I did a fresh install of CM11 again but still didn't fix it. I still had the occasional dialer error and wifi would only work upon boot, after disabling, it never reconnects to any wifi. Battery was still horrible. I went back to stock 4.4.2. RSlite would not work on any version on windows 8.1 64 bit. I had to do msfastbootv2 and was able to restore to stock 4.4.2 However upon booting, it wanted to update to 183.84.15 but failing. It would say there's an update, download it, reboot, and automatically boot into recovery. I would select reboot and it boots in, sometimes saying update complete but it hasnt' actually updated anything. I eventually gave up and started over, this time using stock recovery, not logging into my google account so it doesn't start downloading all my apps, no supersu, no gapps, and it successfully updated to 183.81.15. At that point using mfastbootv2 I installed twrp 2.8.5, rebooted into recovery, installed gapps and supersu. Then used titan to debloat using http://forum.xda-developers.com/droid-razr-m/general/complete-debloat-list-droid-razr-m-t3045731 , removed most of the things on that list, particularly anything I didn't use that I saw running. I also installed Greenify. After about a day I started noticing the google play services issue using a majority of my battery. I downloaded App Ops to disable google play services wake permissions. I am amazed at what happened. I feel like I have the original batteries back. I received 2-3 short calls today, and 2 browsing sessions, installed some apps (facebook lite), and I still have a lot of battery left, normally it would be over half gone. Going home after that much use and still having over 70% of battery left is nothing short of amazing and I no longer feel like getting a new phone. I was very close to trying the Droid Turbo.
TLDR: Got original usage/battery back with stock 4.4.2 + debloat (backup & Uninstall with titanium ) + App ops to fix google services wake battery drain + Greenify. I don't know how much Greenify is doing, I attribute most of my gains from debloat + fixing the google services issue. Before App Ops you'd see a giant bar at the top of Google Services instead of screen.
Still odd you having WiFi issues. I don't I did learn recently that my Bluetooth does not seem to be fully functional.
Sent from my GT-P3110 using XDA Free mobile app
So far, all I've tried (and stuck with) are stock 4.1, stock 4.4.2, and CM 12/12.1.
Stock ROMs were fairly snappy, but I was always a little fearful (irrationally, but still) of trying to debloat while on 4.4 (and I remain fearful of downgrading the bootloader). This is my daily driver, though, and it must remain so until I become eligible for a newer phone in December (or I can pick up something better, used, for extremely cheap ...).
I have been toughing it out on CM 12 since late January. I like several of Lollipop's UI changes and new features (as well as CM's additions over stock), so despite some frustrations with bugs and somewhat-laggy performance, I haven't felt terribly compelled to try CM 11, or to go back to stock 4.4.2. (At least, not all the time; there have been moments of extremely slow response times where I've wanted to wipe /system right then and there and flash CM 11. I have stuck with 12 so far in hopes of improvements on the way to the first snapshot.)
Also, vo_danh, I was the one who reported about the issue with simultaneously running Maps and Play Music. I don't think I've ever gotten a phone call while trying to run those, but suffice to say that I have enough trouble with (occasional) lag when a call comes in.
If you're already on the kk boot loader like me, you don't need to downgrade the boot loader for cm11. Its been almost a week and i am still just amazed at how well this config is working for me. The battery life is like new again. Don't be afraid of debloating with titanium, since you can back it up first before unisntalling, if anything goes wrong, simply reinstall the backup. As a safety, after I restored to stock 4.4.2, updated to 183.84.15 OTA, I created a TWRP backup, so if anything goes wrong I can just restore it with TWRP instead of doing through all the steps to go back to stock. I didn't remove everything that was on that debloat list, just most things from verizon or anything I raw under 'running' list that I didn't need. It's so stable and fast. I would only move to a stock + debloat rom now for this phone for now. If I had a stronger phone there's no doubt i'd be using Cm12.1 but for now, this phone isn't meant to handle it smoothly and the wifi issues i had with Cm11 just make it not worth it. All wifi issues are gone now on stock. I didn't have wifi issues on any of the other roms either.
vo_danh said:
We're all here because we want better roms than what our phones came with...
Click to expand...
Click to collapse
1. One that the phone came with, with a little tweaking. 4.1.2 deodexed and debloated. Best usability and battery life. Slows down with heavy games tho so i unlocked the BL.
2. KK debloated. 4.4.2 i think. better in many respects but I sorely miss the Jb camera. It was wonderful. Battery life had come down a couple of notches.
3. Currently running the Bliss rom (5.1). My earpiece and mic doesn't work with the latest update. lol.
Edit: Call issues in the Bliss rom have been fixed. It's a solid rom and deserves a strong recommendation.
I've had my M8 for about a year now and rooted it almost right away. I've been rooting my phones for years, since my HTC Incredible!
I've had about 4-5 different ROMs on my phone in this past year from CM to Revolution HD and Sky Dragon. But ALL of them seem to have the same issues. After a certain amount of time, maybe a week or maybe a month, they ALL start to get really, really laggy. I swear I've wiped and re-loaded my phone at least a dozen times so far!
For example, if I try to open Gmail or Chrome, it could take upwards of 5 seconds to actually pull up the program. Sometimes it's so bad, I have to force a reboot by holding power+volume up because the phone just won't respond to anything.
I've tried to go into apps and see the running programs, but most of the time either nothing special is running besides system type apps or it will just hang for minutes and I eventually force a reboot.
Am I the only one who is having such problems with these ROMs? Could I have gotten a bum phone? Is there some sort of diagnostics that I can run to make sure the CPU/Memory/etc. is working properly?
I'm at a loss right now. I nearly threw my phone across the room onto the concrete floor yesterday because it was so unusable all day.
Please help me figure out what's going on here, I'm at my wits end with this BS!
ned4spd8874 said:
I've had my M8 for about a year now and rooted it almost right away. I've been rooting my phones for years, since my HTC Incredible!
I've had about 4-5 different ROMs on my phone in this past year from CM to Revolution HD and Sky Dragon. But ALL of them seem to have the same issues. After a certain amount of time, maybe a week or maybe a month, they ALL start to get really, really laggy. I swear I've wiped and re-loaded my phone at least a dozen times so far!
For example, if I try to open Gmail or Chrome, it could take upwards of 5 seconds to actually pull up the program. Sometimes it's so bad, I have to force a reboot by holding power+volume up because the phone just won't respond to anything.
I've tried to go into apps and see the running programs, but most of the time either nothing special is running besides system type apps or it will just hang for minutes and I eventually force a reboot.
Am I the only one who is having such problems with these ROMs? Could I have gotten a bum phone? Is there some sort of diagnostics that I can run to make sure the CPU/Memory/etc. is working properly?
I'm at a loss right now. I nearly threw my phone across the room onto the concrete floor yesterday because it was so unusable all day.
Please help me figure out what's going on here, I'm at my wits end with this BS!
Click to expand...
Click to collapse
Have you tried ViperOneM8?
The latest ROM (4.5.1) is a port of Sense 7 from the M9, but still has some small bugs to iron out. They are being addressed and will be fixed in the next update.
If you were to flash v4.3.0, you would get a stable ROM with lots of customizing options. It is Lollipop as well, but still on the official Sense 6 framework.
xunholyx said:
Have you tried ViperOneM8?
The latest ROM (4.5.1) is a port of Sense 7 from the M9, but still has some small bugs to iron out. They are being addressed and will be fixed in the next update.
If you were to flash v4.3.0, you would get a stable ROM with lots of customizing options. It is Lollipop as well, but still on the official Sense 6 framework.
Click to expand...
Click to collapse
Yep, tried that one. I think it was one of my first ones actually (I actually donated to it!). Ran that one for about 6 months before giving up and moving on.
Dirty Unicorns works well for me, I have never experienced lags but updates are always available so the longest DU rom that stayed on phone was about 3 weeks.
Latest current version is official v9.6 android 5.1.1
Also you could try fstrim app on your current rom.
crackerjack1957 said:
Dirty Unicorns works well for me, I have never experienced lags but updates are always available so the longest DU rom that stayed on phone was about 3 weeks.
Latest current version is official v9.6 android 5.1.1
Also you could try fstrim app on your current rom.
Click to expand...
Click to collapse
Thanks, I'm running CM 12.1 right now and really don't want to install yet another ROM. I'm to the point that if this doesn't work I'll just bring it back to stock and suffer with that or buy a new [email protected] phone!
I did try to run the fstrim app (didn't know about this), but it won't run. Says my system isn't supported.
The ViperOneM8 would be a really good ROM to use. Used it from the start, till moving on to my HTC One M9.
To ensure it always runs stable you got to update your firmware sometimes to match the base the developers are using for theire ROM. Did you always do and take care of this point!?
ned4spd8874 said:
Thanks, I'm running CM 12.1 right now and really don't want to install yet another ROM. I'm to the point that if this doesn't work I'll just bring it back to stock and suffer with that or buy a new [email protected] phone!
I did try to run the fstrim app (didn't know about this), but it won't run. Says my system isn't supported.
Click to expand...
Click to collapse
Always have a backup just in case!!!
Flash pie patch for fstrim to work.
http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
More info why you need pie patch:
http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731
I just came from Razr this year to M8
Stayed with CM11 thru CM12.1 on the Razr up until about this time last year(kept trying up to cm12.1 on other slots until 3/12/15). The whole time the phone would become very laggy after about a week just as you are experiencing now. It was very frustrating & I know how you feel. Tried Liquid Smooth & it was a lot better with no lag but a few bugs, then stayed with AOKP rom until about March of this year,this was the best rom for me on the razr.
Wanted a faster phone because razr was 4 years old & was thinking hardware was just to old for performance.
So my friend DumbleDore suggest M8 running Dirty Unicorns & I have great phone!!!
Had a few issues with screen turning on while in my pocket(stock did it also) but smac0628 told me to turn off ambient display & that issue is resolved.
If Dirty Unicorns does not work for you then it has to be hardware on the phone.
You should try before buying another phone!!!
http://download.dirtyunicorns.com/files/m8/Official/DU_m8_5.1.1_20150814-0142.v9.6-OFFICIAL.zip
More info:
http://forum.xda-developers.com/htc-one-m8/orig-development/rom-dirty-unicorns-5-0-2-htc-one-m8-03-t3052466
crackerjack1957 said:
Always have a backup just in case!!!
Flash pie patch for fstrim to work.
http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
More info why you need pie patch:
http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731
I just came from Razr this year to M8
Stayed with CM11 thru CM12.1 on the Razr up until about this time last year(kept trying up to cm12.1 on other slots until 3/12/15). The whole time the phone would become very laggy after about a week just as you are experiencing now. It was very frustrating & I know how you feel. Tried Liquid Smooth & it was a lot better with no lag but a few bugs, then stayed with AOKP rom until about March of this year,this was the best rom for me on the razr.
Wanted a faster phone because razr was 4 years old & was thinking hardware was just to old for performance.
So my friend DumbleDore suggest M8 running Dirty Unicorns & I have great phone!!!
Had a few issues with screen turning on while in my pocket(stock did it also) but smac0628 told me to turn off ambient display & that issue is resolved.
If Dirty Unicorns does not work for you then it has to be hardware on the phone.
You should try before buying another phone!!!
http://download.dirtyunicorns.com/files/m8/Official/DU_m8_5.1.1_20150814-0142.v9.6-OFFICIAL.zip
More info:
http://forum.xda-developers.com/htc-one-m8/orig-development/rom-dirty-unicorns-5-0-2-htc-one-m8-03-t3052466
Click to expand...
Click to collapse
Thanks, I flashed the pie patch, but that broke CM, it was stuck at the boot animation. I did make a backup, but decided to wipe and install DU for the heck of it. I don't have very high hopes to be honest after all these problems I've been having. I'm also hesitant to try to install the pie patch on DU...we'll see.
Fingers crossed that this all works!
Update: Welp, that was stupid, tried to install the pie patch on DU and it does the same thing; just stays on the boot animation. Dirty flashing the DU ROM seems to have brought it back to life without totally re-flashing.
I've never seen this issue. I'd suggest it has nothing to do with the roms, but more to do with apps installed and possibly also caches.
Yes, a clean install of anything will clean up things and all will be smooth. After time, certain apps and/or full caches can bog things down.
Your setup will determine smoothness also.
Just my opinion... But again, I've never had any rom slow down and lag after any amount of time. But my phone is lean as far as apps and setup go. And housekeeping is strict. :good:
ned4spd8874 said:
Thanks, I flashed the pie patch, but that broke CM, it was stuck at the boot animation. I did make a backup, but decided to wipe and install DU for the heck of it. I don't have very high hopes to be honest after all these problems I've been having. I'm also hesitant to try to install the pie patch on DU...we'll see.
Fingers crossed that this all works!
Update: Welp, that was stupid, tried to install the pie patch on DU and it does the same thing; just stays on the boot animation. Dirty flashing the DU ROM seems to have brought it back to life without totally re-flashing.
Click to expand...
Click to collapse
Sorry about the piepatch link, thought it would have been good.
I have pulled the one I am using from my sd-card on phone & know it works, have used many times.
Here is the upload:
https://www.mediafire.com/?ms7l9xk27rw3fzd
I do not use facebook app, if you need it I would recommend the lite version.
If you need I will try to find for you.
crackerjack1957 said:
Sorry about the piepatch link, thought it would have been good.
I have pulled the one I am using from my sd-card on phone & know it works, have used many times.
Here is the upload:
https://www.mediafire.com/?ms7l9xk27rw3fzd
I do not use facebook app, if you need it I would recommend the lite version.
If you need I will try to find for you.
Click to expand...
Click to collapse
Thanks, that one works!!!
I'm still trying to understand this app and what it does though. So, by default, /data and /cache are checked, but /system is not. Is there a reason to not run this for the /system partition?
ned4spd8874 said:
Thanks, that one works!!!
I'm still trying to understand this app and what it does though. So, by default, /data and /cache are checked, but /system is not. Is there a reason to not run this for the /system partition?
Click to expand...
Click to collapse
Check all partitions, I think some roms or phones have a problem trimming system partition the reason it is not checked by default.
Its my understanding that android 4.3 & latter support trim & run automatically under certain circumstances.
http://www.xda-developers.com/yet-another-reason-to-update-to-android-4-3-trim-support/
The apps just let you control trim manually or schedule trim when you want to.
Trim is also on ssd's(solid state drives) that took the place of hdd's that could be defragged to speed up OS.
Dirty Unicorns has always been fast for me & trim was not needed because of quick updates.:good:
crackerjack1957 said:
Check all partitions, I think some roms or phones have a problem trimming system partition the reason it is not checked by default.
Its my understanding that android 4.3 & latter support trim & run automatically under certain circumstances.
http://www.xda-developers.com/yet-another-reason-to-update-to-android-4-3-trim-support/
The apps just let you control trim manually or schedule trim when you want to.
Trim is also on ssd's(solid state drives) that took the place of hdd's that could be defragged to speed up OS.
Dirty Unicorns has always been fast for me & trim was not needed because of quick updates.:good:
Click to expand...
Click to collapse
Thanks for all the help so far!
Something is still wrong...still locking up and being unresponsive. Just going through and deleting apps until it starts behaving...what a pain! I still don't get it though, it's not like I have new apps, these are the same that I've always been using. Dunno.
ned4spd8874 said:
Thanks for all the help so far!
Something is still wrong...still locking up and being unresponsive. Just going through and deleting apps until it starts behaving...what a pain! I still don't get it though, it's not like I have new apps, these are the same that I've always been using. Dunno.
Click to expand...
Click to collapse
Ok sounds like you have proved it not being a rom issue & think you may be on the right track by eliminating apps that could cause issues(slow & pain-in-the-a**).
I know you been doing this for a while but is firmware & TWRP up to date?
Also when changing roms do you wipe all that is needed before install?
crackerjack1957 said:
Ok sounds like you have proved it not being a rom issue & think you may be on the right track by eliminating apps that could cause issues(slow & pain-in-the-a**).
I know you been doing this for a while but is firmware & TWRP up to date?
Also when changing roms do you wipe all that is needed before install?
Click to expand...
Click to collapse
Latest TWRP and yes, I do believe those are the settings I use when wiping.
One thing I have noticed is that when it does get slow, opening up the recent apps and clearing them seems to help performance. That is, when it's responsive enough to bring up that screen.
About two days and still no luck. Decided to wipe and resist installing any extra programs for now. Running bare bones sucks and it's boring!
I removed about 20 programs and none made a difference. Started with the obvious ones that would/could run in the background like Facebook, but that didn't matter. The only thing that worked every time to help with performance was closing all the recent apps.
Now I'm going to run as bare as I can until at least tomorrow evening and slowly install apps...
ned4spd8874 said:
About two days and still no luck. Decided to wipe and resist installing any extra programs for now. Running bare bones sucks and it's boring!
I removed about 20 programs and none made a difference. Started with the obvious ones that would/could run in the background like Facebook, but that didn't matter. The only thing that worked every time to help with performance was closing all the recent apps.
Now I'm going to run as bare as I can until at least tomorrow evening and slowly install apps...
Click to expand...
Click to collapse
The ROMs that you have mentioned that you have tried are all pretty much as stable as can be. I'm going to say here that it is either user caused, or you are expecting too much.
Do you think there will never be issues? It happens on stock as well.
xunholyx said:
The ROMs that you have mentioned that you have tried are all pretty much as stable as can be. I'm going to say here that it is either user caused, or you are expecting too much.
Do you think there will never be issues? It happens on stock as well.
Click to expand...
Click to collapse
I understand that there will always be issues. But the phone shouldn't lock up totally while doing simple things such as opening email or turning wi-fi off. Last week I was at a point where I had to force reboot my phone just about every time I tried to do something because it was so unresponsive. That is not normal nor acceptable.
I've been running SkyDragon for weeks, dirty flashed and I have loads of crap on mine. I have absolutely no issues with lag, locking up or any other kind of anomaly.
No different to stock Tbh.
I very rarely reboot, I use All-in-one toolbox to disable unnecessary apps from start up and the excellent Extended settings with Xposed.
ashyx said:
I've been running SkyDragon for weeks, dirty flashed and I have loads of crap on mine. I have absolutely no issues with lag, locking up or any other kind of anomaly.
No different to stock Tbh.
I very rarely reboot, I use All-in-one toolbox to disable unnecessary apps from start up and the excellent Extended settings with Xposed.
Click to expand...
Click to collapse
Show off!