yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] 5ft24:
well,

Eonon may have screwed me.

All was good until I followed their final step to set the "car model" they told me to use under extra settings. that changed the resolution. now the screen shows about 2/3 of the screen, from the upper left...

Cant even see the option to get back to it to change. any way to get the resolution changed? Im going to try the 5/15 version that was posted here...
[Android Head-Units] 5ft24:
Under the car model select, all the lines had "1dinFZ". None were without that and none had 2din. Just sent them an email asking for the correct firmware... With a USB keyboard I'm able to tab around and get into the settings
[Android Head-Units] Llew292:
that actually is the right firmware its actually a little older than mine which is Here: https://drive.google.com/file/d/0BwOAE5pUHp8hUEJjam9ZTjAzalU

either will work don't listen when they say to change the resolution...and be sure to clear cashe in recovery i had problems with bluetooth before

you may not need to completely reflash again you may get away with just clearing your data in recovery as wll
[Android Head-Units] ADB100:
Confusion?

I purchased an AllWinner R16 based unit a while ago and it was came with Android 4.4.2. I flashed the IQ Navi firmware that improved it somewhat, however other hardware issues made me remove it from my car. It is one from this thread: https://xdaforums.com/android-auto/android-head-units/2nd-generation-4-4-2-android-21u-ouku-t3230587

I 'think' its the same hardware as the units in this thread, however I can't seem to work out if any of the firmware links will flash?

The filenames for the firmware for my unit have always been:

92e82e86-1e25-11e5-bffa-000c29ba27c0	system

91973a18-1e25-11e5-b937-000c29ba27c0	boot

90436790-1e25-11e5-9b35-000c29ba27c0	data

bd07a5ee-fbb0-11e4-ae78-000c29ba27c0	MCU

ab6475a6-982d-11e4-887a-000c29ba27c0	???

Regardless of whether it was the factory or a custom firmware. These don't seem to tie-up with the firmware filenames shown in this thread?

Has anyone managed to flash any of the Android 6.01 firmware from this thread to one of the older R16 units?

Andy
[Android Head-Units] dick-jones:
Hi! Here is the archive with the firmware and the video instructions.

https://yadi.sk/d/CEZ8Rwe_3KbMbj
[Android Head-Units] 5ft24:
Did clearing the cache and data fix the Bluetooth issue? Mine isn't working now LOL
[Android Head-Units] Bradsr12:
I would just like to say thank you so much, I tried this even you did not know if it would work on the GA7162, however it did, and everything seems to be working fantastically,

So i would really like to say thank you and how grateful I am..

Many thanks
[Android Head-Units] 5ft24:
Cool.

Glad I could help!
[Android Head-Units] Llew292:
yep though i did a factory settings reset with it booted first then rebooted to recovery an wiped data and cashe
[Android Head-Units] 5ft24:
Ok, so the update you have from 05/15 loads fine then changes the resolution to the way the other did. It also has a box with red letters in it that says "unauthorized UI contact your supplier"

Went back to the 5/9 with the fix
[Android Head-Units] 5ft24:
did that, then reflashed it and did it again... Still no BT
[Android Head-Units] pir8man:
Our R16 units are extremely similar, but not the same as the RK3*** units. the CPU/APU is different, although both are designed as clones of the Cortex A9, there may be kernel differences. I have not come across any information about swapping ROMs from a different CPU based Head Unit. On that note... I am looking forward to doing some tests for us. I just split the Malaysk rom up into 400MB files and renamed them same as my R16 unit looks for in System Update. I need to do some backups and such before I can get to testing if it works or bricks my HU. I have recovery, so I should be able to unbrick it. I have unbricked it once already, so I just want some backups before I proceed. Then I need a few hours free to do the testing. LOL!

