Database Develop

Nexus 7 4.1.2 update rolling out.

Android police just announced that a 4.1.2 update has been released to AOSP, and the Nexus 7 is apparently already receiving it!
We're releasing Android 4.1.2 to AOSP today, which is a minor update
on top of 4.1.1.
As a note to maintainers of community builds running on Nexus 7: please update to 4.1.2 at the first opportunity. Future variants of the grouper hardware will have a minor change in one of the components (the power management chip) that will not be compatible with 4.1.1.
The build number is JZO54K, and the tag is android-4.1.2_r1.
Enjoy,
Conley and JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Update #1: 4.1.2 has already started rolling out to the Nexus 7, though mine doesn't see it yet.
Update #2: Since I mentioned seeing 4.1.2 with this very build number in the server logs, I'll throw in the devices that I saw running it, in addition to the Nexus 7 (this doesn't mean the updates for them are out now, but rather a good indication of what's to come):
Are we ready?

JellyBean 4.1.2, the incremental follow up to 4.1.1 isn’t a major update by any means, but promises to improve performance, increase stability and fix certain bugs.
It also adds rotation ability to the homescreen, something that wasn’t possible in the previous version of the software.

Could someone please post a dump of this (or point me towards the easiest way to download it while running a custom ROM on my N7)? I'd like to hack away at pulling out the launcher and making an update.zip for it.

Hi everyone, I hope this update will fix the lag problem with few mb/gb free on my N7.
I dont want to flash the factory image cause it wipes everything.
If I flash a nexus 7 stock rooted odexed will I receive the update? What do u suggest?

Hopefully Google fixed the bad display calibration!
http://tinyurl.com/8ouzlks

dragpyre said:
Android police just announced that a 4.1.2 update has been released to AOSP, and the Nexus 7 is apparently already receiving it!
Are we ready?
Click to expand...
Click to collapse
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now, I will soon I'm sure,
JBQ also said that the updated factory images will be available as soon as the OTA is, and that the change can be pulled from the commits in the repository..
That's all for now.

So I have my Nexus 7 rooted and unlocked running stock software, will I be fine to get the OTA?
Sent from my Nexus 7 using xda app-developers app

rootusr said:
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now, I will soon I'm sure,
JBQ also said that the updated factory images will be available as soon as the OTA is, and that the change can be pulled from the commits in the repository..
That's all for now.
Click to expand...
Click to collapse
No OTA is available now!

rootusr said:
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now
Click to expand...
Click to collapse
Actually, there are many reports of Nexus 7 users getting the update so it is rolling out now. It also adds home screen rotation to the stock launcher.

ezegm said:
So I have my Nexus 7 rooted and unlocked running stock software, will I be fine to get the OTA?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think you will get the update-notification at least..
The question is if a custom-recovery prevents updating.
edit: xda-user dalew729 says he uses CWM and updated OTA without problems....

rockvoid said:
No OTA is available now!
Click to expand...
Click to collapse
Unfortunately, because I'm new i can't post links. If you check the other 4.1.2 thread, and follow the Android Police link, you'll see screenshots detailing this.

dragpyre said:
Unfortunately, because I'm new i can't post links. If you check the other 4.1.2 thread, and follow the Android Police link, you'll see screenshots detailing this.
Click to expand...
Click to collapse
sorry i wanted to post "no, OTA is available now!"

rockvoid said:
sorry i wanted to post "no, OTA is available now!"
Click to expand...
Click to collapse
I'm going from Glazed JellyBean back to stock for this! XD

bozzykid said:
Actually, there are many reports of Nexus 7 users getting the update so it is rolling out now. It also adds home screen rotation to the stock launcher.
Click to expand...
Click to collapse
Yeap, that is what Im Looking now, no word about that from JBQ but there are those reports, No update for me yet.

Saw the 4.1.2 being reported on twitter. Has me all tingly, curious to see what else is included besides home screen rotation. Currently running Codename android rom so I have to wait. :fingers-crossed:

rootusr said:
Yeap, that is what Im Looking now, no word about that from JBQ but there are those reports, No update for me yet.
Click to expand...
Click to collapse
JBQ has nothing to do with the OTAs so he will not be announcing it.

I really can't wait to try this update out!
Unfortunately, I'm not getting any OTA updates. D:

