Related
Is Nook Color in Limbo, or are we at the cusp of something new?
I hope development for the Nook Color has not stagnated. Are we waiting for the new kernel or is there just nothing new on the horizon?
I am just wondering because I have been watching and waiting and it appears development has slowed up for the time being. Not implying anything, just looking to see if something new and wonderful is on the horizon???
I was so looking forward to Honeycomb and it seems Google has pulled the rug out from under us in some back room deal.
Hopeful
migrax
What are you talking about? In limbo? Bluetooth, recent video fixes, new overclocked kernels, work on the next coming edition of kernel to prevent SOD. Man, you must be out of the loop or really impatient.
The Release Candidate of CM7 came out recently. That means a final release is eminent. That final release should include all these awesome tablet tweaks:
http://forum.xda-developers.com/showthread.php?t=1002000
I don't know why you say development is slowing down. I have been flashing a new ROM everyday thanks to mad-murdock!
Im sorry, but what ARE you talking about? In the last month, both hardware accelleration for video and bluetooth were turned on. CM7 has reached release candidate stage, and our devs have said that work is progressing on both a newer kernel version, as well as fixes to the few remaining bugs. Maybe you should actually read some of those nifty development threads around here...
If i am coming off as rude... perhaps that is the intent. There are so many needless threads like this, where some reading and critcal thinking could answer alot of questions. I mean.. developent stopped? As it is, things are ramping up, and a quick read of the forum would show that. Add in the constant misleading talk about what the nook can and can't do, and it is rather frustrating. So yeah, I am venting, but i think it is well deserved.
On the contrary, I think that things are happening real fast. CM7 is heading for a stable release, Mad Murdock's tablet tweaks are a real innovation, as are brianf21's froyo status bar improvements, and real progress is being made in the kernel area - blue tooth, hardware acceleration, etc.
What more can we ask for?
only HC is at a minor hump, the rest are busy, and b&n update is dropping soon. you crazy!
had to chime in to see what the op is smoking...
cm7: hardware video acceleration, tablet tweaks, bluetooth, kernel mods.
froyo: status bar tweaks, 'nookie-comb' looks nice, new official rom coming soon
honeycomb: who cares. google screwed that one up so we wait for IC.
Honestly, right now I'm in limbo about WHICH custom, daily updated, feature rich build to use !
Rooted Stock is good enough for what I do, but then a few games didn't work... so i went to froyo... then tried CM7... then a custom froyo, then another CM7... (and a few hardlocks and flash to stocks in between)..
At this point i just want a "1.0" release of CM7, or for HC to become available... although i'm sure the weeks following HC will be daily build after daily build.
p.s. kinda jealous about the $300 Tegra2 tablet floating around.
Divine_Madcat said:
Im sorry, but what ARE you talking about? In the last month, both hardware accelleration for video and bluetooth were turned on. CM7 has reached release candidate stage, and our devs have said that work is progressing on both a newer kernel version, as well as fixes to the few remaining bugs. Maybe you should actually read some of those nifty development threads around here...
If i am coming off as rude... perhaps that is the intent. There are so many needless threads like this, where some reading and critcal thinking could answer alot of questions. I mean.. developent stopped? As it is, things are ramping up, and a quick read of the forum would show that. Add in the constant misleading talk about what the nook can and can't do, and it is rather frustrating. So yeah, I am venting, but i think it is well deserved.
Click to expand...
Click to collapse
What madcat said
Sent via Cyanogenmod7 Encore RC4 n.35/Tapatalk Pro
roflmao
You want limbo?
My new Droid 2 Global has just one rom which works with global sim capability- flashed it shortly after I got it and no updates since.
Another crew did get D2 roms working on the D2G but no sim card use.
Nothing for months now...
My original DROID has more development work going on than THAT!
The NC has been fairly exciting as far as dev work since Christmas and the last month has been incredible...
I even saw a post fairly recently that leads me to think some folks are working on USB host.... Crossing my fingers on that one.
The last two weeks we have even had a guy working on tweaks for tablets that pretty much makes Honeycomb's issues irrelevant as far as I am concerned.
I'd say that is pretty good.
Sorry, not the intended result.
I guess I am waiting for BN to come out with Android 2.2, I wasn't denegrating all the hard work that has gone on here. A couple of developments have kinda skewed my perceptions, one of which is Honeycomb source being yanked, and the other is of course the expected update from BN not materializing yet... I guess I am getting a little impatient. Sorry for the misunderstanding.
I am using Nookie Froyo at the moment and it is working, however I really liked Stock 1.1.0. but with the NC using Android 2.1 I can't do some things I'd like to do. It just seems to me that BN is dragging their feet. Hence my concerns.
As I understood your original post you are waiting for the official 2.2, not a developer build.
The last rumor that I heard (from these forums) was that it was to go out this month. (but that was a rumor)
Not really sure why people are flaming the OP so hard. Besides CM7 nook color development has practically stopped dead in its tracks. HC is stuck, froyo has been dead for a while.
So i can see how it seems that way unless you watch CM7 development it does look very dead. CM7 is usable enough that froyo is not really relevant and with googles decision to not open source HC means its pretty much dead in the water.
Actually with Tablet Tweaks, CM7 is still seeing updates almost every day. And there's I believe an Experimental Kernel hiding in the CM7 User Thread which seems to have cleaned up the Battery Life on CM7.
As far as the official 2.2 update... Who needs it when you've got CM7? I mean, even if it does come out and we nooter it, it's still not going to do everything that CM7's custom rom can.
HoneyComb, yeah it sucks that it's not coming out right away. And I was pretty upset myself, but with tablets coming out (with similar prices to the nook) that have HC already... I can wait.
notinterested said:
Not really sure why people are flaming the OP so hard. Besides CM7 nook color development has practically stopped dead in its tracks. HC is stuck, froyo has been dead for a while.
So i can see how it seems that way unless you watch CM7 development it does look very dead. CM7 is usable enough that froyo is not really relevant and with googles decision to not open source HC means its pretty much dead in the water.
Click to expand...
Click to collapse
Why waste any more time (right now) on anything BUT CM7? I mean, yes, Froyo and Eclair are dead in the water, but that is good; it just means all the devs are working on the best system we have. When HC source drops, i expect most work on CM7 to dry up, and again move to the better OS.
So yes, dev is on one OS right now, but my oh my, what sweet dev it is. If you call that stagnation, you are crazy..
I'm eager for the bn update just because I like to actually us my nook as an ereader rather than just a tablet. I'm a big fan of the mags and the kid books. Besides, I get my cm7 fix on my dinc.
Sent from my ADR6300 using Tapatalk
Gin1212 said:
Actually with Tablet Tweaks, CM7 is still seeing updates almost every day. And there's I believe an Experimental Kernel hiding in the CM7 User Thread which seems to have cleaned up the Battery Life on CM7.
As far as the official 2.2 update... Who needs it when you've got CM7? I mean, even if it does come out and we nooter it, it's still not going to do everything that CM7's custom rom can.
HoneyComb, yeah it sucks that it's not coming out right away. And I was pretty upset myself, but with tablets coming out (with similar prices to the nook) that have HC already... I can wait.
Click to expand...
Click to collapse
if you know of such a kernel can you link to it?
Also if stock goes to 2.2 and gives us all ability to play flash and the extr speed improvements of a JIT compiler ad can then be nootered and overclocked, why would one need CM7? This way you also get the ui from B&N which includes built in back and menu buttons. It also includes the full B&N experience for reading magazines subscriptions books......You los that on custom Roms.
So while I laud the Devs work, getting nook color to froyo might make much of their work unnecessary, unless it gives them a better platform to make the NC even better.
Unless the stock update brings bluetooth, CM7 will always be better. Sure, i guess there are some people that want the ereader functionality, but there are those the enjoy better hardware functionality.
Not to mention, i guess i am one of few, but i really hated B&N's framework modifications, and really enjoy a stock Android UI..
Divine_Madcat said:
Unless the stock update brings bluetooth, CM7 will always be better. Sure, i guess there are some people that want the ereader functionality, but there are those the enjoy better hardware functionality.
Not to mention, i guess i am one of few, but i really hated B&N's framework modifications, and really enjoy a stock Android UI..
Click to expand...
Click to collapse
I really hope someone manages to port over the slick reader app from stock to CM7.
I like reading on my nook but not at the cost of such horrible performance in everything else.
Divine_Madcat said:
Unless the stock update brings bluetooth, CM7 will always be better. Sure, i guess there are some people that want the ereader functionality, but there are those the enjoy better hardware functionality.
Not to mention, i guess i am one of few, but i really hated B&N's framework modifications, and really enjoy a stock Android UI..
Click to expand...
Click to collapse
Bluetooth works awful at best.
Regular headset doesn't work and range is a foot.
So far most people have keyboard trouble. Seems ext. bluettoh gps seems to be the best bet. So for me a stock rom with all the current missing goodies fixed with nooter and o/c?
I'd be happy.
Outside of bluetooth, if you had fully supported 2.2 on your device so hardware accel video and flash worked perfectly and yet you still had the B&N experience when you wanted it for free instore reading and subscriptions .....what else would you really want?
No, it's not out yet-- but I do have it booting, and with working touchscreen support
Video Link: http://www.youtube.com/watch?v=hnRlyMZzdT0
New video:: http://www.youtube.com/watch?v=2d4pZXyayts
That's about it right now.
Things left:
Mobile Voice
3G Data
4G Data / Voice
Audio
Front Camera
Back Camera
GPS
Bluetooth
Wifi
DSP support for video encode/decode
Vibrate/Notification LED
As I get things working, I'll update this list.
My first priority is wifi, then mobile voice, then 3g data, then vibrate/notification LED.
After that, I'll get GPS working (not hard) then rear camera.
Things that'll probably not happen in CM7 for a while:
Front camera
4G Voice
4G Data
Anything to do with 4G will be VERY tough, since I don't have LG's kernel sources, and I'm no RIL reverse engineer... Any help in this matter is appreciated!
You are the man!
Anxiously awaiting!
Sent from my VS910 4G using XDA Premium App
Uh oh....deciding between 4G and CM7 is going to be rough.
Good work dasgewürfelte (thecubed in German haha)...thanks for everything
Anytime you need a tester Cubed, just let me know. My city is scheduled to get 4G this Thursday so I should be able to test that for you too, soon.
thecubed said:
No, it's not out yet-- but I do have it booting, and with working touchscreen support
That's about it right now.
Things left:
Mobile Voice
3G Data
4G Data / Voice
Audio
Front Camera
Back Camera
GPS
Bluetooth
Wifi
DSP support for video encode/decode
Vibrate/Notification LED
As I get things working, I'll update this list.
My first priority is wifi, then mobile voice, then 3g data, then vibrate/notification LED.
After that, I'll get GPS working (not hard) then rear camera.
Things that'll probably not happen in CM7 for a while:
Front camera
4G Voice
4G Data
Anything to do with 4G will be VERY tough, since I don't have LG's kernel sources, and I'm no RIL reverse engineer... Any help in this matter is appreciated!
Click to expand...
Click to collapse
So, does the release of the kernel change your thoughts on 4G? What about the issues with 3G data lag? Not pressing, just curious. I know with the release of the kernel you aren't going to have a lot of time on your hands to get sidetracked
majorpay said:
So, does the release of the kernel change your thoughts on 4G? What about the issues with 3G data lag? Not pressing, just curious. I know with the release of the kernel you aren't going to have a lot of time on your hands to get sidetracked
Click to expand...
Click to collapse
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
nick99wj said:
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
Click to expand...
Click to collapse
so did I miss LG releasing the kernal source.. or did we get it another way..?
**edit**
so just a few more clicks and I wouldn't have asked that question.. I am game try whatever you have available!
holy crap i just nutted.
mursepaolo said:
holy crap i just nutted.
Click to expand...
Click to collapse
This.
Awesome!
Hey Thecubed, is there a particular reason you went with ADW Launcher as the... er... Launcher? What would keep you from using HeLauncher as the default? Any chance of getting a Samsung style launcher and icons?
And I think its almost been a week, and the phone is still running smooth. I did the stat bar cleaner, thanks MT. And the battery life is stellar.\
Thanks again. I am working overtime so I can get you a sizeable dony.
nick99wj said:
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
Click to expand...
Click to collapse
Very good to hear
Fixing 3G lag will be sooo nice.
markapowell said:
Hey Thecubed, is there a particular reason you went with ADW Launcher as the... er... Launcher? What would keep you from using HeLauncher as the default? Any chance of getting a Samsung style launcher and icons?
And I think its almost been a week, and the phone is still running smooth. I did the stat bar cleaner, thanks MT. And the battery life is stellar.\
Thanks again. I am working overtime so I can get you a sizeable dony.
Click to expand...
Click to collapse
The kingpins of CM7 decided to use ADW.Launcher since its dev open-sourced the launcher. It makes customizations very easy to make. You can always pull it out with TB once you've got your launcher of choice up and running.
Cubed - I was so excited when I saw this thread pop up the other day. I have my Revolution coming in the mail hopefully sometime this afternoon, and I will definitely be on the IRC once it gets in. I won it in a contest, so I won't feel bad if I end up bricking it, especially because I have an upgrade in September.
And as soon as my finances allow, I will most certainly be submitting a donation. Thank you for your support!
I will say though, I just switched to this Fascinate I'm using currently a month ago, and our CM7 code finally got merged upstream, so I'm definitely gonna miss fully-functional GB, but I'm sure you'll have it running smoothly in no time!
Totally double-posting here, but I have my phone activated and running. 4G is friggin' SWEET!
Anywho, if you need any logcats or anything at all that's within my practical ability (I'm willing to flash just about anything since I didn't pay a dime for this phone, and can do any number of logcats/dmesg you need), just let me know. I'll pop onto the IRC from time to time just to check, but if you ever need someone in a hot moment, direct message me and I'll be glad help!
any chance we will see a alpha release to test out for you? would be ballin!
RegnierD said:
The kingpins of CM7 decided to use ADW.Launcher since its dev open-sourced the launcher. It makes customizations very easy to make. You can always pull it out with TB once you've got your launcher of choice up and running.
Cubed - I was so excited when I saw this thread pop up the other day. I have my Revolution coming in the mail hopefully sometime this afternoon, and I will definitely be on the IRC once it gets in. I won it in a contest, so I won't feel bad if I end up bricking it, especially because I have an upgrade in September.
And as soon as my finances allow, I will most certainly be submitting a donation. Thank you for your support!
I will say though, I just switched to this Fascinate I'm using currently a month ago, and our CM7 code finally got merged upstream, so I'm definitely gonna miss fully-functional GB, but I'm sure you'll have it running smoothly in no time!
Click to expand...
Click to collapse
I suspect another reason ADW was incorporated is because it's one of the only open source launchers. That comes without the possible legal ramifications of packaging someone elses work in your creation.
I also wouldn't mind being a testcase, if there is a use for another one.
Right now I'm reworking all the init scripts that LG has written and consolidating them into the cyanogenmod style of a single "init.bryce.rc" initscript.
As I'm doing that, I'm looking for referenced binaries and crossreferencing that list with the list of binaries that cyanogenmod builds (to see what binaries are LG-specific and what are stock Android). After I find the binaries, I am hexdumping each one to find out which libraries they import, and adding those to the cyanogenmod build directory also.
LG really really really needs to write better scripts. Their init process is all over the map, and half of the stuff in the init script isn't even for our device! It references dev platforms and other stuff that really should be trimmed before releasing to the public.
Anyway, in regards to testers, I actually have a device now (my very own device! but no service haha) so I'm able to do testing on my own for intermediate builds. When I release a milestone build (I'd consider wifi and 3d accelerator a milestone build) I'll release it via PM.
I don't want to make the test builds public because I worry that it'd cause problems with people not reading the "WARNING! THIS DOESNT WORK RIGHT!" and coming back saying they bricked their phones.
However, as soon as I have something to show, I'll make a video
Woohoo! That's exciting. I miss stable CM7 so much. It was flawlesson my trusty Incredible, just getting to stable on the Fascinate, and now being started from scratch here.
If you ever need any help, Cubed, I'm game. I would have no qualms with it. I'm available at nearly any moment and always have a computer nearby for logcats and d/kmesg dumps. Plus, I have full services 3/4G and wifi all around me at almost all times.
I'd love to be able to help the community out, even if it's only by flashing and giving error logs.
I noticed when peeking around in the system that things were a little messy too. The build.prop is kinda iffy and their lack of an organized boot animation is annoying. It's like being neat wasn't a concern at all. Seems like they were in a hurry.
RegnierD said:
Woohoo! That's exciting. I miss stable CM7 so much. It was flawlesson my trusty Incredible, just getting to stable on the Fascinate, and now being started from scratch here.
If you ever need any help, Cubed, I'm game. I would have no qualms with it. I'm available at nearly any moment and always have a computer nearby for logcats and d/kmesg dumps. Plus, I have full services 3/4G and wifi all around me at almost all times.
I'd love to be able to help the community out, even if it's only by flashing and giving error logs.
I noticed when peeking around in the system that things were a little messy too. The build.prop is kinda iffy and their lack of an organized boot animation is annoying. It's like being neat wasn't a concern at all. Seems like they were in a hurry.
Click to expand...
Click to collapse
I will need people to test the 3G/4G service once I get the radios initialized, since I only have the phone and no service
Right now I'm still sorting through the binaries and libraries trying to get at a bare minimum wifi and 3d acceleration working.
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
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.
Head over to the main G4 development page if you are interested in this for the H811/H815.
http://forum.xda-developers.com/g4/development/h811-h815-blisspop-cyanogenmod-12-1-t3185593
There's still a long way to go. Most things are still broken and new builds will generally break things on a regular basis. Just be aware before heading over. The post doesn't need more Posts saying goodbye this/that isn't working, it's still very much a WIP.
Sent from my LG-H815 using Tapatalk
IIIIkoolaidIIII said:
There's still a long way to go. Most things are still broken and new builds will generally break things on a regular basis. Just be aware before heading over. The post doesn't need more Posts saying goodbye this/that isn't working, it's still very much a WIP.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
True, and the OP doesn't have the most recent build where most stuff is actually working. I'm running the 10/15 build (page 76-78...somewhere in there, posted by codeworkx) and most of my audio is working. Haven't tried bluetooth, but I rarely use it, apparently voice calls have an echo, but I never call anyone, either. The only thing I really use that has an issue is the camera that delays on opening, but I'm sure that'll be worked out shortly. As soon as codeworkx got to work on it, it's honestly been pretty stable for a WIP, but I think I have a higher tolerance for broken builds and features, having been a crackflasher for 7 years now. I'm just happy to be back on AOSP/CM at this point with this phone.
schreckles said:
True, and the OP doesn't have the most recent build where most stuff is actually working. I'm running the 10/15 build (page 76-78...somewhere in there, posted by codeworkx) and most of my audio is working. Haven't tried bluetooth, but I rarely use it, apparently voice calls have an echo, but I never call anyone, either. The only thing I really use that has an issue is the camera that delays on opening, but I'm sure that'll be worked out shortly. As soon as codeworkx got to work on it, it's honestly been pretty stable for a WIP, but I think I have a higher tolerance for broken builds and features, having been a crackflasher for 7 years now. I'm just happy to be back on AOSP/CM at this point with this phone.
Click to expand...
Click to collapse
I hope nobody thought I was saying it is ready for prime time! Just a heads up. I have not installed it yet as I will wait for a more highly functioning build, but I also know there is a thirst for development here, so I wanted to share the good news!!
Honestly, if you were to try the 10/15 build, you'd be surprised at how "ready from prime time" it actually is. I've been using it as my DD for the last 2 days and it's actually been pretty nice. Couple small things here and there, but the only thing that's affected me at all so far was the camera delay. Now that there's at least a dev or two that seems like they know what they're doing, I'm hoping development for AOSP/CM stuff starts picking up. The little time that codeworkx has put in so far has been looking extremely promising. (Not to take away from the OP on that, but code made it so that I can actually use it as a DD with sound.)
schreckles said:
Honestly, if you were to try the 10/15 build, you'd be surprised at how "ready from prime time" it actually is. I've been using it as my DD for the last 2 days and it's actually been pretty nice. Couple small things here and there, but the only thing that's affected me at all so far was the camera delay. Now that there's at least a dev or two that seems like they know what they're doing, I'm hoping development for AOSP/CM stuff starts picking up. The little time that codeworkx has put in so far has been looking extremely promising. (Not to take away from the OP on that, but code made it so that I can actually use it as a DD with sound.)
Click to expand...
Click to collapse
Hmmm, I didn't realize it was that far along. Between the 815 talk there, it has become tough to follow. I may give it a go. I assumed you did a complete wipe before installing? Thanks, @schreckles
EDIT: You don't use bluetooth I see, and I do quite a bit. From what I understand, that doesn't work, so that's a non-starter for me. Guess I'll wait.
ShermCraig said:
Hmmm, I didn't realize it was that far along. Between the 815 talk there, it has become tough to follow. I may give it a go. I assumed you did a complete wipe before installing? Thanks, @schreckles
Click to expand...
Click to collapse
Yup, sure did. Full wipe (especially when switching back and forth between CM/AOSP and stock roms) and then flashed the 10/15 H811 build that codeworkx posted the other day, along with the nano gapps he'd suggested.
Small issues: Your LED will stay lit up blue until you plug the phone in and unplug again. No biggie. No "OK Google" or anything that requires the phone mic for me thus far (ie Google Sound Search.) Camera takes approximately 4 years to open, but it does open, and the shots it produces aren't bad. They aren't as good as stock, but that's typically been the trade-off even since back in my OG Droid days when going from stock to non-stock base. Call audio, bluetooth, and NFC apparently have some issues still, but I rarely use any of those, so meh. Oh, and I get a popup stating "Settings has closed" every so often, but it doesn't affect anything. I'm sure I could find the cause if I was motivated, but I'm sure it'll get worked out soon enough.
...Mostly just stuff I can live without for now that's broken. I've even been using Xposed and some of my favorite modules without any ill effects.
So is it more or less a theme now or what? I know what CM is, but as far as functionality, is it quite a bit faster than stock or what?
Thanks!
I am assuming that this is the only public aosp build for the G4?
maximus20895 said:
So is it more or less a theme now or what? I know what CM is, but as far as functionality, is it quite a bit faster than stock or what?
Thanks!
Click to expand...
Click to collapse
It's a completely different build of Android using different frameworks and whatnot. It's built upon AOSP and tweaked framework to make it CyanogenMod. I'm not sure if the one I am using currently is the one in this thread but so far it's been pretty smooth. There are definitely some issues but it's a lot further along than I though it would be. Kudos to those guys!
EDIT: That is the same build I am using (in case anyone is wondering).