yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] :
[MENTION=4562972]TheBootloader[/MENTION]

v3 got problems to my phone...

I flashed it and rebooted and everything went fine. Then I connected my device to my PC and it didn't recognise it, it said the my phone was not properly connected or it had problems. And on my phone, it looked like that it was connected to the wall charger, no usb options. THen I rebooted and my phone didn't boot, it stayed at the 'Samsung Galaxy S4 Mini i9195' screen and kept rebooting that way.

I fixed it by flashing the stock samsung2 kernel and then flashing v2 again.
[Galaxy S 4 Mini Android Development] sasank360:
Yes [MENTION=4562972]TheBootloader[/MENTION] I am facing same issue as [MENTION=4846885]RoyaLKurTx3[/MENTION].

Flashed briskV2 to get device working again. Seems to be some issue with adb or mtp in the kernel. Thanks for the update. :)
[Galaxy S 4 Mini Android Development] TheBootloader:
Ouch! Well, that's unexpected.

sasank360: Did the bootloop happen to you too?

Also, can anyone provide phone logfiles when plugging the USB cable into a computer with brisK v3? - I don't have a cable with me right now. Sorry :S

Well, at least everything else seems to work. I expected many more WiFi issues than I experience right now hah :D
[Galaxy S 4 Mini Android Development] :
I'll provide the logs in a minute.

Edit: When I inserted the cable, the phone started the bootloop...
[Galaxy S 4 Mini Android Development] denon480:
Which name of v3 ? I don't see in first post.
[Galaxy S 4 Mini Android Development] sasank360:
Yes, the phone was stuck @ S4 Mini I9195 screen. Does nothing. BTW how to logcat via adb when the phone is not recognised by PC. Thanks.

Find and Download this file ...

brisk_kk-stock_2014-12-07_00-57-00_23da34c.zip

It is in attachments.
[Galaxy S 4 Mini Android Development] kubura2999:
Same here.

Bootloop after i plugg to my laptop.
[Galaxy S 4 Mini Android Development] sasank360:
Here is what I did. Started LOGCAT app and connected to PC. Then phone went into coma. :D

After restoring nandroid I found a text file in internal storage. Zipped that and attached down below.
[Galaxy S 4 Mini Android Development] TheBootloader:
Ah so it bootloops right after connecting. That makes debugging a lot harder. :(

And just to be sure: Taking the battery out and re-inserting it doesn't help either? - It still won't boot again?

Thanks a lot for your effort! Unfortunately this file does not help at all, as logcat crashed along with the kernel before logcat could write what's wrong. :(

Right now I'm preparing 3 different test-kernels. Hopefully 1 of them will work and that will tell me where the error comes from.
[Galaxy S 4 Mini Android Development] TheBootloader:
brisK v3 test kernels with reverted changes.

Hopefully at least 1 of these will allow USB-to-PC connections without causing bootloops.

Please test, if possible. Thanks! :)

Edit: Files removed.
[Galaxy S 4 Mini Android Development] :
Test 1 worked perfectly.

If I understood correctly, 'opt' is the one that's causing MTP not working correctly and causing bootloops.
[Galaxy S 4 Mini Android Development] sasank360:
[MENTION=4562972]TheBootloader[/MENTION] Thanks for your work.

Test-2 and Test-3 builds working fine. MTP works and I tested "adb devices" command via minimal adb. It recognises the device. Thanks again. :)
[Galaxy S 4 Mini Android Development] TheBootloader:
Thanks for testing! Looks like the 'Opt'imizations of the kernel config disabled something important for USB. I assume it was something in the disabled debugging-code. So for now, I've only enabled the debugging-unrelated changes in test4.

Please also try test4, if you can. Thanks a lot! :D

Edit: Files removed
[Galaxy S 4 Mini Android Development] TheBootloader:
With Tony Starks words: My bond is with the people, and I will serve this great nation at the pleasure of myself. If there's one thing I've proven it's that you can count on me to pleasure myself.