http://forum.xda-developers.com/showthread.php?t=1928731
Beaten by 2 minutes.
Closed

Guardian Rom [Secure] [Privacy] [Preview]

Guardian Rom by x942​Thanks to:​
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?​
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?​
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:​
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
​
Click to expand...
Click to collapse
How to use:​
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:​Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.​

Reserved.

you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid

baz77 said:
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
Click to expand...
Click to collapse
I may use SeAndroid. Right now I am focusing on the encryption side of things instead of the exploit mitigation side. That will come later.

Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴

azrash said:
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
Click to expand...
Click to collapse
Awesome! Thanks! It's is based off the latest repo. I simple pulled and than modified the sources. I am currently getting some hosting for our own repo and Tor Hidden service for downloading. Stay tuned much more to come.

TimeAndroid said:
Look'in good, might try.
Click to expand...
Click to collapse
The next build will have an AOSP 4.2.2 base with Mobiflage built in. Also Lock screen PIN and Pre-Boot PINs are now separated. So you can use a simple 4 digit pin on the lock screen and a 32 character pin at boot.
Also for more security you have to passwords one for the "outer volume" which you use as you daily usage and one as "hidden volume" which is your hidden os. You use the second for anything sensitive. That way if an attacker tries to force you to give up your password you just give up the outer volume (decoy) password. There is no way to prove the hidden volume exists.
Encryption also uses AES-256-XTS now instead of AES-128-CBC. Better key length and protection against watermarking attacks.
EDIT: If anyone wants early access please PM. The build is not ready for prime time as there is no GUI for encryption but can be used as a daily driver.

SecUpwN said:
No, I'm sure you're right. But since he explicitly stated that he won't build an ('unofficial') AOKP version, I'm looking for a way to get in the favor of the securiry modifications without gaving to switch to another ROM. It's just that AOKP has so many cool simplifications compared to CyanogenMod, I'd like to avoid a switch backwards. Maybe he could create an unsupported AOKP version every month? Possible?
Click to expand...
Click to collapse
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta

DontPushButtons said:
I'm guessing the modifications he has been making go a little further beyond a flashable zip. Otherwise he would've done that instead of making a whole rom around privacy.
Could be wrong..
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. I custom kernel is needed at the very least. Not to mention removal of Google Apps and tweaked UI for encryption (mobiflage). All of these are OS level tweaks and cannot be made into a ZIP.
droidkevlar said:
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. AOKP will NOT be supported. EVER. If anyone wants a different base download the source code from my github and compile it yourself. Build documentation is on there. Furthermore AOKP and CM10.1 are both great roms, however there are too many variables. Both have a ton of unneeded binaries and settings. We cannot guarantee security are these builds. We choose CM10.1 because it's fully open source and has fewer complications then AOKP. On NEXUS devices we are using AOSP modified with our security tweaks. On non-nexus we use CM10.1 for now for simplicity.
I am hoping with the recent Google Edition devices it will be easier to port/compile AOSP onto those devices.
TL;DR:
WE WILL NEVER OFFICIALLY SUPPORT AOKP.
Thanks for understanding.This message is only meant to stop these requests, not to be rude so please don't take it that way.

Cleaning
This thread is in the DEVELOPMENT section. And is for the "Guardian Rom [Secure] [Privacy] [Preview]".​
If you need to report an issue or bug then READ THIS POST ABOUT BUG REPORTS
Keep ALL posts aimed at the ROM development.
This thread is NOT A Q&A thread.
So don't ask why the WiFi won't work, post a LOGCAT of the actual event or it did not happen.
I have cleaned this thread.
If you repeatedly make junk posts, then INFRACTIONS will follow.
~JAB

Hey @x942, where is our Android 4.3 version of this funky ROM?

SecUpwN said:
Hey @x942, where is our Android 4.3 version of this funky ROM?
Click to expand...
Click to collapse
We are working toward this. The issue we are having is that while 4.3 is latest 5.0 may be just around the corner. We don't want invest a ton of effort just to have re-port everything to 5.0 if it's released 2-3 months from now. That's not to say 4.3 won't happen. It's just we are focusing on adding more security. For now stable is 4.2.2.:good:

Am I missing where to find the flashable zip?
Sent from my Nexus 4 using xda app-developers app

Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?

