Hi Guys,
i bought a card 2DIN unit with android - for Toyota RAV4 - which is actually based on the android HW which is used from TV Sticks.
Model Number: TCC8925
Android Version: 4.0.4 ( V2.2 2013-08-30 SAMSUNG K9GBG08U0A )
Baseband version: Unknown
Kernel Version: 3.0.8 - tcc [email protected] #194
Build Number: TX_T7D_(LC-RGB-BMW)_V2.2_2013-08-30
succesfully rooted - and almost works as it should but: I have for now one big issue with that unit - i have some kind of white noise on the screen - but only on the android screen (As the radio has two modules - DVD (radio, DVD, etc) and Android Modules - both are sharing the display.
In DVD menu the screen is clear. The same is when i'm doing android reset - the frist green picture with the android is clear - and directly after that, the screen starts to flicker - or how to say - it is kind of white noise or sync noise on the screen - but only in the android. Switching to DVD module - and the screen is ok - so it is not the screen what is faulty. I'm assuming as well it is not the android module faulty (hope) as the first android screen directly after reboot is clear.
See attached picture and video file.
Contact with Enco (radio manufacturer) is almost impossible.
What can it be??
First i tried already if all connectors are ok on the boards - but still the same.
Android screen driver?? Wrong screen sync settings?
Related
Hello,
I hope I am in good part of the forum - I have a question to Android geeks -> I have an idea on the project (which in case of WinCE based navi units is explored - but not in Android based ones) - to put an Android based tabled with GPS or GPS navigation unit as a navi unit in my VW RCD510 device... My first question is -> is there a possibility to connect external screen with touch-screen which will be different resolution than the native one on the Android based unit... In particular - the RCD510 unit has a screen resolution (with touch) of: 400x240 pix (6,5") screen...
Is there a possibility to connect that to the tablet or navi unit with Android and to use that screen to controll (completely) the unit??
The main screen of the unit may be not used - it does not make me difference - I only ask about such thing, as I am not really good in Android...
Just one more thing - I do not think about "on-the-go" - it may be some dismounting etc stuff - just to make it work (if possible at all)...
I will appreciate your help...
OK, so this is a really weird one. Never posted before as never had problem like this!
Current: SG3 i9300 international
Flashed a few ROM's without issue. Yesterday I flashed Slim Bean (had it on this device before without issue, so don't think it's the ROM). Full wipe etc before and after flash. After boot, I get to the homescreen and this strange 'notification' type sound repeats, like doo-de-doo doo-de-doo over and over again, sometimes it lags and overlaps itself, sometimes it stops altogether for a few seconds, then starts again. It stops totally when the screen goes off (deep sleep?). Really annoying.
No problem I thought - flash something else, so I tried another two ROMs (PA and Cyanogen 10.1) - full wipe before and after. Exactly the same issue occurs.
No problem I thought - I'll go back to stock, then come back to custom.
Went back to stock ROM (unrooted again) and suprise, suprise the noise was gone! Brilliant - fixed!
Flashed PA 3 this morning and the stupid noise is back again...
Any one got any ideas whats going on here? I don't think it's the ROM's themselves, but not overly techie, so wouldn't rule it out completely - the fact that it happens across loads of different ROMs makes me think it's not that causing it...
Model GT-I9300
Android 4.2.1
Baseband I9300BUELL1
Kernel 3.0.31-CM-g0ae4324
[email protected] #1
Sun Feb 10 20:33:40 IST 2013
ParanoidAndroid Version
3.00
Build
pa_i9300-userdebug 4.2.1 JOP40G
eng.bidyut.20130210.200657 test-keys
Seems to be affected by the volume of notifications, but not ringtone, alarm or media. I can't find a matching notification in my phone... although it sounds similar to "Bellatrix" notification.
Moved to 1st post - sorry guys...
Moved to 1st post - sorry guys...
Moved to 1st post - sorry guys...
4 posts in a row? you can edit your post.
Fixed - turned off NFC. Thanks all for taking the time to look.
Like most people I updated to the 4.3 and the new base band through the sony pc companion and everything was great for the first week, but then the red flags started to go off and here is the list:
- My games and apps that were working fine would not open even sonys stock apps. Tried re starting the phone and it would still not let me use them.
- draw back issues on the lock screen (5sec) and home screen wallpaper (10 sec) plus it auto reverted back to an older wall paper.
- when I connect it to my dock the lock screen does not auto rotate to landscape mode.
I have gone back to factory reset but issue number 2-3 still persist. Can any one help me either solve these issues or tell me the best way to downgrade to the 4.2 stock firmware.
MOEL C6833
current base band is 8974-AAAAANAZQ-10270025-26
KERNEL VERSION
3.4.0-PERF-G4F35567
[email protected]#1
TUE NOV 19 19:53:25 2013
BUILD NUMBER
14.2.A.0.290
Any help will be greatly appreciated. Thanks.
ujan1 said:
Like most people I updated to the 4.3 and the new base band through the sony pc companion and everything was great for the first week, but then the red flags started to go off and here is the list:
- My games and apps that were working fine would not open even sonys stock apps. Tried re starting the phone and it would still not let me use them.
- draw back issues on the lock screen (5sec) and home screen wallpaper (10 sec) plus it auto reverted back to an older wall paper.
- when I connect it to my dock the lock screen does not auto rotate to landscape mode.
I have gone back to factory reset but issue number 2-3 still persist. Can any one help me either solve these issues or tell me the best way to downgrade to the 4.2 stock firmware.
MOEL C6833
current base band is 8974-AAAAANAZQ-10270025-26
KERNEL VERSION
3.4.0-PERF-G4F35567
[email protected]#1
TUE NOV 19 19:53:25 2013
BUILD NUMBER
14.2.A.0.290
Any help will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Do a repair via the Sony PC companion for windows or sony bridge for mac. It may help.
My issue is the dialer. If I answer or call someone, the screen goes black.
Sent from my C6833 using Tapatalk 4
Leechoonhwee said:
My issue is the dialer. If I answer or call someone, the screen goes black.
Sent from my C6833 using Tapatalk 4
Click to expand...
Click to collapse
Do you use front screen protector? maybe you need to replace it with the better one (clear) or use screen protector that has a hole to make the proximity sensor side not covered.
Leechoonhwee said:
My issue is the dialer. If I answer or call someone, the screen goes black.
Sent from my C6833 using Tapatalk 4
Click to expand...
Click to collapse
That happened to me too after updating to 4.3. A reboot fixed it temporarily, but i haven't had any issues after i did a full wipe.
ujan1 said:
Like most people I updated to the 4.3 and the new base band through the sony pc companion and everything was great for the first week, but then the red flags started to go off and here is the list:
- My games and apps that were working fine would not open even sonys stock apps. Tried re starting the phone and it would still not let me use them.
- draw back issues on the lock screen (5sec) and home screen wallpaper (10 sec) plus it auto reverted back to an older wall paper.
- when I connect it to my dock the lock screen does not auto rotate to landscape mode.
I have gone back to factory reset but issue number 2-3 still persist. Can any one help me either solve these issues or tell me the best way to downgrade to the 4.2 stock firmware.
MOEL C6833
current base band is 8974-AAAAANAZQ-10270025-26
KERNEL VERSION
3.4.0-PERF-G4F35567
[email protected]#1
TUE NOV 19 19:53:25 2013
BUILD NUMBER
14.2.A.0.290
Any help will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
- Bluetooh Share Force Closing when Bluetooth is turned off (Not always)
- Launcher redraw is a bit common with 4.3 but loading it back doesn't take too much time due to fast hardware so no big complaint
- Sketch and Note app should be able to be placed at landscape mode. But it's a minor issue.
- Superior Auto Mode.. Man, i do really wish that they just need to reduce the ISO and then voila the result will be a lot better! Tested in Manual Mode and it is confirmed that ISO bigger than 400 will destroy the picture quality, lot of smudges and artifact everywhere!
abuihsan said:
Do you use front screen protector? maybe you need to replace it with the better one (clear) or use screen protector that has a hole to make the proximity sensor side not covered.
Click to expand...
Click to collapse
No screen protector on at all.
LordManhattan said:
That happened to me too after updating to 4.3. A reboot fixed it temporarily, but i haven't had any issues after i did a full wipe.
Click to expand...
Click to collapse
Well. Will try that if it is possible
Hi, after upgrading to 4.3, here are some issues:
+ Device heating + battery super drain
after a lot of flashing and tweaking (not twerking), the current situation is:
+ Normal heat, battery still drain like hell, Android OS takes up to 70%
[S5+][6.0+][Apps&games] "finger down" is stuck when no finger touching the screen
I'm a (new) android developer using the engine Game Maker: Studio but I have general question.
When I test my game on galaxy S5(or higher models) and do a "palm-swipe" the mouse (=finger down) gets stuck.
Long story short - you can see that the black circle won't go with the touch coordinates (as determined by the small white circle - S5 integrated):
This occurs when a large skin touches the screen. The coordinates aren't retrieved back or lost AND the finger down is stuck - until screen is touched again.
I tested with a lot more games (non-Game maker made or Eclipse), some newer games didn't had any issues and some (older) ones did.
Oddly this bug won't happen with lower android versions - tested with:
(Bug occurs Yes/No):
- Galaxy S5 (Android 6.0.1 ) - Yes
- Galaxy S7 (6.0) - Yes
- Galaxy S2 (4.1.2) - No
- Moto E (2014) (5.1) - No
- Shield Tablet 1 (6.0.1) - No
- Tablet Galaxy tab 3 Lite (4.2.2) - No
I posted to many other (game maker forums) but no one had an answer and it was entirely new to them (my project/code was fine and I simply use finger down/up checks).
Anyone else can at least confirm this bug? Or maybe help me with a fix or a lead to somewhere...?
Here is my test apk so you can test:
ask for url.
Here's a link to my post:
ask for url.
Updates:
Still have this issue
No one out there experienced the same issue? Download some old games from the google play and you'll see (see the image above)
Hi all - I've installed the Ugoos AM2 ROM on my Minix U1 box:
Android 6.0.1 Firmware V1.1.1 for AM2 Android 6.0.1 Firmware V1.1.1 for AM2 440.33MiB 21/06/2017
at http://ugoos.net/downloads.
Everything is fine, except that I cannot use the power button on the A2 lite remote. It will start the box, but will not power down. I've read that this could be due to a limitation of android 6, but am not sure. And no matter what setting is entered in Settings->Display->Daydream, I cannot get the unit to fully power down - only sleep ( green light ). So far i have tried:
- changing "stay awake" to "off" in developer mode
- power key action to "shutdown" in display->daydream settings
- HDMI CEC setting = off
... but nothing works. And as mentioned, the A2Lite remote will turn the box on from a dead state, but the power key becomes unresponsive once the rom loads - tested with a keymap app and it wouldn't even register a keypress when I pressed the power button.
I think I found the answer here, but not sure how to enter the data:
https://kodi.wiki/view/MINIX_A2#keyboard.xml_per_Window_customization.2C_refining_remote_actions
#5
5 remote.conf example for amlogic boxes
/etc/amremote/remote.conf
Example settings needed to map the power button (note - this only applies once the device has booted, the initial power on detection appears to be in hardware)
....
factory_code = 0xfe010001
key_begin
0x18 116 # power
key_end
....
..
Very much appreciated - thanks!
A couple questions: 1) Do you get full 4K HDR res - either youtube or personal videos? 2) The power button thing is a mystery - I think the Kodi wiki nailed it when it mentioned that the remote activates the box from a dead state (hardware-based), but becomes unresponsive after boot-up. Any chance I could have a look at the remote.conf of your ROM and see if I can modify it to add functionality?
Also, what the heck happened to the forum - It's still an active company, no? I've been looking at the posts through search engine caching, but those are gradually disappearing ..