yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] ryl313:
Hi USBhost,

I've tried flashing that ROM on my N9. However, wifi does not work and cannot be turned on (I think this is why I always got "Setup Wizard keeps stopping"). This makes me go back to previous Oreo ROM. Hopefully you fix it.

Just so you know, I use your O build as daily driver and I love it.

Keep up the good work :D
[Nexus 9 Android Development] =xom=:
On Android O, I can't turn on wifi.
[Nexus 9 Android Development] nyvled:
I am also unable to turn on WiFi. Any logs you need?
[Nexus 9 Android Development] albsat:
Confirm , WiFi can't be turned on via the toggle .
[Nexus 9 Android Development] iason747:
Took a log while trying to turn wifi on. Idk if it's helpful or not but here you go:

---- 17.09.2017 09:19:41 ----

09-17 09:19:24.101 428 522 I WifiNative-wlan0: Vendor HAL not supported, Ignore start...

09-17 09:19:24.101 428 522 E WificondControl: Failed to get reference to wificond

09-17 09:19:24.102 428 428 E WifiController: WifiControllerWifi turn on failed

09-17 09:19:24.103 428 522 E WificondControl: Failed to get reference to wificond

09-17 09:19:24.103 428 522 E WifiNative-wlan0: Failed to teardown interfaces from Wificond

09-17 09:19:24.105 151 151 W /system/bin/hwservicemanager: getTransportFromManifest: Cannot find entry android.hardware.wifi@1.0::IWifi in either framework or device manifest, using default transport.

09-17 09:19:24.105 428 522 I WifiNative-wlan0: Vendor HAL not supported, Ignore start...

09-17 09:19:24.105 428 522 E WificondControl: Failed to get reference to wificond

09-17 09:19:24.106 428 428 E WifiController: WifiControllerWifi turn on failed

09-17 09:19:24.107 428 522 E WificondControl: Failed to get reference to wificond

09-17 09:19:24.107 428 522 E WifiNative-wlan0: Failed to teardown interfaces from Wificond

09-17 09:19:24.108 151 151 W /system/bin/hwservicemanager: getTransportFromManifest: Cannot find entry android.hardware.wifi@1.0::IWifi in either framework or device manifest, using default transport.

09-17 09:19:24.108 428 522 I WifiNative-wlan0: Vendor HAL not supported, Ignore start...

09-17 09:19:24.108 428 522 E WificondControl: Failed to get reference to wificond

09-17 09:19:24.109 428 428 E WifiController: WifiControllerWifi turn on failed

09-17 09:19:24.110 428 522 E WificondControl: Failed to get reference to wificond

09-17 09:19:24.110 428 522 E WifiNative-wlan0: Failed to teardown interfaces from Wificond
[Nexus 9 Android Development] USBhost:
Okay thanks! I could have sworn it was working for me.

I'll see what's up in the morning
[Nexus 9 Android Development] beerente:
Hope you can fix it. This Oreo build was the only one that booted on my Nexus 9. :good:

-Edwin
[Nexus 9 Android Development] USBhost:
New O build is up and wifi is working!

Enjoy everyone. https://xdaforums.com/showpost.php?p=73806559&postcount=457

The problem was my fault... When I cleaned up all the junk in the device tree.

I forgot to copy one line for wifi https://github.com/USBhost/android_...mmit/815b62b31fc936d561cfae78632a8d1552c497a0

Oh and BTW does LTE work?
[Nexus 9 Android Development] dacench:
The link is empty
[Nexus 9 Android Development] USBhost:
Check again
[Nexus 9 Android Development] nyvled:
Thanks for the great work! I'll flash when I get back.

I have a WiFi model though, can't tell you if LTE works

Edit: Flashed, WiFi works! However initial tests show that YouTube videos on the YouTube app still runs laggy...

I'll test more when I get back home again, had to rush out for dinner!