:D

Test 1 didn't work??:confused:

RoyaLKurTx3, sasank360, one of you two must be wrong. Either test 1 works for both of you, or for none of you. - At least that's how it -should- be. :eek:
[Galaxy S 4 Mini Android Development] sasank360:
I am sorry dude. Because [MENTION=4846885]RoyaLKurTx3[/MENTION] tested and mentioned Test-1 build works I did not bother to test that again. So I went ahead and flashed builds 2 and 3.

So u can take it for granted that all 3 builds are working. :good:
[Galaxy S 4 Mini Android Development] TheBootloader:
No worries, but you scared me a bit! For a moment I thought "Oh god no, this is one of those unsolvable problems..." :D

(The changes from test1 are also in test2. The changes from test1 and test2 are also in test3.

This means if test1 works, test2 and test3 -MUST- work too, or there's something REALLY ****ed up. ;) )

Hopefully test4 will work for you too now. (See my previous posts for download.)

Thanks for testing! :)
[Galaxy S 4 Mini Android Development] :
Test4 worked, so the problem is not from those half optimizations, from the other half.

You can give me half of the not working half to test it ;)
[Galaxy S 4 Mini Android Development] sasank360:
Test-4 works too. :) Just like other builds I tested MTP and ADB works. PC recognises device as both. Good work..
[Galaxy S 4 Mini Android Development] TheBootloader:
You might want to download brisK v4 from the first post! :)​

Thank you two for helping me! :) Much appreciated!! :o :laugh:

brisK v4 is basically the same as test4 - only re-packaged properly. So you don't need to update if you don't want to.

(Maybe I'll upload another test version later, we'll see.)
[Galaxy S 4 Mini Android Development] ladislav.heller:
2 times random reboot with v4.
[Galaxy S 4 Mini Android Development] TheBootloader:
I ran v3 (same as v4 without the USB fix) for ~14hours and had no random reboots so far. I upgraded to v4 too now, we'll see.
[Galaxy S 4 Mini Android Development] nunein:
Just to make sure that i haven't missed this: v4 still doesn't support BLN & USB-OTG?

Thanks anyway.
[Galaxy S 4 Mini Android Development] TheBootloader:
Correct.
[Galaxy S 4 Mini Android Development] :
I didn't have any random reboots..
[Galaxy S 4 Mini Android Development] kaizokan:
Thanks for adding init.D :D

No more JB?
[Galaxy S 4 Mini Android Development] rpgdev:
Once you add BLN I will finally go back to KK stock :)

Keep up the good work!
[Galaxy S 4 Mini Android Development] TheBootloader:
Read the 1st post please, there's all the info about it. :)

Not sure if that will happen. I want it too, but I also have no clue how to fix it. ;)
[Galaxy S 4 Mini Android Development] rpgdev:
Well, that's sad. Thanks for trying tho.
[Galaxy S 4 Mini Android Development] denon480:
wifi dosent work, dosent turn on with v4

try flash modems NE2 and NJ6

Is not help
[Galaxy S 4 Mini Android Development] Aronuser:
Did you flash stock twice or what rom are you using?
[Galaxy S 4 Mini Android Development] denon480:
I am use this http://samsung-updates.com/details/36490/Galaxy_S4_Mini_LTE/GT-I9195/SER/I9195XXUCNJ6.html rom

and why i must flash stock twice?

if you mean modem, yes i flash twice and is changed in about phone
[Galaxy S 4 Mini Android Development] Aronuser:
You've to flash stock twice just like modem that's like that on kk dunno why maybe for security. Enter download mode directly again like at modem and untick freset time and auto reboot
[Galaxy S 4 Mini Android Development] denon480:
i use this rom 2 mounts with this kernel v2 I9195-LTE-Custom-Kernel-Silviu-03122014-Odin-NK1-KitKat.tar - New Kernel source I9195XXUCNJ4 - Ramdisk I9195XXUCNK1 ( u can use on older / newer roms 4.4.2 no problem )

