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

Root CM 10.2 Nightlies Discussion

After replying email I saw a loss WiFi connection. Then I waited for reconnection. Suddenly LG logo appeared. This was not rebooting itself. Just messed up and popped up ANR message.
 

Attachments

  • froze909_014152.jpg
    froze909_014152.jpg
    61.1 KB · Views: 94
  • anr909_014223.jpg
    anr909_014223.jpg
    73.1 KB · Views: 106
Yeah I saw that screen, it happened to me while I was switching to full screen youtube videos, the phone eventually rebooted itself after 20 odd some youtube videos.
 
I'll try to explain it in Windows terms which is what a lot of people understand.

Think of Win95, WinXP, and Win7.

Win95 (GB) is light and smooth. It ran well on low powered machines, but didn't come with many features. It was ahead of the game as far as anything else out at the time. You could run this on a newer machine, but you'd never get the full potential out of the machine as the OS was not optimized for dual cores or better.

WinXP (ICS) was a code re-write that gave it more features, but also required a stronger machine and a different underlying kernel. Items written for XP didn't work on Win95 because you were missing access to certain system files in a lot of cases, but running Win95 programs on XP was more or less easy.

Win7 (JB) was a smoothing of the code, speeding up of the sub system (project Butter on android) and listening to what the public wanted and merging that into the source code and you still get backwards compatibility.

Hopefully that makes sense to you.

If you want the tech details of what was added with each release, I would look here:
Android version history - Wikipedia, the free encyclopedia

It makes plenty of sense, thanks, I really enjoyed reading through the history of all the versions. (ZZZZZZZ, waking up to go to work)One thing is missing from this explanation however. The hardware.

As windows grew, between XP and 7, there were several versions that were less than useful, 2000, vista (yuk), and lots of service packs. But as the programming caught up with the hardware, you could replace your processor with a faster one, install more RAM, etc.

With our phones, you can't do that. You can get a larger capacity SD card, but that's about it. So as the program grows, with more and more features, and functions are loaded into the memory, it has to affect performance doesn't it? And even though they are listening to what the public wants, and trying to give it to them, they are also doing their best to keep THEIR priorities in order (play store). Always have to follow the money trail.....

Which reminds me of another question. Can android read/write to the SD card the same way windows can when more memory is needed? Like a pagefile?

I'll leave this subject alone, as I am aware it really is off topic for this thread. I will continue to try new roms, but for right now, I personally see a debloated deodexed rom as a great achievement!

Every time I look at my phone, I remember all the crap that has been removed, many thanks to all of you guys/girls out there.

Bottom line is we have to pay what I feel are outrageous fees for service, AND they force feed us a bunch of crap on our phones to boot, it really makes me ANGRY. Being able to fight back in some way, any way, is enough for me at this time. :D
 
It makes plenty of sense, thanks, I really enjoyed reading through the history of all the versions. (ZZZZZZZ, waking up to go to work)One thing is missing from this explanation however. The hardware.

As windows grew, between XP and 7, there were several versions that were less than useful, 2000, vista (yuk), and lots of service packs. But as the programming caught up with the hardware, you could replace your processor with a faster one, install more RAM, etc.

With our phones, you can't do that. You can get a larger capacity SD card, but that's about it. So as the program grows, with more and more features, and functions are loaded into the memory, it has to affect performance doesn't it? And even though they are listening to what the public wants, and trying to give it to them, they are also doing their best to keep THEIR priorities in order (play store). Always have to follow the money trail.....

Which reminds me of another question. Can android read/write to the SD card the same way windows can when more memory is needed? Like a pagefile?

I'll leave this subject alone, as I am aware it really is off topic for this thread. I will continue to try new roms, but for right now, I personally see a debloated deodexed rom as a great achievement!

Every time I look at my phone, I remember all the crap that has been removed, many thanks to all of you guys/girls out there.

