[ROM][WIP/Experimental][AOSP][4.3.1] Google Edition for SGS4A (int'l) v0.8

Search This thread

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
What?

  • work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
  • some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
  • build makefiles modified, using CM files where possible
  • some small code modifications
  • for I9295 international only
  • stuff is broken, for how long i do not know. I'm still learning this stuff :)
  • DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned

How?

Credits
  • Google for Android (and Google search, boy this wouldn't have happened without it ;) )
  • CyanogenMod for stuff i'm using to make this happen
  • SlimRom guys
  • LeJay for jactivelte kernel sources and other stuff
  • ohwarumbloss for testing CM builds and donations
  • Chainfire for root
  • other donators and testers :)

Changes v0.8
  • Video preview fixed
  • sub-1080p video recording fixed
  • Audio volume settings copied from SlimRom jf-common, more volume


Changes v0.7.1
  • Only kernel changes
  • Newer Broadcom wireless drivers from S4 CM 10.2 kernel
  • EXT4 and JBD2 drivers from S4 CM 10.2 kernel
  • MSM-8960 related stuff from S4 CM 10.2 kernel
  • Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me :)

Changes v0.7

Changes v0.6
  • dualboot version available
  • some merges from S4 kernel, no changes in functionality
  • cwm update script doesn't format system anymore
  • libbt-vendor natively built instead copy from CM build. No change in functionality


Changes v0.5
  • Sdcard should now work (FAT32 at least, report exfat)
  • Sports Tracker doesn't crash UI when 'network' location provider isn't found

Changes v0.3 & 0.4

  • [*]Receiving calls fixed
  • Hanging up the call fixed
  • NFC doesn't crash on the background anymore, cannot test though
  • Bluetooth fixed, using lib from CM build

Changes v0.2
  • WiFi dhcp fixed
  • SuperSu included
  • init.d support
  • bash included
  • Bluetooth updates, but no full fix yet

Bugs v0.8
  • Whoa, are there any? :)

Bugs v0.7.1
  • Camera: 720p recording produces crappy videos
  • Camera: during video recording the preview is very low resolution

Bugs v0.6
  • Some problems with locations, network locaion isn't really enabled
  • Camera: 720p recording produces crappy videos
  • Camera: during video recording the preview is very low resolution
  • Backup account set to debug-only private cache for some users

Bugs v0.5
  • Some problems with locations
  • Camera: 720p recording produces crappy videos
  • Camera: during video recording the preview is very low resolution

Fixed Bugs
  • Sdcard doesn't mount
  • Cannot receive calls
  • Cannot hang up a call
  • WiFi connects, but doesn't get IP address
  • Bluetooth service fails at start, bluetooth doesn't work
  • NFC seems to be crashing on the background
  • no root as of yet

Source code
https://github.com/spegelius

Will be updating manifests and other stuff there when i figure a good way to get my changes there.

Oh and mods, if this fits the regular development section better, feel free to move it
 
Last edited:

Pkt_Lnt

Inactive Recognized Contributor
Dec 26, 2011
7,894
5,804
SLO
A little incentive. Confirmation number: 1D974208B4414071D

I'll test and report. I'm on the GDE 4.2.2 port from Darkman now.
 
  • Like
Reactions: spegelius

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
Downloading :)
Thank you very much for your efforts Mate!
Going to install this and report back soon!

Sent from my GT-I9295 using xda app-developers app


Edit1
Ok, here I come.

- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)

So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...

Edit 2:

These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so

Code:
/system/lib/hw : 
- nfc_nci.msm8960.so
- power.msm8960.so

Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim

There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)

There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)

I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..

Greetings
Thomas
 
Last edited:

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Downloading :)
Thank you very much for your efforts Mate!
Going to install this and report back soon!

Sent from my GT-I9295 using xda app-developers app


Edit1
Ok, here I come.

- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)

So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...

Edit 2:

These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so

Code:
/system/lib/hw : 
- nfc_nci.msm8960.so
- power.msm8960.so

Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim

There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)

There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)

I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..

Greetings
Thomas