Edit 2: Tested a little more, YouTube videos lag at times, but is easily solved by restarting the app. Doesn't happen often, may encounter a few dropped frames here and there for those interested. It's good enough that I'm staying on this release, thanks so much [MENTION=5501864]USBhost[/MENTION]!
[Nexus 9 Android Development] beerente:
WiFi working on latest build

Hi,

WiFi is working, thanks! :good:

Had to install Gboard, because AOSP keyboard kept foreclosing and couldn't enter my Wifi password (needed an @).

Lets setup now. :)

-Edwin
[Nexus 9 Android Development] tevil:
using the 7.2, not oreo and cant seem to get this to boot. I get to the boot android animation but it just goes and goes forever. Any thoughts?
[Nexus 9 Android Development] USBhost:
Was it a clean flash or dirty
[Nexus 9 Android Development] dictionary:
If this is from a clean flash, then your bootloader and vendor are probably outdated
[Nexus 9 Android Development] tevil:
clean

---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------

thought I grabbed the newest vendor, didnt think of the boot loader. any idea where I can get the most current ones so I can update. Doesnt seem Im finding the correct ones myself.

Thanks
[Nexus 9 Android Development] dictionary:
https://www.androidfilehost.com/?fid=745425885120729017
[Nexus 9 Android Development] tevil:
wouldnt have a vendor link as well by chance so I can compare. Been a LONG time since Ive played with this tablet.

thanks
[Nexus 9 Android Development] dictionary:
https://www.androidfilehost.com/?fid=817550096634791744
[Nexus 9 Android Development] tevil:
THANK YOU, updated the loader and that didnt do it. I dont think its the vendor tho since I know my phone will usually still bot but give you the device error.

Im going from scratch again, thanks guys.
[Nexus 9 Android Development] tevil:
disregard, thank you
[Nexus 9 Android Development] dictionary:
Phone or tablet?
[Nexus 9 Android Development] tevil:
this is my nexus 9 tablet. My nexus 5x phone (and I believe this as well in the past) will give you the device error when the vendor is wrong. I noticed the hang was happening after installing the gapps. If I didnt do apps then the rom booted fast and fine. after the reboot and apps install it would hang. I noticed it was creating some logs and a log zips in the folder after apps install so I removed them and reinstalled the apps and it finally booted after a long time.

I also installed that gapps zip fix so I dont know if that helped but from read I think that was an after boot setup thing.

Also had to end up installing this devs TWRP as mine got borked and would hang and reboot after wiping after a few install tried and the newer vendor and loaders installed.

just an all around weird deal. Its up and running now. Just finished installing my apps from backup.

Thanks.

I needed to get off the rom I was on because of some serious battery drain problems. Hopefully this one is better. I think ES file explorer is starting to become problematic and causing drain so I didnt reinstall that either.
[Nexus 9 Android Development] dictionary:
Just an FYI, this isn't like the 5x. You'll only get a vendor mismatch error after boot, but if your vendor is really old, at times it won't even boot. I've had to flash both new vendor and bootloader to get a couple of ROMs to boot before. If you got it to boot with flashing gapps cool. Just know, next time it's usually recommended to flash both new boot and new vendor.
[Nexus 9 Android Development] enriquejones666:
In case you didn't already know this, Do Not use ES File Explorer unless you have the paid version. The free version now comes bundled with questionable bloatware. MiXplorer is a good free alternative (found in the XDA app).
[Nexus 9 Android Development] albsat:
The last oreo build is not bad at all. Hope hw acceleration will be available soon . Good job!
[Nexus 9 Android Development] tevil:
thanks,

I couldnt find any vendor files other than the one I originally did so maybe it was older. I honestly forgot bootloaders existed.

This is sort of a back up tablet for me aside my pixel c so I havent flashed it in a LONG time. I dont ever remember honestly even needing to flash vendor files for this. ROM is nice, glad I switched over.

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

