Develop Bugs

[COMPLETED] New more stable ril

Decided this should have a thread of its own instead of hiding in another thread.
I originally stumbled onto this thanks to cyryl's post where I found that disabling 3G helped prevent a lot of the Sleep of Deaths (SoDs) I was seeing. (Phone was sleeping with solid green LED, then suddenly switches to orange LED and is totally hung.) That led to the discovery that the Vogue sources (which XDAndroid is derived from) had a bunch of newer fixes to their RIL library that were never pulled into XDAndroid.
I set up a clone of the XDAndroid and Vogue repos and merged them all in here:
http://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/androidhtc1
I also fixed several bugs that weren't fixed in either of the previous source trees as well (mostly memory leaks). The result was working well on my phone, but since then I've gone on to fix additional bugs, making this RIL behave almost identically to the native HTC RIL running on my G1 phone.
I used to get SoDs within about 10 minutes of booting up if I had 3G enabled. Now my phone has lasted 24 hours at a stretch without any crashes. The binary is attached here if anyone else wants to try it out. Instructions courtesy of Entropy512.
Entropy512 said:
To test this fix (should work with any Froyo 2.2.2 based builds):
Unzip the attached zip file
Place libhtcgeneric-ril.so somewhere on your SD card. For organization, I use bindfiles/lib/libhtcgeneric-ril.so
Open conf/froyo.user.conf in your favorite text editor
Within the custom_shells{} section of froyo.user.conf, add:
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
On Gingerbread it would be
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /system/lib/libhtcgeneric-ril.so
Click to expand...
Click to collapse
If you run into problems, get a log taken when the problem occurred and attach it with your post describing the problem!
Problem reports without accompanying logs are useless and a waste of time.
You will always need the output from "logcat -v time -b radio". Sometimes you will also need the output from "logcat -v time" (simultaneous with the first). If you don't know how to obtain these, then please STOP NOW and don't proceed any further with this.
There is an alternate set of files in post #6 for use with a patched rootfs. See that post for the details.
The ril in this post is no longer being updated. Use the alternate ril in post #6 to get the latest bug fixes.

Using CDMA Mode
Documenting this here for my future reference, don't do this unless you're actively involved in helping me debug:
To switch into CDMA mode with your current install
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
update secure set value='4' where name='preferred_network_mode';
.quit
Reboot for it to take effect.
Alternatively you can blow away your data.img and edit /system/build.prop and set ro.telephony.default_network = 4 before booting. (Earlier versions of this post said to use 6 for the mode. That was a mistake, 4 is the correct value.)
The original value was 0, so you can switch back to that if you need to.
You will also need to edit a property file to add your network info anyway. You must add e.g.
Code:
ro.cdma.home.operator.alpha = Sprint
ro.cdma.home.operator.numeric = 310120
Replace "Sprint" and "310120" with the correct name and ID number (MCC/MNC) for your mobile network. If you don't get the operator ID right some features will not work properly (roaming display, international dialing...). The easiest way to do this is just to create a file /data/local.prop and put these settings there. I believe the operator ID for Verizon is 310012 but haven't verified this. A complete list of operator IDs can be found on Wikipedia.
If you run into problems we need "logcat -v time -b radio" starting from as soon as possible in the boot to catch all the gory details. Also a regular "logcat -v time" running at the same time.
In fake GSM mode the phone always used a hardcoded operator ID of 310995, and the APN for that ID was used for mobile data settings. In CDMA mode the phone sees the actual operator ID, so you'll need to add an appropriate APN to match that ID. See http://cleanimport.xda/index.php?threads/1023116/.

Thanks for creating a separate testing thread for this - it needed it, and I was going to suggest it if you hadn't already made this thread .
I have tested this on my CDMA RHOD400.
Seems to work well - unfortunately I'm not a good test case, as I very rarely, if ever, get SoD's.
I do know that 30s sleep issue seems resolved - I made several calls, ran it overnight, and it still sleeps quickly with WisTilt2's test kernel. Now we need him to commit his code, get your code tested a little more and commit yours... Holy cow batman, our port is lookin great!

I use Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Here is my log http://forum.xda-developers.com/showpost.php?p=12403347&postcount=22
Borrow to use once:

After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below

