Related
This thread is in regard to the unofficial development of the Cyangonmod 7.1 for the Dell Streak 7. Absoluetelly nothing works. So a lot of work needs to be done.
First git the entire Cyangonmod 7.1 tree from them, and then drop these files into the device/dell/streak7 folder
http://www.mediafire.com/?q1w57v797u9p953
This rips the files from a stock Android 2.2 image, so you need to make sure that you are at a stock 2.2 image. My next goal is to upgrade to a stock HC and try making the scripts for that and see if it gets me closer.
As of right now, it boots "Dell" logo, then goes to the black screen with "ANDROID" on it, and that is as far as I can get it.
Look at the files, and let me know what changes I should make and in what script.
Driver wise, I believe you might be better off trying to backport the stock HC drivers.
GB <-> HC/ICS are more similar then eclair/froyo <-> GB in respect to drivers.
That's the reason it took half a year to hack together GB for the s5 and why it only tooks weeks to hack froyo from eclair
Rumor has it that dell attempted to port GB to the s7 before giving up, they lost a couple months at Q12011 doing that and likely scrapped everything, then they restarted on porting 3.1 then moved to 3.2 and that's why the summer was pretty quiet and why the S5 prob got no updates all summer
I dont have any substantial evidence to back any of it up, but the timelines all line up far too nicely, dell prob has only a single team for the s5/7/venue, the s10 is done by a different company.
Yeah, I am thinking I am going to try that direction next. Got a list of all the libs, now just need to re-write the scripts.
CM 7.1, Is that gonna be Honeycomb based?
Mysticales said:
CM 7.1, Is that gonna be Honeycomb based?
Click to expand...
Click to collapse
CM7 is Gingerbread...
Nice, gonna check this out once it arrives
You should have killed me, when you had the chance
Mysticales said:
CM 7.1, Is that gonna be Honeycomb based?
Click to expand...
Click to collapse
Cm never did honeycomb because google never released source
I've pulled a list of all the files I need to work with, now will be the time consuming part of checking the scripts to see if they are already listed and then adding the ones that are not listed.
Not to sound negative, but with Dell having released the official HC build and so, would people really use Gingerbread on their tablet?
Mysticales said:
Not to sound negative, but with Dell having released the official HC build and so, would people really use Gingerbread on their tablet?
Click to expand...
Click to collapse
I'm doing this for the same reason any hacker does anything.
For the sheer f*** of doing it.
Currently I am working on building a tegra2 2.6.35 gingerbread kernel.
Hypothetically, if he can get GB to actually work (and by work i mean functional with all the hardware functioning properly) he'll be a dozen steps closer to being able to port over to ICS.
I cant say that it would ultimately lead to ICS, but the documentation generated would help a lot (assuming it's all documented lol)
Documentation......I knew I was forgetting something.
Well, the easy steps right now will be as soon as I get it to boot using CM7.1, i will figure out how to git it up to Cyangonmod and have them review it. Currently I got the information I need to port to CM7.1, its just a matter of plugging that information in. The problem I am wondering is that the current kernel in their directory, I have no idea who built it or what it contains.
Building a working kernel is very tough since I have never done it before. Nvidia does have a Tegra 2 Gingerbread image built and a Tegra 2 Gingerbread kernel build available, its just a matter of me figuring out how to get them to work because I have never done this before.
So this usually consists of me doing the following
1. Run 'make -j4'
2. Get error
3. Research error
4. Attempt some fixes
5. Repeat step 1-4
The s7 is really similar the nvidia's vendeta reference board, and I think that's what dell tried to base their GB attempt off of.
(Also what cpu are you using? -j4 is small unless you're compiling on a laptop or something)
TheManii said:
The s7 is really similar the nvidia's vendeta reference board, and I think that's what dell tried to base their GB attempt off of.
(Also what cpu are you using? -j4 is small unless you're compiling on a laptop or something)
Click to expand...
Click to collapse
Actually it is the ventana (tegra 2 250) board as far as I can tell.
I've got a couple files that say 'init.ventana.rc' on them, plus 'init.streak7.rc'. These were pulled from the ~/ directory
I am in contact with Nvidia in regard to some questions I have but haven't heard from them in a week, they are probably slammed with questions all the time.
Just wanted to say, that nice to see someone interested and capable in doing something for streak7. keep up mate
Sent from my Dell Streak 7 using Tapatalk
giveen said:
I'm doing this for the same reason any hacker does anything.
For the sheer f*** of doing it.
Currently I am working on building a tegra2 2.6.35 gingerbread kernel.
Click to expand...
Click to collapse
Oh dont get me wrong, Its cool that you do that, its the same reason I mess around. I guess its just with Steve working on Honeystreak R8+ and ICS. Just was a wonder how many would use GB.
Too bad one can dual boot. Like have HC on Nand, and boot into a diff Android build on SD. Why would this be cool? Cause honestly.. sometimes HC can suck, least when it comes to mass storage mode. I could see myself using a dual boot at times to boot in GB with my streak 7. =)
the dell streak 7 has a Nvidia Harmony broad also could you not use cm7 Advent Vega as a base
Yes, I have looked into it, and in fact I've stolen lots of information from that build and put into into the build system I am working on.
So before I go on a holiday break, a bit of an update.
Bad News:
I started all over and started working my scripts. Currently its having a problem with my 'recovery.fstab'. Its saying its not there, but I FREAKIN KNOW ITS THERE!!!!!! and its written correctly in my scripts.
Good News:
Two successfull zImages built, one based off of Nvidia's 2.3 stuff combined with DJ_Steve's configuration, probably won't boot because its missing some drivers.
And the other is a DJ_Steve's HC kernel, but I asked him to check over some errors I got, even though it successfully built.
The reason why I built new zImages is because I couldnt' verify who created the kernel file in the github. The label on the folder was 'koush' but I asked him and he said he did not build it, so I have no idea who started the project, hence why I decided to build a new one.
So AFTER I figure out the recovery.fstab error, I will try out both of my new kernels and see which one does the job.
After I take a break.
I got several errors out of the way but....
The CM7 build is on hold, indefinitely. I am currently helping out with the ICS build and it takes a lot of my time and also taking care of my pregnant wife and two children. With the release of ICS, I might not even bother with it after this. And if I do, it will be a casual effort.
I see working on the ICS build as the assistant to a very talented ROM developer a a huge learning process and it is actually helping me become much better at making ROM's.
I recently flashed my P1000 with both Cm9 & AOKP Roms, after a quick installation of both Roms, i decided to AOKP rom as it seemed to offer more features and a secondary launcher which i found quite useful.
My question is in comparing the two roms, what are the main differences and features of each rom? Given that people are clearly fond of both.
I've that the Usb host Control apparently works using a Y cable in the Cm9 Rom,
I've read through AOKP rom thread where this feature is barely if even mentioned.
i am planning on getting a female converter next week to test this and am hoping i can stay on the AOKP rom but if not the Usb host feature might swing me.
Can someone spread some light on this thread please.
Since you are getting the cable anyway, why not you try and let us know if AOKP works with that.
Sent from my GT-P1000 using xda app-developers app
I sure will do that Though it does say on the 1st page of Cm9 USB HOST works with Y cable and nothing related to USB hosting in AOKP thread, though i read the kernels were merged, so as well as trying to find out if AOKP supports USB hosting, i am wanting to find out what features Cm9 has that AOKP doesnt and visa versa.
Yeah, the "secondary" features such as USB host and TV out are not tested/mentioned in AOKP.
We need more users to feedback.
As for direct features comparison, it is also hard. Each gas their tweaks.
But AOKP allow me to toggle off the navbar completely easily even in the middle of a game.
That is superb.
Sent from my GT-P1000 using xda app-developers app
I will be sure to add my feedback once tested, im hoping to to get a mouse and keyboard working on a Usb hub, but not sure if they can both be run at the same time, hopefully they can.
TV-out also brings up some interesting questions, as far as i know TV-out isnt working on the either builds, however i cant confirm that since i dont have a TV-out cable, and reading it doesn't work has made me somewhat reluctant to get one. Possibly someone else could confirm the workings of the TV-out as this is another feature which i am interested in.
The Tweaks part is also interesting as i understand each Rom has its little Tweaks which are hard to pin point, but that is somewhat what i am hoping to do with these questions.
AOKP rom control seems to have quite a few more options than the cm9 builds, I found the option to change music tracks via volume buttons was a really nice touch.. I would love a option for a LED torch as well but i dont think that feature is working in either builds.
I thought Humberos got HDMI Out working for CM9.
Sent from my GT-P1000 using xda app-developers app
Tv out is working on Cm9, but sound is not working through the RCA cable.
Sent from my GT-P1000 using Tapatalk 2
Thanks for replies ; It would seem Cm9 is offering secondary features such as
USB hosting & TV out and possibly a few others which are yet to be mentioned.
I am unaware if AOKP currently supports these secondary/hardware related features. I have read that the kernels were merged but am unaware if the merging has brought these features though, It would be awesome if they have been.
Regarding TV-Out on Cm9 ~ If it is working in Cm9 i assume you mean only the HDMI cable is working with sound and the RCA with video and no sound?
More like it works completely using HDMI pin out.
As for RCA cable only video.
Something like that.
Sent from my GT-P1000 using xda app-developers app
I take it the TV-Out feature is untested on AOKP but confirmed on Cm9 with pin out cable, As well as the Usb host.
These seem like 2 solid features cm9 is offering that AOKP currently isn't, hopefully the TV-out will be implemented into in the near coming future. I will update the status on USB hosting hopefully later this week.
Stimpz0r just announced AOKP #40
Tv-out working.
Sent from my GT-P1000 using xda app-developers app
That truly is awesome news Seems like all the features are being integrated Between the two.. thanks for the update..i will now reconsider getting a HDMI cable along with a USB converter.
UPDATE ~ ON USB HOSTING
Usb hosting is somewhat currently working on AOKP.
I currently have my Tab wired up to a Usb hub, where i can view my 8gb memory stick and mount it.. I am also able to pick up my Cannon camera, however i cannot mount it.
Keyboard and mouse are not detected, though i think to get this working i need to try a different wiring method.
Question ~ I would like to know if anyone has got a mouse and keyboard working on a Hub ? on AOKP or CM9 as i think its the hub which causes a issue in this area, meaning as i currently stand i need to get a different configured Y cable.
USB Host Capability P1000
Awology said:
UPDATE ~ ON USB HOSTING
Usb hosting is somewhat currently working on AOKP.
I currently have my Tab wired up to a Usb hub, where i can view my 8gb memory stick and mount it.. I am also able to pick up my Cannon camera, however i cannot mount it.
Keyboard and mouse are not detected, though i think to get this working i need to try a different wiring method.
Question ~ I would like to know if anyone has got a mouse and keyboard working on a Hub ? on AOKP or CM9 as i think its the hub which causes a issue in this area, meaning as i currently stand i need to get a different configured Y cable.
Click to expand...
Click to collapse
Hi sir, kindly share which thread for the Y cable configuration, ROM and kernel. I cant seem to find these threads.
Thank you
I wanted to put this in the development forum...but anyway. I have never until this morning messed with Safestrap or loading a custom ROM. I finally bit the bullet and loaded Safestrap 2.1 and the KEXEC Alpha 4 on my Droid 3 this morning. Very impressive work you guys do, and I can't wait to see a finished product!
mhelm23 said:
I wanted to put this in the development forum...but anyway. I have never until this morning messed with Safestrap or loading a custom ROM. I finally bit the bullet and loaded Safestrap 2.1 and the KEXEC Alpha 4 on my Droid 3 this morning. Very impressive work you guys do, and I can't wait to see a finished product!
Click to expand...
Click to collapse
Lots of people here do amazing work, good to hear another D3 happy with the progress. Do keep in mind... there's never a 'finished product' it's ALWAYS being updated with better enhancements and whatnot. It's a finished product when it's hardware bricked.
Glad to hear you jumped into the wonderful world of roms though! I hope you enjoy your stay for many years to come.
Major Battery Drain & Gmail Non-Functional
Wish I could post these bugs in the development forum for the Kexec ROM. Should this info be passed along to Hashcode or anyone? If so, what's the best way since I can't respond in the proper thread?
The first day and a half of using this ROM everything was great. All apps worked, the device ran cool and no bugs.
This morning my battery has drained about 80% in an hour. Not sure what caused that.
Other Notes:
Yesterday the Gmail app failed and will no longer work. "Sorry, Gmail has failed...." The screen flashes something so quick I can't read it and returns me back to the Home Screen. I have resorted to using a AquaMail for now. Seems like after the Gmail app failed when I reboot the device now I get some message about Droid is updating. This happens right after the Cynogen screen and before the Home screen loads.
Trivial - System Settings: Battery Usage time is always off.
EDIT: So after going back through the 42 pages on the thread....I am going to reduce the overclock on mine and see if that helps. I also didn't catch that I needed to recalibrate the battery. I will do that after the battery is back up to 100%.
I also can't post in the development forum (yet - one more post after this and I can so that's part of the reason for posting this ) and wanted to add one item to the above:
The car dock USB audio doesn't work. I wouldn't call this a bug so much as a not yet implemented feature. I assume it could be related to the whole audio routing involving missing phone speaker audio with Bluetooth on, etc.
I've been running alpha 4 for nearly a week and it's been surprisingly solid. A few reboots and freezes, but far less than I expected going in.
another user who can't post in development forum.
due to camera issues, shorter battery and random boots i have switched back to CM9 from the Kexec Alpha 4.
hoping to switch back to CM9 Kexec once it get more stable and/or out of alpha
The very bad stability with the stock rom is what lead me to look to alternatives about a year ago and I haven't looked away from Hash ever since! All in all, the instability in Kexec #4 is a little frustrating, but I can deal with it since I know it's not "ready for prime time" like the stock rom claimed to be!
The new jb preview from hash is quite impressive, although not usable at the moment.
Sent from my XT862 using xda premium
Jb is much smoother on my d3 as well. Ics has a force close issue on mine.
Sent from my DROID3 using Tapatalk
Im thinking about trying it out latter. Wish me luck
Anyone done a factory reset on their JB Droid 3 and been unable to pickup service?
For some reason I'm unable to pickup Verizon as my carrier and establish phone service after a factory reset. The phone just sits here and "Searching for Service"..
I'm thinking I just need to re-flash the latest KEXEC JB build and see if that brings me back to service functionality.
I just did a re-flash, and I'm still sittin on the "Searching for Service" screen.
--McBean
(Likewise dev-forum impaired!)
To my knowledge, there are no working "jb" builds for the d3. If you are referring to hashcode's cm10 preview, well the answer is in the title, its just a preview. I suggest wiping and flashing non kexec cm9 or aokp till development on the kexec process furthers.
Sent from my XT862 using xda premium
Hash is working on data for Jellybean. Until then nothing will work.
I must have done something weird my first time through as phone and normal services worked under the preview. (Not trying to ***** or start a flame out of it... just stating a reality.)
I'll go take a crack at CM9 then and see what's up. Maybe I can get Service back up under that and then flash to CM10 to restore phone service....
--McBean
McBeanTIO said:
I must have done something weird my first time through as phone and normal services worked under the preview. (Not trying to ***** or start a flame out of it... just stating a reality.)
I'll go take a crack at CM9 then and see what's up. Maybe I can get Service back up under that and then flash to CM10 to restore phone service....
--McBean
Click to expand...
Click to collapse
Not sure what you managed to do, but if you could replicate it, that might be useful to Hash (and the rest of us). Even on the "it might work" release today, I am not getting anything.
Devil's in the details
keithk23 said:
Not sure what you managed to do, but if you could replicate it, that might be useful to Hash (and the rest of us). Even on the "it might work" release today, I am not getting anything.
Click to expand...
Click to collapse
I'll see what I can do. I'll have go figure out how to go completely stock again and start from the ground up. That's where all the magic began for me. And I'll need to find the ROM from 2-3 weeks ago when I first got the guts to flash CM onto my phone. I don't know what in the hell possessed me to do a factory reset other than sheer stupidity. Totally jinxed a good thing.
--McBean
Anyone knows if someone take the initiative to develop something for our unlucky device?
Is that possible at least?
Im no real dev but I was bored last night and started messing around with it, got the android part to compile, havent flashed it or anything though
But in its current state, ubuntu phone doesnt seem like anything more then, 'hey this is cool, now back to a rom that has some actual support'
Its a dev preview with little to nothing working heh
To answer your question though, on paper, yes, it looks like it would work, just with all the same problems as current cm10.1 that are caused by kexec
That was exaustive man thanks!
Damn kexec is both a great good and a great bad for this device!
Hashcode, you're our only hope!
Looks like Hashcode is planning to port it eventually:
https://wiki.ubuntu.com/Touch/Devices#Work_in_progress
I wasn't really expecting anyone to port this for our Droid 3 considering the low amount of RAM we have when compared to newer devices.
Yeah, Hash is currently working on it (check his Twitter, there are links to the XDA thread. I'd link, but stupid 10 post limit here...), but it's as good as it's gonna get for a little bit.
As he says:
WHAT WORKS:
Display
Touch screen
Wifi
Audio
Click to expand...
Click to collapse
I'm running a D3 on Verizon with SafeStrap 3.05 and the 03-01 Phablet patch, and it CAN make phone calls (so CDMA and GSM both apparently work).
He isn't kidding about needing more swap space, or it being a power drain; a lot of issues with Ubuntu Touch boil down to how much of a WIP it is by the Ubuntu devs.
As soon as I have this 10 post criteria met, I'll post a bit more of an updated "how to install" on his dev thread.
I'm a noob but I finally got something flashed to my D3. I loaded the Nightly CM10.1 Solana from 03-10 and the 03-01 Gapps using TWRP Safestrap 3.05. The phone largely works, the biggest issue I have is that my Bluetooth keyboard doesn't work with it. It pairs but it doesn't send any keystrokes. I know the camera doesn't work, but my D3 pictures never turned out anyway. Operation seems smooth but a little bit on the slow side (which doesn't surprise me).
I haven't done any customizing or optimizing, so perhaps it could be made to run faster by tweaking on it.
I just wanted to try out the phone with larger font size so I don't have to hold the phone so far away. That's why I loaded Jelly Bean on it. The ICS version I installed couldn't make and receive calls, and same thing on the CM10.1 nightly from 03-09. I'm not saying I installed those right or anything. My point is, in my opinion, the March 10 Solana Nightly has left me with a phone that I'm having fun with, and I'm happy to leave it this way for awhile maybe. Perhaps it is not a good idea to load the nightly builds on your machine when you're a noob like me, but hey it looks to me like I picked a good day.
Okay, I wanted to take a moment to talk about the development for our device.
Recently CM decided to no longer support Tegra 2 devices as they are starting to get dated. So basically that boils down to the fact that the CM10.1 will be the last one for our device that I do.
Currently I'm trying to jump start the process of putting out our updated kernel from 2.6.36.4 -> 3.1. This will hopefully put our device at a point where everything should work.
DerArtem is the lead developer on the kernel, but has been busy because he just got married and works a full time job, which puts a damper on his time (which is understandable).
I am putting in an 1-2 hours every morning on this, trying to fix those bugs and was just tipped on a possible way to minimize the overload of the log with the USB error. This will be a hold off till we get the kernel done as these issues should go away after the update.
I am sad to see this tablet come to an end (though not yet). We all have to admit that its time we all start moving on. I am going to push to get these last bit done and call it quits. This can take anywhere from 2-5 months to finish up, maybe a bit longer and then our device will be done.
I have had an amazing time learning about Android under DJ_Steve and DerArtem, and thank them for taking the time to teach me.
I thank you what you done so far and in the future. Can blame you one bit for your decisions.
I think setting an "end game" is respectable, and is a good goal. The kernel work is the key to smoothing things over on what has been wonderful development thus far.
The fact you've taken us this far sir is very commendable and you and the crew deserve many thanks. For your time and efforts, you have my gratitude, and my tablet serves as a hobby rather than a shelved device.
4.2.x has been flawed since release by Google, and with the way android has evolved, future versions will undoubtedly require more current hardware and OEM support. The latest tablet releases have as much computing power as a 2 year old laptop! Thanks to you, we've managed to play with JB, and I look forward to what comes before a final release.:thumbup:
Sent from my Galaxy Nexus using xda premium
Wow, I hate doing this, but I may have to close up shop on all this. Severe lack of any real work is getting done as I am looking for jobs and trying to have some game time as well.
The time to do this isn't worth it. I may ask for payments for my next ROM ($1 per download). Seriously, I hate doing it but this just isn't worth it anymore. Currently working on a AOKP release, to see if this may resolve any bugs I am having.
Hi giveen,
first of all thank you for all the time you spent on our old device. I already donated you some time ago and always had an eye on your progesses. I really understand your decision to ask for some payment for all the work and that is absolutely ok for me.
I use my DS7 (wifi only) on a daily base to check my mails, surf the net and stream some TV and video from my HTPC. Until now I use a HC 3.2 mod (514 mod by dreamer) together with V6 Supercharger script and am so far quite ok with that. So far I see no need to buy me a new tablet as long as the DS7 fits my few needs
But before I collect all my courage and update my DS7 in the near future to your CM10 build I want to ask a few things:
1. Is your build already stable and usable enough for the things I do with my device?
2. Any news from DerArtem about the kernel work? Will there be a new kernel for our device in the future?
THX,
Michael
Montezuma10 said:
Hi giveen,
first of all thank you for all the time you spent on our old device. I already donated you some time ago and always had an eye on your progesses. I really understand your decision to ask for some payment for all the work and that is absolutely ok for me.
I use my DS7 (wifi only) on a daily base to check my mails, surf the net and stream some TV and video from my HTPC. Until now I use a HC 3.2 mod (514 mod by dreamer) together with V6 Supercharger script and am so far quite ok with that. So far I see no need to buy me a new tablet as long as the DS7 fits my few needs
But before I collect all my courage and update my DS7 in the near future to your CM10 build I want to ask a few things:
1. Is your build already stable and usable enough for the things I do with my device?
2. Any news from DerArtem about the kernel work? Will there be a new kernel for our device in the future?
THX,
Michael
Click to expand...
Click to collapse
If its from your HTPC, I honestly don't know as I have never tried it before. This latest build is much more stable, though it still has the gmail keyboard crash that I am tracking down. If you are happy with what you have, don't do anything. I would hate for you to make a purchase and not be happy.
I haven't heard from DerArtem in several weeks because he is in another country (Russia) doing a job. (He lives in Germany). To be honest, I don't think a new kernel is going to happen and I'm really upset by it.
giveen said:
If its from your HTPC, I honestly don't know as I have never tried it before. This latest build is much more stable, though it still has the gmail keyboard crash that I am tracking down. If you are happy with what you have, don't do anything. I would hate for you to make a purchase and not be happy.
I haven't heard from DerArtem in several weeks because he is in another country (Russia) doing a job. (He lives in Germany). To be honest, I don't think a new kernel is going to happen and I'm really upset by it.
Click to expand...
Click to collapse
One issue I see here is that when you start charging, a person paying for it like a app from the Play Store, they expect things to work. This "might" cause you to spend more time than you have been on it. Just my $0.02!
Didn't somebody donate an unused DS7 for DerArtem for this kernel project?
wptski said:
One issue I see here is that when you start charging, a person paying for it like a app from the Play Store, they expect things to work. This "might" cause you to spend more time than you have been on it. Just my $0.02!
Didn't somebody donate an unused DS7 for DerArtem for this kernel project?
Click to expand...
Click to collapse
They can contact me if they are having an issue. I appreciate the concern though.
Yes, someone did give their DS7 to him.
giveen said:
They can contact me if they are having an issue. I appreciate the concern though.
Yes, someone did give their DS7 to him.
Click to expand...
Click to collapse
I'll be downloading it later after some usage and a charge.
I'm working on sensors now. The old sensor drivers we used were for something we dont even have. I found the correct Android drivers but they are for qualcomm devices, so I need to modify them to work.
giveen said:
I'm working on sensors now. The old sensor drivers we used were for something we dont even have. I found the correct Android drivers but they are for qualcomm devices, so I need to modify them to work.
Click to expand...
Click to collapse
after several attempts and research I was still not the sound from my headphones with android android 2 and 3 sound going normally but not with 4.2.1 and 4.2.2.