[Xperia U] Novice developer's diary - Sony Xperia P, U, Sola, Go

Hi all,
I create this thread for annotate my progress in debugging @FXP's CM10 @munjeni CM11 and for create a guide to new developers. So.. Let's start
Quick start:
Get all necessay software in order to compile CyanogenMod's source code: here there is a very good guide by @elia222, I have no more to add.
Get CyanogenMod 's source code as described here but use this device tree.
Debugging using catlog, dmesg and brain.
Goals:
Some of this bugs are already fixed by other users, all credits to relative developers (if you are one of this and I have not mentioned you, or I make a mistake about credits please send me a PM).
Fix Bluetooth ✓
Fix Wi-Fi ✓
Fix Wi-Fi Tethering ✓
Fix Wi-Fi Direct ✓
Fix Camcorder ✓
Fix LED bar ✓
Fix FM radio

Fix main camera upside-down (Fixed here by @Na'onak ):
This fix consist in use right camera file as FreeXperia use the Xperia GO version. The right file can be downloaded from here.
After have substituted the file in relative CyanogenMod's build folder, recompile and flash.
Fix ambient sensor light (Fixed here + this post by @munjeni + @95A31):
This fix consist in adjust ambient sensor light driver. In detail Android Jelly Bean require als_lx parameter that is not in standatd driver source code. This parameter and relative functions were added by @munjeni in the safest possible way: return a fixed value. The fix consist in implement this new functions exploiting the already present functions. The original version can be dowloaded here and the newest is attacched at bottom of this post. After have substituted the file in relative CyanogenMod's build folder, recompile and flash.

good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962

remove FM radio ,its impossible without sources and sources = not possible because ST-Ericsson is no more

loren82 said:
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
Click to expand...
Click to collapse
Thank you but I have already a fix for front camera. He has published the patch before me so the credits go to him. I want give you a little spoiler: in order to fix from camera is necessary modify only 2 files .
Anyway i currently working on Wi-Fi direct, more suggests about this are well accepted .
percy_g2 said:
remove FM radio ,its impossible without sources and sources = not possible because ST-Ericsson is no more
Click to expand...
Click to collapse
I want investigate on these commits:
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/52cedeea40957113358f92780d7f927414fcc73a
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/0f86f877f07c7e9d9de7939012d0a19aa9ae2175
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/61c4290fd4e7cadde9ff42c6fdf0161f6723f2e1
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/8541f5b88cd05789b05ee1bf3034e17cb1c45b70
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/59a6f62c4b4c65ba90a6bbac43c04010b1262d14
and maybe continue to develop this:
https://github.com/freexperia/android_packages_apps_FMRadio
hopefully reusing some code from MIUI FM Radio.

loren82 said:
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
Click to expand...
Click to collapse
While everyone is waiting for camera fix this one above works perfectly and fixes orientation or back camera, also led turns of after this flash when you have used the LED bar fix

@95A31 I guess you forgot to add the link to my guide in the op

Neurom707 said:
While everyone is waiting for camera fix this one above works perfectly and fixes orientation or back camera, also led turns of after this flash when you have used the LED bar fix
Click to expand...
Click to collapse
Front camera fix is coming in couple of days .
elia222 said:
@95A31 I guess you forgot to add the link to my guide in the op
Click to expand...
Click to collapse
Wops, fixed :good:.

95A31 said:
I want investigate on these commits:
https://github.com/CyanogenMod/andr...mmit/52cedeea40957113358f92780d7f927414fcc73a
https://github.com/CyanogenMod/andr...mmit/0f86f877f07c7e9d9de7939012d0a19aa9ae2175
https://github.com/CyanogenMod/andr...mmit/61c4290fd4e7cadde9ff42c6fdf0161f6723f2e1
https://github.com/CyanogenMod/andr...mmit/8541f5b88cd05789b05ee1bf3034e17cb1c45b70
https://github.com/CyanogenMod/andr...mmit/59a6f62c4b4c65ba90a6bbac43c04010b1262d14
and maybe continue to develop this:
https://github.com/freexperia/android_packages_apps_FMRadio
hopefully reusing some code from MIUI FM Radio.
Click to expand...
Click to collapse
If you can get FM audio enabled, there should be enough open source code out there for an open source FM app. The closed source libfmradio.cg2900.so would be needed, but should still work.
An ambitious person might even be able to get FM transmit working on some Euro phones. I was able to enable it with my app, but couldn't figure out how to enable FM transmit audio with some quick attempts.

mikereidis said:
If you can get FM audio enabled, there should be enough open source code out there for an open source FM app. The closed source libfmradio.cg2900.so would be needed, but should still work.
An ambitious person might even be able to get FM transmit working on some Euro phones. I was able to enable it with my app, but couldn't figure out how to enable FM transmit audio with some quick attempts.
Click to expand...
Click to collapse
When I will start to work on the FM radio, I would be happy to collaborate with you .
Fix front camera (Fixed here by @xx214718247):
Also this fix consist in use right camera files as FreeXperia use the Xperia GO version. The right files can be downloaded from here and here. The first one is necessary in order to make able the system to recognize front camera, the second allow to use it. After have substituted the files in relative CyanogenMod's build folders, recompile and flash.

Good to see ambitious devs like you creating xperia u's future!
SIGNATURE OUTDATED. I now use honami moonwalker 4.2

In this period I am looking Team Canjica's camcorder fix:
In this post @DevSwift1 suggest to use android_vendor_sony by Team Canjica for fix camcorder.
It work, but it broke bluethoot. This small issue can be fixed reverting this commit.
The two main differences between Team Canjica's version and TheMuppets' version are:
Different organization of common and device specific libs.
Team Canjica version require that some media and camera libs shoud be compiled from source.
If kumquat-vendor-blobs.mk is modified in order to require that the media and camera libs must be compiled frome source we obtain a lenght 0:00 video and logcat report an error of OMX node allocation about h264enc.
TODO: Search which other differents files are involved in recording/encoding process in order to make TheMuppets' version work.
Currently I am also investigate on Wi-Fi tethering/direct:
For fix these issues I follow this guide by Texas Instruments. The firts issue that I have found is broken Wi-Fi. This can be simply fixed setting the right permissions to files and directories involved in Wi-Fi as described here. The second problem is of corse tethering. The first issue is in hostapd.conf: when Hostapd try to change the owner of the control interface as described in line 8 give a operation not permitted error. The (naive) solution is eliminate line 8 so Hostapd can run without problem. The second and critical issue concern how softAP is used by the system. Below the interesting logcat's part:
Code:
...
E/hostapd ( 2731): Configuration file: /data/misc/wifi/hostapd.conf
...
E/hostapd ( 2731): Using interface wlan0 with hwaddr 01:23:45:67:89:AB and ssid 'AndroidAP'
D/hostapd ( 2731): Deriving WPA PSK based on passphrase
D/SoftapControllerTI( 1484): hostapd started OK
D/SoftapControllerTI( 1484): hostapd set - Ok
E/NetdConnector( 1967): NDC Command {14 softap set wlan0 wl0.1 AndroidAP wpa2-psk trolololol} took too long (1823ms)
D/hostapd ( 2731): random: Got 20/20 bytes from /dev/random
D/hostapd ( 2731): WPA: Delay group state machine start until Beacon frames have been configured
E/hostapd ( 2731): Failed to setup control interface
E/hostapd ( 2731): wlan0: Unable to setup interface.
...
TODO: Search documentation about SoftAP in order to make tethering work.
About Wi-Fi direct the issues start to be hard to fix. From ICS to JB is changed more about Wi-Fi direct managing, in detail JB require a network device called p2p0 in order to get working Wi-Fi direct. AFAIK this device is created and managed only in recents verions of wpa_supplicant and not all drivers can handle this kind of device.
TODO: Porting CM10.2 version of wpa_supplicant in order to make Wi-Fi direct work.

mmm
++++

Hi guys,
here I created a git repository with all fixes that I analized. In order to exploit it just simply download it as zip archive and extract the content over the CyanogenMod's build folder.

I hope in a tethering fix.
Thx for the repo.
Inviato dal mio Xperia U con Tapatalk

For led bar u can use dis..
http://forum.xda-developers.com/showthread.php?t=2429318

marce78 said:
I hope in a tethering fix.
Thx for the repo.
Inviato dal mio Xperia U con Tapatalk
Click to expand...
Click to collapse
I'm working on
ajain3982 said:
For led bar u can use dis..
http://forum.xda-developers.com/showthread.php?t=2429318
Click to expand...
Click to collapse
Thank you :good:
Hi guys, tethering fix is not so easy as I image. I think that @munjeni in this porting have the same problem. Probably is enought a good configuration but without documentation is very hard. I ask you provide to me this files:
init.st-ericsson.rc form Stock Jelly Bean Xperia GO
A logcat from Stock Jelly Bean Xperia GO when Wi-Fi tethering is turn on

Daily report:
Camcorder: For fix this, I decide to use TeamCanjica's android_vendor_sony because it is updated and I prefer his "old" organization of common and device specific files. It already contain the back camera fix, so is useless keep it as different fix. A side effect is broken bluetooth, that as I previous say can be fixed reverting this commit. I fond also iw broken so I used the ICS version.
Wi-Fi thetering: I keep working on this but I dont see the end (for now ). In detail the jellybean Android Network Deamon not has full support for SoftAP used by FreeXperia. The support was reintroduced in this commit. The TeamCanjica has ported this fix in the own Android Network Deamon so I use this last one. I try several configuration of hostapd.conf but none seams work.

@95A31, appreciate doing this and sorry for intruding but it seems that you're the only one looking at real problems right now. Anyway, to the point.
There seems to be everlasting problem of extreme call dialer lag in jb roms, at least in ones that I've tried. During the answering of call phone just freezes and hangs for a period of time during which call gets established but you can't hear or be heard. Lots of people are not using jb especially because of this. However, I haven't tried cm10 in a while 'cause fxp stopped updating it and I don't have enough knowledge to build it, so I can't say if it's present there. So if you think you might be able to fix the dialer please try it. And also if you're already building cm10 with fixes feel free to upload it somewhere, I'm sure people would flash it. That way you could get some more logcats. Of course, I'm just suggesting stuff, there's no pressure and it all depends on if you have free time.
Thanks

Dialer lag affects me only after 3 months of jb. Thereafter, i change roms and wipe data amd to its not there
Sent from my LT22i using xda premium

Related

[DEV] ICS Android 4.0 Porting and Development | es209ra (X10) | alpha1 | 21/11/2011

This is a dev thread. Do not install this release unless you know what you're doing. Do not post if you have nothing to contribute.
This is very early build, we're behind other qsd8k devices but will eventually catch up
Big thanks to all qsd8k developers working on this (N1, Desire, HD2, X10).
[KERNEL]
- ol' good 2.6.29-SEMC
- fixed touchscreen driver (now backward-compatibile with Gingerbread)
[ROM]
- partially based on drewis release (thanks!) - currently I don't have access to PC that could handle compilation of the whole thing
If someone could compile clean es209ra build and upload it would be awesome.
[WORKING]
- it boots
- radio, calls, txt (sms)
- audio partially working (in-call is fine, playing mp3/ringtones leads to WLOD)
- bluetooth, GPS seem to work
- wifi almost working ("can't find wlan0 device")
- mobile data (it gets IP but disconects afterwards, needs investiagtion)
[NOT WORKING]
- most of the stuff does not work
- quite unstable
[SOURCES]
Will upload all of the useful code/fixes here.
- ICS + GB compatibile touch driver: es209ra_touch_mt.c
- compatibile ramdisk (props FXP): http://www.mediafire.com/?1n51pn1upwv79ur
[DOWNLOAD]
Alpha1 ROM (for CWM5) + corresponding kernel (flashtool) is here:
http://www.mediafire.com/?ht6p6tbpj2988d4
Cheers,
z
Just did a major clean up on this thread mates....no more "thanks" posts please. If thankful... click the thanks button.
Regards,
M_T_M
Finally we get it. aZuZu is working on ASOP ICS 4.0.1. This may help him work easier. So with locked bootloader, can we flash cause' you wrote there CWM5?
VIDEO
here's a video for ics on x10 alpha build 1
http://www.youtube.com/watch?v=bsOFn4YLvZU
@frosty666 please kindly include this on your ics discussion thread.
thankz
hi zdzihu, its great to see you back! is this only temporary or, are you going to be more active, like before?
mmmkay, I'm not dev, but I want to ask if you're compiling this from ground up (like Jerpelea's CM7), or you're like just mashup of current SE and ICS sources. if its a mashup, I can help. but I do very little design from ground up things.
Sent from my X10i using xda premium
if you have fixed audio hw sources i could recompile..
altho i have complete es209ra compile with ics hw, old cm gralloc / copybit sources and generic audio..
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
I help if u want
Hello guys, I'm new to the forum and I hope to see well with you.
I would be willing to help compile the source since EXCLUSIVELY use only Linux operating system and is much easier to work on programming because most of the libraries are already installed by default, I hope I was clear.
greetings
Joseph
zdzihu said:
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
Click to expand...
Click to collapse
yaay Z!!!
glad to see back!
now i feel so bad & depressed that i dont have a working x10 with me
hope that service center guy is able to repair it again...
@aZuZu
can u please upload ur work-in-progress sources to git... i know how much fixing u have done... it might help other too
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
so good
I will try to build ICS this weekend!
I have no time this weekday
Zdzihu, if the wifi still reports the same error (can't find wlan0 device), it probably means that the kernel refers to wlan interface as eth0. Try changing the wifi.interface entry in build.prop to eth0.
little help for folks that compile ICS on weak pc
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed << if processes during compile get killed try this script > Fix Swap
Well to me helped so maybe it helps other ppl.
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
WHAT IS IT WITH SOME OF YOU GUYS, IT IS DEV ONLY THREAD AT THE REQUEST OF THE DEVELOPER, IF YOU CAN'T FOLLOW SIMPLE RULES THEN INFRACTIONS WILL BE HANDED OUT, YOU HAVE NOW BEEN WARNED!
wbbigdave said:
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
Click to expand...
Click to collapse
gunzip -c <ramdisk.gz> | cpio -i
Cheers,
z
The next member who disregards a developers request and posts in a non helpful way will be banned for a week.
i encourage any dev or helpful member to pm me or any other mod with the offending post and the user will be dealt with
Please don't reply tp them to tell them they are breaking th rules as you post will then also be rule break worthy
Hugs and kisses
PiLoT
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_frameworks_base,n,z
sorry for posting here. but is for development. for ICS, can we used modified 2.6.29, and modify, like what zdzihu did, it so it 100% or do we have to use 3.x (or whatever) becuase I'm starting to do kernel mods and I want to see what I can contribution.
so in all, does the newest kernel have to be ported? or can we continue using good old 2.6.29 and keep Modding it? (hopefully camera will work, drivers have to be rewritten for kernel. and no one likr to write drivers)
Sent from my X10i using xda premium
In case, we can see here how they get the SD Card working
http://forum.xda-developers.com/showthread.php?p=19774268#post19774268

[ROM][DEV]CM 7.2.0 (Android 2.3.7)

CM 7.2.0 Android 2.3.7:
CyanogenMod 7.2.0 port for FIH FM6 varaints.
Working:
USB
Sensors(partially)
GPS
Audio
Camera(partialy)
Wifi
OpenGL/graphics
Video Playback
Bluetooth
RIL
Bugs:
1) Front Camera is not working
2} Main Camera Zoom is not working for higher resolutions.Works upto some extent for QCIF
3)Portrait orientation is not proper.Some apps run upside down
4)Device suffers from very rare reboot due to kernel panic
Download Link:
ROM:
Code:
http://goo.im/devs/mb-14/viewpad7/cm-7-viewpad7.zip
GAPPS Package:
Code:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Installation:
Boot into CWM 5.0.2.8 recovery
Wipe DATA and Dalvik Cache
Flash ROM
Flash GAPPS package
For DEVS:
Here is my device config:
Code:
https://github.com/mb-14/android_device_viewsonic_viewpad7
Any help will be appreciated.
BUG REPORTING:
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt.
Alternatively, if I ask for a radio logcat, this is the command: adb shell logcat -b radio -d >c:\logcat-radio.txt. Copy and paste this log to pastebin.com, and provide the link.
Send all this information to my email ID:[email protected] with subject as CMBUG
Credits:
CyanogenMod Team for their awesome ROM.
Goo-inside Team for providing their build server
Please donate to these people
Plea for help:
This project would not have been possible without the help of Goo-inside Me Team.
Now they require financial help for upgrading their servers.Please donate to them!!!
For more info check out their website: http://goo.im/
I am eager to test this beta build, and in anything i can help you with... im using a viewpad 7
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
WOw!!! I'm waiting.
s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
Non-working functions are due improper implementation of hardware drivers(working on it)
Right now ill be commiting changes to the device config but due to hardware limitations
it takes lot of time to compile a build.
If you have sufficient hardware resources(RAM,space,cores)
you can clone my repo ,download and build the Cyanogenmod source and test it on your phone
PM me for any queries
s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
+1, same here, can help debug the issues and work with adb.
Maybe an Irc channel for quicker contact?
cant wait for this. very willing to test
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
I'm think cause 2.3 and 2.2 have most possibility to use in stable. Viewpad 7 is to old to play around. And if this device have rom that can use maximum hardware's can do and stable. I think maybe we can see Viewpad7's ICS ROM in real life.
Sorry for my weak english.
sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
Tnie device seems too weak for ics, its a single core 600mhz armv6 CPU.
ics think it wil work on oure device it`s been ported too the x8 to and that`s a arm v6 600 mhz to,
but im happy with 2.3.7
Well, as long as I get 7.1 I'm happy. I still think having it ported is one thing but having it work flawlessly for everyday use is another.
Is wifi working yet? I've seen some commits on github but haven't seen any updates to the update.zip file in the first post.
*edit* where is the update.zip, exactly? Can't seem to find it on the first post anymore
Also, the sensors readout for screen orientation should be somehow flipped or mangled, for by default the device seems to be in landscape mode and if turned to portrait, it flips upside down for me.
hi
really appreciate you looking into porting this to the viewpad/variants etc
hope it goes well, looking forward to a little added ooompf,
(though [ROM]EUViewpad7 v1.7b has been great too)
@googlehome how's the progress?
@anyone I'm a programmer but i'm new to this android build compilation etc. Could anyone point me to tutorial or manual on how to these and those? Thx.
Yes, viewpad 7 seems to weak for ICS... We didn't even get honeycomb (3.X)
Dear Santa...
I'll be happy just with 2.3 and using my front camera with skype or gtalk...
Happy Holidays
Thank for hardwork
Hi
I think Gingerbread is perhaps as far as this device will go - in terms of functionality and "useablilty" - sure I'm sure ICS will "go on" if attempted but i'm pretty sure will fail to be useful (and if someone proves me wrong then I still win as I'll use it)
anyway keep up the good work with this gingerbread attempt - I'm hoping it goes well
Any news for the new year?

Want to start with AOSP JB 4.2 - experienced developers are welcome :)

Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium

