Database Develop

[JB 4.1.1][ROW] Just managed to compile

Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.

Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse

Woohoo! Look forward to trying this!

This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.

Great work, thanks! I'm glad that there is work going on!

Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium

Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!

Wow!! Keep up the good work!!!

can't wait, great work!

Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia

obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.

this isnt for the K1 is it

It's for tpt only

When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.

Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?

What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?

TPT= ThinkPad Tablet

Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.

Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.

mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.

[DEV]kernel 3.0

We have 2 phones with have same chipset and kernel 3.0.x
http://www.gsmarena.com/huawei_u8860_honor-4197.php
Huawei u8860
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
http://www.gsmarena.com/htc_one_v-4575.php
Chipset Qualcomm MSM8255 Snapdragon
CPU 1 GHz
GPU Adreno 205
link for one v sources(3.0.16)
houwei u8860(3.0.8)
:highfive:
Or eaven porting form CAF (3.0.23)
CAF kernel link
Guys ho porting from CAF are using RAY, MINI , LWW , NEO , so no dev form here was join that project
That all from me

[/B]
This howto is working only with 2.6.32.X kernel, when this project will be finished will add HOWTO for 3.0.8
You need linux machine, i don't know it is possible on Windows and if so i don't help you with that!!!
1. Download toolchain.
Download toolchain and extract it to /opt/ directory.
Should looks like:
Code:
/opt/arm-eabi-4.4.3/
2. Set up evn.
Edit your:
Code:
~/.bashrc
file and add at the end of file this two rows:
3. Download kernel - 2.6.32.9.
You can download kernel sources from J repo Doomlord or other repo, and extract to ~/kernel/, this kernels has already needed drivers etc.
4. Compile kernel:
When i'm compiling kernel i'm doing it in this way:
5. Output files.
6. Create boot.img
- Swap kernel and modules and then:
- Creat boot.img
Extract files here /usr/local/bin and set permissions to 755.

are u trying the impossible? lol.. if this is possible it should have happened before during the x10 days. you're just wasting your time bro.

dyepnoodle said:
are u trying the impossible? lol.. if this is possible it should have happened before during the x10 days. you're just wasting your time bro.
Click to expand...
Click to collapse
NO , im now learning C and C++ code
Look here a lot of people think Galaxy S plus will not get 3.0 , same you think for xperia 2011 phone , but look here its link for galaxy s plus 3.0.43kernel. Evertying is posibole only need siklz

It is possible.
3 devs are working on it
they got help from a Sony dev.
They know how to get it booting
1 dev is rewriting the clock for 2011 devices and an other the last board fixes and then it will boot

nickholtus said:
It is possible.
3 devs are working on it
they got help from a Sony dev.
They know how to get it booting
1 dev is rewriting the clock for 2011 devices and an other the last board fixes and then it will boot
Click to expand...
Click to collapse
can you give me link .
ps: how much mony your freind zack have?(for repair phone)
did you fix ril?(for sense 4.0A)

Hi, look at github.com/kamarush
3.0 kernel isn't updated in a few days, but they are still working on it
He has (not 100% sure) $12.00
Ril is still not working, waiting for help from htc devs
I dno why but the thread for donations is gone, without letting me know
Sent from my Xperia P using xda app-developers app

any update on this?

sjondenon said:
any update on this?
Click to expand...
Click to collapse
Here is backport of 3.0.8 form xperia s
https://github.com/tkymgr/KTG_test
Thats all,but we now have nAa on our side...i hope he will done it in future
here is naa sources LINK

N1kolaa, im available for testing/compiling anything, i cant code C, C++, i only know Java, can you set up an IRC channel so we can meet ?

For C let me know if you need help with it. I may not be of great help but can to some extent

Android 4.4 Kit Kat Discussion Thread

This thread is for the developers to discuss the bugs and problems of the kitkat development for the p990.

Nice that you created a thread for kitkat! Really thanks
So for the progress on cm 11:
It is really difficult to find the cause of the dark screen, because we can't get an adb connection to working. The devices don't show up with adb devices
Maybe it is disabled at the moment
We can't take all changes from your slimroms repo, because cyanogenmod toke another way in handling backward compatibility. So for now we have a dark screen with cm 11 and no adb

