Edit, 02/10/2011:
Please keep in mind this post was based on the original release, some things have been fixed/changed since then. See post 1 in the dev thread for full update details.
Original Post:
My wife and I both have XT720, I left her's with stock 2.1, mine I just upgraded to Dexter's 2.2.1 (1.1a release) so I was able to compare the two side-by-side.
I wanted to list some of the differences for people, almost all of these are trivial items but just so you know what you may or may not see:
Menu options missing in Settings are:
Wireless & Network Setings
- Control background data
Call Settings
- TTY mode
- Hearing aids
HDMI
- HDMI Format
Location & Security Settings
- My Location
- Use assisted GPS
- Compass
- Calibrate Compass
Applications
- Double tap home launch
Search
- Google search settings
- Searchable items
- Clear search shortcuts
Language & Keyboard Settings
- Enable cursor positioning
Text to Speech
- Listen to an example
- Install voice data
- Always use my settings
- Speech rate
- Language
Click to expand...
Click to collapse
Some of these may have been depreciated with 2.2 and may be why they are gone. Others not so sure, but all of very low priority in my opinion (except A-GPS and Compass).
* Assisted GPS is useful to lock onto GPS faster, this can also be downloaded with many apps in market. I use "GPS Status & Toolbox" by EclipSim which can also download the A-GPS data.
* Compass does not seem to work at all, always stays within a few degrees of the orientation it thinks it is in. As the menu settings were missing (per above) I have used alternate calibrate and compass functions also in the "GPS Status & Toolbox" app to test. Does not seem to change direction again, more than just a few degrees.
* Proximity sensor does not seem to work, cover it with finger and screen does not go black as expected. This is a problem when using the Phone with dialpad open as I usually manage to press buttons with my ear while talking. I think this proximity sensor issue is biggest problem left (for me).
* Noticed as well, when scrolling a list (like when in Settings menus) that the haptic/audible feedback when you hit the very top or bottom of a long list no longer happens in 2.2.
* Also an app note, when first trying to load Latitude in Google Maps app, it gives errors that it cant connect to your Google account and goes to the add account screen. If you cancel the add account screen, you will see an alert of a notification - this is asking to allow Latitude to access your Google Account. Once approved, Latitude worked fine.
* Noticed in About phone, kernel version says "[email protected] #1" under where it says 2.6.29-omap1, what is this?
* The haptic feedback (vibrations) seems to be much lighter/fainter than in 2.1.
* Bottom 4 lights were stuck in Off until I used the Power Widget to change the screen brightness.
* No Phone or Messaging buttons next to app drawer on home screen.
* Camera mode - stitching, supposed to let you take 6 photos and stitch them together but when you try to take the second photo it just saves the first one only.
Click to expand...
Click to collapse
Again as I said, almost all of these observations are inconsequential - I just wanted to list them in one place for peoples comparison.
Oh, and Google Goggles works in 2.2, it never worked in 2.1 (always scanned as a blank green sceen).
Thanks Dexter for all your hard work in getting this far so quickly!
edit: Home screen and Quadrant score:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cant post to the other thread, so adding some feedback here .. mods can maybe move some of these posts?
Click to expand...
Click to collapse
I reposted your post at the other thread.
Wow!, thank you for such a detailed review of the outstanding issues, functionality and missing features between the versions
now people can think ahead if they are willing to lose some of those functionality or not before upgrading
Reading this i think some understanding of functionality is left to consider?
*Compass
If you rotate the phone, should compass not STILL point the same direction? i think north is arrow points? i tested with GPS test and Compass app, and direction after calibration seems fine. (using the 8 rotation solution to solve calibration)
*Proximity sensor seems to have a long range estimation (tested with Z-devicetester) i made some changes and now it reflect 0cm -> 6cm , in 1.1a it seems to say 0 -> 217cm
*haptic feedback depends on devices, Milestone might just have different device, so they lowered it to make it less hard. cannot be easily fixed unless framework changes.
*Google account in general can report "no network connectivity" as it always try mobiledata before regular wifi, its comon problem on all phones, it does happens not only with maps or gmail/market.. (i see this on Galaxy S as well)
* No Phone or Messaging buttons next to app drawer on home screen.
Must be an observation as its not part of Google Stock , but is a way of design from vendors, motorola do it on some phones now..
LauncherPRO is an excellent way of getting custom buttons back. Stock launcher is always boring.
-----------------------
update to your old information versus new information.:
Wireless & Network Setings
- Control background data moved to Sync options
Location & Security Settings
- My Location still there but more defailed network+gps sat)
- Use assisted GPS always enabled on motorola phones
- Calibrate Compass (no need, sensor calibration using moving in 8 circle
Text to Speech now called Voice input&Output
Depends on the app how the compass rotation is displayed. What I am trying to say is that it does not point how it should. For example, when using Google Sky Map, I hold up the phone and it is always looking South no matter which way I am pointing.
For how much it gets used its not a big deal, just my observation. And thanks for the info on some of the menu options and where they moved.
For "Control Background Data" - I think this is a different option than the "Background Data" in sync as the option under Sync was there before too. The description in 2.1 for "Control Background Data" is "Control background data to extend battery based on network". The option under Sync of "Background data" says "Applications can sync, send, and receive data at any time". I have no idea what the functional difference is, maybe they both do something similar anyways.
Good to know on A-GPS being always on, was not aware of this.
And for Prox sensor, it started working after another reboot, not sure why. It works at the same distance (tested with side-by-side phones) as previously.
So aside from weird compass behavior here, everything seems to be working great now.
One more thing I just noticed with volume control, the explanation may not make sense but functionally when you are using the app it will be clearer.
In 2.1 when in landscape orientation (speaker on left, buttons on right), the volume Up and volume Down are reversed as they then correspond with the display on the screen.
ie. Pressing volume up button would actually turn the volume down, and down button would turn volume up as it was on the right, and that is how the volue bar is displayed on the screen.
In 2.2, volume up button remains as volume up in landscape mode, so when you rpess it and expect the volume slider display to move let (down) it actually goes the other way.
You can see this in Vevo or Angry Birds for example, expect to push left for volume down but it goes volume up. To me it makes sense for it to reverse the volume control buttons when in landscape orientation.
My problems:
1. if i enable auto-proximity sensor, and turn my phone 90° right side (so to east), the screen turns also 90°. so far, so good. but it stays like this the whole time, even if I turn my phone back 90° or 180° or so. sometimes it works normally, but not always does the screen follow the turns.
2. Languages are for example in the camera & task manager in English. But we already know that.
3. Games that are used with apps2sd are often laggy.
4. The button next to camera button does not work, for example when I open the camera and push that button next to camera button, the camera should change to gallery or to camcorder. But it doesn't.
5. For example playing games and I want to change the volume and press "up" at the volume button, the sound gets less loud and if I press "down" at volume button", the sound gets louder.
6. Using the web browser, the pages do not adapt to the screen like in 2.1.
I think there are some compromises we must make in order to have 2.2 on the xt720. The one issue that I am still having that I do not feel i should compromise on is the browser.
The stock browser is killed, not force closed, but killed while in use very often. I do not know what is causing the issue but I saw that users on the ROM thread are having the same problem.
warrenkb said:
I think there are some compromises we must make in order to have 2.2 on the xt720. The one issue that I am still having that I do not feel i should compromise on is the browser.
The stock browser is killed, not force closed, but killed while in use very often. I do not know what is causing the issue but I saw that users on the ROM thread are having the same problem.
Click to expand...
Click to collapse
i will of course follow up on this issue and the music scanning problem..
which for now is "major".. but ill report back on it asap when i got a solution.
and keep the update minimal so ppl do not need to make full flashes or wipe's
strange is that i played with a few flash sites with stock browser, and it did not crash then? can it be flash somehow crashing it or not being there?
nice comparison!
Thanks for the useful review
you should do a 1.2 review by now. so far, 1.2 is a lot better than 1.1+
Agreed, I also have it on my Starhub XT720, and thanks to it I am keeping the phone !
Is chinese language supported in this rom?If not in the future?
chaud said:
Is chinese language supported in this rom?If not in the future?
Click to expand...
Click to collapse
i know its there, so have a try and decide yourself, but for me , being danish, its looks different
Rotation seems to work in both directions rather than just one. I was wondering if there is a way to limit it to just one side again?
trajano said:
Rotation seems to work in both directions rather than just one. I was wondering if there is a way to limit it to just one side again?
Click to expand...
Click to collapse
i doubt it will be better.. most ppl prefer 360 rotation, but maybe disabling rotation will help?
There are Widgets to disable or to manually rotate your screen, you may want to try one of those ... I personally like the 270 degrees of rotation. Just wish the volume rocker would auto switch like in 2.1
Sent from my XT720 using XDA App
R-D said:
There are Widgets to disable or to manually rotate your screen, you may want to try one of those ... I personally like the 270 degrees of rotation. Just wish the volume rocker would auto switch like in 2.1
Click to expand...
Click to collapse
Yes I know about those, but I was wondering how we can have it so it is just 90 degrees. No biggie, but is is still a difference between 2.1 and 2.2 that you may want to add to the list.
SD Card feedback
I am also unable to locate where to disable the SD Card notifications
Related
PLEASE NOTE THE FOLLOWING:
This is BETA code. Some things do not work and you should assume there will be BUGS. I am not responsible if you brick your phone with this or any other firmware. You are your own warranty once you start loading firmware. Please do NOT post about anything that's in the "broken" list; I will ignore you if you do.
If it's not listed as working or broken below then that particular feature has likely not been tested at all.
Kernel: Mine, built from Motorola's released source. Includes Smartassv2 governor and ext2, ext3 and ext4 filesystems plus MSS clamping support.
Codebase and credits: Originally sync'd from Isaac's work, heavily modified at this point. Isaac deserves the credit for getting the base code to boot and getting me interested in hacking on it.
What's working
Pretty much everything, except what's listed below.
What's known BROKEN:
Hdmi non-functional
The is an interrupt storm if you enable both Wifi and Bluetooth at the same time. Don't.
Front camera does not mirror snapshots or video, but does on preview.
Occasional force-closes when switching cameras front-to-back.
What's Intermittent: Nothing.
Included Apps:
Essentially nothing. Load GAPPS for Google apps (yes, you want them) by flashing these AFTER you flash the ROM:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip - Base Google Apps
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip - Google Talk (if you want it)
NOTE: You cannot provision on the CM7 ROM (the "Activate" apk, if you grab it from the Triumph, will not work - it appears to run, but does not function.) You must be provisioned using the stock ROM before you load this code. I am attempting to fix that, but am not confident it can be fixed as it appears to want things in the framework that I have no way to discover or duplicate.
To install:
1. MAKE A NANDROID BACKUP! I cannot emphasize this enough - and make sure you keep that backup somewhere SAFE. Most notably there is no way to activate the phone on CM7 at this time, and there may never be. If you need to change your phone number or similar you need to swap back to stock firmware. If you lose the ability to do that you will be pissed. Consider yourself warned.
2. Place the file in the below post on your SD card in the root.
3. Boot to clockwork by turning your phone off and then hold BOTH volume buttons while pressing POWER. Release power when the phone vibrates and continue to hold both volume rockers until Clockwork comes up.
4. Important: Clear the cache and data ("factory reset") If you fail to do this CM7 will blow up on boot unless you are coming from previous RECENT build. You've been warned! If you're coming from an OLD build (or stock) format /system as well.
5. Select the ZIP file from the SD card (about halfway down on the top screen of Clockwork to get to that menu, then the first entry and point at it.)
6. Commit the update.
7. If you formatted /system (and if you're coming from STOCK) flash GAPPS (below; the first is the standard GAPPS apps, the second is Google Talk) using the same procedure in #5 and #6.
On first boot it will take about 2 minutes before it comes up; if you have lots of apps it may take longer. Provided you see the little CM7 guy with the rotating arrow, it's working - be patient.
Current code download link(s)
11/19 - vB.08 http://www.mediafire.com/?bhmitbx7weqf8g2 - Wifi Tethering / FINAL
11/06 - vB.07 http://www.mediafire.com/?eqdfo7ktmtuq281 - Haptic soft keys / light sensor
10/30 - vB.06 http://www.mediafire.com/?qj28ip6o09j1ai6 - Screenshot / restore GB Launcher
10/29 - vB.05 http://www.mediafire.com/?rjf20vb74oc0irb - Cleanup release; see below
10/26: http://www.mediafire.com/download.php?wwj1l5lzjb4glfy - Wifi/PRL/Prox Sensor
10/22: http://www.mediafire.com/download.php?nssofns6sljfj33 - CIFS/Prox Sensor/USB Tether
10/16: http://www.mediafire.com/?jg5matblx1d7bq2 - First BETA
10/12: http://www.mediafire.com/download.php?wtwvx80ccsz8vfi - Last ALPHA build
Note: Loading this version requires a Clockwork that understands ext4. The following version is recommended: http://www.mediafire.com/download.php?acpcd9xtlpzqge1
Expected to be fixed in the NEXT build -
Work continues on the list in the first post along with tracking bugs that have been posted to GitHub.
Change Log (tracking as of 9/5), reverse chronological order:
11/19:
Wifi tethering is now built into the code (from Isaac's work); untested other than the fact that it does come up and is believed working. No other changes. FINAL RELEASE.
11/06:
Haptic feedback on soft keyboard now works and is treated as any other "virtual key" off the screen. Kernel modified to multiply light sensor readings by 30; this "sorta" aligns them with actual lux values (not really, but I don't have a light box that can get me a closer integration formula) and makes possible the CM7 options for "jump" settings, hysteresis and such to work as designed. No other material changes against b.06.
10/30:
Screenshot from power menu fixed and Gingerbread default launcher restored.
10/29:
Cleanup release. 2.3.7 codebase merge with CM7 upstream completed. "99memory" file added - see the notes below for how to tune this if you want to. Significant change to power management was made in the kernel; if you have Wifi turned off the phone will enter deep sleep, but if it's loaded then the sleep state is held at one level higher to prevent Wifi lockups. Note that data, when active, is a major power pig, even if nothing appears to be using it. It looks like Sprint has some "keep alive" processing going on either at the network level or in the actual CDMA driver code (which we don't have) that plays hell with power consumption. In short, with a data connection up I can't get materially under 30ma when idle and it's either the carrier or the CDMA radio code doing it - either way, I have no way to change it as there's no source to the chipset code available. Juice Defender, assuming Wifi is off, does a amazingly excellent job in conjunction with this release in shutting down the data connection and "waking it" once every 15 minutes or so to check for new notifications. It makes a huge difference in power burn with the phone in your pocket. You decide if its worth losing "instant" data notifies. I noted the same battery behavior on stock (Froyo) when I first got this phone, so my best guess is that this is in the radio firmware itself. Last alpha release pulled.
10/26:
Wifi wakelock problem is fixed. PRL now comes out of the radio and proximity sensor has more changes made. Note that the prox sensor may "flash" if you put the phone to your head before the call connects (before the "vibrate" after you dial); it should stop as soon as the phone goes into the "active" state.
10/22:
CIFS support via kernel loadable (.ko); NOT loaded by default as its very large. You can enable this in the startup scripts if you want it. USB tethering fixed. Proximity sensor "blinking" fixed. Various other minor changes as well.
10/16:
Data drop detection/correct code added. Front camera options that were unsupported in the hardware (and which could cause lockups) removed. Memory management changes made to improve performance. Soft keypad now PWM controlled (change levels under the CM7 options if you don't like my defaults) and other cleanup. Note: This release was early as there's a problem with some of the dependencies in the GIT servers, and as such I could not do a clean "verify builds from zero" run. Note that front camera mirror mode is enabled for preview but is NOT on snapshots and taken videos; this is being investigated as the mirroring should be on but doesn't work when the actual picture is taken.
10/12:
GAPPS removed from base build, front camera fixes complete, rear camera will now video record in HD. Tunneling support now internal to the kernel (no longer requires a loadable) for VPN users. Previous versions REMOVED.
10/2:
Partial front camera support is now available. The camera functions properly in video calling software such as Skype. Note that the "hacked" Froyo-capable Skype does not work properly; the one in the market, however, does. Other video calling applications may work but have not been tested. The Camera application itself will display the preview on the front camera but it is flipped 180 degrees (top to bottom), attempting to switch to video mode force-closes and a snapshot attempt hangs. Don't do that, basically. These are on the list to be fixed but progress is slow due to the very hacksterish way I had to implement the camera (no thanks to Motorola on that with no source access.) Kernel has the smartassv2 governor available for those who wish it and the build tree was synced up from CM7 to incorporate their fixes and updates.
9/25
Bluetooth tethering and MSS clamping implemented. Bluetooth tether is native; the MSS clamping, if recognized by other tethering applications (e.g. wireless tether) will also function to get rid of the need to set the client's MTU.
9/21
GPS now functional
9/10 morning:
Compass/geomagnetic sensors now working properly
Lights code now honors CM7's customization screens
9/5 morning build:
Market problems with apps not showing up repaired.
To file a BUG report
Use the Bugtracker Git at https://github.com/ikarosdev/CM7_Triumph_bug_tracker/issues?sort=created&direction=desc&state=open
Filing a new bug will require that you set up a login ID on Github if you don't have one. Please note that bugs reported in this thread (as opposed to discussion, which is always welcome) may or may not be noticed and tracked; if you care about whatever you're reporting, please use the GITHub system. Bugs filed on Github must include steps to re-create the problem if you're able to do so and if you can obtain one, a logcat or other trace is very helpful. You can also look at the above link to see what issues are open (please do not duplicate already-reported bugs, although if you have comments on them adding them is fine) as well as what has bene closed which may be of interest if you're looking for what is likely to show up in the next code turn.
Notes
Do NOT tamper with the following lines in build.prop:
ro.telephony.ril_nid=97
ro.telephony.ril_prl=1115
ro.telephony.ril_class=Triumph
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
If you do there is a high probability that the radio will break. In particular the ril_class is required to deal with the oddities in the Qualcomm radio code. If you are running a different PRL you can change the prl line but it should remain present.
If you are updating from previous releases and have problems format the /system partition before you load the update. You should not need to format the data partition ("factory reset") and reload your applications, but no promises can be made at this point in development.
Custom backlight options (Settings->Cyanogen Mod->Display->Automatic Backlight) are available; you can change the behavior of the LCD backlight, including thresholds and illumination settings, the number of steps, whether averaging is used, whether hysteresis is operational and whether the button backlight is on or off as desired. Please note that unlike many devices the sensor value returned to the code is not in "lux"; it is a raw value and tops out in full sunlight somewhere under 100, with "0" being a fairly dim (but not dark) room. The default table I have loaded has the button backlight OFF for very dim ambient conditions (I like to use the phone as an alarm clock and want the buttons off at night), ON for low-but-present ambient conditions, and then OFF again (power saving) for ambient light high enough that the backlight has no real purpose. You may change this to suit yourself and your desires; some people will want the buttons on for zero-ambient conditions.
Note: As of 9/24 this load is using the "ext4" filesystem. Alternative kernels must support both that filesystem and the options CONFIG_NETFILTER_XT_TARGET_TCPMSS and CONFIG_IP_NF_MANGLE. If they do not MSS clamping will not function. If ext4 is not supported the kernel will not boot.
3g/1x data lock
If you are in a place that often switches down to 1xRTT for data due to questionable signal levels it is possible to lock the RIL to 3g mode. Note that doing so means you either get 3g speed or nothing. You need to access the "Phone Info" menu to do this using either AnyCut (from the market) or from the "Battery Monitor" Widget (go to "Tests" in the selected screen from there.) Note, however, that doing so (1) will not survive a reboot and (2) disables SMS/MMS and inbound phone calls during the time it is active. SMS/MMS will come through if you make a phone call but the EVDO-only mode for data blocks something in the radio that is required to receive and send SMS messages and the notifications of an inbound call. Since this "mode change" is actually a request to the radio ROM (which we do not have source for) this probably can't be worked around. However, I am looking into what this mode select does in the hope of being able to detect the 1x switch (which I can easily do with the existing RIL support code) and temporarily force a 3g switchback - which may or may not be highly-disruptive to data transport (if it is it's not worth doing at all, but if not...)
Note: There is an apparent memory leak in the base CM7 code somewhere. This is the cause of sensor slowdown (e.g. rotation is not immediately recognized) as the system becomes memory-constrained and ultimately will fault and reboot. I do not have isolation of this problem as of yet and have no reasonable expectation on when or if I may; for the time being I recommend a reboot on a daily basis to avoid the worst of these effects. The impact becomes particularly-severe if you use things like CoPilot that require large working sets of RAM. My instrumentation leads me to believe the problem is not in the kernel nor in the user application side of the system, but rather is in the base CM7 load. Investigation continues.
A note on overclocked kernels:
I will not be supporting these in my builds. They work, and some people want them. Isaac has built one that can (theoretically) go to 1.9Ghz.
Here's the issue in a nutshell: It's pretty easy to exceed thermal limits in a CPU doing this, and if you do, the best thing that happens is that the device becomes unstable and reboots. The worst thing that can happen is that the internal junctions in the CPU can be damaged or even destroyed. This damage is not always immediately apparent and can in fact be cumulative.
I understand some people want to overclock, but nobody really knows where "the wall" in this regard, and if you find it you're going to be very unhappy. As such if you want to have fun of this sort you'll need to load your own overclocked kernel over what I build. I respect those who are willing to take the risk but I just don't see the potential reward as being worthwhile and I don't want to be the guy that hands you a build that smokes the CPU in your phone.
Sweet man, keep up the good work! CM7 is gonna be great on the triumph.
Market fix in the latest build - please update.
Just flashed the updated ROM and so far so good. As long as the calls come through then I can wait for a full port. Thanks for your hard work =)
And on a side note, it seems like I'm getting better reception after I flashed this. (-85dBm vs ~ -95dBm to -105dBm)
The two big problems are the GPS and MMS. The MMS is a matter of hacking and time (Virgin's MMS is... odd...), the GPS is pissing me off. Again a lack of documentation strikes; it appears there's a versioning problem with the RPC stuff and the chipset and driver in question do not expose the NMEA port (which sucks.)
Awesome work!
Here is a random question. Does that lock/unlock flickering issue go away with this? What about the sometimes unresponsive back capacitive key?
Sent from my MOTWX435KT using XDA App
The auto-brightness code was completely re-implemented (by me); it's DIFFERENT in its behavior, but I like how it behaves.
I haven't had a back key problem with either this rom or the original....
HDMI bug report
I'm just trying to help out. HDMI out does not seem to be working just wanted to report this minor bug. Overall I'm loving this rom. Great job.
Great work Genesis!
Sent from my NookColor using xda premium
Anyone experiencing issues with data?
Seems like my data is intermittent and goes in and out randomly. I still see the 3G icon (and the signal status) but it goes white (no Google services) and I have no data access.
Yeah I've been losing data. Easiest fix is to turn on airplane mode on the off. Should come back on.
I've also noticed that email 2.3 keeps force closing. Got around this buy restoring email 2.2 with titanium backup.
stock video player bug
When playing videos with the stock video player the video comes out slightly glitchy. The same thing happens with YouTube videos.
I have not noticed the problem when watching flash videos or using arc media video player (have not had a chance to test others)
Love the ability to use the different themes with theme Chooser.
Agai appreciate all the hard work. Can't wait for a custom kernel
my review
ok i would like to start this off by saying that i love you for all the work you have done, you and Isaac. this is not asking you to fix anything this is just my first impressions after using this rom for two days.
*market: i believe this was already addressed in the original post of this rom. i updated market to the newest version and ever sense it has been force closing at random times. it still works to download things and browse but it will randomly force close.
*battery life has greatly decreased since i flashed cm7. even with juice defender pro it was still a much shorter life span.
*screen auto brightness: this has already been addressed i know but i am trying to do a very in depth review. it takes a while after i turn the screen on for it to brighten up enough to be clearly visible. another thing i just recently noticed was that while i was in a call and holding the phone up to my ear, the screen would repeatedly turn on and off. i believe this may have been the way i was holding the phone but it happened more than once so this is why i thought to address it.
*head set volume dropping issue. i have addressed this in a previous thread as a fix. i was hoping this would be fixed in cm7 but it must be a deep hardware issue. what happens is, when you are listening to music through the headset port and a text comes in, the phone will ring and then the music will come back on but at a significantly lower volume. the only way i have found to bring the volume back up is to make a call and then play your music again.
*music and calling: i have noticed that if you answer a call and have music playing, when you hang up the music will stay paused. i dont know if this can be fixed but i thought i would just throw it out there.
*wifi will work untill the screen goes off. the phone will not rewake and you will have to do a batt pull.
*swype fails hard. with froyo swype worked just fine but now it has very bad lag and doesnt even register when im swyiping sometimes. this is not that big of an issue because i use swype as personal preference.
*wifi wireless teather for root users. this works now! only with google web pages -_-
*mms: wont work at all. just a heads up though you can go to message settings and switch it to split messages so you can send longer messages.
as of now this is all i have but i will update this if i come up with more. as i said before i am not trying to nag you at all i just want to get my views out there and hopefully help with feature development of cm7 for the triumph.
keep up the great work guys! i cant thank you enough.
1. Market - if you loaded over the first load, you need to format /system before you do that. You've got pieces of old things laying around.
2. Battery - it's wrong (charge state) until you fully cycle it. I'm getting battery life roughly equal to the stock load (and I am off-charge a LOT)
3. Auto-brightness - This will be adjustable in the next load - the issue is that the phone turns in with the screen in the "dimmed" state and there's a smoothing period before it reacts. You can set that with the next load to make it behave however you'd like (defaults are close to, but not identical to, how it behaves now.)
4. Headset. I think this is a hardware problem.
5. Music and calling: This is a common issue with Android; when the output and input sources get reassigned the current stream is interrupted. Same thing happens if you're on speakers and plug in a headset. I doubt it's fixable (I know why it happens, but preventing the switching task from throwing the exception upstream could have extremely bad results - I'll look at it at a later date, but this is common to a LOT of Android devices.)
6. Wifi is a documented issue.
7. Swype works fine. Download the CURRENT beta. If you're using a hacked version, all bets are off. I use Swype exclusively for my keyboard on this ROM. Ditto if you're trying to sideload it from somewhere (e.g. restore from Titanium) - don't do that.
8. MMS: Documented as broken.
The thread over on Androidforums is more current than the one here, but I will endeavor to at least mirror MAJOR updates here.
richiehd said:
Here is a random question. Does that lock/unlock flickering issue go away with this? What about the sometimes unresponsive back capacitive key?
Sent from my MOTWX435KT using XDA App
Click to expand...
Click to collapse
Yes, that was something I found with CM7. The screen flickering issue is not present. YMMV.
platypuss94 said:
* another thing i just recently noticed was that while i was in a call and holding the phone up to my ear, the screen would repeatedly turn on and off. i believe this may have been the way i was holding the phone but it happened more than once so this is why i thought to address it.
Click to expand...
Click to collapse
on this note i will say it is in fact how you hold the phone. it happens to me all the time on my stock triumph. no big deal and nothing to worry about. but thank you for saying something about it none the less.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the success of Smart Screen OFF and Smart Screen ON... Here is Keep Screen ON!
Keep Screen ON is an innovative free app that allow you to keep your smartphone screen ON in a smart way. This app will help you saving battery keeping the screen on only when you are holding it. This works thanks to orientation sensor built in your device (smartphone or tablet).
HOW DOES IT WORK?
When you are using your device, you hold it in a specific position. Keep Screen ON let you select the range of activation of the screen brightness based on the device inclination (more smart ways are coming soon).
WHY DOES IT SHOULD IMPROVE BATTERY LIFE?
You know for sure that screen brightness is the most important factor in battery life and you will find it always at the top of the most consuming factors in Android statistics. Keep Screen ON as name implies, keeps brightness enabled only when you are holding it: as soon as you left it on the table, the screen will turn off.
SO WHAT?
Download the app and extend your battery life!
FUTURE
This is first version and powerful improvements are coming soon.
+Battery tab
+Screen settings
+Brightness settings
I WOULD LIKE TO SUGGEST
I'm always open to users suggestions, simply contact me using the forum.
KEEP SCREEN ON PRO
AW: [APP][FREE] Keep Screen ON in a smart way
Cause of your great apps screen off/on and your great support I'll try keep screen on.
I'm using successfuly screebl beta for this since years.
Let the challenge begin
davall said:
Cause of your great apps screen off/on and your great support I'll try keep screen on.
I'm using successfuly screebl beta for this since years.
Let the challenge begin
Click to expand...
Click to collapse
Thanks. I hope you'll like it!
Very nice app, been looking for something like this for a while now.
I have one problem with it, when my phone is in its cradle it falls within the setting range and the screen times never times out.
It would be great if in the future there could a setting to disable the app when connected to an external pwr source and/or an option to let the screen time out after a specific time without any movement.
kantjer said:
Very nice app, been looking for something like this for a while now.
I have one problem with it, when my phone is in its cradle it falls within the setting range and the screen times never times out.
It would be great if in the future there could a setting to disable the app when connected to an external pwr source and/or an option to let the screen time out after a specific time without any movement.
Click to expand...
Click to collapse
Yes, that's a good idea. Disable during charge will be implemented in one of next releases.
I'll also implement a new way to react to movements in the space. :good:
[1.0.1] Little Bug fix for link to PlayStore developer page
AW: [APP][FREE] Keep Screen ON in a smart way
Hide Icon did not work.
After a reboot it works. :thumbup:
Gesendet von meinem GT-N7100
In test mode the model turns green in my hand and grey when the phone is placed on the desk.
When the app is activated proper, I don't notice any change.
Should the screen be turning off and on based on the test model? Am I mistaking the uses of this app, please tell.
Mayday_XL said:
Hide Icon did not work.
After a reboot it works. :thumbup:
Gesendet von meinem GT-N7100
Click to expand...
Click to collapse
Yeah, always make sure to "Save and restart the app" every change you make. If something doesn't work properly, rebooting could do the trick.
noble8 said:
In test mode the model turns green in my hand and grey when the phone is placed on the desk.
When the app is activated proper, I don't notice any change.
Should the screen be turning off and on based on the test model? Am I mistaking the uses of this app, please tell.
Click to expand...
Click to collapse
When you are using the phone, the brightness will never be turned off (screen won't turn off and brightness won't be dimmed).
As soon as you are not using phone anymore (you place it on your desk for example), the app will let screen turn off.
More settings about delay are coming soon :good:
Since some user asked, I will implement an in-app billing system to remove ads from app. It will be available in one of next releases with a couple of new features.
it doesnt work for galaxy s with cm 10.1 but it works for nexus 4
gomek111222 said:
it doesnt work for galaxy s with cm 10.1 but it works for nexus 4
Click to expand...
Click to collapse
Uhm, interesting... Maybe Cyanogen guys missed something orientation related in the rom.
Great to hear it works for Nexus 4, thanks for your feedback.
does not work on the HTC One X
crazyAlex2 said:
does not work on the HTC One X
Click to expand...
Click to collapse
Could you provide a logcat when running the app? After you have turned ON the app and pushed "Save and restart app".
[email protected]
Thanks
This app seems to work (till now) on my P970
DDeleted said:
Uhm, interesting... Maybe Cyanogen guys missed something orientation related in the rom.
Great to hear it works for Nexus 4, thanks for your feedback.
Click to expand...
Click to collapse
it work in the test screen but when i back to home screen the green man doenst change to grey man whe i put the phone plz solve this
(Please delete)
feature request
DDeleted said:
Yes, that's a good idea. Disable during charge will be implemented in one of next releases.
I'll also implement a new way to react to movements in the space. :good:
Click to expand...
Click to collapse
excellent application. its very useful. I would like to request you to implement a few extra features that will be handful in saving battery.
1. warning notification/dialogue for checking screen on time for more than 5 to 30 minutes. (even if the device is in motion or touchevents)
2. need screen timeout option to detect stillness. 1 min to 15 min
3. need to set screen off if the device is held vertical or horizontal ( bcoz we will not hold mobiles in 90 degree except when using camera.
Love this app!!
Using it in conjunction with your other screen off app, and between the two, my screen only ever comes on when actually in use. This is awesome yet so simple, great idea, looking forward to further development.
RR
gomek111222 said:
it work in the test screen but when i back to home screen the green man doenst change to grey man whe i put the phone plz solve this
Click to expand...
Click to collapse
Do you mean the guy in the notification bar doesn't change colour?
martinvillar said:
I hope it doesn't kill my battery!
Click to expand...
Click to collapse
It should not, at all.
shameemindia said:
excellent application. its very useful. I would like to request you to implement a few extra features that will be handful in saving battery.
1. warning notification/dialogue for checking screen on time for more than 5 to 30 minutes. (even if the device is in motion or touchevents)
2. need screen timeout option to detect stillness. 1 min to 15 min
3. need to set screen off if the device is held vertical or horizontal ( bcoz we will not hold mobiles in 90 degree except when using camera.
Click to expand...
Click to collapse
More battery related features are coming in the PRO version. And another free feature to set accuracy has just been added to lite version too.
Thanks for your suggestions.
richierich said:
Love this app!!
Using it in conjunction with your other screen off app, and between the two, my screen only ever comes on when actually in use. This is awesome yet so simple, great idea, looking forward to further development.
RR
Click to expand...
Click to collapse
Glad you are enjoyng the smartness
Hi there xda. A few months ago I posted my first app, IntelliCover, on xda-developers. It got a great response here and was featured on the front page of xda-developers and went on to feature on Discovery Channel's App Snap. Of course, being the smart person that I am...Well, let's just say I lost it...Yes, lost the app...Don't ask how. Anyways, I saw this as a chance to rebuild the app with all your suggestions in mind, from the ground up. So here it is, IntelliCover 2.0!
※ DESCRIPTION
IntelliCover 2.0 is a utility which uses your device’s proximity sensor, light sensor and/or accelerometer to turn the screen on and off, allowing fast and efficient access to your phone or tablet.
It turns the screen off automatically when you put your device in your pockets, close its flip cover, store the device in a bag, or even just leave the device facing down on a table. As soon as the device is back in your hand the proximity/light sensor is triggered again, the screen turns back on and your device in instantly ready for use. This improves productivity immensely on large devices or devices that do not have physical hardware buttons.
IntelliCover 2.0 is the completely revamped and redesigned version of IntelliCover, rebuilt from scratch after listening to the feedback of thousands of users.
※ COMPATIBILITY
IntelliCover works on all Android devices that have a light or proximity sensor, or an accelerometer. It does NOT require your device to be rooted.
※ FEATURES
• Sensor Calibration: Screen On Delay, Screen Off Delay, Suspension Timers, Application Suspension, Light/Shake Sensitivity Calibration
• Application Settings: Disable in Portrait/Landscape Mode, Go to Home Screen, Remove Lock Screen, Screen Off Only, Screen On Only, Start on Boot, Save Profile (Settings), Restore Profile, Restore Default Settings
• Modes: Proximity Mode, Shake Mode, Light Mode, Proximity and Light Combo Mode
• Notifications: Proximity Warning (Vibration), Status Bar Notification
• Toggles(Screen On/Off): Airplane Mode, Auto Sync, Bluetooth, Ringer Mode, Wi-fi
※ SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
※ CHANGELOG
Version 1.0.5 (07/09/2013)
•Fixed problems caused by previous update
Version 1.0.4 (07/09/2013)
•Added Russian language
•Added Pocket Protector Mode
•Fixed crashes, wakelock problems and screen timeout issues
•More battery optimization
Version 1.0.3 (24/08/2013)
•Fixed the crashes caused by previous update.
Version 1.0.2 (24/08/2013)
•Fixed both crashing issues
•Fixed "Remove Lock Screen"
•Fixed "Go to Home Screen" for ignored apps (Application Blacklist)
•Fixed toggles for "Start on Boot"
•Added Widget
•Added Screen Timeout patch
•Removed multiple memory leaks (Battery Optimization)
•"Screen Off Only"/"Screen On Only" now completely turns off proximity sensor when display turns off/on
•Reformatted all text to make it translation-ready (Turkish/Italian versions coming soon)
Version 1.0.1 (15/08/2013)
• Fixed Device Admin cancellation bug.
• Removed all Device Admin permissions except for Force Lock.
Version 1.0.0 (14/08/2013)
- Application released.
※ DOWNLOAD
Link to the Play Store: IntelliCover 2.0 v1.0.5
Awesome app!
Thanks a lot! The app works flawlessly on my Note, really handy indeed.
One question, is this app compatible with tablets, specifically, Nexus 7? I'm not sure if I'm doing something wrong but I couldn't get it to work on that device.
samsung_karl said:
Thanks a lot! The app works flawlessly on my Note, really handy indeed.
One question, is this app compatible with tablets, specifically, Nexus 7? I'm not sure if I'm doing something wrong but I couldn't get it to work on that device.
Click to expand...
Click to collapse
I'm glad you like the app.
Yes, the app is designed to work on all tablets, and has been tested for compatibility on Nexus 7 specifically. Tablets do not have proximity sensor (usually) so you'll have to use it in "Light Mode" which uses the light sensor instead. Don't worry, it works just as well as the proximity sensor. If you are already using light mode, please let me know and I'll try to help you. Can you tell me which Android version you're using?
dragonnis said:
I'm glad you like the app.
Yes, the app is designed to work on all tablets, and has been tested for compatibility on Nexus 7 specifically. Tablets do not have proximity sensor (usually) so you'll have to use it in "Light Mode" which uses the light sensor instead. Don't worry, it works just as well as the proximity sensor. If you are already using light mode, please let me know and I'll try to help you. Can you tell me which Android version you're using?
Click to expand...
Click to collapse
Ah, sorry, my bad. It works great in light mode. I assumed tablets had a proximity sensor (I'm kinda new around here ).
One more thing. I'm not sure if this is a bug, but when the Device Administrator page popped up, I clicked cancel by mistake, but it kept showing up again and again until I clicked Activate. It kept reappearing unless I accepted it.
Thanks again!
samsung_karl said:
Ah, sorry, my bad. It works great in light mode. I assumed tablets had a proximity sensor (I'm kinda new around here ).
One more thing. I'm not sure if this is a bug, but when the Device Administrator page popped up, I clicked cancel by mistake, but it kept showing up again and again until I clicked Activate. It kept reappearing unless I accepted it.
Thanks again!
Click to expand...
Click to collapse
Whoops, that's a weird bug. This is what I get for adding last minute untested modifications. I should've known better. =/ Thanks for the tip, I'll fix it by the next update. =)
Released an absolutely vital mini update. If you are on V1.0.0, please update ASAP.
Version 1.0.1 (15/08/2013)
• Fixed Device Admin cancellation bug.
• Removed all Device Admin permissions except for Force Lock.
Hi Dev.
Thanks for making a very good apps for us.
I am using your Original IntelliCover & its work great
on my Nexus 4 with Cover Case, I am loving it.
Should I need to uninstall the IntelliCover 1 & install the IntelliCover 2...?
Google Play doesn't show up update alert for the new v2....???!!!!
Whats the different between IntelliCover 1 & 2, I see the new one have
much larger file size, 1000k vs 4000k, Which version will work
best on my Nexus 4...?
Thanks...!
Its good but takes lot of RAM compared to intellicover 1 (almost three times). Thank you for making this app anyways but I am still fine with intellicover 1 and that works great. I have to say one thing, for me both work flawless. Please keep intellicover 1 also on google play. Looks like it is removed now.
Small bug that annoy me a lot and improvement request
Bug
1. Remove lock screen will work for sometimes only. It will not work after sometime. It will go back to lock screen mode automatically even the option I already select.
Improvement request
1. When manually press the power button to off the screen, set the program off for temporary so it won't auto screen on again.
Other than that, it is one of the best app I like :laugh:
Talon88 said:
Hi Dev.
Thanks for making a very good apps for us.
I am using your Original IntelliCover & its work great
on my Nexus 4 with Cover Case, I am loving it.
Should I need to uninstall the IntelliCover 1 & install the IntelliCover 2...?
Google Play doesn't show up update alert for the new v2....???!!!!
Whats the different between IntelliCover 1 & 2, I see the new one have
much larger file size, 1000k vs 4000k, Which version will work
best on my Nexus 4...?
Thanks...!
Click to expand...
Click to collapse
I would recommend installing the new version since I will not be updating the old version anymore and the new one has more features. But the new version is still a little buggy since I had to rebuild the whole app, so if you want to wait a little bit, that makes sense too. I couldn't post an update on the old one because I lost the keys for the app and all its data as well. =( That's one reason I had to rebuild it. That's also why the old one hasn't been updated in months. The new one is a bigger filesize because it has a lot more features and a big UI upgrade. =)
raj_k_r said:
Its good but takes lot of RAM compared to intellicover 1 (almost three times). Thank you for making this app anyways but I am still fine with intellicover 1 and that works great. I have to say one thing, for me both work flawless. Please keep intellicover 1 also on google play. Looks like it is removed now.
Click to expand...
Click to collapse
Yes, I realize it is taking up quite a bit of RAM for some reason. I wanted to get the app out there but I haven't started optimizing it completely yet. It makes sense for you to use IntelliCover 1 for now, but I plan on rolling out alot of updates soon that will optimize it, so keep an eye out.
phonixloo said:
Bug
1. Remove lock screen will work for sometimes only. It will not work after sometime. It will go back to lock screen mode automatically even the option I already select.
Improvement request
1. When manually press the power button to off the screen, set the program off for temporary so it won't auto screen on again.
Other than that, it is one of the best app I like :laugh:
Click to expand...
Click to collapse
The lock screen issue is a known bug. I'm working on fixing it as soon as I can, hopefully by next update. Manually pressing the power button should keep the screen off...Hmmm...are you using the proximity sensor or the light sensor?
dragonnis said:
The lock screen issue is a known bug. I'm working on fixing it as soon as I can, hopefully by next update. Manually pressing the power button should keep the screen off...Hmmm...are you using the proximity sensor or the light sensor?
Click to expand...
Click to collapse
In fact I would like to have featured once press the power button to shut off screen, it can automatically disable the program until we manually unlock the screen.
By the way I use proximity sensor only.
Sent from my HTC One X using xda premium
phonixloo said:
In fact I would like to have featured once press the power button to shut off screen, it can automatically disable the program until we manually unlock the screen.
By the way I use proximity sensor only.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, I'm adding that option too. It's been requested by many users, so I'll add it to "Screen Off Only" for the next update. =)
@dragonnis
im using galaxy tab which have no proximity only light sensor.
the program shut my screen too often while im still using the tab.
i have calibrated the app but still it is not working.
i do hope you can include a option to activate in lock screen or similar.
also would like to have tasker/llama/locale option of enabling dissabling of the app.
thanks
eclair88 said:
@dragonnis
im using galaxy tab which have no proximity only light sensor.
the program shut my screen too often while im still using the tab.
i have calibrated the app but still it is not working.
i do hope you can include a option to activate in lock screen or similar.
also would like to have tasker/llama/locale option of enabling dissabling of the app.
thanks
Click to expand...
Click to collapse
Once you calibrate the light sensor to a specific value, it will turn off as soon as it reaches that value. So if you have calibrated it for your bag, the screen may also turn off if you are in a pitch black room, because it has the same light sensor value. I've made the only workaround to this that I can think of, which is that if you are in a dark room, and you press the power button to turn the screen on, it won't turn off again automatically until the light value changes or you press the power button again.
But yes, I will be adding the "Only activate during lockscreen" option in a future update. =)
Edit: Not sure about how to create tasker/llama/locale plugins but I'll check it out as soon as I have time.
Pretty massive update. Fixes alot of common bugs. Thanks for sending in your reports! =)
Version 1.0.2 (24/08/2013)
•Fixed both crashing issues
•Fixed "Remove Lock Screen"
•Fixed "Go to Home Screen" for ignored apps (Application Blacklist)
•Fixed toggles for "Start on Boot"
•Added Widget
•Added Screen Timeout patch
•Removed multiple memory leaks (Battery Optimization)
•"Screen Off Only"/"Screen On Only" now completely turns off proximity sensor when display turns off/on
•Reformatted all text to make it translation-ready (Turkish/Italian versions coming soon)
Hi there, I cannot get this to work correctly on my HTC One. I have tried with both Sense and Aosp lockscreens. Is there something I need to do instead? I wave my hand in front and I can see the screen blink for a second and then that's it. Any help is appreciated. Thanks!
pmt223 said:
Hi there, I cannot get this to work correctly on my HTC One. I have tried with both Sense and Aosp lockscreens. Is there something I need to do instead? I wave my hand in front and I can see the screen blink for a second and then that's it. Any help is appreciated. Thanks!
Click to expand...
Click to collapse
Hello. Interesting, I've tried on the International HTC One but I've received a couple reports about the Sprint version having issues. Could you please tell me which model your phone is? I'm having a little trouble analyzing the issue without a device because turning the screen off is a native Android function that I just need to call upon so I'm not sure where the error lies but I'll try to get my hands on a device. Did the app ask you for Administrator Privileges? Also, if you turn on "Proximity Warning" from the Application Settings menu, do you feel a vibration on triggering the proximity sensor (Just to make sure the proximity sensor's being triggered)?
One last thing I'd like to ask is, does it work when you use your finger instead of a cover? Many proximity sensors don't do well with specific colors. I've had to stick a little piece of paper on my own cover where the proximity sensor lies because the dark brown leather makes the sensor go nuts.
EDIT: Just saw your signature and realized you have the AT&T version. Did anything I mentioned above work?
Released a quick-fix update. Please update to v1.0.3 to avoid the crashes caused by the v1.0.2 update
Awesome, the lock screen removal is fixed. :good:
samsung_karl said:
Awesome, the lock screen removal is fixed. :good:
Click to expand...
Click to collapse
Yup. Tested for a long time before I realized the issue was caused because whenever a notification in the status bar is clicked, the KeyGuard (Lock Screen) gets reset. I just had to detect when one of those notifications is clicked and run the deactivation process again.
I’ve used stock or (virtually stock) Android phones for years. My last properly skinned phone was a Samsung Galaxy s II. So using EMUI on this phone has been interesting. There is a lot that I like, but here I’ll describe a few annoying quirks I’ve noticed, plus any partial-solutions I use. Hopefully this will inform perspective and current P20 owners, but also, if you have a solution to any of these problems, do let me know!
- The settings menu is terrible. They have messed with it so much, and added so many settings, that it is often impossible to find what you’re looking for. The solution is to search, which, thankfully, works well.
- The lock screen wallpaper changes every time you unlock the phone. I feel like an idiot, but I can’t work out how to set my own (single!) wallpaper. There are these collections which you can choose between, and then from the lock screen itself you can favourite wallpapers from the collection (not sure what this does) and pause on a wallpaper from the collection, and it looks like you can add your own collections, but this doesn’t seem to work. There MUST be a work around. All I want is the same wallpaper on my lock and home screen!
- Notification content (including media controls) is always hidden on the lockscreen until you authenticate, regardless of the app setting. This seems to be a bug. Setting up face unlock (and swipe to unlock) at least means you can see your lock screen with notification content when at a face-unlock-friendly angle.
- The double tap vol down to launch camera works fine, except when I’m listening to music, when it just turns down the music. No idea why they don’t give this functionality to the lock button like most OEMs.
- Unlock by voice for Google Assistant doesn’t seem to work. I’ve had this problem on other phones so don’t know if I’d blame Huawei. It responds to ‘OK Google’ from screen off (which is better than my OnePlus) but won’t actually unlock.
- The always on display is a bit weak. It doesn’t even properly show notifications.
Anything to add? What EMUI quirks have you found?
Try this for always on display and notifications
https://forum.xda-developers.com/huawei-p20-pro/how-to/display-notifications-set-t3776376
The settings menu is terrible. They have messed with it so much, and added so many settings, that it is often impossible to find what you’re looking for. The solution is to search, which, thankfully, works well.
Click to expand...
Click to collapse
I find the settings menu perfect compared to samsung or other brands.
The lock screen wallpaper changes every time you unlock the phone. I feel like an idiot, but I can’t work out how to set my own (single!) wallpaper. There are these collections which you can choose between, and then from the lock screen itself you can favourite wallpapers from the collection (not sure what this does) and pause on a wallpaper from the collection, and it looks like you can add your own collections, but this doesn’t seem to work. There MUST be a work around. All I want is the same wallpaper on my lock and home screen!
Click to expand...
Click to collapse
Just open gallery, open any picture you want, set as background for home- and lockscreen, thats it
Notification content (including media controls) is always hidden on the lockscreen until you authenticate, regardless of the app setting. This seems to be a bug. Setting up face unlock (and swipe to unlock) at least means you can see your lock screen with notification content when at a face-unlock-friendly angle.
Click to expand...
Click to collapse
You can set to show always full content, even if not authenticated.
The always on display is a bit weak. It doesn’t even properly show notifications.
Click to expand...
Click to collapse
I´m sure there will be more options with further firmware updates
Anything to add? What EMUI quirks have you found?
Click to expand...
Click to collapse
I have sometimes problems with starting my spotify automatically when connecting a bluetooth device, I think a sleep mode problem. Another bug is the one with updating widgets. My calendar widget f.e. crashes after a time. found a workaround with "your calendar widget".
But I think all in all its a great phone with great features
lobr1 said:
The lock screen wallpaper changes every time you unlock the phone. I feel like an idiot, but I can’t work out how to set my own (single!) wallpaper. There are these collections which you can choose between, and then from the lock screen itself you can favourite wallpapers from the collection (not sure what this does) and pause on a wallpaper from the collection, and it looks like you can add your own collections, but this doesn’t seem to work. There MUST be a work around. All I want is the same wallpaper on my lock and home screen!
Click to expand...
Click to collapse
You can find this setting in 'Security & privacy' - 'Screen lock & passwords'
=> 'Update covers' to enable and disable it and 'Covers' to choose the pictures to show
EMUI has made me fall back in love with OxygenOS - the way EMUI treats notifications and the lock screen is diabolical. If I unlock my Oneplus 3 but don't read a notification, I can lock it again and the notification remains on the lock screen. The notifications span the whole screen, and work perfectly.
Also, Spotify on OxygenOS uses album cover art as lock screen wallpaper when playing, similar to how EMUI treats the local Music app.
This gonna be a debate for eternity.
People who come from xiaomi or samsung wont feel too awkward with emui,
Different case if you come from AOSP, or Oxygen or LOS.
Best solution is slapping NOVA launcher as soon as you use the phone.
I've used several Huawei phones now, in fact since the Mate 8 they've tended to be my main phones through most of the year (I still try others, but tend to come back for the battery life and cameras, granted the cameras have not been as good as competitors but the camera systems are more fun to me as a person with an amateur interest in photography and I've taken a lot of shots I don't think I could have got from the others). The P8Max was my first, and the UI/OS was a bit of a dogs breakfast - so many things were broken (many due to trying to increase battery longevity) and many other things required complex workarounds beyond installing Nova which I've had on each of them. It's pretty well fine now, but if you're coming from Samsung or others it's very different and will take a bit of time to adjust to - particularly the level of granular control you have on things affecting battery life. Once you get a handle on it you'll probably end up appreciating a lot of what it offers.
Google Assistant works fine but it makes conflict with Huawei voice control (so turn off one of them)
Double tap volume down to launch camera is a great idea but why the hell it does not work when players or different apps are in the background.....
Hi there!
Setting your own lockscreen carousel:
Settings>security & privacy>screen lock & passwords>magazine unlock>subscriptions>added by me>add>choose image
You can create your own cycle of wallpapers.
In themes App make sure you set me>customize>lock screen style>magazine unlock
I wish adjusting the volume on Bluetooth headphones adjusted the master volume like on all previous phones I've had instead of acting like an in-line control.
Sent from my CLT-L09 using Tapatalk
Hi how do you get rid of double tap on home screen it's do annoying it's a short cut to access latest apps that have used I have Nova Which is excellent and I'm coming from a Samsung S7 to a P20 pro please help !!
To enable or stop scrolling wallaper just swype from the bottom on the lockscreen and you will see Pause button at the left. if you press that, the scrolling will be disabled and a "play" icon will remain.
I've debloating quite a lot from emui.
Installed swap torpedo
Runs faster now and battery lasts longer.
Huawei should offer a vanilla update.
Last time I saw so much bloat was on Samsung.
Unnecessary.
EMUI was one of the reasons I ditched my P10 after 6 months, went back to an iPhone, then to a Nokia 5...
Have any of the roms developed for the P20 done away with EMUI otherwise this device will be another one i'll have to remove from the list of potential upgrades.
Killing foreground apps
Hi, just bought the p20 pro after years with Samsung. I have noticed that it often kills apps that I am currently using, sending me back to the home screen (reminds me of a crash to desktop in windows computers).
After some googling similar problems I adjusted the app auto start and ignore battery optimization settings and it did get better, although it is still killing apps which I presume is using a lot of memory or battery (or both?), for example posting stuff on Instagram (Instagram is whitelisted from optimization and managed manually).
This is really bugging me, anyone else with the same problem? I'm running android 8.1.0, EMUI 8.1.0 and memory always stays between 2,5 and 3 GB.
vmaxx82 said:
Hi, just bought the p20 pro after years with Samsung. I have noticed that it often kills apps that I am currently using, sending me back to the home screen (reminds me of a crash to desktop in windows computers).
After some googling similar problems I adjusted the app auto start and ignore battery optimization settings and it did get better, although it is still killing apps which I presume is using a lot of memory or battery (or both?), for example posting stuff on Instagram (Instagram is whitelisted from optimization and managed manually).
This is really bugging me, anyone else with the same problem? I'm running android 8.1.0, EMUI 8.1.0 and memory always stays between 2,5 and 3 GB.
Click to expand...
Click to collapse
This is one of the biggest problems I have with this phone. It keeps killing Skype and I miss calls due to it...
rajeshr said:
This is one of the biggest problems I have with this phone. It keeps killing Skype and I miss calls due to it...
Click to expand...
Click to collapse
Yeah, it's turning out to be a deal breaker for me.. Too bad since I really like the phone. Just hope it's a bug ?
Something seems to be happening to spotify when it is running in the background using my bluetooth headphones. I get stuttering and odd pauses, its basically unusable.
I have found if I use andriod auto to run spotify or use the wake lock program to keep the phone in a higher power mode it seems to help. If I have the charger plugged in it works fine as well. It appears to be some sort of power saving issue (yes I have told the phone to ignore spotify's power usage) or something to do with bluetooth power saving. But it works fine in a car.
Thats my only real complaint, and had I known I would have this issue I would have probably grabbed a onePlus device. Using Sure 215's
One thing I did notice, and I also fixed the problem quite simply.
I turned the display Resolution to HD from FHD my thinking was with a lower resolution I'd have better battery and better performance.
What I got was worse.
60fps lagged so badly it was unusable.
Transitions especially to the Google feed lagged and was annoying.
Asphalt 9 lagged and was extremely crap.
Turned FHD back on, all went back to silky smoothes??
Logic didn't exactly prevail here but it works.
So in short if you've turned on adaptive resolution or HD.
Turn it off
I'm facing this weird problem with my p20 pro. In. 128 and 131 and 152 firmware versions whenever in have an incoming call my screen doesn't wake up to show my who is calling me, unless I press the power button or the fingerprint sensor. If the call is missed my screen wakes up normally to show me the missed call notification. Any solution?? I have no fingerprint lock or pass code lock. Just swipe.
Sent from my CLT-L29 using Tapatalk
So I know there are other android 10 threads out there but I felt like y'all should get a list of whats new in front of your eyes instead of looking around:
**Improved night camera quality - Yes I have felt and improvement it is slight however, but it did get somewhat better.
**Google's new navigation gestures (I felt like I should write this because last updates, Sony phones did not get the nav gestures) however the new gestures seem just a tiny bit laggy -rarely though- and when in landscape mode, the slide down bar drops not in a symmetric way but rather drops right sided which makes things look out of place
**New CinemaPro app features - the app now has the levels of both phone microphones like on the v50 and also has aspect ratio check lines (if you want to shoot a video on cinema pro it only shoots 21/9 but you can have check lines to see whats being viewed in any other aspect ratio you choose and you also have a meter inside the camera to show you if youre in the frame or not)
**Dark mode - works on most apps, but I can't seem to activate it on my phone app, any suggestions?
**UI click sounds changed - yup! I love the new ones they sound more like Android rather than Sony and I do love Android!
**FINGERPRINT!!!! - Yes!! finally fingerprint scanner is way more responsive now!! before it was sooo strict about the cleanness and the angle, I registered 3 fingers and it only could recognize one of them because of the angle it provides, but now every finger on any angle with less cleanness is verry responsive! (could still be worked on, but im so happy with it at this moment)
**Sadly no more face unlock, even though I never used it but it worked surprisingly fast when I had the option available, but now it doesnt exist, good thing they improved the fingerprint scanner XD
**Slightly improved battery life - I only noticed it when I tested it, but if youre not a detailed tester you wont be able to recognize throughout the day, maybe if youre a slight user, yes you will notice the phone lasting 2/3 hours longer (overall usage and not screen on time) because I can tell they worked greatly on improving the idle drain.
**Speaker loudness - I think the phone got louder? I am not sure but defiantly notice something that didnt exist, not necessarily higher quality but I do notice something increasing in volume I cant tell if its volume or distortion lol but when I go to max volume there is something that makes you think, a little lower than max sounded like max on previous android but I cant tell if max here is actually louder or just more noisy especially with dolby atmos
**Some people reported signal drops? or bad signal? I havent noticed a difference here so thats good news
**Performance - the phone was fast enough to almost be the king of speed and smoothness so yah even if its better on android 10 I cant even feel the difference but it is VERY smooth even on a new android which means its pretty sick!
**Recent apps button (in old school 3 button nav bar) doesnt seem to do anything if you have custom launcher, but works on default sony launcher.
UPDATE!!
**one handed mode, which I use alot when im in bed, cant seem to be activated in the new navigation gestures, because you have to double tap home button but u dont have it in new gestures, so heres what i did:
Enabled side sense, i know it doesn't work properly, but now you have an option of controlling how to access it, You can actually enable the inside the screen tap rather than from the side (if you have a case on, this will really help you) , adjust sensitivity, position, transparency of the slide activators, and change the gestures of how it works, now i changed the double tap side sense from opening the side sense menu, to activate one handed mode, and now side sense works smoothly with gestures and i can activate one handed mode in new android nav gestures, youre welcome
Thx u for this thread
UI seems a lot smoother. I'm liking the android 10 gestures which adds to the "smoothness".
Can't really say about photo quality, haven't been using the camera much. I can definitely notice a better battery life compared to before.
Basically no issues just yet! Aside from me getting used to the new gestures (+ side sense)
Im using the google dialer app in play store. It has a way better ui, better icons and dark mode compatible. Set it as default and it's all good. I don't understand why sony have decided to use the "stock" google messenger app but not dialer... the dialer seems customized in some way idk
There is a bug that I noticed: when going back home using the gesture, if the app icon is on the dock, the icons a bit laggy and will flash for once. don't really know how to describe it
Someone can make a full review of android 10 and post it on youtube ?
Sugarcube8th said:
Im using the google dialer app in play store. It has a way better ui, better icons and dark mode compatible. Set it as default and it's all good. I don't understand why sony have decided to use the "stock" google messenger app but not dialer... the dialer seems customized in some way idk
There is a bug that I noticed: when going back home using the gesture, if the app icon is on the dock, the icons a bit laggy and will flash for once. don't really know how to describe it
Click to expand...
Click to collapse
Yah you just reminded me to add that bug, also if you on landscape mode the slide down bar is off place slides from the right rather than the middle of the screen
Pandemic said:
Someone can make a full review of android 10 and post it on youtube ?
Click to expand...
Click to collapse
I will try to do so soon, when I have free time from work
Agree with you.
- about the signal, i notice less signals bar (1-2 signal bars most of the time), but no connection drop (yet)
- wifi Mac address new option, set by default at "random Mac address"
Here's a preview of the swipe up animation bug?
https://youtu.be/ZM0Exs9F4yQ
Does anyone else have a weird audio bug where when you pause music or a video the sound spikes up for a second before it pauses. I've only tested it on the native music app and YouTube. I don't use any music streaming service such as Spotify or Pandora. I think I've concluded that this is a software bug since I when I flashed back to the previous firmware and didn't have the same problem. Maybe my device is just strange. Any opinion?
Arsyian said:
Does anyone else have a weird audio bug where when you pause music or a video the sound spikes up for a second before it pauses. I've only tested it on the native music app and YouTube. I don't use any music streaming service such as Spotify or Pandora. I think I've concluded that this is a software bug since I when I flashed back to the previous firmware and didn't have the same problem. Maybe my device is just strange. Any opinion?
Click to expand...
Click to collapse
Yes,I have the same issue, but as I remember this issue also existing on Pie.
t238z said:
Yes,I have the same issue, but as I remember this issue also existing on Pie.
Click to expand...
Click to collapse
That's strange cause I never had the problem till updating to Android 10.
I think i have a bug i have notification from album that i cant remove it. Even though i have restar my phone
It always check the update
blegs said:
I think i have a bug i have notification from album that i cant remove it. Even though i have restar my phone
It always check the update
Click to expand...
Click to collapse
this happens with me with BG player.. I simply turned off its notifications
Sugarcube8th said:
There is a bug that I noticed: when going back home using the gesture, if the app icon is on the dock, the icons a bit laggy and will flash for once. don't really know how to describe it
Click to expand...
Click to collapse
Precisely, IDK if that happens with pixel or one plus devices, but I know that it happens with Xperia 1. When you go back to the app, let's just say it's inside a folder, app shows in the dock then the folder pops back. Then if you open an app let's just say dialer then you switch to camera with recent menu and you go back to home screen it shows dialer app on where the camera icon then you get the camera icon back in the dock. Am I right?
[Bug report] Recent key not working in Android 10.
Screenshot as below: https://www.youtube.com/watch?v=hUlHZ0weCfs&feature=youtu.be
When you press Recent button, there is just nothing.
Remember people more updates will vome of android 10, this is the 1st release so except some tiny bugs. Sony/google will fix that
just added some more updates about bugs and updates in main post check it out
kevinkoo said:
[Bug report] Recent key not working in Android 10.
Screenshot as below: https://www.youtube.com/watch?v=hUlHZ0weCfs&feature=youtu.be
When you press Recent button, there is just nothing.
Click to expand...
Click to collapse
whats that launcher?
Just got mine an hour ago. Hoping that I don't experience those bugs.