yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Troubadour666:
i have some trouble when i flash some ROMs with preload managment partition.

trouble is on 1rst rom or 2nd rom, it only concern 4.1.2 roms. i think i'm the only one with this trouble...

so, flash of rom are ok, rebbot too but when roms boot, after bootanimation, there is no optimisation process like usualy, i have just blackscreen and phone is still alive ATM of blackscreen.

When i boot my 4.4.2 2nd rom to see how i can find solution, i can see that /data_pri_rom/dalvik-cache/ contains all system@framework@...... [MENTION=928382]classe[/MENTION]s.dex files, and only one system classes.dex file which is system@app@SecSettingsProvider.apk@classes.dex.

i dont understand why this happend only with two roms i try. miss all other classes.dex files.

Sometimes, in recovery, when we reboot, we can have 2 questions .

one is about fixing su if i remember, we have to say Yes or No.

the other question i have sometimes in CWM when i reboot is about an 'advise' to flash stock rom , and i think i fix it and since i have trouble with stock jb 4.1.2 rom, in 1rst rom or 2nd position .

this 'cwm advice' i try to explain here in cwm when we reboot is about "flashing stock rom' or something like that if i remember.

- is my trouble relative with this fix i do some days ago?

- i dont want to make total full factory reset wipe.....just want to know how this is possible.

i always backup my actual 4.1.2 rom before a flash, and when i restore it, i clean dalvik and reboot. ROM boot is ok too, optimisation process is ok, and all classes.dex files are present....and when i re-flash this rom , all is fine too.

my trouble only happend when i flash new 4.1.2 roms

realy dont understand what happend.

thanks
[Galaxy S II Android Development] saspo59:
sod/blackscreen on samirom with 8.43.79 with 8.43.76 was ok ,sorry no log just info
[Galaxy S II Android Development] CounterC:
Random soft reboots while navigating in settings menu. Happened twice fast, then wanted to record logcat but did't happen anymore.

Running latest AOSB (4.4.2) and Dorimanx' v79...

Will try to post logcat if I can reproduce...
[Galaxy S II Android Development] sopla4ever:
Try get logs using this guide
[Galaxy S II Android Development] dmagician:
ADB device ID

... bumped ...
[Galaxy S II Android Development] szymko1995:
Latest kernel works damn fast on latest cm11 nighty.

Thx [MENTION=2376110]dorimanx[/MENTION]

Wytapane z sgs2 napędzanego przez cm11
[Galaxy S II Android Development] m1trand1r:
+1....same here....running like a beast here.....on Stable 4.3.1.....Kitkat sucks pretty much because of that extsdcard bug.....that's pitty ....IMO:(

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] cybernetus:
On 4.3.1 too and its amazing here too :)

Sent from my GT-I9100
[Galaxy S II Android Development] Christiancs1969:
this ones ok. Gunnu change kernel...though?
[Galaxy S II Android Development] Computoncio:
[MENTION=4526073]Christiancs1969[/MENTION] can you test to see if v79 is stable with cyanfox?
[Galaxy S II Android Development] Christiancs1969:
Yes...I will
[Galaxy S II Android Development] m1trand1r:
Ah....mate....i'm not in the flashing/wiping etc. mood right now....maybe some other day/time....:)

It might be if extsdcard bug isn't present in Cyanfox itself :good:

It sure rocks here....v79 I mean....:good:

oh.....and apparently [MENTION=2376110]dorimanx[/MENTION] is finalizing kernel for S-2 I saw.....:).....so.....that's somewhat sad IMO....:(....anyway it'll live on my device as long as it'll be able to...:good:

Beam-ed through your pineal gland via//Android 4.3.1:p//

---------- Post added at 08:24 PM ---------- Previous post was at 08:22 PM ----------

yes....you know why...?....coz 4.3.1 is still by far best OS for our "Oldie Goldie" device.....period....:)

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] Christiancs1969:
All good here....
[Galaxy S II Android Development] dorimanx:
That is correct behavior, and by my design.

You want security use stock.

Adb is rooted. Usb debugging icon killed, i like it that way. My kernel my rules. :)

