[Q] CyanogenMod 10.1 Themes - Samsung Galaxy Gio GT-S5660

Hai people, I'm here because I have my Galaxy Gio with CyanogenMod 10.1 and I want to install themes. When I install a theme, it goes well, but when I apply, it displays the following: "This theme was improperly incompiled and can't be applied. Please report this incident to the theme's author." What am I doing wrong?!
Phone Specs:
Model: GT-S5660
Android Version: 4.2.1 Jelly Bean
BaseBand Version: S5660XXKT6
Kernel Version: [email protected]#1 Sun Jan 6 10:38:58 PST 2013
CPU: ARMv6-compatible processor rev 5 (v6l)
RAM: 276Mb
CyanogenMod Version: 10.1-20130106-UNOFFICIAL-gio
Compilation Date: Sun Jan 6 09:57:45 PST 2013
Compilation Number: cm_gio-userdebug 4.2.1 JOP40D eng.olddroid.20130106.095610 test-keys
Rooted: Yes
ClockWorkMod Recovery: Yes
Any info you need I'll present

MetroxGamer said:
Hai people, I'm here because I have my Galaxy Gio with CyanogenMod 10.1 and I want to install themes. When I install a theme, it goes well, but when I apply, it displays the following: "This theme was improperly incompiled and can't be applied. Please report this incident to the theme's author." What am I doing wrong?!
Phone Specs:
Model: GT-S5660
Android Version: 4.2.1 Jelly Bean
BaseBand Version: S5660XXKT6
Kernel Version: [email protected]#1 Sun Jan 6 10:38:58 PST 2013
CPU: ARMv6-compatible processor rev 5 (v6l)
RAM: 276Mb
CyanogenMod Version: 10.1-20130106-UNOFFICIAL-gio
Compilation Date: Sun Jan 6 09:57:45 PST 2013
Compilation Number: cm_gio-userdebug 4.2.1 JOP40D eng.olddroid.20130106.095610 test-keys
Rooted: Yes
ClockWorkMod Recovery: Yes
Any info you need I'll present
Click to expand...
Click to collapse
Go in your build.prop and search for something like screen.dpi or whatever anyway it should be 160 from the start change it to something like 140 and reboot then apply the theme

Desmaize38 said:
Go in your build.prop and search for something like screen.dpi or whatever anyway it should be 160 from the start change it to something like 140 and reboot then apply the theme
Click to expand...
Click to collapse
I have HVGA, do I really need to do that?? (I have no problems in that but just asking)
BTW where can I find that?
~180ppi Pixel Density

MetroxGamer said:
I have HVGA, do I really need to do that?? (I have no problems in that but just asking)
BTW where can I find that?
~180ppi Pixel Density
Click to expand...
Click to collapse
Do you know how to use root explorer? If not then:
Download root browser lite and go to the root folder (contains system, sys, sbin and some other silly folders).
Go in system and at ther botton there should be a file named build.prop, open it with a text editor. Then start looking for a line like this "ro.sf.lcd_density=160" change the 160 to 140 save && reboot. after you can apply your theme. If you dont like the layout you can always change back to 160 and your theme should be still applied.

Desmaize38 said:
Do you know how to use root explorer? If not then:
Download root browser lite and go to the root folder (contains system, sys, sbin and some other silly folders).
Go in system and at ther botton there should be a file named build.prop, open it with a text editor. Then start looking for a line like this "ro.sf.lcd_density=160" change the 160 to 140 save && reboot. after you can apply your theme. If you dont like the layout you can always change back to 160 and your theme should be still applied.
Click to expand...
Click to collapse
I changed it to 140, applied and rebooted; BlackScreen.... Had to reinstall CM10.1 :s

MetroxGamer said:
I changed it to 140, applied and rebooted; BlackScreen.... Had to reinstall CM10.1 :s
Click to expand...
Click to collapse
That's weird.. which CM 10.1 version do you use? (I'll check it myself)

Desmaize38 said:
That's weird.. which CM 10.1 version do you use? (I'll check it myself)
Click to expand...
Click to collapse
Yeah, if you could solve this I would be very appreciated

Related

How can you tell which kernel you are currently running?

