Database Users

Using ErwinP's CM-9 ROM, its fast with some issues

Hello all,
Today i installed the CM-9 ROM by ErwinP on my 1 year old Wildfire.
Its good with some issues:
1. Camera doesn't work.
2. gallery has a bug. The albums were visible when we tap and hold on the screen and drag to left or right. when we lift the finger the screen goes blank.
3. menu loading is slow every time.
4. screen lock is present but you have to select slide in the lock screen settings.
For any further issues, i'll update here, as I am new to this forum.
Some facts:
The ROM after install takes 151.8 MB of internal memory.
I have custom MTD partition of 160MB and 15MB cache. I'm getting 290 of internal memory but the system initially is taking 40 MB(I don't know why.)
So, usable is 250MB internal memory.

rajumack07 said:
Hello all,
Today i installed the CM-9 ROM by ErwinP on my 1 year old Wildfire.
Its good with some issues:
1. Camera doesn't work.
2. gallery has a bug. The albums were visible when we tap and hold on the screen and drag to left or right. when we lift the finger the screen goes blank.
3. menu loading is slow every time.
4. screen lock is present but you have to select slide in the lock screen settings.
For any further issues, i'll update here, as I am new to this forum.
Some facts:
The ROM after install takes 151.8 MB of internal memory.
I have custom MTD partition of 160MB and 15MB cache. I'm getting 290 of internal memory but the system initially is taking 40 MB(I don't know why.)
So, usable is 250MB internal memory.
Click to expand...
Click to collapse
first two issues you pointed are already given issues. read op to check common issues present as well as replacement app particularly for gallery and some other stuff.
other than that i think i dont have any issues like the other things you mentioned.
try 210/25 custom mtd partitions...it worked for me

@pauch_19: thanks for the information. I will look into alternatives to the bugs. Also you can try my custom MTD settings if you want more internal memory. Can you help me in getting the Market app to work(or any alternative app).

rajumack07 said:
@pauch_19: thanks for the information. I will look into alternatives to the bugs. Also you can try my custom MTD settings if you want more internal memory. Can you help me in getting the Market app to work(or any alternative app).
Click to expand...
Click to collapse
What's your problem with the market?
Sent from my Wildfire using xda premium

I installed the market v3.4.4 backed up previously. When I open it, it shutdowns automatically. kindly, guide me.

rajumack07 said:
I installed the market v3.4.4 backed up previously. When I open it, it shutdowns automatically. kindly, guide me.
Click to expand...
Click to collapse
Did you flash Google apps first? Or just install 3.4.4 apk?
You need to flash gapps I think, don't bother with 3.4.4 you should get an auto update to the new play one eventually.
Sent from my Wildfire using xda premium

Scratch0805 said:
Did you flash Google apps first? Or just install 3.4.4 apk?
You need to flash gapps I think, don't bother with 3.4.4 you should get an auto update to the new play one eventually.
Sent from my Wildfire using xda premium
Click to expand...
Click to collapse
Yeah, you'll need the entire gapps since the market also relies on some extra stuff.
(I had the same problem when I just installed the market .apk on my Elf.)
Sent from my Ainol Novo7 Elf using xda premium

that's probably the reason why you have more space on your internal memory because you forgot to flash gapps. incase you havent, flash gapps as what scratch and nejc suggested.. its also posted in op. its the latest gapps, about 52 mb in size so you will have to set your mtd partitions to default which is 250. im using the modified version which is just about 19 mb.
goodluck!

First of all thanks to all(Scratch0805,pauch_19 and nejc121) for your support in providing the information.
After getting the solution suggested by "Scratch0805". I again installed the ROM and along with the gapps at the same time. This time, I have taken the partition as 200 and 20. And after the boot, in terminal i found that system is using 186.4 MB. Still 13.6MB left.
Note: i installed the gapps with the size 51.88MB unmodified zip.
Now, everything works as it should have with camera as the exception.
One thing I want to know, what should be the CPU settings to follow for more than a day of battery life. Previously, i was using ON-DEMAND with 264-672MHz
and getting less than 22hrs of backup in CM7.