Thanks for digging this stuff out. Some of those might be needed, i'l be adding them from CM repos one by one and testing how it works. I did another build, now adding Superuser to makefiles but still no go. Superuser does pop up after boot, telling su binary neds updating... Also added some init.rc scripts which are in CM build, but still no luck. After some digging, it seems that with 4.3, Google has made rooting bit more difficult. Root is my nr. 1 prio now, i'll need it to restore Titanium backups...

I've been using the rom few days now and it seems to work very well all in all. I had a camera hang yesterday, and after killing camera app it said Cannot connect to camera. Could get a logcat...
 

ohwarumbloss

Senior Member
Oct 9, 2010
1,169
805
Kalletal
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil ;)
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP ;)
Greetings
Thomas

Sent from my GT-I9295 using xda app-developers app
 
  • Like
Reactions: Pkt_Lnt

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil ;)
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP ;)
Greetings
Thomas

Sent from my GT-I9295 using xda app-developers app

Well i have the Superuser app as embedded in the rom and when starting TB, logcat shows that su binary tries to start, but fails with error:

D/su ( 2213): su invoked.
D/su ( 2214): starting daemon client 10062 10062
E/su ( 2215): connect failed with 2: No such file or directory
E/o.gZ ( 1909): Root shell has terminated unexpectedly.

Did a search of the error and it seems that it's related to root setting in developer options. The problem is, there's no setting for root in there. Gonna have to do some diffing between CM and AOSP settings.

Haven't looked into the dhcp yet.
 
  • Like
Reactions: ohwarumbloss

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
To get root working:

install SuperSu: http://xdaforums.com/showthread.php?t=1538053

Run in adb shell:
Code:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot

I'm trying to get supersu integrated, but latest from github doesn't like to play ball. Maybe i'll just use the above release and integrate it... Koush's Superuser doesn't display the dialog for root access when using CM's version and latest from github didn't find some symbols.

Edit: use value 3 if you want to give root access to apps and adb
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.

- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...:eek:
- included SuperSu to rom, root should work out of the box :)

Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.

Ver 0.2 is uploading, test away
 

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.

- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...:eek:
- included SuperSu to rom, root should work out of the box :)

Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.

Ver 0.2 is uploading, test away

nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?
 

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?




Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..

Ok, could be. Don't know how ramdisk is created during build, have to look into it.

Also, found a quite major bug: cannot receive phone calls, at least i can't. That's kinda big problem, considering this is a phone still :D
 
Last edited:

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Use dsixda kitchen to exreact the boot.img and view/edit its contents

Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz

Nothing in /dev. Apparently those files are created by kernel/something else?

I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd

From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.

And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
 

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz

Nothing in /dev. Apparently those files are created by kernel/something else?

I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd

From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.

And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.


Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:

edit: Even stock kernel doesnt have have guess issue is different :eek:

---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------

Looking at the logcat and staring at it for 20 minutes i think Logcats says


There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue :D
 

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:

edit: Even stock kernel doesnt have have guess issue is different :eek:

---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------

Looking at the logcat and staring at it for 20 minutes i think Logcats says


There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue :D

Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.

Edit: perms system:
Code:
drwxr-xr-x root     root              2014-01-29 22:11 app
drwxr-xr-x root     shell             2014-01-29 22:12 bin
-rw-r--r-- root     root         3405 2008-08-01 15:00 build.prop
drwxr-xr-x root     root              2014-01-29 22:11 cameradata
drwxr-xr-x root     root              2014-01-29 22:11 etc
drwxr-xr-x root     root              2014-01-29 22:11 fonts
drwxr-xr-x root     root              2014-01-29 22:11 framework
drwxr-xr-x root     root              2014-01-29 22:11 lib
drwxr-xr-x root     root              1970-01-01 02:00 lost+found
drwxr-xr-x root     root              2014-01-29 22:11 media
drwxr-xr-x root     root              2014-01-29 22:11 tts
drwxr-xr-x root     root              2014-01-29 22:11 usr
drwxr-xr-x root     shell             2014-01-29 22:11 vendor
drwxr-xr-x root     shell             2014-01-29 22:12 xbin

