yashsingh1/xdaforums huggingface dataset:
[XPERIA X8 Original Android Development] ->Sid:
These is what I observed while testing oxydo jb,

Initially when I tried the kernel for first time i flashed the kernel went to cwm then backup-restore and my sd card was intact I had backup files, there I tried to restore but got md5 mismatch, so I rebooted to twrp I took time to start only logo was showing up( I guess it was formating my sdcard and had abt 4 gb of data so was taking time) I removed battery and booted again there was nothing on sdcard only a folder named twrp..

I tried to create the bug again, so what I did was got some files on sdcard and deleted that folder named twrp and booted to twrp recovery, these time it didn't took time to start( might be because the data on sd card was less) and got my sdcard formatted, folder named twrp was there again..

I again tried same thing deleted the folder twrp, and put some file and same result..

Hope these could help, and if someone can try what I did and report wether the Same thing happens or not..

Hope we will get solution to it soon..

Did I helped u..

yes..!!

then go on hitting the screen and hit TANX buddy..;)
[XPERIA X8 Original Android Development] :
hey sgt. meow i've comiled cm10.1 rom from source and it's not booting up and i think it's releated to the kernel ,so maybe you can help me with that.
[XPERIA X8 Original Android Development] Daveee10:
Yes, the cm10.1 not booting if not change the required things.. (sd mountpoint, bootclasspath)

What sourcesd using??

Stelois97 and me (OldXperiaTeam) working on it... It works, boots, but the sdcard not recognized... The camera and some other things works, but some not like wifi (TI firmware and supplicant not supported), bluetooth powered on but not working (only the broadcomm BT working now with CM10.1)... So now you only try to build and try to run, but if you don't a ppl who understand the C++ and Java codes, you can't making CM10.1 what usable... Sorry but our kernel is too old and lot of things depends on kernel... Some older device like galaxy ace, mini, zte blade, skate, lg p500 have usable CM10.1 but that's device has 2.6.35 kernel... Now we need a new kernel or need backport lot off things like fs
[XPERIA X8 Original Android Development] :
can you tell me how to make it boot?and then i can go on and try to make things right
[XPERIA X8 Original Android Development] Daveee10:
You need to use correct bootclasspath... That's in the ramdisk....
[XPERIA X8 Original Android Development] :
yeah i get that but how i'm going to do that?and what is the correct bootclasspath?

if i can get it to boot maybe i can help with the other things , i'm good in C++ and Java codes
[XPERIA X8 Original Android Development] Daveee10:
This is the correct:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar

But don't forget, how I'm not your online support so, if you can't make anything pls don't send PM, And don't spam topics... Make a topic for that, but I think the help what you can get for this device is very poor because not too many devs for semc msm7x27... We working on it, so you need to wait when we release the alpha 1, or you can make anything...
[XPERIA X8 Original Android Development] :
it's ok i know you are not my online support , thank you for you help so far and i'm not going to send you any more PM

thank you.
[XPERIA X8 Original Android Development] CtrlAltDelIrl:
Some like CWM because it works and is well presented. TWRP is a mess.

Your statement would be better amended to:

I don't know why people would use my kernel when nAa's works perfectly.
[XPERIA X8 Original Android Development] laufersteppenwolf:
because it's much faster ;)
[XPERIA X8 Original Android Development] sgt. meow:
@CtrlAltDelIrl

What's with the hate man? I thought it was all sorted out. :(

@laufersteppenwolf

Thanks bruv.

@yair25

How'd you manage to compile CM10.1? I mean what sources did you use?

@Sid

Thanks for the report. I remember pulling out the battery when TWRP wasn't loading up. I think that causes the problem.
[XPERIA X8 Original Android Development] Daveee10:
I think he use source from OldXperiaTeam or a little bit newer source from androidarmv6. But we don't released the latest code. Something fixed after commited changes...

Trolled from my X8 using xda premium
[XPERIA X8 Original Android Development] sgt. meow:
I saw that nAa managed to get 2.6.32 booting. Does that mean, if it's working the way it should be, features like WiFi, Bluetooth etc will work on CM10.1? Anyways I used SLQB in the last build (haven't uploaded it yet), and not a single hang-up so far. Thanks for the suggestion, mate.
[XPERIA X8 Original Android Development] mayurcools:
nice :thumbup i can feel difference while using deadline scheduler, less lag :)

