Related
CyanogenMod 7.2.0-RC1 "u8160" Port
Latest release: v1.5 [20120814]
Latest Google Apps package: 20110828
Hey folks,
This is a port of Cyanogen 7.2.0-RC1 (based on Android Gingerbread 2.3.7) for the Vodafone Smart VF858 (Huawei U8160) and Huawei X1 (U8180). The current port status is stable - all hardware is working correctly, but see post #2 for any known issues.
Pre-requisites:
ClockworkMod Recovery. The easiest method to flash ClockworkMod Recovery is via the ROM Manager application. See post #2 for more details.
Install the GooManager application from the Play store.
Installation (updating from older CM7 build):
Open the GooManager application.
Select the Check for rom updates option.
Click on the notification for the available update and then click the Download button.
When the download finishes, enter recovery and install the update package followed by the Google Apps package.
Installation (first time/new users):
Open the GooManager application.
Navigate to psyke83 -> roms -> u8160.
Click on the build you wish to install from the list.
If needed, click the Download Gapps button to download the Google Apps package. The most recent (and most suitable) version will always be selected for you automatically.
Click on the Download button to download the rom.
Once the download(s) are complete, reboot into recovery and install the update package, followed by the Google Apps package.
Important: if you are updating from a stock or custom ROM, choose the data wipe option before rebooting.
Releases / Changelog:
1.5 (20120814):
Updated CyanogenMod source
Undo modification to camera's maximum megapixel resolution for U8180 users (due to crashes)
Switch to using newer U8180 proprietaries by default
Add-on packages for USB host mode kernel, wpa_supplicant 5 and 6 (for users to test for any differences with wifi stability; base ROM uses v6 by default), U8160 and U8180 proprietaries (to test for any changes in functionality with wifi, camera and RIL).
1.4 (final) (20120802):
Hotfix 2: kernel: revert aps-12d change due to problems with proximity sensor; update 02setuphardware script to modify camera's maximum megapixel resolution on per-device basis (2mp for U8160, 3mp for U8180).
Hotfix 1: kernel: add early suspend/resume hooks to aps-12d light sensor driver, disable unused adp5587 keypad driver; remove 1600x1200 resolution filter from Camera app; add ro.config.PicMaxSize=2mp property to build.prop, which should limit libcamera's support to 1600x1200 resolution and therefore prevent camera crashes for certain users.
Updated CyanogenMod source
Consolidate all fixes from 1.4RC release + hotfixes.
Remove RomManager from default installation. Why? I no longer distribute ROMs/updates using it, and debug logging from the app suggests that it may have potential memory leaks issues. My phone now reports 45-60MB (60-75MB without Google Sync activated) free on average after removal of this package. If RomManager is still installed after upgrading to this release, it means that you have a local update installed, which you can uninstall just like a regular user app.
Re-introduce Adriano Carrata's patches: fix PIN entry in airplane mode; add workaround for apps which specify an invalid pixel format (i.e. Sygic).
Enable speex encoder support.
Implement additional patch for security issue CVE-2011-3874. Note: this vulnerability is supposed to be patched in the framework already, but the exploit test case still reports the exploit as being available. This patch may only fix the false-positive result of the exploit test. Either way, it's useful.
1.4 RC1 (20120729):
*Note: I'm provisionally marking this as a release candidate, as I've made a lot of changes to the kernel that may have unforeseen effects for certain users. If there aren't major problems, this will be renamed to the final 1.4 release.
Hotfix 5: removed akm8973 driver (not used after all), added mma8452 driver, more kernel optimizations.
Hotfix 4: added akm8973 driver (for real this time), fixed init.rc script to set U8180 model automatically, small kernel configuration optimizations.
Hotfix 3: added fixed wifi driver to solve issues with power saving mode and resume from idle (I had forgot to include this since hotfix 1 - whoops); added akm8973 and s5ksca drivers back into kernel to fix accelerometer and camera sensors for U8180 (and some U8160) users; fixed video camera mode; removed automatic reodexing option from U8160Parts (too hacky); removed U8180 branding option from U8160Parts (ro.product.model is now adjusted for U8180 users automatically on every boot).
Hotfix 2: fix U8160 (synaptics_i2c_rmi_1564) driver
Hotfix 1: re-added missing drivers and kernel config for U8180; fixed issue in which wifi would get held in maximum power saving mode under certain circumstances.
md5: 936cc309fe0a87c01091cbd0ee5edd9c
Updated CyanogenMod source
Kernel: reworked from scratch for stability (there were some errors in my previous CodeAurora merge); fixed some issues with Huawei-specific USB code; disabled Huawei virtual CD-ROM USB driver; fixed compass driver; removed Huawei wakelock/suspend code that was causing "unknown_wakeups" wakelocks to be generated, possibly draining battery; removed many unnecessary drivers & some debug options from default kernel configuration.
Wifi: Updated bcm4329 driver - adapted from clean android-msm.2.6.39 sources, including patches from Nvidia and Huawei to support our device properly; using wpa_supplicant_6 with combo scan enabled, including a fix for resume from idle. Summary: wireless should now work on all channels (>11 had issues before), hidden SSIDs work properly, and resume from idle works properly.
Removed USB host support from default kernel (will package separately)
Disable compcache (ramzswap) by default
Changed ramzswap, CIFS and TUN (vpn) drivers to modules, moved dhd.ko from boot image to /system to reduce memory footprint of kernel.
1.3 (20120625):
md5: aabb0add99abcec1ceebb5588242358f
Updated CyanogenMod source.
Add U8160Parts settings application. New options available via Settings -> Device settings: ROM re-odexing [not recommended for people already using some form of app2sd], attenuation of speaker, headset, FM radio, Kernel Samepage Merging, Swap, Generate bug report. Removed madconfig script.
Testing some patches by ac1953: automatic resume of music after interruption by incoming call; fix FM radio pop, ensure that last used frequency is properly tuned on cold start of FM app (including my change); enable workaround for invalid PixelFormat 8 (fixes Sygic).
libaudio: add FM audio attenuation support, fix minimum in-call volume causing sound to mute completely.
Resolve battery drain cause by kernel configuration in previous release (CONFIG_FB_EARLYSUSPEND has issues with suspend in Gingebread).
Revert to original bcm4329 driver (from Huawei U8180 source drop) with increased dhd_watchdog_ms period; disable combo scanning in supplicant to fix hidden networks; ensure that dhcpcd server is always stopped when wpa_supplicant is stopped. Testing to see if this improves battery usage, and/or resolves the problem with connecting to networks beyond channel 11.
[release candidate] (20120616):
Updated CyanogenMod source.
Kernel: disable framebuffer console (ANDROID text), instead transitioning directly from egg-timer (or bootsplash image, if installed) to CyanogenMod bootanimation - may improve battery
Kernel: enable USB Host mode (support modules are installed to /system/lib/modules/) - needs testing from users with OTG adaptors
Kernel: enable Kernel Samepage Merging, switch from console-based earlysuspend to framebuffer-based earlysuspend - may improve battery
New libaudio from Adriano Carrata with audio attenuation support, improved AudioFilter.csv - completely solves audio distortion
Switch to open source gralloc module (fixed - video decoders now work properly)
Fix issue in which framebuffer earlysuspend could sometimes cause the screen not to wake properly.
v1.2 (20120403):
Updated CyanogenMod source.
New kernel (based on latest CodeAurora froyo_almond branch).
Enable workaround to reduce audio distortion at higher volume levels.
Completely fixed instability/freezes related to USB tethering.
Various patches for memory leaks and minor bugs from gerrit.
v1.1 (20120317):
Hotfix 1: disable CGROUPS, fix wireless suspend stability issue
Updated CyanogenMod source - version 7.2.0-RC1
Cherry-picked various patches from gerrit to fix issues with core binaries/libraries (dalvik, bionic, zlib, etc.)
Kernel: reverted to stable 2.6.32.9 kernel due to issues with battery consumption. Note: CGROUPS is still enabled, but the Application Not Responding issue on first boot seems to be fixed
Kernel: disabled OTG support due to battery consumption issues (will package a separate kernel for interested testers)
Kernel: updated pmem driver, fixed issues with smartassV2 & interactiveX CPU governors
Wifi: stability patch for bcm4329 driver
wpa_supplicant_6: wait for control interface monitor to be brought up before starting. Improves reliability of wireless when reconnecting from idle.
libaudio: fix for minimum in-call volume being incorrectly muted in certain cases (such as on speakerphone)
GPS: use worldwide SUPL server by default
Compcache: back to 18%
ADWLauncher: lock action buttons by default (helps avoid cases in which users accidentally detach the icons for these buttons)
Change scrolling cache setting to further improve scrolling speed
v1.0 (20120227):
Known issue: you may see the message "process system is not responding" after unlock on first boot. This is due to CGROUPS being enabled in the kernel (and also happens with the stock kernel - it's not a problem with my updates). You can safely disregard the message as no harm will be done.
Hotfix 1test1 [8th March]: Changes to kernel to fix battery drain - please test.
Updated CyanogenMod source.
Kernel: now using version 2.6.32.57 (Code Aurora's froyo_almond updates + upstream's longterm 2.6.32.y updates merged)
Kernel: new bcm4329 wifi driver, which should fix reconnect from idle for hidden networks
Kernel config: enabled CGROUPS, tweaks to improve battery usage
Scrolling cache tweak.
v0.9 (20120203):
Hotfix 4test5 [21 Feb]: Revert longterm patches due to random reboot issue.
Hotfix 4test4 [21 Feb]: Kernel: fix screen not turning back on from suspend, other small fixes.
Hotfix 4test3 [20 Feb]: Kernel: rebased to CodeAurora froyo_almond branch & merged longterm 2.6.32.57 changes, updated wifi source driver.
Hotfix 3 [12 Feb]: Kernel: more stable config (enabled ARMv6 K extensions which stops USB errors; fix for U8180 key issues).
Hotfix 2 [10 Feb]: Fix call audio via Bluetooth headset; disabled AHB overclocking due to instability during USB tethering (and possibly also during other activities); wifi module now built from source to improve reliability; updated wpa_supplicant_6 to use combo scanning; re-enabled SCHED_HRTICK in config (it wasn't the cause of instability).
Hotfix 1: Fix audio routing issues that were causing problems with the mic and headset detection during calls. This may or may not affect the Bluetooth headset bug - please let me know.
Updated CyanogenMod source (almost 7.2.0-RC1).
Performance: disable scrolling cache (prevents lag)
Performance/battery: disable ICS rotation animation (it's slow and causes instability; ICS transition animations are still working smoothly)
Performance/battery: updated android staging kernel drivers from 2.6.35 kernel (notably bringing improvements to the lowmemorykiller driver)
Performance/stability: moved to stable copybit version
Stability: rebuilt kernel using 4.4.3 toolchain from CM7 source.
Stability: kernel audio driver patches to prevent rare blackscreen during incoming calls/low memory conditions
Stability: further updates to latest CAF libaudio version with FM routing code added. Bluetooth calling should work again, but needs testing.
Battery: added 2g/3g mobiledata switch option (allows you to use the mobiledata statusbar button to switch between 2g/3g network modes).
Fancy: enable electron beam animation for screen off by default (performance is satisfactory)
Reverted SIM lock change that was causing people to have problems with certain SIM cards.
FM: fixed audio routing (headphones will not longer malfunction if you use the speaker and then exit the FM app); prevent frequencies out of bounds being used; allow looping between the top/bottom of the frequency bands.
Improved mac address generator script to prevent errors for certain devices.
Increased default compcache memory allocation to 26%.
Miscellaneous code cleanups.
Now distributed via ROM Manager with a greatly simplified installation procedure.
v0.8 - 26 January 2012:
Updated CyanogenMod source (still 7.2.0-RC0).
Fix for rare issue where notification area items can get "stuck", causing notifications to malfunction.
Now includes ICS rotation and transition animations (merged officially into CM7.2)
Wifi: disable wpa_supplicant_6's combo scan to fix reconnect/hidden SSID issues
Bluetooth: disable master mode to increase reliability with some peripherals
libaudio: code cleanup (based on rmcc's geeksphone zero); removed dependency on proprietary liba2dp.so
ADWLauncher: allow rotation of home screen by default
Kernel: re-enable multitouch support (oops)
Init: reduce default mmcblk0 readahead from 2MB -> 258KB to avoid potential lag.
The phone is no longer restricted when network locked and using a different SIM card.
Small cleanups.
v0.7 - 22 January 2012:
Updated CyanogenMod source (still 7.2.0-RC0).
Kernel stability fix (disabled SCHED_HRTICK due to instability/random reboot issue).
MAC addresses for Bluetooth and wifi are now accurate.
Improved Bluetooth audio.conf based on this bug report. This should improve Bluetooth stability with audio peripherals.
Reduced default compcache memory usage from 18% -> 10% to reduce potential lag.
Reduce LatinIME landscape keyboard key height (.25in -> .23in)
Use automatic brightness setting by default.
v0.6 - 29 December 2011:
Hotfix 2 [31 December 2011]: Updated "madconfig" script. You can now run adb shell madconfig u8180 to activate U8180 ROM branding that will survive future ROM upgrades (of my own release).
Hotfix 1 [31 December 2011]: Updated kernel (further stability fixes, added interactiveX cpu scheduler, unlocked overclock frequencies up to 768Mhz); updated libaudio to increase buffer size (this improves smoothness of apps using audio - e.g., Gensoid can now play games at full 50/60fps in landscape with no visual stuttering @633Mhz, whereas before it would stutter constantly); renamed tethering device from usb -> rndis (cosmetic fix); tweaked LatinIME keyboard to use .23in key height (down from .26in).
Updated CyanogenMod source (7.2.0-RC0).
Kernel: rebuilt using latest stable linaro gcc release: 4.5-2011.11
Kernel: fixed phone freeze issue when USB tethering is interrupted. This change also seems to reduce general system lag that was being caused by a conflict in the USB drivers.
Kernel: fixed "back" softkey alignment.
Kernel: fixed touchscreen right edge sensitivity issue (portrait).
Renamed wifi device from eth0 -> wlan0 for better consistency.
Re-enabled surface dithering by default; it has been reported that font rendering is improved with this option enabled, and I don't see much performance impact when enabled.
Experimental build.prop tweak to enable 3mp camera support (untested).
v0.5 - 10 November 2011:
Updated CyanogenMod source.
Partial fix for third-party camera apps (e.g. barcode scanners).
v0.4 - 21 October 2011:
Hotfix 2 [23 October 2011]: Updated device permissions. This fixes the sound recorder and camcorder.
Hotfix 1 [21 October 2011]: Reverted to v5 wpa_supplicant. This solves the issue in which wifi refuses to connect to hidden SSIDs.
Updated CyanogenMod source.
Included some patches to bring further improvements to 2D graphics & general system performance.
Patched framework to swap volume controls when the phone is rotated 90 degrees.
Improve USB transfer speed while in UMS (USB Mass Storage) mode.
Fix some graphical corruption on widgets in stock Camera app.
Other small fixes.
v0.3 - 10 October 2011:
Updated CyanogenMod source - final 7.1 release.
Improved 2D rendering speed.
Switched to EU GPS servers.
Fixed headset/media control keys.
Re-enabled automatic brightness.
v0.2 - 3 October 2011:
Hotfix 3 [6 October 2011]: Kernel: reverted to stable compcache (ramzswap) driver. Framework: disabled JNI debugging -this fixes force-close errors in some applications such as TapFish, and increases overall system performance.
Hotfix 2 [4 October 2011]: Kernel: improved multitouch driver to fix touchscreen accuracy (especially soft keys), improved haptic feedback, fix to zram module. Small fixes to libaudio (the distortion is not yet resolved, however).
Hotfix 1 [3 October 2011]: Kernel: added compcache (zram.ko) module, reduced boot delay, unlocked 729Mhz frequency, small bugfixes. Framework: enable compcache by default (18% RAM usage, customizable in CyanogenMod Settings - Performance -> Compcache RAM Usage.)
Updated CyanogenMod source: now based on Gingerbread version 2.3.7.
Kernel now supports under/overclock from 30Mhz - 710Mhz (min/max frequency is set to 30Mhz - 600Mhz by default, so you must manually activate the higher frequencies via Settings -> CyanogenMod Settings -> Performance -> CPU settings). Thanks to estebanSannin. NOTE: My phone is very unstable at 691Mhz, and freezes immediately at 710Mhz. I am providing these higher frequencies just in case your phone has better tolerance for overclocking. I accept no responsibility for any damage caused as a result of overclocking.
FM Radio app: fixed seeking (left/right arrows).
Disabled automatic brightness (it potentially avoids battery drain, and never worked anyway). Thanks to tas0s for the tip.
Enable workaround to prevent corruption issues if you use the Simple2EXT app2sd app.
Reverted Gallery app to 2D version, due to lack of hardware 3D acceleration on our phone.
Added compatibility with sebastian404's ClockworkMod port. You can now install this ROM using his CWM recovery (as well as my own).
Improved FM volume calculation, reduced overall volume & small fixes to audio code.
Various small bugfixes.
v0.1 - 12 September 2011:
Hotfix 1 [18 September 2011]: Boot: removed custom lowmemorykiller tweaks; kernel: various updates (smartassV2, TinyRCU, Simple and V(R) IO schedulers), bugfixes and optimizations, changed default scheduler to Simple IO; libaudio: code cleanup; Framework: enabled hardware-accelerated 2D rendering.
First release. All hardware appears to be working correctly.
Source Code:
Kernel: https://github.com/psyke83/kernel_huawei_u8160
Device: https://github.com/psyke83/android_device_huawei_u8160
Getting started with ROM Manager & ClockworkMod
Skip to Part B if you have already rooted your phone.
a) Rooting your phone
Go to Settings -> Applications -> Development. Enable the option USB debugging, and wait for the debugging drivers to be automatically installed onto your PC.
On your PC, download the latest release of super1click.
Run super1click and click the Root button. Follow all of the prompts given by the application, but make sure that you choose yes to the prompt on whether to install busybox.
Continue to the next part when your phone is successfully rooted.
b) Installing ROM Manager & ClockworkMod
Install ROM Manager from the Google Play store.
Open the ROM Manager application. Choose the option Flash ClockworkMod Recovery, and confirm the phone model as Huawei U8160.
After downloading the recovery image, a Superuser prompt will ask you for permission for the application to have root access. You should Allow this action.
ClockworkMod should now be flashed to your phone.
Known issues
Excessive bass/distortion at >70% volume - workaround in v1.2.
Technical details:
Kernel 2.6.32:
CPU & AHB overclock supported up to 768Mhz, but default frequencies (122-600Mhz) are used by default for safety/stability reasons
Built-in support for CIFS, TUN, compcache (ramzswap)
Multitouch Synaptics touchscreen driver
Added extra CPU schedulers: interactiveX, smartassV2 (default)
Added extra IO schedulers: BFQ, VIO, SIO (default)
Updated Android staging drivers from 2.6.35 kernel
Patches to improve CyanogenMod compatibility (e.g. USB tethering)
Various other stability & performance patches.
Before you ask...
I have no interest or intention to further "mod" the ROM with any kind of hacks or customizations (like custom apps, themes, Swype, etc.). My only aim is to have a 100% stable port of Cyanogen code. Any such requests will be ignored.
Reporting bugs
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
The version of the ROM you are using (to confirm that you have the latest release)
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt. Copy and paste this log to pastebin.com, and provide the link.
If I ask you to re-test the issue after a data-wipe, do the following: reboot into ClockworkMod, perform a full backup, then data-wipe, reboot and retest the issue, giving a new log if necessary. You can then reboot into ClockworkMod and restore your data backup.
Alternate download location: I would prefer if everybody used the ROM Manager application to download & install my ROMs. If you need to download from the PC, however, you can use this link.
Troubleshooting Battery:
In order to help me to troubleshoot issues with battery usage, please follow these instructions:
Charge your phone to 100% battery.
Use your phone normally for as long as possible (ideally, 12 hours) without plugging the phone into your PC or main charger for the entire test period.
When the test period has ended, plug in the phone and immediately take a "dumpstate" log:
Code:
adb shell dumpstate >dumpstate-u81x0-yournickname.log
Upload the log file to pastebin.com or multiupload.com
Provide a brief summary of your general usage during the test period, such as: wifi usage and sleep policy, 3g/data usage, approx time spent on calls/games/idle, any information you may think is helpful to troubleshoot battery drains.
I'm trying your rom and is good but i have not found FMRadio..... Sorry i found.
can i test this mod on a U8180? the hardware seems almost identical
For real? My girlfriend has this phone, and she has been jealous of the CyanogenMod on my Optimus One ever since I installed it. This should make her happy!
She currently uses the SmartLucky 2.2 Rom developed at androidworld.it, did you work on that too / reuse some of their mods or is this an independent job?
I'll get it flashed for her tomorrow probably and let you know if there are any problems.
Request for info: since this is a low end phone, how much free memory is there after flashing, and (roughly) how does it perform vs stock? I noticed a big jump from stock froyo to CyamogenMod 7 on my O1, but not as much of an improvement from stock froyo to SmartLucky, but then that is also based on a stock froyo rom...
Thanks a lot for this!!
Hi! I just bought a Huawei U8180 (called Gaga here) and am new to the android world. I have a lot of questions... First I want to thank you for this "ROM".
My first question is: "How to root the Huwaei U8180?" I tried AndRoot, ZRoot, ... none of them worked... And, after rooting, how can I install a ROM on it? And finally, will this ROM be compatible with my U8180? Thanks very much.
jajajim said:
can i test this mod on a U8180? the hardware seems almost identical
Click to expand...
Click to collapse
The framework part should work, but you'll most likely need to change the kernel and wifi modules in boot.img to match your device.
---------- Post added at 02:51 AM ---------- Previous post was at 02:50 AM ----------
wassgha said:
Hi! I just bought a Huawei U8180 (called Gaga here) and am new to the android world. I have a lot of questions... First I want to thank you for this "ROM".
My first question is: "How to root the Huwaei U8180?" I tried AndRoot, ZRoot, ... none of them worked... And, after rooting, how can I install a ROM on it? And finally, will this ROM be compatible with my U8180? Thanks very much.
Click to expand...
Click to collapse
I'm not sure about rooting - on my other phone I used Super1Click (but I almost never touch stock ROMs). I already replied to someone else - you'll most likely need to change the kernel for this ROM to work...
---------- Post added at 02:59 AM ---------- Previous post was at 02:51 AM ----------
adfad666 said:
For real? My girlfriend has this phone, and she has been jealous of the CyanogenMod on my Optimus One ever since I installed it. This should make her happy!
She currently uses the SmartLucky 2.2 Rom developed at androidworld.it, did you work on that too / reuse some of their mods or is this an independent job?
Click to expand...
Click to collapse
This is built entirely from source; SmartLucky's ROM is based on the stock ROM with "hacks" (I don't mean that in a bad way - I just mean that no source compilation / recompilation is involved). I used the Ideos Dev Team's CyanogenMod device overlay to begin my port, as the hardware is very similar.
I'll get it flashed for her tomorrow probably and let you know if there are any problems.
Request for info: since this is a low end phone, how much free memory is there after flashing, and (roughly) how does it perform vs stock? I noticed a big jump from stock froyo to CyamogenMod 7 on my O1, but not as much of an improvement from stock froyo to SmartLucky, but then that is also based on a stock froyo rom...
Thanks a lot for this!!
Click to expand...
Click to collapse
Memory usage will always be higher on a Gingerbread ROM (which CM7.1 is based on) compared to Froyo. First boot is a bit slower than Froyo due to comparatively more services being executed, but once it's loaded, in my opinion, performance is as good or better than Froyo. Just keep in mind that SmartLucky's kernel is overclocked - mine is not (yet).
I completed the port in two days, and released just under 2 days ago, so I haven't exhaustively tested everything yet. I've switched back to stock to try to reverse-engineer the stock FM radio's code. There may be some problems, but I will be maintaining the port and releasing fixes to any issues encountered.
I installed this on my U8180 and it works amazingly well. Didn't have to change a single thing.
Wifi, GPS, camera, hardware and touch buttons all work.
It does take a little longer to boot but once it is running it is much more responsive.
Only found one issue so far and that is with LauncherPro having to be force closed occasionally, also it has to reload after quitting out of an app.
bradstewart said:
I installed this on my U8180 and it works amazingly well. Didn't have to change a single thing.
Wifi, GPS, camera, hardware and touch buttons all work.
It does take a little longer to boot but once it is running it is much more responsive.
Only found one issue so far and that is with LauncherPro having to be force closed occasionally, also it has to reload after quitting out of an app.
Click to expand...
Click to collapse
Well, that's interesting...
The slow boot seems to be a kernel bug (it's continually trying to mount a virtual .iso file at /data/cdrom/autorun.iso, which doesn't exist). I'll try to remove this code from the kernel in the next release.
So if it works with u8180 can you please explain how to install it step by step? I am a total noob please i really need your help i know nothing about rooting and custom roms, please give me a minute of your time and help me install this custom rom... your help will be a lot appreciated because there are absolutely no guides about u8180 on the whole net.
I rooted my 8180 using SuperOneClick. Google it. Very easy to use. Put your phine in USB debug mode. Settings > Apps > Development.
I then loaded the Amon RA recovery using the ADB method. I can't post linkks here yet but just search for "[RECOVERY] : ClockworkMod Recovery for Vodafone Smart/Huawei U8160" and its on Modaco. That page has links to all the download files you'll need. Pick recovery-RA-u8160-v2.3.img and copy it to your SD card. Also have a copy of the new ROM on your SD card.
When using the ADB method make sure to change the file name in the last couple of steps to match the one you downloaded.
Once that it done make a nand backup of your phone from recovery. Vol Up and Down to change option and Power to select.
Once that is done you use the option to flash from zip on SD card. Select the right file from your SD and let it do its thing and then reboot.
The first boot can take quite a while, but once you see the Cyanogen bootscreen you should be good.
Hopefully that makes sense.
YAY!! I rooted it! thanks very very much! Had an issue with drivers but found this : theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
Reported Issues:
Issue: It gets stuck on waiting for device…
Solutions: Try these solutions, starting with the first then retry, then the second and retry, and so on until it works.
1. Check to make sure USB debugging is checked on in Settings > Applications > Development.
2. Close the rooting program. Turn off your phone (keeping it still plugged in). Open the rooting program and click root. Then turn on your phone and see if it continues.
3. Close the program and unplug the phone. Download and install PDANet and follow it’s on screen directions to get it to install the drivers manually for your phone. Once it is done installing, plug the phone in and reopen the rooting program.
4. If that still doesn’t work, then go to our How To Setup ADB Procedure, finish it and return here to start over.
Click to expand...
Click to collapse
Now its rooted, I'll continue and tell you what happens
subpsyke said:
This is built entirely from source; SmartLucky's ROM is based on the stock ROM with "hacks" (I don't mean that in a bad way - I just mean that no source compilation / recompilation is involved)
Click to expand...
Click to collapse
The SmartLucky ROM does feel a bit hacky and comes with too many unnecessary apps preinstalled in my opintion.
subpsyke said:
Memory usage will always be higher on a Gingerbread ROM (which CM7.1 is based on) compared to Froyo.
Click to expand...
Click to collapse
Do you have any recommendations for App management with this ROM? I use Link2SD, can I assume this won't be a problem on the compiled kernel?
subpsyke said:
I completed the port in two days, and released just under 2 days ago, so I haven't exhaustively tested everything yet.
Click to expand...
Click to collapse
That's pretty darn fast! I had been thinking of trying something like this myself, I just hadn't got round to it yet, work is very busy this week, but we've only had the phone a couple of weeks anyway.
Thanks!
WOAHO!!! Installed cyanogen on the huawei gaga u8180!
THANKS VERY MUCH subpsyke AND bradstewart!!! You're the best guys!!!
So, here is what I exactly did:
1 . Disconnected the phone, installed PdaNet for the drivers
2 . Downloaded SuperOneClick, connected the phone, Setting > Apps > Developpers > Enabled usb debugging and rooted it.
3 . Got fastboot.exe AND AdbWinApi.dll from the Android SDK zip, got recover.img from megaupload.com/?d=IK2UYQF9 , put them all in a directory called fastboot and placed it in C:/ (wich makes C:/fastboot) runned CMD and typed:
Code:
cd C:/fastboot
fastboot flash recovery recovery.img
fastboot reboot
4 . Once recovery installed, picked adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll from SuperOneClick zip file and put them in a folder called adb and put it on C:/ (wich makes C:/adb/). Opened CMD and typed:
Code:
cd C:/adb
adb shell reboot recovery
5 . Now, in recovery mode, I backed up the system then rebooted the phone, took the backup directory from the SD card and put it in a safe place.
6 . Placed the "update-cm-7.1.0-RC1-u8160-v0.1-signed" zip file (downloaded from the first post on this thread) on the SD card
7 . Another time, runned CMD and typed
Code:
cd C:/adb
adb shell reboot recovery
then installed the ROM
8 . Cyanogen screen is here!
I don't know if I'll have other issues because I think it took 5 minutes until now and still booting... I'll give you updates.
EDIT: I had to wipe my data (something that I forgot) and also installed google apps for the android market
NOW MY PHONE IS BLAZING FAST AND RESPONSIVE, EVERYTHING RUNS SMOOTHLY AND I ALSO GOT THE ARABIC SUPPORT YOU GUYS ARE AMAZING I LOOOOOVVVVVEEEEE YOUUUUUU!!!!!!
U8180
UPDATE: thanks bradstewart !! U8180 booting cyanogen mod 7 use recover.img from megaupload.com/?d=IK2UYQF9
@ wassgha and subpsyke
sorry for my bad english
rooting and clockwork recovery (android.modaco.com/topic/341329-recovery-clockworkmod-recovery-for-vodafone-smarthuawei-u8160/) works fine.
but i get errors at "update-cm-7.1.0-RC1-u8160-v0.1-signed" zip file
screen output:
Finding update package...
opening update package...
Installing update...
assert failed: getprop/"ro.products.device" == "u8160"
...... etc. etc. ........
Installation aborted.
toggle signature verification and scripts make no difference for me. my noob "hacking" build.prop not working
had to try this on the vodafone smart tested all the functions so far and had no problems at all very good work mate the rom runs smooth and all.
The only thing that is bugging me is that the google apps package does not install gmail, youtube, maps etc maybe i am doing it wrong it just only install the market
the steps i did was
a) create recovery (worked fine)
b) wipe data / cache and install rom (worked fine)
c) same as rom select zip from sd card chose the package for google apps that is compatible with cm7 and installed
i then booted the phone and connected my phone had to choose the packages but it will not install gmail, maps etc it says there not in market any ideas how to fix this problem mate
jajajim said:
@ wassgha and subpsyke
sorry for my bad english
rooting and clockwork recovery (android.modaco.com/topic/341329-recovery-clockworkmod-recovery-for-vodafone-smarthuawei-u8160/) works fine.
but i get errors at "update-cm-7.1.0-RC1-u8160-v0.1-signed" zip file
screen output:
Finding update package...
opening update package...
Installing update...
assert failed: getprop/"ro.products.device" == "u8160"
...... etc. etc. ........
Installation aborted.
toggle signature verification and scripts make no difference for me. my noob "hacking" build.prop not working
Click to expand...
Click to collapse
Try flashing the RA recovery instead of the Clockwork one.
Kannibalism said:
had to try this on the vodafone smart tested all the functions so far and had no problems at all very good work mate the rom runs smooth and all.
The only thing that is bugging me is that the google apps package does not install gmail, youtube, maps etc maybe i am doing it wrong it just only install the market
the steps i did was
a) create recovery (worked fine)
b) wipe data / cache and install rom (worked fine)
c) same as rom select zip from sd card chose the package for google apps that is compatible with cm7 and installed
i then booted the phone and connected my phone had to choose the packages but it will not install gmail, maps etc it says there not in market any ideas how to fix this problem mate
Click to expand...
Click to collapse
I resolved this by installing Market Enabler from then market and then fakin a USA market. That will show the google maps, gmail and youtube apps on the market when you search for them
u8150
does this rom work on my u8150 phone?thNKS IN ADVANCE!
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card formatted to ext4 before flashing!!!! This can be created with either CWM recovery or with TWRP. gparted on Linux should also work. If you "SD card not supported" try repartitionning. If you get "Encryption unsuccesful" then you need to format the second partition as ext4 (or f2fs, your choice).
If on a BML rom (stock-based GB)...
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash SuperSU whenever
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
Bluetooth only enables from the notification pulldown, not when you go directly to settings. It does work just fine afterwards though
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Video Recording
Automatic Brightness
Encryption
Compass
GPS
Headset Buttons
Semi-Working
Powered-off charging animation - works at first, but then stops working. Seems to be an Omni problem, but it still charges...
What doesn't
SElinux is currently in permissive mode. Will not be going to enforcing, this would require a data wipe as well
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
Unofficial Omnirom 6.0 for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: OmniRom
Version Information
Status: Beta
Created 2016-01-11
Last Updated 2016-05-12
Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-6.0 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree (create the local_manifests folder if necessary).
After syncing the source, open a terminal and in the directory where you downloaded the source code type "./device/samsung/aries-common/patches/apply_patches.sh" to apply the patches necessary to have a working build. Then run "source ./build/envsetup.sh" and then "brunch galaxys4gmtd". For future builds, only the envsetup and the brunch parts are necessary. Please note that you will have to re-run the apply_patches.sh script after each time that you run repo sync. (Note: the patch script no longer runs automatically)
You should be able to use my trees for other first-gen galaxy S devices. You will need to apply a patch similar to https://github.com/xc-racer99/andro...mmit/fe6bc6b82881a12fc4a5647812f3cf0f52f79c6a to your device tree (if coming from Omni 5.1). I haven't done anything to P1 trees and may have broken the kernel for it...
Changelog
2015-12-20
Initial pre-release - many bugs
2015-12-26
Second pre-release - fewer bugs, but still plenty
2016-01-07
Initial actual release. Quite stable with minimal bugs
2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
Added T959P build
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
Added download mirror thanks to @FBis251
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Changelog for 2016-02-29
Updated Omni source - plenty of new features
Low-resource spinner from LegacyXperia (means that the loading spinner isn't the only thing using the CPU)
Miscellaneous performance tweaks (see github if interested)
md5sum for T959V: a7aa8cca3259208eafba7c2cccecdbfd
md5sum for T959P: 879256c93a0e58de0fb9c9e1be91e0e9
Changelog for 2016-04-02
Security fixes in the kernel
Freed roughly ~4MB of RAM in kernel
Updated android drivers resulting in better multitasking
OpenDelta updating system removed as we weren't using it (it used ~3MB of RAM)
Recents menu now has less lag when opened
Selinux contexts have changed. It could likely be put to enforcing now but this would require a complete data wipe so its still permissive
Live Wallpapers removed - we're low-ram
Bootanimation now fits the screen better
PowerHAL removed - it was broken and has been for a while...
Misc other changes - if you didn't notice problems, you won't notice the solutions
Known bug - Camera on T959V is broken...
md5sum for T959V: 247a721f4c27c5191a2a460e4c72ba3b
md5sum for T959P: d15339d8aa10f765155bdd8d1bb0c5f5
Changelog for 2016-04-08
Fixed camera on T959V
Security patch level of April 2, 2016 (latest to date)
Headset buttons fixed
T959V md5sum: 2b1560b99402c73275d1f69b3ceb9a22
T959P md5sum: e102cce0d624383fb85a32321c98c645
Changelog for 2016-05-09
Uses CMA kernel by default
Performance Control can now modify voltages
Systemless SuperSU is now supported
WebM playback is now working
EFS backup in TWRP now works
Data on boot should now work - no need to toggle airplane mode anymore
md5sum for T959P - 118789dd68760d9fd18cc961398bf346
md5sum for T959V - f9375a8d9792c3a0d222c113213c014d
Changelog for 2016-06-07
Security patch level of June 1, 2016
Microphone mute now works when in call
Battery now charges to 100% and should read properly after a system crash
Standby times should be improved
Slightly less RAM - but should result in better graphics performance
CMA crashes fixed (at least, I haven't crashed once since I started testing the patch a week or so ago)
PowerHAL is back - CPU is boosted when turning screen on to avoid delay
md5sum for the T959P: eeed77fb84189e84f2264e32d18ce454
md5sum for the T959V: b6457319d248029429183c342514b072
Changelog for 2016-08-02
First unified build (ie it works on both the T959P and T959V)
Screen recording now works in portrait mode
MMS should be able to be sent when data is disabled (will still use data though)
Default Camera app portrait photos are no longer square
SuperSU systemless updated to 2.76
Slightly less audio latency with UI sounds (and some sounds have changed)
Data should also be working on boot
Slight changes to battery and graphics config
Security patch level of August 5, 2016 (I'm a time traveller...)
md5sum: df587e0bd69552e0ece4b4ba3e214f45
Source, Downloads, Misc Notes
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-6.0-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-6.0 branch). The patches folder holds all the necessary patches along with a script to apply the patches.
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-6.0 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-6.0 branch)
Downloads!
All builds are found at https://drive.google.com/folderview?id=0B7vXjzo0Hj-iOGJ4dmdCd09OZmM&usp=sharing. As well, recent builds are mirrored on https://files.fernandob.com/#xc-racer99/Omni6.0
Gapps
Gapps cause the first boot to be very, very laggy. Things do improve after that. The best way to get through the Setup Wizard (IMO) is to skip everything possible (ie connecting to Wifi, settings up a Google Account, etc) and then reboot. You can manually add a Google Account later in Settings. While any (small) Marshmallow gapps should work, I have had success with OpenGapps pico package from www.opengapps.org (untested on recent builds).
SuperSu
SuperSu can be found at http://forum.xda-developers.com/apps/supersu. If on May 2016+ builds, systemless 2.71 works (other systemless versions may work, untested). If you're on an older build, you need to either force system mode (create a file in /system or /data called .supersu with the contents "SYSTEMLESS=false") or use an older version (ie version 2.52 or earlier). August 2016 build updates the systemless to 2.76.
Woooow thanks
As you suggested, Gapps caused lots of problems...made the ROM very slow and laggy, lots of FC's, lots of random reboots, etc. I re-flashed without Gapps. Was able to restore apps with TB and root with SuperSu. The basics...calling, browsing, messaging, camera...are working fine. Haven't taken it for a ride yet, but GPS test picked up 5 satellites and I haven't even taken it outside yet. If I desperately need another app, I guess I can find the .apk somewhere. Since I did a TWRP backup, maybe next week I'll try the pico gapps again and see what happens. At any rate, wonderful work.
Update: Took it out for a spin this afternoon....GPS works fine.
Been running the 1/7 for a few days. loving it so far
New Build Uploaded!
Alright, I've uploaded a new build
Changelog for 2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
I've also uploaded a T959P build as I had a request for one. Let me know if you guys find any more bugs.
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
DickyG said:
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
Click to expand...
Click to collapse
Sounds good. Do note that when/if you flash gapps, you will need to do a complete data wipe first, otherwise you will get force-closes like crazy.
I've always just reflashed SuperSU manually and never relied on the script to restore it so I can't help you there.
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
SuccubusInc said:
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
xc-racer99 said:
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
Click to expand...
Click to collapse
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Installing '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: run_program("/tmp/updater.sh") = = 0
E:Error executing updater binary in zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Error flashing zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Updating partition details...
Click to expand...
Click to collapse
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
SuccubusInc said:
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
Click to expand...
Click to collapse
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
I'll try out Blastoff if I can find it. But it probably failed because I did not partition my sdcard. I'll see if that helps later.
Thanks a lot.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
Hey, xc-racer99, after about four assorted blind attempts at installing your work, I flashed back to stock/AntonX kernel with Heimdall and full wiped, then used CWM to create a 4GB partition on my sdcard. The ROM installed through CWM, then TWRP without an error and booted up after fifteen minutes or so of OMNI animation, and is running on my SGS4G without any issues. The only noticeable lag was for the first five minutes after the initial boot. Now my device is gliding smoothly after a few tweaks in the performance settings and turning off background processes. Thank you so very much.
Next time, I'll read the entire post before blundering through the install process with the assumption that I know what I'm doing [as usual].
Sorry for the trouble, if indeed I was any.
xc-racer99 said:
Alright, I've uploaded a new build
Changelog for 2016-01-23
...
Fixed Google Play (and other apps) download error (I think...)
...
Click to expand...
Click to collapse
I tried Pico gapps and the store works perfectly for me now. Thanks!
New Build Uploaded!
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Wooow...thanks
xc-racer99 said:
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Click to expand...
Click to collapse
Finally got pico gapps to run...the initial setup took quite a while but now that it's settled in, no problems. It's also interesting to note that Link2SD is running fine while it seems to be a major problem for other Lollipop & Marshmallow ROM's on other devices.
This is the Official Jaguar rom for Amami, which is based on AOSP with some flavors from Slim and Dirtyunicorn. The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5 built with UBERTC 6.0; hardened rom built with HYPERTOOL 5.4
2. All ciphers enabled in kernel instead of just a few
3. Hardened/Fortified Bionic and Libs
4. Fstack protection strong to resist buffer overflows
5. Many System apps and processes are made read-only, to reduce elevation of privilege
6. Selinux replaced with Tomoyo Security, Yam security
7. Disc encryption, keymaster to 256 bit AES instead of 128
8. Latest TWRP with working brightness and ability to decrypt Data
9. Random number generation mixed hardware/software, as recommended by Linus Torwalds
10. Options to randomize host on every boot
11. Option to have a separate password for lock screen and boot
12. Qualcomm's Time Services disabled due to leaking on early boot (set time to automatic to get it from your carrier). Forget it. The rom now includes Sony TimeKeep that sets the time locally
13. WIFI Background Scanning disabled to prevent leaking
14. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
15. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
16. GRsecurity features, such as Sidechannel implemented
17. Some Pax Security Features
18. Option to deny USB connection: denied always; denied when locked; and allowed always
19. Hardened webview with Google and other "interesting" IPs removed
20. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
21. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
22. Camera hardware button works to focus, take pictures and start video recording
23. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
24. Option to disable continuing writing of logcat
25. Option to disable device cameras: back; front, both or none
26. Always latest Google Security Patches
27. Always latest Code Aurora Security Patches
28. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
29. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10 that has Down Syndrome, but Linux/Google/Code Aurora one)
30. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
31. Many more security features ported from Linux and Copperhead OS
32. Dns Crypt: a feature allowing to choose among many Dns providers (all encrypted)
33. Seccomp: secure computing enabled in kernel
Other features include: Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Supersu included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings; FM Radio and Recording plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. TimeKeep is ported from MM/N. Now time is set locally without the Internet or GSM signal. You need to set it once only and then TimeKeep will keep it current on each reboot, even if Airplane mode.
5. GAPPS: in order to escape f/c, you need to flash GAPPS right after the rom without reboot. If you reboot, you will have problems.
6. If you came from Kitkat directly to a custom LP (without having stock LP at least once), you might experience problems with hardware: gps/wifi irregularites. This applies to any custom rom above Kitkat. To remedy this, flash unmodified Sony stock LP 5.1.1, boot the phone and let it settle. Then you can reboot into fastboot and flash TWRP recovery. Then you can flash Jaguar
Download: All updates and change logs are in Post #3 now
Instructions:
1. You must have flashed and booted stock LP 5.1.1 once to upgrade your hardware (see explanation above)
2 Have TWRP (fastboot my unofficial version), unlocked bootloader and root
3. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
4. Flash the rom
5. If you use xposed, flash the latest installer (As of October 2016 no longer works due to multiple implementations from Nougat)
6. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
7. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault. :laugh:
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Sources: https://github.com/AOSP-Argon/android_kernel_sony_msm8974
XDA:DevDB Information
Jaguar Amami LP 5.1.1 r37 Official, ROM for the Sony Xperia Z1 Compact
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP Slim DirtyUnicorn
Version Information
Status: Stable
Created 2016-06-11
Last Updated 2017-02-09
I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...
Some screenshots: http://forum.xda-developers.com/showpost.php?p=62560391&postcount=2
February 9. New release:
1. February Security patches
2. DNS_Crypt (in settings/security)
3. Seccomp (secure computing implemented in kernel)
4. Open Source Superuser integrated
5. Silent SMS notification enabled
6. 1440p profile in camcorder added
7. Sony TimeKeep: now time is set locally without the Internet or GSM signal (you need to set it right the first time only)
8. Updated TWRP that now works with TimeKeep
If you enable Dnscrypt and you use Afwall, allow internet for apps running as root...
If you prefer closed source Supersu, just flash the zip...
Download Rom: https://forum.xda-developers.com/devdb/project/dl/?id=23073
Download TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=23070
______________________________________________________
January 12: Updated release that includes a fully working NFC-HCE for Android Pay. It may be possible to bypass Safety Net by deleting Superuser or Supersu with su binary, as Lollipop doesn't have dm verity. Although, if the check includes bootloader status, you may be out of luck.
You may flash dirty on top of the previous Jaguar release.
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22567
_________________________________________________________________
January 6: New release with January security patches from Google and Code Aurora. Also, qcom time service is back.
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22449
You can flash on top of the previous release. Otherwise, read the OP (fresh install).
____________________________________________________________________________________
December 10. Rom updated to include:
1. December security patches
2. Signature spoofing (like in Omniroms)
3. USSD fixed (maybe)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22005
__________________________________________________________________________________
November 11. Rom updated to include November Security Patches. I have also removed Supersu, as there is a built-in root manager and quite a few people no longer trust the Chinese owned Supersu.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21448
________________________________________________________________________________
October 5. New release:
1. Kernel overclocked to 2803: experimental, I have used it for 10 days on Z1 without problems
2. October security patches from Google and Code Aurora
3. Over 80 commits from Google Master Gerrit which included changes to bionic, art, frameworks and system
4. Updated Afwall
5. Maybe more
This rom is now about 40% Nougat. One of the side effects: Xposed framework no longer works, but getting rid of it and instead using Privacy Guard is almost as good. Don't forget, Xposed is an exploit, which provides hooks for good and bad things.
Rom Download: http://forum.xda-developers.com/devdb/project/dl/?id=20791
Afwall/Kernel Adiutor Download: http://forum.xda-developers.com/devdb/project/dl/?id=20790
You can flash dirty if on a previous release
_________________________________________________________________________________
September 8. Rom updated to include:
1. September Google security patches
2. Latest Code Aurora patches https://www.codeaurora.org/projects/security-advisories
3. MPdecision is permanently disabled due to interfering with other hotplug and CPU frequencies. Default is MSMdecision, but you can pick several others in Kernel Adiutor
4. CPU overclock and underclock removed: no benefit whatsoever
5. More hardening ported from 3.18 kernel: https://android-review.googlesource.com/#/q/hardened,25 You won't find those on any rom custom or stock. This is from 3.18 kernel and it has nothing to do with Sony
6. About 70-80 commits from Android Master Branch. Folks. This is no longer a lollipop rom
7. PXN security feature implemented, which takes advantage of special instructions on ARMv7 to prevent unprivileged execution. See here: https://android-review.googlesource.com/#/c/265892/
8. Further integration of VOLTE
9. Kernel Adiutor: author has decided to go with Mobile Ads/Adview/Adbanner. So these were removed...
10. Camera: improvements to camera wrapper (missing entries), as well as some modifications in /frameworks/av/camera, so, you have a sharper picture. See photo attached, although, XDA reduces pictures... . This was taken with Open Camera.
Maybe more...
WARNING: you need to do one thing after flashing the rom: flash the latest stock baseband. BASEBAND ONLY. If you don't, you will only have LTE: no H+/H/2G. This is a one-time procedure and is due to Volte implementation. You have been warned. First flash the rom, then reboot, then flash the latest baseband. I don't want to hear cries: where is my 3G!
Download Rom: http://forum.xda-developers.com/devdb/project/dl/?id=20290
Download Afwall/Kernel Adiutor:http://forum.xda-developers.com/devdb/project/dl/?id=20288
You may flash dirty if on a previous release. Otherwise, clean flash...
So far so good but I noticed some bugs which come from CM trees - The scrolling is laggy (this fixed it http://review.cyanogenmod.org/#/c/109956/ ) screen is flickering with low brightness ( I made a fix but looks like I'm not able to complete it https://review.cyanogenmod.org/#/c/106545/ ) and WiFi Mac is wrong (starts with 00:00 and I think this commit fixed it https://review.cyanogenmod.org/#/c/117270/ ) Otherwise great ROM and thanks for the work!
optimumpro said:
This is Official Jaguar Rom LP 5.1.1 r37 which enjoyed over 4000 downloads at Xperia Z1 thread. Jaguar is the only LP rom that is being actively developed and maintained, which means latest sources including June security patches...
Important Disclaimer: I don't have Z1 compact, so, although unlikely, you may have non boot issues. So, back up your prior rom and don't complain, as for the purposes of Z1 compact, this is an experimental build...
As you all know, MM is still in bad alpha state, not to mention horrible camera and it will NOT get any better for many reasons such as: idiotic switching to AOSP (instead of CM) trees; and CM abandoning AOSP in favor of its own closed source OS. Pure AOSP has NEVER had a stable Z1 rom for any version of Android be it MM, LP, Kitkat or even Jeallybean. So, forget about MM. It is bad and isn't getting better.
Click to expand...
Click to collapse
Thanks for the rom, I look forward to trying it out. I must say, though, that we have seen at least a couple of AOSP/AOSP-based ROMs for our device that are developing nicely - fully functional and with good cameras. See DU by @SpiritCroc, and AOSP by @freexperia.
However, as far as CM goes, you're quite right. Several nice ROMs, but little camera progress.
Syssx said:
So far so good but I noticed some bugs which come from CM trees - The scrolling is laggy (this fixed it http://review.cyanogenmod.org/#/c/109956/ ) screen is flickering with low brightness ( I made a fix but looks like I'm not able to complete it https://review.cyanogenmod.org/#/c/106545/ ) and WiFi Mac is wrong (starts with 00:00 and I think this commit fixed it https://review.cyanogenmod.org/#/c/117270/ ) Otherwise great ROM and thanks for the work!
Click to expand...
Click to collapse
In Kernel Adiutor use Ondemandplus, multicore power saving disabled. Set timer_rate at 33000. Don't use mpdecision, instead use Msmpdecision hotplug with idle frequency set at 1497. Use intelithermal. You will also have cpu and gpu overclocked to 2457 and 600 respectively. Also voltage changing is in kernel. Screen flickering does not exist on Z1. I will look into it...
Edit: those old commits were in from the beginning...
12. Mandatory use of Afwall (no internet unless Afwall is activated)
Click to expand...
Click to collapse
Afwall+ has never worked right for me. It actually blocked some apps explicitly whitelisted, and some blacklisted apps would still go through it. I know OP is not to blame about this, but making it mandatory is a big "no" for me.
optimumpro said:
In Kernel Adiutor use Ondemandplus, multicore power saving disabled. Set timer_rate at 33000. Don't use mpdecision, instead use Msmpdecision hotplug with idle frequency set at 1497. Use intelithermal. You will also have cpu and gpu overclocked to 2457 and 600 respectively. Also voltage changing is in kernel. Screen flickering does not exist on Z1. I will look into it...
Edit: those old commits were in from the beginning...
Click to expand...
Click to collapse
Flickering occurs while Adaptive Brightness is on and when Brightness slider is on minimum value. Screen (and or backlight) just starts to flicker.
What gapps should I use fro this rom?
I tried opengapps but they make AOSP keyboard crash. (clean install)
Syssx said:
Flickering occurs while Adaptive Brightness is on and when Brightness slider is on minimum value. Screen (and or backlight) just starts to flicker.
Click to expand...
Click to collapse
Disable ambient display: it is broken on lp and wastes battery.
leonmorlando said:
Afwall+ has never worked right for me. It actually blocked some apps explicitly whitelisted, and some blacklisted apps would still go through it. I know OP is not to blame about this, but making it mandatory is a big "no" for me.
Click to expand...
Click to collapse
You need to use built in binaries for iptables and busybox (prefrences/binaries), as Google iptables are modified to allow certain traffic. Afwall is good in preventing all kinds of leaks, but it can't do anything until it runs and it does not run on boot. So, this rom has a script on early init that cuts the internet until the firewall starts. Without it all your internet traffic is routed through an ip like this one: 26.147.196.122.
Cant install Afwall+KernelAuditori.zip md5 failed
is it the reason why I cant use the internet via WLAN or Mobile Data? Because someone has written that a script block all internet traffic till AFWall is started?
com.android.phone FC when I try to set up some mobile settings by long holding the mobile strengh indikator
Edit: com.android.phone FC only in german language and not in english language
Thanks
AlexandreVegetaroux said:
Cant install Afwall+KernelAuditori.zip md5 failed
is it the reason why I cant use the internet via WLAN or Mobile Data? Because someone has written that a script block all internet traffic till AFWall is started?
com.android.phone FC when I try to set up some mobile settings by long holding the mobile strengh indikator
Edit: com.android.phone FC only in german language and not in english language
Thanks
Click to expand...
Click to collapse
You don't flash Kernel Adiutor and Afwall: unzip the file and install as normal apps, as it says in the OP.
With regard to phone FC, change the language to English, set whatever you need and then switch back to German...
Edit: this rom is not based on CM, which only recently implemented localizations/translations. My rom and development is a one person thing, so, it is not possible for me to do all localizations. However, as described above, you can set whatever you want in English and then switch back to your language: the settings will hold
optimumpro said:
Disable ambient display: it is broken on lp and wastes battery.
Click to expand...
Click to collapse
Man I dont think you got me right. The brightness values of CM sources are too low for Z1C (they are using stock ones and not sony ones) - this file is missing from sources with propper settings https://github.com/sonyxperiadev/de...rameworks/base/core/res/res/values/config.xml
//edit// so ive found that the values are here: https://github.com/CyanogenMod/andr...rameworks/base/core/res/res/values/config.xml and as you can see CM uses lowest value of "20" and SONY AOSP sources use "32" ( <item>32</item> <!-- 64 --> from their source)
no internet
no internet conection with this rom.what is wrong?
Syssx said:
Man I dont think you got me right. The brightness values of CM sources are too low for Z1C (they are using stock ones and not sony ones) - this file is missing from sources with propper settings https://github.com/sonyxperiadev/de...rameworks/base/core/res/res/values/config.xml
//edit// so ive found that the values are here: https://github.com/CyanogenMod/andr...rameworks/base/core/res/res/values/config.xml and as you can see CM uses lowest value of "20" and SONY AOSP sources use "32" ( <item>32</item> <!-- 64 --> from their source)
Click to expand...
Click to collapse
This rom has exactly the same value as in Sony that you linked: 10, 32, 64... . . Is there a reason CM abandoned that commit that had 13 instead of 10? But anyway, whatever the values are, don't set brightness to the extreme low and you won't have any flickering...
bubaliana said:
no internet conection with this rom.what is wrong?
Click to expand...
Click to collapse
You have to read the OP: Install afwall and kernel adiutor as normal apps (they are linked in the OP), set/activate Afwall and you will have the internet...
optimumpro said:
You need to use built in binaries for iptables and busybox (prefrences/binaries), as Google iptables are modified to allow certain traffic. Afwall is good in preventing all kinds of leaks, but it can't do anything until it runs and it does not run on boot. So, this rom has a script on early init that cuts the internet until the firewall starts. Without it all your internet traffic is routed through an ip like this one: 26.147.196.122.
Click to expand...
Click to collapse
you mean we need to follow these instructions http://forum.xda-developers.com/showpost.php?p=62560397&postcount=3?
BTW great rom,thanks for bringing it to Z1C section also:good:
broky said:
you mean we need to follow these instructions http://forum.xda-developers.com/showpost.php?p=62560397&postcount=3?
BTW great rom,thanks for bringing it to Z1C section also:good:
Click to expand...
Click to collapse
No. Since that I have integrated the changes in the rom. Right now all you need to do is to install and activate Afwall. It is simple: no afwall, no internet. Yes activated afwall - yes internet.
optimumpro said:
You have to read the OP: Install afwall and kernel adiutor as normal apps (they are linked in the OP), set/activate Afwall and you will have the internet...
Click to expand...
Click to collapse
Thank you for help.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
All of the LineageOS source code is available on their github.
What's NOT working
Camera
Hotspot
Installation instructions
Boot to recovery mode, use TWRP 3.0.2 only as TWRP 3.0.0 reportedly has issues with flashing it.
Do a factory reset.
Flash ROM, then flash GApps, and then flash the addons if any.
Reboot. First boot will take time.
Downloads
ROM - AndroidfileHost
Source
Device Tree
Kernel Source
Credits
@Olivier @AdrianDC
@Agent_fabulous @STRYDER~007
@AdrianDC and all others who worked in development for Sony devices.
XDA:DevDB Information
LineageOS 15.1, ROM for the Sony Xperia L
Contributors
corphish
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Alpha
Created 2018-02-19
Last Updated 2018-06-10
F.A.Q
Q. Why pre-alpha and all?
The reason why this build is pre-alpha, and in other words, simply unusable, is because deep sleep doesn't work, that means the phone cannot be kept idle (it can be if connected to power source). This is a big issue as it renders other (basic) functionalities useless. I wanted to fix this and then release, but have been out of luck. So I decided to release this anyway, just to let people know that work is being done on getting Lineage 15.x work on Xperia L. Even if this fails big time and the project needs to be abandoned, well atleast the people would get to use whatever worked. Ofcourse I am not giving up yet, unless I really really get frustrated. As of this build, flash it if interested, see how oreo looks like, and then flash back the old rom.
Q. What GApps to flash?
I did not use GApps during my testing, but if you want to use, use opengapps (8.0 ARM). Recommended - pico or micro packages. You do need to modify the installer scripts inside opengapps zip, otherwise installation would fail due to version mismatch.
Changelog
20180610 (Alpha 2)
- Fixed mobile data.
- Fixed issue which caused downloads to fail.
- Updated lineage sources.
20180224 (Alpha 1)
- Fixed deep sleep.
- Fixed proximity sensor.
- Updated lineage sources.
20180219 (Pre-alpha)
- Initial release.
Wow,I was excited,until the moment when my phone turned off and on,every 2 minutes,data transmission not working,I count on amendments in future updates.
Thanks dev.
#Taoshan4ever.
thank you bro. been waiting for this for a long time, many cheers to you
Deep sleep issue was present in every LOS 15 rom, especially lenovo roms, Can it be fixed by replacing libsuspend.so from nougat rom, what's actually the issue
kish11 said:
Deep sleep issue was present in every LOS 15 rom, especially lenovo roms, Can it be fixed by replacing libsuspend.so from nougat rom, what's actually the issue
Click to expand...
Click to collapse
In oreo, earlysuspend got removed from libsuspend, and our kernel uses used earlysuspend. So during initial boot (that is our kernel using earlysuspend, and no earlysuspend in libsuspend), device won't comeback on after I turn off the display, even if it was connected to power source.
An abandoned patch does exist though, which brings back earlysuspend support back to libsuspend. With that patch applied, device did comeback on after display was turned off, and it would function normally as long as power supply was connected to it (just like how it does now), deep sleep still did not work then.
Since the patch was abandoned, and depending on it would not be appropriate, I decided to bring autosleep in kernel, which I eventually did, deep sleep still doesn't work
Great!
Thanks for your hard working and not giving up :good:
It's worth testing, at least we can see how it looks like
wow this is a good news, but i think with more 800MB ram taoshan should use android go
Thank you for your hard works:angel: Corphish :angel:
Hope the bug dies soon :laugh:
Alpha 1
New build is up.
Changelog
Fixed deep sleep.
Fixed proximity sensor, now all the sensors should be working as usual.
Updated lineage-15.1 sources - Switched from staging/lineage-15.1 branch to lineage-15.1 branch. Some immediate changes you will notice are the new icons and the addition of Lineage setup wizard.
Now that this has graduated from pre-alpha, and the device can stay awake in idle, this makes the alpha build way more usable than the pre-alpha build. If you end up using this, and face bugs that are not mentioned in the "not working" list, please let me know by posting about it in this thread. Logs would be welcome, but a proper way of reproducing it would be good too.
P.S - Firefox still doesn't work ¯\_(ツ)_/¯
Links updated in OP.
1. device not booting properly using restart in power options, doesn't respond to any action until battery removed
2 flashlight not working, and the flashlight toggle interrupts the music playback.
3 downloads fail using jelly browser
and, cheers for your hard work @corphish, Thank you
kish11 said:
1. device not booting properly using restart in power options, doesn't respond to any action until battery removed
2 flashlight not working, and the flashlight toggle interrupts the music playback.
3 downloads fail using jelly browser
and, cheers for your hard work @corphish, Thank you
Click to expand...
Click to collapse
1. It works fine here, does take a bit of time though. :/
2. Because camera does not work. It will work when camera is fixed.
3. That is because, vold assigns our internal storage name as "7384-14B3" (atleast it looks like that in mine), so storage location for internal storage is "/storage/7384-14B3". Turns out that DownloadManager cannot handle storage locations with such name . Will try to workaround it in the next build.
Now that's awesome and quick. Great work @corpish
I have tried it. It's amazing and fast
But there are some problems
1. Phone restarts when phone get stuck, or when starting camera
2. Music playback stopped when flash light turned on
3. Downloading get unsuccessful in the stock browser
I think other users have already mentioned some of the following problems.( I think the real problem is with the download manager )
4. And there was no gapps for Oreo 8.1.
So I installed a unofficial gapps which was created for 8.1 and the setup keeps closing
I have only noticed these problems yet.
But it's a amazing ROM.
Thanks Corphish
Nikhil kuttu said:
I have tried it. It's amazing and fast
But there are some problems
1. Phone restarts when phone get stuck, or when starting camera
2. Music playback stopped when flash light turned on
3. Downloading get unsuccessful in the stock browser
I think other users have already mentioned some of the following problems.
4. And there was no gapps for Oreo 8.1.
So I installed a unofficial gapps which was created for 8.1 and the setup keeps closing
I have only noticed these problems yet.
But it's a amazing ROM.
Thanks Corphish
Click to expand...
Click to collapse
I have the same problems
Split screen is not working.it says not supported in any app even sys app.
And casting is not working as well.just after connecting it closes and search for device again
These are not a major problems
But the camera and flash are little impotent
Nikhil kuttu said:
Split screen is not working.it says not supported in any app even sys app.
And casting is not working as well.just after connecting it closes and search for device again
These are not a major problems
But the camera and flash are little impotent
Click to expand...
Click to collapse
If camera and flash are important then,
Flash Back !
I wont change my OS just to get camera and flash
Working again.
Even while it's in alpha stage I really like this Rom:laugh:
The app's stay in the same position even after long time
And now I'm using mostly Google go edition app's to keep the device fast as possible
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
- mtp buggy
Links
SM-T320
12. 20210419: april security patch: https://drive.google.com/file/d/1HkZcWDD9U7D6l_EfFjc_nZ4tHyNlNnwO/view?usp=sharing
11. 20201220: december security patch: https://drive.google.com/file/d/1QxdomNPRsng-_xpBqusRyMXurusx8QOl/view?usp=sharing
10. 20200815: august security patch: https://drive.google.com/file/d/1XAMxA7fAZs5EvBFo1429AdmRybWAIHIJ/view?usp=sharing
9. 20200724: july security patch: https://drive.google.com/file/d/1IdIzEMHrJdF2Q6H9YBcBSfigEB7-UDBf/view?usp=sharing
8. 20200614: june security patch: https://drive.google.com/file/d/1mlYZh-LP0gG8PTT-Hzp8jRC6YRhDJy62/view?usp=sharing
7. 20200523: may security patch, small sources rebuild, back mixer from t320 with video recording fix: https://drive.google.com/file/d/1Bhbk06ku5Svv8MFo3ul2PdHvgRJuErOU/view?usp=sharing
6. 20200412: april security patch, kernel update: https://drive.google.com/file/d/1YgrUvgEHy9K-igM99VAaiXM6Z1SLE3qY/view?usp=sharing
5. 20200212: latest sources, February security patch: https://drive.google.com/file/d/1pbyMFiNEYn4Wqz-N5na95tJvahj5qsju/view?usp=sharing
4. 20200114: latest sources, January security patch, rollback to our old wlan driver (if you have issues with this one - please apply wlan patch): https://drive.google.com/file/d/15cLT0Re3LA5yMLVaPNdfIkG6VCJ8oxQh/view?usp=sharing
3. 20191215: https://drive.google.com/file/d/1OmUxocOWKI2ivN7SjSMrNo-QRIy5fOAh/view?usp=sharing
2. 20191210: latest sources: https://drive.google.com/file/d/16Jfe9kss4yEOhb9sVTduWAOsTlYledmw/view?usp=sharing
1. 20191204: initial build (latest code, new wlan driver (3.8.20.24, old was 3.2.3.172)): https://drive.google.com/file/d/1wrUSp-408XmDTtglvx43jM3Zcfujebkt/view?usp=sharing
SM-T325
12. 20210419: april security patch: https://drive.google.com/file/d/1GDmT5lNQtRM_2xqNHWkvlbGP6MJA6L7U/view?usp=sharing
11. 20201220: december security patch: https://drive.google.com/file/d/1JYdx4EqrJ5Jx1Qd6odjtan5N5ex6QyVK/view?usp=sharing
10. 20200815: august security patch: https://drive.google.com/file/d/19J34mHO3KKPoAUoqIAqok52zRaznrZiE/view?usp=sharing
9. 20200724: july security patch: https://drive.google.com/file/d/1WxG7KypUh4ayWwXsNqeggjDbd4Mp_72X/view?usp=sharing
8. 20200614: june security patch: https://drive.google.com/file/d/1zHz-vAbXvHeuZK5Dg19C9pzDNtxsQexv/view?usp=sharing
7. 20200523: may security patch, small sources rebuild: https://drive.google.com/file/d/10sa_B_5Zi-dSQcSRRfDFcjXjd4_OWe6y/view?usp=sharing
6. 20200412: april security patch, kernel update: https://drive.google.com/file/d/1oqyJt94VsQupRpUH--Pb9uN0TKSpWPc_/view?usp=sharing
5. 20200212: latest sources, February security patch: https://drive.google.com/file/d/1XweMgrmDbmi7_pQPSp6PdnYyn743gnfR/view?usp=sharing
4. 20200114: latest sources, January security patch:, rollback to our old wlan driver (if you have issues with this one - please apply wlan patch): https://drive.google.com/file/d/1M6T7KN6ZOZohKFQ7pYCkqeW5SWXm2yX5/view?usp=sharing
3. 20191215: fix internal speaker, bt calls: https://drive.google.com/file/d/1UP5UtOGXBNYft0WPyth4kcSnsCAb_1YB/view?usp=sharing
2. 20191210: ril + mobile data, latest sources: https://drive.google.com/file/d/1HhfoJZP7mLWpZrqx4LO8b3P6m0Br-nVQ/view?usp=sharing
1. 20191204: initial build (latest code, new wlan driver (3.8.20.24, old was 3.2.3.172)): https://drive.google.com/file/d/1GCTDMFphXYx2MLgeLsGq6QWTA60bIJ4s/view?usp=sharing
Wlan patch
if you have wifi problems in the latest firmware - please apply wifi patch: https://drive.google.com/file/d/14qcYQrs2P1x41zz3FR8uwk4nGxlTJWcf/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Recovery
Use official version from:
SM-T320: https://twrp.me/samsung/samsunggalaxytabpro8.4wifi.html
SM-T325: https://twrp.me/samsung/samsunggalaxytabpro8.4lte.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_mondrianwifi and https://github.com/Valera1978/android_device_samsung_mondrianlte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_mondrianwifi and https://github.com/Valera1978/android_vendor_samsung_mondrianlte
Thanks
Thanks to LineageOS team
Thanks to @bartekm01 for helping test SM-T325.
Congratulations to @Valera1978 - working very well on my T325
@bartekm01
Does mobile data works on this Version?
Valera1978, thanks for building Q. I don't have time to download and test Q, but will after Dec 20.
I will move from Pie to Q on that date.
Outstanding job!
Any chance of an SM-T525 build of Q?
Works amazing. I changed animation scale to .5 on all 3 options and it seems speedier and not so choppy. This tablet is still amazing, GREAT JOB Valera1978.
Another happy soul here. This build works flawlessly on T320 and can imagine it will only get better and better.
A minor bug, doesn't bother me at all though. Settings > System > Status bar > battery status style, changing to circle or text doesn't change the battery icon (vertical bar) in the status bar.
Man you are amazing !
an incredible job ....
two small problems, the battery in text format does not work and the voice synthesis is inactive.
Édit: voice synthesis ok with opengapps
dirty flash?
Did you try a dirty flash (LOS and gapps), coming from your LOS 16 version?
Except for the problem that the microphone is very quiet, LOS16 works very well.
What points should be highlighted that represent an advantage of LOS17 over LOS16?
connecting my t320 to pc with usb and choosing file sharing option makes the tablet reboot
WiFi switch on not working on my SM- T 320.
If I switch WiFi on , it changes directly back to off .
I done a Clean install .
bierma32 said:
WiFi switch on not working on my SM- T 320.
If I switch WiFi on , it changes directly back to off .
I done a Clean install .
Click to expand...
Click to collapse
??? WiFi is OK for my T320, gmail and youtube are working fine here !!
or try rebooting with all cache cleared ...
Obing said:
??? WiFi is OK for my T320, gmail and youtube are working fine here !!
or try rebooting with all cache cleared ...
Click to expand...
Click to collapse
here too all working, format data before , but no root and magisk causes error on supercell games, and lockscreen still on portrait mode when in landscape. netflix 6.26.1 works too. thanks again for all effort
Awesome tried open gapps (11/14) first but it had bugs with various features (setting icon don't work in notification pulldown), setting up lockscreen and probably a bunch of other bugs.
BitGapps seem to work good so far (although no first setup screen), overall rom is fast and smooth, it doesn't pass safetynet but not a big deal, thanks again for making this happen, amazing we have 10 on this device now.
Installed all my usual apps and no apparent issues, camera, and video also work!
Wifi (5ghz) seems very stable with new driver, and even gets better range.
OK update on the safteynet issue, I found that "Petnoire's_SafetyNet_Spoofer" Magisk module made it pass both checks and also the play certification (tried some of the other modules but they failed to make it pass).
You can either use his stock module (which will set it to a xiaomi device fingerprint) or use my modification (which will make it a SM-T320), I only modified it to use the correct build fingerprint for this tablet, so yea rom is fully awesome now
(after installing the module and rebooting , don't forget to force stop the playstore and clear both cache and storage)
this might also work on the Android 9 rom too, but I have only tested it on 10 so far.
Not working on latest build: will see if I can fix.
T325 full wipe + Data format.
TWRP 3.3.1-0 (without EFS backup option although found acc to recovery log of LOS 13) to flash ROM, BitGapps + Magisk gave an error 1 for Magisk.
Had to flash it separately to get it working.
Started without logon screen to Google which was fine for me.
IMEI + SIM gone and no mobile data.
With Odin 3.13. back to Stock -> got my IMEI back with mobile data as well.
Reflashed TWRP + LOS17 gapps and, in a second flash, Magisk.
WiFi is fine but again neither SIM nor mobile data.
EFS partition still existing.
Am not able to install saved apps with totalcammnder although it's a secure source.
Always telling me it can't open the file even the freshly downloaded XDA-labs.apk.
Installations from Playstore and F-Droid working.
bierma32 said:
@bartekm01
Does mobile data works on this Version?
Click to expand...
Click to collapse
No. RIL not worka at this moment
bierma32 said:
WiFi switch on not working on my SM- T 320.
If I switch WiFi on , it changes directly back to off .
I done a Clean install .
Click to expand...
Click to collapse
I also have the same problem with my SM-T320 after a clean install. My WiFi just doesn't want to turn on.
@Valera1978 can anything be done about the microphone volume? I record video but can barely hear anything on playback.
Screencast/Miracast is also broken system softreboots when trying to connect., not sure if these are fixable but just thought id let you know
.