I also just read that the MCU on MCTD units are swappable. Our R16 units have different MCU identifiers, so I am unsure if our units are even MCTD. Apparently you can even unbrick and MCTD unit that got flashed the wrong MCU. But if our R16 units are based on older MCU, then none of that is possible. More research needed. :) I personally am not worried about this... With the 0509 update from EONON, the included MCU update resolved my glitches.
[Android Head-Units] Jefft5:
Hi Pir8man, thanks for taking an interest in my post, have you had any experience of the Maylask rom? In my humble opinion it is so much better than any of the Android head unit stock roms and I can't understand why the head units are marketed with such a limited OS when they are obviously capable of so much more. Anyway, that's my gripe over, I only wish I had sufficient knowledge of the Android system to be able to experiment confidently myself. I don't know if you have seen this thread or if it may be of help to you:- https://xdaforums.com/android-auto/android-head-units/2nd-generation-4-4-2-android-21u-ouku-t3230587. It relates to an earlier version using the R16 cpu and running 4.4.4.

I will follow your progress with great interest, I still have my R16 GA2162 in my test rig so perhaps I may be able to run a couple of tests that may help. I've aleady rooted it but I've found that Xposed can't be loaded in the normal fashion and so has to be loaded using boot. However I have loaded TWRP which allows me to make a backup but it creates a package similar to the Malaysk package which system update ignores.

As you can see my knowledge is very limited.
[Android Head-Units] pir8man:
Sadly, I have not seen a Malaysk ROM in action (only the thread pictures), which is why I started thinking about testing it on my HU. I have no prior knowledge before I picked up this unit a couple months back. I have seen the earlier thread, but only skimmed it as I did not need 4.4.4 knowledge.

I am suprised that you found a working TWRP for the R16. I only have the limited stock recovery.
[Android Head-Units] Jefft5:
The TWRP that I loaded is actually TWRP manager from Playstore and released by JMZ Software, it is not the full version but does allow you to create a backup and restore that backup, but not a lot else, I am working on loading a full version at the moment.

The TWRP manager saves the backup to the sd card in a similar format to the Malaysk custom rom and, although I haven't tried it yet, I believe the restore function may allow the custom rom to be written to OS area, but I want to be sure I can revert to the existing rom before I try that.

I have two other Eonon Android head units, the GA2114 and GA2154 both of which have the Malaysk rom installed and both run smoothly and stably.
[Android Head-Units] Llew292:
Hmmm not sure what's going on there can you turn Bluetooth on an off in the settings?
[Android Head-Units] 5ft24:
Been thru all the settings, and can't find any way to turn Bluetooth on and off.
[Android Head-Units] pir8man:
I received my new HU today. I can't install it until the ISO cable adapter for my Hyundai arrives. So maybe next weekend project to convert from my current to the new one. I am scared to do any testing on it while I rely on it for daily driving. I am gonna hook up 12v supply to the new one in the mean time. I will toy with updates and custom roms on it before it becomes my daily driver unit.

EDIT: Tracking shows my ISO cable adapter will arrive Monday. I will hopefully be able to more testing on both units sooner.

5ft24: your GA2160 unit is a KLD unit. You can swap to the KBT rom, but you HAVE to factory reset & wipe data/cache in recovery for it to adapt properly to your MCU & hardware (BlueTooth/LCD size).

If you are running a KLD/KBT/KED/etc. rom and you update to a newer same manufacturer KLD/KBT/KED rom, you do not have to do any resets (typically). Only when changing from one manufacturer's rom to another. KBT is one company, KLD is another. EONON just resells the units from different manufacturers.

Once flashed, setting car type also helps the MCU configure for LCD/DPI and any Hard/Soft Buttons. Selecting the correct one here is critical. Full resets are required if you get this wrong. A backup of your MCU.cfg is extremely helpful with this. With a good backup of your MCU.cfg, you can flash any R16 rom and restore your MCU.cfg, then reboot and everything works. Much easier than scrolling through the system menus to select and configure buttons, etc.
[Android Head-Units] mrchrister:
Hey giys, seems like I have this model as well. Same processor and 6.0.1. root doesn't work for me though. When I try to root with kingoroot, it reboots the radio at 90%
[Android Head-Units] Jefft5:
Try this:- Got root on my GA2162 stock rom:- Did factory reset (password 7890) then used apk. installer to install Kingroot and KingOroot from sd card (apps downloaded on windows) then copied both files to inand. (no internet connection at this time)