http://xdaforums.com/showthread.php?t=2592308

without any problem, so i dont think is problem in rom
[Galaxy S 4 Mini Android Development] Aronuser:
Okay maybe you're right i just remember i had the same issue with only one flash
[Galaxy S 4 Mini Android Development] lionidas:
:p
[Galaxy S 4 Mini Android Development] impactor:
I observed something unusual. In the battery use section of my rom running TW 4.4.2 + brisk v4, I can see that the WiFi graph indicates that WiFi is on ALL THE TIME except for the times when the phone is on Airplane mode. However, in reality WiFi is on only rarely.

Do others notice similar bug? Is this incorrect display of WiFi history related to kernel perhaps reading WiFi state wrong?
[Galaxy S 4 Mini Android Development] v00d007:
This issue happens when the google search option is turned on in wifi settings. Go to settings/wifi/advanced and deactivate the google wifi search.
[Galaxy S 4 Mini Android Development] impactor:
Bingo. Thanks.
[Galaxy S 4 Mini Android Development] glaucos:
I'm using it for two weeks, all seems to be ok.

Thankyou :)
[Galaxy S 4 Mini Android Development] Han5ixix1:
USB fast charge?
[Galaxy S 4 Mini Android Development] impactor:
I find that with this kernel, every time I turn on WiFi, there is about 10-20% chance the phone will freeze and reboot. Do others have that problem, too?
[Galaxy S 4 Mini Android Development] glaucos:
Never happened to me.
[Galaxy S 4 Mini Android Development] rpgdev:
I have owned like 4 galaxy s4 minis and they all except one suffered from constant "hot reboots" from time to time. I have frozen system apps to death in order to find out what could be the issue and I still haven't found it. This has happened with many kernels, including vikinger. Also with cyanogenmod, using their default kernel. I'm surprised more people don't seem to report this. Other people with s4 minis and stock rom have told me they suffer from the same issue. The only reason I still use the s4 mini is the size and relatively capable performance. I could easily afford an s5 but I hate big phones and the s4 mini's size is perfect.
[Galaxy S 4 Mini Android Development] impactor:
I never had this issue except for TouchWiz KitKat roms. And on current TouchWiz Kitkat rom only reboots are WiFi related. And they are not hot - as in they reboot the phone entirely, not just the system.
[Galaxy S 4 Mini Android Development] kaizokan:
Not using this kernel because i'm on JB, but i also have a S4 mini on stock (rooted and more) but don't have those hot/soft reboots like you mentioned. I did remove certain (a lot) system apps from my rom and also restrict certain functions with XPrivacy and internet with firewall. However i do remember it used to do hot reboots but i think that was because of the superuser (koushik's ) app i had that did not work well with xposed framework or the xprivacy module (still with same amount of apps). I don't have any reboots for a long time already since then.

I also like the mini's for its easy usage with one hand (reaching top left corner with thumb), easily pocket fitting size (not tight) and relative capable performance. (except xperia z compacts which have almost same performance as their big brothers)
[Galaxy S 4 Mini Android Development] rpgdev:
Interesting, I use chainfire's superuser so I think I'm safe there but for the record which superuser app do you use now? Also, can you describe what exactly do yu block with xprivacy and the firewall (I use droidwall myself but just to block the annoying push notifications of some apps). Also tell me which list of system apps did you remove? or did you just froze them? Does it have the same effect? I would really appreciate any hints as to what you've done to stop getting those hot reboots. I'm also on JB.
[Galaxy S 4 Mini Android Development] kaizokan:
Also Chainfire's. Someone else i know has a S4 mini LTE (GT-I9195) too with no reboots either and 100% stock, no root. So i don't know why it happens for yours. Everything i did change had

nothing

to do with the reboots, changing superuser app did. Before that i cannot know because i have never used my phone with full stock rom. But anyway this is what i have done.

Removed around 75 apps/widget and other apk's before i took my rom in use. With AFWall+ i blocked everything except this one 'Download Manager, Downloads, DRM....' and maybe also 'Media server' (don't remember if this is necessary if you don't use a server connection). And off course your apps that need internet connection and maybe other thing that might be necessary for you. I also froze S voice, Gallery, SensorService. And with XPrivacy i restrict almost all apps but i can't just tell what i restrict because and i quote "There are more than 400 restrictions per application and additionally there can be quite some application specific settings, for example when you use white/black lists."

If you suspect it to be app related, then u can just remove or freeze apps and test it out. Freezing is safer. Blocking things is actually more likely to cause things to not work or reboot especially if you remove important system apps or restrict permissions of that apps which can lead to bootloops. Always make a backup first.

EDIT: sorry for off topic. [MENTION=4196760]rpgdev[/MENTION] if you still want to know something pm me or move to appropriate thread : )
[Galaxy S 4 Mini Android Development] AndreaHistoryX:
I use this kernel and it's very good, I hope you can add OTG function. I will love it. thank you in advance :)
[Galaxy S 4 Mini Android Development] complience:
Does this Kernel support lollipop?
[Galaxy S 4 Mini Android Development] sasank360:
[KERNEL][I9195][Stock JB/KK] brisK v4