yeah Ive been removing it from all my devices. To bad it used to be my fav. I use another file explorer app by asus which works well and at least its a known company. I also use root explorer. It seemed every few weeks some other intrusive app was being loaded with ES. It was actually invading my lock screen on my Nexus 9 and I finally had enough and wanted to blow the whole tablet out to be rid of it.
[Nexus 9 Android Development] k8C:
Install ES File Explorer 4.0.2.3, people said it's the last version without bull****.
[Nexus 9 Android Development] albsat:
[MENTION=5501864]USBhost[/MENTION]

I am surprised how smooth is oreo version, although it doesn't have hw acceleration support. Hope you can make it! Great job as always. Thanks for your work!
[Nexus 9 Android Development] USBhost:
https://www.xda-developers.com/came...opers-make-hardware-work-without-source-code/ Hmm.. maybe i could do something like that to fix our HW... hmm.... just a thought
[Nexus 9 Android Development] nyvled:
I'm sure that will take a while; read this a few days ago and got confused by everything it mentioned hahahahahah. All the best to you man!
[Nexus 9 Android Development] USBhost:
Does anyone want an ARM ROM? It may have more free ram. I got arm to build and run just fine with the normal kernel. However GPS won't work because that is only arm64.
[Nexus 9 Android Development] didnt1able:
What's your opinion?
[Nexus 9 Android Development] Vledderos:
I dont need GPS on my N9, cant speak for others though. The only thing I care about for Oreo on N9 is to get HW working :)
[Nexus 9 Android Development] USBhost:
i know man i know! i want it to
[Nexus 9 Android Development] Vledderos:
haha sorry, no pressure ;)
[Nexus 9 Android Development] albsat:
Please express your creativity!
[Nexus 9 Android Development] lmulli:
I'm more partial to a big of LEG myself!
[Nexus 9 Android Development] jolinnard:
I'm interested... Could be an interesting experiment to our (old??) N9. Thanks!
[Nexus 9 Android Development] didnt1able:
If what's his face who is working on the shield kernel port ever gets that up and running a 32bit room would be manditory for it no?
[Nexus 9 Android Development] albsat:
I returned to nougat version and now I have a failed update notification. How do I remove it please?
[Nexus 9 Android Development] USBhost:
Will upload it sometime next week

Yes

You mean 7.1.1? If so just reflash vendor.

If you mean 7.1.2 then it's because google seemed to have dropped support for it. Aka there hasn't been a security update this month or the last iirc.
[Nexus 9 Android Development] albsat:
Can't post a Screenshot for the moment. I am on 7.1.2. The update offered is 779 mg and it offers 2017 - 10 patches.
[Nexus 9 Android Development] Bryanx86:
I love your Oreo rom. Idk how you do it, but you do it! Didn't even notice lack of hw acceleration. I do notice that this is the smoothest my tab has run in awhile, and doesn't seem to get as hot. Thank you!
[Nexus 9 Android Development] USBhost:
i know... i need to disable the ota.

Question to all: do I continue to supply 7.1.1 because 7.1.2 is no longer getting updates?
[Nexus 9 Android Development] dictionary:
I say skip both, and Oreo, and start delivering us some Android Parfait goodness already!! Lol. Just kidding. Personally, I'm in it for Oreo. I'm sure others will chime in though

---------- Post added at 04:14 AM ---------- Previous post was at 04:13 AM ----------

Oh, and release Arm build!!!!
[Nexus 9 Android Development] Bryanx86:
I personally enjoy using your Oreo build more than any other.:victory:
[Nexus 9 Android Development] jolinnard:
IMHO you should build the latest version you can with more security patches into. For now, I skip Oreo until HW accel works... Can we make something? Maybe make a request to HTC or something?
[Nexus 9 Android Development] albsat:
Same thought.
[Nexus 9 Android Development] didnt1able:
It would be Nvidia whom you would contact. And I believe it would be futile. Nvidia isn't known for letting out their secret sauce to some randoms on xda. Best chance is if vulkan gets ported from the shield tablet kernel and patched into the 32 bit o build somehow. It's gonna require max janky workarounds to get it working. There is some crazy ppl on here that get stuff working with obscuro methods so I do hold out hope.
[Nexus 9 Android Development] USBhost:
ANDROID 7.1.2 32BIT is up READ OP

