Related
Got jellybean booting just now.
Proof pics: https://plus.google.com/u/0/102710594547223731659/posts/HKkDrEQveZt
texasice said:
Got jellybean booting just now.
Proof pics: https://plus.google.com/u/0/102710594547223731659/posts/HKkDrEQveZt
Click to expand...
Click to collapse
Link doesn't seem to want to work for me, but great work!
rbaruch said:
Link doesn't seem to want to work for me, but great work!
Click to expand...
Click to collapse
if its not working just click my profile and click the g+ link (i dont know how to embed pictures)
That is awesome!!!! Thank you so much texasice!!!!!!
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Will have my money ready for donation when this completed!
Sent from my SGH-T959 using Tapatalk 2
Join the club Nice work though
Amazing
Hope all feature work well soon
Might not have too wait long for an official release.. according to http://tips4droid.com/list-of-att-v...-phones-that-will-get-android-4-1-jelly-bean/ we're going to see JB sometime in October
ericdjobs said:
Might not have too wait long for an official release.. according to http://tips4droid.com/list-of-att-v...-phones-that-will-get-android-4-1-jelly-bean/ we're going to see JB sometime in October
Click to expand...
Click to collapse
This would be great, if they do announce it and keep their word.
ok when is it going to be fully functional, can you personally PM me with EVERY step in the process since I am so important and need to have my hand held every step of the way.
ETA ETA ETA
just getting that out of the way so everyone else can shut up and let you work
ericdjobs said:
Might not have too wait long for an official release.. according to http://tips4droid.com/list-of-att-v...-phones-that-will-get-android-4-1-jelly-bean/ we're going to see JB sometime in October
Click to expand...
Click to collapse
It really shouldnt take them very long. google did a great job with jellybean. making it extremely compatible with all kinds of hardware. for ics we had to pull ~50 commits to frameworks from qcom to get display working. on jellybean...zero. it just works. no hacks required. google really outdid themselves this time. (also cudos to caf for releasing the display drivers same day!!) just took me 3 days to realize that yea they do work lol.
So in theory it shouldnt be too hard to get jellybean up and running on devices that have aosp 4.0. Correct?
Sent from my HTC Sensation using xda premium
texasice said:
It really shouldnt take them very long. google did a great job with jellybean. making it extremely compatible with all kinds of hardware. for ics we had to pull ~50 commits to frameworks from qcom to get display working. on jellybean...zero. it just works. no hacks required. google really outdid themselves this time. (also cudos to caf for releasing the display drivers same day!!) just took me 3 days to realize that yea they do work lol.
Click to expand...
Click to collapse
so your saying since google did that, it make it easier to get things working? if so, thats great!
Yea any device that already has ics should be pretty painless for the oem to upgrade to jellybean.
texasice said:
Yea any device that already has ics should be pretty painless for the oem to upgrade to jellybean.
Click to expand...
Click to collapse
Well that's sounds awesome man seriously I am looking for an aosp ROM that will take care of all my needs
Sent from my HTC_Amaze_4G using xda premium
So will we get sense something else or how would that work? Also we on tmobile are waiting for source right, does that mean that we are now looking forward to jb source that is modified with sense?
Sent from my HTC_Amaze_4G using xda premium
fcpelayo said:
So will we get sense something else or how would that work? Also we on tmobile are waiting for source right, does that mean that we are now looking forward to jb source that is modified with sense?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Could be because I think that sense 3.6 is garbage and 40 is way better lighter and more responsive or at lest by me using it it seemed like that. But if they do decide to do that I thing they should bring sense 4.0 to all capable devices
Sent from my HTC_Amaze_4G using xda premium
i think once a fully working jb rom is up and a sense 4 the hard part is gonna be picking new version of sense (i love sense) or new version of android(off line voice typing and google now just way too cool)
I created an "everything jellybean" disscussion sticky thread. Please keep all jellybean discussiin there. Thank you.
Thread closed.
••••••••••••••••••••••••••••••••••••••••••••
" if you choose not to decide, you still have made a choice"~Rush
Sent from my Galaxy Note (i717), using XDA Premium.
It's almost that time! It seems that a 100% bug free version of Cm9 is eminent! I personally cannot wait. Can anyone that knows the status for sure give us that are waiting some updates as they come??? I know there are a few builds but I'm talking about straight cm9!
+#4n|<$
#1 rule of XDA: Don't ask for ETAs.
I would say CM9 is 98% complete. Lots of people are reporting Bluetooth not fully working. Give our awesome devs a hug and let them know you love them.
Just hang around until they get JB going.
Is hw excel working?I don't know..I ran sum of the standard benchmark test and saw huge decrease in speed,,plus it gave Me horrible signal.,and cramps
I haven't run a benchmark on this version, but I was getting in the 6k range on Antutu last version, which is the same as Sense.
And, yes, I'm going to hug Chad with more money.
---------- Post added at 08:13 AM ---------- Previous post was at 08:02 AM ----------
takota6 said:
Is hw excel working?I don't know..I ran sum of the standard benchmark test and saw huge decrease in speed,,plus it gave Me horrible signal.,and cramps
Click to expand...
Click to collapse
Just got 6534 in Antutu, including over 59 fps in both 3D tests. It's testing faster than Sense for me.
GrayTheWolf said:
#1 rule of XDA: Don't ask for ETAs.
I would say CM9 is 98% complete. Lots of people are reporting Bluetooth not fully working. Give our awesome devs a hug and let them know you love them.
Just hang around until they get JB going.
Click to expand...
Click to collapse
Jelly bean will be awesome! And I'm not asking for eta. Just updates as they come along )
Sent from my ADR6425LVW using xda app-developers app
I think you mean "imminent."
It looks like were close. Chad said he has fixed everything 100%, and everything just looks to be ROM specific.
I'm sitting on the edge of my seat waiting for a 100% JB ROM, simply because I think it will be along very soon and I hate wiping / reflashing repeatedly. What's another month after all we've been waiting?
I might cave and go for one of the CM9 ROMs or AOKP if Meadows can get it 100%, mainly because it will be official and not a fork from the ROM source.
Chad is amazing, and if I didn't have a car payment, I would have sent a hefty donation his way. Once I get some financial things settled down, I may send him a couple hundred for all his hard and amazing work.
cpurick said:
I think you mean "imminent."
Click to expand...
Click to collapse
Auto predictions. Never typed that word before and that's what came up when I was half way through the word so I quickly hit it. No biggie
EtherBoo said:
It looks like were close. Chad said he has fixed everything 100%, and everything just looks to be ROM specific.
I'm sitting on the edge of my seat waiting for a 100% JB ROM, simply because I think it will be along very soon and I hate wiping / reflashing repeatedly. What's another month after all we've been waiting?
I might cave and go for one of the CM9 ROMs or AOKP if Meadows can get it 100%, mainly because it will be official and not a fork from the ROM source.
Chad is amazing, and if I didn't have a car payment, I would have sent a hefty donation his way. Once I get some financial things settled down, I may send him a couple hundred for all his hard and amazing work.
Click to expand...
Click to collapse
I don't think 100% JB is as close as we would hope but I am definitely ready to flash a 100% bug free cm9 any day... Just a few more bugs! :/ thank god for devs on here.
I'm just happy we've gone as far as we have in development. A 4G NON Nexus Verizon device with AOSP is good enough for me lol. Not many out there.
HTC Rezound
takota6 said:
Is hw excel working?I don't know..I ran sum of the standard benchmark test and saw huge decrease in speed,,plus it gave Me horrible signal.,and cramps
Click to expand...
Click to collapse
This has been working sense day 1
---------- Post added at 07:41 AM ---------- Previous post was at 07:40 AM ----------
cslingerland said:
It's almost that time! It seems that a 100% bug free version of Cm9 is eminent! I personally cannot wait. Can anyone that knows the status for sure give us that are waiting some updates as they come??? I know there are a few builds but I'm talking about straight cm9!
+#4n|<$
Click to expand...
Click to collapse
unless we find a maintainer for CM9 or CM10 it will never be a full support by the CM team all we will have is other members builds on this site.
I'm completely ok with the CM team not supporting it.
cslingerland said:
I don't think 100% JB is as close as we would hope but I am definitely ready to flash a 100% bug free cm9 any day... Just a few more bugs! :/ thank god for devs on here.
Click to expand...
Click to collapse
JB is not as far off as ICS was to GB. The updates are minimal for JB where ICS was a complete rework. Let's pretend you have a house named GingerBread. For ICS, we had to demolish that house and redo the foundation. Now, the house is just about move in ready. Once we've moved in, we can decide to do some remodeling which will take a little longer (JB). The framework is already in place, the devs just need to make a few changes here and there.
luis86dr said:
I'm just happy we've gone as far as we have in development. A 4G NON Nexus Verizon device with AOSP is good enough for me lol. Not many out there.
HTC Rezound
Click to expand...
Click to collapse
Also, remember the S3 has CM9 and I wouldn't be surprised if the Note 2 gets it pretty quickly as well (since others are saying the Rez is the only non-Nexus with CM9).
It's a great accomplishment, I really hope we can get officially added to the ROM so we can update via ROM Manager.
cslingerland said:
I'm completely ok with the CM team not supporting it.
Click to expand...
Click to collapse
As stated above, we really want a maintainer so we can get all the benefits of ROM Manager. If it doesn't get official, I'll stick with AOKP so we can get official support.
No issues here with Chad's CM9 (compiled myself). Its now my dd.
Sent from my ADR6425LVW using xda app-developers app
Snuzzo said:
No issues here with Chad's CM9 (compiled myself). Its now my dd.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Snuzzo, are you gonna post it up?
maniac2k said:
Snuzzo, are you gonna post it up?
Click to expand...
Click to collapse
Do you want one?
I can upload mine. Built at 3 am this morning and working beautifully.
I'll start the upload in about 30 min.
It really is a daily driver.
"Bug free" - no such thing in software development.
One of my pet peeves as a software support technician.
GrayTheWolf said:
Do you want one?
I can upload mine. Built at 3 am this morning and working beautifully.
I'll start the upload in about 30 min.
It really is a daily driver.
Click to expand...
Click to collapse
Post link!
GrayTheWolf said:
Do you want one?
I can upload mine. Built at 3 am this morning and working beautifully.
I'll start the upload in about 30 min.
It really is a daily driver.
Click to expand...
Click to collapse
Hell yeah! Thanks GrayTheWolf!
badogg said:
"Bug free" - no such thing in software development.
One of my pet peeves as a software support technician.
Click to expand...
Click to collapse
Fuuuuuuuu!!!!!!!! Lololol jk bro. Obviously I meant "the closest thing to bug free " my bad
This is for developers only. No builds will be posted in this thread.
https://github.com/CM10DNA
For those who would like to work on it. I would recommend using a combination of the current HTC devices that have cm10.1 and the nexus 4 as a guide.
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Currently working:
Display
Data (3g/4g)
SMS, MMS should work also but I haven't tested
WiFi
adb
MTP
Sensors (compass, gyro etc)
Vibration
LEDs
Audio
GPS
Bluetooth
Camera (FFC still has some issues with face detect)
Not working:
BT headset audio
Bugreport spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0AltBJkYoAZNLdEtQVTFoVkdxcWFfYXFJd05zcFYzUHc&usp=sharing
chad0989 said:
This is for developers only. No builds will be posted in this thread.
I have successfully managed to pull over the required changes from the nexus 4 for AOSP compatibility of our framebuffer and modify our panel drivers to work with it. I've pushed the source to the CM10DNA github here:
https://github.com/CM10DNA
Everything is currently in the cm-10.1-chad branches. Right now its not fully booting but does have working video (the major hurdle with CM10.1). I'm heading out of town for the next week so I won't be able to work on it.
For those who would like to work on it. I would recommend using a combination of the current HTC devices that have cm10.1 and the nexus 4 as a guide. It shouldn't be too hard to get it booting the rest of the way by not building various components (audio, camera etc) until you find the hangup.
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Click to expand...
Click to collapse
I'm all for more development and would never want to sound ungrateful for any community contributions, but I get the impression (since I've been watching closely on XDA and IRC) that you're not working with drewx2 at all on THIS project even though it's been in the works for a while. If you were to contribute there instead of starting from scratch, we'd likely have it fully running in not time. He's only got a couple issues left and I'm not sure the framebuffer is one, but if his code-base falls short there, then you could at least improve on that.
I'd happily donate to you also if you were making contributions toward his project. Please consider that instead of going solo.
rainabba said:
I'm all for more development and would never want to sound ungrateful for any community contributions, but I get the impression (since I've been watching closely on XDA and IRC) that you're not working with drewx2 at all on THIS project even though it's been in the works for a while. If you were to contribute there instead of starting from scratch, we'd likely have it fully running in not time. He's only got a couple issues left and I'm not sure the framebuffer is one, but if his code-base falls short there, then you could at least improve on that.
I'd happily donate to you also if you were making contributions toward his project. Please consider that instead of going solo.
Click to expand...
Click to collapse
This is CM10.1, not CM10. Completely different animals even though one would think otherwise by the numbering. I have no desire to work on CM10. I appreciate your concern but please keep discussion on topic.
Sent from my HTC6435LVW using xda app-developers app
For anyone who is familiar with building CM if not Google is your friend. I have set up everything for you already. The default branch will pull cm-10.1-chad.
https://github.com/CM10DNA/android
Code:
repo init -u git://github.com/CM10DNA/android.git -b cm-10.1-chad
If you fix anything. Be sure to send a pull request back and we will take a look at it. Thank you.
Flyhalf205 said:
For anyone who is familiar with building CM if not Google is your friend. I have set up everything for you already. The default branch will pull cm-10.1-chad.
https://github.com/CM10DNA/android
Code:
repo init -u git://github.com/CM10DNA/android.git -b cm-10.1-chad
If you fix anything. Be sure to send a pull request back and we will take a look at it. Thank you.
Click to expand...
Click to collapse
I would love to take a look at, and for the guy above who thinks this is seperating the process I forked drews hub but could never get it to sync no matter what( I also have very little experience with github so it could be me). Best of wishes to you and yours on your trip. Have fun, be safe, and well. And thanks for making a new hub to play with. Last of my off topic-ness. More on topic what were your last efforts towards? It may make a good starting point.
Sent from my HTC6435LVW using xda premium
Sjflowerhorn said:
I would love to take a look at, and for the guy above who thinks this is seperating the process I forked drews hub but could never get it to sync no matter what( I also have very little experience with github so it could be me). Best of wishes to you and yours on your trip. Have fun, be safe, and well. And thanks for making a new hub to play with. Last of my off topic-ness. More on topic what were your last efforts towards? It may make a good starting point.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Right now it just gets to the boot logo screen. Maybe pulling a log finding out what's making it now boot fully.
Sent from my HTC6435LVW using Tapatalk 2
chad0989 said:
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Click to expand...
Click to collapse
Sent from my HTC6435LVW using xda premium
DirtySimpleClean said:
chad0989 said:
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
Click to expand...
Click to collapse
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
^^^^This^^^^
This is the second time in 24 hours I've had to come in this thread and clean it.
Please abide by the op's request.
I do want to mention for anyone working on this that CM10.1 is distinctly different than CM10. It uses an updated display HAL, audio HAL, GPS HAL, and telephony is significantly different. You can't simply patch up from CM10.
The good news though is that our phone uses the same SOC as the nexus 4. There is no support for the n4 and the newer SoC (apq8064) in CM10, only the older msm8960 which most other HTC devices use. Hence why I keep stressing that its a much better idea to work on 10.1. Most anything we need to update we can pull almost directly from the n4.
I hope now everyone has resolved their differences and this can be worked on as a group. Like I've said anyone can pull anything from my tree and I dont care nor do I need to be credited. I just want fully working AOSP. It should be quite reasonable to achieve now that the display is working. Especially because of our similarities to the nexus.
Sent from my HTC6435LVW using xda app-developers app
chad0989 said:
I hope now everyone has resolved their differences and this can be worked on as a group. Like I've said anyone can pull anything from my tree and I dont care nor do I need to be credited. I just want fully working AOSP. It should be quite reasonable to achieve now that the display is working. Especially because of our similarities to the nexus.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Finally a noteworthy post on this topic. :highfive:
When we work as a team , the total is worth more than the sum of individuals.
Iam sure with devs like you and drew, DNA community will get fully working AOSP at the earliest.
I have the CM10DLX stuff synced already so when I get home tonight I'll switch to the -chad branch.. lol.. sorry I just thing the branch name is a little comical. Either way, have a safe trip man! BTW: Another device I was wondering may help shed some light is the Moto Droid Razr HD. While only dual core it looks like the primary difference is the gpu.. so there may be some helpful stuff in there as well.
Edit, is adb functional?
I just built and booted this and was happy to see that it got as far as upgrading my apps (but then hung when "starting apps"). Very nice.
However, I couldn't get adb to connect. I tried editing the initrd.img to set the property ro.adb.secure=0 in case is was related to securing adb, but that didn't help.
Is there some magic that you need to do? If not, how do you start to debug this?
FYI, in case someone else hits the same error that I did, I also had to do:
Code:
mkdir -p out/target/product/dlx/obj/SHARED_LIBRARIES/libmmjpeg_intermediates/
touch out/target/product/dlx/obj/SHARED_LIBRARIES/libmmjpeg_intermediates/export_includes
to get it to build.
Do you think disabling the old ion api would do much? Pretty sure mako and other 3.4 kernels use new
JoelZ9614 said:
Do you think disabling the old ion api would do much? Pretty sure mako and other 3.4 kernels use new
Click to expand...
Click to collapse
I think it could potentially break some of our proprietary libs. Audio and camera most likely. I think we should keep it the way it is for now. Once everything is working we can give it a shot to see.
Sent from my HTC6435LVW using xda app-developers app
Finally finished sync over night. Started a build before I left for work. I guess the first thing we need to sort out is getting adb working... I wonder if usb debugging is disabled by default..
Sent from my HTC6435LVW using Tapatalk 2
EmericanX said:
Finally finished sync over night. Started a build before I left for work. I guess the first thing we need to sort out is getting adb working... I wonder if usb debugging is disabled by default..
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
adb was working on my build originally. It may have gotten messed up when I pulled the init scripts into the tree. Maybe try messing with the init.usb also.
Sent from my HTC6435LVW using xda app-developers app
Lack of ADB seems to be kernel related. I flashed a different kernel and was able to pickup adb... of coarse it did't play well with libs but atleast its some sort of progress! lol.
EmericanX said:
Lack of ADB seems to be kernel related. I flashed a different kernel and was able to pickup adb... of coarse it did't play well with libs but atleast its some sort of progress! lol.
Click to expand...
Click to collapse
It's something in the ramdisk I'm sure. I'll fix it when I get back this weekend if someone doesn't before then.
Sent from my HTC6435LVW using xda app-developers app
chad0989 said:
It's something in the ramdisk I'm sure. I'll fix it when I get back this weekend if someone doesn't before then.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I've started looking around ramdisk but I'm crashing for the night. I'll do some more looking around tomorrow.
EmericanX said:
I've started looking around ramdisk but I'm crashing for the night. I'll do some more looking around tomorrow.
Click to expand...
Click to collapse
I don't have time to do any real work on this (this is my daily driver, use heavily for work phone and it's a time sink to backup/restore/fix /sdcard/0) today,but I took the boot.img and changed init.rc to include init.dlx.usb.rc instead of init.usb.rc and I believe that should get adb up and running for you.
To test, I booted viper 1.1.3 with the old kernel (no adb ever, but amazingly enough the display works enough for the boot animation) and booted it with the changed kernel which give me adb access.
so like every day i check in atrix 4g thread
and finaly
they relese a public alpha kernel
i think its a start for us too
for 3.1 linux kernel
http://forum.xda-developers.com/showthread.php?t=2016837
Hope this spills over to us somehow.
Sent from my Slim Photon using xda app-developers app
The kernel included with 4.1.2 AOKP by th3bill has nearly the same features (except video recording, since we can't use atrix drivers).
I am watching that thread everyday as well. I hope th3bill is actually able and willing to do something about it once the kernel reaches a stable state.
Sent from my MB855 using xda app-developers app
Kernel is almost completed (at least a lot more than ours is). Where do we go from here?
kingnfs said:
so like every day i check in atrix 4g thread
and finaly
they relese a public alpha kernel
i think its a start for us too
for 3.1 linux kernel
http://forum.xda-developers.com/showthread.php?t=2016837
Click to expand...
Click to collapse
Not so fast. The kernel is known as Alpha Release Candidate 1 (Alpha-RC1). It has only been released from the devs to a select few testers. An official public release has NOT happened.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Not so fast. The kernel is known as Alpha Release Candidate 1 (Alpha-RC1). It has only been released from the devs to a select few testers. An official public release has NOT happened.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Offical alpha is here
tchcaphr said:
Offical alpha is here
Click to expand...
Click to collapse
This is true. My previous post is now outdated.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
This is true. My previous post is now outdated.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i know its outdated, just wanted to let you know; anyways maybe this kernel can help the photon..
tchcaphr said:
i know its outdated, just wanted to let you know; anyways maybe this kernel can help the photon..
Click to expand...
Click to collapse
The Photon and Atrix seem to be extremely similar hardware-wise... what changes would need to be made to the Atrix 3.1 kernel source to make this functional for Photon? From what I can tell, the camera, fingerprint scanner, and radio are the differences...
so...............
Krystian has already stated that he will work on porting the atrix kernel over to the photon once it is stable enough
Sent from my MB855
Somebody please help my Photon.... waiting for a good day to my Photon
Sent from my sunfire using xda premium
Hi guys,
I wanted to do that later but it looks like it will take me some more time to finish Olympus kernel. So I decided to start port for Photon. Since I don't own Photon device, I need couple of volunteers who are willing to break their phones. Also I would need someone who would manage bug tracking and possible hardware differences. I can barely track what's going on Atrix threads, so I need someone as a proxy, who would report me how the things are going. I'm looking for someone who can be considered at least advanced user with a lot of spare time. Also regarding potential testers, I'm sure there are different Photon revisions, so it would be the best if there was a one tester for each rev.
Regards,
Krystian
krystianp said:
Hi guys,
I wanted to do that later but it looks like it will take me some more time to finish Olympus kernel. So I decided to start port for Photon. Since I don't own Photon device, I need couple of volunteers who are willing to break their phones. Also I would need someone who would manage bug tracking and possible hardware differences. I can barely track what's going on Atrix threads, so I need someone as a proxy, who would report me how the things are going. I'm looking for someone who can be considered at least advanced user with a lot of spare time. Also regarding potential testers, I'm sure there are different Photon revisions, so it would be the best if there was a one tester for each rev.
Regards,
Krystian
Click to expand...
Click to collapse
My Electrify already has a dead radio. Please send me specific instructions on how/what to test and I'll try my best to assist you. Also, polish pride.
Here's some xda lovin' to photoners !
http://forum.xda-developers.com/showpost.php?p=45132893&postcount=1394
Disregard....I was not patient.
Hi guys, I just got photon second hand and have been doing a lot of reading to find out what the best thing I can do with it is.
Is the current work using the new open source tegra driver?
If that's the case, I would think it would be almost necessary to skip ICS & JB.
Hey guys,
First off. Mahdi rom is Amazing! I love all the features and it had just the right amount of features for my new G2! Thanks Doc for maintaining this for us!
Second, I am a kernel dev and am working on my own kernel for the G2. I have essentially made my base Savoca's Furnace Kernel (With his permission of course) and will be adding in features as I go. Currently I build for the Moto G but wanted to buy a higher end device and love this phone. I have the D800 (AT&T) so as it stands I only have a test kernel for the D800/JDI. You may be able to use Savoca's new panel tool that you flash after flashing the kernel to swap screen support. I would love for some others to test it out and let me know. I will be bringing a different perspective to kernel Dev'n than normal. I like to be hands on about the process and to instigate discussion so others can learn. Let me know if anyone is interested.I will be building for all variants that Furnace kernel supports.
Note to ALL: I will open an official thread when I am satisfied with testing. Thanks for your interest! Hope I can bring something new to the G2!
Right now I have added:
Custom Hotplug from Blechd0se (Moto G) Falcon Hotplug - Ultra simplified and efficient.
Sl(auo)b optimizations
frandom
ETC
Check source for more indepth info!
Just pm me if you are interested. Everything looks to be going pretty good so I should be opening a thread pretty soon. Remember this is still in Beta. Still I would love to hear from others out there. Thanks!
Render-Kernel-AOSP_d800-06-29-BR3-JDI.zip
Render-Kernel-AOSP_vs980-06-29-BR3-LGD.zip
Render-Kernel-AOSP_d800-07-01-BR3-LGD.zip
Render-Kernel-AOSP_d802-07-01-BR3-LGD.zip
Kind Regards,
Render
Source
kk-test is my active branch right now
Glad to see you here! I'll test out VS980 when you start building the other variants ?
JRJ442 said:
Glad to see you here! I'll test out VS980 when you start building the other variants ?
Click to expand...
Click to collapse
I will go ahead and rip you a build. Give me a sec . . .
JDI?
RenderBroken said:
I will go ahead and rip you a build. Give me a sec . . .
JDI?
Click to expand...
Click to collapse
LGD
JRJ442 said:
LGD
Click to expand...
Click to collapse
OK Give me a tick and I will build it. Should not take long.
Nice, love devs being able to jump in on the g2. Glad your here. The link you posted for the d800....should that work on aicp...?
Sent from my LG-D800 using XDA Premium 4 mobile app
jeff5347 said:
Nice, love devs being able to jump in on the g2. Glad your here. The link you posted for the d800....should that work on aicp...?
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not 100% sure but give it a try. Should hurt anything. I am fairly new to the G2 and don't know every single in and out yet. I do know that the source base is pretty fractured but I am hoping to bridge the gap a bit. Let me know so I can let others know in the future. Thanks!
OK just flashed. Booted fine but froze and that is my fault
..I started playing around and enabled intellidemand. From what I remember for some reason that gov is a problems. Rebooted and left the kernel stock. Now running fine and no problems. I'll update on battery and perf.
Sent from my LG-D800 using XDA Premium 4 mobile app
JRJ442 said:
LGD
Click to expand...
Click to collapse
OK Built and posted in OP#1
jeff5347 said:
OK just flashed. Booted fine but froze and that is my fault
..I started playing around and enabled intellidemand. From what I remember for some reason that gov is a problems. Rebooted and left the kernel stock. Now running fine and no problems. I'll update on battery and perf.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great, Thanks for the info, I will most likely be removing it anyways. I have inherited Savoca's source and am laying mine down ontop. He did all the amazing groundwork that will allow me to support numerous devices much much sooner. Thanks and let me know how it continues to work for you!
@RenderBroken booted up just fine. Running smooth. I'll report back tomorrow as well. Thanks again for building for us. ?
Render, since I cleaned the kernel and left it stock I'm getting the SOD. If I let the screen go off and try to turn the screen back on it just lights up black. Tried and tried but just a black screen. Unfortunately I had to go back for now. Can't wait to try it once it gets cleaned up.
Sent from my LG-D800 using XDA Premium 4 mobile app
Link to source ?
I looked at Savoca source and it appeared to have no FM support in audio driver, same as Mahdi now.
I'll copy my post from Mahdi thread, in case your interested in enabling FM:
I've concluded that sound/soc/msm/msm8974.c needs to be patched with the "#ifdef CONFIG_SND_FM_RADIO" code seen here: https://github.com/CyanogenMod/android_kernel_lge_msm8974/blob/cm-11.0/sound/soc/msm/msm8974.c
Unless you're up for that, I'll presume I'll try it myself.
Any tips for kernel building for a JDI LS980 ? I built a few Android kernels in 2013, but never even tried flashing them.
That said, I've been doing embedded linux professionally since 1997.
Thanks !
1 question. Why didn't you post the kernel in one of the development sections??
Transmitted via Geass
At first it could be in Original Dev section. I can test something on d802 LGD. @mikereidis u have a G2? if yes then it's great to see more devs here
RenderBroken said:
Not 100% sure but give it a try. Should hurt anything. I am fairly new to the G2 and don't know every single in and out yet. I do know that the source base is pretty fractured but I am hoping to bridge the gap a bit. Let me know so I can let others know in the future. Thanks!
Click to expand...
Click to collapse
hi, thank you for supporting our beloved g2 we all appreciate it, i just have a request. you see , only the Qremote can control the IR on our device, lg didnt use the real android open source drivers for it . so we cant use apps like smartIR whereas samsung n htc are compatible. im just suggesting if you can try and implement open source IR drivers to the g2 ? so that we can use all these apps that utilize that api i know this is gonna be an insanely though part as you'd have to figure out which hw IR we are using and then implement a compatible driver for it. but im just suggesting that this is perhaps the only bad part of the g2 till now
Super Post!
jeff5347 said:
Render, since I cleaned the kernel and left it stock I'm getting the SOD. If I let the screen go off and try to turn the screen back on it just lights up black. Tried and tried but just a black screen. Unfortunately I had to go back for now. Can't wait to try it once it gets cleaned up.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Then it sounds like you don't have LDG like you said but you have JDI.
mikereidis said:
Link to source ?
I looked at Savoca source and it appeared to have no FM support in audio driver, same as Mahdi now.
I'll copy my post from Mahdi thread, in case your interested in enabling FM:
I've concluded that sound/soc/msm/msm8974.c needs to be patched with the "#ifdef CONFIG_SND_FM_RADIO" code seen here: https://github.com/CyanogenMod/android_kernel_lge_msm8974/blob/cm-11.0/sound/soc/msm/msm8974.c
Unless you're up for that, I'll presume I'll try it myself.
Any tips for kernel building for a JDI LS980 ? I built a few Android kernels in 2013, but never even tried flashing them.
That said, I've been doing embedded linux professionally since 1997.
Thanks !
Click to expand...
Click to collapse
I will go ahead and push the latest changes and post link. Also I am fairly new to the G2 scene and just how fractured the source code is for it. I would love to take a look at this if its simple enough to add in. I am not against trying though. If you could, remind me when I open up the main thrad in the next few days. I am heading to the beach with my wife and son so will not be able to do much in the next 2 days but when I get back and I get some good word about the builds, I will open the thread and kick in to overdrive.
Ace42 said:
1 question. Why didn't you post the kernel in one of the development sections??
Transmitted via Geass
Click to expand...
Click to collapse
Just wanted some testers for now. I dont want to open a thread to a million questions about each device yet when I don't have a kernel ready for them. I will be creating a thread very soon.
shriom_manerker said:
hi, thank you for supporting our beloved g2 we all appreciate it, i just have a request. you see , only the Qremote can control the IR on our device, lg didnt use the real android open source drivers for it . so we cant use apps like smartIR whereas samsung n htc are compatible. im just suggesting if you can try and implement open source IR drivers to the g2 ? so that we can use all these apps that utilize that api i know this is gonna be an insanely though part as you'd have to figure out which hw IR we are using and then implement a compatible driver for it. but im just suggesting that this is perhaps the only bad part of the g2 till now
Click to expand...
Click to collapse
I like challenges, I will take a look as soon as I can. Most likely it will be after I get everything completely setup. If you could remind me later when I open up the official thread. Thanks!
Planning d801?
RenderBroken said:
I like challenges, I will take a look as soon as I can. Most likely it will be after I get everything completely setup. If you could remind me later when I open up the official thread. Thanks!
Click to expand...
Click to collapse
im experienced at coding, c,java,html and php. i ahve compiled kernels in the past but that was like 4 years ago.ill try my best to help you. although ill need your help too.
I've looked under terminal and it states I have a lgd. Flashed savacos older kernels that were lgd and they all worked fine. I get no black lines just when I shut the screen off it comes on but full black.
Sent from my LG-D800 using XDA Premium 4 mobile app
jamesd1085 said:
Planning d801?
Click to expand...
Click to collapse
I planning for all variants.
shriom_manerker said:
im experienced at coding, c,java,html and php. i ahve compiled kernels in the past but that was like 4 years ago.ill try my best to help you. although ill need your help too.
Click to expand...
Click to collapse
Great, I love to collaborate. That's the best way to learn! Thanks for the offer. My Google hangouts is
[email protected]
jeff5347 said:
I've looked under terminal and it states I have a lgd. Flashed savacos older kernels that were lgd and they all worked fine. I get no black lines just when I shut the screen off it comes on but full black.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Weird, I am pretty certain I build to LGD variant. Sorry brother. Try using Savoca's panel changer that you flash after the kernel. I even used Savoca's build script so not sure what the problem is but I am pretty sure that it's not a SoD problem you are having but a panel issue.