yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Q&A, Help & Troubleshooting] suwu10:
okay so heres the thing......i have a rooted g2 with s-off on ultimate droid rom. but just today the power buttom stopped working and there no way to turn off the screen or anything that uses it. and when i take out the battery to turn it ff you can't turn it back on until its plugged into a charger to where it then goes to clockwork recovery mode. im sending it into warranty and there sending me a new phone. is there any way they can find out if its rooted or would they send my phone back? any thoughts?
[G2 and Desire Z Q&A, Help & Troubleshooting] gurk04:
My originally G2 was unlocked and rooted with custom roms. One day the screen was sort of crapping out on me. I took the chance and sent it to HTC, and they just sent back new or refurbished model.... all I know for sure it was not my original G2.

Unless you think you can fix it yourself, you might as well send it back to HTC to see if they'll fix it, worst case scenario, they'll return it back to you...
[G2 and Desire Z Q&A, Help & Troubleshooting] lainvalenajr:
Okay... that's really hard. I forgot which rom let's you go straight to the bootloader. Anyways what method did you use for prem-root/ S-off?
[G2 and Desire Z Q&A, Help & Troubleshooting] Spastic909:
Rage gfree. If you have insurance with your carrier let it get stolen and get a new one
[G2 and Desire Z Q&A, Help & Troubleshooting] shortlived:
I would like to hear from anyone that has ever had a phone returned by htc because it was rooted...... Anyone? Water damage doesnt count i know they check for that.
[Streak 5 Q&A, Help & Troubleshooting] tamtang79:
How Dell Steak root?

my phone:

Android version 2.2

baseband version GAUSB1A131800-EU

KERNEL VERSION : 2.6.32.9-perf

OEM Version GAUSB1A131800

Build number : 12821

help me, thank you...
[Streak 5 Q&A, Help & Troubleshooting] oddbubble:
i used superoneclick to root mine

http://xdaforums.com/showthread.php?t=803682
[Streak 5 Q&A, Help & Troubleshooting] tamtang79:
ok, it worked for me, but this, I installed App2SD to open this program when it is not reported diver root, please guide me? thank you

sorry, my english is very bad
[Streak 5 Q&A, Help & Troubleshooting] oddbubble:
it should work are you sure you have root
[Vibrant Android Development] Deleted member 2371530:
Removed post
[Vibrant Android Development] xriderx66:
this works for MIUI, so why does it say..

Before going any further, please know this is for CM7 Gingberbread 2.3.3 ONLY.
[Vibrant Android Development] Deleted member 2371530:
The post i posted at first was regaruding that lol
[Vibrant Android Development] zacharias.maladroit:
thanks guys !

just changed that in my main thread from

[CM7] to [CM7/MIUI]

thanks !

@theexel:

please also updated
[Vibrant Android Development] Exel:
Done. Updated!
[Vibrant Android Development] s15274n:
Very nice. Test driving conservative, feels nice.
[Vibrant Android Development] iynfynity:
wow! CM7 with ext4, damn. ow I'm really getting interested to CM7.
[Vibrant Android Development] muleyman:
I had three reboots running this today. The first two occurred when I opened apps, (a game and a streaming radio app). The third time was when I took a phone call. After the third reboot I couldn't get a cell signal, even after a couple of reboots/trying to select a network manually. Ended up having to flash a different kernel to get the phone working again. Before these issues, however, it was running great, and seemed to perform better than my current kernel... not sure what got in to it. Will wipe and try it again!
[Vibrant Android Development] zacharias.maladroit:
it's actually fixes for ext4

and ext4 afaik is only used on /data
[Vibrant Android Development] zacharias.maladroit:
something to play around for you guys - the following should cut battery consumption approx. by half:
[Vibrant Android Development] hitman818:
Is this kernel going to get updated with the latest cm7 nightly?
[Vibrant Android Development] zacharias.maladroit:
I see no kernel updates at the repo

