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.
Related
Not sure if we've had this response so far but I wanted to share it.
______
Dear Dave,
Thank you for your continuous interest on our product.
In particular, we''d like to recommend to use toolchain 2009q3 version. Our development team recommend this version.
(arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2)
Please send full details of your build error log.
Thank you.
Sincerely yours,
Oh, where to begin..
I believe that's the toolchain they recommend in their "instructions".. Regardless, we figured that out rather quickly.
The problem here is that what they released to us was not their production source code. It was some early development version of it, with a number of issues, the most prominent being it didn't even compile as provided.
The fact that we had to patch sound/soc/codecs/wm8994.c so that the phone wouldn't drop audio 5-10 seconds into every phone call is pretty much concrete proof that what we were given was development code, not production code.
I'm going to pass on the exact same message back, we'll see what happens.
Probably nothing.
at this point it's fairly pointless. we have been hastling them for almost a month now, and they've done nothing. despite all the issues with the code, our dev team has gotten their provided kernel source to boot and run with no issues, hence the overclocking kernels available. even if they did release the actual source now it's basically worthless. unless it's for a higher kernel version we can use for a froyo rom.
sonofskywalker3 said:
at this point it's fairly pointless. we have been hastling them for almost a month now, and they've done nothing. despite all the issues with the code, our dev team has gotten their provided kernel source to boot and run with no issues, hence the overclocking kernels available. even if they did release the actual source now it's basically worthless. unless it's for a higher kernel version we can use for a froyo rom.
Click to expand...
Click to collapse
Its not whether I its pointless or not, they need to be held accountable for uploading bad source which I believe is against the gpl. Funny how their build sh is configured for 2010 and they recommend 2009q3...
Sent from my SCH-I500 using XDA App
I agree, but is sending them a million emails that they mostly ignore really "holding them accountable"? I think not.
So ignoring them is the answer?
I think not.
Feedback is the most civil thing at this point. If its ignored, I'm sure more stern action can be taken, if the community as a whole decides to.
Hi
I saw a post in the dev section titled "Source code (Android kernel, Ubuntu) now available".
I saw it here and downloaded it in case it disappears:
https://opensource.motorola.com/sf/sfmain/do/go/rel1543?selectedTab=files
What does this mean for the Atrix now? Is this anything special or won't help us at all? Will it be easier for the devs to crack the bootloader?
I'm still up in the air on whether to buy this phone or not and I'm just waiting to see if more development is made on it to choose.
Bell has lowered the price of the phone by $100 until March 31st so I would like to make my decision before that time. Nexus S and Incredible S are also coming to Bell in April so I'm not sure what to do! But Atrix with unlocked bootloader is like unlimited potential!
Thanks,
Elliott
I too would like to know as well what his could mean to the Atrix. ANy one care reply?
please.
Here are the words from another member at this thread Source code (Android kernel, Ubuntu) now available
ikenley
It will make it easier for tweaks and optimization to occur without access to the bootloader.
It could also mean that there is a possibility for custom Roms for the truly gifted Developers who can do it without modifying the Kernel. Has happened for the Milestone and is currently being undertaken for the Milestone 2 (Droid 2)
Click to expand...
Click to collapse
Thanks I saw that too...
Ahhh I want to wait until the Incredible S and even the Nexus S but the thought of having a dual core proc that is very fast is tempting to me...knowing that these devices only have single cores they're not as future proof...but neither is the Atrix if no development is done on it.
I'm fairly sure the source wont disappear for android that is... the kernel stuff maybe? I think android is GPL'd so it has to be released after modification as part of the license.
Starholdest said:
Thanks I saw that too...
Ahhh I want to wait until the Incredible S and even the Nexus S but the thought of having a dual core proc that is very fast is tempting to me...knowing that these devices only have single cores they're not as future proof...but neither is the Atrix if no development is done on it.
Click to expand...
Click to collapse
I'm in the same boat as you. Even in Canada.
But I guess I'm going to take the plunge and get this phone I'm getting it tomorrow or the day after.
My reasoning is that there will be a new nexus by the end of the year. But I agree fully to what you said above. I wish Motorola made the Nexus S. I wish it was the atrix but an official google device. If only that happened.
Source Code : OSHWT_U1_4.257.14
Starholdest said:
Hi
I saw a post in the dev section titled "Source code (Android kernel, Ubuntu) now available".
I saw it here and downloaded it in case it disappears:
https://opensource.motorola.com/sf/sfmain/do/go/rel1543?selectedTab=files
What does this mean for the Atrix now? Is this anything special or won't help us at all? Will it be easier for the devs to crack the bootloader?
I'm still up in the air on whether to buy this phone or not and I'm just waiting to see if more development is made on it to choose.
Bell has lowered the price of the phone by $100 until March 31st so I would like to make my decision before that time. Nexus S and Incredible S are also coming to Bell in April so I'm not sure what to do! But Atrix with unlocked bootloader is like unlimited potential!
Thanks,
Elliott
Click to expand...
Click to collapse
I see this is the source code for the original retail version (OLYFR_U4_1.2.6). I noticed on there website they also released the source code for what looks like the newest build they have out getting beta tested right now (OSHWT_U1_4.257.14) I might be wrong on that, but if it is, it seems Motorola might be getting easier to work with.
Motorola Website source code >> OSHWT_U1_4.257.14 <<
**Edit** Looks like this is the Source Code for the 'Atrix Webtop'. My bad...
Would it be possible to create a ice cream sandwich rom for the Viewsonic G tablet?
I dont think they have released source code, let alone a phone with the OS yet...
Quickly, I'll hold them off while you go hide!
yashmack said:
I dont think they have released source code, let alone a phone with the OS yet...
Click to expand...
Click to collapse
try again.. Galaxy Nexus will have ics
They said tonight that the sdk will be released today
Sent from my LS670 using Tapatalk
Aaaaaaaand the SDK is out.
http://developer.android.com/sdk/android-4.0.html
Thus this is a valid question which I was going to ask myself
Its not a valid question yet. Once the source is released I hope we can see a stable ics room that's better than the hacked together honeycomb we have
Sent from my Cyanogen Thunderbolt.
drx69 said:
try again.. Galaxy Nexus will have ics
Click to expand...
Click to collapse
I know this but the phone has only been announced, it hasnt been released into the wild yet, no one has one in their hands yet
well, except maybe a few reviewers here and there
pretty sure it wont hit shelves or stores for a few more weeks
---------- Post added at 03:41 AM ---------- Previous post was at 03:29 AM ----------
muerteman said:
Its not a valid question yet. Once the source is released I hope we can see a stable ics room that's better than the hacked together honeycomb we have
Sent from my Cyanogen Thunderbolt.
Click to expand...
Click to collapse
Im not too sure if that will happen, from what im reading the devices that will support ICS are going to be gingerbread devices
If there isnt a gingerbread ROM/kernel it probably wont support ICS
at best it will be as stable as the most stable gingerbread ROM... so not too bad
Im wondering if it will work with the honeycomb kernel the devs are creating from scratch
Theoretically the tablet has the specs to run ICS but its a matter of Google making the source code open source. If it was anything like HC I think we're gonna be out of luck.
My understanding is that Google never intended to make Honeycomb open source in the hopes of avoiding people attempting to put HC on their phones. ICS should be open source, and Google has already stated several times from what i have seen that they intend to make the codes public. I don't see why we wouldn't have a decent ICS rom out in the next month or two.
Sent from my SCH-I500 using XDA App
At the very least we should probably see a CyanogenMod version, since its an officially adopted Tablet. I'm looking forward to it.
I doubt it. We don't have an official honeycomb rom so I don't see ics being supported at all on gtab... I truly believe development for our gtab is officially dead.
jedibbq said:
I doubt it. We don't have an official honeycomb rom so I don't see ics being supported at all on gtab... I truly believe development for our gtab is officially dead.
Click to expand...
Click to collapse
Well, considering that HC was never officially released as open source, I don't know why you would expect a full-featured ROM when the best that anyone could do was essentially a modified bootleg of an existing tablet's firmware. There a TON of G-Tablets out there thanks to the Woot sales, so I think it would be silly to assume that just because development has hit a lull for the last few months that it is totally dead. Give it a few months, and I bet we will see a good ICS ROM made available for our G-Tablets.
I highly doubt that the g-tablet is dead. I myself and one of my friends imported one of these just to get our hands on it.
It will only be dead if people believe that we don't want firmware for it. There is plenty people out there that are looking forward to newer firmare, we just quietly wait patiently for the master coders to do their excellent work.
TBH, I can't thank everyone here enough for the hours they put in to their hobbies. Greatly appreciated.
Google has officially stated that they WILL be releasing the source to Ice Cream Sandwich, so it's VERY likely that there eventually be multiple ICS ROMs (including Cyanogenmod) for the G Tablet.
It's out
I just read that Google has released the source code....
ICS Code-Open Source
will we be seeing an ICS Rom for our Viewsonic G-tab now that the source code was released??
rmejia25 said:
will we be seeing an ICS Rom for our Viewsonic G-tab now that the source code was released??
Click to expand...
Click to collapse
This tablet is on life support. ROM development is a small fraction of what it used to be a year ago. Updates are scarce. Be grateful for the value we got out of it over the past year.
The time to move on is fast approaching... and my eye is on the Asus Transformer Prime.
doug3673 said:
This tablet is on life support. ROM development is a small fraction of what it used to be a year ago. Updates are scarce. Be grateful for the value we got out of it over the past year.
The time to move on is fast approaching... and my eye is on the Asus Transformer Prime.
Click to expand...
Click to collapse
Part of that is to blame on no Honeycomb source, why would devs waste time reverse engineering when they could wait for ICS? Someone will make an ICS ROM, the lull has been to blame on their actually being NOTHING to do on this device with no Honeycomb source.
Now if those Nvidia drivers end up being a pain, it might be another story.
Sent from my T-mobile G2 using Tapatalk
Nospin said:
Part of that is to blame on no Honeycomb source, why would devs waste time reverse engineering when they could wait for ICS? Someone will make an ICS ROM, the lull has been to blame on their actually being NOTHING to do on this device with no Honeycomb source.
Now if those Nvidia drivers end up being a pain, it might be another story.
Sent from my T-mobile G2 using Tapatalk
Click to expand...
Click to collapse
You can blame the lack of source code, I think I'll stick with blaming Viewsonic for not pushing at all to get drivers or any type of updates to us on this device. Without Viewsonic or Nvidia providing drivers we're going to be in for a rough ride.
I can't seem to find any threads about ICS for the Tab. I thought with the release of the source there would at least be some threads asking if anyone can build a rom. Is there more that needs to come out before this starts to happen? I know build are already being created for my phone (Incredible). Just surprised I guess. Of course I'm no developer, so maybe there's something I'm missing?
ejkeebler said:
I can't seem to find any threads about ICS for the Tab. I thought with the release of the source there would at least be some threads asking if anyone can build a rom. Is there more that needs to come out before this starts to happen? I know build are already being created for my phone (Incredible). Just surprised I guess. Of course I'm no developer, so maybe there's something I'm missing?
Click to expand...
Click to collapse
I'm not bashing, but for the tab we have "cooks" that work off a template (Stock ROMS). So far, all the ROMS we've had haven't introduced anything new, they've only improved on what has existed. I also realize there was no honeycomb source to work with.
Again, I love what the devs here have done for us thus far. But, I fear we will have no ICS love for the tab until we have an ICS leak straight from Samsung.
I guess that's pretty accurate, it's a shame and kind of odd as they gave out the tab at the developers convention, you'd think it'd be more popular amongst those that know how to do these sorts of things....
ejkeebler said:
I guess that's pretty accurate, it's a shame and kind of odd as they gave out the tab at the developers convention, you'd think it'd be more popular amongst those that know how to do these sorts of things....
Click to expand...
Click to collapse
Nvidia doesn't release their source so the drivers are proprietary. I'm guessing the 3.X drivers aren't 100% compatible with ICS which means, like someone just said, a leak needs to occur before a working build can be developed.
Supposedly ICS is built off the honeycomb framework. However, the honeycomb specific source is not flagged in the ics source. I am sure we will see it sometime soon in alpha, but we're just now leaking out 3.2 so don't expect it as fast as say the nexus s or evo.
Once galactic stryder started to collected crowd funding to buy a new le max 2 and then also ordered it and then it now arrived because of some issues. Anybody can tell me what happened to the money of yours you donated? And why he is not developing? Just curious to know that!
Heyyo, he posted a while back that he has had stuff going on in life so it was delayed a few months for software development.
Tbh even once he starts it could be a few months before he has a properly working x2 build as he uses his own kernels with some stuff based on Darkobas (Oreo) and I haven't seen anything happening there either... So really who knows when we shall see some AOSPA x2 stuff.
Such is the way with crowdfunding anyways. We funded a device for him and it will take time for things to get done. I know I donated a bunch too but hey I am barely making progress on Oreo but I try with my limited software development skills and time.
He wrote to me that let max 2 "will be supported on our AOSPA 8 from April"
Let's wait for the guy solve his issues. Nobody forced us to donate. I am sure that he didn't run away with the LeMax2 :laugh: Any user should understand that developers are also people with jobs, family, etc. Heck, even to reply to xda Q&A takes time (thanks @ThE_MarD), so it's often to see that there's no answer from the dev to "why torch is not working" question or stuff like that.
Honestly speaking, even without him, the development of X2 is at a very good level by my standards.
I think we should also donate to infrag and all the others who worked really hard to fix the builds for this device.
Thanks to all for info
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
nope that's not correct bro recently he updated his profile and added le max2 and I can see some commits done in his lambda kernel so everyone cheers and hope for good
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
Forgive me, but it's a sad statement.
Actually, a passionate and skilled guy who did a good job with a very similar phone, offered to work on improving support for this device. I can't event think he needed another underpriced (because of lack of official support from manufacturer, bankrupt) smartphone
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
He is very active kernel dev for Le pro 3, so it wasnt like, hey lets give new phone to random guy.
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thanks for clearing situation
Nice to see you after long break, hope you like yours new device
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thank you galactic stryder!
https://forum.xda-developers.com/showpost.php?p=75925873&postcount=318