Sent from my LG-D802
[Galaxy S II Android Development] Rachid.Ala:
btw we love your rules lol :D
[Galaxy S II Android Development] j1gga84:
Is it not possible to fix the ext so card bug by kernel or is this ROM related?

As I said before, absolutely no problems with gustavo_s kernel and that is what I do not understand!?

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] Twiq:
[MENTION=4663860]Computoncio[/MENTION] can you check this when you have the time? https://github.com/gustavoss/androi...mmit/ff657b9c5093b6753276f1eaf847a89d51591671

Running 0213 Sabered SlimKat | Computoncio's DorimanX 10.43v76
[Galaxy S II Android Development] troyjamz:
Softbrick?

Hey guys!

I got a big problem here. Im pretty sure I flashed the wrong kernel (	Kernel_Dorimanx-V10.43v72-cybernetus-[15-42]-[15-02]-JB-SGII-PWR-CORE.zip)

Now obviously this is my own fault, but I seem to have gotten myself into a softbrick of some kind.

I can not boot into a ROM (Not a big deal I can always flash a new one)

Lost my recovery (Same here, I can always reinstall a new recovery)

But here is my biggest issue, I need to be able to flash a stock rom or recovery of some kind via Odin, but now there seems to be an issue with the connectivity(device not being detectd).

What I have done so far is the following:

Downloaded Stock Firmware

Installed Odin3 v.1.85

Installed Kies to get device drivers

Booted into Odin Mode on my phone and connected it to my computer

But no matter what usb port or cable I use I get the same result, the device does not get detected

I also tried connecting my girlfriends SGS4 just to check and that worked fine so the cable and the ports can not be the issue I guess.

Does anyone have any other suggestions for me to try?

Any help is welcomed, thanks ahead of time!
[Galaxy S II Android Development] Rachid.Ala:
your device can't be bricked with flashing Kernel_Dorimanx-V10.43v72-cybernetus-[15-42]-[15-02]-JB-SGII-PWR-CORE.zip

Can you check md5 to see if it's not a corrupted download ?

Do you have access to download mode ?

It looks like you have a problem with drivers, you can try uninstalling them and installing them again
[Galaxy S II Android Development] 99x:
What bug is that mate? I've not noticed any SD issues with cm11, but maybe I'm not looking in the right place lol
[Galaxy S II Android Development] troyjamz:
Well yes, I can access download mode. I just can not get my device to be detected by my computer for some strange reason.

So far I have tried different usb cables and different usb ports but without any luck
[Galaxy S II Android Development] silentcontrole:
try in anather computer then (after runing odin and plug on your device "which is on download mod" your internet need to be on "it might download the drivers it self")
[Galaxy S II Android Development] marjune23:
Start Ot...

No question about that mate.

Your kernel is best among the rest!!!:D:thumbup:

End of Ot...

My tapatalk Signature

Phone: Samsung Galaxy S2 i9100 & Nexus 5 (not rooted)

Currently on Dualboot

1st Rom: AOSP NeatRom v3.1

2nd Rom: NeatRom Aroma v5.7

Kernel: Dorimanx 8.43vXX Test Builds

My procedure in dualbooting NeatRom

Flashing Stock Firmware and Custom Rom

Neatrom Family Off topic discussion

New members friendly Q&A thread

NeatRom v5.7 Collection of Mods (link to post)

Hit thanks button if you think I helped you...:o
[Galaxy S II Android Development] TheImpossibleEnemy:
just to report

v79 better than ever here:D
[Galaxy S II Android Development] sien1996:
It's a media scanner bug. Try listening to music for a long time, it'll suddenly just pause. That's actually the only reason I'm still on 4.3.1 :(

Tapatalked from a S2 powered by Dorimanx kernel!
[Galaxy S II Android Development] bytes2000:
Check this thread: http://xdaforums.com/showthread.php?t=2345831

Just be careful, some of those alternatives look dangerous :)
[Galaxy S II Android Development] Hopper8:
Thanks for linking that, I was just about to link it myself. But nothing in there is dangerous. [MENTION=2071237]troyjamz[/MENTION], Flash the 3 part firmware linked in there, using as many original cables as you can, on different USB ports and different computers. Good luck!
[Galaxy S II Android Development] Computoncio:
Well i manage i way to catch kmsg to a file and it will create a file named /sdcard/2014-02-20.00-00-00kmsg.log.

