If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#31
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
Arlen_Holder
news alt.comp.freeware, wrote: On Sat, 3 Nov 2018 02:00:32 -0000 (UTC), Diesel wrote: It's not really a trick Arlen. There's a bug of sorts. I haven't isolated it to a specific package. Thanks for the help where I spent a few hours on the problem today. I made no progress, where the current status is the same as before It shouldn't have taken you a few hours to do what I suggested, previously. It turns out very many people have the issue I'm having which is simply that Android Studio won't send the app to the Microsoft Android Emulator. Yes, it's a common and known issue. As is the suggested fix I provided for you, which works most of the time, when properly followed. I'm not surprised to see that you didn't follow it to the letter as I previously wrote for you to be doing... A key problem that is critical to keep in mind for anyone trying to solve this is that there are Intel & AMD CPUs out there. Wow. Really? It's not a key problem though. o Any solution for Intel CPUs does _not_ apply to AMD CPUs. o Any solution for AMD CPUs does _not_ apply to Intel CPUs. Obviously this is not accurate. The possibly working solution (as I said, this works the majority of the time, pending no serious corruption issues with the SDK installation) I presented to you already doesn't care what CPU you're using. This is a key distinction because _most_ of the solutions are Intel only. Hence, if a solution doesn't list AMD, by name, that solution is worthless. I really don't know where you get this information from...The solutions you're writing about have to do with tweaking the emulation/stabilizing it, etc. Not getting it initially up and going with your application on it. Readers would be well advised to ignore the 'advice' you've provided on this subject at this point, Arlen... As far as I know, I meet the requirements, but Android Studio 3.2.1 is still not sending the java files to execute on the Microsoft Android Emulator yet. Nope, it's not. You did not follow the instructions I provided you. I don't know what you spent hours doing, exactly, but it sure as hell wasn't doing what I wrote for you to do... I also added "adb" (which is in the SDK) to the path and I added the registry key which is supposedly what the Microsoft Android Emulator is hard coded to, but neither worked any better than nothing. adb being added to the path is more for your convenience than much else. The actual issue is the newly created, but, incomplete registry key. It's incomplete because you (a) didn't follow my instructions and (b) are too arrogant to ask for clarification or further help with that. You just made assumptions and rolled with them. Which, clearly, didn't give you the results you were hoping for. 8. The developers of the MS Android Emulator store this hard-coded path to the Android SDK in the Windows registry: It's not a hard coded path if you can change it, Arlen... [g] Start Run regedit 9. This key is "supposed" to exist, but it doesn't exist for me: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools\ 10. What exists for me is only: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ 11. So I created this key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools\ 12. And set its string value to: C:\app\hardware\android\sdk Did you actually set Android SDK Tools 'string value' to 'C:\app \hardware\android\sdk'? So you glanced over this part of my instructions then? *** begin copy If the key had to be created , be sure you create the string variable, Path and input the information above. Close regedit. Obviously by information above, I specifically mean the location to where Android SDK installed by default. *** end copy Not only did I specifically tell you to reinstall the programs using their default settings, I also provided very specific instructions concerning the creation of the key as well as a very specific piece of it, if it wasn't already present on your machine. You clearly didn't follow through with all of the instructions. Despite them being present... The question is which to add to the path? c:\app\hardware\android\sdk or c:\app\hardware\android\sdk\platform-tools add to the path? I didn't tell you to add anything to the path, Arlen... MID: Open regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools If you don't have this key, create it-- That means, add the key 'Android SDK Tools' under Wow6432Node as you see above. Under the key if it already exists is a string variable called Path. edit it to point to the location of your Android SDK Installation. Example: C:\Program Files (x86)\Android\android-sdk (If you haven't mucked with the default installs, that example *should* be what you need to add. Verify for yourself, though. If the key had to be created , be sure you create the string variable, Path and input the information above. Close regedit. Obviously by information above, I specifically mean the location to where Android SDK installed by default. *** end snippit I don't know where you got PATH= out of what I wrote to you...I specifically wrote 'string variable' which needs to be named, Path and set to the installation folder for the SDK; which would be default, had you done what I wrote for you to do, to the letter, as I told you to do. There was a specific reason I wrote for you to do it as I wrote it to be done, Arlen. Are you ****ing playing games with me, Arlen, or do we have a communications issue of some kind going on here? I suppose it could be both at this point... One last time, either follow the instructions as I wrote them to the ****ing letter Arlen, or I leave you to **** in the wind on this one too. Go back and re-read my post. Follow the instructions, to the ****ing letter, every single one of them. Report back your results. The following url will provide you with most of the post I already wrote (that you skipped and partially ignored) containing the instructions that most likely will get the emulator up and going for you. That is, if you follow them all. http://al.howardknight.net/msgid.cgi?ID=154132021900 Last chance, Arlen, then I'm done wasting time on your dumb ass. Unless you can demonstrate in the future that you can read and understand what you're reading by following the ****ing directions, i'm going to refer to you as a dumb ass. It's not a simple matter of a single ****up on your part, this is the second easily shown one in a matter of days; you clearly don't understand what you read and make poor decisions based on what you thought you read, rather than ask for clarification or further assistance. Those are two classic ear marks of a dumb ass. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit he https://tekrider.net/pages/david-brooks-stalker.php ================================================== = Nobody expects the Spanish Inquisition! |
Ads |
#32
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
Arlen_Holder
news alt.comp.freeware, wrote: Where I can't get the Microsoft Android Emulator to show up in the choices! o http://www.bild.me/bild.php?file=2685733androidstudio12.jpg Covered in another reply. Long and short of it is though, because you're a dumbass. You're a dumbass because you didn't follow directions, obviously didn't understand the directions as written and didn't seek additional clarification or assistance before attempting (and failing) to act on them. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit he https://tekrider.net/pages/david-brooks-stalker.php ================================================== = The wife suggested I get myself one of those penis enlargers, so I did. She's 21, and her name's Kathy. |
#33
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
Bill
Sat, 03 Nov 2018 11:56:09 GMT in alt.comp.freeware, wrote: This is all very well, but a search shows 244 usenet groups with "programming" in the name and none with any combination of "programming" and "java". A recommendation of a specific programming group would be a great help. I think you'll find leaving out the word programming and searching for java (not javascript .js; different creatures) would yield far better results. The other thing I would like to comment on is the use or need to stick to the specific default directory setup with Android Studio. I wanted to be able to locate and understand the various elements of the IDE and the program. The whole point of doing this is to learn and having elements in "phantom" directories is not helpful. If something IDE based doesn't work, it is usually fairly simple to detect where something is looking and revert to defaults if necessary. A release version of any program should be able to be installed where the user wants or should clearly state, or define , where it must be installed. For experienced users, that's fine. Arlen isn't what I consider an experienced or very knowledgeable user (Despite their claims to the contrary), so, for the purposes of troubleshooting (and making my life easier in the process), it's best that they allow the default settings along with default suggested install folders to be used. Once (if they can leave their attitude and arrogance at the door and do what I tell them, specifically to do) we get it up and going, they are more than welcome to reinstall it any place they like, assuming all previously mentioned risks by doing so. I do appreciate any help and discussion here. I try to help when possible, time permitting, those who aren't complete assholes towards me for no valid reason. Arlen for whatever reason, is one of the latter. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit he https://tekrider.net/pages/david-brooks-stalker.php ================================================== = Hard work never hurt anyone, but then neither did a whole lot of good rest. --Richard Arthur Hassell |
#34
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Sun, 4 Nov 2018 08:46:02 -0000 (UTC), Diesel wrote:
You're a dumbass because you didn't follow directions, obviously didn't understand the directions as written and didn't seek additional clarification or assistance before attempting (and failing) to act on them. I openly admit I am only of average intelligence (if that), where I concede easily that I still haven't gotten the java code to work on an Android emulator on the Windows AMD-based desktop. Moving forward on that problem, it seems that Microsoft may have induced Google to attempt to fix their hardware acceleration bugs on AMD-based Widnows desktops. It appears that Microsoft implies the following sequence of events: http://www.bild.me/bild.php?file=5287229emulation01.jpg a. Google (apparently) didn't support hardware acceleration on Windows b. So Microsoft built an Android Emulator that did work on Windows c. Some time thereafter, Google responded by fixing their bugs At least that's implied when you read the orange header he https://visualstudio.microsoft.com/vs/msft-android-emulator/ "Note: After we released the Visual Studio Emulator for Android, Google updated their Android emaulator to use hardware acceleration. [Hence] We recommend you use Google's emulator when you can, as it offers access to the latest Android OS images and Google Play services. If you have enabled Hyper-V, try out our Hyper-V Android emulator compatibility preview to run Google's emulator on Hyper-V directly" https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows The good news is that this implies that Google's Android emulator "should" work with hardware acceleration on Windows PCs, where I've learned the hard way that Intel-based Windows PCs are far better supported for hardware acceleration than are AMD-based Windows PCs. It turns out that any reference that does not mention AMD is worthless when it comes to getting an AMD-based Windows desktop to work with emulation. The good news is that the reference above _does_ mention AMD, so it's at least useful for those of us on the lowly AMD-based Windows desktops. |
#35
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Mon, 5 Nov 2018 17:04:01 -0000 (UTC), Arlen_Holder wrote:
The good news is that the reference above _does_ mention AMD, so it's at least useful for those of us on the lowly AMD-based Windows desktops. This is a classic Windows hardware acceleration setup problem, I think. The problem is emulation hardware acceleration on Windows, since the java code works perfectly on the phone itself when sent over from Windows: http://www.bild.me/bild.php?file=2596267androidstudio06.jpg What complicates things is that any reference that talks about emulation and/or acceleration without mentioning AMD, is utterly worthless for debugging on AMD-based Windows desktops because HAXM just won't fly: http://www.bild.me/bild.php?file=4100603androidstudio07.jpg Even though I was sure that Hyper-V was enabled on Windows 10 Pro based on the output from the Windows "System Information" dialog box: Start Run %windir%\system32\msinfo32.exe It seems that Windows 10 was reporting false information: http://www.bild.me/bild.php?file=1288358androidstudio08.jpg I was also sure that Hyper-V was working based on the output from the AMD-supplied AMD-based Windows Hyper-V checking tool: http://download.amd.com/techdownloads/AMD-VwithRVI_Hyper-V_CompatibilityUtility.zip Which (erroneously?) reported that all was well with Hyper-V: http://www.bild.me/bild.php?file=8692170androidstudio09.jpg And yet, there were hardware-acceleration errors when sending *.java code from Android Studio to the Microsoft Android Emulator on an AMD desktop: http://www.bild.me/bild.php?file=7953529androidstudio10.jpg However, it seems I missed a step in enabling Hyper-V on Windows 10 Pro: https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows Which recommended first that we run the Windows winver command: Start Run winver http://www.bild.me/bild.php?file=9332564androidstudio20.jpg And then we run the far-more-detailed systeminfo command: C: systeminfo c:\tmp\systeminfo.txt Should show Hyper-V (& Windows Version 1803 to at least OS Build 17134.1). And then which suggested we run the Windows "OptionalFeatures" command: C:\Windows\System32\OptionalFeatures.exe In order to ensure that Windows is set to: Enable both Hyper-V and Windows Hypervisor Platform: Where my first results were, astoundingly, after all this, as follows: http://www.bild.me/bild.php?file=9981202androidstudio18.jpg *Now how did _that_ happen, even after the AMD & Windows checks?* Moving on, obviously I checked that "Windows Hypervisor Platform" box! http://www.bild.me/bild.php?file=9740339androidstudio19.jpg and rebooted. *That checkbox made a _huge_ difference in Windows hardware acceleration!* The result was that, back in Android Studio 3.2.1, for the first time, the default Google Android Emulator finally pops up for the very first time! http://www.bild.me/bild.php?file=1034642androidstudio23.jpg But it is blank and unresponsive, where Android Studio displays a completely different set of errors that were not seen prior: Emulator: Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release. Emulator: emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3 Emulator: Hardware-accelerated emulation may not work properly! |
#36
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Mon, 5 Nov 2018 18:32:27 -0000 (UTC), Arlen_Holder wrote:
Emulator: Hardware-accelerated emulation may not work properly! Regarding these errors: Emulator: Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release. Emulator: emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3 Emulator: Hardware-accelerated emulation may not work properly! These "EPT" & "UG" & "SSSE3" features seem to indicate: o EPT = Extended Page Tables (aka SLAT second level address translation) o UG = Unrestricted Guest (aka "real mode") O SSSE3 = Supplemental Streaming SIMD Extensions 3 (cpu instructions) https://en.wikipedia.org/wiki/SSSE3 Windows PowerShell will report your processor family: PowerShell gwmi win32_processor The Sysinternals "coreinfo" tool tells us which features exist in a CPU https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo Sysinternals coreinfo output shows either an asterisk or a dash where "*" means the feature is present "-" means it is missing https://social.technet.microsoft.com/wiki/contents/articles/1401.hyper-v-list-of-slat-capable-cpus-for-hosts.aspx This tells me EPT (aka SLAT) is not supported on my CPU: C:\ coreinfo -v HYPERVISOR * Hypervisor is present SVM - Supports AMD hardware-assisted virtualization NP - Supports AMD nested page tables (SLAT) Wikipedia says my AMD FPU supports SSE3 but not SSSE3 & coreinfo concurs: C:\ coreinfo | findstr "SSSE3" SSSE3 - Supports Supplemental SIMD Extensions 3 So I may have to give up getting Android emulation to work on my AMD CPU, but there's one more test I can run, I think, which is to use an ARM CPU: https://youtu.be/OjD9t1bfYsY?t=193 Where the guy says we can "just click on the ARM processor". |
#37
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Mon, 5 Nov 2018 20:47:48 -0000 (UTC), Arlen_Holder wrote:
So I may have to give up getting Android emulation to work on my AMD CPU, but there's one more test I can run, I think, which is to use an ARM CPU: https://youtu.be/OjD9t1bfYsY?t=193 Where the guy says we can "just click on the ARM processor" Solved ... sort of. I'm not sure exactly how I solved it since I tried many things, but here's the current status (which has a few glitches remaining) and where I'm not sure which "trick" is what made it finally work. o I think it was the "Windows Hypervisor Platform" checkbox FROM: http://www.bild.me/bild.php?file=9981202androidstudio18.jpg TO: http://www.bild.me/bild.php?file=9740339androidstudio19.jpg o Also changing the Google emulator to run on ARM instead of X86 http://www.bild.me/bild.php?file=2999468androidstudio24.jpg These are the three devices I currently tried to emulate: http://www.bild.me/bild.php?file=7607398androidstudio31.jpg o Rounded corners: Nexus S API 25 ARM (Android 7.1.1, API 25) o Squarish corners: Nexus 5X API 25 ARM (Android 7.1.1, API 25) o Bottom Right: MS Android Emulator x86 (Android 5.1.1, API 22) http://www.bild.me/bild.php?file=3093498androidstudio30.jpg One issue with ARM over X86 emulation is that ARM is 10x slower: http://www.bild.me/bild.php?file=2999468androidstudio24.jpg The Microsoft emulator (right) was, by far, _faster than Google_: http://www.bild.me/bild.php?file=4854975androidstudio25.jpg But, eventually, all three emulators (Google, ARM, & MS) came up: http://www.bild.me/bild.php?file=6567987androidstudio26.jpg All 3 had some issues with Android OS apps pre-installed on them. http://www.bild.me/bild.php?file=8587828androidstudio27.jpg But all three were invoked by the IDE; where only 1 ran the app: http://www.bild.me/bild.php?file=1405186androidstudio28.jpg It's preliminary to confirm that it's working, but my tentative recommendation is to run the Microsoft Emulator choosing x86 instead of running the Google emulators on x86 or ARM. http://www.bild.me/bild.php?file=7301488androidstudio29.jpg Since this problem is extremely common on AMD Windows machines, I found a lot of "guesses", many of which I tried, where I "think" the two that finally worked, sort of, we 1. Running the Google emulators as ARM (not x86) enabled the Android Studio IDE to invoke them and for them to populate their operating system - but - the Android IDE "adb" command did not send the APK to run on the emulated Nexus devices. 2. Running the Microsoft emulator as x86 worked almost perfectly, in that it was more than 10 times faster than the Google emulations running as ARM, and better yet, the Android Studio IDE "adb" was able to send the "Hello World" APK to the Microsoft emulator, where the only minor glitch was that there were apps that had to be stopped in the background for some reason. My tentative recommendation for AMD Windows users is: o You can run the Google emulators as ARM (but not x86) o But it's better to run the Microsoft emulator & as x86. |
#38
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Sat, 3 Nov 2018 02:00:34 -0000 (UTC), Diesel wrote:
I didn't run across any horrors with the process. Hi Diesel, Thank you for all your help and kind advice. If you dual-booted to Linux to plug in the iOS iPad via USB without iTunes, the task that takes technical knowledge is knowing how to _write_ to the entire visible file system of the non-jailbroken iPad over USB without iTunes from Linux or Windows, which includes the critically important _DCIM_ directory tree of the non-jailbroken iOS iPad. Keep in mind what I said above entails technical detail of... 1. No jailbreak 2. No iTunes 3. Write access to the entire visible iOS file system For example, *write access to the /DCIM/APPLE101/ folder!* 4. Over USB I'm not a mac person either and didn't run into any serious issues with that. It's binary: a. People either can write to the visible file system, or they can not; b. If they can not, then they don't understand what I'm talking about. A simple yes:no litmus test is: a. Can people write to the DCIM hierarchy of the iOS iPad or not? b. If they can't, then they don't comprehend what I'm explaining. That may actually have something to do with your completely unnecessary desire not to use default installation folders. This post shows that the paths were a red-herring guess: https://groups.google.com/d/msg/comp.mobile.android/aW64zYeBtF0/PDMW1--EBAAJ |
#39
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Sun, 4 Nov 2018 08:46:02 -0000 (UTC), Diesel wrote:
it's best that they allow the default settings along with default suggested install folders to be used. Hi Diesel, Thank you for your help & kind advice about paths & programming. Part of debugging is understanding where problems lie in complex systems. The task is to be logically consistent. Since it was clear that _everyone_ with older AMD CPUs on Windows was having the _same_ errors with the Google emulators set to x86 (but not arm) that I was getting, simple logic rules out the specific paths that I used. It's no different than organizing your tools in your garage at home. It's always logically consistent! You don't let the Home Depot guy organize your tools in your toolbox. He would put all the Home Depot tools in one drawer, called "Home Depot". You don't let the Lowes tool guy organize your tools in your toolbox. He would put all the Lowes tools in one drawer, called "Lowes". IMHO, people should organize their tools to be logically consistent. Their tools should be organized the way they think. I happen to think of tools in terms of "functionality". I organize my tools by what they "do". For example, these new "things" needed places to go: 1. JDKs & JREs (e.g., Oracle Java development kits & runtime environments) 2. SDKs (e.g., the Google Android SDK at various API levels) 3. Emulators (e.g., Google, Genymotion, & Microsoft Android emulators) 4. IDE's (e.g., Google & Microsoft & Eclipse development environments) 5. CPU tools (e.g., Intel HAXM & AMD Hyper-V debugging tools) 6. Project files (e.g., APK hierarchies) 7. Tutorial files (e.g., videos) Just like you put your tools in your garage tool boxes where you can find them (which is likely not in the same place your wife would leave them), I can't tell you where to put your tools. However, I can tell you that each of these tools, if you let it default, will go in a completely different location than the other tools. To keep control over where things go, I put them _all_ in logical places! A. I put the tools in C:\app\editor\android (I never use plurals) B. I put my projects in C:\tmp\android (I use short names when possible) That's it. Whenever I need to *find* something, it's either a tool (which is in a single tool directory) or it's my temporary files (which are in a single project directory). For example on tools, both the Android IDE & the Microsoft IDE are in: C:\app\editor\android\ide\{android_studio,visual_s tudio} Note that the installers follow the same logical hierarchy: C:\software\editor\android\ide\{android_studio,vis ual_studio} Note that the menus follow the same logical hierarchy: Start Menu editor android ide {android_studio,visual_studio} The same logical consistency carries over to all the components. It's all very well thought out, and very logical, and, it carries over from one machine to another, such that the menus from Windows XP work perfectly when literally copied over to Windows 10, for example. I'm logically consistent where I organize my tools by what they do. |
#40
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Sat, 3 Nov 2018 11:56:09 +0000, Bill wrote:
The other thing I would like to comment on is the use or need to stick to the specific default directory setup with Android Studio. Hi Bill, I apologize for going "dark" as I tried to solve the emulation problems, where I was successful with emulation. http://www.bild.me/bild.php?file=7301488androidstudio29.jpg I now can offer noob Android users 20:20 hindsight of the following: 1. If you're on older AMD CPUs on Windows - don't even think of emulation! 2. If you must emulate, don't use the Google emulators (arm or x86)! 3. The best emulator, for older AMD, is the Microsoft Android Emulator. With this 20:20 hindsight, I don't recommend bothering with emulation. Nor do I recommend bothering with text tutorials after the first "hello world" works using the Google tutorial you and I both used, Bill. With 20/20 hindsight, I recommend people start with a good video tutorial. I haven't chosen the best video tutorial yet, but this one is pretty good: https://youtu.be/dFlPARW5IX8 (Bill Butterfield, an adder app) Given that it's human nature for each tutorial writer to name their apps in a way that makes sense to them, my 20/20 hindsight advice to you and any other noob writing their first Android apps, is to name the first app "app01" and to name the second app "app02" and to name the third app "app03", etc. That way they organize themselves consistently as you jump around from tutorial to tutorial. In 20/20 hindsight, I also recommend you choose a consistent *short* company name, e.g., I'm now using "kiss" as the company name, as all the apps will have that same company name for consistency. While I break down my installed programs into categories, I haven't seen the need (yet) to break down the projects into categories, so all my projects fit nicely into c:\tmp\android\{app01,app02,app03,etc.} In stark contrast, my installers are saved in the following hierarchies: 1. JDKs 2. SDKs 3. EMUs 4. IDEs 5. CPUs 6. APKs 7. VIDs For example, 1. The java jdk/jre is saved to C:\software\editor\android\jdk\oracle\. 2. The Android SDK is saved to C:\software\editor\android\sdk\google\. 3. The MS emulator is saved to C:\software\editor\android\emu\microsoft\. 4. The IDE is saved to c:\software\editor\android\ide\android_studio\. 5. The HAXM software is saved to C:\software\editor\android\cpu\haxm\. 6. The final APKs are copied to C:\software\editor\android\apk\app01\. 7. Downloaded videos are saved to C:\software\editor\android\vid\bradsaw\. etc. Of course, none of this did I know _before_ I started, where I'm learning where things logically fit only with 20:20 hindsight. I just now deleted the entire setup, and started over because I had installed so many hacks that I wanted to start with a clean slate. When you try to wipe out everything, you find stuff in the strangest places though, Bill, so take note of some of these strange locations... o %USERPROFILE%\appData\Local\Android o %USERPROFILE%)\.android\ (I'm not sure why stuff was put here) o %USERPROFILE%)\.AndroidStudio3.2\ (I'm not sure why stuff is here either) o %USERPROFILE%)\.gradle\ (I'm not sure why stuff is here either) o %USERPROFILE%)\.m2\ (I'm not sure why stuff is here either) o %APPDATA%\JetBrains\ (where did that come from?) o C:\Program Files\Android\ o %LOCALAPPDATA%\Android\ o %USERPROFILE%\AndroidStudioProjects etc. In summary, I think the perfect place for noobs to share how they got their first few Android apps working using Windows freeware is exactly these newsgroups. The hope is that scores of people will follow in our footsteps, benefiting from our now 20:20 hindsight! Certainly I _wish_ I knew a week ago what I know now about choices to be made when a noob decides to code their first few Android apps using Windows freeware on older desktops. |
#41
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Sun, 4 Nov 2018 08:46:01 -0000 (UTC), Diesel wrote:
Open regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools Hi Diesel, Thanks for your help and advice as I admit I'm an Android noob. I just snapped this snapshot for you so you can see what I have: http://www.bild.me/bild.php?file=3834577androidstudio32.jpg Maybe Bill can tell us what his registry key looks like, since he has the same tools installed. |
#42
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Tue, 6 Nov 2018 02:56:46 -0000 (UTC), Arlen_Holder wrote:
Given that it's human nature for each tutorial writer to name their apps in a way that makes sense to them, my 20/20 hindsight advice to you and any other noob writing their first Android apps, is to name the first app "app01" and to name the second app "app02" and to name the third app "app03", etc. That way they organize themselves consistently as you jump around from tutorial to tutorial. In addition to long apnames truncating to gibberish on the Android homescreen, but in the beginning, all our noob apps have exactly the same homescreen icon! That's why I suggest we noobs name them app01, app02, app03, etc. Using that naming convention, we noobs can logically fit a hundred noob apps on your Android homescreen, if we name them accordingly... o app01 === hello world o app02 === hello world with actions o app03 === a simple adder o app04 === a simple adder that has multiple screens o app05 === a simple 10-minute timer etc. This, I learned in hindsight that I share with other noobs, who are only a few days behind us, Bill, in their Android app-writing endeavors. |
#43
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
On Fri, 2 Nov 2018 08:03:32 -0000 (UTC), Diesel wrote:
Just passing along some friendly intended advice. Woo hoo! *EVERYTHING WORKED PERFECTLY!* Thank you Diesel for all your friendly helpful advice. I deleted everything & started fresh with my 20:20 hindsight experience! Only one Windows freeware package is needed on newer Intel & AMD CPUs: a. Android Studio freware Only two Windows freeware packages are needed on old AMD CPUs a. Android Studio freware b. Microsoft Emulator freeware Once I figured out the tricks, everything worked flawlessly! o The Microsoft Emulator freeware popped up without any errors: http://www.bild.me/bild.php?file=9766951androidstudio33.jpg o And the Android Studio IDE freeware ran on that emulator sans errors: http://www.bild.me/bild.php?file=8780131androidstudio34.jpg The result is that any apps we write using this Windows freeware... o Can run in the Samsung Galaxy S5 emulation on Windows, or, o They can run directly on my LG Stylo 3 Plus phone over USB. Given my new 20:20 hindsight experience, the solution is this simple! 0. You enable Hyper-V & Hypervision in the BIOS & in Windows 1. You install the Android Studio IDE (which installs the SDK & the JDK) 2. You install the Microsoft Emulator (if you're on an old AMD CPU) 3. You configure the MS Emulator in the Android Studio IDE (I configured it for Android 7.0, API 24, x86 Samsung Galaxy S5) 4. You start the MS Emulator from within the IDE & run the Hello World app! Voila! With experience of 20:20 hindsight, even on old AMD CPUs, it's that easy! |
#44
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
Arlen_Holder
news alt.comp.freeware, wrote: On Sun, 4 Nov 2018 08:46:02 -0000 (UTC), Diesel wrote: it's best that they allow the default settings along with default suggested install folders to be used. Hi Diesel, Thank you for your help & kind advice about paths & programming. Part of debugging is understanding where problems lie in complex systems. I'm well aware of what debugging entails... The task is to be logically consistent. Since it was clear that _everyone_ with older AMD CPUs on Windows was having the _same_ errors with the Google emulators set to x86 (but not arm) that I was getting, simple logic rules out the specific paths that I used. No, everyone wasn't...You were, some others were based on forum reading I did, but, not everyone. Some people (not you) understand what the software package is and what it's hardware conditions are for use and configured their systems for it. You did not, I suspect some of them didn't either. It's no different than organizing your tools in your garage at home. It's always logically consistent! Sadly, I've been in more than one or two homes where that isn't the case... You don't let the Home Depot guy organize your tools in your toolbox. He would put all the Home Depot tools in one drawer, called "Home Depot". You don't let the Lowes tool guy organize your tools in your toolbox. He would put all the Lowes tools in one drawer, called "Lowes". I'd hope not. I'd fully expect screwdrivers not to be in the same place as my hammers, etc. IMHO, people should organize their tools to be logically consistent. Their tools should be organized the way they think. Logically consistent != 'organized the way they (a person) thinks'. People don't typically think in a purely logical manner. To keep control over where things go, I put them _all_ in logical places! A. I put the tools in C:\app\editor\android (I never use plurals) B. I put my projects in C:\tmp\android (I use short names when possible) That's it. This methodology worked better on systems of the past, before the OS itself became a complex beast in it's own right... For example on tools, both the Android IDE & the Microsoft IDE are in: C:\app\editor\android\ide\{android_studio,visual_s tudio} Non default install paths, invalid registry key(s) pointing to wrong location; forcing programs which either expect the default install path or a properly configured key to point them to it will either fail to find required support files, or be forced to search for them on it's own. As you've been told before and completely chose to ignore, You don't make the decisions concerning how most things are laid out on your system. Note that the installers follow the same logical hierarchy: C:\software\editor\android\ide\{android_studio,vis ual_studio} Note that the menus follow the same logical hierarchy: Start Menu editor android ide {android_studio,visual_studio} The menus hide the details behind the scenes and provide you with an icon to click. For graphical representation, it can be as simple and as 'logical' as you want it to appear to be. The same logical consistency carries over to all the components. Yes, but, not in the way you think. It's logical from the point of view of the developers, not what you personally think. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit he https://tekrider.net/pages/david-brooks-stalker.php ================================================== = System error 4C: kernel panic |
#45
|
|||
|
|||
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
Arlen_Holder
news alt.comp.freeware, wrote: On Sat, 3 Nov 2018 02:00:34 -0000 (UTC), Diesel wrote: I didn't run across any horrors with the process. Hi Diesel, Thank you for all your help and kind advice. If you dual-booted to Linux to plug in the iOS iPad via USB without iTunes, I don't dual boot. the task that takes technical knowledge is knowing how to _write_ to the entire visible file system of the non-jailbroken iPad over USB without iTunes from Linux or Windows, which includes the critically important _DCIM_ directory tree of the non-jailbroken iOS iPad. I couldn't help but notice you now specifically use the words, 'visible' file system; instead of full access as you previously (yet incorrectly) assumed that 3rd party driver you thought only you knew about (hahaha) gave you. Keep in mind what I said above entails technical detail of... 1. No jailbreak 2. No iTunes 3. Write access to the entire visible iOS file system For example, *write access to the /DCIM/APPLE101/ folder!* 4. Over USB Ayep... I'm not a mac person either and didn't run into any serious issues with that. It's binary: a. People either can write to the visible file system, or they can not; b. If they can not, then they don't understand what I'm talking about. I do question why what I recently wrote, that you're quoting, has to do with writing to iOS file system via 3rd party software? This post shows that the paths were a red-herring guess: Erm, no, it doesn't. It shows me that you don't comprehend basic registry activities and don't want to discuss where and how you ****ed up very simple instructions left for you. I do understand why you'd prefer to dodge that, being the logical person you are. [g] I just don't have time to continue doing this with you, Arlen. You're wasting my time. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit he https://tekrider.net/pages/david-brooks-stalker.php ================================================== = Cats must lurk under the bed and pounce on the unsuspecting human's feet. |
Thread Tools | |
Display Modes | |
|
|