I have a note 5 n920T and the problem that I have is that most of the oreo or pie custom rom dont exist for this particular model. if a rom boots on it usually call audio is an issue. So, I want to modify existing kernel to work with n920T. I have been unable to find any guide related to "modify kernel for another variant of android device". Can anyone point me to any related guide or tutorial or video. I am a newbie to development and watched a few videos related to custom rom development but it doesn't help me as I want to modify kernel belonging to say n920C to work with n920T. I shall be grateful for your guidance. I have programming knowledge including c and c++
The big issue is with the speaker not working properly when ported to the T-Mobile variant. I believe it's a driver issue.
To be honest, none of the Oreo roms for our device are "good". They both are too unstable and have some major issues such as no/bad Camera (most apps will just crash), Bluetooth doesn't work, etc.
I've been using Oreo lately and just today alone I've had 10+ freezes/reboots. Unable to use bluetooth. Many apps using the camera just crash.
I think it's time to upgrade from our device as there's just no third party support anymore. The LG G7 seems to be the best value high-end phone on ebay, however there's not much support via XDA at this time.
Related
Im looking for a way to run a camera control software for nikon DSLRs on my note. However theese apps all are tablet software for android 3+. They run just fine on the cyanogen alpha, but that rom is too far from daily use even for bleeding edge enthusiasts, like most of us here. Thus, until now I have been forced to reflash everytime i need to control the camera with the phone.
Now several ICS ROMs have emerged, but those I have tested, though stable enough, refuse to work with USB on the go devices. The notice about the OTG cable show up all right ob them all, but they do not detect anything attached to the other end of it like in gingerbread and cyanogen alpha.
Is there a way i could fix this by copying some files from the cyanogen ROM over to one of the other ROMs? If so, which files would that be?
It's a kernel related issue. This means that we have to wait for Chainfire to get back from his vacation and tackle this problem. Or some other kernel dev.
Nothing we can do about it right now.
Ok, though i am a novice in the world of android hacking, that is not the case, at all, regarding linux kernel hacking. Setting up a cross compiling dev environment and moving a driver from one kernel source to another or compiling a module is actually less unfamiliar to me than trixing around with binaries from different beta releases. If that is the case i might be up to it. But that would only work if the source code, or at very least the kernel headers are available for the kernels used in the betas.
Sent from my GT-N7000 using XDA App
I want to use ANT+ with some newer rom and not with the original SonyEricson version, but so far i couldn't fine any.
Latest try was the: MiniCM9-3.0.0 [1/4/12]ICS 4.0.4/CM9 port for the Χ8 by nobodyAtall with his ICS nAa kernel.
It looked promissing, because I could download the ANT Radio Services from Play Store, but as soon as i start an ANT+ enabled program I get messages like:
(ANT+ Demo)
Enabling ANT...
Enable ANT ->
(ANT+ Bike display Demo)
ANT radio not enabled
So it looks like it claims radio is there and functioning, but it doesn't work.
Any thoughts? Otherwise I'll have to go back (again, tried couple times already with different version) to old SE rom.
(The MiniCM9-3.0.0 looks great although battery drain is awful.)
Just as a general statement that applies to every ROM that's being developed from source ...
- Developers can't fix things where the required hardware for testing is missing.
- Developers won't fix things they don't use at all.
In short: Custom ROMs are being made by privateers in their spare-time. None of us is a employee of some smartphone manufacturer having access to tons of testing equipment or having someone to pay the bill for buying crap to conducts tests with.
On topic: Up till today the people I saw posting about ANT+ can be counted easily by just using the fingers of one hand ... so it's safe to assume that none of us actually owns a ANT+ gadget or makes use of it.
Just to make sure, i'm only asking for information.
About your statements:
Developers can't fix things where the required hardware for testing is missing:
The ANT+ radio is available in most Sony Ericson phones, you just need to install the drivers, and the demo programs.
You don't need to buy a heart rate monitor to see if it works.
In the case of the roms i tried, they either didn´t recognise ANT+ or the driver didn't initialize correctly.
Developers won't fix things they don't use at all:
No problem, I'll try to look into it myself.
On topic: ANT+ is one of the coolest things Sony Ericson implemented in their mobile phones.
At least for anyone that has a (Garmin) heart rate monitor with ANT+.
With your phone and ANT+ heart rate monitor you have a cheaper more flexible GPS/heart rate monitor device than you can buy from any company's and can make phone calls.
Ant+ Rom
I haven't verified that it is working, but MiniCM7 claims to have working Ant+. Unfortunately, I can't use it because it requires the nAa Kernel and I can't unlock my bootloader because my phone is the 11W29 model.
If I find a way to safely unlock the bootloader I'll definitely be giving MiniCM7 a try. Other than lacking the ANT+, I'm really happy GingerDX.
If you find any way to get it working, please post the info.
hi guys,
have you managed to get ANT working on any rom? I'm trying to use it on a ray with iced bean 3.0, but it's just saying enabling ant and after a while switches to enable ant. I mention, I have installed the ant radio service ant ant demo from play. an tried to activate with the demo.
thanks.
The title may look weird but that's the best sentence I could find to summarize my question.
One of the myths about mobile phones is that they have back doors for the secret services or goverments to tap into and listen to phone calls or SMS messages. This was something we could never be sure about at the old days of Nokia (R.I.P.) "black box" phones.
I've been developing software for more than 20 years but my experience with Android is only 10 months and I've not dived into the big sea of custom ROMs and kernels yet.
My question is simple. How much of custom ROMs and kernels on this device (or any other Android phone) are open source and is it "much" enough to be sure that there is no back door or hidden function?
I would be grateful if ROM and kernel experts can answer this question.
well, honestly this Q sounds a bit strange, but here we go:
1) kernel:
all kernels MUST be 100% open source.
2) device tree
also the device tree has to be open source, just like the kernels
3) ROM
ROMs do not have to be open source. but nearly all (except stock based) custom ROMs for our device are open sourced. otherwise we wouldn't be able to compile them
a special topic are stock ROMs.... i have never seen an open sourced stock ROM from any manufacturer (except google ofc).
now, back doors:
i never heard of a rumor that custom ROMs would have back doors. actually we are working on finding unknown (unwanted) backdoors to fix them.
But for stock ROMs, i personally wouldn't be too sure there is no back door...
Backdoor or not, big agencies (like the NSA for example) do not need backdoors to your phone, they have way more capabilities/possibilities
So it's quite useless thinking about it IMO, as you cannot change anything about it
postacik said:
My question is simple. How much of custom ROMs and kernels on this device (or any other Android phone) are open source and is it "much" enough to be sure that there is no back door or hidden function?
Click to expand...
Click to collapse
Short answer: Not enough.
Longer answer: The kernel and some custom ROMS are open source, but many of the drivers (which operate at root level) remain closed. It should also be plausible to hard-code additional functionality into the hardware of a phone.
The thing that gets the least scrutiny is baseband since it runs on custom hardware. Even with closed source drivers it's arm code running on Linux so lots of people can understand it.
ROMs and kernels aren't really an issue though.
Got my hands - ( don't ask how ) - on what appears to be a fake S5 Mini. Everything about it says Samsung, however neither Kies nor Odin detect the phone and the specs are all wrong anyway. Attached are screenshots from Device Info and CPU-Z.
The phone actually works OK, though it's not nearly as good as a real S5 Mini. But there are several glitches in the system: some apps or options just don't work, multi-language support is deficient, etc.
Nothing surprising from a clone.
Question: is there a ROM I can try to load to that device to see if I can make it work better? I was reading up on MoKee (because of the serrano3g identifier in the model name displayed by CPU-Z), would one of those ROMs work? The phone/wifi/BT portions all work correctly, so I guess there's no need to flash a new radio. Then again, I haven't flashed an Android device in a couple years, I'm basically like a newbie at that stuff, so if anyone can provide me with information on what/how to flash, I'd be grateful.
Thanks!
neat
Any pictures of the phone itself?
SOC seems to be a MediaTek MT6572 if correct see this thread http://forum.xda-developers.com/showthread.php?t=2687487
@protogenxl: Visually, it's an exact replica of a Samsung S5 Mini, with the brandname and all. So if you check out the Samsung site, you'll find plenty of pictures there!
As for the thread you mentioned, I had already read it but I'm still not sure whether that particular ROM can be installed on my device, even though it's a MT6572 ROM. And keep in mind that I am a newbie on flashing devices, so I'm not even sure where to start, what tools to use and what I should be looking for.
Thanks for the suggestion, though!
s5
I have a S5 Mini G8800-F, so the most interesting part would be the layout of the inside of the battery compartment, is the dead space for a second sim there etc....
I would say first order of business is getting a custom recovery installed and getting full backups of original OS in a safe place, after that should be relatively hard to completely brick it as I seriously doubt the clone company put any effort in to boot security
@protogenxl: I'll try and upload a picture of the battery compartment later today. Don't recall seeing a second SIM slot in there, though.
And I agree with you that the clone company didn't put any effort on securing the device. It was rooted when I got it, it's got one of those chinese bootloader menus (I found a video on Youtube explaining what each option means).
As for the custom recovery, should I just pick any of them or are there any recommendations specific to this chipset (or do I even have to care about the chipset at that stage)?
@protogenxl it has been to long since I messed with sisters then boyfriend's phone to get it usable but if memory serves I got a custom made version of CWM from the ChinaPhoneArenea forum.
@protogenxl: here's a youtube video I found which describes the exact device I have: https://www.youtube.com/watch?v=k_-OoKhkD_0
It shows it with its back cover open around the 2:30 mark.
Hello,
I'm very new to android roms
Well, I did a little bit of that back in pre-2010 times and some times with my samsung galaxy nexus, but I assume things have changed a lot since then.
I have many XT1929-17 Z3 non-play and a couple Z4 XT1380 and a few Z2F
I want to try many things,
Download all firmware from each phone, and upload firmware to a phone (I guess that's the flash device and radio firmware , not sure)
Make setup a phone to my taste, make a backup so I can continue messing around without having to go through the entire setup process again !
Next, I have the crappy verizon firmware, I would like the stock android or Z3 motorola stock firmware instead of the verizon one ! WIth all the non-erasable bloat- and spy-ware
Next, I am stuck on Android 9 forever, I would like to try android 10/11/12 especially if the moto mods and gestures are still working. Really, just android 10 would be great, the only thing I really want is darkmode notifications and settings !
After that, if there are roms for those, I would like to try lineageos, grapheneos, pixel experience and the other popular firmwares that are made for many phones.
I would like the fastboot and adb windows 10 offline drivers to remote control all aspects of the phone. (I will be using many of those phones as wifi cameras and I'm trying to reliably stop and start recording 240fps video with wifi remote control)
Oh, and I would like to try just plain linux on those phones, if that's even possible. Even if that's just cpu/ram/wifi. I'd like to use one of them as a mini server
I think that's pretty much all I want to try with these phones, do you have advice on how to do this on Moto Z3 non-play ?
Thanks !
you cannot run linux on android smartphone, except you're talking about "linux" on top of "android kernel" which still provides full hardware HAL access. the overhead is nearly the same as running android, so no point in this. but here you go.
https://docs.ubports.com/en/latest/porting/introduction