Hello guys,
I hope I'm in the right forum.
I've studied several days, if it is possible to update my Smartbook S10 (smartbook.de/produktfeatures/72/technische-daten is the link from the manufacturer) from Android 4.4.2 to at least 7 (best case to the newest 9, that I'm trying atm).
It has got only 8GB of space, so I wanted to ask, if it's even possible with that low space and processor (RK3026)? Couldn't find clear information about this.
I've come that far, that I've created a new AOSP device tree and inserted all data I know/could find. But it fails now at the kernel.
I've tried to compile the common actual kernel 4.19 with Google's Android tools and getting this error:
Code:
/home/test/Android_Kernel/build/_setup_env.sh: line 28: /home/test/Android_Kernel/build.config: No such file or directory
My build repo lays at /home/test/Android_Pie. What am I missing or doing wrong?
Thanks in advance
Greetings
Andi448 said:
Hello guys,
I hope I'm in the right forum.
I've studied several days, if it is possible to update my Smartbook S10 (smartbook.de/produktfeatures/72/technische-daten is the link from the manufacturer) from Android 4.4.2 to at least 7 (best case to the newest 9, that I'm trying atm).
It has got only 8GB of space, so I wanted to ask, if it's even possible with that low space and processor (RK3026)? Couldn't find clear information about this.
I've come that far, that I've created a new AOSP device tree and inserted all data I know/could find. But it fails now at the kernel.
I've tried to compile the common actual kernel 4.19 with Google's Android tools and getting this error:
Code:
/home/test/Android_Kernel/build/_setup_env.sh: line 28: /home/test/Android_Kernel/build.config: No such file or directory
My build repo lays at /home/test/Android_Pie. What am I missing or doing wrong?
Thanks in advance
Greetings
Click to expand...
Click to collapse
Hello Andi,
I've got a similar question about the device, although I'm not at all an expert as you seem to be. Just want to run it with an COS (lineage, etc). So I am looking for a COS for this device.
Did you manage to solve your problem?
Do you have any idea what COS would run on a smartbook S10?
Thanks for your answer
Hi Willi,
I'm sorry to disappoint you, but I gave up this project after a few days, because I couldn't find any further information and I'm no dev at all. This was my very first attempt to compile a new kernel for an (additionally pretty unknown) Android device. The thing, which helped me the most was watching YouTube videos from https://www.youtube.com/channel/UCnGqG_jyyXmTzdamBpKfeHA (AlaskaLinuxUser AKLU).
Maybe some more experienced users can help you here.
Greetings
Related
*edit* sorry, didn't notice general warning, please move to Q&A
I migrated from SGS i9000 to a huawei G700 phone featuring a mtk6589 chipset.
Sadly, the android version limits the possibilities of the phone really hard: it's oriented towards users who play nicely with their phone, not towards me!
so, to keep a long story short, I'd like CM to be ported to this device. this is not a top-of-the-line product, so I'll certainly have to do it myself.
I already got the complete OS image, kernel properties, installed applications, and so on (boot.img, uboot.img, ...), locally installed here.
the question is: where to go from here? In your guides, I can follow what the developers explain to do and why they are doing it, but I got no idea how to convert this OS image into a CM image ...
Also, as there are apparently developers waiting for mtk6859 roms, should I send them a message asking for their help? http://forum.xda-developers.com/showthread.php?t=2375957
the only issue here is that I can't contact them yet because of the noob limit.
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
I’ll start by admiting that, in the arts of cooking/building/porting android innards, I’m closer to being a complete noob than na intermediate user.
I own a Newman K1S, JB 4.2.2, MT6592, 2Gb/16Gb, 720p, and, sadly for me, it looks like the manufacturer (Newman Mobile, or Newsmy, who knows) pretty much disavows any knowledge of this model ever being built or sold. No reference to it, no community, no android updates or ROM releases.
Taking into account some MediaTek source codes for KitKat were made available earlier this year (even if unofficially), I was wondering:
So, question number 1 – Is it possible to build android 4.4 for my device straight from said sources? Or are they unreliable and it would be best not to attempt it?
And question number 2 – Being at the noob level, should I stay away from such a task? And, in this case, would I be better off porting a 4.4 ROM from a similar spec’ed device?
Also, while browsing needrom, I noticed that a 4.4 “official” ROM was posted for my device. However, having flashed it, I found that it produces no sounds from the external speaker (although with headphones it works fine). Same thing was experienced by other users, and there is no fix so far.
Which takes me to question number 3 – What may I try, in order to fix an issue like this? Does KK use the same sound drivers as JB, and maybe it’s only a matter of replacing them? (if so, I believe this is within my grasp, even if I must unpack the IMG files to reach the drivers)
Lastly, Newman K1S has a severe overheating problem when pushed, which I believe would be easily solved by underclocking it to 1.3 or 1.5, or maybe implementing an optimized kernel.
Final question – How do I manage to underclock with my current kernel, or, better yet, how do I port a custom, optimized kernel to my device?
Congratulations to everyone who managed to read this far, and thank you in advance for any help provided. I’ve spent the last few days reading tutorials and guides, only to become even more confused… I did manage to get android kitchen running on my Windows laptop, though!
Links to recent/updated guides that might be useful are appreciated, too.
This is probably an insanely noob-ish question, but I've scoured the internet (and this site) for days and I haven't found anything yet, so I'm hoping someone with some smarts or experience can help me.
I'm trying to build TWRP recovery for my device, an unsupported phone. (The BLU Life One 2015: GSM Arena Specs) Specifically, the 2GB RAM 16GB ROM version, if that helps. I've been following this guide: [DEV]How to compile TWRP touch recovery by Deez Troy, and I've got my whole build environment set up, I have the source downloaded, and I've found (what I'm pretty sure is) a device tree for my phone HERE. I'm convinced it's for my phone since the model listed is X011Q, which is the name of the firmware for my phone.
The issue I'm having is that when I get to the part of the guide about editing the BoardConfig.mk file, I can't find it anywhere. Not in AOSP source, (which I downloaded for later use), not in the TWRP source, not in any of the partitions I've pulled from my phone, or in the device tree. My main questions then are these:
1.)Does it actually exist some where for me to find?
2.)Is it device specific, or will one for a phone with similar specs (probably) work fine?
3.)If I have to make/build it, how do I go about doing that? What needs to be in it? (Though I'm less sure this would be the case thanks to THIS post.
4.)If none of the above questions are the right one to ask, but if you think you know what I need to know/what I need to ask, please TELL ME!
Also, any other resources anyone can point me towards or advice/pointers you can give me would be greatly appreciated.
The same question.
No answers?
Fourteenth said:
The same question.
No answers?
Click to expand...
Click to collapse
Nope. If it didn't spontaneously create itself out of nothingness, you will never be able to find it. No one ever created the files, they popped out of Zeus' forehead fully-formed.
Here is the answer:
source.android.com - new-device
You can download the BoardConfig.mk for your device or make a new one.
Hi all,
Relatively am a new developer, trying to build aosp got everything figured out (I hope). Blindly following some instructions and got device tree from old nougat branch in google git. Building takes more time or just hangs not sure what is happening..
Before you guys reply like you can't do that or this, I just expect a polite answers.
Refer below!
vasanthmes said:
Hi all,
Relatively am a new developer, trying to build aosp got everything figured out (I hope). Blindly following some instructions and got device tree from old nougat branch in google git. Building takes more time or just hangs not sure what is happening..
Before you guys reply like you can't do that or this, I just expect a polite answers.
Refer below!
Click to expand...
Click to collapse
Takes more thime then what?
Perhaps you should start with a known good configuration.
Elektroschmock said:
Takes more thime then what?
Perhaps you should start with a known good configuration.
Click to expand...
Click to collapse
OK. But am having errors in several areas after doing make otapackage.
Is there any good device tree, vendor, kernel to start with?
Because the one I got is from master branch from google git and of course that is from a nougat version.
BTW I'm having a old laptop with i5 and 4Gigs of Ram. Probably that's why it is taking more time. Also running Ubuntu 18 on VM which is storing on my external hard disk of 2 TB connected through USB 3.0..
Am just curious and exploring things & trying to learn.
Thinking of giving up building 9.0 ...since I'm new to this.. May be proceeding with existing builds like 7.x.x from google or cm15.1 ..
vasanthmes said:
OK. But am having errors in several areas after doing make otapackage.
Is there any good device tree, vendor, kernel to start with?
Because the one I got is from master branch from google git and of course that is from a nougat version.
BTW I'm having a old laptop with i5 and 4Gigs of Ram. Probably that's why it is taking more time. Also running Ubuntu 18 on VM which is storing on my external hard disk of 2 TB connected through USB 3.0..
Am just curious and exploring things & trying to learn.
Click to expand...
Click to collapse
4gb of ram is your culprit, I suggest 8gb or 16gb .
Building is RAM dependent , and it also requires a fast SSD. I don't build roms, but I read a lot ?
Using Google Cloud for building now. Its amazingly fast!!!!! :fingers-crossed:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
vasanthmes said:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
Click to expand...
Click to collapse
If you want to build a ROM, you need to search and read a lot! This has been answered literally thousands of time on xda. Just use the search button and you would find that as a first result :fingers-crossed:
All the best for building the ROMs!
Nitin
vasanthmes said:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
Click to expand...
Click to collapse
Do an -eng build, then you can debug the boot process via ADB.
Did you extract the vendor blobs, or add a repository containing them?
Elektroschmock said:
Do an -eng build, then you can debug the boot process via ADB.
Did you extract the vendor blobs, or add a repository containing them?
Click to expand...
Click to collapse
Vendor blobs I think I did, let me check once I reach home.
Thanks for advice on -eng build and by the way as nitin said I will check how to debug as well.
Been trying to build on Google Compute Engine VM... Crazy fast and best for those who are building for first time..
-Vasanth