New init version
This is an alternate version of the ril which uses /system/bin/pppd instead of /bin/pppd. In order for it to work, you also must change some files in the rootfs. The new files are attached here in rootnew.zip. Here are the instructions for installing from a root command shell, assuming the zip file is in /sdcard/rootnew.zip:
Code:
# cd /
# mount -o remount,rw /
# rm -rf .git
# mv init.android init.android.BAK
# unzip /sdcard/rootnew.zip
# chmod 755 init.android init.etc/ppp/ip-*-*
# mount -o remount,ro /
Reboot after installing. You only need to do this once on a given rootfs. If you switch to a different rootfs you will need to do it again.
The advantage of using this approach is that the /system/bin/pppd doesn't ever try to write to /etc/ppp (so there is less opportunity for filesystem corruption when things go wrong) and the ril will not interfere with Android VPN use. Also this approach is required for NAND installs. I expect that this approach will be the default in the next FRX/GBX releases, but so far the changes haven't been merged yet.
This ril is no longer functionally the same as the ril in the first post. The code is in the initpppd branch of my git repo.
https://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/initpppd
Update: Everything in my initpppd branch has been merged into the main xdandroid repo. All of my fixes will be in the next official xdandroid builds, there's no longer any need to use my personal repo.
You can safely install the rootnew files regardless of which ril you use. But the ril in this post requires these files; it will not work without them.
Note: the init script in this rootnew archive is a patched version based on the xdandroid git repo. If you're running on F22's rootfs, you don't need this archive. Instead, you can grab F22's rootfs image with my patches already applied.
Also note: the ril attached here is no longer equivalent in functionality to the one in the original post. This ril no longer has fake GSM support; if you're using a CDMA phone see below. This ril also no longer uses any options in the startup.txt file. If you had force_cdma or north_am_dialing in your startup.txt file they are now ignored. If you set your operator name and ID correctly in build.prop then the dialing is automatically handled by Android.
Also this ril supports dynamic mode switching for world phones. If you have a rhod400/rhod500 and use both GSM and CDMA you can switch back and forth on demand. Currently the menu for this is buried inside the *#*#INFO#*#* menu.
[size="+2"]New CDMA support[/size]
This version now switches into CDMA mode automatically; you no longer need to set the default_network property or muck with sqlite3. If you have a rhod400/rhod500 and no SIM card installed, your phone will use CDMA by default. If you have a SIM card installed, it will default to GSM and you'll have to switch to CDMA yourself. If you're using my updated Phone.apk (a new version of that as well, not yet uploaded) then the World Phone menu will be enabled automatically and you can use that to select the mode. Otherwise just use the *#*#INFO#*#* phone menu.
You will still need to set your APN for MMS to work, and you'll probably still need to install an eri.xml file. And you still need to set your operator ID properties.
Note: if you try to switch modes on the current GBX image, the Phone app will crash. It's a bug in Google's code, not the RIL. I've written a fix for this and the fix is in the XDAndroid repos, so it will work fine in the next GBX release. Froyo is fine either way.

muziling said:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
Click to expand...
Click to collapse
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.

highlandsun said:
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
Click to expand...
Click to collapse
Okay, so just to clarify, this shouldn't work for CDMA at this point? Arrrghhh is on CDMA, it seemed to work for him?
highlandsun said:
OK. Definitely it will fail with Gingerbread. I'm only testing with Froyo so far.
Click to expand...
Click to collapse
Also, just to clarify, this shouldn't work on Gingerbread at all at this point (and not just setting the network to 6 will fail)? I have it mounted in Gingerbread under the lib/froyo directory, since there is no /lib/gingerbread directory, and everything seems to be normal so far but I'm not sure how to tell if it's actually being used and I haven't called the network 6 command yet.

I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6 4).

OK, here's the current status before I leave for the weekend:
Currently the ril code sets a radio status of "SIM not ready" when the radio power is first turned on. The CDMA phone sees this and says "wtf, it's trying to use a GSM SIM card" so it kills itself to start the GSM phone code again.
So we need to be able to obtain the current operating mode in the ril so we can see, if we're trying to startup with network mode 6, it should use some other radio status code instead of the SIM-related codes.
Anyone who wants to dig into it and think about how to do that, please do...

highlandsun said:
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6).
Click to expand...
Click to collapse
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?

pdawg17 said:
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
Click to expand...
Click to collapse
It's only working well for GSM. Sounds like you should pass it by for now.

Request - for those of us following your source tree, when you upload a binary can you post which git revision that binary was built from?

Thanks
Started running this last night when you posted it in the other thread. I'm GSM only (Rhod210) so I can't help with CDMA, but I've been the victim of what are probably RIL related bugs. In areas with bad signal and when switching between EDGE/GPRS/UMTS networks I've experienced a bug where the "phone" part of the phone starts going haywire. The first symptom is that the phone no longer responds to incoming calls. From that point on, I can receive one text message after which point I can no longer send or receive text messages nor can I make or receive calls. Switchiung to airplane mode doesn't fix the issue and a reboot is required.
I'm hoping you've accidentally fixed this bug too.

highlandsun said:
It's only working well for GSM. Sounds like you should pass it by for now.
Click to expand...
Click to collapse
Confirmed. Works well on my Tilt2. It seems that data speeds are better as well. Can't say for sure but will keep testing. Great work!!

For the less educated amongst everyone, what chance is there of making a quick kernel zImage for us to try out?
I can't use anything after Feb 28th or I get a home screen lock.

The RIL is not a kernel module (.ko), but a loadable library (.so). This is why you need to use the mount command in froyo.conf.
-- Starfox

Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Okay, found the conf file. Making the changes now! Must've been a late night. lol

problem still, logs below
6d5b27e_6.zip is network mode 6 's log, com.android.phone keep FC.
6d5b27e_0.zip is network mode 0 's log, when 3G enable, phone in, who call me will listen hang up audio ,and I can not accept and reject this call in my phone.

