yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] derausgewanderte:
thanks, I just tried that. no joy though after a few sods. as soon as I go back to v0.35 everything is perfect.

just cleared cache and dalvik, now seemes to be stable again. looks like this is running close to the limit based on how picky it is.
[TouchPad Development] unsivil_audio:
I would try a clean install of v4 then upgrade to v5. no Sod's here after a couple at the initial install.

Sent from my cm_tenderloin
[TouchPad Development] derausgewanderte:
so far from what I've seen on my system and from other posts it's rather unpredictable. I started with installing this over CM9. I had sods then it was stable for a day and then it started sods again. I then started from scratch, fresh CM9, v0.5 over it and it started fine and then sods again. Just now I only cleared cache and Dalvik and it seems to be fine again.

I believe everybody will see variations of this, depending on rom installation history.

I agree with you that it's probably best practice, especially with this to start from scratch.
[TouchPad Development] unsivil_audio:
Sorry I was unclear. I started with cm9, installed v4 rom and kernel over that. Then installed v5 kernel. Only wiping /cache and dalvik in between installs.

I'm suggesting however that you format /system /cache and dalvik, then reinstall v4 rom and kernel, then upgrade to v5 kernel. It's been stable as hell for me.

Sent from my cm_tenderloin
[TouchPad Development] DanielNTX:
The kernel locked up for me on the Touchstone as well. I had to remove it.
[TouchPad Development] show-p1984:
I am working on a new version ;) Stay put. ;)
[TouchPad Development] derausgewanderte:
cool, thank you for the update
[TouchPad Development] lafester:
sweet!

thank you :)
[TouchPad Development] JohnKoffee:
I get a black screen everytime I try to boot on Bricked. I thought it was because of the ROM I use ( CherryKang).

By the way I even get a black screen when trying to boot on Bricked ROM. Seems I ain't got no luck with Bricked. :( Will try another day. :D
[TouchPad Development] scombellack:
0.5 is working OK for me after a hesitant start

I had one SOD after a couple of hours, rebooted and it has been stable since that. I cleared the cache and Dalvik after first installation.

I upgraded from kernel 0.4.

0.35 was stable for me. 0.4 SODth'd all the time so I went back to WebOS until 0.5 came out. I'm back on ICS now. I do get some odd f/closes, but I'm overclocked to 1.7 so I guess that's to be expected.

So overall, for me, 0.4 is working great.

Really good work, show.
[TouchPad Development] unsivil_audio:
Well after several days of problem free experience, sod's and reboots started happening again. After A wipe of both caches in clockworkmod, it was all good again. I have a feeling this may have to do wih something corrupting the dalvik cache.
[TouchPad Development] ChronoReverse:
Not sure if it's real or just a placebo effect, but I've been avoiding directly turning off my touchpad. That is, I either let it time out or I press the power button then press it again to bring up the lockscreen in order to let it time out faster.

So far no SoDs even on my touchstone.
[TouchPad Development] mejorguille:
Try this: https://market.android.com/details?id=com.katecca.screenofflock

It's a one toggle for turning the screen off.. You can even put it on the notification bar.
[TouchPad Development] enik_fox:
So if I flash this kernel and for whatever reason it doesn't work out, and I re-flash my rom would that remove these kernel files and set things back to normal?
[TouchPad Development] patoberli:
My TP also has instant SOD when on the charger (a normal USB, low power one) and it goes into standby. It's always happening.

I hope the next version will fix this.
[TouchPad Development] xAndrew225x:
I'm having trouble getting my touchpad to mount as mass storage on my pc. It's telling me the drivers were unsuccessfully installed. Any help would be greatly appreciated.

Edit: Sorry if that sounded too vague, I don't have any problem mounting it using webOS or xron. Only with this rom. lol
[TouchPad Development] show-p1984:
This is a kernel.

Afaik there is no mass storage on ics atm.
[TouchPad Development] thedan55:
there is no mass storage, we use MTP on the touchpad.

settings - storage - 3 little dots (menu in the top right corner) usb computer connection - enable MTP et voila!
[TouchPad Development] xAndrew225x:
My bad, I realized that after posting. Meant to post in the Bricked-Rom thread. But thanks for the reply!

Thanks! Just what I was looking for :D
[TouchPad Development] thedan55:
to uninstall the bricked kernel where do i use the commands?

ive just installed CM9 Nightly version and i did a full wipe of system, data and dalvic.

but the kernel is still present in mboot and boots into it. do i use the commands on my pc with usb or in terminal?