This way we may find what's causing the sod in rootbox and others roms, or find new issues, hope not ;)

Just flash kmsg_log_v1.zip in recovery and install is done.

Just flash kmsg_log_v1_uninstall.zip in recovery and uninstall is done.

Or do it the manual way, just copy the file 99zkmsg to /etc/init.d/ to install

and to delete just delete the file 99zkmsg in /etc/init.d/ to uninstall

For the dev's ;)

#!/system/bin/sh
NOW=$( date +"%Y-%m-%d-%H-%M-%S" );

KMSG=$NOW"_kmsg.log";
(cat /proc/kmsg | while read LINE; do echo '\06kernel\0'$LINE'\0' >> /sdcard/$KMSG; done)&
[Galaxy S II Android Development] Twiq:
Sweettt..

I'll save it as script, since i've disabled init.d ?

Running 0213 Sabered SlimKat | Computoncio's DorimanX 10.43v76
[Galaxy S II Android Development] dmagician:
Thanks for the replay (and few more things)

First, thanks for the replay: Now I understand why it is gone.

Second, As you've said, your kernel, your rules -- And I do not have any problem with these rules!

I've been using your kernel for about 4 years now (after the first (and only) half year I've been on the pure Samsung stock)... and at times ware that I could not use it, I've worn off the F5 on my keyboard checking these threads every few hours on a daily basis until I've get it working again.

and as I've said, THANKS!

This was / is / to be the most advanced (and power saving) kernel I've ever used.

(The only this I still do not understand is the strange ADB Device ID... Is this one by design too?)
[Galaxy S II Android Development] dorimanx:
Its special adb bin for dev that build apps. So yes.

Why its so important to you?

Sent from my LG-D802
[Galaxy S II Android Development] Tiongkia:
Thanks!

flashed v79 and booted without issues. Let's hope that it's stable :laugh:
[Galaxy S II Android Development] j1gga84:
Sounds interesting to review because gustavo_s kernel does NOT have the ext sd card bug and I think it is not a shame to investigate commits from another Dev!

Not everybody has this bug but it is annoying and NO, my external SD is fine and I won't format it or whatever. Before I do that I would go back to 4.3.1 or change kernel to "solve" this problem, for me ;)

Maybe also fusionjack can have a look for this because it seems to me that this bug does not have much attention..

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] dorimanx:
we have that.

and FSYNC is OFF as with gustavo.

FSYNC kill data! and very unstable mod. it's should be erased from history for good.

but people still add it, then get burned and turn it OFF... no one learn from others.
[Galaxy S II Android Development] dorimanx:
Uploaded new BLIND TEST KERNEL.

Merged all updates from main line.

Kernel_Dorimanx-V10.43v80-NOT-TESTED-DANGER-[10-33]-[20-02]-JB-SGII-PWR-CORE

DO not test without USB + PC + ODIN + TAR kernel.

have fun.
[Galaxy S II Android Development] sien1996:
Still gonna test even exams are next week, let's do it.

EDIT: Yay it boots and everything is ok with SLIM 4.3.1. Is it just me or after boot, phone was way smoother than before. Or was it the clean flash a few hours ago. Nevertheless it boots and that's the main thing. :D Good job :p

Tapatalked from a S2 powered by Dorimanx kernel!
[Galaxy S II Android Development] manan001:
dude please surly check this out

tap2wakefunctionalaity ported and is implemented in sonyZ you can find

http://www.xda-developers.com/android/tap2wake-function-available-on-the-sony-xperia-z-zr-and-zl/

hope we can get this too also...

we can have for s2 also please check it..
[Galaxy S II Android Development] j1gga84:
I think fusionjack referred besides disabling fsync also to another fsync mechanism that is used by gustavo_s, see:

http://xdaforums.com/showpost.php?p=50477788&postcount=9474

