Hi everyone,
So the question is simple: how hard is to port a firmware that is designed for one android device to another android device?
The devices in question is Samsung Gear Live and LG G Watch R. Both have the same cpu model and same tech specs. While Samsung has square LCD display, LG G has a round LCD display. I am assuming both have different components and drivers for bluetooth/wifi, barometer and other sensors.
However, this should be mostly doable if I can compile kernel modules for the missing drivers, yes?
Related
Hy guys i've a little answer for you i have a samsung galaxy s2 with the cyanogenmod 11 rom and i'm thinking of buy an lg g watch the google sites said that my smartphone is compatible with android wear and also if my phone has bluetooth 3.0 thanks to cm now when i use application like ble checker it said to me that my phone support bluetooth 4le. So my question is saw all this things if i buy an lg g watch i will have problem of compatibility or not?
Realmerlin said:
Hy guys i've a little answer for you i have a samsung galaxy s2 with the cyanogenmod 11 rom and i'm thinking of buy an lg g watch the google sites said that my smartphone is compatible with android wear and also if my phone has bluetooth 3.0 thanks to cm now when i use application like ble checker it said to me that my phone support bluetooth 4le. So my question is saw all this things if i buy an lg g watch i will have problem of compatibility or not?
Click to expand...
Click to collapse
Judging by what you're saying it shows, you are compatible, Android Wear is compatible with 4.3 and above. However if your phone only has Bluetooth 3.0 support and not 4.0LE you'll see some battery drain outside the normal amount specified by both users of the device and the manufacturer. This is because 4.0LE maintains a link with the device without actively being connected to it causing it to use less power to communicate, 3.0 lacks this ability so your phone would need to keep an active link with the watch at all times.
That being said, don't let that discourage you from getting it, your phone is completely compatible as it is now and should give you an alright experience with the device. I personally love my LG G Watch and feel that it's the best purchase I've made in a long time.
thank you so much fantastic answer admins can close the thread
My last and my current smartphones were nexus devices. Since google revealed the pixel I thought about other smartphones. But I don't like update speed from non-google companies.
How difficult would it be to convert the current Stock Android (for example android 7) to the Huawei P9, OnePlus 3 or the Samsung Galaxy S7 or any other top device.
And how much time would you need to support also the curved Display from the Samsung Galaxy S7 Edge or to support the notification button from the OnePlus 3 and the fast charging.
To myself: I would say that I am quite good at Java but not in a professional way.It is just a hobby.
In general: If I buy the latest smartphone of a company like Huawei, Samsung, OnePlus or LG would it be possible to convert the current Android version to my device? How much time would I need for that if I only want the Stock Android functions and the fingerprint sensor (Cyanogen features are not needed) and how long would I need if I also want to support the device specific features like a pen or a curved display?
How dangerous would that be? Breaking my device would be pretty easy right?
If that is possible how do I convert the Stock android to my device?
Thanks a lot
p4
short answer: very difficult. Huawei uses custom SoC from HiSilicon, and the specs for these chips is not published. similarly for Samsung devices using Exynos chips. Samsung phones running Qualcomm have a better chance.
if you want to learn to build AOSP (or something like CM), start with the AOSP documentation, then the CM wiki. Or go to the device forums here and check if someone has already started progress. for Huawei and Samsung (exynos), it's a long journey.
it goes well beyond knowing Java.
relatively speaking, modern devices are tough to permanently brick as long as you don't touch the bootloaders.
Thanks for the answer
Hello, I have a LineageOS 14.1 running LG G2mini (d602). I just saw that there is an android update for his bigger brother d802.
I wondered if it is possible to port it to the d602. I am gonna try to install it directly to see the result, but I suppose it won't be satisfying. I am ready to work on this port but I am not a developer, so I will need some help there. Please write here if you are interested in this project.
The only difference between those two phones that I know (apart from the size) is the version of the snapdragon processor (400 vs 800) and the amount of RAM (1 vs 2). However, I'm not really sure about the logicalboard, thought...
my guy, the hardware is entirely different. You said it yourself, different platform (sd800 sd400), different ram (1 v 2), different displays, different cameras most likely, different everything. A port is impossible. Build it yourself.
I have a Vertu Aster P Chinese clone, purchased from here https://www.luxuryvertu.cn/ProID473.html and since buying it, I've been desperate to try and update it from the Vertu-themed Android 6.0 Marshmallow that it came with.
They lie about the phone specs on their site that I got it from. It doesn't run Android 8.0 and it doesn't have a Qualcomm Snapdragon 660 SoC .The genuine Vertu Aster P runs on Android 9.0 Pie, which is what this clone should have really come with, being a late 2019 phone and to stay true to the genuine Vertu. Trouble is, being a Chinese replica, and having an MTK SoC, there is no support for it. The manufacturers refuse to provide me with the kernel source code, so I'm at a dead end in terms of any Android development.
One thing I did notice is that the 'Device Info' app shows the device as being a 'gionee6755_66_m'. See the second attachment that I've uploaded. Does this mean anything to anyone? Is it the model of a specific Gionee handset? Could this be a clue as to what the Chinese clone makers based this phone off? If so, I do know of a few threads here and there on XDA related to Gionee development.
Also, in the third screenshot attachment that I've uploaded, you can see that the icons for data connection and aeroplane mode are rubbing up against each other, suggesting that someone has made a 'quick and dirty' fix to try and get both of the icons to fit the width of this phone's screen. Which also might suggest that this ROM was actually pulled from another device. Any thoughts?
Chris
@chris8189
Note that you on every Android device can fake its brand and/or model: you can even make it think to be an Apple iPhone 11 Pro. You also can fake its version of Android OS. What you can't (easily) change are descriptions of installed hardware components .
So one can't really say your device is a Vertu Aster P or Gionee6755_66_m or whatever.
What I think happened is that you got screwed.
jwoegerbauer said:
@chris8189
Note that you on every Android device can fake its brand and/or model: you can even make it think to be an Apple iPhone 11 Pro. You also can fake its version of Android OS. What you can't (easily) change are descriptions of installed hardware components .
So one can't really say your device is a Vertu Aster P or Gionee6755_66_m or whatever.
What I think happened is that you got screwed.
Click to expand...
Click to collapse
I wasn't 'screwed' as such. That's a bit of a crass term. The device is of premium quality, feels as heavy as a genuine Vertu and really does look the part. And it performs perfectly fine on Android 6.0. The phone is fast and responsive and does whatever I need it to do.
That said, it wouldn't have caused them any more distress in putting Android 9.0 onto this phone. The MT6755 Helio P10 chipset that this clone has is more than capable of running 9.0. Why they didn't is a mystery to me.
My question may come off as a weird one to some people but I NEED to ask this.
I have Japanese TAB, LGE Qua TAB PZ au 10.1 inches.
I was trying to look for a custom rom for this device but it appears that they simply do not exist on the internet. So I started wondering if I can use a custom rom designed for V521 (T-Mobile version) instead.
You see, the specs on both the devices is identical, both are based on Qualcomm Snapdragon 617, except for 2 differences:
1. The screen size on my device is 10.1 inch while on V521, its 8 inches. Although, the screen resolution appears to be identical
2. The battery on my device is 7000 mah while on V521, its 4650 mah
So is it possible to install a custom rom that was made for V521 on my Qua TAB PZ? If it is possible, what precautions do i need to take while attempting to install the ROM?
Anyone?