Database Develop

4.2.2 Discussion Thread

Any conversation having to do android 4.2.2 goes here. If the ROM you want to talk about has a thread. Then go there!

Here is my PAC rom. can someone please test this? Just flash it like any other 4.2.2 rom. wipe then flash rom and then GAPPS. Please tell me if it boots and if you have time could you obtain a logcat?
http://d-h.st/9jb

Mobile Data seems on my version seems to be connected, but instead of toggling Mobile Data on and off the H just keeps appearing and disappearing.. But it says AT&T in the notification drawer. I will flash your version and try it out once its done downloading.
---------- Post added at 03:12 PM ---------- Previous post was at 02:17 PM ----------
camo_flage said:
Here is my PAC rom. can someone please test this? Just flash it like any other 4.2.2 rom. wipe then flash rom and then GAPPS. Please tell me if it boots and if you have time could you obtain a logcat?
http://d-h.st/9jb
Click to expand...
Click to collapse
First try, stuck on bootscreen.. flashed rom, gapps then 6/30 kernel, will try reflashing with just rom and gapps initially.
Whats the easiest way to get a logcat? I'm still not too sure how to make those of use but I know they are handy
---------- Post added at 03:43 PM ---------- Previous post was at 03:12 PM ----------
Second try, sticks at bootscreen for +10min still. Flashed rom then gapps.
Here is my version that boots, mobile data doesnt work but I can send and recieve texts, and WiFi works... Also no storage.
http://d-h.st/qYQ
Flash ROM zip then gapps, booted within a few minutes for me.

calikevin said:
Mobile Data seems on my version seems to be connected, but instead of toggling Mobile Data on and off the H just keeps appearing and disappearing.. But it says AT&T in the notification drawer. I will flash your version and try it out once its done downloading.
---------- Post added at 03:12 PM ---------- Previous post was at 02:17 PM ----------
First try, stuck on bootscreen.. flashed rom, gapps then 6/30 kernel, will try reflashing with just rom and gapps initially.
Whats the easiest way to get a logcat? I'm still not too sure how to make those of use but I know they are handy
---------- Post added at 03:43 PM ---------- Previous post was at 03:12 PM ----------
Second try, sticks at bootscreen for +10min still. Flashed rom then gapps.
Here is my version that boots, mobile data doesnt work but I can send and recieve texts, and WiFi works... Also no storage.
http://d-h.st/qYQ
Flash ROM zip then gapps, booted within a few minutes for me.
Click to expand...
Click to collapse
Damn must have did something wrong
---------- Post added at 08:17 PM ---------- Previous post was at 08:04 PM ----------
camo_flage said:
Damn must have did something wrong
Click to expand...
Click to collapse
Well I think you should contact albinoman to help sort out the issues...for now I will try to build AOKP because you seem to have PAC covered
Also I am going to switch devices to the amaze for the port because the Vivid and the Amaze are 99% the same internally. Unfortunately, the Amaze does not have a PAC rom . Dang I wish homeslice would come back to the Vivid and help us out with this.

Log cat...
Connect to PC
Make sure adb works...
Type adb logcat
Orrr
Type adb logcat > yourfilename
Sent from my Vivid 4G using Tapatalk 4 Beta

Calikevin I think you have to start building from source now if you want to fix the issues in PAC
Sent from my Vivid 4G using xda premium

I have built CM10 itself from source, but I have no idea how to go about combining source from the port I want into the CM source, that's still a little advanced for me but I will try and figure it out nonetheless
Sent from my Vivid 4G using Tapatalk 4 Beta

Yea that's what I was worried about too.
Sent from my Vivid 4G using xda premium

I am currently syncing the SlimBean repo right now to get started on combining the source but if anyone has any useful links or advice I would greatly appreciate the input

You guys taking requests?
I'd love to see Vanilla Rootbox...
Sent from my Vivid 4G using Tapatalk 4 Beta

rignfool said:
You guys taking requests?
I'd love to see Vanilla Rootbox...
Sent from my Vivid 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't see why not, I've got a few ideas of my own already, I'm this close to having BAKED holiday built, then I would like to see about Illusion.. I did see Vanilla Rootbox too, I'll check it out.

I'm happy that the Vivid development is still alive. Installed the rom, and its running smoothly. Rogers variant.