rajumack07 said:
First of all thanks to all(Scratch0805,pauch_19 and nejc121) for your support in providing the information.
After getting the solution suggested by "Scratch0805". I again installed the ROM and along with the gapps at the same time. This time, I have taken the partition as 200 and 20. And after the boot, in terminal i found that system is using 186.4 MB. Still 13.6MB left.
Note: i installed the gapps with the size 51.88MB unmodified zip.
Now, everything works as it should have with camera as the exception.
One thing I want to know, what should be the CPU settings to follow for more than a day of battery life. Previously, i was using ON-DEMAND with 264-672MHz
and getting less than 22hrs of backup in CM7.
Click to expand...
Click to collapse
mine is 352/729 smartassv2. on minimal - regular use, mine last a day and a half..i really think it depends on phone usage.

@pauch_19 : So, it means you are not using any apps to control the cpu settings.
I also used the smartassv2 governor and i found that backup decreases as it was in on-demand.
But, the smoothness in using gets better in smartassv2. So, can you tell me which governor will be better in terms of battery life and speed or any post where its mentioned.

atm i dont have too many apps which is also i think one reason why my phone is alot smoother, responsive and gives me a very decent battery life. In performance - processor, my cpu frequency minimum is 352 and 729 max. i used this values even when i was on cm7 nightlies coz its much stable..havent tried it at 768 though cpu governor is smartass v2.

rajumack07 said:
@pauch_19 : So, it means you are not using any apps to control the cpu settings.
I also used the smartassv2 governor and i found that backup decreases as it was in on-demand.
But, the smoothness in using gets better in smartassv2. So, can you tell me which governor will be better in terms of battery life and speed or any post where its mentioned.
Click to expand...
Click to collapse
I'm using the miui rom which is basically a modified version of cm9, I use setcpu just to set an underclock profile for when the screen goes off. My settings are on demand176/576 and powersave 176/352 as I've noticed that unless i'm straining the cpu by playing angry birds or watching a video with on demand my cpu tends to stay low doing normal things like making a phone call or checking xda but with smartassv2 it seems to jump high even when it doesn't really need to.
Sent from my Wildfire using xda premium