A forum search turned up nothing, so I'm asking here:
On most Android phones, you usually go to Settings->About Phone and look under the "Kernel Version" section to see the name and version of the kernel you are running.
With my Galaxy Nexus, I don't see kernel names. Instead, I see something like:
Code:
3.0.31-g6fb96c9
[email protected])
#1 SMP PREEMPTY Thu Jun 28 11:02:39 PDT
2012
No matter which kernel I flash, it always seems like the same type of info but no names or version numbers.
I was okay with that as long as I remembered what I flashed last. However, I recently reverted to stock but the kernel looks like it stayed the same. Is there anyway to check if I'm back on stock kernel or still running the last kernel flashed (franco, in my case)?
I'm running leankernel 4.3.0 it says the version
Sent from my Galaxy Nexus
drdoombot said:
A forum search turned up nothing, so I'm asking here:
On most Android phones, you usually go to Settings->About Phone and look under the "Kernel Version" section to see the name and version of the kernel you are running.
With my Galaxy Nexus, I don't see kernel names. Instead, I see something like:
Code:
3.0.31-g6fb96c9
[email protected])
#1 SMP PREEMPTY Thu Jun 28 11:02:39 PDT
2012
No matter which kernel I flash, it always seems like the same type of info but no names or version numbers.
I was okay with that as long as I remembered what I flashed last. However, I recently reverted to stock but the kernel looks like it stayed the same. Is there anyway to check if I'm back on stock kernel or still running the last kernel flashed (franco, in my case)?
Click to expand...
Click to collapse
Most (if not all) kernels have a name similar to stock. But there is usually something amongst the numbers and letters which point to what kernel your running.
For instance my phone running trinity.
I know its trinity because it says dirtymorfic, morfic being the xda name of the trinity kernel developer. I only use stock kernel and trinity so can't comment on the others, but it will always look similar but also always have something pointing to the kernel your using. Hope this helps
Sent from my Galaxy Nexus using Tapatalk 2
Also typing code below in terminal will give you some more bits of info.
Code:
cat /proc/version
good day.
question
sir i want to ask 2 questions :
my phone specifications after flashing jelly blast v2 are:
android version:4.1.1
baseband version :S5360DDLC2
KERNEL VERSION : 2.6.35.7 [email protected]#1
BUILD NUMBER :NXT2ICSv2:jelly blast
1.i want to install jelly blast v3 what i have to do?
2. installing a custom rom change a kernel version or not ?
sunil332011 said:
sir i want to ask 2 questions :
my phone specifications after flashing jelly blast v2 are:
android version:4.1.1
baseband version :S5360DDLC2
KERNEL VERSION : 2.6.35.7 [email protected]#1
BUILD NUMBER :NXT2ICSv2:jelly blast
1.i want to install jelly blast v3 what i have to do?
2. installing a custom rom change a kernel version or not ?
Click to expand...
Click to collapse
Why did you bump a thread that's months old, and you don't even have our device?
Sent from my Nexus
a small doubt about sony xperia z ultra
there is a date under the kernel.
but that is not the same as the date of purchase
date of purchase is june 12 2015 at 12pm
date in the kernel is june 12 2014 at 2pm
am i being cheated with an old or used phone?
also the video clarity is very bad for a FHD screen
help me please
mnanoop said:
there is a date under the kernel.
but that is not the same as the date of purchase
date of purchase is june 12 2015 at 12pm
date in the kernel is june 12 2014 at 2pm
am i being cheated with an old or used phone?
also the video clarity is very bad for a FHD screen
help me please
Click to expand...
Click to collapse
1. Kernel and rom are developed much earlier, you weren't cheated.
2. Video clarity? Do you mean the video recording quality or the screen quality?
im running cm12 (android 5.1.) on my lg d855 right now, and it shows my kernel version in the "about phone" category.

Google Wallet Compatibility List

