Hi,
Have installed two different Pie ROMs on my Nexus 5, first crDroid and now Resurrection Remix.
I use my device extensively for app development, however I am encountering the same problem with both ROMs which suggests it might be an issue with Pie and the Nexus 5 in general. I didn't get the problem previously (was running LineageOS 14.1 on the Nexus 5, however I wanted to upgrade as that was no longer getting security updates).
When using Android Studio, it more often than not hangs at the 'Install' stage.
Similarly, using adb from the command line (adb install path/to/APK) also hangs.
Looking at Stack Overflow various fixes involving turning USB debugging off and on, or specifying auto-connect to debugger in the settings, are offered as a fix - in addition to the common Studio fixes of cleaning the project or invalidating the caches and restarting. None of the suggested fixes work reliably. Indeed, the fact that adb also hangs suggests it's an adb problem, not a Studio problem. FWIW my laptop os is Ubuntu (was 16.04, just upgraded to 18.04, same problem with each).
Anyone else using their device for development and encountering these problems? Any reliable solutions? Have a backup of the old Lineage install but don't really want to go back to that due to the lack of updates, and don't really want to buy a new device if I can help it... apart from this the Nexus is still working fine.
Thanks,
Nick
I'm still running Lineage 14.1 on my N5
Do you have the same issues with wireless ADB?
Related
Greetings everyone!
I author mobile applications using Titanium SDK + Titanium Studio for Android. This morning, while trying to compile the latest APK of one of my projects, I encountered an error from the console indicating that ADB can't see my device. Here is the error:*"[TRACE] adb devices returned 0 devices/emulators"
I wondered if it was an issue with Titanium itself, so I ran ADB directly from the terminal and ran the following command:
zettageeklatform-tools$ ./adb devices
This returned no devices in the list. I SHOULD be seeing a Nexus 7, as that is what is connected to the system right now. I've tried two different cables, and checked the Android settings to verify that USB debugging IS enabled.
The system used to develop the mobile applications is: Mac Mini (i5 / 8GB ram / Mac OS X V 10.7.5)
I'm using the latest Android SDK (adt-bundle-mac-x86_64.zip) available from the Android development website.
I've tried rebooting both the Mac, and the Nexus 7. I've also done a factory-reset on the Nexus 7, and re-enabled USB debugging from the settings. I'm still encoutering the same problems.
Note that this worked fine a few weeks ago, so I'm not sure what's changed. Any advice would be very much appreciated!
Thanks,
ZettaGeek
Try using PDAnet drivers. They mostly fix these problems.
ak700 said:
Try using PDAnet drivers. They mostly fix these problems.
Click to expand...
Click to collapse
I'll try this right now, and post my results shortly. Thanks for your help so far! I hope we can get this working... :fingers-crossed:
Hello,
I am trying to be able to use adb to send the app to my phone for development purposes. I have used eclipse and it worked with my phone, but recently I have switched to android studio. When I try to send my app to my phone, it says the phone is "not compatible". It works on my nexus 7. My phone is a note 2 on stock 4.3 verizon rom. I have usb debugging enabled/installer option on. How can I fix this issue. Also, it seems that this is not a common problem, I looked for it for a while and couldn't find anything that pertained to this issue. Thanks for any help.
Brian
I haven't seen that error before myself, but could the app be the problem? Are you sure it's compatible with your phone (min SDK version, required features, etc?)
It seems android studio adds some line of code that is not compatible with 4.3 if you select compile with 4.4. Anyway, I think I will use eclipse, as studio does not run properly with my phone, it runs into an error in when I try to run it. Thanks for your help though!
To install Sailfish OS you flash it over a CM or AOSP base. So a whole android rom is there unused when you're using Sailfish. So I thought why not make use of it, since Sailfish isn't using the android services like zygote, media, netd, or surfaceflinger they are disabled by default in init.rc, by re-enabling them and turning off Sailfish's Wayland Compositor and turning on Surfaceflinger I was able to boot into CM (for my device the Nexus 5, it's CM11) without input. Today I've finally managed to get input working by changing the usergroup of /dev/input/eventX from video to input. But although I'm able to navigate Android, and use the stock browser it's still quite unstable. Here is a logcat dump of the first few times I've booted into CM from Sailfish now that input is working, and I have no idea how to fix those errors.
If I connect to WiFi from Sailfish and then boot into CM then the Stock browser can use the internet connection and browse websites (although WiFi is off on Android), same goes for mobile data. But If I flash gapps and then try to login to my google account, Android doesn't see the internet connection and tries to make me connect again, at which point Surfaceflinger crashes and doesn't restart.
I made a basic guide of how to get to the same stage, if you would like to test it out once Sailfish is installed. So we can progress with the project.
Instructions of how to get to boot into CM from Sailfish OS
I found out that bluetooth is not always working in Bliss Roms. It can be solved by searching a Android x86 rom like 9.0 R2 that works good with bluetooth
And then upgrade to Bliss OS 11.1 by going to the advanced option and choose upgrade to Bliss OS 11.1 what normally not working with bluetooth if you just install Bliss OS 11.1
It seems that there is a connection between de Android x86 roms and the Bliss OS rom if they are the same version of android that can fix problems like wifi and bluetooth problems.
ServanSchreiber said:
I found out that bluetooth is not always working in Bliss Roms. It can be solved by searching a Android x86 rom like 9.0 R2 that works good with bluetooth
And then upgrade to Bliss OS 11.1 by going to the advanced option and choose upgrade to Bliss OS 11.1 what normally not working with bluetooth if you just install Bliss OS 11.1
It seems that there is a connection between de Android x86 roms and the Bliss OS rom if they are the same version of android that can fix problems like wifi and bluetooth problems.
Click to expand...
Click to collapse
Yo, this is probably the best advice/option I've heard regarding non-working WiFi/BT modules in Bliss OS to date. Seems no streamer/tutorial has covered this route to solve these hardware issues when installing the OS, specially on the latest versions. I'll definitely be trying this on my HP Stream 11 laptop which has a Realtek 8822be WiFi/BT module. Now just gotta figure out how to make a clean install iso of the latest Bliss OS with the drivers working.
hugoBOSS1981 said:
Yo, this is probably the best advice/option I've heard regarding non-working WiFi/BT modules in Bliss OS to date. Seems no streamer/tutorial has covered this route to solve these hardware issues when installing the OS, specially on the latest versions. I'll definitely be trying this on my HP Stream 11 laptop which has a Realtek 8822be WiFi/BT module. Now just gotta figure out how to make a clean install iso of the latest Bliss OS with the drivers working.
Click to expand...
Click to collapse
I don't get the
"going to the advanced option and choose upgrade" bit
the advanced option where, i've tried going from 9.0r2 installed and then booting a USB with bliss11 and there is not upgrade option, or am I just being thick.....(probably)
jonallwright said:
I don't get the
"going to the advanced option and choose upgrade" bit
the advanced option where, i've tried going from 9.0r2 installed and then booting a USB with bliss11 and there is not upgrade option, or am I just being thick.....(probably)
Click to expand...
Click to collapse
Upon usb boot and selecting the Bliss OS 11 iso from your USB, you should be greeted with several sub menu options. Amongst them, is the normal Bliss-os USB live option and several other debug options. At the bottom, there is a menu stating "Advanced options - >"; select it. On the next page to display there should be a few more boot options for "vulkan support, no setup wizard, and no hardware support". Next should be an option to upgrade or update Bliss-OS to the iso version you want (which you selected to boot from earlier). This will update the existing OS directory as if you did a fresh install in my experience using said option. I'd recommend saving a copy of your data.img file from your existing os's root directory so you can replace the fresh default data.img file with the one that has your apps and credentials for accounts, etc already on it. Otherwise you'll have to reconfigure the OS all over again and who wants that, right? The other option I'm aware of is the built in bliss updater utility within the system, but if you're on bliss os 11.13/14, it fails to connect to servers for updates to the OS to move up to 12, 14, or 15. In bliss os 14.3 though, I haven't had a chance to test it to see if it works as far as connecting to servers to update from within the OS to preserve your apps, accounts, etc.
Thanks for a comprehensive response, appreciate it
jonallwright said:
Thanks for a comprehensive response, appreciate it
Click to expand...
Click to collapse
No problem bud. I hate it when others do that to me when stuff like this is hella' technical to understand/follow and most of the time it's just some snarky comment telling you to look it up in the forum(s) or Google; yet a direct answer would be much faster and save everyone else time responding and such and the issue can be tagged as solved,
hi, i have managed to install BlissOS 11.13 (Android 9) with Windows Installer : https://docs.blissos.org/install-bliss-os/install-from-windows-uefi-esp-64-bit, combine it with grub2win and i got working dual-boot win11 and BlissOS without the need to usb boot or make ext4 partition separately. The BlissOS work awesome, the Wifi/Bluetooth working fine, but i loved the BlissOS 14, it's slightly faster in my device (Lenovo Ideapad D330). So i tried "upgrading" by following docs here : https://docs.blissos.org/install-bliss-os/updating-bliss-os-ag-builds. Again, the upgrade went success, until i try to turn on bluetooth, which is failed . Any clue how to resolve this?
hi, i have Ericsson f3507g mobile broadband hardware, how do i make it work in bliss os for call and internet connection. Thank you
So I installed Kali NetHunter to use the Wifite command. Long story short, I find out that I need an external wifi card for programs like Wifite to ACTUALLY run, so I find a tutorial to use Wifite WITHOUT a WiFi card. I installed Hijacker and went through the initial setup process (installing Nexmon). But then, I realised that I can no longer connect to any WiFi networks, despite my phone detecting them. I figured it had to do something with my management utility path for the Nexmon installation not existing at all (the default was /product/bin, which does not exist for my phone). So I reinstalled it, only this time setting the path as /system/bin). Still, it didn’t work. I fugured it has to do something with the bcmdhd_sta.bin file inside of the WiFi folder (/system/vendor/etc/wifi). No luck deleting it (I used amaze file manager). Can anyone pls help me, I just want my phone back, preferably without a hard reset. The device chipset that the Nexmon installation window is showing is 4339a0.
Details of my phone:
Samsung Galaxy Note 3 SM-9005
Android 11, running LineageOS 18.1