p_razzi, is there any chance to test your 3g sim on other device?
Also, do you use any protected connections to corporate network?
Is there a chance that your 3g connection uses l2tp termination on corporate side?
Hi N0p,
I did as your advice:
- Flash v1.0
- Flash v1.1 test 5
- Do Dell Factory Reset,
- Let it boot,
- It will be boot again and stuck at DSC logo.
Regards,
---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------
Hi N0p,
Thanks for your help,
I will test v6 then back to you soon.
Thanks,
F/PrintK (1477): <2>[I2C]IRQ: 90 W2 NAK (63C8)
Invalid debug info stream. class Lcom/android/server/am/ActivityManagerService;; proto (ILjava/lang/String;Landroid/os/IBinder;Ljava/lang/String;ILandroid/content/Intent;Ljava/lang/String;I)Landroid/content/IIntentSender;
p_razzi, is there any chance to test your 3g sim on other device?
Also, do you use any protected connections to corporate network?
Is there a chance that your 3g connection uses l2tp termination on corporate side?
Running DSC 1.1 test 2 with Pdroid patch 1.32. Although pdroid app detects the patch, if you turn on "Notify on data access" in the preferences if fails to deliver any notifications. An example of a working notification can be found here blocking the device ID. http://www.privilege-car.de/xda/3.png
Catlog shows many fatal errorsLog: http://pastebin.com/ByYuc2hYCode:F/PrintK (1477): <2>[I2C]IRQ: 90 W2 NAK (63C8)
Now I tried to run DSC 1.1 test 2 with a Pdroid patch 1.27 that I made, and data access notifications work fine now, but I get random reboots. Catlog shows many debug info stream errors.Code:Invalid debug info stream. class Lcom/android/server/am/ActivityManagerService;; proto (ILjava/lang/String;Landroid/os/IBinder;Ljava/lang/String;ILandroid/content/Intent;Ljava/lang/String;I)Landroid/content/IIntentSender;
Log
http://pastebin.com/98fKvLDN
Hi n0p,
I'm able to install 1.1 b6 on mine. It's working perfectly now.
Thanks for your effort!
Thanks,
Not tried any SIM switching yet, but this from my home network:
1. Working 3G Connection
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.210.9.108 0.0.0.0 255.255.255.252 U 0 0 0 rmnet0
0.0.0.0 10.210.9.109 0.0.0.0 UG 0 0 0 rmnet0
2. Working WiFi Connection
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
3. Switch on WiFi from a working 3G Connection
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0
4. Switch on 3G from a working WiFi Connection (ie switch off WiFi)
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.88.56.156 0.0.0.0 255.255.255.252 U 0 0 0 rmnet0
You can see that there are matching entries on the working connections, but no entries for the non-working ones. Is this a symptom or a cause?
Introducing: one and only Mugen Power batteries config tool - DSC Mugen Power config.
Fixes battery gauge, calculating percent from battery supplied voltage.
Controls imlemented in Phoenix Universal kernel battery parameters.
Check it out.
More - this tool is completely ROM independent and can be used in any GB ROM that uses Phoenix Universal kernel.
I'll update CM7/MIUI Phenix kernel release thread in a couple of days.
--
http://n0p.8bit.fm/streak/updDSCv1.1-test6.zip
Mirror @ khoacoi:
http://www.littlemaruko.com/Nopteam/updDSCv1.1-test6.zip
--
Sergei,
DSC Team.
Kartikaye, you can take and install DSC_Mugen.apk from update, if I recall correctly, you already using Phoenix Universal kernel (it's required for this tool).
Also, take Mugen postboot part (it has a corresponding comment) and add it to your current postboot script
Sergei I downloaded the zip file and took the necessary files. Just want to know what enhancements are there in the camera.apk which is there. Cause the current camera quality is not what it used to be when i am on the froyo. Is there a way to remove the compression option as there is a lot of pixalation and the pic taken looks like a water colour painting.
Have you tried putting
ro.media.enc.jpeg.quality=100
into build.prop?
I think tx power is already on max anyway.
You may add that line to any place of build.prop.
About various hacks and fixes in build.prop - i've analyzed ril libraries and dialer - a lot of "recommended" options don't have a corresponding part there, so they simply don't work.
And I'm unsure of that quality setting, as I haven't a possibility now to check.
Ok i have added the string and have also made the mugen settings as per the mugen app. I have set the permission to the init.dsc.set_mugen as rwx - rx - rx , I hope that is correct..??
Correct. And don't forget to add
#Mugen Power batteries support
/system/etc/init.dsc.set_mugen.sh `cat /data/dsc.mugen_config`
to postboot, so it'll be executed on device start.
fastboot -i 0x413c flash recovery recovery407.img
fastboot -i 0x413c reboot
fastboot -i 0x413c flash recovery recoverysm.img
fastboot -i 0x413c reboot
adb logcat -d >mylog.txt
adb logcat >mylog.txt