[ROM][Beta][CM9][9/28/12] Galaxy Exhibit 4G
- Thread starter jocala
- Start date
-
- Tags
- development
Actually if you do update it be better imo. By installing the update if you open settings > then go to test tool> ON Loop Picture. Not only will the led turn on but it doesn't blink anymore.
Few more steps but hey it works lolHopefully the author of the app will make this the default method. The new update actually says it has fix for our phone. And it kinda does its just not what the app does by default, maybe its just like a preliminary update to test the new method. I wonder if this method could be implemented with the included torch app that would be nice. I just hope we get emergency calling working soon.
Last edited:
He's right. 3 more button presses than before but now it doesn't blink. Stays on bright. I prefer it this way.Actually if you do update it be better imo. By installing the update if you open settings > then go to test tool> ON Loop Picture. Not only will the led turn on but it doesn't blink anymore.
Anybody else having issues with sending picture messages?
Sent from my SGH-T679 using xda app-developers app
Sent from my SGH-T679 using xda app-developers app
I ran test on mine using stock and gosmspro. In stock add subject because it changes from SMS to MMS. In gosms you needn't add a subject. Both work fine here. Fails in stock sent without subject. Hope that helps.
Sent from my SGH-T679 using xda premium
That was the issue. Thanks for your help
Sent from my SGH-T679 using xda app-developers app
The ROM is great, thank you, I just have the following issues:
1) Searching for network or manually selecting a network does not work.
2) Bluetooth tetherig doesn't work
1) Searching for network or manually selecting a network does not work.
2) Bluetooth tetherig doesn't work
Last edited:
I've tested basically ALL the apps, and none work except for the Flashlight HD LED app when you do as people say up there ^^^
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
Charge the phone all the way up and then boot into recovery choose Advanced and wipe battery to see if it fixes it. Then let it go all the way to 0 and shut itself down before recharging it all the way back up.
was hoping to flash this on my dad's phone the 911 not working is a deal breaker since we have no home phone. He is getting old and if there is an emergency 911 needs to work at least from the regular dialer.
He does not have a lock so it alright the emergency dialer does not work, but regular one needs to be fixed and i hope soon. Dieing to get ICS on that phone.
He does not have a lock so it alright the emergency dialer does not work, but regular one needs to be fixed and i hope soon. Dieing to get ICS on that phone.
911
There's currently zero progress with 911 on our phone. The pertinent files are listed below if anyone would like to take a shot at fixing it:
The original patch for 911 can be seen below:
https://github.com/CyanogenMod/andr...mmit/bd6eb47f3cec24bbad996807a140465e89e54365
Most of this is already present in SamsungRIL.java
There's currently zero progress with 911 on our phone. The pertinent files are listed below if anyone would like to take a shot at fixing it:
I've been trying to integrate code from SamsungRIL.java into our device-specific SamsungMSMRIL.java w/o any luck thus far.
The original patch for 911 can be seen below:
https://github.com/CyanogenMod/andr...mmit/bd6eb47f3cec24bbad996807a140465e89e54365
Most of this is already present in SamsungRIL.java
Last edited:
Was just wondering is that the ril we used before we switched to samsungmsmril? So could we switch back to that ril and just network time wont work again? Cause imo emergency calling > network time lol. Like till we figure out how to fix both.
Last edited:
Code:
ro.telephony.ril_class=SamsungMSMRILChange in build.prop and reboot to test your theory.
If 911 isn't working, I would suggest putting that in the list of things that aren't working in the first post.
Are there any problems with 911 in Peach Sunrise? I installed that, and I'm not having any problems with the name of my carrier not showing up properly, or not being able to do a network scan. Everything seems to work for me on that ROM.
Not hating on your CM9 ROM of course... It's pretty remarkable how far you've gotten with this. Hopefully I'll come back to it when it's out of beta status
Are there any problems with 911 in Peach Sunrise? I installed that, and I'm not having any problems with the name of my carrier not showing up properly, or not being able to do a network scan. Everything seems to work for me on that ROM.
Not hating on your CM9 ROM of course... It's pretty remarkable how far you've gotten with this. Hopefully I'll come back to it when it's out of beta status
I would suggest that you re-read the OP
As soon as the 911 issue was discovered it was immediately added to the not-working list.
No, this is a CM issue only.
I'm pretty sure I found out what's happening with battery drain and Groove IP with my phone, it may apply to what others are experiencing with Wifi as well. Apparently Groove IP, as soon as it gets activated by a call, activates WiFi high performance mode. As it happens, when the call is hanged up, most of the time (not always) the high perf mode sticks and doesn't go away until Wifi is turned off and on again.
I have tested this with the test proposed in this app's page:
When using this widget (and Groove IP not running so it gets isolated), WiFi high performance mode dutifully returns to idle state. So, I'm not sure if it's the ROM, but I can't test Groove IP with my other devices (LG Optimus V with IHO CM7 and Nexus 7 with AOKP build 1) because these apparently don't support high perf mode. The Nexus 7 shows a bit of a difference in ping times, but only at the start when Groove IP is dialing, then it goes back to the high-tens/low hundreds of ms, so it's not very reliable to tell the changes. With the Exhibit though, the difference in high-perf and low-perf is extremely marked:
If any of you guys with other devices and Groove IP installed could run the same test and see if Groove IP does the same for you, it would be great. I posted in another forum something about this, and the Groove IP person was being responsive, but I didn't have much to give him.
I have tested this with the test proposed in this app's page:
When using this widget (and Groove IP not running so it gets isolated), WiFi high performance mode dutifully returns to idle state. So, I'm not sure if it's the ROM, but I can't test Groove IP with my other devices (LG Optimus V with IHO CM7 and Nexus 7 with AOKP build 1) because these apparently don't support high perf mode. The Nexus 7 shows a bit of a difference in ping times, but only at the start when Groove IP is dialing, then it goes back to the high-tens/low hundreds of ms, so it's not very reliable to tell the changes. With the Exhibit though, the difference in high-perf and low-perf is extremely marked:
Code:
C:\Users\Andy>ping 192.168.2.9
Pinging 192.168.2.9 with 32 bytes of data:
Reply from 192.168.2.9: bytes=32 time=121ms TTL=64
Reply from 192.168.2.9: bytes=32 time=142ms TTL=64
Reply from 192.168.2.9: bytes=32 time=164ms TTL=64
Reply from 192.168.2.9: bytes=32 time=187ms TTL=64
Ping statistics for 192.168.2.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 187ms, Average = 153ms
C:\Users\Andy>ping 192.168.2.9
Pinging 192.168.2.9 with 32 bytes of data:
Reply from 192.168.2.9: bytes=32 time=2ms TTL=64
Reply from 192.168.2.9: bytes=32 time=1ms TTL=64
Reply from 192.168.2.9: bytes=32 time=1ms TTL=64
Reply from 192.168.2.9: bytes=32 time=2ms TTL=64
Ping statistics for 192.168.2.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1msIf any of you guys with other devices and Groove IP installed could run the same test and see if Groove IP does the same for you, it would be great. I posted in another forum something about this, and the Groove IP person was being responsive, but I didn't have much to give him.
Yea doesn't work to just change it. Have to set it during compile. Not that i could just call 911 anyways lol
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
137This is a port of CyanogenMod 9 (Android 4.0.x) for the Samsung Exhibit II 4G. It is very much a work-in-progress. There are no guarantees whatsoever that it will work to your requirements or that it will progress beyond its current state. Major kudos to Arco68 for his help in getting this going; you would not have this ROM except for him.
Here is a video by dennis96411, showing CM9 on the Exhibit II
What seems to work
Phone
Wifi
SMS/MMS
GPS
Bluetooth audio
Amazon Market
HW accelerated display
Headphone detection
Microphone detection
T-Mobile Wifi-calling (works for most)
init.d support
CIFS networking
Camera (Stock Camera only, 3rd-Party apps mostly don't work)
Haptic keyboard feedback
Market/Play
Gmail
Browser
Screenshots
Streaming video
What does not work (NO ETAs)
911 Emergency Calls
Torch app (check thread for alternatives)
CM9 for the Galaxy Exhibit is NOT vulnerable to USSD dialer exploits.
Vanishing text
The content of text buffers sometimes disappear when touched (messages in: gmail,yahoo,fb). Wiping cache has fixed this for some. Long-press of back key and restarting app for others.
Facebook
Facebook sync is not included in AOSP. 3rd-party apps are available in the market.
3g vs 4g
Cyanogen Mod views UMTS as 3g whereas the stock Exhibit II rom views it as 4g. Even though you see 3g on your status bar, your actual speed should be unchanged from stock.
Changing band preference
In dialer, enter Service Mode via
You should see:
[1] Automatic
[2] WCDMA Band Preference
[3] GSM Band Preference
To force WCDMA only, tap option 2, on next screen tap option 6 - WCDMA All
To force GSM only, tap option 3, on next screen tap option 7 - GSM All
You can use the back button to verify your settings took effect. To exit, tap menu button, quit. This change does not survive a reboot. If you use this frequently, save it as a contact.
WIFI Problems
Wifi is working fine for almost everyone using CyanogenMod 9 Galaxy Exhibit build (and also for the Galaxy W). If you are one of the very few having difficulties, a possible fix has been posted that may help: WiFix Manager.
Installation
Installation requires a CWM-based recovery. Download/update Galaxy Exhibit Custom CWM Recovery here.
Updating CyanogenMod 9
Once you have a stable install you're happy with you can apply future updates w/o any wiping. If for some reason a wipe is required, I'll make that known.
Download CM9 Beta
Core2idiot's CM9 Nightlies
Google Apps
Google Apps gapps-ics-20120429-signed.zip .... Mirror
Kernel sources
Copy the downloaded cm9 beta and gapps zip files to your internal or removable sdcard.
Back up your data.
Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the color Samsung/T-Mobile Exhibit logo.
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
If installing over a non-CM9 ROM you must do a ROMwipe before installing.
Select "Install zip from sdcard." Choose the cm9 beta zip from sdcard or external sdcard, depending on where you placed it. Highlight the cm9 beta zip file then press Home. Confirm the choice and installation will proceed. You may also install Google Apps (gapps) at this time. Gapps does not include all Google apps. Those not included are available from the market.
Please DO NOT PM me with support questions! Post them in this thread!27cm-9-20120810-UNOFFICIAL-ancora_tmo
https://android.googlesource.com/platform/frameworks/support
http://github.com/CyanogenMod/android_packages_apps_DSPManager
http://github.com/CyanogenMod/android_packages_apps_Settings
http://github.com/CyanogenMod/android_packages_apps_Stk
http://github.com/CyanogenMod/android_bootable_recovery
http://github.com/CyanogenMod/android_external_zlib
http://github.com/CyanogenMod/android_hardware_qcom_display
http://github.com/CyanogenMod/android_bootable_recovery
http://github.com/CyanogenMod/android_development
http://github.com/CyanogenMod/android_frameworks_base
http://github.com/CyanogenMod/android_packages_apps_Settings
http://github.com/CyanogenMod/android_vendor_cm
Front camera: working
Rear camera: working
Front video: working
Rear video: working
Panoramic: working
Led: not working
shutter sound plays twice for camera
CM9 Beta:cm-9-20120810-UNOFFICIAL-ancora_tmo.zip22Compile CM9
Portions copied from Motorola Droid X CyanogenMod Wiki
Thanks to Arco68 for hand-holding and patches. Any mistakes are mine.
These instructions assume that you will be using an Ubuntu 10.10 Linux system (or a close relation, Debian, Linux Mint,etc). Setting up a Linux partition or creating a Linux VM are beyond the scope of this post.
First, Install the Android SDK
Next, install the linux build packages required. I install using apt-get:
For 32-bit & 64-bit systems
apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
For 64-bit only systems
apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
These instructions assume an "android" directory located in your home
Install repo
Download CM9 sourceCode:mkdir ~/bin curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo chmod a+x ~/bin/repo
This can take hours. When done, ~/android/system should be at least 11Gb in size.Code:mkdir ~/android/system cd ~/android/system repo init -u git://github.com/CyanogenMod/android.git -b ics repo sync -j16
Next:
Download kernel sourceCode:cd ~/android/system/frameworks/base git remote add arco git://github.com/arco/android_frameworks_base.git git fetch arco
Download ancora_tmo device directoryCode:mkdir -p ~/android/system/kernel/samsung/ancora_tmo cd ~/android/system/kernel/samsung/ancora_tmo git init git pull https://github.com/arco/samsung-kernel-msm7x30.git Repeat the pull command occasionally to obtain updates.
Download ancora_tmo vendor directoryCode:mkdir -p ~/android/system/device/samsung/ancora_tmo cd ~/android/system/device/samsung/ancora_tmo git init git pull git://github.com/Jocala/device.ancora_tmo.ics.git Repeat the pull command occasionally to obtain updates.
Set up prebuilts:Code:mkdir -p ~/android/system/vendor/samsung/ancora_tmo cd ~/android/system/vendor/samsung/ancora_tmo git init git pull git://github.com/Jocala/vendor.ancora_tmo.ics.git Repeat the pull command occasionally to obtain updates.
Applying cherry-picksCode:cd ~/android/system ./vendor/cm/get-prebuilts
You'll need to gain at least a rudimentary knowledge of
using git and github. Teaching this is beyond the scope
of this howto. Cherry-picks must be re-applied after each
repo sync.As time goes by they also get merged, so it may be that some
cherry-picks are no longer required. You can check their status here.
Attached to this post is a script (reposync.txt) that will do a repo
sync then apply current cherry-picks. I keep it in my
android/system directory. Rename and chmod 0755.
Set up your environment & build
Building takes at least an hour. If everything worked, you should have aCode:. build/envsetup.sh lunch cm_ancora_tmo-userdebug brunch ancora_tmo
out/target/product/ancora_tmo/cm-9-SOMEDATE-UNOFFICIAL-ancora_tmo.zip file
============
CCACHE
If you have room on your build system you can speed
your builds up considerably by using ccache. ccache is a compiler
cache. It speeds up re-compilation of C/C++ code by caching
previous compiles and detecting when the same compile is
being done again.
Install it with apt-get: sudo apt-get ccache
Set environment vars for Android use:
(I put these exports in my .bashrc)
Set a cache size of 10G for optimal results:Code:export USE_CCACHE=1 export NDK_CCACHE=ccache
Check the status of your cache with the command:Code:ccache -M 10G
Code:ccache -s Returns: cache directory /home/jocala/.ccache cache hit 106673 cache miss 18379 called for link 3758 preprocessor error 5 not a C/C++ file 4425 unsupported compiler option 678 no input file 4565 files in cache 36758 cache size 3.2 Gbytes max cache size 10.0 Gbytes22
It's always hilarious when a newcomer shows up who absolutely knows it all, refuting everything we only think we know about our phones.
I think the idea of nightlies is great, I never had the resources. I've replaced the OPs download link with a link to Core2Idiot's nightly page.
On another note, I've decided to keep my Exhibit as a dev device, so I'm going to continue busting my head with 911 for a while at least. I'll post if I have any breakthroughs.
New posts
-
-
-
AC8257 CPU Based unit's problems & questions - Couldn't find any info about it- Latest: Oswald Boelcke