koz said:
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
Click to expand...
Click to collapse
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.

Request
Hi,
Please add the new moto g xt1032 to your list of planned devices - it would be a great way to get more people secured as it is a very popular handset
Thanks for all your hard work!

x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
Has this ever been developed for the Galaxy S3? I haven't been able to find a download anywhere...

@X942 gaurdian rom sounds very interesting to me. would also like the att slll i747 to be added on list for consideration for dev.
am not a dev myself.
thank you for your work/time/energy. :thumbup:
err on the side of kindness

good
Sent from my Nexus 4 using XDA Premium 4 mobile app

x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
I cant find a download for the Note 3 ROM. The only thing I read about it is an update on http://shadowdcatconsulting.com/blog/ saying that support will come soon.

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

[5.1.1-LMY48I] Updated GPU Drivers from qualcomm (02/sept.)

Qualcomm posted a few days ago a set of new drivers for our nexus 5, this time its for 5.1.1 LMY48I
no changelog provided.
Source: https://developer.qualcomm.com/download/adreno_nexus_sept2015.zip
Download(specific zip for the nexus 5, tested under TWRP and Chroma rom):
https://drive.google.com/file/d/0BwduAK2l37OaNmlqcDNZcjVTc1k/view?usp=sharing

opssemnik said:
Qualcomm posted a few days ago a set of new drivers for our nexus 5, this time its for 5.1.1 LMY48I
no changelog provided.
Source: https://developer.qualcomm.com/download/adreno_nexus_sept2015.zip
Download(specific zip for the nexus 5, tested under TWRP and Chroma rom):
https://drive.google.com/file/d/0BwduAK2l37OaNmlqcDNZcjVTc1k/view?usp=sharing
Click to expand...
Click to collapse
There is already a thread about it.
Most people say either they're having problems with that driver (not sure if it is 48M version related) or the gain with it is at best negligible .

wizardwiz said:
There is already a thread about it.
Most people say either they're having problems with that driver (not sure if it is 48M version related) or the gain with it is at best negligible .
Click to expand...
Click to collapse
the only thread i see is for 4.4 and op hasnt updated it in a year, and these drivers are for more stability or adding features(i.e opengl extensions), you should not have a huge or noticiable performance increase.

opssemnik said:
the only thread i see is for 4.4 and op hasnt updated it in a year, and these drivers are for more stability or adding features(i.e opengl extensions), you should not have a huge or noticiable performance increase.
Click to expand...
Click to collapse
Actually the 4.4 thread has evolved and it covers 5.5.X
As for myself, crashed me android with 48M ver

opssemnik said:
the only thread i see is for 4.4 and op hasnt updated it in a year, and these drivers are for more stability or adding features(i.e opengl extensions), you should not have a huge or noticiable performance increase.
Click to expand...
Click to collapse
I post updates in the OG thread sometimes for these drivers since the OP and most users who used to maintain them seem to have moved on. I did already post these (if you searched the other thread [emoji14]). You would also have seen that most users did report several different bugs which were also confirmed with other users.
Oh and as per Qualcomm;
"This release is intended only for developers, and does not meet our customer release quality."
Expect bugs. Read the established thread for more info!

This work in Android M Preview 3?

Is this working on LMY48M?

parag60288 said:
Is this working on LMY48M?
Click to expand...
Click to collapse
It didn't work for me. got me stuck on android screen. Had to re-flash system.img (LMY48M)

[DEV] Cyanogenmod 12.1 for Samsung Galaxy A700FD

CyanogenMod for Samsung Galaxy A700FD
I will update various changes and updates in this thread until i release CM publicly.
What is the purpose of this thread ?
To keep updated with all changes and stability
lately m getting a lot of PM's asking ETA's and requests so this thread will be answer to them.
So has you all know CM12.1 booted successfully on A700FD so here is the list of things working and not working (not all things are tested since first major stuff)
Working:
Bluetooth
Auto Brightness
Sensors (few)
Screen Recording
Rear Camera (Photos and Videos)
Front Camera
Applications
Hardware Keys
Photos and Videos
Not Working :
WiFi
Audio
Radio (RIL) Calls,Msgs etc
Red Border Flashes (Occasional)
GPS
Thanks to my best buddy @RVR for testing various builds regularly.
FAQ/Notes
May i know ETA of CM ?
No. do not ask ETA's in any form. Its strictly against XDA Rules.
Google released Marshmallow can we have it for our device too ?
Answer is simple. Until CM12.1 is Stable for A700FD do not expect Android M.
Will you develop Marshmallow for A7 ?
Said above until lollipop is stable no Marshmallow
Can i have a download link for CM ?
I would have been more than happy to provide but sorry since these are highly experimental builds i would not recommend giving links to it.
So when will you release CM12 ?
Once Major bugs like WIFI and all are fixed i will make a first release
​