perms /system/vendor:
Code:
drwxr-xr-x root     shell             2014-01-29 22:11 firmware
drwxr-xr-x root     shell             2014-01-29 22:11 lib

perms /system/vendor/lib:
Code:
-rw-r--r-- root     root        13880 2008-08-01 15:00 libbt-vendor.so

perms /system/vendor/firmware:
Code:
-rw-r--r-- root     root         9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root     root          783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root     root        47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root     root        28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root     root        47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root     root           70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root     root        47921 2008-08-01 15:00 bcm4335_semco.hcd

Maybe i'll need to set them root:shell in vendor?
 
Last edited:

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.

Edit: perms system:
Code:
drwxr-xr-x root     root              2014-01-29 22:11 app
drwxr-xr-x root     shell             2014-01-29 22:12 bin
-rw-r--r-- root     root         3405 2008-08-01 15:00 build.prop
drwxr-xr-x root     root              2014-01-29 22:11 cameradata
drwxr-xr-x root     root              2014-01-29 22:11 etc
drwxr-xr-x root     root              2014-01-29 22:11 fonts
drwxr-xr-x root     root              2014-01-29 22:11 framework
drwxr-xr-x root     root              2014-01-29 22:11 lib
drwxr-xr-x root     root              1970-01-01 02:00 lost+found
drwxr-xr-x root     root              2014-01-29 22:11 media
drwxr-xr-x root     root              2014-01-29 22:11 tts
drwxr-xr-x root     root              2014-01-29 22:11 usr
drwxr-xr-x root     shell             2014-01-29 22:11 vendor
drwxr-xr-x root     shell             2014-01-29 22:12 xbin

perms /system/vendor:
Code:
drwxr-xr-x root     shell             2014-01-29 22:11 firmware
drwxr-xr-x root     shell             2014-01-29 22:11 lib

perms /system/vendor/lib:
Code:
-rw-r--r-- root     root        13880 2008-08-01 15:00 libbt-vendor.so

perms /system/vendor/firmware:
Code:
-rw-r--r-- root     root         9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root     root          783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root     root        47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root     root        28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root     root        47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root     root           70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root     root        47921 2008-08-01 15:00 bcm4335_semco.hcd

Maybe i'll need to set them root:shell in vendor?


try making perms in vendor as root excute user and group (i think in other words it is root:shell) :p this will inusre if we have perm issue
 
  • Like
Reactions: Pkt_Lnt

spegelius

Senior Member
Mar 29, 2011
779
1,443
Oulu
try making perms in vendor as root excute user and group (i think in other words it is root:shell) :p this will inusre if we have perm issue

No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.

I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.

Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
 
  • Like
Reactions: Pkt_Lnt

mythi

Senior Member
Mar 1, 2013
1,429
2,016
Amman
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.

I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.

Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...

Why dont we cherry pick from gs4 snapdragon version qcom things since they share the same board , just cherry pick the diver files from an aosp rom for that device I am quite sure it will work .

Sent from my GT-I9295 using Tapatalk
 
  • Like