That is the title of this thread. It says stock jb or stock kitkat. So no lollipop. Not even custom kitkat like cm11, carbon.
[Galaxy S 4 Mini Android Development] znayver:
can i flash this kernel at ploiki ste rom
[Galaxy S 4 Mini Android Development] sasank360:
Yes you can. Make sure you have a modem that supports this kernel.

Use a good kitkat modem.
[Galaxy S 4 Mini Android Development] dkonect:
And wath about knox? Flash this kernel increase knox counter or not? (my device was built 02/2015 ).
[Galaxy S 4 Mini Android Development] sasank360:
You need custom recovery to flash this kernel.

Custom recovery is flashed with odin.

That triggers knox. No way to use this kernel without

triggering knox.
[Galaxy S 4 Mini Android Development] dkonect:
OK, but I know the kernel trigger knox(because kernel is not SE android enforcing) , but no need custom recovery because flashfire(new mop) works fine on the s4 mini
[Galaxy S 4 Mini Android Development] 00ehsan00:
which modems support this kernel?

or

how do i know my modem support this kernel?

another question : are bln and otg work on kitkat(not jb)?
[Galaxy S 4 Mini Android Development] sasank360:
Any kitkat modem should work just fine. Just read earlier pages of this thread to

see if anyone has any problem with specific kitkat modems. BLN may work. Not sure

But OTG does not work. Kernels for stock roms have less features than those for custom roms.
[Galaxy S 4 Mini Android Development] Runner_cz:
I also do have sometimes (0 to 3 times a day) such spontan reboots with this kernel. (current stock version of the ROM I use is COC2). And from my experience they are not even related to WiFi. They may occur anytime... :( Maybe it's simply because the kernel is already outdated in comparison to the newest ROMs (COC2 and newer). I really don'T know if the stock kernel was much changed since, so maybe the ROM expects something what this kernel does differently than the current kernels?

BTW, what I noticed - if I'm not mistaken the stock kernel from the COC2 has Interactive/ROW by default, while I read somewhere that before the stock kernel usually had Performance/CFQ by default.
[Galaxy S 4 Mini Android Development] impactor:
Just use SilviuMik's kernel. I never had a single reboot with it.
[Galaxy S 4 Mini Android Development] TheBootloader:
Looks like brisK v5 was just released! :) (See first post!)​

Nothing major though, I just saw that Samsungs released 2 new updated packages for the kernel code, so I went and applied those. Nothing major, but if you want to have a deeper look just visit my Github and look through the changes. :)

Also I switched back from "noop" to "CFQ" scheduler.

Have fun! :D
[Galaxy S 4 Mini Android Development] impactor:
[MENTION=4562972]TheBootloader[/MENTION],