but there is problem with recovery, here is what i did:

press and hold power button and then click on reboot into recovery

after oxydo logo i press back button once.

it booted into recovery

after i click on reboot system now.

it rebooted into recovery. again i clicked reboot system now but it was always booting in recovery.

i had to remove and reinsert battery to boot into system.
[XPERIA X8 Original Android Development] sgt. meow:
That's weird. I just used CWM recovery to boot back into system (after a failed backup) by selecting "reboot to system". I'm on v8 but the recovery binary's the same. I have never used reboot to recovery from power menu (tried it only in ADB).
[XPERIA X8 Original Android Development] Daveee10:
No... The wl1271 things using wpa supplicant 6. But thats not supported by android 4.2.... It supports the supplicant 8, but the wl1271 not working with that... Bluetooth is not working now because on 4.2 support only the BCM bt now... The wifi maybe working with wext, but not tested yet... On gingerbread it works if I'm not wrong...

Trolled from my X8 using xda premium
[XPERIA X8 Original Android Development] sgt. meow:
Good luck anyways.
[XPERIA X8 Original Android Development] mayurcools:
ya, it happened with me second time,

reboot to recovery in power menu and then while at kernel logo press back button and after in cwm try to rboot into system

---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------

we already have sources for 2.6.35 kernel mos MSM7227 so why to backport, change kernel version to 2.6.35.

cant it happen???:confused:
[XPERIA X8 Original Android Development] sgt. meow:
@mayurcools

Can you try producing the same bug without using "Reboot to recovery" from power menu? It didn't happen for me.

And even if the source for 2.6.35 kernel for MSM7227 exists (HTC Aria has it), porting necessary drivers will take a long time. After that it's a matter of debugging and getting it to boot. Then some more debugging. Then an alpha release. Pretty tough.
[XPERIA X8 Original Android Development] mayurcools:
yeah got it again:

i am using latest minicm10 nightlies and oxydo jb 07 kernel.

here is what i did:

clicked on reboot into recovery from power menu.

on oxydo jb logo pressed back button couple of times.

then i got boot into recovery

after that clicked into reboot system now.

it boots but into CWM again and again.

i am using W8

---------- Post added at 08:30 PM ---------- Previous post was at 08:21 PM ----------

and ya i know building new kernel wil take a lot of time but i think it will be worth to do them.

as newer linux kernel solves bugs from previous versions and adds extra functionality also our 2.6.29.6 has various modules backported from it.

so maybe we can also solve screen death bug.
[XPERIA X8 Original Android Development] sgt. meow:
It happens to me too. I'll have to use a different version of CWM for the next release. Thanks for bug reporting.

Porting kernels takes months. nAa has already started on 2.6.32. Let's hope it succeeds.
[XPERIA X8 Original Android Development] mayurcools:
please remove TWRP. i am moving to another kernel now.

i got my sd card formatted and it is second time now.

try this:

reboot into cwm from power menu.

at oxydo jb screen touch screen repeatedly.

it boots into cwm and after that it boots into TWRP and puff TWRP disappears and sd card is formatted.

instead of booting into cwm from power menu, press back button 2 3 times and then touch screen same thing happens and sd card is formatted.

i think booting into twrp while cwm is booted is causing sd card format.
[XPERIA X8 Original Android Development] laufersteppenwolf:
if cwm can't boot into system after using the 'reboot into recovery' option, clear your cache and it should boot as usual ;)

at least it did for me :D

---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------

btw, it's only if i use the 'reboot into recovery' option.... if i do it manually, it boots like it should...
[XPERIA X8 Original Android Development] sgt. meow:
@feherneoh

Good to see you back. That could be a cause. Thanks for that.

@laufie (mind if i call you that)

I know. Thanks anyway.
[XPERIA X8 Original Android Development] sgt. meow:
Yes I was thinking of editing the bootrec to include this after mayurcools's last post. Will try to do it tomorrow.
[XPERIA X8 Original Android Development] mayurcools:
@sgt.meow

thanks i think you got cause now...

waiting for next version. and i can see from ur profile that u r using oxydo jb 08 while there is link for 07.

can u share the link with changelog???
[XPERIA X8 Original Android Development] laufersteppenwolf:
if it helps you to fix it, i'm fine with it :p

