2288 replies to this topic

[Noigel]

 

Update Posted

 

Changelog

- Usual under the hood stuff

- Updated GEL Settings to v1.8.2

- Added Android L Keyboard v3.1.20006

- GPS had a fix and SHOULD work without going back to stock and getting lock

 

MD5 -  29335c16d71d79d695fc736e5563e149

 

Clean flash. 0630 build:

- Android L keyboard FC.

- back button on navbar don`t works for me (I tried flash without GAPPS and with Banks GAPPS - same result)

[nprevette420]

Hmm that's weird. That keyboard should work. I'll take it out. Back button shouldn't cause any problems, nothing has changed. Just Uninstall L keyboard.

[Noigel]

Hmm that's weird. That keyboard should work. I'll take it out. Back button shouldn't cause any problems, nothing has changed. Just Uninstall L keyboard.

What recovery did you use? I use TWRP 2.7.1.0 by Dhacker and flash build one more time - "back" button still don`t work... O_o

 

UPD. Hmm... I uninstall L keyboard and back button works now! 

[nprevette420]

What recovery did you use? I use TWRP 2.7.1.0 by Dhacker and flash build one more time - "back" button still don`t work... O_o

I haven't flashed the update, to busy worth work. But yes twrp 2.7.1.0 from dhacker. I'll check it out when I get home. For now just uninstall the L keyboard then reboot and use the other one. Sometimes keyboards mess with the nav bar.

[nate2010]

I also get the FC with the L keyboard. deselect it and all is well. still need to check to see if GPS is back yet. thanks for the update!

[alluringreality]

Can anyone give me more information on the Cyanogenmod "Screen Dimming issue (Old BL)" related to Kitstalk 6-21? I've tried searching about this item, but I don't exactly understand what happens. Is this some sort of problem with the autobrightness setting and light sensor, or does it also affect fixed brightness settings, such as the stock brightness slider? One reply suggested using slide status bar brightness option, so mainly I was curious if the dimming issue only affects autobrightness. I currently have my phone programmed to switch between a fixed brightness and autobrightness using Tasker, so if the issue is only with autobrightness I might be able to simply program Tasker to use various fixed brightness settings as a workaround. My phone is flashed to Page Plus in a way that hasn't been reported to work with the newer Verizon update, so I probably need to stay on the 4.1.2 bootloader as development generally moves to newer software. The person that mentioned the issue in the Page Plus forum appears to have posted the following:

Please Login or Register to see this Hidden Content

[drewrivera]

Those interested in battery usage, this is my KitStalk battery after a day of heavy usage. Much better than stock, IMO. http://www.droidrzr.com/public/style_images/dark_matter/attachicon.gif

Please Login or Register to see this Hidden Content

Sent from my RAZR M xt907 (KitStalk) using Tapatalk

I'm sorry but those battery numbers are not better than stock. You can get up to 17 hours almost 20 on a single charge. That's what we need to come back to the msm's rom

Sent from my DROID RAZR HD using Tapatalk

[dreamjaeil]

Can anyone give me more information on the Cyanogenmod "Screen Dimming issue (Old BL)" related to Kitstalk 6-21? I've tried searching about this item, but I don't exactly understand what happens. Is this some sort of problem with the autobrightness setting and light sensor, or does it also affect fixed brightness settings, such as the stock brightness slider? One reply suggested using slide status bar brightness option, so mainly I was curious if the dimming issue only affects autobrightness. I currently have my phone programmed to switch between a fixed brightness and autobrightness using Tasker, so if the issue is only with autobrightness I might be able to simply program Tasker to use various fixed brightness settings as a workaround. My phone is flashed to Page Plus in a way that hasn't been reported to work with the newer Verizon update, so I probably need to stay on the 4.1.2 bootloader as development generally moves to newer software. The person that mentioned the issue in the Page Plus forum appears to have posted the following:

Please Login or Register to see this Hidden Content

Idk about editing the settings but it will still persist even if you set brightness to certain degree. (i.e dimming to lowest possible state) This issue was solved in newer 4.4.4 based roms.

[nprevette420]

Can anyone give me more information on the Cyanogenmod "Screen Dimming issue (Old BL)" related to Kitstalk 6-21? I've tried searching about this item, but I don't exactly understand what happens. Is this some sort of problem with the autobrightness setting and light sensor, or does it also affect fixed brightness settings, such as the stock brightness slider? One reply suggested using slide status bar brightness option, so mainly I was curious if the dimming issue only affects autobrightness. I currently have my phone programmed to switch between a fixed brightness and autobrightness using Tasker, so if the issue is only with autobrightness I might be able to simply program Tasker to use various fixed brightness settings as a workaround. My phone is flashed to Page Plus in a way that hasn't been reported to work with the newer Verizon update, so I probably need to stay on the 4.1.2 bootloader as development generally moves to newer software. The person that mentioned the issue in the Page Plus forum appears to have posted the following:

Please Login or Register to see this Hidden Content

It's an issue in the kernel. Does it with auto brightness on and off. No fix for it on the old BL.

[nprevette420]

I'm sorry but those battery numbers are not better than stock. You can get up to 17 hours almost 20 on a single charge. That's what we need to come back to the msm's rom

Sent from my DROID RAZR HD using Tapatalk

I was getting 2 days on stock 4.1.2..... 48+ hours. I can get 20 hours out of kitstalk before I need a charge.

[pbanj]

People who are getting the fc with the android L keyboard go into settings/language and input then the settings for the keyboard then go into advanced and change the color scheme to material and try the keyboard again. I'm using the L keyboard with no issue on the second to las jb bl ROM.

[xKroniK13x]

I'm sorry but those battery numbers are not better than stock. You can get up to 17 hours almost 20 on a single charge. That's what we need to come back to the msm's rom

Sent from my DROID RAZR HD using Tapatalk

I noted that those stats were under heavy use. It was on most of the day, downloaded many apps, and lots of browsing. I can get the long battery times if I do moderate to low use.

Sent from my RAZR M xt907 (KitStalk) using Tapatalk

[randysw]

Hi guys, I'm running on an older version of kitstalk atm, v4.2.2, want to upgrade to 4.4.4, and my phone is stuck on the jelly bean bootloader (try as i might i cannt get the phone to update to stock verizon 4.4.2, all the other updates before that one work fine). I see that ill be limited to the release came out june 23, that supports the jellybean bootloader, but is there some way i can manually write the kitkat bootloader to my phone without installing the actual entire verizon version of kitkat? Id really like to be able to stay bleeding edge with beanstalk.

 

Any reply or advice is appreciated, thank you

 

PS. I am in jamaica with the phone GSM unlocked, no verizon stores in jamaica, but all the updates (except kitkat) worked over wifi fine on the stock verizon rom)

[nprevette420]

I dont know of any way of getting only the bootloader. All i can say is to FXZ back to stock 4.4.2 to get it. Get the custom TWRP 2.7.1.0 from dhacker (in OP) and flash away for my newest rom updates. And if you are on JB BL, last one you can use is 6-21...6-23 is for new BL.

But what device do you have...XT907?  XT926?

[nprevette420]

Ok so I wil remove Android L keyboard in my next update since it is causing issues and I just saw there is an update to fix speakerphone  

I will get an update out tomorrow for you guys. As always when i release the update, let me know if the stuff is fixed or not. You guys get to flash the updates before I do lol.

[nate2010]

hmm on a clean install of the 6-30 build and still no GPS :/

[nprevette420]

OK so it wasn't fixed with that patch. Try this with the new 6-30 build

Install this

Please Login or Register to see this Hidden Content

Pick North America then United States (or where ever you are located)

Then try to get a GPS lock. If not then I guess the fix from a few days ago until there is another patch.

[nate2010]

bah, still no joy. ah well. no big deal, i can survive without it.

[aum1020]

Despite my efforts to flash the ROM as clean 3x wipe it will abort as it says the ROM isn't for MB886. I'm coming from 4.4.2 KitStalk and RR 4.4.2,I did all and it goes same way no matter what. I'm not sure if I do the right thing or the ROM is not really compatible, or the CWM 6.0.4.4 is throwing me off somehow.. Any advise will be appreciated!

[aum1020]

Despite my efforts to flash the ROM as clean 3x wipe it will abort as it says the ROM isn't for MB886. I'm coming from 4.4.2 KitStalk and RR 4.4.2,I did all and it goes same way no matter what. I'm not sure if I do the right thing or the ROM is not really compatible, or the CWM 6.0.4.4 is throwing me off somehow.. Any advise will be appreciated!