Raa_1 said:
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Click to expand...
Click to collapse
That's odd - what build are you running, and how was it installed?
I know the conf file was included with the FRX05 full ZIP bundle (or was it the FRX04 bundle?)

WiFi hangs when switched on

Hi folks,
Since last thursday I've got a problem with my WiFi on my wildfire. Every time I turn on the WiFi (via not. bar or settings) the little box is ticked but it does not scan or anything. A couple of seconds later I get the message that the WiFi process in the settings app is not responding together with the option to kill the process. Is my WiFi broken now? Or is there a fix?
Thanks in advance
P.S. I'm using CM7 7.1.0

Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
It doesn't work. When I boot after applying the update after the bootanimation there's just a black screen. It hangs. I pulled the bat and tried it again but the same...

Usually this can be solved by wiping the dalvik cache, have you tried that?

henkdv said:
Usually this can be solved by wiping the dalvik cache, have you tried that?
Click to expand...
Click to collapse
I managed to update CM7 to 7.1.0.1, but Wi-Fi is still not working! It just hangs after switch-on. And the weirdest thing of all is that it just happened, I dind't change anything or install any new apps...

Try reflashing the radio?

3xeno said:
Try reflashing the radio?
Click to expand...
Click to collapse
Reflashed the radio, still no progress It just wont find any wifi networks and after leaving the settings app the WiFi is turned off automatically (or the app hangs and the same happens) Any other suggestions?

By the way, WiFi-Tethering does work. Still confused about this weird problem :S

Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.

henkdv said:
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
Click to expand...
Click to collapse
Could you explain these steps? I'm not so familiar with terminal inputs and especially IP adresses. Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now). Isn't this a software problem?

tobitronics said:
Could you explain these steps?
Click to expand...
Click to collapse
Sure, here's the html formatted manual page. A relevant excerpt:
ip link set - change device attributes
dev DEVICE
DEVICE specifies network device to operate on. When configuring
SR-IOV Virtual Fuction (VF) devices, this keyword should specify
the associated Physical Function (PF) device.​
up and down
change the state of the device to UP or DOWN.​
Click to expand...
Click to collapse
When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.
tobitronics said:
Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now).
Click to expand...
Click to collapse
The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler.
tobitronics said:
Isn't this a software problem?
Click to expand...
Click to collapse
I see no reason to believe the contrary.

henkdv said:
Sure, here's the html formatted manual page. A relevant excerpt:When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler. I see no reason to believe the contrary.
Click to expand...
Click to collapse
I've tried your steps. When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'. It also says something about a loop? When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'. I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused . I hope this problem can be solved....

tobitronics said:
When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'.
Click to expand...
Click to collapse
This is the RFC2863 state of the interface which is seldom relevant, the actual link state is between < and >.
tobitronics said:
It also says something about a loop?
Click to expand...
Click to collapse
That would be the loopback device. It is always present and its parameters are the same across nearly all Linux kernels, one might be funny and try to change the mtu, queueing discipline or address but it's pointless to do so.
tobitronics said:
When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'.
Click to expand...
Click to collapse
According to the documentation, DORMANT means
Interface is L1 up, but waiting for an external event, f.e. for a protocol to establish. (802.1X)
Click to expand...
Click to collapse
This could indicate a problem with wpa_supplicant rather then the radio firmware. Try to connect to an open AP such as the ones at the local Bakker Bart, NS station, McDonalds or T-Mobile shop.
tobitronics said:
I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused .
Click to expand...
Click to collapse
It is the actual source code to "Wi-Fi settings" where you normally see the list of networks.

Thanks for your explanation. So what should I do/try now? I was thinking about reinstalling the settings.apk and settingsprovider.apk ....
Sent from my HTC Wildfire using XDA App

Like I said, try an open 802.11a/b/g access point.

henkdv said:
Like I said, try an open 802.11a/b/g access point.
Click to expand...
Click to collapse
I tried that at the McDonald's and it didn't want to search for available networks, so I couldn't connect

Go to settings > Wireless & Networks. Disable this option
Mobile network
Use phone for data connection when Wi-Fi is unavailable
It should change to
Mobile network
Connect to the Internet

Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App

Takudenatsu said:
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
IT WORKSSS!!!! Thank you all for your help. That such a small little text file could cause such a large annoying problem. I hope it won't happen again...
Sent from my HTC Wildfire using XDA App

could you write how?

[Solved] Broke permissions settings, nandroid can't fix, need help

Re-written to be more concise and readable:
Long story short: I installed the program "Permissions Denied" from the market and restricted a few games. When I rebooted something was broken and I can't quite figure out what, but it runs deep through the phone.
The phone isn't bootlooping, but when I starts up it will very often become unresponsive immediately after getting to the lockscreen, my theory is that things are trying to load and crashing in the background. The only fix for this is to wait until it appear to reboot itself; the screen will come back on and show me a quick few cycles of the boot animation, then back to the lockscreen. After this, it asks to re-activate on the network. Whether or not everything works after this point has been highly variable. Currently, my phone is on but has no way of signing into a google account (isn't even an option in the list under settings).
If I try to restore a nandroid, at the very end it spits out "Error while restoring /data!". I've done this with a couple nandroids that I've used fine in the past. Fully wiping from CWM and installing a fresh rom yields similar results.
Basically my thinking at this point is to back up anything I want while I have access to the phone and try to do as full a factory reset as possible. Any ideas? Of note is that I've run the "fix permissions" function both in CWM and ROM Manager, and when I run it in ROM Manager the log shows permissions for a bunch of programs that have been wiped. So I'm guessing that permissions settings persist across wipes, but I don't know what to address that with specifically.