I appreciate your work but more people would benefit from it if your kernel was compatible with not just devices with KNOX bootloader.

Details: http://xdaforums.com/showpost.php?p=61275482&postcount=949
[Galaxy S 4 Mini Android Development] TheBootloader:
Go forth and test, because

brisK v6​

was just released. As usual, look at the 1st post.

I could swear I did the KNOX stuff before... But apparently I didn't! :) Oh well, here you go!

Thank you, [MENTION=4344511]SilviuMik[/MENTION] ! :D
[Galaxy S 4 Mini Android Development] RuffBuster:
Tried v5 on "scStock" ROM COC2 base and things were working well, but I did get a reboot on a phone call. Moved to latest SilviuMik kernel in the mean time, no reboots so far. But I will be trying your latest build day after tomorrow and run it for a day or two to compare battery life. Fingers crossed as this kernel seemed to have an edge over other stock kernel builds. I do appreciate your stock work as it makes me a little sad to see just a couple of devs with interest in Stock roms. I love my debloated stock rom. I've tried 5 different builds of Lollipop and I'm not that impressed. It's just a lot of glamour at the expense of stability. Many thanks for your efforts!
[Galaxy S 4 Mini Android Development] TheBootloader:
Sorry you had to witness random reboot during a call. :/ Personally I never have experienced that.

As for the battery life: My kernel has a newer WiFi driver, maybe that uses less power? Also I put the "preemption" from "low-latency" down to "desktop". This means the screen -might- be slightly more unsmooth, but the linux kernel behind Android can work with less overhead, so it saves some minimal(?) amount of battery. -> Efficiency goes up a notch. ;) - But I have no idea -how much- this actually makes a difference, I didn't do benchmarks or anything.

About the random reboots again: I have those too sometimes, when my phone gets hot while using mobile data. If it gets hot on WiFi -> no problem. I don't understand it. :eek:
[Galaxy S 4 Mini Android Development] rpgdev:
Does it have BLN now? Sorry I ask again but it used to say on the first post that it wasn't working but now I just see BLN references without the "not working yet" part. Could you clarify please?
[Galaxy S 4 Mini Android Development] impactor:
Thank you. It seems to be working fine now.
[Galaxy S 4 Mini Android Development] TheBootloader:
BLN is unchanged: It works in the JB kernel but not in the KK kernel. Sorry! :crying:

Thank you for confirming! :highfive: Glad to hear it works!
[General Questions and Answers] DJGREEN1980:
I've been trying to get to the bottom of this problem for days now and can't work out whats wrong. I'm sure its just a setting somewhere to fix it.

When looking for an item on the google shopping site and then selecting a shop from any of the shop links I am directed to www.googleadservices.com page saying 'this web page is not available. From there I cannot use the back button on the phone to go back to the previous page as the same ad services page not available page just reloads.

This happens on all browsers on my LG G2. I am running CloudyPro G3 rom but am pretty sure it happened on Cloudy Flex too.

When using Google Shopping on a computer everything works fine as it should.

I've spent hours trying to figure this out! :(

Any ideas anyone?
[General Questions and Answers] DJGREEN1980:
Its the Rom

Google ad services pages don't load using Google Shopping on Cloudy Pro G3 rom on G2. Means you can't access any shop link from Google Shopping
[Moto G 4G Android Development] bkr32:
Reserved

Thank You to [MENTION=2614663]shabbypenguin[/MENTION] For his Source Code for device

ROM may contain same bugs as other currently available custom ROM's

Builds will continue under android L merge meaning no new features for now
[Moto G 4G Android Development] bkr32:
Reserved

ROM is now booting only bug in ROM is

GPS lock
[Moto G 4G Android Development] shabbypenguin:
fixed that for ya ;)
[Moto G 4G Android Development] bkr32:
thanks forgot to include
[Moto G 4G Android Development] classic757:
No boot-up

