Related
I have the Nexus 4 and I'm getting a really annoying error. I had the latest pre-KitKat stock ROM on it yesterday. I received the KitKat OTA update and proceeded to install it. It installed fine and went through the application optimisation steps and once it did it's final reboot it came up with an "Unfortunately, the process android.process.acore has stopped". I've got options to Report or click Ok. Clicking Ok will just bring the message back often immediately but sometimes with a few seconds gap. I could interact with the UI between dialogs but literally have split seconds so made navigation extremely slow (i.e. takes a dozen attempts sometimes to click on something behind the dialog).
I've tried a full factory resetting from the phone menu and from the recovery menu, both have done nothing. The phone continues to display the error as soon as the phone boots up after the reset (i.e. before I even go through the phone setup).
I've managed to Report the issue and Preview the details which reveal the following:
Report type: Crash
Package name: com.android.providers.userdictionary
Package version: 19
Package version name: 4.4-920375
Installed by: com.google.android.gms
Process name: android.process.acore
System app: true
Device: mako
Build Id: KRT16S
Build type: user
Build fingerprint: google/occam/mako:4.4/KRT16S/920375:user/release-keys
Product: occam
SDK version: 19
Release: 4.4
Incremental version: 920375
Codename: REL
Board: MAKO
Brand: google
Exception class name: java.lang.ClassNotFoundException
Source file: BaseDexClassLoader.java
Source class: dalvik.system.BaseDexClassLoader
Source method: findClass
Line number: 56
I've also tried google searching, various other people have had the same issue but what they did to resolve it hasn't worked for me.
Does anyone know what I can do for this?
I'm going to try the full stock binary image from Google's website (https://developers.google.com/android/nexus/images#razorkrt16s). Surely this must resolve the issue.
Techno79 said:
I'm going to try the full stock binary image from Google's website (https://developers.google.com/android/nexus/images#razorkrt16s). Surely this must resolve the issue.
Click to expand...
Click to collapse
And it did indeed solve it.
Please note that I gave up on this unit (MTCD PX5 units are so much nicer...). I will try to update this post (however infrequently) with information that may appear in this thread or come my way by other means, but I will not seek information actively and updates will no longer be from my own experience or experiments.
At the time of writing this head unit is available here and (probably) here. These are both custom fit for Kia Sorento, but other versions do exist; in particular several EONON units feature the same hardware configuration (model numbers GA2160, GA7153 GA7163, and I am sure others).
Hardware-wise this seems to be the same unit as described in this thread so many tricks therein will work for this unit. In particular the USB debugging password continues to be "[email protected]" (without quotes); the extra settings password is most likely either 123456 or 668811; the factory reset and developer options passwords appear to be both 7890.
In all the unit is an Allwinner quad core R16, with the MCU version 5.3.19-16-10-650101-161115 and System version V7.3.1-2016-11-12.100233_TW2. Here is the Droid Info report:
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20161112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20161112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 986 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
Software-wise the unit comes with a fairly stock version of Marshmallow, though as usual the operating system is a bit locked down (but to my surprise not too locked down) compared to stock.
The purpose of this thread is to gather information about the software and possible customization for these units. I have added the information I gathered from my experience and I will update this post with any new information I manage to obtain.
1. Partition dump
For reference I dumped all the partitions of my device. The dump is available here. The dump was done by name (for those partitions that have a name) and symlinks point to the device name from /dev/block. Feel free to share (credit appreciated but not necessary) and please share any information that you gather from it (which will be included in this section as it becomes available).
2. Flashing firmware
There are multiple ways of flashing new firmware, depending on the actual unit and also its state (working, bootloop, etc.). All methods require that the all the files (three to six) that contain said firmware (see next section) be placed in the root of a SD card formatted FAT32 and inserted in the GPS slot of the unit. Some reports of the firmware being flashed from a USB stick rather than the SD card also exist; they also mention that choosing one USB port over another might make the difference between success and failure.
On a working system inserting the card and/or USB stick and choosing "update system" from preferences will likely do the trick.
On a system that is not working the following methods have been reported:
Hold Home, press Reset, and keep holding Home until the update starts (thanks).
A hardware solution is to short Key 1 (steering wheel controls) to ground, then press and hold Reset for 10 seconds; release Reset and disconnect Key 1 when "update" is displayed (thanks).
Yet another procedure might be needed for some units (thanks): Using a USB stick prepared as above and inserted in the unit, turn ignition to ACC, press Reset, turn ignition off, then after 5 seconds turn it again to ACC. A video is also available.
3. Flashable firmware
All the reports I have seen indicate that all the firmware versions are interchangeable. However, a factory reset will be needed most of the time for full functionality, especially so when installing firmware from a different vendor. It is VERY important however to note that the file bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 contains the MCU firmware and so SHOULD NOT be flashed on incompatible devices as doing so will brick the unit (thanks).
Partition 11 of the above dump in particular stores a flashable image. It contains the following files:
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
The files 827ba428-9b57-11e6-8dfb-37398ea70e52.* in particular when cat-ed together form an ext4 file system that appear to be a copy of the system partition. This 4pda forum thread contain more information (thanks @Ahfish22); I do not speak Russian at all but Google Translate does a good job most of the time.
Since I started this thread many people have posted many firmware versions. Here is a hopefully complete list. There might be duplicates and misses and I apologize for both in advance.
The following set of firmware (in particular V7.3.1_20170610.110122_KED1 therein) come recommended by several users (thanks).
EONON firmware:
GA2162_KBT2_20170309 (thanks)
V7.3.1_20170114.111256_KBT2 (thanks)
EONON-R16-20170509 (thanks)
EONON-R16-KLD20170515
V7.3.1_20170427.104257_KBT2 (thanks)
EONON-R16-KLD20170515 (thanks)
KED1 (MEDEKE?) firmware (thanks):
V7.3.1_20170216.180104_KED1
V7.3.1_20170720.152039_KED1
TW2 (TopWinner?) firmware (thanks):
V7.3.1_20170111.114952_TW2-IVT+ROOT+RADIO
V7.3.1_20161229.175327_TW2
V7.3.1_20161201.154419_TW2
TH6 firmware (thanks): V7.3.1_20161129.194710_TH6
JYZC1 (Joying?) firmware (thanks):V7.3.1_20170317.114203_JYZC1
Kaier firmware (thanks)
Rooted KLD (Klyde) firmware (thanks):V7.3.1_20170512.203736_KLD1-0-1-mod
4. Recovery
Mot units do have a working recovery partition, though some are reported not to have such. The command "reboot recovery" at a root prompt (terminal emulator or ADB) will enter recovery (if available).
Alternatively recovery can be reached with an external USB keyboard as follows: While holding Alt and Print Screen keep tapping i; the system will eventually restart in recovery (thanks pir8man) .
It should be noted that despite the on-screen instructions the stock recovery does not react to any buttons on the head unit, but works well with an external USB keyboard.
5. Customization
There are useful tweaks that come with the stock operating system including speed-dependent volume and (apparently, I have not tested exhaustively) the elimination of the full-screen keyboard.
I found this alternative to the stock radio app (context, source code) which is pretty nice except that the app force closes upon attempting to enter settings. If you speak Russian it may be worth discussing this with the developer.
Root: Kingoroot works, though several attempts (reboot and try again) may be needed. Note that a reliable Internet connection is needed during the whole process. I do not like the extra apps and intrusive ads that come with Kingoroot. I therefore recommend once rooted to install Chainfire's SUperSU, let it update the su binary, and then uninstall Kingoroot. Note however that the current Play Store SuperSU (namely, version 2.82) may not be able to overwrite Kingoroot's su (saying instead that "the su binary is occupied"). If this is the case you may want to try version 2.79 (downloadable from here) which is known to work. Once the Kingoroot's su binary is overwritten you can upgrade to the latest (Play Store) SuperSU.
Busybox: Installed without incidents using the usual installer from the Play Store.
Xposed: Installed using the Xposed installer v. 3.1.1 and works well. I tried Gravity Box and Xprivacy.
6. Outstanding issues
It should be possible to redefine the default apps for music, video, and radio but I did not find any way to do it.
Mapping SWC and front button panel events works to some degree (for testing purposes I mapped the "Band" button to the app drawer), but this seems to be exclusively at the mercy of the MCU, which only allows mapping to predefined actions. I could find no way to map these events to custom actions on the OS side. It was reported that button events are communicated to the OS as long as no MCU app is running. However, I was unable to reproduce this; for me no event is ever seen by the OS no matter how many (or how few) apps are running. I stopped all the MCU apps but even so KeyTest does not register any event.
Needless to say, no custom recovery (such as TWRP) exist for these units.
So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?
Can you share me the content of /sbin directory?
sambacha said:
So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?
Click to expand...
Click to collapse
If the hardware matches then I do not see why not. In addition to dd-ing the system and boot partitions of my dump (which you are welcome to try) please see my last edits of the first post for possible flashable firmware being available.
Just make sure that you have a (tested) way to get back if things do not work...
mrtnb said:
Can you share me the content of /sbin directory?
Click to expand...
Click to collapse
See attached.
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Alternative to the stock radio -- help needed
I found this alternative radio app (reference, source code). It works well but I am unable to set preferences as the app force closes on selecting the setting menu item.
I would ask the developer, except that I do not speak Russian. I was wondering if any Russian speaker around here could inquire about the issue. I have also downloaded the sources and I am poking around but I am not holding my breath until I find a solution (I am a coder but not an Android developer). Many thanks in advance!
sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you share your experience and the russian thread's link?
sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you give us a link?
---------- Post added at 07:40 AM ---------- Previous post was at 07:21 AM ----------
can I flash this over Android 4.4?
This is my unit:
Android 4.4.2 Operation System
CPU Processor: Allwinner R16 Cortex A9 Quad-core 1.6GHz
RAM Memory: Samsung DDR3 1GB/16GB
I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.
sbruda said:
[*]It would be great if long press events (SWC and/or front panel buttons) can be used. Some hints in various threads suggest that this is possible with these units but I found no way to do it. Advice is once more much appreciated.
Click to expand...
Click to collapse
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
If I get something new I'll post asap.
Hope this helps.
pir8man said:
I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.
Click to expand...
Click to collapse
could you please upload this rom for us
thanks man
me sumo al pedido
Saludos !
no se si alguien puede pero estaría bueno que puedan subir los packs de actualización. para R16 en la resolucion 1024*600
por ejemplo estos son los Nombres de los archivos que hacen falta...
tambien especificar el android si es 4.4 o 5.1 o 6.0
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
90436790-1e25-11e5-9b35-000c29ba27c0
91973a18-1e25-11e5-b937-000c29ba27c0
92e82e86-1e25-11e5-bffa-000c29ba27c0
khalwd said:
could you please upload this rom for us
thanks man
Click to expand...
Click to collapse
Hi,
(my first post):laugh:
I would also like to have a copy of this ROM.
I have the same Droid report.
Being someone that cant leave things alone i have somehow corrupted my unit.
I rooted with Kingoroot and all worked well. Uploaded a recovery to the cloud, all good.
Decided to down load back to the unit. Wife moves car and interrupts download.
Now when i boot up all i get is the car logo and the android screen, this is where it stops.
Tried installing various updates, They seem to install. Progress bar for abut 5 min shows update end
then boots to the car logo Android screen and stops.
Cheers
Hi,
pirulazul said:
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
Click to expand...
Click to collapse
Thank you for the report. I tried the same (stop all system apps) but even so KeyTest does not register any event. This was done for the panel buttons since I do not have yet any SWC (the unit is on the bench), which may or may not be the cause of my failure.
pirulazul said:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
Click to expand...
Click to collapse
Have you found any way to replace the default association for these apps? By default the "Mode" action cycles through the default apps, did you find any way to convince this action to cycle through some other (custom) rotation?
pirulazul said:
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
Click to expand...
Click to collapse
I'll try to look into this, but at this time I cannot promise any timeline.
Cheers!
would one of my units be similar to yours?
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...
zerozoneice said:
would one of my units be similar to yours?
Click to expand...
Click to collapse
Looks pretty much the same as mine (with a slightly newer firmware though).
zerozoneice said:
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...
Click to expand...
Click to collapse
Most (all?) Chinese vendors know absolutely nothing about the units they sell so it is quite possible to have the wrong firmware. This, or the file got corrupted during transfer somehow. Have you tried my firmware blob or the others that float around? The probability that it will work look decent and what have you gotta loose?
You can also try to restore the resolution by trial and error (touching the screen where things should be). A couple of success stories have been posted in this thread though the process looks painful...
there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Trial & error...i would need to see another menu next to me in order to see where the hell i'm pressing on my screen
Resolution change is the first menu, but is hidden in the extra settings, behind a password which i'd also need to enter....blindly.
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
LE: LOL, i just read the following passage from the thread you posted above:
"What is the Extra Settings password?
Resolved: 123456
Note: Do NOT change the resolution of the head unit. You will destroy your unit. However it is reversible."
Post 807: another quickfinger like me, changed the res. the other way around, from 800 to 1200, but he still sees something....
https://forum.xda-developers.com/showpost.php?p=70762889&postcount=807
Post 747: same problem as me.
https://forum.xda-developers.com/showpost.php?p=70047172&postcount=747
How can i flash this damn unit? How can we connect to it?
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly... THX!
---------- Post added at 04:43 PM ---------- Previous post was at 04:15 PM ----------
HERE is the link to the FW that infidini support provided me.
zerozoneice said:
there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
Click to expand...
Click to collapse
I believe that the four files can be used directly to upgrade, at least this is what people have reported (I have never tried to upgrade myself). This also makes sense given that a restore to factory from the (Android) menu will presumably use the partition with those files.
zerozoneice said:
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Click to expand...
Click to collapse
It would appear that TV out only works for the DVD.
zerozoneice said:
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
Click to expand...
Click to collapse
No, I meant to but I am really pressed for time nowadays so I have no idea when will I get to it.
zerozoneice said:
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly...
Click to expand...
Click to collapse
Here they are. Sorry for the crappy photos but I have no idea how to take screenshots on this unit (please advise):
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.
sbruda said:
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.
Click to expand...
Click to collapse
thx, they're good enough. using phone is fine. afaik password for that extras in my case is 123456 and restore to factory settings 7890
i will try tomorrow.
---------- Post added at 07:32 PM ---------- Previous post was at 07:01 PM ----------
How do you power on the thing when not connected in the car???
[Nougat 7.1.2 Alpha] [LVM] AOKP Unofficial - 22nd May, 2017 - LVM
Okay People, Here is #Android #7.1.2 #Nougat on #Oppo #Find5
Built from the latest AOKP Nougat sources.
Works:
- Network
- Camera
- BT Also works. Takes sometime during voice call connection but that optimization is gonna come in the next build.
- Everything else - Same status as my PACRom 6.
This ROM is STABLE. Bluetooth A2DP/HFP/HFS works as tested. No random reboots & resets.
DO NOT ASK FOR ETAs. I do this in my spare time. You are welcome to help.
Put your comments and test results in the thread below.
And SPREAD THE WORD!
Updates coming smooth :angel:. Next build will target optimizations & speed (though it is very speedy compared to other ROMS).
Follow me on Twitter @wolverine2k and Click thanks if you like my work
XDA:DevDB Information
AOKP #Oppo #Find5 7.1.2 #Nougat, ROM for the Oppo Find 5
Contributors
wolverine2k, wolverine2k
Source Code: https://github.com/wolverine2k/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Oppo Find5 BraveHeart
Based On: AOKP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-01-20
Current Beta Version: 1
Beta Release Date: 2017-01-19
Created 2017-01-20
Last Updated 2017-05-22
Reserved
Downloads
STABLE: 22nd May, 2017:
- Download: AOKP 7.1.2 - 22nd May, 2017
- MD5: 5c3961480f201e74b5ef171172f91bcc
Incremental Fixes in this build from the previous builds:
- Updated to 7.1.2.
- All bugs from previous builds are still valid (+ new bugs might have been introduced).
**********************************************************************************
STABLE: 26th January, 2017:
- Download: AOKP 7.1.1 - 26th January, 2017
- MD5: 35b4e6b287bcb4e785b908711bba1798
Incremental Fixes in this build from the previous builds:
- DisplaySettings & LiveDisplay working.
- BT Address does not randomize anymore.
- BT DUN profile enabled, so dial-up networking should work with BT.
- BT SAP profile enabled, so your car should be able to use the handset's SIM for a true hands-free operation.
NOT WORKING:
- Sound Recorder does not crash but no sound is heard after recording i.e. input device is still blocked
- Navigation buttons are not lit up
**********************************************************************************
STABLE: 25th January, 2017:
- Download: AOKP 7.1.1 - 25th January, 2017
- MD5: 21ed412db6448aec1815cb639f4e877f
Fixed in this build:
- SD Card corrupt message.
- Camping on 2G.
- Video Recording with Camera.
NOT WORKING:
- Sound Recorder does not crash but no sound is heard after recording i.e. input device is still blocked
- Display settings are still crashing
- BT still keeps losing paired device list
- Navigation buttons are not lit up
**********************************************************************************
Second Version: STABLE:
- 20th January, 2017: AOKP 7.1.1 - Same status as my PACRom 6
MD5:e896acaa73c4cfbec1bf37798ca4e72c
- Some bugs but is usable
**********************************************************************************
First Version: Alpha:
- 19th January, 2017: AOKP 7.1.1 Alpha No Sound
MD5: b470f68df8e4a228ec1124ce0262ce5d
Reserved
Installation Instructions:
1. Make sure your phone is charged above 50% or connect it to a power source.
2. Backup EVERYTHING to your PC, all phone storage will be formatted.
3. Download and install the modified LVM capable recovery by Wuxianlin with fastboot or any tool that you like (fastboot command: "fastboot flash recovery find5-twrp-recovery-2.8.6.0-en-lvm.img")
4. Full wipe. Wipe Dalvik cache, system, data, cache, android secure.
6. From the TWRP main screen, go to: Advanced => LVM Partition => Click Merge Partition => Swipe to switch partition. (WARNING! This will completely wipe your phone's data partitions, there is no way back)
7. Install the ROM
8. Reboot
Very IMPORTANT: Go and drink Coffee or Tea or Beer. Takes almost 10 minutes for the first boot to happen.
Enjoy 7.1.1 on Oppo Find 5 with LVM.
Report your experiences/problems/tips etc. here
Everything works in the 2nd build. The status has been upgraded to Stable. I have been using the ROM now for 12 hours and no random crashes or reboots noticed.
Please put in your comments about things you like and dislike in this ROM. Your test reviews would be amazing help. And spread the word!
Reviews and votes on the thread also helps.
Cheers(Y)
Thanks Wolverine2k, this is great news! Gonna try to find time this weekend to flash it.
Forgot to ask, I assume GApps are still required (e.g. the nano 7.1 variant)?
Yes gapps are required. Use open gapps and tem us the result
Dunno if its only for me, but I'm having problems with snapchat. I cannot connect to my account it says "there was a problem connecting to the server. Please Try again. " This didn't happen with other roms, but when I tried earlier pacrom version, I had the same issue.
Microphone in apps not works (recorder, google now, etc). Bluetooth MAC changes after reboot.
Takes almost 10 minutes for the first boot to happen
Click to expand...
Click to collapse
It's been over 30 minutes and still booting - is this normal?!
---------- Post added at 11:56 PM ---------- Previous post was at 10:58 PM ----------
Mateus109 said:
It's been over 30 minutes and still booting - is this normal?!
Click to expand...
Click to collapse
OK so I finally got an encryption error message and was forced to reboot. After that the phone booted fine.
wolverine2k said:
Yes gapps are required. Use open gapps and tem us the result
Click to expand...
Click to collapse
Is it possible to fix MAC bluetooth? Maybe I need to make the some changes in NVRAM?
Very fast and responsive (phone's never every booted this quick!). Definitely suitable for daily use. Bluetooth seems to work for music but not tried it to make a phone call yet. Generally the ROM is awesome!
However there are a few niggles, but I realise this ROM is still work in progress...
- Navigation buttons are not lit up
- Mic not working in apps other than dialler
- Video recorder does not record (maybe due to mic error)
- Accessing display settings crashes Settings app
- "SD card corrupt" error message (but this was easily fixed with the cm-13.0-find5-lvm-patch.zip patch)
- No live display/night mode blue tint function?
Thanks for your hard work!
Issues with camera. Won't record videos using camera app. Phone reboots when recording with instagram.
Also wi-fi hotspot doesn't seem to work either.
@wolverine2k Thank you so much for putting out a new update! Gonna try the new build soon.
Currently i need mic daily, btw. your previous rom is still running perfectly!
Thanks for the status and your comments. In wil start tackling then one by one. Be patient, I will try to fix al the problems but might take time.
Live Display has suddenly started working! Odd, but pleased to have this feature back.
Mateus109 said:
Live Display has suddenly started working! Odd, but pleased to have this feature back.
Click to expand...
Click to collapse
Now that is strange! Did you do anything special?
I will release a new build possibly today fixing:
1. "SD card corrupt" error message (but this was easily fixed with the cm-13.0-find5-lvm-patch.zip patch)
2. 2G camping (I forgot to get this one from PacROM to AOKP)
3. Disable ppd service restarts (as it keeps crashing hence slowing down the phone)
25th January build. Look at 2nd post for downloading links.
Fixes:
- SD Card corrupt message.
- Camping on 2G.
- Video Recording with Camera.
NOT WORKING:
- Sound Recorder does not crash but no sound is heard after recording i.e. input device is still blocked
- Display settings are still crashing
- BT still keeps losing paired device list
- Navigation buttons are not lit up
Thanks wolverine2k. I assume we're OK to dirty flash this update?
(Regarding LiveDisplay, I noticed it stopped working the other evening but after a reboot it started working again fine, so something must cause the service to crash.)
Mateus109 said:
Thanks wolverine2k. I assume we're OK to dirty flash this update?
(Regarding LiveDisplay, I noticed it stopped working the other evening but after a reboot it started working again fine, so something must cause the service to crash.)
Click to expand...
Click to collapse
I suggest a clean install. I have found the reason for LiveDisplay & DisplaySettings to not work. Have fixed it in my next build. Now am trying to see if I can fix my bt address which between is generated on every reboot and stored in /etc/bluetooth/bt_config.conf. One dirty quick fix would be to have a separate script that launches on boot, checks if the config exists and then overwrite the file if a different one exists. That is not a good approach though so will only take that path if the others fail.
Hello,
I have a problem with Samsung SM-G355h.
When I enter in settings/storage or in any application details, system can't calculate how much storage that application occupies or any oder memory space beside available space (there's just calculate... where space amount should be). Besides that I can install apps but can't uninstall them (uninstalling is working but never finishes), there is no error massages. After a while phone just restarts.
I tried following things:
- wipe data and cash, reset to factory settings;
- I used Odin to install newer and older firmware (official);
but it is always the same.
Phone isn't rooted and has no custom rom in it.
If someone has idea what I can do more, his suggestion will be most welcome.
Phone software specifications:
Android version: 4.4.2
Baseband version: G355HXXU0AOB3
Kernel version: 3.10.17-5115844 [email protected] #2 Thu Jan 5 21:10:36 KST 2017
Build number: KOT49H.G355HXXS0AQA4
Security software version: ASKS v1.2_161011
Thank you for your attention
mladja27 said:
Hello,
I have a problem with Samsung SM-G355h.
When I enter in settings/storage or in any application details, system can't calculate how much storage that application occupies or any oder memory space beside available space (there's just calculate... where space amount should be). Besides that I can install apps but can't uninstall them (uninstalling is working but never finishes), there is no error massages. After a while phone just restarts.
I tried following things:
- wipe data and cash, reset to factory settings;
- I used Odin to install newer and older firmware (official);
but it is always the same.
Phone isn't rooted and has no custom rom in it.
If someone has idea what I can do more, his suggestion will be most welcome.
Phone software specifications:
Android version: 4.4.2
Baseband version: G355HXXU0AOB3
Kernel version: 3.10.17-5115844 [email protected] #2 Thu Jan 5 21:10:36 KST 2017
Build number: KOT49H.G355HXXS0AQA4
Security software version: ASKS v1.2_161011
Thank you for your attention
Click to expand...
Click to collapse
Go to recovery and try to clear cache
HI Guys,
Im a newbie here. Posted about a month ago but no reply.
I wish I had found the threads and reviews about the seller before I purchased. Most un helpful
I have a few issues i will list. The last discussion with the seller was about updating firmware. He tells me there is an update but After several weeks of messaging him i have had no reply. I am now discussing with PAYPAL.
http://www.autostereo.com.cn
https://www.aliexpress.com/item/32965483853.html
https://www.ebay.co.uk/itm/283835207820
QUITE FRANKLY. The user interface is very basic and ugly. So looking for assistance to do something.
Wanting to know if the HU is able to be update on firmware or Rooted o think you call it. If so will need instruction, and I am happy to pay someone for this. PAYPAL or Bank Transfer.
OK so issues.
HU
MAIN ISSUE is SOMETIME Screen will Flash a line from top to bottom
1. ECU SPEED AND REVS.. NOT WORKING
( ECU CABLE IS CONNECTED) I
2. ANDROID AUTO… INTERMITTENT. TURNS ON OFF ON OFF ON OFF..
.......FIXED......
3. EASY CONNECT… INTERMITTENT TURNS ON OFF ON OFF ON OFF
FIXED
4. Phone connection AUDIO QUALITY IS TERRIBLE,, SO BAD I cannot hear caller.
In the package, there is the miccorphone, did you connect this?
FIXED
5. DOOR OPEN Shows Wrong side If Car door is open on Left Screen shows on right.
Setting-----user setting----right side
THIS IS FIXED
6. Need to be able to change the Startup Screen (Yellow Car) UGLY. Also Car that show up in PNG file.
CAN ONLY CHANGE BOIT LOGO TO MONDEO OR YELLOW SPORTS CAR
NO OPTION TO USE MY OWN LOGO
Some of these things are nothing major but for what i paid I expect it to work as it should.
Detail are
https://www.aliexpress.com/item/32965483853.html
4gb/64gb 13.6 Android9 13.6" Tesla style Car No DVD Player GPS Navigation For Ford Mondeo Fusion MK5 2017
Android Version 9
Security Patch April 5 2019
Basband Version Unknown
Kernel Version 4.4.167
#24 Thu Dec 26 09:36:21 CST 2019
Build number
rk3399-userdebug 9 PQ2A.190305.002.eng.work2.20191226.161648 test-keys
MCUVer: RL78c_NCHHWY_F047PB -CAN84
FrameworkVer: px6-userdebug 9 PQ2A.190305.002
eng.work2.20191226.161648 test-keys
OSVer: 9 Thu Dec 26 09:3621 CST 2019
APPVer: 200200113-1920x1030-9600chwy-edp
Nandflash: 50.42G/64.00G
RAM: 2G/4G
BTVer: SD_carplay_I2S_191230_sdk1.5
Barcode: ZF-1809X02020033229
Model rk3399
Serial Number
Any help appreciated.
JIMMYRECARD said:
HI Guys,
Im a newbie here. Posted about a month ago but no reply.
I wish I had found the threads and reviews about the seller before I purchased. Most un helpful
I have a few issues i will list. The last discussion with the seller was about updating firmware. He tells me there is an update but After several weeks of messaging him i have had no reply. I am now discussing with PAYPAL.
http://www.autostereo.com.cn
https://www.aliexpress.com/item/32965483853.html
https://www.ebay.co.uk/itm/283835207820
QUITE FRANKLY. The user interface is very basic and ugly. So looking for assistance to do something.
Wanting to know if the HU is able to be update on firmware or Rooted o think you call it. If so will need instruction, and I am happy to pay someone for this. PAYPAL or Bank Transfer.
OK so issues.
HU
MAIN ISSUE is SOMETIME Screen will Flash a line from top to bottom
1. ECU SPEED AND REVS.. NOT WORKING
( ECU CABLE IS CONNECTED) I
2. ANDROID AUTO… INTERMITTENT. TURNS ON OFF ON OFF ON OFF..
.......FIXED......
3. EASY CONNECT… INTERMITTENT TURNS ON OFF ON OFF ON OFF
FIXED
4. Phone connection AUDIO QUALITY IS TERRIBLE,, SO BAD I cannot hear caller.
In the package, there is the miccorphone, did you connect this?
FIXED
5. DOOR OPEN Shows Wrong side If Car door is open on Left Screen shows on right.
Setting-----user setting----right side
THIS IS FIXED
6. Need to be able to change the Startup Screen (Yellow Car) UGLY. Also Car that show up in PNG file.
CAN ONLY CHANGE BOIT LOGO TO MONDEO OR YELLOW SPORTS CAR
NO OPTION TO USE MY OWN LOGO
Some of these things are nothing major but for what i paid I expect it to work as it should.
Detail are
Android Version 9
Security Patch April 5 2019
Basband Version Unknown
Kernel Version 4.4.167
#24 Thu Dec 26 09:36:21 CST 2019
Build number
rk3399-userdebug 9 PQ2A.190305.002.eng.work2.20191226.161648 test-keys
MCUVer: RL78c_NCHHWY_F047PB -CAN84
FrameworkVer: px6-userdebug 9 PQ2A.190305.002
eng.work2.20191226.161648 test-keys
OSVer: 9 Thu Dec 26 09:3621 CST 2019
APPVer: 200200113-1920x1030-9600chwy-edp
Nandflash: 50.42G/64.00G
RAM: 2G/4G
BTVer: SD_carplay_I2S_191230_sdk1.5
Barcode: ZF-1809X02020033229
Model rk3399
Serial Number
Any help appreciated.
Click to expand...
Click to collapse
Hi, with this kind of radio you will never have zero issue. On the other side it can give flexibilty and a lot of things you cannot have on other autoradio.
- To set sometihing you can access the Factory menu (password 126). There you can set logo and others aspets. But please act carefully, and on your own risk. First of all do a config back-up: in Factory menu click the "Export" button; that will create a dmcu.cfg file; save it on an external drive.
-Moreover, you should learn the way you can enter the recovery on your own radio.
- Here you can find about a ROM mod:
https://forum.xda-developers.com/an...t/rom-hal9k-mod-v4-mtcd-e-head-units-t4046361
Anyway if your are not sitisfied, the issue you reported are enough to send back via paypal. I suggest to avoid mods, if you want follow that way.
Usually, the firmware updates that the sellers provide are MCU file (dmcu.img) - if you get, the seller will tell you also the way to install; it's different from ROM.
MediaTerraneo said:
Hi, with this kind of radio you will never have zero issue. On the other side it can give flexibilty and a lot of things you cannot have on other autoradio.
- To set sometihing you can access the Factory menu (password 126). There you can set logo and others aspets. But please act carefully, and on your own risk. First of all do a config back-up: in Factory menu click the "Export" button; that will create a dmcu.cfg file; save it on an external drive.
-Moreover, you should learn the way you can enter the recovery on your own radio.
- Here you can find about a ROM mod:
https://forum.xda-developers.com/an...t/rom-hal9k-mod-v4-mtcd-e-head-units-t4046361
Anyway if your are not sitisfied, the issue you reported are enough to send back via paypal. I suggest to avoid mods, if you want follow that way.
Usually, the firmware updates that the sellers provide are MCU file (dmcu.img) - if you get, the seller will tell you also the way to install; it's different from ROM.
Click to expand...
Click to collapse
Thank you. I will have a look at that.
MediaTerraneo said:
Hi, with this kind of radio you will never have zero issue. On the other side it can give flexibilty and a lot of things you cannot have on other autoradio.
- To set sometihing you can access the Factory menu (password 126). There you can set logo and others aspets. But please act carefully, and on your own risk. First of all do a config back-up: in Factory menu click the "Export" button; that will create a dmcu.cfg file; save it on an external drive.
-Moreover, you should learn the way you can enter the recovery on your own radio.
- Here you can find about a ROM mod:
https://forum.xda-developers.com/an...t/rom-hal9k-mod-v4-mtcd-e-head-units-t4046361
Anyway if your are not sitisfied, the issue you reported are enough to send back via paypal. I suggest to avoid mods, if you want follow that way.
Usually, the firmware updates that the sellers provide are MCU file (dmcu.img) - if you get, the seller will tell you also the way to install; it's different from ROM.
Click to expand...
Click to collapse
Interesting and thanks again.
It doesnt look difficult from what I have read. The only question I would have, Is it worth doing? Can I revert to OEM if it isnt what I want? Further Given the type of HU i have is this possible with the Dowload available or is it for a particular type? Mine is PX6 Android 9.0 from the factory. DOes it make any difference if its 13.6" screen?
But First and foremost I will work out how to get to recovery as you say.
Cheers again, your a good man.
JIMMYRECARD said:
Interesting and thanks again.
It doesnt look difficult from what I have read. The only question I would have, Is it worth doing? Can I revert to OEM if it isnt what I want? Further Given the type of HU i have is this possible with the Dowload available or is it for a particular type? Mine is PX6 Android 9.0 from the factory. DOes it make any difference if its 13.6" screen?
But First and foremost I will work out how to get to recovery as you say.
Cheers again, your a good man.
Click to expand...
Click to collapse
Hi,
It depends on your interest and your intention to dedicate time . In my opinion the @Hal9k_ ROM is a very intersting one.
Yes, you can go back to the original ROM, but you must have the file to do that. May be if you ask to @Hal9k_ , he could tell you more details about the possibility to go back to the OEM.
What makes differece among Head Units is:
- the Hardware model: you have a PX6, a good one
- the Brand, as it tells you the MCU (the low level firmware) you can use when updating it
- the screen size is not so important, but it must be a supported one
About entering recovery have a look https://www.youtube.com/watch?v=lPQgV_55Rkk&feature=youtu.be
It may depend on your specific Unit.
Cheers