So, I have succeeded in porting the Fascinates 2.3.5. stock rom to our Continuum however in the "about phone" section it still says 2.3.3. I checked the build.prop and it says 2.3.5. just not sure why it didnt change the firmware version. The port boots just fine and works well as far as I can tell.. Any ideas?
ticker in port?
If your using our kernel 2.3.3 is in the initramfs
Couldn't tell u with out seeing...
Sent from my SPH-M580BST using Tapatalk 2
Yup ticker is working just fine... However I did a nandroid restore and accidentally did a full restore instead of just data lol, it set me back to the original EG04 and now when I try to flash my port it bootloops.. LOL I dont know if I just got lucky or what... Ill keep trying to fix it..
Well here is where it is crashing in logcat...
I/SystemServer( 108): Vibrator Service
W/dalvikvm( 108): threadid=20: thread exiting with uncaught exception (group=0x40015578)
E/ActivityThread( 108): Failed to find provider info for settings
E/VibratorService( 108): ImmVibeJ loading failed!! : java.lang.NullPointerException
E/ActivityThread( 108): Failed to find provider info for settings
E/ ( 108): Dumpstate > /data/log/dumpstate_sys_error
E/AndroidRuntime( 108): *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService
E/AndroidRuntime( 108): java.lang.NullPointerException
E/AndroidRuntime( 108): at android.content.ContentQueryMap.<init>(ContentQueryMap.java:65)
E/AndroidRuntime( 108): at com.android.server.PowerManagerService.initInThread(PowerManagerService.java:710)
E/AndroidRuntime( 108): at com.android.server.PowerManagerService$2.onLooperPrepared(PowerManagerService.java:635)
E/AndroidRuntime( 108): at android.os.HandlerThread.run(HandlerThread.java:59)
I/dumpstate( 207): begin
E/VoldCmdListener( 62): asec list
D/BatteryService( 108): update start
D/BatteryService( 108): updateBattery level:76 scale:100 status:2 health:2 present:true voltage: 4027 temperature: 320 technology: Li-ion AC powered:false USB powered:true icon:17302234
I/dumpstate( 207): done
D/BatteryService( 108): update start
D/BatteryService( 108): updateBattery level:77 scale:100 status:2 health:2 present:true voltage: 4047 temperature: 320 technology: Li-ion AC powered:false USB powered:true icon:17302234
I/Process ( 108): Sending signal. PID: 108 SIG: 9
E/AndroidRuntime( 108): Error reporting crash
E/AndroidRuntime( 108): java.lang.NullPointerException
E/AndroidRuntime( 108): at android.os.DropBoxManager.isTagEnabled(DropBoxManager.java:288)
E/AndroidRuntime( 108): at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:6811)
E/AndroidRuntime( 108): at com.android.server.am.ActivityManagerService.handleApplicationCrash(ActivityManagerService.java:6528)
E/AndroidRuntime( 108): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:82)
E/AndroidRuntime( 108): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
E/AndroidRuntime( 108): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)
D/BootAnimation( 118): SurfaceFlinger died, exiting...
I/ServiceManager( 61): service 'SurfaceFlinger' died
I/ServiceManager( 61): service 'usagestats' died
I/ServiceManager( 61): service 'batteryinfo' died
I/ServiceManager( 61): service 'sensorservice' died
I/ServiceManager( 61): service 'entropy' died
I/ServiceManager( 61): service 'power' died
I/ServiceManager( 61): service 'telephony.registry' died
I/ServiceManager( 61): service 'permission' died
I/ServiceManager( 61): service 'meminfo' died
I/ServiceManager( 61): service 'activity' died
I/ServiceManager( 61): service 'content' died
I/ServiceManager( 61): service 'package' died
I/ServiceManager( 61): service 'cpuinfo' died
I/ServiceManager( 61): service 'account' died
I/ServiceManager( 61): service 'battery' died
I/ServiceManager( 61): service 'hardware' died
I/ServiceManager( 61): service 'vibrator' died
E/installd( 72): eof
E/installd( 72): failed to read size
I/installd( 72): closing connection
I/Zygote ( 69): Exit zygote because system server (108) has terminated
W/AudioSystem( 119): AudioFlinger server died!
W/IMediaDeathNotifier( 119): media server died
W/AudioSystem( 119): AudioPolicyService server died!
I/ServiceManager( 61): service 'media.audio_flinger' died
I/ServiceManager( 61): service 'media.player' died
I/ServiceManager( 61): service 'media.camera' died
I/ServiceManager( 61): service 'media.audio_policy' died
I believe the issue is with PowerManagerService.java... After some searching this is located in Services.jar but I have no idea where to find this..
I dont understand how I got this to boot once and now it won't anymore... Very frustrating...
This is the solution someone else found when installing Cyanogenmod and getting the same failure.
"Problem Solved!
It would seem that this is behavior one might expect if one has not cleared the personal data in ClockworkMod.
I had already cleared the Cache, but had not cleared the personal data. Having done so, and reloading the cm_nightly zip, all went well.
I am very happy with my newly CyanogenModded MyTouch G4. Thanks to all who took a hand in the hard work."
However I have cleared damn near everything and am still getting the failure...
Did u factory reset?
What zImage are you using?
There might be other modules needed...
Sent from my SPH-M580BST using Tapatalk 2
ciscogee said:
Did u factory reset?
What zImage are you using?
There might be other modules needed...
Sent from my SPH-M580BST using Tapatalk 2
Click to expand...
Click to collapse
Yeah I did factory reset, wipe cache, format cache, wipe dalvik. I am using our EG04 zImage. Not sure about the modules. Its just so damn irritating that I got it to boot once.. Im an idiot for not paying attention to my restore. Not sure where I can go from here. I've rebuilt the rom like 20 times with the same results. I can upload it if you wanna take a look at it.
well im assuming that the port didnt take the first time based on you saying the ticker was intact working cause the ported framework would not have any ref to making anything show up down there and screen res (actual display dimensions) is dif and would overlap like joshkoss' port and dif modules like they have fm radio, blah blah blah
sure send me a link and ill take a look
Related
I started getting an error code on my mogul today every time I try to connect to the internet. I have never gotten it before and have not found any answer anywhere on the net. I am currently on hold with Sprint customer service and have been for 1.5 hours now.
Anyone know what this "error code 78" means?
so after about 4 hours on the phone with Sprint tech support, lost count of the transfers... Sprint gave up and did not have an explanation. About 30 minutes later the EVDO service started working again. About 2 hours later I got a call from the next level tech, I explained that it was working and thanked him to which he responded, "Well I don't think we did anything, but have a great day..."
Moral of the story, if you see this error code, just wait it out.
I had an issue with my RIL crashing after a while due to "Insufficient Resources" which caused the text message I was trying to send to fail. This error occurred after about 2 days of use without a reset. When I rebooted and checked the Battery/CPU/Partial Wake-Lock usage in spare parts, it said that the dialer had been running the whole time(Part of the poor batter life issue).
Has anyone else had this problem?
I think the problems are probably related. Something in the dialer has a memory leak. Part of that leak involves the continuous wake-lock request. The other part has to due with it just eating resources up. All of the problems stem from the TXT messaging part of the dialer.
Once that is fixed it should be fine, I hope.
I recently started noticing constant 3G activity which of course would drain my battery in a matter of a couple of hours. Needless to say it was annoying and so I was trying to track down what connections are being made.
I tried running netstat from the terminal thinking it would show me what all open connections there are, but it doesnt seem to work, or at least it didnt show any open connections to the internet.
I eventually figured out what was causing all the activity by killing services one by one and the activity stopped when I killed the Sync service. That's when I remembered the password had expired on one of my Exchange accounts. After correcting that, the activity stopped and all is well now. I'm running stock DI18. Is this normal for the activity to be pegged like that for an expired password?
Also is there a reason netstat doesnt show open connections over 3G? I havent tested if it shows connections over wifi yet.
http://forum.xda-developers.com/showthread.php?t=798090
Take a look at my post from some time ago about this issue. I never got this figured out. At least it doesn't happen on DK28, so I suspect that it won't happen whatever build gets officially released.
Does anyone know what this FC is or what's causing it? It says, "Unfortunately, Context Service has stopped working." When I press ok it just keeps coming up.
Unfortunately, Context Service has stopped working.
Hey, you ever figure this problem out? I'm having the same issue with my S5. It just keeps popping up. Sometimes back to back like 30 times.. It got better, but now it seems like it's getting worse. I'd rather not factory reset my device. I'm rooted on stock 4.4.2. It's been rooted since it came out. So it's been a while. It's been performing perfectly for many months.. But now this is happening. What's the deal?! Any help would be appreciated. Thanks in advance.
-Christopher
I switched it with a context service apk from another rom
Hi all,
Just a heads up as a word of caution as just received the following text message from Three UK:
"Hi, you may have difficulties calling 999 or 112 from your LG device due to a fault with LG's software. We will inform you as soon as the problem has been fixed. Until then, please call 999 or 112 from a non-LG phone. If you can't, then switch your LG phone off and on again, then redial 999 or 112. From Three."
I have spoken with Three tech support and have confirmed the text message is legit.
Looks like a new update very soon.
Sent from my LG-H815 using Tapatalk