Related
Hey guys,
I'm searching for an Android version that has everything working, i.e. Camera, GPS, WiFi...
I know this was possible with Android 1.6, there were several versions, some had the camera working, some had WiFi working - but none had everything working.
But it proves that it's possible.
Why are people only working on Android 2.x anymore, when there are so many things not working and probably never will?
And why make so many different versions with none of them working 100%? Can people not work together and create ONE version that has everything?
Please, if there is any Android (likely 1.6, cause 2.x seems impossible to get fully working) version that has everything working, direct me to it. If not, why not come together and try it?
If you feel it is this easy, why not do it yourself?
I believe noone has made a fully working distribution yet due to the fact that it is difficult. Add the fact that most of the chefs does this as a hobby, and you might understand why it is hard to get developers to spend a lot of time on it.
My two cents.
-KJ
-------------------------------------
Sent via the XDA Tapatalk App
Well, if you actually read my post, I said all the necessary stuff is there for Android 1.6. It IS possible.
The problem is just that people can't work together. There have been 1.6 versions with the camera working, and others with WiFi working, and others with GPS working, but none with everything.
But it's clear that it would be possible, if people put the pieces together.
Unfortunately, nobody seems to be working on 1.6 anymore. It's clear that 2.x will NEVER be fully working on the Touch HD, so why do people waste their time on that?
I am sure we could have a fully working Android version. It doesn't have to be the newest one, but at least it would be good for everyday use.
Well camera was never working on Touch HD and stuff you mentioned aren't about Android version. Those hardware issues are mostly linux kernel related and only way to fix them is to write a proper drivers and modules - and that's the tricky part. Simply put: Android version has nothing to do with non-working hardware on our devices.
I remeber I had the camera working... or was that another device? I have too many phones lying around here, but actually I am pretty sure I had the camera working in an older Android version.
shaundalglish said:
blah blah...
I know this was possible with Android 1.6, there were several versions, some had the camera working, some had WiFi working - but none had everything working.
...blah blah...
Click to expand...
Click to collapse
hey man, wake up!
You 're just frustrated but you do not propose anything.
Thx for this usefull thread
shaundalglish said:
Well, if you actually read my post, I said all the necessary stuff is there for Android 1.6. It IS possible.
The problem is just that people can't work together. There have been 1.6 versions with the camera working, and others with WiFi working, and others with GPS working, but none with everything.
But it's clear that it would be possible, if people put the pieces together.
Unfortunately, nobody seems to be working on 1.6 anymore. It's clear that 2.x will NEVER be fully working on the Touch HD, so why do people waste their time on that?
I am sure we could have a fully working Android version. It doesn't have to be the newest one, but at least it would be good for everyday use.
Click to expand...
Click to collapse
This is a TOTALLY misleading post.
The number of devices, the variation in hardware and memory is quite extensive... yes, somebody MIGHT get the camera working on ONE specific device... this is hardly a version of Android everybody can enjoy.
For the large part most of the developers ARE sharing knowledge, but there are people screaming "why isn't MY device supported, and other saying why are your bothering with old version of Android, and others screaming, where's Froyo???"
XDAndroid's come a long way. But there are only a handful of developers working on it, and they don't have every single phone at their disposal (not to mention every operator variant with slightly different radio code and configuration).
Each week the development takes two steps forward, and one step back... but it's progress. All that you're asking for is more progress.... and the only way you can get that is by contribution the code changes to the dev team.
If you can't do that, then you just have to sit back and wait.
shaundalglish said:
It's clear that 2.x will NEVER be fully working on the Touch HD, so why do people waste their time on that?
Click to expand...
Click to collapse
How is it clear? It's being worked on... perhaps at a pace that's not to YOUR liking, but it's being worked on.
What evidence do you have to suggest it will NEVER be fully working?
It is true that it's proving to be difficult, but it's also true that it's very hard to stay with 1.6 when many new apps stop working with it, or new features NEED 2.x, and all the latest source code will include support for newer devices and 1.6 won't.
The developers aren't working on HD alone, they are working on a release that works on multiple devices. If someone wanted to focus on HD, they'd be welcome to, but nobody is. They are sharing their knowledge for the greater good of all devices.
To be frank, if someone is truly that crazy for Android, then they are fools to be using a WinMo device. They should have bought an Android device.
If I want OSX, I should buy a Mac. The fact that I can run OSX on my PC is nice, but I should expect issues. The same applies to XDAndroid. Expect issues.
TheBrilliantMistake said:
How is it clear? It's being worked on... perhaps at a pace that's not to YOUR liking, but it's being worked on.
What evidence do you have to suggest it will NEVER be fully working?
It is true that it's proving to be difficult, but it's also true that it's very hard to stay with 1.6 when many new apps stop working with it, or new features NEED 2.x, and all the latest source code will include support for newer devices and 1.6 won't.
The developers aren't working on HD alone, they are working on a release that works on multiple devices. If someone wanted to focus on HD, they'd be welcome to, but nobody is. They are sharing their knowledge for the greater good of all devices.
To be frank, if someone is truly that crazy for Android, then they are fools to be using a WinMo device. They should have bought an Android device.
If I want OSX, I should buy a Mac. The fact that I can run OSX on my PC is nice, but I should expect issues. The same applies to XDAndroid. Expect issues.
Click to expand...
Click to collapse
Very well said. These people never stop complaining.
shaundalglish said:
I remeber I had the camera working... or was that another device? I have too many phones lying around here, but actually I am pretty sure I had the camera working in an older Android version.
Click to expand...
Click to collapse
Sorry buddy, but you're not recalling right, the camera has never worked on the Touch HD, no matter how old the version was (and GPS support only came recently a few weeks ago).
Camera support & GPS are a kernel feature (simply put, the kernel is all the drivers for the hardware in the devices and the way to properly communicate with them) it is not an android feature (android operates on top and apart of the kernel).
I can't comment on the other devices but I don't recall having a winmo device having his camera supported in android, they have a really hard time implementing camera support in the kernel, so they did go on with the other things such as better stability, speed and battery life...
But if you have the resources, feel free to help, xdandroid team will be happy to welcome another dev.
Becoming a bit of a flame war and I see no end result.
Thread closed
i would like to post this thread to ask all the PRO here,
what would u pick if i ask you to just select one OS for ur Ralph?
WinMo?
Android 2.2?
i am seriously thinking to change it from WinMo.
what do you think?
myself will be switching perm to android on my raph very soon as progress has moved forward alot on it only a couple things like camera and battery life ..but from what i understand they may be close to working and fixed
meego for opengles v2
But seriously android.
but yeah seriously i dont know anyone whos tried android and wants to go back to slow crappy winmo.
I can totally agree on it!
From the early stage of kaiser android development, even with almost nothing working, it was still better then winmo. Now kaiser is working cometely and its way better then winmo.
Im not using my touch pro as a phone right now (primarilly because of battery life), but as soon as thats fixed its donating time again and switching to android on touch pro.
Does anyone know the progress on nand for touch pro (and could the same menu from kaiser be used for it to install?)?
Sent from my Full Android on Vogue using XDA App
As soon as Android is flashable - it's bye-bye WinMo for me...
Once camera is working and better battery management levels are obtainable on my touch pro, i won't be going back. I already love everything about android and the games and apps i've been using.
OH, and my whole data signal just stopping after some time for no reason, even though my sprint APN still shows and is checked.
how about run on system memory
anyone know the diff between running the android from memory or from the system memory, will we gain extra speed if we use the system to run?
and will that damage the winmo OS if so?
thanks in advance.
p.s. the launcher pro is expired and i want to install a new one but it will need me to remove/uninstall the previous one.
i try the "application manager" in "settting" but i can't select the "uninstall"
any expert can teach me how?
million thanks in advance.
It's not Ralph, it's Raph
But seriously, I prefer Android more. I use it daily and it rocks!
djdafreund said:
Once camera is working and better battery management levels are obtainable on my touch pro, i won't be going back. I already love everything about android and the games and apps i've been using.
OH, and my whole data signal just stopping after some time for no reason, even though my sprint APN still shows and is checked.
Click to expand...
Click to collapse
Use viruscrazy's kernel regarding the battery management issue.
gm112 said:
Use viruscrazy's kernel regarding the battery management issue.
Click to expand...
Click to collapse
Yeah, i've been highly following and testing viruscrazy's kernel, and it's awesome compared to stock, but he even mentioned you can't use his stuff along with the newest 2.2 (sept.16 release) since there are lot's of new differences that would cause problems. But until then, his stuff does make a huge difference in properly registering battery level's (within 10% tolerance on my touch pro at least, much better even on other devices.)
Bluetooth also needs some work. I'm not sure the FM radio works in Android.
i'm kinda noobie here..
Are all the application we can use in android can also be use in xdandroids?
mizu_ai said:
i'm kinda noobie here..
Are all the application we can use in android can also be use in xdandroids?
Click to expand...
Click to collapse
Eh, for the most part... Not every app will work guaranteed tho. Just try it out, let us know how it works...
I don't get why you posted this question in this thread tho!
wow, i´m really excited to read this posts! i've had my raph for 2 days now and i am really happy with it already flashed winmo 6.5 but i'm really anxious to try out android
I have a question. I have a brand new never activated or used sealed touch pro that I'm thinking about opening and activating just so I can use android on it. But I wanna know is the phone going to have the same battery over heating and freezing issues if I'm using android as if when wm is used. Is those problems os related of phone hardware related?
if so I rather use android on the touch vogue if I'm going have the same over heating issues on the touch tiamond andtouch pro. Or just use wm on my yreo pro.
AL_CAPONE_X3 said:
I have a question. I have a brand new never activated or used sealed touch pro that I'm thinking about opening and activating just so I can use android on it. But I wanna know is the phone going to have the same battery over heating and freezing issues if I'm using android as if when wm is used. Is those problems os related of phone hardware related?
if so I rather use android on the touch vogue if I'm going have the same over heating issues on the touch tiamond andtouch pro. Or just use wm on my yreo pro.
Click to expand...
Click to collapse
Vogue port is basically complete as I understand it. Can't guarantee you won't have issues on your TP. This devices port isn't quite done yet...
the statistical numbers are: winmo:21 vs android 46.
Well, have to say people came to this thread since they like android and use android daily, so the testing result may not be true. It should be more correct by making this survey on the first Fuze discussion site (let Fuze winmo users and android users vote together), just my $.02
For me, 1st Fuze is a phone, dialing effect, talking time and standby time are the most important things to me; 2nd it is an email receiver, web browser; 3rd it is a GPS; 4th, a toy that I can play (games or a brick I can throw )
Android has smoother touch feeling and nicer looking, but for the short battery life and no camera fixed, I will still using my winmo for now.
Windows mobile.
Android is still lacking.. touch screen issues, camera. Our devices dont have a compass. So none of the augmented reality programs will run on our phone.
Ive never been able to get the touch screen to work to my liking. Ive done the touch configuration literally 100s of times. The screen is still off when i touch it. (holding down an icon to move/delete can be very frustrating)
I use Android to play a few media apps (iheartradio) that we just dont have on WM. Other than that, I boot back to WM.
There are many explanations that people will tell you to the answer to the "what is a kernel?" Like this great one from Omnicide
Spoiler
Omnicide said:
The best way i seen it put was, think of the kernel as the engine and the rom as the body of the car. The body of the car (rom) just makes the car look nice and user friendly. Now when we talk about the engine (kernel) simply put red lining the engine will get you to go fast but burn gas. Keeping the rev down low will make you run slower but saving lots of gas. Thats just one way to look at it, rpms being the cpu.
Click to expand...
Click to collapse
or this great one from androidcentral.com
Spoiler
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example --when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
. You probably didn't get it at all, so let me tell you what a kernel is in about 17 words. A kernel is "what makes the phone work, and connects the hardware (camera, storage, etc.) And the software (the Rom)."
I don't want to be thanked for this, thank omnicide, and androidcentral.com for the great explanations.
~~~~~~~~~~~~~~~~~~~~~
Samsung galaxy s2
Rom: Jedi knight 6
kernel: Jedi kernel 2
~~~~~~~~~~~~~~~~~~~~~
And you thought celebrities weren't smart! =P
Kernel can correlate to brains function in the human body meaning the manager of the perishing body.
Or the manager of the resources available.
Or the manager of the body.
Sent from my SAMSUNG-SGH-T989 using xda premium
I flashed JB Jedi 2 which came packed with a rom while it works great I wonder what will happen if I want to switch back to a different Rom will it be compatible with the kernel it installed?
All roms install their own default kernel each time you flash them.
They are usually chosen by the rom's Dev for good reasons (usually stability) .
It's up to you if you then choose to replace the included kernel with one of your own choosing.
At that point you should think twice about posting glitches you encounter on the ROM developer's forum because you have now changed a fundamental component of his work which is not of his choosing. It would be kind of rude to clutter his thread with problems that may be caused by the replacement kernel.
Feel free to push the envelope, just make a backup first then post problems to the kernel's thread.
Ohh ok I really didnt know that as some roms I have downloaded are 90mb some are like 330mb does that mean they are all compressed in different ways?
davcohen said:
Ohh ok I really didnt know that as some roms I have downloaded are 90mb some are like 330mb does that mean they are all compressed in different ways?
Click to expand...
Click to collapse
No. Some ROMSs gave more data or bloat. Slim ROMs, are well, slim. Leaks, like, Jedi jelly, tend to be pretty big, due to all the bloat they have.
LoopDoGG79 said:
No. Some ROMSs gave more data or bloat. Slim ROMs, are well, slim. Leaks, like, Jedi jelly, tend to be pretty big, due to all the bloat they have.
Click to expand...
Click to collapse
Bloat = the stuff, APKs in this case, someone decided are not necessary.
Hi!
I have great respect for the people that give us our great ROMs, and i KNOW that that is hard - but my question is: why exactly is it that hard?
This is just a question out of curiosity, because I would really like to understand the unerlying problems that cause all the other issues.
I was under the impression that the Android stack runs on top of the Linux kernel.
Usually, the Linux kernel is the Hardware Abstraction Layer, and apps and ROM, in theory, should be kind of hardware agnostic?
e.g. the Bluetooth Issue on our Captivate Glides: I would guess that Android communicates, through some API, with the kernel's BT stack/driver. There must be some (open or closed source) driver available (worst case: some .so module ripped out of an official ROM, maybe?). So why does the headset profile not work? Did the APIs change? Are custom ROMs forced to use another version of the driver?
It also happens to this 50$ chinese tablet i have here: some ROM screw up the touchscreen, some break audio, and so forth. Why can't there be some way of installing a generic ROM, and then side-loading the OEM's drivers?
Thank you again to all ROM developers! This is NO WAY a complaint. Just pure curiosity!
I may be out of my league when trying to describe this, but the processor in our phones is somewhat different to the processor in the bulk of other phones. This is where majority of the issues came from in porting ICS to the glide before ATT released it. Even after the first official ICS update, the modders here were the ones who fixed the keyboard lights... I changed up to JB because the GPS wasn't locking quick enough and PACROM had all the quick toggles and the speed/gps lock I needed.
Sure the kernel is the underlying part that pulls it all together, even still there is all the drivers that need to work with it. If there isn't a bluetooth/wifi/HW Video driver for the version of the kernel, then it gets really tricky and now its coding for a piece of software to speak with the hardware ..... We have things that partially work, but not fully ...as with everything computers, in theory things that "should" work, don't always... I'm an IT tech.. I run into weird **** all the time that "should" work ... takes time, but with persistence and the right skillset, majority of the time a resolution can always be found.
Hello guys, it is possible to run Atmosphère on a NVidia Shield ? The hardware (most of it) is the same, so, how difcult can be, to make a "nintendo switch" from a Nvidia Shield TV ?
The X1 in the Switch is locked to a specific clock, which likely creates issues right off the bat.
From my understanding, it is possible. However, it's highly unlikely you'll ever see more than an experimental test, which wouldn't be published.
You would have to have the source code of the Switch OS. And since that is 100% not happening, emulation would be the next step, but emulation requires substantially more power than running the OS natively.
So, no, this will likely never exist.
It's far more likely, and realistic, that you'll see a Switch running Android TV.
[Also, this should have been posted in Q&A]
smam1338 said:
The X1 in the Switch is locked to a specific clock, which likely creates issues right off the bat.
From my understanding, it is possible. However, it's highly unlikely you'll ever see more than an experimental test, which wouldn't be published.
You would have to have the source code of the Switch OS. And since that is 100% not happening, emulation would be the next step, but emulation requires substantially more power than running the OS natively.
So, no, this will likely never exist.
It's far more likely, and realistic, that you'll see a Switch running Android TV.
[Also, this should have been posted in Q&A]
Click to expand...
Click to collapse
There is this, though, if someone has the gusto: https://github.com/reswitched/switch-oss
Switch on shield, damn that would be heavenly