Hi all,
I've tried different modems and know that they effect dramatically on battery life and reception. I also know that the "best" modem is individual and a trial-and-error approach is needed.
Still, is there a documentation somewhere about each modem's features? For example the Nexus kc1 modem (if I'm not mistaken) has the ability to switch to 2G to save power when the phone is idle. I'm wondering which ICS modems (CM9) for the S2 have this feature, for example. Also some modems are reported to work better at certain ranges, etc.
Thanks
Sent from my GT-I9100 using XDA
Subscribed.
Perhaps this thread could & should be under a more general forum?
I'm thinking exactly the same thing.
I'm wondering what the limitations are. I have a feeling some very interesting things could be done with the modem.
http://androidforums.com/galaxy-s2-...3246-extract-radio-modem-tar-md5-package.html
For one, perhaps the polling time to the base station could be increased to save battery, and then put back to the original setting. There might be a standard that companies have against this, there might be a hardware limitation or possibly it's just badly documented right?
Another one could be broadcasting something completely different, or... receiving something you're not supposed to receive... scanning for other mobiles even. It could get quite disruptive.
No idea why not much talk on this... or perhaps we just need the right words to search for?
I can find related talk but nothing on the stack itself:
http://androidforums.com/galaxy-s2-international-all-things-root/489457-latest-i9100-modems.html
Samsung modems come as pre-compiled .bin files and Samsung never releases change logs with modems or ROMs so it's difficult to say what changes between releases. As far as I know, given the proprietary nature of the code it isn't possible (either technically, legally or both) to decompile the modem files and look at the code so any reviews would be purely based on observation of signal strengths and data speeds, also I don't think it's possible to modify them in any way, at least I have never seen anything that suggests a dev has tried.
Modems are black boxes. Documentation ? Bwaaahahahahahaha There's no such thing. Apart from real world tests people on here/elsewhere have done to compare connectivity/data speeds.
Always good to see a bit of maniacal laughter MB.
----------------------
GTI9100 KK5
Hehe ;-) Some of things people expect around here make me laugh.
I mean, documentation. From Samsung ? *****, please. Given how they play hardball with sources they're not going to give us documentation for proprietary code anytime soon.
aceofclubs said:
Always good to see a bit of maniacal laughter MB.
----------------------
GTI9100 KK5
Click to expand...
Click to collapse
Samsung release documentation it not only is read by guys that understand but also every idiot with a SGS2 . They will soon start posting asking for themed modems .
jje
Well I guess this is in the Samsung forum but also I'm thinking it would be nice to know just a little about modems... even just what the API allows would be nice.
As for going deeper it seems that yes, there is no company allowing full access:
"Although its philosophy is somewhat similar to that of Openmoko, GeeksPhone does not publish hardware specifications for its devices beyond a data sheet. Another difference is that GeeksPhone aims to provide a stable device suitable for everyday use and capable of competing with other commercial devices on the market. The GeeksPhone One ships with an Android version which has undergone quality tests and passed Android Open Source Project (AOSP) Code Compliance certification, allowing it to include closed-source Android components and participate in Android Market.
About emerging competitor Synapse-Phones's strategy to offer smartphones with customizable hardware, Rodrigo Silva-Ramos stated that GeeksPhone had tried the same, but found it impossible. He noted, however, that the existence of a competitor confirmed the viability of the company's business model.[10]
Click to expand...
Click to collapse
jago25_98 said:
Well I guess this is in the Samsung forum but also I'm thinking it would be nice to know just a little about modems... even just what the API allows would be nice.
As for going deeper it seems that yes, there is no company allowing full access:
Click to expand...
Click to collapse
The cm team would be on top of this I suspect.
Maybe they have commented their source code. Never looked but worth a shot.
----------------------
GTI9100 KK5
Related
Can someone kindly explain why porting the Nexus S to the Vibrant doesn't work? I have tried to use "Search" but have been unsuccessful with finding in depth information on the subject. From what I have gathered, with the exception of Bluetooth 2.0 vs. 3.0, Front Facing Camera (VGA) lack of external storage, and obviously Android 2.3. There is no other difference. I guess I'm wanting a more technical answer regarding the differences. Yes I understand regarding modems/source codes etc. But I still don't get it. I'm more of an amateur over-clocker on desktops and I guess the differences vs. a desktop and smartphone are greater than I initially realized. Perhaps my chosen search definitions aren't specific enough or are too vague. I'm sure this may have been beaten to death but my want to know has gotten the better of me. I find this community to be full of knowledge but I fear that using search can be frustrating. Thanks in advance for you expertise guys (gals) BTW the similar threads box is awesome.
because porting doesn't involve copying the nexus' rom and pasting it on the vibrant.
the Drivers, which run the whole phone are incompatible, there is a ALPHA build version, with no gps, the buttons are switched, voice doesn't work, etc.
Drivers are not possible for devs to make, and only samsung, and other manufacturers, can make them, and make it compatible.
xriderx66 said:
because porting doesn't involve copying the nexus' rom and pasting it on the vibrant.
the Drivers, which run the whole phone are incompatible, there is a ALPHA build version, with no gps, the buttons are switched, voice doesn't work, etc.
Drivers are not possible for devs to make, and only samsung, and other manufacturers, can make them, and make it compatible.
Click to expand...
Click to collapse
Thanks for your response. I do understand that "cutting & pasting" is a no go. But what got me curious is that the hardware is the same. So speaking from a PC Geek's view a series of GPU's if you will can be produced by different third party vender's. However the Drivers would be the same even if the third party vender changes the BIOS they could still be flashed to another card ex. flashing ASUS bios to a similar card like a MSI GPU. Some vender's may slightly change the user interaction ex. software suites for "tweaking" settings ie over-clocking. So I guess this is why I'm asking what is so different regarding these two phones that prevents a "clean" port. If the hardware was a completely different generation I totally could understand. This unless I am wrong (which I probably am) is what is bending my logic.
Edit: I stand corrected the Nexus is different
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
vs.
http://www.ubmtechinsights.com/repo...stigative-analysis/samsung-galaxy-s/teardown/
amwilliams9 said:
Can someone kindly explain why porting the Nexus S to the Vibrant doesn't work? I have tried to use "Search" but have been unsuccessful with finding in depth information on the subject. From what I have gathered, with the exception of Bluetooth 2.0 vs. 3.0, Front Facing Camera (VGA) lack of external storage, and obviously Android 2.3. There is no other difference. I guess I'm wanting a more technical answer regarding the differences. Yes I understand regarding modems/source codes etc. But I still don't get it. I'm more of an amateur over-clocker on desktops and I guess the differences vs. a desktop and smartphone are greater than I initially realized. Perhaps my chosen search definitions aren't specific enough or are too vague. I'm sure this may have been beaten to death but my want to know has gotten the better of me. I find this community to be full of knowledge but I fear that using search can be frustrating. Thanks in advance for you expertise guys (gals) BTW the similar threads box is awesome.
Click to expand...
Click to collapse
difgerent radio, difgerent storage inand on ns, basically two different phones
And most importantly the lack of vibrant source code
Sent from my Nero powered Vibrant
DISCLAIMER:
This is totally academic, and I only pose the question as that of mere curiosity.
In no way do I mean to accuse any developer here or elsewhere of intentionally or otherwise installing malicious software in our ROMs. Not trying to start a flame war or anything.
What is the possibility that a rogue ROM creator would or could install malicious content on one of our devices? What kind of things would we look for to indicate that our device may be compromised? Perhaps packet sniffing for the extra paranoid.
I am the type that, when I see something that doesn't look normal, I question it. That said, I am a very experience Linux, *BSD, and Solaris administrator; but my experience with Android is just blooming. So I might not know where to look in the Android filesystem, or know which processes may be irregular.
I did some Googling but haven't found anything to indicate this has happened before (thank God). Are there self-checks in Android to prevent this from happening? Call me paranoid, but I just like to know what's going on.
Do the "anti-virus" softwares in the App market actually help with this?
Again just curious. I heard about some apps on the Market that Google had to remotely erase. And I believe I am correct in understanding that Google isn't as restrictive with its applications as Apple.
Any takes on this?
Antivirus and Task killers all that are garbage and slow your phone down. You won't have to worry about that happening on this site.
It depends if he/she is an asshole...
The first "viruses" for android were because people were downloading paid apps on the internet, from some site in china, that had viri put into those apps that people were downloading.
Just dont get on the bad side of a dev.
adrynalyne said:
Just dont get on the bad side of a dev.
Click to expand...
Click to collapse
LOL! I'll make sure not to do that!
I know that task-killers are BS. I figured the anti-virus was a gimmick, too. As far as for self-replicating viruses on the phones I doubt that will occur.
I'm more worried about malware in the form of a sleeper-trojan that calls home with my personal phone information, or gets added to some jack-asses botnet for DDoSing.
That was a worry of mine when I first came to this site, but the dev's I download from I find quit professional. I have since just started to dig into roms trying to port them to the tb, and compare the contents and begin to see what is normally packed in the zip. I have never found a dev on this site attempt to introduce malware. I have seen some intro warz but the site immediately banned them. The site has banned devs for not giving credit were credit is due, and opening multiple accounts in a way to circumvent the system.
This site is great for all, and they do their best to keep everyone honest.
I've been here and ppcgeeks for nearly 3 and 1/2 years, both with winmo and android, and I have never had an issue. It seems that these sites really do the best they can to catch things before they happen. Personally, I can't say enough about our devs. They're great, and they do a good bit of work for people who are honestly not thankful enough to them. I personally don't think you will ever have an issue, as I haven't. And I download tons of stuff from here and other places.
I think everyone is missing the OP's point. OP isn't asking if it's happning now or whether it's happening here.
Instead, the question concerns whether or not it's physicsally possible for malicious code to get executed after installing a custom ROM and/or kernel, assuming the developer of that ROM or Kernel was inclined to put some in there. Assuming it *is* possible, which I certainly believe it is, what if anything can be done by an experienced *NIX adminsitrator to be aware of it?
Is your only option to 'trust' the developer of the ROM or Kernel, or are there things we can do with a runnning android system to know how well the live code is behaving?
I've always been curious of this myself. I am no advanced Linux administrator (yet), just an aspiring IT student. I would think the best people to ask would be the developers themselves, though.
funkybside said:
I think everyone is missing the OP's point. OP isn't asking if it's happning now or whether it's happening here.
Instead, the question concerns whether or not it's physicsally possible for malicious code to get executed after installing a custom ROM and/or kernel, assuming the developer of that ROM or Kernel was inclined to put some in there. Assuming it *is* possible, which I certainly believe it is, what if anything can be done by an experienced *NIX adminsitrator to be aware of it?
Is your only option to 'trust' the developer of the ROM or Kernel, or are there things we can do with a runnning android system to know how well the live code is behaving?
Click to expand...
Click to collapse
No one is missing the point, the op asked if it can happen in roms/kernels/etc. Roms/kernels/etc for the phone are distributed here, therefore he is asking if it can happen here or anywhere that devs create these things for our phones.
BTW an experienced Linux admin should already know how to check for these things
Actually I believe it has happened at least twice. Once by accident, and once there may have been malicious code put into a rom that was set as bate for code thieves.
The first one was stupid, an update agent was left in the rom, and an update got pushed that loaded the phone browser to a certain site (it was not a bad site either). This effected a VERY minor few, as you had to have a certain version of a rom, and have rebooted over a very specific point in time.
The latter I will not go into as I do not know the specifics, or the validity of any of what happened.
g00s3y said:
No one is missing the point, the op asked if it can happen in roms/kernels/etc. Roms/kernels/etc for the phone are distributed here, therefore he is asking if it can happen here or anywhere that devs create these things for our phones.
BTW an experienced Linux admin should already know how to check for these things
Click to expand...
Click to collapse
Sorry if my post offended you and no disrespect intended, but I think you are mistaken. The question of whether or not something "can happen" is fundamentally different from the question of whether or not anyone is actually doing it. Also, saying that any "experienced Linux admin should already know how to check for these things" is in poor taste; it's a personal attack that adds no value to the discussion. The idea here is to address the OPs question as a purely acedemic thought experiment; there is no implict reference to the morality of the developers here...
Perhaps we should ask the same question in a differnet way:
If net-sec researcher working at SANS wanted to test expolitation vectors against their own personal HTC Thunderbolt. Is it physically possible for them to build a custom ROM and/or Kernel such that this custom module includes malicious code that executes automatically after installed on the device?
I'd be highly surprised if anyone claims the answer is no. If the kernel itself is custom, anything the hardware can do is fair game...
Concerning the question of how to know if anything is happening, since we're talking about the firmware itself, it would be difficult to do anything in userspace with confidence. To be really sure, you'd likely need to sniff traffic (both mobile and wifi) as well as physically monitor the hardware's debug output (and perhaps even the circuit traces themselves). With a comprimized kernel, you can't trust anything running throuh the operating system's APIs.
It's very doubtful that any reputable developer on XDA would do this. Impossible? No. But XDA is the kind of place where something like this would be discovered very quickly and spread like wildfire.
Now, some unknown developer, on a random website? While I havent come across this yet, I'd say: More likely.
The question isn't concerning the likelihood of it occuring on XDA or elsewhere, it's specifcally about whether or not it is technically possible to do it.
I think we can infrer from everyone who is answering the unrelated question, i.e. Is it happening on XDA or anywhere else?, that yes, it is possible to insert malicious code into a ROM or kernel.
funkybside said:
The question isn't concerning the likelihood of it occuring on XDA or elsewhere, it's specifcally about whether or not it is technically possible to do it.
I think we can infrer from everyone who is answering the unrelated question, i.e. Is it happening on XDA or anywhere else?, that yes, it is possible to insert malicious code into a ROM or kernel.
Click to expand...
Click to collapse
I think you are right. As long as there is superuser access, then basically anyone with su can pretty much to anything to your phone.
At least that's my take on it.
I'm new to android in general and XDA in particular, so please forgive my ignroance (and yes I will try searching), but this makes me wonder: Do the established developers of custom ROMs and Kernels release their source code? I'd imagine the same terms of the GPL that require HTC to release their source would also require anyone building custom Kernels to do the same. Is this also true for ROMs?
I am an experienced *NIX administrator, and that's what makes me so paranoid. This kernel source isn't coming from a CVS tree that is being scrutinized by hundreds of developers, at least not to my knowledge.
I know how code can be injected into a kernel, into a module, pretty much anywhere. Should I run a diff on the kernel source tree to see what was changed? Could do that, but that may be time consuming. I've seen innocuous kernel modules altered to allow a gateway for elevating to UID 0 (and in fact, more often in Linux than in others.)
I'm pretty confident that the folks here on XDA aren't doing anything malicious: the following of these ROMs are too popular and very fluid, and I would expect something malicious to be found quickly.
Again this is just purely academic.
nerozehl said:
I am an experienced *NIX administrator, and that's what makes me so paranoid. This kernel source isn't coming from a CVS tree that is being scrutinized by hundreds of developers, at least not to my knowledge.
I know how code can be injected into a kernel, into a module, pretty much anywhere. Should I run a diff on the kernel source tree to see what was changed? Could do that, but that may be time consuming. I've seen innocuous kernel modules altered to allow a gateway for elevating to UID 0 (and in fact, more often in Linux than in others.)
I'm pretty confident that the folks here on XDA aren't doing anything malicious: the following of these ROMs are too popular and very fluid, and I would expect something malicious to be found quickly.
Again this is just purely academic.
Click to expand...
Click to collapse
Agreed that the liklihood of stuff here being questionable is low, but the simple fact that there is a non-zero risk certainly makes me think a little bit. You summed it up well and the examples are spot on - this is why I immediately wonderd if developers here are publishing the source code on their customized versions. Ignoring the GPL angle, its just good to know it's out there if it is, and by the same token, also good to know if it's not out there.
I have another question to add. I love miui, and to my understanding miui is made by Chinese developers and it is not open source, it is just translated and ported to our devices. If it is not open source, is there anyway to know for sure?
I am a little bit wary of the security, although I love the rom. I trust all of the credible devs on xda, however I don't know anything about the Chinese devs developing miui. Would the devs porting miui be able to see the malware if it isn't open source
Sent from my ADR6400L using XDA App
It is definitely possible. I read a paper a while back that I've been referencing in my own research where some researchers compiled some kernel modules to do malicious tasks in the background without knowledge of the user, mind you this was on an open source linux based phone system similar to android. Basically compiled in root kits, which replacing your kernel/rom w/ a community developed system would result in possibilities of this occurring. The primary solution to preventing these things from ending up on your phone as well as keeping the Trojans and other malware on the android market come down to the same thing knowing your publisher and being careful what permissions you allow. Like stick to kernels/roms from reputable developers on XDA, and make sure your "movie player" doesn't have access to your SMS system and you'll be fine
Mind you my own research currently is in detection of malware/malicous code & anomalous behavior. As well as hopefully prevention techniques eventually.
We dont allow "whats the best rom?" or "tell me what to run next" threads as it becomes a popularity contest because every phone is different, so you need to try them all and see what you like and what runs best for you.
There are already several threads about which roms and kernels people are running, perhaps that may give you a clue... but you need to try them out on your phone.
Click to expand...
Click to collapse
Yeah, I get that, and wasn't intending to do something that wasn't allowed...
So, allow me to take it in a new direction, please -
With plenty of AT&T i777's out there, why do people seem to get different results by seemingly doing the same thing? You say try it on my phone, and I'd hazard a guess that many have done what I did, yet I saw very few people with the same problems. What are the possible variances?
This is general not question and answer...
Sent from my GT-I9100 using Tapatalk
Thanks... I'm still feeling my way around here... obviously. Guess I gotta figure out how the forums work before I can learn how to make my phone work better.
Apology accepted.
Sent from my SAMSUNG-SGH-I777 using premium space-age technology and tiny invisible lasers
mdaudioguy said:
Yeah, I get that, and wasn't intending to do something that wasn't allowed...
So, allow me to take it in a new direction, please -
With plenty of AT&T i777's out there, why do people seem to get different results by seemingly doing the same thing? You say try it on my phone, and I'd hazard a guess that many have done what I did, yet I saw very few people with the same problems. What are the possible variances?
Click to expand...
Click to collapse
There's about 20 different things that can vary, not counting user's perspective.
ryude said:
There's about 20 different things that can vary, not counting user's perspective.
Click to expand...
Click to collapse
For instance, whether you're in space, or underwater really determines which kernel or ROM works for you. Some people around here say the real place everything varies is on an isolated island with no food or water, just ice skates and a volleyball and your phone with whatever ROM + kernel combo you're using.
Sent from my SAMSUNG-SGH-I777 using smoke signals
Wiilllssooonnn!!!!
Sent from my SGH-I777 using xda premium
Lol
Many things differ. Im far too intoxicated to go in depth, but download a few roms yourself and inspect them. Compare them together and read their logs. You'll really learn a lot by researching in depth.
Different ROMS run differently on every phone. you've gotta find the one that just 'feels' right.
Hope that somewhat answered your question lol
Sent from my SGH-I777 using Tapatalk
I suppose there might be differences depending on what batch your phone was made in. If you look in certain threads, a majority of users might have no problems while a couple have major problems. One time, everyone was having issues with a certain patch, but I found it to run absolutely perfect on my phone.
It's like the battery threads where everyone compares their stock battery. Some people get better batteries than the average, and some get worse batteries.
I try ROMs until I find one that works well for me; I then stick with it until I get bored again.
You will also find that some modem/radios work better in different parts of the country. Also, different kennels may be set up to handle different loads & tasks, meaning that the apps you like to run may play better with kernel "A", but with my setup I might get better performance with kernel "B". People use their phones in vastly different ways, hence, the different user experience.
Example, my wife and I both have this phone but with different ROMS. I put the same kernel on both phones though because i was getting great battery life with it. However, she's not getting near the screen-on time I am because she uses it much differently than i do...she's a chick...Facebook is the devil. Hope this helps some. Just have fun, that's part of the Android experience.
Jank4AU said:
You will also find that some modem/radios work better in different parts of the country. Also, different kennels may be set up to handle different loads & tasks, meaning that the apps you like to run may play better with kernel "A", but with my setup I might get better performance with kernel "B". People use their phones in vastly different ways, hence, the different user experience.
Example, my wife and I both have this phone but with different ROMS. I put the same kernel on both phones though because i was getting great battery life with it. However, she's not getting near the screen-on time I am because she uses it much differently than i do...she's a chick...Facebook is the devil. Hope this helps some. Just have fun, that's part of the Android experience.
Click to expand...
Click to collapse
DITTO! That's hit the nail on the head. All ROMs are different from each other. Even the ones that the same team make (persay) with 2 different versions of the ROM (based on my experience with other phone ROMs). What you will use will depends on which ROM you will select in the long run. For the best performance, battery life, etc... You'll have to decide what you wants out of the ROM then select the one that can handle the tasks that you do.
Just like a personal computer, you could take two identical PCs and depending on the user apps installed and the customizations made by the users they will not perform identically. They will still look the same, but one may not be configured the way the other user prefers it. As the PCs get more use they will change based on user input and configuration. These phones are much the same. A ROM is a very personal choice and while it may look the same on two phones, the way it works is highly dependant upon how the user sets it up, how the use interacts with it, and what apps the user installs. That's why there really is no best ROM, only the ROM that best suits you. Finding it, unfortunately, rquires some personal trial and error to see what works best. No one can tell you what will work best for you.
One thing that bothers me about my Android phone is the opaque, closed-source baseband firmware ("radio" as it's often called here). Since the baseband is interposed between the OS and most hardware functions, its firmware presents a major unknown in the total security of the device.
It's unlikely that the source code for any of this baseband firmware is going to be released, and the open source OsmocomBB baseband is a long way off from supporting Android or the dominant Qualcomm chips. But I would settle for decompiling an existing baseband firmware image, so that I can start to understand some things about it's behavior, and perhaps compile modified versions.
Does anyone know where to begin with this? Many thanks.
I wish somebody participated in this with you. I need it also /
funkydaemon said:
One thing that bothers me about my Android phone is the opaque, closed-source baseband firmware ("radio" as it's often called here). Since the baseband is interposed between the OS and most hardware functions, its firmware presents a major unknown in the total security of the device.
It's unlikely that the source code for any of this baseband firmware is going to be released, and the open source OsmocomBB baseband is a long way off from supporting Android or the dominant Qualcomm chips. But I would settle for decompiling an existing baseband firmware image, so that I can start to understand some things about it's behavior, and perhaps compile modified versions.
Does anyone know where to begin with this? Many thanks.
Click to expand...
Click to collapse
Good idea. Although most probably it'll all be native C code compiled into binary form, not amenable to decompiling.
So you'd probably need a very good debugger and a system call tracing facility in strace.
I guess hell might also break loose because SIM encryption(?), voice encoders(?), network locking(?) and god knows how many of those proprietary tidbits may be sitting in there.
SIM encryption broken leading to duplication of SIMs and leading to smartcard encryption and open source tools to reprogram your credit cards with more money.
That's not hell. That's hell in a hand basket with us enjoying the ride
Keep us posted. It's guys like you who think outside the radio that gave us the TV
For Qualcomm based devices you need to decompile Hexagon code.
For other Intel XMM6260 etc based devices suffice IDA (ARM).
In both cases the raw binary blobs may be encrypted, but extractable from running machine.
I'm working on it, in a fashion, and am writing up a document compiling everything that has been done on cellphone radio hacking. I've not found much on baseband firmware; there's a lot of info out there but it's been tough to find amongst all the other hacking that has similar keywords. Currently most quality info around this subject involve an extra (and depending on desired features; expensive) bit of hardware and two open source software packages with their decencies. As the hardware is currently outside my budget ($300 for the best bang for buck) I'll be working on getting the software to recognize the hardware built in my Android devices. Provided that all goes well I should be able to read and write on the frequencies that the in-built hardware supports and hopefully, as I always get an identical device when getting one, read and write with my backup android device. Be warned if you decide to follow me down this path; there are laws restricting what non-licensed persons/companys can do on certain RF frequencies and this depends on where you live, I'm no expert only a person capable of reading lots of dry informative documents, provided I do achieve direct contact between devices this hack could (and likely will) fry one of my antennas so be warned you'll likely do the same :banghead: so do this on an old device that you don't care about before ever trying on something you use daily. With the warning out of the way lets get down to the quick version.
~~~~~~~~~~~~
Currently all the developing I've found educational has involved the before mentioned "expensive hardware" known as software defined radio, shortened to SDR, go a head and pop open a new tab and Google search either. You'll eventually find that cellphone manufacturers have likely already put these into many devices. You'll also hopefully find the two kickstarters, HackRF ~$300 and bladeRF ~$400, these are likely what I'll be saving up for; HackRF for sure as the next release will likely be able to send and receive at the same time instead of switching quickly between modes. If you dig deep enough you'll find a blog post from a hacker that plugged an Android into a much more expensive SDR and was able to place calls and send/receive text; the blog poster stated something to the effect that this was not a useful hack but I believe that it's a great proof of concept and totally worth another look. However, this hacker has also almost been sewed for some of the demonstrations with this kind of technology involving the capture and description of calls and texts so tread carefully.
The software I mentioned before boil down to GNU Radio and Open BTS; there's dependencies for each but all seem to be installable on Linux running on top of Android. Furthermore I see that someone (I'll edit your name in in a sec Edit: idcrisis ) previous mentioned wanting c or c++ support, GNU Radio uses these languages perhaps I can ask for some help when I get a little further in porting this to run without Linux in the middle so much? I think if we use the GPS to set the time then the signal shouldn't drift to much.
I'm using an app called Debian Kit to give me a flavor of Linux called Squeeze for testing the software. If you choose to try what I'm doing then make use of the readme that the developer wrote or the guide I wrote for general Linux on Android installation and interaction fund in my sig to get started. If you want access to the document I'm compiling then you'll want to PM me at this moment as the chances of hardware frying is high and I'll share a link to Google docs; I'll be releasing a full guide when I've figured out how to avoid damage.
Eventually I hope to port many of the functions in GNU Radio into an app that makes use of internal hardware. Currently I've found a few that make use of hardware plugged into Android through USB "on the go" or "host mode" just search "RTL SDR" in the app store and you'll see'em, but, currently nothing making use of internal hardware. If any are interested in joining forces and helping figure out how to do all this I'd be glad to offer any support I can.
Other things related to cellular antenna hacking other than the above mentioned software and hardware that I'm compiling into the same document. Well this is where we get into the parts I'm hitting the wall on. It looks like I'll have to get into Kernel modification as this is one of the things used to communicate between software and hardware. There's also the flashable files known as radios and I'll be digging further in how these files are modified.
Basically this is a very tough question to answer and has taken many months of reading, searching, and more reading to get this close bit if we all work together I know that we'll be able to modify how the antennas in our devices work.
Edit 01142014- Found a guide on reverse engineering embedded device firmware, the guide is on a router but as the chips in our phones are embedded perhaps the steps are similar
http://www.devttys0.com/2011/05/reverse-engineering-firmware-linksys-wag120n/
Sent from either my SPH-D700 or myTouch3gs or M470BSA
Guide for running Linux on Android that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
^^ NO! The embedded chips in the Linksys routers are MIPS based and not ARM like all our Androids. Very different, although technique is the same.
But thanks, for taking time to check up on all this.
Any updates ?
Hey Guys,
I'm looking into this, I've successfully extracted files from the OnePlus One's baseband, its running RtOS called REX, QC calls it AMSS.
Have a look at the thread here: http://forum.xda-developers.com/oneplus-one/general/discussion-hlos-reverse-engineering-t3292829
Waiting for the OsmocomBB update it projects
QCOM modem leaked sources.
Type in google/bing: "AU_LINUX_ANDROID_JB_MR1_RB1.04.02.02.050.116_msm8974_JB_MR1_RB1_CL3904528_release_AU"
Is there any chance that a Lollipop 5.1.1 rom will be developed for the RK3066? Will it even run on the older HUs?
TIA
ffwd4490 said:
Is there any chance that a Lollipop 5.1.1 rom will be developed for the RK3066? Will it even run on the older HUs?
TIA
Click to expand...
Click to collapse
After finding in other thread that LP for 3188 is in fact 'Frankenstein' 4.4 with LP API level 20 (something used for Android Ware) I guess that there may be possibility to use existing 4.4 kernel of 3066 and just add same API classes.
no..
mtcB will not get real lollipop
RK3066 will not get even the fake lollipop
you need to upgrade to RK3188
doctorman said:
no..
mtcB will not get real lollipop
RK3066 will not get even the fake lollipop
you need to upgrade to RK3188
Click to expand...
Click to collapse
How do you know?
He asked 'is there a possibility'. Yes there is a possibility someon who is true developer to build it. The same way Chinese's did it for rk3188 - using old kernel and adding new API and apps. Only real difference is on kernel level as it is only thing tied to HW (CPU). And as LP is supposedly 'lightier' than KK, even 2 core rk3066 would be good enough and even work better. So technically there is no limits.
So, as I said, there is possibility. If there is true devs to step in instead of these who are just patching and repainting over Chinese's ROMs.
Here on XDA you may find lot of true custom ROMs which are true original development from the scratch instead just cosmetics over stock ROMs.
But I truly doubt that will happen. Here we have no true original ROM development. And thus I may agree with you that rk3066 LP is not possible. Even it technically is.
pa.ko said:
How do you know?
He asked 'is there a possibility'. Yes there is a possibility someon who is true developer to build it. The same way Chinese's did it for rk3188 - using old kernel and adding new API and apps. Only real difference is on kernel level as it is only thing tied to HW (CPU). And as LP is supposedly 'lightier' than KK, even 2 core rk3066 would be good enough and even work better. So technically there is no limits.
So, as I said, there is possibility. If there is true devs to step in instead of these who are just patching and repainting over Chinese's ROMs.
Here on XDA you may find lot of true custom ROMs which are true original development from the scratch instead just cosmetics over stock ROMs.
But I truly doubt that will happen. Here we have no true original ROM development. And thus I may agree with you that rk3066 LP is not possible. Even it technically is.
Click to expand...
Click to collapse
I said it before and I was almost proven wrong by the fake lollipop mtcB ROM but it came out that I was fake.
I worked closely with Joying on this.. they tried and no matter what they did they could not get lollipop loaded on RK3188 mtcB.
considering there is no source code for these around I doubt anyone else spends time on this specially on Rk3066
doctorman said:
I said it before and I was almost proven wrong by the fake lollipop mtcB ROM but it came out that I was fake.
I worked closely with Joying on this.. they tried and no matter what they did they could not get lollipop loaded on RK3188 mtcB.
considering there is no source code for these around I doubt anyone else spends time on this specially on Rk3066
Click to expand...
Click to collapse
And that is where the PK is wrong..
He keeps harping on about fake developers and no one has the skills..
Yet he himself is not a developer.. and is not taking into account that the source code is not released for either the MCU or the layer of Android being used..
It's fine to harp on that there are real developers on XDA ( which as we have not seen any of your work you are not one and there have no credit or the right to bag anyone pulling apart ****ty code)..
So until there is transparency from bottom up by the developers of these machine, then those that are doing their best to at least improve it should be given some credit..
There are numerous examples of **** box's released that have never had code released, as an example the atv1200 .. no kernel codes, and very limited Android core codes released.. thus development was never going to take off and they died a natural death as you can only do so much..
You only have to look over to the tf700 thread and see what Tim has achieved by having SOURCE CODE/DRIVERS..
Actually, comes to mind.. didn't we have a guy doing a crowd funding for some units he was going to make.. how that go?
Anyway PK..you keep banging away on your drum and there are plenty here waiting for you to step up to the plate and provide a true working Fresh ROM for peer review.. or are you just a lurker that had no real skills apart from dropping snide remarks around the threads?
Yes Im developer but not amateur and thus not doing anything here on XDA. Here I just like around and look how some areas are going, looking for new ideas and technical hints. So I don't bite your provocation to provide you something good for free.
From the beginning this all thing was managed wrong. Starting from Chinese crappy product and with that young and inexperienced guy Malaysk who did it all wrong. And you and few others like you helped him to waste time and get to this dead end.
Instead pushing him to learn true Android skills, to learn reverse engineering and spend year or so in truly mastering this units, you applauded him and encouraged him in cosmetics in wasting time on visual appearance and other wasteful and functionaly irrelevant things. And he wasted too much time to face with inevitable: there always will be someone whose taste is different. And we know how emotional he is about his totally amateurish boot logo...
So you helped him to fail. And now you are angry as we all see this is dead end. Yes, LP is Frankenstein full of bugs and empty of functionalities. And he is incapable solving that. As you wasted his enthusiasm on crap.
I tried to help him understand what he should do and what way to go. But he had no capacity to understand and few of you helped him to go wrong way by small donations and loud applauding.
I wonder if you are short-sighted or just like someone else here is working for Chinese's?
Only they have interest noone reverse engineer these units and allow people with existing HW get good new ROM! Which is technically possible. And yes I know that as I'm very profound in such things.
Great...
If you have ever run a team of coders then you know the time and effort it takes..
And yes, we are in agreement on that the 'Original' base is full of bugs..
So leave it alone and move on as until you put forward your own fix's then carry no cred but come off of just another keyboard warrior..
And yes, I have worked in Silicon valley and China with coders so I am comfortable calling you out on your attitude in these forums.. as you are carrying on with personal attacks on the only developer that has put forward any work on these forums in English and dared to open himself to guys like yourself.
Fine you have posted other Russians work and thats all good too..
Fundamental rule ... learn by mistakes .. and keep on learning..thus this is what these pieces of equipment are..
As stated in other threads.. good things are happening in this area so a few years from now your ranting is mote..