If you use the same mechanism like him maybe this "bug" is ROM related and dissapears if fusionjack changes it in ROM but maybe I am completely wrong with my thoughts, sorry, I am no developer :p

Regards
[Galaxy S II Android Development] 99x:
v80 booted fine on cm11 nightly :thumbup:
[Galaxy S II Android Development] dmagician:
I've first noticed it when I've tried using one of my customized automation tasks for installing some files...

-- noticed it because the ADB Device ID was hard coded into one of my batches...

To clarify, It is not SO important, but rather just understanding what is the cause of it, It had no impact on any other thing I've tried.

Just for the sake of understanding.

Thanks for the quick response.
[Galaxy S II Android Development] Ganjax:
It's possible to implement newer CWM (KK support) ? Port or something? or make two versions, first with older cwm and support dual boot, and second with newest cwm and not support dual bot
[Galaxy S II Android Development] sien1996:
This has been mentioned many times before, the new recovery is on the way, courtesy of Mr@StanTRC :p. Actually technically speaking, this kernel supports KitKat, :D just flash a compatible CWM recovery before flashing or patch the META-INF on ROM zip. Both work. Patience is a virtue my friend. :p

Cheers :D

Tapatalked from a S2 powered by Dorimanx kernel!
[Galaxy S II Android Development] j1gga84:
Or a poll who needs dual boot and who does not need it ;)

Regards
[Galaxy S II Android Development] Troubadour666:
hahaha :)

i quoted you again :) here [MENTION=4699854]j1gga84[/MENTION]

i want to add : "are you doctor? why do you want to manage my addiction ? please let me continue to be sick with dualboot :)"

thanks
[Galaxy S II Android Development] Ganjax:
Dear Friend, but with nightlies CM11 daily update, it would bit annoying to change meta-inf folder every time.. next thing is that it's not easy if i download updates by my S2, not by PC, and as you know, OTA Updater does not support custom kernels, sorry, but not everything is easy as we want :)
[Galaxy S II Android Development] sien1996:
CWM compatible is easier man if you don't dualboot that's the way I use when I was on KitKat, just flash CWM compatible for KitKat then reboot to recovery then flash as usual :D

Just an extra minute spent in recovery I think :p

Tapatalked from a S2 powered by Dorimanx kernel!
[Galaxy S II Android Development] Rebelpriest:
Increased Boot time

Hi Everyone,

Please help out with this issues

I have been using the Dori KK Kernel with OMNI ROM & Carbon ROM.

I have seen a great increase in boot time which was With default kernel (38-40 sec) but with Dori 10.43vXX it reached to (90-110+ secs)

but this is for every Boot not only first boot. :(

I have tried installing the Apollo Kernel boot time was like 45-50 secs.

Can You please help me out with this issue? Am I doing it something incorrectly ?

Please guide.
[Galaxy S II Android Development] 99x:
This is just the way it is, dori kernel performs extra checks on boot. I don't think <1 minute is going to ruin your life lol
[Galaxy S II Android Development] Rebelpriest:
Well, I don't mind giving extra minute.

The Only thing is Dori Kernel Are Smart, Famous & most productive. but still other Kernels gets that extra edge over boot time.

Dori Kernels give your device extra RAM to perform Better because of Better display drivers

During JB days, Dori Kernels were Lighting fast.

I have been following this thread & people are sharing boot time reduction posts.

That Actually made me curious Like Am I doing something wrong.

I have searched a lot but I haven't been able to find a concrete reason for the same.

Search Still going on ......!!!

And Its Always good to ask a Question as it makes you learn something new.
[Galaxy S II Android Development] m1trand1r:
Yeah....and

what not?:p

Do you really think that [MENTION=2376110]dorimanx[/MENTION] is an E.T. with extreme super powers?

Well....think again:p

I'm using it.....and until KK is really what we want....i'll dualboot :good:

It's not the question about "who wants to" or "who doesn't want to" dualboot .....kernel has dualboot and it won't get changed to some zillion versions of one kernel....we already have 3 versions....what more do you want?*SMH*:rolleyes:

Hell yeah....signed under your statement :good:....dualboot is tradition and I didn't see any other S-2 kernel to have it....except original Siyah which is more or less dead....:)

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] dorimanx:
no can do, very different touch screen driver.
[Galaxy S II Android Development] cybernetus:
New kernel, v80 runs without problems here .

