{
"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"
}
Enable 64bit mode for the N910C (Exynos)
Hello, I just packed our Logo up there, since the entire effort is initiated by us (SimplTeam), but we're not the only ones working on this. :angel:
This thread was created out of a thread in the General section (here) and is intended as a development thread.
Please only post if you are a developer and/or want to help out with bringing this project ahead. Please post basic questions about 64bit or similar things in the linked thread in the General subforum, so we can keep a clean discussion going.
At the present time only @Pafcholini and me work on this, we'd be happy for any help and delighted if you'd join us
The idea
Usually the Exynos 5433 runs in 32bit mode, but the sourcecode comes with an /arm64 folder inside /arch, which contains a defconfig file for a 64bit build.
Because that would be too easy, that config file has interesting settings, but isn't a standalone defconfig. Too bad..
But it did contain some evidence for being what we thought it might be:
Code:
CONFIG_EXPERIMENTAL=y
CONFIG_ARM64=y
CONFIG_64BIT=y
Note the Experimental part. Merging it with the normal 5433 910C defconfig didn't yield any promising results either, so we instead moved to the Galaxy S6, which has a 64bit 7420 Exy chip aboard and looked into its sourcecode.. Bingo!
With the S6's defconfig we managed to eradicate some of the more severe compilation errors, but obviously we can't just take the config from a different phone and compile a build for a Note with it.
Also the S6 Readme file directed us to a 64bit toolchain (https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8/) with which we managed to get the comp starting. And yes - This time it started compiling by using the /arm64 folder instead the usual ones
The problem(s)
Just had to make this reference.. Sorry. Apparently some of the drivers aren't compatible with 64bit, and we faced problems with the DMAG and GPIO. Both problems have been patched by using the S6 sourcecode as technical reference.
It also seems that the 7420 is in parts running the same hardware as the 5433, the DMAG for example is a PL330 and the same in both chips. That makes patching up problems easier.
Despite our solving attempts since a few days, only about 20% of the compilation is working as of now. Any input and idea on how to get the job done would be hugely appreciated.
The sourcecode is synced with Github, so you can download it, attempt a compilation and fix up stuff if you want. Pull Requests are always welcome. Or just join us alltogether
The x64 repo is here: https://gitlab.com/mythos234/SimplKernel-x64-N910C
If you should need the S6 files for patches or reference, here is my still clean repo with the G920F build: https://gitlab.com/mythos234/SimplKernel-LL-G920F
Lets show Sammy that we can do this
Currently contributing: @Pafcholini
Me
mythos234 said:
Enable 64bit mode for the N910C (Exynos)
Hello, I just packed our Logo up there, since the entire effort is initiated by us (SimplTeam), but we're not the only ones working on this. :angel:
This thread was created out of a thread in the General section (here) and is intended as a development thread.
Please only post if you are a developer and/or want to help out with bringing this project ahead. Please post basic questions about 64bit or similar things in the linked thread in the General subforum, so we can keep a clean discussion going.
At the present time only @Pafcholini and me work on this, we'd be happy for any help and delighted if you'd join us
The idea
Usually the Exynos 5433 runs in 32bit mode, but the sourcecode comes with an /arm64 folder inside /arch, which contains a defconfig file for a 64bit build.
Because that would be too easy, that config file has interesting settings, but isn't a standalone defconfig. Too bad..
But it did contain some evidence for being what we thought it might be:
Code:
CONFIG_EXPERIMENTAL=y
CONFIG_ARM64=y
CONFIG_64BIT=y
Note the Experimental part. Merging it with the normal 5433 910C defconfig didn't yield any promising results either, so we instead moved to the Galaxy S6, which has a 64bit 7420 Exy chip aboard and looked into its sourcecode.. Bingo!
With the S6's defconfig we managed to eradicate some of the more severe compilation errors, but obviously we can't just take the config from a different phone and compile a build for a Note with it.
Also the S6 Readme file directed us to a 64bit toolchain (https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8/) with which we managed to get the comp starting. And yes - This time it started compiling by using the /arm64 folder instead the usual ones
The problem(s)
Just had to make this reference.. Sorry. Apparently some of the drivers aren't compatible with 64bit, and we faced problems with the DMAG and GPIO. Both problems have been patched by using the S6 sourcecode as technical reference.
It also seems that the 7420 is in parts running the same hardware as the 5433, the DMAG for example is a PL330 and the same in both chips. That makes patching up problems easier.
Despite our solving attempts since a few days, only about 20% of the compilation is working as of now. Any input and idea on how to get the job done would be hugely appreciated.
The sourcecode is synced with Github, so you can download it, attempt a compilation and fix up stuff if you want. Pull Requests are always welcome. Or just join us alltogether
The x64 repo is here: https://github.com/stefant234/SimplKernel-x64-N910C
If you should need the S6 files for patches or reference, here is my still clean repo with the G920F build: https://github.com/stefant234/SimplKernel-LL-G920F
Lets show Sammy that we can do this
Currently contributing: @Pafcholini
Me
Click to expand...
Click to collapse
+100000000:fingers-crossed::highfive:
Don't give up!
Sent from my Note 4
midopicanto said:
Don't give up!
Sent from my Note 4
Click to expand...
Click to collapse
We won't But during the next week I'll probably don't really have time to work on this. Got 2 final exams and a lot of learning to do, so I only have time to do some maintenance of public kernel builds for now.. Just wanted to say that before everyone starts wondering if I'm dead
Status Update
Good evening,
I don't really have more time at the moment, but still wanted to try something new..
After I somehow managed to lose my own sources, I had to pull the from github again, only to notice that they lacked a little detail.. The arm64 folder with the config file I need
So I opted for a new approach: Compare the S6 config with the one from the Note4 and overhaul the Note4's config instead going the other way around.
It seems to have worked a little better, it's now compiling a little bit more and past a previous error - I believe - but the joy was too early, since this time the sound drivers said bye-bye :crying:
The reason for it seems pretty clear from the compiler error output, as far as my first quick glance has revealed, some of those drivers just don't want to work with 64bit.. Since I'm flirting with the GS6 Edge anyways at the moment, I'm going to compare them and try to patch the Note4 with stuff I learn from the S6. Both SoC software is pretty similar in many places, which raises the chances of success considerably
mythos234 said:
Good evening,
I don't really have more time at the moment, but still wanted to try something new..
After I somehow managed to lose my own sources, I had to pull the from github again, only to notice that they lacked a little detail.. The arm64 folder with the config file I need
So I opted for a new approach: Compare the S6 config with the one from the Note4 and overhaul the Note4's config instead going the other way around.
It seems to have worked a little better, it's now compiling a little bit more and past a previous error - I believe - but the joy was too early, since this time the sound drivers said bye-bye :crying:
The reason for it seems pretty clear from the compiler error output, as far as my first quick glance has revealed, some of those drivers just don't want to work with 64bit.. Since I'm flirting with the GS6 Edge anyways at the moment, I'm going to compare them and try to patch the Note4 with stuff I learn from the S6. Both SoC software is pretty similar in many places, which raises the chances of success considerably
Click to expand...
Click to collapse
sir, thank you so much for this update, i hope others developers could help you with this, ive seen alot of people talking about this thread already, alot of people are happy and thankful for your hard work, also maybe this work could be done after Note 5 released in a couple of months as is gonna be easier, those are my thoughts, well i hope everything is fine with yourself family or school, god bless you, and thank you again, cheers:fingers-crossed::highfive:
I remember back then when the nexus 4 didnt have LTE capability but tge modem was capable and a great dev did unlock the LTE on it. Belive me man if you get this 64 bit runnin you will make us happy and you will be remembered forever
Sent from my SM-N910H using XDA Free mobile app
sirwanesmail said:
I remember back then when the nexus 4 didnt have LTE capability but tge modem was capable and a great dev did unlock the LTE on it. Belive me man if you get this 64 bit runnin you will make us happy and you will be remembered forever
Sent from my SM-N910H using XDA Free mobile app
Click to expand...
Click to collapse
That's correct, that's my point of view and I've been saying in other threads, this is Android Open Source, Thanks Linux and GOD lol, this is no iOS, it might be hard, or not easy, but neither impossible, I have my hopes, and im always thinking positive, and like I said before maybe with the upcoming Note 5 things could get easier with porting and developing to the Note 4, and yes, we have alottttt of amazing developers, I just wish some of them can TeamUp with @mythos234 and make this possible, cheers:fingers-crossed::highfive:
sirwanesmail said:
I remember back then when the nexus 4 didnt have LTE capability but tge modem was capable and a great dev did unlock the LTE on it. Belive me man if you get this 64 bit runnin you will make us happy and you will be remembered forever
Sent from my SM-N910H using XDA Free mobile app
Click to expand...
Click to collapse
No pressure, huh?
Doing my best
yoniinfante said:
That's correct, that's my point of view and I've been saying in other threads, this is Android Open Source, Thanks Linux and GOD lol, this is no iOS, it might be hard, or not easy, but neither impossible, I have my hopes, and im always thinking positive, and like I said before maybe with the upcoming Note 5 things could get easier with porting and developing to the Note 4, and yes, we have alottttt of amazing developers, I just wish some of them can TeamUp with @mythos234 and make this possible, cheers:fingers-crossed::highfive:
Click to expand...
Click to collapse
Thanks for the support!
It definately possible, there is no doubt there. But I fear that at some point I might run into compatibility problems which will need a software department to rewrite them and that isn't even too unlikely to happen.
At the moment however, I'm just patching, fixing and enjoying it
mythos234 said:
No pressure, huh?
Doing my best
Thanks for the support!
It definately possible, there is no doubt there. But I fear that at some point I might run into compatibility problems which will need a software department to rewrite them and that isn't even too unlikely to happen.
At the moment however, I'm just patching, fixing and enjoying it
Click to expand...
Click to collapse
No rush sir, you keep doing what you doing, we are all glad to know we have your support here, cheers:fingers-crossed::highfive:
yoniinfante said:
No rush sir, you keep doing what you doing, we are all glad to know we have your support here, cheers:fingers-crossed::highfive:
Click to expand...
Click to collapse
Yes we're really excited for this project! And take your time man!
Sent from my Note 4
Any news? :fingers-crossed:
Azcaron said:
Any news? :fingers-crossed:
Click to expand...
Click to collapse
Just wrote my final final exam (lol) and now have some free time and the head to continue
Probably not tomorrow, I'll need to visit Vodafone for their continued screwups and collect my new S6 Edge
Probably can continue on Thursday!
Just a question: I have an imported N910L model, if you and your team do manage to get 64 bit enabled on the n910c model, would it be possible to enable it for other exynos models too? Many thanks for all the efforts, keep up the fantastic work.
PhatFishNL said:
Just a question: I have an imported N910L model, if you and your team do manage to get 64 bit enabled on the n910c model, would it be possible to enable it for other exynos models too? Many thanks for all the efforts, keep up the fantastic work.
Click to expand...
Click to collapse
I think they will work, only the Exynos 5433 can be "if someday happens" 64 bit enable, rather than the Snapdragon which is full 32 bit, but of course I guess that would be depending on the number of developers working on the N910L variant, remember to take everything with a grain of salt, god bless, cheers:fingers-crossed:
PhatFishNL said:
Just a question: I have an imported N910L model, if you and your team do manage to get 64 bit enabled on the n910c model, would it be possible to enable it for other exynos models too? Many thanks for all the efforts, keep up the fantastic work.
Click to expand...
Click to collapse
If your phone can run a C kernel, then yes it should work. Otherwise I'd need to make the build for the L from scratch. Considering how painful this is with one build, that scenario would be rather unlikely, unless I had an extenesive period of boredom Have to admit that I'm still playing with my S6 Edge at the moment, I need a break. Not forgetting this project by any means though :angel:
We are waiting eagerly bro
Sent from my SM-N910H using XDA Free mobile app
sirwanesmail said:
This is going nowhere
Sent from my SM-N910H using XDA Free mobile app
Click to expand...
Click to collapse
You could help, instead of just complaining. This is a Dev-Thread.. Sorry, but that comment is not helping anyone.
I'm doing this in my free time and have to manage 3 builds of SimplKernel as well. You can complain about my speed if I was employed and paid
You are doing a great job bro keep it up if you need beta testers im one of them
Sent from my SM-N910H using XDA Free mobile app
mythos234 said:
You could help, instead of just complaining. This is a Dev-Thread.. Sorry, but that comment is not helping anyone.
I'm doing this in my free time and have to manage 3 builds of SimplKernel as well. You can complain about my speed if I was employed and paid
Click to expand...
Click to collapse
@mythos234 please ignore stupid and negative comments dont waste your time in them they are just looking for some attencion...keep up what you are doing we appreciate every second of it...god bless brother cheers:fingers-crossed:
Related
This is not my development
Information:
It's half a month since I first post on Neopeek that I managed to boot Android Linux kernel on raph800 from NAND. Although after that I had solved some of the basic and important bugs, I'm now really making progress slow.
Some people have made great suggestion that me making all the source open, and I decide to follow it. So here is it.
Plan to support: raph800,raph100.
Likely to be supported: diam types, other raph types.
Whether a phone type is supported depends on the test mechine used by our project members.That is , if you have a phone other than raph800 or raph100 but joined the develop team, then we are happy to add your device to the support list.
Sorry to say that it's nearly impossible to use git over my Internet connection, so I have to host the project on Google, using a svn repository.
Notice:
I'm not a professional Linux kernel developer and it's my first time to participate in a open source project(not to say that I'm even the creator…Orz), so if I make something wrong or inproperly please do feel free to point that out and I'll correct it.
Please none developers don't bother in this…
Resource and Participating:
Project is hosted here.
You are accepted as a team member only if you can follow the instructions below.
Read about the project status and the TODO list.
Make a positive () patch for the project to prove that you're qualified to develop.
Send your patch to me by mail and if it's accepted, I'll then add your account to the contributor list.
And please anyone who likes the project spread the word about it over the net, thanks!
from http://www.fluyu.com/2011/04/7/Project_Announcement.html
the project on neopeek http://www.neopeek.com/viewtopic.php?f=24&t=6490
Very nice! Will post some feed back about my experience on my Fuze/aka RAPH110 once I am able to. Glad to see the project being shared on XDA!!!
video:
http://v.youku.com/v_show/id_XMjUyMjI0ODg4.html
one more link:
http://www.neopeek.com/viewtopic.php?f=24&t=6490
We should please viruscreazy for patch to Camera/Video. Maybe he can help us?
Glad to hear for that, hope to coming soon. I waiting for this too long
good deal! i'll be watching this closely
Oh man now this looks awesome! if they get it to work, i'm going back to my Fuze!
how long the battery can work?
vincentchan said:
how long the battery can work?
Click to expand...
Click to collapse
Exact same as haret/SD card builds, probably worse. Lots of optimization needs to happen for NAND, on RHOD battery life is way worse presently. Just because it's being flashed onto the phone doesn't mean the work is done...
if anyone is interested i downloaded complate source from google code. You can use it at your own risk. I hope someone will make shortly NBH from this.
http://www.zshare.net/download/89284876bbed3e9a/
This is amazing! I would definitely like to test the build.
mirror:
http://www.megaupload.com/?d=FUU8YI4S
majkeljj said:
mirror:
http://www.megaupload.com/?d=FUU8YI4S
Click to expand...
Click to collapse
Well, I had to backtrace you over to neopeek's forum to understand this post, with absolutely no explanation.
Folks, he downloaded the source from jamesallen426's google code site and put it in a 7z file...
It doesn't appear ready to test dude, I really hope you asked jamesallen426 for permission to do this... I would assume if he was ready to test it, he would announce a release and post it...
Oh com'on, he was just thinking of a good way to rid the world of the d-pad devil device (triple-d)
I honestly didn't think it was exactly ready for "prime time" but I was considering flashing when I had the time...
R^7Z said:
Oh com'on, he was just thinking of a good way to rid the world of the d-pad devil device (triple-d)
I honestly didn't think it was exactly ready for "prime time" but I was considering flashing when I had the time...
Click to expand...
Click to collapse
exactly. as I wrote "i downloaded complete source from google code" I don't write that it is flash ready, and write that maybe someone can make nbh from this source if he have time and required knowledge. If you want to play with this, here now you have source in one file, you don't need to install additional applications to download source from google code. If we want to push this project forward we need original files to play with them, test something and send to jamesallen426 new files.
Helo. Can anyone tell me what device is Raphael 800? Is it regular HTC Touch Pro GSM version or? Will this work on this device? Tnx.
Sent from my Android using XDA App
I believe RAPH800 is GSM (I could be wrong) but the idea is, we need others to test this that have no problem with their device ending up as a paper weight. As mentioned earlier: by trying this, no one is liable for you destroying your device. Just need testers who know what they are doing and are willing to accept this.
R^7Z said:
I believe RAPH800 is GSM (I could be wrong) but the idea is, we need others to test this that have no problem with their device ending up as a paper weight. As mentioned earlier: by trying this, no one is liable for you destroying your device. Just need testers who know what they are doing and are willing to accept this.
Click to expand...
Click to collapse
RAPH800 is CDMA (Sprint and others). The RAPH100 and 110 are GSM.
I have an HTC fuze here I will give to a developer for testing purposes. Contact me, and I will arrange to send it to you. US-based preferred, just for the shipping convenience.
Thanks.
Let me in! let me in!
R^7Z said:
I believe RAPH800 is GSM (I could be wrong) but the idea is, we need others to test this that have no problem with their device ending up as a paper weight. As mentioned earlier: by trying this, no one is liable for you destroying your device. Just need testers who know what they are doing and are willing to accept this.
Click to expand...
Click to collapse
I have a spare AT&T Fuze (Raph110) which except for the Touchscreen, everything else is operational. Which means for me it's already a brick anyway (i have 2 other ones), so I have no problem trying out some flashing
Android 3.2 Honeycomb for the Samsung Galaxy Tab
8/14/11: For the time being, this thread will close. Work continues on this (and many other) projects, but this thread has grown too large for its own good and has ceased to be relevant. I will start a new thread when I release 3.2 HC, until then, I'm doing my part to help keep XDA crap-free.
See you soon.
8/5/11: I've been pretty quiet for the last week or so... I've had a lot on my plate, but a lot of things are beginning to fade into the background and HC is more in focus. So far, we have a working kernel for HC (which was a much bigger undertaking that I had thought it would be,) and an HC system based on 3.2 and GB that boots minimally, but provides proof of concept. Next up is correcting video issues, merging in things from the Xoom, building wifi and 3G and enabling the SDcard. I plan to fix video issues first, if only to provide you with some screenshots.
7/25/11:
Code:
public void studyForFinals()
{
if eatSleepUrinate()
{
study();
}
else
{
studyHarder();
}
}
7/23/11: Made quite a few kernel modifications and achieved an HC boot today. Hammering out GFX issues as the system doesn't fully boot in.
7/20/11: I just finished building the first version of the new HC kernel with the latest CWM and it boots. The source is up on github.
7/20/11: I spent the last couple of days building a new honeycomb kernel based on the recently released gingerbread cdma kernel along with a recovery built from CM7 source. Things are proceeding slowly, but progress is being made. It looks like I'll begin assembling the basic system components tomorrow and start uploading things to github as they change. Drop in and watch the magic happen in slow motion over the next few days if you want.
7/17/11: Didn't get quite as far as boot, but I did layout the SDK and the Xoom dump, made a lot of notes and made a system map. Next step is to identify the changes that provide compatibility to our type of device to make sure I target my coding for that. Also working on a new kernel based on gingerbread. Since I'm starting fresh here, I might as well switch to a GB base. So the next couple of days will be about kernel building and assembling a bare base of 3.2 into which I can pour code from the GB releases. Oh, and by the way, I just wanna say:
{
"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"
}
7/15/11: Getting caught up on things. Looks like dev starts tomorrow on HC. Hoping to at least have boot by tomorrow evening.
7/12/11: It never fails; wait a few minutes and everything changes. 3.2 dropped today for the Xoom. I told ya, as soon as I say anything, it's almost immediately irrelevant. Well, now I'm committed to a couple of things, so I'll have to start development in a few days, but I'll let you know how it's going as I do.
7/12/11: It's been one crazy thing after another... It seems that the universe has conspired to prevent development.
First, I got 3G running on both tabs... but spent days trying to work out a way to connect, (it recognizes the modem, but wont actually latch onto a network.) Then I learned about GB dropping shortly and spent a few days doing research on that in hopes of avoiding a slew of bricks, (only to discover that there is no change to the bootloader so far with CDMA devices... excellent news, but a lot of wasted research.) And then I got tied up with family affairs, work, summer classes etc. etc. etc.
The last straw was when I discovered that 3.2 is going to drop on a new 7 inch tab in a month or two (and will be pushed to the Motorola Xoom in a matter of days according to various accounts on tech blogs.) With that news, I've dropped development altogether.
3.2 is designed to be compatible with 7 inch screens and single-core processors... So continuing this port would be like trying to cram your foot into the wrong size shoe when the right size shoe is sitting just across the room... what's the point?
So when I get my hands on that, we will have an HC that was designed to run on devices like ours (with all of the tasty features available in 3.1 plus whatever new things they do for 3.2.) As the port of 3.01 will like never run with full features for our tab, I think waiting for 3.2 (a short wait) will be the best option as we will have all of the features we should have had in the first place, and then some.
In the meantime, I have been swamped with work of various kids, cheifly the development of a website that will provide a space for new and less experienced developers to hone their skills with the benefit of more experienced developers to directly assist them (along with a web page of their own, a forum with moderator privileges and a mirror for projects.) We've been calling it an "Android development lab" and I have high hopes for it as a place for individuals to develop skills, build software and stage releases fit for XDA and the like. Though XDA fulfills this function in some ways, it is often difficult for the new developer to realize a vision by simply searching forum posts. (We are in no way attempting to draw traffic away from XDA, but rather providing an environment focused on preparing inexperienced individuals to contribute to places like the XDA community.) It's still under construction, but should be ready in a few days.
Also, I've been contributing to various other projects in small ways and have worked in an advisory capacity with several individuals to help them get projects going. I've found that I really enjoy this role, and will continue in it for the time being.
While we are waiting for 3.2, I will be working in partnership with others to bring you MIUI for the tab (already under way), a dual boot option for the galaxy tab and a native linux installation focused on utility and hacking. Look for these projects soon.
For now, I will no longer be updating this thread. My apologies for leaving it hanging here so long, it's just that every day seemed to bring with it an unpredictability that quickly rendered anything I had to say irrelevant.
See you soon.
~Space
7-5-11 #2: fyi:
Code:
21:06:33.622 Debug PhoneApp 6634 Radio technology switched. Now CDMA is active.
7-5-11: I know I'm dragging my ass on this one, but sit tight. Good things are coming.
7-1-11: I meant to update sooner than this, but shortly after I created this thread, I found out that gingerbread would be coming to the Sprint tab in a matter of days... (and perhaps the Verizon tab soon?) This changes things in several ways.
There will be new bootloaders on upgraded Sprint tabs that won't be compatible with my froyo-based HC build (and the Verizon tab as well if GB ever gets released for it--I assume it's to happen in the near future.)
I don't know if these boot-loaders will be locked. I don't know if it will be possible to revert to froyo boot-loaders to run my HC, and I definitely don't want to tell anyone not to upgrade their tab to GB just to run my HC. Preventing you folks from enjoying your device would defeat the entire purpose of what I'm doing here.
Not knowing how things are about to change for us, I took a couple of days to do some research and see what I could find out... And I found that there is no existing information, leaked or otherwise, on what the boot-loader situation will be (but if your google-fu outranks mine, please post your find here.)
So i began to look into moving my work into a GB base. I think that not only will this be possible, but should net similar results as using a froyo base for the same purposes (it might be a touch more difficult as GB is not nearly as clean, organized or stable a system as froyo IMO.)
So, I have a froyo based HC release soon to come after it gets some finishing touches and a few last minute fixes. At the same time, I'm working on getting a GB base assembled and functional so that we can side-step these potential issues. When the new HC is released, some of you will be able to run it, others may not, but please don't hesitate to upgrade to GB if you wish. I'll do my best to get HC working for upgraders as well.
This whole thing has me running a little behind schedule--of course. But stay tuned for more details on the upcoming HC release... I think you'll be pleased.
6-30-11: Here we go again.
Reserved for later
And again, reserved
what are the plans now Space?
looking forward to this
k0sh said:
what are the plans now Space?
Click to expand...
Click to collapse
Now? We go to the moon. We build a biosphere. Then we start manufacturing weapons. When Earth invades, we defend ourselves. When they are at their weakest, we launch a full scale attack the likes of which Earth has never seen. When they are defeated...
On to Mars!
spacemoose1 said:
Now? We go to the moon. We build a biosphere. Then we start manufacturing weapons. When Earth invades, we defend ourselves. When they are at their weakest, we launch a full scale attack the likes of which Earth has never seen. When they are defeated...
On to Mars!
Click to expand...
Click to collapse
I, for one, will be glad to join you on your campaign of world, and martian domination!
Onwards!
PS: I mashed your Thanks button until it chided me
spacemoose1 said:
Now? We go to the moon. We build a biosphere. Then we start manufacturing weapons. When Earth invades, we defend ourselves. When they are at their weakest, we launch a full scale attack the likes of which Earth has never seen. When they are defeated...
On to Mars!
Click to expand...
Click to collapse
LMAO .. this is what i'm looking for .. anyone wanna join ?
k0sh said:
LMAO .. this is what i'm looking for .. anyone wanna join ?
Click to expand...
Click to collapse
Depends on the broadband speed...
Count in me if there are some chicks , otherwise i'll take the next flight.
spacemoose1 said:
Now? We go to the moon. We build a biosphere. Then we start manufacturing weapons. When Earth invades, we defend ourselves. When they are at their weakest, we launch a full scale attack the likes of which Earth has never seen. When they are defeated...
On to Mars!
Click to expand...
Click to collapse
k0sh said:
LMAO .. this is what i'm looking for .. anyone wanna join ?
Click to expand...
Click to collapse
af974 said:
Count in me if there are some chicks , otherwise i'll take the next flight.
Click to expand...
Click to collapse
now this is what really i should call LMAO .and WOW you dude just made my night
I've been checking these forums like 3 times a day for a while. Thanks for increasing those numbers. I'm highly anticipating the next release of Honeycomb!
Cant wait man, reading the first three posts made me think of my car lol.
Suzuki Kizashi
(kizashi translated in japanese: good things are coming)
I don't want to be a debbie downer here... and I'm normally one to just stay quiet on most matters...
However, the last thread got out of hand. Off-Topic shenanigans and a constant repetition of questions made it difficult to navigate for both novice and n00b alike... please keep this thread on topic as much as we can. I'm no one, myself. However, I keep my post count down by looking for answers and searching, and it's easier to search a thread full of topic-related posts as opposed to random, mindless banter.
Thanks and Thank you Space for your continued work ethic!
mr2324jgf said:
I don't want to be a debbie downer here... and I'm normally one to just stay quiet on most matters...
However, the last thread got out of hand. Off-Topic shenanigans and a constant repetition of questions made it difficult to navigate for both novice and n00b alike... please keep this thread on topic as much as we can. I'm no one, myself. However, I keep my post count down by looking for answers and searching, and it's easier to search a thread full of topic-related posts as opposed to random, mindless banter.
Thanks and Thank you Space for your continued work ethic!
Click to expand...
Click to collapse
Here here!
Sent from my GT-P1000 using XDA Premium App
spacemoose1 said:
Now? We go to the moon. We build a biosphere. Then we start manufacturing weapons. When Earth invades, we defend ourselves. When they are at their weakest, we launch a full scale attack the likes of which Earth has never seen. When they are defeated...
On to Mars!
Click to expand...
Click to collapse
I'll bring my father along and together dad and I can engineer and build our war planes. (He tells people how to build jets like the jsf stvl, etc.)
Sent from my GTab running Better Than Life RC1
oldmacnut said:
I'll bring my father along and together dad and I can engineer and build our war planes. (He tells people how to build jets like the jsf stvl, etc.)
Sent from my GTab running Better Than Life RC1
Click to expand...
Click to collapse
i can be the assistant engineer, i can rig anything on to anything.
the honeycomb threads make me not want honeycomb
robkoehler said:
the honeycomb threads make me not want honeycomb
Click to expand...
Click to collapse
Lol
Sent from my VZW G-Tab running Oldmacnut's better than life RC1 ROM.
so any news? this thread has been pretty quiet considering the fact that the 2.5 thread got locked. im hoping to hear some good news today
Looking for a new tablet and I know that for my old one it didn't get a lot of development love because it has an exynos processor in it. Is this still true? I won't be using it's phone capabilities but will get the snapdragon if i have to if it means more flashing fun because i cannot survive on stock.
Exynos always lags because Samsung goes well out of their way to sabotage devs. Knox, horrible bootloaders, drivers, plus a bunch of hardware blunders (wipe emmc bug, HMP booboo) tend to deter devs from supporting Exynos but iirc worst is Samsung doesn't release source code in timely manner.
If you have other options ignore the Exynos. The Tab S has such a nice screen I couldn't resist
CrashTestDroid said:
Exynos always lags because Samsung goes well out of their way to sabotage devs. Knox, horrible bootloaders, drivers, plus a bunch of hardware blunders (wipe emmc bug, HMP booboo) tend to deter devs from supporting Exynos but iirc worst is Samsung doesn't release source code in timely manner.
If you have other options ignore the Exynos. The Tab S has such a nice screen I couldn't resist
Click to expand...
Click to collapse
Whoa. Sounds like this tab have a lot of problems. I think I will hold off and see what the new quarter brings. Z3 tablet maybe a new nexus 10. Thanks for the info. :good:
The new Dell with a Samsung AMOLED screen seems very interesting...
Sent from my GT-N7000 using Tapatalk 2
Airtioteclint said:
Whoa. Sounds like this tab have a lot of problems. I think I will hold off and see what the new quarter brings. Z3 tablet maybe a new nexus 10. Thanks for the info. :good:
Click to expand...
Click to collapse
This tab doesn't have many issues at all. The rant above appears to be a general rant and even included issues that are outdated and nothing to to with this device !
If all you care about is dev support, then suggest a SD powered device, but this device kicks as in so many areas. ; )
Sammy is quite good with OPEN SOURCE requirements, but can be slow occasionally. Some OEM don't adhere to the GPL requirements at all. Try building a lenovo kernel, they won't even supply the defconfig to compile it !
The thing is, .... With development here, instead of whining, many users have got off their lazy ass and contributed themselves :thumbup:
Zamboney said:
The new Dell with a Samsung AMOLED screen seems very interesting...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
i will check it out but I'm not sure how much dev support a product from dell will receive. Not much I'd imagine.
UpInTheAir said:
This tab doesn't have many issues at all. The rant above appears to be a general rant and even included issues that are outdated and nothing to to with this device !
If all you care about is dev support, then suggest a SD powered device, but this device kicks as in so many areas. ; )
Sammy is quite good with OPEN SOURCE requirements, but can be slow occasionally. Some OEM don't adhere to the GPL requirements at all. Try building a lenovo kernel, they won't even supply the defconfig to compile it !
The thing is, .... With development here, instead of whining, many users have got off their lazy ass and contributed themselves :thumbup:
Click to expand...
Click to collapse
I had a bit of time to look through the forum last night and it appears this device isn't getting much support at all in any models. I know it's still new but even the 705 which i have the opportunity to buy and supposed to be dev friendly isn't getting much attention.
I don't think it would be good for the community if I started building as a lot of bricked devices would happen. Lol
the tablet community is too widespread. too many device around and low dev support in most of it.
edan1979 said:
the tablet community is too widespread. too many device around and low dev support in most of it.
Click to expand...
Click to collapse
+1 although in Samsung's defense the touchwiz on the S is their absolutely best so far and really good stock with Nova launcher.
Sent from my GT-N7000 using Tapatalk 2
UpInTheAir said:
This tab doesn't have many issues at all. The rant above appears to be a general rant and even included issues that are outdated and nothing to to with this device !
If all you care about is dev support, then suggest a SD powered device, but this device kicks as in so many areas. ; )
Sammy is quite good with OPEN SOURCE requirements, but can be slow occasionally. Some OEM don't adhere to the GPL requirements at all. Try building a lenovo kernel, they won't even supply the defconfig to compile it !
The thing is, .... With development here, instead of whining, many users have got off their lazy ass and contributed themselves :thumbup:
Click to expand...
Click to collapse
General rant was inspired by owning all Samsung's flagship devices since the original Galaxy S, plus trying to build BeanStalk, LiquidSmooth and Gummy for the T700
Past exynos disappointments include the Tab 7.7 (no firmware support from Samsung a few months in) and international Note with the emmc that self-destructs randomly. Great hardware, lousy firmware/drivers/documentation.
Thanks for your kernel too.
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.
m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse
timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Offer a bounty if you're that impatient.
sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.
bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol
m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.
and its outtt
m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then
Qualcomm WinMobile TRACE 319B v2.0.1000.00000
Xiaomi Mi 5 Diagnostic Drivers
(Diag Drivers)
Introduction
By mistake I set the band_ref to USA and thereby disabled my first sim card slot :crying: . I read up on it and knew that it's fixable with the right drivers, so I spent my Sunday searching for the Qualcomm Diagnostic (& more) drivers. This topic lists em. Usually, these drivers are part of the Mi PC Suite, but that thing doesn' t support Android 6 or the Mi5 right now. So it is useless to us right now!
Tested on: Windows 10 64 Bit (in Test Mode)
Download-Link: http://66.38.130.194/driver/driver_vendor.php?id=887246
Or just get it from here: View attachment Mi5_Qualcomm_Drivers.rar
Screenshot
{
"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"
}
How to enable the Diag mode
Code:
*#*#717717#*#*
Guides that helped me
Link: Qualcomm NVRAM Settings & 2G/3G/4G LTE Band Config
Link: [TUTORIAL] How to unlock more LTE frequency bands on Mi Note Pro
Questions & Answers
Q:Did I try to unlock bands: A:NO, I did not.
Q:Will it be possible to unlock more bands with these drivers? A: Maybe.
Hope these are helpful to you guys.
Hey @TheUltrametricSpace,
thanks for sharing with us. I will need to change the band as well (EUR) and hope everything goes right ...
Will let you know in case I need to debug/diagnose something with these drivers. Thanks again!
Thanks for presenting these important issue.
I do accidentally press usa band from #*#*4636*#*# and cant have signal rite now.. just want trying with this solutions rite know. Is there step by step for mi5? Or its just the same like the other phone?
ekowanz said:
I do accidentally press usa band from #*#*4636*#*# and cant have signal rite now.. just want trying with this solutions rite know. Is there step by step for mi5? Or its just the same like the other phone?
Click to expand...
Click to collapse
I did the same! And that's how I started to look for these drivers.
All you need to do is change the ban_pref* values back to the original, for the Sim-Card you changed it.
Set the following values in your phone, for the Sim-Card you disabled em. (By Clicking band mode USA)
Code:
00441 band_pref 0xFFFF
00946 band_pref_16_31 0xBFFF
02954 band_pref_32_63 131072
Ask if you have questions, it's not too hard if you read the guides, but better save than sorry.
Praying for the day someone will unlock band 20, so I can already order the indian version of the mi5..
TheUltrametricSpace said:
I did the same! And that's how I started to look for these drivers.
All you need to do is change the ban_pref* values back to the original, for the Sim-Card you changed it.
Set the following values in your phone, for the Sim-Card you disabled em. (By Clicking band mode USA)
Code:
00441 band_pref 0xFFFF
00946 band_pref_16_31 0xBFFF
02954 band_pref_32_63 131072
Ask if you have questions, it's not too hard if you read the guides, but better save than sorry.
Click to expand...
Click to collapse
hi.. I can confirm that it fixed my phone. Thx a lot brother....
Hey guys, is this device going to have development in roms? I mean, xiaomi uses to release kernel source for snapdragon devices right? Do you think it will be the same with mi5?
I am thinking about buying mi5 or some nexus....depending on the software I will decide. Dont like miui
Javi22 said:
Hey guys, is this device going to have development in roms? I mean, xiaomi uses to release kernel source for snapdragon devices right? Do you think it will be the same with mi5?
I am thinking about buying mi5 or some nexus....depending on the software I will decide. Dont like miui
Click to expand...
Click to collapse
Why would you buy a phone when you already know that you don't like the OS it runs on? .... So if you don't like MIUI you have to trust in a random person who will spend his free time to develop software for the Xiaomi Mi5. (Or maybe a team, let's say, 5 people).
And now you put those 5 people vs the ~750 Android developers that work for Google.
TheUltrametricSpace said:
Why would you buy a phone when you already know that you don't like the OS it runs on? .... So if you don't like MIUI you have to trust in a random person who will spend his free time to develop software for the Xiaomi Mi5. (Or maybe a team, let's say, 5 people).
And now you put those 5 people vs the ~750 Android developers that work for Google.
Click to expand...
Click to collapse
Because of the price difference....Nexus 6P is awesome but I wont pay too much for an smartphone when I can get another similar for much less money
So the only thing that would make me do the effort is software. Because about hardware...I love mi5 as much as 6P. Even I prefer mi5 because of size
And I can see that past Mi devices have had a big development, with CM official and many roms. If them are good enought, would be an option to consider
Javi22 said:
Because of the price difference....Nexus 6P is awesome but I wont pay too much for an smartphone when I can get another similar for much less money
So the only thing that would make me do the effort is software. Because about hardware...I love mi5 as much as 6P. Even I prefer mi5 because of size
And I can see that past Mi devices have had a big development, with CM official and many roms. If them are good enought, would be an option to consider
Click to expand...
Click to collapse
I can relate to that, but this is the android world we live in, where we get awesome phones but the software is not as good, lack of updates, and sometimes like you said thr software is not how we like it and there is too much bloatware...
Sorry for the offtopic
codeglitch said:
I can relate to that, but this is the android world we live in, where we get awesome phones but the software is not as good, lack of updates, and sometimes like you said thr software is not how we like it and there is too much bloatware...
Sorry for the offtopic
Click to expand...
Click to collapse
Yes it's about picking the compromises you can live with.
Good thing about the Xiaomi top products is that they get updates like Nexus devices do.
The Mi3 and Mi4 get Android 6, the mi3 was released in 2013.
The Mi2 from 2012 got Android 5 and with custom Roms might get 6.
Concerning updates, is the Mi5 future proof, but if you don't like Miui... That doesn't help.
TheUltrametricSpace said:
Yes it's about picking the compromises you can live with.
Good thing about the Xiaomi top products is that they get updates like Nexus devices do.
The Mi3 and Mi4 get Android 6, the mi3 was released in 2013.
The Mi2 from 2012 got Android 5 and with custom Roms might get 6.
Concerning updates, is the Mi5 future proof, but if you don't like Miui... That doesn't help.
Click to expand...
Click to collapse
Yep I know. That´s why knowing if xiaomi is releasing kernel and sources would help...because surely many devs would take it and work on it, cause it´s a popular device. Well, I guess hahaha
Miui is regulary updated but it still having some drawbacks. Some apps/xposed dont work well, it´s many different from aosp
Anyway thanks for your opinion. Would be nice If someone has read something about this or know something else
TheUltrametricSpace said:
Qualcomm WinMobile TRACE 319B v2.0.1000.00000
Xiaomi Mi 5 Diagnostic Drivers
(Diag Drivers)
Introduction
By mistake I set the band_ref to USA and thereby disabled my first sim card slot :crying: . I read up on it and knew that it's fixable with the right drivers, so I spent my Sunday searching for the Qualcomm Diagnostic (& more) drivers. This topic lists em. Usually, these drivers are part of the Mi PC Suite, but that thing doesn' t support Android 6 or the Mi5 right now. So it is useless to us right now!
Tested on: Windows 10 64 Bit (in Test Mode)
Download-Link: http://66.38.130.194/driver/driver_vendor.php?id=887246
Or just get it from here: View attachment 3682462
Screenshot
How to enable the Diag mode
Code:
*#*#717717#*#*
Guides that helped me
Link: Qualcomm NVRAM Settings & 2G/3G/4G LTE Band Config
Link: [TUTORIAL] How to unlock more LTE frequency bands on Mi Note Pro
Questions & Answers
Q:Did I try to unlock bands: A:NO, I did not.
Q:Will it be possible to unlock more bands with these drivers? A: Maybe.
Click to expand...
Click to collapse
You can use Qualcomm's own drivers, dont need any "Mi5" drivers to communicate with your phone, and no its not important which android version you have. Windows 10 might be a problem though. But in case you wanna try every driver, here you are, all Sunday you said ?
https://www.google.com.tr/#q=xiaomi+diag+drivers
http://www.androidbrick.com/download/xiaomi-qpst-diag-driver/
https://www.facebook.com/androidbrick/posts/1830816097146100
os_man said:
You can use Qualcomm's own drivers, dont need any "Mi5" drivers to communicate with your phone, and no its not important which android version you have. Windows 10 might be a problem though. But in case you wanna try every driver, here you are, all Sunday you said ?
https://www.google.com.tr/#q=xiaomi+diag+drivers
http://www.androidbrick.com/download/xiaomi-qpst-diag-driver/
https://www.facebook.com/androidbrick/posts/1830816097146100
Click to expand...
Click to collapse
I found a lot of drivers, before finding these.
Which of your links work for the SD 820 and Windows 10 64Bit?
( you surely tried em all and must know)
I'm asking because I'm not sure if you are stupid and trying to be "smart."
... Or if you found drivers.
But before judging, I'm asking. So please explain yourself.
Update:
The Androidbrick page is from April, I got my phone in March and found the drivers in March. So there is a slight possibility that that guy found the same drivers or well he did copy and paste from here. Now that I did not have the possibility to copy the Xiaomi Qualcomm Drivers from myself, as I did not invent time-travel and solve some paradoxes.... I could not copy and paste from myself and so had to find the drivers online. Keeping in mind that the original download page is offline, I am 100% sure that this Androidbrick guy just took the drivers from this topic!
To be sure you get this: Androidpick writes: "Create Date Nisan 11, 2016" what means, "Create Date April 11, 2016".
So that means, I did what you were supposed to do and can end it with the conclusion that you are an idiot. You don't have to respond do this.
TheUltrametricSpace said:
I found a lot of drivers, before finding these.
Which of your links work for the SD 820 and Windows 10 64Bit?
( you surely tried em all and must know)
I'm asking because I'm not sure if you are stupid and trying to be "smart."
... Or if you found drivers.
But before judging, I'm asking. So please explain yourself.
Update:
The Androidbrick page is from April, I got my phone in March and found the drivers in March. So there is a slight possibility that that guy found the same drivers or well he did copy and paste from here. Now that I did not have the possibility to copy the Xiaomi Qualcomm Drivers from myself, as I did not invent time-travel and solve some paradoxes.... I could not copy and paste from myself and so had to find the drivers online. Keeping in mind that the original download page is offline, I am 100% sure that this Androidbrick guy just took the drivers from this topic!
To be sure you get this: Androidpick writes: "Create Date Nisan 11, 2016" what means, "Create Date April 11, 2016".
So that means, I did what you were supposed to do and can end it with the conclusion that you are an idiot. You don't have to respond do this.
Click to expand...
Click to collapse
You will say idiot to me and i'm not supposed to reply ? How old are you ? Date's ? Who cares about dates and who cares what you think ? Check my facebook link and see that i changed imei's of that famous Mi5 of yours, and how am i supposed to that without knowing diag drivers etc ? Google "qfil" and look for the result, more then 250.000 people have downloaded that program from my server, you think why ? Oh sorry, moron's cant think, they just can copy and paste, worldwide
os_man said:
You will say idiot to me and i'm not supposed to reply ? How old are you ? Date's ? Who cares about dates and who cares what you think ? Check my facebook link and see that i changed imei's of that famous Mi5 of yours, and how am i supposed to that without knowing diag drivers etc ? Google "qfil" and look for the result, more then 250.000 people have downloaded that program from my server, you think why ? Oh sorry, moron's cant think, they just can copy and paste, worldwide
Click to expand...
Click to collapse
I am old enough.
And I did say idiot to you, that's right, plus stated reasons for this.
Further, on my Mi 5 is not famous. I don't care about your Facebook link. (As it is from the 6th of April, and this topic was created on the 14th of March)
One little detail to add is: I was one of the very few people that got a Mi5 from the first flash-sale. (Very few people that live outside of China got their Mi 5 on the 7th of March. )
However. Things are as they are. It's simple. You were too lazy and too stupid to check the dates. And for this, I called you an idiot.
One other explanation for your behaviours is that you are a victim of the dunning-kruger-effect, yet I don't care about that, make a test for it and figure it out alone. I won't help you here.
Uh ... and I hope you are aware that the drivers in this topic are Qualcomm's drivers, those drivers have nothing to do with Xiaomi, it's all about Qualcomm.
Hey guys come on don't fight it is normal in a huge world that two guys reach similar goals in their own way.
You both are pioneers and it would be great if you cooperate instead of fight for who arrived first
oile said:
Hey guys come on don't fight it is normal in a huge world that two guys reach similar goals in their own way.
You both are pioneers and it would be great if you cooperate instead of fight for who arrived first
Click to expand...
Click to collapse
That's very kind of you to step in and end this.
But just to be clear, for me, this is not about "I ARE FIRST". The only reason I shared this is to help others, end of the story for my part.
I just get very pissed when people are too stupid to read dates :crying: