What's high power usb supposed to be and what is a hard box?
Sent from my GT-I9300
[Kernel/Recovery][P75XX] A1 Kernel V1.9/TWRP2.6.3.0
- Thread starter AAccount
- Start date
What's high power usb supposed to be and what is a hard box?
Sent from my GT-I9300
high power usb :some device have more a normal device power usage (2-2.5X)like a hdd may containe 2.5W power
that may drain a battery on mobile
i'v test 2.5" hardbox(hddbox-sata/ide external case) wigh usb power usage & 3.5" hardbox with external power usage
with diverse hdd
or some other usb device
that may drain a battery on mobile
i'v test 2.5" hardbox(hddbox-sata/ide external case) wigh usb power usage & 3.5" hardbox with external power usage
with diverse hdd
or some other usb device
Sorry guys but I don't have that much time to work on the kernel right now with school back in session again. Actually, this afternoon I tried to make the "honeycomb tablet mode" mod work a bit better and now it will show your custom toggles but you have to have set them in CM10. It remembers the CM10 custom toggles I set and shows them, but I cannot change it. (I did a dirty flash with no wipe.)
A warning: I must have done the dirtiest, least practical, most Microsoft like way of getting the custom toggles to partially work. Mostly just copying in of CM10 files and updating the xmls, new contexts etc... If somebody knows a better way please say so.
-----------------------------------------------------Added------------------------------------------
Updated zip has been posted. Please see the libre office file for explanations of what and I did and maybe help me.
---------------------------------------------------Added 2------------------------------------------
I took down yesterday's method of semi working custom toggles since it would be too hard to keep up to date with the CM changes. I left the instructions posted, but now I'm just undoing this commit to get generic toggles. I'll probably update the 3 files every week to keep them up to date with the latest CM nightlies.
Last edited:
Hi AAccount,
hope you can reply me and give me a little hand.
I have Samsung Galaxy Tab 10.1 GT-P7510, and I am on Samsung stock 4.0.4. I have flashed your A1-p4-1.8.3-wifi-stock.zip.
all good, did not give me any error or anything.
I just want to make sure this is right file I flashed, and it is the most up to date file.
I have SetCPU, and I am about to overlock to either 1200MHz or 1400MHz. I will hate to mess up all the settings and make my tablet slugish..so asking some advice, if I set 12000MHz max and what could be MHz min should be set? I believe some people set both the same, just not sure, so a little advice would be nice.
also about interactive-> cfg? or interactive-->noop? or ondemand??
hope you can reply me and give me a little hand.
I have Samsung Galaxy Tab 10.1 GT-P7510, and I am on Samsung stock 4.0.4. I have flashed your A1-p4-1.8.3-wifi-stock.zip.
all good, did not give me any error or anything.
I just want to make sure this is right file I flashed, and it is the most up to date file.
I have SetCPU, and I am about to overlock to either 1200MHz or 1400MHz. I will hate to mess up all the settings and make my tablet slugish..so asking some advice, if I set 12000MHz max and what could be MHz min should be set? I believe some people set both the same, just not sure, so a little advice would be nice.
also about interactive-> cfg? or interactive-->noop? or ondemand??
2.4 does not work for me .......
I am on p4wifi and after flashing it I was stuck ...... And had to use Odin to flash cwm to boot into my ROM again!
Any ideas!?
Sent from my Nexus 7 using XDA Premium HD app
Dont set both at the same. It sucks your battery cause the CPU never go to sleep. Take someone between 150MHz and 312MHz. The best governor for this Tegra SoC is Interactive with CFQ.
I've tried all possible seetings. Depending on the governor u choose, u may either get good performance, balanced or battery saver. I do recommend like the setting as stated above.
But my setting is :-
min/max : 312/1400 (made mine higher though)
Governer/scheduler : performance/cfq.
Beware though... If trying to go 1500/1600 for max, may cause hang. Coz mine did.
Hyperjumped from my HTC Sensation Z710e using xda premium
But my setting is :-
min/max : 312/1400 (made mine higher though)
Governer/scheduler : performance/cfq.
Beware though... If trying to go 1500/1600 for max, may cause hang. Coz mine did.
Hyperjumped from my HTC Sensation Z710e using xda premium
Good call. I guess I just gotta wait till I face extreme heat n extreme battery drainage now wouldn't I.
Hehe... I already know. Like I said before, I have already tried every possible setting.
No worries. I know why I chose this setting in particular. ^.~
Hyperjumped from my HTC Sensation Z710e using xda premium
Last edited:
so running with Stock ROM (4.0.4), above settings good enough? all I want is stability and a little faster than original stock kernel. I am not looking to overlock to higher than 1400Mhz.
I think it isnt necessary to OC over 1.2GHz. Only if you want to play with it, but with normal using, like surfing etc., you dont see any effect. So 1.2GHz is more than enough.
I think it isnt necessary to OC over 1.2GHz. Only if you want to play with it, but with normal using, like surfing etc., you dont see any effect. So 1.2GHz is more than enough.
correct, but not just normal usage, but say play games too...I know our tablet is what, like more than 12 months old
I think it isnt necessary to OC over 1.2GHz. Only if you want to play with it, but with normal using, like surfing etc., you dont see any effect. So 1.2GHz is more than enough.
Yeap. Agreed. Running at 1.2GHz should be sufficient even if u wanna use it for gaming. Should be no lag running at 1.2GHz.
Hyperjumped from my HTC Sensation Z710e using xda premium
Re: [Kernel/Recovery/MOD][P75XX] A1 Kernel V1.8.4/TWRP2.3/Simple Mods
Why couldn't you? Either or should be fine.
Sent from my Infamous Tab.
Why couldn't you? Either or should be fine.
Sent from my Infamous Tab.
Alot of talk about TWRP in this thread. I wasnt sure if this was required.
Ive flashed it in cwm and it works fine. Thanks.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
187:good: First of all :good: Thank you for your patronage!!!
:laugh::victory:
Before you do anything: This is purely at your own risk and I will not be responsible for anything that happens to your tablet. I flashed it on mine at my own risk.
Compatibility Information: There are 2 different versions. 1 for stock and 1 for Cyanogenmod. Even though the kernels are intended for the 3G tablet it will work just fine on a WiFi only tablet (like mine). This makes the build process less messy.
**Sources Fully documented v1.9 beginner friendly sources now available including the build script. If more explanations are required, please say so. However, remember that the explanations are not intended to be a blind step by step instructions of going from samsung source to A1.
TWRP V2.6.0.0: Please read: do not worry about any kind of "E:A: Render Error". This is a side effect of removing some image files to save place on the recovery image so it will fit on the 5MB. The error simply means it failed to show (render) and image file that it is looking for. This is not harmful at all. If you can't flash the recovery please try the dd method.
TWRP V2.6.3.0: There are no more E:A Render errors. All graphics that were removed are there. Also, the recovery will install supersu if no root is detected. That feature has also been restored. The kernel has been stripped of anything not recovery related to shrink it down. It also has selinux support which allows the "set_metadata" zip installation to work. The download is in the attachments below.
Changelog:
Changelog:
- Voodoo sound <-- new to version 1.0
- USB charging enabled as well as charging from other chargers *** fixed V1.5.4 thanks to pershoot
- Overclock to 1.2GHz <-- new to version 1.2
- NTFS modules enabled, ondemand default frequency scaler, noop default disk io scheduler <-- new to version 1.2.1
- GPU overclock from 333MHz to 400MHz. <-- new to version 1.3
- Overclock to 1.4GHz <--new to version 1.4
- Support for Current Widget <-- new to version 1.5
- CIFS enabled in kernel config, 1.4GHz attempted stability fix (thanks to jaswinky) <--new to version 1.5.2
- Wifi driver compiled as module <--new to V1.5.3
- More voltage anomalies fixed, updated battery driver to pershoot's 3.1 <-- new to V1.5.4 and V1.5.5XE
- Fixed charging boot bug <--new to V1.5.6SE
- (In case you were wondering 1.5.7 had an issue in it.)
- Disabled frequency lock, added 1GHz default max (you can change it to 1.2GHz or 1.4GHz after boot), 216MHz default min CazeW's suggestion <--new to 1.5.8SE+XE
- Enabled pershoot build/vfp optimization commit, added 150MHz minimum frequency <-- new to 1.5.9SE+XE
- Boot script support (put yours as /data/local/a1init.sh) <-- new to V2.0
- Smarter ram disk that only initializes 3G on 3G tablets<-- new to V2.1
- 1.5GHz && 1.6GHz OC available, cifs utf8 kernel module available <-- new to V2.2
- Support for CM9 <-- new to V2.2CM
- Enabled xbox controller module as xpad.ko <--new to V2.2.1
- NTFS moved to kernel module instead of built in, CIFS moved to kernel module instead of built in, enabled option.ko and usb_wwan.ko for connection of 3G dongle, all nls charsets/codepages built as modules <--new to V2.2.2
- V1.6.3 is pretty much V2.2.2 but without my custom ram disk. I've also tried a boot script method proposed by Toldo but haven't had time to test it yet. Please flash the CM9 stock kernel or Samsung stock kernel before trying V1.6.3.
- Applied git patch to disable mmc_cap_erase <-- new to V1.6.4
- Voltage control, cifs built in again <-- new to V1.7
- Galaxy Tab 8.9 specific fix <--new to V1.7.1
- Cyanogenmod charging mode fix <--new to V1.7.2
- Galaxy Tab 8.9 specific feature <--new to V1.7.3
- CM10 compatibility fix, enabled Samsung's powersaving governor <--new to V1.7.4
- followed pershoot's "-defconfig: jb: unset TEGRA_CONVSERVATIVE_GOV_ON_EARLYSUPSEND" change to fix odd 450MHz capping issue <--new to V1.7.4b
- Copied in pershoot's keyboard dock driver <--new to V1.7.5
- 801MB RAM enabled <-- new to V1.8
Rebased on pershoot's November 17 source <--new to V1.8.1- Back to samsung base, follow pershoot's suggestion of Nexus7 mtp drivers to fix mtp, enabled zRam <--new to V1.8.2
- Reduced RAM to 785MB to prevent intense 3D games issue, enabled KSM (check in settings --> performance --> memory management)
- (CM Version only) works on CM10.1 <--new to V1.8.4
- Incorporated touchscreen death fix. Thank the user who reported it. <-- new to V1.8.5
- Used part of pershoot's kernel config to get data usage working in CM <--new to V1.8.6
- Added CM's version of the ROW (read over write) disk IO scheduler for GT-I9300<-- new to V1.8.7
- Added XDA's grzwolf's solution to the hsic wakeclock problem <--new to V1.8.8
- Added frandom kernel module <-- new to V1.9
Supercurio: voodoo sound
Pershoot: voodoo port, usb charging, flashable zip, OC template, current widget setup
XDA forum's CazeW: used your replace suggestions to patch up wm8994_voodoo.c and wm8994_voodoo.h so it will compile properly, and finding the missing link for 1.4GHz OC, and disabling frequency locks
Task650: providing a nice, clean deodexed rom for me to try this on
XDA forum's RaymanFx: OC instructions
Me: GPU OC
XDA forum's jaswinky for valuable hints and checking my work over.
Xoom ICS kernel: for getting an approximate idea of voltages
(If I missed any credits, please forgive me as this is my first attempt at any kind of development)
XDA forum's motley for voltage control
XDA forum's Unknownzd for mmc_cap_erase patch
XDA's grzwolf for the hsic wakelock fix11Very Good News
So it looks like CM10.2 is actually alive and in testing on my tablet. Big thank you to user epinter for helping me with the graphics issue. I will play with CM10.2 to see how it is. First 10 seconds impression: buttery smooth, wifi works, bluetooth works, sound works, A1 kernel with SELinux firing on all cylinders! Unfortunately it has the 2 bar UI... time to search for that post on how to make tabletui.
Please donate to epinter for CM10.2. He gets the credit for making it work. I just did some minor tweaking to the fstab and audio flinger.
Gotta go to bed. Just check out the screenshot zips to see it working. I have no time adjust the sizes for xda.
THE ZIP IS THE SCREENSHOTS, NOT THE ROM. I will post the rom later this week after testing.10Honeycomb Tablet Mode Partial Fix
Hey everyone,
I managed to figure out how to get the classic honeycomb tablet mode to work in CM10.1 (mostly). You know, the one where you get 1 status bar for the soft buttons and tray. Simply move the jars to /system/framework and the apk to /system/app. Do this with any root explorer or the terminal.
I tried to make a flashable zip, but I managed to screw the permissions in the process and accidentally pull the plug on my computer, corrupting its data partition. I did setup my Linux install to have a system (/) and data partition (/home) like android.
The only down side is that you can't customize the power widget but, on the upside, the UI seems noticeably less laggy than the stock CM10.1 UI with the 2 bars. Why??? Who knows. I think this benefit more than justifies the small annoyance of unchangeable toggles.
Here are the instructions I followed: http://xdaforums.com/showpost.php?p=28957307&postcount=1, http://xdaforums.com/showpost.php?p=36319776&postcount=974.
Last gotcha, it's for wifi only since that's what I have and I don't really want to wait for my computer to compile a whole other rom for the 3G version. (Have mercy on the Core2 mobile).8
Care to try the 3G version I just uploaded? I don't own the 3G version but I followed the same idea for compiling the 3G kernel.7Please do not advertise your roms in my kernel thread. This thread is mainly for bug reports and feature requests. Thank you for your understanding. (I did not advertise my A1 in pershoot's kernel thread saying "hey you want some of these features on stock rom, try my kernel". ) I will fix V2.0 to use a 3G ramdisk so 3G tablets will be able to use boot scripts later today.
