Related
Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
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.
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
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.