Related
Oppo X909 AOSP Beta by kAmMa
Warning
this is BETA version of AOSP port for Oppo X909. it may brick your device. don't flash it, if you don't know, what you are doing...
if you get into boot-loop after install, try to wipe cache and userdata
Prerequisites
custom recovery (i prefer/use TWRP)
How to install
download ROM (link bellow in updates section)
copy it to device
download Google Apps (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
copy it to device
restart device to recovery
make full backup
install both packages
(optional) install root package (https://mega.co.nz/#!aFAyTAoa!TNKZKnStX6v-cplQfDxA9xUOvX4MyO2SmQutTSPh5_M)
reboot device
profit
Updates
Code:
update - 17.04.2013
=============
beta version released
here is the link - https://mega.co.nz/#!nRggFYoJ!ewPABk-I2tUfHeldtkl4CgP6e1hK9L_eNrjRZYcBMlU
update - 16.04.2013
=============
nfc works
all sensors work
update - 11.04.2013 II.
=============
alpha version released
here is the link - https://mega.co.nz/#!SMRT0ABB!Q1yLikQGj42OqXwZZuQsBk8zePlXVsE34vsZhxJuRbk
update - 11.04.2013
=============
home button works
update - 10.04.2013 III.
=============
gps works
update - 10.04.2013 II.
=============
location services works
update - 10.04.2013
=============
phone works correctly (phone calls are played via Earpiece, microphone works)
its possible to use the phone almost on daily basis => alpha release soon... :)
update - 09.04.2013 II.
=============
wifi works
update - 09.04.2013 I.
=============
bluetooth works
update - 27.03.2013
=============
front camera works
rear camera works
main speaker works
Kernel source : https://github.com/kamma-cz/Oppo-Find5-Kernel-Source
------
Works perfect!!
mobile networks config crashes when I try to config my APN settings
Nice job. ty
Sweet.
awesome! will test this one tomorrow!
I already bought you a pivo, so (please) keep developing this
kamma said:
------
Click to expand...
Click to collapse
thanks your rom,but Battery is not durable，wait fix，and wait jb4.2 :laugh:
... so smooth ...
still setting up everything, but the menus feel so incredibly smooth...
not tried anything else, except wifi works like it should
Nice to see you here Kamma, I used to use your stuff on my 3VO.
Thanks for the port, I'm looking at buying one of these phones if a good AOSP based rom is out for it. When you say it could brick the phone, is there any reason this particular operation is more dangerous than flashing any custom rom on any device or are you just giving a standard warning. This port could also be used as a base for CM10? I
Another Great Rom Thanks!
Seems (so far) to be fully usable - i've used RC Roms more buggy then this!
good job...:laugh:
Definately usable as a 'everyday rom' great work on this.
2 Requests
No NFC support?
Any Chance of adding BLN to the kernel?
n1ck75 said:
Definately usable as a 'everyday rom' great work on this.
2 Requests
No NFC support?
Any Chance of adding BLN to the kernel?
Click to expand...
Click to collapse
Why the heck would you want BLN on a device that has a real notification LED???
Haha,good question.
Allanitomwesh said:
Haha,good question.
Click to expand...
Click to collapse
Everything works for the most part but I too have requests.
NFC to work (Will it be possible to hack the software for the Find 5 to support google wallet?)
Video playback fix
Sheer optimization
osmosizzz said:
Everything works for the most part but I too have requests.
NFC to work (Will it be possible to hack the software for the Find 5 to support google wallet?)
Video playback fix
Sheer optimization
Click to expand...
Click to collapse
GW depends on if Oppo included a secure element with Google's keys or not.
LOTS of manufacturers include this even if their device isn't supported by GW, however occasionally devices show up without an SE. (Last ones I saw were Samsung I9100P and I777.)
Quite simple because the led is tiny. BLN looks good and works well, That was just a request.
However since the phone supports it i would love NFC on this ROM
Entropy512 said:
GW depends on if Oppo included a secure element with Google's keys or not.
LOTS of manufacturers include this even if their device isn't supported by GW, however occasionally devices show up without an SE. (Last ones I saw were Samsung I9100P and I777.)
Click to expand...
Click to collapse
Sucks. Hope they did include it
Sent from my Oppo Find 5
I prepared everything to move over to this rom...
backup up my apps, messages, everything...
now I try to (re)download the rom... get this :
Temporarily unavailable
x909-aosp-alpha1.kamma.zip (144.7 MB)
anybody have the ability to host the .zip elsewhere?
kind regards,
s0h0
s0h0punk said:
I prepared everything to move over to this rom...
backup up my apps, messages, everything...
now I try to (re)download the rom... get this :
Temporarily unavailable
x909-aosp-alpha1.kamma.zip (144.7 MB)
anybody have the ability to host the .zip elsewhere?
kind regards,
s0h0
Click to expand...
Click to collapse
I'm getting the same thing. I tried moving over too but can't download the ROM
Sent from my Oppo Find 5
Firmware update WLAN / BT
FW for 32.3.A.0.372/376/378 and 32.3.A.2.33
WLAN: 7.45.59.15 (This firmware WLAN installed in 32.4.A.0.160)
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com
--------------------------------------------------
FW for 32.3.A.0.372/376/378, 32.3.A.2.33, 32.4.A.0.160
WLAN: 7.45.59.16 (This firmware WLAN installed in 32.4.A.1.54)
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com
WLAN: 7.45.59.17
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com
WLAN: 7.45.59.18
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com
To install use TWRP 3.1.1. About changes to don't ask, don't know.
BT is still having issues I think. I've gotten side tracked with my device tree, and been looking at the broadcom c++,
I think googles framework and bt app need fixing
@NeoBeum ,
On stock firmware everything is OK, the BT connection is stable.
Firmware update WLAN and BT for Nougat 7.1.1
Firmware update WLAN / BT
for FW 32.4.A.0.160
WLAN: 7.45.59.16
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com
grayleshy said:
Firmware update WLAN / BT
for FW 32.4.A.0.160
WLAN: 7.45.59.16 (Sony will add this driver in the next firmware.)
BT: cfg121-0121 (BT 4.2)
Click to expand...
Click to collapse
it's got some changes to how the Qualcomm stack, RFCOMM, talk to the Broadcom stuff for SDIO..
I asked about some other stuff on GitHub, but no one's replied yet.
at the moment I can see some conflicts with 'bt.name=Android', the dynamic naming to 'Xperia {Device Model}', and the name users can change in the bluetooth settings
NeoBeum said:
at the moment I can see some conflicts with 'bt.name=Android', the dynamic naming to 'Xperia {Device Model}', and the name users can change in the bluetooth settings
Click to expand...
Click to collapse
You have this conflict on stock FW cfg121-0121 BT 4.1?
The difference between the drivers is minimal and the main part is not affected.
BCM4345C0 Sony Kitakami R21 UART 37.4 MHz BT 4.1 cfg121-0121
BCM4345C0 Sony Loire UART 37.4 MHz BT 4.2 cfg121-0121
its not really firmware related - but software - so the problem exists for almost every release - because either one of them wants to supercede or be in charge...
this is what i was trying to find out... who has final control.. there's 4 vendors involved... qcom, broadcom, sony, google... 5 if you include the user
i was just going through the kitakami bluetooth stuff - you'll probably see my post in github if you have a look
edit: the firmware itself looks solid (apart from the bit where i mentioned the dynamic naming - because there's the override/or not override with build.prop) - it's the google framework added on top of it - that is leading to my suspicions
just go have a look at the system/bt at googlesource - and you might see what i'm having doubts about
NeoBeum said:
its not really firmware related - but software - so the problem exists for almost every release - because either one of them wants to supercede or be in charge...
this is what i was trying to find out... who has final control.. there's 4 vendors involved... qcom, broadcom, sony, google... 5 if you include the user
i was just going through the kitakami bluetooth stuff - you'll probably see my post in github if you have a look
edit: the firmware itself looks solid (apart from the bit where i mentioned the dynamic naming - because there's the override/or not override with build.prop) - it's the google framework added on top of it - that is leading to my suspicions
just go have a look at the system/bt at googlesource - and you might see what i'm having doubts about
Click to expand...
Click to collapse
Post read, I will say a few words about the boot:
- kernel and ramdisk (initialization scripts)
- system/build.prop (medium priority)
- other scripts with higher priority, programs and drivers
In general, it is tedious, but the problem is most likely in the stack between broadcom and google.
To search for the culprit will have to study the source code...
I blame google then, i'll go looking at the system/bt git first
grayleshy said:
...
Click to expand...
Click to collapse
I just realised you're the safeincloud Dev after I got a github mail...
That's my main and only pw/manager... and I recommended it to friends and also made my mum buy it because I was getting tired of unlocking her accounts when she gets locked out of things... hahha
Firmware update WLAN / BT for Nougat
WLAN: 7.45.59.17
BT: cfg121-0121 (BT 4.2)
Hey, quick question:
Should I stick with the firmware that came with my Rom or should I update to the latest version even if it's a different android version? I'm using Marshmallow and wonder if the Nougat update would do anything.
Cerhio said:
Hey, quick question:
Should I stick with the firmware that came with my Rom or should I update to the latest version even if it's a different android version? I'm using Marshmallow and wonder if the Nougat update would do anything.
Click to expand...
Click to collapse
This question is inappropriate in this topic, ask here. https://forum.xda-developers.com/z5-compact/general/ftf-android-7-1-1-xperia-z5c-e5823-32-4-t3628734
Firmware update WLAN / BT for Nougat
WLAN: 7.45.59.18 (r718509)
BT: cfg121-0121 (BT 4.2)
Hi man i changed update script but dont work Z5 premium
ouzqan said:
Hi man i changed update script but dont work Z5 premium
Click to expand...
Click to collapse
FW only for Z5c!
The Z5/Z5P has other Wi-Fi/BT modules.
GreyLeshy said:
FW only for Z5c!
The Z5/Z5P has other Wi-Fi/BT modules.
Click to expand...
Click to collapse
Where to find one for z5 premium?
ouzqan said:
Where to find one for z5 premium?
Click to expand...
Click to collapse
FW for Z5/Z5P. Wlan BCM4356.
FW ver. 7.43.184.20 (r718507) for driver 1.71.26.
GreyLeshy said:
FW for Z5/Z5P. Wlan BCM4356.
FW ver. 7.43.184.20 (r718507) for driver 1.71.26.
Click to expand...
Click to collapse
I Will try. This file Last Update,?
ouzqan said:
I Will try. This file Last Update,?
Click to expand...
Click to collapse
Yes, the latest available FW (2017-08-31).
Currently on hold due to working on Nougat first.
I've got a booting or should I say bootlooping build of Lineage 15.0 for I9000. (galaxysmtd)
I've had to use crazy hacks like adb binary from 7.1 in ramdisk.
Just to get `adb logcat` working.
For now it's stuck at bootlogo. I've attached the logcat here.
I'm looking into it to figure out what needs to be done.
Sources:
manifests and patches I've used.
https://github.com/galaxys1-resurrected/local_manifests
https://github.com/galaxys1-resurrected/android_patches
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
Device Tree:
https://github.com/galaxys1-resurrected/android_device_samsung_aries-common
https://github.com/galaxys1-resurrected/android_device_samsung_galaxysmtd
Thanks:
@rINanDO for backporting kernel side of things to 3.0
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1
And all others who had worked from beginning till now on this device.
Is there anyone still working on this?
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
a1shakes said:
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
Click to expand...
Click to collapse
Unfortunately, no one is really actively working on Oreo. As you've found out, it's an issue with the graphics drivers that is holding everything back. No device (that I've found) that uses a PowerVR graphics chip (we use the PowerVR SGX 540) has working graphics drivers on Oreo. There were rumours that someone had found newer working blobs, but weren't able to release them publicly due to intellectual property laws that they were trying to figure out (but this was months ago).
Our GPU does support sufficient enough OpenGL, but only using BGRA8888 as opposed to RGBA8888. BGRA hasn't officially been supported in Android since ~4.2, but there's been a hack used to make things work. Come Oreo, things have changed and the hack no longer applies cleanly. However, I think the really issue is that the gralloc blobs was extended by PowerVR (see https://github.com/xc-racer99/andro...6.0/exynos3/s5pc110/include/hal_public.h#L119) but with the binderized HALs/VNDK/other low-level Oreo changes something has broken. I had a go at trying to work around things, but failed too.
There are a few ways I can think of getting working graphics:
1) Someone finds some updated blobs for the PowerVR SGX 540 for ARM (I've found x86 ones, but they don't work for obvious reasons)
2) Someone hacks around the source code so that the blobs work - but I'm not sure if it's PowerVR "extension" of the gralloc interface that is causing issues or not...
3) We simply use software rendering, but this would be so slow with our ancient CPU that I haven't bothered to try
4) We work on porting a newer kernel so we have the Samsung DRM kernel driver, use the Linux PowerVR blobs coupled with drm_gralloc/drm_hwcomposer and maybe a wrapper like https://github.com/TexasInstruments/dri3wsegl and somehow cobble together working support
In terms of the mediaextractor crash, that's due to the kernel missing seccomp support. There's a whole bunch of different backports, some more successful than others. Due to our ancient kernel, backporting is no longer very easy...
If we could somehow get the graphics drivers working, we'd have a pretty good base as there are free implementations of all HALs/drivers except for GPS and TV-Out (and, of course, graphics....).
Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?
nailyk said:
Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?
Click to expand...
Click to collapse
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
xc-racer99 said:
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
Click to expand...
Click to collapse
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.
nailyk said:
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.
Click to expand...
Click to collapse
If you're serious about trying to mess with graphics drivers, it might be interesting to check out the blobs from https://www.renesas.com/pt-br/produ...ion-boards/renesas-starter-kit-for-rzg1e.html as it's an ARM-based device with the SGX540. It's possible that they're new enough to not run into the same issues as the older blobs (but equally possible that even the kernel part is closed source). The binary blobs are only semi-SoC specific as I've managed to use the OMAP blobs with only having hardware decoding being broken.
Is it for real???
I9000 !!
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490
Use android go it will be better.
MYEUHD said:
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490
Click to expand...
Click to collapse
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time
xc-racer99 said:
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time
Click to expand...
Click to collapse
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
xc-racer99 said:
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
Click to expand...
Click to collapse
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
ChronoMonochrome said:
In 9.0, to get graphics to work, device is required to support HWC2 (or use either HWC2on1 or HWC2onFb adapters).
Click to expand...
Click to collapse
ChronoMonochrome said:
Yes, HWC has to be at least 1.3, to work with one of aforementioned adapters. With one of those adapters it will work like it was HWC 2 (but actually not exactly same).
Click to expand...
Click to collapse
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung
MYEUHD said:
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung
Click to expand...
Click to collapse
Was unaware of the fact. Are you volunteering to make the patches?
I've uploaded my changes to https://github.com/xc-racer99/proprietary_vendor_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_hardware_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_kernel_samsung_aries/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_aries-common/tree/ddk-1.14 but I think this might be the last I work on this as I don't really have the motivation to work on it anymore. Note the patches are against a custom version of Unlegacy Android 4.4 so you'll need to cherry pick the changes to your ROM of choice if desired.
The changes build, the EGL appears to initialize, but I always get
Code:
E/libEGL ( 471): validate_display:254 error 3008 (EGL_BAD_DISPLAY)
And in dmesg:
Code:
[ 8.509291] init: computing context for service '/system/vendor/bin/pvrsrvinit'
[ 8.509601] init: starting 'pvrsrvinit'
...
[ 8.601890] PVR_K: UM DDK-(4081762) and KM DDK-(4081762) match. [ OK ]
...
[ 8.765955] init: process 'pvrsrvinit', pid 99 exited
...
[ 55.560021] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.563491] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.597577] s3cfb s3cfb: [fb0] video memory released
Whether the issue is in the HWC or the gralloc blob that we've stolen from OMAP, I have no idea.
xc-racer99 said:
Was unaware of the fact. Are you volunteering to make the patches?
Click to expand...
Click to collapse
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
MYEUHD said:
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
Click to expand...
Click to collapse
You really do need jdk-7... I used the "reference implementation" available at http://jdk.java.net/java-se-ri/7 and made sure the java executables were in the PATH before the java I actually have installed.
Note that my Unlegacy Android trees will not work for the i9000 (well, they might, but you'd need to install u-boot as well at a bare minimum...)
It's kinda Insane that people are trying to get an 8 year phone to run oreo
@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?
MYEUHD said:
@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?
Click to expand...
Click to collapse
I've got the .repo folder, but don't have the individual files expanded as I don't have the disk space Could run a repo sync and look at things but don't have the disk space for a full build.
The_Pacific_gamer said:
It's kinda Insane that people are trying to get an 8 year phone to run oreo
Click to expand...
Click to collapse
its kinda insane that people are still using this phone.
Hello,
Since i've moved to Lineage 16, i lost the Radio FM application using the FM chipset (no data used)
I'm not able to find something on the Play Store, any idea ?
Model:SM-A320FL
Thanks
I have with LinageOS 17 still the same issue, no FM Radio.
I was trying to extract the HybridRadio application and its belonging libraries from this ROM [ROM][A320X] H-ROM A7 PORT V6.0 [10.0][OneUI 2.0][64 bits][Treble] but without success to get it working.
I installed following files in the "/system" path:
Code:
/---system
+---etc
| /---permissions
| privapp-permissions-com.sec.android.app.fm.xml
+---lib
| libfmradio_jni.so
|
+---lib64
| libfmradio_jni.so
|
/---priv-app
/---HybridRadio
HybridRadio.apk
After rebooting, the FM Radio App was available but did directly crash when opening.
I have looked into the system logs with logcat and found out that HybridRadio has an unresolved reference in "/system/framework/framework.jar" to some Samsung specific settings classes that are not available in the "framework.jar" of LinageOS.
At this point I have to give up because I don't know how to extract the needed classes out of the H-ROM "framework.jar" and furthermore I then still don't know if these classes have further references that I also can't resolve.
I think the easiest way to solve this problem is to decompile the "HybridRadio.apk" application and remove the references to the H-ROM "framework.jar". But also here I don't have any experience.
Maybe someone else got the FM Radio working or has the knowlegde how to solve the port of the FM Radio application from the H-ROM?
I could provide the files mentioned above if that helps.
First your kernel must support FM radio drivers!
Then you can build same this project:
GitHub - mikereidis/spirit2_free: Spirit2 Free : Open Source Real FM Radio for Android 4.1-5.0+
Spirit2 Free : Open Source Real FM Radio for Android 4.1-5.0+ - GitHub - mikereidis/spirit2_free: Spirit2 Free : Open Source Real FM Radio for Android 4.1-5.0+
github.com
or other "spirit FM" radios
My understanding is that "Spirit FM" supports mostly only Qualcomm chipsets. The A3 2017 has an Exynos chip with integrated FM support. So I think "Spirit FM" application will never work with the A3. "Spirit FM" is also not supported anymore for newer devicces.
I hoped that the extracted "libfmradio_jni.so" was the kernel library and that HybridRadio has everthing available to work.
So the queston is what else has to be extracted from the H-ROM to get the FM Radio working.
iamchriscool said:
My understanding is that "Spirit FM" supports mostly only Qualcomm chipsets. The A3 2017 has an Exynos chip with integrated FM support. So I think "Spirit FM" application will never work with the A3. "Spirit FM" is also not supported anymore for newer devicces.
I hoped that the extracted "libfmradio_jni.so" was the kernel library and that HybridRadio has everthing available to work.
So the queston is what else has to be extracted from the H-ROM to get the FM Radio working.
Click to expand...
Click to collapse
May be Astrako have other information to relate fm radio drivers, ask him!
A1/GT08/DZ09 --Universal Firmware--
About this firmware:
-This firmware is for A1/GT08/DZ09 and experimentally for the U8/GT09 Series Smartwatch (thanks to Andrej Kopac for experimental smartwatch support)
-Based on Carneo U10 (A1) Firmware (with tweaks to work on more smartwatches).
Features: Phone, SMS, Notifications, Speaker, Custom wallpapers, Bootscreens, File manager, Photo viewer, mp3 player and more.
What works?
A1:
-Bluetooth
-Button
-Touch
-Calling
-SMS
-File manager (SDcard)
-Camera (first gen only)
-Settings
-Speaker
GT08:
-Touch
-Bluetooth
-Button (Only some)
-Calling
-SMS
-Camera (first gen only)
-Speaker
-Settings
DZ09:
-Touch
-Camera (only some)
-Speaker
-Bluetooth (only some)
What doesnt work?
A1:
-Camera on second gen
GT08:
-Button on some
-Camera on Second gen
DZ09:
-Button
-Camera on most of them
-Bluetooth
-File manager
-Screen doesnt work properly for now
How to flash?
1. Backup original Firmware in case you dont like this one or something goes wrong!
2. Dowload ROM.
3. Extract it.
4. Flash it using Mediatek Flashtool (Remove battery and plug in USB).
On what CPU's this work?
-MTK6261, 6261A, 6261MA, 6260, 6260A, 6260MA, 6261D (experimental)
Credits: Andys4c, Mediatek Smartwatch ROM EXTRACTOR Team, Andrej Kopac (for the source)
ALL FIRMWARES HAVE BEEN TESTED. IM NOT RESPONSIBLE FOR BRICKED DEVICES. DONT BLAME ME IF SOMETHING DOESNT WORKS SO DONT PM ME WITH THINGS LIKE "SUR THE KAMERA DONT WORK" Just explain the problem to me and i will fix it.
Changelog (changes from my old thread):
-Firmware is universal now
-Fixed display bug on A1
Bluetooth Fixed for the most part
Changed to 2016 source (its more stable on 2016 then on 2017 and 2019 sources)
Experimental GT09 Support by Andrej Kopac
Notice: Because of the older source the QR Code to download the app isnt working so use FUNRUN app to pair. This is technically a port so the name of the device will always be CARNEO or CARNEO U10. Im not allowed to publish the original source code so PM Andrej Kopac for it (he will provide it to anyone). GT09 IS SUPPORTED BUT UNTESTED SO TRY IT AT YOUR OWN RISK!!
Download:
Mirror 1: https://mega.nz/file/S85yTALB#JONRCs6i7asv1HbcYpRePvSjEPLwV9pT8QwMiDlt0d8
Mirror 2: https://ulozto.net/file/bao6mzgfml28/universal-smartwatch-fimware-zip
If you like my work dont forget to smash the THANKS button
Andys4c said:
A1/GT08/DZ09 --Universal Firmware--
About this firmware:
-This firmware is for A1/GT08/DZ09 and experimentally for the U8/GT09 Series Smartwatch (thanks to Andrej Kopac for experimental smartwatch support)
-Based on Carneo U10 (A1) Firmware (with tweaks to work on more smartwatches).
Features: Phone, SMS, Notifications, Speaker, Custom wallpapers, Bootscreens, File manager, Photo viewer, mp3 player and more.
What works?
A1:
-Bluetooth
-Button
-Touch
-Calling
-SMS
-File manager (SDcard)
-Camera (first gen only)
-Settings
-Speaker
GT08:
-Touch
-Bluetooth
-Button (Only some)
-Calling
-SMS
-Camera (first gen only)
-Speaker
-Settings
DZ09:
-Touch
-Camera (only some)
-Speaker
-Bluetooth (only some)
What doesnt work?
A1:
-Camera on second gen
GT08:
-Button on some
-Camera on Second gen
DZ09:
-Button
-Camera on most of them
-Bluetooth
-File manager
-Screen doesnt work properly for now
How to flash?
1. Backup original Firmware in case you dont like this one or something goes wrong!
2. Dowload ROM.
3. Extract it.
4. Flash it using Mediatek Flashtool (Remove battery and plug in USB).
On what CPU's this work?
-MTK6261, 6261A, 6261MA, 6260, 6260A, 6260MA, 6261D (experimental)
Credits: Andys4c, Mediatek Smartwatch ROM EXTRACTOR Team, Andrej Kopac (for the source)
[/COLOR] ALL FIRMWARES HAVE BEEN TESTED. IM NOT RESPONSIBLE FOR BRICKED DEVICES. DONT BLAME ME IF SOMETHING DOESNT WORKS SO DONT PM ME WITH THINGS LIKE "SUR THE KAMERA DONT WORK" Just explain the problem to me and i will fix it.
Changelog (changes from my old thread):
-Firmware is universal now
-Fixed display bug on A1
Bluetooth Fixed for the most part
Changed to 2016 source (its more stable on 2016 then on 2017 and 2019 sources)
Experimental GT09 Support by Andrej Kopac
Notice: Because of the older source the QR Code to download the app isnt working so use FUNRUN app to pair. This is technically a port so the name of the device will always be CARNEO or CARNEO U10. Im not allowed to publish the original source code so PM Andrej Kopac for it (he will provide it to anyone). GT09 IS SUPPORTED BUT UNTESTED SO TRY IT AT YOUR OWN RISK!!
Download:
Mirror 1: https://mega.nz/file/S85yTALB#JONRCs6i7asv1HbcYpRePvSjEPLwV9pT8QwMiDlt0d8
Mirror 2: https://ulozto.net/file/bao6mzgfml28/universal-smartwatch-fimware-zip
If you like my work dont forget to smash the THANKS button
Click to expand...
Click to collapse
Well done!!!!
How did you do these source code changes?
Is this firmware build from source code and the changes are done in source code?
Thanks for reply
OXA
Response
Its based on source code by Andrej Kopac with some changes made by me (to work on more watches).
Update coming soon
Changelog:
Fixed camera on some A1 GEN 2.
Upstreamed to a bit newer source.
Added proper slovak and czech language.
Dropped GT09 support.
Dropped Andrej Kopac experimental support.
Universal version upstreamed to: 1.0.2 Codename: ReloadedPlus
And much more...
hola!!existe mas eoms para el gt08 mtk 6261
darakkyar said:
hola!!existe mas eoms para el gt08 mtk 6261
Click to expand...
Click to collapse
sorry, i cant understand, please reply in english:laugh:
Andys4c said:
sorry, i cant understand, please reply in english:laugh:
Click to expand...
Click to collapse
Hello andy, I have a smarwatch gt08 with cpu 6261, I am looking for roms for him since his interface I do not like and I have not found anything, I followed the steps of your publication and I cannot connect my smart with the cable because it disconnects every while, not counting that I can't get sp flash to recognize the rom you published. I'm a total novice in that, I made a change from rom to my samsung s3 years ago I remember passing it from 4.0 to 7.0 XD. I think at that time It was the lineage that installed my cell phone, so I was encouraged to try my smartwacht
darakkyar said:
Hello andy, I have a smarwatch gt08 with cpu 6261, I am looking for roms for him since his interface I do not like and I have not found anything, I followed the steps of your publication and I cannot connect my smart with the cable because it disconnects every while, not counting that I can't get sp flash to recognize the rom you published. I'm a total novice in that, I made a change from rom to my samsung s3 years ago I remember passing it from 4.0 to 7.0 XD. I think at that time It was the lineage that installed my cell phone, so I was encouraged to try my smartwacht
Click to expand...
Click to collapse
If it cant recognize the watch, remove the battery. If you have problem with the ROM extract it using Mediatek Rom extractor But in most cases you just extract the zip and select the bootloader file
Hi andy
I'm not sure if I'm doing this wrong or if this is incompatible with the watch I got, I'm getting this message
Can't use your scatter file for read back, the only way I was able to dump the stock rom is with miracle tool, here's the scatter file I got from that, not sure if it provides any useful info
cpu is 6260
Nebrassy said:
Hi andy
I'm not sure if I'm doing this wrong or if this is incompatible with the watch I got, I'm getting this message
Can't use your scatter file for read back, the only way I was able to dump the stock rom is with miracle tool, here's the scatter file I got from that, not sure if it provides any useful info
cpu is 6260
Click to expand...
Click to collapse
what kind of watch do you have? Or try older version.
Andys4c said:
what kind of watch do you have? Or try older version.
Click to expand...
Click to collapse
Box only said fopo smart watch, only indication of gt-08 is default Bluetooth name
Andys4c said:
Its based on source code by Andrej Kopac with some changes made by me (to work on more watches).
Click to expand...
Click to collapse
I have an a1 smartwatch with mt6260 cpu, In that couldn't send of receive files through Bluetooth , couldn't change wallpaper &power on off displays and also some codes are not working.
Will this firmware solve my problems??
Anon_y_mous said:
I have an a1 smartwatch with mt6260 cpu, In that couldn't send of receive files through Bluetooth , couldn't change wallpaper &power on off displays and also some codes are not working.
Will this firmware solve my problems??
Click to expand...
Click to collapse
yep
Hello,
How does one go about accessing the source for the A1 smartwatch?
Thanks in advance,
Aj