Hi to all!
Exynos 7580 is a 64bit CPU. I don't know why Samsung made a 32bit system for this A53 CPU. I want to use the lastest Google Camera, but it only supports arm64. So I try to port a 64bit system for my A710F.
I found an A720F lineage OS, and got the files about arm64, like lib64, app_process64,etc. I packed them and flashed it, and my device booted successfully. Then, I put a 64bit camera in /system/app, and it worked successfully, too. But the problem is, I want to install a 64bit software. So I need to modify build.prop.
First time, I entered:
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-US
ro.wifi.channels=
Failed to boot. Zygote failed.
Second time, I entered:
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=arm64-v8a
ro.product.cpu.abilist=armeabi-v7a,arm64-v8a-armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-US
ro.wifi.channels=
The system ui worked no more than 1 second, then fc.
So, I replace it with A720 system ui, but it still fc, and didn't work at all.
There's no a exynos 7580 device running 64bit system, but if there's a device very similar to our device? No only change these things, but also port others. Is it possible? I want to try.
Do you have any ideas? Please discuss it with me!
Thats a good idea, waiting for another people replies
DF11GB said:
I found an A720F lineage OS, and got the files about arm64, like lib64, app_process64,etc. I packed them and flashed it, and my device booted successfully. Then, I put a 64bit camera in /system/app, and it worked successfully, too. But the problem is, I want to install a 64bit software. So I need to modify build.prop.
Click to expand...
Click to collapse
Well this is just a small part of a full 64 bit operating system. In order to run 64 bit apps, system etc. you'll have to care about the other factors too.
The main part of a full 64 bit system requires a 64 bit supported:
- kernel
- ramdisk
- OS: framework and core apps
- libaries
- system binaries (system/bin)
- vendors
The Galaxy A 2016 series only fulfills one of these factors: kernel.
It's possible to port 64 bit system but only if there is an another Sammy device shipped with full 64 bit support and with same SoC as the Galaxy A 2016 series.
deleted..
xXPR0T0TYPEXx said:
Well this is just a small part of a full 64 bit operating system. In order to run 64 bit apps, system etc. you'll have to care about the other factors too.
The main part of a full 64 bit system requires a 64 bit supported:
- kernel
- ramdisk
- OS: framework and core apps
- libaries
- system binaries (system/bin)
- vendors
The Galaxy A 2016 series only fulfills one of these factors: kernel.
It's possible to port 64 bit system but only if there is an another Sammy device shipped with full 64 bit support and with same SoC as the Galaxy A 2016 series.
Click to expand...
Click to collapse
Samsung a9 2016 supports android 8. Can the software be ported to a5 2016?
https://samdb.org/tr/model/SM-A910F/
https://www.gsmarena.com/samsung_gal...2016)-7903.php
xpity34 said:
Samsung a9 2016 supports android 8. Can the software be ported to a5 2016?
https://samdb.org/tr/model/SM-A910F/
https://www.gsmarena.com/samsung_gal...2016)-7903.php
Click to expand...
Click to collapse
No. It runs Qualcomm MSM8976 while A5 2016 runs Exynos 7580 soc.
why to be used google camera any benefits of google camera...?
A7 2016 have the same soc,a3 2016 and Samsung Galaxy View Tablet too (exynos7580)
The Galaxy S5 Neo Sm-G903F is the first smartphone with SoC Exynos 7580, all others devices based on the same soc are derived from it, and it didn't receive 64bit Android OS, only 32bit. It would be nice to have a 64bit version, but this would require to start from ground zero if there is no sourcecode from the other parts required to run in 64bit.
Related
Hello everyone!
Few months ago I had a problem with the my grandma's Pentagram TAB 7.6 tablet.
It doesn't want to boot up (or charge-up).
So I've managed somehow to boot-up and done internally upgraded the firmware (20140115_v1.1 OTA).
The device is now properly turning on, but currently is a another issue:
The both cameras aren't working.
Internal Android app tells me that Gallery ceased to work, and another installed apps from Google Play, which are using camera, reports that they can't connect to camera.
Specs:
Name: Pentagram TAB 7.6 [P 5346]
Model Number: PentagramTAB7.6
Android Version: 4.2.2 (previously was the same)
Kernel: Stock 3.0.36+ #127 Fri Nov 8 13:48:48 CST 2013
Compilation Number: 20140115_v1.1 (previously 20131105v1.0)
Additional Info (provided by manufacturer):
Processor: 2-core - 1,2GHz - Rockchip 3168 ARM Cortex A9
Graphics: PowerVR SGX540 - 3D: OpenGL ES1.1 i 2.0 - 2D: OpenVG1.1, DirectFB, GDI/DirectDraw
Screen: 190.5x113x8 mm
Cameras: Back & Front 0,3 Mpix (VGA).
Is there a posibility to get & inject a working camera driver / get a fully working ROM to use with Rockchip flashing tool etc.?
PS:Some people are also got problem with HDMI, but due to I hadn't a proper cable, I can't verify if this problem applies to her tablet.
Hi, I have a tab Audiola 05783g with the following caracteristics:
Display 7.85" HD IPS, Resolution 1024x768, Processor A7 Dual Core MTK 8312 1.3GHz, RAM 1G DDRIII, Graphics GPU Mali-400, Android 4.2.2 Jelly Bean, Memory 8GB , SDHC 32GB, Front Camera 0,3 Mpixel - Back Camera 2 Mpixel, WI-FI (b-g-n), 3G Voice + Data, Bluetooth 3.0, GPS + AGPS.
The software installed is:
Base Band ver. MOLY.WR8.W1315.MD.WG.MP.V18, 2013/11/29 20:10
Kernel 3.4.5 shyelinktek2 #1 Thu Apr 10 20:55:08 CST 2014
Build number MT83X2_MR790_MR7902H1CW1.2014041020
Personal Build xers. 1.19_20140303
The Tab come without Play Service, and after I had installed it I've got Time Service and Monkey Test malware.
I tryed a factory reset but this did't fix the problem due to the malware become part of the system.
Can anybody of you, expert guys, suggest me the way to clean the system?
Thanks
Ziofritz
Hi all
I need firmware for meanit promise q760
allwinner tech
quad core a33
e9072aa 4ar1 (printed number on a33 p.)
Android 4.4.2
Firmware v. v2.0
core v. 3.4.39
builder [email protected]#3g
fri dec 12 17:15:41 CST 2014
astar_m71-eng 4.4.2 KVT49L 20141212 test-keys
firmware for TAB-P742-V1.0-20141124 works, but only lower fifth of touchscreen, no wi-fi, no camera...
Regards
More info and photos
Here are some more info of my meanit promise q760;
Touchscreen chip: Silead GSL 1680
Wi-fi chip: esp8089
Power Management IC Chip Controller: axp223
Is there any way to recompile kernel from TAB-P742-V1.0-20141124.img with drivers for my tablet? How to do this?
Please help.
Regards
Hi all
Some new firmware images are working with same result (no touchscreen, wifi, camera, bluetooth...)
140D A33 10.1.zip
M1025A_TZX_RASK_TZX0233_DBL2855_ESP8089_GSL3675_HD_20150206.rar
I would write a link for each image but I cannot (new user).
Looks like all of upper images have drivers/kernel modules for my tablet in /system/vendor/modules - esp8089.ko, GSLx680.ko, gslx680new.ko ...
I tried to start those modules with insmod, but other modules are active. I cannot stop rtl8150.ko and ... No rmmod.
How can I load modules that I need on boot?
Please help someone.
Magda
Hi nobody
TAB-P742C_V1.x.zip image works fine on my tablet. I have wifi, location, and lower fifth of toucscreen, no camera.
Insmod and rmmod commands works on this image, and I tried all gslX680 modules from /system/vendor/modules. Only gslX680new.ko is partialy working.
How can I adjust touchscreen? Is there any way?
Please do not let me talk to myself
Magda
Hi all
I tried so many gslX*680.ko modules and I cannot find right one. All I need is gslX680new.ko from meanit promise q760. Please someone send it to me. It is just a small file...
Magda
Hey there everyone,
Im have some issues running a custom recovery on a DUNNS AT1001 tablet, i am also trying to find out what the most popular version of this type of device is.
Specs are as follows :
MT6582 ( MT8382 Is fake ) - According to MTKdroidtools
1GB RAM
8GB ROM
Mali 400MP
4.4.2 Kit Kat
QR Code Scanned on Board : 080872 MT8382V/X NT5CC512M8BN-DI NCEFES78-08G PCDDR31024MB2x8BIT912
Codes on Board :
ELINK-MR906_D3_V10
E320009 RU
EEKSHLF-2
94V-0
H:532 P
Some details from Build prop
ro.build.id=KOT49H
ro.build.display.id=MT83X2_MZ906_MZ1031L2CW2.2015041415
ro.build.version.incremental=eng.yj.1428997614
ro.custom.build.version=2.26_20141108
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.mediatek.version.release=ALPS.KK1.MP1.V2.11
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP1
ro.mediatek.version.sdk=2
ro.build.description=mr900-user 4.4.2 KOT49H eng.yj.1428997614 release-keys
ro.build.fingerprint=alps/mr900/mr900:4.4.2/KOT49H/1428997614:user/release-keys
I managed to get TWRP 2.7.1.0 working through TWRP Magic Installer although the problem is that the touch is off calibration when using it, the buttons arent where they should be. i was also struggling to get other types of custom recovery's installed due to the recovery partition only being just over 6mb big.
My main hope was to try and upgrade this tablet to atleast android 5.1.1 or higher eventually, would there be any hope or is it just not possible on this hardware ? Thank you !
Hello everyone, there is such a problem, this phone comes with a Snapdragon 450 processor and it is 64 bit and should have ARMv8-A instructions, but not from Samsung)). They made the OS Android 11 32-bit why ???) The processor works like this: ARMv8-A (32 bit mode), and has only such instructions: armeabi-v7a, armeabi. I cannot install more than one 64-bit application (even with arm64-v8a + armeabi-v7a), only noarch is installed and that's it). You too?
I think the same problem. When I try install a apk by adb say: INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113 Maybe have relation with 32/64 you say, because the same app work in many phone except this. Change the OS for a 64-bit solves the problem, no?
aspoer said:
Hello everyone, there is such a problem, this phone comes with a Snapdragon 450 processor and it is 64 bit and should have ARMv8-A instructions, but not from Samsung)). They made the OS Android 11 32-bit why ???) The processor works like this: ARMv8-A (32 bit mode), and has only such instructions: armeabi-v7a, armeabi. I cannot install more than one 64-bit application (even with arm64-v8a + armeabi-v7a), only noarch is installed and that's it). You too?
Click to expand...
Click to collapse
Check If the app you are trying to install has a 32bit version(armeabiv7 / arm7)