ANDROID 8.0.0_r17 is up HW still broken though.
[Nexus 9 Android Development] didnt1able:
[MENTION=5501864]USBhost[/MENTION] Just curious has have you recieved any logs related to the HW acceleration on the 8.0 build?

And if not what do you think the best way to diagnose would be? Just curious if you havent recieved any logs i will install later on after i play around with the 32 bit build
[Nexus 9 Android Development] nyvled:
Is there anything new in r17?
[Nexus 9 Android Development] madbat99:
Gotta try this out. Thanks so much [MENTION=5501864]USBhost[/MENTION]
[Nexus 9 Android Development] Vartom:
Give the whole log, from the start of the system.
[Nexus 9 Android Development] USBhost:
Sure thing! Will have it up later today US PDT time.

However I have looked though the log in the past and found nothing wrong until you actually try using HW on videos. Games are completely fine unless they use video.

Edit: [MENTION=6556709]Vartom[/MENTION] here you go

logv is the full boot you wanted

logv2 is trying to play a mp4 and vp8 with MX player going from HW to SW
[Nexus 9 Android Development] albsat:
I tried to install the 32bit rom, but I didn't have complete backup restore with Titanium backup. Then I said to install the latest oreo, but it seems that I have lost recovery and no os. I am trying now to install everything via pc. Hope that the storage and the files are intact.
[Nexus 9 Android Development] USBhost:
Gahh I thought I fixed that recovery problem.... How hard is to to break a function in AOSP...

Your storage files should be fine.
[Nexus 9 Android Development] wantowan2:
If it didn't happen during your testing before you posted, it must be something else that corrupted it? You did test it right? Maybe with experimental builds, a more elaborate step by step of why this new 32bit version is worth while and what you did to have a successful result. It would have been a lot easier for this guy to figure out what happened if he could have followed correct steps and rule things out from there. Unless of course you didn't test it. Haha
[Nexus 9 Android Development] USBhost:
Test recovery yes. Flash ROM reboot system, reboot back to recovery, TWRP still there. And I know my 32bit ROM works. Because I'm typing on it now :cool: it seems to have more free ram but you know how those things go.

1: Flash ROM

2: Flash Gapps

3: Flash FIRE-ICE

4: setup without WiFi

5: reboot

6: add user account // I did this to avoid the long setup time at the wizard

Done.
[Nexus 9 Android Development] albsat:
Let me explain better what happened. I jumped from 7.1.2 to the 32bit version. The titanium Backup restore just hanged in the 32bit version and I could not have back my apps. So I tried to install the oreo version, and here I lost the recovery.

I installed recovery via PC and evth is OK.

If anyone wants to install oreo, it is necessary to install the latest Fire kernel from usbhost.
[Nexus 9 Android Development] albsat:
I really hope that usbhost and Vartom would put their creativity in bringing hw acceleration in oreo. It would be a great achievement for this abandoned tablet from Google. Shame on Google for that. :d
[Nexus 9 Android Development] jolinnard:
Any issues with Google Play Games, or Keep? I tried Oreo ROM yesterday (very late at night) and could setup bypassing setup wizard, but after login to my Google account and install some gapps from Play Store Keep and Play Games didn't work (forced all permissions and tried something else, like install an old version from apkmirror... no luck). Had to recover a backup before sleep, but I'd like to try playing with a 32 bits system...
[Nexus 9 Android Development] USBhost:
Google play games is working just fine however it was a little finicky at first.

