[Q] Noob AOSP build on unsupported device - Android Q&A, Help & Troubleshooting

Hello,
I have an Ampe A10 Quad core tablet (Freescale I.mx6q chip) which has quite a small dev community so far so I am looking at building my own rom for the device.
i can get by in Linux and learn fast so feel I can do it. I have been reading constantly for the last week before even starting to get a grip of whats what. I am trying to make an ASOP version of 4.0.4 to replace the stock 4.0.4, rather poor rom.
My question is what do I do about vendor overlays as there is nothing out there for this device or anything similar. I have done a lot of searching on this and found the suggestion "You could just use an extract from a working Rom or phone" " You use the extracted proprietory files to complete the source" . I understand I need the proprietary binaries to make the build but i don't really understand what that the suggestion means.
Any help you could offer on obtaining the files I need from the stock ROM and how to setup the vendor overlay would be most appriciated.
Cheers,

I don't have your device man, but if there is another similar device out there with a similar board and chip configuration search github for a repo that contains an "extract-files.sh" file for that other device. Fork it, clone into your dev environment under your Device folder, connect your tablet via USB (make sure adb is running), and run that script. It should pull the proprietary files required straight from the device and you may be better off.
Hope this helps a little! Good luck with your project.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

djmatt604 said:
I don't have your device man, but if there is another similar device out there with a similar board and chip configuration search github for a repo that contains an "extract-files.sh" file for that other device. Fork it, clone into your dev environment under your Device folder, connect your tablet via USB (make sure adb is running), and run that script. It should pull the proprietary files required straight from the device and you may be better off.
Hope this helps a little! Good luck with your project.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the advice. I have spend some time searching but cannot find anything on github. There are only a couple of devices that are similar. The Ampe A10 Sanei N10 and Hiapad F10 are all the same thing just rebranded, the other is the Zenithink C94 but I cant find anything on any of them.
How can I create a new device tree for my device? (which from what I understand is what I want) It would be a good thing to achieve as it would help others in the future. I have been through the "Configuring a New Product" on the AOSP site so now understand a bit more what's going on.