so it's already up-to-date
[Vibrant Android Development] hitman818:
So if I flash the kernel the fixes will still be applied with the latest nightly?
[Vibrant Android Development] zacharias.maladroit:
well,

found the changelog in the captivate CM7 thread

the 1st should be only system-related

the 2nd is already included in my kernel

so the short answer: yes, should work
[Vibrant Android Development] djordan79:
What's the difference between the two downloads you have posted here?
[Vibrant Android Development] apollo15rover:
OT Just 4 Fun!

:)
[Vibrant Android Development] dxtrlabs:
Getting random reboots opening pulse and websites anyone else?
[Vibrant Android Development] cervantesjc:
i am testing this right now, i'll let you know how this work on the vibrant, because it looks like this was made on the I9000 forums.
[Vibrant Android Development] charkey:
Just out of curiosity, what is the difference between this kernel and bilboa's CM7 kernel?
[Vibrant Android Development] hardaysknight:
Just flashed the April 25th kernel, and I'm not sure if i'm the only one with this problem but on boot the boot logo is upside down.
[Vibrant Android Development] adyscorpius:
Its normal. And explained by the OP.

Its cuz the kernel dusnt understand the orientation of he screen at boot.

Personally, I like it. Can tease around people that my phone can rotate in all directions... Lolz
[Vibrant Android Development] nickmcminn60:
Uh it can rotate all directions.....so you wouldnt be teasing!
[Vibrant Android Development] adyscorpius:
Ohh, well I can tease other android users that their phone dusnt rotate... Also, when I have headphones.connected, its better to.have the jack below... Lol
[Vibrant Android Development] ewidtfeldt:
Often when I unlock my screen the feedback vibrates and my keyboard is displayed. It happens pretty consistantly. I usually have the no lock screen tweak enabled as well but have never had an issue until the 4/25 kernel
[Vibrant Android Development] dasunsrule32:
No boot issues here. Did you wipe the dalvik cache? That is what would most likely cause that issue.

Miui, I doubt it. I barely have any time. Just got $60k of hardware to install and configure at my part time job.

Sent from my SGH-T959
[Vibrant Android Development] dasunsrule32:
Are you going to include the memory hack that is in the stock kernel?
[Vibrant Android Development] adyscorpius:
Edit: deleted
[Vibrant Android Development] zacharias.maladroit:
which one ?

link ?

thanks :)
[Vibrant Android Development] hitman818:
I just noticed the stock kernel has more ram than this voodoo kernel. The stock kernel was like 330 mb, but this is only 316 mb of ram.
[Vibrant Android Development] adyscorpius:
Delete again... Wrong post..
[Vibrant Android Development] nickmcminn60:
Flashed a different kernel and boots at normal speed.flashed Platypus again....same problem...this is by far my favorite so far. Dont know what it is.............11minute boot time (everytime). Its like its wipping dalvik at every reboot.......if my phone is connected to the computer when I try to boot it wont boot at all.lol. wonder if these ppl that say "flashed this kernel and nothing but boot-loop's" have a similar problem as me and they are nor letting it sit long enough. Guess ill Odin back Friday and start fresh.
[Vibrant Android Development] charkey:
There is a bug with the Messaging app's keyboard on the smiley face where you're supposed to be able to long-press the key and it should pop up with the different type of emoticons. What do you need from me to better help troubleshoot this issue?
[Vibrant Android Development] apollo15rover:
Weird, this happened to me with Core, but then 2Face and Whatitsname have been working great for me..
[Vibrant Android Development] zacharias.maladroit:
kernel stable (?)-release

Introducing "Alice" release

04/27/2011 (release name: "Alice"

already containing parts of Samsung's GB source (thanks teamhacksung !));

Semi-Testing/Stable (for new integrated code from Samsung) and other exciting new stuff )

kernel:

1st Mirror / Host

: [recommended]

"Alice" (thanks a lot to Roland !)

2nd Mirror

:

this thread (XDA) (attachment)

3rd Mirror

:

CM7_VIBRANT_platypus-kernel_20110427_01_alice.zip (5.22 MB)

md5sum:

88b5b538f0af4d69bd32229a06aea2d0 CM7_VIBRANT_platypus-kernel_20110427_01_alice.zip

Changelog:

additional optional features:

* bigger Dalvik VM heapsize (64 MB - like on Samsung's Gingerbread)

adb shell setprop dalvik.vm.heapsize 64m

to check if it's enabled:

adb shell getprop dalvik.vm.heapsize

* semi-fix for GSM/UTMS data signal outage (longer intervals):

adb shell setprop ro.ril.enable.dtm 1

to check if it's enabled:

adb shell getprop ro.ril.enable.dtm

Installation steps:

Auto-Rotation related

:

Generally no special steps should be required -

you could also leave out clearing of /cache & Dalvik Cache but this is to be sure - consequence is significantly slower 1st & 2nd (?) boots

following boots should be way faster than before (!)

Troubleshooting:

Please test specifically for the following sticking points:

enjoy ! :)

FYI:

for your convenience the kernel zip-files are also attached to this post

Thank you A LOT for your feedback on previous kernel releases

thanks !
[Vibrant Android Development] nickmcminn60:
$$$DELETED$$$
[Vibrant Android Development] zacharias.maladroit:
???

no - it's just a known bug - you have to restart VoltageControl several times to get States shown :p
[Vibrant Android Development] nickmcminn60:
still a no go.....im almost certain its not this kernel.
[Vibrant Android Development] nickmcminn60:
Anyone with missing "STATES"......go to system/etc/initi.d folder and delete 90.scaling file and re-launch the voltage app.
[Vibrant Android Development] zacharias.maladroit:
thanks for the reminder jkhrist !

I've looked through the config

but currently I'm out of ideas why those 14 MB might be missing, most probably due to using a not for size tailored kernel

not sure though

@theexel:

please update !

the latest release also includes Voodoo Sound v8

thanks !
[Vibrant Android Development] zacharias.maladroit:
I need feedback for that / these test kernels [should be stable but nevertheless needs testing] (test-release):

Changelog:

(04/27/2011) Changes for platypus-kernel_20110427_18_quorra_r1:

- based on top of bilboa1's kernel (Voodoo Sound v8, LED notification, etc.)

- fsync performance improvements for CFQ with small files

- CONFIG_PVR_ACTIVE_POWER_LATENCY_MS set to 10

- Nick Piggin's filesystem performance improvements

- toolchain switch to Codesourcery 2010.09

(04/27/2011) Changes for platypus-kernel_20110427_18_quorra_r2:

- mainly config changes [from bilboa1's default config to release "alice" config with changes]

- config_embedded re-activated

- config_aio disabled for now

- optimized for speed than for size

- still SLUB (SLQB not added yet)

- bumped the timer to 512

- tweaked cpufreq conservative governor for responsiveness; while screen is off: now also using conservative governor (different settings from while screen is on)

- config_ksm disabled for now

- CONFIG_UACCESS_WITH_MEMCPY disabled for now

- CONFIG_BINFMT_MISC disabled for enhanced security (new)

- re-enabled FM Radio drivers (needs support in userspace / the CM7 or MIUI system to get Radio working)

- added "Automatic ZipAlign by Wes Garner" v1.1 to the scripts

md5sum:

de1fdf05a624ecdfa0ba369b27c56bf1 CM7_VIBRANT_platypus-kernel_20110428_01_quorra-r2.zip

md5sum:

973c5c95cc51818abad53b2493664962 CM7_VIBRANT_platypus-kernel_20110428_01_quorra-r2_interactive.zip

[option] new interactive governor kernel <-- need feedback for that - interactive is enabled while the screen is on only, while screen is off: conservative
[Vibrant Android Development] crazy25000:
Just flashed the interactive kernel on CM7, after reboot, the screen is blank, but the keys light up. I just locked and unlocked then everything displayed normal. Not sure if this is normal :p
[Vibrant Android Development] adyscorpius:
This happened to me too... that when I plugged in the charger or did a hard reset, not otherwise...
[Vibrant Android Development] zacharias.maladroit:
Meanwhile something for you to play ("old" stable material):

I know of the possible call-drops with "alice"

so:

- please test if these kernels are stable

- call drops occur [if the new scripts help]

- functioning of auto-rotation, sensors, ...

The following kernels are "alice" kernels with improved scripts ("conservative" governor all the way and with an option of "interactive" governor while the screen is on)

Changes:

- improved cpufreq governor scripts (mainly only memory settings are changed while screen is on/off) [conservative governor all the way with different settings on/off]

- option of the new "interactive" governor

- [new script] Automatic ZipAlign by Wes Garner

CM7_VIBRANT_platypus-kernel_20110427_01_alice2_interactive.zip (5.22 MB)

md5sum:

245fcec75d9757c0f7882d284e5fba42 CM7_VIBRANT_platypus-kernel_20110427_01_alice2_interactive.zip

CM7_VIBRANT_platypus-kernel_20110427_01_alice2.zip (5.22 MB)

md5sum:

60c77ced682d6d3ad0e7b60258749603 CM7_VIBRANT_platypus-kernel_20110427_01_alice2.zip

These kernels are supposed to be stable - despite occasional (possible) call drops

if you get call drops please report !

- modem

- network type (GSM / WCDMA, UMTS)

- ...

thanks !

yes,

big differences

"quorra"-kernels use bilboa1's latest kernel as base

whereas "alice2" uses an older one with all modifications, improvements & fixes from me

the most notable probably is:

- alice: possible call drops [please test if those are fixed with governor change]; Google Goggles work

- quorra: Google Goggles FCs and blocks subsequent camera access (non-clean closing of the app and camera access); more stable kernel; Goggles probably will work with later quorra releases again

<-- please report any issues you encounter with "Alice" or "Quorra" kernels

thanks !
[Vibrant Android Development] adyscorpius:
Does this fix the mic not working when headphones connected and screen turns off???

And ya, is there some variable like Yamaha wm9884 or whatever number and set_mic_bias?

That thing is what changes I think when we have to mute/unmute to get the mic working on an incoming call...
[Vibrant Android Development] adyscorpius:
[ 208.806349] Universal : Card status 1

[ 208.806585] suspend: exit suspend, ret = 0 (2011-04-28 14:53:24.530694401 UTC)

[ 208.806722] s3cfb_late_resume is called

[ 208.808468] FIMD src sclk = 166750000

[ 208.867302] s3cfb_late_resume is complete

[ 427.515365] wm8994_set_mic_bias: system_rev=48, on=0

[ 433.227755] wm8994_set_mic_bias: system_rev=48, on=0

[ 454.183633] wm8994_set_mic_bias: system_rev=48, on=0

[ 461.194302] wm8994_set_mic_bias: system_rev=48, on=0

[ 516.168610] wm8994_set_mic_bias: system_rev=48, on=0

[ 521.049299] wm8994_set_mic_bias: system_rev=48, on=0

[ 579.131098] request_suspend_state: sleep (0->3) at 579076695035 (2011-04-28 14:59:34.855482272 UTC)

[ 579.133847] SMB380: Set Sleep has been called 1

Thats from /proc/last_kmsg
[Vibrant Android Development] zacharias.maladroit:
Changelog:

(04/29/2011) Changes for CM7_SGS_platypus-kernel_20110429_19_quorra-r3 [NOT compatible with MIUI (MIUI needs new drivers)]:

morfic stable optimizations flags (mfloat, neon, etc.)

∘ + switch to mfloat=hard

• CPUFREQ: Fix power suspend cpu frequency (re-add)

• upstream ARM cpufreq governor delay fixes (re-add)

• cpuidle (sleep, battery runtime) improvements

• jhash3 re-added

• add more cfq improvements (re-add)

• CFS scheduler load balancing & granularity improvements re-added

• BFQ re-added [option]; CFQ is default (unless you've set otherwise in VoltageControl, etc.)

• vmscan stalls fix re-added [less lags during heavy writing]

• ondemand governor: added sampling factor [more efficient & aggressive scaling]

• battery polling intervall to 30 seconds

• new (improved) interactive cpufreq governor from upstream

• new SavagedZen cpufreq governor from upstream + tweaks to it [minimum frequency at 400 MHz]

• lots of memory management improvements (+ stability fixes)

• SLQB (re-add)

• fadvise support; deactivate invalidated pages, reclaim invalidated pages

• simple I/O scheduler (re-add)

• (potential) better battery runtime & deeper sleep (re-add)

• writeback fixes (re-add)

• inactive file ratio (re-add) at 20

• re-activated heap randomization [security improvements; ASLR] [new - thanks to nikademus for the inspiration / "fugu mod style"]

• re-add fugu mod security improvements [in the kernel]

• back to 256 Hz High_Res_Timer [need feedback on responsiveness & lags]

∘ if stuff is getting too slow & laggy I might switch to 512 again

• back to USER_HZ 100 (default)

• fixed Google Goggles (thanks bilboa1 !)

1) Quorra r3 [NOT compatible with MIUI (MIUI needs new drivers)]

1st mirror:

CM7_VIBRANT_platypus-kernel_20110429_22_quorra-r3.zip (thanks to Roland for hosting !)

2nd mirror:

XDA - post (attachment)

3rd mirror:

CM7_VIBRANT_platypus-kernel_20110429_22_quorra-r3.zip (5.13 MB)

md5sum:

022d8c909fd91cec197767b9dd330955 CM7_VIBRANT_platypus-kernel_20110429_22_quorra-r3.zip

edit:

kernel package updated (kernel modules properly moved & updated init scripts)
[Vibrant Android Development] crazy25000:
Wifi doesn't work when I flash these kernels with the new CM7 update.
[Vibrant Android Development] nickmcminn60:
1)(Quote) "Quorra r3 [NOT compatible with MIUI (MIUI needs new drivers)]"