With the main thread for Google Wallet (GW) now reaching well into 200 pages it is getting to the point where it takes hrs to find out if GW will work for you.
lgkahn, daitienshi, and myself have develped a spreadsheet for tracking what works and does not. Feel free to check the list. If the rom you are running is not listed give it a try and let one of us know through a private msg, and we will add it to the list. If you happen to have GW working please let us know so that we can add it to our spreadsheet.
Please include the following.
Carrier
ROM
ROM Version
Base Band (this can be found in settings / about phone)
GW version
Any extras that need to be flashed
What build.prop you used and if you changed it back to stock
Any notes that you feel are relevant.
And last but not least DOES IT WORK.
Samsung Galaxy S III Google Wallet Compatibility
The carriers have been broken out into different tabs at the bottom.​
ROMS that are compatible.
SERENITY 1.3 - T-Mobile GNote II Port
JellyBean747 Milestone 7 Graystone Edition
Carrier : T-mobile
ROM: FreeGS3 R6
ROM Version: R6
Base Band : T999UVLH2
GW version: Wallet version 1.4-r79-v5-2 (Hoping to update to r81 just need to find out what to do to go from current version to latest)
do as stated in original op for gw and you are set
What build.prop you used and if you changed it back to stock: htc_jewel
Any notes that you feel are relevant.: none
And last but not least DOES IT WORK.: Yes it does work tried it at two different McDonald' and my job which is a car dealership. So far so good.
1Shotwonder said:
Carrier : T-mobile
ROM: FreeGS3 R6
ROM Version: R6
Base Band : T999UVLH2
GW version: Wallet version 1.4-r79-v5-2 (Hoping to update to r81 just need to find out what to do to go from current version to latest)
do as stated in original op for gw and you are set
What build.prop you used and if you changed it back to stock: htc_jewel
Any notes that you feel are relevant.: none
And last but not least DOES IT WORK.: Yes it does work tried it at two different McDonald' and my job which is a car dealership. So far so good.
Click to expand...
Click to collapse
Thank you it as been added to the list.
Just a note you forgot to add the carrier to the spread sheet not sure if you left out on purpose but did notice you asked for it but its not in the spread sheet.
Also did update the google wallet but I wont post with latest version till I can do a real test out somewhere hopefully tomorrow I will be able to do so.
1Shotwonder said:
Just a note you forgot to add the carrier to the spread sheet not sure if you left out on purpose but did notice you asked for it but its not in the spread sheet.
Click to expand...
Click to collapse
I separated the spreadsheet into tabs. If you look at the tabs on the bottom the carriers will be there. Sorry for any confusion that this created.
Rom: Stock (rooted)
Rom Version: 4.0.4
Baseband Version: UVALJ4
Google Wallet Version: 1.5-r81-v4
Status: Working
Extra 1: SGS3-TW-US_variants-lib_nfc-fix
Extra 2:
Build prop: (used htc_jewel, then reverted back to stock)
Notes: Changed build prop, flashed lib nfc fix, flash wallet, setup wallet, revert build prop back, profit
imaleecher
Added Thanks
DW
Digital_Warrior said:
imaleecher
Added Thanks
DW
Click to expand...
Click to collapse
Carrier: AT&T
ROM: Tasks AOKP Version 10/21
Android Version: 4.1.2
Baseband: I747UCLH1
GW: com.google.android.apps.walletnfcrel.modaco.1.5-r81-v4.zip
Extras: changed model, device, name to "htc_jewel"
Confirmed working (tested at mcdonalds)
same here worked at Sunoco
Sent from my SGH-I747 using Xparent Blue Tapatalk 2
Carrier: TMO
ROM: Wicked V5, ICS (TMO UVALG1 Base)
Base Band: UVLI1
GW version: com.google.android.apps.walletnfcrel.modaco.1.5-r79-v5-2.zip
Extra: SGS3-TW-US_variants-lib&nfc-fix.zip
Build.prop: ro.product.model=Galaxy Nexus/ro.product.name=yakju/ro.product.device=maguro
Notes: Changed build.prop back to stock after successfully adding card, and before rebooting phone.
Notes: Cards added succesfully at google.com/wallet on PC. Working fine.
Carrier: T-Mobile
ROM: Codename Android
ROM Version: 3.6.6
Base Band: T999UVLH2
GW version: 1.5-r79-v5
Extras: None
Build Prop: htc_jewel then back to stock
Notes: 1. Change build prop to htc_jewel (device, name, model) 2. Flash GW 3. Add cards 4. Revert build prop to stock 5. Reboot
Status: Working
AttachedSilver said:
Carrier: T-Mobile
ROM: Codename Android
ROM Version: 3.6.6
Base Band: T99UVLH2
GW version: 1.5-r79-v5
Extras: None
Build Prop: htc_jewel then back to stock
Notes: 1. Change build prop to htc_jewel (device, name, model) 2. Flash GW 3. Add cards 4. Revert build prop to stock 5. Reboot
Status: Working
Click to expand...
Click to collapse
That's Jelly Bean, I had to look, lol.
Carrier : Rogers
ROM: CM10
ROM Version: 10-20121023-NIGHTLY-d2att
Base Band : I747MVLLH1
GW version: Wallet version 1.5-r81-v4
Extras: none
What build.prop you used and if you changed it back to stock: htc_jewel and Galaxy Nexus
Any notes that you feel are relevant.: none
And last but not least DOES IT WORK.: No. Wallet doesn't show up in app drawer unless I defrost using Titanium. I can then open but adding cards fails.
A thank you.
A Thank you to every one above this post.
Your information has been entered into the spreadsheet.
DW
P.S.
Dam Forum can only thank 8 times per day what a rip off.
NEW VERSION GW TESTED:good:
Carrier : T-mobile
ROM: FreeGS3 R6
ROM Version: R6
Base Band : T999UVLH2
GW version: Wallet version 1.5-r81-v4
do as stated in original op for gw and you are set
What build.prop you used and if you changed it back to stock: htc_jewel
Any notes that you feel are relevant.: none
And last but not least DOES IT WORK.: Yes it does work tried it at a McDonald's this afternoon worked fine like previous version of gw.
Dam Forum can only thank 8 times per day what a rip off.
Click to expand...
Click to collapse
Not too long ago it was just five, lol.:silly:
imaleecher said:
Rom: Stock (rooted)
Rom Version: 4.0.4
Baseband Version: UVALJ4
Google Wallet Version: 1.5-r81-v4
Status: Working
Extra 1: SGS3-TW-US_variants-lib_nfc-fix
Extra 2:
Build prop: (used htc_jewel, then reverted back to stock)
Notes: Changed build prop, flashed lib nfc fix, flash wallet, setup wallet, revert build prop back, profit
Click to expand...
Click to collapse
DId you try using it? I have the exact same setup, it adds card sucessfully, but it does not work when I try it in store today (7-11). The card reader does not pick up google wallet.
zengshengliu said:
DId you try using it? I have the exact same setup, it adds card sucessfully, but it does not work when I try it in store today (7-11). The card reader does not pick up google wallet.
Click to expand...
Click to collapse
I'm using it with this setup and its working for me. I tried it at a circle K. did you switch the build prop back?
AttachedSilver said:
I'm using it with this setup and its working for me. I tried it at a circle K. did you switch the build prop back?
Click to expand...
Click to collapse
I did switched the build prop back to the original one.
I odin back to stock, then root, and follow the step to install the nfc fix and wallet, add card, switch back build prop
When I try it on 7-11, I first turn on the wallet, put it on top of the sensor, no response.
zengshengliu said:
I did switched the build prop back to the original one.
I odin back to stock, then root, and follow the step to install the nfc fix and wallet, add card, switch back build prop
When I try it on 7-11, I first turn on the wallet, put it on top of the sensor, no response.
Click to expand...
Click to collapse
I flashed from CM10 to stock Deodexed LJ4. Is your build LH2?

