I have reason to believe that the G4 is running on 32 bit due to this finding.
" The first ARMv8-A SoC from Samsung is the Exynos 5433 in the Galaxy Note 4, which features two clusters of four Cortex-A57 and Cortex-A53 cores in a big.LITTLE configuration; but it will run only in AArch32 mode"
The G4's snapdragon 808 has the same cluster setup as the note 4's.
So installing the 32bit Xposed will work? That would be AWESOME. Must have SnapPrefs lol.
Lol glad to know core layout determines the os
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
IlyaKol said:
So installing the 32bit Xposed will work? That would be AWESOME. Must have SnapPrefs lol.
Click to expand...
Click to collapse
Yeah don't install 32bit xposed
LancerV said:
Lol glad to know core layout determines the os
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Yeah don't install 32bit xposed
Click to expand...
Click to collapse
I'm confused. If the G4 is build on 32-bit AArch32 then wouldn't we WANT to install 32-bit Xposed and NOT 64-bit XPosed?
Zygote is what runs android applications every 64bit runs both 64bit and 32bit
Zygote64 means it has a 64bit kernel, zygote64 runs 64 apps zygote runs 32bit
LancerV said:
Zygote is what runs android applications every 64bit runs both 64bit and 32bit
Zygote64 means it has a 64bit kernel, zygote64 runs 64 apps zygote runs 32bit
Click to expand...
Click to collapse
Ahh okay. Similar to having C:\Program Files (x86) (32-bit apps) and C:\Program Files (64-bit apps) on a 64-bit Windows machine. Understood.
Thanks for the clarification.
IlyaKol said:
Ahh okay. Similar to having C:\Program Files (x86) (32-bit apps) and C:\Program Files (64-bit apps) on a 64-bit Windows machine. Understood.
Thanks for the clarification.
Click to expand...
Click to collapse
Yeah more like syswow64 which actually runs32bit apps and system32 which runs 64bit. Damn windows and their backwards ****
LancerV said:
Yeah more like syswow64 which actually runs32bit apps and system32 which runs 64bit. Damn windows and their backwards ****
Click to expand...
Click to collapse
Err, yeah that's what I meant. I was thinking more along the lines of where application files (exe's) are installed and not necessarily where it calls system DLL's, etc. from. We're good, I'm on the same page now.
Man...this is a whole new ballgame for me though going from the G3 to a G4. So much stuff is changing that it's going to be tough to use the phone the way I'm used to because half the **** doesn't work anymore. Sucks to be an early adopter.
IlyaKol said:
Err, yeah that's what I meant. I was thinking more along the lines of where application files (exe's) are installed and not necessarily where it calls system DLL's, etc. from. We're good, I'm on the same page now.
Man...this is a whole new ballgame for me though going from the G3 to a G4. So much stuff is changing that it's going to be tough to use the phone the way I'm used to because half the **** doesn't work anymore. Sucks to be an early adopter.
Click to expand...
Click to collapse
Yeah I think more stuff will start coming out once it gets more adaptation. I mean what made android 5.0 so easy to root was the universal exploits android had.
IlyaKol said:
Ahh okay. Similar to having C:\Program Files (x86) (32-bit apps) and C:\Program Files (64-bit apps) on a 64-bit Windows machine. Understood.
Thanks for the clarification.
Click to expand...
Click to collapse
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.
Too much nerd talk..
So is the G4 32bit or 64bit? I was told that the Snapdragon 808 is 64 bit and would feel ripped off otherwise.
macdaddie87 said:
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.
Click to expand...
Click to collapse
Compiling between 64bit and 32bit really isn't that big of a deal.
macdaddie87 said:
The kernal maybe 64bit because the chip is 64bit and the kernal contains the drivers. The libs that LG has compiled maybe compiled as 32bit. This makes sense that LG would do it like this since they have plans to bring UX 4.0 to the G3 and possibly the G2. They would have to compile UX 4.0 from the ground up to make it completely 64bit. Then compile a 32bit version of UX 4.0 for the previous models.
Click to expand...
Click to collapse
If the kernel is 64bit, the libraries are also 64bit.
They might (must) include some 32bit libs for compatibility reasons, so older apps can run, but the system itself would be 64bit throughout.
It makes no sense whatsoever to mismatch kernels and libs, and it makes even less sense to compile a 32bit system for a 64bit platform. It just doesn't happen.
And why would it be such a big deal to recompiling for another platform? You just run a build again for a different target.
Sfkn2 said:
Too much nerd talk..
So is the G4 32bit or 64bit? I was told that the Snapdragon 808 is 64 bit and would feel ripped off otherwise.
Click to expand...
Click to collapse
64-bit, lol.
Sfkn2 said:
Too much nerd talk..
So is the G4 32bit or 64bit? I was told that the Snapdragon 808 is 64 bit and would feel ripped off otherwise.
Click to expand...
Click to collapse
Conspiracy on if the phone uses 64bit because well cores
Makster said:
If the kernel is 64bit, the libraries are also 64bit.
They might (must) include some 32bit libs for compatibility reasons, so older apps can run, but the system itself would be 64bit throughout.
It makes no sense whatsoever to mismatch kernels and libs, and it makes even less sense to compile a 32bit system for a 64bit platform. It just doesn't happen.
And why would it be such a big deal to recompiling for another platform? You just run a build again for a different target.
Click to expand...
Click to collapse
The core could be 64bit but everything else that sits on top like UX 4.0 must be 32bit. How else can you explain us running G4 apps on the G3?
macdaddie87 said:
The core could be 64bit but everything else that sits on top like UX 4.0 must be 32bit. How else can you explain us running G4 apps on the G3?
Click to expand...
Click to collapse
The same way we run S6 apps on an S4 I suppose.
macdaddie87 said:
The core could be 64bit but everything else that sits on top like UX 4.0 must be 32bit. How else can you explain us running G4 apps on the G3?
Click to expand...
Click to collapse
Apps can be 32bit and 64bit isn't really about speed
macdaddie87 said:
The core could be 64bit but everything else that sits on top like UX 4.0 must be 32bit. How else can you explain us running G4 apps on the G3?
Click to expand...
Click to collapse
Just like the core is different from "everything else," UX is different from apps that run within it. Unless I am seriously misunderstanding this architecture (which is possible), UX, TW, Sense, etc. are more or less windowing environments, GUI frameworks. Kind of like Gnome and KDE. That's why you can get rid of them in custom ROMs that still use native OS (kernel+libs).
UX had nevertheless better be tightly coupled with the core OS (see Windows fire an extreme version of this), otherwise performance is going to suck. So, you are not likely to see a 32bit UX on a 64bit system.
And then you have apps. Those are completely separate from the above, they just use library calls into UX and android.
Unless you are installing every bit of that app by hand, I suspect you use an apk. Which is just a zip archive containing, among other things, libraries and executables that app needs. The thing is, the same apk can provide binaries for all sorts of platforms, including x86 and different versions of ARM. That way, you can have the same file downloaded from Google Play work on different platforms.
So it is possible that LG decided to package both 32 and 64 bit versions with its apps.
Or it could be that it would keep some of the apps 32bit, if they are not likely to need access to more memory than the phone has in the first place.
I don't have the phone yet, but it would be interesting to look into some of those apks and see what they stuffed into them.
Generally speaking, I don't see why LG would deliberately handicap itself by going through the trouble of designing a brand new version of its UI as 32bit, when the architecture it is premiering on is 64bit.
Everything is possible, of course, it just doesn't make sense to me.
Myself, I am not concerned with 64bit'ness of the G4 (seriously, it only has 3GB of RAM!) as much as I am with whether it uses the security extensions that are only available on 64bit ARMv8, so that encryption is done in hardware. And judging by the benchmarks results in the encryption thread in the QA forum, it does. That makes me happy.
Related
So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?
It IS Lupus said:
So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?
Click to expand...
Click to collapse
Well... You'll need a vendor tree first. And you'll have to run it on a 64-bit box with 64-bit linux. You have to change 'froyo' to 'gingerbread' in EasyDev, so it will grab CM7 source. There will also be some other differences to work out.
As soon as there's a vendor tree available and I have the time to test, I'll finish up EasyDev v7. Some of the additions that I have actually worked on so far are:
1) two or three bug fixes
2) adding CM7
3) adding option to install tiny or full gapps
The CM6 code has been unstable recently in addition to koush's hosting having issues, so I have had plenty of speed bumps in addition to real life stuff.
So... If you can wait on me, that's fine. If not, go for it! Feel free to post your code changes in the thread. We'll take any help we can get.
gnarlyc said:
And you'll have to run it on a 64-bit box with 64-bit linux.
Click to expand...
Click to collapse
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0
bftb0 said:
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0
Click to expand...
Click to collapse
I honestly wasn't sure, but a quick Google search...
http://groups.google.com/group/android-building/browse_thread/thread/852d63ab6124c87e
This is a post from the Android Building group. It appears to be a JDK issue. I've not really tested either way as of yet, although apparently Google says "use a 64-bit host to build, that's what is supported."
Hi,
This is (as far as I know) the first dump of wp8. It's based on the 9900 (emulator) build and is meant for cooking roms (for WP7/8 devices)
It has all 51 languages and all 3 screen resolutions
Good luck devs,
Download link:
http://htcfanboys.com/download/sianto1997/?action=view&file=14516
If you use this in a rom, please mention me.
greetz
WOW!Thank you very much!:laugh:
Do you know that emulator have x86 version of WP8? It's impossible to use it. So your dump is really useless, even more than me.
Shhh... It's easy to dump the emulator, just mount VHD.
Useless guy said:
Do you know that emulator have x86 version of WP8? It's impossible to use it. So your dump is really useless, even more than me.
Shhh... It's easy to dump the emulator, just mount VHD.
Click to expand...
Click to collapse
I see, sorry, but now no one has to download 7 gb to get the emulator dump!
sianto1997 said:
7 gb to get the emulator dump!
Click to expand...
Click to collapse
Offline ISO weights 1.6GiB. But it's much faster to download using torrent than downloading from unknown hosting.
Sorry but in the future is possible to have a WP8 Rom on a WP 7/7.8 device?
POSSAASSDDE said:
Sorry but in the future is possible to have a WP8 Rom on a WP 7/7.8 device?
Click to expand...
Click to collapse
Yes and no. As it's possable to run on the hardware (all 1st gen are the same CPU wise and 2nd gen are pretty close still) and even Microsoft said so, there are no drivers designed for it. Nevermind the OS is designed for a dual core CPU, so performance could be a big hit.
The HD2 was the ONLY Windows Mobile device to get WP7 and the only reason why that is was because Microsoft used the HD2 in testing WP7 and someone "leaked" the drivers needed. If things follow suit, the chances of getting a WP8 rom running on a WP7.5 device might be like finding that needle in a haystack...might happen but, I would not hold my breath.
I also would love to see it tho.....
I'm trying to compile Omni on a 32 bit Linux system, using the procedure given here: http://docs.omnirom.org/Build_for_i9300. However, the binaries in the directory
~/android/omni/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/
are 64 bit binaries, and I have a 32 bit system. Are these binaries available in 32 bit versions? And if so, how do I download them into my ~/android/omni directory?
Thanks!
AFAIK you cannot compile Android on 32-bit systems.
chasmodo said:
AFAIK you cannot compile Android on 32-bit systems.
Click to expand...
Click to collapse
32 bit systems have not been supported as a build host by Android for a LONG time.
Drat! Oh well... my options for compiling my own mods will have to wait until I either upgrade my system (dunno even if a have a 64-bit chip), or my computer.
Thanks for your replies.
amca1960 said:
Drat! Oh well... my options for compiling my own mods will have to wait until I either upgrade my system (dunno even if a have a 64-bit chip), or my computer.
Click to expand...
Click to collapse
Hi, I struggled with this a year ago and managed to set up a 4.6 compiler for a 32bit machine to build cyanogenmod using
Code:
https://github.com/yath/android_prebuilts_gcc_linux-x86-32_arm_arm-linux-androideabi-4.6
Its not 4.7, and as stated above, its not supported. It worked ok for me for jellybean but not tried it recently as I have a 64bit machine now.
Download: http://geektillithertz.com/wordpress/index.php/2017/01/03/lineageos-13-android-x86-on-pc/
Source: https://github.com/ric96/lineagex86
Bugs:
you tell me
FIRST !!!!!!
Congratulations my friend , but it no workie on my x86 tablet that was running cm13 x86
Kernel bladibla ..sorry so fix it bro !
How does it works?
is it an operating system to install on PC ?
is it a windows application ?
is it a linux application ?
what are we supposed to do with the.7z file ?
This looks promising. Keep up your good work!
Sent from my SM-G935F using Tapatalk
mlsoftlaberge said:
How does it works?
is it an operating system to install on PC ?
is it a windows application ?
is it a linux application ?
what are we supposed to do with the.7z file ?
Click to expand...
Click to collapse
The 7z file needs to be extracted in 7zip file manager. There should then be a IMG file that you need to burn to a USB with Win32DiskImager and boot on a PC. Then install the the HDD in the installer. Be careful with the HDD formatting, its a confusing naming system. I have accidentally formated the wrong drive in the past. It is a full OS.
Is it only for x64-CPUs or also for x86-CPUs? If it is not for x86-CPUs, than i ask you to compile a x86-Build. Thank you! I want install it on an ASUS Netbook.
I try to install geekbench or antuto and it force close
Sent from my MI 5 using Tapatalk
What about lineage-14.1?
it would be awesome if it's 14.1 since nougat support freeform
Lineage is the siccessor of the biggest alternative rom CyanogenMod. For me, there are many reasons to love cm: 1. I like to make all devices looking same, i hate sony-samsung-htc-huawei-moto...themes,bloatware and so on! (Only Sony cam is really nice)
Before a view years, cm was really good. When i buyed a new device (especially 4 months old), mostly there was a ready CyanogenMod out, sometime official, so i flashed and was happy. In the last 2 or three years, CyanogenMod was getting bad worse worst! Not much new devices, not much new updated, not actually Android versions, not much good mods, extras etc. included.
I hope, and it seem so, that it al will be getting better! But there is one big problem:
cm died becouse of getting commercial etc.
Developers must live ,so they need money.
Many developers proramm in their free time and have to work an their main job (waste of genious i say)
My suggestion is that lineage should get the best of both worlds, commercial and free/open source!
The main OS and all of his extras should be free to load, install and use!
Some not important services like OTA updates or user-support (not called customer-support) should cost money, but not much!
I think, a small price of 1€/Month could everyone pay who wants and was respect of this work..i would. When the account is empty, an support ab could be closed and no OTA's could be loaded...
Can you add multi tasking and external screen support to your x86 i mage.
Someone has already done the necessary code for it https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
Just needs to be included in the x86 image
Interesting idea
Enviado de meu Mi 5s Plus usando Tapatalk
Taking to chat instead
Does it work for 32 bit CPUs? I want to install it on my ASUS Netbook.
xEmre66 said:
Does it work for 32 bit CPUs? I want to install it on my ASUS Netbook.
Click to expand...
Click to collapse
There's a new build of CM 14.1 -86 here:
http://www.android-x86.org/download
I managed to install it to an old netbook [Toshiba N450 Netbook].
It is fast and has a beautiful interface.
Some apps keep foreclosing though.
It can be installed on 32bit and 64bit laptops.
It would be great to hear other feedbacks!
Hats OFF to the devs.
patrol31 said:
There's a new build of CM 14.1 -86 here:
http://www.android-x86.org/download
I managed to install it to an old netbook [Toshiba N450 Netbook].
It is fast and has a beautiful interface.
Some apps keep foreclosing though.
It can be installed on 32bit and 64bit laptops.
It would be great to hear other feedbacks!
Hats OFF to the devs.
Click to expand...
Click to collapse
It works great on USB for me but keeps crashing on my NVME install (looping com.phone crashing and system framework keeps stopping). Maybe it's just my pc?
Jbuch84 said:
It works great on USB for me but keeps crashing on my NVME install (looping com.phone crashing and system framework keeps stopping). Maybe it's just my pc?
Click to expand...
Click to collapse
I installed it on the hard disk where my windows is installed and gave it a 16gb data allocation. So far it is running great. Maybe try a fresh install.
Will it work on hp pavilion running on Windows 7 x32 cpu?
If working please tell me the smallest to biggest bug.
patrol31 said:
I installed it on the hard disk where my windows is installed and gave it a 16gb data allocation. So far it is running great. Maybe try a fresh install.
Click to expand...
Click to collapse
Did fresh install. What type of hard disk did you install on.. HHD, M.2, NVME? Mine is NVME and crashes on boot.
Jbuch84 said:
Did fresh install. What type of hard disk did you install on.. HHD, M.2, NVME? Mine is NVME and crashes on boot.
Click to expand...
Click to collapse
HDD, it's an old netbook.
I have been thinking about it more and more and was curious if there was anyone planning on porting android to the steam deck.
Why? If that's what you want get an odin
Why not just install Android x86 on it?
ejosh1 said:
Why? If that's what you want get an odin
Click to expand...
Click to collapse
An odin is nowhere near as powerful even at 9 w a loki is tempting but it wont be out for 6 more months
SteamOS on internal drive and Win11 on microSD.
JustSomeGeek said:
Why not just install Android x86 on it?
Click to expand...
Click to collapse
exactly
no need for porting, this device supports ACPI
bringing over some of its linux drivers to android x86 should be pretty simple as i believe its supported in mainline (amdgpu driver)