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.
Related
I know people are going to hate,this but just wondering is it possible to make a iPhone Rom
Go buy a f***ing iPhone.
Ouch.
That's an interesting question, though. Mac O.S. is basically its own flavour of Unix. Because of this, it makes sense that Iphone O.S. is some derivative of Unix. Since Android is based on the Linux kernel and uses a sort of Linuxy userspace, it might be possible to reverse engineer Iphone O.S., or somehow get the source code (good luck doing this!), patch it and compile it for an A.R.M. prcessor and make a Nexus One boot into it.
I doubt that anyone will really bother, though; there is so much work involved, and you can already buy a Iphone.
It was a question to know if its capable I had a 3gs but I love me nexus and you don't have to be ****
Thank you keet that does sound like a lot but would be pretty cool
ttieder said:
Thank you keet that does sound like a lot but would be pretty cool
Click to expand...
Click to collapse
Why would it be cool?
A couple reasons if you could use the iPhone app store that would be cool because let's face it the iPhone games and some apps are better and you can switch between the 2 best systems and I know if you have a Android phone you don't really like the iPhone a jailbroken iPhone is still a good phone but it needs to be jailbroken
*~* P-u-n-c-t-u-a-t-i-o-n *~*
My brain hurts now...
P.S. I very highly doubt you'd have access to the iPhone's app store, just because you've got a ROM. If this were possible, don't you think someone would have found a way to simple bring that over already!?!?
I just wondering if it was possible thats all
Sure, anything is possible. It essentially comes down to getting the OS to work with the hardware.
but would anyone do it? No
How about a windows 3.11 ROM while we're at it?
Really??????
I only want DOS on my phone. Can someone do this please?!!?!!
No way, let me install Win7 on my N1, please. I want to play Crysis on it.
grainysand said:
No way, let me install Win7 on my N1, please. I want to play Crysis on it.
Click to expand...
Click to collapse
great one!
How did you find this place?
c'mon, plenty of people would be interested in trying an iPhone rom if it were available. however the difference in the chipsets means it probably won't be happening. especially now that Apple makes its own chips.
j.books said:
c'mon, plenty of people would be interested in trying an iPhone rom if it were available. however the difference in the chipsets means it probably won't be happening. especially now that Apple makes its own chips.
Click to expand...
Click to collapse
The A4 is a custom implementation of the ARM A9 processor. Guess which other phone this can be found in...give up? This is also found in the nexus one (Snapdragon). The big difference here is the GPU which is mated with the A9 in appleās design.
Currently, the iPad is the first (and only) product to employ the A4. So for now, porting a rom over wouldn't be limited by the fact it is written against the A4 (A9) but rather they are written against the ARM A8. Not knowing enough about porting I would have to defer to those with larger interest in such a matter but I would think barring any wonky crap apple decided to utilize, a port may not be as impossible as one may think once all of apple's mobile devices are running this new processor.
Having the ability to multi-boot a phone would be insane.
Nexus - custom boot loader (grub) that defaults to the phone's os - android
sd card - debian, winmo7, iphoneOS
Don't like it, don't use it. The ability to do it simply because you can? Sure why not.
McFroger3 said:
I only want DOS on my phone. Can someone do this please?!!?!!
Click to expand...
Click to collapse
Dos games ftw!
liam.lah said:
Dos games ftw!
Click to expand...
Click to collapse
screw all that nonsense. I just want my phone to have a blinking curser.
Or rather lack of it.
I start of by saying, i am not a dev.
But i see that the way rom's is made for Galaxy lack's most of the things that makes custom rom's good, SGS's rom's seem more themes than proper custom rom's.
I have used Nexus and some of the great rom's to that device.
The SGS way to update FW seems to stop all real development?
What do you think?
samsung's drivers are encrypted and this makes developing roms pretty difficult. there can only be roms based on samsung releases. at least this is what i understood .
i am sure that the growing user base of this great phone will bring more attention from great developers ( hi paul ! , who will be able to overcome most of the problems and give us great roms.
The final non-beta firmware from Samsung hasn't even arrived yet! Give it some time!
Custom roms now would be obsolete within one week because of a newer official beta Firmware.
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Did anybody try compiling the sourcecode that was released by samsung to create a flashable working version of the manufacturer Android version that is currently running in our phones?
If that is possible, and we do have the source code from samsung, I don't see why it would be impossible to get at least a vanilla AOSP 2.1-update1 running on our galaxies.
The encrypted (or closed source drivers) can be linked as binaries to the new AOSP build running on top of Samsung's kernel (which we do have the source code to).
Side question, anybody knows how to flash the phone once you got all source code by samsung compiled ? I know we end up with a zImage, possibly a system.img.. can you create Odin files with these easily ? any thoughts?
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Click to expand...
Click to collapse
same here. previous n1 user, got sgs just after google announced no n2 wil be available.
just took some actions to make things smoother for me :
1. launcher pro
2. dialer one
3. handcent sms
i used them all on n1 and now i do on sgs. its all good again . still, untill froyo hits us i think i will still miss n1's speed. also, i think after froyo hits us, we will get some more roms and goodies for our phones.
what exactly is a vendor tree? and how would it be able to get around the driver issue which is apparant to the SGS?
Some info on the .rfs files that samsung uses:
http://movitool.ntd.homelinux.org/trac/movitool/wiki/RFS
Merging into AOSP
It seems like good idea to have the scripts merged into AOSP tree that support building stock ROMS for samsung galaxy s, with binary-only files being downloaded directly from the device (if I'm not mistaken, this is how one can build froyo for N1 from source now).
From someone else experience: would the patches that add vendor-specific support for SGS be accepted into AOSP tree? Are there known blockers for this?
Hmm.. rom development is quite sluggish due to the firmwares that are being released!
But i really don't care! the original rom is fine with WJG5!
I just use Launcher Pro and widgets to make it better! Speed is ok!
bratfink said:
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
Click to expand...
Click to collapse
This isn't fragmentation though, this is exactly what Google wanted Android to be - a base for phone manufacturers to lay their own tweaks on top of. HTC, Motorola, Samsung etc don't just want to be differentiated by how their handset looks, they want to put their own stuff on there too. Previously each had their own OS (Symbian, UIQ etc.) that took years of development time and was very slow moving. Google provided Android as a quick route to market for a phone, the manufacturers didn't really have to worry too much about the OS and then get lots of apps for free.
The thing is, the vanilla apps are a bit.. basic. The standard music player is fine, it works and does what it says on the tin. The standard contacts is fine again etc. Makers can ship a ROM based on vanilla Android and it would be good to go, but if they can improve upon the apps and brand it slightly more then all well and good.
But it's not fragmentation. Android is a base. A starting point. It's not meant to look exactly the same on every device, but it's meant to work exactly the same as much as possible. These manufacturers get a stable, standard, capable phone OS for free, which to them is awesome. It saves them so much time and is ultimately why eventually there will be nothing but Android on devices. It's the Mac vs PC all over again - cool but closed and restricted vs ubiquitous free-for-all.
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
dirk1978 said:
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
Click to expand...
Click to collapse
Didn't they have the source for 1.6's camera drivers? At least then they had a base to start from. That is not true with Samsungs drivers.
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
dirk1978 said:
it's meant to work exactly the same as much as possible.
Click to expand...
Click to collapse
It's when it doesn't work, it's very very annoying. How long do we have to wait for the Samsung music player to enable scrobbling? Sure I can use a different app from the Market - meaning Samsung wasted effort on their own Music app, why didn't they build on the AOSP version which does support scrobbling and iSyncr, etc because they use standard API or whatever so these other programs can read the state or whatever they need to do.
Same with dialer and contacts - on Launcher Pro, pressing the default Contacts icon - won't get you anything except maybe a FC :-(
The AOSP Desk Clock - where is that? If I install a clock from Market then I have two different Alarm daemons which is a waste of everyone's time when the default Clock in AOSP Eclair is fine and - more importantly - compatible with stuff and API calls.
Then all the other stuff that may or may not be Samsung stuff - the DRM, the Device Management, the Samsung Account - given the option I just don't want that stuff.
I'm intending to flash JG5 (from factory shipped JF3) which may increase performance but presume won't make these other problems go away.
I'm really happy with the hardware - but currently I am dissatisfied with the software and "Samsung knows best". For me, personally, Google knows best (and I bet they have data on me to prove it!), so I really want to see Froyo AOSP version for the Galaxy. That day may come, or it may not ...
I know I know, "can't please all of the people all of the time"
PAO1908 said:
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
Click to expand...
Click to collapse
Right now the question for me would be "do I recommend switching from Samsung OS from Froyo" - my answer would be no, unless:
1. better multitouch is important to you (better for gaming, no axis mess-up)
2. 4" screen is important (I do really like the Samsung screen)
3. Better built-in audio quality is important (the Galaxy is noticeably louder than the N1 and I think it may have a better A/D sampler too)
So fully recommend switching for hardware, UNLESS you can't live without Froyo.
I can live with the SGS shortcomings. Well, for a few months anyway ... and even if AOSP never comes there are alternatives in the Market but does mean you have to ignore the Samsung stock apps depending what you want to do (which means added complexity to your life, which I don't always have time to deal with!)
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
Do you have any proof that the drivers are actually locked down in any way?
I can see the source of all the modules provided by samsung, just 3 of them (pvrsrvkm, s3cbc and s3clcd) are just precompiled, and if you check the info they are GPL.
Am I missing something?
@miker71
Thanks a lot !
This is a general question from me trying to understand things better. Before the D4 I had a samsung stratosphere. Completely unlocked bootloader with full capability to flash custom ROM/kernel images. Despite this no AOSP ROMs could be build due to lack of driver sources. It was the same situation with the Epic 4G. The Droid 4 on the other hand had the bootloader locked with the key thrown away. Despite this CM9 and other AOSP ROMs are up and nearly fully operational, even with ICS booting on GB kernels. What makes this possible on D4 but not the stratosphere?
My guess is that driver software is available for the D4. This is due to the fact that Motorola uses parts from other OEMs (TI CPU ect) with public drivers. Samsung on the other hand uses their own proprietary parts and keeps the drivers private. Is this an accurate assessment?
It would seem then that the most important thing to making development possible for a phone (apart from popularity) is driver availability, NOT whether or not the bootloader is unlocked. Is that true? Regardless, I will probably steer clear of samsung for future android purchases. HTC still seems best and motorola acceptable. If only HTC still made high end QWERTYs.
Usually devs just pull the proprietary files off the phone and use it in the compile/builds. This has been going on for Motorola phones since the original Droid.
Sounds like no one invested in seeing what proprietary files were needed from the Stratosphere or Epic 4G.
Public AOSP code mixed with copying in private/proprietary files is how most ROMs are made. The higher the user base of a device, the higher the development activity and the larger number of devs finding out what all is needed to be pulled from the stock device to compile a fully functional ROM.
Since some proprietary files are used....you need them for the same version OS you are building, ie...use stock phones ICS drivers for ICS builds or stock phones GB drivers for Gingerbread builds. You can sometimes hack drivers to work but with lots of limitations. Also drivers depend on the kernel so a matching kernel is needed......requiring the device to have the needed kernel level or an unlocked bootloader to be able to replace the stock kernel.
We wont be seeing an unlocked bootloader? Ever?
Sent from my DROID4 using xda premium
twizzles said:
We wont be seeing an unlocked bootloader? Ever?
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
All signs point to no...we will never see an unlocked bootloader on the current Motorola devices.
With Google owning Motorola Mobility and already replacing MM CEO with one of their own from Google........it's possible future devices may be unlock capable.
Current devices....no, not ever.
The first locked bootloader on a Motorola droid was the Droid 2. It still has not been unlocked, hacked, cracked, etc... How long has it been out?
Motorola released a special Razr Dev model with an unlockable bootloader...retail price, zero warranty, nothing you do on it would transfer over to the normal Razr or Razr Maxx.......so why would anyone buy it? Great PR for them to say "see..we released an unlockable device and no one bought it".
Well that just sucks. Thank you for the info
Sent from my DROID4 using xda premium
I have to say, I don't mind not having an unlocked bootloader. I had the Galaxy Nexus and ran multiple different setups on it. The radio still sucked though. With the Droid 4, I don't feel the need to do a lot of hacking. The phone is well built, radio is awesome, it just works.
GermanGuy said:
I have to say, I don't mind not having an unlocked bootloader. I had the Galaxy Nexus and ran multiple different setups on it. The radio still sucked though. With the Droid 4, I don't feel the need to do a lot of hacking. The phone is well built, radio is awesome, it just works.
Click to expand...
Click to collapse
I kind of agree with you for the most, but still I prefer the option and think we should have it as an option. It's one way to keep a device relevant throughout your 2 year contract. For example....the Droid 3. I have one, bought online day of release. In less than a years time it has become a non-supported, forgotten device from Motorola. The locked bootloader prevents devs from picking apart the Droid 4 leaked ICS kernel and compiling one with Droid 3 specs (less RAM, etc..) and bringing a fully functional ICS build to the Droid 3. Unlocked...that would be possible.
JKingDev said:
This is a general question from me trying to understand things better. Before the D4 I had a samsung stratosphere. Completely unlocked bootloader with full capability to flash custom ROM/kernel images. Despite this no AOSP ROMs could be build due to lack of driver sources. It was the same situation with the Epic 4G. The Droid 4 on the other hand had the bootloader locked with the key thrown away. Despite this CM9 and other AOSP ROMs are up and nearly fully operational, even with ICS booting on GB kernels. What makes this possible on D4 but not the stratosphere?
Click to expand...
Click to collapse
I, as well, went from the Stratosphere to the Droid 4. I love my Stratosphere and still have it, but the lack of development on it is just down right aggravating. That is why I took it upon myself to learn how to compile a kernel to provide everyone with root and recovery for it. Otherwise we wouldn't have the ROMs we have for it now. If it wasn't for the Droid Charge using the exact same dev board as the Strat, I doubt we'd even have that much. I had to take the Charge build of CWM and packed it in a Strat kernel and tweaked the scripts, thank god at least that worked.
JKingDev said:
My guess is that driver software is available for the D4. This is due to the fact that Motorola uses parts from other OEMs (TI CPU ect) with public drivers. Samsung on the other hand uses their own proprietary parts and keeps the drivers private. Is this an accurate assessment?
Click to expand...
Click to collapse
I am not sure about the Motorola drivers, but you are right about Samsung. The first time I compiled the kernel, I was missing 11 modules. I couldn't figure out what I did to keep them from being compiled... and then I learned the sneakiness Samsung uses to get around releasing the source, they compile the kernels for the file system and radios and dynamically link them in the init.rc script. Apparently a lot of them do this, actually.
JKingDev said:
It would seem then that the most important thing to making development possible for a phone (apart from popularity) is driver availability, NOT whether or not the bootloader is unlocked. Is that true?
Click to expand...
Click to collapse
Actually both are true to some extent, with a locked bootloader you are stuck with OEM signed boot images and can't recompile the kernel to your own needs, or compiling one with ro.secure = 0 so you get root access in adb (which is how I rooted the Stratosphere). Then you need the drivers to talk to the hardware too. Without them, you'd need to reverse engineer them or use the currently complied ones (also, like we did with the Strat). Finally, you have to have the source for the RIL (Radio Interface Layer) in Android so Android as an OS knows how to talk to the drivers to make calls, send messages, use data, etc. THIS is where we are currently hung up from using AOSP on the Stratosphere. I know work is being done on the RIL for the Charge and since its the same board, we might get lucky and be able to reuse most (if not all) of the same code and bring new life to it. But, I wasn't getting my hopes up and decided to get a D4 anyway.
JKingDev said:
Regardless, I will probably steer clear of samsung for future android purchases. HTC still seems best and motorola acceptable. If only HTC still made high end QWERTYs.
Click to expand...
Click to collapse
You and me both. I was in love with the keyboard on my HTC Touch Pro 2 and wish they'd release something like that running Android on Verizon with newer hardware. Closest they had to a QWERTY on VZ was the Merge, and they botched that up from the gate. I also have the Rezound and am trying to design a way to attach a sliding keyboard to the back battery cover to give me something closer to what i have been wanting in a phone.
I think us QWERTY loves on VZ are at the mercy of Motorola and Motorola alone with the original Droid line of sliders.
KnightCrusader said:
I, as well, went from the Stratosphere to the Droid 4. I love my Stratosphere and still have it, but the lack of development on it is just down right aggravating. That is why I took it upon myself to learn how to compile a kernel to provide everyone with root and recovery for it. Otherwise we wouldn't have the ROMs we have for it now. If it wasn't for the Droid Charge using the exact same dev board as the Strat, I doubt we'd even have that much. I had to take the Charge build of CWM and packed it in a Strat kernel and tweaked the scripts, thank god at least that worked.
I am not sure about the Motorola drivers, but you are right about Samsung. The first time I compiled the kernel, I was missing 11 modules. I couldn't figure out what I did to keep them from being compiled... and then I learned the sneakiness Samsung uses to get around releasing the source, they compile the kernels for the file system and radios and dynamically link them in the init.rc script. Apparently a lot of them do this, actually.
Actually both are true to some extent, with a locked bootloader you are stuck with OEM signed boot images and can't recompile the kernel to your own needs, or compiling one with ro.secure = 0 so you get root access in adb (which is how I rooted the Stratosphere). Then you need the drivers to talk to the hardware too. Without them, you'd need to reverse engineer them or use the currently complied ones (also, like we did with the Strat). Finally, you have to have the source for the RIL (Radio Interface Layer) in Android so Android as an OS knows how to talk to the drivers to make calls, send messages, use data, etc. THIS is where we are currently hung up from using AOSP on the Stratosphere. I know work is being done on the RIL for the Charge and since its the same board, we might get lucky and be able to reuse most (if not all) of the same code and bring new life to it. But, I wasn't getting my hopes up and decided to get a D4 anyway.
You and me both. I was in love with the keyboard on my HTC Touch Pro 2 and wish they'd release something like that running Android on Verizon with newer hardware. Closest they had to a QWERTY on VZ was the Merge, and they botched that up from the gate. I also have the Rezound and am trying to design a way to attach a sliding keyboard to the back battery cover to give me something closer to what i have been wanting in a phone.
I think us QWERTY loves on VZ are at the mercy of Motorola and Motorola alone with the original Droid line of sliders.
Click to expand...
Click to collapse
Thanks for the replies. It is interesting stuff. And KC I definitely appreciated your work on the Strat. So I guess it really was a question of popularity being the problem for stratosphere. I definitely know it wasnt the most popular device but it also seemed like reverse engineering drivers for the Samsung devices was so much harder. The charge was relatively popular and years later the RIL has still not been successfully reverse engineered. All the moto devices get cracked so quickly. Is it only because they are more popular, or are there other reasons that make them easier to hack? Thats what leads me to think maybe it's samsung's use of proprietary hardware that makes things more difficult. Does that have something to do with it?
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?
StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.
StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.
H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that 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.