I know, I know... the droid x2 is a lost cause, but i have to make it last a little while longer and I have 2 of them so...
Is anyone interested or talented enough to try to get CM11 (kitkat) ported over to this device? I know @kev1nMark has been "talking" to dragonzkiller about getting into it, but anyone else have resources to contribute? I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Thoughts?
smallzfsu said:
I know, I know... the droid x2 is a lost cause, but i have to make it last a little while longer and I have 2 of them so...
Is anyone interested or talented enough to try to get CM11 (kitkat) ported over to this device? I know @kev1nMark has been "talking" to dragonzkiller about getting into it, but anyone else have resources to contribute? I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Thoughts?
Click to expand...
Click to collapse
I am considering it. This devices is a royal pain to work with though. I will see what i can do.
I'm certainly willing to test any builds that may come up, I'll have to locate a wall charger though..
Sent from my LG-LS970 using xda app-developers app
smallzfsu said:
I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Click to expand...
Click to collapse
In the same situation. It's looking like a good deal of work and might be a task I just simply don't have the skill for at this point. Still, I really want to have a useful old phone. Gingerbread makes me sad. Jelly Bean is just a resource hog. I've always wanted to learn a little more about the ROM build process and this might be a decent way to do it.
How does one go about porting KitKat to the X2?
markrulesallnow said:
How does one go about porting KitKat to the X2?
Click to expand...
Click to collapse
This is where I'm starting also w/ dragonzkiller's CM10 repos. http://wiki.cyanogenmod.org/w/Doc:_porting_intro
EDIT: Perhaps it's better to start building an updated CM10 just to get everything building correctly? With my lack of experience diving right into CM11 seems a bit bold.
One can simply put cm11 framework on a cm10 base but that's not what we want.
Sent from my XT907 using XDA Premium 4 mobile app
AKShotgun said:
One can simply put cm11 framework on a cm10 base but that's not what we want.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not what we want, but it may be our only option.
Sent from my SCH-I535 using xda app-developers app
Should anyone decide to take on this herculean task, I'll be more than happy to be a test bunny. My X2 is presently a glorified paperweight.
-blu
I have a Milestone X2 running under the ACS Alaska carrier. My device is rooted and I've used every ROM that Larson Thorpe has put in his MX2 collection. The ICS and JB roms did work, but had too many issues/crashes/reboots/etc so I just stuck with Eclipse 2.3 which is based on Gingerbread.
This phone is just... hard to deal with sometimes, and we all know it's mostly due to the amount of RAM. KitKat seems to take care of a ton of memory issues in Android (tested on my N7.) People have said that KitKat won't actually improve older devices by much, but any improvement would be amazing!
I'm totally down to fully test any builds anyone comes up with. I wish I could help build/develop for this phone, but I'm a web developer and have absolutely no skill with ROM building or kernels or anything like that.
Here's to hoping!
I can get everything set up and running (as in, ready to compile) but the compile errors are truly a mess to debug.
Is anyone willing to make a "how to" thread that describes how to make a basic rom, specific to this phone?
I think enough people are still interested, but I think we'd get further if we helped to educate each other.
LaserChicken said:
Is anyone willing to make a "how to" thread that describes how to make a basic rom, specific to this phone?
I think enough people are still interested, but I think we'd get further if we helped to educate each other.
Click to expand...
Click to collapse
This is about the closest thing I have seen, thanks Kevin for pointing it out already:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Maybe once it gets put on more devices and development starts up again. You could ask nitroglycerin if he would be willing to update eclipse. But being a 512mb device this would be huge.
Sent from my GT-N5110 using XDA Premium HD app
Since we don't have a unlocked bootloader we can't just download the source and compile it, it takes a lot of skill. That's why we have a low development rate
Sent from my XT907 using XDA Premium 4 mobile app
AKShotgun said:
Since we don't have a unlocked bootloader we can't just download the source and compile it, it takes a lot of skill. That's why we have a low development rate
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, actually, you can have CM compile around a pre-compiled kernel (what we have) but there's more to it than that.
One, we already have graphics issues...and KitKat forces you to have newer drivers or else you get black artifacting
This is due to OpenGL 3 not being supported by the vendor blobs
Our blobs don't even have ICS support...
Another nightmare is, yes, getting CM to take the precompiled kernel
If I got my hands on the source that the cm10.1 rom is based off of, we could start work
I would aim to start with 10.2, then maybe add in cm11 features but keep the old system
It would make things easier, keep radios, wifi, storage and display working...hopefully
Also, being as I'm on cm10, could anyone link me the patched recovery?
I'm glad to see I'm not the only one on the ol' X2, this would be so awesome if we got a KitKat ROM
Sent from my MB870 using xda app-developers app
optimusprimeuya said:
I'm glad to see I'm not the only one on the ol' X2, this would be so awesome if we got a KitKat ROM
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
I'm literally ready to start working on it now
But I need our device stuff and I'm waiting for a reply to a PM for it
---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------
Kevin M said:
I can get everything set up and running (as in, ready to compile) but the compile errors are truly a mess to debug.
Click to expand...
Click to collapse
You have the device tree?
That's all I really need to get started
I want to do this soooo badly
Hell...I'm willing to do this Nexus Image style: hacking the files into a precompiled image to get it working
---------- Post added at 10:04 AM ---------- Previous post was at 09:47 AM ----------
Found the sources
smallzfsu said:
I know, I know... the droid x2 is a lost cause, but i have to make it last a little while longer and I have 2 of them so...
Is anyone interested or talented enough to try to get CM11 (kitkat) ported over to this device? I know @kev1nMark has been "talking" to dragonzkiller about getting into it, but anyone else have resources to contribute? I've never worked on the device at such a low level before, but I have written apps for it as well as know a thing or two about code. I'm happy to contribute whatever i can, even if its as simple as running up tests on my spare device.
Thoughts?
Click to expand...
Click to collapse
I am willing to test. My programming skills are certainly not up to this task, but I would like to learn. Any way to get started?
polymath257 said:
I am willing to test. My programming skills are certainly not up to this task, but I would like to learn. Any way to get started?
Click to expand...
Click to collapse
I'm about to go work on it now
Maybe we'll have it in two weeks? No? Probably not...
I'll try building CM11, but don't expect the graphics to work
At all
Related
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.
I will just post this here in General, i would consider this as a complain, although we are greatefull for the job that every developer does in this comunity
example from CM10.X roms around in the forum
i m just wondering, those roms are not good to use as regular rom, i see many reports of battery drain, gps not working etc, what will happen if android 4.4 comes ? the developer moves to android 4.4 and leaves again a rom unfinished ?. what is the situation of the cm10.1 is it stable or again there are many open isues? i dont want to offend anyone but what i see is that we will always have an unfinished not good functioning rom... i 100% believe that in next weeks this version will be abandoned once again (CM10.2) this is what the history shows..... sorry i have been trying to switch to a costum rom since we got the bootloader unlocked but it seems its not worth like many people do so.
Anyways those were just some thoughts, if its not apropriate just delete this thread, i m staring thinking that i spent too much energy for this device trying the roms
spidr said:
I will just post this here in General, i would consider this as a complain, although we are greatefull for the job that every developer does in this comunity
example from CM10.X roms around in the forum
i m just wondering, this rom is not good to use as regular rom, i see many reports of battery drain, gps not working etc, what will happen if android 4.4 comes ? the developer moves to android 4.4 and leaves again a rom unfinished ?. what is the situation of the cm10.1 is it stable or again there are many open isues? i dont want to offend anyone but what i see is that we will always have an unfinished not good functioning rom... i 100% believe that in next weeks this version will be abandoned once again (CM10.2) this is what the history shows..... sorry i have been trying to switch to a costum rom since we got the bootloader unlocked but it seems its not worth like many people do so.
Anyways those were just some thoughts, if its not apropriate just delete this thread, i m staring thinking that i spent too much energy for this device trying the roms
Click to expand...
Click to collapse
Use a custom stock rom.
yes this is what i m doing, atm :good:
I don't get the point of this thread. There are simple fixes for most ROMs. You didn't even state your device.
Sent from my LG-P769 using XDA Premium 4 mobile app
then you dont read correct, it doesnt matter what device i have (lg optimus l9 p760), the point of this topic is that there is no stable costum rom and all the developers instead of creating one good version they stop and move to the next release of the android version, leaving not even one single good rom for daily use, and i m 100% that this will happen again now with the 4.4 version leaving no 4.3 stable version and the same situation was with 4.1 and 4.2 ....
Hyperion 8 crazy battery saving life!!! And super stable etc etc very less cons.
Or maybe you should do what I'm doing. Saving up money for the LTE Nexus 4. $299 is reasonable for me.
Sent from my LG-P769 using XDA Premium 4 mobile app
spidr said:
then you dont read correct, it doesnt matter what device i have (lg optimus l9 p760), the point of this topic is that there is no stable costum rom and all the developers instead of creating one good version they stop and move to the next release of the android version, leaving not even one single good rom for daily use, and i m 100% that this will happen again now with the 4.4 version leaving no 4.3 stable version and the same situation was with 4.1 and 4.2 ....
Click to expand...
Click to collapse
Wow that was all one sentence. Anyways, maybe you should try and LEARN how to develop and port a ROM, as that is what these forums are intended for. Maybe then you'd realize that it isn't easy, and it's discouraging to do it for free when selfish, grabby whiners such as yourself complain about every little issue.
Sent from my LG-P769 using XDA Premium 4 mobile app
---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------
Besides, this phone's forum is dying, and we're going to have to upgrade our devices soon anyways. I'll be sure to get ahold of an UNlockable bootloader.
Sent from my LG-P769 using XDA Premium 4 mobile app
Ilxaot said:
Wow that was all one sentence....
Click to expand...
Click to collapse
you still dont get the point and i still dont know why i answer you.:cyclops:
LaDY Vengeance said:
Or maybe you should do what I'm doing. Saving up money for the LTE Nexus 4. $299 is reasonable for me.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is a very good point, the last past months i started believing that the only android devices that worth to buy are the nexus line...
If developers want to jump between ROMs they can just do it and is not wrong. They are doing this for educational purposes and they are doing it for free. You can do your own ROM and stop complaining, nobody is working for you. The point of this entire site is to learn things, this is not a service.
BTW CM 10.1.3+Xposed is working flawlessly on my P778g, much better than stock. Completely stable.
mato_d007 said:
If developers want to jump between ROMs they can just do it and is not wrong. They are doing this for educational purposes and they are doing it for free. You can do your own ROM and stop complaining, nobody is working for you. The point of this entire site is to learn things, this is not a service.
BTW CM 10.1.3+Xposed is working flawlessly on my P778g, much better than stock. Completely stable.
Click to expand...
Click to collapse
well the purpose of this topic wasnt about asking someone to service me or work for me, if i could do a rom i would try at least to bring it in an acceptable level so others can enjoy my work, the current situation is everyone trys and then switches back to the stock over and over again, and this will be the only case here, unless they focus on a version and dont jump arround everytime google gives a new release. Imo this would be possible only if they couldnt use a newer version...
Flash paranoid android it's the best stable rom and don't forget xda is a development site...
Sent from my P760 using xda app-developers app
I found the best solution. There is a rom called DynamiteBean. Here's how to install it.....
Place your L9 on a stick of dynamite and light the fuse.
Sent from my LG-P769 using XDA Premium 4 mobile app
---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------
Lol. Sorry. My idiot brother took my phone and posted that.
Sent from my LG-P769 using XDA Premium 4 mobile app
cm 10.1 and 10.2 by Anton have been my daily drivers for months. less problematic than stock.
Sent from my LG-P769 using XDA Premium 4 mobile app
Eh, do stock rom (still a rom, right ) with root, Titanium for disable bloatware, and some other apps count as "stable for daily use"?
Yeah, I am on stock, with few apps (Google apps, Phone, Camera taking 1080p, an ebook reader, a gps navigator app) running smoothly and I consider that's good for my daily use (2h screen on avg, recharging every other day). Games are on my 10" tablet of course!
chicguy said:
Eh, do stock rom (still a rom, right ) with root, Titanium for disable bloatware, and some other apps count as "stable for daily use"?
Yeah, I am on stock, with few apps (Google apps, Phone, Camera taking 1080p, an ebook reader, a gps navigator app) running smoothly and I consider that's good for my daily use (2h screen on avg, recharging every other day). Games are on my 10" tablet of course!
Click to expand...
Click to collapse
What you stated is a modified stock. If you want something else, say CM 10.1, develop for yourself. Every developer will want to work with the most recent version, 10.2. Why go back to an older version?
What you're looking for is quality like that of what Google releases Android in. You won't get that on an unofficial port to a phone. Even CM has bugs that need fixing. Don't like it? Learn to code and fix them yourself. These devs work their ass off for people such as I who do not have their skill set, and you should be grateful!
thehritzinator said:
What you stated is a modified stock. If you want something else, say CM 10.1, develop for yourself. Every developer will want to work with the most recent version, 10.2. Why go back to an older version?
What you're looking for is quality like that of what Google releases Android in. You won't get that on an unofficial port to a phone. Even CM has bugs that need fixing. Don't like it? Learn to code and fix them yourself. These devs work their ass off for people such as I who do not have their skill set, and you should be grateful!
Click to expand...
Click to collapse
does my message looks like i disagree with what you say, NO, there is a point on my message those developers do good job but if they continue moving everytime a new release comes then we will always have an unfinished rom with serius instabilities, i dont speak about minor bugs. i m many years arround and i have tried roms in many different phones, what happens here i see it first time. anyway how can we lock this, noone is goin nowhere here.
spidr said:
does my message looks like i disagree with what you say, NO, there is a point on my message those developers do good job but if they continue moving everytime a new release comes then we will always have an unfinished rom with serius instabilities, i dont speak about minor bugs. i m many years arround and i have tried roms in many different phones, what happens here i see it first time. anyway how can we lock this, noone is goin nowhere here.
Click to expand...
Click to collapse
Go make your own ROM or go back to iOS. You're just complaining of WHY instead of learning HOW.
It really pisses me off that people like you think ROMs are made for them. They aren't in most cases. ROMs, a lot of the time, are made to further the knowledge of the creators/porters because they actually want to learn.
CM, PA, AOKP, etc. official releases are made for money.
---------- Post added at 06:46 PM ---------- Previous post was at 06:44 PM ----------
Besides, look at what you post. No offense, but it seems awful "babyish" a lot of the time. Kind of like you're begging for something. You've been on here since 2007, over 6 years! Imagine if you were learning this ENTIRE time. You'd be a pro!
Sent from my LG-P769 using XDA Premium 4 mobile app
spidr said:
does my message looks like i disagree with what you say, NO, there is a point on my message those developers do good job but if they continue moving everytime a new release comes then we will always have an unfinished rom with serius instabilities, i dont speak about minor bugs. i m many years arround and i have tried roms in many different phones, what happens here i see it first time. anyway how can we lock this, noone is goin nowhere here.
Click to expand...
Click to collapse
That depend on preference. Most people want something new, but there're also many that want stable rom for everyday used. You can choose rom that build on stable version such as CM 10.1.3, PAC mr1 milestone.2 or event custom stock rom out there. These roms are very stable and almost bugs free.
But if you want to play with new features and some minor bugs/known issues don't annoy you, you can flash CM 10.2 or PAC mr2.
From what I read, it's not easy to make these CM roms. You need to be pretty savvy with Ubuntu and know how to use terminal. I saw a YouTube video and it confused me after 5 minutes....lol. The devs deserve so much respect!
Sent from my LG-P769 using XDA Premium 4 mobile app
(Cross post from forum.cyanogenmod.com)
Hi everyone,
I wonder if there any plans to support ATT version of Galaxy Note ?
all recent updates are minor and I don't have any hope that CM10.2 (not even mentioning CM11) will be ported to it which is kind of sad.
I understand that there are some issues with stability and drivers. Does that mean I need to get other hardware to continue using CM ?
Due to all those problems I switched back to stock image and not happy with it, but it is damn stable ((
Thanks for any update from the team.
look one thread down from yours, tell me what you see.
JamieD81 said:
look one thread down from yours, tell me what you see.
Click to expand...
Click to collapse
Jamie you the man.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
stimur said:
(Cross post from forum.cyanogenmod.com)
Hi everyone,
I wonder if there any plans to support ATT version of Galaxy Note ?
all recent updates are minor and I don't have any hope that CM10.2 (not even mentioning CM11) will be ported to it which is kind of sad.
I understand that there are some issues with stability and drivers. Does that mean I need to get other hardware to continue using CM ?
Due to all those problems I switched back to stock image and not happy with it, but it is damn stable ((
Thanks for any update from the team.
Click to expand...
Click to collapse
so what i am reading here is you have 6 posts. i understand that you cannot post in development yet, but that does not slow you from reading.
i am not a technical brainchild and lack the ability to understand some of the terminology, so you will have to give me a little leeway.
development may have appeared to have slowed, but take into consideration the age of our device and the rate manufacturers are producing devices. we may not ever get another official upgrade for our Note, but my phone has ran better in the last few months than previous 8 months. there are some brilliant folks out there working selflessly for us. you may not find much in the straight CM development department, but since release of 10.2/ 4.3 roms, it is much more stable than 4.2 ever was. it runs smooth and effortless with none of the random reboots which plagued 4.2.
now we have quickly bumped to the 4.4 development which is still in its infancy. give it time. there are 2 Alpha/Preview releases right now, with at least another in the works that i know of. my guess is someone will have a Beta or full release by the end of the week at the rate these guys go. cant hold me to it as i am just a recipient who benefits from their deeds. that's just my guess from what i see as far as their work pace.
so excuse me now, i have to put some Kit Kat 4.4 on my phone, which has only been approval to run official 4.1.2 JB.
i am sure this is going to prove to be a good conversation starter here. thank you
take the tour here and ask your question again
i am sure this is going to prove to be a good conversation starter here. thank you
take the tour here and ask your question again
Click to expand...
Click to collapse
Thanks for your reply, captemo.
I'm sure there are brilliant people in CM team and they are doing amazing job, this is doubtless.
This is the only reason I'm trying to get back to CM world and get any word on further development.
My only source of information on the releases are:
http://10.1.cmxlog.com/?device=quincyatt
https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
http://download.cyanogenmod.org/?device=quincyatt&type=
and xda of course
First three show very little progress on this particular device. I'm not complaining, but just trying to understand current state of I717 support.
In comparison with I717 twin - N9000, we get less updates.
I saw 10.2 builds in XDA forum threads, but I consider them as unofficial builds, and I know nothing about them, how well they are performing, etc. I will try them for sure, thanks for pointing that out.
All my question is about is future support of this hardware, should I think about upgrade or just give up and use stock ...
JamieD81 said:
look one thread down from yours, tell me what you see.
Click to expand...
Click to collapse
Yes, thanks for pointing that out, I will try your builds.
I will be grumpy user, I promise
stimur said:
Thanks for your reply, captemo.
I'm sure there are brilliant people in CM team and they are doing amazing job, this is doubtless.
This is the only reason I'm trying to get back to CM world and get any word on further development.
My only source of information on the releases are:
http://10.1.cmxlog.com/?device=quincyatt
https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
http://download.cyanogenmod.org/?device=quincyatt&type=
and xda of course
First three show very little progress on this particular device. I'm not complaining, but just trying to understand current state of I717 support.
In comparison with I717 twin - N9000, we get less updates.
I saw 10.2 builds in XDA forum threads, but I consider them as unofficial builds, and I know nothing about them, how well they are performing, etc. I will try them for sure, thanks for pointing that out.
All my question is about is future support of this hardware, should I think about upgrade or just give up and use stock ...
Click to expand...
Click to collapse
as i said take the tour, take some roms for a test drive. i don't know what you consider your experience level is........
everything runs a bit different on everybodys phone. for example, the Carbon rom has lots of cool features, but it just doesn't seem to want to work on my phone. i just don't want you to label all roms on the basis of one. Hellybean runs great on my phone. there are some here that wont give a phone or rom time to settle in. they make so many tweaks and adjustments in a rapid amount of time, they don't know if there adjustments actually did anything.
so be patient......if its not compatible for your phone, you will probably know right away. if it works, give it some time. there are good and helpful people here. just try and help yourself first and read.
getting ready to slam some Kit Kat on my phone right now with Jaime's CM11 preview 4.
As cyanogenmod seems to have dropped us for 10.2, we are unlikely to see official CM11 support. Our hope for further development lies in unofficial builds from Jamie and Patch who have been kind enough to build from source and share their talents with us.
Normally, I would accept that, at some point, you have to stop beating a dead horse. It's unrealistic to expect a 2 year old device to be supported with the latest and greatest - especially in an environment like Android which seems to have such a quick cycle.
The alpha builds, however, have proven to be more stable on my device than anything 4.2 or 4.3. My question is whether or not we will see some important functionality (like TTS and video camera) restored on OUR device if it is not being supported by CM officially?
crutzulee said:
As cyanogenmod seems to have dropped us for 10.2, we are unlikely to see official CM11 support. Our hope for further development lies in unofficial builds from Jamie and Patch who have been kind enough to build from source and share their talents with us.
Normally, I would accept that, at some point, you have to stop beating a dead horse. It's unrealistic to expect a 2 year old device to be supported with the latest and greatest - especially in an environment like Android which seems to have such a quick cycle.
The alpha builds, however, have proven to be more stable on my device than anything 4.2 or 4.3. My question is whether or not we will see some important functionality (like TTS and video camera) restored on OUR device if it is not being supported by CM officially?
Click to expand...
Click to collapse
You say this but look at the craptivate and how much development it's getting
Sent from Outer Space
Mechapanda said:
You say this but look at the craptivate and how much development it's getting
Sent from Outer Space
Click to expand...
Click to collapse
Captivate also probably sold 50 million more devices then the i717 so there is your reasoning
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
JamieD81 said:
Captivate also probably sold 50 million more devices then the i717 so there is your reasoning
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have a good point, at least 4.4 will probably run better than any other 4.x before it
Sent from Outer Space
Mechapanda said:
You have a good point, at least 4.4 will probably run better than any other 4.x before it
Sent from Outer Space
Click to expand...
Click to collapse
Your just crying for some slimkat
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
JamieD81 said:
Your just crying for some slimkat
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Break me a piece of that slimkat! Cm is nice but slim is still slim :3
Sent from Outer Space
Mechapanda said:
Break me a piece of that slimkat! Cm is nice but slim is still slim :3
Sent from Outer Space
Click to expand...
Click to collapse
All 4.4 Roms right now are pretty much the same aosp 4.4, no rush on getting things rolling till things change and merge
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
JamieD81 said:
All 4.4 Roms right now are pretty much the same aosp 4.4, no rush on getting things rolling till things change and merge
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I know
Sent from Outer Space
JamieD81 said:
Captivate also probably sold 50 million more devices then the i717 so there is your reasoning
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So it would be better to get some of popular devices and use it, because "million flies can not be wrong" ?
stimur said:
So it would be better to get some of popular devices and use it, because "million flies can not be wrong" ?
Click to expand...
Click to collapse
More devices in hand means more users and devs, dunno why that's hard to understand
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
JamieD81 said:
More devices in hand means more users and devs, dunno why that's hard to understand
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh, no, don't get me wrong, I do understand that.
What I'm also trying to understand what would be a better strategy to have decent device with enough attention from developers...
There should be some balance here, since advanced devices are good in performance, but expensive and not widely used.
JamieD81 said:
All 4.4 Roms right now are pretty much the same aosp 4.4, no rush on getting things rolling till things change and merge
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Personally, I'm loving the AOSP feel of 4.4 in a way that I have never really cared for it in Android versions prior. The way Google now is integrated into the GEL is how I would use Nova Launcher to setup previous versions.
With it's super stability, I am really praying that you give us something akin to your Nexus or Evervolv roms...Hell if we can just get working TTS and Video camera on top of what you've given us with your alpha, I'm done...............
.......until my next phone.
stimur said:
oh, no, don't get me wrong, I do understand that.
What I'm also trying to understand what would be a better strategy to have decent device with enough attention from developers...
There should be some balance here, since advanced devices are good in performance, but expensive and not widely used.
Click to expand...
Click to collapse
What are you talking about? What strategy? What balance?
Devs are also users. Almost all of the devs work on the devices that they own. We may not have the quantity of devs for other devices, but we definitely have quality devs. I also have GTab 2, and LG Optimus and Galaxy S2 LTE, which I manage for my family. Some have very active devs, some don't, but they all have good devs.
I don't know what you mean by "enough attention from developers", but we are getting plenty from our devs even if we don't deserve them. Whatever we are getting beyond the official 4.1.2 is all gravy. Jamie's CM11 preview is running awesome, and I haven't tried Patch's 4.4 rom, but I expect the same.
What more are you asking for?
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
crparmer
not sure if i spelled it right.
thayl0 said:
crparmer
not sure if i spelled it right.
Click to expand...
Click to collapse
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
thayl0 said:
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
Click to expand...
Click to collapse
I know that but when people have asked him to add sleep to wake he didn't seem interested in that I'm not dogging him at all man he great no question asked.
Sent from my HTC6435LVW using Tapatalk
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
crpalmer said:
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
Click to expand...
Click to collapse
This is why i was trying to shout out to other. I know your work is the real deal man. Its just something I'm interested in. In no way was i trying to insult you.
Kauffman_c said:
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what settings you use with active display but I'm not really sold using it. I like sweep2wake as well.
Sent from my HTC6435LVW using Tapatalk
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
yeah some nice s2w like the old cubed kernel so you can do just "back to home" to wake it, its so nice i dont see how ppl dont want it of course unless they have some crazy circumstance like crpalmer just described
but we have a lot of diff roms so something like this would be rather difficult to choose one version of android for this to be implemented on or many kernels, lotta work it seems.
Ask .torrented. He made a s2w kernel a few months ago. He may have a very busy schedule but if enough people ask he may do it.
jamiethemorris said:
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
Click to expand...
Click to collapse
Yeah I Dont think it's that simple unfortunately.
Sent from my HTC6435LVW using Tapatalk
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
I couldn't resist, I just had to try it. I figured the worst that would happen is I'd have to reflash my ROM. So I flashed the HTC one sti kernel here: http://forum.xda-developers.com/showthread.php?t=2507710 it flashed and booted just fine and everything works... None of the s2w dt2w features etc are working but it said it flashed successfully so I'm assuming it's running the kernel... I don't remember what it said in about phone before but it currently shows "3.4.10-CM-gbce7128 Robert @ minty #1."
Edit: yeah I'm pretty sure that's the stock kernel...
It was worth a try right?
@crpalmer would you be willing to give me some pointers on porting or building a kernel? I'm somewhat inexperienced with building, so I don't know if I should bother taking on a task like this.
Sent from my Droid DNA using Tapatalk Pro
coachcrey said:
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
crpalmer said:
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
Click to expand...
Click to collapse
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
crpalmer said:
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
Click to expand...
Click to collapse
OK right in man. Thanks for all the hard work.
Sent from my HTC6435LVW using Tapatalk
I guess my post didn't go through... @crpalmer what type of programming knowledge are we taking about? My knowledge is limited to some dsdt editing and supercollider... In other words, I'm definitely not a programmer but I understand the general concepts.
Edit: I'm not too experienced with git either but I have built cm10.1 From the source for my nexus 7 a few just as learning experience.
Sent from my Droid DNA using Tapatalk Pro