Related
i always think that Android is more powerful because it is open platform and so you can change source code and create custom rom while IOS you can't change source code and you can't modify OS. So even if you jailbreak the iPhone, there's not much you can do except unlock a few forbidden features and modify some playlists.
But then in another forum, i read this comment:
"Android will never be as powerful as Unix! iOS just scratches the surface of unix until root access allows full control. Android is just several java classes compiled into what you believe is an OS. Android will never be more than glorified embedded software....which is why it is buggy as Hell!"
I always think Android can do things IOS can't via custom ROMS, mods, but his comment suggests otherwise. I am a tech noob, can the Masters out there help me a bit? Thanks
No.
Sent from my GT-N7000
A)this has nothing to do with the note so shouldnt be here
B)considering android is a linux based os and linux is based unix i really dont see where the quote is coming from. And without defining what you mean by powerful no one can help
Sent from my GT-N7000 using xda premium
iOS merely seems more powerful and stable simply because it is like custom software tailored to custom hardware. It is designed to work with specific internal hardware. Android, on the other hand, has to work with a myriad of generic devices and thus cannot be as optimized as Ios. That is why android devices must have higher specs and be more powerful than the iphone in order to compete with the efficiency of apple's os (brute force vs efficiency).
Sent from my GT-N7000 using xda premium
Its never been and it will never be.
And Its not the right forum to asking for the comparision. I think. Ask in Android or IOS forums. They will answer your questions in better way.
Raymond Chong said:
i always think that Android is more powerful because it is open platform and so you can change source code and create custom rom while IOS you can't change source code and you can't modify OS. So even if you jailbreak the iPhone, there's not much you can do except unlock a few forbidden features and modify some playlists.
But then in another forum, i read this comment:
"Android will never be as powerful as Unix! iOS just scratches the surface of unix until root access allows full control. Android is just several java classes compiled into what you believe is an OS. Android will never be more than glorified embedded software....which is why it is buggy as Hell!"
I always think Android can do things IOS can't via custom ROMS, mods, but his comment suggests otherwise. I am a tech noob, can the Masters out there help me a bit? Thanks
Click to expand...
Click to collapse
You have a note and you are wondering whether ios is more powerful than android?? It's a sad day for humankind!
Sent from my GT-N7000 using free xda app-developers app for poor people..
I feel like ios is stable than android
But coming to features,android is far better than ios
Android is totally customizable
I feel android is stable enough for my(every android user) use and so why ios??
Raymond Chong said:
i always think that Android is more powerful because it is open platform and so you can change source code and create custom rom while IOS you can't change source code and you can't modify OS. So even if you jailbreak the iPhone, there's not much you can do except unlock a few forbidden features and modify some playlists.
But then in another forum, i read this comment:
"Android will never be as powerful as Unix! iOS just scratches the surface of unix until root access allows full control. Android is just several java classes compiled into what you believe is an OS. Android will never be more than glorified embedded software....which is why it is buggy as Hell!"
I always think Android can do things IOS can't via custom ROMS, mods, but his comment suggests otherwise. I am a tech noob, can the Masters out there help me a bit? Thanks
Click to expand...
Click to collapse
damn! you've been watching too many scifi movies haven't you?
your confused my young 'padawan' friend.... the dark side clouds everything in you.. The fear of doubt leads to the dark side my young padawan friend... cloud your mind do not...
:silly:
Go to an iOS forum, and ask the same question and see the reply you get. 99% of responses will be just the opposite of
the ones here.
Thread heading no where, Closed and Thank you.
First of all, my apologies if this thread belongs to Q&A - I was not sure mods.
I read about Jolla Sailfish OS being open source. Is it possible to port it on Galaxy S? I have seen no discussion about it. Sailfish OS does look promising.
Regards
DJ
I'm curious, what is the advantage of Jolla vs android?
For a short while I was excited to hear ubuntu was making its way to phones, then with a mix of going from ubuntu to arch on my desktop and the realization that ubuntu doesn't have much of an advantage over android anyway I kinda forgot about it...
Sent from my GT-I9000 using xda premium
http://mer-project.blogspot.co.at/2013/04/wayland-utilizing-android-gpu-drivers.html?m=1
Sailfish uses mer as core of its system. I once read a blogpost...see above...that they try to make the display server wayland,the new xserver replacement compatible with android graphic drivers. I think it will be possible to get the rest of the drivers also somehow working....well i want sailfish too but atm i can only wait
Sent from my GT-I9000 using Tapatalk 2
Hr Kristian said:
I'm curious, what is the advantage of Jolla vs android?
For a short while I was excited to hear ubuntu was making its way to phones, then with a mix of going from ubuntu to arch on my desktop and the realization that ubuntu doesn't have much of an advantage over android anyway I kinda forgot about it...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
android has the fragmentation and lagging problem after a certain usage. also the interface of jolla is really nice , why buying a Jolla if SGS still has some fight left in its big heart?? :victory::victory::victory:
chainer1 said:
http://mer-project.blogspot.co.at/2013/04/wayland-utilizing-android-gpu-drivers.html?m=1
Sailfish uses mer as core of its system. I once read a blogpost...see above...that they try to make the display server wayland,the new xserver replacement compatible with android graphic drivers. I think it will be possible to get the rest of the drivers also somehow working....well i want sailfish too but atm i can only wait
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Aye Wayland is exciting, but what with all the snags it runs into (Ubuntu abandoning it, getting forked) the relatively small team will probably not complete it in a few years yet...
Sent from my GT-I9000 using xda premium
Sailfish OS Now Supports Android Apps Officially
Maybe this will be an added incentive along with the refreshing UI.of Sailfish os.
Link : http://www.ubergizmo.com/2013/09/sailfish-os-now-supports-android-apps-officially/?utm_source=mobile
I'd really like to have Jolla OS on our phone to try Now that its out ...
Crazy what all is possible ...:good:
YouTube http://www.youtube.com/watch?v=y64ja7WBHU8
Looks okay, but there's nothing really groundbreaking about it, or anything that's a real advantage over android considering the customisation you can do with android, or am I missing something?
I had a look at a couple of demo videos for it but I can't see any great things about it that would make me want to change OS. I've already got a hidden status bar(expanded desktop), on off toggles for things I like to be able to quickly switch(quick settings), and nice looking customised home screens.
Controlling apps from their multitasking thumbnails was the only real new thing I saw, and about the only use for that is pausing music or skipping tracks (which was obviously the way it was demonstrated in their videos, because it's pretty much the only use for such a feature). With any other app you need to be able to see what you're doing, so even that is a bit pointless.
Oh, and sailfish is a silly name.
Sent from my GT-I9000 using Tapatalk
It`s not about customizations or having something special. It is new and hopefully wont start lagging after one week of heavy use
Proud owner of an ASUS TF300T stock and the "old faithful" SGS i9000 powered by AndroSlim
Anything new is welcome with an open heart. It's not about jumping ship to a new OS ... But trying them is what I am interested in the most.
I still want to user Ubuntu Touch on daily basis but it's the app ecosystem the issue for my daily use.
Is any here can port sailfish os for us
As using android on this device is very laggy even if u flash GB (2.3.x)
Sent from my iPhone using Tapatalk
Is it possible to port over Nexus 4 ROMs (including 4.4 KitKat) to HTC First? HTC has released the kernel source code for our phones. I like the Nexus experience, and don't really want CM. If HTC made Nexus handsets for Google I would have bought that instead, but the minimalist nature of the First really appeals to me.
r00tb33r said:
Is it possible to port over Nexus 4 ROMs (including 4.4 KitKat) to HTC First? HTC has released the kernel source code for our phones. I like the Nexus experience, and don't really want CM. If HTC made Nexus handsets for Google I would have bought that instead, but the minimalist nature of the First really appeals to me.
Click to expand...
Click to collapse
um that isnt quite as easy as you think. porting cm is easier cause our phone has hardware relatives like the HTC One mini which use the same drivers and stuff like that. also our screen size matches the One mini so porting it would be as easy as 1-2-3. it does take time but it will be a hell of alot faster than BUILDING an AOSP rom. to make aosp work 1, you would need screensize and other hardware compatibility, then 2, the rom was never made for htc and 3, there is not flashable zip of the stock rom to base the OS off of, so it would requre alot more work. trust me , cm and and aosp arent much different so dont worry.
russian392 said:
um that isnt quite as easy as you think. porting cm is easier cause our phone has hardware relatives like the HTC One mini which use the same drivers and stuff like that. also our screen size matches the One mini so porting it would be as easy as 1-2-3. it does take time but it will be a hell of alot faster than BUILDING an AOSP rom. to make aosp work 1, you would need screensize and other hardware compatibility, then 2, the rom was never made for htc and 3, there is not flashable zip of the stock rom to base the OS off of, so it would requre alot more work. trust me , cm and and aosp arent much different so dont worry.
Click to expand...
Click to collapse
Since I have no experience porting Android I can't say that you are incorrect, but isn't the binary architecture of applications the same (ARMv7-A Krait instruction set?), the screen is reasonably similar (1280x720 vs 1280x768, or Nexus 4 having 48 extra pixels on the width in portrait mode). Basically, it's not possible to just stick our device-specific kernel (and kernel modules, aka drivers) in there and have everything else just work? Before Android, I had no problems compiling a new Linux kernel for my distro with new options and applications worked just fine.
By the way, HTC promised a 4.4 KitKat update for HTC One Mini which AFAIK is 95% same as our First. Would it be possible to port that ROM? I'd still prefer Nexus though.
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Kendosis said:
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Click to expand...
Click to collapse
Why would there be bluetooth/camera/wifi issues? We would use our own kernel with correctly configured modules. Both First and One Mini kernel source is out, can't we just run a comparison to see what's different? From the look of it they use the same Linux kernel release, so differences should be few (at least no false positives from different module versions). If newer Android builds will use newer Linux kernel, we can add those differences that we will know of after we do the First vs One Mini source comparison.
I think running the patch program would be an easy way to find the affected source files, as files with no differences will generate no patch lines.
Kendosis said:
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Click to expand...
Click to collapse
It's a darn LG. It would like either 1. Take for ever or 2. Impossible
We are using an HTC lol
Sent from my HTC first using xda app-developers app
russian392 said:
It's a darn LG. It would like either 1. Take for ever or 2. Impossible
We are using an HTC lol
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I don't follow what you mean about incompatibility of LG. It's still the same CPU architecture, and neither the Linux kernel nor the Android operating system are the developments of LG. Explain please.
I'm a computer engineer with a bit of custom hardware core development experience for embedded systems running Linux. I just don't see why there's a problem swapping out all the hardware-specific stuff from underneath Android as long as CPU architecture remains the same.
I have years of Linux experience, just not Android-specific.
r00tb33r said:
I don't follow what you mean about incompatibility of LG. It's still the same CPU architecture, and neither the Linux kernel nor the Android operating system are the developments of LG. Explain please.
I'm a computer engineer with a bit of custom hardware core development experience for embedded systems running Linux. I just don't see why there's a problem swapping out all the hardware-specific stuff from underneath Android as long as CPU architecture remains the same.
I have years of Linux experience, just not Android-specific.
Click to expand...
Click to collapse
well.
1. ive seen people try, its not as easy as it seems.
2. think of it as windows. you install it on your pc, it will take another several hours just to download and install various drivers and software for your hardware.
the thing is not just in the android OS. the os should be able to auto adapt itself to any android capable device. BUT we have to consider 1. drivers for the adreno 305 and the snapdragon 400. we also need kernel/baseband capability. the nexus is pretty much a BLANK device with absolutely nothing on it, and they install a stock kernel and stock rom. we would have to go in and make the kernel work, which hopefuly we can just use a ready built one, and then tweak the rom + kernel to fit the harware, whcih will include the capatative side of the screen, and camera, and everything else, and the ram. and that. although technicaly some of it will be there, its not as easy as you might think.
edit
see, ive worked on an ARMv6 device, and its like much harder than an ARMv7 which has alot of similarities. and mind you, im not saying its IMPOSSIBLE, and im not saying its extremely hard. im sure it can be done, but porting cm form a mimic device like the One Mini would be easier than a Nexus 4, or a Nexus 5 at that.
here. maybe this will make my point clear...its not easy eve for big companies, not just for a single person
http://www.androidcentral.com/why-you-ll-never-have-latest-version-android
Wouldn't it be easier and more connivent to port from the HTC one xl? It does have a good amount of great ROMs
abrahammmmmmm_ said:
Wouldn't it be easier and more connivent to port from the HTC one xl? It does have a good amount of great ROMs
Click to expand...
Click to collapse
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
russian392 said:
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
Click to expand...
Click to collapse
I see what you mean, but I wasn't really aware of the great difference of the adreno 225 & 305. When checking it out I only heard there was some very minor tweaks done to the 225 to get the 305. And I'd actually give it a go if it wasn't for how easily this phone bricks, I guess I'll just have to be patient and wait to see what our great devs we've got can whip up for now
russian392 said:
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
Click to expand...
Click to collapse
Modern operating systems are built on the principle of abstraction layers. The *nix kernels place devices as memory pointers on the filesystem tree (they are not files however in the literal sense), so you can swap out hardware and kernel but maintaining the same pointer names and your upper level application won't care at all, as a matter of fact it may not even know it runs on different hardware from before. The "ROM" that you download and flash onto your device is not monolithic, it's made up of components and the Linux kernel and Android OS, and the rest of the applications are separate parts. You should be able swap out the hardware specific layer, otherwise the design of the OS won't be worth a damn.
From user's perspective however "ROM" means something else, it means a specific set of features, be it pre-installed apps, eyecandy (like Sense or Touchwiz), or other miscellaneous bloatware. Basically it's a snapshot of an environment, which defines the user experience. HTC has their own tailored user experience which they ship with their phones like the One mini, with Sense, and probably some carrier restrictions (like custom restricted Wi-Fi tethering on AT&T). HTC first, because it's a product manufactured FOR Facebook, and marketed as A Facebook phone, has a different user experience from typical HTC products. Samsung has their own tailored user experience with their own apps and Touchwiz. Finally LG makes their own phones too, however the Nexus device they make for Google is a Google product, and Google tailors the user experience for their product. I like Google's vision of the smartphone user experience (I had a Nexus One before), and that's what I want to achieve with the current phone. True, that I could have bought a Nexus 4, however HTC's hardware design allows me to do things that are seemingly impossible with LG... Like swapping the IMEI (don't ask).
Not everybody wants their user experience be of HTC or CM flavor. Please be respectful of that. Arguing against wishes of others accomplishes nothing.
I believe it's clear enough that One mini updates can AND WILL be ported to our phone, there is no point to discuss that further in the context of THIS thread.
r00tb33r said:
Modern operating systems are built on the principle of abstraction layers. The *nix kernels place devices as memory pointers on the filesystem tree (they are not files however in the literal sense), so you can swap out hardware and kernel but maintaining the same pointer names and your upper level application won't care at all, as a matter of fact it may not even know it runs on different hardware from before. The "ROM" that you download and flash onto your device is not monolithic, it's made up of components and the Linux kernel and Android OS, and the rest of the applications are separate parts. You should be able swap out the hardware specific layer, otherwise the design of the OS won't be worth a damn.
From user's perspective however "ROM" means something else, it means a specific set of features, be it pre-installed apps, eyecandy (like Sense or Touchwiz), or other miscellaneous bloatware. Basically it's a snapshot of an environment, which defines the user experience. HTC has their own tailored user experience which they ship with their phones like the One mini, with Sense, and probably some carrier restrictions (like custom restricted Wi-Fi tethering on AT&T). HTC first, because it's a product manufactured FOR Facebook, and marketed as A Facebook phone, has a different user experience from typical HTC products. Samsung has their own tailored user experience with their own apps and Touchwiz. Finally LG makes their own phones too, however the Nexus device they make for Google is a Google product, and Google tailors the user experience for their product. I like Google's vision of the smartphone user experience (I had a Nexus One before), and that's what I want to achieve with the current phone. True, that I could have bought a Nexus 4, however HTC's hardware design allows me to do things that are seemingly impossible with LG... Like swapping the IMEI (don't ask).
Not everybody wants their user experience be of HTC or CM flavor. Please be respectful of that. Arguing against wishes of others accomplishes nothing.
I believe it's clear enough that One mini updates can AND WILL be ported to our phone, there is no point to discuss that further in the context of THIS thread.
Click to expand...
Click to collapse
1. SWAPPING IMEI IS ILLEGAL
2. You are correct, htc has some briliant hardware but the nexus 5 is a monster now haha
3. Go get the stock aosp android rom (4.2 or 4.3) then get a kernel for our phones, and flash it....see what you get and PLEASE let me know if it works cause i highly doubt it.
4. The reason why i duscussed the One Mini ports, is because if they are successfull, you can use them as a basis for for other ports like a nexus 4 port. and it doesnt have to be a nexus 4 port, it can be anything else, just at the moment, so far we have ZERO roms that boot, one bricked phone because of a blind build, and what you basicaly want is a blind build of a nexus 4 rom...so if youre willing to put your phone on the line, go right ahead.
russian392 said:
1. SWAPPING IMEI IS ILLEGAL.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2216371
russian392 said:
1. SWAPPING IMEI IS ILLEGAL
2. You are correct, htc has some briliant hardware but the nexus 5 is a monster now haha
3. Go get the stock aosp android rom (4.2 or 4.3) then get a kernel for our phones, and flash it....see what you get and PLEASE let me know if it works cause i highly doubt it.
4. The reason why i duscussed the One Mini ports, is because if they are successfull, you can use them as a basis for for other ports like a nexus 4 port. and it doesnt have to be a nexus 4 port, it can be anything else, just at the moment, so far we have ZERO roms that boot, one bricked phone because of a blind build, and what you basicaly want is a blind build of a nexus 4 rom...so if youre willing to put your phone on the line, go right ahead.
Click to expand...
Click to collapse
1. Depends, still, don't do it. I don't tell others to do it, and won't say how even if asked. But that's a feature I need hence why I choose HTC.
2. More than I need.
3. When I get around it. Fortunately it's possible to unbrick these if something goes terribly wrong (I have the JTAG pinout for this device). I am waiting on a new JTAG box from the team before I release the pinout to public... Unless of course anyone wants to donate a new box or badass logic probe or a very high speed digital oscilloscope.
4. Of course the One mini port will happen before any others because it will take the least time, however not all of us want to use it.
Thread closed to avoid confusion.
Info.
Bobcus Leper said:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother? In AOSP Nougat, the Snapdragon 800 and 801 chips using the Adreno 330 GPU are no longer supported as well. I guess my question is if it will it be possible to reverse engineer OMAP-4 drivers for Nougat that can support the new surface view texture renderer?
Sent from my Asus Nexus 7 (2013) using XDA Labs
Click to expand...
Click to collapse
I MIGHT be possible to support it, but would take a bit of work, offloading that stuff to the CPU (which is just what we need, right?) and all of which is above my skill level.
Bobcus Leper said:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother?
Click to expand...
Click to collapse
The performance problems are probably a mix of slowish eMMC (have to load the precompiled ART files, and they're not exactly tiny), lack of main memory (ART has a bigger memory footprint), and an unsuitable CPU that was outdated when the phone was built, nevermind nowadays. The latter two are what seem to really kill us in CM13; if we're not stuck reclaiming memory, we're saturating the CPU : \
Having Motorola stroll in and develop some up-to-date, optimized drivers sure would be cool, though...hardware is hardware, but good firmware can make a lot out of little.
Nougat is apparently taking a step back and re-introducing JIT execution...so if our resident maintainer does somehow pull off yet another miracle and we get CM14 on here, I'd expect less I/O and memory pressure at the very least. The stock partitions would become viable again too, what with /data/ not being clogged by ART precompiles, and being able to run off them might also offer a (small) performance increase. /system/ is gonna be a tight fit, though...
But using drivers built in two previous, different eras of Android, most of which were for another device...seems like it's gonna take some serious work.
Sent from my Asus Nexus 7 (2013) using XDA Labs
Galaxy Nexus has Nougat!
MWisBest said:
Nougat build is up. No, I have not died, and neither has the Galaxy Nexus.
Decided to take an extra couple days to get this build stable rather than rushing out something that boots and does nothing else, sorry for the delay.
I can't verify the full functionality of the RIL since I don't have a SIM in my GNex these days, so let me know if there's any issues with that.
Everything else should be working well though.
No idea what to do for GApps at this time. I haven't tried them yet.
Download: aosp_n_tuna_2016-08-27.zip
As usual this was a team effort. @Ziyan helped, and @Hashcode (who I thought had died) helped as well.
Click to expand...
Click to collapse
Sent from my Asus Nexus 7 (2013) using XDA Labs
Last time i talked with i Dev about Andoid 7 on the Droid 4, i was told that it would not be possible because of SELinux. But that Info is almost a year old. Maybe someone has more up to date information about this.
1f5 said:
Last time i talked with i Dev about Andoid 7 on the Droid 4, i was told that it would not be possible because of SELinux. But that Info is almost a year old. Maybe someone has more up to date information about this.
Click to expand...
Click to collapse
Thanks! Maybe we should ask @stargo about it. Although, I know stargo likes to surprise people with a new Android version.
Sent from my Motorola XT912 using XDA Labs
Really hoping this old beast will get CM14 due to the coding magic of stargo or some other guys out there.
I recently aquired a completely new Droid 4 from a Verizon reseller in mint condition. Now I never want to live without a slider again!
It is a bit slow, gets hot sometimes and becomes pretty much unuseable with Google Play installed, but who needs that stuff anyways.
Can keep me warm in winter and after replacing stock apps with Naked Browser and Simple Music Player it runs well and fast.
Please don't let this slider die. The only alternative to this device is the Photon Q and this needs to be soldered due to the missing SIM slot.
Bro i think it will have a cm14 for the droid 4
Bro, there say that it is official for the droid 4 to get cm14 check on gammerson .com
Some new info from JooJooBee666.
u.b.o.o.t said:
Hi folks! I had some spare time to setup CM13 build tool chain and - maybe too late for @Septfox - I made a custom kernel with LMK accounting for swap memory, i.e. LMK does only consider memory pages as free which won't require swapping, now. In order to not spam this thread anymore with LMK issues and memory tuning, I created a new thread: http://forum.xda-developers.com/droid-4/development/wip-custom-kernel-lowmemorykiller-t3470411
Click to expand...
Click to collapse
JooJooBee666--
This is cool. I'll test these out here as well. If things look good I'll see about getting LMK changes added to the cm13 kernel and upcoming cm14 kernels (work just began).:good:
Bobcus Leper said:
CM14 confirmed?:fingers-crossed::good:
Click to expand...
Click to collapse
JooJooBee666 --
Not really confirmed (as in no promises it will ever be fully functional as of yet). Just started working on getting things compiling. After that, it's along ways a way from anything usable as there are some new hurdles to overcome thanks to additional lock-downs on SE Linux. So yeah, :fingers-crossed: is right.
Bobcus Leper said:
Thread closed to avoid confusion.
Click to expand...
Click to collapse
Please ask a Moderator to close your thread - otherwise it isn't actually closed....
I've closed it anyway.
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.