Something to think about is maybe all these weird things are infact our cpu at work. Nvidia kept saying that our CPU optimizes ARM processes they never said ARM64 or aarch64. But they could have meant ARM as a whole. Anyways just thoughts I'm having.

On the side note arm is running quite nicely. I will work on getting the super old gps arm binary to work because having a working gps is better than none.

Edit: oh you meant Oreo... Oops my bad... I was talking about the arm build.

I haven't messed around with O other than testing HW. So I wouldn't know much about.
[Nexus 9 Android Development] didnt1able:
Just a heads up on the 32 bit ROM, changing the minimum gpu frequency in kernel auditor doesn't stick. I find having the minimum gpu frequency at 180 to be very good for UI. Mainly because I'm not sure what Nvidia is doing with their scheduler in regards to clocking up. Just letting you know
[Nexus 9 Android Development] albsat:
Does titanium Backup restore works for you guys that have installed the 32bit version?
[Nexus 9 Android Development] USBhost:
Yes however when coming from 64 to 32 you may have incompatibilies
[Nexus 9 Android Development] jolinnard:
Yeah, possibly you have to download from play store first and then restore only data in Titanium... But who knows what developers do with their apps between architectures...

Thanks for Play Games explanation, at first I wrote my comment for 32 bits, but it was Vartom's build what I tried... Then I edit my comment to O... I think I'll flash your ARM version tomorrow if Keep and Play Games are working. Thanks!

Edit: ARM working fine. Just in case, I deleted all com.google.android.* folders from /sdcard/Android/data/, Play Games are tricky the first time as you said... But it's working waiting some time.
[Nexus 9 Android Development] albsat:
Just curious. What is the advantage of 32bit vs 64 one in nexus 9? Better memory management due to the 2gb memory?
[Nexus 9 Android Development] USBhost:
Less memory footprint // apps use less memory overall

Plus my theory about finicky apps a few posts up

==========

Quick news update

I don't think I will be able to get gps working on 32 bit. unless someone can help me faking the GPS library into thinking it's 32bit so it can load. And those super old GPS binaries they need dependencies I don't know where to find.
[Nexus 9 Android Development] jolinnard:
Can you post which library is? And the old library would be great too. Maybe the 32 bits library could be ported from another device?
[Nexus 9 Android Development] USBhost:
well i did find the missing library (libstlport.so) however ...

it looks like the old is just too old... And i need gps working because my phone's one does not work.

10-21 23:06:14.077 1436 1436 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1436 (glgps)
10-21 23:06:14.133 1437 1437 F DEBUG : pid: 1436, tid: 1436, name: glgps >>> /system/bin/glgps <<<
10-21 23:06:19.188 1448 1448 F libc : CANNOT LINK EXECUTABLE "/system/bin/glgps": cannot locate symbol "_ZN7android9SingletonINS_13SensorManagerEE9sInstanceE" referenced by "/system/bin/glgps"...
[Nexus 9 Android Development] jungaxxx:
How can I install xposed on 7.1.2 32bit? Thanks
[Nexus 9 Android Development] USBhost:
Oreo 32bit no problem // no news yet

I believe so.
[Nexus 9 Android Development] USBhost:
Does LTE work on 32bit?
[Nexus 9 Android Development] jungaxxx:
I had this problem after flash xposed for arm v88.1
[Nexus 9 Android Development] USBhost:
I'll look into it.

Pro tip you don't have to reply to my last post.
[Nexus 9 Android Development] Vartom:
I think that hv video does not work and for the fact that Widevine does not work. In the logs there is no mention of its launch or use.

I want to try to port his library from the ryu.
[Nexus 9 Android Development] USBhost:
Isn't Widevine DRM? Why would that cause HW not to work? or i'm just overthinking it.
[Nexus 9 Android Development] Vartom:
Yes that's it. When I ported the blobs from the shield it was one of the problems with a HW decoder.

