Forgive me for my newbie questions and the possibility that there is a condensed thread somewhere that gives me a step by step guide. I searched, but failed to find one...
I just bought this unit:
Pumpkin Quad Core 7-inch 1024*600 Digital Touchscreen Double Din UNIVERSAL Android 4.4 Head Unit Support GPS Navigation/Radio FM/AM/Bluetooth/Subwoofer/EQ/1080P Display/AUX/3G/WIFI/Reverse Camera/OBD2/Steering Wheel Control (Car Stereo with GPS)
After using it for a few weeks there are some REALLY annoying things bout it that need addressing.
BT music player is terrible. No track info and only basic navigation tools from on screen.
Radio screen is horrible too. The station name is tiny and the ability to store your favourite stations on the buttons you choose is missing.
Music player is nasty to look at, especially if you have 80Gb of tunes to plough through.
So, it looks like I need to change the software. But HOW? I need a simple step by guide to help me out. I don't want to brick the thing! Specs are:
UNIVERSAL head unit.
OS: Android 4.4 Kit Kat,
CPU: RK3188 Cortex A9 Quad Core,
RAM: DDR3 1GB Nand Memory: 16GB,
Screen Resolution: 1024*600,
Can someone help me please? :good:
Bricked it. Damn it all.
Sent from my SM-G928F using Tapatalk
I use Rocket Player on my phone (Galaxy S6) and on my Car Stereo (AN-21U). It's much better than the default player.
The FM tuner I have sucks. I can program the radio stations by holding down the preset that you want for a few seconds.
The catch is, timing the display correctly. If the station ID is being scrolled, it will store that, if it is the song title, it will store that. stupid!
I hate the scrolling radio station / Song ID.
Some stations (93.1 Jack FM, here in Los Angeles) , actually display both, in one line in white text below the scrolling text.
I don't know why they don't use that souce, or better yet, just display the station and song correctly.
RS-TLS said:
Forgive me for my newbie questions and the possibility that there is a condensed thread somewhere that gives me a step by step guide. I searched, but failed to find one...
I just bought this unit:
Pumpkin Quad Core 7-inch 1024*600 Digital Touchscreen Double Din UNIVERSAL Android 4.4 Head Unit Support GPS Navigation/Radio FM/AM/Bluetooth/Subwoofer/EQ/1080P Display/AUX/3G/WIFI/Reverse Camera/OBD2/Steering Wheel Control (Car Stereo with GPS)
After using it for a few weeks there are some REALLY annoying things bout it that need addressing.
BT music player is terrible. No track info and only basic navigation tools from on screen.
Radio screen is horrible too. The station name is tiny and the ability to store your favourite stations on the buttons you choose is missing.
Music player is nasty to look at, especially if you have 80Gb of tunes to plough through.
So, it looks like I need to change the software. But HOW? I need a simple step by guide to help me out. I don't want to brick the thing! Specs are:
UNIVERSAL head unit.
OS: Android 4.4 Kit Kat,
CPU: RK3188 Cortex A9 Quad Core,
RAM: DDR3 1GB Nand Memory: 16GB,
Screen Resolution: 1024*600,
Can someone help me please? :good:
Click to expand...
Click to collapse
Open Play Store ... download new music player? I use BlackPlayer in the car right now. The radio I stole from another ROM but it still sucks, just not as bad (rooted mine). Mine is the Lollipop version though, so dont know if my ROM would brick yours. In fact, the radio might be the same as the old 4.4 based unit!
RS-TLS said:
Bricked it. Damn it all.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Not all bricks are equal. Were you able to get to recovery before you bricked it? Can you now?
In the future, you need to remove the part that updates the recovery image before flashing so that it never overwrites your only means of fixing the problem Its also safer to take a factory image for your device and modify it than to trust some image made for some random unit.
Sent from my X200CA using Tapatalk
I was able to get to recovery before flashing bricked it. No, no way I tried could get it past the bootloader, and I tried every way known to this community.
"In the future, you need to remove the part that updates the recovery image before flashing so that it never overwrites your only means of fixing the problem". Hmm, was not aware of this, or how to actually make it happen...
" Its also safer to take a factory image for your device and modify it than to trust some image made for some random unit."
Sadly, my lack of skills in this area prevented that, which was why I used an image I thought was trusted and safe. Needless to say, I have not attempted to flash the replacement unit even though it has features that boil my piss each time I use it.
uudruid74 said:
Open Play Store ... download new music player? I use BlackPlayer in the car right now.
Click to expand...
Click to collapse
I just use Google Play Music now, but when I did try other players, BlackPlayer was by far my favorite
RS-TLS said:
I was able to get to recovery before flashing bricked it. No, no way I tried could get it past the bootloader, and I tried every way known to this community.
"In the future, you need to remove the part that updates the recovery image before flashing so that it never overwrites your only means of fixing the problem". Hmm, was not aware of this, or how to actually make it happen...
" Its also safer to take a factory image for your device and modify it than to trust some image made for some random unit."
Sadly, my lack of skills in this area prevented that, which was why I used an image I thought was trusted and safe. Needless to say, I have not attempted to flash the replacement unit even though it has features that boil my piss each time I use it.
Click to expand...
Click to collapse
The updates are in Rockchip update format. XDA has a tool floating around for Linux (imgrepackerrk) that can open the file. A tool for Windows is on the Rockchip website. Inside you'll see an update script. Note the lines I commented out:
# <C9><FD><BC><B6>recovery
#write_image PACKAGE:recovery RECOVERY:
#check_image PACKAGE:recovery RECOVERY:
# <C9><FD><BC><B6>system
write_image PACKAGE:system SYSTEM:
check_image PACKAGE:system SYSTEM:
# <C9><FD><BC><B6>backup
write_image PACKAGE:backup BACKUP:
check_image PACKAGE:backup BACKUP:
You'll also see a system.img, which is a raw ext4 file system image that is easily mountable on any Linux system. There are some Windows tools to deal with it too. You open the system.img, tinker, then repack it. You basically can't hurt the system if you only play with the system.img since you can always reflash the factory one. Everything else stays the same and recovery is never touched.
Hopefully this info will be useful to the next person [emoji2]
Sent from my X200CA using Tapatalk
You'd think I'd learn my lesson after the last ten head units I've purchased, but I saw the new Allwinner T8 headunits, and decided I wanted to give it a try. The new radio is currently on it's way from China, and I'll be updating this thread as I find out more information.
Update: Unit passed testing and has just shipped out. Should have it early next week if it doesn't get hung up in customs.
Update 2: Head unit arrived yesterday (11/28/2017), and I installed it today. Initial updates below.
[SIZE="+1"]PHOTOS[/SIZE]
{
"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"
}
View attachment 4331016
[SIZE="+2"]Umecity (Youmecity) Allwinner T8[/SIZE]
OS: Android 7.1.2 (Nougat)
CPU: Allwinner T8, 8-core Cortex-A7 @ 1.6GHz, up to 1.8GHz
Memory: 2GB DDR3 RAM, 32GB EMMC, 2xUSB2, 1 MicroSD
Graphics: PowerVR SGX544MP1 GPU (OpenGL ES1.1/2.0 OpenCL1.1)
Display: 9", 1024x600 capacitive
Radio Tuner: 7786
Amplifier: TDA7851
Output Power: 4x50w
Dimensions: 220mm x 130mm x 27mm
Weight: 5kg
MCU Version: 5.3.19-145-13-A46101-171118
System Vers: V9.2.2_20171117.102842_JP1-FD
Linux Kernel: 3.10.65
Security Patch Level: 2017-07-05, 7.1.2 (Nougat)
MCU Version: T5.3.19-145-10-C06101-170318
System Vers: V9.2.2_20170915.144527_JP1
[SIZE="+1"]Passwords[/SIZE]
Extra Settings: 123456
Developer and Reset: 7890
[SIZE="+2"]Identifying Firmwares[/SIZE]
[SIZE="+1"]General Information[/SIZE]
Example: 9.2.2_20171117.102842_JP1-FD
9.2.2 - The hardware version, and android version. For instance, 9 is T8, and 9.2.2 is Nougat.
20171117 - Release date of the firmware in YYYYMMDD format.
102842 - Possibly the build time for the firmware. Uncertain.
JP1: The manufacturer ID.
FD: ???
[SIZE="+1"]....by Version[/SIZE]
Per @bazanovv, "There are 3 different non-compatible versions of T3 hardware and software, Default one (sleep mode added later and not so good), New one (firmware is a development of R16 branch), and K2001 (usually very compact and cheaper). Allwinner T8 head units continue and develop the same firmware branch - V9.x.x on T8, V8.x.x on T3 New (V8.3.x with Android 7.1) and V7.x.x on R16. Most tips and tricks from T3 (new one) will work on T8."
R16 - 7.x.x
T3 - 8.x.x
T3 - 8.3.x - Android 7.1, Nougat
T8 - 9.1.1 - Android 6.0.1, Marshmallow
T8 - 9.2.2 - Android 7.1.2, Nougat
[SIZE="+1"]...by Manufacturer[/SIZE]
From information gleaned mostly from various threads over on 4PDA, it is advised to not install firmwares from another manufacturer, unless it has already been patched to be universal. Issues such as red messages at the bottom of the screen, or unsupported hardware can result.
JP1 or JP1-FD: Umecity
TW2-FD: TopWay
KED3-5: Kaier
[SIZE="+1"]Allwinner T8 Documentation[/SIZE]
www.allwinnertech.com/uploads/pdf/20160515151908f5.pdf
[SIZE="+1"]4PDA Discussion Thread (Russian)[/SIZE]
https://4pda.ru/forum/index.php?showtopic=875407
[SIZE="+1"]My Initial Feelings:[/SIZE]
This appears to be basically the same chassis as the Allwinner T3 units, but with a newer CPU and OS. Unfortunately, they cheaped out a little with the bezel on this one, which didn't include a MicroSD card slot like was on the previous model. This model has the same issue of accidentally clicking the capacitive bezel buttons that the T3 had.
The wiring is a bit of a mess. Some things were obviously just cheaped out on, like boost power for the antenna to the harness should come with connectors already installed. There is a brown/yellow wire pair coming from the CANBUS box that plugs into the back of the unit, rather than connecting via the main harness plug. Just as with the T3 model, the Volkswagen ISO1 harness has an ISO2 harness spliced into it. Having the extra connector leaves the system open to RF interference, and makes the wiring a mess.
After working with the unit for about an hour, and running the benchmarks, I started to notice some interference from the speakers. It wasn't affected by unit volume, and was present when muted. The noise sounded like either RF interference, or he noise you get when a capacitor is squealing. I did not notice the noise before the benchmarks, and need to see if this recurs on the next boot up. After extensive listening, the noise only seems to occur (for me) after the unit has been powered on for a while, and run hard. Benchmarking, initial setup and app download, etc. Once I reboot, I don't hear the noise anymore.
For scoring so blandly in the benchmarks, this unit is very responsive. I had no issues or slowdowns running multiple apps at the same time: Maps, Play Music, and Play Store downloading in the background, etc.
[SIZE="+1"]Some Items Worth Pointing Out[/SIZE]:
Bluetooth is for phone use only: I've always been critical of Bluetooth audio quality, especially for music. It's interesting that they point out that Bluetooth only works with one sound channel, so music will not sound good. They suggest music over USB. I'm guessing with android auto, or their EasyConnect mirroring.
[SIZE="+1"]Tests and Results[/SIZE]
Ease of install: Super easy to install, due to the extremely shallow depth of the device. Plenty of room for the wires behind the radio. Only annoyance was the combined ISO 1/2 adapter, which is just a mess.
Screen visibility: So far, so good. Less brightness, but better clarity than the Dasaita PX5 unit I have.
Deep Sleep: Well, no deep sleep support. Has a few shutdown times, maxing out at 30 minutes IIRC.
Boot time: So, the numbers quoted up top are pure fiction. Took ~40s from cold boot to launcher.
Backup cam start time: Excellent. Was able to use the backup camera immediately from power on.
Antutu Score: ~22500
3DMark Score: Benchmark crashed.
Volume scaling: Again, default audio is too freaking loud with my OEM Fender amp. Anything past 4-5 (out of thirty) is way too loud. On the good side, seems the Amp Volume can be adjusted. When set at it's lowest level, the scaling seems to be spot on for my Fender system. Nice!
Rootable?: CPU-Z seems to indicate that it is already rooted, however SuperSU states that the su binary is occupied. Need to explore further.
Play Store apps: So far, so good. Only missing items in the store were things like Google Dialer, which would have been nice to have.
Android Auto: Not available in Play Store. Likely need to fake 720p screen.
Google Maps: Works great. No problems in my short test drive.
Waze: Works great. No problems that I saw.
Voice Search: Not installed by default. Install "Google" from Play Store. Unfortunately, internal Mic couldn't hear my voice in testing.
Bluetooth Call w/int mic: No tested yet.
Radio Signal: Strong signal, and easily locked to even faint stations.
Radio Audio Quality: Meh, it's analog OTA, so it sounds about as good as I would expect it to.
CPU Temp: According to Aida64, the CPU temperature idled around 50-60 Celsius, spiking to 74 during the benchmarks.
GPS Lock: GPS locked almost immediately.
What else should I test?
[SIZE="+1"]Pros[/SIZE]:
Solid build, with shallow design.
Easy to install.
Google Maps works great, as does Waze.
[SIZE="+1"]Cons[/SIZE]:
Very easy to accidentally click the capacitive bezel buttons. Can sometimes even detect a hover as a touch.
Internal Microphone only works with Bluetooth calling.
keep us updated. I am looking to buy something similar myself but been confused between this and another one which has a rockchip 3188 and TDA7850. you think this one is better over the rockchip and TDA7850? both are by bonroad I think.
Assuming both have 2GB of memory, I honestly feel like it would be difficult for the average user to tell the difference between the PX3, PX5, T3, and (assuming similar performance) the T8. Well, outside of benchmarks, or games.
I'll be more interested in how it handles power management, and things like audio quality.
I'm impressed that it comes right out and says that Bluetooth music is crap. Saves me some testing.
If possible, please add CPU(SOC) temperature test with the hardware probe (or at least finger touch), because right now situation with CPU temperature is unclear, and software tools show only battery (?!) temperature. T3 was known to be quite hot and sometimes require a heatsink.
BTW, there are 3 different non-compatible versions of T3 hardware and software, Default one (sleep mode added later and not so good), New one (firmware is a development of R16 branch), and K2001 (usually very compact and cheaper). Allwinner T8 head units continue and develop the same firmware branch - V9.x.x on T8, V8.x.x on T3 New (V8.3.x with Android 7.1) and V7.x.x on R16. Most tips and tricks from T3 (new one) will work on T8.
Could you tell me how to root this Headunit? thanks
Updated the first post with my initial reactions to the head unit. I'll upload pictures to the thread later this evening. So far, it seems like a really nice unit, but with a few drawbacks.
Main complaints:
Electrical noise in speakers: Could be due to benchmark stresses. I will watch this and report back.
No deep sleep: Should be able to be fixed with software update.
Volume scaling: May be addressed via a control app, or software update.
Acidental "BACK" clicks: Back button is in a terrible place, and super sensitive. Need to map to long press.
Otherwise, it's a very nice head unit so far. More info as I have it.
bazanovv said:
If possible, please add CPU(SOC) temperature test with the hardware probe (or at least finger touch), because right now situation with CPU temperature is unclear, and software tools show only battery (?!) temperature. T3 was known to be quite hot and sometimes require a heatsink.
Click to expand...
Click to collapse
So, the unit seems to report temperature for the CPU, and the battery (makes no sense), which makes it a little easier. In my testing CPU was idling around 50C, and sitting between 65-75C during benchmarking, and stress testing. Now, to be fair, it's fairly cool here at the moment (50F/10C), so on a hot day, that could spike way up.
I myself own one of these t8 units. Mines from pumpkin and at the start I originally thought it was a PX5.
It blows my old rk3188 out of the water when it comes to performance the only downside is the lack of android support
bazanovv said:
If possible, please add CPU(SOC) temperature test with the hardware probe (or at least finger touch), because right now situation with CPU temperature is unclear, and software tools show only battery (?!) temperature. T3 was known to be quite hot and sometimes require a heatsink.
BTW, there are 3 different non-compatible versions of T3 hardware and software, Default one (sleep mode added later and not so good), New one (firmware is a development of R16 branch), and K2001 (usually very compact and cheaper). Allwinner T8 head units continue and develop the same firmware branch - V9.x.x on T8, V8.x.x on T3 New (V8.3.x with Android 7.1) and V7.x.x on R16. Most tips and tricks from T3 (new one) will work on T8.
Click to expand...
Click to collapse
hal752 said:
I myself own one of these t8 units. Mines from pumpkin and at the start I originally thought it was a PX5.
It blows my old rk3188 out of the water when it comes to performance the only downside is the lack of android support
Click to expand...
Click to collapse
What Android support is it missing? Do you mean as far as updates? Definitely not updated as often as the Dasaita PX5 systems, but that is actually kinda a blessing to be honest. I found that I would get the system where I wanted it, and it would be time to update, and I'd be back spending an hour in my car fussing with my radio. That said, previous models (R16, T3) have had a fair number of OS updates.
I'll honestly be happy if I can get this system to the point where I can "set it and forget it". So far it looks promising.
I fixed the volume scaling problem, and the fix persists through reboots. Not sure exactly which fix worked, so I'll need to reset it and isolate which tweak fixed things. I think my signal noise is from a power line sitting too close to a speaker wire somewhere in the harness. I'll pull the unit and redo the wiring this weekend, which should hopefully fix the noise issue.
Need to figure out how to remap the back button. The panel tool is fairly opaque. Any tips are appreciated!
Rottgrub said:
Need to figure out how to remap the back button.
Click to expand...
Click to collapse
Do manual from T3 version work? I can't check, if this manual actually works, because I don't have this HU.
Settings-Car settings-Extra settings-Touch area keys
In POSITION menu select place (LEFT, RIGHT, TOP, BOTTOM), where sensor buttons are located;
Continue setting like on this video.
Af far as I understand, at first click Clear in the bottom right corner, then click Set in bottom left corner. Select any free cell starting from top left, select key function, press sensor key - stored cell should change it's color. Continue, until all sensor keys set. Click Set in bottom left corner again. Check, if buttons working; if not - set them again. Use USB mouse (right mouse button = back) if something goes wrong.
bazanovv said:
Do manual from T3 version work? I can't check, if this manual actually works, because I don't have this HU.
Settings-Car settings-Extra settings-Touch area keys
In POSITION menu select place (LEFT, RIGHT, TOP, BOTTOM), where sensor buttons are located;
Continue setting like on this video.
Af far as I understand, at first click Clear in the bottom right corner, then click Set in bottom left corner. Select any free cell starting from top left, select key function, press sensor key - stored cell should change it's color. Continue, until all sensor keys set. Click Set in bottom left corner again. Check, if buttons working; if not - set them again. Use USB mouse (right mouse button = back) if something goes wrong.
Click to expand...
Click to collapse
I actually read these, and watched the video before trying last time, but no luck. I think the new panel/button mapping tool may work a little differently (or maybe I just don't get it, which is possible). Start and Clear worked as expected, but when selecting a cell, I didn't get any popup windows asking for short/long press, and no list of actions. If I clicked the button I wanted to map, it would assign the button as expected, but only to the function that was already listed in the cell. I had no way of mapping a long press action that I could find. I'll keep playing with it, and report back if I have any more luck.
Rottgrub said:
I'll keep playing with it, and report back if I have any more luck.
Click to expand...
Click to collapse
Ok, have a good luck! As far as I understand, it is very important to select correct buttons block side location on the first step, before menu with the cells appear.
bazanovv said:
Ok, have a good luck! As far as I understand, it is very important to select correct buttons block side location on the first step, before menu with the cells appear.
Click to expand...
Click to collapse
You are exactly correct. Thank you for the help! I just tried again, and was able to properly map my panel buttons. The trick is to select to primary action you want first if it's already present in a cell. If not, select "Reserved" and a menu will appear to select the primary action. Once that is selected, choose the hardware key to map. Then long press the cell to choose a new "Press", "Long Press", or "Very Long Press" action.
Unfortunately, there is no NULL action that I could find to leave the primary action unmapped, while letting me map a long press. I settled for mapping the primary action to "Mute" for the HOME and BACK buttons. That way I don't lose my application if I touch something near the bottom of the screen.
Youmecity 10 Inch Universal 2 din Android 7.1
Hello
I also bought a T8 unit and I think it is a product conforming to this thread.
But google voice input can not be used(bt hands free call is ok).
I could use it on dasaita PX5 and I have average knowledge of android.
If you have a special trick to use voice input please tell me.
warata said:
Hello
I also bought a T8 unit and I think it is a product conforming to this thread.
But google voice input can not be used(bt hands free call is ok).
I could use it on dasaita PX5 and I have average knowledge of android.
If you have a special trick to use voice input please tell me.
Click to expand...
Click to collapse
If you simply can't activate the "voice control" icons, you probably need to install the "Google" package from the play store. This isn't included with the base firmware, at least on my unit. Issue I'm having is that Voice Search isn't hearing my voice, which may just be a permission issue, addressable in Setting/Apps/Google/Permissions. I need to dig into it more.
Let us know if that helps, and if you get it working, what you did. =) Good luck!
Rottgrub said:
Let us know if that helps, and if you get it working, what you did. =) Good luck!
Click to expand...
Click to collapse
Thanks for your specific answer.I think that my question was not have enough information.
I have installed Google Apps and I giving him all authority given to him.
But he does not listen to anything.It does not react at all even if it repels parts of the physical microphone with fingers.
If it is not possible to use the telephone, I assume that the microphone is defective
and I will return it, but since the hands-free can be used, the microphone is not disconnected.
But car android is generally useless unless you can use Voice input.
Whether it can be settled by setting or not, I have to conclude within a few days whether the unit is defective.
Installing Google App was necessary even on PX5, but it was not particularly difficult.
So I wanted to know if there are any special settings in T8.
Thanks
As in XDA support. None of the custom ROMs work with my device. In regards to updates it's from pumpkin and there has being no news on a update for my device.
Mine was pretty much plug in and play. Apart from removing a few "Chinese" APKs and installing viper. The only issue I have had is that I can't for the life of me connect my obdeleven OBD2 device.
Even my microphone works although could be better. I'm able to send text messages using android auto and head unit reloaded without much error.
warata said:
But car android is generally useless unless you can use Voice input.
Whether it can be settled by setting or not, I have to conclude within a few days whether the unit is defective.
Click to expand...
Click to collapse
Okay, so yeah. Sounds like you are having the same issue I'm having. I agree that it's not a hardware problem. Just to verify, are you using the internal, or external mic? I'm using the internal one only.
I haven't put much time into playing with it yet, but I'll let you know if I can figure out how to get it working.
hal752 said:
As in XDA support. None of the custom ROMs work with my device. In regards to updates it's from pumpkin and there has being no news on a update for my device.
Mine was pretty much plug in and play. Apart from removing a few "Chinese" APKs and installing viper. The only issue I have had is that I can't for the life of me connect my obdeleven OBD2 device.
Even my microphone works although could be better. I'm able to send text messages using android auto and head unit reloaded without much error.
Click to expand...
Click to collapse
What system and MCU version is your system running? If I hang onto this unit, I will be looking into making a custom ROM for it. (No promises)
Rottgrub said:
Okay, so yeah. Sounds like you are having the same issue I'm having. I agree that it's not a hardware problem. Just to verify, are you using the internal, or external mic? I'm using the internal one only.
I haven't put much time into playing with it yet, but I'll let you know if I can figure out how to get it working.
Click to expand...
Click to collapse
Do you have same issue??I thought that It was almost defective...
I tried an external microphone, but It didn't work my own dynamic microphone.
I think that this product uses a condenser microphone.
I ordered the corresponding microphone with aliexpress, but it will be two weeks after arrival.