edit: also is this kernel compatible to cm nightlys?
[TouchPad Development] derausgewanderte:
I see from the other thread at Rootzwiki that you figured this out already.
[TouchPad Development] gary93:
Hi, thanks for the Kernel, it was nice; however I'm always having trouble when in charge or after screen off after a while, I can't turn it back on have to push the power button and the bottom button (I think it called deep sleep.. right?, sorry I'm new here). So I'm trying to go back to stock CM9 A0.6, but I don't quit understand how to remove the kernel, specially those code part... is there any easier way to do that?

Thank you again and hope there is another new one coming soon and fix those problems.
[TouchPad Development] Ratix0:
Just tried this Kernel and I've been having sleep of death problem, the touchpad refuse to wake up after going to sleep and I have to force restart it.

Also another problem is very weird, I don't suppose this kernel should be affecting it but it apparently does. Immediately after flashing this kernel, wifi in CM9 default kernel broke. Im still able to do everything fine using CM9 with Bricked Kernel but when i go back to default CM9 (because this kernel has SOD), I'm unable to connect to wifi at all.

Any help?

EDIT: To elaborate on the wifi problem, it simply just wouldn't turn on. Trying to turn it on through the settings or through notification shortcut both made the toggle immediately go to off when I slide it to on. Also it will display "Turning on wifi..." in the settings menu and freeze there.

EDIT2: Upon reading more...

"If you want to boot into the cm9 kernel for just one time, just choose it. Though wifi will be broken because the modules differ. (pushing the cm9 modules will fix that but break Bricked wifi , how that is done is written a few lines down)"

So I'm guessing its normal to have that problem right? The only way to fix this is to push CM9 stock kernel through instead am I right?
[TouchPad Development] patoberli:
Correct.

10char
[TouchPad Development] The Jack of Clubs:
Does this work with cm9 alpha 1 that just came out?
[TouchPad Development] derausgewanderte:
alpha1 is a new kernel. bricked is a kernel. it's either one or the other, can't have both. (until Show incorporates current changes into the kernel). If one works, the other will not have wifi and vice versa.

wait for an update. dalingrin just released alpha2
[TouchPad Development] lafester:
doesn't seem to work for me! too bad cause alpha1 still has no sound for me after sleeping (been a problem since cm7 alpha 3).
[TouchPad Development] derausgewanderte:
I am not sure what you are trying to accomplish. you install alpha1 because it has a new kernel with hw video enabled. then you install a different kernel over it and expect it to work? you will lose everything you just accomplished with alpha1.

am I missing something?
[TouchPad Development] lafester:
you are missing the fact that this kernel will not boot with alpha1.

obviously hw video will not work that is not the point.
[TouchPad Development] show-p1984:
My closed beta does ;)

And it will soon(tm) get released with sod fixes for the PM core.
[TouchPad Development] lafester:
Nice! Ty and pm me beta info lol.
[TouchPad Development] [TSON]:
Yesssss, my body is ready for 1.75 GHz again. I'm spoiled and can't browse at stock speeds, it's annoying ;___;
[TouchPad Development] Divine_Madcat:
stock alpha 2 kernel oc's to 1.7....
[TouchPad Development] [TSON]:
Wait what... It does?
[TouchPad Development] Divine_Madcat:
Most certainly does. The first thing i did upon getting A2 was to fire up setCPU and crank it to 1.7. Yes, bricked kernel has more tweaks (and higher clocks above 1.7), but stock can be set to 1.7.
[TouchPad Development] itsDefying:
Not for me. it's not even letting me adjust it.
[TouchPad Development] ChronoReverse:
Don't use the built in controls (they don't work yet).

Try SetCPU or System Tuner.
[TouchPad Development] itsDefying:
I was.

Sent from my HP Touchpad with CM9!
[TouchPad Development] Divine_Madcat:
So Show... any teasing you can hit us with? We are dying over here! :D
[TouchPad Development] The Jack of Clubs:
yeah we need some 1.9ghz.
[TouchPad Development] show-p1984:
SOD seems to be finally fixed, thanks to caf and leedroid who found the commits that will get rid of it. ;)

I am testing some other stuff before I will release it to the public

I am very surprised how much oc the chip can handle with some small copper cooling plates applied to it, while it is not so oc friendly in my sensation.
[TouchPad Development] sahhar1993:
woooooooooow

i hope to 2.1 ghz in touchpad

thank you men
[TouchPad Development] show-p1984:
Take a look:

https://twitter.com/#!/showp1984/status/174009119307612160

#Worldrecord? :D
[TouchPad Development] unsivil_audio:
Amazing.

Sent from my cm_tenderloin
[TouchPad Development] derausgewanderte:
can't wait. hope this also means better battery life for lower freqs.

