yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] nycelitemaster:
Check off debugging option in dev mode. It should work.

[MENTION=2394329]sparksco[/MENTION], lol i didnt see anything.. I am guessing its getting hot in here (in my office). That can be the result of heat. Heheh. Also quick question, are you using straight -50 uv across the board? Or its based on Chip type?.

Thx in advance.

Sent via Google N4
[Nexus 4 Original Android Development] tyea:
You have to check of debugging to access via MTP mode, so I've obviously already tried that. My question is really asking is there anything in the ROM or kernel that could be causing this?

LG-E960
[Nexus 4 Original Android Development] sparksco:
[MENTION=490798]copi[/MENTION] it should be compatible.
[Nexus 4 Original Android Development] sparksco:
It's -50. You can go more with system tuner app if your chip gets hot but you might get sod's
[Nexus 4 Original Android Development] nycelitemaster:
Ah.. LoL i calculated by comparing your and harsh kernel. I have fast binned chip and i think i can knock off another few mv. I get no sod on harsh. Since your has some extra tweaks i gave it a go. I think harsh has code to tweak your mV based on cpu binning.

Sent via Google N4
[Nexus 4 Original Android Development] sparksco:
I don't know I don't think anything from the kernel has caused this but there's no way for me to know if its ROM or kernel related.

Edit: try this

http://forums.androidcentral.com/go...4-usb-device-since-carbon-app-downloaded.html
[Nexus 4 Original Android Development] sparksco:
This kernel is based on harsh and cm kernel so it should be the same. I just added some extra things in and keep updated with Linux.
[Nexus 4 Original Android Development] nycelitemaster:
Thank you sir.

Sent via Google N4
[Nexus 4 Original Android Development] Lownita:
Does anything speak against using trickster mod with your kernel? :)
[Nexus 4 Original Android Development] sparksco:
It should work fine just don't use it for voltage control. System tuner is the only app recommended for that.

Is what harsh as faux123 recommend using for that.
[Nexus 4 Original Android Development] Lownita:
Alright, I am coming from harsh and I was doing everything with init.d script. Are all the commands the same?

Looks like this for me:

# Vibration intensity
echo "100" > /sys/class/timed_output/vibrator/amp

# Voltages
echo "384000 712500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "486000 725000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "594000 750000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "702000 775000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "810000 812500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "918000 825000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1026000 850000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1134000 900000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1242000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1350000 950000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1458000 962500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1512000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

#Sound control headset
echo "40" > /sys/kernel/sound_control/gpl_cam_mic_gain
echo "35 35" > /sys/kernel/sound_control/gpl_headphone_gain
echo "40" > /sys/kernel/sound_control/gpl_mic_gain
echo "40" > /sys/kernel/sound_control/gpl_speaker_gain

Was also using gamma commands, but as I was sticking with PA halfbreed colors, I won't need it anymore!

Thanks :)
[Nexus 4 Original Android Development] sparksco:
I don't know about the voltage in init.d script, I just use system tuner app on my devices. Never failed me :) The sound for headset looks fine, it should be the same as faux123's instructions.
[Nexus 4 Original Android Development] ScumDroid:
thanks bro :good:
[Nexus 4 Original Android Development] sparksco:
You guys can post here for now to discuss manta. It should be blazing fast since I added a bunch more device specific optimizations. If you have problems with USB let me know cause it might be a ROM issue.
[Nexus 4 Original Android Development] yukkio:
Let me know if the uv works with that script I also use trickster and uv works (apparently)
[Nexus 4 Original Android Development] bentez2003:
Can the kernel be flashed over other roms like purity or is it only meant for the sabermod rom?

Sent from my Nexus 4
[Nexus 4 Original Android Development] sparksco:
I don't know, try it out and let us know..
[Nexus 4 Original Android Development] Syk69:
Doesn't boot for me. Stays on Google screen. I did factory reset and wiped system, davlick, cache. Using TWRP 2.5
[Nexus 4 Original Android Development] jarjar124:
+1 don't worry though. No rush :) the thought of saber on manta would be unbelievable.
[Nexus 4 Original Android Development] Syk69:
Indeed! :)
[Nexus 4 Original Android Development] sparksco:
I forgot vendor/samsung