Bump? (rewrote OP to make it less of a train wreck of my late-night detective work)
Edit with maybe-progress: I found and installed an older apk for Permissions Denied and even though this is an older nandroid and everything has been wiped time and again, the permissions for the games I changed are still disabled.
Having trouble getting the program to actually undo anything though, and rebooting the phone is a rather tiresome task with all this going on just to find out nothing changed.
Does anyone know
1)Where permissions live, and if I can reflash whatever that is, as it is clearly corrupt here.
2)Where I can get a copy of the v2.9 apk for this app, as maybe it will be better at restoring what it did than the older version I dug up.
Edit2:I eventually just did a factory reset and it fixed everything. I had also emailed the developer of the app and he got back to me with the following advice:
It sounds like the permissions file is locked, packages.xml. Try opening my app, going into the settings, and make sure that the first option is NOT checked.
Then hit the unlock option to unlock the file.
If that doesn't work, try the following in a terminal...
su
chattr -ia /data/system/packages.xml\
Click to expand...
Click to collapse
Intuitively this sounds like it may have fixed the problem, so I'm posting it here in case anyone ends up with similar problems and finds this thread searching.

[ROM][AOSP][CM][SafeStrap]Cyanogenmod 11 for SafeStrap with locked bootloaders

[ NO LONGER ACTIVELY BEING DEVELOPED - SORRY, READ THE POSTS FOR INFORMATION ]
Yes, you read that right. What we have here is a semi-functional CM11 (Kit Kat 4.4.4) for those with the locked boot loader using Safe Strap. I have been working on this for about a month, and this is what has come of that work. However, I need some help. I am not Android savvy enough to fix all of these problems to make this a fully functioning phone.
That being said, the phone does boot up and appears to mostly work. At this time, it is not a stable daily driver.
I did search all the threads, and I believe that this is not covered in another thread, so please forgive me if there is another CM11 thread that is for SS users on AT&T's locked boot loader phones. I don't see any.
How I got here:
Well, I wanted Cyanogenmod on my AT&T locked boot loader Safe Strapped phone. Every thread says we can't do that, and I just don't like hearing people tell me we can't do something and not provide any reasons. So I decided to try for myself. For the most part, they are right, but with enough perseverance, anything could happen.
I wanted to still use my phone as my daily driver, so I needed SafeStrap to work without having to bounce between kernels.
I was currently using Safe Strap with the NB1/NC1 kernels, and running Joe-Tech's GPE 4.4.4, so I decided that I should start with a 4.4.4 variant of CM, which lead me to CM11. I tried all of them, the nightlies, the home builds, the official builds, and I stumbled across one particular CM11 nightly (20151115) that would boot and then crash as soon as it booted. So I decided to use that as a base.
Reviewing the situation/logs/errors after each crash, I slowly removed, edited, or replaced something until it would not receive that error and would move on to the next error. By the grace of God it was slowly coming together! Hence why the built in camera app is gone and replaced with open camera, etc.
If we get this working, we may be able to use these hacks or tricks to get higher versions such as CM12 or perhaps (fingers crossed) CM13. I know this is kind of lofty, but perhaps we could get something going here. Once we identify the key problems, perhaps we can also apply these tricks to other AOSP variants, such as Slim Roms.
However, let's stick to putting one foot in front of the other right now and focus on CM11.
The Setup:
AT&T boot loader locked phone with NB1/NC1 kernel and modules flashed.
Safe Strap 3.75, currently using Rom Slot 1 for this, as my daily driver is on the stock slot, however I have done it both ways, and it works either way.
Download the below CM11 zip and put it on your phone.
In Safe Strap, choose stock or rom slot, then wipe and flash the CM11 zip.
After flashing the zip, flash the wifi modules for your kernel.
Once it boots:
Go to the settings->about phone->tap on build to enable developer mode.
Then, in developer menu, choose "Disable HW overlays" to always use GPU for screen compositing. (To improve graphics performance, you may find playing with the other graphics options help also.)
Then disable the lock screen by changing "slide" to "none" (To prevent sleep of death until we fix it.) Thanks @Sterben Pistole
Temporary Root:
Simply open the KingoRoot app and click on the padlock. This will take roughly 3-5 minutes, but it will successfully give you root permissions. After reboot, root permission will be lost, but you can simply open KingoRoot and give yourself root permissions again.
Download link:
http://www.mediafire.com/download/at7iw100uawi74k/CM11-20160322-SS.zip
OR This version, which includes the qcom scripts (testing):
http://www.mediafire.com/download/nb98rtkk2j0vjpa/CM11-20160326-SS.zip
Screenshots:
Boot animationhttp://www.mediafire.com/view/wgn5m57mjk5irvm/IMG_20160310_165320.jpg
Boot animationhttp://www.mediafire.com/view/7k8y591adrwsscw/IMG_20160310_162451.jpg
Settings http://www.mediafire.com/view/lrni6kpw04oi43d/IMG_20160310_165713.jpg
About phone1http://www.mediafire.com/view/8hb8slcwxgqxycl/IMG_20160310_165603.jpg
About phone2http://www.mediafire.com/view/ugra6jdeiz6wro5/IMG_20160310_165610.jpg
Dev. optionshttp://www.mediafire.com/view/qvd2q9uwd2vv8pn/IMG_20160310_165652.jpg
Home screen2http://www.mediafire.com/view/5h9vg4wxaacfpio/IMG_20160310_165742.jpg
Menu screenhttp://www.mediafire.com/view/55bvds7k08b2nkk/IMG_20160310_165548.jpg
Home screen1http://www.mediafire.com/view/qkod20qyyv3fska/IMG_20160310_165449.jpg
Check the following posts for issues and known working items. If you have an idea of how to solve the item, the best thing to do would be to download this CM11 and try it out. If you can't do that, or if you did and found a solution, just post your thoughts/trials/2 cents here in the forum and we can hopefully integrate it into the final product!
Team Members and Contributors: (People who have contributed to the project.)
@Sterben Pistole
@Evant28
Beta testers: @DeadlySin9
Huge special thanks to @jmsq and @Joe-Tech for permission to use things we need from their GPE roms!

