{
"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"
}
***Built for 3G/4G and Wifi-Only Xoom's running 3.2.0, 3.2.1, and 3.2.2.***
-Rogue v1.4.3-
Rana
Presented By-
TDR
Bazar6
Steady Hawkin
Install Instructions-
-Make a nandroid in your current recovery then proceed
-Download zip file from link below
-Place zip on Micro SDcard
-Reboot into existing recovery
-Choose install zip and select the Rogue Kernel
-Confirm file, wait for it to finish flashing, then reboot
-Enjoy the Rogue Glory!!!
Download's:
Kernel-
Rogue 1.4.3 Rana
or
Rogue 1.4.3 N Rana (Stock clocks for GPU and some other core clocks (sclk, hclk, vde)
Add On's-
Flash any of these after the kernel
USB WWAN
Charge Light Toggle
Source-
Can be found on Github- HERE
Thank You-
Bigrushdog
Coolbho3000
Solarnz
Kcrudup
Cybertronic
Donate to TDR HERE
Stay Tuned For Future Releases!!!
-Partial Changelog-
1.4.3 Rana (Official Release)
+4G Xoom LoS fixed (synced patches from official Google/Moto source tree - Huge thank you to kcrudup!)
+Some other upstream patches
**Note: tun.ko module is now included with the kernel
**Possible issue: Xoom may lock up if suspended with USB OTG HDD connected
1.4.1 Electra (Official Release)
-No more support for Android 3.1
+Revamped installer, works on Android 3.2 and above (including Tiamat ROM 2.2.x)
+SIO (Simple I/O) I/O scheduler by default (CFQ and noop also available)
+SLQB (Queued Allocator) slab memory allocator
+Update modem driver from Qualcomm source
+Tegra framebuffer copy patch (via kcrudup)
*Configuration update with support for 4G Xooms (NOTE: there are reports of problems with some VZW Xooms)
*Fix tegra asm typo
*Fix typo in MDM6600 driver (thanks kcrudup)
1.3.1 Arcturus (Official Release)
+Rogue branding
+A bunch of upstream patches
+Handle corner case of non-US Android 3.2
+Added support for Android 3.2.2
+Even more upstream patches (thanks kcrudup and solarnz)
*Overhauled installation script (better detection of non-US Xooms, can force installation by toggling script asserts)
**Android 3.1 support is frozen and will be removed in future releases
-Special Instructions-
This version of Rogue comes packed with a maximum CPU frequency of 1.7GHz and user adjustable voltages for each frequency. Use these features responsibly! Do not select "Set on boot" unless you are confident the settings you chose are stable! Always make backups!
How to use the voltage control:
The stock frequencies and voltages in a kernel are not optimal for everyone. Userspace voltage control lets you either 'undervolt' (to save power) or 'overvolt' (to try and stabilize) any given CPU frequency to meet your needs.
Undervolting-
The easiest way to adjust these voltages is by using the app "Pimp my Cpu", available either from the Market or xda ([APP] 24 June 2011 : Pimp My Cpu 3.0 (OC/UV kernel control tool) - xda-developers). This app will let you to set an undervolt amount for each possible frequency, as well as fill some of the basic overclocking roles of a tool like SetCPU or Droid Overclock.
Note: at this moment, the app "Voltage Control" is not compatible with Launchpad 1.2.0.
Overvolting-
Unfortunately, Pimp my Cpu does not do overvolting, so you need to execute a shell command to set an overvolt amount.
Say for example 1600MHz isn't quite stable, and you want to give it a little help. From either adb shell or Terminal Emulator, execute the following commands:
su
echo "0 -25 0 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
The second line has a series of 13 numbers, mostly zeros. They represent the number of millivolts to subtract from the default voltage of each possible frequency, starting from the higest (1700MHz) to lowest (216MHz). So in the above example, we apply a negative 25 millivolt undervolt ( which transleted to a 25 millivolt overvolt) to the second fastest CPU frequency (1600MHz). Note that the minimum voltage is 770 millivolts and the maximum voltage is 1400 millivolts. If your new voltage exceeds these limits, it will not work.
Here is an example of bumping up 1500, just so you get how its done:
su
echo "0 0 -25 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
In Pimp my CPU, you will see the following as a result of the first command
Sweet man! Thanks for the hard work! I will give this a test run now.
Call me Noob but will this kernel work for Hammerhead 2.1?
diablo2224 said:
Sweet man! Thanks for the hard work! I will give this a test run now.
Click to expand...
Click to collapse
Thanks for the support bro!
Genshard said:
Call me Noob but will this kernel work for Hammerhead 2.1?
Click to expand...
Click to collapse
Yes it sure will
diablo2224 said:
Sweet man! Thanks for the hard work! I will give this a test run now.
Click to expand...
Click to collapse
let us know if you find a better stability with higher clock than 1.5 with voltage tweaks
joshndroid said:
let us know if you find a better stability with higher clock than 1.5 with voltage tweaks
Click to expand...
Click to collapse
That all depends on the Xoom...
Steady Hawkin said:
That all depends on the Xoom...
Click to expand...
Click to collapse
So true. The Xoom I use primarily has no issue at all running 1.7 Ghz night and day (it's the 3G model, although that doesn't really matter) but my wifi model (both bought on the same day) acts very poorly above 1.504. So, it's more luck than anything else, based on what others have posted as well, as to what speeds your Xoom will support. Goes without saying, be careful... I bricked an epic pushing it to far and foolishly ignoring the warnings it gave me where i could have prevented the expensive paper weight I ended up with.
The kernel seems to be working very well as expected. I've been running it for a bit now, and I am undervolted at -25 mV, and it's doing just fine. Can't tell if it's more stable than the previous build though because the previous build was pretty solid. No issues so far. Thanks again!
Awesome!!!
I flashed it.
Thx!!
I can't understand
what dose it mean
'Android 3.1 support is frozen and will be removed in future releases'
So this kernel are not currently support the Android 3.1??
or support now??
Hi, any instructions on how to use USB_wwan after insmod with
a 3g USB dongle?
Thanks!
Enviado desde mi MB860 usando Tapatalk
kokjsch said:
I can't understand
what dose it mean
'Android 3.1 support is frozen and will be removed in future releases'
So this kernel are not currently support the Android 3.1??
or support now??
Click to expand...
Click to collapse
It is supported in this kernel, but in the future we likely will not support it.
Thanks to answering my question.
lhurtado said:
Hi, any instructions on how to use USB_wwan after insmod with
a 3g USB dongle?
Thanks!
Enviado desde mi MB860 usando Tapatalk
Click to expand...
Click to collapse
Hi, I'm still not sure about using a 3G USB Dongle, but it should work with wired tethering from a phone.
Here are the instructions from bigrushdog.
USB Tether: Plug OTG cable into Xoom. Plug phone with microUSB cable into OTG cable. On phone, enable USB Tether. On Xoom, run the following in terminal or script manager (Scripter, GScript, Tasker) of your choice.
dhcpcd usb1
setprop net.dns1 8.8.8.8
The Xoom will not show any indication that there is a network connection. But pull up your browser and surf away.
Click to expand...
Click to collapse
Thanks Steady, stable as always
thanks.
one question, can not access wifi with HC3.2.2 on wi-fi only xoom(MZ604) whether this kernal can resolve that or we need to wait for new rom based on 3.2.2?
also which governor/scaling is best for your kernal?
musashiken said:
Hi, I'm still not sure about using a 3G USB Dongle, but it should work with wired tethering from a phone.
Here are the instructions from bigrushdog.
Click to expand...
Click to collapse
Thanks! I misunderstood the use of this module.
I flashed the 'N' version of this kernel and then I flashed the Charge lite toggle. Is there anything else I need to do to enable this? I flashed twice and the light still isn't on while charging.
One other thing, the only reason I haven't tried the non 'N' version of the kernel is because I use SetCPU instead of PimpMyCPU. Can you use SetCPU in order to set the overclock freq or is there a specific reason for using PimpMyCPU? I have done overclocking on my Droid Incredible so I am not a noob at it but at the same time I just wanted to ask before hand.
Xoom 3.2
Related
As some of you know, I have encountered some problems while developing this ROM. Some very bad problems actually. Even though I've managed to fix them, it's not enough for me. The only way we can all enjoy VanillaEclair at the moment is to use 3.0, which has the most stable kernel yet, but unfortunately I haven't got the sources anymore.
I will continue my work on the OTA updater, on the kernel, on the framework and on A2DP. Also, I want to improve the VanillaEclair website, so that it can be a useful tool for us all. As I'm working alone, I can't do many things at a time. So please understand that this little break has a good reason behind.
Below you can find the links to VanillaEclair 3.0. If you want something more functional, I suggest you try MaXo64's aHero 1.0. I really do understand that you need a functional phone, and I am exactly in the same position, since the Hero I'm using for development is my everyday phone.
The ETA of VanillaEclair 3.3 is Sunday the 6th. Please post here for apps suggestions, feature requests and wish me luck! Cheers!
DOWNLOAD VanillaEclair 3.0
VanillaEclair 3.2 "Let me put a smile on that face" is the latest VanillaEclair build. For those of you who didn't flash the previous versions, this is the fastest and most stable vanilla 2.1 out here.
NOTE: From 3.1 I won't be supporting any issues if you're using JIT. If you're using it I assume that you are an experienced user. This ROM gives you enough performance, and you won't feel a performance boost after flashing JIT anywhere else than Linpack.
See posts #2 and #3 for more info related to the ROM. Discussions about 3.2 start from here.
Based on the latest 2.6.29 sources, provided by behnaam. Thanks.
Changelog:
- fixed battery issues
- added a few modules
- fixed auto brightness(it seems that this works only for newer phones)
- added EXT4 support
I would also like to say thanks to all users that have been reporting bugs, creating bootanimations and posting fixes. You have helped me improve this! You are great!
For info regarding overclocking, battery and such read posts #2 and #3.
Features:
- GPS & A-GPS
- 100% working youtube
- 100% working camera
- 100% working gallery
- facebook sync(100%)
- busybox
- root
- a quite large APN list
- VPN
- HUGE performance
Benchmark results * without JIT, [email protected]:
- Linpack: 3.35MFolps
- Neocore with sound: 30.1FPS
- Neocore without sound: 33.3FPS
Issues:
- A2DP(will be fixed soon)
If you're not using A2SD, you might get an insufficient storage error when trying to install apps from market. You can fix that in two ways:
1. wipe again after flashing the ROM
2.
adb shell
chown system.system /data/app
Click to expand...
Click to collapse
What's next?
- OTA updater after everything is 100% stable (if you can help me please let me know)
- A2DP, button lights
- backport BFS
- froyo
Because of the bad battery life and some other problems, I've decided to take the link down for the moment. The updated fixed version will be available tomorrow, the 1st of June. Sorry for the inconvenience.
{
"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"
}
Click to expand...
Click to collapse
If you like VanillaEclair, please help me buy a GSM Hero for Dev only.
HOW TO OVERCLOCK - noob-friendly tutorial with recommended settings.
Experienced users might use other settings.
1. Download OverclockWidget from Market (it's free)
2. Put the widget on your screen and make sure you allow it when the Super User permission request comes up(also check the remember option).
3. Reboot
4. Tap it once and select Advanced Setting
5. Check Differ Freq Screen off
Recommended settings:
Screen on: min- 691200 max- 691200
Screen off: min- 245760 max- 245760
6. Check auto start on boot and press save.
Notes:
- overclocking gives you a huge performance boost
- overclocking does not break your phone; it doesn't cause overheating
- overclocking will not affect your battery life(i've taken care of that)
Apps 2 SD FAQ:
1. How do I enable it?
It enables automatically is you have an EXT partition on your SDCARD.
2. Can I use EXT4?
No, sorry. Only EXT2/3 are supported at the moment.
3. What about dalvik cache?
Dalvik-cache is automatically moved on your EXT partition.
Battery tip
IF you're using VanillaEclair 3.1, you shouldn't need to recharge for about 3 days. If you can't get that much, follow the steps:
- wait until the battery is 5-10% left
- go to your recovery image and wipe battery status
- recharge your phone using the wall charger for 4-5 hours or so - you can leave it overnight
That's all!
More about Overclocking(for experienced users):
In VanillaEclair 3.1 I've included a wide range of frequencies that you can use. Here it is - Overclocking widget gets it automatically:
122880
160000
245760
352000
400000
480000
576000
595200
614400
652800
691200
768000
806400
Click to expand...
Click to collapse
I've been able to run at 806MHz, but the phone got VERY hot and sometimes unresponsive. The highest save to run in daily use frequency is 768MHz, but not all phones can go that far!
Downloading now!
Very curious about this one. Will report when I got it booted!
gawd!! i'm wetting LOL
did u try to turn on JIT on this rom? and what is result of linpack on jit?
is it based on cyanogen?
No JIT package?
I don't think you need jit @691MHz, but the JIT package and AS package will come in 30 minutes.
RaduG said:
I don't think you need jit @691MHz, but the JIT package and AS package will come in 30 minutes.
Click to expand...
Click to collapse
I can only OC @ 670, so I need it
I am flashing just now, I hope that will be your perfect build since on 2.0.3 I had a lot of problems
20Mhz won't make any difference
trashed78 said:
is it based on cyanogen?
Click to expand...
Click to collapse
+1
Thanks by the way
The kernel is based on benhaam's sources
I don't think speed is the real reason why adb not working. compares to nexus, hero's speed are very slow
Downloading now
Will try it out and post the feedback... can't wait!
witysimon said:
I don't think speed is the real reason why adb not working. compares to nexus, hero's speed are very slow
Click to expand...
Click to collapse
I didn't say that speed caused ADB not to work...
OK here goes
Please report if A2DP works... it should.
restoring my apps ....
damn i so feel like a 3 yrs old opening christmas pressie!!
RaduG said:
20Mhz won't make any difference
Click to expand...
Click to collapse
I was just kidding
Since I don't use application that seems to have problems with JIT, I always used it.
Bricked-Kernel One X (endeavoru)
The first 100% stable kernel for the HTC One X (endeavoru)
(thx HTC for the screwed source btw, fixed it ^^)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
Features:
Based upon HTC source
Fixed all stability issues from the HTC source
Fixed all section mismatches
Various other fixes
Sweep2wake
tegra_mpdecision, which completely replaces nvidias hotplug manager (better battery life + performance)
extensive sysfs interface for mpdecision with all the tuneables you want
modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
fixed sound playback while screen is off
GPU OC (484Mhz)
Variant free CPU OC for all phones (51 - 1600Mhz)
Compiled with gcc4.7
fixed max cpufreq resets throughout the kernel
all cores now use the max freq (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Check the changelog for the rest
Changelog @ bricked.de
What is sweep2wake?
How to install?
!!!!IMPORTANT!!!!Flash through recovery. But:
Since the htcdev unlock prevents us from flashing the boot partition from recovery, the installer will ONLY INSTALL THE MODULES & disable the HTC screenshot! (needed as a fixup for sweep2wake, use the AOSP screenshot pwr+vol.down instead)
_YOU_ will need to flash the boot.img within the zip (folder: kernel) yourself! (extract it to your desktop so you can use the commands given to you here)
I can't stress enough how important this is. _YOU_ will need to flash it.
How to do that (full guide, if you use the reboot option given to you by the installer you will only need steps 1 & 4-7)
1. Install HTC drivers (how to do that is explained a hundred times all over the web)
2. Reboot
3. in the boot animation, connect your phone to your computer and do:
adb reboot-bootloader
4. You should now see "FASTBOOT USB", if that is the case:
fastboot flash boot %USERPROFILE%\Desktop\boot.img
5. fastboot reboot
6. check with: adb shell uname -a if it says bricked.
7. enjoy
ofc these steps can also be done before the installer is executed from recovery. Just be sure to complete both.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
With special thanks to all piggy bank donators!
Thank you very much!
Source:
Battery life
{
"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"
}
(InsertCoin)
Performance:
Knowledge base:
(under construction)
tegra_mpdecision manual:
coming soon(tm)
Why only clock with 1.4 Ghz max?
That's not a fix, just a point of opinion. I provide stock or close-to-stock kernel settings in regards to UV/Clocks. Usually I don't take HTC's 'stock' but the manufacturer of the component. In this case the soc, so NVIDIA.
Our stock-phone is clocked with 1.5Ghz single core and 1.4Ghz multicore (as soon as the 2nd core comes up). Usually, whatever you do, you will instantly trigger the second core to come up, if even only for a short time. This would effectively limit the cpu clock speed to 1.4Ghz for that time.
Since I overwrote the clock reduce, our phone will clock with the set max at all times. Which, in this case, is overclocking.
So I just reduced the clock back to it's "stock" setting and please trust me that you won't notice the difference to stock in Benchmarks, UI performance, or anywhere else. Not only because it is only 100Mhz on ONE CORE, but also because that core seldom runs alone and therefore can only use the 1.5Ghz for a very short time.
You are ofc free to clock it back to 1.5Ghz again. Please note that this counts as overclocking and the same rules as undervolting apply to it.
Soon to be tested will post results...
Sent from my HTC One X using XDA
Will it work with all the builds say 1.29, 1.28, 1.26?
Sent from my HTC One X
THANHVO31 said:
Will it work with all the builds say 1.29, 1.28, 1.26?
Click to expand...
Click to collapse
I am on 1.29, that's what I have tested. Chances are it will work fine with all builds, test it and report back
got excited and flashed the kernel,
no luck, stuck on htc splash screen
- 1.28 firmware(coredroid 2.1 ROM)
show-p1984!!!!!!!!!!!!! im so happy to see you here!!!!!!!!!!!! love your work on the bricked kernel for the hp touchpad!!!!
cant wait to get stuck into this one!!!!!!!!!
also will you be adding otg support?? just seen it in the changelog for the eternity kernel.
once again so glad to see you working on this awesome device!!!!!!!!!!!!
Buhhhuuuhhhuuuuuuu.... No pc atm.
Download your kernel right now, flash @ 6:15 dhft! (deagleonehomecommingflashtime)
Thanks show, will report
InsertCoined from my nearly"bricked" One X (thanks show, for doing your business^^)
after test eternity project i will test yours. Thanks for your work!!
Just pushed this. Booted just fine. No freezes or reboots. But I do have WiFi error
Sent from my HTC One X using xda premium
Can i install it tru CWM ?
wolfraim said:
Can i install it tru CWM ?
Click to expand...
Click to collapse
TRY reading the OP bro.
I just flashed it and flashed the Boot.img no WiFi. I flashed it through recovery twice. And manually flashed the Boot.img. Still no go. Any idea?
EsHi sir ......hopefully you Will support call recorder....please any chance to provide this feature to one x owners....thanks again in advanced
rayford85 said:
TRY reading the OP bro.
Click to expand...
Click to collapse
Sorry about it. Now im flashing.
---------- Post added at 10:47 PM ---------- Previous post was at 10:37 PM ----------
Installed without problems... no wifi problems for now.
i just do an full wipe with my VillainRom, then i flash the boot and start all again.
Any issues i will put here.
Thanks for now hahaha
rayford85 said:
Just pushed this. Booted just fine. No freezes or reboots. But I do have WiFi error
Click to expand...
Click to collapse
ShyamSasi said:
I just flashed it and flashed the Boot.img no WiFi. I flashed it through recovery twice. And manually flashed the Boot.img. Still no go. Any idea?
Click to expand...
Click to collapse
I am seeing this too in the latest version. I forgot to include some modules :/ Gimme a few.
hasan_abeer said:
EsHi sir ......hopefully you Will support call recorder....please any chance to provide this feature to one x owners....thanks again in advanced
Click to expand...
Click to collapse
I don't mean to sound rude. But you REALLY don't need to post this everywhere! The devs are aware it's a feature people want, but the reality is that getting things STABLE first is the highest priority.
It's not point getting call recording added if the phone doesn't work properly. Please just be patient and stop spamming every thread with your requests.
M.
+1 for Wifi error (maximus 1.3)
+ Led Notify always ON (red)
I had Flash boot.img + copy modules at CWM.
Sweep2Wake is cool but sorry.
Man, sweep2wake its amazing!
Now with no problems about wifi, its weird :s im using VR 2.
Bricked-Kernel One X (endeavoru) AOSP (CM10/etc)
The first 100% stable kernel for the HTC One X (endeavoru)
(thx HTC for the screwed source btw, fixed it ^^)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
Features:
Based upon HTC source
Fixed all stability issues from the HTC source
Fixed all section mismatches
Various other fixes
Sweep2wake
tegra_mpdecision, which completely replaces nvidias hotplug manager (better battery life + performance)
extensive sysfs interface for mpdecision with all the tuneables you want
modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
fixed sound playback while screen is off
fixed bluetooth toggle with gps active
GPU OC (484Mhz)
Variant free CPU OC for all phones (51 - 1600Mhz)
added init.tegra.post_boot.sh support
Compiled with gcc4.7
fixed max cpufreq resets throughout the kernel
all cores now use the max freq (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Check the changelog for the rest
Changelog @ bricked.de
What is sweep2wake?
How to install?
!!!!IMPORTANT!!!!Flash through recovery. But:
Since the htcdev unlock prevents us from flashing the boot partition from recovery, the installer will ONLY INSTALL THE MODULES & disable the HTC screenshot! (needed as a fixup for sweep2wake, use the AOSP screenshot pwr+vol.down instead)
_YOU_ will need to flash the boot.img within the zip (folder: kernel) yourself! (extract it to your desktop so you can use the commands given to you here)
I can't stress enough how important this is. _YOU_ will need to flash it.
How to do that (full guide, if you use the reboot option given to you by the installer you will only need steps 1 & 4-7)
1. Install HTC drivers (how to do that is explained a hundred times all over the web)
2. Reboot
3. in the boot animation, connect your phone to your computer and do:
adb reboot-bootloader
4. You should now see "FASTBOOT USB", if that is the case:
fastboot flash boot %USERPROFILE%\Desktop\boot.img
5. fastboot reboot
6. check with: adb shell uname -a if it says bricked.
7. enjoy
ofc these steps can also be done before the installer is executed from recovery. Just be sure to complete both.
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
Donor List:
> Hall of fame <
With special thanks to all piggy bank donators!
Thank you very much!
Source:
Battery life
{
"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"
}
Performance:
Knowledge base:
(under construction)
tegra_mpdecision manual:
coming soon(tm)
Why only clock with 1.4 Ghz max?
That's not a fix, just a point of opinion. I provide stock or close-to-stock kernel settings in regards to UV/Clocks. Usually I don't take HTC's 'stock' but the manufacturer of the component. In this case the soc, so NVIDIA.
Our stock-phone is clocked with 1.5Ghz single core and 1.4Ghz multicore (as soon as the 2nd core comes up). Usually, whatever you do, you will instantly trigger the second core to come up, if even only for a short time. This would effectively limit the cpu clock speed to 1.4Ghz for that time.
Since I overwrote the clock reduce, our phone will clock with the set max at all times. Which, in this case, is overclocking.
So I just reduced the clock back to it's "stock" setting and please trust me that you won't notice the difference to stock in Benchmarks, UI performance, or anywhere else. Not only because it is only 100Mhz on ONE CORE, but also because that core seldom runs alone and therefore can only use the 1.5Ghz for a very short time.
You are ofc free to clock it back to 1.5Ghz again. Please note that this counts as overclocking and the same rules as undervolting apply to it.
Finally ! Showp did it again ! Awesome work mate ! cant wait to test and report back !
First. Let the force be with u
Edit: damn neo bet he used the red pill
Sent from my ICJ One X powered by pure smooth power NCX
Goku80 said:
First. Let the force be with u
Click to expand...
Click to collapse
Nah, second!
May the force be with you too.
Your 8 Hours Early
show-p1984 do we need repack??? :cyclops:
wow,a new bricked kernel,really exited about that one,hope i get it flashed correct on my rom
TAGTRAUM said:
show-p1984 do we need repack??? :cyclops:
Click to expand...
Click to collapse
It is using a modified CM10 ramdisk, should work across all aosp roms, except there are some strange ramdisk edits in you rom.
show-p1984 said:
It is using a modified CM10 ramdisk, should work across all aosp roms, except there are some strange ramdisk edits in you rom.
Click to expand...
Click to collapse
sounds good,so maybe no need for deleting those lines in init.endeavoru.rc.
Will try now
This is exciting. I'm going to wait on a few reviews though as I'm happy with Faux for now.
Thanks for all your hard work!
:good::good: great!!! thank you Show!
Woooow! Coming from neo's v7 which is stable, pretty fast and is supposed to have good battery also (as far as I experienced with former versions) .
But I have NEVER seen a HOX kernel that has so many 51mhz cpu times w/o lags.
This kernel is pure awesomeness, really a new feeling how cold a HOX can be and i bet the battery life will be outstanding
Good to have you back mate
Cheers Pete
ptr_hamilton said:
Woooow! Coming from neo's v7 which is stable, pretty fast and is supposed to have good battery also (as far as I experienced with former versions) .
But I have NEVER seen a HOX kernel that has so many 51mhz cpu times w/o lags.
This kernel is pure awesomeness, really a new feeling how cold a HOX can be and i bet the battery life will be outstanding
Good to have you back mate
Cheers Pete
Click to expand...
Click to collapse
Well here is the magic wand I used:
https://github.com/showp1984/bricked-endeavoru/blob/exp/arch/arm/mach-tegra/tegra_mpdecision.c
show-p1984 said:
Well here is the magic Light Saber I used here
https://github.com/showp1984/bricked-endeavoru/blob/exp/arch/arm/mach-tegra/tegra_mpdecision.c
Click to expand...
Click to collapse
Fixed.
Show is losing it after doing all night sessions making this happen.
@show-p1984,
Earlier tonight I flashed repacked Bricked_onex_v0.3 for CyanogenMod 10 Nightlies - 4.1.1 by TeamNDVRu.
@First impression all is working perfect; wifi, bluetooth, compass, gps and the rom flies, no delays in end call it's just wonderful.
Going to update asap LoL, thanks for your hard work.
Is it necessary to repack it to use in ICJ AOKP?
rpmfc36 said:
Is it necessary to repack it to use in ICJ AOKP?
Click to expand...
Click to collapse
no ,works fine as it is
rpmfc36 said:
Is it necessary to repack it to use in ICJ AOKP?
Click to expand...
Click to collapse
Nope.
Running it now.
Make sure you flash the zip provided in recovery and reboot into fastboot usb to flash the boot.img
Thanks to showp for the aroma love, made it super easy to flash this.
{
"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"
}
Never skip LAG-day - Live on the EdgeSupported: G925T & G925W8 (Based on sources for International - F -
Code:
###Disclaimer###
Your warranty is now void.
We are not responsible if your phone will be damaged, broken, bootlooping or detonating in a thermonuclear reaction.
YOU are choosing to make these modifications and accept the fact that something might go wrong.
Introduction
SimplKernel is developed by SimplTeam. We originate from the Note4 and have a long story of success there. Our builds are known for being close to stock, yet full of useful features and enhancements. The aim is to provide maximum performance and maximum batterylife. No compromises.
Features
# Based on latest G925FXXU1AOE3
# NightClock fully fixed
# Compiled with AARCH64-Android-4.8 toolchain - Kudos Google, this is one is awesome
# Replaced CPU_FREQ_RELATION_L with C for Interactive -> selects freq with min euclidean distance to target freq, should be more efficient
# MDNIE ColorControl
# VoltageControl (CPU, GPU, HPM, BUS)
# Underclocking by default
# Full Synapse Support
# SELinux mode set to Permissive
# Governors added: powersave, intellidemand, ondemand, bluactive and intelliactive
# busybox and init.d
Click to expand...
Click to collapse
--> More will be added, this is just the start :angel:
Changelog
Code:
R4T/W8 - Same as R4F
R4F
- Based on G925FXXU1AOE3
- Busybox updated to 1.23.2
- NightClock fixed
- GPS Fix for AOE3 based Firmwares
- Synapse included
- Enabled Synapse Support
- mDNIE Control -> Control your DisplayColors! Will be expanded.
- Governor selection for individual cluster (A53 & A57)
- Full CPU VoltageControl for both A53 & A57
- Underclocking to 200mhz enabled by Default
- HPM VoltageControl
- GPU VoltageControl
- Memory Bus, Internal Bus & Image Signal Processor VoltageControl
- mDNIE Tab in Synapse (name is Screen)
- I/O Scheduler settings (Tunables + Definable Read-Ahead)
- BFQ and Deadline I/O scheds added*
- BFQ as default
- VirtualMachine Tweaks
- Full Synapse Settings Backup added
- Fixed 2 GPIO memory leaks + 3rd probable leak
- Memory-killer enhancements (see Github)
- GPU Throttling Levels smoothened
- more stuff I forgot
R2.9F
- Added Overclock and Underclock (@ktoonsez) - Only in Ktweaker for now!
- Added VoltageControl
- Fixed the NightClock - Display is now fully turning off (Switch from MDNIE_LITE to MDNIE)
- DynamicMemoryAllocation: Reduce max PAGE_SIZE to 4 and CMA areas to 4
- Minor tweaks here and there, check my github :D
- Synapse support for 2.9F withdrawn - This build is a patch for NightClock users! R3F coming soon too..
- Added KTweaker for this build - @Ktoonsez ;)
v1.2F/T/W8
- Added T-Mobile, Canadian and I variants (T, W8 & I)
- Added Synapse Support
- Automatized Wifi-Forgetting fix in the ramdisk
- Ported MDNIE HIJACK (ColorControl) - Basic settings for now
- Reverted previous DeepSleep workaround and applied proper patch
- Added awesomeness
v1.1F
- Patched the DeepSleep problem / thanks to @HomerSp for this
- Added governors: Bluactive, Intelliactive, MythX (disabled) and enabled powersave + ondemand
- Added busybox and init.d
- CPU_FREQ_RELATION_C: When scaling freqs, it selects the freq with the minimum euclidean distance to target.
How to install
Via recovery
You have to have a custom recovery like TWRP, Philz or CWM installed.
- Download the kernel
- Reboot to recovery
- A backup is always recommended
- Flash the zip file
- You're done! Reboot and enjoy.
Via Flashify
- Make sure that you are rooted.
- Download the zip and extract the boot.img
- Download the free app Flashify (Caution: Free Version only allows 3 flashes per day!)
- Grant Flashify Root permissions.
- In main screen, select Boot image and navigate to the previously extracted boot.img
Downloads
T-Mobile, Canadian (T & W8): (R4T/W8)
Latest R4T/W8 click here (version with MDNIE and possible viewfinder distortion
Click to expand...
Click to collapse
Please do not make mirrors! If you need one, please post a reply here, and we'll make it happen. Thanks.
If you apply Interactive in Synapse, ALWAYS enable it for both clusters. Enabling it for only one will cause funny effects, perhaps even a solid chaos, batterydrain and other unpleasant things. You've been warned.
Credits
S6 Edge Tester-Team: For doing what no one did before, flashing a never tested build and going through huge pains to help me. It wouldn't be possible without any of you! :angel:
@strikerdj2011
@jaytehnut
@Briz0wn
@charlypaez
@sswagonman
@ShermCraig
@beats4x
@ktetreault14
@nvict
@skivnit
@leoaudio13
@xadidas4lifex
@reesedizan
XDA:DevDB Information
SimplKernel, Kernel for the T-Mobile Samsung Galaxy S6 Edge
Contributors
mythos234
Source Code: https://gitlab.com/mythos234/SimplKernel-LL-G925F
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R4T
Stable Release Date: 2015-05-24
Created 2015-05-25
Last Updated 2018-06-05
Awesome.... Thanks for you contribution can't wait to try it out.
I'm I wrong does this kernel fix the memory leak
winco209 said:
I'm I wrong does this kernel fix the memory leak
Click to expand...
Click to collapse
"The leak" - There are more leaks than either of us can count, some little ones here and there, and all of them hidden. Unlikely that there ever will come a time that there are no leaks at all
But I guess that you are reffering to the major leak with 5.0? That is in the Rom and framework afaik, and thus not my department to fix. I'm not even sure if 5.1 has the proper fix merged to be honest :/
Flashed on top of Alliance v3, a T-mobile based ROM. Everything is super smooth, call audio is fine, GPS test can't see any satellites. Will try some more stuff to see if I can get it to work and then report back.
EDIT:
Flashed the GPS fix from mythos in the international thread.
That post is here: http://forum.xda-developers.com/showthread.php?p=60932260
Just flashed and rebooted, didn't even wipe cache / dalvik. Worked like a charm!
mythos234 said:
"The leak" - There are more leaks than either of us can count, some little ones here and there, and all of them hidden. Unlikely that there ever will come a time that there are no leaks at all
But I guess that you are reffering to the major leak with 5.0? That is in the Rom and framework afaik, and thus not my department to fix. I'm not even sure if 5.1 has the proper fix merged to be honest :/
Click to expand...
Click to collapse
sorry off topic, but do you think we will get miui ported over to here at some point?
kswa1987 said:
Flashed on top of Alliance v3, a T-mobile based ROM. Everything is super smooth, call audio is fine, GPS test can't see any satellites. Will try some more stuff to see if I can get it to work and then report back.
EDIT:
Flashed the GPS fix from mythos in the international thread.
That post is here: http://forum.xda-developers.com/showthread.php?p=60932260
Just flashed and rebooted, didn't even wipe cache / dalvik. Worked like a charm!
Click to expand...
Click to collapse
Good to hear
srkoza said:
sorry off topic, but do you think we will get miui ported over to here at some point?
Click to expand...
Click to collapse
My profile pic, isn't it? Usually there are votings held in the english MIUI forum to decide which phone will (first) get an official port. By the amount of development and users on XDA, I'd put my bets rather on the edge-less S6. But since we can run their Roms too that should not be too big of a problem.
Then again the official 3rd party MIUI not always is a shining light at the horizon. I never liked it. If there are bugs, they won't always get fixed, very frustrating, but understandable - MiPhones do have priority. As to unofficial porting.. I have literally no idea, but it would be nice to see some CM12.1 and MIUI over here, altough I somehow doubt the latter..
mythos234 said:
Good to hear
My profile pic, isn't it? Usually there are votings held in the english MIUI forum to decide which phone will (first) get an official port. By the amount of development and users on XDA, I'd put my bets rather on the edge-less S6. But since we can run their Roms too that should not be too big of a problem.
Then again the official 3rd party MIUI not always is a shining light at the horizon. I never liked it. If there are bugs, they won't always get fixed, very frustrating, but understandable - MiPhones do have priority. As to unofficial porting.. I have literally no idea, but it would be nice to see some CM12.1 and MIUI over here, altough I somehow doubt the latter..
Click to expand...
Click to collapse
i hope so and yes it was the display picture, im also polish noto dziendobry
No wifi calling I assume?
Woohoo!!
This is going to sound strange, but how do I go about deleting synapse? I've completely reflashed my ROM and it keeps reinstalling itself and I don't want it.
Sent from my SM-G925T using Tapatalk
Awesome update. Thanks.
Malnilion said:
This is going to sound strange, but how do I go about deleting synapse? I've completely reflashed my ROM and it keeps reinstalling itself and I don't want it.
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Delete its folder from your sd card and myapps on google play. That should fix it.
Daxxer2007 said:
Delete its folder from your sd card and myapps on google play. That should fix it.
Click to expand...
Click to collapse
Also in /data, delete .simplkernel
Thats new
is bluactive governor a good choice for battery or performance?
never used it before
thanks!
wase4711 said:
is bluactive governor a good choice for battery or performance?
never used it before
thanks!
Click to expand...
Click to collapse
Never tried it, to be honest. I always stick with Interactive
tigercranestyle said:
thx for the kernel, @mythos234 . smooth as butter.
only one thing i've noticed, but it's not isolated to just your kernel. i've had this issue periodically in the past on nexus devices using aosp roms. it always came back to an issue in the kernel... not the rom. this issue is also present in another kernel in the forums for the s6 edge.
the issue is with google play movies not working. the app will open and you can select a movie, but a few seconds after hitting the play button there is a black screen and then it errors out. it doesn't matter if you are streaming the movie or if it's a downloaded one. black screen and then an error.
i've attached a log of the errors.
oh... i'm running simplrom btw.
thx, brosef.
Click to expand...
Click to collapse
Awkward. I'll take a look at it R5 is coming soon as well. It will be called R5U - The U is for Awesome Unified
I dont seem to be able to get bluactive to stick after switching to it; is there a trick to making it active?
I clidk the check mark after changing to it, but after a reboot, its back to interactive..
thanks! This kernel works great on international/s^/Tmobile any rom I have tried it on! :good::good:
wase4711 said:
I dont seem to be able to get bluactive to stick after switching to it; is there a trick to making it active?
I clidk the check mark after changing to it, but after a reboot, its back to interactive..
thanks! This kernel works great on international/s^/Tmobile any rom I have tried it on! :good::good:
Click to expand...
Click to collapse
Did Synapse boot up correctly or did it say something like "Synapse boot cancelled" in the form of a standard toast message?
it does at first, but then it seems to get SU permission, and appears to load correctly...
thanks!
---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------
Actually I just tried again and I think I got it to work!!!
Sent from my SM-G920T using Tapatalk
How come when I wipe both caches and fix permissions on the kernel after using it for a couple days it makes my battery go to 0% when I boot back up when I knew I still had about 40% left before I did that? Thanks
Sent from my SM-G925T using XDA Free mobile app
TEAM PROJECT DESIRE
{
"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"
}
"We sparked a desire..."
"...then it was a dream...""...and now we made the fullfilment"XerXes Artemisia Kernel for Z1
Blazing speed, packed with full of advanced features, rock solid, stable. Forked from OK Kernel project by olokos. Big thanks for him :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Features
+Based on latest .236 kernel sources
+Based on latest .236 kernel ramdisk
+Built-in TWRP 3.0.1 with adjustable brightness and working encryption
+Built with UberTC 6.0.0
+Built with many optimization flags, such as -O3, Graphite, Fast Math,......
+Cortex A15/Krait optimizations
+NEON VFPV4 optimizations
+Turn on all crypto cores, ciphers, encryption methods, compression encryptions, RNG,....
+Optimized AES/SHA1/bit sliced AES/SHA512/SHA256, faster encryption speed
+Come with cool X-style bootlogo
+CPU Overclock to 2,42GHz
+CPU Voltage Control
+GPU Overclock to 533MHz
+GPU Underclock to 27MHz
+Multiple CPU Gov selection
+Multiple I/O Scheds selection, including VR and tripNdroid
+Multiple TCP congestion algorithms
+Adreno-Idler
+Updated KCAL
+Updated display panel calibration, comparable to Z5 (make sure to set Blue value in White Balance to 110)
+exFAT
+Many ext4 optimizations
+F2FS
+SlimBus overclock to 192kHZ
+FauxSound control
+UHQA headphone mode (Ultra High Quality Audio mode)
+Vibration control
+Advanced LED controls
+2-way call recording enabled
+Intelliplug
+Intellithermal
+Dynamic FSync
+Dynamic management of dirty page writeback
+Frandom
+KCAL Color Control
+ZRAM
+UKSM (Ultra Kernel Sampling Memory)
+LZ4 added
+LZO updated
+PowerSuspend
+Added toggles for wakelocks
+Added mac80211 injection patch and HID patch for keyboard support
+Added Enhance power efficiency: Series of patches from NVIDIA
+init.d
+Simple GPU Algorithm
+Added sysfs interface to Enable / Disable Android Logger
+Added power_efficient workqueues
+Last_kmsg
+Support for kernel mode NEON
+Fastcharge
+Disable CRC checks
+Added per-core overall stats
+Enabled higher eMMC speed modes
+Add API for RGB led
+Atheros Prima Wifi driver
+Display Color Inversion
+RIC disabled by default
+GPU optimizations
+CPU optimizations
+Memory optimizations
+OOM optimizations
+config.gz viewable in /proc
+Disabled cpu boost on screen wakeup
+SELinux removed
+Faster camera startups and operations
+Memory aligning to sector size
+Better managment of writing files back to memory
+Boost CPU freq when migrating threads from one cpu to another
+Using latest sony mkqcdtbootimg, that should improve stuff with boot.img DT's.
Many more I dont remember :silly::silly::silly:
So much features, your Z1 will fly at hypersonic speed.....:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Todo list
+Kexec-hardboot
+Unlocked 24bits audio capabilities
+Updated KCAL, Adreno KGSL
+Updated F2FS
+Added exFAT driver from Samsung
+Added amami supports (togari got it working thanks to @PDesire to be my labrat )
+FIxed some hiccups on newer branch
Click to expand...
Click to collapse
How to install
Simply, just require your bootloader to be unlocked
Flash kernel flashable zip then reboot. Done
Click to expand...
Click to collapse
Notes
Use Kernel Adiutor, Pimp my Z1 and other kernel controls app as my kernel packed so much features that a single app cant handle all of it
Visually, u will see the kernel marked itself as "3.4.110". This is caused by bad experiment attemps and will be fixed on newer ver. The true version of kernel is 3.4.25
Click to expand...
Click to collapse
Download
XDA Server
Click to expand...
Click to collapse
If you like this project, dont forget to press "Thanks" and supports this project. If you can, consider to buy me a coke, coffee or make a donation, that will keep me awake and release things faster
XDA:DevDB Information
XerXes Artemisia Kernel for Z1 (Honami), Kernel for the Sony Xperia Z1
Contributors
BlackSoulxxx, Tommy-Geenexus, faux123, DooMLoRD, [NUT], alnikki25k, AndroPlus, venkat kamesh, sharonliu, olokos, cocafe, PDesire, kwoktopus,
Source Code: https://github.com/BlackSoulxxx/XerXes
Kernel Special Features:
Version Information
Status: Testing
Created 2016-08-30
Last Updated 2017-01-31
Reserved
Reserved
where is the download link?
itemmaster said:
where is the download link?
Click to expand...
Click to collapse
updated...
suitable for everyday use ? , There are some bugs ? .... Maybe more information about what might work and what might not work than to praise Sieco in the kernel is a wonderful ???? .. does it work with the system of MXrom ? or he was tested on some other ? a hundred questions, but only what is on the first page of this crap about the excellence of this rom
Awesome one .lets us try :laugh: btw any chance to add gesture wake sir? Sweep2wake maybe or d2wake?? :angel:
Love your work, man. How does this compare with Advanced Kernel? Anybody tested it yet?
this is the best
@BlackSoulxxx
I tested the kernel with Kryptonian rom.
It works very well, buttery smooth and without any kind of slowdown.
You did a good job bro; I still remember when long ago I saw your progress on git and I wondered if the kernel ever would have published
Some problems I faced: in Kernel Adiutor audio gain doesn't remain set (using pymp my z1 for this), but I think it's a problem of the app, and also the GPU clock (it reset after a reboot); finally, using intelliplug, maximum frequency CPU on screen off seems to have some effects also with screen on (freeze the CPU at that clock while using the phone)
A more important issue is that "suspend_backoff" wakelocks it's here (already controlled by amplify and bbs misbehaving app, but seems to have reported to the kernel, since wakelock appeared after it's installed).
If it can help, even with the kernel of good friend @olokos I had the same problem (maybe cause prima driver?)
Anyway will try this beauty for some days and will see how is battery life.
Thanks again for your work and your time, also good job with the mod Artemisia II :good:
Your team is rocking
Best regards,
Fenix
i was using mx rom with kryptonian kernel, yesterday i flash XerXes Artemisia kernal on top of it
now my phone getting bootloop while showing boot animation, bootanimation stuck and phone restarting again and again, really i cant switch of my device now its restarting, i used red switch to turn it of but , wen i connect to charger it restarting not going to charging mode
my pblm is i cant connect to flashtool ,i tried lot by pressing vol down and connecting usb cable , its not booting into flashmod is ther anyway to fix it ???????????
testing on dstrikerkai and everything seem right not so many cpu/cores controls but the ones included works fine the cpu sometimes keep at full speed at sometimes but not really a problem.
smooth and battery seem ok keep resting and write if something happens but I don't think that happen, thanks for this awesome work
im using 1 day and its rly good, no rebots, fast and i think better than ok kernel and i have 64679 points in antutu with dstriker rom
Ranjith pottekkatt said:
i was using mx rom with kryptonian kernel, yesterday i flash XerXes Artemisia kernal on top of it
now my phone getting bootloop while showing boot animation, bootanimation stuck and phone restarting again and again, really i cant switch of my device now its restarting, i used red switch to turn it of but , wen i connect to charger it restarting not going to charging mode
my pblm is i cant connect to flashtool ,i tried lot by pressing vol down and connecting usb cable , its not booting into flashmod is ther anyway to fix it ???????????
Click to expand...
Click to collapse
SOLVED
My phone was restarting when i press vol down and connect usb ,was not going to flashmod
i open back cover and removed battery and connect usb cableby pressing vol down and put battery back,
and thats it it worked ,
Ranjith pottekkatt said:
SOLVED
My phone was restarting when i press vol down and connect usb ,was not going to flashmod
i open back cover and removed battery and connect usb cableby pressing vol down and put battery back,
and thats it it worked ,
Click to expand...
Click to collapse
Im pretty sure that's ROM or phone HW problems. As i tested it on MXROM, eXisTenZ and Dstriker, all normal...
[Fenix] said:
@BlackSoulxxx
I tested the kernel with Kryptonian rom.
It works very well, buttery smooth and without any kind of slowdown.
You did a good job bro; I still remember when long ago I saw your progress on git and I wondered if the kernel ever would have published
Some problems I faced: in Kernel Adiutor audio gain doesn't remain set (using pymp my z1 for this), but I think it's a problem of the app, and also the GPU clock (it reset after a reboot); finally, using intelliplug, maximum frequency CPU on screen off seems to have some effects also with screen on (freeze the CPU at that clock while using the phone)
A more important issue is that "suspend_backoff" wakelocks it's here (already controlled by amplify and bbs misbehaving app, but seems to have reported to the kernel, since wakelock appeared after it's installed).
If it can help, even with the kernel of good friend @olokos I had the same problem (maybe cause prima driver?)
Anyway will try this beauty for some days and will see how is battery life.
Thanks again for your work and your time, also good job with the mod Artemisia II :good:
Your team is rocking
Best regards,
Fenix
Click to expand...
Click to collapse
Thanks for kind words. I will look at the wakelock problem...:good::good:
BlackSoulxxx said:
Im pretty sure that's ROM or phone HW problems. As i tested it on MXROM, eXisTenZ and Dstriker, all normal...
Click to expand...
Click to collapse
i just tried your kernal in fresh stock .236 i got bootloop again showing ur kernal logo(black xperia) and restarting is it only for c6903??? i am having c6902
Ranjith pottekkatt said:
i just tried your kernal in fresh stock .236 i got bootloop again showing ur kernal logo(black xperia) and restarting is it only for c6903??? i am having c6902
Click to expand...
Click to collapse
My kernel come in white bootlogo, which mean u havent flash it/or flash it wrongly
Hi guys,
Mx ROM 8.5 clean install. After first boot i rebooted into recovery and flashed this kernel. Then Ive pressed reboot into system but no more that black screen. Any ideas? Please
EDIT: May I extract only image and flash it thru the recovery? Will be all functional? because in the package is more files not only kernel
EDIT2: Yes I have unlocked BL
Bootloop
BlackSoulxxx said:
Im pretty sure that's ROM or phone HW problems. As i tested it on MXROM, eXisTenZ and Dstriker, all normal...
Click to expand...
Click to collapse
Im getting a bootloop when flashed with latest mx rom. I've unlocked bootloader.