Sent from my GT-I9100
[Galaxy S II Android Development] Christiancs1969:
I'll build cyanfox nightly 20 and then flash report.,?
[Galaxy S II Android Development] j1gga84:
Softreboot after turning on screen on charger! Log in attachment.

but apart from that and the external SD / Musicplayer issue V80 is running very smooth! :good:

Regards
[Galaxy S II Android Development] Spaulding89:
V80 is really great :)
[Galaxy S II Android Development] m1trand1r:
v80....boots on both slots....running w/o any issues on 2nd rom now...:good:

Great work [MENTION=2376110]dorimanx[/MENTION] .....especially w/o device to test...:good:

Beam-ed through your pineal gland via//Android 4.4.2.:p//

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------

there's no DS while charging LOL:p

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] saspo59:
please someone build for 8 ver.:crying:
[Galaxy S II Android Development] j1gga84:
Haha, of course you are right, I changed my post :good: ;)

Regards
[Galaxy S II Android Development] Twiq:
[MENTION=4663860]Computoncio[/MENTION] i've tested [MENTION=4751001]lakicamm[/MENTION]'s proposed values for MXT224E. Initially tested on v76 then switched to v79 and it's behaving normally on both builds, touches and movement are precise and smooth on battery or while charging..

Here are the values :

Batt Touch Treshold E : 40

Batt Move Filter E : 12 (didn't change default value)

Charge Touch Treshold E : 48

Charge Move Filter E : 44

Batt/Charge Noise Treshold E ( not applicable or no option on stweaks )

Running 0213 Sabered SlimKat | Computoncio's DorimanX 10.43v79
[Galaxy S II Android Development] cybernetus:
New builds are up ( v80 for all branches )

The 10.43v80 is the same kernel of [MENTION=2376110]dorimanx[/MENTION].

http://dorimanx.ataliba.eti.br /

Commits

kernel: https://github.com/dorimanx/Doriman...mmit/815e9e1567c512d0777cb0f72ad50f579842d0da

initramfs: https://github.com/dorimanx/initramfs3/commit/726614a9b9d006b07dea7f0d55718b503ced584c
[Galaxy S II Android Development] saspo59:
Can someone clatefay how comp. build get no 81 and ceb. is only 80
[Galaxy S II Android Development] Computoncio:
Thanks [MENTION=4546441]Twiq[/MENTION] for testing the settings on MXT224E.

I added kmsg_and_logcat_log_v1.1.zip to my fileserve,

kmsg_log_v1.1 changelog:

Just log kmsg to sdcard

Add a delay of 2 minutes to execute after boot.

kmsg_and_logcat_log_v1.1 changelog:

Log's ksmg and logcat to sdcard, with a delay of 2 minutes to execute after boot, just to don´t delay the boot time more ;)

Link to my fileserve

Build v81 for all branches

The only difference between my build and dorimanx or cybernetus is the initramfs commit that you see below. That's why i increase the build number, lets see who's the first to ask "What's the difference between......" :P

If you want to test the new touch screen sensibility you must reset stweaks profile in recovery or in stweaks.

Kernel_Dorimanx-V8.43v81-Comp-[14-53]-[20-02]-JB-SGII-PWR-CORE.zip MD5: 790ba0647351569b4a4856317269c38a

Kernel_Dorimanx-V9.43v81-Comp-mv2-[14-50]-[20-02]-JB-SGII-PWR-CORE.zip MD5: 82924eb6585021ca9832ddb65bb045da

Kernel_Dorimanx-V10.43v81-Comp-mv3-[14-47]-[20-02]-JB-SGII-PWR-CORE.zip MD5: 9a03ed4b848ee1177708e6ef0c2ed606

Commits:

Kernel V8: printk: fix syslog() overflowing user buffer

Kernel V9-mv2: printk: fix syslog() overflowing user buffer

Kernel V10-mv3: printk: fix syslog() overflowing user buffer

initramfs: Fix touch screen sensitivity of MXT224 and MXT224E

If you had wait till i announce you will know:rolleyes::cool:
[Galaxy S II Android Development] EvilAndroidVesper:
Nice one :) flashing in progress :P