Bottom line is we have to pay what I feel are outrageous fees for service, AND they force feed us a bunch of crap on our phones to boot, it really makes me ANGRY. Being able to fight back in some way, any way, is enough for me at this time. :D
I'd compare our phones more to having a laptop then a desktop though if you're comparing upgrade ability. The nice thing about android, is that it handles RAM a bit more intelligently then Windows does. You can also set how many back round processes you want to allow to stay open at any point in time. Unfortunately, like windows, when you uninstall a program, it does leave a bit of itself behind in /data. For this reason, I tend to use Titanium backup to wipe the data for the program and then uninstall the program. It gives a cleaner result. You'll still have any files from the program left on your SD card. Now android is based on linux, so in theory you could set up a swap partition, but it would probably be slow as all could be and you'd burn out our SD card extremely quick from all the read/writes.
As for all the minor releases of windows, there were also minor android releases as well. 2.2 (Win98), 2.3 (WinMe), 3.0 (Win2k), 4.0.4(Vista). I just matched up the major releases that people would have used to make my analogy make sense in the original post.
For carrier bloat, it makes sense. How many people ever pay full retail for their phone? If you did, you'd have a better case for having less bloat on the phone. That's why I'm waiting for the Moto X Dev Edition as that will be my next phone. I don't agree with how much carriers charge, but just like Ma Bell in the 80's, the US let carriers become to big and less competition.

OK, so back to the topic at hand. Battery life on this ROM is impressive. 30% drop in 15hrs is better than I've seen of a base setup. I'm having random reboot issues, but I have a feeling it from the program Noom that I run. I turned off the pedometer function yesterday and my lockups and reboots went away. I will be keeping an eye on this. Also, having the same issue of only having metric on the CLock screen. My HD Widgets on my home screen work fine.
 
I'm thinking that the metric on cLock is related to trebuchet, since I am using adw and its displayed correctly for me.
 
I'd compare our phones more to having a laptop then a desktop though if you're comparing upgrade ability. The nice thing about android, is that it handles RAM a bit more intelligently then Windows does. You can also set how many back round processes you want to allow to stay open at any point in time. Unfortunately, like windows, when you uninstall a program, it does leave a bit of itself behind in /data. For this reason, I tend to use Titanium backup to wipe the data for the program and then uninstall the program. It gives a cleaner result. You'll still have any files from the program left on your SD card. Now android is based on linux, so in theory you could set up a swap partition, but it would probably be slow as all could be and you'd burn out our SD card extremely quick from all the read/writes.
As for all the minor releases of windows, there were also minor android releases as well. 2.2 (Win98), 2.3 (WinMe), 3.0 (Win2k), 4.0.4(Vista). I just matched up the major releases that people would have used to make my analogy make sense in the original post.
For carrier bloat, it makes sense. How many people ever pay full retail for their phone? If you did, you'd have a better case for having less bloat on the phone. That's why I'm waiting for the Moto X Dev Edition as that will be my next phone. I don't agree with how much carriers charge, but just like Ma Bell in the 80's, the US let carriers become to big and less competition.

OK, so back to the topic at hand. Battery life on this ROM is impressive. 30% drop in 15hrs is better than I've seen of a base setup. I'm having random reboot issues, but I have a feeling it from the program Noom that I run. I turned off the pedometer function yesterday and my lockups and reboots went away. I will be keeping an eye on this. Also, having the same issue of only having metric on the CLock screen. My HD Widgets on my home screen work fine.

OK I PROMISE I will end this discussion after this.....LOL One last thing. It is true that we rarely pay full price for the phone. I want to mention though that if you found out the true cost to the carrier of the physical device, you may just change your mind about the bloat. (MY LG Spectrum says VERIZON across the top of it, even though THEY did not engineer or construct the device).
In any case, the amount of bloat, the way these bloat programs run, (trying to make customers exceed their low cost data plan, and hit them with a fee), and the monthly charges for having the service in the first place, more than justify fighting back to remove all that bloat. We are being hosed by all of these companies (in my humble opinion), each and every month. OK I'm done, thanks for listening. I feel better now......
 
If you like cLock but want more functionality, try DashClock. It's free and has tons of extra features compared to cLock. I highly recommend it.