Reactions: Pkt_Lnt

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    What?

    • work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
    • some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
    • build makefiles modified, using CM files where possible
    • some small code modifications
    • for I9295 international only
    • stuff is broken, for how long i do not know. I'm still learning this stuff :)
    • DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned

    How?

    Credits
    • Google for Android (and Google search, boy this wouldn't have happened without it ;) )
    • CyanogenMod for stuff i'm using to make this happen
    • SlimRom guys
    • LeJay for jactivelte kernel sources and other stuff
    • ohwarumbloss for testing CM builds and donations
    • Chainfire for root
    • other donators and testers :)

    Changes v0.8
    • Video preview fixed
    • sub-1080p video recording fixed
    • Audio volume settings copied from SlimRom jf-common, more volume


    Changes v0.7.1
    • Only kernel changes
    • Newer Broadcom wireless drivers from S4 CM 10.2 kernel
    • EXT4 and JBD2 drivers from S4 CM 10.2 kernel
    • MSM-8960 related stuff from S4 CM 10.2 kernel
    • Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me :)

    Changes v0.7

    Changes v0.6
    • dualboot version available
    • some merges from S4 kernel, no changes in functionality
    • cwm update script doesn't format system anymore
    • libbt-vendor natively built instead copy from CM build. No change in functionality


    Changes v0.5
    • Sdcard should now work (FAT32 at least, report exfat)
    • Sports Tracker doesn't crash UI when 'network' location provider isn't found

    Changes v0.3 & 0.4

    • [*]Receiving calls fixed
    • Hanging up the call fixed
    • NFC doesn't crash on the background anymore, cannot test though
    • Bluetooth fixed, using lib from CM build

    Changes v0.2
    • WiFi dhcp fixed
    • SuperSu included
    • init.d support
    • bash included
    • Bluetooth updates, but no full fix yet

    Bugs v0.8
    • Whoa, are there any? :)

    Bugs v0.7.1
    • Camera: 720p recording produces crappy videos
    • Camera: during video recording the preview is very low resolution

    Bugs v0.6
    • Some problems with locations, network locaion isn't really enabled
    • Camera: 720p recording produces crappy videos
    • Camera: during video recording the preview is very low resolution
    • Backup account set to debug-only private cache for some users

    Bugs v0.5
    • Some problems with locations
    • Camera: 720p recording produces crappy videos
    • Camera: during video recording the preview is very low resolution

    Fixed Bugs
    • Sdcard doesn't mount
    • Cannot receive calls
    • Cannot hang up a call
    • WiFi connects, but doesn't get IP address
    • Bluetooth service fails at start, bluetooth doesn't work
    • NFC seems to be crashing on the background
    • no root as of yet

    Source code
    https://github.com/spegelius

    Will be updating manifests and other stuff there when i figure a good way to get my changes there.

    Oh and mods, if this fits the regular development section better, feel free to move it
    6
    Uploading 0.7.1 now. Nothing has changed on the rom itself, only kernel changes

    • Newer Broadcom wireless drivers from S4 CM 10.2 kernel
    • EXT4 and JBD2 drivers from S4 CM 10.2 kernel
    • MSM-8960 related stuff from S4 CM 10.2 kernel
    • Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me :)

    What i've tested myself, everything works as before. And actually not expecting drastic changes, the kernel has been working very well already.
    Whati i hoped to achieve was to get S4 and S4 Active kernels as close as possible and i'm happy about the results. Also, i hoped that the 720p recording would've been kernel related, but no. I did some camera debugging and what caught my eye is that even though the quality is set to 720p, debug say that resolution is set to 1920x1080. But needs more investigation.
    4
    Hey. Thanks for the ROM. Always nice to see something in development for the i9295.

    I stuck 0.6 on my S4A today and all looking good so far except I'm getting a "cannot connect to camera" message when opening the camera app (or Snapchat)

    Quick search has someone with the same issue on page 1 but the following posts are more focused on restoring root.

    Any ideas?

    Clean install.

    The issue with camera might be a leftover of my fiddling with some Qualcom camera sources and not cleaning the build env before building another one, yesterday i noticed that i didn't even have the camera app anymore. Sorry about that.

    But don't worry, ver 0.7 is uploading :). Fixes:
    - the camera of course
    - network location finally working. Took some debugging, finally found out that the available location provider for network didn't have a god enough signature for ServiceWatcher. Googled the error and finally found a thread with some meaning which instructed how to add the damn provider to resource xml in frameworks/core.
    - Backup to google account: for those flashing cleanly, the setting should be on. For those dirtyflashing, you need to check this out: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
    3
    Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.

    - wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...:eek:
    - included SuperSu to rom, root should work out of the box :)

    Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.

    Ver 0.2 is uploading, test away
    3
    Hey all,

    found a way to mount the ext SD Card :victory:

    mount -o remount,rw /
    mount -t vfat -o umask=0000 /dev/block/vold/179:33 /storage/sdcard1

    Now this ROM is my daily driver...

    edit: Ringtone issue is gone