:facepalm:

Easy fix
[Nexus 4 Original Android Development] Syk69:
Any gapps that are preferable to run with your rom? Or any will do?
[Nexus 4 Original Android Development] sparksco:
Any should work. I added some gallery fixes simular to mako so photo sync should work out of the box with any gapps.
[Nexus 4 Original Android Development] aaron.bufc:
So happy for the manta love!
[Nexus 4 Original Android Development] jarjar124:
That is indeed a
[Nexus 4 Original Android Development] ruzkay:
I don't think it is related with your ROM.

I've had it happen on stock ROM and on SM 0504 so yes it does happen on other ROMs too. I don't remember it happening on AOKP PUB but there I was using an undervolted kernel.

I think it is when you are using the phone while charging it heats up quickly so it switches to USB charging (some protective mechanism?)

PS: Great work, love SM.
[Nexus 4 Original Android Development] NoLunchBox_:
[MENTION=2394329]sparksco[/MENTION] I switched to another ROM to test it out and just started charging my phone. Long story short, it still switches between USB mode and AC mode while charging so I don't think its something you need to worry about.

Using a different kernel too.
[Nexus 4 Original Android Development] gparmar76:
The latest revision is not syncing with Google after I set my Straight Talk APN settings...checked them three times and redid them...my inverted keyboard swipe stopped working too...5/19 worked perfect.
[Nexus 4 Original Android Development] Dsmforlife92:
Loving this ROM
[Nexus 4 Original Android Development] nycelitemaster:
I think further uv reduced heat

Sent via Google N4
[Nexus 4 Original Android Development] Martin_Ro:
Try a different cable, have read that many times @ Franco.kernel

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] NoLunchBox_:
That's the weird thing, I have. And I know its not a hardware problem cuz when I force USB fast charge, it stays on AC.

So I really don't know if its a ROM or kernel issue. I'm gonna end up flashing stock soon to monitor the issue.
[Nexus 4 Original Android Development] fluffenforliberty:
What happened to all the quick toggles in the latest update?
[Nexus 4 Original Android Development] panooos:
Check OP. Some of them were removed
[Nexus 4 Original Android Development] Martin_Ro:
No, you're wrong: if forcing fast charge solves the problem it still could be the cable. The phone detects the configuration (USB or AC) by checking some pins of the cable. Fast charge simply overrides this check.

So it's propably really the cable.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] apatal:
Just the pins? Are you sure? Because I use the same cable for charging thru the outlet and thru USB..
[Nexus 4 Original Android Development] tyea:
Something weird is going on with USB, because two computers I've used before with adb will no longer recognize the Nexus 4. In device manager, I can't get the MTP driver to load. I suspect this has something to do with AOSP JDQE 4.2.2 and the recent push of Google app updates, but I only know enough to be dangerous to myself.

LG-E960
[Nexus 4 Original Android Development] sparksco:
If you can try to narrow it down some more. In my experience speculation never leads to good things with android.

If it helps any all my Google apps are updated on my nexus 7 and i have no apparent issues with mtp.
[Nexus 4 Original Android Development] Martin_Ro:
Jepp it's only the Pins

https://dangerousthings.com/shop/android-fast-charge-usb-cable/

The "trick" here is, that the shorten of the to pins is not done by the cable in normal but by the charger. But if the cable or the connector of the cable has some damage, the shorten of the pins wouldn't work ->No AC charge even on AC charger
[Nexus 4 Original Android Development] sparksco:
Hmm, seems my router died today, maybe I'll pick up a cheap one somewhere later on today.
[Nexus 4 Original Android Development] trillo69:
That might explain why "fast charge" doesn't seem to have any effect over speed charging. So it also depends on the cable, thanks for the info. :good:
[Nexus 4 Original Android Development] NoLunchBox_:
Hmmmm I guess I'm gonna have to get 2 new cables. Cuz the thing is that I have a old MyTouch cable and my regular N4 cable. I also use my old GNex charger and my regular N4 charger and it happens on both.

