For Those Of You Who are tech geek and has a viewpad 7e. Worth a try to download and take a look at this.
LINK : http://www.viewsoniceurope.com/uk/support/downloads/drivers/?prod_name=viewpad+7e
So I downloaded it, took about an hour. File password protected, any sugustions?
Protected? they should not locked it zzzz
Well after severel e-mails to just about every ViewSonic Support center around the world, they reposted the source file with out the password..Downloaded and extracted. Going to go through it next week. Getting ready to go on vacation for the weekend.
they have posted the source code also, take your time reading, hope there is something use full
http://www.viewsonic.com.sg/downloads/
After a week of playing around with the source code, I have come to the conclusion that ViewSonic posted a very incomplete source. Neither u-boot or kernel will build with the source that they provided. I e-mailed them with the hope that they will update the file to include the entire source for the kernel and u-boot. Only time will tell.
Andyav, Can you tag along with the ICS project for VP 7e?
Link : http://forum.xda-developers.com/showthread.php?t=1724574
Oh yeah. Joined the fb page and posted a pic of my tablet.
Sent from my ADR6425LVW using xda app-developers app
Related
Hello all
I have spent much time recently attempting to modify the zImage included with the Fascinate to include a working recovery image for us to use. However without source code this an extremely difficult (if not possible) goal to achieve.
I am requesting that anyone who owns this device please request the kernel source code from Samsung, so that we may be able to fully utilize our devices. Even if you do not know anything about coding or have any personal use for this source code, it is your right to request it as an owner of the device, and this code will help us all immensely once it is in the right hands.
Requests for source code can be filed on Samsung's website at : opensource . samsung.com/ (remove the extra spaces, apparently I can't post links yet)
Click on the mail icon at the top to submit your request.
Thank you for your assistance.
Requesting right now. Thanks for what your doing! Any updates since last night?
i just finished sending one in
jt1134 said:
Hello all
I have spent much time recently attempting to modify the zImage included with the Fascinate to include a working recovery image for us to use. However without source code this an extremely difficult (if not possible) goal to achieve.
I am requesting that anyone who owns this device please request the kernel source code from Samsung, so that we may be able to fully utilize our devices. Even if you do not know anything about coding or have any personal use for this source code, it is your right to request it as an owner of the device, and this code will help us all immensely once it is in the right hands.
Requests for source code can be filed on Samsung's website at : opensource . samsung.com/ (remove the extra spaces, apparently I can't post links yet)
Click on the mail icon at the top to submit your request.
Thank you for your assistance.
Click to expand...
Click to collapse
You just want everything handed to you, don't you? Quit being so lazy and do some actual work.
But seriously everyone, please take the time to fill out the request. The sooner we get the source, the quicker we'll see some ROMs.
namebrandon said:
You just want everything handed to you, don't you? Quit being so lazy and do some actual work.
But seriously everyone, please take the time to fill out the request. The sooner we get the source, the quicker we'll see some ROMs.
Click to expand...
Click to collapse
This guy again, huh
Seriously, thank you to anyone who fills out the request. Remember, as an owner of the device it is your right to have access to the kernel source code, and it takes less than 2 minutes to fill out the request form. Tell your friends!
http://opensource.samsung.com/reception/reception_main.do?method=inquiryView
There's the direct url for the lazy.
Thanks for direct link. Filled one out through my phone. Made it sound pretty formal lol. Let's hope we get the ball rolling soon, starting to miss all the active development on the older phones.
Submitted a request.
frostman89 said:
Thanks for direct link. Filled one out through my phone. Made it sound pretty formal lol. Let's hope we get the ball rolling soon, starting to miss all the active development on the older phones.
Click to expand...
Click to collapse
Once we get source we will be able to get a working recovery, then the floodgates will be open. My personal mission is to get AOSP/CM on the phone immediately after that happens, can't stand the TouchWiz and I intend to destroy it!!
Submitted a request. Only way I'll be buying this phone is if I can eliminate all Verizon/Samsung UI/apps. Even a vanilla ROM will do over the TouchWiz crap.
I am a little confused. What source code are you requesting?
If you go to h**p://opensource.samsung.com/, click on 'Mobile' at the top, then Ctrl-F for "i9000", you can find (what looks like) a zip containing both the kernel image and files you can plop in an aosp tree in order to build roms for the Galaxy S.
Maybe you guys are talking about source specifically for Fascinate?
partner55583777 said:
I am a little confused. What source code are you requesting?
If you go to h**p://opensource.samsung.com/, click on 'Mobile' at the top, then Ctrl-F for "i9000", you can find (what looks like) a zip containing both the kernel image and files you can plop in an aosp tree in order to build roms for the Galaxy S.
Maybe you guys are talking about source specifically for Fascinate?
Click to expand...
Click to collapse
Yes, we are requesting the source for the fascinate. As the i9000 is a completely different device, and we have the sch-i500
fallingup said:
Yes, we are requesting the source for the fascinate. As the i9000 is a completely different device, and we have the sch-i500
Click to expand...
Click to collapse
Okay, thanks. That clears it up.
So I guess Samsung is currently in violation of the GPL, then? (And probably other licenses).
partner55583777 said:
Okay, thanks. That clears it up.
So I guess Samsung is currently in violation of the GPL, then? (And probably other licenses).
Click to expand...
Click to collapse
Well i am sure they will release the source, its just taking them longer than i would like. They released the source for the Epic about 3 days after the hardware was released, and we are at about a week now.
Yeah, they'll post the code soon, they're just taking their sweet time about it.
Source code released! Thanks guys!
jt1134 said:
Source code released! Thanks guys!
Click to expand...
Click to collapse
and source code fail!
Is the source code on opensource.samsung.com still the wrong one?
ludeboy said:
Is the source code on opensource.samsung.com still the wrong one?
Click to expand...
Click to collapse
Not sure yet. We've confirmed they've had at least two different files for download since last night. The original one wasn't' working. I'm at work, so can't tell you much about the second (latest) one.
Looked thru out the whole site and i can not find a link to migueltherocker mytouch slide 3g. Kernel Not seeing a link to the zip file on sliderom bible.
Many Thanks in advance.
Thats because it eas deleted due to.the fact that hr failed to follow the GPL
Sent from my T-Mobile myTouch 3G Slide using XDA App
Miguel compiled and released a custom/modified Android/Linux Kernel, which is released under an open source (GPL) license: one of the requirements is that when you release the software, you must also release the modified source (with a choice of methods how to do that). At the time of release, Miguel did not comply with this restriction/requirement of using the Linux/Android Kernel.
Currently the XDA forums are cracking down on people who don't comply. The download links were removed (no links that violate the GPL license will be hosted on XDA per sites policy) until Miguel corrected the issue (provided/included the source). It looks like that did not happen in a timely enough manner, and so the thread seems to be deleted/removed.
So technically you won't find a link to the release on XDA as it violates the sites policy and will be removed/deleted.
Hopefully Miguel returns and includes the source (while a github is nice, it's not the bare minimum required to comply with the GPL) as his kernel release seemed to be very promising. (I was using it on a CM6 variant, but it proved too unstable, and was holding out for a CM6 adopted variant. I did like the responsiveness of the smartass-interactive governor, and going back to the previoius onDemand is a tad dissapointing).
So long story short: You won't see links posted here, until Miguel (hopefully) returns, however the thread deletion was without notice, so there may be more happening behind the scenes that we are unaware of, so I would guess that the future of that particular kernel remains uncertain. :/
I believe the real reason he hasn't posted was because he was "grounded" (believe it or not, he's actually 15. Jeez, what a prodigy), and XDA probably considered it abandoned or something
Yeah I remember he posted that a while before it was deleted
Sent from my T-Mobile myTouch 3G Slide using XDA App
petraman said:
I believe the real reason he hasn't posted was because he was "grounded" (believe it or not, he's actually 15. Jeez, what a prodigy), and XDA probably considered it abandoned or something
Click to expand...
Click to collapse
NO. after his thread was closed and we were all notified of why, he stated that he was then grounded and couldn't upload the source. that was not the original cause.
I was explaining his absence, not the reason why it was removed, which was already mentioned early on
I hope he returns and I'm looking forward to see some updates.
This shouldn't really be in Development
Anyway, as I'm sure you all know by now Miguel won't be around for a bit and because of this he is unable to comply with the GPL. Non compliant threads are deleted after a certain period of time has elapsed, if the OP hasn't updated with sources etc.
Already everybody... it's time for Operation Pepperoni! The Linux kernel is open source and if you want to see some cool stuff coming out for your Photon 4G, we need to get Motorola to give us their source code - as is legally required by the GPL! You can start by posting on the discussion boards over at Sourceforge for the Atrix (the Photon's "cousin") asking for the source for the Photon 4G's GNU GPL components!
Link: http://sourceforge.net/motorola/atrix/discussion/
LET'S GET THAT SOURCE!
I am confused on where to start to request the kernel source.
Good idea, I also dropped by motorola's support forums and requested that they update their project list on opensource.motorola.com and release the source code. They'll probably lock the thread.
ericdabbs said:
I am confused on where to start to request the kernel source.
Click to expand...
Click to collapse
For now just post in the Atrix forums that I linked to in the original post.
don't worry I bumped the thread that was there, unless you wanted me to just make a new thread.
Just posted.
Can't wait to get my hands on this thing
brianez21 and timtim, thanks for backing me up on that motorola forum. I'm surprised they didn't lock it by now.
I just want to remind everyone to keep the pressure on Motorola to release their sourcecode. The sooner we get that the more likely we fix our 4g issue with the bootloader. So far the forum manager says that he is in direct contact with the devs who are working on the release right now. Lets, as a community, keep on them to hold to their promise. Don't be mean or irate. Simply let them know that this is important to you. --> https://supportforums.motorola.com/thread/55574
Keep your eyes here for the source code. Right now you'll get a 403 error but once they post the code it'll probably be at this link: https://sourceforge.net/motorola/photon4g/home/Home/
sub2k1 said:
I just want to remind everyone to keep the pressure on Motorola to release their sourcecode. The sooner we get that the more likely we fix our 4g issue with the bootloader. So far the forum manager says that he is in direct contact with the devs who are working on the release right now. Lets, as a community, keep on them to hold to their promise. Don't be mean or irate. Simply let them know that this is important to you. --> https://supportforums.motorola.com/thread/55574
Keep your eyes here for the source code. Right now you'll get a 403 error but once they post the code it'll probably be at this link: https://sourceforge.net/motorola/photon4g/home/Home/
Click to expand...
Click to collapse
I didn't get 403- it took me to a log in page.
You sign up and see the dealio about this?
ScandaLeX said:
I didn't get 403- it took me to a log in page.
Click to expand...
Click to collapse
It is requesting that you log in to verify that you are authorized to access that page. Once you login that link will say 403 Forbidden. Whereas any other link you make up will simply say 404.
So am i the only one here that notices that there hasn't been an update for a ROM in about a month? What's been going on?
Not really. IHO is still alive and well. Some of the froyo roms are at end of life and are considered more or less finished (Harmonia and Bumblebee to name a couple).
Sent from my LG-VM670 using Tapatalk
I don't think it helped that the kernel site was hacked and has been down...?
We are all waiting for kernel.org to be back up, kinda hard to build without source.
Some hackers must sit around and think "Who can I piss off today? I know, most of the android dev community." Some hackers just suck.
Sent from my VM670 using XDA App
This explains a lot.. I've been waiting for an update on IHO for a while
Sent from my LG-VM670 using xda premium
Thanks for the information I had no idea kernel.org got hacked.
Sent from my LG-VM670 using Tapatalk
It is hard waiting for kernel.org to get back up, but I'm more than willing to wait it out patiently. We are talking about the basis to the entire Linux community here, not just Android. While we are pretty sure the hackers couldn't have gotten anything in that wouldn't be noticed due to the inherent nature of the repository system, it is prudent that they do such dilligent work checking everything out to be certain. Imagine if someone was able to insert malicious code at the basis of the kernel's distribution system, botnets that instantly compromise millions of computers, all user data compromised the moment you update your system, the imaginary horror stories are all too real possibilities.
Go outside, fix that garage door, paint that fence, or at least take down last year's xmas lights. Kernel.org will be back up soon enough, and we can all go back to worrying about which color looks best on our phones buttons.
@JerryScript:
I'm guessing you didn't get the codaurora repo patched into your cm7 build system like you mentioned you were going to try?
I bet it's murder to patch CAF source addresses into the repo manifest instead of kernel.org, huh?
bummer.
that blog link you posted over in the build-your-own-rom thread on AC worked great for codeaurora by itself, which I appreciate greatly since I was already working with that before kernel.org bit the big one. then I couldn't sync it for a while until you pointed me the way.
bigsupersquid said:
@JerryScript:
I'm guessing you didn't get the codaurora repo patched into your cm7 build system like you mentioned you were going to try?
I bet it's murder to patch CAF source addresses into the repo manifest instead of kernel.org, huh?
bummer.
that blog link you posted over in the build-your-own-rom thread on AC worked great for codeaurora by itself, which I appreciate greatly since I was already working with that before kernel.org bit the big one. then I couldn't sync it for a while until you pointed me the way.
Click to expand...
Click to collapse
Blarf told me that CAF was to much of a mess to rely on. I'm currently syncing using TI's omapzoom, will let you know if I get a successful build environment setup.
Edit-- There is an easier way than manually patching the mirror, just use the following:
Code:
$ repo init -u git://github.com/inferiorhumanorgans/android.git -b gingerbread --repo-url=git://git.omapzoom.org/tools/repo.git
Notice the --repo-url appended to the normal init line, that will do all the patch magic for you. All you have to do is change the remote.
Big thanks to Sanghee Kim for posting this:
https://groups.google.com/forum/#!topic/repo-discuss/r0wkGaloA5k
@jerryscript I would highly suggest making your own thread with the above information just to make sure all of the devs see. Might help them out a little
Sent from my LG-VM670 using Tapatalk
gannon5197 said:
@jerryscript I would highly suggest making your own thread with the above information just to make sure all of the devs see. Might help them out a little
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I plan on it, as soon as I finish a successful compile.
Sorry I hijacked your thread, to answer your op, should have some new builds soon.
Over the years we have asked Fuhu/Nabi for the source for Nabi2, NabiJR, NabiXD, Dreamtab, etc. A year or more ago they released the source for the Nabi2, NabiXD, and JR. Unfortunately the kernel source was nothing more then a snap shot of the kernel anyone could get but no board specific code, or even a defconfig. I have continued to politely ask over the years and they just released for the Nabi2S, Dreamtab, and BigTab. It still looks quite rough but I am pleased to announce with a little hacking to what they released and I was able to build a booting kernel for the Dreamtab(see attached). I also contacted them back, and asked if they could revisit the code for the Nabi2, JR, and XD. We will see what transpires but it's the best effort they have put forth to date.
https://www.nabitablet.com/support/source-code
aicjofs said:
Over the years we have asked Fuhu/Nabi for the source for Nabi2, NabiJR, NabiXD, Dreamtab, etc. A year or more ago they released the source for the Nabi2, NabiXD, and JR. Unfortunately the kernel source was nothing more then a snap shot of the kernel anyone could get but no board specific code, or even a defconfig. I have continued to politely ask over the years and they just released for the Nabi2S, Dreamtab, and BigTab. It still looks quite rough but I am pleased to announce with a little hacking to what they released and I was able to build a booting kernel for the Dreamtab(see attached). I also contacted them back, and asked if they could revisit the code for the Nabi2, JR, and XD. We will see what transpires but it's the best effort they have put forth to date.
https://www.nabitablet.com/support/source-code
Click to expand...
Click to collapse
I would love to see if any progress comes out of this. Did anyone ever manage to get any other ROMs working for this besides the ones that was ported from the Nexus?
I've been away from these devices for over a year.
SMcC2 said:
I would love to see if any progress comes out of this. Did anyone ever manage to get any other ROMs working for this besides the ones that was ported from the Nexus?
I've been away from these devices for over a year.
Click to expand...
Click to collapse
I have a working Dreamtab kernel. The other devices source looks much worse. I asked them to try again for Nabi2 but never heard back. Haven't done much else, been messing around with LG Gpad lately.
Wonder if they would do the same kernel snapshot with the SE. The latter should also apply to the Mattel-themed variants, e.g. American Girl, Barbie, Hot Wheels and Fisher-Price considering they run off the same hardware with ROMs customised to account for the edition.