Hit Kingroot, took about 30 seconds, root established. Connected to internet, downloaded root checker from Google Playstore, ran root checker, root verified.

I probably didn't need to install KingOroot, I've just quoted above the exact steps that were successful.
[Android Head-Units] mrkambo:
im going to try and go from KBT to KLD see if it fixes the BT issue!

---------- Post added at 10:19 AM ---------- Previous post was at 09:39 AM ----------

Well that didnt work, got stuck in a boot loop! back to 20170509 with broken BT
[Android Head-Units] mrkambo:
Nah i dont think i did, im getting so annoyed, so 20170509 was working fine, got it all setup BT worked, then washed the car and left it parked up for 2 hours, jumped in it to pop over and see a friend, and it was stuck in a boot loop, im wondering if ive killed the unit some how, gonna try 20170427, see if that works

---------- Post added at 05:00 PM ---------- Previous post was at 04:29 PM ----------

well 20170427 didnt work, gonna try 20170309 if it doesnt work, time to get another unit, unless anyone else knows anything else i can try.

---------- Post added at 05:41 PM ---------- Previous post was at 05:00 PM ----------

20170309 didnt work either, its just stuck in a loop, it optimises apps on the initail boot, then after its finished just reboots its self! Fresh out of ideas!
[Android Head-Units] pir8man:
if you are flashing bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 along with your ROM versions, then you are also flashing the MCU. I would locate the bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 (MCU) for YOUR maker and then reset everything again. IF you have not been flashing this also, then I am stumped.
[Android Head-Units] mrkambo:
so i just went out to the car and flashed bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 and yeah its working now, but still no bluetooth, does anyone know of a way to hard reset with hard buttons and not built in factory reset option.

I mean im hoping when i go out to the car in the morning it will still be working, but time will tell
[Android Head-Units] pir8man:
install telnet, enter "reboot recovery" in terminal. this will place you in recovery to select wipe data/cache.
[Android Head-Units] mrkambo:
Worked a treat! Got BT working and everything! Think i might leave it alone for a bit till we get some custom ROMs then ill put it on the bench to play with!
[Android Head-Units] pir8man:
New PX5 unit is installed and working. Now I can wire up the R16 unit for some ROM testing. I am not sure if anything will even work. Thankfully, I no longer rely on the unit for daily driving, so I am willing to flash/brick/unbrick or anything else that is needed. MwaHaHa

Look for updates in a few days after I get wiring done and have time to attempt some flashes.

I prepared latest Malaysk 5.1 and 6.0 roms. I then split (400MB) the image and renamed for R16 units. Hopefully one of them will be CPU compatible. I also have the latest factory ROM (including OS, Recovery, bootloader and MCU) for my unit to unbrick, if necessary.

Schedule lightened up so I completed my wiring and did a test flash. I then went to recovery to wipe data/cache. Reboot shows my OEM logo, but never transistions into ROM loading. That is all I had time for today.
[Android Head-Units] dick-jones:
Hi, can you give me your latest factory ROM?

Thanks.
[Android Head-Units] pir8man:
see post #133
[Android Head-Units] mrchrister:
Just flashed the newest rom over from 4PDA. It kept all my settings and worked a treat but I lost BT (like so many others it seems)

I will try wiping cache/data in recovery tonight. Just wondering [MENTION=707164]pir8man[/MENTION] where would I find the MCU.cfg in my backup?
[Android Head-Units] mrkambo:
which rom is this? do you have a link?
[Android Head-Units] mrchrister:
It's Kaier V7.3.1_20170610.110122_KED1

This came pre-installed:

[IMG="this is the firmware before flashing"]http://i.imgur.com/HG5YDFv.jpg[/IMG]
[Android Head-Units] mrchrister:
I don't want to jinx it but it looks like all it needed was a restart. BT works great now. With the old firmware I had an issue with WiFi and BT not connecting automatically. I always had to go into settings and click on my phones wifi hotspot manually. With the new firmware this is fixed, yey! Happy camper here
[Android Head-Units] dick-jones:
Check out the EQ balance, if not working properly, it is necessary to do a factory reset.
[Android Head-Units] rizu3544:
Dear Gentlemen,

Would you please share the link of Firmware for the attached Android Head Unit.
[Android Head-Units] dick-jones:
Sorry, but I did not see such firmware.

Can you copy the file Launcher2.apk from the folder system/priv-app/Launcher2 and give a link to the file. Thank you.
[Android Head-Units] rizu3544:
Please check attached file.

Would you please share your launcher apk and your launch screenshot... ?
[Android Head-Units] cole7:
Can you share the content please?
[Android Head-Units] dick-jones:
View attachment Launcher2-mlt1.apk

View attachment Launcher2-kld.apk

View attachment Launcher2-ked.apk

View attachment Launcher2-eonon.apk

View attachment Launcher2-TH6.apk

View attachment Launcher2-jyzc.apk

View attachment Launcher2-tw2.apk

You should rename the file to Launcher2.apk, replace it in the folder system/priv-app/Launcher2/ and set permissions to 0644. Need root.

Attention! Before you do that, install any other launcher. Need it, whatever your head unit is not locked, if something you did wrong.
[Android Head-Units] rizu3544:
Thanks bro..!!
[Android Head-Units] grandamle91:
I have the GA2164 and mine is stuck on a bootloop and can't get it to the update start screen. Mine was set to not turn off for a hour after the key was turned off, so even after i do the reset and turn off and back on after 5 secs its just tring to boot
[Android Head-Units] dick-jones:
Try this...

Copy your firmware in root of SD CARD.

You need to copy 4 files from the archive

81cb828c-9b57-11e6-ad2a-df6786178d62

827ba428-9b57-11e6-8dfb-37398ea70e52.0

827ba428-9b57-11e6-8dfb-37398ea70e52.1

827ba428-9b57-11e6-8dfb-37398ea70e52.2

Insert SD CARD in GPS CARD slot. Then hold HOME and press RESET. Hold HOME until update start.
[Honor 8 Questions & Answers] @kevinsaju3:
I think it one of the best camera phone of 2016 and may be 2017.
[Honor 8 Questions & Answers] shook187:
Really? Compared to what other cameras? You must have not used any other phone if you're going to make that statement. It's definitely a mid tier camera compared to the flagship cameras that are currently out.
[Honor 8 Questions & Answers] Sheldd:
I dont see the point of this tread... And let's be serious,isn't the best one. I think you didnt tried to make video recordings using zoom. It's decent,it's good,but not the best ?
[Honor 8 Questions & Answers] jkccl9:
iphone and the pixel cameras are the best huawei are still catching up
[X 2014 Q&A, Help & Troubleshooting] noenoen:
Sorry for the noob. just want to ask how to fix this.

everytime im restart device always go to bootloader and have this message (pic).

later i want to flash stock rom via adb command and fail and have those message.

thank you
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Jaimesco12:
I want to flash an image that wont brick me but one that can make it wifi only. I do not have sprint so I would love to just have the feeling of having a wifi only tab s2. Is there any way I can make this happen? I am on marshmallow.
[Tilt, TyTN II, MDA Vario III Accessories] deadbolt67:
Does anyone have a working "AC Number", or discount code for Proclip? It is going to cost over 100.00 bucks for their mount and I would like to get out a cheap as possible. If anyone can help me out it would be greatly appreciated.

Oh yeah, the 521047 code does not work any longer.

Regards,

Michael
[Tilt, TyTN II, MDA Vario III Accessories] alienboy2k:
discount code

Try 271191, it worked for me a few weeks ago.
[Galaxy S 4 i9506 Android Development] 3lambda:
/** Your warranty is now void. Knox 0x1.*

* I am not responsible for bricked devices, dead SD cards,

* thermonuclear war, or you getting fired because the alarm app failed. Please

* do some research if you have any concerns about features included in this kernel*/

​

CM 14.1 Kernel :​

