Hi all,
Had my Nexus 6 for a while and love it, but its starting to get a little sluggish and I've been having a look at a few ROMs available but I've not quite found one thats took my fancy. I was wondering if someone could recommend a ROM that's minimal providing good performance and possibly something that allows a CPU and GPU overclock? If I'm not mistaken its the kernel that provides the overclocking facility and not the ROM. I have seen a ROM (must include a kernel) that states CPU and GPU overclocks but in the description its actually downclocked for battery life.
Just throwing it out there in case someone reading this could answer as well, I've heard GTA San Andreas is an intense game to play on High settings, how does (stock) perform or as a bonus do you know how it performs with an overclock? I was surprised to see quite a few phone on benchmarks beat the Nexus 6
Thanks for any help/recommendations
first off, questions go into the q&a/help section, not into general. secondly, roms do not provide oc, or performance enhancing. thirdly, you want to try different kernels, as they provide oc and performance enhancements. i use elementalx kernel, which allows me to oc to 3033mhz.
and which phones beat the n6 in benchmarks? i get 58500 on antutu with my n6.
simms22 said:
first off, questions go into the q&a/help section, not into general. secondly, roms do not provide oc, or performance enhancing. thirdly, you want to try different kernels, as they provide oc and performance enhancements. i use elementalx kernel, which allows me to oc to 3033mhz.
and which phones beat the n6 in benchmarks? i get 58500 on antutu with my n6.
Click to expand...
Click to collapse
Hi,
Yes as I did say I did pick up that kernels provided over clocking and I will try elementalx and see how that goes. As for the benchmarks for graphics I come across this website and filtered out Desktop and over 7" devices and that's where I discovered the Nexus 6 quite low down the score board.
http://gfxbench.com/result.jsp
Well definitely got some stuff to do now, I shall hopefully remove forced encryption and get elementalx on the go and see how it goes.
simms22 said:
first off, questions go into the q&a/help section, not into general. secondly, roms do not provide oc, or performance enhancing. thirdly, you want to try different kernels, as they provide oc and performance enhancements. i use elementalx kernel, which allows me to oc to 3033mhz.
and which phones beat the n6 in benchmarks? i get 58500 on antutu with my n6.
Click to expand...
Click to collapse
Hi Again,
Took absolutely ages to install ROM and kernel because I deleted everything I'm twrp (advanced options) but Chroma ROM and Elementalx kernel are installed but I have some questions if you can help. First you have a massive 3033 over clock which if I recall was an option available when installing through recovery, however I've paid for the Elementalx app and highest over clock available is: 2649. Any reason for this? Also can I re install Elementalx through recovery without loosing anything?
Also there's only a 600mhz clock available for graphics is it possible to get higher ?
Last but not least I was really looking forward to having no encryption but it seems Elementalx installs with encryption.. Anyway around this? I've heard of read and write increases of up to three times faster.
mrsweet1991 said:
Hi Again,
Took absolutely ages to install ROM and kernel because I deleted everything I'm twrp (advanced options) but Chroma ROM and Elementalx kernel are installed but I have some questions if you can help. First you have a massive 3033 over clock which if I recall was an option available when installing through recovery, however I've paid for the Elementalx app and highest over clock available is: 2649. Any reason for this? Also can I re install Elementalx through recovery without loosing anything?
Also there's only a 600mhz clock available for graphics is it possible to get higher ?
Last but not least I was really looking forward to having no encryption but it seems Elementalx installs with encryption.. Anyway around this? I've heard of read and write increases of up to three times faster.
Click to expand...
Click to collapse
if you intall the kernel through tbe app, youll get less options. install it tbrough the recovery, amd go ghrough thd setup and choose 3032mhz.
for the gpu, yes, 600 is the max. no way around that.
the kernel supports decryption, but you have to decrypt first, its not automatic. to decrypt, you have to reformat your storage, then boot up with the kernel.
simms22 said:
if you intall the kernel through tbe app, youll get less options. install it tbrough the recovery, amd go ghrough thd setup and choose 3032mhz.
for the gpu, yes, 600 is the max. no way around that.
the kernel supports decryption, but you have to decrypt first, its not automatic. to decrypt, you have to reformat your storage, then boot up with the kernel.
Click to expand...
Click to collapse
Hi again,
I originally did everything through recovery but didn't choose the highest over clock I just assumed it could be changed in settings or something.
Anyway to decrypt.. If I go into TWRP and perform a wipe (the three things that it selects as default) shall I install just the kernal first (no rom, su or gapps) to get the option to decrypt? Then install the ROM , Gapps and su afterwards?
Sorry for the newbness
mrsweet1991 said:
Hi again,
I originally did everything through recovery but didn't choose the highest over clock I just assumed it could be changed in settings or something.
Anyway to decrypt.. If I go into TWRP and perform a wipe (the three things that it selects as default) shall I install just the kernal first (no rom, su or gapps) to get the option to decrypt? Then install the ROM , Gapps and su afterwards?
Sorry for the newbness
Click to expand...
Click to collapse
lol, thats alright, we were all newbs once.
no, thats not how things work. a rom has to be installed, then the kermel. then you reformat your storage, then you just reboot and youre unencrypted
btw, im still encrypted. besides the read/write speeds, it all is the same.
Read the disable forced encryption thread in development. Take your time before you mess things up.
simms22 said:
lol, thats alright, we were all newbs once.
no, thats not how things work. a rom has to be installed, then the kermel. then you reformat your storage, then you just reboot and youre unencrypted
btw, im still encrypted. besides the read/write speeds, it all is the same.
Click to expand...
Click to collapse
ok, I wiped the phone in TWRP installed Chroma then Elementalx, gApps then supersu then I selected to wipe data and I had to type yes. Afterwards Chroma would be stuck in a boot loop. It said Android is starting.. starting apps but then immediately restart. So I tried again but after installing everything I just performed a factory reset and this time it worked, but I have an odd problem.. it;s installing apps but saying I'm running out of storage space?.. I went into storage and it shows 25.98GB available.. any ideas? and also thanks for your help I do now have it decrypted and I think im running an overclock that you had.. I'll have to wait for the app to install to verify
mrsweet1991 said:
ok, I wiped the phone in TWRP installed Chroma then Elementalx, gApps then supersu then I selected to wipe data and I had to type yes. Afterwards Chroma would be stuck in a boot loop. It said Android is starting.. starting apps but then immediately restart. So I tried again but after installing everything I just performed a factory reset and this time it worked, but I have an odd problem.. it;s installing apps but saying I'm running out of storage space?.. I went into storage and it shows 25.98GB available.. any ideas? and also thanks for your help I do now have it decrypted and I think im running an overclock that you had.. I'll have to wait for the app to install to verify
Click to expand...
Click to collapse
just reboot. thst happened to me twice, not enough space, and i rebooted. fixed it for me. i believe it said i was running out of space in the /system/. oh well.
simms22 said:
just reboot. thst happened to me twice, not enough space, and i rebooted. fixed it for me. i believe it said i was running out of space in the /system/. oh well.
Click to expand...
Click to collapse
Hi,
before you replied I went ahead and tried flashing again this time not performing the wipe after I installed everything. But now I can't get rid of the boot loop, everytime Chroma starts for the first time a window appears saying "apps are starting.. starting apps" but once finished it reboots... I've tried flashing everything and performing a wipe, flashing and performing a cache and delvik wipe and also flashing and performing nothing just booting into system... however im still stuck in that boot loop.. seems I've gone a step backwards somewhere lol.. any ideas? I'll continue flashing in the meantime until I get a reply thanks for your help again
This time I wiped user data as well as factory reset so there was nothing at all on the phone. restarted into TWRP which mounted the file system so I could transfer all the files over from my PC. installed everything as per usual and once installed I didn't wipe delvik cache I just selected to boot into system but same again it just says starting apps and once finished just reboots.
mrsweet1991 said:
This time I wiped user data as well as factory reset so there was nothing at all on the phone. restarted into TWRP which mounted the file system so I could transfer all the files over from my PC. installed everything as per usual and once installed I didn't wipe delvik cache I just selected to boot into system but same again it just says starting apps and once finished just reboots.
Click to expand...
Click to collapse
After restarting around 3 times its finally booted.. how odd
mrsweet1991 said:
After restarting around 3 times its finally booted.. how odd
Click to expand...
Click to collapse
ok, I keep getting optimising apps on every boot so not too sure why that is, but storage space running out is gone and encryption is also disabled. One thing however is Elelemntalx app shows the default overclock being used and not exceeding 2265,, however if I go into CPU settings I see 3033 as on option but when selected it won't change the overclock above the default max
mrsweet1991 said:
ok, I keep getting optimising apps on every boot so not too sure why that is, but storage space running out is gone and encryption is also disabled. One thing however is Elelemntalx app shows the default overclock being used and not exceeding 2265,, however if I go into CPU settings I see 3033 as on option but when selected it won't change the overclock above the default max
Click to expand...
Click to collapse
its because youre at 40% battery or less. on 5.1, the cpu automatically drops to 2265. at 20%, it drops even more. nothing you can do about it at this point
simms22 said:
its because youre at 40% battery or less. on 5.1, the cpu automatically drops to 2265. at 20%, it drops even more. nothing you can do about it at this point
Click to expand...
Click to collapse
Sweeet waiting for it to get another 20 odd percent then see if it gets 3033
Vindicator kernel supports 2.9ghz CPU OC and 700mhz GPU. Optipop or benzo ROM are both pretty optimized.
Related
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Make a backup in TWRP, wipe your system partition, Flash the ROM zip and the GAPPS zip, reboot, profit. If anything fails you can roll back to your backup and try again.
Real simple. Download the latest built as well as the latest google apps (gapps)
Reboot to TWRP
Do a backup, so you have a restore point if something happens
Go to wipe->advanced wipe and choose both caches, system and data. DO NOT wipe internal storage
Go to install, choose the ROM and gapps and install them
Reboot
You will now be on the latest. You will have to set your phone up again, and all your text messages, home screen, act will be gone but all your stuff on your sdcard (internal storage) will be untouched.
You can also get real ambitious and make backups with something like titanium backup of all your apps and data and restore it after booting PN, but try to not back up system apps or system data (it should be an option... I dont know, I never use tibu). The main thing you lose without backing up is texts, I usually just deal with it/redownload apps/set up home screen again.
On future updates, unless there are major changes and its indicated by a majority of people in the PN thread, just dirty flash.
That is, backup, wipe caches, install new ROM version( I wouldn't reflash gapps ) this will leave all your apps, settings, ect... But should only be done when flashing the same or a very similar ROM. If you dirty flash and experience problems, go back and clean flash as I first instructed.
So I should not worry about flashing the new 32r radio?
shouldnt this have been one of the first things to learn BEFORE you ever rooted your phone? yea, nice job jumping in before learning your way around. i bet you even used a toolkit to root your device..
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
roy.garlington said:
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
Click to expand...
Click to collapse
no tool kit? ok, your -1 on not learning before rooting has a +1 right by it, for rooting the proper way. you just might earn some respect
Hey there simbo, what do you say about flashing the radio?
Sure. Or don't.
Whatever.
The radio is pretty separate from android. Its basically drivers to tell you phone how to use hardware.
FI has certain requirements for activation that may check what radio you have, but outside of that run what ever works good for you., its not going to for sure be any specific one. Newer may often be better but its not uncommon that an older one may work a little better.
Different apps can help you monitor (I dunno which ones... But I know its a thing ), you can also go into about phone -> status -> sim status and check signal strength where lower dBm is better(well a lower numeric value... Its technically a negative number, so higher is better i.e. -113 is worse then -104). This will vary slightly minute to minute and place to place so just taking a glance once won't really settle it for you
I just use it for a day or two, pay attention to how my signal is (just kinda how often did I have decent # of bars, nothing scientific), and check battery stats clicking on cell standby and looking at % of time with out signal.
roy.garlington said:
Hey there simbo, what do you say about flashing the radio?
Click to expand...
Click to collapse
youre choice. you can try any of the radios, from previous android versions, on any android version. they arent specific. im using the 27R radio. whichever one works best for you, thats whats important
roy.garlington said:
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Click to expand...
Click to collapse
Well, it's all very easy if you read a little. Still i will give you one extra tip in case you start flashing all kinds of roms: You unlocked your bootloader. Before doing that you enabled "OEM unlocking" in 'Developer options'. Leave that enabled (this setting is 'sticky'. even when you wipe the device)!!!!. Leaving OEM unlocking enabled will disable "Device Protection" that causes sometimes a 72 hours lock-out from your Google account.
I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.
Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.
TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.
ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.
Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???
Finally got my phone yesterday and I had some questions. Perhaps some existing users with the phone can answer them.
For the sake of this post, keep the following in mind about the status of my phone:
bootloader - unlocked
custom recovery installed - twrp 3.0.3-1
1. My phone came, it had OOS 3.5.4 installed on it. After I unlocked the bootloader and put twrp on there, I couldn't help trying to get OOS 4.0.2 on there. I followed the 3rd post here to update to 4.0.2: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Regardless of whether or not I try to flash su or magisk, I get the dm-verity message upon booting to system. I just hit the power button to skip the message, but is this normal with flashing the nougat oos? These roms are tock, so I would assume nothing would trigger it unless it's being triggered by twrp? I tried flashing the dm-verity-encryption-fix 5.1 and this doesn't seem to do anything either.
NOTE: I don't get any dm-verity message UNTIL after I flash the stock OOS 4.0.*
with 3.5.4 there were no problems even with custom recovery and magisk installed.
2. I feel really stupid, but I have been wanting to format the system to F2FS partition. In twrp I goto wip --> advanced wipe --> check "system" --> change partition --> check F2FS --> and continue... It says System has been formwatted, if I reboot it tells me there is no OS, so I go back into twrp and reflash the full stock 4.0.2 rom, but then each time my partition goes back to Ext4. Am I missing something??
3. In OOS, is there a way to create folders in the app drawer? I would like to organize my apps.
4. Has anyone figured out a way to get Xposed to work on 4.0.2?
Overall experience with my new phone; I absolutely LOVE it!!!! The phone is fast as hell and responsive as all getout. I honestly think this is the best phone I have ever owned. The fingerprint scanner is insanely quick at unlocking the phone. Initially I was concerned about the physical size of the phone, but it's actually not bad. It's large, but still easy-ish to hold and use. The back camera seems to be VERY sensitive to movement, so I see what people mean when they say images come out a little blurry. The front facing camera is actually really good though IMO. It seems to take pics fine and focus much better on the image.
My wifi signal isn't bad. I don't seem to have any issues with this, and the battery is phenomenal too. I installed forcedoze and leandroid and this phone just isn't phazed by anything. I look forward to using it more today to put it to the test.
1. That's normal. Everyone with TWRP and OOS4.0+ has that message at boot.
2. I am not qualified to answer this question. Sorry.
3. No, but you can download a custom launcher that may be able to do that. I'm 99.98% sure that there is a custom launcher on the Play Store that can do that.
4. Nope. Xposed has not yet been developed for Android Nougat.
Awesome, thanks for your reply! I was concerned at first I was doing something wrong with the install since I kept getting that dm-verity warning.
2. You cannot and really shouldn't format system to f2fs without custom kernel support.. even then.. why would you do it?
Data is already f2fs and it is enough.
V 2.0 said:
2. You cannot and really shouldn't format system to f2fs without custom kernel support.. even then.. why would you do it?
Data is already f2fs and it is enough.
Click to expand...
Click to collapse
Well from what I read F2FS would be the better option since it's optimized for UFS. I know Data is already F2FS, but I figured if system was formatted as f2fs as well, it would launch stuff quicker (even though it's already super fast imo)
Just don't. As I said, won't work on stock for sure and there are no custom kernels yet. Even then I say don't.
Thanks for the feedback! I appreciate it! I'll leave the filesystem the way it is.
Do any of you use custom launchers? From what I'm seeing Apus Launcher and Nova Launcher are the recommended ones, but I'm leaning towards Nova Launcher to better organize my app drawer. Any suggestions?
I am happy with stock launcher, but if you wanna organize app drawer better I also heard only the best about Nova.
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
SynGreis said:
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
Click to expand...
Click to collapse
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
which one do you suggest? i dont see much of a selection.
SynGreis said:
which one do you suggest? i dont see much of a selection.
Click to expand...
Click to collapse
Right now there really aren't any, although there are a few in development, such as AOSP. I think the initial high price, specialized hardware & relative unpopularity has not helped attract any serious development.
I've noticed that ROM development has decreased significantly in the last few years. I remember the days of the Samsung Galaxy Nexus & the HTC Evo 4G where it seemed as if there was a new ROM released every week. I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult.
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
mattwheat said:
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
Click to expand...
Click to collapse
Mine showed as in rog 2 the last time I reloaded the OS. It's because it searches for "phone 2" and randomly guesses. No biggie, just fix it in the settings. No issues here from playstore, if you do it's common on every Android phone and fixable by clearing the data from the app. Maybe you should reflash the stock firmware? I don't see why you would call this phone ****ty. It's basically running AOSP stock except some theming from Razer. I fixed some freezing issues by reseating the Sim and SD card that I have. This thing rocks, just saying.
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
matt that might be just you i havent experienced any issues with this phone whatsoever.
"I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult."
can you provide more info on this A/B partition? id love to see what customizable stuff i can do with this.
mattwheat said:
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
Click to expand...
Click to collapse
The freezing is due to a bug in Google Chrome. All you have to do to fix this issue is roll back the app version to 72 because version 76 doesn't work on our RP2.
Edit: uncheck auto update
Only freeze I had so far was with the infamous switch switch to the tele lens. Not a single other issue with software.
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
MasterThiefGarrett said:
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
Click to expand...
Click to collapse
Take this with a grain of salt, as I just got the RP2, but its the most responsive, "sticky" feeling Android phone I've used. 120hz is like night and day to me.
On a related note, Firefox Fenix with webrender enabled feels significantly more responsive than Chromium atm, as it seemingly renders the whole page instead of stuttering as you scroll like Chrome.
JDBarlow said:
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
Click to expand...
Click to collapse
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
SynGreis said:
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
Click to expand...
Click to collapse
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
duplicate post
JDBarlow said:
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
Click to expand...
Click to collapse
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
SynGreis said:
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
Click to expand...
Click to collapse
So are you on the global version? If so let it update to MR2 and fastboot flash boot arter97 r12 and you'll be just fine.
Which version are you running then to get stuck on boot logo?
Edit: if you want to stay on MR1 then flash arter97 r11
i tried updating to mr2 but says installation failed.
all i do is
faatboot flash boot kernal.img?
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
JDBarlow said:
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
Click to expand...
Click to collapse
My only question is, which version zip of magisk did you use in TWRP to flash? 20 or the latest beta? I'm rooted now with a modded boot.img that someone else used the canary/latest beta. Just don't want to screw myself and end up having to flash mr1 again then taking the update.