arzzzae said:
I'm happy that the Vivid development is still alive. Installed the rom, and its running smoothly. Rogers variant.
Click to expand...
Click to collapse
Check the link in my sig for the most updated Slim release

calikevin said:
Check the link in my sig for the most updated Slim release
Click to expand...
Click to collapse
Will do! Anyways, how do I decrease the overall font size for 4.2.2? It seems missing from the settings.
Edit: Seems like the whole "display" under the settings is missing.
Edit #2: Nevermind, I'm stupid. Found it.

Yea, still working in figuring out the Display force close, it would seem that an entire chunk of android 4.2.2 is missing from the ROM, probably has to do with the vivid.. 4.2.2 has Daydream, and its there in this ROM too but you usually need to go to Display settings to see the options and ours isn't there, but I was able to access the Daydream settings by going through the DashClock settings. Very odd, hopefully sultan or albinoman have some ideas about that
Sent from my SlimBean Vivid 4G using Tapatalk 4 Beta

android1234567 said:
You can delete the useless device trees by modifying the default.xml file (platform manifest) located in .repo/manifests
Click to expand...
Click to collapse
After adding an htc holiday device folder to the .git folder and trying to run git commit -a I keep running into this same error, any idea?
Code:
fatal: 'git status --porcelain' failed in submodule device/htc/holiday

calikevin said:
After adding an htc holiday device folder to the .git folder and trying to run git commit -a I keep running into this same error, any idea?
Code:
fatal: 'git status --porcelain' failed in submodule device/htc/holiday
Click to expand...
Click to collapse
Don't mess with the .git folders. The only file you have to modify to alter the entire source is .repo/manifests/default.xml
You can add and remove device trees by modifying that file, and you can change where existing device trees are fetched from (i.e. you can make an existing device tree be fetched from a different GitHub account instead).

android1234567 said:
Don't mess with the .git folders. The only file you have to modify to alter the entire source is .repo/manifests/default.xml
You can add and remove device trees by modifying that file, and you can change where existing device trees are fetched from (i.e. you can make an existing device tree be fetched from a different GitHub account instead).
Click to expand...
Click to collapse
Thank you!
So for instance.. this is in the default xml for Baked-
Code:
<remote name="baked"
fetch="git://github.com/TeamBAKED/" />
If I change that address to my github address, I will be able to repo sync and git commit from my own repo, and be able to upload the device trees you were trying to take a look at?
And it's safe to take out every one of these except holiday since that's all I'm building for?
Code:
<project path="device/htc/m7ul" name="device_htc_m7ul" remote="baked" revision="jb-4.2" />

My wife has and A&T HTC Vivid phone. She is a huge Instagram fan and was quite excited to see the new video clip feature that was recently introduced to the application. Her phone was running stock ICS and, unfortunately, Instagram video is not functional for anything less than Android Jellybean (at least that is my understanding). The video button doesn't appear in the application under ICS. I don't like messing with my wife's phone but I was forced to make the move to Jellybean.
First stop was PAC-man 4.1.2. The video option shows up in Instagram and videos can be recorded. However, when trying to apply filters the video won't play back properly (either dosn't play back, choppy, or pixelated) and 90+% of the time it ends up causing the phone to freeze/reboot. Not good.
Next stop was the new CM10.1 AOSP 4.2.2 rom. I noticed that video recording had been fixed with this rom. The video option shows up in Instagram and videos can be recorded, same as in PAC-man. The good news is that filters can somewhat be applied and the video will play back better with this rom. There are still issues with the play back causing some of the frames to dance around the screen, however, it no longers crahes the phone. It has crashed the Instagram application but, in general, things can somewhat work but not to the degree to which they should (and definitely not to the degree my wife would find acceptable). I have recorded and played back video using the stock camera app and everything functions smoothly with no hiccups so it is seems that the problem lies in how Instagram is interfacing with the playback capabilities of the phone, using a series of calls that the playback mechanism doesn't quite like. What, if anything, can I do to provide feedback to the developers of CM10.1 that would give them some indication of how Instagram is trying to work with the play back capabilities of the phone? Would a logcat give some indication? What kind of debugging would I need to turn on (if any)?
As a frame of reference, I use CM10.1 4.2.2 Maguro on my Samsung Galaxy Nexus phone. I have the Instagram app installed and the video recording capabilities work smoothly and without an issues within it. Applying filters to videos works perfectly and I haven't had a single crash. I know that this is different hardware but if there is anything that can be leveraged from that rom please let me know.
I must say that development of CM10.1 is moving along at a very rapid pace and, for the most part, it is functioning extremenly well and stable on my wife's phone. The only thing I noticed was that CM10.1 lagged only slightly when compared with PAC-man when responding to screen swipes. I'm sure this will improve with time and I am quite thankful to those developing it for breathing added life into this phone.
Again, I would like to get Instagram working smoothly with the HTC Vivid so suggestions as to what I need to provide to the developers would be greatly appreciated. I haven't made enough posts to the xda-developers forums so I am unable to post to the development threads. Any feedback I create will need to go thru here so hopefully I can get some assistance to get it to the right developers.
Edit: the new 0715 cm 10.1 has fixed the instagram video issues when applying filters to a video. Everything seems to be running smoothly now. My wife is asleep and doesn't know this yet, but I'm sure she'll be quite happy in the morning. Many thanks to the developers. Great job!
Sent from my Galaxy Nexus using Tapatalk 2

