• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] CM 10.1 preview

IMUcarmen said:
moral to the story...don't turn off bluetooth :]

You said that you noticed it being quicker than before. What are you comparing it to? The other CM10.1 or some other rom?
Click to expand...

I was comparing to 10.1. I do see what you are talking about now. 10.1 seemed buttery smooth and pre3 and pre4 seem to have just a slight stutter when swiping screens left and right and on the menus. I may have to go back to 10.1 and if I do I will really pay attention. :) Could be I got so excited about the fixed lag on unlock!!!!
 
reeseboy said:
Baseband listed properly in pre3 for me but not currently in pre4. I dirty flashed from 3 to 4 so it might be something to do with that...

Edit: Just noticed that powering off does a reboot.
Click to expand...

I just tried this and chose Power Off and it worked. The phone was hooked up to the charger when I did this so it came back up to the battery charge screen but it is off. Strange....
 
tdm said:
This happens on my nitro aokp42 also. I think it's an aosp/cm issue. But I haven't verified with official cm yet.

Interesting that you were able to run Pandora on pre3.
Click to expand...

I thought so as well which is why I mentioned it. The more info the better is what I say :D

Another strange item, after I powered my phone off I tried to turn it back on, still plugged into the charger. I would hold the power button for around 5 to 7 seconds and the LG logo would flash but I did not feel the vibrate that normally accompanies powering on and the screen would flash LG logo again and then display the battery charging screen. Unplugged the charger and it did it again. Tried one more time and the phone vibrated and powered on as normal. I had something similar happen weeks ago so I think it may not be related to this specific rom.
 
  • Like
Reactions: tdm
tdm said:
Never on an official CM build. But I expect the devs here should take care of making OC kernels.
Click to expand...

I would have one out right now but none of my builds will boot for some reason. Has anything changed in your command line, tdm?
 
Left off charger overnight, dropped from 93% to 37%. Deep sleep for 5 hours, 192 MHz for 3 hours. WiFi was on, nothing else was running.
 
  • Like
Reactions: tdm
tdm said:
Never on an official CM build. But I expect the devs here should take care of making OC kernels.
Click to expand...

Nice...I wonder if the "not as smooth as...." could be because we are at 1512 vs 1674.....I have noticed some things stutter but they are not show stoppers for me so I still think it is almost as smooove as buttah...
 
sosaudio1 said:
Nice...I wonder if the "not as smooth as...." could be because we are at 1512 vs 1674.....I have noticed some things stutter but they are not show stoppers for me so I still think it is almost as smooove as buttah...
Click to expand...

I had mine set to 1512 on CM10.1 and it was still faster. Just takes things longer to open, screen seems less sensitive, etc.
 
tdm said:
What is typical for your device on other ROMs (especially Q-CM10.1)?
Click to expand...

On CM10.1 it was really good, maybe 5%-10% drop at the most, steady deep sleep with WiFi always on. I had been using DS Battery Saver on CM10 but never needed it on CM10.1.
 
  • Like
Reactions: tdm
More BT info:

I lost BT connection to my headset, it just disconnected on it's own, checked the phone and BT was off. I tried to turn it on from quick settings and the regular settings, nothing.

I have two cell phones paired with my headset at the same time.
HTC Thunderbolt and LG Spectrum. Headset is Plantronics Voyager HD PRO.

BT worked fine paired with both phones on 10.1.

Looks like BT might need a tweek, still running PRE4 :0)
 
Big three wipe before install of pre4 and have the unknown baseband issue. Tried dirty flashing pre4 over itself, still unknown.

No signal issue and shows I am on Verizon's network.

Since trying pre3 and pre4, I have not lost 4G data even in places q-cm10.1 and q-cm10 did lose 4G towers (mainly the mountain I drive around to get to work)

Edit: MMS and SMS works, streaming YouTube in HD works, Talk works, syncing gmail account on clean flash works, I got first GPS lock in 21 sec and after initial lock 6.72sec using z-device test app at 4m error (living in a desert means no clouds to interfere)
 
  • Like
Reactions: tdm
hayneskr said:
More BT info:

I lost BT connection to my headset, it just disconnected on it's own, checked the phone and BT was off. I tried to turn it on from quick settings and the regular settings, nothing.

I have two cell phones paired with my headset at the same time.
HTC Thunderbolt and LG Spectrum. Headset is Plantronics Voyager HD PRO.

BT worked fine paired with both phones on 10.1.

