Hello.
As of now, one user has found the pot of gold from Cyanogen: A phone running on Cyanogen OS (Wileyfox Swift) with mostly the same specs. (The LTE modem is different than One G1's though.)
An unofficial CyanogenMod for the Second Gen. Android One would have to be developed. As of now, a custom recovery is here for the 2nd Gen. Android One, so it will be possible to root the device.
Original message:
Well, the Philippines now has the second generation Android One phone which came from I-Mobile IQ II, which came from General Mobile 4G. It was made (or should I say, "exported") by Cherry Mobile, the same folks who gave us the Cherry Mobile One. That Android One phone was called the "One G1." (No, not Juan gee Juan.)
Well, since it was released in stores right now, how are you going to do, Filipino XDA people?
My response in short words: "Wow, improved Cherry Mobile One. But I have to save my money for that..."
(Also.. Where am I going to introduce? Where's the "Greetings and Farewells" forum in here? I'm new here.)
check the review here:
http://www.semicurrent.com/2015/09/11/cherry-mobile-g1-android-one-review/
I saw that the bootloader can be unlocked via dev options. Would be awesome if it could be rooted already.
Cherry Mobile Android One G1 Keyboard
Hi. Im new here. I'm sorry if I am posting in the wrong section, I really don't have any idea where to post my inquiry. The problem is I am having trouble setting up my keyboard on "text messaging". I really don't know how to explain this but every time I am trying to make a message, it seems that the "Enter" key is missing from the keyboard. There is a "Smiley" Icon on my keyboard that replaced the "Enter" Key. I really don't like the "Smiley" Icon on my keyboard. However, when I am using "FB Messenger" the "Enter" Key is present. I want to know how to make the "Enter" Key available on text messaging.
throi1102 said:
Hi. Im new here. I'm sorry if I am posting in the wrong section, I really don't have any idea where to post my inquiry. The problem is I am having trouble setting up my keyboard on "text messaging". I really don't know how to explain this but every time I am trying to make a message, it seems that the "Enter" key is missing from the keyboard. There is a "Smiley" Icon on my keyboard that replaced the "Enter" Key. I really don't like the "Smiley" Icon on my keyboard. However, when I am using "FB Messenger" the "Enter" Key is present. I want to know how to make the "Enter" Key available on text messaging.
Click to expand...
Click to collapse
The stock messaging app doesn't have that option, but you can download several other messaging apps like Textra in which you can opt for that feature.
I noticed that Cherry Mobile One G1 is exactly the same as Wileyfox Swift that comes with Cyanogen OS. Maybe it'll be possible to flash Cyanogen OS onto G1 and vice versa (I'm more interested in flashing Android One rom on the wileyfox). What do you think?
Maybe I should earn money to buy this phone here
Myrtana said:
I noticed that Cherry Mobile One G1 is exactly the same as Wileyfox Swift that comes with Cyanogen OS. Maybe it'll be possible to flash Cyanogen OS onto G1 and vice versa (I'm more interested in flashing Android One rom on the wileyfox). What do you think?
Click to expand...
Click to collapse
Hmm, it seems that I found a ROM online at a Needrom website.
Seems that development would likely begin I think..
Myrtana said:
I noticed that Cherry Mobile One G1 is exactly the same as Wileyfox Swift that comes with Cyanogen OS. Maybe it'll be possible to flash Cyanogen OS onto G1 and vice versa (I'm more interested in flashing Android One rom on the wileyfox). What do you think?
Click to expand...
Click to collapse
Unless a dev takes a look at both sources, there's no sure way to find out. The specs and look are the same though.
The specs and everything is the same i have successfully flashed wileyfox swift system images onto General Mobile 4G and its working perfectly without a problem
I'm assuming you're talking about the "Enter" key to create a new line right?
Just click the shift key and the "Enter" key will be displayed where the "Emoticon" key was. You have to do this every time though...
throi1102 said:
Hi. Im new here. I'm sorry if I am posting in the wrong section, I really don't have any idea where to post my inquiry. The problem is I am having trouble setting up my keyboard on "text messaging". I really don't know how to explain this but every time I am trying to make a message, it seems that the "Enter" key is missing from the keyboard. There is a "Smiley" Icon on my keyboard that replaced the "Enter" Key. I really don't like the "Smiley" Icon on my keyboard. However, when I am using "FB Messenger" the "Enter" Key is present. I want to know how to make the "Enter" Key available on text messaging.
Click to expand...
Click to collapse
It does work?!?
Sadronis said:
The specs and everything is the same i have successfully flashed wileyfox swift system images onto General Mobile 4G and its working perfectly without a problem
Click to expand...
Click to collapse
Wait, it does work?
I think someone should flash this ROM to either the I-Mobile IQ II or Cherry One G1.
Also, were did you get the ROM? Can you share it?
Of course;
http://www.needrom.com/download/wileyfox-swift/
I have downloaded the rom from there and before you flash the files remember to take dump backup of every partition on phone unless you wont be able to boot stock rom otherwise
Greetings. I have made a big mistake. Try to flash rom posted in needrom, and I got hardbrick (qhsusb_buld detect when i connect). I am asking for any kind of advice. I have found some different methods with qualcomm tools but i dont have the required files to do it.
Thanks for your answers.
Possible CyanogenMod Compatibility? Link Included.
I'm posting the official link to the Wileyfox CyanogenMod OS for those curious enough to try it. According to Sadronis, it's compatible with the General Mobile 4G and, hopefully, the Cherry Mobile G1 since the specs are practically the same.
I'm still mulling over the idea of getting the Android One 2nd Gen so I can't speak as to it's compatibility.
For the dev or brave willing to try it out:
Code named Crackling
Please post your results.
Cyntil8ing said:
I'm posting the official link to the Wileyfox CyanogenMod OS for those curious enough to try it. According to Sadronis, it's compatible with the General Mobile 4G and, hopefully, the Cherry Mobile G1 since the specs are practically the same.
I'm still mulling over the idea of getting the Android One 2nd Gen so I can't speak as to it's compatibility.
For the dev or brave willing to try it out:
Code named Crackling
Please post your results.
Click to expand...
Click to collapse
Im using the latest nightly they have released and its ok
Interesting. So, the Wileyfox Swift (codenamed 'Crackling') is based off the Qualcomm Seed reference device? It seems that the Swift also lacks NFC, unfortunately. (Interestingly, I've also read a rumour that the Swift will be switched from Cyanogen OS to 'stock' Android - but presumably not Android One).
It's important to note, though, that it's only the General Mobile 4G Dual GM-113 that has the same LTE bands as the Wileyfox Swift - the Cherry Mobile One G1 and i-mobile iQ II have different ones.
dabotsonline said:
Interesting. So, the Wileyfox Swift (codenamed 'Crackling') is based off the Qualcomm Seed reference device? It seems that the Swift also lacks NFC, unfortunately. (Interestingly, I've also read a rumour that the Swift will be switched from Cyanogen OS to 'stock' Android - but presumably not Android One).
It's important to note, though, that it's only the General Mobile 4G Dual GM-113 that has the same LTE bands as the Wileyfox Swift - the Cherry Mobile One G1 and i-mobile iQ II have different ones.
Click to expand...
Click to collapse
The Swift, 4G, and G1 are all B3, B7, B20 from what I'm reading.
Source: Official G1 launch report. There are a few other sites that corroborate this but, this seems reliable enough since the reporter was able to do a hands-on review.
Sadronis said:
Im using the latest nightly they have released and its ok
Click to expand...
Click to collapse
This saves us the trouble of creating a device tree from scratch. :good:
Hi @pawitp, maybe we can just fork crackling's device tree to jumpstart Seed's own CM development?
Related
I'm a bit confused. Verizon carries the HTC One, but I don't see it listed separately here in the forums, or on the CyanogenMod listing of supported devices anywhere. Is this because it's not got enough users/developers on that network or am I missing something?
I'm considering purchasing the phone but I am concerned that I won't be able to root/ROM the thing.
Can someone clarify this for me?
Thanks!
ab2 said:
I'm a bit confused. Verizon carries the HTC One, but I don't see it listed separately here in the forums, or on the CyanogenMod listing of supported devices anywhere. Is this because it's not got enough users/developers on that network or am I missing something?
I'm considering purchasing the phone but I am concerned that I won't be able to root/ROM the thing.
Can someone clarify this for me?
Thanks!
Click to expand...
Click to collapse
There is a separate forum. Where are you looking? Click the Home icon and then Newest Devices.
Edit: It appears HTC is now blocking unlocking via htcdev. That was fast.
Weird
I am not sure where I was looking before. I do see it though.
I see now that it was also just released on Thursday. I suppose I should wait a bit for the folks over at CM to get it ported over there, shouldn't I?
Thanks!
ab2 said:
I am not sure where I was looking before. I do see it though.
I see now that it was also just released on Thursday. I suppose I should wait a bit for the folks over at CM to get it ported over there, shouldn't I?
Click to expand...
Click to collapse
It's a bit academic since they don't have root yet. There is a CM port for those lucky folks who were able to unlock on launch day, but it's a WIP at the moment.
Question 1: Seems like Focus S is never getting as much love as HTC Titan for some reason, why is that?
OK, I just got two extra WP phones I got back in 2012 SIM unlocked, sammy focus S and HTC Titan. I plan to give one to my parents in China to use, who are not tech savvy nor heavy cellular data user at all. I have a few questions based on what I skimmed through several WP forums (XDA etc) that I need you experienced users' help.
1. Which one is more idiot-proof for old users, focus S or Titan?
2. Once I SIM unlocked it, I assume they can just pop a local SIM to talk and txt, right? Anything else that needs to be manually set up?
3. I noticed a few threads talking about tricks of setting APN with Straight Talk. How about TMobile? And I assume that's only used for data usage right? If my parents just use it to talk and txt plus WIFI, it should be fine just leave the settings unchanged?
4. Also a lot of threads were debating whether to upgrade to WP7.8 or not and how to do it. Now it's 2014, is WP7.8 upgrade pushed automatically by MS already or I still need to follow the instruction and use 3rd party tools to do it?
5. Is there any custom ROMs for this phone at all? And what are the immediate updates/mods you guys suggest if I boot up the phone for the first time.
Thanks so much.
5.
The focus s was unfortunately an ATT exclusive , meaning one of the best designed windows phone 7 devices ever made was also only available to a tiny number of users, hence the lack of love!
As for setting it up,network unlock it, interop unlock, setup apn , update to 7.8 an your done
Sent from my arc 10HD using xda app-developers app
Focus S to android Os
So noone can get the Focus S to run any android Os ?
Bennyscrewz said:
So noone can get the Focus S to run any android Os ?
Click to expand...
Click to collapse
Dude,
With the exception of ONE device, the immortal HTC HD2, there has never been any (current) device that has had cross platform support, and lets be clear about the HD2, it was a WM device, that was opened up, and rather handily was also used as a test platform for WP. its android life started out as a hack that ran (initially) from within windows, later moved to its own ROM via MAGLDR. There was a lot of very cleaver people using a single device thus it had a lot of support to do these wonderful things.
OEMs shipping android then went nuts and made so many new devices it diluted the support available to specific phones and effectively killed off any further "HD2 Moments"
So no, the focus S doesn't have Android support. No one is working on it, no one tried to and to my knowledge no one will ever work on it, the same can probably be said about most phones.
Besides that, I cant remember which one because there was so many different versions it is but its essentially the same as the Samsung Galaxy 2(s?) so why not buy that if you want android on it?
and Finally
This has been asked So many times about so many devices, even googling it brings up an answer within the first few posts. Just take this as a wee helping hint, try search for your questions, this site has so many users over so many devices that statistically, its likely any question you may have has probably been answered somewhere by someone else
Hello Moto X part of XDA.
While I have a low post count, I'm a big lurker in XDA and not completely new to all this... well. I am new to this phone.
I just received my moto X second hand, and I have a couple questions. I have read The complete Moto X guide and Im still not clear in a couple things
My device is already bootloader unlocked, but not rooted yet. I have android 4.4.3, I thought of rooting so and flashing a new ROM.
So here are my questions:
1. I can see the list of features of the ROMs, but I do wonder if they keep the original moto X functionalities (the active display, the dedicated cores/activities)? Or is it not mentioned because is common knowledge that by using a custom ROM all those things are gone?
2. Can I somehow edit the navigation bar? I come from samsung phones (yeah... I know) and I got used to having the buttons from left to right as "menu", "home", "back". I know this can be done in some ROMs (i had my moto G that way) but I was wondering if there's any way of doing it in the stock firmware?
3. Does the write protection on the root folders only apply to Bootloader locked devices? Since mine is unlocked, once rooted, I wont have a problem to write the root folders?
Sorry for the noobish questions, but I find surprising how different the moto G is to the moto X regarding the developnment.
DBThanatos said:
Hello Moto X part of XDA.
While I have a low post count, I'm a big lurker in XDA and not completely new to all this... well. I am new to this phone.
I just received my moto X second hand, and I have a couple questions. I have read The complete Moto X guide and Im still not clear in a couple things
My device is already bootloader unlocked, but not rooted yet. I have android 4.4.3, I thought of rooting so and flashing a new ROM.
So here are my questions:
1. I can see the list of features of the ROMs, but I do wonder if they keep the original moto X functionalities (the active display, the dedicated cores/activities)? Or is it not mentioned because is common knowledge that by using a custom ROM all those things are gone?
2. Can I somehow edit the navigation bar? I come from samsung phones (yeah... I know) and I got used to having the buttons from left to right as "menu", "home", "back". I know this can be done in some ROMs (i had my moto G that way) but I was wondering if there's any way of doing it in the stock firmware?
3. Does the write protection on the root folders only apply to Bootloader locked devices? Since mine is unlocked, once rooted, I wont have a problem to write the root folders?
Sorry for the noobish questions, but I find surprising how different the moto G is to the moto X regarding the developnment.
Click to expand...
Click to collapse
1. Some ROMs based on other devices might not have Active Display. Some ROMs do. Check out the Moto X Android Development subforum and read the threads there. I also know that some ROMs use a AOSP active display replacement.
2. Most ROMs allow you to edit the navigation bar but you can also do this with Xposed.
3. Yes.
Let us know if you have any more questions ^_^
dier325 said:
1. Some ROMs based on other devices might not have Active Display. Some ROMs do. Check out the Moto X Android Development subforum and read the threads there. I also know that some ROMs use a AOSP active display replacement.
2. Most ROMs allow you to edit the navigation bar but you can also do this with Xposed.
3. Yes.
Let us know if you have any more questions ^_^
Click to expand...
Click to collapse
Thanks a lot for the quick response. I think I'll stay with the stock firmware for now, while I get used to the phone, but I will root it and try with xposed. The main reasons I want another rom was precisely because of the navbar and tweaking the looks of the thing, but if xposed will allow me that, i see no reason to have a whole new ROM just for that.
Once again, thanks a lot for the quick response!
DBThanatos said:
Thanks a lot for the quick response. I think I'll stay with the stock firmware for now, while I get used to the phone, but I will root it and try with xposed. The main reasons I want another rom was precisely because of the navbar and tweaking the looks of the thing, but if xposed will allow me that, i see no reason to have a whole new ROM just for that.
Once again, thanks a lot for the quick response!
Click to expand...
Click to collapse
You should be able to just install a custom recovery and flash SuperSU and then install Xposed. Not as simple for us locked devices
Happy rooting!
Sent from my XT1060 using XDA Premium 4 mobile app
Then you should install CyanogenMod and Gravitybox. You will have the best stock rom with constant nightly updates and the ability to do all the customization (Gravitybox) you need.
Sent from my Nexus 7 using XDA Free mobile app
MikeNaples said:
Then you should install CyanogenMod and Gravitybox. You will have the best stock rom with constant nightly updates and the ability to do all the customization (Gravitybox) you need.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Huh? CyanogenMod isn't stock....OR stock-based.
This means no Active Display or Touchless Controls.
Additionally, there are still some known bugs.
And finally, although nightlies will continue, this project is no longer being maintained for the Moto X because dhacker quit the project.
I disagree!
Sent from my Nexus 7 using XDA Free mobile app
MikeNaples said:
I disagree!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
You may disagree... Its your right.
But the post above yours is 100% accurate. ?
MikeNaples said:
I disagree!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
To which part? Anyone who knows anything knows that CM is not stock based! Its based on source code from github as stated in the OP of that ROM here: http://forum.xda-developers.com/moto-x/orig-development/rom-cyanogenmod-11-moto-x-t2719646
Confirmation that AD and Touchless Controls don't work are here: http://forum.xda-developers.com/showpost.php?p=53977187&postcount=248 and here: http://forum.xda-developers.com/showpost.php?p=52543363&postcount=67
Confirmation that dhacker is no longer maintaining the project can be located here: http://forum.xda-developers.com/showpost.php?p=54462994&postcount=303 or here: http://forum.xda-developers.com/showpost.php?p=54417178&postcount=294 or here: http://forum.xda-developers.com/showpost.php?p=54417194&postcount=295 (you can also check his TWITTER account)
One still-known bug (listed as recently as July 17th) can be found here: http://forum.xda-developers.com/showpost.php?p=54221828&postcount=276
So I'll ask again: what do you disagree with?!?!
I'm not badmouthing CM or it's (now non-existent) maintainers...I LIKE CyanogenMod. But everything I said would appear to be 100% correct. Especially about CM not being stock based (this is beyond obvious)....
Talking about customization on the X here is a example of Active Display. I wish moto will implement this later on though I think it might impact a Lil on battery life. Well for now I'll just test it. http://youtu.be/qk4-RpC8mUM
Sent from my XT1060 using Tapatalk
sorullo_xgrx said:
Talking about customization on the X here is a example of Active Display. I wish moto will implement this later on though I think it might impact a Lil on battery life. Well for now I'll just test it. http://youtu.be/qk4-RpC8mUM
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I don't get it???
KJ said:
I don't get it???
Click to expand...
Click to collapse
That was pretty cool. I would like a nice COLORFUL active display. I just doubt that was running off the low-voltage-core. There wasn't any relevant info in the description of that video...
samwathegreat said:
That was pretty cool. I would like a nice COLORFUL active display. I just doubt that was running off the low-voltage-core. There wasn't any relevant info in the description of that video...
Click to expand...
Click to collapse
Well I wanted for the clock to be able to choose different colors within the app. Maybe a xpose module.. But like I said it might impact in battery life though I'm not completely sure.. Maybe I'll just use darker colors ..
Sent from my XT1060 using Tapatalk
HI everyone,
Is there any definite information available regarding whether the Moto G2 would get the Android N? Thanks for sharing any information about this.
I pray for stock 6.0.1 and security update
support lenovo says that the last tests but when asked which country he could not say
lying, but I hope I'm wrong
forget about stock N..
only custom..
I'll wait a few more weeks as nothing appears I install custom 5.1.1 or RR 5.7.3 based on M.
but on all 6 rom touch issuse is there from what I read
Android N will not be coming to our beloved Moto G2. It will come by CM or other custom rom.
I very doubt it. Titan didn't even got stock 6.0.1 yet. Perhaps CM could bring it, who knows.
Thanks for the replies everyone. Really appreciate it!
Oh well, I am kinda used to the Moto G2 as my second phone. It was quite cheap and is still quite fast and problem-free. So, I was curious (and hopeful) about whether there was any chance of it getting the upcoming Android.
Thanks again! :good:
I am waiting for android N ...lets hope we get it soon
Well, if Lenovo fixed the touch issues, it would make things easier. Anyways, one of CM13's devs for Titan said that it would be hard because stuff changed the camera and without proper source code, it would be hard to make it work. One can only hope.
I just had a chat with Motorola Customer Support. They said that they do not have any information right now as to which all phones will get Android N and by when would they get it.
No stock naugat.
I'm a moto g 2014 owner and i got the official 6.0 patch on my device, though i was a part of a soak test but i'm pretty sure it was released right after the soak ended back in February. chances of Android N on moto g 2nd gen are slim but it could happen.
any chance of custom n rom
josfr4ncisco said:
Well, if Lenovo fixed the touch issues, it would make things easier. Anyways, one of CM13's devs for Titan said that it would be hard because stuff changed the camera and without proper source code, it would be hard to make it work. One can only hope.
Click to expand...
Click to collapse
Why? The custom ROM's currently available are awesome and provide all that I need for now. If getting the latest version of Android becomes that important to me then I will upgrade my phone to one that supports it. But that's me.
pastorbob62 said:
Why? The custom ROM's currently available are awesome and provide all that I need for now. If getting the latest version of Android becomes that important to me then I will upgrade my phone to one that supports it. But that's me.
Click to expand...
Click to collapse
Seems like you don't experience the touch issues which are plaguing the MM ROMs for this device then. And I agree, I don't see a hurry for Nougat for me right now, Marshmallow would be good enough. And I would prefer to see this phone die on MM with a fixed touch drivers (pls Lenovo), rather than going to NG with lots of things broken, according to the devs.
josfr4ncisco said:
Seems like you don't experience the touch issues which are plaguing the MM ROMs for this device then. And I agree, I don't see a hurry for Nougat for me right now, Marshmallow would be good enough. And I would prefer to see this phone die on MM with a fixed touch drivers (pls Lenovo), rather than going to NG with lots of things broken, according to the devs.
Click to expand...
Click to collapse
No I don't have any touch issues. But my post may have been prophetic. Yesterday, my mobile data stopped working for no apparent reason. All of the usual suspects are properly set and on still, so it is definitely a hardware issue. I have no data unless I am connected through a WIFI AP. Really sucks since I cannot access the WIFI at my job with personal devices. And the company laptop is so restricted I can't really get any personal business done on my break times.
Bottom line - I ordered a Moto G 4th gen yesterday evening. Hopefully it will serve me as well as did the 2nd gen. I really gave it a thorough run for the two years I had it. We'll see how it compares.
Touch issues happen only if you have glass protecting screen on some ROMs but if you have i recommend cm13 and if you need more personalization put xposed and thats all
EduardoClasheiro said:
Touch issues happen only if you have glass protecting screen on some ROMs but if you have i recommend cm13 and if you need more personalization put xposed and thats all
Click to expand...
Click to collapse
For all of the hype I see about xposed, I have never had a pressing desire to install it. At least not where my needs lie.
EduardoClasheiro said:
Touch issues happen only if you have glass protecting screen on some ROMs but if you have i recommend cm13 and if you need more personalization put xposed and thats all
Click to expand...
Click to collapse
I don't use a glass screen protector :v
pastorbob62 said:
For all of the hype I see about xposed, I have never had a pressing desire to install it. At least not where my needs lie.
Click to expand...
Click to collapse
Xposed is about more personalization if you dont like or dont care about personalization it will be useless, personaly i dont use it ????
josfr4ncisco said:
I don't use a glass screen protector :v
Click to expand...
Click to collapse
I have issues here and think it is the problem ???? good to know dont is this, by the way cm 13 fixed my problemas ????
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
clive48 said:
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
Click to expand...
Click to collapse
moto g2 xt1068 is not a 4g device. but you can use reliance jio via their jio mifi device which is a portable wifi Hotspot device.
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?
David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.