Related
I wanted to make this post to address two points that I'm sure stir in the hearts of many Vogue owners beyond my own:
Android 2.0, and a flashable ROM.
To begin, I'd like to say that the ability to run Android on our Vogues in the first place is an incredible achievement, thanks to (your) hard work. I know that I speak for the entire community when I say Thank You for making this possible.
This points I'd like to make are:
Windows Mobile 6.5, while an improvement, still leaves myself (and I'm sure others) desiring more. Simply look at the Android interest already generated here, and it's sure to increase with the availability of 2.0--Android is a very slick, capable OS.
Windows Mobile does not include a 3D driver for the integrated ATi Imageon video accelerator--my understanding is that Android does have such support, which is a welcome upgrade in addition to the vast improvement over Windows Mobile that Android is.
The current solution to running Android, booting it from an SD card, feels temporary. I vastly prefer replacing the Windows Mobile ROM with a solid build of Android. This seems like a much more permanent solution, and is the step I'm looking for before making a full transition to Android from Windows Mobile.
I realize that not everyone may agree with me, and that's alright. I wanted to make this thread not only to start conversation, but also to get the thoughts of those developers who could make these dreams a reality.
So the questions become:
Is a fully-functional Android 2.0 build a reality in time? What sort of undertaking might this require? Could this transition be fast, given the progress made already with 1.5/1.6?
Who is in favor of a flashable ROM? Against? Reasons for either? Is a flashable ROM a realistic dream?
Lastly, there are a lot of builds/blends of Android available right now on the vogue-android project. I think this is great, but in the interest of providing a solitary, highest-functionality build of Android for the Vogue, it seems to make sense to try and bring developers together under a single umbrella to get one build completely set up. Would it be a good idea to start an "Android 2.0" project dedicated to moving in this direction?
Again, thanks for everyone's hard work. I look forward to hearing opinions and thoughts, especially as to how far Android on the Vogue may one day go.
This has been discussed at length here:
http://forum.xda-developers.com/showthread.php?t=573397&highlight=bounty
and no the transition to 2.0 will not be quick, for one the aosp isn't even out yet, when it is out, the ril/audio libs/gps libs/bluetooth libs will all have to be rewritten.
I know that a flashable ROM was discussed, but as that thread was left to die, I wanted to start something users can follow up on in looking for a flashable ROM.
What will it take to develop a flashable ROM? Is it something that additional developers are needed for? Is there any way we can help?
mssmison, thanks for clarifying on 2.0. While we might have a start with Android 1.6, re-writing to work with 2.0 could be a big task.
What's still necessary to get a fully-functional, flashable Android ROM? Fix GPS and Bluetooth, and develop a way to flash it and make it native to our devices?
The flashable rom is not dead, and in fact i EXPECT that everyone who put up the bounty will pay out when it comes out.
Well that's fantastic news--thanks for confirming, mssmison.
The next question is, what's left to be finished for a flashable version?
Part of the confusion (my own, at least) is that certain builds have some functionality (GPS), others do not.
I know many are working on Android, in different ports (1.5, 1.6, 2.0, etc.), and I'd really like to see unified work/support to get all features and functionality in a single, flashable build.
I think this is the way to get Vogue users to migrate to Android.
Would there be interest in creating a unified effort to produce a single, completely-functional and flashable build?
I wish I knew more about this. I'm an beginning developer, but I don't hold a candle to the knowledge some of you have in regards to helping the Android movement.
Yes in the near future you will see android running natively replacing windows mobile. Most likely supporting 1.5 and 1.6 with 2.0 when ever google drops the source. I can say that the initial work has been done. I hope everyone makes good on their bounty pledges. The dev that is doing this deserves it.
I will try to put up some money for that too. Anything to make my Vogue run better than it does on Windows Mobile.
BoboBrazil said:
I will try to put up some money for that too. Anything to make my Vogue run better than it does on Windows Mobile.
Click to expand...
Click to collapse
Offer up a donation in the thread: http://forum.xda-developers.com/showthread.php?t=573397
The very not dead thread, in which this discussion should be taking place, and already has some of the answers for the questions asked
Does anyone know where to get the latest rom from the original KIN run? The one that still includes the option for exchange email accounts?
I've tried google, and usually my googlefu is strong but it seems not with this. the latest build seems to be v1 build 2814.0
Also, from what I can see it would work, I'd just have to turn off the cloud stuff using the hidden menu afterwords... or am I wrong?
Thanks
This is actually one of the main problems. If we could get our hands on an actual rom from one of the KINs we would be in pretty good shape, and would be more likely to make progress.
Have you found any rom for a kin? If you have please let us know.
No, although I was only looking for an older rom build.
I'm probably going to call Verizon to try and get them (badger them) to give me an older ROM, since the phones are basically worthless to me without the Exchange email client... Unfortunately, when I looked up the Kin specs, all the sites I checked listed that feature.
Right now I'm hoping that I can either get an older rom on the phone (somehow) or that the newly announced HP Veer comes out on Verizon (also unlikely, since its Tech specs page only lists gsm and not cdma, etc).
I'll see what I can do about getting a ROM first though.
Well, I tried Verizon, and then Sharp.
After the hours on the phone, it appears that:
a.) Verizon could give me an older ROM, if I could somehow get ahold of the right person... since they reason they gave me for not doing it is "As the original equipment manufacturer, Sharp wouldn't let us do that."
b.) Sharp immediately says they have nothing to do with the phone after making it, and only Verizon can help me out.
So with that being a dead end, I can only see 2 options:
1.) Get the info from nvidia that lets us create roms for their tegra stuff (kin one is tegra as well, I believe) and then dump the current rom using their tools and modify it. I don't really think this will be possible, since I'm not an OEM, but I find it more likely than #2.
2.) Get ROM builds and tools from Microsoft. Given how... microsoft... Microsoft is, I really doubt this will be possible.
So, next week I will try #1 (calling them, if possible), followed by #2... but it really looks like its up to the people here to figure out how to dump the phone's current ROM. Given that it has a usb port (and people have gotten some access to the system), I believe its possible one way or another.
Seeing that our current attempts to do something good with the phone had no success yet, i must ask.
Are any news on this topic? I guess we can even just take the "tools" part or drivers, we can skip the rom things .
Maybe Conflipper can help us? It appears he was in the news digging through the original Kin, finding a possible foundation for an instant messenger.
www(dot)phonearena(dot)com/news/Instant-messaging-client-coming-to-the-Microsoft-KIN-handsets_id11919
(sorry add periods between - can't post outside links yet)
Maybe he knows something that might kick start the hacking process?
*** I'm not a regular - I'm sorry I missed Conflipper's retirement ... ***
johnkussack said:
Are any news on this topic? I guess we can even just take the "tools" part or drivers, we can skip the rom things .
Click to expand...
Click to collapse
Sorry, been busy and only news I have on this front is depressing, so I didn't get around to updating quickly.
Can't get anything out of anyone, basically. nvidia wasn't helpful, microsoft wasn't helpful, verizon wasn't helpful, sharp wasn't helpful.
With Verizon, Microsoft, Sharp, it was more like a giant circle... each company would tell me that they couldn't help me, but the next company could, etc.
Calling nvidia just told me to fill out the developer application, but that didn't go anywhere.
It makes me sad because these phones would be awesome if we could actually customize and update them... although I guess there will eventually be replacements running android or something.
HP Veer (webOs) is nice, but it looks like it will be an ATT device, so...
Hi folks,
i have an idea. i am so much fond of windows mobile 6.5.3 and i really like it. i think it's one of the best os for tablets, especially at 7 inches. now you can google for the mangrove 7 to get the idea. unfortunally, the mangrove 7 has never been in production. so i thought of creating my own: i have found a device with almost the same specifications as the hd2. so it must be possible to port that image onto the device. the device is called: huawei ideos s7 slim.
my question: is it possible to run windows mobile on this device by porting the hd2 rom on it? heres why i think:
the both have:
qualcomm 8250 1ghz
adreno 200
and everything else like gps thats involved with the qualcomm chip.
does anyone have an idea how i get the windows mobile on to this specific tablet?
many thanks!
Jakob Sebens
sure its not impissible. but i diubt it will happen. there is hardly any community supportfor that device. alot of work will be required.
hi, thanks for your reply,
why is alot of working needs to be done?
i thougth it was only a matter of flashing the hd2 rom on the device since they have almost identical specs. or must there be done something to make the device accessible for flashing alternative roms?
best regards and thanks for answering!
jakobsebens said:
hi, thanks for your reply,
why is alot of working needs to be done?
i thougth it was only a matter of flashing the hd2 rom on the device since they have almost identical specs. or must there be done something to make the device accessible for flashing alternative roms?
best regards and thanks for answering!
Click to expand...
Click to collapse
Sure. but you need to understand slot...
1) you need a tool to crack the bootloader.
2) you need to write XIP scripts, files etc. you need to build a kitchen.
3) BASICALLY slot of work will be needed! I say it is not impossible but 99% unlikely to happen.
4) Community support! you need at least 15 devs on this project...
Think about the TG01 .. same specs isnt enough! my TG01has virtually the same specs as the HD2 but it still cant get a decent Android Port/ROM dump from HD2. Same snapdragon CPU/GPU, screen, OS, etc.
same specs does not mean same hardware.
if you learned a bit of digital electronics, surely you know about hardware addresses, etc. in our case, device X for hardware A maybe located at address 0x1234 but the same device on hardware B could be located at 0x1000. these addresses are generally hardcoded in ROMs. it's a lot of work to identify those differences & make the necessary modifications.
(a device can be many things - buttons, screen, touch sensor, speaker, mic, communication ports, etc...)
very much thanks for theses replies, consider this thread closed then. i will buy an htc athena then. thanks all for your help.
Admin: you can close this thread.
Hopefully once this hits, it'll be enough to get our CM9/10 roms working a little better. At least, assuming Motorola does indeed cancel our ICS update.
http://www.phoronix.com/scan.php?page=news_item&px=MTE5MTc
I really hope this gives devs everything they need to make a fully operational rom! They've done amazing without the proper tools, imagine if they had them.
Hi everyone,
I wanted to pose this concept to you all to see what you think. Let's say, hypothetically, ASUS was considering having ZenUI, or at least parts of ZenUI open to developers and enthusiasts to tinker around. Can you please answer the following questions - serious replies please!
1) Would that be important to you?
2) What would you do with the code?
3) Would you guys view ASUS differently if we did this? (More negatively, the same, more positively)?
4) Would you recommend ASUS ZenFones to others based on this?
1) yes, very, as practice shows crowd development is much better in finding bugs, fixing them and adding features.
2) nothing, as I am not a coder, but I know many here would love to have it to add features, fix it, make it more suitable for them.
3) already view Asus as a good company, buy my stands would improve definitely.
4) kind of. I am in the boat where I got CN version, not knowing that I would get it, and what would that mean. (EBay seller is to blame here), but seeing that for ng open would give me hope that one day I would be able to unlock all bands needed for US operations. Meaning seeing Asus open their code for ZenUI would give me hope that other parts would become avail later.
even if im not a developer..i can sincerely answer some of the questions from the bottom of my hearts (as an end-user & power user)
1) definitely yes!
2) cant say much as im not a developer, but without the code/sources, things would never be stable and bugs will remain on certain custom roms/kernel, but one thing i can say for sure, the code will help developers to improve asus (software), since there's nothing much can be done on hardware side, so basically what im waiting for is OPTIMIZATION in terms of software and BETTER BATTERY LIFE. ( I know its rude to compare it with other companies, but such as Note 5, 3000mah battery can squeeze 7++ hours of SOT, but with its not impossible with zenfone 2 either!)
3) Yes, this will definitely boost ASUS performances! Just imagine, high end flagship devices that are half the price of other expensive flagships, who would not buy it? and even more, open-sourced? BOOM, ASUS is a winner.
4) Definitely yes, but if my friends were born rich, i would tell him to buy expensive device, but with closed-sources OS, and if he does not mind it. But if he need to choose the affordable one and profitable one, then ASUS is the answer!
Finally, win-win situation for both parties!
1. Yes, absolutely. Both on point of principle (openness is a positive thing), and from a practical standpoint (it would hopefully lead to improvements in the custom AOSP based ROMS and enable some ASUS firmware based ROMS too.
2. Not a dev, so nothing.
3. As I said, I appreciate openness as a positive thing. I would hold ASUS in high regard for such a policy, as it would show a real commitment to maximising device utility and user enjoyment. And it would be really cool.
4. Yeah, it would probably lead me to recommend Zenfones to more people. I am already an advocate of the merits of my device and gladly speak positively of it, but this would just add one more big plus point to shout about. Think it would generate quite a buzz amongst the tech community too.
1. Yes. My 2011 phone's life was extended until just a week ago thanks to the LegacyXperia project, which wouldn't have been possible otherwise.
2. Look at it a little. Maybe suggest improvements through a PR or some such if applicable, although that's fairly unlikely.
3. More positively, of course.
4. I already would, but more so, yes.
1) Yes.
2) I personally won't. But I'm sure some devs such as CM will use it, and I'm already on CM with my Zenfone 2. And I do miss some feature of Stock ROM. So hopefully CM devs can merge some of ZENUI into their ROM, and I would use it.
3) More Positively
4) I already recommend ASUS ZenFones to others, but sometimes it's hard to convince others. If source is opened, I can definitely use that as a reason for ZenFones.
1) yes, and the most important part is hardware sources or maybe support AOSP just like Sony
2) for now nothing but later im planning to learn some coding
3) I already love Asus
4) I already recommend Asus devices to many friends
Sent from my ZF²
ASUS_Khang said:
Hi everyone,
I wanted to pose this concept to you all to see what you think. Let's say, hypothetically, ASUS was considering having ZenUI, or at least parts of ZenUI open to developers and enthusiasts to tinker around. Can you please answer the following questions - serious replies please!
1) Would that be important to you?
2) What would you do with the code?
3) Would you guys view ASUS differently if we did this? (More negatively, the same, more positively)?
4) Would you recommend ASUS ZenFones to others based on this?
Click to expand...
Click to collapse
Just one question could Asus upload the kernel source code to github in the correct way kernel.org do I.e no symlinked folders outside of the main kernel source and keep it upto date day by day to have a complete git history this would help the kernel devs track and fix bugs quicker if all changes are committed as soon as changes are made.
Sent from my ASUS_Z00AD using Tapatalk
eoghan2t7 said:
Just one question could Asus upload the kernel source code to github in the correct way kernel.org do I.e no symlinked folders outside of the main kernel source and keep it upto date day by day to have a complete git history this would help the kernel devs track and fix bugs quicker if all changes are committed as soon as changes are made.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I will definitely pass this along to the Phone team up at HQ. Thanks for the feedback!
1.Yea it would be awesome
2. İ cant so no
3. Much more positively
4 yes i already did
ASUS_Z00AD cihazımdan Tapatalk kullanılarak gönderildi
1)Yes
2)Try to inspect why it require so many permissions
3)More positively
4)Yes
This would be more great for the developers
this will helps developers to optimized zen ui more
ASUS_Khang said:
Hi everyone,
I wanted to pose this concept to you all to see what you think. Let's say, hypothetically, ASUS was considering having ZenUI, or at least parts of ZenUI open to developers and enthusiasts to tinker around. Can you please answer the following questions - serious replies please!
1) Would that be important to you?
2) What would you do with the code?
3) Would you guys view ASUS differently if we did this? (More negatively, the same, more positively)?
4) Would you recommend ASUS ZenFones to others based on this?
Click to expand...
Click to collapse
1) Quite
2) For starters would try to make the options in the drop-down menu and lock screen more customisable. If the ZenUI package includes Camera app I would look into that as well, for I am confident the camera can be improved.
3) I see no negative effects for the customers or developers in such decision, only positive.
4) Certainly
1) Yes, I think to pass on CyanogenMod because of it
2) fit my needs, share what I do, inspire me to better integrate applications (already open source) that I created ZenUI
3) absolutely, I have always made the pub for hardware Asus but this would be the icing on the cake
4) definitely yes yes yes
1) Would that be important to you?
As a developer? no. as im no dev, but as a user knowing what the community can do with stuff, then the answer is yes.
2) What would you do with the code?
Me, nothing. but devs could do some neat things im sure.
3) Would you guys view ASUS differently if we did this? (More negatively, the same, more positively)?
I already view asus positively, i use many asus products that include 2 monitors, a gpu, a laptop, and phone and each item i love
4) Would you recommend ASUS ZenFones to others based on this?
already have talked my best friend into getting one, and have tried talking my grandfather and mother into getting the zenfone max even though they wont support 4g in the usa(there on the fence)
Edit: just noticed someone randomly bumped this thread that was dead sorry :\
ASUS_Khang said:
Hi everyone,
I wanted to pose this concept to you all to see what you think. Let's say, hypothetically, ASUS was considering having ZenUI, or at least parts of ZenUI open to developers and enthusiasts to tinker around. Can you please answer the following questions - serious replies please!
1) Would that be important to you?
2) What would you do with the code?
3) Would you guys view ASUS differently if we did this? (More negatively, the same, more positively)?
4) Would you recommend ASUS ZenFones to others based on this?
Click to expand...
Click to collapse
1) Totally, I have many ideas for launchers.
2) Try to optimize it as much as possible.
3) More positively.
4) Yes, but I'm already recommending it.
1. Heck yassss!!!!! You are in the right place!
2. I'm not a developer, but I've been known to mess around. Seeing a thread like this after buying my first Asus phone after previously owning Samsung devices gives me a damn good reason to stick with Asus.
3. Absolutely! Being inclusive to this community shows a deeper appreciation for your customers than what many people are used to experiencing. It's nice to know that your thoughts and opinions matter and can have a positive influence on future products. My Asus experience is already quite positive. Now, you're earning my respect. Keep it up, Asus!
4. Most definitely! You guys keep searching for Incredible. When I find people looking for the same, they'll be sure to hear about my experience so far.
I didn't know zenphone used a custom proprietary Android when I bought my phone and am very pissed off that I can't build the OS my self and install it on my phone
VeryAngryBird said:
I didn't know zenphone used a custom proprietary Android when I bought my phone and am very pissed off that I can't build the OS my self and install it on my phone
Click to expand...
Click to collapse
...every maker uses a custom "skin" over android. nothing is stopping you from building the rom from there source. but the zenui isnt open source. same with samsungs touchwiz and htc's sense