Hi, first time poster! Anyways I recently acquired the HTC Fuze which is my first Windows mobile phone and everyhting semmed to by working fine until today. Now whenever I enter any games, the camera, or any program that requires the G-sensor it always assumes I am in landscape mode and I am unable to move to portrait mode even when the phone is fully up right.
The sensor still seems to work, but only in landscape mode. I have applied several tweaks and added several applications, but none that were anything major and none that have to do with the G-sensor (at least I think). I have also tried calibrating it several times and the every seems to work right it just won't leave landscae mode. Anyways, is there any way I can fix this without a hard reset (trying to avoid)? Also my phone is still under the ATT 30 day return policy so should I just return it and get a new one?
Thanks to anyone that can help!
does the calibration tool give any feedback?
are you sure your taking the pictures rightside up w/ the camera?
some games require u to flip out the keyboard for landscape or portriate mode, have u tried toggling the keyboard?
Yes, the calibration tool seems to work fine.
Also about the keyboard,yes I have tried that and it seems to work for some applications, but some applications stay in one mode regardless of whether I have it flipped up, down, right, left, or with the keyboard out.
Okay. it now works again, but the when I want to take a picture it is in landscape mode still. I can take a picture in portrait mode, but all the photo adjustment modes (when you tap the screen) are still in landscape, but I think I might know what caused that. I made of few adjustments to the registry to get some more camera modes and i think that might have caused it. Also, why do American cellphone carriers have to stifle innovation by removing the front camera?
Thanks for your advice Orbitrix.
G-sensor only works sometimes
Usually, the G-sensor does not rotate the phone when it is supposed to in various apps-like photos. I have tried adjusting the timing in Advanced Config and using the calibration tool. Sometimes it works perfectly, but usually, nothing happens. This is VERY frustrating!!!
Anyone have any other fixes?
Rom version: 1.90.707.4 WWE
Rom date: 8/23/08
Radio version: 1.02.25.19
Protocol version: 52.33.25.17U
Some progress??
I just noticed, that if I open the Pictures/Video program, so it brings up the screen of thumbnails, then open a photo from there, the G-Sensor doesn't work when I tilt the TP. However, if I scroll through the photos in the TF3D interface, then select a photo from there, the tilt works very quickly. (I reset interval to 75).
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.
Hello
I have a HTC HD2 flashed with ParanoidAndroid 1.5b. I was trying to run the Sygic GPS navigator but it crashes after a while with ICS. This is not a problem with the ROM but with the application. So far so good. However, I found out that since the application opened the GPS to try to get a fix, when it crashed it left the GPS "on" (although the icon on the status bar disappeared after a while). I tried another GPS navigation program but it couldn't get a fix. I thought it was the GPS configuration, so I changed it to reflect my region (Europe, Greece). But to no avail. Whatever I tried, I couldn't get a fix. I rebooted the device and tried GPS status, it got a fix after a minute or so. If I run Sygic (which crashes) again, it is impossible to get a GPS fix afterwards. If an application that uses the GPS crashes while the GPS is on, it leaves the sensor working. However, there is no indication that there is a problem, as the icon disappears after a while, and gets back on when another app tries to use the sensor. It just can't get a fix. What's more, the battery starts to drain after that (easy to spot with Current Widget, since the draw goes from 6-7mAh to 105-107mAh)
Switching the GPS on and off (from the notification drawer) does not fix the problem. The only solution is to reset the device.
My question (finally) is: is there another solution to "resetting" the sensor to its original (after the boot) state?
Best regards
George
Hello,
maybe someone can help with my issue.
I got a new OP8 Phone some days ago and transferred all data from my old phone. While setting up the banking app "Deutsche Bank Mobile" i experienced a weird issue with the screen starting to flicker and inputs are recognized only randomly. It only happens in the screen where you have to set up you personal app pin. It seems like an app problem, since it only occurs in this app in that particular sceen. You also see a blue dot appearing randomly on the middle of the screen. See this video for Details:
File on MEGA
mega.nz
What ive tried so far:
- Clear app data and cache
- Clear system cache
- Set display refresh rate to 60hz and vice versa
- enable/disable dc dimming
- set screen to full brightness
- change graphics driver for the app in developer setting (idk if this makes a difference, theres only the choice between standard and another specific setting)
I dont know if its a system or an app related problem. Maybe someone can help?
MrSliff said:
Hello,
maybe someone can help with my issue.
I got a new OP8 Phone some days ago and transferred all data from my old phone. While setting up the banking app "Deutsche Bank Mobile" i experienced a weird issue with the screen starting to flicker and inputs are recognized only randomly. It only happens in the screen where you have to set up you personal app pin. It seems like an app problem, since it only occurs in this app in that particular sceen. You also see a blue dot appearing randomly on the middle of the screen. See this video for Details:
File on MEGA
mega.nz
What ive tried so far:
- Clear app data and cache
- Clear system cache
- Set display refresh rate to 60hz and vice versa
- enable/disable dc dimming
- set screen to full brightness
- change graphics driver for the app in developer setting (idk if this makes a difference, theres only the choice between standard and another specific setting)
I dont know if its a system or an app related problem. Maybe someone can help?
Click to expand...
Click to collapse
What OOS version were you on when it happened? It's a bug that usually occurs when playing video games, but has been fixed since the latest update.
Check the updates, install them and if it keeps doing that maybe contact the customer service to get a new one
Hi guys I'm new on here, i do apologise if i have posted on the wrong area , i have a Chinese 10.1 inch android SPRD head unit with android 10 installed. I have fallen out with the guy i bought it off as there was a lot of miss advertisements on advert which did not match when i got the unit.
However thats another story and wont get into it, what i want to know and if anyone can help me i will really appreciate it as iv tried everything and getting no where. So here are my problems :-
1, Upgrading android 10 to android 11.. there seems to be no menu that has the upgrade option, so how can i upgrade to android 11 or twelve? And How do i upgrade mcu version?
2, im having problems with GPS when car is on i loose gps signal to like half of one bar.. when car/ignition is turned off GPS comes alive and get good signal and catches satellites.. what does this happen? Whats the solution?
3, i cant change the icons on home screen, cant change/add on tool bar, no bluetooth button to turn on and off on bar on top of screen.. but blue tooth is there works fine when connecting phone and bluetooth icon shows on top bar when connected..
4, the android version seems very limited on this unit, even in developer settings there dont seem to be many adjustments options to turn on or off.. i have a meter display shows cars rom gauge and speedometer its all im KM and there is no options anywhere to change this..
5, system does not shut down when car ignition goes off, i have to manually shut it down, even tho in settings its set to shut down when acc off! Any suggestions?
I have attached pictures of GPS ignition off and one of ignition on.. also all the build software info pictures too..
Any help would be appreciated
1. There's is no upgrade to Android 11 or 12.
These FYT 7862 units only go as high as Android 10. That may change in the future (maybe not) but any that you see say Android 11 or 12 it is fake (like mine, fake Android 11).
2. Are you using a GPS receiver that you got with the head unit or are you using your cars original GPS sensor? Where is it placed? Need more info to answer this
3. I don't know what home screen launcher is installed on your unit so cannot answer. Some launchers cannot change the icons, some can. A photo of the home launcher might help.
j0hn83 said:
1. There's is no upgrade to Android 11 or 12.
These FYT 7862 units only go as high as Android 10. That may change in the future (maybe not) but any that you see say Android 11 or 12 it is fake (like mine, fake Android 11).
2. Are you using a GPS receiver that you got with the head unit or are you using your cars original GPS sensor? Where is it placed? Need more info to answer this
3. I don't know what home screen launcher is installed on your unit so cannot answer. Some launchers cannot change the icons, some can. A photo of the home launcher might help.
Click to expand...
Click to collapse
1, thank you for clarifying
2, cars gps is connected as well as the external gps sensor. As it it dual system (can access cars original system as well as switch to android) cars gps on the car system works fine. The android gps is acting starnge, currently it is behind the dash right behind the head unit mounted on a metal plate top of antenna facing north…
3, i will up load picture shortly of my launcher screen
Thabk you
j0hn83 said:
1. There's is no upgrade to Android 11 or 12.
These FYT 7862 units only go as high as Android 10. That may change in the future (maybe not) but any that you see say Android 11 or 12 it is fake (like mine, fake Android 11).
2. Are you using a GPS receiver that you got with the head unit or are you using your cars original GPS sensor? Where is it placed? Need more info to answer this
3. I don't know what home screen launcher is installed on your unit so cannot answer. Some launchers cannot change the icons, some can. A photo of the home launcher might help.
Click to expand...
Click to collapse
Thats my current launcher john
Update :- problem solved i moved the gps antenna and stuck it behind the head lining restarted system and voila its working now. I had it behind the dash and on top of dash but looks like too much interference for it to work there.