Wow, this device is a lot different from any other android device i've used. Rooting, unlocking, downgrading to unlock...bla bla bla.
Well i am really motivated to install clean rom and so far this is what i've done:
I was on officiel lock and unrooted JB. So i downgraded to ICS, unlocked it, rooted, installed CWM and usually, on any other device i would just flash any rom. But since asus are so freaking strick with their warranties, i rather look like a newb and ask then brick my machine.
So, on the pre-requesites of cleanrom it says
Bootloader: Official Asus Jellybean bootloader
Recovery: TWRP 2.3.1.0 or ClockworkMod 6.0.1.4
I'm not sure, but now that im unlocked and rooted on ICS, can't i just flash cleanrom from recovery or do i really need to be on JB bootloader. Also, since i walready was on JB, did i keep my JB bootloader or did i downgrade it at the same time i reverted back to ICS?
I'm sorry to be such a newb, but with my galaxy S3 i can pretty much do anything to it and i'm not scared a bit of bricking, its so easy to unbrick, but with the tf700, im stressed and rather take my time than rush it.
Thanks for the help!
Lol
Well Fortunately I have made that mistake for you.
It's best to flash clrom whilst on the JB boot loader.
I ran into problems when I flashed clemsyns kernel with clean on ICS.
Sooo yes CleanROM on JB.
Sent from the inside out...
The problem is that clemsyns kernel requires the JB bootloader in order to work correctly. No risk, but it just won't get above 1.3 or 1.4 mhz because the voltage tables between the kernel and bootloader are incompatible.
Easiest way is to do a system restore with a stock JB image from the Asus website. You may lose custom recovery doing this, but since you are unlocked, you can then flash custom recovery via fastboot...
thank you guys, youve been veru helpful! +1
latest ICS bootloader
danger-rat said:
The problem is that clemsyns kernel requires the JB bootloader in order to work correctly. No risk, but it just won't get above 1.3 or 1.4 mhz because the voltage tables between the kernel and bootloader are incompatible.
Easiest way is to do a system restore with a stock JB image from the Asus website. You may lose custom recovery doing this, but since you are unlocked, you can then flash custom recovery via fastboot...
Click to expand...
Click to collapse
please allow me one question. as far as know, the bootloaders of latest ICS version .30 is equal to JB version .18. if so why is JB mandatory?
dc_01 said:
as far as know, the bootloaders of latest ICS version .30 is equal to JB version .18.
Click to expand...
Click to collapse
They are not equal at all. The file size is rather different, and also the version number, which strangely changed from 2.10 to 1.00 in the newer version:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.5.30-20120907"
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.4.18-20121012"
well, I've installed JB and now am runnin cleanrom. I love it! Its fast, snappy and does not lag like the stock rom. I've also installed Clemsyn's kernel but had to revert back to reinstalling cleanrom because I HATED the higher DPI and use DPI modder to reduce it back to 120 and then the tablet didn't want to get past Asus screen where it said "this device is unlocked"
I have higher DPI on this tablet, I thing the stock is perfect and I despise the fast that it comes with the kernel with no option to set it back. Unless I didn't find it. But is it really worth to have that kernel cause as really satisfied with the rom by itself
polish_pat said:
well, I've installed JB and now am runnin cleanrom. I love it! Its fast, snappy and does not lag like the stock rom. I've also installed Clemsyn's kernel but had to revert back to reinstalling cleanrom because I HATED the higher DPI and use DPI modder to reduce it back to 120 and then the tablet didn't want to get past Asus screen where it said "this device is unlocked"
I have higher DPI on this tablet, I thing the stock is perfect and I despise the fast that it comes with the kernel with no option to set it back. Unless I didn't find it. But is it really worth to have that kernel cause as really satisfied with the rom by itself
Click to expand...
Click to collapse
To bring the resolution back to stock you have to bring the DPI to 240 (not 120). Simple change by editing the build.prop (just look for number 160 and change it to 240).
buhohitr said:
To bring the resolution back to stock you have to bring the DPI to 240 (not 120). Simple change by editing the default.prop (just look for number 160 and change it to 240).
Click to expand...
Click to collapse
by default.prop you must mean build.prop because de default has almost nothing in it...
polish_pat said:
by default.prop you must mean build.prop because de default has almost nothing in it...
Click to expand...
Click to collapse
Yes, build.prop, look for the number 160 and change it to 240 save then reboot.
location:
/system/build.prop
before:
ro.sf.lcd_density=160
change to:
ro.sf.lcd_density=240
Had problems getting 240 to stick.
Using ES File explorer the permissions needed to be set rw-rw-rw then back to rw-r-r not sure why.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Related
I thought that the latest bootloader released was locked only for official ROM. This seems inaccurate since I was able to install my Combo in the bootloader (with edited zimage) and I also have more voltage and frequency as a result for my PimpMyGtab.
clemsyn said:
This seems inaccurate
Click to expand...
Click to collapse
I don't think its inaccurate, its just wrong.
IMHO, the bootloader shouldn't be an issue (at least from the end user perspective), with some time invested in getting the 1.1 ROMS working with 1.2 bootloaders (like pershoot suggested in that other thread, a process that apparently needs further debugging right now), everyone should be able to migrate to 1.2 bootloaders (even if its an end user procedure where users repeatedly overwrite the 1.1 kernel in the 1.1 ROM with a 1.2 compatible one).
If this is resolved, the question would then be, "is there a good reason for anyone to keep 1.1 bootloaders on their devices?"
aasoror said:
I don't think its inaccurate, its just wrong.
IMHO, the bootloader shouldn't be an issue (at least from the end user perspective), with some time invested in getting the 1.1 ROMS working with 1.2 bootloaders (like pershoot suggested in that other thread, a process that apparently needs further debugging right now), everyone should be able to migrate to 1.2 bootloaders (even if its an end user procedure where users repeatedly overwrite the 1.1 kernel in the 1.1 ROM with a 1.2 compatible one).
If this is resolved, the question would then be, "is there a good reason for anyone to keep 1.1 bootloaders on their devices?"
Click to expand...
Click to collapse
It took me three reboots but everything is working fine with my COMBO. No issues or whatever. I didn't even make any changes in the ROM part..only in the kernel. I can even restore my data partition from 1.1
clemsyn said:
It took me three reboots but everything is working fine with my COMBO. No issues or whatever. I didn't even make any changes in the ROM part..only in the kernel. I can even restore my data partition from 1.1
Click to expand...
Click to collapse
Will you be releasing a 1.2 based kernel for those of us not running your combo?
"I also have more voltage and frequency as a result for my PimpMyGtab."
For those of us who are idiots, what does this mean and why is it good (assuming it is)?
Sorry to ask what is probably a dumb question, but I figure if the Kernel maker is saying it, it must be important.
clemsyn said:
It took me three reboots but everything is working fine with my COMBO. No issues or whatever. I didn't even make any changes in the ROM part..only in the kernel. I can even restore my data partition from 1.1
Click to expand...
Click to collapse
This is great news clemsyn, can you enumerate the setup process ?!
- nvflash with 1.2 bootloader image (refer to robeets contributions).
- in recovery flash the 1.1 ROM.
- in recovery flash with 1.2 compatible kernel (like your's or pershoot's).
clemsyn said:
I thought that the latest bootloader released was locked only for official ROM. This seems inaccurate since I was able to install my Combo in the bootloader (with edited zimage) and I also have more voltage and frequency as a result for my PimpMyGtab.
Click to expand...
Click to collapse
Great news! I was under the same impression like you.
But, in the light that VS pulled out the new loader... I don't know what to say, what I would like more.
aasoror said:
This is great news clemsyn, can you enumerate the setup process ?!
- nvflash with 1.2 bootloader image (refer to robeets contributions).
- in recovery flash the 1.1 ROM.
- in recovery flash with 1.2 compatible kernel (like your's or pershoot's).
Click to expand...
Click to collapse
Here is the procedure
1. nvflash with 1.2 bootloader by roebeet (4329 regular or 4329 Honeycomb version)
2. Update CWM with compatible booloader
3. Flash ROM (I used my combo)
4. Flash kernel for 1.2 bootloader (I used the froyo version posted in my thread on Slatedriod)
5. Reboot
Then it will most likely hang about 3-4 times, just keep on rebooting and everything will be functional
@Clemsyn
Is the only difference between the 1.2 bootloader and the 1.1 one that it requires a kernel with 8 voltages levels define instead of 7? Are there any other differences between a froyo kernel and a gingerbread/honeycomb one (besides the accompanying ramdisk). They all seem to be 2.6.32.xx.
Just wondering.
clemsyn said:
Here is the procedure
1. nvflash with 1.2 bootloader by roebeet (4329 regular or 4329 Honeycomb version)
2. Update CWM with compatible booloader
3. Flash ROM (I used my combo)
4. Flash kernel for 1.2 bootloader (I used the froyo version posted in my thread on Slatedriod)
5. Reboot
Then it will most likely hang about 3-4 times, just keep on rebooting and everything will be functional
Click to expand...
Click to collapse
Can you elaborate on step 2. It seems like Step 1 would include CWM recovery.
clemsyn said:
Here is the procedure
1. nvflash with 1.2 bootloader by roebeet (4329 regular or 4329 Honeycomb version)
2. Update CWM with compatible booloader
3. Flash ROM (I used my combo)
4. Flash kernel for 1.2 bootloader (I used the froyo version posted in my thread on Slatedriod)
5. Reboot
Then it will most likely hang about 3-4 times, just keep on rebooting and everything will be functional
Click to expand...
Click to collapse
Clemsyn,
Please check. I think it is 4349, not 4329.
I just flashed back to stock from prime via my nandroid backup, but its still using the moobox kernel. Needless to say, certain things are a bit buggy. Do I just flash Eee_PAD_TF101_Kernel_Code_8_2_3_9.zip from the Asus site or do I need something else? Thanks!
I'm not getting impatient, but I am wondering why its not in a sticky. QQ
I would not flash 8.2.3.9 from the Asus site. I did 4days ago and I still haven't gotten the 8.2.3.13 OTA to get me to a stable build
erhovie said:
I would not flash 8.2.3.9 from the Asus site. I did 4days ago and I still haven't gotten the 8.2.3.13 OTA to get me to a stable build
Click to expand...
Click to collapse
No, I've already flashed back to 8.2.3.9 from Prime v1.3 (Based on 8.2.3.13). I'm looking for the stock kernel, not the update
did you ever get an answer?
i flashed the recovery-3.1.0.1-solarnz-R3-240511-1908, wiped data/recovery from clockwork, and even clicked the little tablet reset button is settings (ok i knew that wasnt gonna work).
everything looks stock, but the kernal is still different? any suggestions?
i got a hair under the LCD i jsut cant take anymore, and the charger 0BLF feels like 500 degrees when i charge. i dont want to here asus try to blame that on my kernal.... should i get rid of CWM and the kernal before i send it back? thanks in advance
http://dl.dropbox.com/u/20870695/Transformer/Generic-kernel-signed.zip
Stock 3.1 kernel.
It's kernel not kernal. Your tablet needs to be 100.00% stock in order to be sent back to ASUS.
Didn't 8.4.4.11 include a new kernel? Anyone have that available?
haha. kernel. got it. its not made outta corn?
Kernel Version: 2.6.36.3-00001-gf377a2b [email protected] #1
is that right now?
but my build number says:
HMJ37.prime_epad-1.5-20110626
i was gonna fix that using this method
http:
//dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/
Update_Launcher_SOP_WW.pdf
unless you have another suggestion?
should i delete any SU files on the root or do you think they will look that close for a hair under the LCD issue?
Wrong thread. Sorry
You can revert to the ICS bootloader with the .30 firmware using the information here as a guide: http://forum.xda-developers.com/showthread.php?p=31217902#post31217902
More importantly the new bootloader allows you to boot stock TF300 JB so you can flash back to my ROM if you like. My ROM does NOT touch the bootloader.
Thanks goes to saltxyz for this find.
Mysticial ROM v1 for TF700 and TF300
Thanks and credit to scrosler for his base located here: http://forum.xda-developers.com/showthread.php?t=1881042
Thanks rdejager for his suggestions on kernel kitchens.
And thanks everyone who took the plunge and helped test out the TF300 JB firmware.
STOP
1. I am not responsible for any issues this may cause your device and won't be held for any soft-bricks, hard-bricks, boot loops, exploding pets or Resonance Cascades.
2. You MUST be using the JB bootloader for this ROM to work. (At least I think)
The Goods
Stock
Rooted - credit to scrosler
De-Odex'ed - credit to scrosler
Busybox - credit to scrosler
init.d support - credit to scrosler
Ext 4 optimizations - credit to scrosler
Unsecure boot.img
Battery tweaks
Re-enabled TruMedia and SRS3D
"Unlocked" ro.sf.lcd_density
ro.sf.lcd_density=160 by default
Re-enabled TF700 camera bitrates
What Works/Doesn't Work
What Works:
Camera
GPS
Wi-Fi
Just about everything else
What Doesn't Work:
Changing Brightness
Wi-Fi Direct
Download
Mirror 1: http://dl.dropbox.com/u/83380328/Mystical ROM v1.zip
Mirror 2: https://docs.google.com/open?id=0B9yTvRPDom4ta3JRVVJ1MDQyTDQ
MD5: B309D00CF9F2FE9618607DB16716C931
Installation
1. Power off your tablet
2. Download the ROM
3. Copy the ROM to your MicroSD card or Internal Storage
4. Insert the MicroSD card in your tablet
5. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
6. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
7. Perform a backup from Custom Recovery
8. Wipe EVERYTHING except MicroSD card and Internal Storage
9. From your recovery menu press Install and select the ROM
10. Wait until the install process ends and then restart your device
RECOMMENDED but Optional Steps:
Seriously wipe EVERYTHING but MicroSD and Internal Storage
F.A.Q.
JB seems to be laggy. Any suggestions?
Yes, Wipe!! Even if you've performed a Factory Data Reset or Wipe Data I HIGHLY recommend unlocking your bootloader, installing a Custom Recovery, wiping EVERYTHING and installing the firmware again; preferably using Method 3.
Is there any way to change the Brightness settings?
Yes, through Third Party Apps. The most popular seem to be Lux and Custom Brightness Settings
Are we "SOL" having the TF300 Bootloader when the Tf700 JB Firmware comes out?
Personally I'm not too worried about the bootloader.
Either the official JB for TF700 will have the same bootloader as for the TF300, or it will be a newer version that we'll be able to flash.
The bootloader doesn't seem to be looking for a device check or else the 300 loader wouldn't have installed on the 700.
It really only seems to be doing a sig check for OLDER firmwares, not NEWER.
Why don't we have an Official TF700 JB Firmware yet?
I don't know, ask ASUS. I'm as flabbergasted as you are. We've only found two issues so far!!
Reserved Also
Wow, getting a lot of good roms now, glad to see more stock options too!
Added to the directory...thinking about reflashing! But I just put CM10 on...
DPI Changer
Any way to change the DPI? If you just try to use a DPI changer the tablet won't reboot back up.
alanbradshaw said:
Any way to change the DPI? If you just try to use a DPI changer the tablet won't reboot back up.
Click to expand...
Click to collapse
Just edit the build.prop directly. I personally like Root Explorer for such tasks.
The line your looking for is "ro.sf.lcd_density=160". 240 is default and 200 seems to be a nice inbetween.
Sent from my EVO using xda premium
Just installed this and removed useless apps I don't need and its a lot smoother then just the TF300 build. And I love it Thanks for your work Finally got the idea its not a waste I installed the TF300 firmware XD
Thanks worked great. Used 240
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Are you finding anything on the brigtness controll btw in the kernel stuff?
If I have some spare time I will check it aswell though just wondering
rdejager said:
Are you finding anything on the brigtness controll btw in the kernel stuff?
If I have some spare time I will check it aswell though just wondering
Click to expand...
Click to collapse
Nothing yet.
Feel free to poke around, I certainly don't know it all and am not beyond help or suggestions.
Loving this ROM, nice job
Getting ready to flash this, is there any problems restoring previous TWR backups (JB or ICS) if needed or flashing another JB Rom that doesn't have the TF300 bootloader?
Yes when you flash a stock tf300 JB Rom it changes your bootloader In a way that is not reversible atm not even with a TWRP boot backup.
ICS bootloader based roms (like cm10) will boot but they will be laggy and the volume rocker will not work.
Sent from my GT-I9100 using xda app-developers app
amaury48 said:
Getting ready to flash this, is there any problems restoring previous TWR backups (JB or ICS) if needed or flashing another JB Rom that doesn't have the TF300 bootloader?
Click to expand...
Click to collapse
Lufterfischer said:
Yes when you flash a stock tf300 JB Rom it changes your bootloader In a way that is not reversible atm not even with a TWRP boot backup.
ICS bootloader based roms (like cm10) will boot but they will be laggy and the volume rocker will not work.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Will the JB roms work ok?
amaury48 said:
Will the JB roms work ok?
Click to expand...
Click to collapse
Well yes they will work but not exactly OK ( brightness always on max and thus high battery usage)
But it is important to realize that cm10 and the derivatives are jb based but use ics bootloaders so they do not work equally :
Its like this :
Tf300jb bootloader + tf300 stock jb roms = smooth but high brightness and high battery usage
tf300jb bootloader + tf700 custom roms (includes cm10 und derivatives) = very laggy and volume rocker not working
tf700 ics bootloader + tf700 custom roms (cm 10 and others) = awesome performance and almost everything working
The jb bootloader has a build in check that prevents any older bootloader from installing so there is no working way to downgrade from there
So at the moment it is not a good Idea to flash ANYTHING that uses a tf300 stock jb bootloader because once you did that there is no way to get a fully functional rom at the moment .
Lufterfischer said:
Well yes they will work but not exactly OK ( brightness always on max and thus high battery usage)
But it is important to realize that cm10 and the derivatives are jb based but use ics bootloaders so they do not work equally :
Its like this :
Tf300jb bootloader + tf300 stock jb roms = smooth but high brightness and high battery usage
tf300jb bootloader + tf700 custom roms (includes cm10 und derivatives) = very laggy and volume rocker not working
tf700 ics bootloader + tf700 custom roms (cm 10 and others) = awesome performance and almost everything working
The jb bootloader has a build in check that prevents any older bootloader from installing so there is no working way to downgrade from there
So at the moment it is not a good Idea to flash ANYTHING that uses a tf300 stock jb bootloader because once you did that there is no way to get a fully functional rom at the moment .
Click to expand...
Click to collapse
I restored a Baked Black Bean backup that I created just before installing the Mystic Rom and everything is working perfectly, auto brightness control and volume control. No lagging whatsoever. Could it be cause BBBv3 is a AOSP based ROM? Or was it the TWRP backup that I restored why I don't have any problems?
amaury48 said:
I restored a Baked Black Bean backup that I created just before installing the Mystic Rom and everything is working perfectly, auto brightness control and volume control. No lagging whatsoever. Could it be cause BBBv3 is a AOSP based ROM? Or was it the TWRP backup that I restored why I don't have any problems?
Click to expand...
Click to collapse
I don't know. When I first upgraded to JB from ICS my Brightness worked as well. After reflashing JB Brightness went away. Something seems to be left behind but looking at the configs and initrd it should work and I haven't been able to figure out what it's missing and I haven't been able to reproduce the error.
Could you possibly pull your /system so I can compare it to my ROM stock to see what's new or missing?
MysticMgcn said:
I don't know. When I first upgraded to JB from ICS my Brightness worked as well. After reflashing JB Brightness went away. Something seems to be left behind but looking at the configs and initrd it should work and I haven't been able to figure out what it's missing and I haven't been able to reproduce the error.
Could you possibly pull your /system so I can compare it to my ROM stock to see what's new or missing?
Click to expand...
Click to collapse
I'd be more than happy to do it but your gonna have to walk me thru that process, I'm not that savy with doing that kinda stuff...
is there any way to decrease the temp of the tablet???
Hello,
I am very new to rooting and custom roms so i followed a guide to use cwm to try and root the tablet which didn't work. I was able to install cwm with no issues but when i tried to apply XpLoDWilD root-signed.zip file it would install but when I would reboot with cwm it would say that i would possibly lose root and give me an option to fix root which i would select and then the tablet would reboot and i would use a root check that would say i didn't have root. I wanted to use CWM backup feature before i did any custom roms but i was unable to get a successful backup with cwm. I used cwm to flash CleanRom Inheritance 3.03 onto the tablet and then used a root checker and finally got a successful root result but then i once again tried to backup my tablet using CWM and was unsuccessful again. So I want to know what will happen if I were to do a wipe data/factory reset within CWM or while I am booted into the android OS. I was able to do a titanium backup and copied the titanium backup folder to my mircosd card. Is there anything I need to watch out for or any other backup method i need to do on my tablet?
If you already have a Custom Recovery why the hack you want to stay on original Stock?
CleanRom is twice as good and Stock related, rooted and if you flash a kernel after even OC.
If you really like to root stock there is a superuser file somewere out here called Superuser-3.2-RC3-arm-signed. This should do the trick. But as I wrote before with this you will have a VW Beatle with Clean you have a Porsche
I agree. Not flashing a custom rooted ROM is, IMO, a waste of a good tablet. I was amazed at the increase in performance after flashing the 2.54 version of Paranoid Android with the OCed Untermensch kernel.
I do like the custom cleanrom
mikaole said:
If you already have a Custom Recovery why the hack you want to stay on original Stock?
CleanRom is twice as good and Stock related, rooted and if you flash a kernel after even OC.
If you really like to root stock there is a superuser file somewere out here called Superuser-3.2-RC3-arm-signed. This should do the trick. But as I wrote before with this you will have a VW Beatle with Clean you have a Porsche
Click to expand...
Click to collapse
I do want to keep my custom rom but was worried about making sure I have the os backed up properly in case i need to do a re-install or something. Is titanium backup enough to get me fully restored incase something happened to my tablet?
wetbiker7 said:
I agree. Not flashing a custom rooted ROM is, IMO, a waste of a good tablet. I was amazed at the increase in performance after flashing the 2.54 version of Paranoid Android with the OCed Untermensch kernel.
Click to expand...
Click to collapse
What steps did you take to OC your tablet? I installed Clemsyn's kernal 1.3-1.8Ghz OC kernal and used No frills CPU to play around with OC settings but haven't notice too much of a performance jump. I also made sure the asus was put in performance mode. Do you have any suggestions on roms, kernel, and no frills cpu settings i should use to get a good performance boost?
I'm running Paranoid Android v2.54 with a modified version Of Unters kernel that can be found in the first 2 posted of the thread. You must use the version That Keegan modified. Read the OP and second post to find the link to the kernel. The ROM has a built in performance settings that allows adjusting of the speed and I/O. I really like the ROM. It works great with my dock too. It has many extra settings that the other ROMs do not have. Read the thread well.
Here the link to it. Keep in mind that there is a beta version also. I am not running that version.
http://forum.xda-developers.com/showthread.php?p=33646170
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2
Can't wait to try your setup.
wetbiker7 said:
I'm running Paranoid Android v2.54 with a modified version Of Unters kernel that can be found in the first 2 posted of the thread. You must use the version That Keegan modified. Read the OP and second post to find the link to the kernel. The ROM has a built in performance settings that allows adjusting of the speed and I/O. I really like the ROM. It works great with my dock too. It has many extra settings that the other ROMs do not have. Read the thread well.
Here the link to it. Keep in mind that there is a beta version also. I am not running that version.
http://forum.xda-developers.com/showthread.php?p=33646170
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot for the info I will definitely try this rom especially since i have a dock as well. I really love this tablet.
Correction..... The Untermensch kernel is located in the 3 post under EXTRAS, not the 2nd post.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
spidasense said:
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
Click to expand...
Click to collapse
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
buhohitr said:
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
Click to expand...
Click to collapse
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
Click to expand...
Click to collapse
You should able to flash cleanrom without losing any data, during the install there're options for many kernels, I suggest try the "_that stock kernel" first
spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
Click to expand...
Click to collapse
Anyone else with an unlocked bootloader uses a custom ROM that sets the display dpi. This has nothing to do with the GPU, it's just a setting that tells Android the display resolution so that it can scale UI elements accordingly.
To get your 240 dpi back, either install CleanROM Inheritance, or the first kernel in this thread:
http://forum.xda-developers.com/showthread.php?t=2106689
that is actually the kernel Iflashed to ttry and fix the dpi. thanks for informing me on that, I had a hunch dpi had something t odo with the problem I was having. I only tried one of them I guess theother one (ill have to check my sd card to find out which one ) will fix it.
and to be clear, I can flash clear rom inheritince and not lose app data or settings?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app