You made it hard to choose between yours and and cybers/dorimans. Well I guess lets try both :P

Anyway thanks for awesome work :good:
[Galaxy S II Android Development] m1trand1r:
hey....what's new?:p

No....seriously....v81 runs fine here as of now....I still need to reset Stweaks profiles tho...although everything works as.should ;):good:

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Troubadour666:
Hi,

little speed feedback

1 - i cant test Kernel_Dorimanx-V8.43v81-Comp-[14-53]-[20-02]-JB-SGII-PWR-CORE because META-INF miss in zip, and zip is broken.

2 - with 8.43v80 , wake up is ok when phone in on charge.

3 - 8.43v80 doesnt wake up roms with dualboot i have, Resurection KK and NeatRom 4.1.2.

back to v76 Comp-[00-21]-[17-02] , best for me for now.

thanks.
[Galaxy S II Android Development] kg2811:
I've this problem too. On cybernetus 8.4.3v65 is all good, but on cybernetus v80 and computronicos v79 I"ve got this problem by waking up.
[Galaxy S II Android Development] scorpion.hbs:
phone doesnt boot with RR KK And this v80 kernel.

i tried v9.43 and v 10.43
[Galaxy S II Android Development] Troubadour666:
sory, i use branch 8 (v80 have booted here) and i have to add that i changed Mali in RR rom to dualboot it with JB SAMMY Stock 4.1.2.
[Galaxy S II Android Development] nik60:
RR KK is mali3

Need 10.xx version

Troubadour speak about RR KK modified for dualboot

I have sod in sleep with v77-78-79-80-81
[Galaxy S II Android Development] cybernetus:
I say that here . RR is Mali.v3 and not run with the 8.x branch ...

Sent from my GT-I9100
[Galaxy S II Android Development] scorpion.hbs:
i try v 10 for single boot with rr kk but phone not booted
[Galaxy S II Android Development] cybernetus:
I use RR for a week with the 10.x branch. If this not work you need to get the logcat to show us the error.

Without the error or [MENTION=4144763]westcrip[/MENTION] changes the Kit Kat RR to use the maliv2 .

By the way, if the RR uses the maliv2 the best is use the 9.x branch and not the 8.x branch.
[Galaxy S II Android Development] Troubadour666:
i dont want to pertube thread with my moded resurrection rom. [MENTION=4144763]westcrip[/MENTION] doesnt mod anything about mali AFAIK. but sory, its me, i use MaliV2 patch (Mali.so and /egl/ folder) to boot RR with branch 8 because i need branch 8 to dualboot 4.1.2 rom too. its the only known method.

RR rom have to be used with branch 10, you're right .
[Galaxy S II Android Development] saspo59:
Sod blacscreen on ver 81 comp. On samirom directly after boot

the screen go off for sleep but dusent turn on make a testart

and it hapend again thr same hapend with ver. 79

i will try to get logs.
[Galaxy S II Android Development] scorpion.hbs:
I tried both v9 and 10.

but after the dorimanx logo is black screen.

i reflash rom and phone booted.
[Galaxy S II Android Development] cybernetus:
It's the reason why we need the logcat when you report anything here.

Information like my phone did not initialize or got a black screen ... are irrelevant.

:)
[Galaxy S II Android Development] nik60:
?

hi

i said this,no?

RR KK work with 8.43vxx with my patch mali2 for dualboot (this is for dualboot with sammy rom)

EDIT other thing, if user want use rom 4.3.1 mali2 with dualboot romKK mali3

with branch 9.43vxx is possible with mali2 patch(only flash zip mali2 in KK rom)

my signature
[Galaxy S II Android Development] cybernetus:
Yes :)
[Galaxy S II Android Development] metalgearhathaway:
I might add that comment to my signature LOL :)