21.03.2014 RELEASE #4 UPDATE
Here is first ever CM for LG D605 (Optimus L9 II).
This is unofficial ROM and might have some serious faults, if this breaks your phone or they fire you from your job because alarm didn't start it will be your own fault since you have installed it. You have been warned!
The installation procedure was tested with unbranded phone (OPEN_EU variant). This might not work with branded ROM (but it would be good if someone check it).
Sources can be found at:
https://github.com/Varcain/android_kernel_lge_d605
https://github.com/Varcain/android_device_lge_d605
Things that don't work and won't be included in this ROM by default (possible enable by porting stock apps):
- FM radio
- IR port
Things that I already know that don't work at all or are bugged:
- NFC (no support at all yet)
- Manual service network selection (only auto supported right now)
- SIM card contact/SMS reading
For best battery life keep bluetooth off if you are not using it. It will keep constant wakelock if left on right now
NEWEST RELEASE #4
- Added USB tethering
- Added Bluetooth tethering
- Working move to sd-card function (but MTP on internal memory is disabled, external SD card is now mandatory)
- Vibration patterns tuning
- Correct WLAN and Bluetooth MAC addresses should be used now
CHANGES FROM RELEASE #3
- Fixed first call with no voice bug
- Fixed incoming call volumes
CHANGES FROM RELEASE #2
- Fixed voice call volume
- Fixed mute microphone option during calls
NEWEST ROM RELEASE #4:
d605_cm10_v4.zip - 164.61 MB
GAPPS:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Old releases:
release #3:
http://d-h.st/Zr4
How to install:
1. Flash CWM (from here: http://forum.xda-developers.com/showthread.php?p=50407619)
2. Download the ROM and gapps to sdcard
3. Boot to recovery
4. Wipe all userdata
5. Install CyanogenMod first then gapps
6. Reboot.
Now wait for CM to boot... (first boot will take longer as always).
For reporting bugs/problems:
- Send me logcat output (it would be good to have "logcat -b radio" output too if this is related to sim card/radio)
- Send me dmesg output
If you experience reboot (kernel panic most likely) then send me contents of /proc/last_kmsg (you have to copy this right after reboot, you can do it from terminal application if you don't have access to PC with adb at that time).
Reserve for info.
Thanks Varcain!
Beginning installation right now.
----------------------------------------EDIT---------------------------------------------
Help: http://forum.xda-developers.com/showpost.php?p=50007962&postcount=318
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
TaZRAge said:
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
Click to expand...
Click to collapse
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
How to install:
Unzip contents, boot your phone to stock ROM, connect via USB with USB debugging mode on, install adb (if you don't have it yet), then adb push all unzipped files to /data/local/tmp (for example adb push ./system.tar /data/local/tmp). After that enter adb shell, issue "su" command and:
# cd /data/local/tmp
# chmod 777 clear_partitions.sh
# chmod 777 loki_flash
# chmod 777 system_update.sh
# mkdir mntpoint
# ./clear_partitions.sh
# ./loki_flash recovery rom.lok
# ./system_update.sh
After that locate your unzipped gapps and do the following (I assume gapps are unzipped directly in /storage/external_SD/Download
# cp -r /storage/external_SD/Download/system/* mntpoint/
# sync
# reboot recovery
Click to expand...
Click to collapse
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/sdcard1/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Varcain said:
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/external_SD/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Click to expand...
Click to collapse
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
TaZRAge said:
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
Click to expand...
Click to collapse
I made a typo, try /storage/sdcard1 instead of /storage/external_SD.
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
TaZRAge said:
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
Click to expand...
Click to collapse
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Varcain said:
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Click to expand...
Click to collapse
reinstalled everything
maybe I gona set up a dualboot on my PC too =)
made 2 screenshots from my adb shell with wel.... rare behaviour
but now it worked!
i have Gapps
Not rare behavior at all! You forgot Download directory in first screenshot and in second one it looks fine to me.
Varcain said:
Not rare behavior at all! You forgot Download directory in first screenshot and in second it looks fine to me.
Click to expand...
Click to collapse
*headpalm* no wonder it did not work
Well whatever.... that is one fine port =)
I am only missing my apps i installed via the amazon appmarket =D
And since its not really a ROM for daily use i will not install everything i have in my stock ROM
---------- Post added at 07:44 PM ---------- Previous post was at 07:14 PM ----------
Varcain said:
Just use the ROM like you normally would, compare with stock and if you find some anomalies report it in my ROM's thread, I will add them to bug list and hopefully fix in next release.
you can save logs to sd card and then load them from PC connection (I turned off MTP setting by default so it wont be detected as MTP device for file transfers, you need to turn it on in settings>storage>press menu> select MTP).
To do this from console app in phone:
logcat -d > /storage/sdcard1/logcat.txt
logcat -d -b radio > /storage/sdcard1/logcatradio.txt
dmesg > /storage/sdcard1/dmesg.txt
cat /proc/last_kmsg > /storage/sdcard1/lastkmsg.txt
Click to expand...
Click to collapse
This should be in here too!
And by the way, after activating MTP in the ROM i can use adb shell at my computer again!
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
TaZRAge said:
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
Click to expand...
Click to collapse
Settings>Launcher>Homescreen>Homescreens
TaZRAge said:
*headpalm*
Click to expand...
Click to collapse
Thanks again
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Varcain said:
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Click to expand...
Click to collapse
Works this way!
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
I connected my BT stereoheadset to listen to some music that doesn't sound like coming out a can....
Music via BT is no fun with this right now
I'm sitting next to my phone and the music comes interruptedly and sometimes with crackling sounds.
Gets even worse when i begin to experiment with the equalizer.
Next song comes flawless.... Ah display got disabled.
Screen back working and interruptions are back.
Controlls work perfect as i am used to (volume up + down + start/stop + next song + previous song do what they are supposed to do).
BT Speed to slow?
Disabled GPS now its better again.
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Varcain said:
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Click to expand...
Click to collapse
I tested it with stock many times before. Without problems like these.
And its sure I am in a radio-noisy environment. Around here are 4 wifi nets and the one i am in has 3 repeaters.
I had BT disabled on my computer during the test.
I will test it with a cable headset today, I don't have another BT headset.
Yet i had no other problems, bugs or errors!
Just install it!
First impression is VERY GOOD!
I think is faster than stock rom.
Minor problems with installation.
GApps works ok.
Known problem with camera.
Play some games, all run ok and FAST.
I think battery goes faster.
Install some themes, minor problems.
Basic Bluetooth ok.
That's all for now. I will play more later.
Thanks a lot Varcain! :victory:
I will upload new build in a moment and update the OP with it. There is major bug in first alpha release which causes constant wakelock (so the phone never goes into deep sleep). I managed to debug and fix it, please install new version.
Related
Hi,
Yesterday, my gTablet had some strange issues with sound. When I push the buttons to change the volume, I can only hear "Puck, puck, puck...". If I go to the volume settings and change the volume there, I can hear the test sound. I found later that I could only hear sounds coming from the system ( notification, ringtone, etc. ).
I was using the C&C v6 Rom. I tried to reset factory, reinstall the rom, reformat partition, tried stock rom, FlashBack 8.1, NVFlashed back to latest 1.1 stock rom and then installed VeganTab 5.1 but still no luck. It's also not working when I'm plugging my headphone. When I'm on Flashback, the sounds work but only with a headphone. Any idea on fixing this ? Or is it a hardware defect (I really hope not...) ? What's weird is that I can hear all the Android system sound but not video/music from Youtube or any mediaplayer...
Another user had the same issue
gitah said:
Hi,
Yesterday, my gTablet had some strange issues with sound. When I push the buttons to change the volume, I can only hear "Puck, puck, puck...". If I go to the volume settings and change the volume there, I can hear the test sound. I found later that I could only hear sounds coming from the system ( notification, ringtone, etc. ).
I was using the C&C v6 Rom. I tried to reset factory, reinstall the rom, reformat partition, tried stock rom, FlashBack 8.1, NVFlashed back to latest 1.1 stock rom and then installed VeganTab 5.1 but still no luck. It's also not working when I'm plugging my headphone. When I'm on Flashback, the sounds work but only with a headphone. Any idea on fixing this ? Or is it a hardware defect (I really hope not...) ? What's weird is that I can hear all the Android system sound but not video/music from Youtube or any mediaplayer...
Click to expand...
Click to collapse
Recently worked with another user that had the same problem..could hear notifications, but not music or video audio. The kicker was that he could hear music playing when the gtab goes into sleep mode (try it). Come out of sleep & the sound stops. Also has the same puck, puck, puck as you when you change the volume.
Last heard from him a week ago so I don't know if he got it resolved. He was also on 1.1 branch & it cropped up on him when he nvflashed back to 3588. He was going to try & nvflash to 1.2 branch 4349 & see if it made a difference
aabbondanza said:
Recently worked with another user that had the same problem..could hear notifications, but not music or video audio. The kicker was that he could hear music playing when the gtab goes into sleep mode (try it). Come out of sleep & the sound stops. Also has the same puck, puck, puck as you when you change the volume.
Last heard from him a week ago so I don't know if he got it resolved. He was also on 1.1 branch & it cropped up on him when he nvflashed back to 3588. He was going to try & nvflash to 1.2 branch 4349 & see if it made a difference
Click to expand...
Click to collapse
I tried what you said ( put the gtablet in sleep mode ) and yes I could hear the music playing.
gitah said:
Yesterday, my gTablet had some strange issues with sound. When I push the buttons to change the volume, I can only hear "Puck, puck, puck...". If I go to the volume settings and change the volume there, I can hear the test sound. I found later that I could only hear sounds coming from the system ( notification, ringtone, etc. ).
Click to expand...
Click to collapse
Interesting problem. Can you get me a logcat and a dmesg output from your system?
1. Reboot the gTab.
2. Once the system boots into the desktop, play with the volume settings (both HW and SW).
3. Then run these commands inside a Terminal Emulator app and attach the output:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]dmesg >/mnt/sdcard/dmesg.txt[/B] [I]Get kernel logs[/I]
# [B]logcat -d -v time >/mnt/sdcard/logcat.txt[/B] [I]Get Android system logs[/I]
gitah said:
I tried what you said ( put the gtablet in sleep mode ) and yes I could hear the music playing.
Click to expand...
Click to collapse
I got ahold of the other user with the same problem (sk01bim) and he has not resolved his issue either. I consulted with rajeevvp and he suggests capturing dmesg & logcat output to aid in troubleshooting.
See rajeevvp's instructions on the post above.
I'll try to have sk01bim do the same & post them here also.
Al
rajeevvp said:
Interesting problem. Can you get me a logcat and a dmesg output from your system?
1. Reboot the gTab.
2. Once the system boots into the desktop, play with the volume settings (both HW and SW).
3. Then run these commands inside a Terminal Emulator app and attach the output:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]dmesg >/mnt/sdcard/dmesg.txt[/B] [I]Get kernel logs[/I]
# [B]logcat -d -v time >/mnt/sdcard/logcat.txt[/B] [I]Get Android system logs[/I]
Click to expand...
Click to collapse
Here is a archive containing the two files ( files were too big so I had to zip them ) . Thank you for looking into this problem
gitah said:
Here is a archive containing the two files ( files were too big so I had to zip them ) . Thank you for looking into this problem
Click to expand...
Click to collapse
Wow! There are so many NAND flash-related errors in that dmesg.txt file that most of the relevant messages were ditched (the kernel keeps a fixed sized buffer for messages and old messages are discarded). Try getting me a dmesg while in ClockworkMod. It has a different kernel:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
I don't know if your NAND flash errors are causing your sound problems. We may have to fix them (if possible). However, try this first: Disable bluetooth, unplug wired headphones, then reboot the tablet and check sound. If there is still no sound, kill the abtfilt program if it's running and then check the sound again.
In a Terminal Emulator window:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]kill -9 $(busybox pidof abtfilt)[/B] [I]Kill abtfilt[/I]
# [B]/system/bin/ps | fgrep abtfilt[/B] [I]Check that it died[/I]
# [I]No output means it did[/I]
rajeevvp said:
Wow! There are so many NAND flash-related errors in that dmesg.txt file that most of the relevant messages were ditched (the kernel keeps a fixed sized buffer for messages and old messages are discarded). Try getting me a dmesg while in ClockworkMod. It has a different kernel:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
I don't know if your NAND flash errors are causing your sound problems. We may have to fix them (if possible). However, try this first: Disable bluetooth, unplug wired headphones, then reboot the tablet and check sound. If there is still no sound, kill the abtfilt program if it's running and then check the sound again.
In a Terminal Emulator window:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]kill -9 $(busybox pidof abtfilt)[/B] [I]Kill abtfilt[/I]
# [B]/system/bin/ps | fgrep abtfilt[/B] [I]Check that it died[/I]
# [I]No output means it did[/I]
Click to expand...
Click to collapse
Hmm...sorry but how do I do a dmesg while in CWM ? I tried to go to recovery then use adb but it couldn't find my device.
Also, my bluetooth wasn't on and I tried to kill abtfilt but it says that there's no such process.
gitah said:
Hmm...sorry but how do I do a dmesg while in CWM ? I tried to go to recovery then use adb but it couldn't find my device.
Click to expand...
Click to collapse
The command is already given above, but, you have to set up adb first. Go through this thread, or, a less hassle-free method is to use a Linux live CD.
Okay here's the dmesg while in CWM.
gitah said:
Okay here's the dmesg while in CWM.
Click to expand...
Click to collapse
No errors from the CWM kernel. We'll have to try the ROM kernel again--possibly a different one--to get the error messages (if any)... but, for the time being, do a quick test:
Remove the external SD card from its slot, power on the gTab and see if media playback comes back.
Still no sound after I removed my microsd card
gitah said:
Still no sound after I removed my microsd card
Click to expand...
Click to collapse
Can you install a different kernel and get the logs again (w/o micro sd card in slot)?
Ok...I just installed GHarmony for 1.2 bootloader and still no sound. BUT ! I tried something for the lulz, I ticked the Silent mode in the sound menu and guess what ? I get sound from Youtube... -.- If I untick the Silent mode, I get no sound...
I attached the logcat and dmesg when on Calkulin's rom and when on GHarmony. I tried to do the trick on Calkulin's Rom but it didn't work so I went back to GHarmony.
+1 -- you seem to have figured this out on your own.
Ughh...Now my trick is not working anymore and I DON'T why ?! I only installed the GAPPS for GHarmony and now whatever I set in the volume settings, I get no sound... I guess that the only thing to do now is to use Flashback 8.1 with headphones until something comes out of this :'(
gitah said:
Ughh...Now my trick is not working anymore and I DON'T why ?! I only installed the GAPPS for GHarmony and now whatever I set in the volume settings, I get no sound... I guess that the only thing to do now is to use Flashback 8.1 with headphones until something comes out of this :'(
Click to expand...
Click to collapse
I installed GHarmony yesterday, but, could not reproduce your problem. I can't even see any error messages from the kernel, so I don't know where your problem lies: HW, or SW (kernel or ROM).
The only problem that I did find in your kernel messages is that you have an unreadable bad block on your system partition. So, format just the system partition and reload the ROM of your choice. This should keep all your data intact.
Have the ROM of your choice ready on your SD card, put the gTab into APX mode, then fire up nvflash and format only the system partition (called APP in nvflash). After this boot into CWM and flash whatever ROM you want. You can also wipe the system partition while inside CWM using a
Code:
C:\> [B]adb shell erase_image system[/B]
command, but, I'm operating under the assumption that nvflash might do a more thorough job "fixing" non-factory-marked bad blocks.
Code:
C:\> [B]nvflash --bl bootloader.bin --format_partition 11 --go[/B]
You can use whatever bootloader.bin you want (1.1 or 1.2) as long as it is for the gTablet--it is not stored on the NAND flash when you run it with "--bl ...".
See this post http://forum.xda-developers.com/showpost.php?p=17926964&postcount=3. This user says he fixed his by opening & moving one of the speaker wires away from a contact on the board. Worth considering.
aabbondanza said:
See this post http://forum.xda-developers.com/showpost.php?p=17926964&postcount=3. This user says he fixed his by opening & moving one of the speaker wires away from a contact on the board. Worth considering.
Click to expand...
Click to collapse
Looks like a great solution. I will still try to format my gtablet and see if it works. If not, I'm going to open it. I have a question about your solution. You say that the sound works when the screen is off because there is no current. How comes that the notification sounds still work even with the screen on? Anyway, it fix the problem, I will try it
gitah said:
Looks like a great solution. I will still try to format my gtablet and see if it works. If not, I'm going to open it. I have a question about your solution. You say that the sound works when the screen is off because there is no current. How comes that the notification sounds still work even with the screen on? Anyway, it fix the problem, I will try it
Click to expand...
Click to collapse
You should definitely do rajeevvp's format suggestion since you are getting the unreadable block errors.
I was skeptical when I read the post (and even more skeptical as to why the user said it worked, but hey, stranger things have happened). I don't have the problem & I didn't say I had an explantation as to why it worked for this user. All I did was see the post & thought it was worth a try for you. If you want an answer you'll have to go to the post & ask the user.
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Help
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
hatoo said:
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Click to expand...
Click to collapse
It's in the works. CM10.1 compiles just fine, but i'm getting bootloops due lack of ion support in 2.6 kernel. I've managed to (mostly) port spro-specific things to CodeAurora's 3.4 kernel and fixed all compilation errors, but spro's device configuration routine is sort of different from vanilla msm8260 (some things are being configured by aboot, yet it's performing some checks that are unclear to me at the moment). Currently kernel fails to boot and device is getting into the blink-camera's flash-and-switch-screen-off mode (same mode device gets when it's turned on with volume-up+volume-down keys).
Oh, and by the way: i've tried to contact both Compal (odm and actual kernel developer for spro) and Dell to get information about what kernel was used in that unreleased 062-world wide dell rom. Compal's mailserver refused to deliver my message, and Dell's opensource departament people responded only once askung if i seek information on 2.6 kernel. I've re-stated that i'm seeking information on 062 rom and 3.x kernel - no word from them since then
So, we're up to ourselves with this one. If anyone's capable and willing to help with resolving 3.4 kernel boot issues - drop a line into this thread - i'll upload my current kernel tree to github.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
Click to expand...
Click to collapse
Power+volume up+home if i recall it correctly. Another way is to issue
Code:
fastboot boot your-recovery-image-name.img
while in fastboot mode.
For those who it may concern
Here's a list of my SPro-related repos (in order of appearance):
2.6 kernel - original dell sources bumped to .14 along with other additions. should be suitable for ics-based roms.
caf-3.4 kernel - my current point of interest.
device/dell/msm8660-common and device/dell/streakpro - device source trees for cyanogenmod 10.1, both based on htc pyramid device trees.
While I've never had a SPro, good luck with it.
Awesome!
I use GS01 as my main device, so I'm looking forward to your custom ROM!
Sort of update.
Dell responded:
I apologize for the delay. I have learned that we did not update to 3.x. I think you may have the latest versions. Thank you for your inquiry.
Click to expand...
Click to collapse
So, we're on our own. Great..
Request
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Is this ok?
kibuuka said:
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Click to expand...
Click to collapse
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
hatoo said:
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
Click to expand...
Click to collapse
Yep just what I needed, thanks hatoo.
kibuuka said:
Yep just what I needed, thanks hatoo.
Click to expand...
Click to collapse
Hi Kibuuka!
What about DS5 ICS development, are still working on it?
Regards...
Dell steak 5 can't enter fastboot and always restarting somebody help me pls
unlock
Not really the right thread to ask that, but not able to get into fastboot or not able to get into recovery?
Dell Streak Pro GS01 (E mobile)
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
shakes1883 said:
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
Click to expand...
Click to collapse
First of all - as a rule of thumb you're better NOT to use one-click solutions for anything - these ARE evil.
Let's think you don't want to/can't disassemble it.
You'll need:#1 drivers for Spro - grab it here, #2 fastboot and adb binaries - grab these, #3 one of the stock ROMs - TheManii did a great job collecting them - select one containing SPro in filename from here, #4 CWM recovery image - grab this one (courtesy of TheManii) and #5 - superuser flasheable package (by TheManii as well)
You have to wait until phone's battery is fully drained.
After that you need to connect it to pc. It will enter so called "charge-only state" (charging battery animation). Wait until it fully charges (LED will become green). Disconnect it from pc/power supply now.
Then you'll need to turn it on by pushing power button AND volume down at the same time to enter fastboot mode - screen will go black with two lines on it:
Code:
FATBOOT!!!!
Version 0.5
Connect your phone to pc - you'll see third line
Code:
USB cable connected
and windows will ask for drivers for device (if you don't have them installed already)
After drivers installation you're set to fix you problem.
Open command prompt and cd to a dir containing adb and fastboot binaries (let's assume full path is y:\adb\ and you have copied CWM image into this folder):
Code:
cd y:\adb\
Then boot (we don't flash it this time preserving your device's warranty ) into CMW recovery
Code:
fastboot boot y:\adb\SPro-6.0.1.2.img
You'll see good'ol CWM recovery screen. Navigate to "Mounts and storage", then select "mount USB storage". Your pc will now be able to access phone's internal and external storage. Now copy ROM image of choice and superuser package to either of phone's partitions you've connected to pc on previous step.
Select Unmount in CWM menu (AFTER you did a safe device removal in windows - thin precaution will save you some nerves).
Navigate to "install zip from sdcard", then to "choose zip from sdcard", select ROM image you've copied previously, select "Yes - Install update-zip-you-have-selected.zip"
CWM will install ROM image for you.
Now do the same selecting superuser package instead of ROM image and install it as well.
Select "reboot system now". If everything's ok you'll see your device booting into your newly installed ROM. If it doesn't - get to fastboot mode again, boot CMW image and do a factory reset using it ("wipe data/factory reset").
I'll just leave it here
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
kibuuka said:
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
WOW! AMAZING! Never expect Streak pro will have CM. Thank you so much for you work.
Finally!!
So nice ROM!!
I love you Kibu lol
Please Support Custom rom dell streak pro
I know many xda dev community is a good: Good:, the dell streak pro help you make a rom version 4.x so it works better : O
thanks!
- CPU: Qualcomm MSM8260A Snapdragon, 1.5 GHz Dual-Core Processor
- RAM: 1 GB Memory: 4 GB
- External Memory MicroSD (T-Flash) up to 32 GB
- Camera: 8.0 MP, support LED flash, autofocus
- Cinematography: FullHD 1080p @ 30fps
- Battery capacity: 1520 mAh
- Super AMOLED Plus display with 16 million colors Resolution giai540 x 960 pixels Size 4.3 inches
- OS: 2.3.5 Androi
are looking forward to the help of kibuuka well as helping people in xda
kibuuka said:
Not creating separate thread for this, just teasing a bit .
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
hope you help fix bugs present in nodules rom, dell community treak pro users have been waiting for this day ever. thank you very much
Hello all!
I realize that many many Android users have that issue and don't get any satisfying answer.
Let me introduce you my own experience. This may help and clear things up about Android safe mode.
It started one week ago when I got into a party and the barman threw lots of water at my friends and me. When I went to bed I didn't bother dry myself up, went straight to bed and slept.
When I woke up the next morning (with such a bad headache by the way ), my phone was acting really weird :
1 : it couldn't recognize my SIM card or any SIM card
2 : the little textbox "Safe Mode" had appeared
3 : My Volume up/Volume Down buttons weren't working anymore.
I rebooted the device several times, wondering why would it do that to me!! I googled that all day to understand what was happening to it.
All of the sudden, after a reboot, the Sim Card was recognized again and this problem was fixed. Yay!
Then, I tried all I could about the buttons (opened the device with youtube tutorial and a Torx screw driver T5) tried to clean the volume flex cable, dry it... Nothing to do.
The volume buttons still not responding, safe mode still here.
There are several reasons for safe mode to show itself :
-Holding a button while booting (depending on the device and manufacturer) : simply reboot the device to get back in normal mode.
-A previously downloaded and installed app is causing issues on the device (Android self protection) : you'll need to find that app and uninstall it to get back in normal mode.
-I ran into a forum where someone was explaing how changing one of his internal components that wasn't working anymore fixed his safe mode problem (mostly non responding buttons like my phone).
So I ordered a brand new volume flex cable for my HTC sensation and I am still wating for it (long delivery...) I'll let you know as soon as I replace the component if that has fixed it.
The problem is : in the meantime I just can't access non system apps (in other words : all origin apps, no others). I bought a smartphone to be able to do many more things on it than just call, text message or email...
So I found a solution about it (I am going to test it tonight and will let you know) :
You need to have a rooted device in order to install all apps that you need to run, even though Android is running under safe mode, into /system/apps location. This will "make believe" those apps are actually system apps and will force your device run them at boot.
How does this work?
You need to get ADB tool in order to push command shell to the device (because terminal emulator or other apps that ease root commands directly on the device can't be loaded... Thanks safe mode!!)
!!!!! Important !!!!!!! I haven't tested this myself yet but will tonight and will let you know on that thread, so watch it before doing anything you wouldn't understand.
from Adb terminal you'll need to get into the system partition and mount it as read and write :
adb shell
su
mount -o remount,rw /dev/null /system
give everyone permissions to write in that folder :
chmod 777 /system/app/
Then, you'll need to store the apks you need into your sdcard (wherever).
Then, copy all apps you need into the folder :
cp -a /sdcard/[pathtoyourapk/theapkyouwanttoinstall] /system/app/
reset the permissions on that folder :
chmod 755 /system/app/
mount -o remount,ro /dev/null /system
sync
Reboot the device :
reboot
You're done.
Don't hesitate correct me if I gave any wrong information, but trust me, I spent enough time on this problem to get self confident and write in here.
Thanks for your attention!
Regards!
Adding information
I tested it and it does work.
However I forgot something :
Once you've copied your apk into the system\app folder just chmod it with 644 :
chmod 644 /system/app/[yourapp.apk]
This will give the system and yourself access grant to the application.
There! =)
Description:
This module fixes flashlight of Samsung GALAXY Ace Plus custom ROMs to be able to use any Camera or flashlight app from play store.
If you have a device with the same issue, contact me to see if I can support/fix your device as well.
Google play link:
Flashlight Fixer (Xposed)
Xposed repo link:
Flashlight Fixer
Change log:
Version 1.4:
Applying settings doesn't require rebooting/closing apps.
Added options to enable/disable:
Flash light alternative toggling method
Removing flash mode from camera parameters.
Hooking flash modes, auto/no focus.
Version 1.3:
Support for more devices.
Flash device, supported modes and delays are changeable now, be sure to force close your camera/flashlight app after each change to take effect.
Version 1.2:
Improved auto flash.
Compatible with more ROMs like Pure GALAXY.
Version 1.1:
Optimized auto flash.
Version 1.0:
Initial release.
Awesome!!! It works....
When using auto mode in Camera flash the flash light should get on when focusing but it doesn't. Instead the flashlight starts after the focus is completed due to which the photo gets way too overexposed. Hope it will get fixed in near updates.
awesome man testing it wwill feedback
Androidoo said:
awesome man testing it wwill feedback
Click to expand...
Click to collapse
Androidoo said:
it doesnt works on cm 10.0
Click to expand...
Click to collapse
Did you tick/enable the module in modules tab after successfully installing the framework?
Did you get any error messages?
kk9999gada said:
Awesome!!! It works....
When using auto mode in Camera flash the flash light should get on when focusing but it doesn't. Instead the flashlight starts after the focus is completed due to which the photo gets way too overexposed. Hope it will get fixed in near updates.
Click to expand...
Click to collapse
Thanks for your feedback, the focus control mechanism seems to be written in native code which can't be altered using Xposed, so I just increased the time between turning the flash on and taking the picture to avoid overexposure.
Also added the module to play store (it takes about 2 hours for changes to take effect on the store, just in case you didn't find v1.1 there)
Bassel Bakr said:
Thanks for your feedback, the focus control mechanism seems to be written in native code which can't be altered using Xposed, so I just increased the time between turning the flash on and taking the picture to avoid overexposure.
Also added the module to play store (it takes about 2 hours for changes to take effect on the store, just in case you didn't find v1.1 there)
Click to expand...
Click to collapse
Now the exposure seems to be alright. Thanks for this module.
Bassel Bakr said:
Did you tick/enable the module in modules tab after successfully installing the framework?
Did you get any error messages?
Click to expand...
Click to collapse
ya i did activated and reboot.. n also when i open camera it asks for priviliges(root) and it says root has been granted but no flash..i guess only with me
Androidoo said:
ya i did activated and reboot.. n also when i open camera it asks for priviliges(root) and it says root has been granted but no flash..i guess only with me
Click to expand...
Click to collapse
Oh I forgot to mention it, I use root access to keep track of flash mode since Xposed offers read-only access to app preferences.
Can you tell me which CM 10 ROM are you using? I will download it and check the problem.
Superuser
In Techkang's CM10.1 and Speedmod ROM the flashlight works in all apps even when denying superuser.
So can you remove superuser permission from the app for this reason because there is no need of unnecessarily giving superuser to all the flashlight apps.
Edit : Superuser access is required for using auto mode for flashlight
AWESOME!!
Thanks a whole lot!
Really helps for us darkskinned Kenyans. Can't see a brother on the camera without flash bruh
Made my phone a bit slow but it will live.
On CM 10.2 Dirty(something). Forgot name.
Oh! And flash has to be set to Auto else it will forever shine(lol)
Entropy is at 4k, Performance @ 600MHz and sio.
Thanks again. :good:
Bassel Bakr said:
Oh I forgot to mention it, I use root access to keep track of flash mode since Xposed offers read-only access to app preferences.
Can you tell me which CM 10 ROM are you using? I will download it and check the problem.
Click to expand...
Click to collapse
cm 10.0 pure galaxy i get the toast flashlight have been given superusr but nothing happens tested wwith cymera too
Androidoo said:
cm 10.0 pure galaxy i get the toast flashlight have been given superusr but nothing happens tested wwith cymera too
Click to expand...
Click to collapse
1. Put the attachment in /system/etc/init.d
2. Remove (.txt) extension.
3. Give it 755+ permission.
4. Reboot.
V1.2
V1.2 Works Good. This version removes the requirement of superuser. Tested on various apps such as Camera JB+, QR Barcode Scanner, Stock Camera. Works flawlessly.
V1.3
Works Good. Thanks.
I've set Flash and autofocus delay to 500 milliseconds which works like charm in low light.
how to use
sorry am new to this. am using htc sensation with custom rom vipers 5.2.1 how can i use this mod if it even works on my phone. my phone takes blurry pics in the dark cz the the camera focuses when the flashlight is off
---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------
Bassel Bakr said:
Description:
This module fixes flashlight of Samsung GALAXY Ace Plus custom ROMs to be able to use any Camera or flashlight app from play store.
If you have a device with the same issue, contact me to see if I can support/fix your device as well.
Google play link:
Flashlight Fixer (Xposed)
Xposed repo link:
Flashlight Fixer
Click to expand...
Click to collapse
HTC sensation has the same issue
v.konvict said:
sorry am new to this. am using htc sensation with custom rom vipers 5.2.1 how can i use this mod if it even works on my phone. my phone takes blurry pics in the dark cz the the camera focuses when the flashlight is off
---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------
HTC sensation has the same issue
Click to expand...
Click to collapse
Set Auto focus delay to 1000/2000, force close the camera and reopen it again, auto focus will start one/two minute(s) after the flash had turned on.
If it didn't work set the same values to Infinite focus delay, force close the camera and reopen it again.
Bassel Bakr said:
Set auto focus delay to 1000/2000, force close the camera and reopen it again, auto focus will start one/two minutes after the flash had turned on.
If it didn't work set the dame values to Inifinte focus, force close the camera and reopen it again.
Click to expand...
Click to collapse
unfortunately am getting stuck at bootanimation when i enable this mod....can you fix this
v.konvict said:
unfortunately am getting stuck at bootanimation when i enable this mod....can you fix this
Click to expand...
Click to collapse
Can you give me a logcat please?
Code:
adb logcat -v threadtime
And use these adb shell commands to disable the module:
Code:
adb root
adb shell
su
cd /data/data/de.robv.android.xposed.installer/conf
# Uncomment next two lines to disable all of the modules
#rm modules.list
#reboot
cp modules.list modules.list~
for a in `cat modules.list`
do
case $a in
*bassel*) continue;;
*) echo $a >> new;;
esac
done
mv new modules.list
reboot
Just copy and paste them all in the terminal or command prompt and hit enter, your device will reboot after that.
Bassel Bakr said:
Can you give me a logcat please?
Code:
adb logcat -v threadtime
And use these adb shell commands to disable the module:
Code:
adb root
adb shell
su
cd /data/data/de.robv.android.xposed.installer/conf
# Uncomment next two lines to disable all of the modules
#rm modules.list
#reboot
cp modules.list modules.list~
for a in `cat modules.list`
do
case $a in
*bassel*) continue;;
*) echo $a >> new;;
esac
done
mv new modules.list
reboot
Just copy and paste them all in the terminal or command prompt and hit enter, your device will reboot after that.
Click to expand...
Click to collapse
when do we do this , after installation and reboot?
Hi
I've installed CM10.2 (last update) (http://forum.xda-developers.com/showthread.php?t=2499796) on my Archos 80G9. It also runs the SDE firmware from Archos (http://forum.xda-developers.com/showthread.php?t=1653566). So far, so good, it runs quite nicely, all things concerned. Here's a screenshot to the system info: https://www.dropbox.com/s/0ri8n4jb6gyrfz7/Screenshot_2014-11-17-20-56-01.png?dl=0
Now I'm trying to install X-posed Framework, but this won't work. When I try, I get an error that tells me /system can't be mounted. (Screenshot: https://www.dropbox.com/s/ryaryqkie023sl4/Screenshot_2014-11-17-20-40-16.png?dl=0 )
When I take a look is ES3 if the folder is mounted, it looks like this: https://www.dropbox.com/s/4kwv0ja16qz52tq/Screenshot_2014-11-17-20-49-21.png?dl=0 . I can't tick the other boxes here, I get the message "sorry, operation failed" when I try.
I've already tried to use the "mount -o remount,rw /" command, to no avail...
I have no idea how I have to fix this problem and if it's even fixable.
Does anyone have any idea? Thanks in advance!
Same here...
No solution for that yet.
Before you type the mount command did you type "su" first (without the quotes)?
Just opening up terminal gives you regular user permissions which will not let you run the mount command. You need to become root/superuser first and that's what su does.
Yes I did ... Terminal emulator gives a notification that It's been granted superuser permission, but it still doesn 't Work.
Sent from my Ascend Y300 using XDA Free mobile app
Can you send a screenshot of the "mount" comand and response?
Did the prompt change from $ to #? What was the output of "mount"?
If terminal doesn't work try with superuser adb (allow superuser not only from applications, but from adb). Connect to the device with "adb shell" and issue this command.
Hi, thanks for your response. Here are two screenshots: the first is of the mount command in Terminal Emulator, the second of the same via abd shell. No results.
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Bor-ka said:
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Click to expand...
Click to collapse
1) I had 2.7 Experimental, so I uninstalled it and installed 2.6 Stable instead.
2) I do indeed use the "classical" option for installing Xposed.
3) Tried it, gave the following result: the file is created in /System/bin, so I guess /sytem is mounted okay. (see screenshots)
4) I use SuperSU, XPosed had root acces (see screenshot)
Seems to me /system is mounted fine, but Xposed just doesn't know it...
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Bor-ka said:
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Click to expand...
Click to collapse
Alright, did all of it.
1) Don't fully understand what is listed here, but in the first screenshot is the list of mounts.
2) Checked it, doesn't seem to exist, see second screenshot.
3) Logcat is attached.
Ok, it appears that I got the problem. Need a little time to think how to solve this.
The problem is rather technical. In newer androids supersu has isolated filesystem mounts for different processes.
It means that if you remount filesystem rw in one process, it (read-write-ness) is not accessible to the other process.
I have a little older cm10.2 build (for low-memory devices), perhaps, this was enforced later.
http://su.chainfire.eu/#how-mount (3.5)
So you're saying there's a good chance that if I install version 22_12_2013-13_29_20 (which i was planning anyway), instead of the latest one, the problem could be fixed?
Hmm, I installed the previous version of CM10.2, the problem seems to be persisting...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work. Seems I do have rw access to /system, but not with all apps...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work (permission denied). Seems I do have rw access to /system, but not with all apps...
Well, it seems like what I've said, filesystem mount encapsulation.
I've noticed one thing - you are using the standalone supersu application. And for me superuser mode is integrated in the system settings near the developer options. May be this is the case, internal superuser is patched already.
Alright, I'll uninstall superSU for now, give it a go with the built-in superuser app. I'll let you know!
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself.
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Bor-ka said:
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself..
Click to expand...
Click to collapse
Eureka! I re-installed CM, issued the mount-command i used earlier and installed X-posed! I used the built-in superuser app, no such problems as before. I did have to issue the mount-command, but that isn't a problem Is it normal I have to re-issue the mount-command each time I want to access /system rw?
Thanks a million! I can't believe it was something this trivial But I'm so glad it's solved, thanks!
Bor-ka said:
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Click to expand...
Click to collapse
I don't use the deepsleep-option. I do use Greenify to ensure certain apps (like Youtube or Chrome) aren't active in the background. Boot manager to be sure only essential apps boot in the first place. This seems to save me some battery life. Airplane mode as well.
I got this tablet from my dad because it was so slow he couldn't work with it. Even after factory reset, it very quickly became sluggish again. With CM, it feels like it's a new tablet. So no doubts about CM for me
I do have another issue: My pc won't show the tablet in explorer. I can access it via ADB, but I can't access the storage via explorer... I suppose I best start a new topic for that...
Glad the issue was solved. I wonder why the superuser application didn't work.. Deepsleep - it allowed the tablet to lose, say, 10-15% charge during a week sleep. Very handy if the tablet is used not often - really miss it.
Explorer connection - if I remeber correctly, you should go to settings -> storage (where the size of apps/pictures etc is shown). Then press the three dots in the upper right corner, select "usb computer connection" and select MTP.
P.S. I wonder also if CM12/Android 5.0 in the "development" section is worth a try...