Known problems
Here is a list of the Known issues:
SYSTEM:
-USB - MTP, UMS, and PTP are not currently working properly. The PTP may be working, but my Linux computer cannot connect to it. The UMS will not mount. The MTP says the connection is taking too long and resets (on my computer).
-Sleep of Death - Lock screen causes sleep of death and reboot errors. Must disable the lock screen to prevent this. Thanks @Sterben Pistole !
-Mounting external SD card - Currently the extSdCard is mounted, however it requires root privileges to use it.
-SU - Currently, @Sterben Pistole has found a SU temporary work around, however, it is lost on reboot.
-GPS - Not currently functioning.
-APN settings - Since that portion of the settings crashes, I thought we could edit the xml file directly and set a default option for the carrier of choice. Not ideal, but perhaps a good work around?
-TeleService.apk has been removed, it causes too many crashes, this apk is really important for phone calls/radio control, so this would really need to be replaced.
APPS:
-GPS Status - The app works, but GPS does not appear to be functioning.
-Messaging - Crashes when you open it. I think due to settings issue with connectivity to network.
-Settings - Mostly works, a few settings options cause it to crash, most importantly, the mobile network settings for APN's etc. crashes.
-Torch - Torch apk does not function at this time. Found that during CM kernel init, changes are made to facilitate the torch.apk, which are not done by the stock kernel init. However, it is possible that these could be written in as a init.d script.

Known Working
Here is a list of the known working:
SYSTEM:
-ADB - Fully functional.
-Audio - Makes sounds when you tap on buttons, appears to work fine.
-Bluetooth - Fully functional, used it to tether internet to use the browser, worked great.
-Bootlogo - Fully functional.
-Bootup - Boots all the way up the first time.
-Camera - Fully functional.
-External SD Card - Currently mounts, but requires super user privileges to use it.
-Internal Storage - Fully functional.
-Themes - @Sterben Pistole has verrified that different themes work.
-Wifi - Remember to flash your modules in SS! Thanks @Sterben Pistole
APPS:
-Apollo - Works great.
-Browser - Works great when you have an active network connection.
-Calculator - Works great.
-Calendar - Works great.
-Camera - Works great. Thanks @Sterben Pistole
-Clock - Works great.
-CM File Manager - Now working!
-DSP Manager - Appears to work.
-Email - Appears to work.
-Gallery - Works great!
-Movie Studio - Appears to work.
-People - Appears to work.
-Phone - Appears to work, but due to a settings issue with setting the carrier, I could not connect to make a phone call.
-Terminal Emulator - Works great.
-Voice Dialer - App opens, don't know if it works as I did not add my contacts.

