Nexus 7 LTE General Bugs/Problems & Workarounds
-
@tonoxis Sorry I cannot help with the external display. We are not configuring this somewhere I thin kbut just take the defaults from the driver. But other people might know better....
-
@flohack cool, thanks for the reply anyway though!.I'm trying to recompile the Android system image as Halium-7.1 but my system.img is too small, so I'm waiting on it to transfer to my PC for resizing.
Hopefully my current list, observations and efforts eventually provide some help for us to bring the Deb up to par with Flo.
-
Adding notes on my experiences here. I flashed the dev branch on my deb yesterday. Grabbed the boot image from here today and did:
# fastboot flash boot ./boot.img
Rebooted and working on setup steps here:
# sudo zramctl -s 2G
zramctl: no divice specified
# sudo zramctl --find -s 2G
/dev/zram0
# sudo start zram-touch
zram-touch stop/waiting
# anbox-tool installThis downloads a package, and then hangs. When I ctrl-c if after a while, the tracebach indicates it's in the waitForAnbox function, at time.sleep(1).
If I do anbox-tool disable, and then anbox-tool enable, it says 'start: Job failed to start' and hangs like before.
I'm going to have to try and get an external keyboard working so I can look for logs or something to see what's happening.
Thanks for all the work so far on flo and deb!
-
@a8ksh4 By chance are you using any Slimport cables? I'd like to have someone test that Slimport is still functioning in the current Dev branch as it had stopped after an update for me despite using the same kernel, which had more or less fixed Slimport previously after switching over to using the Flo kernel config instead of the Deb kernel config.
As for Anbox, that's definitely not typical, I wonder if something has changed in how it's supposed to be installed since I wrote those instructions. As I was able to install it, but have a hard time getting it running consistently.
One problem I noticed is that there seems to be a lack of firewall rules that are added, where the script anbox-bridge is supposed to handle them. It doesn't seem to function right on our devices and if you make the anbox-bridge script return true, it should get you past "Job failed to start". There's an old Anbox issue ticket that applies here: https://github.com/anbox/anbox/issues/443 and is linked to the ubports Anbox ticket: https://github.com/ubports/anbox/issues/42 both are applicable because even if Anbox starts properly, the firewall isn't initialized properly and thus anbox has no internet functionality.
-
is there a video tutorial to switch to flo? thanks in advance.
long live the free world -
@joao-0 There is not, I do not put out video tutorials. If you really want to run the Flo software, run the UBports installer and then follow the instructions for if your device wasn't detected and select the Flo. Of course, this means you'll lose LTE connectivity as the Flo image does not support it, for that, you need to Frankenstein the device with a Deb image and Flo kernel.
Because of how sensitive that proceedure is, I advise against YouTube tutorials due to many possibilities, however I'll use the most prominent one from another homebrew scene as my reason why I do not do videos, over in the Nintendo3DS homebrew scene, a dude bricked people's consoles because he uploaded a "One Size Fits All" package with a video, containing device specific files that wouldn't work when put into another console.
If you want a decent Deb experience, download the boot.img in my OP, fastboot up TWRP, and then install the boot.img into the boot partition using it. Reboot. Done.
If you are wanting to use this kernel with a Flo product, simply do the same things. Both Nexus 7 models use the same kernel anyway.
-
@tonoxis
Thank you for your reply.
I'm going to stay like this and forget the Bluetooth. I already tested flo by installer and it didn't work. Without video to test your img, it's too complicated...
Thanks anyway.Merci pour votre réponse.
Je vais rester comme ça et oublier le Bluetooth. J'ai déjà testé flo par l'installateur et cela n'a pas fonctionné. Sans vidéo pour tester votre img, c'est trop compliqué...
Merci quand même. -
@joao-0 Ah, if you've already done the Flo installation, then open a terminal and do
sudo start bluetooth-touch-floIf you want this working on every boot:
sudo mount -o remount,rw /
sudo cp /etc/init/bluetooth-touch-flo.conf /etc/init/bluetooth-touch-deb.confThis is because despite running a Flo kernel, the hardware still reports it's a deb, and the ubPorts image appears to be missing the upstart item for the deb, and is missing a redirect from bluetooth-touch to just use the flo version regardless.
-
@tonoxis
sorry I do not speak english.
UBPORTS_Software_ refuses_FLO_on my nexus 7.
Thanks anyway -
@joao-0
Use this website to translate : https://www.deepl.com/translator -
@keneda
hi
_translation_approximate_Thank you -
@joao-0
I don't use android anymore to avoid google, why the hell i would use google translate ?Plus translation with deepl was accurate every time i tested it.
-
@keneda
ok.
no worry. -
@joao-0 Apologies, wish I had a better way of helping you install it. If you've got my boot.img, and have TWRP on your device, you could always flash it that way.
Or you can boot to Fastboot/bootloader, and issue a
fastboot boot <path/to/boot.img>for temporary testing,
or
fastboot flash boot <path/to/boot.imgfor permanent installation
from a computer -
@tonoxis
A big thank you I managed to make the Bluetooth work with your boot.img
Long live the free world -
@tonoxis if you have any changes in your boot image that improve the device´s experience, please try to work with us in getting them into our default image. That could be nice!
thanks -
@flohack
yes no problem, how can I help? -
@joao-0 can you PM me on Telegram @Flohack ?
-
@flohack I just created my account.
note:. I don't speak English and I live in France with jet lag, it's not going to be easy...
Sincerely Joao -
@joao-0
You're not the only french here ^^
I believe @Flohack lives in Germany, so "jet lag" should not be a problem.