zum Wohl
[TouchPad Development] The Jack of Clubs:
Babies will be had...
[TouchPad Development] show-p1984:
woot? :D

10chars
[TouchPad Development] sahhar1993:
What the freauence of gpu in next kernal? :)
[TouchPad Development] show-p1984:
320mhz for 3D and 266,67Mhz for 2D (so both are OC'd)
[TouchPad Development] nikos5800:
If overclocked CPU examble at 2.0ghz the gpu will underclocked at 266mhz?(for 3d)

And if yes can you fixed?

And finally you will released tomorrow?
[TouchPad Development] show-p1984:
GPU will stay @320 ofc.

I don't know if I will release it tomorrow, depends on if I run into any problems. I am also implementing some new power saving features for the CPU/GPU, as well as testing how much UV the touchpad can handle. I am still in conflict wether this should go into the next or this version.

If it goes into the next version I might release it tomorrow with SoD fixed and higher OC/L2 Boost/GPU OC.
[TouchPad Development] nikos5800:
Thanks for the answer, I think sod fix,and higher Oc/l2 boost/gpu OC its enough for this version :rolleyes:
[TouchPad Development] Traxex_:
Any idea why my wifi is not working when booting into bricked kernel but working fine with the stock CM9 kernel?

Already wiped cache/factory reset and flashed the kernel several times.
[TouchPad Development] Divine_Madcat:
Bricked kernel uses a different Wi-Fi module (that when you flash A2, is overwritten). Thus, the stock CM9 kernel can find the wifi module, but the bricked kernel cannot,... thus, no wifi.

As it is, you shouldn't be using this old version of bricked with A2 anyway.. wait for Show's next release.
[TouchPad Development] Traxex_:
Wifi is now working somehow but Youtube shows an error. No problems with stock kernel.

I better wait for the next release then.
[TouchPad Development] show-p1984:
v0.6 @ OP

compatible with a2
[TouchPad Development] unsivil_audio:
Stuck at loading screen here.
[TouchPad Development] show-p1984:
Try redownload and reflash.

On CM9 A2 it works perfectly here.
[TouchPad Development] unsivil_audio:
Ha...that was it. Hmm, I guess there is a first time for everything. Redownloaded and flashed, and its good. Awesome work my friend.
[TouchPad Development] derausgewanderte:
having some issues too that are reproducible. every other time I reboot it freezes at the CM loading screen that comes right after I see the bricked booting message and before the bootanimation. a hard reset and boot works again until next time when I have to repeat the procedure.
[TouchPad Development] show-p1984:
What are you doing exactly? (step by step, as in 1. bla, 2. blubb, 3. etc ^^)

Also try to manually wipe the caches and/or redownload and reflash the kernel.
[TouchPad Development] derausgewanderte:
2am here, no excuse I know, but I will try your suggestions tomorrow and report back.
[TouchPad Development] show-p1984:
7:22am here, and I was not sleeping yet. :D
[TouchPad Development] derausgewanderte:
I always clear cache and dalvik after a kernel upgrade. I just downloaded it again. cleared everything and will install again now and observe, try a few reboots. (I just realized it's not 2am just yet ;) )

rebooted a few times and it's fine now. works great. no freezing anymore. seemed to have been a hiccup.

edit: ok there it is again.

got a sod. then I had to hard reset. after choosing bricked in moboot it shows the booting message and then stalls at the CM loading screen. Have to hard reset again. After that it boots fine.

sods left and right. Once it freezes I have to hard reset, then it will not boot past the CM loading screen. After hard resetting again it will boot into CM.

it doesn't like my TP...

will try a completely fresh rom tomorrow

back to latest nightly everything is fine. tomorrow is another day. One more post and it's 1000. I hope that is a lucky post ;)
[TouchPad Development] tripacer99:
Also having a freeze up at the "cyanogenmod loading" screen after a reboot. A hard reset seems to fix it, but I have to do this every time I reboot :/

Wiped caches, tried a fresh reinstall, no go. The post above mine is an exact replica of my problem.
[TouchPad Development] show-p1984:
I am running the kernel on CM9 a2, it works perfectly. You might want to stick with that for now, and report any problems with that version.
[TouchPad Development] sahhar1993:
My device crashed after setting speed to max 2157 mhz

But if i use 2022mhz and the other one my device crash after 4-5 mn
[TouchPad Development] show-p1984:
Then your device may not be comfortable with those speeds.
[TouchPad Development] derausgewanderte:
couldn't wait....

I am experiencing the same problem on pure alpha2

edit: looks like I am not alone looking at posts in Rootzwiki...

I may play with voltages as suggested over there

edit2: virgin alpha2 rom, nothing else, installed bricked. Getting sods again. I guess my TP is not made for this.
[TouchPad Development] sahhar1993:
But i dont cleare enything here just put kernal in /boot and change permissions

Any thing wrong
[TouchPad Development] derausgewanderte:
good for you. I've tried a few things, but it doesn't work at the moment. maybe I have to overclock the bejesus out of it to get it to work, lol
[TouchPad Development] sahhar1993:
The kernal is very well and i dont care about new frequence at this time because there is no reason to use it at this time maybe in future

Maybe this frquencys will work in next builds
[TouchPad Development] sahhar1993:
My touchpad very stable in 1.914 amazing :D

after some reboots 2.103 and 2.022 working very well and playing MC3
[TouchPad Development] itsDefying:
Ran into problems the first time I flashed it, but the second time it worked fine. :)
[TouchPad Development] The Jack of Clubs:
mines running fantastic with full overclock. getting high quadrant scores. graphics still suck but thats because of the nasty adreno graphics chip.
[TouchPad Development] derausgewanderte:
interestingly I am having the same problems with sods that I had after flashing over latest nightly rom and then the same rom with original alpha2.

I wiped everything. Installed dalingrin's alpha2 and gapps. then I installed bricked 0.6. it seemed to work fine for a while (~1hr with a few intentional reboots and sleeps to check) and then sods started again. After hard reset it would hang at CM loading screen right after bricked booting message comes and before boot animation. It has been doing this everytime it went to sleep or when I made it go sleep. and everytime this happened it needed a second hard reset because it wouldn't go through the next boot.

seeing that others have no problems I tend to believe that not all TPs were born equal...

that's ok. can't always be at the bleeding edge ;)

