I've been running MM for months now, currently running OctOS MM and it has been running almost flawlessly. The only issues are well documented, the video playback in Chrome and the flashlight turning off. Those things are minor in comparison to the improvements the ROM has made to the phone. It is the fastest it's ever been, nothing compared to the newer phones but snappy and very usable in everyday situations. Which to me is defined as being BT to the car while navigating and playing music. The battery life is amazing, like back to the ICS days. With Greenify's aggressive doze, there is hardly any battery drain with the screen off. I was very near to getting the Nexus 6P but now I'll definitely use this phone as my daily for another year and see what the iPhone 8 brings. I've also been running the phone naked and it just feels right. Perfect proportions! Gave my iPhone 6s to my wife a few months ago because that phone is boring to a fault. Everything just works perfectly which means no fun. Funny that I enjoy Android because it is such a POS. Lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DROID MAXX using Tapatalk
So, tell me my friend...do I have a chance with non-dev SU6-7.3 to get this? Few days I was on first 4.4.4. update and didn't do the next updates and I mistouched the buttons and accidentaly updated my phone...so I did all of them. I'm really jealous of you. Always wanted the best for my MAXX. Is there any chance at least for root?
Sorry, I'm not too familiar with rooting locked phones. I'm always just one drop away from losing my unlocked bootloader. Dropped my first MAXX, which was unlocked from ICS. Send it in to Motorola before Lenovo took over and they replaced it no questions asked. The phone came with 4.4.4 and I lost my unlocked bootloader, but just before I was going to upgrade to 6-7, the bootloader unlock method came out for 4-23 and so I've been unlocked since. The MAXX is very fragile, even when everything looks fine, a good drop will damage the internals, with the rear camera going bad as the first sign. I'm running the phone naked nowadays because I'm extra careful and it feels so light and good to the hands but if I do break it, it'll be an excuse to get a Nexus 6P. I think the MAXX runs 4.4.4 great and you're not losing out on too much. 4.4.2 was the best IMO looking back. Hope you find a way to root but if not, it's still a damn good phone. I still have a backup MotoX on 4.4.4 even though it is also bootloader unlocked. If Motorola know what's good for them, they would offer unlock codes for our phones they screwed us over with LP. LP was complete junk, but it's the principle.. lol. Regardless, I'm done with Motorola as long as they are under Lenovo.
Sent from my DROID MAXX using Tapatalk
Can you tell us where you got this ROM from? I looked on OctOS' site and didn't find DROID MAXX on their supported list.
And/or post a link to full backup of your SYSTEM partition? [I am not sure if there's phone-specific information on that partition, I believe not though since those partitions are reflashed from official and downloaded ROMs all the time.] The reason for this is because I am not sure why we can't take a BL-unlocked phone, upgrade it to LP or MM using CM or another ROM, pull it's SYSTEM partition, and flash that using the @CrashXXL method to a BL-locked phone.
I imagine there is a partition signature verification happening somewhere, but somehow the @CrashXXL method is not tripping that up with the QHS_DLOAD mode method. And I'm willing to try this backdoor method to put an LP/MM SYSTEM on the phone, because I think worst-case I could go back to SU6-7 which is where I am today. Would be in mid-June though.
I'll send a request to them to see if I can share the link to the ROM. I was running their ROM on my MotoX, made a TWRP backup and flashed it onto my MAXX. Used the 5.1 patch to activate the capacitive buttons and all was good. Shared my results with the OctOS folks and they told me, yeah, try this MAXX version they had and been running it since. It is not in the main OctOS website and I don't want to share it without asking them first, standby.
The OctOS ROM also includes KernelAdiutor and I just started playing with the Low Memory Killer and think I stumbled onto something. Right now in Aggressive setting and it is multitasking like a champ, where before it would still stumble and stutter, it is smooth as butter. I have it BT'd to my Bose Mini, playing YouTube Music, Waze, posted on Facebook and now typing this post on Tapatalk and smooth as butter. The phone has never run this smooth at anytime before and running that many app would have likely killed the phone by now. Amazing. So it may be a memory management issue more so than the fact that the MAXX only has a dual core processor. Something to look into. I'm not holding my breath, the real test will be when I drive to work, as the car's BT seems to tax the phone heavily.
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
I'll send a request to them to see if I can share the link to the ROM. I was running their ROM on my MotoX, made a TWRP backup and flashed it onto my MAXX. Used the 5.1 patch to activate the capacitive buttons and all was good. Shared my results with the OctOS folks and they told me, yeah, try this MAXX version they had and been running it since. It is not in the main OctOS website and I don't want to share it without asking them first, standby.
The OctOS ROM also includes KernelAdiutor and I just started playing with the Low Memory Killer and think I stumbled onto something. Right now in Aggressive setting and it is multitasking like a champ, where before it would still stumble and stutter, it is smooth as butter. I have it BT'd to my Bose Mini, playing YouTube Music, Waze, posted on Facebook and now typing this post on Tapatalk and smooth as butter. The phone has never run this smooth at anytime before and running that many app would have likely killed the phone by now. Amazing. So it may be a memory management issue more so than the fact that the MAXX only has a dual core processor. Something to look into. I'm not holding my breath, the real test will be when I drive to work, as the car's BT seems to tax the phone heavily.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Sounds good, I appreciate it and please keep me posted.
lloat said:
Sounds good, I appreciate it and please keep me posted.
Click to expand...
Click to collapse
Here's the link to the ROM. It is not supported, so use at your own risk. With that being said, I've been using the ROM for months. Just discovered a bug where if you try to make a call while BT'd to the car, it will crash. Never noticed it until over the weekend because I've been receiving calls just fine. Might just be a permission issue. Haven't looked into it yet.
https://basketbuild.com/devs/Team_Octos/private/moto
Sent from my Moto X using Tapatalk
Said I was never going to buy anything Motorola post Lenovo but couldn't help myself.
Have it synced to both my MotoX and my MAXX by fooling the watch into thinking it is the same phone. Did that by flashing a MotoX TWRP backup to the MAXX. I need to fix the Tapatalk sig to read sent from my MAXX...
Sent from my Moto X using Tapatalk
Johnny Wong said:
Here's the link to the ROM. It is not supported, so use at your own risk. With that being said, I've been using the ROM for months. Just discovered a bug where if you try to make a call while BT'd to the car, it will crash. Never noticed it until over the weekend because I've been receiving calls just fine. Might just be a permission issue. Haven't looked into it yet.
https://basketbuild.com/devs/Team_Octos/private/moto
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip! This rom really seems excellent. However, there is usually no in-call sound either way when I'm receiving a call! When I initate the call, it's all OK. Out of 3 different callers, I only had one that had a voice connection.
Anyone experiencing the same?
UPDATE: a zip for Moto X from here: http://forum.xda-developers.com/moto-x/development/aosp-audio-fix-ghost-t3380744 seems to have solved the issue. Needs testing though.
I had to go back to LP after discovering that BT is not working correctly when synced to my cars. As soon as I try to make a call, the phone freezes and then reboots. Other than that, the ROM was perfect. Hopefully they will resolve the issue in a future build but for now, I flashed back to OctOS's final build of LP 5.1.1 for the MotoX. This is only the first day back with LP and I already ran into the cell standby battery drain (don't know if it is actually a drain or if it is just reporting wrong) and I'm missing some of the MM features such as the integrated search function. Oh well, that itch to get a Nexus 6p is coming back again and the price is pretty competitive too. So tempting....
I ended up going back to 5.1.1 (DU's 9.8).
The long-standing marshmallow bug of statusbar scrolldown speed (when triggered by an external event, not direct pulldown) is not fixed and really annoying.
Sound was reproducibly fixed by the AOSP patch though.
Yeah, it's too bad no one has cracked the code on some of those MM bugs. If someone can port Now on Tap to LP I would be set. That and Doze. Pretty happy right now with 5.1.1, looks like it has been polished up quite a bit since the last time I ran it. Might have to give DU a try to see if it has the same cell standby battery bug. OctOS never closed out Obake with a final LP build so I'm forced to run the MotoX version. Not bad minus the fact that my capacitive buttons are at full brightness with the MotoX LP 5.1 patch.
Sent from my DROID MAXX using Tapatalk
Tried DU LP with high expectations but couldn't get it to work at all. From first boot up, it was already experiencing random restarts. Probably did something wrong, but I did a full wipe minus internal memory before install. Anyway, restored to OctOS M6 LP, and have been running it for a week. The ROM started to slow down, with random choppiness and was hit with the radio standby bug even with the MobileRadioActiveFix xposed module installed. Was not a happy camper to the point I ordered a One plus 3 but then soon realized it won't work on Verizon (epic fail), don't know how I overlooked that. Anyway, have to return that phone when it arrives but that's a whole different story. Back to the MAXX, went to the MotoX forums and read up on Tycoo's kernel for CM12 and decided to give it a shot. Now it's only been a day but so far, it is running flawlessly. Better than even when I was on MM. Overclocked to 1890mhz, intelliactive, intelliplug, Zen I/o, and other recommended settings such as Zram at 320mb equals a snappy new phone! Don't really care about battery life but the MotoX guys claim 5hr SOT with those settings which means the MAXX would easily do that and more. Will report back, definitely recommend!! Also, I highly recommend the snapdragon camera, it is by far the fastest camera available for our phone.
Sent from my DROID MAXX using Tapatalk
Related
Ok, aside from the bootloop issue upon install, I have to say so far, not bad. The blur aspect is definitely better, however I dont care for it any more now than I did before. The color scheme is quite visually appealing. Very much like lucid steel theme for fission. I would prefer the scheme from the fission gb theme but this is absolutely an improvement over the stock froyo appearance.
Overall system speed seems to be somewhat improved, and there is a big issue w/ launcher pro which sucks. with launcher pro there is some heavy lag in transitions and the general feel of the phone is kind of clunky and choppy. Without launcherpro, phone tends to run quite smooth. no status bar controls kinda sucks, and the reduced screen density w/o launcher pro is also kind of a downer, but overall im not going to complain. Its definitely progress.
One big downside I noticed after 2 days is battery life is very hit or miss. On fission 2.6.1, i was making it easily 1.5-2 days on a single charge. Yesterday I made it home with 40% left, today I was at 10% when i left work. I can attribute this heavily to Blur, but this is definatley somethign that a new fission or UD build should fix
I have to say that since the devs seemed to have abandoned the Fission project, I haven't looked back since upgrading to GB Blur. it's snappy and attractive and while it still has alot of the blur bloat i hate, root + ti backup makes things a little more manageable.
so far, i've managed to remove teh global unplug, task manager, the blur text messenger, backup asssistant and city id. my battery life is probably slightly better than it was on fission, depending on what i'm doing (games seem to destroy it).
we still have to recognize that this IS a leaked version and there are still some misses with the build. data services randomly failing, inability to make calls/send texts and the weird keyboard backlight issue. other than that, i've been pretty pleased.
I just upgraded yesterday and I am very happy with it
Sent from my DROID2 using XDA App
They are making a fission GB right now.. I'm almost positive that Angdroid was busy with some stuff but now hes back
GSletta said:
They are making a fission GB right now.. I'm almost positive that Angdroid was busy with some stuff but now hes back
Click to expand...
Click to collapse
Seems he indicated he was looking at it, but made no promises of an updated ROM on teamdefuse's website, twitter, or this forum...
Did you see something else where he said he was specifically working on GB Fission?
I think GB for the D2 makes some major improvements, but I can't give up liberty for it. Just have to wait and see if Liberty GB comes out.
dudeSDCA said:
Seems he indicated he was looking at it, but made no promises of an updated ROM on teamdefuse's website, twitter, or this forum...
Did you see something else where he said he was specifically working on GB Fission?
Click to expand...
Click to collapse
yeah i thought that topic came up when the sdk was made available, but nothing ever really came to light. i feel like after p3droid's recent tweets/posts, etc., the landscape has been drying up.
I got the impression from what p3 said that the devs were under some fire as google seems to be having second thoughts about open source, as well as unpaid tethering raising some eyebrows with teh carriers, which is understandable.
Hopefully once things get ironed out we'll see some ovens refire and some cool stuff gettin rolled out.
I'm still kind of split and definitely agree that gaming on gb is a battery killer in a huge way. Overall battery life is good, however i've had a few days where it just sucked down. Ive been off charge since 6am, 12 hours later with minimal-moderate useage i'm at 70%, however there have been days where I have used the phone way less and been getting charge warnings by 2pm.
Hopefully the official release will solve the rest of these issues.
All I can say is that I hope some custom ROMs are available for Droid 2 Gingerbread soon, because what I have now is buggy to the point of being frustrating. Besides being a memory hog, I sometimes lose my data connection for no apparent reason and my keyboard backlight doesn't always work. Also, even when I do have a data connection, my phone has problems loading web pages much of the time.
Sent from my DROID2 using XDA App
Oh, and I forgot to mention that the screen sometimes randomly shuts off without warning.
Sent from my DROID2 using XDA App
if you have an issue with the screen randomly shutting off try unchecked the in pocket detection setting. I found this was way to sensitive and would consistently shut my screen off in dimly lit areas.
yeah, battery life has become sketchy, like one day i'll make it through the day with 60% left with moderate useage, similar useage next day i'll be charging by noon. USB reboots have reared their ugly head in the last 48 hours to the point where im charging off of the wall outlet and seriously considering sbfing back to fission 2.6.1
To this point I haven't had any major problems whatsoever ...
Only thing is browser sometimes crashes ...batt life is amazing!
9hr shift on work barely drops to 70% with wifi always turned on moderate txt n web
Sent from my DROID2 using XDA Premium App
SIgh WTF getting whitescreen ....cant get back to CWMR, tried every thing....wtf ..... is this bootlooping? NO MATTER WHAT I do can not get back into recovery.
I have a trick to acces any files but most of them seem corrupted? Im only guesing as there is now a "?" by the file icon.
I tried loading bootsrap recovery
phone appeared bricked. rebooted and again cannot get into recovery.
I laready had 2.3 rom ...did I miss something? IM usually pretty good on this stuff. Modded my hd2 and rooted my g2x no issues....what dee hell is dis sheot
(mods move if I am posting in wrong section)
SOB me having bad day...lol...just realised this is the dev thread not general...I suck .....POINTS!!!!!
EDIT:
AH HA!!!! I was able to get to CWMR by an interesting method! I had previusly DL mini task manager(took it off the market for some reason) and thats THE ONLY ap that was working!
so anyways in the info bar at top it was showing mini task coming up .... Somehow it was acting as a backup! (has any one else experienced this?) so I long tapped on bootstrap rec icon and voila! it asked if I wanted to go into bootstrap and of course I did and .....yes!!! thank you cwm i got to the recovery green screen!!
FIrst I tried Tpro recovery....would not work....tried loading bootstrapzip....nothing...so....I figure since all my shizzle is backed up through my google act I did a factory reset, wipe data, and redid the new GB hack.
VOILA! it loaded ! no bootloop! just had to re-register phone and accounts!
so I leave you with this narcissistic picture of myself....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey everyone,
I've been running GB and ZS for about a week now. The one thing that I noticed was that there isn't anywhere where you can turn off mobile data? Maybe I'm blind, but it's not in wireless and networks? Any ideas? If not, oh well. I still think I found something in GB that's keeping me from going back to 2.2. It's just as stable as 2.2 only faster! Anyways, cheers all!
Seanydizzley said:
Hey everyone,
I've been running GB and ZS for about a week now. The one thing that I noticed was that there isn't anywhere where you can turn off mobile data? Maybe I'm blind, but it's not in wireless and networks? Any ideas? If not, oh well. I still think I found something in GB that's keeping me from going back to 2.2. It's just as stable as 2.2 only faster! Anyways, cheers all!
Click to expand...
Click to collapse
It should be under
-settings
-data/battery
-enable data saver mode
That should only downloads over wifi only
tnygigles66 said:
It should be under
-settings
-data/battery
-enable data saver mode
That should only downloads over wifi only
Click to expand...
Click to collapse
Of course its there. Lol. Didn't even think of that. A nice thanks coming your way!
This device is amazing, or at least was supposed to be. Almost stock android, a good camera, a ridiculously strong chipset, gorgeous screen and tremendous battery capacity.
What could possibly make this phone be anything but awesome? The software!
Motorola may have been on the right direction with these almost pure Android devices and their smart and functional features, but they should urgently look out for some software issues.
1- KitKat on Moto Maxx have a huge battery drain problem when the phone is in stand by mode, never got fixed, and if you use art runtime you have to wait more than 3 minutes to have your devices booted up. Cyanogenmod developers could theach Motorola engineers how to resolve this. That's absurd to me.
2- I'm on the soak test, the super anticipated lollipop, I thought Motorola was leaving KitKat full of bugs to work better on lollipop, but now I have lollipop and things did not get better, I can't and I won't talk about it in details, but it is ridiculous. I had a Galaxy S2, a Galaxy S3 and after that I had a LG G2, though LG and Samsung used to make we wait a lot for updates I saw Cyanogenmod, paranoid, etc ROMs getting around bugs on their alpha and beta ROMs a lot faster then the official Motorola engineers, and I assume they are being well paid by Motorola to work on it.
Moto Maxx have no custom ROMs, no custom kernel, I wish I could do something to change this scenario, but I know nothing about programing. I'm trying hard to like this phone, but it is quite difficult right now, no community, no fast updates, lags, bugs, and the Snapdragon 805 hate the heat so much that the phone appears to be using a low cost processor when it gets hot even when it's not on heavy usage, and I'm not talking about the soak test, I experienced problems since KitKat, looks like they don't care at all. Right now I'm very frustrated, I regret a lot buying this phone and I can't even find anyone willing to buy it, Motorola needs a better development team, cause if things keep going this way, I'll never buy another Motorola device.
RaphaDL said:
KitKat on Moto Maxx have a huge battery drain problem when the phone is in stand by mode, never got fixed, and if you use art runtime you have to wait more than 3 minutes to have your devices booted up. Cyanogenmod developers could theach Motorola engineers how to resolve this. That's absurd to me.
Moto Maxx have no custom ROMs, no custom kernel, I wish I could do something to change this scenario, but I know nothing about programing. I'm trying hard to like this phone, but it is quite difficult right now, no community, no fast updates, lags, bugs, and the Snapdragon 805 hate the heat so much that the phone appears to be using a low cost processor when it gets hot even when it's not on heavy usage, and I'm not talking about the soak test, I experienced problems since KitKat, looks like they don't care at all. Right now I'm very frustrated, I regret a lot buying this phone and I can't even find anyone willing to buy it, Motorola needs a better development team, cause if things keep going this way, I'll never buy another Motorola device.
Click to expand...
Click to collapse
Sorry about your phone. That's not how my two Moto Maxx phones act.
* I don't wait 3 minutes to have my device boot up. Maybe you got a lemon? If your phone is taking over 45 seconds to boot, something is wrong with your phone. My main phone (on Dalvik) boots in 45 seconds with over 300 apps. I just timed it; and that includes the time it takes to unlock the security code.
My second Moto Maxx (on ART) boots in 20 seconds to desktop from the time I hit the power button. Here's a video proving it:
MOTO MAXX BOOTING ON ART
https://www.youtube.com/watch?v=7Swf3rS6-vc
Somebody asked me to make the video because the CDMA Droid Turbo XT1254 has some kind of ART problem, which the "international" Moto Maxx XT1225 seemingly does not. But this proves the Moto Maxx XT1225 boots extremely fast not only on Dalvik but on ART also.
One phone has all my apps installed (over 300), the other does not as I'm keeping it in "new in the box" condition to sell with even the screen protector on. I only take it out to compare to my first phone when necessary. But with two phones, neither even over a minute, shows something is wrong with your phone.
* My battery lasts so much longer than my Nexus 5. Well, it's a bigger battery! Haven't noticed any quick drain. But maybe that's because my Nexus 5 battery was too small and this one is great by comparison.
* Haven't noticed the heat of the Snapdragon 805, but I have heard complaints about the Snapdragon 810. I use a Tech21 case, so maybe I'm just not feeling the heat.
* A dev -- @Skrilax_CZ --in this forum is working on CM12 for us.
Until then, I'm running my daily phone on Dalvik with xposed/Gravity Box toolkit. There is the custom ROM you are looking for...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Although standby drain could be better, mine isn't too bad. How strong is the signal in your area? Are you leaving Bluetooth, auto sync, etc on? Have you tried a factory reset as a last resort?
2. It's a soak test, not the final software. No one knows for sure the reason for the delay in rolling it out, but some of the bugs may be fixed or resolved in the official update (which could be 5.1).
3. I would never buy a phone on the premise that it would get strong developer support. It's something that's tough to guarantee unless you know for definite that devs are getting the phone. In this instance I agree that Moto take some of the blame here for not releasing the Maxx worldwide, but then again it's not their duty to ensure any device of theirs has strong 3rd party support.
RaphaDL said:
This device is amazing, or at least was supposed to be. Almost stock android, a good camera, a ridiculously strong chipset, gorgeous screen and tremendous battery capacity.
What could possibly make this phone be anything but awesome? The software!
Motorola may have been on the right direction with these almost pure Android devices and their smart and functional features, but they should urgently look out for some software issues.
1- KitKat on Moto Maxx have a huge battery drain problem when the phone is in stand by mode, never got fixed, and if you use art runtime you have to wait more than 3 minutes to have your devices booted up. Cyanogenmod developers could theach Motorola engineers how to resolve this. That's absurd to me.
2- I'm on the soak test, the super anticipated lollipop, I thought Motorola was leaving KitKat full of bugs to work better on lollipop, but now I have lollipop and things did not get better, I can't and I won't talk about it in details, but it is ridiculous. I had a Galaxy S2, a Galaxy S3 and after that I had a LG G2, though LG and Samsung used to make we wait a lot for updates I saw Cyanogenmod, paranoid, etc ROMs getting around bugs on their alpha and beta ROMs a lot faster then the official Motorola engineers, and I assume they are being well paid by Motorola to work on it.
Moto Maxx have no custom ROMs, no custom kernel, I wish I could do something to change this scenario, but I know nothing about programing. I'm trying hard to like this phone, but it is quite difficult right now, no community, no fast updates, lags, bugs, and the Snapdragon 805 hate the heat so much that the phone appears to be using a low cost processor when it gets hot even when it's not on heavy usage, and I'm not talking about the soak test, I experienced problems since KitKat, looks like they don't care at all. Right now I'm very frustrated, I regret a lot buying this phone and I can't even find anyone willing to buy it, Motorola needs a better development team, cause if things keep going this way, I'll never buy another Motorola device.
Click to expand...
Click to collapse
1) I'm agree with the battery problem, I come from a Nexus 5 who barely had 1%-2% battery drain over night, and then comes the Maxx with around 15% battery drain overnight, but I have discovered that this is because of the sensors and the GPS accuracy. The biggest drain here is "wave to silence" and "approach to display" functions, under the "Actions" on Moto application. When I disabled those, half of my drain was no more. Besides this, put the location on "Battery Saving", it makes a great difference with "High Accuracy". I'm always reaching around 40hrs on battery and at least 4hrs on screen with just this little changes, everything else is activated and synced all the time.
2) I can't talk about Lollipop, no idea when is coming to my device.
3) About ROM's and kernels, we should wait, there device is still "new" in the market and is not widespread, maybe the launch in India would give us more developers and people who want to participate on this device.
The device is really good, but if you are into customization and ROM's, maybe you should picked the Nexus 6. For me, stock ROM is enough.
About the heat, try to run any benchmark 3 times in a row. Or play a heavy game for more than 15 minutes. Or try to play a game while you charge the phone with it's fast charger. You feel your phone getting slower and slower.
About the battery, as I said, I used to own a LG G2, a 3000mah battery phone. And it's battery life was better on stand by. Overnight my Moto Maxx loses almost 10% of juice, while the G2 used to lose only 2% on the same condition. And I saw a lot of people with this same problem. Having in mind that the Moto Maxx has a 3900mah this is unacceptable.
About ART, well, I can't reproduce my tests anymore cause I'm on lollipop, but when I was using ART on KitKat my phone used to load up all my apps "Updating system" like on every single boot, and I asked other people to reproduce the test and their phone behavior was exactly equal, so maybe the fact that your phone is almost unused is causing you not to feel this problem.
About custom ROMs, I'm waiting for CM12! I emailed the dev already saying that I'm willing to give any help or donation he needs.
RaphaDL said:
About ART, well, I can't reproduce my tests anymore cause I'm on lollipop, but when I was using ART on KitKat my phone used to load up all my apps "Updating system" like on every single boot, and I asked other people to reproduce the test and their phone behavior was exactly equal, so maybe the fact that your phone is almost unused is causing you not to feel this problem.
Click to expand...
Click to collapse
Well, I posted a video to prove the fast boot time for ART. 20 seconds. True that phone only has stock apps.
My other phone with 322 apps takes 45 seconds to boot, and yes it's on Dalvik.
OK, here's what I will do. I will make a new TWRP backup. I will uninstall all my xposed modules, switch temporarily to ART, and boot. Not sure if I will be able to make a video here while at work, but I can time it. Will post results back.
Then, I'll restore my backup.
ChazzMatt said:
Well, I posted a video to prove the fast boot time for ART. 20 seconds. True that phone only has stock apps.
My other phone with 322 apps takes 45 seconds to boot, and yes it's on Dalvik.
OK, here's what I will do. I will make a new TWRP backup. I will uninstall all my xposed modules, switch temporarily to ART, and boot. Not sure if I will be able to make a video here while at work, but I can time it. Will post results back.
Then, I'll restore my backup.
Click to expand...
Click to collapse
Thank you, dude, but you don't need to go through all this trouble. I tested it on 3 Moto Maxx with KitKat and the 3 presented the exactly same problem.
And that's not much of a problem since Lollipop doesn't have this behavior and it uses ART. I just brought that up to illustrate how behind Motorola are when the subject is software.
RaphaDL said:
[B
About ART, well, I can't reproduce my tests anymore cause I'm on lollipop, but when I was using ART on KitKat my phone used to load up all my apps "Updating system" like on every single boot, and I asked other people to reproduce the test and their phone behavior was exactly equal, so maybe the fact that your phone is almost unused is causing you not to feel this problem.
.
Click to expand...
Click to collapse
ChazzMatt said:
Well, I posted a video to prove the fast boot time for ART. 20 seconds. True that phone only has stock apps.
My other phone with 322 apps takes 45 seconds to boot, and yes it's on Dalvik.
OK, here's what I will do. I will make a new TWRP backup. I will uninstall all my xposed modules, switch temporarily to ART, and boot. Not sure if I will be able to make a video here while at work, but I can time it. Will post results back.
Then, I'll restore my backup.
Click to expand...
Click to collapse
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
_______
EDIT: I was still on Dalvik. ARghhh. ART will not stick. Trying to figure out why.
ChazzMatt said:
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
Click to expand...
Click to collapse
On what country you bought your phone? Maybe that's something related to Brazilian Moto Maxx only. I really wish I have recorded in video the tests I made.
ChazzMatt said:
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
Click to expand...
Click to collapse
Hmmmm.... I'm having a hard time making ART stick. I've uninstalled all my xposed modules, but every time I reboot it's back on Dalvik. Anyone have any ideas?
Art dont work well in kitkat, maybe you should try Lollipop, for custom roms, need found more devs with devices, cm 12 comes in some times, but of have more devs maybe we have some kernels
matheus_sc said:
Art dont work well in kitkat, maybe you should try Lollipop, for custom roms, need found more devs with devices, cm 12 comes in some times, but of have more devs maybe we have some kernels
Click to expand...
Click to collapse
Maybe we should gather some money and donate a device to someone. What you guys think?
ChazzMatt said:
On ART (xposed apps disabled) my main phone with over 300 apps takes 30 seconds to boot to desktop. Something is wrong with your phone.
I'll make a video later.
_______
EDIT: I was still on Dalvik. ARghhh. ART will not stick. Trying to figure out why.
Click to expand...
Click to collapse
OK, I was wrong. ART sucks on KitKat. I finally got ART to stick by flashing the xposed disable zip. Switched to ART, and it went through the initial several minute upgrade for 307 apps. (I had unintalled all my xposed modules).
But now when I turn off the phone and boot back up, still takes several minutes to "optimize" 180 apps. EVERY TIME. MORE than 3 minutes -- more like TEN MINUTES every time.
So, after this third time of ART boot up, when it finishes, I'm restoring my TWRP backup to go back to Dalvik so I can boot up in 45 seconds! :laugh:
Nothing is wrong with your phone for the slow boot up, except you are on ART...
If Lollipop is this way, I'm sticking to Kitkat 4.4.4 and Gravity Box.
ChazzMatt said:
OK, I was wrong. ART sucks on KitKat. I finally got ART to stick by flashing the xposed disable zip. Switched to ART, and it went through the initial several minute upgrade for 307 apps. (I had unintalled all my xposed modules).
But now when I turn off the phone and boot back up, still takes several minutes to "optimize" 180 apps. EVERY TIME. MORE than 3 minutes -- more like TEN MINUTES every time.
So, after this third time of ART boot up, when it finishes, I'm restoring my TWRP backup to go back to Dalvik so I can boot up in 45 seconds! :laugh:
Nothing is wrong with your phone for the slow boot up, except you are on ART...
If Lollipop is this way, I'm sticking to Kitkat 4.4.4 and Gravity Box.
Click to expand...
Click to collapse
Exactly.
Lollipop doesn't have this problem, relax. But I'm bringing this problem here just to bring attention to the fact that Motorola have awful software management.
Huge battery, but even bigger battery drain.
Smart features, but no flexibility, why can't we program the sensors to work only when there is a notification to be showed? Why we have to leave the sensors on ALL THE TIME even when we are not using it at all?
Updated software, but small problems that even independent developers are able to get around on other devices. And other than that we can see some incompatibilities, and I'm not taking about soak test, the Moto X 2014 Lollipop bring no integration between Lollipop lockscreen features and Moto benefits.
Motorola must urgently give more attention to the software on their smartphones.
And,guys,we have the same hardware as the Nexus 6, there's absolutely no reason for Motorola not take advantage of that.
RaphaDL said:
Exactly.
Lollipop doesn't have this problem, relax. But I'm bringing this problem here just to bring attention to the fact that Motorola have awful software management.
Huge battery, but even bigger battery drain.
Smart features, but no flexibility, why can't we program the sensors to work only when there is a notification to be showed? Why we have to leave the sensors on ALL THE TIME even when we are not using it at all?
Updated software, but small problems that even independent developers are able to get around on other devices. And other than that we can see some incompatibilities, and I'm not taking about soak test, the Moto X 2014 Lollipop bring no integration between Lollipop lockscreen features and Moto benefits.
Motorola must urgently give more attention to the software on their smartphones.
And,guys,we have the same hardware as the Nexus 6, there's absolutely no reason for Motorola not take advantage of that.
Click to expand...
Click to collapse
Just disable everything under Actions on the Moto app except for the camera, and you should be fine.
It will work as you wanted, just show the notifications where there is one. I have my Maxx since few months like that and it is much better than with those activated. It is annoying besides that everything would turn your screen on.
That would help with the battery drain also.
:fingers-crossed:
Galaxo60 said:
Just disable everything under Actions on the Moto app except for the camera, and you should be fine.
It will work as you wanted, just show the notifications where there is one. I have my Maxx since few months like that and it is much better than with those activated. It is annoying besides that everything would turn your screen on.
That would help with the battery drain also.
:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the tip, but I already tried this.
The movement sensors still turned on all the time, it just disable the waving gesture features. When in a car the screen still turn on every time the car moves, even if there's no notification, also turn on when over a table and the table moves, or over my leg and my leg moves. My point is, sensors still on and for nothing. I would turn this completely off if we had a notification led, but we don't, so I can't.
RaphaDL said:
Motorola must urgently give more attention to the software on their smartphones.
And,guys,we have the same hardware as the Nexus 6, there's absolutely no reason for Motorola not take advantage of that.
Click to expand...
Click to collapse
RaphaDL said:
The movement sensors still turned on all the time, it just disable the waving gesture features. When in a car the screen still turn on every time the car moves, even if there's no notification, also turn on when over a table and the table moves, or over my leg and my leg moves. My point is, sensors still on and for nothing. I would turn this completely off if we had a notification led, but we don't, so I can't.
Click to expand...
Click to collapse
Yes, I greatly miss the notification LED from my Nexus 5.
But Nexus 6 is not an option for me. And thank you for reminding people we have the EXACT same hardware as the Nexus 6 and made by the EXACT same company. Motorola has no excuses.
RaphaDL said:
Thanks for the tip, but I already tried this.
The movement sensors still turned on all the time, it just disable the waving gesture features. When in a car the screen still turn on every time the car moves, even if there's no notification, also turn on when over a table and the table moves, or over my leg and my leg moves. My point is, sensors still on and for nothing. I would turn this completely off if we had a notification led, but we don't, so I can't.
Click to expand...
Click to collapse
Hello Rapha in below theme you can find how to make works the notification led that all we have on our moto maxx devices, Im using it right now
http://forum.xda-developers.com/droid-turbo/general/notification-led-t2960203/page2
Hi to every lucky body that get android 7 final.i made this topic to share your results in android 7 and compare with yours in android 6..like camera..battery..speed..tanx and hope to be usefull and active topic??????
Sent from my Nexus 5X using Tapatalk
Well, it's a tiny bit snappier, and a tiny bit faster overall.
The battery is better; I get 3:45 to 4 hours SOT in auto brightness, full location services with wireless scanning, google now on, google cards on, hot word on from any screen... the full google experience, for short.
It's better than I had with a variety of mods and ROMs on Marshmallow.
I especially enjoy the new notification center. I can read numerous full messages and emails right from the notification slide. Quite awesome.
And I thank the gods of Google for removing the stupid enlarged tiles for Wireless and Bluetooth, the most annoying feature ever.
Battery is not bad for stock but I get the feeling with all mods and tweaks and kernels and such android M was a bit better...
But it would be unfair to compare those two as M has been worked on for a year now... N is fresh out of the box so let's wait and see how much battery can be improved.
Other than that N is very fluent and fast. Up to now also very stable and offers some important options that used to be mods some years ago.
Camera... And such... Did not really compare but would expect them to be similar...
Starship706 said:
Other than that N is very fluent and fast. Up to now also very stable and offers some important options that used to be mods some years ago.
Click to expand...
Click to collapse
I haven't tried N yet, but I was reading a comment on Slashdot that led me to believe, that it included something similar to CM13 privacy manager ? Is this true? Do you now get to choose what apps get access to? Can you block them from wireless, cellular data?
^ This feature alone made me upgrade the wife's and kids tablets from Nexus 7s to Nexus 7 (2013)s so I could put them on CM13.
OhioYJ said:
I haven't tried N yet, but I was reading a comment on Slashdot that led me to believe, that it included something similar to CM13 privacy manager ? Is this true? Do you now get to choose what apps get access to? Can you block them from wireless, cellular data?
^ This feature alone made me upgrade the wife's and kids tablets from Nexus 7s to Nexus 7 (2013)s so I could put them on CM13.
Click to expand...
Click to collapse
No, but you can do that from Data Usage in Settings, in M as well.
I've been using it for 2 days now. The doze feature is way better than that of M. I've noticed certain performance boost in games like asphalt 8 as the game used to lag after thermal throttling was active in M.
The usage is very very smooth, feels very light. I mostly love the quick settings panel as because it looks and is well organised than the previous version. It's just an initial build and its quite stable. I would say I am impressed and good to go with 7.0.
Well this was my perspective.
I think charging while screen is on is improved. Can someone confirm?
eatsleep said:
I think charging while screen is on is improved. Can someone confirm?
Click to expand...
Click to collapse
Not entirely sure... NExus 5x has quite some struggle with charging when screen on.
Under M there was almost no charging when screen was on and you did some browsing...
Might be slightly better under N... though I havent tested it long enough to confirm... Charging basically stopped when you used your phone constantly and not just for writing a text under M...
Nope, seems same like before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: it actually seems better, I'm using my phone on charger for about 10mins, and ampere measures around 1100mAh.
On MM it wouldn't go to more than 300mAh while screen on.
Sent from my Nexus 5X using Tapatalk
Nightshadow931 said:
Nope, seems same like before.
Edit: it actually seems better, I'm using my phone on charger for about 10mins, and ampere measures around 1100mAh.
On MM it wouldn't go to more than 300mAh while screen on.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I tested it while playing a game (8 ball pool, not a resource intensive app) and the percentage went up atleast 2 to 3 % in roughly 5-10 minutes. It seems that it is improved. But we still need someone to look through the kernel's code or run a reliable test!
I have it on my 5x since it dropped was on dp5 before that. Official seems smoother don't really use the 5x since I got the s7.
I'm actually seeing what seems to be worse battery performance. I've eliminated a few apps that were troublesome, but it looks like the battery is draining faster than on "M". I'm hoping that it's simply a problem with the crappy cell signal in my office - my connection bounces between 27 different towers and it's still crappy at best.
Atleast for me, I can confirm that charging while screen on is finally fixed. Hail hydra!
As previously stated, it feels a lot snappier and lighter being on Nougat as opposed to Marshmallow. Quick Settings are better overall, especially when you're able to add custom quick tiles via apps in the Play Store. Only complaint about the Quick Settings is that the Wifi and Bluetooth used to toggle on press, then open mini settings when you clicked the text. Now it just opens mini settings. I can get used to that, though.
Oh, and I still hate the white background in the settings app. Haven't found any Layers themes that work well yet. If anybody else finds one, let me know.
lightningdude said:
As previously stated, it feels a lot snappier and lighter being on Nougat as opposed to Marshmallow. Quick Settings are better overall, especially when you're able to add custom quick tiles via apps in the Play Store. Only complaint about the Quick Settings is that the Wifi and Bluetooth used to toggle on press, then open mini settings when you clicked the text. Now it just opens mini settings. I can get used to that, though.
Oh, and I still hate the white background in the settings app. Haven't found any Layers themes that work well yet. If anybody else finds one, let me know.
Click to expand...
Click to collapse
Just rooted the final N and put Substratum and Mono Theme on. Settings awesomely dark with other theme goodies.
new useful features, more usr friendly interface, for me - good change
enzo_cz said:
Just rooted the final N and put Substratum and Mono Theme on. Settings awesomely dark with other theme goodies.
Click to expand...
Click to collapse
How did you get Substratum working?
bhs73 said:
How did you get Substratum working?
Click to expand...
Click to collapse
Upon getting my phone rooted I downloaded it from PlayStore, installed, did the permissions, insalled Mono theme and that was it.
enzo_cz said:
Upon getting my phone rooted I downloaded it from PlayStore, installed, did the permissions, insalled Mono theme and that was it.
Click to expand...
Click to collapse
Oh, that easy? Thanks man, I owe you a beer.
bhs73 said:
Oh, that easy? Thanks man, I owe you a beer.
Click to expand...
Click to collapse
Important, there are sorta probs about Substratum and Android N, such as make sure you wont apply it to Chrome and Documents for example. You'd get instant force close. And if there's any other app like that, you need to make sure it is off the list to get themed.
Now that the Android 7.0 factory images have been released and most (all?) of the custom ROM & kernel devs are jumping to Nougat, I'm actually missing Marshmallow.
Nougat has some a few interesting features, but it seems like Marshmallow is more stable and is faster (& maybe better battery life too). Maybe this is because the N6 is a 2+ year old device now.
All these new custom ROMs are popping up with "base" versions, lacking much of the functionality they had in Marshmallow. Obviously, that will change over time.
But it leaves me feeling a little empty. I like Marshmallow. It runs well on my device. There are a few apps I use that haven't been updated to Nougat yet and are incompatible. And it leaves me sad to see that development has effectively stopped for MM, even though Google continues to release updates.
I have experimented with building ROMs in the past (Pure Nexus, Dirty Unicorns). Maybe I'll have to learn how to actually build a ROM from scratch to fill this void. Or stick to the "boring" factory images LOL.
I think nougat actually lasts longer. My experience might not be indicative of yours so that's just my opinion. Maybe wait for the apps to get optimized for nougat as well? It might be too early to judge I think
Sent from my pixel using XDA-Developers mobile app
So far I like M better...
Pros and Cons
Would be nice to have a Pros and Cons section. If you post yours I will update the table here.
M Pros (N Cons):
=============
Adaway works out of the box
All root file managers can access the system files.
Xposed.
Layers don't work in N
Faster notifications
Working hotspot hack
Mature GPS (problems reported in Nougat)
N Pros (M Cons):
=============
More updated security patches.
Quick toggles with one swipe.
Keyboard shows numbers on top if entering a password.
Doze (debatable if it is useful or an improvement over M)
Smoother with better battery life? (very questionable!!)
Display can be resized
Saturation of the colors can be changed
Good looking and more functional notifications
najoor said:
Would be nice to start a Pros and Cons section. If you post yours I will update the table here.
M Pros (N Cons):
=============
Adaway works out of the box
All root file managers can access the system files.
N Pros (M Cons):
=============
?
Click to expand...
Click to collapse
For AdAway to run on N you need to flash the systemless host file, then install AdAway and it works.
I think with each in every Android update this always happens. You can choose to wait to update if you want everything to work like you had it, or you can update then wait for everything else to catch up. The choice is yours. I like to update to the newest OS to see what Google has been working on. Everything will work eventually. If you prefer M then stick to it, sooner or later you will need to update to get the latest security.
Datsun.510 said:
For AdAway to run on N you need to flash the systemless host file, then install AdAway and it works.
I think with each in every Android update this always happens. You can choose to wait to update if you want everything to work like you had it, or you can update then wait for everything else to catch up. The choice is yours. I like to update to the newest OS to see what Google has been working on. Everything will work eventually. If you prefer M then stick to it, sooner or later you will need to update to get the latest security.
Click to expand...
Click to collapse
That is what I meant by "out of the box". Adaway always worked with every previous release. This is the first time you need to flash something to make it work.
I will add security to the Cons for M.
What else do you like about N?
najoor said:
That is what I meant by "out of the box". Adaway always worked with every previous release. This is the first time you need to flash something to make it work.
I will add security to the Cons for M.
What else do you like about N?
Click to expand...
Click to collapse
Quick panel on the status bar without having to swipe twice. Of course with customs roms you can do smart pull down right or left, also now you can edit the layout without needing a custom ROM.
I like the fact that the you dont have to use the quick tiles and they are just toggles as they should be. There is no good reason a toggle needs to be that big. It was one of the worst changes Google made. Guess they hear enough complaining.
The new doze feature does seem ti be working but it is not helpful as it kinda defeats the purpose of an always connected device.
Other then that I cant say it is really better.
zelendel said:
I like the fact that the you dont have to use the quick tiles and they are just toggles as they should be. There is no good reason a toggle needs to be that big. It was one of the worst changes Google made. Guess they hear enough complaining.
The new doze feature does seem ti be working but it is not helpful as it kinda defeats the purpose of an always connected device.
Other then that I cant say it is really better.
Click to expand...
Click to collapse
Yes that's what I meant. Quick toggles with one swipe. Also keyboard now shows numbers on top if entering a password.
Datsun.510 said:
Yes that's what I meant. Quick toggles with one swipe. Also keyboard now shows numbers on top if entering a password.
Click to expand...
Click to collapse
Can't say anything about the keyboard. I have never nor will I ever use Google's keyboard.
I actually like Nougat better. I feel it's faster in installing apps smoother overall better battery and a refreshing new ui. Like the jump from kitkat to lollipop. U better learn how to compile because i have been using dirty unicorns 7.0 and its just:good: . I cannot talk about stock os maybe that's why our experiences differ?
Still on Marshmallow and plan on being on it for the foreseeable future. Do not see anything in Nougat that is game changing enough for me to change up right now.
And I also think it is to early to pass judgement between the two. Marshmallow has been around for over a year and therefore devs have had the opportunity to create, test, and mod it to perfection. It is tried and tested at this point. I imagine this same topic comes up whenever a major update comes along. Nougat is still new. In 6 months time, Nougat will be in the process of becoming just as stable and customized as Marshmallow is now. Also keep in mind that Marshallmallow is still barely on that many devices and is still very current and up to date.
Another big deciding factor for me is Xposed. I run a couple Instagram accounts which requires me to post stuff that nobody else has. I acquire that material thru Xposed modules. Also with minminguard, Youtube background playback and ad remover, and Greenify Xposed version, I can't imagine moving on without it. I do not plan on moving on to 7.x until Xposed is updated for it, as well as the modules I use. Keep in mind that this may never come, as Xposed updates are not guaranteed.
In short, I am perfectly fine with staying with Marshmallow. Latest updates from my favorite ROM are from September and as time goes by, being open source, I can merge latest security fixes and build it myself if need be.
PS: I have not even tried Nougat at all. Not even developer previews. Just do not see any valid reason to do so in comparison to Marshmallow.
christianpeso said:
Still on Marshmallow and plan on being on it for the foreseeable future. Do not see anything in Nougat that is game changing enough for me to change up right now.
And I also think it is to early to pass judgement between the two. Marshmallow has been around for over a year and therefore devs have had the opportunity to create, test, and mod it to perfection. It is tried and tested at this point. I imagine this same topic comes up whenever a major update comes along. Nougat is still new. In 6 months time, Nougat will be in the process of becoming just as stable and customized as Marshmallow is now. Also keep in mind that Marshallmallow is still barely on that many devices and is still very current and up to date.
Another big deciding factor for me is Xposed. I run a couple Instagram accounts which requires me to post stuff that nobody else has. I acquire that material thru Xposed modules. Also with minminguard, Youtube background playback and ad remover, and Greenify Xposed version, I can't imagine moving on without it. I do not plan on moving on to 7.x until Xposed is updated for it, as well as the modules I use. Keep in mind that this may never come, as Xposed updates are not guaranteed.
In short, I am perfectly fine with staying with Marshmallow. Latest updates from my favorite ROM are from September and as time goes by, being open source, I can merge latest security fixes and build it myself if need be.
PS: I have not even tried Nougat at all. Not even developer previews. Just do not see any valid reason to do so in comparison to Marshmallow.
Click to expand...
Click to collapse
I'm in the same situation as well. I am probably also one of the few who has never ran Nougat. I'm at a point right now where I need everything stable and working as life has been very busy lately. I also will be staying with Marshmallow until a very stable version of Nougat comes out, esp since I have to change over the radio and bootloader.
I also use Xposed heavily and the current themes that I have..... I don't want to do without just to have the latest version. I'll wait until next year if I have to if thats how long it takes to get Nougat up and running with fully supported Xposed as well.
mikeprius said:
I'm in the same situation as well. I am probably also one of the few who has never ran Nougat. I'm at a point right now where I need everything stable and working as life has been very busy lately. I also will be staying with Marshmallow until a very stable version of Nougat comes out, esp since I have to change over the radio and bootloader.
I also use Xposed heavily and the current themes that I have..... I don't want to do without just to have the latest version. I'll wait until next year if I have to if thats how long it takes to get Nougat up and running with fully supported Xposed as well.
Click to expand...
Click to collapse
I'm a grown-up old dude, and I don't really use my phone like most kids nowadays, my social network footprint is like a lil lovebird. I think I post more here than any other web forum/social place. But i feel my battery is a lot better, not just a bit but a lot, the phone seems faster and snappier, and the only thing I miss from Xposed is blocking adds in YouTube, most of the time you can skip those so not a biggie, and YouTube screen off playback module. Everything else seems better to me on Nougat and I didn't felt the same from LP to MM. I mostly flash aosp Roms or stock based which probably adds to my perception. I know that cm is basically based on aosp like anything Android.
At the time of GB custom Roms were the rule for me cause plain Android lacked many features that cm and others had, but as I grew older I seem to be running less custom options on my phone and have less patience than before to deal with sod, reboots, and such. I still experiment, and when there's something really new I'll flash my phone, but seems I always end up running some kind of aosp/modified stock rom.
If you want a lot of options and customization, stay on MM. Like every other update before this custom roms haven't catch up but it will get there and we'll have this same conversation around October next year.
Probably not on this parts of XDA.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also there's this, for some weird reason I like this crap, lol, I'm a dog person, have a mini pinch and a pitbull.
Sent from my Nexus 6 using Tapatalk
I am a fan of N and have been since the July 18th NDP5. I like the lock screen notifications much better. I like and use split screen (not all the time but when I need it, it works perfect and easy) . I am becoming a bigger fan of security and things being more locked down. The things we really need will come in time they always do (it did just come out). I have always gotten good battery life and still do. I think the stock N is getting much better than stock MM. I like Android Pay so I am actually trying to live with no root on PureNexus, I do really miss adaway the most and being able to substratum the lock screen notifications. But at the end of the day I am fine with it for now.
Overall I am glad to be on N and believe it will get much better once we get 7.1 and higher.
FCORivers said:
I'm a grown-up old dude, and I don't really use my phone like most kids nowadays, my social network footprint is like a lil lovebird. I think I post more here than any other web forum/social place. But i feel my battery is a lot better, not just a bit but a lot, the phone seems faster and snappier, and the only thing I miss from Xposed is blocking adds in YouTube, most of the time you can skip those so not a biggie, and YouTube screen off playback module. Everything else seems better to me on Nougat and I didn't felt the same from LP to MM. I mostly flash aosp Roms or stock based which probably adds to my perception. I know that cm is basically based on aosp like anything Android.
At the time of GB custom Roms were the rule for me cause plain Android lacked many features that cm and others had, but as I grew older I seem to be running less custom options on my phone and have less patience than before to deal with sod, reboots, and such. I still experiment, and when there's something really new I'll flash my phone, but seems I always end up running some kind of aosp/modified stock rom.
If you want a lot of options and customization, stay on MM. Like every other update before this custom roms haven't catch up but it will get there and we'll have this same conversation around October next year.
Probably not on this parts of XDA.
Also there's this, for some weird reason I like this crap, lol, I'm a dog person, have a mini pinch and a pitbull.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I get having everything work, that's one thing that stock Google Android offers is there are minimal bugs vs. custom ROMs. I'm used to a lot of features trying to do without gets to me. One issue is all the ad related things like youtube and Ad away so I use those mods. Plus minminguard. Also some things like the notification light and disabling heads up/toast notifications.
I'll wait until Chroma or DU drops N then I may try it. I'm using DU's latest M ROM and it works 100%.
What is that screenshot of ? the animals ?
mikeprius said:
I get having everything work, that's one thing that stock Google Android offers is there are minimal bugs vs. custom ROMs. I'm used to a lot of features trying to do without gets to me. One issue is all the ad related things like youtube and Ad away so I use those mods. Plus minminguard. Also some things like the notification light and disabling heads up/toast notifications.
I'll wait until Chroma or DU drops N then I may try it. I'm using DU's latest M ROM and it works 100%.
What is that screenshot of ? the animals ?
Click to expand...
Click to collapse
That's the cat game in Nougat.
Thanks for the feedback everyone. Maybe I'll do a build of Pure Nexus 7.0 and give it another try. I see recent commits for controlling the LED!
Sent from my Nexus 6 using XDA Labs
najoor said:
.....
Smoother with better battery life? (very questionable!!)
Click to expand...
Click to collapse
After a few days Nougat on my N6 I think that Marshmallow consumed less battery power.
My battery usage is on par with what I had on MM on the MOBXXX roms, the older roms were better, but MOB was snappier.
I like that the QS tiles can be arranged now without the tuner, the new controls on the first swipe, and the new notifications. Also the much shorter optimizing apps time.
So I wouldn't go back
I also think marshmallow is faster and more fluid. Let's see what happens with 7.1.
Sent from my Nexus 6 using Tapatalk
It seems that my LG G4 has finally died.
It all began a couple of weeks ago when my G4 suddenly crashed while I was using it. The screen turned black and it didn't restart itself. So I turned it back on and there it was, a nice endless bootanimation. The phone did nothing else than bootlooping.
But I am not someone who gives up easily so I tried to boot into TWRP, which booted up successfully and I formatted the whole phone. I started up LG UP to restore my phone with a clean KDZ to see if it would boot up. And yes it did and seemed to work properly so I thought maybe I had some bad luck. But unfortunately after a couple of days the same thing happend again. I booted up TWRP again and tried an AOSP based ROM instead of a LG Stock ROM to see if the same thing would happen again. And yes eventually the same thing happend again.
It seems that my G4 finally turned into a bootlooping brick. I give up. I've had a really nice 3 years with this device even with all the problems it had. I absolutely loved it's camera, that's what mostly kept me to use this device. But I am not planning to buy an other LG device anytime soon, beside all the nice features this device has, like a SD-Card slot, removable battery and the awesome camera, they simply do not make up for all the problems this device has. It's an absolute shame because it could have been the perfect phone for many years. But LG's bad update policy, quality control and support made me to decide to step away from LG. For now I'll be using my old Nexus 5 for a while as a daily driver till I can afford a new device. I want to thank all the dev's for their efforts and time they spend in their awesome work, you've have made and gave us many awesome Mods, Kernels and ROMs to try and enjoy.
Good bye.
what's the build number?
BoyBawang2 said:
what's the build number?
Click to expand...
Click to collapse
The S/N is 506 and to make it even worse it has been repaired once already.
Mr.FREE_Bird said:
It seems that my LG G4 has finally died.
It all began a couple of weeks ago when my G4 suddenly crashed while I was using it. The screen turned black and it didn't restart itself. So I turned it back on and there it was, a nice endless bootanimation. The phone did nothing else than bootlooping.
But I am not someone who gives up easily so I tried to boot into TWRP, which booted up successfully and I formatted the whole phone. I started up LG UP to restore my phone with a clean KDZ to see if it would boot up. And yes it did and seemed to work properly so I thought maybe I had some bad luck. But unfortunately after a couple of days the same thing happend again. I booted up TWRP again and tried an AOSP based ROM instead of a LG Stock ROM to see if the same thing would happen again. And yes eventually the same thing happend again.
It seems that my G4 finally turned into a bootlooping brick. I give up. I've had a really nice 3 years with this device even with all the problems it had. I absolutely loved it's camera, that's what mostly kept me to use this device. But I am not planning to buy an other LG device anytime soon, beside all the nice features this device has, like a SD-Card slot, removable battery and the awesome camera, they simply do not make up for all the problems this device has. It's an absolute shame because it could have been the perfect phone for many years. But LG's bad update policy, quality control and support made me to decide to step away from LG. For now I'll be using my old Nexus 5 for a while as a daily driver till I can afford a new device. I want to thank all the dev's for their efforts and time they spend in their awesome work, you've have made and gave us many awesome Mods, Kernels and ROMs to try and enjoy.
Good bye.
Click to expand...
Click to collapse
Just flash kernel with big cores disabled and you can still use your device afterwards.
tulen_kobi said:
Just flash kernel with big cores disabled and you can still use your device afterwards.
Click to expand...
Click to collapse
Nahh thanks for the suggestion but beside that it will make the phone pretty slow it still has it's problems. So in my eyes it's not worth it.
Mr.FREE_Bird said:
Nahh thanks for the suggestion but beside that it will make the phone pretty slow it still has it's problems. So in my eyes it's not worth it.
Click to expand...
Click to collapse
I would recommend to do it just to have a backup phone if anything goes wrong with the new one or you can repurpose it as a camera or media player.
tulen_kobi said:
I would recommend to do it just to have a backup phone if anything goes wrong with the new one or you can repurpose it as a camera or media player.
Click to expand...
Click to collapse
Well now you brought me on some idea's :good:, might just use that method to still be able to use my device as a camera. That's what I love the most of the LG G4.
Its not that bad on disabled cores. My first G4 was a faulty one I got very cheap and just disabled the cores to get it working. It did die eventually though. I loved the phone so much that I got a new one with 701 s/n. Wasn't so much faster as I was expecting.. Going strong since !
Mr.FREE_Bird said:
The S/N is 506 and to make it even worse it has been repaired once already.
Click to expand...
Click to collapse
If you don't mind .. I would love to use your device as a testing device. If you have some free time and wanting to help me with my unofficial unlock.. I need to test a thing which may convert the device or makes it completely bricked. But as you said it's dead for you anyways.. So.. Let me know
Sent from my LG-H815 using XDA Labs
ezzony said:
Its not that bad on disabled cores. My first G4 was a faulty one I got very cheap and just disabled the cores to get it working. It did die eventually though. I loved the phone so much that I got a new one with 701 s/n. Wasn't so much faster as I was expecting.. Going strong since !
Click to expand...
Click to collapse
I did notice a pretty big difference, especially when I'm multitasking/switching apps. Tried the big cores disable method a while ago just to see how big the difference would be. It doesn't make the device unusable slow but I do need more speed to use it as a daily driver. And I don't really trust my G4 since it became more unstable while time passed. So that's why I'm back to my Nexus 5 for now. And I'm not planning to send back my device to repair it again or for an replacement because I'm pretty much done with LG for now.
steadfasterX said:
If you don't mind .. I would love to use your device as a testing device. If you have some free time and wanting to help me with my unofficial unlock.. I need to test a thing which may convert the device or makes it completely bricked. But as you said it's dead for you anyways.. So.. Let me know
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I would love to help, really appreciate all the work you have done. Tomorrow I will have free time to help and test. And I'm not afraid to brick my device. If I brick it I can still use it for spare parts because my sister has a G4 to and she cracked it's screen. So it won't be wasted if things go wrong. :good:
Why you just dont send it to LG service so it get fixed? It is still really good phone, so dont give up yet.
Juujika said:
Why you just dont send it to LG service so it get fixed? It is still really good phone, so dont give up yet.
Click to expand...
Click to collapse
Well because my device has been fixed once already and LG failed to fix all the issues it had. About 2 years ago I sent my G4 back because it had a really bad image retention problem (not to confuse with burn ins, that are 2 different things), the battery life was absolutely garbage and it heated up way to quick. The overheating problem bothered me the most and it worried me because it might been a sign that it would bootloop eventually. Luckily LG approved to repair my device but after a year or so all the problems it had came back and now it seems that it finally started to bootloop. I'm done, even when I send back my device it would probably show the same problems after a while. I don't trust this device anymore, it's in my opinion unreliable.
Mr.FREE_Bird said:
Well because my device has been fixed once already and LG failed to fix all the issues it had. About 2 years ago I sent my G4 back because it had a really bad image retention problem (not to confuse with burn ins, that are 2 different things), the battery life was absolutely garbage and it heated up way to quick. The overheating problem bothered me the most and it worried me because it might been a sign that it would bootloop eventually. Luckily LG approved to repair my device but after a year or so all the problems it had came back and now it seems that it finally started to bootloop. I'm done, even when I send back my device it would probably show the same problems after a while. I don't trust this device anymore, it's in my opinion unreliable.
Click to expand...
Click to collapse
They cant fix the bootloop. They can fix the issue, but bootloop is a design problem.
I have 505 not yet bootlooped. Battery life is bad and it does heat alot. Still, the phone is really good to use.
Yep, with this phone, you need to have a backup phone... Im not sure what phone i would like to get. Smaller display would be nice, this is hard to use only with one hand.
I have been using my G4 H815P (locked bl) downgraded from MM to L with Artic Silver 5 compound and a small heatsink
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
plus changing the copper tape insulation on top of the processor.
I have root and have disabled the two big cores and set the small core to 1440mhz and big core to powersave 384mhz because with kernel auditor it does not allow you to disable both cores at once. Been using the device for about a month or so. Will upload pictures this weekend if anyone wants to do this "mod".
Alex_XV6700 said:
I have been using my G4 H815P (locked bl) downgraded from MM to L with Artic Silver 5 compound and a small heatsink plus changing the copper tape insulation on top of the processor.
I have root and have disabled the two big cores and set the small core to 1440mhz and big core to powersave 384mhz because with kernel auditor it does not allow you to disable both cores at once. Been using the device for about a month or so. Will upload pictures this weekend if anyone wants to do this "mod".
Click to expand...
Click to collapse
please post your results and guide into my boot loop fix it list see my signature
Sent from my LG-H815 using XDA Labs
steadfasterX said:
please post your results and guide into my boot loop fix it list see my signature
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Sure thing!
I hope to have some time this weekend to take some pictures and document all the process. As I used a "rework" station to recover my G4 from the ILAPO at first.