Screen flicker with New GMapps 7.0
Am getting a screen flicker 80% of the time during maps session (not lighting, actual flicker of maps). It is to the point of not being able to use maps at all. Anyone else?
Assuming not alone:
Appear to have solved it with "Disable HW Overlays", so can only assume this is related to the soft reboots, and associated memory map issue, as I would be surprised that GMaps wouldn't play well with 4.2.2.

Android AOSP 4.3 Compiled for Xperia Z

Since everyone always loves MOAR VERSION NUMBAH...
Android 4.3 for the Xperia Z. With a BIG shout out to Sony Mobile for hosting their own git repository for their deviceshttps://github.com/sonyxperiadev/device-sony-c6603.
This is compiled from AOSP, and has nothing done beyond that. Simply added the Sony repo to Android 4.3 AOSP, and built. As per the Sony AOSP releases, this does not have functional Radio (no phone calls or SMS!!!) or indeed any connectivity.
Working:
Wifi
Not Working:
Mobile network
Bluetooth
I will not tell you how to make mobile network work, but it is not difficult and just involves some binary blobs from memory... Sony don't have the right to distribute those officially, so I won't do it either
In light of this not being a working build, I will not post it as a zip, but as fastboot flashable images. Unlocked bootloader only. C6603 was used to test, other models entirely at your risk (ie. don't bother).
Links:
All files needed are in
http://goo.im/devs/pulser/XperiaZ/4.3AOSP
and will appear there shortly (upload done, it's still propogating)
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
Top secret information:
Yes, you are also permitted to use this... Yes... that's right, you can use it!
To install:
fastboot flash boot boot.img
fastboot flash system system.img
(optionally, I did it, shouldn't be needed)
fastboot flash userdata userdata.img
fastboot flash cache cache.img
Build instructions to replicate :
Get android 4.3 sources.
Get sony c6603 information on repositories and add to local_manifests for 4.3
Get latest v3 blobs for phone and tablet Z
Put them into vendor/sony/
Repo sync
Make

You sir are 1 step ahead of me. Thanks man. Is it ok if i can use these?

Taylor_Swift said:
You sir are 1 step ahead of me. Thanks man. Is it ok if i can use these?
Click to expand...
Click to collapse
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
Click to expand...
Click to collapse
Oops, I forgot to add "use" to that list.
Yes, they can also be used! I shall add "use" to the list
Links not working yet, but I gave them a kick

pulser_g2 said:
Oops, I forgot to add "use" to that list.
Yes, they can also be used! I shall add "use" to the list
Links not working yet, but I gave them a kick
Click to expand...
Click to collapse
Oh i sent you a PM too lol. Sorry but XDA members are really tight when it comes to sharing so when I read that I couldnt believe you said it lol

Taylor_Swift said:
Oh i sent you a PM too lol. Sorry but XDA members are really tight when it comes to sharing so when I read that I couldnt believe you said it lol
Click to expand...
Click to collapse
Lmao... They might be, I'm not... I just typed a few commands, tweaked a couple of stupid errors I made, and it was done.

You are also missing the Camera and getting RIL to work requires more than dropping in some blobs.
I already merged 4.3 in my repo: https://github.com/adrian-bl-yuga

pabx said:
You are also missing the Camera and getting RIL to work requires more than dropping in some blobs.
I already merged 4.3 in my repo: https://github.com/adrian-bl-yuga
Click to expand...
Click to collapse
Yeah, camera blobs are not "officially" made available by sony.
I had just spotted your repo actually and was going to see if it had the RIL etc

So glad I ditched Samsung for Sony :beer:
Sent from my C6603 using xda app-developers app

Congrats on the first non-nexus release of 4.3 I do not have this device but would like to congratulate you

Nicely done! I am happy i bought this device!

when it will be a coumpleterom?

Someone provide galaxy s3 to this AWESOME guy

LegendM said:
Someone provide galaxy s3 to this AWESOME guy
Click to expand...
Click to collapse
No thanks, got plenty of devices, and I have the N7100 (Note 2), which is very similar in hardware to the S3. Exynos is nothing like as easy to do this to, that's why Sony devices are first!
Honestly, it was easier to get this booting on my Z phone and Z tablet, than it was on a Nexus 10 (an official Nexus device!)

pulser_g2 said:
No thanks, got plenty of devices, and I have the N7100 (Note 2), which is very similar in hardware to the S3. Exynos is nothing like as easy to do this to, that's why Sony devices are first!
Honestly, it was easier to get this booting on my Z phone and Z tablet, than it was on a Nexus 10 (an official Nexus device!)
Click to expand...
Click to collapse
We welcome you to the xperia z development scene with open arms

spazzy1912 said:
We welcome you to the xperia z development scene with open arms
Click to expand...
Click to collapse
Thanks Though actually I've been here since the very start, around the very start of the shipments of the Z

FYI: I uploaded my first 4.3 based build:
http://forum.xda-developers.com/showthread.php?p=42084058
I got all hardware working, there are only some minor issues (no 4.3 gapps (using a patched 4.2) and the AOSP voice dialer is hanging (known aosp bug on BT devices).

pabx said:
FYI: I uploaded my first 4.3 based build:
http://forum.xda-developers.com/showthread.php?p=42084058
I got all hardware working, there are only some minor issues (no 4.3 gapps (using a patched 4.2) and the AOSP voice dialer is hanging (known aosp bug on BT devices).
Click to expand...
Click to collapse
Nice to see! You are aware you should be able to make a new GApps package from the factory images? I don't use GApps though, so I haven't done it. But it should be easy enough to do.

I had to see, the recovery is not accessible .... this risk is all the same and no current mod will work with this rom, I'll wait another is, I think,
but thank you for your great job :good: !

In light of there being a supported/maintained 4.3 AOSP for Xperia Z, consider this discontinued.
Indeed, @pabx 's ROM makes the Xperia Z pretty much Nexus standard, in terms of the hardware support. Most impressive from Sony! As such I will close this thread now.

About Android M Source

i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?

I pulled the source via repo, but I haven't got around to a build yet.

Gene Poole said:
I pulled the source via repo, but I haven't got around to a build yet.
Click to expand...
Click to collapse
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?

opssemnik said:
i noticed that a lot of projects on android.googlesource.com already have the android-m tag, including
plataform/system/core
plataform/build
plataform/frameworks/base
so i think if these non gpl projects are updated with M code, is the source code fully complete? can anyone check if we can already update and build M roms?
Click to expand...
Click to collapse
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.

F4uzan said:
I couldn't get it to build (could be an issue on my side, tho). So I guess it's better to wait for the official announcement before building.
Click to expand...
Click to collapse
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing

cell2011 said:
Would you be able to build roms off of M source? Is it enough source or is it better to wait for new update and factory images? Since the bootloader and radio is the same as that of 5.1.1 shouldn't gapps work?
Click to expand...
Click to collapse
gapps relly on the system framework (sdk), radio and bootloader rely on nothing, they control the device in a really low level state, in fact the bootloader is the lowest level, since it starts the kernel.
Sometimes radios/bootloader causes issuses depending on the combination but thats because of the blobs system wise, not because of the os version.
And gapps were updated on M

opssemnik said:
ok thanks, thanks to my "great" internet (10mbps) i didnt want to loose a full day just syncing
Click to expand...
Click to collapse
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.

F4uzan said:
So my whole day sacrifice is worth it then (I synced for like, a day or two).
Anyway, I've seen some component gets android-m-preview tag. Google might be pushing it real soon.
Click to expand...
Click to collapse
Does anyone happen to see what android ver this will be? 5.2?

cell2011 said:
Does anyone happen to see what android ver this will be? 5.2?
Click to expand...
Click to collapse
Nah, just m-preview. It's just like L, the development tag is l-preview.

F4uzan said:
Nah, just m-preview. It's just like L, the development tag is l-preview.
Click to expand...
Click to collapse
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.

dekefake said:
M preview is 5.1.x for sure. Look at the SDK number : 22, like Android 5.1
I'm almost sure you can build Android M from AOSP, and thats why :
I know the difference between Android 5.1.1 and M is very little, just a few adds, i seen somewhere, speaking of less than 20MB of changed files.. So, try to sync a repo with Android 5.1.1 AOSP, and add the M commits and try to build, to see.
If it builds for Nexus 5, so i can be built for any other device supported by AOSP 5.1.1.
Click to expand...
Click to collapse
Thanks for pointing out ! I totally missed the point that the SDK version is still 22.
I'll try rebuilding M again, the fault could be on my side.

So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5

cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
---------- Post added at 06:34 AM ---------- Previous post was at 06:20 AM ----------
This is what member defconoi says about doing a port for the N4. All that needs to be done is to take the nexus 5 image and replace the binaries with the mako binaries preview and then use the nexus 4 m kernel. That's what I did when porting L. I don't know if this can be of any help pertaining to our N5
Click to expand...
Click to collapse
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M

opssemnik said:
just remember, the n4 dosen´t have an updated kernel source tree with M tag, just the binary, so you guys will need to update the ramdisk for M
Click to expand...
Click to collapse
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is

cell2011 said:
Are you working on a build for our N5? Someone on android development has a flashable stock of M deodexed version coming soon its not out yet but the post is
Click to expand...
Click to collapse
im just thinkering with it, nothing for public release.
however you guys can use ext4 image unpacker to work directly with the factory images
http://i.imgur.com/T9SCUSR.png

cell2011 said:
So will this be a build off of 5.1.1 and M if it can be done?
Click to expand...
Click to collapse
I think a combo build with 5.1.1 - M is possible, adding M commits to a 5.1.1 source code, and then, try to build.

[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.

Android nougat 7.0 source code releae

any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0

Arjunfire said:
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Click to expand...
Click to collapse
you can make

I think he asked that because he cant do this. But I think it is only a matter of time until something will be released. At least I hope so.

I want it

Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:

rayzen6 said:
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
Click to expand...
Click to collapse
I think there will be no drivers for Spadragon 800/801...?

Athanatos81 said:
I think there will be no drivers for Spadragon 800/801...?
Click to expand...
Click to collapse
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .

I hope stil working on s5 sm g900f

Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...

rayzen6 said:
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
Click to expand...
Click to collapse
Yup but i guess it can be done without vulkan api. As in nexus 4 port.

kardinal969 said:
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
Click to expand...
Click to collapse
That's what I said brother

freibergisch said:
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
Click to expand...
Click to collapse
it is possible to update drivers for gpu if you have an unlocked bootloader and are on mm aosp rom

Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte

Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
chippinganimal said:
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Click to expand...
Click to collapse
They should

Paoletti said:
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
They should
Click to expand...
Click to collapse
Alright, got ubuntu installed (windows partition had a heart attack afterwards lmao) so now Ill do my best to follow that guide and see what happens i guess... Should build pretty fast since this machine has a i7 3770 and 16gb of ram and it seems the guide says 8gb of ram is fine.

Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?

chippinganimal said:
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
Click to expand...
Click to collapse
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up

Paoletti said:
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Click to expand...
Click to collapse
This is a git thing. Basically the branch name has changed. It's now in the staging branch so:
-b staging/cm-14.0

Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613

rayzen6 said:
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
Click to expand...
Click to collapse
We want to try that build, beta, alpha or wathever it is. We just want to try it, feel nougat in our hands, we want a download link for that build, even if it isn't stable, daily usable and public. We want that, we must have that.