Gonna try out different cables and chargers and see if anything helps.

Thanks
[Nexus 4 Original Android Development] endrekok:
Hi sparksco! Will you continue rassaber project? Rascarlo deleted all his ROMs and stopped the thread. :crying: That's my favourite ROM. If it is over i will go back to stock. :(
[Nexus 4 Original Android Development] trueblueram:
There are users who are building rassaber from source (links on the rasbean thread)
[Nexus 4 Original Android Development] TheDarkDefender:
Yes. But the devs have to keep pushing the commits on github. Else, what's the use of building from an old source?

[MENTION=2394329]sparksco[/MENTION] is this done with?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] sparksco:
I don't know. I'll probably try to push my manta build for sabermod later if i can get a new router. I guess I'll probably take a little break for awhile.
[Nexus 4 Original Android Development] lowert:
spark,please, i dont want to annoy you,but can you make that stock dial pad zip?i would love to have it
[Nexus 4 Original Android Development] sparksco:
It really doesn't seem like that big of a deal to me loll. I don't know why you make such a big deal out of it. It's just a couple black themed places :rolleyes:
[Nexus 4 Original Android Development] lowert:
Well....then just tell me the lines which i have to modify,i will try it myself
[Nexus 4 Original Android Development] sparksco:
I honestly don't know. I reverted a change on github but I guess it didn't revert everything... And I don't have a SaberMod compatible phone right now...

Everyone else seems to be OK with it so that's the way is going to have to stay
[Nexus 4 Original Android Development] sparksco:
Ok guys I finally was able to get the working manta up. I'll try to get the rest of the source up on github later but the size is huge, almost 1GB extra!

This ROM is for the nexus 10

http://developer.clockworkmod.com/downloads/293/4923/sm_manta-1.0.1-1369235877-0522.zip

Have a good day everyone
[Nexus 4 Original Android Development] miguepereira77:
Question [MENTION=2394329]sparksco[/MENTION], what is exactly mmc readahead buffer size and why is so different depending the kernel? Yours is 512, is it worth to make it bigger?. Thanks in advance

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] Syk69:
Loving the speed and stability! Thanks for the great rom! So far only little minor bugs I have noticed.

Sometimes at first when superuser prompt comes up it also takes the window to the system settings screen.

Dual panel settings mode says disabled by default but if I disable and re enable it won't change back.

For some reason some tablet specific apps will show as device not compatible. NBA gametime for tablets specifically.

Other than that. Blazing! :)
[Nexus 4 Original Android Development] sparksco:
Those aren't bugs. Superuser is the way koush designed it. If you have a issue with it contract him.

Dual plane you have to exit settings and go back in...

Apps blame the app developers.
[Nexus 4 Original Android Development] Syk69:
Really? Hmm strange, on other roms when superuser root access prompt comes up it doesnt take the screen to the system settings. And ok didn't know about the dual plane settings thing. Thanks!
[Nexus 4 Original Android Development] alvin182:
this rom includes kernel with gamma controls?
[Nexus 4 Original Android Development] jarjar124:
I don't think so but it comes with pa halfbreed
[Nexus 4 Original Android Development] sparksco:
CM has their own version and probably cm clones or variants. This ROM uses the AOSP version from koush's master branch.
[Nexus 4 Original Android Development] GalaxyFan88:
Hey sparks, thanks for your contribution to a phenomenal nexus 4 experience. Since I flashed this rom a while ago, I never looked back and never was I so satisfied with the performance and stability of my phone. I'm glad you took your time to provide us with such an amazing experience. Apart from a few reboots here and there, the rom is perfect. I can't specify them, it happens occasionally. I'll try to get a logcat when i can reproduce this.

Also I noticed you removed some of the quick toggles which are not compatible with the theme chooser themes. I understand you took this decision to make the sabermod experience more seamless and stock-like but I'm sad about the torch toggle which is gone now. I used this toggle frequently and it was really convenient to turn it on after unlocking the the screen or while doing other stuff on the phone to "light your way'. I'd be glad if you would decide to bring back this toggle. The screen off toggle was also a perfect complement to the torch. I used this combination very often: swipe statusbar down -> trigger torch -> toggle screen off