Here are some of the threads from other tegra2 devices which I'm following:
Galaxy R: link
Galaxy Tab 10.1: link
Captivate Glide: link
Xoom: link
P990: link
Additional T2 devices where I didn't see any Kitkat related threads, yet:
Eee Pad TF101: link
Atrix 4G: link
All still suffer from the same problems, we need some proper workarounds (in frameworks/native most likely) to fix the hot reboots before we can move on to fix the smaller problems.
I've posted in some of them in order to help with other problems (like the set_metadata one where I send the fix to @DJNoXD as well), but I have no idea how to fix the hot reboots currently.
Personally I don't see a use in fixing various stuff as long as the device is too unstable thanks to the reboots (that's why you won't find any 4.4 thread from my so far).
I'm just collecting some information in this thread to have everything together.
Therefore some more stuff regarding the device stuck at boot which we faced earlier as well:
tonyp said:
The only way to fix the blobs would be an update by nvidia / the vendors - which isn't happening obviously.
So you need to workaround the limitations of the old EGL in the sources to re-add compatibility (which btw had to be done for Android 4.3 and partly Android 4.2 as well).
The reason that CM11 doesn't boot up for you is that CM hasn't merged the required patches.
The commits do exist on CMs gerrit though:
http://review.cyanogenmod.org/#/q/s.../android_frameworks_native+branch:cm-11.0,n,z
They're new implementations of the CM10.2 patches by arcee.
Note that in some first tests the new ones didn't work for me on my tegra2 phone anymore - somethings seems to be broken in them for the tegra2 architechture.
The OmniROM has (had? I think they partly reverted it here) used forwardports of the old CM10.2 patches - which the SlimROM has merged as well in a similiar manner.
But this only fixes booting, I still do have way to many hot reboots so some more stuff has changed in 4.4 - which I didn't manage to fix or workaround so far.
What we need is someone with that kind of deep hardware knowledge.
All in all: Blindly changing blobs or other libs won't help here at all. Just building against different framework/native trees won't either.
The surfaceflinger and probably some more stuff in frameworks/native needs to get worked on in code.
Currently there doesn't exist a tegra2 device which fully works to my knowledge - and I'm following a couple ones like the Galaxy R, the Xoom, the Transformer TF 101, the Atrix and the Galaxy Tab 10.1.
I'm working on the 2x, but have way too less time at the moment to dig any deeper into the code - while the current ROM boots (using my frameworks/native repo here) and has a working ril, wifi & storage it's nowhere near a daily driver thanks to frequent hot reboots.
Click to expand...
Click to collapse
Edit: Reminder: Do not spam in this forum section!
I will delete all "thanks" posts or similiar non-development related ones without a comment.

When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
I think if we could find the commits that broke the stability we could search for a work around or fix. I already tried it only for the sufaceflinger but i had no success, because it still worked properly, so it maybe is related to libgui or i think libui?
Took me hours for the surfaceflinger, so it will take even more time for all other in framework native. When i found some time during the week, i will try.
But KitKat is awesome related to RAM, Multitasking and performance.
Gesendet von meinem LG-P990 mit Tapatalk

Evervolv frameworks/native etc were no help getting the tf101 to boot omni. So far we're at Boot Animation
thx to
kishoreinme said:
Having the 3 perfhud .so files in /lib/egl/ causes this. Delete them and it boots
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/showthread.php?t=2517719&page=9
http://forum.xda-developers.com/showthread.php?t=2489841&page=7
Firtecy said:
When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
Gesendet von meinem LG-P990 mit Tapatalk
Click to expand...
Click to collapse
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?

dlumberg said:
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?
Click to expand...
Click to collapse
These are the repos that I use for slimrom:
https://github.com/p990-slimrom/

Here is the GalaxyR Omni 4.4.2 development link
http://forum.xda-developers.com/showthread.php?t=2576793

Eeeeh, have I been gifted with a special P990?
I've flashed Tonyp's 4.4 build named cm-11-20131213-UNOFFICIAL-p990 and I am pretty much facing no bugs. Only bug I could find on this fine evening was that USB doesn't get mounted, it charges when connected though.
Sound works, camera works, external SD card works, WiFi works, I bet GPS works but testing that will have to wait till the morning. All of this is on a clean CM11 build without doing any modifications at all. I too am still shocked over this and since I couldn't believe it myself, so I figured I'd post a video bringing this to light.
Short YouTube footage of my P990 running KitKat: YouTube
Could someone do a full wipe and see what they come up with by flashing that same build? It seems rather surreal if 4.4 only works this well on just my phone.
Please note, I have not been under the developmental processes of this project. This is simply testing - all credits to the developers!

USB tether will not work under windows because there are no drivers found. And it works fine under linux. How to fix the hardware id (vid,pid)?
Sent from my XT875 using XDA Premium 4 mobile app

ASUS Zenfone 2 ROM

USB Driver
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE550ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip.secure
ZE551ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip.secure
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/zenfone2_2_12_40.zip

Great!! Looking forward for great dev support..

Fire code said:
USB Driver
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE550ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip.secure
ZE551ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip.secure
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/zenfone2_2_12_40.zip
Click to expand...
Click to collapse
Links for ZE551ML and ZE550ML ROMs are broken.