Huge thanks to @kyasu for his source !

Thanks @gugu0das for his precious help !

His blog

Features :

- New governors

- New i/o schedulers

- New tcp congestion

- Voltage control

- Adreno idler by @arter97

- Frandom

- intelliplug

- Powersuspend by @faux123

- Add fastcharge (need fix)

- Gave a name to kernel :)

- Some more...

This is experimental and still in beta !!!

Downloads :

CM14 kernel

Resurrection remix,Crdroid kernel

Instruction :

1. make a backup of your kernel

2. flash the kernel

3. Use Kernel auditor to customise kernel feature

More to come !

XDA:DevDB Information

Xenom series cyanogenmod, Kernel for the Samsung Galaxy S4

Contributors

3lambda, gugu0das

Source Code: https://github.com/atxoxx/android_kernel_samsung_msm8974-1

Kernel Special Features:

Version Information

Status: Testing

Current Beta Version: 2.0

Beta Release Date: 2016-12-22

Created 2016-12-22

Last Updated 2016-12-23
[Galaxy S 4 i9506 Android Development] 3lambda:
Kernel updated !

- Frandom

- adreno idler

- intelliplug

Enjoy

cm13 kernel will come this night or tomorrow maybe
[Galaxy S 4 i9506 Android Development] xanderovitch:
It doesn't boot with kyasu 14.1 rom...
[Galaxy S 4 i9506 Android Development] 3lambda:
When I'll go home I'll do something

You stay on the boot animation right ?
[Galaxy S 4 i9506 Android Development] Baffsuki:
Hey 3lambda does the kernel work with other 7.1.1 ROMs such as RR N,crDroid,Beanstalk etc,M
[Galaxy S 4 i9506 Android Development] 3lambda:
It works for resurrection remix (I tested only on this one)

But I'll can support other rom

I'll try to upload different version tomorrow :)

I'll need tester :)
[Galaxy S 4 i9506 Android Development] Baffsuki:
OK! Can I be your tester?

---------- Post added at 03:49 AM ---------- Previous post was at 03:40 AM ----------

Hey 3lambda after flashing the latest version the Fast Charge and Adreno Idler doesn't show in Kernel Adiutor..
[Galaxy S 4 i9506 Android Development] 3lambda:
For fast charge in battery you should see it (I have )

For adreno idler it enable itself (stated 200mhz instead of 3xx something for gpu )
[Galaxy S 4 i9506 Android Development] WeirdSoup:
I found that kyasu has pushed more than 5,000 commits on his repo today. Do you have a plan to merge them into this?
[Galaxy S 4 i9506 Android Development] 3lambda:
If that's kernel related yes :)
[Galaxy S 4 i9506 Android Development] 3lambda:
okay getting some motivation

I'm gonna release new note 7 and cm14.1 (cm and Resurrection remix) kernel

For cm13 it'll come maybe today :)

stay tuned
[Galaxy S 4 i9506 Android Development] Baffsuki:
yiiieeee boiiii thanks
[Galaxy S 4 i9506 Android Development] 3lambda:
Updated !

Made a CM14 version

Made a resurrection remix and crdroid version (need feedback for beanstalk etc)

- fixed some mistakes

Fastcharge is of now as I had problem with it

Stay tuned
[Galaxy S 4 i9506 Android Development] sevenlife:
Still didnt manage to boot with kyasus cm 14.1
[Galaxy S 4 i9506 Android Development] 3lambda:
Which file you flash ?
[Galaxy S 4 i9506 Android Development] Marcin_L:
On crDroid fastcharge is also unavailable
[Galaxy S 4 i9506 Android Development] 3lambda:
Yap

I deactivated it as o had problem with this feature will look later into it

Envoyé de mon GT-I9506 en utilisant Tapatalk
[Galaxy S 4 i9506 Android Development] sevenlife:
Cmnkernel2
[Galaxy S 4 i9506 Android Development] 3lambda:
Hmm weird

I'll try to fix it then

Do anyone else isn't able to boot under kyasu cm ?