I hope you can comprehend my wish. Thank you :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] sparksco:
I'm at the same point as rascarlo at this point. Same questions posted over and over again, same answers from me over and over again. Everyone wants the ROM just the way they like it which is impossible. People can't even read a page or two or three back, or do a simple thread search.

github source: www.github.com/SaberMod

How to set up a build environment on Linux: http://xdaforums.com/showpost.php?p=35338419&postcount=1

repo init -u https://github.com/SaberMod/android.git -b sm-jb-mr1
repo sync
bash sm-mako

Thread closed
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

A quick update I had a offer from someone for beta testing. So I'll probably wait on the next release until I hear back from them that everything is OK
[Nexus 4 Original Android Development] johnson8cyl:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

I don't understand what's going on at all. I came from xenon HD. Used a super wipe script made by xda user awesome, wiped everything but SD card in recovery, flashed banks gapps with stock keyboard and photosphere, wiped both caches then rebooted. No problems at all. Still on old bootloader and radio. Unless I have a reason I didn't see the need to update.
[Nexus 4 Original Android Development] drewtang:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Loved how snappy this ROM is, one of the fastest things I've seen on this phone. Went back to AOKP because I've gotten used to more customization options, but I wanted to pop in and say great job.
[Nexus 4 Original Android Development] johnson8cyl:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

To everyone having issues with the camera

Did you restore apps with titanium?
[Nexus 4 Original Android Development] strapped365:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Yeah, but only after verifying gallery being borked.

Sent From a Freaked out Nexus 4
[Nexus 4 Original Android Development] mrmarshall428:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

I was able to get mine working, after having the gallery issue. I Nandroid back to a PA 3.0 I had then like previous poster stated and used Awesome erase script and flashed Rom and Banks new gapps. Everything is working properly
[Nexus 4 Original Android Development] kptnk:
I have no problem with camera neither gallery, and i restored my app with titanium.

Flash 0220 build, this one has no problem.
[Nexus 4 Original Android Development] strapped365:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Well I used another script that don't wipe all of the SD and the issue is still there. Sunday I'll format all though. Funny thing is I was on a nand of PA to

Sent From a Freaked out Nexus 4
[Nexus 4 Original Android Development] Nark.GA60:
Hey sparksco, great ROM. As good as it is on the N7. Very fast and fluid.

Problem is that I keep my phone on my bedside at night, so I can't live without Quiet Hours. I wouldn't mind CM-style Quick Settings customisability either!

I'll keep subscribed to this thread and help out with mako-specific issues where I can.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Thanks and thanks. I guess you'll never be running this ROM on your nexus 4 then. Find me the change in cm github for QuiteHours, on the jellybean branch. Bet it can't be done. QuickSettings is not going to be like cm. Sorry bud.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Good luck man. Would like to seen that forked kernel you were talking about.
[Nexus 4 Original Android Development] strapped365:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Yeah I'll have tons to sift through on git tomorrow to see what I wanna take and what I wanna leave. Then figuring out the whole LG kernel process lol.

Sent From a Freaked out Nexus 4
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Yeah I mean I feel bad for this kernel that's in this ROM. There' s not really much there besides the sweep2wake from bricked kernel and fixed errors for using GCC 4.7 toolchain. My nexus 7 kernel has hundreds of Linux kernel patches in it, overclocking, user voltage control etc. I just don't really feel comfortable super patching a kernel that I can't test. Also I release a lot more updates for the nexus 7 since I flash all my builds before release.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

I can reproduce the black screen with your latest rom. I think it's kernel related. Every time I flash a 4.2.2. Kernel I get the black screen. On the over side 4.2.1. Kernels are working with out any problems. I don't know if this fact hast been already mentioned.
[Nexus 4 Original Android Development] eep2378:
Interesting. Especially since this Rom is based on 4.2.2

Also 4.2.2 kernel are working on 2/20 and 2/22 builds.
[Nexus 4 Original Android Development] Crimsonthunder:
AW: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

