[NIGHTLY][ROM][4.4] CyanogenMod 11 for Samsung Galaxy S
- Thread starter pawitp
- Start date
frauhottelmann
Inactive Recognized Developer
A little help on my failing USB connection after flashinng CM Rom
Hi Guys,
I have a Samsung Galaxy S GT-I9000.
My problem is as followed:
I installed the Custom Rom: cm-11-20140420-NIGHTLY-galaxysmtd.zip
I used CWM for that to do.
After flashing the phone with the custom rom he starts nicely.
I pass the startup questions and the phone is ready to be used.
When I try to connect the phone through the USB cable (I want the Playstore and Gmail), the PC does not create a connection and a drive to copy too. I did activate the use device as mass storage device on the screen on the phone.
When I go to the "Safely Remove Hardware and Eject Media" (in the right bottom of the windows screen) he does say "Eject GT-I9000".
In the "Diskmanagement" I don't see any mass storage devices from the phone.
I tried to use a lower more stable version of the rom: cm-11-20140405-SNAPSHOT-M5-galaxysmtd.zip but still that had not any result.
Pls help me out with my phone
Phone info:
Modelnumber: GT-I9000
Android version: 4.4.2
Smallbandversion: I9000XXJVT
Kernelversion: 3.0.101 -gd859f62 build01@ cyanogemod #1 Sat Apr 5 13:13:45 PDT 2014
CPU: ARMv7 Processor rev 2 (v7I)
Memory: 317 Mb
CyanogenMod-version: 11-20140405-SNAPSHOT-M5-galaxysmtd
Builddate: Sat Apr 5 12:51:02 PDT 2014
Buildnumber: cm_galaxysmtd-userdebug 4.4.2 KVTL49L 3abcef7900 test-keys
SELinux state: Enforcing
Kind regards,
Paul
Hi Guys,
I have a Samsung Galaxy S GT-I9000.
My problem is as followed:
I installed the Custom Rom: cm-11-20140420-NIGHTLY-galaxysmtd.zip
I used CWM for that to do.
After flashing the phone with the custom rom he starts nicely.
I pass the startup questions and the phone is ready to be used.
When I try to connect the phone through the USB cable (I want the Playstore and Gmail), the PC does not create a connection and a drive to copy too. I did activate the use device as mass storage device on the screen on the phone.
When I go to the "Safely Remove Hardware and Eject Media" (in the right bottom of the windows screen) he does say "Eject GT-I9000".
In the "Diskmanagement" I don't see any mass storage devices from the phone.
I tried to use a lower more stable version of the rom: cm-11-20140405-SNAPSHOT-M5-galaxysmtd.zip but still that had not any result.
Pls help me out with my phone
Phone info:
Modelnumber: GT-I9000
Android version: 4.4.2
Smallbandversion: I9000XXJVT
Kernelversion: 3.0.101 -gd859f62 build01@ cyanogemod #1 Sat Apr 5 13:13:45 PDT 2014
CPU: ARMv7 Processor rev 2 (v7I)
Memory: 317 Mb
CyanogenMod-version: 11-20140405-SNAPSHOT-M5-galaxysmtd
Builddate: Sat Apr 5 12:51:02 PDT 2014
Buildnumber: cm_galaxysmtd-userdebug 4.4.2 KVTL49L 3abcef7900 test-keys
SELinux state: Enforcing
Kind regards,
Paul
You need to install the gapps package in order to install the play store and gmail along with other google apps.
As for your connection issue, what does your computer says, does it recognise your phone. If you run a windows machine you might need to install the samsung's drivers. And it might be a good idea to uninstall kies, if it is on your computer, as you won't be using it.
As for your connection issue, what does your computer says, does it recognise your phone. If you run a windows machine you might need to install the samsung's drivers. And it might be a good idea to uninstall kies, if it is on your computer, as you won't be using it.
Thx for the advice.
I know about the gapps package..
That is why I tried to connect through USB. I have not installed KIES. just the samsung drivers. Furthermore I also have a Note 3 which connects flawless.
When I connect my GT-I9000, Windows also makes the connection sound.
Furthermore it is also noticable in the "Remove Hardware en Eject Media" from Windows 7, but not as a mass storage.
So it seems to be something on the phone itself.
Not really at this moment.. See my post on USB issue a little up on this page. When that is solved I'm very pleased.
What ROM did you come from? Did you do a full wipe before flashing if it wasn't from a previous nightly?
I came from the original stock rom. I did the dalvik cache wipe and so.
I installed the latest nightly. That had the issues. I thought it might be the problem of that nightly.
To make sure that was not the problem I went back to the latest Snapshot. That still kept the problems.
So I have no clue for now.
Last edited:
Did you turn on USB storage on your phone?
Without doing that, you wan't see the sdcards on your PC
Scroll down left part of your uppest status bar, you will see the option, click on it and turn on.
tetakpatalked from Nexus 7
I did turn on the Mass storage on the phone. When I plug in the USB that screen appears.
Then i selected the option to add phone as storage device.
But that does not solve the problem. Still no disk appears in my Windows explorer.
does anyone get process.system.ui force stop while trying to access the notification/quick settings via swiping downwards in status bar... coz i have this problem n it started few nightlies back
Coz of this problem i have switched back to CM11 Milestone 5 build and have experienced no problem so far... since im addicted to nightlies, jus wanna know if this problem has been soved in recent nightlies... sorry for offtopic post but any response is appretiated...
+1 ... flashing nighties almost on a daily basis but... always coming back to M5
+1 ... flashing nighties almost on a daily basis but... always coming back to M5
If you can reproduce the issue take a logcat and submit a bug report. The more information @pawitp has, the better he can work on fixing the issue.
New phone
Hi all devs and friends... I have gone ahead and purchased a Nexus 5. Its an incredible phone and am enjoying it a lot. Needless to say, I had its bootloader unlocked, rooted, installed custom recovery and custom kernel within the first hour of getting it.
I still have my trusty SGS i9000 which I have filled up with games and given to my little daughter. I will now be sharing time between SGS and N5 forums now. Will never actually leave SGS forums I guess
Nevertheless, I thought this to be as appropriate a time as any to thank all the wonderful devs and friends here who help out each other and keep the SGS relevant even after more than 3 years... kudos to all!!! :good:
PS: you will see this message in different threads... that is because I owe this to many devs and don't want to miss out thanking any of them.
Hi all devs and friends... I have gone ahead and purchased a Nexus 5. Its an incredible phone and am enjoying it a lot. Needless to say, I had its bootloader unlocked, rooted, installed custom recovery and custom kernel within the first hour of getting it.
I still have my trusty SGS i9000 which I have filled up with games and given to my little daughter. I will now be sharing time between SGS and N5 forums now. Will never actually leave SGS forums I guess
Nevertheless, I thought this to be as appropriate a time as any to thank all the wonderful devs and friends here who help out each other and keep the SGS relevant even after more than 3 years... kudos to all!!! :good:
PS: you will see this message in different threads... that is because I owe this to many devs and don't want to miss out thanking any of them.
AFAIK, everyone's using the CMA implementation I've released earlier, which is buggy in a lot of places. A different approach is required, but I'm not really interested in debugging/writing it.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
393CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:#include <std_disclaimer.h> /* * Your 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. */
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
Latest build: http://download.cyanogenmod.org/?device=galaxysmtd
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
(Note: a more detailed instruction for first-time install is available on CM Wiki: http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd)
- If you're on a ROM prior to 2.3, upgrade to 2.3 is recommended.
- Root your device and install ClockworkMod Recovery (e.g. Semaphore_2.7.4.tar from http://www.semaphore.gr/downloads).
- Reboot into Recovery using 3-button-combo
- Do a Nandroid backup!
- WIPE (wipe data/factory reset + wipe cache partition)
- Install the ROM from internal sdcard using ClockworkMod Recovery
- Optionally install the Google Addon
- Do a Nandroid Backup!
- WIPE (wipe data/factory reset + wipe cache partition)
- Install the ROM from internal sdcard using ClockworkMod Recovery
- Optionally install the Google Addon
- Do a Nandroid Backup!
- Install the ROM from internal sdcard using ClockworkMod Recovery
- You will finally see a "set_metadata_recursive" status 7 error. That is normal.
- Reboot back into recovery (the reboot is required)
- Install the ROM again from internal sdcard using ClockworkMod Recovery
- Optionally restore /data from Nandroid Backup (the update will wipe your /data)
- Optionally install the Google Addon
- Do a Nandroid Backup!
- Install the ROM from internal sdcard using ClockworkMod Recovery
- Optionally install the Google Addon
- Do a Nandroid Backup!
- Install the ROM from internal sdcard using ClockworkMod Recovery
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
- Some CyanogenMod features a missing - please do not file bug reports for those.
- Cannot set value via custom brightness "Edit" menu
- No account selected for Backup (gapps problem?)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Code:What is your-- Phone model: Radio (baseband): CM version: CM Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: CMSettings/Performance settings (other than stock): ART Runtime: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Does this ROM support FM radio?
I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.
TL;DR: No built-in FM radio except if someone else does it and submits a patch.
Why aren't configurations with more than 368 MB used?
Kernels with more than 368 MB have to sacrifice high-bitrate HD playback ability. The current memory configuration has been designed for maximum compatibility.
Wi-Fi AP does not work after restoring /data with CWM
CWM does not handle SELinux very well yet. Run this in a root shell to clear all wifi data and reboot.
Code:rm -rf /data/misc/wifi
Changelog
A rough changelog is available here:
http://changelog.bbqdroid.org/#/galaxysmtd/next or http://www.cmxlog.com/11/galaxysmtd/
For previous unofficial releases, see here
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!100Need more RAM?
Need more RAM?
Using CMA, memory usually reserved for hardware (camera, video encoding/decoding, jpeg encoding) can be freed for use by applications when they are not in-use. All features, including 720p recording, high-rate video decoding, etc. will still work as before.
This is a WIP. No ETA. There are still a lot of problems with it and it might not be released at all if I don't have time to fix all the issues. Please don't ask to test either, if I need testers, I'd post it in this thread.6520131203
- Added TV Out in Settings -> Display -> Advanced Settings
- Prevent back button from being pressed in incoming call screen
- Fixed Browser FC in Advanced -> Website settings
- Fixed Quick Access Ribbon gone when switching from Quick Settings
- Fixed 2G/3G Quick Settings toggle
- Fixed stuttering FLAC music playback
39About RAM mode
Due to an oversight, this build wasn't shipped with low RAM mode enabled. If anyone wants to try, you can add "ro.config.low_ram=true" to your /system/build.prop.
This will disable several features such as translucent status bar, lock screen widgets.
Future builds will ship with this option enabled. (This is actually mandated by the Android CTS. Those that prefer the effects over low memory usage must manually remove the config from build.prop. Before anyone asks, it won't be configurable from Settings.)