i can imagine that my name is kind of difficult for non-germans ;) :D
[XPERIA X8 Original Android Development] ->Sid:
@sgt.meow can u also make a only cwm containing kernel for next version or current untill the bug is removed..

Just a request..
[XPERIA X8 Original Android Development] hajiborojobo:
from fresh rooted 2.1

incompatibility room or some flash problem?

cypress edition

edited,after getlop i instal room with nAa and then change kernel,ty
[XPERIA X8 Original Android Development] TAJ_Rocks:
@haji see the first two posts about get assert failed solution of sgt.meow:banghead:

Sent From Walk-MAN By Using Thumbs To Yours Retina
[XPERIA X8 Original Android Development] CtrlAltDelIrl:
I can't believe you leave this kernel here on a pubic forum when it is so destructive.

Wiping people's data is not a trivial matter as you seem to think Sgt. Meow.

You should have a small team of dedicated testers who know what they are doing - not unleashing this on the unsuspecting public.

You also should NEVER release a kernel that hasn't reached alpha stage yet.

Your "I really don't care" attitude to people's data being wiped is scandalous!

You should know well enough now that this forum is full of kids who don't read the effin manual.

And TWRP is a joke. It will never be as stable and reliable as CWM so why reinvent the wheel if it won't turn?
[XPERIA X8 Original Android Development] Daveee10:
What??? That's not sgt.meow problem how someone can't reading or don't know what he/she doing... this is dev section and this is wip (work in progress) kernel. So your mind is unusable... If anyone using the forum need to read and know the rules. Sry

Trolled from my X8 using xda premium
[XPERIA X8 Original Android Development] laufersteppenwolf:
sorry, but what is your problem? do you think that this kernel hasn't reached alpha-stage, just because there is a known bug in twrp that COULD format the sdcard? this kernel is completely usable and it's got a much better performance than nAa's. i have tryed everything i could imagine, but i never got the format-bug reproduced. and if you don't want to take the risk, you don't have to use twrp....

and to your opinion about sgt.'s alleged 'i really don't care'-attitude, it has been said often enough that this could happen.....and if people are able to unlock their bootloaders and flash kernels, it can be assumed that they can read the instructions and of course the requirements. if they are after all willing to take the risk, it's their choice and, in the worst case, problem.
[XPERIA X8 Original Android Development] sgt. meow:
@CtrlAltDelIrl

1. It's a WIP as stated in the title. There are certain requirements that need to be met including a backup of the sdcard.

2. I know getting the sdcard formatted is not a trivial matter which is exaclty why I'm trying my best to solve this problem.

3. I do have a small team who test my kernels. According to them and me, this sdcard bug happens only once/twice. And thanks to mayurcools's report, I think we know why now.

4. If you didn't know this very kernel had 5 releases before that were stable as hell, which basically means this kernel is way past alpha. It's still a WIP.

5. I haven't displayed any such attitude. I have already mentioned in the requirements that an sdcard backup is necessary. And even if people face that problem, I try to help them. I think I havefound out the cause and I'm trying my best to solve it as I write this.

6. I have a Behaviour thread (which I suspect very few people read) and tons of posts asking users to read through the first 3-4 posts thoroughly. I know many people don't read and eventually face this problem, but I try my level best to help them.

7. TWRP isn't a joke. TWRP is preferred by thousands of users. That being said CWM is stable. CWM also has a touch version, which, if I'm not wrong, is not officially open-source. And I don't live by the "Don't fix or try to improve anything unless the thing's broken" statement, which is why Daveee10 and I included this recovery in our kernels. And I'm still trying to solve the bug.

8. I almost knew since yesterday that you'd post this. Seriously man what's with the hate? Don't post if you can't post anything useful. If you don't wanna use my kernel, it's fine by me. I know tons of people who want to use this. And all of can read and understand the risks of flashing this. And most of what you've said has been covered in the OP. Please read before posting.

9. I hope I don't sound rude, because I certainly don't mean to. And I'm sorry if I do.

sgt. meow
[XPERIA X8 Original Android Development] CtrlAltDelIrl:
Thanks for the response Sgt. Meow..

I'm not a hater, believe that. But if you look into what constitutes an alpha, beta etc; a bug which can destroy your data would deem the project pre-alpha and therefore wouldn't be publicly available.

I still believe TWRP is a mess though and a waste of time when a better option exists.

