Related
If you wish to request omni forks a repository from AOSP, in order to implement a patch into omni, please post this request here. Eventually this will be carried out via jira (http://jira.omnirom.org)
When posting, please give the path to the repository, and a link to what you want to merge, or a description.
For example if you wish to cherry pick a patch into it, a link to the patch and brief description of the reason for the patch.
We'll then have that repository forked and made available on github and gerrit, permitting you to submit your change.
Before you request, please check on github to ensure it isn't already forked!
For example :
frameworks/base - Needing forked so I can introduce multi window functionality (link here to information)
hardware/broadcom/libbt - Mainly for board-specific configurations (link), but newer CM commits also look promising.
If new device bringups aren't planned yet, ignore the followings:
device/lge/p880 and kernel/lge/p880 - Device bringup (kernel has a non-standard naming at CM repo, it should be android_kernel_lge_x3 (x3 is the board name))
vendor/lge (maybe Omni should create one from scratch)
Adam77Root said:
hardware/broadcom/libbt - Mainly for board-specific configurations (link), but newer CM commits also look promising.
If new device bringups aren't planned yet, ignore the followings:
device/lge/p880 and kernel/lge/p880 - Device bringup (kernel has a non-standard naming at CM repo, it should be android_kernel_lge_x3 (x3 is the board name))
vendor/lge (maybe Omni should create one from scratch)
Click to expand...
Click to collapse
We do have a vendor/lge with just mako, although I'm not sure if its current location.
Vendor blob repos are a legal mess, which is why CM kept them at TheMuppets. We'll likely do something similar if we haven't already (I haven't synced since coming home.) Among other reasons to keep them separate is in the case of a DMCA takedown - usually that happens only to a single repo (see the HTC vendor repos earlier this year) but there's always the risk that damage might be more widespread.
android_external_clang
http://review.cyanogenmod.org/#/c/29799/2
Needed for building my msm8960 device (Motorola Photon Q, xt897c).
arrrghhh said:
android_external_clang
http://review.cyanogenmod.org/#/c/29799/2
Needed for building my msm8960 device (Motorola Photon Q, xt897c).
Click to expand...
Click to collapse
CM bootable recovery and some commits over system core
Black_Prince said:
CM bootable recovery and some commits over system core
Click to expand...
Click to collapse
No for CWM - We're working on forking TWRP in, but some fixes still need to be made to allow it to work on devices with unified recovery/boot image. (Probably one of the biggest holdups for the exynos 4210 family - Sonys with unified boot/recovery can at least use Dees_Troy's FOTAKernel trick).
Getting CWM to build in a tree requires hacks all over the tree in multiple repositories. TWRP is much more self-contained, but needs some tweaks to the build system in order to get it to build properly on a userdebug (as opposed to eng) build.
Entropy512 said:
No for CWM - We're working on forking TWRP in, but some fixes still need to be made to allow it to work on devices with unified recovery/boot image. (Probably one of the biggest holdups for the exynos 4210 family - Sonys with unified boot/recovery can at least use Dees_Troy's FOTAKernel trick).
Getting CWM to build in a tree requires hacks all over the tree in multiple repositories. TWRP is much more self-contained, but needs some tweaks to the build system in order to get it to build properly on a userdebug (as opposed to eng) build.
Click to expand...
Click to collapse
Hmm but until the twrp is ported should i test build for some galaxy devices like SG S2 note 1 with cwm ?
It will make me to push changes to git in device tree ... and will be easy to add support
Black_Prince said:
Hmm but until the twrp is ported should i test build for some galaxy devices like SG S2 note 1 with cwm ?
It will make me to push changes to git in device tree ... and will be easy to add support
Click to expand...
Click to collapse
I'll pull up a remote to use for bootable/recovery until we fork (unless plodey already forked it) from TWRP, won't be able to provide it until tonight.
However, right now, it will only build a working recovery if you do an eng build instead of userdebug. If Dees_Troy's talk at BABBQ is ever posted, that's what I was talking about when I trolled him at the end.
Something like:
Code:
. build/envsetup.sh && brunch custom_n7000-eng
or something like that.
Old
def WriteRawImage(self, mount_point, fn):
"""Write the given package file into the partition for the given
mount point."""
fstab = self.info["fstab"]
if fstab:
p = fstab[mount_point]
partition_type = common.PARTITION_TYPES[p.fs_type]
args = {'device': p.device, 'fn': fn}
if partition_type == "MTD":
self.script.append(
'write_raw_image(package_extract_file("%(fn)s"), "%(device)s");'
% args)
elif partition_type == "EMMC":
self.script.append(
'package_extract_file("%(fn)s", "%(device)s");' % args)
Requested
def WriteRawImage(self, mount_point, fn):
"""Write the given package file into the partition for the given
mount point."""
fstab = self.info["fstab"]
if fstab:
p = fstab[mount_point]
partition_type = common.PARTITION_TYPES[p.fs_type]
args = {'device': p.device, 'fn': fn}
if partition_type == "MTD":
self.script.append(
'package_extract_file("%(fn)s", "/tmp/boot.img");'
'write_raw_image("/tmp/boot.img", "%(device)s");' % args
% args)
elif partition_type == "EMMC":
self.script.append(
'package_extract_file("%(fn)s", "%(device)s");' % args)
elif partition_type == "BML":
self.script.append(
('assert(package_extract_file("%(fn)s", "/tmp/%(device)s.img"),\n'
' write_raw_image("/tmp/%(device)s.img", "%(device)s"),\n'
' delete("/tmp/%(device)s.img"));') % args)
else:
raise ValueError("don't know how to write \"%s\" partitions" % (p.fs_type,))
Flash error in write raw image ...
Also can u cherry pick these commits https://github.com/CyanogenMod/android_system_core/commits/cm-10.2/mkbootimg/unpackbootimg.c
My internal SD card isnt got recognsied , there must be some commits missing in vold ...
I dont even know it got formatted or what in flashing ...
All things working WIFI BLUTOOTH TETHERING CALL DATA MSG MMS OMNITORCH
Also u may have look over https://github.com/CyanogenMod/andr...mmit/f22626cdbecfe27c96f205710173458eab14e1a1
and https://github.com/CyanogenMod/andr...mmit/aee5f78ddec238cec016849acaf1d3007b8b1507
https://android.googlesource.com/platform/hardware/broadcom/libbt
Must haz patch:
https://github.com/CyanogenMod/andr...mmit/4028192a4fe8289bf9b7fb202a2bb2c0d85d98c3
//edit: xplod sorted it out already.
android_packages_apps_PackageInstaller
For
HALO and a feat which enables us to see version of the installed and gonna install app
I need this to make it work with my Samsung galaxy s4
I'm not sure if this is the correct thread, but the following two would be great for i9305 support
smdk4412-qcom-common -> needed for i9305 and t0lte (EDIT: I see this one has now been added)
Thanks!
Hey @pulser_g2,
wondering if i could have the following repositories added in for jf devices,
all features are fully functional with these repositories : branch: cm-10.2 for all
device_samsung_jf-common
android_device_samsung_jflteatt
android_kernel_samsung_jf
CyanogenMod/android_hardware_samsung
CyanogenMod/android_device_samsung_msm8960-common
CyanogenMod/android_device_samsung_qcom-common
@pulser_g2
I just talked to @maxwen and he told me i should post here the needed stuff:
I managed to fix the radio issues today on m7, but i need additionally these commits:
https://github.com/TheMuppets/proprietary_vendor_htc/commit/7bbbe83823525090e7d94c47b439c09a254b380f
https://github.com/TheMuppets/proprietary_vendor_htc/commit/19ed957678d13b489da78d704b27811030688078
https://github.com/TheMuppets/proprietary_vendor_htc/commit/51b006bc8f05757c7dd82361ce6d985e996af360
and please DO NOT merge this: https://github.com/TheMuppets/proprietary_vendor_htc/commit/2b86687a460030199fa42d49207957ce285c1a53
as its not needed and breaks build (I allready have everything in m7-common so no need for vendor)
Thanks in advance
@pulser_g2
we dont need to update anything, please forget my post above, i managed to get it working without all these commits and the right vendor
hardware/qcom/gps - Needing forked so I can build the needed GPS module into my Omnirom build.
The link to this repository is: https://github.com/CyanogenMod/android_hardware_qcom_gps/tree/cm-10.2
I hope it gets included, this saves me a ton of time pulling stuff from other repositories.
Greetings PsychoGame
Galaxy S I9000 (galaxysmtd)
@pulser_g2 Device repos are already forked. Kernel is missing: https://github.com/OmniGalaxyS/android_kernel_samsung_aries
It has android-4.3 and android-4.4 branches up.
Device rocking with Omni!
See you!
Fail
PsychoGame said:
hardware/qcom/gps - Needing forked so I can build the needed GPS module into my Omnirom build.
The link to this repository is: https://github.com/CyanogenMod/android_hardware_qcom_gps/tree/cm-10.2
I hope it gets included, this saves me a ton of time pulling stuff from other repositories.
Greetings PsychoGame
Click to expand...
Click to collapse
I also need android_hardware_qcom_gps (probably best from https://github.com/markcs/android_hardware_qcom_gps/tree/cm-11.0)
We now have a booting CM11 based on 4.4.2 on Galaxy R
Things working (I have checked only these)
Wifi
Audio ( played a youtube video in browser)
2G/3G data
BT scan and pair
ADB
Calls:
Screen goes black at times during call
Call audio is only on speakers
Could not end a call.
Storage:
Both internal EMMC and external SD cards are NOT getting mounted.
So could not play any music or gallery or screenshot doesnt get saved
Camera app is hidden.Could not check
First boot time is pretty long. Subsequent first reboot takes some time to pass the GALAXY R logo.
Link
http://www.mediafire.com/download/sg2ychsh86d772z/cm-11-20131217-UNOFFICIAL-i9103.zip
Just an initial build for testing and demo purpose and please ensure to have a backup .
Sources and credits:
*Device tree : Grarak's cm11 tree ( https://github.com/Grarak/android_device_samsung_i9103/)
*Kernel : Grarak's 4.4 (https://github.com/Grarak/grakernel-n1)
*CM11 sources
*Frameworks/native branch changes merged as TonyP had pointed ( https://github.com/p990-dev/android_frameworks_native/tree/cm-11.0-dev)
*Recovery updater hack (http://forum.xda-developers.com/showpost.php?p=47692333&postcount=15&nocache=1&z=1484923475146786)
Other Devs Who had given us a working device tree historically . Esp Adam, karthik for their patience to answer my newbie questions .
That lib isn't updated for 11 yet. IIRC it's already merged in Omni or it's on Gerrit. You might check that out.
Sent from my OmniROM-powered LG Optimus 4X HD
Thanks for the response Adam. I shall try the Omni RIL.
https://gerrit.omnirom.org/#/c/1701/
Hi Adam
Faced few more generic errors and managed to resolve them.
Now stuck here. Seems something to do with fstab.
Any inputs?
Thanks
Code:
Install system fs image: /home/skishore/cm11/out/target/product/i9103/system.img
/home/skishore/cm11/out/target/product/i9103/system.img+ maxsize=642318336 blocksize=4224 total=321994968 reserve=6488064
Package target files: /home/skishore/cm11/out/target/product/i9103/obj/PACKAGING/target_files_intermediates/cm_i9103-target_files-17d6d7de93.zip
Package OTA: /home/skishore/cm11/out/target/product/i9103/cm_i9103-ota-17d6d7de93.zip
MKBOOTIMG=device/samsung/i9103/recovery/bootimg.mk \
./build/tools/releasetools/ota_from_target_files -v \
-p /home/skishore/cm11/out/host/linux-x86 \
-k build/target/product/security/testkey \
--backup=true \
--override_device=galaxyr,i9103,GT-I9103,GTI9103 \
/home/skishore/cm11/out/target/product/i9103/obj/PACKAGING/target_files_intermediates/cm_i9103-target_files-17d6d7de93.zip /home/skishore/cm11/out/target/product/i9103/cm_i9103-ota-17d6d7de93.zip
unzipping target target-files...
running: unzip -o -q /home/skishore/cm11/out/target/product/i9103/obj/PACKAGING/target_files_intermediates/cm_i9103-target_files-17d6d7de93.zip -d /tmp/targetfiles-2Epmv1
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 887, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 830, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/skishore/cm11/build/tools/releasetools/common.py", line 155, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(zip, d["fstab_version"])
File "/home/skishore/cm11/build/tools/releasetools/common.py", line 227, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/efs ext4 /dev/block/mmcblk0p1"
make: *** [/home/skishore/cm11/out/target/product/i9103/cm_i9103-ota-17d6d7de93.zip] Error 1
It seems like a whitespace is missing there after 'ext4'.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
It seems like a whitespace is missing there after 'ext4'.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I find a recovery.fstab in product out recovery root
Is this the one to be changed? Am not sure where else to find this file.
Code:
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p6
/preload ext4 /dev/block/mmcblk0p11
/misc emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/sdcard vfat /dev/block/mmcblk0p4
/external_sd vfat /dev/block/mmcblk1p1
/sd-ext ext4 /dev/block/mmcblk1p2
This is the content.
FYI i have extracted files for build from my phone running your project equilibrium.
It's the same fstab.n1 in device folder. Why did you extract this kinda files? They're all there in device tree.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
It's the same fstab.n1 in device folder. Why did you extract this kinda files? They're all there in device tree.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Sorry, I meant that .extract-files.sh for vendor proprietary folder. The device folder is cm cloned and untouched.
The issue here I could narrow down further is the misc_info.txt in the target zip file is read by tools/releasetools/common.py for " fstab_version" as for 1 or 2 for further actions. It is fixed as 2 for this branch by the bootable/recovery/Android.mk
There is no such version check in CM10.1 and I assume our recovery.fstab is of version 1.
Is it needed to be rewritten?
kishoreinme said:
Sorry, I meant that .extract-files.sh for vendor proprietary folder. The device folder is cm cloned and untouched.
The issue here I could narrow down further is the misc_info.txt in the target zip file is read by tools/releasetools/common.py for " fstab_version" as for 1 or 2 for further actions. It is fixed as 2 for this branch by the bootable/recovery/Android.mk
There is no such version check in CM10.1 and I assume our recovery.fstab is of version 1.
Is it needed to be rewritten?
Click to expand...
Click to collapse
You cannot build cm 11 with cm 10.1 device tree
at least you will need cm 10.2 tree
Grarak said:
You cannot build cm 11 with cm 10.1 device tree
at least you will need cm 10.2 tree
Click to expand...
Click to collapse
Thanks garak, how to get the 10.2 tree?
But by changing the fstab version to 1, the build completed.
But i could not flash it with my cwm 6.0.3.4
It says installation aborted.status 0
:crying:
If someone can build cm11(4.4 KitKat)for our devices it was great
at least,According from the news 4.4 will more optimize it's memory usage and improve whole performance for low end devices
but I still worrying that may not have or the porting will very hard because our Tegra2 was lack with neon SSIMD
aaa839 said:
If someone can build cm11(4.4 KitKat)for our devices it was great
at least,According from the news 4.4 will more optimize it's memory usage and improve whole performance for low end devices
but I still worrying that may not have or the porting will very hard because our Tegra2 was lack with neon SSIMD
Click to expand...
Click to collapse
Just a heads up if you do get it to work, I tried this for my Galaxy Tab 10.1 and the audio blobs are incompatible with the new audioflinger. I can't get past the boot animation because of this.
AAccount said:
Just a heads up if you do get it to work, I tried this for my Galaxy Tab 10.1 and the audio blobs are incompatible with the new audioflinger. I can't get past the boot animation because of this.
Click to expand...
Click to collapse
We use source-built audio libs, it can be easily modified to work.
For ICS blobs, you have to cherry-pick all old commits, maybe some didn't get into the tree accidentally. I encountered another crash, a function isn't added to the ifdefs yet.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
We use source-built audio libs, it can be easily modified to work.
For ICS blobs, you have to cherry-pick all old commits, maybe some didn't get into the tree accidentally. I encountered another crash, a function isn't added to the ifdefs yet.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Could you please post the source having 10.2 device tree.
And also does flashing CM11 need a new CWM? I have the 6.0.3.5 selinux CWM installed which doesnt allow flashing the zip generated.
Thanks
kishoreinme said:
Could you please post the source having 10.2 device tree.
And also does flashing CM11 need a new CWM? I have the 6.0.3.5 selinux CWM installed which doesnt allow flashing the zip generated.
Thanks
Click to expand...
Click to collapse
https://github.com/tpruvot/android_{device_Samsung_i9103,kernel_samsung_n1}
Yes, you need a newer one which supports the set_metadata_recursive function. You might build one.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
https://github.com/tpruvot/android_{device_Samsung_i9103,kernel_samsung_n1}
Yes, you need a newer one which supports the set_metadata_recursive function. You might build one.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Thanks for the links. Cloned the 10.2 device files/dependencies .
On compiling bionic I am facing compiler issues reporting standard headers missing/pre declared.
Attached log
Could you please help out?
The build completed and the generated cm zip is usable without a new recovery though.
I tried to flash the recovery.img generated during the same with heimdall.
After flashing I Couldnt get into recovery mode.
Is there any other special method to build/flash recovery from cm sources?
or if you can, post a working recovery image.
Sorry that I am bugging more here. This is my first time I try to build CM from sources to get something up on the phone
kishoreinme said:
Thanks for the links. Cloned the 10.2 device files/dependencies .
On compiling bionic I am facing compiler issues reporting standard headers missing/pre declared.
Attached log
Could you please help out?
Click to expand...
Click to collapse
You need to set TARGET_CPU_VARIANT to 'generic' in BoardConfig.mk.
kishoreinme said:
The build completed and the generated cm zip is usable without a new recovery though.
I tried to flash the recovery.img generated during the same with heimdall.
After flashing I Couldnt get into recovery mode.
Is there any other special method to build/flash recovery from cm sources?
or if you can, post a working recovery image.
Sorry that I am bugging more here. This is my first time I try to build CM from sources to get something up on the phone
Click to expand...
Click to collapse
Try to build an image with the online builder at builder.clockworkmod.com. The R can be found among existing devices, but I think it still uses cm-10.1 branch as the official repo isn't updated to 10.2+. Or you can alternatively use the manual mode. I would also prefer the latter.
QUOTE=Adam77Root;47514517]You need to set TARGET_CPU_VARIANT to 'generic' in BoardConfig.mk.
Try to build an image with the online builder at builder.clockworkmod.com. The R can be found among existing devices, but I think it still uses cm-10.1 branch as the official repo isn't updated to 10.2+. Or you can alternatively use the manual mode. I would also prefer the latter.[/QUOTE]
Thanks Adam
I tried manually building at the online builder . Getting the error
Code:
bionic/libc/Android.mk:429: TARGET_CPU_VARIANT is not defined
Console goes here
http://jenkins.cyanogenmod.com/job/recovery/45774/console
Disclaimer (partially borrowed from MIT license) - WARNING:
THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. If you loose your data, brick your device, any other damage or anything else happens (e.g. your cat eats your dog), it is YOUR PROBLEM and YOUR RESPONSIBILITY. Your device warranty is most probably void after installing this.
Although my original intention was just to help with porting CM 13 to i9305, I ended up with my build
To avoid any confusion a because I still have a felling that some people don`t understand this, I have to explain one more detail. I didn`t create this, I only built it. It is a big difference, similar to buying versus building a house. Buying a house is not a simple thing (at least in my country) and you`d probably need to do some changes and repairs before you can start living in it. But building a house is something completely different and much more difficult. The work I`ve done on this CM build is more like buying a house. The see the list of people who "built the house" go into Settings on your phone, section About phone and then Contributors. It is a really long list. Thanks to all of them
Also, please, keep in mind, that I am only sharing results of my hobby.
It is build mostly directly from CyanogenMod 13.0 sources. I only added support for i9305 and cm12 chroot for RIL support. See the original thread for some details. Anyway my work on this is really small, I fixed some problems a put all of this together.
You can download here:
cm-13.0-20160907-UNOFFICIAL-i9305.zip
There is also another builds from @evilracer123. (EDIT 31.3. 2016)
If you want you can also download unofficial build of TWRP with f2fs support TWRP-UNOFFICAIL-3.0.1.img
Changelog:
EDIT (17.1. 2016) - new build with bluetooth fixed
EDIT (19.1. 2016) - new build with bluetooth for non owner fixed, the code for this build downloaded yesterday
EDIT (22.1. 2016) - new build
EDIT (25.1. 2016) - new build - there is some bug in FileManager - see http://forum.xda-developers.com/showpost.php?p=64980000&postcount=150
EDIT (27.1. 2016) - new buld - FileManager bug fixed, Answer call with hardware HOME button commit included
EDIT (29.1. 2016) - new build
EDIT (1.2. 2016) - new build - attempt to fix bluetooth audio problem
EDIT (8.2. 2016) - new build - clock overflow fix (details)
EDIT (17.2. 2016) - new build - I added the SlimISP_PH.bin file, fixed the crashing gallery for non-owner (I added the INTERACT_ACROSS_USERS permission, I hope that it is a correct fix) and added rules for selinux denies @BMP007 reported for logcat.
EDIT (25.2. 2016) - new build with multiple RIL implementations, diff attached
EDIT (19.3. 2016) - new build, f2fs support (some hints here). I attached 2016-03-18_16-49-21-cm-13.0-20160318-UNOFFICIAL-i9305.tar.gz, which contains diff file, roomservice.xml and list of used commits.
EDIT (31.3. 2016) - new build
EDIT (18.4. 2016) - new build
EDIT (25.4. 2016) - new build
EDIT (20.5. 2016) - new build
EDIT (23.6. 2016) - new build
EDIT (7.9. 2016) - new build
EDIT (10.4. 2016) - new build, compiled with ArchiDriod optimizations (thanks to @JustArchi), fixed mDNIe settings
This ROM supports F2FS - you can find some hints, how to use it here. (EDIT 31.3. 2016)
If you want world writable sdcard, set property persist.world_writable_sdcard to true (search the thread to see how) , but be aware that this is not standard behavior.
Multiple RIL implementation
In this ROM, there are more then one RIL implementations. None of them is perfect, but you can choose, which one of them works better for you. The first RIL implementation is the usual CM 12.1 based one (this is the default one), the second one is based on proprietary files extracted from stock 4.4.4 ROM downloaded from sammobile.com (I9305XXUFOB2_I9305PHNFOB2_I9305XXUFOA1_HOME.tar.md5), the third is based on proprietary files from TheMuppets, with one small change (see here for details). To switch between them open shell (over adb, or using the build in app, or whatever you like) and execute command ril. You will see something like this:
Code:
Select RIL implementation:
* 1 - CM 12.1 based
2 - Stock 4.4.4 based
3 - TheMuppets based
x - quit
?
Type 1,2,3 or x and hit enter. The requires root, so be sure it is enabled. After switching, reboot the phone. If you don`t want bother with this, don`t. The default one is, based on my experience, the best
If you want gapps, use http://opengapps.org/. As mentioned several times elsewhere flash it RIGHT AFTER the ROM. I tried the nano version and it works fine.
As far as I know all hardware and RIL is working without problems (even barometer is correctly detected).
Know BUGs:
- sometimes after boot RIL is not started correctly (http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-t3252492/post64740417#post64740417) - data connection (and maybe something else) is not working. In that case turn on and of flight mode (or go somewhere without signal). I trying to fix this, but it is difficult.
- the led flash light used as a torch goes off together with the display (http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-t3252492/post64699946#post64699946)(fixed http://review.cyanogenmod.org/#/c/132783/)
- I suppose there is still msm_hsic_host wakelock bug (https://jira.cyanogenmod.org/browse/CYAN-2266). Supposedly unplugging the charger with display on should prevent this. EDIT (13.2. 2016) Some people are reporting that is fixed. I didn`t anyting specific to fix it, so I am not sure. One possibility is that this was also caused by the clock bug.
- if you have non FAT partition on you sdcard, you get a message that sdcard is corrupted. I`ll try to fix this one, it should not be difficult and it is annoying for me.
- gallery app is crashing for non owner (EDIT 19.1. 2016) (EDIT 17.2. 2016)
- there a problem with bluetooth audio - it occasionally stops for few seconds may be fixed in the today`s build (EDIT 1.2. 2016)
- on the first boot (after /data wipe) the SIM may not be found. Reboot should fix this. (EDIT 31.3. 2016)
Selinux is enforcing. If you used some of my previous builds from the original thread and there is something broken, what worked before, this may be the reason. In that case output of dmesg | grep 'avc.*denied' from the moment the problem happens, is a big help to solve it.
Code related to this can be found here:
https://github.com/p-an/i9305-cm13-device
https://github.com/p-an/android_system_core/tree/cm-13.0
https://github.com/p-an/android_build/
and some smaller changes in attached diffs (part of attached tar.gz archives as code.diff since 2016-3-18)
Build instructions:
This is definitely not the only way how to build CM13 for i9305, but it is the procedure, which I, more or less, use.
First of all read (and understand) the original guide. My build process is modified version of it. The modification is necessary, because there is no official CM13 for i9305, so the breakfast command won`t work. It is replaced by creating .repo/local_manifests/roomservice.xml file. Another change is that proprietary file are part of my github repo, so you don`t have to connect the phone.
Followe the guide mentioned above till the repo command setup. The next step is to initialize the CyanogenMod source repository - use the cm-13.0 branch:
Code:
$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0
Now before you do repo sync, you have to create the roomservice.xml file (note the actual command is old, download the latest .tar.gz archive attached to this post and extract roomservice.xml from it):
Code:
$ mkdir .repo/local_manifests
$ wget "http://forum.xda-developers.com/attachment.php?attachmentid=3657032&d=1456237857" -O .repo/local_manifests/roomservice.xml
Now is time for downloading the code (it takes some time):
Code:
$ repo sync
After this is done you will probably need to sync the code from my github with upstream. It may up to date, but i can`t guarantee it. First add the upstream repo:
Code:
$ cd ~/android/system/system/core/
$ git remote add upstream https://github.com/CyanogenMod/android_system_core.git
And now sync the code:
Code:
$ cd ~/android/system/system/core/
$ git checkout cm-13.0
$ git fetch upstream
$ git merge upstream/cm-13.0 -m 'sync with upstream'
The checkout is necessary to have cm-13.0 branch active. Following two commands download the code from upstream and merge it. They can be replaced with one pull command. Now apply patches. I usually attach them either to this post, or the post, where I announce something new (like a fix). The reason why I share some changes this way, is that I don`t wan`t to fork whole big repository because of a small change. In the latest (cm-13.0-20160217-UNOFFICIAL-i9305.diff) diff there is only one change bigger than one line - delete 5 lines (2 of them are comments). This is usually easy to change manually, if patch fails. You can use this https://groups.google.com/forum/#!topic/repo-discuss/43juvD1qGIQ to apply the patch (store the script into ~/bin/repo_patch and make executable).
Code:
$ cd ~/android/system/
$ repo_patch cm-13.0-20160217-UNOFFICIAL-i9305.diff
Now proceed to the Extract proprietary blobs step. The commands are the same, but you don`t have to connect the phone to the computer:
Code:
$ cd ~/android/system/device/samsung/i9305
$ ./extract-files.sh
Since you skipped the breakfast step, you should now return to the ~/android/system/ directory and setup the environment:
Code:
$ cd ~/android/system/
$ source build/envsetup.sh
Now setup the ccache, if you want. See Turn on caching to speed up build in the original guide.
Start the build:
Code:
$ brunch i9305
If you find some problem let me know, I can try to fix it. But I can`t promise anything, this is only hobby for me and my original intention was just to help with porting CM 13 to i9305.
pAn
reserved
The bug whit the flashlight is on every CM12.1 rom.
2 min using the flashlight and the phone automaticly booting (bootloop).
Is there a chance the problem whit the sdcard to be permision problem?
Thanks i was start thinking that no one want we to have a marshmallow rom for our devices. Live long and prospect.
Sectorian said:
The bug whit the flashlight is on every CM12.1 rom.
2 min using the flashlight and the phone automaticly booting (bootloop).
Click to expand...
Click to collapse
This is new for me. I`ve probably newer used it for such a long time. I`ll put on my list
Sectorian said:
Is there a chance the problem whit the sdcard to be permision problem?
Click to expand...
Click to collapse
I don`t think so. I suppose that this is because there is ext2 partition (with Debian chroot) and Android has never designed to use sdcard with something like this. Until this version it was simply ignored. It is not a big problem, just annoying message.
Nvm sry for asking
russia101 said:
Are there some more changes then the build you already posted on the other thread ?
Click to expand...
Click to collapse
You quote entire OP and you can't read it ?
Please ...
russia101 said:
Are there some more changes then the build you already posted on the other thread ?
Click to expand...
Click to collapse
Edit your post please. No need to quote entire OP
@p.a.n gongrats for your first and the new thread with your rom and many thanks for uploading your sources.
But I am wondering, why you haven't pushed the changes in build and smdk-common, which are present in your posted diff file? Are they not needed (anymore?). And still not clear is, where to put mount_chroot.sh? In system/bin or cm12chroot/system/bin?
ok ... I tried it with usual cyanogenmod smdk-common cm-13.0 branch and original cyanogenmod build and without mount-croot.sh and: sim card and ril is working. But I still cannot hear something or anybody during a call . What vendor/samsung repo are you using? themuppets or crazyweazel and which branch? Maybe there is the problem located?
rodman01 said:
ok ... I tried it with usual cyanogenmod smdk-common cm-13.0 branch and original cyanogenmod build and without mount-croot.sh and: sim card and ril is working. But I still cannot hear something or anybody during a call . What vendor/samsung repo are you using? themuppets or crazyweazel and which branch? Maybe there is the problem located?
Click to expand...
Click to collapse
All the my changes from smdk-common are either in upstream (e.g. the incomminmg call fix) or I moved them to i9305. Script mount-croot.sh is not necessary anymore, the mounts are handled by init (init.target.rc). The only changes from the diffs which are not in those two repositories were in kernel and they are not necessary. The proprietary files which I am using are in the repo (https://github.com/p-an/i9305-cm13-device/tree/cm-13.0/proprietary, https://github.com/p-an/i9305-cm13-device/blob/cm-13.0/cm12chroot/cm12chroot.tgz), I don`t remember where I have it from Just execute extract-files.sh in device/samsung/i9305.
I really have no idea what could be wrong in your case You problems with audio or is it the still the problem with incoming calls (the phone doesn`t ring when someone calls)?
p.a.n. great work brother, installed this ROM with this Gapps (https://www.androidfilehost.com/?fid=24269982086993883) with my outdata Philz Touch 6.48 and works pretty damm good! GPS and wifi OK, incoming and outcoming calls smooth. Congratz!!!
Im expirience a slow charging whit your Rom whit agni kernel. Before that i was on Acip10 whit the same version of agni kernel and the charging work corectly. Hope im helpes.
Oher bugs: trebuchet crashing, skype is not working.
@p.a.n thanks for your all you've done,the rom works great for me,ril data 3g and lte works fine,many thanks ......
@rodman01 just and idea, you`ve probably tried it - do you have data connection, when you try the call? The bug which requires airplane mode on/off effects more than only data connection - if it happens also Llama doesn`t correctly detect area based on cell id. So it could be the reason for your problems.
Sectorian said:
Im expirience a slow charging whit your Rom whit agni kernel. Before that i was on Acip10 whit the same version of agni kernel and the charging work corectly. Hope im helpes.
Click to expand...
Click to collapse
What about cpu load, wakelocks? Did you check it?
Sectorian said:
Oher bugs: trebuchet crashing, skype is not working.
Click to expand...
Click to collapse
Could you provide some details - how to replicate it, logcat, etc. ? Trebuchet seems to be stable to me, but I using mostly another launcher. I don`t use skype, so I am afraid I can`t help with that one
Many thanks for the the tip, I will look at it and make some tests. Sim and ril is working, incoming and outgoing calls too...but no call audio, so I cannot hear the caller and he doesn't hear me neither.
rodman01 said:
Many thanks for the the tip, I will look at it and make some tests. Sim and ril is working, incoming and outgoing calls too...but no call audio, so I cannot hear the caller and he doesn't hear me neither.
Click to expand...
Click to collapse
Can you talk on a headset via the 3.5mm jack? If you can then it's related to RIL or the microphone and earpiece don't work in call.
Thanks for the awesome rom! Do I need to flash anything to get root?
floopyb said:
Thanks for the awesome rom! Do I need to flash anything to get root?
Click to expand...
Click to collapse
No, just enable the developer options, it is there
Sectorian said:
Im expirience a slow charging whit your Rom whit agni kernel. Before that i was on Acip10 whit the same version of agni kernel and the charging work corectly.
Click to expand...
Click to collapse
In AGNi control set 'Ignore unstable charging power', 'ignore safety margin', 'AC charge rate 1500mA'.
You won't damage anything, not phone nor charger.
There is a free app called Galaxy Charging Current which shows you the charging rate.
If you're too scared, just do the ignore unstable power and that will cure your issue. The other two things just make it charge even quicker.
Official LineageOS 14.1 for Samsung Galaxy S III LTE GT-I9305
1 _
_ download odin for windows
# odin
http://forum.xda-developers.com/showthread.php?t=2711451
2 _
_ flash the latest stock rom with odin (ap button)
# I9305XXUFQG1
http://updato.com/firmware-archive-select-model?record=65E064847BE811E7963AFA163EE8F90B
3 _
_ flash twrp recovery with odin (ap button)
# twrp
https://twrp.me/devices/samsunggalaxys3internationallte.html
4 _
_ flash the os with twrp
# unofficial daily build by @walter79
http://buildyourownandroid.selfhost.eu/smartphone/daily-builds/
# official weekly build
https://download.lineageos.org/i9305
5 _
_ you can also flash gapps
# OpenGApps
http://opengapps.org/
Thanks a lot to @BlueFlame4 and @walter79 for offering their build server !
XDA:DevDB Information
[ROM] Official LineageOS 14.1 for GT-I9305, ROM for the Samsung Galaxy S III I9300
Contributors
rgib
Source Code: https://github.com/LineageOS/android_kernel_samsung_smdk4412
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2017-01-20
Last Updated 2017-11-11
Great let me be the first one to thank you.
Keep Up the good work
Hi rgib, in this list of ROMs wich one is the nougat latest version for the i9305? I'm sorry I don't know the denomination.
Thanks
mop09737 said:
Hi rgib, in this list of ROMs wich one is the nougat latest version for the i9305? I'm sorry I don't know the denomination.
Thanks
Click to expand...
Click to collapse
Hi @mop09737,
the denomination is still i9305 but the build wasn't available until recently
https://visi0nary.de/builds/full/lineage-14.1-20170121-UNOFFICIAL-i9305.zip
@rgib, to build it myself, do I just have to:
repo init -b cm-14.1
repo sync --force-sync
brunch i9305
Or is there something else I have to do (maybe install some new dependencies?). I just had an error (I'm currently looking where from).
EDIT:
Found the error, attached a screenshot. Has to do with Wifi I guess.
i9305 blobs missing. check github/themuppets
JUX84 said:
Hi @mop09737,
the denomination is still i9305 but the build wasn't available until recently
https://visi0nary.de/builds/full/lineage-14.1-20170121-UNOFFICIAL-i9305.zip
@rgib, to build it myself, do I just have to:
repo init -b cm-14.1
repo sync --force-sync
brunch i9305
Or is there something else I have to do (maybe install some new dependencies?). I just had an error (I'm currently looking where from).
EDIT:
Found the error, attached a screenshot. Has to do with Wifi I guess.
Click to expand...
Click to collapse
Thanks
walter79 said:
i9305 blobs missing. check github/themuppets
Click to expand...
Click to collapse
Isn't it enough to have it in my local roomservice ?
EDIT: Just checked with 'git status' and I'm at the last commit.
Is there a way to clean up the builds files since I switched from cm-13.0 to cm-14.1, maybe there's some sort of cache or something
Hello
I try to install rom but i have a problem
In recovery during the flash of rom I have two red errors:
"Patching system image unconditionnaly:
E:unknown command [log]
E:unknown command [log]"
If i reboot after flash, phone bootloop
Did i make something wrong?
buscagoule said:
Hello
I try to install rom but i have a problem
In recovery during the flash of rom I have two red errors:
"Patching system image unconditionnaly:
E:unknown command [log]
E:unknown command [log]"
If i reboot after flash, phone bootloop
Did i make something wrong?
Click to expand...
Click to collapse
no, let's flash tomorrow's build.
JUX84 said:
Isn't it enough to have it in my local roomservice ?
EDIT: Just checked with 'git status' and I'm at the last commit.
Is there a way to clean up the builds files since I switched from cm-13.0 to cm-14.1, maybe there's some sort of cache or something
Click to expand...
Click to collapse
I completely deleted the folder contents and did a new repo init + repo sync, and apparently it just werks.
I guess some extra steps are needed when one wants to switch branches.
Is your personal build booting?
rodman01 said:
Is your personal build booting?
Click to expand...
Click to collapse
yes. let's download lineage-14.1-20170122-UNOFFICIAL-i9305.zip
thanks and ok, will try this...I finished also a build yesterday (all sources from leos 14.1), but it doesn't boot.
Stucks on leos bootanimation. Was/is there a fix on github today? Haven't seen seen changes related to smdk or i9305. Additional I got build errors with smdk-gps. I solved it with copying some files or lines from another working rom.
the new version 20170122 is still cant boot, pls help
Looks like exactly the problem I mentioned in the official cm-13.0 thread.
For me previous build booted fine, but i've must wait more time for it than usual. Didn't test latest build.
I had also bootloops with yesterdays build: 20170122. But after flashing the UPDATE-SuperSU-v2.71.zip, it boots now. So it seems, bootloop is happening because of the, from lineaos, currently removed root....
Hi, i a great pleasure to see lineage OS experiment on this device.
Do you think it will be possible that an official build coming soon?
And why this phone (better than I9300) was not fully support by cyanogen team?
Best
Optrolight
I flash 20170124 build:
Boot after flash is very, very long
I can't set up my gmail accompt only with "tap and go" method and i must connect a second phone to access the email set up
No connection data
wifi is ok
Call ok but I listen nothing and nobody hears me
No acces to my sd card with file manager
buscagoule said:
I flash 20170124 build:
Boot after flash is very, very long
I can't set up my gmail accompt only with "tap and go" method and i must connect a second phone to access the email set up
No connection data
wifi is ok
Call ok but I listen nothing and nobody hears me
No acces to my sd card with file manager
Click to expand...
Click to collapse
So why there are lot of differences between I9300 and I9305?
It's a very good question for me!!
hello i was looking for a samsung G928G S6 (Edge plus) kernel that has a drivedroid support but i was unable to find one.
since i am familiar with linux system i decided to try and build my first kernel.
i downloaded a stock kernel source from
https://opensource.samsung.com/uploadSearch?searchValue=g928
and other custom lineage os kernel from github
https://github.com/universal7420/android_kernel_samsung_universal7420
following this guide
https://forum.xda-developers.com/galaxy-s6/general/guide-how-to-build-samsung-kernel-july-t3429355
and this guide.
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
this are the steps that i did
export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-android-
export ARCH=arm64 && export SUBARCH=arm64
when i came to make clean step i was getting this error
aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
i noticed in my toolchain folder aarch64-linux-android-gcc was missing
so i downloaded some other toolchains until i found one that has gcc
moving to next steps
make clean
make mrproper
make exynos7420-zenlte_defconfig based on stock kernel and
make lineageos_zenlte_defconfig based on lineage os kernel
when i did the make -j$(nproc --all) i get this error
make: *** [Makefile:552: scripts] Error 2 and when i checked in Makefile line 552 i found this
$(Q)$(MAKE) $(build)=$(@)
i get this error everytime i try. i use Arch linux i tried in Ubuntu same thing
Cool How about Kali-linux mod did you check it?
We have Kali-Linux mod for S6 it has drive-droid build-in
Johannes89 said:
Cool How about Kali-linux mod did you check it?
We have Kali-Linux mod for S6 it has drive-droid build-in
Click to expand...
Click to collapse
i tried it yesterday but it hangs on creating image since my device is s6 edge+ not s6
Try to create img file from other source like windows or other program and move it to your phone
so i followed your advice and tried to build on windows 10 ubuntu from their store (though i hate using windows) and it was a success. i patched drivedroid stuff in the kernel
i build one from samsung official kernel and boom! drivedroid works , after a minute i experience some never ending bootloops , in 30 seconds i can use my phone after that it boots again, the loop never ends.
i clone another kernel the lineage one , after spending the whole day building , failing ,errors , bugs, electricity issue and stuff ,
I HAVE FINALLY HAVE A DEVICE THAT WORKS NO BOOTLOOPS AND DRIVEDROID IS WORKING. though the lineage os rom has some camera problems . But yeah it was a good day