thanks for the work Show!
[TouchPad Development] show-p1984:
You might want to try this:

Version: 0.6

Buildnumber: #34 (midnight build ^^)

Click me
[TouchPad Development] [TSON]:
That zip still has the problem. Seems like literally every other boot it won't startup.

EDIT: Weird... Seems like after the second boot it stopped doing it altogether... Works for me! (My TP can't handle 2.0 GHz though so I'm really bummed)
[TouchPad Development] derausgewanderte:
so far so good. Have been running it since you posted, no sods or freezes. very different from previous install, which started with problems right away.

Crossing fingers, or better Daumen Druecken.
[TouchPad Development] show-p1984:
You might want to laugh at me, but it's a one liner I forgot to remove :o
[TouchPad Development] derausgewanderte:
no problems still. looks great!

I wouldn't dare laughing at you :). Interesting though that it affects only some and not all?

It would have been cruel if you came back and told me that you actually didn't change anything - LOL

edit: so after a while of it being stable with sleep scenarios I rebooted and it got stuck at CM loading screen. and there it is again - sod. further testing, will see whether it settles after some time...only one so far. definitely much more stable than before. I have a hard time getting it to sod or freeze ;)

edit1: still going great here after several hours
[TouchPad Development] lafester:
Running great so far:) Thank you!
[TouchPad Development] [TSON]:
Left it alone for an hour and got SOD w/ reboot problem... But yeah definitely an improvement over the first one!
[TouchPad Development] mkosem:
Had reboot lockups the first dew times, but it seems better now (strangely). Also had an SOD after the first boot but none since. Agreed on it being an improvement. I'm going to give it a try as my daily driver. Nice work!

--Matt
[TouchPad Development] nomadman:
hey show-p,

since there wont be any regularly released alphas and dalingrin suggested to start using nightlies. can you build your kernel for nightlies? I must admit that i've had a few lockups right before boot animation starts.
[TouchPad Development] [TSON]:
Yeah there's definitely a problem with something here. I tried playing MC3 at 2.0 GHz, locked up. Tried at 2.1. Locked up before I could get ingame. Tried 1.7. Locked up. Tried default. Locked up. It can handle all of the OCs until I start playing games that utilize 3D, then it freezes up & hot reboots.

I haven't gotten any more SOD's though!

I'll try to get a logcat real quick of the crash.

EDIT: Moboot says "lastboot: panic" btw.
[TouchPad Development] ChronoReverse:
Could it be that the overclock on the GPU is pushing too high? That might not show up on show's Touchpads and it's not adjustable on our end either.

Incidentally, just installed this and got a SoD the first time I put it to sleep. Rebooting a few times now to see if that makes it go away.
[TouchPad Development] [TSON]:
Logcat of the freeze @ 2022 MHz playing MC3. Froze in the menu.