As for the thousands of TWRP preferers, I've yet to meet one in the real world..

Your post wasn't rude so I don't take it that way :)
[XPERIA X8 Original Android Development] mayurcools:
i agree with you :good:

and didnt u get bored while typing this long post :laugh: ;)
[XPERIA X8 Original Android Development] sgt. meow:
@CtrlAltDelIrl

People have different opinions.

@mayurcools

Used to it.
[XPERIA X8 Original Android Development] sgt. meow:
@feherneoh, pilu1978 and Daveee10

Can we include this bit in the recovery code

pkill twrp_recovery

and something similar with the twrp_recovery code?

I don't know if the phone can pkill something that's not running.

And is it possible to remove the sdcard mounting line from recovery_cmds and then use it in the separate recovery and twrp_recovery code? If so do we have to remount sdcard after twrp_recovery or recovery is killed?

Please check this file for reference: https://www.dropbox.com/s/wcqk8o1jjnn7rmx/original-bootrec-for-twrp
[XPERIA X8 Original Android Development] mayurcools:
@sgt.meow

what we can do is define 2 bits 1 for CWM and other for TWRP,

lets name them as cwm_boot and twrp_boot

while booting into CWM before initialise check if twrp_boot bit is zero and then set cwm_boot to one.

if twrp_boot is set to one then break from the loop and cwm will not boot.

and while exiting from cwm reset cwm_boot to zero.

also while booting into twrp check if cwm_boot is reset and set twrp_boot bit and boot into twrp.

and exiting twrp will reset twrp_boot.

can you do it?

---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------

i do have knowledge about programming assembly level, C, C++ and all about embedded system but never worked on higher level development so i do not know how to initialise these two variables.

also these variables must be volatile. or if we can initialise them in cache and linked them with ROM code then we can have both options to boot to either recovery from power menu
[XPERIA X8 Original Android Development] Daveee10:
Why you use all codes from me??
[XPERIA X8 Original Android Development] mayurcools:
Hw video is not working for me and i think its prob with ur kernel.
[XPERIA X8 Original Android Development] CnC-ROCK:
remove twrp sgt...for time being....atleast there will be some dev related posts here rather than my sd got formatted posts. the thread is getting filled up with it. everybody reporting the same known bug while some are coming up with "donot release aplha" or"destructive" things.

OR

make up a thread in general forum for bugs and discussion like nAa has done for his rom.

and ask mod to clean up posts except those of you, fotak and Daveee10 and if any other dev related thing. please ask a clean up.

when mod cleans this up then i/you will create a new thread in general section for discussion and bugs.

i am saying so just because in this thread except the OP and posts by the aforementioned people, the thread is filled with posts no good to development.

check PM
[XPERIA X8 Original Android Development] sgt. meow:
You're just too good. Just kidding. Your bootrec is the only one that worked for me, Don't worry though. I've edited the last bit. Need to check if it's working.
[XPERIA X8 Original Android Development] sgt. meow:
Did that. Now it doesn't boot into to different recoveries at the same time. But CWM still doesn't backup properly. :(
[XPERIA X8 Original Android Development] mayurcools:
But in ur code if keycheck it wil boot into cwm but it wil check for touch also as next part of code is touch check this wil boot both recovery

---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------

---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------

Do not use touch cwm, its nt necessarily needed as we have full touch twrp.

---------- Post added at 11:18 PM ---------- Previous post was at 11:15 PM ----------

Code must be like:

If keycheck then

Cwm

Break

Else

If tapcheck then

Twrp

Break

Else

Boot

Endif

Endif
[XPERIA X8 Original Android Development] :
Can't flash latest cm10 nightly. Both twrp and cwm says something "getprop device name E15i" like 4 times than installation aborted..

Error in the zip (status 7)

Installs fine on nAa kernel..
[XPERIA X8 Original Android Development] TAJ_Rocks:
:banghead:

Read the first three post of this thread & report

:banghead:

Sent From Walk-MAN By Using Thumbs To Yours Retina
[XPERIA X8 Original Android Development] laufersteppenwolf:
take a look at the 2nd post...
[XPERIA X8 Original Android Development] pilu1978:
@sgt. meow: looks like the posted bootrec can be the source of the sd bug (multiple mounts of sdcard as feherneoh said). And when you use the chroot command, the whole initializition procedure restarting with a new rootfs (/), all mounts will be invalid. Start the two recovery is funny, but a total idiot idea. And lot of member said: this is a twrp bug, I think they said this because the formatted sdcard contains a twrp folder. But this is normal, if the /sdcard not contains this folder, the recovery (twrp) automatically make it with the empty backup folder and the default config file.

So, try to modify the bootrec, the recovery_cmds line not needed.

P.S.: what is "original" in the posted bootrec? The original TeamWin release not contains bootrec (this is our special hack to solve the missing recovery partition), and I posted a sample bootrec, but this is totally different. :)
[XPERIA X8 Original Android Development] Daveee10:
Yeah that's made by me :)

