Hello everyone, I'm just asking for clarification about the custom rom: currently own a Galaxy S2 which as you well know is equipped with a chipset Exynox for which have not been released the source for the drivers.
Because of this failure to release, the rom that have been developed for this device, and of course the future, even if well designed, will never be 100% compatible with your hardware, or better, will never be optimized properly. Example: The camera, which with a custom rom takes good pictures, yes, but not up to those made with the original rom precisely because of the lack of support of the drivers.
The latest smartphone out, however, (practically all) mountain chipset "snapdragon", produced by qualcomm that from what I understand has released regularly releases and the various drivers for its components. This means that a rom (for example Omni or Cyanogen rom, I do not mean rom based on fimrware original), developed for smartphones that use this chipset, is considered almost "native" as compatibility? Photo and video for example, will have the same quality as those made with the original rom?
In short, install a custom rom on a device with snapdragon chipset, it can be optimized to be considered as if the terminal was shipped from the factory with this rom installed?
There is something wrong in my reasoning? I do not understand something?
Thank you in advance
Related
Tried to search for this but couldnt find anything is it possible to get a mango ROM working on an android tablet?
There are loads of 7" Android tablets out there for under £60 not the biggest fan of android but would like a cheap tablet for quick browsing of web and showing photos to friends etc.
Would be cool if could get a mango ROM flashed onto one of those 7" tabs
That's a good question. I'd also be interested if it were possible to drop Mango onto a tablet that started out life as an Android. It'd have to be a 7" screen, and it'd have to have a capacitive screen
jasongw said:
That's a good question. I'd also be interested if it were possible to drop Mango onto a tablet that started out life as an Android. It'd have to be a 7" screen, and it'd have to have a capacitive screen
Click to expand...
Click to collapse
Why does it have to be 7"? Resolution?
mcorrie1121 said:
Why does it have to be 7"? Resolution?
Click to expand...
Click to collapse
I think we're pretty much locked to 800x480 resolution, which I suspect would look horrible on a 10" tablet
Yea but im sure if it possible to port people will figure out a way around that like a regist edit or something. Actully maybe on a bigger screen more tiles would be visible instead of only 8 tiles or 6 it would be like 12 or 14
That is an interesting question. I was wondering the same thing, which is how I found this thread...
First of all, it would have to be a tablet with a WP7-compatible CPU. Unlike most x86 chips used in PCs, different ARM chips may have incompatible kernel-mode interfaces, so the core of every OS must be built for that chip. Linux (and therefore Android) can be built to run on pretty much any ARM chip. In theory, the same is true of Windows CE (the kernel that WP7 is built on), but without kernel sources (and no, the CE6 and CE7 sources available from MS aren't quite the same) we can't build custom kernels like that.
Second, and much harder, would be finding the drivers for the hardware. Every single WP7 device comes with a bunch of OEM code, the "firmware", that interfaces the kernel to the hardware. This is different from device to device (thus why, if you do something like flash a Samsung Omnia 7 ROM to a Samsung Focus, or even a Focus r3 ROM to a Focus r4, the phone won't work correctly afterward). Android has something similar, but again it has two benefits: the kernel is open-source, and there are Linux drivers for almost every piece of computing hardware (although not always very good ones). For WP7, porting to a new device is very hard because of this. The HD2 worked because
A) it originally ran a CE-based OS (an older one, but still CE based)
B) it's very similar in hardware to the HD7 (not enough to run HD7 ROMs, but enough to pull some drivers from HD7 ROMs)
C) an early firmware for the WP7 kernel was developed for it and leaked.
None of those things are going to be true for the typical random Android tablet.
GoodDayToDie said:
First of all, it would have to be a tablet with a WP7-compatible CPU. Unlike most x86 chips used in PCs, different ARM chips may have incompatible kernel-mode interfaces, so the core of every OS must be built for that chip. Linux (and therefore Android) can be built to run on pretty much any ARM chip. In theory, the same is true of Windows CE (the kernel that WP7 is built on), but without kernel sources (and no, the CE6 and CE7 sources available from MS aren't quite the same) we can't build custom kernels like that.
Second, and much harder, would be finding the drivers for the hardware. Every single WP7 device comes with a bunch of OEM code, the "firmware", that interfaces the kernel to the hardware. This is different from device to device (thus why, if you do something like flash a Samsung Omnia 7 ROM to a Samsung Focus, or even a Focus r3 ROM to a Focus r4, the phone won't work correctly afterward). Android has something similar, but again it has two benefits: the kernel is open-source, and there are Linux drivers for almost every piece of computing hardware (although not always very good ones). For WP7, porting to a new device is very hard because of this. The HD2 worked because
A) it originally ran a CE-based OS (an older one, but still CE based)
B) it's very similar in hardware to the HD7 (not enough to run HD7 ROMs, but enough to pull some drivers from HD7 ROMs)
C) an early firmware for the WP7 kernel was developed for it and leaked.
None of those things are going to be true for the typical random Android tablet.
Click to expand...
Click to collapse
So, long story short, probably not gonna happen. Gotcha. At least I know some of the work that is takes, for I am sure that it will take much more work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
yea your not gonna get arm wp7 on an android tablet , however there are many simulations of wp7 in android tablets , so if you want wp7 on an android yes thats the way to do it , but why?
Hi folks,
I am a owner of a SGS+ (i9001) which chipped with the chipset MSM8255T.
Now I've seen that are out some ICS-ROMs working with the Desire HD already which contains the (estimated) previous version MSM8255.
Unfortunately I could not find any useful information at Qualcomm, which shows the differences between these two chipsets.
May I use one of these ROMs as a base for my development for an MSM8255T or differ the chipsets too much?
There is an Alpha-Release from SE for the Arc S (4.0.1) which has the same Chipset as the i9001 ... but this lacks the basic functions including the modem and wifi ...
not a good starting point when i have the chance to start behind this limitations.
Nice holidays
Hi hirnwunde!
Funny nick )
I own a SGH-T679 (Exhibit II) witch is a half brother of the GT-I8150 (Galaxy Wonder).
What I can state that my phone works with SGW roms, issues are with the keys and the camera.
The SOC seem to be the same on different clock speed.
I don't know if there is a way to safely boot SE or HTC roms on Samsung phones.
hirnwunde said:
Hi folks,
I am a owner of a SGS+ (i9001) which chipped with the chipset MSM8255T.
Now I've seen that are out some ICS-ROMs working with the Desire HD already which contains the (estimated) previous version MSM8255.
Unfortunately I could not find any useful information at Qualcomm, which shows the differences between these two chipsets.
May I use one of these ROMs as a base for my development for an MSM8255T or differ the chipsets too much?
There is an Alpha-Release from SE for the Arc S (4.0.1) which has the same Chipset as the i9001 ... but this lacks the basic functions including the modem and wifi ...
not a good starting point when i have the chance to start behind this limitations.
Nice holidays
Click to expand...
Click to collapse
You have to watch for other device though, for instance the screen and camera needs different drivers. that by itself prevents direct usage from other phones even though the cpu is the same..
Hi everyone!
So I'm in the market for an ARM-based box running Android, but unlike most users here, I'm not looking to use it as a media streaming device for my TV. Instead, I plan to use it for a development project, and I'd like something that can provide me with as "stock" of an Android experience as possible.
My requirements are:
2GB of RAM
16GB flash
Support for custom community ROMs of Android 5.1 or newer that provide an AOSP-like experience
Stable ROMs (hopefully)...
Also, I know that with phones, you have lots of custom ROM developers like Evervolv, Cyanogen, MIUI, and so on... but is there community support for these Android boxes? And if so, are there some well-known ones I should consider to help narrow my search of supported devices?
Instead of ARM, I'd concentrate of AMLOGIC based Devices. Specifically S912 if not then S905 Based ones. Traditionally developer support has been better for Beelink Devices or Xiomi Devices along with the Manufacturer's own So Called "CM".
Since for a given Chip, the firmware is practically same across the manufacturers, you can start with those that have TWRP available and go from there. Lastly Finless Rom is one of the Developer group in this category that I know of.
Hello,
I bought several smartphone in the past until now and I always want to use them as long I can.
So Android obsolescence comes quite quickly once a smartphone arrives on the market (around 2 or 3 years after). We lose security patches, capability to use upper android version.... So each time I try to use custom ROM based on AOSP or Lineage / CM BUT I lose the capability to make decent photo with the Camera.
Currently it is unacceptable because I have to immortalize best moments of my life (childs, family ...).
The questions are simple : Do you know Android smartphone manufacturer or specific models with open / published camera drivers / framework that can be used on AOSP / Lineage OS?
I have the same question, if a manufacturer publish camera drivers that be used on upper Android version (EX: published for Marshmallow but useable on Oreo).
Thanks
There isn't one. This is the difference between open source and closed sourced drivers. The cameras and drivers are not even made by the device oem.
Updates these days are not that bad. You get a flagship and it will easily last 5 years. Even if 2 of them are only with security updates.
Hello zelendel,
Thank you for this reply.
In consequence all smarphone suffer of the same miseries. There is no way to get a Lineage with the same camera quality than stock experience due to closed source?! :crying:
Pretty much yes. I have not found a single device that doesn't suffer. It's one of the things you give up when you swap over to aosp base. Just like when using Linux. You lose anything special the oem did.
Hello everyone,
This is a work in progress thread meant to gather info about how to add hotword detection support while the screen is off and the processor is in deep sleep. Ideally, this will work just like the Pixel devices by Google, so you'll be able to get to the assistant by saying "Ok Google" without turning on your device.
Let's start off with the first big question: Is the hardware that's required to do this in our devices?
Well, not every device. I have only looked into Qualcomm SoCs, but this is also possible with some Exynos processors through S Voice.
Qualcomm first added support for Hotword detection with the Snapdragon 800. The only device prior to that processor that had support for Hotwords was the first gen Moto X, which had its own Custom chip separate from the processor. However, my research indicates that all devices after the Snapdragon 800's launch use the processor's DSP for this job.
You can view the announcement of this feature for the Snapdragon 800 at this link:
https://www.qualcomm.com/news/onq/2...akes-mobile-world-snapdragon-voice-activation
In the blog post, the feature is mentioned as Qualcomm Voice Activation. I also found out that this was eventually also backported to the Snapdragon 600. However, looking elsewhere online reveals that this has other names as well, as it is part of Qualcomm Fluent PRO and All-Ways Aware. There are marketing videos for both online, and they all work with the Hey Snapdragon hotword. However, it seems that all of these features are part of the Hexagon DSP on the actual SoC and that they are compatible with v5 and up. So that means that technically all processors in the 600, 700 (in the future) and 800 line should be able to do this.
As far as I'm aware, the only device that uses the Hey Snapdragon wakeup command is the OnePlus One, which has a Snapdragon 801. On its default firmware, CyanogenMod 11S, you could go into the device's settings and train the device by saying Hey Snapdragon three times. Then, you could select the activity that would run every time you said it.
Someone on XDA updated this feature for newer firmware versions and looking at the flashable zip files it has one application file, a modified mediaserver, a modified audio library for its processor and some lib files for voice detection. I haven't attempted to Port this feature for any other device, but I doubt that it would work, even on devices with the same SoC.
I have also looked at Qualcomm's forums and found this thread which has a reply with links that could probably help us out here:
https://developer.qualcomm.com/foru...timedia-optimization-hexagon-sdk/speech/28153
This is source code from the Google Pixel and AOSP which might be the solution to making this work. I am not familiar with C and AOSP's code, so if someone with more experience could check this out, that would be great!
Lastly, I want to mention that I have a couple of devices that could help with testing including my daily driver Xiaomi Mi 5 (Snapdragon 820), a now retired LG G2 (Snapdragon 800) and a Galaxy S7 Exynos which should be able to use S Voice for this but I have not tested it yet. My friend @David_#27 also has a Redmi Note 4X (Snapdragon 625) and I could probably also borrow a Redmi 4X (Snapdragon 435) if we ever need it for testing.
Hopefully we can get some more info on this topic from people that have looked into this more than I have. Please reply to this topic with any info you may have, any help is very much appreciated! Making this work eventually on our devices would be incredible!
Thank you
Bump!
@chrismin13, think this thread is dead...
No one is taking our consideration for real!?
In my opinion it is kind of creepy having the device listen to every sound around it at all times. Many, MANY, exploits were released in 2016 and 2017 specifically based around bugs in mediaserver, and audioserver.
You said this might entail using "...a modified mediaserver, a modified audio library for its processor and some lib files for voice detection..."
So I don't know if I'd even want to mess around with that until maybe even 8.1
Delgoth said:
In my opinion it is kind of creepy having the device listen to every sound around it at all times. Many, MANY, exploits were released in 2016 and 2017 specifically based around bugs in mediaserver, and audioserver.
You said this might entail using "...a modified mediaserver, a modified audio library for its processor and some lib files for voice detection..."
So I don't know if I'd even want to mess around with that until maybe even 8.1
Click to expand...
Click to collapse
True, there are significant security concerns. However, many other devices have also invaded our personal lives, with smart speakers especially becoming more popular lately. I agree, this is scary, but if I'm the one making the code for my device, then I'm more confident knowing what my device does. Also, this is more of an experiment rather than a long term solution. So it's up to you whether you want it or not. I'm willing to take the risk.