Related
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
Hello everybody, It´s been like a week since I last posted, a lot of things went wrong in my house and I somehow lost all my computers
anyway, back in business again, Last night I had to install the stock Sprint GB sbf, to my surprise it worked Really, Really good.
I´ve had a Defy+ and a Milestone 2, And I remembered having lots of issues with modding aka. no signal, wifi issues (like the cm7 and 9 ones) data issues, system lags, poor battery life, kernel errors on development, Overclocking settings not being saved, recovery mess-ups, and a lot of depicable stuff, most of all kernel-related.
Anyway, last night I flashed the stock rom over cm7 and noticed a real speed, functionality and battery boost, so I thought of just theming, de-bloating and optimizing the stock Sprint ROM.
Please follow me here:
We will never be able to flash custom kernels (not w/o the help of a reaaaaal good DEV)
CM9 &10, though they are eye-candy, are based actually on Gingerbread kernel, so no new features can be added besides the ones you can get withg new apps.
CM7, though stable, lacks the performance and functionality of the stock rom.
Finally, the stock rom as I said, (and I´ve tested TONS of ROMS in different motorola devices) is the one with the best responsivenness, snappiness and battery life, plus It's almost clean (eg. bloatware is easily removed.)
How will it be done?, you may ask.
Well Our first step, will be deodexing the stock GB SBF.
After deodexing we will be optimizing the build.prop on our phone, to trick apps into installing on our phones, and to make some quick optimizations.
Once we have deodexed our rom, we will be able to run,autorun and theme /system/apps.
Apps like Gnow, the statusbar and other tweaks can be easily (RELLY EASY) ported to deodexed ROMS
So this is the challenge guys, Let´s build our own stockcustom ROM.
So far I´m re-flashing stock sprint GB to continue testing only the essential apps, so we can build from there.
And just for a tease; here is my latest build.prop, with some tweaks and tricks taken from other roms and my personal experience, just make sure you have root access, fire up a file explorer and replace your build.prop
Please Refer to next post for links on how to maybe help me with deodexing the full rom.
And please, developers, dont take this as a shady move towards your development, I just think that the best way to make something is to start from scratch..... there are too many source files, modded files and crap files on cm7,9&10 specially when not officially supported (Because everybody messes with the files and re-distributes them, so a lot of clutter and unneeded files, references and code are injected on some releases....)
So my friends, we have a common goal, By now I have succesfully overclocked/undervolted the phone to 1350/233 mhz (not on recovery!!)
I´ve deodexed system/framework/
and Im stuck trying to deodex system/apps/
Xprt Owners of the world, please come on over here, we can do this...
I´m an architect/artist so I really want this to have a sleek look, but not copying a specific stock look, if you know what I mean....
From now on refer to the "wished features post" for features you´d like
And now my final statement:
Though it IS possible to compile JB or ICS from source to our phones, my experience with this somehow outdated android motorolas, is that you will not get significant performance boosts or super cool functions with new software. The only way to get this functionality is by upgrading the kernel which I again declare IS NOT POSSIBLE on our phone. CM9 and 10 my look like JB and ICS, but run straight off a GB kernel.
Yes you will get a lot of new stuff like menus and graphics, but the functionality will be the same, plus all the eye candy will trade off your new features with lags and possible errors.
Software is built in time with devices, and it doesn´t matter how much you say "but the hardware is capable of more!!", incremental software updates "ignore" some HW features, so they have to be forced or modified to run, which adds more procesess/tasks to the kernel and this will suck your speed and battery.
Let´s build something pretty...............:laugh:
Hello everybody, and welcome to the world of modding.
From today, we will be coordinating an army of people to work towards a common goal: Having the best ROM for our phones, and surviving the day.
The tools you absolutely need:
Brain
Hands
Eyes
Text-comprehension.
Be a self-troubleshooter
Advanced Google skills
Patience
Some Weed
First of all I will just oversee the topic: ODEXED vs DEODEXED
In simple words, Odexed systems have XX.apk and XX.odex, which store certain app properties (like icons, colors, fonts, menus) so that they wont be messed up with, thus making the system more stable, Deodexed systems, have only APK´s with their icons, colors and behaviors packed on, thus making theming, modding and using alternative system apps easier.
If you would LOVE to read about the subject, please refer to this: http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Well, now that you are totally aware of the odex-deodex situation, you might ask yourself..
-how the phuck do I deodex my system??????
Well, deodexing implies merging the .odex properties onto the apk.
Hey!!!! but how???
you need brains, patience, Java SDK7, Android sdk, and music.
http://forum.xda-developers.com/showthread.php?t=1852322 this instructions are for deodexing.. good luck....
To save your time, you need Android SDK and JSDK properly installed, you need xUltimate (Try and find the version that works on you), and you need the patience and willingness of Sidharta.
Ive tried already 5 versions of xUltimate to find out errors on different files!!!!!!
http://forum.xda-developers.com/showthread.php?t=2065270This will tell you some other basics on the xultimate deal.
There are other ways to deodex, help me google that.
We will be based on the stock 1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US SBF....
I would love to develop something good to both sprint and boost, but I have a Sprint handset, so I cannot assure our development will work on boost handsets, so please just sprint handset owners only for now.
For xultimate errors and troubleshooting, please refer to Google.com!
Ive been up all last night deodexing my system apps, and found out that most google related apps cannot be deodexed...
maybe that's why you need to install gapps in cm7 or other custom roms...
anyway people, let's get fully deodexed.
Make sure you have both Android SDK and Java SDK 7 PROPERLY installed oin your pc before trying this.
Cheers, luck and please reply
One last thing, I dont know if it is related somehow, but try to flash your stock rom without a SIM card inserted
Quick update: I Think I´ve got it figured out....
You need full Android SDK, and Java development kit, Android sdk tools alone wont do it, and java alone wont do it, you need developer runtimes and libraries for some programs like xultimate to run right.....
And you need not to activate, use or anything your phone before trying to deodex, I guess just starting up and entering simple things as the time, or having a sim card installed, or your google account can write data on the phone and mess up with the deodexing process.....
xultimate has already deodexed full framework and has passed from the yesterday´s troublesome google quick search box...(first thing to fail last night) so let´s hope it goes well.. it is indeed a loong process...
and just another error, but now I think I have it figured out, you need smali-baksmali assembler/disassembler for some specific .jar packed files... I´ve just installed it, and hopefully will post a fully deodexed stock rom today or tomorrow, for you to test and for us to start theming.
remember if you want to try... you need jdk not just java, you need full android sdk bundle, and you need smali/baksmali on your jdk installation for it to work properly...
%#%"!!!
This completely sucks, I´ve been trying to troubleshoot the errors xultimate is throwing at me on specific files, that lead me to download A LOT of java JRE and JDK versions, and both in x64 and x32 flavors, which apparently caused a major mixup on my PC´s guts....
Now I´m freaking trying to clean up my dev enviroment, trying to re-set the appropiate paths and classes, but hell with it...
Anyone succeeded??? please let me know if you´ve tried and if you get into any error can you please upload a screenshot???
thanx
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
tzuba12 said:
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
Same.
Sent from my MB612 using xda app-developers app
are you trying to deodex the stock rom?
rongsang said:
are you trying to deodex the stock rom?
Click to expand...
Click to collapse
yes sir, but in the mean time I managed to patch it with the battery mod, power menu and ICS style notifications
If I can deodex it I think I can improve it a little bit more in terms of performance and looks and functionality , but my powerful pc is a zombie right now, this is no task an old notebook can handle
I have deodexed it a long time back but sadly I can't upload it now. You can run kitchen from cygwin and it will deodexed your rom completely.
Sent from my MB612 using xda app-developers app
Ive used the kitchen and xUltimate with no good results mate!...
I always get smali errors or heap size errors despite I was using even a 4gb heap size, and tried using different versions of smali baksmali....
I am beggining to think I´ve been cursed by the digital gods.
BTW, if you´re able to upload it, I´ll be very thankful dude! I think Im going nowhere right now
Hello everyone,
I am new to the Nexus 4 community however not new to XDA. I have survived an HD2 and also a T989 GSII. I have had so much success with XDA and I am looking forward to working with community of folks over here. I got a Nexus 4 (being delivered Monday) to enjoy the Android experience. However the more I look over it the more I feel it lacks some of the features that I enjoyed with previous custom roms like Toggles on the notification panel for example. I know there are many apps that will accomplish the same thing but why use all these 3rd party apps when you can flash a decent rom and get a better experience with often better battery life. I am coming from an All Star Developer ROM that is a compilation ROM ( CM10, AOKP & PA )
I apologize for the rambling. I need to know:
1: What is the difference between Original Android Dev and Android Development forums? GSII did not have two forums so I was a little confused.
2: For a genuine NEXUS device, are there still bugs in ROMS? RR, SOD, GPS not working, etc? This is not a huge issue with most GSII roms I just wondered if you guys experience this at all with this phone being stock Android already. I wouldn't think this would be the case.
3: I have done my research and I am ready to move on with rooting and probably Romming. Is there anything else maybe that would be noteworthy that is specific to the Nexus line of devices. This is a vague question so don't worry with it too much. I am just curious.
Thanks everyone! I can't wait till Monday!
jcnbama said:
Hello everyone,
I am new to the Nexus 4 community however not new to XDA. I have survived an HD2 and also a T989 GSII. I have had so much success with XDA and I am looking forward to working with community of folks over here. I got a Nexus 4 (being delivered Monday) to enjoy the Android experience. However the more I look over it the more I feel it lacks some of the features that I enjoyed with previous custom roms like Toggles on the notification panel for example. I know there are many apps that will accomplish the same thing but why use all these 3rd party apps when you can flash a decent rom and get a better experience with often better battery life. I am coming from an All Star Developer ROM that is a compilation ROM ( CM10, AOKP & PA )
I apologize for the rambling. I need to know:
1: What is the difference between Original Android Dev and Android Development forums? GSII did not have two forums so I was a little confused.
2: For a genuine NEXUS device, are there still bugs in ROMS? RR, SOD, GPS not working, etc? This is not a huge issue with most GSII roms I just wondered if you guys experience this at all with this phone being stock Android already. I wouldn't think this would be the case.
3: I have done my research and I am ready to move on with rooting and probably Romming. Is there anything else maybe that would be noteworthy that is specific to the Nexus line of devices. This is a vague question so don't worry with it too much. I am just curious.
Thanks everyone! I can't wait till Monday!
Click to expand...
Click to collapse
1. "Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source""
2. Minor bugs here & there, nothing like the ones you're used of. Read the OP & last 20 posts in the thread.
3. follow the link in my signature, do not use toolkits!!
Good luck, it's an amazing phone!
Vangelis13 said:
1. "Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source""
2. Minor bugs here & there, nothing like the ones you're used of. Read the OP & last 20 posts in the thread.
3. follow the link in my signature, do not use toolkits!!
Good luck, it's an amazing phone!
Click to expand...
Click to collapse
Thanks for the info! I guess more specifically I need to know the difference between the "Original" Development thread and just the "Development" thread. Should I refer to one more than another?
Also, in reference to toolkits. I am just curious where the issue lies with that? Because honestly that is exactly what I was going to do. I am not lazy, just efficient lol. I figure why do alot of manual driver installs and command prompts if someone created a program that would do it for you? (I reference links below) Is it faulty software? Badly written programs etc? I would think there would be more room for human error when doing it yourself vs. something automated. What are your thoughts on this? Has anyone else had luck using the toolkits in the links? or any other rooting toolkits? Thanks again!
http://lifehacker.com/5979763/how-to-root-the-lg-nexus-4#13634416619583&{"type":"iframeUpdated","height":640}
http://www.wugfresh.com/nrt/
jcnbama said:
Thanks for the info! I guess more specifically I need to know the difference between the "Original" Development thread and just the "Development" thread. Should I refer to one more than another?
Also, in reference to toolkits. I am just curious where the issue lies with that? Because honestly that is exactly what I was going to do. I am not lazy, just efficient lol. I figure why do alot of manual driver installs and command prompts if someone created a program that would do it for you? (I reference links below) Is it faulty software? Badly written programs etc? I would think there would be more room for human error when doing it yourself vs. something automated. What are your thoughts on this? Has anyone else had luck using the toolkits in the links? or any other rooting toolkits? Thanks again!
http://lifehacker.com/5979763/how-to-root-the-lg-nexus-4#13634416619583&{"type":"iframeUpdated","height":640}
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Because, you learn something very important while rooting & unlocking your phone. Human error is covered for by the step by step guide. Human error while using the toolkit, you're stuck trying to understand what the fck happened. Learn fastboot mate. Learn to control your device to a 100%, learn to fix it if it's stuck. Understand what happens with "fastboot OEM unlock". Do you know what that means btw..?
The difference between Original Development & Development is in the quote I posted above. Paranoid Android = Original.
TWRP Recovery = Original
"XYZ" Rom based on cm 10.1 + abcd theme = Development.
Vangelis13 said:
Because, you learn something very important while rooting & unlocking your phone. Human error is covered for by the step by step guide. Human error while using the toolkit, you're stuck trying to understand what the fck happened. Learn fastboot mate. Learn to control your device to a 100%, learn to fix it if it's stuck. Understand what happens with "fastboot OEM unlock". Do you know what that means btw..?
The difference between Original Development & Development is in the quote I posted above. Paranoid Android = Original.
TWRP Recovery = Original
"XYZ" Rom based on cm 10.1 + abcd theme = Development.
Click to expand...
Click to collapse
Hey thanks again. I appreciate the input. I have more to learn in the NEXUS forum. I am used to ODIN and other forms of Samsung software so I will certainly read over the tutorial and absorb information. It will also help me to share my knowledge with others.
jcnbama said:
Hey thanks again. I appreciate the input. I have more to learn in the NEXUS forum. I am used to ODIN and other forms of Samsung software so I will certainly read over the tutorial and absorb information. It will also help me to share my knowledge with others.
Click to expand...
Click to collapse
If nothing else, you owe it to yourself as a proud n4 owner!!
How would ROM deving work for this type of phone where people choose their own specs?
now that i think of it, how would there be updates either? its like a one and done process. so if you buy the phone, you'll stay on the Android version that comes preloaded
I am thinking towards windows kind of update model but free this time.
Only thing is can we modify Linux kernel for enough flexibility.
NaveenKumarXDA said:
I am thinking towards windows kind of update model but free this time.
Only thing is can we modify Linux kernel for enough flexibility.
Click to expand...
Click to collapse
Might be able to work if the MDK enforces a unified modular structure. And extra parts of ROM's would target some v heavy/popular modules.
I think you ubuntu may be the way to go.
Since my knowledge is really limited, if Google and manufacturers cooperate for open-hardware and open-source environment, it will be like installing drivers on a new OS. So everyone can use latest version of Android. Am I right or really really wrong?
Sent from my GT-I8190 using XDA Premium 4 mobile app
I could imagine an official update method in which the used modules are recognized and the update fits perfect to that phone or the modules have anyhow universal usable drivers stored on themselves while you can change them without re-flashing the entire rom.. what do you think?
Surely if all the componets are made by the same manufacter the roms would be universal but with some roms being heavier for the powerfuller phones and lighter for cheaper phones
It will be harder. There will be bloated kernels that account for unused modules. Likely to be devs that tune to a specific hardware set [their's], etc. But w/ a diy modular phone, they'll probably be no shortage of developers.
A cooler way would be to enable more run as module on kernel and have each module self-load its drivers [like plug-n-play]. This could avoid the kernel bloat I aluded to earlier.
Rob
insink71 said:
A cooler way would be to enable more run as module on kernel and have each module self-load its drivers [like plug-n-play]. This could avoid the kernel bloat I aluded to earlier.
Rob
Click to expand...
Click to collapse
I agree with this, or maybe if the system can build the driver files on startup or installation. but then you will be looking at stall's and system freeze if it's interrupted. (just mentioned something similar in another post lol!):fingers-crossed:
If the bootloader can report the serial/models of the components, the kernel can turn on and off what's needed or not. From there yes, there will be a ****ton of modules to compile even if half aren't used. We can also expect to see hybrid kernel drivers doing different things based on some data returned by the actual component (e.g. 16GB vs 32GB storage) -- assuming those components work the same.
Maybe they'll make a new OS for this, kinda like Windows OS. It's supposed to be universal, no matter what kind of parts are installed.
The rom devs can list the minimum specs for the rom so the user has at least the minimum for the rom
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Nope, it is said that you can change modules on the fly. Maybe there are just drivers in the plug in that are loaded first...
Maybe the compatibility to drivers coves with android 5.0?
Regards
Gesendet von meinem C6503 mit Tapatalk
as people have said this wont be common outside the custom pc type market and if it don't support android in some from whether that be via a custom rom and recovery like cwm/twrp it will be a massive flop
i cant see why it cant come with a option that has cwm installed with a rom,them its attractive to coders
I really hope that they have the option for sales of just the outer shell. Then, people like me can custom select whatever they want without having to waste the stock modules which would then be rendered useless.
i hope they make a rolling system similar to how its done by Arch Linux where you start with just a base and let the owner select his own modules or let the user make their own module. that would be fantastic! i mean perfect!
pandasa123 said:
How would ROM deving work for this type of phone where people choose their own specs?
now that i think of it, how would there be updates either? its like a one and done process. so if you buy the phone, you'll stay on the Android version that comes preloaded
Click to expand...
Click to collapse
I think there will only be ROMs for certain phone combinations
Sent from my ultimately bumped up LG-P700 running CM11
The modularity will be programmed into the OS. Wether that part goes open source or not is another question.
Gesendet von meinem XT1039 mit Tapatalk
all parts will be class compliant iirc, meaning each new OS/rom only needs have generic drivers, anything that isn't class compliant needs to carry its own drivers, i could be wrong but im sure thats what he said in the interview with the first working spiral 1
I may be a bit crazy in thinking this.
But I'd LOVE project ARA and Cyanogenmod to partner and have their CM OS on the ARA modular phones. Imagine we could have theme chooser on the device. And customise it exactly to our liking.
inside and out in this case.
But alas it's only a pipe dream.
I have a Moto G6 device that I need to build a ROM for and I am pretty much stuck at the point where I need to include the proprietary device drivers so that I can compile the ROM. I guess my main issue is knowing where to get the proprietary files and how to incorporate them into my ROM. The device has a separate "/vendor" partition (for Treble compliance) that I was able to use TWRP and ADB to copy the files to my PC by running TWRP and then using ADB PULL command "adb pull /vendor D:\ALI\vendor" to get the files into a folder on my PC and was successful in doing that, but now what? What do I do with them? I downloaded from git the AOSP source for the last build of Oreo (8.0.0_36), so I hope that in itself is correct.
In the past, I have built a custom ROM for the Moto G4 via LineageOS 14.1, so I had a lot of info on how to grab the drivers from a device that was already running LineageOS 14.1, but this Moto G6 is running stock Oreo (8.0.0), so I am at a loss on whether or not I grabbed them from the device properly and now that I have them in folders on my PC what do I do with them and how do I set up the device tree so that I can get AOSP to compile.
So what do I do next and how?
I dont know if you've seen this and sorry if it doesn't help you at all. https://source.android.com/setup/develop/new-device
meatwad0222 said:
I dont know if you've seen this and sorry if it doesn't help you at all. https://source.android.com/setup/develop/new-device
Click to expand...
Click to collapse
I will look it over and see if I can hit the ground running with the info it provides. If not, I'll report back here for more help if needed. Thank you!
hawleytronics said:
I will look it over and see if I can hit the ground running with the info it provides. If not, I'll report back here for more help if needed. Thank you!
Click to expand...
Click to collapse
Honestly, this should have been posted in the Q&A Section, and the title is a little misleading. Just saying.
Anyway, as far as building goes, you have a lot of reading and learning to do. It'll take a lot more than that link the other user provided above as that's more for OEM's (but will give you somewhat of an understanding of what it's gonna take to put together a device, kernel, and vendor trees).
There is a lot of info regarding building ROMs for devices here on xda. I'd recommend reading thru those threads/posts for some insight.
Jleeblanch said:
Honestly, this should have been posted in the Q&A Section, and the title is a little misleading. Just saying.
Anyway, as far as building goes, you have a lot of reading and learning to do. It'll take a lot more than that link the other user provided above as that's more for OEM's (but will give you somewhat of an understanding of what it's gonna take to put together a device, kernel, and vendor trees).
There is a lot of info regarding building ROMs for devices here on xda. I'd recommend reading thru those threads/posts for some insight.
Click to expand...
Click to collapse
OK, thank you, and sorry for posting in the wrong area. It appears that I need to know more in-depth about the actual hardware and what drivers are needed and where they need to go. So more research it is.