Looks like BT might need a tweek, still running PRE4 :0)
Click to expand...
Clean install wiped all coming from beta 4 and having the same issue with BT turning itself off and then refusing to turn back on until I reboot. Just FYI

If it matters, paired with a Jawbone icon headset. Call audio, media audio, and device io (jawbone companion] all work... Until it shuts down
 
After I did the dirty flash something went wrong. Lost GPS. Tried nand backup of q-CM10.1 still no lock. Used pimp my ROM and downloaded US gpsconfig file got initial lock at 15sec and every lock after that was under 5sec. Wish I were at home to get logs of why I lost GPS. Probably just a cwm error and nothing to do with the ROM.

Edit: lock on pre4 after fixing GPS issue
 
Nokoko said:
Left off charger overnight, dropped from 93% to 37%. Deep sleep for 5 hours, 192 MHz for 3 hours. WiFi was on, nothing else was running.
Click to expand...

Seems like im getting some crazy battery drain too.

Installed pre4 right before I left for work this morning. I keep my phone in airplane mode all day at work. Went from 100% battery to 55% in 8h 43m. 8h 3m was spent in deep sleep. 7 hours ESD spent in airplane mode with the screen off. About an hour was spent with the screen off and 4g connected while driving to work.

Typically I only see 10-15% battery loss with this type of use not 45%.

Not sure what's up there...

Sent from my VS920 4G using Tapatalk 2
 
Anyone seeing big battery drains, can you try to figure out what's causing the wakes? Maybe use BetterBatteryStats?

If any devs are seeing the baseband Unknown string, please try to track it down. I suspect it's a race condition. The script to set the baseband string is init.qcom.baseband.sh. It should be run on dev.bootcomplete but maybe that's not the correct place. Make sure it actually runs and see if there's anything that interferes with it. I'll do some testing and also try to look for a way to get it set via the RIL (which is the normal way).
 
Guessing something went wonky with my phone or something.

GPS refused to lock for the last two days. With the CM10.1 Pre releases in this thread. Odd, since it had been working fine in QCM10.1 betas.

Figuring that perhaps I messed something up, since my baseband also reports as unknown. I cab flashed back to V7, then took the V8 OTA just in case. BTW these are the basebands that stock reported:
v7 cab fresh - VS920ZV7-M8660A-AABQNSZM-3.6.2421
v8 ota - VS920ZV8-M8660A-AABQNSZM-3.6.2421
Definitely no change, besides the V8 in there.

Anyway, rooted, unlocked, wiped everything, reflashed pre-4. Still no GPS. Restored a stock nandroid and got a lock. Restored my pre-4 nandroid... GPS works fine now.

I thought we didn't need to get a lock in stock anymore before flashing with the GPS changes?

Anyway, just my experience. I know it was only like me and beezy that couldn't get GPS out of everyone here, so probably just some quirk we're both experiencing.
 
  • Like
Reactions: tdm
Don't know about the GPS that's beyond me since I refuse to let a locked boot loader on my phone. Just my personal preference as a hardcore open source enthusiast.

The change in baseband version indicates something has changed, if only the version string. I'm pleased to see the scraper reporting correctly... :)
 
tdm said:
Don't know about the GPS that's beyond me since I refuse to let a locked boot loader on my phone. Just my personal preference as a hardcore open source enthusiast.

The change in baseband version indicates something has changed, if only the version string. I'm pleased to see the scraper reporting correctly... :)
Click to expand...

Yeah, I wasn't too worried about the GPS either. Only 2 of us with an issue, and it's fixable on our end.

Unfortunately, that's my baseband from stock. CM10.1 is still reporting "Unknown" for me just like it was with the V7 baseband. I saw your post about the script and race condition... Unfortunately, I don't really know how to check when/if a script is running during boot. So I can't be much help there.

On a side note, I'll see if I can't rip my baseband out and toss it on a reply in the basebands thread since you're saying it did actually change.
 
I've had a t ime with my phone today. My home button kept breaking

I was on the pre3 and decided I missed the smoothness of the other cm10.1 and dirty flashed back and then my home buton broke. It worked at first but broke after making some changes so I tried dirty flashing again but it still didn't work. Then I tried dirty flashing pre3 and it still wouldn't work. So I did a full wipe and flash beta4 and during the process of getting everything setup it broke again. So I finally just went ahead and did another full wipe and I'm back on pre3.

Everything Is working now
 
You must log in or register to reply here.
Back
Top Bottom