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.
Hi,
So ~3 weeks ago I got my HTC Sensation XE, eveything has been working flawlessly up until last week.
Issue:
When I start playing video on YouTube App. ( latest version ), it lags for 2-3 seconds, then the next 2-3 seconds are played in slight fast forward and so rinse and repeat. For some videos it's much more distinctive, for some - barely noticeable. This issue causes sound to be desynced as well, for a brief period.
I did factory data reset and nothing changed ( well obviously.. ) except that the preinstalled/default YouTube App. has a different issue. Video playback is fine and such, but it starts lagging whenever I bring up the timeline bar and does not stop unless it disappears.
I did notice that phone has been responding in a sluggish way as well. For example, it sometimes lags when scrolling a list in an App ( Market, etc. ) or just scrolling a change log text ( not that huge ) for an App; thing is - about 80% of the scroll..it scrolls like a slideshow and sometimes it just scrolls flawlessly. You might say that problem is in loading the lists/videos..., however I think that's not the case because the videos are cached fine, signal strength is good. I did test for these issues on different WiFi's and 3G, however, to no avail.
Warranty "Service" + Test
I did take my phone to Warranty service, they did * reprogram* it ( My guess is that they did factory reset ), of course problem was no fixed. I did take it back again to show it, but they replied that they did what they could ... ( part where I get pissed ... might as well as return to them ... )
Well since I am in a conversation with HTC Support, the conclusion that they made was much more appealing and logical - it's either antenna, need for a re-flash or mobo change.
So since my network is working fine and I have no trouble or whatsoever with LOADING the video, the issue HAS to be in the PLAYBACK part ...
I decided to some deductive testing.
I ran YouTube App and Internet browser to check for these problems.
As it turned out, I had no problems in video playback using internet browser both for youtube.com and m.youtube.com, it even played 1080p video ( not really well, but it was much ,much more bearable that those 2-3 second lags and also .. it might be part of the issue I am having )
Then put my phone side by side to PC. Videos using Internet browser were played 1:1, when I played them on YouTube app., phone was noticeably lagging behind and catching up all the time.
So this points to software problem direction.
However I am still concered about Hardware problem since the 1080p was not played really smoothly ( well, it should, shouldn't it ? ) and generally sluggish phone.
Click to expand...
Click to collapse
Questions:
1. Are these Software or Hardware issues? How do I exactly tell that?
2. Since I am seriously concering ROOTing the phone and flashing with CM if the issue is software based, what are main tips to search for? ( What causes bricking of the phone/how to avoid that... etc. )
3. Can any of you give a quick rundown of these terms and how do they differ?
ROM - that's Android OS 2.3.4 (Gingerbread) ... ICS etc., right?
Firmware - ???
Kernel - Hardware level controller??
Baseband - Radio ( WiFi/3G/GSM ?? )
and some more off from "About phone"
- what is Software number?
- what is build version?
- what is Browser version?
Hi everyone!
So I've recently purchased a Mate 9 and while I absolutely adore most aspects of the phone, there's a high number of crashes every day that keeps bugging me.
Ever since I got it (like literally Day 1) it has been crashing on like 80% of all game launches (tested with a dozen of games, it happened randomly and not with distinct games for example), on around 50% of all landscape rotations in photo apps, on like 20% of all landscape rotations and lastly, on around 10% of camera usage and viewing.
I'd assume it is an issue with the gyro sensor being buggy or whatever because it basically is limited to the screen's rotation but I'm not sure.
Did anyone else experience this? Does anyone know how to fix this?
My Mate 9 has the most recent firmware, is neither rooted nor equipped with a custom ROM - I'd prefer to not just factory reset it, so if you have any ideas on how to avoid that, I'd be very thankful! <3
Had bunch of problems on my 432, like voice command problems, Google Calendar sync issues and similar. Factory reset and installing Google calendar fixed them all.
Hello all,
There is a consistent issue that i have been dealing with ever sense the Oreo update rolled out that I have not been able to find a solution for. At times ( watching a Youtube video/ listening to music from Spotify) media audio would begin playing from the phone as if it was ring/ notification audio. All sounds coming from the phone would get cut back in volume by a significant amount and the bottom speaker stops firing completely.
This only seems to happen once I interact with the app after starting to play the video/song (i.e i go to pause a video/ advance 10 seconds). From that point I would need to leave the app and come back for the audio to go back to normal.
As well I have been having audio video sync issues with the Youtube app that I have never dealt with before, related?
I have the US duel sim variant
I am on build number 47.1.A.5.51 , November security patch
I have tested with all audio settings on/off ( EQ, S-Force,ClearAudio+,normalizer)
I have checked the service test menu and everything is shown as calibrated.
Restarted the phone, cleared various caches for apps
I really am at a loss here, anyone else having these issues? Any possible causes/ solutions?
I had that issue on the first version of oreo... I found the latest oreo update fixed it. Maybe uninstall youtube app and reinstall again?
Were you able to fix this issue?
I have the same problem but for me it happens on all applications.
Mate 20 Pro on EMUI 10, although the issue was also there on EMUI 9
Hi all,
I have what seems to be the same issue but in Android 9 PIE, & latest build 47.2.A.10.107.
I didn´t had this issue in my Xperia XZ Premium G8141 (single SIM) , now it happens after switching to a Xperia XZ Premium G8142 (same phone, but dual SIM, same as you have).
In my case I get around opening volume controls and moving the ring and notification volume (with its slider) for some amount back and forth.
Y don´t use youtube so much (in the phone screen) then I cannot tell if it happens with youtube, but does happen in Spotify and it is very annoying to have to correct every now and then.
Then, same phone, completely different Android version, hardware problem?
Will appreciate any hints or troubleshooting tips from you guys.
When I have some time I will take a look to the kernel messages cable-connecting the phone for USB-debug.
Thanks in advance,
Take care,
Alvaro
Not sure if I'm the only one but I always face audio latency issues while gaming with my Bose AE2 SoundLink. Unfortunately I don't have other Bluetooth devices to test it but it works with all my wired headsets.
Only via gaming I face 1-2s latency. I searched the Internet and found solutions like locking the refresh rate but this doesn't work. It's the same for all games, I already tried repairing the headset, tried all modes (x mode) and different settings but it's always the same for every game. As soon as I switch from a normal app to a game the audio lags - everything else (calls, YouTube, etc etc) works fine.
Has someone else the same issue and got it fixed?
Asus 5 ultimate,
Latest firmware as of now (.86)
Rooted
I haven't tried connecting to my speakers, but i'll give it a try and see if I get similar results.
In the meantime, are all of your games running on a profile? What are your settings? I'll go through with all the same stuff.
Things are a little behind on my end. Note 20 Ultra screen decided to start peeling off, so i've been trying to move over everything for a trade-in before it ends up cracked.
It's normal for latency to be higher when gaming, though 1-2 seconds is definitely way too much. It's usually a difference of 0.5 seconds at most
Sorry for my late reply - I was really busy the last weeks.
I had the chance to try it with different devices and it's the same for all of them. I notice it a bit more for some games and a bit less for others. For example Grimvalor has a huge delay that can be noticed really easily because it makes a sound when you slash your sword -> sound starts after the animation is done.
https://play.google.com/store/apps/details?id=com.direlight.grimvalor
I doubt this is a hardware issue since everything works when I don't play games but other media. However I have no idea what the technical differences between games and videos are in the Android world.
Things I tried so far (unsuccessfully) :
factory reset
remove the game from Armory Crate
change refresh rate as well as other settings
try different games
Everything works with a wired Headset or with my old phone.
Not sure if the support can do something but I'm surprised that I'm the only one with this issue.
twistedumbrella said:
In the meantime, are all of your games running on a profile? What are your settings? I'll go through with all the same stuff.
Click to expand...
Click to collapse
I've tried it with and without a profile - that doesn't make any difference.
What settings do you require exactly, I could export a game profile if that helps?
I completely forgot about testing. If none of the settings seem to have any impact, i'll try the defaults. If I can't get the same results, then ill see about trying to find any that cause it.
...oh, it's definitely off. I connected a Wonderboom and launched Nier and pressing the buttons had just enough delay to notice it was out of sync.
Thank you - so I guess it's not just mine.
Not sure if contacting the support will solve the issue. I wonder if all others don't have this issue, don't care about it or better Bluetooth devices.
@reica since you don't seem to face this: could you tell me what device you have or did you change Bluetooth related settings?