While the attempt to integrate Widevine from ryu was unsuccessful.
[Nexus 9 Android Development] USBhost:
Can you tell me the widevine libraries ?
[Nexus 9 Android Development] Vartom:
It looks like libwvm.so libwvdrm_L1.so and a few more files.
[Nexus 9 Android Development] albsat:
The latest conversation between usbhost and Vartom seems like rock music to me. :)
[Nexus 9 Android Development] USBhost:
I just hacked together linker64 with all the required libraries to run glgps. Since we are using a 64bit kernel we can run 64bit binaries. But the real problem I'm having is the hardware library for GPS. Because it's 64bit Android won't load it. However when I used the oldest binaries for the gps I got linking errors for pthread stuff. Then I use the newest arm GPS Hardware Library and the oldest 64bit glgps but Android would load it. However I got message errors in the logcat that gps could not communicate what not. Then I updated to the version that fixed those communication errors however now it wouldn't load our old GPS Hardware Library.

I have now given up on GPS. Unless we can figure out how to make Android load the 64bit HW gps Library.

If you want I can give you my linker64 and all the dependencies
[Nexus 9 Android Development] jolinnard:
Ok.... Yes, that's a (little) problem....

So, IDK if if could help you, but why not? Give me your linker and I can try to experiment with it and those libs. :good:
[Nexus 9 Android Development] USBhost:
lol at the name because it doesnt fix gps lol. well here you go :good:

good luck on your quest. note you will need to compile my rom without https://github.com/USBhost/android_...mmit/481abfea120d0c593ca65d3118847d42b5cf5e0b
[Nexus 9 Android Development] jolinnard:
Ok, building now. I had to fix couple of things: repo init is N, not master branch (repo init -u https://github.com/USBhost/My-AOSP-manifest.git -b N) and then in manifest I had to change android_device_htc_flounder to N32. Then I revert 481abfea120d0c593ca65d3118847d42b5cf5e0b in device/htc/flounder.

:fingers-crossed:
[Nexus 9 Android Development] USBhost:
Oh right I need update my manifest :silly:

I've been very lazy as of late... It must be because of school ;)
[Nexus 9 Android Development] albsat:
Please do not be lazy. :D Without your efforts, the hw will not be fixed oreo. :D
[Nexus 9 Android Development] didnt1able:
Bruh. Never tell someone not to be lazy unless you pay them. Like come on man
[Nexus 9 Android Development] Bryanx86:
I don't think it was a demand as much as it was a request. Probably misunderstood. I say be lazy. But not in school!
[Nexus 9 Android Development] albsat:
My sentence was a kind request with a bit of humor. That is why I put two smilies. :D. The developers should smile a bit.

Who are we to demand on the free work of the developers?

Personally, I appreciate the efforts of usbhost, very much on the Nexus 9.
[Nexus 9 Android Development] didnt1able:
I appologize
[Nexus 9 Android Development] albsat:
No worry man. ;) We are cool.
[Nexus 9 Android Development] jolinnard:
[MENTION=5501864]USBhost[/MENTION] I'm trying to understand how is implemented GPS in flounder, I see bcm47521 as a kernel module in many other devices, but in ours we have glgps and gps.bcm47521.so... You know if our chip is special? Can we switch GPS to a different implementation like Samsung does with all its devices with bcm47521?
[Nexus 9 Android Development] USBhost:
Hmm... good find! Hit me up with the latest device that has as a kernel module and i'll see what I can do.

On the other hand just an quick observation I found out messing around with the ramdisk. Is if you change the main zygote from app_process64 to app_process32 gps will no longer find any satellites in the normal ARM64 build. I found that out the hard way lol

OT: [MENTION=6876250]didnt1able[/MENTION] [MENTION=4413706]albsat[/MENTION] lol all was fine :good: and I want HW working too but im taking a break from it for a little.
[Nexus 9 Android Development] jolinnard:
Samsung Galaxy S4 could be an option (system and kernel are 32 bits).