[Q] HELP ME PLZ | Rom question

I just followed the instructions of qbking77's video walking through the note toolkit v4.1.0
I have granted access for root and i see the superSU app on my
I have created a backup to my external sd card bc my pc has only 800 mb available.
Now i feel like my next step is to "flash a rom". Is this correct. Which ones can and can't i install. I looked at this labrats bc/ it was popular but it is saying it is 4.1.1 while i am at 4.1.2 for my android version.
My model version is sph-l900
android version 4.1.2
baseband version l900vpamc2
Kernel version
3.0.31-903705
[email protected] #1
smp preempt tue jan 29 17:10:38 kst 2013
Build Number: JZ054K.L900VPAMC2
Hardware Version: L900.09
Can you please tell me what is next. and what is possible and what my next steps are? Thank you.
brett701 said:
I just followed the instructions of qbking77's video walking through the note toolkit v4.1.0
I have granted access for root and i see the superSU app on my
I have created a backup to my external sd card bc my pc has only 800 mb available.
Now i feel like my next step is to "flash a rom". Is this correct. Which ones can and can't i install. I looked at this labrats bc/ it was popular but it is saying it is 4.1.1 while i am at 4.1.2 for my android version.
My model version is sph-l900
android version 4.1.2
baseband version l900vpamc2
Kernel version
3.0.31-903705
[email protected] #1
smp preempt tue jan 29 17:10:38 kst 2013
Build Number: JZ054K.L900VPAMC2
Hardware Version: L900.09
Can you please tell me what is next. and what is possible and what my next steps are? Thank you.
Click to expand...
Click to collapse
To my understanding, 4.1.2 allows home screen rotation and minor performance enhancing (i may be wrong) but if you flash a rom and it puts you on 4.1.1 its not a big deal as there are mods you can flash that will enable that option and it's actually built in to some roms. There's tw (touchwiz) roms and there's aosp roms, I suggest you do your research about the difference between the two before flashing either and of course make a backup before flashing anything in case something goes wrong. I also suggest no matter what rom you flash read the OP and at least the first and last 10 pages of that thread, that will give you a good idea as to what issues users have ran into and most likely the fix. Im no expert by any means and I do more reading than posting because just about any question i have has been asked and answered already. You can't go wrong with any tw rom and they all have different mods/tweaks...nothing wrong with trying them all...and the developers are incredible and more than willing to help you out (users are too) as long as you did your part in trying to find the answer your looking for before posting in they're threads. I can't say much for aosp because I stick with tw but I'm sure the devs/users there would help out as well. I can't stress enough about doing your research before flashing anything and always make a backup first. You had a successful root so your off to a good start, good luck man :thumbup:

[ROM] iOS 8.0 [ALPHA] [Alpha 2 WIP]

Hi everyone! Tonight I'm releasing my iOS 8.0 ROM which is based on LineageOS 13.0!
**** | ~WORKING~ | ****
Even though this is still an Alpha Build, everything seems to be working fine already
**** | ~NOT WORKING~ | ****
~ SELinux can't be changed to Enforcing, but that's related to the Base ROM aka LineageOS and also I do not have the knowledge to try to fix that.
**** | ~BUGS~ | ****
~ DualBoot Patcher (Preinstalled, but can be removed) shows the ROM being installed on "Data-Slot" but it's actually supposed to be on "Primary".
I will fix this in the next Builds
~ LineageOS's Stock Camera crashes when switching between Camera and Video, (Both are working though, but Camera Application has to be restarted) Use "Open Camera" to fix this Issue.
**** | ~FEATURES~ | ****
~ Carrier Name can be changed or hidden
~ Battery Percentage can be hidden or Displayed
~ Signal Strength can be hidden or Displayed
~ "Stock" Notificationbar can be accessed through opening the iOS Notificationbar, then swiping down again
~ Spotlight Search (Swipe down from Home Screen)
~ iOS Control Center
~ iOS Lockscreen with PIN Code Support
~ ROOT is included! (SuperSU)
ROM OS VERSION: iOS 8.0 (Android 6.0)
ROM KERNEL: 3.4.x
ROM VERSION REQUIRED: TWRP Recovery 3.2.1-0
BASED ON: LineageOS 13.0
Version Information:
STATUS: ALPHA / WIP
DEVICE: G800F
Created: 04/01/2018
Last Updated: No Update yet!
CHANGELOG:
Code:
04.01.2018 > Initial Release of Alpha 0.1
04.02.2018 > Due to Compatibility Issues the Current Base ROM [LOS 13] will be Updated/Changed, Alpha 2 for now is WIP!
04/02/2018 2:38AM UPDATE: Please see latest Post for further Information.
**** | How to Install | ****
Downloads
~ iOS 8.0 - Alpha 0.1
https://www.androidfilehost.com/?fid=962157660013069618
~ The ROM is completely Google-Free, Which means you need to download your Apps as APK File (I will add some Apps already Installed in the next Builds Just tell me which Apps you're using mostly )
Installation
Download the Backup.rar File, and extract it
in TWRP/BACKUPS/ then reboot to Recovery, wipe everything except /Internal Storage and /External SD, after that go to "Restore" and simply restore the Backup. After that you're done and another reboot will start your Device with the iOS ROM
NOTE: In some cases it might still show "No OS Installed" even after you successfully restored the Backup, but that can be ignored for now.
Can you take some screenshots of the rom?
DechnyLamtra13 said:
Can you take some screenshots of the rom?
Click to expand...
Click to collapse
+1
Reserved LOL
Screenshots:
I will test it,thanks!!!
Del.
Is this for G800F or G800H ?
another343 said:
Is this for G800F or G800H ?
Click to expand...
Click to collapse
It's for the G800F
I get an error when unzipping
Misma13 said:
I get an error when unzipping
Click to expand...
Click to collapse
Which Program do you use for unzipping?
EDIT: I downloaded the ROM again from the Link and extracted it with the app "RAR" and I didn't encounter any Errors.
i can't see the restore backuop. I made my own and i can restore it, but i just dont see yours.
why can i possible doing wrong? file explorer sees it, even the one built in the twrp..
qasq said:
i can't see the restore backuop. I made my own and i can restore it, but i just dont see yours.
why can i possible doing wrong? file explorer sees it, even the one built in the twrp..
Click to expand...
Click to collapse
Try moving the Backup to /TWRP/Backup/iOS-8 ROM/ so that the Backup files are in the iOS-8 ROM Folder, if that doesn't work then move only the Backup Files to /TWRP/Backup/
I will try to find a workaround for that, I did try to make an flashable ZIP first of the ROM but it instantly failed to flash somehow.
I tired all that, even tried from sdcard, backup doesn't seem to be seen the files at all, no matter what. I had many S devices, now I'm on S8+, i got almost all of them, but first time I see such issue I belive it's your fault somewhere or maybe TWRP sees that this is a backup from other device (same, but diffrent) and doesn't let me to use it!? Is there anyone else facing this issue ?
qasq said:
I tired all that, even tried from sdcard, backup doesn't seem to be seen the files at all, no matter what. I had many S devices, now I'm on S8+, i got almost all of them, but first time I see such issue I belive it's your fault somewhere or maybe TWRP sees that this is a backup from other device (same, but diffrent) and doesn't let me to use it!? Is there anyone else facing this issue ?
Click to expand...
Click to collapse
Well then the "Problem" is your Device Since this ROM is actually for the S5 Mini = kminiltexx
Fatal_Scythe said:
Well then the "Problem" is your Device Since this ROM is actually for the S5 Mini = kminiltexx
Click to expand...
Click to collapse
Yes, I know that. I've spelled the wrong thing. I hope this will clear the missunderstooding
Will there be any re to my last post?
qasq said:
Will there be any re to my last post?
Click to expand...
Click to collapse
Well what exactly do you mean / or what question do you want me to answer?

Grom V-line

Hi All.
I am new to XDA so please be gentle and I need some help.
I have a GROM V-Line system installed and it has been giving me hell these last 11 months and I am unable to get a refund from the buyer. It is android powered and uses a custom rom etc. I was wondering if anyone out there has any knowledge of these units and can guide me through a way to maybe update the system to remove custom ROMs so I can use it as a normal android type device.
The current set up is running on Android 5.1.1
Kernel version: 3.10.0 [email protected] #11
Build number: Lite_VL1.6.0.0
Not sure if there is anything I could, I am ready for throwing this out of my motor now.
Please help.
Ta
Kanjar2020 said:
Hi All.
I am new to XDA so please be gentle and I need some help.
I have a GROM V-Line system installed and it has been giving me hell these last 11 months and I am unable to get a refund from the buyer. It is android powered and uses a custom rom etc. I was wondering if anyone out there has any knowledge of these units and can guide me through a way to maybe update the system to remove custom ROMs so I can use it as a normal android type device.
The current set up is running on Android 5.1.1
Kernel version: 3.10.0 [email protected] #11
Build number: Lite_VL1.6.0.0
Not sure if there is anything I could, I am ready for throwing this out of my motor now.
Please help.
Ta
Click to expand...
Click to collapse
Hi Ta,
I installed the Vline VL2 in my Lexus two weeks ago and initially had issues.
Here's my versions out of the box.
System update is Android 8.1 with last security patch dated Jan 5, 2019 and won't update further.
Kernel: (gcc version 6.3.q 20170404 (Linaro GCC 6.3-2017.05))
[email protected] #3
Fri Mar 19 05:27:15 PDT 2021
Vline shows VCore: V20VL3.37.0.0
VBase: 32.38 (L22)
No further updates available.
DashLinq version: 5.5.2.5
Knob Helper version: 1.0
WebView Shell version: 1.0
---
I was initially pissed too but after several resets my system is pretty stable.
One item that remains an issue is crashing when I have any SD card installed...As long as no SD card installed then system runs pretty good.
Several issues via launch controller were fixed with a $1.99 replacement launcher named AGAMA by altercars.ru. https://altercars.ru/#about

Categories

Resources