This post is closed. All developers had been informed and I think this thread is not explained as it must be (is not a thing of aquas only). Just two different sensors in each device...
https://github.com/sonyxperiadev/kernel/issues/353
However it's not something exclusive from Aqua, but also for some other models like D2303 in the 'new period' as you can see here: http://forum.xda-developers.com/showpost.php?p=60797370&postcount=192
I thought the normal m2 was the same, it must be a model revision due to the Accelerometer bug that has been affecting certain production runs. Gonna find out when mine was made had it since beginning of Sept last year not had this bug yet
D2303 stock deodexed 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality
Nice one @linuxct!
Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.
After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
galaxyfreak said:
Nice one @linuxct!
Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.
After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
Click to expand...
Click to collapse
Sounds interesting!
I'd like to do it. But unfortunatetly, I dont' know too much of ROMS, and I don't know exactly for compare the accelerometer drivers and do it compatible with custom roms
galaxyfreak said:
Nice one @linuxct!
Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.
After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
Click to expand...
Click to collapse
I've tried to do it. But I don't find any accelerometer driver in Sony's archive (?)
Also, exams are very close... Might try again after finishing
linuxct said:
I've tried to do it. But I don't find any accelerometer driver in Sony's archive (?)
Click to expand...
Click to collapse
drivers/input/misc/kionix_accel.c
galaxyfreak said:
drivers/input/misc/kionix_accel.c
Click to expand...
Click to collapse
Oh thanks, I was actually looking for an 'accel' folder :silly:. As I said I will try after exams
@linuxct Now when panel on new models and Aqua is solved, before I pull the trigger (add Aqua models to OTA assert, so you can flash the zip), I wanted to look into this.
I don't seem to have accelerometer (kxtj2) on any input. And I'm sure it's working.
How am I supposed to debug this
getevent:
[email protected]:/ # getevent
getevent
add device 1: /dev/input/event7
name: "msm8226-tapan9302-snd-card Headset Jack"
add device 2: /dev/input/event6
name: "msm8226-tapan9302-snd-card Button Jack"
add device 3: /dev/input/event0
name: "cyttsp4_mt"
add device 4: /dev/input/event3
name: "qpnp_pon"
add device 5: /dev/input/event2
name: "proximity"
add device 6: /dev/input/event1
name: "lightsensor-level"
could not get driver version for /dev/input/mice, Not a typewriter
add device 7: /dev/input/event5
name: "gpio-keys"
add device 8: /dev/input/event4
name: "qpnp_chg_unplug_key"
[email protected]:/ # getevent -li /dev/input/event6
getevent -li /dev/input/event6
add device 1: /dev/input/event6
bus: 0000
vendor 0000
product 0000
version 0000
name: "msm8226-tapan9302-snd-card Button Jack"
location: "ALSA"
id: ""
version: 1.0.1
events:
KEY (0001): KEY_MEDIA BTN_1 BTN_2 BTN_3
BTN_4 BTN_5 BTN_6 BTN_7
input props:
<none>
[email protected]:/ # getevent -li /dev/input/event7
getevent -li /dev/input/event7
add device 1: /dev/input/event7
bus: 0000
vendor 0000
product 0000
version 0000
name: "msm8226-tapan9302-snd-card Headset Jack"
location: "ALSA"
id: ""
version: 1.0.1
events:
SW (0005): SW_HEADPHONE_INSERT SW_MICROPHONE_INSERT SW_LINEOUT_INSERT 000e
000f 0010 0011
input props:
<none>
[email protected]:/ #
Click to expand...
Click to collapse
galaxyfreak said:
@linuxct Now when panel on new models and Aqua is solved, before I pull the trigger (add Aqua models to OTA assert, so you can flash the zip), I wanted to look into this.
I don't seem to have accelerometer (kxtj2) on any input. And I'm sure it's working.
How am I supposed to debug this
getevent:
Click to expand...
Click to collapse
Oh, wow. And also you have the gpio-keys placed in event5, it's the first time I see this.
However I must say, the person who had the event7 problem is @iFlashed, not me, as I have old D2303, with event6. I only helped him to discover what was wrong.
Now, if the accel is not placed in any event, then how is it working? Other way of input ??
I'm checking in my device and there's not kxtj2 nor accel... event3 throwed an out-of-memory error btw.
Tell us what to try/do and we'll try.
stock 3.4 and 3.10 have very different sensor implementation.
How did you relate bootloops on Omni and CM12 with sensors.
linuxct said:
Oh, wow. And also you have the gpio-keys placed in event5, it's the first time I see this.
However I must say, the person who had the event7 problem is @iFlashed, not me, as I have old D2303, with event6. I only helped him to discover what was wrong.
Click to expand...
Click to collapse
Information for shifted gpio-keys is known by more than two months.
source
AleksJ said:
Information for shifted gpio-keys is known by more than two months.
source
Click to expand...
Click to collapse
They found before... LOL
That's the problem of local forums, people have to discover things twice if they don't publish it in global-english forums like this one.
However, we still don't know why Sony did this... I can't understand them.
linuxct said:
They found before... LOL
That's the problem of local forums, people have to discover things twice if they don't publish it in global-english forums like this one.
However, we still don't know why Sony did this... I can't understand them.
Click to expand...
Click to collapse
Yes, and that was the reason for the changes, and why they were made hardly anyone here can say with certainty.
What does it matter forum or palace if problem still exist ?
btw, they already published here
AleksJ said:
Yes, and that was the reason for the changes, and why they were made hardly anyone here can say with certainty.
What does it matter forum or palace if problem still exist ?
btw, they already published here
Click to expand...
Click to collapse
What he published didn't work tho, as iFlashed device uses event7 and inside!out give him a boot.img with event4 in bootrec-device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If sony could give us any explanation on why they did this...
messing with sensors in 3.10 will not work. It will probably lead to more bootlooping.
Could you try this workaround? it is sony's stock solution for inputdevices.
https://github.com/android-legacy/a...mmit/491bb77288a5941eba7bdd14fbf5d28470971f0b
you will have to implement it in 3.10 kernel. If you cannot succeed pm or gtalk me, I will do
keep in mind it is a workaround. If this works out, well, with my truly panel fresh in mind, we have to check for a proper solution to get it in sxd kernel.
linuxct said:
If sony could give us any explanation on why they did this...
Click to expand...
Click to collapse
It is probably a hardware mounting things. A lot of electronics have to be mounted in a small device.
If hardwaremounting changes because of using another part for whatever reason (innoluxpanel is mounted up-down, truly is not), that has consequences for programming hardware in kernel. (innolux is flipped up-down in paneldriver, truly is not in de same driver).
Using different hardwareparts for same model is quite common in phones.
It kind of surprises me that no users haven't complained about a sensor not working. In the kernel there is another sensordriver present (bma250 if I remember correctly) which is compiled for eagle, but not fixed yet. Apperently there is still no user who has this particular hardware part in his phone and we (untill now) all share the same sensor hardware so it functions for everyone
erikcas said:
messing with sensors in 3.10 will not work. It will probably lead to more bootlooping.
Could you try this workaround? it is sony's stock solution for inputdevices.
https://github.com/android-legacy/a...mmit/491bb77288a5941eba7bdd14fbf5d28470971f0b
you will have to implement it in 3.10 kernel. If you cannot succeed pm or gtalk me, I will do
keep in mind it is a workaround. If this works out, well, with my truly panel fresh in mind, we have to check for a proper solution to get it in sxd kernel.
Click to expand...
Click to collapse
Nice. I just contacted you through Hangouts.
Thanks!
linuxct said:
What he published didn't work tho, as iFlashed device uses event7 and inside!out give him a boot.img with event4 in bootrec-device
If sony could give us any explanation on why they did this...
Click to expand...
Click to collapse
Means nothing, bootrec-device is no longer used with new recovery.
galaxyfreak said:
Means nothing, bootrec-device is no longer used with new recovery.
Click to expand...
Click to collapse
Yeah, true, but I was just showing what was the problem with prebundled recoveries in boot.img...
Related
. .
cardsharing said:
Hi all developers, i open this thread about porting kernel for photon here. Im working on it and here is interested stuf about bcm4329
Click to expand...
Click to collapse
good link, will follow it!
i'm sure we can find useful stuff on 2.6.32 and backport on 2.6.29.
differences between arch/arm/msm on both versions are quite big, thus im not sure how easy it is to upgrade photon kernel.
i found a way to get some terminal console and some debug outbut:
just install the HTC Sync for HTC Aria, it gives you the USB ADB driver: link here
Then, in a command window, execute following commands:
Code:
adb devices => tells you if your device is recognized
adb shell => launch a basic linux shell
type "dmesg" to have the debug message
"dmesg | /bin/more" to have the same but page by page (press space enter to go next page)
you can also install android applications:
adb install <name of file>
Click to expand...
Click to collapse
at first look, you can see the kernel is compiled with loaaads of debug output.
and we can already see a recurrent segfault that might be the cause of some of the issues we have.
Note: adb.exe enclosed in zip file of this message
Maybe it's a good idea to make a list of all issues we experience at this moment in the first post. That way, we can handle them one by one
This is my list now:
- Battery driver doesn't work.
- Maybe that has to do with the battery driver, but when I use my device with Android for about a half an hour (Angry Birds), the back side comes very warm...
- Data not working (WiFi and GPRS as well)
- Buttons need realignment
- Sometimes it happens that when I turn my device off just with the power button, the lights under the hardware keys keep going.
guys have you seen here?
http://forum.xda-developers.com/showpost.php?p=11390094&postcount=6
Kernel 2.6.32 with Android 2.3 on HTC Aria!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm trying to find where they got the kernel 2.6.32, in cyanogen repository the kernel stops at 2.6.29:
https://github.com/CyanogenMod/htc-kernel-liberty
-r0bin- said:
guys have you seen here?
http://forum.xda-developers.com/showpost.php?p=11390094&postcount=6
Kernel 2.6.32 with Android 2.3 on Aria!
Click to expand...
Click to collapse
And can we get Aria kernel working on Photon? Can you do this?
_Madmatt said:
And can we get Aria kernel working on Photon? Can you do this?
Click to expand...
Click to collapse
yes, cotulla used the kernel of liberty (which is HTC Aria)
actually I think I found the latest kernel \o/
https://github.com/attn1/htc-kernel-msm7227
done by attn1, main contributor of cyanogen for HTC Aria/Liberty
let's try this!!!
-r0bin- said:
yes, cotulla used the kernel of liberty (which is HTC Aria)
actually I think I found the latest kernel \o/
https://github.com/attn1/htc-kernel-msm7227
done by attn1, main contributor of cyanogen for HTC Aria/Liberty
let's try this!!!
Click to expand...
Click to collapse
Try? Shouldn't we do some modifications first?
_Madmatt said:
Try? Shouldn't we do some modifications first?
Click to expand...
Click to collapse
yes, we need to implement cotulla's patch
seems he duplicated the "liberty" files to "photon" in arch/arm/msm and did light modifications
we can do a diff vs the htc aria official source code to have it all
-r0bin- said:
yes, we need to implement cotulla's patch
seems he duplicated the "liberty" files to "photon" in arch/arm/msm and did light modifications
we can do a diff vs the htc aria official source code to have it all
Click to expand...
Click to collapse
Can you do that? I don't have enough Linux knowledge But I'm always ready to try kernels
-r0bin- said:
yes, we need to implement cotulla's patch
seems he duplicated the "liberty" files to "photon" in arch/arm/msm and did light modifications
we can do a diff vs the htc aria official source code to have it all
Click to expand...
Click to collapse
Attention!
i do not want to pick at cotulla, but in fact we want to use his changes for another port it is to say: his code is kind of mess
you can really see that he stopped working on it instantly..
Either someone cleans this up or you will really have to understand what he intended to do!
schlund said:
Attention!
i do not want to pick at cotulla, but in fact we want to use his changes for another port it is to say: his code is kind of mess
you can really see that he stopped working on it instantly..
Either someone cleans this up or you will really have to understand what he intended to do!
Click to expand...
Click to collapse
Well..I think the reason he stopped instantly is here
Cotulla dumped the project few hours after this post,some of you may call it coincidence,but i think Cotulla was reading what we were writting there.
helping someone who is swearing you work is....(i don't wanna use bad words)
if i were him i will do exactly the same!
we need to be thankful that he even released the working haret for us
. .
who can tell ...
hi I want to know about how to custom the haret image. and how to solve the connect problem. so does the battery. so just tell me the general steps.. I am willing to test the image. thanks all the developers.
cardsharing said:
Guys i will post tomorow here all modified 2.6.32 files, dont have time to upload in this time.
Click to expand...
Click to collapse
yeah we'll all be interested to have that.
cardsharing said:
P.S. tracaplaca my english is bad and im sorry for this, ok? PLEASE froget me and my post and please dont post here if your post is not about developming, PLEASE, OK? Cotulla have donatins from me ten minutes after his post abut working photon project and this was my big thanks to big Cotula. So please forget all old posts and please back to post, ok?
Click to expand...
Click to collapse
hey guys don't fight
schlund said:
Attention!
i do not want to pick at cotulla, but in fact we want to use his changes for another port it is to say: his code is kind of mess
you can really see that he stopped working on it instantly..
Either someone cleans this up or you will really have to understand what he intended to do!
Click to expand...
Click to collapse
agree with you.
i'm not sure every single modification is required (code looks like "modif here, compile and see if it works better"), but it's incredible chance to have a working source code and we all thanks cotulla for his work. this way we have a chance to have a clean code starting from the liberty/aria source code.
it seems he tried to investigate the wifi issue (many wifi files modified compare to liberty) but with no luck.
in the kernel configuration he released, he said we could get the kernel debug traces on the PC.
do you guys know how to get it? plugging usb cable when android is booting does not seems to help.
reason I'm asking is, it seems there are lot of debug informations available but so far i cannot access to them...
-r0bin- said:
agree with you.
i'm not sure every single modification is required (code looks like "modif here, compile and see if it works better"), but it's incredible chance to have a working source code and we all thanks cotulla for his work. this way we have a chance to have a clean code starting from the liberty/aria source code.
it seems he tried to investigate the wifi issue (many wifi files modified compare to liberty) but with no luck.
in the kernel configuration he released, he said we could get the kernel debug traces on the PC.
do you guys know how to get it? plugging usb cable when android is booting does not seems to help.
reason I'm asking is, it seems there are lot of debug informations available but so far i cannot access to them...
Click to expand...
Click to collapse
maybe is this
http://droidbar.net/2010/09/how-to-enable-usb-debugging-mode/
That option is enabled by default on the 2.2. image that have been posted.
I think you have to use adb tool as said here to see the output.
. .
thanks! yeah you see it takes time
can you compile the kernel and send the zImage as well?
. .
[DESIRE HD NOKIA X PORT]
I've decided to open a new thread, especially since the previous thread is discontinued. I wanted to highlight progress is very much being made on the Nokia X port for the Desire HD.
When I mention progress, the build boots now; As I've re-based, re-structured and circumvented the issue's preventing a boot.
That's not to say this ROM is functional as a daily driver in it's current status, as it is quite the opposite.
However great strides are being made and success comes with the cost of time, effort and dedication from our developers.
This thread is open now as an invitation to ANY developer that:
1) is interested in this project
2) capable of pushing the project forward in effort to solve existing bugs
3) willing to spare their time to aid development.
As it stands I've done all the leg work getting the build to boot, and only since then I've had some assistance from a couple of sources in solving a few other issues in build.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Developer Activity Status:
At the moment I'm getting some priceless help in patching MSimTelephony references in build from another XDA Dev here, doing wonderful work and I anticipate that we can in fact succeed in a functional port in the near future.
Thus far our current efforts are focused on fixing radio, data and ril so bare with our current working/non-working log below...
(as a result of the above SystemUI is now beginning to respond as should, albeit a few flaws which are actively being ironed out)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Updates:
07/04/14 - [SYSTEMUI] System Statusbar and MSimTelephony references patched @SystemUI/classes.dex [Developer: opssemnik]
07/04/14 - [LIBRARY] Proximity and capacitive Light Sensors are now working [Developer: s89]
08/04/13 - [UPDATE] Investigating possibility of a System Wrapper to patch boolean isMultiSimEnabled @TelephoneManager and other related MsimTelephony calls globally. Eclipse app wrapper begun...
08/04/13 - [STUCTURE] Re-established 4.1.2 kernel, modules, hw and libraries to establish a common base and satisfy kernel requisites. [Developer: s89]
10/04/13 - [UPDATE] Wrapper implemented in build now and loading. Let the MSimTelephony patches commence [Developer: opssemnik]
12/04/13 - [SYSTEM] WIFI Fixed - Correct mismatched blobs and re-worked boot.img to fix Wifi and module loading issues. [Developer: s89]
12/04/13 - [SYSTEM] USB Mount Fixed - Patched storage-list.xml [Developer: opssemnik]
12/04/13 - [UPDATE] GPS Fixed
Click to expand...
Click to collapse
.............: Working :.............
USB Storage
Wifi
GPS
Vibrate
Touchscreen
Hardware|Capacitive Buttons
Display
Battery Sensor
Hardware Acceleration
Light Sensors
..........: Not working :..........
USB Storage
Sound
Camera
Radio
GPS
Wifi
Bluetooth
Light Sensor
.................Probably more
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note: This ROM and Thread is intended for Developer activity only. Please do not fill this thread with spam, jargon and/or testing requests. This includes update requests (FYI All progress will be documented regularly within this post).
I am aware of most if not all of the currently not working and am actively resolving what I can, when I can.
All I ask is for is your patience and support > Public testing will be announced when most if not all the major show stopping bugs have been resolved.
Click to expand...
Click to collapse
If you are interested in joining efforts in minimizing our "Not working" list, feel free to contact me or write a request of interest here.
All and any updates to our current build that address an issue in our bug's list must be communicated back and consolidated into our output build to ensure all developers are up-to-date with the latest changes/bug fixes.
Current Team | Contributing Developers::
stickman89 [s89;] - Porting NokiaX build inc, fixing libraries, patching framework & ramdisk updates.
opssemnik - SystemUI, MSimTelephony Patches & continued wrapper development
Click to expand...
Click to collapse
Reserved...
good job,thanks
wow.......nice work devz
chrisb906 said:
I know this..just letting dev know
Sent from my Desire HD using Tapatalk
---------- Post added at 05:18 AM ---------- Previous post was at 05:15 AM ----------
Oops. Just realized he didn't want test requests on here..lol. My bad
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Yup, this is a DEV thread. Still lots too fix i.e. would like a dev collaboration since I've spent a lot of hours getting us to this point and feel it would be less stressful on me having some more capable hands in the kitchen.
OK NokiaX isn't dependent on ION so I rebuilt with correct kernel, modules, hw and added libraries from our 4.1.2 build however audio is NOT getting loaded for some reason. As far as I'm aware __strlen_chk is referenced at libc.so and libcrypto.so however I've replaced these libraries with that from a functional 4.1.2 build of ours and it's still not loading. Any devs here encountered this? If so which libraries are associated with it?
Code:
E/HAL ( 1424): load: module=/system/lib/hw/audio_policy.default.so
E/HAL ( 1424): Cannot load library: reloc_library[1331]: 1424 cannot locate '__strlen_chk'...
I think we have the same problem with sense 5 too
Gesendet von meinem One X mit Tapatalk
besimm said:
I'm interested on this ROM, can you give me the link??
Click to expand...
Click to collapse
All I ask is for is your patience and support > Public testing will be announced when most if not all the major show stopping bugs have been resolved.
Click to expand...
Click to collapse
No he can't , please be patient , the OP has his own closed testers group and he will release a public test rom when ready.
SO be patient !!!!
EDIT: THREAD CLEANED, STOP ASKING FOR LINKS !!!
THE DEV WILL RELEASE WHEN READY.
Stickman89 said:
OK NokiaX isn't dependent on ION so I rebuilt with correct kernel, modules, hw and added libraries from our 4.1.2 build however audio is NOT getting loaded for some reason. As far as I'm aware __strlen_chk is referenced at libc.so and libcrypto.so however I've replaced these libraries with that from a functional 4.1.2 build of ours and it's still not loading. Any devs here encountered this? If so which libraries are associated with it?
Code:
E/HAL ( 1424): load: module=/system/lib/hw/audio_policy.default.so
E/HAL ( 1424): Cannot load library: reloc_library[1331]: 1424 cannot locate '__strlen_chk'...
Click to expand...
Click to collapse
Did you try with "readelf" ? Maybe you can compare after with what you have and what is missing.
Wrapper implemented in build now and loading. Let the MSimTelephony patches commence. Lots of good stuff happening
RIL work's at this moment (SMS, Calls, USSD, 3G) ?
RazGame said:
RIL work's at this moment (SMS, Calls, USSD, 3G) ?
Click to expand...
Click to collapse
Not just yet, but we haven't finished tracing, debugging and adding Telephony calls to our wrapper. By all mean's not a quick process and ended up being a late night, I'm still wearing my sleepy face aha.
Telephony isn't registering a network as we've intentionally left methods out for the time being as there is more patching to do to SystemUI in regards to directing our new calls. More to continue tonight I imagine so all on your list is a nono for the time being.
If you can give me the files of the ROM I an take a shot in fixing the Storage issue as I am experienced in porting and specifically fixing this bug Have a nice day bro.
CedArctic said:
If you can give me the files of the ROM I an take a shot in fixing the Storage issue as I am experienced in porting and specifically fixing this bug Have a nice day bro.
Click to expand...
Click to collapse
Excellent, be more then welcome to have you aboard. We have a new SystemUI patch to update in build at some point tonight, once that's applied, I'll upload the updated build for your handy work good sir. You'll receive a PM once uploaded.
dont tell anyone you saw this, shhh
usb fixed
wifi fixed
plot twist:
gps fixed
Stickman89 said:
OK NokiaX isn't dependent on ION so I rebuilt with correct kernel, modules, hw and added libraries from our 4.1.2 build however audio is NOT getting loaded for some reason. As far as I'm aware __strlen_chk is referenced at libc.so and libcrypto.so however I've replaced these libraries with that from a functional 4.1.2 build of ours and it's still not loading. Any devs here encountered this? If so which libraries are associated with it?
Code:
E/HAL ( 1424): load: module=/system/lib/hw/audio_policy.default.so
E/HAL ( 1424): Cannot load library: reloc_library[1331]: 1424 cannot locate '__strlen_chk'...
Click to expand...
Click to collapse
Just an update, we already fixed this, just need some smali patching and then audio should work.
any processing?
we are waiting for it
opssemnik said:
Just an update, we already fixed this, just need some smali patching and then audio should work.
Click to expand...
Click to collapse
where is the updating?
if the sound IS ok,upload it plz,thx in advance.
admet615 said:
we are waiting for it
Click to expand...
Click to collapse
Update & Download Link
hi, its been months now, pls whats the progress? we are patiently waiting for an update and download link.
I know the issue has been the sound, how far has it gone. pls keep us updated.
i port cm12.1 from source
with original stok kernel(ramdisk change)
but not working
cell network( that is missing library from stock rom. i find it)
wifi network
blue tooth turn on but maybe not working (i tested it)
nfc not working
sound not working
almost not working
im newbie newbie
so i dont know how to fix
my github is https://github.com/wwwhana
somebody help me?
read thx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kernel cmd
mkbootimg --base 0x00000000 --kernel <zImage> --ramdisk <ramdisk.img> --ramdisk_offset 0x02000000 --dt <dt.img> --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcomyukon user_debug=31 msm_rtb.filter=0x37 androidboot.bootdevice=msm_sdcc.1 slub_min_objects=4 build_variant=user msm_rtb.enable=0" --output <boot.img>
Go to the cyanogenmod forums and ask there.
status
wifi is not working(i dont know why doesn't work it...pront wlan build with kernel....)
camera is not working *this is dosent work camera hal...
audio is sometime build working anothertime is not working
brigtness not working but modified /sys/class/leds/lm3630-lcd-bl/brightness can change
nfc is maybe working(possible turn on off)
bluetooth is working pair possible
baseband(cellular networking) is possible when dumping /bin, /lib, /vendor folder
sensors is maybe not working(i see logs.....many mnay errors....)
who are help me??
Help might have arrived... (I think)
wwwhana said:
wifi is not working(i dont know why doesn't work it...pront wlan build with kernel....)
camera is not working *this is dosent work camera hal...
audio is sometime build working anothertime is not working
brigtness not working but modified /sys/class/leds/lm3630-lcd-bl/brightness can change
nfc is maybe working(possible turn on off)
bluetooth is working pair possible
baseband(cellular networking) is possible when dumping /bin, /lib, /vendor folder
sensors is maybe not working(i see logs.....many mnay errors....)
who are help me??
Click to expand...
Click to collapse
Ah... another one. It seems you have gotten further than me. I'm having a look at your GitHub, maybe I can find something there. We are both new to this though, so maybe teaming up would be a good idea. Please contact me at [email protected] so that we can talk further.
Thanks
Riccorbypro
oh tanks
Riccorbypro said:
Ah... another one. It seems you have gotten further than me. I'm having a look at your GitHub, maybe I can find something there. We are both new to this though, so maybe teaming up would be a good idea. Please contact me at [email protected] so that we can talk further.
Thanks
Riccorbypro
Click to expand...
Click to collapse
i first try build from source. so, just booting but not working every thing
base device tree is tianchi(this device is same stock rom build! and family device)
so i dump from sony stock rom (if exist file not over write)
working cellnetworking
and i try something do...
i try insmod /system/lib/modules/wlan.ko
it working! wifi when type this command
but....i try now but not working....
i use
" http://forum.xda-developers.com/showthread.php?t=2545618 "
this trick
how to base cm rom and i just change lib folder from stock sony rom. i change file about runtime file(libart, linandroid~)
we can get cell networking, camera(!!!) HAL so, if this device need like sony openproject vendor file (that is not equeal) and some orinal library and /bin file need it
but not working gravity sensors...wifi(if shutdown se linux affter insmode...maybe working?).....and not led control(this front led, lcd backlight)
but working near seonsor(display off and do not touch when calling)
so i upload this result....
Just in case I'll put this file.
it's your devlopment and For those who are interested
http://www.mediafire.com/download/ewq6k6nda8a1ssc/and.7z
you can flash use
"fastboot flash system system.img"
fastboot flash boot boot.img"
and this is this rom logs
https://gist.github.com/wwwhana/2586f04fadf6bb59f5b5
thank you.
read my bad english.
xposed also working
Although of course, this is base is aosp so working
i try install xpoesed framework. so, not problem....
so i want this rom is perfect.....
and
that rom is working sound, nfc and already working list
wwwhana said:
Although of course, this is base is aosp so working
i try install xpoesed framework. so, not problem....
so i want this rom is perfect.....
and
that rom is working sound, nfc and already working list
Click to expand...
Click to collapse
*xposed working*
You now have my attention :good:
wifi f#[email protected]#$%
wifi need firmware file in firmware_bin where https://github.com/sonyxperiadev/prima 's prima tree
so now, Xperia c3 with C3(D2533) for cm-12.1 working list
cell networking
wifi
bluetooth
nfc
audio
maybe comming soon working
camera with torch(i find need camera files)
don't working
front led
rotation sensor
lcd-backlight
and i don't know any sensors....
i will comming final test this semester...
so i will comming 12/12 KST
Thank You
Dual sim model?
sorry
i Can't testable xperia C3 dual model
cause i'm not have them
if some one try my test rom, and say to here result
maybe Assuming working, that rom but not working 2nd sim
IF someone try it?
From what I've seen, the kernel for D2533 and D2502/D2503 is the same, there is no difference in the tree. So theoretically there should be one universal build, for both single sim and dual sim.
Sent via Carrier Pigeon
Sensors....
insert sensors.qcom.so
i get infomation about sensors but they not working...
maybe they not connect Android framework
and gps is not working....
cause FLP HAL is not initialize
show me error
missing library? no that.
logs say
07-03 14:18:25.128 764-764/? E/HAL: load: module=/vendor/lib/hw/flp.default.so
dlopen failed: cannot locate symbol "_ZN9LocApiV0216deleteAidingDataEj" referenced by "liblbs_core.so"...
07-03 14:18:25.128 764-764/? E/FlpHardwareProvider: Error hw_get_module 'flp': -22
07-03 14:18:25.129 764-764/? E/LocationManagerService: FLP HAL not supported
07-03 14:18:25.133 764-764/? E/LocationManagerService: Unable to bind FLP Geofence proxy.
Click to expand...
Click to collapse
why not?
Have you checked in CPU-Z if there is information coming from the sensors? I have no idea what's going on with the HAL though... Maybe the sensors.so is related to the HAL, so one won't work without the other...
Sent via Carrier Pigeon
Riccorbypro said:
Have you checked in CPU-Z if there is information coming from the sensors? I have no idea what's going on with the HAL though... Maybe the sensors.so is related to the HAL, so one won't work without the other...
Sent via Carrier Pigeon
Click to expand...
Click to collapse
i think that file name "jni" relate to HAL
Sony device have not camera hal
but jni file is replace that....
maybe sensor also?
Will CM12.1 remove the camera noise/blur?
sorry
AutumQueen92 said:
Will CM12.1 remove the camera noise/blur?
Click to expand...
Click to collapse
i don't know that
but we can't have camera sensor source
so maybe equal stock rom
wwwhana said:
i don't know that
but we can't have camera sensor source
so maybe equal stock rom
Click to expand...
Click to collapse
Well that's disappointing. I was hoping to find a mod for the camera but nothing came up, only Bravia Engine stuffs.
collect sensor log from stock
under link is log from stock rom about sensors
https://gist.github.com/wwwhana/983cae21f13b4e5ed29f
QTI waring/Error is also stock rom....
camera also sam error and warnig my rom
but other sensors?
we know light sensor name is apds9930_als.....
Input path = /sys/devices/virtual/thermal/thermal_zone[0~5]/temp
Ah! i tested near sensor working when call
but others not working....
sensor made me hard....
dual sim kernel maybe not equal single sim
Riccorbypro said:
From what I've seen, the kernel for D2533 and D2502/D2503 is the same, there is no difference in the tree. So theoretically there should be one universal build, for both single sim and dual sim.
Sent via Carrier Pigeon
Click to expand...
Click to collapse
i see about board-sony_tianchi.c and board-sony_tianchi_dsds.c
so i see that difference gpio.....
maybe also difference C3
who try made gpio map for dual sim?
wwwhana said:
i see about board-sony_tianchi.c and board-sony_tianchi_dsds.c
so i see that difference gpio.....
maybe also difference C3
who try made gpio map for dual sim?
Click to expand...
Click to collapse
No one that I know of... I'm the only person that I know that has this phone, and my carrier never sold the dual-sim version anyway, so i think we're going to have to try our best and get a tester for the dual-sim kernel.
Also, any idea why the f2fs compile is failing?
The error:
Code:
system/extras/f2fs_utils/f2fs_utils.c:53:13: error: 'struct f2fs_configuration' has no member named 'kd'
make Error 1
Riccorbypro said:
No one that I know of... I'm the only person that I know that has this phone, and my carrier never sold the dual-sim version anyway, so i think we're going to have to try our best and get a tester for the dual-sim kernel.
Also, any idea why the f2fs compile is failing?
The error:
Code:
system/extras/f2fs_utils/f2fs_utils.c:53:13: error: 'struct f2fs_configuration' has no member named 'kd'
make Error 1
Click to expand...
Click to collapse
.....?
I never get error like that....
if try "rm system/extras/f2fs_utils " and retry repo sync
IUNI U3 KERNEL DEVELOPMENT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Disclaimer:
It's still under development.
I waive all liability... Thermonuclear war will happen whatever you use this kernel or not.
Feel free to contribute, share, participate, post or help it would make me great pleasure!
Introduction
This project aim to develop a kernel for the IUNI U3 able to turn on the latest version of Android and to meet the challenge proposed by IUNI.
The purpose of this post is:
Highlight the development progression.
Log the errors and bugs remaining to be fixed.
Transmit solutions of issues encountered to help those who will have the same kind of error to fix it.
Exchange and learn all together and find out how to fix those bugs.
Click to expand...
Click to collapse
Sources code
Official kernel source: https://gitlab.com/iuni/u3/tree/master/gionee/alps_drv/kernel
Kernel source: https://github.com/Abdess/android_kernel_iuni_msm8974
Device tree & other: https://github.com/Abdess?tab=repositories
Click to expand...
Click to collapse
How-to compile it
Just follow this GUIDE and this README
Click to expand...
Click to collapse
Good to know
About official source code:
The original CAF kernel source code is downloadable HERE
Common drivers are located at gionee/alps_drv
IUNI U3 specific drivers are located at gionee/project/NBL8910A
IUNI U3 Mini specific drivers are located at gionee/project/NBL8905A
The repo use a special script to compile Android with specific "GN_FLAGS" who're located into the gn_project folder, those flags are added on-the-fly and are not integrated into the kernel.
Click to expand...
Click to collapse
State
Working:
Everything
Semi-working:
Nothing
Not working:
Nothing
?:
Nothing
Click to expand...
Click to collapse
Logs
XDA:DevDB Information
IUNI U3, Kernel for all devices (see above for details)
Contributors
Abdess76, Angel_666, feroxxx, alecuba16, 蝴蝶剑
Source Code: https://github.com/Abdess/android_kernel_iuni_u3
Kernel Special Features:
Version Information
Status: Alpha
Created 2017-08-31
Last Updated 2018-01-29
Changelog:
September 4th, 2017:
Kernel:
*Internal storage works
Logs:
dmesg
recovery
Click to expand...
Click to collapse
Original dmesg for comparison
Old changelogs:
August 31, 2017:
*Initial release
Because ADB doesn't works and I can't do an UART, the only way to extract logs of the compiled TWRP recoveryimage is to go into ADVANCED -> TERMINAL and type:
Code:
dmesg
Then take pics of important part of the log
Log pics are uploaded HERE
Log pictures:
1:
2.
3.
4.
5.
6.
7.
8.
Click to expand...
Click to collapse
Miscs
How it looks:
Nice work, might have a play with this over the weekend, although my skills are pretty limited.
Hi! Any news? seems that there no new step forward
Hi, anyone here who want to sell his IUNI U3?
I like it very much but left sim Slot for 4G is not
working and no one can repair.
Hello. That there on the kernel?
I thought the release of the code source would boost developers but it seems nobody wants to work on the U3 anymore, too bad
Hi,
Sorry for not giving any news for a long time, I sorely missed free time.
The kernel is now 100% functional on Android N. There are still some small issues and optimisations to fixes before everything is perfect.
It remains to complete the device tree and blobs to be finally ready.
The project was able to move forward with the help and support of several developers who generously gave their time to help and answer questions:
- @Sultanxda : The kernel is entirely based on his work, and moreover he helped me with all questions and technical problems.
- @feroxxx : It is thanks to him that LineageOS 14.1 is almost fully working on IUNI U3
- @nathanchance : Thanks to his documentation and availability to answer to the questions on the forum he has expanded my knowledge and awareness of security.
- @jerpelea and @GalaticStryder : They helped me to understand some technical and theoretical aspects of the kernel.
And of course also to all those who contributed to all these open-source projects without whom this project would never have emerged.
Thanks, thanks and thanks and thanks again!!!!!
Qidamin said:
Thanks, thanks and thanks and thanks again!!!!!
Click to expand...
Click to collapse
:highfive:
I'll have to update the thread with more details and more regularly, like a log. The goal is to highlight the path used in the development of the kernel. The mistakes made, by which means they were solved.
The intention is to provide answers to questions that a person might ask if he wants to undertake a similar project.
When starting a project for the first time, there is often this famous stage of vast questioning and gray area. With a large amount of documentations, wondering where to start, where to go. Reading the practical experience of others could be a shortcut in the learning journey and have an idea where to start and where to go.
Soon there will be a key to the surprise that IUNI was talking about.)))
Hi, Abdess. When to expect firmware release?
Zewius21 said:
Hi, Abdess. When to expect firmware release?
Click to expand...
Click to collapse
Most likely when it's ready.
Zewius21 said:
Hi, Abdess. When to expect firmware release?
Click to expand...
Click to collapse
Hi, Zewius21. I am sorely lacking time to work on it.
It may take time, unless someone wants to join me in the development.
Zewius21 said:
Soon there will be a key to the surprise that IUNI was talking about.)))
Click to expand...
Click to collapse
They released their surprise and a secret message.
mikeysteele said:
Most likely when it's ready.
Click to expand...
Click to collapse
Haha, exactly.
Ok the kernel source code for LOS 15.1 is available here: https://github.com/Abdess/android_kernel_iuni_msm8974/tree/lineage-15.1
There's a weird issue, everythings looks to works fine (adb, storage, brightness)... into the log... However the display doesn't works but it's acting like working.
It looks like I've to check the MDSS drivers and device tree.
Hi @Abdess76, I just tried building Lineage 14.1 off your sources. It built OK but it doesn't boot . It appears ADB isn't running despite building with user-debug and I can't seem to find any logs in /proc/last_kmesg. Any suggestions as to what I'm doing wrong?
Thank you for adding me to contributors,but how do you find my id in xda?Besides,How is the kernel going?
mikeysteele said:
Hi @Abdess76, I just tried building Lineage 14.1 off your sources. It built OK but it doesn't boot . It appears ADB isn't running despite building with user-debug and I can't seem to find any logs in /proc/last_kmesg. Any suggestions as to what I'm doing wrong?
Click to expand...
Click to collapse
Good question, we can see this together on hangout.
蝴蝶剑 said:
Thank you for adding me to contributors,but how do you find my id in xda?Besides,How is the kernel going?
Click to expand...
Click to collapse
I do not remember how I did to find you. lol
I had to make another break because of the work. Everything works however there is always this display bug. I must find the cause.
https://github.com/Abdess/android_k...mmit/3e0db6ef96f5beac8504d6b8bf157b1c38248425
Abdess76 said:
Good question, we can see this together on hangout.
Click to expand...
Click to collapse
Ok sounds good, although we'll have to find a time which works coz I'm on the other side of the world to you!
It is built by an unofficial maintainer named "moghn", they have been built rom based on Sjll's device tree since the end of 2021. And has successfully ported some sony features, such as creator mod, stock sony camera, sony sound, battery care, etc to their recent builds of Evolution X.
They have built Los 18.1, and Evolution X for android 12/12.1/13 and so on. However, since they didn't post on XDA, I would just mentioned such roms existed.
-----
Unlocked bootloader is MANDATORY
Download Link : here
Flash instruction : check README in the downloaded file
Credits to eswd04 on Telegram for CherishOS release.
He approved to share his release here on XDA.
Click to expand...
Click to collapse
Also credits to Sony Xperia 1 & 5 Indonesia tg group for being resourceful source.
Click to expand...
Click to collapse
Edit: Forgot to mention, do not use the Dolby that come with the ROM, it will result in crack sound in speakers, and turn that off fix the issue. You need to flash a Dolby Magisk Module to make it work.
The creator mode needed to be re-enable after each reboot.
Click to expand...
Click to collapse
If anyone found another ROM and want to share, you are very welcome.
I'll include the link later to the first post & maybe mirror it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then a list of their built roms.
However, once again, they didn't post on Xda, so I guess they have their own reason.
But i don't have account for Coolapk so no way to contact them.
And in fact there are also some MIUI or Flyme android 11 based rom made by others in the forum. Again, NOT gsi.
How to get his? lol. I just want the latest android on my xperia.
Just quick study some for their post. seems that they use the GSI image and Xperia 5 image with the binary image to flash Xperia 1.
And still some bug like camera not work, no alarm, cellular or SMS not work.
May I have direct links to this?
ryo2456 said:
Just quick study some for their post. seems that they use the GSI image and Xperia 5 image with the binary image to flash Xperia 1.
And still some bug like camera not work, no alarm, cellular or SMS not work.
Click to expand...
Click to collapse
Oh well, it is definitely not that case. It is NOT a GSI or any kind........as it is not based on the Sony binary. As I stated, it is a rom based on Sjll's device tree. It works perfectly fine. Camera works (although mine didn't work, due to hardware damage issue), the post they showed with stock Sony camera is a presentation of a sucessfully port. And unless you are using the Japeness Ver, there is no way the SMS service don't work (In my photo there is no any is because I didn't insert one). The only problem I have met is that the format of SD card is only support FAT32.
Unusual Man said:
May I have direct links to this?
Click to expand...
Click to collapse
Link to the Chinese cloud drive
Password: EvCT
Mind few things:
1. The link will expired if it meet the view capacity, which set by the drive service provider.
2. You need an account to download that, which requires a Chinese mainland phone number.
3. You might need an 'excellent' (I can't really know how to define that) network to download it. Because (1) if you didn't download it within a fixed time, the download will be cancelled. Possibly due to the a potential restrcition to non-China mainland IP. (2) In my case, the download speed is incredibly slow, so it is very likely you will encounter the first aforementioned situation.
4. It only supports Chinese language.
I personally recommended you reaches out the developer and get the link. But I can't share their profile link, because (1) Coolapk doesn't support that, (2) It is only accessible in the Coolapk APP. (3) The regesitration of Coolapk account also requires a phone number, with a quick check, it seems like it support non-China phone number.
If you want to try this way, then, after you download the Coolapk APP, just simply search their username 'moghn', and you can go to their profile page.
shahriyarali said:
How to get his? lol. I just want the latest android on my xperia.
Click to expand...
Click to collapse
Check #8
JaneValley said:
Oh well, it is definitely not that case. It is NOT a GSI or any kind........as it is not based on the Sony binary. As I stated, it is a rom based on Sjll's device tree. It works perfectly fine. Camera works (although mine didn't work, due to hardware damage issue), the post they showed with stock Sony camera is a presentation of a sucessfully port. And unless you are using the Japeness Ver, there is no way the SMS service don't work (In my photo there is no any is because I didn't insert one). The only problem I have met is that the format of SD card is only support FAT32.
Click to expand...
Click to collapse
I will try it later, exo seems like fully work.
ryo2456 said:
I will try it later, exo seems like fully work.
Click to expand...
Click to collapse
You have to flash the latest Sony stock firmware first, the rest of procedure is the same as the the rom with a payload bin file > https://forum.xda-developers.com/t/rom-unofficial-pixelos-for-xperia-5-android-12.4355093/ (just in case, the steps are the same for this one)
JaneValley said:
You have to flash the latest Sony stock firmware first, the rest of procedure is the same as the the rom with a payload bin file
Click to expand...
Click to collapse
thanks!
A12L rom is shared in the #1
@JaneValley ,
I just stumbled on this thread and it appears I'm too late to download the EvoX rom. Is there any chance you could upload it again for those of us who didn't notice? I really am tired of the stock rom. Please help if you can.
project_2501 said:
@JaneValley ,
I just stumbled on this thread and it appears I'm too late to download the EvoX rom. Is there any chance you could upload it again for those of us who didn't notice? I really am tired of the stock rom. Please help if you can.
Click to expand...
Click to collapse
I think you can try the GSI first.
project_2501 said:
@JaneValley ,
I just stumbled on this thread and it appears I'm too late to download the EvoX rom. Is there any chance you could upload it again for those of us who didn't notice? I really am tired of the stock rom. Please help if you can.
Click to expand...
Click to collapse
evolution_griffin-ota-sq3a.220705.003.a1-07101137-unofficial-unsigned.zip
1 file sent via WeTransfer, the simplest way to send your files around the world
we.tl
JaneValley said:
evolution_griffin-ota-sq3a.220705.003.a1-07101137-unofficial-unsigned.zip
1 file sent via WeTransfer, the simplest way to send your files around the world
we.tl
Click to expand...
Click to collapse
@JaneValley, do you have the most recent build? It appears the one you posted is from 07-05-22 or 05-07-22 and is not the same as the 09-09-22 build you have posted a thread about.
project_2501 said:
@JaneValley, do you have the most recent build? It appears the one you posted is from 07-05-22 or 05-07-22 and is not the same as the 09-09-22 build you have posted a thread about.
Click to expand...
Click to collapse
That is Android 13, and it is an initial build and has some system interface bugs
And yes this is not the latest A12L build, but second to last, GApps included.
It is a July build
The audio bug is occurred as I read some comment.
ryo2456 said:
The audio bug is occurred as I read some comment.
Click to expand...
Click to collapse
It is already added to the post