what drivers exactly are missing?
[Vibrant Android Development] zacharias.maladroit:
see:

the sensor update seemingly also brought a directory move as an update ...

I don't know exactly I read about some libsensors* file but not sure

thanks
[Vibrant Android Development] crazy25000:
Awesome, thank you. Wifi works.
[Vibrant Android Development] zacharias.maladroit:
kernel package updated (kernel modules properly moved & updated init scripts) :)
[Vibrant Android Development] zacharias.maladroit:
[experimental - old sensors]

1) Quorra r3 [compatible with MIUI]

CM7_VIBRANT_platypus-kernel_20110430_04_quorra-r3_MIUI.zip (5.14 MB)

md5sum:

867b441d634b37bd976d22de0c83e3dc CM7_VIBRANT_platypus-kernel_20110430_04_quorra-r3_MIUI.zip

Changelog:

(04/29/2011) Changes for CM7_SGS_platypus-kernel_20110429_19_quorra-r3 [NOT compatible with MIUI (MIUI needs new drivers)]:

morfic stable optimizations flags (mfloat, neon, etc.)

∘ + switch to mfloat=hard

• CPUFREQ: Fix power suspend cpu frequency (re-add)

• upstream ARM cpufreq governor delay fixes (re-add)

• cpuidle (sleep, battery runtime) improvements

• jhash3 re-added

• add more cfq improvements (re-add)

• CFS scheduler load balancing & granularity improvements re-added