@pauch_19 : As for your settings goes, it good for performance. And you are also getting good life out of it. Nice to know that. I also read a post earlier where members are saying CM7 is better than SplashMOD. If its true, kindly tell me If you know which CM7 nightlies version do i use and how to remove the apps(I once used CM7 # 256,I didn't like the camera UI but it was smooth though) I then, switched to SplashMOD 1.6.
@Scratch0805 : I like the CPU settings you were using. I will definitely try those when I'll install the SPlashMOD v2.0 downloaded yesterday. But, I haven't tried on 176 because i thought then I'll get delay in getting calls and also lag in the background process. If these are not the issues you are getting, then I will must use these, and I can say that I will get at least 35+hrs of backup. And how MIUI is as compared to CM9?
thanks again for the responses I'm getting.

Somewhere in themes and apps section is a thread for miui camera, its a flashable zip which will give you a much nicer camera ui than the cm7 one.
Miui is beautiful as a standalone Rom but gets even better if your prepared to put some effort in, it has the same bugs as cm9, but spend a few hours setting up workarounds and it runs like a dream, I only have 2 problems now 1 is the camera (nevermind tho, I have a digital cam anyway) 2 is if you like theming your phone miui is awesome for it, the only problem is it was designed for hdpi and gingerbread so all the top themes need modding to fit ldpi and ics.
Sent from my Wildfire using xda premium

@Scratch0805 : I don't have any knowledge of modding. But I will definitely try MIUI ROM and can you tell me which CM7 version you are using, just asking if I may try that one anytime soon along with the miui camera.

rajumack07 said:
@pauch_19 : As for your settings goes, it good for performance. And you are also getting good life out of it. Nice to know that. I also read a post earlier where members are saying CM7 is better than SplashMOD. If its true, kindly tell me If you know which CM7 nightlies version do i use and how to remove the apps(I once used CM7 # 256,I didn't like the camera UI but it was smooth though) I then, switched to SplashMOD 1.6.
@Scratch0805 : I like the CPU settings you were using. I will definitely try those when I'll install the SPlashMOD v2.0 downloaded yesterday. But, I haven't tried on 176 because i thought then I'll get delay in getting calls and also lag in the background process. If these are not the issues you are getting, then I will must use these, and I can say that I will get at least 35+hrs of backup. And how MIUI is as compared to CM9?
thanks again for the responses I'm getting.
Click to expand...
Click to collapse
Personally I haven't tried Splashmod so I really couldnt say CM7 is better. I only tried CM7 and Im really impressed at how Cyanogen turned it into a very nice and fast rom. Before trying erwin's CM9 I was on nightly 256 build 14 and everything is working well.

I will try that one also with the miui camera Scratch0805 suggested. If all goes well, at the end of the day I'll be using CM7.

The camera should be fine on any rom I think, splashmod is basically either cm7 or oxygen (can't remember which one its based on atm as the "dev" changes his mind more often than I change my wallpaper ) with some apps removed or substituted for another. Underneath though it will always be cm7 or oxygen.
I'm on miui v4 atm and loving it but I'd recommend till you get into the swing either cm7 nightly 256 or keep an eye on the cm7 thread and look for the unofficial builds which have been built by erwinp and cobje, they may have a few bugs though I doubt anything serious otherwise they wouldn't release it + we are still clinging on to some fairly talented people that will most likely suss out the bugs and let everyone know how to fix them in the thread.
Sent from my Wildfire using xda premium

Well CM9 is really great, i love it, but sometimes my phone randomly reboot. Especially when i start phone.apk. Anybody with the same problem? I'm running on 352-710 MHz.
Also my GPS doesn't work.

F2FS bringing my N6 back to life

Hey everybody, here to try and convince anybody who hasn't to try switching to F2FS to improve your N6 experience. I'd been running darkrom for the past 8 months or so on ext4, and performance wise the phone worked but that was about it. The interface was jaggy and closing/opening apps and getting to the camera was consistently slow which is what I've experienced on most roms I've tried over the past few years. A couple days ago I decided to start from scratch and switch the file system over to f2fs. The process is relatively simple, grab a f2fs enabled TWRP version, clear all data on your phone (backup to a computer or something first if you have stuff you want to keep), use recovery to convert data and cache to f2fs, adb over your new f2fs compatible rom (darkrom/lineage are) and gapps and start it up.
After switching over I'm loving the N6 all over again. Opening and closing apps is consistently quick. No jank in the launcher or accessing the notification bar, no delays when hitting the power button to bring the screen back on. While the phone was doing initial installs of all my apps it was actually usable, previously on ext4 while apps installed it was almost impossible to use the phone it got so slow. On the latest darkrom the phone runs cool and battery life seems to be great at the moment.
Anyway, hope that helps some of you out! If you haven't tried the f2fs switch I would highly recommend it. I had done this in the past on my OG Nexus 7 which made it usable and is why I thought to try it again on my N6, glad I did!

I ran PureNexus for a while with no encryption using EXT4, then switched to F2FS after hearing all the hype.
I'm in the opposite camp to you @gambit07, I think it's all hype. My phone performs no better or worse with the same apps & data with F2FS vs EXT4. The only reason I still keep it F2FS now is because I can't be bothered wiping again.
Are you sure you weren't running encrypted when you had all these slowness issues? I certainly saw a massive improvement going from encrypted to non-encrypted (EXT4 both times).
Everyone else: By all means give it a go, but it's just a slightly different filesystem, some of the magical qualities attributed to it aren't possible.

muppetmania said:
I ran PureNexus for a while with no encryption using EXT4, then switched to F2FS after hearing all the hype.
I'm in the opposite camp to you @gambit07, I think it's all hype. My phone performs no better or worse with the same apps & data with F2FS vs EXT4. The only reason I still keep it F2FS now is because I can't be bothered wiping again.
Are you sure you weren't running encrypted when you had all these slowness issues? I certainly saw a massive improvement going from encrypted to non-encrypted (EXT4 both times).
Everyone else: By all means give it a go, but it's just a slightly different filesystem, some of the magical qualities attributed to it aren't possible.
Click to expand...
Click to collapse
Huh, that's unfortunate. No I removed encryption when I first got my N6 and have never used it. I've been running my N6 on ext4 roms for the last 3 years and I've never noticed this much of a difference in smoothness of the OS. I actually didn't think much of it either which is why it took me so long to try it, but what pushed me was remembering how much better my nexus 7 performed after I switched a few years back. It went from literally not usable due to how slow it was, to usable. Anyway I would encourage others to give it a shot. The only other thing I could see being the reason for the increased performance is maybe the partitions getting formatted. I doubt that would make a difference but that's the only other variable that's changed

Well, I would think that a format will certainly help by itself, though a wipe should be just as good - but how often do we wipe internal storage?
Another thing to remember is that speed drops significantly if the partition is almost full - try always to keep at least 20% free.
I haven't tried f2fs on this phone, and haven't noticed a difference on other phones. From what I read, you should get a marginal improvement on typical use cases.
Also consider that f2fs has only recently stabilized. A plain 3.10 kernel may still have a few bugs left, so it's better if the dev has backported fixes from newer versions. People running f2fs on unpatched 3.0 or 3.4 kernels have seen occasional data corruptions.

After reading this thread I have searched F2FS on Nexus 6 and read some XDA and Reddit posts, seems like it doesn't make any performance difference, I'm on S.i.X v1.6 (Oreo), its working fine, if anyone using F2FS on Oreo ROM, please share you experience.

gambit07 said:
After switching over I'm loving the N6 all over again.
Click to expand...
Click to collapse
Would you mind sharing your ROM, Kernel and setup details

mnsiw said:
Would you mind sharing your ROM, Kernel and setup details
Click to expand...
Click to collapse
Sure! I'm on darkrom 7.1.2, the 9/24 nightly, link below. Gapps are included in his post and it's the stock kernel which is a modified lineageos kernel. Lineage supports f2fs out of the box. Steps were as follows.
https://forum.xda-developers.com/nexus-6/development/rom-dark-rom-t3580215
-Backup current data to external drive
-Fastboot flash f2fs enabled TWRP
-Wipe all partitions in TWRP
-Format Data and Cache partitions as f2fs in recovery
-ADB sideload Rom/Gapps/Magisk/Whatever
-Reboot
Hope that helps! Still working great on my side

runekock said:
Well, I would think that a format will certainly help by itself, though a wipe should be just as good - but how often do we wipe internal storage?
Another thing to remember is that speed drops significantly if the partition is almost full - try always to keep at least 20% free.
I haven't tried f2fs on this phone, and haven't noticed a difference on other phones. From what I read, you should get a marginal improvement on typical use cases.
Also consider that f2fs has only recently stabilized. A plain 3.10 kernel may still have a few bugs left, so it's better if the dev has backported fixes from newer versions. People running f2fs on unpatched 3.0 or 3.4 kernels have seen occasional data corruptions.
Click to expand...
Click to collapse
Yeah, and the cells on internal storage degrade over time as well, but I am never consuming over 80% regardless. I had wiped my data partition a couple times prior to this in the last few years, and have wiped system/cache countless times, so I don't think that accounts for the change in my experience. The only reason I posted is because this is now my second device (after my Nexus 7) where I've switched and seen a noticeable positive improvement. I know for me it's a real change as my Nexus 7 went from actually unusable to being relatively usable after the switch. I had tried countless roms and full wipes on that device with no difference in latency prior. The Nexus 6 isn't as big a change but I can definitely feel the difference

gambit07 said:
Sure! I'm on darkrom 7.1.2, the 9/24 nightly, link below. Gapps are included in his post and it's the stock kernel which is a modified lineageos kernel. Lineage supports f2fs out of the box.
Click to expand...
Click to collapse
Oh, thanks, actually I tried it with latest stock and ElementalX but failed, it stuck on boot animation.
I'm on S.i.X v1.8 (Oreo 8.0), don't feel any performance issue but love to experiment so going to try this F2FS thing

mnsiw said:
Oh, thanks, actually I tried it with latest stock and ElementalX but failed, it stuck on boot animation.
I'm on S.i.X v1.8 (Oreo 8.0), don't feel any performance issue but love to experiment so going to try this F2FS thing
Click to expand...
Click to collapse
Cool, let me know how it works! Curious to see if anybody else feels the difference or if it's just me

mnsiw said:
Oh, thanks, actually I tried it with latest stock and ElementalX but failed, it stuck on boot animation.
I'm on S.i.X v1.8 (Oreo 8.0), don't feel any performance issue but love to experiment so going to try this F2FS thing
Click to expand...
Click to collapse
ElementalX does not support F2FS.

gambit07 said:
Cool, let me know how it works! Curious to see if anybody else feels the difference or if it's just me
Click to expand...
Click to collapse
Downloading 20171010 build, not sure how to check if there is any performance boost, because its already working perfect on current ROM I have recently switched to APFS (High Sierra) on my MacBook from HFS+, there was not any visible performance difference but of course it is new and better file system
Edit: It feel more responsive now, thanks Gambit

mnsiw said:
Downloading 20171010 build, not sure how to check if there is any performance boost, because its already working perfect on current ROM I have recently switched to APFS (High Sierra) on my MacBook from HFS+, there was not any visible performance difference but of course it is new and better file system
Edit: It feel more responsive now, thanks Gambit
Click to expand...
Click to collapse
Awesome, glad to hear it! Yeah I just feel like performance is more consistent. Less hang ups, apps open at a consistent speed. It just feels more fluid

gambit07 said:
Awesome, glad to hear it! Yeah I just feel like performance is more consistent. Less hang ups, apps open at a consistent speed. It just feels more fluid
Click to expand...
Click to collapse
For me, best part about DarkROM is Google Assistant on any screen, even when screen is off. I miss Oreo settings and notification / quick tiles, everything else is great.

I've used F2FS on various devices and while it does provide slight benefits in benchmarks, there's no real world benefits IMO.

brando56894 said:
I've used F2FS on various devices and while it does provide slight benefits in benchmarks, there's no real world benefits IMO.
Click to expand...
Click to collapse
Yeah I don't use benchmarks at all. It's real world use where I notice a difference

I'm back on S.i.X Oreo, honestly feel no difference in performance or smoothness, even it's little better on battery

I'd suggest that you're experiencing the placebo effect, or at the very least, benefits of clear flash memory. I've always found that my phone is faster after I completely format all the memory.

I've been using F2FS for a few months now. It's not a placebo effect. The phone is more fluid, less freezes, and stable performance even after downloading and using a hand full of apps

I have been using F2FS with the latest DU ROM and Sigma Kernel, clean flashed but I don't see any difference at all. In fact I had a couple of freezes and a reboot as well which never happened to me before using this combination. But maybe this in not F2FS related at all.

Oreo 64 bits based roms lag

Hi, does anyone have the problem that when you're in a 64 bit ROM like Pixel Experience or Xperience and you have lag? Like when you activate night light without activating ? Any solution? Thanks
Sorry for bad English

If you're talking about lag in system, yes, lots of us are facing it. I think only 2gb models have this trouble.

The system is struggling because of the lack of RAM. 64bit requires at least 3-4GB of RAM to be decent. I run x64 on mine, and the only time I ever really see any issues is when its night time, almost like its a memory leak. I reboot, and its fine for another 24 hours before it becomes unusable. I am running Pixel Experience.

drsemaj87 said:
The system is struggling because of the lack of RAM. 64bit requires at least 3-4GB of RAM to be decent. I run x64 on mine, and the only time I ever really see any issues is when its night time, almost like its a memory leak. I reboot, and its fine for another 24 hours before it becomes unusable. I am running Pixel Experience.
Click to expand...
Click to collapse
The lag is NOT because of the lack of RAM, rather it's optimisation. The Nexus 5x run 64bit ROMS just fine. That phone came out in 2015 with 2GB of RAM and shipped with 64bit marshmallow and happily runs anything above that.

I have a XT1622, system was using 0,7~1,1GB of RAM so there was plenty of RAM to be used. There was approximately 400MB free all time. I don't think RAM is the problem. After some CPU testing at AICP I reduced the lag by changing the Governor to Performance, which uses A LOT of battery, but it didn't get rid of the lag just made it smoother.
Obs: The lag that I'm talking about is only System lag and it's weird because when the screen is locked and you pull the quick settings it's smooth but after you unlock the phone, you pull the quick settings and there's a crazy lag. It's like playing a game with 10FPS.

GCSortes said:
Obs: The lag that I'm talking about is only System lag and it's weird because when the screen is locked and you pull the quick settings it's smooth but after you unlock the phone, you pull the quick settings and there's a crazy lag. It's like playing a game with 10FPS.
Click to expand...
Click to collapse
This is why I think it's an optimisation problem rather than a hardware issue. Apps and games are smoother than nougat for me but the recents menu, notification area (When unlocked) and launcher lag like crazy and I have no idea why.

DECHTECH said:
This is why I think it's an optimisation problem rather than a hardware issue. Apps and games are smoother than nougat for me but the recents menu, notification area (When unlocked) and launcher lag like crazy and I have no idea why.
Click to expand...
Click to collapse
Hello again, since my last post I've been using Stock 7.0 + ElementalX Kernel + Magisk + Xposed + Gravity Box. Super smooth and shiet but I like theming and customising fonts, so yesterday I tested AICP 8.1 and I felt some improvements, the RAM usage was better (700MB System), the lag wasn't gone but it felt smoother. Now I'm on RR 7.1.2. I'm facing some random reboots but I'll try to grab some logs to dev. If I don't get rid of those reboots I'll jump to AICP and deal with the lag.

GCSortes said:
Hello again, since my last post I've been using Stock 7.0 + ElementalX Kernel + Magisk + Xposed + Gravity Box. Super smooth and shiet but I like theming and customising fonts, so yesterday I tested AICP 8.1 and I felt some improvements, the RAM usage was better (700MB System), the lag wasn't gone but it felt smoother. Now I'm on RR 7.1.2. I'm facing some random reboots but I'll try to grab some logs to dev. If I don't get rid of those reboots I'll jump to AICP and deal with the lag.
Click to expand...
Click to collapse
Just for information: don't post logs with the mods you mentioned here. Logs are only useful to troubleshoot if your rom is installed without any modifications.

GCSortes said:
Hello again, since my last post I've been using Stock 7.0 + ElementalX Kernel + Magisk + Xposed + Gravity Box. Super smooth and shiet but I like theming and customising fonts, so yesterday I tested AICP 8.1 and I felt some improvements, the RAM usage was better (700MB System), the lag wasn't gone but it felt smoother. Now I'm on RR 7.1.2. I'm facing some random reboots but I'll try to grab some logs to dev. If I don't get rid of those reboots I'll jump to AICP and deal with the lag.
Click to expand...
Click to collapse
Try AICP nougat if you want a smooth, stable experience.

Since there are no manufacturer drivers (blobs) for 64 bit, just ported form other devices, the x64 is a poor choice for this phone.

SoNic67 said:
Since there are no manufacturer drivers (blobs) for 64 bit, just ported form other devices, the x64 is a poor choice for this phone.
Click to expand...
Click to collapse
"Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should."

DECHTECH said:
Try AICP nougat if you want a smooth, stable experience.
Click to expand...
Click to collapse
:good:

I think that it's a optimisation problem, cuz I'm on aicp, is so smooth and battery life is so good.

lag

Anyone get lag on most custom roms over time that needs a restart to fix? I don't think it happens often and it doesn't look like clearing recents or anything will help. Is there another method people use to keep it always fast without needing to restart? I forgot if stock had that problem too. When it doesn't lag though, performance is nice and smooth like how it first was after a clean flash while not affecting the battery at all. Would be nice to know what causes it too

do you use the headphone jack? Could be caused by the memory leak on all B12 source based ROMs
Sent from my ZTE Axon 7 using XDA Labs

Infy_AsiX said:
do you use the headphone jack? Could be caused by the memory leak on all B12 source based ROMs
Click to expand...
Click to collapse
Yeah sometimes I think I noticed faster drain too that's been reported as an AEX sound bug before. I'm currently on the latest 7/11 non treble. I wonder if the newer treble builds don't have that problem I'll need to read into it more though it's sad to see the dev has left. Should it be fine if I don't use earphones for the whole day or if changed to a different rom? I think I will go back to using Bluetooth earphones if that fixes it too. I was using wired because I was lazy to connect Bluetooth and hoping it would save some battery. They sound slightly better too but looks like it did the opposite! Would be nice if rom could stay fast the whole time. Thanks for the reply

anon1135 said:
Yeah sometimes I think I noticed faster drain too that's been reported as an AEX sound bug before. I'm currently on the latest 7/11 non treble. I wonder if the newer treble builds don't have that problem I'll need to read into it more though it's sad to see the dev has left. Should it be fine if I don't use earphones for the whole day or if changed to a different rom? I think I will go back to using Bluetooth earphones if that fixes it too. I was using wired because I was lazy to connect Bluetooth and hoping it would save some battery. They sound slightly better too but looks like it did the opposite! Would be nice if rom could stay fast the whole time. Thanks for the reply
Click to expand...
Click to collapse
I didn't persist with B12 ROMs as I soon discovered the bug. I've heard it exists on Treble too. How the memory leaks occur no one has reported.
To check use terminal:
su
top -s 6
Under the USER column the two Audioserver processes can be found. Under their respective RES column is their RAM usage. It may just grow during usage. It may be possible to kill it to restart the memory leak but that won't help with it's large CPU% usage drain either.
Sent from my ZTE Axon 7 using XDA Labs

Infy_AsiX said:
I didn't persist with B12 ROMs as I soon discovered the bug. I've heard it exists on Treble too. How the memory leaks occur no one has reported.
To check use terminal:
su
top -s 6
Under the USER column the two Audioserver processes can be found. Under their respective RES column is their RAM usage. It may just grow during usage. It may be possible to kill it to restart the memory leak but that won't help with it's large CPU% usage drain either.
Click to expand...
Click to collapse
Just out of curiosity which rom are u on now or recommend? If it weren't for this bug the rom the rom would be perfect

anon1135 said:
Just out of curiosity which rom are u on now or recommend? If it weren't for this bug the rom the rom would be perfect
Click to expand...
Click to collapse
The latest available RR-O without the bug. Kranoner's 20180511, google his AFH for it. It also requires a APN fix

Infy_AsiX said:
The latest available RR-O without the bug. Kranoner's 20180511, google his AFH for it. It also requires a APN fix
Click to expand...
Click to collapse
Ty I will try

[ MOD PLEASE DELETE THIS THREAD ]

Deleted

ROM Screenshots
Can be found on my telegram support group

Reserved

Starlight5234 said:
- GPS, Bluetooth & WFD might not work
Click to expand...
Click to collapse
Bluetooth works. GPS doesn't work. WFD - i don't have anything to test.
---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ----------
Is battery life good? I don't play games, mainly use my Vince for youtube and audio recording.
Will we get any updates? I saw post on telegram about dead server.

danko13 said:
Bluetooth works. GPS doesn't work. WFD - i don't have anything to test.
---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ----------
Is battery life good? I don't play games, mainly use my Vince for youtube and audio recording.
Will we get any updates? I saw post on telegram about dead server.
Click to expand...
Click to collapse
Thanks for confirming all these.

Starlight5234 said:
Thanks for confirming all these.
Click to expand...
Click to collapse
GPS might work after all

danko13 said:
GPS might work after all
Click to expand...
Click to collapse
I heard someone say it crashes on choosing travel location

Starlight5234 said:
I heard someone say it crashes on choosing travel location
Click to expand...
Click to collapse
I checked with google maps. Everything works there.

Quick Update Bluetooth and GPS fully working now. Thanks to all guys who reported to me

how good is this rom? screenshots plz..

Worst android 11 rom I have ever tried, enormous battery consumption, I doubt it has less customizations than stock android r
Also, thread says that ROM is performance optimised, I tried running antutu benchmark, the score was lower by 6K compared to MSM Xtended XR
Almost forgot, after installing ROM, it booted automatically and replaced my orangefox with default android recovery.
Definitely worst rom

nevermind23 said:
Worst android 11 rom I have ever tried, enormous battery consumption, I doubt it has less customizations than stock android r
Also, thread says that ROM is performance optimised, I tried running antutu benchmark, the score was lower by 6K compared to MSM Xtended XR
Almost forgot, after installing ROM, it booted automatically and replaced my orangefox with default android recovery.
Definitely worst rom
Click to expand...
Click to collapse
OOPS

nevermind23 said:
Worst android 11 rom I have ever tried, enormous battery consumption, I doubt it has less customizations than stock android r
Also, thread says that ROM is performance optimised, I tried running antutu benchmark, the score was lower by 6K compared to MSM Xtended XR
Almost forgot, after installing ROM, it booted automatically and replaced my orangefox with default android recovery.
Definitely worst rom
Click to expand...
Click to collapse
Bull****. I installed this ROM few times and every one of them my orangefox recovery remained intact.
Yes. It has zero customization. Almost pure AOSP.
"Enormous battery consumption" - bull****. Almost zero discharge in sleep. And same, even better battery life in work.

danko13 said:
Bull****. I installed this ROM few times and every one of them my orangefox recovery remained intact.
Yes. It has zero customization. Almost pure AOSP.
"Enormous battery consumption" - bull****. Almost zero discharge in sleep. And same, even better battery life in work.
Click to expand...
Click to collapse
His comment is mostly bull**** but that recovery issue is there. It happened to me too. After flashing rom phone restarted itself, I didn't even had a chance to flash gapps. After that Orangefox was gone. It doesn't happen every time but it is there. (1 of 3 flashes in my case)
ROM is very nice, fast and responsive. Battery life is pretty good, drain is relatively small. There are a few bugs but it is a BETA so it is fine. Not much customization is not really an issue with the rom, some people prefer stock experience.

nevermind23 said:
Worst android 11 rom I have ever tried, enormous battery consumption, I doubt it has less customizations than stock android r
Also, thread says that ROM is performance optimised, I tried running antutu benchmark, the score was lower by 6K compared to MSM Xtended XR
Almost forgot, after installing ROM, it booted automatically and replaced my orangefox with default android recovery.
Definitely worst rom
Click to expand...
Click to collapse
Always use latest recovery, not a single time did my recovery get wiped. Heard that it was the recovery itself not my rum so.. and about battery consumption is same as MSM-Xtended R cuz the trees and kernel source code used was same. I've been working on kernel source code for a while now and many of my testers have definitely better battery on it just wait for December Security patch than complain without proper logs and stats. Also benchmarks are not what define performance just fyi. And if you still wanna benchmark it then use some good benchmark kits than Antutu for e.g Benchkit module for Magisk . And the ROM is meant to be plain AOSP I've only picked "useful" "user interactive" customisations that are really necessary

Assassins23 said:
how good is this rom? screenshots plz..
Click to expand...
Click to collapse
A serious recommendation is do not ask how a ROM is because it has haters everywhere not talking about my ROM, all. And people who are not as expert at following instruction then end up in misery blaming the dev for his work. Though the ROM is pretty good I'd say wait for December Security Patch update release cause I'm working on stabilizing it completely and I'd say it's 60% there

Great job @Starlight5234 (bruh change your username)! Peeps, this isn't like other generic ROMs, Star knows what he's doing and the ROM source code itself is optimized for Vince, not just the device tree and kernel. Do give this a try y'all. All hail Star the Pro God

kermittos said:
His comment is mostly bull**** but that recovery issue is there. It happened to me too. After flashing rom phone restarted itself, I didn't even had a chance to flash gapps. After that Orangefox was gone. It doesn't happen every time but it is there. (1 of 3 flashes in my case)
ROM is very nice, fast and responsive. Battery life is pretty good, drain is relatively small. There are a few bugs but it is a BETA so it is fine. Not much customization is not really an issue with the rom, some people prefer stock experience.
Click to expand...
Click to collapse
I checked almost every Q and R roms i could find in last couple of weeks. My orangefox recovery still intact. Only one rom ASKED me to update recovery. Can't remember which it was.
I also tested with antutu. This rom gave me 96712, ProjectStreak - 100180. 3468 difference. No big deal, i don't play games on smartphone.

nevermind23 said:
Worst android 11 rom I have ever tried, enormous battery consumption, I doubt it has less customizations than stock android r
Also, thread says that ROM is performance optimised, I tried running antutu benchmark, the score was lower by 6K compared to MSM Xtended XR
Almost forgot, after installing ROM, it booted automatically and replaced my orangefox with default android recovery.
Definitely worst rom
Click to expand...
Click to collapse
1. Everyone in our internal test group reported either the same or better battery life, as the entire ROM is made specially for Vince and not just the device tree and kernel tree. Give the ROM a few cycles.
2. Have you tried pure AOSP R? Literally all custom ROMs have at least one more feature than pure AOSP, that's the whole point of custom ROMs. And Star's ROM has more than a few customisations.
3. AnTuTu is one of the worst benchmarks you can run on smartphones. Most, if not all, benchmarks in Play Store measure thoroughput, not latency. Latency corresponds to UX, not throughput. Bigger numbers aren't always better. Shocking, I know.
4. msm8953 is old, very old. Try MIUI with it's sluggish r*rted code. Any performance improvement (there is quite a difference) you get beyond stock is because of the hard work of developers who get nothing in return. Don't expect smoothness everywhere on a device with a 4 year old budget chipset.
5. Sounds like your recovery is faulty as well.

KenHV said:
Great job @Starlight5234 (bruh change your username)! Peeps, this isn't like other generic ROMs, Star knows what he's doing and the ROM source code itself is optimized for Vince, not just the device tree and kernel. Do give this a try y'all. All hail Star the Pro God
Click to expand...
Click to collapse
Feels good to have a ultra pro max god back me up for my work :highfive: