I've had this issue on Mahdi ROM which is what I'm on right now, but also every other ROM and every kernel that I've tried except for ElementalX. Basically, the kernel will change it's max frequency to 1.19 GHz usually, and soemtimes 1.6 GHz or 1.9GHz and you can't change it back until you flash a different kernel. Rebooting doesn't help, and changing it kernel tuner only helps temporarily. Every other kernel app only changes CPU0 for some reason not sure if that's just be or what. It's a very strange problem, and I have not gotten any help or suggestions so far, so if anyone knows how to help, that would be great. Again, this has happened on every single ROM I've tried, with every kernel, except ElementalX (and I think Trinity but I didn't use it long enough to be sure).
Sent from my Nexus 5 using XDA Premium 4 mobile app
RollTribe said:
I've had this issue on Mahdi ROM which is what I'm on right now, but also every other ROM and every kernel that I've tried except for ElementalX. Basically, the kernel will change it's max frequency to 1.19 GHz usually, and soemtimes 1.6 GHz or 1.9GHz and you can't change it back until you flash a different kernel. Rebooting doesn't help, and changing it kernel tuner only helps temporarily. Every other kernel app only changes CPU0 for some reason not sure if that's just be or what. It's a very strange problem, and I have not gotten any help or suggestions so far, so if anyone knows how to help, that would be great. Again, this has happened on every single ROM I've tried, with every kernel, except ElementalX (and I think Trinity but I didn't use it long enough to be sure).
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
go to /etc/init.d/, then delete all the files inside of it, then reboot for it to take affect.
simms22 said:
go to /etc/init.d/, then delete all the files inside of it, then reboot for it to take affect.
Click to expand...
Click to collapse
Didn't help. Still at 1.19 GHz.
Sent from my Nexus 5 using XDA Premium 4 mobile app
RollTribe said:
Didn't help. Still at 1.19 GHz.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well, its not another rom or kernel issue, its an issue on the user side(a mod or a file that you added?).
simms22 said:
well, its not another rom or kernel issue, its an issue on the user side(a mod or a file that you added?).
Click to expand...
Click to collapse
See, I thought that too, but some ROMs this will happen right when I flash and others it occurs a few days in. It's sort of weird. Clean flashed like 10 times.
Sent from my Nexus 5 using XDA Premium 4 mobile app
RollTribe said:
See, I thought that too, but some ROMs this will happen right when I flash and others it occurs a few days in. It's sort of weird. Clean flashed like 10 times.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
there are things that get missed when wiping, like init.d files sometimes. everyone(but 1 person) ive seen this happen to has had it fixed when deleting their init.d folder/files. id recommend flashing the factory img instead of wiping, it one way to get a true clean flash afterwards.
simms22 said:
there are things that get missed when wiping, like init.d files sometimes. everyone(but 1 person) ive seen this happen to has had it fixed when deleting their init.d folder/files. id recommend flashing the factory img instead of wiping, it one way to get a true clean flash afterwards.
Click to expand...
Click to collapse
I think there may be something seriously wrong with my phone... I went ahead and flash the stock image, and everything went fine... but lo and behold on entirely stock firmware my phone still maxes out at whatever frequency it damn well feels like (1.5 GHz right now, but it was at 1.19 earlier). I have no idea what could possibly be doing this.
RollTribe said:
I think there may be something seriously wrong with my phone... I went ahead and flash the stock image, and everything went fine... but lo and behold on entirely stock firmware my phone still maxes out at whatever frequency it damn well feels like (1.5 GHz right now, but it was at 1.19 earlier). I have no idea what could possibly be doing this.
Click to expand...
Click to collapse
if its completely stock, its probably due to mpdecision.
simms22 said:
if its completely stock, its probably due to mpdecision.
Click to expand...
Click to collapse
Okay, I'll be honest I'm not entirely sure how mpdecision works, but from what I understand this is not how it should behave, yes? My phone is just stuck at 1.19 ghz and won't go up even when the CPU load goes up, and then my device lags. If this is how it is supposed to behave, would you mind explaining why?
Bump. Still having same problem would really like a solution, it's extremely annoying and I've seen a few other people have this problem
Sent from my Nexus 5 using XDA Premium 4 mobile app
If the cpu is not hot (thermal throttling) then maybe you have a defective unit :-s
Sent from my Nexus 7 using Tapatalk
Related
So recently, I flashed ViperXL 2.0.0 to go along with the Beastmode 3.0 kernel. Everything has been going well, but I've been encountering some sort of bug...that doesn't really seem to be a bug, but there's something definitely up with my phone.
About once or twice a day, my phone will just get up and reboot itself completely randomly. I'm not sure what, if anything, is actually triggering it. The weird thing is that other than these reboots, my phone runs extremely smoothly - without lag, freezes, or anything of the sort. I'm not sure what the problem is, and I can't really replicate it because it happens so rarely. Anybody else encountering the same sort of issue?
Wrong Forum. Try clean wipe, cache and dalvik cache as well and re-flash the rom.
So recently, I flashed ViperXL 2.0.0 to go along with the Beastmode 3.0 kernel. Everything has been going well, but I've been encountering some sort of bug...that doesn't really seem to be a bug, but there's something definitely up with my phone.
About once or twice a day, my phone will just get up and reboot itself completely randomly. I'm not sure what, if anything, is actually triggering it. The weird thing is that other than these reboots, my phone runs extremely smoothly - without lag, freezes, or anything of the sort. I'm not sure what the problem is, and I can't really replicate it because it happens so rarely. Anybody else encountering the same sort of issue?
Click to expand...
Click to collapse
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Actually it does work - there was an issue with the cam but a fix was posted.
Sent from my HTC One XL using xda premium
absolutelygrim said:
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
false works fine with the camera fix
beankid said:
Wrong Forum. Try clean wipe, cache and dalvik cache as well and re-flash the rom.
Click to expand...
Click to collapse
I was hoping to avoid that actually, because I've set up all my apps, settings, etc. all nicely after migrating from the stock ROM. The problem is that the reboots are sparse enough so that it's not a hindrance, but it happens enough such that it's a lingering annoyance.
crazylilazn said:
I was hoping to avoid that actually, because I've set up all my apps, settings, etc. all nicely after migrating from the stock ROM. The problem is that the reboots are sparse enough so that it's not a hindrance, but it happens enough such that it's a lingering annoyance.
Click to expand...
Click to collapse
l
wrong forum ... and thats the simplest way to fix the reboot problem im on viper and have not had any troubles
also get a backup app saves time..
backup only the data when doing a backup in recovery wipe and reflash 2.0 and them restore data . if the reboots are still there then i would say its an app causing the reboots
CheesyNutz said:
l
wrong forum ... and thats the simplest way to fix the reboot problem im on viper and have not had any troubles
also get a backup app saves time..
backup only the data when doing a backup in recovery wipe and reflash 2.0 and them restore data . if the reboots are still there then i would say its an app causing the reboots
Click to expand...
Click to collapse
I normally use Titanium. So you're saying to not choose "App+Data Restore", install the apps directly from the market after a flash, and then load the data in?
crazylilazn said:
I normally use Titanium. So you're saying to not choose "App+Data Restore", install the apps directly from the market after a flash, and then load the data in?
Click to expand...
Click to collapse
I use app + data but only for market installed apps, I don't backup system apps or any of the apps installed with the rom. I personally have not had any problems doing it this way. I have not had any reboots or major lags on Viper XL btw.
I was seeing this as well, are u oc to the max 2.1? If so bring it diwn to 1.8, and see if it fixes ur problem. It did for me. One of my hox phones can run 2.1 no issues, but the other one........as soon as i try 2.1 i get all sorts of problems. Try a reflash of the kernel, with 1.8 speed. Post results.
Sent from my HTC One XL using Tapatalk 2
thejosh86 said:
Actually it does work - there was an issue with the cam but a fix was posted.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
CheesyNutz said:
false works fine with the camera fix
Click to expand...
Click to collapse
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
absolutelygrim said:
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
Click to expand...
Click to collapse
Checkout post #3 of the BeastMode kernel thread.
zounduser said:
I was seeing this as well, are u oc to the max 2.1? If so bring it diwn to 1.8, and see if it fixes ur problem. It did for me. One of my hox phones can run 2.1 no issues, but the other one........as soon as i try 2.1 i get all sorts of problems. Try a reflash of the kernel, with 1.8 speed. Post results.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I actually flashed the 1.8Ghz version, and I have been running it at 1.7Ghz only.
However, I have all the voltage-step frequencies set to the default. Global voltage is also set at "0 mV". Does anybody have any suggestions for the Voltage Frequency Steps?
Also, although I have the "Use Separate Voltages" unchecked. I noticed two separate settings for Frequency steps that seems kind of odd.
On one, the frequency says 0MHz, with a corresponding voltage of 852mV.
However, right underneath, the frequency says 0MHz again, but with a voltage of 0 mV. Is that something I should change?
absolutelygrim said:
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
Click to expand...
Click to collapse
At least two weeks ago, I only found it because I was flicking through the viper thread.
Like redpoint said check post #3 of the thread.
Sent from my HTC One XL using xda premium
Trying to overclock, and just can't get it to take
ViperXL 3.1.0
ElementalX-1.5
1.09 Hboot
I've gone so far as to completely wipe the 'sdcard' and start from scratch. Running 'lsmod' in terminal shows that the module is loaded, and the max speed I select shows under cpu in venom tweaks. This is driving me nuts! What can I do to troubleshoot?
When you flashed elemental, what did you set as your max CPU speed?
What program are you using to check / set CPU speed?
thebobmannh said:
When you flashed elemental, what did you set as your max CPU speed?
What program are you using to check / set CPU speed?
Click to expand...
Click to collapse
I've tried 1728, 1809, & 1890. I even tried speeds lower than stock, and it still runs at factory speeds, so I'm thinking something is wrong with the oc module, but I don't know his to check. I tried using the app built into viper, setcpu, and kernel tuner. I thought they may be conflicting, and that's why I wiped and started fresh.
Sent from my Nexus 7 using Tapatalk HD
brbarnyard said:
I've tried 1728, 1809, & 1890. I even tried speeds lower than stock, and it still runs at factory speeds, so I'm thinking something is wrong with the oc module, but I don't know his to check. I tried using the app built into viper, setcpu, and kernel tuner. I thought they may be conflicting, and that's why I wiped and started fresh.
Sent from my Nexus 7 using Tapatalk HD[/QUOTE
My guess is to try, ruuing back to stock re rooting and trying again..
Click to expand...
Click to collapse
some phones just cant OC
CheesyNutz said:
some phones just cant OC
Click to expand...
Click to collapse
I'd be soooooo mad
Sent from my One X using Tapatalk 2
WhatTheAndroid? said:
brbarnyard said:
I've tried 1728, 1809, & 1890. I even tried speeds lower than stock, and it still runs at factory speeds, so I'm thinking something is wrong with the oc module, but I don't know his to check. I tried using the app built into viper, setcpu, and kernel tuner. I thought they may be conflicting, and that's why I wiped and started fresh.
Sent from my Nexus 7 using Tapatalk HD[/QUOTE
My guess is to try, ruuing back to stock re rooting and trying again..
Click to expand...
Click to collapse
Not sure it's worth the trouble!
Don't I have to relock the bootloader, ruu, then unlock it again? It's been a while since I did it, and I don't remember where I put my token... Or do I need the token?
CheesyNutz said:
some phones just cant OC
Click to expand...
Click to collapse
It was overclocked before on other roms, but I just can't get it to work on this one.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Well, come to find out, it's oc'ing just fine, just CPU spy wouldn't show anything over stock speeds for some reason
Sent from my HTC One XL using Tapatalk 2
brbarnyard said:
Well, come to find out, it's oc'ing just fine, just CPU spy wouldn't show anything over stock speeds for some reason
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Someone else told me this, but cpu spy shows me running at higher than stick clock speeds.
Sent from my HTC One X+ using xda app-developers app
Try disabling apply on boot in venum tweeks and any other gov app before you install oc in elemental, I had same issue until I unchecked apply on boot then I reinstalled elemental............something is wacky though because I tried to install back to stock with no oc but on reboot settings in Rom revert back and shows oc....thx tho to dev who works hard sharing there work...
Sent from my HTC One XL using xda premium
For the first custom ROM for the Discover go here http://forum.xda-developers.com/showthread.php?t=2673097
These are stock ROM's for the Samsung Disover SGH-S730M. The will work on the S730G also. I have uploaded these so you can either return to stock or use as a base for your custom development. If you use for custom, please give a mention or a thanks as it took hours upon hours to bring the first flashable ROM to this phone.
Option 1 is bone stock, no root, no busy box, no over clock. After flashing this option CWM will ask you if you want to fix root before you reboot from recovery. Select no. If you want root, download option 2 or 3.
Option 2 is stock, with root and busy box added.
Option 3 is stock, with root, busybox and overclocked to 1000mhz
No other changes have been made.
I have flashed and test all three to verify they are flashing and working properly
Option 1 Download: http://d-h.st/S2R
Option 2 Download: http://d-h.st/cI9
Option 3 Download: http://d-h.st/5FZ
Installation:
1. Wipe data/factory reset
2. Flash
3. Wipe Dalvik
4. Reboot
Enjoy!
Waaoooo!, i download, try and come back you, great job
Edit: Install download Option 2, work
Thanks. Hopefully having these available will inspire and other devs to use them as a base for their own custom
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
In the download option 3 you have set kernel with clock at 1000mhz, and he start at 122mhz too ? or it's 245mhz ?
I used option 2 with NoFrillsCPU for setting cpu at 122mhz. I listen music without problem with bluetooth too.
This rom is stable and no problem with battery. Again great job
Minimum is set at 122 max is 1000. It usually runs between 480 and 600, only boosts up to 800-1000 when needed. It's safe to run option 3, and use nofrills, cpu tuner, set cpu etc, and set the max to 800, then if your playing a game or watching you tube, and find your lagging a bit you at least have the option to bump it up to 1000. Then just set it back when your done. That's how I run it
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
atmu5fear said:
Minimum is set at 122
Click to expand...
Click to collapse
I verify is set at 245mhz, possible to doing fix for 122 ?
Bibounet said:
I verify is set at 245mhz, possible to doing fix for 122 ?
Click to expand...
Click to collapse
I have attached a screenshot from my discover, running the same kernel. Minimum is set to 122 and currently running at such speed when screenshot was taken.
atmu5fear said:
I have attached a screenshot from my discover, running the same kernel. Minimum is set to 122 and currently running at such speed when screenshot was taken.
Click to expand...
Click to collapse
Ok, i verify second time and for me is setted at 245 basicaly, but it's ok i changed the default with CPU Tuner. All work great.
Flashed option 2, working like a charm. Dropped it to 800 mhz and seem to be getting better battery life. Thanks
can anyone give odin flashable stock rom?
mmrozibul said:
can anyone give odin flashable stock rom?
Click to expand...
Click to collapse
I have no intentions of building an Odin flashable version as of right now. There's no real need for it as of yet, and the risk of hard bricking your device grows exponentially if you get one thing wrong in an Odin flashable tar.md5 vs a flashable zip. What do you need it for?
Sent from my SGH-T989D using XDA Premium 4 mobile app
Nomad692000 said:
Flashed option 2, working like a charm. Dropped it to 800 mhz and seem to be getting better battery life. Thanks
Click to expand...
Click to collapse
Glad to hear. Option 2 tho isn't overclocked to 1000mhz, its running at the stock 800mhz out of the box.
Sent from my SGH-T989D using XDA Premium 4 mobile app
atmu5fear said:
Glad to hear. Option 2 tho isn't overclocked to 1000mhz, its running at the stock 800mhz out of the box.
Sent from my SGH-T989D using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Should have been option 3. Dam gonga
atmu5fear said:
I have no intentions of building an Odin flashable version as of right now. There's no real need for it as of yet, and the risk of hard bricking your device grows exponentially if you get one thing wrong in an Odin flashable tar.md5 vs a flashable zip. What do you need it for?
Sent from my SGH-T989D using XDA Premium 4 mobile app
Click to expand...
Click to collapse
need firmware because phone is in restarting condition..
I flashed custom recovery + all rom i found but phone not recover..
mmrozibul said:
need firmware because phone is in restarting condition..
I flashed custom recovery + all rom i found but phone not recover..
Click to expand...
Click to collapse
Did you wipe cache's. Dont forget to flash gapps, mine gave me a fit till I did.
Nomad692000 said:
Did you wipe cache's. Dont forget to flash gapps, mine gave me a fit till I did.
Click to expand...
Click to collapse
yes I did but still same.
Great job. Just flashed option 3 to my old Discover. No issues so far. Can't tell if data and all that is good cause I don't have a SIM in it, bit everything else is great. I have a build environment up and ready. Doing some digging and going to try to make 2 different builds for this device. A customizable ROM based on the stock base you've provided, and a CM10 build. Will be a while but may be of some success.
Sent from my SGH-I777 using xda app-developers app
mmrozibul said:
yes I did but still same.
Click to expand...
Click to collapse
This is precisely the reason I want an odin flashable stock rom before i do anything. The phone is only 4 months old for me, cheap yes but still better to have instanly fixed then wasting $100.
The only thing I have found is flashing the "M" to the "G" you have to manually transfer the apn data after the flash. Or you can't send or recieve mms messages. Other than that no problems.
Nomad692000 said:
The only thing I have found is flashing the "M" to the "G" you have to manually transfer the apn data after the flash. Or you can't send or recieve mms messages. Other than that no problems.
Click to expand...
Click to collapse
Ya that's completely to be expected, the M is from Canada, so it has different carrier APN settings. Easy fix. Just google your carriers APN settings and punch them in
Sent from my SGH-T989D using XDA Premium 4 mobile app
Hi guys =)
After I unlocked bootloader and flashed a custom Kernel, my phone started freezing and sometimes it gets stuck on a bootloop. I've flashed two custom Kernels and the stock one, but nothing seems to help My phone freezing happens frequently. And I can notice some glitches when listening to music or using Chrome. Sometimes I'm doing nothing and it freezes. After a couple of minutes frozen I can use it again.
Do you have any idea on how to fix it? It's quite annoying if I must say.
Latest firmware btw. Rooted.
igohenrique said:
Hi guys =)
After I unlocked bootloader and flashed a custom Kernel, my phone started freezing and sometimes it gets stuck on a bootloop. I've flashed two custom Kernels and the stock one, but nothing seems to help My phone freezing happens frequently. And I can notice some glitches when listening to music or using Chrome. Sometimes I'm doing nothing and it freezes. After a couple of minutes frozen I can use it again.
Do you have any idea on how to fix it? It's quite annoying if I must say.
Latest firmware btw. Rooted.
Click to expand...
Click to collapse
If you're using Phantom Kernel, may I suggest you to try version 4.5 like @faizalotai said to me on this. When I was using latest version, my phone freezes every time, but the downgrade solved the problem. You can get the v4.5 from attachments
It's exactly the lastest version I have flashed on my phone. I'll give it a shot. Thanks =D
You can try to use thunder zap kernel too.
Sent from my C2105 using xda app-developers app
srcharged said:
You can try to use thunder zap kernel too.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
I've never used TZ, 'cause I read in other posts that it mess up a bit the modules and kernel files, besides phone's heat up a lot and for some users they can only change kernel after a fresh FTF flash. Is this true?
NO!!
DsvCdsSoftware said:
I've never used TZ, 'cause I read in other posts that it mess up a bit the modules and kernel files, besides phone's heat up a lot and for some users they can only change kernel after a fresh FTF flash. Is this true?
Click to expand...
Click to collapse
Most certainly no! cos i have flashed phantom and back to TZ and then again to phantom and so on loads of times..
i never had any problems. And everything is working crisply for me. No heating issues, nothing..
Im on CM11. Using TZ 4.1 r-2
I'm using. 14 firmware yet, cause I need Bluetooth in my work, but this issues I told you are in 4.2.2, but I'm thinking in giving a chance to TZ
Sent from my C2104 using XDA Premium 4 mobile app
Sure!
DsvCdsSoftware said:
I'm using. 14 firmware yet, cause I need Bluetooth in my work, but this issues I told you are in 4.2.2, but I'm thinking in giving a chance to TZ
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just give it a try and let me know. Use the Voltage table given by him. And soon we will have bluetooth on our devices. Its all set already!
Thanks, @DsvCdsSoftware It worked! No more phone freezing! I also flashed PurePerformances™X, it's just perfect =)
Kernel download:
http://faux.romhost.me/htc_m8wl/kk44/
Change log:
http://faux.romhost.me/htc_m8wl/kk44/changelog.txt
Source:
https://github.com/faux123/htc_m8
Check the unified thread here for discussions and questions:
http://forum.xda-developers.com/showthread.php?t=2712044
Enjoy!
reesrved 1 just in case
Would love to have a faux kernel for this! Faux was always good for battery life..
Sent from my HTC6525LVW using xda app-developers app
Nice thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Flashed your VZW kernel and booted and working great so far thanks!
Sent from my HTC6525LVW using Tapatalk
Glad I made a good choice and bought the m8. Missing your work man. Samsung is kinda lonely and quiet lately..
Flashing can't wait
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 03:37 AM ---------- Previous post was at 03:30 AM ----------
Installed and butta smooth.
Sent from my HTC6525LVW using Tapatalk
Backed up my boot partition and flashed this. It felt noticeably slower after a few minutes so I restored my boot partition. Now my wifi will no longer turn on. How do I correct the issue? wifi will work when I reinstall but If I try to go back to the stock kernel it no longer will. This kernel is WAY slower than the stock kernel.
ocman40 said:
Backed up my boot partition and flashed this. It felt noticeably slower after a few minutes so I restored my boot partition. Now my wifi will no longer turn on. How do I correct the issue? wifi will work when I reinstall but If I try to go back to the stock kernel it no longer will. This kernel is WAY slower than the stock kernel.
Click to expand...
Click to collapse
if you don't have wifi, download again. there was a 5 min window where an older version was with broken wifi was live
Anyone else having trouble reading their sdcard with this kernel?
Sent from my Nexus 7 using Tapatalk
faux123 said:
if you don't have wifi, download again. there was a 5 min window where an older version was with broken wifi was live
Click to expand...
Click to collapse
I have WIFI with your kernel but its SLOW and laggy as heck. When I got back to my stock kernel WIFI will not turn on. Can you post steps to restore the stock modules please.
ocman40 said:
I have WIFI with your kernel but its SLOW and laggy as heck. When I got back to my stock kernel WIFI will not turn on. Can you post steps to restore the stock modules please.
Click to expand...
Click to collapse
reflash your ROM or nandroid backup.
faux123 said:
reflash your ROM or nandroid backup.
Click to expand...
Click to collapse
a reflash of the nandroid boot partition did not work. Still no WIFI. However if I reflash your kernel wifi returns. What modules are being deleted?
Running smooth as silk over here! Does the faux app work on this phone and if so what are the recommended settings that you use please?
Really nobody else with sdcard issues? My 64gb card won't mount. Was working fine before installing kernel
Sent from my Nexus 7 using Tapatalk
Something is definitely up. Phone seems lagier and using Linpack I now get the same and lower results for Single Thread and Multi Thread. It's as if the other cores aren't being enabled.
Sent from my S-Off VZW HTC One M8
My phone runs pretty smooth I have noticed though that the default clock speed is at 1ghz I believe that may be the reason why people are noticing lag ?
Also my WiFi speeds are normal.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
ickedmel said:
My phone runs pretty smooth I have noticed though that the default clock speed is at 1ghz I believe that may be the reason why people are noticing lag ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I noticed that to 1036. I had to reflash my rom since it broke WIFI.
I noticed before I installed faux kernel app the the kernel is set to max cpu speed at only 1000,as soon as I raised it to stock speed it was working perfectly
Sent from my HTC M8, Verizon style.
Sooooo... Does this include fauxsound?
bawksybrown said:
Sooooo... Does this include fauxsound?
Click to expand...
Click to collapse
fauxsound coding is actually done in my private build, but HTC did something non-standard and is conflicting with fauxsound kernel drivers.. that's why i didn't release it yet.. need to troubleshoot and see what HTC has done to the standard sound driver from Qualcomm...
HTC always do something different from everyone else including the reference design from Qualcomm.... Sometimes they OVER engineered...