Related
Hello to all.
I recently got a Hyundai T7s Tablet.
There is no much support for it and the default ROM has many bugs.
I wanted to start playing around with the ROM and see what I can fix.
But I am really new with the cooking and some things don’t work for me.
The best thing would be to port CM, but that's very hard for me and my up to now knowledge.
I use the dsixda kitchen in ubundu.
The ROM I am using is the original 4.2.2 from Hyundai. You can get it here: https://skydrive.live.com/?cid=0411c6dc1d2f8186&id=411C6DC1D2F8186!1990&authkey=!AG-_MSdQoCJZegs
This ROM is not in the usual format, .zip with META-INF and system folders, but It has many files in it, that you put them in a external SD card and the upgrade is done automatically.
I have managed to change some things in the ROM (remove apk, root etc) , but I cannot manage to save the ROM in the default format with the dsixda kitchen, I always end up with the .zip file with the two folders in it.
I would appreciate any help with that !!!!
fratzeskos said:
Hello to all.
I recently got a Hyundai T7s Tablet.
There is no much support for it and the default ROM has many bugs.
I wanted to start playing around with the ROM and see what I can fix.
But I am really new with the cooking and some things don’t work for me.
The best thing would be to port CM, but that's very hard for me and my up to now knowledge.
I use the dsixda kitchen in ubundu.
The ROM I am using is the original 4.2.2 from Hyundai. You can get it here: https://skydrive.live.com/?cid=0411c6dc1d2f8186&id=411C6DC1D2F8186!1990&authkey=!AG-_MSdQoCJZegs
This ROM is not in the usual format, .zip with META-INF and system folders, but It has many files in it, that you put them in a external SD card and the upgrade is done automatically.
I have managed to change some things in the ROM (remove apk, root etc) , but I cannot manage to save the ROM in the default format with the dsixda kitchen, I always end up with the .zip file with the two folders in it.
I would appreciate any help with that !!!!
Click to expand...
Click to collapse
Yo bruv XD
Yeah Hyundai T7 range are wicked lill tablets, I love the fk outta my T7, so much am gonna sell it and buy a T7S for practically the same price. Shame they will probs never get the scene support they so hugely deserve, these tabs clearly both out-performs and out feature the nexus 7 tabs, at a price anyone can afford. Has great hardware some well tailored Roms would make it fly.
Tab is THE poster boy for affordable high spec tablets IMHO.
So good luck with the Rom project.
My advice is try and get someone with a deal of experience backing you up on this stuff bro. Guys with experience are
often very happy to help new guys ... as they like to see carbon copies of themselves coming up the scene ladder
Post in a few of the lobbies asking for some support with this, just don't spam. A lotta peeps on here only look in
certain lobbies, so spread da word bruv
Few questions. One reason i have held off the T7S move is i was waiting for a 4.2.2 Rom to come out for it.
So can you tell me is this Rom a beta, alpha, or what and what do you mean by "many bugs".
I have the 4.2.2 Rom for my T7 installed and its fine, missing a few deliberately Hyundai removed features, am not
sure if its a beta or not, but works well and is as stable as any other Android Rom i have used.
So is this T7S Rom like that or not??
If answers are positive ima drop the hammer on one of these bad boys immediately.
Hyundai for life !!!!!!!!
Hi, can somebody cook CM 10.1 for T7s ?
Nobody ?!
Background:
Ant+ and Health/Sport accessories are not very widespread among smartphone users, but it was one of the major reasons a which I moved from the Nexus 4 to Galaxy S4.
While S4 on 4.3 works great with my Garmin Heart Rate Monitor(HRM), I'm not satisfied with Touchwiz and Knox.
My S4 feels laggy, slow and I want to use stock android, or even any of those KitKat releases.
Many Xperia devices have Ant+ support, and it seems that they manage to cook it into custom roms successfuly.
Target:
Assemble a flashable zip which would allow anyone with an S4 already flashed to 4.3 to use the Ant+ receiver.
Research:
I've spent some time embeddint the Ant+ files (com.dsi.ant.antradio_library.jar and .xml, and the AntHalService.apl) on MakTail's 4.3 GE but ran into an issue that blocked further investigation:
The AntHalService tries to enable bluetooth, can't find the method and reboots the device.
The version is 3.0.0 which is supplied on Stock ROM, and there is already a 3.1.1 available from Ant Alliance which removes the requirement for enabling bluetooth.
I got the source code and compiled the apk, but I can't run it as a System App, so I got stuck. Spent some time trying to workaround it, but no success.
I guess that even when I get hold of a working 3.1.1, there will be new issues, and I'm a complete newbie on ROM cooking.
So I would like help from others, maybe suggesting next steps or getting hands on with me on this project.
XDA:DevDB Information
Ant+ Support for Non-Stock ROMs, a Tool/Utility for the Samsung Galaxy S 4
Contributors
AdrienC
Version Information
Status: Testing
Created 2013-11-25
Last Updated 2013-11-25
Attached is a file with the system files required for ant which I could find after some investigation.
Links:
Here is the source code for the AntHalService.apk which I couldn't run as System service.
https://github.com/ant-wireless/Android_ANTHALService
And the slooow forum:
http://www.thisisant.com/forum/viewforum/30/
to run as system app if you are rooted just manually copy apk to /system/apk
lgkahn said:
to run as system app if you are rooted just manually copy apk to /system/apk
Click to expand...
Click to collapse
won't work due to the signature I guess. Even when I signed with debug keys didn't work. Maybe due to SELinux?
Code:
I/PackageManager( 707): /system/app/AntHalService.apk changed; collecting certs
W/PackageManager( 707): Signature mismatch for shared user : SharedUserSetting{42a56d98 android.uid.system/1000}
W/PackageManager( 707): SELinuxMMAC.assignSeinfoValue
E/PackageManager( 707): Package com.dsi.ant.server has no signatures that match those in shared user android.uid.system; ignoring!
I am going to flash 4.4 GE edition by Jamal http://forum.xda-developers.com/showthread.php?t=2544474 and will try to survive with my Suunto USB Ant+ stick on OTG to allow me to spend more time trying to make this work.
Will update with any progress/issues.
Well, I send a cry for help to @broodplank1337 and got his awesome reply showing availability and this was my reply, which I decided to share as while I waited for help I made some pretty good advance!
While I was waiting for your reply I made some progress....
I replaced the classes.dex from my compiled apk(from java source) into the samsung apk and that was enough to bypass the cert check ( I was pretty sure I tried that before, but must've done something wrong).
I found out the source code is referencing a kernel module that doesn't exist for Galaxy S4, so I ran Dex2Jar and Java Decompiler and I'm now analysing the source code and I think that it somehow passes the instructions directly to the chip.
I'm thinking about trying to change the bluetooth methods it uses to the ones available on AOSP, which is why the 3.0.0 was failing initially.
It'll probably still take some work, but it might be feasible.
The main issue is that I'm new to android coding, and not a java expert, but used to be a programmer and I'm finding my way (and some joy) hacking thru all this code.
Click to expand...
Click to collapse
I'm attaching the source code for AntHalService.apk from Samsung stock roms (version 3.0.0).
I guess I'll have to work over it, as the 3.1.1 I got from AntWireless references an antradioservice.so which Sammy don't have and causes a bootloop.
I am now comparing the smali code between the 3.0.0 and the 3.1.1 to see if I can do an easy patch, but it's not looking very likely...
Lets see how this goes.
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Guys, an update. I kinda gave up for a while. ANT Forums are helpless, and I got kinda tired of looking around. I'll need to have some free time and motivation to dissect the code and try to make it work on the AOSP bluetooth stack.
A good workaround I found is to have a dual boot solution, so you can switch to the Touchwiz ROM for a training.
karimero said:
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Click to expand...
Click to collapse
blue6800user said:
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Click to expand...
Click to collapse
blue6800user said:
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Click to expand...
Click to collapse
Thanks, hope to eventually come with good news, got kinda sad to hit a wall. But meanwhile, use your favourite rom and dual boot a Touchwiz ROM.
I'm now back to the last released version of 4.3 for Brasil to soon extract the libs and apk's to build a slim TW ROM just for dualbooting.
It'll be an easier workaround. For those with 32GB S4's don't even need to go down this path, just dual boot and be happy!
Thanks for working on this, got the S4 the other day coming from a Bionic that was had ANT+ chipset, but they never turned it on. I too would love a CM 11 with ANT+ support. I will happen, eventually.
ant+ apps on the app store
Hi I'm running 4.4.2 Echoerom on my S4 and just discovered that I'm lacking ANT support despite installing the ant service and apps from the store. Did you try these apps, were you able to make any progress?
Any updates on this ?
I'd like to use ANT+ on my s4 running AOSB.
Any updates for ant+ support in CM11?
The solution of dual boot seems very messy for only that
any news with that?
I'm super late with this, but if anyone is still looking at building ANT+ in to custom ROMs, I have had success building from the ANT Wireless source: check the ANT hardware thread
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
+1
Sent from my SM-N900V using Tapatalk
hectorz321 said:
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
Click to expand...
Click to collapse
Permission failure? Noob here too
I am guessing the ROM you tried to port checks for the Model number of the phone before flashing. What ROM did you try to port to and if you could post the instructions here we will make this the porting thread
Given that HTC One has all the custom ROM's and kernels we need devs or someone like us who can follow instructions to start doing it. I am sure we will get help from one another and end up with custom ROM's for the MAX.
I was also thinking of doing this but just to start with i don't want to look at the fingerprint scanner and may be later we could get it working.
I am certain most people would be willing to not have a working fingerprint scanner, as a trade off for a few custom roms/kernels...
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Murrda said:
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Click to expand...
Click to collapse
this was exciting to read, best of luck
I am going to get Ubuntu installed today and then Android Kitchen here i come!
pradeepvizz said:
I am going to get Ubuntu installed today and then Android Kitchen here i come!
Click to expand...
Click to collapse
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
DeadPhoenix said:
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
Click to expand...
Click to collapse
Thanks, i just installed it via virtual box without disturbing my system.
Just got android kitchen up and running, on prting sides of things got further this time, into aroma installes but error 7 which suggested earlyer is to do with mount points, if anyone could happen to help with theese it would be fab ))
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Click to expand...
Click to collapse
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
pradeepvizz said:
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
Click to expand...
Click to collapse
Murrda said:
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
Click to expand...
Click to collapse
heyy i could use some help doing this part in android kitchen. straight from android kitchens page but i can't seem to get the recovery.fstab out anyway! im on t6ul verson of the max by the way thanks
/HIDE (sorry dont know how to get this to work (forum noob here too)
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
hectorz321 said:
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
Click to expand...
Click to collapse
Good start mate! awesome!
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
hectorz321 said:
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
Click to expand...
Click to collapse
Which guide are you following? i just cooked a ROM today first time. I made the stock ROM for the T6UL.
---------- Post added at 08:34 PM ---------- Previous post was at 08:34 PM ----------
ooo, Merry Christmas everyone
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
HolyAngel said:
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
hectorz321 said:
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
Click to expand...
Click to collapse
Yeah, i know for the kernel, without being able to mess with the zimage, the sense max kernel lacks the init.environ.rc from gpe, the fstab file is different(at least file extension), and there's a few things that point to sense files or folders that don't exist on gpe. Currently there is no released source for the max yet :'( so unless someone knows how to do it manually and hasn't shared HOW to do so, I just have to wait.. Hopefully it won't be too long.
Sent from my HTC One using XDA Premium 4 mobile app
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
Hello, I would like to customize the phone more to my preferences and I would like to edit the systemui etc, I've tried looking for systemui, but just couldn't find it, I am using aosp extended, and when I looked for the systemui.apk in the system folder, its just not there. I used to work a bit with those things a few years back, but I don't know if its different because miui is maybe built differently or just android changed the way files are compiled or anything. Anyway, if someone could shortly explain to me how to edit miui/any custom rom system files, or give me a guide that fits miui, I would really appreciate it, thanks.
anyone pls? :\