Envoyé de mon GT-I9506 en utilisant Tapatalk
[Galaxy S 4 i9506 Android Development] Baffsuki:
I was able to boot fine with Kyasu's CM14.1 ROM with Xenon kernel. Works fine, haven't tested RR yet :)
[Galaxy S 4 i9506 Android Development] 3lambda:
I'll be on vacation so I'll don't have my computer

I'll be back after Christmas

I keep you informed :)
[Galaxy S 4 i9506 Android Development] jqm_:
Is IR sensor working with this kernel? Anyone tested?
[Galaxy S 4 i9506 Android Development] 3lambda:
No idea I never used it

But if it work in stock it'll work on this one too
[Galaxy S 4 i9506 Android Development] Dedede_:
where is the cm13 kernel file?

Merry Christmas ;)
[Galaxy S 4 i9506 Android Development] 3lambda:
I didn't released it yet as I focuses on cm 14 and note 7 rom

When I'll go back from Christmas vacation I'll release it :)

And thanks you too
[Galaxy S 4 i9506 Android Development] TonyTeoTeo:
Hi, do you support E330SLK? Thanks.
[Galaxy S 4 i9506 Android Development] 3lambda:
If stock kernel from kyasu cm14 work

Yes this kernel will work normally :)

Give feedback of it work :) I'll state it in op
[Galaxy S 4 i9506 Android Development] sevenlife:
I still didnt manage to boot with kyasus rom.i have i9506. It stays to boot logo more than 20 mins
[Galaxy S 4 i9506 Android Development] 3lambda:
That's strange...

You're sure you flash cmnkernel.zip ? If yes try to redownload it from another browser

Of it still doesn't work then I don't know.... Some people reported it worked ok
[Galaxy S 4 i9506 Android Development] xarisioannina:
have a good time on your holidays I travel also tomorrow After vacations I will search for the new version of note 7 kernel :P
[Galaxy S 4 i9506 Android Development] marcinadd:
I installed on RR and stucked on boot logo.
[Galaxy S 4 i9506 Android Development] 3lambda:
Which rr version you use?
[Galaxy S 4 i9506 Android Development] marcinadd:
[MENTION=4993440]3lambda[/MENTION] I use version from 23 December.
[Galaxy S 4 i9506 Android Development] 3lambda:
Strange

Have you a system less supersu or Magisk?

Envoyé de mon GT-I9506 en utilisant Tapatalk
[Galaxy S 4 i9506 Android Development] marcinadd:
I have use Root Manager from Settings. I have Data and Cache on F2FS.
[Galaxy S 4 i9506 Android Development] 3lambda:
Hmm on stock kernel f2fs work ?

If so I'll look into that later
[Galaxy S 4 i9506 Android Development] 3lambda:
Cm13 will come in 2 or 3 days :)

Stay tuned
[Galaxy S 4 i9506 Android Development] Baffsuki:
I don't know about you guys but this rom is perfectly compatible with crDroid and RR.

Maybe you have chosen the wrong zip, here:

For RR and crDroid use the RRNKernel.

For Cyanogenmod use the CMNKernel. Its really easy, but I don't know why u guys even have bootloop, maybe you have changed something that the kernel doesn't support or you haven't followed the instructions. Plus we'll have to wait what LineageOS will become, I think that the new crDroid update is based on LineageOS.
[Galaxy S 4 i9506 Android Development] sevenlife:
Propably i have bootloop cause i use f2fs data and case. I cant think something else.
[Galaxy S 4 i9506 Android Development] rinkashime_014:
I tried it on RR and crDroid in f2fs data and cache both stuck in bootlogo.

So I tried again using ext4 data and cache and managed to boot. The bootloop happens when you use f2fs.
[Galaxy S 4 i9506 Android Development] 3lambda:
Weird

That's based on kyasu source and some people had f2fs on kyasu build

I'll take a look when I'll have time
[Galaxy S 4 i9506 Android Development] sevenlife:
With kyasus rom and kernel f2fs works ok, with your kernel and f2fs i have bootloop. I9506