I just followed the instructions on source.android.com for building Android from source. The build appeared to succeed, and it generated .img files which I fastbooted onto a device.
I started up the device, and got a black screen.
I can "adb shell" into the device and cd around and stuff, but nothing shows on the screen.
Usually, a black screen tells me something is wrong, but it's crossed my mind that maybe this time it's actually right, and the Android version one builds from source is a slim version without any of the bells and whistles, desktop with apps, browser, settings etc like the Android you get when you buy a phone.
My question: What normally shows on the screen when you build and run Android from source?
Related
I've been learning and working with Flutter for a few weeks now. I used some of the Android Emulators that Android Studio provides and it was doing fine.
But recently, I opened an emulator to run a Flutter project while a memory card was connected with my laptop, and suddenly a notification was shown in the emulator of detecting a SD card and with that another notification was shown saying:
Serial console enabled
Performance is impacted. To disable, check bootloader
The notification is not clickable, and neither it removes even after I deleted all the emulators that I installed using the AVD manager. And as the notification says, it really is impacting the performance of the emulators. Before it showed up, I could see the changes in the app immediately after making changes to the code and saving it, but now, it takes so much time to show the changes even if I use hot reload or hot restart.
Is there any way to get rid of this? How can I disable the Serial console?
Enter engineer mode (*#801#) and disable the option that says serial. Google it how to access engineer mode if the code doesn't work for you.
I have a Windows Store App that, of course, runs fine on my dev machine.
After creating the package to side load for testing, I installed it on another (desktop) machine. Using the instructions for side-loading contained on pages 25 and 26 of Brundritt's free ebook "Location Intelligence for Windows Store Apps", my app seems to install just fine, except that the app is not added to the Windows 8.1 start screen at the end, as expected.
Nevertheless, I can find the app via the Search functionality - I type the name, it shows up in the "found" list (with its logo), but when I try to run it, the splash screen simply "flashes" and then the app disappears. It icon is indeed parked on the taskbar, and every time I click it, the splash screen flashes, but that's all.
This is a Windows 8.1 app that contains a Bing Map, SQLite (and sqlite-net), as well as ExifLib.
It does show up in Task Manager's "App History" tab.
How can I rectify this problem, or at least determine what the problem might be?
UPDATE
This may (or may not be) significant: the version of the app I sideloaded was built in debug mode. Do I need to build in release mode for this to work?
Also: After building in release mode (for the first time) on the dev machine, it no longer finds the SQLite data that had formerly existed. Does changing from debug to release change the path to the database or something?
Does this help? http://blogs.msdn.com/b/vcblog/archive/2012/09/28/10354327.aspx It appears that the app needs to be built in release mode to work properly.
i'm new into programming for android. And i have few problems with connecting and debugging my eclipse project on android device - which is my phone Samsung Galaxy SIII. According to this link I tried to launch my app on my phone. Saddly when i press run button it tells me that there's no android device connected. And as you may know im not that dumm to not plug it into my computer. Additionally i have USB Debug mode ticked in options. My PC recognises it as "SAMSUNG Android ADB Device".
Some of you might say that i should start using emulator to have better view how this app will work on other phones/versions of android/etc. Thing is that my PC is quite old, and running an emulator makes it respond so slowly that it's nearly impossible to do anything on this emulated device. Plus... im quite sure that i wont publish this app on play store so i dont need to know if it will work on other devices. I just want to make a weather widget for me since stock one that uses accuweather.com tends to fail weather forecast for my country (like it says heavy rain on sunny day).
So here are the things that i have done so far to try to launch:
1. Uninstalled device and set some new drivers that should have helped me - saddly not ;]
2. Tried launching it via command line
3. I found somewhere on the Internet that it is possible to connect and test your app via WiFi using tcpip over 5555 port... saddly it failed too.
Any ideas what else should i try to make it work?
So, attempting to figure out if there was a way to use the arguments in the runtime config I ran across my biggest runtime boast yet, calling the Appcelerator build script for the Android Emulator from the command-line, here's what I mean:
<full-path-to-python.exe> <full-path-2-.../android/builder.py> emulator <project-name> <android-sdk> <project-dir> <project-id> <avd-name>
Example:
"C:\Program Files\Appcelerator\Titanium Studio\plugins\com.appcelerator.titanium.python.win32_1.0.0.1331647813\python\python.exe" "C:\Documents and Settings\user\Application Data\Titanium\mobilesdk\win32\2.0.1.GA2\android\builder.py" emulator JavaHomeBug "C:\Program Files\Android\android-sdk" "C:\Documents and Settings\username\My Documents\Titanium Studio Workspace\JavaHomeBug" tld.domain.JavaHomeBug titanium_1_HVGA
Are there any other ways to get the emulator to load faster, including but not limited not executing anything but the app?
This might not be exactly what your looking for but helps a lot with making changes and viewing them in the emulator.
Appcelerator implemented a festDev server. meaning that you can launch an app in the android emulator and leave it open, as you make changes to the code travel back through pages to make the page be reloaded and the new code will be pulled in.
For example going page 1 -> page 2,
then making a change on page 2,
click back button to go to page 1, now when go to page 2 you'll see your changes.
Takes a hige amount of time off waiting for the emulator to load up each time you change 1 or 2 lines
Solution: Why is Eclipse's Android Device Chooser not showing my Android device?
THis is getting annoying. My device shows up in eclipse on all
platforms.. Except when I am on my Ubuntu laptop.. when I "run
configurations" with it set to Manual.. I can see that there is an
Emmulator running that I can Install the App to.
Problem is, the Emulator is a pile of horse crap when it comes to
testing on real devices like my Samsung Captivate.
When the Captivate is plugged in via USB.. it shows via ICON, except
the ID is set to ??????????? and nothing else seems to be registering.
I can highlight it, but I can't launch it.
The captivate I am using is Rooted and running the LagFix Kernal..
However this has never hindered me on Windows or OSX.
Help.. I am trying to go completely Linux.. if it kills me.
See screenshot below: http://img265.imageshack.us/i/sdkbugeclipse.png/
UPDATE: Device is showing in the manager even when not connected?!?!
This has to be some weird Eclipse bug.. PLEASE HELP!
Solution (in case you missed my edit) need to add the correct Samsung Device ID when using the SDK with Ubuntu: link