[20180521][UNOFFICIAL] CM12.1 for Mad Catz M.O.J.O

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
As active user of the MadCatz MOJO, I found it pitty that rom development halted, mainly because the Android-TV rom from Unjustified Dev has some limitations.
As a result I've done quite some reading on "how to create an android rom from source" in the last 4+ weeks, in the hope that I could improve the work of Unjustified Dev.
In my attempt to understanding building the android source code to create my "own" Android-TV rom, I was succesfull in creating my first CM ROM (took 2h30)
(Big thanks to the source on https://github.com/TeamRegular?utf8=%E2%9C%93&q=mojo )
changelog:
Code:
[B][U]cm-12.1-20171226-UNOFFICIAL-mojo[/U][/B]
- fixed media server crashes, audio is again functional :)
- included the Tegra note 7 - widevine L1 DRM libraries (testing required)
[B][U]CM-12.1-20171222-UNOFFICIAL-mojo[/U][/B]
- Fixed hardware identification
- added DRM libs to support for widevineDRM
[U][B]BUG [/B][/U]: No audio - mediaserver crashes :(
[U][B]cm-12.1-20171216-UNOFFICIAL-mojo[/B][/U]
- changed boot animation to google animation (I like it more then the CM one)
- changed default dpi = 240
- removed not functioning multi rom code
[STRIKE]- synced media profiles to be inline with ADT-1 and cm-13 tree[/STRIKE]
[STRIKE]- added google media_codecs_performance[/STRIKE]
- applied some cm-13 changes to sync tree.
[B][U]BUG[/U][/B]: Play store seems broken,
[U][B]cm-12.1-20171208-UNOFFICIAL-mojo[/B][/U]
- Included nvcgcserver - should fix chrome issues with streaming.
- Applied kernel patch to increase from 3.4.57 -> 3.4.59
[U][B]cm-12.1-20171203-UNOFFICIAL-mojo[/B][/U]
- The update is a minor Android build update : LMY48G -> LMY49J
- Security level set to November 2016
[URL="http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html"]http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html[/URL]
Location of the ROM:
Code:
File name : cm-12.1-20171226-UNOFFICIAL-mojo.zip
[URL="https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy"]https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy[/URL]
File name : cm-12.1-20171208-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2"]https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2[/URL]
File name : cm-12.1-20171203-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l"]https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l[/URL]
Next step:
- fix issue : https://forum.xda-developers.com/showpost.php?p=69887922&postcount=393 the post should contain enough info
- gaining more ROM development skills
- build AndroidTV-5.1 rom or CM13
Side note: I'm not as experienced as Unjustified Dev, so a "mayor" update can take a while,
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Mad Catz M.O.J.O.
Contributors
carp_be, EdoNINJA93
Source Code: https://github.com/dide0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 5.1.1_r37
Beta Release Date: 2017-12-03
Created 2017-12-04
Last Updated 2018-05-21
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Wmapa said:
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Click to expand...
Click to collapse
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
carp_be said:
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
Click to expand...
Click to collapse
Will you work on cm13? It is way better than android tv if we use toplauncher it is very tv friendly
Thank you so much, OT!
Yeah, I also would prefer a Marshmallow or Nougat based ROM, since you can do more stuff with them and you can get an Android TV experience whenever you like by simply using 3rd party launchers.
Keep it up the good work!
Main fixes I'd like to see:
- Chrome fix (I know you just have to put a separate file inside a specific folder, but it would be better to fix it by scratch by installing a fresh new and optimized ROM)
- Netflix fix
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
New release
cm-12.1-20171208-UNOFFICIAL-mojo now available As I don't have Netflix/Amazon , please let me know if the this new build fixed the streaming issues in Chrome. I checked the forum posts, they mentioned setting the permissions on this file. I check the source code and this should be done by default in the building process.
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
Click to expand...
Click to collapse
thanks
For me it's indeed a hobby project for the weekend, I really like programming but besides writing some simulation software for work projects, I'm not in the programming/embedded development business. I already did a lot of reading in the Github changes/commits on the ADT-1 (molly) and TeamRegular repo's. It should be possible to create a CM13 rom as the ADT-1 has a working rom, CM14 is not working atm on the ADT-1 so I don't expect that I could provide such update.
Currently I'm focusing on the CM12.1 branch as there is a working "rom" (see above ) and trying to add Android TV on this. The ADT-1 has such ROM, so it must be possible on the MOJO. I'm busy merging the changes from ADT-1 to MOJO but atm my build is stuck in a boot loop.
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
Click to expand...
Click to collapse
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
I have experienced this on both CM12.1 and Remix OS. Two things can happen:
Firstly, if you are using an SD card in your MOJO and you have this plugged in at boot, it's a lottery as to whether or not the console will boot up with any WiFi. I'm no expert at all, but by this I mean that it appears that the WiFi module doesn't even load into the system. It cannot be turned on or off as it is all greyed out. As I say, this doesn't happen on every boot up, but is very annoying when it does.
Secondly, if you decide to fix this by not using an SD card in your MOJO, the WiFi will be better but still not great compared to the stock OS. Sometimes it never connects on fresh boots, meaning I have to go into WiFi settings and switch off and on again several times before it connects properly. Then on other times very odd things happen when it does connect. For example, quite often I have experienced when downloading big app updates for example, it seems to "flood" the WiFi if that doesn't sound silly, which results in every one in the house complaining that our router has kicked all their devices off the WiFi and they can no longer get any connection. The MOJO itself also disconnects when this happens. The only thing I can do then is to reboot the router.
I am assured none of these things happen on the stock OS.
Good luck with your builds. I myself would love to see CM13, as I use a modified TV Launcher to polish things off. My fear with the Android TV system is it won't recognise my 2TB external drive, which would mean I couldn't use it. Remix had issues with it also. CM12.1 has no problems at all mounting it and allowing me access to my media files.
Great work ! Tested - nothing broken
Keep going !
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
EdoNINJA93 said:
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
Click to expand...
Click to collapse
I've not seen this on the AndroidTV build of Unjustified Dev, so i'll diff it once with my build and see if there are driver changes.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
Could you please provide a feedback about Netflix and Wi-Fi issues?
carp_be said:
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
Click to expand...
Click to collapse
Replace
Code:
persist.sys.usb.config=none
by
Code:
persist.sys.usb.config=adb
in default.prop and build.prop, this will enable usb debuging during boot.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
More info plz!
Is WiFi any better? What apps do you use?
K-Project said:
More info plz!
Is WiFi any better? What apps do you use?
Click to expand...
Click to collapse
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
rahsoft said:
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
Click to expand...
Click to collapse
The playback issues could be related to DRM content. I saw that the CM build don't have the "google widevine" libraries included, while the AndroidTV build has. I'll include this in the next update,might solve the issue. Otherwise If you get a logcat file, the exception thrown by the app could shed some light what is needed.
besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
DPI can be changed to 240, will do (need to adjust ro. sf.lcd_density in system.prop file) .
Log
View attachment 2017-12-12-17-54-04.txt
Made little log - maybe will help
Please look at:
Process com.google.android.youtube (pid 10272) has died
Process com.lolapp.lolapptv (pid 22409) has died
Process ru.norgen.homevideo (pid 26606) has died
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
K-Project said:
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
Click to expand...
Click to collapse
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="[COLOR="yellowgreen"][B]1980[/B][/COLOR]x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="[B][COLOR="YellowGreen"]1920[/COLOR][/B]x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Are you sure?

Sailfish OS for Sony Xperia 1 and 5 (4.4.0.72)

Sailfish OS 4.4.0.72 for Sony Xperia 1 and 5​
These release notes cover Sailfish OS 4.4.0.72 for the following devices:
Sony Xperia 1 (J8110, J9110)
Sony Xperia 5 (J8210, J9210)
Intro​
This port has been updated last to the latest release of Sailfish OS 4.4.0.72 in addition to that several adaptation bugs discovered in the testing of the first release have been fixed.
Also several documentation updates or buildinfrastructure changes have been made.
Updates to these project components are now tracking in the main bug tracking repository SailfishOS-SonyXperia/bugs/releases.
The highlights in this release are:
[prjconf] Fix pattern dependencies. Fixes SailfishOS-SonyXperia/bugs#55, fixes SailfishOS-SonyXperia/bugs#59
[patterns] Require ngfd >= 1.4 instead of ngfd-plugin-native-vibrator. Fixes SailfishOS-SonyXperia/bugs#69
[configs] Keep dual sim configs on J9210/Xperia 5, remove on J8110. Fixes SailfishOS-SonyXperia/bugs#51
[kickstart] Fix @DEVICES@ name for Xperia 5/J9210 in flash-on-windows. Resolves SailfishOS-SonyXperia/bugs#50
Thanks to all who have provided testing, reported bugs or have contributed otherwise.
Functionality​The devices have the same functionality level as the Xperia 10 II port made by Jolla,
except in areas such as VoLTE where public packages are missing or in relation to Sailfish X features which are (currently) unavailable.
Known issues​
SailfishOS-SonyXperia/bugs#33
Because of a missing package inside the adaptation-common repository Windows binaries for flashing are missing inside the zip archive. To workaround that issue have added another zip file that includes these files as "droid-flashingtools.zip" to this release.
SailfishOS-SonyXperia/bugs#37
The launcher icons on the Xperia 1 are to small because there's no bigger graphics-theme size than 2.0.
Project​The Github project that contains this port and all other ports from this project can be found here:
Sailfish OS Community ports for Sony Xperia devices
Sailfish OS comunity ports for Sony Xperia devices - Sailfish OS Community ports for Sony Xperia devices
github.com
Project Updates​As explained above there’s now a separate changelog for project wide updates which can be found down below:
Release Project Update 02-12-2022 · SailfishOS-SonyXperia/bugs
Intro The changelog describes all the project wide changes, such as for example documentation updates or build infrastructure changes. In case an adaptation issue arose from wrong build configurati...
github.com
The changelog file about the project updates can be found down below:
project_changelog.md
About​
The goal of this project is to port additional Sony devices on top of Jolla's existing adaptations while staying as close as possible to the existing ports and contributing back to the upstream where possible.
Most of the changes from Jolla ports are adopted in both directions since the issues that one port has usually apply to the sister device of the same generation (e.g. Xperia 10 II -> Xperia 1/5).
This is the reason why changes from Jolla’s port end up in the changelog for these port,
in many cases because they also affect the specific port but not always.
Where possible changes that were done for this port go back to the _Mer-Hybris_ repositories such as the kernel or droid repositories.
The project is open for anyone that wishes to port additional Sony devices to Sailfish OS. Feel free to suggest new features, provide bug reports or to contribute.
Sources​Any sources specific to this port can be found inside the project linked above. The device repositories are named after the devices board name for example in this case kumano.
All our sources are included inside the project linked above.
All other sources are taken unpatched from upstream which is either Sony-AOSP or SailfishOS/mer-hybris.
If changes are needed inside upstream repositories these are submitted to the upstream repositories.
This GPL includes components such as the kernel or libhybris.
On pressure of XDA I add the direct link to the kernel repository, however the exact ref used during build
can be found inside the droid-hal repository, which in the case of the Xperia 1 for example, droid-hal-kumano.
Sources for this board​
https://github.com/mer-hybris/android_kernel_sony_msm/tree/hybris-sony-aosp/LA.UM.7.1.r1
https://github.com/SailfishOS-SonyXperia/droid-hal-sony-kumano
Report bugs​
Bugs can be opened in the bug repository linked below:
GitHub - SailfishOS-SonyXperia/bugs: Empty repository that is used as a bugtracker
Empty repository that is used as a bugtracker. Contribute to SailfishOS-SonyXperia/bugs development by creating an account on GitHub.
github.com
Download​
Release 4.4.0.72+git1 · SailfishOS-SonyXperia/droid-hal-version-sony-kumano
Sailfish OS 4.4.0.72 for Sony Xperia 1 and 5 These release notes cover Sailfish OS 4.4.0.72 for the following devices: Sony Xperia 1 (J8110, J9110) Sony Xperia 5 (J8210, J9210) Intro This port ha...
github.com
Flashing​
To install Sailfish OS on your device please follow the install instructs in the flashing-readme.txt file included in the archive or read the offical flashing instructions for either the Xperia 10 II or Xperia 10 III:
Sailfish X Installation Instructions - Jolla
jolla.com
Just make sure to download the software binaries for your device instead of the ones mentioned in the instructions:
Software binaries for AOSP Android 10.0 – Kernel 4.14 – Kumano (latest) - Sony Developer World
developer.sony.com
Changelog​https://github.com/SailfishOS-SonyX.../releases/download/4.4.0.72+git1/Changelog.md
Great job, thanks for making the port! Does it have Android app support? If it does I'll definitely give it a try, I saw on the SailfishOS official website that only the paid version can run Android apps...
Edit: I see why now, because of the very very long term support that you get, it's like 7 years of updates for a bit of money, that's pretty good.
just try to use on my device.
its first time for me using Sailfish OS.
but.
when i turn off the phone, and try to turn it on, it asks for the security code, after i enter the security code, it just loading in quite a long time,
then, simcard and wifi didnt works.
I can confirm, that neither data connection nor WiFi works.
Without any data such as logs I can't help you. Please create a bug in the bugtracker.
Please also make sure that you flash the version that matches your device.
Please follow this article to fetch logs:
https://jolla.zendesk.com/hc/en-us/articles/360013910599-Collecting-basic-logs-from-a-Sailfish-device
You can also try to flash the new images, I will add tomorrow.
I updated the release archives today:
Package ngfd as `CUSTOM_’ FFMemless vibration effects require newer version than packaged in SailfishOS 4.4.0.
Fix issue in ssu-vendor-data package that made the address of the adaptation repository invalid. [BUG] address of adaptation repo is invalid #49
I've installed Sailfish and its working fine. But i dont find access to install android apps. Is there a way to install APKs?
Thaodan said:
Without any data such as logs I can't help you. Please create a bug in the bugtracker.
Please also make sure that you flash the version that matches your device.
Please follow this article to fetch logs.
You can also try to flash the new images, I will add tomorrow.
Click to expand...
Click to collapse
First of all, many thanks for your reply - very appreciated!
Yes, I've downloaded and flashed the appropriate version (J9210, Xperia 5, DualSim). As I've bought this device as a new one about 2 years ago, I've used it that time, and it worked. The bootloader was already opened; it was rooted, because of some rooting apps.
Therefore, it was not necessary to check, if data connection, wifi, gps, camera and so on works, because it worked.
I flashed sailfish os (with the latest software binaries, Android 10, Kernel 4.14 - as in the op described [the extracted .img I've placed in the same folder as your firmware, of course]) via Linux Mint.
The device boots up flawlessly, the screen is responding without any problem, and also the intro worked.
But I can't activate wifi. I can push the button, and it responses, but it don't activates wifi. Also, my sim card won't be recognized, therefore there's no chance to enter the sim pin.
So there's a few questions:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Or is it necessary to buy a Yolla licence? No problem, I would pay for it, but the Xperia 5 isn't listed yet on your homepage...
Thanks in advance for your kind reply!
P.S.: Yes, I've tried it 4 times (went back to the latest Sony fw), and the last time I've flashed the latest Sony fw even on slot a and b before flashing Sailfish OS again (the latest [1.06] for the Xperia 5 Dual Sim variant), but unfortunately every time with the aforementioned result...
Klaus N. said:
First of all, many thanks for your reply - very appreciated!
Yes, I've downloaded and flashed the appropriate version (J9210, Xperia 5, DualSim). As I've bought this device as a new one about 2 years ago, I've used it that time, and it worked. The bootloader was already opened; it was rooted, because of some rooting apps.
Click to expand...
Click to collapse
Did you download the version for the J9210? Please check the file name of the archive.
Klaus N. said:
Therefore, it was not necessary to check, if data connection, wifi, gps, camera and so on works, because it worked.
I flashed sailfish os (with the latest software binaries, Android 10, Kernel 4.14 - as in the op described [the extracted .img I've placed in the same folder as your firmware, of course]) via Linux Mint.
Click to expand...
Click to collapse
Extracted the .img? You should extract the .zip archive, then run ./flash.sh to flash Sailfish OS to the device.
Klaus N. said:
The device boots up flawlessly, the screen is responding without any problem, and also the intro worked.
But I can't activate wifi. I can push the button, and it responses, but it don't activates wifi. Also, my sim card won't be recognized, therefore there's no chance to enter the sim pin.
So there's a few questions:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Click to expand...
Click to collapse
Sorry I forgot to post the link, please look again.
Klaus N. said:
Or is it necessary to buy a Yolla licence? No problem, I would pay for it, but the Xperia 5 isn't listed yet on your homepage...
Thanks in advance for your kind reply!
Click to expand...
Click to collapse
Not you don't need to buy a license, the device isn't support by Sailfish X (it is not available so far for community ports).
Klaus N. said:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Click to expand...
Click to collapse
@Thaodan
Thanks for providing the link!
Here's the basic-logs-2022-09-24-1031.tar from my device.
Thank's in advance!
In addition, the answers (sorry, almost forgot) to your questions:
Yes, I've downloaded the Sailfish_OS-Sailfish-SonyXperia-4.4.0.68-j9210-1.0.0.6.zip and the software binaries provided in your op.
I've only extracted the zip, but not the .img, ofc. Then I put the Software Binaries.img into the same folder as the firmware and run ./flash.sh
@Thaodan
As there's one month left in the meanwhile, I only wanted to ask, if there's some progress regarding the J9210!? Is this the wanted logs, do you need some other, or has this project stopped?
Klaus N. said:
@Thaodan
As there's one month left in the meanwhile, I only wanted to ask, if there's some progress regarding the J9210!? Is this the wanted logs, do you need some other, or has this project stopped?
Click to expand...
Click to collapse
I checked and didn't found anything obvious in your logs. I didn't had time to check your device further before my vacation.
I didn't mention it here but please open a bug report, a forum or specificly this forum thread isn't the best place to talk about issues.
My J9210 runs fine.
Thaodan said:
I checked and didn't found anything obvious in your logs. I didn't had time to check your device further before my vacation.
I didn't mention it here but please open a bug report, a forum or specificly this forum thread isn't the best place to talk about issues.
My J9210 runs fine.
Click to expand...
Click to collapse
First of all, thank you very much for your reply!
Ok, so I'll give it one more try: I will set it up with the latest Sony stock fw, put my sim-card into it and test/use everything - as described...
I'll report back!
I just checked my test phone everything works so far.
Please check if it doesn't work that you flash the latest stock version that is close to this one: 55.0.A.11.25.
Thaodan said:
I just checked my test phone everything works so far.
Please check if it doesn't work that you flash the latest stock version that is close to this one: 55.0.A.11.25.
Click to expand...
Click to collapse
The Xperia 5 firmware I've flashed is the J9210_Customized EU_55.2.A.4.332-R13C one. I'll flash it again and give SF OS another try. Perhaps it failed because my Xperia 5 was rooted and debloated; I also had AFWall+, the Xposed framework and XPrivacyLUA installed. I don't know...
Right after flashing the aforementioned fw I will test GPS, mobile data, wifi and so on, and will keep everything turned on before flashing SF OS - maybe it will work?
@Thaodan
One further question: Have you installed Sailfish OS via Windows or Linux? I did it with Linux Mint...
Klaus N. said:
The Xperia 5 firmware I've flashed is the J9210_Customized EU_55.2.A.4.332-R13C one. I'll flash it again and give SF OS another try. Perhaps it failed because my Xperia 5 was rooted and debloated; I also had AFWall+, the Xposed framework and XPrivacyLUA installed. I don't know...
Right after flashing the aforementioned fw I will test GPS, mobile data, wifi and so on, and will keep everything turned on before flashing SF OS - maybe it will work?
Click to expand...
Click to collapse
have you tried?
I want to try it again, but it's a shame if it's without a simcard or wifi.
Well, now I've flashed the J9210_Customized EU_55.2.A.4.332-R13C fw, played around with data connection, wifi, bluetooth, camera, and everything worked.
Then I tried to install SF OS via Windows 10 64 bit, but there must be a mistake inside the script. I definitely own a Xperia 5 dual-sim (J9210)!!!!!!! But: Please have a look into the attached pic...
Then I tried to flash SF OS running Linux Mint (latest stable release); the flash ran through without any error, but again: No WiFi, no data connection.
I'm about to give up!!!
One note:
I've flashed so many devices, mostly LineageOS, but also Ubuntu Touch, and never had any problem like that - unfortunately, it's annoying...
Klaus N. said:
Well, now I've flashed the J9210_Customized EU_55.2.A.4.332-R13C fw, played around with data connection, wifi, bluetooth, camera, and everything worked.
Then I tried to install SF OS via Windows 10 64 bit, but there must be a mistake inside the script. I definitely own a Xperia 5 dual-sim (J9210)!!!!!!! But: Please have a look into the attached pic...
Then I tried to flash SF OS running Linux Mint (latest stable release); the flash ran through without any error, but again: No WiFi, no data connection.
I'm about to give up!!!
One note:
I've flashed so many devices, mostly LineageOS, but also Ubuntu Touch, and never had any problem like that - unfortunately, it's annoying...
Click to expand...
Click to collapse
Isually use Linux to flash but also should have checked the Windows flash script.
Please edit the batch script you called and replace j9210 with J9210.
I just fixed the issue but for now just change the flash script for Windows:
[BUG] Device is invalid in windows flashing script for Xperia 5/j9210 · Issue #50 · SailfishOS-SonyXperia/bugs
The @[email protected] in the kickstart script is written as j9210 but it should be J9210.
github.com
Thaodan said:
Isually use Linux to flash but also should have checked the Windows flash script.
Please edit the batch script you called and replace j9210 with J9210.
I just fixed the issue but for now just change the flash script for Windows:
[BUG] Device is invalid in windows flashing script for Xperia 5/j9210 · Issue #50 · SailfishOS-SonyXperia/bugs
The @[email protected] in the kickstart script is written as j9210 but it should be J9210.
github.com
Click to expand...
Click to collapse
Thank you very much for the response - and your efforts, ofc!
Finally: It works
I had not to flash the latest firmware (doesn't work), but a rollback to the J9210_Customized EU_1320-0801_55.1.A.9.52_R10B fw before flashing Sailfish OS did the trick!

Categories

Resources