EDIT: klembo, if you really want to steer clear of the bloatware, use a Nexus device. The only downside to that is the newest Nexus device that works with VZW is the Galaxy Nexus and it's 2 years old now.
 
OK I PROMISE I will end this discussion after this.....LOL One last thing. It is true that we rarely pay full price for the phone. I want to mention though that if you found out the true cost to the carrier of the physical device, you may just change your mind about the bloat. (MY LG Spectrum says VERIZON across the top of it, even though THEY did not engineer or construct the device).
In any case, the amount of bloat, the way these bloat programs run, (trying to make customers exceed their low cost data plan, and hit them with a fee), and the monthly charges for having the service in the first place, more than justify fighting back to remove all that bloat. We are being hosed by all of these companies (in my humble opinion), each and every month. OK I'm done, thanks for listening. I feel better now......
+1
If you buy a car the dealer/maker can't put ads on the car, it is yours even though you are paying it off, but not phones I find that funny. And yes you can ask the dealer to remove his or her logo from the automobile and they have to.
As for all the minor releases of windows, there were also minor android releases as well. 2.2 (Win98), 2.3 (WinMe), 3.0 (Win2k), 4.0.4(Vista). I just matched up the major releases that people would have used to make my analogy make sense in the original post.
For carrier bloat, it makes sense. How many people ever pay full retail for their phone? If you did, you'd have a better case for having less bloat on the phone. That's why I'm waiting for the Moto X Dev Edition as that will be my next phone. I don't agree with how much carriers charge, but just like Ma Bell in the 80's, the US let carriers become to big and less competition.
Linux is not Winders, the Kernel is the biggest thing with Linux the GUI is just fluff on top of it.
You do realize that you pay full price for a subsidized device in that your monthly cost are based upon the repayment of the subsidize. Whether you like or not you pay full price and then some.
 
If you like cLock but want more functionality, try DashClock. It's free and has tons of extra features compared to cLock. I highly recommend it.

EDIT: klembo, if you really want to steer clear of the bloatware, use a Nexus device. The only downside to that is the newest Nexus device that works with VZW is the Galaxy Nexus and it's 2 years old now.

No that's OK really. The Spectrum I have is my first phone of this type, and I am satisfied. All this ranting on my part stems from philosophical musings I have from time to time, related to how and why things happen the way they do.

Disclaimer: I am NOT in any way attempting to belittle the fine work done in this forum. :smokingsomb: I have A LOT of respect for many of the members here, and their abilities. I guess I just have a different perspective, as far as roms go anyway. It is a lot of fun trying ALL of them out. Experience is the best teacher I guess, and perhaps with time things will become clearer.
 
Wow, can someone move this discussion to another thread. I keep checking back for a discussion on 10.2 and I keep finding, this.
 
Wow, can someone move this discussion to another thread. I keep checking back for a discussion on 10.2 and I keep finding, this.
Sorry, I didn't really expect it to grow like this. We all are waiting for 10.2. I took advantage since many of the experienced devs were available here. Sorry.............:D
 
I wonder if just flashing the radios zip during the 10.2 initial flash would result in 4G.

So maybe a process would be wipe dv/wipe cache/wipe data/install 10.2/install 4.3 Gapps/install radios - reboot
 
Sorry I've been busy. I'll request some data and provide a test replacement for the telephony code tomorrow.

@sosaudio1 this has nothing to do with the baseband it's an issue in the android telephony code.
 
It's working great for me, better than the latest CM10.1 stable :-P I dirty flashed, have working 4G and no reboots.
 
Sorry I've been busy. I'll request some data and provide a test replacement for the telephony code tomorrow.

@sosaudio1 this has nothing to do with the baseband it's an issue in the android telephony code.

Killer just wondered if that would have helped thanks tdm
 
A few issues I had and some things that fixed it...

