Related
I am trying to get the AT&T stuff out of my phone, and to have updates and bug fixes every now and then.
Untill now, found only the safestrap but i did not find any ROM that seems to have android 4.4.4. Is there anything like cyanogenmod?
eliuha said:
I am trying to get the AT&T stuff out of my phone, and to have updates and bug fixes every now and then.
Untill now, found only the safestrap but i did not find any ROM that seems to have android 4.4.4. Is there anything like cyanogenmod?
Click to expand...
Click to collapse
Can't use a ROM with custom kernel, yet. I recommend 4.4.2 and HyperDrive 19. It works really well, has a nice installer with lots of extras, good battery life... All around, it's a really well built ROM.
eliuha said:
I am trying to get the AT&T stuff out of my phone, and to have updates and bug fixes every now and then.
Untill now, found only the safestrap but i did not find any ROM that seems to have android 4.4.4. Is there anything like cyanogenmod?
Click to expand...
Click to collapse
As someone who was blindsided and crestfallen to find out about the locked bootloader (no cyanogenmod for us,we're S.O.L.) let me make some recommendations to at least get some of that stock android (i.e. cyanogenmod) feel back (I'm assuming you're already rooted, if not, google towelroot and follow directions):
Get SafeStrap
Flash this mod to drastically improve battery life and general performance
Get rid of KNOX
De-Odex your stock ROM (it's easy and allows a lot more customization)
And enter the exciting world of SMALI editing. This takes a little practice, and still doesn't afford the full freedom of CM, but you can customize the look and feel of your phone, still feel like a champ, and just learn about android in general. I've used a bunch of these successfully, with virtually no prior coding experience. E.g. I hated those battery/charger cover notifications, thanks to this thread, they're gone and not coming back.
Also, get rid of the stock launcher and replace it with NOVA launcher. More customization, smoother, better performance, looks more like CM. You can (and should) use Titanium Backup to either freeze or uninstall bloatware (at the very least any app with AT&T in the name).
AdAway is your friend.
Quick and easy mobile data toggle mod
I would recommend the Knox_Out zip in my post here since the one in the OP hasn't been updated since July and removes an apk you might actually need.
Good Afternoon, people.
I am brazilian and I have a smartphone that did not get into US and European market. It's name is "Motorola D3" and the number associate to it is "XT920".
Motorola Brazil were suposed to provide de newest rom for this device (marketing promissess). It took they almost 1 year to launch the Android Kitkat version 4.4.2.
The problem is: We want the Cyanogenmod in our device and all the newest ROM's.
That been said, I start to study to try yo port or Build a AOSP ROM to XT920 and, therefore, a CM11.
No threads on "how to port / build" a rom for a New device went trhough this problem. This device runs as a Mediatek MTK6577. I've seen that the kernel for this processor was released, but I don't know how to handle the kernel with the device and ROM properly.
Another doubt is: what is the difference between port and build a ROM? I've seen videos of porting and building and it is not clear to me.
I have reached the point where I have to download the drivers, but, in the tutorial the person was dealing with a NEXUS, wich is much easier to build, since it have a native android support.
Anyway, I want to keep this project going, and I really need some help with this questions.
Thankyou
digo_santista said:
This device runs as a Mediatek MTK6577.
Click to expand...
Click to collapse
You're screwed. MTK devices are extremely nightmarish to work with. Their kernel source is a mess and the platform source is an even bigger mess.
Even people who have had access to a complete OEM source code tree for an MT6589 device didn't succeed in getting the hacks to play nice with an AOSP source tree.
Android One has helped somewhat with devices that are released as part of the One program, but non-One MTK devices are still a nightmare.
The process of doing an AOSP bringup for a new device isn't particularly well defined because it is different for every device in existence. The only way to learn is by doing.
It helps a lot if a device with a similar chipset to yours is supported by whatever project you're trying to work with - for example most mid-to-high-end Qualcomm chipsets are not very difficult to work with. But MTK devices were nearly impossible to support with AOSP-derivative projects prior to One, and even after One, it seems like only Android One devices are "clean" enough to leverage Google's improvements to MTK support.
:/ should I waste more time or just drop it?
Entropy512 said:
You're screwed.
Click to expand...
Click to collapse
What should I do? I just quit without trying? I understand that this is a huge problem. But, if I decide to take the chalenge, is there a chance to succeed?
I am trying to figure this out and I didn't found an answer to this question: can I use the kernel that is packed with my stock ROM (provided by motorola) to build or port a CM11 ROM?
Sorry to bother, but I is really keeping me up at night
Regards,
Cassio Rodrigo
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
MrBrady said:
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
Click to expand...
Click to collapse
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
simms22 said:
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
Click to expand...
Click to collapse
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
MrBrady said:
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
Click to expand...
Click to collapse
well, first off, aosp and stock are two completely different roms. stock roms also have closed source code included, where aosp roms dont have that code included, so they WILL run differently, as two different roms should.
---------- Post added at 03:20 PM ---------- Previous post was at 02:58 PM ----------
anyways, the answer to your question is really simple.. better is whatever is better for you,personally. to you, image based roms are better. for me, aosp is better.
as a real answer of which is better doesnt exist, its all which is better for you(or me).
Had you followed the rules you would know threads like this don't stay open long.
There is no best. Or better. There is only what works for you.
Most people that get a nexus device do it for the active development. Which does mean some bugs here and there, but that is the fun. In learning, finding and killing bugs. If you got a nexus for any other reason you really are not doing yourself any favors.
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Q9Nap said:
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Click to expand...
Click to collapse
Factory firmware for Shamu was 5.0. Thats what it shipped with. Their was never a 4.X for Shamu.
As for 4.4.4, anything is possible. Will you be able to find a dev willing to work on it? Most likely not. Makes no sense other than the challenge of it. Might be a project you can take up yourself if you like. There are tons of tutorials, information, and devs around to give advice.
Q9Nap said:
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Click to expand...
Click to collapse
sure, its possible.. do you havd a kitkat driver for the n6 to make it work? if not, then itll never work. btw, google never released the drivers.
christianpeso said:
Factory firmware for Shamu was 5.0. Thats what it shipped with. Their was never a 4.X for Shamu.
As for 4.4.4, anything is possible. Will you be able to find a dev willing to work on it? Most likely not. Makes no sense other than the challenge of it. Might be a project you can take up yourself if you like. There are tons of tutorials, information, and devs around to give advice.
Click to expand...
Click to collapse
Yes, Shamu shipped with 5.0, but there is a 4.4.4 factory firmware file that is available for use by repair centers.
I've tried it, and it is a very minimal build. It isn't worth using as a daily driver at all.
I'm sure I could repo sync and compile aosp 4.4.4, but I don't want to take the time and effort if it won't work lol.
Besides the lack of 4.4.4 proprietary binaries, there is also no official 4.4.4 kernel source, so I'm basically wondering if it could work with 5.0 proprietary binaries and kernel source?
simms22 said:
sure, its possible.. do you havd a kitkat driver for the n6 to make it work? if not, then itll never work. btw, google never released the drivers.
Click to expand...
Click to collapse
Right, the lack of 4.4.4 drivers and kernel source are my main concern as far as whether it would work.
I'm wondering whether it would be possible to extract the necessary driver files and kernel from the factory buid?
Q9Nap said:
Right, the lack of 4.4.4 drivers and kernel source are my main concern as far as whether it would work.
I'm wondering whether it would be possible to extract the necessary driver files and kernel from the factory buid?
Click to expand...
Click to collapse
theres no kitkat driver, period. if there is, google has it. no, you cant extract a past driver from a newer os.
simms22 said:
theres no kitkat driver, period. if there is, google has it. no, you cant extract a past driver from a newer os.
Click to expand...
Click to collapse
I have a 4.4.4 pre-release build from Motorola; would it be possible to extract the drivers and use its kernel/boot image?
Pre-release build of what from Motorola? Unless that pre-release build is specifically for the Nexus 6, you won't be able to use its kernel with the device.
*removed*
Q9Nap said:
I have a 4.4.4 pre-release build from Motorola; would it be possible to extract the drivers and use its kernel/boot image?
Click to expand...
Click to collapse
nope. drivers are very device specific. it has to be a nexus 6 driver, or you will not get any of the software to work with the hardware and with the physical device.
simms22 said:
nope. drivers are very device specific. it has to be a nexus 6 driver, or you will not get any of the software to work with the hardware and with the physical device.
Click to expand...
Click to collapse
Ok, I'll say it again; I have official 4.4.4 Motorola firmware for the Nexus 6. See the build.prop in the previous post.
Is it possible to extract the drivers and kernel from this and include in AOSP 4.4.4?
It is factory test firmware and isn't really viable to use as a daily driver, which is why I want to use parts from it to build AOSP.
Q9Nap said:
Ok, I'll say it again; I have official 4.4.4 Motorola firmware for the Nexus 6. See the build.prop in the previous post.
Is it possible to extract the drivers and kernel from this and include in AOSP 4.4.4?
It is factory test firmware and isn't really viable to use as a daily driver, which is why I want to use parts from it to build AOSP.
Click to expand...
Click to collapse
you can try, thats the best that i can say..
As @simms22 already said, you can try it. However, according to the build.prop, ro.product.model is an XT-1080,which is a Droid Ultra. The hardware for the Droid Ultra is completely different from the N6, with specs more applicable to a Samsung Galaxy S3, and thus its drivers and kernel will both be different. Neither will work on the Nexus 6.
I'm sorry, but I highly doubt this is a genuine Nexus 6 pre-release ROM. Posting the build.prop is insufficient proof, as the build.prop can be easily edited to have it say whatever you choose. You'll have to find another way to persuade the audience.
I'm not trying to persuade anyone, lol. I'm just asking whether it's theoretically possible or not.
You are welcome to have access to the full firmware if you like, sheesh.
Why would I bother faking a build.prop?
It's not, as the Droid Ultra hardware is totally different. As to why anyone would want to fake a pre-release ROM, your guess is as good as mine. But at least you provided something when asked, unlike one guy in the S4 forums who claimed he could reset the Knox efuse after it was tripped, something not even Samsung can do.
Strephon Alkhalikoi said:
It's not, as the Droid Ultra hardware is totally different. As to why anyone would want to fake a pre-release ROM, your guess is as good as mine. But at least you provided something when asked, unlike one guy in the S4 forums who claimed he could reset the Knox efuse after it was tripped, something not even Samsung can do.
Click to expand...
Click to collapse
This is not for droid ultra. Yes, one line in the build.prop says xt1080, but everything else says shamu. Apparently, xt1080 was the working model number during testing.
For you and any other doubters, here ya go:
https://drive.google.com/file/d/0B-53iD-71B3iMElKNWdybC1aanc/view?usp=sharing
Wow, this thread is hilarious.
First off, there is no such thing as a driver that is linked specifically to a version of Android. The driver is between LINUX and HARDWARE.
While newer versions of Android may be more demanding of the kernel, they are not intrinsically tied together. You can run Android 2.0 on Kernel 4.6 if you want. Nothing is going to stop you from doing that.
Now the place where you could run into some stickyness, is in the **hardware abstraction layers**. These are not the drivers. These are the bits of code that talk Android API on one side, and Linux on the other side. Most of the HALs are open source, so could be converted if need be.
Most of the HAL changes are things being added into the new versions that didn't exist in the old. As a result, in most cases, you could take a 5.0 HAL and stuff it into a 4.4 system image -- and it should work.
But the big question is.... why would you ever want to do that? 4.4 is obsolete and dead. LEAVE IT BE!
doitright said:
Wow, this thread is hilarious.
First off, there is no such thing as a driver that is linked specifically to a version of Android. The driver is between LINUX and HARDWARE.
While newer versions of Android may be more demanding of the kernel, they are not intrinsically tied together. You can run Android 2.0 on Kernel 4.6 if you want. Nothing is going to stop you from doing that.
Now the place where you could run into some stickyness, is in the **hardware abstraction layers**. These are not the drivers. These are the bits of code that talk Android API on one side, and Linux on the other side. Most of the HALs are open source, so could be converted if need be.
Most of the HAL changes are things being added into the new versions that didn't exist in the old. As a result, in most cases, you could take a 5.0 HAL and stuff it into a 4.4 system image -- and it should work.
But the big question is.... why would you ever want to do that? 4.4 is obsolete and dead. LEAVE IT BE!
Click to expand...
Click to collapse
This is the kind of response I was looking for, thank you!
Yeah I know KK is obsolete; the main reason I am interested, besides theoretical curiosity, is the holo dark ui; really don't like the bright material white ui, and the material dark ui doesn't look that great either.
I know I can use cmte, layers, or substratum to install a dark ui theme, but I haven't found a theme yet that doesn't have issues and/or inconsistencies, and they don't look as good as og holo dark imo.
Anyway, it definitely sounds like more trouble than it's worth, lol.
i can only find one derpest download here
https://sourceforge.net/projects/derpfest/files/
can a custom rom like this be loaded onto a samsung note 4 SM910F, if someone has to try and its not suitable will it just not load, bits of it not work, or brick the fone. I nhave twrp installed so as long as I can get back to twrp I can go back to another rom.
Senior member please help, my knowledge is low, and really trying to understand this.
.....Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01, and where everything important, CAMERA bluetooth etc all work. If so may I have a link please. THANKyOOOOOO
I doubt it will be compatible with the Galaxy Note 4 but you could do a search from the link below. Good luck
https://derpfest.org/devices
gwm121 said:
i can only find one derpest download here
https://sourceforge.net/projects/derpfest/files/
can a custom rom like this be loaded onto a samsung note 4 SM910F, if someone has to try and its not suitable will it just not load, bits of it not work, or brick the fone. I nhave twrp installed so as long as I can get back to twrp I can go back to another rom.
Senior member please help, my knowledge is low, and really trying to understand this.
.....Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01, and where everything important, CAMERA bluetooth etc all work. If so may I have a link please. THANKyOOOOOO
Click to expand...
Click to collapse
There are 2 types of ROMS for the 910F:
a. stock - original mage by Samsung
b. custom roms AOSP based
Type b can be also divided in 2 -
b1. custom ROMs AOSP based
b2. custom ROMs ported from stock from other Samsung devices - but that involves HUGE amount of knowledge, time and resources spent to get them to work.
I suggest you go and READ and get as much info as you can to be able to understand these terms.
It's not hard, depending on your time and will.
As for your questions of derfest - it is an AOSP based ROM, but if no developer has built it on the official site, it's pretty hard to ask for it for the 910F. I saw no Samsung there.
"can a custom rom like this be loaded onto a samsung note 4 SM910F" - yes, there is Lineage, RR, Havoc, AEX, etc - go check them in the dedicated section of the forum for your device.
"Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01"
There are pie style ROMs (as said above, go check them) faster than android 6. Android 6 was whatever you want, but not fast.
However, there's no pie ROMs ported from other Samsung devices to 910F.
Good luck.
note 4 sm910F custom roms fast stable .. and thankyou
Thank you for reply, appreciated. yes reading as much as possible.
I have rooted, loaded twrp, via odin,
and loaded threee of the four custom roms you mention, Lineage, RR, Havoc, and will look for AEX,
rr res remix is running now, however is slower than android 6.01, 55 seconds for cold start and generally a little laggy, and the camera intermiitntly freezes. Im reading everything I can, but dont understand if the camera problem is , ... a bug on rr, a bug on some camera apps including the one supplied with pico gapps,, an app ive loaded interfering with it or what. Ive seen comments about dirty load and clean load, and wipe with twrp default suggestions before loading rr,.
The reason for wanting a custom rom, is its nice to have both my fones with similar operating systems, the method of getting to app draw, unlocking fone swpe direction, accessing swype down shade are so different android 6 to pie,
and having apps like sonos being able to run
and possibly volte running tho no rom so far has done this.
If the disadvantages of a custom rom outweigh android 6 Ill look at going back to stock, Samsung wont supply the firmware but will do it at their shop!!
Android 6 had one feature better than pie I think, shade accessed by one sype down, and the initial screan names like wifi data in words beneath each item, thats so helpful no pie type rom so far has this
Again big thankyou for reply.
w41ru5 said:
There are 2 types of ROMS for the 910F:
a. stock - original mage by Samsung
b. custom roms AOSP based
Type b can be also divided in 2 -
b1. custom ROMs AOSP based
b2. custom ROMs ported from stock from other Samsung devices - but that involves HUGE amount of knowledge, time and resources spent to get them to work.
I suggest you go and READ and get as much info as you can to be able to understand these terms.
It's not hard, depending on your time and will.
As for your questions of derfest - it is an AOSP based ROM, but if no developer has built it on the official site, it's pretty hard to ask for it for the 910F. I saw no Samsung there.
"can a custom rom like this be loaded onto a samsung note 4 SM910F" - yes, there is Lineage, RR, Havoc, AEX, etc - go check them in the dedicated section of the forum for your device.
"Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01"
There are pie style ROMs (as said above, go check them) faster than android 6. Android 6 was whatever you want, but not fast.
However, there's no pie ROMs ported from other Samsung devices to 910F.
Good luck.
Click to expand...
Click to collapse
gwm121 said:
Thank you for reply, appreciated. yes reading as much as possible.
I have rooted, loaded twrp, via odin,
and loaded threee of the four custom roms you mention, Lineage, RR, Havoc, and will look for AEX,
rr res remix is running now, however is slower than android 6.01, 55 seconds for cold start and generally a little laggy, and the camera intermiitntly freezes. Im reading everything I can, but dont understand if the camera problem is , ... a bug on rr, a bug on some camera apps including the one supplied with pico gapps,, an app ive loaded interfering with it or what. Ive seen comments about dirty load and clean load, and wipe with twrp default suggestions before loading rr,.
1. camera can't be as stock - original blobs (coding) of the app are Samsung proprietary, not open source, it's very difficult to have the same quality
2. coming from stock to custom ROM it's always recommended to format data (wipe is not enough) - that includes the internal storage, so save it before you do it
The reason for wanting a custom rom, is its nice to have both my fones with similar operating systems, the method of getting to app draw, unlocking fone swpe direction, accessing swype down shade are so different android 6 to pie, and having apps like sonos being able to run and possibly volte running tho no rom so far has done this.
these are your preferences, no comment here - however, volte is quite a specific thing, not all developers are bothered/care about it - so again, take it or leave it
If the disadvantages of a custom rom outweigh android 6 Ill look at going back to stock, Samsung wont supply the firmware but will do it at their shop!!
you can go back to stock if you would have made a back-up of stock with the fresh installed TWRP
or use Odin to flash with PC
Android 6 had one feature better than pie I think, shade accessed by one sype down, and the initial screan names like wifi data in words beneath each item, thats so helpful, no pie type rom so far has this
Again big thank you for reply.
Click to expand...
Click to collapse
No problem glad I could help.
Have a nice day.