Related
NEWS: AS OF TODAY FEB 26TH WE HAVE A BOOTABLE KERNEL! WE ARE WORKING TO IMPROVE IT'S STABILITY. STILL NO FRAME BUFFER SO WE CAN NOT SEE OUTPUT PAST THE KERNEL BOOT.
*********************************************
NEWS:
Since I don't update this first post very often I thought I'd share some news for those following the project.
We have a git repository now! This will allow the project developers to share code and work together much more efficiently. Anyone interested in joining us send me a PM
The stable branch is the one we will be adding permanent commits to, the experimental branch adds official support for the lg incites registered mach type, meaning the kernel recognizes our device, it will be merged into the stable branch once it is bug free and cleaned up.
Stable Branch(still not booting)
http://gitorious.org/~szeng/linux-on-qualcomm-s-msm/linux-msm-lg-incite
Experimental Branch (still not booting)
http://gitorious.org/~randomblame/linux-on-qualcomm-s-msm/experimental-linux-msm-lg-incite
We also have an IRC channel, you can join us on freenode channel #lg-linux
http://www.lg-incite.com/index.php?topic=3198.0
I attach the haret.exe and the zimage
Someone can throw(shoot) a hand to me helps
i just bump it, i will work for this when i can i guess in weekends , who need GF anyway
odd that looks like something I wrote... very strange.
Android for LG GM750 would be cool!
great.. are you completing the project.. i was failed and tired
I´m hopefully awaiting an working stable port for the gm750,
because its hardware is great for its price, but the system is crap and since we also know that development for winmo 6.x will slowly die within the release of wp7, android would be a great(and only) chance to have an up to date, good system which will also get lots of support in the future.
So, please keep working on it guys!
No news?
woonaval said:
No news?
Click to expand...
Click to collapse
no news???
NO NEWS?
leobillson said:
no news???
Click to expand...
Click to collapse
NO NEWS?
This is my Christmas wish
what about this,
we have fully funtioal processor then what is the problem here??
propsia said:
what about this,
we have fully funtioal processor then what is the problem here??
Click to expand...
Click to collapse
LG Gm750 restarts when booting up the phone and that's it ... I still have a problem .. : '(
fdavs said:
LG Gm750 restarts when booting up the phone and that's it ... I still have a problem .. : '(
Click to expand...
Click to collapse
I think this needs a bump.
Well, it's pretty big bulge ) xD
Dont let this topic die...i have GM750 and i need android on it...ill tried to modify other phone`s default.txt file a lot but no luck...it would be fine to get a working port on this handy.
I do not want to die in this thread because I also really like LG and GM750 is, Windows Mobile just does not like it. I do not understand the Android Linux kernel access this building ... so i can not help this. But I think if the team is dealing with XDANDROID 1 day is running smoothly I think you could do ... Someone please HELP! (sorry I'm not English [translate.google.com] )
still hoping... no new apps for wm6.5 now
I agree
Im from over at the lg-incite.com forum, and I've been following the progress of their Android port for a rather long time. The guy who's been doing most of the programming has other life issues he's dealing with right now. Car wreck, kid on the way, etc, and I can sympathize.
Our biggest roadblock is an lcd driver. Over here in xda, they had the same problem with, i believe, the htc diamond. Their solution was to make their own driver. We don't have that kind of knowledge (that i know of). If someone from XDANDROID could pop on over and give us a hand, whether through making us a driver, or pointing us in the right direction, this project can be resurrected, finished, and ready for the world to see!
i've been trying to help as much as I can, but a college kid that works full time and plays in a band doesn't have much spare time. But I try. I love my Incite and want to see this thing run all the same stuff the modern PDAs run.
LONG LIVE THE INCITE
Hix, adroid is a dream with my GM750
Android / Linux port for PHOTON
Introduction:
HTC Photon looks very similar to HTC Liberty. It's not only external look, as well they are very similar.
My goals was to determine how fast it can be binged up on HTC PHOTON.
Actually they much more changes, that it looks at first view.
PHOTON doesn't have digital compass, while LIBERTY have it.
As well LIBERTY have optical trackball, PHOTON doesn't.
Notes about future development:
All GPIOs looks same in PHOTON & LIBERTY.
Only 192Mb RAM used for now. Additional RAM can be activated.
Battery driver doesn't work, heave difference between PHOTON & LIBERTY.
GSensor doesn't work, looks like it's problem of userspace android library.
Calls are working, data (GPRS) - not. It maybe big problem to implement DATA connection.
WLAN also not working somehow.
Buttons are working, but they need proper align. (buttons are part of touchscreen).
Status:
http://htc-linux.org/wiki/index.php?title=PhotonStatus
"Unknown" means not tested. I had not enough time to test it well.
I didn't test anything really. Only just looks for "yes" / "no", no deep testing because not enough time.
Files to download:
for developers:
KERNEL + HARET sources.
Note this HARET only compatible with HTC PHOTON.
http://cotulla.pp.ru/photon/Cotulla_PHOTON_AD_Devs.rar
for users:
ANDROID which runs from SD card, without removing Windows Mobile.
Copy files to root of SD card and run "HARET_PHOTON7227.exe"
http://cotulla.pp.ru/photon/Cotulla_PHOTON_AD_Users.rar
NOTE about files. I will delete this files tomorrow or after tomorrow.
Please reupload them to different file share hostings. Otherwise it will cause too big traffic to my site. Sorry for that.
Disclaimer:
This product is free to use at your own risk. We take no
responsibility for any conflict, fault, or damage caused by
this unlocking procedure. No warranties, implied or otherwise, are given if you agree to use this product.
No problems were found while testing this product on several different devices, your experience may vary.
This software is free, but not open source.
DISCONTINUED:
I won't continue developing of Android/Linux for PHOTON. Why?
*Main goals of this project are passed. All stuffs was ported in about 5 days.
*I have not much free time to develop android for another device. (I am supporting several devices, they take a lot of time)
*It's rather useless? You can sold PHOTON and buy LIBERTY. With native android inside. With compass inside. With trackball inside. With same size and design like PHOTON.
*And main reason: My father's phone is broken. I will give him PHOTON So I won't have PHOTON device anymore. And can't develop for it.
*I hope you appreciate all this
Anyway goodluck in developing, a lot of work already done (the hardest part however...)
-Cotulla
Awesome job you did there Cotulla. I don't own a Photon myself but have been trying to help the guys in another thread with some hints to try and get HaRET working. It's unfortunate you can't continue development. But with your work maybe some other developers that have the Photon can make it fully functional.
I've mirrored the files here:
http://netripper.com/photon/Cotulla_PHOTON_AD_Devs.rar
http://netripper.com/photon/Cotulla_PHOTON_AD_Users.rar
This is SO NICE!! I hope someone can pick up Android development now and we can get Android on our devices. And what you're saying about HTC Liberty, we can't buy it over here So I had to buy HD Mini
Thank you so much!
PS: I still hope you'll get another Photon in the future
Thank you so much! This a VERY BIG STEP for us!
We will continue with your work
Thank You Very Much Cotulla!!!
Cotulla? ... THANK YOU!
. .
thanks thanks
Thanks a lot cotulla you are such a big help
Thanks so Much!!
Спасибо БОЛЬШОЕ!!
Here are some more links
Cotulla_PHOTON_AD_Devs.rar
w_ww.multiupload.com/5RGRYQYP2M
Cotulla_PHOTON_AD_Users.rar
w_ww.multiupload.com/JQV692NKNG
many many thanks, i hope other Devs pick this.
good luck with other projects
Cotulla you are a genius!
Thanks so much!
Mirror (Direct Download):
http://www.bb-projects.de/Cotulla_PHOTON_AD_Users.rar
http://www.bb-projects.de/Cotulla_PHOTON_AD_Devs.rar
I am very happy. looks great on my HTC HD mini. thanks a million times !
i know its a little bit early but im so exciting because of this! did someone tried and tested it on the mini? maybe upp some screens ?! thanks again cotulla. Hope someone will finished his work
Silver1987 said:
i know its a little bit early but im so exciting because of this! did someone tried and tested it on the mini? maybe upp some screens ?! thanks again cotulla. Hope someone will finished his work
Click to expand...
Click to collapse
Yes. I have tried
I can only tell a compliment to devolopment.
... a very polished look and work a little slower than wm (so far)
for 2 hours of testing a few times I had to put the sim card pin
hm i tested it too and android working ..but i have a few questions...hm could it be that our (or my european device from germany) mini ist not fully working with ARIA rom? maybe we need Gratia rom ? im asking that because ehen i started booting first time i could only chose betwen 3 languages (and german or other European languages are not there). and the second thing is that it didnt find my SD-Card .. and i heard that aria only accept specific SD Cards`? is that right?
or is it possible to replace this aria(liberty) rom to an gratia rom? because we now have working haretfix `? thanks for the attention greetz silver sorry for my english
first off all:
THIS IS NOT A WORKING ANDROID!
please read first post for details.
haret does not give us the possibility to run complete "ROMS". we have to build kernels and android on our own. and as i can see there is no special gratia source on htc developers site, so i think there is no difference in hardware.
great job! thanks so much
ok thanks for the explanation schlund
Hey, I'm a noob, let's get that out of the way first.
Alright, so I'd like to know, why is it so hard to get special ROMs working on certain devices?
For example, I have an Evo 3D (HTC Evo V 4G, whatever), so why is it so hard to get, say, stock ICS running on it?
Inthe end, isn't the hardware all the same, other than say processors and screen size? To get a stock ICS ROM working, couldn't you just pull it off of a similar phone with an S3 processor and a 4.3 inch screen?
Or is it not that simple? Are different codes baked into the hardware that make it impossible to just modify the pixel density, size of the screen and have the ROM work with the processors?
I understand the cameras are different, hence cameras not working on early builds of CM9... but considering many phones run the same processors, couldn't they just all work?
Please explain... thanks, thebeastglasser.
thebeastglasser said:
Hey, I'm a noob, let's get that out of the way first.
Alright, so I'd like to know, why is it so hard to get special ROMs working on certain devices?
For example, I have an Evo 3D (HTC Evo V 4G, whatever), so why is it so hard to get, say, stock ICS running on it?
Inthe end, isn't the hardware all the same, other than say processors and screen size? To get a stock ICS ROM working, couldn't you just pull it off of a similar phone with an S3 processor and a 4.3 inch screen?
Or is it not that simple? Are different codes baked into the hardware that make it impossible to just modify the pixel density, size of the screen and have the ROM work with the processors?
I understand the cameras are different, hence cameras not working on early builds of CM9... but considering many phones run the same processors, couldn't they just all work?
Please explain... thanks, thebeastglasser.
Click to expand...
Click to collapse
Is not that easy! I'm an EVO user/rom porter and I hear this alot where users such as yourself think is an easy process BUT is not. Same processor, same screen size maybe the same BUT at times the kernel is not there. Either the kernel for the device doesn't support ROM A or ROM B and therefore it can't be ported to whatever device or the libs keep it from running half way decent.....i.e WiFi doesn't work, sound is **** up or whatever the case maybe...just not functional to say the least.
Take for example Sense 4.0 on the One V....it was ported to the EVO4g and the ROM barely works! Both the One V and the EVO4g have similar hardware but one runs Sense 4.0 like a dream and the other one struggles with simple things like WiFi and Sound.
Now I'm sure someone else with a bit more knowledge on this can get into the specifics and the why's and what's of WHY this can't happen BUT that's it in a nut shell.....the kernel and 9/10 times libs
See ya around dude!
Hey first off, thanks! Second...
Another question then. If they all have relatively similar hardware, why isn't it that a universal kernel for similar phones can't be created?
Or better explained, what about the phone, makes it so that the kernel doesn't work? Or why couldn't you just take the kernel from device A and shove it on device B?
Sorry if I'm overloading you with questions, but hey I'm curious. Ya know?
EDIT: Or if they're practically both the same phones, why is it that you can't just take the ROM AND the kernel from phone A and put it onto phone B?
thebeastglasser said:
Hey first off, thanks! Second...
Another question then. If they all have relatively similar hardware, why isn't it that a universal kernel for similar phones can't be created?
Or better explained, what about the phone, makes it so that the kernel doesn't work? Or why couldn't you just take the kernel from device A and shove it on device B?
Sorry if I'm overloading you with questions, but hey I'm curious. Ya know?
EDIT: Or if they're practically both the same phones, why is it that you can't just take the ROM AND the kernel from phone A and put it onto phone B?
Click to expand...
Click to collapse
It's the manufacturer of the device who would need to release the kernel sources for the certain firmware version which they won't do continuously. In other words, device A may get ICS, hence the kernel sources may be released, but device B may be stuck with gingerbread and may not have a kernel which supports ICS. Back-porting can be done, but in many cases it is very difficult and in the end there still could be a lot of bugs.
You can't just take a kernel and "shove" it in another device. If you did this, it's quite likely nothing would work. The device would not even boot. Remember, the kernel is the center of android (Linux), so everything needs to be "linked" and correspond with each other exactly for it to work (I'm trying to make it as simple as possible ).
If they are the same devices, that would not be necessary. They would use the same roms/kernels. If they are just very similar (e.g. the a100 and a500) you may have some luck with the roms, but not the kernel. Some a500 roms can be flashed onto an a100 and work flawlessly BUT the device's original kernel must be restored for the device to boot.
Theonew said:
It's the manufacturer of the device who would need to release the kernel sources for the certain firmware version which they won't do continuously. In other words, device A may get ICS, hence the kernel sources may be released, but device B may be stuck with gingerbread and may not have a kernel which supports ICS. Back-porting can be done, but in many cases it is very difficult and in the end there still could be a lot of bugs.
You can't just take a kernel and "shove" it in another device. If you did this, it's quite likely nothing would work. The device would not even boot. Remember, the kernel is the center of android (Linux), so everything needs to be "linked" and correspond with each other exactly for it to work (I'm trying to make it as simple as possible ).
If they are the same devices, that would not be necessary. They would use the same roms/kernels. If they are just very similar (e.g. the a100 and a500) you may have some luck with the roms, but not the kernel. Some a500 roms can be flashed onto an a100 and work flawlessly BUT the device's original kernel must be restored for the device to boot.
Click to expand...
Click to collapse
I have the strangest feeling I just tried to jump into the shallow end of the swimming pool, and yet instead was shot out of a cannon into the middle of the sea without a scuba diver's suit... If only I could understand this more!
thebeastglasser said:
I have the strangest feeling I just tried to jump into the shallow end of the swimming pool, and yet instead was shot out of a cannon into the middle of the sea without a scuba diver's suit... If only I could understand this more!
Click to expand...
Click to collapse
Think about it this way. The Android OS could be run on a number of different devices that run slightly different hardware such as cameras, touchscreens, processors, etc...but the OS has to be able to communicate properly to that hardware using device drivers. Just like Windows from a 30000 foot view. It can run on a Dell or Acer computer, but must have the proper drivers.
If the manufacturer's of those devices do not write ICS drivers or preferably furnish their source code, then it is incredibly difficult if not impossible for someone without the internal company documentation to write such a driver.
mf2112 said:
Think about it this way. The Android OS could be run on a number of different devices that run slightly different hardware such as cameras, touchscreens, processors, etc...but the OS has to be able to communicate properly to that hardware using device drivers. Just like Windows from a 30000 foot view. It can run on a Dell or Acer computer, but must have the proper drivers.
If the manufacturer's of those devices do not write ICS drivers or preferably furnish their source code, then it is incredibly difficult if not impossible for someone without the internal company documentation to write such a driver.
Click to expand...
Click to collapse
Ohhh... so say you decided to put your own little phone together according to your own prerequisites, it'd be simple for you to do something on it, but not so much for someone who only has the hardware to look at... correct?
Another question, why is it so easy to port things onto Nexus Devices? Are they just more compatible with all drivers? As I've heard from one of my friends that he has a fully working Sense 4 ROM on his Nexus S... and yet it's tough to find one for my Evo V.
EDIT: I'm out of "thanks" I'll give you one as soon as I get some more...
thebeastglasser said:
Ohhh... so say you decided to put your own little phone together according to your own prerequisites, it'd be simple for you to do something on it, but not so much for someone who only has the hardware to look at... correct?
Another question, why is it so easy to port things onto Nexus Devices? Are they just more compatible with all drivers? As I've heard from one of my friends that he has a fully working Sense 4 ROM on his Nexus S... and yet it's tough to find one for my Evo V.
EDIT: I'm out of "thanks" I'll give you one as soon as I get some more...
Click to expand...
Click to collapse
Hmmm, I am not as familiar with the Nexus devices, but I suspect that Google has released the hardware spec details and the source code for the drivers for Nexus phones, so the source code can be modified and included for the ports. HTC unfortunately has not been as open with some of their phones.
If you were to put a phone together, you would need to use hardware in it that you had access to the specs and source code for. This is not a great analogy, but I think it will serve. The camera app tells the OS, "take a picture", then the OS tells the driver, "make the camera take a picture", and the camera device driver controls the hardware parts like the shutter, the focus, and zoom to cause the picture to be taken and handed back to the OS to be saved and then the OS notifies the app, "here is your picture, awaiting next command".
If you do not have access to the camera driver source code and camera hardware specs to create a driver, or an actual driver from the camera manufacturer, then you are missing the crucial third part and you cannot make the camera take a picture even if you get an OS loaded and an app installed there.
Check out The Tricorder Project for an excellent example. Create your own Star Trek "tricorder" with various sensors and a touchscreen that runs on Linux for around $200 and some work putting it together.
thebeastglasser said:
Ohhh... so say you decided to put your own little phone together according to your own prerequisites, it'd be simple for you to do something on it, but not so much for someone who only has the hardware to look at... correct?
Another question, why is it so easy to port things onto Nexus Devices? Are they just more compatible with all drivers? As I've heard from one of my friends that he has a fully working Sense 4 ROM on his Nexus S... and yet it's tough to find one for my Evo V.
EDIT: I'm out of "thanks" I'll give you one as soon as I get some more...
Click to expand...
Click to collapse
Its easy to develop for nexus devices since Google always releases their sources and those devices are easily unlockable (the bootloader). This is one reason why they are usually referred to as development/developer devices.
So in other words, the software communicates with the hardware, but without the proper code embedded in the hardware, it's not possible for the software to communicate with it? And without source code given from the developer of the hardware, you're making software that hypothetically should work, but because of the different device hardware it may or may not work...?
And that's also big because some guy on the portal recently found out that all of the eight mega pixel cameras on HTC devices are the same, so it should now be easy to use working cameras on ported and newly created ROMs...
Am I getting anywhere with this?
thebeastglasser said:
So in other words, the software communicates with the hardware, but without the proper code embedded in the hardware, it's not possible for the software to communicate with it? And without source code given from the developer of the hardware, you're making software that hypothetically should work, but because of the different device hardware it may or may not work...?
And that's also big because some guy on the portal recently found out that all of the eight mega pixel cameras on HTC devices are the same, so it should now be easy to use working cameras on ported and newly created ROMs...
Am I getting anywhere with this?
Click to expand...
Click to collapse
Yes, you got it a bit better now. The software needs to have the same codes embedded in the hardware to correspond with it. The source code is not from the hardware but of the software (kernel source).
Yes if the ROM was ported to other HTC devices with the same/similar camera (some libs will still need to be changed though).
Theonew said:
Yes, you got it a bit better now. The software needs to have the same codes embedded in the hardware to correspond with it. The source code is not from the hardware but of the software (kernel source).
Yes if the ROM was ported to other HTC devices with the same/similar camera (some libs will still need to be changed though).
Click to expand...
Click to collapse
Alright that makes a bit more sense. Thanks for your help guys!
I've started this thread to track the progress of the kernel for Haier W910.
Since Haier refuses to release the source all progress needs to be made by reverse engineering. I've started with the kernel sources for the Acer A9 as it's referred to in the kernel ( Acer CloudMobile S500 ). And so far have created a custom kernel configuration based on the one extracted from the Haier binary kernel.
It compiles without the Acer additions for now but that's as far as I've got. There are no modifications made that are specific to the W910. To proceed there are 2 sources of information. The ones we can get from /proc, /sys , debugfs and other things from the running binary kernel and the ones we can get from the binary kernel and IDA Pro. I'll upload the IDA Pro files with function names obtained from kallsyms.
Thanks to h3adcrash and china jay chou for their help so far. Feel free to join in, everybody is welcome, I'm not an expert myself but with patience and hard work we'll get a source code for the kernel and then we use Cyanogenmod and other custom ROMS.
Kernel source is here: https://github.com/mcirsta/Haier_W910
Please note it's not ready for use !!!
Excellent - subscribed
I will try this out for sure. One step to making this great phone even better
Subscribed!
Did you also give a look at Codeaurora Android for MSM Project ?
It is a project aimed to build Android Open Source Project (AOSP) on Qualcomm chipsets.
Looking into the “release” development branch there is the configuration to make a build for the varoious generic MSM8x60 chipset family.
MMartini65 said:
Subscribed!
Did you also give a look at Codeaurora Android for MSM Project ?
It is a project aimed to build Android Open Source Project (AOSP) on Qualcomm chipsets.
Looking into the “release” development branch there is the configuration to make a build for the varoious generic MSM8x60 chipset family.
Click to expand...
Click to collapse
Yes I did but I've found that the Acer sources were a better match. With Codeaurora it was hard to establish the time in the git repo history when Haier made their fork of the kernel.
Even with the Acer sources there are probably minor differences but they do seem very similar. In the kernel binary I've found references to all the *.c filenames used to build the Haier kernel. Comparing these to the Acer kernel resulted in only 2 missing files in the Acer sources. There 2 missing .c files were for the AUO display and the Synaptics touchscreen which Acer does not use for the S500(Acer A9) so that was normal.
I based my Haier config (https://github.com/mcirsta/Haier_W910/blob/master/arch/arm/configs/haier_w910_defconfig) on the one extracted from the running binary ( zcat /proc/config.gz ) merged with whatever I thought was useful from the Acer A9 config but without Acer specific stuff.
What I should now have is hopefully close to the kernel the W910 uses but without any Haier specific code. I'm now planning on going over the source code to see what's exported through /proc and /sys as this is stuff I can easily extract from the running W910 kernel. For other stuff I'll have to look into the binary with IDA Pro I think.
Is this still ongoing? I know nothing about development but if I can help in any way
facelessone1 said:
Is this still ongoing? I know nothing about development but if I can help in any way
Click to expand...
Click to collapse
Didn't have much of a chance to work on it last week but it's still on. Right now I'm waiting for my soldering station as I need to solder the wires for UART to make debugging easy.
If anyone is willing to take their W910 apart that would help . I've got a spare one that I'd going to work on.
Other than that I'm not really sure how to proceed myself. I've finished the first stage, adapting the Acer one but now I need to find the right setting for our Haier. First thing to do are probably GPIOs.
There's plenty of info you can get from debugfs and proc that might come in handy.
If you want to help you don't need to be a developer, just to be willing to learn. I'm a programmer but I've got no idea about kernel development either.
disassembled
Just a quick update, I've managed to disassemble a W910, reaching the battery. I still haven't found the UART port though but there's still some more to disassemble.
Once I find the UART port I can easily get debugging message so this should help a lot.
it is good news. thanks for yours hard work
I don't know how are you on UART port, but is is this maybe?
facelessone1 said:
I don't know how are you on UART port, but is is this maybe?
Click to expand...
Click to collapse
Wow, didn't know anyone got this far with the dissasembly. I'm suspecting it's one of those pads but haven't been able to confirm it yet. Any idea where a GND is ? If I get a GND then I can check with the RX on different pads and maybe I'll get something. If it outputs anything on the UART.
One other possibility is that those pads are for the JTAG ? Not very familiar with JTAG though.
I was really hoping the UART was on the other side of the board though but oh well.
I've also been able to confirm that Qisda manufactured this and it's also known as the Acer C9 and probably the Acer V350. Qisda developed the SW for it anyway so I'm trying to see if they'll release something.
I'd still like to get a working UART though.
Anyway good job facelessone1
I didn't dissasemble it myself. Someone from the Croatia tried to do some photo shooting underwater and it went badly as the phone is not waterproof. Phone was dissasembled to be fully dry.
Here are some more shots.
That could be JTAG :/
Nexus 4 UART http://blog.accuvant.com/jduckandryan/building-a-nexus-4-uart-debug-cable/
Here original thread of disassembly in Croatian:
http://forum.pcekspert.com/showthread.php?p=2516220
Have contacted this guy, will post back if I get a reply how he did it.
Sent from my HTC Desire using Tapatalk
jukyO said:
Here original thread of disassembly in Croatian:
http://forum.pcekspert.com/showthread.php?p=2516220
Have contacted this guy, will post back if I get a reply how he did it.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks, maybe he'd be interested in some soldering ? I've managed to disassemble the phome myself but now I'm stuck looking for the UART pads, I was hoping they'd just be marked with RX, TX like on many other devices I've seen but not such luck
Nothing on Haier?
Here are some better pictures, maybe someone can help?
mforce2, are you still up for some soldering?
This device could use custom kernel and better rom so much.
I was thinking, last picture, bottom left corner of the board, 4 pads?
facelessone1 said:
Nothing on Haier?
Here are some better pictures, maybe someone can help?
mforce2, are you still up for some soldering?
This device could use custom kernel and better rom so much.
I was thinking, last picture, bottom left corner of the board, 4 pads?
Click to expand...
Click to collapse
Could be but it doesn't have to be 4 pads, I've often found boards where there were only 2 pads, RX and TX so you had to get your ground from somewhere else. I'm not even sure where GND is and my skills in the electronics department are not that good.
I'll give it a shot though, it's not like I have anything to loose since the phone is still in pieces and I'm note really sure I can put it back
Why can't you put it back? What's wrong?
I don't have USB-UART and don't know almost anything about it, but I will be ordering this in a few days.
I wasn't really careful taking it apart and besides I've got an Optimus G now so I've got no need for a W910 as is. If I were able to get some open source kernel working though that would be fun. What I'm really lacking is time and determination but I think I'm going to try and make slow progress with this.
It's still a great phone IMO and I can see this working nicely. I don't really think you need more than the hardware it has.
Hardware is okay, but software part could do much better. I think people would start developing, altho there are no many, if only someone makes brakethrou'
Check out this, same chipset, has kernel, has kitkat
facelessone1 said:
Hardware is okay, but software part could do much better. I think people would start developing, altho there are no many, if only someone makes brakethrou'
Check out this, same chipset, has kernel, has kitkat
Click to expand...
Click to collapse
Sure but Samsung has a lot of community support around it and sources released by the manufacturer. I've tried really hard to get the sources for this W910 but no one wants to release them. With device tree this would have been much easier but ...
We'll see... first I need to find that UART and there's also the problem of UART voltage, I really hope it uses the standard 3.3V levels because otherwise I won't find it with my current USB to serial TTL cable.
X86 Atom Android tablet BLISS ROM. Kernel source & HALS, is tha enough to get going?
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS
madhits45 said:
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS
Click to expand...
Click to collapse
For one, you should ask Bliss OS (x86) related questions in the Bliss OS thread: https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second, I tend to only use source dumps that maintain proper commit attribution. This is our way of giving credit where it is due (the original developers) Most of the source dumps I come across are a bunch of source code, with one commit at best titled, "initial commit" or "dump", and this to me says that there is something not trustworthy about it. I would like to see all the individual commits and changes made throughout the commit history, as this allows us to easily target changes that were made for that specific device.
If others want to go through the trouble of picking out those differences and creating a pull request with the proper attribution attached, we have no issues merging into our releases after testing.
electrikjesus said:
For one, you should ask Bliss OS (x86) related questions in the Bliss OS thread: https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second, I tend to only use source dumps that maintain proper commit attribution. This is our way of giving credit where it is due (the original developers) Most of the source dumps I come across are a bunch of source code, with one commit at best titled, "initial commit" or "dump", and this to me says that there is something not trustworthy about it. I would like to see all the individual commits and changes made throughout the commit history, as this allows us to easily target changes that were made for that specific device.
If others want to go through the trouble of picking out those differences and creating a pull request with the proper attribution attached, we have no issues merging into our releases after testing.
Click to expand...
Click to collapse
Did you look at my source to see if this is a problem? I'm not exactly sure how it needs to look but is this something you have found to be the case with other asus sources in the past? I'd be surprised if it was. I'd love to get a bliss rom for my tablet but I figured this would not be so easy even with x86 support being its base.
madhits45 said:
Did you look at my source to see if this is a problem? I'm not exactly sure how it needs to look but is this something you have found to be the case with other asus sources in the past? I'd be surprised if it was. I'd love to get a bliss rom for my tablet but I figured this would not be so easy even with x86 support being its base.
Click to expand...
Click to collapse
By the time I read your post, the links didn't work. And of the Asus source dumps I've seen in the past, they haven't included any git history
electrikjesus said:
By the time I read your post, the links didn't work. And of the Asus source dumps I've seen in the past, they haven't included any git history
Click to expand...
Click to collapse
Hey Electrik jesus, Here is the new link: https://www.asus.com/2-in-1-PCs/ASUS_Transformer_Book_Trio_TX201LA/HelpDesk_Download/
I'm from Michigan to.. So hopefully you can help another Michigander lol with a bliss build. Asus recently changed up there whole support site and the source code used to only be available on the international site now it seems its also on there US site. The Tx201LA was sold more overseas then in the US. It so similar to about 50 other devices (same Soc) asus made but mostly a lot of them are phones.
madhits45 said:
Hey Electrik jesus, Here is the new link: https://www.asus.com/2-in-1-PCs/ASUS_Transformer_Book_Trio_TX201LA/HelpDesk_Download/
I'm from Michigan to.. So hopefully you can help another Michigander lol with a bliss build. Asus recently changed up there whole support site and the source code used to only be available on the international site now it seems its also on there US site. The Tx201LA was sold more overseas then in the US. It so similar to about 50 other devices (same Soc) asus made but mostly a lot of them are phones.
Click to expand...
Click to collapse
I checked it out, and it is just as I was expecting. no .git folder or anything to show what commits were made on top of the standard kernel source. I guess the only thing we can do about it though is set an example of how to do it...
Example of how a kernel commit history could look: https://github.com/BlissRoms-x86/platform_kernel_common/commits/k4.15.10-ipts
electrikjesus said:
I checked it out, and it is just as I was expecting. no .git folder or anything to show what commits were made on top of the standard kernel source. I guess the only thing we can do about it though is set an example of how to do it...
Example of how a kernel commit history could look: https://github.com/BlissRoms-x86/platform_kernel_common/commits/k4.15.10-ipts
Click to expand...
Click to collapse
So if I understand you correctly the source code needs to be gone through to be pick out the comments etc and then it can be pulled into the bliss x86 source for merging? I think this is above my skill set, what can I do if I dont have the skills to do this?
madhits45 said:
So if I understand you correctly the source code needs to be gone through to be pick out the comments etc and then it can be pulled into the bliss x86 source for merging? I think this is above my skill set, what can I do if I dont have the skills to do this?
Click to expand...
Click to collapse
It's more of a prevention on our end from not giving attribution to the original author. Let's say that someone who worked on a linux project, got the GPU to finally work right with the chipsets in your ASUS. I would like to see that one guy's additions, but even moreso, I would like to see ASUS show that they used his work. Because for all we know, there are hundreds of commits in there that were added, and some of that could be work that someone else deserves to be reimbursed for. The fact that they removed the .git folder shows that they have something to hide. Calling it "trade secrets" shouldn't be allowed when it comes to kernel code.
electrikjesus said:
It's more of a prevention on our end from not giving attribution to the original author. Let's say that someone who worked on a linux project, got the GPU to finally work right with the chipsets in your ASUS. I would like to see that one guy's additions, but even moreso, I would like to see ASUS show that they used his work. Because for all we know, there are hundreds of commits in there that were added, and some of that could be work that someone else deserves to be reimbursed for. The fact that they removed the .git folder shows that they have something to hide. Calling it "trade secrets" shouldn't be allowed when it comes to kernel code.
Click to expand...
Click to collapse
So its about credit and royalties? I understand being upset at asus because they did not or have not credited someone but what can i do about that? Am I stuck at not being able to have my device supported because asus is a bad actor? Is there any way I can get support?
madhits45 said:
So its about credit and royalties? I understand being upset at asus because they did not or have not credited someone but what can i do about that? Am I stuck at not being able to have my device supported because asus is a bad actor? Is there any way I can get support?
Click to expand...
Click to collapse
There is, you could take the route Jakeday has for the Surface line. Since we don't know the author, he created patches to add the support needed to the kernel. It's far from the easy road, but this is what helps developers far more than any source dump
https://github.com/jakeday/linux-surface
electrikjesus said:
There is, you could take the route Jakeday has for the Surface line. Since we don't know the author, he created patches to add the support needed to the kernel. It's far from the easy road, but this is what helps developers far more than any source dump
https://github.com/jakeday/linux-surface
Click to expand...
Click to collapse
What I am confused about is this.
1. Is it a protocol thing? IE asus did not give credit and thus bliss refuses to add support unless they do.
OR
2. Is it an actual road block? IE we cant use the source code as is because it needs more information or reformatting?
Or is it both with more weight on #2?
If its #1 then can we make an exception? and if it is #2 why isnt there some sort of code AI that can redo the code to make it conform to the needed edits, seems like that should be possible. I would hope that if it is #1 only that you would admit that is all it is and help more people instead of forcing people to work around the bureaucracy brought onto them by bad actors like asus.
madhits45 said:
What I am confused about is this.
1. Is it a protocol thing? IE asus did not give credit and thus bliss refuses to add support unless they do.
OR
2. Is it an actual road block? IE we cant use the source code as is because it needs more information or reformatting?
Or is it both with more weight on #2?
If its #1 then can we make an exception? and if it is #2 why isnt there some sort of code AI that can redo the code to make it conform to the needed edits, seems like that should be possible. I would hope that if it is #1 only that you would admit that is all it is and help more people instead of forcing people to work around the bureaucracy brought onto them by bad actors like asus.
Click to expand...
Click to collapse
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
electrikjesus said:
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
Click to expand...
Click to collapse
LOL.. Pretty PLEASE, with big traverse city cherrys on top.
I have also emailed asus to see if they will look at the source code again to properly format it, not likely but worth a shot.
Does this help: https://proandroiddev.com/ooga-chaka-git-hooks-to-enforce-code-quality-11ce8d0d23cb
Is the process of going through the code very time consuming? So even if using git hooks it will take time? Im still trying to understand why there is no AI that can go through it.
electrikjesus said:
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
Click to expand...
Click to collapse
It is important for several people. I hope at some point you have enough time to be able to help us. please help.
I am revisiting this conversation after a few months, and for starters, I would like to say I'm sorry for being rude. Secondly, I would like to use this conversation to start change where we need it. Innovation is the key point here. and if any of us are to build off of one another, we must work together to make it all possible. The lack of commit attribution by OEMs is a blatant disregard for GPL and Open Source licensing. As a ROM team, I would love to work with any OEM to help them through the process of adding a proper commit history. As Bliss, we are open to taking on any new device work, and we have in the past with Udoo-x86 & PINE64, but one of our requirements is that we can release full source, commit history, etc. Everything anyone could need to build off our work.
Too many OEM's are using patents as a way to stab eachother in the back, or use it as a "competitive" road block to stop the sale other devices that may have a similar method or feature. We don't agree with this practice and believe it is driven by greed and the wants of a few, not the needs of the majority. We as Bliss will continue to do what we can to act as an example of what should be done to best facilitate the rapid development of mobile technology and software for all parties involved.