Can you also reproduce this?
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

By "latest ROM" I'm assuming your talking about the 22 build. Also I don't know what people mean when they say "black screen". Is there a Google logo and then the screen goes black? Or no Google logo? The kernel/ROM are both 4.2.2. Are others not? If it's a kernel issue I don't really know what it could be since it's based off Google's kernel source with some minor modifications. But nothing that should really cause the kernel not to boot. Have you tried the kernel in the first post on other Roms? I haven't heard of anyone having troubles with just the kernel in general on other 4.2.2 Roms.

Anyways, I don't think development can continue with more updates because of the confusion. If it's kernel related I need to know because some people say the included kernel works fine.
[Nexus 4 Original Android Development] eep2378:
On boot the Google logo shows but after that its a black screen(NO boot animation) and then it just hangs on black screen. I can't test the kernel in the first post on other roms ATM(I'm at work with 15% battery left, someone stole my charger too :mad: I had an extra one here at work)
[Nexus 4 Original Android Development] Matt:
I think it's kernel related. The screen basically doesn't show anything past the Google logo, but the phone boots up and works perfectly, just doesn't show anything.
[Nexus 4 Original Android Development] eep2378:
Re: [ROM][4.2.2-JDQ39][AOSP][LINARO][SaberMod-toolchain-4.7.x]OFFICIAL SaberMod

I just tried with an older 4.2.1 kernel(Trinity) and it booted. I tried with two 4.2.2 kernels(the one in OP and harsh) both resulted in black screen.

2/23 beta build here

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] -viper-:
Guess your Finally back? Nice surprise...!
[Nexus 4 Original Android Development] kptnk:
This is a great news, thank you Sparksco :)

"Patience is mother of all the virtues"
[Nexus 4 Original Android Development] yukkio:
Hi sparksco, thank you for give us another chance :) I write a pm but I think I've problem sending pm because they dont appear in the sent box. I'm trying to compile your kernel for mako. I'm following this tutorial: http://xdaforums.com/showthread.php?t=2021202

Is it good to build your kernel?

Thank you.

BR.
[Nexus 4 Original Android Development] TheDarkDefender:
Wow. Nice FAQ. Should save you a lot of time, IF people read the second post. Haha. Nice to have you back sparksco. :)

Sent from my Nexus 7
[Nexus 4 Original Android Development] sparksco:
Yes but use my toolchain for 4.7 and use sabermod_mako_defconfig instead of mako_defconfig as shown in this script: https://github.com/SaberMod/android_build/blob/sm-jb-mr1/tools/build-scripts/mako-kernel
[Nexus 4 Original Android Development] yukkio:
Ok man sorry for double question here and in the PM

Thanks
[Nexus 4 Original Android Development] jarjar124:
About time you reopened this thread. I'll put that FAQ on the nexus 10 thread once I'm home ;)

Edit: you misspelled FAQ lol

Edit2: added it since I'm forgetful.

Guys the dalvik tweaks done on carbon and rasbean has been added to this ROM already. The next update will contain it so don't need to ask :)
[Nexus 4 Original Android Development] clintb:
Awesome to see this thread unlocked for an absolutely amazing ROM! I don't have anything extraordinary to post about screen on times due to my usage being low, but I can say this ROM and the STS kernel are champs at going for a long time between recharges.
[Nexus 4 Original Android Development] sparksco:
Fixed. I tried to make the FAQ somewhat funny, hope I succeed :D
[Nexus 4 Original Android Development] yukkio:
Incredible, kernel +toolchains = 2.2gb :eek:
[Nexus 4 Original Android Development] jarjar124:
Haha. I see some sarcasm. Just hope people don't take it too seriously lol.
[Nexus 4 Original Android Development] apatal:
Great to see you guys working together. 2 budding developers watching each other's back. Should be fun. Looking forward to more great things from your collaboration. Don't forget you're studies! :)
[Nexus 4 Original Android Development] miguepereira77:
Yeaaaahhh! Bienvenido sparksco!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] yukkio:
Cross Fingers, building kernel started at 22:55 Hope ends someday with this core2duo :)