First off, my order of install:
Booted to recovery
Wiped all but SD
Installed CM10.1 (Latest stable build)
Rebooted (No Gapps, I figured the less crap installed the better.)
OS booted, no setup due to no gapps. 3G acquired signal.
Rebooted to recovery (I'm using TWRP btw)
Installed CM10.2 test build with the latest gapps for it.
Rebooted, Android 4.3 with data.

So now the findings...

FC on apps and phone gets warm/battery cranks:
Checking into the performance area of settings, I checked out the frequency and governor. Default governor is ondemand. Default max frequency 1512.
For some reason, "Current CPU Frequency" was just cranked at 1512, constant. I'm not sure why. I changed the governor to Interactive and dropped the max frequency to 1458. My FC's and instability went away and the frequency started varying quite a bit and sitting at minimum while at the screen with the occasional jump. Not sure what differs, just giving experience.

Bluetooth:
I use BT for my car stereo ALL THE TIME. I stream from my phone to it every car ride. How my stereo works is it never tells the phone it's a stereo device until you try playing on the Bluetooth section of the stereo. Otherwise, it only reads as a headset for phone calls. I tried pairing from the Bluetooth music portion of the stereo, it wouldn't pair and I had the same BT issues as 10.1. I rebooted. I paired it from just the phone section on the stereo, it paired just fine. I then went to play from the music side of the stereo. Stereo speaker appeared as a function in the pairing options and I got iHeartRadio playing. I shut off the car, waited 5 minutes, turned it back on, and it auto-paired. I then hit play, and it played in the car. Unfortunately, on lunch, I got in my car and the stereo wouldn't pair. I had to reboot the phone for it to pair.
So in a nutshell, it appears bluetooth is plagued with the same problems we've had the last few versions of Android. This is sadface because it's a necessity for me.

Lock screen gesture sensitivity:
Sometimes when I go to unlock my screen I try to swipe from the center to the right like a typical unlock. But for some reason, the notification window comes down instead. I do absolutely nothing differently. When it gets in this finicky state, I have to be super-careful to only use the tip of my thumb and come straight down onto it to unlock.
The oddness of this is that it only happens once in a while. Not sure what's up.

Default phone shortcut not working:
The default shortcut on trebuchet when I first entered 10.2 for the phone says the application is no longer installed. I simply deleted that shortcut and put the other one in and it worked.
Obviously not anything major but more of a "Da F*ck??" Possibly result of the dirty flash?

Lag on Trebuchet icon dragging:
As it says, when dragging shortcuts around Trebuchet's home screen, there's lag. Not terribly significant, but some.

In honesty, so far, these are the only things. It's been working great so far (For all of the 1 day I've used it.) If you don't rely on bluetooth for what I do (it may actually work for simple phone calls) then this may be a great ROM for ya!
 
So the apn database is: /data/data/com.android.providers.telephony/databases/telephony.db

I'll need a copy of a working database on cm10.2 (from a dirty flash) and a non-working database on cm-10.2 (from a clean flash) to compare.

I'm trying to find place(s) in the code that may be causing this.
 
So the apn database is: /data/data/com.android.providers.telephony/databases/telephony.db

I'll need a copy of a working database on cm10.2 (from a dirty flash) and a non-working database on cm-10.2 (from a clean flash) to compare.

I'm trying to find place(s) in the code that may be causing this.

Here is a working one.

I should be able to get a nonworking one in 1.5 hrs if no one beats me to it.
 

Attachments

For me, replacing telephony.db caused phone to crash and then a bootloop.

It is possible that permissions might have needed reset on the file, I didn't check them.
 
  • Like
Reactions: tdm
For me, replacing telephony.db caused phone to crash and then a bootloop.

It is possible that permissions might have needed reset on the file, I didn't check them.

Permissions is a definite possibility for causing the crash. Try opening a terminal on the phone and doing the following:
Code:
su
chmod 755 /path/to/telephony.db

Then, post back and tell us your results. Assuming, of course, that you can access a terminal with the different telephony file. If someone doesn't beat me to it, I'll try and whip up a flashable zip to install the working telephony.db
 
Just me or is charging horribly slow on aftermarket charger? And extended battery. Feels like icy fusion is twice as fast
 
Back
Top Bottom