Related
Ok, I must say that I have not had any reason to complain regarding the ROM's that I'm using, I will make this thread a bash of them either, but Ineed to understand a few things....
Ok so I have been running CM6.1.0 stable for a few weeks (since it was made available) and really have not had many issues. As a matter of fact it runs very smooth. I have since installed Pershoot's kernel and it much improved my battery....and here lies the issue I have tried to run many scenarios to improve my battery duration (about 8 hrs on ChiChis 1800 mAh).
So I have installed the following apps:
- Advanced task Killer - set on agressive
- Juice Defender - set to turn off all connections while screen is off
- Juice Tracker - Plots battery consumption (very nice!!!)
And while my battery performance has increased greatly...I'm getting anywhere between 13 to 17 hrs depending on use and gaming.
The other thing that I found rather odd was the fact that I no longer have the 5 different options on SetCPU. I am limited to:
- Performance
- On Demand
- User space (recommended not to be used by dev).
I am missing:
- Conservative
- ???? I forgot what what the other level
Nayone having or had anything like this?
As I'm typing this I'm downloading the Pershoot Kernel, but I am still hesitant about the CM 6.1.1.
Thanks!!!
Hi there, well im just asking for help. My device 800i is lagging as hell and i just dont know why. since 2 days now, i tried everything offered here and its just getting worse. My two setups i tried are :
Basic : 800i, 16gb Sandisk cls4
A: Stock Rom .62
Kernel Doom v11 , bfq and SmartAss V2 ->1107 mhz
Supercharger v6 U9Rc7 with Option 7 and 20
Link2SD, 2nd Partition ext3
=> Micro Stuttering and furthermore, all games pauses itselfs like it needs to reload or something. YES, I mean Pauses, the pause-screen do appear in every game, in short periods
I switched to Doom v10 cause i thought microstuttering came from the gpu-oc. yupp it got fixed, but still get those "Force-Pause"-Screen
B: JokaWild Rom V2.5
Kernel Doom v10 , sio and SmartAss V2 ->1107 mhz
Supercharger v6 U9Rc7 with Option 7 and 20
Link2SD, 2nd Partition fat32
=> Oh my...this is even worse. instead of microstuttering or pause-screens (which seems to be gone here) its like periodically lagging as hell.I cant really describe, its just so heavy lagging. In between though, it runs super fast (until it gets its mega lag-cycle.
now, i dont know what to do..im getting like crazy cause everything just runs ****ty....i dont even want to start with a gameloft game, cause they are already "special"....this + my lagging would turn out to a flying xperia ...if ya know what i mean
please help me, thx in advance
i do however prefer stock, cause it runs "fluentlier"...just this pause-screen-reloading-crab annoys me haaaaardd
Im having the same problem bro, any help would be great
Sent from my R800i using XDA
okay first i thnk i will revert back to supercharger v6 u8
boxkillor said:
Hi there, well im just asking for help. My device 800i is lagging as hell and i just dont know why. since 2 days now, i tried everything offered here and its just getting worse. My two setups i tried are :
Basic : 800i, 16gb Sandisk cls4
A: Stock Rom .62
Kernel Doom v11 , bfq and SmartAss V2 ->1107 mhz
Supercharger v6 U9Rc7 with Option 7 and 20
Link2SD, 2nd Partition ext3
=> Micro Stuttering and furthermore, all games pauses itselfs like it needs to reload or something. YES, I mean Pauses, the pause-screen do appear in every game, in short periods
I switched to Doom v10 cause i thought microstuttering came from the gpu-oc. yupp it got fixed, but still get those "Force-Pause"-Screen
B: JokaWild Rom V2.5
Kernel Doom v10 , sio and SmartAss V2 ->1107 mhz
Supercharger v6 U9Rc7 with Option 7 and 20
Link2SD, 2nd Partition fat32
=> Oh my...this is even worse. instead of microstuttering or pause-screens (which seems to be gone here) its like periodically lagging as hell.I cant really describe, its just so heavy lagging. In between though, it runs super fast (until it gets its mega lag-cycle.
now, i dont know what to do..im getting like crazy cause everything just runs ****ty....i dont even want to start with a gameloft game, cause they are already "special"....this + my lagging would turn out to a flying xperia ...if ya know what i mean
please help me, thx in advance
i do however prefer stock, cause it runs "fluentlier"...just this pause-screen-reloading-crab annoys me haaaaardd
Click to expand...
Click to collapse
have you tried moving your apps to your sd card? how much internal memory do you have? have you tried other troubleshooting tips posted here in the forums?
I am using JokaWild v2.5 (see my signature for more details) and my Xplay is extremely stable and fast and no battery drain issues or lags. Have you tried factory reset in settings menu? any task killers installed? clear cache and memory? maybe you have corrupted backup and no antivirus at all?
debloat the rom? found my phone significantly sped up after deleted all the unneeded stock apps and timescape stuff.
thx bro´s and a special "salamat" to my fellow-countryman
i actually tried both of your advices too. (Besides the 400+mb trick) just no luck :/
my actual plan is to : (this is kind of a guide i guess ^^)
* Format my sdcard (16gb) to 14,3gb Fat32 - Rest ext4
* Revert to Stock 62
* Doing a Factory Reset
* Flashing Doom v10 (without baseband .36)
* After a Restart, Flashing the needed zips (like wifi-modules, bravia etc)
* Setting bfq and smartass v2
* installing the "tweak.apk" for touchscreen-tweak and gpu-home-rendering
* (Optional) the 400mb+ internal memory thing
* getting link2sd for auto-moving to 2nd partition
* reinstalling my apps
* debloating my Fw
what do u think? any tips? thx in advance
I had lag this week, R800i .42 firmware, micro-stutter, and forced pause mode on at least one game. That was Gangstar Rio, which is a very buggy game anyway, but also just web browsing caused a lot of annoying stutter. I don't use task killers, and have always had frozen bloatware since rooting. But it's working well again now after restoring a lot of stock settings:
- Downgraded Doomkernel from v11 to v10. I don't think my GPU likes being overclocked either. My 3D benchmark in Antutu was consistently a bit lower. But now it seems I can now O/C to 1.4GHz on Doomkernel v10, at the 1GHz stock voltage if I want to, I'm just not sure how comfortable I am with O/C-ing habitually.
- Un-supercharged v6 U9Rc7.
- Restored my original backup of build.prop. Something in it caused my CPU to top out at 921MHz on boot, but restoring the build.prop also seemed to make that and a lot of lag go away. I have no idea what I did to it
- Went through the options in PowerAmp and ensured anything pertaining to an auto-scan of library was switched off.
- Went back to normal CPU settings of 1017/249 ondemand. Trying the lowest clock for the min speed and SmartAssV2 gave me my one and only bootloop (may have been a coincidence).
- Uninstalled some unused games from internal memory - can retreive them from the Market or from TB if I need them. This probably made no real difference as I only gained about 5MB or so.
After a day or so, my phone runs fine now.
I am an Android newbie though, so while that worked for me, I'm not confident about my own "advice" for other people...
yeah i got this 921mhz thing on boot too, but it is fixáble by setting it to 1017 in voltage control as an init.script.
----
i somehow have the feeling the lag heavily depends on the sd card. it is a sandisk cls4 which is good according to a thread here in forums but i think that there must be something wrong with it...hell i dont even know if i already exceeded the lifespan lol ^^
^ Yes I found that worked, but I didn't want to have to rely on boot scripts to fix something that wasn't broken when I was fully stock
I have a Sandisk Class 4 as well... 32GB not 16GB, but I think they're pretty tried and trusted. I read the forums heavily before buying the card as well. I've never really had lag before this week (other than when I'd just closed a heavy game like GTA, and the launcher needed to redraw etc)
exactly what i did too. i came to the idea that my sd may broke because everything feels like it needs to reload. i think sluggish is the right word to describe it.
are u using supercharger?
^ I don't have supercharger installed now, but that's mainly because my logic was to put everything back to how it was. I wasn't sure what effect it had on performance other than to keep the launcher in memory.
i can confirm that laggyness will decrease with it. but tbh in the latest rc... i think its too agressive for my device which leads me to use the old v6 u8
boxkillor said:
yeah i got this 921mhz thing on boot too, but it is fixáble by setting it to 1017 in voltage control as an init.script.
----
i somehow have the feeling the lag heavily depends on the sd card. it is a sandisk cls4 which is good according to a thread here in forums but i think that there must be something wrong with it...hell i dont even know if i already exceeded the lifespan lol ^^
Click to expand...
Click to collapse
have you tried setting your read/write cache to higher than 2048? do not use voltage control or antutu I've tried those before and they only drain your battery use sytem tuner as it has everything you need. I set my read/write to 6041 and it speeds up apps loading time. I use transcend for my 16gb sd card and only costs 1.5k+ pesos. I do not use link2sd as zdbox has built in feature to move apps to sd card like app2sd. You can also try moving apps through Titanium backup. Try tweaking your startup apps as well (use system tuner). "Sakin ka maniwala kababayan"
Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
herqulees said:
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
AndyYan said:
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
I've already deleted every system app I'm comfortable removing using Root Uninstaller. After having everything I have to have installed on the phone, with as many apps set to not run in the background that I can and Greenify helping too, I tend to have 10-70MB of RAM free, it tends to be 15-35MB free though. I don't use task killers since all they do is play cat and mouse and waste battery, and tried a few auto start managers but can't really get into using it with how complicated they are. Right now the main thing I want to figure out is getting a swap partition up and running since that sounds the most promising with how little RAM this phone has.
Did a backup and switched to the nitest-0721 kernel and so far it's doing good. Disappointed the OC only goes up to 1.2GHz but it's better than nothing (don't understand kernels that limit how much you can OC when it's up to you to find how much your phone can OC), hopefully I can find a way to get it to go higher, and the "voodoo color" is weird but I can install a different version of the kernel to remove that if my eyes don't adjust first. Anyways... my free RAM now stays between 100-200MB, usually about 160MB, with 18% zRAM, purging of assets, and samepage merging enabled which is amazing. Apps are opening faster and don't stutter anywhere near as much as before, so I'm happy but will see how things go tonight when I go to work and am playing with it on and off, along with need to find a way to really overclock it.
herqulees said:
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
Try going with one of didhiy's nitest kernels and maybe a different AOSP ROM, like AOKP, PAC, etc. Or try out SuperNexus even. That's an extremely lightweight ROM with no customization options (Its straight up stock Android, just like a brand new Nexus phone), but its fast and quite stable from what I remember.
Sent from my LG-LS970 using xda app-developers app
Or find one of didhiy's nutest kernels, those have live oc, more free ram, and i believe it goes to 1.4 GHz. I'm not sure though. But it is less stable than nitest
Sent from my SPH-D700 using Tapatalk 2
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
herqulees said:
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
Click to expand...
Click to collapse
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
AndyYan said:
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Click to expand...
Click to collapse
I just seriously hate kernels that limit how high you can overclock instead of making OC options to unreachable levels letting you find your phones limits. People make kernels, roms, hacks, etc so we can get around limitations that the hardware vendors put up. So if we've managed to circumvent the manufacturers blocks why are the same people that got around them making their own blocks, they already put up silly warnings about anything you install/do could break your phone but if you're going to give that warning it needs to be true. Anyways ending my rant lol...
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
herqulees said:
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
Click to expand...
Click to collapse
Uh, AFAIK, isn't these frequency decided only when the kernel is COMPILED (from source code)? I don't exactly know...
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Hi all.
This thread is for random builds and development. There is no agenda other than to keep the Kindle Fire alive for the few of us that remain. This thread is not meant to support any specific ROM. I hope this is okay with the forum administrators.
With that said, please join in. We're all in this together.
Cm-12.1 2015-10-15
I made a public viewable folder on my Google Drive for Android stuff here https://drive.google.com/folderview?id=0B7BjC3Ky49TVcjdZQlpHYV9JWXc&usp=sharing
I uploaded a build of CM-12.1. The file name is weird so I will explain (in case you care):
cm-12.1-20151015-UNOFFICIAL-kad-rsm-O3-mo3-wifi-otterx.zip:
kad = kernel compiled with ArchiDroid toolchain
rsm = ROM compiled with SaberMod toolchain
O3 = almost all compiled with -O3
mo3 = more optimization, specifically as much of JustArchi's compiler flags as would work. The '3' is my third attempt to add more optimizations.
wifi = hack to make wifi work without doing a clean install, that is, there is a script, fix-mac.sh, which I think only gets run with a clean install. My hack was simply to copy the file that the wifi driver wants to the name that it wants. This should allow either dirty or clean flashing.
Suggestions:
* Change the animation duration levels in Developer Options to 0.3x or less.
* Use the Noop I/O scheduler for regular things like reading a book (that's why you bought a kindle, right) or browsing the web.
* Use the Deadline I/O scheduler for interactive things like playing a game.
* If you like Gapps, I suggest OpenGapps or TK Gapps. I have not tried this ROM with Gapps.
* You will need to get a third party program to change kernel settings. I like Kernel Adiutor.
The issues:
* Don't use the brightness slider in quicksettings. If you do use it, the status bar goes away and leaves the top part of the quicksettings panel in its place. I suggest disabling the slider and using the brightness control in the status bar settings. I'm not sure if this is a new bug or the result of too much optimization.
* There are no app snapshots in the recents switcher. This may be internal to Android as a way to save memory for low RAM devices, or it may be a bug in CM.
* The Kindle Fire just doesn't have enough RAM (or rather Android is just too freakishly bloated). Attempting to run memory intensive apps will likely result in them crashing or running slowly because the RAM they are using is being swapped to ZRAM. You may be able to adjust the ZRAM size and get better results.
There you have it. I hope you find it useful.
Ah. I just realize this thread. Going to try the 12.1 now
Sent from my Nexus 5 using Tapatalk
@pfederighi. Running fine and fast on the first boot. I clean flashed it without gapps.
After I flash Pico opengapps, it's rather slow now, but probably adjusting things. I'm going to use this for a while and see.
I M using privacy guard to block wake up and keep wake permission for (almost) all apps, since I don't use app that need to do that. Been set it up like that since ur cm11. Gave me very good battery life.
Will post some screenshot later
Thanks for this
Sent from my Nexus 5 using Tapatalk
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Battery life looks good.
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
View attachment 3514625View attachment 3514626View attachment 3514627
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
kev716 said:
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
Click to expand...
Click to collapse
U don't need supersu. There's su app built in. Try installing Adiutor again, I remember I had that issue too, but I re open it, and it ask superuser request.
Su setting is on developer options. It's enabled by default.
Did u open kernel Adiutor and supersu from notification panel? (the one that tell us that xxx app is installed). I did, and it give that error. starting the app from home screen and app drawer works fine. Dunno if it's related to notification panel one, or u just need to open it twice.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
pfederighi said:
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Click to expand...
Click to collapse
I don't use that many app, so dunno have experience with crashing. I use 1gb zram since ur cm11, although I don't see any benefit. No crashes though.
I'll try 256mb later then.
I thought swap is remmended at 2x ram on Linux?
Sent from my Nexus 5 using Tapatalk
dokie80 said:
I thought swap is remmended at 2x ram on Linux?
Click to expand...
Click to collapse
Indeed, but that is swap to disk. ZRAM is the method of allocating an area of RAM that is treated as a compressed disk and using it as a swap file system. It is a way of using limited RAM more efficiently, at the expense of CPU time, but it is still using RAM. So, on our device, 100 MB is eaten up by graphics buffers and proprietary firmware. Another ~300 MB is eaten up by Lollipop itself. This leaves us with ~100 MB for user programs, which is not a lot. If you allocate ZRAM at 60 MB, that leaves 40 MB of regular RAM + ~120 MB compressed on the ZRAM drive for programs. This gives us more memory to work with, but effectively 75% of it is compressed, which means every time it's read, it needs to be decompressed, and every time it's written, it needs to be compressed. The memory manager of linux does a great job of making it efficient, but it still slows down the system.
If Android were to actually swap to disk, which it can do, it would wear out the solid state media very quickly because there are a limited number of writes before the media no longer works. There have been great advances in the field of solid state technology such as Intel's and Micron's new 3D XPoint (it's awesome, check it out). So, in the near future this may no longer be an issue, but it doesn't help our old devices.
If you really do need the memory, you can make a swap file on an externally powered USB hard disk, mount the drive, and then issue a `swapon path_to_your_swap_file` from the terminal. I've done it before. It's painfully slow, but it works.
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Regarding not using ZRAM:
From what I understand, yes, if you have enough RAM without using ZRAM, then it's generally better to not use it.
Regarding KSM:
KSM compares the specified number (default 100) of RAM pages per check. If it finds that any RAM pages are identical, it merges them to a single copy-on-write page (that is, they will remain merged until a process attempts to write to it, at which point it'll be copied back to separate pages). Since there are often many read-only pages that happen to be identical, it tends to be very effective.
It runs at the specified interval (default 500ms). I've found that increasing the interval to 750ms or even 1000ms significantly reduces system load with no appreciable difference in the amount of RAM freed.
Because for some CPU & RAM intensive programs I've noticed slightly worse performance with KSM running, I have sometimes run KSM for a few seconds to free up the RAM, disabled it, and then run said program. It seems to work rather well. I suppose I could also have left it running and just increased the sleep interval to a higher amount, say 10000ms.
In general, KSM will free up about 10% of the total RAM, which in my experience is true.
CM-11.0
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
pfederighi said:
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Click to expand...
Click to collapse
I would be interested in a 10.2 build.
And of course thx for all your interest in keeping this device alive. Great little tablet.
pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I don't remember facing those issues. About have to press button several time to wake up, sometimes it just need 1-3 secs for the screen to wake, probably because of low cpu clock too.
I remember using 10.x that has privacy guard, but it's different from 11.x. As long I can block wake up and keep wake, I'm sold.
As the sound,
Anyway, since you re offering otterx version, I definitely will test it out, since it's easy and won't require a pc.
Thanks
Sent from my Nexus 5 using Tapatalk
pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I thought CM11 had more free ram than CM10?
VTCruzer said:
I thought CM11 had more free ram than CM10?
Click to expand...
Click to collapse
10 is faster, much more responsive than 11. For free RAM I'm not sure, but AFAIK, free RAM can be set using minfree. More free RAM doesn't mean it will run faster, it just mean less crash on apps and more capable on running apps that need high ram.
@pfederighi already explain about the zram. Using that, we can get more free RAM, but will use More cpu to decompress the zram when accessed. So, probably not faster than without using zram.
If we really want to compare the ram, I suggest to compare the usage (system), not the free one.
Sent from my Nexus 5 using Tapatalk
I too would be very interested in a 10.2 build for otterx