reserved 1

reserved 2

uptil now only Bugs remaining are
1) Audio
2) RIL
3) WIFI
4) GPS
Rest all is working for more info see the OP

jackeagle said:
uptil now only Bugs remaining are
1) Audio
2) RIL
3) WIFI
4) GPS
Rest all is working for more info see the OP
Click to expand...
Click to collapse
Can you give me your roomservice.xml?
I am busy for the A700F but i have to make a device tree from scratch.
Sent from my SM-A700F using XDA Free mobile app

mmarkvoort said:
Can you give me your roomservice.xml?
I am busy for the A700F but i have to make a device tree from scratch.
Sent from my SM-A700F using XDA Free mobile app
Click to expand...
Click to collapse
you cannot use qcom roomservice for exynos exynos is way different and it needs lot different hardware repos and modification its no way near to qcom type

jackeagle said:
you cannot use qcom roomservice for exynos exynos is way different and it needs lot different hardware repos and modification its no way near to qcom type
Click to expand...
Click to collapse
I know
Am transforming a7lte device stuff to a7alte.
Am using some stuff from slte which also has the exynos 5340.
Was more qurious to the file itself. I made one with repos on my own giyhub but it won't sync notmally. Real weird.
Sent from my SM-A700F using XDA Free mobile app

mmarkvoort said:
I know
Am transforming a7lte device stuff to a7alte.
Am using some stuff from slte which also has the exynos 5340.
Was more qurious to the file itself. I made one with repos on my own giyhub but it won't sync notmally. Real weird.
Sent from my SM-A700F using XDA Free mobile app
Click to expand...
Click to collapse
well honestly dont transform a7lte tree you will hardbrick your device. you have to come up with a tree from scratch. take reference of exynos devices trees and try to make your own. a7lte tree is only for qcom and hence you cannot transform/ref it for exynos

jackeagle said:
well honestly dont transform a7lte tree you will hardbrick your device. you have to come up with a tree from scratch. take reference of exynos devices trees and try to make your own. a7lte tree is only for qcom and hence you cannot transform/ref it for exynos
Click to expand...
Click to collapse
Hmmm good to know. I'll try to get another device to use then. Maybe the slte for this too.
Used to build several ROMs for HTC One S but there i had a normal device tree.
Now i have nothing. And i am not a real expert about that kind if stuff.
Sent from my SM-A700F using XDA Free mobile app

jackeagle said:
well honestly dont transform a7lte tree you will hardbrick your device. you have to come up with a tree from scratch. take reference of exynos devices trees and try to make your own. a7lte tree is only for qcom and hence you cannot transform/ref it for exynos
Click to expand...
Click to collapse
Do you know what device i could use best as base???
Sent from my SM-A700F using XDA Free mobile app

haris7647 said:
Galaxy A5 and A5 got CM12.1 but we are still waiting fot it will u please hurry up to upload the link for Galaxy A7?
Click to expand...
Click to collapse
If it's not ready why will he upload. Even if he does what u will do when u can't use it as a daily driver as RIL functionality is not up. He has made several roms for other Galaxy models in past. Just enjoy the stock lollipop, it'll come with time.

Many of us don't even have Lollipop yet. LOL

jackeagle said:
well honestly dont transform a7lte tree you will hardbrick your device. you have to come up with a tree from scratch. take reference of exynos devices trees and try to make your own. a7lte tree is only for qcom and hence you cannot transform/ref it for exynos
Click to expand...
Click to collapse
Can you tell me what device to use best as base for a7alte then??
Thanks !!
Sent from my SM-A700F using XDA Free mobile app

Mod Edit
Thread closed at the request of the [OP]
malybru
Forum Moderator