Change log
Code:
3/26/16
-New QCOM script testing download link CM11-20160326-SS.zip
-Removed two of the scripts, the BT, and the BTDUN scripts. Those two scripts cause the Bluetooth to fail. Now the bluetooth works just as it did before the scripts were added.
3/24/16
-Alternate CM11-20160324-QCOMSCRIPTS-SS.zip download link
-Our NB1/NC1 kernel will need certain settings, services, and scripts run to be fully functional in regards to the hardware. Our kernel, through init, was calling for several qcom shells that did not exist. They have been added into this zip. Although it does not immediately solve any issues, it may be worth trying some of the things in these scripts, thus the original 20160322 zip is still available for download.
3/22/16
-New CM11-20160322-SS.zip download link
-Removed /recovery, boot.img, and file_context from zip as well as from updater-script. This makes it smaller and quicker to flash to your phone.
-Removed Loki script from installation script, as we do not need it on SS.
3/16/16
-New CM11-20160316-SS.zip download link
-External SD card now is auto mounted to /storage/extSdCard, however, it requires super user permission to use it.
-Dropped UltraExplorer and added ES File Manager for maintenance tools. Not intended for final product.
3/15/16
-New CM11-20160315-SS.zip download link
-Added Kingoroot for simpler one click rooting, root is still temporary.
(We had already achieved temporary root, but it was more complicated to activate than this. Kingoroot can re-root after restarting your phone.)
3/14/16
-New CM11-20160314-SS.zip download link
-Subtle changes in build.prop, fixed model # in about phone.
-Added TowelRoot, UltraExplorer, and Pushbullet for maintenance tools. Not intended for final product.
3/13/16
-New CM11-20160313-SS.zip download link.
-Camera2.apk fixed, open camera removed. Thanks [user=6053184]@Sterben Pistole[/user]
-CM File Manager fixed, removed ES File explorer.
3/12/16
-New CM11-20160312-SS.zip download link.
-WiFi Fixed, be sure to flash the appropriate modules in SS! Thanks [user=6053184]@Sterben Pistole[/user] !
3/11/16
-New CM11-20160311-AKLU-SS.zip download link with fix for internal phone memory "sdcard" mounting with SS.
-Sleep of death and reboot error workaround - Thanks [user=6053184]@Sterben Pistole[/user]
- Disable the lock screen to prevent sleep of death and to allow future reboots. We will want to disable or fix the lock screen function, but the workaround allows us to continue working at this time!
3/10/16
-Uploaded to XDA for assistance from other members and to share what has been done so far.
2/26/16
-Created new boot animation reflecting SS and CM.
2/24/16
-Removed Torch.apk, camera.apk, camera2.apk due to issues.
-Added OpenCamera - works great, and you can choose where to save pics.
-Added /system/lib/modules, but still cannot insmod them, due to no root permission.
-Tried Kingroot, will not root without internet connection, used bluetooth tether, but it did not recognize internet connection, even though browser worked online.
-Tried SuperSU, but it cannot update the binary.
2/23/16
-Removed teleservices.apk from /system/priv-app due to issues.
-Edited build.prop
-Now the crrashing has stopped, however we cannot use data or make phone calls without teleservices.apk. Perhaps we can steal it from another rom?
-Camera app crashes when accessing the camera.
-Settings sometimes crash.
-File manager could not find any storage devices, internal or external. Replacd with ES File Manager and now can see all files in mounted partitions.
-sdcard and extSdCard are not mounted at boot. Write script to do that?
-GPU needed set to no HW overlays in dev. options to prevent graphics errors/tearing.
-Bluetooth tests sat! :)
2/22/16
-Installed CM11 nightly through SS, but it constantly crashes.

I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.

Wow, this looks great! I'd love to help with this if I can.

Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.

Sterben Pistole said:
I'm going to be experimenting with your build as I've started working on the same type of project as of last week. I'm going to see what I can do to fix a couple of the crashes and report back to you.
EDIT: TO ALL, IF YOU DON'T KNOW WHAT YOU'RE DOING DO NOT INSTALL THIS. IT IS NOT A DAILY DRIVER AT ALL.
EDIT 2: As I suspected, if you go into the settings and disable the lockscreen it won't go into the sleep of death.
Click to expand...
Click to collapse
Tested, works great! Updated thread! Great work!
Now we should replace or fix the lock screen. At least now we know what the problem was. Great insight!

Evant28 said:
Wow, this looks great! I'd love to help with this if I can.
Click to expand...
Click to collapse
Evant28,
You bet, if you can, download the files and play around with it. Let us know if you find any way to fix anything and we'll put it to work.

Sterben Pistole said:
Rebooting works flawlessly if you turn off the lock screen. As for the internal and external storage not mounting properly, you need a wrapper script for that. I think @jmsq made one a while ago, but he's not active anymore.
Click to expand...
Click to collapse
Great find on the disabled lock screen allowing reboots! I've added it to the instructions after booting up the first time. I am breaking down @jmsq GPE 4.4.3 rom to look at the script. I've also pm'd to ask their permission.

To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.

*deleted*

DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.

Mounting of sdcard fixed.
DeadlySin9 said:
To be fair, some of those people saying it wasn't possible did specify that it would require plenty of work that most people don't want to/can't do. Kitkat probably is the best option since we did get those GPE's working though, and I certainly applaud your efforts. I'm no developer myself or I'd help out, but I think a good way to get some things working since we can't change the kernel is to try and build and load modules for it using bypasslkm. I don't know the viability of that, but I know at least for the storage issue I've seen a case where a module was loaded in order to allow mounting.
Click to expand...
Click to collapse
Internal phone storage "sdcard" mounting is fixed, new download link in OP. Turns out SS roms use a special sdcard mounting script. Thanks for the suggestions though, we need all the help we can get!

Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?

