[I815/P6800/P6810] CyanogenMod 9 (08/12/2012)
- Thread starter locerra
- Start date
Not working on mine. I can't search for any network...
Sent from my GT-P6800 using Tapatalk 2
When I built Alpha 2, there was a bug in Cyanogenmod (not specific to any device), that broke data. I'm hoping to be able to get back to developing within the week, and first thing I plan to do is make a new build, which should hopefully fix data and bluetooth (as well as bring in all the changes that have been going on with Cyanogenmod during the last month).
edan1979
Senior Member
Did alpha 1 have working 3G data? You still have link for Alpha 1?
Sent from my GT-P6800 using Tapatalk 2
I hope we can see soon a build with WiFi fully working. At least Bluetooth, so I probably can tether my nexus data connection through Bluetooth... not as efficient as WiFi but better than nothing.
Locerra, do you think that we can expect a Jelly Bean porting soon or later? I mean: since JB is a minor update to ICS, I suppose hardware drivers should be the same , so JB porting shouldn't be too different. Am I wrong?
Sent from my Galaxy Nexus running JB
Locerra, do you think that we can expect a Jelly Bean porting soon or later? I mean: since JB is a minor update to ICS, I suppose hardware drivers should be the same , so JB porting shouldn't be too different. Am I wrong?
Sent from my Galaxy Nexus running JB
Me too, but everything I throw at it fails
.Aorth and I (deviceless) fixed Bluetooth for the Tab 7+, and considering we have the exact same Bluetooth chip (and share a common device tree), it should just work once I make a new build. The main thing holding up a new build is that I need to reapply the hack for fixing the graphic issues, but I tossed the hack while trying to work on a real fix for them. Then of course my tab broke, so I can't really re-figure out the hack until I get a replacement (which I'm hoping to do this week).
That is the hope, but we haven't gotten any source from Google yet, so we don't really know. Regardless, I hope to make this an official CM10 device (we probably could have been official with CM9 if we could have figured out a fix for the wifi issues).
When we get the official update, would you be able to port the binary blob driver for wifi, or is CM9 strictly against use of closed blobs?
Most phones rely on binary drivers for some things, but the kernel side of the code wasn't released for wifi on our tab. This is because the wifi drivers used are under a different licence which meant Samsung didn't have to release the code. Hopefully they're using the newer drivers for ICS though, which are GPL (I believe), so they will have to release the source.
CyanogenMod isn't against binary blobs per se, they just don't redistribute them with the source code, you have to pull them off a device if you want to make a build.
Is it at all possible to make a 6810 rom from that 6800 rom or just better off waiting the few days (hopefully)?
Been seeing some 4.1 videos of my SGS running, would be so awesome to see 4.1 on our epic tabs to show their potential.
Thanks for all the effort so far!!! Hope its encouraging (and not daunting) to see all these people keen for your work OP!
I've been using alpha 2 for a long time now. Even with all the issues I preferred it to samsung's HC version. I've gotten so used to the unadulterated ICS that I'm thinking twice about whether to jump onto the official ICS upgrade or just wait for better versions of this rom.
I have sort of working 3G data with alpha 2, which doesn't have the graphics issues of alpha 1, plus has working HW acceleration. On the flip side, wifi doesn't work, it worked in alpha 1 if sitting very close to the access point, e.g. tethering from your phone.
3G data works fine only once it's working. Sometimes it won't connect to any cellular network and you need to reboot 1-3 times, or even turn it off and then back on. If the connection is active, it will stop working once the screen is turned off (standby mode) and require a reboot to get it back. That doesn't apply if the tab is plugged in to the power adapter. It also has issues entering or leaving airplane mode, it will only work as per the setting that was set coming from a fresh reboot. So as locerra said, all these issues might be related to the bugs at the time in CM9.
Just wanted to share my experience running alpha 2, if you can live without wifi, bt and a few other things, with the hope that they'll eventually be fixed, alpha 2 is pretty much usable.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
109I've started porting CyanogenMod 9 to the Galaxy Tab 7.7. Do not flash this unless you know how to backup your data and especially unless you know how to get back to stock. If you don't already know how to do this, you might want to familiarize yourself with the process now, while the developers try to stablize CM9. I don't have time to help people unbrick their devices, and will not take responsibility for any user bricking their device, you flash this at your own risk.
If you are a developer interested in helping out with the porting effort, please PM me.
Known Issues
- HDMI dongle doesn't work
- Some USB keyboards aren't working
- I815: CDMA and LTE isn't enabled
- I815: GPS doesn't work
- I815: Autobrightness is broken
Google apps can be found at http://goo.im/gapps
- I815 (August 15, 2012): http://goo.im/devs/ohanar/i815/cyanogenmod/cm-9-20120815-NIGHTLY-i815.zip
- P6800 (August 15, 2012): http://goo.im/devs/ohanar/p6800/cyanogenmod/cm-9-20120815-NIGHTLY-p6800.zip
- P6810 (August 15, 2012): http://goo.im/devs/ohanar/p6810/cyanogenmod/cm-9-20120815-NIGHTLY-p6810.zip
- P6810 (DP1, April 4, 2012): http://goo.gl/ANRQx (md5: 2be30aaa4aadcd3065239e16f0ca5247)
- P6800 (DP1, April 5, 2012): http://goo.gl/CrwCQ (md5: f333f6aca81e1fb0f08244358e492813)
Flash
Flash from ClockworkMod Recovery, make sure to wipe data/factory reset. No whining if it eats your homework.
Build Instructions
Setup a standard CyanogenMod 9 build environment (there are plenty of tutorials on the web already on how to do this). Then
- Add add the following entries to your local manifest
where you replace XXX with your device (i815, p6200, p6210, p6800, p6810, or t869).Code:<project path="device/samsung/XXX" name="ohanar/android_device_samsung_XXX" revision="ics" remote="github" /> <project path="device/samsung/smdk4210-tab" name="ohanar/android_device_samsung_smdk4210-tab" revision="ics" remote="github" /> <project path="kernel/samsung/smdk4210-tab" name="ohanar/android_kernel_samsung_smdk4210-tab" revision="ics" remote="github" /> - Make sure that your device is running the newest build of CyanogenMod 9 or stock ICS if your device has it.
- Make sure your device is plugged in and has debugging enabled.
- Run the extract-files script from your particular device tree.
- Run vendor/cm/get-prebuilts
- Your sources are now ready, to build run
Code:$ . build/envsetup.sh # this sets up the build environment $ lunch cm_XXX-userdebug # this selects your device $ mka bacon # this builds CM
- 08/08/2012
- Hopefully remaining wifi issues fixed (wifi hotfix shouldn't be needed anymore)
- Wifi tethering enabled (no clue if it works)
- 08/03/2012
- LPM fixed (can now charge while off)
- Camera force closes fixed
- 7/19/2012
- P68x0: Autobrightness fixed
- Bluetooth fixed (thanks to lowtraxx for pointing out where the issue was)
- I815: LTE Modem's massive power drain fixed
- 7/15/2012
- Wifi! -- for real real, not for play play
- P6800: SIM Toolkit Support
- Hardware-Accelerated Video (Regression in 7/10/2012)
- ASOP Charging mode (still not really working)
- 7/10/2012
- smdk4210-tab kernel
- I815 build
- vibration (regression in Alpha 2)
- 3g data on P6800 (regression in Alpha 2)
- Camera (both front and back)
- Regression: Hardware-accelated video (this also means no previews in the Camera)
- Regression: LPM
- Alpha 2
- smdk4210 kernel (common kernel used in the CM9 ports for the i9100, i777, n7000, p6200, p6210, p6800, and p6810)
- USB gadget support
- Hardware-accelerated video
- Rear facing camera (only stills for now)
- Better auto brightness (values still need to be tuned)
- LPM (charge while off)
- Probably other stuff (been a long time since last update)
- Regression: Vibrator no longer works, we now get a beep instead
- Alpha 1
- Upgrade wifi driver to compat-wireless-3.4-rc3-1
- GPS hopefully fixed (thanks to Alan Orth)
- Data Usage fixed (thanks to Alan Orth + Galaxy Tab 10.1 devs)
- DP3.1
- Wifi fix that sometimes works
- DP3
- Torch App (thanks to Alan Orth)
- Fixed reboot download
- Wifi partially works
- Other random bugs caused by building with gcc 4.6 (now using the recommended 4.4)
- DP2.1
- 3G/GSM fix (thanks to poisike)
- DP2
- Audio works!
- DP1.1
- Partial fix for autobrightness (gets brighter, doesn't get darker)
- Phone like interface is gone
- P6800: added GSM libraries, and basic 3g configuration
Credits
- aorth -- set up the device tree for the GT-6200 (Tab Plus 3g), has been a great collaborator
- poisike -- provided fix for 3g/gsm
- teamhacksung -- set up the galaxys2 device tree, which was the basis for my tree
17Everyone who is having trouble with wifi, make sure you do the following
- Wipe/Factory reset
- If you know how make a logcat.
- If you made a logcat, post it, and if you didn't don't post anything -- I'm fully aware that Wifi isn't working for everyone
- Try the hotfix I've attached to this post
If you mean it doesn't have the wpa_supplicant from stock ICS, that is because it is impossible to include a binary wpa_supplicant in the CM build process (if you tried, it would get overwritten by the one that is built from source). The reasoning is that wpa_supplicant is GPL'ed, so by law any alterations made to it that are used in a distributed binary must be publicly shared -- unfortunately Samsung has decided to ignore the law and has not released their modifications. The best I can do is provide a hotfix zip with the stock ICS wpa_supplicant until I manage to get the opensource driver fully functional.15Thread Cleaned
I have cleaned all of the off topic posts from the last few pages. I remind all this is a development thread and not for general discussion.
EDIT: Once again i have cleaned this thread, please only post here if you have something to add to the development. Lets keep it on topic from now!14So aorth just fixed RIL, the last outstanding issue from switching kernels that has plagued the Tab 7+. Unfortunately we weren't as lucky, and had a few more:
- screen glitches (which make the build unusable)
- the vibrator is broken (and produces annoying beeps)
- usb gadget support (adb should work on all platforms, mtp should work, usb tethering, etc...)
- hardware accelerated video
- proof of concept camera (this and wifi are what I'm currently working on)
- possibly other stuff that I'm forgetting