Posted w/ my touch pad on 2022 MHz just fine. Antutu made it freeze tho :(
[TouchPad Development] nomadman:
since Settings can set the frequency, does this still apply? (only applies to nightlies)

@TSON, I doubt show-p can do anything about that since not all touchpads are created equal. mine locks on 3d games at anything over 1836, but runs fine on 2d at 1914.
[TouchPad Development] [TSON]:
I can't play 3d games on stock OC which is deemed stable on Bricked while I can on 1728 MHz+ on stock/old Bricked versions... a couple people on rootz are reporting this too. I used that high OC because it locks up faster for logcat purposes.
[TouchPad Development] show-p1984:
Since 0.4 I am using the pyramid kgsl drivers I have optimized and tuned for over half a year now.

These seem to need some adjusting to our touchpad.

That's all what it is about. I guess I will have to revert to the stock drivers until this is cleared out, though it will probably eat more power and give us less performance =/
[TouchPad Development] nomadman:
i'm fine with that. i'm sure it'll all get sorted out when a solid beta is released.
[TouchPad Development] derausgewanderte:
still running great here with your interim build you posted. I am not playing games on the TP.
[TouchPad Development] [TSON]:
aww /:

well, gives us something to look forward to. thanks for all of the work you're doing!
[TouchPad Development] silverstream:
Indeed the interim 0.6 seems to fix the sod! Thanks
[TouchPad Development] nomadman:
i think i'll keep this kernel on the back burner until it hits the nightlies. there's forward movement on nightlies and i'll like to help support and troubleshoot it.

thanks for all the work you put into it show-p. i hope you get your quad core when it's released! :P
[TouchPad Development] Divine_Madcat:
Well, i loved the performance, but sadly, both touchpads i have here would SOD as soon as they slept; back to stock kernel for now, and hope that a fix is found (i am REALLY going to miss the GPU overclock...
[TouchPad Development] [TSON]:
Use the one on last page.
[TouchPad Development] Divine_Madcat:
Already did. I am trying it again, but i am not crossing fingers..
[TouchPad Development] ChronoReverse:
Looks like my Touchpad will crash in 3D games after some time even at stock. It was noticeably faster though so that's really too bad =(
[TouchPad Development] sahhar1993:
games working very well at 1914 mhz and less

gpu much better than the stock kernal

i hope to see gpu at 400 mhz :D:D
[TouchPad Development] ChronoReverse:
For me it depended on the 3D game. Antutu, GLbenchmark, Taiji all worked fine. Jelly Defense didn't crash either. But Dungeon Defenders consistently crashed after 5 minutes.
[TouchPad Development] sahhar1993:
@ 1.5 Ghz
[TouchPad Development] show-p1984:
v0.65 Test

Click me

I made a few adjustments to the kgsl resume/suspend.

It will now check if the earlysuspend was successful. If not the device will be put into lowest powerstate instead of assuming everything has worked. If a device could not be woken up the device will now be reset and jumpstarted to the highest power level. This adds robustness to the existing code. Testing it for further SODs is crucial.

I have also identified and fixed a 2minute bootup pause @ the cyanogenmod logo (some ppl had assumed that it froze, which is incorrect but understandable).

Furthermore this fixes an issue which caused CPUs to be stuck @ a clock.

Gogo. Test it! :P
[TouchPad Development] silverstream:
Thanks ! Trying it now!

---------- Post added at 01:54 PM ---------- Previous post was at 01:31 PM ----------

Initial feedback:

1st boot - No problem, but once screen is off, it goes into a reboot.

2nd boot - Stuck at CM logo. Waited 2min, no go. Reboot. Status shows lastboot="crash"

3rd boot - Clear both caches, and boot up again. But it auto reboot after screen is off.

4th boot - Reboot after screen is off. "lastboot =crash"

5th boot - SoD :(
[TouchPad Development] [TSON]:
Yeah, seems like the 2 minute thing just lasts forever now. Haven't gotten any SoD's yet...
[TouchPad Development] silverstream:
After removing Bricked-Kernel, I'm getting constant reboot. Not sure if related.
[TouchPad Development] happyta5:
update . 65 kernel on cm9. Few crashes and reboot.reset all voltage setting and 2.05ghz max now. It seems stable now. X my fingers......

HP-ics
[TouchPad Development] sahhar1993:
what is the voltage that you use please :confused:

at 1.512 and more
[TouchPad Development] Juan685:
Ive a question, can I flash this on MIUI 4.0?
[TouchPad Development] show-p1984:
I have no idea what miui 4 has running in the background. (and I am too lazy to look it up :P)

Try it. Then report back ;)
[TouchPad Development] sahhar1993:
Miui using the same kernal in classic N