Evant28 said:
Wow great progress! I'll be installing as soon as I get home. Now that internal storage is fixed does WiFi work?
Click to expand...
Click to collapse
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great

Sterben Pistole said:
Not at the moment. Even if Wi-Fi was working this would still be far off from being a stable daily driver. I'll post an update if I figure something out.
EDIT: WIFI IS NOW UP AND RUNNING! Modules are needed as always.
EDIT 2: Uploading build with working Wi-Fi as I am typing this. I have slow Wi-Fi so it'll be a while ;-;
EDIT 3: Got root working, but it's not out of the box. You need to flash SU in Safestrap right after modules, download towelroot, make it rain, and then install SU binary's from SU app.
EDIT 4: Root is only temporary. After a reboot it disappears. Also, theme's work great
Click to expand...
Click to collapse
Just about to flash, did you by chance get the build uploaded? Awesome work!

Evant28 said:
Just about to flash, did you by chance get the build uploaded? Awesome work!
Click to expand...
Click to collapse
uploaded wrong file lol There you go btw, there's still no service.
EDIT: Reuploading... Uploaded the original one by accident :/

Sterben Pistole said:
Does BypassLKM work on 4.4.2? I know it works on 4.3, because that's what it was built for, but if it does it would definitely help a good bit.
Click to expand...
Click to collapse
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.

DeadlySin9 said:
I'm pretty sure someone got it working while everyone was looking into getting a working kexec module. I'll see if I can't find a link somewhere.
EDIT: Still searching, but there are also directions on how to point it to the right address and compile it in the bypasslkm thread. Surge1223 built one for 4.4.2, but it's for verizon NC5 and I haven't found the link yet just found it here.
Click to expand...
Click to collapse
http://ubunmobile.blogspot.com/2015/03/moddev-enable-unsigned-kernel-modules.html Here's a link to what seems like it's what we're looking for.

AOSP 7.1 ROM/Discussion

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
What is this ROM/thread?
This is a port to the i9000 of my work for the SGH-T959P which is the Telus version of the Galaxy S. I initially started work on AOSP to see what exactly needed to be changed from AOSP to work on my device. I had a request for access to an i9000 build hence I created this thread. This is also a place to discuss using my source code to build other ROMs and/or improve it. This is not a place for a general development "How do I build a ROM?" questions - there are plenty of guides on XDA and elsewhere that say how to do this. Since I don't have an i9000, I probably can't reproduce your bug unless it is common on my device as well. As such, I will be able to provide very limited support, so if you have any concerns about your phone bricking, do not flash anything from this thread!!
Installation Instructions
You should be able to flash this from any MTD rom, but it probably works best from a 6.0 or 7.x based ROM. Root does not come pre-installed, instead you need to manually install. Due to our odd partition system, please see http://forum.xda-developers.com/showpost.php?p=69245956&postcount=3 for instructions.
Things to Take Note Of
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features" - nor will I add any as this is
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico should work just fine but are untested
Backup Backup Backup! I'm not responsible for you losing any data or anything else that could go wrong.
Working on my variant
Camera (built-in app needs workaround, see below)
RIL
SMS
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P
Headset Buttons
Partially working
Bluetooth - first time trying to enable won't work, back out of the Settings page, re-enter it and try enabling again. It should work this time...
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What doesn't
TWRP build is currently broken. To work around this, replace the ramdisk-recovery.img in the zip with the one from CM14.1
SElinux is currently in permissive mode. Still missing are the GPS sepolicies plus the LVM ones. If someone sends me a dmesg, I might be able to change this...
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+ Please do not ask me to implement this, I've tried several times and failed miserably each time.
I haven't actually verified that this boots as I don't have this specific variant!!!
XDA:DevDB Information
AOSP 7.1 ROM/Discussion, ROM for the Samsung Galaxy S I9000
Contributors
xc-racer99, Coldwindofnowhere
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Android 6.0
Based On: AOSP
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-20