BACKUP
Quote:
Originally Posted by Fire code
USB Driver
https://drive.google.com/open?id=0B-1_qo5woThsQkNWQnVwZG9CVzA&authuser=0
ZE550ML ROM
N/A(sorry ~i didn't backup this~ )
ZE551ML ROM
https://drive.google.com/open?id=0B-1_qo5woThsTnM3bjQxaHJoUzg&authuser=0
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/Zen...e2_2_12_40.zip
https://drive.google.com/open?id=0B-1_qo5woThsOHhkTUNEUFItdFU&authuser=0

I can't wait tell I get this device. Nothing but good old cyanogenmod and aosp roms.
Sent from my SM-T230NU using XDA Free mobile app

Anyone rip any apps out and had success with them running on AOSP yet?

Do you guys think there will be an Ubuntu Touch edition for the ZenFone 2? It has an Intel CPU, I really wish that.

update link
USB Driver:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE500CL
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/UL-ASUS_Z00D-WW-12.16.4.3-user.zip
ZE550ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.11-user.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip
ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.11-user.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip

hp420 said:
Anyone rip any apps out and had success with them running on AOSP yet?
Click to expand...
Click to collapse
You can get some ZenFone 2 apps From :-
I have deodexed rom.
and ported some apps and they are working flawlessly on CM11 without any bug.
http://forum.xda-developers.com/and...enfone-2-apps-port-root-t3073195#post59906345

ThunderSky7 said:
You can get some ZenFone 2 apps From :-
I have deodexed rom.
and ported some apps and they are working flawlessly on CM11 without any bug.
http://forum.xda-developers.com/and...enfone-2-apps-port-root-t3073195#post59906345
Click to expand...
Click to collapse
Deodexed rom meaning you have a zenfone 2 stock deodexded rom? Do you have a link to it or the rom is private?

You should add screenshots.. :good:

thanks for drivers

sooo much repo'ing to get AOSP before the compiling even begins. There's gotta be a better way for them to maintain the repository. :/
Edit:
After downloading around 40 gigs of files from AOSP, won't compile on our phones. Looks like build tools are only 64-bit and the Debian Jessie chroot I'm using on the phone isn't allowing the 64-bit tools to execute. Our kernel reports that it IS in fact x86_64, but I can't seem to find the phone's /lib64 directory to map to the chroot. So, something that could be fun is now a huge headache -- may need to put together a pc just to build this kernel & hope I still have enough bandwidth from my ISP to repo another 40 gigs.

ycavan said:
sooo much repo'ing to get AOSP before the compiling even begins. There's gotta be a better way for them to maintain the repository. :/
Edit:
After downloading around 40 gigs of files from AOSP, won't compile on our phones. Looks like build tools are only 64-bit and the Debian Jessie chroot I'm using on the phone isn't allowing the 64-bit tools to execute. Our kernel reports that it IS in fact x86_64, but I can't seem to find the phone's /lib64 directory to map to the chroot. So, something that could be fun is now a huge headache -- may need to put together a pc just to build this kernel & hope I still have enough bandwidth from my ISP to repo another 40 gigs.
Click to expand...
Click to collapse
It's already several years ago Android build tools migrated to x64-only. So, you cannot build Android (even 32bit version) on x32 machine.
Zenfone 2 kernel is 64bit. But Android itself is 32bit. You still can start 64bit binaries if you want. I'm using 64bit busybox and some other utilities I've made.
I didn't try to compile Zf2 kernel yet because there is no unlocked bootloader exist, so you simply can't boot your own kernel.

I was able to apt-get lib64 on debian jessie ( was called libc6-amd64 ) & that moved things along until the assembler refused to load libz.so. No amount of looking around helped figure that one out since libz.so did exist.
This is just something fun to do while waiting for the unlocked bootloader. Wouldn't it be nice to be able to just compile your own kernel on your phone?

Compilation requires a lot of typing in command line. I cannot imagine doing this on phone. It's simply crazy. I'm not even talking about time needed for compilation.
I'm using PC (with linux VM) to compile everything.

sorg said:
Compilation requires a lot of typing in command line. I cannot imagine doing this on phone. It's simply crazy. I'm not even talking about time needed for compilation.
I'm using PC (with linux VM) to compile everything.
Click to expand...
Click to collapse
@sorg..so currently is there anything that you have produced for zenfone 2? and is it possible for this phone to be developed once asus release and unlock the BL?

cangcan said:
@sorg..so currently is there anything that you have produced for zenfone 2? and is it possible for this phone to be developed once asus release and unlock the BL?
Click to expand...
Click to collapse
Yes, i've compiled many binaries already.
Of course it's possible to develop for ZF2. There is ASUS Nexsus Player (fugu) device in CM12 repository which is basically very close to ZE550/ZE551. So, there is already a lot of code in Cyanogenmod. But, i prefer stock ROM anyway.

sorg said:
Yes, i've compiled many binaries already.
Of course it's possible to develop for ZF2. There is ASUS Nexsus Player (fugu) device in CM12 repository which is basically very close to ZE550/ZE551. So, there is already a lot of code in Cyanogenmod. But, i prefer stock ROM anyway.
Click to expand...
Click to collapse
That's good news sorg, great to know you've been getting some code flowing while waiting for the bootloader unlock tool.:thumbup: I'll have to check out your repositories when I get the chance, especially since I wanted the device tree for my rom projects.
Sent from the Ace's MB865 using Tapatalk

edit: nvm

[DEV][G925F] CyanogenMod 12.1 Development

Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
​

Reserved

i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)

vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.

add me as participant to the repos ^^
https://github.com/OldDroid

OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them

Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.

mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?

nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support

First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying

mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then

Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer

Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?

Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself

mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk

lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset

Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.

mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.

-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes

mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.