Hey guys !
For my part, i love Sony Xperia UI. So, what do you think about porting it ?
I found this rom : Xperia Z2 stock, Zipaligned and Deodexed, and rooted.
I open this thread, so we can chat about this. I'm not the best guy to mod kernel, so any help is very apreciated.
I know Lollipop is released few days ago and you're still in love on it
Cheers
Good night, and good luck
dekefake said:
Hey guys !
For my part, i love Sony Xperia UI. So, what do you think about porting it ?
I found this rom : Xperia Z2 stock, Zipaligned and Deodexed, and rooted.
I open this thread, so we can chat about this. I'm not the best guy to mod kernel, so any help is very apreciated.
I know Lollipop is released few days ago and you're still in love on it
Cheers
Good night, and good luck
Click to expand...
Click to collapse
while the idea of a nexus running the finest OEM UI on the market does intrigue me,
The thought of this thread turning into a troll fest and off topic discussion is screaming in my face.
I am going to allow this thread on the basis that it is a thread for the development work of porting Sony UI to the phone.
If I find unneeded posts or off topic chit-chat this thread will be closed. I have subscribed to this thread for observations
If you have any issues with this just PM me.
DO NOT REPLY HERE.
Please stay on -topic of development ONLY.
Thanks for the cooperation,
~JAB
XDA Mod
Link is broken.
kidrobot52 said:
Link is broken.
Click to expand...
Click to collapse
Yep for me too.
He gave the link to his in-progress download, not a shareable link
Sent from my Sony Xperia ION
Toledo_JAB said:
while the idea of a nexus running the finest OEM UI on the market does intrigue me,
The thought of this thread turning into a troll fest and off topic discussion is screaming in my face.
I am going to allow this thread on the basis that it is a thread for the development work of porting Sony UI to the phone.
If I find unneeded posts or off topic chit-chat this thread will be closed. I have subscribed to this thread for observations
If you have any issues with this just PM me.
DO NOT REPLY HERE.
Please stay on -topic of development ONLY.
Thanks for the cooperation,
~JAB
XDA Mod
Click to expand...
Click to collapse
I opened this thread to have help and discussion to port it because i'm in love on Sony UI and it would be awesome to see it running on Nexus 5. It's not a troll.
kidrobot52 said:
Link is broken.
Click to expand...
Click to collapse
You're right. Link fixed to OP
I think the most difficult thing is porting the UI, because other things only require to copy the apk, for example the launcher, sony apps...
Sony widgets only work with sony launcher at least on my old xperia arc. Good luck
We've been through this before, people have tried porting ROM's from other devices and it's always been a dead end. Proprietary libs will always be the one road block unless we know any devs with exceptional knowledge in decompiling and patching libs. Don't want to be a downer but that's the truth
jlmcr87 said:
I think the most difficult thing is porting the UI, because other things only require to copy the apk, for example the launcher, sony apps...
Sony widgets only work with sony launcher at least on my old xperia arc. Good luck
Click to expand...
Click to collapse
No. The apk copy is useless if you dont copy the entire framework folder with apk's. For my part, i started, and can't see the bootanimation. The phone reboots.
topgeardave said:
We've been through this before, people have tried porting ROM's from other devices and it's always been a dead end. Proprietary libs will always be the one road block unless we know any devs with exceptional knowledge in decompiling and patching libs. Don't want to be a downer but that's the truth
Click to expand...
Click to collapse
Know that. Porting is hardcore. For now, i didn't obtained anything nice.
Have some news :
Flashed a Xperia Z2 kernel to my phone (Attempting to get working my port as secondary rom) on Multirom.
After it, flashed Uber kernel. Now, the phone still stuck to Google logo, but 5 seconds after, i've got a little vibration. I remember my old Xperia X10 did a vibration when it boots, indicating you can access the recovery pressing back button.
If somebody has skills on editing kernel, and want to contribute to this project, thanks to contact me.
dekefake said:
Have some news :
Flashed a Xperia Z2 kernel to my phone (Attempting to get working my port as secondary rom) on Multirom.
After it, flashed Uber kernel. Now, the phone still stuck to Google logo, but 5 seconds after, i've got a little vibration. I remember my old Xperia X10 did a vibration when it boots, indicating you can access the recovery pressing back button.
If somebody has skills on editing kernel, and want to contribute to this project, thanks to contact me.
Click to expand...
Click to collapse
That's dangerous mate, you're lucky you didn't brick your phone as the Z2 has different mount points
dekefake said:
Have some news :
Flashed a Xperia Z2 kernel to my phone (Attempting to get working my port as secondary rom) on Multirom.
After it, flashed Uber kernel. Now, the phone still stuck to Google logo, but 5 seconds after, i've got a little vibration. I remember my old Xperia X10 did a vibration when it boots, indicating you can access the recovery pressing back button.
If somebody has skills on editing kernel, and want to contribute to this project, thanks to contact me.
Click to expand...
Click to collapse
That little vibration was most likely the boot loop recycling after the boot failed. My S3 would do that too when stuck in a boot loop
DigitalUnderground said:
That little vibration was most likely the boot loop recycling after the boot failed. My S3 would do that too when stuck in a boot loop
Click to expand...
Click to collapse
Yeah, it was like a start up vibrate. Common on my GT-i9300
topgeardave said:
That's dangerous mate, you're lucky you didn't brick your phone as the Z2 has different mount points
Click to expand...
Click to collapse
Know it, it's why i did it on Multirom, and edited updater-script
rootSU said:
Yeah, it was like a start up vibrate. Common on my GT-i9300
Click to expand...
Click to collapse
I think so.. 10 seconds after that, it reboots. I'm sure the reboot loop it's related to kernel. I think i must contact somebody to help me with the kernel.
Cheers guys.
OMG found something awesome will try to build 19.2.A.0.344 for hammerhead right now guys
dekefake said:
OMG found something awesome will try to build 19.2.A.0.344 for hammerhead right now guys
Click to expand...
Click to collapse
Best of luck! Continuing to watch this thread. This one is the only OEM skin I wouldn't mind having ported over to our N5. Thanks for your continued development, keep us posted!
RoyJ said:
Best of luck! Continuing to watch this thread. This one is the only OEM skin I wouldn't mind having ported over to our N5. Thanks for your continued development, keep us posted!
Click to expand...
Click to collapse
Yes i think i can yes ! Look here
Launched repo init -u ... android-4.4.4_r2 branch of AOSP. once repo init finished, downloaded it and unziped to root of my android source tree. Created .repo/local_manifests/shinano.xml like Sony says, and now running repo sync. After, will build, but for hammerhead. Hope it will work
That is only for AOSP. Sony releases the bits and pieces for their devices. This is going to only get you an aosp build, nothing more.
The got repo you listed is only the device information for building. It is not going to net you anything.
Dameon87 said:
That is only for AOSP. Sony releases the bits and pieces for their devices. This is going to only get you an aosp build, nothing more.
The got repo you listed is only the device information for building. It is not going to net you anything.
Click to expand...
Click to collapse
Are you sure ? repo sync already has downloaded 35Go.. and no i don't think it's normal.
Very much so. And 35GB is normal for a repo sync. I believe my sync for 5.0 was like 40GB.
But back to your question. Just look at the files that are in the bits you linked. Sony's OEM skin and enhancements are not open source. Most OEMs release source for the modified items related to the kernel, and some software. Sony is rare in that they actually release enough to build an actual aosp build. The files you are using are going to net you nothing more than an AOSP build.
Dameon87 said:
Very much so. And 35GB is normal for a repo sync. I believe my sync for 5.0 was like 40GB.
But back to your question. Just look at the files that are in the bits you linked. Sony's OEM skin and enhancements are not open source. Most OEMs release source for the modified items related to the kernel, and some software. Sony is rare in that they actually release enough to build an actual aosp build. The files you are using are going to net you nothing more than an AOSP build.
Click to expand...
Click to collapse
Ok thanks so much. I don't want to build AOSP so i'll search a little more
Cheers
Related
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.
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
pattyboi:) said:
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
Click to expand...
Click to collapse
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
OnlySomeDood said:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
Click to expand...
Click to collapse
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
pattyboi:) said:
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
Click to expand...
Click to collapse
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils
OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere
for sure, that's what this thread is for afterall
OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
OnlySomeDood said:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
OnlySomeDood said:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
OnlySomeDood said:
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
Click to expand...
Click to collapse
can you post one of the errors when you get a sec?
& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
OnlySomeDood said:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
Click to expand...
Click to collapse
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
dip_spit said:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
OnlySomeDood said:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
Click to expand...
Click to collapse
i dont blame you,makes sense to me
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.
--FOR MORE INFO AND NEWS ALWAYS CHECK MY LAST REPLY!--
Thanks for understanding!
PROJECT IS ABANDONED.
Regards,
Holy ****, finally. I cant try it out for my self cause i need to leave to malta tomorrow but i can try it later
MIUI Rom, finally!!!!
I hope they fix the bug as soon as possible
Again, the ROM is NOT bootable, I need logcats from you to fix the problem, hopefully.
So don't expect this to boot.
Thanks for understanding!
Try to take a look here Logcats
I hope to have helped
Giuseppe300715 said:
Try to take a look here http://https://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
I cannot open the link. It gives me an error.
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
He meant this link https://forum.xda-developers.com/showthread.php?t=1726238
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
I just fix the connection
---------- Post added at 09:04 AM ---------- Previous post was at 08:50 AM ----------
[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot
[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
That's all I've found and that can be useful for both this Rom and others that you will develop.
Thank you, but I know how to dump logcats. I asked you if you could provide me some logcats of the rom not booting from your device and send me.
Thank you.
XTutorials said:
The ROM is compiled, but it doesn't boot and me and @AymenDe7 need logcats.
I will provide a download link, but just in google drive so not much downloads will be allowed. Bootable version (if) will be released on androidfilehost.
https://drive.google.com/open?id=0Bx9qplihpe8YVUNZRTNnSFY1bkk
Full no reject source code:
https://github.com/aymende7/XTutorials_Miui8
For now I need logcats from you.
Thanks for understanding!
Click to expand...
Click to collapse
Here's my logcat. http://www117.zippyshare.com/v/WcWK3ksX/file.html
I think there's problem with OpenGL
06-13 10:04:20.297 2468 2468 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: library "/system/lib64/egl/libGLES_mali.so" not found
06-13 10:04:20.297 2468 2468 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
Click to expand...
Click to collapse
And if you would copy libGLES_mali.so to /system/lib64/egl?
Would it work?
Thank you for your logcats. I will see what I can do.
How does it go with progress?
Should boot if you use custom kernel and copy&replace blobs
I am giving up on trying to fix that error message. I am trying to build AOSP 6 and then try again patchtom, hopefully I won't get that error.
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
haky 86 said:
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
Click to expand...
Click to collapse
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
Yeah. We have like 2 developers(one is a team) On this device. Haky and OpenKirin. And 6 "different" ROMs that all work the same, with the exception off the nougat FOMs, which have even more bugs.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
haky 86 said:
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
Click to expand...
Click to collapse
I know man, I wasn't talking about you. I was talking in general. I know you're doing god work, despite I'm not developing anything since a long time I still read forum and follow what's happening.
Like @Vinnipinni said, 2 guys and 6 "different" roms. But all working the same.
Back in times people were more likely waiting for stable CM/AOSP before compiling bunch of other distros. Now it's just mess.
I really wish I could go back to developing for android devices, especially now when I have programming knowledge and experience.