So you say how not needed the mount before chroot? And that's cause sd format?

Trolled from my X8 using xda premium
[XPERIA X8 Original Android Development] pilu1978:
I think not need to mount. The twrp handle the partitions with own partitionmanager, and need to define the mountpoint of sdcard directly in the boardconfig when you compile it. With a "normal" phone (normal = existing recovery partition) you not need any mount. We not have dedicated recovery partition, and we must use a fake partition (the chroot method) with own init.rc (what not contains mounts before start the recovery).
[XPERIA X8 Original Android Development] kiratheone:
someone can help me?

why i cant change the I/O scheduler from default noop?:confused:
[XPERIA X8 Original Android Development] sgt. meow:
@pilu1978

I removed the mount line from recovery_cmds and inserted separate mount lines in the different recovery functions.

I also made sure that two recoveries are not booted at a time. You cannot boot into TWRP if you've already pressed the back button, and vice versa.

I'll pack a ramdisk with the aforementioned commands in bootrec removed.

And it's named original because I still hadn't changed anything at the time of upload.

Thanks a lot.

@kiratheone

You have to use SetCPU or any other CPU control app. You can change it from there.
[XPERIA X8 Original Android Development] mayurcools:
use no frills cpu

---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------

@sgt.meow

please check HW video decoder bug
[XPERIA X8 Original Android Development] kiratheone:
ok thanks:good:

solved the problem

btw its bug? coz when i using nAa kernel and try change the I/O scheduler, its work.
[XPERIA X8 Original Android Development] sgt. meow:
After testing (mayurcools and I tested it), I can confirm the following fixes and bugs:

1. SDcard bug is fixed (still a bit unsure about it, but neither mayurcools nor I could reproduce the bug)

2. The "entering both recoveries" bug is fixed.

3. H/W video decoder is fixed.

4. I/O Schedulers still can't be changed from the Settings > Performance > I/O Schedulers drop-down list.

5. CWM backups still have problems.

6. GApps can't be flashed via CWM but they seem to work fine when flashed via TWRP.

That's the way to go. Please help with bug-reports. And don't spam. If you have any idea, let us know here. But please don't spam.

Next release will be uploaded after another user tests it.

Stay tuned.

sgt. meow
[XPERIA X8 Original Android Development] Daveee10:
I've got idea why not works I/O scheduler changing... If I arrive home i will write pm for you

Trolled from my X8 using xda premium
[XPERIA X8 Original Android Development] sgt. meow:
@Daveee10

The solution to the sdcard bug (I'm still praying it doesn't randomly show up again) was so simple, I literally laughed till tears ran out of my eyes. Mom thought I was going nuts. I just removed the mount line from recovery_cmds, and added it to the separate recovery and twrp_recovery codes. And then at the end I just had to write some if lines.

if keycheck

then

recovery

else

if ??check (I forgot the name :p)

then

twrp_recovery

else

the actual boot bit (I added the mount bit here too, just in case)

fi

fi

Credits: Daveee10, feherneoh, mayurcools, pilu1978 and everyone else who reported the bug.
[XPERIA X8 Original Android Development] mayurcools:
i also had same problem.

you have to mount system first before flashing sevenbean gapps.
[XPERIA X8 Original Android Development] sgt. meow:
CWM backups work now after mounting /system and /data!

Note: Don't pull out the battery if you think it's taking too long. It's actually in progress. The progress bar is really tiny and you can't see it properly, but it's actually working.

Daveee10 has found out a way to change I/O schedulers.

Expect a fully fixed release soon!
[XPERIA X8 Original Android Development] sgt. meow:
Thread updated with new version. Most bugs have been solved. Therefore I expect no further spamming.