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
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Hey guys I have got some great news for Xperia E1 and E1 dual users. There is going to be a CyanogenMod 11 Port for these two devices. I have been working on this port and 50% of it is done.
Once I have a stable version I will post the link for the ROM and might start porting CM12 for Xperia E1/E1 Dual.
but i need help from some people. Right now the xperia e1 is stuck at the cm11 boot logo.
It would be grateful if some could assist/help me so I can port the rom quickly.
I'll keep you guys updated.
We discontinued for a reason.
Any Custom rom for E1 Will not be possible. EVER.
It has been repeated enough times already.
If you didn't notice, you could have first tried the "basic" porting
Such as searching another MSM8210 phone with a CM port and try copying Xperia E1's system files into the port ROM
The reason it will not work is because the lib files does not communicate with other Android ROMs other than Sony's stock ROM
Either hack the libs, search for similar "drivers", or wait for Sony to release AOSP support for this device (which I assume they will never give support for this phone...)
Sadly we can't do anything about it, we tried everything. The only way to boot into CM on E1 is trying the above I typed.
Regardless of this, I will help you out. Just mentioned this to let you know
I can help you with logcat logs If needed, and trying out test builds
I don't know what's wrong with some people. There are ports for other xperia devices but not for xperia e1. Rather than saying it's impossible you should help each other. Just because you can't do it doesn't mean they it's impossible.
Sent from my D2005 using XDA Free mobile app
jalp_14 said:
I don't know what's wrong with some people. There are ports for other xperia devices but not for xperia e1. Rather than saying it's impossible you should help each other. Just because you can't do it doesn't mean they it's impossible.
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
You say it like we never tried it before. Saatvik, who's good at porting stuff apparently failed porting both CM11 and 12 for E1
Not because he does not have the knowledge to do it, it's the phone itself that is holding him back.
A guy who works at Sony said this that we should not bother with E1 as it's system files (Sony vendor) will never communicate with Cyanogenmod at all, no matter how we struggle to make it work. (This includes AOSP as this phone does not have AOSP support)
OK now I understand what you are saying.
Sent from my D2005 using XDA Free mobile app
Xperia E1
Xperia e1 should have AOSP suppourt.
There is a article from tomshardware that says all the 2014 xperia devices with qualcomm chip is getting AOSP support from Sony.
Xperia E1 was released in 2014 and has a Qualcomm chip so it should hae AOSP suppourt.
jalp_14 said:
Xperia e1 should have AOSP suppourt.
There is a article from tomshardware that says all the 2014 xperia devices with qualcomm chip is getting AOSP support from Sony.
Xperia E1 was released in 2014 and has a Qualcomm chip so it should hae AOSP suppourt.
Click to expand...
Click to collapse
"Xperia E1 can not be added to our AOSP project because there is no support for msm8210 (Snapdragon 200) in AOSP and our goal is to build a clean AOSP without patches
Google AOSP code https://android.googlesource.com/ can be a good place to check which devices can be added to AOSP"
I hope this will open your eyes.
---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------
However I still does not understand why Sony vendor (msm8210) does not work with Cyanogenmod, they said It will not communicate because It has no AOSP support, and Cyanogenmod is a heavily edited AOSP rom
From what I've been experienced in the last 6 months, It is simply Sony that does not care about E1. Low budget phone, weak components, etc. You know the rest
We could hack msm8226 libs to work with msm8210, but when It is finally finished, everyone else will have a better phone than E1
This doesn't make any sense
Other phones with snapdragon 200 like Moto E and ZTE Open C has cynogenmod why????
Sent from my D2005 using XDA Free mobile app
jalp_14 said:
This doesn't make any sense
Other phones with snapdragon 200 like Moto E and ZTE Open C has cynogenmod why????
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
E1 is Europe exclusive == It is not available in the USA
I've seen petitions regarding CM port for E1 (and AOSP), it is useless, nobody will do it.
Can we do something like you said hack the lib files
Sent from my D2005 using XDA Free mobile app
jalp_14 said:
Can we do something like you said hack the lib files
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not an Android expert, nor good at Hex editing
If you could find someone who could do it, then there's a small chance that we can get Cyanogenmod
I found out that Xperia E1 has AOSP suppourt. Look at the screenshot attached https:
Kizoky said:
If you didn't notice, you could have first tried the "basic" porting
Such as searching another MSM8210 phone with a CM port and try copying Xperia E1's system files into the port ROM
The reason it will not work is because the lib files does not communicate with other Android ROMs other than Sony's stock ROM
Either hack the libs, search for similar "drivers", or wait for Sony to release AOSP support for this device (which I assume they will never give support for this phone...)
Sadly we can't do anything about it, we tried everything. The only way to boot into CM on E1 is trying the above I typed.
Regardless of this, I will help you out. Just mentioned this to let you know
I can help you with logcat logs If needed, and trying out test builds
Click to expand...
Click to collapse
Also I downloaded the AOSP build for Xperia E1 and it has the Kernel and the lib file
jalp_14 said:
Click to expand...
Click to collapse
https://www.dropbox.com/sh/fldeqf2kglrlwh2/AAB5zVOOrsG74ST8EaMna1oMa?dl=0
jalp_14 said:
https://www.dropbox.com/sh/fldeqf2kglrlwh2/AAB5zVOOrsG74ST8EaMna1oMa?dl=0
Click to expand...
Click to collapse
No, It has NO AOSP Support
While the kernel (MSM8210) is not owned by Sony, they are forced to release every kernel files (source files) If asked
That is only the kernel, nothing more (Which is useless)
And how about LG L70? It uses MSM8210, and have a working CM 11 port.
Zsenyka said:
And how about LG L70? It uses MSM8210, and have a working CM 11 port.
Click to expand...
Click to collapse
We can try it. But I don't think Wi-Fi and Bluetooth will work though
Here's the CM 11: androidforums.com/threads/unofficial-cyanogenmod-11-for-lg-l70-d320-d320n-d325.890205/
And it has CM 12 too: androidforums.com/threads/unofficial-cyanogenmod-12-for-lg-l70-d320-d320n-d325.893621/
(I can't post outside links yet :/)
CM11
Found another phone with MSM8610, it also has CM 11: modaco.com/forums/topic/373214-devrom88-cyanogenmod-11-android-444-for-zte-open-c-kis-3/