Please have a look at the thread I created for my variant at http://forum.xda-developers.com/galaxy-s-4g/development/rom-aosp-7-x-galaxy-s-4g-t3485237
Build your own!
All the device-specific source code is on my github at https://github.com/xc-racer99/. The branch I've used for the build posted below is the aosp-7.1 branch. The aosp-7.1-ddk-1.19 is test branch that uses the latest DDK 1.19 PVR blobs for OMAP devices. Unfortunately, it breaks hardware decoding (and you would need to compile the correct kernel as it uses a different PVR kernel driver). It is more of interest than of actual use.
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds of 7.1. Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b 7.1". Continue on with the build guide, the device codename you want is "galaxysmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxysmtd
Other aries devices (captivate, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work. There is an i9000B kernel uploaded to https://www.androidfilehost.com/?fid=457095661767123305 - simply replace the boot.img in the i9000's zip with this one and it should work (except that in Settings you will appear as an i9000 instead of an i9000B).
For porting to other ROMs, please take note of https://github.com/xc-racer99/android_patches - these are the patches that the custom ROM and/or you must implement to have a successfully booting and functional device. You also need to have busybox and TWRP as part of the build tree.
Download Link and Changelogs
A reminder - I've not personally tested any of these builds...
2017-01-19 Build
Updated interactive governor - should result in fewer slowdowns if you use this governor
Changed low memory killer parameters so it kills a little quicker (ie before it runs out of memory)
Disabled a bit more background stuff to hopefully free a bit more memory
Fixed/cleaned up the shims that are used for the RIL - should prevent SSL issues (eg with Hotmail accounts) as well as being slightly faster and more reliable
Selinux is still in permissive mode (a dmesg could possibly help me in putting this to enforcing, if people are interested). I still don't know if the TWRP included in it is functional or not (someone can let me know, I guess )
Older Builds
2016-12-26 Build
Home button should now work
SD card/internal storage should work properly
Added ability to have /data on microSD (see here for info)
2016-12-19 Build

Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...

Coldwindofnowhere said:
Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...
Click to expand...
Click to collapse
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.

ioannis_m said:
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.
Click to expand...
Click to collapse
Hmm, ok. Thanks for testing. I guess that means it boots Did the sdcard(s) get detected properly? In my earlier builds of AOSP I had difficulties with this.
It's possible that my TWRP build is non-functional. Try replacing the ramdisk-recovery.img in the zip with one from @Coldwindofnowhere CM14 build.
Thanks for testing.

First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.

udhy said:
First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.
Click to expand...
Click to collapse
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.

xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.

Coldwindofnowhere said:
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.
Click to expand...
Click to collapse
Have you (or anyone else) managed to get a log (radio logcat, dmesg and regular logcat)? Just wondering what exactly is crashing. Likely rild - and there's a bug in our libsec-ril.so so that it won't restart automatically because then it crashes the system...

xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.

Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel

DanielBR911 said:
Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
View attachment 3976988
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel
Click to expand...
Click to collapse
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from https://www.androidfilehost.com/?fid=673368273298918331
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
udhy said:
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.
Click to expand...
Click to collapse
Ok, thanks for the clarification.

xc-racer99 said:
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
Ok, thanks for the clarification.
Click to expand...
Click to collapse
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel

I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.

DanielBR911 said:
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel
Click to expand...
Click to collapse
DanielBR911 said:
I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.
Click to expand...
Click to collapse
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.

xc-racer99 said:
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.
Click to expand...
Click to collapse
Here my logcat:
View attachment logcat.log
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.

DanielBR911 said:
Here my logcat:
View attachment 3977611
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
View attachment 3977629
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
View attachment 3977630
View attachment 3977631
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.
Click to expand...
Click to collapse
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.

xc-racer99 said:
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.
Click to expand...
Click to collapse
Thanks.
Here my dmesg:
View attachment dmesg.log

Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logcats (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.

Ano59 said:
Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logacts (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.
Click to expand...
Click to collapse
Alright, thanks for the complete rundown on errors. I'll try to go through them:
Bluetooth - having difficulty activating is not surprising. Android technically doesn't support non BT LE devices such as ours - I had to hack in support for no LE/SMP/GATT (the supporting parts of the BT stack AFAIK) with the patch https://github.com/xc-racer99/android_patches/blob/aosp-7.1/system_bt.patch. There's nothing I can really do about this. If you read the OP, it says
first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Click to expand...
Click to collapse
This was for 7.0, I guess it's changed slightly in 7.1 so I'll update the OP.
Data - this sounds totally bizarre. I wish I had an i9000 to test this. One of the big differences between the i9000 and my device, the SGH-T959P, is that you guys use the (infineon?) XMM616 for your modem while mine uses the M5720 by STE. I have yet to have an issue with data when I've tested it on my variant. Again, I'm afraid I can't do too much about this
Wifi - this sounds weird. There's some noise in the logcat, ie "12-24 02:50:04.778 W/CommandListener( 164): Failed to retrieve HW addr for wlan0 (No such device)". This is very surprising, I have nothing like this in a logcat on my device. I'm thinking perhaps that the MAC address wasn't properly setup. Could you please run "adb shell getprop | grep macaddr"? The RIL actually sets the macaddr so these two issues might be related. Did you check the md5 of the zip after downloading? It almost sounds like a bad download/ flash. The other thing is that yours is a special hardware model which doesn't like having the wifi driver built into the kernel (I did see a reference to this in a commit from the CM10.1 days). @Coldwindofnowhere's CM14 has it as a module so it might be working there.
Home button - I probably messed up the keylayout somewhere. My device has a capactive home button as opposed to a hard button. Please try pushing the attached files to /system/usr/keylayout after removing the ".img" at the end of the filename (to get around XDA's filetype filter).
Corrupt SDCard is probably my fault. Please try the new build at https://www.androidfilehost.com/?fid=529152257862690355 as I think I've found and corrected the issue.
Unfortunately, your logcat is very "chatty" - basically android prevents things from creating too much logspam. This sucks for debugging as we lose many lines, so to turn it off run
Code:
adb logcat -P ""
right at boot
Since we're having so many issues with mobile network/wifi/bluetooth, I'm wondering if our netfilter code in the kernel isn't working properly.... The thing against this theory is that things work on my variant.