Thanks to all these posts from Secretcow and changguangyu for enabling the community to switch to the CN ROM, I took the majority of information from these guides :
https://forum.xda-developers.com/red-magic-3/how-to/guide-unlocking-red-magic-3s-bootloader-t3935630
https://forum.xda-developers.com/red-magic-3/how-to/guide-flash-global-rom-to-chinese-rom-t3937505
https://forum.xda-developers.com/red-magic-3/how-to/guide-flashing-twrp-granting-root-t3936148
https://forum.xda-developers.com/red-magic-3/how-to/guide-install-gapps-red-magic-3-t3933153
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
I successfully managed to migrate over to the CN ROM after some trial and error and would like to share with the community a step-by-step guide on making your expensive paperweight less so. As usual, I take no responsibility if you make your phone an even more expensive paperweight due to my guide. You have been warned! I also apologize for my poor formatting, it was quite a pain trying to format this huge wall of text. The actual guide begins when you see bigger looking and bold text that marks the start of the guide.
Before I get on with the guide, I'm going to list out the pros and cons between the CN and Global ROM so that you would have a better idea of what you would be sacrificing and gaining from switching to the CN ROM.
Both ROMs do not have Bluetooth aptX support whatsoever. Whoever that did the spec sheet on GSMarena for the Red Magic 3 is incorrect. It only officially supports the AAC Bluetooth codec. Using https://github.com/gjf/gjf_bt to enable aptX & aptX-HD did not work for me. Volume output on the Global ROM is also louder compared to the CN ROM. Only when you enable DTS:X and disable it on the CN ROM. Disabling DTX:X and restarting the phone solved the issue.
DC dimming is also supported on both ROM's, with the CN ROM natively (Actually unusable, the colour depth is reduced so drastically to the point where the colours become blocky shades) and the Global ROM using the Darker app https://play.google.com/store/apps/details?id=com.mlhg.screenfilter&hl=en with the forced minimum hardware brightness option ticked and the phone's default brightness slider slightly above 0%. Works on CN ROM too but the brightness slider can be kept at 0% and it still works.
DTS:X Ultra only works on audio devices plugged into the headphone jack on the phone. (CN ROM only when I wrote this) It does not support the stereo speakers on the phone, contrary to what the marketing material for this phone implies. The stereo speakers for this phone are not very good, and not true stereo (earpiece speaker is only for highs). Marketing material implies that it is true stereo and half-assed reviewers do not point this out! Personally, I do not think it is worth the hassle of switching to the CN ROM for DTS:X Ultra, in my opinion, it's not good enough. (just 3 presets you can choose from, music, movie and game. There is no proper sound customization like Dolby Atmos for mobile. The overall effect, however, is fairly good in my opinion, gentle, widened, fairly natural soundstage with boosted sub-bass, bass and or highs depending on the preset. If you already have nice open sounding cans, it would be of little benefit to you. )
Pros of Global Global EN v2.10 ROM:
Ability to switch the default launcher easily
Picture-in-picture mode for Whatsapp in Game Space
Extremely stock OS with zero bloat*
4G connection signal seems better**
Lower and more stable temps while gaming***
*So stock that it is missing core features
**Based on what the signal icon is showing
***Based on Game Space temps while playing on Auto and Super setting (FPS is worse compared to CN ROM even if temps are lower)
Cons of Global EN v2.10 ROM:
Unusable (tons of infuriating bugs and instability)*
No Qualcomm quick-charge support (up to 18w only)
Feels slightly less responsive to CN ROM**
DTS:X Ultra Missing
No full-screen gestures
*The bug list includes: Touching the shoulder triggers while watching youtube videos pops up the player controls, alarm seems to not work on Mondays, ringing 30+ mins late, once in awhile the OS freezes and reboots on its own, fingerprint sensor randomly disables itself etc.
**Based on "Feelings". No actual tests were performed
Pros of CN ROM V2.34:
Root is available (Magisk)
OS is gaming themed
Better gaming performance
Super mode in Game Space works
Smooth, stable and bug-free OS
4D shock is implemented in the OS*
27W Qualcomm Quickcharge 4+ Support
The typical quality of life features from most android phones **
DTS:X Ultra Support (Using 3.5mm Jack only)
Better standby time***
*When you perform gestures or touch certain elements, the phone selectively vibrates only that portion of the screen. It sounds like a gimmick but this feature is nice to have, it makes the touch screen feel more "physical". More companies should implement this feature, it makes the phone much more satisfying to use. Unfortunately, the stock keyboard does not support this feature.
**Like double-tap to wake, palm touch to lock. Ability to selectively keep apps running and a "close all recent" button when multitasking etc.
***Based on "Feelings". No actual tests were performed
Cons of CN ROM V2.34:
Bloat city. The amount of bloat present in the CN ROM is nuts
Worse battery life while actively using it*
No Picture-in-picture mode for Whatsapp in Game Space
Changing the default launcher is a pain in the ass (https://forum.xda-developers.com/red-magic-3/help/launcher-t3935186/page2)
Some useless CN features baked in the OS
Some parts of the ROM are still in Chinese
No option to change the display size
Notifications are disabled for apps by default
Higher temps while in gaming mode. Gets insanely hot when Super mode is enabled in Game Space. About 1-3C hotter in Auto. About 10-15C hotter in Super**
*Based on "Feelings". No actual tests were performed
**The temps climb much more slowly compared to global ROM. Global ROM always instantly hits 40C average while the CN one slowly climbs to about 41-43C
Now let's get on with the actual steps!
If you are coming in fresh with no data, you can skip this part. Otherwise, make sure you backup your phone with a generic backup program (for photos, music, contacts, messages etc). Changing to the CN ROM will result in a reformat as unlocking the bootloader will force the phone to reformat.
As a safety precaution, please charge your phone to at least 50% before attempting to do any flashing
I attempted all this on a USB 3.0 port and an AMD Ryzen system with no issues at all. You might want to try on a USB 2.0 port if for some reason USB 3.0 does not work for you
Keep the phone connected to your PC at all times
All commands are put in " ", so enter only the text and not the double quotation marks
Firstly, you have to unlock the bootloader on your phone:
Get minimal ADB and fastboot here:
https://forum.xda-developers.com/showthread.php?t=2317790, make sure you take note of where you installed the files to!
Go to developer options on your phone and ("About Phone" > "Build Number"), tap on it until the developer options are enabled) enable USB Debugging and OEM Unlock
Connect your phone to the computer
Allow the request for USB debugging on your phone
Open the command prompt and run as administrator
cd to the location of where you installed ADB drivers to in the command prompt ("cd C:\ADB", for example)
In the command prompt, type "adb devices". If the previous steps were done correctly, a device will be shown
In the command prompt, type "adb reboot bootloader"
Once your phone has rebooted to the bootloader, type in the command prompt "fastboot devices". Your phone should show up in the list of fastboot devices.
Then, enter in "fastboot oem nubia_unlock NUBIA_NX629J"
Finally, enter in "fastboot flashing unlock"
Use the volume up and down keys on your phone to select the option and the Power key to confirm the option to reboot into the system
Installing the CN ROM:
Download the Chinese ROM from http://ui.nubia.cn/rom/detail/62
Go to "Settings" > "System Update" > "Options" (the three dots on the top right corner) > "Local update".
Select the CN ROM which you downloaded and click on "Install now"
Wait for the phone to finish updating and boot back into the welcome screen
Flashing Magisk and GApps:
*TWRP is not permanent and will always be reflashed to the stock recovery when you boot into the OS until someone finds a way to make it permanent
Seems like its permanent after you flash Magisk, you will need to enter in your phone password to enter TWRP
Download TWRP from https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482(choose the latest version), GApps Pico from https://opengapps.org/("ARM64" > "9.0" > "Pico") and Magisk from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Latest stable version)
Put GApps and Magisk on your phone storage and the TWRP .img file in your ADB folder
Restart the phone. While it is restarting hold down the volume down button while it restarts to boot into fastboot mode
Type in the command prompt"fastboot devices"with the directory still being in the ADB folder to check that your device is shown
Then, enter in "fastboot oem nubia_unlock NUBIA_NX629J"
To flash TWRP, enter in "fastboot flash recovery <name of recovery.img>" (omitting the arrows)
Once done, reboot to recovery in the fastboot menu
When in TWRP, go to install, install the Magisk zip first then GApps Pico. Swipe to install
While still in TWRP, go to wipe, advanced wipe, check Dalvik Art Cache, Data, Internal Storage and cache and swipe to wipe
Reboot your phone to the system in TWRP, during the google setup, skip as many steps as possible (gestures don't work when in the default google setup)
Continue with the nubia setup. Once done, download the Magisk Manager to allow root requests and install modules (at your own risk!) https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Allow unknown sources installation and install the Magisk Manager apk. Run the app and allow it to patch the system. Restart and you are done!
I wanted to mention that Carrier Aggregation doesn't work for me on the Global nor Chinese ROM.
The Chinese ROM has an option in the settings menu to enable Carrier Aggregation but it does nothing.
If anyone can get it to work, I'd really appreciate it.
nerdydesi said:
I wanted to mention that Carrier Aggregation doesn't work for me on the Global nor Chinese ROM.
The Chinese ROM has an option in the settings menu to enable Carrier Aggregation but it does nothing.
If anyone can get it to work, I'd really appreciate it.
Click to expand...
Click to collapse
How do you know if carrier aggregation is working? Is it when the 4G+ icon is shown on the phone? Mine seems to have the +. I didn't do a speed test of the Global ROM vs the CN ROM as I have very little data to spare.
Outstanding guide, really well thought out and organized!
A few extras everyone on the global rom should be using (root needed):
For apt-x and double bandwith sbc (should work on global & cn): https://github.com/Magisk-Modules-Repo/gjf_bt
Making the speakers sound really good on global: https://github.com/Magisk-Modules-Repo/ViPER4AndroidFX-Legacy (Go the v4a app. Under phone Speaker turn on Master Power, & copy my FIREqualizer custom settings, doesnt have to be exact. https://photos.app.goo.gl/zDgqgnqKM4RvuM9S7 )
Wifi Bodning (double your wifi bandwith): https://github.com/Magisk-Modules-Repo/wifi-bonding
Sentinei said:
How do you know if carrier aggregation is working? Is it when the 4G+ icon is shown on the phone? Mine seems to have the +. I didn't do a speed test of the Global ROM vs the CN ROM as I have very little data to spare.
Click to expand...
Click to collapse
Yes, the LTE+ should indicate carrier aggregation is enabled. But I've never seen that icon on my phone after running speedtests and downloading large files.
Who is your carrier? I've tried both Verizon Wireless and Tmobile USA.
Thanks very much.
Success after few attempt.
nerdydesi said:
Yes, the LTE+ should indicate carrier aggregation is enabled. But I've never seen that icon on my phone after running speedtests and downloading large files.
Who is your carrier? I've tried both Verizon Wireless and Tmobile USA.
Click to expand...
Click to collapse
Sorry, don't think I can help, I'm on Singtel all the way in Singapore. That said, I did some research and came across a website called https://www.frequencycheck.com/ that attempts to check if your phone is compatible with the cellular network in that country. The red magic 3 managed to support 2/3 of the 4G bands available on Verizon wireless https://www.frequencycheck.com/carrier-compatibility/mL6W5/verizon-wireless-united-states/devices?utf8=%E2%9C%93&q%5Bfull_name_cont%5D=red+magic+3&q%5Bdevice_brand_id_eq%5D=&commit=Search and 3/5 bands on T-Mobile https://www.frequencycheck.com/carrier-compatibility/w4mjn/t-mobile-united-states/devices?utf8=%E2%9C%93&q%5Bfull_name_cont%5D=red+magic+3&q%5Bdevice_brand_id_eq%5D=&commit=Search while it supported 3/3 bands on my Singtel network https://www.frequencycheck.com/carrier-compatibility/bLYG4/singtel-singapore/devices?utf8=%E2%9C%93&q%5Bfull_name_cont%5D=red+magic+3&q%5Bdevice_brand_id_eq%5D=&commit=Search Maybe its a hardware thing?
want to add some more. i just flash cn rom but it seems not compatible with flydigi waps 2.the shoulder button seems freeze when i use it in pubG, so i change back to global. now i gonna stick with global. and BTW my recovery is permanent (TWRP) dunno what happens. i do it just as told but its permanent.
elfee said:
want to add some more. i just flash cn rom but it seems not compatible with flydigi waps 2.the shoulder button seems freeze when i use it in pubG, so i change back to global. now i gonna stick with global. and BTW my recovery is permanent (TWRP) dunno what happens. i do it just as told but its permanent.
Click to expand...
Click to collapse
Yup, thanks for informing me, seems like TWRP becomes permanent after flashing Magisk I think? The last time I tried to boot into TWRP again before flashing Magisk it would boot back to the stock recovery which required a reflash of TWRP.
Secretcow said:
Outstanding guide, really well thought out and organized!
A few extras everyone on the global rom should be using (root needed):
For apt-x and double bandwith sbc (should work on global & cn): https://github.com/Magisk-Modules-Repo/gjf_bt
Making the speakers sound really good on global: https://github.com/Magisk-Modules-Repo/ViPER4AndroidFX-Legacy (Go the v4a app. Under phone Speaker turn on Master Power, & copy my FIREqualizer custom settings, doesnt have to be exact. https://photos.app.goo.gl/zDgqgnqKM4RvuM9S7 )
Wifi Bodning (double your wifi bandwith): https://github.com/Magisk-Modules-Repo/wifi-bonding
Click to expand...
Click to collapse
Thanks for the mentioning the extra modules, will probably try the aptx, aptx hd and sbc hd codec enabler when I have the time. I don't use Bluetooth much so its not a concern for me. So far I tested Ainur Sauron 12.08, V4A 2.7.1.0, Audio Modification Library v2.4 and ScreenCam Screen Recorder modules, all are working fine. I also installed Audio Compatibility Patch 1.7.3 as I was unsure as to how the new unofficial V4A worked, so I thought installing this module might fix something. Seems like you have to enable the master limiter in V4A for V4A to work. It probably works without ACP? V4A works, but for it to actually work requires too much fiddling with restarting processes, which makes it useless. The SBC HD + aptx + aptx HD module unfortunately does not seem to work, still unable to connect using aptx though I think the SBC HD codec did work. (Did not actually look at the Bluetooth log files, it's just based on what I heard)
So can i use the stock recovery to flash the CN rom without root?
Sentinei said:
Thanks to all these posts from Secretcow and changguangyu for enabling the community to switch to the CN ROM, I took the majority of information from these guides :
https://forum.xda-developers.com/red-magic-3/how-to/guide-unlocking-red-magic-3s-bootloader-t3935630
https://forum.xda-developers.com/red-magic-3/how-to/guide-flash-global-rom-to-chinese-rom-t3937505
https://forum.xda-developers.com/red-magic-3/how-to/guide-flashing-twrp-granting-root-t3936148
https://forum.xda-developers.com/red-magic-3/how-to/guide-install-gapps-red-magic-3-t3933153
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
I successfully managed to migrate over to the CN ROM after some trial and error and would like to share with the community a step-by-step guide on making your expensive paperweight less so. As usual, I take no responsibility if you make your phone an even more expensive paperweight due to my guide. You have been warned! I also apologize for my poor formatting, it was quite a pain trying to format this huge wall of text. The actual guide begins when you see bigger looking and bold text that marks the start of the guide.
Before I get on with the guide, I'm going to list out the pros and cons between the CN and Global ROM so that you would have a better idea of what you would be sacrificing and gaining from switching to the CN ROM.
Both ROMs do not have Bluetooth aptX support whatsoever. Whoever that did the spec sheet on GSMarena for the Red Magic 3 is incorrect. It only officially supports AAC. Volume output on the Global ROM at the same volume level is also louder compared to the CN ROM strangely. Using poweramp with the Hi-Res option at 44.1Khz 24bit fixed the issue on the CN ROM (unusable, when phone screen switches off, the sound does too even after enabling the options to fix that in poweramp)
DC dimming is also supported on both ROM's, with the CN ROM natively (Actually unusable, the colour depth is reduced so drastically to the point where the colours become blocky shades) and the Global ROM using the Darker app https://play.google.com/store/apps/details?id=com.mlhg.screenfilter&hl=en with the forced minimum hardware brightness option ticked and the phone's default brightness slider slightly above 0%. Works on CN ROM too but the brightness slider can be kept at 0% and it still works.
DTS:X Ultra only works on audio devices plugged into the headphone jack on the phone. (CN ROM only when I wrote this) It does not support the stereo speakers on the phone, contrary to what the marketing material for this phone implies. The stereo speakers for this phone are not very good, and not true stereo (earpiece speaker is only for highs). Marketing material implies that it is true stereo and half-assed reviewers do not point this out! Personally, I do not think it is worth the hassle of switching to the CN ROM for DTS:X Ultra, in my opinion, it's not good enough. (just 3 presets you can choose from, music, movie and game. There is no proper sound customization like Dolby Atmos for mobile. The overall effect, however, is fairly good in my opinion, gentle, widened, fairly natural soundstage with boosted sub-bass, bass and or highs depending on the preset. If you already have nice open sounding cans, it would be of little benefit to you. )
Pros of Global Global EN v2.10 ROM:
Ability to switch the default launcher easily
Picture-in-picture mode for Whatsapp in Game Space
Extremely stock OS with zero bloat*
4G connection signal seems better**
Lower and more stable temps while gaming***
*So stock that it is missing core features
**Based on what the signal icon is showing
***Based on Game Space temps while playing on Auto and Super setting (FPS is worse compared to CN ROM even if temps are lower)
Cons of Global EN v2.10 ROM:
Unusable (tons of infuriating bugs and instability)*
No Qualcomm quick-charge support (up to 18w only)
Feels slightly less responsive to CN ROM**
DTS:X Ultra Missing
No full-screen gestures
*The bug list includes: Touching the shoulder triggers while watching youtube videos pops up the player controls, alarm seems to not work on Mondays, ringing 30+ mins late, once in awhile the OS freezes and reboots on its own, fingerprint sensor randomly disables itself etc.
**Based on "Feelings". No actual tests were performed
Pros of CN ROM V2.34:
Root is available (Magisk)
OS is gaming themed
Better gaming performance
Super mode in Game Space works
Smooth, stable and bug-free OS
4D shock is implemented in the OS*
27W Qualcomm Quickcharge 4+ Support
The typical quality of life features from most android phones **
DTS:X Ultra Support (Using 3.5mm Jack only)
Better standby time***
*When you perform gestures or touch certain elements, the phone selectively vibrates only that portion of the screen. It sounds like a gimmick but this feature is nice to have, it makes the touch screen feel more "physical". More companies should implement this feature, it makes the phone much more satisfying to use. Unfortunately, the stock keyboard does not support this feature.
**Like double-tap to wake, palm touch to lock. Ability to selectively keep apps running and a "close all recent" button when multitasking etc.
***Based on "Feelings". No actual tests were performed
Cons of CN ROM V2.34:
Bloat city. The amount of bloat present in the CN ROM is nuts
Worse battery life while actively using it*
No Picture-in-picture mode for Whatsapp in Game Space
Changing the default launcher is a pain in the ass (https://forum.xda-developers.com/red-magic-3/help/launcher-t3935186/page2)
Some useless CN features baked in the OS
Some parts of the ROM are still in Chinese
No option to change the display size
Notifications are disabled for apps by default
Higher temps while in gaming mode. Gets insanely hot when Super mode is enabled in Game Space. About 1-3C hotter in Auto. About 10-15C hotter in Super**
*Based on "Feelings". No actual tests were performed
**The temps climb much more slowly compared to global ROM. Global ROM always instantly hits 40C average while the CN one slowly climbs to about 41-43C
Now let's get on with the actual steps!
If you are coming in fresh with no data, you can skip this part. Otherwise, make sure you backup your phone with a generic backup program (for photos, music, contacts, messages etc). Changing to the CN ROM will result in a reformat as unlocking the bootloader will force the phone to reformat.
As a safety precaution, please charge your phone to at least 50% before attempting to do any flashing
I attempted all this on a USB 3.0 port and an AMD Ryzen system with no issues at all. You might want to try on a USB 2.0 port if for some reason USB 3.0 does not work for you
Keep the phone connected to your PC at all times
All commands are put in " ", so enter only the text and not the double quotation marks
Firstly, you have to unlock the bootloader on your phone:
Get minimal ADB and fastboot here:
https://forum.xda-developers.com/showthread.php?t=2317790, make sure you take note of where you installed the files to!
Go to developer options on your phone and ("About Phone" > "Build Number"), tap on it until the developer options are enabled) enable USB Debugging and OEM Unlock
Connect your phone to the computer
Allow the request for USB debugging on your phone
Open the command prompt and run as administrator
cd to the location of where you installed ADB drivers to in the command prompt ("cd C:\ADB", for example)
In the command prompt, type "adb devices". If the previous steps were done correctly, a device will be shown
In the command prompt, type "adb reboot bootloader"
Once your phone has rebooted to the bootloader, type in the command prompt "fastboot devices". Your phone should show up in the list of fastboot devices.
Then, enter in "fastboot oem nubia_unlock NUBIA_NX629J"
Finally, enter in "fastboot flashing unlock"
Use the volume up and down keys on your phone to select the option and the Power key to confirm the option to reboot into the system
Installing the CN ROM:
Download the Chinese ROM from http://ui.nubia.cn/rom/detail/62
Go to "Settings" > "System Update" > "Options" (the three dots on the top right corner) > "Local update".
Select the CN ROM which you downloaded and click on "Install now"
Wait for the phone to finish updating and boot back into the welcome screen
Flashing Magisk and GApps:
*TWRP is not permanent and will always be reflashed to the stock recovery when you boot into the OS until someone finds a way to make it permanent
Seems like its permanent after you flash Magisk, you will need to enter in your phone password to enter TWRP
Download TWRP from https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482(choose the latest version), GApps Pico from https://opengapps.org/("ARM64" > "9.0" > "Pico") and Magisk from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Latest stable version)
Put GApps and Magisk on your phone storage and the TWRP .img file in your ADB folder
Restart the phone. While it is restarting hold down the volume down button while it restarts to boot into fastboot mode
Type in the command prompt"fastboot devices"with the directory still being in the ADB folder to check that your device is shown
Then, enter in "fastboot oem nubia_unlock NUBIA_NX629J"
To flash TWRP, enter in "fastboot flash recovery <name of recovery.img>" (omitting the arrows)
Once done, reboot to recovery in the fastboot menu
When in TWRP, go to install, install the Magisk zip first then GApps Pico. Swipe to install
While still in TWRP, go to wipe, advanced wipe, check Dalvik Art Cache, Data, Internal Storage and cache and swipe to wipe
Reboot your phone to the system in TWRP, during the google setup, skip as many steps as possible (gestures don't work when in the default google setup)
Continue with the nubia setup. Once done, download the Magisk Manager to allow root requests and install modules (at your own risk!) https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Allow unknown sources installation and install the Magisk Manager apk. Run the app and allow it to patch the system. Restart and you are done!
Click to expand...
Click to collapse
pls help me ! i buy nubia red magic 3s, and setup the same nubia red magic 3. them is code name N629J, the same TWRP and Root
KushBeaver said:
So can i use the stock recovery to flash the CN rom without root?
Click to expand...
Click to collapse
Yes, but without root you cannot flash GApps.
chipheo62 said:
pls help me ! i buy nubia red magic 3s, and setup the same nubia red magic 3. them is code name N629J, the same TWRP and Root
Click to expand...
Click to collapse
Sorry, can't help as it's a different phone compared to the original red magic 3. You can try my guide, but there is a very high chance that trying to flash this version of TWRP for the red magic 3 will brick your phone.
I want to publish a ROM from China Forum, but I don't have permission to post it.
死求了鸭 said:
I want to publish a ROM from China Forum, but I don't have permission to post it.
Click to expand...
Click to collapse
You can publish any ROM in ROMs, KERNELS... But if you want to publish a ROM you have to provide the kernel source of the ROM
Enviado desde mi Redmi 3S mediante Tapatalk
elfee said:
want to add some more. i just flash cn rom but it seems not compatible with flydigi waps 2.the shoulder button seems freeze when i use it in pubG, so i change back to global. now i gonna stick with global. and BTW my recovery is permanent (TWRP) dunno what happens. i do it just as told but its permanent.
Click to expand...
Click to collapse
How did you change back to global? Using twrp or stock recovery? Im try using stock recovery, but it always fails at 25%.
i using cn romv 2.35 ... so far so good... if i want to update v2.36? direct update at system or what???
Does cn fw have AOD?
Ray-DX said:
How did you change back to global? Using twrp or stock recovery? Im try using stock recovery, but it always fails at 25%.
Click to expand...
Click to collapse
I have the same problem, 25% the flash fails with stock recovery by OTG
Related
I decided to create this thread so that people don't need to hunt through the large discussion threads.
Note that this is *not* a thread for discussing the ROM.
I will update these posts based on *confirmed* bugs. By that, I mean two or more people confirming the bug on pure cm 10.2 - not using other kernels.
Also the ROM must have had a clean install (wipe data, cache, system) and not flashed over a previous install.
It's also worth reading what CyanogenMod have to say about the 10.2 nightlies (http://www.cyanogenmod.org/blog/this-week-in-cm-aug-16-2013) as it gives you an idea of what to expect from the ROM at this stage.
ROM is available here: http://download.cyanogenmod.com/?device=jfltexx
The official ROM thread is here: http://forum.xda-developers.com/showthread.php?p=42387383
The discussion thread is here: http://forum.xda-developers.com/showthread.php?p=41851449
Only flash the ROM with the latest CWM (http://www.clockworkmod.com/rommanager), TWRP 2.6.0 (http://techerrata.com/browse/twrp2/jfltexx), or the latest PhilZ (http://d-h.st/users/philz_touch/?fld_id=16685#files)
DO NOT use earlier versions of PhilZ (prior to 5.13.9) or you will have boot (no animation, hang on updating apps) and installation (no signal, no baseband) problems.
DO NOT use TWRP 2.6.1 as it fails to flash the ROM.
First time cm 10.2 users please see post #4 for some useful tips.
Sent from my GT-I9505
Bug list
Bluetooth
(Does not affect all users and may be related to BT 4.0 devices)
No audio on BT; doesn't connect/disconnect properly.
Compass
The compass doesn't work "out of the box".
Solution:
- when first using an app requiring the compass (Google maps, GPS status, etc), the compass is "frozen" until it is calibrated (rotate the phone 2-3 times about each of its three axes).
- the compass will then move, but very erraticly, often going around in circles
- if you exit the app and then reopen it, the compass will work properly from then on.
DSP
DSP distorts sounds. This affects music play back.
Workaround: freeze DSP using TB
Mobile network modes
(Not everyone has this problem as it is language related)
- It is set to: GSM/WCDMA/LTE, but when opening the drop-down menu it selects the option LTE (which is two above GSM/WCDMA/LTE).
- Selecting some options may cause an FC.
Network operator name
Name shows correctly on the notification shade, but only numbers are shown in Settings/Wireless&Networks/Mobile networks/Network operators
Apps
Camera
- HDR doesn't produce a proper HDR image. It only takes one low exposure image.
- Some people have been getting occasional green lines on photos taken using the front-facing camera.
- In Scene or HDR mode, touching on the screen does not refocus.
- (0908 ) Video recording at 1080p will cause the phone to reboot.
- (0908 ) Exposure is locked at the value of the first photo taken (if taken without flash). Subsequent photos use the same exposure as the first photo.
Workaround: change the flash mode to automatic then change it to none. Then it will work properly. But this needs to be done each time the camera app is started.
File Manager
(1113: reintroduced ) In root access mode the bookmark for the internal SD card points to /storage/emulated/0 which doesn't exist.
Workaround: bookmark /data/media/0 or /storage/sdcard0
Terminal
- su doesn't inherit PATH if it was previously modified by export.
- Arrow keys don't work properly in su mode.
Fixed
List of fixed bugs (version fixed)
Headphone mic doesn't work (20130818 )
Phone picks up sound from the phone microphones.
Workaround: keep the phone close to you.
Home key long press (20130818 )
Changing the option in Settings/Buttons/Home Button:Long press doesn't actually change the long press behaviour of the Home button.
Key backlight (20130827)
There is no longer an option to disable the backlight on the menu and back keys.
Workaround: flash this http://db.tt/evvZLhkx. Note that if you wiped /data then you must flash this file *after* the ROM has booted for the first time.
Lock screen (20130924)
If the icons of the shortcuts are changed, they must all be changed at the same time otherwise the ones that were previously changed revert to the original app icon.
Quick Settings panel
- (0924 or earlier) Orientation tile: it doesn't lock/unlock screen rotation immediately. It needs a screen change (such as bringing up the recent app list) to take effect. (20131001)
Random reboots
(0909) Some users get random reboots.
Root cause: bug in Chrome beta. See http://forum.xda-developers.com/showthread.php?p=45642265
SELinux status (20130818 )
Repeated taping on the SELinux status in Settings/About phone will freeze the phone and cause it to reboot after some time.
Sound recording (20131011)
Volume is very low in Sound Recorder and video recordings.
Partial workaround: use Smart Voice Recorder https://play.google.com/store/apps/details?id=com.andrwq.recorder and disable automatic gain control.
Workaround: use ktoonsez kernel and faux sound control app to increase the microphone gain.
Super user (20130815)
Does not work properly after a clean install.
Workaround: change Root access to Apps and ADB in Settings/Developer options
Apps
Camera
- No option to save to external SD card. This may be by design rather than a bug. (20130821)
Workaround: use Gallery2.apk from cm 10.1
- (1017) Note: cm are working in the camera. The camera will sometimes hang, often after using video. Force closing it results in a "Can't connect to camera" message. A reboot is required to reactivate the camera. (20131021)
File Manager (20130918 )
In root access mode the bookmark for the internal SD card points to /storage/emulated/0 which doesn't exist.
Workaround: bookmark /data/media/0
Trebuchet
- Icons in folders disappear after a while. (20130817)
Workaround: use a different launcher
- When icon labels are hidden, the label on an app will reappear if it is updated. (20131001)
Terminal
- (0918 ) In su mode, /sdcard points to /storage/emulated/legacy (/data/media/legacy), which is empty, instead of /storage/emulated/0 (/data/media/0). (20131011)
First time users
A few things you need to know:
Developer options
Only shows up in Settings when you tap 7 times on the Build number in Settings/About phone.
Reboot options on Power menu
Check Advanced reboot in Settings/Developer options.
ADB
For your PC to get ADB access, enable USB debugging in Settings/Developer options.
Watch your phone when you first run ADB and allow the PC access to your phone.
Internal SD card
With Android 4.2.2 (or was it earlier?) the internal SD card is now mounted at /data/media/0 in order to support multiple user profiles. Your files may still be in /data/media/legacy.
Sorry for repeating, but this information could be useful (cwm 6.0.3.6, cm10.2 nightly 14/08, previous firmware - cm10.1 nightly 13/08).
mreugene said:
Everything is ok after installing via last cwm and some magic
I had two minor bugs:
1. unable to update the software - fixed by readding the google account and cleaning dalvik cache.
2. crashes of keep, play music, google disc and youtube- fixed by reinstalling these programs.
Click to expand...
Click to collapse
Deleted
awesome
Glad to see this being worked on.
I had issues with the focal camera and would love some a2sd support. I had to go back to stock aosp but certainly wiling to do any testing if needed.
Very convenient.. Thanks!
Deleted
Just did a clean flash. Noticed directly that LTE didn't work. It says LTE in status menu. But no LTE in data connection. Not even HSDPA. Calls and Sms works.
Titanium backup doesn't work on 10.2 for me.
Sent from my GT-I9505 using Tapatalk 4
is there any mute calls or not?
Audioboxer said:
Titanium backup doesn't work on 10.2 for me.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Mohanned85 said:
is there any mute calls or not?
Click to expand...
Click to collapse
Take these questions to the discussion forum.
Sent from my GT-I9505
deezytg1 said:
Glad to see this being worked on.
I had issues with the focal camera and would love some a2sd support. I had to go back to stock aosp but certainly wiling to do any testing if needed.
Click to expand...
Click to collapse
I'm not a developer; I'm simply providing a list of bugs to help our community of cm 10.2 users.
Sent from my GT-I9505
Audioboxer said:
Titanium backup doesn't work on 10.2 for me.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Developer options
Only shows up in Settings when you tap 7 times on the Build number in Settings/About phone.
ADB
For your PC to get ADB access, enable USB debugging in Settings/Developer options.
Super user
Does not work after a clean install.
Workaround: change Root access to Apps and ADB in Settings/Developer options
OR
Install SuperSU from Play Store and install binaries
TB will work fine then...
bariz143 said:
Just did a clean flash. Noticed directly that LTE didn't work. It says LTE in status menu. But no LTE in data connection. Not even HSDPA. Calls and Sms works.
Click to expand...
Click to collapse
Went to the mall and saw LTE appears which I didn't expect to work since I've been on AOSP for a while without it. Quickly did a speed test and got 8 Mbps down and 3.5 up and this is with Sprint.
vboyz103 said:
Went to the mall and saw LTE appears which I didn't expect to work since I've been on AOSP for a while without it. Quickly did a speed test and got 8 Mbps down and 3.5 up and this is with Sprint.
Click to expand...
Click to collapse
LTE or 4G works fine for me also.
Sent from my GT-I9505
There is a bug in Trebuchet launcher. After reboot some of icons in folders simply disappear
two bugs I noticed:
Alternate action of 'long press Home button' doesn't stick (after closing settings It's back to app-switching when I long press, where I selected Search-app)
Mobile network modes set to: GSM/WCDMA/LTE, when opening the drop-down menu it selects the option LTE (which is two above GSM/WCDMA/LTE)
lostfriends said:
There is a bug in Trebuchet launcher. After reboot some of icons in folders simply disappear
Click to expand...
Click to collapse
Can others confirm this?
Akerboom said:
two bugs I noticed:
Alternate action of 'long press Home button' doesn't stick (after closing settings It's back to app-switching when I long press, where I selected Search-app)
Mobile network modes set to: GSM/WCDMA/LTE, when opening the drop-down menu it selects the option LTE (which is two above GSM/WCDMA/LTE)
Click to expand...
Click to collapse
Can others confirm these?
For me, the network modes work properly. And I don't have an LTE option on its own.
Sent from my GT-I9505
so I had almost decided to give up my One X for something newer (I have been looking at Xiaomi MI3 ), but I wanted to give the One X one last shot.
I have no other problem with my Evita except for the battery life - so that is the one thing I wanted improved. This post is not for people who are already getting 4-5 hours of screen-on time. But I was barely getting through HALF A DAY on my evita.
WARNING: this will format your entire phone - including SDCARD and the whole system. So make sure your system is backed up. Also make sure that you are S-OFF.
step 1 - upgrade the firmware/hboot to 2.18. A lot of you will flash the RUU for this - I went for the simpler method (thanks @timmaaa ) using the firmware here.
Code:
fastboot oem rebootRUU
fastboot flash zip 218firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
fastboot reboot-bootloader
step 2 - upgrade recovery to TWRP 2.7.1.0
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0-evita.img
step 3 - boot to recovery. in TWRP run a full wipe . EVERYTHING. Reboot to recovery.
step 4 - boot to recovery. advanced -> fix permissions. Reboot to recovery.
step 5 - boot to recovery. copy your ROM and gapps to "internal_sd" (note if you see your folder as "/sdcard", then try wiping and rebooting again). I used cm-11-20140718-NIGHTLY-evita.zip and pa_gapps-modular-micro-4.4.4-20140716-signed.zip
step 6 - boot normally and setup your android. reboot to recovery
step 7 - download bubba kernel as well as normalToQV script. install from recovery.
step 8 - Download PurePerformanceX and install through recovery.
step 9 - boot normally
step 10 - go to your brightness settings and click the small settings icon next to the brightness bar. Set sensitivity to "very high" and click adjust (this will cause the evita to react quickly to ambient light changes). Also (and this bit is a little hard to explain) you need to set the system so that it is dimmer than necessary. The Evita's backlight is actually too bright for its own good and consumes a lot of power. So reduce the intensity of backlight at all "levels"
Step 11 - remember to turn off NFC. You can switch off other networks off too, but I keep GPS at high accuracy most of the time.
Ste 12 - with full credit to @timmaaa through this post. I have made some changes in the text below
"First (and I'm not sure if this is relevant because I am still waiting for my OPO to be delivered) thing is to enter Privacy Guard through Settings (if it exists), then click Advanced or Show Built-In Apps. From here you can select Google Play Services and turn off everything except for location.
Next you need to download Android Tuner. Open it and go to Android Tuner -> Sidebar Menu -> Apps Manager -> Application Startups, open the box at the top and change it to All, click the button in the bottom-right until it says System, scroll to Google Play Services and select it, a huge list will open, scroll to very near the bottom and find the Wakeup option, uncheck the box.
Again, open Android Tuner it and pull out the side menu on the left, and go to Android Tuner -> Sidebar Menu -> Apps Manager -> Application Manager. Then select the "Apps" tab and Click the centre box at the bottom until it says System, scroll to find Google Play Services and highlight it, press the Manage button in the bottom-right and select Permissions. This should bring you to the Perms tab, swipe across to the Services tab. In this list you want to uncheck anything that starts with Ads or Analytics, you also want to uncheck anything that starts with com.Google.android.location.reporting as well.
Doing all of this has completely stopped Play Services from draining the battery for me."
Click to expand...
Click to collapse
I am now getting close to 4 hours screen on time. Keeping my fingers crossed - will update this thread if there power consumption goes down. Do note that I already have whatsapp, facebook, truecaller, twitter running - so power consumption is a realistic indication.
Good guide. I think it might belong in General though, I'll ask for it to be moved for you.
Sent from my Evita
Yes. Very good guide. Question, what would one benefit by setting that brightness thing to very high? I noticed there are very high,high,medium and low. I never understood those settings. Could you help me understand ? ?
marknoll said:
Yes. Very good guide. Question, what would one benefit by setting that brightness thing to very high? I noticed there are very high,high,medium and low. I never understood those settings. Could you help me understand ? ?
Click to expand...
Click to collapse
What you're doing is setting the sensitivity to high, it's kinda like fooling the phone into thinking the ambient light is brighter than it actually is and therefore lowering the brightness of the backlight. Of course this is only relevant for auto-brightness. It's to combat the fact that this device over compensates for ambient brightness and unnecessarily raises the brightness of the backlight.
Sent from my Evita
So on that note,its safe to say that having it on very high helps battery? Would it help in the aspects of making the phone brighter in let's say..daylight?
@marknoll - let me elaborate. What I meant was that the screen should be dimmer than default. And sensitivity is very high,so that the screen responds fairly quickly to changes in ambient light. I did NOT mean screen should be brighter than normal. The Evita screen consumes a LOT of power. My apologies if my language was a bit confusing. I'll correct it once I get to my laptop
@sandy. Dude. I'm not referring to u . I was asking in my behalf. Not yours
really glad you shared your method with us........ me too thought of mi3 but my attraction for evita is still enough to use though my only problem is battery life like you..... does your method works for sense roms as well.... il give it a try anyways though...
paras33 said:
really glad you shared your method with us........ me too thought of mi3 but my attraction for evita is still enough to use though my only problem is battery life like you..... does your method works for sense roms as well.... il give it a try anyways though...
Click to expand...
Click to collapse
@paras33 - I suggest you dont try this method with sense ROMs. I'm not sure about the interplay of recovery 2.7.1.0 with sense roms. Especially the whole "internal_sd/sd0" vs "/sdcard" differences. I do recommend that you try the particular CM rom that I pointed to - you might really like it !
How to change settings for PurePerformanceX ?
sandys1 said:
@paras33 - I suggest you dont try this method with sense ROMs. I'm not sure about the interplay of recovery 2.7.1.0 with sense roms. Especially the whole "internal_sd/sd0" vs "/sdcard" differences. I do recommend that you try the particular CM rom that I pointed to - you might really like it !
Click to expand...
Click to collapse
Ok so i'm gonna try this with rom u said but how to revert back if want go back to sense 5..?
Also is pure performancex compatible with sense rom.?..thanks
Sent from my HTC One XL using xda premium
paras33 said:
Ok so i'm gonna try this with rom u said but how to revert back if want go back to sense 5..?
Also is pure performancex compatible with sense rom.?..thanks
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I think you should go and ask this on the Evita sense rom thread (e.g. ViperXL). I'm not sure if TWRP 2.7.1 and PurePerformanceX are compatible with sense
I am unable to boot up with bubba. I always get stuck on the boot animation. No matter how long I wait it just stays there. I've tried with and without the voltage script.
Sent from my One X using XDA Free mobile app
Did you follow the exact steps that I have outlined? This means your phone was clean-wiped. You shouldn't have had this issue - can u confirm?
Yes. I wiped everything. I wiped several times just to make sure it was clean. O forgot to mention i am running candykat rom, which may be the issue. I asked in their q/a thread about bubba with no answer. I had tried bubba before this also and had same issue. I can run torched OK. When I have time I may try again with a full wipe but I need to back some things up first.
Sent from my One X using XDA Free mobile app
So I found the problem. I had been using art runtime. I switched back to dalvik and booted fine. Apparently it does not like art.
Sent from my One X using XDA Free mobile app
As a continuation of discussions from the super thread (http://forum.xda-developers.com/showthread.php?t=2006388), I present the build thread .
Introducing Vanir-Exodus for the Samsung Rugby Pro (comanche):
What works:
- Phone: All works. We can hang up, recieve and send calls.
- SMS/MMS: Image messaging works perfectly.
- Wifi
- Bluetooth
- NFC
- GPS
What's still broken:
- Camera: this has been a fun one...
- Screen rotation: Just disabled in the kernel currently
Screenshots:
DOWNLOADS:
Vanir-exodus comanche
Credits:
- Kemonine96 - If you don't know by now, you haven't been around the comanche threads
- VanirAOSP team - Putting up with me as a pseudo-maintainer for so long
- Dave Kessler - Bringing up Exodus from the Vanir tree
Installation:
1. YOU MUST BE USING A RECOVERY THAT SUPPORTS SELinux. Currently, this is only the TWRP image I built before. I'll have the latest TWRP soonish.
2. BACKUP AND FACTORY RESET. Vanir checks for incompatible data and errors if it won't work. I won't answer "flash error" posts if you tell me you didn't format.
3. Flash the ROM, then GAPPs.
4. Enjoy the wonderment that is 5.0
Changelog:
1/10/15 - Fixed root access: The team was tinkering with a different root implementation, so gaining root became difficult. Root in this version works fine, but the UI is gone.
I really dislike sounding like a begger, but I could use your giys' help.
I'm currently building with 4GB of RAM, which as anyone who's source built can tell you, is quite low. Between the amount my onboard graphics eat, the file hosting and building, my RAM get's spent pretty quick.
What I'm currently looking at is a Gskill 16GB upgrade, which is about $140 max. This will not only speed up build times but help me run more things at once.
Never expected, always appreciated .
G.Skill Ares 16GB upgrade
Hey there. I thought I should post about the rom here instead of the super thread, no? Anyway, I have given it the two-three day daily test and it ran pretty good. The calls work great, recieve texts, e-mails fine. I took it out today and played soundcloud over bluetooth. It all ran great. But I do have a small list of things that didn't past the test.
These things are mostly small annoyances that I know will be fixed
The screen rotation only got a little annoying once it came to watching youtube videos, but I know that will be fixed
I still have some lost SD card issues and I can't really explain how it happens
The camera is still broken, but I know that will be fixed too
But I have had some big problems with the notifications. Its either that something is broken or I just haven't figured out Lollipop yet.
I can't seem to find an option to have the physical buttons flash as a notification light, I think there was an option for that in CM 10 (or am I wrong?)
I don't know how to change the quick settings panel in lollipop, is there a way to do that?
The notification tones don't work at all. The notification tone is selectable in the settings menu, but every time I get a text or email it doesn't go off
Phone ringtone is also selectable but nothing plays no matter what I set it to. it also doesn't play when I get a call
Heres a breakdown of the notifications on my phone
Call, screen comes on, no ringtone plays
Text, no screen comes on, no notification tone
E-mail, same as text
Also I get no vibrations. The phone vibrates while typing, but no vibration other than that for anything. I put the ring volume to vibrate and still nothing.
The count down clock and alarm tone does work though, and the alarm vibrates
Other than that, the phone works great. I have been using an older phone until this release came out, and boy is it nice to have a fast loading phone again, with such a great screen too. Thanks man for all of your work, I'll donate when I can Later.
Edit: Also I have found that this ROM is not rooted. Is that true? Thanks.
Motorhead1991 said:
Changelog:
1/10/15 - Fixed root access: The team was tinkering with a different root implementation, so gaining root became difficult. Root in this version works fine, but the UI is gone.
Click to expand...
Click to collapse
Quick question about the root access on this ROM. I've installed SuperSU and when I open it, it tells me the binaries need to be updated. When I go to update the binaries, it always fails. I'm assuming I missed doing something to enable the root access, so any advice would be appreciated.
Syncline said:
Quick question about the root access on this ROM. I've installed SuperSU and when I open it, it tells me the binaries need to be updated. When I go to update the binaries, it always fails. I'm assuming I missed doing something to enable the root access, so any advice would be appreciated.
Click to expand...
Click to collapse
On this build they basically removed the root manager interface, so root is handled by appops (or something similar). Why they (the android aftermarket) went this way is beyond me. Any time you go to activate a root app, a prompt should come up. (If it doesn't, open Settings > Developer Options > Root access, and tap "apps and adb" or whatever suits your needs).
If you'd rather use SuperSU (or any others), find a flashable zip and flash it in recovery. This should correct any issues you have with using said app.
Motorhead1991 said:
On this build they basically removed the root manager interface, so root is handled by appops (or something similar). Why they (the android aftermarket) went this way is beyond me. Any time you go to activate a root app, a prompt should come up. (If it doesn't, open Settings > Developer Options > Root access, and tap "apps and adb" or whatever suits your needs).
If you'd rather use SuperSU (or any others), find a flashable zip and flash it in recovery. This should correct any issues you have with using said app.
Click to expand...
Click to collapse
Thanks, appreciate the assistance.
Need the rom if possible
Hi, I am still using this phone as a daily and it is now slowe than ever and I was wondering if someone still have the rom since the links are broken. Thanks
1. On 5.1 there is still no option to add hidden SSID WIFI network on first setup steps ("Select WiFi network" after selecting language), if there is no other visible WIFI networks in the range.
2. Still no silent mode, and still bug after restarting phone with volume level on 1 changes it to 0 (silent mode?). What if I want to use my ringer on level 1 volume?
3. No option to turn off automatic network change to mobile data when WiFi has no internet connection.
4. ART is slow on booting times after cleaning cache in recovery, or after flashing stock image, or after flashing custom ROMs, and when installing new apps, etc. Also it eats more space than dalvik. And after all it is not saving battery life or offers better performance (try to flash some kitkat ROMs after 5.x and you'll notice how fast your Nexus on dalvik).
5. Power saving's orange bars. Why orange? Why I can't change color? Why it changes to orange at all?
6. Still no reboot menu.
7. Still no option to clear all recent apps and no option to stop keeping them after reboot.
8. Very slow dialer app, especially when power saving is turned on. There is more than 3 seconds lasts before caller screen appears.
I'm sure there is still a lot of bugs and annoyances in the latest android. But I don't know why they're (Google) not fixing it. And not listening to customers. Android 5.1 just arrived - and ruined all hopes that many things will be better.
1. Cant help you there. It would be a good option. I do agree.
2. You do have silent mode. Its just implemented differently to allow for certain priority events (configurable)to occur which I personally like.
But it would be nice if they added a pure silent mode too.
3. For me, I simply turn off cellular data if I don't want it to switch to mobile data.
4. No argument there. But my N5 is fast enough its not really bothersome for me.
5. I guess orange so you are aware the mode is active? CM Themer can change the color in many custom ROM's (I think)
6. Agreed. This should be an option in stock Android. But for me, a custom ROM such as euphoria fixes the reboot shortfall.
7 Again I agree. This should be an option in stock Android. Custom ROM fixes this except no option to stop keeping them after reboot that I can find.
8. I guess its slow because battery saver has lowered your cpu in an attempt to extend battey . For me it is ok, life is full of tradeoffs.
Flying spaghetti monster. I'm so sick of people pitching about the new silent mode. I wish these people would stay on KitKat or switch to iPhone.
Is there anyway to fix number 3 with some app or module on xposed?
AndrasLOHF said:
Flying spaghetti monster
Click to expand...
Click to collapse
LOL dude.
Pastafarians ~ LMAO
I learn something new here at XDA every day!
krugdenis said:
1. On 5.1 there is still no option to add hidden SSID WIFI network on first setup steps ("Select WiFi network" after selecting language), if there is no other visible WIFI networks in the range.
2. Still no silent mode, and still bug after restarting phone with volume level on 1 changes it to 0 (silent mode?). What if I want to use my ringer on level 1 volume?
3. No option to turn off automatic network change to mobile data when WiFi has no internet connection.
4. ART is slow on booting times after cleaning cache in recovery, or after flashing stock image, or after flashing custom ROMs, and when installing new apps, etc. Also it eats more space than dalvik. And after all it is not saving battery life or offers better performance (try to flash some kitkat ROMs after 5.x and you'll notice how fast your Nexus on dalvik).
5. Power saving's orange bars. Why orange? Why I can't change color? Why it changes to orange at all?
6. Still no reboot menu.
7. Still no option to clear all recent apps and no option to stop keeping them after reboot.
8. Very slow dialer app, especially when power saving is turned on. There is more than 3 seconds lasts before caller screen appears.
I'm sure there is still a lot of bugs and annoyances in the latest android. But I don't know why they're (Google) not fixing it. And not listening to customers. Android 5.1 just arrived - and ruined all hopes that many things will be better.
Click to expand...
Click to collapse
well first of all none of the things you mentioned fall in Bug category.
second all options you asked for were never be on stock rom and never will be...stock android remains as simple as Google wants ..if you need other options use custom roms with their bugs/problem !
3rd we moved on from Kitkat and we are Ok with some difference in Lollipop...this is not Crappy iOS or Laggy Touchwiz who always looks same & have same funtions ...you are not Ok with it stay on Kitkat , No one if forcing you ! or Buy device with one of those -_-
Finally don't start thread for only giving your opinions or desires or well known things ...there are thousands of nexus 5 owners on XDA , imagine what will happen if all of them will do same as you ! ( we already have 5.1 discussion thread you could have place your so called "bug list " there ! )
4g lte
in italy,with vodafone, the phone does not connect more in 4g but only in 3g / h.
before 5.1 (with 5.0.1) everything was ok
AndrasLOHF said:
Flying spaghetti monster. I'm so sick of people pitching about the new silent mode. I wish these people would stay on KitKat or switch to iPhone.
Click to expand...
Click to collapse
LOL. If you didn't know what is true silent mode, here is an explanation: http://forum.xda-developers.com/showpost.php?p=59333086&postcount=85 :laugh:
jineshpatel30 said:
well first of all none of the things you mentioned fall in Bug category.
second all options you asked for were never be on stock rom and never will be...stock android remains as simple as Google wants ..if you need other options use custom roms with their bugs/problem !
3rd we moved on from Kitkat and we are Ok with some difference in Lollipop...this is not Crappy iOS or Laggy Touchwiz who always looks same & have same funtions ...you are not Ok with it stay on Kitkat , No one if forcing you ! or Buy device with one of those -_-
Finally don't start thread for only giving your opinions or desires or well known things ...there are thousands of nexus 5 owners on XDA , imagine what will happen if all of them will do same as you ! ( we already have 5.1 discussion thread you could have place your so called "bug list " there ! )
Click to expand...
Click to collapse
So, when device can't connect to hidden wifi on first run, it's not a bug, it's feature?
Or, when device volume set to 1 and after reboot it becoming completely silent, it's feature too? No bugs on stock Android?
You people complain about these "you-can-live-without" issues. Haven't you seen the 5.1 changelogs? It has 14,694 commits. Again, 14,694! Most of them are of MEMORY LEAK bugs and other necessary optimizations to make the phone usable at the moment. Then you'll complain about not having that silent mode? Dalvik won't consume that much if you remove some bloatwares. Then the orange status and navi bars coz of the battery saving mode? Seriously?! Can't you find more serious bugs than that?
krugdenis said:
So, when device can't connect to hidden wifi on first run, it's not a bug, it's feature?
Click to expand...
Click to collapse
I never used hidden SSID on android so i don't know what problem is occurring to you and i also don't know whether older verson like 4.4.4 was wroking with it or not.
I use MAC restricted WAP2 and it connected without problem in 1st bootup
Btw why you are using hidden SSID ? More security ? Then here you Go if any other reason tjen you should probably ask other user using SSID about this
Or, when device volume set to 1 and after reboot it becoming completely silent, it's feature too? No bugs on stock Android?
Click to expand...
Click to collapse
I justs checked it and this is not happening to me , it stays on 1 after reboot also.....so may be something wrong with your device you should try factory reset if you didn't already
Real annoyances I have on stock 5.1:
1. Name of provider above data toggle in quick settings randomly dissapears
2. After phone restart there is allways "No internet connection" warning in Google app
3. Scrolling bug is really there
4. And I still don't now, how the h*** you integrate updates of system apps into rom
Hello,
I'm a noobie. I bought a oneplus 7 Pro from a prestigious store (EMAG), not connected to any mobile network(1. this means is already rooted?).
Problem is I bought it resealed, Oxygen 10.0.3.GM21BA was already installed on it. I like newer versions of Android, and my phone, but it can't do basic functions. The call and sms and notifications volume is stuck on 0. I want to try to put Android 9 on it and try to install android 10 myself(2. Is this a good ideea ? will I loose my warranty, and not be able to return the phone? Should I just return the phone?). 3.How can I rollback my phone to Android 9?(simple steps that a noobie can follow. 4. Should I install then Android 10? which is a stable version?
Please help, I lost 5 hours reading and trying to solve it myself, I'm very sad!
If the volume is stuck on 0, check the notification slider on the right;
Top is mute all except alarms or "Silent" (Great for setting an alarm to wake yourself up without being woken up by stupid alerts and app noises)
Middle is Ringer off but media sounds enabled or "Vibrate"
Bottom is all sounds on and vibrations on or "Ring"
Although you might need to use the volume buttons to turn the volumes back up if they had been adjusted while the slider was moved, just move the slider to the bottom position then use the volume buttons to turn the volume up. You can also check Settings>Sound and vibration to see what the levels are at and use the sliders there too.
If you're a noobie then DO NOT TRY TO ROLL BACK THE PHONE, if you don't know what you're doing then you're highly likely to get into problems. There's nothing wrong with Android 10 on the OP7Pro, believe me.
Also, You don't need to "install Android 10", you're already on it.
If you've bought a resealed phone then I would recommend wiping the data and treating it as a brand new phone. Reboot the phone and hold down the volume down button which should take you into the recovery menu, go into recovery, then data and wipe data and cache. Then, when you reboot the phone it will be ready to setup as a new phone.
To ensure you've not received a tampered phone, when the phone is booting check for a screen saying "The boot loader is unlocked and software integrity cannot be guaranteed", if that does not show up then the OS should not have been tampered with and the phone should be safe. If it does then that doesn't necessarily mean it's dangerous, as the previous owner may have just installed a custom recovery (TWRP) and rooted the phone or tried some custom roms, but you should think about re-installing the OS if the bootloader is unlocked, download the OS from here :
https://www.oneplus.com/uk/support/softwareupgrade/details?code=PM1574156267635
OnePlus's official forums are here, you should think about registering and keeping an eye on them as you'll see announcements about new versions of the OS as well as beta versions, although if you're not confident flashing roms then you might want to stick with the default one that OnePlus pushes to your phone.
Also EMAG seems to be a Romanian store? So, if you go into Settings>About phone (at the bottom), then tap on Android Version, your installed OS version should be shown under "Build number" at the bottom of that page. EU versions should show "BA" as the last 2 characters, Global versions show "AA". The latest for each at the moment is :
Oxygen OS 10.3.0.GM21AA (Global)
Oxygen OS 10.0.3.GM21BA (EU)
Although you did say your build is already BA so it should be correct if you are from Romania? If your data isn't working then I would be checking that the phone wasn't locked to one particular supplier in that country but you may get away from flashing the European build from OnePlus's downloads above.
Don't ask us why they're using a different build number cos we don't know either, possibly to avoid confusion for users? In any case, you shouldn't have any problems with data connection but, if you do and it shows "AA" at the end, then you could try flashing the EU build instead. Just download it from the link I provided above, place it in the root folder of your phone's storage and then go into Settings>System Updates (Bottom), then tap the cog on the top right and go to Local upgrade, you should see the rom you downloaded there. Select it and follow the instructions. To save you getting into trouble, I would recommend removing your pin or screen lock before doing so.
Solved
Thank you so much it was the slider. It was something hardware. I looked for software solutions everywhere. I was so sad yesterday. Now I can actually keep the phone! Thank you very much!Since I moved the hardware slider and I could move software slider, a smile stayed on my face! Thank you so much!
djsubterrain said:
If the volume is stuck on 0, check the notification slider on the right;
Top is mute all except alarms or "Silent" (Great for setting an alarm to wake yourself up without being woken up by stupid alerts and app noises)
Middle is Ringer off but media sounds enabled or "Vibrate"
Bottom is all sounds on and vibrations on or "Ring"
Although you might need to use the volume buttons to turn the volumes back up if they had been adjusted while the slider was moved, just move the slider to the bottom position then use the volume buttons to turn the volume up. You can also check Settings>Sound and vibration to see what the levels are at and use the sliders there too.
If you're a noobie then DO NOT TRY TO ROLL BACK THE PHONE, if you don't know what you're doing then you're highly likely to get into problems. There's nothing wrong with Android 10 on the OP7Pro, believe me.
Also, You don't need to "install Android 10", you're already on it.
If you've bought a resealed phone then I would recommend wiping the data and treating it as a brand new phone. Reboot the phone and hold down the volume down button which should take you into the recovery menu, go into recovery, then data and wipe data and cache. Then, when you reboot the phone it will be ready to setup as a new phone.
To ensure you've not received a tampered phone, when the phone is booting check for a screen saying "The boot loader is unlocked and software integrity cannot be guaranteed", if that does not show up then the OS should not have been tampered with and the phone should be safe. If it does then that doesn't necessarily mean it's dangerous, as the previous owner may have just installed a custom recovery (TWRP) and rooted the phone or tried some custom roms, but you should think about re-installing the OS if the bootloader is unlocked, download the OS from here :
https://www.oneplus.com/uk/support/softwareupgrade/details?code=PM1574156267635
OnePlus's official forums are here, you should think about registering and keeping an eye on them as you'll see announcements about new versions of the OS as well as beta versions, although if you're not confident flashing roms then you might want to stick with the default one that OnePlus pushes to your phone.
Also EMAG seems to be a Romanian store? So, if you go into Settings>About phone (at the bottom), then tap on Android Version, your installed OS version should be shown under "Build number" at the bottom of that page. EU versions should show "BA" as the last 2 characters, Global versions show "AA". The latest for each at the moment is :
Oxygen OS 10.3.0.GM21AA (Global)
Oxygen OS 10.0.3.GM21BA (EU)
Although you did say your build is already BA so it should be correct if you are from Romania? If your data isn't working then I would be checking that the phone wasn't locked to one particular supplier in that country but you may get away from flashing the European build from OnePlus's downloads above.
Don't ask us why they're using a different build number cos we don't know either, possibly to avoid confusion for users? In any case, you shouldn't have any problems with data connection but, if you do and it shows "AA" at the end, then you could try flashing the EU build instead. Just download it from the link I provided above, place it in the root folder of your phone's storage and then go into Settings>System Updates (Bottom), then tap the cog on the top right and go to Local upgrade, you should see the rom you downloaded there. Select it and follow the instructions. To save you getting into trouble, I would recommend removing your pin or screen lock before doing so.
Click to expand...
Click to collapse
Great advice, but i have to disagree with you, Android 10 still has Bluetooth issues. I'm looking to roll back myself because of it.