Sp3ktral said:
Thanks for the advice. I have spend some time searching but cannot find anything on github. There are only a couple of devices that are similar. The Ampe A10 Sanei N10 and Hiapad F10 are all the same thing just rebranded, the other is the Zenithink C94 but I cant find anything on any of them.
How can I create a new device tree for my device? (which from what I understand is what I want) It would be a good thing to achieve as it would help others in the future. I have been through the "Configuring a New Product" on the AOSP site so now understand a bit more what's going on.
Click to expand...
Click to collapse
extract-files.sh is a cyanogenmod creation, so you'd be lucky to find anything....... Linaro offer support for the sabre lite development platform which is a i.MX 6q based board, maybe building Linaro's version of the AOSP would be a good start
Here's a couple of links to get you started
https://wiki.linaro.org/Boards/MX6QSabreLite - Overview of the Board, you can check how close it is to your device
https://wiki.linaro.org/Platform/Android/BuildSource
You are correct you need to create a device tree , a couple of good resources I've used in the past when creating device tree from scratch are
Embedded Android ( http://shop.oreilly.com/product/0636920021094.do ) this book is pretty close to the bible on the Android Build System and worth the Investment. Alternatively ( more importantly free! ) a slide deck by the same author ( http://events.linuxfoundation.org/slides/2011/abs/abs2011_yaghmour_porting.pdf )
Android Device Porting - http://www.youtube.com/watch?v=mvxYt3AkbrE

Could the extract script not be used to help pull the right files straight from the device for his vendor folder though? He would just need to edit the list of files to be pulled in the referenced list the script uses in the loop if he knows what configuration files are needed, no?
I'm by no means an expert but on first glance that's all the extract-files script does...or is there something I'm missing? I'm learning too so would be good to know either way lol
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

djmatt604 said:
Could the extract script not be used to help pull the right files straight from the device for his vendor folder though? He would just need to edit the list of files to be pulled in the referenced list the script uses in the loop if he knows what configuration files are needed, no?
I'm by no means an expert but on first glance that's all the extract-files script does...or is there something I'm missing? I'm learning too so would be good to know either way lol
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Apologieses if that came across as abrupt, Just sayin' you'd be lucky to find one that come close to his board etc, iMX Freescale chips are not that mainstream But yeah if you can find an extract script than have at it! Saying that why do you even need a script? just pull the files yourself through adb, pointless wasting time searching. The question then becomes, what files? And that is unique the each device and each version and how much of it is open source etc,etc.
I think the OP is probably a way off doing that, when I've played around starting a device tree from scratch, I've find it is easier to start off with the base requirements, i.e processor architecture, maybe start with building a mini package first or even BUILD_TINY_ANDROID on a generic arm board. The whole starting from scratch thing is not a small task, which I suppose was your point in the first place lol

For sure. It really does boil down to what files, whether a script is used to pull them or not lol.
Thanks for the links by the way, SUPER informative
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

thanks for all the great info Trevd. The Sabre lite board is very similar indeed! There seem to be only a few minor differences which are inconsequential anyway. For example the tablet have less USB and no Ethernet. I think it could be a good starting point.
I guessed when I started this project it wouldn't be a quick fix but that't not a problem, At the end of it I will have my own working ROM and that's the point.
I can see the Freescale chips being taken more in to the main stream in the future. The tablet is VERY fast and reliable it has just been let down by poor, half-arsed software. For example all the aspects of Android relating to telephony have still been left in.
Thanks again,

Sp3ktral said:
thanks for all the great info Trevd. The Sabre lite board is very similar indeed! There seem to be only a few minor differences which are inconsequential anyway. For example the tablet have less USB and no Ethernet. I think it could be a good starting point.
I guessed when I started this project it wouldn't be a quick fix but that't not a problem, At the end of it I will have my own working ROM and that's the point.
I can see the Freescale chips being taken more in to the main stream in the future. The tablet is VERY fast and reliable it has just been let down by poor, half-arsed software. For example all the aspects of Android relating to telephony have still been left in.
Thanks again,
Click to expand...
Click to collapse
Plz keep us in the loop on how the rom is comming along.
Not that many I.MX6Q roms out there yet, and im sure many peeps are waiting for it
Thx for giving it a shot
Ill be watching

Corw1n said:
Plz keep us in the loop on how the rom is comming along.
Not that many I.MX6Q roms out there yet, and im sure many peeps are waiting for it
Thx for giving it a shot
Ill be watching
Click to expand...
Click to collapse
I'm one if those hoping for a decent rom... Apparently freescale have released a beta for jelly bean on the imx6.

MrVanDango said:
I'm one if those hoping for a decent rom... Apparently freescale have released a beta for jelly bean on the imx6.
Click to expand...
Click to collapse
Oh? Where did u find that? Been googeling my ass off trying to find a freescale jb rom....
Hope it comes tho.....already ordered my ampe a10 quad.....

Corw1n said:
Oh? Where did u find that? Been googeling my ass off trying to find a freescale jb rom....
Hope it comes tho.....already ordered my ampe a10 quad.....
Click to expand...
Click to collapse
You can download it from github. I can't post links at the moment. If you can't find it PM me and i'll forward the link i have.

MrVanDango said:
You can download it from github. I can't post links at the moment. If you can't find it PM me and i'll forward the link i have.
Click to expand...
Click to collapse
any updates on this? i cant find it on github either.

goldenpipes said:
any updates on this? i cant find it on github either.
Click to expand...
Click to collapse
The Freescale Github account is here, and it doesn't look like they provide much more useful stuff than their meta-packages there: github.com/Freescale
What I know is that for every SoC they have a page (sorry, not allowed to link yet. just search "i.MX6" on the freescale website) where they offer demo images and at least a set of patches with some documentation on how to build that Android branch.
E.g. at "Operating System Software-Board Support Packages" you can find a demo image for Kitkat and a source package: "IMX6_KK442_100_ANDROID_SOURCE_BSP" (you have to register a free account with your mail to download this). Then usually it works like this:
Get the according AOSP branch from Google
Apply patches provided by Freescale
Clone their kernel repository
Clone their uboot repository
Build
Look for a document named "Sabrelite-Android_User's_Guide.pdf" for more detailed information. Sorry, I can't remember if it was included in the source package or in another download provided in their list.

Related

[Q] how to port ics (serious learner)

Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte

Want to start with AOSP JB 4.2 - experienced developers are welcome :)

Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium

[Q] Samusung XCOVER/GT-S5690 questions.

Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed

[Q] how to use Samsung Open Source files and JB AOSP (4.1.2_r2.1)?

Hello all,
I'm trying hard to figure out how one goes about compiling Android JB AOSP (4.1.2_r2.1) platform for the samsung galaxy s2 (GT-I9100M), with the source code that samsung gives you?
I've setup ubuntu 14, and I see how I can run . build/envsetup.sh, and then lunch.
I get all the options to build, and I see where the saumsung scripts are located, in device/samsung.
I've downloaded the open source file GT-I9100M_BMC_JB_Opensource.zip, and compiled the Kernel.
Now its time to build the platform. I see the folder structure, but I see no instructions.
When I unzip the Platform, I see build, external, vendor, and device, which has the folder "smdk_common".
If I put all files in the corisponding locations within the AOSP, I get errors, as there's only a folder "alsa-lib". (sound drivers).
And if I were to compare what's in here to whats in the AOSP device/samsung folders, there's lots more info.
Do I need to copy files from the default AOSP device/samsung folders and modify to suite my needs or?
Can anyone point me to how-tos? I've been trying to figure this out for days!
I see a lot of how tos on building with existing ROMS, and using kitchen, etc.
But I just want to build samsung from scratch FIRST...
OK, so doing a lot more research, both here and google, I obviously need to create a device tree OFF of the files that samsung has released to everyone. Surely someone has done this already?
I see there are a few GIT repositories that have device trees, but they are based upon existing files, etc.
I'm looking to find a device tree that has all the basics, OR a "template" one i can try and work with samsungs...
technobuddha said:
OK, so doing a lot more research, both here and google, I obviously need to create a device tree OFF of the files that samsung has released to everyone. Surely someone has done this already?
I see there are a few GIT repositories that have device trees, but they are based upon existing files, etc.
I'm looking to find a device tree that has all the basics, OR a "template" one i can try and work with samsungs...
Click to expand...
Click to collapse
Hi,
did you succeeded in your approach to build a device tree with the Samsung-opensource-files? if yes then I'll be very interested in the way you do it as I'm on the same status for a Samsung device which has absolutely no support in the hole internet (except one thread here in XDA
BR
SP
No I didn't.
and I got no help what so ever from the people here at xda-developers.
I even approached some of the people who compile the roms, and got no response from them.
I suspect the only help you'll ever get from these forums is if you ask for help from EXISTING roms,
or you're an "existing" developer that has years of experience.
this place is not for new developers at all.
a lot of brown nosing going on here..
good luck in your search!
SolarPlexus said:
Hi,
did you succeeded in your approach to build a device tree with the Samsung-opensource-files? if yes then I'll be very interested in the way you do it as I'm on the same status for a Samsung device which has absolutely no support in the hole internet (except one thread here in XDA
BR
SP
Click to expand...
Click to collapse
technobuddha said:
No I didn't.
and I got no help what so ever from the people here at xda-developers.
I even approached some of the people who compile the roms, and got no response from them.
I suspect the only help you'll ever get from these forums is if you ask for help from EXISTING roms,
or you're an "existing" developer that has years of experience.
this place is not for new developers at all.
a lot of brown nosing going on here..
good luck in your search!
Click to expand...
Click to collapse
OK, thanks for your response. Thats also my experiance more ore less I have found (with some exceptions which really try to help).
So I'll try to work on it, and if I succseed, I'll make a guide... maybe it will help then others
BR
SP
what phone is it?
and yea, if you need any help,just ask me.
SolarPlexus said:
OK, thanks for your response. Thats also my experiance more ore less I have found (with some exceptions which really try to help).
So I'll try to work on it, and if I succseed, I'll make a guide... maybe it will help then others
BR
SP
Click to expand...
Click to collapse
Its the Samsung sg-i8200 (s3 mini value edition)
The previous phone was supported very well (i8190) but the i8200 has a complete new hardwarebase and its really garbage...
send with my Oneplus One (bacon) SlimKat Tapatalk

[TREE] Need help creating the Honor 7 device tree.

NEED HELP​
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin​
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common​
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin​
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common​
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source(PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.

Categories

Resources