CyanogenMod 9 for Samsung Galaxy S2 HD LTE (SGH-I757M)
THIS IS AN UNOFFICIAL BUILD OF CYANOGENMOD 9 BUT CAN STILL BE USED AS A DAILY DRIVER.
CyanogenMod is an open source replacement firmware based on the Android mobile operating system for smart phones and tablet computers. It offers features and options not found in the official firmware distributed by vendors of these devices.
Click to expand...
Click to collapse
Bell Canada released the Galaxy S2 HD LTE (SGH-I757M), which is a slight upgrade from its original Galaxy S2 GT-I9100M released the summer before, with now a bigger display and HD resolution. Since Bell hadn't released an ICS update yet, I have ported CyanogenMod 9 (stock ICS / Android 4.0) to the SGH-I757M.
NOTE: I was told by mods to post this thread in this General forum because it's not an I9100.
{
"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"
}
(Screenshots attached below)
What works:
Pretty much everything for daily use. Click below for details.
Code:
- Phone calls
- 3G/HSPA/LTE Data
- SMS send/receive
- Wi-Fi
- Video playback
- YouTube (including HD videos)
- Adobe Flash
- Hardware acceleration in browser
- Rear camera (model M5MO) takes photos and videos, and uses flash
- Front camera (model SR200PC20M) - takes photos and videos
- BLN (Backlight Notification on buttons)
- Overclocking/underclocking
- Face Unlock
- Panorama mode for camera
- USB mass storage
- MTP
- Skype
- Audio from speakers
- Play Store
- Vibration and haptic feedback
- Orientation sensor
- Magnetic field sensor / compass (model AK8975)
- Gyroscope (model K3G)
- Accelerometer (model K3DH)
- Optical sensor, i.e. proximity and ambient light sensor (model TAOS)
- Auto-brightness
- Bluetooth (and A2DP)
- GPS
- Headphone audio
- Torch app
- USB tethering
- Speakerphone
- Wi-Fi hotspot
- Google Goggles
- Lights on capacitive buttons
- Internal and external (micro) SD card access
- Note: Internal SD is under [B]/mnt/emmc[/B], micro SD is '/sdcard'
- CPU frequency is being reported correctly as 1512MHz
- MHL (compiled into kernel but not tried yet)
What doesn't work:
- I.P. CALLING: VoIP/SIP clients like CSipSimple and Dell Voice crash when making calls, or nothing heard at other end of line when using them. Click here and here for more info. Skype works fine.
- IN CAMCORDER: The 'Silly Faces' effects option for the front/rear camcorders is currently showing a distorted image in the preview screen. However, the video recording itself gets saved perfectly with the chosen effect. Normal front/rear camcorder functionality (i.e. without the silly effects) has no issues. If you want to help out, click here for all the logcat info and analysis for the Silly Faces option.
- IN CAMCORDER: Not really an issue, but the zoom control should not be present in 1080p mode for the camcorder, because it does not zoom in 1080p (limitation of Galaxy S2, not CM9)
- IN CAMERA: No touch-to-focus for camera, although regular focus works fine. A workaround would be to use LgCamera app from the Play Store.
- CAPACITIVE BUTTONS: button lights will not come on when turning device on from sleep; user must touch screen after 10 seconds to turn button lights on (issue is common in CM9 for other SGS2 Qualcomm-based variants)
Download:
WARNING! Do not flash this to a different device model from the one it's meant for. It will not work with the other Galaxy S2 iterations, so don't try it with the Bell Galaxy S2 I9100M (non-HD). DO NOT flash it on the Asian variant of the GS2 HD (SHV-E120) either, as it uses slightly different internal hardware - the ROM will be unstable and the phone component will not work. If you are sure you have the CANADIAN Bell Galaxy S2 HD LTE (SGH-I757M), then click on the button below:
(For questions about CM9 for the SHV-120L, contact skysbird on Twitter or GitHub. I will not discuss that device in my thread.)
OLD LINK: http://d-h.st/users/dsi
UPDATE: September 20, 2012: I don't own this device anymore, and am no longer maintaining the builds, please find latest versions here, thanks to XDA user crlogic:
http://d-h.st/users/crlogic
Go to the Dev-Host link above and navigate to the CM9 sub-folder to access the files required for the following steps. Please read the installation instructions carefully.
Support my work:
DONATE / FOLLOW ME
Full instructions for installing:
Download the necessary files:
1) Ensure you have my latest ClockworkMod (CWM) Recovery image for the SGH-I757M. Please refer to this thread for details. NOTE: The original released version of CWM for this device is not compatible with the CM9 ROMs, so update to the latest one please.
2) Download the CM9 ROM from the SGS2 HD LTE / cyanogenmod9 folder found at the big Dev-Host link above.
3) Download the Google Apps (gapps) file from the SGS2 HD LTE / cyanogenmod9 folder found at the link above. The Google Apps are flashed separately from the ROM due to legal requirements (proprietary files). They include Gmail, YouTube, Play Store, Maps, etc.
4) Optional: Download the stock Bell ICS modem (MUGLH2) from the SGS2 HD LTE / factory images folder. You should skip this step if you had earlier flashed the stock Bell ICS update, since it contains that modem/baseband (check your Settings-->About screen to verify the Baseband).
Back up your data:
1) If you're coming from a non-CM9 ROM, back up your apps and data with the Titanium Backup app if you wish. Back up your SMS messages with apps like 'SMS Backup and Restore'.
2) Boot into CWM (hold down power and both volume buttons, let go at the Samsung logo)
3) Enter CWM Recovery and make a Nandroid backup of your current ROM, just in case.
Now flash:
1a) If you have CM9 already installed and want to flash it again: In CWM - wipe cache, then go to Advanced menu and wipe Dalvik cache. Then flash the CM9 zip file.
1b) OR if this is your first time flashing CM9: In CWM - wipe data (factory reset), then flash the CM9 zip file TWICE.
2) Next, flash the zip file for Google Apps - it is recommended to flash this every time you flash a new CM9 ROM!
3) If you had also downloaded the modem, then flash that as well.
4) Reboot phone
5) If you have problems, read the FAQ below and ask questions in this thread if necessary. Please do not PM me about tech support.
Frequently Asked Questions (FAQ), Change Logs, Sources, Acknowledgements, etc.
- NOTE: I do not own this device anymore and cannot provide tech support. All help is found in the following posts.
CyanogenMod 10 - Jelly Bean available?
- Yes it is, go here.
Frequently Asked Questions
Q. I flashed CM9 after coming from another non-CM9 ROM, and I get errors or phone fails to boot.
A. Make sure you read the instructions in Post 1 for flashing correctly. If you still can't figure it out, go to the "advanced" menu section in the recovery menu and select the log output to see what went wrong. If it says you have an "assert" issue then you obviously have the wrong version of ClockworkMod recovery and you didn't follow the instructions.
Q. How do I restore my phone back to factory conditions so that I don't have a voided warranty?
A. Flash the stock Bell firmware (found at my dev-host link) with Odin. OR download the stock firmware by creating an account at sammobile.com and going to the Firmware section (search for SGH-I757M); then flash it with Odin.
Q. I'm not getting LTE (4G) speeds on my phone with CM9
A. By default the ROM is set to normal GSM (3G/HSPA). You can change it under System Settings --> More --> Mobile Networks --> Network Mode --> LTE/GSM. For some providers like Rogers you may need to manually add the APN for the LTE network as well. To verify you have LTE working, you'll see the "4G" icon on the notification bar. In addition, you can run the Speed Test app to ensure you get LTE download speeds like 25Mbps instead of 4 Mbps. Of course, all this depends on whether your location has LTE towers within its vicinity.
Q. Why do my buttons light up when I get a notification?
A. By default the Backlight Notification (BLN) is turned on. You can disable it under System Settings -> Advanced -> Sensors.
Q. The NFC options can be enabled in the Settings but why doesn't Android Beam work?
A. The device seems to not have the hardware support. The same problem happens in the stock Samsung firmware. However, the online user manual mentions the use of Tags, although when I tried with both stock Samsung 2.3 and CyanogenMod 9 they couldn't read the NFC tags (at the same time I was using an Xperia S and that was able to read the same tags fine). There is discussion going on in this thread stating that we may need an NFC-enabled battery and/or special battery cover. Click here for some debug info from the phone when we turn on NFC.
Q. If I power on the device while the charger is plugged in, it does not turn on. I need to pull out and re-insert the battery to start it again.
A. This is a known issue in CyanogenMod 9 and in AOKP, not just this ROM. You could also try unplugging the phone and holding down the power button for several seconds to turn it on.
Q. How do I access internal storage and also my micro SD card?
A. Internal storage is under the folder /mnt/emmc; micro SD is under /sdcard.
Q. Does FM radio work?
A. No, this device does not have FM radio hardware support.
Q. My battery life sucks.
A. Not my fault, I did not do some geeky tweaks or overclock your phone. The device itself has a crappy battery and you'll notice the same issues in stock. Click here for some battery-saving tips.
Q. I am a newb but want to help out with ADB and/or debugging an issue, how can I?
A. Read here. Also see the following posts on how to get the sources to build the ROM.
Change Log
cm-9-20120901-UNOFFICIAL-celoxhd.zip
- Synced up with latest upstream changes to CM9 sources
cm-9-20120829-UNOFFICIAL-celoxhd.zip
- Updated with more binaries from latest Bell ICS update (netmgrd, qmiproxy, sec-ril)
- Updated build fingerprint to GLH2
- Synced up with latest upstream changes to CM9 sources
cm-9-20120828b-UNOFFICIAL-celoxhd.zip
- Updated with many new binaries from latest Bell ICS update, including for Wi-Fi, camera, DivX, GPS, audio, and RIL
- Synced up with latest upstream changes to CM9 sources
cm-9-20120828-UNOFFICIAL-celoxhd.zip
- Disabled some debugging in the kernel, should improve performance
- Synced up with latest upstream changes to CM9 sources
cm-9-20120823-UNOFFICIAL-celoxhd.zip
- Added a fix where camera photos stored on the microSD may still appear in Gallery even if deleted (merged from Skyrocket repository)
- Fixed wrong product string in USB Mass Storage mode (was being reported as SGH-I727 rather than SGH-I757M)
cm-9-20120820-UNOFFICIAL-celoxhd.zip
- first version of I757's CM9 to support the new CWM Touch Recovery
- rebuilt with latest CM9 sources
- enabled VOIP in kernel - not a complete fix but should assist when debugging with logcat and dmesg
- replaced custom capacitive button code with common Snapdragon S3 MSM8660 code (liblights): should save battery, as the capacitive button lights will now turn off after 5 seconds of touch inactivity
-- Now compatible with custom button dim level options in Settings
-- NOTE: Minor issue (also seen in other CM9 MSM8660 devices): button lights will not come on when turning device on from sleep; user must touch screen after 10 seconds to turn button lights on
cm-9-20120723-UNOFFICIAL-celoxhd.zip
- Backlight Notifications (BLN) now blink every 10 seconds instead of staying on. Should improve battery life.
cm-9-20120722-UNOFFICIAL-celoxhd.zip
- Fix for missing modelid_cfg.sh and /system mounting issue during flash
cm-9-20120721-UNOFFICIAL-celoxhd.zip
- Kernel now uses CyanogenMod version of latest kernel sources (I've also included the latest updates for overclocking, which are still under review)
- Updated mpdecision binary (handles CPU performance)
- Updated sec-ril binary (for phone functionality)
- Use Bell LTE as default APN, not AT&T
- Set in-call noise supression
- Enable Samsung SIM Toolkit functionality
- fixed capitalization issue with new DivX DRM library file; was not recognized by system in previous build
cm-9-20120718-UNOFFICIAL-celoxhd.zip
- Included latest ICS Samsung system libraries for sensors, graphics, compass, video, audio, GPS and phone
cm-9-20120717-UNOFFICIAL-celoxhd.zip
- Various minor fixes, including for HDMI output, audio and graphics
cm-9-20120713-UNOFFICIAL-celoxhd.zip
- Front camera now works
- Added SGH-I757M ICS camera binaries
- Updated to newer kernel sources (this allowed the front camera to work with the above binaries)
- Merged kernel configuration with that from SGH-I757M ICS test ROM (generally the same but CM9 version includes BLN and overclocking)
cm-9-20120707a-UNOFFICIAL-celoxhd.zip
- Fixed issue with not being able to adjust maximum CPU frequency; overclocking now works
cm-9-20120707-UNOFFICIAL-celoxhd.zip
- Fixed issue with button lights dimming and sometimes not turning back on when touched
- Added MHL support in kernel
cm-9-20120705a-UNOFFICIAL-celoxhd.zip
- Added back backlight notifications
- Fixed issue when backlight was enabled: After backlight notification came on, and then phone was turned on, the button backlight would turn off
- Fixed issue when backlight was disabled: If you screen brightness was adjusted manually, the button backlight would turn on
cm-9-20120705-UNOFFICIAL-celoxhd.zip
- Correct default CPU frequency is now set, at 1.5 GHz
- Front camera option disabled in camera app, to prevent 'stuck' front camera setting if someone switched to it
- BLN disabled
cm-9-20120703-UNOFFICIAL-celoxhd.zip
- Enhanced NFC support
- GPS Utils
- Updated Adreno drivers
- Enabled CONFIG_MMC_BLOCK_BOUNCE in kernel - may help with SD card read/write performance
cm-9-20120629-UNOFFICIAL-celoxhd.zip
- Fixed optical sensor issues (proximity and ambient light) by using libs for TAOS
cm-9-20120628a-UNOFFICIAL-celoxhd.zip
- backlight fix (first alpha version in this thread)
cm-9-20120628-UNOFFICIAL-celoxhd.zip
- Added wi-fi hotspot functionality
- Fixed NFC so no more errors show up in logcat when enabled/disabled
cm-9-20120625c-UNOFFICIAL-celoxhd.zip
- Phone functionality and SMS enabled (RIL)
- Mobile data (3G/LTE) works
cm-9-20120625b-UNOFFICIAL-celoxhd.zip
- Working rear camera
cm-9-20120625-UNOFFICIAL-celoxhd.zip
- Added kernel modules (Now working: Bluetooth, GPS, Wi-fi, vibration, MTP, USB mass storage)
June 24th build (cm-celoxhd-ota-eng.dsixda.zip)
- Initial alpha version of CM9, boots to system
Past Milestones
June 22, 2012
- Custom ICS kernel created, boots into CWM
June 12th, 2012
- Initial version of ClockworkMod Recovery released
Source code
- Link to all my source files for CM9 at GitHub for device "celoxhd". Build instructions are found in my device repo.
Other useful links
- This ROM was featured on one of Canada's top smartphone sites, Mobile Syrup
- This ROM was featured on the xda-developers news portal
- Original discussion on root methods and CM9 for SGH-I757M
- My ClockworkMod Recovery for SGH-I757M
- Rogers LTE APN settings
- Google Now from Jelly Bean
Acknowledgements
- Cyanogen
- Koush (for ClockworkMod)
- Team Chopsticks (borrowed files and help) - #teamchopsticks on IRC Freenode server
- Team Evervolv (for help, especially preludedrew on IRC) - #evervolv on IRC Freenode server
- yurilebbie on IRC channel #teamchopsticks for assistance with overclocking
- adlx.xda (help and support)
- crazy Canuck testers (you know who you are)
- Chainfire (inspiration)
- my awesome Twitter followers (continual help and encouragement)
- and last but not least my wife and daughter for not getting mad as much as they should be for the time I spend on this!!
I'm not sure if I dis something wrong but I did it the same as I had for my sgs i9000 countless times..
Please let me know thanks.
Sent from my SGH-I757M using xda app-developers app
I've watched the development for this device since day one and it's pretty remarkable how quick we went from struggling to find a root method to having CWM and now CM 9. Much thanks to dsixda!
Now down to business. I remember in the original thread someone confirmed that the light sensor was working however, running the latest revision I don't seem to be getting any response from the light sensor, I've tried a few sensor monitoring apps and the brightness wont adjust when set to "Auto Brightness". Has anyone else experienced this?
@johnnyjb that output doesn't really help. It didn't show you flashed anything. Did you get that after a reboot? Use adb to grab /tmp/recovery.log or /cache/recovery/last_log right after flash.
If you are flashing from an external SD card and getting incomplete flashes or it's stuck at boot, then you might have a corrupted SD. This happened to me.
jsr84 said:
I've watched the development for this device since day one and it's pretty remarkable how quick we went from struggling to find a root method to having CWM and now CM 9. Much thanks to dsixda!
Now down to business. I remember in the original thread someone confirmed that the light sensor was working however, running the latest revision I don't seem to be getting any response from the light sensor, I've tried a few sensor monitoring apps and the brightness wont adjust when set to "Auto Brightness". Has anyone else experienced this?
Click to expand...
Click to collapse
Set it to lowest brightness manually, then set to auto brightness. You should see adjustment to normal brightness eventually. I do notice the sensor is a bit slow on mine though.
dsixda said:
@johnnyjb that output doesn't really help. It didn't show you flashed anything. Did you get that after a reboot? Use adb to grab /tmp/recovery.log or /cache/recovery/last_log right after flash.
If you are flashing from an external SD card and getting incomplete flashes or it's stuck at boot, then you might have a corrupted SD. This happened to me.
Click to expand...
Click to collapse
The phone works but it will freeze when i do much of any thing, then reboot and some times boot loop, but it seems like it is when it is charging, very strange.
And I'll try to get the log for you here or in the morning, thanks again for all your hard long work, and thank your wife for me too.
Sent from my Transformer TF101 using xda app-developers app
dsixda said:
Set it to lowest brightness manually, then set to auto brightness. You should see adjustment to normal brightness eventually. I do notice the sensor is a bit slow on mine though.
Click to expand...
Click to collapse
I noticed a small amount of adjustment. I thought I would restore back to GB to compare the sensor using the same app and in GB the app reports the sensor as a "TAOS" sensor in CM9 its reporting the sensor as a "Sharp". In GB the sensor seems to react to different light levels were as in CM9 it wont respond to any light changes.
A screen capture from GB
And one from CM9
I know your plate has enough on in with regards to this port, but it was just something I noticed, I'm not even sure if its relevant.
Thank you for all your hard work. I am a new to this and you have made it easy for someonelike me just starting to flash custom roms. Followed your guides and now have cm9 on my phone. looks and works great so far. Once again Thank -You
jsr84 said:
I noticed a small amount of adjustment. I thought I would restore back to GB to compare the sensor using the same app and in GB the app reports the sensor as a "TAOS" sensor in CM9 its reporting the sensor as a "Sharp". In GB the sensor seems to react to different light levels were as in CM9 it wont respond to any light changes.
I know your plate has enough on in with regards to this port, but it was just something I noticed, I'm not even sure if its relevant.
Click to expand...
Click to collapse
Oh I know how to fix this, it's in the kernel. I'll get to it right away. I notice that the GB kernel has the correct model of sensor (TAOS) but I overlooked it when making the ICS kernel. Thanks a lot for the useful info.
I believe this will also fix the proximity sensor because apparently these 'optical' sensors are dual purpose.
I'll have a fixed build by the evening.
dsixda said:
Oh I know how to fix this, it's in the kernel. I'll get to it right away. I notice that the GB kernel has the correct model of sensor (TAOS) but I overlooked it when making the ICS kernel. Thanks a lot for the useful info.
I believe this will also fix the proximity sensor because apparently these 'optical' sensors are dual purpose.
I'll have a fixed build by the evening.
Click to expand...
Click to collapse
Good stuff!! It will probably fix the black screen at the end of a call, the sgs3 has an aokp rom, I'm gonna give that ago at porting, it's like the ultimate customizable rom even more than cm9. Figure if more of us can figure out to do what you do dsixda, it'll give you a much needed break
Sent from my SGH-I757M using xda premium
hope it works for e120l
Thanks for all of your hard work on this and the other ROM!
I am (still) getting errors when flashing to my phone. I get this when trying to flash:
Code:
assert failed: getprop("ro.product.device") == "SGH-I757M" ||
getprop("ro.build.product") == "SGH-I757M" ||
getprop("ro.product.device") == SGH-I757" ||
getprop("rp.build.product") == "SGH-I757M" ||
getprop("ro.product.device") == "celoxhd" ||
getprop("ro.build.product") == "celdoxhd"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Here's what I've done:
Wiped data, cache, dalvik cache for each step below
Tried to install from SD card
Tried to install from internal storage
Tried renaming to update.zip
Tried flashing the stock ROM and upgrading from there
Tried a new download of the .zip
Let me know if any other information would be helpful.
assortiment said:
hope it works for e120l
Click to expand...
Click to collapse
See the big bolded warning on post #1.
ZarboktheMunificent said:
Thanks for all of your hard work on this and the other ROM!
I am (still) getting errors when flashing to my phone. I get this when trying to flash:
Code:
assert failed: getprop("ro.product.device") == "SGH-I757M" ||
getprop("ro.build.product") == "SGH-I757M" ||
getprop("ro.product.device") == SGH-I757" ||
getprop("rp.build.product") == "SGH-I757M" ||
getprop("ro.product.device") == "celoxhd" ||
getprop("ro.build.product") == "celdoxhd"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted.
[/LIST]
Let me know if any other information would be helpful.
Click to expand...
Click to collapse
You missed Step 3 in installation instructions?
ZarboktheMunificent said:
Thanks for all of your hard work on this and the other ROM!
I am (still) getting errors when flashing to my phone. I get this when trying to flash:
Code:
assert failed: getprop("ro.product.device") == "SGH-I757M" ||
getprop("ro.build.product") == "SGH-I757M" ||
getprop("ro.product.device") == SGH-I757" ||
getprop("rp.build.product") == "SGH-I757M" ||
getprop("ro.product.device") == "celoxhd" ||
getprop("ro.build.product") == "celdoxhd"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Here's what I've done:
Wiped data, cache, dalvik cache for each step below
Tried to install from SD card
Tried to install from internal storage
Tried renaming to update.zip
Tried flashing the stock ROM and upgrading from there
Tried a new download of the .zip
Let me know if any other information would be helpful.
Click to expand...
Click to collapse
What version of CWM are you using?
Well that's embarrassing. That was the issue. I thought I had flashed the newest one the other day but it turns out I grabbed a previous download by mistake.
I noticed that both under Performance settings and using some overclocking apps on the market that the maximum CPU frequency is set to 1836 MHz, and cannot be changed(always reverts). Unless I've been misinformed isn't the default maximum CPU frequency 1.5GHz? If so isn't it a bit haphazard to have it set so high above the normal by default?
Cr15py said:
I noticed that both under Performance settings and using some overclocking apps on the market that the maximum CPU frequency is set to 1836 MHz, and cannot be changed(always reverts). Unless I've been misinformed isn't the default maximum CPU frequency 1.5GHz? If so isn't it a bit haphazard to have it set so high above the normal by default?
Click to expand...
Click to collapse
I noticed that too and I wouldn't do that intentionally. In fact I don't even know how to overclock in the kernel! Not a big issue IMO, but I'll look into it when the big issues have been fixed. Thanks
Related
***ATTENTION IF YOU ARE COMING FROM A 4349+ STOCK ROM or MOD based off that PLEASE VISIT THE FOLLOWING LINK TO DOWNGRADE YOUR BOOTLOADER AND TNT VERSION BEFORE FLASHING CWM AND THIS OR ANY OTHER ROM****
http://forum.xda-developers.com/showthread.php?t=1036956
LINK TO NEWEST DEVELOPMENT: VEGAn-TAB GINGEREDITION: http://forum.xda-developers.com/showthread.php?t=1031250
VEGAn 1.00 beta 5.1.1 supplement - Thanks Roebeet for staying on top of it!
Link: http://www.mediafire.com/?jhq1cnu5wgkg3j5
md5sum: 7f3920a3ef2dabf264bfc8550d8f6d00
List of fixes / enhancements in this supplement:
- Maps 5.1 with the rotation fix
- Market 2.2.11
- Updated drivers that should bump up Quadrant slightly, and significantly improves Nenamark scores
- Frame rate change from 50 to 60
- Replaced the Froyo keyboard with the Gingerbread keyboard
- Added Adam Sniffer app, and their keyboard as an option
Quick instructions: This is a supplement, not a full firmware. You would run this like any other update.zip, but since the changes are small you shouldn't have to wipe data. You'd want beta 5.1 as your baseline, before running this, download link is further below for the full install of beta 5.1.
I know that the VEGAn users probably haven't been "feeling the love" the last few weeks, so we wanted to at least bump you up to some of the latest changes ported to TNTL. I have been plugging away hard on CM7 and VEGAn-TAB GingerEdition and rothnic's expertise with a lot of the these enhancements are the reason why they exist right now. The Nenamark bump actually originated from our Adam testing, believe it or not.
As Per usual USE THIS ROM AT YOUR OWN RISK. We highly recommend clockworkmod recovery as a pre-req. We are only testing for cwm users.
I would also recommend a full data wipe between updates, at least for now when we reach STABLE RELEASE stage this may not be always necessary. There is a great tool out there you can use if you don't know about it already called Titanium Backup it is on the market and there is a free version. It allows you to backup/restore all your apps and even save/restore data for those apps... the only caveat I will say is do not restore any system apps (ie. apps preloaded with our roms) this can cause issues.
****The First Boot after installing BETA 5.1 will take a few minutes to catch up and will feel "laggy" this depends on how much media you have on your device for it to scan in the first time****
**If you are having issues with the new market telling you you don't have enough space to download then your SD Partitions are incorrect and need fixed** -Boot Clockworkmod, select advanded, then partition SD, 2048 for first option, and 0 for second. process will take ~10 mins ******WARNING THIS WILL DELETE EVERYTING ON SDCARD (internal) MAKE A BACKUP!!!!******
Now that we are nearing a STABLE Release here are some new links you may not be aware of:
Build URL: http://vegantab.gojimi.com/
Downloads section: http://vegantab.gojimi.com/downloads
ON TO THE ROM:
***UPDATE***
1.0.0 Beta5.1 Link: http://vegantab.gojimi.com/download/gtab.VEGAn.1.00.beta5.1.user.final.zip
md5sum: a01171d77f25444088ecc884c793d105
This is an update.zip formatted file. You'd run this like you'd run any other update.zip file.
-----------------------------------------------
ONLY DO THIS IF YOU DO NOT CARE ABOUT G-SENSOR BEING RIGHT FOR MOST G-SENSOR GAMES & WOULD RATHER HAVE MOUSE SUPPORT BACK -- *****PATCH TO REMOVE G-SENSOR FIX AND RESTORE MOUSE SUPPORT***** - ONLY INSTALL THIS AFTER BETA 5: http://vegantab.gojimi.com/download/patch.VEGAn.BETA5.remove.Gsensor.zip **Flash this like you do the roms in clockwork**
This is a collaboration between myself, Roebeet, and Rothnic - The G-TabDevs Team.
BETA 5 changes:
* NEW KERNEL **Thank you Rothnic** We have compiled alot of new features in to this with more on it’s way at some point.
* LAG on WAKE FIX! woo hoo! no more laggy tablet after sleeping.
* CIFS support (allows mounting shared folders over a network) – search CIFS in the android market for apps
* NTFS support (this gives us the ability to mount drives formatted NTFS which is popular on Windows machines…. Larger File Support)
* Ethernet on DOCK Support (This will only work right now if the device is booted while connected to the dock to activate the port)
* ***UPDATED EVEN BETTER****G-Sensor Fix (this has been long awaited by many! Fixes most games that use the g-sensor for controls, etc.) **this is a DIRTY FIX but it works… only issue is it does mess up mouse usage… so if you are a mouse user and don’t care about the g-sensor being right for games there is a patch below that you can apply ***AFTER*** you install BETA 5.
* REBOOT OPTION has now been added to the power menu. Remember that popup menu is a scrollable menu so if you don’t see it all use your finger and scroll on down!
* I increased the DELAY for the LONGPRESS Power button to bring up the menu… it is now a full second. This has dramatically decreased the number of time the power menu has accidentally popped up when trying to wake the device.
* Added the Tablet Compatible Stock Calendar that I dropped on you guys at Christmas on the Website.
No Major theme changes, nor some of the other fixes that I have been having issues with. The next release should include those. This is the LAST BETA I believe. The next release will take some time so settle in for a bit while we work on Release Candidate 1.
-------------------------------------------------------------------
Benefits to us
- Soft buttons, like TnT. But no TnT UI layer getting in our way. So, for example, keyboard replacements should work.
- Just as fast as the new builds we have if not FASTER.
- Vega build has a bootup script where we can install user-based apks, after a data wipe. So, for example, Flash is now added to the build.
- Vega firmware development is probably more active than the official TnT development, at least from the little I've seen so far (though TnT have been fairly active lately).
Known issues
- Videos are not being automatically scanned on the EXTERNAL SDCARD.
*****FIXED**** Weird orange bar is showing up in the stock Calendar app *****FIXED****
- The newest Market apk seems to have issues with any device that's been re-partitioned outside of the default of 2048. The "fix" is to re-partition your SD back to the default of 2048, in clockworkmod. Thanks to proengin for informing us of this.
Changelog
- (a2) We are using alpha1 as our "base" image, and then a modular format on top of that. So, alpha2 is a full update.zip package.
- (a2) VOLD should be fixed using a hack. 30 seconds after bootup, SDCARD2 should start working. Or, it may not work. It's an alpha.
- (a2) Vega user apk script has been added, which is supposed to add Flash on a newly wiped system. But it's spotty at best.
- (a2) Camera should be fixed.
- (a2) We're deleting some of the unneeded system apps like Twitter, Facebook, the Htc stuff in gapps and talkback. You can always add these back via the Market. The reason is to keep the image a little cleaner.
- (a2) Audio fix added.
- (a3) Added changes to the framework for smaller status bar and VEGAn boot screen.
- (a3) Added Gingerbread keyboard.
- (b1) SSL bug fixed. Also, added the latest YouTube and Gmail apps. Removed the user apk script for now, as it's really buggy.
- (b2) VOLD post-boot replaced with a mount commend. Should be more stable and might fix the disappearing apps, I hope. New Gmail, adhoc wireless support added, adfree hosts file removed (get "adfree android" app in the market to get it back), removed the Phone apks which should improve battery life.
- (b3) Mounting issues should be completely corrected, audio issues are corrected, new rothnic theme added, new Gmail and Voice apps, new Settings app with advanced Wifi (and policy is set to "never sleep" by default).
- (b4) A New Cleaner Base System Image with the addition of files from new Advent Vega Release (we can finally get rid of the hacked together Image That I originally created for VEGAn)
- (b4) New Kernel (from latest unreleased TNT Update kernel version #15)
- (b4) New Boot Logo(replaces G-Tablet on white background)
- (b4) New VOLD Binary and MediaProvider(allows media to be seen from External SD Card as well as internal)(videos are not being automatically found on SDCARD2 ATM I am working on that)
- (b4) Settings app no longer has Call Settings option or mobile networks as it is not a phone
- (b4) New Market (We have got it showing even more apps... but still not all. Still need to do the market hack.)
- (b4) Some Graphics and Performance Improvements reduces video tearing issue among other improvements (G-TabDevs Performance Pack)
- (b4) New Music Player(pulled the one from CM6.1 and got it running on VEGAn)
- (b4) framework laid for bluetooth HID(not sure if it is fully functional yet please let us know if it work for you)
- (b4) laid the framework for POSSIBLE OPENVPN support(not fully functional yet sure if I can get it to work yet)
- (b4) New Theme Improvements - Switched to a more Cyan color highlights (the previous green may be available as a small update at a later date.
- (b4) Flash now auto installs on first boot up usually after about 15 secs so the tablet can finish booting
1.0.0 Beta 5:
{
"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"
}
------------------------------------------------------------------
Archives:
1.0.0 Beta3 Link: http://www.mediafire.com/?tt3n3njojetnscx
Alternate link: http://www.megaupload.com/?d=3KJ799TZ
md5sum: fea915609ab56aa233fabcfff3bcc2a3
1.0.0 Beta2 Link: http://www.mediafire.com/?c9a1c11zz1wgza9
Alternate link: http://www.megaupload.com/?d=MKKNTZP1
md5sum: 1b16d0cf7f02702a6796914195d8339b
1.0.0 Beta1 Link: http://www.mediafire.com/?5hr09gj53ut1208
Alternate link: http://www.megaupload.com/?d=Y9NR34AD
md5sum: 2906ed4fd5ae4fc1954b7b5e766f1507
1.0.0 Alpha3 Link: http://www.mediafire.com/?tzhc7vtstdl128x
Alternate link: http://www.megaupload.com/?d=9SPCOMPY
md5sum: 148a7bf52458cbedc9d859e91281a6c8
1.0.0 Alpha2 Link: http://www.mediafire.com/?bdurosaclrp4r3i
Alternate link: http://www.megaupload.com/?d=H264QQRH
md5sum: 2541fccfb01fb8b398fc38beaa5b3355
1.0.0 Alpha1 : http://forum.xda-developers.com/show...5&postcount=57
Stuck thread
I hope you have a lot of bandwidth on that server, gojimi, because you're about to get hammered. Might want to consider uploading through multiupload.com, the service roebeet's been using.
Downloading and getting ready to flash here, btw.
Downloading now! thanks for all the fast updates!!
Thanks for the hard work!!!!!! Downloading now
Ahh! didnot bring Gtab to work !
Will D/L after work.
Thank you Santa Clause ('s)
LOL.
And I just got done loading up the new latest VS ROM. It's much better, but it still ain't Vegan.
Oh well, I got no problem swapping out ROMS. Thanks for the hard work guys.
Thank You!!Just updated then did the TnT Kb + Live WP + Gapps..Formatted SD 2048 / 0 ..Did Market Fix and Im In....
Love the new Image instead of the gtab image.....
Can't decide on the bios or this boot logo..
Quadrant 2463
Thanks Again!!
looking sexy downloading now!!!
Is there any way to have the Home button bring up the launcher instead of the Clock app? Or am I experiencing a unique issue?
HID Testing
How do I enable the bluetooth HID? I am trying to connect to my keyboard, but I don't see any option for it?
It does bring up the generic message to try "0000" or "1234" however it did not work, or do I mis understand? is this something I need to do at the command line hidd --connect etc?
Everything else seems to work great, at least what I have tested.
Thanks !
Wiped everything before install. Runs well, but noticed a few issues.
First, my power button stopped putting the device to sleep. I could hold and get the shutdown menu. Reboot fixed this.
Second, if you use the lock screen feature and try to log in before the device finishes starting up (after a power on or reboot) the touchscreen becomes unresponsive. You have to hold down the power button for 10 seconds to force shutdown. Noticed this with beta 3 as well.
Third, hacked TSCalibration doesn't appear to be proloaded to find INI file on root of /sdcard instead of /sdcard2.
Seems great other than that!
So far so good! Wiped data, cache, and dalvik then installed. Got TB and restored my Pro license, then selected apps with data (no system data) to restore. Entered in Gmail account, tested Market. Applied Swype install/hack and rebooted. Running smooth, Quadrant in the 2400+ range.
The only problem I have is I can't sync my Facebook account under Accounts. I don't need this per se, but I'd like to have them.
-=Sent from my Droid 2 (Fission 2.4.3) using Tapatalk=-
schauerd said:
How do I enable the bluetooth HID? I am trying to connect to my keyboard, but I don't see any option for it?
It does bring up the generic message to try "0000" or "1234" however it did not work, or do I mis understand? is this something I need to do at the command line hidd --connect etc?
Everything else seems to work great, at least what I have tested.
Thanks !
Click to expand...
Click to collapse
I wasn't totally sure I had bluetooth HID licked this round or not... I don't have a bluetooth keyboard to test with... looks like we are part way there maybe by the next build we'll have a better understanding of what needs done.
ehunyadi said:
Is there any way to have the Home button bring up the launcher instead of the Clock app? Or am I experiencing a unique issue?
Click to expand...
Click to collapse
Ehunyadi: you are one of only two people experiencing this issue. I would like to know what the model number of your tablet is. On the back starts with UPC3*** etc. It seems this may be linked to a specific run of devices but we are not sure. Let me know so I can track down the root cause of this.
gojimi said:
Ehunyadi: you are one of only two people experiencing this issue. I would like to know what the model number of your tablet is. On the back starts with UPC3*** etc. It seems this may be linked to a specific run of devices but we are not sure. Let me know so I can track down the root cause of this.
Click to expand...
Click to collapse
Model: UPC300-2.2
ehunyadi said:
Model: UPC300-2.2
Click to expand...
Click to collapse
I have the same model number and my home buttons work fine.
Thanks for the response !
ehunyadi said:
Model: UPC300-2.2
Click to expand...
Click to collapse
Now that's weird... I guess it is not model specific then... It seems like something is telling it the tablet is docked when it clearly is not. Just to clarify did you do a full data/cache wipe in Clockwork Mod after installing BETA 4?
Just trying to run through the troubleshoot list.
Was loudness increased? Seems louder. Also seems a tad quicker.
Now, I am no great Android developer... I'm just someone who is technically inclined to piece together several different mods and tweaks from different sources... and I do it because I love getting the best out of my GTablet...
I pretty sure everyone reading this agrees that CyanogenMod is the best after-market AOSP-based community initiative ROM available... it's got dozens of new features, fixes, modifications and enhancements over pure AOSP Android... And thanks to the efforts of the entire CyanogenMod team, especially bekit, pershoot & mad-murdock, we have CyanogenMod for our GTablets...
I keep experimenting with the latest CyanogenMod build and the tonnes of other contributions by various people in the community (XDA, TabletRoms, SlateDroid, etc.)... trying to mix and match and find a combination which will give me the best of both worlds...
I started this off as a personal initiative... and decided to share it with the community... but this effort of merging various community contributions into CyanogenMod ROMs takes time and quite often needs thorough testing, it is not practical for me to release updates very frequently. But every so often, when I see commits in CyanogenMod or contributions in the community which would be nice to repack and share with the community, I will hope on board and create a new release.
Please read through the post thoroughy, especially the instructions, troubleshooting and known issues section and familarise yourself with NVFlash recovery.
Credit for most of the amazing features of this ROM goes to the CyanogenMod team (especially pershoot, bekit, mad-murdock) and contributors... and the various other members of the community who share their brilliant mods and tweaks...
Big thanks to dev-host.org team for hosting the files with no bandwidth restrictions...
LATEST RELEASE | CYANOGENMOD7.2.0-RC0-BUILD98-REPACK | ANDROID 2.3.7
REPACK DOWNLOAD [Bootloader 1.1]
MD5Sum = 9a038efaa6acd207868696c657a34cb4
REPACK DOWNLOAD [Bootloader 1.2]
MD5Sum = cd2041dd0fd2d8e2dbda9adb2fbe3025
FIX FOR MOBILE SIGNAL ICON IN STATUS BAR [Both bootloaders]
MD5Sum = 1fc03c6f05a8b9da43d4966c6ad42549
OFFICIAL CHANGELOG
NIGHTLIES CHANGELOG
REPACK CHANGELOG:
Code:
1. All features of the official CM7.2.0-RC0 Build 98 [credits to CM team]
2. Android Gingerbread 2.3.7 along with all 2.3.7 GWK74 Google Apps [credits to Google]
3. Latest Android Market 3.3.12 [credits to Google]
4. Superuser 3.0.7 [credits to ChainsDD]
5. QuickOffice Tablet from Notion Ink Adam
6. Google Music 4.0.9 with Google Music cloud sync [credits to Google]
7. Demotivators Protips (hilarious de-motivational sayings) [credits to david1171]
8. Updated the build fingerprint to 2.3.6 GRK39F [based on the latest Nexus One OTA]
9. Changed display density to 120 (was 160) which means more real estate
10. Uses latest libs, jars & other proprietary from the latest 1.2-5274 TnT ROM (BL1.2 release only) [credits to TnT team]
11. Separate releases for bootloaders 1.1 & 1.2
12. Switchable internal & external storage mount points [credits to CM team]
13. Kernel 2.6.32.48 – OC-UV-VFP_FP (up to 1.400GHz) [credits to pershoot]
14. Several stagefright (Android Media Framework) fixes and tweaks to improve audio and video decoding [credits to CM team]
15. Latest stock camera with all CM tweaks and fixes and no pixelated still photographs [credits to CM team]
16. New GoogleTalk with voice & video (only one way video, GTablet video broken) [credits to britoso, B3ATTY]
17. Fixed assert checks in update script for Clockwork recovery for BL 1.1 & 1.2
18. Removed ROMManager since it does not play nice with the GTablet
19. Hand-picked tweaks for performance, battery life & internet from a collection by knzo [credits to knzo]
20. Tweaked minfree (low memory killer) for performance improvement
21. Increased internal & external (if present) storage read cache to 2048 to improve storage access speed
22. Hardware decoding for MP4 h264 Baseline videos upto 720p [credits to CM team]
23. Pandora and other internet radio application playback no more slow [credits to CM team]
24. Browser default bookmarks modified to include GTablet specific bookmarks
25. Full working Android Market with tablet recognisation (no Market fixes needed)
INSTALLATION INSTRUCTIONS:
1. Download the ROM from the appropriate bootloader.
2. Verify the MD5Sum of the downloaded ROM.
3. Clear cache & dalvik cache using Clockwork recovery if you were not using a CM7 2.3.7 ROM prior to flashing this
4. Flash using Clockwork recovery.
RECOMMENDED:
1. If you are using the 1.2 bootloader version, use the latest 1.2 bootloader from the 1.2-5274 ROM.
2. Wipe data/factory reset is recommended if you were not using a CM7 2.3.7 ROM prior to flashing this.
3. Since most newer ROMs are based on the 1.2 bootloader, it is recommended that you upgrade to the 1.2-5274 ROM so that you have more freedom to switch to other newer ROMs.
ADD-ONS:
1. Extra kernel modules for pershoot's kernel 2.6.32.48 (lib-2632.48_gb.tar.gz) [For advanced users only]
2. Possible SOD (sleep of death) fixes
TIPS & TWEAKS:
1. You can enable and disable the lockscreen from Settings -> CyanogenMod settings -> Tablet tweaks -> Disable lockscreen.
2. You can switch the mount points of the internal & external memory. You can mount the internal memory as /mnt/sdcard or as /mnt/emmc. Go to Settings -> CyanogenMod settings -> Application -> Use internal storage. This is not part of the CyanogenMod-7.1.0-RC1 build.
3. Since hardware decoding of videos is not working, use MX Video Player or Mobo Player which have software rendering for videos. I recommend one of these players since they have ARMv7 (Tegra) optimised software codecs (FFMPEG).
4. If you want to change the LCD density, download & install PropEditor. Click the "Backup" button to create a backup in case you need to revert back. Then click the "Open" button and in the file manager which opens, tap ".." till you reach the system root. Then tap "system" and the tap "build.prop" to open the editor. Look for "ro.sf.lcd.density" and tap it to change the value. Press the "Menu" key and tap "Save". Reboot.
5. Increasing the DalvikVM memory size will improve performance of the bigger high-graphics Tegra games. Go to Settings -> CyanogenMod settings -> Performance -> VM heap size and set it as 64m.
6. To overclock or underclock your device, go to Settings -> CyanogenMod settings -> Performance -> CPU settings and set the Min CPU frequency and Max CPU frequency to a value of your choice. Click Set on boot to make the frequency setting persistent after reboot.
7. If the Clock app opens every time you press the Home button, it's because Android thinks you GTablet is docked (I don't know why yet!). Install Dock No-Op to fix it.
8. If you wish to use Market Enabler, use the one by For2w. It has many more providers to fake and works properly with the Android Marker 3.x.
KNOWN ISSUES:
1. Due to lack of official drivers and/or OpenGL issues, the video camera does not work and stagefright (media framework) FCs.
2. Due to lack of official drivers & codecs, hardware decoding for videos does not work for most video formats other than MP4. Use a video player with software rendering.
3. If audio from the loudspeaker suddenly stops, plug in a headset and then unplug it.
4. Since the video camera does not work, any video apps which use the stock video camera will not work. Users have reported Fring & Oovoo video chat works.
5. GoogleTalk and Skype now support ARMv7 without neon. This version of GoogleTalk is included in this ROM. But due to lack of official drivers and/or OpenGL issues, both GoogleTalk and Skype cannot broadcast video from the GTablet. The reciepent's video is visible on the GTablet.
6. If you have a problem downloading applications from the Android Market and all/most apps show as "not available for device", try wiping Market data and cache and rebooting. If that does not work, edit build.prop and change the resolution 160 DPI and wipe Market data and cache and reboot.
7. Some user may face SODs (Sleep of Death) wherein the device does not wake after sleep until a hard-reboot. Some possible workarounds are
a. Enabling the lockscreen (see Tips & Tweaks)
b. Setting the device to wake using volume keys (CyanogenMod setting -> Input -> Volume rocker wake)
c. Setting the Min CPU frequency to 312 MHz or 456 MHz (see Tips & Tweaks)
d. Visit this thread for more solutions
8. Google Maps 6.x force closes due to openGL issues with Gingerbread on the GTablet. Use Google Maps 5.x.
TROUBLESHOOTING STEPS:
1. Try a data/factory reset
2. Use ClockworkMod recovery and try a data/factory reset and format the boot and system partitions
3. Use ClockworkMod recovery and partition the internal SD card as 2048MB ext, 0MB swap, remaining FAT32
4. nvFlash to the stock image
DISCLAIMER:
While this has been branded a "stable" release, do note that it is not 100% perfect. I will do my best to help you out if you have any problems, but I take no responsibility if you land up with a brick. Much of the actual hard-work behind the functionality of this ROM belongs to the various developers and teams credited in the changelogs above. Throw a nice thanks to them for their hard work.
ARCHIVED RELEASE:
1. CYANOGENMOD7.1.0.1-REPACK | ANDROID 2.3.7
2. CYANOGENMOD7.1-RC-Build52-REPACK | ANDROID 2.3.7
3. CYANOGENMOD7.1-RC-Build21-REPACK | ANDROID 2.3.5
4. CYANOGENMOD-7.1.0-RC1 | ANDROID 2.3.4
More details and download links for archived releases
I got installation of 7.1.0 RC "aborted"
Same here using 1.2 BL & CW.
The usual asserts error, expecting HARMONY as system type. Also, are those the right GAPPS, or should it be gapps-gb-20110613?
MC
Disabling assert doesn't get this installed. Was really hoping for an rc1 for 1.2...
MicroChip said:
The usual asserts error, expecting HARMONY as system type. Also, are those the right GAPPS, or should it be gapps-gb-20110613?
MC
Click to expand...
Click to collapse
This is the 2.3.4 Google Apps with the new Google Talk with Voice & Video... the one you noted is the 2.3.3 Google Apps... this was created using the official GRJ22 firmware...
And for those having problems with the asserts, try removing the assert line (the line mentioned below) from the update-script in the ROM zip...
Code:
assert(getprop("ro.product.device") == "harmony" || getprop("ro.build.product") == "harmony" || getprop("ro.product.board") == "harmony" ||
getprop("ro.product.device") == "smb_a1002" || getprop("ro.build.product") == "smb_a1002" || getprop("ro.product.board") == "smb_a1002");
I've managed to set up CM7.1 RC1 on both the BL1.1 & BL1.2 after removing the above line.
craigacgomez said:
And for those having problems with the asserts, try removing the assert line (the line mentioned below) from the update-script in the ROM zip...
Code:
assert(getprop("ro.product.device") == "harmony" || getprop("ro.build.product") == "harmony" || getprop("ro.product.board") == "harmony" ||
getprop("ro.product.device") == "smb_a1002" || getprop("ro.build.product") == "smb_a1002" || getprop("ro.product.board") == "smb_a1002");
I've managed to set up CM7.1 RC1 on both the BL1.1 & BL1.2 after removing the above line.
Click to expand...
Click to collapse
I didn't try it but have in the past and I'm pretty sure it doesn't work because changing that line makes the rom fail md5 test if I recall?
Check with zyhong, he's packaged 1.1 CM for 1.2 bl successfully. Wish somebody would write up how to do it, I'd do it myself.
Thanks!
MC
MicroChip said:
The usual asserts error, expecting HARMONY as
system type.
Click to expand...
Click to collapse
+1 for me.
craigacgomez said:
And for those having problems with the asserts, try removing the assert line (the line mentioned below) from the update-script in the ROM zip...
Code:
assert(getprop("ro.product.device") == "harmony" || getprop("ro.build.product") == "harmony" || getprop("ro.product.board") == "harmony" ||
getprop("ro.product.device") == "smb_a1002" || getprop("ro.build.product") == "smb_a1002" || getprop("ro.product.board") == "smb_a1002");
I've managed to set up CM7.1 RC1 on both the BL1.1 & BL1.2 after removing the above line.
Click to expand...
Click to collapse
This results in an immediate "Installation Aborted" error for me - sans the "assert failed" notice.
First, Thanks for your efforts, but just like the several other threads created for the same topic (with its slight variations) this need to be moved to General section.
The development section is kept for those ROMs developed by the XDA contributors.
craigacgomez said:
This is the 2.3.4 Google Apps with the new Google Talk with Voice & Video... the one you noted is the 2.3.3 Google Apps... this was created using the official GRJ22 firmware...
Click to expand...
Click to collapse
Strange, I thought it was 2.3.4 too.
20110613: This package is designed for Android 2.3.4, and will not work on 2.3.3. It contains all of the applications updated for 2.3.4, but does not include the new Google Talk with video chat due to there being no compatible library available for non-ARM7 and non-neon board devices, from Google or another OEM. This package should work on all 2.3.4 ROMs, and has the latest Android Market update in it, which includes in-app purchase support. This package is listed in the above table, ROM Manager, and latest/7/universal. It should be used with ROMs such as CyanogenMod 7.1.0 (though at the time that I'm updating this, 20110307 is still listed in the ROM Manager manifest for the CyanogenMod Nightlies).
Click to expand...
Click to collapse
That said, does video chat work on your tablet ?!
MicroChip said:
I didn't try it but have in the past and I'm pretty sure it doesn't work because changing that line makes the rom fail md5 test if I recall?
Check with zyhong, he's packaged 1.1 CM for 1.2 bl successfully. Wish somebody would write up how to do it, I'd do it myself.
Thanks!
MC
Click to expand...
Click to collapse
I have put an instruction on the second post of my GB for BL1.2 post, and someone in slatedroid have successfully build the cm7.1 RC1, which is confirmed by some users that works well. I have put a link for that build on my post as well. Hope this help.
I think I know the answer, but I'm no expert - does CM7.1 for the G-tab have hardware acceleration? If no, I see reports of Flash working so do problems with HD video still exist?
I'm considering moving from Vegan (Froyo) to see if it clears up a couple minor annoyances but I need a (mostly) fully functional tablet. That being said, I use the MoboPlayer so I can soft-decode when needed.
Thanks!
zyhong said:
I have put an instruction on the second post of my GB for BL1.2 post, and someone in slatedroid have successfully build the cm7.1 RC1, which is confirmed by some users that works well. I have put a link for that build on my post as well. Hope this help.
Click to expand...
Click to collapse
I was able to find, and able to get 7.1RC1 on 1.2 bootloader.. Thank you.
For those looking for a flashable update for the 1.2 bootloader:
CM 7.1.0 RC1 for 1.2
md5: 3c22f7acc3dd9f82bd3e5a64915d27d4
Hope it helps.
Edit: Btw, this includes the pershoot kernel.
Hmm things worked fine until I added the pershoot kernel, then I lost wifi
I tried CM 7.1.0 RC1 for 1.2, I'm just sitting at the birds screen.
Did you do a factory reset before rebooting? It fixes the bootloop usually.
Yes I did and it just sat at the birds but will try again. I can't seem to get Clockwork to install alone either
I will re-create the CM7.1 RC 1 for both bootloader versions in a day or two so that it will work with any bootloader and even the stock recoveries.
I am using CWR 3.0.2.8 and used install zip from sdcard to flash the rom. Did you flash it that way?
Disclaimer: I am not responsible for any damage (including, but not limited to, loss of data, non-functional device etc.) which may occur to your device from following the directions (or from any failure to follow the directions) found on this post. Use (and flash) at your own risk.
Credits go to genokolar for actually porting the U8860 2.3.6 firmware to the U8800Pro. This builds upon his port.
You may find his port announcement here, and you can download it from here. Thanks to user Skyline111 for the mirror.
Thanks also go to birdyi, who ported the U8860 2.3.6 firmware to the U8860. His port contained some brilliant things such as CarrierIQ framework removal.
--
This is a 2.3.6 ROM for the U8800Pro based on the U8860 B866 ROM. 2.3.6, naturally, brings a slightly newer version of Gingerbread compared to our 2.3.5 with B540. While I know it's all about CM9 (ICS), MIUI and so on these days, I'm a fan of stock (in the Huawei sense of the term) Gingerbread.
Features (or limitations depending on what you think of some of the following entries) of this ROM:
Rooted (adb also runs as root, too)
(Huawei) DLNA
(Huawei) A task manager that shows open applications with pictures (launching it when pressing Home has disabled in this modification because I found the Recent menu saves more time)
(Huawei) Security Guard, a way of hiding text messages, I think
(Huawei) Traffic Manager – a data counter
(Huawei) Wi-Fi WPS support
(Genokolar) FPS unlocked by default (configurable in enhanced.conf)
(Genokolar) ZRAM (Compcache) enabled
(Genokolar) Changed the autorun.iso path to the image partition so that formatting /data from CWM does not leave you with an empty CD-ROM drive when you plug the phone into a computer
bugreports service turned off entirely so that pressing the volume up button quickly after you've pressed volume down does not leave you with a few seconds' delay and a bugreports folder on your memory card
BusyBox from CM7
Android’s toolbox (poor coreutils replacement; more barebones than BusyBox) has its full set of links installed in /system/bin, so you use Android’s native chmod etc. tools. Why? To match the stock B512 firmware and to ensure developers testing on the U8800Pro correctly hardcode “busybox” in their root programs if needed
Optional lazy CPUfreq governor
Default language and region changed from Chinese – China to English – United Kingdom
Added in boombuler’s AppWidgetPicker
CM7’s Pacman added in to remind you to install Google Apps after adding an account with the Setup Wizard (make sure GApps is installed!)
VoiceDialler.apk added in from B512 firmware (although, to be honest, the microphone quality on my phone is awful…)
Bash shell, fix_permissions script, iwmulticall, MMS.apk, tcpdump and gdbserver and additional ringtones etc. from CyanogenMod (20120107-cm-7.1.0-u8800pro-Geno-en.zip) added in
Phone model changed to Desire HD, so Gameloft games can be bought. This may cause licensing problems with bought Market applications so be careful. (Although, I must admit that giving money to a company that doesn't support our phone seems counter-intuitive.)
Shutdown vibration reduced from 500ms to 100ms because I hate it (especially at night) but understand its usefulness in determining the answer to the question “Has the phone gone off yet?”
Huawei’s god-awful Low Battery notification replaced with a nicer one from CyanogenMod
Widgets actually restore themselves after a reboot! This was fixed by me replacing 2.3.6's PackageManager service with Huawei's 2.3.5 one.
MyCalendar widget from birdyi's port and MyEmail from B512 added in
Fixed proximity sensor dying if the light sensor was on, too.
Stripped down enhanced.conf - only swappiness, VSync and ZRAM settings available. I don't like /system/log.txt being created every time my phone boots and I think using a tool in Android like, say, No-frills CPU Control is the better place to set the frequency. SetXperia has support for setting the phone's CPU voltage.
More languages selectable from the Setup Wizard than just English (US) and Chinese.
Flash Player removed for copyright reasons. You can install it from the Market
Notepad and Richpad removed
Droid Sans Fallback supports more character ranges
Toolbox correctly has "Wi-Fi" instead of "WLAN"
Misc. kernel modules, like in B512, included
But I like the BusyBox tools and want to use them without having to prefix BusyBox everytime!
Just run the bash shell; BusyBox versions of cat, chmod, chown, df, insmod, ln, lsmod, mkdir, mount, mv, rm, rmdir, rmmod, umount, sleep, kill, and ifconfig will become the default while you’re using the bash shell (also nicer, BTW: you get tab-completion, for one) thanks to the CyanogenMod team.
Attempts to remove Carrier IQ. Huawei *do* include Carrier IQ in their firmware.
I’ve done the following to attempt to remove it the best I can:
Edited boot.img to not start Carrier IQ services
Removed Carrier IQ libraries from /system/lib and CiQ binaries from /system/bin
Added lines to build.prop to disable CarrierIQ, taken from the framework.jar file itself.
birdyi has also modified framework.jar to stop the CarrierIQ objects from being instantiated.
Ideally the best way to be Huawei-free is to use CyanogenMod.
I've removed the Cloud+ apps because of this. I've left some Huawei apps in, but I strongly recommend you install PDroid (the patcher works fine with this ROM) and block the more concerning permissions of Huawei system apps.
Kernel changes
Since the kernel genokolar provided with his port had a problem when a program used the light and proximity sensor at the same time – the proximity sensor would die out until the next restart – I took it upon myself to rebuild the kernel available from his github repository with the config from his latest kernel. After comparing his kernel to the source Huawei put out, I could see no code changes that would cause the proximity sensor to die out. Since I was rebuilding the kernel, I thought I’d make a few changes:
Add in the Lazy CPU governor by Ezekeel
Update a patch by stockwell to disable keypad lights (echo 1 > /sys/module/leds_msm_pmic/parameters/disable_button_leds) - use ButtonLock to control
Reverse genokolar’s decision to always allow NV logging – this can be turned on and off from the service menu on a stock ROM anyway…
Set minimum backlight level to 15, from Franco’s kernel. Warning: I haven’t tried setting it to 15 so I don’t know if that value renders the display practically useless, and I don’t know if Android lets you set it to 15 from its settings!
ButtonLock
Not as revolutionary as I'd like it to be, but useful nevertheless. I've written a quick widget, which looks like the Power Saving one, that turns off the button backlight. Useful for when you're reading books through FBReader.
You need to be using my kernel as it has the disable_button_leds patch. The advantage the disable_button_leds patch has over the chmod 444 method is that it doesn't introduce noticable lag. The widget's source is in the same folder.
When pressing the widget's button for the first time, there is a delay as the Superuser allow/deny dialog box takes its time to come up. After accepting, future launches are instantaneous.
If you need something that this ROM doesn’t provide compared to other stock ROMs, I recommend:
Not using it; or
Using a combination of diff, abootimg, Winmerge (or Beyond Compare) and apktool to compare this with genokolar’s original release, and with birdyi's ROM, and add what you want back in
Installation
Note: You must be running firmware version B522 on your device! If you have B540, you need to downgrade. If you have a firmware version lower than B522 (Froyo?), you must upgrade to B522 first. If you're already running a custom ROM, ignore this.
Take out the SIM card if you want the setup wizard to use Wi-Fi during setup.
Install genokolar’s recovery: http://forum.xda-developers.com/showthread.php?t=1343276
Place u8800pro-2.3.6-geno-v1-modified.zip on the internal memory card or an external one (I recommend the internal one to ensure you don’t run into U8800Pro CWM bugs with the external).
Get gapps for Gingerbread and place on your memory card. Find the link using every Android user’s favourite search engine.
I highly recommend using PDroid, but it’s up to you whether you want to use it. If you would like to use it, get the patcher from http://forum.xda-developers.com/showthread.php?t=1357056 and point it to u8800pro-2.3.6-geno-v1-modified.zip. Place the PDroid-v1.27-u8800pro-2.3.6-geno-v1-modified.zip file onto your memory card.
Boot into recovery (make sure that fast boot is turned off in Settings->Applications and hold power and volume up while turning the phone on)
Do a data/factory reset.
Install the ZIPs, starting with u8800pro-2.3.6-geno-v1-modified.zip (obviously).
Reboot!
Install the Google apps (those ones not included in CM's gapps ZIP like YouTube) if desired when prompted – but note that the Market will probably close as you’re doing this as it will automatically update itself.
Downloads
ROM: http://www.mediafire.com/?k0g17z1kraw7b67
SHA512: 4988B123488B8B24732401420DE849E8D8E5632C075A4520F176AA1D64DA0ECF946FF4D4E6CEC4D257EE4C4C999200A93C2CB309FD7B5FE50234A1C5700DEB2D
Modified kernel source (I suck at Git - I really need to read that VCS by Example book I have ): http://www.mediafire.com/download.php?a0022t73q2v7r7d
ButtonLock source (Apache licensed, though I must admit I'm more of a GPL person...): attached.
--
Extras:
genokolar's 5.0.27 recovery for the U8800Pro with the charging animations from https://github.com/Victor-android/android_device_huawei_u8800pro/tree/master/recovery/res/images:
attached.
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Too times was a situation, when phone lost connection with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
...
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
bobsido said:
with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
Click to expand...
Click to collapse
Interesting. I've had no problems reconnecting to a network that uses WPA2-PSK and another that uses 802.11x authentication.
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
Click to expand...
Click to collapse
Are your APNs set correctly? In my case 2G works and I've had HSDPA working because when testing the Weather Clock widget (from B522, when I had it in) it would connect using it - I could see the icon in the status bar - and I had the pleasure of having my balance run down each time - I'm not a rich man
Edit: In build.prop, you can try playing with ro.config.hw_fast_dormancy=3 - genokolar had it set to 2, but I changed it back to 3 from the U8800Pro original ROM because I wouldn't be able to connect to my network otherwise.
Hopefully, it's not the case but it could be hardware differences. genokolar, who's work this is based on, being from China, probably has a Unicom U8800Pro, just like I do...
@Zaic
B512? This is for the U8800Pro. I'd advise you not to flash it. I'd recommend using birdyi's ROM. If you're after a certain improvement from this ROM, tell me and I'll try and isolate it for you (as long as it doesn't involve kernel stuff - I don't know how to build U8800 kernels) so that you can use with birdyi's ROM
I have u8800 pro - 100%
My ROM is original unrooted 2.3.5 B512 its one before the latest release which is B540
My ROM still has access to pink screen, otherwise its the same as B540 I guess
SO what should I do first to install this ROM? roll back to 2.2.2 or was it 2.2.3?
Ah, if you're running 2.3.5 already and in the pink screen mode you see a folder called image when connecting your phone to the computer you're ready to go
Hi!
My compliments for the porting of Android 2.3.6 to U8800Pro!
I am using your rom since yesterday and still now I am not having any kind of problems.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Please try to reproduce this bug.
I am using LauncherPro but this bug is indipendent by the launcher (for example I tried also Zeam Launcher, Go Launcher EX, etc etc).
I hope you can solve this bug, maybe kernel-related.
Regards,
kalo86
Hi,
kalo86 said:
My compliments for the porting of Android 2.3.6 to U8800Pro!
Click to expand...
Click to collapse
The honor is genokolar's
I am using your rom since yesterday and still now I am not having any kind of problems.
Click to expand...
Click to collapse
Thanks; it's nice to know that it's working OK on somebody else's device other than mine.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Click to expand...
Click to collapse
Sorry for asking, but how do you pinch to zoom on the home screen? I'm using Go Launcher Ex and I know that that has the swipe up gesture but I can activate that with one finger, anyway.
In any case, have you applied the Synaptics touchscreen update? For me it has increased the touchscreen performance greatly. I had one problem that when after unlocking, the touchscreen wouldn't respond unless I turned the screen off and tried again. The update solved that.
If you want to try it, open the service menu (*#*#2846579#*#*), go to ProjectMenu->Upgrade->Touch screen version query and see if it says "synaptics". If so, put the original Huawei recovery.img back on and put the synaptics.img file in a folder called update on your SD card. Use the recovery's "touchscreen firmware update" update option and it will automatically reboot when it's done.
Best regards,
qwerty12
Oh, really thank you for this "news" about the synaptics touchscreen update!
I have a synaptics too, then I am going to update the firmware.
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Thanks to You and Genokolar for our development!
Regards,
kalo86
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Video demonstration
This is a video which I just uploaded on YouTube with the real multitouch bug.
This bug is in 4 different U8800 Pro.
http://www.youtube.com/watch?v=avSdW2V8TLg
kalo86 said:
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Click to expand...
Click to collapse
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Click to expand...
Click to collapse
Thanks for the video! Unfortunately I don't know how this can be fixed - I'm not a developer! It was only yesterday I tried looking in the driver to see how I can enable more than two finger recognition but I'm not seeing it...
Best regards,
qwerty12
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
qwerty12 said:
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
Click to expand...
Click to collapse
The same here with sd,full power off device, power on then sd card is not mounted and cpu load is almost 100%. after restart or reinserting sd, problem just dissapear. on every rom i tried. i flashed official V100R001C00B512G001Gb (2.3.5) and then tried CM7; u8800+v100r001c00b540g001gb-rooted_geno-v4.
Is FM Radio working in this ROM?
Yes, Radio is working fine
qwerty12 said:
Are your APNs set correctly?
Click to expand...
Click to collapse
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
kalo86 said:
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
Click to expand...
Click to collapse
A little bit - after unlocking, I can do the multitouch gesture and phone will respond like it's supposed to but I have seen twice that it has not responded to me; I have to do it twice more...
Barracuda72 said:
Is FM Radio working in this ROM?
Click to expand...
Click to collapse
Like kalo86 said, it is indeed
bobsido said:
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
Click to expand...
Click to collapse
Please do let me know if you come across more problems
Zaic said:
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Click to expand...
Click to collapse
So, any missed calls?
If someone wants to help the Community to understand the sdcard mount bug, please have a look here: http://forum.xda-developers.com/showthread.php?t=1483519
This is a poll, please vote!
Best regards,
kalo86
Zyzas said:
So, any missed calls?
Click to expand...
Click to collapse
Haven't had time to install this ROM yet.... but ill report as soon as I know
{
"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"
}
About
This is a clean ICS ROM built from from the Qualcomm Code Aurora source.
Everything is functional including the camera, video recording, bluetooth and GPU acceleration.
This is based on the ics_chocolate branch and a new version is released regularly.
https://www.codeaurora.org/xwiki/bin/QAEP/ics_chocolate
Full source is available on github, see here:http://forum.xda-developers.com/showpost.php?p=22770874&postcount=747
Please do not use this thread to ask questions that are not related to development.
Use this thread in the general section instead: http://forum.xda-developers.com/showthread.php?t=1579821
Features
3.0.8 Kernel running at 1GHz default.
Google apps included
Known Bugs
Use this issue tracker to report bugs/problems:
http://code.google.com/p/ics-aurora/issues/list
If you get a reboot, do the following from a terminal or over adb:
Code:
su
cat /dev/block/mmcblk0p7 > /sdcard/crash.txt
Then post the crash file (if it has anything in it) here or on the issue tracker.
Downloads
Download it here:
https://sourceforge.net/projects/icsaurora/files/
or here:
http://code.google.com/p/ics-aurora/downloads/list
Installation
To install, you must have upgraded to the official gingerbread rom and installed CWM recovery 5.0.2.7 or 5.5.0.4.
You will have to wipe data when you first install but upgrading shouldn't need a wipe unless it is stated in the release notes.
Some instructions on upgrading are here: http://forum.xda-developers.com/showthread.php?p=22682229#post22682229
and here: http://forum.xda-developers.com/showthread.php?t=1420728
Users in Finland on the Saunalahti network need to change a setting for the sim card to load correctly.
download a terminal program such as connectbot and open a local session, then type:
su
setprop persist.opl.enabled 0
setprop persist.pnn.enabled 0
setprop persist.eons.enabled 0
Now reboot.
You only have to do this again if you wipe data.
Thanks
Thanks to the Code Aurora team at Qualcomm.
Thanks to Tom Giordano/bukington for some of the the ics kernel commits.
Thanks to early testers who risked missed calls and corrupt memory cards to try it out.
Thanks to all those who have donated - your contributions help me continue this work. This stuff takes a lot of time so your support makes a big difference. All donations are much appreciated.
Please also support my work by buying my Camera App:
https://play.google.com/store/apps/details?id=com.marginz.snap
Changelog and Release Notes
Initial Version 1.0
camera not functional
low in call volume
sound recording is quiet and distorted
wifi doesn't always connect automatically
notification led doesn't flash
Version 1.1
fix low in call volume
fix bootloop on enabling cell location
fix light and proximity sensors
fix home key on amtel touchscreens
enable mtp mode for data transfer
Version 1.2
fix for bootloop when audioflinger doesn't start sometimes
enable usb mass storage
mount internal emmc as /mnt/sdcard1
build with all languages
Version 1.3
Working camera (no video yet)
fix for SD card not being recognised and getting corrupted
change to the rpc ril instead of the qmi ril
There are still random crashes but I think they are caused by the GPU failing when the device suspends if you don't use live wallpapers that may help.
Version 1.4
Fix low resolution icons
Fix Mobile Networks menu when language is not US English
Update kernel GPU driver to latest version
Version 1.5
Fix video recording
If you switch away from the cam when it's in video mode (e.g. to view a video), it will crash when you return to it.
This doesn't affect the functionality but is annoying.
It does full 720p h264 with audio.
Version 1.6
Fix a bug that caused the gpu to sometimes crash when the display was switched off.
Enable autobrightness (don't think it actually works yet though)
Flash led for notifications - fast flash means phone is awake, slow flash means phone is power collapsed (in deep sleep)
Version 1.7
Update to M7630AABBQMLZA4040295I release
Fix camera crashes
Fix barcode apps not working
Include ES file explorer
Fix for echo on speakerphone (not well tested)
Use handset mike when headset is plugged in (not tested)
Reduce brightness of keypad led
Fix wifi not always connecting automatically
Turn off bluetooth completely when not in use
Extra CPU frequencies (thanks godofdream)
Version 1.8
Fix music not skipping to next track. This was a kernel audio problem and fixing it has
fixed some other problems. e.g. with some games pausing while trying to play audio.
Fix picture rotation for the camera.
Add smartass2 cpufreq governor, I don't care about this but somebody asked for it.
Change some values in /system/etc/gps.conf - don't know if this will help.
Version 1.8a
Fix video recorder crash
Version 1.9
Change speaker acoustic profile - hopefully this will fix audio problems
Change sensitivity of synaptics touchscreen
put aurora version in build number
change phone name, model and manufacturer to the correct values
fix strictmode not turning off (may need a reboot)
fix raw picture mode for camera (not very useful)
set build type to user rather than eng
Version 1.10
Fix battery stats not showing (needs more power data to be useful)
Add ability to skip loading some records from the SIM card (for Finland)
Fix compass
Remove some frequencies from cpufreq table (might help with battery life)
Change wifi scan rate from 15 to 60 seconds
Add latest google apps (should let navigation work better)
Free up a bit of spare memory from the kernel
Add FM radio - (thanks to honking)
Replace ringtones and notifications with those from Nexus S
Add simple boot logo (sorry, the full animated logo didn't fit)
Version 1.11
Fix FM radio
Add another fix for Saunalahti
Update all proprietary libs to newer versions
Free up some more memory (camera was being very greedy)
add headsetmic and dualmic properties
Version 1.12
Update to M7630AABBQMLZA4040296I release - fairly big change so this may introduce new bugs
Use version 0.8 of wpa_supplicant with wext library (should help with wifi connection problems)
Fix atmel touchscreen
Add settings for dualmic and headset to settings app (in Sound) - property names had to change so you will need to set them again.
Version 1.12a
Fix 720p video recording
Version 1.13
Use the 2d graphics core for composition - should make graphics faster and use less power (set debug.composition.type=gpu in build.prop if you don't like it)
Update power profile so battery stats work better
Some gps changes (not tested well)
Remove some unused resources to reduce the size of /system
Add a system property to override the wifi mac address - use su; setprop persist.sys.wifimac mac_param=11:22:33:44:55:66
Version 1.14
Fix FM Radio
Possible fix for audio volume problems after a notification or call
Some updates for graphics composition
Version 2.0
Getting stable now so bump the version up to 2.0
Add camera library from latest official gb (seems to focus better)
Update bootlogo
Reorganise camera ui so flash menu is visible
Remove 480p from camcorder menu (use wvga instead)
Enable panorama mode for camera (pan slowly with the phone held horizontally)
Fix Pinyin IME (Chinese input)
Update market and music apps to Google Play versions
Version 2.02
Notification drawer widget and settings (some things don't work yet)
Fix to stop wifi disconnecting when the device sleeps
Kernel dumps a log to /dev/block/mmcblk0p7 on a panic (kernel crash)
Change default I/O scheduler to no-op
Disable some GPIOs that were unnecessarily enabled (may save some power)
Update FM radio
Version 2.04
Update to M7630AABBQMLZA404030I release
Fix torch in Notification drawer and add torch app
Add new wifi driver, enable it from Settings..Developer Options
The new driver uses much less power and stays connected when the phone is asleep but doesn't work with WEP networks and may be more buggy.
Update GPU drivers to the binaries that were released by Qualcomm.
Enable gpu composition, 2D is slower but some apps work better.
Change Bluetooth power level to 2. May help BT connection problems.
Saunalahti users note that the SIM loading hack has changed - see the installation instructions.
Version 2.05
Update to kernel version 3.0.8 (ported from u8860 with lots of work), this may be less stable than earlier versions.
Only the new wifi driver will work, the settings app still shows a choice but changing it won't do anything.
New wifi config file (thanks to sbasil).
Fix the date in exif tags for photos.
Fix button backlight, now has autobrightness too.
Fix photo editor crashing.
Use CAF radio app (has a horrible interface but the old one no longer works). Supports rds.
Version 2.06_experimental
Update to latest ics_chocolate (caf_AU_LINUX_ANDROID_ICS_CHOCOLATE.04.00.03.05.169 manifest)
This is Android version 4.0.4 so there are lots of changes from 4.0.3 and that is why it's experimental.
Fix camera picture corruption (camera may still not be completely stable)
Fix wifi not seeing some APs
Fix some causes of wifi reboots.
Warning: Since this is a new Android version you may not be able to downgrade without clearing data so make a backup first.
Version 2.07_test
Update to latest tagged release for msm7x30 (M7630AABBQMLZA4040305I)
Change touchscreen mode to avoid jitter
Update some proprietary binaries
Fix failure to send vreg rpc to the modem from causing battery drain sometimes
Wifi fix for occasional reboots
In /system/etc/firmware/wlan/qcom_cfg.ini I have set gMaxPsPoll=1 because without this wifi doesn't stay connected during sleep. Some people claim this gives problems when connecting to certain APs but I have never seen this.
Version 2.08
Fix SD card detection using a gpio interrupt
Free 33M ram by reducing the size of the surfaceflinger cache and the camera record buffer
Fix a couple of memory leaks in the wifi module
Fix notification of an incoming call during a call
Switch back to version 0.8 of wpa_supplicant (should help with wifi connection problems)
Version 2.09
fix sd card not mounting if wifi is initially off
add haptic feedback for atmel touchscreens (to disable, put "echo 0 > /sys/module/atmel_i2c_rmi_QT602240/parameters/vibrate" at the end of /system/etc/init.qcom.post_boot.sh)
fix bluetooth not pairing
make wifi module much smaller (from 2M to 800K)
update root filesystem and rc files
Version 2.10
Update ril proprietary libs
Enable HSDPA symbol
Fix button lights with manual brightness
Fix time lapse video recording (720p only)
First try at getting native wifi tethering working (turns on but doesn't work)
Increase surfaceflinger pmem size
Version 2.11
Possible fix for volume button failure
Revert to the larger wifi driver
Increase minimum free memory available
Increase echo cancelling microphone level in calls
Update kernel GPU driver to latest version
Fix wifi not always resuming from suspend correctly
Fix noise on non-echo cancelling microphone
Update to latest proprietary GPU libraries
Fix notification of an incoming call during a call (Again!)
Update to latest google apps, google music and es file explorer
Version 2.11a
Fix wifi configuration in 2.11
2.11a Update1
Install from recovery on top of an existing 2.11a installation
Fix volume button breakage (for real this time)
Fix native wifi tethering
Set default min/max cpu frequency to 122MHz/800MHz, this saves some battery and you can always change it with setcpu.
Version 3.0_beta
Update to new CAF release M7630AABBQMLZA404031I
New LED driver (only does the same notifications as before but is much more programmable)
Use older kgsl driver (possibly more stable)
Version 3.0_beta2
Revert to older version of the ril because some people had problems with mobile data
Use older wpa_supplicant to fix wifi connection problems
Use the new kgsl driver again since the old one didn't seem to fix anything
Remove the software opengl lib from egl.cfg
Remove qualcomm's media parser from the media scanner, this may help with media scanning problems.
3.0_beta2_update1 (Install from recovery on top of an existing 3.0_beta2 installation)
Apply the patches described here: http://epiccm.blogspot.co.nz/2012/03/details-on-disappearing-sd-media-issue.html
Increase the panel frame rate to 53fps - thanks to zephyr1988
Add smartass2 (not default) - also thanks to zephyr1988
3.0_beta2_update1a
Remove the panel modification patch because it doesn't seem to work on some hardware
3.0_beta2_update1b
fix kernel config
3.0_beta2_update2 (Install from recovery on top of an existing 3.0_beta2 installation)
Same fixes as update1 +
more reliable wifi driver
Settings to allow switch between MTP and mass storage mode:
Use settings..storage..menu..USB Computer Connection
The second option will enable Mass Storage (for languages other than English, this will be displayed as PTP mode)
Version 3.1
Fix Pinyin Keyboard
Use small wifi driver again
Use version 2.0 wpa_supplicant. (this may cause problems with some APs but I think it's better to use this than version 0.8 because the rest of the system is designed for it). If it doesn't connect to an AP, post a log giving all the details and I'll try to fix it.
Add /HWuserdata as a symlink to the internal sdcard
Use settings..storage..menu..USB Computer Connection to switch between usb storage and MTP mode (some people have reported lost data on the card when doing this, you have been warned). MTP mode is probably what most people want.
Fix battery reporting for the backlight.
Reduce flashlight LED brightness.
set modprobe path correctly so modules will load
Updated network drivers
Update to latest sd card, fb and kgsl drivers.
Add SmartassV2 governor
Fix to allow Light Flow to control notification LED
aurora_3.1_update1 (Install from recovery on top of an existing 3.1 installation)
Fix wifi not connecting on boot
This may also fix some (but probably not all) wifi disconnection problems
Add battery percentage option in settings..development
aurora_3.1_update3 (Includes fixes in update1)
Fix bluetooth pairing.
Fix searching for available networks.
aurora_3.1_update4 (Includes fixes in updates 1 and 3)
Add "strip unicode" and timestamp options for SMS (thanks to mrasquinho)
Fix for bluetooth not sleeping correctly
Some updated translations in settings (thanks to mrasquinho and one-2-z)
A possible fix for wifi crashing on wakeup
Fix for a rpc wakelock never being released sometimes
aurora_3.1_update5 (Includes fixes in updates 1-4)
Fix Gallery causing reboot
Fix laggy transitions on some devices
Update Mms translations by mrasquinho
aurora_4.0
update to new CAF release M7630AABBQMLZA404032I
This is on a new release branch - ics_chocolate_rb7.1
There are a lot of changes here so some things may break, others may be fixed....
aurora_4.1
update to new CAF release M7630AABBQMLZA4040325I on ics_chocolate_rb7.2 (lots of changes)
Fix voip apps not working (not well tested and may be buggy)
Fix for missed call led notification
Update video encode/decode driver
Update rotator hardware (this does hardware rotation of video and wasn't being used before)
New proprietary binaries
aurora_4.1_update1 (Install from recovery on top of an existing 4.1 installation)
Fix gallery crash
Fix overlay (uses less power when playing videos)
Disable continuous focus for video recording
Enable brightness control using volup/down buttons in camera
aurora_5.0_experimental
New kernel based on the u8800pro source
Updated camera HAL and libs, zoom bug and green lines on thumbnails are gone
Enable continuous focus for video recording
aurora_5.0_update2 (Install from recovery on top of an existing 5.0 installation)
Update for atmel ts (still not great)
Fix USB mass storage
Fix wifi driver not loading/unloading if memory is fragmented
Allow scene mode when recording videos
Fix date on pics
aurora_5.0_update9 (Install from recovery on top of an existing 5.0 installation or any other 5.0 update)
Fix audio after sound recording
Fix atmel ts
Add ram console and panic dumper
kgsl changes suggested by PaulMilbank, thanks Paul
Fix memory allocation for wifi
Fix wifi hardware crashing not recovering correctly
Enable runtime power management
aurora_5.0_update11 (Install from recovery on top of an existing 5.0 installation or any other 5.0 update)
Fix camera chroma in portrait mode
Fix unforgettable wifi
Fix atmel haptic feedback
Fix button brightness after closing camera
aurora_5.0_update14 (Install from recovery on top of an existing 5.0 installation or any other 5.0 update)
Fix button backlight
Fix bluetooth pairing
aurora_5.0_update16 (Install from recovery on top of an existing 5.0 installation or any other 5.0 update)
Fix gallery causing a reboot on some devices.
aurora_5.0_update18 (Install from recovery on top of an existing 5.0 installation or any other 5.0 update)
Fix 1080p showing up in my Camera App.
Fix wifi memory allocation problem.
Fix button backlight again
aurora_5.0_update20 (Install from recovery on top of an existing 5.0 installation or any other 5.0 update)
Improve wifi driver
add entropy fix
Thank you!!!
Great news man, have to try it after I come from Ice Fishing. Will post bugs/news/related.
Great! Thank you.
Sent from my Ideos X5 using XDA App
Thank you very much for the work done!
Thank you!!!
You are my Huawei Hero!!!
Hell yeah!
home key doesn't bring me home. is this confirmed?
swayjd said:
Hell yeah!
home key doesn't bring me home. is this confirmed?
Click to expand...
Click to collapse
I can confirm. And I can't use Phone App. too.
Awesome..... I will test this later.
Sent from my u8800 using xda premium
good work. I'll try it after it grew somewhat mature.
its built using 7630 code. isn't 7230 code available???
Home key works fine for me, did you wipe data?
No pin request before i linked my google account, then got the pin request, but phone reboots every time it picks up service
Awesome.
Sent from my Derp using XDA Herp
[QUITE]
its built using 7630 code. isn't 7230 code available???[/QUOTE]
The 7630 code is designed for 7230 and 8255 as well. 7630 just has some cdma hardware too.
dzo said:
Home key works fine for me, did you wipe data?
Click to expand...
Click to collapse
I wiped data/cache. Home key isn't working.
When I dial someone phone app FC too. (If I select "wait" option phone restarts.)
I have Atmel.
Noticed one other thing, Isn't ics have all languages? This one only have 5 language.
There is something wrong with sdcard, when I open any app that use sdcard phone restarts, and its looping. I don't know whats wrong with it. If you interested I cant send debug logs.
PS: Can wifi cause the reboot loop? Because When I add my google account phone starting to restart itself after 3-5 min.
Edit: adb don't see the phone. So i can't send logs.
Edit 2 : Seems like I don't have signal from mobile network. And *#06# doesn't seems to be working.
I don't have much time now, but I will be back for this topic.
Great! Thank you.
Very fast and smooth in my phone.
I have problems with sd card mounting after restart.
- sometimes phone repotrs broken sd card
- sometimes phone repotrs removed sd card
- sometimes phone repotrs empty sd card
- sometimes mount is OK,
but e.g. in recovery sd card is without errors, same in notebook.
Home button also does not work.
But thank you.
Keep up the good work
can i flash it with recovery CWM 5.5.0.4?
good work! thanks
---------- Post added at 12:09 PM ---------- Previous post was at 12:01 PM ----------
@Dzo. You can try my drivers.
download link: http://www.mediafire.com/?heb55wz54r85b5e
Nice job!
Anyway, what is the difference in the CodeAurora's ICS and AOSP ICS?
Initial post for Sailfish Os for the Samsung Galaxy S2 (i9100) device.
Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! W A R N I N G !!
!! !!
!!(Although I am using this on my backup phone)!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! ROM IS NOT SUITABLE FOR DAILY DRIVE !!
!! ONLY FOR EXPERIMENTAL PURPOSES !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Making this port was challenging because Sailfish OS, from version 3, doesn't support kernel version 3.0 which is apparently the kernel on the S2.
Fortunately, the SailfishOS-porter guys do very seriously know their business and they are extremely helpful.
From here I would like to emphasize my gratitude towards them for helping me in this project! Thank you!
Requirements:
Before you start to download anything, please read it carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
For this ROM you can either use the stock partitions or you can re-partition to give more space to /system and /data. It doesn't matter which one you chose, I tried and both worked well.
Or if you scroll down to the New partition layout, you can use a completely unique partition layout which gives the most of the internal storage to Sailfish OS. (I currently use my device with this setup.)
Installation instructions:
1. Download all files, CM12.1 zip, Sailfish OS zip, twrp2.8.7.img and kernel*.img to the external SD card on the phone
2. Reboot into TWRP (hold buttons: Power on + Home + Volume up)
3. Do a factory reset
At this point if you want you can repartition the S2 internal storage. (Later you can put the stock layout back if you want to go back to Android.)
The steps for repartitioning are:
Download the 'Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB' or the 'Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB' .zip file and put into the external SD card. (The difference between these two is explained down at the New partition layout section
Then boot into TWRP and flash the zip as any other zip file. The script first will warn you that it cannot do the partitioning with mounted partitions and it also copies the script itself into /tmp. You just simply need to flash the copied version from /tmp and that will do the trick. The script will format the new partitions accordingly, so once it is completed you can go ahead with the next step.
4. Still in recovery, flash the CM12.1 image
5. Still in recovery, flash Sailfish Os image
6. Still in recovery, flash twrp2.8.7.img to recovery partition
7. Still in recovery, flash kernel*.img to boot partition (this step is not required since sfos 4.4, kernel is installed by flashing the zip file)
8. Reboot
9. Enjoy the latest (4.4.0.68) Sailfish OS on your i9100.
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on CM 12.1.
Downloads:
kernel12_mtp.img for Sailfish OS 3.2.1.20
kernel33016.img for Sailfish OS 3.3.0.16
kernel34024.img for Sailfish OS 3.4.0.24
kernel41024.img for Sailfish OS 4.1.0.24
kernel43015.img for Sailfish OS 4.3.0.15
twrp2.8.7.img for i9100
CM 12.1 for i9100
Sailfish OS 3.2.1.20 for i9100
Sailfish OS 3.3.0.16 for i9100
Sailfish OS 3.4.0.24 for i9100
Sailfish OS 4.1.0.24 for i9100
Sailfish OS 4.3.0.15 for i9100
Sailfish OS 4.4.0.64 for i9100
Sailfish OS 4.4.0.68 for i9100
Sailfish OS 4.4.0.72 for i9100
Odin v1.83
AOSP-LP-Kernel+_25-08-2015_TWRP-2.8.7.0.tar
Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB
Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB
Stock partition pit file
kernel07_flatpak (kernel with Flatpak support. Flatpak install/usage instructions.)
Some useful tips:
Low power mode aka ambient mode (in Fingerterm):
Code:
mcetool --set-low-power-mode=enabled
Disable lock screen animation (in Fingerterm):
Code:
mcetool --set-lockscreen-animation=disabled
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community-made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
Now the old clunky method is no longer needed. Once you flashed the twrp2.8.7.img to the recovery partition you can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Instructions for Bluetooth (On Sfos 4.3, BT works normally, don't need this magic)
BT works however turning it on/off is not as user friendly as I hoped. Here is a little instruction/troubleshooting.
Turn BT on (It only works from Settings/Bluetooth!!!!! DON'T try from TOP MENU!!):
If BT hasn't turned on since last boot:
go to Settings/Bluetooth
tap on the dot next to the Bluetooth option
If BT has turned on at least once since last boot:
go to Settings/Bluetooth and tap on the dot next to the Bluetooth option
go back to Settings
go to into Settings/Bluetooth again
tap on the dot next to the Bluetooth option (if it is not turned on repeat from Step 2! Eventually, BT should turn on.)
Turning BT off: Go to Settings/Bluetooth and tap on the white dot next to the Bluetooth option.
Notice: Never try to tap on the white dot twice without going back to the main menu of Settings.
Never try to turn BT on from Top Menu.
However, if you accidentally did any of these BT cannot be turned on again unless you:
reboot the device (this is the easiest) or
in a command line as root issue the following command 'systemctl restart bluetooth-rfkill-event.service' (this will restart the bluetooth-rfkill-event service)
I am not sure how pairing works with different devices.
New partition layout
I mentioned that I tried this Sailfish OS installation with the stock partitions and with another what created for Android 7.1.2. With the stock partitions however was a bit more sluggish than the other one. No wonder as in the stock partitions the /system has only 0.5GB and the /data has only 2GB storage and the rest 12GB is the separate internal storage (eMMC). In Sailfish the entire os (rootfs) including all directories (like /home) live on the /data partition so the 2GB was a bit tight. (The OS itself consumes about 1GB so not much left for apps and other stuff.)
With the other partition layout, the picture was a bit better as the /system had 1GB, the /data got 4GB and the rest 9GB remained for the internal storage. But the partition where the OS lives was separated from the 9GB partition. When I installed a few apps and copied some big files into the /home, I felt the limitation very soon.
Although this layout was sufficient for android but not good enough for Sailfish.
Therefore I have created my own partition table where I restructured the sizes accordingly to my need. (The lanchon repit zip file is available in the download section.)
In this new layout I gave 1GB for the /system (the prior 0.5GB was also fine as the CM12.1 base consumed only 400MB which let a 100MB free space, but I thought that might be not enough in the future so I have chosen 1GB here), I gave only 8MB for the internal storage (eMMC which is mounted into /android directory in this rom), and this made me possible to gave all the rest 14GB to the /data partition. So basically the Sailfish apps and /home can utilize the entire internal storage.
As an extra, on the S2 there is a 0.5GB /preload partition which is hidden and unused by default. In my partition setup I set 7MB to this and the rest almost 0.5GB is also added to the /data.
Go back to stock partitions
In case you would like to do this, you can download the stock partition pit file from the download section.
For this use Odin v1.83 which is also in the download section.
The steps are:
Boot the device into download mode and connect to the PC.
Open Odin v1.83 and tick the 'Re-partition' checkbox at the Option.
Then click on the PIT button and select the downloaded stock pit file.
Then click on the PDA button and select the downloaded TWRP (AOSP kernel) file.
Then click on start.
Done. You need to boot into TWRP and wipe all partitions (system, data, emmc) then you can install the stock rom back. (or if you select the stock rom at PDA instead of the AOSP kernel, it will do the repartition and install the stock rom as well. In this case, you don't need to wipe anything and the device will reboot into the stock Android at the end.)
Changelog:
15.02.2022
=========
General advice:
Patience! All (except camera) apps do start and work but they do need time. This is true for websites. When you clicked on something, wait patiently, eventually, it will start/load.
Work:
Same as previously
Improvement: Stock browser stable and works!
Do not work:
The camera app crashes the device into reboot.
03.09.2021
=========
Work:
Same as previously
Bluetooth does work, but once it is off, needs to be toggled a few times in Settings to make it turn on again.
14.06.2020
=========
Work:
Same as previously + Mobile data is fixed! (To make it work: change Protocol to IP in Settings/Mobile network/Data access point.)
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
06.05.2020
=========
The latest version of Sailfish OS 3.3.0.16 is available to download. This requires a different kernel. Both of these can be found in the download section.
Note: With the new version the patch that displays the provider logo at the bottom on the lock screen stopped working. This issue is not related to the OS. The owner of the app should fix it.
Update: In openrepos Kodi is fixed for SFOS 3.3.0.16!
29.04.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
MTP
Bluetooth (instruction is above)
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (Can be changed to 0.82 which is more appropriate for the device's screen. to do this as root run the 'kimmoli-diyicons.sh 0.82' command. It will fail to install imagemagick but will set the ratio to 0.82 and as we have all icons in place it will work.)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
the charging icon does work properly, however, there is a little delay
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
kernel and recovery .img can be flashed from TWRP (no need for PC to flash Sailfish OS, kernel and recovery)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
The softkeys (each side of the home button) work as notification leds
Do not work:
Mobile data (WIP)
Video recording (It doesn't really work in other 3.x versions either. See my test results here.)
There is an extra little issue that is a delay in screen refresh which is related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin. I managed to improve this but there is a little delay still. Probably this is the reason why we need to jump back to Settings every time before trying to turn BT on, but I am not sure.
04.04.2020
=========
Work:
Same as previously + Softkeys are used as notification leds
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
23.03.2020
=========
Work:
Same as previously + with 'kernel12_mtp' the MTP works!
Bluetooth partially works (to switch on BT requires a reboot or issue a command manually, it is still WIP)
Do not work:
Same as previously
25.02.2020
=========
Work:
Same as previously + with 'kernel07_flatpak' the Low Power Mode (AKA "sneak peek" or "ambient display") works! (install instruction is in this post)
Do not work:
Same as previously
23.02.2020
=========
Work:
Same as previously + but from now on you don't need PC and heimdall to flash kernel and twrp
Do not work:
Same as previously
19.02.2020
=========
Work:
The same as listed earlier + with the new kernel (kernel06) I attached you can boot into TWRP with the usual button combination (hold buttons: Power on + Home + Volume up)
Do not work:
Same as previously except the TWRP/Sailfish OS boot which has fixed.
08.02.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_
(where _sdcard_name_ is the name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (can be changed, I set 0.82 which is more appropriate for the device's screen resolution see the download section)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
Do not work:
Mobile data
Bluetooth (the bt driver is in the kernel, so in theory, with some config file changes on the device it can work)
MTP
Video recording (It doesn't really work in other devices with CM12.1 base.)
Screen delay in refresh (related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin)
the charging icon doesn't work properly: when the device is not on charger still shows it's charging (when I unplug the cable the message appears: "Charging..."
cannot boot into TWRP recovery (See Notes above)
Battery life:
In my experience the battery life is good. On standby, it can survive 10 days. (Almost 11.) I have checked once or twice daily during this period.
{
"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"
}
Pictures:
App drawer
Top menu
Settings
About product
In case somebody missed these I would like to highlight some improvements since day 1:
Now both the kernel and twrp can be flashed as an .img from twrp (no need for PC and heimdall anymore)
Plus I uploaded a kernel with Flatpak support
With kernel07_flatpak, I have installed Flatpak and Angelfish but got an error when started Angelfish.
It looks like this is a limitation of the old kernel, but there might be a workaround.
I'll keep you posted.
With kernel12_mtp, MTP works. (and bluetooth partially)
The soft keys each side of the home button are used as notification leds. As this device doesn't have leds, the softkeys can be re-used as "leds". They do blink if the device is fully charged or there is an unread incoming text message. When the device is on charger they are on, otherwise both of them are off.
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Galaxyninja66 said:
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Click to expand...
Click to collapse
Sorry for delay in my reply.
The necessary repos in github are:
local manifest
dhd (in here the dhd submodule has to be refreshed from mer-hybris repo upgrade-3.2.1 branch)
droid-hal-i9100
droid-hal-version-i9100
android_device
kernel
The file (path to android base kernel image) command gives me: "Linux kernel ARM boot executable zImage (little-endian)"
A new image has been generated and can be downloaded. This one includes the patch of reusing the two softkeys (each side of the home button) and they do work as a notification leds!
Currently I am working on the mobile data and bluetooth (this latter partially works but is not reliable yet).
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Galaxyninja66 said:
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Click to expand...
Click to collapse
I am not sure what you d understand under 'any service' but except the mobile data, everything else works fine (calls in/out, texts in/out).
I don't know the difference between the i9100 and i9100m but on the internet you probably can find something about it.
One suggestion, before you start porting, install an android onto and boot into that and note the mounting points. This can save a little time when you need to set the fixup_mountpoints in hybris-boot.
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
I think the reason why this doesn't get more hype because this is a very old device and except some old fashioned folks like us, not many are using anymore. I don't mind it because this is my hobby. I am going through a to-do list until all I wanted works.
Currently, as the new version 3.3.0.14 is out) I am working on to update my port to 3.3.0.14. Unfortunately currently there is no OTA but hope eventually it will be sorted.
Changing the pixel ratio is not essential as the default 1.0 is ok-ish. I have found the 0.82 better so I included the icons into my image. As the script (kimmoli-diyicons.sh) is also included, we just need to run one command as root. I may try to set the 0.82 out of the box but currently it is not my to priority. As I will need to re-build everything for 3.3.0.14, I will try to set 0.82 in the pattern file.
Please keep me posted with your progress.
edp17 said:
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
Click to expand...
Click to collapse
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Galaxyninja66 said:
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Click to expand...
Click to collapse
I remember that I built gstreamer and un-commented the related stuff in the pattern file. I don't know whether easier to build now because I don't know how difficult it was before. I only can compare this project against my hammerhead one a few months earlier. For the hammerhead I needed to build the image with MIC, now the rpm/dhd/helpers/build_packages.sh command does everything for you. (For this you need to export the RELEASE, EXTRA_NAME values in your .hadk.env)
Unfortunately I still don't have OBS account so I couldn't add this device into the wiki. Thank you for doing that! Unfortunately new account creation on the mer bug wiki is restricted at the moment.
I have checked the wiki you have added and if you don't mind I would like you to amend a few things:
LED works (the two softkeys have repurposed as notification leds)
GPS works
Sensors Gyro and Magnetometer both work
(I need to double check the RTC alarm and USB net.)
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Galaxyninja66 said:
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Click to expand...
Click to collapse
Thank you for the update and for the congrats but I think it is only partially my merits. I probably couldn't done this without the help of sailfishos-porter guys.
As I mentioned in the main comment, I am using my S2 with this image on it as a secondary phone already. Mobile data is not crucial as my main phone can be a hotspot and with my S2 I can connect to it via wifi. Of course this doesn't stop me trying to make that work. (The BT was almost done but I then broke something.)
The camera is a different story. Afaik the video recording generally is broken in the CM12.1 base that I chosen for this device. (That doesn't work on my hammerhead which is also using CM12.1 base.) So I think that will remain outstanding unless I try to port with a different android base.
I think will stop with this for while because the new version (3.3) is out soon and would like to upgrade to it first, then continue working on the missing bits.
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Galaxyninja66 said:
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Click to expand...
Click to collapse
I think the video recording also works in cm12.1 on the android side, but the problem is a, between the android and Sailfish or b, on the Sailfish side. I am not sure but when I tried to fix it on the hammerhead (same cm12.1 base) I was told the recording was broken in general with cm12.1 base. I'll see how it works (what I can do about it) after Sailfish 3.3 is out.
Have you thought about to purchase a cheap android phone to use as daily driver and using the i9100m for your Sailfish project? (You probably can get a decent second hand android phone for sub 20 maybe with better spec than the i900.)
Thanks again for the kind words. This phone (the S2) is my favorite old friend. It is indestructible . I have soft bricked so many times and managed to install many other OS but as couldn't find Sailfish OS, so I though worth a try to port. And with support of the Sailfishos-porters guys, my dream became real :good: .
Sailfish
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I am glad you managed to install it. Have you tried to re-partition the internal memory as I advised?
Yeah, the bt and mobile data is still WIP status. Hopefully will have some time to complete them soon.
For the browser, the native one doesn't hang for me. You can try to look for and install one from the openrepos. (I suggest to install the Storeman as you will find more useful apps for Sailfish OS.)
I don't know linusdan but have seen he has checked this post already. Hope he also found it useful.
I am aware of the postmarketos for the S2 and tested it on my S2. At that time (about a year ago) there was no mainline linux kernel option for the S2. Unfortunately the mainline kernel doesn't help with Sailfish because the Samsung proprietary blobs are missing from there. This means Sailfish wouldn't work. It needs the drivers from the Android layer.
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I forgot to mention that there should be a folder '/edp17packages/bluetooth' where you can find the missing packages for the bt. Once you installed it, probably only need to tweak some config files and need to create some scripts. I currently started working on it.