yashsingh1/xdaforums huggingface dataset:
[Shield Tablet General] MrKaon:
looking for latest K1 Stock Recover Image here can't see 5.3 :eek::eek: it is been ages since OTA released but no factory image yet.

Why NVIDIA can't release it same time as OTA, like Google does:confused:
[Shield Tablet General] fpozar:
If you want to you can go to 5.2 as described here, then ota to 5.3 and then continue the guide.
[Shield Tablet General] alekos1992:
Man, thank you so much! I was looking for anything to refresh my poor old K1 as it came to a point where 2:30 hours of SOT was the achievement of a century and the general performance where comparable with that of the HTC Dream..

I followed step by step your instructions and everything turned out WAY better than I expected! Just passed the 2 hours of SOT after setting up the minimal stuff are now installed on it while consuming only 30% battery on half brightness and playing sweet sweet tunes!

Of course the performance are not even comparable with today's devices but it is night and day compared to the latest stock rom (and countless stuff I had installed), I would say the performance now are OK, definitely not frustrating, which is a huge and very noticeable difference..

Also first time installing a Lineage ROM (I installed tesla a year back but it wasn't really any better than the stock ROM). I've got to say, very stable and the basic suit of apps is sweet and really just enough for the K1 if your main intent is to watch stuff on it. (of course always installing MiXPlorer instead of using the painful stock file "manager").

Thank you again for saving my sad tablet :D
[Shield Tablet General] moliverac8:
What happened with this? :(
[Shield Tablet General] fpozar:
Don't worry the update is coming, even after 2 weeks of testing it's still very quick and ram management is great too. It's just that I'm quite busy, I will try to do it one day next week.
[Shield Tablet General] fpozar:
Guide updated ! Check the OP :)
[Shield Tablet General] moliverac8:
Go through MicroG settings app self check tool and get everything to have a tick

I don't understand this last step. I can't see any microG settings or app. I have flashed the lineage ROM with microG support you gave us. I tried to install the gsmcore.apk as the microG page said, but the system doesn't allow me to.

I have another problem, I saw that I can't use any of the apps that I paid for in the play store, and I saw that you can get the play store with microG but I'm unable to install it.

Also, Ram management is awesome, feels like a totally new tablet, I can keep Spotify and several chrome pages at the time, and none of those apps got killed and this is just an example. Snappy as hell.

As you said, it's totally game changer
[Shield Tablet General] fpozar:
Are you sure you flashed the microg version of lineage os? If I remember correctly, after flashing I didn't have to install anything and microg was mostly good to go out of the box.

Though, it's been 3 weeks since I've done that so I might have forgotten something, I may do a clean flash some time in a week or two if I find the time, but I am not sure. But, most of this regarding microg isn't device specific so any guide for other devices should do the trick. Report back if you find out more :)
[Shield Tablet General] NoFrown:
Install MicroG

It might be my mistake, but I can't find a guide to install MicroG anywhere.

I want to install it on Validus Rom.

I only see a special fork for lineageOS.

Help would be really appreciated.

I might be just blind, but really couldn't find it anywhere :silly:
[Shield Tablet General] fpozar:
I didn't write how to do it here because it requires xposed and stuff.
[Shield Tablet General] darth_antz:
thanks again for your awesome post, youve helped me get a lot out of my shield tablet.

With the release of bitobsessions new kernel, and progress happening in lineage 15 (probably only a few weeks to go until an official build), i hope you do continue this thread and keep us all informed with the process.

I think you lost a few of us with MicroG, but that should be seen as an alternative, if you rely solely on apk's and not google play.

Ive also implemented battery charge limit, to preserve my battery. i got it from this thread in the axon 7

https://xdaforums.com/axon-7/how-to/guide-how-to-avoid-battery-degradation-t3789740

Since moving to lineage, i dont think my speakers are as loud as stock. Please add any sound support you may have used to the guide, with the pending lineage 15 updates.
[Shield Tablet General] fpozar:
Thanks for reading the guide, I'm glad I could help! I'm sorry if MicroG part was harder to follow/understand but I've kept the old guide, there is a link to it in the OP which you can always follow. It is a bit harder to understand and follow, but as you said, it pays off greatly if you don't need google play games (some google services DO work, like logging into chrome, google drive, youtube, syncing etc...).

Regarding Los15.1, I'm keeping an eye on oreo development and most certanly will try oreo and android GO when we get hw acceleration. I'm not sure about the sound, perhaps you can tinker with it by using Viper4Android or Audio Fx to increase base volume (don't increase by much tho). Also, how good is the newest kernel from BitO? I haven't tried it because my tablet is serving me too well atm to go through all the hassle of flashing again.

Edit : that battery charging limitation was a smart thing to do. I use it on my phone to keep it healthy (I don't allow it to charge above 85%) but I don't use it on the tablet because I keep the shield turned off during the day so I don't charge it all to often really. Never the less, I might add that in the next update
[Shield Tablet General] darth_antz:
I installed the latest RR build and the new bitobsession kernel on Saturday.

Everytime i update a new build, i open and follow your guide again. I only wipe dalvik and cache, then install the new build. this way i dont need to set anything up new again.

New kernel installation is straight forward, havent had any issues yet. But also i havent done anything intensive, just basic web browsing and e-book. everything is smooth and i havent had any restarts.

I'll just use a cheap bluetooth speaker i have to combat my low volume audio issues. i spent a lot of time early on with my axon7 getting viper4arise running and it was a big stuff around. its straight forward now, but i wouldnt bother with it largely untested/advertised in these forums.

wont be long until oreo now! And everyone give your thanks to Steele1 and bitobsession for their work and contributions to make this tablet great

Thanks fpozar
[Shield Tablet General] fpozar:
You are very welcome, that's exactly what I was trying to accomplish with this, I wanted a place where I (and others) can return for the links and steps. And yes, the hw acceleration thing is a major breakthrough, I'll try my first oreo rom next week I hope :)

If you wanna try viper4android it's very easy to set up on roms without audiofx. You just download a magisk module which is available inside magisk manager app under downloads tab and you should be good to go out of the box.
[Shield Tablet General] jemail:
For those wanting to install microg on a non lineage microg rom

Google 'Shadow53 microg' and read his blog.

He provides flashable microg zips, Google calendar and contacts sync zips, swype libs, the whole lot.
[Shield Tablet General] RichDem:
HI All,

I wanted to try this so I flashed the latest original ROM as suggested, everything appeared to go OK but the tablet just sits on the Android logo screen. I left it for over 30 minutes so I am sure it is in a bootloop. I can get back into the bootloader so I tried to get in the recovery to do a factory reset but get stuck on the "No Command" screen. I have tried every key combination for the last 2 hours but cannot get into the stock recovery. Is it something to do with the fact when I did the original setup I changed the file system

Any ideas what I can do?
[Shield Tablet General] RichDem:
OK I figured out that I can boot to TWRP and follow the procedure to get Lineage running. My issue i when I try to go back to the stock Nvidia Rom, then it hangs on the Android logo
[Shield Tablet General] fpozar:
You have to flash using adb (maybe fastboot i can't remember any more), there is a guide included in every stock rom zip file

Edit : this procedure only applies to stock roms, for any custom rom (not based on stock) you can follow this
[Shield Tablet General] RichDem:
That is exactly how did flash the original ROM, I downloaded the recovery files and placed them into my ADB folder, confirmed I could see the tablet then boot into the bootloader. I tried the "Flash-all.bat" procedure and manually flashing each part as per the Nvidia instructions. Both ways appeared to be successful but the tablet will still not boot up and no matter what I do I cannot access the android recovery to perform a factory wipe and clear the cache. I wonder if it is something to do with changing the file system when following this procedure for data & cache but am not sure what file system the original ROM uses.

Last night I followed the new procedure using MicroG and have my tablet back up and running with the Fork of Lineage but I would like to know how to get it back to the stock ROM
[Shield Tablet General] fpozar:
I'm not sure to be honest. I haven't been on stock even for firmware purposes for over a year. Did you try to use a different cable and usb port (if you're using a PC try connecting to the back side ports, not the ones on your case's hub)? Also try using "minimal fastboot and adb" (just google it). Btw, you should be able to clean stuff through adb, there is a delete all or clear all command, it's also in the manual.

One more thing I personally would do is flash the oldest shield tablet rom you can find (the only lolipop version) and then flash some other version you prefer. The lolipop rom is labeled factory rom or something like that, maybe it's more compatible than others? Sorry if this is too much bro science xD, I'm no developer at all so I'm just throwing stuff that I know from experience. Good luck !
[Shield Tablet General] RichDem:
Hey no worries.

I appreciate your help and your work putting this together. Maybe someone else will see this and chime in, for now I will just stick to the Lineage for MicroG as I just use this tablet at work for Spotify and for other media consumption.

I thought I would post an update (Dec 2019), I decided to play around with my Shield K1 again, I fixed the issue of not being able to flash the stock ROM by simply changing the data & cache partitions back to ext2 before flashing the stock ROM. After doing this I could install the stock ROM without any issues
[FYT Android Head Units] sweetnothings:
I made a small apk which can forward a dial request from Google Voice to the Joying BT Dial app.

the following patterns get stripped out to make it work: " ", "-", "(0)", "(", ")", "."

There is no launchable activity so you cant see it in launcher, it is only visible by the installed apps list in settings.

On first use:

- In the result of Google Voice search (where it repeats your command and call the dialer) you need to choose the new dialer with the 3-dot menu button. the choice is sticky on future calls as long as you dont change it back again.

- And you need to grant Call Permission to it and redo your voice search on the first time.

- You can use a contact management app too (like google contacts), just make my app the default dialer and it should work.

the app is available in Play Store:

http://play.google.com/store/apps/details?id=com.judlis.googlevoicecallhandler4joying

i will post the source code when i think it is stable enough.

One important note:

If you keep seeing a window with 1 input field containing the number and 2 buttons "Make Call" and "Cancel" please report me the exact content of the input field and, if it is not a valid phone number to dial, the number with minimal changes it needs to be valid. Use "x" instead of numbers to keep privacy of the phone contact.
[FYT Android Head Units] gustden:
I looked at writing an app for this about a year ago. I ended up making a modification to the paid app "Tablet Talk" so it would perform the same function. I bought it to allow SMS capabilities on the head unit, but it was able to be modified to also perform this same function. Since it was a paid app, I did not distribute the apk, just instructions on how to modify the app.

https://xdaforums.com/android-auto/android-head-units/google-voice-to-initiate-calls-joying-t3528923

Great to see an easy way for users to get this to work without having to buy an app and modifying it. I will give it a try when it is in the app store.

Nice work!
[FYT Android Head Units] sweetnothings:
Yes, i used your instructions too before i made this one, thanks.

By the way, Google has approved and enabled the app this morning. So it is availavle now.
[FYT Android Head Units] ste2002:
Same here: had to install a paid voice assistant (non-modified though) which is able to make "built-in" Joying dialer dial a contact (on non-rooted HU). "OK Google" could not. Still on 1 week demo period. Pity it can not be widely recommended since it only works with my local language (Dusi Assistant). Off: funny it can report news, weather, location, launch navi already with destination, tell anecdotes, call mom etc, manage tasker tasks and other scripts etc. - rather powerful assistant.

Thanks for the app - the link is already alive, will try it shortly (+1).
[FYT Android Head Units] ste2002:
I've just installed and tried the app, but when Google started dialing there is "Start of Joying BT App failed" error message.

Should HU be rooted for app to work? Mine is not. I used Android settings to allow the app using phone (the only option there), have chosen the app as a default dialer, but no success. I did not do " redo your voice search on the first time" recomendation since did not quite get what exactly is to be done. Tried dialing several times.
[FYT Android Head Units] sweetnothings:
on which rom version is your HU? i assume you did not replace the Joying BT apk as you did not install any superuser.

root is not needed.

i upload a modified version which rethrows the exception "joying bt activity not found" so you can report it to play store and i can get it. (should be on play store in about 1 to 3 hours, if you force to research for updates)
[FYT Android Head Units] ste2002:
My HU is on September latest rom version. I will download modified app and report the state in hour or two, thank you.
[FYT Android Head Units] ste2002:
Have just sent error report (2 times, under "Error" and "Error2 the same error") using udated application. Hope it can help understand what's wrong with my setup, thank you.
[FYT Android Head Units] sweetnothings:
thanks, you can load a new update from play store to try out.
[FYT Android Head Units] ste2002:
Now it goes one step further: phone number with + prefix is shown at top left together with two buttons like dial and canceal and then says "Joying BT app not found" and there is no option to send a report. I could press dial button again having again that error message.
[FYT Android Head Units] sweetnothings:
ok, i am sorry about that.

lets try one more approach. you can find a new version in Play Store.

if this does not do the trick, i will have to debug this with same conditions as yours on my end i think.
[FYT Android Head Units] ste2002:
Yesss, now it works!

It is not as fast as Dusi in starting the dialing itself - one can feel some background struggle with built-in BT (which shows at screen top like icons flicker), but it does the trick. Just great, you've done it, thank you so much!
[FYT Android Head Units] sweetnothings:
you are welcome! i am happy that it works for you now and thank you for the testing!

can you tell me in what kind of format your phone numbers are? mine are in int. format like +41 99 999 99 99. but there are a lot formats depending of localization, not sure if i got all variants.

and if you use a phone book app like Google Contacts or something similar if you can initiate a call from there?
[FYT Android Head Units] sweetnothings:
for all others who try out the app, please report here :

- the format of phone numbers you are using

- and if you use a phone book app like Google Contacts or some similar app if you can make a call from it.

thanks
[FYT Android Head Units] ste2002:
As to phone format here, it is as follows: if we want to make it kind of "readable", it can look like +7(916)123-45-67 or 8(916)123-4567.

But what surprizes me is how phonenumbers are currently shown in my Galaxy S6 phone: +79161234567 - no any characters to spoil the dialing process, but before your app Google could not really dial those on Joying HU, was only pretending it dials. It was/is OK with dialing by voice on phone itself.

Thank you again, it was a major hole in Joying basic functionality.
[FYT Android Head Units] sweetnothings:
+79161234567 is the international format which works, we will see if other formats are used by google too.

if the would be passed from Google Voice Command to the Joying app in exactly this format it would work out of the box.

But the problem is that Google Voice Command reformat the numbers before passing it to Joying depending of the Region with caracters like minus sign, dot or spaces what the Joying app did not like.

thanks for sharing your informations.
[FYT Android Head Units] ste2002:
Just an observation, I can not explain this: on the first attempt (after wake-up) to voice call a contact no factory BT is initiated. Begins to work from the second try. Pity I mostly need only one outcoming call per drive.
[FYT Android Head Units] sweetnothings:
strange thing, i never had this on my unit.

may be a timing problem, but no clue where.

are there any (error) messages?

at which point exactly does it stop?

or whats the exact difference compared to the working case?

can you try the following:

- open the Joying bt-app

- make sure it has connection to your phone

- go to home screen

- try to dial out with google voice command
[FYT Android Head Units] hidroela:
first of all thanks for the app, would be really nice if the make call button have not need to be press to finalize the process.
[FYT Android Head Units] sweetnothings:
should not be needed, just if i am unsure if phone numer is formatted correct.

can you please tell me the exact content in the input field and where you are located? have you stored the numbers in international format?
[FYT Android Head Units] hidroela:
+1832xxxxxxx

USA

1 832-xxx-xxxx

thanks for looking
[FYT Android Head Units] sweetnothings:
so "+1832xxxxxxx" is the exact format of the content in the input field? ("+" sign is not missing?)

if you do not push the button for make the call and instead voice dial it again, does it behave the same way?

are ther any messages appearing in the app?
[FYT Android Head Units] hidroela:
sorry the + sign does not show on the input field, what i got is 1832xxxxxxx
[FYT Android Head Units] ste2002:
Hi!

There is no any messages, BT app simply does not pop up, no any seen difference to a working case. If I start BT app before making 1st call and then switch to Google, that also does not help. In both cases no any phone number is shown above, there is no those 2 fields which I could see in earlier version of your app.

Can not even say if "+" sign is present - might be the clue to try?

===============================

Just a wild suggestion: strip the phonenumber string of all symbols except 0123456789, including "+" sign, then append "+" sign at the beginning and pass it to Joying BT app.

Just in case: I have not written any code since '90s, sorry :).
[FYT Android Head Units] sweetnothings:
ok and the number saved on Contacts is exactly as "1 832-xxx-xxxx"?

or is it as "01 832-xxx-xxxx"?

EDIT: There is a new version with added phone number info provided by Google Voice Search which info will help me to implement the correct transformation, if you dont mind to check that for me.
[FYT Android Head Units] hidroela:
yes it is exactly as "1 832-xxx-xxxx" will try when I get home

thanks
[FYT Android Head Units] sweetnothings:
may it works now with the latest version.

can you tell me which of the following numbers are valid ones in the US?

1 832-xxx-xxxx (i am sure it is)

+1 832-xxx-xxxx (pretty sure it is too)

001 832-xxx-xxxx

01 832-xxx-xxxx

832-xxx-xxxx

xxx-xxxx

i would guess int. numbers like this works too right?

+41 xxxxxxxxx

or has it still to be in this format?

011 41 xxxxxxxxx

tnx for your great assistance!
[FYT Android Head Units] ste2002:
I have just tried a new version, there was an error which I could not read without glasses, but error log was sent (my format is +7 987 123 45 67, +7(987)123-45-67).
[FYT Android Head Units] sweetnothings:
your number format should always work without problem.

please check if you have the latest version (2.4), there was a bug in 2.3
[FYT Android Head Units] sweetnothings:
so in not working case, the app opens but not more? what is displayed then in the app? what do you mean with there are not 2 fields visible?

there should be the the title, one input field (may be empty but should be there) and 2 buttons.

now in the latest version, the number passed from google should also be displayed below the title.

may you can post a picture of the screen
[FYT Android Head Units] hidroela:
try the latest version 2.6 and it is working like it is supposed to thanks for this little app
[FYT Android Head Units] ste2002:
Still (with latest version) the 1st attempt fails to popup BT app. The second try is successful. In both cases (success or not) the field with phone number and two buttons appear at left top very shortly - I can hardly read-out the phone number (it looks correct, but one can not be absolutely sure because of little time).

I did not try the method of starting BT app prior to making a call yet.
[FYT Android Head Units] sweetnothings:
in the not working case, does my app stay open or close immediately too?
[FYT Android Head Units] ste2002:
Do you mean in background? Because I do not see your app on the foreground in both cases, only an icon on left top for short time (and phone number field with two buttons shortly).

I use 3rd party "Car Launcher AG" and next time I am going to switch back to Joying launcher before dialing.
[FYT Android Head Units] sweetnothings:
Yes thats all it is, two buttons and the number field.

when it close my app then the joying activity has been closed. since joying does always respond canceled status, i cannot check that anything more.

but i will try to check how fast it does return, if it is to quick i will try again one time.

Can you send me your Google Play Store email address with a private message so i can add you as beta tester? that way i can push special test versions for you.
[FYT Android Head Units] ste2002:
Done. Thank you.

=====================

Just became a "tester", now going outside to download and make a test call, thank you.

=====================

Had it just tested, details in PM.
[FYT Android Head Units] RONIN68:
Hello, from the playstore I see it is compatible only from android 5.0 (I tried and on 4.0 it does not install). Can you make a version compatible with 4.0?

thank you (excuse me for english english - google translator)
[FYT Android Head Units] sweetnothings:
if you send me your google play email adress (private message) i will add you as beta tester