Related
TESTERS SELECTED, THOSE CHOSEN WILL BE CONTACTED ON PM WITH FURTHER INSTRUCTIONS.
please mr. clow, if you could close this thread i would appreciate it!
reserved for any announcements !
Withdrawn, not sure I have the time commitment available to thoroughly test an alpha build anymore.
Bug report cm7
Phone: international ATRIX
Rom: cm7.1 alpha
Kernel: edgans d00 overclock
Bugs
Cmparts. In settings- :
tablet settings FC's
Auto brightness not available.
No fixes found
No data connection on reboot. Apns being deleted on boot.
Logcat attached
DOWNLOAD
Sent from my MB860 using XDA Premium App
May i please? I dont work dont go to skool and i sit in front of my puter all day playin wit my fones
*edit*
dont kno great bug or any bugs for that matter
nevermind
/////////////
Pick me pleeeease! \o|
I'm a senior .NET developer with 13+ years programming experience, now studding Android for a couple of months now, also doing a two weeks Android course (this week and the next one). My goal is to start creating some ROMs for the device too, but my current knowledge is pretty basic and theoretical right now.
I'm also very experienced on testing ROMs (used to do it a lot on my old Xperia X10). tested many versions from Eclair 2.1 to GB 2.3, including MIUI and CyanogeMod too
I can apply the test CM7！
Been waiting for this to come for a while. Be nice to be a tester
Sent from my MB860 using XDA App
To all of you posting, "pick me"
It's not going to help you at all. If you read the original post, it was mentioned that you needed to provide a sample bug report to be considered.
I don't have much free time on my hands lately, but if you need a backup let me know.
Bug Report:
Blind_Guardian
Phone: ATT Atrix
Radio: OTA Stock (N_01.77.30P)
Hacks/Mods used: Battery fix, webtop on HDMI, Gtalk on 3g
Kernel: Stock
What is the expected behavior?
When the google navigation app is started the GPS should lock on within a reasonable amount of time and should remain locked on. Should it lose a lock, it should re-lock within a reasonable amount of time. The "maps" app should operate within the same limits.
What is the actual behavior?
When the GPS app is started, the initial lock takes anywhere between 3-5 minutes to get a lock. Once a lock occurs it will remain locked for a short while. It does not lose the lock at the same time intervals, it is sporadic. I've seen it take anywhere from 10-15 minutes. Once a lock is lost and you hear the audible warning... the phone will reboot itself every time. The same issue occurs if you use the "maps" app. You are able to get gps data, but once you lose a lock the phone reboots itself.
What steps will reproduce the problem?
- Make sure GPS radio is on.
- Initiate "navigation app" or "maps"
- Wait for a GPS lock
- Wait for GPS signal loss
Possible workarounds:
None, that I could find.
Bug: stewartsoda isn't an alpha tester
Environment: Life v0.1 Alpha 2
Firmware: R0001
Hardware: Human
Expected behavior: stewartsoda has access to alpha builds for testing
Observed behavior: stewartsoda doesn't have access to alpha builds for testing
Steps to reproduce: Ask stewartsoda to retrieve the latest build for testing. He will be unable to do so.
Conjecture: There are many possible reasons why Stewartsoda doesn't have access.
One- he hasn't been granted access.
Two- he hasn't known about formal alpha testing of CM7 until now.
Three- he hasn't been invited to the project and doesn't know where to retrieve builds from.
Possible solutions:
One- invite stewartsoda to be an alpha tester for cm7 on the Atrix.
Two- provide download links to stewartsoda through PM.
Attachments:
Attachment 1: logcat.txt - Brain lolcat output
Attachment 2: dmesg.txt - Brain dmesg output
Seriously though. I'm a test development engineer and Bugzilla admin for a large SSD manufacturer and developer. This is what I do for a living.
Sent from my MB860 using XDA App
Bug Report
Forum name: ramguerra
Phone: AT&T Atrix 4G AKA MB860
Radio: N_01.77.30P
Firmware: CM 7.0A
Hacks/Mods used: N/A
When a user places a call, the proximity sensor will detect the distance from the persons cheek, and when close enough, will shut off the screen and de-activate the touch sensor in order to avoid accidental key presses.
------------------------------------------------------------------------
The proximity sensor on the phone seems to not be responding as it should. I have noticed that when I place a call on 7.0A, the screen stays on and does not shut off. My cheek will then press the speaker phone button, or any other button that is there. This was not a problem on stock FW so it is not a phone issue.
To reproduce:
Place a call and listen to it.
Notice that your cheek will press additional buttons.
To verify, try another call and place your finger at the top right corner of the phone next to the sound opening. On stock, the screen will shut off.
Fix:
Verify that the prox sensor is activated, then try increasing the sensitivity of the sensor in order to shorten the distance needed to the reciever to trigger the screen shut off.
I can apply the test CM7
I would be happy to put it through it's paces for you
It's what I do damnit
I only work 15 days a month. (2-2-3 schedule dont ask)
I was tutor of the year in 2002 at my community college, where I tutored special needs students (pateince^2)
TESTER:
Yes I am free, cheap, and easy.
I am a "Test Technician" for a living at raytheon. I test laser/sensor(camera) turrets for military aircraft.
I have an AS in Electronics, will be getting my BAAS with a technology focus in December, and I am taking technical writing for the hell of it.
Athailias:
Bug: Touch screen becomes unresponsive after 12 seconds.
steps: Play super mario 64 and do any of the koopa races and halfway up the hill you DIE and DIE because the damn screen stops responding... but seriously hold the screen for 12 seconds and it stops responding
Bug fix: hire me to assassinate the moisture detection software developers at motorola, or get CM7 ported.
Honestly I would love to help, just to help. I dont want anything in return, im not going to *****. i just enjoy tinkering with the phone. I am a flash addict and will flash every darn rev that comes out and use the crap out of it even if I cant make calls. Ive been known to "use" my captivate at work as a paper holder all night because I flashed at work with no pc backup. I havent used logcat or dmeschmegma, but i bet I can figure it out before the beta starts. I would like to also add that I am a military veteran for equal opportunity employment, and I am mexican... ok half mexican
I would love to test, but unfortunately do not have the time to dedicate to this.
Good luck with the development, and hopefully you can weed through the Darwin filled gene pool in your thread and select the few testers who will actually be useful, and help you. It's very apparent most of them cannot even read!!!
To those who read the OP, and responded correctly, good luck at being some of the first to test this on the Atrix!
I would love to apply the test CM7
I am a programmer and linux administrator, and have led major projects (think: popular Half-Life 2 mod) with major bug-tracking efforts. So, with that said, I am *very* familiar with both the development process, and how to submit bugs.
But before I toss my name in the hat (with a proper application), I must know: How functional is this alpha? My atrix is my only phone at the moment, so I can't lose phone functionality if the ROM has issues with the radio.
Sample bug report:
Camera flash causes reboot
Tester: bilbert
Description: Turning on the camera's flash functionality via a non-camera application causes the phone to reboot.
Found in: CM7a 1.01-27
Present up to: CM7a 1.01-31
To reproduce:
* Install "Widgetsoid".
* Create a widget with a "flashlight" button.
* In Widgetsoid options, select flashlight option 2.
* Add widget to home screen.
* Press flashlight button. It will take a second, but it will turn the camera LED on.
* Press flashlight button again. LED will turn off.
* Press flashlight button again. Leave on until screen turns off. Phone will reboot.
Attached are logcat and dmesg, with relevant error messages.
sounds pretty good job guys. I offer my tester: D
I'd be up to testing.
I haven't done much Android ROM testing, but I know the whole test, bug report, etc drill as I've done a few of the 360 firmware betas, Moto soak betas, and Cr48 pilot
I've also got plenty of time, no job besides work I do around the house.
Suddenly, bug report
----
KefkaticFanatic
Model: MB860
Kernal: 2.6.32.9-00001 [stock]
Radio: N_01.77.30P
ROM: kennethpenn's Gingerbread Beta 4
Mods installed: AOSP Gingerbread theme 6.7, Battery Fix
Issue: Data connection shows a connection but does not transfer any data
Description: After switching off the WiFi connection, I notice that for a short while the wireless connection will show a signal but be unable to work with any data. This is seen with various apps, such as Friendcaster, the Market, Dolphin, etc. They will simply be unable to load any pages for a small amount of time, usually between 30-60 seconds, and then will suddenly be able to load properly.
Reproduce: Start using an app requiring a web connection like a Facebook or Twitter app over the WiFi. Then, switch off the WiFi and attempt to load a page or refresh the main page of the app.
logcat and dmesg attached
Thanks!
-----------
And thanks for considering and continuing to develop
I know that there has been quite a lot of these threads, and I've gone through a lot of them, but I havent really found a pattern as to the suggested ROMs, so I'm going to have a go myself with a new thread and I hope you will bear with me...
The thing is that I need to use my HD2 with Android for work related use (self-employed freight carrier). And I only have a few specific requirements:
- SUPER stable!
- Working GPS (For use with both Google Navigation and CoPilot v8 Professionel)
- Working Camera (For taking a few pictures, if I come across damaged goods - video not required)
- Decent battery life (I don't need 160 hours of stand-by as it will be on cable in the car most of the time - but it would be nice if it could hold a weekend on pure standby)
- And then it will be using an app programmed by a local software house, but I do not know the requirements of this. But it is installed as a service and works together with the two navigation systems.
I will NOT be using it for phonecalls or text messages at all. There will only be a data SIM card in it.
Currently I have only tried NexusHD2 Gingerbread v3.2a NAND (installed with MAGLDR). And it usually reboots 3-4 times a day + Google Navigation closes a couple of times during a workday. And 1-2 times a day it locks up so I have to remove battery.
This is not acceptable for my use, when I'm driving a car and sometimes need to rely 100% on my navigation. No disrespect to tytung. I may just have a bad phone or have been very unlucky with your ROM.
I dont care what version of Android the ROM is built on as long as the above requirements are met.
Thanks a lot for your time and any suggestions.
// Martin
gpc v2.8
http://translate.googleusercontent....PLB8JH&usg=ALkJrhgYtN0WTwy1B4Snry54m_Ek_RSo4w
micavimale said:
http://translate.googleusercontent.c...9OYIuvQ253qMzw
Click to expand...
Click to collapse
Link is not working for me.
...corrected!!!
Recovery 5/150/5
Thanks, but I would prefer links to ROM threads rather than direct links to ROMs I know nothing about.
...your decision.
http://forum.xda-developers.com/showthread.php?t=909096&page=216
Thank you very much. I will have a look at it.
Other suggestions are still welcome.
Hy,i search the best rom with HTC sense 3.5
There is a rom with the dormianx kernel and app2SD?
Now i use a CM7.2 rom with the dorimanx kernel and it's very fast and have a great battery use. So i search something like this but with HTC sense
If someone can help me i'm very gratful
Try coredroid the battery is gr8 also the speed ;-)
I would suggest Team Blue DROID rom
If version 7.9 is stable with the lockscreen I would say MwakiousRUNNINGrom.
LOVED that rom, specially version 3.0 but now I am looking for a Rom that has Tweaks (RCMix3D Tweaks) and Beats Audio.
the MwakiousRUNNINGrom has this, but is so unstable in the lockscreen, sometimes it works and sometimes not.
I'm using the Sense 3.5 rom from Team Blue Droid at the moment (Beats won't work ), but when MwakiousRUNNINGrom 7.9 is out I really will give it a try (again....)
Vinny1994 said:
If version 7.9 is stable with the lockscreen I would say MwakiousRUNNINGrom.
LOVED that rom, specially version 3.0 but now I am looking for a Rom that has Tweaks (RCMix3D Tweaks) and Beats Audio.
the MwakiousRUNNINGrom has this, but is so unstable in the lockscreen, sometimes it works and sometimes not.
I'm using the Sense 3.5 rom from Team Blue Droid at the moment (Beats won't work ), but when MwakiousRUNNINGrom 7.9 is out I really will give it a try (again....)
Click to expand...
Click to collapse
beats audio doesnt work on any rom unless you have beats audio headphones
its all a figmant of imagination that beats audio will work on the hd2
@Kameirus (yeah I pressed quick reply instead of quote lol)
Guess it will never really work on the HTC HD2 because it doesn't have the hardware for it.
But, I do hear a sound difference on the rom "SENSATION XL V 3.0 stock ALL IN ONE" by haldric with my friend's Beats Solo headphone.
Yes, I also think thats really weird.
Vinny1994 said:
@Kameirus (yeah I pressed quick reply instead of quote lol)
Guess it will never really work on the HTC HD2 because it doesn't have the hardware for it.
But, I do hear a sound difference on the rom "SENSATION XL V 3.0 stock ALL IN ONE" by haldric with my friend's Beats Solo headphone.
Yes, I also think thats really weird.
Click to expand...
Click to collapse
excatly you hear the difference with beats headphones
not the stock headphones or phone speaker
thats why it was removed from the TBD roms
not many of us can afford 200 dollar headphones lol
team blue droid, IMHO
all work but not without some bugs, ... but this is the best =) thanks to creators
I've been using it since I saw sens ROM
Kameirus said:
excatly you hear the difference with beats headphones
not the stock headphones or phone speaker
thats why it was removed from the TBD roms
not many of us can afford 200 dollar headphones lol
Click to expand...
Click to collapse
Haha, I lolled at that last line
I am also looking for a Sense with Tweaks + Beats because I want to buy a "Beats by Dr. Dre Beats Pro" for my girlfriend's birthday.
But ofcourse if the Beats Audio does not work it doesn't make sense to get her this headphone.
The only thing that made music sound better trough my stock headphones is Volume + (Sound Boost) the payed version.
thanks to all I'm trying the team blue v3.4 but for me it have to much bugs i think i will return to my old cm7.2
But if will be corrct all the most important bugs I will be happy to give an other chance at team blue's rom
Ansem said:
thanks to all I'm trying the team blue v3.4 but for me it have to much bugs i think i will return to my old cm7.2
But if will be corrct all the most important bugs I will be happy to give an other chance at team blue's rom
Click to expand...
Click to collapse
and what bugs would they be
my feedback on TBD 3.4
Hi,
some feedback I have on the TBD ROM:
* overall acceptable experience, but not bug free
* still have to reboot about once a day, system freezes from time to time
* had to set settings/power/sleep mode to off. Otherwise the phone seems to loose the settings/wireless&networks/Mobile networks/always-on mobile data setting.
* had to switch off facebook live updates. Serious battery hog.
* had to set settings/power/power mode to normal. Economy mode seems to freeze the phone when battery level is too low, and prevent restarting.
(very weird bug: did not want to start with battery X which ran down the day before, but did so with battery Y. Still, both batteries had about the same charge level. Had to push reset to get the phone starting with battery X. And yes, tested both with 10 sec off battery interval, so reset should not have been needed)
* it does not want to sync mail overnight, even with the correct settings in setting/accounts&sync on the individual accounts, and sleep mode off.
* SMS delivery notifications do not work: settings keep coming back to 'off'. Think I've seen it working once, but no more.
* built-in wifi and USB tethering do not work. wifi tethering beacon info does not publish WPA (and therefore makes it impossible to connect) and above that, it makes the phone crash when enabled for the 2nd time in a row. USB tethering keeps saying it is unable to activate. Using Barnacle now (which also complains about wpa).
* android rants, very probably not TBD related:
* calendar notifications in the notification bar do not disappear when read from the calendar directly. I now have to acknowledge meetings twice.
* tasks and notes do not sync seamlessly. Too many apps involved, too many flavours, too many clicks/taps. (using MyPhoneExplorer for the moment)
Not business ready.
overall impression of this android version compared to WM:
+: better apps, web sites with flash, better on line experience. side by side agendas.
-: slower, more bugs, less battery life, more hussle
But hey, I still stick with it after 4 days, so it's no too bad. Will try a faster SD card, to see how it behaves then.
(Using stock TBD 3.4 in NAND, latest CLK, class 4 SD card, from fresh clean latest WM official rom )
hansboot020 said:
Hi,
some feedback I have on the TBD ROM:
* overall acceptable experience, but not bug free
* still have to reboot about once a day, system freezes from time to time
* had to set settings/power/sleep mode to off. Otherwise the phone seems to loose the settings/wireless&networks/Mobile networks/always-on mobile data setting.
* had to switch off facebook live updates. Serious battery hog.
* had to set settings/power/power mode to normal. Economy mode seems to freeze the phone when battery level is too low, and prevent restarting.
(very weird bug: did not want to start with battery X which ran down the day before, but did so with battery Y. Still, both batteries had about the same charge level. Had to push reset to get the phone starting with battery X. And yes, tested both with 10 sec off battery interval, so reset should not have been needed)
* it does not want to sync mail overnight, even with the correct settings in setting/accounts&sync on the individual accounts, and sleep mode off.
* SMS delivery notifications do not work: settings keep coming back to 'off'. Think I've seen it working once, but no more.
* built-in wifi and USB tethering do not work. wifi tethering beacon info does not publish WPA (and therefore makes it impossible to connect) and above that, it makes the phone crash when enabled for the 2nd time in a row. USB tethering keeps saying it is unable to activate. Using Barnacle now (which also complains about wpa).
* android rants, very probably not TBD related:
* calendar notifications in the notification bar do not disappear when read from the calendar directly. I now have to acknowledge meetings twice.
* tasks and notes do not sync seamlessly. Too many apps involved, too many flavours, too many clicks/taps. (using MyPhoneExplorer for the moment)
Not business ready.
overall impression of this android version compared to WM:
+: better apps, web sites with flash, better on line experience. side by side agendas.
-: slower, more bugs, less battery life, more hussle
But hey, I still stick with it after 4 days, so it's no too bad. Will try a faster SD card, to see how it behaves then.
(Using stock TBD 3.4 in NAND, latest CLK, class 4 SD card, from fresh clean latest WM official rom )
Click to expand...
Click to collapse
Don't waste your money on a new SD card if you don't already have one, it shouldn't make any difference to your experience. If necessary, move all of your heavily used apps to internal storage, this will make them less buggy and more responsive, and will allow them to load much faster on boot.
APN error for SFR (France)
Hi,
just to let you know, the built in APN definitions are wrong for SFR (France) in TBD 3.4:
APN 'full internet'/sl2sfr should have 'APN type' set to 'default' and not 'default,hipri'.
Otherwise 3G/3G+ won't turn on, and negotiation at data connection start will take longer. Being stuck to Edge and GPRS is a bit of a shame...
hansboot020 said:
Hi,
some feedback I have on the TBD ROM:
* overall acceptable experience, but not bug free
* still have to reboot about once a day, system freezes from time to time
* had to set settings/power/sleep mode to off. Otherwise the phone seems to loose the settings/wireless&networks/Mobile networks/always-on mobile data setting.
* had to switch off facebook live updates. Serious battery hog.
* had to set settings/power/power mode to normal. Economy mode seems to freeze the phone when battery level is too low, and prevent restarting.
(very weird bug: did not want to start with battery X which ran down the day before, but did so with battery Y. Still, both batteries had about the same charge level. Had to push reset to get the phone starting with battery X. And yes, tested both with 10 sec off battery interval, so reset should not have been needed)
* it does not want to sync mail overnight, even with the correct settings in setting/accounts&sync on the individual accounts, and sleep mode off.
* SMS delivery notifications do not work: settings keep coming back to 'off'. Think I've seen it working once, but no more.
* built-in wifi and USB tethering do not work. wifi tethering beacon info does not publish WPA (and therefore makes it impossible to connect) and above that, it makes the phone crash when enabled for the 2nd time in a row. USB tethering keeps saying it is unable to activate. Using Barnacle now (which also complains about wpa).
* android rants, very probably not TBD related:
* calendar notifications in the notification bar do not disappear when read from the calendar directly. I now have to acknowledge meetings twice.
* tasks and notes do not sync seamlessly. Too many apps involved, too many flavours, too many clicks/taps. (using MyPhoneExplorer for the moment)
Not business ready.
overall impression of this android version compared to WM:
+: better apps, web sites with flash, better on line experience. side by side agendas.
-: slower, more bugs, less battery life, more hussle
But hey, I still stick with it after 4 days, so it's no too bad. Will try a faster SD card, to see how it behaves then.
(Using stock TBD 3.4 in NAND, latest CLK, class 4 SD card, from fresh clean latest WM official rom )
Click to expand...
Click to collapse
Nice information u have there, i just completed download the TBD v3.5 and looking for review... Thank god i read this thread.... Anyway thanks
Sent from my mighty HTC HD2
Hi all,
Currently looking for an upgrade from my Moto G and have a specific list of requirements (long-ish battery life, cheap-ish, ideally fast charging, ideally ANT+, ideally waterproof, accurate GPS for tracking runs) which the S5 seems to meet well. Only thing I dont think I could live with is TouchWiz (and the assosciated lag I would expect it would bring with it).
My question: how is CM running on these devices with regards stability and force closes etc. Can live with a small dip in camera quality and having never had a fingerprint scanner I wont miss it but really need a rock solid, stable device. Is there a better alternative out there (am also closely considering the Zuk - but not waterproof and possibly patchy GPS - and the Moto X Play - slightly more expensive and reports of lag)?
I'm currently running CM13 on my KLTE, and it honestly seems fine.
Battery life is just under 4hrs SOT.
It charges pretty fast IMO (About an hour and a little bit with a constant 1800mA @ 4.5V)
Though was I've read in a quick Google search is that CM doesn't support ANT+ ever since the s4 branch.
Never had issues when the phone's been blessed with water, Its a pretty tight seal all around.
GPS is accurate. I usually get a fix within the first ten seconds. Mind you I use GPS Status to download AGPS info to help.
I rarely get force closes but there are the occasional soft reboots with the phone, which seems to put it in a boot-loop when it does. But that could be my configuration of Xposed and other modifications that do that.
i dont like the in-use battery life at all, deep sleep life is insanely improved on CM13 i assume due to doze, you can buy third party extra large batteries that are also a replacement for the back cover
cm-12.1-20151226-NIGHTLY-klte = quite stable, think i had only a couple minor bugs, no crashes, my baseband is a little old, i tried some gps app from fdroid during a walk & it was as if the calibration kept changing... i passed the same spot more than once, it would be too far north one time then too far southeast another time & so on, but maybe it was storing literal data points (some other apps, especially map apps i would assume they might auto align themselves to roads), crashed the camera when using opencamera too fast or switching between it & stock camera, opencamera couldnt do 60 or 120fps videos even though the option was set
cm-13.0-20160116-NIGHTLY-klte = turning flashlight off kills camera (& the flashlight tile) until reboot, i was going through menus fast or something, the status bar crashed & then soft reboot was frozen on the loading face icon, i was hoping snapdragoncamera was enabled cuz i see it in changelogs, but i still see stock camera unfortunately...
charging is quite fast, from 0 to ~80% at least (this is normal for about every device anyway)
i havent tried any other versions yet, i dont have gapps, only been web browsing in lightning browser (from fdroid), trying kernel adiutor, notepad, little bit of camera, i dont have a SIM card yet, hope it works fine...
i believe i saw a modified TW rom that keeps the TW framework, but visually tries to be AOSP, the purpose of course is to be able to use the samsung camera & some of the other proprietary apps/features
My build is a KLTEusc smg900r4, with cm13, on first boot I had issues with the access points to the mobile network, but after I input one access point it found the rest on its own, only other issue is when sending long text messages it doesn't go through from some reason, overall very proud of it, much better than touchwiz
Hey I just had a few questions when it came to flashing a custom Nougat ROM at the moment. If anyone could answer them that would be great I am on stock Marshmallow right now and not rooted or anything. But I am thinking about flashing a custom ROM if there are benefits.
What features do we lose when we are coming from stock? (Moto Display/Gestures mainly)
How's the battery life compared to stock?
Any issues calls/texts/signal/wifi/bluetooth?
Is there an audio problem with most of the ROMs?
How is the camera on Nougat?
Any help would be much appreciated. Thanks in advance to those that respond
Jyjieng11 said:
Hey I just had a few questions when it came to flashing a custom Nougat ROM at the moment. If anyone could answer them that would be great I am on stock Marshmallow right now and not rooted or anything. But I am thinking about flashing a custom ROM if there are benefits.
What features do we lose when we are coming from stock? (Moto Display/Gestures mainly)
How's the battery life compared to stock?
Any issues calls/texts/signal/wifi/bluetooth?
Is there an audio problem with most of the ROMs?
How is the camera on Nougat?
Any help would be much appreciated. Thanks in advance to those that respond
Click to expand...
Click to collapse
Whether or not you will benefit from a custom ROM will depend on you and your expectations.
Ambient display is the alternative/replacement to Moto display and some ROMs and add-ons allow for gestures.
As far as your other questions, these vary from ROM to ROM and user to user and the set ups they have (apps, kernel, customization, etc.) The best thing to do is read through the threads for the various nougat Roms and determine for yourself if they will meet your specific requirements...then test them for yourself.
aybarrap1 said:
Whether or not you will benefit from a custom ROM will depend on you and your expectations.
Ambient display is the alternative/replacement to Moto display and some ROMs and add-ons allow for gestures.
As far as your other questions, these vary from ROM to ROM and user to user and the set ups they have (apps, kernel, customization, etc.) The best thing to do is read through the threads for the various nougat Roms and determine for yourself if they will meet your specific requirements...then test them for yourself.
Click to expand...
Click to collapse
Thanks for the reply. I know I made a really big generalization here I was just wondering with other people's mileage whether Nougat helped there battery life or not, etc. But thank you
Here's the lowdown:
As far as features, you would probably gain a few that you don't really need (like the ability to use themes, and control the audio levels) and battery will be roughly the same, if not a little worse usually (stock ROM is more optimized). A few features will be slightly different (like ambient display instead of moto display) and you'll also gain access to the hidden LED inside the top speaker of this phone. That's right, the MXPE has a notification LED! Can you even imagine? But it's there!
LineageOS is a good choice if you want to test out nougat, it's very stable at this point and is easily the cleanest ROM in my opinion (no bloat, feels like stock android). Battery life is pretty good but it drains a lot more on standby than stock does. Remember when you flash a non-stock rom you will also have to flash google apps. I like the stock or "super" options because they also give you the pixel launcher.
Root adds a whole new world of possibilities, with the ability to modify or add functionality you wouldn't normally be able to access. Like changing CPU governors (for better battery or better performance). LineageOS comes unrooted, and personally I keep it that way for maximum app compatibility (Pokémon Go, many streaming video services, and some banking apps don't work with rooted devices). If you wanted to play with root you could flash the root .zip file or just flash supersu like I think most people on XDA do.
As far as issues, every ROM has different quirks. I can tell you that often times the hardware drivers for custom ROMs can be hit-or-miss. Right now LineageOS (and anything based on LOS) is very stable and doesn't have many bugs, but that can change anytime. Any time your ROM updates it could potentially add a new quirk/bug. As of the latest nightly (2/21/17) I have not seen any significant bugs. No issues with Bluetooth or cell service (AT&T) and all gestures work (twist for camera, chop for flashlight, wave hand over screen to silence ring, ambient display, etc) GPS also works well. The only quirks I've noticed on this build is the camera takes a little longer to start up (sometimes up to 7 seconds) and occasionally my cell signal will say I have zero bars for a few seconds even though I still have service (no dropped calls/dropped web pages/etc).
Sean89us said:
Here's the lowdown:
As far as features, you would probably gain a few that you don't really need (like the ability to use themes, and control the audio levels) and battery will be roughly the same, if not a little worse usually (stock ROM is more optimized). A few features will be slightly different (like ambient display instead of moto display) and you'll also gain access to the hidden LED inside the top speaker of this phone. That's right, the MXPE has a notification LED! Can you even imagine? But it's there!
LineageOS is a good choice if you want to test out nougat, it's very stable at this point and is easily the cleanest ROM in my opinion (no bloat, feels like stock android). Battery life is pretty good but it drains a lot more on standby than stock does. Remember when you flash a non-stock rom you will also have to flash google apps. I like the stock or "super" options because they also give you the pixel launcher.
Root adds a whole new world of possibilities, with the ability to modify or add functionality you wouldn't normally be able to access. Like changing CPU governors (for better battery or better performance). LineageOS comes unrooted, and personally I keep it that way for maximum app compatibility (Pokémon Go, many streaming video services, and some banking apps don't work with rooted devices). If you wanted to play with root you could flash the root .zip file or just flash supersu like I think most people on XDA do.
As far as issues, every ROM has different quirks. I can tell you that often times the hardware drivers for custom ROMs can be hit-or-miss. Right now LineageOS (and anything based on LOS) is very stable and doesn't have many bugs, but that can change anytime. Any time your ROM updates it could potentially add a new quirk/bug. As of the latest nightly (2/21/17) I have not seen any significant bugs. No issues with Bluetooth or cell service (AT&T) and all gestures work (twist for camera, chop for flashlight, wave hand over screen to silence ring, ambient display, etc) GPS also works well. The only quirks I've noticed on this build is the camera takes a little longer to start up (sometimes up to 7 seconds) and occasionally my cell signal will say I have zero bars for a few seconds even though I still have service (no dropped calls/dropped web pages/etc).
Click to expand...
Click to collapse
Thanks for all the information that really helped me out. I will most likely stay stock due to the fact that battery life is important to me. It's hard to get good battery when the phone is in your pocket and doze doesn't work during movement.