Wanted to test this rom but after several attempts to wipe and install, rom does not boot-up. Only I keep getting rerouted back to TWRP recovery.

Here is what I did to try and install:

wipe system,data, cache and dalvik

install rom

install gapps

reboot

would not boot

rerouted to recovery

wipe system,data,cache and dalvik

install rom

install gapps

reboot

would not boot

rerouted to recovery

Tried this several more times, no go. :(

xt1028 Moto G
[Moto G 4G Android Development] meekrawb:
Do you have a Moto G LTE?
[Moto G 4G Android Development] classic757:
No. Mine is the Verizon 3g CDMA version of the Moto G.

Is this rom for the LTE Moto G?

Edit: Okay. Now I see it in the top and bottom of the post. Moto G 4G. Got it. :silly:
[Moto G 4G Android Development] RazorGTX:
[emoji4][emoji6]

Gesendet von meinem XT1039 mit Tapatalk
[Moto G 4G Android Development] obsolete1:
Flashed it and no boot. Just hangs at the unlocked bootloader screen, so I could not take logcat.
[Moto G 4G Android Development] eteles:
Is it booting up yet? CM now has officiall support for the moto G LTE (peregrine)... Maybe you could update the source now...
[Moto G 4G Android Development] bkr32:
New Build someone test
[Moto G 4G Android Development] MissyVixen:
I have downloaded and tested it so far but I cant even get this one to install:

Isnt the Bacon the One+One ?

Finding update package...
Opening Update Package...
This Package is for "bacon,a0001" devices: this is a ""
Error in /external_sd/Roms/AOSB_kk_1.3.7_bacon.zip
(Status 7)
E: Installation aborted
[Moto G 4G Android Development] bkr32:
My bad they were in same folder and must've uploaded it by mistake, re-uploading peregrine build my upload is slow so please give it 40mins

Uplaoded correct build
[Moto G 4G Android Development] Xplorer4x4:
I might be blind..but I don't see a download link in the op.
[Moto G 4G Android Development] bkr32:
http://xdaforums.com/devdb/project/?id=5476#downloads
[Moto G 4G Android Development] RazorGTX:
Thanx

Gesendet von meinem XT1039 mit Tapatalk
[Moto G 4G Android Development] daljitbanga:
First of thank you for your hard work, good ROM.

A few minor issues I think.

1. Not showing call history

2. WiFi problem where data stops receiving and transmitting ( happens with all other ROMs even stock I think it virgin media superhub)

3. Sony smart watch 2 randomly disconnecting (not happening on stock ROM)

But can be used a daily driver.
[Moto G 4G Android Development] bkr32:
from what i understand call history and wifi seem to be issue with device tree, as for smart watches gear etc support for them will be added to ROM soon

this is just test build
[Moto G 4G Android Development] MissyVixen:
I too am having some issues with the wifi : as in it refuses to connect to any network. Neither to my WPA2 home network, or my open media streaming router. It just hangs up at obtaining IP address (same as some of the other roms floating around, so some sort of issue in the main tree), but this is the first I have seen it lock up on an open network. Will test some later as I run around town before courses this evening.

Update:

Connected fine to the FreeWifi at my doctor, and at my college. However here at home it again is not connecting. I don't know if its an issue with my router, or the ROM, but the stock Rom seems to connect fine (though it drops randomly)
[Moto G 4G Android Development] Xplorer4x4:
This is a great median between CM(lack of tweaks) and Carbon(feature packed) untill Carbon gets fixed. Sadly it was doing way to many random reboots for me. Will try the next nightly and keep my fingers crossed its more reliable. I will try to grab a logcat if it happens on the next nightly. Can you post the instructions to check out and build the source?
[Moto G 4G Android Development] PatrickDziura:
What's the bugs?
[Moto G 4G Android Development] JimYoung:
The ROM is amazing with lots of features, but I have two serious bugs: when I try to add an apn I get a message saying that phone process has stopped. Also I get error 491 on play store every time I try to download or update an app