• BFQ re-added [option]; CFQ is default (unless you've set otherwise in VoltageControl, etc.)

• vmscan stalls fix re-added [less lags during heavy writing]

• ondemand governor: added sampling factor [more efficient & aggressive scaling]

• battery polling intervall to 30 seconds

• new (improved) interactive cpufreq governor from upstream

• new SavagedZen cpufreq governor from upstream + tweaks to it [minimum frequency at 400 MHz]

• lots of memory management improvements (+ stability fixes)

• SLQB (re-add)

• fadvise support; deactivate invalidated pages, reclaim invalidated pages

• simple I/O scheduler (re-add)

• (potential) better battery runtime & deeper sleep (re-add)

• writeback fixes (re-add)

• inactive file ratio (re-add) at 20

• re-activated heap randomization [security improvements; ASLR] [new - thanks to nikademus for the inspiration / "fugu mod style"]

• re-add fugu mod security improvements [in the kernel]

• back to 256 Hz High_Res_Timer [need feedback on responsiveness & lags]

∘ if stuff is getting too slow & laggy I might switch to 512 again

• back to USER_HZ 100 (default)

• fixed Google Goggles (thanks bilboa1 !)
[Vibrant Android Development] adyscorpius:
Hey, thanks for the backward support... Appreciate your effort... :D
[Vibrant Android Development] crazy25000:
Thank you sir, much appreciated :D
[Vibrant Android Development] jonathanhuerta4:
Hey, I'm trying to make the ondemand governor stick on this kernel. The only way I am able to make this governor stick is to back up the "90screen_scaling" and then proceed to delete it. So i'm asking what edits to the lines should I change?. thnx in advance. :confused:
[Vibrant Android Development] jonathanhuerta4:
Well looks like all I needed to do was make a simple change and reboot. :o. Well now I need to clean up the changes I made.:)

BTW: for people who also wish to use a different governor, edit the "90screen_scaling" in "/etc/init.d/", and change AWAKE_GOVERNOR="conservative" (UNDER "# One governor to rule them all") to AWAKE_GOVERNOR="ondemand" or other available governors, and then adb push it back in, or save and exit if you are in root explorer, then proceed to reboot. Hope I helped
[Vibrant Android Development] nickmcminn60:
I deleted my 90scaling file and performance and battery have been dramaticly improved. According to CPU Spy its scaling thru all frequencies.
[Vibrant Android Development] jonathanhuerta4:
hmm thats actually ironic. Well I will delete it and run it for a day, as well as post my battery results.:)
[Vibrant Android Development] Echo113:
Is this for a mytouch 4g too?

Relayed from Tofer's CM7 final v2 MyTouch 4g now with BluMagic theme! Go Steelers!!
[Vibrant Android Development] jonathanhuerta4:
Before someone starts to flame and not respond to your question. No, this kernel "Platypus", was originally for the I9000 (Original Galaxy S) and is now available for the Vibrant. So with this in mind, this kernel is not for any other device, but Vibrant, I9000, and Captivate. It is not for the MyTouch 4g.
[Vibrant Android Development] zacharias.maladroit:
jonathanhuerta4, nickmcminn60:

please keep us updated in this matter

if the battery runtime really shall be improved I'll - of course - switch to ondemand as default governor :)

thanks !
[Vibrant Android Development] jonathanhuerta4:
No problem, glad to be of assistance.
[Vibrant Android Development] nickmcminn60:
i first started deleting 90scaling on the kang kernel. And it is very smootnh and battery is a lot better. the reaaso i started is because after installing cpu spy, I noticed that it would quit scaling properly. It would sometimes get stuck at 1300 for long periods for no reason despite what i ticked in the voltage app. scales perfect and efficiantly with the file removed. no wake lag or any thingeven while using the ''cube'' effect in the miui launcher and LW running. Ive found it a LOT less laggy all around.
[Vibrant Android Development] notverycreative:
Where exactly is this 90scaling file?

EDIT: found it.

Sent from my Vibrant on CM7
[Vibrant Android Development] nickmcminn60:
Here is a Extended Voltage App that I found in the Captivate thread. It allows you to monitor how long the cpu was at each frequency (under states)(like CPU Spy) and quite a few extra options that are not available in xans app. If states are missing just close and reload several times and it will show up ;) Hope you guys enjoy!

Now I have one less app running in the background.