Related
Hello!
I see all these advices on making a ROM. But these advices and the issues they deal with are IMHO not the real issue. If you have a Nexus One phone and want to modify the Android OS there's nothing stopping you. It's "easy". It's all "there".
But what if you have a new Android phone which has proprietary driver code and made by a company that has NO interest in sharing it's code or make it easy for you to root your phone? Making ROMs for these devices is the interesting thing to talk about. Otherwise you can change the name on this forum part to: "Make ROM = *.android.com"
So these two issues are the most important ones IMHO:
1) Devices DO get rooted. So some people must know how to get there. I assume that there is no "one way" of doing this but it would be nice to discuss this and make some sort of a list on what to THINK about.
Many devices will never get rooted because the brand is despised here. That is why it would be good to have some general knowledge so others that ARE interested in these despised brands can take action.
2) You have a rooted device. You load a standard Android OS ROM. All proprietary drivers are lost and thus many features and maybe whole hardware units are unavailable to you. How do you locate and use unsupported hardware in your ROM?
I understand why many "elite" devs have a Nexus One since there are no propietary driver code in that one and rooting was easy. So the doorway to the Nexus One Kitchen is wide open. But what about the rest of the new Android phones that are out and will come. Why don't you discuss and explain the general thinking in rooting a device and finding/using hardware/features that are lost because of proprietary driver code.
Thanks for your time
BR
Robert
Wow, you really need to do some reading is all I will say.
carz12 said:
Wow, you really need to do some reading is all I will say.
Click to expand...
Click to collapse
+1. i don't even get his problem tbh.
can someone please help me understand the major issues of porting android to the hd2? devs from htc can obviously get android running perfectly across numerous hardware platforms, so why is it so hard for anyone to port any version of android to the hd2 without some type of bug or problem? you can flame me all you want I just want to know what the major hurdles are so I can have a better understanding. Is it that HTC doesn't give you guys enough info on the hardware? is htc purposely holding back info from you guys so it's impossible to succeed? The hd2 has been out for ages and as far as I know, there is not one 100% fully working port of sense or stock froyo to the hd2 that I have seen.
It says right at the top of the forum.
READ BEFORE POSTING.
http://forum.xda-developers.com/showthread.php?t=734335
You must be able to read some English, even if it is one giant block of text...
Read everything in that thread, THEN ask a question, in the appropriate section.
You have no idea how much work is involved in porting over an operating system, or creating drivers from scratch. You sound like an ignorant moron, and that is not me flaming you, but being honest.
I have a 100% working version of Android on my HD2, and I have had it for more than 2 months now. You're probably just doing it wrong, because you have failed to read the stickies.
Read the stickies.
Good luck.
Custom drivers to initialize the hardware. The problem is that when you don't have the proper hardware schematics or internals, you have to write them from scratch and/or piece code together in order to get it to work.
The main issue is around creating things from scratch at times - very hard to do when you don't have the hardware particulars to build the code from.
Make sense? It's NOT an easy process at all. And yes, the hardware IS different between a lot of the phones. Anything from screens to CPU's to antennae configs, etc.
No idea what are you talking about, I am using Mdeejay Froyo Sense 2.4 and it is working 100% for me, every function i use on a daily basis works as well as when my HD2 was running WM if not better. As mentioned in the replies above, read, search if you feel your Android isnt working to your liking. If you do not understand how difficult it is to port an OS onto a device, research about it and you will understand these devs have done so much in such a short time and they rival any group of highly-skilled SW engineers that any tech company would love to get their hands on.
FriedSushi87 said:
It says right at the top of the forum.
READ BEFORE POSTING.
http://forum.xda-developers.com/showthread.php?t=734335
You must be able to read some English, even if it is one giant block of text...
Read everything in that thread, THEN ask a question, in the appropriate section.
You have no idea how much work is involved in porting over an operating system, or creating drivers from scratch. You sound like an ignorant moron, and that is not me flaming you, but being honest.
I have a 100% working version of Android on my HD2, and I have had it for more than 2 months now. You're probably just doing it wrong, because you have failed to read the stickies.
Read the stickies.
Good luck.
Click to expand...
Click to collapse
so you're telling me you have 100% working version as original as far as battery drain, tethering, camera, wifi, boot time, call quality, etc etc? if so, which one is that? seems I missed it somehow.
ruinertt said:
Custom drivers to initialize the hardware. The problem is that when you don't have the proper hardware schematics or internals, you have to write them from scratch and/or piece code together in order to get it to work.
The main issue is around creating things from scratch at times - very hard to do when you don't have the hardware particulars to build the code from.
Make sense? It's NOT an easy process at all. And yes, the hardware IS different between a lot of the phones. Anything from screens to CPU's to antennae configs, etc.
Click to expand...
Click to collapse
then it sounds to me like HTC is crazy, why would they change each hardware so much and have to re-invent the wheel constantly?
If u read my last reply in a previous post, NO QUESTION IS A DUMB ONE! Thats why these forums are here. Now I'm not a dev nor am I that tech savvy but I wud assume that the software has to match the hardware. While different companies make multiple devices, u wud think it shouldn't be hard to root one from the other, understand that each device has different hardware specs, therefore requiring hardware specific software. Hope that helps. As for the other guy telling u to read all the threads to find wut u are looking for, not everyone has the time to read thru all the threads to find the answer to a specific question. Sometimes it's easier to just ask the question in hopes that someone who knows the answer wud reply.
microse23 said:
If u read my last reply in a previous post, NO QUESTION IS A DUMB ONE! Thats why these forums are here. Now I'm not a dev nor am I that tech savvy but I wud assume that the software has to match the hardware. While different companies make multiple devices, u wud think it shouldn't be hard to root one from the other, understand that each device has different hardware specs, therefore requiring hardware specific software. Hope that helps. As for the other guy telling u to read all the threads to find wut u are looking for, not everyone has the time to read thru all the threads to find the answer to a specific question. Sometimes it's easier to just ask the question in hopes that someone who knows the answer wud reply.
Click to expand...
Click to collapse
you guys are all the best, and that's why I posted my question here. Yes the search feature is a PITA in it's own right, with the captcha bs and 1000 search hits. I could spend another hour refining my search, or spend 2 mins asking the question. If everyone expects people to search first then at least it should be faster or equal to just asking the question, then people would use it more I would think.
initzero said:
then it sounds to me like HTC is crazy, why would they change each hardware so much and have to re-invent the wheel constantly?
Click to expand...
Click to collapse
Each software has certain hardware needs to work. Obviously HTC is raking in millions and millions, so I wouldnt say they are too crazy.
Just because we can get a lot of different ROMs to work on our phones does not mean that all phones can handle all versions of Android and run perfectly out of the box. Although it would be cool.
thanks guys, so it seems the root issue is that HTC really does change their hardware fairly drastically between models and that just seems so insane to me. Why would they do such a thing? It seems so counter productive, and adds so many extra costs. That really sucks but I guess they have the $$ to do it with their stock being up there above google's.
I realize now that htc really is making (figuratively speaking) an apple, a pc, an xbox, a nintendo ds, a psp, a palm etc and getting their OS to run on it. That is really unbelievable. It must be a requirement of the different carriers. Pretty amazing how they were able to do that if you think about it. No wonder it's a nightmare for the devs here. That is exactly what I needed to know and it makes everything very clear now, thanks everyone.
p.s. microse23 you're always so nice, thanks man I appreciate it
initzero said:
so you're telling me you have 100% working version as original as far as battery drain, tethering, camera, wifi, boot time, call quality, etc etc? if so, which one is that? seems I missed it somehow.
Click to expand...
Click to collapse
please elaborate what y
you mean by battery drain. obivously the battery is going to drain, constant use of the SD card will do that to a phone , as far as boot time is concerned have you ever booted into a Linux live disk? it isnt all too fast is it? hmmmm i wonder why android take a sec to boot.... and here is a working rom for you: Nexus to HD2. I am using it and it works great! GPS lock in like 20 sec for me, sd is fine, tethering works, camera works (5mpx) boot time is about the same as my mytouch 3G slide after HaRET, call quality is clear no robot voice, apps from market install, HD youtube works. little to no touchscreen freezes, screen wakes up fast. (<--run-on lol) seems to be working 100%...
You don't understand how a computer runs.
There are apps that run ontop of runtime environments which are connected to the OS, the Kernel through the API (applicaiton programming interface) and then that talks directly to the hardware via the Hardware Abstraction layer, which is made up of a bunch of drivers which are individual files that detail what language and what commands are to be sent to a device to make it do certain things, which change with each device, which each screen resolution change and new technology or tweak on old technologies. Especially with the radio where it changes from 2G and 2.5G and 3G and H and H+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
APPS
API
OS
DRIVERS
HAL
HARDWARE
why can't they port a perfect copies? MONEY!...HTC paid their employees millions of dollar to put this thing together and make it run. Here at XDA, we have geniuses but they are working own their own time and reverse engineering isn't easy. I guess it would be like walking in a maze that doesn't always have an exit. Another thing, HTC is not exactly giving away much information on their hardware too which makes thing harder.
Think about it, we still can't get a PERFECT snes Emulators. They work and have MORE features than the original hardware console but still have issues.
Making software/os work on hardware that's not intended for isn't always clear cut.
encrypti0n said:
Nexus to HD2. I am using it and it works great! GPS lock in like 20 sec for me, sd is fine, tethering works, camera works (5mpx with 720p)
Click to expand...
Click to collapse
What.
Did I miss this?
FriedSushi87 said:
You don't understand how a computer runs.
There are apps that run ontop of runtime environments which are connected to the OS, the Kernel through the API (applicaiton programming interface) and then that talks directly to the hardware via the Hardware Abstraction layer, which is made up of a bunch of drivers which are individual files that detail what language and what commands are to be sent to a device to make it do certain things, which change with each device, which each screen resolution change and new technology or tweak on old technologies. Especially with the radio where it changes from 2G and 2.5G and 3G and H and H+.
APPS
API
OS
DRIVERS
HAL
HARDWARE
Click to expand...
Click to collapse
I assume you mean me? I do understand how a computer works as I repair them, the LiveCD/usb thing was very vague comparison.
shadiku said:
What.
Did I miss this?
Click to expand...
Click to collapse
OHSHI- thought I read it in the post was WRONG, my bad disregard that. FIX'D
Key points missed so far.
When HTC gets hardware from a supplier (Eg Qualcomm) they include driver source. Hardware API's etc for HTC to quickly develop drivers. Guys like Cotulla don't have access to this information so they clip some code from here, there and everywhere.
The hardware may be the same but the Bios (Radio) also defines how that HW is presented to the OS. The radio for a WM phone may present the hardware differently to an android phone. This needs different drivers.
There are 1000's of components and features in a phone all comprising of different models, revisions and manufacturers.
Cotulla and the guys work for free in there spare time. Big difference compared to being paid as part of a team of 20 people to do the job.
So in summary. What the guys are doing is trying to build there own UFO using photo's of an alien UFO that no one even understands the technology or how it works.
Would be a lot easier if the aliens left the instruction and design manual in the glovebox
Hi please stop this thread
Hi to the person who started this thread if you are so smart stop asking questions and read between the lines ,do you have any idea how an os is built and how programs are written in different languages,please google and find your answers rather than wasting the developers hard time they are spending at developing the android builds.please dont spend your valuable time answering my reply rather google your question you may get more info towards your required answer.
Please to the moderator stop such threads unless they are reporting build problems.
Guys (and girls ... if any are reading .. )
After some tinkering about (for days now) with Mango build 7720 (Thanks again YUKI + XBOXMOD!) I can confirm that the many of the issues present in Mango Beta are now gone ... Ok granted the MicroSD gets encrypted but its not meant to be removed on an original WP7! You can refer to Yuki's thread on how to unlock your MicroSD card if you don't fancy the likes Microsofts OS and want to revert back to Android .....
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way. Have been using it some years now on a daily basis. I am willing to provide my help. I hope that anyone could help along maybe we create yet another open source bootloader which does the trick.
Hoping to hear from you so we get something going ...
Regards
Al
I would really like to hear from some devs I am more than sure that the community would be very grateful.
Secondly (courtesy of warriorvibhu)
I suggest that you all Sign this Petition.. Kindly inform all fellow HD2 owners to sign it ... especially if they were impressed by WP7 on HD2.
Alcatrazx said:
Guys (and girls ... if any are reading .. )
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
No there are some issues in camera and sound with android but is related to incomplete kernel. They are not related to each other for example no multi touch issues on android. All those issues are related to not perfect drivers hd7 is using another touchscreen panel I guess and maybe different speakers and camera. Anyway those drivers are complexed to write because we dont get source from microsoft on how to write them.
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Theoritically yes but CLK is designed to load an linux kernel. So if we want that we need to write a complete new bootloader.
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
Yes but you need to go backt to Windows 6.5 and read out the current drivers and port them to windows phone 7 properly. But you will need a JTAG for it and you must be very skilled.
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way.
Hoping to hear from you so we get something going ...
Regards
Al
Question
Click to expand...
Click to collapse
Hope this make some stuff clear.
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
We need an asm developer for try to fix multitouch problem... or the source code of driver...
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Just hope that's will come soon, I cant wait it !
However, I also hope the Mango will worked with flash and include more apps in the marketplace.
Fisher_9511 said:
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Click to expand...
Click to collapse
Its not working in any of multitouch Games.
Nice thread,curious to See the answers, definitely camera is a big issue for me, hope it get fixed soon.
Sent from my HTC HD2 using XDA App
Dont forget the need to use the "batterytrick"
good thread by the way
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Try to think positive man... Have you ever seen the arm listed file? We need to find a timer between the two finger... would not be so so so hard... but only hard...XD
TonyCubed said:
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Click to expand...
Click to collapse
Hi and thanks for the feedback. With a negative attitude the thread will lead to nowhere yes. That was what people said a year ago when they said that WP7 will never run on the HD2 but the devs ultimately got there. Thanks for answering the question re the Android drivers though.
You are RIGHT that the drivers in WP7 are closed source drivers ... so is MAGLDR. Rewriting another bootloader (if needed) which does not have all the frills of MAGLDR but which is open source could be a possibility.
I am not interested in getting into the WP7 ROM and modifying the drivers built in ... We have to use a technique similar to what they use when creating emulators by reverse engineering ... The most die hard emulators out there such as some of the Playstation emus out there were all closed source but it did not stop the devs from doing a proper emulation of the console.
I'd really appreciate if you could be more specific when you said that we are using the stuff which was leaked from the original "LEO" ROM ... as far as I know, is it not the Schubert which was leaked? Correct me if I'm wrong ... We got too far to give up just now...
Multitouch games do not work .. with the current Multitouch driver .. mainly due to the finger position bug .... This is explained in detail on youtube.
Sound is distorted because the input gain is too high ...
Let's not speak about the camera for now ... I think those are the two major issues which need to be remedied for now. Hopefully this thread will get us somewhere.
Regards
Al
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
backlashsid said:
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
Click to expand...
Click to collapse
Nicely said and many thanks
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
Click to expand...
Click to collapse
That is not exactly fixing the issue... It just modifies the maxima and minima ... The sound (input gain) is too high making it sound distorted from the HD2. The fix does remedy this a bit but its ... erm not really fixing the problem.
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
dazza9075 said:
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
Click to expand...
Click to collapse
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
backlashsid said:
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
Click to expand...
Click to collapse
I'd say... let's do this! If we get enough people, and those will send emails like everyday, then why not? There's nothing to lose
IF, and its a big IF, we are going to get it working better its going to need ideas like the comment from backlashsid to get unofficial support from these companies
In my humble opinion there is little chance of getting anything else working better without the support of people in the loop, essentially that means HTC and Qualcomm, but remember that by getting the HD2 running WP7 we are costing them money in lost sales, so there is little incentive for them to support us in an official capacity, what we're looking for is an insider!
it doesnt hurt hunting for new devices with the same hardware but its unlikely anyone would use old gear.
This would be nice so then we (as the community of XDA) can show off our HD2's as the beast-mode phone and bestest phone ever!
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
My Atrix got it's case cracked and the touch-screen display died, and given I already got a replacement phone I feel a bit adventurous. I wanted to see if I could build my own computer with what remains, so I wanted to run Linux natively (no Android). Given that there's a Linux 4 Tegra from Nvidia:
Is there a chance that I could build my own distro based on that?
Should I use another kernel (like the one currently used in gingerbread or CM7)?
Please note that I'm not trying to do webtop.
I thought of building my own handheld with the Atrix, or what remains of it. So any tips on how to get started would be great.
Cheers!
wrong section
ovitz said:
wrong section
Click to expand...
Click to collapse
Umm... what section would you suggest other than Q&A?
It was moved. Sorry 'bout that. I was under the impression that development questions were on the other forum...
"Android development" is in the description. I think they keep that forum just for Android-specific things, even though Android is just a flavor of linux.
tonglebeak said:
"Android development" is in the description. I think they keep that forum just for Android-specific things, even though Android is just a flavor of linux.
Click to expand...
Click to collapse
You're being way too literal. It's been used for all sorts of non-Android dev multiple times. Right now, Boot2Gecko is right there. The fact of the matter is that when it pertains to dev questions, this post would most likely be answered there. I'm pretty sure it'll die here on this forum with barely any useful answer, if at all.
The development section is mostly for things that are "in progress", ie. with "something to show". Questions, discussions and ideas go elsewhere.
As for your question, I believe I've seen a thread about this already, and quite recently too.
ravilov said:
The development section is mostly for things that are "in progress", ie. with "something to show". Questions, discussions and ideas go elsewhere.
As for your question, I believe I've seen a thread about this already, and quite recently too.
Click to expand...
Click to collapse
I've checked a few that I've found on the forum, but most had no answer and were about other devices. With regards to the Atrix or the Tegra, I've only found threads about webtop.
Not to argue too much about this too much, but I've seen threads that started with nothing in the dev section. Like the Kernel porting project that started as a mere placeholder for the project. Point is, I've done my research and found no pointers to the questions I have. I made it in case another dev had an idea about it. I may have missed something, but that's why I asked in the first place. If I believed I had covered all grounds by myself, I wouldn't have asked in the first place.
Lugaidster said:
I've checked a few that I've found on the forum, but most had no answer and were about other devices. With regards to the Atrix or the Tegra, I've only found threads about webtop.
Not to argue too much about this too much, but I've seen threads that started with nothing in the dev section. Like the Kernel porting project that started as a mere placeholder for the project. Point is, I've done my research and found no pointers to the questions I have. I made it in case another dev had an idea about it. I may have missed something, but that's why I asked in the first place. If I believed I had covered all grounds by myself, I wouldn't have asked in the first place.
Click to expand...
Click to collapse
What you're looking to do seems similar to this question: http://forum.xda-developers.com/showthread.php?t=2110161
The difference between the webtop and a stand alone installation of Linux won't be that different, mainly it would just be where on the device the OS is installed and how video is handled. That said, I'm not sure about the kernel, specifically the video drivers, since they're intended for Android and may not be compatible with X. AFAIK, Wayland is closer to Android than X is, but Wayland isn't quite ready.
Anyway, assuming you did succeed, what you would end up with would be less like a true desktop (as you'd be pretty much locked into a specific kernel, and therefor any packages limited by it, but it doesn't invalidate the effort), and more like a persistent live CD, since the OS would be installed to an area mounted as read-only (to prevent flash wear), with access to an area that has read/write access, like in Android where you store apps and user files. Overall, it could be fun if you enjoy a challenge and aren't intimidated by soldering and using the JTAG connector.
lehjr said:
What you're looking to do seems similar to this question: http://forum.xda-developers.com/showthread.php?t=2110161
The difference between the webtop and a stand alone installation of Linux won't be that different, mainly it would just be where on the device the OS is installed and how video is handled. That said, I'm not sure about the kernel, specifically the video drivers, since they're intended for Android and may not be compatible with X. AFAIK, Wayland is closer to Android than X is, but Wayland isn't quite ready.
Anyway, assuming you did succeed, what you would end up with would be less like a true desktop (as you'd be pretty much locked into a specific kernel, and therefor any packages limited by it, but it doesn't invalidate the effort), and more like a persistent live CD, since the OS would be installed to an area mounted as read-only (to prevent flash wear), with access to an area that has read/write access, like in Android where you store apps and user files. Overall, it could be fun if you enjoy a challenge and aren't intimidated by soldering and using the JTAG connector.
Click to expand...
Click to collapse
Actually, I might have to do soldering anyway. I'm not really intimidated by it and don't really care all that much for phone functionality and such. I'm not even interested all that much in X as my project is more towards transforming it into a handheld gaming (more like emu) device. I don't mind compiling software specifically for the system. The question is pretty low-level in that regard for me. I want to know if I have to do anything with regards to the kernel since it's specific to Android. Given that most emus I know that would run acceptably in a tegra 2 don't really need the GPU, I don't mind just using framebuffer so HW doesn't really interest me.
Lugaidster said:
Actually, I might have to do soldering anyway. I'm not really intimidated by it and don't really care all that much for phone functionality and such. I'm not even interested all that much in X as my project is more towards transforming it into a handheld gaming (more like emu) device. I don't mind compiling software specifically for the system. The question is pretty low-level in that regard for me. I want to know if I have to do anything with regards to the kernel since it's specific to Android. Given that most emus I know that would run acceptably in a tegra 2 don't really need the GPU, I don't mind just using framebuffer so HW doesn't really interest me.
Click to expand...
Click to collapse
Unfortunately, it's going to be one of those areas where you'll have to make an educated guess, since as far as we know, no one has successfully pulled off a straight Linux implementation on the device.
That said, nVidia does have both Android and Linux images for the Ventana dev kit, so it should be possible. In my case, I would compare the source code for their Linux kernel vs the stock Linux kernel vs their closest Android kernel vs the stock Android kernel. The biggest thing is how the the device specific files translate from one kernel to another, because you'll likely need to translate the device specific files for the Atrix in the same manner. The changes may be subtle or they may be drastic. The main thing is to just be able to set the pins properly so you don't release any "magic smoke". Unfortunately, I see no source code for any of nVidia's kernels.
Anyway, that's how I would do it, but I do suspect that someone with more knowledge could find a much simpler approach and hopefully they'll chime in, but this part of the forums isn't the thriving hub of activity it used to be, so I don't know if that will happen any time soon or at all.
lehjr said:
nVidia does have both Android and Linux images for the Ventana dev kit
Click to expand...
Click to collapse
Atrix is a Whistler, not a Ventana.
http://forum.xda-developers.com/showthread.php?p=33289027#post33289027
ravilov said:
Atrix is a Whistler, not a Ventana.
http://forum.xda-developers.com/showthread.php?p=33289027#post33289027
Click to expand...
Click to collapse
Thanks for the heads up and the link! :highfive: