Teamhacksung just released CM9 Alpha (Build 15).
I am currently on Team ICSSGS RC3.1 release and very satisfied. I even managed to work out a known issue about the screen flashing for a split second after locking screen by flashing the Devil Kernel.
Is there anyone else in my shoes who's considering going over to teamhacksung's release? Anyone tried them both?
I would like to see how many soldiers each side has and compare opinions
It's like comparing apples to oranges.
cspiby said:
It's like comparing apples to oranges.
Click to expand...
Click to collapse
i ve read that same quote somewhere before and i dont get it.
they re both designed to bring ics to i9000, therefore to me they fall under the same category
(i dont care much about the code differences and the ideology that each has adopted, i just care for which one is the most stable ICS rom for my phone)
and btw, i dont mind comparing apples and oranges, i hate oranges, i love apples
use cm9.issues are less.won't bug really bug u anyway.very stable.plus if u want overclock there
are custom kernels as well.
senotrius said:
use cm9.issues are less.won't bug really bug u anyway.very stable.plus if u want overclock there
are custom kernels as well.
Click to expand...
Click to collapse
The custom kernels work fine on TEAMICS too...
Depends what you want, clean ICS (TEAMICS) or customized (CM9).
senotrius said:
use cm9.issues are less.won't bug really bug u anyway.very stable.plus if u want overclock there
are custom kernels as well.
Click to expand...
Click to collapse
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
cspiby said:
Depends what you want, clean ICS (TEAMICS) or customized (CM9).
Click to expand...
Click to collapse
i dont care much about costumization at this early point. if they were both stable it would a whole other story but now,
i prefer more stable over more customizable. however since build 15 is actually a cm9 alpha now,
i m wondering if it's stability is enough to worth the transition
c0rpse_grinder said:
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
Click to expand...
Click to collapse
this is the reason icssgs is the one for now for me ...
haven't tries ICSSGS yet... working on CM9 foe almost 2 weeks now and its pretty decent... stable too... one thing that bugs me is how little mods are available for CM9 at this point... however CM9 for SGS2 is littered with mods... some quite useful (like ANZO MOD)... whats it like for ICSSGS version?
c0rpse_grinder said:
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
Click to expand...
Click to collapse
Cm9 have more issue because it have more users, and I don't think those are only cm9 bugs, happend on onecosmic's as well
Sent from my GT-I9000 using Tapatalk
cspiby said:
It's like comparing apples to oranges.
Click to expand...
Click to collapse
All based on ICS 4.0.3 source, so why? Because another team ports it to the GS? I think still Apples to Apples and they both do a good job..
onecosmic's team doesn't release all all issue .
CM9 is better and stabler. I traid onecosmic's RC3 and RC3.1 for a while but no that not comparable to CM9.
I am on teamhacksung build 15 and not going back to Samsung ROM or any other ROM because it's stable, smooth and fast.
It has issues and so does others, I can live with it.
Sent from my GT-I9000 using xda premium
im using CM9 alpha RC0 (TH 15)
theres not many working options in the menus yet but ive been getting really good battery life and performance from lulzactive governor after flashing devil kernels. Seems good so far but disappointed that the battery indicator option in the menus didnt work to change the battery icon to percentage. Il probably stick with CM9, big userbase so should keep getting frequent updates
I'm using CM9 Build 15 with Devil Kernel
it works grat =)
I would at this point go for the Teamhacksungs myself. There are a number of reasons, both stability and feature wise.
1. They offer control over visualisations.
2. They have quick setting available on the drop down tray
3. The media duplicate issue has been sorted
4. It doesnt lag and lose stablity when more apps are installed
5. I am not sure this is an experience of others, but I have found Teamhacksungs battery life far superior. (not by a lot though! maybe my battery is failing generally)
There are still a few glitches... I tried to go back to Gingerbread... man, after 5 days on ICS, its not possible to go back. Believe me. ICS is almost perfect.
Reason why I have always went with RC3.1 Over CM9 is because CM9 the text always looks terrible and all pixelated
Does this happen for other people? or just me
My choise is Teamhacksungs CM9 because of its stability and other stuff it has. I am proud user of Teamhaksungs since build 6 and i will never switch to onecosmics and ICSSGS because ICSSGS is built ontop of onecosmic's and both do not display a full list of bugs and glitches they have by only showing "what works" while CM9 offers a full list of what it can and can't do.
CM9 teams doesn't go away if some trolls spam their tread... Cant say the same for Onecosmic..
As I need something I can rely for some time, I prefer to go to the ROM that gives me more guarantees that there will be an upgrade path for the coming weeks...
Other than this I cant compare because I'me using only Teamhacksung builds for some time..
tried both
c0rpse_grinder said:
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
Click to expand...
Click to collapse
Personally, I had more issues with onecosmic rc3.1 (only had it installed for 3 days tbf) - not to say I haven't had any issues with cm9 build15 and build14 for a week before that, but generally I prefer both the stability and customisations of cm9 (eg power widget bar)
The fact that they know of, and are bothered enough to release a list of, the bugs encourages me that they're working on it
Also, I miss pvz but that's down to app incompatability with ics in general...
Related
So, in lieu of Google holding onto the HC source code and me getting fed up with the stock ROM, I am wondering if I should for for Nookie Froyo or CM7 or maybe wait longer...
List of things I don't like about 2.1 rooted ROM:
B&N launcher, I'm always hitting it by accident
No copy/paste (need!)
No Flash support
Overall slow, buggy performance, screen not so accurate (big pain)
App incompatibility, I'd like to try some apps like Firefox or update Maps regularly
WiFi issues, have to toggle on/off to connect
Poor battery life
List of things holding me to 2.1 now:
Notification bar on bottom, with back and menu buttons (this is a big one)
Ability to quickly lock to portrait mode by tapping the clock
And since I only have 2 GB uSD cards, can I completely copy my current ROM with CWM to restore back to where I am now?
Thanks for any input
I suggest you check out CyanogenMod 7 with tablet options from this thread: http://forum.xda-developers.com/showthread.php?t=1002000
[MOD][CM7] Honeycomb features - in progress - updated 03/26
It addresses the features you are concerend with and is great on the NookColor!
Sent from my Droid using Tapatalk
i have tried nookie froyo, Honeycomb and now CM7 on the ineternal memory and personally i find CM7 alot more stable, my youtube works, flash works, bluetooth works, orientation is smoother than others, apps do not seem to over scale/under scale often...oooh yeah my angry birds work, wifi stays connected when coming out of sleep mode, but early way you go you are gonna get some bugginess. but CM7 does not seem to have as many.
CM7 hands down. A fast working community.
> Sent from my Super Clean Fascinate via XDA Premium app <
Well, I dove right in and installed Honeycomb v4 on eMMC and I am super excited for it. I just had to give it a go.
I guess lots of apps aren't really working for it right now?
Which Rom
I use Nookie Froyo (from the sd card) on my unrooted Nook. It works really well gives u access to the market and all that it brings; I have gmail,Gtalk etc. good battery life, and you can just remove the sd card to use the Nook in the "out of the box form".
One of the great things about the NC as it is right now:
there are a HUGE number of ways to try new things.
Personally I am a fan of rooting for the speed gains and ease- once cwm recovery is installed I can flash and revert easily and as needed.
I run CM7 nightlies on emmc (internal memory) and keep important backups (still have rooted stock and at least 2 GOOD, stable backups at all times) and yet test any and all new rom updates and test I choose.
Flash works and video should be perfect in CM7 soon: I just tried the video test build (and wiped data) and reverted back to my nightly with Tablet Tweaks and 1.1Ghz overclock, all configured and ready to go. Nightlies have not YET required me to do a data wipe....
My point being- it is pretty simple to try any and all roms and decide which you want from personal experience.
Hello you all,
Here's a non-official CyanogenMod 9 beta ROM which is almost fully working on our wildfire.
/!\ WARNING /!\ this ROM is currently BETA. Important things work, there are still things that doesn't work and the device is suffering slow-downs
If you can't stand that, make sure you have a nandroid backup to revert to after 'test'.
Please read this first:
I am absolutely no developer. I just learnt how to compile from source, and all that I'm presenting here is the result of the big efforts from the CM9 team in general, and Arco68's more specific - the CM guru for our device.
I cannot be taken responsible for anything regarding this ROM: if it suddenly bootloops, if it looks bad, if certain things don't work or stop working or if your devices tries to bite you mother-in-law and messes up the hair of your fiancée just the day before your wedding - it can be my fault, but it is your own responsibility. So don't come complaining that I screwed up your wedding party - you shouldn't have been occupied with your phone the day before your wedding in the first place.
I greatly encourage everybody to help to make this ROM better. Not only because this ROM has some great potential, but most because it is fun to do (and very addictive, be careful!) and you learn A LOT from it. So If you have find a fix of any kind, post it here and send me a pm so I can update the OP with your contribution. But please: say exactly what you did! This is an open source project and nothing is more frustrating than seeing that a specific problem has occurred on another device as well, and then noticing that people "just fixed it, yeah baby". If you are new to all this building headaches - don't use this thread to start learning how to work with git and github, but personally I don't have no single problem with more advanced questions in which the effort that you have already tried to fix it, can be seen.
I won't be posting changelogs - they are way to much changes to keep track on the ones that effect the wildfire. For recent merged changes, I refer to the gerrit.
Do not complain, but enjoy both the fact that we can run ICS on our low-end device.
This being said: download time!
New build from 2013.01.01: download.
For all previous builds, check my google drive
Custom google apps (no faceunlock stuff, no GalleryGoogle.apk, only non-neon libs => smallest footprint (something like ~4mb)):click and press ctrl-S (Thanks to Sympnotic for making it)
latest "official" gapps :download (goo-inside.me)
MTD partion size
With tiny gapps, /system takes 181 mb -> I use 200 mb to be confortable
With tiny gapps /cache takes 1.2 mb
Updates worth mentioning regarding the Wildfire
General updates. Please note that there are almost no updates, as the CM team is focussing now on CM10.1.
Ported the libstagefright changes for the msm7x27 to match the new OMX IL libraries. I however do not think that it works...
Ported some Trebuchet features from cm-10.1. This is still a work in progress, and I don't know to what extend I will succeed with this.
Fix NPE when rotating
Remove wallpaper offset
Only mark preferences changed when they actually are changed
Fix for NPE in showAllAppsCling
Fix desktop alignment when Search Bar is hidden
LauncherModel: Fix possible NPE
Wallpaper Hack
This doesn't work good yet! In fact, it gives a very interesting phenotype: when you select this, you will not see the homescreen dock anymore (so the buttons for launching the app drawer, ... that are on the bottom of the screen). However, you can still click on them, as if they were there. So you don't see them, but they are there
Workspace: Update wallpaper offsets to match hack for recent apps window
Not (properly) working
Wallpaper hack
Do not set Launcher Drawer's scrolling Transition effect to "Tablet". It reboots your device every time you open the Launcher (thanks to musicazx)
Camera panoramic view
The flashlight option on your camera. It does however work in the camcorder (the native one and Camcorder Illusion)
Playing youtube video's in HD quality (without HD it goes fine)
Gallery (use QuickPic as a good alternative)
Voice-to-text: read this
Data usage is working well, but the "general" graph is showing all blue.
Stuff that works but need resizement
Apollo - but only a bit.
Tips and tricks
Best Overclock settings are between 691 and 768 MHz w/o problems. SMARTASSV2 is the best compromise between performance and battery life.
Tip from Onisciente: If we turn off (Settings > Trebuchet > Applications settings > Widgets : Join with apps. App drawer will be faster; it won't display widgets in App drawer list, "widgets"
If you find Trebuchet Launcher slow, there are some alternative launchers. Nova Launcher is one of them, Apex Launcher & LauncherPro work great
FM radio : should be fixed but for now, use Spirit Free FM (Spirit Free FM thread):
Allow it to have superuser rights
Go to settings - audio - method and select msm7x30
When playing a youtube video, make sure that you disable HD, or it will not play well. You can do that by clicking on the red HD icon at the left of the video. If the icon isn't red anymore, HD is disabled.
Google VoiceSearch: read this.
WinSuk's script for trackball button wake-up is included. To enable/disable it: open terminal emulator, type 'trackballwake', allow superuser rights, wait for the message of success and reboot. ALL credits for this script goes to WinSuk!
Credits goes to
the whole CyanogenMod team
Arco68
And people working on this rom :
Sympnotic
Rallapag
plakiko
Have fun with it!
Erwin
Thanks a lot for this build Erwin,
trying it ASAP.
One Q: are wifi hot-sopt and mobile data working OK??
Mobile data works fine, but I haven't tested the hot-spot functionality yet. So you tell us
I've forgotten to say: if the device asks you re-enter your pin code, you must do so. If it then says that you should reboot your device: just press "back" and most of the time you should be fine. I've noticed however that doing a reboot stops hem from asking it.
Calendar works to sync fine
I'm not going to complain, but this ROM at current stage is only for users with backup phone. Trying ICS is intresting, but for this while unusable for daily use. Even writing messages is a bit sluggish and frustrating. Beta testers will come, and help with testing CM9 for Wildfire, but it must runs with reasonable speed and funcionality
Bonus
Bluetooth tethering working which is a new option in CM9...
If you install it and replace Trebuchet with Nova Launcher and run SetCpu @ 729Mhz, it is running just fine.
Sometimes you've got to look for the alternatives that fix some issues...
Also, in development settings you can set the animations at .5x.
This makes them a LOT smoother!
Bugs I'd like to report:
-All the cyanogenmod settings like those in CM7 are missing
-I don't have any lockscreen for some reason?
-Camera doesn't work
-Phone has a weird layout in Landscape-mode
-Browser doesn't work
-Animations are still laggy
-Rotation animation goes to black screen for a second and only after that it does a rotation animation
-I can't seem to get the Market working, after flashing the .zip mentioned in the first post of this thread
I just don't see a Market-icon in the app drawer...
New update - sorry if you just installed the previous one, but I was testing something and didn't know if it would work. But it does Check it out, lots of differences.
Opson said:
I'm not going to complain, but this ROM at current stage is only for users with backup phone. Trying ICS is intresting, but for this while unusable for daily use. Even writing messages is a bit sluggish and frustrating. Beta testers will come, and help with testing CM9 for Wildfire, but it must runs with reasonable speed and funcionality
Click to expand...
Click to collapse
You are right, I haven't stress that out enough. I update the OP.
Reserved!
Congratulations Erwin! And the CM team also.
I know its just in the early stages but having dedicated people contributing to these project just makes things exciting.
Lets all hope for the best on this project and for our wildfire!
Cheers!
provide the link for the gapps because in OP its not displaying....
installing now......
What's included in the new CM options.
Sent from my HTC Wildfire using xda premium
Use the 28-11-11 gapps ics, those work.
---------- Post added at 12:48 PM ---------- Previous post was at 12:43 PM ----------
http://forum.xda-developers.com/showthread.php?t=1313198&page=23
Oops! they worked fine in the previous version, not the 31-1 one!!!
What kind of mtd partitions work with this rom? I have 150 and something and it doesn't seem to be booting. The last build did boot with the same partitions.
Read the OP, you cannot install gapps due to a lack of space.. I'm working with the standerd MTD partitions.
@ErwinP, I have to say that the new bootanimation looks gorgeous, thanks for adding that
Now I would like to flash gapps on it after I've set some custom MTD partitions.
How large do you suggest the system-partition to be? Since 150 isn't enough... Just don't want to leave too much free space on /system which I could be using for /data...
-How much space does ics gapps need on /system?
-Now much space does your latest build need on /system?
Last build not work for me fine. There are FC's of all, that can FC. I can't open launcher and lock screen. But first build was good.
THX for CM9 build anyway.
P.S. Sorry for my bad English
UPD: Sorry, gapps led to FC's. When i reinstall ROM in third time it loaded perfectly.
ErwinP said:
Read the OP, you cannot install gapps due to a lack of space.. I'm working with the standerd MTD partitions.
Click to expand...
Click to collapse
Yeah lol should have read more carefully. I'm checking to see if the rom itself boots with my partitions.
Edit: It did not and the mtd partitions I was using were 150 10. Had a good time to look at the bootanimaton it does look pretty good
I also seem to have problems with the latest build + gapps to fit on my /system partition.
Now that I think about it, it could be because it's still only 150MB in size since my CM7 flashing...
I'll erase everything, create a new custom MTD /system partition of 250MB which should be large enough.
I'll check out the used size of /system with the terminal afterwards so you guys can optimize your device with the minimal needed /system size...
I guess the use of app2sd will be needed for apps since ICS itself + gapps takes quite some space....
In my default partition size, /system uses 150mb RAM. My partition is 250mb, but yet I can't install gaps because on the first boot, when DexOpting all those google apps, it stops with "Zip inflate: write failed: No space left on device". How big are those apps?
Bar/QR code scanning doesn't work yet. I use the barcode scanner daily, so I'm not ready to make this my everyday rom yet. A paid game from the market - Asphalt 6: Adrenaline from the 10 cent days - wouldn't load because of an OS version error (the app probably isn't ICS-compatible). Outside of these very minor personal gripes, I think the rom kicks ass!
This doesn't surprise me. The actual patch that gets the camera going is just a software hack (and partial addition), which is why the video and panorama modes don't work. With that being said, this doesn't surprise me that the scanning ability isn't working correctly.
with the camera working now, do you know how do you change the default folder location for the images? It automatically puts the DCIM in the internal sd with no option to change location to ext-sd in the camera itself or system settings (unless im just overlooking it, or the newer versions have it), but this is just in case i brick my phone i can recover any default data/images loaded on the ext-sd and not lost inside.
yeah awesome job on the rom though! loving everything about it so far. looking forward to #5.5/6
Beta#2
SlimKat is a V4 (KitKat) ROM by SlimRoms. It's based on AOSP 4.4.4. Its latest release, build 9.0, was Dec-22 2014 with a 3.0.8 kernel.
Its disadvanatges are that it is no longer supported by the Slim dev team; no custom overclock kernels exist for it; no hand-wave for notifications lockscreen feature of the later 5.0+ versions; and there's no support for altpart Safestrap.
But that's where its downsides end and its upsides begin. With nearly any 3rd-party ROM it's a series of tradeoffs. What works and what doesn't, what do you need and what can you do without. Not so with SlimKat. Everything, and I mean everything, just... works. Flawlessly. Even HDMI. This ROM is feature-rich, yet still so lean you can run it with Slim's normal Gapps package on the stock slot. At 180MB, Slim's normal Gapps package is 15MB smaller than the OpenGapps nano package for 7.1.2. I've been running this as a daily driver for over a month and not a single thing has gone wrong with it. No force-closes. No hangs. No jitters. No crashes. No random reboots. This is as close to a stock ROM's stability and performance as anything I've ever used. It's fast and responsive and handles whatever you throw at it. All that and great battery life too - I typically get about 36-44 hours from a full charge.
Support for 4.4.4 is extensive throughout the app community and I have yet to find an app that doesn't work with it. Custom fonts are easily installed with iFont and there are extensive interface and navigation customizations available in the SlimCenter. Cyanogenmod/LineageOS 11 themes are available for it on the Play Store.
The stock SlimLauncher is extensively configurable, and supports gestures, desktop folders, grid size configuration, icon size configuration, hidden apps, hidden icon labels and much more. I prefer a horizontally paged interface for my app drawer, and this one works exactly as this should work, where you swipe left or right and each page of app icons disappears behind the next, rather than a continuous side-scroll. This is especially important on the Droid 4 because of its TFT screen's limitations that make things difficult to read when continuously scrolling against a dark background.
While most ROMs will let you disable some system apps, SlimKat has a SlimSizer app in the SlimCenter settings that lets you save or fully remove any included system app from a simple checklist. SU is integrated and the ROM is rooted out-of-the-box. Google Voice works seamlessly with it. Voice Search starts up quickly and doesn't hang or crash, and interactions with it are predictable. The built-in WiFi hotspot works flawlessly. It natively supports Face Unlock.
Its sole quirks are that the keyboard doesn't illuminate when you slide it open until you press a key, and direct reboot to recovery doesn't work (just do a standard reboot and activate SafeStrap recovery at startup).
Verdict: Hands down, the overall best 3rd party ROM I've tested for the Droid 4. Rock-solid, OEM-level reliability and performance in a compact yet feature-rich package with outstanding battery life. If you don't require a newer version of Android (5+) for app compatibility or features, and don't want the code-bloat of the later versions, you simply can't do better than SlimKat on the Droid 4.
Thank you for this!
I was hoping there were some posts like this, but it being 2018 I wasn't optimistic...
just picked up a droid 4 to have a backup phone and for a bit of nostalgia - I had an OG droid that I kind of miss using
Update: After six months with SlimKat, I'm moving on. There's only one real problem I've had with it, but it's been really annoying. Frequently it just won't wake up the screen - the soft buttons light up, but the screen stays blank. It can often take several attempts before it works, if at all - usually after the third try I just give up and wait it out until the next time I want to check it. This is especially frustrating when receiving a call, as I've often missed calls just waiting for it to wake up the screen so I can answer it. Never been able to track down the cause or figure out a solution.
There's also a strange problem in the file system that there are "ghost" files throughout. Blanks show up randomly throughout my gallery, and duplicates of music and videos also work their way in, confusing the database and making it difficult and sometimes impossible to play back these files. I tried clearing app data for the Gallery and rescanning, even moving files to new folders, but it would only fix it temporarily and eventually these would come back. My gallery would show I had 1200 pictures when I had at most 350, and my music library would also show five copies of the same song, only one of which would actually play. I thought maybe these were ghosts of deleted files, but could never be sure. I used an alternate gallery app, QuickPic, and it worked normally without the blanks.
The hotspot feature had issues as well. It would pass the traffic for the connected devices, but after a while it would stop working for the apps on the phone itself, until I shut it off.
I'm not sure if it's a possible problem in my phone either, so I'm trying something different.
All information regarding this unofficial LOS build and all credit for this ROM go here.
Only thing I did was edit updater script to remove device verification, so you can install it through TWRP on Honor 10. Prior installation I was on unlocked bootloader with TWRP from my other thread here and rooted with Magisk, I wiped all caches, system and data. Installation went fine, in the end it shows one mounting bug but end up succesfull 1.0. Then wipe cache, install GZR zero gapps (just in case, you can try regular opengapps), reboot to system and very fast first boot (less than 1min) without bootloops. Rooting by flashing newestMagisk ZIP without any issues. Install gapps right after installing ROM, if you install it after booting already you will need to wipe because otherwise gapps will show you app stopped responding error.
I made this small modification for myself, so don't expect any support/response from me, DON'T FORGET TWRP backup prior flashing and restore it in case of trouble.
Calls, Wifi, camera and basics work, fingerprint works as home and back button, not sure about recent apps, anyway I use Edge gestures with all functions on right edge.
bugs:
- These LOS ports have no support for notch so it's completely ignored and icons might be cropped behind notch (disable unnecessary trhough Status bar, personally I disabled network (Mobile data) indicators to save space),
- status bar is slightly smaller than notch which is sticking out a bit, use Notch remover with 63% setting to completely hide it, not possible to make status bar thicker without recompiling stuff, lazy to play with that, maybe xposed or DPI change will help if someone is too bothered
- because of rounded corners top left and top right corner of icons/time are slightly cropped
- minimum brightness it's quite high, can't find way to really lower it
Click to expand...
Click to collapse
DOWNLOAD
20180925 (uploaded 20181003) - seem no issues, no changelog
https://mega.nz/#!XZtRmI5Y!ewcPwL6eebnrzAGs55OJAnJN7FSsnB3pxEE_ZrMuFw0
Recommended camera it's Magisk module "Honor V10 Stock Camera" from David Sn & flex1911, AI doesn't work, gallery thumbnail shortcut will pop-up error, but regular photos/videos from all cameras work fine plus portrait (bokeh) mode works fine on front camera (not rear)
Thank you, it works!
Worked for me too. Sooooo good to move off EMUI...
Will post issues if I find any.
Thanks Peter!
How to go back to emui after I flash this??
Flash original eRecovery and download and install stock rom in eRecovery.
Odesláno z mého COL-L29 pomocí Tapatalk
srharshajava said:
How to go back to emui after I flash this??
Click to expand...
Click to collapse
do TWRP backup prior flashing and just restore TWRP backup, honestly if you need to ask this better don't flash anything
after using it for many days as daily I would just add one more "bug" - minimum brightness it's quite high
PeterMarkoff said:
after using it for many days as daily I would just add one more "bug" - minimum brightness it's quite high
Click to expand...
Click to collapse
Is the performance good ?
And battery ?
can't judge performance, not playing games, but battery on Wi-Fi only i had just record like day before yesterday 9 hours SoT
del
Hey guys,
and especially thanks again to Peter – so great you're testing all this stuff for us!
Now I'm having another question that I'm still not sure about:
Could I flash these ROMs onto the COL-AL10 (6gb RAM China version) without making another change to the files you've uploaded?
I mean they have the same SoC but doesn't the ROM affect e.g. the use of the RAM as well? And does it matter wether it's "China-branded"?
vollkornbaguette said:
Hey guys,
and especially thanks again to Peter – so great you're testing all this stuff for us!
Now I'm having another question that I'm still not sure about:
Could I flash these ROMs onto the COL-AL10 (6gb RAM China version) without making another change to the files you've uploaded?
I mean they have the same SoC but doesn't the ROM affect e.g. the use of the RAM as well? And does it matter wether it's "China-branded"?
Click to expand...
Click to collapse
it should not affect RAM, not sure if it will work on Chinese version, the easiest way it's to try
PeterMarkoff said:
today June 13th I dirty flashed modified Charlotte (P20 Pro) build (link in OP in top) over Berkeley (Honor V10) build without any issues, I just had to reinstall Huawei camera and disable always on ambient display and that's it, next builds I will use Charlotte since it is sharing at least same resoluton display with notch, although even on charlotte build it's notch sticking out a bit from status bar
Click to expand...
Click to collapse
Great work Peter. I'm thinking of flashing this as EMUIs ram management needs improvement. The only things worrying me is audio through headphone jack and whether it's daily driver ready. I know it's a rom and there is bugs but in your experience would you say it's good enough to use as a daily driver at the moment?
i am using it as daily driver, jack works fine, no hiss, just listening Sicario The beast to test it since actually didn't have time to listen anything on phone in long time
for me works pretty much everything, rarely i see pop up about some app stopped but you just relaunch it, other than that everything else it's cosmetic things regarding status bar/notch
it seem Huawei stock port is unable to save portrait mode photos for unknown reason, they are shown in viewfinder correctly, they even seem to be saved according gallery thumbnail, but they are nowhere to seen, regular photos and videos from all cameras work fine
PeterMarkoff said:
i am using it as daily driver, jack works fine, no hiss, just listening Sicario The beast to test it since actually didn't have time to listen anything on phone in long time
for me works pretty much everything, rarely i see pop up about some app stopped but you just relaunch it, other than that everything else it's cosmetic things regarding status bar/notch
it seem Huawei stock port is unable to save portrait mode photos for unknown reason, they are shown in viewfinder correctly, they even seem to be saved according gallery thumbnail, but they are nowhere to seen, regular photos and videos from all cameras work fine
Click to expand...
Click to collapse
Thanks. I'm convinced.
Also dirty flashed the Charlotte ROM.
No need to change the build.prop file, no issues so far.
Notch handling is better
New build for Charlotte is up. I edited the flashing script from OP and it works and flashed successfully. For some reason security patch is still on May 2018 but all seems to be working well. As far as I know, the new build improves the fingerprint scanner and auto brightness.
Edit: Did find one common bug - audio through headphone jack not working because the P20 and P20 Pro don't have a headphone jack.
@PeterMarkoff This will be a nice rom for our Honor 10. AOSP Oreo. https://forum.xda-developers.com/honor-view-10/development/rom-aosp-oreo-view-10-t3803803
Should be the same type of flash script mod by changing it to "Kirin970"
awells845 said:
New build for Charlotte is up. I edited the flashing script from OP and it works and flashed successfully. For some reason security patch is still on May 2018 but all seems to be working well. As far as I know, the new build improves the fingerprint scanner and auto brightness.
Edit: Did find one common bug - audio through headphone jack not working because the P20 and P20 Pro don't have a headphone jack.
Click to expand...
Click to collapse
jack works fine for me
PeterMarkoff said:
jack works fine for me
Click to expand...
Click to collapse
How? P20 Pro (Charlotte) only supports USB audio playback as it doesn't have a headphone jack so it wouldn't be possible to use headphone jack audio unless there's a way of editing the build prop to support it on other devices.